RACH Setup Analysis & Case Study 1
1/28/16
Confidential
© Nokia 2014
Summary Objectives: To study what is RACH & its types. Compl RACH stp SR counters used & calculations. To study Small message & Large message. Compl RACH stp SR trend for N2 (City wise). As per request PrachCS (10 13) , prachConfIndex (319 ) and RootSeqIndex(613) changed for 244B1LN1 on 18th Nov & KPI was monitored. Compl RACH stp SR Analysis & Case Study done for Worst Cells (Top 10 Cells of N2 region & Top 5 cells of Hsinchu).
Analysis &Troubleshooting Results: N2, New Taipei city, Hsinchu & Taoyuan is having 87% Small message & 13 % Large message. Suggest to pre-check PCI confusion/collision after found some Top 10 worst cell cases of very low Compl RACH stp SR. Layer1 optimization is required based on the case study 242H2LN1 which is overshooting to Shulin. Compl RACH stp SR improved for 244B1LN1 after parameter changes on 18th Nov due to Preamble format change from 01 causing the cell radius increased. 2 1/28/16 © Nokia 2014 Confidential To further study & implement the three parameters in 31304LN1_112 & 30314LN1_111.
Random Access Procedure (#1) RACH has very important functionality especially in LTE (and in WCDMA as well). The main purpose of RACH can be described as follows. • Achieve UP link synchronization between UE and eNB • Obtain the resource for Message 3 (e.g, RRC Connection Request) The use cases are usually: • Initial access when establishing a radio link (RRC_IDLE to RRC_CONNECTED) • To re-establish a radio link after a radio link failure • During the handover process to establish uplink synchronization to the target cell
No Retransmission 3
1/28/16
Confidential
© Nokia 2014
Random Access Procedure (#2) There are two forms of Random Access procedures : (a) Contention based (risk of collision). If the same PRACH preamble from multiple UE reaches the NW at the same time, this kind of PRACH collision is called "Contention" and the RACH process that allows this type of "Contention" is called "Contention based" RACH Process. In this kind of contention based RACH process, Network would go through additional process at later step to resolve these contention and this process is called "Contention Resolution" step. i) UE --> NW : RACH Preamble (RA-RNTI, indication for L2/L3 message size) ii) UE <-- NW : Random Access Response (Timing Advance, T_C-RNTI, UL grant for L2/L3 message) iii) UE --> NW : L2/L3 message iv) Message for early contention resolution
(b) Contention free. In this case RACH Preamble is assigned to UE by the eNB. i) UE <--NW : RACH Preamble (PRACH) Assignment ii) UE --> NW : RACH Preamble (RA-RNTI, indication for L2/L3 message size) iii) UE <--NW : Random Access Response (Timing Advance, C-RNTI, UL grant for L2/L3 message) 4
1/28/16
Confidential
© Nokia 2014
Complete RACH Setup SR Formula KPI ID
KPI Title
LTE_105 Complete RACH Setup Success 6d Rate
Unit
RL60 KPI Formula (with Counter Name)
%
100 * SUM(RRC_CON_RE_ESTAB_ATT + SIGN_CONN_ESTAB_ATT_MO_S + SIGN_CONN_ESTAB_ATT_MT + SIGN_CONN_ESTAB_ATT_MO_D + SIGN_CONN_ESTAB_ATT_OTHERS + SIGN_CONN_ESTAB_ATT_EMG + SIGN_CONN_ESTAB_ATT_HIPRIO + SIGN_CONN_ESTAB_ATT_DEL_TOL) / SUM(RACH_STP_ATT_SMALL_MSG + RACH_STP_ATT_LARGE_MSG)
RACH Success (Numerator): The number of successful RACH attempts Formula: SUM(RRC_CON_RE_ESTAB_ATT + SIGN_CONN_ESTAB_ATT_MO_S +SIGN_CONN_ESTAB_ATT_MT + +
SIGN_CONN_ESTAB_ATT_MO_D +SIGN_CONN_ESTAB_ATT_OTHERS +SIGN_CONN_ESTAB_ATT_EMG SIGN_CONN_ESTAB_ATT_HIPRIO +SIGN_CONN_ESTAB_ATT_DEL_TOL)
RACH Attempts (Denominator): The number of RACH Setup Attempts Formula: SUM(RACH_STP_ATT_SMALL_MSG+ RACH_STP_ATT_LARGE_MSG)
RACH Failures : RACH Attempts - RACH Success
Complete RACH Setup Success Rate= 100*(RACH Success)/ (RACH Attempts) 5
1/28/16
Confidential
© Nokia 2014
Compl RACH stp SR- City Comparison Region N2: Compl RACH stp SR- : 68.71 RACH_STP_ATT_SMALL_MSG: 594.14 million ( 87.15%) RACH_STP_ATT_LARGE_MSG: 87.72 million (12.85%)
Hsinchu: Compl RACH stp SR- : 68.20 RACH_STP_ATT_SMALL_MSG: 29.82 million ( 87.46%) RACH_STP_ATT_LARGE_MSG: 4.28 million (12.54%)
Data taken Since 1st Nov(1st Nov-2nd Dec) Mentioned above are Daily average values 2013 NSN NWP RF - TWM Project 6
© Nokia Solutions Networks
NSN TWM Project
New Taipei: Compl RACH stp SR- : 69.03 RACH_STP_ATT_SMALL_MSG: 398.44 million (87.01 %) RACH_STP_ATT_LARGE_MSG: 59.48 million (12.99%)
Taoyuan: Compl RACH stp SR- : 68.90 RACH_STP_ATT_SMALL_MSG: 165.89 million (87.37 %) RACH_STP_ATT_LARGE_MSG: 23.97 million (12.63%)
N2 – RACH Attempt KPI Performance
RACH setup attempts are increasing with the traffic growth. 7
1/28/16
Confidential
© Nokia 2014
N2 – RACH Setup KPI Performance
Hsinchu county is having lower Compl RACH stp SR among all the cities.
8
1/28/16
Confidential
© Nokia 2014
Complete RACH Setup SR Top 10 Worst Cells(18 to 24 Nov): Compl LNB LNBT RACH RACH RACH LNCE RACH TS_I S_NA _Atte _Succ _Failu L_ID stp D ME mpts ess res SR 24210 242L7L 9 N1
113
2.38
Remarks
Degraded between 17th to 28th 1888054 1843204 448495 Nov. Back to normal (70%) after 3 8 28 Nov.
Actions Hardware issue suspected, No major parameter/PCI change, No Action
10/Nov: PCI retuned(375137) -KPI degraded because of mod-3 220N4LN1(2.6 Km collision, away) having same 5504850 1387336 4117514 27/Nov: mod of PCI PCI as of 23895LN1, changed(137135)-KPI improved need to retune PCI for to 55.5 (7 days avg), more 220N4LN1. improvement expected. Suspect PCI confusion, Need to CR Sent to TWM on 8 3550031 82009 3468022 retune PCI Dec Cell is overshooting KPI suddenly degraded after 12 at 4th tier. Down-tilt 3810110 1452336 2357774 Nov, no major issue/changes proposed Further observed, no alarm found analysis with cluster owner Border cell, facing towards open Overshooting cell, 5871155 3555257 2315898 area Down-Tilt suggested
23803 23895L 2 N1
111
25.2
23706 237C5L 1 N1
111
2.31
24212 242H2L 4 N1
112
38.12
113
60.55
112
63.53
5732220 3641924 2090296 Overshooting cell, 42 m height
Down-Tilt suggested
© Nokia 2014 113 65.09
5614980 3654926 1960054 Overshooting cell, 36 m height
Down-Tilt suggested
112
4794851 2941829 1853022 Overshooting cell. 48 m height
Down-Tilt suggested
23804 23882L 5 N1 24700 24702L 3 N1 23604 9 236F8L 1/28/16 4 Confidential N1 24210 242K3L 8 N1
61.35
Complete RACH Setup SR Top 10 Worst Cells(18 to 24 Nov): Traffic Data RLC SDU LNB Compl RACH_F DL-DTCH RRC_CONN LNBTS_NA LNCE RACH_At RACH_S TS_I RACH ailures( Traffic Vol _UE_MAX( ME L_ID tempts uccess D stp SR Sum) in Avg) MB(Sum) 24210 242L7LN1 113 2.38 18880543 448495 18432048 173716.95 41.28 9 23803 23895LN1 111 25.2 5504850 1387336 4117514 962842.16 127.42 2 23706 237C5LN1 111 2.31 3550031 82009 3468022 17207.04 12.14 1 24212 242H2LN1 112 38.12 3810110 1452336 2357774 897059.13 124.57 4 23804 23882LN1 113 60.55 5871155 3555257 2315898 1573798.77 307.42 5 24700 24702LN1 112 63.53 5732220 3641924 2090296 1631757.4 270 3 23604 236F8LN1 113 65.09 5614980 3654926 1960054 1644790.79 264.71 4 24210 242K3LN1 112 61.35 4794851 2941829 1853022 1572461.98 222.14 8 22001 112 64.13 4891958 3137345 1754613 1807902.87 234.71 8Cells22016LN1 highlighted in red are the high traffic cells in terms of RLC SDU DL24213 DTCH Traffic Vol(Sum of 7 days) & RRC_CONN_UE_MAX (Daily avg.) 198.29 24218LN1 111 63.17 4753377 3002624 1750753 1499749.45 © Nokia 2014 010 1/28/16 Confidential
Hsinchu Complete RACH Setup SR Top 5 Worst Cells(18 to 24 Nov): LNB Compl RACH RACH_ RACH_ LNBTS_ LNCE TS_I RACH _Atte Succe Failur NAME L_ID D stp SR mpts ss es
Remarks
Actions
RACH Fail in poor coverage Proposed to change due to hilly terrain Parameters
31300 31304LN1 2
112
12.46
1109339
30301 30314LN1 2
111
64.29
2337897 1502936
834961
30003 30087LN1 0
111
64.91
2213812 1437026
776786
30200 30209LN1 5
113
60.37
1932079 1166320
765759 number of attempts in poor Down-Tilt suggested
30004 300K7LN1 4
112
138271
971068
Site having 54 M height, Cell facing towards open area
Proposed to change Parameters
This cell is overshooting far Down-Tilt suggested away. Overshooting cell, large
59.59
1826482 1088409
coverage This cell is overshooting far 738073 away & taking traffic in Down-Tilt suggested poor coverage
HSINCHU is having lower Complete RACH Setup SR among the all Cities. 11 1/28/16 © Nokia 2014 So Top 5 worst cells are filtered out & analyzed Confidential
AR/CR Site Name
Comments
242H2LN 1 23882LN 1 242K3LN 1 24218LN 1 30087LN 1 30209LN 1 300K7LN 1 24702LN 1 236F8LN 1 22016LN 1
Down Tilt 242H2LN1 S2 (PCI= 224) from M-4 / E-12 to M-4 / E-14 Down Tilt 23882LN1 S3 (PCI= 404) from M-0 / E-8 to M-2 / E8 Down Tilt 242K3LN1 S2 (PCI= 315) from M-4 / E-15 to M-6 / E-15 Down Tilt 24218LN1 S1 (PCI= 435) from M-8 / E-12 to M-8 / E-14 Down Tilt 30087LN1 S1 (PCI= 168) from M-9 / E-6 to M-9 / E9 Down Tilt 30209LN1 S3 (PCI= 398) from M-10 / E-10 to M-10 / E-12
12
1/28/16
Confidential
Action Site
242H2LN 1 23882LN 1 242K3LN 1 24218LN 1 30087LN 1 30209LN 1 300K7LN index LTE Objects-DN phyCellId Down TiltMOD 300K7LN1 S2 (PCI= 82) from M-0 / E-3 to M-0 / E-5 207 1 MRBTS-237061/LNBTS-237061/LNCEL-111 Down Tilt 24702LN1 S2 (PCI= 64) from M-10 / E-8 to M-10 / 24702LN MOD MRBTS-237061/LNBTS-237061/LNCEL-112 209 E-10 1 index LTE Objects-DN PrachCS Down Tilt 236F8LN1 S3 (PCI= 311) from M-2 / E-8 to M-4 / E- 236F8LN MRBTS-313002/LNBTS8 1 313002/LNCEL-112 13 MOD Down Tilt 22016LN1 S2 (PCI= 13) from M-6 / E-10 to M-10 / 22016LN MRBTS-303012/LNBTSE-10 1 index LTE Objects-DN prachConfIndex 303012/LNCEL-111 13 MOD MRBTS-313002/LNBTS313002/LNCEL-112 19 MOD MRBTS-303012/LNBTSindex LTE Objects-DN RootSeqIndex 303012/LNCEL-111 19 MOD © Nokia 2014 MRBTS-313002/LNBTS313002/LNCEL-112 13 MOD MRBTS-303012/LNBTS-
Action Cell
112 113 112 111 111 113 112 112 113 112
Parameters Description (PrachCS, PrachConfIndex & RootSeqIndex )
13
1/28/16
Confidential
© Nokia 2014
PRACH Configuration Index and Frequency Offset RACH operation uses 1.08 MHz bandwidth (6 PRB) The location of those resource blocks is dynamically defined by 2 RRC Layer Parameters (PRACH Configuration Index and PRACH Frequency offset) (a) PRACH Configuration Index, prachConfIndex (default=3, possible values 3-8 and 19-24) (b) 4 possible PRACH durations for FDD ( PRACH configuration index parameter selects one of the 4)
-For example, the length of PRACH with preamble format 0 is (3168 + 24567) Samples. -Preamble format 4 is for TDD.
14
1/28/16
Confidential
© Nokia 2014
PRACH Frequency Offset: Indicate the location of preamble in the frequency domain. Scheduled by eNB.
PRACH Cyclic Shift (PrachCS) (a) PrachCS is used to increase preamble capacity, it defines how many cyclic shifts are needed to generate the preamble. (b) Controls how many preambles can be generated from one root sequence (c) PrachCS depends on the cell size -Different cell ranges correspond to different PrachCS.
15
1/28/16
Confidential
© Nokia 2014
3GPP 36.211: PRACH Configuration Index
16
1/28/16
Confidential
© Nokia 2014
Preamble Format and Cell Range The physical layer random access preamble, shown in figure below, consists of a cyclic prefix of length TCP and a sequence part of length TSEQ
17
1/28/16
Confidential
© Nokia 2014
Root Sequence Index and Cell Range The cell range i.e. the requirement for guard period defines the length of the cyclic shift, NCS , which therefore determines how many root sequences are needed per cell for a certain coverage. The UE starts with the broadcasted root index and applies cyclic shifts to generate preambles: #cyclic shifts per root sequence =sequence) / NCS ) #root sequences needed (64 sequences for 64 preambles per cell) = roundup(64 / #cyclic shifts per root sequence)
18
1/28/16
© Nokia 2014
Confidential
Zero Correlation Zone Configuration(0-15) (regarding to the cell radius & maximum multiple-path delay).
244B1LN1 Pre-Post Comparison
19
1/28/16
Confidential
© Nokia 2014
244B1LN1 KPI Trend Befor e
After Date:18 Nov PrachCS(1013) & prachConfindex(319) RootSeqIndex(613)
Befor e
After
Befor e
After
20
1/28/16
Confidential
© Nokia 2014
244B1LN1 KPI Trend Befor e
After Date:18 Nov PrachCS(1013) & prachConfindex(319) RootSeqIndex(613)
Befor e
21
1/28/16
Confidential
After
© Nokia 2014
OSS KPI Performance Monitoring_L700 KPI observation period: 1-Nov to 17-Nov (pre-parameter change) & 18-Nov to 02-Dec (post-parameter change) KPI
Site
244B1L N1 244B1L Compl RACH stp SR N1 244B1L RACH Stp Completion SR N1 244B1L RRC STP ATT N1 244B1L RRC conn stp SR N1 244B1L E-RAB SAtt N1 244B1L DATA RB STP ATT N1 244B1L RB DR N1 244B1L E-UTRAN E-RAB stp SR N1 244B1L RB SR N1 E-UTRAN Avg PRB usage per 244B1L TTI DL N1 22 1/28/16 © Nokia 2014 244B1L Confidential Avg PRB usage per TTI UL N1 244B1L E-UTRAN Cell AvailR
Before
After
100.00 100.00
Delta
Delta %
0.00
0.00
32.67
59.80
27.13
83.04
78.41
94.81
16.40
20.92
18744.8 19405. 661.11 2 93 99.89
99.87
-0.02
18530.8 19066. 535.44 2 27 30226.6 30516. 289.82 5 47 0.11
0.16
0.05
99.96
99.94
-0.01
99.89
99.84
-0.05
3.21
3.97
0.75
0.70
0.80
0.10
3.53 0.02 2.89 0.96
Status Maintain ed Improve d Improve d Increase d Maintain ed Increase d Increase d
42.39 Degraded Maintain ed Maintain -0.05 ed Increase 23.50 d Increase 14.29 d Improve -0.01
Remark Major improvement Major improvement
OSS KPI Performance Monitoring_L1800 KPI observation period: 1-Nov to 17-Nov (pre-parameter change) & 18-Nov to 02-Dec (post-parameter change) KPI
Site
244B1L N1 244B1L Compl RACH stp SR N1 244B1L RACH Stp Completion SR N1 244B1L RRC STP ATT N1 244B1L RRC conn stp SR N1 244B1L E-RAB SAtt N1 244B1L DATA RB STP ATT N1 244B1L RB DR N1 244B1L E-UTRAN E-RAB stp SR N1 244B1L RB SR N1 E-UTRAN Avg PRB usage per 244B1L TTI DL N1 23 1/28/16 © Nokia 2014 244B1L Confidential Avg PRB usage per TTI UL N1 244B1L E-UTRAN Cell AvailR
Before
After
100.00 100.00
Delta
Delta %
0.00
0.00
12.54
61.10
48.56
387.3 6
91.13
98.82
7.68
8.43
6771.06 99.48
6724.0 -47.06 0 99.36
-0.12
-0.69 0.12
6240.7 -194.56 -3.02 3 11792.4 11864. 72.05 0.61 1 47 6435.29
Status
Remark
Maintain ed Improve Major d improvement Improve Major d improvement Maintain ed Maintain ed Decrease d Increase d
0.32
0.46
0.14
43.73 Degraded
99.89
99.86
-0.03
-0.03
Maintain ed
99.68
99.54
-0.14
-0.14 Degraded
3.41
3.44
0.03
0.51
0.79
0.27
Increase d Increase 53.72 d Improve 0.83
Case Study (DT Analysis)
24
1/28/16
Confidential
© Nokia 2014
RACH Attempt Failure – DT Analysis 242H2LN1 RSRP CINR RACH Attempt Fail
Case 1
RACH Attempt fail at the areas due to poor RSRP and CINR. 25
1/28/16
Confidential
© Nokia 2014
Case 1
RACH Attempt Fail
Case 1 (#1) RSRP
PCI 224 is overshooting with poor RF & not able to HO to PCI 115
CINR
RACH Attempt Fail
RACH Attempt Fail
Case 1
Site 242H2LN1_S2 (PCI=224) is overshooting with poor RSRP & CINR causing RACH Attempt fail. 26 1/28/16 © Nokia 2014 Confidential
Case 1 (#2) CINR
PCI 224
RACH Attempt Fail
PCI 031
Case-1
27
1/28/16
Confidential
© Nokia 2014
PCI 115
Case 1 (#3) Poor Poor RSRP RSRP
RACH Attempt Fail due to poor radio condition. HO failure & RRC drop occurred (due to cell overshooting from 242H2LN1_S2 (PCI=242)
Handover Failure
RACH Attempt Fail
New RRC request after RRC drop
28
1/28/16
Confidential
© Nokia 2014
RRC Drop
RACH Failure Analysis – 242H2LN1 Completion RACH Stp SR degraded since 14.11.2015
29
1/28/16
Confidential
© Nokia 2014
Backup Slides
30
1/28/16
Confidential
© Nokia 2014
Overshooting cell 242H2LN1_112
31
1/28/16
Confidential
© Nokia 2014
Overshooting cell 23882LN1_113
32
1/28/16
Confidential
© Nokia 2014
Overshooting cell 242K3LN1_112
33
1/28/16
Confidential
© Nokia 2014
Overshooting cell 24218LN1_111
34
1/28/16
Confidential
© Nokia 2014
Overshooting - 24702LN1_112 RSRP PCI=64
35
1/28/16
Confidential
© Nokia 2014
CINR
Overshooting - 22016LN1_112 RSRP PCI=13
CINR
36
1/28/16
Confidential
© Nokia 2014
Overshooting - 236F8LN1_113 RSRP PCI=311
CINR
37
1/28/16
Confidential
© Nokia 2014
Overshooting cell 30314LN1_111
38
1/28/16
Confidential
© Nokia 2014
Overshooting cell 30209LN1_113
RACH attempt
39
1/28/16
Confidential
© Nokia 2014
RACH Fail
Overshooting cell 30087LN1_111
40
1/28/16
Confidential
© Nokia 2014
Overshooting cell 300K7LN1_112
41
1/28/16
Confidential
© Nokia 2014
Overshooting cell 31304LN1_112
RACH Fail
RACH Fail
42
1/28/16
Confidential
© Nokia 2014
Overshooting cell 31304LN1_112 RACH Fail
43
1/28/16
Confidential
© Nokia 2014
Counter_Explanation(Denominator) NetAct name: RACH_STP_ATT_SMALL_MSG Description: The number of RACH setup attempts for small size messages. Updated: The receipt of an RA preamble group A sent by the UE to eNB.
NetAct name: RACH_STP_ATT_LARGE_MSG Description: The number of RACH setup attempts for large size messages. Updated: The receipt of an RA preamble group B sent by the UE to eNB.
64 Preambles
GroupA Small size messages + large messages in poor radio conditions
GroupB
Large messages in good radio conditions
UE selects a preamble from one of the two groups based upon 1. The size of uplink packet to be sent 2. The radio conditions Small message size(in bits)
2013 NSN NWP RF - TWM Project 44
© Nokia Solutions Networks
NSN TWM Project
Large message size(in bits)>msg3(RRCConnectionrequest)
Counter_Explanation(Denominator) NetAct name: RACH_STP_ATT_SMALL_MSG Description: The number of RACH setup attempts for small size messages. Updated: The receipt of an RA preamble group A sent by the UE to eNB.
NetAct name: RACH_STP_ATT_LARGE_MSG Description: The number of RACH setup attempts for large size messages. Updated: The receipt of an RA preamble group B sent by the UE to eNB.
A maximum of 64 preamble sequences are available. These sequences can be divided into group A sequences and group B sequences UE selects a sequence from one of the two groups based upon 1. 2.
The size of uplink packet to be sent The radio conditions
Group A sequences are intended for small packets or large packets in poor radio conditions. Group B sequence are intended for large packets in good radio conditions Group A sequences are indexed from 0 to ‘size of preamble group A’ – 1 where the size of preamble group A parameter ranges from 4 to 60 and is broadcast in SIB2. Group B sequences are indexed from ‘size of preamble group A’ to ‘total number of preambles’ where the Total number of preambles parameter ranges from 4 to 64 and 2013 NSN NWP RF - TWM Project is ©broadcast in SIB2. 45 Nokia Solutions Networks NSN TWM Project
Counter_Explanation(Numerator) NetAct name: RRC_CON_RE_ESTAB_ATT Description: The number of attempted RRC Connection Re-establishment procedures. Updated: This counter is updated following the reception of an RRC: RRCConnectionReestablishmentRequest message from the UE
NetAct name: SIGN_CONN_ESTAB_ATT_MO_S Description: The number of Signaling Connection Establishment attempts for mobile originated signaling. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED has started. Updated: This counter is updated following the receipt of an RRC Connection Request message sent by the UE to eNB. Note: If a UE (erroneously) sends this message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.
NetAct name: SIGN_CONN_ESTAB_ATT_MT Description: The number of Signaling Connection Establishment attempts for mobile terminated connections. From UE's point of view, the transition from ECM-IDLE to ECMCONNECTED is started. Updated: This counter is updated following the receipt of an RRC Connection Request message sent by the UE to eNB. Note: If a UE (erroneously) sends this message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.
NetAct name: SIGN_CONN_ESTAB_ATT_MO_D Description: The number of Signaling Connection Establishment attempts for mobile originated data connections. From UE's point of view, the transition from ECM-IDLE to ECM2013 NSN NWP RF - TWM Project is started. 46 CONNECTED © Nokia Solutions Networks NSN TWM Project Updated: The receipt of an RRC Connection Request message sent by the UE to eNB. Note:
Counter_Explanation(Numerator) NetAct name: SIGN_CONN_ESTAB_ATT_OTHERS Description: The number of Signaling Connection Establishment attempts due to other reasons. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started. Updated: The receipt of an RRC Connection Request message sent by the UE to eNB.
NetAct name: SIGN_CONN_ESTAB_ATT_EMG Description: Number of Signalling Connection Establishment attempts for emergency callsUpdate Updated: Reception of the RRC: RRCConnectionRequest message (eNB <- UE) in case that this message contains the EstablishmentCause set to emergency (3GPP TS 36.331).
NetAct name: SIGN_CONN_ESTAB_ATT_HIPRIO Description: The number of Signaling Connection Establishment attempts for highPriorityAccess connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.. Updated: The reception of an RRCConnectionRequest message with highPriorityAccess EstablishmentCause sent by the UE to eNB.Note: If a UE (erroneously) sends this message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.
NetAct name: SIGN_CONN_ESTAB_ATT_DEL_TOL Description: The number of Signaling Connection Establishment attempts for delayTolerantAccess connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is startedUpdated: The reception of an RRCConnectionRequest message with delayTolerantAccess EstablishmentCause sent by the UE to eNB.Note: If a UE (erroneously) sends this message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted. 2013 NSN NWP RF - TWM Project 47
© Nokia Solutions Networks
NSN TWM Project
242L7LN1_113 KPIs
48
1/28/16
Confidential
© Nokia 2014
23895LN1_111 KPIs
49
1/28/16
Confidential
© Nokia 2014
237C5LN1_111 KPIs
50
1/28/16
Confidential
© Nokia 2014
242H2LN1_112 KPIs
51
1/28/16
Confidential
© Nokia 2014
23882LN1_113 KPIs
52
1/28/16
Confidential
© Nokia 2014
24702LN1_112 KPIs
53
1/28/16
Confidential
© Nokia 2014
236F8LN1_113 KPIs
54
1/28/16
Confidential
© Nokia 2014
242K3LN1_112 KPIs
55
1/28/16
Confidential
© Nokia 2014
22016LN1_112 KPIs
56
1/28/16
Confidential
© Nokia 2014
24218LN1_111 KPIs
57
1/28/16
Confidential
© Nokia 2014
RACH Setup SR - Network KPI RACH Setup Completion SR is at average of about 99.12%. However, Completion RACH Setup SR is lower and only at average of 76.58%.
58
1/28/16
Confidential
© Nokia 2014
Other Reference for RACH Failure Analysis & Troubleshooting Guides
59
1/28/16
Confidential
© Nokia 2014
RACH Failure Analysis – MSG1 to MSG2
60
1/28/16
Confidential
© Nokia 2014
RACH Failure Analysis – MSG2 to MSG3
61
1/28/16
Confidential
© Nokia 2014
Thank you
62
1/28/16
Confidential
© Nokia 2014
