LTE Accessibility Opitimization Guide

LTE Accessibility
Optimization Guide
Agenda
eNB Accessibility Procedure
KPI and Parameters
Solution and Case Study
LTE Accessibility Optimization Guide| 2017-04-17 | Page 2

Scope and objectives
Scope
› eNB accessibility definition;
› Random access;
› Initial E-RAB setup procedure;
› Accessibility KPI;
Objectives
Upon completion of this course, you will be able
to:
› Measure LTE accessibility performance;
› Describe the random access procedure;
› Describe the E-RAB setup procedure and
associated counters;
› Use eNB counters to create E-RAB accessibility
KPIs;

agenda
› Accessibility Definition;
› Random Access;
› RRC Connection Establishment;
› S1 Signaling Connection Establishment;
› Initial E-RAB Establishment or E-RAB Addition;
› Accessibility KPI

Accessibility Definition
› Accessibility for the EUTRAN is a measure of the ability of
a user to obtain an E-RAB from the system.
› The initial E-RAB establishment process can be divided

into the following phases:
– RRC Connection Establishment
– S1 Signaling Connection Establishment
– Initial E-RAB Establishment or E-RAB Addition

MME
*
1. System Information
Cell
Select *
LTE Call Flow
RRC IDLE 2. Random Access Preamble
3. Random Access Response
Random Access
4. RRC CONNECTION REQUEST
5. RRC CONNECTION SETUP RRC Conn Estab

6. RRC CONNECTION SETUP COMPLETE (Attach Request)
7. INITIAL UE MESSAGE (Attach Request)
S1 Signaling
Conn Estab 8.RRC DL INFORMATION TRANSFER (UE Identity Request) DL NAS TRANSFER (UE Identity Req)
9. RRC UL INFORMATION TRANSFER (UE Identity Response) UL NAS TRANSFER (UEid Response)
10.RRC DL INFORMATION TRANSFER (Authentication Request) DL NAS TRANSFER (Authentication)
11. RRC UL INFORMATION TRANSFER (Authentication Response) UL NAS TRANSFER (Auth. Response)
12. RRC DL INFORMATION TRANSFER (Security Mode Command) DL NAS TRANSFER (NAS SMC)
13. RRC UL INFORMATION TRANSFER (Security Mode Complete) UL NAS TRANSFER (NAS SMC)
14. INITIAL CONTEXT SETUP REQUEST
15. RRC SECURITY MODE COMMAND (EPS bearers, Attach Accept, Security)
16.RRC SECURITY MODE COMPLETE
17. RRC UE CAPABILITY ENQUIRY
E-RAB 18. RRC UE CAPABILITY iNFORMATION

Establishment 20. RRC CONNECTION RECONFIGURATION (Bearer Setup)
19. UE CAPABILITY INFO INDICATION
(UE Radio Capability)
21. RRC CONNECTION RECONFIGURATION COMPLETE
22. INITIAL CONTEXT SETUP RESPONSE
(EPS bearers)
23. RRC UL INFORMATION TRANSFER (Attach Complete)) UL NAS TRANSFER (Attach Complete)
24. UE CONTEXT RELEASE COMMAND

RRC IDLE
26. RRC CONNECTION RELEASE 25. UE CONTEXT RELEASE COMPLETE

agenda
› Random Access;
› Accessibility KPI
Random access
› This is a preliminary process that occurs whenever the UE needs to get
the initial access to the system and affects directly accessibility;
› It is used in the following scenarios:
– UE in RRC_CONNECTED state but not UL-synchronized
› To send new UL data or control info
- Event-triggered measurement report
› To receive new DL data, and therefore to transmit corresponding ACK/NACK in
the UL
– UE in RRC_CONNECTED state
› Performing HO from its current serving cell to a target cell.
› For positioning purposes, when timing advance is needed for UE positioning
– UE performing transition from RRC_IDLE state to RRC_CONNECTED state
› For initial access or tracking area updates.
› Recovering from radio link failure.
› Two types of RA procedures are defined in the standard for FDD
– CBRA (Contention Based Random Access)
– CFRA (Contention Free Random Access)

Random access
cbra
BCCH: System Information
RRC RRC
UE randomly selects one of the available preambles (max 64 in 1 or 2
groups) and sends it with preambleInitialReceivedTargetPower
PRACH: Preamble
MAC MAC
If no answer is received within ra-ResponseWindowSize preamble is sent again with

preambleInitialReceivedTargetPower + powerRampingStep
PRACH: Preamble
MAC MAC
eNodeB MAC entity allocates

TC-RNTI (in some cases)
PDCCH: RA-RNTI; Scheduling Grant;TA
DL-SCH: RACH response (RAPID; TC-RNTI)
MAC MAC
If the UE sees its RAPID it responds

RRC Connection Request is not sent in all
PUSCH: TC-RNTI
UL SCH: RA message3
Random Access cases
CCCH: RRC Connection Req (Initial 48 bit UE ID, Est Cause)
RRC MAC MAC RRC
Random access
CBRA
PDCCH: TC-RNTI; Scheduling Grant

DL-SCH: C-RNTI; Contention Resolution
RRC MAC MAC RRC
CCCH: RRC Connection Setup
(SRB1 parameters)
The 48-bit MAC "UE contention resolution ID" should

be identical to the one sent in RA message 3.
UL-SCH: C-RNTI; BSR

RRC MAC MAC RRC
DCCH: RRC Connection Setup Complete
(Selected PLMN id, NAS: Attach Request
Use TC-RNTI to decode DL SCH. If the UE contention

resolution ID MAC control element matches the one sent in
the RAmsg3 message, promote TC-RNTI to C_RNTI.

Random access
CFRA
›Used with Incoming handover
› UE uses RACH of dedicated configuration
› UE is assigned preamble in asignaling message sent in the serving cell.
›Used for 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.
› UE is assigned preamble via PDDCH
›Benefits in High RACH load scenarios:
› It avoids contention by dedicating resources (preambles) for UE to use for
random access.
› It reduces access latency
› Reduces the interrupt time for handover
› Reduces packet drops in user plane.
› Reduced access delay
› Reduced need for PRACH resources
›CFRA is disabled by default for all cells but can be enabled in any cell by
settingLTEthe cfraEnable parameter to true. (currently false in our network)
Accessibility Optimization Guide| 2017-04-17 | Page 12
Random access
CFRA (HO case)
PDCCH or
DL-DCCH: RRC Connection Reconfiguration
RRC RRC
UE sends given preamble at preambleInitialReceivedTargetPower
PRACH: Preamble
MAC MAC
If no answer is received within ra-ResponseWindowSize preamble is sent again with

preambleInitialReceivedTargetPower + powerRampingStep
PRACH: Preamble
MAC MAC
PDCCH: RA-RNTI; Scheduling Grant; TA

DL-SCH: RACH response (RAPID; TC-RNTI)
MAC MAC
PUSCH: C-RNTI
UL SCH: RA message3 (BSR, PHR)
MAC MAC
Random access
parameters
Parameter Description
rachRootSequence First root sequence number for RACH preamble generation
RACH root sequence is broadcast as a part of system

information distribution and used for preamble detection.
cellRange Defines the maximum distance from the RBS where a
connection to a UE can be setup or maintained, or both
cfraEnable This parameter is used to enable or disable the CFRA

Random access
counters
Counter Description
pmRaAttCbra The number of detected CBRA preambles in the cell.
pmRaSuccCbra The number of successfully detected RA Message 3 for CBRA.
pmRaAttCfra The number of detected CFRA preambles in the cell.
pmRaSuccCfra The number of successfully detected RA Message 3 for CFRA.
pmRaAllocCfra The number of allocated CFRA preambles in the cell.
The number of detected CFRA preambles that are not allocated to

pmRaUnassignedCfraFalse any UE.
The total number of unassigned CFRA preambles at each PRACH

pmRaUnassignedCfraSum activity.
The number of CBRA preambles for which no random access

response (RA Msg2) was sent due to expiry of the random access
response window.
pmRaFailCbraMsg2Disc
The number of CFRA preambles for which no random access
response (RA Msg2) was sent due to expiry of the random access
response window.
pmRaFailCfraMsg2Disc

Random access
Flow chart
CBRA CFRA
agenda
› Random Access;
RRC Connection Establishment
› The RRC connection is a dedicated connection used for
control signaling between the EUTRAN and one UE;
› Reasons for RRC connection establishment:

– Receive a paging message (idle mode UE);
– Tracking area update;
– Going to setup a session;
› Signaling Radio bearers SRB0,SRB1 and SRB2 are used

for the transmission of RRC messages.

Signaling Radio Bearers

Procedure
Idle Mode
RRC CONNECTION REQUEST (ue-Identity: S-TMSI or random

value between 0 and 2^40 – 1; establishmentCause)
pmRrcConnEstabAtt +
RRC CONNECTION REQUEST
pmRrcConnEstabReatt +
SRB 0
RRC CONNECTION SETUP (CCCH)

Information needed to
set up SRB1 on DCCH
Connected mode
RRC CONNECTION SETUP COMPLETE (selected PLMN-identity;

registeredMME; dedicatedInfoNAS)
SRB 1 pmRrcConnEstabSucc +

connection reject
RRC CONNECTION REQUEST (ue-Identity: S-TMSI or random

value between 0 and 2^40 – 1; establishmentCause)
pmRrcConnEstabAtt +
RRC CONNECTION REQUEST
pmRrcConnEstabReatt +
SRB 0
RRC CONNECTION REJECT (wait time)
› The eNodeB may reject the request of RRC connection establishment based on its radio
resource management (RRM) algorithm;
› Upon sending RRC CONNECTION REQUEST message, UE starts the T300 timer. If the
UE does not receive either the RRC connection setup message or the RRC connection
reject message before the expiry of timer T300, the RRC connection establishment
procedure is terminated;
› Upon receiving an RRC Connection Reject message, the UE starts the T302 timer with
its value set equal to the wait time. T302 is stopped if the UE completes cell reselection.
In that case, the UE is permitted to send an RRC Connection Request to the new cell

counters

Flow chart

agenda
› Random Access;
S1 Signaling connection establishment
› After RRC connection setup, the logical S1 connection is

established;
› Used to perform authentication with the MME and setup

the EUTRAN security functions;
› UE is identified and authenticated by MME using the S1

signaling connection establishment;
› S1 signaling connection failure is mainly due to the

authentication failure of UE in MME.

MME
RRC CONNECTION SETUP COMPLETE

Piggybacked NAS ‘Attach Request’
INITIAL UE M ESSAGE
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

counters

Flow Chart

agenda
› Random Access;
Initial E-RAB Establishment
› The Initial Context Setup procedure is triggered by the MME by
sending the INITIAL CONTEXT SETUP REQUEST to the eNB. This
message includes a list of E-RABs to be setup;
› If the resources are available for the requested configuration, the eNB
shall allocate resources for the first Data Radio Bearer (DRB), and
execute the requested E-RAB configuration by sending a RRC
CONNECTION RECONFIGURATION message to the UE;
› The UE responds with RRC CONNECTION RECONFIGURATION
COMPLETE and the procedure is completed after the eNB has sent
INITIAL CONTEXT SETUP RESPONSE to the MME.

procedure
MME
Authentication and security mode procedures

pmErabEstabAttInit + INITIAL CONTEXT SETUP REQUEST
pmErabEstabAttInitQci + Includes a list of E-RABs to be setup
RRC CONNECTION RECONFIGURATION
Contains info needed to setup RB

RRC CONNECTION
RECONFIGURATION COMPLETE
pmErabEstabSuccInit + INITIAL CONTEXT SETUP RESPONSE
pmErabEstabSuccInitQci +

Added E-RAB establishment
› The MME can add additional E-RABs to the connection, and initiates
the procedure by sending an E-RAB SETUP REQUEST message to
the eNB;
› The eNB uses the E-RAB Setup Request to configure itself for the
added bearer. The RRC Connection Reconfiguration message
provides the UE with information necessary to configure the added
bearer

E-RAB establishment
counters (1/2)

E-RAB establishment
counters (2/2)

flow chart (include S1)

Added E-RAB establishment
flow chart

agenda
› Random Access;
Accessibility KPI
RRC S1 E-RAB

Agenda
KPI and Parameters
Solution and Case Study

Accessibility Solution and
Case Study
Scope and objectives
Scope
› LTE accessibility investigation;
› Accessibility optimization methods;
› Accessibility case study;
Objectives
Upon completion of this course, you will be
able to:
› Describe reasons for RA failure; RRC
failure; S1 failure, and E-RAB failure;
› Know solutions of accessibility issues;
› Build up troubleshooting skills by case
studying from both True live network and
other markets;
agenda
› Accessibility Optimization;
– Random Access;
– RRC Connection Establishment;
– S1 Signaling Connection Establishment;
– Initial E-RAB Establishment or E-RAB Addition;
› Case Study

Random Access Optimization
› Possible reasons for RACH failure:
– Improper RA preamble planning;
– Poor RF condition;
– High uplink interference;
– Sleeping cell;
› solutions:
– For current cell range setting (15km), the parameter rachRootSequence
should differ at least 10 between any two neighbors;
– Check for poor RF conditions. Increase the coverage area by adjusting
Tilt/Azimuths of self/neighbor sites;
– Due to UL interference, RBS can not detect/decode the request sent by UE.
For how to monitor and minimize UL interference, check session3 &
session5;
– Sleeping cell is hard to detect. When there are many RA attempt, but none
successes (high pmRaFailCbraMsg2Disc), the cell is considered a sleeping
one. Try to lock/unlock the cell, or restart;
Optimization
› Possible reasons for RRC failures:
– RRC rejects due to lack of license (pmRrcConnEstabFailLic );
– RRC rejects due to high load or overload
(pmRrcConnEstabFailHighLoad/pmRrcConnEstabFailOverload );
– Improper parameters setting;
– Poor RF conditions (pmbadcovevalreport/pmRrcConnEstabAttReatt);
– High UL interference;
– Sleeping cell
– Hardware issue / Alarms

Optimization
› Solutions:
– Lack of license:
› Load new LKF;
› Offload traffic to neighbor cells / 3G (adjusting coverage,
changing mobility parameters);
› Add new site;
– High load / overload:
› Offload traffic to neighbor cells / 3G;
› Reduce dlMaxRetxThreshold & ulMaxRetxThreshold of SRB1;
› Raise qRxLevMin;

Optimization
› Solutions:
– Improper parameter setting:
› Apart from the above mentioned parameters, if UE camps in
wrong cell, parameters for cell reselection can be tuned;
– Poor RF condition / High UL interference / Sleeping cell:
› Same solution as in RA optimization;
– Hardware issue / Alarms:
› Check for the Major & Critical Hardware alarms, VSWR &Return
Loss issues in the sources as well as neighbor cells.

S1 Establishment Optimization
› Possible reasons for S1 failures:
– Transport issue: normally results in Service Unavailable alarm;
– Software error: e.g., “eNB_UE_S1AP_ID” is not recognized by the MME;
– Wrong TAC-LAC mapping: happen during CSFB;
› Solutions:
– Needs to be investigated and resolved with the help of transport team;
– Lock the TermPointToMme, wait 5 seconds then unlock the
TermPointToMme;
– Restart the eNB;
– Check the TAC-LAC table, and make sure the mapping is correct.

E-rab setup optimization
› Possible reasons for E-RAB failures:
– License issue;
– eNB issue;
– UE issue;
› Solutions:
– If there are more than one E-RAB required for one UE, check the feature
Multiple Radio Bearer per user is activated or not;
– Check RLC UM feature if the failed E-RAB establishment requires UM
mode;
– ERAB failures can happen due to an UE issue or due to hanging resources
in the ENB or an RRU issue;
– With regards to hanging resources in ENB – a restart normally helps. With
regards to faulty RRU’s – if restarting the RRU doesn’t help, replacing the
RRU is the option.
– To find out particular UE issue, We need to analyze CTR & EBM(MME).
agenda
› Accessibility Optimization;
– Random Access;
– RRC Connection Establishment;
– S1 Signaling Connection Establishment;
– Initial E-RAB Establishment or E-RAB Addition;
› Case Study

Case1: UL interference
KPI for Cell CCL04145

Case2: RRC Failure

Case3: S1 failure
Probably the MME is not getting the message from eNB and that’s due to S1 link losing the
message before it gets to MME. As long failure happens few times only then MME is not
suspected of having wrong configuration.
Action : Need S1 link investigation and a confirmation from MME team.

Case4: E-RAB failure
– CCL00703 Gamma sector has a high number of ERAB failures. RRC rate and S1
success rate is good.

Case4: E-RAB failure
All Access failures in the Gamma sector are due to one UE with the IMSI
310410426878445.

Q&A

time SPEND IN ACCESS PROCESS

LTE Accessibility Opitimization Guide

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 Accessibility Opitimization Guide

Uploaded by

Copyright:

Available Formats

LTE Accessibility

eNB Accessibility Procedure

KPI and Parameters

Solution and Case Study

LTE Accessibility Optimization Guide| 2017-04-17 | Page 2

LTE Accessibility Optimization Guide| 2017-04-17 | Page 4

› RRC Connection Establishment;

› S1 Signaling Connection Establishment;

› Initial E-RAB Establishment or E-RAB Addition;

LTE Accessibility Optimization Guide| 2017-04-17 | Page 5

› The initial E-RAB establishment process can be divided

LTE Accessibility Optimization Guide| 2017-04-17 | Page 6

5. RRC CONNECTION SETUP RRC Conn Estab

10.RRC DL INFORMATION TRANSFER (Authentication Request) DL NAS TRANSFER (Authentication)

17. RRC UE CAPABILITY ENQUIRY

E-RAB 18. RRC UE CAPABILITY iNFORMATION

24. UE CONTEXT RELEASE COMMAND

LTE Accessibility Optimization Guide| 2017-04-17 | Page 7

› RRC Connection Establishment;

› S1 Signaling Connection Establishment;

› Initial E-RAB Establishment or E-RAB Addition;

LTE Accessibility Optimization Guide| 2017-04-17 | Page 9

If no answer is received within ra-ResponseWindowSize preamble is sent again with

eNodeB MAC entity allocates

If the UE sees its RAPID it responds

PDCCH: TC-RNTI; Scheduling Grant

The 48-bit MAC "UE contention resolution ID" should

UL-SCH: C-RNTI; BSR

Use TC-RNTI to decode DL SCH. If the UE contention

LTE Accessibility Optimization Guide| 2017-04-17 | Page 11

UE sends given preamble at preambleInitialReceivedTargetPower

If no answer is received within ra-ResponseWindowSize preamble is sent again with

PDCCH: RA-RNTI; Scheduling Grant; TA

RACH root sequence is broadcast as a part of system

cfraEnable This parameter is used to enable or disable the CFRA

LTE Accessibility Optimization Guide| 2017-04-17 | Page 14

pmRaAttCbra The number of detected CBRA preambles in the cell.

pmRaSuccCbra The number of successfully detected RA Message 3 for CBRA.

pmRaAttCfra The number of detected CFRA preambles in the cell.

pmRaSuccCfra The number of successfully detected RA Message 3 for CFRA.

pmRaAllocCfra The number of allocated CFRA preambles in the cell.

The number of detected CFRA preambles that are not allocated to

The total number of unassigned CFRA preambles at each PRACH

The number of CBRA preambles for which no random access

LTE Accessibility Optimization Guide| 2017-04-17 | Page 15

› RRC Connection Establishment;

› S1 Signaling Connection Establishment;

› Initial E-RAB Establishment or E-RAB Addition;

› Reasons for RRC connection establishment:

› Signaling Radio bearers SRB0,SRB1 and SRB2 are used

LTE Accessibility Optimization Guide| 2017-04-17 | Page 18

LTE Accessibility Optimization Guide| 2017-04-17 | Page 19

RRC CONNECTION REQUEST (ue-Identity: S-TMSI or random

RRC CONNECTION SETUP (CCCH)

RRC CONNECTION SETUP COMPLETE (selected PLMN-identity;

LTE Accessibility Optimization Guide| 2017-04-17 | Page 20

RRC CONNECTION REQUEST (ue-Identity: S-TMSI or random

RRC CONNECTION REJECT (wait time)

LTE Accessibility Optimization Guide| 2017-04-17 | Page 21

LTE Accessibility Optimization Guide| 2017-04-17 | Page 22

LTE Accessibility Optimization Guide| 2017-04-17 | Page 23

› RRC Connection Establishment;

› S1 Signaling Connection Establishment;

› Initial E-RAB Establishment or E-RAB Addition;