No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.

NetAct™ 22

Single RAN Management Overview

DN09212604
Issue: 6-0 Final

© 2021 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.

Single RAN Management Overview DN09212604 6-0 Disclaimer

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and consulting with standards
bodies to ensure that terminology is inclusive and aligned with the industry. Our future customer documentation will be updated accordingly.

This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without
the prior written consent of Nokia.

This document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a product purchased or licensed from any company
within Nokia Group of Companies. Use this document as agreed. You agree to notify Nokia of any errors you may find in this document;
however, should you elect to use this document for any purpose(s) for which it is not intended, You understand and warrant that any
determinations You may make or actions You may take will be based upon Your independent judgment and analysis of the content of this
document.

Nokia reserves the right to make changes to this document without notice. At all times, the controlling version is the one available on Nokia’s
site.

No part of this document may be modified.

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY
OR F IT NE SS FO R A PA RT ICU LAR PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T.
IN NO EVEN T WI L L NOK IA B E LI ABLE F OR AN Y DA M A G E S , I N C L U D I N G B U T N O T L I M I T E D TO S P E C I A L ,
D IRE CT, IN D IRECT, I NCI DE NTAL OR C ON SEQ UE N T IA L OR A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D TO LO SS
OF PRO F IT, REVE NU E, B US IN ESS IN T ER RU PT I ON , B U S I NE S S O P P O RT U N I T Y O R D ATA T H AT M AY A R I S E
FRO M T HE USE O F TH IS DO CU M EN T O R T HE IN F OR M AT IO N I N I T, E V E N I N T H E C A S E O F E R R O R S I N O R
OM IS SI O NS FRO M T HI S DOC UM EN T O R IT S CO NT E N T.

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.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be
trademarks of their respective owners.

© 2021 Nokia.

© 2021 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.

Single RAN Management Overview DN09212604 6-0 Table of Contents

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Contents
1 Introduction to Single RAN............................................................................................................................ 5

2 Single RAN system architecture overview................................................................................................... 6

2.1 NetAct support for Single RAN evolution path......................................................................................... 7
2.2 BTS Mediator.......................................................................................................................................... 11
2.2.1 BTS Mediator CM functionalities.................................................................................................... 13
2.2.2 BTS Mediator FM functionalities.................................................................................................... 13
2.2.3 BTS Mediator PM functionalities.................................................................................................... 13
2.2.4 BTS Mediator software management functionalities...................................................................... 13
2.2.5 BTS Mediator security management functionalities....................................................................... 13
2.3 Removing BTS Mediator from NetAct.................................................................................................... 14
2.3.1 Removing BTSMED software packages from Software Manager..................................................14
2.3.2 Removing BTSMED integration......................................................................................................15
2.3.3 Removing BTSMED DNS entry from NetAct................................................................................. 17
2.3.4 Removing BTSMED firewall rule from Network Segregation environment.....................................17
2.4 External SBTS management plane interfaces........................................................................................19

3 Object model.................................................................................................................................................. 21

4 Configuration management.......................................................................................................................... 27
4.1 Pre-validation and validation...................................................................................................................27
4.2 Provisioning and send to network.......................................................................................................... 28
4.3 Upload and events.................................................................................................................................. 28
4.4 BTS Conversion Service.........................................................................................................................29

5 Software management.................................................................................................................................. 30

6 Fault management......................................................................................................................................... 31

7 Performance management............................................................................................................................32
7.1 Single RAN common transport............................................................................................................... 32
7.2 Single RAN GSM.................................................................................................................................... 32
7.3 Single RAN WCDMA.............................................................................................................................. 32
7.4 Single RAN LTE...................................................................................................................................... 33
7.5 Single RAN 5G........................................................................................................................................33
7.6 Administration of Measurements.............................................................................................................34

8 Hardware inventory management................................................................................................................35

9 State management.........................................................................................................................................37

10 License management.................................................................................................................................. 39

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 3

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Table of Contents

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
11 Searching Single RAN data in Object Information Browser................................................................... 40

12 Site element management.......................................................................................................................... 43

13 Troubleshooting........................................................................................................................................... 44

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 4

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Introduction to Single RAN

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
1 Introduction to Single RAN
This document concentrates on high-level differences between the Single RAN (SRAN) network man-
agement and the Single RAT 5G, LTE, WCDMA, and GSM network management operations.

For more information on Single RAN documentation, see the documents in the Single RAN Operating
Documentation set.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 5

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
2 Single RAN system architecture overview
Single RAN provides a common BTS O&M architecture, site solution, and transport solution for the ra-
dio access technologies (RAT).

Single RAN BTS (SBTS) can host multiple RATs simultaneously, or it can be configured for one sin-
gle RAT only. The SBTS maximum concurrent configuration consists of one instance for each RAT
(5G, LTE, WCDMA and GSM). GSM and WCDMA RATs are configured in the controllers as BCF and
WBTS in addition to the site configuration in the SBTS. LTE and 5G RAT (LNBTS and NRBTS) are
configured in the SBTS only.

5G21BCLA is the last 5G Classical release that has a dedicated software package. 5G Classical soft-
ware is now provided only as a part of the SBTS software. Note that 5G Cloud is a separate product
and not part of SRAN.

LTE19 is the last LTE macro release that has a dedicated software package. LTE macro software is
now provided only as a part of the SBTS software. Note that LTE micro (small cells) is a separate
product and not part of SRAN.

AirScale support for GSM and WCDMA is only provided with the SBTS software.

The SRAN network, including SBTS and the related controllers, should be managed by one NetAct
cluster, because of the close relationships between the elements.

SBTS is integrated to NetAct via the NE3SWS mediation. The interface enables the following BTS
management functionalities:

• Configuration management
• Software management
• Fault management
• Performance management
• Security management
• License management
• Hardware inventory management

BSC and RNC controllers are required for GSM and WCDMA radio management, however, the con-
troller role in the SBTS management is limited, as SBTS has the direct management interface. Ex-
isting controller management interfaces (Q3, NWI3) are used for the radio management in BSC and
RNC. Controllers produce own performance and alarm data related to SBTS, and in case of GSM,
BSC also mediates the SBTS generated performance and alarm data to NetAct. NetAct filters SBTS
generated alarms sent by BSC as these alarms are sent to NetAct also directly by SBTS via the NE3S
interface.

The following picture describes the management interfaces of the SRAN and legacy BTSs.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 6

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Net Act
NE3S Q3 NE3S NWI3 NE3S NE3S NWI3

BTSMED * OMS BTSMED iOMS

BSC RNC

SOAM IF BTS O& M

BTS BTS BTS BTS BTS BTS BTS

GSM BTS SBTS WCDMA BTS LTE BTS LTE BTS LTE BTS
(m icro) (old releases)
(LTE19
m acro)
SRAN dom ain
5G dom ain GSM dom ain (LTE, 5G, WCDMA, GSM) WCDMA dom ain LTE dom ain
* BTSMED can be dropped during SRAN19A,
M-plane C/U-plane wit h lim it ed M-plane funct ionalit ies in Abis SRAN19B, or at t he lat est during SRAN20A

Figure 1: Single RAN system architecture

5G, LTE, WCDMA, Transport and performance management data is collected in a single PM data file
from SBTS and transferred to NetAct via the NE3SWS mediation. SRAN GSM performance manage-
ment data is transferred to NetAct via the BSC and Q3 mediation.

5G, LTE, WCDMA, GSM, SBTS transport and fault management data is collected from SBTS and
transferred to NetAct via the NE3SWS mediation directly.

Configuration management data for SBTS transport, site configuration, and LTE and 5G radio network
is managed via the NE3SWS mediation. The GSM radio network configuration data in BSC is man-
aged via the Q3 mediation, and the WCDMA radio network configuration data in RNC via the NWI3
mediation.

Hardware inventory data for SBTS is collected from SBTS via the NE3S/WS mediation.

2.1 NetAct support for Single RAN evolution path

NetAct supports the evolution path of the SBTS O&M architecture:

1. SRAN17A - SRAN19: mediated integration (BTSMED)

2. SRAN19A – SRAN19B: mediated integration (BTSMED) and direct integration
3. SRAN20A onward: direct integration

The following picture illustrates the O&M evolution path from SRAN17A onward. SRAN17A intro-
duced BTS Mediator to mediate BTS data between BTS and network management system (NetAct).
SRAN19A introduced direct integration between BTS and NetAct, and the role of BTS Mediator dimin-
ished to configuration data pre-validation in the new architecture. From SRAN20A onward only the di-
rect integration is supported, however, a limited mediated integration support is provided in SRAN20A

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 7

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
to enable the software upgrade from SRAN19/19A/19B to SRAN20A. PDL Validation Service can be
used for pre-validation instead of BTS Mediator. The last supported BTSMED release is BTSMED19B.

Figure 2: O&M evolution path from SRAN17A onward

NetAct supports SBTS rollout and provides workflows for moving between the architectures within
SRAN and from legacy technologies to SRAN. The following table gives an overview of the function-
alities supported by NetAct and provides references to documents that describe the required prereq-
uisites and the use case in detail. Moving between the BTS products (legacy – SBTS), or between ar-
chitectures (OMS, mediated integration (BTSMED), direct integration) requires planning from the sys-
tem administrator to ensure full management functionalities for the operating personnel before and af-
ter the change.

Source archi- Target archi- Documenta- Additional in-

Use case Workflow
tecture tecture tion formation

Manual inte- N/A SRAN direct Network inte- Integrating Input data in
gration integration gration wizard SBTS to Net- Excel format.
Act

The Integrating
SBTS to Net-
Act document

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 8

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Source archi- Target archi- Documenta- Additional in-
Use case Workflow
tecture tecture tion formation

is available
once respec-
tive NetAct fast
pass Service
Package is in-
stalled.

Plug and Play N/A SRAN direct Unified PnP - Configuring A workflow for
integration Direct integra- Radio Network PnP databuild
tion planning Elements with planning.
Plug and Play
Unified PnP - Autoconnec-
Maintenance tion and auto-
operations and configuration
troubleshooting support.

RACCLI: Input data in

XML/CSV for-
Unified_PnP_
mat.
COAM_Site_
Preparation Validation by
PDL Valida-
Unified_PnP_
tion Service
Reset_Auto-
(NetAct 19
connection_
SP2002 on-
State
ward) or by of-
fline BTSMED.

Licensed fea-
ture.

Recommis- SRAN (mediat- SRAN direct Plan BTS site Rebuilding Several sce-
sioning ed integration, integration rebuilding BTS Sites narios support-
BTSMED) ed.
Rebuild BTS
SRAN (direct site A generic
integration) workflow for
databuild plan-
WCDMA
ning.

A supportive
workflow for
NetAct data
updates during

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 9

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Source archi- Target archi- Documenta- Additional in-
Use case Workflow
tecture tecture tion formation

BTS recom-
missioning.

Input data in
XML format.

Validation by
PDL validation
service (NetAct
19 SP2002 on-
ward) or by of-
fline BTSMED.

Licensed fea-
ture.

Manual inte- N/A SRAN mediat- Network inte- Integrating Input data in
gration ed integration gration wizard SBTS to Net- Excel format.
(BTSMED) Act

The Integrating
SBTS to Net-
Act document
is available
once respec-
tive NetAct fast
pass Service
Package is in-
stalled.

Plug and Play N/A SRAN mediat- Unified PnP - Configuring A workflow for
ed integration Mediated inte- Radio Network PnP databuild
(BTSMED) gration plan- Elements with planning.
ning Plug and Play
Autoconnec-
Unified PnP - tion and auto-
Maintenance configuration
operations and support.
troubleshooting
Input data in
RACCLI: XML/CSV for-
mat.
Unified_PnP_
SOAM_Site_ Validation by
Preparation BTSMED.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 10

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Source archi- Target archi- Documenta- Additional in-
Use case Workflow
tecture tecture tion formation

Unified_PnP_ Licensed fea-

Reset_Auto- ture.
connection_
State

Table 1: Architecture renewal

Note: Combined software upgrade and switchover, for example SBTS19A/SBTS19B (medi-
ated integration) to SBTS20A (direct integration) is not supported as a mass operation. How-
ever, rebuilding workflows support combined switchover and upgrade in the recommission-
ing.

2.2 BTS Mediator

Note: BTS Mediator support is removed in SRAN20A, and SRAN19B is the last supported
release.

BTS Mediator needs to be deployed before integrating the base stations when the release version is
lower than SBTS19A. BTS Mediator is deployed on a virtual machine in NetAct Data Center. One BTS
Mediator per one NetAct needs to be deployed.

The following picture describes the connectivity configuration between NetAct, BTS Mediator, and
BTS.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 11

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Figure 3: Connectivity between NetAct, BTS Mediator, and BTS

In the following tables you can find examples on the DNS and NASDA entries in NetAct:

FQDN of MRBTS IP address

[Link] [Link]

[Link] [Link]

[Link] [Link]

[Link] [Link]

Table 2: DNS entries in NetAct

MRBTS-10

NE3SWS-1 hostname [Link]

EM hostname [Link]

MRBTS-11

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 12

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
NE3SWS-1 hostname [Link]

EM hostname [Link]

Table 3: NASDA entries in NetAct

BTS Mediator internal mapping

BTS Mediator internal mapping (southboundIPAddress, for example [Link]) is used between
the btsId and tcp connection based on the BTS self-identification during a session establishment pro-
cedure.

2.2.1 BTS Mediator CM functionalities

The elementary functionality of BTS Mediator is to provide an information model conversion from the
site configuration file (in RAML format) into a corresponding IMI format (binary representative) in up-
load and configuration change notifications. BTS Mediator obtains the actual configuration from BTS
for the configuration upload to NetAct. BTS Mediator provides the configuration validation for the com-
missioned and pre-commissioned BTSs.

2.2.2 BTS Mediator FM functionalities

BTS Mediator converts alarms to OFaS format and forwards the alarm content to NetAct. BTS Medi-
ator also generates its own alarms. BTS Mediator supervises the link towards the BTS and generates
an alarm when the connection is lost. The BTS supervises the links towards the BTS Mediator and
generates an alarm when a connection loss is detected.

2.2.3 BTS Mediator PM functionalities

BTS Mediator works as a proxy for the PM data. All PM files from BTSs are transferred to NE3S and
forwarded directly to NetAct. BTS Mediator does not store or aggregate PM data.

2.2.4 BTS Mediator software management functionalities

BTS Mediator supports BTS software updates from NetAct Software Manager towards pre-commis-
sioned BTSs. BTS Mediator supports an autonomous BTS SW update request in the BTS pre-com-
missioned state.

BTS Mediator requests NetAct for a software update, for example for a plan validation.

2.2.5 BTS Mediator security management functionalities

BTS Mediator acts as a mediator for certification and user management operations between NetAct
and SBTSs. NE3S certificate and user management commands are translated to multiple messages in
SBTSs.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 13

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
2.3 Removing BTS Mediator from NetAct
Clean up BTS Mediator (BTSMED) from NetAct if BTSMED is not used anymore.

When cleaning up BTSMED from NetAct, there are the following phases:

1. Removal of BTSMED software packages from Software Manager.

2. Removal of BTSMED integration from NetAct.
3. Removal of BTSMED DNS entry from NetAct.
4. Removal of BTSMED firewall rule from Network Segregation environment.

Note:

• In addition to the cleanup items above, some BTSMED related cleanup activities will be
handled in SR002818 BTSMED support SW removal.
• Perform these instructions before BTSMED VM removal.

2.3.1 Removing BTSMED software packages from Software Manager

1. Log in to the NetAct Start Page as the integration user.

a) In the address field of your internet browser, type the following URL address:

[Link]

where <system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer
for WebSphere. For more information, see Launching the NetAct Start Page.
b) Type the Username and Password of the integration user, and click Log In.

Note: If the terms and conditions appear, select the I have read and agree to
the above terms and conditions check box, and then click Log In. For more
information, see Modifying terms and conditions page.

c) Click Accept or Continue.

2. Remove BTSMED software packages with Software Manager.

a) On the NetAct Start Page, open Configuration → Software Manager.
b) Delete BTSMED software packages from Software Archive, see Deleting software packages
from Software Archive in Software Manager Help.
c) Delete BTSMED software packages from remote repository, see Deleting software packages
from remote repository in Software Manager Help.

Note:

• Only BTSMED software packages under BTSMED MO type can be removed.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 14

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
• Check that a BTSMED software package is no longer used by any other
BTSMED before removing the software package.

2.3.2 Removing BTSMED integration

1. Delete configuration management data.

a) On the NetAct Start Page, click Configuration → CM Operations Manager.
b) To open the Workflow Engine dialog, click Tools → Workflow Engine....
c) In the MO(s) field of the Workflow Engine dialog, add the BTSMED managed object to be
cleaned up.

• On the NetAct Start Page, click Configuration → CM Editor.

• In the CM Editor tree view, expand Actual Configuration.
• Drag-and-drop or copy and paste the BTSMED managed object of the integrated network
element to the MO(s) field of the Workflow Engine dialog in CM Operations Manager.

Note: You must have both CM Editor and the Workflow Engine dialog open to drag-
and-drop or copy and paste the managed object.

d) From the Operation List drop-down list, select NE data deletion from Configurator.

Expected outcome

The selected operation shows in the Operation column, and the corresponding attributes of
the operation are shown on the right.

e) (Optional) In the Name field, enter a name for the operation.

f) (Optional) In the Description field, enter a description for the operation.
g) On the Scope area, select the BTSMED managed object DN for which the deletion operation
needs to be performed if it is not selected.
h) Click Start.
i) When prompted, click Yes.

Expected outcome

The NE data deletion from Configurator: Finished dialog appears displaying the feedback.

2. On the NetAct Start Page, click Monitoring → Monitor.

3. In NetAct Monitor, click Tools → Managed Objects → Object Explorer.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 15

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Expected outcome

The Objects pane opens.

4. Unregister BTS Mediator.

a) Right-click the BTSMED object and select Properties.
b) In the Properties pane, find the Distinguished Name attribute.
c) Log in as the omc user to one of the VMs on which the common_mediations service is running.
d) Enter the following command: /opt/oss/NSN-ne3sws_core/install/bin/
[Link] '<Distinguished Name>'

Expected outcome

BTS Mediator is unregistered successfully.

Note: If the un-registration of BTS Mediator fails, troubleshoot the problem by following
the instructions in Un-registration fails in Troubleshooting Southbound Mediations.

5. Delete the NE3S interface object.

a) Right-click the BTSMED-<instance ID>/NE3SWS-1 interface object and select Delete
Object.
b) When a confirmation dialog box is shown, click Delete.

6. Delete the fault management data.

a) Right-click the BTSMED object and select Delete All Alarms from Database → Delete
Alarms For Object And Its Subnetwork.
b) When a confirmation dialog is shown, click Yes.

Expected outcome

On the Operations History area, it is shown that the operation is completed successfully.

7. Delete the managed object.

a) Right-click the BTSMED object and select Delete Object.
b) When a confirmation dialog is shown, click Delete.

8. Remove the IP address of the BTS Mediator from Brute force attack white-list. Check if the IP
address of the BTS Mediator is added to the allowed list by executing the current brute force
protection status command. If the IP address of the BTS Mediator is included in the allowed
list, remove the IP address from the white-list. If not, skip this step. For more information, see
Configuring brute force protection for web services in Administering NetAct System Security.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 16

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
2.3.3 Removing BTSMED DNS entry from NetAct
Follow the instructions in Removing hosts from the master zone files in Administering DNS in Net-
Act to remove the DNS entries whose hostname points to the BTSMED northbound IP address and
BTSMED northbound virtual IP address in NetAct VM where the DNS-Master service is running.

Note:

• Contact the BTSMED administrator to get the BTSMED northbound IP address and
BTSMED northbound virtual IP address. BTSMED northbound virtual IP address is
involved only when SR001756/LTE3875: BTS Mediator Resiliency (Active-Standby) is
enabled.
• For the SBTS hostnames which also point to the BTSMED northbound IP address
or BTSMED northbound virtual IP address, check that they are not used by the user
anymore before the removal.
• If an external DNS server is used, the corresponding BTSMED DNS entry needs to be
removed also.

2.3.4 Removing BTSMED firewall rule from Network Segregation environment

Network Segregation is a licensed feature, which is not enabled by default. Skip this section if the Net-
work Segregation function is disabled.

If the Network Segregation feature is enabled, follow the instructions to disable BTSMED firewall rules
for Network Segregation environment. In Network Segregation environment, to check whether the Net-
Act firewall rules are enabled for BTSMED, see Viewing firewall rules and customization information in
Administering NetGuard Virtual Firewall and Windows Firewall. If NetAct firewall rules are not enabled
for BTSMED, skip this section. Network Segregation feature is supported only for NetAct and NetAct
Cloud (OpenStack) and is not supported for NetAct Cloud (VMware).

The default firewall rules for connecting BTS Mediator to NetAct are listed in the following tables:

Note:

• If the Network Segregation function is enabled, IP addresses of all the NetAct nodes
in the following table must be the NetGuard routable public IP addresses. For more
information on how to query the NetGuard routable public IP addresses in Network
Segregation environment, see Listing NetGuard routable endpoints for network
segregated environment in Administering Network Segregation in NetAct.
• To prevent security risks, Nokia recommends that you choose the secure protocol
HTTPS instead of HTTP.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 17

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Destination 1 2 Service
Source Source port Destination AL TL Description
port object

BTSMED ephemeral LB JBI virtu- 30505 HTTP TCP tcp-30505 NE3S/WS SMI for SBTS FM/PM no-
al IP tification. Optional: This firewall rule
is not required if the respective se-
cure protocol is used (port 30510).

BTSMED ephemeral LB JBI virtu- 30508 HTTP TCP tcp-30508 Software Manager outgoing request.
al IP Optional: This firewall rule is not re-
quired if the respective secure proto-
col is used.

BTSMED ephemeral LB JBI virtu- 30509 HTTPS TCP tcp-30509 Software Manager outgoing request.
al IP Should be enabled when secure pro-
tocol is used.

BTSMED ephemeral LB JBI virtu- 30510 HTTPS TCP tcp-30510 NE3S/WS SMI for BTSMED FM/PM
al IP notification.

BTSMED ephemeral LB WAS vir- 80 HTTP TCP http NE3S/WS SMI for BTSMED CM noti-
tual IP fications. A port used by BTSMED to
transfer BTSMED software from Net-
Act Software Manager to BTSMED,
when IPSec not in use. Optional:
This firewall rule is not required if the
respective secure protocol is used.

BTSMED ephemeral LB WAS vir- 448 HTTPS TCP tcp-448 NE3S/WS SMI for BTSMED CM noti-
tual IP fications.

BTSMED ephemeral LB WAS vir- 10510 HTTP TCP tcp-10510 NE3S/WS SMI for BTSMED CM noti-
tual IP fications. Optional: This firewall rule
is not required if the respective se-
cure protocol is used This firewall
rule is required if default port 80 is
disabled.

SBI-Com- ephemeral BTSMED 8080 HTTP/ TCP NE3S/WS BTSMED integration with non-TLS
monMedia- SOAP mode Optional: This firewall rule is
tion not required if the respective secure
protocol is used. This port is also
used in SOAM BTS integration.

SBI-Com- ephemeral BTSMED 8443 HTTPS/ TCP NE3S/WS BTSMED integration with TLS mode.
monMedia- SOAP This port is also used in SOAM BTS
tion integration.

cmwas ephemeral BTSMED 8080 HTTP/ TCP tcp-8080 NE3S/WS communication from Con-
SOAP figurator to BTSMED/SOAMBTS.
Optional: This firewall rule is not re-
quired if the respective secure proto-
col is used.

cmwas ephemeral BTSMED 8443 HTTPS/ TCP tcp-8443 NE3S/WS communication from Con-
SOAP figurator to BTSMED/SOAMBTS.

fmwas ephemeral BTSMED 22 SSH TCP ssh For SCLI connections to BTSMED

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 18

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Table 4: Firewall rules of BTS Mediator

Note:
1
• AL : Application Layer
2
• TL : Transport Layer
• If the port is ephemeral, select a port from the port pool of the IP stack.

For detailed descriptions of all the sources and destinations, see the following table:

Node Description

NetAct nodes

LB WAS virtual IP Virtual IP address of the WebSphere Application

Server load balancer

LB JBI virtual IP Virtual IP address of the JBI load balancer

DB IP address of the VM where the db service is run-

ning

SBI-CommonMediation IP addresses of the VMs where the common_me-

diations service is running

cmwas IP addresses of the VMs where the cmwas ser-

vices are running

fmwas IP addresses of the VMs where the fmwas ser-

vices are running

BTS Mediator nodes

BTSMED BTS Mediator for Single O&M BTS

Table 5: Node descriptions

For more information on how to get the NetAct IP addresses for a virtual machine (VM) on which a
certain service is running, see Locating the right virtual machine for a service in Administering NetAct
Virtual Infrastructure.

2.4 External SBTS management plane interfaces

NE3S interface provides the M-plane interface for centralized configuration, software, fault, perfor-
mance, and license management from NetAct.

CMP server is used to manage SBTS certificates with the operator Certificate Authority servers. SBTS
has the same functionality as in WCDMA and LTE.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 19

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Single RAN system architecture overview

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
LDAP is used for SBTS remote user and operation authentication and authorization. SBTS has the
same authentication and authorization functionality as the WCDMA and LTE base stations. The re-
mote user authentication needs to be available in SBTS to guarantee the NE3S operation authentica-
tion and authorization and the local element manager access.

SBTS implements an NTP client to retrieve the time information from the NTP server in NetAct. In the
configurations with more than one system module, the primary system module synchronizes the time
with the other system modules.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 20

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Object model

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
3 Object model
Single RAN base station is represented by MRBTS root object directly under PLMN in the network ob-
ject model hierarchy. This is similar to LTE and 5G MRBTS, whereas Single RAT WCDMA and GSM
have the base station site configuration modeled under RNC/WBTS and BSC/BCF respectively.

MRBTS object hierarchies contain the common site and transport configuration. SBTS can contain
multiple technologies. LTE and 5G radio network configurations are modeled directly under the SBTS
containment tree.

The association between the radio network configuration in RNC/WBTS and/or in BSC/BCF is based
on the SBTS ID that the commissioned SBTS informs towards the controller. Using the SBTS ID, Net-
Act builds a relationship between SRAN base station and the respective radio network configuration in
the controller. NetAct also updates RNC/WBTS and BSC/BCF topology information necessary for FM
and PM adaptations (version, adaptation, relationship) based on a special warning alarm provided by
the SBTS.

The radio-specific object model in RNC/WBTS and BSC/BCF is the same in Single RAT and Single
RAN base stations. SBTS has a similar LNBTS object model, but with a dedicated release version.
Single RAT 5G and SBTS use the same NRBTS object model.

The following high-level picture illustrates the relationships between SRAN base station and
the controllers. Solid line represents the parent-child relationship and dotted line represents the
relationship by the SBTSId attribute.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 21

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Object model

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
PLMN

MRBTS-200

NRBTS-200

LNBTS-200

WBTS-200

BCF-200

RNC-1

WBTS-200 WBTS:SBTSId= 200

MRBTS-200
BSC-1

BCF-200 BCF:SBTSId= 200

MRBTS-200
Figure 4: SRAN high-level object model

SBTS object model

The MRBTS containment tree includes objects modeling:

• Common MRBTS object.

• common RAT-independent resources: configured BTS equipment (EQM), runtime BTS equipment
(EQM_R), management layer (MNL), and transport (TNL).
• RAT-specific, non-radio network layer resources like local cell configurations (WNBTS, GNBTS).
• LTE radio network layer resources (LNBTS).
• 5G radio network layer resources (NRBTS).

Note that the picture does not include all object classes.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 22

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Object model

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
PLMN

MRBTS-200

GNBTS-1

LNBTS-200

WNBTS-1

NRBTS-200
EQM-1

EQM_R-1

HW-1

MNL-1
TNLSV-1
Figure 5: SRAN object model

Here is more detailed information on the objects in the MRBTS object model figure:

Managed object Description

MRBTS-200 Identification and autoconnection related parame-

ters.

Related adaptations:

• CM adaptation: [Link]
• FM adaptation: [Link]
• PM adaptation: nokmrn

GNBTS-1 GSM-specific site configuration, for example

• Local sectors
• Management plane towards BSC

Related adaptations:

• CM adaptation: [Link]
• FM adaptation: N/A
• PM adaptation: N/A

LNBTS-200 LTE radio configuration

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 23

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Object model

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Managed object Description

Related adaptations:

• CM adaptation: NOKLTE
• FM adaptation: NOKLTE
• PM adaptation: NOKLTE

NRBTS-200 5G Radio configuration

Related adaptations:

• CM: [Link]
• FM: [Link]
• PM: [Link]

WNBTS-1 WCDMA-specific site configuration, for example

• Local cells and local cell groups

• User plane configuration
• Control plane configuration
• Performance management

Related adaptations:

• CM adaptation: [Link]
• FM adaptation: N/A
• PM adaptation: N/A

EQM-1 Configured equipment and topology. Config-

urable by operator. Includes for example

• Radio and system modules

• Antenna line devices
• Cable topology

Related adaptations:

• CM adaptation: [Link]
• FM adaptation: N/A
• PM adaptation: N/A

EQM_R-1 Runtime/detected equipment and topology. Not

configurable by operator. Includes for example

• Radio and system modules

• Antenna line devices
• Cable topology

Related adaptations:

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 24

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Object model

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Managed object Description

• CM adaptation: [Link]
• FM adaptation: [Link]
• PM adaptation: N/A

INVUNIT_R (child object of EQM_R-1) Hardware inventory data

Related adaptations: [Link]

Note: From SRAN19 onward, IN-

VUNIT_R objects do not exist.

HW-1 3GPP hardware inventory

Related adaptations:

• CM adaptation: [Link]
• CM adaptation: [Link]

MNL-1 Management layer. Includes for example

• Fault management administration

• Performance monitoring administration
• Security administration
• Troubleshooting administration
• Capacity administration
• BTS level feature administration
• Synchronization administration
• Tests execution
• Commands execution for operations like re-
sets

Related adaptations:

• CM adaptation: [Link]
• FM adaptation: [Link]
• PM adaptation: nokmrn

TNLSCV-1 Transport network layer, for example

• Ethernet
• PPP
• IP interfaces
• IP routing
• Transport security
• Quality of service

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 25

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Object model

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Managed object Description

• Transport network operation and mainte-

nance
• Protection

Related adaptations:

• CM adaptation: [Link]
• FM adaptation: [Link]
• PM adaptation: nokmrn

Table 6: MRBTS object model information

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 26

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Configuration management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
4 Configuration management
SBTS supports the basic configuration management operations (provisioning including download, val-
idate, and activate; upload; configuration change notifications), following the same basic principles as
other Nokia base stations.

Configuration management operations operate on the delta plan meaning that only the changed para-
meter content is provisioned to the BTS. This is optimal for the network service because the service
impact depends on the parameter content in the plan: BTS restart, RAT restart, object locking, or on-
line. For more information on the service impact in SBTS, see State management.

Site configuration file (SCF) is used for the SBTS commissioning. Site configuration file usually refers
to the entire content of the BTS configuration. It can also be used to refer to the BTS interpretation of
the NetAct XML/RAML plans. For more information on the NetAct support for the site configuration file,
see section Site configuration file in Configuration in Configuration Management Overview and Opera-
tions.

Configuration management operations from NetAct toward each SBTS are handled as independent
actions, and there are no dependencies between BTSs. The basic principle is that SBTS can perform
only one configuration management operation at a time. However, some level of concurrency is sup-
ported for upload and download, which can be run parallel with other types of configuration manage-
ment operations under certain conditions.

4.1 Pre-validation and validation

SBTS supports both pre-validation and validation. Pre-validation refers to checking the complete (full)
configuration of a BTS before commissioning or recommissioning. Pre-validation is an offline activity
and is performed by a service dedicated for this purpose. Validation checks instead that a delta plan
together with the BTS actual configuration forms a valid configuration. Validation is online activity and
performed by the BTS.

For more information on pre-validation, see Pre-validating plans in Configuration Management

Overview and Operations.

For more information on validation, see Validating plans in Configuration Management Overview and
Operations.

The BTS plan pre-validation and validation can be divided into the following layers:

Responsible compo-
Validation type Example Note
nent

Simple validation rules Parameter value check Metadata checks in

NetAct
Parameter range check
Pre-validation

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 27

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Configuration management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Responsible compo-
Validation type Example Note
nent

Validation

Logical validation Parameter relationships Pre-validation

Validation

Hardware validation CABLINK matches with Validation Hardware validation en-

the connector sures that the planned
configuration match-
es with the actual hard-
ware

Table 7: Validation types

4.2 Provisioning and send to network

Both plan provisioning and send to network are supported.

NetAct provides two alternatives for mass provisioning of the SBTS plans (including download, vali-
date, and activate):

• Best effort - only the successfully validated SBTS configurations are activated.
• Best consistency ('all or nothing') - plan is activated only if all the accessible SBTSs are validated
successfully.

For choosing between these alternatives, you can use option Activate only after successful pre-ac-
tivation of all BTSs in the Provision dialog of CM Operations Manager.

4.3 Upload and events

Configuration upload contains the entire SBTS configuration including site, transport, and LTE and 5G
RNW configuration.

In the Configurator user interface, the upload scope can be MRBTS, RNC, BSC, or OMS. When the
scope is RNC, BSC, or OMS, Configurator creates separate upload requests for SRAT base stations
and SBTSs.

SBTS sends events on configuration changes.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 28

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Configuration management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
4.4 BTS Conversion Service
BTS Conversion Service is a service that can be integrated to NetAct and used for migrating BTS con-
figuration data to the target SBTS release. The benefit is that the existing actual configuration data can
be used in the SBTS plan creation.

BTS Conversion Service is a licensed feature and part of the BTS site rebuilding use case.

For more information, see Overview of integrating BTS Conversion Service in Integrating BTS Conver-
sion Service to NetAct.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 29

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Software management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
5 Software management
The basic software management operations are supported for SBTS. Software management opera-
tions are executed directly on the SBTS network elements, not via OMS, RNC, or BSC. However, it is
possible to activate the SBTS software package on top of WCDMA and LTE software via OMS/RNC in
the migration use case.

SBTS software package includes the SBTS O&M software, common transport software, and the soft-
ware of all the radio access technologies: LTE, 5G, WCDMA, and GSM. New SBTS software package
can be activated with NetAct Software Manager and Web Element Manager on top of SBTS software
and with Rescue Console on top of factory delivery software (FDSW). BTS Site Manager can be used
to activate SBTS software on top of LTE (up to LTE18A) and WCDMA software. For limitations, refer to
SRAN upgrade rules in SRAN operating documentation.

For more information on software management, see About Software Manager in Software Manager
Help.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 30

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Fault management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
6 Fault management
Alarms about failures in the SBTS services are reported depending on the impact and entity detecting
the fault. The alarms may be reported for common SBTS objects and/or for the radio configuration ob-
jects of the technology.

Common alarms, for example transmission and hardware fault related alarms are targeted to the com-
mon objects of the SBTS site configuration. A common alarm without RAT impact can be, for example
an EAC (external alarm connection) alarm, or an alarm about a configuration error of resources with-
out RAT allocations. If the fault impacts the RATs in SBTS, the alarm is reported to the relevant RNW
objects. If the fault impacts more than one RAT, the alarm is reported to all relevant RATs.

Since the common faults are reported for more than one object, NetAct provides an alarm correlation
function for filtering and modifying alarms with user-defined correlation rules. For example, you can
view only your important alarms, or several RAT alarms can be merged into one. For more information,
see Alarm correlation in Fault Management Overview and Operations.

If a fault affects the radio configuration, SBTS reports an alarm for the impacted radio, for exam-
ple RNC-1010/WBTS-100/WCEL-1, BSC-1234/BCF-100/BTS-101, MRBTS-123/LNBTS-100,
MRBTS-123/NRBTS-101. For an alarm affecting more than one RAT, SBTS includes a shared tag in
the alarm information. This can be used in the alarm correlation in NetAct later.

RNC and BSC generate their own alarms for the radio service objects. The alarm numbers in the
SBTS radio service and controller radio service alarms are different. Separate alarm uploads for each
element (SBTS, RNC, BSC) are needed to get all the alarms related to a single RAN base station.

For more information on fault management, see About SingleRAN Site View in SingleRAN Site View
Help for NetAct Monitor.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 31

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Performance management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
7 Performance management
Besides the common transport measurements, SBTS can generate BTS measurements for 5G, LTE,
WCDMA and GSM technologies. The legacy GSM, WCDMA, LTE and 5G technologies in Perfor-
mance Manager+ are reused for Single RAN GSM, Single RAN WCDMA, Single RAN LTE reporting
and Single RAN 5G reporting.

7.1 Single RAN common transport

The table below shows the Technology and Hierarchy in Performance Manager+ utilized to create Sin-
gle RAN common transport reports and Thresholder and Profiler plans.

Technology Hierarchy

SBTS-Nokia Multi Radio Transceiver Station PLMN-MRBTS

Table 8: Technology and Hierarchy in Performance Manager+

7.2 Single RAN GSM

The table below shows the technology and hierarchy in Performance Manager+ utilized to create Sin-
gle RAN GSM reports and Thresholder and Profiler plans.

Technology Hierarchy

BSC-NSN Base Station Controller for GSM PLMN-BSC

Table 9: GSM Technology and Hierarchy in Performance Manager+

Note: SBTS supports a part of GSM KPIs and measurements.

7.3 Single RAN WCDMA

The table below shows the technology and hierarchy in Performance Manager+ utilized to create Sin-
gle RAN WCDMA reports and Thresholder and Profiler plans.

Technology Hierarchy

RNC-NSN Radio Network Controller PLMN-RNC-WBTS

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 32

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Performance management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Table 10: WCDMA Technology and Hierarchy in Performance Manager+

Note: SBTS supports a part of WCDMA KPIs and measurements.

7.4 Single RAN LTE

The table below shows the technology, hierarchy, and working sets in Performance Manager+ utilized
to create Single RAN LTE reports and Thresholder and Profiler plans.

Technology Hierarchy Working set

LNBTS-NSN LTE Base Trans- PLMN-MRBTS PLMN/WS_MRBTS

ceiver Station
PLMN/WS_LNBTS

PLMN/WS_LNCEL

Table 11: LTE technology, hierarchy, and working sets in Performance Manager+

Note: SBTS supports a part of LTE KPIs and measurements.

7.5 Single RAN 5G

The table below shows the technology and hierarchy in Performance Manager utilized to create Single
RAN 5G reports and Thresholder and Profiler plans.

Technology Hierarchy Working set

NRBTS-Nokia AirScale BTS 5G PLMN-MRBTS PLMN/WS_MRBTS

PLMN/WS_NRBTS

PLMN/WS_NRCEL

PLMN/WS_NRDU

Table 12: 5G technology, hierarchy in Performance Manager+

Note: SBTS supports a part of 5G KPIs and measurements.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 33

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Performance management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
7.6 Administration of Measurements
Administration of Measurements application uses two adaptations to administrate the SRAN measure-
ments of different radio access technologies:

• [Link] adaptation is used for administering SBTS common transport, WCDMA, LTE
and 5G measurements.
• NOKBSC adaptation is used for administering SBTS GSM measurements.

In Administration of Measurements you can select

• [Link] (for example Nokia MRBTS([Link])-SBTS17A) to display and

administrate all the WCDMA, LTE, and common transport measurements that are supported by
SRAN.
• NOKBSC (for example Nokia BSC(NOKBSC)-BSC17) to display and administrate all the GSM
measurements.

Note: The [Link] adaptation (for example Nokia

MRBTS([Link])-SBTS21B) is used for administering the SBTS common
transport, WCDMA, LTE, and 5G measurements.

For more information on the GSM measurements supported by SRAN, see Searching Single RAN da-
ta in Object Information Browser .

For more information on the corresponding GSM release when selecting the NOKBSC adaptation, see:

• Configuring GSM, WCDMA and LTE radio access technologies in Integrating SBTS to NetAct
• Configuring GSM and WCDMA radio access technologies in Integrating SBTS to NetAct
• Configuring GSM and WCDMA radio access technologies in Integrating SBTS to NetAct

The Integrating SBTS to NetAct document is available once respective NetAct fast pass Service Pack-
age is installed.

Note: Administration of Measurements for GSM is performed on the BSC level, that is to
say, you administrate all the BCFs under a BSC, and not only the BCF that is related to the
SBTS.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 34

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Hardware inventory management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
8 Hardware inventory management
SBTS implements the 3GPP-compliant hardware inventory model. Element-level parameters follow
the 3GPP TS 32.622 definition for managedElement. Unit-level parameters apply the 3GPP TS
32.692 ALT1 version of the inventoryUnit parameters. The following table states the Nokia
compliance with the inventoryUnit parameters:

Attribute name Support qualifier Nokia compliance

id Mandatory Nokia format

inventoryUnitType Mandatory Compliant

vendorUnitFamilyType Conditionally mandatory (de- Compliant

pends on the unit in question)

vendorUnitTypeNumber Conditionally mandatory (de- Compliant

pends on the unit in question)

versionNumber Optional Compliant when available

vendorName Mandatory Compliant

serialNumber Conditionally mandatory (de- Compliant when available

pends on the unit in question)

dateOfManufacture Optional Compliant when available

dateOfLastService Optional Compliant when available

unitPosition Optional Compliant

manufacturerData Optional Compliant when available

relatedFunction Optional Not supported

Table 13: Supported hardware inventory parameters

HW object in the hardware inventory model represents the base station. Hardware inventory data in-
cludes both auto-detected units and passive units, which are manually defined in the site configuration
file.

Hardware inventory can be viewed in the NetAct Configurator user interface, and exported to up-
per-layer management systems via northbound interfaces.

The following table lists the CM adaptations for SRAN hardware inventory data:

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 35

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Hardware inventory management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
CM adaptation abbreviated
Model Description
name

SRAN19 onward 3GPP compli- [Link] The hardware inventory mod-

ant hardware inventory model el generated in the SBTS and
provided by a separate upload
operation to NetAct. INVUNIT
object represents the hardware
units.

This model replaces [Link].

[Link] and [Link].
hwinv.

3GPP compliant hardware in- [Link] The hardware inventory mod-

ventory model, SRAN18A and el converted from the relevant
earlier hardware objects in the EQM_R
and the INVUNIT_R in the site
configuration file.

Inventory unit, SRAN18A and [Link] The INVUNIT_R object con-

earlier tains hardware inventory para-
meters used as a source for the
3GPP model conversion. The
INVUNIT_R object appears as a
child object for the objects rep-
resenting hardware units (for ex-
ample SMOD, RMOD).

Table 14: CM adaptations for SRAN hardware inventory data

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 36

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 State management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
9 State management
State management refers to the network element's ability to report its current status (operational, ad-
ministrative, local) and the operations to control the status (lock/unlock, shutdown).

SBTS inherits the RAT-specific states from 5G, LTE, WCDMA, and GSM, so the same principles and
functionalities are used.

RAT and cell operational states can be displayed with the following tools:

• LNBTS and LNCEL operational states are available in NetAct Monitor, NetAct Configurator and
Web Element Manager.
• NRBTS and NRCELL operational states are available in NetAct Monitor, NetAct Configurator and
Web Element Manager.
• WBTS operational state is SBTS internal information. WCEL operational state is available in RNC
MMLs and NetAct Configurator.
• BCF, BTS, TRX, and timeslot operational states are available only in BSC MMLs.

RAT and cell administrative states can be displayed and managed with the following tools:

• LNCEL administrative state is managed in NetAct Monitor, NetAct Configurator and Web Element
Manager.
• NRCELL administrative state is managed in NetAct Monitor, NetAct Configurator and Web Ele-
ment Manager.
• WCEL administrative state is managed in NetAct Monitor, NetAct Configurator, RNC MML, and
OMS Element Manager.
• BCF, BTS, and TRX administrative state is managed in NetAct Monitor, NetAct Configurator, and
BSC MML.

If a parameter modification requires object locking, an automatic lock/unlock is triggered if the respec-
tive technology supports it.

SBTS supports the restart of the whole base station and the restart of one technology only.

• SBTS restart can be triggered with Web Element Manager and NetAct Configurator.
• LTE RAT (LNBTS) and LNCEL restart can be triggered from NetAct Monitor, NetAct Configurator,
and Web Element Manager.
• WCDMA RAT (WBTS) restart can be triggered from NetAct Monitor, RNC MML, OMS Element
Manager, and Web Element Manager.
• GSM RAT (BCF) restart can be triggered from NetAct Configurator, BSC MMLs, and Web Element
Manager.
• 5G RAT (NRBTS) and NRCELL restart can be triggered from NetAct Monitor, NetAct Configurator,
and Web Element Manager.

The modification of the BTS restart needed parameters in SBTS triggers an automatic restart in
the base station. Depending on the SBTS parameter, the restart can be limited to the impacted RAT
(LTE, 5G, WCDMA, GSM), or the whole base station is restarted (common site configuration, transport

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 37

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 State management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
configuration). If the reset is triggered by BSC, for example via the BCF parameter change or the reset
command, only GSM RAT is restarted.

Alarm status and Unknown status are determined by NetAct internally based on alarm information.

• SBTS, LNBTS, and LNCEL, NRBTS, NRCELL Unknown status is based on the NetAct connectivi-
ty to SBTS.
• WBTS and WCEL Unknown status is based on the NetAct connectivity to RNC.
• BCF and BTS Unknown status is based on the NetAct connectivity to BSC.

Blocking state is only managed via Web Element Manager. It is possible to block and unblock SBTS,
RAT (NRBTS, LNBTS, WNBTS, GNBTS), and a cell.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 38

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 License management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
10 License management
The SBTS license management uses several approaches because of cross-technology and cross-ele-
ment nature of the solution.

The existing license management concepts for 5G, LTE, RNC, and BSC are still valid for controlling
the feature and capacity usage in SBTS. RNC and BSC licenses need to be activated with License
Manager. BSC also controls GSM capacity and base station optional features as before. LTE and 5G
uses measurement-based monitoring by Software Asset Monitoring.

The new SBTS license mechanism protects cross-technology SBTSs and premium and hardware acti-
vation features (for example a feature configured for more cells than allowed). The file-based WCDMA
BTS license management is replaced with the SBTS license concept.

In the new license mechanism, the license files are not downloaded to the base station, but stored in
NetAct Centralized License Server. When new optional functionality or licensed capacity is configured
in SBTS, NetAct Software Entitlement Manager (SWEM) reports the feature usage and reserves the
capacity from the license pool in CLS.

For more information on monitoring-based license management and Single RAN licenses, see Moni-
toring based license management in Software Asset Monitoring.

From NetAct 22 release onwards, NetAct Radio SRAN Standard SW license (feature code: 17753) is
discontinued. SBTS integration requires license based on SBTS RAT configuration.

The following table lists the required NetAct Radio Standard SW license for each RAT configuration:

RAT Technology License

5G • Feature code: 49261

• Feature name: NetAct Radio 5G Standard SW

LTE • Feature code: 3599

• Feature name: NetAct Radio LTE FD TD FZ stan-
dard SW

WCDMA • Feature code: 3598

• Feature name: NetAct Radio WCDMA Standard
SW

GSM • Feature code: 3597

• Feature name: NetAct Radio GSM Standard SW

Table 15: NetAct Radio Standard SW license for RAT Technology

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 39

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Searching Single RAN data in Object

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Information Browser

11 Searching Single RAN data in Object Information

Browser
Single RAN is a multi-RAT solution. There is Single RAN data for performance management, fault
management, configuration management, and hardware inventory in the Single RAN specific adapta-
tions. In addition, RAT-specific data (5G, LTE, WCDMA and GSM) of the existing SRAT solutions are
reused in Single RAN. Note, however, there are new adaptations for BCF and WBTS fault manage-
ment data.

To find RAT-specific performance management objects and measurements you can also use the Note
field for advanced search (5G objects, measurements counters and GSM counters are not supported),
WCDMA and LTE counters are supported. By entering a Single RAN release in the Note field, for ex-
ample SBTS17A, you get the RAT-specific data of the selected adaptation which is also relevant for
SRAN17A. You can use the same method when searching Object Information Browser Excels in Sup-
port portal in [Link] Accessing the documentation and software in the portal re-
quires authentication.

The table below shows how to search for Single RAN related data in Object Information Browser.

SBTS

• transport SRAN WCD-

SRAN 5G SRAN LTE SRAN GSM
• site configuration MA
• hardware

Objects PM: Nokia Single RAN base PM and CM: • PM: PM: Nokia
station MRBTS (com. Nokia LTE Nokia Base Sta-
Nokia AirS-
[Link]) Base Station Radio tion Controller
cale BTS 5G
(NOKLTE). Network (NOKBSC)
([Link]. • Nokia LTE/SRAN
Note: the re- Con-
nrbts). BTS management CM:
lease should troller
layer ([Link].
Note: the re- start with Nokia Base
[Link]) (NOKRNC)
lease should "SBTS". Station Con-
• Nokia LTE/SRAN • Nokia
start with troller (NOK-
BTS equipment mcRNC
"SBTS" BSC)
([Link]. (com.
CM: nsn. AirScale BSC
eqm)
mcrnc) ([Link].
Nokia New • Nokia LTE/SRAN
asbsc)
Radio Base BTS runtime equip- CM:
Station (com. ment ([Link]. CM adapta-
Nokia Ra-
[Link]. [Link]) tion for Nokia
dio Network
nrbts) • Nokia SRAN BTS SRAN BTS
Controller
transport layer (com. GSM config-
(NOKRNC)
[Link]) uration (com.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 40

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Searching Single RAN data in Object

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Information Browser

SBTS

• transport SRAN WCD-

SRAN 5G SRAN LTE SRAN GSM
• site configuration MA
• hardware

Nokia [Link].
ncRNC gsm)
([Link].
mcrnc)

AirScale
RNC (com.
[Link])

CM adapta-
tion for Nokia

SRAN BTS
WCDMA
configuration
([Link].
[Link])

Measure- Nokia AirS- Nokia Single RAN base Nokia LTE Nokia Ra- Nokia Base
ments and cale BTS 5G station MRBTS (nokmrn) Base Sta- dio Network Station Con-
counters (nokgnb) tion (noklte). Controller troller (nokb-
Note: the re- (nokrww) sc)
Note: the re-
lease should
lease should
start with
start with
"SBTS".
"SBTS"

Alarms Nokia AirS- Nokia Single RAN base Nokia LTE Nokia Sin- Nokia Single
cale BTS 5G station MRBTS (com. Base Station gle RAN RAN Base
([Link]. [Link]) (NOKLTE). Base Sta- Station (NOK-
nrbts) Note: the re- tion (NOK- BCF). Note:
lease should WBTS) Note: the release
Note: the re-
start with the release should start
lease should
"SBTS". should start with "SBTS".
start with
with "SBTS".
"SBTS"

Hardware • CM adaptation for

inventory Nokia common
equipment inventory
([Link])

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 41

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Searching Single RAN data in Object

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
Information Browser

SBTS

• transport SRAN WCD-

SRAN 5G SRAN LTE SRAN GSM
• site configuration MA
• hardware

• CM adaptation for
Nokia Single RAN
BTS inventory unit
data ([Link].
[Link])
• CM adaptation for
Nokia Single RAN
base station 3GPP
hardware invento-
ry ([Link].
hw)

Table 16: SRAN data in Object Information Browser

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 42

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Site element management

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
12 Site element management
Web Element Manager provides local and remote SBTS management functions. The management
functions include, for example SBTS software packages and site configuration file activation, trou-
bleshooting, alarm, and hardware views. Web Element Manager allows several users to access the
same BTS simultaneously.

Besides a standard compatible web browser application, Web Element Manager does not require any
additional software installation for the used terminal (for example laptop). SBTS software provides the
web server functionalities for the element manager. When connected to the web server in SBTS, the
browser uploads all the necessary data for the element manager.

Web Element Manager also provides offline functionality: an HTML file can be saved during an active
session to a BTS, and then opened in offline mode in a web browser. The local management terminal
needs to be physically connected to an Ethernet connector in the SBTS system module. Also a remote
connection through the O&M DCN is possible. NetAct integrates Web Element Manager into NetAct’s
own management views and task flows for remote use.

While the existing BTS Site Manager is no longer used for SBTS, it still has a role in the manual com-
missioning of the SBTS. This is because the FSMF factory delivery software is based on the BTS soft-
ware architecture, and it does not have the web server for the SRAN element managers.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 43

Final Use subject to agreed restrictions on disclosure and use.
Single RAN Management Overview DN09212604 6-0 Troubleshooting

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [Link]@[Link] on 20-06-2022.
13 Troubleshooting
You can collect an SBTS snapshot remotely using NetAct, or with SBTS Element Manager. When us-
ing NetAct, you can collect snapshot data from multiple SBTSs parallel.

The snapshot collection is triggered from Configurator. When the snapshot collection is completed at
the SBTS, the snapshot is automatically uploaded, and saved to the NetAct file system.

In Trace Viewer it is possible to use the LTE user tracing functionality (subscriber, equipment, and cell)
for SBTS.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 44

Final Use subject to agreed restrictions on disclosure and use.