ZTE LR14 LTE FDD License Feature Guide

ZTE LTE FDD License
Feature Guide
LR14
ZTE LTE FDD License Feature Guide

Version Date Author Reviewer Notes
Wang
V1.0 2014/08/20 Li Chunyan First Release version
Zhuanli
1 Add the eNodeB level license state
management
2 Modify the limit exceeding alarms about
Wang eNodeB level
V2.0 2015-01-07 Li Chunyan
Zhuanli 3 Add the general description about
eNodeB level
4 Add the eNodeB level alarms
5. Change the word template
© 2015 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential & Proprietary 1

TABLE OF CONTENTS
1 Introduction ....................................................................................................... 7
1.1 Scope .................................................................................................................. 7
1.2 Target Group ....................................................................................................... 7
1.3 Feature Attribute .................................................................................................. 7
2 Function Description......................................................................................... 8
2.1 Network-Level License Management ................................................................... 9
2.1.1 Management Mode .............................................................................................. 9
2.1.2 File Description .................................................................................................... 9
2.2 eNodeB-Level License Management ................................................................. 13
2.2.1 Control Item Types............................................................................................. 13
2.2.2 License Files ...................................................................................................... 14
2.2.3 File Description .................................................................................................. 15
3 Technical Description ..................................................................................... 18

3.1 Network-Level License Management ................................................................. 18
3.1.1 File Management ............................................................................................... 20
3.1.2 Information Queries ........................................................................................... 21
3.1.3 Limit Exceeding Alarms...................................................................................... 22
3.1.4 Emergent Cancellation of License Restriction .................................................... 22
3.1.5 File Expiry .......................................................................................................... 23
3.1.6 Temporary Capacity Expansion ......................................................................... 23
3.1.7 Reports .............................................................................................................. 23
3.1.8 Multi-Time-Zone DST ......................................................................................... 24
3.1.9 Protection under Link Disconnection .................................................................. 24
3.1.10 Pre-Authentication ............................................................................................. 24
3.2 eNodeB-Level License Management ................................................................. 25
3.2.1 File Management ............................................................................................... 25
3.2.3 Limit Exceeding Alarms...................................................................................... 27
3.2.5 File Expiry .......................................................................................................... 29
3.2.6 Status Management ........................................................................................... 30
3.2.7 Temporary Capacity Expansion ......................................................................... 32
3.2.8 Reports .............................................................................................................. 32
4 Key Parameters and Configuration ................................................................ 33

4.1.1 File Management ............................................................................................... 33
2 ZTE Confidential & Proprietary


4.1.3 License file rollback............................................................................................ 37
4.1.4 Reports .............................................................................................................. 38
4.1.5 Pre-Authentication ............................................................................................. 39
4.2 eNodeB- Level License Management ................................................................ 43
4.2.1 File Management ............................................................................................... 43
5 Alarm ................................................................................................................ 53
5.2 eNodeB- Level License Management ................................................................ 54
5.2.1 Plat Alarm .......................................................................................................... 54
5.2.2 LTE FDD Alarm ................................................................................................. 54
6 Function Tests .................................................................................................. 55

6.1 Network-Level Function Tests ............................................................................. 55
6.1.1 Importing/Loading/Update Function Tests for a License File ................................ 55
6.1.2 Exporting Function Test for a License File ............................................................ 57
6.1.3 Rollback Function Test for the License File ........................................................... 58
6.1.4 Authorization and Usage Tests for the License File ............................................... 59
6.2 eNodeB-Level Function Tests .............................................................................. 62
6.2.1 File Management Function Test ........................................................................... 62
6.2.2 Information Query Function Test ......................................................................... 66
7 Abbreviations .................................................................................................. 73

FIGURES
Figure 2-1 Location of the License Management System in the Network ............................ 9
Figure 3-1 System Composition Diagram ...........................................................................19
Figure 3-2 Emergency Command ......................................................................................29
Figure 4-1 Import License file.............................................................................................33
Figure 4-2 Push license file to license control center..........................................................34
Figure 4-3 Formal License File ..........................................................................................35
Figure 4-4 Trial License File...............................................................................................36
Figure 4-5 Authorized Value ..............................................................................................36
Figure 4-6 Information Queries ..........................................................................................37
Figure 4-7 License file rollback ..........................................................................................38
Figure 4-8 Export Report ...................................................................................................39
Figure 4-9 Entrance of SubNetwork Level License Pre-authentication ...............................40
Figure 4-10 Authentication .................................................................................................41
Figure 4-11 Temporary Opening ........................................................................................42
Figure 4-12 Set Temporary Openning ................................................................................42
Figure 4-13 Entrance of LTE eNodeB Level License Management ....................................43
Figure 4-14 Import License File .........................................................................................44
Figure 4-15 Load License File ............................................................................................45
Figure 4-16 Query License File Brief Information ...............................................................46
Figure 4-17 Query License File Detailed Information .........................................................47
Figure 4-18 View Detail Information ...................................................................................48
Figure 4-19 Query License System Status .........................................................................49
Figure 4-20 Query License Function Item Usage ...............................................................50
Figure 4-22 export the query result ....................................................................................51
Figure 4-23 Configuration data unmatched with the License ..............................................51
Figure 4-24 Query License Authentication Result ..............................................................52

Figure 4-26 Set LicenseEmergency ...................................................................................53

Figure 6-1 Function Test Environment for Making a License File .......................................55
Figure 6-2 AISG Function Fails ..........................................................................................61
Figure 6-3 AISG Function Succeeds ..................................................................................61
Figure 6-4 Selecting LTE eNodeB Level License Management .........................................63
Figure 6-5 Importing a License File ....................................................................................64
Figure 6-6 Selecting the License File of the Corresponding Version ..................................64
Figure 6-7 License File Is Successfully Loaded .................................................................65
Figure 6-8 Loading the License File to the eNodeB ...........................................................66
Figure 6-9 Selecting the Base to Be Queried .....................................................................68
Figure 6-10 Brief Information Is Successfully Queried........................................................68
Figure 6-11 Exporting the Query Result .............................................................................69
Figure 6-12 Selecting the Base to Be Queried ...................................................................69
Figure 6-13 Detailed Information Is Successfully Queried ..................................................70
Figure 6-15 Querying Function Items .................................................................................71
Figure 6-16 Function Item Information Is Successfully Queried..........................................71
Figure 6-18 Querying the System Status ...........................................................................72
Figure 6-19 System Status Is Successfully Queried ...........................................................73
TABLES
Table 5-1 Related Alarms ..................................................................................................53

Table 5-2 Related License Alarms of Plat ..........................................................................54
Table 5-3 Related License Alarms of LTE FDD..................................................................54
Table 6-1 Tested Devices ..................................................................................................55

Table 6-2 Importing/Loading/Update Function Tests for a License File ..............................56

Table 6-3 Exporting Function Test for a License File .........................................................57
Table 6-4 Rollback Function Test for the License File ........................................................58
Table 6-5 Authorization and Usage Tests for the License File ...........................................59
Table 6-6 Test Criteria for the File Management Function .................................................62
Table 6-7 Test Criteria for the Information Query Function.................................................66

1 Introduction
1.1 Scope
This document describes license feature or technology within the eNodeB in LTE
network. The main contents comprise the following: technical description, key
parameters and configuration, related counters, KPI statistics and alarms.
1.2 Target Group
This document is intended for:
 Personnel who need to understand FDD License function
 Personnel who work with ZTE products
1.3 Feature Attribute
 For FDD single-mode eNodeB V3.20.50.20 series:
OMMB version: V12.13.58
EMS version: V12.13.58
 For GUL multi-mode eNodeB V4.13.15series:
OMMB version: V12.13.52
EMS version: V12.13.51
Note:

FDD single-mode V3.20.50.20 corresponds to GUL multi-mode V4.13.15, and LTE

technology description and operation requirements in the corresponding versions are the
same.
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
√ √ √ - - - - -
Note:
*-: Not involved
*√: involved
2 Function Description
License management (software license management) is intended to provide
corresponding network functions and performance resources based on the software
licenses purchased by users.
The LTE license provides the corresponding network functions and capacity through
software control. This enables carriers to purchase the corresponding number of licenses
based on the growth and development of network services for network expansion and
upgrade. In this way, carriers can establish high-quality, low-TCO, and future-oriented
smooth-upgrade networks.
The LTE license management includes the network-level license management and
eNodeB –level license management. The control nodes for the network-level license
management are located on the OMC and there is only one license file for the entire
network. The control nodes for the eNodeB level license management are located on
BSs, and there is one license file for each BS.

2.1 Network-Level License Management
2.1.1 Management Mode
The license management system using the server/client architecture is developed in the
JAVA language, and supports the Solaris, Linux, and other operating systems. The
license server loads license files, and provides the license inspection after the
EMS/OMM is started and establishes a connection to the license server. You can view
information about the authorization and use of the licenses on a license client.
Figure 2-1 Location of the License Management System in the Network
As shown in the above figure, the licenses of the entire network are controlled in the
license management system. When the EMS/OMM is started and establishes a
connection to the network, changes the configuration, or uploads data from the NE, the
use of various licenses is calculated. Moreover, the EMS/OMM sends a request to the
license management system, and the system determines whether the modification is
allowed. At the same time, the EMS/OMM reports the use of licenses to the license
management system periodically, so that the system can timely update the authorization
information about the licenses used by the EMS/OMM.
The license of the LTE system is composed of a formal license file and multiple trial
license files (optional).
2.1.2 File Description
License files are stored in an encrypted manner. A product may have multiple license
files, including a formal license file and multiple trial license files. The formal license file
(required) is the unique certificate to ensure the normal operation of the network under
the control of the license management system. Trial license files are optional.

Trial license files must be used along with the formal license file, and they cannot be
used after the expiration date. The license management system performs authorization
through the formal license file and trial license files.
Both the formal license file and trial license files have the latest validation dates. After the
dates are expired, these files cannot be used. By default, license files are effective within
half a year after they are made.
A license file is composed of the following items:
1. Standard license information:
 contract number: contract number, 23 digits.
 last contract number: required only for the trial license. The setting is the same
as the contract number of the formal license.
 customer name
 license type: FORMAL (no effect date and invalidation date), TRIAL (both
effect date and invalidation date are required), and GROUP.
 sn
 publish date
 use date
 maker
 maker department
 product name
 product version
 product number
 manager center
 macbind type

 mac info
 hard lock
 hard lock ID
 effect date
 invalidation date
 awake date
 awake text
 expire text
 modify or adjust
 official rise rate
 temporary open
 temporary open days
 temporary open times
2. Operator list: lists the information about all operators contained in the license. This
list helps to determine the authorization for each operator when the network is
shared among these operators.
 Operator ID
 Chinese Name
 English Name
 MCC and MNC
3. Group list: A group in a license file is a set of license authentication objects, and has
no association with the group objects on the EMS. The objects in the same group
can share the license function items for the group. Each operator in a group must be

included in all quantitative authentication items involved in function items. Switch

items, index items, and specific restrictions are consistent for a single NE or the
whole network. Therefore, it is unnecessary to specify them by group.
 Group ID
 Group Type
 Group Name
 English Name
4. NE list: lists all NEs. This is helpful to group NEs or split licenses, and grant
authorization to NE indexes and specific items.
 NE ID: The MeID is defined as a sub-network number, and is in the format of

“LTE_SubNetwork[**]” (where, ** is the sub-network number in the network
management system, and other characters are fixed format and are
case-sensitive).
 Associated Group: the group that the sub-network belongs to.
 NE Name
 English Name
5. Function item list: lists all function items for displaying function names.
 Feature ID
 Feature Type: number-type or switch-type
 Chinese Name
 English Name
6. General authorization: All authorization items in function items must be confirmed

by operator. The authorization number, authorization switch, authorization indexes,
and authorization strings are determined based on the types of different
authorization item types.

 Number-type authorization items:
Operator ID
Authorization Range
Authorized Object
Function Item ID
Authorization Number
 Switch-type authorization items:
Operator ID
Authorization Range
Authorized Object
Function Item ID
Enabled or Not: Y (the user purchases the function, and the switch is enabled)
or N (the user does not purchase the function, and the switch must not be
enabled)
Whether the Authorization Period is Defined
Expiration Date
2.2 eNodeB-Level License Management
2.2.1 Control Item Types
License control items are divided into the following types:
1. License of function switch type

The license of this type is used to perform license control on independent sales. The
license control of function switch type is performed on all optional functions
described in the feature list in the pre-sale document. The license of this type
enhances perception and optimizes services. The users can purchase the functions
based on their features.
2. License of number type
License of this type includes the license control items related to hardware capacity
and the Number allowed to use the license. A hardware capacity-related license
includes the maximum number of RRC_connected users, maximum traffic volume,
maximum bandwidth, and maximum power consumption. The function-type number
control items include the number of super cells and the number of carrier aggregated
cells. Users can purchase the corresponding number-type licenses based on the actual
network features and local use habits. The maximum capacity that the system
supports does not need to be purchased, so that resources can be properly utilized
and cost can be reduced.
2.2.2 License Files
2.2.2.1 File Types
Based on application scenarios, license files are divided into the following types:
1. Formal license files
Formal license files are also commercial license files, and they are generated based
on commercial contracts.
2. Trial license files
Trial license files are temporarily used during commissioning. The control items in
the files have the same deadline. Trial file types are as follows:
i. The trial license files (validity: three months) for a specified NE: can be loaded
only three times.

ii. The trial license files (validity: six months) for all NEs: The version file of an NE
can be loaded only once.
iii. The temporary license files (validity: one year) for all NEs: The number of times
that the license file is loaded is not restricted. As a special file, this file can only
be automatically loaded rather than manually loaded on the OMC. When the
hardware bound to the file changes and the NE has no matched file, this file is
automatically loaded to the NE.
2.2.2.2 License File Management
License file management supports the following:
1. Generating license files. License files are generated by the ZTE IT system in an
encrypted manner.
2. Loading license files. License files can be loaded from the network management
system to a BS in automatic loading mode or manual loading mode. License files can
be loaded in batches, or a BS can be specified to load the corresponding license
file.
3. Checking license files. A validity check can be performed for the formats of license
files, including the version number, hardware sequence number, digital signature,
and the information field for each item.
4. Querying license files. The contents and authorization information about license
files can be viewed in real time.
5. Invalidating license files. When the system is upgraded or license files need to be
replaced, the license files in use must be invalidated.
6. Reports: License contents can be exported from the OMC system to excel files.
2.2.3 File Description
A license file is composed of the following items:
1. Standard license information:

 contract number: contract number, 23 digits.
 last contract number: required only for the trial license. It is the same as the
contract number of the formal license.
 Customer name
 License type: FORMAL (no effect date and invalidation date) or TRIAL (both
the effect date and invalidation date are required)
 sn
 publish date
 use date
 maker
 maker department
 product name
 product version
 product number
 manager center
 macbind type
 mac info
 hard lock
 hard lock ID
 effect date
 invalidation date
 awake date

 awake text
 expire text
 modify or adjust
 official rise rate
 temporary open
 temporary open days
 temporary open times
2. Operator list: lists the information about all operators contained in the license. This
can determine the rights granted to each operator when the network is shared
among these operators.
 Operator ID
 Chinese Name
 English Name
 MCC and MNC
3. Function item list: lists all function items for displaying function names.
 Feature ID
 Feature Type: number-type or switch-type
 Chinese Name
 English Name
4. General authorization: All authorization items in function items must be confirmed

by operator. The authorization number, authorization switch, authorization indexes,
and authorization strings are determined based on the types of different
authorization item types.

 Number-type authorization items:
Operator ID
Authorization Range
Authorized Object
Function Item ID
Authorization Number
 Switch-type authorization items:
Operator ID
Authorization Range
Authorized Object
Function Item ID
Enabled or Not: Y (the user purchases the function, and the switch is enabled)
or N (the user does not purchase the function, and the switch must not be
enabled)
Whether the Authorization Period is Defined
Expiration Date
3 Technical Description
The license management system is composed of a license server and a license proxy.
The license proxy acts as a module of the EMS/OMM software, and is implemented and

integrated through the software. This proxy is used to communicate with the license
server over the DLCP-based link. The license server is composed of a DLCP module, a
license file management module, and a license authorization management module.
Figure 3-1 System Composition Diagram
EMS/OMM Server License Management Server
DLCP
Protocol DLCP Protocol
License File License Authorization

Management and Usage Querying
License Agent
License Log License Reports

EMS/OMM Server Management Management
A description of each module is as follows:
1. DLCP module
Dynamic License Control Protocol (DLCP) is a dedicated license management

protocol based on TCP/IP. The DH algorithm is used to exchange symmetric keys
during the connection setup process. The subsequently transmitted connection and
data information is encrypted through DES. This provides the safe, reliable, and
end-to-end transmission of license control command and information.
2. License file management
License file management supports the decryption, loading, historical rollback, and
temporary validation of files. License files are stored in an encrypted manner.
Therefore, before loading license files, decryption is required to convert license files
to the data objects that can be transmitted and processed. File loading is the
process of loading files to the license server and sending copies to the license proxy
when the EMS/OMM is initialized during the startup process, establishes a link to

the license server, and license files are updated. Historical rollback is the process of
rolling back newly loaded files to the files before the update. Temporary validation is
the process of cancelling all license control during a period of time in the specified
scenario.
3. License authorization inspection
When the configuration is changed or data is uploaded, a license authorization

inspection must be performed, regardless of whether the EMS/OMM is connected
to the license server. In online cases, the license server inspects all authorization
items and returns results. In offline cases, the authorization inspection is performed
based on the known license information in the license proxy.
3.1.1 File Management
License file management supports the importing, exporting, removal, and comparison of
license files.
1. The importing of license files is intended to use new license information. Before
importing them, the files must be decrypted, and the digital signature must be
checked to verify the validity of the license files.
2. The exporting of license files is the process of exporting the current license
information to excel files.
3. The comparison of license files is used to compare the consistency between

validated license files and the license files to be imported.
4. License files must be stored and backed up on the license management server in a
unified manner. Each EMS/OMM managed by the license management system
stores the license information allocated by the system. The consistency of license
information is ensured through the coordination between the license management
system and the EMS/OMM.
5. The compatibility between the function items in license files and the license center
version: Changes of the control item contents in license files do not cause the
license management system to upgrade software version files.

6. The compatibility between the function items in license files and the OMM version
files: Different OMM version files may support varied license items. The supported
licenses are determined by the OMM system. This means that, new function items
can be added to license files, but lack of some function items causes some OMM
authentication items that are not upgraded to fail (in this case, the deleted function
items are still used for authentication).
License file update: The license management server supports updating license files after
the files are imported.
1. If the original license file is a formal file, and if the license file to be updated is a trial
file, the file update process is to combine the original formal license file and new trial
license file together.
2. If both the original license file and the license file to be updated are formal files, the
file update process is to replace the original formal file with the file to be updated.
3. If the original license file is composed of a formal file and a trial file, and if the
license file to be updated is a formal file, the file update process is to disable the
previous formal file and trial file and use the new formal file instead.
License file rollback: The replaced license file can be automatically or manually rolled
back, and only one rollback is supported. If replacing a license file fails, the license file
information before the replacement is still used. If the replacement is successful, the
replaced license file can be kept for a period of time (14 days). During the time period,
users can roll back the file. After the period is exceeded, the rollback operation is not
supported.
3.1.2 Information Queries
The license server supports the content query after all formal and trial license files are
combined.
1. The total authorization number and total use can be queried after formal and trial
licenses are combined

2. The combined authorization number and the use of each NE can be queried by
group.
3. The use of a single NE can be queried.
3.1.3 Limit Exceeding Alarms
If the number of licenses exceeds the configured authorization threshold, an alarm is

raised, indicating that the maximum license number is exceeded.
1. Limit exceeding related to a number-type function item: When the total authorization
number for all NEs in the group management exceeds the maximum, an alarm is
raised, indicating that the total authorization number for user groups exceeds the
number that can be allocated.
2. Limit exceeding related to a switch-type function item: An alarm is raised, indicating

that the use of the item on the specific NE is illegal.
After the limit is exceeded, an alarm is raised in the periodical detection (performed
between 00:00 Am and 00:15 AM each day). The alarm threshold is compared during the
limit exceeding check. This threshold is configured in the configuration file on the license
server, and can also be modified through the license client interface.
3.1.4 Emergent Cancellation of License Restriction
To reduce the interference to configuration changes due to the license restriction (in the
complicated license adjusting) and cancel the license control function temporarily for
emergent capacity expansion in disaster cases or allowing users to try some functions,
all license requests are permitted during a period of time.
The emergent cancellation function, and the temporary emergent cancellation times and
duration (in days) can be configured in license files.
The emergent cancellation function can be enabled on the client of the license center.

3.1.5 File Expiry
The license server periodically checks whether temporary license files are valid between
00:00 AM to 00:15 AM each day.
1. During the validity, trial licenses can be used.
2. When trial licenses are about to expire (the time is configurable), the connected
OMM or EMS receives the corresponding alarm. When the expiration date is
reached, an alarm is sent each day.
3. After the expiration date is exceeded, all authorized items in trial licenses are
terminated. The system performs management based on the formal license and
other effective trial licenses.
3.1.6 Temporary Capacity Expansion
In the commercial temporary exhibition scenarios, the maximum numbers of some

license function items are allowed to be extended during a period of time. When the
capacity expansion time is expired, the original license control capacity is restored.
In this case, the policy is to use trial license files and the formal license file.
When the system grants authorizations based on the formal license file, the maximum
numbers of some function items must be extended temporarily. In this case, a trial file
needs to be re-requested, and the file validity is the time period when capacity expansion
is allowed. The function item authorization list in the file provides the quantities allowed to
be added.
3.1.7 Reports
In the license management interface, the summarization of license reports and the
summarization of licenses by logical group are supported, so that the license control
information on the site can be obtained at any time. The information about license
authorization, use, and remaining quantities can be output. Reports can be exported to
excel files.

3.1.8 Multi-Time-Zone DST
The license management server and the EMS/OMM system can be deployed in different
time zones. The system supports the normal license inspections for the EMSs/OMMs in
different time zones.
3.1.9 Protection under Link Disconnection
After establishing a link to the EMS/OMM for the first time, the license server saves the
authorization information about the current license file to the license agent of the
EMS/OMM. At the same time, the license proxy maintains the historical configuration of
the EMS/OMM. Therefore, when the EMS/OMM fails to connect to the license server, the
license agent makes an authorization decision based on the historical configuration and
authorization information about the current license file. In this way, when the link between
the license server and the EMS/OMM is broken, both the normal license check and the
normal operation of the EMS are guaranteed, ensuring high-reliable license services.
3.1.10 Pre-Authentication
Pre-authentication is applied to the following scenarios:
1. Export data before the license is modified for ease of reasonable allocation of the
resources to be authorized
2. Check the license immediately after the license is modified, and the modification
does not need to be synchronized. In this way, the license authorization information
is verified in advance. Modify the license if its authorization information fails to be
verified.
Before data is synchronized to the NE after a configuration change, pre-authentication

can be performed for parameters, and parameters are modified based on results. This
ensures that data synchronization is performed after the modification meets license
restriction requirements, reducing the impact caused by an authentication failure.
Pre-authentication is configured on the OMMB. Users can choose whether to perform
per-authentication manually and select the NEs to be pre-authenticated. The license data
is sent to the license center for check purposes. Regardless of whether the result is
successful, the license center does not deduct the pre-authentication number, and only

returns the result to the network management system. This improves the operation and
maintenance efficiency.
3.2 eNodeB-Level License Management
The eNodeB-level license management implements license authentication on the NE

side. Each NE is allocated with an independent license file, and the eNodeB manages
license control items. The license file is allocated by the OMC, and the NE performs
license control.
The dedicated license file of each eNodeB is bound to a hardware EID of the eNodeB,
which is any EID of an eNodeB power board. Based on this EID, the OMM automatically
matches the NE to implement file loading.
The eNodeB-level license provides the following file management:
1. File importing. A single file or a compressed package can be imported.
2. Loading a single file or batch files. Files are automatically matched based on the
selected NE.
3. Loading files automatically or manually. During the manual loading, the system
matches files based on the selected NE and displays available lists. In this case,
select Load. During the automatic loading, the system loads the latest file based on
the system version file.
Note: ANY files cannot be automatically loaded.
4. Error tolerance for files. The file check result is provided when a file is loaded. For
some errors that can be tolerated, you can specify whether to load the file. If the
user chooses to load the file, the system provides a two-month trial period for the
file with errors.
5. The network management client supports viewing offline file contents.

6. A specified file can be deleted on an OMC client based on the eNodeB EID that it is
bound to.
The eNodeB-level license supports the query of license contents and authorization
information about control items. A command can be sent from the network management
system to the front-end subsystem to query the following information:
1. Brief information about a file.
The sequence number, file deadline and loading date, and expiration date of a file
can be queried.
2. Detailed information about a file.
All contents in the license file can be queried.
3. License control items in use.
The following values can be queried on BS side: authorization values of current

license control items, the configured value of corresponding parameters, validated
values, and permitted values.
i. The authorization value of a license control item refers to the license value.
A parameter configuration value refers to the corresponding function value
configured on the OMC.
ii. A validated value refers to a license value and parameter configuration value
verified by authentication rules.
iii. An operating value is a dynamic value actually counted by the system. Only
some control items of number type have such value,, such as the number of
RRC_connected users, , number of E-RABs, and traffic.
4. Authentication status Query.

Default status, emergency status, temporary status, and normal status can be
queried.
Status information is described as follows:
i. Default status: An eNodeB that does not have an available license file is in
default status. In default status, all optional sales-related functions are
unavailable. Control items of number type are authorized by the default rule.
Based on the default rule, the number of RRC_connected users is 10, the
number of E-RABs is 15, the downlink traffic is 100 M, and the uplink traffic is
50 M.
For the details of the default rule, refer to the control item manual.
ii. Emergency status: When the emergency function is enabled, the eNode B is in
emergency status, and all control items are not restricted by the license file.
iii. Temporary status: After loaded with a temporary license file, the eNodeB is in
temporary status.
iv. Normal status: After loaded with an official license file, the eNodeB is in normal
status.
5. Emergency condition query
The remaining emergency times and the number of remaining emergency days can
be queried.
3.2.3 Limit Exceeding Alarms
When the actual number of use related to a number-type license control item is about to
exceed the authorization number, a notification or alarm is raised. The system compares
the operation quantities related to number-type license control items and the
authorization quantities each hour. If the ratio:
1. Reaches 80 to 90 percent, a notification is raised.
2. Reaches 90 to 100 percent, an alarm is raised.

3. Reaches 80 to 90 percent, no notification is raised if an alarm is already raised.
4. Reaches a value below 80 percent, an alarm recovery message is raised if an alarm

is already raised.
Emergent cancellation of license restriction is mostly used in disaster scenarios (such as

earthquakes and tidal waves). In these scenarios, the following modes are supported:
1. The system has no capacity restriction, and the maximum capability of the system is
used (for example, the maximum number of users that the RRC can connect to,
and maximum flow).
2. The system has no restriction on functions, and users can use all available
functions.
3. In emergency commands, each roadmap version is allowed to be enabled for three

times, seven days for each time.
The emergent cancellation of license restriction can be triggered by a dynamic

command.

Figure 3-2 Emergency Command
Authentication rules in emergency status are used based on system capability.
OMC configures emergency status by dynamic command, and the command is

correlated with user rights, and only the user with the highest rights can perform
operation.
3.2.5 File Expiry
If the loaded license file is a temporary file, the BS checks whether the file is expired at 2
AM each day.
1. The expiry time of the temporary file depends on the file type and the time when the
file becomes unavailable.
For the file type, refer to the Section 2.2.2.1.. The time provided by the file type is a
relative time, which starts from the time when the file is loaded to the eNodeB.
The time when the file becomes unavailable is an absolute time.
If the time provided by the file type is earlier, the time is used as the expiry
time of the temporary file. If the time when the file becomes unavailable is earlier,

the time is used.
2. When the reminding time (30 days ahead of the expiry date) is reached, the BS reports
a notification every day.
v. If the system has an available official file, a notification is reported, indicating

that the temporary file is to be expired. This notification is reported every day.
vi. If the system does not have an available official file, an alarm is reported,
indicating that the temporary file is to be expired. This alarm is only reported
once before the alarm is cleared.
3. When the temporary file is expired:
i. If the system has an available official file, authorizations are granted based on
the official file and the function permissions that are enabled in the capacity
expansion are reclaimed.
ii. If the system does not have an available official file, an alarm (indicating that
no license file exists) is reported, and an alarm (indicating that the temporary
file is going to be expired) is cleared. .
By default, authorizations are granted based on the default license file, and the
function permissions that are enabled in the capacity expansion are reclaimed
3.2.6 Status Management
To manage the license function change, the system divides the license statuses into four
types: default status, normal status, temporary status, and emergency status.
 Default status
When there is no available license file, set the license to “default status”. Control
items are authorized by the default rule, and the system provides minimum support
capability.
The transformation rule in default status is as follows:

i. When an official license file is loaded, the license is transformed to normal

status.
ii. When a temporary license file is loaded, the license is transformed to

temporary status.
iii. When the emergency function is enabled, the license is transformed to

emergency status.
 Normal status
When an official license file is loaded, the license is transformed to normal status.
The transformation rule in normal status is as follows:
i. When a temporary license file is loaded, the license is transformed to

temporary status.
ii. When the emergency function is enabled, the license is transformed to

emergency status.
 Temporary status
When a temporary license file is loaded, the license is transformed to temporary

status.
The transformation rule in temporary status is as follows:
i. When an official license file is loaded, the license is transformed to normal

status.
ii. When the emergency function is enabled, the license is transformed to

emergency status.
iii. When the temporary file is expired, and an available official file exists in the
system, the license is transformed to normal status.
iv. When the temporary file is expired, and no available official file exists in the
system, the license is transformed to default status.

 Emergency status
When the emergency function is enabled, the license is transformed to emergency

status. In this status, all function items are available, and the system provides the
maximum capability.
The transformation rule in emergency status is as follows:
i. When the emergency function is disabled, and an available temporary file

exists in the system, the license is transformed to temporary status.
ii. When the emergency function is disabled, and an available official file, rather
than a temporary file, exists in the system, the license is transformed to normal
status.
iii. When the emergency function is disabled, and no available license file exists,
the license is transformed to default status.
3.2.7 Temporary Capacity Expansion
If temporary short-term capacity expansion is needed (for example, in the commercial

temporary exhibition scenario and tourist festival) in a network, the operator can
purchase a trial license for capacity expansion. When the capacity expansion time is
reached, the original license control capacity is restored.
When the system operates based on the authorization information about the formal
license file, some new functions need to be temporarily tried. In this case, you can
request a trial license file, and the file validity is the time period when the new functions
are allowed to be tried.
During temporary expansion, there are two files (official and temporary files) on the
eNodeB. After the temporary file is expired, the eNodeB uses the official file to trigger the
authentication function.
3.2.8 Reports
The license management interface supports exporting license reports, and outputting the
information about license authorization, used license quantities, and the license files.

4 Key Parameters and Configuration
4.1.1.1 Import License File
In the License client,click ,Load license file to the license terminal.
Figure 4-1 Import License file
Click ,Push license file to license control center.

Figure 4-2 Push license file to license control center
4.1.1.2 Formal License File
The formal file has no invalidation date.After imported,it can be used for ever.

Figure 4-3 Formal License File
4.1.1.3 Trial License File
The Trial License File must be used with the Formal License file to extend the License
Center‟s capacity temporarily.The Trial License File‟s „History contract number‟ is the
Formal License File‟s „Current contract number‟.

Figure 4-4 Trial License File
The Authorized Value contains the Formal License File‟s and the Trial License File‟s.
Figure 4-5 Authorized Value

In the „Quantity License Usage Status‟,We can query the License File‟s Authorized Value，
Total Consumption。The use of each Subnet can bequeried.
Figure 4-6 Information Queries
4.1.3 License file rollback
The replaced license file can be manually rolled back, and only one rollback is
supported.Click ,Cancel the last uploaded license file and rool back to the previous
file.When replacing a license file successful, users can roll back the file during 14 days.

Figure 4-7 License file rollback
4.1.4 Reports
In the license management interface, the summarization of license reports can be
exported to excel files. Click ,Export current license information to Excel file.

Figure 4-8 Export Report
4.1.5 Pre-Authentication
Before data is synchronized to the NE after a configuration change, pre-authentication

can be performed for parameters, and parameters are modified based on results. This
ensures that data synchronization is performed after the modification meets license
restriction requirements, reducing the impact caused by an authentication failure.
In the NE Management of EMS client, Click Configuration Management->Special

Function of Standard->SubNetwork Level License Pre-authentication.

Figure 4-9 Entrance of SubNetwork Level License Pre-authentication
In the SubNetwork Level License Pre-authentication window. Select NE ， click

Authentication.

Figure 4-10 Authentication
The emergent cancellation function can cancel the license control function temporarily for
emergent capacity expansion in disaster cases or allowing users to try some functions,
all license requests are permitted during a period of time.
In the follow figure,The license file permits for temporary opening.Total duration of
temporary opening is 7 darys.Total times of temporary opening is 3.

Figure 4-11 Temporary Opening
Click to open or close temporary opening.
Figure 4-12 Set Temporary Openning

4.2 eNodeB- Level License Management
In NE Management,Select NE Agent,right key,click LTE eNodeB Level License

Management.
Figure 4-13 Entrance of LTE eNodeB Level License Management
4.2.1.1 Import License File
In the Load License File page,click -> Select license file -> click Open.The License
file can be imported.

Figure 4-14 Import License File
4.2.1.2 Load License File
In the Load License File page ,click .pop Load License File.First Select File,if the
License File binded with the PMEID,please choose Load Private File;if the License File is
a ANY File,please choose Load Universal File.Second Select NE.Third click
Match,choose the result,click Load.

Figure 4-15 Load License File
4.2.2.1 Query License File Brief Information
This function can query brief information about a file such as the sequence number, the
expiration date of a file.
In the Query License File Brief Information page,click -> select NE -> click Query.

Figure 4-16 Query License File Brief Information
4.2.2.2 Query License File Detailed Information
All contents in the license file can be queried.In the Query License File Detailed
Information page,click -> select NE->choose Query Master File->click Query.

Figure 4-17 Query License File Detailed Information
Select query result-> click right key -> click View Detail Information,pop the Detail
Information window.

Figure 4-18 View Detail Information
4.2.2.3 Query License System Status
The remaining emergency times or the number of remaining emergency days and the
System State can be queried by Query License System Status.
In the Query License System Status page,click -> select NE -> click Query.

Figure 4-19 Query License System Status
4.2.2.4 Query License Function Item Usage
This function can query The authorization values of license control items on the BS side,
parameter values, validated values, and permitted values.
In the Query License Function Item Usage page,click -> Select NE -> click Query.

Figure 4-20 Query License Function Item Usage
Select the query result -> click right key -> choose View Detail Information,pop Detail
Information window.

After Query Query License Function Item Usage ,click ,export the query result.
Figure 4-22 export the query result
4.2.2.5 Query License Authentication Result
When the configured vaule is different as the corresponding effective vaule permitted by
the license,there will be a alarm named Configuration data unmatched with the License
to remind users.
Figure 4-23 Configuration data unmatched with the License
Users can use Query License Authentication Result to query the inconsstency efficient
data.
In the Query License Authentication Result page, click -> Select NE -> click Query.

Figure 4-24 Query License Authentication Result
Select the query result->click right key->choose View Detail Information,pop Detail
Information window.

During the period of Emergent cancellation of license restriction, The system has no
capacity restriction, and the maximum capability of the system is used. The system has
no restriction on functions, and users can use all available functions.
In emergency commands, each roading version is allowed to be enabled for three times,
seven days for each time.
Users can open or close License Emergency Switch in the Dynamic Management.The
operation of open/close License Emergency Switch is as follow:
Select NE->Double click Set LicenseEmergency->click ->set Open/Close->click OK
Figure 4-26 Set LicenseEmergency
5 Alarm
Table 5-1 Related Alarms
Alarm No. Alarm Name Alarm Level Alarm Types

Alarm No. Alarm Name Alarm Level Alarm Types
1034 License consumption exceeds Major OMC alarm

the alarm threshold
1012 License is expired Major OMC alarm
1013 License is about to expire Major OMC alarm
1032 Link breakage between the Major OMC alarm

network management system
and the
license center
5.2 eNodeB- Level License Management
5.2.1 Plat Alarm
Table 5-2 Related License Alarms of Plat
Alarm No. Alarm Name Alarm Level

198097670 The system has no the Major
available License file
198098002 The License is entering to Notification

trying urgency state
198098003 The license file will soon fall Notification

due
198097673 The license file will soon fall Warning

due
198097651 Configuration data Warning

unmatched with the license
198098005 System capacity overload Notification
198097672 System capacity overload Warning
5.2.2 LTE FDD Alarm
Table 5-3 Related License Alarms of LTE FDD

198094459(FDD) The system capacity will Warning

exceed the License limit
198094460（FDD） The system capacity will Notification

exceed the License limit
6 Function Tests
6.1 Network-Level Function Tests
6.1.1 Importing/Loading/Update Function Tests for a License File
6.1.1.1 Test Environment
Figure 6-1 Function Test Environment for Making a License File
Table 6-1 Tested Devices
ID Device Name Note
1 eNodeB system -
2 Tested UE -
3 EPC -
4 OMC Includes the OMMB and

EMS.
5 License Center Includes the server and

client.

6.1.1.2 Test Method
Table 6-2 Importing/Loading/Update Function Tests for a License File
Task Importing/loading/update function tests for the license file.
Purpose Verify the flows that a license file is loaded, imported, and updated.
Prerequisite The license management center software is operating properly.
Step Result
Log in to a client of the license

1 You are logged in to the license client.
management center.
Open the window for importing the The window for importing the license file
2
license file. is displayed.
Select the license file to be The license file to be imported can be

3
imported. selected.
The license file is successfully imported.
Note：
4 Click OK to import the file.
The license file can be updated in the same
way.
Click the icon to upload the The license file is successfully uploaded to
5
file to the license management the license management center.
center.
Expected The license file is successfully imported and uploaded to the license
Result management center.
The license file is successfully imported and uploaded to the license

Pass Criteria
management center.
Test Result Pass
6.1.1.3 Querying Test Results
For the test steps and results, refer to Section 4.1.1 File Management.

6.1.2 Exporting Function Test for a License File
Refer to Section 6.1.1.1 Test Environment.
6.1.2.2 Test Method
Table 6-3 Exporting Function Test for a License File
Task Exporting function test for a license file
Purpose Verify the exporting function of a license file.
Step Result
1 Obtain a license file. The license file is obtained successfully.
Log in to a client of the license You are logged in to the license client.
2
management center.
Open the page for importing the The page for importing the license file is
3
license file. displayed.
Select the license file to be imported

4 The license file to be imported is selected.
on the client.
5 Click OK to import the file. The license file is successfully imported.
Click the Export icon to export the A dialog box for exporting the license file is
license file. displayed. Select the storage path, modify
6 the name of the exported file (in .xls
format), and finally click the Save button
to save the license file.
Click the Export icon. A dialog box for exporting the license file can be
Expected displayed. After selecting the storage path, and modifying the name of
Result the exported file (in .xls format), and clicking the Save button, the
license file can be successfully saved.
Pass Criteria The license file can be normally exported.
Test Result Pass

For the test steps and results, refer to Section 4.1.4 Reports.
6.1.3 Rollback Function Test for the License File
For the test environment, refer to Section 6.1.1.1 Test Environment..
6.1.3.2 Test Method
Table 6-4 Rollback Function Test for the License File
Task Rollback function test for the license file
Purpose Verify the rollback function test of the license file
Step Result
1 Obtain the license file. The license file is obtained successfully.
Load the license file on the client of

2 The license file can be loaded successfully.
the license management center.
The license file can be uploaded

Upload the license file to the server
3 successfully, and the rollback icon is grey
where no license file exists.
(unavailable).
After multiple license files are The license file is rolled back to the
4
imported, click the rollback icon. previous license file.
After the license file is rolled back,

5 The rollback icon is grey (unavailable).
click the rollback icon.
Modify the configuration, and check The license file control items are available
6
the current license file. after the rollback.
Expected
The rollback function of the license file is available.
Result
Pass Criteria The rollback function of the license file is normal.

Test Result Pass
For the test steps and result, refer to Section 4.1.3 License file rollback.
6.1.4 Authorization and Usage Tests for the License File
For the test environment, refer to Section 6.1.1.1 Test Environment.
6.1.4.2 Test Method
Table 6-5 Authorization and Usage Tests for the License File
Task Authorization and usage tests for the license file
Purpose Verify the authorization and usage information of the license file.
Step Result
No tasks are controlled, and all operations

Verify that the network is operating
1 are regarded as legal operations because
without a license file.
there is no license file.
2 Make a license file. The license file is made successfully.
The license file is successfully imported.

The entire network is controlled by this
Import the license on a license
3 official license file, and the license cannot
client.
be rolled back to the state when no license
exists.
Turn on the license switch on the

OMM, and then a message is sent to
All entries applied by the license file are
4 the license center, requesting the
permitted.
license center to determine whether
the applied entries are permitted.

Change the configurations to values

within the license restriction, for The configuration parameters of each NE
5
example, the number of users and can be successfully saved.
bandwidth.
Change the configurations to values A prompt is displayed, indicates that

beyond the license restriction, for related parameters of the license file
6
example, the number of users and exceed the license restriction, and cannot
bandwidth. be saved.
If the license parameters do not exceed the restriction, modified

Expected parameters can be saved normally. If the license parameters exceed
Result the restriction, modified parameters cannot be saved normal, and a
prompt is displayed.
Pass Criteria The authorization and usage status of the license file is normal.
Test Result Pass
If a license file is not authorized, related functions may fail. This procedure uses the AISG
RET function as an example.
1. If the AISG operation fails because the AISG License function is unavailable, a dialog
box is displayed, see the following figure:

Figure 6-2 AISG Function Fails
2. If the license function is available, a normal function window is displayed, see the
following figure:
Figure 6-3 AISG Function Succeeds

6.2 eNodeB-Level Function Tests
6.2.1 File Management Function Test
6.2.1.2 Test Method
Table 6-6 Test Criteria for the File Management Function
Task File management function test
Purpose Verify the file management function.
1. The network environment is normal, and cells can be established

Prerequisite successfully.
2. The OMMB or EMS is operating properly.
Step Result
On the OMM, select View -> LTE

1 eNodeB Level License -
Management.
Select the license to be loaded,

2 The license file is successfully loaded.
and load the license file.
Load the license file to the front The license file is successfully loaded to the
3
end. front end.
Expected
The file management function is normal.
Result
Pass Criteria
Test Result Pass

1. On the OMM, select View -> LTE eNodeB Level License Management, see the
following figure:
Figure 6-4 Selecting LTE eNodeB Level License Management
2. On the LTE eNodeB-level license management window, select the license file to be
loaded, and click the icon marked in the following figure to import the file.

Figure 6-5 Importing a License File
3. Select the license file of the corresponding version, and click Open, see the
following figure:
Figure 6-6 Selecting the License File of the Corresponding Version
4. A message box is displayed, indicating that the license file is successfully loaded,
see the following figure:

Figure 6-7 License File Is Successfully Loaded
5. On the LTE eNodeB-level license management window, select the license file to be
loaded, and click the icon marked in the following figure to load the file to a specified
eNodeB.

Figure 6-8 Loading the License File to the eNodeB
6.2.2 Information Query Function Test
6.2.2.2 Test Method
For the test criteria for the information query function, refer to the following table:
Table 6-7 Test Criteria for the Information Query Function
Task Information query function test
Purpose Verify the information query function.
1. The network environment is normal, and cells can be established

Prerequisite successfully.
2. The OMMB or EMS is operating properly.

Step Result
On the OMM, select View -> LTE

1 eNodeB Level License
Management.
Query the brief information of The brief information of the license file is
2
the license file. successfully queried.
Query the detailed information The detailed information of the license file is
3
of the license file. successfully queried.
Query the usage information of The usage information of function items of the
4
function items of the license file. license file is successfully queried.
5 Query the license system status. The system status is successfully queried.
Expected
The information query function is normal.
Result
Pass Criteria
Test Result Pass
1. On the OMM, select View -> LTE eNode Level License Management.-> Query
LCS Brief Information, and select the base to be queried, see the following figure:

Figure 6-9 Selecting the Base to Be Queried
2. The brief information is successfully queried, see the following figure:
Figure 6-10 Brief Information Is Successfully Queried
3. Click the icon marked in the following figure to export the query result, see the
following figure:

Figure 6-11 Exporting the Query Result
4. On the OMM, select View -> LTE eNodeB Level License Management-> Query LCS
Detailed Information, and select the base to be queried, see the following figure:
Figure 6-12 Selecting the Base to Be Queried
5. The detailed information is successfully queried, see the following figure:

Figure 6-13 Detailed Information Is Successfully Queried
following figure:
7. On the OMM, select View -> LTE eNodeB Level License Management-> Query LCS
Function Item Usage, and select the base to be queried, see the following figure:

Figure 6-15 Querying Function Items
8. The function item information is successfully queried, see the following figure:
Figure 6-16 Function Item Information Is Successfully Queried
following figure:

10. On the OMM, select View -> LTE eNodeB Level License Management-> Query System
Status, and select the base to be queried, see the following figure:
Figure 6-18 Querying the System Status
11. The system status is successfully queried, see the following figure:

Figure 6-19 System Status Is Successfully Queried
following figure:
7 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.

ZTE LR14 LTE FDD License Feature Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZTE LR14 LTE FDD License Feature Guide

Caricato da

Copyright:

Formati disponibili

ZTE LTE FDD License

ZTE LTE FDD License Feature Guide

© 2015 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

3 Technical Description ..................................................................................... 18

4 Key Parameters and Configuration ................................................................ 33

2 ZTE Confidential & Proprietary

4.1.2 Information Queries ........................................................................................... 37

6 Function Tests .................................................................................................. 55

ZTE Confidential & Proprietary 3

4 ZTE Confidential & Proprietary

Figure 4-26 Set LicenseEmergency ...................................................................................53

Table 5-1 Related Alarms ..................................................................................................53

ZTE Confidential & Proprietary 5

Table 6-2 Importing/Loading/Update Function Tests for a License File ..............................56

6 ZTE Confidential & Proprietary

1.2 Target Group

This document is intended for:

 Personnel who need to understand FDD License function

 Personnel who work with ZTE products

1.3 Feature Attribute

 For FDD single-mode eNodeB V3.20.50.20 series:

OMMB version: V12.13.58

EMS version: V12.13.58

 For GUL multi-mode eNodeB V4.13.15series:

OMMB version: V12.13.52

EMS version: V12.13.51

ZTE Confidential & Proprietary 7

FDD single-mode V3.20.50.20 corresponds to GUL multi-mode V4.13.15, and LTE

8 ZTE Confidential & Proprietary

2.1 Network-Level License Management

2.1.1 Management Mode

Figure 2-1 Location of the License Management System in the Network

2.1.2 File Description

ZTE Confidential & Proprietary 9

A license file is composed of the following items:

1. Standard license information:

 contract number: contract number, 23 digits.

10 ZTE Confidential & Proprietary

 official rise rate

 temporary open days

 temporary open times

 MCC and MNC

ZTE Confidential & Proprietary 11

included in all quantitative authentication items involved in function items. Switch

 NE ID: The MeID is defined as a sub-network number, and is in the format of

 Associated Group: the group that the sub-network belongs to.

 Feature Type: number-type or switch-type

6. General authorization: All authorization items in function items must be confirmed

12 ZTE Confidential & Proprietary

 Number-type authorization items:

 Switch-type authorization items:

Whether the Authorization Period is Defined

2.2 eNodeB-Level License Management

2.2.1 Control Item Types

License control items are divided into the following types:

1. License of function switch type

ZTE Confidential & Proprietary 13

2. License of number type

2.2.2 License Files

2.2.2.1 File Types

1. Formal license files

2. Trial license files

14 ZTE Confidential & Proprietary