Airscale RNC SW Sales

PROPOSAL
RAN network

Dec 2018

Company Confidential
VRNC Proposal

Contents

1. Document Scope ............................................................................................................... 3

2. Functional description ...................................................................................................... 3
2.1. Nokia AirScale RNC............................................................................................................ 3
2.2. VRNC Integration, management and support tools ......................................................... 4
3. Reference HW configuration for Airsclae RNC 17............................................................. 5
4. Airscale RNC 17 _ Capacity values .................................................................................... 6
5. Airscale RNC Operability ................................................................................................... 7
6. OMS with Airscale RNC ..................................................................................................... 7
7. Centralized license management based on CLS and SWEM ................................. 8
8. Licence Principle................................................................................................................ 9
9. Airscale RNC sales structure and sales items .................................................................... 9
9.1. VRNC product and related sales items ............................................................................. 9
9.2. VRNC sw sales items structure........................................................................................ 10
9.3. Additional items .............................................................................................................. 10
9.3.1 NDCS Airframe HW (mandatory) .................................................................................... 10
9.3.2. NCIR SW (mandatory) ...................................................................................................... 11
9.3.3. CBAM (Mandatory) .......................................................................................................... 12
9.3.4. NASM (Mandatory) .......................................................................................................... 12

2
VRNC Proposal

1. Document Scope
Aim of this documents is to provide HiWeb with BRTel advances services and solutions
regarding VRNC feature and Function.
Current document includes general information of the feature for customer.
Instructions on how to perform activation of feature are out of this document’s scope.

Document title Version Delivery Upda

no. date te
Airscale RNC SW Sales Proposal V1.0 10.12.2018 -

BRTel shall be pleased to address the above factors and goals by proposing the
following chapters.

2. Functional description

2.1. Nokia AirScale RNC

Nokia Airsclae RNC is an evolution to cloud

3
VRNC Proposal

2.2. VRNC Integration, management and support tools

 NetAct handles Cloud and non-Cloud NEs at the same time

 Existing Northbound interfaces preserved
 CBAM Manages Cloud applications
 (Nokia Cloud Network Director for E2E network orchestration in large
Clouds)
 Reduces practical support needs
 Reduces OPEX

4
VRNC Proposal

3. Reference HW configuration for Airsclae RNC 17

5
VRNC Proposal

4. Airscale RNC 17 _ Capacity values

Maximum Capacity

Reference Configuration ID RC1 RC2 RC3

User plane capacity
AMR Erlangs 18 860 37 720 66 020
AMR Erlangs (including soft handover) 26 400 52 810 92 430
User plane throughput (Iub total in Mbps) 6 110 11 820 28 120
DL user plane throughput (Iub total in Mbps) 5 300 10 250 24 380
UL user plane throughput (Iub total in Mbps) 810 1 570 3 740
Control plane capacity
RNC subscribers 754 400 1 508 800 2 640 800
AMR Busy Hour Call Attempts 754 400 1 508 800 2 640 800
PS Busy Hour Call Attempts1 1 957 000 4 893 000 11 090 000
PS Session 2 Busy Hour Call Attempts 3 914 000 9 786 000 22 180 000
Signaling capacity (CS+PS session BHCA) 3 3 874 390 9 685 980 21 954 890
Max number of RRC connected UEs 390 000 1 000 000 1 000 000
Network connectivity
Max number of cells 2 640 6 600 10 000
Max number of BTS sites 520 1320 2 000

Smartphone Capacity

Reference Configuration ID RC1 RC2 RC3

Control plane capacity
Smartphone CS+PS BHCA 490 470 1 252 820 2 839 720
Smartphone CS+PS session BHCA 1 460 230 3 729 920 8 454 490
Smartphone CS BHCA 198 640 507 390 1 150 090
Smartphone PS BHCA 291 830 745 430 1 689 630
Smartphone PS session BHCA 1261 590 3 222 530 7 304 410
User plane capacity
Smartphone CS Erlangs 4 680 11 960 27 110
Smartphone PS Erlangs 108 240 276 490 626 720
Smartphone CS+PS Iub FP UL+DL
2 900 7 400 16 780
throughput
Smartphone CS+PS Iub FP DL throughput 2510 6420 14 550
Smartphone CS+PS Iub FP UL throughput 390 980 2230

1) Packet Switched Radio Access Bearer Busy Hour Call Attempts (BHCA) assuming 2x PS HSPA session per RAB
2) Session means RAB setup, state change to CELL_DCH, state change to HS-FACH/RACH.
3) AirScale RNC signaling capacity.

6
VRNC Proposal

5. Airscale RNC Operability

It deploys Built on CloudBand Application Manager and NetAct

6. OMS with Airscale RNC

- Support for AirScale RNC, mcRNC and RNC2600
• Simultaneously supports up to 20 RNC
- Both bare metal OMS and Cloud OMS support all RNC types (ASRNC,
mcRNC, RNC2600)
- Local user interface
- Strong data aggregation
- Commercial OMS hardware
• High capacity
• High connectivity
- Installation either on RNC site or remote
(e.g. NetAct site)

7
VRNC Proposal

7. Centralized license management based on CLS and

SWEM

• License management via CLS and SWEM

• Automatic license allocation
• No physical license keys in NEs
• License pooling. (Floating in future release).
• Supporting different license models
• Subscription model: term based licenses
• Perpetual model: one-time payment
• Own sales items for AirScale RNC:
• ASW features
• RNC capacity licenses
• Note: WCDMA BTS licensing remains the same as in WCDMA 17.

8
VRNC Proposal

8. Licence Principle
Basic principle of PM based capacity licenses and CM based feature ON/OFF
licenses illustrated in below picture

9. Airscale RNC sales structure and sales items

9.1. VRNC product and related sales items

9
VRNC Proposal

9.2. VRNC sw sales items structure

9.3. Additional items

9.3.1 NDCS Airframe HW (mandatory)

• AirScale RNC is supported on NDCS (AirFrame) HW.

• In AirScale RNC 17, the reference HW configuration is based on NDCS RM
17 HW.
• Supported configuration is: NCIR 16 A SP1 ‘Redundant full-rack
configuration’. Example configuration listed in the table below.
* = the quantity of compute nodes depends on required AirScale RNC capacity.

10
VRNC Proposal

Nokia Product name Nokia Sales Item Qty

AirFrame RM Compute Node 1 SET Broadwell NDCHW0129 20 *
AirFrame RM Controller Node 1 SET Broadwell NDCHW0131 2
AirFrame RM Storage Node 1 SET Broadwell NDCHW0133 2
AirFrame RM Switch S4048ON 48xPlug 10Gb NDCHW0124 2
AirFrame RM Switch S4048T 48xFix 10Gb NDCHW0123 2
AirFrame RM Switch S3048ON 48xFix 1Gb (optional HW Mgmt
NDCHW0126 0
switch)
AirFrame Rack Blank panel 1U 19 inch NDCHW1022 9
Rear side blank panel - 1U for optional HW Mgmt switch slot NDCHW1162 1
AirFrame PDU 3-phase 22 kW 48xC13 NDCHW1097 2
AirFrame RM rack system w/o units 24U/4 SFP+/2T NDCHW0215 1

9.3.2. NCIR SW (mandatory)

• AirScale RNC is supported on NCIR host OS SW.

• In AirScale RNC 17, the supported NCIR sw version is NCIR 16A SP1.
• The required NCIR sales items are listed below.
• Note the amount of sales items (1 per compute node or 1 per compute/controller/storage node).

11
VRNC Proposal

9.3.3. CBAM (Mandatory)

• CloudBand Application Manager (CBAM) manages the lifecycle of Virtualized
Network Functions on OpenStack cloud.
• CBAM is required for the lifecycle management of AirScale RNC (e.g.
deployment/undeployment, scaling and sw management)
• Please contact CBAM product manager for detailed sales information
regarding CBAM sw and related cloud infra requirements

9.3.4. NASM (Mandatory)

• AirFrame System Manager provides a secure and intuitive interface to review
system hardware configuration and datacenter status information.
• One NASM instance can monitor ~5000 nodes. One NASM license is required for each node and switch.
• Currently NASM available as a bare metal solution and thus requires dedicated node outside of the NCIR
instance. It can be installed on one Compute Node. For future, NDCS is planning a new cost-optimized
node configuration for NASM.

12