Nokia Networks
Single RAN, Rel. SRAN 16.2, Operating Documentation, Issue 02 Single RAN License Operation DN09228784 Issue 01 Approval Date 2015-12-11
Single RAN License Operation
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“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 Solutions and Networks. 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 Solutions and Networks 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 Solutions and Networks welcome 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 Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks 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, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS 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 Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2016 Nokia Solutions and Networks. 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 Solutions and Networks 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 Solutions and Networks for any additional information.
2
DN09228784
Issue: 01
Single RAN License Operation
Table of Contents This document has 18 pages
Summary of changes..................................................................... 6
Issue: 01
1
Introduction to license management in Single RAN.......................7
2
Overview of licenses and license management in Single RAN......8
3 3.1 3.2
Architecture of license management in Single RAN.................... 10 Mechanism for checking configuration data in Single RAN license management.................................................................................11 Software license migration from WBTS to SBTS......................... 12
4
Planning and ordering.................................................................. 13
5
Integrating a new network element.............................................. 14
6
Capacity expansion......................................................................15
7
Single RAN Monitoring Modules.................................................. 16
8
Free period for licenses................................................................17
9
Licenses in Single RAN................................................................18
DN09228784
3
Single RAN License Operation
List of Figures
4
Figure 1
Software License Keys concept in Single RAN.................................. 11
Figure 2
Mechanism for checking configuration data in LTE License Management....................................................................................... 11
DN09228784
Issue: 01
Single RAN License Operation
List of Tables Table 1
Issue: 01
Single RAN 16.2 licenses................................................................... 18
DN09228784
5
Summary of changes
Single RAN License Operation
Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Issue 01 (2015-12-11, Single RAN 16.2). This is the first issue of the document.
6
DN09228784
Issue: 01
Single RAN License Operation
Introduction to license management in Single RAN
1 Introduction to license management in Single RAN This section contains general information on license management in Single RAN. From Single RAN 16.2 onwards, Nokia introduces a new software (SW) license management, which is an evolution of the mechanism currently existing in WCDMA RAN. After a customer’s order, SW License Keys can be retrieved by Nokia Central Licensing System (CLicS), which generates SW License Keys (LKs). The LKs have to be uploaded to the Centralized SW License Server (CLS). The LKs are assigned automatically to the Single BTSs (SBTSs) according to the usage of SW LK protected Sales Items. The LKs are not physically downloaded to the SBTSs. They are kept in the CLS from where NetAct SW Entitlement Manager (SWEM) assigned Right To Use (RTU) to the particular SBTSs. There is one CLS per the whole operator’s network. The CLS cooperates with SW Entitlement Managers (SWEMs) in NetAct Regional Clusters (NetAct RCs).
g
Note: For Single RAN, the new licensing mechanism, as described in the Single RAN License Operation document, applies only for SBTS. Consequently, the SW licensing mechanism existing in the radio network elements (NEs), such as WBTS, RNC, BSC, and NetAct, does not change. For more information on RNC, see the WCDMA RAN License Operation / License management in RNC document available in NOLS. For more information on BSC, see the GSM/EDGE BSS / Administer / BSC/TCSM and mcBSC/mcTC / License Management in BSC document available in NOLS.
Issue: 01
DN09228784
7
Overview of licenses and license management in Single RAN
Single RAN License Operation
2 Overview of licenses and license management in Single RAN Description of licenses in LTE License management is a method for controlling the use of optional software applications, the capacity of network elements, and some optional hardware functionalities. Licenses, also called License Keys, are XML files that enable using a specific feature or multiple features. They are generated via the Central Licensing System (CLicS) based on customer’s orders.
g
Note: Do not modify the license file by editing or renaming it. Otherwise, the license file is corrupted. A license file can include the following entries: • • • • • • • • • • • • • • • • • •
License code License name Order ID Serial number Customer ID Customer name Maximum value Start time End time Target network element (NE) type Target ID Feature code Feature name Signature Additional info Capacity unit License type (possible values for this field are On/Off/Capacity) Usage type (possible values for this field is Pool - Commercial License)
The target identifier (target ID) is an identifier of the Centralized License Server (CLS), for which a particular license key can be used.
g
Note: A license file is identified by its filename and a serial number. When there are two files with the same filename and serial number, these files might be different versions of the same license file. License management in Single RAN All licenses in Single RAN are pool licenses. After ordering license capacity, pool license keys and ordered capacity can be retrieved via the CLicS tool, which is Nokia Central Licensing System to generate license files. Then, the license is installed in the CLS pool. The OSS SWEM (SW Entitlement Manger, a component of the SW Asset Monitoring) tool calculates the required license capacity. The capacity is determined based on the NetAct Regional Cluster (NetAct RC) database configuration parameters. The OSS SWEM cooperates with the CLS to allocate calculated pool license capacity. Licenses are not downloaded to the SBTS, but they are kept in CLS.
8
DN09228784
Issue: 01
Single RAN License Operation
Overview of licenses and license management in Single RAN
Pool licenses in Single RAN license management Pool licenses are used for SBTSes in Single RAN. All pool licenses are stored in the CLS. They are available to all NetAct RCs of the operator’s network. Pool licenses specify the size of the pool. The size is interpreted in two different ways as On/Off licenses and capacity licenses. •
•
Issue: 01
For the On/Off licenses, the size of the pool defines the number of entities, for example network elements that are permitted to use the functionality. This means that you can create licenses for a particular number of entities. For the capacity licenses, the size of the pool represents the total amount of capacity that can be divided among network elements in the operator’s network. This means that the CLS can grant or deny right-to-use (RTU) of required capacity available in the pool.
DN09228784
9
Architecture of license management in Single RAN
Single RAN License Operation
3 Architecture of license management in Single RAN Nokia introduces the physical software License Keys (SW LKs) concept for the SBTSes in Single RAN. In the operator’s network there is one network-wide pool within a single CLS. The pools of licenses are not split into the NetAct RCs as it was implemented for WCDMA BTSes. The components of the Single RAN SW License Management and their roles: •
•
•
•
•
10
Central Licensing System (CLicS) The ClicS is an application and interface for creating and delivering SW license keys that Nokia generates based on the customer’s order. Centralized License Server (CLS) The CLS is an application that provides a central control point for granting or denying right-to-use (RTU) to Nokia software. There is one CLS per a whole customer’s network. All NetAct Clusters are connected to the CLS. NetAct Regional Cluster (NetAct RC) The NetAct RC is a framework that offers a versatile network and a mobile service management solution. In Single RAN each NetAct RC runs its own SW Entitlement Manager (SWEM). Software Entitlement Manager (SWEM) The SWEM, as a component of existing SWAM, is a software component located in a NetAct RC. It continuously checks configuration data and counter information provided by the NetAct RC for relevant Sales Items (SIs). The SWEM verifies the activation and the capacity of Standard, High-value, and Hardware (STD/HVF/HWA) features. The SWEM cooperates with the CLS to verify if sufficient SW license capacity exists. The SW license keys are not physically installed at the eNB. They are booked in the CLS and SWEM as an RTU. In case of missing SW license capacity, the SWEM generates a limitation command to the related SBTS. Software Asset Monitoring (SWAM) For the customer purposes, the SWAM is a process of monitoring the performance management, charging statistics, and configuration management data that is related to software assets in the customer network. The SWEM and the SWAM are using the same calculation methods for checking license usage. The monitoring happens in the customer network, but it is controlled and invoiced by Nokia according to the customer contract.
g
Note: Once licenses are assigned to an SBTS, they are tied to this SBTS and cannot be redistributed. Consequently, floating is not supported.
g
Note: The OSS SWEM is a component of the SWAM and is available with every NetAct RC installation.
g
Note: Only one CLS for the complete customer’s network is needed. The CLS has to be deployed on any existing NetAct cluster as optional (Virtual Machine) nodes.
DN09228784
Issue: 01
Single RAN License Operation
Architecture of license management in Single RAN
Figure 1
Software License Keys concept in Single RAN Operator'sNetwork CM&PMdatachecking forRTUbySWEM SBTS
NetActRC RTURequest/ Release
CLicS LKs
SBTS
PM SWEM
SBTS
CM
Centralized LicenseServer CLS
XML XML
Databasesupervised bySWEM
PoolLKs
SBTS
NetActRC RTUGrant/ Deny
SBTS
PM SWEM
SBTS
CM
PM PerformanceManagement CM ConfigurationManagement
3.1 Mechanism for checking configuration data in Single RAN license management Mechanism for checking configuration data in Single RAN License Management The mechanism of checking configuration data is applicable for STD/HVF/HWA features. The SWEM checks continuously the NetAct RC configuration data and compares values with the previous maximum value. In case of increased capacity, the SWEM checks with the CLS if enough license capacity is still available in the pool. The license capacity is reduced in the pool and the SWEM allocates the related RTU to the SBTS. There is no physical license key downloaded to the SBTS. In case of missing SW licenses, the SWEM generates a license missing alarm. Figure 2
Mechanism for checking configuration data in LTE License Management Operator'sNetwork
SWLicense Keys
Centralized LicenseServer
NetActRC RTURequest/ Release
CLS SWLKs
PM SWEM
RTUGrant/ Deny
XML XML
SBTS
CM
Dataupload
PM CM
Pools
PM PerformanceManagement CM Configuration Management
Issue: 01
DN09228784
11
Architecture of license management in Single RAN
Single RAN License Operation
3.2 Software license migration from WBTS to SBTS The migration from a WCDMA BTS (WBTS) to an Single RAN BTS (SBTS) is a simple process. The license capacity, as required for SBTSs, needs to be ordered and loaded to the pool. After startup, according to the configuration and usage, the software license keys (SW LKs) provide capacity which is automatically allocated from the pool. The pool capacity is reduced respectively. After the upgrade, the SW LKs become ineffective as they already exist in the WBTS. They do not block or harm anything. After the migration, these SW LKs can be removed without any impact on NEs. For the new SBTS, the SW LKs are in the CLS, whilst in the WBTS the SW LKs are physically installed on the NEs. As the approaches differ in the WBTS and the SBTS, no direct migration is possible.
12
DN09228784
Issue: 01
Single RAN License Operation
Planning and ordering
4 Planning and ordering The principles of planning required pool licenses are as follows: • •
The SBTS HW needs to be definied for an initial rollout or for a capacity upgrade. The SW functionality needs to be definied and parametrized.
The process of ordering required licenses is as follows: 1. Network planning identifies the need for a capacity upgrade to guarantee a certain service. 2. The amount of required capacity is identified. 3. A purchase order for licenses with the required capacities is issued. 4. Nokia delivers the licenses taking respective lead times into account. 5. The licenses are imported to the network's CLS. 6. The operations department performs the license distributions according to specified processes. For more information on CLS, see Centralized License Server Overview available in Nokia Networks Online Services (NOLS). Accessing NOLS requires authentication. For more information, see Plan and Dimension/Dimensioning SBTS document.
Issue: 01
DN09228784
13
Integrating a new network element
Single RAN License Operation
5 Integrating a new network element Before integrating a new network element, it is recommended to check if enough pool license capacity is available in the CLS. If not, additional license capacity is needed to be installed. The connection between the NE and the NetAct RC is established and then the licenses distribution is done automatically. An example of an integration procedure for an NE is as follows: 1. 2. 3. 4. 5. 6.
The NE is installed and commissioned by the customer. The customer integrates the NE into NetAct RC. The customer downloads and activates the latest SW release if necessary. Additional cells are enabled and additional features are switched on by the customer. The NetAct database is updated automatically. By periodical database's checking, the SWEM detects a new enabled functionality or extended capacity. 7. The SWEM automatically requests additional capacity from the CLS. 8. The CLS grants or denies RTU.
14
DN09228784
Issue: 01
Single RAN License Operation
Capacity expansion
6 Capacity expansion In case of capacity expansion, for example when features are configured on additional cells, the updated configuration is monitored and checked by the SWEM. As a result the SWEM automatically allocates additional capacity from the CLS pool. If the required capacity is missing, an alarm 41003 LICENSE CAPACITY NOT AVAILABLE is raised. The consequence is that capacity expansions do not need any specific activities related to license management.
g
Issue: 01
Note: In the Single RAN 16.2 there are no Sales Items based on Performance Management. Blocking and limitations are not present as well.
DN09228784
15
Single RAN Monitoring Modules
Single RAN License Operation
7 Single RAN Monitoring Modules The existing SW Monitoring still supports the Single RAN. Consequently, in addition to physical LKs, configuration of Sales Items and the usage based on counters relevant for invoicing can be reported. For more information on SWAM, see NetAct operating documentation: Software Asset Monitoring available in Nokia Networks Online Services (NOLS). Accessing NOLS requires authentication.
16
DN09228784
Issue: 01
Single RAN License Operation
Free period for licenses
8 Free period for licenses In the Single RAN every feature gets 14-days free period. During the first activation, the operator is informed about it and has 14 days (license free period) to order licenses as needed. The following two options are possible in case of activating features: • •
g
Issue: 01
The customer activates a licensed features and license exists in the pool - the license is allocated as an RTU to the dedicated NE. The customer activates a feature but no license exists in the pool - the customer has 14 days during which the feature can be disabled and then no license is needed at all. Note: A threshold can be defined in the CLS. The threshold enables early indication of running out capacity. The information is delivered via email to the operator.
DN09228784
17
Licenses in Single RAN
Single RAN License Operation
9 Licenses in Single RAN This chapter provides an overview of all license-controlled sales items (SIs) in SW release Single RAN 16.2. Table 1
Single RAN 16.2 licenses
Sales Item (SI)
Feature Code
Description
Feature ID RP000357
Capacity Unit
SR000357.T
5691
Additional 2 E1/T1 Interfaces
Number of E1 interfaces
SR000365.T
5692
Additional 1GE RP000365 interfaceSmall Form Factor RP000367 Plugable Slot (SFP slot)
Number of 1GE ports
SR000360.T
5675
IP Transport Network Measurements
RP000360
BTS
SR000375.T
5677
Synchronous Ethernet
RP000375
BTS
SR000374.T
5678
Timing over Packet with Frequency Sync
PR000374
BTS
SR000411.T
5676
Transport Separation for LTE RAN Sharing
PR000411
BTS
SR000376.T
5679
Synchronization from 2.048MHz signal
RP000376
BTS
RP000788
1PPs / ToD or 2MHz from Ext Sync
18
SR000344.T
5674
Fast IP Rerouting
RP000344
BTS
SR000383.T
5687
Timing over Packet with Phase Sync
RP000383
BTS
SR000356.T
5688
IPsec for BTS
RP000356
BTS
SR000954.T
5689
SBTS Multi-RAT Operation PR000954
BTS
SR000600.T
5690
Backup Ipsec Tunnel
PR000600
BTS
SR001000.T
5646
SBTS RF Sharing
RP001000
Number of RATs
SR000972.T
5649
SBTS System Module Sharing
RP000972
Number of RATs in the same unit
SR001005.T
5648
SBTS Channel bandwidth
RP001005
Number of bandwidth 1MHz
SR001015.T
5650
SBTS Incremental 20W Power
RP001015
Number of 20W
DN09228784
Issue: 01
