RBS6000 MCPA TRX Technical Document PA1

RBS6000 MCPA TRX Technical
1 (20)
Prepared (also subject responsible if other)
No.
CBC/ND/R/S lizhong zhao

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
RBS6000 MCPA TRX technical document

1
RBS6000 MCPA overview

1.1 MCPA TRX introduce
1.2 MCPA Power Distribution and Sharing
1.3 Work Mode of MCPA
1.4 MCPA Power Overbooking and Temporary Power Override
1.5 MCPA backed-off
Feature Considerations
2.1 No available features:
2.2 Recommend Features
Power parameter in Single Mode
BSS license
Some license command
About MCPA Parameters
Managed Object (Single Mode)
RBS OMT configuration
9.
RBS DT example
9.1 BSC Software upgrade
9.2 License installation
9.3 RBS Software upgrade
9.4 RBS configuration DT

2 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
1. RBS6000 MCPA overview

1.1
MCPA TRX introduce
The digital part of each TRX is located on the DUG 20 unit

The radio part is located in the RUS unit
Multi Carrier Power Amplifier (MCPA) will be capable of amplifying signals from many TXs at the same
time.
RBS 6000 with DUG 10 and RUG does not contain any MCPA based TRXs.
RBS 6000 with DUG 20 and RUS contain MCPA based TRXs.

3 (20)
No.

Approved
1.2
Checked
Date
Rev
2012-02-10
PA1
Reference
MCPA Power Distribution and Sharing
The MCPA in the RUS supports several TRXs sharing the same output power
All users that are allocated on the same TS in the air and using the same PA will share the total mean
MCPA Power
The total power used on a certain TS on an MCPA can not exceed the maximum mean power that the
PA can support

4 (20)
No.

Approved
1.3
Checked
Date
Rev
2012-02-10
PA1
Reference
Work Mode of MCPA
Backwards compatible mode

When using BTS SW version G11A with any BSC SW version
When using any BTS SW version and BSC SW version older than G10B
The BSC is unaware of that some TRXs are tightly connected via MCPA.
Single mode
When using BTS SW version G11B or newer with BSC SW version G10B or newer
The BSC is responsible for configuration of the power distribution within the MCPAs
It is also possible to configure more power than available in the MCPA (overbooking).
Mixed mode

5 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
When using BTS SW version G12A or newer with BSC SW version G11B or newer
The MCPA is shared between GSM and WCDMA or LTE.
The BSC is responsible for configuration of the power distribution within the GSM part of the MCPAs
1.4 MCPA Power Overbooking and Temporary Power Override
Overbooking ( one TS)

The sum of BSC configured TX power for all TRXs using the same MCPA may exceed the maximum
MCPA Power
Normally not all users that want to transmit via the MCPA at a certain time need the full configured
power.
Some channels might not be allocated at all, other users may be configured these power.
This is allowed only if:
Feature GSM MCPA Intelligent Power Management is available
Configuring HW activation codes for at least 3 GSM TRXs
Configuring HW activation codes for MCPA power corresponding to the maximum MCPA power
Temporary power override (one MCPA)

6 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
When the MCPA power is overbooked

there is though a theoretical risk that the MCPA power is not enough to cover the need for all users
that want to transmit via the MCPA at a certain time
Temporary power override makes it possible to overuse the MCPA power for short periods of time,
as long as the long time average is kept below the maximum MCPA power
The temporary power override functionality is not available for all RUS configurations (For instance
configuring a RUS 02 for 6 TRXs or more)
1.5
MCPA backed-off
If the sum of ordered power on all TRXs exceeds the MCPA maximum power during a specified time the channels
used for the most robust connections (the lowest priority channels) will be backed-of
If the maximum allowed amount of back-of for the channels with lowest priorityis not enough to reach the goal,
then also channels with the second lowest priority will be backed-of and so on.
If temporary power override is activated the mean power averaged during a longer time (several TDMA frames) is
monitored. If not, the mean power for each TS is monitored

7 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
Feature Considerations
2.1 no available features:

Antenna Hopping and Find Faulty Transmit Antenna Data
Software Power Boost (not supported on MCPA based cells)
Transmitter Coherent Combining (not available since there is no extra gain compared to configuring
higher output power per TX)
Frequency Hopping over wider range than the MCPA supported bandwidth
BTS Power Savings and TS Power Savings (not recommended since turning off one TRX or TS out of
several in an MCPA will not significantly reduce the power consumption and would only risk causing
unnecessary handovers)
2.2 Recommend Features

Dynamic BTS Power Control
Dynamic MS Power Control
Discontinuous Transmission (DTX) Downlink
Discontinuous Transmission (DTX) Uplink
Reduced Power Level after Handover
Dynamic HR Allocation and/or Dynamic FR/HR Adaptation
Power parameter in Single Mode

RXMOI: MO=MCTR-xx-x [,MAXPWR=maxpwr] [,MAXTRX=maxtrx] [,TXMPWR=auto/manual] [,PAO=pao];
RXMOI: MO=TX-xx-,BAND=band,MPWR=mpwr[,ANT=ant];

8 (20)
No.

Approved
Checked
40dbm
10W
42dbm
15W
43dbm
20W
45dbm
30W
46dbm
40W
48dbm
60W
49dbm
80W
Date
Rev
2012-02-10
PA1
Reference
When defining a MCTRI MO Using the parameter TXMPWR it is possible to decide whether to use equal
sharing or not.
TXMPWR=AUTO

9 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
The system will distribute the available MCPA power equally between the configured TRXs .
the maximum TX power is set automatically for the TX when its superior TRXC is connected to the
MCTR. In this mode the maximum TX power must not be changed manually.
The maximum TX power is equal for all TXs using the MCTR and its value is calculated according to
the following algorithm: the maximum power of MCTR is divided by the maximum number of TRXCs
that can be connected to the MCTR. If the maximum power of MCTR or the maximum number of
TRXCs that can be connected to the MCTR or both are changed, then the maximum TX power is
recalculated for each TX with superior TRXC connected to the MCTR.
there will be no possibility to configure more power on the sum of TRXs than the configured total
MCPA mean power
TXMPWR=MANUAL
All power configuration will be made manually by using the parameter MPWR on the different TXs.
Each time TRXC with subordinate TX is connected to the MCTR, a check is made if the maximum
power of MCTR is not exceeded.
When PA overbooking is activated then the maximum power of MCTR can be exceeded.
it may also be possible to configure more power on the sum of TRXs than the configured total
MCPA mean power (overbooking).
When defining a TX MO,
parameter MPWR is mandatory if superior TRXC is not connected to MCTR or is connected to
MCTR configured with parameter TXMPWR=MANUAL.
The parameter MPWR is not allowed when superior TRXC is connected to MCTR configured with
parameter TXMPWR=AUTO.
When TXMPWR=MANUAL and PAO=OFF
The sum of maximum TX power values of all TXs using MCTR must not exceed the maximum
mean output power of MCTR.
When parameter PAO=ON is specified for a MCTR MO

10 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
MAXPWR and MAXTRX must be given.

Parameter PAO=ON is only allowed in combination with parameter MAXPWR equal 48 and
parameter MAXTRX equal or greater than 3.
BSS license
From BSC G10B, each BSC node needs to have one Key File containing a number of license keys and
HW activation codes. The Key File is a partly encrypted file that contains license information and HW
activation codes about products. (One Key File: containing a number of license keys and HW activation
codes about products)
Information in the Key File:
HW Resource Name -- identify a specific hardware or node in ELIS (BSC node name in OSS-RC)
Fingerprint
License keys
HW activation codes
Digital signature.
Fingerprint
an identity of the BSC that is used to lock the Key File
must be obtained from the BSC and added to ELIS before the Key File can be generated.
the APG40 must be updated to at least AGM020 and APG43 must be updated to at least AGM317 to
be able to obtain the fingerprint
Emergency unlock
Can be used if the operator needs to immediately make some traffic related capacity (which is under
license control) unrestricted for a node
Is intended to be used in case of emergency such as natural disasters
grace mode in the following scenarios
When license key file is missing, invalid or corrupted
When node fingerprint is changed
The CP can't contact the license manager in the APG
License about MCPA:

FAK 101 0008 RUS HW Activation GSM TRXs
G10B
FAK 101 0009 RUS HW Activation 20 to 40W, If more than 20W per RUS is to be used
G10B

11 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
FAK 101 0010 RUS HW Activation 40 to 60W, if more than 40W per RUS is to be used
G10B
G12A
G12A
NOTE: With BTS SW older than G12A_1 or BSC SW older than G12A it will not be possible to set the MCPA power with one
decimal. This means that the power in dBm is abbreviated to a suitable level of HW activation codes. Using MAXPWR=48 dBm
(60W) will thus not require a HW activation code for 60->80 W.
NOTE: However when using BTS G12A_1 or newer with BSC G12A or newer, the value MAXPWR=48.0 dbm (60W) will require
a HW activation code for 60->80 W.
For example:
Configuring 2 TRXs per MCPA and a total of 40 W per MCPA, in a BTS equipped with 3 RUS 01, then there must be:
six GSM TRX HW activation codes

three 20->40W HW activation codes available for this BSC
For example:
Configuring an MCPA with 4 TRXs and 60W (48 dBm), there is a need
four GSM TRX HW activation codes

one 20->40W HW activation code
one 40->60W HW activation code

12 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference

13 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
5. Some license command

lmemstart [-f]
-f
force
This option activates the Emergency State Capacity Unlock Mode without a confirmation request.
This command activates the Emergency State Capacity Unlock Mode.

The Emergency State Capacity Unlock Mode allows to free up all capacity for a period of 7 days.
The activation can be done only twice after which Emergency State Mode is not allowed unless a new License Key File with a
valid Emergency State Reset Key is installed using the command lminst.
This command can be executed only on AP1 active node.
Example: 1
The following example activates the emergency state.
Lmemstart
Are you sure you want to enter the Emergency State Mode (y/n)?: y
Example: 2
The following example activates the emergency state without confirmation.
lmemstart -f
lmfpprint
This command prints the fingerprint (FP) of the system. It can be executed only on Application Platform (AP) 1 active node.

14 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
The FP is an identity of the system that is used to lock the License Key File to that system only.
Example: 1
Lmfpprint
CUSTOM FINGERPRINT: 1e-*1YC E2CJ WYZJ 32BJ
lminst lkfpath
- lkfpath
License Key File path

This operand specifies the filename with full path or relative path of the License Key File to be installed.
Installs a License Key File.

Is stored in the directory K:\ACS\data\LM.
local backup copy of the installed License Key File is stored in C:\Programfiles\AP\ACS\sys.
The License Key File is valid only if every License Key is valid in the License Key File.
If the installation fails, the previous valid License Key File is retained.
It can be executed only on Application Platform (AP) 1 active node.
Example: 1
The following example installs the License Key File C:\temp\license.txt.
lminst C:\temp\license.txt
lmlkls [-e daystoexpire]
-e daystoexpire
Expiring License Keys.
This option lists the License Keys which will expire within the specified number of days.
Signed integer 1 - 60
This command lists the installed License Keys and their status. License Keys have been previously installed through lminst
command.
This command can be executed only on Application Platform (AP) 1 active node.
Example: 1
The following example lists License Keys installed on the node and their status.
Lmlkls
LKID
CXC001
CXC002
START
2009/01/12
2008/02/15
END
2009/12/05
2009/01/19
VALUE
15
10
DESCRIPTION
advice-of-charge
advice-of- Callwaiting

15 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
6. About MCPA Parameters
IPM is a parameter set per MCTR MO to activate and deactivate the temporary power override functionality, to better
utilize the MCPA power. Default value is OFF.
MAXPWR is a parameter set per MCTR MO to define the maximum allowed mean power used by the MCPA,
corresponding to a certain HW activation code. This parameter can be set with one decimal from G12A and on. The
default value is 43.0 dBm.
MAXTRX is a parameter set per MCTR MO to define the maximum number of TRXs possible to connect to the MCPA,
corresponding to the same amount of HW activation codes for GSM TRXs. The value range is 0-16, but not all values
are applicable for all MCPA HW variants, The default value is 0.
MCTRI is a parameter set per TRXC MO to map the TRX to a specific MCPA.Applicable values are 0-15 and UNDEF
(which means that the TRX is not connected to any MCPA). Default value is UNDEF
MPWR is a parameter set per TX MO to limit the maximum cell power (BSPWRB/BSPWRT) that may be used for this
TX. Applicable values are 0-63 dBm. See further parameter TXMPWR.
PAO is a parameter set per MCTR MO to decide whether overbooking of MCPA power shall be allowed or not. If it is set
to ON the sum of maximum TX power values (MPWR) of all TXs using given MCPA may exceed the maximum mean
power of MCPA (MAXPWR). To utilize this mode the parameter TXMPWR must be set to MANUAL. If it is set to OFF
the sum of maximum TX power values (MPWR) of all TXs using given MCPA may not exceed the maximum mean
power of MCPA (MAXPWR). Default value is OFF.
TXMPWR is a parameter set per MCTR MO to decide with what method the maximum TX power (MPWR) shall be set.
The mode AUTO means that MPWR is set automatically for the TX when its superior TRXC MO is mapped to the MCTR
MO. In this mode MPWR must not be changed manually. The maximum MCPA power (MAXPWR) will be equally
divided between all TXs using the MCPA (MAXTRX). The mode MANUAL means that the maximum TX power is set
manually with the parameter MPWR. The default value is AUTO.

16 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
7. Managed Object (Single Mode)
A TG MO consists of a maximum number of
16 TRXCs
16 RXs
16 TXs
128 TSs
16 MCTRs
16 channel groups.
one CF
one IS
one TF
one CON
four DPs.
Reference

17 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
MO Class
MO Identification
Value Range
TG
CF
CON
IS
DP
RXOTG-tg
RXOCF-tg
RXOCON-tg
RXOIS-tg
RXODP-tg-ldp
TF
MCTR
RXOTF-tg
RXOMCTR-tg-lmctr
TRXC
RXOTRX-tg-ltrxc
RX
RXORX-tg-ltrxc
TX
RXOTX-tg-ltrxc
TS
RXOTS-tg-ltrxc-lts
tg
tg
tg
tg
tg
ldp
tg
tg
lmctr
tg
ltrxc
tg
ltrxc
tg
ltrxc
tg
ltrxc
lts
Reference
0-2047
0-2047
0-2047
0-2047
0-2047
0-3
0-2047
0-2047
0-15
0-2047
0-15
0-2047
0-15
0-2047
0-15
0-2047
0-15
0-7
8. RBS OMT configuration

9. RBS DT configuration
9.1 BSC Software upgrade
Upgrade to G10B or newer.
9.2 License installation
License installation by command
dir K:\ACS\data\LM
dir C:\Programfiles\AP\ACS\sys
lminst <license file >
stored in the directory K:\ACS\data\LM

a local backup copy of the installed License Key File is stored in
C:\Programfiles\AP\ACS\sys of both the nodes
full path or relative path of the License Key File to be installed.

18 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
type K:\ACS\data\LM\lservrc
Lmlkls
:
LKID
CXC4010767
CXC4010769
CXC4010898
START
yyyy-mm-dd
yyyy-mm-dd
yyyy-mm-dd
END
VALUE DESCRIPTION
NEVER xx
FAK_101_0009_RUS_HW_Activation_20->40W
NEVER xx
FAK_101_0010_RUS_HW_Activation_40->60W
NEVER xx
FAK_101_0008_RUS_HW_Activation_GSM_TRXs
License installation by OSS-RC/SMO
Refer to INSTALLING LISENCES USING SMO
Check license installation
DBTSP: TAB=AXEPARS, NAME=MCTRTRX;

DBTSP: TAB=AXEPARS, NAME=MCTRPWR40;
DBTSP: TAB=AXEPARS, NAME=MCTRPWR60;
The result should be same to the Lmlkls print result.

If the result ist ok. We should install the license again.
command:
lminst <license file >
9.3 RBS Software upgrade
Upgrade to G11B or newer
9.4 RBS configuration DT
Define MO RXOMCTR
RXMSP: MO=RXOTG-<tg>,subord;
RXBLI:MO=RXOTG-<tg>,SUBORD,FORCE;
RXESE:MO=RXOTG-<tg>,SUBORD;
RXMOI: MO=(to create the MCTR object)
Example for 2 RUS with 4 TRX each:

19 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference
RXMOI:MO=RXOMCTR-XXX-0,MAXPWR=48,MAXTRX=4,TXMPWR=AUTO;
RXMOI:MO=RXOMCTR-XXX-1,MAXPWR=48,MAXTRX=4,TXMPWR=AUTO;
//MAXPWR=43 => 20 WATT, MAXPWR=46 => 40 WATT, MAXPWR=48 => 60 WATT, MAXPWR=49 => 80 WATT
We can check the RUS MAXPWR by RXCAP:mo=rxomctr-xx-y command
RXMOI:MO=RXOTRX-XXX-0,MCTRI=0;
Example for 6 RUS with 2 TRX each:
RXMOI:MO=RXOMCTR-XXX-0,MAXTRX=2,maxpwr=48;
RXMOC:MO=RXOTRX-XXX-0 ,MCTRI=0;
RXMOC:MO=RXOTRX-XXX-10,MCTRI=5;
RXMOC:MO=RXOTRX-XXX-11,MCTRI=5;
RXESI:MO= RXOTG-<tg>,SUBORD;
RXBLE:MO= RXOTG-<tg>,SUBORD;
Define cell power parameter
RXMOP:MO=RXOTX-<TG>-0&&-11;
Set the CELL power parameter according to the result of RXMOP:MO=RXOTX
RLCPC:CELL=xxxx,BSPWRB=y,BSPWRT=y;
RBS configuration DT example

20 (20)
No.

Approved
Checked
Date
Rev
2012-02-10
PA1
Reference

RBS6000 MCPA TRX Technical Document PA1

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

RBS6000 MCPA TRX Technical Document PA1

Enviado por

Direitos autorais:

Formatos disponíveis

RBS6000 MCPA TRX Technical

CBC/ND/R/S lizhong zhao