LTE Access Fault Diagnsis

LTE Access Fault Diagnos
is
www.huawei.com
Attention: This document is only for the basic study. If you need
the latest issue troubleshooting, please to check the related L2
course of X solution.
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

Page3
Contents
1. EUTRAN Typical Signaling Procedure
2. Typical Access Fault Analysis and Process
3. Case Study

Page4
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

Page5
UE Initial Attach Procedure
UE
eNodeB MME
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

Page6
Service Request Procedure
UE eNodeB MME
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)
RRC_SECUR_MODE_CMD
RRC_SECUR_MODE_CMP
E-RAB
RRC_CONN_RECFG
Setup
RRC_CONN_RECFG_CMP
NAS Procedure
Dedicated E-RAB_SETUP_REQ
E-RAB RRC_CONN_RECFG
Setup RRC_CONN_RECFG_CMP
E-RAB_SETUP_RSP

Page7
TAU Update Procedure
UE eNodeB MME
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

Page8
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)

Page9
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
Contention Resolution
Contention based Non-contention based
 UE randomly selects a prea  Before random access, eNodeB

mble and sends it, conflic assigns a dedicated preamble to
t might occurs UE, so there is no conflict.
 Can be used for all cases

Page10
Preamble Index Configuration

Page11
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

Page12
Preamble Sending
 In contention based case, UE randomly select a preamble based o

n 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)

Page13

Page14
UL Data Sending (Msg 3)

Page15
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
Page16
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

Page17
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 emergen
cy

Page18
Initial ERAB Setup
eNodeB MME
UE
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

Page19
S1 Initial UE Message
Initial UE Message
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

Page20
S1 Initial Context Setup Request
Initial Co nte xt 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

Page21
Security Mode Setup
Security Mode 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 ciph
ering
 Integrity protect: only for signaling, support AES, snow3G and Null
 Ciphering: both for signaling and data, support AES, snow3G and Null

Page22
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 capab

ility 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

Page23
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

Page24
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

Page25
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

Page26
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

Page27
Contents
3. Case Study

Page28
Access Performance Evaluation
 From performance management
 Access successful ratio = RRC setup successful ratio x
ERAB setup successful ratio
 Random access and NAS failures are not considered in eN
odeB performance management, but these factors also imp
act user experience
 From drive test tools (probe)
 It can identify access failure caused by random access
failure and NAS failure

Page29
General Process
 Determine the scale of problem
 From the performance statistic, we can determine the scale of the prob
lem, is it global problem, or cell level problem or just some individu
al UE problem. Then we can select bottom N cell as optimization target
 Customer complain is an effective way to locate the individual UE pro
blem
 For large scale access failure
 Check eNodeB alarm and basic configuration
 Check RF channel problem
 Once RF channel is abnormal, such as high VSWR, low RSSI Too Low or RSSI is
unbalanced, then the access performance should be significantly affected.
 For individual UE problem, signaling analysis can be used to locate

the detailed cause

Page30
Handle eNodeB Generic Alarm
 Tools: M2000 or LMT
 Procedure
 Check the generic hardware fault alarm, such as hardwa
re fault, board unusable , or any other alarms which ar
e related with hardware failure or link failure.
 Solution: Replace the faulty component.

Page31
Check DL Power Configuration
 To ensure the coverage, the DL power parameters should be properly set
 RS power = Maximum RRU power/channel – 10lg(total subcarriers ) + 10lg(Pb
+1)
 If the single antenna, Pb=0
 If 2 or 4 antennas, Pb=1
 PDSCH power = PA + RS power
 If single antenna, PA=0
 If 2 or 4 antennas, PA=-3
 Related command:
 LST PDSCHCFG: check Pb and RS power setting
 LST CELLDLPCPDSCHPA: check PA setting

Page32
Check CRPI Rate
 If the bandwidth is 10MHz or above, the CPRI rate sho

uld be equal or more than 2.5Gbps, otherwise, the cel
l can’t be setup
 If the rate is not correct, change the CPRI module
Page33
Check S1 Interface Status
 If SCTP link is faulty, check t
he SCTP configuration, such as
peer IP address, SCTP port numb
er
 If S1intrface state is faulty,
check the PLMN and operator ID.

Page34
Check Cell Barred Status
 If cell is barred, use the following command to recov

er it

Page35
Check RF Channel Problem
 Due to the bad feeder quality, incorrect feeder connection
or strong interference, it might affect RF channel perform
ance which has impact on UE access.
 Relevant problem:
 High VSWR: ALM-26529 RF Unit VSWR Threshold Crossed
 Low RSSI: ALM-26521 RF Unit RX Channel RSSI Too Low
 RSSI unbalance: ALM-26522 RF Unit RX Channel RSSI Unbalanced
 RSSI of the main RX channel and the RSSI of the diversity RX chann
el exceeds 10 dB.
 High RSSI: Caused by interference

Page36
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 t
han 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

Page37
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- proce
ssing threshold)
Threshold for TX shutdown
Threshold VSWR alarm

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

Page38
Cause of Low RSSI
 Alarm generation: If RSSI is less than a specified va
lue
 Incorrect RX attenuation setting
 If no TMA, the attenuation should be 0
 If 12dB TMA is used, the attenuation should be 4 to 11d
B
 If 24dB TMA is used, the attenuation should be 11 to 22
dB
 Feeder problem
 Due to bad feeder quality, causing additional loss
Copyright © 
2014 Huawei Technologies Co., Ltd. All rights reserved.
Page39
RRU fault
Solutions for Low RSSI
 Step 1: Check if RRU RX attenuation is correct
 Step2: If attenuation is correct, then check the feed

er installation and connection

Page40
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

Page41
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

Page42
Classification of Interference
 Passive inter-module interference:
 Due to non-linearity of radio component ,the high phase
harmonic wave might be generated and inter-modulated by
RX signal, thus the new inter-module signal will arrive
the receiver causing the interference.
 External interference:
 Interference from the other system, such as 2G, 3G, CDM
A, radio, radar eg.

Page43
How to Located Inter-modulated I
nterference
 This kind of interference increases with eNodeB trans
mit power, so we can simulate the DL load, and chec
k RSSI, if it obviously increases with the DL load in
censement, then we can determine the interference
 Load simulation:

Page44
How to Located External Interferen
ce
 If we exclude inter-modulated interference, then it s
hould be external interference
 Shutdown the TX of RRU/RFU, if RSSI is still high, the
n we can conclude this is external interference

Page45
Analysis of Tracing
 Driver test tracing analysis
 We can get all UU interface messages, internal UE message as well as
RSRP value
 eNdoeB tracing analysis
 We can get UU interface message and S1 interface message
 Form the above tracing analysis, we can locate the problem with t
he following causes:
 Random access failure
 RRC setup failure
 NAS procedure failure
 ERAB setup failure

Page46
Random Access Failure
 Generic scenario: There is no “RRC connect request ”message
 Possible cause:
 UE doesn’t support the band
 Scenario: UE doesn't receive any system message
 Solution: Check if UE band is identical with eNdoeB configuration
 Poor coverage
 Scenario :Due to poor DL or UL coverage, UE or eNodeB miss receiving the rel
evant random access message
 Solution: Perform RF tuning. Use TMA on uplink
 Cell is barred
 Check the cell status, should be not barred.

Page47
RRC Connection Failure
UE eNodeB
RRC_CONN_REQ
RRC_CONN_REJECT
 Scenario 1: eNodeB directly send reject message

 Possible cause: No radio resource due to no enough reso
urce for PUCCH and SRS
 Solution: Check the cell load status, if it is very hig
h, consider capacity extension

Page48
RRC Connection Failure (Cont.)
UE eNodeB
RRC_CONN_REQ
RRC_CONN_SETUP
RRC_CONN_REQ
 Scenario 2: UE doesn’t receive “RRC connection setup” mes

sage, and repeat sending request message until timer is out
 Possible cause:
 Poor DL coverage, check RSRP and RSRQ
 Solution:
 Perform RF tuning

Page49
RRC Connection Failure (Cont.)
UE eNodeB
RRC_CONN_REQ
RRC_CONN_SETUP
Waiting “RRC
Compelet”time out
 Scenario 3: eNodeB send RRC setup message, but doesn’t get

complete message
 Possible cause
 If UE doesn’t reply RRC complete, it should be UE problem
 If UE already send RRC complete, then it should be poor UL cover
age

Page50
NAS Procedure Failure MME
eNodeB
UE
S1AP_INITIAL_UE_MSG
S1AP_DL_INFO_TRANSF
RRC_DL_INFO_TRANSF
RRC_UL_INFO_TRANS
S1AP_UL_INFO_TRANSF
S1AP_UE_CONTEXT_REL_CMD
S1AP_UE_CONTEXT_REL_CMP
 Note: NAS failure is not counted in performance statistic

Page51
ERAB Setup Failure
eNodeB MME
UE
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

Page52
ERAB Setup Failure Cause
 If any failure occurs during ERAB setup, we can directly g
et the failure cause form performance statistic, the relev
ant counters are:
 L.E-RAB.FailEst.NoReply (No response from UE)
 L.E-RAB.FailEst.MME (EPC fault)
 L.E-RAB.FailEst.TNL (Transport fault)
 L.E-RAB.FailEst.RNL (Radio network fault)
 L.E-RAB.FailEst.NoRadioRes (No radio resource)
 L.E-RAB.FailEst.SecurModeFail (Security mode setup fault)

Page53
Faulty Signaling of No UE Response

Page54
Fault Signaling of Other Cause
 Scenario: eNodeB receives “initial context setup req

uest” or “E-RAB setup request” message, after tha
t, if failures happen, then eNB replies response mess
age with failure cause

Page55
Analysis of EPC Fault
 Cause ：
 S1 message validity check failure, including
 Error exist in S1 message
 Duplicated ERAB ID
 Conflict with other procedures
 Solution:
 Contact EPC engineer to locate the problem

Page56
Analysis of Transport Fault
 Possible causes:
 Transport admission failure
 S1 link failure during S1 message exchange
 Incorrect IP path configuration
 Wrong QoS configuration in EPC
 Solutions:
 Check transport admission algorithm, consider extend S1 bandwidth
 Check S1 interface
 Check IP path configuration
 Check relevant QoS configuration, AMBR should be more than 0, and for initi
al ERAB setup, the QCI must be 6~9

Page57
Analysis of Radio Network Fault
 Possible cause
 UU message process failure due to UE capability (UE doe
sn’t support relevant service)
 eNodeB failure during ERAB setup
 Solutions:
 Check UE capability
 Check eNodeB status

Page58
Analysis of No Radio Resource
 Possible cause
 Radio admission failure for ERAB
 Solution:
 Check if admission parameters are correct
 Consider to enable load balance algorithm
 Consider capacity extension

Page59
Analysis of Security Mode Failure
 Possible cause:
 UE security capability is not identical with eNodeB sec
urity capability
 Solution:
 Modify the eNB security algorithm to match it.

Page60
Contents
3. Case Study

Page61
Case 1 – IP Path Configuration L
eads to Low Access Ratio
 Description: In one live network, ERAB setup ratio is v
ery low, but it’s not zero.
 Alarm info: None
 Analysis:
 Check the performance statistic of ERAB release, we found
that most of failures are caused by transport resource no
t available
 From the message tracing, we can also confirm this result

Page62
Case 1 –IP Path Configuration Le
ads to Low Access Ratio (Cont.)
 Now we can locate that the problem is due to IP path
configuration. We check eNodeB configuration and fin
d a valid IP path, the connection is valid. And it i
s also weird that this problem occurs with a probabi
lity
 Then we analyze the message again, and find that in
the “UE context setup request” message delivers va
riable GTPU address, and these address is not ident
ical with eNodeB configuration.

Page63
Case 1 –IP Path Configuration Le
ads to Low Access Ratio (Cont.)
 Conclusion :As the SGW deliveries multiple GTUP addre
ss to eNodeB, but we only configure one IP path to SG
W, so it causes the partly ERAB setup failure
 Solutions: We confirm this with EPC engineer, SGW poo
l function is used, so there are multiple IP addresse
s for SGW. Then we make up the IP path for all addres
s, the problem is cleared.

Page64
Case 2 – Multi-mode UE Attach Fai
lure
S1
UU trace
trace
 Description: During the commissioning of one live network, we found tha

t UE attach fails.
 Message Tracing: From the message tracing, we can see that most of acce
ss procedures are normal, after ERAB setup, MME release the connection
with the cause “normal release”
Page65
lure (Cont.)
 Analysis
 Since the most of procedures are normal, and eNodeB consider that i
t’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 N
AS message, we can see that MME response the attach with the cause
“MSC-temporatily-not-reachable”, as show above. now we can confir
m that this is root cause of attach failure

Page66
lure (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 at
tach request message we verify our assumption.

Page67
lure (Cont.)
 Conclusion:
 We check that there is no CS domain configuration in current EPS network, so MM
E 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

Page68
Case 3 – SRS Configuration Leads
to Low RRC SSR
 Description: RRC SSR of site RNNTL079 is very low. Traffic measu
rement data analysis shows it’s mainly caused by Cell3.

 Analysis:
 Classify the detail reasons of L.RRC.SetupFail.ResFail, we fo
und the main reason is RRC.SetupFail.ResFail.SRS

Page70
to Low RRC SSR (cont.)
 Analysis
 Check the license configuration, the license setting is correct
 Check the parameter configuration, we found the “TDD SRS
Configuration Mode” of cell 3 are different. The configurations of
Cell 1,2,3 are experience first, cell 4,5,6 are access first.

Page71
to Low RRC SSR (cont.)
 Solution:
 Change to access first and observe the test result, RRC connection SSR bec
omes normal.
 Conclusion:
 If SRS configuration mode is Experience First, one cell can support about
140 users. If it’s access first, one cell can support about 400 users. Wh
en the reason of low RRC SSR is RRC.SetupFail.ResFail.SRS, we should check
SRS configuration.
Page72
Thank you
www.huawei.com

LTE Access Fault Diagnsis

Uploaded by

Copyright:

Available Formats

You might also like

LTE Access Fault Diagnsis

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE Access Fault Diagnsis

Uploaded by

Copyright:

Available Formats

LTE Access Fault Diagnos

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

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

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

Partial visible flow

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

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

NAS Procedure (No authentication procedure)

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

DL NAS (TAU update accept )

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

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

Random Access Preamble Random Access Preamble

Contention based Non-contention based

 UE randomly selects a prea  Before random access, eNodeB

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

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

CP Sequence Guard Period

CP Sequence Guard Period

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

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

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

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

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

Case1: Detect C-RNTI Contention Resolution message

Case2: Detect temporary C-RNTI on PDCCH and

RRC Connection Setup Complete

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

 According to different NAS procedure, the RRC cause

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

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

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

Initial Context Setup Request

Initial Context Setup Response NAS PDU

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

Security Mode Command

Security Mode Complete

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

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

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

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

RRC Connection Reconfiguration

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

Initial Context Setup Request

Initial Context Setup Response

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

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

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

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

 For individual UE problem, signaling analysis can be used to locate

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

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

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

 If the bandwidth is 10MHz or above, the CPRI rate sho

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

 If cell is barred, use the following command to recov

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

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