Manage Licenses SW 16

Manage Licenses

hp://localhost:9032/alexserv?AC=LINK&ID=32232&FN=31_1553-LZA7...

User Guide

31/155 31/1553-L 3-LZA ZA 701 701 6004 6004/1 /1 Uen Uen B4

Manage Licenses Contents Descriptions License Management Overview License Handling Process Feature Licenses Hardware Activation Codes OSS and RBS License Management Software ELIS Temporary States License Observability Procedures Install License using OSS-RC Add Licenses from a License Pool Manage Licenses in Autointegration Activate Feature Deactivate Feature

1 Descriptions 1.1 License Management Overview LTE basic functionality can be enhanced by adding features and capacity. LTE capacity. This is done by ordering and installing licenses for SW SW features features and Hardware Activation Codes ( HWAC HWAC)) for HW HW capabilities. capabilities. Each capacity feature licenses can be applied in three levels: Priced level – Existing and supported handling. Boundary level – The Connected Users capacity is restricted at a boundary level defined in the contract. Not Contractually Limited (NCL) level – No f inite capacity is defined in the contract, which means the capacity restriction for a capacity feature is disabled. Note: For the MSRBS V1 there is currently no license management. LTE LT E license management is handled in the following way: Operators order feature licenses and HWAC HWAC in in bulk, separately from ordering the RBS hardware. The licenses are distributed through Ope rations Support System (OSS ( OSS)) to each RBS by RBS by matching the fingerprint (unique logical name) of the RBS RBS with with the fingerprint information in the license keys. LTE RB RBSs Ss are are delivered with wi th limited capacity, capacity, which is extended with HWAC HWAC after after installation to provide the capacity required in the operator network. There are no pre-installed feature licenses or HWAC HWAC in in the RBS RBS..

Manage Licenses


All HWAC and feature licenses are managed by network management software. 1.1.1

RBS Identity

During RBS installation at the site, the field engineer loads a site configuration file in the RBS. The site configuration file includes the RBS unique logical name, also called fingerprint, which is used to authenticate the RBS. 1.1.2

License Allocation

Based on a network plan, the operator specifies the licenses to allocate to each RBS. The specification can be prepared using external tools, MS Excel, or di rectly in ELIS. Each LTE RBS is identified in ELIS by its fingerprint, a unique logical name. ELIS allocates licenses accordingly from the operator's pool of licenses, and creates the corresponding License Key Files.

1.2 License Handling Process

Figure 1

Process of License Handling

Figure 1 provides an overview of license handling in t he following steps:

1. The operator plans and dimensions the network to determine the licenses and HWAC required.

2. After network planning and dimensioning, the operator places orders for HWAC and for software licenses with the Ericsson Market Unit (MU).

3. The MU distributes the order to Ericsson's Electronic Licensing Solution (ELIS).

Manage Licenses


4. The ONE system generates a License Authorization Code (LAC) letter and Ericsson sends the LAC letter to the operator. The authorization code allows license keys (capacity keys and feature keys) to be allocated to the RBSs using ELIS. The license keys are downloaded to each RBS using OSS.

1.3 Feature Licenses Feature licenses enable use of SW features adding functionality to the network. 1.3.1

Licensing using GLMS

Features introduced in L13B or later are using the Generic License M anagement Solution (GLMS). All features will gradually migrate to GLMS. For each optional feature using GLMS an MO instance of the MO class OptionalFeatureLicense gets automatically created. The features are activated by setting the featureState parameter for the optional feature MO instance to ACTIVATED. For more information, see Managed Object Model (MOM). For each capacity feature using GLMS an MO instance of the MO class CapacityFeatureLicense gets automatically created. The capacities are enabled when a license key is installed. For more information, see Managed Object Model (MOM). 1.3.2

Licensing using the Legacy Licensing Infrastructure

Features are activated by setting the feature state parameter for that optional feature MO class to ACTIVATED. For more information, see Managed Object Model (MOM). Capacity features are enabled when a license key is installed. For more information, see Managed Object Model (MOM). 1.3.3

Mixed Mode Licenses (FDD Only)

The feature Mixed Mode in Multistandard RBS requires a license. A feature license for Mixed Mode i s needed for all radio standards in a Multistandard RBS running Mixed Mode. If radio output is to be above 20 W, the RUs in the node require HWACs for each radio standard.

1.4 Hardware Activation Codes HWAC provide access to HW related RBS capabilities, that is HW related optional features and HW related node capacity. HWACs are controlled by keys. The following figure illustrates the process of evaluating the HWAC required:

Manage Licenses


Figure 2

Evaluation of required capacity

HWACs are required for activation of the following capabilities: Connected Users Downlink and Uplink Capacity Channel Bandwidth Output Power 1.4.1

Connected Users

Connected users in an RBS is the sum of connected users in all cells. The total connected users in the RBS is continuously updated in the identity register. When a HWAC is installed, the license key contains the connected users maximum limit. 1.4.2

Downlink and Uplink Capacity

The scheduled throughput, including retransmission and control signalling is set with downlink and uplink capacity. Capacity requirements are measured as Layer 2 throughput. In a multi-DU configured RBS the downlink and uplink capacity licenses can be distributed between the DUs, see Licensing for parameter settings. 1.4.3

Channel Bandwidth

Channel bandwidth is licensed per cell. For example, when an RBS is configured with three cells with up to 20 MHz bandwidth, then a license key for t hree cells results in one 20-MHz CapacityFeatureLicense = CapacityChannelBandwidth Managed Object (MO) Instance allowing three cells. The license handling software controls how the capacity is distributed among the cells. 1.4.4

Output Power

Manage Licenses


Output power is licensed per radio unit and sector. An RBS can operate sectors at 20 W without a license, since 20 W is included with each radio unit. Each output power level also requires a HWAC for the level below to be active. For example, to configure a radio unit with 60 W, both one 40 W and one 60 W HWAC is required. A sector is configured with the to tal output power available for all radio units belonging to the sector. The sector assigns output power to all connected radio units. When a cell is unlocked, licenses are checked for the configured total output power of the sector. If the RBS contains enough licenses, the request is granted and the license pool is decreased by corresponding number of licenses.

1.5 OSS and RBS License Management Software The OSS and RBS software used to manage licensing in LTE is described in the following table: Table 1

Functions of License Management Software

Software

Description of Function

OSS

The Software Management Organizer (SMO) communicates with the RBS to verify the products in the network. All license types are managed by the SMO. The Element Manager communicates with the RBS to authorize licensed configurations. The Fault Manager communicates with the RBS to authorize licensed fault management services. Also monitors li censing-related alarms and notifications.

RBS Licensing Verification

The RBS licensing software verifies the licenses for capacity and features in the RBS.

1.6 ELIS Ericsson Electronic Licensing Solution (ELIS) is a web-based entitlement management system for SW licenses and HWAC. ELIS is used for activating licenses and managing license pools. ELIS generates license keys based on a License Authorization Code (LAC) letter and handles single or quantity li censes for capacity and features. License Key Files can be exported to the SMO in OSS, or to other storage media to provide support for installation of license keys at the site. ELIS can also import information for a selection of, or all RBSs from OSS. License keys can be generated simultaneously for all RBSs in a network. One license key can be generated in less than a minute, and 5000 license keys in less than two hours.

1.7 Temporary States Capacity and features can under some circumstances be temporarily made available as described in the following sections. 1.7.1

Trial Licenses

When an operator wants to try out a feature in t he network, a trial license can be ordered. A trial license opens up a feature for a limited period of time. When the limited trial license period expires, the license management software deactivates the trial license key and the feature.

Manage Licenses

1.7.2


Grace Period

The Grace Period for the chosen capacity licenses provides the possibility to exceed the licensed capacity limits for a limited period of time. This enables the operator to see the utility of the capability at run time and allows time for ordering and installation of additional capacity. The grace period can only be used once. The grace period is reset by adding more capacity. The grace period is disabled for NCL. 1.7.3

Emergency Unlock

In the case of an emergency, for example an earthquake or a tsunami, license limitations can be temporarily disabled. In such cases, the Emergency Unlock function opens up all available resources during a limited period of ti me. OSS detects that the unlock function is active and when it expires. Note: Emergency Unlock of optional features works only with features operating under Generic License Management Solution (GLMS). Export-restricted features or capacities are only enabled, or provided without capacity limitations, if they were valid before activating Emergency Unlock. IPsec is an example of an export-restricted feature. Emergency Unlock can be used limited number of times. Additional emergency unlocks are provided by the licensed feature Emergency Unlock Reset.

1.8 License Observability LTE provides counters for managing licensing. Information about the available counters can be found in the respective feature description for the capacity features: Connected Users Downlink Baseband Capacity Uplink Baseband Capacity For more information about observability and performance management, see Performance Management, License and Resource Use Indicators and Key Performance Indicators.

2 Procedures Information about licensing configuration and settings can be found in the managed area description Licensing. It is important that the node system clock is set correctly when licenses are installed. If the system clock is incorrectly set, signature validation is affected and the license key file installation can be rejected by the node.

2.1 Install License using OSS-RC LTE licenses are managed with OSS-RC. The license installation process using OSS-RC is shown in the following figure:

Manage Licenses


Figure 3

License Activation with OSS-RC

Steps License keys are installed with OSS-RC in the following way: 1. During RBS installation at the site, the fie ld engineer loads a site configuration file in the RBS. The site configuration file includes the RBS unique logical name, also called fingerprint, which is used to authenticate the RBS. 2. OSS-RC verifies that the unique logical name is unique in the network. 3. When the RBS is authenticated and activated by SMO in OSS-RC, the matching license key file is installed by the RBS license manager.

2.2 Add Licenses from a License Pool Licenses from a license pool can be installed in the RBSs in a network as shown in the following figure:

Figure 4

Installing Licenses from a License Pool

Steps Installing licenses from the license pool in an RBS includes the following:

Manage Licenses


1. The RBS has an existing license key file installed with a set of license keys and HWAC. 2. A new license key file containing a new set of licenses is generated in ELIS and installed in the RBS. The new license key file includes t he original set of license keys and additional license keys from the license pool. 3. The RBS now uses the new license key file, and the new licenses (additional to the original set) have been subtracted from the license pool.

2.3 Manage Licenses in Autointegration With RBS autointegration, license key files are stored for automatic download from OSS-RC to the RBS. Without intervention from an OSS-RC operator, the autointegration process installs HWAC and feature license keys and brings the RBS online and ready for network traffic. Steps License management in autointegration includes the following high level procedure steps: 1. The RBS authenticates itself with OSS-RC. OSS-RC verifies that the RBS unique logical name is unique in the network. 2. The RBS obtains the HWAC and feature license keys from OSS-RC or a license server. 3. The RBS goes online with the correct licenses installed.

2.4 Activate Feature Activating a licensed feature requires t hat the correct license is installed. To activate a feature, do the following: Steps 1. Find the MO instance of OptionalFeatureLicense that controls the feature state. This is automatically created when the license is installed. Find the MO instance for each feature in the applicable feature description. Capacity feature activation and deactivation is performed in an MO instance of CapacityFeatureLicense . 2. Set the attribute featureState for the feature MO instance to ACTIVATED.

2.5 Deactivate Feature To deactivate a feature, do the following: Steps 1. Find the MO instance of OptionalFeatureLicense that controls the feature state. This is automatically created when the license is installed. Find the MO instance for each feature in the applicable feature description. Capacity feature activation and deactivation is performed in an MO instance of CapacityFeatureLicense .

Manage Licenses


2. Set the attribute featureState for the feature MO instance to DEACTIVATED.

Copyright

© Ericsson AB 2016. All rights reserved. No part of this d ocument may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in

Disclaimer

methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

Manage Licenses

Manage Licenses SW 16

Recommend Documents