Extra High Value Feature

NETWORK ENGINEERING

5G RAN Sharing
5GC000738 Multiple PLMN ID Support
5GC001840 5G RAN Sharing with multiple PLMNs NSA 3x and single PLMN SA
5GC001630 RAN Sharing in SA and additional configuration for NSA 3x
CB005830 NR RAN Sharing support for Unified Access Barring in SA mode

Network Engineering Information

• Doc ID: 5e32b89e058285001c5bdd60
• Version number: 1.5.2
• Authors/Presenters - Mateusz Raczkowiak, Konrad Prusak
• Approved
• 14-01-2021

Please, always check the latest version of NEI slides.

If you are using the content form this presentation in
1 © Nokia 2020
your own materials, please add webNEI reference
Nokia internal use
Disclaimer
• NEI PPT slide deck together with additional webNEI content is prepared to facilitate MN product competence development
and is intended to equip readers with comprehensive explanation of feature’ technical principles. It reflects the state of the
feature/solution as it is at the moment of NEI release and it will be maintained till C5 milestone (general availability) of the
release. While deploying feature at later phase (after C5 or with next software releases) please refer to corresponding
Customer Documentation.

• 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 Product Management and/or local sales teams at first.
Distribution and storage of NEI materials using external (non Nokia IT certified) media is strictly forbidden and violates
Nokia Information Security.

• Each NEI PPT slide deck is enriched with supplementary webNEI section listing CRs and CNIs relevant to features in scope.
Please review that section to acquaint with the latest feature changes and to check the status of NEI updates
corresponding to them.
On top of CR/CNI section, please refer to other components sourced by automated workflows listing feature
interdependencies, parameters, KPI, counters and other information related to given feature.

• NEI materials provide guidance for feature implementation. However actual configuration, parametrisation or feature
benefits may strongly depend on the specifics of the network scenario where given functionality is deployed.

• Content of NEI and corresponding tools is subject to change along with constant knowledge build-up based on progress in
feature development, testing, verification and feedbacks from pilots.

2
Nokia internal use
Feature scope matrix
List of features, subfeatures and CRs considered for this presentation (1/2)

Feature / CR ID Considered subfeatures CFAM version Comment

5GC000738 5GC000738-A Multiple PLMN ID support. V1.3 released on -
Multiple PLMN ID Support 2019-07-24
5GC000738-B PM support for NR RAN Sharing.
Aligned to 3GPP
5GC000738-C MDT (Message Definition Table guidelines) Rel. 15 December

5GC001840 5GC001840-A NR RAN Sharing for NSA + SA V0.19 -

5G RAN Sharing with multiple PLMNs 13-12-2019
NSA 3x and single PLMN SA 5GC001840-B SA handover in NR RAN Sharing configuration

5GC001840-D Performance management for NR RAN Sharing for SA

part

5GC001840-E NR RAN Sharing enabling/disabling in the runtime

5GC001630 5GC001630-A - SA sharing support up to 6 PLMNs and single PLMN V0.18

RAN Sharing in SA and additional Set cell 10-01-2020
configuration for NSA 3x
5GC001630-B SA sharing support up to 6 PLMNs and multiple PLMN
Sets per cell

5GC001630-C NSA + SA sharing up to 6 PLMNs

5GC001630-H NR RAN Sharing interaction with Mobility.

5GC001630-J PM Counters enhancement NSA

5GC001630-K NR RAN Sharing interaction with Slicing.

5GC001630-L pill over from 5GC000637-Q (Concurrency Handling)

3
Nokia internal use
Feature scope matrix
List of features, subfeatures and CRs considered for this presentation (2/2)

Feature / CR ID Considered subfeatures CFAM version Comment

CB005830 (5GC001630-I) V3.6 -
NR RAN Sharing support for Unified 2020-06-18
Access Barring in SA mode

4
Nokia internal use
5G RAN Sharing

6
Nokia internal use
 <chapter: introduction>

5G RAN Sharing

Introduction

7 © Nokia 2020
Nokia internal use
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

8
Nokia internal use
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

9
Core Network
Nokia internal use
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

10
Nokia internal use
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

11
Nokia internal use
 <5GC000738>

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 NSA 3.X 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
12
Nokia internal use
 <5GC001840>

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
13
Nokia internal use
 <5GC001630>

Introduction
5GC001630 overview

• 5GC001630 RAN Sharing in SA and additional configuration for NSA 3x is another feature from RAN
Sharing area
• This feature, introduced in 5G20A, brings support for up to 6 PLMNs with any combination of SA and
NSA Operators
• New performance measurement counters are introduced for RAN Sharing

EPC1
LTE Op1

5G Core

14
Nokia internal use
 <CB005830>

Introduction
CB005830 overview

• This feature enhances RAN sharing introduced before for standalone (SA) architecture with the
following functionalities:
- Broadcast of per-PLMN UAC (Unified Access Control) barring based on:
• configurable access class barring schemes (introduced in 5GC00742, defined by Operator),
• independent settings per access categories (Voice, Video, Data, etc.).
• UAC is a set of mechanism (algorithm) to determine whether to allow the UE for a specific services or state changes.
In MOCN, thanks to CB005830 and the shared NG-RAN, there is possibility to broadcast barring control information
for each PLMN individually in NR SIB1.

SIB1 per-PLMN SIB1

SIB1 SIB1 broadcast

SIB1 SIB1

Core Network

Core Network

15
Nokia internal use
 <5GC000738>

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

16
Nokia internal use
 <5GC001840>

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

17
Nokia internal use
 <5GC001630>

Introduction
Before & after 5GC001630

Before After

• Network Sharing possible between 2 • Up to 6 Operators (PLMNs) can be

operators with only one of them configured in a shared gNB
operatoring in 5G Standalone mode • Any mixture of NSA/SA is possible within
those 6 PLMNs

18
Nokia internal use
 CB005830
<CB005830>

Introduction
Before & after CB005830

Before After

• Broadcasted Unified Access Barring • Broadcast of Unified Access Barring

control informations were determined control information can be determined
for all PLMNs. for individual PLMN or for all PLMNs.

19
Nokia internal use
Introduction
RAN Sharing features landscape

• RAN Sharing is a complex solution which is enhanced with more and more features aiming at radio
aspects, transport and operability  few RAN Sharing features are listed below

Multiple PLMNs NSA Additional

RAN Sharing RRM
& Single PLMN SA Configuration for 5G RAN Sharing
5GC00738 (5G19A)
5GC001840 (5G19B) 5GC001630

Set of features related to transport separation

5GC001464, 5GC002018, 5GC001734

(QoS) non-GBR service

differentiation
5GC001926
ROADMAP

20
Nokia internal use
 <chapter: technical details>

5G RAN Sharing

Technical Details

21 © Nokia 2020
Nokia internal use
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
• With 5GC001630 (5G20A), up to 6 PLMNs can be configured in a shared gNB
• 5GC00738, BGC001840 and 5GC001630 are activated by means of dedicated feature activation flag
NRBTS.actRanSharing
• CB005830 is activated by means of dedicated feature activation flag NRBTS.actUacBarPerPlmn
- Then usage of particular feature depends on further configuration of cell type and PLMNs (NSA, SA)  more details
on the next slides

LTE Op1
EPC1

5G Core

22
Nokia internal use
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
• There are no special requirements regarding HW support for RAN Sharing
- RAN Sharing can be enabled on any HW available for Classical BTS

23
Nokia internal use
Technical Details
MORAN + MOCN general deployment overview

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
24
Nokia internal use
 <5GC000738>

Technical Details
PLMN configuration 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 broadcasts 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

25
Nokia internal use
 <5GC001840,5GC001630>

Technical Details
PLMN configuration in RAN Sharing from 5G19B onwards

• 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)
PLMNs (up to 6) of the RAN Sharing
Operators, without information regarding
SA / NSA (these are specified on a cell level) NRPLMN NRCELL
nrPlmnId lcrId
userLabel plmnList
Master PLMN (NRBTS) must be configured
mcc, mnc, mncLength configuredEpsTAC Parameters for single
as 1st PLMN here  NRPLMN-1
trackingAreaDn operator gNB / no RAN
Sharing

Assignment of a PLMN ID to a cell specific NRPLMNSET_NSA NRPLMNSET_SA

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

26
Nokia internal use
 <5GC000738>

Technical Details
PLMN aspects in RAN Sharing (NSA) – 5G19A

• 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. See more
info on LTE RAN Sharing materials

HRL – Handover Restriction List

27
Nokia internal use
 <5GC000738>

Technical Details
PLMN aspects in RAN Sharing (NSA) – 5G19A

• 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

28
Nokia internal use
 <5GC001840, 5GC001630>

Technical Details
PLMN aspects in RAN Sharing - SA (1/4)

• 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
- With 5GC001630 number of PLMNs is extended to 6
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 (Both) 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)
29
Nokia internal use
 <5GC001630>

Technical Details
PLMN aspects in RAN Sharing - SA (2/4)

• In LTE, there is a 3GPP constraint that makes mandatory for the eNB and all its hosted cells to have the
same PLMN ID used. So the PLMN ID in Global eNB ID and in ECGI of hosted cells must be identical
- In practice it means that Primary PLMN is included in SIB1 for all cells within shared eNB
• In 5G, this constraint has been removed in NR SIB1  different Primary PLMN can be broadcast in
different logical cells in NR SIB1
- “Traditional” master PLMN is kept in Nokia 5G RAN: master PLMN hosting the gNB and which will appear in "GlobalGNB-
ID“ and “NR CGI” that are carried over X2/Xn/F1 interfaces
- Primary PLMN broadcast in first position in all gNB cells is not needed anymore

Master PLMN: PLMN 1

Cell ID 1
PLMN 1 (Both)
PLMN 2 (Both) In LTE, Cell 2 would broadcast PLMN1 (as Primary
PLMN) and PLMN2 (Further PLMN which is cell
Cell ID 2 specific). PLMN1 in such cell need to be set to
PLMN 2 (SA) ‚reserved for operator use’

30
Nokia internal use
 <5GC001630>

Technical Details
PLMN aspects in RAN Sharing - SA (3/4)

• In 5G, SIB1 contains list of PLMNs (up to 12 according to 3GPP, up to 6 in Nokia implementation) in which
there is no differentiation between Primary (Master) PLMN and Further PLMN
• The only requirement is that list cannot be empty i.e. at least one PLMN ID must be present
- And this requirement, together with AMF availability, defines the content of SIB1 in terms of PLMN
• PLMN will be present in SIB1 if it is configured in the particular cell and gNB has a connection with an
AMF supporting this particular PLMN
- If AMF(s) supporting particular PLMN are not available, then PLMN is removed from SIB1

AMF1
Master PLMN: PLMN 1 Ng PLMN1
Cell ID 1
PLMN 1 (SA), PLMN 2 (SA) Ng AMF2
PLMN 3 (SA) PLMN2

Ng
AMF3
PLMN3

31
Nokia internal use
 <5GC001630>

Technical Details
PLMN aspects in RAN Sharing - SA (4/4)

• Again, contrary to LTE, presence of Master PLMN in SIB1 is not mandatory

• As a result, it may happen that due to unavailability of AMFs, only 1 PLMN which is not Master PLMN will
be included in SIB1
• If ’last PLMN’ becomes unavailable, cell is set to ’barred’  status is set in MIB to early decode cell status

AMF1
Master PLMN: PLMN 1 Ng PLMN1
Cell ID 1
PLMN 1 (SA), PLMN 2 (SA) Ng AMF2
PLMN 3 (SA) PLMN2

Ng
AMF3
PLMN3

32
Nokia internal use
 5G RAC
Technical Details
(click to follow the link)

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
33 algorithm is resumed from phase 1 to select
another CellGroup taking the next strongest cell. Nokia internal use
 <5GC001630>

Technical Details
Mobility in a shared network (1/4)

• 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
• With parallel use of NSA/SA, gNB must also know the deployment of particular PLMN in a target cell
since mobility between NSA and SA is not supported
• As target cell can support RAN Sharing as well, new MOCs have been introduced to list PLMNs
supported in a target cell (NRREL.REL_NRPLMNSET_SA, NRREL.REL_NRPLMNSET_NSA)
- Based on those parameters, the source gNB knows:
• which PLMNs are supported by the target neighbour gNB cell
• what deployment type for particular PLMN is supported (SA/NSA)
• Tracking Area Code of the target cell (with connection to a
PLMN and Slice)
• NRREL.REL_NRPLMNSET_SA  relNrPlmnSetSaId,
fiveGsTac, nrPlmnDNList
• NRREL.REL_NRPLMNSET_NSA  relNrPlmnSetNsaId,
nrPlmnDNList
34 Non-binding & customer confidential
Nokia internal use
 <5GC001630>

Technical Details
Mobility in a shared network (2/4)

• Neighbour Relation configuration principles in a shared network

NRBTS
mcc, mnc, mncLength

NRPLMN (0…6)
NRCELL
nrPlmnId
lcrId
userLabel
configuredEpsTAC
mcc, mnc, mncLength
trackingAreaDn

NRREL
cellDepType=both
NRPLMNSET_NSA NRPLMNSET_SA
nrPlmnSetNsaId nrPlmnSetSaId
configuredEpsTac trackingAreaDN
nrPlmnDNList nrPlmnDNList
REL_NRPLMNSET_SA
REL_NRPLMNSET_NSA
relNrPlmnSetSaId
relNrPlmnSetNsaId
fiveGsTac
nrPlmnDNList
nrPlmnDNList

35 Non-binding & customer confidential

Nokia internal use
 <5GC001630>

Technical Details
Mobility in a shared network (3/4)

• During HO procedure, gNB checks PLMN status in a target cell i.e.

- before Handover Request is send from Source to Target gNB, Source gNB checks latest status of a PLMN received via
Xn interface from Target gNB
- to perform HO, following conditions must be fulfilled with respect to the PLMN:
• NRREL object is properly configured with PLMN related information and deployment option (NSA/SA)
• Latest info regarding Broadcast PLMNs in the Target gNB contains PLMN valid for particular UE  list of Broadcast PLMNs is
delivered in Served Cell Information NR Information Elements (IE)  part of XnSetupResponse or Xn NG-RAN Node
Configuration Update

36 Non-binding & customer confidential

Nokia internal use
 <5GC001630>

Technical Details
Mobility in a shared network (4/4)

• In the example below, two SA PLMNs are configured in the REL_NRPLMNSET_SA (PLMN1, PLMN2) object
in the source cell
Initially i.e. during Xn Setup, source gNB receives information that both PLMNs are available in the target cell
- Then target gNB lost a connection with AMF supporting PLMN2 which result in removal of PLMN2 from SIB1 and
triggering Xn Configuration procedure towards Source cell with info that only PLMN1 is only supported
- As a result, target cell can be used for HO procedure only for the UEs with PLMN1  this will continue until another Xn
Update with information that PLMN2 is again available in Target cell
Source Target

Before HO, gNB performs crosscheck between

information configured in the NRREL and last
update from potential Target cell.

37 Non-binding & customer confidential

Nokia internal use
 <5GC000738>

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.

38
Nokia internal use
 <5GC000738>

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.

39
Nokia internal use
 <5GC001630>

Technical Details
Tracking Area configuration (1/2)

• In 5G, TAC can be common for all Operators in Network Sharing or each can have own TAC
• IE: PLMN-IdentityList in SIB1 allows to broadcast different TACs for different PLMNs

• Decision how many TACs will be bradcast depends on the MOC TRACKINGAREA configuration and
NRPLMNSET_SA
• Two options are possible:
1. All PLMNs are configured within the same NRPLMNSET_SA  per NRPLMNSET_SA only one TAC can
be defined, as a result all PLMNs will have the same TAC
2. Each PLMN is configured in an own, dedicated NRPLMNSET_SA and different TACs are assigned

40
Nokia internal use
 <5GC001630>

Technical Details
Tracking Area configuration (2/2)

Case 1: Case 2:
NRBTS NRBTS
mcc, mnc, mncLength
mcc, mnc, mncLength

TRACKINGAREA-1 TRACKINGAREA-1
NRCELL trackingAreaId
NRCELL trackingAreaId
lcrId fiveGsTac
lcrId fiveGsTac TRACKINGAREA-2
snssaiDNList
snssaiDNList trackingAreaId
fiveGsTac
snssaiDNList

NRPLMNSET_SA-1 NRPLMNSET_SA-1
nrPlmnSetSaId nrPlmnSetSaId
trackingAreaDN (TAC-1) trackingAreaDN (TAC-1)
nrPlmnDNList (PLMN1, nrPlmnDNList (PLMN1)
PLMN2)
NRPLMNSET_SA-2
nrPlmnSetSaId
trackingAreaDN (TAC-2)
nrPlmnDNList (PLMN2)
41
Nokia internal use
 <5GC001630>

Technical Details
Network Slicing configuration in a shared network (1/3)

• Configuration of a Network Slicing in a shared network allows to offer either the same set of slices for
participating Operators or different set of slices for different PLMNs
- Common slices can be one defined by 3GPP only (eMBB, URLLC, MIoT)
- Even if one TAC is used in a shared cell with MOCN, still set of slices for different Operators can be
different as slice is coupled not only with TAC but with PLMN as well
NRBTS
mcc, mnc, mncLength

NRCELL TRACKINGAREA SNSSAI

lcrId trackingAreaId snssaiId
fiveGsTac sst
snssaiDNList nrPlmnDNList

NRPLMNSET_SA
nrPlmnSetSaId
trackingAreaDN
nrPlmnDNList

42
Nokia internal use
 <5GC001630>

Technical Details
Network Slicing configuration in a shared network (2/3)

• Example below shows configuration in which single TAC is used for two Operators while set of slices
offered for their users is different
- In the below example, two slices are configured where one of them is common for both Operators
and one is available for one Operator only
NRBTS
mcc, mnc, mncLength

NRCELL TRACKINGAREA-1
SNSSAI-1
lcrId trackingAreaId
snssaiId
fiveGsTac
sst
snssaiDNList (SNSSAI-1, SNSSAI-2
nrPlmnDNList (PLMN1)
SNSSAI-2) snssaiId
sst
NRPLMNSET_SA nrPlmnDNList
Single TAC supports two
nrPlmnSetSaId • PLMN1
trackingAreaDN-1 different slices
• PLMN2
nrPlmnDNList Slice-1 is configured
• PLMN1 only for PLMN1
• PLMN2
Slice-2 is common for
PLMN1, PLMN2
43
Nokia internal use
 <5GC001630>

Technical Details
Network Slicing configuration in a shared network (3/3)

• In the second example, each Operator has its own Tracking Area, which doesn’t prevent using the same
type of slice  again, slice which is common must be the one defined by 3GPP only
- Configuration below can be used when Operators wants to have dedicated TACs but the same set of
slices  other option to achieve such confiuration is with 2 SNSSAIs with the same slice, each for
different operator
NRBTS
mcc, mnc, mncLength

NRCELL TRACKINGAREA-1
lcrId trackingAreaId
fiveGsTac
SNSSAI-1
snssaiDNList (SNSSAI-1) snssaiId
sst
TRACKINGAREA-2 nrPlmnDNList (PLMN1, PLMN2)
NRPLMNSET_SA-1
nrPlmnSetSaId trackingAreaId
trackingAreaDN-1 fiveGsTac
nrPlmnDNList snssaiDNList (SNSSAI-1)
NRPLMNSET_SA-2
• PLMN1 nrPlmnSetSaId
trackingAreaDN-2
44 nrPlmnDNList
• PLMN2 Nokia internal use
Technical Details
Resource sharing within common network

• With 5GC000738 & 5GC001840 features, no additional functionality aiming at controlled resource
sharing is introduced i.e. all the resources are fully pooled
• As a result it may happen that users of one Operator will ‘consume’ most of the cell capacity resources
e.g. controlled by the Admission Control mechanism
- Consequently only small number of other Operator UEs will be admitted → see example below
- This may also lead to imbalance in achieved throughputs per PLMN (which will be visible in counters/KPIs)

x25

x5

45
Nokia internal use
 CB005830
<CB005830>

Technical Details
Broadcast of Unified Access Barring per PLMN over SA Cells
• UAC is a mechanism introduced in 3GPP R15 System Information Block 1 (SIB1)
to determine whether to allow the UE for a
individualPLMNList
specific services or state changes.
uac-BarringPerPLMN-List AccessCategory1-SelectionAssistanceInf
• In 5G NR, SIB1 carries information if a UE is
allowed to access a cell and provides barring NRCELL.NRPLMN_UACBAR: NRCELL.plmnIndvSelAssisInfoList:

information required for UAC. • acBarListType • plmnIndvSelAssisInfo

• uacImplicitACBarringList • nrPlmnDN
• After a handover resulting in change of PCell • uacExplicitACBarringList
the UE defer access barring checks until it • nrPlmnDN
has obtained valid UAC information (from
SIB1) from the target cell.

• Thanks to CB005830 there is possibility to

provide per-PLMN UAC information. PLMN1 UE

• SA Cell needs to be configured with UAC

barring per PLMN parameters to be included PLMN2 UE
in IE SIB1 individualPLMNList. SA Cell

PLMN3 UE
46
Nokia internal use
 CB005830
<CB005830>

Technical Details
CB005830 parameters (1/2)

NRBTS
Activation flag
actUacBarPerPlmn
for CB005830 This parameter indicates the individual PLMN
assistance information for the UE to determine
whether Access Category 1 applies to the UE
This parameter indicates the list of individual NRCELL (more about that on the next slide).
PLMN assistance information for the UE to
plmnIndvSelAssisInfoList:
determine whether Access Category 1 applies.
It must be configured for SIB1 to broadcast • plmnIndvSelAssisInfo
uac-AccessCategory1-SelectionAssistanceInfo • nrPlmnDN
for individual PLMNs.

NRPLMN_UACBAR NRPLMNSET_SA
This parameter indicates nrPlmnUacBarId nrPlmnDNList
whether UAC - implicit nrPlmnDN
(all 63 access categories acBarListType This parameter indicates the access category.
configured), or explicit uacImplicitACBarringList 1 … 63 (more about that on the next slide)
(selected access categories uacExplicitACBarringList: Categories must be unique on BTS level.
configured) • accessCategory
AC Barring List is to be
• uacBarringInfoSetIndex This parameter indicates the index of the entry
used in the associated NR
PLMN. in the field 'SIB1’.
1…8

47
Nokia internal use
 CB005830
<CB005830>

Technical Details
CB005830 parameters (2/2)
Table below is presenting all of the Access Categories defined by 3GPP in R15 with description and type of access attempt.

Access Category Conditions related to UE Type of access attempt NOTE:

Access Category 1 is accompanied with
0 All MO signalling resulting from paging information that define whether Access
UE is configured for delay tolerant service and Category applies to UEs within one of the
subject to access control for Access Category 1, All except for Emergency, following categories:
1 (NOTE)
which is judged based on relation of UE’s HPLMN or MO exception data
• 0 – cat. A - UEs that are configured for
and the selected PLMN. delay tolerant service;
2 All Emergency
MO signalling on NAS level • 1 – cat. B - UEs that are configured for
3 All except for the conditions in Access Category 1. delay tolerant service and are neither in
resulting from other than paging
their HPLMN nor in a PLMN that is
MMTEL voice
4 All except for the conditions in Access Category 1. equivalent;
(Includes Real-Time Text - RTT)
5 All except for the conditions in Access Category 1. MMTEL video • 2 – cat. C - UEs that are configured for
6 All except for the conditions in Access Category 1. SMS delay tolerant service and are neither in
MO data that do not belong to any other the PLMN listed as most preferred.
7 All except for the conditions in Access Category 1.
Access Categories (includes IMS messaging)
MO signalling on RRC level
8 All except for the conditions in Access Category 1
resulting from other than paging
MO IMS registration related signalling
9 All except for the conditions in Access Category 1
(includes IMS registration related signalling)
10 All MO exception data
11-31 Reserved standardized Access Categories
32-63 All Based on operator classification.

48
Nokia internal use
 CB005830
<CB005830>

Technical Details
CB005830 SIB1 overload
SIB1
The size of uac-BarringPerPLMN-List IE broadcast in SIB1 depends on:

- Number of PLMNs supported in Cell,

- Setting of acBarListType:

• If it’s set to „Implicit” – all 63 Access Categories must be configured,

• If it’s set to „Explicit” – selected specific Access Categories may be configured,

- Number of Access Categories configured for each PLMN.

For multiple PLMNs supported it’s recommended to use „Explicit” acBarListType with specific categories defined,
becuse there is possibility to exceed SIB1 size limit by IE.

If supported size limit of SIB1 (up to 372 bytes depending on cell configurations) is exceeded:
- During cell configuration, alarm 7516 will be generated with Severity set to ‘Out-of-Order’. Cell will not be functioning in this
case until SIB1 parameters are reconfigured and the alarm is cleared.
- During cell reconfiguration, alarm 7516 will be generated with Severity set to ‘Degraded’. In this case, there will be no updates
to MIB, SIB1 and all other SI until the alarm is cleared.

49
Nokia internal use
 CB005830
<CB005830>

Technical Details
Dynamic cell reconfiguration procedure (1/2)
The purpose of the gNB-DU Configuration Update procedure is to update application level configuration data needed
for the gNB-DU and the gNB-CU to interoperate correctly on the F1 interface. Thanks to updated configuration gNB may
broadcast SIB1 with appropriate UAC barring information to appropriate UEs.

gNB-DU Served Cells To Modify List:

- Served Cells To Modify Item 1:
gNB-CU
- Old NR CGI
- Served Cell Information (with no update)
- gNB-DU System Info (with updated SIB1)
gNB-CU
replaces
F1AP*: GNB-FU CONFIGURATION UPDATE old SIB1
indicating
gNB-DU F1AP: GNB-DU CONFIGURATION UPDATE ACK by each
broadcast „Old NR CGI”
new SIB1
based on
„NR CGI” Cells To Be Activated List:
with AC - Cells To Be Activated List Item 1:
- NR CGI (corresponding to each „Old NR CGI”)

50
Nokia internal use
 CB005830
<CB005830>

Technical Details
Dynamic cell reconfiguration procedure (2/2)
When feature is enabled and SIB1 broadcast in SA Cell indicates more than one PLMN ID assigned:

Dynamic cell reconfiguration procedure is executed:

a) gNB-DU triggers F1AP (F1 Application Protocol) GNB-DU CONFIGURATION UPDATE to inform gNB-CU of the
updated SIB1 with UAC barring per PLMN parameters in Served Cells to Modify List IE.
The gNB-CU modify information of cell indicated by „Old NR CGI” IE according to the information in the Served Cell Information IE
and overwrite the Served Cell Information for the affected served cell.
Further, if the gNB-DU System Information IE is present the gNB-CU store and replace any previous information received.

b) gNB-CU stores and replaces the previous received SIB1 of the cells indicating by each „Old NR CGI” and responds
with F1AP: GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE.

When UAC barring parameters broadcast in SIB1 are changed, UE will update based on NR CGI IE its stored UAC barring
parameters according to the selected PLMN, and its access class.

c) gNB-DU broadcast the updated SIB1.

51
Nokia internal use
Technical Details
Network Sharing Management Approach

• The master Operator hosting the gNB is responsible for gNB supervision, troubleshooting and
maintenance.
- Master Operator has whole information related to problem investigation and maintenance.
- Other Operator are able to check the service quality (this is a driver to establish dedicated KPI per PLMN level which
goal is to QoS and throughput verification).
• Other operators are able to use services provided by the master Operator

Parametrization
• All features enabled at gNB level, as well as parameters on that level, are common for all Operators.
• All features/parameters configured on a cell level are:
• common for all operators in MOCN deployment
• remain dedicated to one operator in MORAN deployment

Operability
• There is no operator specific view/setting of counter monitoring or resource supervision
• There is only one management termination point including MORAN case.

52
Nokia internal use
 <chapter: benefits & gains>

5G RAN Sharing

Benefits & Gains

53 © Nokia 2020
Nokia internal use
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
- Thanks to CB005830 broadcast of Unified Access Barring control informations for PLMNs in SA architecture is
possible.

54
Nokia internal use
 <chapter: benefits & gains>

5G RAN Sharing

Interdependencies
Please note this section in materials shows only
where to find relevant information on
interdependencies in WebNEI portal

55 © Nokia 2020
Nokia internal use
How to find feature interdependencies in WebNEI?

• Under Network Engineering Information materials for certain feature there is dedicated section called Feature
Interdependency Matrix, which describes feature relations based on R&D input with additional NetEng add-ons:

• If necessary you can always download a copy of the relations by pushing a button in right corner

56
Nokia internal use
 <chapter: deployment aspects>

5G RAN Sharing
Please note this section in materials shows
only where to find relevant information on
Configuration parameters in WebNEI portal

Management

57 © Nokia 2020
Nokia internal use
How to find Configuration Management in WebNEI?

• Under feature materials in WebNEI platform there is dedicated section called Parameter Configuration, which lists all
parameters related to given functionality

• If necessary you can always download a copy of the parameters by pushing a button in right corner

58
Nokia internal use
 <chapter: deployment aspects>

5G RAN Sharing

Deployment Aspects

59 © Nokia 2020
Nokia internal use
Deployment Aspects
Deployment scenarios (1/6)
• RAN Sharing solutions introduced in a 5G product gives high flexibility in deployment options (MOCN,
MORAN, MOCN + MORAN, NSA, NSA +SA)
- Next couple of slides provide example configurations for different deployment scenarios

• General note valid for MORAN case

- Master PLMN is defined on a global gNB level. It has to be included in the list of Served PLMNs for each cell
• Rationale: If particular cell would be assigned to single PLMN different that master PLMN then it would be a mismatch
between list of Served PLMNs for such cell and NR Cell Global Identifier (NCGI) which includes always master PLMN. However
during Admission Control procedure master PLMN is not considered as a possible candidate
• Note: Above information is about handling master PLMN between MeNB and SgNB – Still, for non-master cell, operator does
not set master PLMN ID in NRCELL.plmnList parameter

60
Nokia internal use
 4G MORAN
Deployment Aspects 5G MORAN

Deployment scenarios (2/6)

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

61 Customer Confidential
Nokia internal use
 4G MOCN,
Deployment Aspects 5G MOCN

Deployment scenarios (3/6)

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

62 Customer Confidential
Nokia internal use
 4G-not shared,
Deployment Aspects 5G MORAN

Deployment scenarios (4/6)

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

63 Customer Confidential
Nokia internal use
 4G-not shared,
Deployment Aspects 5G MOCN

Deployment scenarios (5/6)

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

64 Customer Confidential
Nokia internal use
 4G MOCN,
Deployment Aspects 5G MOCN
(NSA + SA)
Deployment scenarios (6/6)

NR gNB configuration EPC EPC 5GC 5GC

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

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

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)
Cell-1: PLMN1, PLMN2, TAC1, NCGI-11
4G MOCN 5G MOCN

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

65 Non-binding & customer confidential

Nokia internal use
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
- from 5G19B onwards, PLMNs are defined once in NR_PLMN object 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

66
Nokia internal use
 <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

67
Nokia internal use
 <5GC000740>

Deployment Aspects
NG-C Flex
• In network sharing scenarios (MOCN, MORAN) Core Networks are dedicated per Operator
• Therefore to allow connection from a shared gNB to multiple Core Network nodes (AMFs) feature
5GC000740 NG-C Flex is introduced in 5G20A release
- In maximum configuration up to 32 AMFs can be connected to a single gNB
- Feature is activated by means of dedicated feature activation flag, namely NRBTS.actNgcFlexSaMode

gNB 1
AMF Set 1 Operator 1 Core Network

Pointer 1

Operator 2 Core Network

68
Nokia internal use
 CB005830
<CB005830>

Deployment Aspects
CB005830 parameters configuration (1/2)
Configuration of AccessCategory-SelectionAssistanceInfo:
Configure instances of NRCELL.plmnIndvSelAssisInfoList. In each instance:

NRBTS
actUacBarPerPlmn Set plmnIndvSelAssisInfo to value
representing individual PLMN assistance
information for the UE to determine
Set nrPlmnDN to one of the NRCELL whether Access Category 1 applies to it:
NRPLMN distinguished names in plmnIndvSelAssisInfoList:
NRPLMNSET_SA.nrPlmnDNList • plmnIndvSelAssisInfo • 0 – category A - UEs that are
of a NRPLMNSET_SA instance • nrPlmnDN configured for delay tolerant service;
with the same parent NRCELL
• 1 – category B - UEs that are
instance
configured for delay tolerant service
and are neither in their HPLMN nor in
a PLMN that is equivalent to it;
NRPLMN_UACBAR NRPLMNSET_SA
• 2 – category C - UEs that are
nrPlmnUacBarId nrPlmnDNList
configured for delay tolerant service
nrPlmnDN
and are neither in the PLMN listed as
acBarListType
most preferred.
uacImplicitACBarringList
uacExplicitACBarringList

69
Nokia internal use
 CB005830
<CB005830>

Deployment Aspects
CB005830 parameters configuration (2/2)
Configuration of uac-BarringPerPLMN-List:
Configure instances of NRPLMN_UACBAR for all PLMNs is. In each instance:
If acBarListType is set to ‘Implicit’:
NRBTS Configuration of all 63 categories
actUacBarPerPlmn
63 instances of uacImplicitACBarringList
must be configured for 63 access
NRCELL categories:
plmnIndvSelAssisInfoList Set each uacImplicitACBarringList to a
Set nrPlmnDN to one of the value between 1 to 8 (total instances of
NRPLMN distinguished names in uacAcContParSetList) pointing to the
NRPLMNSET_SA.nrPlmnDNList NRPLMN_UACBAR NRPLMNSET_SA instance of uacAcContParSetList to be
of a NRPLMNSET_SA instance nrPlmnUacBarId nrPlmnDNList used for the access category.
with the same parent NRCELL nrPlmnDN
instance acBarListType
uacImplicitACBarringList If acBarListType is set to ‘Explicit’ - cofiguration of specific categories,
Indicates list type. uacExplicitACBarringList:
Must be set to: • accessCategory Configure a few instances of uacExplicitACBarringList. In each instance:
• 0 - „Implicit” • uacBarringInfoSetIndex Set accessCategory to a value between 1 to 63 indicting an access
or category.
• 1 - „Explicit” Set uacBarringInfoSetIndex to a value between 1 to 8 (total instances
of uacAcContParSetList) pointing to the instance of
to be used for the access category.
70
Nokia internal use
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 (link)
- NR_558a: 5G PDCP SDU user UL data volume per PLMN (link)

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)
71
Nokia internal use
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

72
Nokia internal use
 <chapter: performance aspects>

5G RAN Sharing

Performance Aspects
Please note this section in materials shows only
where to find relevant information on
interdependencies in WebNEI portal

73 © Nokia 2020
Nokia internal use
How to find feature related counters & KPIs in WebNEI?

• Under feature materials in WebNEI platform there are dedicated sections called Counters and KPIs, which lists all
those related to given functionality

• If necessary you can always download a copy of the parameters by pushing a button in right corner

74
Nokia internal use
References and acknowledgments

Reference Version Author(s) Link Date of access

CFAM 5GC000738 1.3 Pawel H. Nowak (CFAM Leader) 26.07.2019

13.12.2019
CFAM 5GC001840 0.19 Pawel H. Nowak (CFAM Leader)

CFAM 5GC001630 0.35 Pawel H. Nowak (CFAM Leader) 18.09.2020

CFAM CB005830 3.6 Liwa Wang (CFAM Leader) 30.09.2020

75
Nokia internal use
 Copyright and confidentiality

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

76
Nokia internal use
Nokia internal use