Académique Documents
Professionnel Documents
Culture Documents
21C&RRH2x60
Document number:
Document issue:
Document status:
Date:
UMT/BTS/DD/044675
01.03 / EN
Approved-Standard
06/08/2014
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
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 AlcatelLucent. 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. Networks assumes no responsibility for errors that might appear in t.All other brand and
product names are trademarks or regist
ered trademarks of their respective holders.
PUBLICATION HISTORY
06/AUGUST/2014
Issue 01.01 / EN, Draft
Creation. Yan Miao
18/SEPTEMBER/2014
Issue 01.02 / EN, Draft
Modification according to the comments. Yan Miao
28/November/2014
Issue 01.03/ EN, Approved-Standard
Document status changed. Yan Miao
01.03 / EN
Approved-Standard
06/08/2014
Page 2 of 24
CONTENTS
INTRODUCTION .............................................................................................................. 6
HW REQUIREMENT .................................................................................................. 13
4.2.2
4.4.1.2
4.4.1.3
4.4.1.3.1
4.4.1.3.2
4.4.1.3.3
4.4.1.3.4
RRH ............................................................................................................. 16
4.4.1.3.5
FPGA ........................................................................................................... 17
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
UMT/BTS/DD/044675
01.03 / EN
Approved-Standard
06/08/2014
Page 3 of 24
LOADER ........................................................................................................ 17
4.4.1.3.7
PLATFORM SOFTWARE....................................................................................... 17
4.4.1.3.8
HARDWARE .................................................................................................... 17
4.6.2
4.6.3
DIMENSIONING ....................................................................................................... 19
4.6.4
CAPACITY............................................................................................................. 19
4.6.5
DEPENDABILITY ...................................................................................................... 19
4.7 SECURITY.............................................................................................. 19
5
INTERFACES .........................................................................................................19
OAM ...................................................................................................................19
6.1.2
6.1.3
ALARMS ............................................................................................................... 20
6.2.2
STATE CHANGES..................................................................................................... 20
COUNTERS............................................................................................................ 20
6.3.2
6.3.3
6.3.4
6.3.5
TRACES ............................................................................................................... 21
01.03 / EN
Approved-Standard
06/08/2014
Page 4 of 24
01.03 / EN
Approved-Standard
06/08/2014
Page 5 of 24
INTRODUCTION
1.1
OBJECT
This document specifies a new capability to adjust the operating mode of an RF asset to optimize
its power consumption when operating below its maximum RF power. The aim of this document is
to describe the software impact for supporting new feature.
1.2
FRS
FSD131825 Power Saving for ASB RRH2x60
FSD131826 Power saving for ASB RRH60-21C
1.3
1.4
01.03 / EN
Approved-Standard
06/08/2014
Page 6 of 24
RELATED DOCUMENTS
2.1
APPLICABLE DOCUMENTS
2.2
[A1]
UMT/SYS/APR/036279
[A2]
UMT/SYS/APR/043851
[A3]
UMT/SYS/APR/0xxxxx
REFERENCE DOCUMENTS
[R1]
UMT/BTS/DD/031734
01.03 / EN
Approved-Standard
06/08/2014
Page 7 of 24
FUNCTION OVERVIEW
3.1
FEATURE OVERVIEW
This feature is expected to adjust the drain voltage of PA(Power Amplifier) to provide minimum
power consumption for the configured RF power supported by the carrier configuration. Rather
than the previous design, this allows the reduction of power consumption for each PA.
Feature 131825 is for ASB RRH2x60 series and feature 131826 is for ASB RRH60-21C, but from RRH
software view , the implement of these two feature mostly are the same, so the solution of these
two feature will be combined together in this document.
3.2
COMPLIANCE MATRIX
Reference of the FSD131826 ed01.05.
R&D compliance
assessment
Requirement id
FN Section(s)
addressing this
requirement
Requirement description
At DR0 or DR1,
(chose the
latest
assessment
available)
Not Compliant
R1
R2
SE Note This is
not so much
BBU OAM
control as RRH
internal
software
functionality.
There is no
direct
control
visibility of
internal setting
to WMS,RMT.
NA
4.4.1.2
Compliant
01.03 / EN
Approved-Standard
06/08/2014
Page 8 of 24
R3
4.4.1.1
Compliant
R9
NA
Compliant
4.2.2
Compliant
R10
Not Compliant
R12
R22
(This is not so
much OAM
control as RRH
internal
software
functionality.
There is no
direct control)
NA
NA
NA
NA
NA
R23
01.03 / EN
Approved-Standard
06/08/2014
Page 9 of 24
Requirement id
R1
FN Section(s)
addressing this
requirement
R&D compliance
assessment
NA
NA
At DR0 or DR1,
(chose the
latest
assessment
available)
Requirement description
R1.1
RRH2x60-21
4.2.1
Compliant
R1.2
RRH2x60-21A
4.2.1
Compliant.
4.2.1
Compliant
R1.3
RRH2x60-850
When connected to iBTS digital units
R1.4
Not Compliant
RRH2x60-850
When connected to OneBTS digital units
R1.5
RRH2x60-1900
When connected to iBTS digital units
(The scope of
this FN is only
iBTS digital
units.)
NA
4.2.1
Compliant
Not Compliant
RRH2x60-1900
R1.6
R1.7
RRH2x60-1900A
When connected to iBTS digital units
(The scope of
this FN is only
iBTS digital
units.)
NA
4.2.1
Compliant
Not Compliant
RRH2x60-1900A
R1.8
R2
(The scope of
this FN is only
iBTS digital
units.)
NA
4.4.1.3
Compliant
01.03 / EN
Approved-Standard
06/08/2014
Page 10 of 24
01.03 / EN
Approved-Standard
06/08/2014
Page 11 of 24
FUNCTIONAL DESCRIPTION
4.1
PRINCIPLE
1) The feature is based on ASB RRH2x60 series and ASB RRH60-21C, which can support the
adjustment of PA drain voltage. According to their HW architecture, The PA has ability to set the
drain voltage via RS485 interface by RRH software.
RRH217_2440
POWER
-48V
+24V
+5.5V
AlertSig
TRX
TX1
Digital Processor
(VSWR Detecting,
LNA Controlling,
Alert reporting etc.)
+28V
+5.5V
FEU
PA
TX1_OUT
PA1_IN
PA1_OUT
TX2_OUT
PA2_IN
PA2_OUT
TX1_IN
CPRI_PRI
ANT1_OUT
RX1_OUT
CPRI_SEC
TX2
VSWR
DETECTOR
FDR1_IN
AISG
FDR
FDR1_OUT
FDR2_OUT
TX2_IN
FDR2_IN
AlertSig
SER_PORT
Digital
ANT2_OUT
RX2_OUT
CtrlSig
OCI(Ethernet)
VSWR
DETECTOR
RX1
RX1_IN
RX2
RX2_IN
RX3
RX3_IN
RX4
RX4_IN
Alert Light
RX3_OUT
ANT3_OUT
RX4_OUT
ANT4_OUT
+5.5V
AlertSig CtrlSig
VSWR Detecting
01.03 / EN
Approved-Standard
06/08/2014
Page 12 of 24
FEU21-W1T2R
CPRI_1
Lightning Protection
RF to digital
LNA
convertor
E
Baseband
EAC_2
Processing
RF to digital
E
(CPRI, CFR,
Power &
Control
-T
DPD, DDC,
DUC, AGC)
Lightning Protection
CPRI_2
LNA
Internal Bias
convertor
Temp
sensor
EAC_1
Aux_EAC1/2
AISG
RETA/ AISG
MCU
Digital to RF
convertor
DC(-48 V)
DC & filter
PA Fb Loop
Clock Circuits
AC option
Power &
Control
TRX21-W4C
PA21-W60
4.2
4.2.1 HW REQUIREMENT
Digital Unit:
D4Uv3
Other cabinet with D2U/D4U sub rack installed (such as 9100MBS) (TBC)
Note: from software point of view, there is no restriction of supporting all the iBTS cabinets.
01.03 / EN
Approved-Standard
06/08/2014
Page 13 of 24
RRH2x60-2100
RRH2x60-850
RRH2x60-1900
RRH2x60-19A
RRH2x60-21A
RRH60-21C
<End: FN-131825&131826-10>
4.2.2 RADIO CONFIGURATION
No impact on the radio configuration, this feature will support all the existing radio
configurations, such as STSRX, STSRX+Y, Daisy Chain, VAM/MIMO and so on.
Note: when feature 176717 RRH2x60-21A support of 2 sectors and feature 165529 RRH2x601900A with 9926 digital available, there is no limitation to extend the configuration.
4.3
4.4
This is a pure RRH feature without any iBTS BBU modification, so the BBU behaviours are the
same as previously.
The RRH2x60 series use a common drain voltage for both PA. The drain voltage and power
consumption for both PAs is managed in parallel and the PAs are not settable independently,
RRH software will choose the highest power consumption and set to both PA.
FUNCTIONALITY DISTRIBUTION
01.03 / EN
Approved-Standard
06/08/2014
Page 14 of 24
BBU
RRH TRX
PA
CARRIERCFG REQ
CARRIERCFG RSP
4.4.1.3.1
CCM OAM
No impact.
4.4.1.3.2
CCM CallP
No impact
01.03 / EN
Approved-Standard
06/08/2014
Page 15 of 24
4.4.1.3.3
Layer 1/2
No impact
4.4.1.3.4
RRH
RRH software should has a rule to select an appropriate drain voltage according to the transmit
power. Most of the RRH types has been deployed in the field for a long time before this feature,
some of these RRH has the direct correspondence between drain voltage and transmit power in
the EEPROM of PA, but some is not. So we need to find an easy way to be backward-compatible
with all the types of RRH mentioned in the FSD.
The correspondence between drain voltage and transmit power will be provided by every vendor
of RRHs, and a drain voltage/transmit power table will be introduced in to RRH software as below:
Product
-vendor
RRH2x60 21
- ASB
RRH2x60 21A 20M
- Gewei
RRH2x60 1900
- ASB
RRH2x60 1900A
- ASB
RRH2x60 850
- ASB
ASB RRH 21C
- ASB
ASB RRH 21C
- Gewei
Drain Voltage
Range
010W
1020W
2030W
3040W
4050W
5060W
>60W
24V 32V,
default = 28V
24
24
26
27
28
29
30
24
24
26
28
30
30
30
24V 32V,
default = 28V
24
26
27
28
29
30
30
24V 32V,
default = 28V
24
26
27
28
29
30
30
24V 32V,
default = 30V
24
24
26
28
28
28
28
25V 32V,
default = 28V
25
25
25
26
27
28
28
25
25
26
28
30
30
30
24V 32V,
default = 30V
25V 32V,
default = 30V
If the PA vendor detected by RRH software is not in this table, then this RRH will not benefit from
this feature, and the drain voltage will always be maximum as default.
The transmit power of each PA is split into 7 steps artificially, every power step will be mapped
to a drain voltage. When total transmit power based on the existing carriers of one PA is
calculated, RRH software will look up the table according to the corresponding PA vendor for a
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
UMT/BTS/DD/044675
01.03 / EN
Approved-Standard
06/08/2014
Page 16 of 24
4.4.1.3.5
FPGA
No impact
4.4.1.3.6
Loader
No impact
4.4.1.3.7
Platform Software
No impact
4.4.1.3.8
Hardware
No impact
<End: FN-131825&131826-20>
4.5
FEATURE INTERWORKING
FRS153028 RRH2x60-21A support of 2 sectors (176717) (RF Shadow)
FRS165529 RRH2X60-1900 with 4 antenna connections
4.6
CCM
PQ3
CEM
PQ2
CEM
PQ3
CEM
DSP
CEM
DSP
CEM
DSP
CEM
ASIC
CEM
ASIC
TRM
01.03 / EN
Approved-Standard
06/08/2014
Page 17 of 24
Core
1
Core
2
OCC
ESIPC
Impact in
no
load
condition
without
cells up (*)
in % CPU
no
no
no
no
no
no
no
no
no
Impact in
no
load
condition
with cells
up (**) in %
CPU
no
no
no
no
no
no
no
no
no
Impact on
NBAP
transaction
processing
in % CPU
no
no
no
no
no
no
no
no
no
(*) no load condition without cells set up : CPU load observed after iBTS init just before cells set
up and without traffic.
(**) no load condition with cells set up : CPU load observed with cells up and without traffic.
Radio Equipment impact template :
RE processor (on RRH/TRDU/MCTRX)
CPU
no
no
(*) no load condition without cells up : CPU load observed after iBTS init just before cells set up
and without traffic.
(**) no load condition with cells set up : CPU load observed with cells up and without traffic.
Type of memory
xCCM
eCCM
no
no
no
no
01.03 / EN
Approved-Standard
06/08/2014
Page 18 of 24
xCEM PQ2
xCEM PQ3
eCEM PQ2
eCEM PQ3
no
no
no
no
no
no
no
no
4.6.3 DIMENSIONING
No impact.
4.6.4 CAPACITY
No impact.
4.6.5 DEPENDABILITY
The startup time or upgrade time will not increase.
No impact for the System availability.
4.7
SECURITY
No impact.
INTERFACES
5.1
UMTS INTERFACES
No impact
5.2
5.3
OAM
01.03 / EN
Approved-Standard
06/08/2014
Page 19 of 24
6.1
CONFIGURATION MANAGEMENT
6.2
FAULT MANAGEMENT
6.2.1 ALARMS
No new alarms added or modified.
6.3
PERFORMANCE MANAGEMENT
6.3.1 COUNTERS
No new counters.
CCM
Callp
TRM/RRH
- PM
- PM
ATM
IP
PCM
SYN
SYNCESSM
CCM
iCEM
CCM
xCEM
CCM
SLOAM-
driver
driver
driver-
driver-
driver
Callp-
Callp
Callp
PQ2
OAM-
CEM
- PM
PM
PM
iCEM
xCEM
SLOAM
PQ2
- PM
iCEM
01.03 / EN
Approved-Standard
06/08/2014
Page 20 of 24
L1
(ITF2)
xCEM
PQ2
PQ3
(ITF3)
(ITF4)
(CPIF)
(ITF2)
Note: If any new interface impact needs to be mentioned, please add the same.
6.3.5 TRACES
No impact
6.4
I&C
No impact
6.5
MISCELLANEOUS
No impact
O&M PROCEDURES
7.1
7.2
7.3
FIELD INTRODUCTION
8.1
HARDWARE CONSTRAINTS
No impact.
01.03 / EN
Approved-Standard
06/08/2014
Page 21 of 24
8.2
MS INTERWORKING
No impact.
TOOLS IMPACTS
No impact.
01.03 / EN
Approved-Standard
06/08/2014
Page 22 of 24
ABBREVIATIONS
BBU
BTS
DxU
Digital 2U or 4U node B
WMS
RRH
PA
Power Amplifier
R&D
RF
Reverse Forward
Rx
Reception
STSR
Sectorised Tx Sectorised Rx
TRM
Transceiver Module
Tx
Transmission
Ul
Uplink
UMTS
VSWR
01.03 / EN
Approved-Standard
06/08/2014
Page 23 of 24
9.2
DEFINITIONS
Class 0: the parameter cannot be modified and a new object instance must be created or
recreated with the requested value, thanks to build process or on line creation command.
Class 2: the object instance (or the parent object instance) must be locked to modify the
parameter and the modification will be taken into account after the object instance (or the
parent object instance) has been unlocked.
Class 3: the parameter can be changed on-line without impact on the service. The new value is
taken into account either immediately or for new calls only.
Operator: the parameter is configurable from the OMC and seen by the operator
Manufacturer: the parameter is configurable from the OMC and only seen by Nortel engineering
teams
END OF DOCUMENT
01.03 / EN
Approved-Standard
06/08/2014
Page 24 of 24