Академический Документы
Профессиональный Документы
Культура Документы
Issue 04
Date 2015-01-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 Introduction....................................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
1.4 Differences Between Base Station Types.......................................................................................................................5
2 Overview.........................................................................................................................................6
2.1 Base Stations and Cabinets.............................................................................................................................................6
2.1.1 Mapping Between Base Station Models and Cabinet Types.......................................................................................6
2.1.2 Cabinet Numbering Rules.........................................................................................................................................10
2.2 Subrack.........................................................................................................................................................................13
2.2.1 Subrack Types...........................................................................................................................................................13
2.2.2 Subrack Numbering Rules.........................................................................................................................................14
2.3 BBU Board Types........................................................................................................................................................17
2.4 USU Board Types.........................................................................................................................................................20
2.5 Typical Cabinet and Subrack Configurations for 3900 Series Base Stations...............................................................21
3 Related Features...........................................................................................................................32
4 Impact on the Network...............................................................................................................33
5 Engineering Guidelines.............................................................................................................34
5.1 Information to Be Collected.........................................................................................................................................34
5.2 Feature Deployment.....................................................................................................................................................34
5.2.1 Deployment Requirements........................................................................................................................................34
5.2.2 Network Planning......................................................................................................................................................34
5.2.3 Data Preparation........................................................................................................................................................34
5.2.4 Feature Activation/Initial Configuration...................................................................................................................44
5.2.5 Activation Observation..............................................................................................................................................47
5.3 Feature Reconfiguration...............................................................................................................................................47
5.3.1 Modifying Cabinet Configuration.............................................................................................................................47
5.3.2 Modifying Subrack Configuration.............................................................................................................................49
5.3.3 Modifying BBU Board Configuration.......................................................................................................................50
5.3.4 Deleting BBU Boards................................................................................................................................................56
5.4 BBU Board Maintenance..............................................................................................................................................58
6 Parameters.....................................................................................................................................60
7 Counters........................................................................................................................................68
8 Glossary.........................................................................................................................................69
9 Reference Documents.................................................................................................................70
1 Introduction
1.1 Scope
This document describes which cabinets and subracks are required for different base station
models and how to configure them. This document also describes how to configure and maintain
boards in a baseband unit (BBU) subrack. This document applies to macro base stations
(BTS3900, BTS3900L, BTS3900A, BTS3900AL, BTS3900C, and DBS3900) and LampSite
base stations.
Any managed objects (MOs), parameters, alarms, or counters described in this document
correspond to the software release delivered with this document. In the event of updates, the
updates will be described in the product documentation delivered with the latest software release.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
SRAN9.0 04 (2015-01-30)
Compared with Issue 03 (2014-08-30) , SRAN9.0 04 (2015-01-30) includes the following
changes.
SRAN9.0 03 (2014-08-30)
Compared with Issue 02 (2014-04-30), SRAN9.0 03 (2014-08-30) includes the following
changes.
SRAN9.0 02 (2014-04-30)
Compared with Issue 01 (2014-04-21), SRAN9.0 02 (2014-04-30) includes the following
changes.
SRAN9.0 01 (2014-04-21)
Compared with Issue Draft C (2014-03-26), SRAN9.0 01 (2014-04-21) have no changes.
Feature Added the BBU3910 as well as configurations Extended the value range of
change and maintenance of modules in a BBU3910, the TYPE parameter.
For details, see section Table 5-3.
2 Overview
l BTS3900
l BTS3900L
l BTS3900A
l BTS3900AL
l DBS3900
l BTS3900C
The 3900 series base stations have the following cabinet types:
l BTS3900
l BTS3900L
l Advanced power module (APM30) series cabinets
l Radio frequency cabinet (RFC)
l Transmission cabinet (TMC) series cabinets
l Outdoor mini box (OMB)
l Battery backup cabinet (BBC)
l BTS3900AL
l TP48600A-H17B1
l BTS3012_SRAN cabinet
l BTS3012II_SRAN cabinet
l BTS3012AE_SRAN cabinet
l VIRTUAL cabinet
For details about the mapping between base station models and cabinet types, see section Table
2-1.
NOTE
VIRTUAL indicates a virtual cabinet. It can be an object in physical entity modeling, for example, a legacy
cabinet or a cabinet type not included in the existing cabinet types. It can also be an object when there is
no physical entity, for example, when a base station is installed in an open rack.
Table 2-1 Mapping between base station models and cabinet type
NOTE
(1) The BTS3900C is a type of distributed base station. The logical names of other cabinets used by the
BTS3900C are configured to the same as those of the DBS3900.
Table 2-4 BTS3900A and DBS3900 (including outdoor APM30H) cabinet numbering rules
2.2 Subrack
Subrack numbers range from 0 to 254. Numbers of entity subracks cannot be changed. Numbers
of extension subracks can be defined by users. Table 2-9, Table 2-10 and Table 2-11 describe
how subracks are numbered.
Table 2-9 Subrack numbering rules for BTS3900 series base stations (including upgraded ones)
RRU 60 to 254 Entity subrack You are advised to comply with the
following rules when configuring
RRU subrack numbers:
l The RRU subrack numbers for the
same project must consistent with
each other.
l If a multimode RRU needs to be
configured in multiple modes, it
must be configured with the same
subrack number. Otherwise an
alarm is generated, indicating the
configuration conflict.
l The RRU subrack numbers are
numbered starting from the lowest
band that the RRUs support. Some
subrack numbers need to be
reserved for capacity expansion.
For example, in a network using
the RRU3926 of 900 MHz,
RRU3929 of 1800 MHz, and
RRU3806 of 2100 MHz, the
subrack numbers are assigned as
follows: 60 to 69 are assigned to
the RRU3926s of 900 MHz, 70 to
79 are assigned to the RRU3929s
of 1800 MHz, and 80 to 89 are
assigned to the RRU3806s of
2100 MHz.
Table 2-10 Upgraded BTS3012 series base station subrack numbering rules
Table 2-13 lists the modules that can be configured in a BBU3910 and the corresponding
configuration rules.
NOTE
BBU board in a BTS supports automatic or manual configuration. If a BBU board supports automatic
configuration, the configuration of the board automatically takes effect when the configuration of the
cabinet housing the board takes effect. If a BBU board supports manual configuration, the configuration
of the board takes effect only after the board is manually configured. In a BBU of a BTS, the GTMU, FAN,
and UPEU support automatic configuration, whereas other boards require manual configuration.
All boards installed in a BBU must be configured.
All GTMU boards in the BBU3910 are GTMUb boards rather than GTMUa boards, which are not supported
by the BBU3910.
The BBU board slot assignment described here only indicates the slots in which BBU boards
can be configured using MML commands or the CME. However, the slots in which a BBU board
can actually be configured vary according to the RAT or RATs supported by the board. For
details, see BBU Hardware Description.
Table 2-15 Typical subrack configuration for 3900 series base stations
EMU/ 40
EMUA
BBU390 0
0/
BBU391
0
EMU/ 40
EMUA
PMU 7
EMU/ 40
EMUA
GATM0 50 subrack is
numbered 12.
GATM1 51
BBU390 0
0/
BBU391
0
PMU 7
EMU/ 40 It is configured in
EMUA No.0 APM30.
GATM0 50
GATM1 51
TMC11H 0 to 1 7 or 8 TCU 8
TMC (1)
PMU 7
FMU 11
EMU/ 40
EMUA
BBU390 0
0/
BBU391
0
PMU 7 None
PMU 7
TCU 8
EMU 40
BBU390 0
0/
BBU391
0
BBU390 0
0/
BBU391
0
BBU390 1
0/
BBU391
0
PMU 7
TCU 8
CCU 15
FMU 11
EMU 40
RFU 4
TMC11H 0 to 1 0 TCU 8
TMC
IBBS700 1 to 2 9 to CCU 15
D/ BBCs 10
IBBS700 TCU 8
T or
IBBS300
D/
IBBS300
T
PMU 7
TCU 8
NOTE
The recommended cabinet number for a transmission cabinet configured with a BBU is 7. If conditions do
not allow, configure the transmission cabinet as cabinet 8.
3 Related Features
N/A
N/A
5 Engineering Guidelines
cabinet 0 is an
extension
cabinet.
The default value
is DEFAULT.
NOTE
A cabinet with a BBU
is defined as a basic
cabinet, and a cabinet
without a BBU is
defined as an
extension cabinet.
Table 5-2 Parameters for adding cabinets to eGBTSs, NodeBs, eNodeBs, or Co-MPT base
stations
Table 5-3 Parameters for adding subracks to eGBTSs, NodeBs, eNodeBs, or Co-MPT base
stations
Table 5-5 Parameters for adding BBU boards to eGBTSs, NodeBs, eNodeBs, or Co-MPT base
stations
Board BT This parameter indicates the logical board type. Set this Netwo
type parameter according to the board in use. rk plan
Value range: UMPT, WMPT, LMPT, UCIU, GTMU,
UTRP, WBBP, LBBP, UBRI, USCU, UBBP, FAN,
UPEU, UEIU
SubBoar SBT This parameter indicates the subboard type in the UTRP. Netwo
d Type Set this parameter according to the subboard used in the rk plan
UTRP.
Value range: UAEC, UIEC, UUAS, UQEC, UEOC, UIEB,
UTRPc
Base BBWS This parameter indicates the modes for which the UBBP Netwo
Band provides baseband processing resources. If the UBBP rk plan
Work provides only CPRI ports for a mode, you do not need to
Standard configure this mode for the UBBP.
Value range: GSM, UMTS, LTE_FDD, LTE_TDD
Only the UBBP supports the BBWS parameter.
CPRI CPRIEX This parameter indicates the CPRI extension switch of a Netwo
Extensio BBP. The transmission capability of a fiber optic cable is rk plan
n improved when this parameter is set to ON. Value Range:
OFF, ON
Only LBBPd supports this parameter.
Cell CCNE This parameter indicates the cell channel number Netwo
Channel extension switch. When the CCNE is set to ON for a BBP, rk plan
Number the number of supported cell channels doubles and the
Extensio capability of distance between channels reduces by half.
n Only the UBBP supports this parameter and it takes effect
only to the UBBPd9. In addition, the UBBPd9 is reset after
this parameter is modified.
The parameter takes effect only in LTE.
NOTE
l If you want to expand capacity by adding WBBPs or increase downlink CE resources by adding boards
to the downlink resource group, set Resource Allocate Rule to CAPAFIRST(Capacity First
Rule).
Board BT This parameter indicates the logical board type. Set this Network
type parameter according to the board in use. plan
Value range: SMPT, UPEU, UEIU, UCXU, FAN, UCIU
Configuring eNodeB Device Data > Configuring Cabinet, Subrack, and BBU data >
Procedure.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Co-MPT Base Stations > Creating a Single Co-MPT
Base Station > Configuring Device Data About the Co-MPT Base Station > Configuring
Cabinet, Subrack, and BBU data > Procedure.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations >Creating Separate-MPT Multimode Base Stations > Creating
a Single Separate-MPT Multimode Base Station > Configuring Device Data About the
Separate-MPT Base Station > Configuring Cabinet and BBU Data > Procedure.
l Configuring base stations in batches
You can save the data of a single base station (including data of the BBU subrack) as a
template. Then, configure multiple base stations in batches by importing this template.
Follow the instructions in the following reference documents and refer to section 6.2.3
"Data Preparation" to complete the initial configuration.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating GBTSs > Creating GBTSs in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating a NodeB > Creating NodeBs in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating an eNodeB > Creating eNodeBs in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Co-MPT Base Stations >Creating Co-MPT Base
Stations in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Separate-MPT Multimode Base Stations > Creating
Separate-MPT Multimode Base Stations in Batches.
l Configuring a single base station using MML commands
– Run the ADD BTSCABINET command to add a GBTS cabinet.
– Run the ADD CABINET command to add an eGBTS, NodeB, or eNodeB cabinet. Run
the ADD SUBRACK command to add an eGBTS, NodeB, or eNodeB subrack.
Creating Base Stations > Creating GBTSs > Creating a Single GBTS > Configuring
GBTS Device Data > Configuring Cabinet and BBU3900 data > Procedure.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating a NodeB > Creating a Single NodeB > Configuring
NodeB Device Data > Configuring Cabinet, Subrack, and BBU data > Procedure.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating an eNodeB > Creating a Single eNodeB >
Configuring eNodeB Device Data > Configuring Cabinet, Subrack, and BBU data >
Procedure.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Co-MPT Base Stations > Creating a Single Co-MPT
Base Station > Configuring Device Data > Configuring Cabinet, Subrack, and BBU
data > Procedure.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Separate-MPT Multimode Base Stations > Creating
a Single Separate-MPT Multimode Base Station > Configuring Device Data >
Configuring Device Data About the Separate-MPT Base Station > Procedure.
l Configuring base stations in batches
You can save the data of a single base station (including data of the BBU subrack) as a
template. Then, configure multiple base stations in batches by importing this template.
Follow the instructions in the following reference documents and refer to section 6.2.3
"Data Preparation" to complete the initial configuration.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating GBTSs > Creating GBTSs in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating a NodeB > Creating NodeBs in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating an eNodeB > Creating eNodeBs in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Co-MPT Base Stations >Creating Co-MPT Base
Stations in Batches.
– For details, see 3900 Series Base Station Initial Configuration Guide and navigate in
the following sequence: 3900 Series Base Station Initial Configuration (CME-based) >
Creating Base Stations > Creating Separate-MPT Multimode Base Stations > Creating
Separate-MPT Multimode Base Stations in Batches.
l Configuring a single base station using MML commands
– Run the ADD BTSBRD command to add boards to a GBTS cabinet.
– Run the ADD BRD command to add boards to an eGBTS, NodeB, or eNodeB cabinet.
NOTE
l You can only change the virtual cabinet to other types of cabinets.
l If a cabinet to be modified contains non-BBU subracks, you cannot change the cabinet type.
l If a cabinet to be modified contains only BBU subracks and can house additional BBU subracks, you
can change the cabinet type. Otherwise, you cannot change the cabinet type.
l If a cabinet to be modified contains no subracks, you can change the cabinet type according to the
onsite cabinet type.
Run the MOD SUBRACK command to modify the parameters related to eGBTSs, NodeBs,
eNodeBs, or Co-MPT base stations, as described in Table 5-9.
l Before modifying the working mode of the LBBP for the existing activated cell, ensure
that the eNodeB supports the modified working mode and that there are sufficient idle
resources (see the cell specifications of the LBBP). Otherwise, the cell cannot be activated.
l LBBPs in FDD mode support 1T1R, 1T2R, 2T2R, 2T4R, and 4T4R FDD cells.
l LBBPs in TDD mode support 1T1R, 2T2R, 4T4R, and 8T8R TDD cells.
l If an RRU chain/ring in load sharing mode is configured on LBBPs and the chain head and
tail belong to different LBBPs, the working mode of the LBBP cannot be modified.
l If the RRU/RFU cannot set up links or work at the maximum line rate after the LBBP is
blocked/unblocked, run the STR CPRILBRNEG command to manually initiate
negotiation.
l After the board is blocked, ALM-26210 Board Blocked will be reported and the board will
not provide services. After the board is unblocked, the alarm will be cleared.
Modifying the Work Mode, Hardware Capacity Enhance or CPRI Extension parameter
interrupts services on the WBBP/LBBP/UBBP. After the WBBP/LBBP/UBBP resets, services
on this board return to normal. Among all baseband processing boards, only the WBBPd supports
the hybrid mode. If an RRU chain is configured on any of optical ports 3 through 5 of an LBBP,
the CPRIEX parameter cannot be set to ON.
Deleting BBU Boards from eGBTSs, NodeBs, eNodeBs, or Co-MPT Base Stations
Run the RMV BRD command to delete a BBU board from eGBTSs, NodeBs, eNodeBs, or Co-
MPT base stations. Table 5-13 describes the related parameters.
l Deleting a board causes a board reset.
l After a board is deleted, services on the board are interrupted.
l If a WBBP/LBBP has been configured with an RRU chain, it cannot be deleted. If you
want to delete the WBBP/LBBP, delete the RRU chain configuration first and then delete
the WBBP/LBBP.
l If a board has been configured with a subboard, the subboard is deleted when the board is
deleted.
Table 5-13 Parameters for deleting BBU boards from eGBTSs, NodeBs, eNodeBs, or Co-MPT
base stations
l In multi-mode scenarios, you can reset common devices at the peer end. Resetting common
devices at the peer end interrupts services on the common devices.
l In multi-mode base stations, resetting the GTMU, UMPT, WMPT, LMPT, and UTRP may
interrupt services on base stations of other modes.
Reset using this command consists of soft reset and power-off reset, which are specified by
corresponding parameters. If power-off reset is selected for a multi-mode base station, boards
in the BBUs of other modes are reset.
Only normal boards support soft reset. Normal boards are those BBU boards excluding the
GTMU and UBRI.
l GTMU
l UBRI
Resetting BBU Boards in Soft Reset Mode in GBTSs, NodeBs, eNodeBs, or Co-MPT
Base Stations
If a board has a fault that cannot be rectified, soft reset is required. Soft reset takes a relatively
short time.
NOTE
After the RST BRD command is executed, the BBU Board Maintenance Link Failure alarm and
the Board Startup event alarm are generated. Run the DSP BRD command to check the values
of AvailabilityStatus and OpState. If the value of AvailabilityStatus is Normal and the value
of OpState is Enabled, the board has started up properly and the fault has been rectified.
NOTE
After the RST BRDPWROFF command is executed, the BBU Board Maintenance Link Failure
alarm and the Board Startup event alarm are generated. Run the DSP BRD command to check
the values of AvailabilityStatus and OpState. If the value of AvailabilityStatus is Normal and
the value of OpState is Enabled, the board has started up properly and the fault has been rectified.
Step 2 Run the DSP BRDMFRINFO command to query the manufacturing information about a board
in eGBTSs, NodeBs, eNodeBs, or Co-MPT base stations.
----End
6 Parameters
TYPE BTS390 ADD None None Meaning: Type of a cabinet. This parameter is set to
0, CABIN VIRTUAL when the type of a cabinet is not within the
BTS390 ET value range of this parameter.
0 MOD GUI Value Range: APM30(APM30), TMC(TMC),
WCDM CABIN BBC(BBC), APM100(APM100), APM200(APM200),
A, ET PS4890(PS4890), OMB(OMB), RFC(RFC), BTS3900
BTS390 (BTS3900), BTS3900L(BTS3900L), BTS3900AL
0 LTE LST
CABIN (BTS3900AL), VIRTUAL(Virtual Cabinet),
ET BTS3900D(BTS3900D), BTS3012_SRAN
(BTS3012_SRAN), BTS3012AE_SRAN
(BTS3012AE_SRAN), BTS3012II_SRAN
(BTS3012II_SRAN), TP48300A(TP48300A),
TP48600A(TP48600A), ILC29(ILC29)
Unit: None
Actual Value Range: APM30, TMC, BBC, APM100,
APM200, PS4890, OMB, RFC, BTS3900, BTS3900L,
BTS3900AL, VIRTUAL, BTS3900D,
BTS3012_SRAN, BTS3012AE_SRAN,
BTS3012II_SRAN, TP48300A, TP48600A, ILC29
Default Value: VIRTUAL(Virtual Cabinet)
DESC BTS390 ADD None None Meaning: Indicates a brief description of the cabinet,
0, CABIN which can be the function, location, and some other
BTS390 ET information of the cabinet.
0 MOD GUI Value Range: 0~79 characters
WCDM CABIN
A, Unit: None
ET
BTS390 Actual Value Range: 0~79 characters
0 LTE LST
CABIN Default Value: NULL(empty string)
ET
CN BTS390 ADD None None Meaning: Indicates the cabinet number of the subrack.
0, SUBRA GUI Value Range: 0~62
BTS390 CK
0 Unit: None
LST
WCDM SUBRA Actual Value Range: 0~62
A, CK Default Value: None
BTS390
0 LTE MOD
SUBRA
CK
RMV
SUBRA
CK
SRN BTS390 ADD None None Meaning: Indicates the number of the subrack.
0, SUBRA GUI Value Range: 0~254
BTS390 CK
0 Unit: None
LST
WCDM SUBRA Actual Value Range: 0~254
A, CK Default Value: None
BTS390
0 LTE MOD
SUBRA
CK
RMV
SUBRA
CK
TYPE BTS390 ADD None None Meaning: Indicates the type of the subrack.
0, SUBRA GUI Value Range: BBU3900(BBU3900 Subrack),
BTS390 CK RFU(RFU Subrack), PMU(PMU Subrack), TCU(TCU
0 MOD Subrack), FMU(FMU Subrack), RRU(RRU Subrack),
WCDM SUBRA RHUB(RHUB Subrack), PRRU(PRRU Subrack),
A, CK EMU(EMU Subrack), GRU(GRU Subrack),
BTS390 BBU3900-1U(BBU3900-1U Subrack), GATM
0 LTE LST
SUBRA (GATM Subrack), PICO(PICO Subrack), CCU(CCU
CK Subrack), AAS(AAS Subrack), BBU3910(BBU3910
Subrack), UNKNOWN(Unknown Subrack)
Unit: None
Actual Value Range: BBU3900, RFU, PMU, TCU,
FMU, RRU, RHUB, PRRU, EMU, GRU,
BBU3900-1U, GATM, PICO, CCU, AAS, BBU3910,
UNKNOWN
Default Value: None
DESC BTS390 ADD None None Meaning: Indicates a brief description of the subrack,
0, SUBRA which can be the function, location, and some other
BTS390 CK information of the subrack.
0 MOD GUI Value Range: 0~79 characters
WCDM SUBRA
A, Unit: None
CK
BTS390 Actual Value Range: 0~79 characters
0 LTE LST
SUBRA Default Value: NULL(empty string)
CK
WM BTS390 ADD None None Meaning: Indicates the working mode of the baseband
0, BRD processing board. There are seven working modes:
BTS390 MOD FDD, TDD, HYBRID, TDD_ENHANCE, TDD_8T8R,
0 BBP TDD_TL and FDD_ATG. The Frequency Division
WCDM Duplex (FDD) mode carries the traditional voice and
A, LST data services. TDD is short for Time Division Duplex.
BTS390 BBP The HYBRID mode is a combination of FDD and IMB
0 LTE modes. In Integrated Mobile Broadcasting (IMB) mode,
the baseband processing board carries the mobile TV
services. The value TDD_ENHANCE indicates the
TDD mode integrated with the BeamForming (BF)
function. The BF function provides the data
transmission service in transmission modes 7 and 8
defined in protocols. For details, see 3GPP TS 36.213.
In TDD_8T8R mode, the baseband processing board
supports TD-LTE single-mode 8T8R. In addition, the
baseband processing board supports the BF function
and CPRI specifications are applied between the BBU
and RRU. In TDD_TL mode, the baseband processing
board supports the TD-LTE&TDS-CDMA dual mode
and the TD-LTE single mode. In addition, the baseband
processing board supports 8T8R BF and 2T2R
Multiple-Input Multiple-Output (MIMO) and CMCC
TD-LTE IR specifications are applied between the BBU
and RRU. In FDD_ATG mode, the baseband processing
board supports communication between Air and
Ground. The FDD_ATG mode applies only to
communication between air and ground.
GUI Value Range: FDD(Frequency Division Duplex),
TDD(Time Division Duplex), HYBRID(HYBRID),
TDD_ENHANCE(Support TDD BF), TDD_8T8R
(TDD_8T8R), TDD_TL(TDD_TL), FDD_ATG
(AirToGround)
Unit: None
Actual Value Range: FDD, TDD, HYBRID,
TDD_ENHANCE, TDD_8T8R, TDD_TL, FDD_ATG
Default Value: FDD(Frequency Division Duplex)
HCE BTS390 ADD None None Meaning: Indicates the hardware capabilities of a
0, BRD baseband processing board. This parameter is controlled
BTS390 MOD by a license control item and is customized for a specific
0 BBP operator. For other operators, this parameter is invalid
WCDM and the hardware capabilities of a baseband processing
A, LST board are consistent with the hardware specifications of
BTS390 BBP this board. This parameter takes effect only in UMTS.
0 LTE GUI Value Range: NORMAL(NORMAL), PARTIAL
(PARTIAL), FULL(FULL)
Unit: None
Actual Value Range: NORMAL, PARTIAL, FULL
Default Value: FULL(FULL)
BBWS BTS390 ADD None None Meaning: Indicates the modes for which the UBBP
0, BRD provides baseband processing resources. If the UBBP
BTS390 MOD provides only CPRI ports for a mode, you do not need
0 BBP to configure this mode for the UBBP.
WCDM GUI Value Range: GSM(GSM), UMTS(UMTS),
A, LST
BBP LTE_FDD(LTE FDD), LTE_TDD(LTE TDD)
BTS390
0 LTE Unit: None
Actual Value Range: GSM, UMTS, LTE_FDD,
LTE_TDD
Default Value: GSM:NO, UMTS:NO, LTE_FDD:NO,
LTE_TDD:NO
CPRIEX BTS390 ADD None None Meaning: Indicates the CPRI extension switch of a
0, BRD BBP. The transmission capability of a fiber optic cable
BTS390 MOD is improved when this parameter is set to ON. Only
0 BBP LBBPd supports this parameter.The BBP is reset after
WCDM the parameter is modified.
A, LST
BBP GUI Value Range: OFF(Off), ON(On)
BTS390
0 LTE Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
BRDSP BTS390 ADD None None Meaning: Indicates the specifications of a board. If the
EC 0, BRD user does not need to forcibly verify the board
BTS390 MOD specifications using the CME, this parameter can be left
0 BBP unspecified. Leaving this parameter unspecified has no
WCDM impact on the base station. If the user needs to forcibly
A, LST verify the board specifications using the CME, this
BTS390 BBP parameter must be set to the hardware type of the board.
0 LTE For example, this parameter must be set to UBBPd1 for
a UBBPd1 board and be set to UBBPd2 for a UBBPd2
board. After this parameter is specified, the CME checks
the configurations of the board based on the value of
this parameter. This ensures that these configurations
are correct before they take effect.
GUI Value Range: 0~15 characters
Unit: None
Actual Value Range: 0~15 characters
Default Value: NULL(empty string)
CCNE BTS390 ADD None None Meaning: Indicates the cell channel number extension
0, BRD switch. When this parameter is set to ON, more cell
BTS390 MOD channels are supported and the distance between
0 BBP channels decreases. Only the UBBP supports this
WCDM parameter and it takes effect only to the UBBPd9. In
A, LST addition, the UBBPd9 is reset after this parameter is
BTS390 BBP modified. The parameter takes effect only in LTE.
0 LTE GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
CN BTS390 DSP None None Meaning: Indicates the cabinet number of the baseband
0, BBPTC processing board.
BTS390 LST GUI Value Range: 0~7
0 BBP
WCDM Unit: None
A, MOD Actual Value Range: 0~7
BTS390 BBP
Default Value: 0
0 LTE
SRN BTS390 DSP None None Meaning: Indicates the subrack number of the baseband
0, BBPTC processing board.
BTS390 LST GUI Value Range: 0~1
0 BBP
WCDM Unit: None
A, MOD Actual Value Range: 0~1
BTS390 BBP
Default Value: 0
0 LTE
SN BTS390 DSP None None Meaning: Indicates the slot number of the baseband
0, BBPTC processing board.
BTS390 LST GUI Value Range: 0~5
0 BBP
WCDM Unit: None
A, MOD Actual Value Range: 0~5
BTS390 BBP
Default Value: None
0 LTE
CN BTS390 DSP None None Meaning: Indicates the cabinet number of the extension
0, BRDRA transmission board.
BTS390 T GUI Value Range: 0~7
0 LST
WCDM Unit: None
UTRP
A, Actual Value Range: 0~7
BTS390 MOD
UTRP Default Value: None
0 LTE
SET
BRDRA
T
SRN BTS390 DSP None None Meaning: Indicates the subrack number of the extension
0, BRDRA transmission board.
BTS390 T GUI Value Range: 0~1
0 LST
WCDM Unit: None
UTRP
A, Actual Value Range: 0~1
BTS390 MOD
UTRP Default Value: None
0 LTE
SET
BRDRA
T
SN BTS390 DSP None None Meaning: Indicates the slot number of the extension
0, BRDRA transmission board.
BTS390 T GUI Value Range: 0~6
0 LST
WCDM Unit: None
UTRP
A, Actual Value Range: 0~6
BTS390 MOD
UTRP Default Value: None
0 LTE
SET
BRDRA
T
SUBTY BTS390 MOD None None Meaning: Indicates the type of the sub-board.
PE 0, UTRP GUI Value Range: NULL(NULL), UAEC(UAEC),
BTS390 LST UIEC(UIEC), UUAS(UUAS), UQEC(UQEC), UEOC
0 UTRP (UEOC), UIEB(UIEB), UTRPc(UTRPc)
WCDM
A, Unit: None
BTS390 Actual Value Range: NULL, UAEC, UIEC, UUAS,
0 LTE UQEC, UEOC, UIEB, UTRPc
Default Value: None
7 Counters
8 Glossary
9 Reference Documents