Call Setup Optimization

RA47044EN40GLA0 1
Call Setup Optimization

RA47044EN40GLA0 3
Call Setup Optimization

RA47044EN40GLA0 4
Call Setup Optimization

This module is for connection setup. Call drops after setup phase are discussed in
another module.

RA47044EN40GLA0 5
Call Setup Optimization

RA47044EN40GLA0 6
Call Setup Optimization

RA47044EN40GLA0 7
Call Setup Optimization

RA47044EN40GLA0 8
Call Setup Optimization

RA47044EN40GLA0 9
Call Setup Optimization

RA47044EN40GLA0 10
Call Setup Optimization

RA47044EN40GLA0 11
Call Setup Optimization

RA47044EN40GLA0 12
Call Setup Optimization

RA47044EN40GLA0 13
Call Setup Optimization

In case of TAU only steps 1-2.

RA47044EN40GLA0 14
Call Setup Optimization

RA47044EN40GLA0 15
Call Setup Optimization

RA47044EN40GLA0 16
Call Setup Optimization

RA47044EN40GLA0 17
Call Setup Optimization

RA47044EN40GLA0 18
Call Setup Optimization

RA47044EN40GLA0 19
Call Setup Optimization

RA47044EN40GLA0 20
Call Setup Optimization

RA47044EN40GLA0 21
Call Setup Optimization

RA47044EN40GLA0 22
Call Setup Optimization

1. How does NSN handle repeated RRC signaling connection attempts? Counted only
once or stepped for each repetition? ([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])
----
If UEC receives repeated MAC_CCCH_DATA_RECEIVE_IND_MSG ->
RRC_CONNECTION_REQUEST with same crnti it is silently discarded and not counted.
If UEC receives repeated MAC_CCCH_DATA_RECEIVE_IND_MSG ->
RRC_CONNECTION_REQUEST with new crnti it is handled and counted. (the old
context will be deleted after timeout)

RA47044EN40GLA0 23
Call Setup Optimization

RA47044EN40GLA0 24
Call Setup Optimization

RA47044EN40GLA0 25
Call Setup Optimization

RA47044EN40GLA0 26
Call Setup Optimization

RA47044EN40GLA0 27
Call Setup Optimization

RA47044EN40GLA0 28
Call Setup Optimization

RA47044EN40GLA0 29
Call Setup Optimization

RA47044EN40GLA0 30
Call Setup Optimization

RA47044EN40GLA0 31
Call Setup Optimization

RA47044EN40GLA0 32
Call Setup Optimization

RA47044EN40GLA0 33
Call Setup Optimization

RA47044EN40GLA0 34
Call Setup Optimization

RA47044EN40GLA0 35
Call Setup Optimization

RA47044EN40GLA0 36
Call Setup Optimization

RA47044EN40GLA0 37
Call Setup Optimization

* Additional tuning parameter

LNCEL: raRespWinSize
Description: Random Access Response Window Size parameter defines the window
size for the random access response in TTIs.
Range And Step: 2 (0), 3 (1), 4 (2), 5 (3), 6 (4), 7 (5), 8 (6), 10 (7) Default Value: 10 (7)

RA47044EN40GLA0 38
Call Setup Optimization

RA47044EN40GLA0 39
Call Setup Optimization

RA47044EN40GLA0 40
Call Setup Optimization

RA47044EN40GLA0 41
Call Setup Optimization

RA47044EN40GLA0 42
Call Setup Optimization

RA47044EN40GLA0 43
Call Setup Optimization

3GPP TS 36.321 V8.8.0 (2009-12)

Msg3: Message transmitted on UL-SCH containing a C-RNTI MAC CE or CCCH SDU,

submitted from upper layer and associated with the UE Contention Resolution Identity, as
part of a random access procedure. Comment: Excludes contention-based random
access.

Comment:
C-RNTI MAC CE is contained in
- Random Access Scheduling Request
- PDCCH Order
- RRC Reconfig Complete in target cell in HO

CCCH SDU is contained in:

- RRC Connection Setup
- RRC Connection Re-Establishment
- RRC Reconfig Complete

The UE is configured with a Maximum number of HARQ transmissions and a Maximum

number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx
respectively. For transmissions on all HARQ processes and all logical channels except
for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of
transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the
Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Msg3Tx.

RA47044EN40GLA0 44
Call Setup Optimization

RA47044EN40GLA0 45
Call Setup Optimization

RA47044EN40GLA0 46
Call Setup Optimization

RA47044EN40GLA0 47
Call Setup Optimization

RA47044EN40GLA0 48
Call Setup Optimization

RA47044EN40GLA0 49
Call Setup Optimization

RA47044EN40GLA0 50
Call Setup Optimization

RA47044EN40GLA0 51
Call Setup Optimization

RA47044EN40GLA0 52
Call Setup Optimization

RA47044EN40GLA0 53
Call Setup Optimization

RA47044EN40GLA0 54
Call Setup Optimization

RA47044EN40GLA0 55
Call Setup Optimization

RA47044EN40GLA0 56
Call Setup Optimization

RA47044EN40GLA0 57
Call Setup Optimization

RA47044EN40GLA0 58
Call Setup Optimization

RA47044EN40GLA0 59
Call Setup Optimization

RA47044EN40GLA0 60
Call Setup Optimization

RA47044EN40GLA0 61
Call Setup Optimization

RA47044EN40GLA0 62
Call Setup Optimization

RA47044EN40GLA0 63
Call Setup Optimization

RA47044EN40GLA0 64
Call Setup Optimization

RA47044EN40GLA0 65
Call Setup Optimization

RA47044EN40GLA0 66
Call Setup Optimization

RA47044EN40GLA0 67
Call Setup Optimization

RA47044EN40GLA0 68
Call Setup Optimization

RA47044EN40GLA0 69
Call Setup Optimization

RA47044EN40GLA0 70
Call Setup Optimization

RA47044EN40GLA0 71
Call Setup Optimization

RA47044EN40GLA0 72
Call Setup Optimization

RA47044EN40GLA0 73
Call Setup Optimization

RA47044EN40GLA0 74
Call Setup Optimization

RA47044EN40GLA0 75
Call Setup Optimization

RA47044EN40GLA0 76
Call Setup Optimization

RA47044EN40GLA0 77
Call Setup Optimization

RA47044EN40GLA0 78
Call Setup Optimization

RA47044EN40GLA0 79
Call Setup Optimization

RA47044EN40GLA0 80
Call Setup Optimization

RA47044EN40GLA0 81
Call Setup Optimization

Note: It was noticed that 30 out of 315 LNCELs from LTE Phase 1 sites also had Step 1
implemented.

RA47044EN40GLA0 82
Call Setup Optimization

RA47044EN40GLA0 83
Call Setup Optimization

RA47044EN40GLA0 84
Call Setup Optimization

RA47044EN40GLA0 85
Call Setup Optimization

RA47044EN40GLA0 86
Call Setup Optimization

RA47044EN40GLA0 87
Call Setup Optimization

RA47044EN40GLA0 88
Call Setup Optimization

RA47044EN40GLA0 89
Call Setup Optimization

RA47044EN40GLA0 90
Call Setup Optimization

RA47044EN40GLA0 91