NETWORK

5G18A: Cell access aspects part 2 ENGINEERING

Synchronization Signals
System Information Broadcast
Random Access
Network Engineering Information
• Doc ID: 5ace1352de26750012b7630c
• Version: 1.1
• Authors: Wojciech Wascinski/Rafal Kosek
• Status: Approved
• 14-05-2018

Please, always check the latest version of NEI slides.

1 © Nokia 2018
Disclaimer

• Please note that the NEI materials are for internal use only. If they shall be used as a source for the customer
presentation, it is mandatory to align the contents with the Product Management and/or local sales teams at
first!

• 5G18A content provided in these slides is for information only and does not imply committed status
(5G18A C3 milestone is planned on 09/18).
Any customer communication should be aligned with Product Management.

• The 3GPP Release 15 is only partially completed as of beginning of 2018. The full and complete
specification is expected to be released 07/2018. Therefore certain solutions presented in this slide
deck might be modified by 3GPP

2 © Nokia 2018 Nokia Internal Use

Revision history and metadata
Please, note that NEI is a controlled document and it is obligatory to fill in and maintain
its Revision History
Document ID: 5ace1352de26750012b7630c
Document location: https://webnei.emea.nsn-net.net/#/webnei/5ace1352de26750012b7630c/1
Organization: Network Engineering

Version Description of Changes Date Doc Owner Doc Status Reviewed Approver Approval Date
by
V0.1 First version of the material 10-04-2018 Wojciech Wascinski, Draft
Rafal Kosek

V0.2 Version with first review commets included 12-04-2018 Wojciech Wascinski, Rafal Draft 5G forum
Kosek audience

V1.0 Approved version 17-04-2018 Wojciech Wascinski, Rafal Approved

Kosek

V1.1 Cell ranges for short preamble formats added 14-05-2018 Wojciech Wascinski, Rafal Approved
Kosek

3 © Nokia 2018 Nokia Internal Use

Agenda

1
Introduction
2
Technical
Details
3
Configuration
Management

4 © Nokia 2018 Nokia Internal Use

 NOTE: In 5G18A release, option 3.X of Non-Standalone Architecture (dual
connectivity LTE/5G) is supported
Support for Standalone (SA) architecture, where each eNB or gNB has both control plane and
user plane direct connections to the CN is planned for further releases

5 © Nokia 2018 Nokia Internal Use

Introduction
Related features

Information enclosed in this material come from several 5G18A features

5GC000425 - TDD lower layer support - 100 MHz

5G18A Cell
cell bandwidth

5GC000509 - L3 Non Standalone call with data

access
transmission

5G000521 Master Information Block

aspects
part 2
5GC000511 PRACH Control

6 © Nokia 2018 Nokia Internal Use

Introduction
Overall procedure of cell access

• Downlink Synchronization is the very first step when UE wants to camp on any cell
OBTAIN
• UE acquires physical cell id, time slot and frame synchronization, which will enable UE to
DOWNLINK read System Information Blocks
SYNCHRONIZAT
ION
• System Information provides information to the UEs about various parameters that are
common for all the UEs in the same cell
DECODE
• UEs use this information for mutliple purposes, mainly system access and idle mode
SYSTEM mobility procedures
INFORMATION

• When the UE has obtained System Information, it has to request an RRCConnection

PERFORM • Like it has no dedicated resources, the UE requests the connection using the Random Access
RANDOM ACCESS Procedure via common uplink resources

7 © Nokia 2018 Nokia Internal Use

Introduction
LTE interworking - Overall Signaling Procedure
UE LTE 5G gNB
• Master Node: LTE eNB sends SgNB Addition Request to Secondary Node: 5G eNB
SgNB Addition Request
gNB
• LTE eNB forward information to 5G gNB (E-RAB characteristics, UE SgNB Addition Request Ack

capabilities, security information…) RRC Connection Reconfiguration

• If gNB decided to accept the request, it sends SgNB Addition Request Ack RRC Connection Reconfiguration
• If 5G gNB accept the SN addition request and provides all the necessary Complete

information to LTE eNB SgNB Reconfiguration Complete

• LTE eNB generates RRC Connection Reconfiguation message carrying all the
necessary information and send it to UE Cell Detection (PSS and SSS)

‒ This message carries RRC Connection Cofiguration so UE can figure out

System Information decoding
the necessary configuration information for gNB
• After UE received RRCConnectionReconfiguration, it checks if all the Random Access Procedure
configurations in the message is doable in UE side and sends
RRCConnectionReconfigurationComplete message
• Once LTE eNB received RRCConnectionReconfigurationComplete from UE,
Based on the RRC Connection
the eNB informs gNB that UE has completed the reconfiguration procedure Reconfiguration message, UE detects PSS,
SSS and PBCH of NR gNB.
Once it successfully detects PSS, SSS, PBCH
of NR gNB, it performs RACH procedure to
LTE-5G interworking will be covered in dedicated material:
5G Non-Standalone Architecture option 3X PSCell of the gNB
8 © Nokia 2018 Nokia Internal Use
Agenda

1
Introduction
2
Technical
Details
3
Configuration
Management

9 © Nokia 2018 Nokia Internal Use

 Synchronization Signals
System Information Broadcast

10 © Nokia 2018 Nokia Internal Use

Introduction
Synchronization Signals

• For the case of cell access, it is very important that the UE has to perform time and frequency
synchronization procedures
• To perform above operations, Synchronization Signals are periodically transmitted by 5G gNB

• In 5G18A there are two types of Synchronization Signals:

• Primary Synchronization Signal (PSS)
• Secondary Synchronization Signal (SSS)
• After PSS and SSS detection UE determines the Physical Cell ID and it is synchronized in time and
frequency domain with the corresponding cell
• Now the UE is ready to receive downlink broadcast data…

11 © Nokia 2018 Nokia Internal Use

Introduction
System Information Broadcast
• System Information provides information to the UEs about various parameters of both the Access Stratum and Non Access
Stratum

• These are parameters that are common for all the UEs in the same cell

• UEs read the System Information during the initial attach process and whenever it is camped to a new cell

• According to 3GPP 5G System Information is classified into 3 groups:

‒ Minimum System Information (Min SI - MIB)
‒ Remaining Minimum System Information (RMSI - SIB1) MIB
‒ Other SI (SIB2 onwards)
SIBs

In 5G18A, only the transmission of the

Master Information Block (MIB) via the
PBCH (Physical Broadcast Channel) is
supported
12 © Nokia 2018 Nokia Internal Use
Technical Details
Physical Cell Identity
Physical Cell Identity (PCI) identifies the given 5G Cell

• There are 1008 (0…1007) unique Physical Cell ID’s available in the system

• The physical-layer cell identities are grouped into 336 (0…335) unique physical-layer cell-identity groups, each group
containing 3 (0…2) unique identities thus the unique Physical Cell ID for each cell is defined by:

+
where:
• (0…1007) Physical Cell ID (NRCELL:physCellId)
• (0…335) defines the Secondary Synchronization Signal (SSS)
• (0,1,2) defines the Primary Synchronization Signal (PSS)

• Synchronization Signals are used for:

‒ frequency synchronization
‒ frame synchronization
‒ cell ID detection

13 © Nokia 2018 Nokia Internal Use

Technical Details Draft – to be updated

Master Information Block content

• In 5G18A, only the transmission of the Master Information Block (MIB) via Physical Broadcast Channel (PBCH) is
supported
• A change of the MIB leads to a reset of the cell
• The MIB includes the most essential information for the initial UE access
• The following information is contained in the MIB:
IE/Group Name Presence Range Description
systemFrameNumber M BIT STRING (SIZE(10)) The 6 most significant bit (MSB) of the 10 bit System Frame Number
subCarrierSpacingCommon M INTEGER (0,1) Subcarrier spacing for SIB1, Msg.2/4 for initial access and broadcast SI-messages. Not supported in 5G18A
ssb-subcarrierOffset M INTEGER (0…11) The frequency domain offset between SSB and the overall resource block grid in number of subcarriers.
Not supported in 5G18A
dmrs-TypeA-Position M ENUMERATED {pos2, pos3} Position of (first) DL DM-RS. Not supported in 5G18A
pdcchConfigSIB1 M INTEGER (0…7) Determines a bandwidth for PDCCH/SIB. Not supported in 5G18A
halfFrameIndicator M INTEGER (0,1) Indicates  whether the SS block is in the first or second 5 ms of a radio frame
cellBarred M ENUMERATED {barred, notBarred) The cell barred flag indicates if the cell status is barred or not. A barred cell is a cell that a UE is not allowed to camp on, not
even for emergency calls. Configured using NRCELL:cellBarred
intraFreqReselection M ENUMERATED {allowed, Determines whether or not intra frequency cell reselection is allowed . Configured using
notAllowed) NRCELL:intraFreqReselection
ssb-IndexExplicit O INTEGER (1…7) Identifies the time domain location of SSB in the SS-Burst-Set. The field is only present for carrier frequencies > 6 GHz.
spare M BIT STRING (SIZE(7))

14 © Nokia 2018 Nokia Internal Use

Technical Details
Synchronization Signal Block

• 5G broadcast transmission is organized in Synchronization Signal Blocks (SS Blocks)

• The length of SS block is 4 OFDM symbols:

‒ 1 OFDM symbol of Primary Synchronization Signal
‒ 1 OFDM symbol of Secondary Synchronization Signal
‒ and 3 OFDM symbols of PBCH

• PSS, SSS and PBCH are time and frequency domain multiplexed on four consecutive OFDM symbols

SSS
PBC PBC
PSS PBC
H H
H block
4-Symbol SS/PBCH

15 © Nokia 2018 Nokia Internal Use

Technical Details
Synchronization Signal Block Burst

• Synchronization Signal Block Burst (SS Block Burst) is a set of consecutive SS blocks
• In 5G18A, there are:
‒ up to 2 blocks in a SS block burst below 6 GHz
‒ and up to 4 SS blocks in a SS block burst above 6 GHz

sub 6 GHz above 6 GHz

SS burst SS burst

SS SS time SS SS SS SS time
block block block block block block
0 1 0 1 2 3

16 © Nokia 2018 Nokia Internal Use

Technical Details
Synchronization Signal Block Burst Set
• SS Block Burst Set comprises of multiple SS Block Bursts, and maximum number of SS Blocks L within the SS Block Burst
Set is according to frequency band:
‒ For frequency range up to 3 GHz, is 4 (not supported in 5G18A)
‒ For frequency range from 3 GHz to 6 GHz, is 8
‒ For frequency range from 6 GHz to 52.6 GHz, is 64
• SS Block Burst Set Periodicity - SS block burst set is repeated periodically:
• Periodicity can be configured using parameter NRCELLGRP:ssBurstSetPeriod (10ms or 20ms)
• For initial access UE assumes periodicity of 20 ms in both-sub 6GHz, and above 6 GHz

SS burst set 0 SS burst set 1

SS SS SS SS SS SS SS SS SS SS time
block block block block … block … block block block block … block
0 1 2 3 L 0 1 2 3 L
. . .
SS burst periodicity

17 © Nokia 2018 Nokia Internal Use

 Technical Details
SS Block Burst Set: multi-beam sweeping
• Within an SS/PBCH burst set, beams are mapped in consecutive SS/PBCH blocks in increasing order of beam index
• The beam indexes are numbered from 0 to L-1 where L represents the maximum number of beams where SS/PBCH blocks are broadcasted within
a SS/PBCH burst set
• The beam indexing initialization is such that the beam 0 is transmitted in the first SS/PBCH block of the first radio frame carrying SS/PBCH block

SS Burst Set 1 The number of SS Blocks in SS Burst Set

SS Burst Set 0
equals the number of beams. Parameter
SS SS SS SS SS SS SS SS SS SS NRCELLGRP:numberOfTransmittedSsBlo
… block block block block … block … block block block block … block … cks defines the number of transmitted SS
0 1 2 3 L 0 1 2 3 L ValueBlocks
Name
1 1 beam
Multi-beam
sweeping
… …
2
4
2 beams
4 beams
6 6 beams
beam #0 beam #1 beam #2 beam #3 beam #L-1 beam #0 beam #1 beam #2 beam #3 beam #L-1 8 8 beams
9 9 beams
12 12 beams
The main purpose of SS Burst sets is to support DL beam 15 15 beams
18 18 beams
sweeping, in which DL Tx beams are sequentially 21 21 beams
transmitted in order to cover the whole service area in one 24
32
24 beams
32 beams
SS Burst Set
18 © Nokia 2018
Technical Details
5G18A broadcast transmission - summary

PSS SSS PBCH

PSS, SSS and PBCH

(carrying MIB) are time SS Burst SS Burst Set
and frequency multiplexed
Below SSS
6GHz 2x PSS
PBC
H PBC
PBC
H
3 to
6GHz 8x PSS
PBC
SSS
PBC
H PBC H
H
H
Above SSS
4x PSS
PBC PBC Above
64 x* PBC
SSS
PBC
SS Block 6GHz H PBC
H
H 6GHz PSS
H PBC H
H
SSS SS Blocks form SS Burst that is a set
PBC PBC SS Bursts compose SS Burst set used for
PSS of consecutive SS blocks
H PBC H multi beam sweeping
H
That set compose SS Block *Up to 32 according to
in four consecutive OFDM NRCELLGRP:numberOfTransmittedSsBlocks
symbols parameter range

19 © Nokia 2018 Nokia Internal Use

 239

Technical Details
238
237
236
234

Frequency structure of SS Block 233

193
…
192
191
190
189
3GPP 38.211- Table 7.4.3.1-1: Resources within an SS/PBCH block for PSS, SSS, PBCH, and DM-RS for PBCH 188
187
186
239
Channel or OFDM symbol number l relative to the Subcarrier number k relative to the start 185 P
B
signal start of an SS block of an SS block 184
C
183
182 192 H
PSS 0 56, 57, …, 182 181
180 182
SSS 2 56, 57, …, 182 179
178 P P
177 P S
0 0, 1, …, 55, 183, 184, …, 236 176 Subcarrier B B
Set to 0 175 S S
number C C
2 48, 49, …, 55, 183, 184, …, 191 174

63
… S
H
S
H
1, 3 0, 1, …, 239 62
56
61
PBCH 0, 1, …, 47 60
2 59 47 P
192, 193, …, 239 58 B
C
57

frequency
H
1, 3 0+v, 4+v, 8+v, …, 236+v *
56
55 0
DMRS for 54
0 1 2 3
0+v, 4+v, 8+v, …, 44+v
*
53
PBCH 2 52
192+v, 196+v, …, 236+v 51
50 OFDM symbol
* v depends on Physical Cell Identity 49
48 number
47
46
45
44
…

frequency
5
time
4
3 Offset of PRB 0 of the SS block to PRB 0 of
2
1
common resource block:
0 • Below 6 GHz (SCS=30kHz): 118
time • Above 6 GHz (SCS=240kHz): 12

20 © Nokia 2018 Nokia Internal Use

Technical Details
Time structure of SS Block

3GPP 38.213 - 4.1 Cell Search

SSB Subcarrier
OFDM symbol f <= 3 GHz 3 GHz < f <= 6 GHz 6 GHz < f
Spacing
15 kHz {2,8} + 14n n = 0,1 n = 0,1,2,3

30 kHz (4,8,16,20} + 28n n = 0,1 n = 0,1

60 kHz {2,8} + 14n n = 0,1 n = 0,1,2,3

120 kHz {4,8,16,20} + 28n n = 0,1,2,3,5,6,7,8,

10,11,12,13,15,16,17,18
240 kHz {8,12,16,20,32,36,40,44} + 56n n = 0,1,2,3,5,6,7,8

Not supported in 5G18A

In 5G18A release:
• Bandwidth 100MHz and frequency below 6GHz => SSB subcarrier spacing = 30kHz
• Bandwidth 100MHz and frequency above 6GHz => SSB subcarrier spacing 240kHz

21 © Nokia 2018 Nokia Internal Use

Technical Details
Time structure of SS Block below 6GHz (SCS 30kHz)
3GPP 38.213 - 4.1 Cell Search
SSB Subcarrier
OFDM symbol f <= 3 GHz 3 GHz < f <= 6 GHz 6 GHz < f
Spacing
Based on 38.211 (Table 7.4.3.1-1) using the
15 kHz {2,8} + 14n n = 0,1 n = 0,1,2,3
following formula {4,8,16,20} +28n where n =
30 kHz (4,8,16,20} + 28n n = 0,1 n = 0,1
0,1 starting OFDM symbols for SS blocks are:
60 kHz {2,8} + 14n n = 0,1 n = 0,1,2,3
4, 8, 16, 20, 32, 36, 44, 48
120 kHz {4,8,16,20} + 28n n = 0,1,2,3,5,6,7,8,
10,11,12,13,15,16,17,18

240 kHz {8,12,16,20,32,36,40,44} + 56n n = 0,1,2,3,5,6,7,8

Not supported in 5G18A

half frame = 5ms

SCS=30kHz
slot

SS Burst
SS
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 48 50 51 52 53 54 55 279
Block
…
slot #0 slot #1 slot #2 slot #3 slot #20
slot
radio frame

Slot/symbol containing SS Blocks

22 © Nokia 2018 Nokia Internal Use
Technical Details
Time structure of SS Block below 6GHz (SCS 30kHz)
SS block pattern below 6GHz (SSB SCS 30kHz) differs for odd and even SS burst

Even SS burst/slot Odd SS burst/slot

Nband-slot(Nss-slot) #2j Nband-slot(Nss-slot) #2j+1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13

P P P P
P B S P B S P B S P B S
127 127
S C S S C S tones
20 PRB S C S S C S tones
20 PRB
S HS S H S S HS S HS

118 PRB 118 PRB

SS/PBCH SS/PBCH SS/PBCH SS/PBCH

block 0 block 1 block 0 block 1
23 © Nokia 2018 Nokia Internal Use
Technical Details Nband-slot #2j+1
Nss-slot #4j+3
Nss-slot #4j+2
Time structure of SS Block 0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13

above 6GHz (SCS 240kHz)

P P P P P P P P
Odd SS/PBCH P B S B P B S B P B S B P B S B 127
burst S C S C S C S C S C S C S C S C 20 PRB
tones
S H S H S H S H S H S H S H S H

6 PRB

SS block pattern above 6GHz (SSB SS/PBCH

block 0
SS/PBCH
block 1
SS/PBCH
block 2
SS/PBCH
block 3
SCS 240kHz) differs for odd and even
SS burst Nband-slot #2j
Nss-slot #4j Nss-slot #4j+1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13

P P P P P P P P
Even SS/PBCH P B S B P B S B P B S B P B S B 127
burst S C S C S C S C S C S C S C S C 20 PRB
tones
S H S H S H S H S H S H S H S H

6 PRB
SS/PBCH SS/PBCH SS/PBCH SS/PBCH
block 0 block 1 block 2 block 3

24 © Nokia 2018 Nokia Internal Use

 Random Access

25 © Nokia 2018 Nokia Internal Use

Overview
Why and when random access is used ?

• The main purpose of RACH procedure is to:

- Obtain the resources for Msg3
- Assign a unique identifier to communicate with the UE Random Access
over the air interface (C-RNTI) types
- Initial L1 synchronization (Timing and power)

Su feat 572
sub C00
pp ur -I
5G
• Random access procedure is needed in the following

ort e
ed
0

wi
cases:

th
- Initial access Contention Based Non-Contention
Non-Contention Based
Based
•gNB5GNB selects preamble
- Loss of UL synchronization UE selects preamble selects preamble

- Handover

The following material focuses on Contention Based Random Access procedure during initial
access (as non-Contention Based is still under specification/implementation)

26 © Nokia 2018 Nokia Internal Use

Overview
Higlevel view
DL SS burst
Physical Random Access Channel design needs to
take into account the beamforming principle. There Specified
is no continuous DL coverage with control amount of
channels, and equivalently, there is no always-on time
listening space for the common channels in the
uplink Uplink RA
message

The gNB periodically activates a receive beam

covering a specific zone of the cell coverage, to
receive Random Access messages from the UEs
that are present in that specific zone

The uplink RX beam activation is periodic and is The UE infers from the reception time of the
linked to the downlink SS burst periodicity downlink SS beam the exact time slot where the
RA message shall be sent (if needed)

27 © Nokia 2018 Nokia Internal Use

 Once non-Contention based RA is available (5GC000572-I),
Overview dedicated preamble is provided to UE during SgNB addition to avoid
Before Random Access may happen collisions

• Once it is decided that UE will utilze 5G resources, MeNB (Master eNB)

LTE 5G sends RRC Connection Reconfiguration to the UE (after successful SgNB
UE (MeNB) (SgNB) (secondary gNB) addition processs)
SgNB addition request • RRC Connection Reconfiguration message contains crucial information for the
UE to perform synchronization and Random Access Procedure
SgNB addition request
ACK
RRC Connection
Reconfiguration Some of the most important Random Access parameters from
RRC Connection RRCConnectionReconfiguration*:
Reconfiguration Complete
SgNB Reconfiguration • >RACH-ConfigCommon
Complete
• RACH-ConfigCommonGeneric (SEQUENCE)
• msg1-SubcarrierSpacing  (30kHz for below 6GHz, 120kHz for above 6GHz)
• prach-ConfigurationIndex  parameter: NRCELL/prachConfigurationIndex
Synchronization • prach-RootSequenceIndex  parameter: NRCELL/prachRootSequenceIndex
• ra-ContentionResolutionTimer  parameter: NRCELL/raContentionResolutionTmr
• rsrp-ThresholdSSB  parameter NRCELL/rsrpThresholdSSB
• >RACH-ConfigCommonGeneric
Random Access • zeroCorrelationZoneConfig  parameter: NRCELL/zeroCorrelationZoneConfig
• preambleReceivedTargetPower  parameter: NRCELL/preambleReceivedTargetPower
• preambleTransMax  parameter: NRCELL/preambleTransMax
• powerRampingStep  parameter NRCELL/powerRampingStep
• ra-ResponseWindow  parameter: NRCELL/raResponseWindow

28 © Nokia 2018 Nokia Internal Use

*new parameters may be added when full alignment with 3gpp is done
 Overview
Random Access call flow / Contention based
4-step Random Access Procedure UE Synchronization
•1 The UE randomly selects a preamble and transmits it in resources
Random Access

reserved for PRACH channel 1

Msg1 - Preamble transmission
(Zadoff-Chu sequence)
•2 Upon reception of preamble, gNB prepares Response containing
Msg2 Random Access Response
information to align timing of UE, assigns a Temporary C-RNTI (Temp. C-RNTI, UL Grant, TA)
2
and schedules an UL Grant to send Msg3

•3 UE sends first scheduled transmission using Temp. C-RNTI

Contention Resolution

Msg3
containing Contention Resolution ID (CRID). 3
(CRID)
•4 Msg4 is addressed to the UE using Temporary C-RNTI containing
the selected CRID. If 2 or more UEs selected the same preamble Msg4
4
and PRACH resources, collision occurs and only the UE which (CRID)

receives his CRID will proceed

29 © Nokia 2018 Nokia Internal Use

Random Access
Msg1 – Preamble Transmission
Msg2 – Random access Response (RAR)

30 © Nokia 2018 Nokia Internal Use

Msg1 - Preamble transmission
1 2
Preamble selection PRACH slot
• There are 138 or 838 root sequences available depending on preamble • Periodicity and location of PRACH slot per
format in each cell Radio frame is set according to the PRACH
• A preamble sequence is determined from the root and cyclic shift provided configuration Index
by higher layers • PRACH configuration is obtained in RRC
• UE randomly selects 1 out of all available preambles that will be used for Connection Reconfiguration message
Msg1
3
PRACH occasions
• 3 occasions per PRACH slot are available in
time domain (fixed frequency domain)
4 • gNB has to sweep over beams for Random
PRACH transmission power Access in the same way as for Broadcast
• A preamble transmission power for PRACH is determined using • UE selects PRACH occasion based on DL beam
information obtained in RRC Connection Reconfiguration defining the with power satisfying configured level
target received power at the gNB. • A unique relation between sweeping and
• UE will increase its transmission power by a defined step for each Msg1 Random Access 5GNB beams is required in
retransmission order to enable initial acquisition by the UE

31 © Nokia 2018 Nokia Internal Use

 5GC000425-U, 5GC000425-Q

Periodicity T=2
Technical Details Assumptions:
radio frame 0 (10ms) radio frame 1 (10ms) PRACH config. = 0
Frame structure Slots
0 1 2 3 17 18 19 0 1 2 3 17 18 19
Periodicity T=2
number
PRACH slot
Preamble format = A2
Subcarrier spacing = 30kHz
4.32 MHz

PRACH frequency 0 Occasion #1 Occasion #2 Occasion #3

1

No
C H s l o t.
2
of 12 PRBs
A
granularity

3
led i n P R
CH i s schedu o t.
nly PR A n this sl
4
l e as e , o e c te d i
A re ex p
In 5G18 nels/signals are
5
4.32 MHz = 12 PRBs * an
other ch
6
12 subcarriers per PRB *
7
30 kHz subcarrier spacing

14 symbols in slot. Slot duration with given assumptions = 0.5 ms

Even though in 12 PRBs there are Occassion

144 subcarriers, final PRACH
occasion occupies 139 of them
subcarriers

Subcarrier spacing:
CP Preamble sequence
139

• 30 kHz for below 6GHz

32 © Nokia 2018 Nokia Internal Use

CP + Sequence duration with given assumptions = 0.14 ms
Technical Details
Msg1 - PRACH preamble 1

What is a preamble
Zadoff-Chu Sequences:
G
CP SEQ
P • Constant Amplitude Zero Auto correlation sequences (i.e.
orthogonal to its cyclic shifts)
• Low cross correlation between root sequences
TCP TSEQ TGP
• The physical layer random access preamble, consists of a cyclic
prefix of length TCP and a sequence part of length TSEQ.
• Depending on format, premable may have Guard Period (GP)
Preamble types
• Preambles are based on Zadoff-Chu sequences of length depending Contention based Non-contention based
on preamble format (139 or 839)
• There are 138 or 838 root sequences depending on format • UEs randomly select • gNB dedicates preamble
preamble to UE
Cyclic prefix: • More than 1 UE may • No collision possible
select same preamble • Used during handovers
• Guard period to avoid inter-symbol interferences
(collision) and SgNB addition
• Repetition of the end of the preamble sequence to maintain
• Used during SgNB (from subfeature
orthogonality of preambles 5GC000572-I)
addition
• The length of the cyclic prefix determines the maximum (before subfeature
propagation delay and is determined according to the preamble 5GC000572-I)
format.

33 © Nokia 2018 Nokia Internal Use

Technical Details
Msg1 - Root sequence & cyclic shifts 1

Root sequence is cell specific and should be considered during planning phase

Cyclic
• Root sequence is obtained from RRC Connection Reconfiguration message shift
together with other Random Access related parameters
• Multiple preambles can be obtained (depending on configuration) by applying
different cyclic shifts to root sequences, thus expanding the preamble capacity
• Each root sequence is orthogonal to its cyclic shifts
• If one root sequence and its cyclic shifts are not enough to generate a given number
Root sequence
of preambles available in a cell, the UEs will move on to the next root sequence
Shifted root
and its cyclic shifts for preamble sequence generation sequence
• Number of Cyclic shifts possible per root sequence are determined according 𝜋 𝑢𝑛(𝑖+1 )
−𝑗
𝐿𝑅𝐴
to zero correlation zone configuration associated with preamble format (short, 𝒙 (𝒊)=𝑒
long format – see next slides)
𝟎 ≤ 𝒊 ≤ 𝑁 𝑍𝐶 −1

34 © Nokia 2018 Nokia Internal Use

 5GC000425-U, 5GC001070-C

Technical Details
Msg1 – Preambles available 1

Preamble format 0* (long) Preamble format A2, C2** (short)

• Preamble length is 839 • Preamble length is 139
• Supported subcarrier spacing: • Supported subcarrier spacings:
• 1.25 kHz  for below 6 GHz • 30 kHz  for below 6 GHz
• 120 kHz  for above 6 GHz
• There is a pool of 64 preambles available per cell (for contention and non-contention based RA)
• Number of preamble index allocated to non-dedicated preamble pool is defined by parameter
NRCELL/cbPreamblesPerSsb (applicable with subfeature 5GC000572-I)
• Non-dedicated preamble corresponds to preamble indices with index < cbPreamblesPerSsb
• Preamble format determines table with zero correlation zone configuration
• Depending on configuration, different number of cyclic shifts per root is available

UE randomly selects one out of all available preambles to initiate Random Access Procedure

*Format available for L1 (not e2e) with subfeature 5GC001070-C (R5, 03/2018 3gpp). Before that only short format is in use
** Availability of format C2 for demo purposes in 5G18A
35 © Nokia 2018 Nokia Internal Use
 5GC000425-P, 5GC000511-D

Technical Details
Msg1 – Root sequence 1

• Root sequence index parameter is obtained by the UE from RRC Conection Reconfiguration message
(RACH-ConfigCommon structure)
- prach-RootSequenceIndex CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137}
• It is configurable on NRCELL level  NRCELL/prachRootSequenceIndex
• It indicates first Zadoff-Chu sequence from which preambles starts to be generated
- Pool of 64 preambles may be split into dedicated and non-dedicated preambles. Dedicated preambles will be available with introduction of subfeature
5GC000572-I
3gpp 38.211 Table 6.3.3.1-4: Mapping from PRACHRootSequenceIndex i to sequence number u for preamble formats with LRA= 139
i Sequence number u in increasing order of i
Root sequence index 0 – 19
20 – 39
1
11
138
128
2
12
137
127
3
13
136
126
4
14
135
125
5
15
134
124 16
6 133
123
7
17
132
122
8
18
131
121
9
19
130
120
10
20
129
119
assignment is highly related to 40 – 59
60 – 79
21
31
118
108
22
32
117
107
23
33
116
106
24
34
115
105
25
35
114 26
104 36
113
103
27
37
112
102
28
38
111
101
29
39
110
100
30
40
109
99
planning aspects 80 – 99
100 – 119
41
51
98
88
42
52
97
87
43
53
96
86
44
54
95
85
45
55
94
84
46
56
93
83
47
57
92
82
48
58
91
81
49
59
90
80
50
60
89
79
Neighboring cells 120 – 137
138 – 837
61 78 62 77 63 76 64 75 65 74
N/A
66 73 67 72 68 71 69 70 - -

shouldn’t have overlapping

preamble pools

36 © Nokia 2018 Nokia Internal Use

 5GC001070-C, 5GC000425-P, 5GC000511-D

Technical Details
Msg1 - Preamble format 1 3gpp 38.211
𝐿𝑅𝐴 =839 and Δ 𝑓 𝑅𝐴 𝜖 {1.25,5 } 𝑘𝐻𝑧
Table 6.3.3.1-1: PRACH preamble formats for
Format 𝑅𝐴
𝑁 𝐶𝑃 Support for
• Two preamble formats are defined LRA Δ 𝑓 𝑅𝐴 Nu restricted sets
by 3gpp: Supported soon 0 839 24576 𝜅 3168 𝜅 Type A, Type B
1 839 1.25 kHz
2∙24576 𝜅 21024 𝜅 Type A, Type B
- Short  Sequence length LRA = 139 2 839
4 ∙24576 𝜅 4 688 𝜅 Type A, Type B
3 839 5 kHz
4 ∙6144 𝜅 3168 𝜅 Type A, Type B
- Long  Sequence length LRA = 839
• Nokia 5G18A release supports:
3gpp 38.211
- For now just A2 format Table 6.3.3.1-2: PRACH preamble formats for 𝐿𝑅𝐴 =139 and
- Format 0 (later also in 5G18A) kHz where𝜇𝜖 0,1,2,3{ }
Format 𝑅𝐴 Support for Max cell range [m]
- Format C2 for demo purposes LRA Δ 𝑓 𝑅𝐴 Nu 𝑁 𝐶𝑃
restricted sets for SCS = 30 kHz
A1 139 - 469
Supported A2 139 - 1055
Preambe format determines A3
B1
139
139
-
-
1758
176
duration of cyclic prefix and B2
B3
139
139
kHz -
-
528
879
B4 139 -
sequence (thus cell range) C0 139 - 1934
2650
C2 139  
Demo purposes 4600

Nu – preamble sequence length

- Subcarrier spacing
𝑅𝐴
37 © Nokia 2018 Nokia Internal Use 𝑁 𝐶𝑃 −𝑐𝑦𝑐𝑙𝑖𝑐 𝑝𝑟𝑒𝑓𝑖𝑥 𝑙𝑒𝑛𝑔𝑡h
 5GC000425-P, 5GC000511-D

Technical Details
3gpp 38.211
Msg1 – zeroCorrelationZoneConfig 1 Table 6.3.3.1-7: NCS for preamble formats
𝑅𝐴
withΔ 𝑓 =15 ∙ 2
𝜇
where {
𝜇𝜖 0,1,2,3 }
zeroCorrelation
• Another parameter obtained by the UE from RRC Connection Reconfiguration ZoneConfig
NCS value

(RACH-ConfigCommonGeneric) is zeroCorrelationZoneConfig (all values 0 0

1 2
supported) 2 4
3 6
- zeroCorrelationZoneConfig INTEGER(0..15) 4 8
5 10
- Depending on SCS, slighly different table is given by 3gpp (3 variants) 6 12
7 13
• It is configurable on NRCELL level  NRCELL/zeroCorrelationZoneConfig 8 15
9 17
• Table provides mapping between zeroCorrelationZoneConfig and NCS value 10 19
11 23
(Cyclic Shift Interval) 12 27
13 34
- NCS determines how many cyclic shifts per root is available Value for example 14 46
(the higher NCS the lower number of cyclic shifts per root) 15 69

Number of Cyclic shifts per root assuming

zeroCorrelationZoneCOnfig = 13  NCS = 34 Ncs = 0 means that no
Root #x 0 … 33 34 … 67 68 … 101 102 … 135 cyclic shifts
applicable for root
NCS = 34

38 © Nokia 2018 Nokia Internal Use

LRA=139
 5GC000425-U
3gpp 38.211
Technical Details Table 6.3.3.1-7: NCS for preamble formats
𝑅𝐴 𝜇
{
𝜇𝜖 0,1,2,3 }
withΔ 𝑓 =15 ∙ 2 where
Msg1 – Preambles generation 1
zeroCorrelation NCS value
ZoneConfig
0 0
• Each cell computes 64 preambles based on parameters: 1 2
2 4
- Root sequence index (indicates from which root computation starts) 3 6
4 8
- Zero Correlation Zone Config (relevat table depends on preamble format and SCS) 5 10
6 12
7 13
• Depending on NCS, there is different „capacity” of each root 8 15
9 17
sequence 10 19
11 23
- If one root is not enough to generate 64 preambles, next roots are taken 12 27
13 34
14 46
Generation of 64 preambles assuming LRA=139 and Value for example 15 69
zeroCorrelationZoneCOnfig = 13  NCS = 34

Root #1 0 … 33 34 … 67 68 … 101 102 … 135

Root #2 0 … 33 34 … 67 68 … 101 102 … 135
16 Roots needed
Root #3 0 … 33 34 … 67 68 … 101 102 … 135
to generate 64
preambles
…

…
…
…

…
0 … 33 34 … 67 68 … 101 102 … 135 (4*16)
Root #16

39 © Nokia 2018 Nokia Internal Use

 5GC000425-AC, 5GC000425-U, 5GC000425-Q,
5GC001070-C

Technical Details
Msg1 - PRACH subframe structure 2

PRACH slot In 5G18A, two configurations are

• UEs send Msg1 on PRACH channel in specific slot based on PRACH
supported:
configuration • PRACH conf. index = 0 AND
• The PRACH configuration is delivered to UEs in RRCConnectionReconfig. SCS = 30 kHz (Periodicity T=2)
• There are multiple Occasions per PRACH slot depending on the preamble - Slots #18,19 in frame 2x
format (for now all supported options consist of 3 occasions)
- Slot #19 in frame 2x+1
- 3 PRACH occasions in each slot
Periodicity T=2
• PRACH conf. index = 1
radio frame 0 radio frame 1
(10ms) (10ms)
AND SCS = 120 kHz (Periodicity T=4)
Slots
number 0 1 2 3 17 18 19 0 1 2 3 17 18 19
- Slots #57,58,59,77,78,79 in 3 consecutive frames
2x, 2x+1, 2x+2
- Slots #59,77,78,79 in frame 2x+3
- 3 PRACH occasions in each slot
Occasion #1 Occasion #2 Occasion #3
• From 5GC000425-AC, support of one occasion
CP + Sequence duration
(starting from symbol 9 in slot) and periodicity
Slot duration 20us available introduced for A2

40 © Nokia 2018 Nokia Internal Use

 5GC000425-U

Technical Details
Msg1 - PRACH configuration Index 2

• PRACH configuration is another parameter obtained by the UE from RRC Connection Reconfiguration
(RACH-ConfigCommon structure)
- prach-ConfigurationIndex INTEGER (0..255)
• It is configurable on NRCELL level  NRCELL/prachConfigurationIndex
• With this parameter UE knows which time location is dedicated for Random Access (PRACH)
• Below table corresponds to Nokia shadow specification (v6) of PRACH configuration Index as 3gpp
specification is not yet finished in this area
PRACH configuration Periodicity # PRACH PRACH starting PRACH formats PRACH frame and slot
index T occasions OFDM symbol combination per slot (frame,slot)
0 9 {(0,18);(0,19);
2 0 (A2,A2,A2)
(for below 6GHz) (3 per slot) (1,19)}
{(0,57);(0,58); (0,59);(0,77);(0,78);(0,79);
1 66 (1,57);(1,58);(1,59);(1,77);(1,78);(1,79);
4 0 (A2,A2,A2)
(for above 6GHz) (3 per slot) (2,57);(2,58);(2,59);(2,77);(2,78);(2,79);
(3,57);(3,77);(3,78);(3,79)}

41 © Nokia 2018 Nokia Internal Use

Technical Details
Msg1 – Occasion selection 3

Occasion to use for preamble transmission

• Before UE starts RA procedure, it looks for SS/PBCH blocks (SSB)
• If it happen that RSRP of certain beam transmitting SSB is higher than configured threshold
(NRCELL/rsrp-ThresholdSSB) this beam can be used to transmit preamble (up to UE implementation which beam exactly)
• Mapping between SSB index and Occasion (in frame and slot) to be used is shown in below table
(example with preamble format A2, PRACH configuration index = 1 and 32 configured beams):
• Mapping is Nokia proprietary, it will be aligned with 3gpp when relevant content is completed

SSB indices = consecutive beams

Occasion indices

Slots according to PRACH configuration

(3 occasion per slot)

Fixed

Assumption Occasion selection

Occasion UE successfully received SS/PBCH SSB index 19 points to frame SFNmod4=1 and second (out of 3)
selection block from beam (SSB index) 19 and occasion in slot #57 in that frame.
example it’s RSRP is higher than threshold At this time UE randomly selects 1 out of all available preambles

42 © Nokia 2018 Nokia Internal Use

Technical Details
Msg1 - Power for preamble (Msg1) transmission 4
preambleReceivedTargetPower

From RRC Connection Reconfiguration message

(RACH-ConfigCommonGeneric) UE receives two RX power: -
96 dBm
RX power: -
94 dBm
RX power: -
92 dBm
important parameters for Msg1 transmission:
NRCELL/preambleReceivedTargetPower - parameter

RRC Conn. Reconfig.

indicating initial RA preamble signal level (in dBm) required

(parameters)
(targeted) at gNB (-96dBm by default)
Msg1
(pathloss
NRCELL/powerRampingStep – parameter used to increase assumed to
power by UE in each preamble retransmission be 116 dB)
(2dB by default)
PUE_max = 23 dBm PUE_max = 23 dBm PUE_max = 23 dBm

PPRACH= 20 dBm PPRACH= 22 dBm PPRACH= 23 dBm

PPRACH – power used for transmission 2nd Tx 3rd Tx

1st Tx
(if needed) (if needed)
PUE_max – Highest power that can be used by the UE TX power selected
for transmission

43 © Nokia 2018 Nokia Internal Use + powerRampingStep

Technical Details
Msg2 – Random Access Response (RAR)

RAR grant :
• Upon receipt of Msg1 gNB will create temporary UE context and schedules a grant
for Random Access Response (RAR) PRACH: Msg1 - Preamble transmission
• The UE uses the beam to receive as it used for the transmission of PRACH (Zadoff-Chu sequence)
• If the RAR grant is not received within a specific time window, the UE will Create Temp.
UE Context
retransmit preamble with same power ramped up by a value specified in the RRC PDCCH - (RAR Grant)
Reconfiguration Complete message
PDSCH: Msg2 Random Access Response
(temp. C-RNTI, UL Grant, TA)

RAR grant timing

If RAR not received within
• Earliest: 3 subframes after the PRACH slot when the preamble has been received (3TTI+ raResponseWindow)
• Latest: 3 + NRCELL/ raResponseWindow slots after this PRACH slot
PRACH: Msg1 - Preamble transmission
(Zadoff-Chu sequence)

Radio Frame 0 Radio Frame 1

Slots 0 19 0 1 2 3 4 5 6 7 19
RAR window

PRACH
slot
n+3 (n+3) +
RAR window
44 © Nokia 2018 Nokia Internal Use
 5GC000425-Q

Technical Details
Msg2 – Random Access Response (RAR)
Random access response will be addressed to UEs by scrambling CRC of PDCCH with RA-RNTI

Example (For slot #18 & slot #19, SCS=30kHz)

RA-RNTI derivation from Msg1
sid tid RA-RNTI
0 18 0xFD
RA-RNTI = 1 + sid + 14 * (tid + X * fid) 4 18 0x101

8 18 0x105
Where: 0 19 0x10B
• Sid - index of first OFDM symbol of PRACH occasion in slot
4 19 0x10F
• tid – PRACH slot number ; fid – frequency index, equal to 0
• X – value dependant on SCS (0 as fid = 0) 8 19 0x113

The values from 0x0001 to 0xFFEF are reserved for C-RNTI. Possible RA-RNTI values are filtered out from
this range to be used specifically for RA-RNTI purposes.
Sid radio frame 0 radio frame 1
Slots (10ms) (10ms)
number 0 1 2 3 17 18 19 0 1 2 3 17 18 19
{0} {4} {8}
Occasion #1 Occasion #2 Occasion #3 {18} {19} {19}

45 © Nokia 2018 PRACH slot (14 symbols) tid

 5GC000425-U

Technical Details
Msg2 - Random Access Response (RAR)
Random Access Response (RAR):
• The RAR consists of a MAC RAR header and MAC RAR payload PRACH: Msg1 - Preamble transmission
• There is one sub-header per Random Access Response (Zadoff-Chu sequence)
• The MAC RAR header contains the detected preamble ID transmitted by UE Create Temp.
UE Context
• The RAR payload contains TA command, Temp-CRNTI and UL grant for Msg3 PDDCH: RAR Grant
• RAR must be sent within configurable NRCELL/raReponseWindow + 3 slots, (PRBs, MCS)
otherwise temporary UE context and temporary C-RNTI are released PDSCH: Msg2 Random Access Response
• Possible window duration depends on SCS (e.g. max 20 slots for below 6GHz) (temp. C-RNTI, UL Grant, TA)

If RAR not received within

MAC RAR Header MAC RAR Payload (3slots+ raResponseWindow)
E T RAPID TA command UL Grant Temp C-RNTI
PRACH: Msg1 - Preamble transmission
(Zadoff-Chu sequence)
RACH Msg2

MAC RAR header (1 byte) MAC RAR payload (6 bytes)

1 E: 1 bit field, Indicates if this is the last RAR sub-header 1 TA command: 12 bit field with Timing Advance Command
2 T: 1 bit field, Presence of RAPID or back-off indicator (BI) 2 UL Grant: 20 bit field, FD RB assignment (48 PRB), TD Resource Assignment (k0=0 &
SLIV=68), MCS (0), TPC command (=3, 0dB)
3 RAPID: 6 bit field, Random Access preamble ID sent
by UE, detected by 5GNB 3 Temp C-RNTI: 16 bit field (values from 0x0001 to 0xFFEF) – (excluding possible
RA-RNTI values)
46 © Nokia 2018 Nokia Internal Use
 5GC000425-AC, 5GC000425-X

Technical Details
Msg2 - Random Access Response (RAR)
Random Access Response (RAR):
• The RAR consists of a MAC RAR header and MAC RAR payload PRACH: Msg1 - Preamble transmission
• There is one sub-header per Random Access Response (Zadoff-Chu sequence)
• The MAC RAR header contains the detected preamble ID transmitted by UE Create Temp.
UE Context
• The RAR payload contains TA command, Temp-CRNTI and UL grant for Msg3 PDDCH: RAR Grant
• RAR must be sent within configurable NRCELL/raReponseWindow + 3 slots, (PRBs, MCS)
otherwise temporary UE context and temporary C-RNTI are released PDSCH: Msg2 Random Access Response
• Possible window duration depends on SCS (e.g. max 20 slots for below 6GHz) (temp. C-RNTI, UL Grant, TA)

If RAR not received within

MAC RAR Header MAC RAR Payload (3slots+ raResponseWindow)
E T RAPID TA command UL Grant Temp C-RNTI
PRACH: Msg1 - Preamble transmission
(Zadoff-Chu sequence)
RACH Msg2

MAC RAR header (1 byte) MAC RAR payload (6 bytes)

1 E: 1 bit field, Indicates if this is the last RAR sub-header 1 TA command: 12 bit field with Timing Advance Command
2 T: 1 bit field, Presence of RAPID or back-off indicator (BI) 2 UL Grant: 27 bit field, FD RB assignment (48 PRB), TD Resource Assignment (k0=0 &
SLIV=68), MCS (0), TPC command (=3, 0dB), UL delay
3 RAPID: 6 bit field, Random Access preamble ID sent
by UE, detected by 5GNB 3 Temp C-RNTI: 16 bit field (values from 0x0001 to 0xFFEF) – (excluding possible
RA-RNTI values)
47 © Nokia 2018 Nokia Internal Use
Contention Resolution
Msg3
Msg4

49 © Nokia 2018 Nokia Internal Use

Technical Details
RA Msg3

RACH Msg3 transmission:

• UE receives the UL grant in RAR Msg2 received from the gNB. Distance between
Msg2 TX and Msg3 RX must be within 6-9 slots PRACH: Msg1 - Preamble
• The UE sends the RACH Msg3 containing the 48-bit Contention Resolution ID (Zadoff-Chu sequence)
(CRID) PDSCH: Msg2 - RAR (RA-RNTI)
(Temp. C-RNTI, UL Grant, TA)

MAC contention resolution timer: PUSCH: Tx1- Msg3 (temp-CRNTI)

OK
(CRID)
• After transmission of Msg3, UE starts the MAC contention Resolution timer Make UE Context
MAC Contention
(NRCELL/raContentionResolutionTmr) Resolution Timer
permanent

• The MAC contention Resolution timer monitors the reception of RACH Msg4
• The UE restarts the Mac Contention Resolution Timer at each HARQ reTx
PUSCH: Tx2- Msg3 (temp-CRNTI)
(CRID)
• At the successful reception of RACH Msg3, gNB makes UE context permanent and NOK
Restart Contention

Optional
stores the temporary C-RNTI and the selected MAC CE CRID Resolution Timer

• If the CRC is NOK a retransmission of Msg3 is scheduled with HARQ ID set to '0' and NRCELL/maxHarqMsg3Tx reached
NDI set to '0' . If the maximum number of RA Msg3 transmissions
(NRCELLGRP/maxHarqMsg3Tx) has been reached and still the CRC is NOK then gNB PRACH: Msg1 - Preamble
(Zadoff-Chu sequence)
releases the UE context and the temporary C-RNTI

50 © Nokia 2018 Nokia Internal Use

Technical Details
Msg4 – Contention Resolution
• After transmission of Msg3, UE starts the MAC contention Resolution timer
AT UE

(NRCELL/raContentionResolutionTmr) PRACH: Msg1 - Preamble

• The MAC contention Resolution timer monitors the reception of RACH msg4 (Zadoff-Chu sequence)

PDSCH: Msg2 - RAR (RA-RNTI)

(Temp. C-RNTI, UL Grant, TA)
AT gNB

• After successful reception of RACH Msg3, 5GNB resolves RACH Contention by PUSCH: Msg3 (temp. C-RNTI)
transmission of MAC PDU with the Contention Resolution MAC CE (CRID)
MAC Contention
Resolution Timer
PDCCH: DL Grant
• If the UE receives RA msg4 before MAC contention resolution timer expiry AND the
Contention resolution MAC CE matches the CRID, the UE considers the Random Access PDSCH: Msg4 (temp. C-RNTI)
procedure as successfully completed and will set the C-RNTI to the value of the Temporary C- (CRID)
RNTI UE compares CRID from
Msg3 and Msg4
ACK
• The UE considers the contention • Following the contention resolution failure,
resolution unsuccessful the UE
- If the Contention resolution MAC CE - Increments CRID does not match or MAC Contention

Optional
does not match the CRID OR PREAMBLE_TRANSMISSION_COUNTER Resolution timer expires or max. number of
- MAC contention resolution timer expires by 1 transmissions reached
OR - If
- Maximum number of transmissions has PREAMBLE_TRANSMISSION_COUNTER
been reached exceeds NRCELL/preambleTransMax declare PRACH: Msg1 - Preamble transmission
Random Access failure, and delay the next RA (Zadoff-Chu sequence)
transmission by backoff time.
51 © Nokia 2018 - Use
Nokia Internal Starts the Random Access procedure
Agenda

1
Introduction
2
Technical
Details
3
Configuration
Management

52 © Nokia 2018 Nokia Internal Use

Configuration Management
Definition of terms and rules for parameter classification*
The ‘Basic Parameters’ category contains primary
parameters which should be considered during cell
deployment and must be adjusted to a particular
scenario:
• Network Element (NE) identifiers
• Planning parameters, e.g. neighbour definitions, frequency, scrambling
codes, PCI, RA preambles
• Parameters that are the outcome from dimensioning, i.e. basic
parameters defining amount of resources
• Basic parameters activating basic functionalities, e.g. power control,
admission control, handovers
• Parameters defining operators’ strategy, e.g. traffic steering, thresholds
for power control, handovers, cell reselections, basic parameters defining
feature behaviour
The ‘Advanced Parameters’ category contains the
parameters for network optimisation and fine tuning:
• Decent network performance should be achieved without tuning these
parameters
• Universal defaults ensuring decent network performance need to be
defined for all parameters of this category. If this is not possible for a
given parameter it must be put to the ‘Basic Parameters’ category
• Parameters requiring detailed system knowledge and broad experience
unless rules for the ‘Basic Parameters’ category are violated
• All parameters (even without defaults, e.g. optional structures) related
to advanced and very complex features

The ‘Obsolete parameters’ category is intended for parameters that are candidates to be removed from the
product in a future release: * - purpose: Categories of parameters have been defined to simplify network
• Parameters always used with default value parametrization. Parameterization effort shall be focused mainly on Basic ones.
• Parameters that are not used by operators Categorization is reflected in a ‘view’ definition in NetAct CM Editor.
• Parameters that are not relevant anymore

53 © Nokia 2018 Nokia Internal Use

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRCELL/ CBRA preambles per SSB This parameter defines the number of CBRA preambles 1...64, step 1 64
cbPreamblesPerSsb per SSB per RACH transmission occasion

NRCELL/ PRACH Frequency start This parameter defines the PRACH Frequency start. It 0…36, step 1 0
msg1FrequencyStart corresponds to RRC parameter 'msg1-FrequencyStart'
(see 38.331) and L1 parameter 'prach-frequency-start'
(see 38.211).
It defines the offset of the lowest PRACH transmission
occasion in frequency domain with respect to the PRB
0 of the initial active UL BWP(s)

NRCELL/ Number of SSBs per RACH This parameter defines the number of SSBs per RACH 0:oneEighth; 1:oneFourth; 3
nbrOfSsbPerRachOccasion occasion occasion. 2:oneHalf; 3:one; 4:two;
5:four; 6:eight; 7:sixteen
The only supported value is 3 corresponding to one.

NRCELL/ Power ramping factor This parameter defines the power ramping factor 0:dB0; 1:dB2; 3:dB4; 4:dB6 1
powerRampingStep

54 © Nokia 2018 Customer Confidential

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRCELL/ PRACH Configuration Index This parameter defines the PRACH Configuration 0...255, step 1 0
prachConfigurationIndex Index

NRCELL/ PRACH root sequence index This parameter defines the PRACH root sequence from 0 to 837 step 1 0
prachRootSequenceIndex index.
For the short PRACH format (L=139), the maximum
value is137.
For the long PRACH format (L=839), the maximum
value is 837.
NRCELL/ Initial preamble power This parameter defines the initial preamble power 0:dBm-120; 1:dBm-118; … 12:dBm-96
preambleReceivedTargetPo 12:dBm-96; 13:dBm-94 …
wer 62:dBm4; 63:dBm6
NRCELL/ Power ramping factor This parameter defines the maximum number of 0:n3; 1:n4; 2:n5; 3:n6; 4:n7; 6:n10
preambleTransMax preamble transmission 5:n8; 6:n10; 7:n20; 8:n50;
9:n100; 10:n200

55 © Nokia 2018 Customer Confidential

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRCELL/ Timer for contention resolution This parameter defines the timer for contention 0:sf8; 1:sf16; 7:sf64
raContentionResolutionTm resolution
r 2:sf24; 3:sf32;
4:sf40; 5:sf48;
6:sf56; 7:sf64
NRCELL/ Duration of random access response This parameter defines the duration of random access 0:sl1; 1:sl2; See
raResponseWindow window response window. description
2:sl4; 3:sl8;
Default Value for the parameter depends on whether
the New Radio cell gets its HW resources from radio 4:sl10; 5:sl20;
module(s) supported in analog beamforming (carrier 6:sl40; 7:sl80
frequencies above 6GHz) or digital beamforming
(carrier frequencies below 6GHz).
1) In case of analog beamforming, default value for
this parameter should be equal to 7 (corresponding
to sl80, i.e. 80 slots)
2) In case of digital beamforming, default value for
this parameter should be equal to 5 (corresponding
to sl20, i.e. 20 slots)

56 © Nokia 2018 Customer Confidential

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRCELL/ Zero Correlation Zone Config This parameter defines the zero Correlation Zone 0...15, step 1 13
zeroCorrelationZoneConfi Config
g
NRCELL/ RRSRP threshold for SSB block This parameter defines the RSRP threshold for SSB 0…124, step 1 See
rsrpThresholdSSB selection block selection. Using this parameter, the UE can select description
the SS block and corresponding PRACH resource for
path loss estimation and (re)transmission based on SS
blocks that satisfy the SSB threshold.
Default Value for the parameter depends on whether
the New Radio cell gets its HW resources from radio
module(s) supported in analog beamforming (carrier
frequencies above 6GHz) or digital beamforming
(carrier frequencies below 6GHz).
1) In case of analog beamforming, this parameter
should have default value equal to 11
(corresponding to -103dBm)
2) In case of digital beamforming, this parameter
should have default value equal to 19
(corresponding to -119 dBm)

57 © Nokia 2018 Customer Confidential

Nokia Internal Use
References and acknowledgments

References
5G 3gpp specifications (38.xxx family)

Nokia shadow specifications

Various 5G CFAMs

5G User Plane specification

PRACH (gNB-ABIL) L1 feature specification for 5G18A

PSS/SSS (Airphone-ABIL) L1 Level Feature Specification for 5G18A

PBCH-DMRS/PSS/SSS L1 Level Feature, Specification for 5G18A

59 © Nokia 2018 Nokia Internal Use

Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia Solutions and Networks. This
document is provided subject to confidentiality obligations
of the applicable agreement(s).
This document is intended for use of Nokia Solutions and
Networks customers and collaborators only for the purpose
for which this document is submitted by Nokia Solution and
Networks. No part of this document may be reproduced or
made available to the public or to any third party in any
form or means without the prior written permission of Nokia
Solutions and Networks. This document is to be used by
properly trained professional personnel. Any use of the
contents in this document is limited strictly to the use(s)
specifically created in the applicable agreement(s) under
which the document is submitted. The user of this document
may voluntarily provide suggestions, comments or other
feedback to Nokia Solutions and Networks in respect of the
contents of this document ("Feedback"). Such Feedback may
60 © Nokia 2018 Nokia Internal Use
be used in Nokia Solutions and Networks products and
related specifications or other documentation. Accordingly,
if the user of this document gives Nokia Solutions and
Networks Feedback on the contents of this document, Nokia
Solutions and Networks may freely use, disclose, reproduce,
license, distribute and otherwise commercialize the feedback
in any Nokia Solutions and Networks product, technology,
service, specification or
other documentation.
Nokia Solutions and Networks operates a policy of ongoing
development. Nokia Solutions and Networks reserves the
right to make changes and improvements to any of the
products and/or services described in this document or
withdraw this document at any time without prior notice.
The contents of this document are provided "as is". Except
as required by applicable law, no warranties of any kind,
either express or implied, including, but not limited to, the
implied warranties of merchantability and fitness for a
particular purpose, are made in relation to the accuracy,
reliability or contents of this document. NOKIA
SOLUTIONS AND NETWORKS SHALL NOT BE
RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT or for any loss of data or income or any
special, incidental, consequential, indirect or direct damages
howsoever caused, that might arise from the use of this
document or any contents of this document.
This document and the product(s) it describes are protected
by copyright according to the
applicable laws.
Nokia is a registered trademark of Nokia Corporation. Other
product and company names mentioned herein may be
trademarks or trade names of their respective owners.
© Nokia Solutions and Networks 2014