Professional Documents
Culture Documents
SJ-20151105120414-003-ZXSDR UniRAN FDD-LTE (V3.30.20.00) License Management Description
SJ-20151105120414-003-ZXSDR UniRAN FDD-LTE (V3.30.20.00) License Management Description
SJ-20151105120414-003-ZXSDR UniRAN FDD-LTE (V3.30.20.00) License Management Description
Version: V3.30.20.00
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: 800@zte.com.cn
LEGAL INFORMATION
Copyright © 2016 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
R1.1 2016-01-08 l Added the description of license file deletion in Section 3.3.1
File Management.
l Added the description of querying the special file usage,
license authentication results, and license redundancy
information in Section 3.3.2 Information Query.
l Modified the period ahead of the expiration date to one
month for sending a notification message in Section 3.3.5
File Expiration.
l Modified the descriptive contents in the manual.
Glossary .......................................................................................................... I
II
Intended Audience
l Network planning engineers
l Software debugging engineers
l Data configuration engineers
l Network monitoring engineers
l Maintenance engineers
l Network optimization engineers
Chapter 2, LTE EMS-Level Describes the EMS-level license management procedure, and
License Functions descriptions of license files and functions.
Conventions
This manual uses the following conventions.
II
1-1
1-2
2-1
Note:
License client software and EMS/OMM client software can be deployed on the same PC or
on different PCs. License server software and EMS/OMM server software can be deployed
on the same PC or on different PCs.
File Contents
For the items contained in a license file, refer to Table 2-1.
Table 2-1 License File Content Description
Customer name -
2-2
SN -
Publishing date -
Use date -
Maker -
Maker department -
Product name -
Product version -
Product number -
Manager center -
Mac info -
Hard lock -
Hard lock ID -
Effect date -
Invalidation date -
Awake date -
Awake text -
Expire text -
Modify or adjust -
Temporary open -
2-3
2-4
Operation Description
License file export Exports the current license information to excel files.
License file comparison Compares the consistency between validated license files and the
license files to be imported.
License file storage and backup License files must be stored and backed up on the license
management server in a unified manner. Each EMS/OMM stores
license information allocated by the license management system.
The consistency of license information is ensured through the
coordination between the license management system and the
EMS/OMM.
Compatibility of license files The compatibility between the function items in license files and the
software versions of the license center: Changes of the control
items in license files do not cause the license management system
to upgrade software versions.
The compatibility between the function items in license files and
the OMM software versions: Different OMM versions may support
various license items. The supported license items are determined
by the OMM system. New function items can be added to license
files, but removal of some function items from license files may
cause 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 server supports updating license files after the files
are imported.
l If the old license file is a formal file and the license file to be
updated is a trial file, the file update process is to combine the
old formal license file with the new trial license file.
l If both the old license file and the license file to be updated are
formal files, the file update process is to replace the old formal
file with the file to be updated.
l If the old license files include a formal file and trial files and
the license file to be updated is a formal file, the file update
process is to replace the old formal file and trial files with the
formal file to be updated.
2-5
Operation Description
License file rollback The replaced license file can be automatically or manually rolled
back, and only one rollback is supported. If an old license file fails
to be replaced, the old license file before file replacement is still
used. If the replacement is successful, the replaced license file
can be kept for a period of time (14 days). During that time period,
users can roll back the file manually. When the period expires, the
rollback operation is no longer supported.
When total license authorization amount for all NEs under group management
exceeds the maximum value, an alarm is raised, indicating that the total license
authorization amount for user groups exceeds the amount that can be allocated.
l Overrun relating to a switch-type function item
An alarm is raised, indicating that the use of the function item on a specific NE is illegal.
If the limit is exceeded, the actual value is compared with the alarm threshold during
an overrun check and an alarm is raised during periodical detection that is performed
between 00:00 a.m. and 00:15 a.m. each day. This threshold is configured in the
configuration file on the license server, and can also be modified through the license
client.
2-6
Scenario Processing
Commercial temporary The formal license file is used together with trial license files. The
exhibition maximum number of license function items is allowed to be extended
during a certain period of time. When the duration for capacity expansion
expires, the original license capacity is restored.
When the system grants A trial file with an allowable time limit for capacity expansion needs to
authorization based on be re-requested. The function item authorization in the file provides the
the formal license file and number of function items to be added for capacity expansion.
needs to expand some
function items temporarily
2.3.7 Reports
l The license management system provides the license report summarization function.
Reports can be exported as Excel files.
l Licenses are summarized by logical group, so that license control information on site
can be obtained at any time.
l Information about license authorization, use, and remaining quantity can be outputted.
2-7
2.3.8 Multi-Time-Zone
The license management server and the EMS/OMM systems can be deployed separately
in different time zones, so that license inspections can be performed on the EMS/OMM
systems in different time zones.
Therefore, when the EMS/OMM fails to connect to the license server, the license agent
makes an authorization decision based on authorization information and historical
configuration data about the current license file. In this way, both regular license check
and proper operation of the EMS are guaranteed, ensuring high-reliable license services.
2.3.10 Pre-Authentication
Before data is synchronized to an NE after a configuration change, pre-authentication
can be performed on parameters and then parameters are modified based on the
pre-authentication result. In this way, data can be synchronized only after the modification
meets license restriction requirements, reducing the impact caused by an authentication
failure.
Pre-authentication is configured on the OMMB server. Users can determine whether
or not to manually perform per-authentication and manually select the NEs to be
pre-authenticated as necessary. License data is sent to the license center for data check.
Regardless of the check result, the license center returns the result to the EMS without
withholding the license to improve the operation and maintenance efficiency.
2-8
3-1
File Management
License file management provides the following functions:
l Generating license files. License files are generated and encrypted by the IT system.
l Loading license files. License files can be loaded from the EMS to an eNodeB
dynamically or statically.
à License files can be loaded in batches.
à License files can be loaded to an eNodeB individually.
l Checking license files. A validity check can be performed on the format of license
files, including version number, hardware sequence number, digital signature, and
information field for each item.
l Querying license files. The contents and authorization information about license files
can be viewed in real time.
l Invalidating license files. When the system is upgraded or new license files are used,
the license files in use must be invalidated.
l Reports: License contents can be exported from the OMM system to excel files.
File Contents
For the items contained in a license file, refer to Table 3-1.
Customer name -
3-2
Sn -
Publish date -
Use date -
Maker -
Maker department -
Product name -
Product version -
Product number -
Manager center -
MAC info -
Hard lock -
Hard lock ID -
Effect date -
Invalidation date -
Awake date -
Awake text -
Expire text -
Modify or adjust -
Temporary open -
3-3
Operation Description
3-4
Operation Description
Load a license file Loads a single file or files in batches. License files are automatically
matched based on the selected NEs.
License files can be loaded automatically or manually.
l During manual loading, the system automatically matches license files
based on the selected NEs and displays an available list for loading.
l During automatic loading, the system loads the latest license file
based on the system version.
Delete a license file The EMS system can delete license files on the EMS side by EID, rather
than the license files on the base station side.
Tolerate a license file Faults in license files can be tolerated. License files are checked during
error license file loading. For the file with some tolerable faults, users can
determine whether or not to load it. If users choose to load the file with
faults, the system grants a period of two months for the file.
License file view The EMS client supports content viewing of offline license files.
3-5
l Every day, the eNodeB reports a notification message one month ahead of the
expiration date.
l When a trial file expires, the system processes the privilege for functions. For privilege
processing after trial file expiration, refer to Table 3-3.
3-6
There is an available formal A notification message is reported, indicating that the trial file
license file is replaced by the formal file.
Authentication is performed based on formal license and the
function privilege that was granted for temporary capacity
expansion is revoked.
There is no available formal An alarm is reported, indicating that no license file is available.
license file Authentication is performed based on default license and the
function privilege that was temporarily granted is revoked.
3.3.7 Reports
The license management system exports license reports, containing information about
license authorization, the number of used licenses, and the number of remaining licenses.
3.3.8 Pre-Authentication
There are two types of eNodeB-level license pre-authentication:
l Pre-authentication of licenses to be imported
It is used to find inconsistencies between the new license file and the data of the
existing network or the data displayed in the modification area to determine whether
to apply for a new license file again or adjust configuration data.
l Pre-authentication of licenses running on eNodeBs
It is used to find inconsistencies between the data in the modification area and the
active license file to adjust parameters in advance if the configuration data is beyond
the range restricted by the license file. It can improve eNodeB commissioning,
operation, and maintenance efficiency.
3-7
3-8
NE
- Network Element
OMM
- Operation & Maintenance Module
OMMB
- Operation and Maintenance Module for BTS, NodeB and eNodeB
RRC
- Radio Resource Controller
ZTE
- Zhongxing Telecommunications Equipment
eNodeB
- Evolved NodeB