Anda di halaman 1dari 85

LTE Access Fault

Diagnosis

www.huawei.com

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.


Objectives
 Upon completion of this course, you will be able to:
 Get deep understanding of UE initial access flow

 Describe the typical access fault scenarios

 Describe how to locate the access fault

 Typical methods for fault analysis

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page1
Contents
1. EUTRAN Typical Signaling Procedure

2. Common Access Problem and Influence Factors

3. Access Problem Analysis and Case Study

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page2
UE Initialization Flow UE power on
PLMN Selection

Cell Search

UE idle
System
behavior phase
message
reception

Cell Selection
Invisible flow

Partial visible flow


Random Acces Visible flow
UE access
phase
UE Initial Attach

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page3
UE Initial Attach Procedure
eNodeB MME
UE
Uu:RRC/NAS S1-MME:S1AP

RA PREEMBLE
Random RA RESPONSE
Access
RRC_CONN_REQ

RRC RRC_CONN_SETUP
Connection
RRC_CONN_SETUP_CMP
S1AP_INITIAL_UE_MSG

NAS Procedure

S1AP_INITIAL_CONTEXT_SETUP_REQ
RRC_SECUR_MODE_CMD
RRC_SECUR_MODE_CMP
RRC_UE_CAP_ENQUIRY
E-RAB
Setup RRC_UE_CAP_INFO

RRC_CONN_RECFG
RRC_CONN_RECFG_CMP
S1AP_INITIAL_CONTEXT_SETUP_RSP

NAS Procedure

Dedicated E-RAB_SETUP_REQ
E-RAB RRC_CONN_RECFG
Setup RRC_CONN_RECFG_CMP
E-RAB_SETUP_RSP

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page4
Service Request Procedure
eNodeB MME
UE
Uu:RRC/NAS S1-MME:S1AP

RA PREEMBLE
Random RA RESPONSE
Access
RRC_CONN_REQ

RRC RRC_CONN_SETUP
Connection
RRC_CONN_SETUP_CMP
S1AP_INITIAL_UE_MSG

NAS Procedure (No authentication procedure)

S1AP_INITIAL_CONTEXT_SETUP_REQ
RRC_SECUR_MODE_CMD
RRC_SECUR_MODE_CMP
E-RAB
RRC_CONN_RECFG
Setup
RRC_CONN_RECFG_CMP
S1AP_INITIAL_CONTEXT_SETUP_RSP

NAS Procedure

Dedicated E-RAB_SETUP_REQ
E-RAB RRC_CONN_RECFG
Setup RRC_CONN_RECFG_CMP
E-RAB_SETUP_RSP

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page5
TAU Update Procedure eNodeB MME
UE

Uu:RRC/NAS S1-MME:S1AP
RA PREEMBLE
Random RA RESPONSE
Access
RRC_CONN_REQ

RRC RRC_CONN_SETUP
Connection
RRC_CONN_SETUP_CMP
S1AP_INITIAL_UE_MSG

DL NAS (TAU update accept )

S1AP_UE_CONTEXT_REL_CMD

RRC_REL
S1AP_UE_CONTEXT_REL_CMP

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page6
Random Access Procedure Overview
 Purpose of random access
 Get uplink synchronization
 Send schedule request if no PUCCH resource
 Scenarios:
 Case1: UE initial attach
 Case2: RRC reestablishment after RLF
 Case3: Handover in a new cell
 Case4: UE sends uplink data while RLF occurs
 Case5: UE notices that downlink data arrival while RLF occurs
 Case6: When UE trigger LCS(Location service)

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page7
Classification of Random Access
UE
eNodeB UE
eNodeB

Random Access Preamble Random Access Preamble


assignment
Random Access Response
Random Access Preamble
First scheduled UL
transmission
Random Access Response
Contention Resolution

Contention based Non-contention based

 UE randomly selects a  Before random access,


preamble and sends it, eNodeB assigns a dedicated
conflict might occurs preamble to UE, so there is

 Can be used for all cases no conflict.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page8
Preamble Index Configuration

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page9
Preamble Format
0 ms 1 ms 2 ms 3 ms

CP Sequence
0.1 Format 0
0.1 0.8

CP Sequence Guard Period


Format 1
0.68 0.8 0.52

CP Sequence Format 2
0.2
0.2 1.6

CP Sequence Guard Period


0.68 1.6 0.72 Format 3

5102 xTs

Format 4

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page10
Preamble Sending

 In contention based case, UE randomly select a preamble based


on RACH configuration and send it on the corresponding time slot

 Once the frequency and time is determined, the corresponding


RA_RNTI is already known by the UE, where RA_RNTI= 1 +
t_id+10*f_id (t_id indicates the start subframe number, f_id
indicate the frequency offset of RACH)

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page11
Random Access Response

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page12
UL Data Sending (Msg 3)

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page13
Contention Resolution
Contention Resolution message

PDCCH
(Scrambled by PDSCH
C-RNTI)

Case1: Detect C-RNTI Contention Resolution message


on PDCCH
PDCCH
(Scrambled by
temporary C- PDSCH (MAC PDU)
RNTI)

Case2: Detect temporary C-RNTI on PDCCH and


decode the corresponding MAC PDU on PDSCH.
In the MAC PDU, it contains the UE ID that send
in Msg 3

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page14
RRC Connection Setup Procedure
RRC Connection Request
RRC Connection Setup
UE Identity
Radio Resource Config Dedicated
Cause
- srb-ToAddModList
- drb-ToAddModList
- drb-ToReleaseList
UE eNB - MAC Main Config
RRC Connection Request - SPS Config
A
- Physical Config Dedicated
RRC Connection Setup
RRC Connection Setup Complete
B

RRC Connection Setup Complete


Selected PLMN-Identity
Registered MME
Dedicated Info NAS

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page15
RRC Cause
NAS Procedure RRC Cause Type of call
Attach MO – signaling Original signaling
TAU MO – signaling Original signaling
MO - data Original call
Service Request MT – access Terminated call
MO – data (original CSFB) Original call
MT – access (terminated CSFB) Terminated call
Extended Service
Request Emergency (emergency CSFB) Emergency call

 According to different NAS procedure, the RRC cause can


be MO-singling, MO-data, MT-access, and emergency

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page16
Initial ERAB Setup
eNodeB MME
UE
Uu:RRC/NAS S1-MME:S1AP

S1AP_INITIAL_UE_MSG

A S1AP_INITIAL_CONTEXT_SETUP_REQ
RRC_SECUR_MODE_CMD
RRC_SECUR_MODE_CMP

RRC_UE_CAP_ENQUIRY
RRC_UE_CAP_INFO
RRC_UE_CAP_INDICATION

RRC_CONN_RECFG

RRC_CONN_RECFG_CMP

B S1AP_INITIAL_CONTEXT_SETUP_RSP

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page17
S1 Initial UE Message

Initial UE M essage
eNB UE S1AP ID
NAS-PDU
TAI
E-UTRAN CGI
S-TMSI (O)
CSG Identity (O)
RRC Establishment cause
GUMMEI (O)
eNB MME
Initial UE Message

NAS PDU

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page18
S1 Initial Context Setup Request
Initial Context Setup Request
MME UE S1AP ID
eNB UE S1AP ID
UE Aggregate Maximum Bit Rate
E-RAB to Be Setup List
- E-RAB ID
- E-RAB Level QoS Parameters
- Transport Layer Address
- GTP-TEID
- NAS-PDU (O)
UE Security Capabilities
Security Key
Trace Activation (O)
Handover Restriction List (O)
UE Radio Capability (O)
Subscriber Profile ID for RAT/Frequency Priority (O)
CS Fallback Indicator (O)
SRVCC Operation Possible (O)

eNB MME

Initial Context Setup Request

Initial Context Setup Response NAS PDU

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page19
Security Mode Setup
Security M ode Command
Ciphering Algorithm
Integrity Protection Algorithm
UE eNB

Security Mode Command

Security Mode Complete


Security Mode Failure

 Purpose:
 Activated AS security algorithms, including integrity protect and ciphering
 Integrity protect: only for signaling, support AES, snow3G and Null
 Ciphering: both for signaling and data, support AES, snow3G and Null

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page20
UE Capability Query
eNodeB MME
UE

RRC_UE_CAP_ENQUIRY

RRC_UE_CAP_INFO

RRC_UE_CAP_INFO_IND

 If no UE capability in MME, eNodeB will trigger UE


capability query and store it and also inform MME
 If MME already stored UE capability, it will forward to eNode
via S1 initial contexts setup request message

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page21
SRB2 Setup

RRC Connection
Reconfiguration Request
Dedicated Info NAS
UE eNB Radio Resource Config Dedicated
RRC Connection Reconfiguration
- srb-ToAddModList
Request
- drb-ToAddModList
RRC Connection Reconfiguration - drb-ToReleaseList
Complete - MAC Main Config
- SPS Config
- Physical Config Dedicated

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page22
Measurement Control

RRC Connection Reconfiguration


Request
Measurement Configuration
UE eNB - measObjectToRemoveList
RRC Connection Reconfiguration - measObjectToAddModList
Request - reportConfigToRemoveList
- reportConfigToAddModList
RRC Connection Reconfiguration - measIdToRemoveList
Complete - measIdToAddModList
- quantityConfig
- measGapConfig
- s-Measure

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page23
S1 Initial Context Setup Response
Initial Context Setup Response
MME UE S1AP ID
eNB UE S1AP ID
E-RAB Setup List
- E-RAB ID
- Transport Layer Address
- GTP-TEID
E-RAB Failed to Setup List (O)
eNB Criticality Diagnostics (O) MME

Initial Context Setup Request

Initial Context Setup Response

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page24
NAS Procedure
eNodeB MME
UE

Attach request
PDN Connectivity Request
Authentication request
Authentication response
Attach accept
Activate default EPS bearer context request
Attach complete
Activate default EPS bearer context accept

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page25
Contents
1. EUTRAN Typical Signaling Procedure

2. Common Access Problem and Influence Factors

3. Access Problem Analysis and Case Study

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page26
Common Access Problem
Source Problem Identification Method
Low RRC establishment success 1. A KPI is below the baseline or required
rate value.
Or low E-RAB establishment 2. A KPI deteriorates after an upgrade.
success rate
Traffic Or low CSSR success rate
KPI Unstable RRC connection setup A KPI varies that of the previous day or the
success rate/ E-RAB connection same day of the previous week ( more than
setup success rate/CSSR 20%)
success rate
An abrupt increase or drop in Despite an abrupt increase or drop in the
access requests measured value of the number of RRC
connection setup attempts in a cell, the RRC
and E-RAB setup success rates are as the
same as normal and the measured value of
the maximum number of users in a cell
remains basically stable.
Sleeping cells No UEs can access a cell all of a sudden that
has been maintaining accessible or UEs of a
cell gradually reduces to zero.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page27
Common Access Problem (Cont.)
Source Problem Identification Method
Unsatisfactory call setup The drive test results show that the
KPI of success rate CSSR is below the baseline or required
driver test value.
Long attach delay The drive test results show that the
average attach delay is below the
baseline or required value.
Long Idle-to-Active Delay The drive test results show that the
average attach delay is below the
baseline or required value.
Complaints Failures of calls or data 1.No signal bar is displayed on a UE
services 2. Signal bars are displayed on a UE,
but the user still cannot make a call or
perform a data service.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page28
Common Factors of Access Fault
RF planning issues:
Resource issues
1.Wrong PRACH Coverage issues
1. Air interface
RF parameters 1.Weak coverage
resource limited
2.Improper TA 2.Cross converge
2.CPU overload
planning

Parameters issues RF channel & Transmission


Parameter 1.Wrong parameters Interference: issues
Common s& setting 1.High VSWR 1.Wrong parameter
Factors Channel 2.Improper setting ;
2.High RSSI/RSSI
parameters setting unbalance 2.High BER

EPC
eNodeB issues
UE issues: 1.Wrong
Device 1.eNodeB fault
1.Top UE problem subscription data
2.Sleeping cell
2.EPC abnormal

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page29
Contents
1. EUTRAN Typical Signaling Procedure

2. Common Access Problem and Influence Factors

3. Access Problem Analysis and Case Study

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page30
General Analysis Procedure
Step Prerequisit Purpose
e
Perform scope
1. Determine whether the problem is a top cell problem or
identification, KPI
network-wide problem.
trend analysis, None
2. Analyze the major causes of access failures and come up
and cause
with priority actions.
resolution
Checking 1.Check operation logs to identify parameter modification and
operation logs, operations that may cause problems.
device faults, None. 2. Check whether there are device faults that result in access
alarms, and problems or whether access-related alarms are reported.
external events
Checking 1.Analyze whether the core access parameters are proper on
None
parameters or consistent between the eNodeB and EPC.
Perform this 1. Check the access problem is caused by improper
action based configurations of parameters
Checking network on the 2. Check whether an access problem is caused directly by
planning and analysis resource congestions or indirectly by improper parameter
optimization results configurations.
provided by 3. Check whether an access failure is caused by weak
action 1. coverage.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page31
General Analysis Procedure (Cont.)
Action Prerequisite Purpose
For top cell 1. Check whether RF channels are normal.
Checking RF
problems, perform 2. Check for uplink interference
channels
this action.
For top-cell
1. Check whether access-related KPI deterioration
problems, check
Checking top UE happens on individual user(s).
top users.
types and top 2. Check whether the access problem is caused by a
For network-wide
users certain type of UEs.
problems, check
top UE types.
Perform this
action based on Check whether an access failure is caused by the EPC
Checking the
the analysis faults.
EPC
results provided
by action 1
Perform this
action based on
Checking Check whether the access failure is caused by
the analysis
transmission transmission faults.
results provided
by action 1.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page32
Relevant Data Source
 Performance Counters
 Performance counters can be obtained easily and allows data collection after
the event. However, it provides only a rough problem identification result.
 Performance counters help determine whether an access problem occurs in
the RRC connection setup phase or in the E-RAB connection setup phase and
the main causes of the problem. It can be used for rapid problem identification
and rough location of the fault NE.
 Trace signaling
 Signaling messages help accurately identify the phase in which an access
failure occurs, which is useful for checking compatibility problem of UEs and
the EPC and problems discovered during drive test and repeating an access
problem. It is good practice to perform signaling tracing over Uu and S1
interfaces on the faulty node on which an access problem is discovered by
analyzing performance counters and alarms or during drive tests.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page33
Relevant Data Source (Cont.)
 Drive Test Data
 The drive test data helps obtain the signal strength, scheduling
information (depending on drive test tools and UEs) of the UEs.
An access problem can be accurately identified by comparing
the drive test data with the signaling messages on the eNodeB
side.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page34
Action 1: Scope Identification
Data Analysis Method Solution
Sourc
e
Perfor 1. Identify the scope of the problem Continue to
mance 2. Identify whether the access problem occurs in perform other
Counte
rs the RRC connection setup phase or the E-RAB steps in action 1.
connection setup phase by analyzing the RRC
connection success rates and the E-RAB
connection success rates.
3. If the access problem occurs in the RRC
connection setup phase, collect the data of
RRC connection setup success rates in
different scenarios by the cause of the RRC
connection setup

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page35
Action 1: KPI Trend Analysis

Data Analysis Method Solution


Sourc
e
Perfor 1. Analyze KPI trend by day 1. If the KPI deteriorates suddenly,
mance 2. Analyze KPI trend by check whether the deterioration is
Counte hour caused by an upgrade, abnormal
rs 3. Analyze related KPIs: operations, external interference,
and burst of services.
2. If the KPI deteriorates gradually,
check whether the service volume is
increasing or a new type of UEs are
released.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page36
Action 1: Cause Resolution and KPI
Correlation
Procedure Access Criteria Description Prevaile
Failure Cause d Action
Random No UEs Cell status is normal and Sleeping cell None
access access the UEs access the network.
network. The following situation
suddenly or gradually
occurs:
L.Traffic.User.Max = 0 or
L.RRC.ConnReq.Att = 0
RRC L.RRC.SetupF L.Traffic.User.Max is close Resource congestion Check
success ail.Rej to or satisfy product congestio
rate specifications. n
deterioratio
RRC connection setup 1. PUCCH parameter configurations are Check
n
Reject contains limited. congestio
L.RRC.SetupFail.ResFail. 2. PUCCH resources fail to be n
PUCCH. expanded.
3. The number of UEs is large.
RRC connection setup The number of online UEs exceeds the Check
Reject contains CAPS specifications of a single eNodeB congestio
L.RRC.SetupFail.Rej.Flow and VS.BBUBoard.CPUload.Max is less n
Ctrl. than 80%.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page37
Action 1: Cause Resolution and KPI
Correlation (Cont.)
Procedure Access Criteria Description Prevailed Action
Failure
Cause
RRC .RRC.SetupF L.UL.Interference.Avg ≥ - 1. Interference exists. Check for
success ail.NoReply 105 2. Top users or UEs are interference.
rate abnormal. Check for exceptions
deterioratio on top users or UEs.
n BBP BBP The BBP CPU usage is Check for congestion
VS.Board.CP VS.Board.CPUload.Max high due to congestion
Uload.Max is is about 90%.
about 90%.
The L.RRC.Conn The number of RRC 1. TA planning is improper. Check parameter
number of Req.Att connections 2. NAS messages on the Check for EPC
RRC abruptly (L.RRC.ConnReq.Att) EPC are abnormal. exceptions.
connection increases. abruptly increases, the 3. UE processing is Check for exceptions
abnormal.
s abruptly RRC&E-RAB setup on top users or UEs.
increases. success rate is normal,
and L.Traffic.User.Max
does not suddenly
increase.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page38
Action 1: Cause Resolution and KPI
Correlation (Cont.)
Proce Access Criteria Description Prevailed Action
dure Failure
Cause
L.E- 1. E-RAB setup failures occur due to EPC Check for EPC
RAB.FailEst. exceptions. exceptions.
MME 2. The eNodeB does not receive any UE's Check for
response and the timer at the eNodeB air exceptions on top
None
interface and S1 interface is greater than users or UEs.
the context setup timeout timer on the
EPC. As a result, the EPC releases the
UE's context setup message earlier.
L.E- 1. IPPATH is not configured or incorrectly Check for
RAB.FailEst. configured. transmission
TNL None
2. The SCTP link is intermittently exceptions
E-RAB
disconnected.
setup
succes L.E- 1. Interference exists. Check for
s rate RAB.FailEst. L.UL.Interferenc 2. Top users or UEs are abnormal. interference.
deterio NoReply e.Avg ≥ -105
Check for
ration exceptions on top
users or UEs.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page39
Action 1: Cause Resolution and KPI
Correlation (Cont.)
Proce Access Failure Criteria Description Prevailed
dure Cause Action
L.E- 1. The system exceeds the license Check
RAB.FailEst.No capacity. congestion
RadioRes None
2. Parameter configurations are
E- incorrect.
RAB L.E- 1. The security mode configuration Check for
setup RAB.FailEst.Sec fails due to UE incompatibility. exceptions on
succe urModeFail 2. The EPC is abnormal. top users or
ss 3. eNodeB completeness or encryption UEs.
rate None
algorithms are incorrectly configured. Check for EPC
deteri exceptions
oratio
n

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page40
Action 2: Check Operation Log
Data Analysis Method Solution
Source
Operation Analysis method: Check whether
logs 1. Check for abnormal operations that may have the operation
(operation been performed a week before the can be rolled
logs of top deterioration occurs in a sudden KPI back. If yes,
10 sites for deterioration scenario. check whether
a network- 2. Check for abnormal operations that may have the KPI
wide been performed within the latest week in a improves after
problem and gradual KPI deterioration scenario. the rollback.
top 10 cells 3. Check for abnormal operations that may have
for a top-cell been performed at all sites if a problem occurs
problem) on the entire network.
4. Abnormal operations include but not limited to
addition, removal, blocking, activation, and
deactivation.
5. If an operation is performed in a batch fashion,
it needs to be checked on the M2000 because
the operation details are not available on the
eNodeB side.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page41
Action 2: Check Device Fault & Alarm
Data Analysis Method Solution
Source
Alarm and 1. Check alarms and device fault logs Analyze the impact of
fault logs within a week before the deterioration alarms and device
(top 10 occurs and active alarms and faults in faults on an access
sites for a a sudden KPI deterioration scenario. KPI. Then, clear
network- 2. Check alarms and device fault logs these alarms by
wide within the latest week and active referring to the alarm
problem alarms and faults in a gradual KPI and fault handling
and top 10 deterioration scenario. guide and check
cells for a 3. Check for abnormal operations that whether the KPI
top-cell may have been performed at all sites improves after the
problem) if a problem occurs on the entire alarms are cleared.
network.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page42
Typical Alarm for Access Problem
Mod
Alarm/Event Name Alarm/Event Impact
ule
Services that exceed the license capacity cannot be
accessed.
eRan3.0:If a license capacity for the maximum number of
users exceeds the limit, the eNodeB allows these UEs to
ALM-26812 System
access the network and immediately releases these UEs.
Licen Dynamic Traffic
As a result, the number of E-RAB connection setup
se Exceeding Licensed
attempts and releases increases.
Limit
eRan6.0:If a license capacity for the maximum number of
users exceeds the limit, the ERAB setup will fail. The
eNodeB response MME UE context setup fail with cause
radio-resources-not-available.
This PDSCH power configuration change does not take
ALM-29241 Cell
effect. As a result, the cell coverage does not meet the
Reconfiguration Failed
requirement.
Cell
ALM-29245 Cell Blocked The cell cannot provide services.
ALM-29240 Cell
The cell cannot provide services.
Unavailable

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page43
Typical Alarm for Access Problem (Cont.)
Module Alarm/Event Name Alarm/Event Impact
The board cannot work properly and services carried over
this board may be interrupted.
ALM-26200 Board Hardware
The board cannot perform all the designed functions and
Fault
the board reliability degrades. If this problem persists,
services carried over this board may be interrupted.
The access success rates and service quality may
Board
deteriorate.
If this problem persists, the maintenance operations on this
ALM-26202 Board Overload board may slowly respond and even fail due to operation
timeout.
The test operations and tracing tasks of lower priorities
may be suspended or terminated.
ALM-29207 eNodeB Control
All the SCTP links in the eNodeB are faulty, resulting in
Plane Transmission
failures such as S1 and X2 link setup failure, cell activation
Interruption
failure, and network access failure of users.
S1
Interfac ALM-25888 SCTP Link Fault The SCTP link cannot process signaling.
e
ALM-25889 SCTP Link The services are interrupted because the data cannot be
Congestion transmitted due to insufficient space of the sending buffer.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page44
Typical Alarm for Access Problem
(Cont.)
Module Alarm/Event Name Alarm/Event Impact
The return loss at the antenna port is excessive. As a
ALM-26529 RF Unit VSWR result, the RF unit automatically switches off the TX
Threshold Crossed channel, and the ongoing services carried on the TX
channel are interrupted.
ALM-26532 RF Unit Hardware The RF unit may work improperly. The ongoing services
Fault carried on the RF unit may be interrupted.
ALM-29207 eNodeB Control
All the SCTP links in the eNodeB are faulty, resulting in
Plane Transmission
failures such as S1 and X2 link setup failure, cell activation
RF Interruption
failure, and network access failure of users.
Channel
The receive sensitivity of the RFU decreases, the
ALM-26521 RF Unit RX demodulation performance of the cell deteriorates, and the
Channel RTWP/RSSI Too Low uplink coverage shrinks.
If the RTWP/RSSI on all RX channels of the cell is too low,
the ongoing services of the cell may be interrupted.
ALM-26522 RF Unit RX The receive sensitivity of the RFU decreases, the
Channel RTWP/RSSI demodulation performance of the cell deteriorates, and the
Unbalanced uplink coverage shrinks.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page45
Cause of High VSWR
 VSWR: Voltage Standard Wave Ratio, indicate the if feeder impedance is
match or not. The normal VSWR range is 1~1.5. If current VSWR is more
than a specified threshold, then eNodeB will generate relevant alarm.
 Alarm generation:
 Cell is activated
 RF power is more than 34dBm/channel
 VSWR is more than a specified threshold
 Possible cause:
 Incorrect VSWR alarm threshold
 RF unit hardware fault
 RRU/RFU wrong connection
 Bad feeder quality or nonstandard feeder installation

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page46
Solution for High VSWR
 Step 1: Check if the VSWR alarm threshold is correct (default is 2dB).
 Note: RRU TX channel will automatic closed if VSWR is extremely high (more than post-
processing threshold)

Threshold for TX shutdown

Threshold VSWR alarm


generation

 Step 2: If alarm threshold is correct, then check if relevant feeder installation and RRU
connections are meet the standard.
 Step3: After the feeder tuning, if TX channel is closed, then activate TX channel again
 MOD TXBRANCH

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page47
Cause of Low RSSI
 Alarm generation: If RSSI is less than a specified value

 Incorrect RX attenuation setting


 If no TMA, the attenuation should be 0

 If 12dB TMA is used, the attenuation should be 4 to 11dB

 If 24dB TMA is used, the attenuation should be 11 to 22dB

 Feeder problem
 Due to bad feeder quality, causing additional loss

 RRU fault

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page48
Solutions for Low RSSI
 Step 1: Check if RRU RX attenuation is correct

 Step2: If attenuation is correct, then check the feeder


installation and connection

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page49
Cause of Imbalance of RSSI
 Alarm generation: RSSI of the main RX channel and the
RSSI of the diversity RX channel exceeds 10 dB.

 Possible causes
 High interference

 RRU cross connections

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page50
Solution of Imbalance of RSSI
 UL interference check
 From web-LMT: Perform spectrum detection to evaluate UL interference
 From M2000 client: Perform interference detect monitoring
 Find out interference source

 Check RRU connections, avoid cross connections, show as below

A A
N N
T T
1 2

RRU1 RRU2

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page51
Action 3: Check Parameters
Parameter Source Impact Recommended Value

Number of initial MML If the switch for dynamic adjustment If the switch for dynamic
PDCCH to the number of OFDM symbols adjustment to the number of
symbols occupied by the PDCCH is turned off OFDM symbols occupied by the
and this parameter is set to 1, the PDCCH is turned on, preferably
peak throughput of a single user set this parameter to 1.
increases. However, if the bandwidth If the switch for dynamic
of the cell is lower than 3 MHz, it will adjustment to the number of
impact user access OFDM symbols occupied by the
PDCCH is turned off, preferably
set this parameter to 3
Encryption MML In the ENodeBCipherCap MO, the PrimaryCipherAlgo = AES,
Algorithm PrimaryCipherAlgo, SecondCipherAlgo = Snow3G,
SecondCipherAlgo, and ThirdCipherAlgo = NULL;
ThirdCipherAlgo parameters must be
set to different values.
Primary integrity MML In the ENodeBIntegrityCap MO, the PrimaryIntegrityAlgo = AES,
algorithm PrimaryIntegrityAlgo, SecondIntegrityAlgo = Snow3G,
SecondIntegrityAlgo, and ThirdIntegrityAlgo = NULL;
ThirdIntegrityAlgo parameters must
be set to different values.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page52
Action 3: Check Parameters (Cont.)
Parameter Source Impact Recomme
nded
Value
S1 MML If this parameter is set to a small value, the eNodeB 20s
message may determine that timeout occurs even when the
waiting MME does not respond to the message. If this
timer parameter is set to a large value, when exceptions
occur but no response messages from the MME are
received, system resources will be occupied for a
long period of time.
Uu MML This parameter affects the timeout length for the 35s
message timer for the eNodeB waiting for the UE to send the
waiting Uu response message. If this parameter is set to a
timer small value, the eNodeB may determine that timeout
occurs even when the UE does not respond to the
message. If this parameter is set to a large value,
when exceptions occur but no response messages
from the UE are received, system resources will be
occupied for a long period of time.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page53
Action 3: Check Parameters (Cont.)
Parameter Source Recommended Value

AMBR S1 signaling (MME) Set this parameter a value greater than 0. If


AMBR is set to 0, users cannot access the
network.

ARP S1 signaling (MME) Set this parameter to a non-zero value. If ARP is


set to 0, users cannot access the network.
Network mode Configurations on the UE Set this parameter to Auto (rather than WCDMA-
side only or GSM-only, or LTE-only if inter-RAT
interoperability is enabled on a network)
Set this parameter to LTE-only if UEs are always
camping on a WCDMA or GSM network when this
parameter is set to Auto.

APN Configurations on the UE Dynamic APN configurations are preferred.


configuration side

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page54
Action 4: Weak Coverage Check

Data Analysis method Solution


Sourc
e
Driver Analysis method: If the drive test 1. If only top UEs are
test log log shows that the downlink RSRP experiencing weak
is below -119 dBm, the problem is coverage, clarify this point
caused by weak coverage. to the operator.
2. If massive UEs are
experiencing weak
coverage, perform RF
tuning

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page55
Action 4: Check Congestion
Data Analysis method Solution
Source
Performa Check relevant resource, Located the
nce including: PRB, CCE, CPU bottleneck of
counter usage, license, PUCCH usage, congestion and
active user number perform capacity
extension
 Relevant threshold for congestion prevention
 PRB usage < 70%
 CCE usage < 70%
 CPU usage < 60%
 PUCCH usage < 70%

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page56
Action 5: Check Interference

Data Analysis method Solution


Source
Interfer Check for uplink interference traffic statistics of cells in idle hours. Interference
ence If L.UL.Interference.Avg is -105 dBm or greater, UL interference is analysis
traffic likely to occur.
statistic
s
Interfer Perform the real time interference monitoring, if interference
ence power on each RB is more than -129dBm, we can consider there
monitori is an interference
ng

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page57
Action 6 : Top UE Check
Data Source Analysis method Solution
Use the Capabilities of the Top Users function 1. Check for known
Nastar provided by the Nastar to check the ratio of top UE issues in the
(Choose top type problems to total exceptions. If the ratio of
current UE version.
10 sites for a exceptions due to top 1 UE type is twice higher
network-wide than that of normal UE types, the problem is a top 2. Use the UE to
problem. UE type problem. repeat the problem
) 1. Collect logs of top 10 sites and statistics about
the UE capacity recorded in CHRs. Then,
generate the ratio of each UE capacity to
obtain top 1 UE type.
2. Calculate the proportion of exceptions
generated by the top 1 UE type and
proportions of exceptions generated by other
top UE types based on the statistical results of
the CHR.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page58
Action 7: Check EPC Exceptions
Data Analysis method Solution
Source
E-RAB setup failures: Analyze the following problems by using 1. If EPC
CHR and CHRs and Uu/S1 signaling. exceptions exist,
Uu/S1 1. Failure of an eNodeB to respond to a context,Check AS layer locate the problem
signaling integrated protection and encrypted algorithm configuration on the with EPC
eNodeB by using standard signaling. Check whether IP address at personnel.
the transmission layer on the EPC, AMBR, and ARP are correct. 2. If UE exceptions
2. Abnormal release of active MME release: According to CHRs or exist, perform top
Uu/S1 signaling, check whether the EPC delivers the release users/UE check
command too early or the the EPC delivers the release command 3. If air interface
after the timer for the EPC waiting for context setup expires because scheduling is
the eNdoeB air interface waits for a long period of time. For such inappropriate,
problems, check the length of the timer for waiting contexts with the perform weak
EPC personnel. coverage and
Abnormal NAS: interference check
1.Authentication failure
2.NAS security activation failure

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page59
Action 8: Check Transmission
Data Analysis method Solution
source
Performa The cause value of an access failure is L.E- 1. Repeat the transmission
nce RAB.FailEst.TNL. caused access problem.
Counters
Analyze the quality of SCTP link by counters of 2. Troubleshoot the
VS.SCTPLnk.Cong.Dur and VS.SCTPLnk.Cong and transmission faults.
VS.SCTPLnk.Unavail.Durand VS.SCTPLnk.Unavail.
Alarm Check for ALM-25888 SCTP Link Fault, ALM-25886 IP Clear the reported alarms by
Path Fault, and ALM-29240 Cell Unavailable referring to the Alarm/Event
References.
Paramet Check whether the settings of VLAN, DSCP, IPRT, IPPATH, Reconfigure the parameters
er SCTP, and other transmission parameters are the same as
that are not currently
settings the planned settings.
configured as the planned
settings.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page60
Action 8: Check Transmission (Cont.)

Data Analysis method Solution


source
Signalin If a context setup fails, check the 1. If an IP address is not configured at the
g value of the eNodeB transmission layer, configure an
messag transportLayerAddress field in
es over IP address for the IP path of the eNodeB.
the
S1 INITIAL_CONTEXT_SETUP_RE 2. If an IP address is not configured as
interfac Q message is consistent with the planned at the eNodeB transmission
e peer IP address of the IP path by layer, reconfigure an IP address for the
using the S1 interface signaling IP path of the eNodeB.
message.
3. If an IP address is not configured as
planned at the EPC transmission layer,
contact the EPC engineer for a
reconfiguration of an IP address for the
IP path of the eNodeB.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page61
Case 1:IP Path Configuration Leads
to Low Access Ratio
 Description: In one live network, ERAB setup ratio is very
low, almost 50%

 Alarm info: None

 Analysis:
 Check the performance statistic of ERAB release, we found
that most of failures are caused by transport resource not
available

 From the message tracing, we can also confirm this result

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page62
IP Path Configuration Leads to Low
Access Ratio (Cont.)
 Now we can locate that the problem is due to IP path
configuration. We check eNodeB configuration and find a
valid IP path, the connection is valid. And it is also weird
that this problem occurs with a probability

 Then we analyze the message again, and find that in the


“UE context setup request” message delivers variable
GTPU address, and these address is not identical with
eNodeB configuration.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page63
IP Path Configuration Leads to Low
Access Ratio (Cont.)
 Conclusion :As the SGW deliveries multiple GTUP address
to eNodeB, but we only configure one IP path to SGW, so it
causes the partly ERAB setup failure

 Solutions: We confirm this with EPC engineer, SGW pool


function is used, so there are multiple IP addresses for
SGW. Then we make up the IP path for all address, the
problem is cleared.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page64
Case 2:Wrong EPC Parameters
Leads to ERAB Setup Failure
 Description: In one live network, ERAB setup ratio is very
low, it is about 85%

 Alarm info: None

 Analysis: We first check the failure cause, most of failure


reason is “MME related”, and we check with MME side,
everything seems normal. So we find some top cells, trace
S1 message during the busy hour.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page65
Wrong EPC Parameters Leads to
ERAB Setup Failure (Cont.)

 Above is a failure message, from the message, we find that


the failure cause is “ semantic error” which means there is
something error in previous message.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page66
Wrong EPC Parameters Leads to
ERAB Setup Failure (Cont.)

 We go on to check the previous message, and find that the


QCI from MME is wrong.

 Solution: this is a bug of MME, sometimes MME will give the


wrong QCI. After software upgrade, the problem is solved

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page67
Case 3:Multi-mode UE Attach Failure

S1
UU trace
trace

 Description: During the commissioning of one live network, we found that UE


attach fails.
 Alarm info: None
 Message Tracing: From the message tracing, we can see that most of access
procedures are normal, after ERAB setup, MME release the connection with
the cause “normal release”

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page68
Multi-mode UE Attach Failure (Cont.)

 Analysis
 Since the most of procedures are normal, and eNodeB consider
that it’s a normal release, so we locate that the problem is due to
NAS failure.
 So we continue to analyze the previous NAS message, and in the
DL NAS message, we can see that MME response the attach with
the cause “MSC-temporarily-not-reachable”, as show above. now
we can confirm that this is root cause of attach failure

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page69
Multi-mode UE Attach Failure (Cont.)

 Analysis (Cont.)
 Why should UE need attach to MSC ? We check the UE model,
it ‘s Huawei E398, with multi-modes(GSM/UMTS/LTE). So we
assume that this UE performs combined attach. From the
attach request message we verify our assumption.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page70
Multi-mode UE Attach Failure (Cont.)

 Conclusion:
 We check that there is no CS domain configuration in current EPS network, so
MME only replies PS attach accept, and also inform that MSC can’t reachable
 Temporary solution:
 Change UE attach mode with PS only
 Add CS domain configuration in EPC
 Final solution:
 Update MME to compatible with combined attach even there is no CS domain

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page71
Case 4 : Low Access Success Rate
Due to Improper SRS Subframe
Configuration
 Problem: The onsite KPI monitoring engineer discovers a
decrease in access success rates at one site between
September 24 and October 7.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page72
Troubleshooting Process

The performance counters


exported by using the FMA
shows that the number of
L.RRC.SetupFail.ResFail
messages is equal to that
of the The maximum
L.RRC.SetupFail.Rej number of
message, which indicates users is 14 in
that RRC connection this cell,
setup failures are caused which stands
by allocation failures of below the
resources of RRC allowed limit.
connections.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page73
Troubleshooting Process (Cont.)
Stat
Action Analysis Results
us
Action 2: checking operation
No operation alarms of this cell are reported within the one
logs, device faults, alarms, and OK
week that precedes the occurrence of this problem.
external events
The configuration files of this eNodeB and these of the eNodeB
of which the cells are normal are compared by the frontline
Action 3: checking parameters OK
engineers, finding that the SRSSUBFRAMECFG parameter is
set to SC9 at this site and is SC3 at other sites.
Action 4: checking version
This problem has been identified, and this action is not required. /
differences and known issues

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page74
Case 5 :Drastic Increase in the Number
of RRC Connection Setup Attempts
Due to Improper TAC Planning

 Problem description: Despite normal setup success rates of


RRC connections and E-RAB connections in some areas of
a site, the number of RRC connection setup attempts
increases drastically and the number of E-RAB connection
setup attempts remains the same.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page75
Troubleshooting Process

Action Analysis Results Status


1. Analysis of daily performance counters
shows that the drastic increase of RRC
connection setup attempts takes place only
at the top sites, rather than on the entire
Action 1: network.
performing scope 2. Despite normal setup success rates of
identification, KPI RRC connections and E-RAB connections, OK
trend analysis, and the number of RRC connection setup
cause resolution attempts increases drastically and the
number of E-RAB connection setup
attempts remains the same. Therefore, this
problem is empirically caused by improper
TAU planning.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page76
Troubleshooting Process (Cont.)
Action Analysis Results Status
Action 2:
checking
operation logs,
No exception is found. OK
device faults,
alarms, and
external events
The eNodeB parameter configurations of
Action 3:
the problematic site and these of the
checking OK
normal sites are compared, and no
parameters
difference is found.
Action 4:
No known issue that will result in this
checking version
problem is found in the related release OK
differences and
notes and preventive guides.
known issues

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page77
Troubleshooting Process (Cont.)
Action Analysis Results Status

The checking of the network topology finds that the top


sites (in the red circles in the following figure) are different
Action 5: checking
from the nearby sites in terms of TAC planning and they
network planning and OK
belong to different TALs. Therefore, the top sites are
optimization
discretely distributed, with improper TAC and TAL
planning. For details, see the following figure.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page78
Case 6: Low RRC Connection Setup
Success Rate Due to Intermodulation
Interference
 Problem description: The RRC connection setup success
rate keeps staying at a low level, about 40%, far below the
requirement

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page79
Troubleshooting Process
Action Analysis Results Status
1. The frontline engineer finds that the
RRC connection setup success rate
keeps staying a low level only in one
cell of the site during routine KPI
Action 1:
monitoring. Therefore, this problem is a
performing scope
top-cell problem.
identification, KPI
2. Analysis of performance counters OK
trend analysis,
shows that the cause of the RRC
and cause
connection setup failures is
resolution
L.RRC.Setup.NoReply, indicating that
the eNodeB does not receive RRC
Connection Complete messages from
UEs.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page80
Troubleshooting Process (Cont.)
Action Analysis Results Status
Action 2: checking
operation logs, No abnormal operations are performed or
OK
device faults, alarms, related alarms are reported.
and external events
Action 3: checking
No exception is found. OK
parameters
Action 4: checking The site where the problem occurs is
version differences running the same version as other sites on OK
and known issues the network.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page81
Troubleshooting Process (Cont.)
Statu
Action Analysis Results
s
Action 5: checking
Analysis of the CHR log through the FMA shows that this access
network planning and OK
problem is not caused by weak coverage.
optimization
1. Analysis of the CHR log through the FMA shows that this
access problem is caused mostly by weak coverage.
2. Determination rule for uplink interference during an RRC
connection setup in eRAN2.8 or later by using the FMA: The
uplink RSRP is greater than -130 dBm and the SINR is not
greater than 0 dB, or the SINR is not greater than 5 dB and the
difference between the uplink interference and the SINR is not
Action 6: checking
less than -124. The following figure shows that the uplink OK
interference
RSRP and SINR fall within this interval. Therefore, this problem
is caused by the uplink interference. RF channel checking is
performed then to identify the interference source.
3. Wideband spectrum scanning is then performed, finding that
the cell is experiencing intermodulation interference. The
frontline engineer then performs onsite check and troubleshoot
the jumper connection faults.

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page82
Troubleshooting Process (Cont.)
 Note:
 The intermodulation
interference on the 800 MHz
band typically features a
decrease in the maximum
received level from left to right.
 The intermodulation
interference on the non-800
MHz band typically features
an increase in the maximum
received level from left to right

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page83
Thank you
www.huawei.com

Anda mungkin juga menyukai