Академический Документы
Профессиональный Документы
Культура Документы
1G: When the first cellular systems launched, even though data
wasn't offered by the carriers, a few hardy users provided their own
(MNP10) modems for haphazard, slow data via dialup access
• The internet wasn't a big factor yet!
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
2G provided digital data but at low bit rates -- 9600 - 32k bps
• Downloading a 2MB file took an hour or more (if it didn't drop in
the middle and require manually re-starting)
• Travel agents with telephones were still faster than online res.
October, 2011 Course 512 v1.0 (c)2011 Scott Baxter Page 6
Wireless Generations and Sector Data Speeds
153˅ 200+˅
153˄ 200+˄
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
3.1M˅
1.8M˄ 7M+˅
153˅ 200+˅
3M+˄
153˄ 200+˄
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
4G WiMAX LTE
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
VOIP?
7M+˅
VOIP
VOIP
1.8M˄
153˅ 200+˅
3M+˄
153˄ 200+˄
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
Finally the industry will settle on one or two VOIP standards for
LTE, voice traffic of legacy CDMA and GSM will finally go to LTE
Nearly all WiMax networks will finally convert to LTE
CDMA and LTE voice networks won't die until 2017 or even later!
October, 2011 Course 512 v1.0 (c)2011 Scott Baxter Page 11
Wireless Generations and Sector Data Speeds
1000M˅
100M˅ 100M˅ 500M˄
50M˄ 50M˄
44M˅
22M˄
HSPA+
3.1M˅
VOIP?
7M+˅
VOIP
VOIP
1.8M˄
153˅ 200+˅
3M+˄
153˄ 200+˄
2G CDMA IS-95, J-Std 008 TDMA: NADC, IS-136 TDMA: GSM, HSCSD TDMA: IDEN
1G: Users provided their own modems for haphazard, slow data
2G provided digital data but at low bit rates -- 9600 - 32k bps
3G data users finally passed 1 Mb/s in EV-DO and HSPA
4G users finally get10 Mb/s+
Page 12 Course 512 v1.0 (c)2013 Scott Baxter October, 2013
LTE Design Objectives
Power
• The signal consists of many (from dozens to
Frequency
thousands) of thin carriers carrying symbols
• In OFDMA, the symbols are for multiple users
• OFDM provides dense spectral efficiency and robust
resistance to fading, with great flexibility of use
Multiple-Antenna Techniques to Multiply Radio Throughput
MIMO MIMO
• Multiple Input Multiple Output
• An ideal companion to OFDM, MIMO allows
exploitation of multiple antennas at the base station
and the mobile to effectively multiply the throughput
for the base station and users
SMART ANTENNAS
• Beam forming for C/I improvement and
interference reduction
Page 17 Course 512 v1.0 (c)2013 Scott Baxter October, 2013
Summary of Major Progress
in Wireless Communications
Cellular Frequency Reuse Concept
From No Frequency Reuse
with handoffs
Progress in
Network Configuration
to
and Frequency Reuse
B D
A C
1xRTT RC4
1xEV-DO
Analog*
Signal
CDMA
GPRS
EDGE
GSM
UMTS HSPA LTE
Technology
Signal Bandwidth, MHz = 0.03 0.03 0.2 0.2 0.2 1.2 1.2 1.2 3.84 3.84 20
User Bits/Second = 9600* 28k 104k 160k 384k 360k 720k 3.1M 2M 8M 100M
Signal Efficiency bits/Hz = 0.3* 0.9 0.5 0.8 1.9 0.3 0.6 2.4 0.5 2.1 5.5
Frequency Reuse N = 7 7 3 3 3 1 1 1 1 1 ~3
MIMO factor = 1 1 1 1 1 1 1 1 1 1 4
Spectral Efficiency bits/Hz/Area = 0.04 0.13 0.17 0.27 0.63 0.3 0.6 2.4 0.5 2.1 7.3
Progress in
Devices
Frequency
Uplink
In TDD, uplink and downlink take turns transmitting in a single block
of spectrum.
Operators’ choice of FDD or TDD operation is usually dictated by the
frequencies assigned by government
In FDD, the capacity of uplink and downlink is determined by the
spectrum allocated to each (usually equal)
In TDD, the relative capacity of uplink and downlink can be adjusted
to most closely match the actual distribution of uplink and downlink
traffic, getting greatest efficiency from available spectrum
The WiMAX standard was first developed in only a TDD version
The LTE technology was first developed in only an FDD version
Today both LTE and WiMAX have FDD and TDD versions
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 22
Orthogonal Frequency Division
Multiple Access - OFDMA
Uplink Downlink
Uplink spectrum is empty Downlink spectrum on active system
if no UEs are transmitting usually appears fully occupied
706 716 730 740
1.4, 3, 5, 10, 15 or 20 MHz. 1.4, 3, 5, 10, 15 or 20 MHz.
CELL UPLINK
CELL DNLNK
Proposed AWS-2
PCS AWS
AWS?
AWS PCS Down-
SAT
SAT
IDEN
IDEN
700 MHz. Down-
Uplink Uplink Link
Link
700 MHz 800 900 1700 1800 1900 2000 2100 2200
Frequency, MegaHertz
Modern wireless began in the 800 MHz. range, when the US FCC
reallocated UHF TV channels 70-83 for wireless use and AT&T’s
proposed analog technology “AMPS” was chosen.
Nextel bought many existing 800 MHz. Enhanced Specialized Mobile
Radio (ESMR) systems and converted to Motorola’s “IDEN” technology
The FCC allocated 1900 MHz. spectrum for Personal Communications
Services, “PCS”, auctioning the frequencies for over $20 billion
With the end of Analog TV broadcasting in 2013, the FCC auctioned
former TV channels 52-69 for wireless use, the “700 MHz.” band
The FCC also auctioned spectrum near 1700 and 2100 MHz. for
Advanced Wireless Services, “AWS”.
Technically speaking, any technology can operate in any band. The
choice of technology is largely a business decision by system operators.
In the U.S., the former television channels 52-69 have been re-allocated
to wireless operators and public safety entities.
The “Upper C” block (striped red) is now used by Verizon Wireless in
virtually the entire U.S. with uplink in 776-787 MHz. and downlink in
746-757 MHz. Verizon’s partnership with rural operators has given it a
head-start in completing LTE service along virtually all interstate
highways and many surrounding rural areas.
AT&T has obtained the lower B and/or lower C block in many areas.
After considerable delay it is now well along in its national rollout.
Other operators also use lower A, B, and/or C blocks in many areas.
There is controversy over adjacency of lower A to TV channel 51.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 25
LTE Band
Classes
Frequency,
KHz
-30 -15 FSC +15 +30
UE
eNB
Radio signals in a mobile environment don’t follow just one direct pathway
from transmitter to receiver. The signal travels over every possible path. The
receiver gets a “jumble” of what was transmitted, “blurred” in time.
On arrival, the boundary between one symbol and the next is “fuzzy”. A
symbol is sometimes interfered with by overlapping remnants of the symbol
sent just before of it. This is called “intersymbol interference”, ISI.
LTE exploits Discrete Fourier Transforms to overcome ISI. Each symbol
begins with a preview of its end value, called a “cyclic prefix”.
If the CP length is longer than the time-blurring of the radio channel, the
Discrete Fourier Transform can eliminate the intersymbol interference.
LTE systems have a “normal” CP length which nicely fits most situations. The
CP length can also be “extended” to get good performance in very reflective
areas such as big cities and mountain canyons, and in Multicast transmission.
The 1.4 MHz. bandwidth is used only for initial addition of LTE to
cleared spectrum of an existing FDD system which is converting
from another technology to LTE FDD.
The 1.6 MHz. bandwidth is used only for initial addition of LTE to
cleared spectrum of an existing TDD system which is converting
from another technology to LTE TDD.
The other bandwidths match frequency blocks authorized by
various countries’ governments for wireless operation.
LTE uses a high spectral efficiency multicarrier multiple access approach, OFDM
• Downlink: OFDMA (Orthogonal Frequency Division Multiple Access)
• Uplink: SC-FDMA (Single Carrier - Frequency Division Multiple Access), also
called DFT (Discrete Fourier Transform) spread OFDMA.
OFDM fills the available bandwidth with many mutually orthogonal narrowband
subcarriers, shared by multiple users.
• OFDMA is spectrum-efficient, but needs fast processors to make and decode
• The OFDMA signal has a high peak-to-average power ratio, needing power-
hungry linear amplifiers. It’s no problem for eNBs, but makes handsets costly.
• A near-cousin to OFDMA, SC-FDMA, is used on the uplink because it has the
same multi-carrier structure but a low peak-to-average power ratio.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 40
MIMO
Multiple Input Multiple Output
Time
Time
Page 47
LTE Channels – Logical, Transport, Physical
User
Traffic
Control
Random
Control Access Random Access
Public
Traffic
Multi- Multi-
MultiMedia
Media Media
Traffic
Control
Shared Paging
October, 2013
Control
Public
Paging Paging
Overhead Broadcast Broadcast
Overhead Overhead
Types of Channels in LTE
Logical Channels
• A logical channel carries a specific traffic or control messaging
between the RLC and an upper-level entity
Transport Channels
• The Transport channels carry information between Medium
Access Control (MAC) and higher layers.
Physical Channels
• A physical channel holds content with bits mapped into the
appropriate format to be transmitted over the air interface
• In addition to physical channels carrying user and control bits,
there are also physical signals
– PSS: downlink Primary Synchronization Signal
– SSS: downlink Secondary Synchronization Signal
– RS: downlink demodulation Reference Signal
– Uplink demodulation Reference Signal
PBCH
The Physical Broadcast Channel carries system
information for UEs needing to access the network.
• It carries only the Master Information Block, MIB.
• The modulation is always QPSK.
• The information bits are coded, rate matched, and then
scrambled using a cell-specific sequence to prevent
confusion with data from other cells
• It’s carried in the central six resource blocks of the LTE
signal (72 subcarriers) regardless of the overall system
bandwidth.
• The PBCH message is repeated every 40 ms, i.e. one
TTI of PBCH includes four radio frames.
• One PBCH transmission contains 14 information bits,
10 spare bits, and 16 CRC bits.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 51
Downlink LTE Physical Channels
PCFICH: The Physical Control Format Indicator Channel
PCFICH symbols
PDCCH symbols
PHICH symbols
Resources in LTE
• Resource Element, Resource Block, Slot, Sub-frame
• Resource Grid
Control Information
• Physical Channels, PDCCH, DCI
Resource Allocation
• Resource Block Group (RBG) based
• RBG Subset based
• Virtual Resource Block (VRB)-based
Interactive LTE downlink signal demonstration:
• http://paul.wad.homepage.dk/LTE/lte_resource_grid.html
cc
For the overall LTE signal structure, both uplink and downlink, a
Physical Resource Block (PRB) is the main allocated “chunk” of
signal.
However, control channels are mapped into smaller units called
Resource Element Groups (REG). Because control channel
information is usually very compact in size, an REG easily fits
inside a PRB.
An REG is just one symbol long, and it takes up either 4 or 6
subcarriers – depending on whether pilot subcarriers are included.
Several REG may be grouped into a Control Channel Element
(CCE).
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 63
The Downlink Reference Signal
DCI +
16 bit CRC
scrambled with RNTI
RB Control EPC
Connection Mobility Ctrl
MME
Radio Admission Ctrl.
NAS Security
eNB Measurement
Config. & Provision
Idle State Mobility
Dynamic Resource Handling
Allocation (scheduler)
EPS Bearer
Control
RRC
PDCP
S-GW P-GW
RLC
Mobility UE IP Address
MAC
Anchoring Allocation
Internet
S1
PHY Packet Filtering
GERAN Gb
Policy and Charging Rules Function
S5b
Home Subscriber Server
S5a
WCDMA /HSPA radio Networks “Super HLR”
Ref Pt.
Mobility Management Entity S6a HSS
User Plane Entity
S1 SGi Operator’s
Evolved MME 3GPP SAE IP Services
RAN: eNB Ref Pt. UPE Anchor Anchor
LTE radio Inter Access System Anchor IASA
Networks
Non-Access Stratum
NAS Core<>UE signaling
NAS
Layer 2
RLC RLC
Logical Channel
UE eNodeB
(user Physical Channel (base
Equipment) station)
Upper layer
SDU
RRC_Connected
• UE is connected to the RAN
• Date can be immediately exchanged between network and UE
• Network know UE location down to the cell level
• The Network will maintain the connection by managing
handovers when necessary
RRC_Idle
• The UE is not connected to the network; there is no traffic
being sent in either direction between UE and RAN
• The network knows the UE is present, and the location area
where it can be paged to deliver an incoming call
• The UE is monitoring the network discontinuously to save radio
resources and its battery; the system knows when it will be
listening for pages and other orders
In-Sequence
Correction
RLC SDUs
RLC PDUs
ARQ Error
Managing
Managing
Delivery
PDCP
MAC Layer
Physical Layer
UU Air Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 100
Intercell Interference Coordination
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 102
Waking Up with a UE:
LTE ‘Call Processing’
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 103
System Acquisition
Searching In Frequency Searching In Time
At power-up, the UE notes its LTE band class capabilities and begins
exploring all the possible center frequencies that might be hold the SCH
The UE first looks for the primary synchronization signal (P-SCH) in the
last OFDM symbol of the first time slot of the first subframe (subframe 0)
in each radio frame. It reads symbol timing, and learns which of three cell
identities is being transmitted, and locks its frequencies to the eNB.
The UE next searches for the (S-SCH) secondary synchronization signal,
and learns which of 170 cell identities it carries. From this it decodes the
PCI, physical cell identity, and the frame boundaries
The UE next finds the RS sequence and learns antenna port configuration
Now the UE can decode the P-BCH and apply cell selection and
reselection criteria
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 104
Cell Reselection (Idle Mode Handover)
October, 2013 Course 502 v1.0.1 (c)2013 Scott Baxter Page 105
Cell Search Measurements
October, 2013 Course 502 v1.0.1 (c)2013 Scott Baxter Page 107
LTE Measurement: RSSI
LTE Downlink
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 108
LTE Measurement: RSRP
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 109
LTE Measurement: RSRQ
RB RB RB RB RB RB RB RB RB RB RB RB
After finding a cell, the UE may or may not be permitted to use it,
based on various signal quality criteria broadcast by the eNB.
Here are two procedures for cell qualification:
• In the initial cell selection procedure, no knowledge about RF
channels carrying an E-UTRA signal is available at the UE.
– In that case the UE scans the supported E-UTRA
frequency bands to find a suitable cell. Only the cell with
the strongest signal per carrier will be selected by the UE.
• The second procedure relies on information about carrier
frequencies and optionally cell parameters received and stored
from previously-detected cells.
– If no suitable cell is found using the stored information the
UE starts with the initial cell selection procedure.
S is the criterion defined to decide if the cell is still suitable . This
criterion is fulfilled when the cell selection receive level is Srxlev >
0. Srxlev is computed based on the following Equation:
October, 2013 Course 502 v1.0.1 (c)2013 Scott Baxter Page 111
‘S’ Cell Selection and Reselection criteria
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation
Where Pcompensation = max (PEMAX – PUMAX, 0)
All in db
Qrxlevmeas is the UE-measured receive level value for this cell, i.e.
the Reference Signal Received Power (RSRP
Qrxlevmin is the minimum required receive level in this cell, in dBm.
Qrxlevminoffset is an offset to Qrxlevmin that is only taken into
account as a result of a periodic search for a higher priority PLMN
while camped normally in a Visitor PLMN (VPLMN).
PCompensation is a maximum function. PEMAX is maximum power
allowed for a UE in this cell. PUMAX is maximum for power class
A UE may discover cells from different network operators.
• First the UE will look for the strongest cell per carrier,
• Then the PLMN identity from the SIB Type 1 to see if suitable,
• Then it will compute the S criterion and decide if suitable
October, 2013 Course 502 v1.0.1 (c)2013 Scott Baxter Page 112
Special Details for TDD
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 113
Getting Needed Cell Parameters:
Information Blocks
inter
The Master Information Block (MIB) gives the basic signal configuration
and bandwith
System Information Block 1 declares what other information blocks exist,
and the mobile goes about collecting all their contents
The MIB and SIB1 are carried by the BCH channel; all the other SIBS are
carried by the DL-SCH
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 114
UE (Mobile) Categories
Rationale:
The LTE UE categories or UE classes are needed to ensure that
the base station, or eNodeB, eNB can communicate correctly with
the user equipment. By relaying the LTE UE category information
to the base station, it is able to determine the performance of the
UE and communicate with it accordingly.
As the LTE category defines the overall performance and the
capabilities of the UE, it is possible for the eNB to communicate
using capabilities that it knows the UE possesses. Accordingly the
eNB will not communicate beyond the performance of the UE.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 116
LTE UE Category Definitions
Data Rates by UE Category
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 118
DRX and DTX
In active mode, there is dynamic transition between long DRX and short
DRX. Durations for long and short DRX are configured by the RRC. The
transition is determined by the eNodeB (MAC commands) or by the UE
based on an activity timer. The figure shows DRX cycle operation during a
voice over IP example. A lower duty cycle could be used during a pause in
speaking during a voice over IP call; packets are coming at a lower rate,
so the UE can be off for a longer period of time. When speaking resumes,
this results in lower latency. Packets are coming more often, so the DRX
interval is reduced during this period.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 120
UE (Mobile) States
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 122
Idle Mode Operation
EPS also includes the concept of TAL, the Tracking Area List.
• A uE does not need to initiate a TAU when it enters a new Tracking
Area, if that area is already in its present Tracking Area List
• Provisioning different lists to the UEs can avoid signaling peaks when
a large nujmber of Ues cross a TA border, for example on a train or
other public transport
EMM Connection Management Procedures
• Service request UE initiates to begin NAS signaling connection
• Network-initiated paging on NAS to UE to send service request
• Transport of NAS messages for SMS (CS fallback)
• Generic transport of NAS messages, various others
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 125
Management and Control Functions
UE management and control is handled in Radio Resource Control
(RRC). Functions handled by RRC include:
• Processing broadcast system information, so a device can decide to
connect to the network from access stratum (AS) and/or non access
stratum (NAS)
– The access stratum is the functional grouping of the parts in the
infrastructure and the UE, and protocols between them, for
access. The access stratum provides transmission of data over
the radio interface and management of the radio interface to the
other parts of UMTS
• Paging, indicating to an idle device that it may have an incoming call
• RRC connection management between the UE and the eNodeB
• Protection/ciphering RRC messages (different keys than user plane)
• Radio Bearer control (logical channels at the top of the PDCP)
• Mobility functions (handover when active, cell reselection when idle)
• UE measurement reporting and control of signal quality, both for the
current base station and other base stations that the UE can hear
• QoS management maintains the uplink scheduling to maintain QoS
requirements for different active radio bearers
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 126
EPS Session Management
EPS Session Management Protocol establishes and handles user data in the NAS
Two EPS concepts define IP connectivity between UE and packet data network:
• PDN connection
• EPS bearer
A PDN connection includes a default EPS bearer and possibly additional “dedicated
bearers” to give specific QoS handling for the traffic data flows
A UE can have multiple simultaneous PDN connections (one for web, one IMS, etc)
EPS procedure Categories:
• Network-initiated EPS procedures to activate, deactivate or modify bearers
• Transaction-related procedures initiated by the UE for
– PDN connection establishment and disconnection
– Requests for bearer resource allocation and modification
– Release requests
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 127
Access Barring During System Overload
During overload, the network can cope by changing the SIB2 (System
Information Block Type 2). The UE generates a random number “Rand”
and must pass a “persistence” test before making an access attempt.
• By setting ac-Barring to a lower value, normal UEs are randomly
delayed while priority users with AC11 – 15 have no restriction
• Regular users AC 0 – 9 obey ac-Barring Factor and ac-Barring Time.
• Emergency calls (AC10) use ac-Barring For Emergency – on or off
• UEs of AC11- 15 use ac-Barring For Special AC – on or off
• The eNB transmits ‘mean duration of access control’ and the barring
rate for each type of access attempt (data origination, signaling orig.)
• Service Specific Access Control (SSAC) can restrict attempts by
service type.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 128
Cell Reselection (Idle Mode Handover)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 129
Flow Examples
Random Access
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 130
What is Random Access?
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 132
The Steps of the Random Access Process
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 133
eNB Announces the Rules,
All the UEs learn the necessary details of the Random Access
process before they even need to use it. The network transmits it in
overhead messages. The key details include:
• Which Preamble Format to use
– Usually Preamble Format 0 providing range up to about 14
kM. Other formats are available if greater range is needed.
• When the PRACH occurs, usually once per 10 ms. radio frame
• How the UE should calculate its “open loop” transmit power for its
initial transmissions before the eNB acknowledges it
– When the eNB finally responds, it will take over using “closed
loop” power control
Step 1: Now the UE transmits its first Random Access Preamble.
3GPP TS 36.321 contains more information on power control.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 134
2. eNB sends Random Access
Response Message
When the eNB hears the UE’s random
access preamble, it generates and sends a
Random Access Response Message on the
Physical Downlink Shared Channel (PDSCH)
• It’s addressed to a specific Random Access Radio Network
Temporary Identifier (RA-RNTI) address.
• There’s room in the RARM for multiple RA-RNTI addresses in
case multiple UEs were heard and need to be acknowledged
The UE watches the PDCCH for its specific RA-RNTI address to
recognize its random access response message, which contains:
• Random access preamble sequence code identifying the
preamble sequence code which has been detected by the eNB
• Initial uplink schedule grant used for transmitting subsequent
data on the uplink channel
• Timing Alignment information so packet collisions won’t occur
• A Cell Radio Network Temporary Identifier (C-RNTI) for the UE
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 135
CBRA Contention Resolution:
Steps 3 and 4
Contention resolution steps (3 and 4) are
used whenever multiple UEs are detected
attempting random access using the same
preamble code sequence.
Step 3: The UE hears the RARM and makes its first scheduled
uplink transmission on Physical Uplink Shared Channel (PUSCH).
The UE gives the network a unique identifier in this message.
Step 4: The eNB repeats back the UE identity provided in step 3. A
UE which hears a match with the identity it transmitted now
declares the random access procedure successful. It transmits an
acknowledgment in the uplink.
UEs which don’t hear a match know they have failed the random
access procedure. They have to start over again at step 1.
Both step 3 and step 4 use the Hybrid Automatic Repeat Request
(HARQ) process. Further details on the contention resolution
process and the HARQ process are in Chapter 5.1 of 3GPP TS
36.321.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 136
Flow Examples
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 137
Tracking Area Update from LTE to GSM
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 139
Case VII. LTE>GSM Tracking Area Update
The UE moves away from the LTE network and into the
UTRAN/GERAN service area
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 140
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 141
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 142
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 143
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 144
Case VII. LTE>GSM Tracking Area Update
The Gn/Gp SGSN sends a SGSN Context ACK to the Old MME
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 145
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 146
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 147
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 148
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 149
Case VII. LTE>GSM Tracking Area Update
>GSM
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 150
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 151
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 152
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 153
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 154
Case VII. LTE>GSM Tracking Area Update
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 155
Case VII. LTE>GSM Tracking Area Update
Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 157
The S1 interface is initialized by request from the eNB to the MME
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 158
The MME confirms setup of the S1AP interface by sending an S1
Setup Successful Outcome message to the eNB
S1 Setup: This is where eNB is attached to the network. As long
the eNB is functioning the S1 setup remains.
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 159
The UE sends an RRC connection request message to the eNB
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 160
The eNB sends an RRC Connection Setup message to the UE
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 161
The UE sends an RRC Connection Setup Complete message to
the eNB
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 162
The eNB sends the requests on to the MME
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 163
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 164
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 165
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 166
LTE Initial Attach
The eNB sends a RRC DL info Transfer and NAS message to the
UE, containing the Authentication Request
Authentication/Security: Networks request Authentication Vectors
from UE. Once UE provides them, MME compares them with what
HSS has sent. If they match UE is authenticated. Next is security.
After the security all the NAS messages are encrypted using the
security algorithms that were exchanged.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 167
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 168
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 169
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 170
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 171
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 172
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 173
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 174
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 175
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 176
LTE Initial Attach
MME sends eNB the Initial Context Setup Request and NAS
message containing Attach Accept and Activate Default EPS
Bearer Context Request
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 177
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 178
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 179
LTE Initial Attach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 180
LTE Initial Attach
Attach complete
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 184
Flow Examples
UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 185
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 186
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 187
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 188
LTE UE Detach
The MME sends a Delete Session Request to the SGW using GTP
protocol.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 189
LTE UE Detach
The SGW sends the PGW a PMIP Proxy Binding Update, deleting
the EPS bearers.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 190
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 191
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 192
LTE UE Detach
The MME updates the HSS on the UE’s detachment with a Notify
Request
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 193
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 194
LTE UE Detach
Now the MME sends the eNB a DL NAS Transport + NAS Detach
Accept
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 195
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 196
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 197
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 198
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 199
LTE UE Detach
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 200
Radio System Identifiers,
Tunnels, Connections, Bearers
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 201
3. Radio System Identifiers and Parameters
UE Identifiers (IMSI, TMSI, GUTI …) • C-RNTI (Cell Radio Network Temporary
• Random Access Radio Network Identifier)
Temporary Identifier (RA-RNTI) • PCI Physical Cell Identifier
– contained in the MAC sub- • QCI QoS Class Identifier
header of each random access • RNTI Radio Network Temporary
response Identifier
• LCID Logical channel identifier • SystemInformationBlockType9 contains
• RRC layer in the Enb allocates cell- a home eNB identifier (HNBID);
level temporary identifiers • eNB Identifier (eNB ID): used to identify
• S-TMSI SAE Temporary Mobile eNBs within a PLMN.
Station Identifier • Tracking Area identity (TAI): used to
UTRAN and EPC Identifiers identify tracking areas
• ECGI E-UTRAN Cell Global • NAS UE identifier
Identifier • NAS (EPC/UE) level AKA procedure
• one or multiple 'PLMN identity' in a (KASME) and identified with a key
given cell identifier (KSIASME).
• CSG identity: broadcast by cells in a • MME includes a session identifier
CSG to allow authorized CSG • SI-RNTI System Information RNTI
member UEs to access
• CID Context Identifier
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 202
E-UTRAN Network Identities
PLMN Identity
• A Public Land Mobile Network is uniquely identified by its PLMN Identity.
Globally Unique MME Identifier (GUMMEI)
• The Globally Unique MME Identifier consists of a PLMN Identity, a MME Group
Identity and a MME Code
• An MME logical node may be associated with one or more GUMMEI, but each
GUMMEI uniquely identifies an MME logical node.
Global eNB ID
• The Global eNB ID is used to globally identify an eNB
E-UTRAN Cell Global Identifier (ECGI)
• The ECGI is used to globally identify a cell.
Tracking Area Identity (TAI)
• Each Tracking Area (a defined group of local cells) has an assigned TAI
E-RAB ID
• An E-RAB uniquely identifies the combination of an S1 bearer and the
corresponding Data Radio Bearer. Under an E-RAB, there is a one-to-one
mapping between this E-RAB and an EPS bearer of the Non Access Stratum.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 203
E-UTRAN UE Identifiers (1)
RNTI
• Radio Network Temporary Identifiers (RNTI) are used as UE
identifiers within E-UTRAN and in signaling messages between
UE and E-UTRAN. Some types of RNTI exist:
• C-RNTI Connected Radio Network Temporary Identifier
– The C-RNTI provides a unique UE identification at the cell
level identifying RRC Connection
• RA-RNTI Random-Access Ratio Network Temporary Identifier
– The RA-RNTI is used during some transient states, the UE
is temporarily identified with a random value for contention
resolution purposes
• S-TMSI S-Temporary Mobile Subscriber Identity (S-TMSI)
– The S-TMSI is a temporary UE identity in order to support
the subscriber identity confidentiality. This S-TMSI is
allocated by MME.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 204
E-UTRAN UE Identifiers (2)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 206
LTE Bearers
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 208
LTE QoS Architecture
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 209
QoS Parameters and TFTs (1)
A Traffic Flow Template (TFT) is all the packet filters associated with an EPS bearer.
• A packet filter may be associated with a protocol.
• Several packet filters can be combined to form a Traffic Flow Template.
• EBI+Packet filter ID gives us a "unique" packet filter Identifier. The following is the
TFT for FTP protocol.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 210
QoS Parameters and TFTs (2)
Bearer level QoS is associated with a bearer and all traffic mapped
to that will receive same bearer level packet forwarding treatment.
QoS parameter values of the default bearer are assigned by the
network based on the subscription data received from HSS.
In LTE the decision to establish or modify a dedicated bearer is
taken by EPC and bearer level QoS parameters are assigned by
EPC. These values are not modified by MME but are forwarded
transparently to EUTRAN. However MME may reject the
establishment of dedicated bearer if there is any discrepancy.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 211
QoS Parameters and TFTs (2)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 212
Flow Examples
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 213
LTE Default Bearer Establishment,
Incoming (1)
UE is in RRC_IDLE condition
MME has traffic for specific UE. It sends Page message to all
eNBs in UE’s current tracking area (TA).
eNB sends page message over air interface for UE
UE recognizes the page and responds by sending RRC
Connection Request message to eNB
eNB sends RRC Connection Setup message to UE
UE sends eNB a RRC Connection Setup Complete message and
NAS message including Attach Request and PDN Connectivity
Request
eNB sends Initial UE Message + NAS attach request and PDN
connectivity request to MME
eNB sends Initial UE Message + NAS attach request and PDN
connectivity request to MME
MME sends Create Session Request to SGW using GTP
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 214
LTE Default Bearer Establishment, Incoming
UE is in RRC_IDLE condition
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 215
LTE Default Bearer Establishment, Incoming
MME has traffic for specific UE. It sends Page message to all
eNBs in UE’s current tracking area (TA).
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 216
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 217
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 218
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 219
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 220
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 221
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 222
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 223
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 224
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 225
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 226
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 227
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 228
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 229
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 230
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 231
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 232
LTE Default Bearer Establishment, Incoming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 234
LTE Default Bearer Establishment, Outgoing
UE is in RRC_Idle mode
UE has data and needs connection to network
UE sends RRC Connection Request to eNB
eNB sends RRC Connection Setup to UE
UE sends RRC Connection Setup Complete and NAS Attach
Request and PDN Connectivity Request to eNB
eNB sends Initial UE Message and NAS Attach Request and PDN
Connectivity Request to MME
MME sends Create Session Request to SGW using GTP
SGW sends PMIP Proxy Binding Update to PGW
PGW sends PMIP Proxy Binding Ack to SGW
SGW sends Create Session Response to MME by GTP
MME sends eNB an Initial Context Setup Request and NAS
Activate Default EPS Bearer Context request and Attach Accept
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 235
LTE Default Bearer Establishment, Outgoing
UE is in RRC_Idle mode
UE has data and needs connection to network
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 236
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 237
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 238
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 239
LTE Default Bearer Establishment, Outgoing
eNB sends Initial UE Message and NAS Attach Request and PDN
Connectivity Request to MME
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 240
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 241
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 242
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 243
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 244
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 245
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 246
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 247
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 248
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 249
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 250
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 251
LTE Default Bearer Establishment, Outgoing
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 253
Resource Allocation in LTE
Resources in LTE
• Resource Grid, Resource Block, Slot, Sub-frame
Control Information
• Physical Channels, PDCCH, DCI
Resource Allocation
• Resource Block Group (RBG) based
• RBG Subset based
• Virtual Resource Block (VRB)-based
Helpful Link: very useful utility showing LTE resource grid
• http://paul.wad.homepage.dk/LTE/lte_resource_grid.html
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 254
LTE Scheduling
The eNodeB allocates physical layer resources for the uplink and
downlink shared channels (UL-SCH and DL-SCH). Resources are
composed of Physical Resource Blocks (PRB) and Modulation
Coding Scheme (MCS). The MCS determines the bit rate, and
thus the capacity, of PRBs. Allocations may be valid for one or
more TTIs; each TTI interval is one subframe (1 ms).
Semi-persistent scheduling reduces control channel signaling. If
every allocation was individually signaled, the overhead would be
unacceptable. In an application such as voice over IP, for example,
a downlink frame occurs every 10 to 20 milliseconds. If each
downlink frame were signaled individually, it would cause a lot of
traffic on the control channel and the control channel would need a
lot more bandwidth than necessary. Semi-persistent scheduling
lets you set up an ongoing allocation that persists until it is
changed. Semi-persistent schedules can be configured for both
uplink and downlink.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 255
Scheduling: Transmission Time Interval (TTI)
The scheduler is the main player in rapidly utilized radio resource. The
smallest Transmission Time Interval (TTI) is only 1 ms.
During each TTI the eNB scheduler:
• considers the physical radio environment per UE. The UEs report
received radio quality to the scheduler which decides which
Modulation and Coding scheme to use. The scheduler rapidly adapts
to channel variations, using HARQ (Hybrid Automatic Repeat
Request), soft-combining, and rate adaptation.
• prioritizes QoS requirements among the UEs. Both delay sensitive
and rate-sensitive data services are accomodated.
• informs UEs of their allocated downlink and uplink radio resources.
Each UE scheduled in a TTI gets a Transport Block (TB) carrying its data.
• On downlink there can be a maximum of two TBs generated per UE if
using MIMO. The TBs are delivered over a transport channel.
• The user plane has only one shared channel in each direction. The TB
can contain bits from several services, multiplexed together.
• In theory the highest number of users that can be scheduled during 1
ms is 440, presuming 20 MHz band and 4x4 Multi User MIMO.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 256
Downlink: Dynamic Scheduling
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 259
Downlink Scheduling with HARQ
This figures shows the ACK/NACK process. The Physical HARQ Indicator Channel
(PHICH) is a special channel for providing feedback from the eNodeB back to the
UE on the uplink HARQ process. It carries ACK/NACK messages for uplink data
transport blocks. HARQ is synchronous, with a fixed time of 4 TTI from uplink to
ACK/NACK on the downlink from the eNodeB. The eNodeB responds back with an
opportunity to retransmit which is then scheduled and retransmitted. Although this
illustration does not show the positive acknowledgement after that, it would occur.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 262
LTE Handover and Roaming
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 263
Introduction to Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 264
Handover Measurement
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 265
Handover: Neighbor Lists
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 266
Handover Procedures - Objectives
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 267
Handover Types
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 268
Flow Examples
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 269
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 270
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
The Data call is already established between the UE, S-eNB and
network elements.
Data packets are already flowing to/from the UE on both DL & UL.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 271
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 272
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 273
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 274
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 275
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 276
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 277
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 278
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 279
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
In the meantime, the UE tries to access the T-eNB cell using the
non-contention-based Random Access Procedure.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 280
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 281
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 282
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 283
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
The SGW sends one or more “end marker” packets on the old path
to the S-eNB and then can release any user plane / TNL resources
toward the S-eNB.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 284
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
15. The MME responds to the T-eNB with a PATH SWITCH REQ
ACK message to notify the completion of the handover.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 285
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
User data packets now flow between the SGW and the UE.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 286
Case I. Intra-LTE (Intra-MME / SGW) Handover
Using the X2 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 287
Flow Examples
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 288
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
An S1-based handover procedure is used when the X2-based
handover cannot be used
• no X2 connectivity to the target eNodeB;
• by an error indication from the T-eNB after an unsuccessful X2-
based handover
• by dynamic information learned by the S-eNB using the
STATUS TRANSFER procedure.
The S-eNB initiates the handover by sending a Handover required
message over the S1-MME reference point. The EPC does not
change the decisions taken by the S-eNB.
The availability of a direct forwarding path is determined in the S-
eNB (based on the X2 connectivity with the T-eNB) and indicated
to the source MME.
• If a direct forwarding path is not available, indirect forwarding
will be used. The source MME uses the indication from the S-
eNB to determine whether to apply indirect forwarding or not.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 289
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 290
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
The UE is sending and receiving user data on both the uplink and
downlink.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 291
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 292
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 293
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 294
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 295
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 296
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 297
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 298
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 299
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 300
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 301
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 302
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 303
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 304
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 305
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 306
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 307
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
User data packets now flow between the UE and the SGW.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 308
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 309
Case II. Intra-LTE (Intra-MME / SGW) Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 310
Flow Examples
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 311
Case III. Inter-MME Handover (Intra-SGW)
(no change in Gateway)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 312
Case III. Inter-MME Handover (Intra-SGW)
The UE is sending and receiving user data on both the uplink and
downlink.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 313
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 314
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 315
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 316
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 317
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 318
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 319
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 320
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 321
Case III. Inter-MME Handover (Intra-SGW)
The Target MME sends an eNB Status Transfer to the Target eNB
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 322
Case III. Inter-MME Handover (Intra-SGW)
The Serving eNB sends Forward User data to the SGW by GTP
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 323
Case III. Inter-MME Handover (Intra-SGW)
The SGW sends Forward User Data to the Target eNB by GTP
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 324
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 325
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 326
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 327
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 328
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 329
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 330
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 331
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 332
Case III. Inter-MME Handover (Intra-SGW)
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 335
Case IV. Inter-MME / SGW Handover
Using the S1 Interface
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 336
Case IV. Inter-MME / SGW Handover
Using the S1 Interface
The UE is sending and receiving user data on both the uplink and
downlink.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 338
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 339
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 340
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 341
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 342
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 343
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 344
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 345
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 346
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 347
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 348
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 349
Case IV. Inter-MME / SGW Handover
The Target MME sends an eNB Status Transfer to the Target eNB
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 350
Case IV. Inter-MME / SGW Handover
The Serving eNB sends Forward User Data to the Target eNB
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 351
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 352
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 353
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 354
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 355
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 356
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 357
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 358
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 359
Case IV. Inter-MME / SGW Handover
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 364
LTE Security
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 365
LTE Security Objectives
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 366
Basic Development of LTE Security
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 367
The LTE USIM
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 368
Voice over LTE
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 369
Why Voice Over LTE?
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 370
Options for Voice over LTE
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 371
Issues for Voice Services over LTE
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 372
Voice over LTE (VoLTE) Basics
The One Voice profile for Voice over LTE (VoLTE) was developed
by a collaboration between over forty operators and manufacturers
including AT&T, Verizon Wireless, Nokia and Alcatel-Lucent.
• At the 2010 GSMA Mobile World Congress, GSMA announced
their support for the VoLTE solution to provide Voice over LTE.
• VoLTE, Voice over LTE is an IMS-based specification.
Adopting this approach, it enables the system to be integrated
with the suite of applications that will become available on LTE
Three interfaces are being defined to provide VoLTE:
• User Network interface, UNI: between the user's equipment
and the operators network.
• Roaming Network Network Interface, R-NNI: located between
the Home and Visited Network.
• Interconnect Network Network Interface, I-NNI: located
between the networks of the two parties making a call.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 373
Continuing Work on LTE
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 374
IMS
IP Multimedia Subsystem
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 375
What is IMS?
IP Multimedia Core Network Subsystem
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 376
IMS Basics
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 377
IMS Architecture Basics
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 378
IMS Architecture Functional View
Elements of overall IMS architecture:
Server CSCF: session control for endpoint
devices; maintains state.
Proxy CSCF: entry point to IMS for the UE;
forwards SIP messages to user's home S-CSCF;
controls inter-working security; QoS mgt.
Interrogating CSCF: a session control for endpoint
devices.
Home Subscriber Server, HSS: provides
subscriber database for the home network.
Breakout gateway control function, BGCF: selects
the network in which a PSTN breakout is to occur.
If on in the same network as the BGCF, also
selects a media gateway control function, MGCF
Media gateway control function, MGCF:
interworks the SIP signalling. manages sessions
across multiple media gateways
Media server function control, MSCF: manages
the use of resources on media servers.
SIP applications server, SIP-AS: execution
platform to deploy more services
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 379
LTE Advanced
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 380
LTE Advanced
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 381
LTE Advanced (2)
Carrier Aggregation
The simplest way to increase
capacity is to add more bandwidth.
To keep backward compatibility with
R8 and R9 mobiles the increase in
bandwidth in LTE-Advanced is
provided through aggregation of
R8/R9 carriers. Carrier aggregation
can be used for both FDD and TDD.
Each aggregated carrier is referred
to as a component carrier.
A component carrier can have a
bandwidth of 1.4, 3, 5, 10, 15 or 20
MHz Up to five component carriers The maximum aggregate
can be aggregated. bandwidth is 100 MHz.
R10 UEs can use DL and UL on up The number of aggregated
to five Component Carriers (CC). carriers can be different in DL
R8/R9 UEs can use any ONE of the and UL, but UL is never larger
CCs. The CCs can be of different than DL. The individual
bandwidths. component carriers can have
different bandwidths.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 382
LTE Advanced (3)
Continuous and Non-Continuous Aggregation
Contiguous component carriers in the same operating frequency band are called
intra-band contiguous. This simplest arrangement is not always possible..
Non-contiguous allocation can be intra-band, i.e. the component carriers belong to
the same operating frequency band, but are separated by a gap
Non-contiguous allocation can be inter-band, in which case the component carriers
belong to different operating frequency bands
Each component carrier is present on certain cells. Not all cells have all carriers.
The coverage of serving cells may differ due to different frequencies and powers
RRC connection is handled by one cell, the Primary serving cell, using the Primary
component carrier (DL and UL PCC). The other component carriers are called
Secondary component carriers (DL and UL SCC), on secondary serving cells.
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 383
Differing Coverage of Different Carriers
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 385
Main Differences in LTE Protocols
to Support Carrier Aggregation
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 386
Cross-Carrier Scheduling
Regarding scheduling there are two main alternatives for CA, either
resources are scheduled on the same carrier as the grant is received, or
so called cross-carrier scheduling may be used
Figure 5. CA scheduling (FDD). Cross- carrier scheduling is only used to
schedule resources on SCC without PDCCH. The CIF (Carrier Indicator
Field) on PDCCH (represented by the red area) indicates on which carrier
the scheduled resource is located
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 387
More References on Carrier Aggregation
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 388
LTE SON:
Self Organizing/Optimizing Networks
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 389
Major Elements of LTE SON
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 390
LTE SON Development
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 391
LTE SON and 3GPP Standards
October, 2013 Course 512 v1.0 (c)2013 Scott Baxter Page 392