NETWORK ENGINEERING
5G20B
5GC000988 Transport support for Basic
Network slicing
Network Engineering Information
• Doc ID: 5f645b9ce5077200117888dc
• Version number: 1.1
• Author/Presenter: Marcin Lewicki
• Status: APPROVED
• 21-08-2020
Please, always check the latest version of NEI slides.
1
© Nokia 2019
Nokia internal use
If you are using the content form this presentation in
your own materials, please add webNEI reference
Disclaimer
• Please note that the NEI materials are for internal use only. If they shall be used as a source for
the customer presentation, it is mandatory to align the contents with the Product Management
and/or local sales teams at first
• The results of simulations shown in this presentation are examples only. They demonstrate trends
(not absolute values) expected after feature activation. The presented simulations should be
analyzed with respect to the assumptions taken. They may differ from results achievable in real
networks.
• This NEI slide deck reflects the state of the feature/solution as it is at the moment of the NEI slide
deck release and is being updated up to C5 (release available) milestone .
2
Nokia internal use
Revision history and metadata
Document ID: 5f645b9ce5077200117888dc
Document location: https://webnei.emea.nsn-net.net/#/webnei/5f645b9ce5077200117888dc/1
Organization: Network Engineering
Version
Description of Changes
Date
Doc Owner
Doc Status
Reviewed by
0.1
DRAFT version
21-08-2020
Marcin Lewicki
DRAFT
George, Bino (Nokia - IN/Bangalore)
<bino.george@nokia.com>;
Sreenivas, Deepak (Nokia - IN/Bangalore)
<deepak.sreenivas@nokia.com>;
Metsala, Esa (Nokia - FI/Espoo)
<esa.metsala@nokia.com>;
Bandi, Srinivas (Nokia - IN/Bangalore)
<srinivas.bandi@nokia.com>;
Nanjangud Keerthi, Kavitha (Nokia IN/Bangalore)
<kavitha.nanjangud_keerthi@nokia.com>
1.0
APPROVED 1.0 version
17-08-2020
Marcin Lewicki
APPROVED
1.1
Transport Separation at Xn interface is descoped from
5GC000988 feature scope -> adding one slide about no
transport separation at Xn level (Technical details),
removing all Xn parameters and elements from figures
from Deployment Aspects chapter. Slide about multiple
PLMN in SNSSAI MOC added (Technical Details).
09-10-2020
Marcin Lewicki
3
Nokia internal use
Changes reviewed by:
George, Bino (Nokia - IN/Bangalore)
<bino.george@nokia.com>;
Approver
Approval Date
5GC000988 Transport support for Basic Network slicing
4
Nokia internal use
<chapter: introduction>
5GC000988 Transport support for Basic Network slicing
Introduction
5
© Nokia 2019
Nokia internal use
Introduction
Legend
NR
Backhaul (BH) / Fronthaul (FH)
network
BTS
(Base Transceiver Station)
Common node
icons are used
throughout the
presentation, as
defined on this
slide
BH/FH switch
Cloud BTS
components
(RU/RAU/RAC)
……
BH/FH router
BTS integrated
routing / switching
function
ToP Server
IPsec engine
Scheduler /
shaper function
NetAct
Core nodes
(AMF/UPF)
WebUI
IPv4
IPv6
Application binding to
transport IP interface
U
C
M
S
U
C
M
S
Application binding to
virtual IP interface
U
C
M
S
U
C
M
S
Transport IP interface (VLAN or untagged
Ethernet; no application binding, used e.g.
for tunnel termination or redundancy)
Security Gateway
(SecGW)
IPsec tunnel
T
T
6
Nokia internal use
<feature: 5GC000988>
Introduction
Scope
• This document focuses on NR SA implementation details of NR BTS - UPF path Slicing solution.
• 5G20B 5GC000988 Transport support for Basic Network slicing
Introduces slicing functionalities by using a separate logical interface per network slice in NR SA
(Classical Architecture). After feature introducing gNB will be able to provide separate transport
resources per slice based on S-NSSAI provided by UE. Each slice has its own U-Plane IP@ at BTS
which is identified as transport resource. Mutual isolation at transport level is ensured by mapping
source U-Plane IP address of slice to VLAN or IPsec tunnel (optional).
5GC000988
feature scope
UEs
Public Safety
U
UEs
1st hop router
Radio waves
Dedicated VLAN / IP subnet
Dedicated transport service
UPF
site router
U
Enterprise
U
UEs
NR BTS
IP Backhaul Network
UPF
MVNO
7
Nokia internal use
Introduction
5GC000988 Transport support for Basic Network slicing – Before & after
Before
• No possibility to provide traffic separation based on S-NSSAI
After
• Possibility to configure specific transport path (slices) per U-Plane based on:
• Source IP address
• VLAN or IPsec (optional, for traffic isolation only)
• Up to 20 additional U-plane IP addresses are supported (IPv4 or IPv6) (one per slice)
8
Nokia internal use
Introduction
IP addressing (extreme case) – 5GC000988 & 5GC002018 features enabled
Any other combination
is also supported
Planes can be associated
to the virtual IP@ also
Additional NG-U, NG-C, Xn-U and Xn-C IP
addresses per operator if 5GC002018 Transport
NG
U1
Xn
U1
NG
C1
Xn
C1
…
NG
U6
Xn
U6
NG
C6
Xn
C6
NG-U
x1
NG-U
x2
…
9
© Nokia 2017
separation for RAN sharing in SA Classical gnB
with up to six operators feature is enabled
NR BTS IP addressing:
C-Plane:
• NG-C and Xn-C Interfaces for signalling
U-Plane:
• NG-U and Xn U-Plane IP@ for standard services
• Additional 20 slices freely divided among operators
(Transport support for Basic Network slicing (5GC000988)
enabled)
-
Currently (5G20B) slices cannot use separate Xn-U IP@ and NG-U
IP@ -> Whole Xn-U traffic flows via single (default) Xn-U interface
NG-U
x20
Nokia internal use
Introduction
Feature scope conception visualization (single operator slices)
Xn-U
No transport separation
at Xn interface (whole
X-U traffic flows via
single (default) Xn
interface)
Normal User
U7
Standard U-Plane
(i.e. rest of services /
default slice)
Dedicated logical
network (e.g. IP VPN
Service) or Ipsec tunnel
per slice (optional)
UE
APN
1
Enterprise 1 User
U6
UE
U1
UPF
U2
U3
APN
2
MVNO User
U4
UE
NR BTS
UPF
U5
C1
Normal (standard)
& Enterprise 1 APN
Public Safety 1 User
MVNO APN
APN
3
Slice’s U-Planes
UE
UPF
NG-C
Public Safety 2 User
AMF
UE
10
Nokia internal use
Public Safety
APN
<chapter: technical details>
5GC000988 Transport support for Basic Network slicing
Technical Details
11
© Nokia 2019
Nokia internal use
<feature: 5GC000988>
Technical Details
5GC000988 Transport support for Basic Network slicing
•
The scope of this feature is to provide the transport capability to support dedicated IP resources
per slice. Each slice is identified by:
-
•
Additionally operator should configure dedicated (per slice):
-
•
IP address at gNB (slice’s source IP address) – single IP@ can handle multiple S-NSSAIs
VLAN or
IPsec tunnel
to isolate slices traffic between them if needed. When slices are appropriately isolated:
- no slice can interfere with another slice traffic
- this lowers the risk of introducing and running new services and supports migration because
new technologies or architectures can be launched on isolated slices
- it also has a security advantage that an attack would be confined in a slice and not able to
spread beyond that slice
If operator does not use VLANs or IPsec tunnels in RAN then each slice’s U-Plane IP address have
to be in separate IP subnet
12
Nokia internal use
Technical Details
Simplified end to end slices separation at transport level visualization using source IP@
Transport separation in mobile
backhaul can be realized using
various dedicated transport services
(EVC, IP VPN etc.) and technologies
(MPLS, MPLS-TE, QinQ etc. etc.)
C1
APN
1
U1
APN
2
U2
…
U20
(Uplane) Source IP@
APN
n
Source IP@ -> EVC
EVC-> VLAN
VLAN -> Dst. IP@
Source IP@
Source IP@
EVC
EVC
VLAN ID
VLAN ID
Dst. IP@
IP@ 1
IP@ 1
1
1
400
400
IP@ 1
IP@ 2
IP@ 2
2
2
401
401
IP@ 2
:
:
:
:
:
:
:
IP@ 20
IP@ 20
n
n
VLANID n
VLANID n
IP@ n
Each source IP address
at BTS belongs to the
different subnet
13
Nokia internal use
SLICES
Technical Details
Simplified end to end slices isolation at transport level visualization using VLANs
Transport separation in mobile
backhaul can be realized using
various dedicated transport services
(EVC, IP VPN etc.) and technologies
(MPLS, MPLS-TE, QinQ etc. etc.)
C1
APN
1
U1
APN
2
U2
…
U20
APN
n
Uplane IP@ -> VLAN
VLAN -> EVC
EVC-> VLAN
VLAN -> Dst. IP@
Source IP@
VLAN ID
VLAN ID
EVC
EVC
VLAN ID
VLAN ID
Dst. IP@
IP@ 1
200
200
1
1
400
400
SGW 1 IP@
IP@ 2
201
201
2
2
401
401
SGW 2 IP@
:
:
:
:
:
:
:
:
IP@ 20
VLANID n
VLANID n
n
n
VLANID n
VLANID n
SGW n IP@
Alternatively operator can use IPsec tunnels to isolate slices at transport level
14
Nokia internal use
SLICES
Technical Details
5GC000988 Transport support for Basic Network slicing – IP address sharing
Operator has to configure SNSSAI ↔ IP Interface mapping. Multiple slices (SNSSAI) can be
associated with single:
If SNSSAI.ngUplane is not configured,
• Transport IP interface
then slice will use primary
NRBTS.ngUplane as source IP@
• Virtual IP interface
(no transport separation between slices)
via SNSSAI and IPIF instances configuration
Virtual IP interface
Transport IP interface
U1
ipV4AddressDN1 ipV4AddressDN1
15
Both – IPv4 and IPv6
IP addresses are supported
(not simultaneously)
U1
ipV4AddressDN1 ipV4AddressDN1
NRBTS/SNSSAI-1
NRBTS/SNSSAI-2
NRBTS/SNSSAI-1
NRBTS/SNSSAI-2
ngUplane
ipV4AddressDN1=U1
ipV6AddressDN1
ngUplane
ipV4AddressDN1=U1
ipV6AddressDN1
ngUplane
ipV4AddressDN1=U1
ipV6AddressDN1
ngUplane
ipV4AddressDN1=U1
ipV6AddressDN1
In that case, when IP address is shared by multiple
SNSSAIs there is no transport separation between them!
Nokia internal use
Technical Details
5GC000988 Transport support for Basic Network slicing – multiple PLMN in SNSSAI
5GC001630 RAN Sharing in SA and additional configuration for NSA 3x feature introduces possibility
to configure multiple PLMN in a single SNSSAI MOC. In that case gNB will establish multiple slices, one
per configured PLMN and there will be no transport separation between these slices (common IP
address). If operator want to provide transport separation between slices must ensure there is
only one PLMN configured in specific SNSSAI MOC (dedicated IP address).
…/NRBTS/SNSSAI-1
…/NRBTS/SNSSAI-1
ngUplane
ipV4AddressDN1
ipV6AddressDN1
nrPlmnDNList-1 =…/NRPLMN-1
nrPlmnDNList-2 =…/NRPLMN-2
nrPlmnDNList-3 =…/NRPLMN-3
…
ngUplane
ipV4AddressDN1
ipV6AddressDN1
nrPlmnDNList-1 =…/NRPLMN-1
…
3 slices share the same source IP@ no transport separation between slices
1 slice with dedicated IP@ transport separation between slices
This rule (single PLMN in SNSSAI when operator want to provide transport
separation between slices) should be guaranteed by operator!
16
Nokia internal use
Technical Details
5GC000988 Transport support for Basic Network slicing
After 5GC000988Transport support for Basic Network slicing introducing NR
BTS SA supports additional:
• 20 additional IP addresses (one per slice)
- IPv4 or IPv6 -> dual IP addresses are not supported)
• 20 additional VLAN IDs (one per slice)
Slice specific QoS is out of scope of this feature so there is no additional first
level scheduler after feature implementation. However in 5G20B there are 45
first level scheduler by default which can be freely divided among IP interfaces
(default/slices/control traffic interfaces etc.)
17
Nokia internal use
Technical Details
Xn GTP-U Path Endpoint for slice
Currently (5G20B) there is no transport separation at Xn-U interface
As long as gNB does not support dedicted Xn IP address per SNSSAI instance then there
is no possibility to separate traffic on this part of path. Whole gNB ↔ gNB traffic goes via
primary (default) Xn interface.
Dedicated
logical
network
per slice
There is no transport
separation at Xn interface
(whole Xn-U traffic flows via
single (default) Xn interface)
UC2
NR BTS 2
Xn
UPF
UPF
U1
U2
NR BTS 1
UPF
U3
UC1
UPF
NG-U
AMF
NG-C
18
Nokia internal use
Technical Details
5GC000988 Transport support for Basic Network slicing - Licensing
First slice creation does not need any Licensing.
For every slice after the first slice, License Key is needed. SWEM uses SNSSAI
object instances in Netact database to track and enforce licensing.
For reference, SWEM can use following algorithm to calculate necessary
License keys.
𝑳𝒊𝒄𝒆𝒏𝒔𝒆 𝑲𝒆𝒚 =
𝒔𝒊𝒛𝒆(𝑺𝑵𝑺𝑺𝑨𝑰. 𝒏𝒓𝑷𝑳𝑴𝑵𝑫𝑵𝑳𝒊𝒔𝒕) − 𝟏
𝒇𝒐𝒓 𝒆𝒂𝒄𝒉
𝑺𝑵𝑺𝑺𝑨𝑰 𝒊𝒏𝒕𝒂𝒏𝒄𝒆
19
Nokia internal use
<chapter: benefits & gains>
5GC000988 Transport support for Basic Network slicing
Benefits & Gains
20
© Nokia 2019
Nokia internal use
Benefits & Gains
5GC000988 Transport support for Basic Network slicing
• Key enabler for E2E Network Slicing
- feature provides transport path selection for the slices
• Creating major customer value and business profit for operator by
enabling:
- New mobile connectivity services
- Network & service automation
- Higher operations cost-effectiveness
• CAPEX savings
- Operator is able to perform slices using currently built-in mechanism
without buying new devices
21
Nokia internal use
<chapter: benefits & gains>
5GC000988 Transport support for Basic Network slicing
Interdependencies
22
© Nokia 2019
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
23
Nokia internal use
<chapter: deployment aspects>
5GC000988 Transport support for Basic Network slicing
Configuration
Management
24
© Nokia 2019
Nokia internal use
How to find feature parameters 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 parameterss by pushing a button in right corner
25
Nokia internal use
<chapter: deployment aspects>
5GC000988 Transport support for Basic Network slicing
Deployment Aspects
26
© Nokia 2019
Nokia internal use
Deployment Aspects
cOAM introduction – Classical RAN 5G BTS
Since 5G19A release Classical RAN 5G BTS uses Common OAM (cOAM) architecture. cOAM is based
on SingleOAM (SOAM) architecture initially introduced for SBTS in SRAN17A, later introduced for
LTE BTS in LTE19.
That means SRAN/LTE and Classical 5G object model and parameters are highly harmonized since
19A release, especially with regard to transport functions and features. Not all legacy SRAN/LTE
transport features are supported in Classical 5G20B release scope, but those which are already
available have virtually the same functional scope as in SRAN/LTE (there still might be some
implementation differences due to HW dependencies).
Ultimate goal is to have full parity at object model and features scope at transport level between
SRAN/LTE and 5G Nokia base stations, expected to be achieved in some future release.
27
Nokia internal use
Deployment Aspects
cOAM introduction – Classical RAN 5G BTS
Classical 5G20B SW components are shown below. General (RAT agnostic) transport functions are
included in TNL package.
Some transport related configuration parts (OAM, logical interfaces binding for C-Plane and U-Plane,
HW dependencies, main slicing parameters) are also included in MNL, MRBTS, EQM, NRBTS_SOAM
packages respectively. All 5GC000988 parameters are in NRBTS_SOAM package.
EQM
EQM20B
EQM HW
EQMHW19A
EQM_R
EQMR20A
MRBTS
SBTS5GC20A
MNL
MNL5GC20B
TNL
TNL5GC20B
NRBTS_SOAM
NRBTSCL5G20B
One of the key properties of cOAM are Distinguished Name (DN) parameters. These provide reference to other MOC/parameter.
As a DN parameter value, full path is required (e.g. TNLSVC-1/TNL-1/IPNO-1/IPIF-3/IPADDRESSV4-1), but for simplicity root
MOCs are omitted in exemplary scenarios in this document.
28
Nokia internal use
Deployment Aspects
5GC000988 Transport support for Basic Network slicing
MOCs extended/using by 5GC000988 Transport support for Basic Network
slicing feature are in following MOCs:
Extended:
• NRBTS/SNSSAI: Provides slice configuration (i.e. Slice Differentiator, AdministrativeState).
5GC000988 adds paramter where we can configure dedicated ngUplane IP address per slice.
Single SNNSAI instance per slice.
Using:
• TNLSVC/TNL/IPNO: Provides IP interface configuration per slice including IP routing table
configuration
• TNLSVC/TNL/ETHSVC/ETIHIF/VLANIF: Provides VLAN configuration for each slice
29
Nokia internal use
Deployment Aspects
5GC000988 Transport support for Basic Network slicing
Parameter – contains reference as value
Fixed Association
Configurable association
MOC NAME
Parameter name
Parameter value
Object model
Configure proper IP
address (IPv4/IPv6)
for slice
…IPIF/IPADDRESSV4-1
localIpAddr=
ipV4AddressDN1
ipV6AddressDN1
Configure proper
VLAN for slice
…/VLANIF
vlanId=
…
interfaceDN
…/IPNO/IPIF
interfaceDN=
userLabel=
…
If SNSSAI specific ngUplane IP addresses is not
configured, then slice will use default/primary
IP address from NRBTS.ngUplane
…/NRBTS/SNSSAI
administrativeState
ngUplane
ipV4AddressDN1
ipV6AddressDN1
nrPlmnDNList
operationalState
sd
sst
userLabel
snssaiId
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=
…
These parameters are introduced with
5GC000988 feature
Underlined have to be set by operator
(rest of it are set automatically by the system)
30
Nokia internal use
SNSSAI.nrPlmnDNList
shall contains the reference
to the single
MRBTS.NRBTS.NRPLMN
if you want to provide
Transport Separation for slices
Deployment Aspects
5GC000988 Transport support for Basic Network slicing – User Scenarios
Following configuration scenarios are covered on next slides (mainly to show
parameterization details from IP interfaces perspective):
Scenario 1: Single operator on classical NR BTS, all planes assigned to transport
interfaces, 3 slices configuration, dedicated 1st level scheduler per slice
Scenario 2: Two operators on classical NR BTS (5GC002018 Transport
separation for RAN sharing in SA classical gnB enabled), all planes assigned to
transport interfaces, 2 slices per operator
Scenario 3: Single operator on classical NR BTS, all 3 slices’s planes assigned to
virtual interfaces
Scenario 4: Single operator on classical NR BTS, 2 IP@ dedicated for slices
associated with single VLAN
31
Nokia internal use
5G
Deployment Aspects
5G20B Scenario 1 – Scenario overview
Scenario overview:
•
Single operator is using NR BTS
•
Dedicated VLAN per slice
•
Each U-Plane IP@ (slice) is associated to the dedicated UPF
•
Each slice is associated with the dedicated SNSSAI(s)
•
M-Plane and S-Plane are ignored for simplicity (one per BTS)
•
BTSs are colocated
No transport separation
Standard, default
slice traffic
Dedicated
logical
network
per slice
at Xn interface (whole
X-U traffic flows via
single (default) Xn
interface)
APN
2
UPF
UC2
Standard
User
APN
3
UE
Xn
UPF
Enterprise 1
User
SNSSAI 1 slice
SNSSAI 2 slice
SNSSAI 3&4 slice
UE
UPF
U2
UC1 U3
MVNO User
UPF
UE
NG-C
Public Safety
User
Public Safety APN
NG-U
AMF
Sliced
traffic
MVNO APN
APN
4
U1
NR BTS
Enterprise-1 APN
UE
32
Nokia internal use
APN
1
Normal APN
5G
Deployment Aspects
5G20B Scenario 1 – Transport slicing configuration – configuration details (1/2)
More about schedulers configuring
you can find here
Configuration details for NR BTS:
•
Transport IP addresses:
-
•
2nd level scheduler
IP addresses:
•
U1 (SNSSAI #1) belongs to VLAN 100
•
U2 (SNSSAI #2) belongs to VLAN 200
•
U3 (SNSSAI #3&4) belongs to VLAN 300
•
UC1 (standard) belongs to VLAN 400
Applications’ IP addresses can be alternatively
assigned to virtual IP addresses (see Scenario 3)
Configuration details for 1st hop router:
•
VID-1004
Integrated switch
1st level schedulers
APN
1
UPF 1
VID-1001
NR BTS
UPF 2
U2 VID-200
VID-100
VID-200
S21
VID-300
VID-400
T1
T2
T3
T4
VID-1002
UPF 3
IP backhaul
UC1 VID-400
-
Slice #1 VLAN 100 (U-plane 1) → EVC 1
-
Slice #2 VLAN 200 (U-plane 2) → EVC 2
-
Slice #3 VLAN 300 (U-plane 3) → EVC 3
U6
APN
3
VID-1003
VLANs to EVC mapping:
U5
APN
2
U1 VID-100
U3 VID-300
U4
U7
APN
4
UPF 4
VID-400
UC2
Dedicated
1st
level scheduler per slice is used to provide dedicated QoS
configuration (per slice).
C3
VID-1005
5GC000988 does not introduce support of any new 1st level scheduler,
so there is possibility there is not enough 1st level schedulers to
33
associate each slice with dedicated 1st level scheduler
Nokia internal use
AMF
UPF/AMF
site routers
5G
Deployment Aspects
5G20B Scenario 1 – Transport slicing configuration – configuration details (2/2)
More about schedulers configuring
you can find here
Configuration details for UPF/AMF site router:
•
2nd level scheduler
EVC to VLANs mapping :
-
Slice #1 EVC 1 → VLAN 1001 (U-plane 5)
-
Slice #2 EVC 2 → VLAN 1002 (U-plane 6)
-
Slice #3 EVC 3 → VLAN 1003 (U-plane 7)
Configuration details for UPF and AMF
•
VID-1004
Integrated switch
1st level schedulers
UPF 2
U2 VID-200
IP addresses:
VID-100
S21
UPF 1 → U4 IP@ (VLAN 1004) standard traffic
-
UPF 2 → U5 IP@ (VLAN 1001) Slice #1
-
UPF 3 → U6 IP@ (VLAN 1002) Slice #2
-
UPF 4 → U7 IP@ (VLAN 1003) Slice #3
U3 VID-300
U5
APN
2
U1 VID-100
VID-200
-
APN
1
UPF 1
VID-1001
NR BTS
U4
VID-300
VID-400
T1
T2
T3
T4
VID-1002
U6
APN
3
UPF 3
IP backhaul
VID-1003
UC1 VID-400
U7
APN
4
UPF 4
VID-400
UC2
Dedicated
1st
level scheduler per slice is used to provide dedicated QoS
configuration (per slice).
C3
VID-1005
5GC000988 does not introduce support of any new 1st level scheduler,
so there is possibility there is not enough 1st level schedulers to
34
associate each slice with dedicated 1st level scheduler
Nokia internal use
AMF
UPF/AMF
site routers
5G
Deployment Aspects
5G20B Scenario 1 – Simplified end to end slices isolation using VLANs at transport level visualization
Transport separation in mobile
backhaul can be realized using
various dedicated transport services
(EVC, IP VPN etc.) and technologies
(MPLS, MPLS-TE, QinQ etc. etc.)
UC1
APN
2
U7
U1
U2
APN
3
U6
U3
U5
Uplane IP@ -> VLAN
VLAN -> EVC
EVC-> VLAN
SNSSAI
Source IP@
VLAN ID
1
U1
100
100
1
2
U2
200
200
2
3&4
U3
300
300
3
VLAN ID
EVC
APN
4
VLAN -> Dst. IP@
VLAN ID
VLAN ID
Dst. IP@
1
1001
1001
U5
2
1002
1002
U6
3
1003
1003
U7
EVC
Alternatively operator can use IPsec tunnels to isolate slices at transport level
35
Nokia internal use
SLICES
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 1 – Simplified IP interfaces (standard Planes) configuration (extended version here)
…/NRBTS
ngUplane
ipV4AddressDN1= …/IPIF-4/IPADDRESSV4-1
nrPlmnDN=…/NRBTS-1/NRPLMN-1
…
Configure proper standard
NG U-Plane IP@ & PLMN ID
ipV4AddressDN1
…/IPIF-4/IPADDRESSV4-1
Configure proper IP
address (IPv4/IPv6)
localIpAddr=U4 IP@
…
…/VLANIF-4
vlanId=400
…
Configure 2nd level
scheduler
Automatic
association
…/ETHIF-1
linkSelectorDN=…/IBRGPRT-1
…
linkSelectorDN
Configure proper
VLAN
…/IPNO/IPIF-4
interfaceDN=…/VLANIF-4
userLabel=U4
…
ipIfDN
Configure 1st level
scheduler
…/IPNO/QOS/FSTSCH-4
ipIfDN=…/IPIF-4
…
…/L2SWI-1/IBRGPRT-1
…
Rest of standard planes
(i.e. NGC, XnC and XnU-plane)
should be configured in the
same manner
36
Nokia internal use
Configure BTS
Integrated Ethernet
Switch
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 1 – Routing policies
…/IPRT-1
…/RTPOL-1
routingPolicies
orderNumber-1
routingTableDN=…/IPRT-1
srcIpAddress=UC1 IP@
userLabel=UC1
…
orderNumber-2
routingTableDN=…/IPRT-2
srcIpAddress=U1 IP@
userLabel=U1
…
orderNumber-3
routingTableDN=…/IPRT-3
srcIpAddress=U2 IP@
userLabel=U2
…
orderNumber-4
routingTableDN=…/IPRT-4
srcIpAddress=U3 IP@
userLabel=U3
…
More about IP Interfaces
configuration you can find here
37
staticRoutes-1
gateway=UC3 (NR BTS 2)
destIpAddr=UC3 IP@
…
staticRoutes-2
gateway=T4 (1st hop router)
destIpAddr=0.0.0.0
NR BTS 1
U1 VID-100
U2 VID-200
VID-100
VID-200
…/IPRT-2
S21
U3 VID-300
staticRoutes-1
gateway=U7 (NR BTS 2)
destIpAddr=U7 IP@
…
staticRoutes-2
gateway=T1 (1st hop router)
destIpAddr=0.0.0.0
IP Backhaul Network
UC1 VID-400
…/IPRT-3
staticRoutes-1
gateway=U8 (NR BTS 2)
destIpAddr=U8 IP@
…
staticRoutes-2
gateway=T2 (1st hop router)
destIpAddr=0.0.0.0
…/IPRT-4
VID-300
VID-400
T1
T2
T3
T4
VID-400
UC3
Thanks to staticRoutes-1 direct
NR BTS 1 <-> NR BTS 2 connection
is possible (Xn Planes traffic
doesn’t go through router if link
between BTSs works correctly)
staticRoutes-1
gateway=U9 (NR BTS 2)
destIpAddr=U9 IP@
…
staticRoutes-2
gateway=T3 (1st hop router)
destIpAddr=0.0.0.0
Nokia internal use
NR BTS 2
NR BTS 2 is
connected to IP
backhaul network
too (not shown)
Fixed Association
Configurable association
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 1 – Slice #1 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
Configure proper
VLAN for slice
…/VLANIF-1
interfaceDN
vlanId=100
…
…/IPIF-1/IPADDRESSV4-1
localIpAddr=U1 IP@
…/IPNO/IPIF-1
interfaceDN=…/VLANIF-1
userLabel=U1
…
ipV4AddressDN1
…/NRBTS/SNSSAI-1
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-1/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=101
sst=1
userLabel=Enterprise_1
snssaiId=1
…/IPNO/QOS/FSTSCH-1
1st
Configure
level
scheduler for slice
ipIfDN=…/IPIF-1
…
38
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
Fixed Association
Configurable association
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 1 – Slice #2 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
Configure proper
VLAN for slice
…/VLANIF-2
interfaceDN
vlanId=200
…
…/IPIF-2/IPADDRESSV4-1
localIpAddr=U2 IP@
…/IPNO/IPIF-2
interfaceDN=…/VLANIF-2
userLabel=U2
…
ipV4AddressDN1
…/NRBTS/SNSSAI-2
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-2/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=102
sst=1
userLabel=MVNO
snssaiId=2
…/IPNO/QOS/FSTSCH-2
1st
Configure
level
scheduler for slice
ipIfDN=…/IPIF-2
…
39
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
Fixed Association
Configurable association
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 1 – Slice #3 – Object model
…/NRBTS/SNSSAI-3
Configure proper
VLAN for slice
…/VLANIF-3
interfaceDN
vlanId=300
…
…/IPIF-3/IPADDRESSV4-1
localIpAddr=U3 IP@
…/IPNO/IPIF-3
interfaceDN=…/VLANIF-3
userLabel=U3
…
…/IPNO/QOS/FSTSCH-3
1st
Configure
level
scheduler for slice
40
ipIfDN=…/IPIF-3
…
There is no transport separation between
SNSSAI-3 and SNSSAI-4 traffic
(both are using the same source IP@)
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-3/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=103
sst=1
userLabel=Public_Safety
snssaiId=3
…/NRBTS/SNSSAI-4
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-3/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=104
sst=1
userLabel=Public_Safety
snssaiId=4
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
nrPlmnDNList
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 1 - Transport slicing configuration
In scenario 1 operator configure (per slice):
• dedicated 1st level scheduler (FSTSCH MOC)
• dedicated VLAN (VLANIF MOC)
• dedicated IPv4 or IPv6 address (IPADDRESSV4-1 or IPADDRESSV6-1 MOC)
Dedicated 1st level scheduler per slice is used to provide dedicated QoS configuration (per slice). 5GC000988 does not
introduce support of any new 1st level scheduler, so there is possibility there is not enough 1st level schedulers to
associate each slice with dedicated 1st level scheduler. But there will be always enough number of available VLANs
and IP addresses (both IPv4 and IPv6).
•
More about Transport QoS configuring here
•
More information about IP Interfaces configuring you can find here
41
Nokia internal use
5G
Deployment Aspects
5G20B Scenario 2 – Scenario overview
Scenario overview:
•
•
•
•
Two operators are using NR BTS - 5GC002018 Transport separation for RAN sharing in SA classical gnB must be enabled
Dedicated VLAN per slice
Each operator is using two slices
M-Plane and S-Plane are ignored for simplicity (one per BTS, under authority of primary operator (Operator 1)
Standard U-Planes
(i.e. rest of services)
APN
1
NG-C
Normal APN
AMF
Operator 1
APN
2
Operator 1 APN
UPF
Operator 1
User
UE
APN
3
UC1 U12
Operator 1 APN
UPF
U13
U22
APN
4
UC2 U23
Operator 2 APN
Operator 2
User
Operator 2
APN
5
UE
UPF
Operator 2 APN
Standard U-Planes
(i.e. rest of services)
NG-C
APN
6
AMF
42
Nokia internal use
Normal APN
5G
Deployment Aspects
5G20B Scenario 2 – Configuration details (1/2)
Configuration details for NR BTS:
•
Transport IP addresses:
-
Operator 1:
-
•
1st level schedulers
AMF 1
2nd level scheduler
-
UC1 (Standard/default ) belongs to VLAN 100
-
U11 (SNSSAI 1) belongs to VLAN 200
-
U12 (SNSSAI 2) belongs to VLAN 300
Operator 2:
-
UC1 (Standard/default ) belongs to VLAN 400
-
U21 (SNSSAI 3) belongs to VLAN 500
-
U22 (SNSSAI 4) belongs to VLAN 600
NR BTS
UC1 VID-100
VLANs to EVC mapping:
-
VLAN 200 → EVC 2
-
VLAN 500 → EVC 5
-
VLAN 300 → EVC 3
-
VLAN 600 → EVC 6
Integrated
switch
VID-1001
U1
VID-1002
U2
UPF 11
U11 VID-200
U12 VID-300
VID-1003
APN
1
APN
2
U3
APN
3
UPF 12
1st hop
router
Applications’ IP addresses can be alternatively assigned
to virtual IP addresses
Configuration details for 1st hop router:
•
Operator 1
UC2 VID-400
U21 VID-500
IP backhaul
VID-2001
U4
APN
4
VID-2002
U5
APN
5
U6
APN
6
UPF 21
VID-2003
U22 VID-600
AMF 2
Operator 2
43
Nokia internal use
UPF/AMF
routers
5G
Deployment Aspects
5G20B Scenario 2 – Configuration details (2/2)
Configuration details for UPF/AMF site router:
•
Operator 1
1st level schedulers
EVC to VLANs mapping:
-
Slice #1 EVC 2 → VLAN 1002 (U1-plane)
-
Slice #2 EVC 3 → VLAN 1003 (U2-plane)
-
Slice #4 EVC 5 → VLAN 2002 (U4-plane)
-
Slice #5 EVC 6 → VLAN 2003 (U5-plane)
AMF 1
2nd level scheduler
NR BTS
UC1 VID-100
Integrated
switch
VID-1001
U1
VID-1002
U2
UPF 11
U11 VID-200
APN
1
APN
2
Configuration details for UPF and AMF
•
IP addresses:
-
U12 VID-300
VID-1003
U3
APN
3
UPF 11 → U1 IP@ (VLAN1001) & U2 IP@ (VLAN1002)
-
UPF 12 → U3 IP@ (VLAN1003)
-
UPF 21 → U4 IP@ (VLAN2001) & U5 IP@ (VLAN2002) &
UPF 12
1st hop
router
U6 IP@ (VLAN2003)
UC2 VID-400
There is no dedicated 1st level scheduler per slice
U21 VID-500
IP backhaul
VID-2001
U4
APN
4
VID-2002
U5
APN
5
U6
APN
6
UPF 21
VID-2003
so you can’t configure different QoS configuration
(burst size, shaping, queuing) per slice
U22 VID-600
AMF 2
Operator 2
44
Nokia internal use
UPF/AMF
routers
Operator 1
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 2 – Simplified IP interfaces (standard Planes) configuration (extended version here)
…/NRBTS
ngUplane
ipV4AddressDN1= …/IPIF-1/IPAADDRESSV4-1
nrPlmnDN=…/NRBTS-1/NRPLMN-1
…
Configure proper
standard NG U-Plane
IP & PLMN ID
ipV4AddressDN1
…/IPIF-1/IPADDRESSV4-1
Configure proper IP
address (IPv4/IPv6)
localIpAddr=UC1 IP@
…
…/VLANIF-1
vlanId=100
…
Configure 2nd level
scheduler
Automatic
association
…/ETHIF-1
linkSelectorDN=…/IBRGPRT-1
…
linkSelectorDN
Configure proper
VLAN
…/IPNO/IPIF-1
interfaceDN=…/VLANIF-1
userLabel=UC1
…
ipIfDN
…/IPNO/QOS/FSTSCH-2
Configure common
1st level scheduler
for slice #1 & #2
ipIfDN=…/IPIF-2
ipIfDN=…/IPIF-3
…
…/L2SWI-1/IBRGPRT-1
…
Rest of standard planes
(i.e. NGC, XnC and XnU-plane)
should be configured in the
same manner
45
Nokia internal use
Configure BTS
Integrated Ethernet
Switch
Operator 2
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 2 – Simplified IP interfaces (standard Planes) configuration (extended version here)
…/NRBTS
ngUplane
ipV4AddressDN1= …/IPIF-4/IPAADDRESSV4-1
nrPlmnDN=…/NRBTS-1/NRPLMN-2
…
Configure proper
standard NG U-Plane
IP & PLMN ID
ipV4AddressDN1
…/IPIF-4/IPADDRESSV4-1
Configure proper IP
address (IPv4/IPv6)
localIpAddr=UC2 IP@
…
…/VLANIF-4
vlanId=400
…
Configure 2nd level
scheduler
Automatic
association
…/ETHIF-1
linkSelectorDN=…/IBRGPRT-1
…
linkSelectorDN
Configure proper
VLAN
…/IPNO/IPIF-4
interfaceDN=…/VLANIF-4
userLabel=UC2
…
ipIfDN
Configure common
1st level scheduler
for slice #1 & #2 and
UC2 plane
46
…/IPNO/QOS/FSTSCH-3
ipIfDN=…/IPIF-4
ipIfDN=…/IPIF-5
ipIfDN=…/IPIF-6
…
…/L2SWI-1/IBRGPRT-1
…
Rest of standard planes
(i.e. NGC, XnC and XnU-plane)
should be configured in the
same manner
Nokia internal use
Configure BTS
Integrated Ethernet
Switch
Operator 1
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 2 – Operator 1 – Slice #1 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
…/IPIF-2/IPADDRESSV4-1
Configure proper
VLAN ID
…/VLANIF-2
localIpAddr=U11 IP@
interfaceDN
vlanId=200
…
…/IPNO/IPIF-2
interfaceDN=…/VLANIF-2
userLabel=U11
…
ipV4AddressDN1
…/NRBTS/SNSSAI-1
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-2/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=101
sst=1
userLabel=Operator1_slice1
snssaiId=1
…/IPNO/QOS/FSTSCH-2
Configure common
1st level scheduler
for slice #1 & #2
ipIfDN=…/IPIF-2
ipIfDN=…/IPIF-3
…
47
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
Operator 1
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 2 – Operator 1 – Slice #2 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
…/IPIF-3/IPADDRESSV4-1
Configure proper
VLAN ID
…/VLANIF-3
localIpAddr=U12 IP@
interfaceDN
vlanId=300
…
…/IPNO/IPIF-3
interfaceDN=…/VLANIF-3
userLabel=U12
…
ipV4AddressDN1
…/NRBTS/SNSSAI-2
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-2/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=102
sst=1
userLabel=Operator1_slice2
snssaiId=2
…/IPNO/QOS/FSTSCH-2
Configure common
1st level scheduler
for slice #1 & #2
ipIfDN=…/IPIF-2
ipIfDN=…/IPIF-3
…
48
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
Operator 2
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 2 – Operator 2 – Slice #1 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
…/IPIF-5/IPADDRESSV4-1
Configure proper
VLAN ID
…/VLANIF-5
localIpAddr=U21 IP@
interfaceDN
vlanId=500
…
…/IPNO/IPIF-5
interfaceDN=…/VLANIF-5
userLabel=U21
…
ipV4AddressDN1
…/NRBTS/SNSSAI-3
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-5/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-2
operationalState=1
sd=103
sst=1
userLabel=Operator2_slice1
snssaiId=3
…/IPNO/QOS/FSTSCH-3
Configure common
1st level scheduler
for slice #1 & #2 and
UC2 plane
ipIfDN=…/IPIF-4
ipIfDN=…/IPIF-5
ipIfDN=…/IPIF-6
…
49
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-2
nrPlmnId=2
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
Operator 2
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 2 – Operator 2 – Slice #2 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
…/IPIF-6/IPADDRESSV4-1
Configure proper
VLAN ID
…/VLANIF-6
localIpAddr=U22 IP@
interfaceDN
vlanId=600
…
…/IPNO/IPIF-6
interfaceDN=…/VLANIF-6
userLabel=U22
…
ipV4AddressDN1
…/NRBTS/SNSSAI-4
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-6/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-2
operationalState=1
sd=104
sst=1
userLabel=Operator2_slice2
snssaiId=4
…/IPNO/QOS/FSTSCH-3
Configure common
1st level scheduler
for slice #1 & #2 and
UC2 plane
ipIfDN=…/IPIF-4
ipIfDN=…/IPIF-5
ipIfDN=…/IPIF-6
…
50
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-2
nrPlmnId=2
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 2 – Routing policies
…/RTPOL-1
Operator 1
staticRoutes-1
gateway=T1 (1st hop router)
destIpAddr=0.0.0.0
…
…/IPRT-2
orderNumber-5
routingTableDN=…/IPRT-5
srcIpAddress=U21 IP@
userLabel=U21
…
orderNumber-6
routingTableDN=…/IPRT-6
srcIpAddress=U22 IP@
userLabel=U22
…
staticRoutes-1
gateway=T2 (1st hop router)
destIpAddr=0.0.0.0
…
…/IPRT-3
1st level schedulers
VID-400
2nd level scheduler
NR BTS
UC1 VID-100
Integrated
switch
U11 VID-200
staticRoutes-1
gateway=T3 (1st hop router)
destIpAddr=0.0.0.0
…
U12 VID-300
T1
T2
IP backhaul
T3
…
…
routingPolicies
orderNumber-1
routingTableDN=…/IPRT-1
srcIpAddress=UC1 IP@
userLabel=UC1
…
orderNumber-2
routingTableDN=…/IPRT-2
srcIpAddress=U11 IP@
userLabel=U11
…
orderNumber-3
routingTableDN=…/IPRT-3
srcIpAddress=U12 IP@
userLabel=U12
…
…/IPRT-1
1st hop
router
…/IPRT-5
staticRoutes-1
gateway=T5 (1st hop router)
destIpAddr=0.0.0.0
…
…/IPRT-6
UC2 VID-400
T4
T5
staticRoutes-1
gateway=T6 (1st hop router)
destIpAddr=0.0.0.0
…
U21 VID-500
U22 VID-600
More about IP Interfaces
configuration you can find here
Operator 2
51
Nokia internal use
T6
IP backhaul
5G
Deployment Aspects
5G20B Scenario 3 – Transport slicing configuration
Scenario overview:
•
Single operator is using NR BTS
•
Dedicated VLAN per slice
•
Each U-Plane IP@ (slice) is associated to the dedicated UPF
•
Each slice is associated to the dedicated SNSSAI
•
M-Plane and S-Plane are ignored for simplicity (one per BTS)
Standard, default
slice traffic
UC2
Standard
User
APN
2
Dedicated
logical
network
per slice
UE
UPF
APN
3
UPF
Xn
Enterprise 1
User
SNSSAI 1 slice
SNSSAI 2 slice
SNSSAI 3&4 slice
UE
U1
NR BTS
U2
T1
U3
UC1 T3
UPF
UPF
UE
NG-C
Public Safety
User
Public Safety APN
NG-U
AMF
Sliced
traffic
MVNO APN
APN
4
T2
MVNO User
Enterprise-1 APN
UE
52
Nokia internal use
APN
1
Normal APN
Deployment Aspects
5G20B Scenario 3 – Configuration details (1/2)
Configuration details for NR BTS:
•
VID-1004
IP addresses:
APN
1
•
U1 (SSNSAI 1) routed to T4 (via T1 - VLAN 100)
•
U2 (SSNSAI 2) routed to T5 (via T2 - VLAN 200)
•
U3 (SSNSAI 3 & 4) routed to T6 (via T3 - VLAN 300)
•
UC1 (standard traffic) belongs to VLAN 400
1st level schedulers
Integrated switch
UPF 1
VID-1001
APN
2
NR BTS
VID-1002
Applications’ IP addresses can be alternatively
assigned to transport IP addresses (see Scenario 1)
U1
Configuration details for 1st hop router:
•
VID-100
T2 VID-200
VID-200
U2
U3
U5
UPF 2
T1 VID-100
•
U4
S21
T3 VID-300
VID-300
VID-400
U6
APN
3
T4
T5
T6
T7
UPF 3
VID-1003
U7
IP backhaul
APN
4
UPF 4
UC1 VID-400
VLANs to EVC mapping:
-
Slice #1 VLAN 100 (U-plane 1) → EVC 1
-
Slice #2 VLAN 200 (U-plane 2) → EVC 2
-
Slice #3 VLAN 300 (U-plane 3) → EVC 3
-
VID-400
UC2
C1
VID-1005
Standard traffic VLAN 400 (UC-plane 1) → EVC 4
AMF
2nd level scheduler
53
Nokia internal use
UPF/AMF
site routers
Deployment Aspects
5G20B Scenario 3 – Configuration details (2/2)
VID-1004
U4
APN
1
1st level schedulers
Configuration details for UPF/AMF site router:
Integrated switch
UPF 1
VID-1001
•
EVC to VLANs mapping :
-
Slice #1 EVC 1 → VLAN 1001 (U-plane 5)
-
Slice #2 EVC 2 → VLAN 1002 (U-plane 6)
-
Slice #3 EVC 3 → VLAN 1003 (U-plane 7)
-
Standard traffic EVC 4 → VLAN 1004 (U-plane 4)
APN
2
UPF 2
NR BTS
T1 VID-100
VID-1002
U1
VID-100
T2 VID-200
VID-200
U2
Configuration details for UPF and AMF
•
U3
S21
T3 VID-300
VID-300
VID-400
UPF 1 → U5 IP@ (VLAN1001) Slice #1
-
UPF 2 → U6 IP@ (VLAN1002) Slice #2
-
UPF 3 → U7 IP@ (VLAN1003) Slice #3
-
UPF 4 → U4 IP@ (VLAN1004) Standard traffic
-
AMF → C1 IP@ (VLAN1005) Signalling traffic
U6
APN
3
T4
T5
T6
T7
UPF 3
VID-1003
U7
IP backhaul
IP addresses:
-
U5
APN
4
UPF 4
UC1 VID-400
VID-400
UC2
C1
VID-1005
AMF
2nd level scheduler
54
Nokia internal use
UPF/AMF
site routers
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 3 – Simplified IP interfaces (standard Planes) configuration (extended version here)
…/NRBTS
NGUplane
ipV4AddressDN1= …/IPIF-5/IPAADDRESSV4-1
nrPlmnDN=…/NRBTS-1/NRPLMN-1
…
Configure proper
standard NG U-Plane IP
& PLMN ID
ipV4AddressDN1
…/IPIF-5/IPADDRESSV4-1
Configure proper IP
address (IPv4/IPv6)
localIpAddr=UC1 IP@
…
…/VLANIF-4
vlanId=400
…
Configure 2nd level
scheduler
Automatic
association
…/ETHIF-1
linkSelectorDN=…/IBRGPRT-1
…
linkSelectorDN
Configure proper
VLAN
…/IPNO/IPIF-5
interfaceDN=…/VLANIF-4
userLabel=UC1
…
ipIfDN
Configure 1st level
scheduler
…/IPNO/QOS/FSTSCH-4
ipIfDN=…/IPIF-5
…
…/L2SWI-1/IBRGPRT-1
…
Rest of standard planes
(i.e. X2C and X2U-plane)
should be configured in the
same manner
55
Nokia internal use
Configure BTS
Integrated Ethernet
Switch
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 3 – Routing Policies
…/RTPOL-1
…/IPRT-1
…/IPNO/IPIF-1
interfaceDN=not defined (= virtual)
userLabel=Virtual IFs
…
staticRoutes-1
gateway=T4 (1st hop router)
destIpAddr=0.0.0.0
……/IPRT-3
…/IPIF-1/IPADDRESSV4-1
localIpAddr=U1 IP@
localIpPrefixLength=32
…/IPIF-1/IPADDRESSV4-2
…
localIpAddr=U2 IP@
localIpPrefixLength=32
…/IPIF-1/IPADDRESSV4-3
…
localIpAddr=U3 IP@
localIpPrefixLength=32
…
Virtual interfaces
configuration
staticRoutes-1
gateway=T7 (1st hop router)
destIpAddr=0.0.0.0
……/IPRT-2
staticRoutes-1
gateway=T5 (1st hop router)
destIpAddr=0.0.0.0
……/IPRT-4
staticRoutes-1
gateway=T6 (1st hop router)
destIpAddr=0.0.0.0
…
More about IP Interfaces
configuration you can
find here
56
Nokia internal use
routingPolicies
orderNumber-1
routingTableDN=…/IPRT-1
srcIpAddress=UC1 IP@
userLabel=UC1
…
orderNumber-2
routingTableDN=…/IPRT-2
srcIpAddress=U1 IP@
userLabel=V1
…
orderNumber-3
routingTableDN=…/IPRT-3
srcIpAddress=U2 IP@
userLabel=V2
…
orderNumber-4
routingTableDN=…/IPRT-4
srcIpAddress=U3 IP@
userLabel=V3
…
Routing policies
configuration
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 3 – Slice #1 – Object model
…/IPIF-2/IPADDRESSV4-1
Configure proper
VLAN ID
…/VLANIF-1
ipV4AddressDN1
localIpAddr=U1 IP@
interfaceDN
vlanId=100
…
T1 interface
configuration
Configure common
1st level scheduler for
slice #1, #2 and #3
Configure proper IP
address (IPv4/IPv6)
for slice
…/IPIF-1/IPADDRESSV4-1
localIpAddr=U1 IP@
…/IPNO/IPIF-2
interfaceDN=…/VLANIF-1
userLabel=U1
…
…/IPNO/QOS/FSTSCH-2
ipIfDN=…/IPIF-2
ipIfDN=…/IPIF-3
ipIfDN=…/IPIF-4
…
…/NRBTS/SNSSAI-0
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-1/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=101
sst=1
userLabel=Slice#1
snssaiId=0
57
Nokia internal use
Slice
configuration
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
5G
Deployment Aspects
5G20B – Scenario 4 – Scenario overview
Scenario overview:
•
Single operator is using NR BTS
•
Each slice is associated with the dedicated SNSSAI
•
M-Plane and S-Plane are ignored for simplicity (one per BTS)
•
1st and 2nd are associated with single VLAN
UC3
Standard, default
slice traffic
Standard
User
Xn
APN
2
UE
Enterprise 1
User
SNSSAI 1 slice
SNSSAI 2 slice
SNSSAI 3 slice
Dedicated
logical
network
per slice
UE
UPF
APN
3
U1
NR BTS
UPF
U2
UC1 U3
MVNO User
UPF
UE
NG-C
Public Safety
User
Public Safety APN
NG-U
AMF
Sliced
traffic
Enterprise 1 & MVNO APN
UE
58
Nokia internal use
APN
1
Normal APN
5G
Deployment Aspects
5G20B Scenario 4 – Configuration details (1/2)
More about schedulers configuring
you can find here
Configuration details for NR BTS:
•
Transport IP addresses:
-
•
2nd level scheduler
IP addresses:
•
U1 (SNSSAI #1) belongs to VLAN 100
•
U2 (SNSSAI #2) belongs to VLAN 100
•
U3 (SNSSAI #3) belongs to VLAN 200
•
UC1 (standard) belongs to VLAN 300
Applications’ IP addresses can be alternatively
assigned to virtual IP addresses (see Scenario 3)
Configuration details for 1st hop router:
Integrated switch
1st level schedulers
VID-1003
NR BTS
APN
1
U1 VID-100
UPF 1
Slice 1&2
VID-1001
U2 VID-100
VID-100
S21
U3 VID-200
VID-200
VID-300
T1
T2
T3
VLANs to EVC mapping:
-
Slice #1 & Slice #2 VLAN 100 (U-plane 1) → EVC 1
-
Slice #3 VLAN 200 (U-plane 3) → EVC 2
U5
APN
2
UPF 2
IP backhaul
VID-1002
•
U4
UC1 VID-300
U6
APN
3
UPF 3
VID-300
UC2
Dedicated
1st
level scheduler per slice is used to provide dedicated QoS
configuration (per slice).
C3
VID-1004
5GC000988 does not introduce support of any new 1st level scheduler,
so there is possibility there is not enough 1st level schedulers to
59
associate each slice with dedicated 1st level scheduler
Nokia internal use
AMF
UPF/AMF
site routers
5G
Deployment Aspects
5G20B Scenario 4 – Configuration details (2/2)
More about schedulers configuring
you can find here
Configuration details for UPF/AMF site router:
•
2nd level scheduler
EVC to VLANs mapping :
-
Slice #1 & Slice #2 EVC1 → VLAN 1001 (U-plane 5)
-
Slice #3 EVC 2 → VLAN 1002 (U-plane 6)
Integrated switch
1st level schedulers
VID-1003
NR BTS
APN
1
U1 VID-100
Configuration details for UPF and AMF
•
VID-1001
VID-100
S21
-
UPF 1 → U4 IP@ (VLAN 1003) standard traffic
-
UPF 2 → U5 IP@ (VLAN 1001) Slice #1 & Slice #2
-
UPF 3 → U6 IP@ (VLAN 1002) Slice #3
UPF 1
Slice 1&2
U2 VID-100
IP addresses:
U3 VID-200
U4
VID-200
VID-300
T1
T2
T3
U5
APN
2
UPF 2
IP backhaul
VID-1002
UC1 VID-300
U6
APN
3
UPF 3
VID-300
UC2
Dedicated
1st
level scheduler per slice is used to provide dedicated QoS
configuration (per slice).
C3
VID-1004
5GC000988 does not introduce support of any new 1st level scheduler,
so there is possibility there is not enough 1st level schedulers to
60
associate each slice with dedicated 1st level scheduler
Nokia internal use
AMF
UPF/AMF
site routers
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 4 – Simplified IP interfaces (standard Planes) configuration (extended version here)
…/NRBTS
ngUplane
ipV4AddressDN1= …/IPIF-4/IPADDRESSV4-1
nrPlmnDN=…/NRBTS-1/NRPLMN-1
…
Configure proper standard
NG U-Plane IP@ & PLMN ID
ipV4AddressDN1
…/IPIF-4/IPADDRESSV4-1
Configure proper IP
address (IPv4/IPv6)
localIpAddr=U4 IP@
…
…/VLANIF-3
vlanId=300
…
Configure 2nd level
scheduler
Automatic
association
…/ETHIF-1
linkSelectorDN=…/IBRGPRT-1
…
linkSelectorDN
Configure proper
VLAN
…/IPNO/IPIF-4
interfaceDN=…/VLANIF-3
userLabel=U4
…
ipIfDN
Configure 1st level
scheduler
…/IPNO/QOS/FSTSCH-4
ipIfDN=…/IPIF-4
…
…/L2SWI-1/IBRGPRT-1
…
Rest of standard planes
(i.e. NGC, XnC and XnU-plane)
should be configured in the
same manner
61
Nokia internal use
Configure BTS
Integrated Ethernet
Switch
MOC NAME
Parameter name
Parameter value
Deployment Aspects
5G20B Scenario 4 – Routing policies
…/IPRT-1
…/RTPOL-1
routingPolicies
orderNumber-1
routingTableDN=…/IPRT-1
srcIpAddress=UC1 IP@
userLabel=UC1
…
orderNumber-2
routingTableDN=…/IPRT-2
srcIpAddress=U1 IP@
userLabel=U1
…
orderNumber-3
routingTableDN=…/IPRT-2
srcIpAddress=U2 IP@
userLabel=U2
…
orderNumber-4
routingTableDN=…/IPRT-3
srcIpAddress=U3 IP@
userLabel=U3
…
More about IP Interfaces
configuration you can find here
staticRoutes-1
gateway=UC2 (NR BTS 2)
destIpAddr=UC2 IP@
…
staticRoutes-2
gateway=T3 (1st hop router)
destIpAddr=0.0.0.0
NR BTS 1
U1 VID-100
Slice 1&2
U2 VID-100
VID-100
S21
…/IPRT-2
staticRoutes-1
gateway=U4 (NR BTS 2)
destIpAddr=U4 IP@
…
staticRoutes-2
gateway=U5 (NR BTS 2)
destIpAddr=U5 IP@
…
staticRoutes-3
gateway=U7 (1st hop router)
destIpAddr=0.0.0.0
…
…/IPRT-3
staticRoutes-1
gateway=U6 (NR BTS 2)
destIpAddr=U6 IP@
…
staticRoutes-2
gateway=T2 (1st hop router)
destIpAddr=0.0.0.0
U3 VID-200
VID-200
VID-300
T1
T2
T3
IP Backhaul Network
UC1 VID-300
VID-300
UC2
Thanks to staticRoutes-1 (and -2 in
IPRT-2) direct NR BTS 1 <-> NR BTS 2
connection is possible (Xn Planes
traffic doesn’t go through router if link
between BTSs works correctly)
62
Nokia internal use
NR BTS 2
NR BTS 2 is
connected to IP
backhaul network
too (not shown)
Fixed Association
Configurable association
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 4 – Slice #1 & Slice 2 – Object model
…/IPIF-1/IPADDRESSV4-1
…/IPIF-1/IPADDRESSV4-2
localIpAddr=U1 IP@
localIpAddr=U1 IP@
Configure proper
VLAN for slice
…/VLANIF-1
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-1/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=101
sst=1
userLabel=Enterprise_1
snssaiId=1
…/IPNO/IPIF-1
interfaceDN=…/VLANIF-1
userLabel=U1
…
vlanId=100
…
…/IPNO/QOS/FSTSCH-1
Configure 1st level
scheduler for slice
…/NRBTS/SNSSAI-1
ipIfDN=…/IPIF-1
…
…/NRBTS/SNSSAI-2
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-1/IPADDRESSV4-2
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=102
sst=1
userLabel=MVNO
snssaiId=2
63
Nokia internal use
nrPlmnDNList
SNSSAI.nrPlmnDNList
contains the reference
to
MRBTS.NRBTS.NRPLMN
nrPlmnDNList
ipV4AddressDN1
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
Fixed Association
Configurable association
Deployment Aspects
MOC NAME
Parameter name
Parameter value
5G20B Scenario 4 – Slice #3 – Object model
Configure proper IP
address (IPv4/IPv6)
for slice
…/IPIF-3/IPADDRESSV4-1
localIpAddr=U3 IP@
Configure proper
VLAN for slice
…/VLANIF-1
…/IPNO/IPIF-2
interfaceDN=…/VLANIF-2
userLabel=U3
…
vlanId=200
…
ipV4AddressDN1
…/NRBTS/SNSSAI-3
administrativeState=2
ngUplane
ipV4AddressDN1=IPIF-3/IPADDRESSV4-1
ipV6AddressDN1=
nrPlmnDNList=…/NRBTS/NRPLMN-1
operationalState=1
sd=103
sst=1
userLabel=Public_Safety
snssaiId=3
…/IPNO/QOS/FSTSCH-3
Configure 1st level
scheduler for slice
ipIfDN=…/IPIF-3
…
64
Nokia internal use
nrPlmnDNList
…/NRBTS/NRPLMN-1
nrPlmnId=1
…
SNSSAI.nrPlmnDNList
contains the reference to
MRBTS.NRBTS.NRPLMN
References and acknowledgments
Reference
Version
Author(s)
5GC000988 CFAM
3.0.3
Bino George
5G20A Transport QoS Complex
1.1
Marcin Lewicki
Link
01.08.2020
5G20B 5G BTS IP Interfaces: Classical RAN
Architecture
1.1
Michał Malcher
Link
10.10.2020
65
Nokia internal use
Link
Date of access
29.09.2020
Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is
provided subject to confidentiality obligations of the
applicable agreement(s).
This document is intended for use of Nokia’s
customers and collaborators only for the purpose
for which this document is submitted by Nokia. No
part of this document may be reproduced or made
available to the public or to any third party in any
form or means without the prior written permission
of Nokia. This document is to be used by properly
trained professional personnel. Any use of the
contents in this document is limited strictly to the
use(s) specifically created in the applicable
agreement(s) under which the document is
submitted. The user of this document may
voluntarily provide suggestions, comments or other
feedback to Nokia in respect of the contents of this
document ("Feedback").
Such Feedback may be used in Nokia products and
related specifications or other documentation.
Accordingly, if the user of this document gives Nokia
Feedback on the contents of this document, Nokia
may freely use, disclose, reproduce, license,
distribute and otherwise commercialize the
feedback in any Nokia product, technology, service,
specification or other documentation.
are made in relation to the accuracy, reliability or
contents of this document. NOKIA SHALL NOT BE
RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT or for any loss of data or income or any
special, incidental, consequential, indirect or direct
damages howsoever caused, that might arise from
the use of this document or any contents of this
document.
Nokia operates a policy of ongoing development.
Nokia reserves the right to make changes and
improvements to any of the products and/or
services described in this document or withdraw this
document at any time without prior notice.
This document and the product(s) it describes
are protected by copyright according to the
applicable laws.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties
of any kind, either express or implied, including, but
not limited to, the implied warranties of
merchantability and fitness for a particular purpose,
66
Nokia internal use
Nokia is a registered trademark of Nokia
Corporation. Other product and company names
mentioned herein may be trademarks or trade
names of their respective owners.
Nokia internal use