eRAN
License Management Feature
Parameter Description
Issue
Draft A
Date
2019-01-05
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address:
Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
i
eRAN
License Management Feature Parameter Description
Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 1
2 About This Document.................................................................................................................. 3
2.1 General Statements......................................................................................................................................................... 3
2.2 Applicable RAT.............................................................................................................................................................. 4
2.3 Features in This Document.............................................................................................................................................4
2.4 Feature Differences Between NB-IoT and FDD............................................................................................................ 5
2.5 Feature Differences Between FDD and TDD.................................................................................................................5
3 General Principles......................................................................................................................... 6
3.1 LKF Introduction............................................................................................................................................................ 6
3.1.1 LKF Structure.............................................................................................................................................................. 6
3.1.1.1 Header.......................................................................................................................................................................7
3.1.1.2 SaleInfo.....................................................................................................................................................................8
3.1.1.3 KeyInfo................................................................................................................................................................... 10
3.1.1.4 Footer...................................................................................................................................................................... 11
3.1.2 LKF Types................................................................................................................................................................. 11
3.2 License Control Items...................................................................................................................................................13
3.2.1 License Control Items................................................................................................................................................13
3.2.2 License Control Item Types.......................................................................................................................................13
3.2.3 Multimode Base Stations...........................................................................................................................................14
3.2.3.1 LKFs for Multimode Base Stations........................................................................................................................ 14
3.2.3.2 License Control Items for Multimode Base Stations..............................................................................................14
3.2.4 Single-Mode Base Stations........................................................................................................................................24
3.2.4.1 LKFs for Single-Mode Base Stations..................................................................................................................... 24
3.2.4.2 License Control Items for Single-Mode Base Stations (FDD)...............................................................................24
3.2.4.3 License Control Items for Single-Mode Base Stations (TDD)...............................................................................52
3.2.5 License Control Items for USUs............................................................................................................................... 66
4 License Management.................................................................................................................. 67
4.1 License States............................................................................................................................................................... 67
4.1.1 Default License State.................................................................................................................................................68
4.1.2 Commissioning License State................................................................................................................................... 69
4.1.3 Normal License State.................................................................................................................................................69
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
ii
eRAN
License Management Feature Parameter Description
Contents
4.1.4 Emergency License State...........................................................................................................................................69
4.1.5 Grace Period State..................................................................................................................................................... 69
4.2 Common Methods for LKF Management.................................................................................................................... 70
4.2.1 LKF Precheck............................................................................................................................................................ 70
4.2.2 LKF Verification........................................................................................................................................................70
4.2.3 Consistency Check Between Licensed Values and Data Configurations.................................................................. 71
4.2.4 LKF Revocation........................................................................................................................................................ 71
4.2.5 License Overload....................................................................................................................................................... 72
4.2.6 License Redundancy..................................................................................................................................................72
4.2.7 LKF Backup and Restore.......................................................................................................................................... 72
4.2.8 Invalidating Fixed-term License Items......................................................................................................................73
4.3 NB-IoT Annual Fee Mode............................................................................................................................................74
4.3.1 Principles................................................................................................................................................................... 74
4.3.2 LKF Structure............................................................................................................................................................ 80
4.4 Multi-Operator License Management...........................................................................................................................80
4.4.1 Separate Capacities....................................................................................................................................................80
4.4.2 Shared Capacities...................................................................................................................................................... 81
4.4.3 Separate Features....................................................................................................................................................... 81
4.4.4 Shared Features..........................................................................................................................................................81
4.5 Network Analysis......................................................................................................................................................... 81
4.5.1 Benefits...................................................................................................................................................................... 82
4.5.1.1 eNodeB Deployment.............................................................................................................................................. 82
4.5.1.2 R-Version Upgrade or Capacity Expansion............................................................................................................82
4.5.1.3 Licensed Capacity Adjustment............................................................................................................................... 82
4.5.1.4 ESN Change........................................................................................................................................................... 82
4.5.2 Requirements............................................................................................................................................................. 83
4.5.2.1 Software..................................................................................................................................................................83
4.5.2.2 Hardware................................................................................................................................................................ 83
4.5.2.3 Others......................................................................................................................................................................83
4.5.3 Impacts.......................................................................................................................................................................83
4.6 Operation and Maintenance..........................................................................................................................................84
4.6.1 Data Configuration.................................................................................................................................................... 84
4.6.1.1 Data Preparation..................................................................................................................................................... 84
4.6.1.2 Using MML Commands......................................................................................................................................... 84
4.6.2 Activation Observation..............................................................................................................................................84
4.6.3 Common License Operations.................................................................................................................................... 84
4.6.3.1 License Operations on the U2020.......................................................................................................................... 85
4.6.3.2 License Operations on an LMT.............................................................................................................................. 91
5 Possible Issues............................................................................................................................. 95
5.1 Faults Occurred During Installation............................................................................................................................. 95
5.2 Faults During Operation............................................................................................................................................... 98
5.3 Alarms.......................................................................................................................................................................... 98
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
iii
eRAN
License Management Feature Parameter Description
Contents
5.4 Events........................................................................................................................................................................... 98
6 Parameters..................................................................................................................................... 99
7 Counters...................................................................................................................................... 100
8 Glossary....................................................................................................................................... 101
9 Reference Documents............................................................................................................... 102
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
iv
eRAN
License Management Feature Parameter Description
1 Change History
1
Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l
Technical changes
Changes in functions and their corresponding parameters
l
Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 Draft A (2019-01-05)
This issue introduces the following changes to eRAN13.1 01 (2018-04-10).
Technical Changes
Change Description
Paramete
r Change
RAT
Base Station
Model
Modified the functions and licensing
principles of LT4SUBBPMMCN and
LT4SUBBPMMBD. For details, see 3.2.4.3
License Control Items for Single-Mode
Base Stations (TDD).
None
TDD
3900 and 5900
series base
stations
Added the Massive MIMO Multimode
License for 5000 Series RF Module and
Massive MIMO Multi-band License for
5000 Series Multi-band RF Module. For
details, see 3.2.3.2 License Control Items
for Multimode Base Stations.
None
FDD
3900 and 5900
series base
stations
Changed the name of the U2000 to U2020
and updated related operations. For details,
see 4.6.3.1 License Operations on the
U2020.
None
Issue Draft A (2019-01-05)
TDD
Copyright © Huawei Technologies Co., Ltd.
FDD
TDD
3900 and 5900
series base
stations
1
eRAN
License Management Feature Parameter Description
1 Change History
Change Description
Paramete
r Change
RAT
Base Station
Model
Added LT4SOVTBAS15,
LT4SUBBPMMBD, and
LT4SUBBPMMCN. For details, see 3.2.4.3
License Control Items for Single-Mode
Base Stations (TDD).
None
TDD
3900 and 5900
series base
stations
Editorial Changes
Revised descriptions in this document.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
2
eRAN
License Management Feature Parameter Description
2 About This Document
2
About This Document
2.1 General Statements
Purpose
This document is intended to acquaint readers with:
l
The technical principles of features and their related parameters
l
The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l
Requirements of the operating environment that must be met before feature activation
l
Parameter configuration required for feature activation, verification of feature activation,
and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and feature
gains depend on the specifics of the network scenario where the feature is deployed. To achieve
the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document
apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for certain
reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible.
However, these features can still be used for testing purposes or commercial network trials.
Anyone who desires to use the trial features shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such
trial features. Trial features are not for sale in the current version but customers may try them
for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk
due to absence of commercial testing. Before using them, customers shall fully understand not
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
3
eRAN
License Management Feature Parameter Description
2 About This Document
only the expected benefits of such trial features but also the possible impact they may exert on
the network. In addition, customers acknowledge and undertake that since trial features are
free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the
trial features. Huawei does not promise that problems with trial features will be resolved in
the current version. Huawei reserves the rights to convert trial features into commercial
features in later R/C versions. If trial features are converted into commercial features in a later
version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the
said commercial features. If a customer fails to purchase such a license, the trial feature(s)
will be invalidated automatically when the product is upgraded.
Feature Differences Between RATs
The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a description does
not apply to all RATs, the specific RAT that it does apply to will be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-MIMO", "TDD
cells" indicates that this function cannot be used in non-TDD cells.
2.2 Applicable RAT
This document applies to FDD/NB-IoT/TDD.
2.3 Features in This Document
This document describes the following FDD features.
Feature ID
Feature Name
Section
LBFD-004014
License Management
3 General Principles
LBFD-004015
License Control for
Urgency
4.1.4 Emergency License State
This document describes the following NB-IoT features.
Feature ID
Feature Name
Section
MLBFD-1200
0414
License Management
3 General Principles
MLBFD-1200
0415
License Control for
Urgency
4.1.4 Emergency License State
This document describes the following TDD features.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
4
eRAN
License Management Feature Parameter Description
2 About This Document
Feature ID
Feature Name
Section
TDLBFD-004
014
License Management
3 General Principles
TDLBFD-004
015
License Control for
Urgency
4.1.4 Emergency License State
2.4 Feature Differences Between NB-IoT and FDD
NB-IoT
Feature
ID
NB-IoT
Feature
Name
FDD
Feature
ID
FDD
Feature
Name
Difference
Section
MLBFD-1
2000414
License
Manageme
nt
LBFD-0
04014
License
Management
None
3 General
Principles
MLBFD-1
2000415
License
Control for
Urgency
LBFD-0
04015
License
Control for
Urgency
None
4.1.4 Emergency
License State
2.5 Feature Differences Between FDD and TDD
FDD
Feature
ID
FDD
Feature
Name
TDD
Feature
ID
TDD
Feature
Name
Difference
Section
LBFD-004
014
License
Manageme
nt
TDLBF
D-00401
4
License
Management
None
3 General
Principles
LBFD-004
015
License
Control for
Urgency
TDLBF
D-00401
5
License
Control for
Urgency
None
4.1.4 Emergency
License State
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
5
eRAN
License Management Feature Parameter Description
3 General Principles
3
General Principles
Licenses are contracts that specify the features, releases, capacities, validity periods, and
usage scope of an operator's purchased products. All license information is carried by license
key files (LKFs).
Operators can purchase licenses to select network functions and capacities flexibly at specific
stages. This helps increase return on investment and reduces network deployment costs.
By performing license management, operators can ensure that the system operates properly
with the licensed features, releases, and capacities during the licensed time. As shown in
Figure 3-1, operators can download an LKF to an eNodeB and manage and query the
contents in this LKF using the local maintenance terminal (LMT) or U2020.
The LKF of an eNodeB or USU is stored on the main control board.
Figure 3-1 License management architecture
3.1 LKF Introduction
3.1.1 LKF Structure
LKFs are saved as .xml files. Table 3-1 describes the information contained in an LKF. The
LKF contains only information about the purchased features and capacities.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
6
eRAN
License Management Feature Parameter Description
3 General Principles
Table 3-1 Segments of the LKF
Segment
Content
Header
General information describing an LKF, including the
GeneralInfo, CustomerInfo, and NodeInfo sections
SaleInfo
Customer-oriented sales information, including the product
information and sales items
KeyInfo
Software control information
Footer
Signature
NOTE
The following types of values are involved in the use of LKFs:
l Licensed value: number of hardware or feature licenses purchased by a customer
l Configured value: number of hardware or feature licenses configured on the NE for a customer
l Used value: number of hardware or feature licenses actually used by a customer
3.1.1.1 Header
GeneralInfo
Table 3-2 describes the fields in the GeneralInfo section.
Table 3-2 Fields in the GeneralInfo section
Field
Description
CopyRight
Copyright, which is always "Huawei Technologies Co., Ltd. All rights
reserved."
LSN
Serial number of the LKF
LicType
Type of the LKF
GraceDay
Number of days in a grace period, during which the licensed capacities
and features are still in effect, after the LKF expires
Creator
Company that created the LKF, which is always "Huawei Technologies
Co., Ltd."
Issuer
Person who issued the LKF
CreateTime
Time when the LKF was created
CustomerInfo
Table 3-3 describes the fields in the CustomerInfo section.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
7
eRAN
License Management Feature Parameter Description
3 General Principles
Table 3-3 Fields in the CustomerInfo section
Field
Description
Customer
Operator name
Country
Country where the operator is located
Office
City where the operator is located
NodeInfo
Table 3-4 describes the fields in the NodeInfo section.
Table 3-4 Fields in the NodeInfo section
Field
Description
Node
Name of the network element (NE) to which the LKF applies
Des
Detailed description of the NE
Sequence
Sequence number. A value x indicates that this LKF is the xth LKF for
the NE. The value increases each time the LKF is updated because of an
upgrade, capacity expansion, reconfiguration, equipment serial number
(ESN) change, or issuer change. This field does not appear in demo
LKFs.
LockModel
Locking mode, which occupies a maximum of 16 bytes. This field has
two values: NODELOCK (default) and DUALLOCK.
NOTE
NODELOCK: The LKF is locked to one specified NE.
DUALLOCK: The LKF can be locked to several specified NEs.
ESN
ESN of the NE
3.1.1.2 SaleInfo
OfferingProduct
The OfferingProduct field has the attributes described in Table 3-5.
Table 3-5 Attributes of the OfferingProduct field
Attribute
Description
name
Product name
version
Product version
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
8
eRAN
License Management Feature Parameter Description
3 General Principles
SaleItem
Each SaleItem field has an attribute of name, which indicates the sales bill of material
(SBOM) part number of the sales item. The SaleItem sections contain only the purchased
features and capacities.
Table 3-6 describes the fields in each SaleItem section.
Table 3-6 Fields in each SaleItem section
Field
Field Description
Attribute
Description
Value
Purchased units of the
sales item
validDate
Expiration date, in the
format of YYYY-MM-DD.
This attribute has a value
of PERMANENT if the
item never expires.
NOTE
If a permanent license
control item and a fixed-term
license control item coexist,
the section may include more
than one Value field with
different validDate
attributes.
DesChs/
DesEng
Chinese or English
description of the sales
item
unit
Sales unit
CapacityKey
Resource item. Table 3-7
describes the subordinate
field.
name
Name of a license control
item
name
Name of a license control
item
One SaleItem section may
contain more than one
CapacityKey field.
FeatureKey
Function item. Table 3-7
describes the subordinate
field.
One SaleItem section may
contain more than one
FeatureKey field.
Table 3-7 Field under CapacityKey and FeatureKey
Field
Field Description
Attribute
Description
Value
Licensed value
validDate
Expiration date, in the
format of YYYY-MM-DD.
This attribute has a value
of PERMANENT if the
item never expires.
NOTE
If a permanent license
control item and a fixedterm license control item
coexist, the section may
include more than one
Value field with different
validDate attributes.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
9
eRAN
License Management Feature Parameter Description
3 General Principles
A CapacityKey (or FeatureKey) field may have different Value settings in the SaleInfo and
KeyInfo segments. The SaleInfo segment provides sales information, and the KeyInfo
segment provides software control information. The Value settings in the two segments can
be converted into each other and may be different.
3.1.1.3 KeyInfo
The KeyInfo field has the attributes described in Table 3-8.
Table 3-8 Attributes of the KeyInfo field
Attribute
Description
productName
Product name
productVersion
Product version
The KeyInfo segment contains at least one CapacityKey or FeatureKey section. Table 3-9
describes the fields in each KeyInfo segment.
Table 3-9 Fields in each KeyInfo segment
Field
Field Description
Attribute
Description
CapacityKey
Resource item. Table 3-10
describes the subordinate
field.
name
Name of a license control
item
group
Group to which the
license control item
belongs
Function item. Table 3-10
describes the subordinate
field.
name
Name of a license control
item
group
Group to which the
license control item
belongs
FeatureKey
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
10
eRAN
License Management Feature Parameter Description
3 General Principles
Table 3-10 Field under CapacityKey and FeatureKey
Field
Field Description
Attribute
Description
Value
Licensed value
validDate
Expiration date, in the
format of YYYY-MM-DD.
This attribute has a value
of PERMANENT if the
item never expires.
NOTE
If a permanent license control
item and a fixed-term license
control item coexist, the segment
may include more than one Value
field with different validDate
attributes.
3.1.1.4 Footer
Table 3-11 describes the fields in the Footer segment.
Table 3-11 Fields in the Footer segment
Field
Field Description
Attribute
Description
CommonSi
gn
Common signature
method
ID of the encryption
algorithm.
ProductSig
n
Customized signature.
method
ID of the encryption
algorithm.
NOTE
The following encryption
algorithms are supported:
1-RSA1024, 2-RSA2048,
3-ECC163, and 4-ECC233.
3.1.2 LKF Types
LKFs are classified into commercial LKF, commercially permanent & fixed-term LKF, and
demo LKF based on application scenarios.
Commercial LKF
A commercial LKF is created on the basis of a business contract. In principle, a license
certificate together with the electronic LKF is issued to the customer. The authorization type
(LicType) for a commercial LKF is COMM.
All license control items have the same expiration date, either permanent or a specific date,
which corresponds to a commercially permanent license or a fixed-term license. The default
grace period for license control items in a fixed-term license is 60 days.
Commercially Permanent & Fixed-term LKF
A commercially permanent & fixed-term LKF is used when a network needs to be frequently
adjusted and license trial is required before purchase. The authorization type (LicType) for a
commercially permanent & fixed-term LKF is COMM.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
11
eRAN
License Management Feature Parameter Description
3 General Principles
A commercially permanent & fixed-term LKF comprises permanent license control items and
license control items having a fixed expiration date. The expiration date is PERMANENT for
permanent license control items.
Demo LKF
A demo LKF is temporarily used for verifying software functions during project
implementation. In principle, a license certificate together with the electronic LKF must be
issued to the customer.
The authorization type (LicType) is DEMO, and all license control items in a demo LKF
have the same expiration date.
Demo LKFs are further classified into the following subcategories:
RA
T
Subcategory
Description
FD
D
Demo LKF with a 255day validity period and
ESN set to ANY
This type of LKF applies to eNodeBs. There are no
restrictions on the number of times that demo LKFs of this
type can be loaded within the 255-day time period. This
type of LKF can be used for a maximum of 255 days in
total on a single eNodeB within one software release.
Demo LKF with a
validity period of one,
two, or three days and
ESN set to ANY
This type of LKF applies to eNodeBs. There are no
restrictions on the number of times that demo LKFs of this
type can be loaded. The use duration of this type of demo
LKFs is not added to the total number of days that demo
LKFs with ESN set to ANY are used. Therefore, this type
of demo LKFs is not subject to the restriction that demo
LKFs with ESN set to ANY cannot be used for more than
255 days within one software release. This type of LKFs is
used only for fault rectification.
Demo LKF with a 14day validity period and
ESN not set to ANY
This type of LKF applies to eNodeBs or USUs with
specific ESNs. All the features specified in such an LKF
are valid for 14 days. There are no restrictions on the
number of times that demo LKFs of this type can be
loaded within the 14-day period. This type of LKFs is used
only for fault rectification.
Demo LKF with a 255day validity period and
ESN set to ANY
This type of LKF applies to USUs. There are no
restrictions on the number of times that demo LKFs of this
type can be loaded within the 255-day time period. This
type of LKF can be used for a maximum of 255 days in
total on a single USU within one software release.
TD
D
FD
D
TD
D
FD
D
TD
D
FD
D
TD
D
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
12
eRAN
License Management Feature Parameter Description
3 General Principles
RA
T
Subcategory
Description
FD
D
Demo LKF with a 3day validity period and
ESN set to ANY
This type of LKF applies to any USUs. There are no
restrictions on the number of times that demo LKFs of this
type can be loaded. The use duration of this type of demo
LKFs is not added to the total number of days that demo
LKFs with ESN set to ANY are used. Therefore, this type
of demo LKFs is not subject to the restriction that demo
LKFs with ESN set to ANY cannot be used for more than
255 days. This type of demo LKFs is used only for fault
rectification.
TD
D
3.2 License Control Items
3.2.1 License Control Items
License control items are key components in an LKF, and they are displayed as models in the
LKF. After an LKF is installed and functions properly, license control items in use can be
queried by running the DSP LICINFO command, and their descriptions are displayed in the
command output. The model and description of a license control item are described as
follows:
l
Model
A license control item is displayed as a model in an LKF and consists of letters in upper
case and digits. A model uniquely identifies a license control item.
l
Description
The description of a license control item is similar to its feature or capacity name. For
details about the mapping between license control item descriptions and feature or
capacity names, see:
–
License Control Item Lists (FDD)
–
License Control Item Lists (TDD)
–
License Control Item Lists (CIoT)
NOTE
License control item descriptions are displayed in the Description column in the DSP LICINFO
command output.
3.2.2 License Control Item Types
An LKF is used on multimode and single-mode base stations. License control items are
classified into the following two types:
l
Capacity items
Operators can purchase license units for the level of capacity that they require without
spending money for capacity that they will not use.
l
Feature items
Feature items cover basic and optional software features. Basic software features are
usually assembled into a basic package for sale. The basic package is mandatory.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
13
eRAN
License Management Feature Parameter Description
3 General Principles
3.2.3 Multimode Base Stations
3.2.3.1 LKFs for Multimode Base Stations
Multimode base stations can work in GSM, UMTS, LTE FDD, LTE TDD, and LTE NB-IoT
modes and are classified into co-MPT and separate-MPT base stations.
l
A co-MPT base station has only one OMCH with the U2020, and it is managed and
maintained as one logical NE (BTS3900) on the U2020.
l
A separate-MPT base station has multiple OMCHs with the U2020, and it is managed
and maintained as a number of logical NEs on the U2020.
There is no dedicated LKF for a multimode base station (co-MPT or separate-MPT). The
GBTS, eGBTS, NodeB, or eNodeB in a multimode base station has a separate LKF and
manages its license independently. Details are as follows:
l
GBTS: The GBTS is managed as a component of the base station controller (BSC) and
its license is also managed by the BSC.
l
eGBTS: The eGBTS's LKF is stored on the U2020 and shared by all eGBTSs under the
same BSC.
l
NodeB: The NodeB's LKF is stored on the U2020. License management of the NodeB is
the same as that of a single-mode NodeB.
l
eNodeB: The eNodeB can work in LTE FDD, LTE TDD, or NB-IoT mode but uses the
same LKF with different license control items for FDD, TDD, and NB-IoT. The LKF is
stored on the base station and the license management mechanism is the same as that of a
single-mode eNodeB (FDD, TDD, or NB-IoT).
3.2.3.2 License Control Items for Multimode Base Stations
License control items for multimode base stations are categorized as capacity items and
feature items.
Capacity Items
The capacity items for a multimode base station are classified into single-mode and radio
access technology (RAT) items.
l
Single-mode items are dedicated to an RAT. For details about single-mode items, see
capacity license items in License Management for each RAT.
l
RAT items are used to allocate the hardware capacity of modules working in several
RATs in parallel. Such item can be used only after it has been purchased for the
corresponding RAT. There are currently RF multimode license control items, UMPT
multimode license control items, UBBP multimode license control items, multimode
license control items for micro base stations, and RF spectrum sharing license control
items.
–
RF multimode license control items: Different types of RF modules use different
multimode license solutions. If a base station has different types of RF modules,
different multimode license solutions must be used for sale and control of these RF
modules.
(1) When a single-band RF module (non-5000 series RF module) is configured to
work in two RATs (GU/GL/UL), the operator needs to purchase the corresponding
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
14
eRAN
License Management Feature Parameter Description
3 General Principles
RF module dual-mode (GU/GL/UL) license. This type of license is sold and
controlled on the basis of the more recent RAT of the two RATs (LTE NB-IoT >
LTE TDD > LTE FDD > UMTS > GSM). When the RF module works in a single
RAT (GO/UO/LO), the operator does not need to purchase RF module multimode
licenses. When the RF module works in multiple RATs including NB-IoT, the
operator needs to purchase the RF Multi-Mode license(NB-IoT).
If a 5000 series RF module is working only for one RAT, the operator needs to
purchase the first-mode license for this RAT. If the 5000 series RF module is
working for multiple RATs, each RAT requires one license. Additionally, the lowest
RAT uses a first-mode license while the other RATs use multimode licenses. The
descending order of RATs is as follows: LTE NB-IoT > LTE TDD > LTE FDD >
UMTS > GSM. For example:
n
An RF module working in GSM mode requires one First Mode License for
5000 Series RF Module (GSM).
n
An RF module working in GU modes requires one First Mode License for
5000 Series RF Module (GSM) and one Multimode License for 5000 Series
RF Module (UMTS).
n
An RF module working in GUL modes requires one First Mode License for
5000 Series RF Module (GSM), one Multimode License for 5000 Series RF
Module (UMTS), and one Multimode License for 5000 Series RF Module
(FDD).
For 5000 series single-band RF modules, the RFU, RRU, and AAU can share a
license.
(2) For a non-5000 series multi-band RF module (except the RRU3961), the RF
module licenses are classified into the First Mode First Band License for MultiBand RF Module and Multi-Mode Multi-Band License for Multi-Band RF Module
in sales for GSM, UMTS, LTE FDD, or LTE NB-IoT. For the first frequency band
of the first RAT, the operator needs to purchase the First Mode First Band License
for Multi-Band RF Module for this RAT. For other RATs and other frequency
bands, the operator needs to purchase the Multi-Mode Multi-Band License for
Multi-Band RF Module for the corresponding RATs. During the use, the First Mode
First Band License for Multi-Band RF Module is automatically converted into the
Multi-Mode Multi-Band License for Multi-Band RF Module. Therefore, one MultiMode Multi-Band License for Multi-Band RF Module is required for each band of a
multimode RF module running on GSM, UMTS, LTE FDD, or LTE NB-IoT. Take
AAU3940 (L1800+UL2100) as an example. Two pieces of Multi-Mode Multi-Band
License for Multi-Band RF Module (LTE FDD) and one piece of Multi-Mode
Multi-Band License for Multi-Band RF Module (UMTS) need to be allocated for
this RF module for LTE FDD and UMTS, respectively.
For 5000 series multi-band RF modules, an RAT-specific license and band license
are sold together. Additionally, the band license is sold only for LTE FDD and LTE
TDD, not for GSM, UMTS, and LTE NB-IoT. For a GU dual-band RF module for
example, one First Mode License for 5000 Series RF Module (GSM) and one
Multimode License for 5000 Series RF Module (UMTS) are required while no band
license is required. For GUL dual-band RF modules, there are two scenarios:
Issue Draft A (2019-01-05)
n
When LTE is applied only on one frequency band, the RF module requires one
First Mode License for 5000 Series RF Module (GSM), one Multimode
License for 5000 Series RF Module (UMTS), and one Multimode License for
5000 Series RF Module (FDD).
n
When LTE is applied on both frequency bands, the RF module requires one
First Mode License for 5000 Series RF Module (GSM), one Multimode
Copyright © Huawei Technologies Co., Ltd.
15
eRAN
License Management Feature Parameter Description
3 General Principles
License for 5000 Series RF Module (UMTS), one Multimode License for 5000
Series RF Module (FDD), and one Multi-band License for 5000 Series Multiband RF Module (FDD).
For 5000 series multi-band RF modules, the RFU, RRU, and AAU can share a
license.
(3) For a multi-band RRU3961, license control should be performed based on the
working RATs and operating bands of the RRU3961. If an RRU3961 is configured
to work in a single RAT, there is no need to purchase RF multimode licenses. If an
RRU3961 is configured with GSM 900 MHz and UMTS 900 MHz cells, the
operator needs to purchase an RF GSM/UMTS Dual Mode license. If an RRU3961
is configured with LTE 800 MHz and GSM or UMTS 900 MHz cells, the operator
needs to purchase the RF 800M/900M Multi Band license (FDD). If an RRU3961 is
configured with LTE FDD 800 MHz and LTE NB-IoT 800 MHz cells, the operator
needs to purchase the RF Multi-Mode license(NB-IoT). For example, if an
RRU3961 works in the GU900+L800 frequency bands, the operator needs to
purchase an RF GSM/UMTS Dual Mode license and an RF 800M/900M Multi
Band license.
(4) For a pRRU3901 of LampSite base stations, if an RF card is configured to work
in UL mode, the operator needs to purchase the LampSite UMTS/LTE(FDD) Dual
Mode license for Multi-Mode RF (Per RF card). This type of license is sold and
controlled in the more recent RAT (LTE FDD) of the two RATs. If an RF card is
configured to work in a single RAT (UO or LO), there is no need to purchase this
type of license.
(4) 3000 series pRRUs except the pRRU3901 have four licenses: LampSite First
Mode First Band License for Multi-Band RF Module(LTE FDD), LampSite MultiMode Multi-Band License for Multi-Band RF Module(LTE FDD), LampSite First
Mode First Band License for Multi-Band RF Module(UMTS), and LampSite MultiBand License for Multi-Band RF Module(UMTS). The sales means and usage of
the modules are the same as those of multi-band RF modules (except the RRU3961)
for macro base stations.
(6) For LampSite 5000 series pRRU modules [the modules in (4) and (5) are both
non-5000 series modules], only the mode license is sold.
If the module is working only for one RAT, the operator needs to purchase the firstmode license for this RAT. If the module is working for multiple RATs, each RAT
requires one mode license. Additionally, the lowest RAT uses a first-mode license
while the other RATs use multimode licenses. The descending order of RATs is as
follows: NB-IoT > LTE TDD > LTE FDD > UMTS. For example, if UMTS and
LTE work concurrently on an RRU, the First Mode License for 5000 Series RF
Module (UMTS) and Multimode License for 5000 Series RF Module (FDD) are
required.
(7) After 5000 series massive MIMO AAUs are introduced, 5000 series RF
modules are classified into the following types in terms of multimode license
control:
n
5000 series nTnR (sub-6G 8T8R or lower)
n
5000 series massive MIMO (sub-6G 16T16R or higher)
The consumption principles of the RAT license items and frequency band
license items are as follows:
n
Issue Draft A (2019-01-05)
For 5000 series nTnR (sub-6G 8T8R or lower), its license consumption is the
same as the original 5000 series RF license consumption.
Copyright © Huawei Technologies Co., Ltd.
16
eRAN
License Management Feature Parameter Description
n
3 General Principles
For 5000 series massive MIMO (sub-6G 16T16R or higher), its license
consumption is based on the new 5000 series massive MIMO RAT license
item and frequency band license item.
The RTU of 5000 series massive MIMO does not distinguish the first RAT from the
multiple RATs. Only one RAT license is defined, which is consumed in both singleRAT and multi-RAT scenarios.
Table 3-12 lists RF multimode license control items.
Table 3-12 RF multimode license control items
NE Type
Model
Description
NodeB
WDMS00GUDM00
RF GSM/UMTS Dual Mode
license
eNodeB
WDMS00GLDM00
GSM/LTE Dual Mode license
(FDD)
eNodeB
WDMS00GLDM01
GSM/LTE Dual Mode license for
Blade and AAU (FDD)
eNodeB
WDMS00ULDM00
UMTS/LTE Dual Mode license
(FDD)
eNodeB
WDMS00ULDM01
UMTS/LTE Dual Mode license for
Blade and AAU (FDD)
eNodeB
ML1S00RFDM00
RF Multi-Mode license(NB-IoT)
eNodeB
ML1S00RFDM01
RF Multi-Mode license for Blade
and AAU(NB-IoT)
eNodeB
WDMS0R89MB00
RF 800M/900M Multi Band
license(FDD)
eGBTS/GBTS
WDMSFMFBMBG0
First Mode First Band License for
Multi-Band RF Module (GSM)
WDMSMMMBMBG0
Multi-Mode Multi-Band License
for Multi-Band RF Module (GSM)
WDMSFMFBMBU0
First Mode First Band License for
Multi-Band RF Module (UMTS)
WDMSMMMBMBU0
Multi-Mode Multi-Band License
for Multi-Band RF Module
(UMTS)
WDMSFMFBMBL0
First Mode First Band License for
Multi-Band RF Module (LTE
FDD)
WDMSMMMBMBL0
Multi-Mode Multi-Band License
for Multi-Band RF Module (LTE
FDD)
NodeB
eNodeB
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
17
eRAN
License Management Feature Parameter Description
NE Type
Model
Description
eNodeB
ML1SFMFBMBM0
First Mode First Band License for
Multi-Band RF Module(NB-IoT)
ML1SMMMBMBM0
Multi-Mode Multi-Band License
for Multi-Band RF Module(NBIoT)
WD6SFMFBMBU00
LampSite First Mode First Band
License for Multi-Band RF
Module(UMTS)
WD6SMMBMBU00
LampSite Multi-Band License for
Multi-Band RF Module(UMTS)
WD6SFMFBMBL00
LampSite First Mode First Band
License for Multi-Band RF
Module(LTE FDD)
WD6SMMBMBL00
LampSite Multi-Mode Multi-Band
License for Multi-Band RF
Module(LTE FDD)
WD6SFMFBMBL01
LampSite First Mode First Band
License for Multi-Band RF(LTE
TDD)
WD6SMMBMBL01
LampSite Multi-Mode Multi-Band
License for Multi-Band RF(LTE
TDD)
NodeB/eNodeB
WD6S00ULDM00
LampSite UMTS/LTE(FDD) Dual
Mode license for Multi-Mode RF
(Per RF card)
eGBTS/GBTS
GMMS5000FMRR
First Mode License for 5000 Series
RF Module (GSM)
eGBTS/GBTS
GMMS5000MMRR
Multimode License for 5000
Series RF Module (GSM)
NodeB
WDMS5000FMRR
First Mode License for 5000 Series
RF Module (UMTS)
NodeB
WDMS5000MMRR
Multimode License for 5000
Series RF Module (UMTS)
eNodeB
LT1S5000FMRR
First Mode License for 5000 Series
RF Module (FDD)
eNodeB
LT1S5000MMRR
Multimode License for 5000
Series RF Module (FDD)
eNodeB
LT4SFM5TRR00
First Mode License for 5000 Series
RF Module (TDD)
NodeB
eNodeB
eNodeB
Issue Draft A (2019-01-05)
3 General Principles
Copyright © Huawei Technologies Co., Ltd.
18
eRAN
License Management Feature Parameter Description
Issue Draft A (2019-01-05)
3 General Principles
NE Type
Model
Description
eNodeB
LT4SMM5TRR00
Multimode License for 5000
Series RF Module (TDD)
eNodeB
ML1S5000FMRR
First Mode License for 5000 Series
RF Module (NB-IoT)
eNodeB
ML1S5000MMRR
Multimode License for 5000
Series RF Module (NB-IoT)
eNodeB
LT1S5000MMMR
Multi-band License for 5000
Series Multi-band RF Module
(FDD)
eNodeB
LT4SMB5SMR00
Multi-band License for 5000
Series Multi-band RF Module
(TDD)
eNodeB
LT1SFSTMOD00
First Mode License for 5000 Series
LampSite pRRU(FDD)
eNodeB
LT1SMUTMOD00
Multimode License for 5000
Series LampSite pRRU(FDD)
eNodeB
LT14FM5SPR00
First Mode License for 5000 Series
LampSite pRRU (TDD)
eNodeB
LT14MM5SPR00
Multimode License for 5000
Series LampSite pRRU (TDD)
NodeB
QWMSFSTMOD00
First Mode License for 5000 Series
LampSite pRRU (UMTS)
NodeB
QWMSMUTMOD00
Multimode License for 5000
Series LampSite pRRU(UMTS)
eNodeB
ML1SFMFBMN00
LampSite First Mode First Band
License for Multi-Band RF
Module(NB-IoT)
eNodeB
ML1SMMMBMN00
LampSite Multi-Mode Multi-Band
License for Multi-Band RF
Module(NB-IoT)
eNodeB
ML1SFMFBMN50
First Mode License for 5000 Series
LampSite pRRU(NB-IoT)
eNodeB
ML1SMMMBMN50
Multimode License for 5000
Series LampSite pRRU(NB-IoT)
eNodeB
LT1SMMRFMD00
Massive MIMO Multimode
License for 5000 Series RF
Module (FDD)
Copyright © Huawei Technologies Co., Ltd.
19
eRAN
License Management Feature Parameter Description
–
3 General Principles
NE Type
Model
Description
eNodeB
LT4SMULMM5RF
Massive MIMO Multimode
License for 5000 Series RF
Module (TDD)
eNodeB
ML1SMMRFMD00
Massive MIMO Multimode
License for 5000 Series RF
Module (NB-IoT)
eNodeB
LT1SMMMBMD00
Massive MIMO Multi-band
License for 5000 Series Multiband RF Module (FDD)
eNodeB
LT4SMMMBMD00
Massive MIMO Multi-band
License for 5000 Series Multiband RF Module (TDD)
UMPT multimode license: There is no need to purchase a UMPT multimode license
when the UMPT works in a single RAT. RAT extension for a base station requires
the license for the added RAT. When deploying a new multimode base station, the
operator needs to purchase licenses for the desired N-1 RATs (N indicates the total
number of RATs). For example, when GSM and UMTS coexist, the operator needs
to purchase a license either for GSM or UMTS; when GSM, UMTS, and LTE
coexist, the operator needs to purchase licenses for any two of the three RATs. If the
authorized value and usage value of this license control item as queried on the
eNodeB are 0 and 1, respectively, and ALM-26819 Data Configuration Exceeding
Licensed Limit is not reported, the usage value 1 indicates the default authorized
value when no license control item is present. This symptom is normal and you do
not need to handle this issue. Table 3-13 lists the UMPT multimode license control
items.
Table 3-13 UMPT multimode license control items
–
Issue Draft A (2019-01-05)
NE Type
Model
Description
eGBTS
WDMS0UMMG00
UMPT Multi Mode License(GSM)
NodeB
WDMS0UMMU00
UMPT Multi Mode
License(UMTS)
eNodeB
WDMS0UMML00
UMPT Multi Mode license(FDD)
eNodeB
LT1UMPTMMS00
UMPT Multi Mode license(LTE
TDD)
eNodeB
ML1SUMPTMM00
UMPT Multi Mode license(NBIoT)
UBBP multimode licenses: The UBBP is a multimode baseband processing unit,
but it can also be used for a single RAT. The UBBP requires the license for at least
one RAT. For GSM, UMTS, or LTE, UBBP multimode licenses are classified into
the UBBP First-Mode license and UBBP Multi-Mode license. When the UBBP
works for a single RAT, the operator needs to purchase only the UBBP First-Mode
Copyright © Huawei Technologies Co., Ltd.
20
eRAN
License Management Feature Parameter Description
3 General Principles
license for this RAT. RAT extension for a base station requires the license for the
added RAT. When deploying a new multimode base station, the operator needs to
purchase one UBBP First-Mode license and N-1 UBBP Multi-Mode licenses (N
indicates the total number of RATs).
For example, for a GUL (LTE FDD) triple-mode base station, the license purchase
scheme can be any of the following: 1. UBBP First-Mode license (GSM), UBBP
Multi-Mode license (UMTS), and UBBP Multi-Mode license (LTE FDD) 2. UBBP
First-Mode license (UMTS), UBBP Multi-Mode license (GSM), and UBBP MultiMode license (LTE FDD) 3. UBBP First-Mode license (LTE FDD), UBBP MultiMode license (GSM), and UBBP Multi-Mode license (UMTS). Table 3-14 lists
UBBP multimode license control items.
Table 3-14 UBBP multimode license control items
NE Type
Model
Description
eGBTS/GBTS
WDMS00UFMG00
UBBP First-Mode license (GSM)
WDMS00UMMG00
UBBP Multi-Mode license (GSM)
WDMS00UFMU00
UBBP First-Mode license (UMTS)
WDMS00UMMU00
UBBP Multi-Mode license
(UMTS)
WDMS0UFMLF00
UBBP First-Mode license (LTE
FDD)
WDMS0UMMLF00
UBBP Multi-Mode license (LTE
FDD)
LT1SUMMLFL01
UBBP First-Mode License(LTE
TDD)
LT1SUMMLFL00
UBBP Multi-Mode license(LTE
TDD)
ML1SUBBPFM00
UBBP First-Mode license(NBIoT)
ML1SUBBPMM00
UBBP Multi-Mode license(NBIoT)
NodeB
eNodeB
eNodeB
eNodeB
NOTE
The UMDU combines main control and baseband processing functionalities. Therefore, an
operator needs to purchase the corresponding UMPT Multi Mode licenses and UBBP MultiMode licenses.
–
RF spectrum sharing license control items: As shown in Table 3-15, non-5000
series RF modules and 5000 series RF modules consume different RF spectrum
sharing license control items, and RF modules of different RATs consume different
RF spectrum sharing license control items. The following uses 5000 series RF
modules as an example:
n
Issue Draft A (2019-01-05)
Scenario 1: If GSM cells enabling MRFD-130201 GSM and LTE Spectrum
Concurrency(GSM) are configured on 5000 series RF modules, the following
Copyright © Huawei Technologies Co., Ltd.
21
eRAN
License Management Feature Parameter Description
3 General Principles
license control item is required: Spectrum Sharing License for 5000 Series RF
Module (GSM).
n
Scenario 2: If LTE cells enabling MRFD-130221 GSM and LTE Spectrum
Concurrency (LTE FDD) are configured on 5000 series RF modules, the
following license control item is required: Spectrum Sharing License for 5000
Series RF Module (FDD).
n
Scenario 3: If both GSM cells with MRFD-130201 GSM and LTE Spectrum
Concurrency(GSM) enabled and LTE cells with MRFD-130221 GSM and LTE
Spectrum Concurrency (LTE FDD) enabled are configured on 5000 series RF
modules, the following license control items are required: Spectrum Sharing
License for 5000 Series RF Module (GSM) and Spectrum Sharing License for
5000 Series RF Module (FDD).
NOTE
For the same RF module, if spectrum sharing-related features are enabled on intra-RAT
multiband RF modules, a number of spectrum sharing license control items equal to the
frequency band quantity are consumed; if multiple spectrum sharing-related features are
enabled on intra-RAT intra-band RF modules, only one spectrum sharing license control
item is consumed.
The spectrum sharing features are as follows:
GSM: MRFD-130201 GSM and LTE Spectrum Concurrency (GSM)
LTE: MRFD-130221 GSM and LTE Spectrum Concurrency (LTE FDD)
Table 3-15 RF spectrum sharing license control items
–
NE Type
Model
Description
GBTS/eGBTS
LGMIRFSSL
RF Spectrum Sharing License
(GSM)
GBTS/eGBTS
LGMIRFSSLWY
Spectrum Sharing License for
5000 Series RF Module (GSM)
eNodeB
LT1SRFSPCS00
RF Spectrum Sharing License
(FDD)
eNodeB
LT1S5000RFSS
Spectrum Sharing License for
5000 Series RF Module (FDD)
Multi-Mode License for Micro BTS: As listed in Table 3-16, Multi-Mode License
for Micro BTS is classified into Multi-Band License and Multi-Mode License and
they are applicable only to LTE FDD and NB-IoT currently.
n
If a micro base station uses N frequency bands, the operator needs to purchase
N-1 multi-band licenses, either the Multi-Band License for Micro BTS(NBIoT) or the Multi-Band License for Micro BTS(FDD) or a combination of the
two license types.
n
If a micro base station works for N RATs on the same frequency band, the
operator needs to purchase N-1 multimode licenses, either the Multi-Mode
License for Micro BTS(NB-IoT) or the Multi-Mode License for Micro
BTS(FDD) or a combination of the two license types.
One RAT uses only one multimode license on a frequency band. The sale of multiband and multimode licenses is controlled according to the descending order of NBIoT, LTE FDD, and UMTS. Such licenses are not set for UMTS. For example:
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
22
eRAN
License Management Feature Parameter Description
3 General Principles
n
If UMTS and LTE FDD are deployed on separate frequency bands such as 2.1
GHz and 1.8 GHz on a module, the operator needs to purchase a Multi-Band
License for Micro BTS(FDD). If UMTS and LTE FDD are deployed on the
same frequency band such as 2.1 GHz on a module, the operator needs to
purchase a Multi-Mode License for Micro BTS(FDD).
n
If NB-IoT and LTE FDD are deployed on separate frequency bands such as 2.1
GHz and 1.8 GHz on a module, the operator needs to purchase a Multi-Band
License for Micro BTS(NB-IoT). If NB-IoT and LTE FDD are deployed on
the same frequency band such as 900 MHz on a module, the operator needs to
purchase a Multi-Mode License for Micro BTS(NB-IoT).
Table 3-16 Multimode license control items for micro base stations
NE Type
Feature Name
Model
Description
eNodeB
N/A
LT9S0MMLMB
00
Multi-Mode
License for
Micro
BTS(FDD)
N/A
LT9S0MBLMB
00
Multi-Band
License for
Micro
BTS(FDD)
N/A
LT9SMUTMOD
01
Multi-Mode
License for
Micro BTS(NBIoT)
N/A
LT9SMUTCAR
01
Multi-Band
License for
Micro BTS(NBIoT)
NOTE
If license control items First Mode First Band License for Multi-Band RF Module (LTE FDD) and
Multi-Mode Multi-Band License for Multi-Band RF Module (LTE FDD) are purchased, the licensed
values for the license control items are separately displayed in the Allocated column in the DSP
LICINFO command output, and the sum of configured values and the sum of actually used values for
the license control items are displayed in columns Config and Actual Used in the command output,
respectively.
The preceding mechanism also applies to UBBP First-Mode license (LTE FDD) and UBBP Multi-Mode
license (LTE FDD), First Mode First Band License for Multi-Band RF Module(NB-IoT) and MultiMode Multi-Band License for Multi-Band RF Module(NB-IoT), and UBBP First-Mode license(NBIoT) and UBBP Multi-Mode license(NB-IoT) in the DSP LICINFO command output.
Feature Items
Multimode feature license control items include all the feature license control items of the
separate RATs of a multimode base station. That is, if an operator wants to use features on a
multimode base station, the operator must purchase the feature license control items for each
RAT of the multimode base station. However, some features only need to be licensed in one
RAT for a multimode base station, as provided in Table 3-17.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
23
eRAN
License Management Feature Parameter Description
3 General Principles
Table 3-17 License control items required only in one RAT for a multimode base station
Feature Name
Feature ID and Name
Model
Intelligent
Battery
Management
GSM: GBFD-510710 Intelligent Battery
Management
GMISBATMGT00
UMTS: WRFD-140220 Intelligent
Battery Management
QWMS0IBATM01
LTE FDD: LOFD-001071 Intelligent
Battery Management
LT1S000IBM00
LTE FDD: TDLOFD-001071 Intelligent
Battery Management
LT1ST00IBM00
GSM: GBFD-111608 PSU Smart
Control
GMIS0PSUSC00
UMTS: WRFD-020121 Intelligent
Power Management
QWMSPSUISS00
LTE FDD: LOFD-001056 PSU
Intelligent Sleep Mode
LT1S00PISM00
LTE FDD: TDLOFD-001056 PSU
Intelligent Sleep Mode
LT1STPSUSM00
PSU Intelligent
Shutdown
3.2.4 Single-Mode Base Stations
3.2.4.1 LKFs for Single-Mode Base Stations
A single-mode base station refers to the LTE FDD/LTE NB-IoT/LTE TDD eNodeB.
The LKF is stored on the eNodeB, and the eNodeB implements functions such as loading,
controlling, querying, and verifying the LKF.
3.2.4.2 License Control Items for Single-Mode Base Stations (FDD)
License control items can be categorized into capacity items and feature items.
Capacity Items
An LTE only (LO) base station requires capacity-related license control items for LTE. If the
LO base station uses multi-band RF modules or UBBPs, the corresponding First Mode First
Band License for Multi-Band RF Module (LTE FDD) or UBBP First-Mode license (LTE
FDD) must also be purchased.
Table 3-18 describes LO capacity-related license control items. The Model and Description
columns map the information in the DSP LICINFO command output. where:
l
If no LKF is installed on an eNodeB, the amount of resources available for the eNodeB
is the "Default capacity" values listed in the table.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
24
eRAN
License Management Feature Parameter Description
l
3 General Principles
If an LKF is installed on the eNodeB:
–
For a license control item RF Output Power, BB Transmit Channel, BB Receive
Channel, RF Transmit Channel, or RF Receive Channel, the amount of resources
available for the eNodeB is the sum of the default capacity of that item and the
capacity provided by purchased license units.
–
For a license control item other than those listed above, the amount of resources
available for the eNodeB is the capacity provided by purchased license units.
Table 3-18 LTE FDD capacity-related license control items
Model
Description
Details
LT1S0000PA
00
RF Output Power
(FDD)
Function: controls the maximum power of RF
modules in an eNodeB.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units
of 20 W. One license unit is required for every 20 W
except for the default 20 W power per RF module.
The number of license units to be purchased for a
cell is determined by the cell power.
Total capacity: Maximum power of an eNodeB =
(Number of RF modules + Number of purchased
license units) x 20 W
LT1S005MH
Z00
Carrier Bandwidth
- 0~5MHz(FDD)
Function: controls the 0–5 MHz carrier bandwidth
capability of RF modules.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 5 MHz
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 0–5
MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 0–5 MHz carrier
bandwidth available for an eNodeB = Number of
purchased license units x 5 MHz
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
25
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S010MH
Z00
Carrier Bandwidth
- 5~10MHz(FDD)
Function: controls the 5–10 MHz carrier
bandwidth capability of RF modules.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 5–
10 MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 5–10 MHz carrier
bandwidth available for an eNodeB = Number of
purchased license units x 5 MHz
LT1S015MH
Z00
Carrier Bandwidth
10~15MHz(FDD)
Function: controls the 10–15 MHz carrier
bandwidth capability of RF modules.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 10–
15 MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 10–15 MHz
carrier bandwidth available for an eNodeB =
Number of purchased license units x 5 MHz
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
26
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S020MH
Z00
Carrier Bandwidth
15~20MHz(FDD)
Function: controls the 15–20 MHz carrier
bandwidth capability of RF modules.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 15–
20 MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 15–20 MHz
carrier bandwidth available for an eNodeB =
Number of purchased license units x 5 MHz
NOTE
The following are the principles for applying for carrier
bandwidth license units:
1. If the cell bandwidth is 5 MHz or less, apply for one unit
of Carrier Bandwidth - 0~5MHz (FDD).
2. If the cell bandwidth is 10 MHz, apply for one unit of
Carrier Bandwidth - 0~5MHz (FDD) and one unit of
Carrier Bandwidth - 5~10MHz (FDD).
3. If the cell bandwidth is 15 MHz, apply for one unit of
Carrier Bandwidth - 0~5MHz (FDD), one unit of Carrier
Bandwidth - 5~10MHz (FDD), and one unit of Carrier
Bandwidth - 10~15MHz (FDD).
4. If the cell bandwidth is 20 MHz, apply for one unit of
Carrier Bandwidth - 0~5MHz (FDD), one unit of Carrier
Bandwidth - 5~10MHz (FDD), one unit of Carrier
Bandwidth - 10~15MHz (FDD), and one unit of Carrier
Bandwidth - 15~20MHz (FDD).
LT1S00BBT
C00
BB Transmit
Channel (FDD)
Function: controls the logical baseband TX channel
capability of baseband processing units.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two baseband TX channels per
cell on each BBP
Licensing principles: One license unit is required
for each baseband TX channel except the two default
baseband TX channels per cell.
Total capacity: Number of baseband TX channels
provided by an eNodeB = Number of cells served by
the eNodeB x 2 + Number of purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
27
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S00BBR
C00
BB Receive
Channel (FDD)
Function: controls the logical baseband RX channel
capability of baseband processing units.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two baseband RX channels per
cell on each BBP
Licensing principles: One license unit is required
for each baseband RX channel except for the two
default baseband RX channels per cell.
Total capacity: Number of baseband RX channels
provided by an eNodeB = Number of cells served by
the eNodeB x 2 + Number of purchased license units
LT1S00RFTC
00
RF Transmit
Channel (FDD)
Function: controls the physical transmit (TX)
channel capability of RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF TX channels per RF
module
Licensing principles: One license unit is required
for each RF TX channel except for the two default
RF TX channels per RF module.
NOTE
The number of license units required for RF TX channels
of an RF module serving a cell is dependent on the sector
equipment configuration and not dependent on the number
of antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
Total capacity: Number of RF TX channels
provided by an eNodeB = Number of RF modules x
2 + Number of purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
28
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S00RFRC
00
RF Receive
Channel (FDD)
Function: controls the physical receive (RX)
channel capability of RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF RX channels per RF
module
Licensing principles: One license unit is required
for each RF RX channel except for the two default
RF RX channels per RF module.
NOTE
The number of license units for RF RX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF RX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
Total capacity: Number of RF RX channels
provided by an eNodeB = Number of RF modules x
2 + Number of purchased license units
NOTE
For macro eNodeBs, the following are examples of
applying for baseband or RF TX/RX channel license
units:
1. If two 4T4R RF modules serve three 2T2R cells, the RF
module serving two cells requires two RF TX channel
license units and two RF RX channel license units, and the
RF module serving one cell does not require RF TX/RX
channel license units. None of the cells require baseband
TX/RX channel license units.
2. If a 4T4R RF module serves two 2T2R cells, the RF
module requires two RF TX channel license units and two
RF RX channel license units. The cells do not require
baseband TX/RX channel license units.
3. If a 4T4R RF module serves only one 2T2R cell, the RF
module does not require RF TX/RX channel license units,
and the cell does not require baseband TX/RX channel
license units.
4. If six 2T2R RF modules serve three 4T4R cells, the RF
modules do not require RF TX/RX channel license units,
but the cells require six baseband TX channel license units
and six baseband RX channel license units.
For multi-carrier scenarios:
If an RF module bears multiple carriers, the cells for the
carriers must be mapped to the same set of sector
equipment. In this way, the eNodeB can correctly consume
RF TX and RX channel license units.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
29
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S000MC
A00
RF Multi
Carrier(FDD)
Function: controls the multi-carrier capability of RF
modules.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: An RF module operates with only
one carrier and does not support multiple carriers by
default.
Licensing principles: One license unit is required
for each carrier except for the default carrier per RF
module. The number of license units required for an
RF module is equal to the total number of carriers on
the RF module minus 1.
Total capacity: Number of carriers except for the
default carrier per RF module available for an
eNodeB = Number of purchased license units
NOTE
For an RF module with the TX/RX mode of 8T8R or
higher, the first carrier of each RF module requires no
license unit while the other carriers of the RF module
require license units. For an RF module with the TX/RX
mode lower than 8T8R, the first carrier for each sector
equipment of each RF module requires no license unit
while the other carriers require license units.
LT1SFDMCL
L00
LTE FDD MultiCarrier License for
LampSite pRRU
(FDD)
Function: controls the multi-carrier capability of the
pRRU on a frequency band.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: A pRRU operates with only one
carrier and does not support multiple carriers on
each frequency band by default.
Licensing principles: One license unit is required
for each carrier on a frequency band except for the
default carrier of a pRRU. The number of license
units required for a frequency band of a pRRU is
equal to the total number of carriers on the
frequency band of the pRRU minus 1.
Total capacity: Number of carriers except for the
default carrier per RF module available for an
eNodeB = Number of purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
30
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S0000PA
01
RF Output Power
for Blade and
AAU (FDD)
Function: controls the maximum power of blade
remote radio units (RRUs) and active antenna units
(AAUs) in an eNodeB. (RF modules in this row
refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units
of 20 W. One license unit is required for every 20 W
except for the default 20 W power per RF module.
The number of license units to be purchased for a
cell is determined by the cell power.
Total capacity: Maximum power of an eNodeB =
(Number of RF modules + Number of purchased
license units) x 20 W
LT1S005MH
Z01
Carrier Bandwidth
- 0~5MHz for
Blade and AAU
(FDD)
Function: controls the 0–5 MHz carrier bandwidth
capability of blade RRUs and AAUs. (RF modules
in this row refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 5 MHz
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 0–5
MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 0–5 MHz carrier
bandwidth available for an eNodeB = Number of
purchased license units x 5 MHz
LT1S010MH
Z01
Carrier Bandwidth
- 5~10MHz for
Blade and AAU
(FDD)
Function: controls the 5–10 MHz carrier
bandwidth capability of blade RRUs and AAUs. (RF
modules in this row refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 5–
10 MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 5–10 MHz carrier
bandwidth available for an eNodeB = Number of
purchased license units x 5 MHz
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
31
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S015MH
Z01
Carrier Bandwidth
- 10~15MHz for
Blade and AAU
(FDD)
Function: controls the 10–15 MHz carrier
bandwidth capability of blade RRUs and AAUs. (RF
modules in this row refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 10–
15 MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 10–15 MHz
carrier bandwidth available for an eNodeB =
Number of purchased license units x 5 MHz
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
32
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S020MH
Z01
Carrier Bandwidth
- 15~20MHz for
Blade and AAU
(FDD)
Function: controls the 15–20 MHz carrier
bandwidth capability of blade RRUs and AAUs. (RF
modules in this row refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
each 5 MHz unit. The number of license units to be
purchased is determined by the total amount of 15–
20 MHz carrier bandwidth units required by an
eNodeB.
Total capacity: Total amount of 15–20 MHz
carrier bandwidth available for an eNodeB =
Number of purchased license units x 5 MHz
NOTE
The following are the principles for applying for carrier
bandwidth license units:
1. If the cell bandwidth is 5 MHz or less, apply for one unit
of Carrier Bandwidth - 0~5MHz for Blade and AAU
(FDD).
2. If the cell bandwidth is 10 MHz, apply for one unit of
Carrier Bandwidth - 0~5MHz for Blade and AAU (FDD)
and one unit of Carrier Bandwidth - 5~10MHz for Blade
and AAU (FDD).
3. If the cell bandwidth is 15 MHz, apply for one unit of
Carrier Bandwidth - 0~5MHz for Blade and AAU (FDD),
one unit of Carrier Bandwidth - 5~10MHz for Blade and
AAU (FDD), and one unit of Carrier Bandwidth 10~15MHz for Blade and AAU (FDD).
4. If the cell bandwidth is 20 MHz, apply for one unit of
Carrier Bandwidth - 0~5MHz for Blade and AAU (FDD),
one unit of Carrier Bandwidth - 5~10MHz for Blade and
AAU (FDD), one unit of Carrier Bandwidth - 10~15MHz
for Blade and AAU (FDD), and one unit of Carrier
Bandwidth - 15~20MHz for Blade and AAU (FDD).
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
33
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S00RFTC
01
RF Transmit
Channel for Blade
and AAU (FDD)
Function: controls the physical TX channel
capability of blade RRUs and AAUs. (RF modules
in this row refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF TX channels per RF
module
Licensing principles: One license unit is required
for each RF TX channel except for the two default
RF TX channels per RF module.
NOTE
The number of license units for RF TX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF TX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
Total capacity: Number of RF TX channels
provided by an eNodeB = Number of RF modules x
2 + Number of purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
34
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S00RFRC
01
RF Receive
Channel for Blade
and AAU (FDD)
Function: controls the physical RX channel
capability of blade RRUs and AAUs. (RF modules
in this row refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF RX channels per RF
module
Licensing principles: One license unit is required
for each RF RX channel except for the two default
RF RX channels per RF module.
NOTE
The number of license units for RF RX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF RX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
Total capacity: Number of RF RX channels
provided by an eNodeB = Number of RF modules x
2 + Number of purchased license units
NOTE
The following are examples of applying for baseband or
RF TX/RX channel license units:
1. If two 4T4R RF modules serve three 2T2R cells, the RF
module serving two cells requires two RF TX channel
license units and two RF RX channel license units, and the
RF module serving one cell does not require RF TX/RX
channel license units. None of the cells require baseband
TX/RX channel license units.
2. If a 4T4R RF module serves two 2T2R cells, the RF
module requires two RF TX channel license units and two
RF RX channel license units. The cells do not require
baseband TX/RX channel license units.
3. If a 4T4R RF module serves only one 2T2R cell, the RF
module does not require RF TX/RX channel license units,
and the cell does not require baseband TX/RX channel
license units.
4. If six 2T2R RF modules serve three 4T4R cells, the RF
modules do not require RF TX/RX channel license units,
but the cells require six baseband TX channel license units
and six baseband RX channel license units.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
35
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S000MC
A01
RF Multi Carrier
for Blade and
AAU (FDD)
Function: controls the multi-carrier capability of
blade RRUs and AAUs. (RF modules in this row
refer to blade RRUs and AAUs.)
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: An RF module operates with only
one carrier and does not support multiple carriers by
default.
Licensing principles: One license unit is required
for each carrier except for the default carrier per RF
module. The number of license units required for an
RF module is equal to the total number of carriers on
the RF module minus 1.
Total capacity: Number of carriers except for the
default carrier per RF module available for an
eNodeB = Number of purchased license units
NOTE
For an RF module with the TX/RX mode of 8T8R or
higher, the first carrier of each RF module requires no
license unit while the other carriers of the RF module
require license units. For an RF module with the TX/RX
mode lower than 8T8R, the first carrier for each sector
equipment of each RF module requires no license unit
while the other carriers require license units.
LT1S0ACTU
S00
RRC Connected
User (FDD)
Function: controls the number of
RRC_CONNECTED UEs on baseband processing
units in an eNodeB.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: six RRC_CONNECTED UEs
Licensing principles: One license unit is required
for each RRC_CONNECTED UE. The number of
license units to be purchased is equal to the
maximum number of RRC_CONNECTED UEs to
be served by an eNodeB.
Total capacity: Maximum number of
RRC_CONNECTED UEs to be served by an
eNodeB = Number of purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
36
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S0THRO
U00
Throughput
Capacity (FDD)
Function: controls the application-layer data rate on
the user plane of an eNodeB. This rate is measured
based on Packet Data Convergence Protocol (PDCP)
and GPRS Tunneling Protocol for User Plane (GTPU) payload.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 5 Mbit/s
Licensing principles: One license unit is required
for each 1 Mbit/s. The number of license units to be
purchased is determined by the sum of uplink and
downlink data rates of an eNodeB.
Admission control: Admission control on a new
service is performed based on its uplink and
downlink load measured by the throughput license
algorithm. If the new service's load measured by the
throughput license algorithm plus existing services'
load measured by the throughput license algorithm
exceeds the licensed throughput of the eNodeB
(LT1S0THROU00), the eNodeB rejects the service
admission request.
Overload control: Overload control is performed
based on the existing services' uplink and downlink
load measured by the throughput license algorithm.
If the existing services' uplink and downlink load
measured by the throughput license algorithm
exceeds the licensed throughput of the eNodeB, the
eNodeB preferentially releases low-priority services
whose ARP IE Pre-emption Vulnerability is set to
pre-emptable. This helps ensure the quality of highpriority services.
The load measured by the throughput license
algorithm is calculated as follows:
l Flow-control services:
Admitted and new services: (GBR or MinGBR) x
activity factor
l Non-flow-control services
– Admitted service: actual throughput
– New service: (GBR or MinGBR) x activity
factor
Flow-control and non-flow-control services are
configured by QciPara.FlowCtrlType, uplink
MinGBR is configured by QciPara.UlMinGbr,
downlink MinGBR is configured by
QciPara.DlMinGbr, and the activity factor is
configured by UDTPARAGRP.ACTFACTOR. If no
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
37
eRAN
License Management Feature Parameter Description
Model
Description
3 General Principles
Details
activity factor is configured, the default value 0%
takes effect.
Reconfiguring the MinGBR or activity factor
impacts service admission based on the throughput
license. A smaller value of the MinGBR or activity
factor indicates a smaller minimum guaranteed bit
rate for services with the corresponding QCI and
results in a lower load measured by the license
throughput algorithm; however, the number of
services that can be admitted increases when the
licensed throughput capacity of the eNodeB is
limited. A larger parameter value results in the
opposite effects.
NOTE
The token bucket algorithm is used to control traffic. The
licensed data rate is the rate at which tokens are injected
into a token bucket. Operators can define the ratio of
licensed uplink or downlink traffic to the total licensed
traffic by running the MOD LICRATIO command. The
UpLicRatio parameter of this command specifies the
percentage of licensed uplink traffic. According to the
algorithm, the token bucket size is determined by the token
injection rate and the token measurement period, which is
a fixed value of 1800 seconds. If there are sufficient tokens
in the bucket, the eNodeB processes data normally;
otherwise, the eNodeB starts to control traffic, which
affects data processing.
This algorithm is adopted because the traffic volume
fluctuates between peak and off-peak hours. To smooth the
traffic burr (instantaneous peak rate) for a single eNodeB
and to efficiently utilize the traffic capacity during off-peak
hours, the traffic capacity for a maximum of 1800 seconds
in off-peak hours can be accumulated for use in peak
hours.
For example:
In the first 1800-second period, the eNodeB has no traffic,
and the traffic capacity of 9000 megabits (5 Mbit/s x
1800s) is accumulated. A UE accesses the network at the
1801st second. The data rate of the UE is maintained at 10
Mbit/s, which is twice the licensed 5 Mbit/s. This burst
time can last throughout the second 1800-second period.
During the third period, the data rate of the UE is
maintained at 5 Mbit/s and the service is not interrupted.
Total capacity: Total throughput of an eNodeB =
Number of purchased license units x 1 Mbit/s
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
38
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S0000RB
00
Resource Block
(FDD)
Function: controls the number of resource blocks
(RBs) in the frequency domain within the carrier
bandwidth of cells served by an eNodeB.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 25 RBs, which correspond to a
bandwidth of 5 MHz
Licensing principles: One license unit is required
for each RB. The number of license units to be
purchased is determined by cell bandwidths. The
following is the mapping between carrier
bandwidths and the number of RBs:
l 1.4 MHz: 6 RBs
l 3 MHz: 15 RBs
l 5 MHz: 25 RBs
l 10 MHz: 50 RBs
l 15 MHz: 75 RBs
l 20 MHz: 100 RBs
Total capacity: Number of RBs within the
bandwidth of cells served by an eNodeB = Number
of purchased license units
LT1S0BASIC
15
eNodeB FDD
Basic Software,
V100R015(FDD)
Function: controls the number of cells that can be
activated in an eNodeB.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: one cell
Licensing principles: One license unit is required
for each activated cell. The number of license units
to be purchased is equal to the number of cells that
must be activated in an eNodeB.
Total capacity: Number of cells that can be
activated in an eNodeB = Number of purchased
license units
LT1S0POW5
R00
20W Power
License for 5000
Series RF Module
(FDD)
Function: controls the maximum power of 5000
series RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units
of 20 W. One license unit is required for every 20 W
except for the default 20 W power per RF module.
The number of license units to be purchased for a
cell is determined by the cell power.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
39
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S00BW5
R00
5MHz Cell
Bandwidth
License for 5000
Series RF Module
(FDD)
Function: controls the 5 MHz bandwidth capability
of 5000 series RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 5 MHz per cell
Licensing principles: One license unit is required
for each 5 MHz carrier of an eNodeB.
LT1SRFTC5
R00
Transmit Channel
License for 5000
Series RF Module
(FDD)
Function: controls the physical TX channel
capability of 5000 series RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF TX channels per RF
module
Licensing principles: One license unit is required
for each RF TX channel except for the two default
RF TX channels per RF module.
NOTE
The number of license units for RF TX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF TX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
LT1SRFRC5
R00
Receive Channel
License for 5000
Series RF Module
(FDD)
Function: controls the physical RX channel
capability of 5000 series RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF RX channels per RF
module
Licensing principles: One license unit is required
for each RF RX channel except for the two default
RF RX channels per RF module.
NOTE
The number of license units for RF RX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF RX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
40
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1SMUCA5
R00
Multi-carrier
License for 5000
Series RF Module
(FDD)
Function: controls the multi-carrier capability of
5000 series RF modules.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: An RF module operates with only
one carrier and does not support multiple carriers by
default.
Licensing principles: One license unit is required
for each carrier except for the default carrier per RF
module. The number of license units required for an
RF module is equal to the total number of carriers on
the RF module minus 1.
LT1SEMTCB
S15
eNodeB eMTC
Basic Software,
V100R015
Function: Controls the number of eMTC-only cells
that can be activated. The sales unit is per eMTConly cell.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Licensing principles: One license unit is required
when an eMTC-only cell is activated.
LT1SEMUSE
R00
eMTC User(FDD)
Function: Controls the number of eMTC UEs
camping on a cell. The sales unit is per 100 eMTC
UEs.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Licensing principles: One license unit is required
for 100 eMTC UEs.
LT1SEMBHC
A00
eMTC
BHCA(FDD)
Function: controls the number of times that the
eNodeB provides access for eMTC UEs per hour.
The sales unit is 100 BHCAs.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 1
Licensing principles: One license unit is required
when eMTC UEs successfully access the eNodeB
100 times within one hour. The operator needs to
purchase license units based on the maximum
number of times that eMTC UEs might access an
eNodeB within one hour.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
41
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1SEMBDC
A00
eMTC
BDCA(FDD)
Function: controls the number of times that the
eNodeB provides access for eMTC UEs every 24
hours. The sales unit is 1000 BDCAs.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 1
Licensing principles: One license unit is required
when eMTC UEs successfully access the eNodeB
1000 times within 24 hours. The operator needs to
purchase license units based on the maximum
number of times that eMTC UEs might access an
eNodeB within 24 hours.
LT1SFD5MH
Z00
5MHz Bandwidth
License for 5000
Series LampSite
pRRU(FDD)
Function: controls the 5 MHz bandwidth capability
of 5000 series LampSite pRRUs.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: None. No bandwidth is provided
to the pRRU for free by default.
Licensing principles: The bandwidth is licensed in
units of 5 MHz. The number of license units to be
purchased is determined by the total pRRU
bandwidth required by an eNodeB.
Total capacity: Total amount of 5 MHz bandwidth
available for an eNodeB = Number of purchased
license units x 5 MHz
LT1SMMBB
16T0
Massive MIMO
BB 16-Transmit
Channel Group
License(FDD)
Function: controls the logical TX channel capability
of massive MIMO BBPs.
Default capacity: 16 baseband TX channels per cell
on each BBP
Licensing principles: One license unit is required
for every 16 baseband TX channels except the 16
default baseband TX channels per cell on each BBP.
Total capacity: Number of baseband TX channels
provided by an eNodeB = Number of cells on the
eNodeB x 16 + Number of purchased license units x
16
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
42
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1SMMBB
16R0
Massive MIMO
BB 16-Receive
Channel Group
License(FDD)
Function: controls the logical RX channel capability
of massive MIMO BBPs.
Default capacity: 16 baseband RX channels per cell
on each BBP
Licensing principles: One license unit is required
for every 16 baseband RX channels except the 16
default baseband RX channels per cell on each BBP.
Total capacity: Number of baseband RX channels
provided by an eNodeB = Number of cells on the
eNodeB x 16 + Number of purchased license units x
16
LT1SMMRF1
6T0
Massive MIMO
RF 16-Transmit
Channel Group
License for 5000
Series(FDD)
Function: Controls the physical TX channel
capability of 5000 series massive MIMO RF
modules.
Default capacity: 16 RF TX channels per RF
module
Licensing principles: One license unit is required
for every 16 RF TX channels except the 16 default
RF TX channels per RF module.
LT1SMMRF1
6R0
Massive MIMO
RF 16-Receive
Channel Group
License for 5000
Series(FDD)
Function: Controls the physical RX channel
capability of 5000 series massive MIMO RF
modules.
Default capacity: 16 RF RX channels per RF
module
Licensing principles: One license unit is required
for every 16 RF RX channels except the 16 default
RF RX channels per RF module.
LT1S0MM20
P00
LT1S0MM5C
B00
Issue Draft A (2019-01-05)
Massive MIMO
20W Power
License for 5000
Series RF
Module(FDD)
Function: Controls the maximum power of 5000
series massive MIMO RF modules.
Massive MIMO
5MHz Cell
Bandwidth
License for 5000
Series RF
Module(FDD)
Function: Controls the 5 MHz bandwidth capability
of 5000 series massive MIMO RF modules.
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units
of 20 W. One license unit is required for every 20 W
except for the default 20 W power per RF module.
The number of license units to be purchased for a
cell is determined by the cell power.
Default capacity: none
Licensing principles: Carrier bandwidth is licensed
in units of 5 MHz. One license unit is required for
every 5 MHz bandwidth unit. The number of license
units to be purchased is determined by the total
number of 5 MHz carrier bandwidth units required
by an eNodeB.
Copyright © Huawei Technologies Co., Ltd.
43
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
LT1S00MM
MC00
Massive MIMO
Multi-carrier
License for 5000
Series RF
Module(FDD)
Function: controls the multi-carrier capability of
5000 series massive MIMO RF modules.
Default capacity: An RF module operates with only
one carrier and does not support multiple carriers by
default.
Licensing principles: One license unit is required
for each carrier except for the default carrier per RF
module. The number of license units required for an
RF module is equal to the total number of carriers on
the RF module minus 1.
LT1SMMDL
2EPU
Massive MIMO
DL 2-Layers
Extended
Processing Unit
License(FDD)
Function: controls the downlink TM9 multi-layer
transmission capability of BBPs of FDD massive
MIMO cells.
Default capacity: none
Licensing principles: Apply for the number of
license units based on the total number of downlink
layers in the massive MIMO cells on each BBP. One
license unit is required for every two layers in the
massive MIMO cells on each BBP.
Number of license units to be purchased for a cell =
Number of downlink layers in the cell / 2
The total number of license units purchased for an
eNodeB must not exceed the maximum multi-layer
transmission capability of a BBP.
NOTE
If an operator purchases both common RF modules and blade RRUs and AAUs, there is no license
control differentiation on these two types of hardware. In the output of the DSP LICINFO command,
the licensed values for the two types of hardware are separately displayed in the Allocated column, and
the sum of configured values and sum of actually used values for the license control items of the two
types of hardware are displayed in columns Config and Actual Used.
As different from common cells, licensed-assisted access (LAA) cells consume capacity
license units only for LAA cells (see Table 3-19 for details) and do not consume capacity
license units for common cells.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
44
eRAN
License Management Feature Parameter Description
3 General Principles
Table 3-19 Capacity license control items for LAA cells
Model
Description
Details
LT1SFDDBSC0
1
eNodeB Basic
Software -U,
V100R013
Function: controls the number of LAA cells that
can be activated in an eNodeB.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: one LAA cell
Licensing principles: One license unit is required
for each activated LAA cell. The number of license
units to be purchased is equal to the number of LAA
cells that must be activated in an eNodeB.
Total capacity: Number of LAA cells that can be
activated in an eNodeB = Number of purchased
license units
WD6SMUTCA
R00
LTE MultiCarrier License
for LampSite
pRRU -U
Function: controls the multi-carrier capability of the
pRRU for LAA cells.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: A pRRU supports one carrier and
does not support multiple carriers for an LAA cell
by default.
Licensing principles: One license unit is required
for each LAA carrier except for the default LAA
carrier per pRRU. The number of license units to be
purchased for a pRRU is equal to the number of
LAA carriers on the pRRU minus one.
Total capacity: Number of LAA carriers except for
the default LAA carrier per pRRU available for an
eNodeB = Number of purchased license units
WD6STCMBPS
00
LTE
Throughput
Capacity for
LampSite
pRRU -U
Function: controls the application-layer data rate of
all LAA cells served by an eNodeB on the user
plane.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 5 Mbit/s
Licensing principles: One license unit is required
for each 1 Mbit/s. The number of license units to be
purchased is determined by the sum of uplink and
downlink data rates of the LAA cells served by an
eNodeB.
Total capacity: Total throughput of an eNodeB =
Number of purchased license units x 1 Mbit/s
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
45
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
WD6SMBRFM
U00
LampSite
Multi-Mode
Multi-Band
License for
Multi-Band RF
Module -U
Function: controls the number of frequency bands
available for an RF module of an LAA cell.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: One license unit is required
for each operating band of an LAA cell on each RF
module.
Total capacity: Number of operating bands used by
LAA cells on RF modules of an eNodeB = Number
of purchased license units
Table 3-20 describes LTE NB-IoT capacity-related license control items.
Table 3-20 LTE NB-IoT capacity-related license control items
Model
Description
Details
ML1S0000PA00
RF Output
Power(NB-IoT)
Function: controls the maximum power of RF
modules in an eNodeB working in NB-IoT mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 20 W per RF module in NB-IoT
mode
Licensing principles: RF power is licensed in units
of 20 W in NB-IoT mode. One license unit is
required for every 20 W except for the default 20 W
power per RF module. The number of license units
to be purchased for a cell is determined by the cell
power.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
46
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
ML1S00RFTC0
0
RF Transmit
Power(NB-IoT)
Function: controls the physical transmit (TX)
channel capability of RF modules in NB-IoT mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF TX channels per RF
module in NB-IoT mode
Licensing principles: One license unit is required
for each RF TX channel except for the two default
RF TX channels per RF module in NB-IoT mode.
NOTE
The number of license units for RF TX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF TX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
ML1S00RFRC0
0
RF Receive
Channel(NBIoT)
Function: controls the physical receive (RX)
channel capability of RF modules in NB-IoT mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF RX channels per RF
module in NB-IoT mode
Licensing principles: One license unit is required
for each RF RX channel except for the two default
RF RX channels per RF module in NB-IoT mode.
NOTE
The number of license units for RF RX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF RX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
ML1S000MCA0
0
RF Multi
Carrier(NBIoT)
Function: controls the multi-carrier capability of RF
modules in NB-IoT mode.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: An RF module operates with only
one carrier and does not support multiple carriers in
NB-IoT mode by default.
Licensing principles: One license unit is required
for each carrier except for the default carrier per RF
module in NB-IoT mode. The number of license
units required for an RF module is equal to the total
number of carriers on the RF module minus 1.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
47
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
ML1S0000PA01
RF Output
Power for Blade
and AAU(NBIoT)
See the related description of the RF Output
Power(NB-IoT) license control item.
ML1S00RFTC0
1
RF Transmit
Channel for
Blade and
AAU(NB-IoT)
See the related description of the RF Transmit
Channel(NB-IoT) license control item.
ML1S00RFRC0
1
RF Receive
Channel for
Blade and
AAU(NB-IoT)
See the related description of the RF Receive
Channel(NB-IoT) license control item.
ML1S000MCA0
1
RF Multi
Carrier for
Blade and
AAU(NB-IoT)
See the related description of the RF Multi
Carrier(NB-IoT) license control item.
ML1S0LBBPM0
0
LBBP NB-IoT
license(NB-IoT)
Function: controls the LBBP capability for NB-IoT.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: One license unit is required
for each LBBP supporting NB-IoT.
ML1S00LMMM
00
LMPT NB-IoT
license(NB-IoT)
Function: controls the LMPT capability for NBIoT.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: One license unit is required
for the primary LMPT on the eNodeB to support
NB-IoT.
ML1SUMPTM
M00
UMPT Multi
Mode
license(NB-IoT)
Function: controls the UMPT capability for NBIoT.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: none
Licensing principles: One license unit is required
for the primary UMPT on the eNodeB to support
NB-IoT.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
48
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
ML1S00BHCA0
0
NB-IoT
BHCA(NB-IoT)
Function: controls the number of times that the
eNodeB provides access for NB-IoT UEs per hour.
The sales unit is 100 BHCAs.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 1
Licensing principles: One license unit is required
when NB-IoT UEs successfully access the eNodeB
100 times within one hour. The operator needs to
purchase license units based on the maximum
number of times that NB-IoT UEs might access an
eNodeB within one hour.
ML1S00BDCA0
0
NB-IoT
BDCA(NB-IoT)
Function: controls the number of times that the
eNodeB provides access for NB-IoT UEs every 24
hours. The sales unit is 1000 BDCAs.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 1
Licensing principles: One license unit is required
when NB-IoT UEs successfully access the eNodeB
1000 times within 24 hours. The operator needs to
purchase license units based on the maximum
number of times that NB-IoT UEs might access an
eNodeB within 24 hours.
ML1S00CELL0
0
NB-IoT
Carrier(NBIoT)
Function: controls the number of 200 kHz NB-IoT
carriers supported by the baseband processing unit.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: one carrier
Licensing principles: One license unit is required
for each NB-IoT carrier.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
49
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
ML1S00BBRC0
0
BB Receive
Channel(NBIoT)
Function: controls the logical baseband RX channel
capability of baseband processing units for NB-IoT
cells.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two baseband RX channels per
NB-IoT cell on each baseband processing unit
Licensing principles: One license unit is required
for each baseband RX channel except for the two
default baseband RX channels per NB-IoT cell.
Total capacity: Number of baseband RX channels
provided by an eNodeB for NB-IoT cells = Number
of NB-IoT cells served by the eNodeB x 2 +
Number of purchased license units
ML1S0ATCUS0
0
NB-IoT
User(NB-IoT)
Function: controls the number of NB-IoT UEs for
which the eNodeB has saved their contexts. The
sales unit is 100 NB-IoT UEs.
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Default capacity: 1
Licensing principles: One license unit is required
when the eNodeB successfully saves the contexts of
100 NB-IoT UEs. The number of required license
units is determined by the maximum number of NBIoT UEs for which the eNodeB can save their
contexts.
ML1S0BASIC1
5
eNodeB NBIoT Basic
Software,
V100R015(NBIoT)
Function: controls the number of NB-IoT cells that
can be activated in an eNodeB.
Default capacity: one cell
Applicable eNodeBs: 3900 series base stations,
5900 series base stations, BTS3911E, BTS3912E
Licensing principles: One license unit is required
for each activated NB-IoT cell. The number of
license units to be purchased is equal to the number
of NB-IoT cells that must be activated in an
eNodeB.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
50
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
ML1S0POW5R0
0
20W Power
License for
5000 Series RF
Module (NBIoT)
Function: controls the maximum power of 5000
series RF modules in NB-IoT mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: 20 W per RF module in NB-IoT
mode
Licensing principles: RF power is licensed in units
of 20 W in NB-IoT mode. One license unit is
required for every 20 W except for the default 20 W
power per RF module. The number of license units
to be purchased for a cell is determined by the cell
power.
ML1SRFTC5R0
0
Transmit
Channel
License for
5000 Series RF
Module (NBIoT)
Function: controls the physical TX channel
capability of 5000 series RF modules in NB-IoT
mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF TX channels per RF
module in NB-IoT mode
Licensing principles: One license unit is required
for each RF TX channel except for the two default
RF TX channels per RF module in NB-IoT mode.
NOTE
The number of license units for RF TX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF TX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
ML1SRFRC5R0
0
Receive
Channel
License for
5000 Series RF
Module (NBIoT)
Function: controls the physical RX channel
capability of 5000 series RF modules in NB-IoT
mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: two RF RX channels per RF
module in NB-IoT mode
Licensing principles: One license unit is required
for each RF RX channel except for the two default
RF RX channels per RF module in NB-IoT mode.
NOTE
The number of license units for RF RX channels of an RF
module is related to the sector equipment configuration.
The number of license units for RF RX channels of an RF
module serving a cell is not related to the number of
antennas serving the cell and is not calculated on a per
carrier basis for multi-carrier RF modules.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
51
eRAN
License Management Feature Parameter Description
3 General Principles
Model
Description
Details
ML1SMUCA5R
00
Multi-carrier
License for
5000 Series RF
Module (NBIoT)
Function: controls the multi-carrier capability of
5000 series RF modules in NB-IoT mode.
Applicable eNodeBs: 3900 and 5900 series base
stations
Default capacity: An RF module operates with only
one carrier and does not support multiple carriers in
NB-IoT mode by default.
Licensing principles: One license unit is required
for each carrier except for the default carrier per RF
module in NB-IoT mode. The number of license
units required for an RF module is equal to the total
number of carriers on the RF module minus 1.
Feature Items
Feature items cover the following feature types:
l
Basic software features
Basic software features are the fundamental part of a software release and not licensecontrolled.
They are usually assembled into a basic package for sale, such as the "eNodeB FDD
Basic Software" in Table 3-18. IDs of basic software features contain six digits.
For basic features and their descriptions, see product-specific feature lists and feature
description documents.
l
Optional software features
Optional software features are features other than basic software features in a software
release. License units can be purchased for optional features upon request. For optional
features and their descriptions, see product-specific feature lists and feature description
documents.
IDs of optional features contain either six or eight digits. Features whose IDs contain
eight digits are child features of those whose IDs contain the first six of the eight digits.
License control items are defined on a per parent feature basis, and child features are
controlled together with their parent features. For example, a license control item is
defined only for LOFD-003014 among the following optional features:
–
LOFD-003014 Integrated Firewall
–
LOFD-00301401 Access Control List (ACL)
–
LOFD-00301402 Automatic ACL Rule Configuration
3.2.4.3 License Control Items for Single-Mode Base Stations (TDD)
License control items can be categorized into capacity items and feature items.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
52
eRAN
License Management Feature Parameter Description
3 General Principles
Capacity Items
The following table describes the capacity license control items. Operators can purchase a
license for the required hardware resources without having to pay for the maximum capacity
of all hardware resources.
l
If no LKF is installed on an eNodeB, the amount of resources available for the eNodeB
is the "Default capacity" values listed in the table.
l
If an LKF is installed on the eNodeB, the amount of resources available for the eNodeB
is calculated in either of the following ways:
Equal to the sum of the default capacity of the corresponding license control item and the
capacity provided by purchased license units for this item
Equal to the capacity provided by purchased license units for the corresponding license
control item
Table 3-21 Capacity license control items
License
Control
Item
Model
Description
eNodeB
TDD Basic
Software,
V100R015
(per Cell)
(TDD)
LT4SOV
TBAS15
Function: Controls the number of cells that can be activated on
an eNodeB.
Default capacity: one cell
Licensing principles: One license unit is required for each
activated cell. The number of license units to be purchased is
equal to the number of cells that must be activated on an eNodeB.
Total capacity: Number of cells that can be activated on an
eNodeB = Number of purchased license units
RF Output
Power (per
20W)
(TDD)
LT1ST0
00PA00
Function: Controls the maximum power of non-massive-MIMO
RF modules other than 5000 series.
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units of 20 W. One
license unit is required for every 20 W except for the default 20
W power per RF module. The number of license units to be
purchased for a cell is determined by the cell power.
Total capacity: Maximum power of an eNodeB = (Number of
RF modules + Number of purchased license units) x 20 W
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
53
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Carrier
Bandwidth
- 0~5MHz
(TDD)
LT1ST0
5MHZ00
Function: Controls the 0–5 MHz carrier bandwidth capability
of non-massive-MIMO RF modules other than 5000 series.
Default capacity: 5 MHz
Licensing principles: Carrier bandwidth is licensed in units of 5
MHz. One license unit is required for every 5 MHz bandwidth
unit. The number of license units to be purchased is determined
by the total number of 0–5 MHz carrier bandwidth units
required by an eNodeB.
Total capacity: Total amount of 0–5 MHz carrier bandwidth
available for an eNodeB = Number of purchased license units x 5
MHz
Carrier
Bandwidth
5~10MHz
(TDD)
LT1ST1
0MHZ00
Function: Controls the 5–10 MHz carrier bandwidth capability
of non-massive-MIMO RF modules other than 5000 series.
Default capacity: none
Licensing principles: Carrier bandwidth is licensed in units of 5
MHz. One license unit is required for every 5 MHz bandwidth
unit. The number of license units to be purchased is determined
by the total number of 5–10 MHz carrier bandwidth units
required by an eNodeB.
Total capacity: Total amount of 5–10 MHz carrier bandwidth
available for an eNodeB = Number of purchased license units x 5
MHz
Carrier
Bandwidth
10~15MH
z (TDD)
LT1ST1
5MHZ00
Function: Controls the 10–15 MHz carrier bandwidth capability
of non-massive-MIMO RF modules other than 5000 series.
Default capacity: none
Licensing principles: Carrier bandwidth is licensed in units of 5
MHz. One license unit is required for every 5 MHz bandwidth
unit. The number of license units to be purchased is determined
by the total number of 10–15 MHz carrier bandwidth units
required by an eNodeB.
Total capacity: Total amount of 10–15 MHz carrier bandwidth
available for an eNodeB = Number of purchased license units x 5
MHz
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
54
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Carrier
Bandwidth
15~20MH
z (TDD)
LT1ST2
0MHZ00
Function: Controls the 15–20 MHz carrier bandwidth capability
of non-massive-MIMO RF modules other than 5000 series.
Default capacity: none
Licensing principles: Carrier bandwidth is licensed in units of 5
MHz. One license unit is required for every 5 MHz bandwidth
unit. The number of license units to be purchased is determined
by the total number of 15–20 MHz carrier bandwidth units
required by an eNodeB.
Total capacity: Total amount of 15–20 MHz carrier bandwidth
available for an eNodeB = Number of purchased license units x 5
MHz
NOTE
The following are the principles for applying for carrier bandwidth license
units:
l If the cell bandwidth is 5 MHz, apply for one unit of Carrier
Bandwidth - 0~5MHz (TDD).
l If the cell bandwidth is 10 MHz, apply for one unit of Carrier
Bandwidth - 0~5MHz (TDD) and one unit of Carrier Bandwidth 5~10MHz (TDD).
l If the cell bandwidth is 15 MHz, apply for one unit of Carrier
Bandwidth - 0~5MHz (TDD), one unit of Carrier Bandwidth 5~10MHz (TDD), and one unit of Carrier Bandwidth - 10~15MHz
(TDD).
l If the cell bandwidth is 20 MHz, apply for one unit of Carrier
Bandwidth - 0~5MHz (TDD), one unit of Carrier Bandwidth 5~10MHz (TDD), one unit of Carrier Bandwidth - 10~15MHz
(TDD), and one unit of Carrier Bandwidth - 15~20MHz (TDD).
RRC
Connected
User (per
RRC
Connected
User)
(TDD)
LT1STA
CTUS00
Function: Controls the number of UEs in RRC_CONNECTED
mode served by an eNodeB.
Default capacity: six RRC_CONNECTED UEs
Licensing principles: One license unit is required for each
RRC_CONNECTED UE. The number of license units to be
purchased equals the maximum number of RRC_CONNECTED
UEs to be served by an eNodeB.
Total capacity: Maximum number of RRC_CONNECTED UEs
to be served by an eNodeB = Number of purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
55
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Throughpu
t Capacity
(per Mbps)
(TDD)
LT1STT
HROU0
0
Function: Controls the application-layer data rate on the user
plane of an eNodeB. This rate is measured based on Packet Data
Convergence Protocol (PDCP) and GPRS Tunneling Protocol for
User Plane (GTP-U) payload.
Applicable eNodeBs: 3900 and 5900 series base stations
Default capacity: 5 Mbit/s
Licensing principles: One license unit is required for each 1
Mbit/s. The number of license units to be purchased is
determined by the sum of uplink and downlink data rates of an
eNodeB.
Admission control: Admission control on a new service is
performed based on its uplink and downlink load measured by
the throughput license algorithm. If the new service's load
measured by the throughput license algorithm plus existing
services' load measured by the throughput license algorithm
exceeds the licensed throughput of the eNodeB
(LT1S0THROU00), the eNodeB rejects the service admission
request.
Overload control: Overload control is performed based on the
existing services' uplink and downlink load measured by the
throughput license algorithm. If the existing services' uplink and
downlink load measured by the throughput license algorithm
exceeds the licensed throughput of the eNodeB, the eNodeB
preferentially releases low-priority services whose ARP IE Preemption Vulnerability is set to pre-emptable. This helps ensure
the quality of high-priority services.
The load measured by the throughput license algorithm is
calculated as follows:
l Flow-control services:
Admitted and new services: (GBR or MinGBR) x activity
factor
l Non-flow-control services:
– Admitted service: actual throughput
– New service: (GBR or MinGBR) x activity factor
Flow-control and non-flow-control services are configured by
QciPara.FlowCtrlType, uplink MinGBR is configured by
QciPara.UlMinGbr, downlink MinGBR is configured by
QciPara.DlMinGbr, and the activity factor is configured by
UDTPARAGRP.ACTFACTOR. If no activity factor is
configured, the default value 0% takes effect.
Reconfiguring the MinGBR or activity factor impacts service
admission based on the throughput license. A smaller value of the
MinGBR or activity factor indicates a smaller minimum
guaranteed bit rate for services with the corresponding QCI and
results in a lower load measured by the license throughput
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
56
eRAN
License Management Feature Parameter Description
License
Control
Item
Model
3 General Principles
Description
algorithm; however, the number of services that can be admitted
increases when the licensed throughput capacity of the eNodeB is
limited. A larger parameter value results in the opposite effects.
NOTE
The token bucket algorithm is used to control traffic. The licensed data
rate is the rate at which tokens are injected into a token bucket. Operators
can define the ratio of licensed uplink or downlink traffic to the total
licensed traffic by running the MOD LICRATIO command. The
UpLicRatio parameter of this command specifies the percentage of
licensed uplink traffic. According to the algorithm, the token bucket size
is determined by the token injection rate and the token measurement
period, which is a fixed value of 1800 seconds. If there are sufficient
tokens in the bucket, the eNodeB processes data normally; otherwise, the
eNodeB starts to control traffic, which affects data processing.
This algorithm is adopted because the traffic volume fluctuates between
peak and off-peak hours. To smooth the traffic burr (instantaneous peak
rate) for a single eNodeB and to efficiently utilize the traffic capacity
during off-peak hours, the traffic capacity for a maximum of 1800
seconds in off-peak hours can be accumulated for use in peak hours.
For example:
In the first 1800-second period, the eNodeB has no traffic, and the traffic
capacity of 9000 megabits (5 Mbit/s x 1800s) is accumulated. A UE
accesses the network at the 1801st second. The data rate of the UE is
maintained at 10 Mbit/s, which is twice the licensed 5 Mbit/s. This burst
time can last throughout the second 1800-second period. During the third
period, the data rate of the UE is maintained at 5 Mbit/s and the service is
not interrupted.
Total capacity: Total throughput of an eNodeB = Number of
purchased license units x 1 Mbit/s
RF Multi
Carrier
(per
Carrier)
(TDD)
LT1ST0
0MCA0
0
Function: Controls the multi-carrier capability of non-massiveMIMO RF modules other than 5000 series.
Default capacity: An RF module operates with only one carrier
and does not support multiple carriers by default.
Licensing principles: The number of license units required for
an RF module is equal to the total number of carriers on the RF
module minus 1. If the RF module is required to support only one
carrier, the multi-carrier license is not required.
Total capacity: Number of carriers except the default carrier per
RF module available for an eNodeB = Number of purchased
license units
NOTE
If a 4T4R RRU is split into two 2T2R RRUs, each 2T2R RRU supports
one carrier by default. These carriers do not consume license units. If such
a 2T2R RRU provides more than one carrier, each of the extra carriers
consumes one license unit.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
57
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Resource
Block (per
RB)(TDD)
LT1S000
TRB00
Function: Controls the number of resource blocks (RBs) within
the bandwidth of cells served by an eNodeB.
Default capacity: 25 RBs, which correspond to a bandwidth of 5
MHz
Licensing principles: One license unit is required for each RB.
The number of license units to be purchased is determined by cell
bandwidths. The following is the mapping between carrier
bandwidths and the number of RBs:
l 5 MHz: 25 RBs
l 10 MHz: 50 RBs
l 15 MHz: 75 RBs
l 20 MHz: 100 RBs
Total capacity: Number of RBs within the bandwidth of cells on
an eNodeB = Number of purchased license units
NOTE
The number of RBs required for a single frequency network (SFN) cell
equals the sum of RBs required for all the physical cells that compose the
SFN cell. For example, a 20 MHz SFN cell served by three RRUs
requires 300 RBs.
BB
Transmit
Channel
(per
Channel)
(TDD)
LT1S0T
BBTC00
Function: Controls the logical transmit (TX) channel capability
of non-massive-MIMO BBPs.
Default capacity: two baseband TX channels per cell on each
BBP
Licensing principles: One license unit is required for each
baseband TX channel except the two default baseband TX
channels per cell.
Total capacity: Number of baseband TX channels provided by
an eNodeB = Number of cells on the eNodeB x 2 + Number of
purchased license units
BB
Receive
Channel
(per
Channel)
(TDD)
LT1S0T
BBRC00
Function: Controls the logical receive (RX) channel capability of
non-massive-MIMO BBPs.
Default capacity: two baseband RX channels per cell on each
BBP
Licensing principles: One license unit is required for each
baseband RX channel except the two default baseband RX
channels per cell.
Total capacity: Number of baseband RX channels provided by
an eNodeB = Number of cells on the eNodeB x 2 + Number of
purchased license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
58
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
RF
Transmit
Channel
(per
Channel)
(TDD)
LT1S0T
RFTC00
Function: Controls the physical TX channel capability of nonmassive-MIMO RF modules other than 5000 series.
Default capacity: two RF TX channels per RF module
Licensing principles: One license unit is required for each RF
TX channel except the two default RF TX channels per RF
module.
NOTE
The number of license units for RF TX channels of an RF module serving
a cell is not related to the number of antennas serving the cell and is not
calculated on a per carrier basis for multi-carrier RF modules.
Total capacity: Number of RF TX channels provided by an
eNodeB = Number of RF modules x 2 + Number of purchased
license units
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
59
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
RF
Receive
Channel
(per
Channel)
(TDD)
LT1S0T
RFRC00
Function: Controls the physical RX channel capability of nonmassive-MIMO RF modules other than 5000 series.
Default capacity: two RF RX channels per RF module
Licensing principles: One license unit is required for each RF
RX channel except the two default RF RX channels per RF
module.
NOTE
The number of license units for RF RX channels of an RF module serving
a cell is not related to the number of antennas serving the cell and is not
calculated on a per carrier basis for multi-carrier RF modules.
Total capacity: Number of RF RX channels provided by an
eNodeB = Number of RF modules x 2 + Number of purchased
license units
NOTE
The following are examples of applying for baseband or RF TX/RX
channel license units:
l If a 4T4R RF module serves two 2T2R cells, the RF module requires
two RF TX channel license units and two RF RX channel license
units. The cells do not require additional baseband TX/RX channel
license units.
l If a 4T4R RF module serves only one 2T2R cell, the RF module does
not require RF TX/RX channel license units, and the cell does not
require additional baseband TX/RX channel license units.
l If two 4T4R RF modules serve three 2T2R cells, the RF module
serving two cells requires two RF TX channel license units and two
RF RX channel license units, and the RF module serving one cell
does not require RF TX/RX channel license units. Baseband TX/RX
channel license units are not required.
l If six 2T2R RF modules serve three 4T4R cells, the RF modules do
not require additional RF TX/RX channel license units, but the cells
require six baseband TX channel license units and six baseband RX
channel license units.
In multi-carrier scenarios:
If an RF module bears a number of carriers, the cells on these carriers
must be mapped to the same set of sector equipment. In this way, the
eNodeB can correctly consume RF TX or RX channel license units.
20W
Power
License for
5000
Series RF
Module
(TDD)
Issue Draft A (2019-01-05)
LT1ST5
P20W00
Function: Controls the maximum power of 5000 series nonmassive-MIMO RF modules.
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units of 20 W. One
license unit is required for every 20 W except for the default 20
W power per RF module. The number of license units to be
purchased for a cell is determined by the cell power.
Copyright © Huawei Technologies Co., Ltd.
60
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
5MHz Cell
Bandwidth
License for
5000
Series RF
Module
(TDD)
LT1ST5
5MHZ00
Function: Controls the 5 MHz bandwidth capability of 5000
series non-massive-MIMO RF modules.
Transmit
Channel
License for
5000
Series RF
Module
(TDD)
LT1ST5
RFTC00
Receive
Channel
License for
5000
Series RF
Module
(TDD)
LT1ST5
RFRC00
Multicarrier
License for
5000
Series RF
Module
(TDD)
LT1ST5
MUCA0
0
pRRU RF
Multi
Carrier(TD
D)
LT1SPR
RFMC0
0
Default capacity: none
Licensing principles: Carrier bandwidth is licensed in units of 5
MHz. One license unit is required for every 5 MHz bandwidth
unit. The number of license units to be purchased is determined
by the total number of 5 MHz carrier bandwidth units required by
an eNodeB.
Function: Controls the physical TX channel capability of 5000
series non-massive-MIMO RF modules.
Default capacity: two RF TX channels per RF module
Licensing principles: One license unit is required for each RF
TX channel except the two default RF TX channels per RF
module.
Function: Controls the physical RX channel capability of 5000
series non-massive-MIMO RF modules.
Default capacity: two RF RX channels per RF module
Licensing principles: One license unit is required for each RF
RX channel except the two default RF RX channels per RF
module.
Function: Controls the multi-carrier capability of 5000 series
non-massive-MIMO RF modules.
Default capacity: An RF module operates with only one carrier
and does not support multiple carriers by default.
Licensing principles: One license unit is required for each
carrier except for the default carrier per RF module. The number
of license units required for an RF module is equal to the total
number of carriers on the RF module minus 1.
Function: Controls the multi-carrier capability of LampSite RF
modules other than 5000 series.
Default capacity: An RF module operates with only one carrier
and does not support multiple carriers by default.
Licensing principles: One license unit is required for each
carrier except for the default carrier per RF module. The number
of license units required for an RF module is equal to the total
number of carriers on the RF module minus 1.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
61
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Massive
MIMO
20W
Power
License for
5000
Series RF
Module
(TDD)
LT4S20
WPMM
RF
Function: Controls the maximum power of 5000 series massive
MIMO RF modules.
Massive
MIMO
5MHz Cell
Bandwidth
License for
5000
Series RF
Module(T
DD)
LT4S5M
CMMR0
0
Massive
MIMO
Multicarrier
License for
5000
Series RF
Module
(TDD)
LT4SM
CMMRF
00
Massive
MIMO RF
16Transmit
Channel
Group
License for
5000
Series(TD
D)
LT1SM
MRTCG
00
Massive
MIMO RF
16-Receive
Channel
Group
License for
5000
Series(TD
D)
LT1SM
MRRCG
00
Issue Draft A (2019-01-05)
Default capacity: 20 W per RF module
Licensing principles: RF power is licensed in units of 20 W. One
license unit is required for every 20 W except for the default 20
W power per RF module. The number of license units to be
purchased for a cell is determined by the cell power.
Function: Controls the 5 MHz bandwidth capability of 5000
series massive MIMO RF modules.
Default capacity: none
Licensing principles: Carrier bandwidth is licensed in units of 5
MHz. One license unit is required for every 5 MHz bandwidth
unit. The number of license units to be purchased is determined
by the total number of 5 MHz carrier bandwidth units required by
an eNodeB.
Function: Controls the multi-carrier capability of 5000 series
64T massive MIMO RF modules.
Default capacity: An RF module operates with only one carrier
and does not support multiple carriers by default.
Licensing principles: One license unit is required for each
carrier except for the default carrier per RF module. The number
of license units required for an RF module is equal to the total
number of carriers on the RF module minus 1.
Function: Controls the physical TX channel capability of 5000
series massive MIMO RF modules.
Default capacity: 32 RF TX channels per RF module
Licensing principles: One license unit is required for every 16
RF TX channels except the 32 default RF TX channels per RF
module.
Function: Controls the physical RX channel capability of 5000
series massive MIMO RF modules.
Default capacity: 32 RF RX channels per RF module
Licensing principles: One license unit is required for every 16
RF RX channels except the 32 default RF RX channels per RF
module.
Copyright © Huawei Technologies Co., Ltd.
62
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Massive
MIMO BB
16Transmit
Channel
Group
License(T
DD)
LT4SM
MBTCG
00
Function: Controls the logical TX channel capability of massive
MIMO BBP UBBPem or UBBPf1.
Default capacity: 32 baseband TX channels per cell on each
BBP
Licensing principles: For the UBBPem or UBBPf1, one license
unit is required for every 16 baseband TX channels except the 32
default baseband TX channels per cell on each BBP.
Total capacity: Number of license units for baseband TX
channels provided by an eNodeB = Number of cells on the
eNodeB x 2 + Number of purchased license units
Massive
MIMO BB
16-Receive
Channel
Group
License(T
DD)
LT1SM
MBRCG
00
Function: Controls the logical RX channel capability of massive
MIMO BBP UBBPem or UBBPf1.
Default capacity: 32 baseband RX channels per cell on each
BBP
Licensing principles: For the UBBPem or UBBPf1, one license
unit is required for every 16 baseband RX channels except the 32
default baseband RX channels per cell on each BBP.
Total capacity: Number of license units for baseband RX
channels provided by an eNodeB = Number of cells on the
eNodeB x 2 + Number of purchased license units
Massive
MIMO UL
2-Layers
Extended
Processing
Unit
License(T
DD)
LT4SM
MULML
01
Function: Controls the uplink multi-layer transmission capability
of BBPs of a massive MIMO cell
Default capacity: none
Licensing principles: Apply for the number of license units
based on the total number of uplink layers in the massive MIMO
cells on each BBP. One license unit is required for every two
layers in the massive MIMO cells on each BBP.
Number of license units to be purchased for a cell = Number of
uplink layers in the cell/2
The total number of license units purchased for an eNodeB must
not exceed the maximum multi-layer transmission capability of a
BBP.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
63
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
Massive
MIMO DL
2-Layers
Extended
Processing
Unit
License
(TDD)
LT4SM
MDLML
01
Function: Controls the downlink multi-layer transmission
capability of BBPs of massive MIMO cells
Default capacity: none
Licensing principles: Apply for the number of license units
based on the total number of downlink layers in the massive
MIMO cells on each BBP. One license unit is required for every
two layers in the massive MIMO cells on each BBP.
Number of license units to be purchased for a cell = Number of
downlink layers in the cell/2
The total number of license units purchased for an eNodeB must
not exceed the maximum multi-layer transmission capability of a
BBP.
UBBP
Massive
MIMO
Operating
Bandwidth
1*20MHz
License(pe
r 20MHz)
(TDD)
LT4SUB
BPMMB
D
Function: Controls the bandwidth capability of the massive
MIMO BBP UBBPfw1/UBBPf3.
Default capacity: none
Licensing principles: For the UBBPfw1/UBBPf3, apply for
license units based on the baseband bandwidth of cells
established on each BBP. For each 20 MHz cell adopting eCPRI
transmission, one license unit is required. If the bandwidth of a
cell is less than 20 MHz, the cell bandwidth is regarded as 20
MHz. For each 20 MHz cell adopting CPRI transmission, apply
for two license units. If the bandwidth of a cell is less than 20
MHz, the cell bandwidth is regarded as 20 MHz.
Total capacity: Baseband bandwidth supported by the eNodeB =
Number of purchased license units x 20 MHz
UBBP
Massive
MIMO
Extended
Channel
1*16T16R
License
(TDD)
LT4SUB
BPMMC
N
Function: Controls the logical TX channel capability of the
massive MIMO BBP UBBPfw1/UBBPf3.
Default capacity: Each Massive MIMO cell supports 16T16R by
default.
Licensing principles: One license unit is required for every 16
baseband TX channels except the 16 default baseband TX
channels per massive MIMO cell on the UBBPfw1/UBBPf3.
The formula for calculating the total capacity after the license
unit is purchased is as follows: Number of baseband extension
channels supported by the UBBPfw1/UBBPf3 = Number of
purchased license units x 16T16R + Number of Massive MIMO
cells established on the UBBPfw1/UBBPf3 x 16T16R The
number of logical channels refers to the maximum number of TX
or RX channels.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
64
eRAN
License Management Feature Parameter Description
3 General Principles
License
Control
Item
Model
Description
5MHz
Bandwidth
License for
5000
Series
LampSite
pRRU(TD
D)
LT145M
CB5S10
Function: controls the 5 MHz bandwidth capability of 5000
series LampSite pRRUs.
eMTC
User(TDD
)
LT4STD
EMTCU
S
Default capacity: None. No bandwidth is provided to the pRRU
for free by default.
Licensing principles: The bandwidth is licensed in units of 5
MHz. The number of license units to be purchased is determined
by the total pRRU bandwidth required by an eNodeB.
Function: Controls the number of eMTC UEs camping on a cell.
The sales unit is per 100 eMTC UEs.
Applicable eNodeBs: 3900 and 5900 series base stations
Licensing principles: One license unit is required for 100 eMTC
UEs.
eMTC
BHCA(TD
D)
LT4SEM
TCBHC
A
Function: controls the number of times that the eNodeB provides
access for eMTC UEs per hour. The sales unit is 100 BHCAs.
Applicable eNodeBs: 3900 and 5900 series base stations
Default capacity: 1
Licensing principles: One license unit is required when eMTC
UEs successfully access the eNodeB 100 times within one hour.
The operator needs to purchase license units based on the
maximum number of times that eMTC UEs might access an
eNodeB within one hour.
eMTC
BDCA(TD
D)
LT4STD
EMTCB
D
Function: controls the number of times that the eNodeB provides
access for eMTC UEs every 24 hours. The sales unit is 1000
BDCAs.
Applicable eNodeBs: 3900 and 5900 series base stations
Default capacity: 1
Licensing principles: One license unit is required when eMTC
UEs successfully access the eNodeB 1000 times within 24 hours.
The operator needs to purchase license units based on the
maximum number of times that eMTC UEs might access an
eNodeB within 24 hours.
Feature License
Feature licenses cover the following feature types:
l
Basic software features
Basic software features are a fundamental part of a software release.
They are usually assembled into a basic software package for sales. The basic software
package must be purchased to use the software. For basic features and their descriptions,
see product-specific feature lists and feature description documents.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
65
eRAN
License Management Feature Parameter Description
3 General Principles
The license for the basic software package controls the number of cells that can be
activated on an eNodeB.
l
Optional software features
Optional software features are features other than the basic features in a software release.
Licenses must be purchased for optional software features.
IDs of optional features contain either six or eight digits. Features whose IDs contain
eight digits are child features of their parent features whose IDs are the first six of the
eight digits. License control items are defined on a per parent feature basis, and child
features are controlled together with their parent features.
3.2.5 License Control Items for USUs
License
Control
Item
Model
Description
BBU Pool
Interconne
ction Port
License
(per BBU/
USU)
LT1S0B
BUIP00
Function: Controls the number of connections set up for a USU
to BBUs or other USUs.
Default capacity: none
Licensing principles: One license unit is required for each
connection between a USU and a BBU or another USU.
Total capacity: Number of BBUs or USUs that are connected to
a USU = Number of purchased license units
USU3900
Basic
Software,
V100R015
(per USU)
LT1S1B
ASIC15
Function: USU3900 basic software package
Default capacity: 1
Licensing principles: There is no licensing requirement. It
indicates a change in the R version.
Total capacity: 1
USU3910
Basic
Software,
V100R015
(per USU)
QWUS0
BASIC1
5
Function: USU3910 basic software package
Default capacity: 1
Licensing principles: There is no licensing requirement. It
indicates a change in the R version.
Total capacity: 1
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
66
eRAN
License Management Feature Parameter Description
4 License Management
4
License Management
License management is performed to ensure that a software system is used within the scope of
the licensed features, releases, and capacities and for the specified validity period.
NOTE
Unless otherwise specified, the NEs mentioned in 4.1 License States and 4.2 Common Methods for
LKF Management refer to eNodeBs or USUs.
4.1 License States
An NE may be in one of the following license states: default, commissioning, normal,
emergency, and grace period. The license states are as follows:
l
Default license state: If no valid LKF has been installed on an NE during new site
deployment, the query result indicates the default license state.
l
Commissioning license state: If a demo LKF has been installed on an NE during
engineering implementation, the query result indicates the commissioning license state.
l
Normal license state: If a commercial or commercially permanent & fixed-term LKF has
been on an NE during the engineering acceptance stage, the query result indicates the
normal license state.
l
Emergency license state: In case of emergency (such as an earthquake) during the
maintenance stage, if the emergency license has been activated by running the SET
LICENSECTRL command, the query result indicates the emergency license state. The
USU does not support the emergency state.
l
Grace period state: When an NE is operating, the query result indicates the grace period
in any of the following situations:
–
An ESN or Version check on an LKF fails.
–
A demo LKF expires.
–
A commercial LKF or a commercially permanent & fixed-term LKF is revoked.
Figure 4-1 shows the transition of license states.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
67
eRAN
License Management Feature Parameter Description
4 License Management
Figure 4-1 License state transition
4.1.1 Default License State
An operating NE enters the default license state if either of the following conditions is
fulfilled:
l
No valid LKF is installed on the NE.
l
The NE has been in the grace period for 60 days.
In the default license state, the NE operates at the default capacity of license control items,
and all optional function items are turned off. In the default license state, the switching
function of the USU is disabled.
When an NE enters the default license state, it reports ALM-26818 No License Running in
System.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
68
eRAN
License Management Feature Parameter Description
4 License Management
4.1.2 Commissioning License State
An operating NE enters the commissioning license state when a demo LKF is installed on the
NE. In a typical demo LKF, resource items are set to the maximum values and optional
function items are all turned on.
After a demo LKF expires, the NE status changes from the commissioning license state to the
grace period. An NE can stay in the grace period for up to 60 days. After 60 days, the NE
enters the default license state.
4.1.3 Normal License State
An operating NE enters the normal license state when a commercial or commercially
permanent & fixed-term LKF is installed on the NE. In the normal license state, the NE
operates within the licensed values defined in the LKF.
NOTE
If license control items in the fixed-term feature segments of a commercially permanent & fixed-term
LKF expire, the NE reports ALM-26815 Licensed Feature Entering Keep-Alive Period. After 60 days,
these license control items become invalid, and the NE reports ALM-26816 Licensed Feature Unusable.
4.1.4 Emergency License State
The emergency switch state can be set to on for an eNodeB on special occasions (such as
earthquakes). In the emergency license state, the eNodeB operates with the maximum
allowable data rate and serves the maximum number of UEs, rather than be confined to the
licensed limits. This ensures that the performance does not deteriorate. After the emergency
switch state is set to on for an eNodeB operating in default license state, the eNodeB operates
with the maximum allowable capabilities in terms of data rate, number of UEs, and other
license control items. The emergency license state can be started three times at most for an
eNodeB in the same R version. The emergency license state after each startup can last for
seven consecutive days. When the eNodeB enters or exits the emergency license state, it
reports an event:
l
Entering the state: EVT-26820 License Emergency Status Activated
l
Exiting the state: EVT-26821 License Emergency Status Ceased
The LST LICENSECTRL command can be used to query Emergency Switch State,
Remaining Emergency Times, and Remaining Emergency Days.
4.1.5 Grace Period State
An operating NE enters the grace period state when any of the following conditions is
fulfilled:
l
An ESN or Version check on its LKF fails.
l
Its demo LKF expires.
l
Its commercial LKF or commercially permanent & fixed-term LKF is revoked.
In the grace period state, the NE can operate at the licensed values for up to 60 days with no
impact on services. After 60 days, the NE enters the default license state.
When an NE enters the grace period state, it reports ALM-26817 License on Trial.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
69
eRAN
License Management Feature Parameter Description
4 License Management
NOTE
The reporting of ALM-26817 License on Trial does not affect ongoing services. If O&M engineers
manually clear or mask this alarm and do not install a commercial LKF timely, network accidents may
arise. To avoid this situation, the NE will check and report the alarm the next day after the alarm is
cleared, and O&M engineers cannot mask the alarm.
4.2 Common Methods for LKF Management
Each NE stores one LKF in its main control board. Each LKF is dedicated to one NE and
cannot be shared between NEs except for a demo LKF with ESN set to ANY (which can be
installed on any NE).
LKFs have one-to-one mapping with ESNs. The ESN of an NE is the ESN of the backplane in
its BBU. An new LKF is required if the ESN is changed (for example, when the BBU is
replaced).
NOTE
l If the main control board of an NE is replaced but the ESN remains unchanged, the original LKF can be
installed on the new main control board. There is no need to apply for a new LKF in this situation.
l After a new LKF is obtained, the LKF can be installed and activated through the U2020 or LMT. When
the LKF is being installed, the eNodeB checks the consistency between the license control items in the
LKF and the configured data.
4.2.1 LKF Precheck
Before an LKF is to be installed on an NE, the U2020 delivers the LKF to the NE for
precheck to ensure the validity of the LKF. The NE only checks the validity of the LKF but is
not loaded with the LKF. After the precheck, the NE reports the check results to the U2020,
and the U2020 generates a result file for operators to determine whether the LKF is valid. For
detailed operations, see 4.6.3.1 License Operations on the U2020.
4.2.2 LKF Verification
When an LKF is being installed on an NE, the NE verifies the LKF and one of the following
situations may occur:
l
If the LKF has already expired, it fails to be installed.
l
If the product name or the signature in the Footer segment fails verification, the LKF
fails to be installed.
l
If the value of ESN does not match the ESN of the NE, the LKF fails to be installed.
l
If the value of Version does not match the version of the NE, the installation result
indicates the error and the operator can choose to forcibly install the LKF. After the
forced installation, the NE operates in the grace period state.
NOTE
The LKF of a release that has a different Version value from the version of the NE can be forcibly
installed only once.
l
If licensed limits (pertaining to function items, resource items, and validity periods) in
the LKF are different from those in the previous LKF, the installation result indicates the
differences and the operator can choose to forcibly install the new LKF.
l
If the value of a license control item (excluding the basic item such as the number of
cells per eNodeB) in the LKF is less than the specific configured value, the installation
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
70
eRAN
License Management Feature Parameter Description
4 License Management
result lists the license control item. The operator can choose to forcibly install the new
LKF.
NOTE
If a license control item is not available from the LKF, the corresponding function is license controlled
at the minimum value.
4.2.3 Consistency Check Between Licensed Values and Data
Configurations
The consistency check between licensed values and data configurations can be used in the
following scenarios:
l
LKF installation
If a license control item has the corresponding configuration data but the licensed limit in
the LKF is less than the configured value, the LMT returns a minor error message while
the U2020 returns a major error message. If the LKF is forcibly installed, the NE reports
ALM-26819 Data Configuration Exceeding Licensed Limit and the configured data
beyond the licensed value does not take effect. For details, see 5.1 Faults Occurred
During Installation.
NOTE
LKF installation fails directly if any of the following license control items is unavailable: eNodeB
Basic Software, RRC Connected User, and Throughput Capacity.
l
Data configuration
An NE compares data configurations with licensed values when it attempts to make the
data configurations take effect, rather than when the data is configured. Data can be
written into the database when data configuration constraints are fulfilled. When the NE
attempts to make the data configurations take effect, a failure message is displayed if the
NE finds that the configured data is greater than the licensed values. In addition, the NE
reports ALM-26819 Data Configuration Exceeding Licensed Limit.
l
License maintenance before and after LKF installation
Before a new LKF is installed on an NE, consistency between the LKF and data
configurations of the NE can be checked to verify whether the LKF meets the
requirements of the configurations. For details about how to perform the check, see
4.6.3.1 License Operations on the U2020. After an LKF is installed on an NE, if the
configured data of the NE exceeds the licensed limits and ALM-26819 Data
Configuration Exceeding Licensed Limit is reported, consistency between the LKF and
data configurations of the NE can also be checked. For details about how to perform the
check, see 4.6.3.1 License Operations on the U2020.
4.2.4 LKF Revocation
A new LKF is required to replace an existing commercial LKF if the related ESN is changed
or the licensed capacity is adjusted. Before applying for a new LKF, ensure that the previous
commercial LKF has been revoked and a revocation code has been obtained. The following
are descriptions about LKF revocation and revocation codes:
l
LKF revocation is an operation of retrieving license keys to ensure that they will not be
reused on devices. To revoke an LKF, perform the revocation operations on the U2020
client as described in Revoking an LKF in 4.6.3.1 License Operations on the U2020, or
run the RVK LICENSE command on the LMT.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
71
eRAN
License Management Feature Parameter Description
l
4 License Management
A revocation code is a character string generated after an LKF is revoked. A license
revocation code is proof of proper LKF revocation and a prerequisite to applying for a
new LKF.
After the LKF is revoked, a revocation code is returned by the NE. The NE enters the grace
period state, retaining its services for up to 60 days.
When an LKF on an NE is revoked, the NE reports ALM-26817 License on Trial.
4.2.5 License Overload
During system operation, the usage of capacity resource items, such as the UE count and
traffic rate, may become so high that it is confined to the licensed limits. This license
insufficiency affects the services that require the resources beyond the licensed limits. To
promptly inform users of a requirement for capacity expansion, ALM-26812 System Dynamic
Traffic Exceeding Licensed Limit is reported when the usage of the dynamic resource items
exceeds the licensed value.
The alarm mechanism performs as follows: If the usage of a capacity resource item exceeds a
percentage of the licensed value (configurable, 100% by default), the eNodeB reports
ALM-26812 System Dynamic Traffic Exceeding Licensed Limit. If the usage of the capacity
resource item reduces to a percentage of the licensed value or less (configurable, 90% by
default), ALM-26812 System Dynamic Traffic Exceeding Licensed Limit is cleared. To
prevent repeated alarm reporting and clearing, an alarm detection duration and an alarm
clearing duration can be set. The default value is 5 minutes for both durations. An alarm is
reported if a dynamic resource item meets the alarm reporting condition at all check points
within an alarm detection duration. The alarm is cleared if the item meets the alarm clearing
condition at all check points within an alarm clearing duration.
ALM-26812 System Dynamic Traffic Exceeding Licensed Limit is reported only when the
total traffic volume on the uplink and downlink of an eNodeB exceeds the licensed limit.
NOTE
The alarm threshold percentages, the alarm clearing percentages, the alarm detection duration and the
alarm clearing duration can be set by running the SET ENBLICENSEALMTHD command.
4.2.6 License Redundancy
The usage of capacity resource items, such as the UE count and traffic rate, may fluctuate
greatly during system operation and is confined to the licensed limits even when the usage
only slightly exceeds the licensed value. To prevent this problem and improve user
experience, the usage of some capacity resource items is allowed to reach 110% of the
licensed values. If the values corresponding to 110% of the licensed values exceed the
hardware capabilities, the hardware capabilities become the upper limits for these items.
In the LTE system, only the usage of the UE count and traffic rate is allowed to reach 110% of
the licensed values.
4.2.7 LKF Backup and Restore
An LKF contains important NE data and it can be backed up and restored using the U2020. If
the LKF on the NE must be reloaded because the LKF is damaged, the NE version is rolled
back, or other problems occur (for example, the main control board is damaged), the LKF can
be restored using the U2020. The U2020 supports LKF backup and restore in batches for
eNodeBs. LKF backup and restore using the U2020 can be performed in the following ways:
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
72
eRAN
License Management Feature Parameter Description
l
4 License Management
Automatic backup of LKFs
If an LKF is successfully installed on an NE using the U2020, the LKF is uploaded to the
backup directory of the U2020 server. If the installation fails, the LKF is not automatically
backed up.
l
Manual backup of LKFs
If an LKF is installed on an NE using the LMT, the LKF is not automatically backed up on
the U2020 server. Operators can select a batch of NEs using the U2020 client and upload the
LKFs of the NEs to the backup directory of the U2020 server. For details about how to
manually back up LKFs, see 4.6.3.1 License Operations on the U2020.
l
Manual restoration of LKFs
The LKFs of NEs can be restored in batches. There are two methods of manually
restoring LKFs:
–
Using the LKFs stored in the backup directory of the U2020 server
–
Downloading LKFs from the U2020 server to the U2020 client and then reloading
the LKFs onto NEs
In the first method, the U2020 server searches its backup directory for the LKF mapping
the NE based on the NE name and ESN. If the LKF is available, the LKF is restored. If
the LKF is unavailable, the NE is not displayed in the list of candidate NEs for LKF
restoration and the LKF of the NE cannot be restored.
For details about how to manually restore LKFs by using the two methods, see 4.6.3.1
License Operations on the U2020.
NOTE
Both automatic and manual LKF backup using the U2020 adheres to the following principles:
l Backup LKFs are named in the format of "NE name_ESN_Backup time". After the backup, the
original LKF (if any) is replaced by the new LKF, ensuring that only one LKF maps to an NE.
l During automatic and manual LKF backup, both LKFs in use and LKFs not in use are backed up,
and they are stored in subdirectories active and inactive in the backup directory of the U2020 server,
respectively.
4.2.8 Invalidating Fixed-term License Items
If an operator determines that all fixed-term feature segments in a commercially permanent &
fixed-term LKF are not required any more, the operator can run the SET
FIXTERMLICSWITCH command to invalidate their license items with fixed expiration
dates. Then, the corresponding features become unusable, and no ALM-26816 Licensed
Feature Unusable or ALM-26815 Licensed Feature Entering Keep-Alive Period will be
reported when a licensed feature expires or the grace period of an expired feature controlled
by the license elapses.
This function does not take effect for other types of LKFs.
When an LKF of any type is reloaded or the base station experiences a cross-R version
change, the fixed-term license switch will restore to the default value.
NOTE
An operator can perform this function only after determining that all the fixed-term license items in the
LKF are not required any more. Otherwise, ongoing services may be affected due to lack of license
items, and ALM-26819 Data Configuration Exceeding Licensed Limit may be reported.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
73
eRAN
License Management Feature Parameter Description
4 License Management
4.3 NB-IoT Annual Fee Mode
4.3.1 Principles
The annual fee mode refers to the sales of Huawei NB-IoT licenses in the unit of a certain
period (the current period is year). A license can be upgraded to the latest version within the
licensed usage period.
To improve the license delivery efficiency, single license control items in NB-IoT are
combined into annual fee packages for sale. A customer can apply for a package to associate
the license control items in the package. Then, the eNodeB controls these license control
items accordingly. Table 4-1 describes the packages and the license control items in the
packages.
NOTE
l The maximum values of packaged control items indicate that the use of the license control items in a
package is not restricted after a customer has applied for the package.
l When the annual fee mode is selected for the customer's NB-IoT products, all the sites, entitlements,
and resource pools of earlier versions that support NB-IoT on the customer's network must be
upgraded to a version that supports the annual fee mode before the switch to the annual fee mode.
The switch to annual fee mode is not allowed when different NB-IoT versions are deployed on the
network.
Table 4-1 NB-IoT annual fee packages and packaged control items
Package
SBOM
Packaged Control
Item SBOM
Description
Licensing
Principles
ML1S0SWRTU
00
N/A
NB-IoT Software and
RTU Package (per
eNodeB)
One for each site
ML1S0SWRTU
00
ML1S0BASIC13
eNodeB NB-IoT Basic
Software, V100R013 (per
Cell)
ML1S0SWRTU
00
ML1SNBCVEX00
NB-IoT Coverage
Extension (per Cell)
Apply for one
package. The
maximum values of
the packaged
control items are
granted.
ML1S0SWRTU
00
ML1S0U4ARD00
UL 4-Antenna Receive
Diversity (per Cell)
ML1S0SWRTU
00
ML1S000SFN00
SFN (per Cell)
ML1S0SWRTU
00
ML1S00IMED00
Idle Mode eDRX (per
Cell)
ML1S0SWRTU
00
ML1S00MLTN00
Multi-tone (per Cell)
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
74
eRAN
License Management Feature Parameter Description
4 License Management
Package
SBOM
Packaged Control
Item SBOM
Description
ML1S0SWRTU
00
ML1S00RSCC00
NB-IoT RAN Sharing
with Common Carrier
(per Cell)
ML1S0SWRTU
00
ML1S00RSDC00
NB-IoT RAN Sharing
with Dedicated Carrier
(per Cell)
ML1S0SWRTU
00
ML1S000SPS00
Symbol Power Saving
(per Cell)
ML1S0SWRTU
00
ML1S000ACP00
Adaptive Power
Consumption (per Cell)
ML1S0SWRTU
00
ML1S00PISM00
PSU Intelligent Sleep
Mode (per Cell)
ML1S0SWRTU
00
ML1S000IBM00
Intelligent Battery
Management (per Cell)
ML1S0SWRTU
00
ML1SSDHARQ00
Dual HARQ (per Cell)
ML1S0SWRTU
00
ML1S0000MC01
Multi-Carrier (per
Carrier)
ML1S0SWRTU
00
ML1SSOTDOA00
OTDOA (per Cell)
ML1S0SWRTU
00
ML1S00SIUC00
Intra-eNodeB UL CoMP
(per Cell)
ML1S0SWRTU
00
ML1SCOTRAN00
2G/3G and eNodeB Cotransmission (per
eNodeB)
ML1S0SWRTU
00
ML1S0IPAPM00
IP Active Performance
Measurement (per
eNodeB)
ML1S0SWRTU
00
ML1S00EOAM00
Ethernet OAM (per
eNodeB)
ML1S0SWRTU
00
ML1S00OMCB00
OM Channel Backup (per
eNodeB)
ML1S0SWRTU
00
ML1S000BFD00
Bidirectional Forwarding
Detection (per eNodeB)
ML1S0SWRTU
00
ML1S000ELA00
Ethernet Link
Aggregation (IEEE
802.3ad) (per eNodeB)
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
Licensing
Principles
75
eRAN
License Management Feature Parameter Description
4 License Management
Package
SBOM
Packaged Control
Item SBOM
Description
ML1S0SWRTU
00
ML1SS1IPV600
S1 over IPv6 (per
eNodeB)
ML1S0SWRTU
00
ML1SIEIPV600
IEEE 1588v2 over IPv6
(per eNodeB)
ML1S0SWRTU
00
ML1S00ENSY00
Enhanced
Synchronization (per
eNodeB)
ML1S0SWRTU
00
ML1SINFIRE00
Integrated Firewall (per
eNodeB)
ML1S0SWRTU
00
ML1S000ACC00
Access Control based on
802.1x (per eNodeB)
ML1S0SWRTU
00
ML1SESPKIR00
eNodeB Supporting PKI
Redundancy (per
eNodeB)
ML1S0SWRTU
00
ML1SESMUPKI0
eNodeB Supporting
Multi-operator PKI (per
eNodeB)
ML1S0SWRTU
00
ML1SIPIPV600
IPsec for IPv6 (per
eNodeB)
ML1S0SWRTU
00
ML1S0IPSEC00
IPsec (per eNodeB)
ML1S0SWRTU
00
ML1SIPSERA00
IPsec Redundancy
Among Multiple SeGWs
(per eNodeB)
ML1S0SWRTU
00
ML1SDIGWHI00
eNodeB Supporting
Digital Certificate
Whitelist Management
(per eNodeB)
ML1S0SWRTU
00
ML1S00IPTB00
IPsec Tunnel Backup (per
eNodeB)
ML1S0SWRTU
00
ML1SIPSECRE0
eNodeB Supporting IPsec
Redirection (per eNodeB)
ML1S0SWRTU
00
ML1S0000PA00
RF Output Power (per
20W)
ML1S0SWRTU
00
ML1S00RFTC00
RF Transmit Channel
(per Channel)
ML1S0SWRTU
00
ML1S00RFRC00
RF Receive Channel (per
Channel)
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
Licensing
Principles
76
eRAN
License Management Feature Parameter Description
4 License Management
Package
SBOM
Packaged Control
Item SBOM
Description
ML1S0SWRTU
00
ML1S00RFDM00
RF Multi Mode
license(NB-IoT) (per
Sector)
ML1S0SWRTU
00
ML1S0000PA01
RF Output Power for
Blade and AAU (per
20W)
ML1S0SWRTU
00
ML1S00RFTC01
RF Transmit Channel for
Blade and AAU (per
Channel)
ML1S0SWRTU
00
ML1S00RFRC01
RF Receive Channel for
Blade and AAU (per
Channel)
ML1S0SWRTU
00
ML1S000MCA01
RF Multi Carrier for
Blade and AAU (per
Carrier)
ML1S0SWRTU
00
ML1S0LBBPM00
LBBP NB-IoT license
(per LBBP)
ML1S0SWRTU
00
ML1S00LMMM00
LMPT NB-IoT license
(per LMPT)
ML1S0SWRTU
00
ML1S000MCA00
RF Multi Carrier (per
Carrier)
ML1S0SWRTU
00
ML1S00BBTC00
BB Transmit Channel
(per Channel)
ML1S0SWRTU
00
ML1S00BBRC00
BB Receive Channel (per
Channel)
ML1S0SWRTU
00
ML1S00RFDM01
RF Multi Mode license
for Blade and AAU(NBIoT) (per Sector)
ML1S0SWRTU
00
ML1S0POW5R00
20W Power License for
5000 Series RF Module
(NB-IoT)
ML1S0SWRTU
00
ML1SRFTC5R00
Transmit Channel
License for 5000 Series
RF Module (NB-IoT)
(per Channel)
ML1S0SWRTU
00
ML1SRFRC5R00
Receive Channel License
for 5000 Series RF
Module (NB-IoT) (per
Channel)
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
Licensing
Principles
77
eRAN
License Management Feature Parameter Description
4 License Management
Package
SBOM
Packaged Control
Item SBOM
Description
ML1S0SWRTU
00
ML1SMUCA5R00
Multi-carrier License for
5000 Series RF Module
(NB-IoT) (per Carrier)
ML1S0SWRTU
00
ML1S5000FMRR
First Mode License for
5000 Series RF Module
(NB-IoT)
ML1S0SWRTU
00
ML1S5000MMRR
Multimode License for
5000 Series RF Module
(NB-IoT)
ML1S0SWRTU
00
ML1SFMFBMBM
0
First Mode First Band
License for Multi-Band
RF Module(NB-IoT) (per
Band per RRU)
ML1S0SWRTU
00
ML1SMMMBMB
M0
Multi-Mode Multi-Band
License for Multi-Band
RF Module(NB-IoT) (per
Band per RRU)
ML1S0SWRTU
00
ML1SUMPTMM00
UMPT Multi Mode
license(NB-IoT) (per
UMPT)
ML1S0SWRTU
00
ML1SUBBPFM00
UBBP First-Mode license
(NB-IoT) (per UBBP)
ML1S0SWRTU
00
ML1SUBBPMM00
UBBP Multi-Mode
license (NB-IoT) (per
UBBP)
ML1S00NBCN0
1
N/A
NB-IoT User Number
(per 100 NB-IoT User)
One is required for
every 100 users.
ML1S00NBCN0
1
ML1S0ATCUS00
NB-IoT User (per 100
NB-IoT User)
The number of
license units for this
item is the same as
the corresponding
package number.
For example, if one
package of
ML1S00NBCN01
is purchased, one
license unit for this
item is purchased
accordingly.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
Licensing
Principles
78
eRAN
License Management Feature Parameter Description
4 License Management
Package
SBOM
Packaged Control
Item SBOM
Description
Licensing
Principles
ML1S00NBCN0
1
ML1S00BHCA00
NB-IoT BHCA (per 100
BHCA)
Apply for one
package. The
maximum values of
the packaged
control items are
granted.
ML1S00BHCA0
1
N/A
NB-IoT BHCA (per 100
NB-IoT BHCA)
One is required for
every 100 BHCAs.
ML1S00BHCA0
1
ML1S00BHCA00
NB-IoT BHCA (per 100
BHCA)
The number of
license units for this
item is the same as
the corresponding
package number.
For example, if one
package of
ML1S00BHCA01
is purchased, one
license unit for this
item is purchased
accordingly.
ML1S00BHCA0
1
ML1S0ATCUS00
NB-IoT User (per 100
NB-IoT User)
Apply for one
package. The
maximum values of
the packaged
control items are
granted.
ML1S00NBCA0
1
N/A
NB-IoT Carrier (per
200KHz Carrier)
One is required for
each 200 kHz of a
carrier.
ML1S00NBCA0
1
ML1S00CELL00
NB-IoT Carrier (per
200kHz Carrier)
The number of
license units for this
item is the same as
the corresponding
package number.
For example, if one
package of
ML1S00NBCA01
is purchased, one
license unit for this
item is purchased
accordingly.
To apply for a license, you only need to apply for a package. The packaged control items are
automatically generated in the LKF. On the eNodeB, you can run the DSP LICINFO
command with Item Type set to PACKAGE_ONLY or ALL.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
79
eRAN
License Management Feature Parameter Description
4 License Management
4.3.2 LKF Structure
After the packaging scheme is used, the original SaleInfo field in the license file is changed,
and the PackageInfo field is added. The original KeyInfo field remains unchanged.
Package
A package contains the following fields (attributes):
l
PackageItem (name)
l
Value (validDate)
l
DesEng (unit)
l
Packaged control items
Packaged Control Item
A license control item in the package contains only the following fields (attributes):
l
SaleItem (name)
l
Value (validDate and noControl)
noControl indicates whether the authorization is controlled in the software. The options are
as follows:
l
The value yes indicates that there is no authorization control on a feature in the software
and the maximum value is automatically granted to the SBOM of the feature.
l
The value no indicates that a licensed value works in the software.
The noControl field is optional. If this field is not displayed, the default value is no.
4.4 Multi-Operator License Management
In a multi-operator sharing scenario, an Evolved UTRAN (E-UTRAN) is shared by operators.
A license purchase order is placed by only one party, which can be the primary operator or a
joint venture of the operators.
If operators share an E-UTRAN, each eNodeB still has only one LKF and the LKF specifies
all the limitations of the license for the operators.
The following license sharing schemes are available:
l
Separate capacities
l
Shared capacities
l
Separate features
l
Shared features
4.4.1 Separate Capacities
In the separate capacity scheme, capacities for each operator are specified separately by
setting percentages of the total licensed capacity purchased by the primary operator or a joint
venture of the operators. The sum of the capacities for the operators must be less than or equal
to the total licensed capacities.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
80
eRAN
License Management Feature Parameter Description
4 License Management
This scheme currently applies to traffic and UE count license control items. The UE count
license employs a static percentage policy whereas the traffic license uses a dynamic
percentage policy. The policies are described as follows:
l
Static percentage policy for the UE count license
Each operator owns a dedicated percentage of the licensed UEs. After the primary
operator or a joint venture of the operators purchases a UE capacity license, the
operators' percentages must be specified so that each operator's share of the licensed UEs
is confined to the specified percentage. The sum of the shares must not exceed the
licensed capacity.
l
Dynamic percentage policy for traffic license
The traffic capacity for each operator consists of the following percentages of the
licensed traffic rate:
1. Static percentage
Each operator owns a static percentage of the licensed traffic rate. After the primary
operator or a joint venture of the operators purchases a capacity license regarding the
traffic rate, each operator's percentage must be specified to enable license sharing. The
sum of the shares must not exceed the licensed capacity.
2. Capacity penetration percentage
A capacity penetration percentage is the percentage of the licensed traffic rate that can be
shared by operators. An operator can share part of its traffic capacity with another
operator when they have traffic capacity to spare. When traffic volume rises, the operator
reclaims the traffic capacity they shared.
For example, operators A and B share an eNodeB and their static traffic percentages are
both set to 50% and capacity penetration percentages are set to 10%. If the actual traffic
rate for operator A exceeds 50% of the total licensed traffic rate but operator B is below
50%, operator A can use up to 10% of operator B's portion of the traffic capacity.
NOTE
For details about how to set percentages for the licensed capacities, see RAN Sharing.
4.4.2 Shared Capacities
In the shared capacity scheme, the licensed capacities in an eNodeB are shared by operators.
The sum of the shares must not exceed the licensed capacity. This scheme currently applies to
power and bandwidth license control items.
4.4.3 Separate Features
In the separate feature scheme, each operator can deploy a separate set of features. For
example, operator A deploys automatic neighbor relation (ANR), whereas operator B does
not. A licensed set of features must be a combination of feature sets deployed by the
operators. Currently, this scheme does not apply to any optional features for the eNodeB.
4.4.4 Shared Features
In the shared feature scheme, all operators involved deploy the same set of features. This
scheme currently applies to all optional features for the eNodeB.
4.5 Network Analysis
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
81
eRAN
License Management Feature Parameter Description
4 License Management
4.5.1 Benefits
4.5.1.1 eNodeB Deployment
When an eNodeB is deployed, install a demo LKF with 255-day validity and ESN set to ANY
on eNodeBs for commissioning. After a purchase order is placed, Huawei engineers apply for
commercial LKFs based on the network plan for subsequent use.
Operations Related to Demo LKFs
When eNodeBs are deployed, commercial LKF allocation for the eNodeBs cannot be
determined, because of uncertainty of the network plan. Therefore, during eNodeB
deployment, demo LKFs must be installed on the eNodeBs for commissioning. Before
installing eNodeBs, contact Huawei engineers to obtain a demo LKF with 255-day validity
and ESN set to ANY. The demo LKF can be installed on any eNodeBs to facilitate
deployment.
Operations Related to Commercial LKFs
Demo LKFs are valid for only a limited period of time. When eNodeBs operate stably,
commercial LKFs must be created for the eNodeBs based on the network plan and installed
on the eNodeBs by Huawei engineers.
NOTE
Engineers may create commercial LKFs in a batch and install them on the corresponding eNodeBs in a
single operation. For details, see "Installing an LKF with ESN Set to ANY on a Number of eNodeBs".
4.5.1.2 R-Version Upgrade or Capacity Expansion
Commercial LKFs must be re-created by Huawei engineers upon R-version upgrades or
capacity expansion to meet requirements for the increasing traffic volume or new services.
Before re-creating an LKF for an NE, obtain the current LKF information and ESN of the NE
by referring to 4.6.3.1 License Operations on the U2020.
4.5.1.3 Licensed Capacity Adjustment
If the network plan is adjusted, commercial LKFs on NEs must be re-created by Huawei
engineers with adjusted licensed capacities for the NEs.
Before re-creating an LKF for an NE, revoke the LKF and obtain the current LKF
information, ESN of the NE, and LKF revocation code by referring to 4.6.3.1 License
Operations on the U2020.
NOTE
If a commercially permanent & fixed-term LKF is used, capacities can be adjusted only for permanent license
items. Capacities for fixed-term license items remain unchanged.
4.5.1.4 ESN Change
An LKF becomes invalid if the ESN of the corresponding NE changes or the LKF is moved
to another NE. In this situation, the LKF must be re-created with a correct value of ESN by a
Huawei engineer.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
82
eRAN
License Management Feature Parameter Description
4 License Management
Before re-creating an LKF, revoke the LKF and obtain the previous ESN information and
LKF revocation code by referring to 4.6.3.1 License Operations on the U2020 or running
the RVK LICENSE command.
NOTE
The LKF must be updated only when the BBU of the macro eNodeB or the module of the micro eNodeB is
replaced. If the main control board is replaced, there is no need to update the ESN. After the ESN is replaced,
the previous LKF (with the same ESN) needs to be installed on the new main control board or the module.
4.5.2 Requirements
4.5.2.1 Software
Prerequisite Functions
None
Mutually Exclusive Functions
None
4.5.2.2 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.5.2.3 Others
None
4.5.3 Impacts
Network Impacts
None
Function Impacts
None
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
83
eRAN
License Management Feature Parameter Description
4 License Management
4.6 Operation and Maintenance
4.6.1 Data Configuration
4.6.1.1 Data Preparation
Parameter
Name
Paramete
r ID
Setting Notes
Emergency
Switch State
SWITCH
Set this parameter to ON in case of an emergency (such as
an earthquake) where the NE is required to operate with the
maximum allowable data rate and serve the maximum
number of UEs, rather than be confined to the licensed
limits.
Function Type
FUNCTIO
NTYPE
Set this parameter to eNodeB if an eNodeB is used.
4.6.1.2 Using MML Commands
Activation Command Examples
//Turning on the emergency license state switch
SET LICENSECTRL:SWITCH=ON,FUNCTIONTYPE=eNodeB;
Deactivation Command Examples
//Turning off the emergency license state switch
SET LICENSECTRL:SWITCH=OFF,FUNCTIONTYPE=eNodeB;
4.6.2 Activation Observation
Step 1 Run the DSP LICINFO command, and check that the values of traffic and number of users
displayed in the Allocated column in the command output reach the maximum.
Step 2 Run the LST LICENSECTRL command to check that the Emergency Switch State
parameter value is ON.
----End
4.6.3 Common License Operations
This section describes common license operations on a U2020 client or an LMT.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
84
eRAN
License Management Feature Parameter Description
4 License Management
4.6.3.1 License Operations on the U2020
Section
Description
Synchronizing NE
Information
Describes how to synchronize ESN and license information of
eNodeBs to the U2020.
Prechecking LKFs
Describes how to precheck LKFs to be installed.
Loading Licenses
Describes how to install commercial or demo LKFs on
eNodeBs.
Revoking an LKF
Describes how to revoke a commercial LKF and how to export
the revocation information to the U2020.
Querying License
Information
Describes how to query license information about eNodeBs.
Adjusting License
Capacity
Describes how to adjust the license capacity of eNodeBs using
the U2020.
Checking Consistency
Between Existing
Licensed Values and
Data Configurations
Describes how to check consistency between existing licensed
values and data configurations and how to export the result to
the U2020.
Checking Consistency
Between an LKF to Be
Installed and Data
Configurations
Describes how to check consistency between the LKF to be
installed and data configurations and how to export the result
to the U2020.
Exporting NE
Application Information
Describes how to export license application information of an
NE to the U2020.
Backing Up LKFs
Describes how to back up the LKFs of eNodeBs on the
U2020.
Obtaining Backup
LKFs
Describes how to obtain backup LKFs from the U2020 and
save them locally.
Restoring LKFs
Describes how to load the eNodeB LKFs backed up on the
U2020 to the eNodeBs.
Exporting SBOM
Statistics
Describes how to export SBOM statistics of eNodeBs.
Synchronizing NE Information
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Click NE License Maintenance Operation and select Synchronize NE Information.
Step 4 Select the NEs whose information you want to synchronize.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
85
eRAN
License Management Feature Parameter Description
4 License Management
Step 5 Click OK.
----End
Prechecking LKFs
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Check License.
Step 5 In the Check License dialog box, select Check license and click Next.
Step 6 Click
l
.
If the LKF is in the TXT, DAT, or XML format:
a.
In the Open dialog box, select an LKF in the TXT, DAT, or XML format, and click
Open. In the Check License dialog box, click Next.
b.
In the Map NE wizard, click Select.
c.
In the Select NE dialog box, select the NE whose license is to be checked, click
, and click OK.
l
d.
In the Check License dialog box, click Next.
e.
. In the Save dialog box, set the file name, save path, and file type, and
Click
click Save. The result can be saved in .csv, .xls, .xlsx, or .xml format. In an .xls
or .xlsx file, a cell can support a maximum of 32,767 characters.
If the LKF is in the ZIP format:
a.
In the Open dialog box, select the LKF, and click Open. In the Check License
dialog box, click Next.
The LKFs that successfully match NEs in the OSS are automatically selected and
the NE names are displayed in the NE Name column. The LKFs that do not match
NEs in the OSS are not selected.
b.
You can select LKFs to be delivered to NEs as required.
c.
Click Next.
d.
Set the precheck result save path.
Step 7 Click Finish.
----End
Loading Licenses
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
86
eRAN
License Management Feature Parameter Description
4 License Management
Step 4 Click NE License Maintenance Operation and select Load License File.
Step 5 In the Load License File dialog box, click
l
l
.
If the LKF is in the TXT, DAT, or XML format:
a.
In the Open dialog box, select the LKF, and click Open.
b.
In the Load License File dialog box, click Next.
c.
In the Load License File dialog box, click Select.
d.
In the Select NE dialog box, select the NE, click
, and click OK.
If the LKF is in the ZIP format:
a.
In the Open dialog box, select the LKF, and click Open.
b.
In the Load License File dialog box, click Next.
The LKFs that successfully match NEs in the OSS are automatically selected and
the NE names are displayed in the NE Name column. The LKFs that do not match
NEs in the OSS are not selected.
c.
You can select LKFs to be delivered to NEs as required.
Step 6 Click Finish.
----End
Revoking an LKF
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Revoke License.
Step 5 In the Confirm dialog box, click Yes to confirm that you want to revoke the stand-alone
license.
Step 6 Select the NE whose LKF is to be revoked.
Step 7 Set the export path for revoked license information.
Step 8 Click OK.
----End
Querying License Information
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose License Maintenance
Query.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Set filter criteria.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
87
eRAN
License Management Feature Parameter Description
4 License Management
NOTE
If filter criteria have been set, click Filter.
1.
In the License States area of the Filter dialog box, set the license state.
2.
In the Device area, click Select.
3.
In the Select NE dialog box, select the required NE and click
4.
In the Select NE dialog box, click OK.
5.
In the Filter dialog box, click OK.
.
Step 5 The right list of the License Information Query node displays information corresponding to
the queried license. Select a stand-alone license record. In the Details area, you can view the
detailed information about a stand-alone license.
----End
Adjusting License Capacity
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Adjust License Capacity. In the
Confirm dialog box, click Yes.
Step 5 Select the NE whose LKF you want to adjust.
Step 6 Set the export path for the license capacity adjustment application file.
Step 7 Click OK.
Step 8 In the NE License Maintenance panel, choose NE License Maintenance Operation > Load
License File to load the new license file onto the NE. For details, see Loading Licenses.
----End
Checking Consistency Between Existing Licensed Values and Data
Configurations
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Check License.
Step 5 In the Check License dialog box, select Check configuration data and click Next.
Step 6 Select Existing license file, and click Next.
Step 7 Select the NE to be checked.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
88
eRAN
License Management Feature Parameter Description
4 License Management
Step 8 In the Select Export Path wizard, click Next.
Step 9 Set the check result save path.
Step 10 Click Finish.
----End
Checking Consistency Between an LKF to Be Installed and Data Configurations
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Check License.
Step 5 In the Check License dialog box, select Check configuration data and click Next.
Step 6 Select New license file and click
l
l
.
If the LKF is in the TXT, DAT, or XML format:
a.
In the Open dialog box, select the LKF, and click Open. In the Check License
dialog box, click Next.
b.
Select the NE to be checked.
c.
In the Map NE wizard, click Next.
d.
Set the check result save path.
If the LKF is in the ZIP format:
a.
In the Open dialog box, select the LKF, and click Open. In the Check License
dialog box, click Next.
The LKFs that successfully match NEs in the OSS are automatically selected and
the NE names are displayed in the NE Name column. The LKFs that do not match
NEs in the OSS are not selected.
b.
You can select LKFs to be delivered to NEs as required.
c.
Click Next.
d.
Set the check result save path.
Step 7 Click Finish.
----End
Exporting NE Application Information
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Export NE Application
Information.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
89
eRAN
License Management Feature Parameter Description
4 License Management
Step 5 Select the NE for which you want to apply for a license.
Step 6 Set the path for saving the stand-alone license application information.
Step 7 Click OK.
Step 8 Send the exported NE application information to Huawei technical support engineers for them
to apply for a stand-alone license.
----End
Backing Up LKFs
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Back Up License File.
Step 5 Select the NE for which you want to back up its license.
Step 6 Click OK.
----End
Obtaining Backup LKFs
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Obtain Backup License File.
Step 5 Select the NE whose backup LKF you want to obtain.
Step 6 Set the path for saving the backup LKF.
Step 7 In the Obtain Backup License File dialog box, click OK.
----End
Restoring LKFs
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select Restore License File.
Step 5 Select the NE for which you want to restore its license.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
90
eRAN
License Management Feature Parameter Description
4 License Management
Step 6 Select Active or Inactive in the License Type area in the Restore License File dialog box.
l
If you select Active, the U2020 uses an active backup file to restore the license. That is,
the U2020 uses an active backup file under <Shared directory>/Product/
CommonLicService/var/standaloneNELicense/active/<Product name> in the server to
restore the license.
l
If you select Inactive, the U2020 uses an inactive backup file to restore the license. That
is, the U2020 uses an inactive backup file under <Shared directory>/Product/
CommonLicService/var/standaloneNELicense/inactive/<Product name> in the server to
restore the license.
Step 7 Click OK.
Step 8 In the Confirm dialog box, click Yes.
----End
Exporting SBOM Statistics
Step 1 Choose License > NE License Management > Stand-Alone.
Step 2 In the Stand-Alone License Management navigation tree, choose NE License
Maintenance.
Step 3 Select a product from the Current Product drop-down list and click Apply.
Step 4 Click NE License Maintenance Operation and select SBOM Information.
Step 5 Select the NE whose SBOM statistics you want to export.
Step 6 Set the export path.
Step 7 Click OK.
----End
4.6.3.2 License Operations on an LMT
To...
Run...
Description
Precheck or
install an LKF
INS
LICENSE
l If the PREFLG parameter is set to YES(Yes), this
command is used to precheck an LKF.
NOTE
Set the FLG parameter to NO(No) before using the LKF
precheck function.
l If the PREFLG parameter is set to NO(No), this
command is used to download an LKF to an NE
and activate the LKF. The LKF can be a
commercial, demo, or commercially permanent &
fixed-term LKF.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
91
eRAN
License Management Feature Parameter Description
4 License Management
To...
Run...
Description
Activate an
LKF
ACT
LICENSE
This command is used to activate an LKF on the NE.
l If the PREFLG parameter is set to YES(Yes), this
command is used to precheck an LKF.
NOTE
Set the FLG parameter to NO(No) before using the LKF
precheck function.
l If the PREFLG parameter is set to NO(No), this
command is used to activate an LKF. The LKF can
be a commercial, demo, or commercially
permanent & fixed-term LKF.
NOTE
If the FLG parameter is set to YES(Yes), a minor error
that occurs during the installation will be ignored and the
LKF will be installed forcibly.
Turn on the
emergency
license state
switch
SET
LICENSECT
RL
This command is used to turn on the emergency
license state switch. After this command is executed,
the eNodeB enters the emergency license state. In this
state, the eNodeB operates with the maximum
allowable data rate and serves the maximum number
of UEs, rather than be confined to the licensed limits.
An eNodeB of an R version can enter the emergency
license state up to three times and remain in that state
for up to seven days each time. This command does
not apply to the USU.
Revoke an LKF
RVK
LICENSE
This command is used to revoke the LKF that is in
use.
Upload an LKF
ULD
LICENSE
This command is used to upload an LKF for NEspecific LKF backup.
Query the status
of the
emergency
license state
switch
LST
LICENSECT
RL
This command is used to query whether the
emergency license state switch is turned on. This
command does not apply to the USU.
Query LKF
information
LST
LICENSE
This command is used to query information about an
LKF. Information (such as the number, name,
activation time, and status) about all LKFs on the
current eNodeB can be queried.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
92
eRAN
License Management Feature Parameter Description
4 License Management
To...
Run...
Description
Query the
license
configuration
DSP
LICINFO
This command is used to query the license status, time
to enter the grace period, and license configurations of
the eNodeB. The following configurations are
included:
l Operator Index
l Operator Name
l Model
l Description
l Allocated
l Config
l Actual Used
l Unit
l Expiration Date
NOTE
Config indicates the value of a license control item
configured on the eNodeB, and it does not indicate the
actually consumed value. Actual Used indicates the actually
consumed value of a license control item after the cell is
activated.
Query LKF
information
DSP
LICENSE
This command is used to query the license
configuration of a USU.
Check the
consistency
between
licensed values
and data
configurations
CHK
DATA2LIC
This command is used to check whether the data
configurations of an eNodeB are consistent with an
LKF. This LKF can be either a specified file or the
LKF that currently takes effect on the eNodeB (the
default). If there is any inconsistency, the command
output displays the license control items involved and
the following information about the corresponding
configuration objects: type, name (if involved),
attributes (if involved), and quantity (required for
resource items).
Set the
thresholds for
generating or
clearing a
license overload
alarm
SET
ENBLICENS
EALMTHD
This command is used to change the thresholds for
generating or clearing a license overload alarm and the
durations involved. The following parameters are
included:
l eNBLicenseAlmThd.OTHD (indicates the
threshold for generating the alarm)
l eNBLicenseAlmThd.OPRD (indicates the alarm
detection duration)
l eNBLicenseAlmThd.RTHD (indicates the
threshold for clearing the alarm)
l eNBLicenseAlmThd.RPRD (indicates the alarm
clearing duration)
This command does not apply to the USU.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
93
eRAN
License Management Feature Parameter Description
4 License Management
To...
Run...
Description
Query the
thresholds for
generating or
clearing a
license overload
alarm
LST
ENBLICENS
EALMTHD
This command is used to query the thresholds for
generating or clearing a license overload alarm and the
durations involved. This command does not apply to
the USU.
Set the status of
fixed-term
license items
SET
FIXTERMLI
CSWITCH
This command is used to control whether fixed-term
license items take effect. The default value is ON(On),
indicating that the fixed-term license items are
effective.
This command is effective only for commercially
permanent & fixed-term LKFs. When an LKF of any
type is reloaded or the eNodeB experiences a cross-R
version change, the switch will restore to its default
value.
Query the status
of fixed-term
license items
LST
FIXTERMLI
CSWITCH
This command is used to query the status of the switch
controlling fixed-term license items.
Query license
revocation
information
DSP
RVKLICINF
O
This command is used to query revocation information
about an LKF.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
94
eRAN
License Management Feature Parameter Description
5 Possible Issues
5
Possible Issues
5.1 Faults Occurred During Installation
l
Major Errors
If a major error occurs during LKF installation, the installation fails. The following table
describes error messages indicating major errors and provides recommended actions.
Error Message
Recommended Action
License file validation failed.
Reapply for an LKF.
The license sequence number is already revoked.
Reapply for an LKF.
The license file does not belong to the product.
l If the software version is
correct, apply for and install an
LKF with the correct product
name.
l If the LKF is correct, install it
on an eNodeB with the same
product name.
License file check failed because the file expires.
Reapply for an LKF.
Days when the commissioning license with the ESN
of ANY is allowed to use have elapsed.
Install a commercial LKF, or install
a demo LKF with ESN not set to
ANY.
The license file with ESN or version mismatched
cannot be activated repetitively.
l If the software version is
correct, apply for and install an
LKF matching the ESN or
version.
l If the LKF is correct, install it
on an eNodeB with the same
ESN or Version.
The ESN indicated in the license file differs from
the ESN of the NE.
Issue Draft A (2019-01-05)
Apply for and install an LKF with
the correct ESN.
Copyright © Huawei Technologies Co., Ltd.
95
eRAN
License Management Feature Parameter Description
5 Possible Issues
Error Message
Recommended Action
The configuration value of the basic control item is
greater than the value in the license file.
Apply for and install an LKF with
the basic control item.
NOTE
Currently, eNodeB basic software is the only basic control
item.
The system displays "The value of a license control
item in the license file is smaller than its minimum
value." and provides a list of involved control items.
l
Check whether the values of the
license control items in the new
LKF are smaller than the minimum
values. If yes, change the values to
be larger than or equal to the
minimum values and reapply for a
new LKF.
Minor Errors
–
If error messages indicating minor errors are displayed during LKF installation and
forced installation is selected, LKFs can be successfully installed.
–
If forcible installation is not selected, LKFs can be successfully installed only after
the recommended actions are taken.
If a minor error occurs during LKF installation on an eNodeB and the U2020 displays
"Major error" or "Major error (risk involved)" and reminds users that forcible LKF
installation will affect services, you are advised to resolve the error and then install the
LKF.
Error Message
Recommended Action
The version indicated in the
license file differs from the
active version of the NE.
l If the software version is correct, apply for and install
an LKF with the same Version.
l If the LKF is correct, install it on an eNodeB with the
same Version.
l If neither of these recommended actions is taken or
they do not produce the desired result, the eNodeB
will enter the 60-day grace period after the LKF is
forcibly installed and takes effect.
The system displays "The
actual value of a license
control item is greater than the
value in the license file." and
provides a list of involved
control items.
Check whether the values of the control items in the new
LKF are correct.
The system displays "The
license control item has
exceeded the deadline but has
not exceeded the grace
period." and provides a list of
involved control items.
Check whether the expiration dates in the new LKF are
correct.
Issue Draft A (2019-01-05)
l If yes, forcibly install the new LKF.
l If no, change the values of the control items and
reapply for an LKF.
l If the dates are correct, forcibly install the new LKF.
l If the dates are incorrect, change the expiration dates
and reapply for an LKF.
Copyright © Huawei Technologies Co., Ltd.
96
eRAN
License Management Feature Parameter Description
5 Possible Issues
Error Message
Recommended Action
The system displays "The
license control item has
exceeded the grace period."
and provides a list of involved
control items.
Check whether the expiration dates in the new LKF are
correct.
l If the dates are correct, forcibly install the new LKF.
l If the dates are incorrect, change the expiration dates
and reapply for an LKF.
The eNodeB configuration takes effect based on the configured values of the control items in
an LKF when the LKF is forcibly installed on an eNodeB (with two exceptions). The
exceptions are as follows:
NOTE
Maximum value (Vmax): indicates the maximum value of a license item supported by an NE
Minimum value (Vmin): indicates the minimum value of a license item supported by an NE
l
If the licensed value of an item in the LKF is less than Vmin:
For a commercial or demo LKF, the licensed value of an item is equal to Vmin. For a
commercially permanent & fixed-term LKF:
l
–
If the licensed value of an item with a commercially permanent date plus the
licensed value of the item with a fixed-term date is less than Vmin, then the
licensed value of the item with the commercially permanent date is equal to Vmin
while the licensed value of the item with the fixed-term date is equal to that in the
LKF.
–
If the licensed value of an item with a commercially permanent date plus the
licensed value of the item with a fixed-term date is larger than Vmin but the
licensed value of the item with the commercially permanent date is less than Vmin,
then the licensed value of the item with the commercially permanent date is equal to
Vmin while the licensed value of the item with the fixed-term date is equal to that
in the LKF.
If the licensed value of an item in the LKF is larger than Vmax:
For a commercial or demo LKF, the licensed value of an item is equal to Vmax. For a
commercially permanent & fixed-term LKF:
–
If the licensed value of an item with a commercially permanent date plus the
licensed value of the item with a fixed-term date is larger than Vmax and the
licensed value of the item with the commercially permanent date is greater than
Vmax, then the licensed value of the item with the commercially permanent date is
equal to Vmax while the licensed value of the item with the fixed-term date is equal
to 0.
–
If the licensed value of an item with a commercially permanent date plus the
licensed value of the item with a fixed-term date is larger than Vmax and the
licensed value of the item with the commercially permanent date is less than or
equal to Vmax, then the licensed value of the item with the commercially
permanent date is equal to that in the LKF while the licensed value of the item with
the fixed-term date is equal to Vmax minus the licensed value of the item with the
commercially permanent date.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
97
eRAN
License Management Feature Parameter Description
5 Possible Issues
5.2 Faults During Operation
For details about alarms and events related to faults during operation, see 5.3 Alarms and 5.4
Events.
5.3 Alarms
Alarm ID
Alarm Name
Alarm Severity
26812
System Dynamic Traffic Exceeding
Licensed Limit
Major
26815
Licensed Feature Entering KeepAlive Period
Major
26816
Licensed Feature Unusable
Major
26817
License on Trial
The alarm severity level
is major at the beginning
and then changed to
critical when the license
file has entered the grace
period and the remaining
days before an expiry is
less than or equal to
seven days.
26818
No License Running in System
Critical
26819
Data Configuration Exceeding
Licensed Limit
Major
NOTE
In inter-eNodeB SFN based on coordinated eNodeB and inter-eNodeB adaptive SFN/SDMA based on
eNodeB coordination scenarios, if the licenses on both the primary and auxiliary BBUs do not meet
service requirements, ALM-26819 will be reported only on the primary BBU. If the license on the
primary BBU meets service requirements but that on the auxiliary BBU does not, this alarm will be
reported on the auxiliary BBU.
ALM-26812 System Dynamic Traffic Exceeding Licensed Limit is unavailable for USUs.
5.4 Events
Event ID
Event Name
Event Severity
26820
License Emergency Status Activated
Warning
26821
License Emergency Status Ceased
Warning
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
98
eRAN
License Management Feature Parameter Description
6 Parameters
6
Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l
Node Parameter Reference: contains device and transport parameters.
l
eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version on the live network from
the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
99
eRAN
License Management Feature Parameter Description
7 Counters
7
Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l
Node Performance Counter Summary: contains device and transport counters.
l
eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1 Open the EXCEL file of performance counter reference.
Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
100
eRAN
License Management Feature Parameter Description
8 Glossary
8
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue Draft A (2019-01-05)
Copyright © Huawei Technologies Co., Ltd.
101
eRAN
License Management Feature Parameter Description
9 Reference Documents
9
1.
RAN Sharing
2.
License Control Item Lists (FDD)
3.
License Control Item Lists (TDD)
4.
License Control Item Lists (CIoT)
Issue Draft A (2019-01-05)
Reference Documents
Copyright © Huawei Technologies Co., Ltd.
102