AirScale BSC SW Sales Guide

Nokia Next Generation Radio Access:
AirScale BSC – Sales guide
October 2020
Version : 2.63
1 © Nokia 2020 Confidential

AirScale BSC – Sales Guide
- This document provides general information on AirScale BSC SW configuration and related pricing using CSP / IPC
- Additionally, information on the reference data center infrastructure HW, host SW and management entities is provided :
• NCIR19 SW – infrastructure for AirScale BSC VNF deployment, mandatory
• NDCS, Nokia AirFrame HW – infrastructure for AirScale BSC VNF deployment, mandatory
• NADCM – Nokia AirFrame infrastructure management, mandatory
• CBAM – VNFM for AirScale BSC lifecycle management, mandatory
• This document is for internal use only - do not distribute to customers
• AirScale BSC SW IRP list is available through MN Commercial Management SharePoint :

https://nokia.sharepoint.com/sites/MNProductsCommercialManagement/RadioNetworksPricing/_layouts/15/DocIdRedir.aspx?ID=RTI4PLPIUPB3-
149537009-280
• Note: NCIR19 SW and CBAM SW order intake needs to be indicated in sCRM. Pricing related details available through NSW
2 © Nokia 2019
Confidential
Nokia AirScale RNC and AirScale BSC
Future-proof solutions for WCDMA and GSM controller implementation
Common Multi-tenancy Cost savings Processing
infrastructure through resources
2G 3G
between consolidation optimized
different AirScale BSC, AirSCale RNC VNFs according
technologies AirScale RNC AirScale AirScale BSC
RNC/BSC network
evolution
Nokia AirFrame Nokia AirFrame Georesiliency
Rackmount Openrack
From low to high High capacity edge and AirScale

Legacy controllers
capacity distributed regional datacenters AirScale AirScale RNC/BSC
edge datacenters RNC/BSC RNC/BSC
Technology agnostic Concurrent 2G/3G Efficient controller Optimize with

Investments with Nokia AirFrame Operation modernization resource scaling
3 © Nokia 2020
2016
Nokia AirScale BSC
Benefits
Future proof HW Site consolidation Common infrastructure
Re-useabilty through data center Less controllers

capacity sharing Less space Common racks and servers across
Efficient modernization radio technologies
OPEX savings AirScale

Reduced effort Flexible life-cycle
BSC
management
Less controllers
Less space
Deployment time Enhanced capacity management
Power saving
Enhanced SW management Resource scaling functionalities
4 © 2019 Nokia Confidential

Reference infrastructure
Nokia
NetAct CloudBand
Network
Director
Service, VNF and Infrastructure Description
(CBND)
NetAct
NetAct NetAct
OMS
Nokia
AirScale BSC, AirScale RNC
CloudBand
AirScale RNC AirScale BSC VNF
lifecycle management
Application
Manager
(CBAM)
NFVI
Nokia Cloud
Virtual Infrastructure R (NCIR) SW Virtual
Virtual Storage on Compute
Computing Network Nokia Cloud Infrastructure R
& Storage Nodes
(NCIR) SW on
Virtualization Layer Controller Nodes
Virtualized
Hardware resources Infrastructure
Computing Storage
Nokia
Network
AirFrame Manager(s)
Nokia Internal Use
Hardware Hardware Datacenter Solution (NDCS)
Hardware
55 ©
© Nokia
Nokia 2019
2018 Confidential
AirScale BSC
Overview
AirScale BSC combines the functionalities of

existing Nokia BSC solutions with cloud-based capabilities
Functional Architecture
AirScale BSC VN
F
application SW
In
NCIR f ra
s tru
Common infrastructure for all Cloud RAN products
ct
ur
e (AirScale BSC, AirScale RNC)
Nokia AirFrame HW

AirScale BSC – capacity comparision against Multicontroller BSC
*Erlangs / cabinet, RM19

Future proof Reduced effort
165 000 Erlangs • Re-useable • Simplified VNF deployment
• Common infrastructure • Concurrent operability with
between technologies multitenancy
*PDCH / TRX / BSC *BTS

connectivity /
8 / TRX
With resource scaling
cabinet,
22 000 RM19
*Data throughput
/ cabinet, RM19
6 6 Gbps
Site Consolidation Flexible and Agile
AirScale BSC
22 000 • Less controllers • Enhanced capacity
management
• Less space
• Resource scaling
• Efficient modernization
*TRX connectivity / cabinet, RM19
27 500
* Maximum capacity per cabinet Multicontroller BSC
77 ©
© Nokia
Nokia 2019
2018
AirScale BSC customer piloting
AirScale BSC was piloted in three commercial customer Example KPIs collected during the AirScale BSC piloting from one customer
networks having an overall pilot project coverage of 10 network – controller modernization : 56 existing BTS sites rehosted from
AirScale BSC VNFs and ~900 BTSs GSM
existing Flexi BSCSWtoRelease Subscription
a new AirScale BSC price
VNF
• SRS introduces mandatory pricing element with grant access to
existing and to new SW release(s) with new/updated content
AirScale BSC pilot configurations and summary
published during a valid subscription period
• Nokia AirFrame NDCS RM17 HW implementation with GSM Cloud Essential SW price
10 and 20 compute nodes • Essential SW pack contains initial and mandatory SW
• AirScale BSC single tenant deployments functionalities in all AirScale BSC offers
• AirScale BSC – AirScale BSC multitenancy : two
AirScale BSC VNFs (RD3_BSC 5500) in one cloud GSM Cloud Enhanced SW price
instance • Enhanced SW pack contains optional SW functionalities for all
• Stable KPIs with good level stability and performance AirScale BSC offers
After the pilot project closure, activities in pilot customer HVF and E-HVF SW price
networks are continuing • HVF & E-HVF SW contains optional SW functionalities in all
AirScale BSC offers
• AirScale BSC – AirScale RNC multitenant deployment is • Equal prices for inherited common GSM features
taken into live network operation • Cloud features are priced separately
• Rollout and controller modernization continues with
additional deployed AirScale BSC VNFs and additional Capacity price
rehosted BTS sites • SW capacity, to price and sell VNF SW and HW capacity
performance in AirScale BSC solution
8 © Nokia 2019
AirScale BSC, AirScale RNC – KPI comparision during network
implementation
Network performance comparision during network implementation Network performance comparision during network implementation
and rehosting, when BTS sites (4) were rehomed from mcBSC to and rehosting, when BTS sites (4) were rehomed from mcRNC to
GSM SW Release Subscription price
AirScale BSC VNF AirScale RNC VNF
• SRS introduces mandatory pricing element with grant access to
existing and to new SW release(s) with new/updated content
GSM Cloud Essential SW price

• Essential SW pack contains initial and mandatory SW
functionalities in all AirScale BSC offers
GSM Cloud Enhanced SW price

• Enhanced SW pack contains optional SW functionalities for all
AirScale BSC offers
HVF and E-HVF SW price

• HVF & E-HVF SW contains optional SW functionalities in all
AirScale BSC offers
• Equal prices for inherited common GSM features
• Cloud features are priced separately
Capacity price
• SW capacity, to price and sell VNF SW and HW capacity
9
Confidential
AirScale BSC, AirScale RNC - Press Releases
Advancing its digital transformation with Nokia, Telenor Pakistan deploys country's first 5G-ready cloud-based RAN platform and controllers
14 February 2019
Islamabad, Pakistan - Nokia's 5G-ready AirScale Cloud RAN solution and controllers have been successfully deployed by Telenor Pakistan, further advancing its
goal of digital transformation to optimize the end customer experience, improve total cost of ownership and quickly respond to emerging opportunities.
This marks the first deployment of the AirScale Base Station Controller (BSC) and AirScale Radio Network Controller (RNC) on AirFrame cloud infrastructure in
Pakistan, and the first cloud-based BSC deployment in the Middle East and Africa region.
The Nokia solution reduces network complexity and operational cost, allowing service providers to provide innovative services more cost effectively. The added
agility that this software delivers will enhance efficiency, and prepare them for 5G.
Khurrum Ashfaque, Chief Technology Officer, Telenor Pakistan, said: "Telenor Pakistan has always been a frontrunner in the growth of technology and
innovation. With a global purpose of connecting people to what matters most, we continue to empower the Pakistani society with our innovative digital initiatives.
Together with Nokia's cloud solutions, we are well on our way to accelerating digital transformation. We will have added flexibility to scale the radio network
resources based on demand as well as greater agility, which is critical as a significant percentage of our subscribers continue to use 2G and 3G services. With this
deployment, we will be able to introduce new services and solutions faster, and quickly take advantage of emerging business opportunities."
10
Confidential
Nokia cloud controllers AirScale BSC and AirScale RNC
Large scale commercial SRAN network
Required 2G and 3G controller capacity
Network elements to has been implemented with AirScale BSC
operate
and AirScale RNC. In total of 51 AirScale
BSC and AirScale RNC VNFs are getting
-40% their required HW capacity from HW
resource pools, containing in total of 29
Location 1 Nokia AirFrame/NCIR infrastructure
86 racks.
Location 2 Location 3 Similar capacity 2G and 3G controller
implementation with previous
conventional hardware-based Nokia
51 controller products would have required
86 BSC and RNC network elements. Now
with high capacity AirScale BSC and
AirScale RNC implementation, the total
amount of required network elements
Conventional hardware-based Nokia controllers
needed to be operated can be reduced by
AirScale BSC / RNC VNFs
40%

Nokia cloud controllers AirScale BSC and AirScale RNC
Controller modernization
Combine to Existing Nokia 2G and 3G controllers have been
concurrently operate in modernized with high capacity AirScale BSC and
common infrastructure AirScale RNC implementation. During controller
HW resource pool modernization existing BTS sites are rehomed to new
AirScale BSC VNF
AirScale controller VNFs. At the end old Nokia 2G and
AirScale RNC VNF
Off 3G controllers are removed from network operation.
Off
Common HW resource pool, provided by Nokia
AirFrame/NCIR infrastructure, serves both AirScale BSC
Controller location and AirScale RNC concurrently and allows to balance
Balance the resource resource usage between 2G and 3G controller VNFs
usage between 2G and through resource scaling functionality.
3G controller VNFs
through resource 51 High capacity AirScale BSC and AirScale RNC VNFs
scaling enable to combine both exisiting 2G and 3G controllers
into a single and common infrastructure HW resource
pool within the existing location. Required site space is
reduced by 20%

AirScale BSC pricing
AirScale BSC consists of six main pricing elements :
GSM SW Release Subscription price
• RGCS2001 GSM SW Release Subscription • SRS introduces mandatory pricing element with grant access to
• existing and to new SW release(s) with new/updated content
RGC2001 GSM Cloud Essential SW
• RGC2002 GSM Cloud Enhanced SW
• RGCxxxx HVF SW, multiple sales items GSM Cloud Essential SW price
• RGCxxxx E-HVF SW, multiple sales items • Essential SW pack contains initial and mandatory SW
functionalities in all AirScale BSC offers
• AirScale BSC capacity triggers
• ASBSC1001 Traffic Capacity, Erlangs GSM Cloud Enhanced SW price
• ASBSC1002 TRX Connectivity • Enhanced SW pack contains optional SW functionalities for all
• ASBSC1003 PCU Channel Connectivity AirScale BSC offers
HVF and E-HVF SW price

All these pricing components and items are important where SW • HVF & E-HVF SW contains optional SW functionalities in all
Release Subscription and Cloud Essential SW, together with AirScale BSC offers
capacity triggers, are mandatory • Equal prices for inherited common GSM features
• Cloud features are priced separately
Capacity price
• SW capacity, to price and sell VNF SW and HW capacity
13 © Nokia 2019
AirScale BSC is aimed to use SW Subscription sales concept
SW Subscription = Annual SW fee and Time limited SW RTU Subscription (LKs)

Optional • Multiple sales items AirScale BSC VNF
E-HVF SW • Content to increase in new releases New
functionalities services and functionalities priced
• Existing and new (E)-HVF features having
Optional HVF SW separate sales items
functionalities
AirScale Cloud Infrastructure

Solution
Standard Content SW Defines standard content in SW

Subscription Subscription BTS(s)
• Cloud Essential SW - Mandatory
• Cloud Enhanced SW – Optional
Cloud RAN Capacity •AirScale BSC capacity
Cloud RAN SW •Mandatory pricing component BB units
Release Subscription RF units
14 Cloud Infrastructure
01/04/2023 © Nokia 2016 • Data Center HW and SW pricing
Solution
Confidential (AirFrame HW & NCIR/CBAM SW)
AirScale BSC comparison against Multicontroller BSC
AirScale BSC VNF * Multicontroller BSC
TRX connectivity 8 800 >> mcBSC 4 400
PS data RTSL (MCS9) * 29 370 >> mcBSC 20 400

Traffic Handling Capacity 52 800 Erlangs >> mcBSC 26 400 Erlangs
* All defined maximum VNF level capacities cannot be reached simultaneously, check AirScale BSC reference deployments
* For equal comparision, PCU capacity is stated in terms of RTSLs (MCS9)
Five reference deployments :

Comparable mcBSC capacity
PS data RTSL (MCS9) PS data RTSL (MCS9)
TRX step (both TRX + PS data TRX BCN HW modules
* *
capacity considered)
RD1_BSC
1 100 2 670  S2 1 100 3 000 3
1100
RD2_BSC
3 300 13 350  S5 3 300 10 800 6
3300
RD3_BSC
5 500 8 900  S4 + S1 5 500 9 000 7
5500
RD4_BSC
8 800 29 370  S6 + S5 8 800 26 400 13
8800
RD5_BSCD
4 400 19 580  S7 4 400 20 400 8
4400
15 Confidential
AirScale BSC comparison against Multicontroller BSC - PCU
* For equal comparision, PCU capacity in terms Comparing units : Comparing configurations :
of RTSLs (MCS9) is used
Multicontroller BSC, capacity step 4
PCUM (BMPP2-B HW processing unit) • 5 x BCN HW modules
• 2560 PCU channels (MCS1 RTSL) • 13 active PCUM units
• 600 RTSL (MCS9)
•
BMPP2-B
BMPP2-B
BMPP2-B
• 550 BCFs 7 800 RTSLs for GPRS / EDGE
• 550 BTSs • 1.8 GPRS / EDGE RTSL per TRX
• 550 TRXs
* Multicontroller BSC – HW Rel2
AirScale BSC, RD4_BSC 8800

Virtual AirScale BSC PCUM
• 20 x compute nodes (RM17)
VNF (AirScale BSC) • 1640 PCU channels (MCS1 RTSL) • 33 active PCUM units
• 890 RTSL (MCS9)
• 550 BCFs • 29 370 RTSLs for GPRS / EDGE
PCUM VM • 550 BTSs • 3.3 GPRS / EDGE RTSL per TRX
• 550 TRXs
16 Confidential
AirScale BSC comparison against Multicontroller BSC – capacity steps
Multicontroller BSC capacity steps: AirScale BSC deployments: *
Maximum TRX 4400 mcBSC PS Capacity step 7 : RD5_BSCD

TRX 4400
Packet Abis channels for PS data / MCS9 RTSL 87040 / 20400 ext module 8 modules 4400 MCS9 RTSL 19580
Maximum TRX 4400 mcBSC PS Capacity step 6 : TRX 4400

ext module RD5_BSCD
Packet Abis channels for PS data / MCS9 RTSL 66560 / 15600 7 modules 4400 MCS9 RTSL 19580
Maximum TRX 4400 mcBSC PS Capacity step 5 : TRX 4400

ext module RD5_BSCD
Maximum TRX 4400 mcBSC TRX Capacity step 4 : TRX 5500

RD3_BSC
Packet Abis channels for PS data / MCS9 RTSL 33280 / 7800 ext module 5 modules 5500 MCS9 RTSL 8900

ext module RD2_BSC

RD2_BSC
Packet Abis channels for PS data / MCS9 RTSL 12800 / 3000 ext module
3 modules 3300 MCS9 RTSL 13350
Maximum TRX 1100 Capacity step 1 : TRX 1100

mcBSC basic RD1_BSC
Packet Abis channels for PS data / MCS9 RTSL 5120 / 1200 modules 2 modules 1100 MCS9 RTSL 2670
17
* AirScale BSC reference deployments can be adjusted with resource scaling after initial deployment and according infrastructure
For internal use
HW resource availability. Additionally RD4_BSC 8800 exceeds Multicontroller BSC capacity.
1 controller site – implementation with AirScale BSC / AirScale RNC
Overall dimensioning - (5500 TRX AirScale BSC VNFs), case example, Site A
5 Multicontroller racks within 1 controller site → 2 AirFrame racks within 1 controller site
compute triplets
VNF1
RD3_BSC 5500
VNF2
RD3_BSC 5500
VNF3
RC2
VNF4 Storage / compute triplet

RC2
Controller / compute triplet
mcBSC S4 mcBSC S4 mcBSC S1 mcRNC S3 mcRNC S3
© Nokia 2019 Confidential

1 controller site – implementation with AirScale BSC / AirScale RNC BoQ
Cumulative HW and Infrastructure view – Site A

-21%
Multicontroller AirScale
Perpetual Subscription
900 000
800 000
mcRNC Hardware mcBSC Hardware
700 000
600 000
500 000
AirFrame Hardware CBAM Software

400 000
300 000
200 000
100 000 NCIR Software
0
Year1 Year2 Year3 Year1 Year2 Year3
5 Multicontroller racks within 1 controller site → 1 AirFrame rack within 1 controller site (5500 TRX AirScale BSC VNFs)

AirScale BSC or Multicontroller BSC – BoQ comparison
BTS MSS MGW SGSN NetAct
Example comparison BoQs,
Network implementation in planning area Nokia Pricing Tool
and in BSC location :
• Erlangs : 43 200 Multicontroller BSC

• PDCH : 21 600
• Number of TRXs : 10 800
• Number of cells 3 600
Backbone • Number of BTSs : 1 200
Backhaul
BSC SITE
AirScale BSC
Network Infrastructure within
Cloud RAN
AirScale BSC • Required HW capacity for

VNF NASM implementation needs
AirScale BSC to be considered separately on
network level
• Overall CBAM
AirScale BSC implementation strategy and
VNF Multicontroller BSC HW capacity for CBAM
implementation needs to be
Multicontroller considered separately on
BSC network level
Note : Presented dimensioning is indicative and is subject to further analysis on

© Nokia 2019 actual traffic capacity requirements
AirScale RNC/BSC or Multicontroller RNC/BSC – BoQ comparison
WBTS BTS MSS MGW SGSN NetAct OMS Network implementation in planning area and
in RNC / BSC location : Example comparison BoQs,
Nokia Pricing Tool
• GSM Erlangs : 64 800 • CS BHCA : 296 651
• PDCH : 32 400 • PS BHCA : 320 197
• Number of TRXs : 16 200 • PS Session BHCA : 5 235 542 Multicontroller
• Number of cells 5 400 • AMR Erlangs : 7 935 RNC/BSC
• Number of BTSs : 1 800 • Iub DL throughput : 3 031 Mbps
• Iub UL throughput : 506 Mbps
Backbone
Backhaul • Number of cells 6 378
• Number iof BTSs : 1 547
RNC / BSC SITE
AirScale
Network Infrastructure within Cloud RAN
AirScale RNC VNF RNC/BSC
• Required HW capacity for NADCM
implementation needs to be considered
AirScale BSC VNF
separately on network level
AirScale RNC / BSC
• Overall CBAM implementation strategy and
AirScale BSC VNF HW capacity for CBAM implementation needs
to be considered separately on network level
Multicontroller
AirScale BSC VNF RNC / BSC
Multicontroller
RNC / BSC
Note : Presented dimensioning is indicative and is subject to further analysis on actual traffic capacity requirements
© Nokia 2019
Nokia AirScale BSC Sales Guide – Summary for offering
VNF capacity Infrastructure Comparison

• Define the required controller • Define the required Nokia • Only compare against
capacity (RNC and BSC) on AirFrame HW capacity for multicontrollers on controller site
physical site level controller (RNC and BSC) level and in terms of comparable
deployment – use full rack Nokia site level capacity
AirFrame HW implementations
• Consider :
1. Existing distributed controller
• Use :
sites
1. AirScale BSC – AirScale BSC
2. Centralized data centers for
multi-tenancy
consolidation
2. AirScale BSC – AirScale RNC
multi-tenancy

Centralized license management based on CLS and SWEM
No license key installations on AirScale BSC NEs
• No physical license keys in the network element. Automatic license allocation through CLS. SWEM regularly supervices and executes RTU verification and can initiate
limitation action in AirScale BSC VNF in case of RTU not granted.
• No physical license keys in NEs, License pooling
• Dedicated sales items for AirScale BSC - AirScale BSC ASW features, AirScale BSC capacity licenses
Centralized License Server NetAct

RTU request SW usage info
AirScale BSC VNFs
CLS SWEM PM
RTU response
Regular RTU
CM
verification by
SWEM
RTU not granted
License violation identified RTU not RTU not granted alarm

granted
License missing alarm Limitation action
LK Pools
SWEM = SW Entitlement Manager

CLS = Centralized License Server
RTU = Right To Use
23 © Nokia 2019
Confidential
PM based licenses and CM based licenses
Overview
1b. Feature usage from SWEM = Software Entitlement Manager
4a. If additional capacity needed from the CM data CLS = Centralized License Manager
pool and available  capacity reduced from NE = Network Element
the pool and SWEM assigns to NE (book
keeping in SWEM) NetAct
4a
Centralized 1b 4b. If no capacity available:
License Server - SWEM generates license missing alarm
SWE 4b and can trigger traffic limitation
CLS
3 M CM
3. If current value > PM

previous max, SWEM 2 AirScale BSC VNFs
checks from CLS, if
sufficient license
1a
Traffic limitation
capacity is available
LK Pools
in license pool 2. SWEM calculates PM 1a. For PM based capacity
based capacity usage licenses: NetAct retrieves
values and compares CM NE measurements (e.g.
data 60min interval)
24 © Nokia 2019
AirScale BSC and related infrastructure and management sales structures
AirScale BSC
AirScale BSC SW NCIR SW NDCS NASM CBAM SW

Nokia AirFrame NADCM
HW + SW HW + SW
AirScale BSC VNF Infrastructure *
* Sales structures and sales items of NCIR, NDCS, NASM, NADCM and CBAM are defined and
maintained separately by respective product lines. Further information can be found in the related
product specific sales guides.
25 © Nokia 2019
Confidential
V
N
AirScale BSC – VNF SW sales structures F
AirScale BSC SW
AirScale BSC ASBSC 19 SW AirScale BSC VNF Network

AirScale BSC capacity licenses AirScale BSC ASW
SW Release Subscription delivery items element ID
GSM SW Release Subscription TL CLTU Traffic capacity 1 Erl TL CLTU GSM Cloud Essential SW TL CLTU AirScale BSC 19 SW e-media AirScale BSC VNF NEID
RGCS2001.TTL ASBSC1001.TTL RGC2001.TTL RGC19SW ASBSC3001
BSC 19 Release LK TRX connectivity 1 TRX TL CLTU GSM Cloud Enhanced SW TL CLTU AirScale BSC 19 SW 1xDVD
RGCREL19LK ASBSC1002.TTL RGC2002.TTL RCG19CM
BSC 20 Release LK PCU connectivity 256 Ch TL CLTU BSC Cloud SW migration TL CLTU AirScale BSC 19 FP CSW e-media
RGCREL20LK ASBSC1003.TTL RGC2003.TTL RGC19SWCFP AirScale BSC 19
SW delivery items
for AirScale BSC
AirScale BSC Product Configuration Items (PCI) HVF / E-HVF Feature AirScale BSC 19 FP SW 1xDVD 19 FP1, FP2
Code Description RGC0xxx.TTL RGC19CMCFP
AIRSCALE-BSC-NEID AirScale BSC VNF Network element ID HVF / E-HVF Feature
RGC0xxx.TTL
CBSC0001 Cloud AirScale BSC LTU and SW HVF / E-HVF Feature
CBSC0002 Cloud AirScale BSC Physical Delivery RGC0xxx.TTL
CBSC0003 Cloud AirScale BSC SW LK
26 © Nokia 2019
Confidential
V
N
AirScale BSC – VNF SW sales structures F
AirScale BSC SW
ASBSC 20 SW AirScale BSC

delivery items OEM SW
AirScale BSC 20 SW e-media

6WINDSW 1 TRX LTU
RGC20SW
OEM6WINDSW0002
AirScale BSC 20 SW 1xDVD

RCG20CM
AirScale BSC 20 FP CSW e-media

RGC20SWCFP AirScale BSC 20
SW delivery items
for AirScale BSC
AirScale BSC 20 FP SW 1xDVD 20 FP1, FP2
RGC20CMCFP
27 © Nokia 2019
Confidential
V
N
Mandatory NE ID for AirScale BSC VNF F
• NEID : Network Element Identifier, Nokia level unique serial number for each AirScale BSC VNF. NEID is an input
parameter entered in CBAM GUI for AirScale BSC instantiation.
NE ID generation:
• SW PCI and sales item below needs be ordered for each AirScale VNF in order to to get the NEID delivered
o PCI AIRSCALE-BSC-NEID AirScale BSC VNF Network element ID

o Sales item, qty : 1 pcs ASBSC3001 AirScale BSC VNF NEID
• IPC configurator model for AirScale BSC includes 1 pcs of sales item ASBSC3001 into each new AirScale BSC
VNF configuration BoQ automatically
28 2019
Confidential
V
N
AirScale BSC lifecycle management with Nokia VNFM – AirScale BSC NEID F
AirScale BSC instantiation – setting the Network Element ID

Note : bsc_c_number needs mandatorily
to be ordered with sales item :
Preconditions : VNFD
package uploaded to CBAM ASBSC3001 AirScale BSC VNF NEID
catalog, VNF created in
CBAM
2
1. Select ’Modify’ → extension
2. Modify ’bsc_c_number’
3. Press ’Modify
29 © 2019 Nokia
V
N
AirScale BSC SW sales items F
Subscription model
• Subscription model is the primary option for AirScale BSC SW and capacity
• Term licenses for subscription model are identified with TL in sales item name and code
• RGCS2001 GSM SW Release Subscription is a mandatory sales item
• RGCREL19LK BSC 19 Release LK for controlling release subscription and for enabling visibility of release specific features
• RGCREL20LK BSC 20 Release LK for controlling release subscription and for enabling visibility of release specific features
LKs and invoice items

• AirScale BSC sales items are categorized into two groups - license key (LK) items and invoice items (CLTU)
• LKs are used to activate the capacity support
• CLTU invoice items are for invoicing only
30 © Nokia 2019
Confidential
V
N
AirScale BSC - Capacity SW sales items F
ASBSC1001 Traffic capacity 1 Erl

• License enables AirScale BSC to support 1 Erlang of voice traffic
ASBSC1002 TRX connectivity 1 TRX
• License enables AirScale BSC to have connectivity for 1 TRX
ASBSC1003 PCU connectivity 256 Ch
• License enables AirScale BSC to have connectivity for 256 PCU channels
31 © Nokia 2019
Confidential
V
N
AirScale BSC - ASW sales items F
RGC2001 GSM Cloud Essential SW

• This sales item includes GSM SW features from the Essential category, and additionally new essential AirScale BSC SW features and
GSM SW features being mandatory for the operation of the product. See IRP list for detailed content of this SW package
RGC2002 GSM Cloud Enhanced SW
• This sales item includes GSM SW features from the Enhanced category and additionally new enhanced AirScale BSC SW features. See
IRP list for detailed content of this sw package
RGC0xxx HVF / E-HVF SW features
• GSM SW features and Cloud RAN specific HVF / E-HVF features. See IRP list for full list of sales items
32 © Nokia 2019
Confidential
V
N
Mandatory OEM SW for AirScale BSC VNF F
• OEM SW sales item is mandatory for each AirScale BSC VNF .
• OEM SW sales item to be included in AirScale BSC VNF SW BoQ as below. Qty of sales item is according AirScale
BSC VNF TRX capacity. OEM SW sales item is defined for 6WIND royalty licenses, being volume based with
AirScale BSC
o OEM6WINDSW0002 6WINDSW 1 TRX LTU
• IPC configurator model for AirScale BSC includes sales item OEM6WINDSW0002 into each AirScale BSC VNF
configuration BoQ automatically
33 2019
Confidential
SW Transformation fee to migrate bare metal BSC install base to Cloud RAN
I.e. legacy BSC to AirScale BSC
SW Cloud RAN GSM (time limited SW RTU) Migration
Bare Metal GSM
(perpetual SW RTU/time limited SW RTU) Transformation customer pricing
System/Cloud/VNF BTS
Sales opportunity:
Capacity Capacity (BSC/VNF & BTS)
- SW Transformation fee
GSM SW
- New Erl capacity

(E)-High Value Functionalities (E)-High Value Functionality subscriptions
- New SW Release Subscription, SRS
Migration from - New HVF + E-HVF functionalities
Essential & Enhanced packs bare metal BSC Essential & Enhanced Subscriptions
Existing Installed base and valid in existing
to AirScale BSC BSC:
SW Release Subscription
SW Release Upgrade
- Installed TRX & PCU capacity
- Installed STD + HVF + E-HVF SW
GSM HW
HWA HWA
- RU to replace with SRS
Physical HW BTS Physical HW BTS
Sales opportunity:
Physical HW Controllers - BTS HW updates
Opera- Data Center
NCIR, CBAM Sales opportunity:

AirFrame HW - Nokia Data Center solution
CloudBand Sales opportunity:

bility
NetAct NetAct - NetAct Cloud
01/04/2023 © Nokia 2019

Migration customer pricing
Sales opportunity Migration pricing, BSC SW to AirScale BSC SW
SW Transformation - License to upgrade bare metal BSC SW to AirScale BSC SW and harmonize content to be
comparable. This enables to reuse installed SW functionalities and capacity  Cloud
enablement for the bare metal SW
- Cloud Essential SW is part of SW Transformation fee
- SW Transformation fee is the SW value difference between BSC vs AirScale BSC
Installed TRX & PCU capacity - Already sold and valid in AirScale BSC
- Additional AirScale BSC capacity shall be priced additionally
Installed STD, HVF, and E-HVF - Installed functionalities are part of SW Transformation fee
- New and Cloud features shall be priced additionally
CAP: Erl, Installed TRX&PCU - AirScale BSC SW capacity Erl is a new SW capacity price and shall be priced from zero - Erl
has been bare metal BSC HW capacity pricing component
- Installed based TRX, and PCU capacity part of SW transformation fee
- Capacity extensions shall be priced additionally
SW Release Upgrade - RU shall be replaced with SW Release Subscription
01/04/2023 © Nokia 2019

AirScale BSC - ASW sales items
RGC2003 BSC Cloud SW migration
• When modernizing existing bare metal products, e.g. Flexi BSC or Multicontroller BSC with AirScale BSC, SW and capacity migration
to new Cloud RAN SW is needed
• BSC Cloud SW migration (RGC2003) sales item is defined for this purpose. Sales item enables the capacity licenses worth of capacity of
the legacy product to be delivered to AirScale BSC without new capacity invoice
• Additionally, this sales item enables the Cloud RAN functionalities that have not been included in legacy GSM Essential SW
• Note: the capacity migration does not include the Erlang capacity license ASBSC1001, erlang capacity has been part of the legacy
BSC HW price. Erlang capacity needs to be priced and ordered from zero in case of legacy migration to AirScale BSC
36 © Nokia 2019
Confidential
O
pe
nR
AirScale BSC reference deployments – Nokia AirFrame, OpenRack ac
k
• Five reference deployments for initial dimensioning and default deployment compute triplets
• HW configuration for the used reference deployment in standalone AirScale BSC

installation can be selected according to network implementation requirements.
• Reference deployments can be scaled with AirScale BSC resource scaling operations
after default instantiation according required network capacities.
• AirFrame hardware can be flexibly expanded by simply adding more compute nodes :
hardware scaling step size is one OR triplet
Leaf switches
HW management switch
PCU Ch for Memory
Reference deployment TRX vCPU (#) Disk (GB)
GPRS/EDGE (GB)
RD1_BSC 1100 1100 4864 136 180 337
RD2_BSC 3300 3300 24576 328 436 487
RD3_BSC 5500 5500 16384 328 436 477

Storage / compute triplet
RD4_BSC 8800 8800 54016 682 908 757
RD5_BSCD 4400 4400 35840 442 588 577 Controller / compute triplet
Note : Complete OR system HW configuration needs to be defined separately according to required AirScale BSC VNF
deployment. System HW configuration includes storage, controller and compute triplets as well as additional servers Virtual Infrastructure (Host)
potentially required to reach OR HW scaling step (servers in reference OR HW implementation can be scaled on a NCIR W
granularity of one OR triplet). Additionally failover server capacity is considered in a complete system configuration NDCS OR Hardware (Nokia AirFrame)

O
R1
AirScale BSC reference deployments – Nokia AirFrame, OR18 / NCIR19 8
Standalone system configuration, RC0994

• Complete standalone system configuration with OR18 Skylake / NCIR19 based
infrastructure contains :
1. One Storage / Compute triplet

2. One Controller / Compute triplet
3. Compute triplets according required AirScale BSC reference deployment
4. Failover server capacity
5. Additional servers to reach OR18 Skylake HW capacity step of one triplet
• Controller / Compute and Storage / Compute triplets provide HW caoacity also for VNF
use Leaf switches
Additional
Storage / Controller / Failover
Reference deployment Compute Compute
Compute
server
servers to Total number of RD4_BSC 8800
nodes reach OR OR triplets
triplet triplet capacity
triplet
Compute nodes
Failover server capacity
RD1_BSC 1100 1 1 0 1 2 3 Additional servers to reach OR
triplet
RD2_BSC 3300 1 1 3 1 2 4
RD3_BSC 5500 1 1 3 1 2 4
RD4_BSC 8800 1 1 11 1 0 6
Storage / Compute triplet
RD5_BSCD 4400 1 1 6 1 2 5 Controller / Compute triplet

O
A R1
AirScale BSC reference deployments – Nokia AirFrame, OR19 / NCIR19 SB
SC
20
9
Standalone system configuration, RC1764 FP

1
• Complete standalone system configuration with OR19 Cascade Lake / NCIR19 based infrastructure
contains :

3. Compute triplets according required AirScale BSC reference deployment
5. Additional servers to reach OR19 Cascade Lake HW capacity step of one triplet
• Controller / Compute and Storage / Compute triplets provide HW capacity also for VNF use.
Leaf switches
Additional
Compute servers to Total number of
Reference deployment Compute Compute server
triplet RD4_BSC 8800
RD1_BSC 1100 1 1 0 1 2 3 Compute nodes

RD2_BSC 3300 1 1 1 1 1 3 Additional servers to reach OR
triplet
RD3_BSC 5500 1 1 1 1 1 3
RD4_BSC 8800 1 1 7 1 1 5
RD5_BSCD 4400 1 1 3 1 2 4 Controller / Compute triplet

Ra
ck
m
AirScale BSC reference deployments – Nokia AirFrame, Rackmount ou
nt
• Five reference deployments for initial dimensioning and default deployment compute nodes, failover server
capacity
• HW configuration for the used reference deployment in standalone AirScale BSC
installation can be selected according to network implementation requirements.
• Reference deployments can be scaled with AirScale BSC resource scaling operations
after default instantiation according required network capacities.
• AirFrame hardware can be flexibly expanded by simply adding more compute nodes :
hardware scaling step size is one server
Leaf switches
PCU Ch for Memory
Reference deployment TRX vCPU (#) Disk (GB) *
GPRS/EDGE (GB)
Storage nodes
RD1_BSC 1100 1100 4864 136 180 287
Controller nodes
RD2_BSC 3300 3300 24576 328 436 362
RD3_BSC 5500 5500 16384 328 436 357 compute nodes, failover server
capacity
RD4_BSC 8800 8800 54016 682 908 497
RD5_BSCD 4400 4400 35840 442 588 407
Note : Complete Nokia AirFrame Rackmount system HW configuration needs to be defined separately according to
required AirScale BSC VNF deployment. System HW configuration includes storage, controller and compute servers.
Virtual Infrastructure (Host)
Additionally failover server capacity is considered in a complete system configuration.
NCIR SW
* AirScale BSC deployments ontop of AirFrame rackmount are utilizing optimized Cinder volumes for ETM, PCUM NDCS RM Hardware (Nokia AirFrame)
and GPLU VNFCs

A RM
SB
AirScale BSC reference deployments – Nokia AirFrame, RM19 / NCIR19 SC
20
19
FP
Standalone system configuration, RC0952 20
A
• Complete standalone system configuration with RM19 Cascade Lake / NCIR19 based infrastructure
contains :
1. Two Storage / Compute servers

2. Three Controller / Compute servers
3. Compute servers according required AirScale BSC reference deployment
• Controller / Compute and Storage / Compute servers provide HW capacity also for VNF use. RD4_BSC 8800
Leaf switches
Storage / Failover
Controller / Compute Total number of
Reference deployment Compute server
Compute servers servers servers Storage / Compute servers
servers capacity
Controller / Compute servers
RD1_BSC 1100 2 3 0 1 6
Compute servers
RD2_BSC 3300 2 3 2 1 8 Failover server capacity
RD3_BSC 5500 2 3 2 1 8
RD4_BSC 8800 2 3 8 1 14
RD5_BSCD 4400 2 3 4 1 10

V
N
AirScale BSC network connectivity and traffic handling capacity F
Network connectivity and capacities of AirScale BSC reference deployments :
RD1_BSC RD2_BSC RD3_BSC RD4_BSC RD5_BSCD

Description 1100 3300 5500 8800 4400
Network connectivity
Number of TRXs TRX 1100 3300 5500 8800 4400
Number of cells BTS, SEG 1100 3300 4400 4400 4400
Number of BTS sites BCF 1100 3300 4400 4400 4400
User plane capacity
Erlangs Erlangs 6600 19800 33000 52800 26400
PCU Channels for GPRS / EDGE PCU channel 4864 24576 16384 54016 35840
Note : Stated traffic handling capacities of AirScale BSC reference deployments are defined against the Nokia nominal traffic profile

V
N
AirScale BSC deployment F
On reference Nokia AirFrame HW

Maximum values for one AirScale BSC VNF *
VNF (AirScale BSC) VNF1
8 800 TRX
VM
4 400 BTS
52 800 Erlangs Virtual Infrastructure (Host)

NCIR SW
PCU channels for NDCS Hardware
GPRS/EDGE : scalable upto (Nokia AirFrame)
100 PCU VMs according HW
resource availability *
Elasticity enables ’any size’ AirScale BSC within maximum VNF level capacities according HW resource
availability
* Maximum VNF level capacities are defined against reference HW configurations
* Depending on infrastructure implementation, all defined maximum VNF level capacities cannot be reached simultaneously, check AirScale BSC reference deployments
* Up 34 PCU VMs with AirScale BSC 19 FP1 (including spare PCUM VMs)

O
R1
Efficient AirScale BSC deployment with multi-tenancy 8
RC0994
Nokia AirFrame OR18 Skylake / NCIR19
Multiple AirScale BSC VNFs in one cloud instance :
RD1_BSC RD2_BSC
• 8 AirScale BSC VNFs in one Nokia AirFrame installation when instantiated 1100 3300
RD3_BSC
5500 RD4_BSC
with reference deployment RD1_BSC 1100 8800
• Efficient HW resource utilisation within the cloud infrastructure, logical BSC RD1_BSC
1100 RD2_BSC
network structure can be maintained during modernisation 3300
RD3_BSC
5500
RD1_BSC
1100
Reference deployment Number of tenants RD2_BSC RD3_BSC

RD1_BSC 3300 5500
1100
RD1_BSC 1100 8
RD1_BSC RD2_BSC RD3_BSC
1100 RD4_BSC
RD2_BSC 3300 6 3300 5500
8800
RD1_BSC
RD3_BSC 5500 6 1100
RD2_BSC RD3_BSC
RD4_BSC 8800 2 RD1_BSC
3300 5500
1100
RD5_BSCD 4400 4
RD1_BSC RD2_BSC RD3_BSC
1100 3300 5500
Note : Complete OR18 system HW configuration needs to be defined separately
according to required AirScale BSC VNF deployment. System HW configuration includes
storage, controller and compute triplets as well as additional servers potentially required
to reach OR18 HW scaling step (servers in reference OR18 HW implementation can be
scaled on a granularity of one OR triplet). Additionally failover server capacity is
considered in a complete system configuration

O
R1
AirScale BSC reference deployments – Nokia AirFrame, OR18 / NCIR19 8
Multitenant system configuration, RC0994

• Complete multitenant system configuration with OR18 Skylake / NCIR19 based infrastructure contains :

3. Compute triplets according required AirScale BSC reference deployments
4. Failover server capacity 2 x RD4_BSC 8800
Compute nodes
• Controller / Compute and Storage / Compute triplets provide HW capacity also for VNF use. Required amount of Failover server capacity
Additional servers to reach OR
HW resources is defined based on the required amount of virtual resources according deployed VNFs – HW triplet
resource utilisation needs to remain below 80% (excl. failover server capacity). In minimum there needs to be
failover server capacity worth of one full server
Leaf switches
Additional
Number Storage / Controller / Failover
Reference deployment of Compute Compute server Compute nodes
tenants triplet triplet capacity Failover server capacity
triplet
triplet
RD1_BSC 1100 8 1 1 21 1 2 10
RD2_BSC 3300 6 1 1 40 1 1 16
RD3_BSC 5500 6 1 1 40 1 1 16
RD4_BSC 8800 2 1 1 27 1 2 12
RD5_BSCD 4400 4 1 1 36 1 2 15 Controller / Compute triplet

O
A R1
Efficient AirScale BSC deployment with multi-tenancy SB
SC
20
9
RC1764 FP
1
Nokia AirFrame OR19 Cascade Lake / NCIR19
RD1_BSC
• 8 AirScale BSC VNFs in one Nokia AirFrame installation when instantiated 1100
with reference deployment RD1_BSC 1100 RD2_BSC RD3_BSC RD4_BSC
3300 5500 8800
1100
network structure can be maintained during modernisation RD2_BSC RD3_BSC
RD1_BSC 3300 5500
1100
RD2_BSC RD3_BSC
Reference deployment Number of tenants RD1_BSC 3300 5500 RD4_BSC
1100 8800
RD2_BSC RD3_BSC
RD1_BSC 1100 8 3300 5500
RD1_BSC
1100
RD2_BSC 3300 7 RD2_BSC RD3_BSC
RD1_BSC 3300 5500
RD3_BSC 5500 7 1100 RD4_BSC
RD2_BSC RD3_BSC
RD4_BSC 8800 3 8800
RD1_BSC 3300 5500
1100
RD5_BSCD 4400 5 RD2_BSC RD3_BSC
RD1_BSC 3300 5500
1100
Note : Complete OR19 system HW configuration needs to be defined separately
according to required AirScale BSC VNF deployment. System HW configuration includes
storage, controller and compute triplets as well as additional servers potentially required
to reach OR19 HW scaling step (servers in reference OR19 HW implementation can be
scaled on a granularity of one OR triplet). Additionally failover server capacity is
considered in a complete system configuration

O
A R1
AirScale BSC reference deployments – Nokia AirFrame, OR19 / NCIR19 SB
SC
20
9
Multitenant system configuration, RC1764 FP

1
• Complete multitenant system configuration with OR19 Cascade Lake / NCIR19 based infrastructure contains :

3. Compute triplets according required AirScale BSC reference deployments
4. Failover server capacity 3 x RD4_BSC 8800
5. Additional servers to reach OR19 Cascade Lake HW capacity step of one triplet
Compute nodes
• Controller / Compute and Storage / Compute triplets provide HW capacity also for VNF use. Required amount of HW Failover server capacity
resources is defined based on the required amount of virtual resources according deployed VNFs – HW resource Additional servers to reach OR
triplet
utilisation needs to remain below 80% (excl. failover server capacity). In minimum there needs to be failover server
capacity worth of one full server
Leaf switches
Additional
Number Storage / Controller / Failover
Reference deployment of Compute Compute server Compute nodes
tenants triplet triplet capacity Failover server capacity
triplet
triplet
RD1_BSC 1100 8 1 1 15 1 2 8
RD2_BSC 3300 7 1 1 36 1 2 15
RD3_BSC 5500 7 1 1 36 1 2 15
RD4_BSC 8800 3 1 1 32 1 0 13
RD5_BSCD 4400 5 1 1 35 1 0 14 Controller / Compute triplet

A RM
SB
Efficient AirScale BSC deployment with multi-tenancy SC
20
19
FP
RC0952 20
A
Nokia AirFrame RM19 Cascade Lake / NCIR19
• 8 AirScale BSC VNFs in one Nokia AirFrame installation when instantiated RD1_BSC
1100
with reference deployment RD1_BSC 1100 RD2_BSC RD3_BSC RD4_BSC
3300 5500 8800
1100
network structure can be maintained during modernisation RD2_BSC RD3_BSC
3300 5500
RD1_BSC
1100
RD2_BSC RD3_BSC
Reference deployment Number of tenants 3300 5500
RD1_BSC RD4_BSC
1100 8800
RD2_BSC RD3_BSC
RD1_BSC 1100 6 3300 5500
RD1_BSC
RD2_BSC 3300 5 1100
RD2_BSC RD3_BSC
3300 5500
1100
1100
RD5_BSCD 4400 3
RD1_BSC
1100
Note : Complete RM19 Cascade Lake system HW configuration needs to be defined
separately according to required AirScale BSC VNF deployment. System HW
configuration includes storage, controller and compute nodes. Additionally failover server
capacity is considered in a complete system configuration

A RM
SB
AirScale BSC reference deployments – Nokia AirFrame, RM19 / NCIR19 SC
20
19
FP
Multitenant system configuration, RC0952 20
A
• Complete multitenant system configuration with RM19 Cascade Lake / NCIR19 based infrastructure contains :
1. Two Storage / Compute nodes

2. Three Controller / Compute nodes
3. Compute nodes according required AirScale BSC reference deployments 2 x RD4_BSC 8800
Compute servers
• Controller / Compute and Storage / Compute nodes provide HW capacity also for VNF use. Required amount of HW Failover server capacity
resources is defined based on the required amount of virtual resources according deployed VNFs – HW resource
utilisation needs to remain below 80% (excl. failover server capacity). In minimum there needs to be failover server
capacity worth of one full server
Leaf switches
Number of Compute Total number of
tenants servers servers
servers servers capacity Storage / Compute servers
Controller / Compute servers
RD1_BSC 1100 6 2 3 11 1 17
RD2_BSC 3300 5 2 3 25 1 31 Compute servers

RD3_BSC 5500 5 2 3 25 1 31
RD4_BSC 8800 2 2 3 21 1 27
RD5_BSCD 4400 3 2 3 20 1 26

V
N
AirScale BSC / AirScale RNC multi-tenancy F
Optimised TCO - AirScale BSC and AirScale RNC VNFs sharing the same cloud instance
• Concurrent operation – common cloud infrastructure accross technologies
• Optimised TCO and efficient HW resource utilization within the shared cloud infrastructure - available resources in data center can be used for both;
for GSM controller implementation and for WCDMA controller implementation
• Reference Nokia AirFrame HW :

• AirFrame NDCS RM17 / NDCS OR 18 (ASBSC 19 FP3) / NDCS OR 19 (ASBSC20 FP1) / NDCS RM19 (ASBSC20 FP3)
1 2 3
Define required BSC capacity on Select AirScale BSC reference
controller site level according network deployment(s) meeting the needs of
dimensioning required BSC capacity Combine selected AirScale BSC and
AirScale RNC reference deployments
Define required RNC capacity on Select AirScale RNC reference into the same cloud instance for
controller site level according network deployment(s) meeting the needs of optimized HW resource usage
dimensioning required RNC capacity

Concurrent GSM/WCDMA operation with multi-tenancy
RC0903
AirScale BSC and AirScale RNC VNFs sharing the cloud instance :
• Efficient HW resource utilisation within the cloud infrastructure - available resources in data
center can be used for both, GSM controller implementation and WCDMA controller
implementation
• Concurrent operation - common infrastructure across technologies
• Reference Nokia AirFrame HW: AirFrame NDCS RM19 Cascade Lake AirScale RNC VNF
AirScale BSC VNF

Examples : AirScale BSC and AirScale RNC VNFs – sharing the cloud
AirScale RNC reference
instance *
Reference HW, NDCS RM19 number
Reference deployment
deployment of servers *
RD1_BSC 1100 + RC1 → 8

RD2_BSC 3300 + RC2 → 15
RD3_BSC 5500 + RC2 → 15
* Maximum size of cloud instance : One rack Virtual Infrastructure

* In reference to Nokia AirFrame NDCS RM19 Cascade Lake HW NCIR SW
* Failover server capacity worth of one server included NDCS RM19 Hardware Common infrastructure
(Nokia AirFrame) AirFrame HW, NCIR SW
Common management
NetAct, CBAM

AirScale BSC and AirScale RNC deployment on servers
Deployment rules - hardware and software extension
MCMU RRMU 0 EIPU 2
0
AirScale BSC and AirScale RNC deployment SNServerOMU
#12 Server #2
BCXU Server #3
• MCMUs are placed in one anti-affinity server group: active and spare VMs are located
on different physical servers BCXU CSPU ETMA
• CFPUs and SNs are placed in one anti-affinity server group: active and spare VMs are
located on different physical servers
ETME MCMU SN EIPU 1
• RRMUs are placed in one anti-affinity server group: active and spare VMs are located 1
on different physical compute nodes Server #4 Server
EIPU 0 #12 Server #6
CSPU
• EIPUs are placed in one anti-affinity server group: EIPU pair (i.e. active and spare
VM) are located on different physical servers USPU PCUM USPU
• BCXUs, ETMAs, ETMEs, CSPUs, USPUs and PCUMs are allocated by OpenStack to
servers dynamically, balancing the resource usage
CFPU 0 BCXU RRMU 1
Capacity extension
Server #7
CSPU Server
EIPU 3 #12 Server #9
CSPU
• If free HW resources are available, VMs can be scaled out.
ETMA USPU
• If all HW resources are in use already, HW capacity must be extended first by adding
servers in a granularity of one OR triplet
• CFPU 1 USPU
VNF capacity can be then expanded via scale-out of VMs
PCUM
Server #12 ETME
Server #12 Server #12
Note : Simplified view - in actual operation VMs are allocated by OpenStack dynamically to servers SN

V
N
AirScale BSC / AirScale RNC multi-tenancy F
Examples of combined reference deployments

• AirScale BSC and AirScale RNC reference deployments can be combined into the same cloud instance – available resources in the data
center can be used for both
• Similarly as with single tenant deployments, also with all multi-tenant deployments, maximum size of the cloud instance equals to one
rack
• Available failover HW resources for VNF level redundancy models can be optimized – common failover HW resources for both
AirScale BSC and AirScale RNC VNFs can be considered in the amount of required servers
AirScale RNC Number of

reference AirScale BSC servers, NDCS
deployment reference deployment RM19
Examples of combined reference deployments in the same cloud instance
One small size RNC and one small size BSCs 1 x RC1 + 1 x RD1_BSC 1100 8
One small size RNC and one medium size BSC 1 x RC1 + 1 x RD2_BSC 3300 12
One small size RNC and one large size BSC 1 x RC1 + 1 x RD3_BSC 5500 12
One medium size RNC and one small size BSC 1 x RC2 + 1 x RD1_BSC 1100 11
One medium size RNC and one medium size BSC 1 x RC2 + 1 x RD2_BSC 3300 15
One medium size RNC and one large size BSC 1 x RC2 + 1 x RD3_BSC 5500 15

• AirScale BSC and AirScale RNC implementation in a
AirScale BSC / AirScale RNC implementation country having 16 distributed controller sites – both GSM
and WCDMA capacity is needed on all areas
Example of multi-tenant deployment • Required BSC and RNC capacity is defined on controller
site level and required AirScale BSC and AirScale RNC
reference deployments are selected
1 • Controller sites having capabilities for AirScale BSC /
8 AirScale RNC multi-tenancy are identified
RD2_BSC 3300 4
RC1
RD2_BSC 3300
7 RD3_BSC 5500 Identified controller sites with reference deployment
RC2 combinations having capabilities for multi-tenancy
RC1 RD3_BSC 5500
2 RC1 E.g. controller site 8 :
14
15 RD4_BSC 8800
6
RC3 5 RD2_BSC 3300
RD2_BSC 3300 RD3_BSC 5500 RC1
RC1 RC2 RD3_BSC 5500
16 RC2 8 One AirFrame rack, 20
RD4_BSC 8800 11 compute nodes
RC2
3 RD3_BSC 5500
RD3_BSC 5500 RC2
RD4_BSC 8800
RD2_BSC 3300 13 RC1
RC3
RD3_BSC 5500 10
RC2
RD3_BSC 5500 38% reduction in required amount of AirFrame HW
9 RC2
with multi-tenancy
12 RD2_BSC 5500 AirScale BSC / AirScale RNC multi-
AirFrame racks
Avg. Airframe racks
RC1 tenancy example per controller site
RD4_BSC 8800
RD3_BSC 5500 Standalone deployment 34 2.1
RC2
With multi-tenancy 21 1.3

Concurrent GSM/WCDMA operation with multi-tenancy
AirScale BSC and AirScale RNC VNFs sharing the infrastructure : compute triplets
• Efficient HW resource utilisation within the infrastructure - available resources in data

center can be used for both, GSM controller implementation and WCDMA controller
implementation
• Concurrent operation - common infrastructure across technologies
• Reference Nokia AirFrame HW: AirFrame NDCS OR19
Examples of a AirScale BSC ↔ AirScale RNC multitenant deployments :

Leaf switches
16500 GSM TRXs and 28 Gbps for a GSM/WCDMA controller location :
AirScale BSC reference AirScale RNC reference Reference HW, NDCS OR19 number
deployments deployments of triplets
3 x RD3_BSC 5500 + 1 x RC3 → 11 Storage / compute triplet
Controller / compute triplet

11000 GSM TRXs and 38 Gbps for a GSM/WCDMA controller location :
AirScale BSC reference AirScale RNC reference Reference HW, NDCS OR19 number Common infrastructure
deployments deployments of triplets AirFrame HW, NCIR SW
Common management
2 x RD3_BSC 5500 + 3 x RC2 → 11 NetAct, CBAM

RM
AirScale BSC / AirScale RNC multi-tenancy

1
un 7 H
de W
rp d
ha eli
Example BoQs se ve
-o rie
ut s
Multitenancy : AirScale BSC and AirScale RNC VNFs sharing the same cloud instance
AirScale BSC / AirScale RNC multitenancy, example BoQ (NDCS RM17) :
AirScale BSC / AirScale RNC multitenancy, example BoQ (NDCS OR18) :
AirScale BSC / AirScale RNC multitenancy, example BoQ (NDCS RM19) :

AirScale BSC / RNC reference deployments – Nokia AirFrame, OR18 / NCIR19
Power consumption of a system configuration
• Complete system configuration with OR18 Skylake / NCIR19 based infrastructure contains : Compute nodes
1. One Storage / Compute triplet triplet
3. Compute triplets according required AirScale BSC / RNC reference deployments
6. Leaf switches, HW management switch and other mechanics
• Typical power consumption in VNF use is based on AirScale BSC / RNC deployment characteristics and required
Nokia AirFrame, OR18 Skylake / NCIR19 infrastructure implementation
Leaf and HW management
switches
• Power consumption can be optimized by switching off unused servers, not required by VNF deployments :
Compute nodes
1. Switching off additional servers in the configuration, added for reaching OR triplet Failover server capacity
2. Switching off servers freed after initial deployment as a result of AirScale BSC resource scaling Additional servers to reach OR
triplet
Power consumption Power consumption

Component Component
(W) * (W) *
Leaf switch 200 Compute (not in VNF use) 175

HW management switch 150 Power shelf 420
Controller / Compute triplet
Compute / Controller 320 * Typical power consumption in VNF use according Nokia
Compute / Storage 320 nominal reference traffic profile. Infrastructure site power
distribution needs to be defined according Nokia AirFrame
Compute (fully utilised by VNF) 275 installation site requirements

AirScale BSC / RNC reference deployments – Nokia AirFrame, OR18 / NCIR19
Power consumption of a system configuration
• Typical power consumption in VNF use is based on AirScale BSC / RNC deployment characteristics and required
Nokia AirFrame, OR18 Skylake / NCIR19 infrastructure implementation Compute nodes
16500 GSM TRXs and 28 Gbps for a GSM/WCDMA controller location : triplet
• AirScale BSC and AirScale RNC reference deployments for the required controller capacity :
Additional
triplet
Leaf and HW management
3 x RD3_BSC switches
1 1 36 1 2 15
5500 + 1 x RC3
Compute nodes
• Power consumption of an example system configuration : Failover server capacity
triplet
Power consumption Power consumption
Component qty Component qty
(W) * (W) *
Leaf switch 2 400 Compute (not in VNF

3 525
use)
HW management switch 1 150
Power shelf 2 840 Storage / Compute triplet
Compute / Controller 3 960 Controller / Compute triplet
Compute / Storage 3 960
Compute (fully utilised by

36 9 900 Totalconsumption in VNF use according
* Typical power 13 735
Nokia nominal reference traffic profile. Infrastructure site power
VNF)
distribution needs to be defined according Nokia AirFrame installation site requirements
AirScale BSC / RNC, Multicontroller BSC / RNC – comparing power
consumption
WBTS BTS MSS MGW SGSN NetAct OMS Network implementation in planning area and in RNC / BSC location :
• GSM Erlangs : 64 800 • CS BHCA : 296 651

• PDCH : 32 400 • PS BHCA : 320 197
• Number of TRXs : 16 200 • PS Session BHCA : 5 235 542
• Number of cells 5 400 • AMR Erlangs : 7 935
• Number of BTSs : 1 800 • Iub DL throughput : 3 031 Mbps
• Iub UL throughput : 506 Mbps
Backbone
• Number of cells 6 378
Backhaul
• Number iof BTSs : 1 547
RNC / BSC SITE

AirScale BSC / RNC
Multicontroller BSC / RNC
AirFrame NDCS OR18
AirScale RNC VNF
14 850 (W*) 13 735 (W*)
AirScale BSC VNF
AirScale RNC / BSC -7%
AirScale BSC VNF
* Typical power consumption according Nokia nominal reference
Multicontroller traffic profile.. Nokia AirFrame Infrastructure and Multicontroller
AirScale BSC VNF RNC / BSC
BSC / RNC site power distribution needs to be defined according
installation site requirements
Note : Presented dimensioning is indicative and is subject to further analysis on actual traffic capacity requirements
59 © Nokia 2020
AirScale BSC / RNC – using Acord to define infrastructure HW configuration (1/2)
Dimensioning results for

According required VNF 4 AirScale BSC
2 dimensioning, 3 x RD3_BSC
5500 configured
AirScale BSC, AirScale RNC

1 and Nokia Data Center Solution
included in Acord project
• As a result from VNF dimensioning,

required AirScale BSC and AirScale
RNC reference deployments for the
planning area :
Dimensioning results for
• AirScale BSC : 3 x RD3_BSC 5500 5 AirScale RNC
According required VNF
• AirScale RNC :1 x RC3 3 dimensioning, 1 x RC3
configured
• Nokia AirFrame OR18 infrastructure

is planned to be used

AirScale BSC / RNC – using Acord to define infrastructure HW configuration (2/2)
Infrastructure dimensioning
results for AirScale BSC,
7 AirScale RNC multitenant
deployment
OR18 / NCIR18 infrastructure

selected. AirScale BSC and
6 AirScale RNC VNFs included
for multitenant deployment
• As a result from VNF dimensioning, required AirScale BSC and AirScale RNC
reference deployments for the planning area :
• AirScale BSC : 3 x RD3_BSC 5500

• AirScale RNC :1 x RC3
• Nokia AirFrame OR18 infrastructure is planned to be used
61 © Nokia 2019
In
f ra
st r
Nokia AirFrame - NDCS HW, NCIR19 SW

uc
tu
re
• NDCS HW and NCIR19 SW are configured through CAT tool via CSP (OR18, OR19, RM19) :
NDCS OR18 / OR19 / RM19 : CAT tool via CSP, Configuration model: Nokia AirFrame Open Rack / Rackmount
• Detailed sales support for the Nokia AirFrame Data Center Solution through Data Center product management
https://nokia.sharepoint.com/sites/AirFrame/SitePages/Home.aspx
• For further details on NDCS HW and NCIR SW :

• Radio Cloud Infrastructure (NCIR) Pricing Guideline :
https://nokia.sharepoint.com/:p:/r/sites/MNProductsCommercialManagement/ConvergedCorePricing/Converged%20Core%20Pricing%20docume
nt%20library/Radio%20Cloud%20Infrastructure%20(NCIR)%20Pricing%20Guideline.pptx?d=w6886204c209d44678bd73203416c6c79&csf=1
• NDCS OR18 ordering instructions :

https://sharenet-ims.int.net.nokia.com/Open/D555377769
• NCIR ordering instructions :
https://sharenet-ims.int.net.nokia.com/Open/D562809838
62 01/04/2023 © Nokia 2019

Confidential
In
f ra
st r
Nokia AirFrame - NDCS HW, NCIR SW

uc
tu
re
• Transceivers and cables in Nokia AirFrame portfolio :

• Transceivers : Pluggable transceivers are available for optical and electrical connections.The link below lists pluggable transceivers available for
NDCS HW. SFP and SFP+ transceivers
• Cables : Interconnection cables are available for network and power connections. Cables
• If suitable cables or transceivers are not found fom Nokia AirFrame portfolio, contact GS NI
• AirScale BSC 19 FP1 deployment is supported on top of NCIR 17A / RM17. Select ‘Redundant full-rack configuration’ in Nokia AirFrame Data
Center Solution IPC model. In CSP / IPC select the number of compute nodes according HW capacity required for AirScale BSC deployment. See :
AirScale BSC reference deployments. Remember to configure required SFP modules and cables for DTOR / MTOR uplink connectivity in CSP /
IPC
• AirScale BSC 19 FP3 deployment is also supported on top of NCIR 18 FP2.1 / NDCS OR 18 Skylake. Use CAT tool via CSP, Configuration
model: Nokia AirFrame Open Rack OR18 / NCIR – for infrastructure BoQ creation
• In CAT tool select the number of triplets according HW capacity required for AirScale BSC deployment. See : AirScale BSC reference deployments
.
• AirScale BSC 20 FP1 deployment is also supported on top of NCIR 18 PP3.1 / NDCS OR 19 Cascade Lake. Use CAT tool via CSP, Configuration
model: Nokia AirFrame Open Rack OR19 / NCIR – for infrastructure BoQ creation
• In CAT tool select the number of triplets according HW capacity required for AirScale BSC deployment. See : AirScale BSC reference deployments
.
63 01/04/2023 © Nokia 2018

Confidential
In
f ra
st r
Nokia AirFrame - NDCS HW, NCIR SW

uc
tu
re
• AirScale BSC 20 FP20A deployment is also supported on top of NCIR 19 / NDCS RM 19 Cascade Lake. Use CAT tool via CSP, Configuration
model: Nokia AirFrame Rackmount RM19 / NCIR – for infrastructure BoQ creation
• In CAT tool select the number of servers according HW capacity required for AirScale BSC deployment. See : AirScale BSC reference deployments
.
64 01/04/2023 © Nokia 2018

Confidential
AirScale RNC, AirScale BSC – using CAT for infrastructure configuration (1/6)
NDCS OR18 / OR19 : CAT tool via CSP
Configuration model: Nokia AirFrame Open Rack
• Login for CAT via CSP : https://crm.int.net.nokia.com/sap/crm_logon

• For details on Nokia AirFrame infrastructure HW, contact : AirFrame Open Rack : Ylitalo, Tapio (Nokia - FI/Espoo)
Select storages and controllers

1 Select system configuration
3 separated
2 Select NCIR blueprint template
Note : NCIR server profiles having separated storage and controller are
used for AirScale BSC and AirScale RNC deployment

NDCS OR18 / OR19 : CAT tool via CSP
Select all other options : #of triplets, leaf

and HW management switches, power feed,
SW (eSW, NADCM, NCIR), other
mechanics and options
Select amount of triplets

4 according VNF dimensioning
5 Select AirFrame switches
Completed configuration
6 enables HW BoQ creation

NDCS RM19 Cascade Lake : CAT tool via CSP
Configuration model: Nokia AirFrame Rackmount

• For details on Nokia AirFrame infrastructure HW, contact : AirFrame Rack-mount : Ruohonen, Jari (Nokia - FI/Espoo)
1 Select system configuration
2 Select NCIR blueprint template

Configuration model: Nokia AirFrame Rackmount

3 Select HA deployment model Note : NCIR HA deployment

model used for AirScale BSC and
AirScale RNC deployment
4
Select storages and controllers
separated
Note : NCIR server profiles
having separated storage and
controller are used for AirScale
BSC and AirScale RNC
deployment


Note : 3 x controller / compute nodes for AirScale

BSC and AirScale RNC deployment
Note : 2 x storage / compute nodes for AirScale

BSC and AirScale RNC deployment
Select amount of compute

5 nodes according VNF
dimensioning

6 Select AirFrame switches
Select all other options : #of compute

nodes, leaf and HW management switches,
power feed, SW (eSW, NADCM, NCIR),
other mechanics and options
Completed configuration
7 enables HW BoQ creation

In
f ra
st r
Flexible infrastructure options for AirScale RNC and BSC deployment uc
tu
re
Infrastructure decoupled from VNFs

Infrastructure usage planned to adopt the speed and flexibility of cloud infrastructure
Higher utilisation Lower utilisation

Spare HW capacity Spare HW capacity
Spare HW capacity
Spare capacity Spare capacity
VNF Utilised capacity VNF Utilised capacity
VNF Utilised capacity
Spare capacity Spare capacity

VNF Utilised capacity
VNF Utilised capacity VNF Utilised capacity

In
f ra
st r
Two infrastructure options for AirScale BSC and AirScale RNC deployment uc
tu
re
1. AirFrame Rack-mount 2. AirFrame OpenRack

Available :
Available : Hyper Scale AirScale RNC 19 FP2 :
Easy scalability RC0529 AirScale RNC
AirScale RNC deployment Efficiency with Open
for datacenters deployment on Nokia
on Nokia AirFrame RM17 Compute Project
with Rack-mount AirFrame OR18
configuration (OCP)
Available :
AirScale BSC deployment Available :
on Nokia AirFrame RM17 AirScale BSC 19 FP3 :
RC0994 AirScale BSC
deployment on Nokia
AirFrame OR18
AirScale RNC 20 FP20A :

Available :
RC2095 AirScale RNC
deployment on Nokia AirScale RNC 20 FP1 :
AirFrame RM19 RC1487 AirScale RNC
deployment on Nokia
AirFrame OR19
AirScale BSC 20 FP20A :
RC0952 AirScale BSC
AirScale BSC 20 FP1 :
deployment on Nokia
RC1764 AirScale BSC
AirFrame RM19 Low to medium capacity distributed edge datacenters High capacity edge and regional datacenters – deployment on Nokia
– multitenant AirScale BSC / multitenant AirScale BSC / AirFrame OR19
AirScale RNC deployments AirScale RNC deployments

In
f ra
st r
AirScale BSC, AirScale RNC deployment on Nokia AirFrame OpenRack uc
tu
re
Nokia AirFrame NDCS OpenRack HW performance evolution

• High capacity AirScale BSC and AirScale RNC
deployments with enhanced energy efficiency and Nokia AirFrame OR18 / NCIR Nokia AirFrame OR19 / NCIR
reduced footprint
• Optimal for high capacity edge and regional

datacenters where processing resources are shared Higher capacity HW resource
between several VNFs pool for AirScale BSC and
AirScale RNC VNF
deployment
OpenRack HW CPU generation
NDCS OR18 Intel Xeon Skylake (16 cores, 2.1GHz)
NDCS OR19 Intel Xeon Cascade Lake (20 cores, 2.1GHz
• Available vCPUs for VNF use with different + 30%

server profiles :
Storage / Controller /
Nokia AirFrame
OpenRack HW
OpenRack HW Compute performance
Compute Compute evolution with new
CPU generation
NDCS OR18 54 50 40
NDCS OR19 70 66 56

In
f ra
Concurrent GSM/WCDMA operation with multi-tenancy st r
uc
tu
re
Nokia AirFrame OpenRack / NCIR
Nokia AirFrame OR19 / NCIR
• Efficient HW resource utilisation within the cloud infrastructure - available
resources in datacenter can be used for both, GSM controller High capacity HW resource
implementation and WCDMA controller implementation pool for Cloud RAN VNF
• Concurrent operation - common infrastructure across technologies deployment
• Reference Nokia AirFrame HW: AirFrame NDCS OR19
HW resource utilization
AirScale RNC VNF RC3

Other Cloud RAN 56%
AirScale BSC VNF AirScale BSC VNF VNFs
RD3_BSC 5500 RD3_BSC 5500
Common infrastructure
Nokia AirFrame NDCS OR19 / NCIR SW
11 000 GSM TRXs and 28 Gbps
9 OR triplets for a GSM/WDDMA controller location
11 000 TRX
28 Gbps
Edge datacenters Regional datacenters

In
f ra
Concurrent GSM/WCDMA operation with multi-tenancy st r
uc
tu
re
Nokia AirFrame Rack-mount / NCIR
Infrastructure
• Efficient infrastructure option for distributed low to medium capacity
edge datacenters - available resources in datacenter can be used for
both, GSM controller implementation and WCDMA controller NDCS RM19 / NCIR
implementation
• Existing network architecture can be maintained during controller Cascade Lake
modernization
• Reference Nokia AirFrame HW: AirFrame NDCS RM19 (Cascade
Lake) Footprint Power consumption
Existing Multicontroller
BSC / Multicontroller RNC -25%
implementation -10%
AirScale BSC VNF
RD3_BSC 5500
5 500 TRX
6 600 cells AirScale RNC VNF
RC2
Edge datacenters Regional datacenters

In
f ra
st r
Nokia AirFrame, NDCS Rackmount – building blocks uc
tu
re
Reference hardware for Rack Servers

AirScale BSC / AirScale RNC
42 U
deployment 19 inch equipment width
1991 x 600 x 1200mm
(Height x Width x Depth)
PDUs Storage
AC, DC
AC DC
NADCM Switches
Nokia AirFrame
Data Center
Manager

In
f ra
st r
Nokia AirFrame, NDCS Rackmount RM19 – controller / compute node uc
tu
re
Server profiles : Controller / Compute or Compute

X 14
RM 19
• 2x Intel Xeon Cascade Lake (20 core, 2.1GHz)
• 12x 16GB DDR4/2933 RDIMM (192GB)
• 2x Mellanox ConnectX-4 NIC, 2x 25Gbit ports

X3* • 2x 960GB 2.5“ SATA SSD

Compute nodes in reference HW implementation can be scaled on a granularity of
X 13 one server
* Controller / compute node, quantity (3) of controller / compute nodes is the same
in all reference HW implementations (controller and storage separated)

In
f ra
st r
Nokia AirFrame, NDCS Rackmount RM19 – storage / compute node uc
tu
re
Server profile : Storage / Compute
RM 19
• 12x 16GB DDR4/2933 RDIMM (192GB)

• 4x 980GB 2.5“ SATA SSD
X2
Quantity of storage / compute nodes (2) is the same in all reference HW

implementations (controller and storage separated)

In
f ra
st r
Nokia AirFrame, NDCS Rackmout RM19 – switches uc
tu
re
Switches
X3
Data plane / Management plane (Leaf switch) :
• Nokia AirFrame Switch Z9100ON (32x 100GBit)
HW management switch :
• DC : Nokia AirFrame Switch S4048T (48x 10GBit, 6x 40GBit)
• AC : Nokia AirFrame Switch S3048ON (48x 1Gbit, 4x 10GBit)
Quantity of switches is the same in all reference HW implementations

AirScale BSC / AirScale RNC deployment on Nokia AirFrame OpenRack
New reference HW for Existing AirScale BSC Higher rack level GSM Higher rack level Higher rack level
AirScale BSC and and AirScale RNC BSC capacity with WCDMA RNC concurrent
AirScale RNC refence deployments AirScale BSC ↔ capacity with AirScale GSM/WCDMA
deployment remain AirScale BSC RNC ↔ AirScale RNC capacity with AirScale
multitenancy multitenancy BSC ↔ AirScale RNC
multitenancy
Infrastructure Optimal for BSC and Common single rack Further capacity
dimensioning based on RNC modernization – NCIR blueprint site evolution for AirScale
required amount of legacy controller solution for AirScale BSC and AirScale RNC
virtual resources consolidation to high BSC and AirScale RNC deployment according
capacity edge and deployment ontop of Nokia AirFrame HW
regional datacenters Nokia AirFrame evolution – NDCS
OpenRack OR18, NDCS OR19

In
f ra
st r
Nokia AirFrame, NDCS OpenRack – building blocks uc
tu
re
Reference hardware for Rack Servers

AirScale BSC / AirScale RNC
42 U
deployment 21 inch equipment width
2210 x 600 x 1070mm
(Height x Width x Depth)
PDUs Storage
AC, DC
NADCM Switches
Nokia AirFrame
Data Center
Manager

In
f ra
st r
Nokia AirFrame, NDCS OpenRack OR19 – controller / compute node uc
tu
re
Server profiles : Controller / Compute or Compute

X 12
OR 19
• 12x 16GB DDR4/2933 RDIMM (192GB)
X 12 • 2x Mellanox ConnectX-4 NIC, 2x 25Gbit ports

• 1x 1Gbit LoM port (IPMI / HW management)
• 1x 480GB SATA M.2 device
X 12
Compute nodes in reference HW implementation can be scaled on a granularity of one

OR triplet
X9
X3* * Controller / compute node, quantity of controller / compute nodes is the same in all
reference HW implementations (controller and storage separated)

In
f ra
st r
Nokia AirFrame, NDCS OpenRack OR19 – storage / compute node uc
tu
re
Server profile : Storage / Compute
OR 19
• 12x 16GB DDR4/2933 RDIMM (192GB)

• 1x 1Gbit LoM port (IPMI / HW management)
• 1x 480GB SATA M.2 device
Quantity of storage / compute nodes is the same in all reference HW implementations

(controller and storage separated)

X3*

In
f ra
st r
Nokia AirFrame, NDCS OpenRack OR19 – switches uc
tu
re
Switches
X3 Data plane / Management plane (Leaf switch) :

• Nokia AirFrame Switch Z9100ON (32x 100GBit)
HW management switch :
• Nokia AirFrame Switch S4048T (48x 10GBit, 6x 40GBit)
Quantity of switches is the same in all reference HW implementations

V
N
AirScale BSC F
Selecting AirScale BSC capacity step and required HW configuration
1 2 3
Select HW configuration with
Define required BSC capacity required amount of compute
according network dimensioning Select AirScale BSC reference nodes for selected AirScale BSC
deployment reference deployment
AirScale BSC 19 / AirScale BSC 20 : AirScale BSC 19 / AirScale BSC 20 :
Reference deployments, example Nokia VNF infrastructure requirements for

AirFrame HW BoQs CBAM dimensioning

In
f ra
Uplink connectivity (RM19, OR19) - VNF networks, 100G at EDGE routers st r
uc
tu
re
Nokia AirFrame Switch Z9100ON (32x 100GBit) LEAF-2 1

100G QSFP28
uplink connectivity (QSFP28) QSFP28 100G
QSFP28 100G
100G QSFP28
100G 100G
2 x 100G Trunks
EDGE 2
100G 100G
100G QSFP28
QSFP28 100G
100G QSFP28
QSFP28 100G
LEAF-1
EDGE 1
1
100GbE AOC
QSFP28/QSFP28 connectors
86 © 2018 Nokia Confidential Nokia AirFrame : Available transceivers and active optical cables (AOCs)
In
f ra
uc
tu
re

100G QSFP28
QSFP 40G
uplink connectivity (QSFP28) 100G port 100G QSFP28
splitted
into one QSFP 40G
40G port
100G QSFP28 QSFP 40G
100G QSFP28 QSFP 40G

100G 100G
2 x 100G Trunks
EDGE 2
100G 100G
100G QSFP28
100G port 100G QSFP28

splitted
into one QSFP 40G
40G port
100G QSFP28
QSFP 40G
100G QSFP28 40G

QSFP
LEAF-1
QSFP 40G
EDGE 1
1
40GbE AOC
QSFP/QSFP connectors
In
f ra
uc
tu
re

100G QSFP28 1 2
SFP+ 10G
uplink connectivity (QSFP28) 100G port
100G QSFP28 1 2
2
splitted
into four SFP+ 10G
2
10G ports
100G QSFP28 1 2 2 SFP+ 10G
100G QSFP28 1 2 2 SFP+ 10G

100G 100G
2 x 100G Trunks
EDGE 2
100G 100G
100G QSFP28 1 2
100G port
splitted 100G QSFP28 1 2
into four
10G ports 2 SFP+ 10G
100G QSFP28 1 2
2 SFP+ 10G
100G QSFP28 1 2 10G

2 SFP+
LEAF-1
2 SFP+ 10G
1 EDGE 1
2 3
QSFP to SFP+ adapter
10G SPF+ trasceiver
Optical cable
In
f ra
Uplink connectivity (RM19 DC, OR19) – HW management st r
uc
tu
re
Nokia AirFrame Switch S4048T (48x 10GBit, 6x 40GBit) LEAF-2

100G
Uplink connectivity (QSFP)
3
EDGE 2
Management network
40G QSFP 1 2
2 SFP+ 10G
HW mgmt
1 HW spine
2 3 QSFP to SFP+ adapter
10G SPF+ trasceiver
Optical cable
In
f ra
Uplink connectivity (RM19 AC) – HW management st r
uc
tu
re
Nokia AirFrame Switch S3048ON (48x 1Gbit, 4x 10GBit)

LEAF-2
100G
Uplink connectivity (SFP+)
2 EDGE 2
Management network
10G SFP+ 1
1 SFP+ 10G
HW mgmt
HW spine
1 2
10G SPF+ trasceiver
Optical cable
What is sometimes forgotten from AS RNC/BSC offering?
Following topics need to be addressed when preparing offer
• Connecting AirScale RNC/BSC to EDGE/Site routers (via Leaf Switches in cabinet) additional SFP modules and
adapters are needed
• See slides 86-90 in this sales guide
• Additional servers/HW are needed to run NADCM and CBAM (outside AS BSC/RNC rack)
• NADCM is recommended to be installed outside the rack it supervises
• CBAM can be installed to the AS RNC/BSC rack or centrally
• See slide 100 for limitations
• ACORD tool offers optimized quantity of servers against the input parameters
• To have more flexibility in the field additional server(s) should be considered
• For scaling out VMs (like additional PCUM capacity)
• For maintenance tasks needing one empty server
• Latest SW level should always be offered with related compatibilities
• Latest SW release level ascertain longer support time, latest corrections and minimizes the need for soon t
o come SW release upgrade
• The time between offering and contract/ordering can be long and
it is good to check and update the SW levels when moving to ordering phase
• GeoResiliency can be highlighted / offered even customer hasn’t specifically requested it
• On top of disaster recovery it is very useful in smooth SW maintenance tasks
91 © 2018 Nokia
Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR)
Update on NCIR scope 3Q 2021
• NCIR product responsibility has moved from CNS to MN 1.7.2021
• NCIR roadmap will not be updated any more, latest version will be frozen
• NCIR19 FP2 is the latest SW release and no new SW releases under planning
• Today NCIR is only used with AirScale BSC/RNC products
• Any new development will be described in AirScale BSC/RNC material
• AirScale BSC/RNC topics will be included in RAN SW Roadmap
• NCIR offering and ordering as earlier except change in pricing guidance:

• Term pricing mode NCIR SW lic. should be part of offering BoQ with 0.00 IRP for ordering purpose and its
value is covered with ASRNC and ASBSC product. There is no perpetual pricing for NCIR SW lic.
92 © 2018 Nokia
In
f ra
st r
NADCM uc
tu
re
• NADCM is configured through CSP / IPC / CAT, NDCS / NCIR IPC / OR18 / OR19 CAT model is used for configuration :
Product ID: 134-080698.00, Product description: Nokia AirFrame Data Center Solution
• CAT model for OR18 / OR19

Product ID: 833-012540.00, Product description: Nokia AirFrame Data Center Open Rack
• Nokia AirFrame Data Center Manager (NADCM) – management system for optimizing and automating Data Center operations
and resource utilization
• For further details on NADCM :
• Nokia AirFrame Data Center Manager : NADCM (sharepoint.com) / https://nokia.sharepoint.com/sites/NADCM/SitePages/NADCM.aspx

93 • Ordering©instructions
Nokia 2019 : NADCM Order Information.pptx (sharepoint.com) /
Confidentialhttps://nokia.sharepoint.com/:p:/r/sites/cce/gpcp/_layouts/15/Doc.aspx?sourcedoc=%7Bf6c2b32d-a011-4257-89f8-81231d674dbf%7D&action
=edit&mobileredirect=true
In
f ra
st r
Nokia AirFrame Data Center Manager, NADCM uc
tu
re
Data Center operations automation, overview

Cloud
Controllers
• DC Hardware Management WebUI
Bare Metal
- Automatic HW discovery & inventory Applications
- Events, KPI monitoring & alerting
OSS systems
- Thermal & power management HTTPS ( RESTful )
- Configuration & firmware management
- User management
Nokia AirFrame
• Open HW management Data Center
- Supports Airframe hardware Manager
- Servers, switches, storages, and power/rack management
- Out-of-band HW management, no impact to host side
Out of Band Management Other Management Protocols:
• Scalable Multi Data Center management Protocols: IPMI, SNMP, SSH DHCP, TFTP, HTTPS
- From small distributed to centralized hyperscale
• Web User interface
• RESTful APIs
- North bound integration with cloud controllers, bare-metal environments and
umbrella OSSs
94 © 2018 Nokia Nokia Internal Use
Nokia AirScale RNC and AirScale BSC operability
Infrastructure – Nokia AirFrame Data Center Manager (NADCM)
VNF Management - CBAM NetAct
• Infrastructure PM, FM
• VNF lifecycle management
• Infrastructure Element Manager launch
• VNF Elasticity management
• VNF SW upgrade
NADCM
Web UI
Elasticity VNF Lifecycle
Management Management FM PM
Located outside of Nokia AirFrame Data Center Manager (NADCM) OMS VNF NetAct integration
managed Nokia
AirFrame racks, Provides the HW management functions for servers, switches and AC
Instantiate VNF
Terminate VNF
single server : PDU’s :

Scale-out
Scale-in
VNFs - AirScale BSC, AirScale RNC FM, PM

FM
PM
• Bare metal VNF Configuration Management

• HW inventory management https
PM
FM
• Virtual machine • Device control
GUI through Web Application
• Firmware and configuration management
Required HW capacity • HW monitoring, metrics and events
NCIR number of
according Virtual Infrastructure Manager
Hypervisor
managed nodes
AirFrame HW Network Storage

Compute NADCM

CBAM
• CloudBand Application Manager (CBAM) manages the lifecycle of Virtualized Network Functions. In case of AirScale BSC, CBAM
manages e.g. deployment/undeployment, scaling and SW management of the AirScale BSC VNF
• CBAM is always configured through CSP / IPC, CBAM IPC model is used for configuration :
Product ID: 833-003361.00, Product description: CloudBand Application Manager
• For further details on CBAM :

• CBAM technical information: https://confluence.int.net.nokia.com/display/CloudBandProducts/CBAM+Technical+information
• CBAM sales information: https://confluence.int.net.nokia.com/display/CloudBandProducts/CBAM+Sales+information
• Reference infrastructure for CBAM deployment :

• Reference infrastructure for CBAM deployment - CBIS. CBIS ordering instruction:
https://sharenet-ims.int.net.nokia.com/livelink/livelink/overview/D553220638
• CBAM can be also deployed on NCIR19 infrastructure
• Please contact NSW pre-sales team for detailed CBAM dimensioning and BoQ support.
• CBAM SW license dimensioning is based on vCPUs managed by the CBAM. See the the ‘Example Nokia AirFrame reference HW BoQ’ in
this document for AirScale BSC VNF infrastructure requirements and CBAM license anounts for different AirScale BSC reference
deployments.
96 © Nokia 2019
• CBAM
Confidential contacts:
• CBAM product management Daniel Fey, daniel.fey@nokia.com
Nokia AirScale RNC and AirScale BSC operability
Infrastructure – Cloud Band Application Manager (CBAM)
VNF Management - CBAM NetAct
CBAM
• Infrastructure PM, FM
• VNF lifecycle management Web UI • Infrastructure Element Manager launch
• VNF Elasticity management
• VNF SW upgrade
Elasticity VNF Lifecycle

Management Management FM PM Options for deployment
OMS VNF NetAct integration
Cloud Band Application Manager (CBAM)
GUI through Web Application • Centralized
Instantiate VNF
• Distributed
Terminate VNF
Operations for AirScale BSC and AirScale RNC network

Scale-out
Scale-in
elements:
VNFs - AirScale BSC, AirScale RNC
FM
PM
VNF Configuration Management
PM
FM
• Manage the network element lifecycle: Create, Instantiate,
Terminate, Delete
• Manage the network element capacity : Scale-out, Scale-in
NCIR • Manage the
Virtual Infrastructure Manager
network element SW : Upgrade VNF SW
Hypervisor
AirFrame HW Network Storage

Compute NADCM

Lifecycle management with VNFM - distributed CBAM deployment
WBTS MSS MGW SGSN NetAct
Infrastructure for VNF deployment :
• Nokia AirFrame, NDCS RM19

• NCIR19
Controller
VNF1 • VNFM : CBAM (single instance) *
Backbone
Backhaul Upto 32 servers
Controller
VNF2
CBAM * Dependant on the availability of HW

VNF resources for CBAM deployment
SITE A SITE B
Controller VNF1 VNF management Controller VNF1 VNF management
Controller VNF2 Controller VNF2
NCIR
NCIR CBAM VNF CBAM VNF

Lifecycle management with VNFM - centralized CBAM deployment
WBTS MSS MGW SGSN NetAct
SITE C
VNF management Infrastructure for controller

VNF deployment :
CBAM VNF • Nokia AirFrame, NDCS RM19

Controller
• NCIR19
VNF1
Backbone Upto 32 servers

Backhaul
Controller
VNF2
Separate Infrastructure for VNFM
SITE A SITE B • VNFM : CBAM (HA or non-HA)

NCIR NCIR

CBAM Deployment Models for AirScale BSC / AirScale RNC
Centralized Distributed
NetAct CBAM NetAct
CBAM
… CBAM
BSC / RNC … BSC / RNC … BSC / RNC BSC / RNC BSC / RNC
1 – N (within location) 1 – N (within location) 1 – N (within location) 1 – N (within location) 1 – N (within location)
+ CBAM capacity utilization can be optimized − Lower CBAM capacity utilization

+ Smaller number of CBAM deployments & Upgrades − Higher number of CBAM deployments & Upgrades
+ Smaller number of integration points in NetAct − Higher number of integration points in NetAct
- Higher amount of HW resources required for CBAM + Lowest resource requirements through CBAM single
Multi-Node (HA) configuration instance deployment together with AirScale BSC/RNC.
CBAM resiliency through frequent backups

CBAM installation in same NCIR instance as AS RNC/AS BSC
Hard disk limitation with multi-node CBAM
• In some current AirScale BSC/RNC cases/projects in the field, Nokia has offered a design where CBAM is
running on the same NCIR19 instance as AirScale BSC and/or AirScale RNC.
• In nearly all of these cases, multi-node CBAM seems to be proposed.
• However, multi-node CBAM resource consumption is excessive for AirScale cloud controllers, which do
not need the performance or the high-availability features. Single-node CBAM with proper backup
arrangements is enough.
• Storage capacity is the bottleneck, as multi-node CBAM requires 1500 GB and during upgrade 3000 GB.
• Total Ceph capacity available in RM19 radio setups is 2100 GB.... so multi-node CBAM also does not fit in.
If it is anyway installed offline CBAM upgrade is only viable solution with radio blueprint HW.
• Single-node CBAM only should be sold to these cases.
• More centralized CBAM location is also feasible and recommended way to proceed.

VN
AirScale BSC – Configuring with CSP/IPC (1/4) F
AirScale BSC CSP /

IPC model :
Product ID: 833-004574.00

Product description: Cloud RAN SW
2 Select pricing model
1 Select AirScale BSC
3 Select SW release
10 © Nokia 2018
2
VN
Select SW Release
4 subscription capacity
10 © Nokia 2018
3
VN
Select AirScale BSC

5 VNF Capacity SW
10 © Nokia 2018
4
Complete BoQ for VN
8
AirScale BSC – Configuring with CSP/IPC (4/4) the configuration F
Select Essential SW
6 capacity
Select Enhanced SW
7 capacity
Note : Essential SW pack is mandatory and contains initial SW functionalities

in all AirScale BSC offers
10 © Nokia 2018
5

AirScale BSC SW Sales Guide

Uploaded by

Copyright:

Available Formats

You might also like

AirScale BSC SW Sales Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AirScale BSC SW Sales Guide

Uploaded by

Copyright:

Available Formats

Nokia Next Generation Radio Access:

AirScale BSC – Sales guide

1 © Nokia 2020 Confidential

• AirScale BSC SW IRP list is available through MN Commercial Management SharePoint :

From low to high High capacity edge and AirScale

Technology agnostic Concurrent 2G/3G Efficient controller Optimize with

Future proof HW Site consolidation Common infrastructure

Re-useabilty through data center Less controllers

OPEX savings AirScale

4 © 2019 Nokia Confidential

AirScale BSC combines the functionalities of

6 © 2019 Nokia Confidential

*Erlangs / cabinet, RM19

*PDCH / TRX / BSC *BTS

GSM Cloud Essential SW price

GSM Cloud Enhanced SW price

HVF and E-HVF SW price

11 © 2019 Nokia Confidential

12 © 2019 Nokia Confidential

HVF and E-HVF SW price

SW Subscription = Annual SW fee and Time limited SW RTU Subscription (LKs)

AirScale Cloud Infrastructure

Standard Content SW Defines standard content in SW

Cloud RAN Capacity •AirScale BSC capacity

Cloud RAN SW •Mandatory pricing component BB units

Release Subscription RF units

PS data RTSL (MCS9) * 29 370 >> mcBSC 20 400

Five reference deployments :

* Multicontroller BSC – HW Rel2

AirScale BSC, RD4_BSC 8800

Maximum TRX 4400 mcBSC PS Capacity step 7 : RD5_BSCD

Maximum TRX 4400 mcBSC PS Capacity step 6 : TRX 4400

Maximum TRX 4400 mcBSC PS Capacity step 5 : TRX 4400

Maximum TRX 4400 mcBSC TRX Capacity step 4 : TRX 5500

Maximum TRX 3300 mcBSC TRX Capacity step 3 : TRX 3300

Maximum TRX 2200 mcBSC TRX Capacity step 2 : TRX 3300

Maximum TRX 1100 Capacity step 1 : TRX 1100

VNF4 Storage / compute triplet

mcBSC S4 mcBSC S4 mcBSC S1 mcRNC S3 mcRNC S3

© Nokia 2019 Confidential

Cumulative HW and Infrastructure view – Site A

AirFrame Hardware CBAM Software

100 000 NCIR Software

© Nokia 2019 Confidential

• Erlangs : 43 200 Multicontroller BSC

AirScale BSC • Required HW capacity for

Note : Presented dimensioning is indicative and is subject to further analysis on

RNC / BSC SITE

VNF capacity Infrastructure Comparison

22 © 2019 Nokia Confidential

Centralized License Server NetAct

License violation identified RTU not RTU not granted alarm

SWEM = SW Entitlement Manager

3. If current value > PM

AirScale BSC SW NCIR SW NDCS NASM CBAM SW

AirScale BSC VNF Infrastructure *

AirScale BSC ASBSC 19 SW AirScale BSC VNF Network

ASBSC 20 SW AirScale BSC

PDCH / TRX / BSC BTS