CPRI MUX (LampSite)(SRAN11.1_02)

SingleRAN

CPRI MUX (LampSite) Feature Parameter Description Issue

02

Date

2016-03-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. 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 02 (2016-03-31)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

SingleRAN CPRI MUX (LampSite) 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 Base Station Types....................................................................................................................... 2

2 Overview......................................................................................................................................... 3 2.1 Introduction.................................................................................................................................................................... 3 2.2 Benefits........................................................................................................................................................................... 4

3 Dependencies on BBU Boards and RF Units........................................................................... 5 3.1 BBU3900 Boards Supporting CPRI MUX.....................................................................................................................6 3.2 BBU3910 Boards Supporting CPRI MUX.....................................................................................................................8 3.3 RF Units Supporting CPRI MUX...................................................................................................................................9

4 CPRI MUX Topologies with BBU3900s Used in the LampSite Solution......................... 11 4.1 CPRI MUX for Co-MPT Multimode Base Stations.....................................................................................................12 4.1.1 Constraints................................................................................................................................................................. 12 4.1.2 CPRI MUX Networking Mode..................................................................................................................................12 4.2 CPRI MUX for Separate-MPT Multimode Base Stations............................................................................................15 4.2.1 Constraints................................................................................................................................................................. 15 4.2.2 CPRI MUX Networking Mode..................................................................................................................................15

5 CPRI MUX Topologies with BBU3910s Used in the LampSite Solution......................... 19 5.1 CPRI MUX for Co-MPT Multimode Base Stations.....................................................................................................20 5.1.1 Constraints................................................................................................................................................................. 20 5.1.2 CPRI MUX Networking Mode..................................................................................................................................20 5.2 CPRI MUX for Separate-MPT Multimode Base Stations............................................................................................22 5.2.1 Constraints................................................................................................................................................................. 22 5.2.2 CPRI MUX Networking Mode..................................................................................................................................22

6 Specifications of the CPRI MUX Feature................................................................................26 7 Related Features...........................................................................................................................45 8 Network Impact........................................................................................................................... 46 8.1 System Capacity........................................................................................................................................................... 46 Issue 02 (2016-03-31)


ii


Contents

8.2 Network Performance...................................................................................................................................................46 8.3 Reliability..................................................................................................................................................................... 46

9 Engineering Guidelines............................................................................................................. 48 9.1 When to Use CPRI MUX............................................................................................................................................. 49 9.2 Required Information................................................................................................................................................... 49 9.3 Planning........................................................................................................................................................................ 49 9.4 Deployment.................................................................................................................................................................. 50 9.4.1 Requirements............................................................................................................................................................. 50 9.4.2 Data Preparation........................................................................................................................................................ 50 9.4.3 Activation.................................................................................................................................................................. 54 9.4.4 Activation Observation..............................................................................................................................................56 9.4.5 Deactivation...............................................................................................................................................................57 9.4.6 Reconfiguration......................................................................................................................................................... 57 9.5 Performance Monitoring...............................................................................................................................................57 9.6 Parameter Optimization................................................................................................................................................ 57 9.7 Troubleshooting............................................................................................................................................................ 57 9.7.1 Related Alarms.......................................................................................................................................................... 58 9.7.2 MML Commands for Maintenance........................................................................................................................... 58

10 Parameters................................................................................................................................... 61 11 Counters...................................................................................................................................... 62 12 Glossary....................................................................................................................................... 63 13 Reference Documents............................................................................................................... 64

Issue 02 (2016-03-31)


iii


1

1 About This Document

About This Document

1.1 Scope This document describes the CPRI MUX feature, including its technical principles, related features, network impact, and engineering guidelines. The base stations mentioned in this document refer to DBS3900 base stations in the LampSite solution. Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases. GSM, UMTS, and LTE are abbreviated as G, U, and L, respectively.

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.

SRAN11.1 02 (2016-03-31) This issue includes the following changes. Issue 02 (2016-03-31)


1


1 About This Document

Change Type

Change Description

Parameter Change

Feature change

Supported the UBBPe board. For details, see the following chapters:

None

l 3 Dependencies on BBU Boards and RF Units l 4 CPRI MUX Topologies with BBU3900s Used in the LampSite Solution l 5 CPRI MUX Topologies with BBU3910s Used in the LampSite Solution Editorial change

None

None

SRAN11.1 01 (2016-03-07) This issue includes the following changes. Change Type

Change Description

Parameter Change

Feature change

None

None

Editorial change

None

None

SRAN11.1 Draft A (2015-12-30) This issue includes the following changes. Change Type

Change Description

Parameter Change

Feature change

Modified the CPRI line rate supported by LampSite. Fordetails, see 6 Specifications of the CPRI MUX Feature

None

Editorial change

None

None

1.4 Differences Between Base Station Types This feature can only be used with LampSite. Issue 02 (2016-03-31)


2


2 Overview

2

Overview

2.1 Introduction The CPRI MUX feature enables data transmission of multiple modes (such as UMTS, and LTE) on a common public radio interface (CPRI) port. Figure 2-1 shows the working principle of CPRI MUX. A multimode RF unit is connected to a single-mode or multimode(1) baseband processing unit (BBP)/interface board through CPRI connection. Another single-mode or multimode(1) BBP/interface board is connected to the preceding BBP/interface board through the BBU backplane and indirectly communicates with the multimode RF unit. The BBP/interface board that is directly connected to the multimode RF unit is called the converging board, and the corresponding mode is called the converging party. The BBP/ interface board that is indirectly connected to the multimode RF unit is called the converged board, and the corresponding mode is called the converged party. In Figure 2-1, mode A is the converged party and mode B is the converging party. Figure 2-1 Working principle of CPRI MUX

NOTE

In the LampSite solution, a multimode RF unit indicates a combination of the RHUB and pRRU.

Issue 02 (2016-03-31)


3


2 Overview

2.2 Benefits This feature provides the following benefits: l

Reduced costs on optical modules and fiber optic cables for newly deployed multimode base stations: Multiple modes can use a CPRI port to transmit data, reducing the number of required optical modules and fiber optic cables considerably.

l

Low engineering costs and short service interruption duration in refarming scenarios: A multimode RF unit uses a single CPRI cable at the initial phase. CPRI MUX enables newly deployed modes to reuse the existing multimode RF unit and CPRI cable in refarming scenarios.

l

Guaranteed coverage for cascaded multimode RF units: CPRI MUX allows multimode RF units to be cascaded to ensure indoor coverage of different floors or areas. The LampSite solution supports only RHUB cascading and does not support pRRU cascading.

Issue 02 (2016-03-31)


4


3

3 Dependencies on BBU Boards and RF Units

Dependencies on BBU Boards and RF Units

This chapter describes BBU boards and RF units that support CPRI MUX.

Issue 02 (2016-03-31)


5



3.1 BBU3900 Boards Supporting CPRI MUX Co-MPT Scenarios In co-MPT scenarios, either or both of UMTS and LTE can serve as the converging party or converged party. A new feature is introduced in SRAN11.0, enabling LTE FDD and LTE TDD to use the same MPT board. Both UL and FT support the co-MPT scenarios in SRAN11.0. Table 3-1 lists BBU3900 boards that support the CPRI MUX feature in a co-MPT multimode base station and constraints on the slots of the converging and converged boards. Table 3-1 BBU3900 boards that support the CPRI MUX feature in a co-MPT multimode base station and constraints on networking Mod e

Converging Board

Slot of the Converging Board

Constraints on Networking

UL

WBBPf, LBBPd, UBBPd/e_U, UBBPd/e_L

Slot 2 or 3

A WBBPf or UBBPd/e_Ux must be configured in slot 2 or 3.

FT

LBBPd, UBBPd/e_L

Slot 2 or 3

A UBBPd/e_Ux must be configured in slot 2 or 3.

NOTE

If a baseband processing board is named UBBPd/e_A/B/C, "A", "B", "C" indicates the mode whose baseband resources are configured on this board, baseband resources of different modes are isolated by "/". For example, UBBPd/e_U/L indicates a UBBPd/e configured with UMTS baseband resources, LTE baseband resources.

Separate-MPT Scenarios In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. SRAN11.0 allows LTE FDD and LTE TDD to use the same MPT board, so that UMTS and FDD+TDD can be applied to a separate-MPT multimode base station in SRAN11.0. Table 3-2 lists BBU3900 boards that support the CPRI MUX feature in a separate-MPT multimode base station and constraints on the slots of the converging and converged boards.

Issue 02 (2016-03-31)


6



Table 3-2 BBU3900 boards that support the CPRI MUX feature in a separate-MPT multimode base station and constraints on the slots of the converging and converged boards Mode

Converging Board


Converged Board

Slot of the Converged Board

UL

WBBPf or UBBPd/e_U

Slot 2 or 3

LBBPd or UBBPd/e_L

An LBBPd must be installed in slot 3 or 2.

LBBPd or UBBPd/e_L

Slot 2 or 3

WBBPf or UBBPd/e_U

A WBBPf must be installed in slot 3 or 2.

WBBPf or UBBPd/e_U

Slot 2 or 3

LBBPd or UBBPd/e_L

An LBBPd or UBBPd/e_L must be installed in slot 3 or 2.

LBBPd or UBBPd/e_L

Slot 2 or 3

WBBPf or UBBPd/e_U

A WBBPf or UBBPd/e_U must be installed in slot 3 or 2.

U+FT

Restrictions on Slot Cabling Restrictions on slot cabling are imposed to maximize the utilization of baseband resources when the network uses CPRI MUX. Following these restrictions, operators do not need to adjust the connections of boards or fiber optic cables in future capacity expansion (for example, capacity expansion from UMTS Only or LTE Only to UMTS+LTE). l

If a UBBPd/e is to be installed with a WBBPf or LBBPd, install the UBBPd/e in slot 2 or 3 and the LBBPd3 in slot 1. It is recommended that the fiber optic cables be connected to slot 3 of the UBBPd/e.

l

If an LBBPd1 or LBBPd2 is to be installed with an LBBPd3, install the LBBPd3 preferentially in a switching slot(such as slot3) or slot1. It is recommended that the fiber optic cables be connected to slot 3.

l

If a WBBPf3 or WBBPf4 is to be installed with an LBBPd1, LBBPd2, or LBBPd3, install them in slots 2 and 3, which are switching slots. Install the LBBPd3 preferentially in slot 3 or 1. It is recommended that the fiber optic cables be connected to slot 3.

l

In UMTS Only scenarios, the fiber optic cables can be connected to slots 2 and 3. It is recommended that the fiber optic cables be connected to slot 3. Do not connect the fiber optic cables to other slots to prevent cable adjustment in future capacity expansion from UMTS Only to UMTS+LTE.

l

In LTE Only scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4, and 5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and slot 2. Do not connect the fiber optic cables to other slots to prevent cable adjustment in future capacity expansion from LTE Only to UMTS+LTE.

l

In UMTS+LTE scenarios, the fiber optic cables can be connected only to slots 2 and 3. It is recommended that the fiber optic cables be connected to slot 3.

Issue 02 (2016-03-31)


7



3.2 BBU3910 Boards Supporting CPRI MUX Co-MPT Scenarios In co-MPT scenarios, either or both of UMTS and LTE can serve as the converging party or converged party. A new feature is introduced in SRAN11.0, enabling LTE FDD and LTE TDD to use the same MPT board. Both UL and FT support the co-MPT scenarios in SRAN11.0. Table 3-3 lists BBU3910 boards that support the CPRI MUX feature in a co-MPT multimode base station and constraints on the slots of the converging and converged boards. Table 3-3 BBU3910 boards that support the CPRI MUX feature in a co-MPT multimode base station Mode

Converging Board


UL

UBBPd/e_U/L

Slot0~Slot5

FT

UBBPd/e_L

Slot0~Slot5

Separate-MPT Scenarios In separate-MPT scenarios, only UMTS and LTE can serve as the converging party. SRAN11.0 allows LTE FDD and LTE TDD to use the same MPT board, so that UMTS and FDD+TDD can be applied to a separate-MPT multimode base station in SRAN11.0. Table 3-4 lists BBU3910 boards that support the CPRI MUX feature in a separate-MPT multimode base station and constraints on the slots of the converging and converged boards. Table 3-4 BBU3910 boards that support the CPRI MUX feature in a separate-MPT multimode base station Mode

Converging Board


Converged Board


UL

UBBPd_U

Slot0~Slot5

UBBPd_L

Slot0~Slot5

UBBPd_L

Slot0~Slot5

UBBPd_U

Slot0~Slot5

UBBPd_U

Slot0~Slot5

UBBPd_L

Slot0~Slot5

UBBPd_L

Slot0~Slot5

UBBPd_U

Slot0~Slot5

U+FT

In SRAN11.0, optical fibers can be connected to slots 2 and 3 on the UMTS+LTE BBU3910 in CPRI MUX. In separate-MPT scenarios, one-to-two converging mode is used and two Issue 02 (2016-03-31)


8



converging parties are allowed. The two converging parties must work in the same radio access technology. Table 3-5 BBU3910 boards in CPRI MUX that support two-slot optical fiber connections in a separate-MPT multimode base station Mode

Converging Board


Converged Board


UL

UBBPd_U+ UBBPd_U

Slot2 + Slot3

UBBPd_L

Slot0, Slot1, Slot4, and Slot5

UBBPd_L+ UBBPd_L

Slot2 + Slot3

UBBPd_U

Slot0, Slot1, Slot4, and Slot5

Restrictions on Slot Cabling Restrictions on slot cabling are imposed to maximize the utilization of baseband resources when the network uses CPRI MUX. Following these restrictions, operators do not need to adjust the connections of boards or fiber optic cables in future capacity expansion (for example, capacity expansion from UMTS Only or LTE Only to UMTS+LTE). l

In the current release, the BBU3910 supports only the UBBPd serving as the baseband processing unit. The UBBPd can be installed in any slot. In separate-MPT scenarios, you are advised to install the baseband processing units of the same radio access technology in slots 2 and 3 so that the fiber optic cables can be connected to the two slots to support UMTS and LTE in future capacity expansion. In co-MPT scenarios, there are no such restrictions.

l

In UMTS Only scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4, and 5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and slot 2. Do not connect the fiber optic cables to other slots to prevent cable adjustment in future capacity expansion from UMTS Only to UMTS+LTE.

l

In LTE Only scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4, and 5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and slot 2. Do not connect the fiber optic cables to other slots to prevent cable adjustment in future capacity expansion from LTE Only to UMTS+LTE.

l

In UMTS+LTE scenarios, the fiber optic cables can be connected to slots 0, 1, 2, 3, 4, and 5. It is recommended that the fiber optic cables be connected to slot 3 (preferred) and slot 2. Do not connect the fiber optic cables to other slots.

3.3 RF Units Supporting CPRI MUX Table 3-6 lists RF units that support the CPRI MUX feature. Table 3-6 RF units that support CPRI MUX RF Unit

Issue 02 (2016-03-31)

Working Mode

CPRI MUX Support (Yes/No) Co-MPT


Separate-MPT 9


Issue 02 (2016-03-31)


RHUB3908

UL

Yes

Yes

pRRU3901

UL

Yes

Yes

pRRU3902

UL

Yes

Yes

pRRU3907

UL

Yes

Yes

pRRU3911

UL

Yes

Yes


10


4

4 CPRI MUX Topologies with BBU3900s Used in the LampSite Solution

CPRI MUX Topologies with BBU3900s Used in the LampSite Solution

This chapter describes CPRI MUX topologies in the LampSite solution for co-MPT multimode base stations and separate-MPT multimode base stations.

Issue 02 (2016-03-31)


11



4.1 CPRI MUX for Co-MPT Multimode Base Stations 4.1.1 Constraints The converging and converged parties in the CPRI MUX feature must share one BBU.

4.1.2 CPRI MUX Networking Mode The following conditions must be met: l

A WBBPf, LBBPd, UBBPd/e_U, UBBPd/e_L can serve as the converging board and must be configured in slot 2 or 3.

l

A WBBPf or UBBPd/e_U must be configured in slot 2 or 3.

l

A BBU can connect to a maximum of 24 RHUBs. The RHUB connects to the BBU only in chain (single-link) topology. A BBU supports multiple RHUB chains. Each CPRI link supports a maximum of four levels of RHUB cascading.

l

When RHUBs and pRRUs work in branch chain (single-link) topology, an RHUB can connect to a maximum of eight pRRUs and the pRRUs do not support cascading.

l

When RHUBs and pRRUs work in branch load sharing topology, an RHUB can connect to a maximum of four pRRUs and the pRRUs do not support cascading.

Figure 4-1 shows UMTS+LTE CPRI MUX in branch chain (single-link) topology, where LTE serves as the converging party and UMTS serves as the converged party; the LBBPd/ UBBPd_L serves as the converging board and the WBBPf/UBBPd_U serves as the converged board. Figure 4-1 UMTS+LTE CPRI MUX in co-MPT scenarios in branch chain (single-link) topology

Issue 02 (2016-03-31)


12



Figure 4-2 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE serves as the converging party and UMTS serves as the converged party; the LBBPd/ UBBPd_L serves as the converging board and the WBBPf/UBBPd_U serves as the converged board. Figure 4-2 UMTS+LTE CPRI MUX in co-MPT scenarios in branch load sharing topology

Figure 4-3 shows LTE FDD+LTE TDD CPRI MUX in branch chain (single-link) topology, where LTE TDD serves as the converging party and LTE FDD serves as the converged party; the LBBPd_T/UBBPd_T serves as the converging board and the LBBPd_F/UBBPd_F serves as the converged board.

Issue 02 (2016-03-31)


13



Figure 4-3 FDD+TDD CPRI MUX in co-MPT scenarios in branch chain (single-link) topology

Figure 4-4 shows LTE FDD+LTE TDD CPRI MUX in branch load sharing topology, where LTE TDD serves as the converging party and LTE FDD serves as the converged party; the LBBPd_T/UBBPd_T serves as the converging board and the LBBPd_F/UBBPd_F serves as the converged board. Figure 4-4 FDD+TDD CPRI MUX in co-MPT scenarios in branch load sharing topology

Issue 02 (2016-03-31)


14



4.2 CPRI MUX for Separate-MPT Multimode Base Stations 4.2.1 Constraints l

The converging and converged parties in the CPRI MUX feature must share one BBU.

l

One mode serves as either the converging party or the converged party but cannot serves as both parties. Data can be converged only to one converging board at a time.

l

One BBU can provide a maximum of six CPRI ports for data convergence, and these CPRI ports must be provided by the WBBPf, LBBPd, UBBPd/e_U, or UBBPd/e_L that is installed in slot 2 or 3.


A WBBPf, LBBPd, UBBPd/e_U, or UBBPd/e_L can serve as the converging board and must be configured in slot 2 or 3.

l

A WBBPf/UBBPd/e_U and an LBBPd/UBBPd/e_L must be configured in slot 2 and slot 3, respectively.

l


l


l


Figure 4-5 shows UMTS+LTE CPRI MUX in branch chain (single-link) topology, where LTE serves as the converging party and UMTS serves as the converged party; the LBBPd/ UBBPd/e_L serves as the converging board and the WBBPf/UBBPd/e_U serves as the converged board.

Issue 02 (2016-03-31)


15



Figure 4-5 UMTS+LTE CPRI MUX in separate-MPT scenarios in branch chain (single-link) topology

Figure 4-6 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE serves as the converging party and UMTS serves as the converged party; the LBBPd/ UBBPd/e_L serves as the converging board and the WBBPf/UBBPd/e_U serves as the converged board. Figure 4-6 UMTS+LTE CPRI MUX in separate-MPT scenarios in load sharing topology

Figure 4-7 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch chain (single-link) topology, where LTE (FDD+TDD) serves as the converging party and UMTS serves as the Issue 02 (2016-03-31)


16



converged party; the LBBPd_T/UBBPd/e_T serves as the converging board and the LBBPd_F/UBBPd/e_F and WBBPf/UBBPd/e_U serve as the converged boards. Figure 4-7 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch chain (single-link) topology

Figure 4-8 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch load sharing topology, where LTE (FDD+TDD) serves as the converging party and UMTS serves as the converged party; the LBBPd_T/UBBPd/e_T serves as the converging board and the LBBPd_F/ UBBPd/e_F and WBBPf/UBBPd/e_U serve as the converged boards.

Issue 02 (2016-03-31)


17



Figure 4-8 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch load sharing topology

Issue 02 (2016-03-31)


18


5


CPRI MUX Topologies with BBU3910s Used in the LampSite Solution

This chapter describes CPRI MUX topologies in the LampSite solution for co-MPT multimode base stations and separate-MPT multimode base stations.

Issue 02 (2016-03-31)


19



5.1 CPRI MUX for Co-MPT Multimode Base Stations 5.1.1 Constraints The converging and converged parties in the CPRI MUX feature must share one BBU. In SRAN11.1, fiber optic cables can be connected to 12 CPRI ports on the BBU baseband processing unit to support the CPRI MUX feature.


A UBBPd/e_U, UBBPd/e_L can serve as the converging board and can be configured in slot 0~5. In SRAN11.0, optical fibers can be connected to slots 2 and 3 on the BBU3910 in CPRI MUX. The converging board is UBBPd/e_U/L.

l


l


l


Figure 5-1 shows UMTS+LTE CPRI MUX in branch chain (single-link) topology, where LTE serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L serves as the converging board and the UBBPd/e_U serves as the converged board. Figure 5-1 UMTS+LTE CPRI MUX in co-MPT scenarios in branch chain (single-link) topology

Issue 02 (2016-03-31)


20



Figure 5-2 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L serves as the converging board and the UBBPd/e_U serves as the converged board. Figure 5-2 UMTS+LTE CPRI MUX in co-MPT scenarios in branch load sharing topology

Figure 5-3 shows LTE FDD+LTE TDD CPRI MUX in branch chain (single-link) topology, where LTE TDD serves as the converging party and LTE FDD serves as the converged party; the UBBPd/e_T serves as the converging board and the UBBPd/e_F serves as the converged board. Figure 5-3 FDD+TDD CPRI MUX in co-MPT scenarios in branch chain (single-link) topology

Issue 02 (2016-03-31)


21



Figure 5-4 shows LTE FDD+LTE TDD CPRI MUX in branch load sharing topology, where LTE TDD serves as the converging party and LTE FDD serves as the converged party; the UBBPd/e_T serves as the converging board and the UBBPd/e_F serves as the converged board. Figure 5-4 FDD+TDD CPRI MUX in co-MPT scenarios in branch load sharing topology

5.2 CPRI MUX for Separate-MPT Multimode Base Stations 5.2.1 Constraints The converging and converged parties in the CPRI MUX feature must share one BBU.


A UBBPd/e_U or UBBPd/e_L can serve as the converging board and can be configured in slot 0~5. In SRAN11.0, optical fibers can be connected to slots 2 and 3 on the BBU3910 in CPRI MUX. The converging board is UBBPd/e_U/L. Slots 2 and 3 must house the baseband processing units working in the same radio access technology.

l


l


l


Issue 02 (2016-03-31)


22



Figure 5-5 shows UMTS+LTE CPRI MUX in branch chain (single-link) topology, where LTE serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L serves as the converging board and the UBBPd/e_U serves as the converged board. Figure 5-5 UMTS+LTE CPRI MUX in separate-MPT scenarios in branch chain (single-link) topology

Figure 5-6 shows UMTS+LTE CPRI MUX in branch load sharing topology, where LTE serves as the converging party and UMTS serves as the converged party; the UBBPd/e_L serves as the converging board and the UBBPd/e_U serves as the converged board. Figure 5-6 UMTS+LTE CPRI MUX in separate-MPT scenarios in load sharing topology

Issue 02 (2016-03-31)


23



Figure 5-7 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch chain (single-link) topology, where LTE (FDD+TDD) serves as the converging party and UMTS serves as the converged party; the UBBPd/e_T serves as the converging board and the UBBPd/e_F and UBBPd/e_U serve as the converged boards. Figure 5-7 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch chain (single-link) topology

Figure 5-8 shows UMTS+LTE (FDD+TDD) CPRI MUX in branch load sharing topology, where LTE (FDD+TDD) serves as the converging party and UMTS serves as the converged party; the UBBPd/e_T serves as the converging board and the UBBPd/e_F and UBBPd/e_U serve as the converged boards.

Issue 02 (2016-03-31)


24



Figure 5-8 UMTS+LTE (FDD+TDD) CPRI MUX in separate-MPT scenarios in branch load sharing topology

Issue 02 (2016-03-31)


25


6

6 Specifications of the CPRI MUX Feature

Specifications of the CPRI MUX Feature

In separate-MPT or co-MPT CPRI MUX scenarios, the converging capabilities of a multimode base station are determined by CPRI line rates and the capabilities of the converging party. Table 6-1 and Table 6-2 provide the converging capabilities of the converging party.

Issue 02 (2016-03-31)


26



Table 6-1 Converging capabilities of the converging party in multimode base stations enabled with CPRI MUX (LTE full compression) Co-MPT or SeparateMPT

Baseband Processing Board Providing CPRI Optical Ports

Converging Capabilities of A CPRI Link (4.9 Gbit/s)


Co-MPT

WBBPf/LBBPd

4*LTE20MHz+UMTS 0*Cell(20M/15M only)

5*LTE20MHz+UMTS 0*Cell

3*LTE20MHz+UMTS 0*Cell(with different LTE bandwidths)


2*LTE20MHz+UMTS 1*Cell 1*LTE20MHz+UMTS 3*Cell 0*LTE20MHz+UMTS 6*Cell 6*LTE10MHz+UMTS 0*Cell(10M only) 5*LTE10MHz+UMTS 0*Cell(with different LTE bandwidths)

3*LTE20MHz+UMTS 4*Cell 2*LTE20MHz+UMTS 6*Cell 1*LTE20MHz+UMTS 8*Cell 0*LTE20MHz+UMTS 10*Cell 8*LTE10MHz+UMTS 0*Cell 7*LTE10MHz+UMTS 1*Cell








3*LTE10MHz+UMTS 6*Cell 2*LTE10MHz+UMTS 8*Cell 1*LTE10MHz+UMTS 9*Cell 0*LTE10MHz+UMTS 10*Cell

Issue 02 (2016-03-31)


27


Co-MPT or SeparateMPT





UBBPd/e











6*LTE10MHz+UMTS 0*Cell(10M only)




3*LTE10MHz+UMTS 1*Cell 2*LTE10MHz+UMTS 2*Cell

0*LTE20MHz+UMTS 13*Cell 12*LTE10MHz+UMTS 0*Cell(10M only)




8*LTE10MHz+UMTS 1*Cell 7*LTE10MHz+UMTS 2*Cell 6*LTE10MHz+UMTS 3*Cell 5*LTE10MHz+UMTS 4*Cell 4*LTE10MHz+UMTS 5*Cell 3*LTE10MHz+UMTS 6*Cell 2*LTE10MHz+UMTS 8*Cell 1*LTE10MHz+UMTS 10*Cell 0*LTE10MHz+UMTS 13*Cell

Issue 02 (2016-03-31)


28







Separate-MPT

WBBPf/LBBPd





2*LTE20MHz+UMTS 2*Cell 1*LTE20MHz+UMTS 5*Cell 0*LTE20MHz+UMTS 6*Cell 6*LTE10MHz+UMTS 0*Cell(10M only) 5*LTE10MHz+UMTS 0*Cell(with different LTE bandwidths)











2*LTE10MHz+UMTS 10*Cell 1*LTE10MHz+UMTS 10*Cell 0*LTE10MHz+UMTS 10*Cell

Issue 02 (2016-03-31)


29







LBBPd Extended

Not supported

8*LTE20MHz+UMTS 0*Cell(20M/15M only) 6*LTE20MHz+UMTS 0*Cell(with different LTE bandwidths) 5*LTE20MHz+UMTS 3*Cell 4*LTE20MHz+UMTS 5*Cell 3*LTE20MHz+UMTS 7*Cell 2*LTE20MHz+UMTS 9*Cell 1*LTE20MHz+UMTS 10*Cell 0*LTE20MHz+UMTS 10*Cell 12*LTE10MHz+UMTS 0*Cell(10M only) 10*LTE10MHz+UMTS 0*Cell(with different LTE bandwidths) 9*LTE10MHz+UMTS 1*Cell 8*LTE10MHz+UMTS 3*Cell 7*LTE10MHz+UMTS 4*Cell 6*LTE10MHz+UMTS 5*Cell 5*LTE10MHz+UMTS 6*Cell 4*LTE10MHz+UMTS 8*Cell 3*LTE10MHz+UMTS 9*Cell 2*LTE10MHz+UMTS 10*Cell 1*LTE10MHz+UMTS 10*Cell

Issue 02 (2016-03-31)


30








Issue 02 (2016-03-31)


31







UBBPd/e











6*LTE10MHz+UMTS 0*Cell(10M only)




4*LTE10MHz+UMTS 1*Cell 3*LTE10MHz+UMTS 2*Cell

0*LTE20MHz+UMTS 13*Cell 12*LTE10MHz+UMTS 0*Cell(10M only)






8*LTE10MHz+UMTS 3*Cell 7*LTE10MHz+UMTS 4*Cell 6*LTE10MHz+UMTS 5*Cell 5*LTE10MHz+UMTS 6*Cell 4*LTE10MHz+UMTS 8*Cell 3*LTE10MHz+UMTS 9*Cell 2*LTE10MHz+UMTS 10*Cell 1*LTE10MHz+UMTS 12*Cell

Issue 02 (2016-03-31)


32








NOTE

l The converging capabilities of a CPRI link or a board and the CPRI link rate refer to those of the converging party. l In the LampSite solution, the CPRI line rate of 4.9 Gbit/s or 9.8 Gbit/s is recommended. l The capabilities of the converging board cannot exceed the maximum capacity specifications of a site. For the maximum capacity specifications of a site, see Product Specifications > Technical Specifications of the BBU3900 > Capacity Specifications in DBS3900 LampSite Technical Description. l Converging capabilities in Table 6-1 apply to common cells. For the impact of different features on cell capacity, see the corresponding feature parameter description. l Table 6-1 lists the number of UMTS cells supported when the antenna capability is 1T2R. l Table 6-1 lists the number of LTE 20 MHz cells supported in the 2T2R antenna configuration, 20 MHz cell bandwidth, and 2:1 compression configuration for CPRI bandwidth. l Table 6-1 lists the number of LTE 10 MHz cells supported in the 2T2R antenna configuration, 10 MHz cell bandwidth, and 3:2 compression configuration for CPRI bandwidth. l Table 6-1 lists the converging capability of the LBBPd extended board at 9.8 Gbit/s in separateMPT mode when the LBBPd board enables the extended mode. CPRI extension mode is enabled through CPRIEX in the MOD BBP or LST BBP command. CPRI extension mode only affects the bandwidth specifications of the LBBPd at 9.8 Gbit/s in CPRI compression mode. For details, see BBU Hardware Description > BBU3900 and BBU3910 Hardware Description > BBU3900 and BBU3910 Boards > LBBP in 3900 Series Base Station Product Documentation. l The WBBPf3 board supports CPRI line rates of 4.9 Gbit/s, 6.144 Gbit/s, and 9.8 Gbit/s, but the RHUB does not support 6.144 Gbit/s. Table 6-1 does not list the CPRI line rate of 6.144 Gbit/s for the WBBPf3 board because this rate is not applicable when the WBBPf3 board is connected to the RHUB. l In separate-MPT scenarios, the LBBPd board supports CPRI extension mode. In CPRI extension mode, LTE bandwidth compression must be used. For example, a 5 MHz or 10 MHz bandwidth uses 3:2 compression and a 15 MHz or 20 MHz bandwidth uses 2:1 compression for LTE cells. l In separate-MPT scenarios, when the LBBPd board at a CPRI line rate of 9.8 Gbit/s does not enable CPRI extension mode, LTE bandwidth compression and non-compression cannot be configured on the same CPRI link. l In co-MPT scenarios, the LBBPd board does not support CPRI extension mode. l LTE in Table 6-1 supports TDD, FDD, and FDD+TDD. Note that LTE TDD 5 MHz does not support bandwidth compression but LTE FDD 5 MHz supports 3:2 bandwidth compression. Bandwidth combinations in this table do not support LTE TDD 5 MHz. Table 6-2 lists bandwidth combinations for LTE TDD 5 MHz. l "With different LTE bandwidths" in the table indicates that an LTE cell of a smaller bandwidth exists in addition to the bandwidths specified in a combination. In the combination of 6 x LTE 20 MHz + UMTS 0 x cell (with different LTE bandwidths), an LTE cell of 10 MHz or 5 MHz exists in addition to at least one 20 MHz bandwidth specified in the combination. Unless otherwise stated, a combination supports different LTE bandwidths. LampSite supports only LTE cells of 5 MHz or higher. Therefore, LTE 5 MHz in the combinations does not include other bandwidths.

Issue 02 (2016-03-31)


33



Capacity specifications for each mode with different configurations are calculated as follows: l

l

Issue 02 (2016-03-31)

UMTS –

The number of cells supported when the antenna capability is 1T1R is the same as that supported when the antenna capability is 2T2R.

–

The antenna capability is inversely proportional to the number of cells. For example, the number of cells supported when the antenna capability is 1T1R is twice that supported when the antenna capability is 2T2R.

LTE –

When LTE cells have the same antenna capability and CPRI line rate, the number of 5 MHz or 10 MHz cells supported is inversely proportional to the bandwidth of cells. For example, the number of cells supported by a 5 MHz cell is twice that supported by a 10 MHz cell. LTE 5 MHz cells and 10 MHz cells use the same compression configuration 3:2.

–

When LTE cells have the same antenna capability and CPRI line rate, 15- and 20MHz cells support the same number of cells.

–

When LTE cells have the same bandwidth, the number of cells supported by 1T2R and 2T2R antennas is the same.


34



Table 6-2 Converging capabilities of the converging party in multimode base stations enabled with CPRI MUX (LTE full non-compression/compression and non-compression) Co-MPT or SeparateMPT




Co-MPT

WBBPf/LBBPd





0*LTE20MHz+UMTS 6*Cell 4*LTE10MHz+UMTS 0*Cell(Non-compression +10M only) 3*LTE10MHz+UMTS 0*Cell(Compression/ non-compression with different LTE bandwidths)

2*LTE20MHz+UMTS 3*Cell 1*LTE20MHz+UMTS 6*Cell 0*LTE20MHz+UMTS 10*Cell 8*LTE10MHz+UMTS 0*Cell(10M only)







8*LTE5MHz+UMTS 0*Cell(Non-compression only)


6*LTE5MHz+UMTS 0*Cell(Compression and non-compression) 4*LTE5MHz+UMTS 1*Cell 3*LTE5MHz+UMTS 2*Cell 2*LTE5MHz+UMTS 3*Cell 0*LTE5MHz+UMTS 6*Cell

2*LTE10MHz+UMTS 6*Cell 1*LTE10MHz+UMTS 9*Cell 0*LTE10MHz+UMTS 10*Cell 16*LTE5MHz+UMTS 0*Cell 13*LTE5MHz+UMTS 1*Cell 10*LTE5MHz+UMTS 2*Cell 8*LTE5MHz+UMTS 3*Cell 7*LTE5MHz+UMTS 4*Cell

Issue 02 (2016-03-31)


35







5*LTE5MHz+UMTS 6*Cell 4*LTE5MHz+UMTS 7*Cell 2*LTE5MHz+UMTS 8*Cell 1*LTE5MHz+UMTS 10*Cell 0*LTE5MHz+UMTS 10*Cell

Issue 02 (2016-03-31)


36







UBBPd/e





0*LTE20MHz+UMTS 6*Cell 4*LTE10MHz+UMTS 0*Cell(Non-compression +10M only) 3*LTE10MHz+UMTS 0*Cell(Compression/ non-compression with different LTE bandwidths)

2*LTE20MHz+UMTS 3*Cell 1*LTE20MHz+UMTS 6*Cell 0*LTE20MHz+UMTS 13*Cell 8*LTE10MHz+UMTS 0*Cell(10M only)







8*LTE5MHz+UMTS 0*Cell(Non-compression only)


6*LTE5MHz+UMTS 0*Cell(Compression/ non-compression) 4*LTE5MHz+UMTS 1*Cell 3*LTE5MHz+UMTS 2*Cell 2*LTE5MHz+UMTS 3*Cell 0*LTE5MHz+UMTS 6*Cell


Issue 02 (2016-03-31)


37







4*LTE5MHz+UMTS 7*Cell 2*LTE5MHz+UMTS 8*Cell 1*LTE5MHz+UMTS 10*Cell 0*LTE5MHz+UMTS 13*Cell

Issue 02 (2016-03-31)


38







Separate-MPT

WBBPf/LBBPd







4*LTE10MHz+UMTS 0*Cell(Non-compression +10M only)


3*LTE10MHz+UMTS 0*Cell(Compression/ non-compression with different LTE bandwidths) 2*LTE10MHz+UMTS 2*Cell 1*LTE10MHz+UMTS 5*Cell 0*LTE10MHz+UMTS 6*Cell 8*LTE5MHz+UMTS 0*Cell(Non-compression only) 6*LTE5MHz+UMTS 0*Cell(Compression/ non-compression)

0*LTE20MHz+UMTS 10*Cell 8*LTE10MHz+UMTS 0*Cell(10M only) 6*LTE10MHz+UMTS 0*Cell(with different LTE bandwidths) 5*LTE10MHz+UMTS 3*Cell 4*LTE10MHz+UMTS 5*Cell 3*LTE10MHz+UMTS 7*Cell 2*LTE10MHz+UMTS 9*Cell 1*LTE10MHz+UMTS 10*Cell










12*LTE5MHz+UMTS 3*Cell 11*LTE5MHz+UMTS 4*Cell 10*LTE5MHz+UMTS 5*Cell

Issue 02 (2016-03-31)


39








Issue 02 (2016-03-31)


40







UBBPd/e







4*LTE10MHz+UMTS 0*Cell(Non-compression +10M only)


3*LTE10MHz+UMTS 0*Cell(Compression/ non-compression with different LTE bandwidths) 2*LTE10MHz+UMTS 2*Cell 1*LTE10MHz+UMTS 5*Cell 0*LTE10MHz+UMTS 6*Cell 8*LTE5MHz+UMTS 0*Cell(Non-compression only) 6*LTE5MHz+UMTS 0*Cell(Compression/ non-compression) 5*LTE5MHz+UMTS 1*Cell 4*LTE5MHz+UMTS 2*Cell 3*LTE5MHz+UMTS 3*Cell 2*LTE5MHz+UMTS 4*Cell 0*LTE5MHz+UMTS 6*Cell

0*LTE20MHz+UMTS 13*Cell 8*LTE10MHz+UMTS 0*Cell(Non-compression +10M only) 6*LTE10MHz+UMTS 0*Cell(Compression/ noncompression with different LTE bandwidths) 5*LTE10MHz+UMTS 3*Cell 4*LTE10MHz+UMTS 5*Cell 3*LTE10MHz+UMTS 7*Cell 2*LTE10MHz+UMTS 9*Cell 1*LTE10MHz+UMTS 11*Cell 0*LTE10MHz+UMTS 13*Cell 16*LTE5MHz+UMTS 0*Cell(Non-compression only) 12*LTE5MHz+UMTS 0*Cell(Compression/ noncompression) 11*LTE5MHz+UMTS 1*Cell 10*LTE5MHz+UMTS 2*Cell

Issue 02 (2016-03-31)


41








Issue 02 (2016-03-31)


42



NOTE

l The converging capabilities of a CPRI link or a board and the CPRI link rate refer to those of the converging party. l In the LampSite solution, the CPRI line rate of 4.9 Gbit/s or 9.8 Gbit/s is recommended. l The capabilities of the converging board cannot exceed the maximum capacity specifications of a site. For the maximum capacity specifications of a site, see Product Specifications > Technical Specifications of the BBU3900 > Capacity Specifications in DBS3900 LampSite Technical Description. l Converging capabilities in Table 6-2 apply to common cells. For the impact of different features on cell capacity, see the corresponding feature parameter description. l Table 6-2 lists the number of UMTS cells supported when the antenna capability is 1T2R. l Table 6-2 lists the number of LTE 20 MHz cells supported when the following configurations are applied: 2T2R antenna configuration, 20 MHz cell bandwidth, and CPRI bandwidth in noncompression only mode or mode coexistence of non-compression and 2:1 compression. Unless otherwise stated for the LTE 20 MHz cells, non-compression coexists with 2:1 compression. If the CPRI line rate of the WBBPf/LBBPd board is 9.8 Gbit/s, mode coexistence of non-compression and compression is not supported, no matter whether the base station works in separate-MPT scenarios or co-MPT scenarios; in this situation, data in the table is in non-compression only mode. The UBBPd/e board is free from this restriction. l Table 6-2 lists the number of LTE 10 MHz cells supported when the following configurations are applied: 2T2R antenna configuration, 10 MHz cell bandwidth, and CPRI bandwidth in noncompression only mode or mode coexistence of non-compression and 3:2 compression. Unless otherwise stated for the LTE 10 MHz cells, non-compression coexists with 3:2 compression. If the CPRI line rate of the WBBPf/LBBPd board is 9.8 Gbit/s, mode coexistence of non-compression and compression is not supported, no matter whether the base station works in separate-MPT scenarios or co-MPT scenarios; in this situation, data in the table is in non-compression only mode. The UBBPd/e board is free from this restriction. l Table 6-2 lists the number of LTE 5 MHz cells supported when the following configurations are applied: 2T2R antenna configuration, 5 MHz cell bandwidth, and CPRI bandwidth in noncompression only mode or mode coexistence of non-compression and 3:2 compression. Unless otherwise stated for the LTE 5 MHz cells, non-compression coexists with 3:2 compression. If the CPRI line rate of the WBBPf/LBBPd board is 9.8 Gbit/s, mode coexistence of non-compression and compression is not supported, no matter whether the base station works in separate-MPT scenarios or co-MPT scenarios; in this situation, data in the table is in non-compression only mode. The UBBPd/e board is free from this restriction. l In non-compression only mode or mode coexistence of non-compression and compression for an LTE network, the LBBPd board does not support CPRI extension mode. l LTE in Table 6-2 supports TDD, FDD, and FDD+TDD. Note that LTE TDD 5 MHz does not support bandwidth compression but LTE FDD 5 MHz supports 3:2 bandwidth compression. Bandwidth combinations in this table support LTE TDD 5 MHz. l "With different LTE bandwidths" in the table indicates that an LTE cell of a smaller bandwidth exists in addition to the bandwidths specified in a combination. In the combination of 6 x LTE 20 MHz + UMTS 0 x cell (with different LTE bandwidths), an LTE cell of 10 MHz or 5 MHz exists in addition to the 20 MHz bandwidth specified in the combination. Unless otherwise stated, a combination supports different LTE bandwidths. LampSite supports only LTE cells of 5 MHz or higher. Therefore, LTE 5 MHz in the combinations does not include other bandwidths.

Capacity specifications for each mode with different configurations are calculated as follows: l

Issue 02 (2016-03-31)

UMTS –

The number of cells supported when the antenna capability is 1T1R is the same as that supported when the antenna capability is 2T2R.

–

The antenna capability is inversely proportional to the number of cells. For example, the number of cells supported when the antenna capability is 1T1R is twice that supported when the antenna capability is 2T2R. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

43


l

Issue 02 (2016-03-31)


LTE –

When LTE cells have the same antenna capability and CPRI line rate, the number of 15- and 20-MHz cells supported is the same.

–

When LTE cells have the same bandwidth, the number of cells supported by 1T2R and 2T2R antennas is the same.


44


7 Related Features

7

Related Features

Prerequisite Features None

Mutually Exclusive Features None

Impacted Features None

Issue 02 (2016-03-31)


45


8 Network Impact

8

Network Impact

8.1 System Capacity No impact.

8.2 Network Performance No impact.

8.3 Reliability CPRI MUX in Separate-MPT Scenarios CPRI MUX in separate-MPT scenarios has the following impacts on system reliability: l

Operations or exceptions on the converging party Circuit switched (CS) and packet switched (PS) services of the converged party will be interrupted if a CPRI port of the converging party becomes faulty or if any of the following operations is performed by the converging party: –

Software reset or power-off reset on the main control board or the converging board

–

Blocking, removing and then inserting the main control board or the converging board

–

Commissioning a CPRI port on the converging board

In general, the service interruption lasts less than 3 minutes. In the worst case, the service interruption does not exceed 5 minutes. l

Issue 02 (2016-03-31)

Operations or exceptions on the converged party –

Performing software reset on the main control board: The data rate of PS services of the converging party may be reduced for less than 3s and the longest duration of rate reduction does not exceed 10s. CS services remain normal in this situation.

–

Performing power-off reset, inserting and then removing the main control board: CS and PS services on the converging party will be interrupted for less than 1 minute in general. In the worst case, the service interruption does not exceed 3 minutes. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

46


8 Network Impact

CPRI MUX in Co-MPT Scenarios CPRI MUX in co-MPT scenarios has the following impacts on system reliability: l

CS and PS services of the converged party will be interrupted if a CPRI port of the converging party becomes faulty or if any of the following operations is performed by the converging party: –

Software reset or power-off reset on the converging board

–

Blocking, removing and then inserting the converging board

–

Commissioning a CPRI port on the converging board

In general, the service interruption lasts less than 3 minutes. In the worst case, the service interruption does not exceed 5 minutes. l

If the WBBPf converges data, cells on the converged party will become unavailable for less than 5 minutes when a UMTS application is deleted or reset.

l

If the LBBPd converges data, cells on the converged party will become unavailable for less than 5 minutes when an LTE application is deleted or reset.

l

When a UBBPd/e serves as the converging board, deleting or resetting the applications of the modes configured on this board does not affect the converged party.

l

Adding baseband resources to one mode on a UBBPd/e interrupts services of other modes on this UBBPd/e, but does not affect services of the converged party that communicates with this UBBPd/e through the BBU backplane. NOTE

The service interruption period does not include the time required for manual operations, such as blocking, removing, and inserting boards.

Issue 02 (2016-03-31)


47


9

9 Engineering Guidelines

Engineering Guidelines

This chapter describes how to implement the CPRI MUX feature.

Issue 02 (2016-03-31)


48



9.1 When to Use CPRI MUX You can enable the CPRI MUX feature in the following scenarios: l

Sites in which a single-mode base station is to be evolved into a multimode base station and the operator requires that the existing topology of fiber optic cables remain unchanged to reduce engineering costs

l

Sites in which a co-MPT dual-mode or multimode base station is to be deployed and the operator requires that costs of fiber optic cables be reduced

l

Sites whose coverage must be ensured through cascaded RF units, such as stadiums, subways, and high-speed railways

9.2 Required Information The following information must be collected before feature deployment: l

Names of baseband processing units that are to be used in CPRI MUX

l

Names of RF units that are to be used in CPRI MUX

l

Information about optical modules

l

Planned site capacity

9.3 Planning RF Planning N/A

Network Planning Perform network planning according to 4 CPRI MUX Topologies with BBU3900s Used in the LampSite Solution.

Hardware Planning When selecting boards and RF units that are to be used in the CPRI MUX feature, you must consider the application scenarios and constraints provided in 3 Dependencies on BBU Boards and RF Units and 4 CPRI MUX Topologies with BBU3900s Used in the LampSite Solution.

NOTICE The CPRI link rates of baseband processing units/interface boards, optical modules, and RF units must match each other and meet the specifications in 6 Specifications of the CPRI MUX Feature.

Issue 02 (2016-03-31)


49



9.4 Deployment 9.4.1 Requirements Hardware RF units have been installed. Cables between RF units and BBUs have been connected as required by the CPRI MUX feature. For detailed installation procedures, see the corresponding Base Station Installation Guide and Site Maintenance Guide of the base stations. NOTE

If CPRI MUX is to be deployed in a site where a single-mode base station is to be evolved into a multimode base station, the hardware configuration must meet the requirements of CPRI MUX. Otherwise, replace the hardware.

License None

9.4.2 Data Preparation l

l

Issue 02 (2016-03-31)

The following table describes the parameters related to the RRUCHAIN MO for configuring the RHUB chain. Parameter Name

Parameter ID

Remarks

Data Source

Topo Type

TT

Set this parameter to CHAIN.

Network plan (negotiation not required)

Backup Mode

BM

Set this parameter to COLD.


The following table describes the parameters related to the RHUB MO for configuring the RHUB. Parameter Name

Parameter ID

Remarks

Data Source

RHUB Chain No.

RCN

Set this parameter to the number of the RHUB chain onsite.



50


l


Parameter Name

Parameter ID

Remarks

Data Source

RHUB Position

PS

This parameter specifies the position of an RHUB on an RHUB chain or ring. For example, set this parameter to 0 for the firstlevel RHUB and 1 for the second-level RHUB.


The following table describes the parameters related to the RRUCHAIN MO for configuring the pRRU chain. Parameter Name

Parameter ID

Remarks

Data Source

Topo Type

TT

Set this parameter to CHAIN.


Backup Mode

BM

Set this parameter to COLD.


NOTE This parameter is required only when the RHUBs and pRRUs work in branch chain (single-link) topology.

l

Issue 02 (2016-03-31)

The following table describes the parameters related to the RRU MO for configuring the pRRU. Parameter Name

Parameter ID

Remarks

Data Source

RRU Chain No.

RCN

Set this parameter to the number of the pRRU chain onsite.


RRU Position

PS

Set this parameter to 0.


RRU type

RT

Set this parameter to MPMU.


RRU Topo Position

TP

Set this parameter to BRANCH.



51



Parameter Name

Parameter ID

Remarks

Data Source

RF Unit Working Mode

RS

l In Branch Chain (Single-Link) Topology, set this parameter to UO(UMTS_ONLY), TDL(LTE_TDD), LO(LTE_FDD), or UL(UMTS_LTE).


l In Branch Load Sharing Topology, set this parameter to TDL(LTE_TDD), LO(LTE_FDD), or UL(UMTS_LTE).

CPRI MUX in Separate-MPT Scenarios Multimode RF units that work in multiple modes must follow the following configuration rules: l

RF units are configured and monitored by each mode.

l

RF units working in the same mode must have the same configuration. Otherwise, ALM-26274 Inter-System Board Object Configuration Conflict will be reported.

l

Table 9-1 lists parameters that must have the same configuration when CPRI MUX is deployed in separate-MPT scenarios.

Table 9-1 Configuration of common parameters Parameter Name on the UMTS/LTE Side

Parameter ID on the UMTS/LTE Side

Topo Type

TT

Cabinet No.

CN

Subrack No.

SRN

Slot No.

SN

RRU Type

RT

RRU Work Standard

RS

The RHUB/pRRU configuration of the converged party takes effect only after RHUB/pRRUs of the converging party have been configured. Before activating CPRI MUX, configure the RRUCHAIN MO on the converged party (UMTS or LTE). The key parameters are listed in Table 9-2. Issue 02 (2016-03-31)


52



Table 9-2 Parameters to be configured on the converged party Parameter Name

Parameter ID

Remarks (Configuration Principle for Different Scenarios)

Data Source

Access Type

AT

Set this parameter to PEERPORT.

Engineering Design

Head Cabinet No.

HCN

Engineering Design

Head Subrack No.

HSRN

Head Slot No.

HSN

Set these parameters to the cabinet number, subrack number, slot number, and optical port number of the CPRI port on the baseband board of the peer end, respectively.

Head Port No.

HPN

Local Slot No.

LSN

Engineering Design Engineering Design Engineering Design

If a BBU3900 is used, the slot number for the converged board does not need to be configured. In this case, set this parameter to 255.

Equipment Planning

If a BBU3910 is used and CPRI MUX works in UMTS/LTE separate-MPT scenarios, set this parameter to the slot number for the converged board.

CPRI MUX in Co-MPT Scenarios In co-MPT scenarios, if the networking meets the requirements in 4.1.1 Constraints, CPRI MUX is supported by default. Activating this feature does not need software configurations. NOTE

When CPRI MUX is used in UMTS+LTE co-MPT scenarios where the LBBPd or WBBPf provides 9.8 Gbit/s CPRI optical ports, run the ADD RRUCHAIN command to set the CPRI line rate to 4.9 Gbit/s. In co-MPT scenarios, the LBBPd board does not support CPRI extension mode.

Issue 02 (2016-03-31)


53



9.4.3 Activation Using MML Commands Step 1 On the converging party, run the ADD RRUCHAIN command to add an RHUB chain. Step 2 On the converging party, run the ADD RHUB command to add an RHUB to the RHUB chain. Step 3 On the converging party, run the ADD RRUCHAIN command to configure the pRRU chain. Step 4 On the converging party, run the ADD RRU command to add a pRRU to the pRRU chain. Step 5 On the converged party, run the ADD RRUCHAIN command for UMTS or LTE to add an RHUB chain. Step 6 On the converged party, run the ADD RHUB command to add an RHUB to the RHUB chain. Step 7 On the converged party, run the ADD RRUCHAIN command for UMTS or LTE to configure the pRRU chain. Step 8 On the converged party, run the ADD RRU command for UMTS or LTE to add a pRRU to the pRRU chain. ----End NOTE

Data configurations must be the same for RRUs on the converging party and converged party. For detailed parameter settings, see Table 9-1. When configuring the parameter AT in separate-MPT scenarios, set the local port for the converging party and the peer port for the converged party. For details, see Table 9-2. In separate-MPT scenarios where the CPRI line rate is 9.8 Gbit/s, if the bandwidth compression mode is changed for a cell on a CPRI link, all cells on the CPRI link must be deactivated, reconfigured, and then activated.

Using the CME to Perform Single Configuration Set parameters on the CME according to the operation sequence in Table 9-3. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide. Table 9-3 Configuring parameters on the CME

Issue 02 (2016-03-31)

SN

MO

Parameter Name

Parameter ID

Notes

1

RRUCHAIN

Chain No.

RCN

Topo Type

TT

Access Type

AT

Add an RRU chain on the converging party side.

Head Cabinet No.

HCN

Head Subrack No.

HSRN

Head Slot No.

HSN


54


SN

2

3

4

5

6

Issue 02 (2016-03-31)

MO

RHUB

RRUCHAIN

RRU

RRUCHAIN

RHUB


Parameter Name

Parameter ID

Head Port No.

HPN

Cabinet No.

CN

Subrack No.

SRN

Slot No.

SN

RRU Chain No.

RCN

RRU Position

PS

RHUB Name

RN

Chain No.

RCN

Topo Type

TT

Access Type

AT

Head Cabinet No.

HCN

Head Subrack No.

HSRN

Head Slot No.

HSN

Head Port No.

HPN

Cabinet No.

CN

Subrack No.

SRN

Slot No.

SN

RRU Chain No.

RCN

RRU Type

RT


RS

Chain No.

RCN

Topo Type

TT

Access Type

AT

Head Cabinet No.

HCN

Head Subrack No.

HSRN

Head Slot No.

HSN

Head Port No.

HPN

Local Slot No.

LSN

Cabinet No.

CN


Notes

Add an RHUB to the RRU chain on the converging party side.

Add an RRU chain on the converging party side.

Add a pRRU to the RRU chain on the converging party side.

Add an RRU chain on the converged party side for UMTS/ LTE.

Add an RHUB to the RRU

55


SN

MO

7

RRUCHAIN

8

RRU


Parameter Name

Parameter ID

Notes

Subrack No.

SRN

Slot No.

SN

chain on the converged party side.

RRU Chain No.

RCN

RRU Position

PS

RHUB Name

RN

Chain No.

RCN

Topo Type

TT

Access Type

AT

Head Cabinet No.

HCN

Head Subrack No.

HSRN

Head Slot No.

HSN

Head Port No.

HPN

Local Slot No.

LSN

Cabinet No.

CN

Subrack No.

SRN

Slot No.

SN

RRU Chain No.

RCN

RRU Type

RT


RS

Add an RRU chain on the converged party side.

Add a pRRU to the RRU chain on the converged party side.

Using the CME to Perform Batch Modification This feature does not support batch modification using the CME.

9.4.4 Activation Observation After the configured data is activated, check whether RF unit-related alarms are reported on the Alarm/Event tab page of the RNC LMT, and eNodeB LMT. For details about RF unitrelated alarms, see 9.7.1 Related Alarms. Check whether the status of pRRUs is normal. l

Check whether the status of pRRUs is normal. –

Issue 02 (2016-03-31)

Separate-MPT scenarios Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

56



On the NodeB LMT or U2000, run the DSP BRD command to check whether RF units function properly. On the eNodeB LMT or U2000, run the DSP BRD command to check whether RF units function properly. –

Co-MPT scenarios On the BTS3900 LMT or U2000, run the DSP BRD command to check whether RF units function properly.

l

Check whether the line rate of the converging port is the same as planned. –

Separate-MPT scenarios On the LMT or U2000 of the converging party of a 3900 series base station, run the DSP CPRIPORT command to check whether the line rate of the converging port is the same as planned.

–

Co-MPT scenarios Run the DSP CPRIPORT command to check whether the line rate of the converging port is the same as planned.

9.4.5 Deactivation This feature does not need to be deactivated.

9.4.6 Reconfiguration Reconfiguration in the UL dual-mode branch chain (single-link) topology and UL dual-mode branch load sharing topology includes the following operations: l

Adding an RHUB to an RHUB chain

l

Adding a pRRU to an RHUB

l

Removing an RHUB from an RHUB chain

l

Removing a pRRU from an RHUB

For details about these operations, navigate to Engineering Guidelines (NodeB) > Deployment > Reconfiguration or Engineering Guidelines (eNodeB) > Deployment > Reconfiguration in RF Unit and Topology Management Feature Parameter Description.

9.5 Performance Monitoring N/A

9.6 Parameter Optimization N/A

9.7 Troubleshooting

Issue 02 (2016-03-31)


57



9.7.1 Related Alarms Table 9-4 lists alarms related to the CPRI MUX feature. For detailed troubleshooting operations, see 3900 Series Multimode Base Station Alarm Reference. Table 9-4 CPRI MUX-related alarms Alarm ID

Alarm Name

ALM-26215

Inter-Board Service Link Failure

ALM-26235

RF Unit Maintenance Link Failure

ALM-26270

Inter-System Communication Failure

ALM-26272

Inter-System RF Unit Parameter Settings Conflict

ALM-26274

Inter-System Board Object Configuration Conflict

ALM-26277

Inter-System Control Rights Conflict

ALM-26278

RF Unit Working Mode and Board Capability Mismatch

ALM-28203

Local Cell Unusable

ALM-28206

Local Cell Capability Decline

ALM-29240

Cell Unavailable

ALM-29243

Cell Capability Degraded

NOTE

In separate-MPT scenarios, if a UMTS cell fails to be activated and EVT-28200 Iub Common Procedure Failure Indication is reported, check whether the UMTS+LTE cell configurations exceed the specifications of a single Ethernet cable. If so, modify the UMTS+LTE cell configurations. If not, run the BLK CPRIPORT command to block the CPRI_E port and then the UBL CPRIPORT command to unblock the CPRI_E port.

9.7.2 MML Commands for Maintenance In separate-MPT scenarios, the converging and converged parties have their own O&M platforms. In co-MPT scenarios, the converging and converged parties share the same O&M platform. Table 9-5 lists MML commands for maintenance. NOTE

After CPRI MUX is implemented, alarms will be reported if any exceptions occur. Clear the alarms according to the alarm reference.

Issue 02 (2016-03-31)


58



Table 9-5 MML commands for maintenance MML Command

Application Scenario

Support by the Converging Party

Support by the Converged Party (Only in SeparateMPT Scenarios)

DSP RRUCHAIN

Use this command to query:

Fully supported

Fully supported

l Number of pRRUs/ RHUBs carried on an RRU chain or ring over an optical port on the converging party l Number of RHUB cascading levels. DSP RRUCHAINPH YTOPO

Use this command to query information about the pRRUs/RHUBs connected to the CPRI port.

Fully supported

Fully supported

DSP CPRIPORT


Fully supported

Partially supported: Use this command to query:

l Real-time data rates and other information about the optical port on the panel of the converging party

l Data rates on the CPRI port l Aggregation state

l Whether the optical port is in the aggregation state DSP CPRILBR


Fully supported

l Current CPRI line rate of the specified chain or ring l Maximum CPRI line rate of the baseband processing board

Partially supported: Use this command to query the line rate on the head and the end of the CPRI chain or ring. Other information is displayed as NULL.

l Maximum CPRI line rate of each RHUB on a chain or ring

Issue 02 (2016-03-31)


59


MML Command

Application Scenario

Support by the Converging Party

Support by the Converged Party (Only in SeparateMPT Scenarios)

STR CPRILBRNEG

Use this command to start negotiation of the line rate on the optical port on the panel. Run this command if the RHUB chain cannot be set up or the chain cannot operate at the maximum line rate due to changes in parameter settings of the RHUB chain. Executing this command causes link disconnection, interrupting services.

Supported

Not supported

MOD RRUCHAIN

Use this command to set breakpoints on an RHUB chain.

Supported

Not supported

L: DSP CELL

Use this command to query the cell status. Cell setup fails and cell capability degrades when CPRI bandwidth is insufficient.

Supported

Supported

U: DSP ULOCELL

Issue 02 (2016-03-31)



60


10 Parameters

10

Parameters

Table 10-1 Parameters MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

RRUCH AIN

AT

ADD RRUCH AIN

None

None

Meaning: Indicates the access type of the board on an RRU chain/ring. When Access Type is set to LOCALPORT(local port), the BBP connects to the board on an RRU chain/ring through the CPRI port. When Access Type is set to PEERPORT(peer port), the local BBP connects to the peer BBP through the IDX2 port on the backplane and the peer BBP connects to a board on an RRU chain/ring.

MOD RRUCH AIN LST RRUCH AIN

GUI Value Range: LOCALPORT(local port), PEERPORT(peer port) Unit: None Actual Value Range: LOCALPORT, PEERPORT Default Value: LOCALPORT(local port)

Issue 02 (2016-03-31)


61


11 Counters

11

Counters

There are no specific counters associated with this feature.

Issue 02 (2016-03-31)


62


12 Glossary

12

Glossary

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

Issue 02 (2016-03-31)


63


13

13 Reference Documents

Reference Documents

1.

3900 Series Base Station Technical Description

2.

3900 Series Multimode Base Station Alarm Reference

3.

3900 series base station installation guide package

4.

NodeB MML Command Reference

5.

eNodeB MML Command Reference

6.

RF Unit and Topology Management

7.

3900 series base station site maintenance guide package

Issue 02 (2016-03-31)


64

CPRI MUX (LampSite)(SRAN11.1_02)

Recommend Documents