CPRI Sharing (eRAN12.1 - 04)

eRAN
CPRI Sharing Feature Parameter

Description
Issue 04
Date 2017-08-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2017-08-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eRAN
CPRI Sharing Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between eNodeB Types.............................................................................................................................. 4
1.5 Functional Differences Between NB-IoT and FDD....................................................................................................... 4
2 Overview......................................................................................................................................... 5
2.1 Introduction.................................................................................................................................................................... 5
2.2 Benefits........................................................................................................................................................................... 7
3 Application Scenarios...................................................................................................................8
3.1 Examples........................................................................................................................................................................ 8
3.1.1 Multi-Carrier Convergence..........................................................................................................................................8
3.1.1.1 Convergence at an LBBPc........................................................................................................................................8
3.1.1.2 Convergence at an LBBPd/UBBPd/UBBPe/UBBPei............................................................................................ 10
3.1.1.3 Mutual Convergence...............................................................................................................................................12
3.1.2 CPRI Port Extension..................................................................................................................................................13
3.1.2.1 Using the LBBP/UBBPd/UBBPe/UBBPei as the Port Extension Board...............................................................13
3.1.2.2 Using the UBRI as the Port Extension Board.........................................................................................................14
3.2 Restrictions................................................................................................................................................................... 17
4 Related Features...........................................................................................................................22
5 Network Impact........................................................................................................................... 23
6 Engineering Guidelines............................................................................................................. 24
6.1 When to Use................................................................................................................................................................. 24
6.2 Required Information................................................................................................................................................... 24
6.3 Planning........................................................................................................................................................................ 25
6.4 Deployment.................................................................................................................................................................. 25
6.4.1 Process....................................................................................................................................................................... 25
6.4.2 Requirements............................................................................................................................................................. 25
6.4.3 Precautions.................................................................................................................................................................26
6.4.4 Hardware Adjustment................................................................................................................................................27
6.4.5 Data Preparation and Initial Configuration............................................................................................................... 27
Issue 04 (2017-08-30) Huawei Proprietary and Confidential ii

eRAN
CPRI Sharing Feature Parameter Description Contents
6.4.5.1 Data Preparation..................................................................................................................................................... 27

6.4.5.2 Using the CME....................................................................................................................................................... 29
6.4.5.3 Using MML Commands......................................................................................................................................... 29
6.4.6 Activation Observation..............................................................................................................................................30
6.4.7 Reconfiguration......................................................................................................................................................... 31
6.4.8 Deactivation...............................................................................................................................................................31
6.4.8.1 Using the CME....................................................................................................................................................... 31
6.4.8.2 Using MML Commands......................................................................................................................................... 31
6.5 Performance Monitoring...............................................................................................................................................31
6.6 Parameter Optimization................................................................................................................................................ 31
6.7 Possible Issues.............................................................................................................................................................. 31
7 Parameters..................................................................................................................................... 33
8 Counters........................................................................................................................................ 42
9 Glossary......................................................................................................................................... 43
10 Reference Documents............................................................................................................... 44
Issue 04 (2017-08-30) Huawei Proprietary and Confidential iii

eRAN
CPRI Sharing Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes CPRI Sharing, including its technical principles, related features,
network impact, and engineering guidelines.
This feature applies to macro and LampSite eNodeBs.
Any parameters, alarms, counters, or managed objects (MOs) 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.
This document applies to LTE FDD or LTE (NB-IoT). Unless otherwise specified, in this
document, "LTE" refers to LTE FDD or LTE NB-IoT, and "eNodeB" refers to LTE FDD or
LTE NB-IoT eNodeB.
This feature applies to the BBU3900 and BBU3910.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
Issue 04 (2017-08-30) Huawei Proprietary and Confidential 1

eRAN
eRAN12.1 04 (2017-08-30)
This issue includes the following changes.
Change Change Description Parameter Change Affected

Type Entity
Feature Updated models of RF modules None Macro

change supporting CPRI Sharing. For details, eNodeB
see 6.4.2 Requirements.
Editorial None None N/A

change
eRAN12.1 03 (2017-07-29)

Type Entity


change
eRAN12.1 02 (2017-04-26)

Type Entity


change
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
eRAN12.1 Draft B (2017-02-10)


eRAN

Type Entity
Feature Added information about the LTE NB- None Macro

change IoT. For details, see 1.5 Functional eNodeB
Differences Between NB-IoT and
FDD and 3.2 Restrictions.
Added the method of calculating

capacity specifications for different
configurations. For details, see 3.2
Restrictions.

change
eRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of eRAN12.1 introduces the following changes to Issue 04
(2016-11-01) of eRAN11.1.

Type Entity
Feature Added the UBBPei board. For details, None Macro

change see 2.1 Introduction, 3.1.1.2 eNodeB
Convergence at an LBBPd/UBBPd/
UBBPe/UBBPei, 3.1.1.3 Mutual
Convergence, 3.1.2.1 Using the LBBP/
UBBPd/UBBPe/UBBPei as the Port
Extension Board, 3.2 Restrictions, and
6.4.2 Requirements.
Updated models of RF modules

supporting CPRI Sharing. For details,
Deleted the mapping between CPRI None LampSite

Sharing and LOFD-003032 Intra-BBU eNodeBs
Baseband Sharing (2T) in LampSite
scenarios. For details, see 1.1 Scope and
1.4 Differences Between eNodeB
Types.

change

eRAN
1.4 Differences Between eNodeB Types

Function Implementation in Macro and LampSite eNodeBs
Function Difference
CPRI Sharing l Difference in configuration parameters in macro and LampSite

eNodeBs:
For macro eNodeBs, the cell sector equipment needs to be
configured. The corresponding MO is eUCellSectorEqm.
For LampSite eNodeBs, the cell sector equipment group needs
to be configured. The corresponding MO is
EuSectorEqmGroup.
For detailed differences, see 6.4.5.1 Data Preparation and
6.4.5.3 Using MML Commands.
l Descriptions of LBBPc boards are provided only for macro
eNodeBs.
LTE FDD LampSite eNodeBs do not support LBBPc or
UBBPei boards but support only LBBPd, UBBPd, and UBBPe
boards.
Macro eNodeBs support LBBPc, LBBPd, UBBPd, UBBPe,
and UBBPei boards.
1.5 Functional Differences Between NB-IoT and FDD

There are no functional differences between NB-IoT and FDD.

eRAN
CPRI Sharing Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
When LTE baseband processing units and an optional universal baseband radio interface unit
(UBRI) are installed in the same baseband unit (BBU), common public radio interface (CPRI)
ports on a BBP or the UBRI can be shared by the other BBPs. CPRI sharing enables the CPRI
interface function on a BBP to be provided by another board, which increases the flexibility
of fiber connections and reduces the number of optical fibers.
For an eNodeB, the baseband processing board refers to an LBBP, UBBPd, UBBPe, UBBPei,
which provides the baseband processing and CPRI interface functions; the interface board
refers to the UBRIb, which provides the CPRI interface function but not the baseband
processing function.
The following terms are used in CPRI sharing:
l Convergence cell
The baseband processing and baseband interface functions of a convergence cell are
provided by different boards. For example, cell 1 in Figure 2-1 is a convergence cell.
l Non-convergence cell
The baseband processing and baseband interface functions of a non-convergence cell are
provided by a single board. For example, cell 0 in Figure 2-1 is a non-convergence cell.
l Converging board
Baseband processing boards or interface boards directly connected to RF modules are
converging boards.
l Converged board
One or more converged boards (BBPs) are connected to the converging board through
the backplane of the BBU and process services for the convergence cells.
l Mutual convergence
In mutual convergence, two BBPs work as a converging board and also work as a
converged board for each other.
Converged and converging boards provide the baseband processing and CPRI interface
functions for cells, respectively. For example, if BBP A communicates with the RF modules
that serve all or some of the cells (that is, convergence cells) on BBP A through CPRI ports

eRAN
on board B, board B is the converging board and BBP A is the converged board. The
converged board may have cable connections to the RF modules (for example, in CPRI port
extension scenarios) so that the RF modules can serve non-convergence cells on the board.
CPRI sharing described in this document involves only level-1 convergence. That is, cell data
sent to and from a converged board converges on only one converging board through a
backplane channel. A converged board must be a BBP, whereas a converging board can be a
BBP or a UBRI.
Figure 2-1 shows an example of connections for CPRI sharing. In this example, LBBP1
works as the converging board, and LBBP2 works as the converged board.
Figure 2-1 Example of connections for CPRI sharing
Figure 2-2 shows the connections for mutual convergence for CPRI sharing using LBBP 1
and LBBP 2. For cell 0, LBBP 1 works as the converged board, and LBBP 2 works as the
converging board. For cell 1, LBBP 1 works as the converging board, and LBBP 2 works as
the converged board.
In an eNodeB, only an LBBPd/UBBPd/UBBPe/UBBPei supports mutual convergence.
Figure 2-2 Example of connections for mutual convergence in CPRI sharing

eRAN
2.2 Benefits
CPRI sharing offers benefits in the following scenarios:
l Multi-carrier convergence
If only one carrier was initially configured on a multi-carrier RF module or for a CPRI
link, the original optical cables can be reused when an additional BBP needs to be added
for a new carrier. This does not require additional CPRI optical cables, thereby reducing
network construction costs and the service interruption duration.
l CPRI port extension
If the number of CPRI ports on a BBP does not meet service requirements (for example,
when six cells are configured on the BBP and combined RF modules are connected to
the BBP in a star topology), enable this feature so that the CPRI ports on another board
can be used as extension ports for the BBP.

eRAN
CPRI Sharing Feature Parameter Description 3 Application Scenarios
3 Application Scenarios
3.1 Examples
3.1.1 Multi-Carrier Convergence
Multi-carrier convergence allows converged and converging boards to share optical cables for
multi-carrier transmission. In multi-carrier convergence, a multi-carrier RF module is
connected to a CPRI port on a BBP or multiple single-carrier RF modules are cascaded to a
CPRI port on a BBP.
3.1.1.1 Convergence at an LBBPc

When an LBBPc works as a converging board, the converged board can be another LBBPc,
an LBBPd, a UBBPd, or a UBBPe, as shown in Figure 3-1 and Figure 3-2. In this example,
the eNodeB establishes three cells on each BBP. The RF modules shown in Figure 3-1 are
dual-carrier RF modules. The RF modules shown in Figure 3-2 are single-carrier RF
modules.
Figure 3-1 CPRI Sharing networking 1

eRAN
LMPT: LTE main processing and transmission unit
UMPT_L: universal main processing and transmission unit for LTE
Figure 3-2 CPRI Sharing networking 2
An LBBPc working as a converging board poses the following limitations:
l Only one converged board is supported. In addition, the data of no more than three 20
MHz 2T2R cells can be converged through the backplane channel. 2T2R refers to two
transmit channels and two receive channels.
l If an LBBPd/UBBPd/UBBPe works as the converged board, cells on the LBBPd/
UBBPd/UBBPe cannot be enabled with CPRI compression.
l The BBU model must be BBU3900.
Table 3-1 list (lists) the BBU slot assignment principles.
Table 3-1 BBU slot assignment principles (BBU3900, with convergence at an LBBPc)
Converg Conver Slot for Converged Board Slot for Converging

ed Board ging Board
Type Board
Type
LBBPc/ LBBPc Slot 1, 2, or 3 Slot 0

LBBPd/
UBBPd/ Slot 0, 2, or 3 Slot 1
UBBPe Slot 0, 1, 3, 4, or 5 Slot 2
Slot 0, 1, 2, 4, or 5 Slot 3
Slot 2, 3, or 5 Slot 4
Slot 2, 3, or 4 Slot 5

eRAN
3.1.1.2 Convergence at an LBBPd/UBBPd/UBBPe/UBBPei

When an LBBPd, UBBPd, UBBPe, or UBBPei works as a converging board, the converged
boards can be LBBPc boards, LBBPd boards, UBBPd boards, UBBPe boards, UBBPei
boards, or a combination of these boards. The number of converged boards ranges from 1 to
5. Figure 3-3 shows the networking for CPRI sharing with convergence at a BBP board. In
this networking mode, the eNodeB establishes three cells on each BBP, and the six dual-
carrier RF modules can serve a maximum of 12 cells. The cascaded networking is similar to
the networking shown in Figure 3-2 of 3.1.1.1 Convergence at an LBBPc, that is, each dual-
carrier RF module is split into two single-carrier RF modules for cascading.
Figure 3-3 CPRI Sharing networking
If a BBU3910 is used, the BBP must be the UBBPd/UBBPe/UBBPei, and the following BBU
slot assignment rules apply:
l For the LBBPd, UBBPd, UBBPe, and UBBPei boards, if the converging board is
installed in slot x (x can be 0, 1, 2, 3, 4, or 5), the converged boards can be installed in
any slots other than slot x among slots 0 to 5. One converged board occupies one slot,
with no requirements on the slot position.
If a BBU3900 is used, the BBU slot assignment must follow the rules described in Table 3-2.

eRAN
Table 3-2 BBU slot assignment rules (BBU3900, with convergence at an LBBPd, a UBBPd,
or a UBBPe)
Number Converge Converging Slot for Converged Slot for
of d Board Board Type Board Converging Board
Converged Type
Boards
1 LBBPc/ LBBPd/ Slot 1, 2, or 3 Slot 0

LBBPd/ UBBPd/
UBBPd/ UBBPe Slot 0, 2, 3, 4 (non- Slot 1
UBBPe LBBPc), or 5 (non-
LBBPc)
Slot 0, 1, 3, 4, or 5 Slot 2
Slot 0, 1, 2, 4, or 5 Slot 3
Slot 1 (non-LBBPc), Slot 4

2, 3, or 5
Slot 1 (non-LBBPc), Slot 5

2, 3, or 4
2 LBBPc, LBBPd/ l Slots 1 and 2 Slot 0

LBBPd, UBBPd/ l Slots 1 and 3
UBBPd, UBBPe
UBBPe, or l Slots 2 and 3
a Any two of slots 0, 2, Slot 1
combinatio 3, 4 (non-LBBPc), and
n of them 5 (non-LBBPc)
Any two of slots 0, 1, Slot 2

3, 4, and 5

2, 4, and 5
Any two of slots 1 Slot 4

(non-LBBPc), 2, 3,
and 5
Any two of slots 1 Slot 5

(non-LBBPc), 2, 3,
and 4
3 LBBPc, LBBPd/ Slots 1, 2, and 3 Slot 0

LBBPd, UBBPd/
UBBPd, UBBPe Any three of slots 0, 2, Slot 1
UBBPe, or 3, 4 (non-LBBPc), and
a 5 (non-LBBPc)
combinatio Any three of slots 0, 1, Slot 2
n of them 3, 4, and 5
Any three of slots 0, 1, Slot 3

2, 4, and 5

eRAN
Number Converge Converging Slot for Converged Slot for

of d Board Board Type Board Converging Board
Converged Type
Boards
Any three of slots 1 Slot 4

(non-LBBPc), 2, 3,
and 5
Any three of slots 1 Slot 5

(non-LBBPc), 2, 3,
and 4
4 LBBPc, LBBPd/ Not supported Slot 0

LBBPd, UBBPd/
UBBPd, UBBPe Any four of slots 0, 2, Slot 1
UBBPe, or 3, 4 (non-LBBPc), and
a 5 (non-LBBPc)
combinatio Any four of slots 0, 1, Slot 2
n of them 3, 4, and 5
Any four of slots 0, 1, Slot 3

2, 4, and 5
Slot 1 (non-LBBPc) + Slot 4

Slot 2 + Slot 3 + Slot
5
Slot 1 (non-LBBPc) + Slot 5

Slot 2 + Slot 3 + Slot
4
5 LBBPc, LBBPd, Not supported Slot 0

LBBPd, UBBPd, or
UBBPd, UBBPe Slot 0, 2, 3, 4 (non- Slot 1
UBBPe, or LBBPc), or 5 (non-
a LBBPc)
combinatio Slots 0, 1, 3, 4, and 5 Slot 2
n of them
Slots 0, 1, 2, 4, and 5 Slot 3
Not supported Slot 4
Not supported Slot 5
When the LBBPc works as a converged board, only one board can converge data sent to and
from an LBBPc. For details, see 3.2 Restrictions.
3.1.1.3 Mutual Convergence

If all RF modules are connected to one BBP board, cell services are interrupted when the BBP
board becomes faulty. To enhance reliability, mutual convergence is introduced. For mutual
convergence, RF modules are connected to different BBP boards. Figure 3-4 shows an

eRAN
example of connections for mutual convergence involving the LBBPd, UBBPd, or UBBPe. In
this example, six cells are configured on each of the three BBP boards, and each BBP board
supports only one frequency. Frequencies F1, F2, and F3 are configured on the BBP boards in
slots 1, 2, and 3, respectively. There are a total of six CPRI chains between BBP boards and
RF modules. Three RF modules are cascaded in one chain. The three RF modules use
frequencies F1, F2, and F3, respectively.
Figure 3-4 Example of connections for LBBPd/UBBPd/UBBPe+LBBPd/UBBPd/UBBPe

CPRI sharing (with mutual convergence)
In an eNodeB, only an LBBPd/UBBPd/UBBPe/UBBPei supports mutual convergence. For

details about the restrictions in BBU slot assignment in mutual convergence scenarios, see
3.1.1.2 Convergence at an LBBPd/UBBPd/UBBPe/UBBPei.
3.1.2 CPRI Port Extension
3.1.2.1 Using the LBBP/UBBPd/UBBPe/UBBPei as the Port Extension Board

When six or more cells are configured on a BBP and six CPRI ports on the unit are occupied
by three pairs of combined RF modules that serve three cells in a star topology, the RF
modules that serve the other cells cannot be connected to the BBP. To address this situation,
unused CPRI ports on another BBP can be used as extended ports for the original BBP.
Figure 3-5 shows an example in which six cells on frequencies F1 and F3 are configured on
the LBBPd in slot 3. Three cells on frequency F1 are served by three pairs of combined RF
modules and occupy all six CPRI ports on the LBBPd. The RF modules that serve the three

eRAN
cells on frequency F3 are connected to unused CPRI ports 0, 1, and 2 of another LBBPd in
slot 0. The RF modules that serve the three cells on frequency F2 are connected to CPRI ports
3, 4, and 5 of the LBBPd in slot 0.
Figure 3-5 Example of connections for CPRI sharing with an LBBP providing extended
CPRI ports
The BBP that provides the port extension function must be the LBBPd, UBBPd, UBBPe, or
UBBPei board.
For details about the restrictions in BBU slot assignment in mutual convergence scenarios, see
3.1.1.2 Convergence at an LBBPd/UBBPd/UBBPe/UBBPei.
3.1.2.2 Using the UBRI as the Port Extension Board

When six or more cells are configured on a BBP and six CPRI ports on the BBP are occupied
by three pairs of combined RF modules that serve three cells in a star topology, the RF
modules that serve the other cells cannot be connected to the BBP. To address this situation,

eRAN
unused CPRI ports on a UBRI can be used as extended CPRI ports to connect RF modules.
Figure 3-6 shows an example in which:
l Six cells on frequencies F1 and F2 are configured on the LBBPd in slot 3.

l Three cells on frequency F1 are served by three pairs of combined RF modules and fully
occupy six CPRI ports of the LBBPd board.
l Three cells on frequency F2 are connected to RRUs or RFUs through CPRI ports on the
UBRIb.
Figure 3-6 Example of connections for CPRI sharing with a UBRIb providing extended CPRI
ports
Only the UBRIb can be used as the LTE CPRI port extension board. CPRI port specifications
and backplane switching specifications of the UBRIb board are the same as those of the
LBBPd board. For details, see 3.2 Restrictions.

eRAN
For a BBU3910, the slot assignment rules for the UBRIb board functioning as the converging
board are as follows:
If the converging board is installed in slot x (x can be 0, 1, 2, 3, 4, or 5), the converged boards
can be installed in any slots other than slot x among slots 0 to 5. One converged board
occupies one slot, with no requirements on the slot position.
For a BBU3900, the slot assignment rules for the UBRIb board functioning as the converging
board are described in Table 3-3.
Table 3-3 Slot assignment rules (BBU3900, a UBRIb board functioning as the converging
board)
Number Type of Type of Slots for Converged Slot for
of Converge Converging Boards Converging Board
Converged d Board Board
Boards
1 LBBPc/ UBRIb Slot 1, 2, or 3 Slot 0

LBBPd/
UBBPd/ Slot 0, 2, 3, 4 (for non- Slot 1
UBBPe LBBPc), or 5 (for non-
LBBPc)
Slot 0, 1, 3, 4, or 5 Slot 2
Slot 0, 1, 2, 4, or 5 Slot 3
2 LBBPc, UBRIb l Slots 1 and 2 Slot 0

LBBPd, l Slots 1 and 3
UBBPd,
UBBPe, or l Slots 2 and 3
a Any two of slots 0, 2, Slot 1
combinatio 3, 4 (for non-LBBPc),
n of them and 5 (for non-
LBBPc)

3, 4, and 5

2, 4, and 5
3 LBBPc, UBRIb Slots 1, 2, and 3 Slot 0

LBBPd,
UBBPd, Any three of slots 0, 2, Slot 1
UBBPe, or 3, 4 (for non-LBBPc),
a and 5 (for non-
combinatio LBBPc)
n of them Any three of slots 0, 1, Slot 2
3, 4, and 5
Any three of slots 0, 1, Slot 3

2, 4, and 5

eRAN
Number Type of Type of Slots for Converged Slot for

of Converge Converging Boards Converging Board
Converged d Board Board
Boards
4 LBBPc, UBRIb N/A Slot 0

LBBPd,
UBBPd, Any four of slots 0, 2, Slot 1
UBBPe, or 3, 4 (for non-LBBPc),
a and 5 (for non-
combinatio LBBPc)
n of them Any four of slots 0, 1, Slot 2
3, 4, and 5
Any four of slots 0, 1, Slot 3

2, 4, and 5
5 LBBPc, UBRIb N/A Slot 0

LBBPd,
UBBPd, Slot 0, 2, 3, 4 (for non- Slot 1
UBBPe, or LBBPc), or 5 (for non-
a LBBPc)
combinatio Slot 0, 1, 3, 4, or 5 Slot 2
n of them
Slot 0, 1, 2, 4, or 5 Slot 3
3.2 Restrictions
In CPRI sharing scenarios, the cells must be bound to a baseband resource group.
The LBBPc cannot work as a converging board and a converged board simultaneously.
When the LBBPc works as a converging board, the following restrictions are imposed:
l 4T or 4R cells cannot be configured on the LBBPc.

l RF modules can be connected to the LBBPc only in a star, chain, or dual-star topology,
and only one converged board is supported.
l 1T1R/1T2R/2T2R common cells can be configured. When 2T2R common cells are
configured, one 2T2R RRU in the cell is connected to one CPRI port. In addition, a cell
in a sector with RRU/RFU combination is not supported.
When the LBBPc works as a converged board, the following restrictions are imposed:
l 4T or 4R cells cannot be configured on the LBBPc.

l Data on the LBBPc board can be converged to one board and data sent to and received
from multiple boards cannot be converged to the LBBPc.
l A maximum of three 20 MHz 2T2R cells can be configured on the LBBPc. Specifically,
the data of cells with more than two antennas cannot be transmitted over the backplane.
l A cell with RRU/RFU combination cannot be configured on a converged board.

eRAN
If a combination of LBBPc and LBBPc/LBBPd/UBBPd/UBBPe/UBBPei/UBRIb is

configured for CPRI sharing, multi-RRU combination cells whose Cell.MultiRruCellMode is
set to TWO_RRU_COMBINATION are not supported.
l When an LBBPd, a UBBPd, or a UBBPe works as a converging board, RF modules can

be connected to the LBBPd, UBBPd, or UBBPe only in star topology, chain topology,
intra-board cold-backup ring, intra-board load sharing mode, or dual-star topology. The
hot-backup ring topology or inter-board cold-backup ring topology cannot be used.
l When a UBBPei works as a converging board, RF modules can be connected to the
board only in a star or intra-board load sharing topology.
Table 3-4 lists the radio specifications of the backplane channel on a BBU3900 when CPRI
compression is disabled and Table 3-5 lists the radio specifications of the backplane channel
on a BBU3900 when CPRI compression is enabled.
NOTE
l The radio specifications of the backplane channel indicate the maximum specifications when CPRI
sharing is enabled. For example, the specifications "3 x (20 MHz, 2T2R)" indicate that the
backplane channel can transmit data for up to three 2T2R cells with the following bandwidths when
CPRI sharing is enabled: 20 MHz, 15 MHz, 10 MHz, 5 MHz, 3 MHz, and 1.4 MHz.
l The LTE cell capacity conversion formulas are as follows:
One LTE FDD cell with the bandwidth of 10 MHz equals four LTE NB-IoT cells with the bandwidth
of 200 KHz.
One LTE FDD cell with the bandwidth of 20 MHz equals eight LTE NB-IoT cells with the
bandwidth of 200 KHz.
l Capacity specifications for different configurations are calculated as follows:
1. When LTE cells have the same antenna capability and CPRI line rate, the number of cells (3 MHz,
5 MHz, 10 MHz, and 20 MHz) supported is inversely proportional to the bandwidth of LTE cells.
For example, the number of supported 3 MHz cells is twice that of supported 5 MHz cells, and the
number of supported 5 MHz cells is twice that of supported 10 MHz cells.
2. When LTE cells have the same antenna capability and CPRI line rate, the number of supported 1.4
MHz cells is the same as that of supported 3 MHz cells, and the number of supported 15 MHz cells
is the same as that of supported 20 MHz cells.
3. When LTE cells have the same bandwidth, the antenna capability is inversely proportional to the
number of cells for 1T1R, 2T2R, 4T4R. For example, when the cell bandwidth is 20 MHz, the
number of cells supported when the antenna capability is 2T2R is twice that supported when the
antenna capability is 4T4R.
4. When LTE cells have the same bandwidth, the number of cells supported by 1T2R and 2T2R
antennas is the same, and that supported by 2T4R and 4T4R antennas is the same.
Table 3-4 Radio specifications of the backplane channel (BBU3900 with CPRI compression
disabled)
Conver Converg Only One of Converging and Converging and
ging ed Board the Converged Boards Converged Boards
Board Converging in Slots 0 and 1, in Slots 1 and 4 or
and Slots 2 and 3, Slot 4 Slots 1 and 5
Converged and 5, or Slots 1 Respectively
Boards in Slot and 3 Respectively
2 or 3
LBBPd LBBPd/ 4 x (20 MHz, 8 x (20 MHz, 2T2R) 4 x (20 MHz, 2T2R)
UBBPd/ 2T2R)
UBBPe

eRAN
Conver Converg Only One of Converging and Converging and

ging ed Board the Converged Boards Converged Boards
Board Converging in Slots 0 and 1, in Slots 1 and 4 or
and Slots 2 and 3, Slot 4 Slots 1 and 5
Converged and 5, or Slots 1 Respectively
Boards in Slot and 3 Respectively
2 or 3
LBBPc 3 x (20 MHz, 3 x (20 MHz, 2T2R) Not supported

2T2R)
LBBPc LBBPc/ 3 x (20 MHz, 3 x (20 MHz, 2T2R) Not supported

LBBPd/ 2T2R)
UBBPd/
UBBPe
UBRIb LBBPd/ 4 x (20 MHz, 8 x (20 MHz, 2T2R) 4 x (20 MHz, 2T2R)
UBBPd/ 2T2R) NOTE
UBBPe The UBRIb board
cannot be installed in
slot 4 or 5.

2T2R) NOTE
The UBRIb board
cannot be installed in
slot 4 or 5.
UBBPd/ LBBPd 4 x (20 MHz, 8 x (20 MHz, 2T2R) 4 x (20 MHz, 2T2R)
UBBPe 2T2R)
UBBPd/ 5 x (20 MHz, 10 x (20 MHz, 2T2R) 5 x (20 MHz, 2T2R)

UBBPe 2T2R)

2T2R)
enabled)
Conver Converged Only One of the Converging and
ging Board Converging and Converged Boards in
Board Converted Boards in Slots 0 and 1, Slots 2 and
Slot 2 or 3; Converging 3, Slot 4 and 5, or Slots 1
and Converged Boards and 3 Respectively
in Slots 1 and 4 or Slots
1 and 5 Respectively
LBBPd LBBPd Common compression: 5 x Common compression: 10 x

(20 MHz, 2T2R) (20 MHz, 2T2R)

eRAN
Conver Converged Only One of the Converging and

ging Board Converging and Converged Boards in
Board Converted Boards in Slots 0 and 1, Slots 2 and
Slot 2 or 3; Converging 3, Slot 4 and 5, or Slots 1
and Converged Boards and 3 Respectively
in Slots 1 and 4 or Slots
1 and 5 Respectively
LBBPd UBBPd/UBBPe Common compression: 5 x Common compression: 10 x

(20 MHz, 2T2R) (20 MHz, 2T2R)
Enhanced compression: 8 x Enhanced compression: 16 x
(20 MHz, 2T2R) (20 MHz, 2T2R)
UBBPd/ LBBPd Common compression: 5 x Common compression: 10 x

UBBPe (20 MHz, 2T2R) (20 MHz, 2T2R)
UBBPd/ UBBPd/UBBPe Common compression: 10 Common compression: 20 x

UBBPe x (20 MHz, 2T2R) (20 MHz, 2T2R)
Enhanced compression: 15 Enhanced compression: 30 x
x (20 MHz, 2T2R) (20 MHz, 2T2R)
UBRIb LBBPd Common compression: 5 x Common compression: 10 x

(20 MHz, 2T2R) (20 MHz, 2T2R)
NOTE
The UBRIb board cannot be
installed in slot 4 or 5.
UBBPd/UBBPe Common compression: 5 x Common compression: 10 x

(20 MHz, 2T2R) (20 MHz, 2T2R)
Enhanced compression: 8 x Enhanced compression: 16 x
(20 MHz, 2T2R) (20 MHz, 2T2R)
NOTE
The UBRIb board cannot be
installed in slot 4 or 5.
NOTE
In other CPRI compression scenarios, calculate the radio specifications of the backplane channel
according to the configured CPRI compression mode. For details about the calculation method, see
CPRI Compression Feature Parameter Description.
Table 3-6 and Table 3-7 list the radio specifications of the backplane channel on a BBU3910
when CPRI compression is disabled and enabled, respectively.

eRAN
disabled)
Converging Board Converged Radio Specifications of the Backplane
Board Channel
UBBPd/UBBPe/UBBPei UBBPd/ 10 x (20 MHz, 2T2R)

UBBPe/
UBBPei
UBRIb UBBPd/ 8 x (20 MHz, 2T2R)

UBBPe
enabled)
Converging Board Converged Radio Specifications of the Backplane
Board Channel
UBBPd/UBBPe/UBBPei UBBPd/ Common compression: 20 x (20 MHz,

UBBPe/ 2T2R)
UBBPei Enhanced compression: 30 x (20 MHz,
2T2R)
UBRIb UBBPd/ Common compression: 10 x (20 MHz,

UBBPe 2T2R)
Enhanced compression: 16 x (20 MHz,
2T2R)
NOTE
In other CPRI compression scenarios, calculate the radio specifications of the backplane channel
according to the configured CPRI compression mode. For details about the calculation method, see
CPRI Compression Feature Parameter Description.

eRAN
CPRI Sharing Feature Parameter Description 4 Related Features
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

eRAN
CPRI Sharing Feature Parameter Description 5 Network Impact
5 Network Impact
System Capacity
None
Network Performance
Services on converged boards are interrupted when any of the following occurs on the
converging board:
l The converging board restarts under software control.
l The converging board is powered off and then restarted.
l The converging board is removed and then reinstalled.
l CPRI ports are being commissioned.
l CPRI ports are running improperly.

eRAN
CPRI Sharing Feature Parameter Description 6 Engineering Guidelines
6 Engineering Guidelines
6.1 When to Use

You are advised to use CPRI sharing when operators can tolerate the service interruption
described in Network Performance in any of the following scenarios:
l An RF module transition from a single-carrier configuration to a multi-carrier

configuration is required without any change in topology between the BBU and RF
modules so that network construction costs can be reduced.
l Optical fiber cables between the BBU and RF modules should be shared by BBPs so that
no additional optical fiber cables are required and costs can be saved.
l CPRI port extension scenarios exist where cells configured on a BBP require more than
six CPRI ports for data transmission.
Use CPRI sharing in the following scenarios:
l The number of cells (including cells on cascaded RRUs) served by RRUs connecting to
the BBP that provides optical cables exceeds the BBP cell specification.
l The cell BBP is not the board that provides CPRI optical cables. For example, in UL
CoMP scenarios, cells served by the BBP that provides CPRI optical cables are not intra-
frequency cells, and intra-frequency cells need to be configured on the same BBP.
6.2 Required Information

Collect the following information before deploying CPRI sharing:
l Models of the RF modules and BBPs that will be used in CPRI sharing and slot
assignment information
l Cell information, including cell ID and cell sector equipment (for macro eNodeBs)/
sector equipment group (for LampSite eNodeBs)
l Baseband equipment information, including baseband equipment No., slot No. for the
baseband processing unit, and slot No. for the baseband interface board if any
Select topologies based on topology characteristics and network planning requirements.

eRAN
6.3 Planning
RF Planning
None
Network Planning
Deploy the network according to the networking described in 3.1 Examples.
Hardware Planning
Perform hardware planning according to the networking described in 3.1 Examples and based
on 3.2 Restrictions.
6.4 Deployment
6.4.1 Process
None
6.4.2 Requirements
Other Features
See 4 Related Features.
Hardware
The following table lists the hardware requirements.
RF When an LBBPc is working as a converging or converged board, not all

Module RRUs or RFUs support CPRI Sharing. If the Description field in the DSP
BRDMFRINFO command output contains MRRU V1, MRRU V2, V1, or
V2, CPRI Sharing is not supported.
NOTE
RRU3936, RRU3824, and RRU3826 do not support CPRI Sharing.
NOTE
For details about LTE FDD or LTE NB-IoT support for these RF modules, see 3900 Series Base Station
Technical Description.
License
None

eRAN
Other Requirements
l Transmission networking
For details about networking requirements for CPRI sharing, see 3.2 Restrictions.
l Operating environment
When an LBBPc works as a converging board, its maximum CPRI rate and the
maximum number of CPRI links to it are 4.9 Gbit/s and 6, respectively.
When an LBBPd, a UBBPd, a UBBPe, or a UBRIb works as a converging board, its
maximum CPRI rate and the maximum number of CPRI links to it are 9.8 Gbit/s
and 6, respectively. When a UBBPei works as the converging party, it supports two
XCI ports, each with a maximum data rate of 4 x 10.1 Gbit/s.
6.4.3 Precautions
You must configure a converging board and the related converged boards in the same set of
baseband equipment by running the ADD BASEBANDEQM command when creating cells.
The eNodeB selects baseband resources for a cell only from the set of baseband equipment to
which the RF module that serves the cell is connected. This solution prevents the eNodeB
from randomly selecting baseband resources for cells.
The following illustrates the reason for performing this operation.
When an eNodeB establishes a cell preferentially on a BBP, it preferentially chooses one with
optical cable connections to the RF modules that serve that cell. If all the resources on the
BBP are occupied, the eNodeB will establish the cell on a BBP with RF modules that
communicate through a backplane channel. When an LBBPc works as a converging board or
a converged board, only one converging board is supported or only one board can converge
data sent to and from an LBBPc. That is, when an LBBPc is connected to a board using a
backplane channel, the LBBPc cannot be connected to other boards through backplane
channels.
Therefore, if RF modules are connected to CPRI ports on different boards in a BBU, some
cells may not be established because these boards start up not at the same time.
In Figure 6-1, two LBBPc boards, one LBBPd board, and one UBRIb board are configured
on the network and each BBP can be configured with a maximum of three cells. The RF
module in slot 3 is a dual-carrier RF module. According to the network plan, data sent to and
from the LBBPd in slot 2 should be converged by the UBRIb in slot 0, and data sent to and
from the LBBPc in slot 1 should be converged by the LBBPc in slot 3. The LBBPd in slot 2
communicates with the UBRIb in slot 0 for two cells and with the LBBPc in slot 3 for the
other cell. In this situation, the LBBPc in slot 1 cannot communicate with the LBBPc in slot 3
through a backplane channel because the LBBPd board in slot 2 and the LBBPc board in slot
3 already communicate with each other through a backplane channel.

eRAN
Figure 6-1 Baseband resource conflict when multiple converging boards are configured
To resolve this problem, configure the boards in slots 0 and 2 as a baseband resource group
and configure the boards in slots 1 and 3 as another baseband resource group. The eNodeB
selects only the LBBPd in slot 2 for cells served by the RF module in slot 0, and the eNodeB
selects only the baseband processing board in slot 1 or 3 for cells served by the RF module in
slot 3.
In the BBU3900, some slots are not interconnected through the backplane. As shown in
3.1.1.2 Convergence at an LBBPd/UBBPd/UBBPe/UBBPei, slot 0 is not interconnected
with slot 4 or 5 through the backplane. To prevent the eNodeB from selecting a BBP for a cell
through the backplane in such scenarios, bind this cell to its baseband resource group in
advance. Then, the eNodeB will set up the cell only on this BBP. This bind relationship
prevents a cell setup failure due to no backplane interconnection resources.
6.4.4 Hardware Adjustment

N/A
6.4.5 Data Preparation and Initial Configuration
6.4.5.1 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for
a specific feature deployment scenario. There are three types of data sources:
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the
operator

eRAN
l User-defined: parameter values set by users
Required Data
Collect data as follows:
1. Collect the parameter settings for the SECTOR, SECTOREQM, CnOperator,

CnOperatorTa, Cell, and CellOp MOs. For details, see the "Data Preparation" section
in Cell Management Feature Parameter Description.
2. Collect the parameter settings for the BASEBANDEQM MO used to configure
baseband equipment.
Parameter Name Parameter ID Setting Notes
Baseband equipment ID BASEBANDEQM.BASE Configure a converging

BANDEQMID board and the related
converged boards as a set
of baseband resource
group. One BBP can be
configured in only one set
of baseband equipment.
Baseband Equipment Type BASEBANDEQM.BASE -

BANDEQMTYPE
UMTS UL Demodulation BASEBANDEQM.UMTS This parameter is invalid

Mode DEMMODE for LTE networks.
Baseband Equipment BASEBANDEQM.BASE -

Board BANDEQMBOARD
3. (For macro eNodeBs) Collect the parameter settings for the eUCellSectorEqm MO used
to configure sector equipment of a cell.
Local cell ID eUCellSectorEqm.Lo -

calCellId
Sector equipment eUCellSectorEqm.se -

ID ctorEqmId
Baseband eUCellSectorEqm.Ba This parameter specifies the baseband

equipment ID seBandEqmId equipment ID used by a cell. Set this
parameter to the equipment ID
defined in the preceding step.
4. (For LampSite eNodeBs) Collect the parameter settings for the EuSectorEqmGroup
MO used to configure the sector equipment group of a cell.
Local cell ID EuSectorEqmGroup. -

LocalCellId

eRAN
Sector Equipment EuSectorEqmGroup. -

Group ID SectorEqmGroupId
Baseband EuSectorEqmGroup. This parameter specifies the baseband

equipment ID BaseBandEqmId equipment ID used by a cell. Set this
parameter to the equipment ID
defined in the preceding step.
Scenario-specific Data
It is deployed during cell establishment. For details about scenario-specific data preparation
for configuring cells, see the "Data Preparation" section in Cell Management Feature
Parameter Description.
6.4.5.2 Using the CME

For detailed operations, see CME-based Feature Configuration.
6.4.5.3 Using MML Commands

Step 1 On the LMT, run the ADD SECTOR command to add a sector.
Step 2 Run the ADD SECTOREQM command to add a set of sector equipment.
Step 3 Run the ADD BASEBANDEQM command to configure a converging board and a converged
board as a baseband resource group.
The following is an example:
ADD BASEBANDEQM:BASEBANDEQMID=1,BASEBANDEQMTYPE=ULDL,UMTSDEMMODE=NULL,SN1=1,SN2=2;
Step 4 Run the ADD CNOPERATOR command to add a core network (CN) operator.
Step 5 Run the ADD CNOPERATORTA command to add a tracking area for the operator.
Step 6 Run the ADD CELL command to add a cell.
Step 7 Run the ADD CELLOP command to add a cell operator.
Step 8 (For macro eNodeBs) Run the ADD EUCELLSECTOREQM command to bind the cell and
the sector equipment and bind the cell and the baseband resource group.
The following is an example:
ADD EUCELLSECTOREQM:LocalCellId=0,SectorEqmId=1,BaseBandEqmId=1;
Step 9 (For LampSite eNodeBs) Run the ADD EUSECTOREQMGROUP command to bind the
cell and the baseband resource group. The following is an example:
ADD EUSECTOREQMGROUP:LocalCellId=0,SectorEqmGroupId=0,BaseBandEqmId=1;
Step 10 (For LampSite eNodeBs) Run the ADD EUSECTOREQMID2GROUP command to bind
the cell and the sector equipment and bind the cell and the sector equipment group. The
following are examples:
ADD EUSECTOREQMID2GROUP:LocalCellId=0,SectorEqmGroupId=0,SectorEqmId=1;
ADD EUSECTOREQMID2GROUP:LocalCellId=0,SectorEqmGroupId=0,SectorEqmId=2;

eRAN
Step 11 Run the ACT CELL command to activate the cell.
----End
6.4.6 Activation Observation

An eNodeB preferentially establishes a cell on a BBP to which the RF modules that serve the
cell are connected through cables. If all the resources on the BBP are occupied, the eNodeB
establishes the cell on another BBP with which the RF modules communicate through a
backplane channel. In this case, if a cell on a BBP to which the RF modules are not connected
through cables is normal, CPRI sharing has been activated.
The observation procedure is as follows:
Step 1 On the U2000 client or eNodeB LMT, run the DSP CELL command to query the status of a
cell and information about the RF module and BBP that serve the cell. The following figure
shows an example of the command output.
Step 2 Run the LST RRU command to query the chain/ring No. of the RF module serving the cell.
In this step, set the cabinet No., subrack No., and slot No. to the values queried in Step 1. The
following figure shows an example of the command output.
Step 3 Run the LST RRUCHAIN command to query the head cabinet No., head subrack No., and
head slot No. of the RRU chain. In this step, set the RRU chain/ring No. to that queried in
Step 2. The following figure shows an example of the command output.
The command output in Step 1 shows that the cabinet No., subrack No., and slot No. of the
LBBP on which the cell is configured are 0, 0, and 2, respectively. The command output in
Step 3 shows that the cabinet No., subrack No., and slot No. of the RRU chain/ring head are

eRAN
0, 0, and 3, respectively. The baseband processing and CPRI interface functions for the cell
are provided by two different boards. This indicates that CPRI sharing has been activated.
----End
6.4.7 Reconfiguration
This section describes how to change a pair of converged+converging boards for CPRI
sharing from X+Y to X+Z or Z+Y.
Prerequisites:
l The hardware planning and adjustment are complete.
l Baseband resources are sufficient.
Reconfigure the BASENABDEQM MO to adjust information about the baseband resource
group where cells belong.
6.4.8 Deactivation
CPRI sharing takes effect only if the convergence cells are activated. To deactivate CPRI
sharing, deactivate the convergence cells (whose baseband processing boards and CPRI
interface boards are different boards).
6.4.8.1 Using the CME

For detailed operations, see CME-based Feature Configuration.
6.4.8.2 Using MML Commands

Run the DEA CELL command to deactivate the cell.
6.5 Performance Monitoring

N/A
6.6 Parameter Optimization

N/A
6.7 Possible Issues

Fault Description
Cell status is abnormal.
Fault Handling
On the U2000 client, monitor the cell status. If an alarm is generated to indicate a problem
such as cell unavailability or cell capability degradation, clear the alarm by following the
alarm handling suggestions in the alarm reference.

eRAN
The following table lists common alarms related to a cell.
Alarm ID Alarm Name Alarm Type Severity Network

Management
Type
ALM-29240 Cell Fault Major Signaling

Unavailable system
ALM-29243 Cell Capability Fault Major Signaling

Degraded system

eRAN
CPRI Sharing Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates the type of the multi-RRU cell.
uCellMo CELL 03029 / Adaptiv GUI Value Range: SFN(SFN),
de MOD TDLOF e SFN/ CELL_COMBINATION(Cell Combination),
CELL D-00107 SDMA TWO_RRU_COMBINATION(TWO RRU
5 Combination), DIGITAL_COMBINATION(Cell
LST Inter-
CELL LOFD-0 BBP Digital Combination),
70205 / SFN MPRU_AGGREGATION(MPRU_AGGREGATION)
TDLOF Unit: None
D-00200 Inter-
8 BBU Actual Value Range: SFN, CELL_COMBINATION,
SFN TWO_RRU_COMBINATION,
TDLOF DIGITAL_COMBINATION,
D-00109 Inter-
BBP MPRU_AGGREGATION
8
Adaptiv Default Value: SFN(SFN)
TDLOF e SFN/
D-00108 SDMA
0
Inter-
TDLOF BBU
D-00108 Adaptiv
1 e SFN/
TDLOF SDMA
D-00108
2

eRAN

nd
BASEB BASEB ADD None None Meaning: Indicates the number of the baseband
ANDEQ ANDEQ BASEB equipment.
M MID ANDEQ GUI Value Range: 0~23
M
Unit: None
LST
BASEB Actual Value Range: 0~23
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
BASEB BASEB ADD None None Meaning: Indicates the type of baseband equipment.
ANDEQ ANDEQ BASEB GUI Value Range: UL(UL), DL(DL),
M MTYPE ANDEQ ULDL(Combined UL and DL)
M
Unit: None
LST
BASEB Actual Value Range: UL, DL, ULDL
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M

eRAN

nd
BASEB UMTSD ADD None None Meaning: Indicates the demodulation mode of uplink
ANDEQ EMMO BASEB baseband equipment for UMTS mode. When uplink
M DE ANDEQ (or uplink and downlink) baseband equipment is
M added, its demodulation mode must be specified.
LST Different demodulation modes can be specified for
BASEB different sets of uplink (or uplink and downlink)
ANDEQ baseband equipment. This parameter is not used for
M GSM mode, and therefore it is recommended that this
parameter be set to NULL for GSM mode. This
parameter cannot be set to NULL for UMTS mode.
This parameter is not used for LTE mode, and
therefore it is recommended that this parameter be set
to NULL for LTE mode.
GUI Value Range: NULL(NULL), DEM_4_CHAN(4-
Channels Demodulation Mode),
DEM_ECON_4_CHAN(Economical 4-Channels
Demodulation Mode), DEM_2_CHAN(2-Channels
Demodulation Mode), DEM_ADPT_CHAN(Self-
adaption Demodulation Mode)
Unit: None
Actual Value Range: NULL, DEM_4_CHAN,
DEM_ECON_4_CHAN, DEM_2_CHAN,
DEM_ADPT_CHAN
Default Value: None
BASEB BASEB None None None Meaning: Indicates the information about the
ANDEQ ANDEQ baseband processing unit.
M MBOA GUI Value Range: 0~12
RD
Unit: None
Actual Value Range: 0~12
Default Value: None

eRAN

nd
eUCellS LocalCe ADD LOFD-0 Intra- Meaning: Indicates the local ID of a cell. It uniquely
ectorEq llId EUCEL 03032 BBU identifies a cell within an eNodeB.
m LSECT Baseban GUI Value Range: 0~255
OREQ d
M Sharing Unit: None
ADD (2T) Actual Value Range: 0~255

PRBTO Default Value: None
EUCEL
LSECT
OREQ
M
LST
EUCEL
LSECT
OREQ
M
LST
PRBTO
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
RMV
PRBTO
EUCEL
LSECT
OREQ
M
DSP
EURTW
P

eRAN

nd
eUCellS SectorE ADD LOFD-0 Intra- Meaning: Indicates the ID of the sector equipment
ectorEq qmId EUCEL 03032 BBU serving a cell. It uniquely identifies a piece of sector
m LSECT Baseban equipment within an eNodeB.
OREQ d GUI Value Range: 0~65535
M Sharing
(2T) Unit: None
ADD
PRBTO Actual Value Range: 0~65535
EUCEL Default Value: None
LSECT
OREQ
M
DSP
EURTW
P
LST
EUCEL
LSECT
OREQ
M
LST
PRBTO
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
RMV
PRBTO
EUCEL
LSECT
OREQ
M
RST
EUCEL
LRES
DSP
INREC

eRAN

nd
eUCellS BaseBan ADD LOFD-0 Intra- Meaning:

ectorEq dEqmId EUCEL 03032 BBU Indicates the ID of the baseband equipment serving a
m LSECT Baseban cell.
OREQ d
M Sharing When this parameter is set to 255, the baseband
MOD (2T) equipment serving a cell is not specified. In this
EUCEL scenario, the LTE BBPs serving a cell are selected
LSECT among all BBPs in the eNodeB, and the BBPs to
OREQ which the cell's serving RRU is connected are
M preferentially selected.
LST When this parameter is set to a value other than 255,

EUCEL the cell is served only by BBPs in the specified
LSECT baseband equipment, and the BBPs to which the cell's
OREQ serving RRU is connected are preferentially selected.
M GUI Value Range: 0~23,255
Unit: None
Actual Value Range: 0~23,255
Default Value: 255

eRAN

nd
EuSecto LocalCe ADD LOFD-0 Intra- Meaning: Indicates the local cell ID. It uniquely
rEqmGr llId EUSEC 03032 BBU identifies a cell within an eNodeB. This parameter
oup TOREQ Baseban applies only to LTE FDD and LTE TDD.
MGRO d GUI Value Range: 0~255
UP Sharing
(2T) Unit: None
ADD
EUSEC Actual Value Range: 0~255
TOREQ Default Value: None
MID2G
ROUP
LST
EUSEC
TOREQ
MGRO
UP
LST
EUSEC
TOREQ
MID2G
ROUP
MOD
EUSEC
TOREQ
MGRO
UP
RMV
EUSEC
TOREQ
MGRO
UP
RMV
EUSEC
TOREQ
MID2G
ROUP

eRAN

nd
EuSecto SectorE ADD LOFD-0 Intra- Meaning: Indicates the ID of a sector equipment
rEqmGr qmGrou EUSEC 03032 BBU group serving a cell. It uniquely identifies a sector
oup pId TOREQ Baseban equipment group within a cell. This parameter applies
MGRO d only to LTE FDD and LTE TDD.
UP Sharing GUI Value Range: 0~35
ADD (2T)
Unit: None
EUSEC
TOREQ Actual Value Range: 0~35
MID2G Default Value: None
ROUP
LST
EUSEC
TOREQ
MGRO
UP
LST
EUSEC
TOREQ
MID2G
ROUP
MOD
EUSEC
TOREQ
MGRO
UP
RMV
EUSEC
TOREQ
MGRO
UP
RMV
EUSEC
TOREQ
MID2G
ROUP

eRAN

nd
EuSecto BaseBan ADD LOFD-0 Intra- Meaning:

rEqmGr dEqmId EUSEC 03032 BBU Indicates the number of the baseband equipment used
oup TOREQ Baseban by a cell.
MGRO d
UP Sharing When this parameter is set to 255, the baseband
MOD (2T) equipment serving a cell is not specified. In this
EUSEC scenario, any baseband processing unit (BBP) in the
TOREQ eNodeB can be selected to serve a cell, and the BBPs
MGRO to which the cell's serving RRU is connected are
UP preferentially selected.
LST When this parameter is set to a value other than 255,

EUSEC the baseband equipment serving a cell is specified. In
TOREQ this scenario, only BBPs in the specified baseband
MGRO equipment can be selected to serve a cell. This
UP parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: 0~23,255
Unit: None
Actual Value Range: 0~23,255
Default Value: 255

eRAN
CPRI Sharing Feature Parameter Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

eRAN
CPRI Sharing Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
CPRI Sharing Feature Parameter Description 10 Reference Documents
10 Reference Documents
1. Cell Management Feature Parameter Description


CPRI Sharing (eRAN12.1 - 04)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CPRI Sharing (eRAN12.1 - 04)

Загружено:

Авторское право:

Доступные форматы

eRAN

CPRI Sharing Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2017-08-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 04 (2017-08-30) Huawei Proprietary and Confidential ii

6.4.5.1 Data Preparation..................................................................................................................................................... 27

Issue 04 (2017-08-30) Huawei Proprietary and Confidential iii

1 About This Document

This feature applies to macro and LampSite eNodeBs.

This feature applies to the BBU3900 and BBU3910.

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 1

Change Change Description Parameter Change Affected

Feature Updated models of RF modules None Macro

Editorial None None N/A

Change Change Description Parameter Change Affected

Feature Updated models of RF modules None Macro

Editorial None None N/A

Change Change Description Parameter Change Affected

Feature Updated models of RF modules None Macro

Editorial None None N/A

eRAN12.1 Draft B (2017-02-10)

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change Affected

Feature Added information about the LTE NB- None Macro

Added the method of calculating

Editorial None None N/A

eRAN12.1 Draft A (2016-12-30)

Change Change Description Parameter Change Affected

Feature Added the UBBPei board. For details, None Macro

Updated models of RF modules

Deleted the mapping between CPRI None LampSite

Editorial None None N/A

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 3

1.4 Differences Between eNodeB Types

CPRI Sharing l Difference in configuration parameters in macro and LampSite

1.5 Functional Differences Between NB-IoT and FDD

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 4

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 5

Figure 2-1 Example of connections for CPRI sharing

In an eNodeB, only an LBBPd/UBBPd/UBBPe/UBBPei supports mutual convergence.

Figure 2-2 Example of connections for mutual convergence in CPRI sharing

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 6

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 7

3.1.1.1 Convergence at an LBBPc

Figure 3-1 CPRI Sharing networking 1

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 8

LMPT: LTE main processing and transmission unit

UMPT_L: universal main processing and transmission unit for LTE

Figure 3-2 CPRI Sharing networking 2

An LBBPc working as a converging board poses the following limitations:

Table 3-1 list (lists) the BBU slot assignment principles.

Converg Conver Slot for Converged Board Slot for Converging

LBBPc/ LBBPc Slot 1, 2, or 3 Slot 0

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 9

3.1.1.2 Convergence at an LBBPd/UBBPd/UBBPe/UBBPei

Figure 3-3 CPRI Sharing networking

Issue 04 (2017-08-30) Huawei Proprietary and Confidential 10