Professional Documents
Culture Documents
Issue 02
Date 2016-03-31
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
2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 4
9 Engineering Guidelines............................................................................................................. 48
9.1 When to Use CPRI MUX............................................................................................................................................. 49
9.2 Required Information................................................................................................................................................... 49
9.3 Planning........................................................................................................................................................................ 49
9.4 Deployment.................................................................................................................................................................. 50
9.4.1 Requirements............................................................................................................................................................. 50
9.4.2 Data Preparation........................................................................................................................................................ 50
9.4.3 Activation.................................................................................................................................................................. 54
9.4.4 Activation Observation..............................................................................................................................................56
9.4.5 Deactivation...............................................................................................................................................................57
9.4.6 Reconfiguration......................................................................................................................................................... 57
9.5 Performance Monitoring...............................................................................................................................................57
9.6 Parameter Optimization................................................................................................................................................ 57
9.7 Troubleshooting............................................................................................................................................................ 57
9.7.1 Related Alarms.......................................................................................................................................................... 58
9.7.2 MML Commands for Maintenance........................................................................................................................... 58
10 Parameters................................................................................................................................... 61
11 Counters...................................................................................................................................... 62
12 Glossary....................................................................................................................................... 63
13 Reference Documents............................................................................................................... 64
1.1 Scope
This document describes the CPRI MUX feature, including its technical principles, related
features, network impact, and engineering guidelines.
The base stations mentioned in this document refer to DBS3900 base stations in the LampSite
solution.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
GSM, UMTS, and LTE are abbreviated as G, U, and L, respectively.
SRAN11.1 02 (2016-03-31)
This issue includes the following changes.
SRAN11.1 01 (2016-03-07)
This issue includes the following changes.
2 Overview
2.1 Introduction
The CPRI MUX feature enables data transmission of multiple modes (such as UMTS, and
LTE) on a common public radio interface (CPRI) port.
Figure 2-1 shows the working principle of CPRI MUX. A multimode RF unit is connected to
a single-mode or multimode(1) baseband processing unit (BBP)/interface board through CPRI
connection. Another single-mode or multimode(1) BBP/interface board is connected to the
preceding BBP/interface board through the BBU backplane and indirectly communicates with
the multimode RF unit.
The BBP/interface board that is directly connected to the multimode RF unit is called the
converging board, and the corresponding mode is called the converging party. The BBP/
interface board that is indirectly connected to the multimode RF unit is called the converged
board, and the corresponding mode is called the converged party.
In Figure 2-1, mode A is the converged party and mode B is the converging party.
NOTE
In the LampSite solution, a multimode RF unit indicates a combination of the RHUB and pRRU.
2.2 Benefits
This feature provides the following benefits:
l Reduced costs on optical modules and fiber optic cables for newly deployed multimode
base stations: Multiple modes can use a CPRI port to transmit data, reducing the number
of required optical modules and fiber optic cables considerably.
l Low engineering costs and short service interruption duration in refarming scenarios: A
multimode RF unit uses a single CPRI cable at the initial phase. CPRI MUX enables
newly deployed modes to reuse the existing multimode RF unit and CPRI cable in
refarming scenarios.
l Guaranteed coverage for cascaded multimode RF units: CPRI MUX allows multimode
RF units to be cascaded to ensure indoor coverage of different floors or areas. The
LampSite solution supports only RHUB cascading and does not support pRRU
cascading.
This chapter describes BBU boards and RF units that support CPRI MUX.
Table 3-1 BBU3900 boards that support the CPRI MUX feature in a co-MPT multimode base
station and constraints on networking
Mod Converging Slot of the Constraints on Networking
e Board Converging Board
NOTE
If a baseband processing board is named UBBPd/e_A/B/C, "A", "B", "C" indicates the mode whose
baseband resources are configured on this board, baseband resources of different modes are isolated by
"/". For example, UBBPd/e_U/L indicates a UBBPd/e configured with UMTS baseband resources, LTE
baseband resources.
Separate-MPT Scenarios
In separate-MPT scenarios, only UMTS and LTE can serve as the converging party.
SRAN11.0 allows LTE FDD and LTE TDD to use the same MPT board, so that UMTS and
FDD+TDD can be applied to a separate-MPT multimode base station in SRAN11.0.
Table 3-2 lists BBU3900 boards that support the CPRI MUX feature in a separate-MPT
multimode base station and constraints on the slots of the converging and converged boards.
Table 3-2 BBU3900 boards that support the CPRI MUX feature in a separate-MPT
multimode base station and constraints on the slots of the converging and converged boards
Mode Converging Slot of the Converged Slot of the
Board Converging Board Converged Board
Board
Table 3-3 BBU3910 boards that support the CPRI MUX feature in a co-MPT multimode base
station
Mode Converging Board Slot of the Converging Board
UL UBBPd/e_U/L Slot0~Slot5
FT UBBPd/e_L Slot0~Slot5
Separate-MPT Scenarios
In separate-MPT scenarios, only UMTS and LTE can serve as the converging party.
SRAN11.0 allows LTE FDD and LTE TDD to use the same MPT board, so that UMTS and
FDD+TDD can be applied to a separate-MPT multimode base station in SRAN11.0.
Table 3-4 lists BBU3910 boards that support the CPRI MUX feature in a separate-MPT
multimode base station and constraints on the slots of the converging and converged boards.
Table 3-4 BBU3910 boards that support the CPRI MUX feature in a separate-MPT
multimode base station
Mode Converging Slot of the Converged Slot of the
Board Converging Board Converged Board
Board
In SRAN11.0, optical fibers can be connected to slots 2 and 3 on the UMTS+LTE BBU3910
in CPRI MUX. In separate-MPT scenarios, one-to-two converging mode is used and two
converging parties are allowed. The two converging parties must work in the same radio
access technology.
Table 3-5 BBU3910 boards in CPRI MUX that support two-slot optical fiber connections in a
separate-MPT multimode base station
Mode Converging Slot of the Converged Slot of the
Board Converging Board Converged Board
Board
l In the current release, the BBU3910 supports only the UBBPd serving as the baseband
processing unit. The UBBPd can be installed in any slot. In separate-MPT scenarios, you
are advised to install the baseband processing units of the same radio access technology
in slots 2 and 3 so that the fiber optic cables can be connected to the two slots to support
UMTS and LTE in future capacity expansion. In co-MPT scenarios, there are no such
restrictions.
l In UMTS Only scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4,
and 5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and
slot 2. Do not connect the fiber optic cables to other slots to prevent cable adjustment in
future capacity expansion from UMTS Only to UMTS+LTE.
l In LTE Only scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4, and
5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and slot
2. Do not connect the fiber optic cables to other slots to prevent cable adjustment in
future capacity expansion from LTE Only to UMTS+LTE.
l In UMTS+LTE scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4,
and 5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and
slot 2. Do not connect the fiber optic cables to other slots.
This chapter describes CPRI MUX topologies in the LampSite solution for co-MPT
multimode base stations and separate-MPT multimode base stations.
4.1.1 Constraints
The converging and converged parties in the CPRI MUX feature must share one BBU.
l A WBBPf, LBBPd, UBBPd/e_U, UBBPd/e_L can serve as the converging board and
must be configured in slot 2 or 3.
l A WBBPf or UBBPd/e_U must be configured in slot 2 or 3.
l A BBU can connect to a maximum of 24 RHUBs. The RHUB connects to the BBU only
in chain (single-link) topology. A BBU supports multiple RHUB chains. Each CPRI link
supports a maximum of four levels of RHUB cascading.
l When RHUBs and pRRUs work in branch chain (single-link) topology, an RHUB can
connect to a maximum of eight pRRUs and the pRRUs do not support cascading.
l When RHUBs and pRRUs work in branch load sharing topology, an RHUB can connect
to a maximum of four pRRUs and the pRRUs do not support cascading.
Figure 4-1 shows UMTS+LTE CPRI MUX in branch chain (single-link) topology, where
LTE serves as the converging party and UMTS serves as the converged party; the LBBPd/
UBBPd_L serves as the converging board and the WBBPf/UBBPd_U serves as the converged
board.
Figure 4-1 UMTS+LTE CPRI MUX in co-MPT scenarios in branch chain (single-link)
topology
Figure 4-2 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE
serves as the converging party and UMTS serves as the converged party; the LBBPd/
UBBPd_L serves as the converging board and the WBBPf/UBBPd_U serves as the converged
board.
Figure 4-2 UMTS+LTE CPRI MUX in co-MPT scenarios in branch load sharing topology
Figure 4-3 shows LTE FDD+LTE TDD CPRI MUX in branch chain (single-link) topology,
where LTE TDD serves as the converging party and LTE FDD serves as the converged party;
the LBBPd_T/UBBPd_T serves as the converging board and the LBBPd_F/UBBPd_F serves
as the converged board.
Figure 4-3 FDD+TDD CPRI MUX in co-MPT scenarios in branch chain (single-link)
topology
Figure 4-4 shows LTE FDD+LTE TDD CPRI MUX in branch load sharing topology, where
LTE TDD serves as the converging party and LTE FDD serves as the converged party; the
LBBPd_T/UBBPd_T serves as the converging board and the LBBPd_F/UBBPd_F serves as
the converged board.
Figure 4-4 FDD+TDD CPRI MUX in co-MPT scenarios in branch load sharing topology
4.2.1 Constraints
l The converging and converged parties in the CPRI MUX feature must share one BBU.
l One mode serves as either the converging party or the converged party but cannot serves
as both parties. Data can be converged only to one converging board at a time.
l One BBU can provide a maximum of six CPRI ports for data convergence, and these
CPRI ports must be provided by the WBBPf, LBBPd, UBBPd/e_U, or UBBPd/e_L that
is installed in slot 2 or 3.
Figure 4-5 UMTS+LTE CPRI MUX in separate-MPT scenarios in branch chain (single-link)
topology
Figure 4-6 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE
serves as the converging party and UMTS serves as the converged party; the LBBPd/
UBBPd/e_L serves as the converging board and the WBBPf/UBBPd/e_U serves as the
converged board.
Figure 4-6 UMTS+LTE CPRI MUX in separate-MPT scenarios in load sharing topology
Figure 4-7 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch chain (single-link)
topology, where LTE (FDD+TDD) serves as the converging party and UMTS serves as the
converged party; the LBBPd_T/UBBPd/e_T serves as the converging board and the
LBBPd_F/UBBPd/e_F and WBBPf/UBBPd/e_U serve as the converged boards.
Figure 4-7 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch chain
(single-link) topology
Figure 4-8 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch load sharing topology,
where LTE (FDD+TDD) serves as the converging party and UMTS serves as the converged
party; the LBBPd_T/UBBPd/e_T serves as the converging board and the LBBPd_F/
UBBPd/e_F and WBBPf/UBBPd/e_U serve as the converged boards.
Figure 4-8 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch load
sharing topology
This chapter describes CPRI MUX topologies in the LampSite solution for co-MPT
multimode base stations and separate-MPT multimode base stations.
5.1.1 Constraints
The converging and converged parties in the CPRI MUX feature must share one BBU.
In SRAN11.1, fiber optic cables can be connected to 12 CPRI ports on the BBU baseband
processing unit to support the CPRI MUX feature.
Figure 5-1 UMTS+LTE CPRI MUX in co-MPT scenarios in branch chain (single-link)
topology
Figure 5-2 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE
serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L
serves as the converging board and the UBBPd/e_U serves as the converged board.
Figure 5-2 UMTS+LTE CPRI MUX in co-MPT scenarios in branch load sharing topology
Figure 5-3 shows LTE FDD+LTE TDD CPRI MUX in branch chain (single-link) topology,
where LTE TDD serves as the converging party and LTE FDD serves as the converged party;
the UBBPd/e_T serves as the converging board and the UBBPd/e_F serves as the converged
board.
Figure 5-3 FDD+TDD CPRI MUX in co-MPT scenarios in branch chain (single-link)
topology
Figure 5-4 shows LTE FDD+LTE TDD CPRI MUX in branch load sharing topology, where
LTE TDD serves as the converging party and LTE FDD serves as the converged party; the
UBBPd/e_T serves as the converging board and the UBBPd/e_F serves as the converged
board.
Figure 5-4 FDD+TDD CPRI MUX in co-MPT scenarios in branch load sharing topology
5.2.1 Constraints
The converging and converged parties in the CPRI MUX feature must share one BBU.
Figure 5-5 shows UMTS+LTE CPRI MUX in branch chain (single-link) topology, where
LTE serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L
serves as the converging board and the UBBPd/e_U serves as the converged board.
Figure 5-5 UMTS+LTE CPRI MUX in separate-MPT scenarios in branch chain (single-link)
topology
Figure 5-6 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE
serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L
serves as the converging board and the UBBPd/e_U serves as the converged board.
Figure 5-6 UMTS+LTE CPRI MUX in separate-MPT scenarios in load sharing topology
Figure 5-7 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch chain (single-link)
topology, where LTE (FDD+TDD) serves as the converging party and UMTS serves as the
converged party; the UBBPd/e_T serves as the converging board and the UBBPd/e_F and
UBBPd/e_U serve as the converged boards.
Figure 5-7 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch chain
(single-link) topology
Figure 5-8 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch load sharing topology,
where LTE (FDD+TDD) serves as the converging party and UMTS serves as the converged
party; the UBBPd/e_T serves as the converging board and the UBBPd/e_F and UBBPd/e_U
serve as the converged boards.
Figure 5-8 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch load
sharing topology
Table 6-1 Converging capabilities of the converging party in multimode base stations enabled
with CPRI MUX (LTE full compression)
Co-MPT or Baseband Converging Converging Capabilities
Separate- Processing Capabilities of A of A CPRI Link (9.8
MPT Board CPRI Link (4.9 Gbit/s)
Providing Gbit/s)
CPRI Optical
Ports
0*LTE10MHz+UMTS
10*Cell
0*LTE10MHz+UMTS
13*Cell
NOTE
l The converging capabilities of a CPRI link or a board and the CPRI link rate refer to those of the
converging party.
l In the LampSite solution, the CPRI line rate of 4.9 Gbit/s or 9.8 Gbit/s is recommended.
l The capabilities of the converging board cannot exceed the maximum capacity specifications of a
site. For the maximum capacity specifications of a site, see Product Specifications > Technical
Specifications of the BBU3900 > Capacity Specifications in DBS3900 LampSite Technical
Description.
l Converging capabilities in Table 6-1 apply to common cells. For the impact of different features on
cell capacity, see the corresponding feature parameter description.
l Table 6-1 lists the number of UMTS cells supported when the antenna capability is 1T2R.
l Table 6-1 lists the number of LTE 20 MHz cells supported in the 2T2R antenna configuration, 20
MHz cell bandwidth, and 2:1 compression configuration for CPRI bandwidth.
l Table 6-1 lists the number of LTE 10 MHz cells supported in the 2T2R antenna configuration, 10
MHz cell bandwidth, and 3:2 compression configuration for CPRI bandwidth.
l Table 6-1 lists the converging capability of the LBBPd extended board at 9.8 Gbit/s in separate-
MPT mode when the LBBPd board enables the extended mode. CPRI extension mode is enabled
through CPRIEX in the MOD BBP or LST BBP command. CPRI extension mode only affects the
bandwidth specifications of the LBBPd at 9.8 Gbit/s in CPRI compression mode. For details, see
BBU Hardware Description > BBU3900 and BBU3910 Hardware Description > BBU3900 and
BBU3910 Boards > LBBP in 3900 Series Base Station Product Documentation.
l The WBBPf3 board supports CPRI line rates of 4.9 Gbit/s, 6.144 Gbit/s, and 9.8 Gbit/s, but the
RHUB does not support 6.144 Gbit/s. Table 6-1 does not list the CPRI line rate of 6.144 Gbit/s for
the WBBPf3 board because this rate is not applicable when the WBBPf3 board is connected to the
RHUB.
l In separate-MPT scenarios, the LBBPd board supports CPRI extension mode. In CPRI extension
mode, LTE bandwidth compression must be used. For example, a 5 MHz or 10 MHz bandwidth uses
3:2 compression and a 15 MHz or 20 MHz bandwidth uses 2:1 compression for LTE cells.
l In separate-MPT scenarios, when the LBBPd board at a CPRI line rate of 9.8 Gbit/s does not enable
CPRI extension mode, LTE bandwidth compression and non-compression cannot be configured on
the same CPRI link.
l In co-MPT scenarios, the LBBPd board does not support CPRI extension mode.
l LTE in Table 6-1 supports TDD, FDD, and FDD+TDD. Note that LTE TDD 5 MHz does not
support bandwidth compression but LTE FDD 5 MHz supports 3:2 bandwidth compression.
Bandwidth combinations in this table do not support LTE TDD 5 MHz. Table 6-2 lists bandwidth
combinations for LTE TDD 5 MHz.
l "With different LTE bandwidths" in the table indicates that an LTE cell of a smaller bandwidth exists
in addition to the bandwidths specified in a combination. In the combination of 6 x LTE 20 MHz +
UMTS 0 x cell (with different LTE bandwidths), an LTE cell of 10 MHz or 5 MHz exists in addition
to at least one 20 MHz bandwidth specified in the combination. Unless otherwise stated, a
combination supports different LTE bandwidths. LampSite supports only LTE cells of 5 MHz or
higher. Therefore, LTE 5 MHz in the combinations does not include other bandwidths.
Capacity specifications for each mode with different configurations are calculated as follows:
l UMTS
The number of cells supported when the antenna capability is 1T1R is the same as
that supported when the antenna capability is 2T2R.
The antenna capability is inversely proportional to the number of cells. For
example, the number of cells supported when the antenna capability is 1T1R is
twice that supported when the antenna capability is 2T2R.
l LTE
When LTE cells have the same antenna capability and CPRI line rate, the number of
5 MHz or 10 MHz cells supported is inversely proportional to the bandwidth of
cells. For example, the number of cells supported by a 5 MHz cell is twice that
supported by a 10 MHz cell. LTE 5 MHz cells and 10 MHz cells use the same
compression configuration 3:2.
When LTE cells have the same antenna capability and CPRI line rate, 15- and 20-
MHz cells support the same number of cells.
When LTE cells have the same bandwidth, the number of cells supported by 1T2R
and 2T2R antennas is the same.
Table 6-2 Converging capabilities of the converging party in multimode base stations enabled
with CPRI MUX (LTE full non-compression/compression and non-compression)
Co-MPT or Baseband Converging Converging
Separate- Processing Capabilities of A Capabilities of A CPRI
MPT Board CPRI Link (4.9 Gbit/s) Link (9.8 Gbit/s)
Providing
CPRI Optical
Ports
5*LTE5MHz+UMTS
6*Cell
4*LTE5MHz+UMTS
7*Cell
2*LTE5MHz+UMTS
8*Cell
1*LTE5MHz+UMTS
10*Cell
0*LTE5MHz+UMTS
10*Cell
4*LTE5MHz+UMTS
7*Cell
2*LTE5MHz+UMTS
8*Cell
1*LTE5MHz+UMTS
10*Cell
0*LTE5MHz+UMTS
13*Cell
5*LTE5MHz+UMTS 0*LTE10MHz+UMTS
1*Cell 10*Cell
4*LTE5MHz+UMTS 16*LTE5MHz+UMTS
2*Cell 0*Cell
3*LTE5MHz+UMTS 14*LTE5MHz+UMTS
3*Cell 1*Cell
2*LTE5MHz+UMTS 13*LTE5MHz+UMTS
4*Cell 2*Cell
0*LTE5MHz+UMTS 12*LTE5MHz+UMTS
6*Cell 3*Cell
11*LTE5MHz+UMTS
4*Cell
10*LTE5MHz+UMTS
5*Cell
8*LTE5MHz+UMTS
6*Cell
7*LTE5MHz+UMTS
7*Cell
6*LTE5MHz+UMTS
8*Cell
5*LTE5MHz+UMTS
9*Cell
4*LTE5MHz+UMTS
10*Cell
0*LTE5MHz+UMTS
10*Cell
9*LTE5MHz+UMTS
3*Cell
8*LTE5MHz+UMTS
4*Cell
7*LTE5MHz+UMTS
5*Cell
6*LTE5MHz+UMTS
6*Cell
5*LTE5MHz+UMTS
7*Cell
4*LTE5MHz+UMTS
8*Cell
2*LTE5MHz+UMTS
11*Cell
1*LTE5MHz+UMTS
12*Cell
0*LTE5MHz+UMTS
13*Cell
NOTE
l The converging capabilities of a CPRI link or a board and the CPRI link rate refer to those of the
converging party.
l In the LampSite solution, the CPRI line rate of 4.9 Gbit/s or 9.8 Gbit/s is recommended.
l The capabilities of the converging board cannot exceed the maximum capacity specifications of a
site. For the maximum capacity specifications of a site, see Product Specifications > Technical
Specifications of the BBU3900 > Capacity Specifications in DBS3900 LampSite Technical
Description.
l Converging capabilities in Table 6-2 apply to common cells. For the impact of different features on
cell capacity, see the corresponding feature parameter description.
l Table 6-2 lists the number of UMTS cells supported when the antenna capability is 1T2R.
l Table 6-2 lists the number of LTE 20 MHz cells supported when the following configurations are
applied: 2T2R antenna configuration, 20 MHz cell bandwidth, and CPRI bandwidth in non-
compression only mode or mode coexistence of non-compression and 2:1 compression. Unless
otherwise stated for the LTE 20 MHz cells, non-compression coexists with 2:1 compression. If the
CPRI line rate of the WBBPf/LBBPd board is 9.8 Gbit/s, mode coexistence of non-compression and
compression is not supported, no matter whether the base station works in separate-MPT scenarios
or co-MPT scenarios; in this situation, data in the table is in non-compression only mode. The
UBBPd/e board is free from this restriction.
l Table 6-2 lists the number of LTE 10 MHz cells supported when the following configurations are
applied: 2T2R antenna configuration, 10 MHz cell bandwidth, and CPRI bandwidth in non-
compression only mode or mode coexistence of non-compression and 3:2 compression. Unless
otherwise stated for the LTE 10 MHz cells, non-compression coexists with 3:2 compression. If the
CPRI line rate of the WBBPf/LBBPd board is 9.8 Gbit/s, mode coexistence of non-compression and
compression is not supported, no matter whether the base station works in separate-MPT scenarios
or co-MPT scenarios; in this situation, data in the table is in non-compression only mode. The
UBBPd/e board is free from this restriction.
l Table 6-2 lists the number of LTE 5 MHz cells supported when the following configurations are
applied: 2T2R antenna configuration, 5 MHz cell bandwidth, and CPRI bandwidth in non-
compression only mode or mode coexistence of non-compression and 3:2 compression. Unless
otherwise stated for the LTE 5 MHz cells, non-compression coexists with 3:2 compression. If the
CPRI line rate of the WBBPf/LBBPd board is 9.8 Gbit/s, mode coexistence of non-compression and
compression is not supported, no matter whether the base station works in separate-MPT scenarios
or co-MPT scenarios; in this situation, data in the table is in non-compression only mode. The
UBBPd/e board is free from this restriction.
l In non-compression only mode or mode coexistence of non-compression and compression for an
LTE network, the LBBPd board does not support CPRI extension mode.
l LTE in Table 6-2 supports TDD, FDD, and FDD+TDD. Note that LTE TDD 5 MHz does not
support bandwidth compression but LTE FDD 5 MHz supports 3:2 bandwidth compression.
Bandwidth combinations in this table support LTE TDD 5 MHz.
l "With different LTE bandwidths" in the table indicates that an LTE cell of a smaller bandwidth exists
in addition to the bandwidths specified in a combination. In the combination of 6 x LTE 20 MHz +
UMTS 0 x cell (with different LTE bandwidths), an LTE cell of 10 MHz or 5 MHz exists in addition
to the 20 MHz bandwidth specified in the combination. Unless otherwise stated, a combination
supports different LTE bandwidths. LampSite supports only LTE cells of 5 MHz or higher.
Therefore, LTE 5 MHz in the combinations does not include other bandwidths.
Capacity specifications for each mode with different configurations are calculated as follows:
l UMTS
The number of cells supported when the antenna capability is 1T1R is the same as
that supported when the antenna capability is 2T2R.
The antenna capability is inversely proportional to the number of cells. For
example, the number of cells supported when the antenna capability is 1T1R is
twice that supported when the antenna capability is 2T2R.
l LTE
When LTE cells have the same antenna capability and CPRI line rate, the number of
15- and 20-MHz cells supported is the same.
When LTE cells have the same bandwidth, the number of cells supported by 1T2R
and 2T2R antennas is the same.
7 Related Features
Prerequisite Features
None
Impacted Features
None
8 Network Impact
8.3 Reliability
CPRI MUX in Separate-MPT Scenarios
CPRI MUX in separate-MPT scenarios has the following impacts on system reliability:
l Operations or exceptions on the converging party
Circuit switched (CS) and packet switched (PS) services of the converged party will be
interrupted if a CPRI port of the converging party becomes faulty or if any of the
following operations is performed by the converging party:
Software reset or power-off reset on the main control board or the converging board
Blocking, removing and then inserting the main control board or the converging
board
Commissioning a CPRI port on the converging board
In general, the service interruption lasts less than 3 minutes. In the worst case, the service
interruption does not exceed 5 minutes.
l Operations or exceptions on the converged party
Performing software reset on the main control board: The data rate of PS services of
the converging party may be reduced for less than 3s and the longest duration of
rate reduction does not exceed 10s. CS services remain normal in this situation.
Performing power-off reset, inserting and then removing the main control board: CS
and PS services on the converging party will be interrupted for less than 1 minute in
general. In the worst case, the service interruption does not exceed 3 minutes.
NOTE
The service interruption period does not include the time required for manual operations, such as
blocking, removing, and inserting boards.
9 Engineering Guidelines
l Sites in which a single-mode base station is to be evolved into a multimode base station
and the operator requires that the existing topology of fiber optic cables remain
unchanged to reduce engineering costs
l Sites in which a co-MPT dual-mode or multimode base station is to be deployed and the
operator requires that costs of fiber optic cables be reduced
l Sites whose coverage must be ensured through cascaded RF units, such as stadiums,
subways, and high-speed railways
9.3 Planning
RF Planning
N/A
Network Planning
Perform network planning according to 4 CPRI MUX Topologies with BBU3900s Used in
the LampSite Solution.
Hardware Planning
When selecting boards and RF units that are to be used in the CPRI MUX feature, you must
consider the application scenarios and constraints provided in 3 Dependencies on BBU
Boards and RF Units and 4 CPRI MUX Topologies with BBU3900s Used in the
LampSite Solution.
NOTICE
The CPRI link rates of baseband processing units/interface boards, optical modules, and RF
units must match each other and meet the specifications in 6 Specifications of the CPRI
MUX Feature.
9.4 Deployment
9.4.1 Requirements
Hardware
RF units have been installed. Cables between RF units and BBUs have been connected as
required by the CPRI MUX feature. For detailed installation procedures, see the
corresponding Base Station Installation Guide and Site Maintenance Guide of the base
stations.
NOTE
If CPRI MUX is to be deployed in a site where a single-mode base station is to be evolved into a
multimode base station, the hardware configuration must meet the requirements of CPRI MUX.
Otherwise, replace the hardware.
License
None
l The following table describes the parameters related to the RHUB MO for configuring
the RHUB.
Parameter Parameter ID Remarks Data Source
Name
RHUB Chain No. RCN Set this parameter to the Network plan
number of the RHUB (negotiation not
chain onsite. required)
l The following table describes the parameters related to the RRUCHAIN MO for
configuring the pRRU chain.
Parameter Parameter ID Remarks Data Source
Name
l The following table describes the parameters related to the RRU MO for configuring the
pRRU.
Parameter Parameter ID Remarks Data Source
Name
RRU Chain No. RCN Set this parameter to the Network plan
number of the pRRU chain (negotiation not
onsite. required)
Topo Type TT
Cabinet No. CN
Slot No. SN
RRU Type RT
The RHUB/pRRU configuration of the converged party takes effect only after RHUB/pRRUs
of the converging party have been configured.
Before activating CPRI MUX, configure the RRUCHAIN MO on the converged party
(UMTS or LTE). The key parameters are listed in Table 9-2.
NOTE
When CPRI MUX is used in UMTS+LTE co-MPT scenarios where the LBBPd or WBBPf provides 9.8
Gbit/s CPRI optical ports, run the ADD RRUCHAIN command to set the CPRI line rate to 4.9 Gbit/s.
In co-MPT scenarios, the LBBPd board does not support CPRI extension mode.
9.4.3 Activation
Step 2 On the converging party, run the ADD RHUB command to add an RHUB to the RHUB
chain.
Step 3 On the converging party, run the ADD RRUCHAIN command to configure the pRRU chain.
Step 4 On the converging party, run the ADD RRU command to add a pRRU to the pRRU chain.
Step 5 On the converged party, run the ADD RRUCHAIN command for UMTS or LTE to add an
RHUB chain.
Step 6 On the converged party, run the ADD RHUB command to add an RHUB to the RHUB chain.
Step 7 On the converged party, run the ADD RRUCHAIN command for UMTS or LTE to configure
the pRRU chain.
Step 8 On the converged party, run the ADD RRU command for UMTS or LTE to add a pRRU to
the pRRU chain.
----End
NOTE
Data configurations must be the same for RRUs on the converging party and converged party. For
detailed parameter settings, see Table 9-1. When configuring the parameter AT in separate-MPT
scenarios, set the local port for the converging party and the peer port for the converged party. For
details, see Table 9-2.
In separate-MPT scenarios where the CPRI line rate is 9.8 Gbit/s, if the bandwidth compression mode is
changed for a cell on a CPRI link, all cells on the CPRI link must be deactivated, reconfigured, and then
activated.
RRU Position PS
RHUB Name RN
RRU Type RT
RF Unit Working RS
Mode
RRU Position PS
RHUB Name RN
RRU Type RT
RF Unit Working RS
Mode
On the NodeB LMT or U2000, run the DSP BRD command to check whether RF
units function properly.
On the eNodeB LMT or U2000, run the DSP BRD command to check whether RF
units function properly.
Co-MPT scenarios
On the BTS3900 LMT or U2000, run the DSP BRD command to check whether RF
units function properly.
l Check whether the line rate of the converging port is the same as planned.
Separate-MPT scenarios
On the LMT or U2000 of the converging party of a 3900 series base station, run the
DSP CPRIPORT command to check whether the line rate of the converging port is
the same as planned.
Co-MPT scenarios
Run the DSP CPRIPORT command to check whether the line rate of the
converging port is the same as planned.
9.4.5 Deactivation
This feature does not need to be deactivated.
9.4.6 Reconfiguration
Reconfiguration in the UL dual-mode branch chain (single-link) topology and UL dual-mode
branch load sharing topology includes the following operations:
For details about these operations, navigate to Engineering Guidelines (NodeB) >
Deployment > Reconfiguration or Engineering Guidelines (eNodeB) > Deployment >
Reconfiguration in RF Unit and Topology Management Feature Parameter Description.
9.7 Troubleshooting
NOTE
In separate-MPT scenarios, if a UMTS cell fails to be activated and EVT-28200 Iub Common Procedure
Failure Indication is reported, check whether the UMTS+LTE cell configurations exceed the
specifications of a single Ethernet cable. If so, modify the UMTS+LTE cell configurations. If not, run
the BLK CPRIPORT command to block the CPRI_E port and then the UBL CPRIPORT command to
unblock the CPRI_E port.
NOTE
After CPRI MUX is implemented, alarms will be reported if any exceptions occur. Clear the alarms
according to the alarm reference.
10 Parameters
RRUCH AT ADD None None Meaning: Indicates the access type of the board on an
AIN RRUCH RRU chain/ring. When Access Type is set to
AIN LOCALPORT(local port), the BBP connects to the
MOD board on an RRU chain/ring through the CPRI port.
RRUCH When Access Type is set to PEERPORT(peer port),
AIN the local BBP connects to the peer BBP through the
IDX2 port on the backplane and the peer BBP
LST connects to a board on an RRU chain/ring.
RRUCH
AIN GUI Value Range: LOCALPORT(local port),
PEERPORT(peer port)
Unit: None
Actual Value Range: LOCALPORT, PEERPORT
Default Value: LOCALPORT(local port)
11 Counters
12 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
13 Reference Documents