Internal Use Only

LTE Access Optimization

CL Product Support Department

 内部公开▲

Table of Contents
 Access Procedure
 Access-Related Parameters
 Access-Related KPIs
 Common Access Optimization Approaches
 Analysis of Typical Access Failures
 Paging Procedure
 Paging-Related Parameters
 Paging-Related KPIs
 Common Paging Optimization Approaches
 Analysis of Typical Paging Failures
 内部公开▲

5 Random Access Scenarios

Scenario 1: Initial
access and transition
from RRC_IDLE state
to
RRC_CONNECTED

Scenario 5: Arrival of Scenario 2:

uplink data but uplink Reestablishment of
synchronization not radio link after a
complete failure

Scenario 4: Arrival of
downlink data but Scenario 3: Access to
uplink a new cell after a
synchronization not handover
complete
 内部公开▲

Random Access Procedure (1)

UE eNodeB EPC
A UE in Idle state but with data or
signaling message transmitted
initiates a service request
1. RA Preamble

2. RA Response Set up SRB0

3. RRCConnectionRequest

4. RRCConnectionSetup Set up SRB1

5. RRCConnectionSetupComplete
(including Service Request message)
6. Initial UE message
(Including Service Request
message)

7. Authentication

Set up default EPS bearer

 内部公开▲

Random Access Procedure (2)

UE eNodeB EPC
8. S1-AP: Initial Context Setup Request
9. UECapabilityEnquiry

10. UECapabilityInfomation
11. UE Capability Info Indication
12. SecurityModeCommand

13. SecurityModeComplete

14. RRCConnectionReconfiguration Set up SRB2 and DRB

15. RRCConnectionReconfigurationComplete

16. S1-AP: Initial Context Setup Response

 内部公开▲

Random Access Procedure (3)

UE eNodeB EPC
First Uplink Data

Update bearer
First Downlink Data

Detect User Inactivity

17. UE Context Release Request (Cause)

Update bearer

18. UE Context Release Command

19. RRC Connection Release

20. UE Context Release Complete

Contention-based Random Access – Contention 内部公开▲

Resolution
UE eNodeB

Random Access Preamble

1
Sent on PRACH with RA-RNTI

Random Access Response

2
RAP sent on PDSCH, addressed by
PDCCH using RA-RNTI

Scheduled Transmission
3
Data sent on PUSCH

Contention resolution
4
CR sent on PDSCH, addressed
by PDCCH using TC/C-RNTI
Contention-Free Random Access – Dedicated Pr 内部公开▲

eamble
UE eNodeB

Msg0: PDCCH order

0
Dedicated Preamble ID, Mask Index

Msg1: Random Access Preamble

1
Dedicated preamble

Msg2: RA Response
2
sent on PDSCH

Msg3: Contention requirement

3
Data or padding
 内部公开▲

Table of Contents
 Access Procedure
 Access-Related Parameters
 Access-Related KPIs
 Common Access Optimization Approaches
 Analysis of Typical Access Failures
 Paging Procedure
 Paging-Related Parameters
 Paging-Related KPIs
 Common Paging Optimization Approaches
 Analysis of Typical Paging Failures
 内部公开▲

Access-Related Parameters
1. Cell High-speed Attribute
2. Ncs Used to Generate PRACH Preamble
3. Logical Root Sequence Start Number Used to Generate PRACH Preamble
4. Number of Non-dedicated Random Access Preambles
5. Size of Random Access Preambles Group A
6. Threshold of Selecting Preamble Group
7. Message Power Offset for Group B
8. The Initial RB Number for Random Access Preambles
9. PRACH Configuration Index
10. Initial Power for Preamble of PRACH
11. Power Ramping Step for PRACH
12. Max retransmit number for PRACH
13. TTI Window Size for PRACH Response
14. Max Number of Messages HARQ Transmissions Message 3
15. MAC Contention Resolution Timer
16. Dedicated Preamble Life Time
 内部公开▲

Cell Attribute
Parameter Name: Cell High-speed Attribute
Value Range: Not high speed cell, high speed cell
Default value: Not high speed cell

终端最大发射功率

Cell Radius

Preamble Format RadiusThrdLRa (km) RadiusThrdHRa (km)

0 0 14
1 29 77
2 14 29
3 77 100
 内部公开▲

PRACH Format
TCP TSEQ TGP

CP Sequence Guard Pd
T RTD TMTD

Preamble TCP TMTD MaxCellRadius

format TMTDTGP (km)

R cell  min(TCP  TMTD , TGP )/6.67

0 103.2768 97.0176 5.2 14.545367

1 685.3824 516.384 16.7 77.418191

2 203.424 197.1648 16.7 27.994603

3 685.3824 716.6784 16.7 100.25223

One subframe (1ms)

15360  Ts 15360  Ts 15360  Ts 15360  Ts 15360  Ts 15360  Ts

One slot
2976  Ts
Supported Cell
3168  Ts 24576 T
24576  Tss Format 0 Radius Ranges:
21024  Ts 24576  Ts 15840  Ts Format 1
• 0 ~15 km
Format 2
• 30 ~ 77 km
6240  Ts 24576  Ts 24576  Ts 6080  Ts

• 15 ~ 30 km
21024  Ts 24576  Ts 24576  Ts Format 3
21993  Ts
• 77 ~ 100 km
 内部公开▲

Generation of PRACH Preamble

Parameter Name: Ncs Used to Generate PRACH Preamble
Value Range: 1 - 11
Default value: 10
Ncs Configuration for Preamble Generation (preamble formats 0-3)

Ncs for
Ncs for
Medium-/ Cell Ncs in Cell Ncs in
Number of High-rate Number of
SN Low-rate Radius Each Radius Each
Root u Scenarios Root u
Scenarios (km) Preamble (km) Preamble
(≥)
(<)

0 0 118.93 1 64 15 1.08 55 2
1 13 0.79 64 1 18 1.51 46 2
2 15 1.08 55 2 22 2.08 38 2
3 18 1.51 46 2 26 2.65 32 2
4 22 2.08 38 2 32 3.51 26 3
5 26 2.65 32 2 38 4.37 22 3
6 32 3.51 26 3 46 5.51 18 4
7 38 4.37 22 3 55 6.80 15 5
8 46 5.51 18 4 68 8.66 12 6
9 59 7.37 14 5 82 10.66 10 7
10 76 9.80 11 6 100 13.23 8 8
11 93 12.23 9 8 128 17.23 6 11
12 119 15.95 7 10 158 21.52 5 13
13 167 22.82 5 13 202 27.81 4 16
14 279 38.84 3 22 237 32.82 3 22
15 419 58.86 2 32 - -
 内部公开▲

Generation of PRACH Preamble

Parameter Name: Logical Root Sequence Start Number Used to Generate PRACH
Value Range: 0 - 837
Default Value: None
Root Zadoff-Chu Sequence Order for Preamble Format 0 – 3
Logical Root Physical Root Sequence Number u
Sequence Number (in increasing order of the corresponding logical sequence number)
0–23 129, 710, 140, 699, 120, 719, 210, 629, 168, 671, 84, 755, 105, 734, 93, 746, 70, 769, 60, 779
2, 837, 1, 838
24–29 56, 783, 112, 727, 148, 691
… …
204-263 152, 687, 144, 695, 134, 705, 138, 701, 199, 640, 162, 677, 176, 663, 119  
720, 158, 681, 164, 675, 174, 665, 171, 668, 170, 669, 87, 752, 169, 670, 88, 751, 107, 732, 81, 758, 82, 757, 100, 739, 98, 741, 71,
768, 59, 780, 65, 774, 50, 789, 49, 790, 26, 813, 17, 822, 13, 826, 6, 833
… …
328–383 225, 614, 224, 615, 221, 618, 220, 619, 127, 712, 147, 692, 124, 715, 193, 646, 205, 634, 206, 633, 116, 723, 160, 679, 186, 653, 167,
672, 79, 760, 85, 754, 77, 762, 92, 747, 58, 781, 62, 777, 69, 770, 54, 785, 36, 803, 32, 807, 25, 814, 18, 821, 11, 828, 4, 835
384–455 3, 836, 19, 820, 22, 817, 41, 798, 38, 801, 44, 795, 52, 787, 45, 794, 63, 776, 67, 772, 72, 767, 76, 763, 94, 745, 102, 737, 90, 749, 109, 730,
165, 674, 111, 728, 209, 630, 204, 635, 117, 722, 188, 651, 159, 680, 198, 641, 113, 726, 183, 656, 180, 659, 177, 662, 196, 643, 155,
684, 214, 625, 126, 713, 131, 708, 219, 620, 222, 617, 226, 613
… …
820-837 336, 503, 305, 534, 373, 466, 280, 559, 279, 560, 419, 420, 240, 599, 258, 581, 229, 610

Selection of PRACH Preamble
64 Preambles
n Preamble dedicated
p Preamble Group A
Parameter Name: Number of Non-
dedicated Random Access Preambles
Value Range: 4, 8, 12, 16, 20, 24, 28,
32, 36, 40, 44, 48, 52, 56, 60, 64
Default Value: 60
Parameter Name: Threshold of Selecting
Preamble Group
Value Range (bit): 56, 144, 208, 256
Default Value: 144 bit
内部公开▲
m Preamble non-dedicated
q Preamble Group B
Parameter Name: Size of Random
Access Preambles Group A
Value Range: 4, 8, 12, 16, 20, 24, 28,
32, 36, 40, 44, 48, 52, 56, 60
& Default Value: 56
Parameter Name: Message Power
Offset for Group B
Value Range (dB): 0, 5, 8, 10, 12, 15, 18
Default Value: 0 dB
 内部公开▲

Location of PRACH Preamble

Parameter Name: PRACH
Parameter Name: The Initial RB Number Configuration Index
for Random Access Preambles Value Range: 0 - 63
Value Range: 0 - 94 Default Value: 3
Default Value: None Uplink
subframe
Specifical Uplink
subframe subframe

nPRB  49
nPRB  48
nPRB  47
……………

nPRB  8
nPRB  7
………...

nPRB=2 nPRB  2
nPRB  1
nPRB  0

0n N 6
SR CCR#0 data: CQI CCR#0 pilot: CQI
RA UL
PRBoffset RB PUSCH CCR#1 data: CQI CCR#1 pilot: CQI

DMRS CCR#2 data: ACK/NACK CCR#2 pilot: ACK/NACK

RACH CCR#3 data: ACK/NACK CCR#3 pilot: ACK/NACK

 内部公开▲

PRACH Configuration Index

Frame Structure Type 1 Random Access Configuration for Preamble Formats 0
PRACH Configuration Index Preamble Format System Frame Number Subframe Number
0 0 Even 1

1 0 Even 4

2 0 Even 7

3 0 Any 1

4 0 Any 4

5 0 Any 7

6 0 Any 1, 6

7 0 Any 2 ,7

8 0 Any 3, 8

9 0 Any 1, 4, 7

10 0 Any 2, 5, 8

11 0 Any 3, 6, 9

12 0 Any 0, 2, 4, 6, 8

13 Number0 of Any PRACH Configuration Index

1, 3, 5, 7, 9
slots per
14 second0 Preamble Format 0Any Preamble Format 0,
1 1, 2,Preamble Format
3, 4, 5, 6, 7, 8, 9 2 Preamble Format 3
15 0 Even 9

 The number of random 50 0, 1, 2, 15 16, 17, 18, 31 32, 33, 34, 47 48, 49, 50, 63
accessing based on 100 3, 4, 5 19, 20, 21 35, 36, 37 51, 52, 53
contention resolution;
200 6, 7, 8 22, 23, 24 38, 39, 40 54, 55, 56
 Probability of RA colliding;
300 9, 10, 11 25, 26, 27 41, 42, 43 57, 58, 59
 Physical Cell ID.
500 12, 13 28, 29 44, 45 N/A
1000 14 N/A N/A N/A
 内部公开▲

PRACH Transmit Power

Parameter Name: Max retransmit number
for PRACH
P0 +5deta (P)
Value Range: 3, 4, 5, 6, 7, 8, 10, 20, 50,
100, 200 Incremental Power (optional)
Default Value: 8
P0 +3deta (P)
Parameter Name: Power Ramping Step for
PRACH P0 +2deta (P)
Value Range (dB): 0, 2, 4, 6 P0 +deta(P)
Default Value: 2 dB
P0
Parameter Name: Initial Power for
Preamble of PRACH
Value Range (dBm): -120, -118, -116, -114,
-112, -110, -108, -106, -104, -102, -100, -98, T1 T2 T3 T4 T5 T6
-96, -94, -92, -90
Default Value: -110 dBm

PRACH = min{PcMAX, PREAMBLE_RECEIVED_TARGET_POWER + PL}

PcMAX = Plmax + Pinitial + (N-1)*step

 内部公开▲

Contention Resolution
Parameter Name: TTI Window UE eNodeB
Size for PRACH Response
Value Range (ms): 2, 3, 4, 5, 6, 7, Msg1: Random Access Preamble
8, 10
Default Value: 10 ms

Msg2: Random Access Response

Parameter Name: Max Number of
Messages HARQ Transmissions
Value Range: 1 - 8
Default Value: 3
Msg3: Scheduled Transmission

Parameter Name: MAC

Contention Resolution Timer
Value Range (sf): 8, 16, 24, 32, 40, Msg4: Contention resolution
48, 56, 64
Default Value: 48 sf
 内部公开▲

Dedicated Preamble Life

UE
Parameter Name: Dedicated
Preamble Life Time
Value Range (ms): 0 - 100
Default Value: 100 ms
1
eNodeB
Msg0: PDCCH order
0
Dedicated Preamble ID, Mask Index
Msg1: Random Access Preamble
Dedicated preamble

Msg2: RA Response
2
sent on PDSCH

Msg3: Contention requirement

3
Data or padding
 内部公开▲

Table of Contents
 Access Procedure
 Access-Related Parameters
 Access-Related KPIs
 Common Access Optimization Approaches
 Analysis of Typical Access Failures
 Paging Procedure
 Paging-Related Parameters
 Paging-Related KPIs
 Common Paging Optimization Approaches
 Analysis of Typical Paging Failures
 内部公开▲

Access Performance
Access

Initial E-RAB setup success ratio PS DT/CQT 97% *

RRC setup success ratio PS Stat. 96%

E-RAB setup success ratio PS Stat. 97%

System Availability

Cell availability PS Stat. 99%

E-RAB setup congestion ratio PS Stat. 1%

Paging congestion ratio PS Stat. 1%

*This value is for reference only. For a specific project, this index should be determined
according to the project or contract requirements.
 内部公开▲

RRC Connection Setup Success Ratio

UE EUTRAN
RRC Connection Request

RRC Connection Setup

RRC Connection Setup Complete

RRC connection setup success ratio = Number of successful RRC

connection setups/Number of RRC connection requests
= C373200021/C373200020 x 100%
 内部公开▲

Initial E-RAB Setup Success Ratio

eNodeB MME

Initial Context Setup Request

Initial Context Setup Response

Initial E-RAB setup success ratio = Number of successful initial E-RAB

setups/Number of initial E-RAB setup requests
= C373210492/C373210494 x 100%
 内部公开▲

E-RAB Setup Congestion Ratio

eNodeB MME

E-RAB Setup Request

E-RAB Setup Response

E-RAB setup congestion ratio = Number of failed E-RAB setup attempts of

a cell/Number of E-RAB setup requests of a cell
= C373210492/C373210494 x 100%

Cell Availability
CRM
The DRM often initiates the
deletion of a cell setup in one of the
following cases:
1. Normal cell setup deletion
2. Cell setup timeout
3. Cell setup failure
4. Manual blocking/unblocking
operation
5. Audit failure
6. S1 link interruption
Cell availability = Serving time of the
cell/Granularity
= C373940102/Gr x 100%
CCM
EV_CRM_CCM_CELL_CONFIG_REQ
After the CCM is powered
on, a timer is started,
enabling the serving time of
the cell to be reported to
the PM every 15 minutes.
The formerly reported
values will be cleared after
the reporting.
EV_CRM_CCM_CELL_DEL_REQ
内部公开▲
CCMI
EV_CRM_CCM_CELL_CONFIG_REQ
After RNLU/CMAC/RRU is
configured, the service start
time of the cell is recorded.
EV_CRM_CCM_CELL_DEL_REQ
After RNLU/CMAC/RRU is
deleted, the service end time
of the cell is recorded.
 内部公开▲

Ways to Obtain Network Performance Indexes

Obtaining
Network
Performance
Indexes

Traffic Data
DT/CQT
Analysis

Network Network
Performance Performance CNA/STS
Evaluation Warning
 内部公开▲

Traffic Data Analysis Methods

performance cells
TOP N lowest Time-trend map

Traffic Data
Analysis
Methods

Comparison
Region location
 内部公开▲

Table of Contents
 Access Procedure
 Access-Related Parameters
 Access-Related KPIs
 Common Access Optimization Approaches
 Analysis of Typical Access Failures
 Paging Procedure
 Paging-Related Parameters
 Paging-Related KPIs
 Common Paging Optimization Approaches
 Analysis of Typical Paging Failures
 内部公开▲

Access Problem Analysis Procedure

Start
Start

Find an access problem Drive test data

with aAccess Problemtool
data analysis DT data

Is there any
Accessfailure?
access Failure

Does
RRCRRC connection
connection RRC
RRC setup problem
connection problem
fail to set up?
Failure

DoesAuthentication
authentication or Authentication or
Authentication problem
encryption
Failurefail? encryption problem

Does E-RAB
E-RAB fail to set
establish E-RABestablish
setup problem
up?
Failure E-RAB problem

Other abnormalities
Abnormal problem

End
End
 内部公开▲

RRC Setup Failure Analysis Procedure

RRC setup problem

UE send No UE abnormal
?
Preamble? problem
Yes
eNodeB received No Adjust PRACH
Preamble parameters

Yes
UE received RA No Adjust PDCCH
response ? parameters
Yes
UE sent RRC No UE abnormal
request? problem

Yes
No Adjust UL open
eNpdeB received loop power control
RRC request? parameters
Yes

eNodeB sent setup No Congestion or other

message? problem
Yes No Adjust PDCCH
parameters
UE received setup No
message? Cell reselection
Optimize cell
Yes Yes reselection

UE sent setup No Radom Access

complete message? contention

Yes
eNodeB received No Adjust UL open
setup complete loop power control
message? parameters
Yes

End
Typical Reasons for a RRC Connection Setup Fa 内部公开▲

ilure
Call origination in poor coverage area

Uplink RACH problem

Paging failure in the TAU procedure

Improper cell reselection parameter settings, causing cells not

to be timely reselected, and the best cell not to be selected

Improper RS power and power distribution parameter settings

Congestion

Device failure
 内部公开▲

Solutions for a RRC Connection Setup Failure

Make RF optimization to eliminate coverage holes or over-coverage

Optimize TA boundaries to reduce unnecessary and frequent

location update. If possible, set the boundary in a low-dense area

Adjust the values of cell reselection parameters, ensuring the UE is

be able to quickly select the best cell for call origination

If possible, modify the settings of random access parameters and

power distribution parameters, such as power offsets of RACH,
PCCH, PDCCH, PDSCH, and/or Msg3

Modify RS power, ensuring it meets the expected cell coverage

radius requirement
 内部公开▲

RRC Connection Problem Analysis (1)

Problem:
One UE sends an RRC Connection Request message,
but the eNodeB does not receive it.
Analysis:
 If the downlink RSRP is quite low, it is likely caused by
poor coverage.
 If the downlink RSRP is normal (greater than -105
dBm), the cause often lies in the RACH, and the
reasons may be one of the following:
 The power of the Preamble is not high enough
 The output power of the UE is lower than the
requirement
 The eNodeB device does not work properly, which
leads to high VSWR
 The cell radius is not properly set
 内部公开▲

RRC Connection Problem Analysis (2)

Problem:
The eNodeB receives an RRC connection setup request
from one UE and returns an RRC Connection Setup
message, but the UE does not receive the message.
Analysis:
 Poor Coverage
If possible, improve the coverage by adding eNodeBs
or optimizing the antenna feeder system; otherwise,
increase RS power or reset the power distribution
parameter.

 Improper cell selection and reselection

Quicken cell selection and reselection by resetting the
related parameters.
 内部公开▲

RRC Connection Problem Analysis (3)

Problem:
The eNodeB receives an RRC connection setup request
from one UE but returns an RRC Connection Reject
message.
Analysis:
In this case, check the reason value. There are two
reason values for RRC connection reject:
 Congestion: which means network congestion
occurs. In this case, check the network load.
 Unspecified: In this case, it is required to check the
logs to find out the specific reason.
 内部公开▲

RRC Connection Problem Analysis (4)

Problem:
One UE receives an RRC Connection Setup message,
but does not return a Setup Complete message.
Analysis:
If the downlink signals are of good quality, it is likely to be
caused by a UE failure.
 内部公开▲

RRC Connection Problem Analysis (5)

Problem:
One UE sends an RRC Setup Complete message, but
the eNodeB does not receive it.
Analysis:
This problem is unlikely to occur.
As the initial uplink power control causes the transmit
power of the UE to increase, there is not a good solution
yet.
 内部公开▲

Authentication/Encryption Failure -- MAC Failure

UE MME
AUTHENTICATION REQUEST
Start T3460
AUTHENTICATION FAILURE (cause = "MAC failure")
Start T3418 Stop T3460
IDENTITY REQUEST
Start T3470
IDENTITY RESPONSE (IMSI)
Stop T3470
AUTHENTICATION REQUEST
Stop T3418 Start T3460
AUTHENTICATION RESPONSE
Stop T3460
 内部公开▲

Encryption/Authentication Failure -- Sync Failure

UE MME

AUTHENTICATION REQUEST
Start T3460
AUTHENTICATION FAILURE (cause = "synch failure")
Start T3420 Stop T3460
Perform
re-synch
with HSS
AUTHENTICATION REQUEST
Stop T3420 Start T3460
AUTHENTICATION RESPONSE
Stop T3460
 内部公开▲

Typical Reasons for E-RAB Setup Failure

Call origination over weak signals

Access rejection from UE/MME

Improper parameter setting

Corner Effect

Device failure
 内部公开▲

Solutions for E-RAB Setup Failure (1)

Reason:
Call origination over weak signals
Solution:
 Poor coverage
 If the uplink coverage is poor, check the uplink
interference.
 If the downlink coverage is poor, first, check the
UE’s demodulation performance; then, improve the
coverage with optimization methods, including
adding eNodeBs, RF optimization, adjusting
antenna feeder system, and increasing RS power.
 UE not residing in the best cell when originating a call
 Increase the start threshold of co-frequency cell
reselection to quicken cell reselection, enabling the
UE to quickly reside in the best cell and originate
the call there.
 内部公开▲

Solutions for E-RAB Setup Failure (2)

Reason:
Access rejection from UE/MME
Solution:
 Rejection from the UE due to a UE failure: Upgrade
HW/SW version or replace the UE with another UE.
 Rejection from the MME: Analyze the STS signaling
trace data on the eNodeB side, check whether the
signals are of poor quality or the S1 link interrupts. If
the eNodeB side works properly, submit the problem
to the CN team for troubleshooting.
 内部公开▲

Solutions for E-RAB Setup Failure (3)

Reason:
Improper parameter setting
Solution:
Adjust the parameter settings according to the specific
scenario.
First of all, check the parameter settings and compare
the settings of the cells suffering access problem with
those of a normal cell. If they are different, check
whether the settings affect the access of the UEs. If yes,
reset the parameters.
 内部公开▲

Solutions for E-RAB Setup Failure (4)

Reason:
Corner effect
Solution:
Conduct RF optimization: Adjust the antenna or RS
power, enabling the antenna of the target cell to cover
beyond the corner, and making cell reselection take
place before the corner; or let the antenna of the current
cell cover beyond the corner, avoiding the quick change
of signals arisen from the corner.
 内部公开▲

Solutions for E-RAB Setup Failure (5)

Reason:
Device Failure
Solution:
Find out and solve the failure, such as eNodeB failure,
BPL or other board failure.
If the problem persists, ask the R&D team for
assistance.
 内部公开▲

Table of Contents
 Access Procedure
 Access-Related Parameters
 Access-Related KPIs
 Common Access Optimization Approaches
 Analysis of Typical Access Failures
 Paging Procedure
 Paging-Related Parameters
 Paging-Related KPIs
 Common Paging Optimization Approaches
 Analysis of Typical Paging Failures
 内部公开▲

Access Problem due to PRACH not Planned (1)

Symptom:
In a site test, the UE under one cell can make a call in the areas opposite to the
antenna, but it is difficult to access or even unable to access the eNodeB in the
areas that other cells can also cover. The RSRP and CINR meet the access
requirements.
Analysis:
1. After the other two cells of the eNodeB are disabled, the UE can access the
eNodeB if the signals meet the access requirements.
2. After all three cells are enabled, access is difficult or unable in the overlapped
coverage areas of the three cells. The UE sends the RRC Connection Request
message, but the system does not respond.
3. Signaling on the eNodeB side shows the system receives the message and
responds, but the response is not received by the UE.
4. Check results of the access parameter configuration show the parameter
“Logical root sequence start number used to generate prach preamble” of the
three cells is set to 0, and the parameter “NCS used to generate prach
preamble” is set to 11. This means the access preambles of the three cells sent
to the UE are the same. When the UE is in the overlapped coverage area, the
three cells receive the message from the UE and returns the MSG4 message at
the same time. The UE receive two MSG4 messages and cannot demodulate
them, so the access attempt fails.
 内部公开▲

Access Problem due to PRACH not Planned (2)

Solution:
Reset the PRACH parameters, including “Logical root sequence start
number used to generate prach preamble”, and “NCS used to generate
prach preamble”. After the resetting, the UE can access the system in
any coverage area of the eNodeB so long as the signals are of good
quality.
Summary:
Prior to the kickoff of a project, it is required to plan access-related
parameters in addition to PCI and neighbor cells.
UE Unable to Access due to Incorrect Parameter 内部公开▲

Configuration (1)
Symptom:
In the pre-preliminary acceptance test of PGP, it is found under the cell
whose PCI is 50, UEs cannot access the SMV eNodeB and several access
failures take place in one minute. However, the radio signal quality is found
good (RSRP = -104 dBm, CINR = 102 dB).
UE Unable to Access due to Incorrect Parameter 内部公开▲

Configuration (2)
Analysis:
The UE should report the Status packet to the eNodeB after it receives the LTE
DL AM All PDU message.
However, the analysis of UE logs shows the eNodeB does not receive the
Status packet. As a result, the eNodeB repeats sending the message in the RLC
layer.
On the UE side, the UE has received the message 4 times, while on the eNodeB
side, the RNLU sends the RnluRnlcErrInd message to the RNLC, and the RNLC
returns the RrcConnectionRelease message, causing the UE’s failure to access.
By default, our network parameter setting allows SRB signaling to be repeatedly
transmitted for up to 16 times.
Check the parameter setting and find the maximum RLC AM retransmission time
was incorrectly set to 4.
Meanwhile, the SRB RLC Type of the eNodeB is also incorrectly configured as
UM (Unacknowledged Mode), which should be AM (Acknowledged Mode).

Solution:
Modify the SRB RLC Type to be AM and the problem is solved.
 内部公开▲

Access Failure due to a UE Fault (1)

Symptom:
In the pre-preliminary acceptance test of PGP, it is found Samsung UEs
fail to work from time to time, leading to access failure.
 内部公开▲

Access Failure due to a UE Fault (2)

Analysis:
First, the UE logs are analyzed. The radio environment is good as the
RSRP is -82 dBm and the CINR is 19 dB. But after the UE receives the
“Activate default EPS bearer context request” message from the MME,
it rejects the request through the “ulInformationTransfer” message on
the uplink and returns the reason “PTI unmatched”.
However, the comparison of the signaling elements in the normal
procedure with those in the abnormal procedure shows the PTI
(Procedure transaction identity) sent by the MME is the same as the
PTI carried in the attach request message of the UE.
Therefore, it is concluded that the problem is caused by Samsung UE’s
failing to maintain the PTI properly.
Solution:
Update the HW/SW version of Samsung UE or replace Samsung UE
with other UEs, for example, Qualcomm UEs do not report such a
problem.
内部公开▲