NodeB & RNC Capacity Licensing Model Offer

NodeB & RNC Capacity Licensing Model Offer
Provisioning Guide
Document number: UMT/PFO/APP/030572
Document issue: 01.14 / EN
Document status: Standard
Date: 8/9/2014
Passing on or copying of this document, use and communication of its contents not permitted without
Alcatel·Lucent written authorization
Copyright 2014 Alcatel-Lucent, All Rights Reserved
Printed in France
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write
protected”; it may be altered only by authorized persons. While copies may be printed, it is not recommended.
Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded
as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-
Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information
contained herein confidential, shall disclose the information only to its employees with a need to know, and shall
protect the information from disclosure and dissemination to third parties. Except as expressly authorized in
writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have
received this document in error, please notify the sender and destroy it immediately.
without notice. Nortel Networks assumes no responsibility for errors that might appear in t.All other brand and
NodeB & RNC Capacity Licensing Model Offer Provisioning Guide
PUBLICATION HISTORY
3/3/2010
Issue 01.01/ EN, Under review
Creation
11/3/2010
Issue 01.02/ EN, standard
Update after review, comments from SW supply chain and Ch D
26/8/2010
Add info on MC-TRX and RET for RRH
Review with Ch Dumont. Update section 4.8 with restrictions

27/12/2010
Update rule for RTU-carrier-activation: 3JR35004AAAA, aligned with SW portfolio
ordering guideline v 1.09.
o 1 Carrier_token to be purchased to be able to activate the first carrier
o 2 Carrier_token to be purchased to be able to activate the 2nd carrier
o 3 Carrier_token to be purchased to be able to activate the 3rd carrier
o 4 Carrier_token to be purchased to be able to activate the 4th carrier
24/2/2011
29/9/2011
RTU applicable to RRH are also applicable to TwinRRH. This information has been
added in the document.
Add RNC capacity licensing for eDCPS card in UA08.1
4/10/2011
Issue 01.07/ EN, for review
Apply changes on the carrier licensing, in accordance with FSD 112779 “unique
carrier licensing scheme for RRH and CPRI based RF modules”.
Change rules between UA07.1 and UA08.1 for the RTU Nb of radio per sector and
carrier activation on RTU/TRDU.
RTU: 3JR35004ACAA and 3JR35004AAAA are obsolete in UA08.1.
11/10/2011
Issue 01.08/ EN, Standard
Update reviewed and approved by PLM
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 2/25

18/10/2011
Update requested from Tendering team: section 5.1, 5.2 and 5.3
- RTU SCPA 55W is removed (no more sales on this product)
- RTU initial MCPA 30W (3JR35002AEAA) not used anymore and replaced by 2x
RTU 15W PA (3JR35002ACAA)
- RTU initial RRH/TRDU 20W (3JR35002AFAA ) not used anymore and replaced
by 2x RTU 10W (3JR35002ABAA)
4/11/2011
Minor updates on wording
30/10/2012
Section 7: Update RTU 3JR35020ACAA, change description RTU INTEGRATED RET FOR
RRH by RTU INTEGRATED AISG DEVICES MANAGEMENT
16/11/2012
Update based on W-CDMA SW portfolio guideline UMT/UTR/INF/030044 v1.15 nov
2012.
Section 6.2.2: replace code 3JR35045ACAA by 3JR35004AAAA, with a new rule
8/9/2014
Update with radio modules MC-TRDU

TABLE OF CONTENTS
TABLE OF CONTENTS .............................................................................................................................4
1. INTRODUCTION ............................................................................................................................6
1.1. OBJECT ....................................................................................................................................6
1.2. SCOPE OF THIS DOCUMENT .......................................................................................................6

1.3. AUDIENCE FOR THIS DOCUMENT ................................................................................................6
2. RELATED DOCUMENTS ..............................................................................................................7

2.1. REFERENCE DOCUMENTS ..........................................................................................................7
2.2. KNOWLEDGE TRANSFER SESSION ..............................................................................................7
3. CAPACITY LICENSING INTRODUCTION....................................................................................8

3.1. CAPACITY LICENSING FEATURE ..................................................................................................8
3.2. KEY PRINCIPLES .......................................................................................................................8
3.3. ORDERING SCHEME ..................................................................................................................9
3.4. HW RESOURCES CONTROLLED BY CAPACITY LICENSING .............................................................9
3.5. CAPACITY LICENSING PARAMETERS LIST...................................................................................10
4. CEM CAPACITY LICENSING .....................................................................................................12

4.1. RULES APPLIED ON INCREMENTAL DCH (D) ..............................................................................12
5. RADIO POWER CAPACITY LICENSING ...................................................................................14

5.1. MCPA POWER CAPACITY LICENSING ........................................................................................14
5.2. RRH AND TRDU POWER CAPACITY LICENSING.........................................................................14
5.3. MC-TRX POWER CAPACITY LICENSING ....................................................................................15
6. CARRIERS CAPACITY LICENSING ..........................................................................................17

6.1. CARRIER RTU ASSOCIATED WITH XTRM BOARD ......................................................................17
6.2. CARRIER RTU ASSOCIATED WITH RRH AND TRDU ..................................................................17
6.2.1 Rule applicable before UA08.1 release ........................................................................17

6.2.2 Rule applicable from UA08.1 release ...........................................................................18
6.3. CARRIER RTU ASSOCIATED WITH MC-TRX/MC-RRH/MC-TRDU ............................................18
6.4. RTU ASSOCIATED WITH NBER OF RADIO PER SECTOR ...............................................................18
6.4.1 rule applicable before UA08.1 release ..........................................................................18
6.4.2 rule applicable from UA08.1 release .............................................................................19
7. INTEGRATED RETA FOR RRH ..................................................................................................19
8. RNC CAPACITY LICENSING .....................................................................................................21

8.1. RTU ASSOCIATED WITH EDCPS BOARD.....................................................................................21

9. HARDWARE FULL CAPACITY ..................................................................................................22
10. LKDI RTU USED IN THIS DOCUMENT ......................................................................................23
11. ABBREVATIONS AND DEFINITIONS ........................................................................................24

11.1. ABBREVIATIONS ......................................................................................................................24
11.2. DEFINITIONS ...........................................................................................................................24

1. INTRODUCTION
1.1. OBJECT
The objective of this document is to guide the reader to know what product codes
need to be ordered in WCDMA with respect of the feature capacity licensing,
introduced in UTRAN release WCDMA UA06.0.
1.2. SCOPE OF THIS DOCUMENT

The scope of this document is the Model Offer Provisioning Guide for capacity
licensing, applicable to the Node B (digital part and radio part) and RNC.
This edition will address the provisioning of the initial nodes. It is applicable from
UMTS Release UA6.0. It is also applicable for further releases except if a new edition
of this document is available. Please check the last available edition of this document.
The hardware aspect is covered in the MOPG of the NodeB and RNC.
The Capacity licensing feature is not applicable to the OneBTS, nor the Micro or Pico
products.
Software & Services are outside the scope of this document.
The process of how to order this equipment is outside the scope of this document.
The scope of regions is worldwide.
1.3. AUDIENCE FOR THIS DOCUMENT

This is primarily an external document and secondarily an internal document; the
target audience is:
Alcatel-Lucent Customers (Network Engineering and Network operations)
Alcatel-Lucent Network Engineering, TSS, Sales, Product Marketing, Account
teams (for information & alignment)

2. RELATED DOCUMENTS
2.1. REFERENCE DOCUMENTS

NN-20500-240 - Alcatel-Lucent 9300 W-CDMA LKDI CLM User Manual
NN-20500-241 - Alcatel-Lucent 9300 W-CDMA LKDI RLA Administrator Manual
NN-20500-154 - Alcatel-Lucent W-CDMA Node B Capacity Licensing
UMT/UTR/INF/030044 W-CDMA SW Portfolio ordering guideline - UTRAN
Documents are available at : https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=53468779&objAction=browse&sort=nam
e&viewType=1
UMT/SYS/APR/023381 FN Capacity Licensing

licensing web sheets. : http://wsa.web.alcatel-
lucent.com/nav/#?navurl=http://wsa.web.alcatel-lucent.com/wcdma/licensing.php
2.2. KNOWLEDGE TRANSFER SESSION

TTP21146 -Part 1 UA06 Node B Capacity licensing Overview by F Iordache
TTP21230 - Capacity Licensing Process - LKDI (Tool) by Christophe Dumont
TTP 21234 - Capacity Management – Services offering by K EL Massaoudi

3. CAPACITY LICENSING INTRODUCTION
3.1. CAPACITY LICENSING FEATURE

To provide network facilities that include a better Return On Investment (ROI) for
customers, Alcatel-Lucent include in their Node B offer the possibility to "Pay as you
grow".
This allows a client to reduce initial costs by tailoring their Node B capacities to meet
their current network requirements. As network demands increase, the Node B license
capacity can be increased up to the maximum hardware capacities.
The capacity licensing scheme is the following:
• customers can buy HW at reduced cost; the HW capacity is restricted by a

license.
• additional capacity can be purchased when needed, w/o need to purchase and
install additional HW (until the actual HW capacity limit is reached)
The License is generated for one specific OAM (ROC) and contains the set of tokens
that can be distributed to all the Node Bs supervised by the OAM.
The tokens represent the sum of the feature values that can be manually applied to
the group of Node Bs in a RAN.
3.2. KEY PRINCIPLES

• The Capacity Licensing feature is a not optional feature in UA06/07. All customers
upgrading to UA6/UA7 must deploy licenses on their network,
• Capacity licensing operational terms must be decided & agreed with the customer
• Roles must be put in place in ALU regional teams, and at customer level to cope
with License Generation & Installation
• Perform Purchase Order of capacity into the ALU Ordering System using the
same process as HW. Network capacity increase is blocked until a new PO is
performed. Strong recommendation to always have RTU spares available in the
license.
• The RTUs associated with hardware capacity are available from release N
(introduction release) to release N + X. The logistical code associated with this
RTU is always the same. What it can happen from a release to an other:
o If the hardware capacity of a module increases from release (N) to

release (N + X), then the number of RTU associated with this capacity
increases too, but the logistical code remains the same. For ex: CEM
capacity, power capacity of radio modules.
o A new feature may introduce a new capacity licensing parameter and
then a new RTU. This RTU is available for release (N), (N+X) but does
not exist for release (N-1).

o In LKDI the version associated with the capacity licensing product,

corresponds to the UTRAN release introduction (N). It doesn’t mean this
capacity licensing is only available in this release, but it means this
capacity licensing is available from this release (N) to the release (N +
X). In the example bellow, “16CE-R99” is a capacity licensing introduced
in UA06 and available in UA07, UA08 as well. In the same way,
“Add_Radio_per_Sector” is available in UA07.1, UA08, etc …., but not
available in UA06.
3.3. ORDERING SCHEME

Capacity licensing can be ordered:
When ordering new Hardware modules – RTU capacity are purchased with the
HW configuration
RTU capacity can be purchased separately from HW
Feature Activation must be ordered before every upgrade: Features licenses must be
renewed each time there’s an upgrade to a new dot release
3.4. HW RESOURCES CONTROLLED BY CAPACITY LICENSING

For the capacity, the license is applied to increase the capacity of some functionalities
(such as number of users or amount of power), or to unlock other functionalities
(activation of frequency carriers).
The hardware resources that can be put under the Capacity Licensing framework are
the following:
Product based on 9311 Macro NodeB
• CEM board: iCEM, xCEM, eCEM.These boards were presentin the 9311
Macro NodeB
• TRM board: this module was present in the NodeB housing MCPA (9311
Macro, Street and rCompact), DR6 products.
• Radio PA: this module is present in the NodeB housing MCPA (Macro,
Street and rCompact).
Product based on 9926 BBU and 9926 BBU 4U

• CEM-U board:, xCEM-U and eCEM-U. These boards are part of the digital
controller D2U or D4U.

• RRH/MC-RRH/TwinRRH, TRDU, MC-TRDU, MC-TRX: these radio modules

are present in the solutions based on the 9326 D2U, 9926 BBU and 9926
BBU 4U as digital part.
RNC product
• EDCPS board: The feature 83985, introduced in release UA08.1 provides
the option to boost the capacity of a RNC equipped with eDCPS.
3.5. CAPACITY LICENSING PARAMETERS LIST

When the license is created in the LKDI, tokens are purchased for each parameter,
only whole numbers can be purchased. In the following list, the value of the token is
indicated.
The parameters are represented by the following attributes, which are respectively:
• edchNumberUserCapacityLicensing
defines the maximum number of tokens for HSUPA users.
One token = 8 connections
• edchThroughputCapacityLicensing
defines the maximum number of tokens for HSUPA throughput.
One token = 480 Kbps
• hsdpaNumberUserCapacityLicensing
defines the maximum number of tokens for HSDPA users.
One token = 8 connections
• hsdpaThroughputCapacityLicensing
defines the maximum number of tokens for HSDPA throughput.
One token = 1.8 Mbps
• r99NumberCeCapacityLicensing
defines the number of Channel Elements (CEs) that the Node B is allowed to allocate
for R99 traffic (common or dedicated channels). the value range is from 16 to 65520.
One token = 16 CEs.
• paPowerCapacityLicensing
defines the power allowed for the pool of PAs (by increments of 1Wat the NodeB). A
minimum of 30W/PA is allocated - One token = 15W.
• rrhPowerCapacityLicensing
defines the power allowed for all RRHs or TRDUs related with the Node B (by
increments of 1Wat the NodeB). A minimum of 20W/RRH is allocated - One token =
10W.
• xTRMCarrierCapacityLicensing
defines the number of secondary Rx carriers allowed for the pool of xTRMs. One
token = 1 carrier

• rrhCarrierCapacityLicensing (obsolete in UA08.1)

defines the number of secondary Rx carriers allowed for the pool of RRHs or TRDUs.
One token = 1 carrier.
• additionalRadioPerSectorCapacityLicensing (Obsolete in UA08.1)

defines the number of additional radios per sector allowed for the Macro legacy with
PA. One Token = 1 additional radio module.
This parameter is kept (default value “infinite”, but not supervised by capacity licensing
anymore.
• radioCarrierCapacityLicensing
st nd rd
Introduced in UA08.1 for carrier licencing. It applies to all carriers, 1 , 2 , 3 , ….
• NbOfRetaCapacityLicensing
Associated with the feature Integrated RETA support at the RRH.
One Token = per NodeB supporting the feature
• integratedAisgDevicesManagement
Introduced in RAN model UA08.1 Drop9 . Limitation of Number of sites with Integrated AISG
devices management.
This feature completes the RETA for RRH feature 33213/ 97006 that was delivered in UA7.1.3,
by adding capacity licensing to manage its deployment. / / / RETA for RRHs: / / RRH (Remote
Radio Heads) is an alternative to standard Node-B solution. Therefore, the support of RETA is
strongly expected by the Customers, as for RETA with standard macro Node-B.

4. CEM CAPACITY LICENSING

As a strong market request for limited CEM processing capacity steps has been
identified, the CEM capacity for R99 and HSPA connections can be purchased in
small steps in order to allow for cheap initial configurations and capacity upgrades
according to the “pay-as-you-grow” principle.
The following RTU are associated with all types of CEM boards (iCEM (U), xCEM (U),
eCEM (U). The CEM board is housed in the digital part of the NodeB.
Initial RTU Capacity

RTU code Description capacity
value
3JR35001AAAA RTU INCREMENT DCH 16 CE 0 1 RTU (D) = 16 CE
3JR35001ADAA RTU INCREMENT 8 HSDPA CONNECTION 0 1 RTU (H1) = 8 HSDPA connections
3JR35001AFAA RTU 1800KBPS HSDPA 0 1 RTU (H2) = Peak DL 1800 Kbit/s
3JR35001AEAA RTU INCREMENT 8 HSUPA CONNECTION 0 1 RTU (E1) = 8 EDCH connections
3JR35001AGAA RTU 480KBPS EDCH 0 1 RTU (E2) = Peak UL 480 Kbit/s
Initial capacity value = 0: The board is delivered with no capacity. The capacity in term
of CE, HSxPA connections and throughput requires the order of Incremental RTUs.
The number of RTU can be calculated as follows:
Nb of D token = nb of required CE/16
Nb of H1 token = number of HSDPA cnx/8
Nb of H2 token = required throughput/1.8
Nb of E1 token = number of HSUPA cnx/8
Nb of E2 tokens = required throughput/0.48
The following table summarizes the max number of RTU per CEM card and per
release:
UTRAN Release Type of CEM Number of tokens per CEM
D H1 H2 E1 E2
xCEM/xCEM-u
UA07 16 16 22 16 21
eCEM/eCEM-u
xCEM/xCEM-u
16 16 22 16 68
UA08.1 eCEM
eCEM-u 16 16 33 16 68
4.1. RULES APPLIED ON INCREMENTAL DCH (D)

The xCEM or eCEM board supports up to 256 DCH calls with any 128 of them
supporting HSDPA and/or HSUPA.
Example: if you order the maximum number of CE per xCEM, (256 CE), and if you
need to establish 128 HSxPA connections, the CE assessment is the following

• 1 Signaling Radio Bearer per HSxPA connection => 128 CE for SRB
• 128 CE are available for R99 calls.
i.e: 256 CE per xCEM doesn’t mean 256 R99 calls per xCEM, the number of HSxPA
connections must be considered first.
This table provides the maximum capacity on each type of CEM board.
CEM Capacity R99 CE HSDPA HSDPA EDCH EDCH Throughput
Users Throughput Users
iCEM64 max 1d-iBBU 64 CE 48 Users 10800 Kbps 15 Users 2100 Kbps
iCEM128 max 2 d-iBBU 128 CE 96 Users 21600 Kbps 30 Users 4200 Kbps
xCEM/eCEM in BBU 256 CE 128 Users 28800 Kbps 128 Users 7680 Kbps (UA06)
mode 10080 Kbps (UA07)

5. RADIO POWER CAPACITY LICENSING

These RTU applied to the following radio modules:
o MCPA or SCPA inside the Macro Legacy NodeB
o RRH, Twin RRH and MC-RRH in 3G mode

o TRDU, MC-TRDU in 3G mode
o MC-TRX in 3G mode
5.1. MCPA POWER CAPACITY LICENSING

The Radio MCPA is found in the MACRO, STREET and RCOMPACT NodeB.
The Radio Power Amplifier can be purchased in small steps in order to allow for cheap
initial configurations and capacity upgrades according to the “pay-as-you-grow”
principle.
The initial configuration of the MCPA (850, 1900 and 2100 MHz) is 30W. The power
capacity can be increased in 15W steps, till the maximum MCPA power, as shown in
the figure.
From UA07.1, the same RTU is used for initial and incremental capacity.
H/W RTU RTU

0 capacity + 15W
capacity +
15W
capacity
H/W code 30W Initial Incremental capacity

Order 2 x RTU Order N x RTU 15W
ITEM TO ORDER
RTU code Description RTU Capacity

Order at least 2 RTU to get the 30W
3JR35002ACAA RTU INCREMENT 15W PA OUTPUT initial capacity and N x RTU for each
additional 15W power capacity.
5.2. RRH AND TRDU POWER CAPACITY LICENSING

RRH (RRH, MC-RRH, TwinRRH) and TRDU (TRDU60, TRDU2x80, MC-TRDU) are
the radio modules associated with a 9326 D2U or 9926 BBU (D2U or D4U) as digital
part of the NodeB.

MC-RRH and MC-TRDU can work in 2G mode, associated with SUMx and in 3G
mode associated with a D2U or D4U. Capacity licensing applies in this document is
only for MC-RRH or MC-TRDU in 3G mode.
The first step is the initial configuration of the radio module. The minimum power is
20W. 2x RTU 10W must be ordered to get the minimum capacity.
The power capacity can be increased in 10W steps, till the maximum power of the
module, as shown in the figure.
H/W RTU RTU

0 capacity + 10W
capacity +
10W
capacity

ITEM TO ORDER

Order at least 2 RTU to get the
20W initial capacity and N x RTU
3JR35002ABAA RTU INCREMENT 10W RRH OR TRDU
for each additional 10W power
capacity.
5.3. MC-TRX POWER CAPACITY LICENSING

The MC-TRX is a radio module which can work in 2G mode, associated with a SUMx
or in a 3G mode, associated with a 9326 D2U or 9926 BBU as digital part of the
NodeB.
MC-TRX Capacity licensing applies in this document is only for MC-RRH in 3G mode.
The first step is the initial configuration of the radio module. The minimum power is
20W. 2x RTU 10W must be ordered to get the minimum capacity.
The power capacity can be increased in 10W steps, till the maximum power of the
module, as shown in the figure.
H/W RTU RTU

10W 10W
0 capacity + capacity + capacity


ITEM TO ORDER

Order at least 2 RTU to get the
20W initial capacity and N x
3JR35002ABAA RTU INCREMENT 10W RRH OR TRDU
RTU for each additional 10W
power capacity.

6. CARRIERS CAPACITY LICENSING

These RTU applied to the following radio modules:
o XTRM associated with MCPA inside the Macro Legacy NodeB

o RRH, Twin RRH and MC-RRH in 3G mode
o TRDU, MC-TRDU in 3G mode
o MC-TRX in 3G mode
6.1. CARRIER RTU ASSOCIATED WITH XTRM BOARD

The xTRM board is always associated with MCPA. As a consequence, this board is
found in the MACRO, STREET and RCOMPACT NodeB, DR6 products.
xTRM can be configured with at most 2 Rx Carriers. The first carrier activation on the
TRM board is not concerned by the capacity licensing.
The activation of the second carrier in the xTRM is subject to capacity licensing.
RTU
H/W
1 carrier + Incremental
carrier
H/W code RTU 2nd carrier
ITEM TO ORDER

3JR35003AAAA RTU INCREMENT XTRM 2ND CARRIER ACTIV 1 RTU = 1 additional Carrier
6.2. CARRIER RTU ASSOCIATED WITH RRH AND TRDU
6.2.1 RULE APPLICABLE BEFORE UA08.1 RELEASE

The current carrier licensing scheme for RRH and TRDU starts with the second carrier
activation. The first carrier is not under capacity licensing.
st
Pricing Rule to compute quantity: 1 carrier priced per 3G-only Radio Module, only
nd
when purchasing 2 carrier.

ITEM TO ORDER

Order 1 RTU per carrier activation. (Example: 3 carriers
3JR35004AAAA RTU CARRIER ACTIVATION
activation order 3 RTU).
6.2.2 RULE APPLICABLE FROM UA08.1 RELEASE

The new licensing scheme includes the licensing of first carrier for RRH (TwinRRH),
TRDU, MCTRX and MCRRH. All carriers are considered as identical. There will thus
be only one license parameter for the number of carriers per radio module.
The RTU to order for RRH and TRDU in this release is the same RTU than in the
previous release, but the rule is changed.: the activation is “per carrier”
RTU
H/W
0 capacity + Incremental
carrier
H/W code N x RTU carrier activation
ITEM TO ORDER

Order 1 RTU per each carrier activation (including
3JR35004AAAA RTU CARRIER ACTIVATION
STSRx, STSRx+y)
6.3. CARRIER RTU ASSOCIATED WITH MC-TRX/MC-RRH/MC-

TRDU
The activation of the carrier in the MC-TRX, MC-RRH or MC-TRDU in 3G mode is
subject to capacity licensing for the first carrier activation.
ITEM TO ORDER

RTU MC_TRX_RRH CARRIER
3JR35045ACAA ACTIVATION Order 1 RTU per each carrier activation.
6.4. RTU ASSOCIATED WITH NBER OF RADIO PER SECTOR
6.4.1 RULE APPLICABLE BEFORE UA08.1 RELEASE

In UA07.1, a configuration token for number of radios (PA/TRDU/RRH) per sector is
required. One token controls the configuration of two radios (PA/TRDU/RRH) on one
sector, i.e. it allows the activation of y carriers for STSR (x+y ) configurations

In the following figure, xTRM1 is associated to one PA / sector and xTRM2 is

associated to the second PA of the same sector. In that case we need to order this
RTU to support such configuration.
6 Rx signals (3 sectors Main + Div )

Macro Node B Sector 1
M/D
GPSAM xTRM 1 PA 1
DDM 1
Processes
PA 2
TX f1
RX f1
iCEM or iCCM 2 or Sector 2
M/D
xCEM xCCM PA 3
DDM 2
PA 4
xTRM 2
Processes Sector 3
TX f2 PA 5 M/D
RX f2
DDM 3
STSR x+y
PA 6
6 Rx signals (3 sectors Main + Div ) Main antennas f1(x)

Div antennas f2 (y)
Figure 1: Configuration STSR x+y in Macro NodeB
ITEM TO ORDER

3JR35004ACAA INCREMENT RTU ADD. RADIO PER SECTOR 1 RTU = 1 additional Radio/Sector
6.4.2 RULE APPLICABLE FROM UA08.1 RELEASE

In UA08.1, it has been decided to remove the parameter
“additionalRadioPerSectorCapacityLicensing” from the licensing scheme, which it
introduces unnecessary complexity at upgrades and in the toolchain.
In other word, in UA08.1, RTU: 3JR35004ACAA becomes obsolete.
7. INTEGRATED RETA FOR RRH

This RTU is introduced in UA07.1.3 release, with the feature Integrated RETA support
at the RRH. RETA for RRHs saves the capital expense of purchase of a separate
CCU and associated tower cabling.
The RTU is applicable per NodeB, whatever the number of RRHs and the number of
RRH per sector.
RRH supporting the feature:

2100 MHZ RRH40-21, RRH60-21/21A/21C, RRH2x60
900 MHz RRH60-09 and RRH60-09A

AWS RRH40-AWS
1900 MHz RRH40/60, RRH2x60
850 MHz RRH40/60, RRH2x60
Restrictions:
RRH20-21 is not supported by the feature
Release UTRAN UA07.1.3 minimum.
ITEM TO ORDER

1 RTU per NodeB supporting the
RTU INTEGRATED AISG DEVICES feature.
3JR35020ACAA MANAGEMENT (release of introduction= UA07.1.3)

8. RNC CAPACITY LICENSING
8.1. RTU ASSOCIATED WITH EDCPS BOARD

The feature 83985, introduced in release UA08.1 provides the option to boost the
capacity of a RNC equipped with eDCPS only through software. Additional capacity
brought by eDCPS is locked (at global RNC level), unless a specific License Key is
delivered. Capacity increase brought by capacity license is only working if the 9370
RNC is 100% eDCPS.
ITEM TO ORDER
Order Code Code Description Provisioning Rule

3JR35043ABAA LKDI RTU Qty= 1 per RNC shelf, to validate the eDCPS full
RNC_eDCPS_capa_increase capacity

9. HARDWARE FULL CAPACITY

If the commercial contract authorises to have No capacity Limitation on a given NodeB
resources, then Regional License Admin will use a specific process for requesting the
creating of the appropriate RTU entitlements. But be aware that such request will
necessitate approval from WCDMA Licensing Administrator
Note that the full capacity licence is applicable per OMC, meaning that all the NodeB
driven by this OMC have to follow the same rules in term of capacity licensing.

10. LKDI RTU USED IN THIS DOCUMENT

RTU Code Designation
3JR35001AAAA LKDI RTU INCREMENT DCH 16 CE
3JR35001ADAA LKDI RTU INCREMENT 8 HSDPA CONNECTION
3JR35001AEAA LKDI RTU INCREMENT 8 HSUPA CONNECTION
3JR35001AFAA LKDI RTU 1800KBPS HSDPA
3JR35001AGAA LKDI RTU 480KBPS EDCH
3JR35002ABAA LKDI RTU INCREMENT 10W RRH OR TRDU
3JR35002ACAA LKDI RTU INCREMENT 15W PA OUTPUT
3JR35003AAAA LKDI RTU INCREMENT XTRM 2ND CARRIER ACTIV
3JR35004AAAA LKDI RTU CARRIER ACTIVATION
3JR35004ACAA INCREMENT RTU ADD. RADIO PER SECTOR
3JR35045ACAA LKDI RTU CARRIER ACTIVATION
3JR35020ACAA LKDI RTU INTEGRATED RET FOR RRH
3JR35043ABAA LKDI RTU RNC_eDCPS_capa_increase

11. ABBREVATIONS AND DEFINITIONS
11.1. ABBREVIATIONS
BTS Base Transceiver Station
CCM Core Control Module
CEM Channel Element Module
DDM Dual Duplexer Module
D2U Digital 2U
E-DCH Enhanced Dedicated Channel
FRU Field Replaceable Unit
FRUP Field Replaceable Unit Prevented
HSUPA High Speed Uplink Packet Access
HSDPA High Speed Downlink Packet Access
ICCM Integrated Core Control Module
ICCM2 2nd generation of iCCM (integrated Core Control Module)
nd
ICEM2 2 generation of iCEM (integrated Channel Element Module)
LKDI License Key Delivery Infrastructure
MCPA Multi Carrier Power Amplifier
PCM Pulse Code Modulation
RRH Remote Radio Head
RNC Radio Network Controller
RoHS Restriction of Hazardous Substance
ROI Return On Investment
RTU Right To Use
SRB Signaling Radio Bearer
SRU Shop Replaceable Unit
SCPA Single Carrier Power Amplifier
iTRM/xTRM Transceiver Receiver Module
TRDU Transmitter Receiver Duplexer Unit
UMTS Universal Mobile Telecommunications System
11.2. DEFINITIONS
Ancillaries Miscellaneous hardware items used for installing and

interconnecting Alcatel-Lucent equipment (ex: cables and
connectors). The customer can either order them from Alcatel-

Lucent or buy them locally.

Configuration Defined list of values for the features associated with the product.
Extension Adding more bandwidth to the current configuration.
Feature Portion of the product design that represents a specific
functionality.
Initial Functional product configuration for a new installation.
Kit Pre-defined bundle of parts/items providing a given product
feature or option.
Optional feature Non-mandatory feature that can be provided to enhance the
configuration.
Package A bundle of items that are NOT functional by themselves
(e.g. configuration extension, upgrade, feature or option
addition).
Product Bundle of hardware and software items that provides a specific
function in the telecom network.
Upgrade When the hardware/software platform is being enhanced to add
new functionality or value.
BP Building Package. A building package is a no functional model;
Building Package for example a kit.
FRU A Field Replaceable Unit is an HWI (Hardware Item) that may fail
Field Replaceable Unit or is in the scope of preventive maintenance and that customers
should have in stocks. FRUs have dependability data (MTBF or
life duration). An FRU must be alarmed.
FRUP It's an HWI (Hardware Item) with lifetime limited, periodically
Field Replaceable Unit replace, and maintenance procedure associated with; for
Prevented example an air filter.
SRU It's a HWI (Hardware Item) that might be replaced on site when
Shop Replaceable Unit broken. An SRU does not require a spare on field. SRU is not
associated with a MTBF
SAV Is considered as SAV, technical items (HWI = Hardware Item)
Spare Apart Volume potentially requested by customers in case of damage and that
ALU accept to sale as stand alone.
A SAV item is a lowest orderable items and a SLI sub-element.
A SAV item have to be codified and documented in PDM tool and
ecat but not in the MOPG.
A SAV item is not proposed in ALU customer catalog
END OF DOCUMENT 

NodeB &amp; RNC Capacity Licensing Model Offer

Uploaded by

Document Information

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

NodeB &amp; RNC Capacity Licensing Model Offer

Uploaded by

Copyright:

Available Formats

NodeB & RNC Capacity Licensing Model Offer

Copyright 2014 Alcatel-Lucent, All Rights Reserved

Review with Ch Dumont. Update section 4.8 with restrictions

o 1 Carrier_token to be purchased to be able to activate the first carrier

o 2 Carrier_token to be purchased to be able to activate the 2nd carrier

o 3 Carrier_token to be purchased to be able to activate the 3rd carrier

o 4 Carrier_token to be purchased to be able to activate the 4th carrier

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 2/25

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 3/25

1.2. SCOPE OF THIS DOCUMENT .......................................................................................................6

2. RELATED DOCUMENTS ..............................................................................................................7

3. CAPACITY LICENSING INTRODUCTION....................................................................................8

4. CEM CAPACITY LICENSING .....................................................................................................12

5. RADIO POWER CAPACITY LICENSING ...................................................................................14

6. CARRIERS CAPACITY LICENSING ..........................................................................................17

6.2.1 Rule applicable before UA08.1 release ........................................................................17

7. INTEGRATED RETA FOR RRH ..................................................................................................19

8. RNC CAPACITY LICENSING .....................................................................................................21

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 4/25

9. HARDWARE FULL CAPACITY ..................................................................................................22

10. LKDI RTU USED IN THIS DOCUMENT ......................................................................................23

11. ABBREVATIONS AND DEFINITIONS ........................................................................................24

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 5/25

1.2. SCOPE OF THIS DOCUMENT

1.3. AUDIENCE FOR THIS DOCUMENT

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 6/25

2.1. REFERENCE DOCUMENTS

UMT/SYS/APR/023381 FN Capacity Licensing

2.2. KNOWLEDGE TRANSFER SESSION

TTP 21234 - Capacity Management – Services offering by K EL Massaoudi

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 7/25

3. CAPACITY LICENSING INTRODUCTION

3.1. CAPACITY LICENSING FEATURE

• customers can buy HW at reduced cost; the HW capacity is restricted by a

3.2. KEY PRINCIPLES

o If the hardware capacity of a module increases from release (N) to

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 8/25

o In LKDI the version associated with the capacity licensing product,

3.3. ORDERING SCHEME

3.4. HW RESOURCES CONTROLLED BY CAPACITY LICENSING

Product based on 9311 Macro NodeB

Product based on 9926 BBU and 9926 BBU 4U

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 9/25

• RRH/MC-RRH/TwinRRH, TRDU, MC-TRDU, MC-TRX: these radio modules

3.5. CAPACITY LICENSING PARAMETERS LIST

One token = 8 connections

One token = 480 Kbps

One token = 8 connections

One token = 1.8 Mbps

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 10/25

• rrhCarrierCapacityLicensing (obsolete in UA08.1)

• additionalRadioPerSectorCapacityLicensing (Obsolete in UA08.1)

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 11/25

4. CEM CAPACITY LICENSING

Initial RTU Capacity

4.1. RULES APPLIED ON INCREMENTAL DCH (D)

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 12/25

UMT/PFO/APP/030572 01.14 / EN Standard 8/9/2014 Page 13/25

5. RADIO POWER CAPACITY LICENSING

o MCPA or SCPA inside the Macro Legacy NodeB

o RRH, Twin RRH and MC-RRH in 3G mode

5.1. MCPA POWER CAPACITY LICENSING

H/W RTU RTU

H/W code 30W Initial Incremental capacity

NodeB & RNC Capacity Licensing Model Offer

NodeB & RNC Capacity Licensing Model Offer