5G Planning Topics – Part 3

5G19

Chris Johnson
LDO Europe, Radio
4th June 2019

1 18/03/2025 © Nokia 2017

Customer Confidential
Introduction

• Series of 3 sessions to address 5G Radio Network Planning

requirements
• Remote delivery via 2 hour Webex
• Sessions to be recorded
• Inclusion of both 4G and 5G parameter sets
30th April 21st May 4th June

5G 5G 5G Design
Planning Planning within 4G
Part 1 Part 2 BTS

5G Design within 4G BTS - Updated WebEx.ics

2 18/03/2025 © Nokia 2014

For internal use
Session 1 – 5G Planning Part 1 – Tuesday 30th April 2019

• NR-ARFCN & GSCN

• Numerology
• Cyclic Prefix
• PCI Allocation
• Slot Format
• Active Antenna Planning
• Beam Set Selection
• SS/PBCH Block Configuration
• CSI Reference Signal for Beam
Management
LINK
Material and Recording available in webNEI at:

3 18/03/2025 © Nokia 2014

For internal use
Session 2 – 5G Planning Part 2 – Tuesday 21st May 2019

• PRACH Planning
• Scheduling Request
• Admission Control
• Downlink Transmit Powers
• Neighbour Planning
• Mobility
• Cell and BTS Identity
Planning
• Tracking Area Planning
Material and Recording available in webNEI at:
LINK

4 18/03/2025 © Nokia 2014

For internal use
Session 3 – 5G Design within 4G BTS – Tuesday 4th June
2019

• Introduction
• 5G Status Indicator
• 4G Anchor Carrier Selection
• Admission of 5G Subscribers
• NSA Activation
• Measurement based 5G SCell Addition

5 18/03/2025 © Nokia 2014

For internal use
4G Parameter Design
for 5G Non-Standalone
(NSA)
LTE19
Issue 1
Global NPO
March 2019

6 18/03/2025 © Nokia 2017

For Internal Use
Content

• Introduction
• 5G Status Indicator
• 4G Anchor Carrier Selection
• Admission of 5G Subscribers
• NSA Activation
• Measurement based 5G SCell Addition

7 18/03/2025 © Nokia 2014

For internal use
Introduction

8 18/03/2025 © Nokia 2017

For Internal Use
Background

• The Non-Standalone Base Station architecture requires feature activation and

parameter configuration at the 4G Base Station
• The features available in LTE19 are:
• LTE4088: LTE-NR Dual Connectivity Option 3X
• LTE4193: Dynamic Trigger for LTE-NR DC Option 3X
• LTE4575: Blind Carrier Aggregation with LTE-NR DC Option 3X
• LTE4087: X2 interface with NR gNB
• LTE4744: gNB Initiated EN-DC Configuration Update

• LTE4088 introduces the basic parameter set for the Non-Standalone configuration
• LTE4193 provides an enhanced solution for adding the 5G secondary cell

• LTE19 also allows the ‘5G Status Indicator’ to be broadcast by 4G SIB2

9 18/03/2025 © Nokia 2018

For internal use
 NRDCDPR
4G Databuild Structure nrDcPrId
carrierFreqNrCell nrDcMeasConfig
LNBTS dataVolThreshold
GTPU b1ThresholdNrRsrp
enDCpMaxEUTRApowerOffset
b1ThresholdNrRsrq
actLteNrDualConnectivity gNBIpAddrList enDCpMaxNRpowerOffset
b1TimeToTriggerRsrp
actDynTrigLteNrDualConnectivity cAggrLteNrDcCellList
b1TimeToTriggerRsrq
actCAggrLteNrDualConnectivity b1TriggerQuantity
tLteNrDualConnectPrep dynTriggerLteNrDcConfList
hysB1ThresholdRsrp
tS1eRABModInd lcrId hysB1ThresholdRsrq
tDataFwdX2gNB
LNADJGNB method quantityConfigId
adjGnbId ssbDuration
pdcpProf1001 nrDcQuantityConfig ssbOffset
adjGnbIdLength
administrativeState quantityConfigId ssbPeriodicity
pdcpProfileId ssbSubcarrierSpacing
snSizeDl cPlaneIpAddr filterCoefficientRsrp
snSizeUl lnAdjGnbId filterCoefficientRsrq
statusRepReq mcc
tDiscard mnc
mncLength LNRELGNBCELL
x2ToGnbLinkStatus lnRelGnbCellId
qciTab6/7/8/9/Operator gnbIdLength
lteNrDualConnectAllowed
lteNrDualConnectSupport LNCEL nrCellId
nrPdcpProfIdx
mcc
startArpEnDc defaultLnRelGnbCellId mnc
stopArpEnDc upperLayerIndicationR15 mncLength
nrStatus
SIB
10 18/03/2025 © Nokia 2018
For internal use primPlmnUpperLayerIndicationR15
5G Status Indicator

11 18/03/2025 © Nokia 2017

For Internal Use
Introduction

• The 5G ‘Status Indicator’ is used to display a ‘5G’ icon

on the screen of the end-user device
• Informs the end-user that services can benefit from a
5G connection

• Requirement to ensure that 5G icon is displayed only when UE is within 5G

coverage
• 5G Status Indicator is broadcast by 4G SIB so risk of UE being inside 4G
coverage but outside 5G coverage
• Icon has a large dependence upon UE implementation

• Use of the Status Indicator must be agreed with the operator before enabling

12 18/03/2025 © Nokia 2018

For internal use
NAS: Attach Accept

• The UE is provided with the NAS:

Content from NAS: Attach Accept message
Attach Accept message when
registering with the MME (3GPP TS 24.301)

• This message includes the

‘RestrictDCNR’ flag which reflects the
subscription information provided by
the HSS

• A UE should only display the 5G Icon

when a user has subscribed to 5G
services and is not restricted
• this statement relies upon UE
implementation

13 18/03/2025 © Nokia 2018

For internal use
‘Upper Layer Indication’
• The release 15 version of the 4G SIB2 includes the following flag:

• This flag is intended to indicate that 5G is available at that

location
• The device can then display a 5G icon for the end-user Value ‘0’ is interpreted as
‘false’
• The flag can be configured for each PLMN listed in SIB1
Value ‘1’ is interpreted as
• The Nokia 4G databuild includes the following parameters: ‘true’
Parameter Object Range Default
Values ‘2’ to ‘7’ are reserved
primPlmnUpperLayerIndication
SIB 0 to 7 -
R15
upperLayerIndicationR15 LNCEL 0 to 7 -

14 18/03/2025 © Nokia 2018

For internal use Belongs to furtherPlmnIdL parameter
structure
Layer specific Configuration

• In general, it is recommended that the ‘Upper Layer Indication’ is only broadcast by 4G

cells which support 5G Secondary Cell Addition
• EN-DC feature is enabled and at least one cell level 4G->5G neighbour relation is
configured

Broadcast
5G Cell 4G Anchor Cell Upper Layer
Indication
Do not Broadcast
4G Cell (no 5G Upper Layer
Access) Indication

15 18/03/2025 © Nokia 2018

For internal use
5G Status Indicator - Scenarios

• Use of the flag in isolation can provide the end-user with misleading information
• For example, UE can be within 4G coverage and receive the flag from SIB2, but
the UE may be outside 5G coverage and so unable to benefit from 5G

UE inside 5G coverage UE outside 5G coverage

Flag provides meaningful indication Flag provides misleading indication

5G Cell 5G Cell

4G Cell 4G Cell

16 18/03/2025 © Nokia 2018

For internal use
5G Status Indicator - Rules

• The following rules have been agreed to determine when the 5G icon is displayed
• UE vendors can activate ‘Config A’ to ‘Config D’ according to individual operator
requirements
• ‘Config A’ is the most stringent and only displays the 5G icon when the UE is already
connected to a 5G cell for NSA operation (or when the UE is camped on/connected to
• a NG-RAN/5G
‘Config Core)
D’ is the most relaxed and
allows the 5G icon to be displayed
without checking for 5G coverage
• ‘Configs B & C’ appear fair to the
end-user because the UE measures
the 5G coverage to verify that it
exists before displaying the 5G icon

Microsoft Word
17 18/03/2025 © Nokia 2018
97 - 2003 Document Liaison Statement from GSMA
For internal use
5G Status Indicator – Challenges with Coverage
Verification
• Verifying that 5G coverage exists before displaying the 5G icon is not simplistic
• the UE would need to apply a measurement threshold, e.g. RSRP
• this threshold would need to be aligned with any threshold used by the
network
• if the UE uses a relaxed threshold while the network uses a stringent
threshold then the UE may not be allocated 5G by the network after the UE
has displayed the 5G icon
• identification of 5G carrier to measure
• the 4G network is not required to broadcast any 5G carrier information in its
SIB for NSA operation because there is no cell reselection towards 5G
• this means that the UE does not know which 5G carrier to measure
• UE could complete a band scan but this would not help because 5G carriers
for NSA are ‘anonymous’, i.e. 5G SIB are not broadcast so UE does not know
which carrier belongs to which operator
• Potential solution could be that UE remembers 5G carrier(s) that are allocated
18 18/03/2025 © Nokia 2018
while in RRC Connected and then uses those carriers for measurement
For internal use
5G Status Indicator – Without Measurements

• If measurements are not feasible then the choice is reduced to ‘Config A’ or ‘Config
D’
• ‘Config A’ conservative approach with less promotion of 5G
• ‘Config D’ aggressive approach with potentially misleading indication

19 18/03/2025 © Nokia 2018

For internal use
4G Anchor Carrier Selection

20 18/03/2025 © Nokia 2017

For Internal Use
 Background
• Existing 4G network is likely to have multiple RF carriers
• It is necessary to identify a strategy for allowing access to 5G from those carriers

Allow 5G access from all 4G carriers

• Avoids the requirement to move 5G capable UE onto a specific carrier
• Maximises utilisation of 5G
An
• Relies upon UE support for all band combinations
intermediat
• Increased number of neighbour objects per LNBTS e solution is
also
Allow 5G access from specific 4G carrier possible,
allowing 5G
• Requirement to move 5G capable UE onto a specific carrier without impacting existing access from
traffic balance a subset of
• Unlikely that 100% of 5G capable UE will be on the selected carrier so 5G utilisation likely 4G carriers
to be lower
• Specific anchor carrier can be selected based upon UE capabilities/coverage/capacity
• Reduced number of neighbour objects per LNBTS
21 18/03/2025 © Nokia 2018
For internal use
 Access from all 4G Carriers (I)

• 3GPP specifications (TS 39.101-3) should be checked to identify whether or not all
band combinations have been standardised
• Example on this slide based upon:
• 4G network using L2100, L800, L1800, L900, T2300
• 5G using 3.5 GHz (band n77 or n78)
• Band combination 40_n78
has not been standardised
so in this example it is more L2100
attractive to configure 5G as
band n77 L1800
• For some band combinations
L900
it is not mandatory for UE to
support dual uplink L800
transmission
• can impact peak uplink T2300
22 18/03/2025 © Nokia 2018
throughputs
For internal use
Access from all 4G Carriers (II)

• UE capability information should also be checked

• If dominant UE models do not support the majority of the required band combinations
then it may be preferable to allow 5G access from a specific 4G carrier and implement
a solution to move 5G devices onto that carrier

• If the majority of UE models support the majority of the required band combinations
then 4G->5G neighbour objects can be created from each 4G cell towards each target
5G cell
• LNADJGNB object from LNBTS towards specific 5G BTS
• LNRELGNBCELL object from LNCEL towards specific 5G cell

23 18/03/2025 © Nokia 2018

For internal use
Access from specific 4G Carrier(s) (I)

• 3GPP specifications (TS 39.101-3) should be checked to identify which band

combinations have been standardised
• UE capability information should be checked for all dominant devices
• Ideally, a 4G band should be selected such that:
• all 5G capable UE support the band combination
• the 4G band offers better coverage than other 4G
4G cell
bands
• the 4G band offers higher bandwidth than other 4G
bands 4G cell
• The existing traffic management strategy
• This strategy is the
prioritises likely to require
selected banda solution to move
4G cell 5G cell
only 5G capable UE towards the selected carrier
providing 5G
Access

24 18/03/2025 © Nokia 2018

For internal use
Access from specific 4G Carrier (II)

• ‘Basic’ traffic management solutions are not able to differentiate 5G capable UE

from any other UE, e.g. the use of basic Absolute Priorities in Idle mode will move
all UE rather than just 5G capable UE
• It is necessary to use more advanced traffic management solutions to move 5G UE
to a specific carrier without impacting the balance of legacy UE
• Mobility Profiles can be used for this purpose: LNCEL - moPrMappingList

lteNrDualConnectSupport
Mobility Profile based Mobility Profile based
mcc
upon UE Capability upon SPID
mnc
mncLength
• Configuring a mobility profile based upon UE capability moPrId
Mobility
profile based
avoids the requirement to define specific SPID values in spid upon UE
the HSS spidLast capability
• All 5G capable UE would be moved towards the 4G anchor
carrier irrespective of 5G subscription information within
25 18/03/2025 © Nokia 2018 Mobility profile
theuseHSS
For internal based upon
SPID
Access from specific 4G Carrier (III)

• If end-user has a 5G device but does not purchase a 5G

Mobility Profile based subscription then the UE will be moved to the 5G
upon UE Capability anchor carrier
• not desirable
• If end-user purchases a 5G subscription but places SIM
Mobility Profile based within a 4G device then the UE will be moved to the 5G
upon SPID anchor carrier
• not desirable

Mobility Profile based

• UE is only moved to a 5G anchor carrier if:
upon UE Capability
• the end-user has purchased a 5G subscription,
Mobility Profile based AND
upon SPID
• the device is 5G capable
26 18/03/2025 © Nokia 2018
For internal use
 Access from specific 4G Carrier (IV)

• When using Mobility Profiles, the eNB relies upon receiving information from the MME
during the Initial Context Setup procedure
• The MME is able to provide UE capability information and SPID information
• The relevant section is checked depending upon the strategy

S1AP: INITIAL CONTEXT SETUP REQUEST

S1AP: INITIAL CONTEXT SETUP REQUEST

27 18/03/2025 © Nokia 2018 RAT/Frequency Selection

For internal use Priority (RFSP) Index for NGAP
case
Access from specific 4G Carrier (V)

• Focus can be placed upon Idle Mode features to keep design relatively simple
• Requirement to evaluate features:
• LTE490 Subscriber profile ID selective neighbor cell list
• LTE487 Idle Mode Load Balancing
• LTE1677 Idle Mode Mobility Balancing Extensions
• LTE2166 Dedicated Idle Mode Mobility Priorities
• LTE2050 Load Triggered Idle Mode Load Balancing
• LTE2051 Measurement Based Idle Mode Load Balancing
• Requirement to configure new parameter objects:
• MODPR
• MOPR
• MOIMP (parented by MOPR)

28 18/03/2025 © Nokia 2018

For internal use
 MOIMP
Access from specific 4G Carrier (V)
Create
moimpId
instances for cdmaHrpdBdClL - cdmaHrpdBdCl
each LTE cdmaHrpdBdClL - idleLBHrpdCelResPrio
carrier cdmaHrpdBdClL - idleLBHrpdCelResWeight
cdmaRttBdClL - cdmaRttBdCl
cdmaRttBdClL - idleLBRttCelResPrio
cdmaRttBdClL - idleLBRttCelResWeight
• The MOIMP object allows Idle Mode Load Balancing dlCarFrqEutL - dlCarFrqEut
dlCarFrqEutL - idleLBEutCelResPrio
weights to be configured for specific 4G carriers and dlCarFrqEutL - idleLBEutCelResPrio2CC
specific mobility profiles dlCarFrqEutL - idleLBEutCelResPrio3CC
dlCarFrqEutL - idleLBEutCelResPrio4CC
• Requirement to configure and verify the Idle Mode Load dlCarFrqEutL - idleLBEutCelResPrio5CC
dlCarFrqEutL - idleLBEutCelResPrio6CC
Balancing feature dlCarFrqEutL - idleLBEutCelResPrio7CC
dlCarFrqEutL - idleLBEutCelResWeight
• Requirement to verify that UE specific priorities are dlCarFrqEutL - idleLBEutCelResWeight2CC
dlCarFrqEutL - idleLBEutCelResWeight3CC
applied throughout the duration of LNCEL - T320 (5 min dlCarFrqEutL - idleLBEutCelResWeight4CC
to 3 hrs) dlCarFrqEutL - idleLBEutCelResWeight5CC
dlCarFrqEutL - idleLBEutCelResWeight6CC
dlCarFrqEutL - idleLBEutCelResWeight7CC
geranCarFrqBd - geranBandInd
geranCarFrqBd - idleLBGeranCelResPrio
Allocate weight of 100 to LTE geranCarFrqBd - idleLBGeranCelResWeight
carriers which provide access to geranCarFrqIdleModeL
5G utrFddCarFrqL - idleLBUtraFddCelResWeight
utrFddCarFrqL - idleLBUtranFddCelResPrio
Do not populate weights for utrFddCarFrqL - utrFddCarFrq
other LTE carriers utrTddCarFrqL - idleLBUtranTddCelResPrio
29 18/03/2025 © Nokia 2018 utrTddCarFrqL - idleLBUtraTddCelResWeight
For internal use utrTddCarFrqL - utrTddCarFrq
Admission of 5G Subscribers

30 18/03/2025 © Nokia 2017

For Internal Use
Background

• The 4G BTS is required to determine which UE are eligible

to have a 5G Secondary Cell Group
• The checks completed are:
• has the UE been allocated a QCI which is eligible for
5G?
• has the UE been allocated an ARP which is eligible for
5G?
• does the Handover Restriction List from the MME
indicate that the UE is eligible for 5G?

• If the operator strategy specifies that only certain

subscribers are allowed to use 5G, e.g. those subscribers
that have paid an increased monthly fee, then the 4G BTS
must use at least one of the above checks to differentiate
the UE
31 18/03/2025 © Nokia 2018
• All 3 checks rely upon HSS configuration
For internal use
QCI Check
LNBTS
• non-GBR QCI tables include the
lteNrDualConnectSupport flag qciTab6/7/8/9/Operator
• 5G subscribers could be allocated a different QCI relative to lteNrDualConnectSupport
all other subscribers nrPdcpProfIdx
startArpEnDc
• The lteNrDualConnectSupport flag can be used to stopArpEnDc
enable 5G only for that specific QCI

ARP Check
• non-GBR QCI tables include startArpEnDc and stopArpEnDc parameters
• 5G subscribers could be allocated a different ARP relative to all other subscribers
• The startArpEnDc and stopArpEnDc parameters can be used to enable 5G
only for that specific ARP

32 18/03/2025 © Nokia 2018

For internal use
Handover Restriction List Check

• The ‘Handover Restriction List’ provided by the MME within the S1AP: INITIAL
CONTEXT SETUP REQUEST, indicates whether or not the UE is permitted to have
access to 5G
• Initial testing should verify that the MME provides this field
• This represents the simplest solution because it is not necessary to configure
separate QCI nor ARP for the 5G subscribers

Field within ‘Handover Restriction List’ belonging to S1AP: INITIAL CONTEXT SETUP REQUEST

33 18/03/2025 © Nokia 2018

For internal use
NSA Activation

34 18/03/2025 © Nokia 2017

For Internal Use
Feature Activation

• The primary feature activation switch for EN-DC at the 4G BTS is

actLteNrDualConnectivity
• online parameter changes permitted

Parameter Object Range Default

actLteNrDualConnectivit
LNBTS False (0), True (1) False (0)
y

• If feature is enabled then

• actSatBackhaul must be set to 'false’
• tLteNrDualConnectPrep must be configured
• an NRDCDPR instance must be created
• if lteNrDualConnectSupport is set to 'EN-DC’ for a specific QCI then
nrPdcpProfIdx must be configured

35 18/03/2025 © Nokia 2018

For internal use
LNADJGNB Object

• The LNADJGNB object defines the neighbour relationship for a specific 5G BTS
• allows the X2 connection to be setup between the 4G and 5G BTS
• As a minimum, an instance of the object should be created for the co-sited 5G
BTS
• The requirement for additional LNADJGNB
LNADJGNB depends upon the 4G /5G lnAdjGnbId
operating bands and the site density adjGnbId
• An example strategy could be to adjGnbIdLength
BTS Identity administrativeState
create LNADJGNB instances for at
least the first tier of neighbouring 5G cPlaneIpAddr
BTS mcc
BTS IP mnc
Address
mncLength
x2ToGnbLinkStatus

36 18/03/2025 © Nokia 2018

Output parameter
For internal use
 LNRELGNBCELL Object

• The LNRELGNBCELL object points towards 5G cells which can be added as 5G

Secondary Cell Group (SCG) cells
• The minimum requirement is to add the co-sited co-sectored 5G cell
• If separate antenna are used for 4G and 5G then azimuths may be different so it
is recommended to also add co-sited non-co-sectored 5G cells
• For interference limited deployments, it
may also be necessary to create objects LNRELGNBCELL
for 5G cells belonging to neighbouring EN-DC lnRelGnbCellId
BTS enabled gnbIdLength
• Cell Identity lteNrDualConnectAllowed
defaultLnRelGnbCellId should be
nrCellId
configured as the co-sited co-sectored
mcc
5G cell
LNCEL mnc
mncLength
defaultLnRelGnbCellId
nrStatus

37 18/03/2025 © Nokia 2018

For internal use
 PDCP Profile
• It is necessary to create a new PDCP profile for 5G
• uses identity 1001
• configured to use the 18 bit Sequence Number

Parameter Object Range Default LNBTS

pdcpProfileI
LNBTS 1001 1001 pdcpProf1001
d
pdcpProfileId
snSizeDl LNBTS 18 bits (3) 18 bits (3) snSizeDl
snSizeUl LNBTS 18 bits (3) 18 bits (3) snSizeUl
statusRepReq
Candidate for no Status Report (0) tDiscard
optimisation eNB Status Report (1) eNB and
statusRepRe
LNBTS UE Status Report (2) UE Status
q qciTab6/7/8/9/Operator
eNB and UE Status Report Report (3)
(3) lteNrDualConnectSupport
nrPdcpProfIdx
tDiscard LNBTS 10 to 1500 ms, infinity 300 ms
Parameter Object Range Default startArpEnDc
stopArpEnDc
nrPdcpProfId
LNBTS 1001 1001
x
38 18/03/2025 © Nokia 2018
For internal use
QCI Profile

• EUTRA – NR Dual Connectivity (EN-DC) can be enabled/disabled for each non-GBR

QCI
• In each case, EN-DC can be enabled for a specific set of ARP values
• Allows EN-DC utilisation to be managed using the subscriber profile in the HSS
• Simplistic solution is to enable for all ARP values belonging the relevant QCI

LNBTS
qciTab6/7/8/9/Operator
Parameter Object Range Default
lteNrDualConnectSupport
lteNrDualConnectSupp Disabled nrPdcpProfIdx
LNBTS Disabled (0), EN-DC (1)
ort (0) startArpEnDc
startArpEnDc LNBTS 1 to 15 1 stopArpEnDc

stopArpEnDc LNBTS 1 to 15 15

39 18/03/2025 © Nokia 2018

For internal use
Data Volume Threshold

• This data volume threshold determines the trigger for setting up an EN-DC connection
• By default,
• if a UE transfers less than 1024 kB then the connection uses only 4G
• If a UE transfers more than 1024 kB then the 5G Secondary Cell Group is added
• General principle is that the reconfiguration for 5G Secondary Cell addition is only
justified if the UE is transferring a larger volume of data
• The threshold of 1024 kB will mean that Smart Phone background traffic will not use
5G
• Threshold may be reduced if there is a requirement to increase utilisation of 5G

Parameter Object Range Default NRDCDPR

1024 nrDcPrId
dataVolThreshold NRDCDPR 1 to 65 536 kBytes carrierFreqNrCell
kBytes
dataVolThreshold
enDCpMaxEUTRApowerOffset
enDCpMaxNRpowerOffset
40 18/03/2025 © Nokia 2018
For internal use
Timers

• tLteNrDualConnectPrep is used as a supervision timer for signalling procedures

between the Master eNB and the Secondary gNB, e.g. SgNB Addition, Modification and
Release
• corresponds to 3GPP parameter TDCPrep when used during the Addition
procedure
• tS1eRABModInd defines a supervision timer for the S1AP: E-RAB Modification
Indication procedure
• tDataFwdX2gNB defines a timer to restrict the time that the MeNB receives or
transmits data across the X2 after the E-RAB Modification procedure
LNBTS
Parameter Object Range Default
actLteNrDualConnectivity
tLteNrDualConnectPre actDynTrigLteNrDualConnectivity
LNBTS 10 to 10000 ms 500 ms
p tLteNrDualConnectPrep
tS1eRABModInd
tS1eRABModInd LNBTS 10 to 5000 ms 500 ms tDataFwdX2gNB
tDataFwdX2gNB LNBTS 10 to 2000 ms 10 ms

41 18/03/2025 © Nokia 2018

For internal use
Power Control

42 18/03/2025 © Nokia 2017

For Internal Use
Single Uplink Transmission
• In general, it is mandatory for a UE to be capable of transmitting simultaneously on both
4G and 5G
• However, some exceptions are permitted for specific band combinations to avoid
potential issues with inter-modulation products
• inter-modulation products can fall within the UE receive band
• It is optional for UE to support simultaneous 4G and 5G transmission for these exceptions
• depends upon UE capability to suppress intermodulation products
These parameters are provided
for each band combination

Exception UE indicates whether or not it only

43 18/03/2025 © Nokia 2018 permitted supports single uplink transmission
For internal use for each band combination
 UE Power Classes Frequency Range
• 1
Only Power Class 3 is currently specified within
Frequency Range 1 for inter-band EN-DC
• corresponds to 23 dBm conducted power
at antenna connector
• Power Classes 1 to 4 specified for Frequency
Range 2
• specified in terms of radiated power
•power class 1 intended for Fixed Wireless
Frequency Range
Access2

TRP =
Total
Radiated
Power

44 18/03/2025 © Nokia 2018

For internal use
Power Sharing (I) Power Sharing for EN-DC with FR1

4G
• When using Non-standalone operation between 4G 23 dBm
and: 5G FR1
• 5G Frequency Range 1, the nominal UE transmit
power is shared between the two technologies
Dedicated Power for EN-DC with FR2
• 5G Frequency Range 2, there is a dedicated UE
transmit power for each technology 23 dBm 4G
• It is optional for UE to support dynamic power sharing
between 4G and 5G Frequency Range 1 23 dBm 5G FR2

4G
5G
Master Node
Secondary
(MN) UE transmit
Node (SN)
power

45 18/03/2025 © Nokia 2018 UE indicates support for

For internal use dynamic power sharing
Power Sharing (II)

• The UE is configured with:

• p-MaxEUTRA for the maximum power on 4G
• p-NR for the maximum power on 5G
• The UE applies the 4G and 5G power control equations to calculate the transmit
power requirement on each technology

• If the sum of the two transmit powers is less than the configured maximum power
then the UE transmits at the calculated powers

• If the UE supports dynamic power sharing and the sum of the two transmit powers is
greater than the configured maximum power, then the 5G transmit power is reduced
• If the power reduction requirement is greater than Xscale then the UE can decide to
not transmit on 5G

Currently
46 18/03/2025 © Nokia 2018
not
For internal use
supported
Power Sharing – Static Power Allocation (I) Currently
not
supported
• If the UE does not support dynamic power sharing then the UE expects to be configured
with the tdm-PatternConfig-r15 parameter
• this parameter reserves uplink subframes for 4G. The UE does not expect to
receive uplink resource allocations for 5G during the uplink subframes defined by
tdm-PatternConfig-r15
• Alternatively, the UE can be configured with maximum 4G and 5G maximum transmit
powers such that the sum of the two powers does not exceed the total UE transmit
power capability
• provides a static power allocation between 4G and 5G
• The ulPowerAllocatingNode parameter determines the Base Station which determines
the UE transmit power limits
• default value indicates that
Parameter power limits originate
Object Range from 4G BTS Default
ulPowerAllocatingNode NRCELL MeNB (0), SgNB (1) MeNB (0)

47 18/03/2025 © Nokia 2018

For internal use
 Power Sharing – Static Power Allocation (II)

• The 4G and 5G power limits are calculated as:

• P_MaxEUTRA = min ( UE_MRDC_PowerClass – enDCpMaxEUTRApowerOffset ;
pMaxOwnCell )
• P_MaxNR _FR1= UE_MRDC_PowerClass – enDCpMaxNRpowerOffset

• The values allocated to the power offsets must be co- NRDCDPR

ordinated to ensure that the UE total power is not enDCpMaxEUTRApowerOffset
exceeded enDCpMaxNRpowerOffset

• For example, they could be set to 3 dB for each

technology so the UE can transmit up to half of the total
Power Offset 1 Power Offset 2
power on 4G/5G
Parameter Object Range Default
1 dB 7 dB
enDCpMaxEUTRApowerOff
NRDCPR 0 to 7 dB - 2 dB >= 5 dB
set
3 or 4 dB > =3 dB
enDCpMaxNRpowerOffset NRDCPR 0 to 7 dB -
5 or 6 dB >= 2 dB
48 18/03/2025 © Nokia 2018
7 dB >= 1 dB
For internal use
Measurement Based SCell
Addition

49 18/03/2025 © Nokia 2017

For Internal Use
 Feature Activation

• In general, it is recommended to enable LTE4193: ‘Dynamic Trigger for LTE-NR DC

Option 3X’
• Blind trigger (LTE4193 disabled) can be used if faster 5G SCell addition is required and
4G/5G coverage areas are similar
• Feature is enabled using actDynTrigLteNrDualConnectivity
• online parameter changes permitted

Parameter Object Range Default

actDynTrigLteNrDualConnecti
LNBTS False (0), True (1) False (0)
vity

• If feature is enabled at a TDD cell then:

• measGapPattern must be set to ‘gap0’

40ms periodicity
with 6ms
50 18/03/2025 © Nokia 2018
For internal use
duration
Beam Level and Cell Level Measurements

• LTE4193 ‘Dynamic Trigger for LTE-NR DC Option 3X’ relies upon Measurement Reporting
Event B1
• UE physically measures a beam on 5G, i.e. the UE measures an SS/PBCH Block
transmitted by a specific beam
• The UE measures multiple beams if they are received
• Measurement Reporting Events, e.g. Event B1, are triggered by Cell Level
measurements rather than Beam Level measurements
• UE is responsible for deriving Cell Level measurement from one or more Beam Level
• Current implementation is
measurements
hardcoded E.g. maximum of 2 beams averaged
• UE is instructed to set Cell RSRP threshold
Level measurement equal to
strongest Beam Level
measurement

51 18/03/2025 © Nokia 2018

For internal use
Measurement Configuration & Object

• Event B1 requires the 4G BTS to configure:

• Measurement Configuration
• defines the parameters associated with Event B1
• Measurement Object
• defines the 5G carrier to be measured & the time windows for measurement
• Quantity Configuration
• defines the Layer 3 filtering coefficients
• Measurement Identity
• links the Measurement Object to the Measurement Configuration

Quantity Measuremen Measuremen Measureme

Configuration t Object t Identity nt
Configuratio
n
52 18/03/2025 © Nokia 2018
For internal use
 Measurement Configuration (I)
• This NRDCDPR object includes the nrDcMeasConfig parameter structure which provides
the parameters used configure Event B1
• Event B1 relies only upon target cell measurements, i.e. NR measurements:
NRDCDPR
Measneigh + Offsetfreq + Offsetcell – Hyst > Threshold nrDcMeasConfig
b1ThresholdNrRsrp
b1ThresholdNrRsrq
• The b1ThresholdNrRsrp and b1ThresholdNrRsrq parameters b1TimeToTriggerRsrp
b1TimeToTriggerRsrq
define the Threshold when using RSRP or RSRQ respectively b1TriggerQuantity
hysB1ThresholdRsrp
hysB1ThresholdRsrq
b1ThresholdNrRsrp
quantityConfigId
or
Applicable to ssbDuration
b1ThresholdNrRsrq
Measurement ssbOffset
NR Cell ssbPeriodicity
Object
ssbSubcarrierSpacing

LTE Cell

53 18/03/2025 © Nokia 2018

For internal use
 Measurement Configuration (II)
• b1TriggerQuantity defines the triggering quantity for event B1 – either RSRP or RSRQ
• Recommended to use RSRP as an initial quantity
• RSRQ may be used as an optimisation if 5G cells found to experience interference

Parameter Object Range Default

b1TriggerQuantity NRDCDPR RSRP, RSRQ -

• b1ThresholdNrRsrp and b1ThresholdNrRsrq define the thresholds used to add the 5G

secondary cell
• Suggested to use a relaxed RSRP threshold initially to allow easy addition of the 5G cell
Parameter Object Range Default
b1ThresholdNrRsrp NRDCDPR -140 to -43 dBm -
b1ThresholdNrRsrq NRDCDPR -20 to -3 dB -

54 18/03/2025 © Nokia 2018

For internal use
Measurement Configuration (III)

• Hysteresis is used to prevent ping-pong between the event triggering and not
triggering
• Time-to-trigger avoids event triggering due to short term RF spikes
• Default values can be adopted

Parameter Object Range Default

hysB1ThresholdRsrp NRDCDPR 0 to 15 dB 2 dB
hysB1ThresholdRsrq NRDCDPR 0 to 15 dB 2 dB
b1TimeToTriggerRsrp NRDCDPR 0 to 5120 ms 256 ms
b1TimeToTriggerRsrq NRDCDPR 0 to 5120 ms 256 ms

55 18/03/2025 © Nokia 2018

For internal use
 Measurement Object (I) NRDCDPR
nrDcPrId nrDcMeasConfig
carrierFreqNrCell
• carrierFreqNrCell identifies the Global dataVolThreshold
b1ThresholdNrRsrp
b1ThresholdNrRsrq
Synchronisation Channel Number (GSCN) enDCpMaxEUTRApowerOffset
b1TimeToTriggerRsrp
enDCpMaxNRpowerOffset
of the target 5G carrier b1TimeToTriggerRsrq
dynTriggerLteNrDcConfList b1TriggerQuantity
• Corresponds to the center frequency of hysB1ThresholdRsrp
lcrId hysB1ThresholdRsrq
the SS/PBCH Block method quantityConfigId
ssbDuration
nrDcQuantityConfig ssbOffset
Parameter Object Range Default ssbPeriodicity
quantityConfigId
NRDCDP filterCoefficientRsrp ssbSubcarrierSpacing
carrierFreqNrCell 0 to 3279167 -
R filterCoefficientRsrq

• The quantityConfigId defines a pointer towards the parameter structure which

defines the filter coefficients for the 5G measurements

Parameter Object Range Default

quantityConfigId NRDCDPR 0, 1 -

56 18/03/2025 © Nokia 2018

For internal use
GSCN -> NR-ARFCN

• Consider an SS/PBCH which has been

allocated a GSCN = 7860
• This value tells us that the SS/PBCH is
within the range 3000 to 24250 MHz

• We then calculate the value of 'N' as GSCN - 7499 = 7860 - 7499 = 361
• We can then calculate the GSCN frequency in MHz using 3000 + N * 1.44 =
3519.84 MHz
• Then to obtain the NR-ARFCN:
NR-ARFCN = [(Freq - Freq_off) / delta_F_global ] + N_off NR-ARFCN
= [(3519.84 - 3000) / 0.015] + 600 000
= 634 656

57 18/03/2025 © Nokia 2018

For internal use
NR Measurements from 4G

• The UE is provided with 2 sets of timing information:

• Measurement Gap timing (Measurement Gaps are always configured)
• SS/PBCH timing (also known as SS/PBCH Measurement Timing Configuration (SMTC))
• Impact upon 4G data transfer determined by Measurement Gap duration and repetition
period
• current implementation uses Measurement Gap Pattern 0

Transceiver Transceiver
Re-tuning Re-tuning

SMTC Duration
SS/PBCH

4G Data Transfer 4G Data Transfer

58 18/03/2025 © Nokia 2018 Measurement Gap

For internal use
4G Measurement Gap Patterns

• Measurement Gap Pattern lengths of

3, 4 or 6 ms
• 2, 3 or 5 ms of measurement
time for Frequency Range 1
• 2.5, 3.5, 5.5 ms of measurement
time for Frequency Range 2
• Repetition periods range from 20 ms
to 160 ms

• 5G19 implementation uses Gap

Pattern 0

59 18/03/2025 © Nokia 2018

For internal use
 Measurement Object (II)
• The UE is provided with information to help it measure the 5G carrier
• ssbSubcarrierSpacing needs to be aligned with the SS/PBCH subcarrier spacing
configured at the gNB
• ssbDuration provides a time window for the UE to measure the 5G carrier using the
SS/PBCH Blocks
• This time window needs to be sufficiently long to capture all SS/PBCH Blocks for all beams
• it is necessary to understand the SS/PBCH Block transmission timings on 5G (see next
slide)
SS/PBCH Blocks measurement window defined by ssbDuration
• parameters within the gNB databuild need to be checked

NRCELLGRP – ssBurstSetPeriod (from gNB databuild)

Parameter Object Range Default

60 18/03/2025 © Nokia 2018
ssbSubcarrierSpacin
For internal use
NRDCDPR 15, 30, 120, 240 kHz Set equal to NRCELL - ssbScs
g
SS/PBCH Block Timing

• Figures below assume that all SS/PBCH Blocks are transmitted

• requirement to check NRCELLGRP – numberOfTransmittedSsBlocks parameter in
gNB to determine actual number of beams which transmitted

<= 3 GHz
Subcarrie Slot >3 GHz & <= 6 GHz > 6 GHz
(up to 4
r Spacing Duration (up to 8 beams) (up to 64 beams)
beams)
2, 8, 16, 22 2, 8, 16, 22, 30, 36, 44, 50
15 kHz 1 ms 2 ms window 4 ms window Symbol numbers -
4, 8, 16, 20 4, 8, 16, 20, 32, 36, 44, 48
where SS/PBCH Block
30 kHz 0.5 ms 1 ms window 2 ms window starts -

2, 8, 16, 22 2, 8, 16, 22, 30, 36, 44, 50

30 kHz 0.5 ms 1 ms window 2 ms window -

4, 8, 16, 20, 32, 36, 44, 48, 60, 64, 72, 76, 88, 92, 100, 104, 144, 148,
156, 160, 172, 176, 184, 188, 200, 204, 212, 216, 228, 232, 240, 244,
284, 288, 296, 300, 312, 316, 324, 328, 340, 344, 352, 356, 368, 372,
120 kHz 0.125 ms - - 380, 384, 424, 428, 436, 440, 452, 456, 464, 468, 480, 484, 492, 496,
508, 512, 520, 524
5 ms window
8, 12, 16, 20, 32, 36, 40, 44, 64, 68, 72, 76, 88, 92, 96, 100, 120, 124,
61 18/03/2025 © Nokia 2018 128, 132, 144, 148, 152, 156, 176, 180, 184, 188, 200, 204, 208, 212,
288, 292, 296, 300, 312, 316, 320, 324, 344, 348, 352, 356, 368, 372,
240
For kHz
internal use0.0625 ms - - 376, 380, 400, 404, 408, 412, 424, 428, 432, 436, 456, 460, 464, 468,
480, 484, 488, 492
Measurement Object (III)

• ssbDuration can be aligned with the window durations shown in the previous slide

Paramet
Object Range Default
er
ssbDuratio
NRDCDPR 1, 2, 3, 4 subframes -
n

3GPP also supports 5

subframes to cater for 64
beams in FR2

• ssbDuration does not determine the impact upon 4G data transfer

• Measurement Gap duration determines impact upon 4G data transfer

62 18/03/2025 © Nokia 2018

For internal use
 Measurement Object (IV)
• UE is always configured with Measurement Gaps when using Event B1 for NR
measurements
• only gap pattern 0 is currently supported (40ms periodicity with 6ms duration)
• UE may require additional measurement time to allow for transceiver switching
• dependant upon UE capability
• Transceiver switching in:
• Frequency Range 1 assumed to require 0.5 ms per switch (1 ms in total)
• Frequency Range 2 assumed to require 0.25 ms per switch (0.5 ms in total)

Transceiver 2 ms Transceiver
Switch Switch
Example: 30 kHz with 8 beams

Measurement Gap = 6
ms
63 18/03/2025 © Nokia 2018
For internal use
 Measurement Object (V)

• ssbPeriodicity can be set equal to the SS/PBCH period configured at the gNB
• check NRCELLGRP - ssBurstSetPeriod parameter
• It could also be set larger than the value configured at the gNB but this may increase
measurement delays

Parameter Object Range Default

ssbPeriodicity NRDCDPR 5, 10, 20, 40, 80, 160 subframes -

SS/PBCH Blocks measurement window defined by ssbDuration

NRCELLGRP – ssBurstSetPeriod (from gNB databuild)

64 18/03/2025 © Nokia 2018
For internal use
 Measurement Object (VI)

• ssbOffset needs to ensure that the start of the measurement window captures the
first SS/PBCH transmission within a burst
• Range depends upon the ssbPeriodicity configuration
• This can be set to 0 when the LTE and NR radio frame timing is aligned

Parameter Object Range Default

ssbOffset NRDCDPR 0 to 79 0

SS/PBCH Blocks measurement window defined by ssbDuration

SFN = 0
of 4G ssbOffset
Cell
65 18/03/2025 © Nokia 2018
For internal use
 ssbOffset Configurations (I)

• For most configurations, 4G and 5G

SFN are time synchronised and the
SS/PBCH appear at the start of the
5G radio frames
• In these cases ssbOffset can be
set to 0

SS/PBCH Blocks measurement window defined by ssbDuration

SFN = 0 ssbOffset = 0
of 4G
Cell
66 18/03/2025 © Nokia 2018
For internal use
 lteToNrFrameShift = 0 ms
ssbOffset Configurations (II) LTE Uplink/Downlink Configuration 2 (1DL:1SP:1UL:2DL)
LTE Special Subframe Configuration 6 (9DwPTS:3GP:2UpPTS)
Sp Sp
DL (9,3,2)
UL DL DL DL (9,3,2)
UL DL DL

• If frameStructureType = ‘tdLte’ and

5G equivalent when using 30 kHz
lteToNrFrameShift = 3 ms, then the start DL DL DL Sp UL UL DL DL DL DL subcarrier spacing
of the 5G radio frame is delayed by 3 ms (4,6,4)

• In this case, ssbOffset should be set to 3

Pattern 1
3 DL Slots
Pattern 2
4 DL Slots
4 DL Symbols
ms so the UE searches for the SS/PBCH at 4 UL Symbols
2 UL Slots 1 ms duration
the correct time
lteToNrFrameShift = 3 ms
SS/PBCH Blocks LTE Uplink/Downlink Configuration 2 (1DL:1SP:1UL:2DL)
LTE Special Subframe Configuration 6 (9DwPTS:3GP:2UpPTS)
Sp Sp
DL (9,3,2)
UL DL DL DL (9,3,2)
UL DL DL

SFN = 0 3 ms delay to start

DL DL DL DL DL DL DL Sp UL UL 5G equivalent
of 5G frame
of 4G ssbOffset = 3 ms when using 30 kHz
Pattern 1 (4,6,4) subcarrier spacing
Cell 7 DL Slots
4 DL Symbols
4 UL Symbols
67 18/03/2025 © Nokia 2018 2 UL Slots
For internal use 1 ms
duration
 Measurement Gap Timing Advance (information only)

• If using 64 beams in Frequency Range 2, then the SMTC duration needs to be 5 ms

• After accounting for the transceiver re-tuning delay, this requires the 6 ms Measurement
Gap duration
• The Gap Offset has a step size of 1 ms so either the first SS/PBCH overlap with the
transceiver re-tuning, or the last SS/PBCH overlap with the SS/PBCH re-tuning
• Thus 3GPP has introduced a 0.5 ms Measurement Gap Timing Advance which allows the
Measurement Gap to be brought forward by 0.5 ms
1 ms step
size SMTC Duration

64 SS/PBCH

SMTC Duration

64 SS/PBCH

68 18/03/2025 © Nokia 2018

For internal use
 Quantity Configuration (I) NRDCDPR
nrDcPrId nrDcMeasConfig
carrierFreqNrCell
b1ThresholdNrRsrp
• The Quantity Configuration defines the dataVolThreshold
b1ThresholdNrRsrq
enDCpMaxEUTRApowerOffset
filter coefficients used for Layer 3 filtering enDCpMaxNRpowerOffset
b1TimeToTriggerRsrp
b1TimeToTriggerRsrq
• The object identity (0 or 1) should be set dynTriggerLteNrDcConfList b1TriggerQuantity
equal to the pointer within the hysB1ThresholdRsrp
lcrId hysB1ThresholdRsrq
nrDcMeasConfig, i.e. quantityConfigId method quantityConfigId
ssbDuration
• Default values of ‘4’ can be used for the nrDcQuantityConfig ssbOffset
filter coefficients quantityConfigId ssbPeriodicity
filterCoefficientRsrp ssbSubcarrierSpacing
filterCoefficientRsrq

Parameter Object Range Default

quantityConfigId NRDCDPR 0, 1 0
filterCoefficientRsrp NRDCDPR 0 to 19 4
filterCoefficientRsrq NRDCDPR 0 to 19 4

69 18/03/2025 © Nokia 2018

For internal use
LTE4575: Blind Carrier
Aggregation with LTE-NR DC
Option 3x

70 18/03/2025 © Nokia 2017

Customer Confidential
Feature Configuration

• Carrier Aggregation can be enabled for UE

which are configured with the NR PDCP within
the 4G Master Node
• Feature enabled using
actCAggrLteNrDualConnectivity parameter
• Candidate LTE cells for CA can be listed using
cAggrLteNrDcCellList
• special value of ‘-1’ indicates that all cells
are candidates
• Requirement to check supported band
combinations
Parameter Object Range Default
actCAggrLteNrDualConnectivity LNBTS Disabled (0), blind_CA_LTE_NR (1) Disabled (0)
cAggrLteNrDcCellList NRDCDPR 0 to 255 (-1 special value) -

71 18/03/2025 © Nokia 2018

For internal use
72 18/03/2025 © Nokia 2017
For Internal Use