Professional Documents
Culture Documents
Page 2
Contents
1.
2.
License Status
3.
License Tool
4.
License Scenarios
Page 3
Page 4
LKF
Page 5
LKF Structure
Common
Segment
Feature
Segment
Page 6
Page 7
ESN
Page 8
Page 9
LKF Types
Type
Commercial LKF
Description
An LKF created based on a business contract. In principles, a license certificate together with the
electronic LKF must be issued to the customer.
In a commercial LKF, the authorization type is COMM, all feature segments have the same expiration
date (either permanent or a specific date), and the default grace period is 60 days.
A temporary LKF used for verifying software functions during project implementation.
All feature segments in a demo LKF contain the same expiration date. Demo LKFs are further classified
into the following types:
Demo LKF
Demo LKFs valid for three months with ESN not set to ANY. An eNodeB can use this type of LFK up
to three times.
Demo LKFs valid for six months with ESN set to ANY. This type of LKF can be used only once for an
R-level release (for example, V100R002) of an eNodeB.
Demo LKFs valid for seven days with ESN not set to ANY. There are no restrictions as to the number
of times that this type of LKF can be used within the seven-day time period.
An LKF used in scenarios where a network needs to be frequently adjusted and license trial is required
before purchase.
Permanent &
temporary LKF
A permanent & temporary LKF contains temporary feature segments in addition to the contents of a
commercial LKF. In a permanent & temporary LKF, the authorization type is COMM; permanent feature
segments do not have expiration dates but temporary feature segments have.
The control items in temporary feature segments can be only resource control items.
Page 10
License Status
2.1 License Status of eNodeBs
2.2 States of Licenses
Page 11
At the engineering construction stage, a demo license file is installed on the eNodeB.
The license status of the eNodeB is "demo".
At the engineering acceptance stage, the customer has installed the commercial LKF
on the eNodeB. The license status of the eNodeB is "normal".
When the eNodeB is working, the eNodeB license enters the protected status in any
of the following situations:
The check of the ESN or product version contained in the LKE fails,
Page 12
The eNodeB has been in the protected license state for 60 days.
In the default license state, the eNodeB uses the default values of the
license items. The default values of Active User, Throughput Capacity,
Carrier Bandwidth, and RF Output Power are 6, 5 Mbps, 5 MHz, and 0 W,
respectively. All optional functions are disabled.
Page 13
An operating eNodeB enters the protected license state when any of the
following conditions is met:
In the protected license state, the eNodeB can operate at the licensed
values for up to 60 days without affecting services. After 60 days elapse,
the eNodeB enters the default license state.
Page 14
When a demo LKF expires, the eNodeB status changes from the
demo license state to the protected license state. An eNodeB can
stay in the protected license state for up to 60 days. After 60 days
elapse, the eNodeB enters the default license state.
Page 15
Page 16
switched to the emergency state. An eNodeB in the normal or demo license state
enters the emergency license state when the emergency license is activated. In the
emergency license state, the eNodeB operates with the maximum allowable traffic
rate and the number of managed UEs can reach the maximum value, rather than
confined to the licensed limits. In this way, the eNodeB avoid performance
deterioration.
An eNodeB of an R-level release can enter the emergency license state up to three
times and remain in that state for up to seven days each time.
When an eNodeB enters the emergency license state, it reports a License Emergency
Status Activated event.
When the eNodeB exits the emergency license state, it reports a License Emergency
Status Ceased event.
Page 17
License Status
2.1 License Status of eNodeBs
2.2 States of Licenses
Page 18
States of Licenses
Default state
Protected state
Emergency state
Normal state
Page 19
License Tool
3.1 Functions of the License Tool
3.2 Position of the License Tool in the System
Page 20
The Adjust License function imports existing licenses from the NEs and
redistributes them among the NEs. After redistributing the licenses, the
Adjust License function exports license approval documents.
The Compare License Files function compares two license files. The
result shows the differences of the two license files. A user can use this
function to view the content of a license file.
Page 21
License Tool
3.1 Functions of the License Tool
3.2 Position of the License Tool in the System
Page 22
The input to the Batch Map NE to Order function is provided by the FNO and M2000. The
output goes to the FNO.
The input to the Adjust License function is provided by the M2000 or the license file of the
eNodeB. The output is Approval Files.
Page 23
License Scenarios
5.1 Obtaining a Demo License
5.2 Obtaining Commercial License
5.3 Adjusting License Capacity
5.4 Changing the ESN
5.5 Revoking a License File
5.6 Version Upgrade and Capacity Expansion
Page 24
Page 25
Step 1: Log in to the FNO system at http://license.huawei.com using the user account and
password of the China domain.
Note: The GTS engineers can use the user account and password of the China domain to
log in to the FNO of the latest version. If they have no permission, they must access the
IT Account & Privilege Request database to apply for an FNO account.
Step 2: Click Download Commissioning License in the navigation tree. The Download
Commissioning License window is displayed.
Page 26
Step 5: Select the expiration term and click Submit. The license key file is displayed.
Page 27
License Scenarios
5.1 Obtaining a Demo License
5.2 Obtaining Commercial License
5.3 Adjusting License Capacity
5.4 Changing the ESN
5.5 Revoking a License File
5.6 Version Upgrade and Capacity Expansion
Page 28
Page 29
FNO
provides
order
information
to the
License Tool.
NE information
and ESN are
obtained from the
M2000 and
provided to the
License Tool.
NE information
License Tool matches site type
and generates matching
information and license
capacity information.
Order information
Automatic match
Filtered match
Forced match
FNO self-service
application
License file (zip)
Page 30
Page 31
License Scenarios
5.1 Obtaining a Demo License
5.2 Obtaining Commercial License
5.3 Adjusting License Capacity
5.4 Changing the ESN
5.5 Revoking a License File
5.6 Version Upgrade and Capacity Expansion
Page 32
Page 33
After a license file is activated before the PAC point, if the values of the license file are
inconsistent with the actual values, the license capacity needs to be adjusted before the PAC
point.
Rule 2: License adjustment is allowed among eNodeBs of the same product and same VR
versions.
Rule 3: Only permanent license files are adjusted. Demo licenses, permanent temporary
license files, and temporary license files are not adjusted.
Rule 5: The total capacity must be unchanged before and after the adjustment.
Page 34
M2000
Obtain the revocation
code of the license file to
be adjusted.
Note:
Online adjustment
is applicable to a
small number of
eNodeBs.
Offline adjustment
is applicable to a
large number of
eNodeBs.
FNO
Offline adjustment: Import the
adjusted license information to
generate a new license file.
Online adjustment: Enter the
revocation code to adjust the
license capacity and generate a
new license file.
Page 35
If engineers of the GTS department want to adjust the network after the PAC point,
they must submit an application. The application must be approved.
Rule 2: License adjustment is allowed among eNodeBs of the same product and
same VR versions.
Rule 3: Only permanent license files are adjusted. Demo licenses, permanent
temporary license files, and temporary license files are not adjusted.
Rule 5: The total capacity must be unchanged before and after the adjustment.
Page 36
M2000
Export the license file
information and revocation
code.
License Tool
Enter the license file information and revocation code to the License Tool.
Download an application
form at
http://w3.huawei.com/domin
oapp/isc/license/platform.nsf/
fmDatabase?ReadForm and
submit the application for
approval.
Page 37
License Scenarios
5.1 Obtaining a Demo License
5.2 Obtaining Commercial License
5.3 Adjusting License Capacity
5.4 Changing the ESN
5.5 Revoking a License File
5.6 Version Upgrade and Capacity Expansion
Page 38
Before changing the ESN, revoke the license file, obtain the ESN
information and revocation code, and generate a new license file.
Page 39
M2000
Export revocation code and ESN in batches
FNO
Enter the revocation code
and ESN to generate a new
license file.
Page 40
License Scenarios
5.1 Obtaining a Demo License
5.2 Obtaining Commercial License
5.3 Adjusting License Capacity
5.4 Changing the ESN
5.5 Revoking a License File
5.6 Version Upgrade and Capacity Expansion
Page 41
If due to ESN change or adjustment of the license capacity, a new license file is
needed to replace the existing commercial license file, the existing commercial
license file must be revoked and a revocation code be obtained before an
application for a new license file is submitted.
To revoke a license file is to recycle the authorized license key, ensuring that the
license key is no longer used by the eNodeB.
Run the RVK LICENSE command to revoke a license file. After the license file is
revoked, the eNodeB returns a license revocation code.
After being revoked, the license enters the protected state; the services on the
eNodeB are unaffected for 60 days.
After the license file is revoked, the eNodeB reports the License on Trial alarm.
Page 42
Objective
Before upgrading an R version, the existing license file must be revoked. If the upgrade fails, the new license file
needs to roll back to the existing license file. Currently, the system does not support batch rollback of license
files.
Current implementation
Enter revocation
code.
Current method
To roll back to the original license file, enter the revocation code of the original license file. No batch operation is
available.
Page 43
License Scenarios
5.1 Obtaining a Demo License
5.2 Obtaining Commercial License
5.3 Adjusting License Capacity
5.4 Changing the ESN
5.5 Revoking a License File
5.6 Version Upgrade and Capacity Expansion
Page 44
Page 45
NE information
Automatic match
Matching information (.xml)
Filtered match
Forced match
Page 46
Optional
References
Page 47
Full Name
ESN
LSN
FNO
PAC
Page 48
Thank you
www.huawei.com