LTE100-Motorola LTE Training

LTE100: Introduction to Long Term Evolution
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, Tasknder 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 conrms Motorola Ltds 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.
Contents

LTE100: Introduction to Long Term Evolution Chapter 1: Lesson 1: What is Long Term Evolution (LTE)?
Course Introduction . . . . . . . . . . . . . . . . . . . . . . Preface . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . Target Audience . . . . . . . . . . . . . . . . . . . . . . Conventions Used in this Guide . . . . . . . . . . . . . . Purpose of the Participant Guide . . . . . . . . . . . . . . References and Resources. . . . . . . . . . . . . . . . . Expectations . . . . . . . . . . . . . . . . . . . . . . . . Practicalities . . . . . . . . . . . . . . . . . . . . . . . . Course Objectives . . . . . . . . . . . . . . . . . . . . . Course Schedule . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . Drivers for Long Term Evolution (LTE) . . . . . . . . . . . . . 3rd Generation Partnership Project (3GPP). . . . . . . . . . . GSM Network Evolution . . . . . . . . . . . . . . . . . . . . Global System for Mobile Communication (GSM) Evolution . How Does LTE Fit into 3GPP Roadmap? . . . . . . . . . . 3GPP Release 8 Network Architecture (LTE) . . . . . . . . . . E-EUTRAN Air Interface . . . . . . . . . . . . . . . . . . . . Performance Goals for LTE. . . . . . . . . . . . . . . . . . . Spectrum Flexibility . . . . . . . . . . . . . . . . . . . . Spectrum Efciency . . . . . . . . . . . . . . . . . . . . Increased Peak Data Rates . . . . . . . . . . . . . . . . Increased User Throughput . . . . . . . . . . . . . . . . Control Plane Latency . . . . . . . . . . . . . . . . . . . User Plane Latency . . . . . . . . . . . . . . . . . . . . Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Coverage . . . . . . . . . . . . . . . . . . . . . . . Lesson 1 Summary. . . . . . . . . . . . . . . . . . . . . . . Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3 1- 3 1- 3 1- 3 1- 3 1- 3 1- 4 1- 5 1- 5 1- 6 1- 6 1- 8 1- 9 1-10 1-11 1-11 1-13 1-19 1-20 1-21 1-21 1-22 1-22 1-23 1-23 1-24 1-24 1-24 1-24 1-25 1-26
Chapter 2: Lesson 2: LTE Network Architecture

Objectives . . . . . . . . . . . . . . . . . . . . . . . 3GPP Release 8 Network Architecture (LTE) . . . . . . evolved Node B (eNodeB) . . . . . . . . . . . . . User Entity (UE) . . . . . . . . . . . . . . . . . . Mobility Management Entity (MME) . . . . . . . . . Serving Gateway (S-GW). . . . . . . . . . . . . . Packet Data Network Gateway (P-GW) . . . . . . . Other EPC Network Elements . . . . . . . . . . . Interworking with Other Technologies . . . . . . . . eNodeB Reference Points . . . . . . . . . . . . . Motorola LTE Architecture . . . . . . . . . . . . . . . eNodeB . . . . . . . . . . . . . . . . . . . . . . Wireless Broadband Controller (WBC) 700 . . . . . Wireless Broadband Controller (WBC) 700 as S-GW Wireless Broadband Core (WBC) 700 as P-GW . . Wireless Broadband Manager (WBM) 700 . . . . . WBM 700 Features. . . . . . . . . . . . . . . . . GSM to LTE Migration/Overlay . . . . . . . . . . . CDMA LTE Overlay . . . . . . . . . . . . . . . . CDMA Evolution . . . . . . . . . . . . . . . . . . Self-Organizing Network (SON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3 2- 4 2- 4 2- 5 2- 6 2- 8 2- 9 2-10 2-10 2-13 2-14 2-14 2-16 2-17 2-18 2-18 2-19 2-20 2-21 2-21 2-24
2010 Motorola, Inc.
Contents
SON Denition . . . . . . . . . . Motorola SON Architecture . . . . Proposed Motorola SON Features Lesson 2 Summary. . . . . . . . . . Memory Points . . . . . . . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
2-24 2-24 2-25 2-26 2-27
Chapter 3: Lesson 3: LTE Air Interface

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

Objectives . . . . . . . . . . . . . . . . . . . . . . . . Selected EPS Interfaces . . . . . . . . . . . . . . . . . EPS and the TCP/IP Protocol Suite . . . . . . . . . Control Plane . . . . . . . . . . . . . . . . . . . . User Plane . . . . . . . . . . . . . . . . . . . . . . Uu Interface Data Link Layer . . . . . . . . . . . . . . . Radio Resource Control (RRC) Sublayer . . . . . . . Packet Data Convergence Protocol (PDCP) Sublayer Radio Link Control (RLC) Sublayer . . . . . . . . . . Medium Access Control (MAC) Sublayer . . . . . . . Uu Physical Layer . . . . . . . . . . . . . . . . . . SAE and LTE Channel Architecture . . . . . . . . . . . Logical Channels . . . . . . . . . . . . . . . . . . . Transport Channels . . . . . . . . . . . . . . . . . Physical Channels . . . . . . . . . . . . . . . . . . Transport to Physical Channel Mapping. . . . . . . . Mapping DL Physical Channels to Subframes . . . . . . Broadcast Channel . . . . . . . . . . . . . . . . . . Synchronization Signals . . . . . . . . . . . . . . . Mapping UL Physical Channels to Subframes . . . . . . Mapping PUCCH to Subframes . . . . . . . . . . . Random Access Channel. . . . . . . . . . . . . . . Random Access Operation . . . . . . . . . . . . . . S1-MME Interface . . . . . . . . . . . . . . . . . . . . S1-MME Interface Control Protocol Stack. . . . . . . S1 Application Protocol (S1AP) Functions . . . . . . UE to MME Control Plane . . . . . . . . . . . . . . S1-U and S5-U Interfaces . . . . . . . . . . . . . . . . S1-U User Plane Protocol Stack . . . . . . . . . . . S5 Interface User Plane Protocol Stack . . . . . . . S5 Control Plane Protocol Stack . . . . . . . . . . . Uu to P-GW User Plane . . . . . . . . . . . . . . . X2 Interface Functions . . . . . . . . . . . . . . . . . . X2 Control Plane Protocol Stack . . . . . . . . . . . X2 Application Protocol (X2AP) Functions . . . . . . X2 User Plane Protocol Stack . . . . . . . . . . . . Lesson 4 Summary. . . . . . . . . . . . . . . . . . . . Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 3 4- 4 4- 4 4- 5 4- 6 4- 8 4- 9 4- 9 4- 9 4-10 4-10 4-11 4-11 4-13 4-14 4-15 4-16 4-16 4-17 4-20 4-20 4-21 4-22 4-24 4-24 4-25 4-27 4-28 4-28 4-29 4-29 4-30 4-31 4-31 4-32 4-33 4-36 4-37
Chapter 5: Lesson 5: Network Acquisition and Call Process

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Procedures . . . . . . . . . . . . . . . . . . . . . . . Radio Resource Control (RRC) States . . . . . . . . . . . . . Radio Resource Control (RRC) Idle . . . . . . . . . . . Radio Resource Control (RRC) Connect . . . . . . . . . Radio Resource Control (RRC) Connection . . . . . . . . . EPS Mobility Management (EMM) States . . . . . . . . . . . . EPS Mobility Management (EMM) Deregistered . . . . . EPS Mobility Management (EMM) Registered . . . . . . EPS Connection Management (ECM) States . . . . . . . . . . EPS Connection Management (ECM) Idle . . . . . . . . EPS Connection Management (ECM) Connect . . . . . . EPS Session Management (ESM) . . . . . . . . . . . . . . . ESM_INACTIVE . . . . . . . . . . . . . . . . . . . . . . ESM_ACTIVE . . . . . . . . . . . . . . . . . . . . . . . Non Access Stratum (NAS) States . . . . . . . . . . . . . . . EMM_DEREGISTERED, ECM_IDLE and ESM_INACTIVE . EMM_REGISTERED, ECM_IDLE and ESM_ACTIVE . . . . EMM_REGISTERED, ECM_CONNECT and ESM_ACTIVE. Selected EPS IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 3 5- 4 5- 5 5- 5 5- 5 5- 5 5- 7 5- 7 5- 7 5- 8 5- 8 5- 8 5- 9 5- 9 5- 9 5-10 5-10 5-10 5-10 5-11
2010 Motorola, Inc.
iii
Contents
MME IDs . . . . . . . . . . . . . . . . . . . . . . . . UE IDs . . . . . . . . . . . . . . . . . . . . . . . . . International Mobile Subscriber Identier (IMSI) Structure Attaching to the Network . . . . . . . . . . . . . . . . . . . eNodeB Acquisition . . . . . . . . . . . . . . . . . . . System Information (SI) . . . . . . . . . . . . . . . . . Initial Cell Selection . . . . . . . . . . . . . . . . . . . Network Attach . . . . . . . . . . . . . . . . . . . . . . Quality of Service (QoS) / EPS Bearer . . . . . . . . . . . . Bearer Service Architecture . . . . . . . . . . . . . . . QoS Parameters . . . . . . . . . . . . . . . . . . . . . Service Request . . . . . . . . . . . . . . . . . . . . . . . UE Triggered Service Request Simplied . . . . . . . Mobility Procedures . . . . . . . . . . . . . . . . . . . . . Tracking Area (TA) . . . . . . . . . . . . . . . . . . . . MME and S-GW Pools . . . . . . . . . . . . . . . . . . Tracking Area Update (TAU) . . . . . . . . . . . . . . . X2 Handover . . . . . . . . . . . . . . . . . . . . . . UE Triggered Detach (UE Switched Off) . . . . . . . . . . . Security in LTE . . . . . . . . . . . . . . . . . . . . . . . . LTE Security Keys . . . . . . . . . . . . . . . . . . . . Function of LTE Security Keys . . . . . . . . . . . . . . Authentication and Key Agreement Process (AKA) . . . . Lesson 5 Summary. . . . . . . . . . . . . . . . . . . . . . Memory Points . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
5-11 5-12 5-13 5-14 5-14 5-15 5-16 5-16 5-18 5-19 5-20 5-21 5-21 5-22 5-22 5-23 5-24 5-25 5-28 5-30 5-30 5-31 5-31 5-33 5-34
iv
2010 Motorola, Inc.
About This Manual
Version 3 Rev 1

2010 Motorola, Inc.
Version 3 Rev 1
This page intentionally left blank.
2010 Motorola, Inc.
Lesson 1: What is Long Term Evolution (LTE)?
Version 3 Rev 1
Chapter 1

In this lesson, we will introduce the LTE standards body, dene LTE and its performance goals, look at the network architecture changes introduced by LTE, and compare/contrast LTE to current wireless technologies.
2010 Motorola, Inc.
1-1
Version 3 Rev 1
1-2
2010 Motorola, Inc.
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 nd 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.
Telecoms
LTE
300
Indicates a list of References that provide additional information about a topic. Indicates a Lab that provides the opportunity for you to exercise what youve learned.
Indicates a Warning or Caution. These generally ag a service affecting operation. Indicates a Memory Point. These provide a chance for the candidate to reect 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 youd 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.
2010 Motorola, Inc.
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
Telecoms
LTE
300
3GPP Technical Specications (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 Specication 36.322 Radio Link Control (RLC) Protocol Specication 36.323 Packet Data Convergence Protocol (PDCP) Specication 36.331 Radio Resource Control (RRC) Protocol Specication 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 RMAs to send boards back for repair, and download technical documentation.
1-4
2010 Motorola, Inc.
Course Introduction
Version 3 Rev 1
Course Introduction
Figure 1-1
The URL of the customer support web The URL of the customer support web page is: page is: hps://mynetworksupport.motorola.com hps://mynetworksupport.motorola.com This is a secure web site. A password This is a secure web site. A password request form can be downloaded from request form can be downloaded from this page. page. this pag ge.
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 locations 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.
2010 Motorola, Inc.
1-5
Version 3 Rev 1
Course Introduction
Course Introduction
Course Objectives
Describe the goals of the 3rd Generation Partnership Project (3GPP) Explain the performance goals of LTE Explain where LTE ts 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 Motorolas 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, S5C 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-6
2010 Motorola, Inc.
Version 3 Rev 1
Course Introduction
2010 Motorola, Inc.
1-7
Version 3 Rev 1
Objectives
Objectives
At the completion of this lesson, youll be able to: Describe the goals of the 3rd Generation Partnership Project (3GPP) Explain the performance goals of LTE Explain where LTE ts in the evolution of GSM/UMTS networks Explain how LTE differs from existing 3G networks Describe the changes in network architecture introduced by LTE
1-8
2010 Motorola, Inc.
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 xed-line operators are expanding their boundaries outside the home while the traditional mobile operators are moving into the xed line business. The goal of both is to capture maximum revenue while trying to meet the customers 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 exibility, 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).
2010 Motorola, Inc.
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 specications 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).
1-10
2010 Motorola, Inc.
GSM Network Evolution
Version 3 Rev 1

Figure 1-4 GSM Network Evolution
New mobile services such as streaming HD video, Online Gaming, Live Video, Social Networking, and Peer2Peer le 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, lets 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.
2010 Motorola, Inc.
1-11
Version 3 Rev 1

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 rst 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 trafc) and a Packet Switch Core Network (PS-CN, data trafc).
1-12
2010 Motorola, Inc.
Version 3 Rev 1

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 efcient 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.
2010 Motorola, Inc.
1-13
Version 3 Rev 1

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.
1-14
2010 Motorola, Inc.
Version 3 Rev 1

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 trafc now goes through the PS domain while all voice trafc (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 rst 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).
2010 Motorola, Inc.
1-15
Version 3 Rev 1

UMTSR4 Figure 1-11 UMTS R4
UMTS R4 provides a more efcient 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. 2. 3. Starts the shift to an all IP network with the introduction of the IP Multimedia Subsystem (IMS). The Circuit Switch Domain is collapsed moving the Softswitch and telephony functions into the IMS cloud.
1-16
2010 Motorola, Inc.
Version 3 Rev 1

Changes the UE functionality enabling it to setup multimedia calls using the IETFs Session Initiation Protocol (SIP). The IP Multimedia Subsystem replaces the call control and interworking functions of the circuit switched domain with a more exible, packet-based, multimedia core service architecture. Although originally dened 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 ows. 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.
2010 Motorola, Inc.
1-17
Version 3 Rev 1

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.
1-18
2010 Motorola, Inc.
3GPP Release 8 Network Architecture (LTE)
Version 3 Rev 1

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.
2010 Motorola, Inc.
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 efciency.
NOTE
OFDMA, SC-FDMA, TDD, FDD, and MIMO will be discussed in greater detail in Lesson 3.
1-20
2010 Motorola, Inc.
Performance Goals for LTE
Version 3 Rev 1

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 exible 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.
2010 Motorola, Inc.
1-21
Version 3 Rev 1

Spectrum Efciency
Spectrum efciency 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).
1-22
2010 Motorola, Inc.
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.
2010 Motorola, Inc.
1-23
Version 3 Rev 1

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 efciencies, 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 efciency is permitted. Cell ranges up to 100 km (~62 miles) are supporteddegradation is accepted.
1-24
2010 Motorola, Inc.
Lesson 1 Summary
Version 3 Rev 1
Lesson 1 Summary
In this lesson you learned about: The The The The The The key drivers for Long Term Evolution (LTE) Standards Body 3GPP that established the goals for LTE GSM network evolutions and the upgrade path to LTE Performance Goals for LTE changes to the current 3G architecture brought about by LTE 3GPP Release 8 (LTE) Network Architecture
2010 Motorola, Inc.
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 debrieng 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:
1-26
2010 Motorola, Inc.
Lesson 2: LTE Network Architecture
Version 3 Rev 1
Chapter 2

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 Motorolas LTE solution.
2010 Motorola, Inc.
2-1
Version 3 Rev 1
2-2
2010 Motorola, Inc.
Objectives
Version 3 Rev 1
Objectives
At the completion of this lesson, youll 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 Motorolas LTE network architecture
2010 Motorola, Inc.
2-3
Version 3 Rev 1

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.
2-4
2010 Motorola, Inc.
Version 3 Rev 1

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 congured 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
2010 Motorola, Inc.
2-5
Version 3 Rev 1

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. 3GPP TS 36.101 User Equipment (UE) Radio Transmission and Reception
Telecoms
LTE
2-6
300
2010 Motorola, Inc.
Version 3 Rev 1

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 users 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
2010 Motorola, Inc.
2-7
Version 3 Rev 1

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
2-8
2010 Motorola, Inc.
Version 3 Rev 1

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 (operators network and Internet). The P-GW provides charging (billing) support, packet ltering/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 verication
2010 Motorola, Inc.
2-9
Version 3 Rev 1

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 proles 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 ow detection, gating, QoS authorization and ow based charging. Applies the security procedures, as required by the operator, before accepting service information Decides how a certain service data ow will be treated in the P-GW and ensures that the P-GW user plane trafc mapping and treatment matches the users subscription prole Provides the S-GW with QoS policy and trafc ow 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.
2-10
2010 Motorola, Inc.
Version 3 Rev 1

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 dened by 3GPP. Non-3GPP access technologies include WiFi, WiMAX, xed 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.
2010 Motorola, Inc.
2-11
Version 3 Rev 1

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.
2-12
2010 Motorola, Inc.
Version 3 Rev 1

eNodeB Reference Points
Figure 2-10 eNodeB Reference Points
S1-MME Carries control plane trafc between E-UTRAN and MME. S1-U - Carries bearer plane trafc between the eNodeB and S-GW. S5 Carries control and bearer trafc 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 trafc between an S-GW and P-GW located in different networks. S10 - Carries context and other information between MMEs. S11 Carries control trafc 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.
2010 Motorola, Inc.
2-13
Version 3 Rev 1
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 Motorolas solution for each of the LTE Network Elements.
2-14
2010 Motorola, Inc.
Version 3 Rev 1

eNodeB
Figure 2-12 eNodeB Types
Motorolas 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 congurations: Traditional Frame where all equipment is co-located in a 19, indoor frame conguration Remote Radio Head where the transceiver and Power Amplier (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.
2010 Motorola, Inc.
2-15
Version 3 Rev 1

Wireless Broadband Controller (WBC) 700
Figure 2-13 Wireless Broadband Controller (WBC) 700
Motorolas 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
2-16
2010 Motorola, Inc.
Version 3 Rev 1

Wireless Broadband Controller (WBC) 700 as S-GW
Figure 2-14 WBC 700 as S-GW
Motorolas 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 congurations: Standalone S-GW or, Standalone P-GW or, Combined S-GW and P-GW
2010 Motorola, Inc.
2-17
Version 3 Rev 1

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 dened 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.
2-18
2010 Motorola, Inc.
Version 3 Rev 1

WBM 700 Features
Figure 2-17 WBM 700 Features
2010 Motorola, Inc.
2-19
Version 3 Rev 1

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) GSM to LTE Overlay
Figure 2-19
2-20
2010 Motorola, Inc.
Version 3 Rev 1

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. Motorolas 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).
2010 Motorola, Inc.
2-21
Version 3 Rev 1

CDMA Evolution
CDMA2000 technical specications are established by the 3rd Generation Partnership Project 2 (3GPP2). 3GPP2 was set up in late 1998 to create globally applicable specications 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).
2-22
2010 Motorola, Inc.
Version 3 Rev 1

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.
2010 Motorola, Inc.
2-23
Version 3 Rev 1
Self-Organizing Network (SON)

SON Denition
A self-organizing network is a network that can automatically extend, change, congure, and optimize its topology, coverage, capacity, cell size, and channel allocation based on changes in location, trafc pattern, interference, and the situation/environment. Purpose Reduce operational costs Focus Areas Self-installation and self-conguration Self-operating Self-optimization Operator controls the behavior of the SON instead of controlling detail and xed 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-conguring, 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 conguration 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 NEs, 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
2-24
2010 Motorola, Inc.
Version 3 Rev 1

controls, verication of SON optimization recommendations (establishing trust), and full tracking of all manual and automated conguration 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 conguration capabilities required which span across the network or multiple NE types.
Proposed Motorola SON Features

Basic Auto Operations { { { { { Autonomous Inventory, auto detection, test and conguration of hardware on insert Near Real-Time PM reporting Automatic EMS Software Upgrade Automatic NE Software Upgrade Dynamic Conguration of signaling links Automatic generation of radio, HO conguration parameters Auto Backup and restore
Advanced Auto Operations Resource outage detection and action, e.g. Sleeping Cell Outage Compensation Smart re-conguration
Basic Deployment { { { { { Auto-detect PnP hardware, auto-authenticate Auto inventory On connection to EMS, auto-software upgrade Auto RF/Transport cong 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 conguration of X2 signaling link
Subscriber Trace Support { NE support for trace on per-subscriber identity (IMSI) and per-equipment identity (IMEI) basis
2010 Motorola, Inc.
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 Trafc Areas and Pooling (MME and S-GW) concepts How LTE interworks with other technologies Motorolas LTE architecture Motorolas migration paths from GSM/CDMA to LTE
2-26
2010 Motorola, Inc.
Memory Points
Version 3 Rev 1
Memory Points
2010 Motorola, Inc.
2-27
Version 3 Rev 1
Memory Points
2-28
2010 Motorola, Inc.
Lesson 3: LTE Air Interface
Version 3 Rev 1
Chapter 3

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.
2010 Motorola, Inc.
3-1
Version 3 Rev 1
3-2
2010 Motorola, Inc.
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 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
Telecoms
LTE
300
2010 Motorola, Inc.
3-3
Version 3 Rev 1
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
3-4
2010 Motorola, Inc.
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 1 2 3 4 5 6 7 8 9 10 11 12 13 14 ... 17 ... 33 34 35 36 37 38 39 40
Note1:
Uplink (UL) 19201980 MHz 18501910 MHz 17101785 MHz 17101755 MHz 824849 MHz 830840 MHz 25002570 MHz 880915 MHz 1749.91784.9 MHz 17101770 MHz 1427.91452.9 MHz 698716 MHz 777787 MHz 788798 MHz 704716 MHz
Downlink (DL) 21102170 MHz 19301990 MHz 18051880 MHz 21102155 MHz 869894 MHz 875885 MHz 26202690 MHz 925960 MHz 1844.91879.9 MHz 21102170 MHz 1475.91500.9 MHz 728746 MHz 746756 MHz 758768 MHz 734746 MHz
Duplex Mode FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD TDD TDD TDD TDD TDD TDD TDD TDD
Channel BW Supported 5, 10, 15, 20 MHz 1.4, 3, 5, 10, 15Note1, 20Note1 MHz 1.4, 3, 5, 10, 15Note1, 20Note1 MHz 1.4, 3, 5, 10, 15, 20 MHz 1.4, 3, 5, 10Note1 MHz 5, 10Note1 MHz 5, 10, 15, 20Note1 MHz 1.4, 3, 5, 10Note1 MHz 5, 10, 15Note1, 20Note1 MHz 5, 10, 15, 20 MHz 5, 10Note1, 15Note1, 20Note1 MHz 1.4, 3, 5Note1, 10Note1 MHz 1.4, 3, 5Note1, 10Note1 MHz 1.4, 3, 5Note1, 10Note1 MHz 1.4, 3, 5Note1, 10Note1 MHz 5, 10, 15, 20 MHz 5, 10, 15 MHz 1.4, 3, 5, 10, 15, 20 MHz 1.4, 3, 5, 10, 15, 20 MHz 5, 10, 15, 20 MHz 5, 10 MHz 5, 10, 15, 20 MHz 10, 15, 20 MHz
19001920 MHz 20102025 MHz 18501910 MHz 19301990 MHz 19101930 MHz 25702620 MHz 18801920 MHz 23002400 MHz
The UE receiver sensitivity may be relaxed when operating at this channel bandwidth.
2010 Motorola, Inc.
3-5
Version 3 Rev 1

E-UTRA is designed to operate in the RF bands listed above. 3GPP TS 36.101 E-UTRA UE Radio Transmission and Reception
Telecoms
LTE
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 Sampling Freq (Fs) 1.4 MHz 1.92 MHz 3 MHz 3.84 MHz 5 MHz 7.68 MHz 10 MHz 15.36 MHz 15 MHz 23.04 MHz 20 MHz 30.72 MHz
3-6
300
2010 Motorola, Inc.
Orthogonal Frequency Division Multiplexing (OFDM)
Version 3 Rev 1

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.
2010 Motorola, Inc.
3-7
Version 3 Rev 1

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.
3-8
2010 Motorola, Inc.
Version 3 Rev 1

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 dont interfere with each other, and dont 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
2010 Motorola, Inc.
3-9
Version 3 Rev 1

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.
3-10
2010 Motorola, Inc.
Version 3 Rev 1

Subcarrier Receiver Operation
Figure 3-8 Subcarrier Receiver Operation
At the receiver, each subcarrier receives the modulated signal at its specic frequency, demodulates the signal into bits, and restores the original bit pattern.
Fast Fourier Transform (FFT)

Figure 3-9 IFFT Operation
We dont 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).
2010 Motorola, Inc.
3-11
Version 3 Rev 1

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.
3-12
2010 Motorola, Inc.
Version 3 Rev 1

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 Nominal Channel Bandwidth Parameters Sampling Freq (Fs) NFFT 1.4 MHz 1.92 MHz 128 3 MHz 3.84 MHz 256 5 MHz 7.68 MHz 512 10 MHz 15.36 MHz 1024 15 MHz 23.04 MHz 1536 20 MHz 30.72 MHz 2048
2010 Motorola, Inc.
3-13
Version 3 Rev 1

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 Nominal Channel Bandwidth Parameters Sampling Freq (Fs) NFFT Subcarrier Spacing (f) For multimedia broadcast/multicast (MBMS) trafc, LTE uses 7.5 kHz subcarrier spacing. 1.4 MHz 1.92 MHz 128 3 MHz 3.84 MHz 256 5 MHz 7.68 MHz 512 10 MHz 15.36 MHz 1024 15 MHz 23.04 MHz 1536 20 MHz 30.72 MHz 2048
3-14
2010 Motorola, Inc.
Version 3 Rev 1

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 xed-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.
2010 Motorola, Inc.
3-15
Version 3 Rev 1

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 trafc 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.
3-16
2010 Motorola, Inc.
Version 3 Rev 1

Cyclic Prex
Figure 3-15 Cyclic Prex
The Cyclic Prex 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 Prex 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 Prex guarantees a whole number of Hz per symbol time and no phase or amplitude changes during the extended symbol time (requirements of FFT). LTE denes two TCP sizes, normal (4.67 microseconds) and extended (16.67 microseconds).
2010 Motorola, Inc.
3-17
Version 3 Rev 1

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
3-18
2010 Motorola, Inc.
Version 3 Rev 1

Occupied Subcarriers
Figure 3-17 Occupied Subcarriers
Occupied Subcarriers Nominal Channel Bandwidth Parameters Sampling Freq (Fs) NFFT Subcarrier Spacing (f) Occupied Subcarriers 72 180 300 600 900 1200 1.4 MHz 1.92 MHz 128 3 MHz 3.84 MHz 256 5 MHz 7.68 MHz 512 10 MHz 15.36 MHz 1024 15 MHz 23.04 MHz 1536 20 MHz 30.72 MHz 2048
2010 Motorola, Inc.
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 congurations for Frame Type 1 or 2. Calculating the Frame Rate
1.
Assuming 10 ms per frame, how many LTE frames are transmitted per second?
3-20
2010 Motorola, Inc.
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.
2010 Motorola, Inc.
3-21
Version 3 Rev 1
Channel Direction
Channel Direction
Figure 3-20 Channel Direction
The Down Link (DL) carries trafc owing from or through the eNodeB to the subscribers, while the Up Link (UL) carries trafc from the subscriber stations to the eNodeB. DL and UL bandwidth is shared by the active subscribers in a sector. DLand UL trafc 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)
3-22
2010 Motorola, Inc.
Channel Direction
Version 3 Rev 1
Channel Direction
FDD uses pairs of frequencies, one to transmit trafc from the eNodeB to the subscribers (DL) and one to receive trafc 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 trafc. Both DL and UL trafc 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.
2010 Motorola, Inc.
3-23
Version 3 Rev 1
Frame Type 1 Structure

Slots
Figure 3-23 Frame Type 1 Slots
10 ms Frame Frame Type 1

.5 ms Slot S S S S S S S S S S S l l l l l l l l l l l o o o o o o o o o o o t t t t t t t t t t t 0 1 2 3 4 5 6 7 8 9 1 0 S S S S l l l l o o o o t t t t 1 1 1 2 1 3 1 4 S S S S l l l l o o o o t t t t 1 5 1 6 1 7 1 8 .5 ms Slot S l o t 1 9
C P
Symbol
If normal TCP used, slot contains 7 symbols For normal TCP , symbol 0 TCP size is 5.21 s For normal TCP , symbols 1-6 TCP size is 4.67 s
Type 1 frames are divided into 20 slots; each slot is .5 ms long. Depending on the length of the Cyclic Prex, a slot contains either 7 or 6 symbols. (As illustrated above, a slot which uses normal size Cyclic Prexes contains 7 symbols). If extended Cyclic Prexes are used, a slot contains only 6 symbols. Every extended TCP is exactly the same size (16.67 microseconds). For FDD operation, this frame structure occurs simultaneously for both the DL and UL on their respective frequencies. For normal sized Cyclic Prexes, the rst symbols Cyclic Prex is slightly larger than the TCP of the other symbols in the slot.
3-24
2010 Motorola, Inc.
Version 3 Rev 1

Resource Blocks and Resource Elements
Figure 3-24 Resource Blocks and Resource Elements
7 or 6 Symbols Slot Resource Block f=1 f=2 f=3
RB RB
12 Subcarriers (180 kHz)
Resource Element
RB RB
S=0 S=n f=11 f=12
Bandwidth within slots is allocated based on resource blocks. A resource block is 180 kHz (12 subcarriers) in the frequency domain and one slot in the time domain. A resource element is one subcarrier by one symbol. A resource element may carry modulated data or a reference signal. When using normal sized TCP, a resource block contains 84 resource elements (12 subcarriers by 7 symbols). When using extended TCP, a resource block contains 72 resource elements (12 subcarriers by 6 symbols).
Physical and Virtual Resource Blocks

3GPP standards describe physical resource blocks and virtual resource blocks. A Physical Resource Block (PRB) consists of consecutive subcarriers in the frequency domain and consecutive symbols in the time domain. Virtual Resource Blocks (VRB) are mapped to physical resource blocks. A VRB may be either localized or distributed. Calculating Resource Blocks per Slot
Calculating Resource Blocks per Slot Nominal Channel Bandwidth Parameters Sampling Freq (Fs) NFFT Subcarrier Spacing ( f ) 1.4 MHz 1.92 MHz 128 3 MHz 3.84 MHz 256 5 MHz 7.68 MHz 512 10 MHz 15.36 MHz 1024 15 kHz 15 MHz 23.04 MHz 1536 20 MHz 30.72 MHz 2048
2010 Motorola, Inc.
3-25
Version 3 Rev 1

Nominal Channel Bandwidth Parameters 1.4 MHz 3 MHz 180 5 MHz 300 10 MHz 600 15 MHz 900 20 MHz 1200 72 Occupied Subcarriers Resource Blocks per Slot 1. Using the formula below, calculate the number of resource blocks per slot for each channel size. Occupied Subcarriers / Subcarriers per Resource Block
Reference Signals
Figure 3-25 Reference Signals
DL and UL directions use different numbers of reference signals. For the DL, 4 reference signals are distributed in the resource block. For the UL, an entire symbol time is devoted to carrying reference signals. Note that the graphic shows resource blocks using normal sized TCP. All of the unshaded resource elements may be used to carry modulated data or control information. The graphic illustrates the DL reference signals used with normal TCP for a single port antenna. Two and four port antennas use a different DL reference signal pattern for each port. Two port antennas use an 8 reference signal pattern for the DL, while four port antennas use a 12 reference signal pattern for the DL.
3-26
2010 Motorola, Inc.
Version 3 Rev 1

Frame Type 1 Subframes
Figure 3-26 Frame Type 1 Subframes
Adjacent slots are combined into a subframe; each subframe is 1 ms long. DL and UL bandwidth allocations are made within a subframe. In TDD operation, a subframe may be associated with either the DL or UL direction.
2010 Motorola, Inc.
3-27
Version 3 Rev 1

FDD Operation DL
Figure 3-27 FDD Operation DL
Control information at the beginning of a DL subframe describes both DL scheduling and UL resource allocations (grants). The DL subframe may include broadcast information, including system information or paging. Every UE must receive and interpret the broadcast information. DL scheduling is described in the control information. For example, DL trafc intended for UE1 is described using the starting resource block within the subframe, number of resource blocks which carry the UE1 data, and modulation scheme selected by the eNodeB. The DL scheduling information is carried in the Physical DL Control Channel (PDCCH).
3-28
2010 Motorola, Inc.
Version 3 Rev 1

FDD UL Operation
Figure 3-28 FDD Operation UL
UL bandwidth allocations, also known as grants, are also described in the PDCCH. UL grants indicate the UE, the starting resource block within the UL subframe, number of resource blocks allocated to the UE, and modulation scheme selected by the eNodeB. The UE must completely ll the bandwidth grant, inserting padding if necessary. The UL subframe may also contain a Random Access Channel. The Random Access Channel allows subscribers to request bandwidth, re-enter the network from idle mode, and so on.
2010 Motorola, Inc.
3-29
Version 3 Rev 1
Frame Type 2
Frame Type 2
Figure 3-29 Frame Type 2
Frame Type 2 is designed exclusively for TDD operation. Similar to Frame Type 1, a Type 2 Frame is 10 milliseconds long, and contains 10 1-ms subframes. With the exception of Special Subframes (Subframe 1 and possibly 6), each DL or UL subframe contains two .5 ms slot; each slot contains 6 or 7 symbol periods. DL scheduling and UL grants are always described in the DL PDCCH channel. The DL and UL subframe allocations are controlled by the eNodeB. They may vary from frame to frame.
Special Subframe
A Special Subframe contains Downlink Pilot Timeslot (DwPTS), Guard Period (GP), and Uplink Pilot Timeslot (UpPTS) elds. The DwPTS eld contains the primary timing (slot synchronization) signal UpPTS may be used for UL Sounding Reference Signals or the PRACH channel GP provides a DL-to-UL guard interval
3-30
2010 Motorola, Inc.
Frame Type 2
Version 3 Rev 1
Frame Type 2
Frame Type 2 UL/DL Congurations
Frame Type 2 UL/DL Congurations Dl-to-UL UL/DL Switch-Point Cong. 0 Period 0 1 2 3 4 5 6 5 ms 5 ms 5 ms 10 ms 10 ms 10 ms 5 ms DL DL DL DL DL DL DL Subframe Number 1 1 S S S S S S 2 UL UL UL UL UL UL UL 3 UL UL DL UL V DL V 4 5 6 S S S DL DL DL S 7 UL UL UL DL DL DL UL 8 9
UL DL DL DL DL DL UL DL DL DL DL DL UL DL
UL UL UL DL DL DL DL DL DL DL DL DL UL DL
Note In the table above, S refers to the Special Subframe format.
2010 Motorola, Inc.
3-31
Version 3 Rev 1
OFDM Bandwidth Allocation

Figure 3-30 OFDM Bandwidth Allocation
OFDM assigns all subcarriers for a symbol to a single user. Although a user may be allocated more than one symbol time, OFDM was not intended to assign less than a full symbol period. That may be wasteful, depending on the actual user bandwidth requirement.
OFDMA Bandwidth Allocation

Figure 3-31 OFDMA Bandwidth Allocation
3-32
2010 Motorola, Inc.
Version 3 Rev 1

Orthogonal Frequency Division Multiple Access (OFDMA) assigns bandwidth more efciently than OFDM. Rather than allocating all subcarriers for a symbol to a single user, OFDMA assigns resource blocks as needed to users. LTE uses OFDMA on the DL. LTE allocates DL (OFDMA) bandwidth based on resource blocks rather than individual subcarriers.
2010 Motorola, Inc.
3-33
Version 3 Rev 1
OFDMA Transmitter Functions
OFDMA Transmitter Functions

Figure 3-32 OFDMA Transmitter Functions
The OFDMA transmitter must perform the following steps: 1. 2. 3. 4. 5. 6. Channel Coding Bits are scrambled, encoded for Forward Error Correction, and interleaved. Modulation The encoded bits are grouped into 1 to 6 bit symbols and modulated using BPSK, QPSK, 16QAM, or 64QAM. Channel Mapping The modulated signals are mapped into all or part of the channel for the required number of symbol times. Inverse FFT (IFFT) This step creates the time-domain waveform by summing the modulated subcarriers. Cyclic Prex Insertion This step attaches the Cyclic Prex to the beginning of the symbol. Transmit Power is adjusted as needed and the waveform is transmitted by one or more antenna ports.
3-34
2010 Motorola, Inc.
OFDMA Receiver Functions
Version 3 Rev 1
OFDMA Receiver Functions

Figure 3-33 OFDMA Receiver Functions
The OFDMA receiver must perform the following steps: 1. 2. 3. 4. 5. 6. Receive The UE receives the waveform from the eNodeB. Cyclic Prex Removal The CP is removed from the front of the symbol. FFT FFT recreates the frequency spectrum of the received signal, recreating the subcarriers and their modulated bits. Channel Demapping The channel mapping is reversed to discover individual user's symbols. Demodulation Each modulated symbol is demodulated into its original bits. Channel Decoding The bits are returned to their original order (de-interleaved), FEC error correction is performed, and bits are unscrambled. The resulting bit stream should be identical to the original bit stream in the transmitter.
2010 Motorola, Inc.
3-35
Version 3 Rev 1
Single Carrier-Frequency Division Multiple Access (SC-FDMA)

OFDMA Issues
LTE does not use OFDMA for the UL. OFDMA problems include: High Peak-to-Average Power Ratio (PAPR or PAR) Per subcarrier equalization for all subcarriers High sensitivity to frequency offset for mobile subscribers High amplitude power peaks occur when the transmitted signal is a combination of all of the subcarriers. To deal with the resulting high Peak-to-Average Power Ratio, the power amplier must have a greater linear range than other technologies, such as SC-FDMA. The eNodeB is capable of greater power and complexity than the UE. OFDMA is appropriate for DL trafc from the eNodeB to the UE. However, it was not selected for the UL direction.
UE Requirements
UE requirements include: Reduced complexity Lower transmit power High QoS at cell boundaries High data rates Although the eNodeB is fully capable of transmitting and receiving OFDMA symbols, the UE must balance reduced complexity and lower transmit power requirements with support for high data rates and good QoS at cell boundaries. For the UL, Single Carrier Frequency Division Multiple Access (SC-FDMA) was selected to meet those requirements. SC-FDMA helps with PAPR reduction by adding extra encoding steps. The modulated bits are run through a Discrete Fourier Transform (DFT) algorithm using a subset of subcarriers with a xed amplitude, then mapped into a limited number of subcarriers. The normal Inverse FFT process views this as a single-carrier input spread over a few subcarriers. All other subcarriers are set to null, reducing the power (and battery) requirements in the UE. The unused subcarriers may be used by other UEs in the cell.
3-36
2010 Motorola, Inc.
Version 3 Rev 1

SC-FDMA Transmitter Functions
Figure 3-34 SC-FDMA Transmitter Functions
The SC-FDMA transmitter must perform the following steps: 1. 2. 3. 4. 5. 6. 7. Channel Coding Bits are scrambled, encoded for Forward Error Correction, and interleaved. Modulation The encoded bits are grouped into 1 to 6 bit symbols and modulated using BPSK, QPSK, 16QAM, or 64QAM. DFT The modulated symbols are run through an Discrete Fourier Transform (DFT) process with a limited number of subcarriers at a xed amplitude. Subcarrier Mapping The FFT frequency domain output is mapped into part of the channel. All other subcarriers are set to null. Inverse FFT (IFFT) This step creates the time-domain waveform by adding the modulated subcarriers. The output is called an SC-FDMA symbol. Cyclic Prex Insertion Attaches the Cyclic Prex to the beginning of the symbol Transmit Power is adjusted as needed and the waveform is transmitted. SC-FDMA specic behavior is associated with steps 3, 4, 11, and 12. We will discuss these additional steps over the next few pages.
2010 Motorola, Inc.
3-37
Version 3 Rev 1

SC-FDMA Receiver Functions
Figure 3-35 SC-FDMA Receiver Functions
The SC-FDMA receiver must perform the following steps: 1. 2. 3. 4. 5. 6. 7. Receive The eNodeB receives the waveform from the UE. Cyclic Prex Removal The CP is removed from the front of the symbol. FFT FFT recreates the frequency spectrum of the received signal, recreating the subcarriers and their modulated symbols received in step 5 Subcarrier Demapping The channel mapping is reversed to discover individual user's symbols. Inverse DFT (IDFT) The DFT process from step 3 is reversed to discover the time domain of the signals. Demodulation Each modulated symbol is demodulated into its original bits. Channel Decoding The bits are returned to their original order (de-interleaved), FEC error correction is performed, and bits are unscrambled. The resulting bit stream should be identical to the original bit stream in the transmitter.
3-38
2010 Motorola, Inc.
Version 3 Rev 1

OFDMA Subcarrier Encoding
Figure 3-36 OFDMA Subcarrier Encoding
Lets compare OFDMA and SC-FDMA subcarrier encoding for twelve subcarriers for one symbol time. As shown above, our serial bit stream is modulated using QPSK. In the OFDMA example, each QPSK symbol is encoded in parallel on a separate subcarrier. Because the eNodeB transmits over the entire range of occupied subcarriers, the QPSK data symbols are already positioned at the desired location in the channel bandwidth; no separate step is needed to shift the symbol location. As described earlier, the eNodeB allocates subcarriers in units of 12 adjacent subcarriers (a resource block).
2010 Motorola, Inc.
3-39
Version 3 Rev 1

SC-FDMA Subcarrier Encoding
Figure 3-37 SC-FDMA Subcarrier Encoding
SC-FDMA subcarrier encoding is signicantly different. Instead of transmitting each data symbol in a separate subcarrier, SC-FDMA transmits M data symbols in the same subcarrier and symbol time. These sub-symbols are spread over M subcarriers. In other words, each SC-FDMA symbol contains M sub-symbols transmitted at the rate M times 15 kHz. As shown in the example, the value of M is 12. Unlike OFDMA, the SC-FDMA signal appears to be more like a single-carrier with each data symbol represented by a wide signal spanning several subcarriers.
3-40
2010 Motorola, Inc.
Modulation and Coding Schemes (MCS)
Version 3 Rev 1

Selected Transmitter Functions
Figure 3-38 Selected Transmitter Functions
Lets discuss the rst two steps of the transmission process: channel coding and modulation. In Step 1, bits are scrambled, encoded for Forward Error Correction, and interleaved. Scrambling shufes the bit pattern to avoid long strings of 0 or 1 bits. Forward Error Correction (FEC) adds redundant bits to the transmitted data enabling the receiver to correct errors without requesting retransmission. In Step 2, the scrambled, interleaved, and forward error corrected bits are grouped into 2-6 bit symbols and modulated using QPSK, 16QAM, or 64QAM. These functions are performed by both OFDMA and SC-FDMA transmitters. In either case, the receiver must reverse these actions.
Modulation Techniques Supported

Modulation techniques supported: BPSK 1 bit per symbol QPSK 2 bits per symbol 16QAM 4 bits per symbol 64QAM 6 bits per symbol DL trafc uses QPSK, 16QAM, 64QAM UL trafc uses QPSK, 16QAM, (64QAM optional) LTE devices use QPSK, 16QAM and 64QAM to modulate data and control information. The eNodeB supports all of these modulation techniques for the Down Link direction. However, 64QAM is optional in the Up Link direction.
2010 Motorola, Inc.
3-41
Version 3 Rev 1

Modulation Review
Figure 3-39 Modulation Review
Each symbol represents 1-6 bits depending on the modulation technique. Each data point represents a different bit pattern. QPSK bit patterns are illustrated on the graphic.
3-42
2010 Motorola, Inc.
Version 3 Rev 1

Modulation and Signal Quality
Figure 3-40 Modulation and Signal Quality
A modulation technique is selected based on the measured SNR. Subscribers located away from the eNodeB must use more robust modulation schemes (lower throughput), or they will experience unacceptable data loss rates. In addition, subscribers close to a cell boundary may experience inter-cell interference. Each modulation scheme has a threshold SNR ratio. For example, lets assume QPSK is associated with SNR 9 dB, 16QAM with 15 dB, and 64QAM with 25 dB. If the SNR drops below 15 dB, the eNodeB will instruct the UE to use QPSK modulation.
2010 Motorola, Inc.
3-43
Version 3 Rev 1

Estimating FDD Capacity
The formula below estimates the FDD capacity for a given channel bandwidth and modulation
MCS?
TCP Size and # of Antenna Ports?
(Bits per Symbol * Data Resource Elements per Resource Block) * Channel Size? 20 100
(Resource Blocks per Slot * Slots per frame) * Frames per second
Calculating DL Capacity Reference Nominal Channel Bandwidth Parameters Sampling Freq (Fs) NFFT 1.4 MHz 1.92 MHz 128 3 MHz 3.84 MHz 256 180 15 5 MHz 7.68 MHz 512 300 25 10 MHz 15.36 MHz 1024 600 50 15 MHz 23.04 MHz 1536 900 75 20 MHz 30.72 MHz 2048 1200 100
72 Occupied Subcarriers Resource Blocks per Slot 6
Calculating FDD DL Capacity
Assume normal sized TCP and one antenna port are used for each of the following questions. The table above is included for reference. 1. Estimate the DL capacity in bits per second for a 20 MHz channel operating at 64QAM. 6 X 80 X 100 X 20 X 100 =
2.
Estimate the DL capacity in bits per second for a 20 MHz channel operating at QPSK.
3.
Estimate the DL capacity in bits per second for a 5 MHz channel operating at 16QAM.
3-44
2010 Motorola, Inc.
Version 3 Rev 1

Calculating FDD UL Capacity
Using the formula and table from the facing page, estimate the FDD UL capacity for a given channel bandwidth and modulation scheme. Assume normal sized TCP and one antenna port are used for each of the following questions. 1. Estimate the UL capacity in bits per second for a 20 MHz channel operating at 16QAM. 4 X 72 X 100 X 20 X 100 =
2.
Estimate the UL capacity in bits per second for a 20 MHz channel operating at QPSK.
3.
Estimate the UL capacity in bits per second for a 5 MHz channel operating at 16QAM.
2010 Motorola, Inc.
3-45
Version 3 Rev 1
Multiple Antenna Systems

Figure 3-41 Multiple Antenna Systems
LTE Physical Layer services assume multiple port antenna systems are used. Multiple port antenna systems are implemented for the following reasons: Improved transmission reliability Greater coverage or range Reduced UE power consumption Increased transmission throughput Multiple port antenna systems include the following: Single Input Multiple Output (SIMO) Multiple Input Single Output (MISO) Multiple Input Multiple Output (MIMO)
3-46
2010 Motorola, Inc.
Version 3 Rev 1

Single Input Multiple Output (SIMO)
Figure 3-42 Single Input Multiple Output (SIMO)
In a SIMO conguration the transmitter (usually the UE) has one transmitter and the receiver (the eNodeB) has two physically separated antenna ports. The receiver picks up multiple versions of the same signal but separated spatially. SIMO receivers use the following techniques to compute the best received signal. Switched Diversity In Switched Diversity, the input with the best signal is chosen as the best source. The best signal may be based on Signal-to-Noise Ratio (SNR) or Bit Error Rate (BER). Switched diversity is the most simple and inexpensive SIMO technique. Equal Gain Combining Equal Gain Combining is a summation of all available received signals. Maximum Ratio Combining In Maximum Ratio Combining (MRC), each received signal has compensation applied to it before being combined to produce a composite single signal. This technique is particularly effective where the signal undergoes deep fading. Because fading probably occurs at different frequencies on each antenna port, the reliability of the radio link is increased.
2010 Motorola, Inc.
3-47
Version 3 Rev 1

Multiple Input Single Output (MISO)
Figure 3-43 Multiple Input Single Output (MISO)
A MISO (eNodeB) transmitter has two or more physically separated antenna ports, while the MISO (UE) receiver has one antenna. Each Tx port transmits the same information bits. In addition to data signals, reference signals are also transmitted via both antenna ports. The normal reference signal pattern is sent via the rst antenna port and the diversity reference signal pattern via the second antenna port. Space-Time Transmit Diversity (STTD) In Space-Time Transmit Diversity (STTD) the same data is transmitted simultaneously over both Tx ports. On each port, the channel-coded data is processed in blocks of four bits, then the bits are time reversed and complex conjugated. The physical separation of the antenna ports provides the space diversity, and the time difference derived from the bit-reversing process provides the time diversity. These features together make the decoding process in the receiver more reliable.
3-48
2010 Motorola, Inc.
Version 3 Rev 1

Multiple Input Multiple Output (MIMO)
Figure 3-44 Multiple Input Multiple Output (MIMO)
MIMO systems contain multiple antenna ports at both the transmitter and receiver. The MIMO transmitter transmits signals using time, frequency, and space diversity. The MIMO receiver recovers the data across multiple receiving antenna ports. MIMO antenna systems are not unique to LTE; WiMAX, WiFi, and some cellular networks also use MIMO. The techniques described in this topic apply to any MIMO system; they are not restricted to LTE.
2010 Motorola, Inc.
3-49
Version 3 Rev 1

MIMO Techniques
Figure 3-45 MIMO Techniques
Space-Time Coding (STC) Space-Time Coding (STC) provides diversity gain to combat the effects of unwanted multipath propagation. Similar to STTD, time delayed and coded versions of the same signal are sent from the same transmitter antenna. The codes that are used are mainly: trellis and block (less complex) codes. This improves the SNR for cell edge performance. Spatial Multiplexing (SM) With Spatial Multiplexing, unique (different) data streams are transmitted over different antenna ports. Spatial multiplexing can double (2x2 MIMO) or quadruple (4x4 MIMO) capacity and throughput. This technique gives higher capacity when RF conditions are favorable and users are closer to the eNodeB. The graphic shows spatial multiplexing with a 2x2 MIMO conguration. The receiver can identify the transmitting antenna port for each received signal. A combination of spatial multiplexing and space-time coding may be implemented. Depending on the RF conditions, a device may dynamically switch between the two MIMO techniques.
3-50
2010 Motorola, Inc.
Version 3 Rev 1

Single User MIMO (SUMIMO)
Figure 3-46 Single User MIMO (SUMIMO)
MIMO supports single user MIMO and multi-user MIMO. Single User MIMO improves the performance for a UE (via space time coding), or increases the throughput for a UE (using spatial multiplexing).
Multi-User MIMO (MUMIMO)

Figure 3-47 Multi-User MIMO (MUMIMO)
In multi-user MIMO, the data for different users is multiplexed onto a single time-frequency resource, so the capacity of the cell can increase in terms of users without increasing the system bandwidth. Switching between SU-MIMO and MU-MIMO is supported on a per UE basis. The use of codes and reference signals not only allows the receiver to differentiate between antenna streams and users, but also allows accurate channel estimation.
2010 Motorola, Inc.
3-51
Version 3 Rev 1

Open Loop vs Closed Loop MIMO Figure 3-48 Closed Loop MIMO
MIMO supports both open loop and closed loop control. Open loop MIMO transceivers adjust their transmission based on received (reference signal) measurements. This assumes no rapid feedback technique is available from the UE receiver back to the eNodeB transmitter. Unfortunately, in open loop operation, the transmitter receives no feedback regarding antenna port operation or signal strength in the forward direction. Closed loop MIMO supports a feedback loop describing eNodeB transmitter operation and UE recommendations. Both the eNodeB and UE contain a codebook which describes possible RF parameters, for example, the phase shift between antenna ports. In closed loop MIMO, the UE describes eNodeB transmitter operation by returning an index into the shared codebook. Closed loop operation uses the following steps. 1. 2. 3. 4. The eNodeB transmits a DL pilot channel as a reference signal on all antenna ports. he UE evaluates various codebook options that specify the RF parameters. The UE transmits its recommendations in the form of a codebook index to the eNodeB. The eNodeB adjusts its DL transmission to the UE based on the recommended parameters.
3-52
2010 Motorola, Inc.
Lesson 3 Summary
Version 3 Rev 1
Lesson 3 Summary
State the operating frequencies used by the LTE air interface Describe OFDM subcarrier and symbol concepts 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
2010 Motorola, Inc.
3-53
Version 3 Rev 1
Memory Points
Memory Points
3-54
2010 Motorola, Inc.
Lesson 4: LTE and EPC Protocol Overview
Version 3 Rev 1
Chapter 4

In this lesson we will discuss the LTE Air Interface (Uu) sublayers, the LTE Logical and Physical Channels, and the S1, S5, and X2 interface User and Control Plane protocol stacks.
2010 Motorola, Inc.
4-1
Version 3 Rev 1
4-2
2010 Motorola, Inc.
Objectives
Version 3 Rev 1
Objectives
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, S5C and X2 User and Control Plane protocol stacks
2010 Motorola, Inc.
4-3
Version 3 Rev 1
Selected EPS Interfaces

S1-MME Carries control plane trafc between E-UTRAN and MME. S1-U Carries bearer plane trafc between the eNodeB and S-GW. S5 Carries control and bearer trafc 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 trafc between an S-GW and P-GW located in different networks. S10 Carries context and other information between MMEs. S11 Carries control trafc 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.
4-4
2010 Motorola, Inc.
Version 3 Rev 1

EPS and the TCP/IP Protocol Suite
Figure 4-2 TCP/IP Protocol Suite
The 3GPP standards describe an all-IP network. Both control plane (signaling) trafc and user plane (bearer) trafc user the TCP/IP protocol suite. Except for the LTE air (Uu) interface, essentially any Data Link and Physical Layer protocols are allowed. 3GPP mandates support for either IPv4 or IPv6, or both. Depending on the interface and trafc type, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or Stream Control Transmission Protocol (SCTP) may be used at the Transport Layer. The LTE air (Uu) interface subdivides the Data Link Layer into sublayers for user bearer and control trafc. All bearer trafc, including voice, video and data, uses IP for transport. Either IPv4 or IPv6, or both, may be supported.
2010 Motorola, Inc.
4-5
Version 3 Rev 1

Control Plane
Figure 4-3 Control Plane
A control plane describes the protocol stack(s) required to transport control (signaling) trafc. The LTE/SAE architecture distinguishes between signaling that directly controls the air interface or Access Stratum (AS), and Non-Access Stratum (NAS) signaling passed transparently from the UE to the MME. Radio Resource Control (RRC) signaling messages directly control the air (Uu) interface between the UE and eNodeB. As needed, the eNodeB will interwork RRC actions with S1 Application Protocol (S1AP) operations and forward the S1AP message to the MME. These access stratum actions include radio bearer management, user paging, radio mobility control, etc. NAS messages are carried inside of RRC messages, and passed transparently through the eNodeB to the MME. NAS actions Evolved Packet System (EPS) bearer management, GPRS Tunneling Protocol (GTP) management, security control and authentication, and so on.
4-6
2010 Motorola, Inc.
Version 3 Rev 1

User Plane
Figure 4-4 User Plane
A User Plane (UP) describes the protocol stack(s) required to transport data trafc. Data trafc includes any user bearer trafc such as voice or video packets, Internet access, email, and so on. In addition, application signaling messages are viewed as data. Application signaling messages are viewed as data; they are transparent to the LTE/SAE architecture. For example, voice over IP sessions are managed using Session Initiation Protocol (SIP). Essentially, the LTE/SAE architecture views SIP messages as regular data.
2010 Motorola, Inc.
4-7
Version 3 Rev 1
Uu Interface Data Link Layer

Figure 4-5 Uu Interface Data Link Layer
For the Uu (air) interface, LTE divides the Data Link Layer into the following sublayers: Radio Resource Control (RRC) Packet Data Convergence Protocol (PDCP) Radio Link Control (RLC) Medium Access Control (MAC) As illustrated in the graphic, control trafc and bearer trafc use different protocol stacks.
Figure 4-6
RRC and PDCP Sublayer Functions
4-8
2010 Motorola, Inc.
Version 3 Rev 1

Radio Resource Control (RRC) Sublayer
The Radio Resource Control (RRC) Sublayer is responsible for broadcast of system information, RRC connection and conguration control, paging, initial security activation, mobility and handovers, recovery from radio link failure and generic protocol error handling, measurement conguration and reporting, and MBMS scheduling. RRC connection and conguration control includes setting up Radio Bearer (RB) channels carrying user data, QoS conguration, and error recovery (ARQ and HARQ) conguration.
Packet Data Convergence Protocol (PDCP) Sublayer

The Packet Data Convergence Protocol (PDCP) Sublayer is responsible for transferring RRC signaling or user data, compressing data packet headers, timer-based packet discards, and encrypting packets. For signaling packets, the PDCP Sublayer also checks message integrity. 3GPP TS 36.331 Radio Resource Control (RRC) Protocol Specication 3GPP TS 36.323 Packet Data Convergence Protocol (PDCP) Specication
Telecoms
LTE
Figure 4-7
300
RLC and MAC Sublayer Functions
Radio Link Control (RLC) Sublayer

The Radio Link Control (RLC) Sublayer segments large packets and concatenates small packets for handling by the MAC Sublayer and Physical Layer. RLC supports acknowledged, unacknowledged, and transparent mode operation. In addition, the RLC Sublayer performs Automatic Repeat Request (ARQ) error recovery for data packets. ARQ is a retransmission error recovery technique.
2010 Motorola, Inc.
4-9
Version 3 Rev 1

Medium Access Control (MAC) Sublayer
The Medium Access Control (MAC) Sublayer performs dynamic scheduling of Physical Layer resources, and maps data and control trafc to and from the Physical Layer. The MAC Sublayer multiplexes RLC packets into a single MAC PDU for transmission by the Physical Layer. In addition, the MAC Sublayer performs Hybrid ARQ (HARQ) error recovery. Like ARQ, HARQ is a retransmission error recovery technique. 3GPP TS 36.322 Radio Link Control (RLC) Protocol Specication 3GPP TS 36.321 Medium Access Control (MAC) Protocol Specication
Telecoms
LTE
Uu Physical Layer
Figure 4-8 Physical Layer
As discussed in the last lesson, the Uu Physical (PHY) Layer applies FEC encoding, modulates bits, and maps the modulated signals into physical frames and subframes. In addition, the Physical Layer calculates and attaches a 24-bit Cyclic Redundancy Check (CRC) to the end of the MAC PDU before scrambling and modulating the packet.
4-10
300
2010 Motorola, Inc.
SAE and LTE Channel Architecture
Version 3 Rev 1

Figure 4-9 SAE and LTE Channel Architecture
The SAE and LTE Channel Architecture denes SAE bearer channels, Radio Bearer (RB) channels, Signaling Radio Bearer (SRB) channels, logical channels, transport channels, and physical channels. In general, each category behaves as a service access point between adjacent protocol layers. SAE Bearer An SAE bearer channel carries one or more service data ows between a UE and the EPC. Radio Bearer A radio bearer channel transports the data packets of an SAE Bearer from the eNodeB toward the UE. Each SAE Bearer has a one-to-one mapping with a radio bearer. Signaling Radio Bearer A SRB channel transports signaling packets between the RRC Sublayer and the PDCP Sublayer. Logical Channel A logical channel transports control or data trafc between the RLC Sublayer and the MAC Sublayer. Logical control channels are mapped to SRB channels, while logical trafc channels are mapped to RB channels. Logical channels describe the transmission reliability (RLC Acknowledged Mode, etc.). Transport Channel A transport channel forwards control or data trafc between the MAC Sublayer and the Physical Layer. Each logical channel is mapped to a transport channel. Transport channels describe how the information will be formatted before being transmitted (coding, transport block size, etc.). Physical Channel A physical channel provides the transmission media (resource elements) through which the information is actually transmitted. Each transport channel is mapped to a physical channel.
2010 Motorola, Inc.
4-11
Version 3 Rev 1

Logical Channels
Figure 4-10 Logical Channels
Logical channels provide control and data transport between the RLC and MAC Sublayers. Signaling trafc is carried by Control Channels (CCH), and data trafc is carried by Trafc Channels (TCH). Control channels are mapped to SRB channels, and trafc channels are mapped to user plane radio bearer channels. Figure 4-11 Logical Channel Types
Control Channels Broadcast Control Channel (BCCH) DL channel used to broadcast system information. Paging Control Channel (PCH) DL channel used to carry paging information when the network does not know the location of the UE. Common Control Channel (CCCH) Carries RRC signaling when no RRC connection currently exists for the UE. Dedicated Control Channel (DCCH) A bidirectional control channel used to carry signaling information when an RRC connection exists for the UE. Multicast Control Channel (MCCH) Carries multicast signaling information; it controls the operation of the MTCH channel.
4-12
2010 Motorola, Inc.
Version 3 Rev 1

Trafc Channels Dedicated Trafc Channel (DTCH) A point-to-point channel dedicated to one UE for transmission of user data. The DTCH may be uplink, downlink, or both. Multicast Trafc Channel (MTCH) A DL channel used to carry multicast data trafc.
Transport Channels
Figure 4-12 Transport Channel Types
Transport channels carry signaling and data trafc between the MAC Sublayer and the Physical Layer. Except for the RACH channel, each transport channel is mapped to one or more logical channels. Downlink Transport Channels Broadcast Channel (BCH) Forwards broadcast information to the entire cell. The BCH maps to the BCCH logical channel. Paging Channel (PCH) Forwards UE paging information to the entire cell. The PCH maps to the PCCH logical channel. Downlink Shared Channel (DL-SCH) Carries DL data and some control trafc. For data trafc, DL-SCH supports HARQ and dynamic link adaptation. The DL-SCH maps to the DCCH, CCCH, and DTCH logical channels. Multicast Channel (MCH) Carries multicast trafc for the entire cell. The MCH maps to the MCCH and MTCH logical channels. Uplink Transport Channels Uplink Shared Channel (UL-SCH) Carries UL data and some control trafc. The UL-SCH maps to the DCCH, CCCH, and DTCH logical channels. Random Access Channel (RACH) Used for initial access to the cell or when a known UE needs to transmit on the PUSCH or PUCCH and does not have a valid uplink grant. The RACH is not mapped to a logical channel.
2010 Motorola, Inc.
4-13
Version 3 Rev 1

Logical Channel to Transport Channel Mapping Figure 4-13 Logical Channel to Transport Channel Mapping
The graphic shows the mapping between the LTE logical channels and transport channels.
Physical Channels
Figure 4-14 DL Physical Channels
A physical channel is a set of resource elements carrying information originating from the higher layers. Each transport channel maps into a physical channel. Downlink Physical Channels Physical Broadcast Channel (PBCH) DL channel that carries broadcast information. Physical Hybrid ARQ Indicator Channel (PHICH) Carries Hybrid ARQ (HARQ) ACKs or NACKs for the UL transmissions on the PUSCH. Physical Control Format Indicator Channel (PCFICH) Transmitted every subframe to inform the UE about the number of OFDM symbols used for the PDCCH channel. Physical Downlink Control Channel (PDCCH) Informs the UE about the resource allocation for PCH and DL-SCH, plus the HARQ information relating to the DL-SCH. It also controls the UL-SCH scheduling grants and indicates the UE identity. The PDCCH has four formats, hence the need for the PCFICH. The PDCCH signaling is located in the rst 13 OFDM symbols in each subframe.
4-14
2010 Motorola, Inc.
Version 3 Rev 1

Physical Downlink Shared Channel (PDSCH) Carries downlink data and higher layer signaling. The PDSCH is allocated to different UEs periodically, usually every 1 ms. PDSCH channel coding, modulation, and subcarrier allocation is dynamically controlled by the PDCCH. Physical Multicast Channel (PMCH) Carries the MBMS data and control if the cell supports MBMS functionality. Uplink Physical Channels Figure 4-15 UL Physical Channels
Physical Random Access Channel (PRACH) Carries the random access preambles used when the UE makes initial contact with the network, etc. Physical Uplink Shared Channel (PUSCH) Carries uplink data and higher layer signaling. PUSCH is a shared channel allocated to different UEs periodically, usually every 1 ms. The channel coding, modulation, and subcarrier allocation is dynamically controlled by the PDCCH. Physical Uplink Control Channel (PUCCH) Carries uplink control information for a UE, including CQI, HARQ ACKs and NACKs, and UL scheduling requests.
Transport to Physical Channel Mapping

Figure 4-16 Transport to Physical Channel Mapping
The graphic shows the mapping between LTE transport channels and physical channels.
2010 Motorola, Inc.
4-15
Version 3 Rev 1
Mapping DL Physical Channels to Subframes

Figure 4-17 Mapping DL Physical Channels to Subframes
The PDCCH, PHICH, and PCFICH control channels occupy the 1st-3rd symbols of a subframe. The PDSCH channel occupies the remaining symbols of the subframe. The PCFICH channel is 16 resource elements long and is located in the 1st symbol. The PCFICH channel indicates how many (1-3) symbols are used by the DL control channels in this subframe. The PHICH channel is 12 resource elements long and is located in the 1st or 3rd symbol. This channel carries the HARQ ACKs and NACKs for packets sent by a UE on the uplink. The PDCCH channel occupies the remaining resource elements in the 1st-3rd symbols (as signaled by the PCFICH channel). The PDCCH channel describes DL trafc and UL bandwidth grants for each UE. DL trafc is carried in the PDSCH channel in the remaining symbols of the subframe. The graphic shows the Reference Signal pattern for port 0 of a 2-port MIMO antenna. The resource elements with an X are powered by antenna port 1.
4-16
2010 Motorola, Inc.
Version 3 Rev 1

Broadcast Channel
Figure 4-18 Physical Broadcast Channel
The Physical Broadcast Channel (PBCH) carries DL system bandwidth, the number of transmit antenna ports, Reference Signal transmit power, system frame number, and so on. This information is critical for UEs attempting to enter or re-enter the network. The PBCH is located on the 72 subcarriers centered around the DC subcarrier in slot 1, symbols 0 through 3. The PBCH information is spread over four consecutive LTE radio frames.
Synchronization Signals
Synchronization signals allow the UE to synchronize with the recurring slots and frames transmitted by the eNodeB. The Primary Synchronization Signal (P-SS) provides LTE slot synchronization. The Secondary Synchronization Signal (S-SS) provides LTE frame synchronization. In both cases, the sync signals are transmitted by the eNodeB on 62 subcarriers centered around the DC subcarrier.
2010 Motorola, Inc.
4-17
Version 3 Rev 1

Synchronization Signals, Frame Type 1 Figure 4-19 Sync Signals, Frame Type 1
For Frame Type 1, the Primary Synchronization Signal (P-SS) is located in the last symbol of slots 0 and 10. The graphic shows slots using a normal TCP, with the P-SS located in symbol 6.
4-18
2010 Motorola, Inc.
Version 3 Rev 1

The Secondary Synchronization Signal (S-SS) is located in the next to last symbol of slots 0 and 10. The P-SS and S-SS signals are sent on the same antenna port.
Synchronization Signals, Frame Type 2 Figure 4-20 Sync Signals, Frame Type 2
For Frame Type 2, the P-SS is carried in the 3rd OFDM symbol in subframes 1 and 6 (in the DwPTS eld). The S-SS is carried in the last symbol of Slots 1 and 11.
2010 Motorola, Inc.
4-19
Version 3 Rev 1
Mapping UL Physical Channels to Subframes

Figure 4-21 Mapping UL Physical Channels to Subframes
The graphic illustrates the mapping of UL physical channels to subframes. Resources for the PUSCH are allocated on a subframe basis by the eNodeB. Subcarriers are allocated in physical resource blocks and may be frequency hopped from subframe to subframe. The PUSCH may employ QPSK, 16QAM or 64QAM modulation.
4-20
2010 Motorola, Inc.
Version 3 Rev 1

Mapping PUCCH to Subframes
Figure 4-22 Mapping PUCCH to Subframes
The PUCCH carries uplink control information such as CQI, scheduling requests, and ACKs/NACKs for a UE. It is never transmitted simultaneously with the PUSCH. As shown in the graphic, the PUCCH transmission is frequency hopped at the slot boundary for added reliability.
2010 Motorola, Inc.
4-21
Version 3 Rev 1

Random Access Channel
Figure 4-23 Random Access Preamble
The Random Access Channel (RACH/PRACH) is an UL contention-based channel which allows any UE to request network entry, access a target cell after handover, access a cell to send a Scheduling Request, and so on. The UE uses the PRACH channel to send a Random Access Preamble. Random Access Preambles are transmitted on blocks of 72 contiguous 1.25 kHz subcarriers allocated for the Physical Random Access Channel (PRACH) by the eNodeB. For burst formats 0-3, the PRACH Conguration Index describes the burst format and subframe location within an LTE radio frame type 1. Burst Formats 2 and 3 are dened to support power balancing and low data rates at the cell edge. In addition, Frame Type 2 supports burst format 4. When using burst format 4, the UpPTS eld carries the PRACH channel using 7.5 kHz subcarriers. 3GPP TS 36.211 Physical Channels and Modulation
Telecoms
LTE
4-22
300
2010 Motorola, Inc.
Version 3 Rev 1

Random Access Operation
Figure 4-24 Random Access Operation
The graphic shows a random access handshake. 1. 2. 3. The eNodeB will allocate bandwidth for the PRACH in the UL. As needed, a UE will send a Random Access Preamble in the PRACH. If successful, the eNodeB will send a Random Access Response (RAR) PDU to the UE in a subsequent DL subframe. The RAR includes a temporary UE identity and a (small) UL resource grant to allow the network entry or other operation to continue.
2010 Motorola, Inc.
4-23
Version 3 Rev 1
S1-MME Interface
S1-MME Interface
Figure 4-25 S1-MME Interface
The S1-MME interface is an open logical interface that carries signaling information between an eNodeB and the MME. The S1-MME interface functions are: UE context management SAE bearer management S1-MME and S1-U link management GTP-U tunnels management Mobility for active UEs Paging Network sharing and NAS node selection coordination Security, including data condentiality, air interface encryption and key management, and data integrity Service and network access, including signaling data transfer, UE tracing, and location reporting 3GPP TS 36.410; S1 General Aspects and Principles 3GPP TS 36.411; S1 Layer 1
Telecoms
LTE
4-24
300
2010 Motorola, Inc.
S1-MME Interface
Version 3 Rev 1
S1-MME Interface
S1-MME Interface Control Protocol Stack
Figure 4-26 S1-MME Interface Control Protocol Stack
The graphic illustrates the S1-MME Interface signaling protocol stack. Any Physical Layer and Data Link Layer are allowed. The IP version may be IPv6 and/or IPv4. In either case, the S1 endpoints must support IP Differentiated Services (DiffServ) Code Points for QoS. Instead of using TCP or UDP, 3GPP selected Stream Control Transmission Protocol (SCTP) at Layer 4. Essentially SCTP offers TCP-like reliability and error recovery with UDP-like throughput. The S1 signaling state machine and messages are controlled by the S1 Application Protocol (S1AP). The S1 Interface signaling protocol stack provides: Reliable transfer of S1AP messages over the S1 Interface Networking and routing Redundancy in the signaling network Flow control and overload protection In the future, this Interface may support load-sharing and dynamic S1-MME conguration 3GPP TS 36.412; S1 Signaling Transport 3GPP TS 36.413; S1 Application Program (S1AP) 3GPP TS 36.411; S1 Layer 1
Telecoms
LTE
300
2010 Motorola, Inc.
4-25
Version 3 Rev 1
S1-MME Interface
S1-MME Interface
S1 Application Protocol (S1AP) Functions
Figure 4-27
The S1 Application Protocol (S1AP) provides the following functions: UE context transfer and context release SAE bearer management, including setting up, modifying and releasing SAE bearer channels Provides capability information to the UE Mobility Functions, including changing eNodeBs within LTE or RAN nodes between different RATs Paging S1 interface management functions, including S1 conguration and reset capability, error indication, overload handling, and load balancing Transfer NAS signaling before or after the UE context is established in the eNodeB S1 UE context release PDCP sequence number status transfer
4-26
2010 Motorola, Inc.
S1-MME Interface
Version 3 Rev 1
S1-MME Interface
UE to MME Control Plane
Figure 4-28 NAS Signaling Transport
The graphic illustrates the control plane between the UE and the MME, including the air (Uu) and S1-MME interfaces. The eNodeB interworks Access Stratum (AS) RRC and S1AP signaling; Non-Access Stratum (NAS) signaling is passed transparently from the UE to the MME.
2010 Motorola, Inc.
4-27
Version 3 Rev 1
S1-U and S5-U Interfaces

Figure 4-29 S1-U and S5-U Interfaces
The S1-U and S5-U interfaces forward user data trafc between the eNodeB and S-GW, and the S-GW and P-GW, respectively. Both interfaces support GPRS Tunneling Protocol (GTP) for IP mobility.
S1-U User Plane Protocol Stack

Figure 4-30 S1-U User Plane Protocol Stack
The graphic illustrates the protocol stack required to forward user data trafc over the S1-U interface. A user data packet (Layers 3-5) is encapsulated by the GPRS Tunneling Protocol (GTP). The GTP packet is carried by UDP/IP over any Data Link and Physical Layer. IPv4 and/or IPv6 may be supported. GTP is the IP mobility protocol initially dened for GPRS mobile devices. Although GTP predated the Internet Engineering Task Force (IETF) Mobile IP (MIP) standards, both GTP and MIP have the same objective: mobility across an IP based network. They differ mainly in how the mobility tunnels are created and managed.
4-28
2010 Motorola, Inc.
Version 3 Rev 1

Each data stream is carried on a dedicated transport bearer; each transport bearer is uniquely identied by the IP address and Tunnel Endpoint ID (TEID) of the GTP tunnel. 3GPP TS 36.414; S1 Data Transport 3GPP TS 29.274 Evolved GPRS Tunneling Protocol for EPS (GTPv2)
Telecoms
LTE
S5 Interface User Plane Protocol Stack

Figure 4-31 S5 Interface User Plane Protocol Stack
The S5-U interface forwards user plane trafc between an S-GW and a P-GW. The S5-U interface uses exactly the same protocol stack as the S1-U interface.
300
2010 Motorola, Inc.
4-29
Version 3 Rev 1

S5 Control Plane Protocol Stack
Figure 4-32 S5 Control Plane Protocol Stack
The graphic illustrates the S5 control plane protocol stack. The S5-CP interface carries signaling that manages the GTP tunnels between the S-GW and P-GW.
Uu to P-GW User Plane

Figure 4-33 UE to P-GW User Plane
The graphic illustrates the user plane between the UE and the P-GW, including the Uu, S1-U, and S5-U interfaces. Note that the P-GW extracts the original user trafc (Layer 3-5) from the GTP mobility tunnel. The resulting packet may be forwarded based on the user-supplied destination IP address, or placed in another GTP or Mobile IP tunnel and forwarded to another network. In the latter case, the P-GW will interwork the two mobility tunnels.
4-30
2010 Motorola, Inc.
X2 Interface Functions
Version 3 Rev 1
Figure 4-34 X2 Interface
The X2 interface is an open logical interface between two adjacent eNodeBs. The X2 interface carries control (signaling) information between the eNodeBs and forwards user data trafc as needed toward an S-GW or UE. X2 interface functions are: Intra LTE-Access-System Mobility Support for UE in LTE_ACTIVE, including UE context transfer, controlling user plane tunnels, and handover cancellation Load Management Inter-cell Interference Coordination General X2 management and error handling functions Trace functions Forward user data trafc as needed 3GPP TS 36.420; X2 General Aspects and Principles 3GPP TS 36.421; X2 Layer 1 3GPP TS 36.422; X2 Signaling Transport 3GPP TS 36.423; X2 Application Program 3GPP TS 36.424; X2 Data Transport
Telecoms
LTE
300
2010 Motorola, Inc.
4-31
Version 3 Rev 1
X2 Control Plane Protocol Stack
Figure 4-35 X2 Control Plane Protocol Stack
The graphic illustrates the X2 Interface signaling protocol stack. Any Physical Layer and Data Link Layer are allowed. The IP version may be IPv6 and/or IPv4. In either case, the X2 (eNodeB) endpoints must support Differentiated Services Code Points (DSCP) for QoS. Instead of using TCP or UDP, 3GPP selected Stream Control Transmission Protocol (SCTP) at Layer 4. Essentially SCTP offers TCP-like reliability and error recovery with UDP-like throughput. In addition, SCTP supports multi-homing for redundancy and continued operation even during a transport network failure. The X2 signaling messages and state machine are controlled by the X2 Application Protocol (X2AP). The X2 Interface signaling protocol stack provides: Reliable transfer of X2AP messages over the X2 Interface Networking and routing Redundancy in the signaling network Flow control and overload protection
4-32
2010 Motorola, Inc.
Version 3 Rev 1
X2 Application Protocol (X2AP) Functions
Figure 4-36 X2AP Functions
The X2 Application Protocol (X2AP) provides the following functions: Mobility management Allows the eNodeB to move the responsibility for a UE to another eNodeB. Mobility management includes forwarding of user plane data, Status Transfer and UE Context Release. Load management Indicates resource status, overload, and trafc load to an adjacent eNodeB. Reporting general error situations Reports general error situations, for which function- specic error messages have not been dened. Resetting the X2 Completely resets the X2 interface. Setting up the X2 Exchanges necessary data for the eNodeB to setup the X2 interface. eNodeB conguration update Updates application level data needed for two eNodeBs to interoperate correctly over the X2 interface.
2010 Motorola, Inc.
4-33
Version 3 Rev 1
X2 User Plane Protocol Stack
Figure 4-37 X2 User Plane Protocol Stack
The graphic illustrates the protocol stack required to forward user data trafc over the X2 interface. A data packet is encapsulated by the GPRS Tunneling Protocol (GTP). The GTP packet is carried by UDP/IP over any Data Link and Physical Layer. IPv4 and/or IPv6 may be supported. Each data stream is carried on a dedicated transport bearer; each transport bearer is uniquely identied by the IP address and Tunnel Endpoint ID (TEID) of the GTP tunnel. Mobility and X2 User Plane Figure 4-38 Mobility and X2 Data Transport 1
4-34
2010 Motorola, Inc.
Version 3 Rev 1
Why do we need X2 data transport? The X2 user plane allows side-haul of user trafc during a handover between two eNodeBs STEP 1. 2. 3. 4. The GTP mobility tunnel for a UE is initially anchored at a source or originating eNodeB (eNodeB1 in our example). After measuring the service available from the neighbor eNodeBs, the UE signals a handover to eNB2. The source and target eNodeBs perform the handover, and notify the MME of the operation. The original mobility tunnel persists until the users mobility tunnel can be anchored at eNodeB2. A side-haul tunnel is set up between eNodeB1 and eNodeB2 to forward incoming data trafc to the user. The MME instructs the S-GW to recongure the mobility tunnel for UE1, anchoring the tunnel at eNodeB2. After forwarding any remaining trafc between eNodeB1 and eNodeB2, the previous tunnel between the S-GW and eNodeB1 is deleted. The handover operation is now complete. 3GPP TS 36.424 X2 Data Transport
Telecoms
LTE
300
2010 Motorola, Inc.
4-35
Version 3 Rev 1
Lesson 4 Summary
Lesson 4 Summary
List the Uu, S1, S5, and X2 interface functions Describe the S1, S5, and X2 User and Control Plane protocol stacks Compare the LTE Uu User and Control Plane protocol stacks List the LTE logical channels Explain the functions of the LTE physical channels
4-36
2010 Motorola, Inc.
Memory Points
Version 3 Rev 1
Memory Points
2010 Motorola, Inc.
4-37
Version 3 Rev 1
Memory Points
4-38
2010 Motorola, Inc.
Lesson 5: Network Acquisition and Call Process
Version 3 Rev 1
Chapter 5

In this lesson we will look at how a UE gains access to and makes a call on an LTE network. We will discuss the UE attach and registration procedures. We will then take a look at a UE initiated call, a typical handover, and a UE detach.
2010 Motorola, Inc.
5-1
Version 3 Rev 1
5-2
2010 Motorola, Inc.
Objectives
Version 3 Rev 1
Objectives
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
2010 Motorola, Inc.
5-3
Version 3 Rev 1
Basic Procedures
Basic Procedures
Figure 5-1 Basic Procedures
There are ve (5) basic procedures that we are going to discuss: Attach Service Request Tracking Area Update (TAU) Handover Detach Before we discuss the procedures, we need to discuss a few concepts that will be used throughout this lesson.
5-4
2010 Motorola, Inc.
Radio Resource Control (RRC) States
Version 3 Rev 1

Lets look at the UEs RRC states. Before the UE can do anything, a RRC connection must be established between the UE and E-UTRAN. Figure 5-2 RRC and MM States
Radio Resource Control (RRC) Idle

The UE is considered RRC_IDLE once it obtains the center frequency, reads the timing information, syncs to the eNodeB, and is ready to receive system broadcast information. At this point the UE has no signaling connection to the eNodeB. From the RRC_IDLE state the UE must perform: System acquisition Receive and respond to paging Tracking Area Update Cell re-selection as needed
Radio Resource Control (RRC) Connect

In order to register with the EPC, the UE must set-up RRC signaling with the eNodeB. This is the RRC_CONNECT state. From the RRC_CONNECT state the UE must perform: System acquisition Monitor DL control channels Send Channel Quality Information (CQI) as directed by the eNodeB Handover 3GPP TS 36.331 RRC Protocol Specication
Telecoms
LTE
300
2010 Motorola, Inc.
5-5
Version 3 Rev 1

Radio Resource Control (RRC) Connection
Figure 5-3 RRC Connection
RRC Connection is a logical connection between E-UTRAN and UE used to carry all UE-to-eNodeB or UE-to-MME (NAS) signaling, UE location tracking, UE state tracking, and establish a temporary identity for the UE (C-RNTI). After the RRC connection is set up the UE is known to the eNodeB, and the UE is in RRC_CONNECT state.
5-6
2010 Motorola, Inc.
EPS Mobility Management (EMM) States
Version 3 Rev 1
EPS Mobility Management (EMM) States

Figure 5-4 EPS Mobility Management States
EPS Mobility Management (EMM) Deregistered

In the EMM_DEREGISTERED state, the MME is not aware of the UE. It has no valid location or routing information for the UE.
EPS Mobility Management (EMM) Registered

The UE enters the EMM_REGISTERED state by a successful registration with an Attach procedure. In the EMM_REGISTERED state, the UE can receive services that require registration in the EPS. 3GPP TS 23.401 GPRS Enhancements for E-UTRAN Access
Telecoms
LTE
300
2010 Motorola, Inc.
5-7
Version 3 Rev 1
EPS Connection Management (ECM) States
EPS Connection Management (ECM) States

Figure 5-5 EPS Connection Management States
EPS Connection Management (ECM) Idle

A UE is in ECM_IDLE state when no NAS signaling connection exists between the UE and MME. In ECM_IDLE state, a UE performs cell selection/reselection. The UE location is known in the MME with an accuracy of a Tracking Area (TA).
EPS Connection Management (ECM) Connect

In the ECM_CONNECT state, a (NAS) signaling connection exists between the UE and the MME. The UE location is known in the MME with an accuracy of a serving eNodeB ID. UE mobility is handled by the handover procedure. 3GPP TS 23.401 GPRS Enhancements for E-UTRAN Access
Telecoms
LTE
5-8
300
2010 Motorola, Inc.
EPS Session Management (ESM)
Version 3 Rev 1
EPS Session Management (ESM)

Figure 5-6 EPS Session Management (ESM)
The LTE standards also describe the EPS Session Management states: ESM_ACTIVE.
ESM_INACTIVE and
ESM_INACTIVE
In this state, the UE has no default or dedicated bearers associated with it.
ESM_ACTIVE
In this state, the UE has at least one bearer associated with it. Since the UE must be registered before establishing a bearer, a UE in ESM_ACTIVE state will also be in EMM_REGISTERED state. Data transfer may occur if the UE is in ECM_CONNECT state. 3GPP TS 23.401 GPRS Enhancements for E-UTRAN Access
Telecoms
LTE
300
2010 Motorola, Inc.
5-9
Version 3 Rev 1
Non Access Stratum (NAS) States
Non Access Stratum (NAS) States

The Non Access Stratum (NAS) state model combines EPS Mobility Management (EMM) states, EPS Connection Management (ECM) states and EPS State Management (ESM) states as shown in the table below. Figure 5-7 NAS States
Registraon Service Request TA update, paging, etc.
EMM-Deregistered, ECM-Idle and ESMInacve

RRC: Null No RRC or EPC Context
Power On
EMM-Registered, ECM-Idle and ESMAcve

RRC: IDLE EPC Context S-TMSI, TA-ID, IP Address UE Known at TA Level TA Update DRX on DL
Inacvity Deregistraon
EMM-Registered, ECM-Connected and ESM-Acve

RRC: CONNECTED RRC & EPC Context S-TMSI, TA-ID, IP Address UE Known at Cell Level Handovers UL/DL Data Transfer
IMSI Idener UE Unknown PLMN Selecon No Data Transfer

Periodic TA update Timeout out of area
EMM_DEREGISTERED, ECM_IDLE and ESM_INACTIVE

In this state, the UE is not known by the network. The UE will use the Attach Procedure to become registered (known) by the network. A registration process moves a UE from this state to EMM_REGISTERED, ECM_CONNECT and ESM_ACTIVE.
EMM_REGISTERED, ECM_IDLE and ESM_ACTIVE

In this state, the UE has registered with the network. Its location in the network is known to Tracking Area (TA) level. An IP Address will also have been issued to the UE. The UE will also be able to perform cell reselections. An Tracking Area Update (TAU) timeout moves a UE from this state to EMM_DEREGISTERED, ECM_IDLE and ESM_INACTIVE. A deregistration process moves a UE from this state to EMM_DEREGISTERED, ECM_IDLE and ESM_INACTIVE.
EMM_REGISTERED, ECM_CONNECT and ESM_ACTIVE

In this state, the UE is able to send and receive data. Its location is known to the serving eNodeB ID. The mobility of UE is handled by the handover procedure. An inactivity timeout moves a UE from this state to EMM_REGISTERED, ECM_IDLE and ESM_ACTIVE. A deregistration process moves a UE from this state to EMM_DEREGISTERED, ECM_IDLE and ESM_INACTIVE.
5-10
2010 Motorola, Inc.
Selected EPS IDs
Version 3 Rev 1
Selected EPS IDs

MME IDs
Public Land Mobile Network (PLMN) Identity Identies the mobile network carrier. The PLMN ID consists of the Mobile Country Code (MCC) and the Mobile Network Code (MNC). MME Group Identity (MMEGI) Identies the MME group in a PLMN. MME Code (MMEC) Uniquely identies the MME in a group. Globally Unique MME Identity (GUMMEI) Uniquely identies a specic MME in a PLMN. The GUMMEI consists of the MCC + MNC +MMEGI +MMEC.
2010 Motorola, Inc.
5-11
Version 3 Rev 1
Selected EPS IDs
Selected EPS IDs

UE IDs
Figure 5-9 UE Identities
International Mobile Subscriber ID (IMSI) Uniquely identies the subscriber within a mobile network. The IMSI is assigned by the home mobile network and stored in the SIM/USIM. International Mobile Equipment ID (IMEI) Uniquely identies the subscriber equipment type. The IMEI is stored in the device. Cell Radio Network Temporary ID (C-RNTI) A temporary ID used by the eNodeB for scheduling resources. The C-RNTI is assigned by the eNodeB. The C-RNTI is used by the eNodeB for scheduling resources on the DL or UL. MME Temporary Mobile Subscriber ID (M-TMSI) A temporary ID used to identify the UE within the MME. The M-TMSI is assigned by the MME. The M-TMSI, GUTI, and S-TMSI are used by the MME to identify a UE for paging or control procedures. Globally Unique Temporary UE ID (GUTI) Uniquely identies the UE within the PLMN. The GUTI consists of the GUMMEI and the M-TMSI. SAE Temporary Mobile Subscriber ID (S-TMSI) A smaller version of the GUTI used for paging the UE. The S-TMSI consists of the MMEC plus the M-TMSI.
5-12
2010 Motorola, Inc.
Selected EPS IDs
Version 3 Rev 1
Selected EPS IDs

International Mobile Subscriber Identier (IMSI) Structure
Figure 5-10 IMSI Structure
An LTE carrier uses the International Mobile Subscriber Identier (IMSI) to uniquely identify individual subscribers. The IMSI consists of a country code, mobile network code, and a subscriber identication number. The IMSI is stored in the LTE mobile device SIM/USIM, and signaled to the network during the initial attach process. After the subscriber attaches to a network, LTE network elements refer to the subscriber with temporary identiers such as C-RNTI or S-TMSI.
2010 Motorola, Inc.
5-13
Version 3 Rev 1
Attaching to the Network

Figure 5-11 Attaching to the Network
In order to send and receive data, the UE has to attach to both the E-UTRAN and the EPC. Attaching to the E-UTRAN synchronizes the UE to the eNodeB allowing the UE to receive system broadcast information to continue with the network attachment process. Attaching to the EPC provides the UE with an IP address, sets-up QoS, and establishes bearer service. Here is a simplied view of the Network Attach process we will be discussing in this lesson. Attach synchronizes UE to eNodeB and allows the UE to receive system broadcast information to continue with the network attachment process. Authenticate UE is authenticated on the system. MME Registration UE is assigned to and registered on an MME. P-GW Select a P-GW is assigned. An IP address for the UE is also assigned during this step. MME / S-GW Accept the MME and S-GW accept the QoS parameters, bearers, and other system information that was negotiated during the attach process and passes this information to the UE. UE ACK Network Attach UE acknowledges the MME / S-GW accept and attaches to the LTE Network.
eNodeB Acquisition
Figure 5-12 eNodeB Acquisition
5-14
2010 Motorola, Inc.
Version 3 Rev 1

When the UE powers-up, it looks for and acquires the RF center frequency. Once it obtains the center frequency, it reads the timing information and syncs to the eNodeB. With the UE synchronized to the eNodeB, it may receive system broadcast information. The UE is now considered in the RRC_IDLE state.
System Information (SI)

Figure 5-13 System Information (SI)
System information is broadcast in System Information (SI) Radio Resource Control (RRC) messages. The Master Information Block (MIB) is transmitted on the PBCH and contains the DL system bandwidth. After reading this information in the PBCH, a UE is able to read messages spread across the total number of occupied subcarriers. System Information Block Type 1 (SIB Type 1) is transmitted on the PDSCH and contains the PLMN ID, cell ID, Tracking Area ID, and the scheduling for other SIB types. From the information received in System Information messages, the UE again searches the frequency bands to try to nd a suitable cell. A suitable cell is one that meets cell selection criteria and is not barred or reserved. Once it nds an acceptable cell, it camps on the cell and continues with EPC attach procedure.
Telecoms
LTE
SIB2 messages carry common and shared channel information SIB3-SIB8 messages carry cell reselection parameters for EUTRAN and other Radio Access Technology (RAT) neighbors SIB 10-11 carry emergency information
3GPP TS 36.331 RRC Protocol Specication

300
2010 Motorola, Inc.
5-15
Version 3 Rev 1

Initial Cell Selection
Figure 5-14 Initial Cell Selection
LTE uses the following cell selection procedures. 1. 2. Initial Cell Selection requires no knowledge of which RF channels are E-UTRA carriers. The UE scans all RF channels in the E-UTRA bands to nd the strongest suitable cell. Once a suitable cell is found this cell is selected. Stored Information Cell Selection requires stored information of carrier frequencies and (optionally) cell parameters from previously received measurement control information or from previously detected cells. If no suitable cell is found based on stored information, the Initial Cell Selection procedure is started.
Cell Service Types Cells are categorized according to which services they offer. Acceptable Cell a cell on which the UE may camp-on to obtain limited service (originate emergency calls) Suitable Cell a cell on which the UE may camp-on to obtain normal service Barred and Reserved Cells available for operator access only. Cell barring (reserved) status is signaled in SIB1 messages.
Network Attach
A UE needs to register with the network to receive services that require registration. This registration is called Network Attach. The always-on IP connectivity for the UE of the EPS is enabled by establishing a default EPS bearer during the Network Attach. Network Attach Simplied Procedure This simplied procedure is described in the steps and associated Figure following.
5-16
2010 Motorola, Inc.
Version 3 Rev 1

1. 2. The UE performs the RRC Connection Establishment procedure as described previously. During the RRC Connection Establishment procedure the UE initiates the Network Attach procedure by the transmission, the eNodeB of an Attach Request. This message contains parameters to identify the UE (e.g. IMSI) and the UEs capabilities (e.g. Core Network (CN) capabilities). Assuming no UE context for the UE exists anywhere in the network, or security checks for the UE fail, then authentication and NAS security setup procedures take place. The default bearer is created between the P-GW and eNodeB by identifying GTP TEIDs and IP addresses for all network elements. If dynamic Policy Charging Control (PCC) is deployed the P-GW performs an IP-CAN session establishment with the Policy Charging Rules Function (PCRF). The RRC Connection Recongure message contains the EPS radio bearer id together with the radio layer context. The Attach Accept is actually embedded in the S1AP message from the MME to eNodeB (part of step 4) and the RRC Connection Recongure (part of step 5). The Attach Accept contains the Tracking Area Identity (TAI) and GUTI, hence it can derive the S-TMSI. The UE will also be given the PDN user IP and UL TFT and Access Point Name (APN) At this stage downlink data maybe transferred and buffered at the S-GW. The Attach Complete is embedded in a Direct Transfer message to the eNodeB and an Uplink NAS Transport message to the MME. The Attach Complete message contains the EPS Bearer Id, NAS Sequence Number etc. After the UE has obtained a PDN address, the UE can send uplink packets towards the eNodeB which is then tunnelled to the S-GW and P-GW. Upon reception of the Attach Complete the MME sends a Modify Bearer Request containing the EPS Bearer Id, eNodeB address and TEID to the S-GW. The S-GW responds with a Modify Bearer Response and the S-GW can send its buffered downlink packets.
3. 4.
5. 6.
7.
8.
Figure 5-15
2010 Motorola, Inc.
5-17
Version 3 Rev 1
Quality of Service (QoS) / EPS Bearer

Figure 5-16 Quality of Service (QoS) / EPS Bearer
Quality of Service (QoS) parameters cannot be applied separately from the data ows to which they relate to. Because of this, the EPS Bearer has been added to the LTE standard. The EPS bearer is a logical connection between the UE and the P-GW. One EPS bearer is established when the UE connects to a PDN, and that remains established throughout the lifetime of the PDN connection to provide the UE with always-on IP connectivity to that PDN. That bearer is referred to as the default bearer. Any additional EPS bearer that is established to the same PDN is referred to as a dedicated bearer. The initial bearer level QoS parameter values of the default bearer are assigned by the network, based on subscription data. The decision to establish or modify a dedicated bearer can only be taken by the EPC, and the bearer level QoS parameter values are always assigned by the EPC. An EPS bearer is comprised of the following elements: S5/S8 Bearer a tunnel which transports packets between the S-GW and P-GW S1 Bearer a tunnel which transports packets between the S-GW and eNodeB Radio Bearer established by an RLC connection between the eNodeB and the UE (one RLC per Radio Bearer)
5-18
2010 Motorola, Inc.
Version 3 Rev 1

Bearer Service Architecture
Figure 5-17 Bearer Service Architecture
The data ows being transported by the EPS bearer are known as Service Data Flow(s) (SDF). Each of them identies both termination points Terminal Endpoint Identier (TEID) as well as the service being used. An SDF could be a connection to a web server, streaming video server, etc. An UL Trafc Flow Template (TFT) in the UE binds an SDF to an EPS bearer in the uplink direction. Multiple SDFs can be multiplexed onto the same EPS bearer by including multiple uplink packet lters in the UL TFT. A DL TFT in the P-GW binds an SDF to an EPS bearer in the downlink direction. Multiple SDFs can be multiplexed onto the same EPS bearer by including multiple downlink packet lters in the DL TFT. A Radio Bearer transports the packets of an EPS bearer between a UE and an eNodeB. There is a one-to-one mapping between an EPS bearer and a Radio Bearer. An S1 bearer transports the packets of an EPS bearer between an eNodeB and a S-GW. An S5/S8 bearer transports the packets of an EPS bearer between an S-GW and a P-GW. A UE stores a mapping between an uplink packet lter and a Radio Bearer to create the binding between an SDF and a Radio Bearer in the uplink. A P-GW stores a mapping between a downlink packet lter and an S5/S8 bearer to create the binding between an SDF and an S5/S8 bearer in the downlink. An eNodeB stores a one-to-one mapping between a radio bearer and an S1 to create the binding between a Radio Bearer and an S1 bearer in both the uplink and downlink. An S-GW stores a one-to-one mapping between an S1 bearer and an S5/S8 bearer to create the binding between an S1 bearer and an S5/S8 bearer in both the uplink and downlink.
2010 Motorola, Inc.
5-19
Version 3 Rev 1

QoS Parameters
Figure 5-18 QoS Parameters
The bearer level (i.e. per bearer or per bearer aggregate) QoS parameters are QoS Class Identier (QCI), Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR), and Aggregate Maximum Bit Rate (AMBR). Each EPS bearer is associated with the following bearer level QoS parameters: QoS Class Identier (QCI) used as a reference to access node-specic parameters that control bearer level packet forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol conguration, etc.), and that have been pre-congured by the operator owning the eNodeB. Allocation and Retention Priority (ARP) the primary purpose of ARP is to decide whether a bearer establishment / modication request can be accepted or needs to be rejected in case of resource limitations. In addition, the ARP can be used by the eNodeB to decide which bearer(s) to drop during exceptional resource limitations (e.g. at handover). Guaranteed Bit Rate (GBR) applicable to bearers which require guaranteed QoS for services such as VoIP and streaming video. Maximum Bit Rate (MBR) maximum amount of bandwidth a GBR ow can use. Aggregate Maximum Bit Rate (AMBR) denotes a bit rate of trafc per group of bearers and applies to only non-guaranteed bit rate bearers. The AMBR limits the overall bit rate of all bearers associated with the limit for a given Packet Data Network.
5-20
2010 Motorola, Inc.
Service Request
Version 3 Rev 1
Service Request
A Service Request sets up or modies an EPS bearer. Each EPS bearer has some or all of the QoS characteristics described on the preceding pages. Three general procedures are available. Create Bearer One or more EPS bearers may be created upon network entry, or as needed Modify Bearer, UE Triggered an existing EPS bearer may be modied based on UE-initiated signaling Modify Bearer, Network Triggered an existing EPS bearer may be modied based on network-initiated signaling (e.g. incoming call)
UE Triggered Service Request Simplied

STEPS 1. 2. 3. 4. 5. 6. 7. 8. The NAS Service Request is sent from the UE to MME. This informs the MME of the identity of the UE (S-TMSI), Tracking Area and Cell. A cause value is also included to indicate to the MME the reason for setting up the call (i.e. Mobile Originating Access). NAS Authentication maybe performed at this stage. The MME sends an S1AP Initial Context Request message to the eNodeB to activate the Radio and EPS Bearers required. The eNodeB performs the RB establishment procedure for the UP, when this is complete the EPS bearers are considered synchronized between the UE and the network. The UL data can now be transferred by the eNodeB to the S-GW by the routes specied in steps 3 and 4. The eNodeB sends an Initial Context Setup Complete message that indicates to the MME which bearers the UE will use. The MME exchanges messaging with the S-GW to notify which bearers shall be used. If there are any non-accepted bearers the MME initiates a bearer release procedure. The S-GW is now able to send DL packets to the UE. UE Service Request
Figure 5-19
2010 Motorola, Inc.
5-21
Version 3 Rev 1
Mobility Procedures
Mobility Procedures
Figure 5-20 Mobility
As a UE moves throughout the network, it is listening to system messages that help determine its location in the network (if it has changed Tracking Areas). Those system messages also have the UE measure and report channel quality. Among other things, the channel quality report sent back to the network can indicate that one of the neighboring cells has a stronger signal than that of the current serving cell, making it a candidate for a handover. Mobility Procedures UE State RRC_IDLE, ECM_IDLE RRC_IDLE, ECM_IDLE RRC_CONNECT, ECM_CONNECT RRC_CONNECT, ECM_CONNECT Mobility Procedure Tracking Area Update (TAU) TAU with MME/S-GW Change eNodeB Handover Handover with MME/S-GW Change Handover to GSM/UMTS, cdma2000
5-22
2010 Motorola, Inc.
Mobility Procedures
Version 3 Rev 1
Mobility Procedures
Tracking Area (TA)
Figure 5-21 Tracking Areas
A Tracking Area (TA) is a dened group of cells which can be used by the MME to page idle UEs. Within a Tracking Area, a UE is associated with a single MME and S-GW. As it moves to a new Tracking Area, an idle UE must announce its new location to the serving MME. That process is called a Tracking Area Update (TAU). A Tracking Area ID (TAI) uniquely identies the MME tracking area for paging and location updates. The TAI consists of the Mobile Country Code (MCC), Mobile Network Code (MNC), and Tracking Area Code (TAC). Instead of using a single Tracking Area, the MME may supply a Tracking Area List to reduce the location update signaling from the UE. As long as the UE is located in any of the listed Tracking Areas, a TAU is not necessary.
MME and S-GW Pools

Figure 5-22 Network Element Pooling
2010 Motorola, Inc.
5-23
Version 3 Rev 1
Mobility Procedures
Mobility Procedures
The EPC supports MME and S-GW pools for improved mobility, geographical redundancy, and load balancing. A pool is a set of MMEs or S-GWs that serve a set of Tracking Areas. A pool area is dened as an area where a UE may be served without needing to change the serving network element. Each cell is associated with a pool of MMEs and a pool of S-GWs. After an eNodeB selects an MME for a UE, the selected MME will select an S-GW within the S-GW Pool supported by the cell. There is no distinct relationship between S-GW Pools and MME Pools. However the following must be considered when the Pools are dened: S-GW Pools are not tied to MME Pools S-GW Service Areas can be a subset or a super-set of MME Pool Areas S-GW Service Areas can overlap MME Pool Areas MME Pool Areas can overlap S-GW Service Areas
Tracking Area Update (TAU)

When the UE moves between different TAI it will have to perform a Tracking Area Update (TAU) procedure. The UE detects a change to a new TA by discovering that its current TAI is not in the list of TAIs that the UE registered with the network, or the UE reselects an E-UTRAN cell and is not registered, or updated with the MME (e.g. periodic TAU timer expired while camping on GERAN or UTRAN), or the UE was in PMM_Connected state (e.g. URA_PCH) when it reselects an E UTRAN cell. There are four different types of TAU currently dened in 3GPP 23.401 (v8.6.0): TAU procedure with S-GW change TAU procedure without S-GW change Routing Area Update (RAU) with MME interaction and without SGW change (2G/3G to LTE) RAU with MME interaction and with SGW change (2G/3G to LTE)
In this course we shall only concentrate on the TAU procedure without S-GW change. TAU Procedure without S-GW Change STEPS 1. 2. The trigger to start the TAU procedure has been detected by the UE. The UE initiates the TAU procedure by sending the eNodeB a TAU request. This contains the UEs CN capabilities, EPS bearer status, identity, security information, old GUTI, TAI and selected network. The eNodeB forwards the TAU request together with the TAI and EGCI of the cell where it received the message to the new MME. The new MME can derive the old MME (or SGSN) from the old GUTI received and sends a context request to retrieve the user information including the EPS bearer contexts for the UE. The new MME may be able to maintain authentication for the UE so the authentication/security procedures listed in step 4 might not be necessary. If the integrity check in step was to fail, then the authentication procedure is mandatory. If security is enabled in the network then ciphering procedures will be used. The new MME adopts the bearer contexts received from the old MME/SGSN as the UEs EPS bearer contexts to be maintained by the new MME. The new MME veries the EPS bearer status received from the UE with the EPS bearer contexts it maintains and releases any network resources not actively used by the UE. To do this a Modify Bearer request/Response procedure is used between the MME and S-GW. If the RAT type has changed the P-GW will be informed for charging purposes, also if PCC is deployed the PCRF will be used If the new MME doesn't hold any subscription data regarding this UE, this will have to be retrieved from the HSS. The HSS cancels the subscription data from the old MME. The new MME responds to the UE with a TAU Accept giving the UE the new GUTI, TAI lists, EPS bearer status etc. When the GUTI has changed the UE will respond with a TAU complete.
3.
4. 5.
6. 7. 8.
5-24
2010 Motorola, Inc.
Mobility Procedures
Version 3 Rev 1
Mobility Procedures
Figure 5-23 Tracking Area Update
X2 Handover
These procedures are used to handover a UE from a source eNodeB to a target eNodeB using the X2 reference point. In these procedures the MME is unchanged. Two procedures are dened depending on whether the S-GW unchanged or is relocated: X2based handover without S-GW relocation X2based handover with S-GW relocation.
In this course we will discuss the simplied 'X2based handover without S-GW relocation' procedure. In the beginning of the description the UE has an ongoing data call. STEP 1. During the initial data call setup the UE would be sent via RRC signalling a Measurement Control message. This contains the handover parameters needed to enable the UE to inform the eNodeB that it has detected that it needs to do a handover. When the UE detects the need for a handover it sends a RRC Measurement Report to the source eNodeB containing the cause value and a list of neighbor cells ranked by signal strength or quality. The source eNodeB makes a decision based on the RRC Measurement Report and other factors such as the target eNodeB loading or type, to decide which neighbor cell the handover should be directed to. An X2AP Handover Request is sent to the target eNodeB. This identies the target cell id, the EPS bearers that need to be established and the physical cell id of source cell. At this stage the target eNodeB can make a decision on whether it can except this incoming handover or not, based on its available capacity. If the incoming handover can be excepted the target eNodeB will respond with a X2AP Handover Request Acknowledge message to the source eNodeB. This contains a new C-RNTI, security and access parameters. This message gives the source eNodeB the parameters it needs to build the handover message. The handover command is embedded in the RRC Connection Reconguration message. This contains the parameters needed (sent by the target eNodeB) by the UE to perform the handover. Any EPS bearers not identied will be removed by the UE. The source eNodeB sends an X2AP SN Status Transfer message to the target eNodeB to convey the UL/DL PDCP SN status of the SAE bearers. Data can now be forwarded and buffered to the target eNodeB.
2. 3.
4. 5. 6.
2010 Motorola, Inc.
5-25
Version 3 Rev 1
Mobility Procedures
Mobility Procedures
7. 8. 9. Using the RRC procedures the UE will synchronize to the target eNodeB, during this procedure the UE obtains its new timing advance etc. At the end of the synchronization phase the UE will send the RRC Connection Reconguration Complete message to the target eNodeB to conrm the successful completion of an RRC Connection Reconguration. When the UE has arrived at the target eNodeB, downlink data forwarding by the source eNodeB can be delivered to it. Figure 5-24 X2 Handover 1
10. 11. 12. 13. 14. 15.
16.
STEP Uplink data from the UE can be delivered via the S-GW to the P-GW as the UL GTP TEID parameters have been sent in step 3. The target eNodeB sends a Path Switch request message to the MME, this includes the new cell EGCI and TAI of the target cell, also the list of EPS bearers (if any). In this case the MME will determine that the S-GW can continue to serve the UE. The MME sends a Modify Bearer request containing the eNodeB address and TEIDs for the DL UP for all the accepted EPS bearers to the S-GW. The MME will release any non-accepted EPS bearers. Once a Modify Bearer response is sent back to the MME the S-GW starts sending packets to the target eNodeB using the newly received address and TEIDs. In order to assist the reordering function in the eNodeB, the S-GW sends one of more end marker packets on the old path immediately after switching the path. The MME conrms the Path Switch Request message with the Path Switch Acknowledge. Any bearers which have changed will be indicated to the eNodeB. STEP The Release Resource message indicates the success of the handover and informs the source eNodeB to release resources.
5-26
2010 Motorola, Inc.
Mobility Procedures
Version 3 Rev 1
Mobility Procedures
17. If the UE has moved to a cell in another Tracking Area (TA) then a TAU procedure will be performed. Figure 5-25 X2 Handover 2
2010 Motorola, Inc.
5-27
Version 3 Rev 1
UE Triggered Detach (UE Switched Off)

This procedure describes the case where the UE camps on the E-UTRAN and a Detach Request is sent to the MME when the UE switches off. STEP 1. The UE sends the NAS message Detach request containing the GUTI and Switch Off indication to the MME. This NAS message is used to trigger the establishment of the S1 connection if the UE was in ECM-IDLE mode. Switch Off indicates whether Detach is due to a switch off situation or not. The eNodeB forwards this message to the MME along with the TAI and EGCI of the cell where the UE is camped. The active EPS Bearers in the S-GW are deactivated by the MME sending a Delete Session Request to the S-GW. When the S-GW receives the Delete Session Request message from the MME it releases the related EPS Bearer Context information and sends a Delete Session Request to the P-GW. If the P-GW employs PCEF initiated IP-CAN Session Termination procedure, then the PCRF will be told that the EPS Bearers are to be released. The P-GW acknowledges with Delete Bearer Response. The S-GW sends Delete Bearer Request. The MME releases the S1MME signaling connection for the UE by sending a S1 Release Command to the eNodeB with a cause value set to detach. UE Triggered Detach
2.
3.
Figure 5-26
5-28
2010 Motorola, Inc.
Version 3 Rev 1
2010 Motorola, Inc.
5-29
Version 3 Rev 1
Security in LTE
Security in LTE
Figure 5-27 Security in LTE
Lets take a brief look at the user security methods employed in LTE. User data and RRC signaling between the UE and the eNodeB is protected by ciphering and integrity methods. The security keys used are forwarded to the eNodeB by the MME to the eNodeB after the Universal Subscriber Identity Module (USIM) and the MME have been authenticated. NAS signaling is also cipher and integrity protected between the UE and MME using separate keys. There are three types of security protections employed within the EPS: Ciphering protects data from being overheard. This applies to user data as well as signaling messages. Integrity ensures that the receiving network element is able to verify that the signaling data has not been modied since it was transmitted by the sending network element. Mutual Authentication conrms the UEs identity to the network, and the networks identity to the UE.
LTE Security Keys

Figure 5-28 LTE Security Keys
5-30
2010 Motorola, Inc.
Security in LTE
Version 3 Rev 1
Security in LTE
The 3GPP LTE standard introduces new security keys to ensure the correct protection is applied for the different information ows. K secret key permanently stored in the USIM and the HSS. CK, IK Ciphering Key and Integrity Key computed in the UE and HSS. KASME (Access Security Management Entity) derived by the UE and HSS from CK and IK during the Authentication process. KASME is responsible for establishing and maintaining security associations with UEs based on keys received from the HSS. In LTE, the ASME function is provided by the MME. KeNB derived by UE and MME from KASME and is used by the eNodeB to derive the keys for RRC and User Plane trafc. Using those keys, the other keys are produced to ensure integrity and privacy of: NAS signaling between the UE and MME AS (Access Stratum) signaling between the UE and eNodeB User Plane data between UE and S-GW.
Function of LTE Security Keys

Figure 5-29 Function of LTE Security Keys
The function of each security key is depicted in the diagram above.
Authentication and Key Agreement Process (AKA)

LTE and UMTS use the same Authentication and Key Agreement Process (AKA) process. The AKA procedure uses the following keys: RAND Random Challenge parameter used to generate the other four parameters in the vector (XRES, AUTN, CK, IK below) XRES Expected Result used by the network to Universal Subscriber Identity Module (USIM) authentication AUTN Authentication Token used by the USIM for network authentication CK Ciphering Key IK Integrity Key KASME Key Access Security Management Entity KSIASME Key Set Identier Access Security Management Entity
2010 Motorola, Inc.
5-31
Version 3 Rev 1
Security in LTE
Security in LTE
Figure 5-30 AKA
The diagram above illustrates AKA Procedure. Step 1 2 3 4 Connection or service request by the UE. The UE identies itself with the IMSI. This is typically done at power-on. MME requests authentication information for that IMSI from HSS. HSS sends MME one (1) to ve (5) authentication vectors each containing RAND, AUTH, XRES and KASME. The MME chooses one of the ve vectors and sends the UE a USER AUTHENTICATION REQUEST using the RAND, AUTN and KSIASME. Using the RAND and its stored K secret key, the UE authenticates the network by verifying the AUTN. The UE then generates the RES and sends a USER AUTHENTICATION RESPONSE to MME. MME authenticates the UE by comparing the RES sent by the UE and the XRES. The CK and IK are computed in the UE the same way that they are computed in the HSS. This way, they never have to be sent over the air interface.
6a 6b
5-32
2010 Motorola, Inc.
Lesson 5 Summary
Version 3 Rev 1
Lesson 5 Summary
In this lesson you learned: How the UE attaches to the E-UTRAN and EPC How the UE attaches, authenticates, and registers on the LTE Network The different RRC and Mobility Management States How the UE acquires and selects an eNodeB The Initial Attach, UE Service Request, Network Triggered Service Request, UE Triggered Detach, Tracking Area Update, and Handover call processes
2010 Motorola, Inc.
5-33
Version 3 Rev 1
Memory Points
Memory Points
5-34
2010 Motorola, Inc.

LTE100-Motorola LTE Training

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE100-Motorola LTE Training

Uploaded by

Copyright:

Available Formats

LTE100: Introduction to Long Term Evolution

2010 Motorola, Inc.

2010 Motorola, Inc.

Chapter 2: Lesson 2: LTE Network Architecture

2010 Motorola, Inc.

LTE100: Introduction to Long Term Evolution

2-24 2-24 2-25 2-26 2-27

Chapter 3: Lesson 3: LTE Air Interface

2010 Motorola, Inc.

LTE100: Introduction to Long Term Evolution

Lesson 3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4: Lesson 4: LTE and EPC Protocol Overview

Chapter 5: Lesson 5: Network Acquisition and Call Process

2010 Motorola, Inc.

LTE100: Introduction to Long Term Evolution

2010 Motorola, Inc.

About This Manual

LTE100: Introduction to Long Term Evolution

2010 Motorola, Inc.

This page intentionally left blank.

2010 Motorola, Inc.

Lesson 1: What is Long Term Evolution (LTE)?

Lesson 1: What is Long Term Evolution (LTE)?

2010 Motorola, Inc.

Lesson 1: What is Long Term Evolution (LTE)?

This page intentionally left blank.

2010 Motorola, Inc.

Conventions Used in this Guide

Purpose of the Participant Guide

2010 Motorola, Inc.

2010 Motorola, Inc.

2010 Motorola, Inc.

2010 Motorola, Inc.

This page intentionally left blank.

2010 Motorola, Inc.

2010 Motorola, Inc.

Drivers for Long Term Evolution (LTE)

Drivers for Long Term Evolution (LTE)

2010 Motorola, Inc.

3rd Generation Partnership Project (3GPP)

3rd Generation Partnership Project (3GPP)

GSM GPRS/EDGE UMTS HSDPA HSUPA HSPA+ IMS MBMS LTE

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution

2010 Motorola, Inc.

GSM Network Evolution

GSM Network Evolution