CPRI Sharing(eRAN7.0_06)

8/18/2019 CPRI Sharing(eRAN7.0_06)

http://slidepdf.com/reader/full/cpri-sharingeran7006 1/44

eRAN

CPRI Sharing Feature Parameter

Description

Issue 06

Date 2015-03-30

HUAWEI TECHNOLOGIES CO., LTD.



Copyright © Huawei Technologies Co., Ltd. 2015. 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: [email protected]

Issue 06 (2015-03-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/



Contents

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

1.1 Scope..............................................................................................................................................................................1

1.2 Intended Audience..........................................................................................................................................................1

1.3 Change History...............................................................................................................................................................2

1.4 Differences Between eNodeB Types..............................................................................................................................5

2 Overview.........................................................................................................................................6

2.1 Introduction....................................................................................................................................................................6

2.2 Benefits...........................................................................................................................................................................8

3 Application Scenarios...................................................................................................................9

3.1 Examples........................................................................................................................................................................9

3.1.1 Multi-Carrier Convergence..........................................................................................................................................9

3.1.1.1 Convergence at an LBBPc........................................................................................................................................9

3.1.1.2 Convergence at an LBBPd or a UBBPd.................................................................................................................11

3.1.1.3 Mutual Convergence...............................................................................................................................................14

3.1.2 CPRI Port Extension..................................................................................................................................................15

3.1.2.1 Using the LBBP/UBBPd as the Port Extension Board...........................................................................................15

3.1.2.2 Using the UBRI as the Port Extension Board.........................................................................................................16

3.2 Restrictions...................................................................................................................................................................18

4 Related Features...........................................................................................................................21

4.1 Features R elated to LOFD-003032 Intra-BBU Baseband Sharing (2T)......................................................................21

5 Network Impact...........................................................................................................................225.1 LOFD-003032 Intra-BBU Baseband Sharing (2T)......................................................................................................22

6 Engineering Guidelines.............................................................................................................23

6.1 When to Use CPRI Sharing..........................................................................................................................................23

6.2 Required Information...................................................................................................................................................23

6.3 Planning........................................................................................................................................................................23

6.4 Deployment..................................................................................................................................................................24

6.4.1 Process.......................................................................................................................................................................24

6.4.2 Requirements.............................................................................................................................................................24

6.4.3 Data Preparation........................................................................................................................................................24

eRAN

CPRI Sharing Feature Parameter Description Contents



ii



6.4.4 Precautions.................................................................................................................................................................26

6.4.5 Hardware Adjustment................................................................................................................................................27

6.4.6 Initial Configuration..................................................................................................................................................27

6.4.6.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................27

6.4.6.2 Using the CME to Perform Batch Configuration for Existing eNodeBs...............................................................28

6.4.6.3 Using the CME to Perform Single Configuration..................................................................................................29

6.4.6.4 Using MML Commands.........................................................................................................................................29

6.4.7 Activation Observation..............................................................................................................................................30

6.4.8 Reconfiguration.........................................................................................................................................................31

6.4.9 Deactivation...............................................................................................................................................................31

6.4.9.1 Using the CME to Perform Batch Configuration...................................................................................................31

6.4.9.2 Using the CME to Perform Single Configuration..................................................................................................32

6.4.9.3 Using MML Commands.........................................................................................................................................32

6.5 Performance Monitoring...............................................................................................................................................32

6.6 Parameter Optimization................................................................................................................................................32

6.7 Troubleshooting............................................................................................................................................................32

7 Parameters.....................................................................................................................................34

8 Counters........................................................................................................................................38

9 Glossary.........................................................................................................................................39

10 Reference Documents...............................................................................................................40

eRAN

CPRI Sharing Feature Parameter Description Contents



iii



1 About This Document

1.1 Scope

This document describes CPRI Sharing, including its technical principles, related features,

network impact, and engineering guidelines. CPRI Sharing applies to LampSite and Macro

solutions. For LampSite solutions, LOFD-003032 Intra-BBU Baseband Sharing (2T)

corresponds to this feature.

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.

This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and"eNodeB" refers to LTE FDD eNodeB.

This feature applies to the BBU3900 and BBU3910.

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

LampSite DBS3900

1.2 Intended Audience

This document is intended for personnel who:

l Need to understand the features described herein

l Work with Huawei products

eRAN

CPRI Sharing Feature Parameter Description 1 About This Document



1



1.3 Change History

This section provides information about the changes in different document versions. There aretwo 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.

eRAN7.0 06 (2015-03-30)

This issue includes the following changes.

ChangeType

Change Description ParameterChange

Affected Entity

Feature

change

In LampSite solutions, CPRI sharing is

not under license control. For details, see

6.4.2 Requirements.

None N/A

Added AAU3940 in Hardware

Planning.

None N/A

Editorial

change

Modified descriptions of the 1.4

Differences Between eNodeB Types.

None N/A

eRAN7.0 05 (2014-12-30)


ChangeType


Affected Entity

Feature

change

Added MRFUd, MRFUdw in

Hardware Planning.

None N/A

Editorial

change

None None N/A

eRAN7.0 04 (2014-11-13)


eRAN




2



ChangeType


Affected Entity

Feature

change

Added RRU3959w, RRU3962 and

AAU3920 in Hardware Planning.

None N/A

Editorial

change

l Clarified that CPRI Sharing applies

to LampSite and Macro solutions.

For LampSite solutions,

LOFD-003032 Intra-BBU Baseband

Sharing (2T) corresponds to this

feature. For details, see 1.1 Scope.

l Added the description that cells on a

converged board do not support

RRU/RFU combination when an

LBBPc works as the converged

board. For details, see 3.2

Restrictions.

None N/A

eRAN7.0 03 (2014-09-30)


ChangeType


Affected Entity

Feature

change

Added RRU3952, RRU3953, RRU3959

and RRU3668 in Hardware Planning.

None N/A

Editorial

change

Added the specifications of CPRI

sharing when CPRI compression is

enabled or disabled. For details, see 3.2

Restrictions.

None N/A

eRAN7.0 02 (2014-07-30)


ChangeType


Affected Entity

Feature

change

Added an RRU type (RRU3269) that

supports CPRI Sharing. For details, see

Hardware Planning.

None N/A

eRAN




3



ChangeType


Affected Entity

Editorial

change

Described that the LBBPc cannot work

as a converging board and a converged board simultaneously in 3.2

Restrictions.

None N/A

eRAN7.0 01 (2014-04-26)

This issue does not include any changes.

eRAN7.0 Draft C (2014-03-07)


ChangeType


Affected Entity

Feature

change

None None N/A

Editorial

change

Added 1.4 Differences Between

eNodeB Types, which describes

differences in feature support between

eNodeB types.

None N/A

eRAN7.0 Draft B (2014-02-28)

Compared with Draft A (2014-01-20) of eRAN7.0, Draft B (2014-02-28) of eRAN7.0 includes

the following changes.

Change Type Change Description ParameterChange

Feature change Added the configuration restraint: In CPRI sharing

scenarios, a cell must be bound to a baseband processing

unit. For details, see 3.2 Restrictions and 6.4.6.4 Using

MML Commands.

None

Editorial

change

None None

eRAN7.0 Draft A (2014-01-20)

Compared with Issue 01 (2013-07-30) of eRAN6.0, Draft A (2014-01-20) of eRAN7.0 includes

the following changes.

eRAN




4



Change Type Change Description Parameterchange

Feature change l Added the function descriptions and impacts of the

BBU3910 and UBBPd.l Changed the name of Huawei mobile element

management system from M2000 to U2000.

None

Editorial

change

Revised 2.1 Introduction. None

1.4 Differences Between eNodeB Types

CPRI sharing applies to Macro and LampSite solutions.

eRAN




5



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 ena bles the CPRI

interface function on a BBP to be provided by another board, which increases the flexibility of

fiber connections.

In an eNodeB, an LTE baseband processing unit (LBBP) or a universal baseband processing

unit type d (UBBPd) provides the baseband processing and CPRI interface functions, whereas

a UBRI provides only the CPRI interface function.The following terms are used in CPRI sharing:

l Convergence cell

The baseband processing and CPRI 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 CPRI 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

With CPRI sharing, radio frequency (RF) modules that serve the convergence cells connectto a converging board (a BBP or a UBRI) through cables.

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 on

eRAN

CPRI Sharing Feature Parameter Description 2 Overview



6



board B, board B is the converging board and BBP A is the converged board. The converged

board may be connected to RF modules by cables (for example, in CPRI port extension scenarios)

to enable the RF modules to 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, a LBBP1 works

as the converging board, and an LBBP2 works as the converged board.

Figure 2-1 Example of connections for CPRI sharing

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. For cell 0, LBBP1 works as the converged board, and LBBP2 works as the

converging board. For cell 1, LBBP1 works as the converging board, and LBBP2 works as the

converged board.

eNodeBs support mutual convergence only between LBBPd boards, between UBBPd boards,

and between LBBPd and UBBPd boards.

eRAN




7



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

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 fiber cables can be reused when an

additional BBP needs to be added for services of a new carrier. This reduces the cost of

network construction 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), the CPRI ports on another board can be used as extension ports for the BBP.

eRAN




8



3 Application Scenarios

3.1 Examples

3.1.1 Multi-Carrier Convergence

Multi-carrier convergence allows converged and converging boards to share optical fiber 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, or a UBBPd 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, with each pair

cascaded to a CPRI port on an LBBPc.

eRAN

CPRI Sharing Feature Parameter Description 3 Application Scenarios



9



Figure 3-1 Example 1 of connections for LBBPc/LBBPd/UBBPd+LBBPc CPRI sharing (with

convergence at the latter LBBPc)

LMPT: LTE main processing and transmission unit

UMPT_L: universal main processing and transmission unit for LTE

Figure 3-2 Example 2 of connections for LBBPc/LBBPd/UBBPd+LBBPc CPRI sharing (with

convergence at the latter LBBPc)

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

l Only one converged board is supported. In addition, the data of a maximum of 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 or UBBPd works as the converged board, the LBBPd or UBBPd cannot be

configured to work in CPRI compression mode.

eRAN




10



l The BBU model must be BBU3900.

Table 3-1 lists the BBU slot assignment principles.

Table 3-1 BBU slot assignment principles (with convergence at an LBBPc)

Converg ed BoardType

Converging BoardType

Slot for Converged Board Slot for Converging Board

LBBPc,

LBBPd,

or UBBPd

LBBPc Slot 1, 2, or 3 Slot 0

Slot 0, 2, or 3 Slot 1

Slot 0, 1, 4, or 5 Slot 2 or 3



3.1.1.2 Convergence at an LBBPd or a UBBPd

When an LBBPd or a UBBPd works as a converging board, the converged boards can be LBBPc

boards, LBBPd boards, UBBPd boards, or a combination of these boards. The number of

converged boards can range from 1 to 5. Figure 3-3 shows an example of connections for CPRI

sharing with convergence at an LBBPd or a UBBPd. In this example, the eNodeB establishes

three cells on each BBP, and the six dual-carrier RF modules can serve a maximum of 12 cells.If single-carrier RF modules are used, a pair of RF modules is cascaded to each CPRI port on

the converging board. The connections are similar to those shown in Figure 3-2.

eRAN




11



Figure 3-3 Example of connections for LBBPc/LBBPd/UBBPd+LBBPd/UBBPd CPRI sharing

(with convergence at an LBBPd/UBBPd)

Only one board can converge data sent to and from an LBBPc.

If a BBU3910 is used, the BBPs must be UBBPd boards. In addition, the following BBU slot

assignment rule applies:

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.

Table 3-2 BBU slot assignment rules (with convergence at an LBBPd or a UBBPd)

Number ofConvergedBoards

Converged BoardType

Converging Board Type

Slot for ConvergedBoard

Slot forConverging Board

1 LBBPc,

LBBPd, or

UBBPd

LBBPd or

UBBPd



Slot 0, 1, 4, or 5 Slot 2 or 3

eRAN




12




Converged BoardType






2 LBBPc,

LBBPd,

UBBPd, or

a

combinatio

n of them

LBBPd or

UBBPd

l Slots 1 and 2

l Slots 1 and 3

l Slots 2 and 3

Slot 0

l Slots 0 and 2

l Slots 0 and 3

l Slots 2 and 3

Slot 1

Any two of slots 0, 1, 3,4, and 5

Slot 2

Any two of slots 0, 1, 2,

4, and 5

Slot 3

l Slots 2 and 5

l Slots 3 and 5

l Slots 2 and 3

Slot 4

l Slots 2 and 4

lSlots 3 and 4

l Slots 2 and 3

Slot 5

3 LBBPc,

LBBPd,

UBBPd, or

a

combinatio

n of them

LBBPd or

UBBPd

Slots 1, 2, and 3 Slot 0


Any three of slots 0, 1,

3, 4, and 5

Slot 2

Any three of slots 0, 1,

2, 4, and 5

Slot 3



4 LBBPc,

LBBPd,

UBBPd, or

a

combinatio

n of them

LBBPd or

UBBPd

Not supported Slot 0


Any four of slots 0, 1,

3, 4, and 5

Slot 2

Any four of slots 0, 1,

2, 4, and 5

Slot 3

eRAN




13




Converged BoardType






5 LBBPc,

LBBPd,

UBBPd, or

a

combinatio

n of them

LBBPd or

UBBPd



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

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



3.1.1.3 Mutual Convergence

If all RF modules are connected to one BBP, cell services are interrupted when the BBP fails.

To enhance reliability, mutual convergence is introduced. For mutual convergence, RF modules

are connected to different BBPs. Figure 3-4 shows an example of connections for mutual

convergence. In this example, six cells are configured on each of the three BBPs, and each BBP

supports only one frequency. Cells on frequencies 1, 2, and 3 are configured on the BBPs in

slots 1, 2, and 3, respectively. Six chains of RF modules are connected to a total of six CPRI ports on the BBPs. On each chain, three RF modules are cascaded and operate on different

frequencies (1, 2, and 3).

eRAN




14



Figure 3-4 Example of connections for LBBPd/UBBPd+LBBPd/UBBPd CPRI sharing (with

mutual convergence)

In an eNodeB, only the LBBPd and UBBPd support mutual convergence. The BBU slot

assignment rules for mutual convergence scenarios are the same as those described in 3.1.1.2

Convergence at an LBBPd or a UBBPd.

3.1.2 CPRI Port Extension

3.1.2.1 Using the LBBP/UBBPd 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 extension ports on the original BBP. Figure 3-5 shows an

example in which:

l Six cells on frequencies 1 and 3 are configured on the LBBPd in slot 3.

l Three cells on frequency 1 are served by three pairs of combined RF modules.

l The RF modules that serve the three cells on frequency 3 are connected to unused CPRI

ports 0, 1, and 2 of another LBBPd in slot 0.

eRAN




15



l The RF modules that serve the three cells on frequency 2 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 extension CPRI

ports

The BBP that provides the port extension function must be an LBBPd or a UBBPd.

The BBU slot assignment rules for this scenario are the same as those described in 3.1.1.2

Convergence at an LBBPd or a UBBPd.

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 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, CPRI ports

on a UBRI can be used as extension ports on the BBP. Figure 3-6 shows an example in which:

eRAN




16



l Six cells on frequencies 1 and 2 are configured on the LBBPd in slot 3.

l Three cells on frequency 1 are served by three pairs of combined RF modules.

l The RF modules that serve the three cells on frequency 2 are connected to CPRI ports 0,

1, and 2 of the UBRI in slot 0.

Figure 3-6 Example of connections for CPRI sharing with a UBRIb providing extension CPRI

ports

The UBRI that is used must be a UBRIb.

The CPRI port specifications and backplane-channel radio specifications of the UBRIb are the

same as those of the LBBPd. When a UBRIb works as a converging board, the BBU slot

assignment rules are the same as those described in Table 3-2. For information on the slots where

a UBRIb can be installed, see section "Slot Assignment in the BBU3900" in BBU3900 Hardware

Description.

eRAN




17



3.2 Restrictions

In CPRI sharing scenarios, a cell must be bound to a baseband processing unit.

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 sent to and from the LBBPc can be converged by only one board and multiple boards

cannot be converged by the LBBPc.

l A maximum of three 20 MHz 2T2R cells can be configured on the LBBPc, specifically,

the data volume of cells with more than two antennas cannot be transmitted over the

backplane.

l Cells on a converged board do not support RRU/RFU combination.

When an LBBPd or a UBBPd works as a converging board, RF modules can be connected to

the LBBPd or UBBPd only in a star, chain, intra-board cold-backup ring, intra-board loadsharing, or dual-star topology.

Table 3-3 lists the radio specifications of the backplane channel on a BBU3900 when CPRI

compression is disabled and Table 3-4 lists the radio specifications of the backplane channel on

a BBU3900 when CPRI compression is enabled.

NOTE

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:

l 20 MHz

l 15 MHz

l 10 MHz

l 5 MHz

l 3 MHz

l 1.4 MHz

eRAN




18



Table 3-3 Radio specifications of the backplane channel (BBU3900 with CPRI compression

disabled)

Converging Board

ConvergedBoard

Only One of theConverging andConverged Boards inSlot 2 or 3

Converging andConverged Boards inSlots 0 and 1, Slots 2and 3, or Slot 4 and 5Respectively

LBBPd LBBPd or

UBBPd

4 x (20 MHz, 2T2R) 8 x (20 MHz, 2T2R)

LBBPc 3 x (20 MHz, 2T2R) 3 x (20 MHz, 2T2R)

LBBPc LBBPc,

LBBPd, or

UBBPd

3 x (20 MHz, 2T2R) 3 x (20 MHz, 2T2R)

UBRIb LBBPd or

UBBPd

4 x (20 MHz, 2T2R) 8 x (20 MHz, 2T2R)


UBBPd LBBPd 4 x (20 MHz, 2T2R) 8 x (20 MHz, 2T2R)

UBBPd 5 x (20 MHz, 2T2R) 10 x (20 MHz, 2T2R)



enabled)

Converging Board

ConvergedBoard

Only One of theConverging andConverged Boards inSlot 2 or 3

Converging andConverged Boards inSlots 0 and 1, Slots 2and 3, or Slot 4 and 5Respectively

LBBPd LBBPd or

UBBPd

5*20M 2T2R 10*20M 2T2R

UBBPd LBBPd 5*20M 2T2R 10*20M 2T2R

NOTE

When you configure CPRI compression in other 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-5 lists the radio specifications of the backplane channel on a BBU3910 when CPRI

compression is disabled and Table 3-6 lists the radio specifications of the backplane channel on

a BBU3910 when CPRI compression is enabled.

eRAN




19




disabled)

Converging Board ConvergedBoard

Radio Specifications of the BackplaneChannel

UBBPd UBBPd 10 x (20 MHz, 2T2R)

UBBPd LBBPd 8 x (20 MHz, 2T2R)


enabled)

Converging Board ConvergedBoard

Radio Specifications of the BackplaneChannel

UBBPd LBBPd 10*20M 2T2R

NOTE

When you configure CPRI compression in other 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




20



4 Related Features

4.1 Features Related to LOFD-003032 Intra-BBU BasebandSharing (2T)

Prerequisite Features

None

Mutually Exclusive Features

lRing topologyCPRI sharing cannot be used on CPRI interfaces with a hot-backup ring or inter-board cold-

backup ring topology.

l 2-RRU combination cell

If a combination of LBBPc and LBBPc/LBBPd/UBBPd/UBRI are configured for CPRI

sharing, 2-RRU combination cells are not supported. Cells whose MultiRruCellMode

parameter is set to TWO_RRU_COMBINATION are referred to as 2-RRU combination

cells.

Impacted Features

None

eRAN

CPRI Sharing Feature Parameter Description 4 Related Features



21



5 Network Impact

5.1 LOFD-003032 Intra-BBU Baseband Sharing (2T)

System Capacity

No impact.

Network Performance

The services of 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 The CPRI ports are being commissioned.

l The CPRI ports are abnormal.

eRAN

CPRI Sharing Feature Parameter Description 5 Network Impact



22



6 Engineering Guidelines

6.1 When to Use CPRI Sharing

Use CPRI sharing when operators can tolerate the impact of service interruption described in

Network Performance and have any of the following requirements:

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.

6.2 Required Information

Collect the following information before deploying CPRI sharing:

l Model numbers of the RF modules and BBPs that will be used in CPRI sharing

l Cell IDs, sector equipment for cells, and baseband equipment ID

l BBU slot assignment

Select topologies based on topology characteristics and network planning requirements.

6.3 Planning

RF Planning

None

Network Planning

Connect devices according to the scenarios described in 3.1 Examples.

eRAN

CPRI Sharing Feature Parameter Description 6 Engineering Guidelines



23



Hardware Planning

The LBBP, UBBP, UBRI, and RF modules that support CPRI sharing are subject to application

scenarios of CPRI sharing.

When an LBBPc works as a converging board or a converged board, it supports only the radio

HUB (RHUB) or the following RF modules:

RRU3221, RRU3240, RRU3249, RRU3828, RRU3829, RRU3928, RRU3929, WRFUd,

WRFUe, LRFUe, MRFUd, RRU3229, RRU3841, RRU3642, RRU3962d, RRU3965d,

RRU3965, RRU3963d, RRU3963, RRU3942, RRU3961, RRU3838, RRU3832, RRU3268,

RRU3220E, RRU3269, RRU3260, RRU3936, RRU3938, RRU3939, RRU3262, RRU3952,

RRU3953 RRU3959, RRU3962, AAU3920, AAU3940, RRU3959w, and RRU3668 .

6.4 Deployment

6.4.1 Process

None

6.4.2 Requirements

Operating Environment

l When an LBBPc works as a converging board, its CPRI rate and the number of CPRI chains

to it cannot exceed 4.9 Gbit/s and six, respectively.

l When an LBBPd, a UBBPd, or a UBRIb works as a converging board, its CPRI rate and

the number of CPRI chains to it cannot exceed 9.8 Gbit/s and six, respectively.

Transmission Networking

For details about networking requirements for CPRI sharing, see 3.2 Restrictions.

License

CPRI sharing is not under license control.

6.4.3 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

l User-defined: parameter values set by users

eRAN




24



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 inCell Management Feature Parameter Description.

2. Collect the parameter settings for a BASEBANDEQM MO used to configure a set of

baseband equipment.

Parameter Name Parameter ID Data Source Setting Notes

Baseband

Equipment ID

BASEBANDEQM

.

BASEBANDEQM

ID

Network plan

(negotiation not

required)

Configure a

converging board

and the related

converged boards

as a set of baseband

equipment. One

BBP can be

configured in only

one set of baseband

equipment.

Baseband

Equipment Type

BASEBANDEQM

.

BASEBANDEQM

TYPE

Network plan

(negotiation not

required)

N/A

UMTS UL

Demodulation

Mode

BASEBANDEQM

.

UMTSDEMMOD

E

Network plan

(negotiation not

required)

This parameter is

invalid for LTE

networks.

Baseband

Equipment Board

BASEBANDEQM

.

BASEBANDEQM

BOARD

Network plan

(negotiation not

required)

N/A

3. Collect the parameter settings for an EUCELLSECTOREQM MO used to configure a

set of sector equipment for a cell.

ParameterName

Parameter ID Data Source Setting Notes

Local cell ID EUCELLSECT

OREQM.

LocalCellId

Network plan

(negotiation

not required)

N/A

Sector

equipment ID

EUCELLSECT

OREQM.

sectorEqmId

Network plan

(negotiation

not required)

N/A

eRAN




25



ParameterName

Parameter ID Data Source Setting Notes

Baseband

equipment ID

EUCELLSECT

OREQM. BaseBandEqmId

Network plan

(negotiationnot required)

Set this parameter to the equipment

ID defined in the preceding step (inthis section).

Scenario-specific Data

CPRI sharing does not require scenario-specific data preparation. 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.4 PrecautionsYou 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 within 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 provides additional detail as to why:

An eNodeB establishes a cell preferentially 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 addition, when an LBBPc works as a converging board, it supports onlyone converged board. When an LBBPc works as a converged board, data sent to and from the

LBBPc can be converged by only one board. (For details, see 3.2 Restrictions.) That is, when

an LBBPc is connected to a board through 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 after these boards start up in sequence. Figure 6-1 shows an example of

an error condition. In this example, the BBU is equipped with two LBBPc boards, one LBBPd

board, and one UBRIb board. The UBRIb in slot 0 and the LBBPc in slot 3 (in the lower left

corner) are connected to RF modules. The LBBPd in slot 2 can communicate with the boards in

slot 0, 1, and 3 through backplane channels at the same time. Each LBBP supports a maximum

of three cells. Each of the RF modules connected to the LBBPc in slot 3 supports two carriers.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




26



Figure 6-1 Baseband resource conflict when multiple converging boards are configured

To solve this problem, configure the boards in slots 0 and 2 as a single set of baseband equipment

and the boards in slots 1 and 3 as another set. The eNodeB selects only the LBBPd in slot 2 for

cells served by the RF modules connected to the UBRIb in slot 0, and the eNodeB selects only

the LBBPc boards in slots 1 and 3 for cells served by the RF modules connected to the LBBPc

in slot 3.

In the BBU3900, some slots are not interconnected through the backplane. As shown in Table

3-2, slot 0 is not interconnected with slot 4 or 5 through the backplane. To prevent the eNodeB

from selecting a baseband processing unit for a cell through the backplane in such scenarios,

bind this cell to its directly connected baseband processing unit in advance. Then, the eNodeB

will set up the cell only on this baseband processing unit, avoiding a cell setup failure due to no

interconnection between slots.

6.4.5 Hardware Adjustment

N/A

6.4.6 Initial Configuration

6.4.6.1 Using the CME to Perform Batch Configuration for Newly DeployedeNodeBs

Enter the values of the parameters listed in Table 6-1 in a summary data file, which also contains

other data for the new eNodeBs to be deployed. Then, import the summary data file into the

Configuration Management Express (CME) for batch configuration. For detailed instructions,

see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB,

which is available in the eNodeB product documentation.

eRAN




27



The summary data file may be a scenario-specific file provided by the CME or a customized

file, depending on the following conditions:

l The managed objects (MOs) in Table 6-1 are contained in a scenario-specific summary

data file. In this situation, set the parameters in the MOs, and then verify and save the file.

l Some MOs in Table 6-1 are not contained in a scenario-specific summary data file. In this

situation, customize a summary data file to include the MOs before you can set the

parameters.

Table 6-1 Parameters for CPRI sharing

MO Sheet in theSummary DataFile

ParameterGroup

Remarks

BASEBA

NDEQM

BASEBANDEQM Baseband

Equipment ID,

Baseband

Equipment Type,

UMTS UL

Demodulation

Mode, Baseband

Equipment Board,

Cabinet No., Slot

No., Subrack No.

N/A

6.4.6.2 Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on

existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple

eNodeBs in a single procedure. The procedure is as follows:

Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose

Advanced > Customize Summary Data File (CME client mode), to customize a summary data

file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration

Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station

Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into

the customized summary data file.

Step 3 In the summary data file, set the parameters in the MOs listed in 6.4.6.1 Using the CME to

Perform Batch Configuration for Newly Deployed eNodeBs and close the file.

Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration

Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station

Bulk Configuration Data (CME client mode), to import the summary data file into the CME.

eRAN




28



Step 5 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose

Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export

and activate the incremental scripts.

----End

6.4.6.3 Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.

The procedure is as follows:

Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.

Step 2 In area 1 shown in Figure 6-2, select the eNodeB to which the MOs belong.

Figure 6-2 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.

Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are

displayed in area 4.

Step 5 Set the parameters in area 4 or 5.

Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose

Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export

and activate the incremental scripts.

----End

6.4.6.4 Using MML Commands

The configuration procedures are as follows:

eRAN




29



Step 1 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 the related

converged boards as a set of baseband equipment.

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 Run the ADD EUCELLSECTOREQM command to bind the cell to the sector equipment and

baseband equipment.

Example:

ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=1, BASEBANDEQMID=1;

Step 9 Run the ACT CELL command to activate the cell.

----End

6.4.7 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. Therefore, 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 figureshows an example of the command output.

Step 2 Run the LST RRU command to query the chain number of the RF module serving the cell. In

this step, set the cabinet number, subrack number, and slot number to the values queried in Step

1. The following figure shows an example of the command output.

eRAN




30



Step 3 Run the LST RRUCHAIN command to query the head cabinet number, head subrack number,

and head slot number of the RRU chain. In this step, set the RRU chain number to that queried

in Step 2. The following figure shows an example of the command output.

The result of Step 1 shows that the cabinet number, subrack number, and slot number of the

LBBP on which the cell is configured are 0, 0, and 2, respectively. The result of Step 3 shows

that the cabinet number, subrack number, and slot number of the RRU chain head are 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.8 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 completed.

lThe baseband resources are sufficient.

Reconfigure the BASENABDEQM MO with the slot numbers changed from X and Y to X and

Z or Y and Z .

6.4.9 Deactivation

CPRI sharing takes effect only if the convergence cells are activated. To deactivate CPRI sharing,

deactivate the convergence cells.

6.4.9.1 Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on

eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple

eRAN




31



eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for

feature activation described in 6.4.6.1 Using the CME to Perform Batch Configuration for

Newly Deployed eNodeBs. In the procedure, modify parameters according to Table 6-2.

Table 6-2 MO involved in feature deactivation

MO Sheet in the SummaryData File

Parameter Group Setting Notes

Cell Cell Basic Parameters CellActiveState Set this parameter to

CELL_DEACTIV

E(Deactivated).

6.4.9.2 Using the CME to Perform Single Configuration

On the CME, set the parameter according to Table 6-2. For detailed instructions, see 6.4.6.3

Using the CME to Perform Single Configuration described for feature activation.

6.4.9.3 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 Troubleshooting

Fault Description

Cell status is abnormal.

Fault Handling

Start cell status monitoring on the U2000 client. 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.

The following table lists common alarms related to a cell.

eRAN




32



Alarm ID Alarm Name Alarm Type Severity NetworkManagementType

ALM-29240 CellUnavailable Fault Major Signalingsystem

ALM-29243 Cell Capability

Degraded

Fault Major Signaling

system

eRAN




33



7 Parameters

Table 7-1 Parameter description

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

BASEB

ANDEQ

M

BASEB

ANDEQ

MID

ADD

BASEB

ANDEQ

M

LST

BASEB

ANDEQM

MOD

BASEB

ANDEQ

M

RMV

BASEB

ANDEQ

M

None None Meaning: Indicates the number of the baseband

equipment.

GUI Value Range: 0~23

Unit: None

Actual Value Range: 0~23

Default Value: None

eRAN

CPRI Sharing Feature Parameter Description 7 Parameters



34



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

BASEBANDEQ

M

BASEBANDEQ

MTYPE

ADDBASEB

ANDEQ

M

LST

BASEB

ANDEQ

M

MOD

BASEB

ANDEQ

MRMV

BASEB

ANDEQ

M

None None Meaning: Indicates the type of baseband equipment.GUI Value Range: UL(UL), DL(DL), ULDL

(Combined UL and DL)

Unit: None

Actual Value Range: UL, DL, ULDL

Default Value: None

BASEB

ANDEQ

M

UMTSD

EMMO

DE

ADD

BASEB

ANDEQ

M

LST

BASEBANDEQ

M

None None Meaning: Indicates the demodulation mode of an uplink

baseband signaling processing equipment for UMTS.

For a newly added uplink baseband signaling

processing board, the demodulation mode must be

specified. Different sets of uplink baseband signaling

processing board can have different demodulation

modes. This parameter is not used for the GSM mode,

and therefore it is recommended that this parameter be

set to NULL for the GSM mode. This parameter cannot

be set to NULL for the UMTS mode. This parameter is

not used for the LTE mode, and therefore it is

recommended that this parameter be set to NULL for

the 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)

Unit: None

Actual Value Range: NULL, DEM_4_CHAN,

DEM_ECON_4_CHAN, DEM_2_CHAN

Default Value: None

eRAN




35



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

BASEBANDEQ

M

BASEBANDEQ

MBOA

RD

None None None Meaning: Indicates the information about the baseband processing unit.


Unit: None


Default Value: None

eUCellS

ectorEq

m

LocalCe

llId

ADD

EUCEL

LSECT

OREQ

M

LST

EUCEL

LSECT

OREQ

M

MOD

EUCEL

LSECT

OREQ

M

RMV

EUCEL

LSECT

OREQ

M

DSP

EURTW

P

None None Meaning: Indicates the local cell identity. It uniquely

identifies a cell within an eNodeB.


Unit: NoneActual Value Range: 0~255

Default Value: None

eRAN




36



MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

eUCellSectorEq

m

SectorEqmId ADDEUCEL

LSECT

OREQ

M

DSP

EURTW

P

LST

EUCEL

LSECT

OREQM

MOD

EUCEL

LSECT

OREQ

M

RMV

EUCEL

LSECT

OREQ

M

None None Meaning: Indicates the ID of the sector device thatserves the cell,it uniquely identifies a sector device

within an eNodeB.


Unit: None


Default Value: None

EuSecto

rEqmGr

oup

BaseBan

dEqmId

ADD

EUSEC

TOREQ

MGRO

UP

MOD

EUSEC

TOREQ

MGRO

UPLST

EUSEC

TOREQ

MGRO

UP

None None Meaning: Indicates the ID of the baseband equipment

serving a cell. When this parameter is set to 255, the

baseband equipment serving a cell is not specified. In

this scenario, the LTE baseband processing units

(LBBPs) serving a cell are selected among all LBBPs

in the eNodeB, and the LBBPs to which the cell's

serving RRU is connected are preferentially selected.

When this parameter is set to a value other than 255, the

cell is served by LBBPs in the specified baseband

equipment, and the LBBPs to which the cell's serving

RRU is connected are preferentially selected.

GUI Value Range: 0~23,255

Unit: None

Actual Value Range: 0~23,255

Default Value: 255

eRAN




37



8 Counters

There are no specific counters associated with this feature.

eRAN

CPRI Sharing Feature Parameter Description 8 Counters



38



9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN

CPRI Sharing Feature Parameter Description 9 Glossary



39



10 Reference Documents

1. Cell Management Feature Parameter Description

eRAN

CPRI Sharing Feature Parameter Description 10 Reference Documents