Lte Enodeb License Management: Security Level: Intramural

Security Level: intramural
LTE eNodeB License

Management
www.huawei.com
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

About This Course
 This course describes concepts about LTE eNodeB license
management and end-to-end operations.
 The intended readers of this course are Huawei customer
service engineers who want to understand Huawei LTE
eNodeB license management and operations.
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved. Page 2
Contents
1. License Key File
2. License Status
3. License Tool
4. License Scenarios
License Key File
1.1 LKF Structure
1.2 ESN
1.3 LKF Types
LKF
 An LKF is an authorization to use a software program and consists
of common segment, service segment, and feature segment.
 The common segment contains customer name, license serial
number (LSN), equipment serial number (ESN), product name,
product version, and authorization type (commercial or non-
commercial).
 The feature segment contains resources (such as 100 users),
functions (such as support of short message service), expiration
date of the resources and functions, and reservation period. The
reservation period is 60 days after expiration of the resources and
functions. During the reservation period, an expiration alert is sent
every day.
LKF Structure
Common
Segment
Feature
Segment
License Key File
1.1 LKF Structure
1.2 ESN
1.3 LKF Types
ESN
 An ESN is a unique character string that identifies the
equipment. It ensures that the LKF is assigned to the
correct equipment.
 The ESN of an eNodeB is the ESN of the backplane in the
BBU where the main control board is installed.
License Key File
1.1 LKF Structure
1.2 ESN
1.3 LKF Types
LKF Types
Type 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.
Commercial LKF 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 LKFs valid for three months with ESN not set to ANY. An eNodeB can use this type of LFK up
Demo LKF 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 & A permanent & temporary LKF contains temporary feature segments in addition to the contents of a
temporary LKF 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.
License Status
2.1 License Status of eNodeBs
2.2 States of Licenses
License Status of eNodeBs
An eNodeB may be in one of the following license states: default, demo, normal,
emergency, and protected. Users can query license information on an M2000 client or
run the DSP ENODEB command to query the license status of an eNodeB.
 At the new site construction stage, no license file is installed on the eNodeB. The
license status of the eNodeB is "default".
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".
At the engineering maintenance stage, in an emergent situation such as earthquake,
the license can be switched to the emergency state by running the SET
LICENSECTRL command.
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,
 The demo LKF expires.
 The commercial LKF is revoked.
License Status of eNodeBs – Default
License State
 An operating eNodeB enters the default license state if either of the
following conditions is true:
 No valid LKF is installed on the eNodeB.
 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.
 When an eNodeB enters the default license state, it reports a No License
Running in System alarm.
License Status of eNodeBs – Protected
License State
 An operating eNodeB enters the protected license state when any of the
following conditions is met:
 An ESN or Version check on its LKF fails.
 Its demo LKF expires.
 Its commercial LKF is revoked.
 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.
 When an eNodeB enters the protected license state, it reports a License
on Trial alarm.
License Status of eNodeBs – Demo
License State
 An operating eNodeB enters the demo license state when a demo
LKF is installed on eNodeB. In a typical demo LKF, resource items
are set to the maximum values and function items are all turned
on.
 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.
License Status of eNodeBs – Normal
License State
 An operating eNodeB enters the normal license state when
a commercial LKF is installed on the eNodeB. In the normal
license state, the eNodeB operates within the licensed
values defined in the LKF.
License Status of eNodeBs – Emergency
License State
 In special situations such as in a major holiday or an activity, the license can be
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.
License Status
2.1 License Status of eNodeBs
2.2 States of Licenses
States of Licenses
 Default state
 Protected state
 Emergency state
 Normal state
License Tool
3.1 Functions of the License Tool
3.2 Position of the License Tool in the System
Functions of the License Tool
 The Batch Map NE to Order function makes it easy to import NE
information to the order that matches the NE and export the matching
information. The FNO system uses this matching information to create
license files in batches for the eNodeBs.
 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.
License Tool
3.1 Functions of the License Tool
3.2 Position of the License Tool in the System
Position of the License Tool in the System
 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.
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
Obtaining a Demo License
 During a new site construction, due to uncertainties in network
planning, the commercial license file cannot be determined.
Therefore, a demo license file is installed. After the engineering
commissioning is completed, the demo license file is replaced by
a commercial license file.
 Huawei engineers can obtain a demo license from the FNO. In
this demo license file, the value of ESN is ANY and the validity
period is 6 months. This demo license can be installed on any
eNodeB to be deployed.
 Operation direction: FNO -> M2000
 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.
Step 3: Click Search. In the displayed box,

enter LTE and click Search to query the
demo licenses of all versions of a product.
Select the correct version.
Step 4: Select All from the Type drop-down list box..
 Step 5: Select the expiration term and click Submit. The license key file is
displayed.
 Step 6: click Save to save theIffile
you to theyes,
select local
the disk.
license key file has an
expiration term of 180 days and is not bound to
any ESN.
If you select no, the license key file has an

expiration term of 90 days or 7 days and is
bound to an ESN. Specify the ESN and
expiration term.
License Scenarios
Obtaining Commercial License
 The demo license installed during the new site construction
has an expiration date. After the network becomes stable, a
commercial license is generated and installed based on the
actual situation.
Operation direction:
M2000->FNO -> License Tool -> FNO -> M2000
FNO
NE information provides
and ESN are order
obtained from the information
M2000 and to the
provided to the License
License Tool. Tool.
NE information License Tool match Order information
License Tool matches site type

and generates matching  Automatic match
information and license  Filtered match
capacity information.  Forced match
Matching information (xml)
FNO generates license file

package according to the
matching information provided FNO self-service
by the License Tool. application
License file (zip)
Query license status
License Scenarios
Adjusting License Capacity
 After a commercial license file is installed, if the license capacity
needs to be adjusted among eNodeBs due to change of the
network planning, you can use the Adjust Capacity function of the
License Tool.
 The license file information, ESN information, and revocation code
are required. After the license capacity is adjusted, a new license
file is generated.
 If the project has not passed the Preliminary Acceptance
Certificate (PAC) point, online or offline self-service adjustment is
available. If the project has passed the PAC, an approval must be
obtained before the adjustment.
Adjusting License Capacity Before the
PAC Point
 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.
 The following rules must be met:
 Rule 1: License adjustment is allowed among eNodeBs of the same customer.
 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 4: Only resources are adjusted. Functions are not adjusted.
 Rule 5: The total capacity must be unchanged before and after the adjustment.
 Rule 6: License adjustment is allowed only before the PAC point.
 Rule 7: A revocation code is required by the license adjustment.
Adjusting License Capacity Before the PAC Point
(Self-Service)
Operation direction
Online adjustment: M2000 -> FNO-> M2000
Offline adjustment: M2000-> License Tool -> FNO ->M2000
M2000
Obtain the revocation
code of the license file to
be adjusted.
License Tool (offline adjustment) Note:

Online adjustment
Enter the license file information
and revocation code. is applicable to a
small number of
eNodeBs.
Offline adjustment
FNO is applicable to a
Offline adjustment: Import the large number of
adjusted license information to eNodeBs.
generate a new license file.
Online adjustment: Enter the
revocation code to adjust the
license capacity and generate a
new license file.
Adjusting License Capacity After the
PAC Point
 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.
 The following rules must be met:
 Rule 1: License adjustment is allowed among eNodeBs of the same customer.
 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 4: Only resources are adjusted. Functions are not adjusted.
 Rule 5: The total capacity must be unchanged before and after the adjustment.
 Rule 6: A revocation code is required by the license adjustment.
Adjusting License Capacity After the PAC Point
M2000-> License Tool -> Lotus Notes Workflow -> M2000
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.
License Scenarios
Changing the ESN
 In case of ESN change or license file transfer between eNodeBs,

the license file becomes unavailable. In this case, the ESN
contained in the license file needs to be changed.
 Before changing the ESN, revoke the license file, obtain the ESN
information and revocation code, and generate a new license file.
Changing the ESN
M2000 -> FNO-> M2000
M2000
Export revocation code and ESN in batches
FNO
Enter the revocation code
and ESN to generate a new
license file.
License Scenarios
Revoking the License
 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.
 A license revocation code is a character string generated by the RVK LICENSE
command. The FNO uses this revocation code to determine that the license file
uniquely mapped to this revocation code is revoked. The license revocation code is
an evidence of license key invalidation and is a prerequisite for applying new
license key.
 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.
Rolling Back a Revoked License File
 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.
License Scenarios
Version Upgrade and Capacity Expansion
 If the traffic volume increases or new services are launched, the
customer may want to upgrade the R version or expand the
capacity. In this case, the license file must be upgraded or
capacity-expanded.
 Before upgrading or capacity-expanding the license file, obtain the
license file and ESN information of the eNodeB and the revocation
code. The upgrade or capacity expansion of the license file must
be performed by Huawei engineers.
Upgrading an R-Level Version
NE information License Tool match Order information (FNO)
Automatic match
Matching information (.xml) Filtered match
Forced match
FNO self-service application
License file (.zip)
Optional
References
 LTE eNodeB License Operation Guide for GTS Engineers.doc
 Huawei License Control Specifications V1.0.doc
Acronyms and Abbreviations
Acronyms and Abbreviations Full Name
ESN electronic serial number
LSN license serial number
FNO FlexNet Operations System
PAC Preliminary Acceptance Certificate
Thank you
www.huawei.com

Lte Enodeb License Management: Security Level: Intramural

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lte Enodeb License Management: Security Level: Intramural

Uploaded by

Copyright:

Available Formats

Security Level: intramural

LTE eNodeB License

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

1.3 LKF Types

1.3 LKF Types

1.3 LKF Types

2.2 States of Licenses

2.2 States of Licenses

3.2 Position of the License Tool in the System

3.2 Position of the License Tool in the System

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

Step 3: Click Search. In the displayed box,

Step 4: Select All from the Type drop-down list box..

If you select no, the license key file has an

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

NE information License Tool match Order information

License Tool matches site type

FNO generates license file

License file (zip)

Query license status

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

License Tool (offline adjustment) Note:

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

 In case of ESN change or license file transfer between eNodeBs,

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

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

NE information License Tool match Order information (FNO)

FNO self-service application

License file (.zip)

ESN electronic serial number

LSN license serial number

FNO FlexNet Operations System

PAC Preliminary Acceptance Certificate

You might also like