Multi-BBU Interconnection(SRAN9.0_Draft A).pdf

SingleRAN

Multi-BBU Interconnection Feature Parameter Description Issue

Draft A

Date

2014-01-20

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. 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 mentioned in this document are the property of of their respective respective holders. 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 document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, 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 recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue Draft A (2014-01-20)

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

i

Copyright © Huawei Technologies Co., Ltd. 2014. 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 mentioned in this document are the property of of their respective respective holders. 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 document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, 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 recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]



i

SingleRAN Multi-BBU Interconnection Feature Parameter Description

Contents

Contents 1 About This This Document......................... Document.......................................................................... .........................................................................................1 ........................................1 1.1 Scope..............................................................................................................................................................................1 Scope....... .......................................................................................................................................................................1 1.2 Intended Audience..........................................................................................................................................................1 1.3 Change History...............................................................................................................................................................1 H istory...............................................................................................................................................................1

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

3 Multi-BBU Interconnection Modes........ Modes.............................. ............................................ ............................................ ........................................4 ..................4 3.1 Introduction....................................................................................................................................................................4 3.2 Interconnection Interconne ction Between BBUs and a USU...................................................................................................................6 3.3 Interconnection Interconne ction Between BBUs and Two Levels of USUs..........................................................................................11

4 Clock Synchronization Synchronization Solutions............... Solutions.......................................... ...................................................... ...................................................16 ........................16 4.1 Solution 1......................................................................................................................................................................17 1 ......................................................................................................................................................................17 4.2 Solution 2......................................................................................................................................................................17 2 ......................................................................................................................................................................17 4.3 Solution 3......................................................................................................................................................................18 3 ......................................................................................................................................................................18

5 Related Features.......... Features...................................... ........................................................ ........................................................ ........................................................ .............................20 .20 6 Network Impact....................... Impact.................................................................... ........................................................................................... .......................................................21 .........21 6.1 System Capacity...........................................................................................................................................................21 6.2 Network Performance...................................................................................................................................................21 P erformance...................................................................................................................................................21

7 Engineering Guidelines........................... Guidelines................................................................................ ..................................................................................22 .............................22 7.1 When to Use Multi-BBU Interconnection....................................................................................................................22 7.2 Required Information...................................................................................................................................................22 I nformation...................................................................................................................................................22 7.3 Planning........................................................................................................................................................................22 Planning........................................................................................................................................................................22 7.3.1 BBU and an d USU Installation Position and USU Hardware Planning..........................................................................22 7.3.2 Transmission Transmission Mode Planning....................................................................................................................................23 7.4 Deployment..................................................................................................................................................................23 Deployment..................................................................................................................................................................23 7.4.1 Process.......................................................................................................................................................................23 7.4.2 Requirements.............................................................................................................................................................23 7.4.3 Data Preparation........................................................................................................................................................24 7.4.4 Initial Configuration..................................................................................................................................................27 Issue Draft A (2014-01-20)


ii


Contents

7.4.5 Activation Observation..............................................................................................................................................30 7.4.6 Reconfiguration.........................................................................................................................................................31 7.4.7 MML Command Examples.......................................................................................................................................35 7.5 Parameter Optimization................................................................................................................................................36 7.6 Troubleshooting............................................................................................................................................................36

8 Parameters....... Parameters..................................... ............................................................ ............................................................ ............................................................ ....................................38 ......38 9 Counters....................... Counters............................................................................... ............................................................................................................... .........................................................39 ..39 10 Glossary.......... Glossary....................................... ........................................................... ............................................................ ............................................................ ....................................40 ......40 11 Reference Documents........... Documents................................................ .......................................................................... ...............................................................41 ..........................41



iii


1 About This Document

1

About This Document

1.1 Scope This document describes the multi-BBU interconnection feature, including its technical principles, related features, network impact, and engineering guidelines. 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.

1.2 Intended Audience This document is intended for personnel who: l l

Need to understand the features described herein 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, which are defined as follows: l

Feature change Changes in features of a specific product version

l

Editorial change Changes in wording or addition of information that was not described in the earlier version

Draft A (2013-12-10) This document is created for SRAN9.0. Compared with Issue 02 (2013-10-15) of SRAN8.1, Draft A (2013-12-10) of SRAN9.0 includes the following changes. Issue Draft A (2014-01-20)


1


1 About This Document

Change Type

Change Description

Parameter Change

Feature change

Added the following functions:

None

l

l

Editorial change


Locking of universal switching unit (USU) clocks. For details, see 7.4.4 Initial Configuration. GPS clock source sharing and interconnection between BBUs and two levels of USUs for LTE FDD. For details, see 3 Multi-BBU Interconnection Modes.

l

Interconnection between BBU3910s and a USU.

l

Added 4 Clock Synchronization Solutions.

l

Reorganized 3.2 Interconnection Between BBUs and a USU and 3.3 Interconnection Between BBUs and Two Levels of USUs, and added figures of cable connections between BBUs and USUs to these two sections.

l

Revised the descriptions in this document.


None

2


2 Overview

2

Overview

2.1 Introduction Multi-BBU interconnection allows two or more BBUs to communicate with each other and process services by connecting the BBUs and USUs. BBUs and USUs are connected using the following types of cables: l

Infrastructure interconnection cable This type of cable connects the main control board in a BBU and the universal interconnection infrastructure unit (UCIU) in a USU to transmit control information about the topology, clock, heartbeat, and inter-cell link setup and release.

l

Baseband interconnection cable This type of cable connects a baseband processing unit (BBP) in a BBU and a universal inter-connection extension unit (UCXU) in a USU to transmit cell coordination information.

2.2 Benefits Multi-BBU interconnection provides the following benefits: l

Helps achieve coordination between inter-BBU cells when features, such as WRFD-151207 Uplink CoMP (Joint Reception) based on Coordinated BBU, LAOFD-070214 UL CoMP based on Coordinated BBU, and LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU), are enabled.

l

Reduces the number of required GPS or RGPS antennas because interconnected BBUs can share GPS or RGPS clock sources.



3


3 Multi-BBU Interconnection Modes

3

Multi-BBU Interconnection Modes

3.1 Introduction NOTE

In eRAN TDD 7.0, USU3900s are used. In this document, USU refers to USU3900.

Table 3-1 describes multi-BBU interconnection modes.



4



Table 3-1 Multi-BBU interconnection modes

Mode Intercon nection between BBUs and a USU

Purpose

Number of USUs

Number of BBUs

1

A maximu m of 5

To support the use of TDLOFD-001080 Inter-BBU SFN or TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA in the LTE TDD system for cell coordination

3

A maximu m of 10

To support the use of LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU in the LTE FDD system for cell coordination

3 or 4

A maximu m of 15

To share the GPS clock source between BBUs in the LTE FDD or TDD system

3 to 6

A maximu m of 25

To share the RGPS clock source between BBUs in the LTE TDD system

3 to 6

A maximu m of 25

l

To support the use of the following features for cell coordination:

– WRFD-151207 Uplink CoMP (Joint Reception) based on Coordinated BBU in the UMTS system

– LAOFD-070214 UL CoMP based on Coordinated BBU, LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU, or LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB) in the LTE FDD system

– TDLOFD-001080 Inter-BBU SFN or TDLOFD-001082 Inter-BBU Adaptive SFN/ SDMA in the LTE TDD system l

To share the GPS clock source between BBUs in the LTE FDD or TDD system

l

To share the RGPS clock source between BBUs in the LTE TDD system NOTE RGPS clock source sharing requires that RRUs provide RGPS antenna ports. Currently, only some RRU models (such as RRU3252 and RRU3256) in the LTE TDD system provide RGPS antenna ports.

Intercon nection between BBUs and two levels of USUs

NOTE RGPS clock source sharing requires that RRUs provide RGPS antenna ports. Currently, only some RRU models (such as RRU3252 and RRU3256) in the LTE TDD system provide RGPS antenna ports.

After BBUs are interconnected, each BBU and USU function as an independent network element (NE) in the radio access network.



5



3.2 Interconnection Between BBUs and a USU Cable Connections NOTE

The number of BBPs shown in the following figures is used as an example. The number of BBPs to be installed depends on service requirements. BBPs refer to LBBPd or UBBPd boards. LBBP is short for LTE baseband process unit, and UBBP is short for universal baseband process unit.

Figure 3-1 shows the interconnection between BBUs and a USU for cell coordination. Figure 3-1 Interconnection between BBUs and a USU (1)



6



NOTE

SMPT: switch main processing & transmission unit UCIU: universal inter-connection infrastructure unit UCXU: universal inter-connection extension unit UMPT: universal main processing and transmission unit UPEU: universal power and environment interface unit

Two types of clock sources are available in multi-BBU interconnection: GPS clock source connected to a BBU, and RGPS clock source connected to an RRU. Figure 3-2 and Figure 3-3 show multi-BBU interconnection for GPS and RGPS clock source sharing, respectively. Clock source sharing requires only i nfrastructure interconnection cables between the BBUs and USU. Figure 3-2 Interconnection between BBUs and a USU (2)



7



Figure 3-3 Interconnection between BBUs and a USU (3)

BBUs can share a maximum of two clock sources, which can be any of the following combinations: GPS+GPS, RGPS+RGPS, and GPS+RGPS. Figure 3-4 shows the interconnection between BBUs and a USU when the BBUs share one GPS clock source and one RGPS clock source.



8



Figure 3-4 Interconnection between BBUs and a USU (4)

When one of interconnected BBUs is configured with a clock source (such as BBU4 in Figure 3-2 and Figure 3-3), these BBUs can share the clock source as follows: 1.

BBU4 transmits clock signals to the USU.

2.

The USU transmits the signals to other connected BBUs.

Cable Connection Principles The cable connections are as follows: l

An infrastructure interconnection cable connects the cascading interface (CI) port on the UMPT in a BBU to one of ports M0 to M4/S1 on the UCIU in the USU.

l

A baseband interconnection cable connects the high speed extension interface (HEI) port on the BBP in a BBU to one of ports M0 to M4/S1 on a UCXU in the USU.

l

An infrastructure interconnection cable functions as a logical control link. On the control link between a BBU and the USU, the USU port is the upstream port of the BBU port by default. NOTE

The M0, M1, M2, M3, and M4/S1 ports are prioritized in descending order.



9



Application Scenarios Table 3-2 lists the application scenarios for the interconnection between BBUs and a USU. Table 3-2 Application scenarios for the interconnection between BBUs and a USU

Number of BBPs in a BBU Connected to the USU

Position of an LTE BBP in a BBU

Position of a UMTS BBP in a BBU

Position of a UCXU in the USU

1

Slot 3

Slot 3

Slot 3

2

Slots 2 and 3

Slots 2 and 3

Slots 2 and 3

3

Slots 1 to 3

Not supported

Slots 1 to 3

4

Slots 0 to 3

Not supported

Slots 0 to 3

l

LTE: Slots 0 to 3 for BBPs are prioritized in ascending order. A BBP can be installed i n slot 4 or 5 but cannot be connected to the USU.

l

UMTS: Slots 2 and 3 for BBPs are prioritized in ascending order. A BBP can be installed in slot 0, 1, 4, or 5 but cannot be connected to the USU.

Restrictions Restrictions on the interconnection between BBUs and a USU are as follows: l

Two to five BBUs can be connected to the USU.

l

The USU can house a maximum of four UCXUs and one UCIU. The UCIU is always installed in slot 5.

l

The number of UCXUs to be configured depends on the number of BBPs in a BBU to be connected to the UCXUs. For example, when three LBBPd boards in a BBU need to be connected to UCXUs, three UCXUs are required. In UMTS mode, a maximum of two UCXUs can be configured. In LTE mode, a maximum of four UCXUs can be configured.

l

The slot number of the UCXU connected to a BBP must be the same as the number of the slot in which the BBP is installed. For example, if the BBP is installed in slot 3 of a BBU, the UCXU connected to the BBP must also be installed in slot 3 of the USU.

l

Ports M0 to M4/S1 on the UCXU and UCIU must be arranged in the same order as that of BBU0 to BBU4. For example, the HEI port on the BBP installed in slot 2 of BBU1 must be connected to the M1 port on the UCXU installed in slot 2 of the USU, and the CI port on the UMPT in BBU1 must be connected to the M1 port on the UCIU.



10

SingleRAN Multi-BBU Interconnection Feature Parameter Description l


BBU3900s and BBU3910s cannot be connected to the same USU.

l

When a BBU3910 is connected to the USU, the UMPTb must function as the main control board and UBBPd boards must function as baseband processing units in this BBU3910.

l

When a BBU3900 is connected to the USU, the UMPTa or UMPTb must function as the main control board, and the UBBPd, LBBPd, or WBBPf4 must function as baseband processing units in this BBU3900.

l

UBBPd boards apply to the LTE FDD, LTE TDD, or UMTS system, LBBPd boards apply to the LTE FDD or LTE TDD system, and WBBPf4 boards apply only to the UMTS system. Among these three models of baseband processing units, only UBBPd boards support uplink CoMP.

l

WBBPf4 boards are connected to the USU through the quad small form-factor pluggable (QSFP) ports.

3.3 Interconnection Between BBUs and Two Levels of USUs Cable Connections NOTE

The number of BBPs shown in the following figures is used as an example. The number of BBPs to be installed depends on service requirements.

Figure 3-5 shows the interconnection between BBUs and two levels of USUs for cell coordination.



11



Figure 3-5 Interconnection between BBUs and two levels of USUs (1)

Two types of clock sources are available in multi-BBU interconnection: GPS clock source connected to a BBU, and RGPS clock source connected to an RRU. Figure 3-6 and Figure 3-7 show multi-BBU interconnection for GPS and RGPS clock source sharing, respectively. Clock source sharing requires only i nfrastructure interconnection cables between the BBUs and USUs. For details about infrastructure interconnection cable connections, see Figure 3-5.



12





BBUs can share a maximum of two clock sources, which can be any of the following combinations: GPS+GPS, RGPS+RGPS, and GPS+RGPS. When the BBUs share one GPS clock source and one RGPS clock source, BBUs and two levels of USUs are interconnected in the way shown in Figure 3-8.



13




When one of interconnected BBUs is configured with a clock source (such as BBU0 in Figure 3-6 or Figure 3-7), these BBUs can share the clock source as follows: 1.

BBU0 transmits clock signals to the first-level USU (USU0) connected to BBU0.

2.

USU0 transmits the signals to the second-level USU and the other connected BBUs.

3.

The second-level USU transmits the signals to the other first-level USUs.

4.

The other first-level USUs transmit the signals to their connected BBUs.

Cable Connection Principles The cable connections are as follows: l

An infrastructure interconnection cable connects the CI port on the SMPT of a first-level USU to one of ports M0 to M4/S1 on the UCIU of the second-level USU.

l

A baseband interconnection cable connects the S0 port on a UCXU of the first-level USU to one of ports M0 to M4/S1 on the UCXU of the second-level USU. NOTE

The M0, M1, M2, M3, and M4/S1 ports are prioritized in descending order.

Application Scenarios Table 3-3 lists the application scenarios for the interconnection between BBUs and two levels of USUs.



14



Table 3-3 Application scenarios for the interconnection between BBUs and two levels of USUs

Number of BBPs in a BBU Connected to a First-Level USU

Position of an LBBPd or LTE UBBPd in a BBU

Position of a UCXU in a FirstLevel USU

Position of a UCXU in the Second-Level USU

1

Slot 3

Slot 3

Slot 3

2

Slots 2 and 3

Slots 2 and 3

Slots 2 and 3

3

Slots 1 to 3

Slots 1 to 3

Slots 1 to 3

4

Slots 0 to 3

Slots 0 to 3

Slots 0 to 3

Restrictions Restrictions on the interconnection between BBUs and two levels of USUs are as follows: l

When BBUs share GPS or RGPS clock sources, a maximum of five first-level USUs can be connected to the second-level USU. When LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU is enabled in the LTE FDD system, a maximum of three first-level USUs can be connected to the second-level USU. When TDLOFD-001082 InterBBU Adaptive SFN/SDMA is enabled in the LTE TDD system, only two first-level USUs can be connected to the second-level USU.

l

The USU can house a maximum of four UCXUs and one UCIU. The UCIU is always installed in slot 5.

l

The slot number of the UCXU in the second-level USU must be the same as that of the UCXU in a first-level USU when the two UCXUs need to be connected. For example, the UCXU connected to the UCXU in slot 3 of a first-level USU must also be installed in slot 3 of the second-level USU.

l

The M0 and M1 ports on the UCXUs and UCIU of the second-level USU must be arranged in the same order as the first-level USUs. For example, the S0 port on the UCXU in slot 2 of USU0 must be connected to the M0 port on the UCXU installed in slot 2 of the second-level USU, and the CI port on the SMPT of USU0 must be connected to the M0 port on the UCIU of the second-level USU.

l l

BBU3900s and BBU3910s cannot be connected to the same USU. When a BBU3910 is connected to the USU, the UMPTb must function as the main control board and UBBPd boards must function as baseband processing units in this BBU3910.



15


4 Clock Synchronization Solutions

4

Clock Synchronization Solutions

After BBUs are interconnected, links on the user and control planes are automatically set up without manual configuration. To meet the clock synchronization requirements of cell coordination between interconnected BBUs, one of the following clock synchronization solutions can be used: l

Solution 1: Each BBU is configured with a clock source for time synchronization, and the USU clock can work in free running mode.

l

Solution 2: One BBU is configured with the GPS or RGPS clock source for synchronization and shares the clock source with other interconnected BBUs.

l

Solution 3: No clock source is available for time synchronization, BBUs lock the USU clock, and both BBUs and USUs lock external clock sources for frequency synchronization.



16



4.1 Solution 1 This solution applies to inter-BBU cell coordination only in the LTE FDD or TDD system. Figure 4-1 shows clock synchronization solution 1. Figure 4-1 Clock synchronization solution 1

4.2 Solution 2 This solution applies to inter-BBU cell coordination only in the LTE FDD or TDD system. Figure 4-2 shows clock synchronization solution 2.



17



Figure 4-2 Clock synchronization solution 2

4.3 Solution 3 This solution applies to inter-BBU cell coordination only in the LTE FDD or UMTS system, and is available only to interconnection between BBUs and a USU. Figure 4-3 shows clock synchronization solution 3. Figure 4-3 Clock synchronization solution 3



18



If the link between a BBU and USU is disconnected or the USU resets after clock synchronization between them has been established, the BBU must synchronize with the USU again and the services on the BBU are interrupted for 10 seconds to 1 minute.



19


5 Related Features

5

Related Features

Prerequisite Features None

Mutually Exclusive Features None

Impacted Features Multi-BBU interconnection must be enabled before enabling the following features: l

LTE TDD

– TDLOFD-001080 Inter-BBU SFN – TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA l

LTE FDD

– LAOFD-070214 UL CoMP based on Coordinated BBU – LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU – LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB) l

UMTS

– WRFD-151207 Uplink CoMP (Joint Reception) based on Coordinated BBU



20


6 Network Impact

6

Network Impact

6.1 System Capacity The multi-BBU interconnection feature has no impact on system capacity. However, other features, such as WRFD-151207 Uplink CoMP (Joint Reception) based on Coordinated BBU, LAOFD-070214 UL CoMP based on Coordinated BBU, and LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU, can increase system capacity after the multiBBU interconnection feature is enabled. This is because the multi-BBU interconnection feature facilitates inter-BBU cell coordination. For details about the impact of these features on system capacity, see the relevant feature parameter descriptions.

6.2 Network Performance The multi-BBU interconnection feature has no impact on network performance. However, other features, such as WRFD-151207 Uplink CoMP (Joint Reception) based on Coordinated BBU, LAOFD-070214 UL CoMP based on Coordinated BBU, and LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU, can enhance network performance after the multi-BBU interconnection feature is enabled. This is because the multi-BBU interconnection feature facilitates inter-BBU cell coordination. For details about the impact of these features on network performance, see the relevant feature parameter descriptions. If the link between a BBU and USU is disconnected or the USU resets after clock synchronization between them has been established, the BBU must synchronize with the USU again and the services on the BBU are interrupted for 10 seconds to 1 minute.



21


7 Engineering Guidelines

7

Engineering Guidelines

7.1 When to Use Multi-BBU Interconnection This feature applies to the following scenarios: Inter-BBU cell coordination is required.

l

For example, WRFD-151207 Uplink CoMP (Joint Reception) based on Coordinated BBU, LAOFD-070214 UL CoMP based on Coordinated BBU, LAOFD-001003 Carrier Aggregation for 2CC based on Coordinated BBU, LOFD-070208 Coordinated Scheduling based Power Control (Cloud BB), or TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA is enabled. l

Multiple BBUs share GPS or RGPS clock sources. In this scenario, USUs transmit GPS or RGPS clock signals between BBUs.

7.2 Required Information Collect the initial configurations of the BBUs and USUs involved in multi-BBU interconnection. For details, see 3900 Series Base Station Initial Configuration Guide and USU3900 Initial Configuration Guide.

7.3 Planning Before deploying the multi-BBU interconnection feature, plan the following items: l

BBU and USU installation positions and USU hardware

l

Transmission modes

7.3.1 BBU and USU Installation Position and USU Hardware Planning For details about BBU and USU installation positions in cabinets, see Base Station Cabinets and Subracks (Including the BBU Subrack) Configuration Feature Parameter Description. Issue Draft A (2014-01-20)


22



After the installation positions have been planned, plan USU hardware according to 3.2 Interconnection Between BBUs and a USU .

7.3.2 Transmission Mode Planning The multi-BBU interconnection feature has no additional requirements for the base station transmission mode. A USU must set up an operation and maintenance (O&M) channel with the operations support system (OSS) through the FE/GE0 or FE/GE1 port.

7.4 Deployment 7.4.1 Process Figure 7-1 shows the process for deploying the multi-BBU interconnection feature. Figure 7-1 Process

7.4.2 Requirements l

USUs must be installed to interconnect BBUs.

l

To use the multi-BBU interconnection feature, operators must purchase the licenses of this feature and load them onto USUs. The number of licenses to be purchased depends on the number of BBUs to be connected to USUs.



23



l

The UMPT must be installed in each BBU and connected to the UCIU by using an infrastructure interconnection cable. The LMPT or WMPT cannot function as the main control board in multi-BBU interconnection.

l

LBBPd, UBBPd, or WBBPf4 boards must be installed in each BBU and connected to UCXUs by using baseband interconnection cables. Other types of BBPs, such as t he LBBPc and WBBPd, cannot be connected to UCXUs.

l

The cable between a USU and a BBU must be equal to or shorter than 100 meters.

l

Interconnected BBUs must work in the same RAT, such as UMTS, LTE FDD, or LTE TDD.

l

The software versions of base stations and USUs must be compatible with those used in SRAN9.0.

7.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 not required): parameter values planned and set by the operator

l

Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment

l

User-defined: parameter values set by users

Required Data The following table describes the parameter that must be set in EQUIPMENT MOs to configure BBUs and USUs.

Paramete r Name

Paramet er ID

Setting Notes

Data Source

Open DU Interface ID

ODIID

If this parameter is set to 0, no open datalink interface Network (ODI) ID is configured and the base station cannot plan communicate with other base stations. In multi-BBU (negotiati interconnection scenarios, the parameter for each on not BBU and USU must be set to a unique value ranging required) from 1 to 254.

The following table describes the parameter that must be set in CASCADEPORT MOs to configure BBUs and USUs.



24



Paramete r Name

Paramet er ID

Setting Notes

Data Source

Switch

SW

The alarm generated on a port can be reported only after the port is enabled. Set this parameter to ON (On) when the port needs to be used.

Network plan (negotiati on not required)

Operators must plan IP addresses for each USU. For details about USU configuration, see USU3900 Initial Configuration Guide.

Scenario-specific Data Clock synchronization configurations on USUs and BBUs vary with RATs and service requirements. l

Clock synchronization solution 1 The following table describes the parameters that must be set in TASM MOs to configure the system clock.

Parameter Name

Paramete r ID

Setting Notes

Data Source

Clock Working Mode

MODE

Set this parameter to FREE(Free) for each USU and MANUAL(Manual) for each BBU.

Network plan (negotiatio n not required)

Selected Clock Source

CLKSRC

Set this parameter to GPS(GPS Clock) or IPCLK(IP Clock) for each BBU.


Clock CLKSYNC Set this parameter to TIME(TIME) for each Network Synchroniza MODE BBU. plan tion Mode (negotiatio n not required)

l




25



Parameter Name

Parameter ID

Setting Notes

Data Source

Cloud BB Clock Reference Source Flag

CLOUDSR C

Set this parameter to ENABLE Network (ENABLE) for the eNodeB configured plan with the GPS clock source. (negotiatio n not Set this parameter to DISABLE required) (DISABLE) for each eNodeBs receiving GPS clock signals.


CLKSRC

Set this parameter to GPS(GPS Clock) Network for the eNodeB configured with the GPS plan clock source. (negotiatio n not Set this parameter to INTERCLK required) (Inter Clock) for each eNodeBs receiving GPS clock signals.

CLKSYNC Clock Synchronizatio MODE n Mode

Set this parameter to TIME(TIME) for Network each BBU. plan (negotiatio n not required)

The following table describes the parameters that must be set in InterClk MOs to configure the shared clock source.

Parameter Name

Parameter ID

Setting Notes

Data Source

Interconnectio n Clock No.

LN

The default value is 0.


Priority

PRI

Set this parameter to the priority of the GPS or RGPS clock source on an eNodeB receiving GPS or RGPS clock signals. The value ranges from 1 to 4. The default value is 4, which indicates the lowest priority.


If the system clock working mode of this eNodeB is set to AUTO(Auto) , the eNodeB selects the clock source with the highest priority.

l




26


Parameter Name

Parameter ID


Setting Notes

Data Source

Clock Working MODE Mode

Set this parameter to MANUAL (Manual) for each USU.



CLKSRC

Set this parameter to IPCLK(IP Clock) or SYNCETH(SyncEth Clock) for each USU.


System Clock Source

SYSCLKSR C

Set this parameter to INTER_SYSCLK Network (Interconnection Clock) for each base plan station. (negotiatio n not required)

Clock Synchronizatio n Mode

CLKSYNC MODE

Set this parameter to FREQ(FREQ) on Network the BBU. plan (negotiatio n not required)

7.4.4 Initial Configuration Using the CME to Perform Batch Configuration for Newly Deployed Base Stations NOTE

Before starting the initial configuration for multi-BBU interconnection, configure the BBUs and USUs according to 3900 Series Base Station Initial Configuration Guide and USU3900 Initial Configuration Guide, respectively. Before performing batch configuration on the Configuration Management Express (CME), familiarize yourself with the batch configuration procedure in the "Initially Configuring USUs in Batches" section in USU3900 Initial Configuration Guide.

Enter the values of the parameters listed in Table 7-1 and Table 7-2 in a summary data file, which also contains other data for the new base stations to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see USU3900 Initial Configuration Guide and 3900 Series Base Station Initial Configuration Guide. 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 7-1 and Table 7-2 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.



27



Some MOs in Table 7-1 and Table 7-2 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 7-1 Multi-BBU interconnection parameters on BBUs

MO

Sheet in the Summary Data File

Parameter Group

EQUIPMENT

Equipment


This parameter has been set in the default template.

CASCADEPO RT

Cascade Port

Switch

This parameter must be customized in the template.

INTERCLK

InterClk

Interconnection Clock No.

These parameters must be customized in the template.

Priority

TASM

TASM

Remarks

Clock Working Mode

These parameters Selected Clock Source must be Cloud BB Clock Reference customized in Source Flag the template. Clock Synchronization Mode

Table 7-2 Multi-BBU interconnection parameters on USUs

MO


Parameter Group

EQUIPMENT

Equipment


This parameter has been set in the default template.

CASCADEPO RT

Cascade Port

Switch

This parameter must be customized in the template.



Remarks

28



MO


Parameter Group

TASM

TASM

Clock Working Mode

Remarks

These parameters Selected Clock Source must be Cloud BB Clock Reference customized in Source Flag the template. Clock Synchronization Mode

Using MML Commands Step 1 Configure each BBU by following the procedure for configuring a single base station using manmachine language (MML) commands. For details, see 3900 Series Base Station Initial Configuration Guide.

Step 2 Configure each USU according to the "Configuration for a Single USU" section in USU3900 Initial Configuration Guide.

Step 3 Run the SET EQUIPMENT command on each BBU and USU to specify ODI IDs. NOTE

The ODI ID for each BBU and USU must be unique. The setting of the Open DU Interface ID parameter takes effect only after the SMPT or UMPT resets. Therefore, a base station must be reset after the initial configuration of the base station is complete.

Step 4 Run the SET CASCADEPORT commands on each BBU and USU to enable the ports required for interconnection. NOTE

The alarm generated on an interconnection port can be reported only after the port is enabled. If you do not need to use an interconnection port, do not enable it. To query the number of an interconnection port, run the LST CASCADEPORT command. The number of the CI port on the UMPT is 8, and the number of the HEI port on a BBP is 6.

Step 5 Configure the clock source. NOTE

The clock synchronization requirements of inter-BBU cell coordination vary with the RAT. In the LTE FDD or TDD system, inter-BBU cell coordination requires phase synchronization between eNodeBs (that is, each eNodeB can obtain clock signals). In the UMTS system, NodeBs must lock the USU clock to maintain frame timing and frame synchronization between the BBUs and USUs because of CPRI frame transmission between the BBUs and USUs. l

Clock synchronization solution 1

– On each USU, run the SET CLKMODE command with Clock Working Mode set to FREE(Free) .

– On each eNodeB, run the SET CLKMODE command with Selected Clock Source set to GPS(GPS Clock) or IPCLK(IP Clock), and run the SET CLKSYNCMODE command with Clock Synchronization Mode set to TIME(TIME) . l




29



– On the eNodeB configured with the GPS or RGPS clock source, run the SET CLOUDSRC command with Cloud BB Clock Reference Source Flag set to ENABLE (ENABLE) , and run the SET CLKMODE command with Selected Clock Source set to GPS(GPS Clock).

– On each eNodeB receiving GPS or RGPS clock signals, run the ADD INTERCLK command to add a clock link, and run the SET CLKMODE command with Selected Clock Source set to INTERCLK(Inter Clock).

– On each eNodeB, run the SET CLKSYNCMODE command with Clock Synchronization Mode set to TIME(TIME) . l


– On each USU, run the SET CLKMODE command with Clock Working Mode set to MANUAL(Manual) and Selected Clock Source set to SYNCETH(SyncEth Clock) or IPCLK(IP Clock).

– On each NodeB or eNodeB, run the SET CLKSYNCMODE command with System Clock Source set to INTER_SYSCLK(Interconnection Clock) and Clock Synchronization Mode command set to FREQ(FREQ) , and run the SET CLKMODE command to specify an external clock source. ----End

7.4.5 Activation Observation Local Observation l

On a BBU, view the following indicators to check the status of the infrastructure and baseband interconnection cables:

– Indicator of the CI port on the UMPT: If the i ndicator is steady green, the infrastructure interconnection cable between the BBU and the USU is properly connected.

– Indicator of the HEI port on the BBP: If the indicator is steady green, the baseband interconnection cable between the BBU and the USU is properly connected. l

On a USU, view the following indicators to check the status of the infrastructure and baseband interconnection cables:

– Indicator of an M port on the UCIU: If the indicator is steady green, the infrastructure interconnection cable between the BBU and the first-level USU or between two levels of USUs is properly connected.

– Indicator of an M port on the UCXU: If the indicator is steady green, the baseband interconnection cable between the BBU and the first-level USU or between two levels of USUs is properly connected.

– Indicator of the CI port on the SMPT: If the indicator is steady green, the infrastructure interconnection cable between two levels of USUs is properly connected. If only one USU is configured, skip this check item.

– Indicator of the S0 port on the UCXU: If the indicator is steady green, the baseband interconnection cable between two levels of USUs is properly connected. If only one USU is configured, skip this check item.

Remote Observation 1.

Run the DSP INTERCONTOPO command on a USU to check the status of connections between the USU and BBUs:



30


l

2.


If the query results are consistent with the network plan, the cables between the USU and BBUs are properly connected. If the query results are not consistent with the network plan, reconnect the cables between the USU and BBUs.

Run the DSP CTRLLNKSTAT and DSP BBPLNKSTAT commands on the USU to check the status of links between the USU and BBUs: l

If the queried bit error rates (BERs) on these links are within the normal range, the links are working properly.

l

If the queried BERs on these links are outside the normal range, locate and rectify the fault.

7.4.6 Reconfiguration Network reconfiguration includes the following procedures: l

Adding BBUs only

l

Adding BBUs and USUs

Adding BBUs Only This section describes the reconfiguration procedure when the number of BBUs i ncreases from 2 to 4 and only one USU is configured. Figure 7-2 shows the hardware configurations before and after two BBUs are added. Figure 7-2 Hardware configurations before and after two BBUs are added

Preparing Hardware

Before reconfiguring data, obtain the devices listed in the following table.



31



Device

Quantity

BBU subrack

2

UMPT

2

BBP (LBBPd, UBBPd, or WBBPf4)

4

Infrastructure interconnection cable

2

Baseband interconnection cable

4

Small form-factor pluggable (SFP) optical module

4

QSFP optical module

8

Cables, such as the common public radio interface (CPRI) cable, transmission cable, clock cable, power cable, and monitoring cable

Based on the site plan

NOTE l

An infrastructure interconnection cable connects the CI port on a UMPT to an M port on the UCIU.

l

A baseband interconnection cable connects port HEI on a BBP to an M port on a UCXU.

l

An SFP optical module is inserted in the CI port on a UMPT or an M port on the UCIU.

l

A QSFP optical module is inserted in the HEI port on a BBP or an M port on a UCXU.

Installing Hardware

Step 1 Install UMPTs and BBPs in BBU2 and BBU3, and connect cables, such as CPRI cables, transmission cables, clock cables, power cables, and monitoring cables.

Step 2 Use infrastructure interconnection cables to connect the CI ports on the UMPTs to the M ports on the UCIU.

Step 3 Use baseband interconnection cables to connect the HEI ports on the BBPs to the M ports on UCXUs. NOTE

For details about the restrictions on the preceding cable connections, see Restrictions.

----End Reconfiguring Data

Step 1 Configure BBU2 and BBU3 according to 3900 Series Base Station Initial Configuration Guide.

Step 2 Run the SET EQUIPMENT commands on BBU2 and BBU3 to specify ODI IDs. NOTE

The setting of the ODIID parameter takes effect only after the SMPT or UMPT resets. Therefore, a base station must be reset after the initial configuration of the base station is complete.



32



Step 3 Run the SET CASCADEPORT commands on BBU2, BBU3, and the USU to enable the ports required for interconnection: l

On BBU2 and BBU3, enable the CI ports on the UMPTs and the HEI ports on the BBPs.

l

On the USU, enable the M2 and M3 ports on the UCXUs and UCIU. NOTE

The alarm generated on an interconnection port can be reported only after the port is enabled. If you do not need to use an interconnection port, do not enable it.

----End

Adding BBUs and USUs When 6 to 10 BBUs are interconnected, two levels of USUs are required. This section describes the reconfiguration procedure when the number of BBUs increases from 5 to 8 and the number of USUs increases from 1 to 3. Figure 7-3 shows the hardware configurations after three BBUs and two USUs are added. Figure 7-3 Hardware configurations after three BBUs and two USUs are added

For the hardware configurations before BBU and USU addition, see Figure 3-1. Preparing Hardware

Before reconfiguring data, obtain the devices listed in the following table. Issue Draft A (2014-01-20)


33



Device

Quantity

BBU subrack

3

USU subrack

2

UMPT

3

BBP (LBBPd, UBBPd, or WBBPf4)

6

SMPT

2

UCXU

4

UCIU

2

Infrastructure interconnection cable

5

Baseband interconnection cable

10

SFP optical module

10

QSFP optical module

20

Cables, such as the CPRI cable, transmission cable, clock cable, power cable, and monitoring cable

Based on the site plan

NOTE l

An infrastructure interconnection cable connects the CI port on a UMPT to an M port on the UCIU of a first-level USU or connects the CI port on the SMPT of a first-level USU to an M port on the UCIU of the second-level USU.

l

A baseband interconnection cable connects the HEI port on a BBP to an M port on a UCXU or connects the S0 port on a UCXU of a first-level USU to an M port on a UCXU of the second-level USU.

l

An SFP optical module is inserted in the CI port on a UMPT or SMPT or an M port on a UCIU.

l

A QSFP optical module is inserted in the HEI port on a BBP or an M port or the S0 port on a UCXU.

Installing Hardware

Step 1 Install UMPTs and BBPs in BBU5 to BBU7, and connect cables, such as CPRI cables, transmission cables, clock cables, power cables, and monitoring cables.

Step 2 Install SMPTs, UCXUs, and UCIUs in USU1 and USU2, and connect cables, such as transmission cables, power cables, and monitoring cables.

Step 3 Use infrastructure interconnection cables to connect the CI ports on the UMPTs to the M ports on the UCIU in USU1.

Step 4 Use baseband interconnection cables to connect the HEI ports on the BBPs to the M ports on UCXUs in USU1.

Step 5 Use infrastructure interconnection cables to connect the CI ports on the SMPTs in USU0 and USU1 to the M ports on the UCIU in USU2.

Step 6 Use baseband interconnection cables to connect the S0 ports on the UCXUs in USU0 and USU1 to the M ports on the UCXUs in USU2. Issue Draft A (2014-01-20)


34



NOTE

For details about the restrictions on the preceding cable connections, see Restrictions.

----End Reconfiguring Data

Step 1 Configure BBU5 to BBU7 according to 3900 Series Base Station Initial Configuration Guide. Step 2 Configure USU1 and USU2 according to the "Configuration for a Single USU" section in USU3900 Initial Configuration Guide.

Step 3 Run the SET EQUIPMENT commands on BBU5, BBU6, BBU7, USU0, and USU1 to specify ODI IDs. NOTE

The setting of the ODIID parameter takes effect only after the SMPT or UMPT resets. Therefore, a base station must be reset after the initial configuration of the base station is complete.

Step 4 Run the SET CASCADEPORT commands on BBU5, BBU6, BBU7, USU0, USU1, and USU2 to enable the ports required for interconnection: l

On BBU5 to BBU7, enable the CI ports on the UMPTs and the HEI ports on the BBPs.

l

On USU0, enable the CI port on the SMPT and the S ports on the UCXUs.

l

On USU1, enable the CI port on the SMPT, the M0, M1, M2, and S0 ports on the UCXUs, and the M0, M1, and M2 ports on the UCIU.

l

On USU2, enable the M0 and M1 ports on the UCXUs and UCIU. NOTE

The alarm generated on an interconnection port can be reported only after the port is enabled. If you do not need to use an interconnection port, do not enable it.

----End

7.4.7 MML Command Examples NOTE

The parameter settings in the following commands are used for reference only. Set the parameters based on network conditions. For the MML command examples of USU initial configuration, see the following section in USU3900 Initial Configuration Guide: Configuration for a Single USU > Typical Configuration Script

//Specifying the ODI ID for a BBU SET EQUIPMENT: ODIID=175; //Resetting the UMPT in slot 6 RST BRD: CN=0, SRN=0, SN=6; //Enabling the HEI port on the BBP in slot 3 SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON; //Enabling the CI port on the UMPT in slot 6 SET CASCADEPORT: CN=0, SRN=0, SN=6, PN=8, SW=ON; Issue Draft A (2014-01-20)


35



//Specifying the ODI ID for a USU SET EQUIPMENT: ODIID=125; //Resetting the SMPT in slot 6 RST BRD: CN=0, SRN=0, SN=6; //Enabling the M0 port on the UCXU in slot 3 SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=0, SW=ON; //Enabling the M0 port on the UCIU in slot 5 SET CASCADEPORT: CN=0, SRN=0, SN=5, PN=0, SW=ON; //Enabling the S0 port on the UCXU in slot 3 SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=5, SW=ON;

7.5 Parameter Optimization N/A

7.6 Troubleshooting Alarms related to multi-BBU interconnection are reported due to the following reasons: l

Two or more NEs involved in multi-BBU interconnection are configured with the same ODI ID.

l

An optical module for connecting a BBU and a USU is faulty or cannot be detected, data transmission or receiving fails on the optical port where the optical module is installed, or the optical port where the optical module is installed is faulty.

l

Cables are incorrectly connected between a BBU and a USU.

If an alarm listed in Table 7-3 or Table 7-4 is generated, clear the alarm by referring to the alarm handling suggestions in the alarm reference. Table 7-3 Alarms related to BBUs

Alarm ID

Alarm Name

26116

Inter-NE Address Conflict

26310

Inter-BBU Optical Module Fault

26311

Inter-BBU Optical Module Not in Position

26312

Inter-BBU Optical Module Receive Failure

26313

Inter-BBU Optical Module Transmit Failure

26314

Inter-BBU Port Failure

26315

Inter-BBU Port Connection Error



36



Table 7-4 Alarms related to USUs

Alarm ID

Alarm Name

26116

Inter-NE Address Conflict

27105

Interconnected Optical Module Fault

27106

Interconnected Optical Module Not Installed

27107

Interconnected Optical Module Receive Failure

27108

Interconnected Optical Module Transmit Failure

27109

Inter-Port Failure

27110

Inter-Port Connection Error



37


8 Parameters

8

Parameters

There are no specific parameters associated with this feature.



38


9 Counters

9

Counters

There are no specific counters associated with this feature.



39


10 Glossary

10

Glossary

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



40

Multi-BBU Interconnection(SRAN9.0_Draft A).pdf

Recommend Documents