5GC000738 Multiple PLMN ID Support

5GC001840 5G RAN Sharing with multiple PLMNs NSA 3x and single PLMN SA

Sprint 5G19B deep dive

May 2020

The functionality provided in these charts is for information only and does not imply a committed status. Feature
content and delivery is subject to a separate commercial agreement between Sprint and Nokia

1 © Nokia 2020 Customer Confidential

5G RAN Sharing

2 Customer Confidential
 <chapter: introduction>

5G RAN Sharing

Introduction

3 © Nokia 2020 Customer Confidential

Introduction
Overview on Network Sharing solutions
PASSIVE SHARING ACTIVE SHARING (RAN SHARING) FULL SHARING

INDEPENDENT SITE
SITE SHARING MORAN MOCN NATIONAL ROAMING

▪ Transport, power supplies, Benefits from site sharing, plus: Whole network is shared
towers may be shared ▪ gNB is shared (RAN Sharing) Driven by:
▪ RAN is not shared ▪ Frequency spectrum can be ▪ Filling coverage gaps
shared ▪ Financial investments decision
▪ A way to access new sites ▪ Core is not shared ▪ Lack of spectrum
▪ Cost savings in rental sites ▪ OPEX reduction (energy, site
maintenance etc.)

CAPEX REDUCTION

MORAN – Multi-Operator Radio Access Network; MOCN – Multi-Operator Core Network → more details on next slides

4 Customer Confidential
Introduction
RAN Sharing introduction

• RAN Sharing is a solution that allows multiple Operators to share the same resources of the Radio
Access Network
• Sharing of the radio access network between different operators may be worth of considering in the
following contexts:
- cost related to investments (new HW and SW, building new sites or modernization of existing ones) are divided
between the participating Operators
- spectrum aspects → more spectrum in a shared network which gives the operator competitive advantage over its
rivals in a perpetual race for offering higher throughputs to the end users
• 5G RAN can be shared with the help of 2 solutions (known already from 2G, 3G and LTE) namely:
- Multi-Operator Core Network (MOCN) → specified by the 3GPP
- Multi-Operator Radio Access Network (MORAN) → Nokia proprietary solution

Example of MOCN

Core Network

5 Customer Confidential
Core Network
Introduction
RAN Sharing introduction

• Multi-Operator Radio Access Network (MORAN):

- each Operator has its own Core Network nodes while site equipment is shared between the Operators
- each Operator has its own dedicated cells and dedicated frequencies

• Multi-Operator Core Network (MOCN):

- In MOCN Operators have its own Core Network, site equipment is shared however, contrary to MORAN, also cells
are shared i.e. cell resources are available for users of both Operators

6
Introduction
RAN Sharing introduction

• One of the most important differentiator between MOCN and MORAN is spectrum allocation
• In MORAN spectrum is not shared between the Operators (the cell is fully dedicated to only one PLMN)
- NR Frequency carriers of each MNO may have the same or different bandwidth

PLMN 1 PLMN 2
frequency

• In MOCN spectrum is shared between participating operators

- Without dedicated features, common carrier is fully pooled → it means that there are no reserved resources for the
operators within the common carrier

PLMN 1, PLMN 2
frequency

7 Customer Confidential
Introduction
5GC000738 overview

• 5GC000738 Multiple PLMN ID Support feature (from 5G19A release) introduces RAN Sharing
concept
• Up to 2 Operators, identified by the unique PLMN IDs, can share the gNB with 5GC000738
• Feature is supported in a Classical deployment of 3.X Non-Standalone Architecture
• 5GC000738 introduces support for both MOCN and MORAN solutions
- Moreover both solution can be deployed on the same gNB → different cells can have different RAN Sharing
solution configured

EPC1
LTE Op1

LTE Op2
EPC2
8 Customer Confidential
Introduction
5GC001840 overview

• 5GC001840 5G RAN Sharing with multiple PLMNs NSA 3x and single PLMN SA is an enhancement
aiming at more flexibility in 5G deployments
• This feature, introduced in 5G19B, enhances 5GC000738 by support of SA (Standalone Access)
• With this feature following cell sharing combinations are supported:
- NSA-only mode (up to two PLMNs per cell – introduced by 5GC000738)
- SA-only mode (single PLMN per cell and single PLMN per gNB) → can be used in a MORAN scenario
- Mixed NSA and SA mode (same limitation of PLMNs per cell for NSA and SA as above – totally 2 PLMNs per cell)

EPC1
LTE Op1

5G Core
9 Customer Confidential
Introduction
Before & after 5GC000738

Before After

• Network Sharing was not supported • Active Network sharing is supported

• Each Operator must build and maintain • Operators can share gNB according to
own 5G RAN which requires huge MOCN and MORAN schemes
investments • MOCN enables full resources sharing
• MORAN enables gNB sharing while cells
are fully dedicated only to one MNO

10 Customer Confidential
Introduction
Before & after 5GC001840

Before After

• Network Sharing was already supported • Active Network sharing is supported

but only for the NSA operators with even higher flexibility in 5G
deployment scenarios
• RAN can be shared by the NSA & SA
Operators in parallel

11 Customer Confidential
Introduction
Benefits & Gains

• Introduction of the RAN Sharing in 5G brings the following benefits:

- run 5G service for MNO in case of lack or limited spectrum resources
- high CAPEX/OPEX savings compared to the simple “site sharing” network scenario
- lower initial investment requirement for a roll-out of a new network and services
- high flexibility in selection of deployment as both MOCN and MORAN as well as NSA and SA configurations are
supported

12 Customer Confidential
 4G MORAN
Introduction 5G MORAN

Deployment scenarios (1/5)

NR gNB configuration EPC EPC

Global gNB ID: PLMN1
Op-1 Op-2
Cell Operator-1: PLMN1
Cell Operator-2: PLMN1, PLMN2

S1-C S1-U S1-U

LTE eNB configuration
Global gNB ID: PLMN1 (primary)
Cell Operator-1: PLMN1
Cell Operator-2: PLMN1 (reserved), PLMN2

LTE eNB X2 NR en-gNB

PLMN-1, PLMN-2 PLMN-1, PLMN-2

4G MORAN 5G MORAN

5G
SIB1 (LTE)
Operator-1: PLMN1, TAC1, ECGI-11 5G
Operator-2: PLMN1, PLMN2, TAC2, ECGI-12 4G
4G

13 Customer Confidential
 4G MOCN,
Introduction 5G MOCN

Deployment scenarios (2/5)

NR gNB configuration EPC EPC

Global gNB ID: PLMN1
Op-1 Op-2
Cell Operator-1 & 2: PLMN1, PLMN2

LTE eNB configuration S1-C S1-U S1-U

Global gNB ID: PLMN1 (primary)
Cell Operator-1 & 2: PLMN1, PLMN2 S1-U
S1-C

LTE eNB X2 NR en-gNB

PLMN-1, PLMN-2 PLMN-1, PLMN-2

4G MOCN 5G MOCN

SIB1 (LTE)
Operator-1: PLMN1, PLMN2, TAC1, ECGI-11 5G
Operator-2: PLMN1, PLMN2, TAC1, ECGI-12 4G

14 Customer Confidential
 4G-not shared,
Introduction 5G MORAN

Deployment scenarios (3/5)

NR gNB configuration EPC EPC

Global gNB ID: PLMN1
Op-1 Op-2
Cell Operator-1: PLMN1
Cell Operator-2: PLMN1, PLMN2

S1-C S1-U
LTE eNB-1 configuration S1-U
Global gNB ID: PLMN1
LTE eNB-2 configuration
Global gNB ID: PLMN2

LTE eNB-1 X2 NR en-gNB

PLMN-1 PLMN-1, PLMN-2

5G MORAN
LTE eNB-2
SIB1 (LTE)
PLMN-2 5G
Operator-1: PLMN1, TAC1, ECGI-11 5G
Operator-2: PLMN2, TAC2, ECGI-12
4G
4G

15 Customer Confidential
 4G-not shared,
Introduction 5G MOCN

Deployment scenarios (4/5)

NR gNB configuration EPC EPC

Global gNB ID: PLMN1
Op-1 Op-2
Cell Operator-1 & 2: PLMN1, PLMN2

LTE eNB-1 configuration S1-C S1-U

Global gNB ID: PLMN1 S1-U
LTE eNB-2 configuration
Global gNB ID: PLMN2

LTE eNB-1 X2 NR en-gNB

PLMN-1 PLMN-1, PLMN-2

5G MOCN
LTE eNB-2
PLMN-2
SIB1 (LTE)
Operator-1: PLMN1, TAC1, ECGI-11 5G
Operator-2: PLMN2, TAC2, ECGI-12
4G
4G

16 Customer Confidential
 4G MOCN,
Introduction 5G MOCN + SA

Deployment scenarios (5/5)

NR gNB configuration EPC EPC 5GC

Global gNB ID: PLMN1 Op-1
Op-1 Op-2
Cell Operator-1 & 2: PLMN1, PLMN2

LTE eNB configuration S1-C S1-U S1-U

Global gNB ID: PLMN1 (primary)
S1-U
Ng
Cell Operator-1 & 2: PLMN1, PLMN2
S1-C

LTE eNB X2 NR en-gNB

PLMN-1, PLMN-2 PLMN-1, PLMN-2
SIB1 (5G)
Operator-1: PLMN1, PLMN2, TAC1, NCGI-11
4G MOCN 5G MOCN

SIB1 (LTE) 5G
Operator-1: PLMN1, PLMN2, TAC1, ECGI-11
Operator-2: PLMN1, PLMN2, TAC1, ECGI-12 4G

17 Customer Confidential
 <chapter: technical details>

5G RAN Sharing

Technical Details

18 © Nokia 2020 Customer Confidential

Technical Details
Features in a nutshell

• 5GC00738 (5G19A) is the first feature introducing Network Sharing concept in the 5G networks while
5GC001840 (5G19B) enhances this with support for 5G SA
• Both features are activated by means of dedicated feature activation flag NRBTS.actRanSharing
- Then usage of particular feature depends on further configuration of cell type and PLMNs (NSA, SA) → more details
on the next slides
• Up to 2 Operators can share 5G RAN with 5GC00738 and 5GC001840
- 5G19A 2x NSA Operators, in 5G19B 1x NSA + 1x SA (on top of 5G19A possibilities) → more details on next slides

LTE Op1
EPC1

5G Core

19 Customer Confidential
Technical Details
MORAN/MOCN general deployment overview
RU can be shared. They are capable to Radio configuration
support multiple carriers (limited by does not impact RAN Sharing
max NR carriers supported by a RU) (e.g. number of radio units)

RU RU RU RU

RAU RAU
Cell #1 Cell #2 X2 Cell #1 Cell #2 X2
PLMN 1 PLMN 1 eNB PLMN 1 PLMN 2
eNB
PLMN 2 PLMN 2

gNB gNB

MOCN MORAN

20 Customer Confidential
Technical Details
MORAN + MOCN general deployment overview

RU RU RU

RAU
Cell #1 Cell #2 Cell #3
PLMN 1 PLMN 1 PLMN 2
PLMN 2

X2
MOCN MORAN MORAN eNB
gNB

MOCN + MORAN (example deployment)

• Mixed usage of MOCN and MORAN is possible within the gNB e.g. one cell is shared between the
operators while anothers are fully dedicated to one operator only
21 Customer Confidential
Technical Details
PLMN aspects in RAN Sharing – NSA

• As already mentioned, in NSA deployment - 5G PLMN IDs are not broadcast by 5G cells
• 5G PLMN ID selection is triggered by SgNB Addition/Modification procedure
- MeNB provides to SgNB information about allowed PLMNs for the user
- SgNB matches it with assigned PLMN IDs to existing cells during cell selection → see next slides for more details

SIB1 contains LTE PLMN list, which is broadcast by MeNB

Any changes here according to NSA 5G RAN Sharing, all legacy
rules related to PLMN selection and HRL* takes place.

HRL – Handover Restriction List

22 Customer Confidential
Technical Details
PLMN aspects in RAN Sharing – NSA

• PLMN ID selection is triggered by

- SgNB Addition procedure or
- SgNB Modification procedure (i.e. HO Case)

LTE MeNB 5G SgNB

SEND ALLOWED PLMN(S) ID FOR A PROPER USER

X2AP: SgNB Addition Request / X2AP: SgNB Modification Request

Allowed PLMN(s) for particular user are defined by Selected PLMN and HRL Select cell assign to one of allowed
(Handover Restriction List) parameters provided by MeNB.
PLMN(s)
If there is no HRL ever provided for particular user then there are no PLMN If there is no proper cell to be selected for this
restrictions and all PLMNs are allowed for this user. user, then cell selection procedure is failed (and
proper reject message is sent)

X2AP: SgNB Modification Request Acknowledge / X2AP: SgNB Addition Request Acknowledge

23 Customer Confidential
Technical Details
PLMN aspects in RAN Sharing – 5G19B

• 5GC001840 functionality brings a possibility to share 5G RAN with SA Operator (single SA PLMN per gNB)
- PLMN ID defined for SA could be a subset of NSA or totally different considering maximum 2 PLMNs per gNB limitation

RAU
Master PLMN: PLMN 1 Xn Broadcasted cells:
Cell 1 (PLMN 1); Cell 2 (PLMN 1); Cell 3 (PLMN 1)
Cell ID 1
PLMN 1 (Both)
PLMN 2 (NSA) gNB (PLMN 1 & 2)

Cell ID 2 Broadcasted cells:

PLMN 1 (SA) X2 Cell 1 (PLMN 1, PLMN 2); Cell 2 (PLMN 2)
PLMN 2 (NSA)
eNB (PLMN 1 & 2)
MOCN

MORAN
Broadcasted cells:
Cell ID 3 Ng Cell 1 (PLMN 1); Cell 2 (PLMN 1); Cell 3 (PLMN 1)
PLMN 1 (SA)

AMF (PLMN 1)

24 Customer Confidential
 Technical Details
PLMN aspects in RAN Sharing – 5G19B

• Introduction of SA support brings changes in the configuration of PLMNs in a shared network

- New MOCs connecting PLMN IDs with deployment type (NRPLMNSET_NSA, NRPLMNSET_SA) has been introduced
→ more details in Deployment Aspects section
NRBTS
Master PLMN which is part of
mcc, mnc, mncLength
NCGI (common for all cells)

NRPLMN NRCELL
PLMNs (up to 2) of the RAN Sharing nrPlmnId lcrId
Operators, without information regarding userLabel plmnList
SA / NSA (these are specified on a cell level) mcc, mnc, mncLength configuredEpsTAC
trackingAreaDn

Assignment of a PLMN ID to a cell specific NRPLMNSET_NSA NRPLMNSET_SA

nrPlmnSetNsaId nrPlmnSetSaId
configuration e.g.:
configuredEpsTac trackingAreaDN
• MOCN: 2 PLMNs (2x NSA or 1x NSA + 1xSA)
nrPlmnDNList nrPlmnDNList
• in case of MORAN only one PLMN used (either
SA or NSA)

25 Customer Confidential
 Technical Details
Radio Admission Control – interaction with PLMN selection

PSCell selection from received Cell List DU / Cell NRCELLGRP: Cell PLMN1 PLMN2 NRCELL: UEs in Cell List
Group maxNumOfUsers maxNumOfUsersPerCell Cell (from the
strongest):
Phase 1: Cell Group selection DU 1 / Cell 10 Cell1 8 4
1. Select the first cell from the "Cell List” which is Group 1
Cell3 8 4 Cell 4
sorted in descending order of the signal
Cell Group 1
strength. Cell4 8 2
2. Retrieve the DU ID and Cell Group ID of that
DU 2 / Cell 10 Cell2 8 0
selected cell Cell 2
Group 2
Cell5 8 0 Cell Group 2
Phase 2: PSCell selection
Among the list of the cells (sorted in descending
Cell6 8 0
order of the signal strength) belonging to the 1st priority Cell 3
selected Cell Group in phase 1, search for the first Selected PLMN: PLMN3 2nd priority 3rd priority Cell Group 1
cell that satisfies all of the below conditions, Handover Restriction List (HRL) -> Serving PLMN: PLMN2; Equivalent PLMNs: PLMN1, PLMN 3
starting from the cell with the strongest signal. Cell 1
1. Cell has allowed PLMN ID for the given NSA UE Cell Group 1
2. Cell has sufficient capacity to handle at least In this case Cell Group 2 is selected and Cell6 is selected as PSCell because:
one NSA UE (cellOperationalMode is “NSA” or • there is no cell assigned to Selected PLMN: PLMN3 Cell 5
“SA and NSA”) • strongest cells which are assigned to Serving PLMN from HRL: PLMN2 are Cell Group 2
3. Cell Group has sufficient capacity to handle at from the Cell Group which reaches maximum users
least one NSA UE • only Cell 6 from Cell Group 2 is assigned to PLMN2. Cell 6
4. Cell that is not configured as LTE-NR DSS cell
Cell Group 2
(NRCELL:lteNrDssMode="None") if UE is not
capable of LTE-CRS rate matching in the NR
PLMNs assigned to cell are defined by NIDD parameters:
band of that cell • NRCELL.plmnList NRCELL.NRPLMNSET_NSA.nrPlmnDNList – this list is validated only if NR RAN
If in the selected CellGroup from phase 1 there is no Sharing is enabled via NRBTS/actRanSharing
cell that satisfies all the above conditions from phase • NRBTS.mcc, mnc – this PLMN is validated only if NR RAN sharing functionality is disabled
2, then
26 algorithm is resumed from phase 1 to select Customer Confidential
another CellGroup taking the next strongest cell.
Technical Details
Mobility in a shared network

• In a shared network source gNB has to know which PLMNs are supported by the target cell to
properly perform mobility procedures e.g. to configure measurements and select proper target cells
- Legacy approach: by default only master PLMN defined for neighbour gNB by NRREL.gnbPLMN would be validate
during HO.
• As target cell can support RAN Sharing as well, new parameter has been introduced to list PLMNs
supported in a target cell (NRREL.plmnList)
- Based on this parameter, the source gNB knows:
• which PLMNs are supported by the target neighbour gNB cell
• and for which of PLMNs handled there we support handover.
It might be so that not for all supported PLMNs the
HO is allowed.

Note: For a relation with cells handled in the same gNB, this
structure (NRREL.plmnList) should be empty

27 Customer Confidential
Technical Details
PLMN selection during HO initiated by SgNB

• PLMN ID selection during handover initiated by SgNB based on measurement report from UE
LTE 5G
MeNB SgNB
MEASUREMENT REPORT FROM UE
X2 RRC Transfer message (if SRB3 is not configured),
or F1 UL RRC Message (if SRB3 is configured)

CELL SELECTION: gNB validates PLMN ID of candidate

cell with PLMNs defined for particular user.
Cell is selected only if at least one of assigned PLMN ID is
matching with PLMNs allowed for this UE.

X2AP: SgNB Modification Required or SgNB Change Required starting intra- or inter-SgNB handover procedure

Mobility to a different PLMN ID is possible, but keeping the same PLMN ID during mobility procedures is
always favoured.

28 Customer Confidential
Technical Details
PLMN change during HO and roaming initiated by MeNB (i.e. Intra-MeNB LTE handover)

• MeNB provides to SgNB information about selected PLMN ID and HRL. SgNB match it with existing PLMN
IDs and if currently chosen PLMN ID cannot be handled any longer then new PLMN is chosen.
LTE 5G
MeNB SgNB

SEND ALLOWED PLMN(S) ID FOR A PROPER USER.

X2AP: SgNB Addition Request \ X2AP: SgNB Modification Request

CELL SELECTION, gNB validates selected PLMN ID

▪ HRL provided in SgNB Addition or SgNB Modification request overwrites
existing HRL list for particular user. with PLMN IDs assigned to existing cells.
If there is a mismatch, then gNB matches PLMN IDs
from Handover Restriction List provided by MeNB
with PLMN IDs assigned to existing cells.

X2AP: SgNB Modification Request Acknowledge \ X2AP: SgNB Addition Request Acknowledge

Note 1: If selected PLMN ID is not contained in the SgNB Addition\Modification Request but stored previously, use store selected
PLMN for match
Note 2: If HRL is not contained in the SgNB Addition\Modification Request but stored previously, use stored HRL for match.

29 Customer Confidential
 <chapter: benefits & gains>

5G RAN Sharing

Interdependencies

30 © Nokia 2020 Customer Confidential

Interdependencies

prerequisites 5GC000900 Concurrent SA and NSA operation

Feature introduces support of a 5G Standalone mode and
must be activated prior to 5GC001840 use

31
 <chapter: deployment aspects>

5G RAN Sharing

Configuration
Management

32 © Nokia 2020 Customer Confidential

Configuration Management

Abbreviated name Full name Description Range and step Default

Activate RAN
actransharing This parameter activates/deactivates 5G RAN sharing. 0: false, 1: true 0
sharing
This parameter uniquely identifies the New Radio PLMN
New Radio PLMN (default not
nrplmnid (NRPLMN) instance within the same containing NRBTS from 1 to 6
instance identifier defined)
instance
This parameter indicates the MCC (Mobile Country (default not
mcc MCC in PLMN from 0 to 999
Code) in the PLMN (Public Land Mobile Network) ID. defined)
This parameter indicates the MNC (Mobile Network (default not
mnc MNC in PLMN from 0 to 999
Code) in the PLMN (Public Land Mobile Network) ID. defined)
This parameter indicates the length of the MNC (Mobile
MNC length in
mnclength Network Code) in the PLMN (Public Land Mobile from 2 to 3 2
PLMN
Network) ID, in digits.
This parameter denotes a label that can be used for a (default not
userlabel User label ()
user-friendly name of the NR PLMN defined)

REQUIRES BTS RESTART REQUIRES CELL LOCKING ONLINE MODIFIABLE

33 Customer Confidential
Configuration Management

Cell deployment 0: NSA, 1: SA, 2:

celldeptype This parameter indicates if a given cell supports access 0
type both
List of NRPLMN This parameter defines the distinguished name of the
(default not
nrplmndnlist distinguished NRPLMN instance(s) defining each operator for NR RAN ()
defined)
names Sharing.
New Radio PLMN This parameter uniquely identifies the New Radio PLMN
(default not
nrplmnsetnsaid Set for NSA Set for NSA (NRPLMNSET_NSA) instance within the same from 1 to 1
defined)
instance identifier containing NRBTS/NRCELL instance.
This parameter indicates the configured EPS tracking
Configured EPS (default not
configuredepstac area code (TAC) for a given New Radio cell. It enables to from 0 to 65535
tracking area code defined)
apply Roaming and Access Restrictions for EN-DC.
New Radio PLMN This parameter uniquely identifies the New Radio PLMN
(default not
nrplmnsetsaid Set for SA instance Set for SA (NRPLMNSET_SA) instance within the same from 1 to 6
defined)
identifier containing NRBTS/NRCELL instance.
Tracking Area
This parameter indicates the distinguished name of the (default not
trackingareadn distinguished ()
TRACKINGAREA instance. defined)
name
List of NRPLMN This parameter defines the distinguished name of the
(default not
nrplmndnlist distinguished NRPLMN instance(s) defining each operator for NR RAN ()
defined)
names Sharing.
34 REQUIRES BTS RESTART REQUIRES CELL LOCKING Customer
ONLINE MODIFIABLE
Confidential
Configuration Management

This parameter indicates the configured EPS tracking

Configured EPS (default not
configuredepstac area code (TAC) for a given New Radio cell. It enables to from 0 to 65535
tracking area code defined)
apply Roaming and Access Restrictions for EN-DC.
List of SNSSAI This parameter indicates the list of distinguished names
(default not
snssaidnlist distinguished of the SNSSAI instances representing the network slices ()
defined)
names for the TRACKINGAREA instance.
This parameter indicates a list of PLMNs assigned to the
neighbor gNB cell for handover and RAN sharing
(default not
plmnlist PLMN list purpose in NSA and SA configuration. Based on this ()
defined)
parameter, the source gNB knows what PLMNs are
supported by the target neighbour gNB cell.
This parameter indicates the mode of the corresponding 0: NSA, 1: SA, 2: (default not
plmnmode PLMN mode
PLMN for neighbor cell: NSA, SA or both. both defined)
Cell deployment This parameter indicates if a given neighbour cell 0: NSA, 1: SA, 2:
celldeptype 0
type supports access both
REQUIRES BTS RESTART REQUIRES CELL LOCKING ONLINE MODIFIABLE

35 Customer Confidential
 <chapter: deployment aspects>

5G RAN Sharing

Deployment Aspects

36 © Nokia 2020 Customer Confidential

Deployment Aspects
PLMN configuration aspects
• There are some differences in configuration of cel specific PLMNs in a shared network between 5G19A
and 5G19B → note that configuration of a Master PLMN on the NRBTS level remains unchanged
- in 5G19A these PLMNs must be configured (mcc, mnc, mncLength, plmnMode) in each NRCELL separately
- in 5G19B PLMNs are defined once in a new object NR_PLMN without information regarding deployment type
• then for each cell Operator needs to assign previously configured PLMN ID with proper deployment type defined by new
MOCs (NRPLMNSET_NSA, NRPLMNSET_SA) → no need to configure PLMN parameters (mcc, mnc, mncLength) for each cell
separately

5G19A 5G19B

PLMN assignment

37 Customer Confidential
 <5GC001840>

Deployment Aspects
Miscelanneous aspects
• Introduction of a Standalone support in RAN Sharing requires activation of a 5GC000900 Concurrent
SA and NSA operation functionality (and all its prerequisites)
- With this feature each cell has defined deployment type (NSA, SA, both) via NRCELL.cellDepType and this
configuration must be consistent with PLMN configuration → see examples below

NRPLMNSET_NSA (PLMN 1, PLMN 2), cellDepType=NSA

NRPLMNSET_SA (PLMN 1), NRPLMNSET_NSA (PLMN 2), cellDepType=both

NRPLMNSET_SA (PLMN 1), cellDepType=SA

• Also it is recommended to set PLMN which is supporting SA as Master PLMN in the gNB
- Since Master PLMN is common for all cells and will be broadcast in SIB1

38 Customer Confidential
Deployment Aspects
Feature impact analysis (1/2)
Feature impact How to measure?
To prove that feature is working properly, counters and Counters & KPIs:
KPIs related to RAN Sharing must be pegged
- The number of radio admitted UEs for NSA user per PLMN-ID
In case of 5GC000738 NSA counters per PLMN must be (M55145C00005)
incremented .
- The number of radio admitted non-GBR DRBs for NSA user
per PLMN-ID (M55145C00006)
- NR_557a: 5G PDCP SDU user DL data volume per PLMN
- NR_558a: 5G PDCP SDU user UL data volume per PLMN

With 5GC001840 also SA counters must be incremented. - The number of radio admitted UEs for SA user per PLMN-ID
(M55145C00501)
- The number of radio admitted non-GBR DRBs for SA user per
PLMN-ID (M55145C00502)
- PDCP SDU user DL data volume per PLMN-ID for SA user
(M55326C00501)
Examples only, for full list of RAN Sharing
counters go to Performance Aspects section - PDCP SDU user UL data volume per PLMN-ID for SA user
(M55326C00502)
39 Customer Confidential
Deployment Aspects
Feature impact analysis (2/2)
Feature impact How to measure?
Higher amount of 5G users and traffic amount KPIs:
In a shared network it is expected to have more users and more - NR_5123a 5G Maximum number of active UEs with data in the
traffic in comparison to single operator networks. buffer for DRBs in UL
If RAN Sharing is used from the scratch then such impact will - NR_5122a 5G Maximum number of active UEs with data in the
not be visible (i.e. effects will be visible if network is build for buffer for DRBs in DL
one operator, then second one is added to existing network)
- NR_5121a 5G Average number of active UEs with data in the
buffer for DRBs in UL
- NR_5120a 5G Average number of active UEs with data in the
buffer for DRBs in DL
- NR_5083a 5G MAC SDU data volume received in UL on DTCH
- NR_5082a 5G MAC SDU data volume transmitted in DL on
DTCH

40 Customer Confidential
 <chapter: performance aspects>

5G RAN Sharing

Performance Aspects

41 © Nokia 2020 Customer Confidential

Performance Aspects
Counter name Description
PDCP_SDU_UDATA_VOL_DL_NSA_PLMN PDCP SDU user DL data volume measured for NSA user per PLMN-ID
(M55145C00001) Repetitions and duplications are also counted.

MEASUREMENT: NR RAN Sharing TRIGGER EVENT: This counter is updated based on user data transmission of a PDCP SDU in the
downlink (gNB -> UE) for NSA UEs that are connected to specific PLMN (PLMN-ID) regardless of the
transmission success.
PDCP_SDU_UDATA_VOL_UL_NSA_PLMN PDCP SDU user UL data volume measured for NSA user per PLMN-ID
(M55145C00002) Repetitions and duplications are also counted.

MEASUREMENT: NR RAN Sharing TRIGGER EVENT: This counter is updated based on user data transmission of a PDCP SDU in the uplink
(UE -> gNB) for NSA UEs that are connected to specific PLMN (PLMN-ID) regardless of the
transmission success.
PDCP_SDU_SDATA_VOL_DL_NSA_PLMN Total number of PDCP SDU signaling DL bytes measured for NSA user per PLMN-ID
(M55145C00003)
TRIGGER EVENT: This counter is updated based on signaling data transmission of a PCDP SDU in the
MEASUREMENT: NR RAN Sharing downlink (gNB -> UE) for NSA UEs having SRB3 established that are connected to specific PLMN
(PLMN-ID) regardless of the transmission success.
PDCP_SDU_SDATA_VOL_UL_NSA_PLMN Total number of PDCP SDU signaling UL bytes measured for NSA user per PLMN-ID
(M55145C00004)
TRIGGER EVENT: This counter is updated based on signaling data transmission of a PCDP SDU in the
MEASUREMENT: NR RAN Sharing uplink (UE -> gNB) for NSA UEs having SRB3 established that are connected to specific PLMN (PLMN-
ID) regardless of the transmission success.

42 Customer Confidential
Performance Aspects
Counter name Description
RA_UE_NSA_PLMN Number of radio admitted UEs for NSA user per PLMN-ID
(M55145C00005)
TRIGGER EVENT: This counter is updated to the selected PS-Cell in the selected cell group (DU)
MEASUREMENT: NR RAN Sharing whenever CP-CELL makes successful radio admission for new NSA user, or new PLMN has been chosen
for existing user due to handover.

RA_NGBR_DRB_NSA_PLMN Number of radio admitted non-GBR DRBs for NSA user per PLMN-ID
(M55145C00006)
TRIGGER EVENT: This counter is updated to the selected PS-Cell in the DU whenever CP-CELL makes
MEASUREMENT: NR RAN Sharing successful radio admission for new non-GBR DRB for NSA user, or new PLMN has been chosen for
existing user due to handover.

RA_UE_SA_PLMN Number of radio admitted UEs for SA user per PLMN-ID

(M55145C00501)
TRIGGER EVENT: This counter is updated to the selected PS-Cell in the selected cell group (DU)
MEASUREMENT: NR RAN Sharing whenever CP-CELL makes successful radio admission for new SA user.

RA_NGBR_DRB_SA_PLMN Number of radio admitted non-GBR DRBs for SA user per PLMN-ID
(M55145C00502)
TRIGGER EVENT: This counter is updated to the selected PS-Cell in the DU whenever CP-CELL makes
MEASUREMENT: NR RAN Sharing successful radio admission for new non-GBR DRB for SA user.

43 Customer Confidential
Performance Aspects
Counter name Description
PDCP_SDU_USDAT_VOL_DL_NSA_PLMN PDCP SDU user DL data volume measured for NSA user per PLMN-ID
(M55326C00001) Repetitions and duplications are also counted.

MEASUREMENT: NR RAN Sharing UP TRIGGER EVENT: This counter is updated based on user data transmission of a PDCP SDU in the
downlink (gNB -> UE) for NSA UEs that are connected to specific PLMN (PLMN-ID) regardless of the
transmission success.
PDCP_SDU_USDAT_VOL_UL_NSA_PLMN PDCP SDU user UL data volume measured for NSA user per PLMN-ID
(M55326C00002) Repetitions and duplications are also counted.

MEASUREMENT: NR RAN Sharing UP TRIGGER EVENT: This counter is updated based on user data transmission of a PDCP SDU in the uplink
(UE -> gNB) for NSA UEs that are connected to specific PLMN (PLMN-ID) regardless of the
transmission success.
PDCP_SDU_SIDAT_VOL_DL_NSA_PLMN Total number of PDCP SDU signaling DL bytes measured for NSA user per PLMN-ID
(M55326C00003)
TRIGGER EVENT: This counter is updated based on signaling data transmission of a PCDP SDU in the
MEASUREMENT: NR RAN Sharing UP downlink (gNB -> UE) for NSA UEs having SRB3 established that are connected to specific PLMN
(PLMN-ID) regardless of the transmission success.
PDCP_SDU_SIDAT_VOL_UL_NSA_PLMN Total number of PDCP SDU signaling UL bytes measured for NSA user per PLMN-ID
(M55326C00004)
TRIGGER EVENT: This counter is updated based on signaling data transmission of a PCDP SDU in the
MEASUREMENT: NR RAN Sharing UP uplink (UE -> gNB) for NSA UEs having SRB3 established that are connected to specific PLMN (PLMN-
ID) regardless of the transmission success.

44 Customer Confidential
Performance Aspects
Counter name Description
PDCP_SDU_USDAT_VOL_DL_SA_PLMN PDCP SDU user DL data volume measured for SA user per PLMN-ID
(M55326C00501) Repetitions and duplications are also counted.

MEASUREMENT: NR RAN Sharing UP TRIGGER EVENT: This counter is updated based on user data transmission of a PDCP SDU in the
downlink (gNB -> UE) for SA UEs that are connected to specific PLMN (PLMN-ID) regardless of the
transmission success in the air interface.
Actual trigger point is when PDCP SDU of SA UE is sent to the RLC layer of gNB.
PDCP_SDU_USDAT_VOL_UL_SA_PLMN PDCP SDU user UL data volume measured for SA user per PLMN-ID
(M55326C00502) Repetitions and duplications are also counted.

MEASUREMENT: NR RAN Sharing UP TRIGGER EVENT: This counter is updated based on user data reception of a PDCP SDU in the uplink (UE
-> gNB) for SA UEs that are connected to specific PLMN (PLMN-ID).
Actual trigger point is when PDCP SDU of SA UE is received from the RLC layer of gNB.
PDCP_SDU_SIDAT_VOL_DL_SA_PLMN Total number of PDCP SDU signaling DL bytes measured for SA user per PLMN-ID
(M55326C00503)
TRIGGER EVENT: This counter is updated based on signaling data transmission of a PCDP SDU in the
MEASUREMENT: NR RAN Sharing UP downlink (gNB -> UE) for SA UEs having SRB(s) established that are connected to specific PLMN
(PLMN-ID) regardless of the transmission success.
PDCP_SDU_SIDAT_VOL_UL_SA_PLMN Total number of PDCP SDU signaling UL bytes measured for SA user per PLMN-ID
(M55326C00504)
TRIGGER EVENT: This counter is updated based on signaling data transmission of a PCDP SDU in the
MEASUREMENT: NR RAN Sharing UP uplink (UE -> gNB) for SA UEs having SRB(s) established that are connected to specific PLMN (PLMN-
ID) regardless of the transmission success.
45 Customer Confidential
Customer Confidential
Technical Details
PLMN aspects in RAN Sharing – 5G19A

• In 5G19A, with 5GC00738 feature, only NSA operators can share the 5G RAN
- this means that no SIB is broadcast on 5G side and access is realized via LTE which broadcast information regarding
supported PLMN(s)
- Nevertheless, 5G PLMNs must be configured in the gNB → Master PLMN common for each cell – according to 3GPP
(NRBTS.mnc, NRBTS.mncLength, NRBTS.mcc) and cell specific PLMN (configured within NRCELL.plmnList)

• Depending on selected RAN Sharing solution configuration of the PLMNs is as follows:

- To set up MORAN: NRCELL.plmnList contains only one element
- To set up MOCN: NRCELL.plmnList contains two element (the master PLMN is repeated here)

NRCELL.plmnList (structure)
‚SA’ and ‚both’ values are related to 5GC001840 feature which introduces
plmnMode – {NSA,SA,both}
support for SA Operator thus in 5G19A parameter can be configured to ‚NSA’
mnc – Mobile Network Code (0-999) value only.
mncLength – Length of MNC - in digits (2-3) Note: NRCELL.plmnList is not used from 5G19A onwards → see more details
mcc – Mobile Country Code (0-999) on next slides

48 Customer Confidential