AirScale RNC Product Description

AirScale RNC, Rel. 17, Operating Documentation, Issue 02, Change Delivery 1 AirScale RNC Product Description DN09232214 Issue 01B Approval Date 2017-10-04

AirScale RNC Product Description

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY AVAILABILITY,, ACCURACY, ACCURACY, RELIABILITY, RELIABILITY, TITLE, NON-INFRINGEMENT NON-INFRINGEMENT,, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners. Copyright © 2017 Nokia. All rights reserved.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.

2

© 2017 Nokia

DN09232214 Issue: 01B


The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY AVAILABILITY,, ACCURACY, ACCURACY, RELIABILITY, RELIABILITY, TITLE, NON-INFRINGEMENT NON-INFRINGEMENT,, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners. Copyright © 2017 Nokia. All rights reserved.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.

2

© 2017 Nokia

DN09232214 Issue: 01B


Table of Contents This This document has 45 pages Summary of changes..................................................................... changes..................................................................... 7 1 1.1 1. 1 1.2 1.2.1

Overview of AirScale RNC............................................................. RNC.............................................................9 9 Radi Ra dio o co cont ntro roll ller er fu func ncti tion onal alit itie ies.. s.... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... 9 AirScale RNC within the 3G System Network topology................1 topology................11 1 RAN in 3G system........................................................................12 12

1.2.1.1 1.2.1. 1 1.2.1.2 1.2.1 .2 1.2.1.3 1.2.1 .3 1.3 1. 3 1.4

Core net Core netwo work rk ele elemen ments ts in 3G net netwo works rks... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ..... 13 RAN ele eleme ments nts in 3G ne netwo tworks rks... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...14 14 OSS OS S ele eleme ments nts in 3G ne netwo tworks rks... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...14 14 Logi Lo gica call in inte terf rfac aces es in a ra radi dio o co cont ntro roll ller er.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... .....1 ..15 5 AirScale RNC as a VNF within the ETSI NFV..............................16

2 2.1 2.2 2. 2 2.3 2.4 2.5

Functional architecture architecture................................................................. .................................................................18 18 CFPU functionalitie functionalities..................................................................... s.....................................................................19 19 CSPU CS PU fu func ncti tion onal alit itie ies.. s.... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... .... .. 19 USPU functionalitie functionalities.................................................................... s.................................................................... 20 20 EIPU functionaliti functionalities...................................................................... es......................................................................20 20 Other nodes................................................................................. 20 20

3 3.1

AirScale RNC redunda redundancy ncy model................................................ model................................................ 22 22 Redundancy Redundan cy principles................................................................. principles.................................................................22 22

4 4.1 4.2 4.3 4.4 4. 4 4.4.1 4.4 .1 4.4.2 4.4 .2 4.4.3 4.4 .3 4.5 4. 5 4.6 4. 6

Capaci Capa city ty an and d VM di dime mens nsio ioni ning ng.. .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ....2 ..23 3 VM dimension dimensioning.......................................................................... ing..........................................................................23 23 Configuration Configura tion limits....................................................................... limits.......................................................................23 23 Reference configuratio configurations............................................................. ns.............................................................24 24 Refe Re fere renc nce e tr traf affi fic c pr prof ofil iles es.. .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .. 25 Voic oice e tra traff ffic ic pr profi ofile le re refer feren ence ce ... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... .....25 ..25 HSPA HSP A tra traff ffic ic pr profi ofile le ref refer eren ence ce ... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ..... 25 Smartp Sma rtpho hone ne tra traff ffic ic pr profi ofile le ref refer eren ence. ce.... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ......26 ...26 Maxi Ma ximu mum m ca capa paci city ty.. .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... .. 27 Smar Sm artp tpho hone ne ca capa paci city. ty... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... 28

5 5.1 5. 1 5.2 5. 2 5.3 5. 3 5.4 5. 4 5.5 5. 5 5.5. 5. 5.1 1 5.5.2 5.5 .2 5.5.3 5.5 .3 5.6 5. 6

AirSca AirS cale le RN RNC C Op Oper erat atio ion n an and d Ma Mana nage geme ment nt.. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 30 NetA Ne tAct ct op oper erat atio ions ns an and d ma mana nage geme ment nt.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... ....3 ..30 0 Oper Op erat atio ion n an and d Ma Mana nage geme ment nt Se Serv rver er.. .... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... ....31 ..31 CBAM CB AM fu func ncti tion onal alit itie ies. s... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .. 33 SCLI SC LI ch char arac acte teri rist stic ics.. s.... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .. 34 AirS Ai rSca cale le RN RNC C mo moni nito tori ring ng an and d me meas asur urin ing. g... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... 35 L3 Da Data ta Co Coll llec ecto torr an and d L3 Da Data ta An Anal alyz yzer er.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ...35 .35 Traf Tr affic fica a for ra radio dio WCD WCDMA MA ne netwo twork. rk.... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... .....38 ..38 NetAct Net Act Tr Trace aceVi Viewe ewer.. r..... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ..... .. 38 AirS Ai rSca cale le RN RNC C Li Lice cens nse e Ma Mana nage geme ment nt.. .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ...39 .39

DN09232214 Issue: 01B

© 2017 Nokia

3


4

6 6.1 6. 1

Site So Site Solu luti tion on.. ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... 40 Stan St anda dalo lone ne Si Site te So Solu luti tion on fo forr Ai AirS rSca cale le RN RNC C .. ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .. 41

7

AirS Ai rSca cale le RN RNC C re requ quir irem emen ents ts re rega gard rdin ing g th the e VN VNF F in infr fras astr truc uctu ture re.. .... ...4 .43 3

© 2017 Nokia

DN09232214 Issue: 01B


List of Figures Figure 1

Radio Resource Management..............................................................9

Figure 2

3G Network architecture.....................................................................12

Figure 3

Logical interfaces of AirScale RNC.................................................... 16

Figure 4

ETSI NFV framework..........................................................................17

Figure 5

VNFCs in AirScale RNC..................................................................... 19

Figure 6

OMS GUI main view on Applications..................................................32

Figure 7

OMS GUI main view on External Applications................................... 33

Figure 8

CBAM contribution in the AirScale RNC operation and management.... 34

Figure 9

L3 Data Collector and L3 Data Analyzer functional view....................36

Figure 10

GEO Interface.....................................................................................37

Figure 11

Traffica Interface.................................................................................38

Figure 12

AirScale RNC internal and external subnets...................................... 40

Figure 13

Standalone AirScale RNC Site Solution.............................................42

Figure 14

AirFrame HW full rack configuration...................................................44

DN09232214 Issue: 01B

© 2017 Nokia

5


List of Tables

6

Table 1

Nokia products mapping with ETSI NFV............................................ 17

Table 2

Cloud infrastructure and application SW division............................... 18

Table 3

VNFC redundancy models................................................................. 22

Table 4

Dimensioning flavors in the AirScale RNC 17 release....................... 23

Table 5

Configuration limits in the AirScale RNC 17 release.......................... 24

Table 6

AirScale RNC release VMs deployment in RC1, RC2, RC3.............. 24

Table 7

Voice traffic profile.............................................................................. 25

Table 8

HSPA traffic profile..............................................................................25

Table 9

Smartphone traffic profile................................................................... 26

Table 10

Maximum capacity for user plane in AirScale RNC............................27

Table 11

Maximum capacity for control plane in AirScale RNC........................ 28

Table 12

Maximum capacity for network connectivity in AirScale RNC............ 28

Table 13

Control plane capacity with the smartphone traffic profile.................. 28

Table 14

User plane capacity with the smartphone traffic profile...................... 29

Table 15

OMS GUI applications........................................................................31

Table 16

HW configuration for the AirScale RNC 17 release............................43

Table 17

RC1, RC2 and RC3 reference configurations in the AirScale RNC 17 release................................................................................................44

© 2017 Nokia

DN09232214 Issue: 01B


Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Changes between Issue 01A (2017-05-18, AirScale RNC 17) and Issue 01B (201710-04, AirScale RNC 17): Maximum capacity •

Values for the Maximum number of DCH users (CS+PS) were added to the Maximum capacity for user plane in AirScale RNC

AirScale RNC requirements regarding the VNF infrastructure •

Number of compute nodes in the Table 16: HW configuration for the AirScale RNC 17 release table has been updated.

Smartphone capacity •

The Smartphone PS Erlangs values for the User plane capacity with the smartphone traffic profile table were corrected.

Changes between Issue 01 (2017-03-03, AirScale RNC 17) and Issue 01A (2017-0518, AirScale RNC 17): Introduction •

The chapter was removed.

Overview of AirScale RNC •

The chapter was updated.

OSS elements in 3G networks •

The sections on OMS, CBAM and L3 data collection and analysis solutions were updated.

AirScale RNC as a VNF within the ETSI NFV •

The figure on ETSI NFV framework was updated.

VM dimensioning •

The table on dimensioning flavors was updated.

Configuration limits •

The note on the number of EIPU pairs for configuration limits was modified.

Reference configurations •

The note on the number of EIPU pairs in different reference configurations was modified.

HSPA traffic profile reference

DN09232214 Issue: 01B

© 2017 Nokia

7

Summary of changes


•

The table on HSPA traffic profile was updated.

Smartphone traffic profile reference •

The table on smartphone traffic profile was updated.

Maximum capacity • •

The table on maximum capacity for user plane in the AirScale RNC was updated. The table on maximum capacity for control plane in the AirScale RNC was updated.

Smartphone capacity • •

The table on control plane capacity with the smartphone traffic profile was updated. The table on user plane capacity with the smartphone traffic profile was updated.

Operation and Management Server • •

The figure of OMS GUI main view on applications was updated. The figure of OMS GUI main view on external applications was updated.

CBAM functionalities •

The section on VNF operations was updated.

AirScale RNC monitoring and measuring •

The topic has been divided into three subchapters: – – –

L3 Data Collector and L3 Data Analyzer Traffica for radio WCDMA network NetAct TraceViewer

Site Solution •

The VNF internal networks and VNF external networks sections were added.

This is the first issue of the document.

8

© 2017 Nokia

DN09232214 Issue: 01B


Overview of AirScale RNC

1 Overview of AirScale RNC The AirScale RNC functionality and benefits The Radio Network Controller (RNC) is a network element (NE) responsible for radio resource management (RRM) and telecommunication management in WCDMA RAN. AirScale RNC, which is a cloud-based RNC product, runs on top of Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR) deployed on a Nokia AirFrame Data Center Solution (NDCS). Thanks to AirScale RNC, you can combine the functionality of the existing Nokia solutions with cloud-based capabilities. Nokia designs AirScale RNC to support easy scaling of the resources. AirScale RNC adapts to changing capacity, connectivity and functionality in a flexible and cost-efficient way. It means that you can scale in or scale out the capacity in AirScale RNC, and be sure that the hardware use is optimized.

1.1 Radio controller functionalities Radio controllers provide radio resource management (RRM), operation and maintenance, telecom, transmission, transport, and measurement and observation functionalities. Radio resource management The available radio spectrum is used efficiently to optimize the inter-related cell coverage, cell capacity and service quality aspects according to the network planning and end-user experience targets. The advanced RRM algorithms (admission control, handover control, load control, packet scheduling and power control) make this possible. The RRM solution features a wide selection of radio bearers and Quality of Service (QoS) mechanisms. AirScale RNC RRM manages the channel allocations, that is, the number of traffic channels and signaling channels that you can use in the Radio Access Network (RAN) simultaneously. This is done in connection with the radio network planning. RRM can be divided into network-based functions and connection-based functions. Figure 1

Radio Resource Management

Network-based

Admission

Load

Packet

functions

Control

Control

Scheduler

Power

Handover

Control

Control

Connection-based functions

DN09232214 Issue: 01B

© 2017 Nokia

9



Some network-based functions, for example, admission control and packet scheduler, work on event basis, that is, service requests are handled as they arrive. Load control is a continuous process of monitoring the cell load and managing the loads when necessary. When it comes to the connection-based functions, power control and handover control are activated when a radio link is allocated to a connection. The user equipment (UE) runs the handover control, outer loop power control and fast closed loop power control in the mobile Cell_DCH state. In other states the UE uses the open loop power control. Admission control

The Admission control (AC) is used to maintain stability and to achieve high traffic capacity of the RAN. When AirScale RNC receives any kind of radio resource request, the admission control of the RRM estimates the minimum radio resources that are required to provide the expected quality of the service described in the request. If these resources are available, the AC allocates them. The AC algorithm is executed at the radio access bearer setup or modification. The AC measurement takes place also in all handover types.

Load control

Load control (LC) ensures that the system is not overloaded and that it remains stable. If, however, the system is overloaded, it returns to the normal load state, defined by the radio network planning in a quick and controlled manner.

Power control

Since the WCDMA system is interference-limited (less interference equals more capacity), it is beneficial that the transmitting entities use as low transmission power as possible. The goal of the power control (PC) is to achieve the minimum signal-to-interference ratio (SIR) required for a connection to be of sufficient quality. PC works on a radio link basis.

Handover control

Handover (HO) control ensures that the UE is connected to the strongest cell at all times, and supports user mobility by ensuring that the radio connection is uninterrupted while the UE moves in the network. Soft and hard handovers are both supported in the RAN. HOs are controlled by AirScale RNC, but both the UE and AirScale RNC can initiate them.

Packet scheduler

The packet scheduler is a general feature which takes care of scheduling radio resources for the non-real-time radio bearers.

Operation and maintenance O&M is implemented in the Operation and Management Server (OMS) and in AirScale RNC. OMS aggregates, parses, and consolidates operation and management traffic flow between NetAct and access network elements under control of NetAct. NetAct does not need to perform individual management operations towards each network element, since those are performed in the lower level of the management hierarchy by OMS. As for AirScale RNC, O&M contains the cellular network-related functions such as: • •

10

Radio network configuration management Radio network recovery

© 2017 Nokia

DN09232214 Issue: 01B


• • •


Radio network database Radio network monitoring and measurements Mediation functionality towards BTSs

The standalone WCDMA OMS deploys a common O&M solution for a variety of dedicated radio controllers. It provides operability and management services for: • • •

Radio network configuration management Fault management Radio network measurements

For more information on the dedicated OMS, see the RAN1783: Standalone OMS for RNC . Telecom Telecom basic functionality and end-user related features concentrate on the functional procedures and end-user services provided by the RAN, such as: • • • • • •

User plane processing towards the circuit-switched (CS) and packet-switched (PS) core networks as in radio access bearers (RAB) management Radio network layer control plane processing Security functions, integrity checking, ciphering Location services Service area broadcast HSPA functionalities

Transmission and transport Transmission and transport features include: •

Transmission interfaces for IP over Ethernet

Measurements and observations AirScale RNC executes various measurements about radio network, transmission network and the controller performance. You can measure cell loads, handover control and outer loop power control in the radio network in real time (online monitoring). In the controller there are also extended key performance indicators (KPIs) calculating possibilities.

1.2 AirScale RNC within the 3G System Network topology AirScale RNC provides the radio controller functionality in the 3G architecture. The 3G network architecture is divided into three subsystems: • •

DN09232214 Issue: 01B

WCDMA Radio Access Network (RAN) Core Network (CN)

© 2017 Nokia

11


•


Operations Support System (OSS)

Despite being deployed within a Cloud infrastructure, AirScale RNC is completely integrated into the 3G network, maintaining the complete set of relations and interfaces to the remaining network elements. Other NEs within the network might be deployed as Cloud or dedicated HW solutions without having an impact on the logical architecture of the Nokia WCDMA system. Figure 2

3G Network architecture Core network elements

WCDMA RAN elements

Operating support system

Network analysis solution

MSS WCDMA BTS

RNC lub

IMS: Im, Presence Poc, Video Sharing

BTSOM luCS-U

luPS-U

IuPS-U MGW or IuPS-C SGSN

3D GL Go

lur

3D GL Interface

NetAct Traceviewer

IuPS-U or IuPS-C

NetAct platform

CBAM

L3 Data Collector & Viewer

Gn-C

Troubleshooting Monitoring

NWI3

luPS-U luPS-U

L3 messages /RTTs

Gi

luPS-U

GGSN luCS-U

lu-BC

Content and Connectivity Internet+Intranet OMS

OAM

L3 data TCP connection

Traffica

lub BTSOM

WCDMA BTS

SAS

AirScale RNC

Real time data

SAS SAS

lu-BC

CBC

CG

SAS

Iu-PC

1.2.1

RAN in 3G system Radio Access Network (RAN) functionalities The RAN consists of one or more radio network subsystems (RNSs). The RNS is a subnetwork within the RAN and it consists of one radio network controller (RNC) and one or more base transceiver stations (BTSs). The RNC controls the radio network while the BTS physically implements the WCDMA radio path. WCDMA RAN: •

•

12

supports the radio access and related functions. The major impact on the design of WCDMA RAN is the requirement to support the soft handover (one terminal connected to the network via two or more active cells) and the WCDMA-specific radio resource management (RRM) algorithms. maximizes the commonalities in the handling of the packet-switched (PS) and circuitswitched (CS) data, with a unique radio interface protocol stack and with the use of the same interface for the connection from the WCDMA RAN to both PS and CS domains of the core network.

© 2017 Nokia

DN09232214 Issue: 01B


• •

1.2.1.1


maximizes the commonalities with GSM, when possible. uses the IP transport as the transport mechanisms.

Core network elements in 3G networks 3G core network elements include the MSC, MGW, SGSN, GGSN, Cell broadcast center, SAS, CG, and IMS. MSS

The MSC server (MSS) is a core element that acts as a server providing the call control, multimedia gateways control, and allows the same circuit-switched (CS) services as the mobile services switching center (MSC). The MSS integrates the functions of an MSC, visitor location register (VLR), service switching point (SSP), and multimedia gateway (MGW) control into a single entity. The MSS is a further development of the 3G MSC.

MGW

The Multimedia gateway (MGW) is a core network element used for transmitting and converting the user plane traffic both in the CS core networks and in the IP multimedia subsystem (IMS). For more information, see MGW Product Documentation.

SGSN

The Serving GPRS support node (SGSN) is a 2G core element that serves the GPRS mobile stations by sending or receiving the packets via a base station subsystem or a radio access network. The SGSN is the basic element of GPRS infrastructure. It stores parameters used to route the packets into the network. The SGSN can be integrated in 3G technology. For more information, see SGSN Product Documentation.

GGSN

The Gateway GPRS support node (GGSN) is a 2G core element that acts as a gateway between the GPRS network and a packet-switched public data network (PSPDN). In the PSPDN, the GPRS network resembles a subnetwork, which transfers data to or from a GPRS mobile station. The GGSN hides the operation of the GPRS network from the PSPDN through the encapsulation of the packets. For more information, see GGSN Product Documentation.

CBC

The Cell broadcast centre (CBC) is a core network element used by the operator for centralized control of message transfer throughout a cell.

SAS

The Standalone A-GPS Serving Mobile Location Center (SAS) is a core network element that acts as a location calculation server. It calculates the final location and estimates its accuracy.

CG

The Charging gateway (CG) is a core network element that receives charging records (CDR) from other network elements, gathers the CDRs of calls and then forwards the collected ones to the billing system.

IMS

The IMS provides the IP multimedia services that complement the services provided by the CS core network

DN09232214 Issue: 01B

© 2017 Nokia

13



domain. The IMS contains all core network elements that are necessary for providing the multimedia services.

1.2.1.2

RAN elements in 3G networks WCDMA RAN elements include the radio network controller (RNC) and the base transceiver station (BTS).

1.2.1.3

RNC

The RNC is a network element responsible for radio resource management (RRM) and telecommunication management in WCDMA RAN. Nokia offers a variety of RNC solutions: IPA-RNC, mcRNC, and AirScale RNC.

WCDMA BTS

The main function of the BTS is to perform the radio interface L1 processing such as channel coding and interleaving, rate adaptation, and spreading. It also performs some basic RRM operations as the inner loop power control.

OSS elements in 3G networks 3G network Operations Support System (OSS) elements include OMS, NetAct, and CBAM. OMS

The Operation and Management Server (OMS) acts as an Element Manager (EM) for AirScale RNC. It is designed for operational and installation purposes. It performs operation and management functions related to configuration, performance, and fault management of network elements.

NetAct

NetAct is an operations support system for WCDMA, GSM, and long term evolution (LTE). NetAct is a framework that offers a versatile network and mobile service management solution.

CBAM

CloudBand Application Manager (CBAM) is a generic Virtualized Network Function Manager (VNFM) compliant with ETSI Network Function Virtualization (NFV). It automates Virtualized Network Function (VNF) lifecycle management and cloud resource management. Its standards-based application programming interfaces (APIs) make it easy to work with any VNF, Element Management System (EMS), Virtualized Infrastructure Manager (VIM), and NFV Orchestrator (NFVO). CBAM provides the framework for VNF templates and scripts to perform the actual operations. These artefacts define how and what is deployed when a new virtual network element (NE) is instantiated, and the rules when and how the services of the VNFs are scaled. One CBAM can control the VNF operations of several small data centers, or if the data center is large enough, a dedicated CBAM can be assigned for the VNF management within that data center.

14

© 2017 Nokia

DN09232214 Issue: 01B



CBAM possesses information on the Virtual Network Function Instances (VNFIs) and their VMs within its data centers. L3 data collection and analysis solutions

L3 data collection and analysis solutions provide a deep analysis of the network behaviors. They capture signaling data and signaling interfaces to monitor and analyze them.

The L3 Data Collection L3 Data Analyzer

L3 Data Collector application provides user interface, and controls data collection. It receives, stores and forwards the L3 data. It can be used with the L3 Data Analyzer application for collected data analysis.

Traffica

Traffica is used for real-time monitoring and troubleshooting in the network. Operators can monitor both the quality of the service and quality of the network. They are able to see the functioning of the network all the way down to the individual subscriber. Traffica can be used in multi technology environments by combining the graphs received from 2G, 3G and 4G networks into one screen. It provides end-user specific, detailed information about successful and unsuccessful call attempts, data session activations and location information including root cause for failure.

3 Dimension Geo Location (3D GL)

It is a software solution that incorporates the advanced and sophisticated radio analysis methods for the Radio Access Network (RAN) analysis and optimization. Massive data are grabbed from the Telecom Operator Network via an interconnection to the L3 Data Collector platform.

NetAct TraceViewer

The NetAct TraceViewer is a solution providing a mechanism to manage, collect and view data from different NEs that is related to a specific subscriber, a mobile phone, a particular cell or an NE.

1.3 Logical interfaces in a radio controller AirScale RNC provides logical interfaces to base transceiver stations (BTSs), other radio controllers, operations support systems (OSS), packet-switched (PS) and circuitswitched (CS) core networks, the cell broadcast center (CBC), and the stand-alone SMLC (SAS).

DN09232214 Issue: 01B

© 2017 Nokia

15



Figure 3

Logical interfaces of AirScale RNC NetAct

NWI3

CBAM

OMS

SSH

BTSOM CS Core network

lub

BTS

AirScale RNC

lu-CS

lu-PS

BTSOM

PS Core network

lur

lu-BC

lu-PC

CBC RNC

CBC

SAS

Descriptions of the particular interfaces: Iu-CS

Logical interface between the controller and the CS core network

Iu-PS

Logical interface between the controller and the PS core network

Iur

Logical interface for the interconnection of two neighboring controllers

Iub

Logical interface between the controller and the WBTS

Iu-BC

Logical interface between the controller and the CBC

Iu-PC

Logical interface between the controller and the SAS

BTSOM

Nokia proprietary O&M interface

OAM

Nokia proprietary O&M interface

1.4 AirScale RNC as a VNF within the ETSI NFV The AirScale RNC application deployed within the Nokia Airframe Data Center Solution (NDCS) acts as a Virtualized Network Function (VNF) within the ETSI Network Function Virtualization (NFV) framework.

16

© 2017 Nokia

DN09232214 Issue: 01B



NFV is a network architecture concept defined by ETSI, which leverages standard IT virtualization technology to consolidate many network equipment types onto industrystandard high-volume servers, switches and storage, which can be located in data centers, network nodes and in the end-user premises. Within the NFV framework, VNFs are run on the virtual machines (VMs) within a Network Function Virtualization Infrastructure (NFVI). Reference configurations for AirScale RNC run on VMs hosted by the Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR) which is deployed over a particular configuration of hardware resources. Figure 4

ETSI NFV framework Os-Ma

OSS/BSS Service, VNF and Infrastructure Description

Se-Ma

Orchestrator

Or-Vnfm

EMS 1

EMS 2

EMS 3

VNF 1

VNF 2

VNF 3

Vn-Nf NFVI

Vn-Nf

Virtual Computing

Ve-Vnfm

VNF Manager(s)

Or-Vi

Vn-Nf

Virtual Storage

Virtual Network

Vi-Vnfm

Virtualisation Layer VI-Ha

Computing Hardware

Table 1

Hardware resources Storage Network Hardware Hardware

Nf-Vi

Virtualised Infrastructure Manager(s)

Nokia products mapping with ETSI NFV ETSI NFV entity

Nokia product

EMS

NetAct

VNF

AirScale RNC

VNF Manager

CBAM

NFVI

NCIR software running on NDCS hardware

Virtualization is designed to maintain the original functionality of standard 3GPP Network Elements. All of the Nokia VNF applications maintain their standard 3GPP interfaces available, similarly to the traditional, non-cloud based telecommunication applications running on the dedicated hardware.

DN09232214 Issue: 01B

© 2017 Nokia

17

Functional architecture


2 Functional architecture AirScale RNC is a radio controller Virtual Network Function (VNF) application deployed on top of Nokia telco cloud infrastructure. AirScale RNC consists of virtualized RNC application software running on top of the Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR). The NCIR cloud infrastructure is deployed on the Nokia AirFrame Data Center Solution (NDCS). Individual VNFs can be understood as guest applications running on top of a host Network Function Virtualization Infrastructure (NFVI). Table 2

Cloud infrastructure and application SW division

Infrastructure/application elements

Element type

AirScale RNC

VNF (guest)

NCIR

NFVI (host)

NDCS

Similarly to the physical Nokia RNC products, the AirScale RNC architecture consists of a number of high-level functions: • • • • • •

Network interface functions Switching functions (provided by the NFVI) Control plane processing User plane processing Carrier connectivity functions O&M functions

The AirScale RNC functions are covered by individual Virtual Network Function Components (VNFCs) which are mapped to the dedicated virtual machines (VMs) within the NFVI. The computing resource flexibility of the NFVI enables a large degree of functional architecture freedom. Resource scaling enables AirScale RNC to scale the number of VNFCs. AirScale RNC VNFCs

18

Centralized Functions Processing Unit (CFPU)

Hosts O&M and centralized processing functions.

Cell-specific Processing Unit (CSPU)

Cell-specific control and user plane processing.

UE-specific Processing Unit (USPU)

UE-specific control and user plane processing.

External Interface Processing Unit/Network Processing Unit (EIPU)

Terminates control and user plane traffic.

Storage Node (SN)

Redundant and distributed block storage.

Upgrade VM (UVM)

Ephemeral unit deployed during software upgrades.

© 2017 Nokia

DN09232214 Issue: 01B


Figure 5


VNFCs in AirScale RNC

N+

2N

USPU

EIPU

N+ CSPU

2N

2N SN

CFPU Ctrl/User Planes

UVM

Mgt Plane

VNF Network Site/Edge Routers

OAM

Backbone/Backhaul

2.1 CFPU functionalities The Centralized Functions Processing Unit (CFPU) supervises and controls the functions of the AirScale RNC. The CFPU, which is one of the AirScale RNC VNFs, provides all centralized services needed for running AirScale RNC. These services include: • • • •

O&M functions Cell network-related functions, including radio network configuration management and radio network recovery Centralized functions related to the call management Centralized functions related to the location services

The CFPU hosts also the radio network database that contains the radio network configuration, as well as the master LDAP database that contains most of the configuration data of the radio controller.

2.2 CSPU functionalities The Cell-specific Processing Unit (CSPU) implements all cell-specific processing of control plane (C-plane) and user plane (U-plane) traffic. All the C-plane and U-plane resources of a particular base transceiver station (BTS) are allocated to the same CSPU unit. This makes the CSPU units completely independent of each other, so that different CSPUs might not have any kind of mutual communication. The allocation of the BTSs to the specific CSPUs is facilitated by the O&M functionality in the CFPU.

DN09232214 Issue: 01B

© 2017 Nokia

19



The CFPU allows to support the graceful reallocation of BTSs from one CSPU to another on a one-by-one basis. All existing CSPU units within AirScale RNC form a common resource pool where any unit can be allocated to handle the resources related to a certain BTS.

2.3 USPU functionalities The UE-specific Processing Unit (USPU) implements all services for UE-specific control and user plane processing. All dedicated control plane and user plane resources for a single UE are allocated to the same USPU unit. This makes USPU units completely independent of each other, so that different USPUs might not have any kind of mutual communication. All USPU units within AirScale RNC form a common resource pool where any unit can be allocated to handle the resources of a particular UE.

2.4 EIPU functionalities The External Interface Processing Unit (EIPU) hosts the networking and transport stacks needed for processing both signaling and user plane data. The EIPU terminates the control and user plane traffic at the IP layer. The EIPU units are deployed in pairs. Each EIPU is allocated to a different Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR) compute nodes. This provides redundancy for external connectivity, and covers possible infrastructure failures. The incoming traffic from the virtual network interfaces of a Virtual Network Function Component (VNFC) module is assigned to the EIPU unit within the same infrastructure node.

2.5 Other nodes Additional Virtual Network Function Components (VNFCs) are responsible for supporting the functionalities. Storage Node (SN) Redundant and distributed storage block. AirScale RNC requires the deployment of three storage nodes: • •

Redundant SN-0 and SN-1 holding the actual storage volumes SN-2 acting as a quorum server

Reliability is further increased by deploying each SN in different compute nodes and deploying the redundant storage service in Nokia AirFrame Cloud Infrastructure for Realtime applications (NCIR).

20

© 2017 Nokia

DN09232214 Issue: 01B



Upgrade VM (UVM) The UVM is an ephemeral unit deployed to support the AirScale RNC SW upgrades.

DN09232214 Issue: 01B

© 2017 Nokia

21

AirScale RNC redundancy model


3 AirScale RNC redundancy model Each Virtual Network Function Component (VNFC) unit within the AirScale RNC is deployed with a particular redundancy model. RNC components are constantly monitored. When a defect is detected in an active functional entity, a spare entity is activated by an automatic recovery function. The RNC is designed to meet the availability recommendations of the ITU Telecommunication Standardization Sector (ITU-T). Simplicity and speed of the maintenance procedures are the prerequisites for the availability of RNC. The maintenance is improved and easier due to the simplified modularity of the equipment, automatic fault detection procedures and elimination of downtime by using a hot standby unit in the event of a failure. Table 3

VNFC redundancy models VNFC

Redundancy model

Notes

CFPU

2N

-

CSPU

N+

-

USPU

N+

-

EIPU

2N

-

SN

2N

-

UVM

No backup

The ephemeral node type used during release upgrade

3.1 Redundancy principles 2N, N+ principles provide different approaches to unit redundancy.

22

Duplication (2N)

If the spare unit is designated for one active unit only, the software in the spare unit is kept synchronized so that taking it in use in fault situations (switchover) is very fast. The spare unit can be in the hot standby mode.

Load sharing (N+)

Unit groups can act as resource pools. The number of units in the pool is selected so that their resource capacity exceeds the strictly required parameters. If the units within the resource pool are disabled because of faults, the group as a whole is still able to perform all actions by sharing the unit's faults load. A higher level function must be in place to perform the load distribution and monitor the health status of the individual units. If one of the load sharing units fails, its load is distributed among the rest of the units, which enables a gradual degradation of the performance in the failure scenarios.

© 2017 Nokia

DN09232214 Issue: 01B


Capacity and VM dimensioning

4 Capacity and VM dimensioning The virtual machines (VMs) deploying particular AirScale RNC VNFC nodes are subject to dimensioning considerations, which are managed through VM flavors. AirScale RNC VNF consists of various VMs which are subject to dimensioning considerations that are managed through VM flavors. Additionally, the number of each VM type is limited by the SW and available HW. Both the VM flavors and VM deployment impact the capacity of AirScale RNC VNF. This chapter describes the VM flavors and configuration limits as well as the pre-defined reference configurations on the reference cloud infrastructure, and the capacity reached with each of these reference configurations with different traffic models.

4.1 VM dimensioning AirScale RNC flavor dimensioning The OpenStack cloud environment defines the flavors as virtual hardware templates, which define the dimensioning of virtual memory, storage, and computing resources for a particular virtual machine (VM). Each Virtual Network Function Component (VNFC) within AirScale RNC is deployed as one or more VMs. VMs serving the same VNFC node share the same VM flavor. Table 4

Dimensioning flavors in the AirScale RNC 17 release

VM Type

g

Number of vCPUs

Memory (MB)

Disk storage (GB)

SN

2

4096

10

CFPU

6

12288

10

CSPU

6

12288

10

USPU

8

12288

10

EIPU

12

12288

10

UVM

2

4096

10

Note: Assuming hyper-threading is enabled, the provided values are valid for the AirScale RNC dimensioning flavors.

4.2 Configuration limits Maximum and minimum numbers of VMs in AirScale RNC Table 5: Configuration limits in the AirScale RNC 17 release lists the minimum and maximum number of each VM type in the AirScale RNC 17 release. The minimum numbers enable an AirScale RNC VNF with the required redundancy of VMs. The

DN09232214 Issue: 01B

© 2017 Nokia

23



absolute maximum numbers define the limits set by the SW. Note that it is not possible to configure all VMs with maximum number simultaneously. For more information, see the Reference configurations section. Table 5

Configuration limits in the AirScale RNC 17 release VM Type

g

Absolute Maximum 1

Minimum

SN

3

3

CFPU

2

2

CSPU

2

39

USPU

2

77

EIPU2

2

16

UVM

0

1

Note: 1 Absolute maximum values are limited by the software in the AirScale RNC 17 release. This limitation might change in future releases. 2

EIPUs are deployed in pairs. The number of EIPU pairs in minimum and maximum limits is 1 and 8.

4.3 Reference configurations Deployment of virtual machines (VMs) in the AirScale RNC 17 release Three reference configurations have been defined in the AirScale RNC 17 release in order to support dimensioning of the product on NDCS RM 17 full-rack redundant configuration described in AirScale RNC requirements regarding the VNF infrastructure: RC1 (6 compute nodes) RC2 (10 compute nodes) RC3 (20 compute nodes)

• • •

Table 6

AirScale RNC release VMs deployment in RC1, RC2, RC3

VM Type

g

24

RC1

RC2

RC3

SN

3

3

3

CFPU

2

2

2

CSPU

4

6

12

USPU

15

29

65

EIPU1

4

8

16

UVM

1

1

1

Note: 1 EIPUs are deployed in pairs. The number of EIPU pairs in different reference configurations is 2, 4 and 8.

© 2017 Nokia

DN09232214 Issue: 01B



4.4 Reference traffic profiles Three different traffic profiles are defined and used in the AirScale RNC 17 release for modeling different traffic patterns. Reference traffic profiles vary in the user equipment (UE) distribution percentage. Traffic profiles are described by the numbers which base on the UE distribution. Traffic profiles assumptions are as follows: Voice traffic profile reference: 50% are basic UE, 45% are smartphones, and 5% are laptops. HSPA traffic profile reference: 20% are basic UE, 22% are smartphones and 58% are laptops. Smartphone traffic profile reference: 13% are basic UE, 80% are smartphones and 7% are laptops.

• • •

4.4.1

Voice traffic profile reference The voice traffic profile represents the traffic in a voice dominated network. Table 7

Voice traffic profile Property

g 4.4.2

Value

Mean holding time (MHT)

90 s

Proportion of UE originating calls

55%

Proportion of UE terminating calls

45%

Proportion of handovers

40%

- hard handovers

0.1 per call

- soft handovers

6 per call

Bearer

16 kbps

Traffic per user

25 mErl

CS BHCA per subscriber

1

SHO interval

15 s

Note: The voice traffic profile is used for the maximum AMR calculation for the three reference configurations in the Maximum capacity section.

HSPA traffic profile reference The HSPA traffic profile represents the traffic in a data dominated network. Table 8

HSPA traffic profile Property

RAB MHT

DN09232214 Issue: 01B

Value

1000 s

© 2017 Nokia

25


Table 8


HSPA traffic profile (Cont.) Property

g 4.4.3

Value

SHO interval

15 s

Total data transfer duration per RAB

820 s

HSPA RAB active time bit rate

206 kbps

Average bit rate during data transfer

191 kbps

PS RAB BHCA per laptop UE

1


0

Number of data transfers per RAB

3.4

Number of state changes to DCH per HSPA RAB

3.4

Note: This HSPA traffic profile is used for the maximum throughput calculation for the three reference configurations in the Maximum capacity section.

Smartphone traffic profile reference Smartphone traffic profile represents the traffic in a network where traffic is dominated by signaling generated by smartphones. The smartphone traffic profile assumes higher usage of traditional packet-switched (PS) services (for example, web browsing), and Always On applications (instant messaging, app widgets, push mail, location services, and so on) generate a lot of signaling traffic. For a good user experience, each Always On application must keep the IP connection active for a long time. This is achieved by sending the keepalive messages (heartbeats) periodically. As a result, each Always On application on top of the user plane data must send and receive small packets very frequently. Depending on the application and network configuration or parametrization, each heartbeat triggers some signaling events, which must be processed in the RNC (state transition from Cell_PCH to Cell_FACH/Cell_DCH or even whole PS call attempt procedure). The resulting smartphone traffic profile is characterized by a very high control plane load compared to a low PS throughput. Table 9

Smartphone traffic profile Property

26

Value


0.9

PS BHCA per subscriber

1.3

CS Mean Holding Time

84 s

Proportion of handovers

40%

- hard handovers

0.1 per CS call

- soft handovers

6 per CS call

CS traffic per user

21 mErl

PS traffic per user

13 kbps

NAS BHCA per user

2.8

© 2017 Nokia

DN09232214 Issue: 01B


Table 9


Smartphone traffic profile (Cont.) Property

g

Value

PS RAB MHT

1132 s

PS session BHCA per smartphone subscriber

16.3

PS session BHCA for human per smartphone subscriber

6

PS session BHCA for pollings per smartphone subscriber

10.3

SHO per PS RAB

1.9

Note: PS session BHCA per subscriber is a sum of PS session BHCA for human per subscriber and PS session BHCA for pollings per subscriber. Session means RAB setup, state change to CELL_DCH, state change to HSFACH/RACH.

g

Note: The smartphone traffic profile is used for the smartphone capacity values for the reference configurations described in the Smartphone capacity section.

4.5 Maximum capacity Capacity values of AirScale RNC Maximum capacity is achieved by AirScale RNC according to the traffic mix rule described in Dimensioning AirScale RNC . The maximum capacities of AirScale RNC assume that, with a certain traffic profile, the unit processor loads do not exceed 80%. It is impossible to reach the maximum voice capacity and data throughput capacity simultaneously as they are defined with different traffic profiles. Table 10

Maximum capacity for user plane in AirScale RNC

Reference configuration

RC1

RC2

RC3

AMR Erlangs

18 860

37 720

75 450

AMR Erlangs (including soft handover)

26 400

52 810

105 630

User plane (U-plane) throughput (Iub total in Mbps)

6 110

11 820

26 480

DL U-plane throughput (Iub total in Mbps)

5 410

10 460

23 430

UL U-plane throughput (Iub total in Mbps)

700

1 360

3 050

Maximum number of DCH users (CS+PS)

28 020

54 160

121 400

DN09232214 Issue: 01B

© 2017 Nokia

27


Table 11


Maximum capacity for control plane in AirScale RNC


g

RC1

RC2

RC3

RNC subscribers

680 640

1 361 280

2 722 570

AMR Busy Hour Call Attempts

680 640

1 361 280

2 722 570

PS Busy Hour Call Attempts1

1 957 000

4 893 000

11 090 000

PS Session2 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

Maximum number of RRC connected UEs

400 000

942 500

1 000 000

Note: 1 Packet-Switched (PS) Radio Access Bearer (RAB) Busy Hour Call Attempts (BHCA) assuming 2x PS HSPA session per RAB 2

Session: RAB setup, state change to CELL_DCH, state change to HS-FACH/RACH

3 AirScale

Table 12

RNC signaling capacity Maximum capacity for network connectivity in AirScale RNC

Reference Configuration

RC1

RC2

RC3

Maximum number of cells

2 640

6 600

10 000

Maximum number of BTS equipment

520

1 320

2 000

4.6 Smartphone capacity Maximum capacity values achievable with the smartphone traffic profile Because of high control plane resource consumption caused by smartphones, the AirScale RNC maximum capacity described in Table 12: Maximum capacity for network connectivity in AirScale RNC cannot be achieved in a network with high smartphone penetration. In order to have an indication on the achievable capacity with smartphone traffic profile separate capacity limits are defined. Table 13

Control plane capacity with the smartphone traffic profile


28

RC1

RC2

RC3

Smartphone CS+PS BHCA

501 090

1 079 680

2 159 360

Smartphone CS+PS session BHCA

1 491 840

3 729 730

7 520 580

Smartphone CS BHCA

202 940

434 220

868 450

Smartphone PS BHCA

298 150

645 460

1 290 910

Smartphone PS session BHCA

1 288 900

3 222 370

6 652 130

© 2017 Nokia

DN09232214 Issue: 01B


Table 14


User plane capacity with the smartphone traffic profile


RC1

RC2

RC3

Smartphone CS Erlangs

4 780

10 970

21 940

Smartphone PS Erlangs

28 020

54 160

121 400

Smartphone CS+PS Iub FP UL+DL throughput (Iub total in Mbps)

2 830

5 200

10 400

Smartphone CS+PS Iub FP DL throughput (Iub total in Mbps)

2 450

4 510

9 020

Smartphone CS+PS Iub FP UL throughput (Iub total in Mbps)

380

690

1 380

DN09232214 Issue: 01B

© 2017 Nokia

29

AirScale RNC Operation and Management


5 AirScale RNC Operation and Management Overview of the AirScale RNC operation and management infrastructure The AirScale RNC operation and management architecture is mainly composed of: • •

an Element Management System (EMS), meaning the Operation and Management Server (OMS) connected to NetAct with NWI3 interface. a Virtual Network Function Manager, meaning CloudBand Application Manager (CBAM).

However, the VNF and Virtual Network Function Component (VNFC) configuration can also be accessed via the Virtual Infrastructure Manager interfaces, meaning CLI and GUI. AirScale RNC has also an OMS that is included in the operability solution.

5.1 NetAct operations and management NetAct offers a uniform set of tools for radio, core and transport network management. Overview of NetAct NetAct enables full visibility of the network. It provides comprehensive management for all communications networks, including the most complex multi-vendor and multitechnology ones. It provides a holistic view all the way from the network to the customer experience. It responds quickly to the changes and is automated to save time and effort. NetAct allows to upgrade the software of the controller or several controllers at the same time. Operator's benefits of using NetAct: • • • • •

It saves time and resources, and reduces manual errors with highly automated operations. It identifies customer service related problems. It improves operational efficiency. It deploys multi-vendor integrations quickly and ensures access to all relevant data immediately. It provides a common, reusable platform across all NetAct applications, boosting efficiency.

NetAct functionalities for the controller NetAct main tasks are concentrated on the following areas: • • • • • •

30

Performance Management Software Management Configuration Management Fault Management Troubleshooting Security

© 2017 Nokia

DN09232214 Issue: 01B



g

Note: For the AirScale RNC 17 release the cloud infrastructure information is not available.

g

Note: For the AirScale RNC 17 release the software management provides only software-version information. Actual software management is supported by CBAM. For more information on NetAct, see NetAct System Overview .

5.2 Operation and Management Server The Operation and Management Server (OMS) is a mandatory network element (NE) in the operability architecture of AirScale RNC Solution. The OMS contributes to the overall operation and management solution efficiency and helps the operators to achieve cost efficiency in the network operation and investments. The OMS performs operation and management activities towards AirScale RNC and WCDMA base stations. It provides the interface to the higher-level network management functions and local user interface functions. These functions include both generic interfacing to the data communication network (DCN) and application-specific functions such as processing of fault and performance management data, implementation of the user interface for AirScale RNC, and support for configuration management of AirScale RNC. This way the OMS provides an easy and flexible interfacing to AirScale RNC. The OMS supports multiple controllers with the stand-alone solution. The OMS software runs on top of a carrier-grade Linux-based SW platform. It is a highly available and reliable platform providing security and high performance. The OMS is responsible for: NetAct interface. user interface for the OMS and AirScale RNC, accessible locally or remotely. Both GUI functionalities and CLI or SCLI terminal sessions are supported. post-processing support for measurement and statistics tasks, local PM database and applications to manage data locally. alarm forwarding towards NetAct, alarm filtering, local fault management database and applications to manage the real-time data locally. configuration management changes forwarding towards NetAct and application to manage the current configuration data locally.

• • • • •

The OMS element manager provides several user interface applications. Table 15

OMS GUI applications

Application

Description

Topology Browser

The Topology Browser provides the user with a general view on the managed objects in the radio network (RNW). The RNW database contains the configuration data and the control parameters of the radio access network (RAN) controlled by the controller (AirScale RNC).

NE Parameter Editor

Allows the modification of the RNW parameters.

DN09232214 Issue: 01B

© 2017 Nokia

31


Table 15


OMS GUI applications (Cont.)

Application

Description

Radio Network Measurement Management

Allows the management of radio network measurements. RNW Measurement Management application is used to manage the AirScale RNC radio network measurements, WBTS radio network measurements and FlexiBTS transmission measurements.

Radio Network Measurement Presentation

Creates presentations from radio network measurement data.

Radio Network onlinemonitoring

The online monitoring feature can be used to obtain real-time information from the predefined cells. Online monitoring provides valuable information for configuring and optimizing the network.

Fault management

Fault management in OMS consists of a set of functions to detect and correct fault situations in the system. The Fault Management GUI can be used for monitoring fault situations, alarm cancellation and alarm parameters change.

NE Threshold Management

Used for setting threshold values for performance indicators.

For more information regarding OMS, see the OMS Product Description. The OMS offers a local operation interface towards the NEs. The interface makes it possible to monitor access networks locally via the OMS (not only in the network roll-out, upgrade and expansion phases, but also during regular daily operation, when reasonable). The OMS user interface applications are either web applications or Java-based client applications. Figure 6

32

OMS GUI main view on Applications

© 2017 Nokia

DN09232214 Issue: 01B


Figure 7


OMS GUI main view on External Applications

5.3 CBAM functionalities CloudBand Application Manager (CBAM) is a generic Virtualized Network Function Manager (VNFM) which automates VNF lifecycle management and cloud resource management. VNF operations Nokia deploys CBAM application as its Virtual Network Function Management (VNFM) solution. CBAM standard lifecycle operations include: VNF creation

AirScale RNC VNF is created in the inventory of CBAM.

VNF instantiation

AirScale RNC VNF is instantiated to the cloud infrastructure, and the connection towards OMS is commissioned.

VNF scalability

AirScale RNC VNF capacity and processing power is scaled by adding or removing virtual machines (VMs).

VNF termination

AirScale RNC VNF is terminated and the resources are freed from the cloud infrastructure.

VNF deletion

AirScale RNC VNF is deleted from the inventory of CBAM.

CBAM custom lifecycle operations for SW management include: Upgrade of the AirScale RNC VNF SW version

DN09232214 Issue: 01B

Automated workflow for performing VNF software upgrade consisting of pre-checks, data conversions, SW activation and post-checks.

© 2017 Nokia

33



Rollback of the AirScale RNC VNF SW version

Activation of previous VNF SW version and configuration in case VNF software upgrade fails.

Switchover of the AirScale RNC SW version

Switching between software image currently and previously activated on the VNF.

Query the AirScale RNC VNF SW versions

Lists the software images currently and previously activated on the VNF.

For more details on CBAM operations, see the CBAM user guide. VNF software update In cloud deployment, the SW management procedure of a network element (NE) is controlled by CBAM. In the SW upgrade, the new SW images and artifacts are onboarded to CBAM and NCIR. The Virtual Network Function Components (VNFCs) of the VNF are created newly with these new SW images. The new SW package of the Cloud NE includes SW for converting the old configuration with the required changes in the new SW. Figure 8

CBAM contribution in the AirScale RNC operation and management NFVO (optional) CBAM

CLS

NetAct

OMS BTSOM

VNF Topology & Lifecycle manager

Alarm Manager

Mistral Workflow engine

Resource Monitor

Ansible

NWI3

CLI over SSh

VNF - AirScale RNC

CBAM UI

k c a t S n e p O

Template store

s n o i t a r e p o

M F d u o l C

Openstack

Openstack APls Heat

Key stone Nova Cinder Neutron

V I M

5.4 SCLI characteristics AirScale RNC provides a structured command line interface (SCLI) for various configuration, administration and monitoring tasks. The SCLI is an extension of the basic command line interface that makes it easier to find and browse commands. With SCLI, the user can browse available commands in a command syntax tree view, use automatic command completion, and access contextsensitive help provided for the commands or individual parameters. Users can be

34

© 2017 Nokia

DN09232214 Issue: 01B



granted or denied access to the particular commands to prevent the unauthorized personnel from executing SCLI commands. This could have potential effects on, for example, the system traffic carrying capability. The SCLI Reference Guide describes the use of the AirScale RNC SCLI and lists the available commands, parameters and values. For more information, see AirScale RNC SCLI Commands.

5.5 AirScale RNC monitoring and measuring AirScale RNC provides a set of recording and monitoring tools, and interfaces to observe and analyze the whole performance. AirScale RNC offers a range of network analysis tools to manage, collect and view data from different network elements. These tools are: • • • •

L3 Data Collector and L3 Data Analyzer GEO Interface Traffica Interface NetAct TraceViewer

The aim is to see the functioning of the network, monitor the quality of the service and quality of the network, and analyze the performance.

5.5.1

L3 Data Collector and L3 Data Analyzer L3 Data Collector (L3 DC) and L3 Data Analyzer (L3 DA) are used for a deep Layer 3 (L3) signaling analysis. L3 Data Collector and L3 Data Analyzer The L3 DC and L3 DA offer comprehensive data collection and analysis framework for analyzing the events behind key performance indicators (KPIs) on L3 signaling level, and beyond it. The L3 DC and L3 DA offer a software platform that can be used to build new solutions required for Planning, Optimization and Troubleshooting networks.

DN09232214 Issue: 01B

© 2017 Nokia

35


Figure 9


L3 Data Collector and L3 Data Analyzer functional view AirScale RNC

Data Collector and Analyzer Server Data Collector: - data collection control - data receiving and storage - forwarding raw data to Data Analyzer

OMU (SP) OMU (WO)

Control process

Control Plane (CP) Data Provider

External L3-routed monitoring network

Data Analyzer: - real-time and offline data processing and analysis - forwarding processed data to other applications

Hard disk (RAID array)

GEO interface

Functional units with CP Data Provider Control Plane (CP) Data Provider Functional units with CP Data Provider: CFCP, USCP, CSCP, USUPPXY, CSUPPXY, EITPPXY, QNUP, QNIU, QNIUB

Control connection CCP data streams

L3 Data Collector The L3 DC is a log recording tool developed to collect data necessary in troubleshooting and other events requiring the detailed data analysis. The L3 DC continuously records all data related to the occurring events, and stores or forwards this information for further processing. The L3 DC collects message monitoring data from the network element (NE) in the real time. The data typically consists of L3 signaling of calls made through the NE. The collected data is stored on the hard disk and/or streamed to the receiving applications. The L3 DC does not analyze the data by itself. On the L3 DC application control data collection, reception, storage and forwarding are managed through a user interface. L3 Data Analyzer/Viewer The L3 DA is a message monitoring analysis tool. In the AirScale RNC, L3 DA combines all L3 messages that are related to a call going through the AirScaleRNC into one signaling flow view, including the NE internal L3 signaling messages and external interface messages with the L3 Viewer application that enable an analysis of the L3 signaling scenarios in a windows environment. For more information on L3 DC, see the Configuring the L3 Data Collector chapter in the Configuring IP Connectivity for Air Scale RNC document. GEO Interface Nokia GEO Interface is an open interface where third-party vendors can connect their GEO location solutions. The GEO Interface offers a real-time transmission control protocol (TCP) stream with all necessary information for the GEO location.

36

© 2017 Nokia

DN09232214 Issue: 01B



The local GUI of the GEO Interface is a start-stop type of interface including the IP address and Port definition for the message collection platform. For a GEO-interface user, only the actual third-party GEO location SW uses and shows the captured information. Figure 10

GEO Interface GEO IF 3G

L3 Data Collector AirScale RNC

HP or DELL windows server a.k.a Server

GEO Interface solution

GEO Interface solution Application/Service layer

Content of the interface: • • •

GEO Interface contains the call-specific L3 signaling messages in the ASN.1 format such as relevant NBAP, RRC, RANAP, and RNSAP messages. GEO Interface contains additional binary format information such as the interface control message and the RNC name. GEO Interface data is only readable by a Geo location solution on the other side of the interface.

Example of a 3G location solution: The 3 Dimension Geo Location (3D GL) is a software solution designed by R&D that incorporates more advanced and sofisticated radio analysis methods for the Radio Access Network analysis and optimization. The 3D GL supports currently UMTS and LTE. It is composed of three main blocs: • •

•

The data collection system that grabs massive data from the Telecom Operator Network via an interconnection to L3 DC Nokia platform. The CORE applications processing a unique and accurate GEO location of call sessions and measurement reports of the user equipment (UE). This extensive set of software allows to calculate the predictive coverage in three dimensions via many algorithms including the Nokia four rays tracing. This prediction is later compared with the network geolocalized data. In 3G, the UE measures many KPIs that are collected and represented in the 3D GL. Drop call, root causes and handovers are also available. The data center needs to have enough capacity to process the data in a useful time frame. The Business Intelligence (BI) interconnected with 2D and 3D Graphical Information Solutions (GIS) offers an unmatched, dynamic and unique interface allowing the display of maps constrained by the unlimited number of filters, rankings, selections queries N-CUBE cascaded selections, and so on.

Traffica Interface Traffica Interface implemented on the L3 DC server offers the real-time information about the network behavior for Traffica. This solution is available for 2G, 3G and the LTE version. The local GUI of the Traffica Interface is a start-stop type of interface with some parameters solution settings. The full presentation of data is done within Traffica itself. Traffica Interface is only providing the necessary information on this topic.

DN09232214 Issue: 01B

© 2017 Nokia

37


Figure 11


Traffica Interface Traffica IF 3G

L3 Data Collector AirScale RNC

Traffica Interface solution

3L Data Collector Server

Traffica Application/Service layer

Traffica Interface contains call-specific information needed for Traffica presentations. This interface data is readable only by the Traffica solution.

5.5.2

Traffica for radio WCDMA network Traffica is used for real-time monitoring and troubleshooting in the network. Traffica provides the operations teams with the real-time data on the quality levels for the Radio Access Network (RAN) services that are provided to the subscribers. The relevant operator teams can use tools such as Traffic Views for displaying the graphs updated in a real time to monitor the mobile services performance indicators and traffic news for troubleshooting, and an individual subscriber to identify the root cause of a failure situation. Traffica for radio WCDMA networks can offer the following functionalities: • •

•

• •

In a real time on a map of an NE or network location, the user can monitor the service quality and indicate the objects where the service degradation is the greatest. The user can understand the health of the inspected NE or network location by having, in a details panel, access to the status of the NEs or network location based on the last minutes service quality indicators. The user can drill down the functionality for the inspected network element or network location (for example, the user can drill down to individual error causes to identify the root cause of the failure). The user can use the map to visualize and get quick access to a certain point of interest. The user can drill down to the Traffic Views and Traffic News tools. The user can continue the investigation by a context-sensitive launch of Traffic Views and Traffic News, and get access to the raw data as received and calculated by the Traffica TNES.

For more information on Traffica, see Traffica 17.2 Release Documentation in Product Information Center ► Operations Support Systems ► Serve atOnce Traffica at NOLS https://online.networks.nokia.com .

5.5.3

NetAct TraceViewer NetAct TraceViewer features a system-level trace for a number of Nokia network elements (NEs) and systems. NetAct TraceViewer enables the operators to manage, collect, and view the data NEs related to a specific subscriber or a specific mobile phone.

38

© 2017 Nokia

DN09232214 Issue: 01B



With NetAct TraceViewer, it is possible to: analyze test calls network-wide. minimize the number of site visits and drive tests. analyze problems prior to an actual roll-out or introduction of services. verify radio network roll-out.

• • • •

System-level tracing relates to observing the activities of either a mobile phone (IMEI trace), a subscriber (IMSI, MSISDN trace), and a cell (Cell Name) or even NE (NE name) in a mobile network on a detailed level. Tracing data provides further insight into network performance, for example, a view of end-user quality of service (QoS) during a call, correlation between protocol messages and radio frequency measurements or interoperability with specific mobile vendors. To differentiate from reporting, tracing is an instant means of observation of a specific event and the data provided by tracing are used for troubleshooting and network optimization. For more information on NetAct TraceViewer, see NetAct 17.2 Final Operating Documentation in Product Information Center ► Operations Support Systems ► NetAct at NOLS https://online.networks.nokia.com .

5.6 AirScale RNC License Management AirScale RNC introduces a license management process through the Centralized License Server (CLS). Centralized licensing is introduced with AirScale RNC. The entire RNC license management becomes easier as the physical license keys are no longer installed in AirScale RNC, but they are pooled in the CLS. NetAct SW Entitlement Manager (SWEM) manages these pool licenses and keeps track of license usage, and allocates licenses automatically for AirScale RNC based on the usage. This solution supports pool licenses.

g

Note: WCDMA BTS licensing remains the same as in WCDMA 17 release, that is BTS licenses are not managed by CLS/SWEM.

DN09232214 Issue: 01B

© 2017 Nokia

39

Site Solution


6 Site Solution Overview of the subnets within the Virtual Network Function (VNF) internal and external networks The Virtual Network Function Components (VNFCs) that cover the AirScale RNC functionalities are interconnected by a series of internal and external subnets. Some of these networks are internal to AirScale RNC, while others are carried over outside of the cloud host. Figure 12

AirScale RNC internal and external subnets

Internal VNF networks

CSPU

USPU USPU

EIPU EIPU

CSPU CFPU

SN

UVM

External VNF networks ToR switches/ Edge Routers

External networks (VNF external)

Internal networks (VNF internal)

user plane network control plane network oam network monitoring network

internal network fastdist network management network

The controller and compute nodes are connected to two pairs of switches for redundancy, meaning Management and Data Top-of-Rack (ToR) switches. The Management ToR switch is used for Cloud Infrastructure management networks. The Data ToR switch is used for the VNF tenant networks and corresponding provider networks. It provides the internal and external network connectivity for the VNF. The site solutions therefore focus on the connectivity of the VNF with the Data ToR switches. Each compute node is physically connected to both ToR switches. These links are configured in an active-active link aggregation (LAG) mode. The ToR switches are configured in a multi-chassis link aggregation (MC-LAG) mode for redundancy and high availability. VNF internal networks

40

© 2017 Nokia

DN09232214 Issue: 01B


Site Solution

Internal network

Carries over platform-internal control and management traffic between the VMs.

Fastdist network

Carries over the user plane traffic between EIPU, CSPU, and USPU.

Management network

Retrieves user data from the metadata server.

VNF external networks External control plane network

Control plane network connected to other NE

External user plane networks

User plane networks connected to other NEs

OAM network

Network carrying over O&M traffic towards NetAct, Operation and Management Server (OMS), Traffica, and CloudBand Application Manager (CBAM)

Monitoring network

Network for the L3 Data Collector

6.1 Standalone Site Solution for AirScale RNC Standalone AirScale RNC utilizes the deployment of a single rack, which hosts all virtual machines (VMs) of a Virtualized Network Function (VNF). This standalone site solution assumes that the Virtual Network Function Components (VNFCs) supporting the VMs of the AirScale RNC application are hosted across the available compute nodes of Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR) cloud host. The connections between these VMs and between the VMs and external peer network elements (NEs) are carried over individual subnets configured over several Virtual Network Interface Controllers (vNICs) of the VMs. The traffic is carried by several provider Virtual Local Area Networks (VLANs) over the activeactive multi-chassis link aggregation (MC-LAG) interfaces which bind two physical links from each compute node with the Top-of-Rack (ToR) switches. The ToR switch acts as an L3 switch supporting MC-LAG and Virtual Router Redundancy Protocol (VRRP), and provides fully L3-routed interfaces to connect the rack to the Edge routers, avoiding risks and scalability issues of L2 integration. VRF-lite is used for traffic separation in the ToR and Edge devices. The open shortest path first (OSPF) protocol is used to exchange and update routes dynamically between the ToR and Edge devices. The standalone solution is more suitable for simpler configurations and where the ToR switches are directly integrated with the Edge routers. Multiple standalone AirScale RNCs can be connected to same pair of edge routers using additional spine switches.

DN09232214 Issue: 01B

© 2017 Nokia

41

Site Solution


Figure 13

Standalone AirScale RNC Site Solution

NetAct Compute Node VM Provider Network LAN

vNIC

WBTS

vNIC

AVS

OSPF

MC-LAG Provider VLANs

Core Active-active LAG

VRRP Data ToR

Edge Router

RNC

For more information on the standalone AirScale RNC site solutions, see the Standalone AirScale RNC Site Solutions chapter in the AirScale RNC Site Solutions document. For more information on the AirFrame data center, see AirFrame Data Center Solution, Rel. NDCS RM 17, Hardware Operating Documentation in Product Information Center ► Platforms ► AirFrame Data Center Solution at NOLS.

42

© 2017 Nokia

DN09232214 Issue: 01B


AirScale RNC requirements regarding the VNF infrastructure

7 AirScale RNC requirements regarding the VNF infrastructure AirScale RNC requires the Nokia AirFrame Cloud Infrastructure for Real-time applications (NCIR) deployed on Nokia Data Center Solution (NDCS) HW. NFVI requirements The AirScale RNC 17 release is supported on the Network Function Virtualization Infrastructure (NFVI) consisting of the following cloud stack and hardware: NCIR 16A SP1 (OpenStack) NDCS RM 17 (AirFrame HW)

• •

For more information on AirFrame Cloud Infrastructure and NCIR, see Nokia AirFrame Cloud Infrastructure for Real-time applications, Rel. NCI R16A SP1, Operating Documentation in Product Information Center ► Platforms ► AirFrame Cloud Infrastructure at NOLS. For more information on AirFrame data center, see AirFrame Data Center Solution, Rel. NDCS RM 17, Hardware Operating Documentation in Product Information Center ► Platforms ► AirFrame Data Center Solution at NOLS. HW configuration Table 16

HW configuration for the AirScale RNC 17 release Element

Full rack with full hardware redundancy

NCIR release

NCIR 16A SP1

NDCS (AirFrame HW) release

NDCS RM 17

Number of controller nodes

2

Number of storage nodes

2

Number of compute nodes

From 6 to 20

Number of ToR switches per rack

2 management ToR switches and 2 data ToR switches

ToR switch redundancy

MC-LAG

Availability zones

1

Maximum failure scope (SPoF)

1 server

Server BW

2-4x10GE (act/act LAG)

Maximum rack uplink BW

2x4x40 Gbps

L2 VLAN to Edge

Not recommended

L3+VXLAN to Edge

Supported

L3 routing to Edge

Supported with VRF lite

DN09232214 Issue: 01B

© 2017 Nokia

43

AirScale RNC requirements regarding the VNF infrastructure

Figure 14


AirFrame HW full rack configuration

Reference configurations for dimensioning AirScale RNC SW can be scaled to different configurations using the manual scaling functionality. For dimensioning tool purpose there are three reference configurations defined for the AirScale RNC 17 release. The number of compute nodes varies as presented in Table 17: RC1, RC2 and RC3 reference configurations in the AirScale RNC 17 release. The amount of controller nodes, storage nodes and switches is the same in all reference configurations as shown in Table 16: HW configuration for the AirScale RNC 17 release. This ensures the required redundancy, and also enables easy HW expansion by simply adding more compute nodes. Pre-cabled Nokia AirFrame Data Center Solution (NDCS) rack is recommended for all configurations. Table 17

RC1, RC2 and RC3 reference configurations in the AirScale RNC 17 release

Reference configuration name

44

Number of compute nodes

Power consumption in NDCS RM 17 HW**

Note

RC1

6*

3000 W

-

RC2

10*

4000 W

Half-rack configuration

RC3

20*

6500 W

Full-rack maximum configuration

© 2017 Nokia

DN09232214 Issue: 01B

AirScale RNC Product Description

Recommend Documents