LTE Protocol, Procedure, Performance Management & Optimization Training Material

LTE Protocols, Procedures, Air Interface,
Performance Management & Optimization
LTE Protocols and

Procedures
EPS Protocols Introduction
1
Objectives of Chapter 1
After this chapter the participants will be able to:

1. Distinguish between the different EPS protocol types.
2. Explain the EPS architecture, Bearer and Tracking Area.
3. Draw a simplified EPS diagram showing the protocols used.
LTE Air Interface Features Overview
TX RX
Fast Link Adaptation 64QAM MIMO Advanced Scheduling
due to channel behavior Modulation Tx Channel Rx Time & Freq.
scalable Short TTI = 1 ms

Transmission time
interval
ARQ Automatic
Repeat Request
DL: OFDMA
UL: SC-FDMA
OFDM is the state-of-the-art and most efficient and robust air interface
2
Evolved Packet System (EPS)
User Plane IP Networks PCRF: Policy and Charging Rules Function
Control Plane PGW: Packet Data Network Gateway

SGi
HSS: Home Subscriber Server
S4
Gx EPC: Evolved Packet Core
HSS PGW PCRF
SGW: Serving Gateway
S10 S6a S5/S8
UE: User Equipment
EPC
S3 EUTRAN: Evolved UTRAN
SGSN MME SGW
S11 eNodeB: Enhanced Node B
SGs
VLR: Visitor Location Register
S1-MME S1-U
MSC/VLR MSC: Mobile Switching Centre
X2 MME: Mobility Management Entity

eNodeB eNodeB
GPRS Network LTE Uu LTE Uu: LTE UTRAN UE Interface
Only most important EUTRAN
UE SGSN: Serving GPRS Support Node
interfaces shown here
What is a ‘Protocol’?
Definition for computers:
Protocol is a set of rules governing the
format of messages that are
exchanged between computers.
3
Protocol Categories
› Signalling Protocols (Layer 3)
These protocols are used to communicate between nodes using various messages
with a defined structure.
An example of a signalling protocol (Layer 3) is the X2 Application Protocol (X2AP)
which is used by eNodeBs to communicate across the X2 interface.
› Transport Protocols (Layer 2)
These protocols are used to transport signalling and user data across the EPC
interfaces and are responsible for the following functions:
- Header Compression/Decompression
- Ciphering
- Segmentation and concatenation
- In sequence delivery
- Automatic Retransmission reQuest (ARQ)
An example of a transport protocol (Layer 2) is the Radio Link Control (RLC)
protocol used to carry signalling and user data across the air interface.
LTE Specifications
36.201 – Physical layer general description 36.401 – E-UTRA Architecture Description
36.211 – Physical channels and modulation 36.410 – S1 interface general aspects & principle
36.212 – Multiplexing and channel coding 36.411 – S1 interface Layer 1
36.213 – Physical layer procedures 36.412 – S1 interface signalling transport
36.214 – Physical layer measurements 36.413 – S1 application protocol S1AP
36.414 – S1 interface data transport
36.420 – X2 interface general aspects and principles
36.421 – X2 interface layer1
36.422 – X2 interface signalling transport
36.300 – E-UTRA overall description 36.423 – X2 interface application part X2AP
36.302 – Services provided by the physical layer 36.442 – UTRAN Implementation Specific O&M Transport
36.304 – UE Functions related to idle mode 29.274 – GTP-C
36.306 – UE radio access capabilities 29.281 – GTP-U
36.321 – Medium Access Control (MAC)
Protocol Specification 23.002 – Network Architecture
36.322 – Radio Link Control (RLC) 23.003 – Numbering, addressing and identification
Protocol Specification 23.009 – Handover Procedures
36.323 – Packet Data convergence Protocol (PDCP) 23.048 – Security mechanisms for USIM application
Protocol Specification 23.401 – GPRS enhancements for eUTRA
36.331 – Radio Resource Control (RRC) 23.203 – QoS Concept
Protocol Specification 23.272 – CS Fallback in EPS
33.401 – System Architecture Evolution (SAE);

Security Architecture
36.101 – UE radio transmission and reception (FDD)
36.104 – BTS radio transmission and reception (FDD)
24.301 – NAS Protocol for Evolved Packet System (EPS)
36.113 – Base station EMC
24.302 – Access to the EPC via non 3GPP networks
36.133 – Requirements for support of Radio Resource
Management (FDD)
36.141 – Base station conformance testing (FDD)
All specifications can be found on the

web site www.3gpp.org
4
EPS Bearer
EUTRAN EPC IP Network
UE eNodeB SGW PGW Peer
Entity
End-to-end Service
EPS Bearer External Bearer
E-RAB S5/S8 Bearer
Data Radio Bearer S1 Bearer
Uu S1-U S5/S8 SGi

Established by UE at connection to network and maintained
Default Bearer: until UE is switched off or out of coverage. (no QoS defined)
Dedicated Bearer: Established by network to allow flow of traffic between UE and

PGW and is maintained until data is transferred. (various QoS)
LTE UE States
MME Tracking Area Update Handover
(TAU)
eNodeB
Tracking Area (TA)

UE position known on Cell
UE pos known on TA level in MME level in eNodeB
ECM: EPC Connection Management
Detach, Attach reject,
TAU reject EMM: EPC Mobility Management
Signaling RRC: Radio Resource Management
connection
establishment
UE
position
not known
ECM-IDLE ECM-CONNECTED
in network
RRC_IDLE RRC_IDLE RRC_CONNECTED
PLMN
selection Signaling
EMM- connection EMM-
DEREGISTERED release REGISTERED
Attach accept,
TAU accept
5
EPS Control Plane Protocols
LTE Uu S1-MME
NAS NAS S11 S5/S8
Relay
RRC S1AP GTP-C GTP-C GTP-C
RRC S1AP
PDCP PDCP SCTP SCTP UDP UDP UDP
RLC RLC IP IP IP IP IP
MAC MAC L2 L2 L2 L2 L2
L1 L1 L1 L1 L1 L1 L1
UE eNodeB X2 MME S10 SGW PGW
X2AP X2AP GTP-C GTP-C
SCTP SCTP UDP UDP

IP IP IP IP
L2 L2 L2 L2
L1 L1 L1 L1
eNodeB eNodeB MME MME
EPS User Plane Protocols

LTE Uu S1-U S5/S8 SGi
Application
IP IP
Relay Relay
PDCP GTP-U
PDCP GTP-U GTP-U GTP-U
RLC RLC UDP UDP UDP UDP
IP IP IP IP
L2
MAC MAC
L2 L2 L2 L2
L1 L1 L1
L1 L1 L1 L1
UE eNodeB X2* SGW PGW

GTP-U GTP-U
* X2 User plane used
UDP UDP
to support ‘Data
IP IP
forwarding at intra
L2 L2
LTE handover’
L1 L1
eNodeB eNodeB
6
EPS Protocol Categories
L3 Signalling L2 Transport
Non Access Stratum (NAS) Packet Data Convergence Protocol (PDCP)
Communication between UE and MME - Ciphering and integrity protection for RRC messages
- IP header compression/decompression for user plane
Radio Resource Control (RRC)

Communication between UE and eNodeB Radio Link Control (RLC)
- Transfer of RRC messages and user data using:
* Acknowledged Mode (AM)
S1 Application Protocol (S1AP) * Transparent Mode (TM) or
Communication between eNodeB and MME * Unacknowledged Mode (UM)
- Error Correction (ARQ)
X2 Application Protocol (X2AP) Medium Access Control (MAC)

Communication between eNodeB and eNodeB - Error Correction (HARQ)
- Transfer of RRC messages and user data using:
- Priority handling (scheduling)
GPRS Tunneling Protocol Control (GTP-C) - Transport Format selection
- Communication between MME and SGW
- Communication between SGW and PGW GPRS Tunneling Protocol User (GTP-U)
- Communication between MME and MME Transfers data between GPRS tunneling endpoints
Summary of Chapter 1
The students should now be able to:

1. Distinguish between the different EPS protocol types.
2. Explain the EPS architecture, Bearer and Tracking Area.
3. Draw a simplified EPS diagram showing the protocols used.
7
Thank You
8
LTE Protocols and
Procedures
Quality of Service and Security in LTE

1. Explain the concept of Quality of Service
2. Explain the purpose of EPS Bearer Services and eUTRA Radio Bearers
3. List the different attributes of the eUTRA Radio Bearer and explain how
they are used
4. Explain Authentication Procedure
5. Explain Radio Access Security
6. Explain TN Security
9
Quality of Service
User (subscriber)
Quality
of service
Service Service Service Service Service Service

support operability accessibility retainability integrity security
performance performance performance performance performance
Serveability performance
Quality of Service
Network Performance
Provider (operator)
Quality of service: How the subscriber is

satisfied with the Overall Service
› Accessibility:
– To be able to get in contact with the network
› Retainability:
– To continue the connection with the network until all tasks are
successfully terminated
› Service Integrity:
– To be able to perform a service and to keep the quality of the connection
on a level, where the information can successfully be exchanged in the
shortest possible time
› Support Performance:
– The ability of the operator to provide the service and to use its utilization
› Operability Performance:
– The ability of a service to be successfully and easily used by the user
› Security:
– EIR, secure billing, no unauthorized monitoring, TMSI, etc.
10
Network Security Concepts
› Authentication
– I know who I am talking to and who is talking to me.
› Integrity Protection
– Nobody has tampered with the data I am sending/receiving
› Confidentiality
– I know that nobody else can listen other than who my information is
intended for.
› Keys
– Shared pieces of information to enable authentication, integrity protection
and ciphering. Eg password
› Security Algorithms
– Used with keys to
› Authenticate users and network.
› Digitally sign a piece of information to enable integrity protection.
› Turn unencrypted information into encrypted information and vice-versa.
Security on Uu & S1 Interfaces

User Plane
IP Payload S-GW
LTE Security
PDCP PDCP GTP-U GTP-U (defined by 3GPP )
RLC RLC UDP UDP
User plane (Uu component):
MAC MAC IP IP Ciphering only.
IPsec IPsec
Data Link Data Link Implemented on PDCP layer.
Physical Physical Physical Physical
NAS signalling:
Control Plane Integrity and ciphering.
Implemented in NAS protocol.
MME
NAS NAS RRC:
Integrity and ciphering.
Implemented in PDCP layer.
RRC RRC
S1AP S1AP
PDCP PDCP
SCTP SCTP IP Network Security
RLC RLC
(defined by IETF RFCs)
MAC MAC IP IP
IPsec IPsec
Data Link Data Link Transport network:
Physical Physical Physical Physical Integrity and ciphering.
Secured by IPsec tunnels
Uu S1
11
Bearer Concept
E-UTRAN EPC Internet
UE eNB S-GW P -GW Peer

Entity
End-to-end Service
EPS Bearer External Bearer
E-RAB S5/S8 Bearer
Radio Bearer S1 Bearer
Radio S1 S5/ S8 Gi
Two Unicast EPS Bearers

TS 23.401
Application / Service Layer
UL Traffic Flow Aggregates DL Traffic Flow Aggregates

UL-TFT DL-TFT
UL-TFT  RB-ID DL-TFT  S5/S8-TEID
RB-ID S1-TEID S1-TEID S5/S8-TEID
UE eNodeB
eNB Serving GW PDN GW
Radio Bearer S1 Bearer S5/S8 Bearer
TFT: Traffic Flow Template, TEID: Tunnel Endpoint Identifier
12
Standardized QoS TS 23.203
QCI Resource Priority Packet Packet Example Services
Type Delay Error
(Quality Class Identifier)
Budget Loss
Rate
1 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video
(Live Streaming)
GBR
3 3 50 ms 10-3 Real Time Gaming
4 5 300 ms 10-6 Non-Conversational Video
(Buffered Streaming)
5 1 100 ms 10-6 IMS Signalling
Voice,
6 6 300 ms 10-6 Video (Live streaming)
Interactive Gaming
7 7 10-3 Voice,
Non GBR
100 ms Video (Live Streaming)
Interactive Gaming
8 8 TCP-based (e.g., www, e-
9 9 mail, chat, ftp, p2p file
300 ms 10-6
sharing, progressive
video, etc.
LTE/EPC/IMS Architecture example and

QoS Mapping of EPS Bearers for Voice
S6a Sh
HSS
MME
Cx MTAS
S1-MME S11
Gx PCRF Rx ISC
S5/
e-Uu S1-U SGi Mw
S8
I-/S-
eNB PDN CSCF
S-GW GW
Gm P-CSCF
SIP (SDP) Default Bearer for IMS Signaling,QCI=5
Voice(RTP) Mb
Dedicated Bearer for Voice (RTP) , QCI=1
RTCP
BGF / orig
term
XCAP Default Bearer , QCI=8/9 Ut MGw
E-UTRAN EPC IMS
13
LTE/EPC/IMS Architecture example and
QoS Mapping of EPS Bearers for Video Call
S6a Sh
HSS
MME
Cx MTAS
S1-MME S11
Gx PCRF Rx ISC
S5/
e-Uu S1-U SGi Mw
S8
I-/S-
eNB PDN CSCF
S-GW GW
Gm P-CSCF
SIP (SDP) Default Bearer for IMS Signaling,QCI=5
Voice(RTP) Mb
Dedicated Bearer for Voice (RTP) , QCI=1
RTCP
Video(RTP) Dedicated Bearer for Video,
QCI=2 GBR /QCI=6, non-GBR orig
RTCP Ut BGF / term
XCAP Default Bearer , QCI=8/9 MGw

E-UTRAN EPC IMS
Multiple Data Radio Bearer
MME PCRF
PCRF
RRC_
CONNECTED
SGW
PDN
S-GW GW
SIGNALLING RADIO BEARER S1 BEARER
EPS BEARER QCI=5

EPS BEARER QCI=1
Max 8
EPS BEARER QCI=9
EPS BEARER QCI=2
14
QoS Framework in E-UTRAN
OSS-RC
Operator specific QoS parameters
QCI Prio LCG DSCP

2 2 46
MME 1
QoS Table
QCI 2 4 1 36
: : :
: : : :
:
9 3 12
9
10 3 0
10-256
Prio,LCG DSCP
Radio Network: Transport Network:

Scheduler strategy (per RBS) X2 Packet Forwarding
Ul/DL Scheduling S1 UL Packet treatment
UL Traffic Separation
QCI LCG Example of mapping of logical
channels to logical channel
1-3 1
groups in uplink
4-6 2
7-9 3
10-256 3
LCG 0 LCG 1 LCG 2 LCG 3
QCI 1 QCI 4 QCI 7
QCI 8
QCI 2 QCI 5
Logical QCI LCG QCI 9
Channel QCI 3 QCI 6 QCI 10-256
3 3 1
4 8 3
5 3 1
1 2 3 8 5 6 4 7
6 3 2
7 7 3
8 2 1
Logical
channels
15
IP DiffServ Field
Precedence Level
IP
Header DS5 DS4 DS3 DS2 DS1 DS0 ECNECN
Precedence
Description
Level
7 Stays the same

Assured Forwarding (AF)
6 Stays the same
Drop Class 1 Class 2 Class 3 Class 4
5 Express Forwarding (EF)
4 Class 4 Low
001 010 010 010 011 010 100 010
DSCP= 10 DSCP= 18 DSCP= 26 DSCP= 34
3 Class 3
Medium
001 100 010 100 011 100 100 100
2 Class 2 DSCP= 12 DSCP= 20 DSCP= 28 DSCP= 36
1 Class 1
High
001 110 010 110 011 110 100 110
0 Best Effort DSCP= 14 DSCP= 22 DSCP= 30 DSCP= 38
Eg. Best Effort 000000 DSCP =0 and Class 2, low drop 010010 DSCP=18
Mapping from QCI to DSCP and Pbits
Bearer QoS details from MME (QCI, MBR/GBR, ARP) Data
Takes place in
Mapping
eNodeB and SGW
function
IP datagram DSCP Data

IP header
Mapping Takes place in devices
function on edge between
L3 and L2 network
Ethernet
frame Pbits DSCP Data
Ethernet header IP header
16
Default Bearer Setup
False
S1AP: Initial Context Setup Request

GTP-C: Create Session Request S-GW
MME
Default Bearer QoS

Recommended QoS Handling
Traffic Type DSCP DSCP P-bits Minimized Starvation & Minimized jitter & Bandwidth
code Strict Priority guarantees
4 CoS 3 CoS 4 CoS 3 CoS

Network Synch LU 49 7
1 1
Routing, Network Control CS6 48 7 1 1
QCI5–IMS Signalling CS5 40 6 2 2
QCI1–GBR Conversational Voice EF 46 5
QCI3–GBR Real Time Gaming AF41 34 5 1 1
QCI2–GBR Conversational Video (Live Streaming) AF42 36 5
2 2
QCI4-GBR Non-Conversational Video (Buffered Streaming) AF31 26 4
QCI6-Non-GBR TCP Specific Services AF32 28 4 2 2

S1AP/X2AP-Inter-node Signalling CS3 24 4
QCI7-Non-GBR Voice/Video Interactive Gaming AF22 18 3
3 3
OAM Access CS2 16 3
QCI8-Non-GBR TCP ’Premium bearer’ AF11 10 1 3 3
QCI9-Non-GBR TCP Default Bearer AF12 12 0 4 4
OAM Bulk Data CS1 8 0
DSCP = 12, P-bits = 0
17
QCI 9 Predefined Mapping
DSCP to P-Bit Mapping
0 Not Default setting
18
Dedicated Bearer Setup
true
true
S1AP: E-RAB Setup Request

GTP-C: Create Bearer Request
MME S-GW
Dedicated Bearer QoS (QCI 5)

Recommended QoS Handling
Traffic Type DSCP DSCP P-bits Minimized Starvation & Minimized jitter & Bandwidth
code Strict Priority guarantees
4 CoS 3 CoS 4 CoS 3 CoS

Network Synch LU 49 7
1 1
Routing, Network Control CS6 48 7 1 1
QCI5–IMS Signalling CS5 40 6 2 2
QCI1–GBR Conversational Voice EF 46 5
QCI3–GBR Real Time Gaming AF41 34 5 1 1
QCI2–GBR Conversational Video (Live Streaming) AF42 36 5
2 2
QCI4-GBR Non-Conversational Video (Buffered AF31 26 4
Streaming)
QCI6-Non-GBR TCP Specific Services AF32 28 4 2 2
S1AP/X2AP-Inter-node Signalling CS3 24 4

QCI7-Non-GBR Voice/Video Interactive Gaming AF22 18 3
3 3
OAM Access CS2 16 3
QCI8-Non-GBR TCP ’Premium bearer’ AF11 10 1 3 3
QCI9-Non-GBR TCP Default Bearer AF12 12 0 4 4
OAM Bulk Data CS1 8 0
DSCP = 40, P-bits = 6
19
QCI 5 Predefined Mapping
DSCP to P-Bit Mapping
6 Not Default setting
20

1. Explain the concept of Quality of Service
2. Explain the purpose of EPS Bearer Services and eUTRA Radio Bearers
3. List the different attributes of the eUTRA Radio Bearer and explain how
they are used
4. Explain Authentication Procedure
5. Explain Radio Access Security
6. Explain TN Security
Thank You
21
LTE Protocols and
Procedures
L3 Protocols: NAS, RRC, S1AP, X2AP, GTP-C
› Explain the functions of the Non Access Stratum NAS

protocol
› Describe the procedures in the NAS layer
› Explain the interaction between RRC and the lower layers in
the control plane
› Explain the RRC connected and idle modes (states)
› Explain the functions and services of RRC such as System
Information Broadcast, Paging, Cell Selection and Mobility
› Explain the main functions and procedures of X2AP signaling
protocol
› Explain the main functions and procedures of S1AP signaling
protocol
› Explain the main functions and procedures of the signaling
protocol GTP-C
22
NAS: UEMME Signaling
› Support of Session management

› Support of UE mobility
MME
› NAS Security
NAS Elementary Procedures
EPS Elementary
Procedures
EPS Connection Management EPS Mobility Management
"ready-to-use" IP connectivity and an "always-on" experience
23
NAS EPS Mobility
Management Messages
› Attach Request › Identity Request
› Attach Accept › Identity Response
› Attach Complete › Security Mode Command
› Attach Reject › Security Mode Complete
› Authentication Request › Security Mode Reject
› Authentication Response › Security Protected NAS message
› Authentication Failure › Service Request
› Authentication Reject › Service Reject
› CS Service Notification › Tracking Area Update Request
› Detach Request › Tracking Area Update Accept
› Detach Accept › Tracking Area Update Complete
› Downlink NAS Transport › Tracking Area Update Reject
› EMM Information › Uplink NAS Transport
› EMM Status › Downlink generic NAS transport
› Extended Service Request › Uplink generic NAS transport
› GUTI Reallocation Command
› GUTI Reallocation Complete
NAS EPS Session

Management Messages
› Activate Dedicated EPS Bearer Context Request › ESM Information Request
› Activate Dedicated EPS Bearer Context Accept › ESM Information Response
› Activate Dedicated EPS Bearer Context Reject › ESM Status
› Activate Default EPS Bearer Context Request › Modify EPS Bearer Context Request
› Activate Default EPS Bearer Context Accept › Modify EPS Bearer Context Accept
› Activate Default EPS Bearer Context Reject › Modify EPS Bearer Context Reject
› Bearer Resource Allocation Request › Notification
› Bearer Resource Allocation Reject › PDN Connectivity Request
› Bearer Resource Modification Request › PDN Connectivity Reject
› Bearer Resource Modification Reject › PDN Disconnect Reject
› Deactivate EPS Bearer context Request › PDN Disconnect Request
› Deactivate EPS Bearer context Accept
› Deactivate EPS Bearer context Reject
24
EMM States
EMM-TRACKING-
EMM NULL AREA-UPDATING-
INITIATED
EMM- EMM-
1 DEREGISTERED DEREGISTERED
-INITIATED -INITIATED
EMM EMM EMM REGISTERED

EMM REGISTERED
DEREGISTERED DEREGISTERED
2 EMM- 3 1 EMM- 2
REGISTERED COMMON PROC
-INITIATED -INITIATED
Any State EMM-SERVICE-

REQUEST-
INITIATED
EMM main states in the UE EMM main states in the MME
EMM- REGISTERED Mode
EMM IDLE EMM REGISTERED EMM CONNECTED
NOTE:
EMM-CONNECTED mode: A UE is in EMM-CONNECTED mode when a NAS signalling connection
between UE and network is established. The term EMM-CONNECTED mode used in the TS 24.301
corresponds to the term ECM-CONNECTED state used in 3GPP TS 23.401.
EMM-IDLE mode: A UE is in EMM-IDLE mode when no NAS signalling connection between UE and
network exists. The term EMM-IDLE mode used in the TS 24.301 corresponds to the term ECM-IDLE
state used in 3GPP TS 23.401
25
UE Context in MME
• GUTI
• TA List
• COUNT
• SGW TEID
• eNB S1AP id
• eNB TEID
UE Mode of Operation
Voice Centric
CS/PS Mode1:
UE registeres to EPS PS Mode1:
services and non EPS UE registeres only to
Services CS/PS EPS services
PS Mode 1 and UE usage is voice
UE usage is voice centric Mode 1
centric
Data Centric
CS/PS
CS/PS Mode2:
UE registeres to EPS Mode 2 PS Mode 2
services and non EPS
Services PS Mode:
UE usage is data centric UE registeres only to
EPS services
UE usage is data centric
26
Elementary Procedures for EPS MM
EMM Common Procedures

› Establishment of NAS Signaling Connection
› Release of the NAS Signaling Connection
› GUTI Reallocation Procedure
› Authentication Procedure
› Security Mode Control Procedure
› Identification Procedure
› EMM Information Procedure
Elementary Procedures for EPS MM
EMM Specific Procedures

› Attach Procedure
› Detach Procedure
› Tracking Area Update Procedure
EMM Connection Management Procedures

› Service Request
› Paging Procedure
› Transport of NAS Messages Procedure
› EMM Information Procedure
27
Elementary Procedures for EPS SM
ESM Procedures Related to EPS Bearer
› Default EPS Bearer Context Activation
› Dedicated EPS Bearer Context Activation
› EPS Bearer Context Modification
› EPS Bearer Context Deactivation
ESM Transaction Related Procedures

› PDN Connectivity Procedure
› PDN Disconnect Procedure
› Bearer Resource Allocation Procedure
› Bearer Resource Modification Procedure
RRC: UEeNB Signaling
Idle Mode Support

E-RAB Management Support
Mobility Management Support
RAN Security Support
Radio Connection Supervision Support
Transparent Signaling Support
28
UE Protocol Stack
Session Mobility
NAS Security
NAS Management Management
Application
System Info Cell Paging Connected

Aquisition Selection Reception Mode
Mobility IP
RRC RB Measurement
RRC AS Security
Connection Managementv Reporting
Control/Report SAPs
Integrity/ ROHC/
Ciphering Ciphering
PDCP
TM/UM AM
UM/AM
RLC
HARQ
RA Control
MAC Control
L2
Physical Layer
EPS States
Tracking Area Update Tracking Area Update

Connection Re-activation
ECM-IDLE ECM-CONNECTED
(EMM- REGISTERED) (EMM-REGISTERED)
MME-initiated
Detach Connection Release
Attach
Detach
EMM-DEREGISTERED
29
RRC States
Tracking Area Update Tracking Area Update

Connection Re-activation
RRC-IDLE RRC- CONNECTED

(EMM- REGISTERED) (EMM-REGISTERED)
MME-initiated
Connection Release or
RL Failure
Idle Mode Tasks

Manual Mode Automatic mode
PLMN Selection
Indication
to user Location PLMNs
Registration available
response AvailableCSG IDs
to NAS
Support for manual
CSG ID selection
PLMN
selected CSG ID
selected
NAS Control
Cell Selection
and Reselection
Radio measurements
Registration
Area
changes
Service requests
Location
Registration
30
RRC_IDLE Cell Selection - Cell Reselection
go here whenever
a new PLMN is selected
cell information no cell information
stored for the PLMN 1 stored for the PLMN
Stored Information Initial
Cell Selection no suitable cell found Cell Selection
no suitable
Cell found
2
suitable cell found
Cell Selection when
leaving connected suitable cell found
Camped suitable cell found
mode
Normally
return to Leave Idle Mode
Idle Mode Selected PLMN
Suitable is rejected
trigger
Cell found go here
Connected When no USIM
Mode in the UE
Cell Reselection no suitable Any Cell
Evaluation Process Cell found Selection
no acceptable cell found USIM inserted
Cell Selection when Acceptable Acceptable

leaving connected Camped on Cell Found 1
Cell found
mode any cell
Suitable
Cell found 2
return to leave
Idle Mode Acceptable
Idle Mode trigger Cell found
Connected Mode
(Emergency calls only) Cell Reselection no acceptable
Evaluation Process Cell Found
RRC Procedures
› System information
› Cell Selection / Reselection TS 36.331
› Connection control
– Paging System Info Cell Paging Connected
– RRC connection establishment Aquisition Selection Reception Mode
– Security activation Mobility
RRC
– RRC connection reconfiguration RRC RB Measurement
– RRC connection re-establishment AS Security
Connection Management Reporting
– RRC connection release
– Radio link failure related actions
› Measurement Control
– Measurement configuration
– Measurement reporting
› Mobility Management
– Inter/Intra E-UTRA mobility
– Mobility from E-UTRA
– Handover to E-UTRA
› Other procedures
– DL Information Transfer
– UL Information Transfer
– UE capability transfer
– Protocol error handling
31
RRC Messages
› CounterCheck › RRCConnectionRequest
› CounterCheckResponse › RRCConnectionSetup
› CSFBParametersRequest › RRCConnectionSetupComplete
› CSFBParametersResponse › SecurityModeCommand
› DLInformationTransfer
› SecurityModeComplete
› HandoverFromEUTRAPreparationRequest
› SecurityModeFailure
› InterFreqRSTDMeasurementIndication
› SystemInformation
› LoggedMeasurementConfiguration
› SystemInformationBlockType1
› MasterInformationBlock
› UECapabilityEnquiry
› MBMSCounting Request
› MBMSCountingResponse › UECapabilityInformation
› MBSFNAreaConfiguration › UEInformationRequest
› MeasurementReport › UEInformationResponse
› MobilityFromEUTRACommand › ULHandoverPreparationTransfer
› Paging › ULInformationTransfer
› ProximityIndication
› RNReconfiguration › CSFBParametersRequestCDMA2000
› RRCConnectionReconfiguration › CSFBParametersResponseCDMA2000
› RRCConnectionReconfigurationComplete › HandoverFromEUTRAPreparationRequest
› RRCConnectionReestablishment (CDMA2000)
› RRCConnectionReestablishmentComplete › ULHandoverPreparationTransfer (CDMA2000)
› RRCConnectionReestablishmentReject
› RRCConnectionReestablishmentRequest
› RRCConnectionRelease
System Information
MASTER INFORMATION BLOCK (MIB)
SYSTEM INFORMATION 1
SYSTEM INFORMATION N
32
System Information Mapping (example)
MIB SIB1 SIB2 SIB3 SIB4 SIB5
SI-1 SI-2
BCCH BCCH BCCH
BCH DL-SCH DL-SCH
TTI= 40 TTI=80 TTI= 160 TTI= 320
PBCH PDSCH PDSCH
System information in MIB &

SIBs
MIB: DL BW, PHICH configuration, System frame number
System Parameters Related to SIB 1 SIB 2 SIB 3 SIB 4

Cell Selection Info x
PLMN-id x
Tracking Area Code x
Cell Id x
Cell Barred x
Frequency Band Indicator x
SIB Scheduling x
UL EARFCN x
UL Bandwith x
Common Radio Resource Conf x
Paging Info x
Cell Reselection x
Neighbouring Cells -intra frequency x
33
System information in more SIBs
S S S S S S S S S S S S
I I I I I I I I I I I I
System Parameters B B B B B B B B B B B B
Related to 5 6 7 8 9 10 11 12 13 14 15 16
Neighbouring Cells -
inter frequency x
Inter RAT reselection
(UTRA) x
(GRAN) x
(CDMA2000) x
home eNodeB x
ETWS notification x x
CMAS notification x
MBMS x x
GPS time and UTC x
EAB (extended
access baring) x
Re-reading of System Information
a) RRC_IDLE and RRC_CONNECTED - Paging

b) UE needs to reread SIB1 and check value tag
PCCH/PCH ”Paging: System Info Modification”
34
CN Initiated Paging
The MME sends the PAGING message to each eNode B
with cells belonging to the tracking area(s) in which the UE
is registered.
Each eNode B can contain cells belonging to different

tracking areas, whereas each cell can only belong to one
TA.
MME
UEs use DRx when in idle mode in order to wake at regular
intervals to check for paging messages.
The paging response back to the MME is initiated on NAS

layer and is sent by the eNB based on NAS-level routing
S1AP Paging message information.
TAC 2 TAC
1
RRC Paging message
CN Initiated Paging details

The MME initiates a paging message which is
sent to all eNodeBs in a tracking area(s)
MME
S1AP:Paging
RRC IDLE RRC: Paging
Random Access Procedure
RRC Connection Request
RRC Connection Setup
RRC Connection Setup Complete

(Service Request)
Initial UE Message (Service Request)
35
RRC Connection
MME
SIGNALLING RADIO BEARER 0
SIGNALLING RADIO BEARER 1

RRC S1 BEARER
Connection SIGNALLING RADIO BEARER 2
Signalling Connection
Signalling Radio Bearers (SRBs)
RRC
SRB0 SRB1 SRB2
PDCP
› Signalling Radio Bearers (SRBs) are offered by the PDCP layer to
the RRC layer for transport of RRC (and NAS) messages
– SRB0: Used for RRC messages on the CCCH

– SRB1: Used for RRC and NAS messages on the DCCH
– SRB2: Used for NAS messages, SRB2 has a lower-priority
than SRB1 and is always configured by E-UTRAN after
security activation.
36
RRC Connection Establishment
”RRC Connection Request” CCCH/ULSCH

RRC IDLE › RRC Connection Request is initiated by the
higher layers in the UE
DLSCH ”RRC Connection Setup”

› RRC Connection Setup
(C-RNTI is allocated in MAC layer)
”RRC Connection Setup Complete” DCCH/ULSCH

› RRC connection establishment procedure
RRC creates the signaling radio bearer RB#1,
CONNECTED
Establishment Cause
IE/Group Name IE type and reference

RRC Establishment Cause Emergency Call,
High Priority Access,
MT-Access,
MO-Signalling,
MO-Data,
Delay Tolerant Access
37
Security Related Procedures
MME
INITIAL CONTEXT SETUP REQUEST

(Integrity Protection Algorithm EIA;
Ciphering Algorithm EEA;
Security Key)
2. Decide Algorithms,
Derive Keys
Activate Security for SRB
SECURITY MODE COMMAND(EEA;EIA)
SECURITY MODE COMPLETE

INITIAL CONTEXT SETUP RESPONSE
UL/DL Information Transfer
RRC UL INFORMATION TRANSFER (NAS message)
RRC DL INFORMATION TRANSFER (NAS message)
38
UE Capability Transfer
MME
S1AP: Initial Context Setup Request

RRC UE CAPABILITY ENQUIRY
(UE Radio Capability)
RRC UE CAPABILITY INFORMATION
S1AP: UE Capability Info Indication
RRC Connection Reconfiguration
Purpose : modify an RRC Connection
RRC CONNECTION RECONFIGURATION
RRC CONNECTION RECONFIGURATION COMPLETE
It may convey:
› radio resource configuration (including RBs, MAC main configuration,
configuration of SCells for CA and physical channel configuration)
› associated dedicated NAS Information and security configuration.
› mobility control information (eg. order Handovers)
› measurement configuration (eg. setup/modify/release Measurements)
39
Measurement Configuration

(Measurement configuration)
MeasObject: The objects the UE shall perform measurements on e.g. EUTRAN, UTRAN, GERAN
cell information
ReportConfig:
Measurement reporting criteria: The criteria that trigger the UE to send a measurement report, e.g.
periodical or event-triggered reporting.
Trigger quantity: The quantity the UE shall measure (RSRP or RSRQ).
MeasId: Maps the Measurement Objects to Report Configurations
Measurement Reports (Event Triggered)

Events
Serving becomes better than

A1 Threshold
Serving becomes worse than
A2 Threshold
Neighbour becomes offset better
A3 than serving
threshold1 and neighbour
A5 becomes better than threshold2
Neighbour becomes offset better than
A6 Scell
Reporting
criteria Inter RAT neighbour becomes
fulfilled B1 better than threshold
RRC MEASUREMENT REPORT threshold1 and inter RAT
(Measurement Id, neighbour becomes better than
Primary cell measurement results, B2 threshold2
Neighbor measurement results)
40
UE Attach
eNodeB MME
1. System Information *
RRC IDLE Cell
Select *
2. Random Access Preamble
3. Random Access Response
4. RRC CONNECTION REQUEST
5. RRC CONNECTION SETUP
7. INITIAL UE MESSAGE (Attach Request
RRC 6.RRC CONNECTION SETUP COMPLETE(Attach Request+PDN Connectivity Req
+PDN Connectivity Req)
CONNECTED
8.RRC DL INFORMATION TRANSFER (UE Identity Request) DL NAS TRANSPORT (UE Identity Req)
9. RRC UL INFORMATION TRANSFER (UE Identity Response) UL NAS TRANSPORT (UEid Response)
10.RRC DL INFORMATION TRANSFER (Authentication Request) DL NAS TRANSPORT (Authentication)

11. RRC UL INFORMATION TRANSFER (Authentication Response) UL NAS TRANSPORT (Auth. Response)
12. RRC DL INFORMATION TRANSFER (Security Mode Command (IMEISV Req)) DL NAS TRANSPORT (NAS SMC)
13. RRC UL INFORMATION TRANSFER (Security Mode Complete) UL NAS TRANSPORT (NAS SMC)
15. RRC SECURITY MODE COMMAND 14. INITIAL CONTEXT SETUP REQUEST
(EPS bearers, Security, Attach Accept
16.RRC SECURITY MODE COMPLETE
+ Activate Default EPS bearer context request)
17. RRC UE CAPABILITY ENQUIRY
18. RRC UE CAPABILITY iNFORMATION
19. UE CAPABILITY INFO INDICATION
20. RRC CONNECTION RECONFIGURATION (Attach Accept, Bearer Setup) (UE Radio Capability)
21. RRC CONNECTION RECONFIGURATION COMPLETE
22. INITIAL CONTEXT SETUP RESPONSE
(EPS bearers)
23. RRC UL INFORMATION TRANSFER (Attach Complete UL NAS TRANSPORT (Attach Complete)
+ Activate Default EPS bearer context Accept) 24. UE CONTEXT RELEASE COMMAND
RRC IDLE
26. RRC CONNECTION RELEASE 25. UE CONTEXT RELEASE COMPLETE
Connection Reactivation
eNodeB MME
1. System Information *
Cell
RRC IDLE Select *
2. Random Access Preamble
3. Random Access Response
4. RRC CONNECTION REQUEST

RRC 5. RRC CONNECTION SETUP
CONNECTED
6. RRC CONNECTION SETUP COMPLETE (Service Request)
7. INITIAL UE MESSAGE (Service Request)
Optional Optional
8.RRC DL INFORMATION TRANSFER (Authentication Request) DL NAS TRANSPORT (Authentication)

9. RRC UL INFORMATION TRANSFER (Authentication Response) UL NAS TRANSPORT (Auth. Response)
10. RRC DL INFORMATION TRANSFER (Security Mode Command) DL NAS TRANSPORT (NAS SMC)
11. RRC UL INFORMATION TRANSFER (Security Mode Complete) UL NAS TRANSPORT (NAS SMC)
12. INITIAL CONTEXT SETUP REQUEST

13. RRC SECURITY MODE COMMAND (EPS bearers, Security, UECap Request)
14.RRC SECURITY MODE COMPLETE
15. RRC UE CAPABILITY ENQUIRY
Optional
16. RRC UE CAPABILITY iNFORMATION

17. UE CAPABILITY INFO INDICATION
(UE Radio Capability)
18. RRC CONNECTION RECONFIGURATION
(Bearer Setup,Measurement conf))
RRC 19. RRC CONNECTION RECONFIGURATION COMPLETE
CONNECTED 20. INITIAL CONTEXT SETUP RESPONSE
(EPS bearers)
41
Additional Default EPS Bearer
Establishment
-
eNodeB MME S-GW P-GW
UL INFO TRANSFER UPLINK DATA TRANSPORT

(NAS: PDN Connectivity
. Request (including specific APN)) Create Session Req Create Session Req
Create Session Resp Create Session Resp
E-RAB
- SETUP REQ
RRC CONNECTION RECONFIG (NAS: Activate Default EPS Bearer Context Request)
Establish DRBs, NAS message
RRC CONNECTION RECONFIG

COMPLETE E-RAB SETUP RESPONSE

NAS: Activate Dedicated EPS Bearer Context Accept
,
Dedicated EPS Bearer

Establishment
-
Create Bearer Req

.
Create Bearer Req
E-RAB
- SETUP REQ
RRC CONNECTION RECONFIG Bearer parameters,
Establish DRBs, NAS message NAS message : Activate Dedicated EPS Bearer Context Request


NAS message : Create Bearer Resp
Activate Dedicated EPS Bearer Context Accept
,
Create Bearer Resp
42
RRC Connection
Re-establishment procedure
› Without optional feature : “Multi-Target RRC

Connection Re-establishment”
› Only in serving cell with no ongoing procedure
› With optional feature: “Multi-Target RRC

Connection Re-establishment”
› in another cell with no ongoing procedure
› in any cell during ongoing X2 handover
› in source eNB during outgoing S1 handover
/SRVCC
› during RRC Connection Reconfiguration cases
Multi-Target RRC Connection

Reestablishment in an unprepared cell
Serving eNB PCI=A Target eNB 1 Target eNB 2 Target eNB 3
MME
RRC Connection ReestablishmentRequest

(PCI =A, C-RNTI…)
Context not
found
Lookup X2 related eNBs
that have a cell with PCI =A
Context Fetch Request

Context Fetch Response
Apply
UE Context
Context Fetch Response Accept
RRCConnectionReestablishment
RRCConnectionReestablishmentComplete
S1: Path Switch Request
S1: Path Switch Request Acknowledge
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
X2: Release UE Context
43
Carrier Aggregation PCell &
SCell(s)
PCell: Primary Cell
› RRC Connection establishment / (PCell)
re-establishment
› All L3 signaling in UL and DL
(RRC & NAS)
› Used for transmission of PUCCH
› Can only be changed at handover
Scell:
Secondary
› Configured by RRC Connection Cell (SCell)
Reconfiguration
› Can be activated/deactivated by
means of MAC Control Element
RRC Connection reconfiguration

for SCell configuration
Extract from 36.331
44
S1 Interface
Radio Control Plane User Plane
Network
Layer S1-AP User Plane
PDUs
Transport Transport Network Transport Network

Network User Plane User Plane
Layer
GTP-U
SCTP UDP
IP IP
Data link layer Data link layer
Physical layer Physical layer
S1AP: eNBMME Signaling

› E-RAB Management
› Initial Context Transfer Function
› UE Capability Info Indication Function
› Mobility Function for UEs in LTE_ACTIVE
› Paging
› S1 Interface Management Functions
› NAS signaling Transport between UE and MME
› S1 UE Context Release Function MME
› UE Context Modification Function
› Status Transfer
› Trace Function
› Location Reporting
› S1 CDMA 2000 Tunneling Function
› Warning Message Transmission Function
› RAN Information Management (RIM)
› Configuration Transfer function
45
S1AP Elementary Procedures,
class 1(1/2)
Elementary Initiating Message Successful Outcome Unsuccessful outcome
Procedure, class 1 Response Message Response Message
Handover Preparation HANDOVER HANDOVER HANDOVER

REQUIRED COMMAND PREPARATION FAILURE
Handover Resource Allocation HANDOVER HANDOVER REQUEST HANDOVER FAILURE
REQUEST ACKNOWLEDGE
Path Switch Request PATH SWITCH PATH SWITCH PATH SWITCH REQUEST
REQUEST REQUEST FAILURE
ACKNOWLEDGE
Handover Cancellation HANDOVER CANCEL HANDOVER CANCEL
ACKNOWLEDGE
E-RAB Setup E-RAB SETUP E-RAB SETUP
REQUEST RESPONSE
E-RAB Modify E-RAB MODIFY E-RAB MODIFY
REQUEST RESPONSE
E-RAB Release E-RAB RELEASE E-RAB RELEASE
COMMAND RESPONSE
Initial Context Setup INITIAL CONTEXT INITIAL CONTEXT INITIAL CONTEXT SETUP
SETUP REQUEST SETUP RESPONSE FAILURE

class 1(2/2)
Reset RESET RESET

ACKNOWLEDGE
S1 Setup S1 SETUP REQUEST S1 SETUP RESPONSE S1 SETUP FAILURE
UE Context Release UE CONTEXT UE CONTEXT

RELEASE COMMAND RELEASE COMPLETE
UE Context Modification UE CONTEXT UE CONTEXT UE CONTEXT
MODIFICATION MODIFICATION MODIFICATION
REQUEST RESPONSE FAILURE
eNB Configuration Update ENB ENB CONFIGURATION ENB CONFIGURATION
CONFIGURATION UPDATE UPDATE FAILURE
UPDATE ACKNOWLEDGE
MME Configuration Update MME MME MME
CONFIGURATION CONFIGURATION CONFIGURATION
UPDATE UPDATE UPDATE FAILURE
ACKNOWLEDGE
Write-Replace Warning WRITE-REPLACE WRITE-REPLACE
WARNING REQUEST WARNING RESPONSE
Kill KILL REQUEST KILL RESPONSE
46
Class 2 (1/2)
Elementary procedure, class 2 Initiating Message
Handover Notification HANDOVER NOTIFY
E-RAB Release Indication E-RAB RELEASE INDICATION
Paging PAGING
Initial UE Message INITIAL UE MESSAGE
Downlink NAS Transport DOWNLINK NAS TRANSPORT
Uplink NAS Transport UPLINK NAS TRANSPORT
NAS non delivery Indication NAS NON DELIVERY INDICATION
Error Indication ERROR INDICATION
UE Context Release Request UE CONTEXT RELEASE REQUEST
Downlink S1 CDMA 2000 Tunneling DOWNLINK S1 CDMA 2000 TUNNELING
Uplink S1 CDMA2000 Tunneling UPLINK S1 CDMA2000 TUNNELING
UE Capability Info Indication UE CAPABILITY INFO INDICATION
eNB Status Transfer ENB STATUS TRANSFER
MME Status Transfer MME STATUS TRANSFER
Deactivate Trace DEACTIVATE TRACE
Trace Start TRACE START

Class 2 (2/2)
Trace Failure Indication TRACE FAILURE INDICATION

Location Reporting Control LOCATION REPORTING CONTROL
Location Reporting Failure Indication LOCATION REPORTING FAILURE INDICATION
Location Report LOCATION REPORT
Overload Start OVERLOAD START
Overload Stop OVERLOAD STOP
eNB Direct Information Transfer ENB DIRECT INFORMATION TRANSFER
MME Direct Information Transfer MME DIRECT INFORMATION TRANSFER
eNB Configuration Transfer ENB CONFIGURATION TRANSFER
MME Configuration Transfer MME CONFIGURATION TRANSFER
Cell Traffic Trace CELL TRAFFIC TRACE
Downlink UE Associated LPPa Transport DOWNLINK UE ASSOCIATED LPPA TRANSPORT
Uplink UE Associated LPPa Transport UPLINK UE ASSOCIATED LPPA TRANSPORT
Downlink Non UE Associated LPPa Transport DOWNLINK NON UE ASSOCIATED LPPA
TRANSPORT
Uplink Non UE Associated LPPa Transport UPLINK NON UE ASSOCIATED LPPA TRANSPORT
47
E-RAB Modification procedure
List of RABs and corresponding

QoS Profile to be modified
aswell as an optional NAS
message per RAB
MME
E-RAB MODIFY REQUEST
RRC: Connection Reconf.

Contains a list of all successfully
RRC: Connection Reconf. complete
modified RABs and possibly a
list of all RABs that failed to be
E-RAB MODIFY RESPONS
modified
Includes the optional NAS

message ”Radio Modify Setup”
Note that this RRC procedure is
not always triggered
E-RAB Modify Request Description

IE/Group Name Presence Range IE type Semantics Criticality Assigned
and descriptio Criticality
reference n
Message Type M 9.2.1.1 YES reject
MME UE S1AP ID M 9.2.3.3 YES reject
eNB UE S1AP ID M 9.2.3.4 YES reject

UE AMBR
UE Aggregate O 9.2.1.20 YES reject
Maximum Bit Rate
E-RAB to be 1 YES reject
Modified List
>E-RAB To Be 1 to <maxnoof EACH reject
Modified Item IEs E-RABs>
>>E-RAB ID M 9.2.1.2 -
>>E-RAB Level QoS M 9.2.1.15 Includes -

QCI, ARP,
Parameters necessary
GBR/MBR
QoS
parameters
>>NAS-PDU M 9.2.3.5 -
48
E-RAB Modify Response Description
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 9.2.1.1 YES reject
MME UE S1AP ID M 9.2.3.3 YES ignore
eNB UE S1AP ID M 9.2.3.4 YES ignore
E-RAB Modify List 0..1 YES ignore
>E-RAB Modify Item IEs 1 to <maxnoof E- EACH ignore

RABs>
>>E-RABID M 9.2.1.2 -
E-RAB Failed to Modify O E-RAB List a value for E- YES ignore

List 9.2.1.36 RAB ID shall
only be
present once
in E-RAB
Modify List IE
+ E-RAB
Failed to
Modify List IE
Criticality Diagnostics O 9.2.1.21 YES ignore
MME Overload Control

MME
Overload =
Signaling load
> threshold
S1AP: Overload Start

IE: Overload action*
RRC Connection Request (Establishment Cause, S-TMSI)
RRC Connection Reject

(depending on S-TMSI, establishment cause & overload action) Overload resolved
Signaling load
<threshold
S1AP: Overload stop
Overload Action:
› Reject all RRC connection requests with establishment cause “mo-data”
› Reject all RRC connection requests with establishment causes “mo-data” and “mo-signaling”
49
X2 Protocol Model
Radio Control Plane User Plane
Network
Layer X2-AP User Plane
PDUs
Transport Transport Network Transport Network

Network User Plane User Plane
Layer
GTP-U
SCTP UDP
IP IP
Data link layer Data link layer
Physical layer Physical layer
X2AP: eNBeNB Signaling
Mobility Management
Load Management
Reporting of General Error Situations
Resetting the X2
Setting up the X2
eNodeB Configuration Update
50
X2AP Elementary Procedures,
class 1
HANDOVER PREPARATION HANDOVER HANDOVER REQUEST HANDOVER

REQUEST ACKNOWLEDGE PREPARATION
FAILURE
RESET RESET REQUEST RESET RESPONSE
X2 SETUP X2 SETUP REQUEST X2 SETUP RESPONSE X2 SETUP FAILURE

ENB CONFIGURATION ENB ENB CONFIGURATION ENB CONFIGURATION
UPDATE CONFIGURATION UPDATE UPDATE FAILURE
UPDATE ACKNOWLEDGE
RESOURCE STATUS RESOURCE STATUS RESOURCE STATUS RESOURCE STATUS

REPORTING INITIATION REQUEST RESPONSE FAILURE
Mobility Settings Change MOBILITY CHANGE MOBILITY CHANGE MOBILITY CHANGE

REQUEST ACKNOWLEDGE FAILURE
Cell Activation CELL ACTIVATION CELL ACTIVATION CELL ACTIVATION

REQUEST RESPONSE FAILURE
X2AP Elementary Procedures,

Class 2
LOAD INDICATION LOAD INFORMATION
HANDOVER CANCEL HANDOVER CANCEL
SN STATUS TRANSFER SN STATUS TRANSFER
UE CONTEXT RELEASE UE CONTEXT RELEASE
RESOURCE STATUS REPORTING RESOURCE STATUS UPDATE
ERROR INDICATION ERROR INDICATION
RADIO LINK FAILURE INDICATION RLF INDICATION
HANDOVER REPORT HANDOVER REPORT
51
GTP – GPRS Tunneling
Protocol
GTP GTP
Node A
GTP I/F
Node B
TEID=xxx TEID=yyy
Destination Port: GTP GTP TUNNEL GTP
GTPv2-C=2123 UDP UDP
IP Address = AAA
GTPv1-U=2152 IP IP
Protocol ID: IP Address = BBB
L1/L2 L1/L2
UDP=17
GTP TUNNEL
Identified in each node by:
[TEID, IP-addr, Port number]
UTRAN S12
S16 All interfaces are
GTPv2-C only, except:
SGSN
S4
MSC
Server S1-U, S12, X2
S3 (only GTPv1-U)
Sv
HRPD S11 S4, S5/S8 (both)
CDMA
PDSN
S102 MME
2000
S10
X2 S1-U SGW S5/S8 PGW
HRPD High Rate Packet Data GTP GPRS Tunneling Protocol

PDSN Packet Data Serving Node TEID Tunnel Endpoint Identifier
GTP-C v2: MMESGW PGW Signaling
MME PGW
› Path Management
› Tunnel Management
› Mobility Management
› CS Fallback and SRVCC related msgs
› Non 3GPP related msgs
MME
SGW
52
GTP-C Protocol Stack
GTP GTP
UDP UDP
IP IP
L2 L2
L1 L1
GTPv2 entit y GTPv2 entity

GTPv2 based
interface
GTP Message Types

Path Management
Message Type value (Decimal) Message Reference GTP-C GTP-U
0 Reserved
1 Echo Request X X
2 Echo Response X X
3 Version Not Supported X

Indication
4 to 24 Reserved for S101 TS 29.276 [14]

interface
25 to 31 Reserved for Sv TS 29.280 [15]
interface
53
Path Management Messages
› Echo Request
› Echo Response
MME PGW
ECHO Response
ECHO Request
ECHO Response
ECHO Request
T3-RESPONSE
T3-RESPONSE ECHO Request N3-REQUESTS
MME ECHO Response SGW/
N3-REQUESTS
T3-RESPONSE
N3-REQUESTS
GTP-C MME SGWPGW

Message Type value (Decimal) Message
SGSN/MME to PGW (S4/S11, S5/S8)
32/33 Create Session Request /Response

36/37 Delete Session Request / Response
34/35 Modify Bearer Request / Response
PGW to SGSN/MME/ePDG (S5/S8, S4/S11, S2b)
95/96 Create Bearer Request /Response
97/98 Update Bearer Request/Response
99/100 Delete Bearer Request/ Response
For the complete table see: TS 29.274
54
GTP-C v2: MMESGW PGW Signaling
Session Creation: PGW
› E-UTRAN Initial Attach
Create Session Request (QoS)

› UE requested PDN connectivity
S5/S8
GTP-C is also used to convey:
-Tracking Area Update procedure with Serving GW change
-S1/X2-based handover with SGW change
S11
-UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change
MME -GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change
SGW
Create
-3G Gn/Gp SGSN Session
to MME Request
combined (QoS)
hard handover and SRNS
relocation procedure
-Gn/Gp SGSN to MME Tracking Area Update procedure
Example: “Session creation” in

PDN Connectivity Scenario
-

(NAS: PDN Connectivity
. Request (including specific APN)) Create Session Req Create Session Req
Create Session Resp Create Session Resp
E-RAB
- SETUP REQ
RRC CONNECTION RECONFIG (NAS: Activate Default EPS Bearer Context Request)
Establish DRBs, NAS message


NAS: Activate Dedicated EPS Bearer Context Accept
,
55
› Explain the functions of the Access Stratum NAS protocol

› Describe the procedures in the NAS layer
› Explain the interaction between RRC and the lower layers in
the control plane
› Explain the RRC connected and idle modes (states)
› Explain the functions and services of RRC such as System
Information Broadcast, Paging, Cell Selection and Mobility
› Explain the main functions and procedures of X2AP signaling
protocol.
› Explain the main functions and procedures of S1AP signaling
protocol.
› Explain the main functions and procedures of the signaling
protocol GTP-C.
Thank You
56
LTE Protocols and
Procedures
PDCP, RLC, MAC and GTP-U Protocols
1. Explain the PDCP functions and services such as header compression
and ciphering.
2. Explain the RLC Functions
3. List different modes of RLC (transparent, unacknowledged and
acknowledged) and explain the structure of the PDU involved in these
cases
4. Explain the MAC functions such as HARQ, BCH Reception, PCH
Reception
5. Explain MAC Architecture, its entities and their usage for the mapping of
transport channels
6. List the content of the MAC Packet Data Unit (PDU).
7. Explain the main functions and procedures of the transport protocol
GTP-U
57
Packet Data Convergence Protocol
TS 36.323
› PDCP Services
– Transfer of user plane data
– Transfer of control plane data
– Header compression
– Integrity protection of control plane
– Ciphering both control and user plane
› PDCP Functions
– Header compression/decompression of IP data flows using ROHC
– Transfer of data
– Maintenence of SNs for radio bearers
– In sequence delivery of upper layer PDUs at re-establishment of lower layers
– Duplicate detection of lower layer SDUs at re-establishment of lower layers for radio
bearers mapped on RLC acknowledged mode
– Integrity protection/verification of CP
– Ciphering/deciphering of data
– Timer based discard
– Duplicate discarding
PDCP Architecture
TS 36.323
UE/E-UTRAN
PDCP-SAP PDCP-SAP Radio Bearers
C-SAP ... PDCP
PDCP entity PDCP entity
PDCP - PDU
RLC - SDU
...
RLC
RLC UM-SAP RLC AM-SAP
58
PDCP Entity
UE/E-UTRAN E-UTRAN/ UE
Transmitting Receiving
PDCP entity PDCP entity
TS 36.323
In order delivery and duplicate

Sequence numbering
Detection (U plane)
Header Compression Header Compression

(user plane only) (user plane only)
Packets associated
to a PDCP SDU
Packets NOT associated
to a PDCP SDU Packets associated
to a PDCP SDU
Packets NOT associated
to a PDCP SDU
Integrity Protection Integrity Verification

(control plane only) (control plane only)
Ciphering Deciphering
Add PDCP header Remove PDCP Header
Radio Interface(Uu)
Sequence Numbering
WHY: * Reordering
* Duplicate detection
* Integrity protection
* Ciphering
eNB
SRB1_UL SRB1_UL COUNT

COUNT
SRB1_DL SRB1_DL COUNT

COUNT
UE
UE Ctx
COUNT DRB_UL DRB_UL COUNT
COUNT DRB_DL DRB_DL COUNT
HOW:
PDCP SN:
HFN PDCP SN Next_PDCP_TX_SN
TX_HFN
COUNT
59
Header Compression
8
WHY: Saving the bandwith by V=4 Hlen TOS Packet length
Flags Fragment offset STATIC
HOW: *removing redundant info Identification
Protocol Checksum INFERRED
*Encoding important info IPv4 TTL
Source address CHANGES
*Hop to Hop Destination address
RARELY
*Unidirectional Source port Destination port
CHANGES
UDP OFTEN
Length Checksum
Appr. 30 of
V CC M PT Sequence no
40 octets are
RTP Timestamp static or easily
compressible!
SSRC Identifier
UE/UE Context
PDCP SDU
IP Header IP data RB_UL IP data RB_UL IP data IP Header
PDCP SDU
CRC
Compressed
checksum covering the header before
Header
compression is included in the compressed header UE/UE Context
Contains
encoded
data
Integrity Protection
WHY: To ensure data origin
Header
PDCP PDU PDCP SDU
PDCP PDU PDCP PDU

PDCP PDU PDCP PDU
PDCP SDU PDCP SDU
Header Header
COUNT COUNT
Direction
K_eNB_RRCInt
EIA MAC-I XMAC-I
EIA Direction
K_RRCInt
Bearer Id Bearer Id
MAC-I
= XMAC-I
Sending Side Receiving Side

UE/eNB UE/eNB
60
Ciphering
WHY: To protect the data over radio
EEA0
EEA1
EEA2
EEA3
COUNT DIRECTION COUNT DIRECTION
BEARER LENGTH BEARER LENGTH
KEYUPenc EEA KEYUPenc EEA
KEYSTREAM KEYSTREAM
BLOCK BLOCK
PLAINTEXT CIPHERTEXT PLAINTEXT

BLOCK BLOCK BLOCK
Sender Receiver
PDCP PDU
The PDCP Data PDU is used to convey:
› a PDCP SDU SN; and

› user plane data containing an uncompressed PDCP SDU; or
› user plane data containing a compressed PDCP SDU; or
› control plane data; and
› a MAC-I field for SRBs only
61
RLC Protocol Entity–Functions & Services
› RLC Services
TS 36.322
RLC Services provided to upper layers:
– Transparent data transfer
– Unacknowledged data transfer
– Acknowledged data transfer
RLC Services expected from lower layers:
– Data transfer
– Notification of a transmission opportunity
– Notification of HARQ delivery failure from transmitting MAC entity
› RLC Functions
– Segmentation, re-segmentation and assembly
– Concatenation
– Padding
– Transfer of user data in TM, UM and AM.
– Error correction (ARQ)
– In-sequence delivery
– Duplicate detection
– Flow control
– RLC Re-establishment
– Protocol Error Detection and Recovery
RLC Entities
upper layer (i.e. RRC layer or PDCP sub layer)
SAP between
upper layers
transmitting receiving transmitting receiving

TM RLC entity TM RLC entity UM RLC entity UM RLC entity
AM RLC entity eNB
logical
channel
lower layers
(i.e. MAC sub layer and physical layer)
radio interface
lower layers
(i.e. MAC sub layer and physical layer)
logical
channel
receiving transmitting receiving transmitting

TM RLC entity TM RLC entity UM RLC entity UM RLC entity
AM RLC entity UE
SAP between
upper layers
upper layer (i.e. RRC layer or PDCP sub layer)
62
RLC TM Entity
UE/ENB ENB/UE
radio interface
TM-SAP TM-SAP
TM-RLC TM-RLC
entity entity
Transmission
buffer
BCCH/PCCH/CCCH BCCH/PCCH/CCCH
RLC UM Entity
UE /ENB ENB /UE
radio interface
UM -SAP UM -SAP
Transmission SDU reassembly

buffer
UM -RLC UM -RLC
entity entity
Segmentation & Remove RLC header

Concatenation
Reception
Add RLC header buffer & HARQ
reordering
DTCH DTCH
63
RLC AM Entity
AM -SAP
Transmission
RLC control SDU reassembly
buffer
Remove RLC header

Segmentation & Retransmission
Concatenation buffer
Reception
buffer & HARQ
reordering
Add RLC header

Routing
DCCH /DTCH DCCH /DTCH
Protocol Data Units - PDU
› RLC Data PDU

– TM PDU, UM PDU, AM PDU and AMD PDU
Segment
› RLC Control PDU

– STATUS PDU
64
RLC Transparent Mode PDU
› The RLC TM PDU introduces no overhead
› TM is used for signaling on BCCH, PCCH and CCCH.
MAC Protocol Entity

Upper layers
PCCH BCCH CCCH DCCH DTCH MAC
-control
› MAC Services
Logical Channel Prioritization
(
– Data Transfer
(De-) Multiplexing Control
– Reallocation of resources HARQ Random
Access Control
› MAC Functions
– Mapping between logical channels and transport channels PCH BCH DL-SCH UL-SCH
Lower layer
RACH
– Multiplexing of MAC SDUs from one or different logical channels onto

transport block (TB) to be delivered to the physical layer on a transport
channel
– Demultiplexing of MAC SDUs from one or different logical channels
from transport block (TB) to be delivered from the physical layer on a
transport channel
– Scheduling information reporting
– Error Correction (HARQ)
– Priority handling between UEs by means of dynamic scheduling
– Priority handling between logical channels of one UE
– Logical channel prioritization
– Transport Format selection
65
MAC Structure, UE side
Upper layers
PCCH BCCH CCCH DCCH DTCH MAC-control
Logical Channel Prioritization (UL only)
(De-) Multiplexing Control
Random
HARQ
Access Control
PCH BCH DL-SCH UL-SCH RACH

Lower layer
MAC Structure, NW Side

MAC Control
CCCH DCCH DTCH DCCH DTCH CCCH PCCH BCCH
Scheduling / Priority
Scheduling / Priority Handling Handling
Scheduler
Control
Multiplexing Demultiplexing
HARQ
HARQ HARQ
PDCCH
PUCCH
SR
DL-SCH HARQ UL-SCH HARQ PCH BCH DL-SCH

Feedback Feedback
66
MAC Function Location
MAC function UE eNB Downlink Uplink
Mapping between logical channels and transport X X X

channels
X X X
Multiplexing X X
X X
Demultiplexing X X
X X
Error correction through HARQ X X X
X X X
Transport Format Selection X X X
Priority handling between UEs X X X
Priority handling between logical channels of one X X X
UE
Logical Channel prioritisation X X
Scheduling information reporting X X
Logical Channels – Control

› Broadcast Control Channel (BCCH)
– DL broadcast of system control information.
› Paging Control Channel (PCCH)
– DL paging information. UE position not known on cell level
› Common Control Channel (CCCH)
– UL/DL. When no RRC connection exists.
› Multicast Control Channel (MCCH)
– DL point-to-multipoint for MBMS scheduling and control, for one or
several MTCHs.
› Dedicated Control Channel (DCCH)
– UL/DL dedicated control information. Used by UEs having an RRC
connection.
67
Logical Channels - Traffic
› Dedicated Traffic Channel (DTCH)
– UL/DL Dedicated Traffic to one UE, user information.
› Multicast Traffic Channel (MTCH)
– DL point-to-multipoint. MBMS user data.
Transport Channels - DL
› Broadcast Channel (BCH)
– System Information broadcasted in the entire coverage area of the cell.
Beamforming is not applied.
› Downlink Shared Channel (DL-SCH)
– User data, control signaling and System Info. HARQ and link
adaptation. Broadcast in the entire cell or beamforming. DRX and
MBMS supported.
› Paging Channel (PCH)
– Paging Info broadcasted in the entire cell. DRX
› Multicast Channel (MCH)
– MBMS traffic broadcasted in entire cell. MBSFN is supported.
68
Transport Channels - UL
› Uplink Shared channel (UL-SCH)
– User data and control signaling. HARQ and link adaptation.
Beamforming may be applied.
› Random Access Channel (RACH)
– Random Access transmissions (asynchronous and synchronous). The
transmission is typically contention based. For UEs having an RRC
connection there is some limited support for contention free access.
Physical Channels and Signals

Physical channels
› Physical Downlink Shared Channel (PDSCH)
– transmission of the DL-SCH transport channel
› Physical Uplink Shared Channel (PUSCH)
– transmission of the UL-SCH transport channel
› Physical Control Format Indicator Channel (PCFICH)
– indicates the PDCCH format in DL
› Physical Downlink Control Channel (PDCCH)
– DL L1/L2 control signaling
› Physical Uplink Control Channel (PUCCH)
– UL L1/L2 control signaling
› Physical Hybrid ARQ Indicator Channel (PHICH)
– DL HARQ info
› Physical Broadcast Channel (PBCH)
– DL transmission of the BCH transport channel.
› Physical Multicast Channel (PMCH)
– DL transmission of the MCH transport channel.
› Physical Random Access Channel (PRACH)
– UL transmission of the random access preamble as given by the RACH transport channel.
Physical signals
› Reference Signals (RS)
– support measurements and coherent demodulation in uplink and downlink.
› Primary and Secondary Synchronization signals (P-SCH and S-SCH)
– DL only and used in the cell search procedure.
› Sounding Reference Signal (SRS)
– supports UL scheduling measurements
69
Channel Mapping
Downlink Uplink
PCCH MTCH MCCH BCCH DTCH DCCH CCCH DTCH DCCH CCCH
Logical Channels
“type of information”
MIB SIB (traffic/control)
PCH MCH BCH DL-SCH UL-SCH RACH

Transport Channels
“how and with what
characteristics”
(common/shared/mc/bc)
-Sched TF DL
-Sched grant UL -CQI
PDCCH -Pwr Ctrl cmd -ACK/NACK
info -HARQ info ACK/NACK -Sched req. Physical Channels
“bits, symbols,
PMCH PBCH PDSCH PCFICH PDCCH PHICH PUCCH PUSCH PRACH modulation, radio
frames etc”
-meas for DL sched
-meas for mobility -half frame sync -frame sync -measurements for
-coherent demod -cell id -cell id group -coherent demod UL scheduling
Physical Signals
“only L1 info”
RS P-SCH S-SCH RS SRS
MAC Procedures
› Random Access
› Maintenance of Uplink Time Alignment
› DL-SCH data transfer
› UL-SCH data transfer
› PCH reception
› BCH reception
› Discontinuous Reception (DRX)
› MAC reconfiguration
› MAC Reset
› Semi-Persistent Scheduling
70
Random Access (RA) Procedure
› Purpose
– Initial access
– Establish UL synchronization
– Indicate presence of UL data
› Two cases
– Contention-based
– Contention-free
› Consists of four phases (messages)
1.Random Access Preamble
2.Random Access Response
3.L2/L3 message
4.Contention Resolution
CBRA vs CFRA during

CBRA CFRA
UE eNB UE eNB
Random Access Preamble Random Access Preamble
1. (Randomly selected Preamble Id) 1. (Pre-allocated Preamble Id)
Random Access Response 2. Random Access Response 2.
3. RRC Connection Request 3. RRC Connection Request
RRC Connection Setup 4. RRC Connection Setup 4.
71
Initial Random Access
rach-Configuration {
preambleInformation { numberOfRA-Preambles n64 },
powerRampingParameters { powerRampingStep dB2,
preambleInitialReceivedTargetPower dBm-104 },
ra-SupervisionInformation { preambleTransMax n10,
ra-ResponseWindowSize sf4,
BCCH: System Information
mac-ContentionResolutionTimer sf48 }, RRC RRC
maxHARQ-Msg3Tx 1 },
PRACH: RACH preamble

UE randomly selects MAC MAC
one of the 64 preambles and send it based on
preambleInitialReceivedTargetPower PRACH: RACH preamble
MAC MAC RA-RNTI = 1+ t_id + 10f_id
MAC allocate TC-RNTI
If no answer is received within PDCCH: RA-RNTI; Scheduling Grant;TA
ra-ResponseWindowSize preamble is DL-SCH: RACH response
sent again based on MAC (RAPID; TC-RNTI); MAC
preambleInitialReceivedTargetPower + powerRampingStep
PUSCH: TC-RNTI
UL SCH: RA message3
If the UE sees its preamble, it CCCH: RRC Connection Request
RRC RRC
will respond with RRCConnectionReq (Initial UE identity, Cause) The TC-RNTI is "promoted" to a C-RNTI,
Including its 48 bit UE-id and Est. i.e. the same 16-bit value
Cause) allocated for TC-RNTI
The 40-bit MAC "UE contention resolution PDCCH: TC-RNTI; Scheduling Grant will continue to be used as C-RNTI
identity" is identical to the RRC Connection DL-SCH: C-RNTI; Contention ResolutionMAC after the random access procedure
MAC is successfully concluded.
Request sent in RA message 3.
RRC CCCH: RRC Connection Setup
RRC
(SRB1 parameters)
Use TC-RNTI to decode DL SCH. If the UE contention

resolution
identity MAC control element matches the RRC UL-SCH: C-RNTI; BSR
MAC MAC
connection request
message promote TC-RNTI to C_RNTI. DCCH: RRC Connection Setup Complete
RRC (Selected PLMN id, NAS: Attach Request *) RRC
Scheduling Request – Random Access

rach-Configuration {
preambleInformation { numberOfRA-Preambles n64 },
powerRampingParameters { powerRampingStep dB2,
preambleInitialReceivedTargetPower dBm-104 },
ra-SupervisionInformation { preambleTransMax n10,
ra-ResponseWindowSize sf4, BCCH: System Information •no PUCCH resources
mac-ContentionResolutionTimer sf48 }, RRC RRC
•no UL Synch (TAT is not running)
maxHARQ-Msg3Tx 1 },
•has repeated SR on PUCCH max no of times
UE randomly selects MAC MAC
one of the 64 preambles and send it based on
preambleInitialReceivedTargetPower
MAC MAC
RA-RNTI = 1+ t_id + 10f_id
If no answer is received within MAC allocate TC-RNTI
PDCCH: RA-RNTI; Scheduling Grant;TA
ra-ResponseWindowSize preamble is DL-SCH: RACH response
sent again based on MAC (RAPID; TC-RNTI); MAC
preambleInitialReceivedTargetPower + powerRampingStep
If the UE sees its preamable, it

will respond with Scheduling Request MAC PUSCH: C-RNTI MAC
UL SCH: msg3 (BSR,
by sending msg3 containing MAC
PHR)
control elements( BSR and/or PHR)
and identified by C-RNTI
PDCCH: C-RNTI; Scheduling Grant

MAC MAC
C-RNTI provides contention resolution
Use C-RNTI to decode DL SCH..

MAC UL-SCH: C-RNTI; BSR
MAC
RLC DTCH/DCCH:
Scheduled Unicast Transmission RLC
72
Contention Free Random Access
The CFRA can be used for:
›Incoming handover and
›PDCCH ordered UL re-synchronization (in case of DL data arrival for a UE that is out-
of-sync in UL, i.e. a UE whose time alignment timer has expired)
“Cell 1” ““Cell 2”
RRC: RACH-ConfigDedicated
PDCCH for DL
pUE1 data arrival
pUE2
› UE1 is assigned preamble pUE1 by means of RRC signalling via cell 1 which is the
serving cell of UE1
› UE2 is assigned preamble pUE2 directly via PDCCH.
Benefits
› Contention free random access can be used as random
access for cases when UE is RRC_CONNECTED, i.e.
› In a high RACH load scenario, the benefit can be
summarized as:
– It avoids contention by dedicating resources for UE to use for
random access.
– It reduces access latency
– reduces the interrupt time for handover and
– Reduces packet drops in user plane.
– reduced access delay
– reduced need for PRACH resources
73
HARQ Principle
- four multiple hybrid ARQ processes
Demultiplexed into logical channels and forwarded to RLC for reordering
TrBlk 1 TrBlk 2 TrBlk 0 TrBlk 5
Hybrid
Receiver processing Receiver processing
Receiver processing
ARQ Receiver processing
Receiver processing Receiver processing
processes Receiver processing Receiver processing
NAK ACK ACK ACK NAK ACK

NAK NAK
CFN0 1 2 3 4 5 6 7 8 9
TrBlk 0 TrBlk 1 TrBlk 2 TrBlk 3 TrBlk 0 TrBlk 4 TrBlk 5 TrBlk 3 TrBlk 0 TrBlk 4
1 ms TTI Fixed timing relation
HARQ and ARQ

RLC SDUs
BLER ~10-6
RLC
Sliding Window ARQ
UL ARQ UL ARQ
Transmitter Receiver
RLC PDUs RLC Status

RLC Status RLC PDUs
BLER ~10-4 to 10-3 BLER ~10-4 to 10-3 (DL HARQ data)
MAC
DL HARQ UL HARQ Stop and Wait HARQ
UL HARQ DL HARQ
Receiver Transmitter
Receiver Transmitter
BLER ~10-1 Transport Block +CRC

BLER ~10-1
Uplink L1
Downlink L1
74
Paging Reception and DRX cycle
› Paging channel (PCH) uses PDSCH transmission

› Paging indicated on PDCCH
– DRX cycle defined
– Special ‘paging MAC ID’ indicating paging group
– If ID matches  UE reads PDSCH to find which UE that is paged
PDCCH Possibility to page this terminal
UE receiver circuitry switched off UE receiver circuitry switched off

subframe
DRX cycle
BCH Reception
SFN-div-4 = 102 SFN-div-4 = 103

MIB MIB
Coding etc. Coding etc.
0 5 0 5 0 5 0 5 0 5 0
SFN=408 SFN=409 SFN=410 SFN=411 SFN=412

10 ms 10 ms
40 ms
75
DRX Operation A+D
A+D
DL Assignment + DL Data that will be ACKed
DL Assignment + DL Data that will be NACKed
G UL Grant
D UL Data following UL Grant that will be ACKed
DRX Cycle
Opportunity for DRX Opportunity for DRX

Inactivity Timer
(restarted)
On Duration
DL RX
Nack
ACK
A+D
A+D
A+D
Ack
G
HARQ RTT Timers DRX Retransmission Timer

(one per process) (if DL retransmission expected)
UL TX
Nack
Ack
Ack
D
Data Flow Through Air Interface

IP
IP MACHeader
MAC Header
IP
IP TCP
TCP Payload
Payload IP
IP TCP
TCP
via
viaS1
S1 or
orfrom
from 20B
20B 20B
20B e.g.
e.g.50
50Byte
Byte 20B
20B 20B
20B
•Payload
e.g.
Payload
• LCID
LCID(5
e.g.1460
1460Byte
Byte
(5bit)
bit)
UE’s
UE’s stack
stack RLCRadio
RLC
 RadioBearer
Bearerxx
•• Length
LengthField
Field(15
(15bit)
bit)
MACSDU
MAC
 SDUisis927
927Byte
Byte
PDCP
PDCP HH
~3B
HH
~3B
•• LCID
LCID(5
(5bit)
bit)
~3B ~3B
Header
HeaderCompression
Compression LCID==Padding
LCID Padding

&& Ciphering
Ciphering PDCP
PDCP PDCP
PDCP SDU
SDU PDCP
PDCP PDCP
PDCP
2B
2B 2B
2B •• …
…and
and77other
otherbits
bits PDU
PDU
RLC
RLC
RLC
RLC RLC PDCP Header
RLC SDU
SDU Segmentation
Segmentation
4B
4B
Segmentation
Segmentation • Sequence Number (12 bit)
concatenation
concatenation RLC
RLC
For ciphering, integrity protection RLC SDU
RLC SDU RLC
RLC
Concatenation
Concatenation
RLC Header
RLC Header 2B
2B
and during handover
PDU
PDU
•• Sequence
Sequence
• … Number
and
Number
4 other
(10 bits
(10 bit)
bit)
MAC
MAC ARQARQ Window
Windowsize
size==512
512 Multiplexing
Multiplexing (Padding)
(Padding)
MAC
MAC SDU
SDU (e.g.
(e.g.599
599Byte)
Byte)
MAC
MAC 1B
1B •• Framing
Framing Info
Info (2
(2 bit)
bit)
Multiplexing
Multiplexing 0:first
0:
 firstSDU
SDUstarts
MAC
starts
MAC here
here MAC
MAC
MAC
MAC SDU
SDU(e.g.
(e.g.927
927Byte)
Byte)
1:last
1:
 lastSDU 4B
4B not
SDUdoes
does notend
endhere
here PDU
PDU
•• …
… and
and 44 other
other bits
bits
L1
L1 RLC
RLC Framing
Framing Sub-Header
Sub-Header CRC
CRC
Transport
TransportBlock
Block
Coding,
Coding, •• Length
Length Indicator
Indicator (11
(11 bit)
bit) 3B
3B
Interleaving,
Interleaving,  Maximum
 Maximum SDUSDU size
size== 2048
2048Byte
Byte
Modulation
Modulation  First
 FirstSDU
SDU is
is55
55Byte
Byte
•• Extension
Extension bit
bit
76
L2 Structure for DL
Radio
Bearers
PDCP
RLC
Logical
channels
MAC
Transport
channels
L2 Structure for DL with

Carrier Aggregation
Radio
Bearers
PDCP
RLC
Logical
channels
MAC
Transport
channels
77
GPRS Tunneling Protocol for
the user plane (GTP-U)
Application N/w
IP IP
Relay Relay
PDCP GTP-U
PDCP GTP-U GTP-U
GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC L2 L2 L2 L2
L1 L1 L1 L1 L1 L1
LTE-Uu S1-U S5/S8 SGi

a
UE eNodeB Serving GW PDN GW
1. Explain the PDCP functions and services such as header compression
and ciphering.
2. Explain the RLC Functions
3. List different modes of RLC (transparent, unacknowledged and
acknowledged) and explain the structure of the PDU involved in these
cases
4. Explain the MAC functions such as HARQ, BCH Reception, PCH
Reception
5. Explain MAC Architecture, its entities and their usage for the mapping of
transport channels
6. List the content of the MAC Packet Data Unit (PDU).
7. Explain the main functions and procedures of the transport protocol
GTP-U
78
Thank You
79
LTE Protocols and
Procedures
Mobility
Explain Mobility in LTE
1. Explain the Intra-Frequency Handover (X2 and S1
Handover)
2. Discuss Coverage Triggered Session Continuity
3. Explain Inter-frequency Handover
4. Explain IRAT Handover
5. Describe CS Fallback
6. Discuss Single Radio Voice Call Continuity (SRVCC)
Handover to UTRAN/GERAN/CDMA1x
80
Mobility in RRC_Idle mode
› The eNodeB broadcasts idle mode information that assists
and controls the UE to select PLMN and best suitable LTE
cell.
› The UE performs tracking area updates when needed.

Otherwise no signaling between the UE and the Network,
except for the IRAT case.
› The user context (IP address etc) is maintained by the

EPC.
Mobility in RRC_CONNECTED mode

› Intra LTE Intra-frequency Handover
- Intra RBS Handover
- X2 based Inter RBS Handover
- S1 based Inter RBS Handover
› Coverage Triggered Session Continuity to
-WCDMA
-GERAN
-CDMA
-different LTE frequency
› Coverage triggered Handover
- Inter-frequency (Intra RBS, X2 or S1 HO)
- WCDMA IRAT
- Intra-LTE Inter-mode Handover (X2 or S1 HO)
› CS Fallback to GERAN / UTRAN / 1xRTT CDMA2000
› SRVCC Handover to UTRAN/GERAN
81
Intra and Inter eNodeB Handover
Intra eNB handover Inter eNB X2 handover Inter eNB S1 handover
MME SGW MME SGW
LTE NodeB
Mobility Schemes – X2 Handover
› Simplified mobility
MME SGW
scheme to handle the
most common scenario
› Forwarding of user data
on X2 interface (Selective
Forwarding)
LTE Node B
› After handover is
completed, EPC is
informed and the route is
LTE NodeB
X2
optimized
X2
LTE Node B
82
X2 Handover (basic scenario)
S-GW MME
Source eNB Target eNB
RRC 1. RRC CONNECTION RECONFIGURATION
CONNECTED (Bearer Setup,Measurement conf))
2. RRC Measurement Report

(Event A3)
3. HO
Decision
4. X2 HANDOVER REQUEST
5.Admission
TRELOCprep Control
6. X2 HANDOVER REQUEST
ACKNOWLEDGE
8. Start Data
7. X2 SN STATUS TRANSFER
forwarding
T304 10. RRC CONNECTION RECONFIGURATION
9. Buffer
(Handover Command,Measurement conf)
Forwarded
Regenerate Data
Security Keys 11 MAC: CFRA Random Access Preamble
12. MAC Random Access Response (UL allocation + TA)
13. RRC CONNECTION RECONFIGURATION COMPLETE
(Handover Complete) 14.Data Transfer in Target
15. S1 PATH SWITCH REQUEST
16. S5 USER PLANE
17.Data Transfer in Target UPDATE REQ
18. S5 USER PLANE
UPDATE RSPONSE
19. S1 PATH SWITCH RESPONSE
RRC 20. X2 UE CONTEXT RELEASE

21. Forward if any
CONNECTED Data in transition
and release
X2- Handover Request

IE/Group Name P IE type and reference
Message Type M Handover Request
Old eNB UE X2AP ID M eNB UE X2AP ID Integer (0..4095) Allocated at the source eNB
Cause M e.g Handover Desirable for Radio Reasons
Target Cell ID M ECGI; E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell
GUMMEI M Globally unique MME identity
UE Context Information
> MME UE S1AP ID M INTEGER (0..232 -1) MME UE S1AP ID allocated at the MME
> UE Security Capabilities M Encryption and Integrity Algorithms
>AS Security Information M KeNB; NextHop Chaining Count
> UE Aggregate Maximum Bit Rate M UE Aggregate Maximum Bit Rate Uplink/Dl
> Subscriber Profile ID for RAT/Frequency priority O (1..256)
>E-RABs To Be Setup List
>>E-RABs To Be Setup Item <1..maxnoof Bearers> maxnoofBearers = 256
>>> E-RAB ID M This IE uniquely identifies an E-RAB for a UE
>>> E-RAB Level QoS Parameters M QCI;ARP;GBR QoS (Max BitrateUL/DL;Guaranteed itrate UL/DL)
>>> DL Forwarding O indicates that the E-RAB is proposed for forwarding of downlink packets
>>> UL GTP Tunnel Endpoint M Transport Layer Address and GTP TEID;SGW endpoint of the S1 transport bearer. For delivery of UL
PDUs
> RRC Context M OCTET STRING; Includes the RRC Handover Preparation Information message
>Handover Restriction List O area roaming or access restrictions for handover
>Location Reporting Information O Event and Report Area
UE History Information M Last Visited Cell List
Trace Activation O E-UTRAN Trace ID; Depth; Ip to report
SRVCC Operation Possible O indicates that both the UE and the MME are SRVCC-capable
83
X2 Handover Request Ack
IE/Group Name P Range IE type and reference
Message Type M Handover Request Acknowledge
Old eNB UE X2AP ID M eNB UE X2AP ID; Allocated at the source eNB
New eNB UE X2AP ID M eNB UE X2AP ID Allocated at the target eNB
E-RABs Admitted List 1

> E-RABs Admitted Item 1 to <maxnoof
Bearers>
>> E-RAB ID M
>> UL GTP Tunnel Endpoint O GTP Tunnel Endpoint; Identifies the X2 transport bearer used
for forwarding of UL PDUs
>> DL GTP Tunnel Endpoint O GTP Tunnel Endpoint; Identifies the X2 transport bearer. used
for forwarding of DL PDUs
E-RABs Not Admitted List O E-RAB List

Target eNB To Source eNB Transparent Container M OCTET STRING; Includes the RRC E-UTRA Handover
Command message
RRC Container, extract

RRCConnectionReconfiguration message
RRCConnectionReconfiguration-r8-IEs {
measConfig
mobilityControlInfo
radioResourceConfigDedicated
securityConfigHO
MobilityControlInfo ::=
targetPhysCellId
carrierFreq O
carrierBandwidth O
additionalSpectrumEmission O
t304 ENUMERATED { ms50, ms100, ms150, ms200, ms500, ms1000,
ms2000, spare1},
newUE-Identity C-RNTI,
radioResourceConfigCommon
rach-ConfigDedicated ra-PreambleIndex INTEGER (0..63),
5 MHz
ra-PRACH-MaskIndex INTEGER (0..15)
CarrierBandwidthEUTRA ::= SEQUENCE {

dl-Bandwidth ENUMERATED { n6, n15, n25, n50, n75, n100}
ul-Bandwidth ENUMERATED {n6, n15, n25, n50, n75, n100}
CarrierFreqEUTRA ::=
dl-CarrierFreq
ul-CarrierFreq O
SecurityConfigHO ::=handoverType CHOICE {
intraLTE {
securityAlgorithmConfig O
keyChangeIndicator BOOLEAN,
nextHopChainingCount
},
interRAT {
securityAlgorithmConfig
nas-SecurityParamToEUTRA
84
S1 Path Switch Request
IE/Group Name P IE type and reference Semantics description
Message Type M PathSwitchRequest

eNB UE S1AP ID M The eNB UE S1AP ID uniquely identify the UE association
over the S1 interface within the eNB
E-RAB To Be Switched in Downlink List M
>E-RABs Switched in Downlink Item IEs
>> E-RAB ID M This element uniquely identifies a radio access bearer for a
particular UE, which makes the E-RAB ID unique over one
S1 connection. The E-RAB ID shall remain the same for
the duration of the E-RAB even if the UE-associated
logical S1-connection is released or moved using S1
handover.
>> Transport layer address M The Radio Network Layer is not supposed to interpret the
address information. It should pass it to the transport layer
for interpretation.
>> GTP-TEID M To deliver DL PDUs
Source MME UE S1AP ID M The MME UE S1AP ID uniquely identify the UE association
over the S1 interface within the MME.
E-UTRAN CGI M used to globally identify a cell
TAI M uniquely identify a Tracking Area
UE Security Capabilities M Encryption and Integrity Protection Algorithms
S1 Path Switch Request Acknowledge

IE/Group Name P IE type and reference Semantics
description
Message Type M PathSwitchRequestAck
MME UE S1AP ID M The MME UE S1AP ID uniquely identify the UE association over the S1 interface
within the MME.
eNB UE S1AP ID M The eNB UE S1AP ID uniquely identify the UE association over the S1 interface
within the eNB
UE Aggregate Maximum Bit Rate O The UE Aggregate Maximum Bitrate is applicable for all Non-GBR bearers per UE
which is defined for the Downlink and the Uplink direction and provided by the
MME to the eNB.
E-RAB To Be Switched in Uplink List O
> E-RABs Switched in Uplink Item IEs
>> E-RAB ID M This element uniquely identifies a radio access bearer for a particular UE, which
makes the E-RAB ID unique over one S1 connection. The E-RAB ID shall remain the
same for the duration of the E-RAB even if the UE-associated logical S1-connection is
released or moved using S1 handover.
>> Transport Layer Address M The Radio Network Layer is not supposed to interpret the address information. It
should pass it to the transport layer for interpretation.
>> GTP-TEID M This information element is the GTP Tunnel Endpoint Identifier to be used for the
user plane transport between eNB and the serving gateway
E-RAB To Be Released List O E-RAB List
Security Context M The purpose of the Security Context IE is to provide security related parameters to the One pair of
eNB which are used to derive security keys for user plane traffic and RRC signalling {NCC, NH} is
messages and for security parameter generation for subsequent X2 or intra eNB provided
Handovers, or for the security parameters for the current S1 Handover
85
DL Data Forwarding for AM
RLC end marker
S-GW
PDCP SN is continuous
through Handover
X2APNext SN = 7
Transmitter State 6 5 4
6 Source eNB Target eNB

5
Receiver State
4
Status:
6 ACK 4 & 5
5
4
› Source forwards outstanding un-ACK:ed SDUs to target with their SN.

› Source tells Target what PDCP SN to allocate next.
› Non-outstanding SDUs are forwarded (in order) without SN
› Target “prioritizes” forwarded SDUs.
› UE re-orders PDCP SDUs based on the SN.
› UE may submit a PDCP Status to guide Target re-Tx
› NO Data forwarding for SRBs; PDCP SN and HFN are reset @ target
Packet Forwarding for UM RLC

No PDCP SN information is
transferred to the target-eNB
*
PDCP SN and HFN are
reset at target-eNB
86
Mobility Schemes – S1 Handover
› S1 handover:
– Relocation of MME or
SGW
– Handover to UTRAN or
MME SGW MME SGW GSM
– Change of MME pool
area
› Signalling is done via
EPC and does not
assume the existance of
an X2 interface.
› Similar to inter-RAT
handover
› Forwarding of user data
LTE NodeB
either directly between
eNodeB or in-direct via
S-GW (Selective
Forwarding)
S1 Handover
S-GW MME MME
S-GW
Source eNB
Source eNB Target
Target eNB
eNB Source Target Source Target
RRC 1. RRC CONNECTION RECONFIGURATION
CONNECTED (Bearer Setup,Measurement conf))
2. RRC Measurement Report

(Event A3)
3. HO
Decision
4. S1 HANDOVER REQIRED
(Source to Target Transparent Container ) 5. S10 FORWARD RELOCATION
TS1RELOCprep REQUEST
6. S11 CREATE SESSION REQ/RES
7. S1 HANDOVER REQUEST
8. Admission
Control
9. S1 HANDOVER REQUEST ACKNOWLEDGE
10. S10 FORWARD RELOCATION
11. S11 CREATE BEARER REQ/RES RESPONSE
UP Forwarding
12. S1 HANDOVER COMMAND
13. RRC CONNECTION RECONFIGURATION
T304
(Handover Command,Measurement conf)
14 MAC: CFRA Random Access Preamble
Regenerate 15. MAC Random Access Response (UL allocation + TA)
Security Keys 16. RRC CONNECTION RECONFIGURATION COMPLETE
(Handover Confirm) 17. S1 HANDOVER NOTIFY
18.Data Transfer in Target
20. S1 UE CONTEXT RELEASE 19. S10 FORWARD RELOCATION

RRC
COMMAND COMPLETE/ ACK
CONNECTED
(Cause: Successful Handover)
87
Packet Forwarding at S1 Handover
Source TS 23.401
TS 36.300
Direct and Indirect Packet Forwarding
› Support for direct and indirect packet forwarding during

Intra-LTE S1 handover.
S-SGW T-SGW
Indirect
Direct
IP
S-eNB T-eNB
88
Limitations and Dependencies
Limitations
› No support for UL packet forwarding.
› Packet forwarding is currently only supported for intra LTE
handovers, not supported for IRAT handover.
› Indirect forwarding is not currently supported by the
Ericsson MME.
Dependencies
› Support needed in MME and SGW for indirect forwarding
› SGW needs support for IPv4 – IPv6 transition during S1
HO.
Source eNB Overview
89
Target eNB Overview
Interworking with 2G/3G

PMM_CONNECTED ECM - CONNECTED
Handover
GSM_Connected
CELL_DCH E-UTRA Handover
RRC_CONNECTED
GPRS Packet
transfer mode
CELL_FACH
Release
with Redirect CCO with
CCO,
CELL_PCH NACC
Reselection
URA_PCH
Connection Connection
Connection establishment/release establishment/release
establishment/release Reselection
Reselection
Reselection E-UTRA GSM_Idle/
UTRA_Idle
RRC Idle CCO, Reselection +
GPRS Idle
Reselection +
PMM_IDLE ECM -IDLE PDP context est*
PDP context est*
Cell change Cell change

without signaling without signaling
PMM_DETACHED EMM-DEREGISTERED Idle
* PDP Context establishment is needed if no PDP context exists
90
LTE to 3G Cell-reselection
PDN-GW
6
1a. Routing Area Update Request
7
1b. Routing Area Update Request
2. Context Request
S-GW 3. Context Response
5 4. Context Acknowledge
8 5. Update Bearer Request
2 4 6. Update Bearer Request
7. Update Bearer Response
SGSN MME 8. Update Bearer Response
9. Routing Area Update Accept
1b 3
10. Routing Area Update Complete
RNC
10
1a
Coverage triggered mobility

Session continuity
Blind release
with redirect (to
one of the candidate freq)
Only if QCI≠/1
FALSE
Release with
redirect (to freq
ueMeasurementActive=? reported by A5/B2)
a5B2MobilityTimer
Bad Coverage NO Event
RBS determines a REDIRECT
Event A2 set of candidate A3orA5/B2
frequencies Is there an IF/ WCDMA/ Serving worse than
TRUE
Serving cell IRAT/ Inter mode cell that threshold1 AND f2 mobilityAction=
worse than fully covers the source / IRAT/ inter mode ?
threshold cell? neighbor better
Event A1 than threshold2
HANDOVER
Good coverage
detected EUtranCellRelationTDD
YES (E)UtranCellRelation
externalUtranCellFDD
lac≠0 and lac≠-1
isHoAllowed=true
covTriggeredBlindHoAllowed=true
IF/IRAT/Inter mode HO
mobilityAction=HANDOVER Handover
coverageIndicator=covers
isHoAllowed=true
Blind
IF/IRAT/Inter mode HO
91
Coverage triggered session continuity to WCDMA
MME MME
RRC Connection Reconfiguration (Measurement conf)
(Measurement conf)
RRC Measurement Report
RRC Measurement Report (Event A2)
(Event A2)
Parameter
Parameter
ueMeasurementsActive
ueMeasurementsActive
= True
= False
RRC Connection Release RRC Connection Reconfiguration

UE Context Release (Measurement conf – event B2)
(redirection information) Request
RRC Measurement Report (Event B2)
UE Context Release
Command RRC Connection Release UE Context Release
UE context Release (redirection information) Request
complete UE Context Release
Com mand
RNC UE context Release
RRC SGSN
complete
RNC
CONNECTIONESTABLISHMENT
RRC
CONNECTIONESTABLISHMENT SGSN
ROUTING AREA UPDATE & SERVICE REQUEST
ROUTING AREA UPDATE & SERVICE REQUEST
LTE to 3G Handover – preparation phase

Source Target Source Target Source Target PDN
UE eNB RNC MME SGSN SGW SGW GW
1. Measurement Report
2. HandoverRequired 3. Forward Relocation Request

4. Create Session Request
4a. Create Session Response

5. RelocationRequest
5a. RelocationRequest Acknowledge
6. Create Indirect Data Forwarding Tunnel Request
6a. Create Indirect Data Forwarding Tunnel Response

7. Forward Relocation Response
8. Create Indirect Data Forwarding Tunnel Request

8a. Create Indirect Data Forwarding Tunnel Response
92
LTE to 3G Handover – execution phase
Source Target
Source MME Target SGSN Source SGW Target SGW PDN GW
UE eNB RNC
1. Handover Command
2. HO from EUTRAN Command
4a. Handover to UTRAN Complete
5. Relocation Complete
6. Forward Relocation Complete Notification
6a. Forward Relocation Complete Acknowledge

7. Modify Bearer Request
8. Modify Bearer Request
9. Modify Bearer Response 8a.Modify Bearer Response
10. Routing Area Update procedure
11. Delete Session Request

11b. Release Resources
11a. Delete Session Response
12. Delete Indirect Data Forwarding Tunnel Request

12a. Delete Indirect Data Forwarding Tunnel Response
13. Delete Indirect Data Forwarding Tunnel Request
13a. Delete Indirect Data Forwarding Tunnel Response
Coverage triggered Inter-Frequency

blind handover
MME
Source eNB
Source eNB Target eNB
Target eNB
RRC MEASUREMENT REPORT

(Event A2)
F2 LTE cell fully
covers f1 LTE cell
HANDOVER REQUEST
(HO PREPARATION INFORMATION)
HANDOVER REQUEST ACKNOWLEDGE

(Handover Command)
(Handover Command)
SN STATUS TRANSFER
MAC: CFRA Random Access Preamble

MAC Random Access Response (UL allocation + TA)

PATH SWITCH REQUEST
PATH SWITCH ACKNOWLEDGE

UE CONTEXT RELEASE COMMAND
UE CONTEXT RELEASE COMPLETE
93
Coverage triggered Inter-Frequency
handover (event A5)
MME
RRC MEASUREMENT REPORT Source eNB Target eNB
(Event A2)
(Measurement configuration – event A5)
Timer started –
expect eA5
(Event A5)
Measurement Report received, or
Timer expired
HANDOVER REQUEST
(HO PREPARATION INFORMATION)

(Handover Command)
(Handover Command)
SN STATUS TRANSFER

PATH SWITCH REQUEST
UE CONTEXT RELEASE COMMAND PATH SWITCH ACKNOWLEDGE
Intra-LTE Inter-Mode X2 Handover

Source eNB MME
Target eNB
Measurement Report (event A5)
Handover Request
Handover Request Acknowledge

(HO command)

( HO command )
SN Status Transfer

RRC Connection Reconfiguration Complete
(HO complete) Path Switch Request
Path Switch Request Acknowledge
UE context Release

( measurement configuration )
94
Intra-LTE Inter-Mode S1 Handover
MME
S-GW S-GW
Source eNB Target eNB Source Target
Measurement Report
(event A5) Handover Required
Create Session Request
Create Session Response

Handover Request
Handover Request Acknowledge
Handover Command
(HO Command)
eNB Status Transfer
MME Status Transfer

(HO Complete) Handover Notify

( measurement configuration )
UE Context Release Command
Delete Session Request
UE Context Release Complete
Delete Session Response
Non-Planned PCI Range

Introduction
HeNB
› List of ‘non-planned PCIs’

PCI x
can be defined per EUTRAN HeNB
frequency
› UE must report CGI and PCI x

handover is performed
over S1 HeNB
› HeNBs can be
PCI x
deployed with the
same PCI HeNB
PCI x
95
Non-Planned PCI Range
Handover Message flow
Target
HeNB GW
HeNB
MME
1. Configuration for Non-planned
PCI Range feature
2. Measurement Configuration for mobility ( Configure cellIndividualOffset for all Non-
(Intra-Freq: A3, Inter-freq: A3/A5) planned PCI)
Measurement
& evaluation
3. Measurement Reports for
mobility (A3/A5)
4. Check if the reported PCI is
within Non-planned PCI range
5. Measurement Configuration for CGI
reading (including DRX reconfigure)
6. Acquisition Broadcast System Information
Of CGI Information
7. Measurement Report including CGI Information
8. DRX reconfigure back to previous
9. Trigger S1 Handover
without neighbor relation
10. HANDOVER REQUIRED
(Target eNB-ID: Home eNB ID or
Macro eNB ID) 11. HANDOVER REQUEST
13. HANDOVER 12. HANDOVER REQUEST ACK.

14. RRC Connection Reconfiguration
COMMAND
15. RRC Connection Reconfiguration
Complete
CS Fallback
WHY?
Voice services needed but:
› IMS is not used as voice engine in the cell
› UEs not supporting VoLTE
Fallback triggered to overlapping CS domain (2G/3G or CDMA

2000)
LTE island
PS PS
LTE
LTE
LTE LTE
LTE
LTE
CS (+PS) LTE
LTE LTE
GERAN/UTRAN or CDMA 2000
96
CS Fallback flavors
› CS Fallback to GERAN and UTRAN
› PSHO-Based CS Fallback to UTRAN
› Measurement-Based CSFB Target Selection (GERAN &

UTRAN)
› CS Fallback for Dual-Radio UEs (CDMA 2000)
› CS Fallback to CDMA 2000
› Enhanced CS Fallback to CDMA 1X
› Emergency Call Handling for CS Fallback
UE Mode of Operation
CS/PS Mode1: PS Mode1:
Voice Centric
UE registeres to EPS UE registeres only to
services and non EPS EPS services
Services CS/PS and UE usage is voice
UE usage is voice centric PS Mode 1
centric
Mode 1
Voice Centric
CS fallback capable UE: A UE that uses a CS Fallback

CS infrastructure for a voice call and
other CS-domain services by falling back
to A/Gb or Iu mode if the UE is served by
E-UTRAN when a CS service is requested.
Data Centric
1x CS fallback capable UE: A UE that uses a

CS infrastructure for a voice call and other
CS-domain services by falling back to
CS/PS
cdma2000® 1x access network Mode 2 PS Mode 2
if the UE is served by E-UTRAN
when a CS service is requested. CS/PS
Mode2:
UE registeres to EPS PS Mode:
services and non EPS UE registeres
Data Centric only to
Services EPS services
UE usage is data centric UE usage is data centric
97
Attach Procedure to GERAN/
UTRAN before CS Fallback
MSS HSS
MME Server
RRC Connection Set up Procedure
RRC CONNECTION SETUP COMPLETE

(Attach Request)
EPS attach type IE:

001 EPS attach
010 combined EPS/IMSI attach
110 EPS emergency attach
111 reserved
Attach Procedure according to 23.401
Derive VLR number;

Allocate default LAI
LOCATION UPDATE REQ
Update Location in CS domain

LOCATION UPDATE ACCEPT
Attach Procedure according to 23.401
CS Fallback – Mobile Terminated Call

2. CS domain updated of subscribers
whereabouts through CS signaling
over MME-MSC (LUP, SMS etc.)
1. Subscriber registered in
MSC but roam in LTE CS signaling
Packet Core
LTE RAN
MME SAE Gw
4. Page over
CSFB SGSN GGSN
SGs-interface
Terminal
MSS
GSM / WCDMA RAN
RC
5. UE is informed
CSFB M-MGw MSC-S
and RAN triggers Terminal IM-MGw MGCF

MRFP
a release with
redirect 3. Incoming call to
payload
subscriber in LTE
6. Page response
and call setup over
2G/3G radio
98
CS Fallback - Mobile
Terminated Call (UE Active)
RNC/BSS MME MSC S/P-GW SGSN
1A. NAS CS Service Notification 1A. Paging Request
1A. Service Request

1b. NAS Extended Service Request
1c. CS Paging Reject
1d. UE Context Modification Request (CS fallback indicator)
1e. UE Context Modification Response
2. Optional Measurement Report Measurement-Based CSFB
Target Selection feature
3. RRC Connection Release (with Redirect)
4. UE Context Release Request
5. S1 UE Context Release & 6. UE changes RAT
7a.Suspend (see 23.060)
7b. Suspend Request / Response
8 Update Bearers
9. Paging Response
9a. Establish CS Connection
9b. Signalling Connection Release 9b. Connection Reject If the MSC is
changed
9c. Location Area Update or Combined RA/LA Update
CS Fallback - Mobile
Terminated Call (UE idle)
1c.Paging 1b. Paging 1a. Paging Request
1d. NAS Extended Service Request

1e. Service Request
1f. Initial UE context Setup
1g. Initial UE context Setup Response
2. Optional Measurement Report Measurement-Based CSFB

4. UE Context Release Request
5. S1 UE Context Release & 6. UE changes RAT
7a.Suspend (see 23.060)
8 Update Bearers
9. Paging Response
9a. Establish CS Connection
9b. Signalling Connection Release 9b. Connection Reject If the MSC is
changed
9c. Location Area Update or Combined RA/LA Update
99
CS Fallback – Mobile Originated Call
1a. Extended Service Request
1b. S1AP UE Context Modification Request message with CS Fallback Indicator
1c. S1AP UE Context Modification
e Response
2. Measurement Report Solicitation Measurement-Based CSFB
4. S1-AP: S1 UE Context Release
Request
5. S1 UE Context Release
6.UE changes RAT then LA Update or Combined RA/LA Update or LAU and RA
7a. Suspend (see 23.060)
8. Update bearer(s)
9. CM Service Request 9. A/Iu-cs message (with CM Service Request
)
10a. Service Reject
If the MSC
10b. Location Area Update is changed
10c. CS MO call
11. Routing Area Update or Combined RA/LA Update
PSHO-Based CS Fallback to
UTRAN – MO Call
MSC SGSN Serving PGW/
UE/MS eNodeB BSS/RNS MME
GW GGSN
1a. Extended Service Request
1b. S1-AP Request message with CS Fallback indicator
1c. S1-AP Response message
2. Optional Measurement Report
3a. PS HO (preparation phase and start of execution phase)
3b. Suspend
3c. Update Bearer(s)
4a. Location Area Update
4b. CM Service Request

4b. A/Iu-cs message (with CM Service
Request)
5. CM Service Reject 5. CM Service Reject
If the
MSC is
Location Area Update or Combined RA/LA Update
changed
6. CS call establishment procedure
7. PS HO (continuation of execution phase)
100
PSHO-Based CS Fallback to
UTRAN – MT Call
UE/MS eNodeB BSS/RNS MME MSC SGSN SGW P-GW/
GGSN
1a. Paging Request
1a. CS Paging Notification
1a. Service Request
1b. NAS Extended Service Request
1c. CS Paging Reject
1d. S1-AP UE Context Modification Request with CS Fallback indicator
1e. S1-AP UE Context Modification Response message
2. Optional Measurement Report Solicitation
3a. PS HO (preparation phase and start of execution phase)

3b. Suspend
3c. Update Bearer(s)
4a. Location Area Update

4b. Paging Response 4b. A/Iu-cs message (with Paging Response)
5a. Establish CS MSC is not changed

connection
5b. Signalling Connection Release 5b. Connection Reject
If the MSC
5b. Location Area Update or Combined RA/LA Update is changed
5c. CS call establishment procedure
6. PS HO (continuation of execution phase)
1x RTT CS Pre-Registration
over EPS Procedure
MME 1xCS 1xRTT/

IWS MSC
1. UE attaches to E-UTRAN
2. Decision to register
in 1xRTT CS
3. Service Request procedure if the UE is in idle state
4. 1xRTT CS registration request

4a. UL Inf Transfer 4b. S1 CDMA2000 4c. S102 Direct Transfer
Tunneling
5. Location update to
1x RTT CS Domain
6. 1xRTT CS registration response

6c. DL Inf Transfer 6b. S1 CDMA2000 6a. S102 Direct Transfer
Tunneling
101
CS MO Call Using Fallback to
CDMA 1x RTT Network
1xCS 1xRTT/
MME IWS MSC S/P-GW
1 UE is E-UTRAN attached and registered with 1xRTT
2 Decision to make a
MO Call in 1xRTT CS
3. Extended Service Request
4. S1 UE Context Modification
5. S1 UE Context Modification Resp
6. E-UTRAN triggers
RRC connection Release with redirection
8. Suspend notification
9. Suspend Acknowledge
11. 1x RTT MO call establishment
Enhanced CSFB to CDMA2000

1xRTT during MO Call
1xCS 1xRTT/
MME IWS MSC S/P-GW
1 UE is E-UTRAN attached and registered with 1xRTT
2 Decision to make a
MO Call in 1xRTT CS
3. Extended Service Request

4. UE Context Modification/Setup Request
5. UE Context Modification/Setup Response
6. RRC Con Reconfiguration(events B1,B2, cells and carrier frequencies)
7. Measurement Report (event B1orB2)

8.HOfromEUTRAPreparationReq
9. HOPreparationTransfer
10. UL S1 CDMA Tunneling
S102 Direct transfer and 1xMSC
interworking
11. DL S1 CDMA Tunneling
12. MobilityfromEUTRACommand
14. 1x RTT MO call establishment
102
SRVCC (Single Radio Voice
Call Continuity) Handover
Circuit
GSM
GSM switched
CORE
IMS/MMTEl
3G
Telephony
HSPA
WCDMA
Packet
Core
LTE
LTE
INTERNET
*QCI=1
LTE SRVCC handover
CS coverage
SRVCC Example case

3b. The MSS set up a call leg
to the SCC AS
Um / Uu SCC
BTS BSC MSS AS
NodeB RNC MGCF
GSM / WCDMA
4. The SCC AS finds
the anchored call
MMTel and executes
Sv
3a. The MSS and RAN session transfer
A
prepares to receive a
handover
B
5. The UE tunes MME
in to GSM or CSCF
WCDMA
1. UE sends
Measurement Report.
The eNodeB decides if
SRVCC HO is required S&P
eNodeB GW
LTE
2. The MME
handles the Signaling
SRVCC HO via
the Sv interface Voice media
CSCF: Call Session Control Function
MMTel: MultiMedia Telephony
103
IRAT SRVCC HO FROM
LTE/ EPC PERSPECTIVE
Ue eNB RNC MME MSC MSS IMS
Voice
Measurement
Report PS to CS Req
Handover Required
(A2 or B2)
(SRVCC HO Indication)
HO from
Preparation of target RAT
EUTRAN Handover Command
Command
IMS Service Continuity
GERAN/UTRAN Access Procedures L1/L2 interruption

Handover to UTRAN of 100-200 ms
complete
Relocation Complete
Voice
Signaling Overview M S C S e rv e r/ T a rg e t T a rg e t T a rg e t S G W /P G W IM S
UE S o u rce S o u rc e
E -U T R A N MME MGW M SC SGSN R N S /B S S
1 . M e a s u r e m e n t r e p o r ts
2 . D e c i s io n fo r H O
3 . H a n d o v e r R e q u ir e d
4 . B e a r e r S p li tt i n g
5 a . P S to C S R e q
5 b . P re p H O
Req 5 c . R e lo c /H O R e q
6 a . F o r w a r d R e lo c R e q
6 b . R e lo c / H O R e q
7 a . R e lo c / H O R e q A c k
7 b . F o r w a r d R e lo c R e s p
8 a . R e lo c /H O R e q A c k
8 b . P re p H O R e sp
8 c . E s t a b l is h c i r c u i t
9 . I n it i a ti o n o f S e s s io n T r a n s f e r ( S T N - S R o r E - S T N - S R )
1 2 . P S to C S R e s p
1 0 . S e s s io n t r a n s f e r a n d
13. H andover C om m and u p d a te r e m o t e le g
1 4 . H O fro m E U T R A N c o m m a n d
1 1 . R e le a s e o f I M S a c c e s s
le g
1 5 . U E tu n e s to
U T R A N /G E R A N
1 6 . H O D e te c t io n
1 7 a . R e l o c / H O C o m p le t e
1 7 b . S E S ( H O C o m p le t e )
17c. AN SW ER
1 7 d . P S to C S C o m p le te /A c k
1 7 e . D e le t e b e a r e r
1 7 f . T M S I R e a l l o c a t io n
HSS/
1 7 g . U p d a te L o c
HLR
1 8 a . R e l o c / H O C o m p le t e
1 8 b . F o r w a r d R e lo c C o m p l e t e / A c k
1 8 c . U p d a te b e a re r
1 8 e . R e le a s e R e s o u rc e s 1 8 d . D e le t e S e s s io n
1 9 . S u b s c r i b e r L o c a t io n R e p o r t
G M LC
From 23.216
(SRVCC stage 2)
104
Explain Mobility in LTE
1. Explain the Intra-Frequency Handover (X2 and S1
Handover)
2. Discuss Coverage Triggered Session Continuity
3. Explain Inter-frequency Handover
4. Explain IRAT Handover
5. Describe CS Fallback
6. Discuss Single Radio Voice Call Continuity (SRVCC)
Handover to UTRAN/GERAN/CDMA1x
Thank You
105
LTE Performance
Management and
Optimization
LTE Performance Management Introduction
After completion of this chapter the participants will be able to:

1. Explain the E-UTRAN Performance Management solution
1.1 Explain the E-UTRAN Optimization Solution
1.2 Describe how eNodeB counters are collected and stored
1.3 Describe the eNodeB counter types and structures
1.4 Explain briefly Quality of Service concepts in EPS
106
EPS Architecture Packet
Switched
Networks
EPS (Evolved Packet System) SGi

EPC (Evolved
Packet Core)
2G/3G Core Network Gx
HSS PGW PCRF
MME S10 S6a S5/S8

SGs
MSC-S
S11
S3 MME SGW
S4
SGSN S1-MME S1-U
E-UTRAN X2
(Evolved
LTE Uu
UMTS
Terrestrial
WCDMA/GSM eNodeB eNodeB
Radio
RAN Access X2 X2
Network ) eNodeB
Standardized QoS (TS23.203)

Packet Packet
QCI Resource Priority Delay Error Loss Example Services
Type Budget Rate
1 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video (Live Streaming)
3 GBR 5 300 ms 10-6 Non-Conversational Video
(Buffered Streaming)
4 3 50 ms 10-3 Real Time Gaming

5 1 100 ms 10-6 IMS Signalling
Voice,
6 7 100 ms 10-3 Video (Live streaming)
Non-GBR Interactive Gaming
7 6 10-6 Video (Buffered Streaming)
8 8 300 ms TCP-based (e.g., www, e-mail, chat, ftp,
9 9 p2p file sharing, progressive video, etc.
107
EPS Bearers
IMS Signaling (QCI 5) on Default Bearer
LTE QoS VoIP Traffic (QCI 1) on Dedicated Bearer
All other traffic (QCI 9) on Default Bearer
Dedicated Default
Bearer Bearer
Non-GBR GBR Non-GBR

QCI: Quality Class Indicator
APN: Access Point Name
QCI 5 - 9 QCI 1 - 4 QCI 5 - 9 AMBR: Aggregate Maximum Bit Rate
APN – AMBR GBR APN – AMBR UE: User Equipment
UE – AMBR MBR UE – AMBR TFT: Traffic Flow Template
TFT TFT APN ARP: Allocation Retention Priority
L-EBI: Linked EPS Bearer ID
ARP ARP IP Address GBP: Guaranteed Bit Rate
L-EBI L-EBI ARP MBR: Maximum Bit Rate
Default Bearer Establishment
NAS Activate Default

EPS Bearer Context
Request MME
S1AP Initial
Context GTP-C
Setup Create
Request Session
Request
eNodeB SGW PGW
108
Default Bearer (QCI 9)
EPS Bearer Context
Request EPS Bearer Identity : 5 MME
QCI : (9) QCI 9
Access Point Name Value : ltemobile.apn.mnc18.mcc240.gprs
PDN Address : 25.125.184.99
Maximum Bit Rate for Uplink : (254) Indicate higher than 8640 kbps
Maximum Bit Rate for Downlink : (254) Indicate higher than 8640 kbps
Guaranteed Bit Rate for Uplink : (255) 0 kbps
Guaranteed Bit Rate for Downlink : (255) 0 kbps
Maximum Bit Rate for Downlink (extended) : (247) 250 Mbps
Maximum Bit Rate for Uplink (extended) : (158) 100 Mbps
Radio Priority Level Value : (4) Priority level 4 (lowest)
APN AMBR for Downlink : 250000 kbps
APN AMBR for Uplink : 100000 kbps
Default Bearer (QCI 5)

EPS Bearer Context
Request EPS Bearer Identity : 6 MME
QCI : (5) QCI 5
Access Point Name Value : ims.mnc18.mcc240.gprs
PDN Address : 25.30.1.2
Maximum Bit Rate for Uplink : (247) 8192 kbps
Maximum Bit Rate for Downlink : (254) Indicate higher than 8640 kbps
Guaranteed Bit Rate for Uplink : (255) 0 kbps
Guaranteed Bit Rate for Downlink : (255) 0 kbps
Maximum Bit Rate for Downlink (extended) (100) 42 Mbps
Maximum Bit Rate for Uplink (extended) : Use the value indicated by …
Radio Priority Level Value : (1) Priority level 1 (highest)
APN AMBR for Downlink : 42000 kbps
APN AMBR for Uplink : 8192 kbps
109
Dedicated Bearer Establishment
NAS Activate Dedicated

EPS Bearer Context
Request MME
S1AP
E-RAB GTP-C
Setup Create
Request Bearer
Request
eNodeB SGW PGW
Dedicated Bearer (QCI 1)

NAS Activate Dedicated
EPS Bearer Context
MME
Request EPS Bearer Identity : 7
Linked EPS Bearer Identity Value : (6) EPS bearer identity value 6
QCI : (1) QCI 1
Maximum Bit Rate for Uplink : 30 kbps
Maximum Bit Rate for Downlink : 30 kbps
Guaranteed Bit Rate for Uplink : 30 kbps
Guaranteed Bit Rate for Downlink : 30 kbps
TFT Operation Code : (1) Create new TFT
Number of Packet Filters : 4
Packet Filter Identifier : 16
Component Type : (16) IPv4 source address type
Address : 10.133.144.22
Radio Priority Level Value : (1) Priority level 1 (highest)
110
EUTRAN Evolution
Business Plan
Performance Management
& Optimization Radio Network
Design
Commercial Site
Launch Acquisition
Site
Initial Tuning
Engineering
Civil
Integration
Works
Installation
RAN Services
Drive Test Radio Network Statistics
Initial Tuning Optimization
• Antenna azimuth and/or downtilt changes • Parameter changes

• Other network configuration changes • Other network configuration changes
111
LTE Performance Statistics
Performance Monitorings (PMs) Subscription Profiles
(also called ‘scanners’)
System Defined
System Defined To collect counters required for the
Created by the System Defined Subscription predefined reports. (Primary for eNodeB)
Profile (Primary for ENodeB)
User Defined
User Defined Created by a user to collect counters not
Created by the User Defined Subscription Profile contained in the predefined profile.
PMS file system

OSS-RC
Stats.xml
Stats.xml.gz
eNodeB
eNodeB Statistics Storage

Parameters
ManagedElement
+-SystemFunctions
+-PmService
maxNoOfCounters = 65000 {10000..350000}
maxNoOfMonitors = 10 {1..30}
maxNoOfPmFiles = 200 {10..200}
performanceDataPath = /c/pm_data/
112
LTE Performance Recording
Performance Monitorings (PMs) Subscription Profiles
(also called ‘scanners’)
User Defined
User Defined Created by a user to collect events and
Created by the User Defined Subscription Profile radio related measurements applicable to
either a particular UE or cell
Trace
LTE UE Trace PMS file system
OSS-RC Recording.bin
LTE Cell Trace

eNodeB Recording.bin.gz
LTE Performance Data Analysis

BIS: Business Intelligence Server
Business Objects WAS: Windows Application Server

BIS WAS
Reports
Predefined Reports Predefined Reports User defined Reports

Sybase IQ Data
Warehouse
ENIQ
OSS-RC
PMS file system
OSS-RC Stats.xml
eNodeB
Stats.xml.gz
113
Optimization Solution
Data Engineer Performing Improved
Inputs Optimization KPIs
PM Statistics Accessibility
Network Optimization Activities
(Analysis ofStatistics, Logs and/or Drive
Knowledge of
Tests)
how the Retainability
System works
Periodical Reports
Preparation of
Integrity
Tools
Requirements Mobility
Corrective Actions
Performance
Management
EUTRAN Observability
Model
Key Performance Indicator (KPI) level End-user
Perception
Performance Indicator (PI) level
Procedure level
System
Characteristics
114
EUTRAN KPIs and PIs
Optimization Workflow
Preparation Analysis
Collection of Recommendation/
PM (Stats) Execution
Verification:
No Performance
Acceptable?
Yes
Performance
Management
115
EUTRAN Counter Name
<pm><Measurement Family><Counter Specific><Filter><Cause>
pm Mandatory prefix to differentiate counters from other objects in the Managed Object Model (MOM).
Measurement Family Describes the measurement level, for example, RRC, PDCP and so on.
Counter Specific Describes the measurement for the counter and could be divided into three subparts, as follows:
<Operation><Reason/Result><Direction>
The Operation subpart is establishment, modification or termination
The Reason/Result subpart is attempt, failure, success, throughput, volume and so on
The Direction subpart is UL/DL or Incoming/Outgoing
Filter Describes the filter that has been applied to the measure, for example Max (maximum)
Cause Describes the cause for the reason or the result of the operation, for example, if the counter registers
when an RRC message is deleted due to failed integrity check, the Cause sub-name would be
Integrity.
Example: pmErabEstabSuccAdded
This counter counts the total number of successfully added E-RABs per
cell. Added E-RABs are all E-RABs present in the S1 message E-RAB
Setup Request.
Peg Counter
HOTEL ROLL
Count at end of ROP:
Peg
pmGuestsIn = 0
7
6
5
4
3
2
1
To OSS
116
Gauge Counter
HOTEL ROLL
Gauge
pmGuestsInGauge = 0
5
4
3
2
1
To OSS
Accumulator and Scan

Counters
Accumulator 27
HOTEL ROLL Average =
Scan
=
3
=9
Accumulator and Scan
Accumulator counter:
pmSumSampGuests= 27
16
0
7 Sample
Scan counter:
pmNoOfSampGuests= 0
3
2
1 Sample
To OSS
morning afternoon evening
117
Probability Density Function
HOTEL ROLL Sample every
3 minutes

PDF
Scan “counter in range”
pmNoOfGuests[0] 0
1 Sample

pmNoOfGuests[1-10] 0
3
2
1 Sample

pmNoOfGuests[11-25] 0
1 Sample
Normal: 0, 0, 0, 0, 0, 3, 0, 0, 0, 22, 0
To OSS Compressed: 2, 5, 3, 9, 22
Counter Type Examples

PEG: pmErabEstabAttInit
The total number of initial E-RAB Establishment attempts.
Example: 652 652 ERAB Establishment attempts
GAUGE: pmErabMax
The peak number of simultaneous E-RAB usage.
Example: 73 A peak of 73 simultaneous ERABs
EUtranCellFDD
ACC: pmErabLevSum eNodeBxx
The peak number of simultaneous E-RAB usage.
Example: 7080
SCAN: pmErabLevSamp Average number of
Counts the number of times the corresponding
ERABs =
Sum counters has been incremented.
7080/180 = 39.33
Example: 180
Compressed: pmErabEstabAttInitQci
PDF The total number of initial E-RAB setup attempts per QCI
Example: 3,1,1,5,207,9,444 One attempt to establish a QCI 1 ERAB
207 attempts to establish a QCI 5 ERAB
444 attempts to establish a QCI 9 ERAB
Total = 1 + 207 + 444 = 652
118
EUTRAN Counter Descriptions
MME Triggered UE Context

Release
UE context release is triggered UE Context release
by UE context release command RBS MME
command
pmUeCtxtRelMme +
No Data in UL or DL
buffer?
Yes
pmUeCtxtRelMmeAct +
UE Context
RBS MME
release complete
End of
UE context release
119
The participants should now be able to:

1. Explain the E-UTRAN Performance Management solution
1.1 Explain the E-UTRAN Optimization Solution
1.2 Describe how eNodeB counters are collected and stored
1.3 Describe the eNodeB counter types and structures
1.4 Explain briefly Quality of Service concepts in EPS
Thank You
120
LTE Performance
Management and
Optimization
LTE Accessibility Optimization

2. Measure LTE Accessibility performance
2.1 Describe the Random Access procedure
2.2 Describe the E-RAB setup procedure and associated counters
2.3 Use eNodeB counters to create E-RAB Accessibility KPIs
2.4 Explain the eNodeB parameters and features that influence
Accessibility
121
Random Access Procedure
ManagedElement
+-ENodeBFunction
RA Preamble Assignment +-EUtranCellFDD
0
cfraEnable = TRUE
Random Access Preamble CFRA

1
Used for incoming
handover and PDCCH
Random Access Response
2 ordered uplink re-sync.
CBRA
Used for Scheduled Transmission (MSG3)
3
initial E-RAB HARQ
establishment
process. Contention Resolution (MSG4)
4
HARQ
Uplink Open Loop Power

Control
preambleInitialReceivedTargetPower = -110 { -120..-90 } [Unit: 1 dBm]
PREAMBLE _ RECEIVED _ TARGET _ POWER  preambleInitial Re ceivedT arg etPower   PREAMBLE 

PREAMBLE _ TRANSMISSION _ COUNTER  1 powerRampingStep
1) UE measures RS
Connection
established
with minimum
3) The power is ramped up until a interference
response is heard or maximum to other cells
number of re-attempts is reached
122
Contention Based Random
Access Success Rate
pmRaSuccCbra The number of successfully detected RA Msg3 for CBRA

pmRaAttCbra The number of detected contention-based random access preambles
pmRaUnassignedCfraFalse The number of detected Contention Free Random Access preambles
that are not allocated to any UE
pmRaUnassignedCfraSum The total number of unassigned Contention Free Random Access
preambles at each PRACH occasion during the reporting period.
pmRaFailCbraMsg2Disc The number of CBRA preambles for which no random access
response (RA Msg2) was sent due to expiration of the random
access response window.
pmRaFailCbraMsg1DiscSched The number of CBRA preambles that are discarded because
maximum number of RA Msg3 are already scheduled.
pmRaFailCbraMsg1DiscOoc The number of CBRA preambles that are discarded because timing
offset of CBRA preamble corresponds to a distance greater than
configured cell range.
Overshooting Cell
cellRange ManagedElement
+-ENodeBFunction
+-EUtranCellFDD
cellRange = 15 { 1..100 }
[Unit: 1 km]
pmRaFailCbraMsg1DiscOoc
Incremented for each preamble that is discarded because it
was detected from a UE outside the configured cell range.
The ‘Maximum Cell Range’ (FAJ 121 0869) optional feature is

required to support cell ranges >15 km.
123
Uplink Interference
pmRadioRecInterferencePwr:
0,139,457290,272646,84684,33072,17023,11251,8475,3359,10791,1112,146,12,0,0
pmRadioRecInterferencePwr
Low Interference The measured Noise and

Interference Power on PUSCH,
according to 36.214
PDF ranges:
[0]: N+I <= -121
[1]: -121 < N+I <= -120
[2]: -120 < N+I <= -119
[3]: -119 < N+I <= -118
[4]: -118 < N+I <= -117
pmRadioRecInterferencePwr: [5]: -117 < N+I <= -116
0,0,0,0,0,0,0,0,0,0,0,0,0,0,585400,314600 [6]: -116 < N+I <= -115
[7]: -115 < N+I <= -114
[8]: -114< N+I <= -113
[9]: -113 < N+I <= -112
[10]: -112 < N+I <= -108
High Interference [11]: -108 < N+I <= -104
[12]: -104 < N+I <= -100
[13]: -100 < N+I <= -96
[14]: -96 < N+I <= -92
[15]: -92 < N+I
Unit: 1 dBm/PRB
RACH Root Sequence

Planning
Poor Random Access
Success Rate
rachRootSequence = 50
rachRootSequence = 0 rachRootSequence = 60 rachRootSequence = 90
rachRootSequence = 10 rachRootSequence = 70
rachRootSequence = 80 rachRootSequence = 110
124
Automated RACH Root
Sequence Allocation
› Semi-Static Root Sequence Allocation
› Root Sequence Index (for non-high Speed cells) may be
choosen [0,837]
› PCI based selection: RS  (( PCI  PLSCI  8) mod PCI )  N RS 
 
 N PCI 
› PLCIG:=physicalLayerCellIdGroup [0..167] RSI = 0

PCI = 0
› PLSCI:=physicalLayerSubCellId [0,1,2] RSI = 2
PCI = 1
› PCI= PLCIG * 3 + PLSCI RSI = 3
PCI = 2
RSI = 544 RSI = 95
› NRS=838, PCI = 327 PCI = 57
RSI 547 RSI 96
› NPCI=504 PCI 329
RSI 98
PCI = 58
RSI 545
PCI=328 PCI = 59
EUTRAN Accessibility KPIs

The ability of a user to obtain a
requested service from the system
Initial E-RAB Establishment Success Rate [%]:

RRC Success S1 Success E-RAB Success X 100
= X X
RRC Attempts – RRC Reattempts S1 Attempts E-RAB Attempts
125
RRC
Idle
Mode
RRC CONNECTION REQUEST
pmRrcConnEstabAtt +
SRB 0 RRC CONNECTION REQUEST

pmRrcConnEstabAttReatt +
RRC CONNECTION SETUP Information needed to

set up SRB 1 on DCCH.
Connected
Mode

SRB 1 pmRrcConnEstabSucc +

Failure Counters
CUL
exceeded or Yes
hard limit
pmRrcConnEstabFailLic +
reached?
No
Active Users
Yes
license pmRrcConnEstabFailLicActiveUsers +
exceeded?
No
MP Load pmRrcConnEstabFailHighLoad +
Yes
high or or
Overload?
pmRrcConnEstabFailOverload +
No
RAC-BB
signal queue
Yes pmRrcConnEstabFailMISigQCong +
Congestion?
No
MME Yes pmRrcConnEstabFailMmeOvlMos +
Overload? or
pmRrcConnEstabFailMmeOvlMod +
No
126
S1 Signalling Connection
Establishment
RRC S1AP
MME

Piggybacked NAS ’Attach Request’
INITIAL UE MESSAGE
pmS1SigConnEstabAtt +
Contains NAS ’Attach Request’
DOWNLINK NAS TRANSPORT

pmS1SigConnEstabSucc +
Contains NAS UE identity Request’
DL INFORMATION TRANSFER
Contains NAS UE identity Request’
logical S1 connection
S1 Signalling Connection
Establishment Failure Counters
RBS timeout
on initial context Yes
setup No Counter
request from
MME?
No
MME
overload ? Yes
(Mobile originating pmS1SigConnEstabFailMmeOvlMos +
Signalling)
No
127
Initial E-RAB Establishment
RRC S1AP
MME
Authentication and security mode procedures

pmErabEstabAttInit + INITIAL CONTEXT SETUP REQUEST
pmErabEstabAttInitQci + Includes a list of E-RABs to be setup

Contains information needed to set up RB
RRC CONNECTION
RECONFIGURATION COMPLETE
pmErabEstabSuccInit + INITIAL CONTEXT SETUP RESPONSE
pmErabEstabSuccInitQci +
Initial E-RAB Establishment

Failure Counters
Licence
for number of
E-RABs per user/ Yes
pmErabEstabFailInitLic +
License for RLC UM
Exceeded?
No
DL/UL pmErabEstabFailGbrDlEnb +
Yes
GBR resource or
overload? pmErabEstabFailGbrUlEnb +
No
128
E-RAB Addition
RRC S1AP
MME
pmErabEstabAttAdded + E-RAB SETUP REQUEST
pmErabEstabAttAddedQci + Includes a list of E-RABs to be setup

Contains information needed to set up RB
RRC CONNECTION
RECONFIGURATION COMPLETE
pmErabEstabSuccAdded + E-RAB SETUP RESPONSE
pmErabEstabSuccAddedQci +
E-RAB Addition Failure

Counters
Licence Yes
for number of
E-RABs per user/ pmErabEstabFailAddedLic +
License for RLC UM
Exceeded?
No
Yes
DL/UL pmErabEstabFailGbrDlEnb +
GBR resource or
overload? pmErabEstabFailGbrUlEnb +
No
129

2. Measure LTE Accessibility performance
2.1 Describe the Random Access procedure
2.2 Describe the E-RAB setup procedure and associated counters
2.3 Use eNodeB counters to create E-RAB Accessibility KPIs
2.4 Explain the eNodeB parameters and features that influence
Accessibility
Thank You
130
LTE Performance
Management and
Optimization
LTE Retainability Optimization

3. Measure LTE Retainability performance
3.1 Describe the E-RAB release procedure and associated
counters
3.2 Use eNodeB counters to create E-RAB Retainability KPIs
3.3 Explain Radio Connection Supervision
3.4 Explain the parameters and features that influence
Retainability
131
EUTRAN Retainability KPI
X
The ability of user to retain its requested service
once connected for the desired duration
E-RAB Retainability [%]:
ENB Abnormal E-RAB releases+ MME Abnormal E-RAB releases
= X100
Total releases
UE Session Time
pmSessionTimeUe +
Data
Transfer
in session out of session in session
100 msec 100 msec
Time
132
MME Initiated E-RAB
Release
RRC S1AP
MME
E-RAB RELEASE COMMAND
Includes a list of E-RABs to be released
Normal release pmErabRelMme +
Abnormal release pmErabRelAbnormalMme +
Data buffers OR pmErabRelAbnomalMmeAct +

UL DL
All resources for the E-RAB are released
(DRB and S1 Bearer)
E-RAB RELEASE RESPONSE
Includes a list of released E-RABs
RBS Initiated E-RAB Release

RRC S1AP
MME
Normal release pmErabRelNormalEnb +
Abnormal release pmErabRelAbnormalEnb +
Data buffers OR pmErabRelAbnormalEnbAct +

UL DL
All resources for the E-RAB are released

(DRB and S1 Bearer)
E-RAB RELEASE INDICATION
Includes a list of released E-RABs
133
MME Initiated UE Context
Release
RRC S1AP
MME
pmErabRelMme +
pmUeCtxtRelMme +
pmErabRelMmeAct +
Data buffers OR
pmUeCtxtRelMmeAct +
UL DL
All resources for the UE context are released

(DRB and S1 Bearer)
RBS Initiated UE Context

Release
RRC S1AP
UE CONTEXT RELEASE REQUEST MME
Includes release cause

pmErabRelNormalEnb +
Normal release
pmUeCtxtRelNormalEnb +
pmErabRelAbnormalEnb +
Abnormal release
pmUeCtxtRelAbnormalEnb +
pmErabRelAbnormalEnbAct +
Data buffers OR
pmUeCtxtRelAbnormalEnbAct +
UL DL
All resources for the UE context are released
(DRB and S1 Bearer)
134
RBS Initiated UE Context
Release Flow Chart
UE lost due Yes
to S1 I/F pmUeCtxtRelAbnormalEnbActTnFail +
down?
No
HO fails,
Yes
UE dropped ? pmUeCtxtRelAbnormalEnbActHo +
No
UE Yes
connection pmUeCtxtRelAbnormalEnbActUeLost +
lost ?
No
UE lost due to
Yes
cell downtime pmUeCtxtRelAbnormalEnbActCdt +
(manual intervention)
No
RBS Initiated E-RAB Release

Flow Chart
Yes
E-RAB lost due to
S1 I/F down?
pmErabRelAbnormalEnbActTnFail +
No
HO fails Yes
UE dropped? pmErabRelAbnormalEnbActHo +
No
HO excludes Yes
E-RAB? pmErabRelAbnormalEnbActHpr +
No
E-RAB lost due to Yes
UE unreachable? pmErabRelAbnormalEnbActUeLost +
No
Cell downtime Yes
manual interv? pmErabRelAbnormalEnbActCdt +
No
135
Radio Connection
Supervision Principles
RRC_CONNECTED
Maximum
No Inactivity for number of RLC No
‘tInactivityTimer’ retransmissions
0 = Off RLC Acknowledged

Yes Yes
10 to 86400 seconds Mode parameters
RRC_IDLE
RLC Retransmission
Parameters
ManagedElement
+-ENodeBFunction
+-RadioBearerTable
+-DataRadioBearer
dlMaxRetxThreshold = 8 { 1, 2, 3, 4, 6, 8, 16, 32 }
tPollRetransmitDl = 80 { 5, 10, 15, 20, 25, 30, 35, 40, 45, 50,
55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 105, 110, 115, 120,
125, 130, 135, 140, 145, 150, 155, 160, 165, 170, 175, 180,
185, 190, 195, 200, 205, 210, 215, 220, 225, 230, 235, 240,
245, 250, 300, 350, 400, 450, 500 } [msec]
tPollRetransmitUl = 80 { 5, 10, 15, 20, 25, 30, 35, 40, 45, 50,
55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 105, 110, 115, 120,
125, 130, 135, 140, 145, 150, 155, 160, 165, 170, 175, 180,
185, 190, 195, 200, 205, 210, 215, 220, 225, 230, 235, 240,
245, 250, 300, 350, 400, 450, 500 } [msec]
ulMaxRetxThreshold = 8 { 1, 2, 3, 4, 6, 8, 16, 32 }
136
Uplink RLC Failure
‘tPollRetransmitUl’ = 80 msec (default)
Transmit PDU with polling bit

Wait for Status
Indication
Retransmit PDU with polling bit
‘ulMaxRetxThreshold’ = 8 (default)
Retransmission # n Retransmit PDU with polling bit
n = maximum allowed number of retransmissions

=> UE will attempt RRC Re-establishment
UE Radio Link Failure

Detection
SIB 2
ue-TimersAndConstants
t310 : ms2000
n310 : n20
t311 : ms3000
n311 : n1
t301 : ms1000
BLER estimated by UE
UE returns to
RRC_IDLE
n310 t310 t311
Qout
(10% BLER)
Waiting for n311 in RRC Re-establishment
sync indications Procedure
Out-of-sync indications
Qin
(2% BLER)
200 msec Time
137
RRC Connection Re-
Establishment
RRC S1AP MME
Radio Link RRC Connection Re-

Failure Establishment
is transparent to the MME
RRC CONNECTION RESTABLISHMENT REQUEST
t301 pmRrcConnReestAtt +
RRC CONNECTION RESTABLISHMENT
RRC CONNECTION RESTABLISHMENT REQUEST

pmRrcConnReestSucc +
COMPLETE

COMPLETE
UE Radio Link Failure

Detection Parameters
ManagedElement
+-RlfProfile
n310 = 20 { 1, 2, 3, 4, 6, 8, 10, 20 }
n311 = 1 { 1, 2, 3, 4, 5, 6, 8, 10 }
t301 = 400 { 100, 200, 300, 400, 600, 1000,

1500, 2000 } [msec]
t310 = 2000 { 0, 50, 100, 200, 500, 1000,

2000 } [msec]
t311 = 3000 { 1000, 3000, 5000, 10000,

15000, 20000, 30000 } [msec]
138
RRC Connection
Re-establishment Procedure
‘RRC Connection Re-Establishment’ Multi-Target RRC Connection
(FAJ 121 3019) L12B basic feature Re-Establishment’ (FAJ 121 3023) L13B
optional feature
RRC Connection RRC Connection

Re-establishment Request Re-establishment Request
Ongoing
RRC Connection RRC Connection procedure
Re-establishment Not Re-establishment other than
serving handover, X2
RRC Connection RRC Connection unavailable,
cell or
Re-establishment Reject Re-establishment Reject S1 handover,
ongoing
RRC Connection H/O RRC Connection other node
Re-establishment Complete Re-establishment Complete not Ericsson
Only supported in serving cell Supported during ongoing handover and for
and not if there is an ongoing RRC connection re-establishment in any cell
handover procedure were the original source cell is included in
the neighbor list of the serving cell
UE Context Fetch Procedure

UE Serving eNB Target eNB 1 Target eNB 2 Target eNB 3 MME
› In unprepared cell:
If several cells with same
– UE context is fetched from serving
PCI existcell
RRCConnectionReestablishmentRequest(PCI=A, C-RNTI...)
in neighbor eNBs
Context not found!!
– In serving cell – same license controls the Lookup X2 related eNBs
sending of context that have a cell with PCI=A


Context Fetch Response
Apply UE Context
Context Fetch Response Accept
RRCConnectionReestablishment
RRCConnectionReestablishmentComplete
S1: Path Switch Request
S1: Path Switch Request Acknowledge

RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
X2:Release UE Context
139
Multi-Target RRC Connection
Re-Establishment Counters
Counter Name MO Description
The number of RRC Connection Reestablishment

pmRrcConnReestAtt EUtranCell
attempts.
The number of RRC Connection Reestablishments
pmRrcConnReestAttHo EUtranCell
attempted during an ongoing handover.
The number of successful RRC Connection
pmRrcConnReestSucc EUtranCell
Reestablishments.
The number of successful RRC Connection
pmRrcConnReestSuccHo EUtranCell Reestablishments attempted during an ongoing
handover.
The number of RRC Connection Reestablishments
pmRrcConnReestFailLicMtRees EUtranCell attempts that failed due to feature "Multi-Target RRC
Connection Reestablishment" not being OPERABLE.
Number of UE Context Fetch Request messages
pmUeCtxtFetchAtt EUtranCell
received.
The number of UE context fetch attempts that were
successfully replied with a context fetch reply
pmUeCtxtFetchSucc EUtranCell
message. Number of UE Context Fetch procedures
successfully completed.
Mobility Control at Poor

Coverage (Without Feature)
Highest Priority Event A5 or A2 reported:
Frequency: Handover or RwR to reported cell
- Inter-Frequency = A5 No A5 or A2 reported and
- IRAT = A2 ‘a5b2MobilityTimer’ has expired:
RwR to high priority frequency
(only if no QCI 1 bearer)
UE reports event A1
UE reports event A2 and is ordered to measure on the highest priority

frequency according to ‘connectedModeMobilityPrio’ or ‘VoicePrio’ if it
has a QCI1 bearer.
(Blind Handover is also possible if neighbor coverageIndicator=covers)
140
Coverage (With Feature)
On reception of event A5, A3 Measurements stopped if LTE
or B2 Handover or RwR RSRP or RSRQ reaches critical
performed in the normal way. level and blind handover is
(ANR addition also possible) performed to a neighbor with
‘coverageIndicator’ = ‘covers’ or
Search Region RwR to highest priority frequency
(only if there is no QCI1 bearer)
Measurements
UE reports event A1 stopped if
measurements ‘a5b2Mobility’
stopped expires
UE reports event A2 and is given a list of candidate frequencies for

measurement based on frequencies and RATs supported by the UE
and the ‘connectedModeMobilityPrio’ and ‘voicePrio’ parameters
(No Blind handover at this point)

Coverage Parameters (1)
ManagedElement
+-SystemFunctions
+-Licensing
+-OptionalFeatures
+-MobCtrlAtPoorCov
featureStateMobCtrlAtPoorCov = ACTIVATED
Indicates if the licensed feature Mobility Control At Poor
Coverage is ACTIVATED or DEACTIVATED.
+-ENodeBFunction
+-EUtranCellFDD
mobCtrlAtPoorCovActive = true
+-UeMeasControl
ueMeasurementsActive = true
a5B2MobilityTimer = 0 { 0..120000 } [msec]
+-EUtranFreqRelation
interFreqMeasType = EVENT_A5 {EVENT_A5, EVENT_A3}
141
ManagedElement
+-ENodeBFunction
+-EUtranCellFDD
+-UeMeasControl
+-ReportConfigSearch
a1a2SearchThresholdRsrp = -134 { -140..-44 } Unit: 1 dB
a1a2SearchThresholdRsrq = -165 { -195..-30 } Unit: 0.1 dB
a2CriticalThresholdRsrp = -140 { -140..-44 } Unit: 1 dB
a2CriticalThresholdRsrq = -195 { -195..-30 } Unit: 0.1 dB
hysteresisA1A2SearchRsrp = 20 { 0..150 } Unit: 0.1 dB
hysteresisA1A2SearchRsrq = 15 { 0..150 } Unit: 0.1 dB
hysteresisA2CriticalRsrp = 10 { 0..150 } Unit: 0.1 dB
hysteresisA2CriticalRsrq = 10 { 0..150 } Unit: 0.1 dB
timeToTriggerA1Search = 640 { 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512,
640, 1024, 1280, 2560, 5120 } Unit: 1 ms
timeToTriggerA2Critical = 40 { 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512,
640, 1024, 1280, 2560, 5120 } Unit: 1 ms
timeToTriggerA2Search = 40 { 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512,
640, 1024, 1280, 2560, 5120 } Unit: 1 ms

ManagedElement
+-ENodeBFunction
+-EUtranCellFDD
+-UeMeasControl
+-ReportConfigEUtraBestCell
a3offset = 30 { -150..150 } Unit: 0.1 dB
hysteresisA3 = 10 { 0..150 } Unit: 0.1 dB
timeToTriggerA3 = 40 { 0, 40, 64, 80, 100, 128, 160,
256, 320, 480, 512, 640, 1024, 1280, 2560, 5120 }
Unit: 1 ms
triggerQuantityA3 = RSRP {RSRP, RSRQ}
142
Coverage Counters
Counter
Counter Name Description
Type
The total number of A2 measurement reports received due to entering the

Search zone.
This counter is used when the feature Mobility Control at Poor Coverage
pmBadCovSearchEvalReport PEG
is activated.
Stepped at reception of traffic measurement report from UE indicating
bad coverage due to Event A2_Search (either RSRP or RSRQ triggered).
The total number of A2 measurement reports received due to critical

threshold is reached.
This counter is used instead of pmBadCovEvalReport when the feature
pmCriticalBorderEvalReport PEG
Mobility Control at Poor Coverage is activated.
Stepped at reception of traffic measurement report from UE indicating
bad coverage due to Event A2_Critical (either RSRP or RSRQ triggered).
The total number of traffic Best Cell measurement reports received.

Stepped at reception of traffic measurement report indicating a better cell
pmBestCellEvalReport due to Event A3, 'Neighbor becomes amount of offset better than serving'. PEG
In L13B this counter triggers also when an event A3 inter-frequency
measurement report is received.

3. Measure LTE Retainability performance
3.1 Describe the E-RAB release procedure and associated
counters
3.2 Use eNodeB counters to create E-RAB Retainability KPIs
3.3 Explain Radio Connection Supervision
3.4 Explain the parameters and features that influence
Retainability
143
Thank You
144
LTE Performance
Management and
Optimization
LTE Integrity Optimization

4. Measure LTE Integrity performance
4.1 Explain the counters that are used to measure LTE Radio
Bearer throughput
4.2 Use eNodeB counters to create E-UTRAN Integrity KPIs
4.3 Explain the eNodeB features and parameters that influence
Integrity
145
Web Browsing Traffic
www.ericsson.com
Protocol Stack
Hypertext Transfer Protocol
HTTP
Transmission Control Protocol
TCP
Internet Protocol
IP
Email Traffic
Protocol Stack
HTTP
TCP
Internet Protocol
IP
146
Video Streaming Traffic
Protocol Stack
HTTP
TCP
Internet Protocol
IP
File Transfer Traffic
Protocol Stack
File Transfer Protocol
FTP
TCP
Internet Protocol
IP
147
Voice Traffic
3 minutes of speech:
(21.4 + 24.7) X 103 X 60 X 3
≈ 1 MB
8 X 220
Protocol Stack
User Datagram Protocol
UDP
Internet Protocol
IP
Transmission Control
Protocol
+ Bits 0-7 Bits 8-15 Bits 16-23 Bits 24-31
0 Source Port Destination Port
32 Sequence Number
64 Acknowledgement Number
96 Offset Res Flags Window
128 Checksum Urgent Pointer
160 Options Padding
• Connection-oriented
• Data sent between ‘sockets’
• Sequence number on each segment.
192+ Data
• Tx waits for ACKnoledgement
• Each end informs the other about window size
• Connection closed by ‘FIN’ flag.
148
TCP Operation
Sequence No: 1,000 Flags
Window size: 8,750 Bytes SYN
Max segment: 1,460 Bytes Sequence No: 3,000 Flags
Three-way Acknowledgment No: 1,001 SYN
Window size: 8,750 Bytes ACK
handshake Max segment: 1,460 Bytes
Acknowledgment No: 3,001 ACK
Sequence No: x Flags
Acknowledgment No: 1 ACK
Data
Sequence No: y Flags

Acknowledgment No: 1 ACK
Sequence No: n Flags

Data
Server
Client Acknowledgment No: z ACK

Acknowledgment No: 5,145 FIN
ACK
Closing the
connection Sequence No: 5,146 Flags
Acknowledgment No: 3,532 FIN
ACK
TCP Flow Control

Slow Start Congestion avoidance
Receiver Window Size

Number of Segments sent
Packet Loss
(congestion)
SSTresh
Initial cwnd
Time
149
TCP Throughput
Receive Window Size
DL Throughput =
Round Trip Time
Window Size
Round Trip Time
Server
DL Throughput
UL Throughput = X ACK Size
(2 X Segment Size)
TCP Throughput Example

(8750 X 8)
DL Throughput = 7000000 = ___
=_________ 7 mbps
10 X 10-3
8,750 Bytes
10 msec
Server
7000000
UL Throughput = 51470 ___kbps
X 160 = ______= 51
(2X10880)
150
User Datagram Protocol
+ Bits 0-7 Bits 8-15 Bits 16-23 Bits 24-31
0 Source Port Destination Port
32 Length Checksum
• Connectionless
64 Data Data
• Unreliable
+
• Efficient
• No sequence numbering
• No connection opening or closing

Command Uniform Resource Location (URL)
GET http://server.name/path/file.type
Server
Requested web page carried to user by TCP
151
HTTP Operation Example
Domain
Name
Server
‘www.3gpp.org’ IP address?
1
2
IP address is ‘195.238.226.15
3
TCP connection setup
www.3gpp.org/specs/numbering.htm
4 HTTP GET /specs/numbering.htm
ACK ACK
7 5 ‘numbering.htm’ sent to browser 3GPP
Segment Segment Segment Segment Segment Segment
www.3gpp.org
6 TCP connection released
195.238.226.15
File Transfer Protocol

TCP Port Response: # 220 (FTP Server ready) TCP Port
xxxx 21
Request: USER ‘anonymous’
Response: # 331 (Username OK, password required)

Server
Client
Request: PASS ‘IEuser@’
Response: 230 (Guest Login okay)
Response: 226 (Transfer complete)
TCP Port TCP Port

yyyy zzzz
Segment Segment Segment Segment Segment Segment TCP TCP TCP
ACK ACK
152
Voice over LTE Total Delay
eNodeB eNodeB
Terminating
Originating Service UE
UE Network
AMR: AMR
AMR AMR + jitter buffer:
Tframe
+ RTP/UDP UDP/RTP Tdec
GW GW
Tenc +
IP IP IP IP Djitter
PDCP PDCP PDCP PDCP
RLC UM RLC RLC RLC UM
MAC MAC MAC MAC
PHY HARQ PHY TR TR TR TR PHY HARQ PHY
Radio Radio
delay: delay:
Tr Tr
Transport: Service: Transport:

Tt Ts Tt
User satisfaction depends on total delay

(Tframe + Penc + Tr + Tt + Ts + Tt + Tr + Tdec + Tjitter)
HARQ Effect on Voice

Service
Power
WCDMA
X X
Speech Frame
#1
20 msec
Speech Frame
#2
20 msec
Speech Frame
#3
20 msec
Speech Frame
#4
20 msec Time
Power
LTE
X X X XXX X X
1 msec
Time
Radio Delay (Tr)
Radio Delay (Tr) < 80 msec

Lost or late Blocks <1 %
153
EUTRAN Throughput KPIs
The speed at which packets can be
transferred once the first packet has
been scheduled on the air interface.
Average UE PDCP DL Throughput [kbps]:
pmPdcpVolDlDrb – pmPdcpVolDlDrbLastTTI
=
pmUeThpTimeDl/1000
Average PDCP Cell DL Throughput [kbps]:
pmPdcpVolDlDrb
=
pmSchedActivityCellDl/1000

Average MAC Cell DL Throughput [kbps]:
pmRadioThpVolDl
=
pmSchedActivityCellDl/1000
Average UE DL PDCP Throughput per QCI [kbps]:
pmPdcpVolDlDrbQci – pmPdcpVolDlDrbLastTTIQci
=
pmDrbThpTimeDlQci/1000
154
Average UE UL PDCP Throughput [kbps]:
pmUeThpVolUl
=
pmUeThpTimeUl/1000
Average Cell UL PDCP Throughput [kbps]:
pmPdcpVolUlDrb
=
pmSchedActivityCellUl/1000

Average Cell UL MAC Throughput [kbps]:
pmRadioThpVolUl
=
pmSchedActivityCellUl/1000
Average UE UL Throughput per LCG [kbps]:

pmLcgThpVolUlLcg
=
pmLcgThpTimeUlLcg/1000
155
DL DRB Traffic Volume
Measurement The last TTI with
data is removed
since coding may
Traffic Volume Measured by:
pmPdcpVolDlDrbLastTTI be based on size
rather than radio
Traffic Volume Measured by: conditions and
pmPdcpVolDlDrb hence does not
DL Transport Time measured by:
impact the end
pmUeThpTimeDl user.
Data arrives to First data is Time (ms)

empty DL buffer transmitted to the UE
No transmission, buffer not empty Failed transmission
(e.g. due to contention) (Block Error)
Successful transmission by RLC, Successful transmission by RLC,
buffer not empty buffer empty
UL DRB Traffic Volume

Measurement
Traffic Volume Measured by: Contributions
pmUeThpVolUl from the first 4
and last TTI
UL Transport Time measured by:
removed
pmUeThpTimeUl
Data arrives to Grants sent Time (ms)

empty UL buffer to the UE
Scheduling request sent to RBS First data sent to RBS Send buffer is empty again
No receptions, buffer not empty Failed receptions Successful

(e.g. due to contention) (Block Error) reception,
Successful receptions, buffer not Receptions excluded from buffer empty
empty throughput measurement
156
UL DRB Traffic Volume
Measurement per LCG
LCG 1
LCG 2
LCG 3
LCG1 UL Transport Time for LCG3

LCG2 pmLcgThpVolUlLcg[1,2,3]
LCG3
Time (ms)
Contributions from the first
4 and last TTI removed pmLcgThpTimeUlLcg[1,2,3]
EUTRAN Latency KPIs

The time it takes to schedule the first
packet on the air interface, determined
from the time it was received in RBS.
Downlink Average Latency [ms]:

pmPdcpLatTimeDl
=
pmPdcpLatPktTransDl
Downlink Average Latency per QCI [ms]:

pmPdcpLatTimeDlQci
=
pmPdcpLatPktTransDlQci
Uplink Latency not measured
157
Downlink Latency
Measurement
PDCP SDU arrival Samples No receptions, buffer not empty
during (e.g. due to contention)
No Handover Successful receptions, buffer not
Buffer empty?
excluded empty
Yes
t=t0 Note: Corresponding counter per QCI:
pmPdcpLatPktTransDlQci+
pmPdcpLatPktTransDl +
Packet sent on No
Uu?
Data arrives to First data is
Yes
empty DL buffer transmitted to the UE
t=t1
pmPdcpLatTimeDl + t1 – t0
aggregated t = (t1 – t0)
Note: Corresponding counter per QCI:
End pmPdcpLatTimeDlQci+
Discontinuous Reception
2, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 10, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512,
160, 256, 320, 512 or 640 sub-frames. 640, 1024, 1280, 2048 or 2560 sub-frames.
Default = 40 (40 msec) Default = 320 (320 msec)
(1 sub-frame = 1 msec) (1 sub-frame = 1 msec)
shortDRXCycle longDRXCycle shortDRXCycle
Active
Sleep
shortDRXCycleTime shortDRXCycleTime
At data send/receive start inactivityTimer
Data 1, 2, 3, 4, 5, 6, 8, 10, 20, 30, 40, 50, 60,
At expiry of DrxinactivityTimer: 80, 100, 200, 300, 500, 750, 1280, 1920,
- enter shortDRXCycle 2560 and 0 PDCCH sub-frames.
onDuration - start shortDRXCycleTimer Default = 200 (200 msec)
(marked by )
At expiry of shortDRXCycleTimer (1 sub-frame = 1 msec)
- enter longDRXCycle
158
EUTRAN Packet Loss KPIs
?
The ratio of lost and transferred packets.
Downlink Packet Error Loss Rate [%]:
pmPdcpPktDiscDlPelr + pmPdcpPktDiscDlPelrUu + pmPdcpPktDiscDlHo + A

= X100
pmPdcpPktReceivedDl – pmPdcpPktFwdDl + A
pmPdcpPktReceivedDl
A = [pmPdcpPktDiscDlEth + pmPdcpPktDiscDlNoUeCtxt] x
∑ pmPdcpPktReceivedDl
RBS
Uplink Packet Loss Rate [%]:
pmPdcpPktLostUl
= X100
pmPdcpPktLostUl + pmPdcpPktReceivedUl
EUTRAN Packet Loss KPIs

? The ratio of lost and transferred packets.
Downlink Packet Error Loss Rate per Qci [%]:
pmPdcpPktDiscDlPelrQci + pmPdcpPktDiscDlPelrUuQci + pmPdcpPktDiscDlHoQci + B

= X100
pmPdcpPktDiscDlPelrQci + pmPdcpPktDiscDlPelrUuQci + pmPdcpPktDiscDlHoQci + B + pmPdcpPktTransDlQci
pmPdcpPktReceivedDlQci
B= [pmPdcpPktDiscDlEth + pmPdcpPktDiscDlNoUeCtxt] X
∑ pmPdcpPktReceivedDlQci
RBS
Uplink Packet Loss Rate per Qci [%]:
pmPdcpPktLostUlQci
= X100
pmPdcpPktLostUlQci + pmPdcpPktReceivedUlQci
159
Downlink Packet Loss
Measurement
Only partially transmitted over air No part transmitted over air interface
interface due to reasons other than HO: due to reasons other than HO:
pmPdcpPktDiscDlPelrUu pmPdcpPktDiscDlPelr
Total packets (PDCP SDUs) received

in the PDCP layer in the RBS:
pmPdcpPktReceivedDl
Lost due to HO:

pmPdcpPktDiscDlHo
SGW
Discarded in Ethernet part of RBS:

pmPdcpPktDiscDlEth
((NOTE baseband processor level
counter)
Forwarded to target cell at HO:
pmPdcpPktFwdDl
Uplink Packet Loss

Measurement
Total packets received in the UL:

pmPdcpPktReceivedUl
Total packets lost in the UL:

pmPdcpPktLostUl
160
VoIP Integrity
This KPI measures the integrity impact for VoIP in
the RAN .
VoIP Integrity [%]:
pmVoipQualityUeUlOk
= X100
pmVoipQualityUeUlOk + pmVoipQualityUeUlNok
VoIP Integrity [cell] [%]:
pmVoipQualityRbUlOk
= X100
pmVoipQualityRbUlOk+ pmVoipQualityRbUlNok
VoIP User Satisfaction

QCI Resource Priority PDB PELR Example services
type
1 GBR 2 100ms 10-2 Conversational
Voice
7 Non GBR 7 100ms 10-3 Voice, Video,
Interactive
The Number of UE that are gaming
satisfied with their VoIP quality
TS23.203
pmVoipQualityUeUlOk + The UE is considered to be
satisfied if:
The Number of UE that are not • The minimum amount of VoIP

satisfied with their VoIP quality packets is available for the
measurement
pmVoipQualityUeUlNok +
• At least 99% of the VoIP
packets of the UE had an air
The number of VoIP quality measurements with low interface delay within the packet
number of samples while the VoIP satisfaction of a UE delay budget.
is between 50% and 99%:
pmVoipQualityUeUlLowSampl +
161

4. Measure LTE Integrity performance
4.1 Explain the counters that are used to measure LTE Radio
Bearer throughput
4.2 Use eNodeB counters to create E-UTRAN Integrity KPIs
Integrity
Thank You
162
LTE Performance
Management and
Optimization
LTE Mobility Optimization
After Completion of this chapter the participants will be able to:

5. Measure LTE Mobility performance
5.1 Explain the various LTE mobility procedures and associated
counters
5.2 Use eNodeB counters to create E-UTRAN Mobility KPIs
Mobility
163
EUTRAN Mobility KPI
The ability to provide the requested
service to the user with mobility.
EUTRAN Mobility Success Rate [%]:
= Preparation Success X Execution Success X 100

Preparation Attempts Execution Attempt
* For accurate formulas and the additional EUTRAN Mobility Success Rate KPIs such as
Intra, Inter /IRAT handovers and the Load balancing and eMBMS features contributions CPI
document Key Performance Indicators
Intra LTE Handover Types

MME SGW
S1-MME S1-U
Intra RBS
X2
X2 Based S1 Based
164
Inter Frequency and IRAT
Handover SGSN/MME P/SGW
S1-MME
S1-U
UTRAN RNC
Iub F2
X2
IRAT
F1
Inter Frequency
Intra RBS Handover

Preparation Source SGW MME
Target
pmHoPrepAttLteIntraF +
or
(Event A3)
pmHoPrepAttLteInterF +
Handover Decision
Internal RBS trigger:

Target cell informs source
cell that UE resources
have been reserved for an
intra-RBS handover.
pmHoPrepSuccLteIntraF +
or
pmHoPrepSuccLteInterF +
165
Intra RBS Handover
Execution Source SGW MME
Target
pmHoExeAttLteIntraF +
or
(Including ‘mobilityControlInformation’)
pmHoExeAttLteInterF +
Random Access Preamble and Response
(Handover complete)
Data transfer in Target cell
Internal RBS trigger:

UE has changed cell.
pmHoExeSuccLteIntraF +
or
pmHoExeSuccLteInterF +
X2 Based Handover
Preparation SGW MME
Source Target

pmHoPrepAttLteIntraF +
or
(Event A3)
pmHoPrepAttLteInterF +
Handover Decision
HANDOVER REQUEST
Admission Control
pmHoPrepSuccLteIntraF + HANDOVER REQUEST
or
ACKNOWLEDGE
166
X2 Based Handover
Execution MME
SGW
Source Target

pmHoExeAttLteIntraF +
or
pmHoExeAttLteInterF +

(Handover complete)
Data transfer in Target RBS PATH SWITCH REQUEST
MODIFY BEARER
REQUEST
MODIFY BEARER
RESPONSE
PATH SWITCH RESPONSE
pmHoExeSuccLteIntraF + UE CONTEXT RELEASE
or
Cause: Successful Handover
pmHoExeSuccLteInterF +
S1 Based Handover
Preparation SGW MME
Source Target Source Target

Source Target
RRC MEASUREMENT REPORT pmHoPrepAttLteIntraF +
or
(Event A3) pmHoPrepAttLteInterF +
Handover Decision
HANDOVER REQUIRED FORWARD
RELOCATION
REQUEST
Allocate resources
in target S-GW
HANDOVER REQUEST
Admission Control
FORWARD
pmHoPrepSuccLteIntraF + HANDOVER COMMAND RELOCATION

or RESPONSE
167
S1 Based Handover
Execution SGW MME
Source Target Source Target Source Target
RRC CONNECTION RECONFIGURATION pmHoExeAttLteIntraF +

or
(Including ‘mobilityControlInformation’) pmHoExeAttLteInterF +

HANDOVER NOTIFY
(Handover confirm)
Data transfer in Target RBS and S-GW FORWARD
RELOCATION
COMPLETE
FORWARD
RELOCATION
pmHoExeSuccLteIntraF + UE CONTEXT RELEASE COMPLETE
or ACK
pmHoExeSuccLteInterF + Cause: Successful Handover
LTE to WCDMA Mobility

A2 Event Received
Stop process and coverageIndicator=COVERS
wait for A2 event Blind Handover to pre-
again Yes defined LTE or
Handover
? WCDMA cell
No
Event 1A
(Good coverage) Start B2 and A1 Session Continuity
reported measurements to priority cell
B2 event time out
received Handover to
Yes reported LTE or
Handover
? WCDMA cell
No
Session Continuity to
reported frequency or IRAT
168
LTE to WCDMA Handover
Preparation RNC SGW MME SGSN
Target Source Target Source Target

Source
RRC MEASUREMENT REPORT pmHoPrepAtt +
(Event A2 or B2)
Handover Decision
Handover Required
FORWARD
RELOCATION
REQUEST
Allocate resources in
target SGSN
RELOCATION REQUEST
Admission Control
RELOCATION REQUEST ACKNOWLEDGE
FORWARD
pmHoPrepSucc + HANDOVER COMMAND
RELOCATION
RESPONSE
LTE to WCDMA Handover

Execution RNC SGW MME SGSN
Target Source Target Source Target

Source
RRC MobilityFromEUTRANCommand pmHoExeAtt +
RRC HANDOVER COMPLETE
RELOCATION COMPLETE
(Handover confirm)
Forward Relocation
Complete Notification
Forward Relocation
Complete acknowledge
MODIFY BEARER REQUEST
MODIFY BEARER RESPONSE
Routing Area Update Procedure

pmHoExeSucc + UE CONTEXT RELEASE
169
WCDMA Session Continuity
RNC SGW MME SGSN
(Event A2)
(Measurement conf – event B2)

Only performed if LTE parameter ‘ueMeasurementsActive’ = TRUE
(Event B2)
pmUeCtxtRelSCWcdma +
RRC CONNECTION RELEASE
UE Context Release Request
(redirect information)
UE Context Release Command
UE Context Release Complete
RRC Connection Establishment Procedure
Routing Area Update and Service Request Procedure
CS Fallback to WCDMA or
GSM
› Subscribers roaming with preference on LTE access, no CS-voice
service available (i.e. IMS is not used as voice engine)
› Fallback triggered to overlapping CS domain (2G/3G) whenever voice

service is requested
› Resumed LTE access for PS services after call completion

(cell reselection)
LTE island
PS PS
LTE
LTE
LTE
CS (+PS)
LTE
GERAN/UTRAN
170
CSFB High Level Signalling
Flow RNC/BSC MME MSC
Target Source Target

E-UTRAN Source
RRC_CONNETED
EXTENDED SERVICE REQUEST
UE CONTEXT MODIFICATION REQUEST
(CS Fallback Indicator)

UE CONTEXT MODIFICATION RESPONSE
MEASUREMENT REPORT SOLICITATION
RRC CONNECTION RELEASE pmUeCtxtRelCsfbGsm(Em) +

or
pmUeCtxtRelCsfbWcdma(Em)
UE CONTEXT RELEASE REQUEST
UE CONTEXT RELEASE
UE changes RAT then LA Update

CS Mobile Originated Call
Other Mobility Formulas

WCDMA
IRAT Rate [%]:
pmUeCtxtRelSCWcdma
= X100
pmUeCtxtEstabSucc
The % of connections that perform Session Continuity to WCDMA
CSFB Rate [%]:
pmUeCtxtRelCsfbWcdma + pmUeCtxtRelCsfbWcdmaEm
= X100
pmUeCtxtEstabSucc
The % of connections that perform CSFB to WCDMA
171
Automated Neighbor Relation
PCI Reported
PCI does not correspond to Note: If

any known cell ‘nrHoNeededToAddCellRelation’ > 0
The neighbour is added as an
Ask same UE for CGI internal ENodeB temporary
EUtranCellRelation.
(not shown in the MOM)
If answer from same UE
The neighbour is added to the MOM
when the number of handover
Add missing neighbor RBS, attempts has reached the setting of:
cell, neighbor relation and X2 ‘nrHoNeededToAddCellRelation’
Ready
A new relationship is created
ANR Counters
Neighbor relation removed
X
pmAnrNeighbrelRem
Neighbor relation added √ pmAnrNeighbrelAdd
172
ANR Reporting UEs
Intra Frequency Inter Frequency
anrUesEUtraIntraFMax = 20 { 0..100 } anrUesThreshInterFMax = 20 { 0..100 }
Unit = UE Unit = UE
known neighbor reported=> decrease by: known neighbor reported=> decrease by:
anrUesEUtraIntraFDecr = 10 { 0..1000 } anrUesThreshInterFDecr = 10 { 0..1000 }
Unit = centiUE - Unit = centiUE -
Unknown neighbor reported=> increase by: Unknown neighbor reported=> increase by:
anrUesEUtraIntraFIncrHo = 100 { 0..1000 } anrUesThreshInterFIncrHo = 100 { 0..1000 }
Unit = centiUE Unit = centiUE
+ +
anrUesEUtraIntraFMin = 1 { 0..100 } anrUesThreshInterFMin = 1 { 0..100 }
Unit = UE Unit = UE
UE Level Oscillating Handover

Minimization
› Oscillating handovers may
occur due to specific radio
conditions
› Increased network load (signaling)

› Increased risk for HO failure
› Packet loss for UM connections -
Voice
› Reduced throughput
› Remedy: increased HO margin only

for these UEs!!!
173
Handover Oscillation
Prevention Rules
› Rule 1: Very fast HOs are rejected
– Probably due to erroneous report from UE
› Rule 2: Fast HOs are moderated
– An extra 1 dB of gain of HO is required for a fast HO
› Rule 3: Oscillating HOs are moderated
– An extra 2 dB of gain is required to HO again into a cell the UE
didn’t stay in last time
Handover Oscillation
Prevention Rules -details
TC Time in Last Cell Action
(TL)
TC < T1 - Reject handover.
T1 ≤ TC < T2 TL < T2 Apply an extra offset2 (2dB) on handover
margin for handover back to the last cell.
Apply an extra offset1 (1dB) on handover
margin for handover to any other cell
T1 ≤ TC < T2 TL ≥T2 Apply an extra offset1 (1dB) on handover
margin.
T2 ≤ TC < T3 TL < T2 Apply an extra offset2 (2dB) on handover
margin for handover back to the last cell.
Attempt handover
T2 ≤ TC < T3 TL ≥ T2 Attempt handover
T3 ≤ TC - Attempt handover
TC: Time in current cell T1: Time limit 1 = 200 ms

TL: Time in last cell T2: Time limit 2 = 2,000 ms
T3: Time limit 3 = 5,000 ms
174
Automated Mobility Optimization
› Before L14A, UE Level Oscillating Handover Minimization

prevents Oscillating HO per UE, by controlling UE specific
cellindividualoffset values.
› In L14A, the Automated Mobility Optimization feature
gathers statistics about each relation and adjusts the
cellindividualoffset value per relation, applicable on all UE’s
in the cell.
Background Problem
› The UE monitors if HO events are triggered based on threshold

values sent by the eNB in the measurement configurations.
Some of these thresholds are the same for all cells, while others
such as cellIndividualOffset is unique per cell relation (PCI).
› Manual configuration of these thresholds is difficult and wrong
settings may lead to more drop connections and oscillating
handovers.
› This feature automatically configures the cellIndividualOffsett
value per cell relation in order to reduce the number of drop
connections and oscillating handovers.
175
HO Failures & Oscillating HO
Too Early HO
› The UE has a connection failure during a HO procedure or soon (less
than one second) after a successful HO and if the UE re-establishes in
the source cell.
Too Late HO
› The UE has a connection failure during a HO procedure or after a long
stay (more than one second) in the same cell and if the UE re-
establishes in a different cell.
HO to wrong cell
› The UE has a connection failure during a HO procedure or soon (less
than one second) after a successful HO and if the UE re-establishes in a
cell which was neither the original source or the target cell.
Oscillating HO
› A UE comes back successfully to the same cell within one second after
a completion of the HO.
HO Failures & Oscillating HO

Illustration HO border from A to B
HO border from B to A
› Handover Failure Types

– Too Early Handover Cell-A
– Too Late Handover
– Handover to Wrong Cell
› Oscillating Handover
HO border from A to C
B
176
Automated Mobility
Optimization Overview
› The Automated Mobility Optimization feature optimizes the
cell borders based on the observed output of the different
error cases and builds up statistics about the relation.
› The Algorithm is based on an evaluation time, where
statistics are collected on each cell border and changes are
made if enough statistics are gathered during that time
period. The algorithm also considers statistics from the late
changes and evaluates if the change that was made was
the correct change.
Automated Mobility Optimization

Parameters
hoOptStatTime
-(def. 24 hrs) specifies the time interval between evaluations
hoOptStatNum
-the minimum number of HO required by the HO
optimization function before adjusting HO parameters
hoOptAdjThresholdAbs
-the absolute threshold value for adjusted handover failure
rate required to adjust handover parameters
hoOptAdjThresholdPerc
-the percentage threshold value for adjusted handover
failure rate required to adjust handover parameters
cioUpperLimitAdjBySon and cioLowerLimitAdjBySon

controls the upper and lower limit on how far the Automated
Mobility Optimization feature can adjust the
CellIndividualOffset
177

5. Measure LTE Mobility performance
5.1 Explain the various LTE mobility procedures and associated
counters
5.2 Use eNodeB counters to create E-UTRAN Mobility KPIs
Mobility
Thank You
178
LTE Performance
Management and
Optimization
LTE Availability and System Utilization
After Completion of this chapter the participants will be able to:

6. Measure LTE Cell Availability
6.1 Explain the counters that are used to measure LTE Cell
Availability
6.2 Use eNodeB counters to create Cell Availability KPIs and
measure System Utilization
6.3 Explain the eNodeB parameters that influence Cell Availability
and System Utilization
179
EUTRAN Cell Availability
Cell Auto Blocked:
pmCellDowntimeAuto + (every second)
Cell Manually Blocked:
pmCellDowntimeMan + (every second)
EUTRAN Availability KPI

The percentage of time that a cell is
considered available.
Cell Availability [%]:
N X L X 900 – ∑(pmCellDowntimeAuto + pmCellDowntimeMan)

= X 100
N X L X 900
Where:
N is the number of reporting periods (e.g. 4 for one hour)
L is the number of cells to be measured
180
EUTRAN PIs
DBB Capacity Licenses

ManagedElement
+-SystemFunctions
+-Licensing
+-CapacityLicenses
+-CapacityConnectedUsers
licenseCapacityConnectedUsers { 0..65535 }
The licensed capacity limit for Connected Users.
+-DlBasebandCapacity
licenseCapacityDlBbCapacity { 0..65535 }
The licensed capacity limit for downlink Baseband capacity.
+-DlPrbCapacity
licenseCapacityDlPrbCapacity { 0..65535 }
The licensed capacity limit for downlink PRB capacity.
+-UlBasebandCapacity
licenseCapacityUlBbCapacity { 0..65535 }
The licensed capacity limit for uplink Baseband capacity.
+-UlPrbCapacity
licenseCapacityUlPrbCapacity { 0..65535 }
The licensed capacity limit for uplink PRB capacity.
181
CUL Capacity Licenses
License Key File (LKF)
Users in ‘RRC_CONNECTED’ state
OSS-RC
ManagedElement
+-SystemFunctions
+-Licensing
+-CapacityLicenses
+CapacityConnectedUsers READ ONLY
licenseCapacityConnectedUsers {0..65535}
Maximum in L15B is 4000 (single DUS41)
Or 8000 (Dual DUS41)
CUL Use Distribution

16
14
12
[% of time]
10
8
6
4 Peak use
2
0
[0..5%]
[10..15%]
[15..20%]
[20..25%]
[25..30%]
[30..35%]
[35..40%]
[40..45%]
[45..50%]
[50..55%]
[55..60%]
[60..65%]
[65..70%]
[70..75%]
[75..80%]
[80..85%]
[85..90%]
[90..95%]
[95..100%]
[5..10%]
pmLicConnectedUsersDistr
182
CUL Use Distribution
Counter
Counter
Counter Name Managed Object Description
Type
Shows the utilization for the number of

connected users in the RBS.
PDF ranges:
[0]: [0..5]%,
[1]: ]5..10]%,
[2]: ]10..15]%,
[3]: ]15..20]%,
[4]: ]20..25]%,
[5]: ]25..30]%,
[6]: ]30..35]%,
[7]: ]35..40]%,
[8]: ]40..45]%,
[9]: ]45..50]%,
pmLicConnectedUsersDistr CapacityConnectedUsers [19]: ]50..55]%, PDF
[11]: ]55..60]%,
[12]: ]60..65]%,
[13]: ]65..70]%,
[14]: ]70..75]%,
[15]: ]75..80]%,
[16]: ]80..85]%,
[17]: ]85..90]%,
[18]: ]90..95]%,
Grace Period
[19]: ]95..100]%
[20]: ]100..125]%
[21]: ]125..150]%
[22]: ]150..200]%
[23]: ]200..65535]%
CUL Grace Period

CUL
Capacity
Max
License
Grace Time
Period
ManagedElement
+-SystemFunctions
+-Licensing
+-CapacityLicenses
+CapacityConnectedUsers
gracePeriodActive READ ONLY
gracePeriodAvailable
gracePeriodOriginalLinceseLimit {0..65535}
gracePeriodTimeLeft {0..65535}
183
CUL Utilization Example
Utilization = pmLicConnectedUsersMax / pmLicConnectedUsersLicense
Average CUL Percentile

Example 1: ‘licConnectedUsersPercentileConf’= 90 => pmLicConnectedUsersActual = 85-90%
Example 2: ‘licConnectedUsersPercentileConf’= 20 => pmLicConnectedUsersActual = 40-45%
16
90 percentile
14
12
[% of time]
10
8
20 percentile
6
0
[40..45%]
[30..35%]
[35..40%]
[45..50%]
[50..55%]
[55..60%]
[60..65%]
[25..30%]
[65..70%]
[90..95%]
[85..90%]
[20..25%]
[70..75%]
[10..15%]
[15..20%]
[75..80%]
[80..85%]
[5..10%]
[95..100%]
[0..5%]
pmLicConnectedUsersActual
=
M pmLicConnectedUsersDistr
184
CUL Time Congestion
pmLicConnectedUsersTimeCong + (every second)

CUL Time Congestion [%]:
pmLicConnectedUsersTimeCong
= X 100
N X M X 900
Where:
N is the number of reporting periods (e.g. 4 for one hour)
M is the number of cells to be measured
Average No of RRC Connected

Users
pmRrcConnLevSamp
(ACC sampled every 5 seconds)
= pmRrcConnLevSum
/L
pmRrcConnLevSamp
L= number of cells
The counters are on a cell level
185
Peak No of RRC Connected
Users
Peak number of RRC Connected Users=max pmRrcConnMax
40
[RRC_CONNECTED MODE]
35
30
25
20
15
10
0
Peak number of UE in RRC_CONNECTED mode 15 [min]
in one ROP
pmRrcConnMax
Downlink Baseband Capacity

Utilization
16
14
12
[% of time]
10
8
6
4 Peak use
2
0
[0..5%]
[10..15%]
[15..20%]
[20..25%]
[25..30%]
[30..35%]
[35..40%]
[40..45%]
[45..50%]
[50..55%]
[55..60%]
[60..65%]
[65..70%]
[70..75%]
[75..80%]
[80..85%]
[85..90%]
[90..95%]
[95..100%]
[5..10%]
pmLicDlCapDistr
186
=
[% of time] [% of time]
10
12
14
16
0
2
4
6
8
10
12
14
16
0
2
4
6
8
[0..5%]
[0..5%]
[5..10%]
[5..10%]
M
[10..15%]
[10..15%]
[15..20%]
[15..20%]
∑pmLicDlCapActual
[20..25%]
Utilization
[20..25%]
[25..30%]
[25..30%]
20 percentile
90 percentile
[30..35%] [30..35%]
Utilization PIs
[35..40%] [35..40%]
[40..45%] [40..45%]
[45..50%] [45..50%]
[50..55%] [50..55%]
[55..60%] [55..60%]
[60..65%] [60..65%]
[65..70%] [65..70%]
[70..75%] [70..75%]
pmLicDlCapDistr
Example 2: ‘licDlBbPercentileConf’= 20 => pmLicDlCapActual = 40-45%
Example 1: ‘licDlBbPercentileConf’= 90 => pmLicDlCapActual = 85-90%
Uplink Baseband Capacity

[75..80%] [75..80%]
pmLicUlCapDistr
[80..85%] [80..85%]
Downlink Baseband Capacity
[85..90%] [85..90%]
[90..95%] [90..95%]
[95..100%] [95..100%]
Peak use
187
Uplink Baseband Capacity
Utilization PIs
Example 1: ‘licUlBbPercentileConf’= 90 => pmLicUlCapActual = 85-90%
Example 2: ‘licUlBbPercentileConf’= 20 => pmLicUlCapActual = 40-45%
16
90 percentile
14
12
[% of time]
10
8
20 percentile
6
[40..45%]
[55..60%]
[25..30%]
[30..35%]
[35..40%]
[45..50%]
[50..55%]
[60..65%]
[65..70%]
[90..95%]
[85..90%]
[95..100%]
[10..15%]
[15..20%]
[20..25%]
[70..75%]
[5..10%]
[0..5%]
[75..80%]
[80..85%]
∑ pmLicUlCapActual
=
M = pmLicUlCapDistr
Average Transferred Downlink

Volume PI
pmPdcpVolDlDrb =
[kilobit]
pmPdcpVolDlDrbTransQci =
pmPdcpVolDlSrb = [kilobit]
L= number of cells
= ∑(pmPdcpVolDlDrb + pmPdcpVolDlSrb)/L [kilobits]
Per QCI = ∑ pmPdcpVolDlDrbQci/L [kilobits]
188
Average Received Uplink
Volume PI
pmPdcpVolUlDrb =
[kilobit]
pmPdcpVolUlDrbQci =
pmPdcpVolUlSrb = [kilobit]
L= number of cells
= ∑ (pmPdcpVolUlDrb + pmPdcpVolUlSrb)/L [kilobits]
Per QCI = ∑ pmPdcpVolUlDrbQci/L [kilobits]
RRC Connected and Active UE
Data
RRC_Connected
Transfer
Data in Buffer
Time
DL or UL
Inactivity
100 msec
RRC_Idle RRC_Idle
holdover
tInactivityTimer
expires
Active
189
Active UEs Downlink PIs
Average number of simultaneous Actives UEs in DL:
pmActiveUeDlSum
=∑ /L
L pmSchedActivityCellDl
Average number of simultaneous Actives UEs in DL per QCI:
pmActiveUeDlSumQci
=∑ /L
L pmSchedActivityCellDl
Peak number of simultaneous Active UEs in DL

Peak No of Active UEs in DL = max pmActiveUeDlMax
Active UEs Uplink PIs

Average number of simultaneous Actives UEs in UL:
pmActiveUeUlSum
=∑ /L
L pmSchedActivityCellUl
Average number of simultaneous Actives UEs in UL per LCG:
pmActiveUeUlSumLcg
=∑ /L
L pmSchedActivityCellUl
Peak number of simultaneous Active UEs in UL

Peak No of Active UEs in DL = max pmActiveUeUlMax
190
Average No of Simultaneous
E-RABs PIs
pmErabLevSum and pmErabQciLevSum
(ACC sampled every 5 seconds)
Per QCI:
= ∑ pmErabLevSum ∑ pmErabQciLevSum
L pmErabLevSamp
/L = /L
L pmErabLevSamp
L= number of cells
Peak No of Established E-
RABs
Peak number of Established E-RABs=max L cells pmErabMax
Peak number of Established E-RABs,QCI=max L cells pmErabQciMax
40
35
[No of E-RABS]
30
25
20
15
10
0
0 Peak number of E-RABs 15 [min]
in one ROP
pmErabMax
Per QCI: pmErabQciMax
191
Session Time PI
in session out of session in session
Data
Transfer 100 msec 100 msec
Average UE Session Time Average DRB Session Time per QCI
= ∑ pmSessionTimeUe/L [sec] = ∑ pmSessionTimeDrbQci/L [sec]

L L
L= number of cells
Control Channel Element

f
1 Control Channel Element
t
1 Resource Element Group
1 Resource Element
PDCCH Format Number of CCEs Number of REGs Number of PDCCH bits

0 1 9 72
1 2 18 144
2 4 36 288
3 8 72 576
192
Control Channel Element PIs
CCE Utilization:
PDCCH Utilization=pmPdcchCceUtil
CCE Utilization per QCI in DL:
= pmPdcchCceUsedDlQci
pmPdcchMaxCceAvail
CCE Utilization per QCI in UL:
= pmPdcchCceUsedUlQci
pmPdcchMaxCceAvail
Downlink PRB Utilization

16
14
12
[% of time]
10
8
6
4 Peak use
2
0
[0..5%]
[10..15%]
[15..20%]
[20..25%]
[25..30%]
[30..35%]
[35..40%]
[40..45%]
[45..50%]
[50..55%]
[55..60%]
[60..65%]
[65..70%]
[70..75%]
[75..80%]
[80..85%]
[85..90%]
[90..95%]
[95..100%]
[5..10%]
pmPrbUtilDl
193
Downlink PRB Capacity
Utilization PIs
Example 1: ‘licDlPrbPercentileConf’= 90 => pmLicDlPrbCapActual = 85-90%
Example 2: ‘licDlPrbPercentileConf’= 20 => pmLicDlPrbCapActual = 40-45%
16
90 percentile
14
12
[% of time]
10
8
20 percentile
6
[40..45%]
[55..60%]
[25..30%]
[30..35%]
[35..40%]
[45..50%]
[50..55%]
[60..65%]
[65..70%]
[90..95%]
[85..90%]
[95..100%]
[10..15%]
[15..20%]
[20..25%]
[70..75%]
[5..10%]
[0..5%]
[75..80%]
[80..85%]
pmLicDlPrbCapActual
=
L pmLicDlPrbCapDistr
Downlink PRB Utilization per

QCI PI.
The average use of the Physical
Resource Blocks (PRB) in the
downlink per QCI.
Downlink PRB utilization, QCI [%]
pmPrbUsedDlReTrans
pmPrbUsedDlDtchFirstTransQci 1+
pmPrbUsedDlFirstTrans
= x100
pmPrbAvailDl
194
=
[% of time]
[% of time]
10
12
14
16
0
2
4
6
8
10
12
14
16
0
2
4
6
8
[0..5%]
[0..5%]
[5..10%]
[5..10%]
L
[10..15%]
[10..15%]
[15..20%]
[15..20%]
[20..25%]
pmLicUlPrbCapActual
[20..25%]
[25..30%]
[25..30%]
20 percentile
90 percentile
[30..35%]
[30..35%]
Utilization PIs
[35..40%]
[35..40%]
[40..45%] [40..45%]
[45..50%] [45..50%]
[50..55%] [50..55%]
[55..60%] [55..60%]
Uplink PRB Capacity

Uplink PBR Utilization
[60..65%] [60..65%]
[65..70%] [65..70%]
[70..75%] [70..75%]
pmPrbUtilUl
pmLicUlPrbCapDistr
[75..80%] [75..80%]
Example 2: ‘licUlPrbPercentileConf’= 20 => pmLicUlPrbCapActual = 40-45%

Example 1: ‘licUlPrbPercentileConf’= 90 => pmLicUlPrbCapActual = 85-90%
[80..85%] [80..85%]
[85..90%] [85..90%]
[90..95%] [90..95%]
[95..100%] [95..100%]
Peak use
195
Uplink PRB Utilization per
QCI PI.
The average use of the Physical
Resource Blocks (PRB) in the
uplink per QCI.
Uplink PRB utilization, QCI [%]
pmPrbUsedUlDtchQci
= x100
pmPrbAvailUl
Main Processor Load

Distribution
30
[% of time]
25
20
Peak Load
15
10
5
0
[0..20%]
[20..30%]
[30..40%]
[40..50%]
[50..60%]
[60..70%]
[70..80%]
[80..85%]
[85..90%]
[90..95%]
[>95%]
pmProcessorLoadDistr
196

6. Measure LTE Cell Availability
6.1 Explain the counters that are used to measure LTE Cell
Availability
6.2 Use eNodeB counters to create Cell Availability KPIs and
measure System Utilization
6.3 Explain the eNodeB parameters that influence Cell Availability
and System Utilization
Thank You
197
LTE Performance
Management and
Optimization
LTE Cell and UE Trace

7. Explain what is collected by LTE Cell and UE Trace
7.1 Explain briefly how LTE Cell and UE Trace are collected and
stored
198
LTE UE and Cell Trace
Introduction
UE Trace: UE Trace:
Operator decides Maximum 16 per eNodeB
which UE to record
Both UE and Cell Trace

record events and radio
environment measurements
selected by the operator
Cell Trace:
Fraction of UEs in Cell Trace:
selected cell recorded Maximum 6 per eNodeB
LTE UE and Cell Trace

Contents Internal Events:
• ‘INTERNAL_EVENT_’.
• ‘INTERNAL_PER _’
• ‘INTERNAL_PROC_’
RRC External Events S1 External Events
X2 External Events MME

Internal Events:
• ‘UE_MEAS’
199
‘INTERNAL_EVENT_’ Events
Event Event
Event Name Event Trigger
ID Type
Internal problem at decoding message

INTERNAL_EVENT_RRC_ERROR 5120 UE
occurs
RESET ACKNOWLEDGE has not been
INTERNAL_EVENT_NO_RESET_ACK_FROM_MME 5123 RBS received from the remote node (MME),
despite re-transmissions of RESET.
. . .
. . . .
. . . .
. When a UE is to be configured using
RRC Connection Reconfiguration to
INTERNAL_EVENT_MEAS_CONFIG_PERIODICAL_GERAN 5183 UE report measurements on GERAN with
Report Configuration of type Periodical
(see 3GPP TS 36.331).
When a UE is to be configured using
RRC Connection Reconfiguration to
INTERNAL_EVENT_MEAS_CONFIG_PERIODICAL_UTRA 5184 UE report measurements on UTRA with
Report Configuration of type Periodical
(see 3GPP TS 36.331).
‘INTERNAL_EVENT_’ Example
200
‘UE_MEAS_’ Events
Event Event
ID Type
Used as configuration for the first

configured periodic PM Initiated UE
UE_MEAS_INTRAFREQ1 5153 UE
Measurement for infra frequency
EUTRA measurements.
Used as configuration for the second
configured periodic PM Initiated UE
UE_MEAS_INTRAFREQ2 5154 UE
Measurement for intra frequency
EUTRA measurements.
Used when a PM Initiated UE
measurement has been triggered and
UE_MEAS_EVENT_FEAT_NOT_AVAIL 5155 RBS
rejected because no license for the
optional feature exists on the node.
Used when a PM Initiated UE
Measurement has been trigger, but
UE_MEAS_EVENT_NOT_CONFIG 5156 Cell no configuration exist for the
measurement object or report
configuration.
‘UE_MEAS_’ Example
201
‘INTERNAL_PER_’ Events
Event Event
ID Type
Measurements of the radio enviroment.

INTERNAL_PER_RADIO_UTILIZATION 3072 Cell
Measurements are measured continously.
Measurements of the radio environment.
INTERNAL_PER_UE_ACTIVE_SESSION_TIME 3074 Cell Measurements are measured
continuously.
. . . .
. . . .
. . . .
A repetition of a Commercial Mobile
Alert System (CMAS) message has been
completed. A repetition comprises a
INTERNAL_PER_EVENT_CMAS_REPET_COMPL 3107 Cell
number of SIB12 transmissions with one
paging cycle at the start and one paging
cycle after stop of transmission.
UE level measurements with Timing
INTERNAL_PER_RADIO_UE_MEASUREMENT_TA 3108 UE Alignment information sent periodically
(aproximately 1 per minute- 60 samples)
‘INTERNAL_PER_’ Example
202
‘INTERNAL_PROC_’ Events
Event Event
ID Type
The event is triggered at successful reception

of RRC message RRC Connection Setup
INTERNAL_PROC_RRC_CONN_SETUP 4097 UE
Complete or whenever the RRC Connection
Setup procedure fails
The event is triggered at any response to an
INTERNAL_PROC_S1_SIG_CONN_SETUP 4098 UE
initial UE message.
. . . .
. . . .
. . . .
Generated for the UE Context Release
procedure to release a UE Context. Contains
INTERNAL_PROC_UE_CTXT_RELEASE 4125 UE
information about the releasing node, cause
and bearer information.
Generate dfor the UE Context Modification

INTERNAL_PROC_UE_CTXT_MODIFY 4126 UE
procedure
‘INTERNAL_PROC_’ Example
203
RRC External Events
Event
Event Name Event Type Event Trigger
ID
RRC CONNECTION SETUP is

RRC_RRC_CONNECTION_SETUP 0 EXTERNAL
encoded
RRC CONNECTION REJECT is

RRC_RRC_CONNECTION_REJECT 1 EXTERNAL
encoded
. . .
. . .
. . .
RRC message sent when an UE

RRC_UE_INFORMATION_RESPONSE 26 EXTERNAL
responds to an UE Information request
RRC message sent when an UE

RRC_UE_INFORMATION_REQUEST 27 EXTERNAL
responds to an UE Information request
RRC External Event Example
204
S1 External Events
Event
ID
when protocol message

S1_DOWNLINK_S1_CDMA2000_TUNNELING 1024 EXTERNAL
is received
when protocol message

S1_DOWNLINK_NAS_TRANSPORT 1025 EXTERNAL
. . . is received
. . .
. . .
MME
S1_KILL_RESPONSE
S1_KILL_RESPONSE 1079 EXTERNAL
sent, 3GPP 36.413
S1_ERAB_RELEASE_
S1_ERAB_RELEASE_INDICATION 1080 EXTERNAL INDICATION sent. See
3GPP 36.413
S1 External Event Example
205
X2 External Events
Event
ID
when protocol message is

X2_RESET_REQUEST 2048 EXTERNAL
received or sent

X2_RESET_RESPONSE 2049 EXTERNAL
received or sent
. . .
. . .
. . .

X2_UE_CONTEXT_RELEASE 2061 EXTERNAL
received or sent

X2_HANDOVER_PREPARATION_FAILURE 2062 EXTERNAL
received or sent
X2 External Event Example
206
PM Event Descriptions
Trace Decoding Example 1
207
Trace Decoding Example 2
RSRP Decoding (TS36.133)
Reported value = 30
Measured quantity value = (30 - 141) ≤ RSRP < (30 - 140) dBm
= - 111 ≤ RSRP < - 110 dBm
208
Timing Advance
Perfect UL timing
0.30us
16Ts = 0.52us 16Ts = 0.52us
Timing Advance = 32 NTA,new = NTA,old + (TA -31)x16

= NTA,old + (32 -31)x16
= NTA,old + 16
UE transmits data 0.52usec earlier
0.22us
16Ts = 0.52us 16Ts = 0.52us
Timing Advance in LTE Cell

Trace
INTERNAL_PER_RADIO_UE_MEASUREMENT_TA {
EVENT_PARAM_TIMESTAMP_HOUR 11,
EVENT_PARAM_TIMESTAMP_MINUTE 42,
EVENT_PARAM_TIMESTAMP_SECOND 52,
EVENT_PARAM_TA_INTERVAL 1000,
EVENT_PARAM_TIMESTAMP_MILLISEC 291,
EVENT_PARAM_SCANNER_ID 131072,
EVENT_ARRAY_TA 304,
EVENT_PARAM_RBS_MODULE_ID EVENT_VALUE_MASTER_DU (0),
EVENT_PARAM_GLOBAL_CELL_ID 36017422, EVENT_ARRAY_TA 304, UE Distance from eNodeB
EVENT_PARAM_ENBS1APID 485,
EVENT_PARAM_MMES1APID 168822750, EVENT_ARRAY_TA 304, =(304 X 3.25 X 10-8 X 3 x 108)/2
EVENT_ARRAY_TA 304, = 1482 m
EVENT_PARAM_GUMMEI '00 62 F2 20 EE BB 73'H,
EVENT_PARAM_RAC_UE_REF 121241662,
EVENT_PARAM_TRACE_RECORDING_SESSION_REFERENCE '00 14 CD'H,
EVENT_PARAM_TIMESTAMP_START_HOUR 11, EVENT_ARRAY_TA 304,
EVENT_ARRAY_TA 320, UE Distance from -8

eNodeB
EVENT_PARAM_TIMESTAMP_START_MINUTE 42,
EVENT_PARAM_TIMESTAMP_START_SECOND 43,
EVENT_PARAM_TIMESTAMP_START_MILLISEC 291, =(320 X 3.25 X 10 X 3 x 108)/2
EVENT_PARAM_TA_INTERVAL 1000, EVENT_ARRAY_TA 320, = 1560 m
EVENT_ARRAY_TA 304,
EVENT_ARRAY_TA 304, EVENT_ARRAY_TA 336, UE Distance from eNodeB
EVENT_ARRAY_TA 304,
EVENT_ARRAY_TA 304, EVENT_ARRAY_TA 336, =(336 X 3.25 X 10-8 X 3 x 108)/2
EVENT_ARRAY_TA 304,
EVENT_ARRAY_TA 320, EVENT_ARRAY_TA 336, = 1638 m
EVENT_ARRAY_TA 320,
EVENT_ARRAY_TA 336,
EVENT_ARRAY_TA 336,
EVENT_ARRAY_TA unavailable,
EVENT_ARRAY_TA 336, Connection released
EVENT_ARRAY_TA unavailable, EVENT_ARRAY_TA unavailable,
EVENT_ARRAY_TA unavailable,
(‘EVENT_ARRAY_TA’ X 3.25 x 10-8 X 3 x 108

UE distance from eNodeB = [m]
2
209
Student_Event_Decoder
Cell Trace File Naming

Convention
<A><start_date>.<start_time>-<end_time>_CellTrace_DUL<No>_<RC>.bin.gz
A Single Network Element and single recording or granularity period (always set to ‘A’)
start_date YYYYMMDD
start_time HHMM (UTC or Local Time)
end_time HHMM (UTC or Local Time)
No Indicates the number of the DUL with one digit.
RC Set to “1” for “normal Cell Trace data and “2” for high priority Cell Trace data
Example 1 (UTC):
A20100127.0815-0830_CellTrace_DUL1_1.bin.gz
(ROP file recorded between 08:15 and 08:30 UTC on 27/01/2010)
Example 2 (Local Time):

A20100127.0915+0100-0930+0100_CellTrace_DUL1_1.bin.gz
(ROP file recorded between 09:15 and 09:30 local time on 27/01/2010 where the local time is UTC +1)
210
Cell Trace File Collection and
Storage
OSS-RC file system
/var/opt/ericsson/nms_umts_pms_seg/segment1/CELLTRACE
/SubNetwork=LTEKi
/MeContext=kienb4001
A20140127.0915+0100-0930+0100_SubNetwork=ONRM_ROOT_MO,
SubNetwork=LTEKi,MeContext=kienb4001_celltracefile_1.bin.gz
eNodeB file System

/C
/pm_data 5 min
A20140127.0815-0830_CellTrace_DUL1_1.bin.gz
UE Trace File Naming

Convention
<A><start_date>.<start_time>-<end_time>_uetrace_<TraceRef>.bin.gz
A Single Network Element and single recording or granularity period (always set to ‘A’)
start_date YYYYMMDD
start_time HHMM (UTC or Local Time)
end_time HHMM (UTC or Local Time)
TraceRef The Trace Reference to start the UE Trace, received either from the CN or from
another RBS at handover.
Example 1 (UTC):
A20140127.0815-0830_uetrace_272F0110010000001.bin.gz
(ROP file recorded between 08:15 and 08:30 UTC on 27/01/2014)
Example 2 (Local Time):
A20140127.0915+0100-0930+0100_uetrace_272F0110010000001.bin.gz
(ROP file recorded between 09:15 and 09:30 local time on 27/01/2014 where the local
time is UTC +1)
211
UE Trace File Collection and
Storage
OSS-RC file system
/var/opt/ericsson/nms_umts_pms_seg/segment1//UETRACE/272F0110010000001
/SubNetwork=LTEKi
/MeContext=kienb4001
A20140127.0915+0100-0930+0100_SubNetwork=ONRM_ROOT _MO,SubNetwork=
LTEKi,MeContext=kienb4001__272F0110010000001_234151234567890_uetracefile.bin
eNodeB file System

/C
/pm_data 5 min
A20140127.0815-0830_uetrace_272F0110010000001.bin.gz
RBS Event Streaming
UE Trace Cell Trace

UDP Header TCP Header
Event Event
Event Event
UDP Package border
Decoder
Event
UDP Header
Event TCP Header
Event IP Address: 10.20.30.10
Event
Port: 20
UDP Package border
212
Trace Depth
Recording entire signalling messages plus any vendor
specific extensions to this definition, in encoded format.
Recording of some IEs in the signalling messages plus any

vendor specific extensions to this definition, in decoded format.
Recording of some IEs in the signalling

messages together with the radio
measurement IEs plus any vendor
specific extensions to this definition, in
decoded format.

messages in decoded format.

messages together with the radio
measurement IEs in decoded format.
Recording entire signalling messages in encoded format.
Performance Management
Description
213

7. Explain what is collected by LTE Cell and UE Trace
7.1 Explain briefly how LTE Cell and UE Trace are collected and
stored
Thank You
214
LTE Performance
Management and
Optimization
OSS-RC Statistics, Cell and UE Trace Handling

8. Use the OSS-RC to collect E-UTRAN counters and handle LTE
Cell and UE Trace
8.1 Create, activate and delete subscription profiles
8.2 Use the OSS-RC to open and view the contents of LTE Cell
and UE Trace files
215
Launching Data Collection
GUI
System Defined Subscription

Profiles
Right-Click
216
Performance Monitorings
(Scanners)
Scanner associated with ‘System ERBS PRIMARY’

subscription profile
User Defined Subscription

Profiles
Profile limits
217
User Defined Profile Limits
Subscription Profile Wizard
218
LTE RAN Subscription Profile
Steps
(Plug and Play)
Select UE
Select Select
Fraction
Output Events
(1...1000)
Mode Select
Cells*
*Individual cell(s) may not be selected,

Cell Trace all cells per LTE RBS must be selected
Start Finish
Choose Enter User Statistics
Select Select Set up
Profile Name & eRBS(s) Counters Schedule
Type Comment
UE Trace Enter
Select
UE Trace
Interfaces
Parameters
Subscription Profile Schedule
Continuous
Data will be collected for as
long as the profile is activated.
(statistics profiles only)
Scheduled
Data will be collected for the
specified duration (days,
hours and minutes) when the
profile is activated.
Periodic
Data will be collected for the
specified duration (days, Periodic Scheduled Continuous
hours and minutes) when the
profile is activated. The profile Statistics YES YES YES
will be activated on the Cell trace YES YES NO
specified start data and time.
UE trace YES NO NO
219
Subscription Profile Help
Subscription Profile User

Guide
220
Network Status Display
Traffic Recordings View
221
Exporting Cell and UE Trace
Real Time KPIs in NSD
222
KPI Visualization
details
results
Network Status Display Help
223
Network Status Display User
Guide

8. Use the OSS-RC to collect E-UTRAN counters and handle LTE
Cell and UE Trace
8.1 Create, activate and delete subscription profiles
8.2 Use the OSS-RC to open and view the contents of LTE Cell
and UE Trace files
224
Thank You
225
LTE Performance
Management and
Optimization
Advanced MO Scripting (AMOS)

9. Open an AMOS session
9.1 Use AMOS to perform basic Performance Management operation
226
AMOS User Guide
AMOS Introduction
NODE
CORBA-CM
(pget, pdiff)
MIB
CORBA-PM
(pst,pgets,pcr,etc.)
Statistics
AMOS Scanner
Events
Scanner
XML
FTP/SFTP ROP file
(pmr,pmx,pme) Binary
ROP file
227
Starting AMOS
1 Right-Click on Common Explorer > Launch
‘lc’ Command
Load MO tree (full or partial) and build proxy table.

MUST BE PERFORMED BEFORE OTHER COMMANDS!
228
‘pr’ Command
Print MOs that contain
‘eutrancell’ in the name
Print MO LDNs and proxy ids for all or part of the

MO tree currently loaded in AMOS.
‘get’ Command (using Proxy)

Read attributes of Proxy 529
Read CM/FM attribute(s) from MO(s).
229
‘get’ Command (Using Proxy
and Attributes)
Read attributes of Proxy 529 that contain ‘state’
Read CM/FM attribute(s) from MO(s).
‘set’ Command
Set ‘administrativeState’ attribute of Proxy 529 to ‘0’ (Locked)
Set an attribute value on one or several MOs.
230
‘ue print – admitted’ Command
AMOS PM Commands
eg. h pmom <RETURN> will give help on pmom command
‘p’ <RETURN> shows list of PM commands
231
‘pst’ Command
List all PM scanners and their state.
‘pgets’ Command
Scanner ‘PROXY’ number used
Print scanner contents.
232
‘pmom’ Command
Print description of PM counters.
‘pmx’ Command (Single ROP)
rbs
Password is required as AMOS needs to

connect to the node to retrieve the XML files
Display counter values, extracted from the statistics ROP files.
233
‘pmx’ Command (Multiple ROP)
(-m 1 = go back 1 hour)
Display counter values, extracted from 4 ROP files (1 hour).
‘pget’ Command
Needs ‘lc’ command run first!
Counter incrementing
between commands
Read counter values directly from MO(s).
234
‘pdiff’ Command
Needs ‘lc’ command run first!
Counter incremented
by 31 in 30 seconds
Shows how counter values have
incremented in the last 30 seconds.
‘pmr’ Command
Location of KPI Formulas
Produce PM KPI reports, based on counter values in statistics

ROP files and formulas in CPI documentation.
235
ERBS EutranCell Traffic
Performance, ROP by ROP

9. Open an AMOS session
9.1 Use AMOS to perform basic Performance Management operation
236
Thank You
237

LTE Protocol, Procedure, Performance Management &amp; Optimization Training Material

Uploaded by

Copyright:

Available Formats

You might also like

LTE Protocol, Procedure, Performance Management &amp; Optimization Training Material

Uploaded by

Document Information

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

LTE Protocol, Procedure, Performance Management &amp; Optimization Training Material

Uploaded by

Copyright:

Available Formats

LTE Protocols, Procedures, Air Interface,

Performance Management & Optimization

LTE Protocols and

EPS Protocols Introduction

After this chapter the participants will be able to:

LTE Air Interface Features Overview

scalable Short TTI = 1 ms

Control Plane PGW: Packet Data Network Gateway

X2 MME: Mobility Management Entity

33.401 – System Architecture Evolution (SAE);

All specifications can be found on the

EPS Bearer External Bearer

E-RAB S5/S8 Bearer

Data Radio Bearer S1 Bearer

Uu S1-U S5/S8 SGi

Dedicated Bearer: Established by network to allow flow of traffic between UE and

Tracking Area (TA)

UE eNodeB X2 MME S10 SGW PGW

X2AP X2AP GTP-C GTP-C

SCTP SCTP UDP UDP

eNodeB eNodeB MME MME

EPS User Plane Protocols

RLC RLC UDP UDP UDP UDP

UE eNodeB X2* SGW PGW

Radio Resource Control (RRC)

X2 Application Protocol (X2AP) Medium Access Control (MAC)

The students should now be able to:

Quality of Service and Security in LTE

After this chapter the participants will be able to:

Service Service Service Service Service Service

Quality of service: How the subscriber is

Security on Uu & S1 Interfaces

UE eNB S-GW P -GW Peer

EPS Bearer External Bearer

E-RAB S5/S8 Bearer

Radio Bearer S1 Bearer

Two Unicast EPS Bearers

Application / Service Layer

UL Traffic Flow Aggregates DL Traffic Flow Aggregates

1 2 100 ms 10-2 Conversational Voice

LTE/EPC/IMS Architecture example and

E-UTRAN EPC IMS

XCAP Default Bearer , QCI=8/9 MGw

Multiple Data Radio Bearer

SIGNALLING RADIO BEARER S1 BEARER

EPS BEARER QCI=5

Operator specific QoS parameters

QCI Prio LCG DSCP

Radio Network: Transport Network:

7 Stays the same

Mapping from QCI to DSCP and Pbits

Bearer QoS details from MME (QCI, MBR/GBR, ARP) Data

IP datagram DSCP Data

S1AP: Initial Context Setup Request

Default Bearer QoS

4 CoS 3 CoS 4 CoS 3 CoS

QCI6-Non-GBR TCP Specific Services AF32 28 4 2 2

DSCP = 12, P-bits = 0

DSCP to P-Bit Mapping

LTE Protocol, Procedure, Performance Management & Optimization Training Material

LTE Protocol, Procedure, Performance Management & Optimization Training Material

LTE Protocol, Procedure, Performance Management & Optimization Training Material