03. RACH Setup Analysis & Case Study_Wk50v1

(1)

1/28/16

1 © Nokia 2014 Confidential

RACH Setup Analysis

&

(2)

1/28/16

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 (319 ) and RootSeqIndex(613)}

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 01 causing the cell radius increased.

(3)

1/28/16

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

(4)

1/28/16

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)

(5)

1/28/16

Complete RACH Setup SR Formula

KPI ID KPI Title Unit RL60 KPI Formula (with Counter Name)

LTE_105

6d

Complete RACH Setup Success

Rate

% 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

(6)

2013 NSN NWP RF - TWM Project

6 © Nokia Solutions Networks NSN TWM Project

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

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

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

New Taipei:

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

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

Taoyuan:



Data taken Since 1

st

_Nov(1

st

_Nov-2

nd

_Dec)

(7)

1/28/16

N2 – RACH Attempt KPI

Performance

RACH setup attempts are increasing with the traffic growth.

(8)

1/28/16

N2 – RACH Setup KPI

Performance

Hsinchu county is having lower Compl RACH stp SR among all

the cities.

Hsinchu county is having lower Compl RACH stp SR among all

the cities.

(9)

1/28/16

Complete RACH Setup SR

Top 10 Worst Cells(18 to 24 Nov):

LNB

TS_I

D

LNBT

S_NA

ME

LNCE

L_ID

Compl

RACH

stp

SR

RACH

_Atte

mpts

RACH

_Succ

ess

RACH

_Failu

res

Remarks

Actions

24210

9 242L7LN1 113 2.38 18880543 448495 18432048

Degraded between 17th_{to 28}th

Nov. Back to normal (70%) after 28 Nov. Hardware issue suspected, No major parameter/PCI change, No Action 23803 2 23895LN1 111 25.2 5504850 1387336 4117514

10/Nov: PCI retuned(375137) -KPI degraded because of mod-3

collision,

27/Nov: mod of PCI

changed(137135)-KPI improved to 55.5 (7 days avg), more

improvement expected.

220N4LN1(2.6 Km away) having same PCI as of 23895LN1, need to retune PCI for

220N4LN1. 23706

1 237C5LN1 111 2.31 3550031 82009 3468022 Suspect PCI confusion, Need to retune PCI CR Sent to TWM on 8 Dec

24212

4 242H2LN1 112 38.12 3810110 1452336 2357774

KPI suddenly degraded after 12 Nov, no major issue/changes

observed, no alarm found

Cell is overshooting at 4th_{tier. Down-tilt}

proposed Further analysis with cluster

owner 23804

5 23882LN1 113 60.55 5871155 3555257 2315898 Border cell, facing towards open area Down-Tilt suggestedOvershooting cell, 24700

3 24702LN1 112 63.53 5732220 3641924 2090296 Overshooting cell, 42 m height Down-Tilt suggested

23604

4 236F8LN1 113 65.09 5614980 3654926 1960054 Overshooting cell, 36 m height Down-Tilt suggested

24210

8 242K3LN1 112 61.35 4794851 2941829 1853022 Overshooting cell. 48 m height Down-Tilt suggested

22001

8 22016LN1 112 64.13 4891958 3137345 1754613 Overshooting cell, 42 m height Down-Tilt suggested

24213 0

24218L

(10)

1/28/16

Complete RACH Setup SR Top 10

Worst Cells(18 to 24 Nov): Traffic

Data

LNB

TS_I

D

LNBTS_NA

ME

LNCE

L_ID

Compl

RACH

stp SR

RACH_At

tempts

RACH_S

uccess

RACH_F

ailures(

Sum)

RLC SDU

DL-DTCH

Traffic Vol

in

MB(Sum)

RRC_CONN

_UE_MAX(

Avg)

24210 9 242L7LN1 113 2.38 18880543 448495 18432048 173716.95 41.28 23803 2 23895LN1 111 25.2 5504850 1387336 4117514 962842.16 127.42 23706 1 237C5LN1 111 2.31 3550031 82009 3468022 17207.04 12.14 24212 4 242H2LN1 112 38.12 3810110 1452336 2357774 897059.13 124.57 23804 5 23882LN1 113 60.55 5871155 3555257 2315898 1573798.77 307.42 24700 3 24702LN1 112 63.53 5732220 3641924 2090296 1631757.4 270 23604 4 236F8LN1 113 65.09 5614980 3654926 1960054 1644790.79 264.71 24210 8 242K3LN1 112 61.35 4794851 2941829 1853022 1572461.98 222.14 22001 8 22016LN1 112 64.13 4891958 3137345 1754613 1807902.87 234.71 24213 0 24218LN1 111 63.17 4753377 3002624 1750753 1499749.45 198.29



_{Cells highlighted in red are the high traffic cells in terms of RLC SDU}

(11)

1/28/16

Hsinchu Complete RACH Setup SR

Top 5 Worst Cells(18 to 24 Nov):



_{HSINCHU is having lower Complete RACH Setup SR among the all Cities.}

So Top 5 worst cells are filtered out & analyzed

LNB

TS_I

D

LNBTS_

NAME

LNCE

L_ID

Compl

RACH

stp SR

RACH

_Atte

mpts

RACH_

Succe

ss

RACH_

Failur

es

Remarks

Actions

31300

2 31304LN1 112 12.46 1109339 138271 971068 RACH Fail in poor coverage due to hilly terrain Proposed to change Parameters

30301

2 30314LN1 111 64.29 2337897 1502936 834961

Site having 54 M height, Cell facing towards open

area

Proposed to change Parameters

30003

0 30087LN1 111 64.91 2213812 1437026 776786 This cell is overshooting far away. Down-Tilt suggested

30200

5 30209LN1 113 60.37 1932079 1166320 765759

Overshooting cell, large number of attempts in poor

coverage Down-Tilt suggested

30004

4 300K7LN1 112 59.59 1826482 1088409 738073

This cell is overshooting far away & taking traffic in

(12)

1/28/16

AR/CR

index

LTE Objects-DN

phyCellId

MOD

MRBTS-237061/LNBTS-237061/LNCEL-111

207

MOD

MRBTS-237061/LNBTS-237061/LNCEL-112

209

Site Name Comments Action Site Action Cell

242H2LN

1 Down Tilt 242H2LN1 S2 (PCI= 224) from M-4 / E-12 to M-4 /

E-14

242H2LN

1

112 23882LN

1 Down Tilt 23882LN1 S3 (PCI= 404) from M-0 / 8 to M-2 /

E-8

23882LN

1

113 242K3LN

1 Down Tilt 242K3LN1 S2 (PCI= 315) from M-4 / E-15 to M-6 /

E-15

242K3LN

1

112 24218LN

1 Down Tilt 24218LN1 S1 (PCI= 435) from M-8 / E-12 to M-8 /

E-14

24218LN

1

111 30087LN

1 Down Tilt 30087LN1 S1 (PCI= 168) from M-9 / 6 to M-9 /

E-9

30087LN

1

111 30209LN

1 Down Tilt 30209LN1 S3 (PCI= 398) from M-10 / E-10 to M-10

/ E-12

30209LN

1

113 300K7LN

1 Down Tilt 300K7LN1 S2 (PCI= 82) from M-0 / E-3 to M-0 / E-5

300K7LN

1

112 24702LN

1 Down Tilt 24702LN1 S2 (PCI= 64) from M-10 / E-8 to M-10 /

E-10

24702LN

1

112 236F8LN

1 Down Tilt 236F8LN1 S3 (PCI= 311) from M-2 / 8 to M-4 /

E-8

236F8LN

1

113 22016LN

1 Down Tilt 22016LN1 S2 (PCI= 13) from M-6 / E-10 to M-10 /

E-10

22016LN

1

112 index

LTE Objects-DN

PrachCS

MOD

MRBTS-313002/LNBTS-313002/LNCEL-112

13

MOD

MRBTS-303012/LNBTS-303012/LNCEL-111

13 index

LTE Objects-DN

prachConfIndex

MOD

MRBTS-313002/LNBTS-313002/LNCEL-112

19

MOD

MRBTS-303012/LNBTS-303012/LNCEL-111

19 index

LTE Objects-DN

RootSeqIndex

MOD

MRBTS-313002/LNBTS-313002/LNCEL-112

13

MOD

MRBTS-303012/LNBTS-303012/LNCEL-111

13

(13)

1/28/16

Parameters Description

(PrachCS, PrachConfIndex &

RootSeqIndex )

(14)

1/28/16

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.

PRACH Frequency Offset: Indicate the location of preamble in the frequency domain. Scheduled by eNB.

(15)

1/28/16

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

(16)

1/28/16

3GPP 36.211: PRACH Configuration

Index

(17)

1/28/16

Preamble Format and Cell Range

The physical layer random access preamble, shown in figure below,

(18)

1/28/16

Root Sequence Index and Cell Range

The cell range i.e. the requirement for guard period defines the length of the cyclic

shift, N

_CS

, 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) / N

_CS

)

#root sequences needed (64 sequences for 64 preambles per cell) =

roundup(64 / #cyclic shifts per root sequence)

(19)

1/28/16

244B1LN1 Pre-Post

Comparison

(20)

1/28/16 20 © Nokia 2014 Confidential

244B1LN1 KPI Trend

Date:18 Nov PrachCS(1013) & prachConfindex(319) RootSeqIndex(613) Date:18 Nov PrachCS(1013) & prachConfindex(319) RootSeqIndex(613)

Befor

e

Befor

e

After

Befor

e

Befor

e

After

Befor

e

Befor

e

After

(21)

244B1LN1 KPI Trend

Befor

e

Befor

e

After

Befor

e

Befor

e

After

Date:18 Nov PrachCS(1013) & prachConfindex(319) RootSeqIndex(613) Date:18 Nov PrachCS(1013) & prachConfindex(319) RootSeqIndex(613)

(22)

1/28/16

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

Before After

Delta

%

Status

Remark

E-UTRAN Cell AvailR

244B1L

_N1

100.00 100.00

0.00

0.00 Maintain

_ed

Compl RACH stp SR

244B1L

N1

32.67

59.80 27.13 83.04

Improve

d

Major

improvement

RACH Stp Completion SR

244B1L

_N1

78.41

94.81 16.40 20.92

Improve

_d

_improvement

Major

RRC STP ATT

244B1L

N1

18744.8

2 19405.

93 661.11 3.53

Increase

d

RRC conn stp SR

244B1L

_N1

99.89

99.87 -0.02

0.02 Maintain

_ed

E-RAB SAtt

244B1L

N1

18530.8

2 19066.

27 535.44 2.89

Increase

d

DATA RB STP ATT

244B1L

_N1

30226.6

₅

30516.

₄₇

289.82 0.96

Increase

_d

RB DR

244B1L

N1

0.11

0.16

0.05

42.39 Degraded

E-UTRAN E-RAB stp SR

244B1L

_N1

99.96

99.94 -0.01

-0.01

Maintain

_ed

RB SR

244B1L

_N1

99.89

99.84 -0.05

-0.05

Maintain

_ed

E-UTRAN Avg PRB usage per

TTI DL

244B1L

N1

3.21

3.97

0.75

23.50 Increase

d

Avg PRB usage per TTI UL

244B1L

_N1

0.70

0.80

0.10

14.29 Increase

_d

Data RB stp SR

244B1L

_N1

97.82

99.15

1.33

1.36 Improve

_d

inter eNB E-UTRAN HO SR X2

244B1L

_N1

98.92

97.81 -1.11

-1.12

Degraded

RRC_CONN_UE_MAX

244B1L

N1

22.18

23.33

1.16

5.22 Increase

d

Avg RLC Layer cell thp,

DL(kbps)

244B1L

N1

836.70 949.36 112.66 13.46

Improve

d

Avg RLC Cell Thp UL(kbps)

244B1L

N1

56.12

57.04

0.92

1.65 Improve

d

E-UTRAN RLC PDU Vol UL(MB)

244B1L

_N1

606.03 615.20

9.17

1.51 Increase

_d

RLC PDU Vol DL(MB)

244B1L

N1

9036.31

10241.

60 1205.29 13.34

Increase

d

Intra eNB HO SR

244B1L

_N1

89.57

89.66

0.08

0.09 Improve

_d

RACH stp att

244B1L

_N1

107602.

₅₃

64646.

₈₇

-42955.6

6 -39.92

Decrease

d

(23)

1/28/16

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

Before After

Delta

%

Status

Remark

E-UTRAN Cell AvailR

244B1L

_N1

100.00 100.00

0.00

0.00 Maintain

_ed

Compl RACH stp SR

244B1L

N1

12.54

61.10

48.56

387.3

6 Improve

d

Major

improvement

RACH Stp Completion SR

244B1L

_N1

91.13

98.82

7.68

8.43 Improve

_d

_improvement

Major

RRC STP ATT

244B1L

N1

6771.06

6724.0

0 -47.06 -0.69

Maintain

ed

RRC conn stp SR

244B1L

_N1

99.48

99.36 -0.12

0.12 Maintain

_ed

E-RAB SAtt

244B1L

N1

6435.29

6240.7

3 -194.56 -3.02

Decrease

d

DATA RB STP ATT

244B1L

_N1

11792.4

₁

11864.

₄₇

72.05

0.61 Increase

_d

RB DR

244B1L

N1

0.32

0.46

0.14

43.73 Degraded

E-UTRAN E-RAB stp SR

244B1L

_N1

99.89

99.86 -0.03

-0.03

Maintain

_ed

RB SR

244B1L

_N1

99.68

99.54 -0.14

-0.14

Degraded

E-UTRAN Avg PRB usage per

TTI DL

244B1L

N1

3.41

3.44

0.03

0.83 Increase

d

Avg PRB usage per TTI UL

244B1L

_N1

0.51

0.79

0.27

53.72 Increase

_d

Data RB stp SR

244B1L

_N1

98.40

99.57

1.18

1.20 Improve

_d

inter eNB E-UTRAN HO SR X2

244B1L

_N1

98.06

96.85 -1.22

-1.24

Degraded

RRC_CONN_UE_MAX

244B1L

N1

11.12

11.73

0.62

5.54 Increase

d

Avg RLC Layer cell thp,

DL(kbps)

244B1L

N1

427.01 453.57

26.57

6.22 Improve

d

Avg RLC Cell Thp UL(kbps)

244B1L

N1

20.60

28.05

7.45

36.19 Improve

d

E-UTRAN RLC PDU Vol UL(MB)

244B1L

_N1

222.45 302.68

80.23 36.07

Increase

_d

RLC PDU Vol DL(MB)

244B1L

N1

4611.67

4893.3

4 281.68 6.11

Increase

d

Intra eNB HO SR

244B1L

_N1

94.32

95.09

0.77

0.81 Improve

_d

RACH stp att

244B1L

_N1

81331.7

₆

25321.

₈₇

-56009.9

0 -68.87

Decrease

d

(24)

1/28/16

Case Study

(25)

1/28/16

RSRP

RSRP CINRCINR

RACH Attempt fail at the areas due to poor RSRP and CINR.

RACH Attempt Failure – DT Analysis

242H2LN1

RACH Attempt Fail

Case 1

RACH Attempt Fail

(26)

1/28/16

RSRP

RSRP CINRCINR

Site 242H2LN1_S2 (PCI=224) is overshooting with poor RSRP & CINR causing

RACH Attempt fail.

Case 1 (#1)

RACH Attempt Fail

Case 1

PCI 224 is overshooting with poor RF & not able to HO

to PCI 115 PCI 224 is overshooting with poor RF & not able to HO

to PCI 115

(27)

Case 1 (#2)

(28)

1/28/16

Case 1 (#3)

New RRC request after RRC drop New RRC request after RRC drop

Handover Failure Handover Failure

RRC Drop RRC Drop RACH Attempt Fail

RACH Attempt Fail

P o o r R S R P P o o r R S R

P RACH Attempt Fail due to _{poor radio condition. HO}

failure & RRC drop occurred (due to cell

overshooting from 242H2LN1_S2 (PCI=242) RACH Attempt Fail due to

poor radio condition. HO failure & RRC drop occurred (due to cell

overshooting from 242H2LN1_S2 (PCI=242)

(29)

1/28/16

RACH Failure Analysis – 242H2LN1

Completion RACH Stp SR degraded since 14.11.2015 Completion RACH Stp SR degraded since 14.11.2015

(30)

1/28/16

(31)

1/28/16

Overshooting cell

242H2LN1_112

(32)

1/28/16

Overshooting cell

23882LN1_113

(33)

1/28/16

Overshooting cell

242K3LN1_112

(34)

1/28/16

Overshooting cell

24218LN1_111

(35)

Overshooting - 24702LN1_112

RSRP PCI=64 CINR

(36)

Overshooting - 22016LN1_112

RSRP PCI=13 CINR

(37)

Overshooting - 236F8LN1_113

RSRP PCI=311 CINR

(38)

1/28/16

Overshooting cell

30314LN1_111

(39)

Overshooting cell

30209LN1_113

RACH attempt

RACH Fail

(40)

1/28/16

Overshooting cell

30087LN1_111

(41)

1/28/16

Overshooting cell

300K7LN1_112

(42)

Overshooting cell

31304LN1_112

RACH Fail

(43)

Overshooting cell

31304LN1_112

RACH Fail

(44)

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

_GroupB

GroupB

Small size

messages + large

messages in poor

radio conditions

Small size

messages + large

messages in poor

radio conditions

Large messages

in good radio

conditions

Large messages

in good radio

conditions

Small message size(in

bits)<msg3(RRCConnectionrequest)

Small message size(in

bits)<msg3(RRCConnectionrequest)

_{bits)>msg3(RRCConnectionrequest)}

Large message size(in

bits)>msg3(RRCConnectionrequest)

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

(45)

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. The size of uplink packet to be sent

2. 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

is broadcast in SIB2.

(46)

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 IDLE to ECM-CONNECTED 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 IDLE to ECM-CONNECTED is started.

Updated: 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

(47)

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.

(48)

1/28/16

(49)

1/28/16

(50)

1/28/16

(51)

1/28/16

(52)

1/28/16

(53)

1/28/16

(54)

1/28/16

(55)

1/28/16

(56)

1/28/16

(57)

1/28/16

(58)

1/28/16

RACH Setup SR - Network KPI

RACH Setup Completion SR is at average of about 99.12%.

(59)

1/28/16

Other Reference for RACH

Failure Analysis &

(60)

1/28/16

(61)

1/28/16

(62)

1/28/16