LTE Access Fault Diagnosis ISSUE2 00

LTE Access Fault Diagnosis
www.huawei.com
Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.
Learning Guide
Before learn this course, you should have:
Known the LTE basic knowledge

Studied LTE Air Interface courses
Studied LTE Signaling Flow courses

Page3
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

Page4
Contents
1. Access Problem Overview
2. Access Problem Analysis

Page5
Random Access Overview
Contention based
Non-contention based

Page6
Random Access Procedure
Contention based
Note
Solid line is visible signaling
Dash line is invisible
signaling

Page7
UE Initial Attach Procedure

After UE power on, UE will select a
suitable cell and camp on, then initi
als Attach flow
Attach procedure including the foll
owing procedure:
Random access
RRC connection setup
NAS authentication procedure
E-RAB setup
RRC connection setup cause:

MO signaling
During the Attach procedure, data
card terminal set up only one defa
ult bearer . In addition ,the UE sup
port VoIP will setup dedicated bear
er
Page8
Random Access Success Rate Definition
Random Access Success Rate = ( L.RA.GrpA.ContResolution

+ L.RA.GrpB.ContResolution ) / ( L.RA.GrpA.Att + L.RA.GrpB.
Att )
L.RA.GrpA.Att
L.RA.GrpB.Att
L.RA.GrpA.ContResolution
L.RA.GrpB.ContResolution

Page9
RRC Connection Setup Success Rate Defin

ition
RRC Connection Setup Success Rate = L.RRC.ConnReq.Succ / L.R

RC.ConnReq.Att
L.RRC.ConnReq.Att
L.RRC.ConnReq.Succ

Page10
E-RAB Setup Success Rate Definition
E-RAB Setup Success Rate = L.E-RAB.SuccEst / L.E-RAB.AttEst
L.E-RAB.AttEst
L.E-RAB.SuccEst

Page11
Contents
2.1 Low Random Access Rate
2.2 Low RRC Connection Setup Success Rate
2.3 NAS Procedure failure
2.4 Low E-RAB Setup Success Rate

Page12
Low Random Access Rate Cause Analysi

s
Low random access rate common causes:
UE Accesses the Cell beyond the Cell Radius

Root sequence conflict
Serious interference

Page13
UE Accesses the Cell beyond the Cell

Radius Overview
Description :
UE locate within the area of cell coverage, but UE outside the

area of the cell radius accesses a cell
Impact :
Time offset phenomenon
eNodeB detect the Preamble ID sends from UE has deviation, the

refore eNodeB estimate the TA value of UE has deviation

Page14
Time Deviation
Preamble sequence are generated from cyclic shifts

of root sequence, the number of preamble sequence
generated by each root sequence is determined by
PreambleFmt, HighSpeedFlag, CellRadius

Page15
Time Deviation (Cont.)
Suppose : Preamble format is set to 0 , low-speed cell ,

cell radius it 15Km
Thus : Ncs=119 , each root sequence index can
generate 7 preamble sequence, that is 7 Preamble ID
detect range in eNodeB and invalid detect range Null
size is 839-119*7=6 . Preamble ID distribute on the
root sequence is below :

Page16
The rules of Preamble ID and TA detection :
Invalid detect range Null size is 6, TA=ceil(6*(800/839)/

(16*Ts))=11
Suppose : The maximum TA value corresponding to
preamble search range is TNCS ,the time offset of UE is Toff
,usually , the TA of UE is TA0, the peak value position is P0
As shown in the next slide :
When UE select Preamble ID=0 , eNB detect the
correlation peak value on the P1 position which Preamble
ID=6 , and detect the TA value is TA=TA1
When UE select Preamble ID=5 , eNB detect the
correlation peak value on the P2 position which Preamble
ID=4 , and detect the TA Value is TA=TA2

Page17
The rules of Preamble ID and TA detection :
Relationship between TA1 and TA2 :
TA1+11+ TNCS -TA0 = TA2+ TNCS -TA0 = Toff

That is : TA1+11=TA2 . Indicate that when UE select Preamble ID=
0, the TA value detected by eNB is 11 smaller than those correspo
nding to the other Preamble IDs

Page18
When time offset exist , UE select the Preamble ID randomly f

rom the 9 Preamble ID under the same root sequence , there
by the probability that UE select Preamble ID=0 is 1/7, thus , t
he probability is 1/7 that the TA value detected by eNB is 11 s
maller than those corresponding to the other Preamble IDs:

Page19
Preamble fix retransmission interval :
Suppose : PRAConfigIndex=3, the 4th subframe is RAR window after rand

om access preamble is sent . Currently, the ra-Response WindowSize is fi
x to 10 subframe through product implementation. Therefore, during the
ra-Response WindowSize duration , UE cannot receive the RAR message ,
UE resends the preamble in the next PRACH position, the retransmission
interval is 20ms , as shown below :

Page20
Fix TA deviation
Base on the assumption ,each root sequence index can generate 7 prea
mble sequence. When UE random access is fail , UE resends the preambl
e periodically. Therefore, the probability that eNB detect the Preamble I
D=6,13,20,27 is 1/7 . The TA value detected by eNB is 11 smaller than tho
se corresponding to the other Preamble IDs

Page21
Case
The retransmission interval is 20ms , therefore it is real user acces

s failure
Due to exist Null range, the Preamble ID eNB detected is 6 smalle
r than the UE select ,that is The TA value detected by eNB is 11 s
maller than those corresponding to the other Preamble IDs

Page22
UE Accesses the Cell beyond the Cell Ra

dius Troubleshooting
Perform CELL DT tracing, analyze TTI level data
Check contention RA failure is real user
If it is real user , the retransmission interval is fix , such as when P

RAConfigIndex=3 , UE resends the Preamble ID per 20ms

Page23
UE Accesses the Cell beyond the Cell Ra

dius Troubleshooting (Cont.)
Check the relationship between retransmission Preamble ID r

esent by UE and TA value in a continuous period of time
Preamble ID distribute randomly in Group A, TA value is almost th

e same in this continuous period of time, but some TA value is dif
ferent , such as 11 smaller than the normal TA value
Note is the case of UE accesses the cell beyond the cell radius. Th
e cell is low-speed cell , cell radius is set to 10Km. When UE acces
ses the cell beyond the cell radius , the TA is 3 or 4 smaller than t
he normal TA value, such as the normal TA value is 161, but some
TA value is 158 or 154. Meanwhile the Preamble ID are the last pr
eamble ID generated by each root sequence , such as preamble i
d 17/34

Page24
Case 1
Please refer to the case of Low Random Access

Success Rate Caused by UE Accesses the Cell
beyond the Cell Radius

Page25
Root Sequence Conflict Overview
Definition
The root sequence used in serving cell are reused or overlap

with neighbor cell
Impact
UE locate in neighbor cell initiates random access to neighbor

cell failure

Page26
Root Sequence Conflict Correlation Prin

ciple
Preamble Generation
Each cell is allocated a maximum of 64 preambles for RA. The

RA preamble sequence can be obtained through cyclic shiftin
g of the zero correlation zone ZC root sequence based on the
Ncs.

Page27

ciple (Cont.)
Logical root sequence mapping to physical root sequence
The Root Zadoff-Chu (ZC) sequence is defined by:
u n (n 1)
N ZC
xu n e
, 0n N
1
ZC
u is physical root sequence corresponds
to logical root sequence. It is
defined by 3GPP protocol 36.211 Table 5.7.2-4 and Table 5.7.2-5 . The fi
rst logical root sequence is determined by the parameter RootSequenc
eIdx .
j
Nzc indicates the length of the ZC sequence. It determined by paramet

er PreambleFmt, and defined by 3GPP protocol 36.211 Table 5.7.2-1
Preamble
format
03
4
Nzc
839
139

Page28

ciple (Cont.)
Ncs calculation
The Ncs is relevant to the cell radius and delay spread:

N_CS * T_s T_RTD + T_max + T_AdSch
T_s refers to the preamble sampling interval

T_RTD refers to maximum RTD in a cell , and is relevant to the sett
ing of cell radius
T_max refers to the maximum multi-path delay spread, with the v
alue of 5us
T_AdSch refers to length of forward search time , and the maxim
um downlink synchronization error is 2us

Page29
Root Sequence Conflict Phenomenon
If RootSeqConflictDetSwitch set as on, and meet the

following two condition, the alarm about the conflict
is displayed in the ALM-26247 alarm console :
The PRACH root sequence of the local cell conflict with

that of its neighboring cell
The PRA time-frequency resourceare overlap between
local cell and neighboring cell
If RootSeqConflictDetSwitch is set as off, the ALM26247 alarm is disappear

Page30
Root Sequence Conflict Phenomenon (C

ont.)
When random access is failed , the Preamble ID

distribution gather regularly on specific Preamble ID:
If change the cell radius , the random access failure

Preamble ID distribution share the same regular
trend

Page31

ont.)
The number of random access failure increase

tremendously in busy hour :

Page32

ont.)
When random access is failed due to root sequence

conflict ,the TA distribution is as following:

Page33
Locate Root Sequence Conflict Problem
Root sequence conflict problem troubleshooting :
Analyze the Preamble ID distribution ,confirm the

Preamble ID distribution gather regularly on specific
Preamble ID
Analyze the characteristic of random access failure, the
number of random access failure increase
tremendously with traffic increase in busy hour
Analyze the root sequence of local cell and neighbor
cell, confirm the conflict

Page34
Case 2
Please refer to the case of Low RACH Success

Rate Caused by Root Sequence Conflicts and
Inappropriate Cell Radius Planning

Page35
Interference Phenomenon
When random access is failed , there is no obvious

regularity of Preamble ID distribution. Preamble ID
distribute in the whole Preamble zone, that is GrpA ,
GrpB:

Page36
Interference Phenomenon (Cont.)
Random access failure due to interference, the TA

distribution is below:

Page37
Interference Phenomenon (Cont.)
Access problem due to interference can be located

by tracing the CELL DT and analyzing TTI data:
Analyze the number of random access distribution

base on different Preamble ID, confirm whether
random access failure exist in the whole Preamble ID
zone
Analyze characteristic of TA distribution when random
access failure occur , confirm the TA distribution
regularity

Page38
Case 3
Please refer to the case of Random Access failure

Caused by Narrow Band Interference within
LTE Frequency Band

Page39
Contents

Page40
Low RRC Connection Setup Success Rat

e Analysis
Low RRC Setup Success Rate common causes:
UE no reply
Resource allocation failure
Flow control

Page41
Contents
2.2.1 UE no reply
2.2.2 Resource allocation failure
2.2.3 Flow control

Page42
UE No Reply Overview
Description:
After eNodeB receive RRC

Connection Request , eNodeB
response UE with RRC Connection
Setup , then eNodeB starts the
timer to wait for an RRC Connection
Setup Complete sends from UE. If
eNodeB cannot receive RRC
Connection Setup Complete
message before the timer expires,
RRC setup is failed.

Page43
UE No Reply Phenomenon
KPI counter :
L.RRC.SetupFail.NoReply
Signaling flow :
Abnormal: RRC No Reply

Normal: RRC Succ

Page44
UE No Reply Causes
UE no reply common causes :
Parameter settings
T300
P0nominalPUSCH & PassLossCoeff
Interference
Clock problem
FrameOffset
Hardware & Device
TOP UE

Page45
Parameter Settings T300
T300
Parameter Name : Timer 300

Recommended Value : MS1000_T300(1000ms)
Start timer : UE sends RRCConnectionRequest message
Stop timer : UE receive RRCConnectionSetup or
RRCConnectionReject
Expire : UE enters the RRC_IDLE state

Page46
Case 4
Please refer to the case of Low RRC Connection

Setup Success Rate Caused by Incorrect
Parameter Setting in New Site

Page47
Parameter
Setting
Interference
Hardware &
Device
Parameter Settings P0nominalPUSCH

& PassLossCoeff
PUSCH dynamic power control calcultation :
PPUSCH (i ) min{ PCMAX ,10 log( M PUSCH (i )) Po _ PUSCH PL TF (i ) f (i )}
PCMAX : The maximum transmit power of UE
MPUSCH (i) : The PUSCH transmission bandwidth(RB

number) for i subframe
Po_pusch : The receive power expected by the eNodeB
: Path loss compensation factor
TF (i) : Offset of the power for the current MCS format
against the reference MCS format
f (i) : Adjustment of the PUSCH transmit power of the UE

Page48
Parameter
Setting
Interference
Hardware &
Device
Parameter Settings P0nominalPUSCH

& PassLossCoeff (Cont.)
P0nominalPUSCH
Parameter Name : P0 nominal PUSCH

Recommended Value : -67 dBm
PassLossCoef
Parameter Name : Path loss coefficient

Recommended Value : AL07(0.7)

Page49
Case 5
Please refer to the case of Deterioration of RRC

Connection Setup Success Rate Caused by
Incorrect PassLossCoef Configuration

Page50
Hardware &
Device
Interference Overview
The common causes leads to UE no reply caused by

interference are as follows :
Clock problem
RRC setup failure phenomenon due to interference

phenomenon are as follows:
KPI degrade in the whole zone

TDD network : Clock Reference Problem

Page51
Interference Clock Reference Proble

m
When the base station fails to synchronize with the

reference clock lasts for 200s , clock reference problem
ALM-26262 is reported
Alarm Impact
System clock is unavailable
The quality of services of the base station decreases,

resulting in handover failures and call drops. In certain
cases, the base station cannot provide services
Base station is out of synchronize with the reference clock of
adjacent cell
Affect the service of adjacent cell, such as access success
rate, call drop rate

Page52
Interference Clock Reference Proble

m Handling

Page53
Case 6
Please refer to the case of Low RRC Connection Setup Su
ccess Rate Caused by GPS Unlocked

Page54
Hardware & Device TOP UE
Access problem due to TOP UE, base on the distribution of UE,

might cause TOPN cell KPI deterioration or whole network KPI d
eterioration
During the access procedure, TOP UE might lead to the following

known problem:
UE does not response DRX configuration carried by the Reconfigur

ation message
During the UE process Reconfiguration message procedure , sched
uling period is abnormal
UE concurrent process the security mode and Reconfiguration mes
sage abnormally

Page55
Hardware & Device TOP UE (Cont.)
TOP UE troubleshooting
Analyze the CHR log to check whether TOP TMSI or TOP FGI causin
g huge amount of RRC setup failure
During RRC procedure , if user use random value to access, analyz
e the interval of the RRC setup failure user initiate RRC connection,
such as each RRC connection interval is 10s-15s, and channel quali
ty are approximately the same, in this case , RRC setup failure are
caused by specific users

Page56
Case 7
Please refer to the case of RRC Connection Setup Failure Due
to TOP UE

Page57
Contents
2.2.1 UE no reply
2.2.3 Flow control

Page58
Resource Allocation Failure Overview
Description:
After eNodeB receive the RRC Connection Request message sends

from UE, eNodeB responds RRC Connection Reject to UE due to re
source allocation failure, then RRC setup is failed

Page59
Resource Allocation Failure Overview (Co

nt.)
KPI counter :
L.RRC.SetupFail.ResFail.SRS
L.RRC.SetupFail.ResFail.PUCCH
L.RRC.SetupFail.ResFail.UserSpec
Signaling flow :

Page60
Resource Allocation Failure Analysis
The common causes leads to resource allocation failure :
Parameter setting
PucchSwitch
SriPeriodAdaptive
TddSrsCfgMode
S1 interface fault

Page61
Parameter setting PucchSwitch
PucchAlgoSwitch
Parameter Name : PUCCH algorithm switch

Recommended Value :
PucchSwitch:
In ultra-high-speed scenarios, the recommended value is Off
In other scenarios, the recommended value is On

Page62
Parameter setting PucchSwitch
PucchAlgoSwitch
Parameter Name : PUCCH algorithm switch

Recommended Value :
PucchSwitch:
In ultra-high-speed scenarios, the recommended value is Off
In other scenarios, the recommended value is On

Page63
Case 9
Please refer to the case of Low RRC Connection Setup Succes
s Rate Due to PUCCH Resource Congestion

Page64
Parameter setting SriPeriodAdaptive
SriPeriodAdaptive
Parameter Name : SRI Period Adaptive Switch

Recommended Value :
QCIADAPTIVE(QCIADAPTIVE), it is determined by RF engineer

Page65
Case 10
s Rate Due to SRI Resource Congestion

Page66
Parameter setting TddSrsCfgMode
TddSrsCfgMode
Parameter Name : TDD SRS Configuration Mode

Recommended Value :
ACCESS_ENHANCED(Access Enhanced), it is determined by RF engineer

Page67
Case 11
s Rate Due to limitation of UE Number Specification

Page68
S1 interface fault
S1 interface fault alarm
This alarm is reported in the following scenarios :
The configuration data of the S1AP layer is incorrect, the MME is abnor
mal, the S1 link is blocked, or the S1 interface setup failure is caused by
license limitation
The S1 link bearing the SCTP is unavailable for 18 seconds continuously
.The alarm is cleared when the S1 link bearing the SCTP becomes availa
ble again and stays available for 28 seconds
System Actions
The S1 interface setup procedure is reinitiated if the S1 interface setup

procedure fails

Page69
S1 interface fault (Cont.)
S1 interface fault alarm
Impact :
If the alarm is caused by a blocked S1 link, new admission requests will

be rejected over the faulty S1 interface
If the alarm is caused by other faults, the eNodeB releases all UEs that
have accessed the network over the faulty S1 interface

Page70
Case 12
s Rate Due to S1 Intermittent Disconnection

Page71
Contents
2.2 Low RRC Setup Connection Success Rate
2.2.1 UE no reply
2.2.3 Flow control

Page72
Flow control Overview
Description :
After eNodeB receives RRC Connection Request message sends fro

m UE, eNodeB responds RRC Connection Reject message to UE du
e to flow control , then RRC set up is failed

Page73
Flow control Overview (Cont.)
KPI counter :
L.RRC.SetupFail.Rej.FlowCtrl
L.RRC.ConnReq.Msg.disc.FlowCtrl
Signaling flow :
Maximum CPU board usage exceed 90%

Page74
Flow control Analysis
The common causes lead to flow control :
If the number of Msg3 eNodeB receives per second exceed CAPS
CPU usage is high

Page75
The Number of Msg3 eNodeB Receives p

er second exceed CAPS
If the number of Msg3 eNodeB receives per second exceed CAP

S, eNodeB will start flow control :
BBP board
BBP board starts Msg3 flow Control if Num of Msg3 exceed CAPS
The number of discards count to L.RRC.ConnReq.Msg.disc.FlowCtrl
MPT board
CPU usage 90%

Discards RRC Connection Request and Handover Request message
80% CPU usage <90%

Starts flow control, responds rejected UE with RRC Connection Reject or H
andover Failure message base on priority

Page76
Case 13
Please refer to the case of Deterioration of Radio Connection

Success Rate Due to UE Number Surge

Page77
CPU Usage is High
If the user number exceed the technical specification of CPU , C

PU starts flow control , however the procedure is the same as t
he flow control caused by the Number of Msg3 eNodeB Receive
s per second exceed CAPS
The possible causes of CPU usage is high exclude the number of

user growth:
Board reset
Starts CELL DT tracing , such as select large L1/L2 information

Page78
Case 14
Please refer to the case of RRC Connection Request Message

is Discarded due to Flow Control

Page79
Contents

Page80
NAS Procedure
NAS procedure is an interworking procedure between MME and

UE, consists of authentication and NAS security :
Authentication
NAS Security

Page81
NAS Procedure Failure Common Phenom

enon
The common phenomenon of NAS procedure failure :
NAS procedure is abnormal, MME initiates to release the UE

MME does not send Initial Context Setup REQ msg to eNodeB, eNo
deB initiates to release the UE

Page82
MME Initiates to Release the UE
When MME initiates to release the UE, the signaling flow is belo
w:

Page83
eNodeB Initiates to Release the UE
After eNodeB sent INITIAL_UE_MSG to MME 20s later, MME doe

s not send UE_CONTEXT_SETUP_REQ, eNodeB Initiates to Releas
e the UE

Page84
NAS Procedure Failure Analysis
MME Initiates to Release the UE
Emm-Cause : Unknown or missing APN
Emm-Cause : network failure
eNodeB configure the TAC, MME does not configure the TAC
assigned APN of MME not exist
Transport link abort and fault between MME and HSS
eNodeB Initiates to Release the UE
Abnormal UE

Page85
Case 15
Please refer to the case of Attach failure due to Missing Conf

iguration of TAC DNS

Page86
Contents

Page87
Low E-RAB Setup Success Rate Common

Causes
The common causes lead to low E-RAB setup success rate :
UE no reply
Insufficient radio resource
Security mode failure
MME problem
Transport network layer faults

Page88
Contents
2.4.1 UE no reply

Page89
UE No Reply
Description :
During the UE context setup and

E-RAB setup procedure, after eN
odeB sends RRC signaling messa
ge to UE, before the correspondi
ng timer expire eNodeB cannot r
eceive the response message fro
m UE, E-RAB setup is fail
UpUeCapInfoWaitingTi
mer
SecCmpWaitingTimer
UuMessageWaitingTimer
UuMessageWaitingTimer

Page90
UE No Reply Phenomenon
KPI counter :
L.E-RAB.FailEst.NoReply
Signaling flow :
UE release due to waiting RRC_SECUR_MODE_CMP message timeout

Page91
UE No Reply Analysis
The common causes lead to UE no reply :
Uplink weak coverage

Uplink interference

Page92
Uplink Weak Coverage
Definition :
Normally , uplink RSRP<=-130dBm is uplink weak coverage
Background noise of system bandwidth :

-174+10*logBW + NF =-174+10*log(15*1000)+2.5=-129.7dBm
BW is bandwidth , unit is Hz
NF is the noise factor of RF module , usually is 2~2.5
For the data domain , if SINR>-3dB ,that is uplink RSRP>-132dBm then t

he data can be decoded correctly. Usually , consider the uplink interfer
ence of adjacent cell user is 3dB. As conclusion, uplink RSRP<=-130dB
m is uplink weak coverage

Page93
Uplink Interference
Definition :
IN = RSRP SINR
If IN is near to background noise, that is no interference.

If IN is greater than background noise 5dB, that is uplink interference
Background noise of system bandwidth:
-174+10*logBW + NF =-174+10*log(15*1000)+2.5=-129.7dBm
BW is bandwidth , unit is Hz
NF is the noise factor of RF module , usually is 2~2.5

Page94
Summary
How to define the access setup success problem ?

Whats the common problem for RRC and setup ? How to lo
cate the problem ?

Page95
Thank you
www.huawei.com

LTE Access Fault Diagnosis ISSUE2 00

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LTE Access Fault Diagnosis ISSUE2 00

Hochgeladen von

Copyright:

Verfügbare Formate

LTE Access Fault Diagnosis

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Before learn this course, you should have:

Known the LTE basic knowledge

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

Get deep understanding of UE initial access flow

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Random Access Overview

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Random Access Procedure

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

UE Initial Attach Procedure

RRC connection setup

NAS authentication procedure

RRC connection setup cause:

Random Access Success Rate Definition

Random Access Success Rate = ( L.RA.GrpA.ContResolution

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

RRC Connection Setup Success Rate Defin

RRC Connection Setup Success Rate = L.RRC.ConnReq.Succ / L.R

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

E-RAB Setup Success Rate Definition

E-RAB Setup Success Rate = L.E-RAB.SuccEst / L.E-RAB.AttEst

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Low Random Access Rate Cause Analysi

Low random access rate common causes:

UE Accesses the Cell beyond the Cell Radius

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

UE Accesses the Cell beyond the Cell

UE locate within the area of cell coverage, but UE outside the

Time offset phenomenon

eNodeB detect the Preamble ID sends from UE has deviation, the

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Preamble sequence are generated from cyclic shifts

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

Suppose : Preamble format is set to 0 , low-speed cell ,

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

The rules of Preamble ID and TA detection :

Invalid detect range Null size is 6, TA=ceil(6*(800/839)/

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

The rules of Preamble ID and TA detection :

Relationship between TA1 and TA2 :

TA1+11+ TNCS -TA0 = TA2+ TNCS -TA0 = Toff

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

When time offset exist , UE select the Preamble ID randomly f

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

Preamble fix retransmission interval :

Suppose : PRAConfigIndex=3, the 4th subframe is RAR window after rand

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

Time Deviation (Cont.)

The retransmission interval is 20ms , therefore it is real user acces

Copyright 2016 Huawei Technologies Co., Ltd. All rights reserved.

UE Accesses the Cell beyond the Cell Ra

Perform CELL DT tracing, analyze TTI level data