3/5/24, 9:34 AM Building Blocks

Description 24/1551-LZA 701 6001/1-A46 Uen BS

Building Blocks
Contents

about:blank 1/268
3/5/24, 9:34 AM Building Blocks

1 Building Blocks
This section describes all building blocks used in radio configurations. For information on which building blocks are
supported for specific radio standards and specific RBS types, see the following sections:

– Multistandard and single standard: Radio Configurations for Multistandard and Single Standard Mixed Mode

– GSM: Radio Configurations for GSM

– WCDMA: Radio Configurations for WCDMA

– LTE: Radio Configurations for LTE

– CDMA: Radio Configurations for CDMA

– NR: Radio Configurations for NR

– ESS: Radio Configurations for ESS

– Massive IoT: Radio Configurations for Massive IoT

1.1 DBBs
Each DBB defines a unique way of combining DUs or Baseband units in one node with connections to radios.

DBBs are named as follows: DBB[X][Y]_[ZZ], where:

X Number of DUs or Baseband units

Y Number of CPRI links for DU interconnection

ZZ Number that represents the CPRI port configuration or a set of rules for how to configure the ports.

Example: DBB21_01

– Two DUs

– One CPRI link between DUs

– CPRI port configuration number 01

For RBBs with more than one CPRI connection, the ports in the RBB are used from top to bottom as seen in the block
diagrams in RBBs.

For DBBs with more than one CPRI connection to each sector, DU and Baseband ports are used in alphabetical order.

In configurations where DUW 30 is used, the ODW 30 digital unit can also be used.

In configurations where DUS 41 is used, the ODS 41 digital unit can also be used.

Each sector is denoted Sx, where x is the number of the sector. Cascaded configurations and ring configurations are
indicated by the use of a comma. For example, S1, S2, S3 indicates that the RBBs for sector 1, sector 2 and sector 3 are
cascaded and therefore connected to the DU using the same CPRI connection.

1.1.1 DBB10_xx
This section describes DBBs with one DU, DBB10_xx. For a description of DBB10_81, see DBB10_81. For a description of
DBB10_99, see DBB10_99.

about:blank 2/268
3/5/24, 9:34 AM Building Blocks
Figure 1 shows the DBB10_xx block diagram.

RI A

RI B

RI C

DU
RI D

RI E

RI F

Ge26679A

Figure 1 DBB10_xx Block Diagram

Table 1 lists the DBB10_xx variants and their connections between DUs and sectors.

Table 1 DBB10_xx
Connection Connection to Sector
from DU
Port DBB10_01 DBB10_02 DBB10_21 DBB10_22 DBB10_23 DBB10_44 DBB10_45 DBB10_50 DBB10_51 DBB10_52

S1, S2, S3, S1, S2, S3,

RI A S1 S1 S1, S2, S3 S1, S2 S1 S1 S1, S2, S3 S1, S2
S4, S5, S6 S4, S5, S6
S6, S5, S4,
RI B S2 S2 - S4, S5, S6 S3, S4 S1 S1 S4, S5, S6 S3, S4
S3, S2, S1
RI C S3 S3 - - S5, S6 S1 S1 - S3, S2, S1 S5, S6
RI D S1 S4 - - S1, S2 S2 S1 - S6, S5, S4 S2, S1
RI E S2 S5 - - S3, S4 S2 S2 - - S4, S3
RI F S3 S6 - - S5, S6 S2 S2 - - S6, S5

1.1.2 DBB10_81
This sections describes DBB10_81, which has support for DU, Baseband, Baseband R503 and Baseband P614.

For DU, Baseband, and software dependencies related to Baseband R503, see Fronthaul.

For DU, Baseband, and software dependencies related to Baseband P614, see Fronthaul.

Figure 2 shows an example of the DBB10_81 block diagram for DU and Baseband with six RI ports.

Figure 2 Example of DBB10_81 Block Diagram for DU and Baseband with Six RI Ports

The following rules apply to configurations with DBB10_81:

about:blank 3/268
3/5/24, 9:34 AM Building Blocks
– All available RI ports can be used for radio connections.

– Each RI port can connect to one radio or one cascade chain (up to four radios). For more information on CPRI
dependencies and cascading, see DBB10_81 Configurations

– Normally one RBB is only connected to one DU or Baseband.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

– All connected RBBs must not use more than the supported capacity of the specified DU or Baseband.

1.1.2.1 DBB10_81 Configurations

DBB10_81 configurations must follow the following connection rules:

– DBB10_81 is used for:

• CDMA, LTE FDD, CDMA + LTE FDD with DUL 20.

• CDMA, LTE FDD, LTE TDD, CDMA + LTE FDD, LTE FDD + LTE TDD node configurations with one DUS 31, DUS 41,
ODS 41.

• GSM, WCDMA, LTE FDD, LTE TDD, LTE FDD + LTE TDD, NR FDD, NR TDD, single and mixed mode Baseband node
configurations.

• LTE FDD with RBS 6501.

– Supports all RBBs supported in GSM, WCDMA, LTE and NR configurations.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– Baseband R503 used with a cascading chain is considered to be the first unit in the chain. These defined RBBs can
be connected to Baseband R503 and for the maximum number of units in the cascading chain (counting both radio
units and Baseband R503), see Fronthaul.

1.1.3 DBB10_99
This sections describes DBB10_99, used for GSM and WCDMA configurations.

Figure 3 shows the DBB10_99 block diagram.

RI A

RI B

RI C
DU

RI D

RI E

RI F

Ge26679A

Figure 3 DBB10_99 Block Diagram

The following rules apply to configurations with DBB10_99:

– DBB10_99 is used only for GSM and WCDMA.

– All available RI ports can be used for radio connections.

about:blank 4/268
3/5/24, 9:34 AM Building Blocks
– Each RI port can connect to one radio or one cascade chain (up to six radios). For more information on CPRI
dependencies and cascading, see DBB10_99 Configurations.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

– All connected RBBs must not use more than the supported capacity of the specific DU.

1.1.3.1 DBB10_99 Configurations

DBB10_99 configurations must follow the following connection rules:

– DBB10_99 is only used by GSM configurations with DUG 20 and WCDMA configurations with DUW 01, DUW 11,
DUW 20, DUW 30, DUW 31, DUW 41, RBS 6501, ODW 30.

– DBB10_99 can use one DU.

– DBB10_99 can use all available RI ports to connect to radios.

– Each RI port can connect to one radio or one cascaded radio chain which supports GSM and WCDMA configurations.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– DBB10_99 can support all RBBs, which support GSM and WCDMA single mode star and cascade configurations.

– DBB10_99 cannot support GSM with mixed mode radios or ring configurations.

1.1.4 DBB11_xx
This section describes DBBs with one DU and one IDL2 link to another DBB through a CPRI connection. For a description of
DBB11_99, see DBB11_99.

Figure 4 shows the DBB11_xx block diagram. Figure 5 shows an example of a DBB11_xx connected to another DBB.

RI A

RI B

RI C
DU

RI D

RI E

RI F

Ge26680A

Figure 4 DBB11_xx Block Diagram

about:blank 5/268
3/5/24, 9:34 AM Building Blocks

RI A

RI B

RI C

DU
DBB 11
RI D

RI E

RI F

RI A

RI B

RI C
DU

DBB 11
RI D

RI E

RI F
Ge26681A

Figure 5 Block Diagram for Two Interconnected DBB11_xx

Table 2 lists the DBB11_xx variants and their connections from DU to sectors and other DBBs.

Table 2 DBB11_xx
Connection Connection to Sector
from DU
Port DBB11_01 DBB11_02 DBB11_03 DBB11_04 DBB11_21 DBB11_22 DBB11_23 DBB11_24 DBB11_25 DBB11_26
S1, S2, S3, S1, S2, S3,
RI A S1 S1 S1 S1 S1, S2, S3 S1, S2 S1, S2, S3 S1, S2
S4, S5, S6 S4, S5, S6
S6, S5, S4,
RI B S2 S2 S1 S1 - S4, S5, S6 S3, S4 S4, S5, S6 S3, S4
S3, S2, S1
RI C S3 S3 S1 S1 - - S5, S6 - S3, S2, S1 S2, S1
RI D S4 S1 S2 S1 - - - - S6, S5, S4 S4, S3
RI E S5 S2 S2 S2 - - - - - -
RI F DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU

1.1.5 DBB11_99
This sections describes DBB11_99, used for GSM configurations.

Figure 6 shows the DBB11_99 block diagram.

RI A

RI B

RI C
DU

RI D

RI E

RI F

Ge26680A

Figure 6 DBB11_99 Block Diagram

about:blank 6/268
3/5/24, 9:34 AM Building Blocks
The following rules apply to configurations with DBB11_99:

– DBB11_99 is used only for GSM.

– Port RI F is used for synchronization between DUs.

– Ports RI A, RI B, RI C, RI D, and RI E can be used for radio connections.

– Each RI port can connect to one radio or one cascade chain (up to six radios). For more information on CPRI
dependencies and cascading, see DBB11_99 Configurations.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

– All connected RBBs must not use more than the supported capacity of the specified DU.

1.1.5.1 DBB11_99 Configurations

DBB11_99 configurations must follow the following connection rules:

– DBB11_99 is only used by GSM configurations with DUG 20.

– DBB11_99 uses one DU.

– DBB11_99 uses port RI F for synchronization between DUs.

– DBB11_99 can use ports RI A, RI B, RI C, RI D, and RI E to connect to radios.

– Each RI port can connect to one radio or one cascaded radio chain which supports GSM configurations.

– DBB11_99 supports all RBBs, which support GSM single mode star and cascade configurations.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– DBB11_99 does not support mixed mode radios or ring configurations.

– All radio units and connected RBBs shall not use more than the capacity of the DU.

1.1.6 DBB12_xx
This section describes DBBs with one DU and two IDL2 links to other DBBs through CPRI connections. For a description of
DBB12_99, see DBB12_99.

Figure 7 shows the DBB12_xx block diagram. Figure 8 shows an example of DBB12_xx connected to two other DBBs.

RI A

RI B

RI C
DU

RI D

RI E

RI F

Ge26682A

Figure 7 DBB12_xx Block Diagram

about:blank 7/268
3/5/24, 9:34 AM Building Blocks

RI A

RI B

RI C

DU
DBB 12
RI D

RI E

RI F

RI A

RI B

RI C
DU

DBB 11
RI D

RI E

RI F

RI A

RI B

RI C
DU

DBB 11
RI D

RI E

RI F
Ge26683A

Figure 8 Block Diagram for DBB12_xx Connected to Two DBB11_xx.

Table 3 lists the DBB12_xx variants and their connections from DU to sectors and other DBBs. Each sector is denoted Sx,
where x is the number of the sector. Cascaded configurations are indicated by the use of a comma. For example, S1, S2, S3
indicates that the RBBs for sector 1, sector 2, and sector 3 are cascaded and therefore connected to DU using the same
CPRI connection.

Table 3 DBB12_xx
Connection Connection to Sector
from DU
Port DBB12_01 DBB12_02 DBB12_03 DBB12_04 DBB12_05 DBB12_21 DBB12_22 DBB12_23 DBB21_24 DBB12_25 DBB12_26
S1, S2, S3, S1, S2, S3,
RI A S1 S1 S1 S1 S1 S1, S2, S3 S1, S2 S1, S2, S3 S1, S2
S4, S5, S6 S4, S5, S6
S6, S5, S4,
RI B S2 S2 S1 S1 S2 - S4, S5, S6 S3, S4 S4, S5, S6 S3, S4
S3, S2, S1
RI C S3 S3 S1 S1 S1 - - S5, S6 - S3, S2, S1 S2, S1
RI D S4 S1 S2 S1 S2 - - - - S6, S5, S4 S4, S3
RI E DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU
RI F DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU DU-DU

1.1.7 DBB12_99
This sections describes DBB12_99, used for GSM configurations.

Figure 9 shows the DBB12_99 block diagram.

about:blank 8/268
3/5/24, 9:34 AM Building Blocks

RI A

RI B

RI C

DU
RI D

RI E

RI F

Ge26682A

Figure 9 DBB12_99 Block Diagram

The following rules apply to configurations with DBB12_99:

– DBB12_99 is used only for GSM.

– Ports RI E and RI F are used for synchronization between DUs.

– Ports RI A, RI B, RI C, and RI D can be used for radio connections.

– Each RI port can connect to one radio or one cascade chain (up to six radios). For more information on CPRI
dependencies and cascading, see DBB12_99 Configurations.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

– All connected RBBs must not use more than the supported capacity of the specified DU.

1.1.7.1 DBB12_99 Configurations

DBB12_99 configurations must follow the following connection rules:

– DBB12_99 is only used by GSM configurations with DUG 20.

– DBB12_99 shall use one DU unit.

– DBB12_99 shall use ports RI E and RI F for synchronization between DUs.

– DBB12_99 can use ports RI A, RI B, RI C, and RI D to connect to radios.

– Each RI port can connect to one radio or one cascaded radio chain which supports GSM configurations.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– DBB12_99 shall support all RBBs, which support GSM single mode star and cascade configurations.

– DBB12_99 shall not support mixed mode radios or ring configurations.

– All radio units and connected RBBs shall not use more than the capacity of the DU.

1.1.8 DBB20_81
This section describes DBB20_81, which has the following:

– Two DUs and one IDL1 link for DU interconnection.

– Support for Baseband R503.

For DU, Baseband, and software dependencies related to Baseband R503, see Fronthaul.

about:blank 9/268
3/5/24, 9:34 AM Building Blocks
Figure 10 shows the DBB20_81 block diagram.

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26684A

Figure 10 DBB20_81 Block Diagram

The following rules apply to configurations with DBB20_81:

– The two DUs must be of the same type.

– All available RI ports can be used for radio connections.

– Each RI port can connect to one radio or one cascade chain (up to four radios).

– Any single DU in DBB20_81 can be connected to RBBs supported in DBB10_81 following the same placement rules.
For more information on CPRI dependencies and cascading, see DBB10_81, DBB10_81 Configurations

– Normally one RBB is only connected to one DU.

– The following RBBs with two CPRI links can be connected to two DUs (one CPRI is connected to the first DU and
another CPRI is connected to the second DU, but no Carrier aggregation between DUs): RBB11_2A, RBB11_2B,
RBB22_2C and RBB88_2A.

– Any single DU in DBB20_81 must support the same node capacity as in DBB10_81.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

– All connected RBBs must not use more than the supported capacity of the specified DU.

For Baseband R503 connections to DU and to radios, see Baseband R503 in Fronthaul.

1.1.9 DBB21_xx
This section describes DBB21_xx, which has two DUs and one CPRI link for DU interconnection (IDL2). For a description of
DBB21_81, see DBB21_81. For a description of DBB21_99, see DBB21_99.

Figure 11 shows the DBB21_xx block diagram.

about:blank 10/268
3/5/24, 9:34 AM Building Blocks

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26686A

Figure 11 DBB21_xx Block Diagram

Table 4 lists the DBB21_xx variants and their connections between DUs and sectors.

Table 4 DBB21_xx
Connection from DU Port Connection to Sector
DBB21_01 DBB21_02
RI A S1 S1
RI B S2 S2
RI C S3 S3
DU 1
RI D - -
RI E - -
RI F DU 2 DU 2
RI A S4 S1
RI B S5 S2
RI C S6 S3
DU 2
RI D - -
RI E - -
RI F DU 1 DU 1

1.1.10 DBB21_81
This section describes DBB21_81, used for LTE configurations, which contains the following:

– Two DUs and one IDL2 link for DU interconnection

– Support for Baseband R503

For DU, Baseband, and software dependencies related to Baseband R503, see Fronthaul.

Figure 12 shows the DBB21_81 block diagram. One DU is configured as the core DU for the node and the other one is
configured as the extension DU .

about:blank 11/268
3/5/24, 9:34 AM Building Blocks

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26685A

Figure 12 DBB21_81 Block Diagram

The following apply for DU interconnections for DBB21_81:

– Any of the ports RI C, RI D, RI E and RI F on both DUs can be used for the IDL2 link. The default connection is
between the RI F ports.

– DUS 31 and DUS 41 must not be mixed in the DBB.

– If the extension DU is a DUS 31 01 or a DUS 41 01, then the IDL1 link (dotted line in the block diagram) between the
core DU and extension DU is required.

– If the extension DU is a DUS 31 02 or a DUS 41 02, then the IDL1 link (dotted line in the block diagram) between the
core DU and extension DU is optional, but recommended.

See Table 5 for IDL1 configuration with DBB21_81

Table 5 IDL1 Support with DUS 31 and DUS 41 for DBB21_81

DU 1 (Core) DU 2 (Extension) IDL1 Use

DUS 31 01 DUS 31 01 Required
DUS 31 01 DUS 31 02 Optional
DUS 31 02 DUS 31 01 Required
DUS 31 02 DUS 31 02 Optional
DUS 41 01 DUS 41 01 Required
DUS 41 01 DUS 41 02 Optional
DUS 41 02 DUS 41 01 Required
DUS 41 02 DUS 41 02 Optional

The following rules apply to configurations with DBB21_81:

– DBB21_81 is used only for LTE, with support for FDD, TDD or a mix of FDD and TDD configurations.

– Two of the available RI ports, one port per DU, are unavailable for connections to RBBs.

about:blank 12/268
3/5/24, 9:34 AM Building Blocks
– RBBs can be connected to any RI ports on DU that not are used for the IDL2 link or Baseband R503.

– Each RI port can connect to one radio or one cascade chain.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– Any single DU in DBB21_81 can be connected to RBBs supported in DBB10_81 following the same placement rules.
For more information on CPRI dependencies and cascading, see DBB10_81, DBB10_81 Configurations

– Normally one RBB is only connected to one DU.

– The following RBBs with two CPRI links can be connected to two DUs (one CPRI is connected to the first DU and
another CPRI is connected to the second DU, but no Carrier aggregation between DUs): RBB11_2A, RBB11_2B,
RBB22_2C and RBB88_2A.

– Any single DU in DBB21_81 must support the same node capacity as in DBB10_81.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

1.1.11 DBB21_99
This section describes DBB21_99, used for WCDMA configurations, which contains the following:

– Two DUs and one CPRI link for interconnecting these

Figure 12 shows the DBB21_99 block diagram. One DU is configured as the core DU for the node and the other one is
configured as the extension DU.

DU 1
RI A

RI B

RI C
DU

RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26685A

Figure 13 DBB21_99 Block Diagram

The DU interconnections for DBB21_99 are described below:

– The two DUs are connected by a CPRI link between the RI F ports.

The following rules apply to configurations with DBB21_99:

– DBB21_99 is used only for WCDMA.

about:blank 13/268
3/5/24, 9:34 AM Building Blocks
– Two of the available RI ports, one port per DU, are unavailable for connections to RBBs.

– RBBs can be connected to any RI ports on the DUs that not are used for the CPRI DU interconnection link.

– Each RI port can connect to one radio or one cascade chain.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– Normally an RBB is only connected to one DU.

– Any single DU in DBB21_99 can be connected to RBBs supported in DBB10_99 following the same placement rules.
For more information on CPRI dependencies and cascading, see DBB10_99, DBB10_99 Configurations.

– Any single DU in DBB21_99 must support the same node capacity as in DBB10_99.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

Radio Radio Radio Radio Radio

RBB(s)

DU Radio Radio Radio

RBB(s)

Radio

Radio

RBB(s)

DU Radio

Radio

Ge26690A

Figure 14 Examples of DBB21_99 Configurations With Cascading, Single and Multiple CPRI Links per RBB

1.1.12 DBB22_xx
This section describes DBB22_xx, which has two DUs and two CPRI links for DU interconnections (IDL2) with different port
configurations. For a description of DBB22_99, see DBB22_99.

Figure 15 shows the DBB22_xx block diagram.

about:blank 14/268
3/5/24, 9:34 AM Building Blocks

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge4651D

Figure 15 DBB22_xx Block Diagram

Table 6 lists the DBB22_xx variants and their connections between DUs and sectors.

Table 6 DBB22_xx
Connection from DU Port Connection to Sector
DBB22_01 DBB22_02
RI A S1 S1
RI B S2 S2
RI C S3 S3
DU 1
RI D - -
RI E DU 2, RI E DU 2, RI E
RI F DU 2, RI F DU 2, RI F
RI A S4 S1
RI B S5 S2
RI C S6 S3
DU 2
RI D - -
RI E DU 1, RI E DU 1, RI E
RI F DU 1, RI F DU 1, RI F

1.1.13 DBB22_99
This section describes DBB22_99, used for WCDMA configurations, which has:

– Two DUs and two CPRI links for DU interconnection

Figure 12 shows the DBB22_99 block diagram. One DU is configured as the core DU for the node and the other one is
configured as the extension DU.

about:blank 15/268
3/5/24, 9:34 AM Building Blocks

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26687A

Figure 16 DBB22_99 Block Diagram

The DU interconnections for DBB22_99 are described below:

– The two DUs are connected by two CPRI links between the RI E ports and between the RI F ports on both DUs.

The following rules apply to configurations with DBB22_99:

– DBB22_99 is used only for WCDMA.

– In total four of the available RI ports, two ports per DU, are unavailable for connections to RBBs.

– RBBs can be connected to any RI ports on the DUs that not are used for the CPRI DU interconnection links.

– Each RI port can connect to one radio or one cascade chain.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– Normally an RBB is only connected to one DU.

– Any single DU in DBB22_99 can be connected to RBBs supported in DBB10_99 following the same placement rules.
For more information on CPRI dependencies and cascading, see DBB10_99, DBB10_99 Configurations.

– Any single DU in DBB22_99 must support the same node capacity as in DBB10_99.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

about:blank 16/268
3/5/24, 9:34 AM Building Blocks

Radio Radio Radio Radio Radio

RBB(s)

DU Radio Radio Radio

RBB(s)

Radio

Radio

RBB(s)

DU Radio

Radio

Ge26690A

Figure 17 Examples of DBB22_99 Configurations with Cascading, Single and Multiple CPRI Links per RBB

1.1.14 DBB31_81
This section describes DBB31_81, used for LTE configurations, which contains the following:

– Three DUs and two links for DU interconnections

– Support for Baseband R503

For DU, Baseband, and software dependencies related to Baseband R503, see Fronthaul.

Figure 18 shows the DBB31_81 block diagram. DU 1 in the block diagram is configured as the core DU for the node. DU 2
and DU 3 are configured as extension DUs.

about:blank 17/268
3/5/24, 9:34 AM Building Blocks

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F

DU 3
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26688A

Figure 18 DBB31_81 Block Diagram Showing the Default DU Interconnections

The DU interconnections for DBB31_81 are described below:

– The core DU is connected to DU 2 (extension) through an IDL1 link.

– The core DU is connected to DU 3 (extension) through an IDL2 link. Any of the ports RI C, RI D, RI E or RI F on the
core DU is connected to any of the ports RI C, RI D, RI E or RI F on the extension DU. The default connection is
between the RI F ports.

– DUS 31 and DUS 41 must not be mixed in the DBB.

– DU 3 must be a DUS 31 02 or a DUS 41 02.

See Table 7 for DUS 31 and DUS 31 Configurations with DBB31_81

Table 7 DUS 31 and DUS 41 Configurations for DBB31_81

DU 1 (Core) DU 2 (Extension) DU 3 (Extension) IDL1 Use

DUS 31 01 DUS 31 01 DUS 31 02 Required
DUS 31 01 DUS 31 02 DUS 31 02 Required
DUS 31 02 DUS 31 01 DUS 31 02 Required
DUS 31 02 DUS 31 02 DUS 31 02 Required
DUS 41 01 DUS 41 01 DUS 41 02 Required

about:blank 18/268
3/5/24, 9:34 AM Building Blocks

DU 1 (Core) DU 2 (Extension) DU 3 (Extension) IDL1 Use

DUS 41 01 DUS 41 02 DUS 41 02 Required
DUS 41 02 DUS 41 01 DUS 41 02 Required
DUS 41 02 DUS 41 02 DUS 41 02 Required

The following rules apply to configurations with DBB31_81:

– DBB31_81 is used only for LTE, with support for FDD or TDD.

– In total two of the RI ports are unavailable for connections to RBBs.

– RBBs can be connected to any RI ports on the DUs that not are used for the IDL2 link.

– Each RI port can connect to one radio or one cascade chain.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– Any single DU in DBB31_81 can be connected to RBBs supported in DBB10_81 following the same placement rules.
For more information on CPRI dependencies and cascading, see DBB10_81, DBB10_81 Configurations.

– Each RBB is connected to only one of the DUs.

– Any single DU in DBB31_81 must support the same node capacity as in DBB10_81.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

1.1.15 DBB32_81
This section describes DBB32_81, used for LTE configurations, which contains the following:

– Three DUs and two IDL2 links for DU interconnection

– Support for Baseband R503

For DU, Baseband, and software dependencies related to Baseband R503, see Fronthaul.

Figure 19 shows the DBB32_81 block diagram. DU 1 in the block diagram is configured as the core DU for the node. DU 2
and DU 3 are configured as extension DUs.

about:blank 19/268
3/5/24, 9:34 AM Building Blocks

DU 1
RI A

RI B

RI C

DU
RI D

RI E

RI F

DU 2
RI A

RI B

RI C
DU

RI D

RI E

RI F

DU 3
RI A

RI B

RI C
DU

RI D

RI E

RI F
Ge26689A

Figure 19 DBB32_81 Block Diagram Showing the Default DU Interconnections

DU interconnections for DBB32_81 are described below:

– The core DU is connected to the extension DUs through IDL2 links. Any of the ports RI C, RI D, RI E or RI F on the
core DU is connected to any of the ports RI C, RI D, RI E or RI F on the extension DUs. The default connections are
from the RI E and RI F ports on the core DU to the RI F port on each extension DU.

– DUS 31 and DUS 41 must not be mixed in the DBB.

– DU 3 must be a DUS 31 02 or a DUS 41 02.

– If DU 2 is a DUS 31 01 or a DUS 41 01, then the IDL1 link (dotted line in the block diagram) between DU 1 (core) and
DU 2 (extension) is required.

– If DU 2 is a DUS 31 02 or a DUS 41 02, then the IDL1 link (dotted line in the block diagram) between DU 1 (core) and
DU 2 (extension) is optional, but recommended.

See Table 8 for IDL1 configuration with DBB32_81.

Table 8 IDL1 Support with DUS 31 and DUS 41 for DBB32_81

DU 1 (Core) DU 2 (Extension) DU 3 (Extension) IDL1 Use

DUS 31 01 DUS 31 01 DUS 31 02 Required
DUS 31 01 DUS 31 02 DUS 31 02 Optional

about:blank 20/268
3/5/24, 9:34 AM Building Blocks

DU 1 (Core) DU 2 (Extension) DU 3 (Extension) IDL1 Use

DUS 31 02 DUS 31 01 DUS 31 02 Required
DUS 31 02 DUS 31 02 DUS 31 02 Optional
DUS 41 01 DUS 41 01 DUS 41 02 Required
DUS 41 01 DUS 41 02 DUS 41 02 Optional
DUS 41 02 DUS 41 01 DUS 41 02 Required
DUS 41 02 DUS 41 02 DUS 41 02 Optional

The following rules apply to configurations with DBB32_81

– DBB32_81 is used only for LTE, with support for FDD or TDD.

– In total four of the RI ports are unavailable for connections to RBBs.

– RBBs can be connected to any RI ports on the DU unit that not are used for the IDL2 links.

– Each RI port can connect to one radio or one cascade chain.

– Radio Cascade Configuration Rules describes radio cascade configuration rules.

– Any single DU unit in DBB32_81 can be connected to RBBs supported in DBB10_81 following the same placement
rules. For more information on CPRI dependencies and cascading, see DBB10_81, DBB10_81 Configurations.

– Each RBB is connected to only one of the DUs.

– Any single DU unit in DBB32_81 must support the same node capacity as in DBB10_81.

– The supported sectors, radios, and cells must not exceed the capacity of one node.

1.2 RBBs
Each RBB defines a unique way of combining either internal radios, external radios or AIR in one sector with connections to
DUs or Baseband units and the antenna system.

RBBs are named as follows: RBB[Tx][Rx]_[C][V], where:

Tx Number of Transmitter (TX) branches

Rx Number of Receiver (RX) branches (excluding co-siting RX ports)

C Number of Common Public Radio Interface (CPRI) links

V Version

Example: RBB12_1A

– One TX branch

– Two RX branches

– One CPRI link between DU or Baseband and radio

– Version A

Note: Which ports are available, depends on the radio. All the ports shown in the RBB block diagram are not always
available.

CPRI link is connected to Data 1 or Data 2 depending upon the radio standard. CPRI Connections from DU or Baseband to
Radio chapter in Fronthaul lists the CPRI connections.

about:blank 21/268
3/5/24, 9:34 AM Building Blocks

1.2.1 RBBs with Different Frequency Bands on Different RF Ports

Different radios in the RBB support different frequency bands, and software can allocate each carrier to the correct RF
ports based on radio capabilities.

Table 9 Downlink and Uplink Support for NB-IoT Standalone for Band 111 and Band 222
Radio Frequency Band Downlink and Uplink Support
Radio 4415 B70 Band 222 DL on 4 ports
Band 111 UL on 2 ports
Radio 0208 BH
Band 222 UL on 2 ports
Radio 2012 B29
Band 111 DL on 2 ports
RRUS E2 B29

Downlink and uplink capabilities per RF frequency branch and band for the different RBBs are shown in Table 10.

Table 10 Downlink and Uplink Capabilities per RF Frequency Branch for Different RBBs
RBB Frequency Band RF Branch for Downlink RF Branch for Uplink
RBB24_1D
RBB24_2E Band 222 1, 2 3, 4
RBB24_2F
RBB44_1L Band 111 5, 6 3, 4
RBB44_2Q
RBB44_3C
RBB44_3D Band 222 1, 2 3, 4

RBB46_1A
Band 222 1, 2, 3, 4 5, 6
RBB46_2A
RBB66_1A Band 111 7, 8 5, 6
RBB66_3A Band 222 1, 2, 3, 4 5, 6

1.2.2 RBB10_1A
RBB10_1A is used for sectors with one TX branch, two external RX branches, and one CPRI connection. This RBB is
supported for MSMM configurations.
For mixed mode, the port Data 2 can be used. For more information, see CPRI Connections from DU or Baseband to Radio
in Fronthaul.
Figure 20 shows the RBB10_1A block diagram.

RI Link RF Branch

1: TX A
Node 1 Data A

2: RX A
Radio 1 RXA I/O

3: RX B
Other Node Data RXB I/O
or Cascade

Ge13103D

Figure 20 RBB10_1A Block Diagram

1.2.3 RBB11_1A
RBB11_1A is used for sectors with one TX branch and two RX branches, one of which is an external RX branch for antenna
sharing, and one CPRI connection. This RBB is supported for MSMM configurations.

about:blank 22/268
3/5/24, 9:34 AM Building Blocks
For mixed mode, the port Data 2 can be used. For more information, see CPRI Connections from DU or Baseband to Radio
in Fronthaul.
Figure 21 shows the RBB11_1A block diagram.
Figure 22 shows the RBB11_1A block diagram for AIR.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: RX B
Other Node Data RXB I/O
or Cascade

Ge13104C

Figure 21 RBB11_1A Block Diagram

RI Link
AIR Unit RF Branch
1: TX A / RX A
Node 1 Data A
AIR 1 2: RX B
Other Node Data RXB I/O
or Cascade

HW unit including ABB

Ge14131C

Figure 22 RBB11_1A Block Diagram for AIR

1.2.4 RBB11_1C
RBB11_1C is used for sectors with one TX branch, one RX branch, and one CPRI connection. This RBB is supported for
MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Data
Other Node(s) Radio 1 A
Data
or Cascade
Data

Ge26390A

Figure 23 RBB11_1C Block Diagram

about:blank 23/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Radio 1 A
Other Node or
Data
Cascade

Ge13140C

Figure 24 Example of RBB11_1C for Radio Units with Two Data Ports

RI Link RF Branch RF Branch

Node 1 Data
1A 1: TX A / RX A
A
Radio 1 1B
(virtual port) E
Other Node Data
or Cascade

Ge22829B

Figure 25 RBB11_1C Block Diagram for Radio 4449 B5 B13

1.2.5 RBB11_1D
RBB11_1D is used for sectors with one TX branch, one RX branch, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB11_1D is used together with RBB11_1C.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Data
Other Node(s) Radio 1 B
Data
or Cascade
Data

Ge26391A

Figure 26 RBB11_1D Block Diagram

about:blank 24/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1
Data
1: TX A / RX A
Radio 1 B
Other Node Data
or Cascade

Ge13142C

Figure 27 Example of RBB11_1D for Radio Units with Two Data Ports

RI Link RF Branch RF Branch

Node 1 Data
1A 1: TX A / RX A
B
Radio 1 1B
(virtual port) F
Other Node Data
or Cascade

Ge22830B

Figure 28 RBB11_1D Block Diagram for Radio 4449 B5 B13

1.2.6 RBB11_1E
RBB11_1E is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Data
Other Node(s) Radio 1 C
Data
or Cascade
Data

Ge26392A

Figure 29 RBB11_1E Block Diagram

RI Link RF Branch

Node 1
Data
1: TX A / RX A
Radio 1 C
Other Node Data
or Cascade

Ge22720B

Figure 30 Example of RBB11_1E for Radio Units with Two Data Ports

about:blank 25/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch RF Branch

Node 1 Data
1A 1: TX A / RX A
C
Radio 1 1B
(virtual port) G
Other Node Data
or Cascade

Ge22822B

Figure 31 RBB11_1E Block Diagram for Radio 4449 B5 B13

1.2.7 RBB11_1F
RBB11_1F is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Data
Other Node(s) Radio 1 D
Data
or Cascade
Data

Ge26393A

Figure 32 RBB11_1F Block Diagram

RI Link RF Branch

Node 1
Data
1: TX A / RX A
Radio 1 D
Other Node Data
or Cascade

Ge22721B

Figure 33 Example of RBB11_1F for Radio Units with Two Data Ports

RI Link RF Branch RF Branch

Node 1 Data
1A 1: TX A / RX A
D
Radio 1 1B
(virtual port) H
Other Node Data
or Cascade

Ge22823B

about:blank 26/268
3/5/24, 9:34 AM Building Blocks

Figure 34 RBB11_1F Block Diagram for Radio 4449 B5 B13

1.2.8 RBB11_1G
RBB11_1G is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Data
Other Node(s) Radio 1 E
Data
or Cascade
Data

Ge26394A

Figure 35 RBB11_1G Block Diagram

RI Link RF Branch

Node 1
Data
1: TX A / RX A
Radio 1 E
Other Node Data
or Cascade

Ge22722B

Figure 36 Example of RBB11_1G for Radio Units with Two Data Ports

1.2.9 RBB11_1H
RBB11_1H is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Data
Other Node(s) Radio 1 F
Data
or Cascade
Data

Ge26395A

Figure 37 RBB11_1H Block Diagram

about:blank 27/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1
Data
1: TX A / RX A
Radio 1 F
Other Node Data
or Cascade

Ge22723B

Figure 38 Example of RBB11_1H for Radio Units with Two Data Ports

1.2.10 RBB11_1J
RBB11_1J is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Node 1 Data

Other Node
Data
or Cascade 1: TX A / RX A
Radio 1 G

Data
Other
Node(s)
Data

Ge28000A

Figure 39 RBB11_1J Block Diagram

Note: The number of available data ports depends on the used radio unit.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Radio 1 G
Other Node Data
or Cascade

Ge22724B

Figure 40 Example of RBB11_1J for Radio Unit with Two Data Ports

1.2.11 RBB11_1K
RBB11_1K is used for sectors with one TX branch, one RX branch, and one CPRI connection.

about:blank 28/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data

Other Node
Data
or Cascade 1: TX A / RX A
Radio 1 H

Data
Other
Node(s)
Data

Ge28001A

Figure 41 RBB11_1K Block Diagram

Note: The number of available data ports depends on the used radio unit.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Radio 1 H
Other Node Data
or Cascade

Ge22725B

Figure 42 Example of RBB11_1K for Radio Unit with Two Data Ports

1.2.12 RBB11_2A
RBB11_2A is used for sectors with one TX branch, one RX branch, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Data
Data
Radio 1 A
Other
Node(s) or Data
Cascade

Ge26396A

Figure 43 RBB11_2A Block Diagram

about:blank 29/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
Node 1 Radio 1 A
Data

Ge13141B

Figure 44 Example of RBB11_2A for Radio Units with Two Data Ports

RI Link RF Branch
RF Branch

Data
1A 1: TX A / RX A
A
Node 1 Radio 1 1B
(virtual port) E
Data

Ge26421B

Figure 45 RBB11_2A Block Diagram for Radio 4449 B5 B13

1.2.13 RBB11_2B
RBB11_2B is used for sectors with one TX branch, one RX branch, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB11_2B is used together with RBB11_2A.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Data
Radio 1 B
Other Data
Node(s) or Data
Cascade

Ge26397A

Figure 46 RBB11_2B Block Diagram

about:blank 30/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
Node 1 Radio 1 B
Data

Ge13143C

Figure 47 Example of RBB11_2B for Radio Units with Two Data Ports

RI Link RF Branch
RF Branch

Data
1A 1: TX A / RX A
B
Node 1 Radio 1 1B
(virtual port) F
Data

Ge22832B

Figure 48 RBB11_2B Block Diagram for Radio 4449 B5 B13

1.2.14 RBB11_2C
RBB11_2C is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Data
Data
Radio 1 C
Other
Node(s) or Data
Cascade

Ge26398A

Figure 49 RBB11_2C Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
Node 1 Radio 1 C
Data

Ge22726B

Figure 50 Example of RBB11_2C for Radio Units with Two Data Ports

about:blank 31/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch
RF Branch

Data
1A 1: TX A / RX A
C
Node 1 Radio 1 1B
(virtual port) G
Data

Ge22824B

Figure 51 RBB11_2C Block Diagram for Radio 4449 B5 B13

1.2.15 RBB11_2D
RBB11_2D is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Data
Data
Radio 1 D
Other
Node(s) or Data
Cascade

Ge26399A

Figure 52 RBB11_2D Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
Node 1 Radio 1 D
Data

Ge22727B

Figure 53 Example of RBB11_2D for Radio Units with Two Data Ports

RI Link RF Branch
RF Branch

Data
1A 1: TX A / RX A
D
Node 1 Radio 1 1B
(virtual port) H
Data

Ge26422B

about:blank 32/268
3/5/24, 9:34 AM Building Blocks

Figure 54 RBB11_2D Block Diagram for Radio 4449 B5 B13

1.2.16 RBB11_2E
RBB11_2E is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Data
Radio 1 E
Other Data
Node(s) or Data
Cascade

Ge26400A

Figure 55 RBB11_2E Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
Node 1 Radio 1 E
Data

Ge22728B

Figure 56 Example of RBB11_2E for Radio Units with Two Data Ports

1.2.17 RBB11_2F
RBB11_2F is used for sectors with one TX branch, one RX branch, and one CPRI connection.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Data
Data
Radio 1 F
Other
Node(s) or Data
Cascade

Ge26401A

Figure 57 RBB11_2F Block Diagram

about:blank 33/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
Node 1 Radio 1 F
Data

Ge22729B

Figure 58 Example of RBB11_2F for Radio Units with Two Data Ports

1.2.18 RBB11_2G
RBB11_2G is used for sectors with one TX branch, one RX branch, and one CPRI connection.
Figure 59 shows the RBB11_2G block diagram.

RI Link RF Branch

Data
Node 1
Data
1: TX A / RX A
Radio 1 G
Data
Other
Node(s)
Data

Ge22730C

Figure 59 RBB11_2G Block Diagram

1.2.19 RBB11_2H
RBB11_2H is used for sectors with one TX branch, one RX branch, and one CPRI connection.
Figure 60 shows the RBB11_2H block diagram.

RI Link RF Branch

Data
Node 1
Data
1: TX A / RX A
Radio 1 H
Data
Other
Node(s)
Data

Ge22731C

Figure 60 RBB11_2H Block Diagram

1.2.20 RBB11_3A
RBB11_3A is used for sectors with one TX branch, one RX branch, and three CPRI connections.

about:blank 34/268
3/5/24, 9:34 AM Building Blocks
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 61 shows the RBB11_3A block diagram.

RI Link RF Branch

Data
Node 1 Data 1: TX A / RX A
Data
Radio 1 A

Other Node Data

or Cascade

Ge25800

Figure 61 RBB11_3A Block Diagram

1.2.21 RBB11_3B
RBB11_3B is used for sectors with one TX branch, one RX branch, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 62 shows the RBB11_3B block diagram.

RI Link RF Branch

Data
Node 1 Data 1: TX A / RX A
Data
Radio 1 B

Other Node Data

or Cascade

Ge25801

Figure 62 RBB11_3B Block Diagram

1.2.22 RBB11_3C
RBB11_3C is used for sectors with one TX branch, one RX branch, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 63 shows the RBB11_3C block diagram.

RI Link RF Branch

Data
Node 1 Data 1: TX A / RX A
Data
Radio 1 C

Other Node Data

or Cascade

Ge25802

Figure 63 RBB11_3C Block Diagram

about:blank 35/268
3/5/24, 9:34 AM Building Blocks

1.2.23 RBB11_3D
RBB11_3D is used for sectors with one TX branch, one RX branch, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 64 shows the RBB11_3D block diagram.

RI Link RF Branch

Data
Node 1 Data 1: TX A / RX A
Data
Radio 1 D

Other Node Data

or Cascade

Ge25803

Figure 64 RBB11_3D Block Diagram

1.2.24 RBB11_3E
RBB11_3E is used for sectors with one TX branch, one RX branch, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 65 shows the RBB11_3E block diagram.

RI Link RF Branch

Data
Node 1 Data 1: TX A / RX A
Data
Radio 1 E

Other Node Data

or Cascade

Ge25804

Figure 65 RBB11_3E Block Diagram

1.2.25 RBB11_3F
RBB11_3F is used for sectors with one TX branch, one RX branch, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 66 shows the RBB11_3F block diagram.

RI Link RF Branch

Data
Node 1 Data 1: TX A / RX A
Data
Radio 1 F

Other Node Data

or Cascade

Ge25805

about:blank 36/268
3/5/24, 9:34 AM Building Blocks

Figure 66 RBB11_3F Block Diagram

1.2.26 RBB11_3G

RBB11_3G is used for sectors with one TX branch, one RX branch, and four CPRI connections. RF G port is used in this RBB.

RI Link RF Branch

Data

Node 1 Data
1: TX A / RX A
Radio 1 G

Data

Other Node Data

Ge28002A

Figure 67 RBB11_3G Block Diagram

1.2.27 RBB11_3H

RBB11_3H is used for sectors with one TX branch, one RX branch, and four CPRI connections. RF H port is used in this RBB.

RI Link RF Branch

Data

Node 1 Data
1: TX A / RX A
Radio 1 H

Data

Other Node Data

Ge28003A

Figure 68 RBB11_3H Block Diagram

1.2.28 RBB11_4A
RBB11_4A is used for sectors with one TX branch, one RX branch, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 69 shows the RBB11_4A block diagram.

about:blank 37/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
Data 1: TX A / RX A
Node 1
Data
Radio 1 A

Data

Ge25806

Figure 69 RBB11_4A Block Diagram

1.2.29 RBB11_4B
RBB11_4B is used for sectors with one TX branch, one RX branch, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 70 shows the RBB11_4B block diagram.

RI Link RF Branch

Data
Data 1: TX A / RX A
Node 1
Data
Radio 1 B

Data

Ge25807

Figure 70 RBB11_4B Block Diagram

1.2.30 RBB11_4C
RBB11_4C is used for sectors with one TX branch, one RX branch, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 71 shows the RBB11_4C block diagram.

RI Link RF Branch

Data
Data 1: TX A / RX A
Node 1
Data
Radio 1 C

Data

Ge25808

Figure 71 RBB11_4C Block Diagram

1.2.31 RBB11_4D
RBB11_4D is used for sectors with one TX branch, one RX branch, and four CPRI connections.
about:blank 38/268
3/5/24, 9:34 AM Building Blocks
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 72 shows the RBB11_4D block diagram.

RI Link RF Branch

Data
Data 1: TX A / RX A
Node 1
Data
Radio 1 D

Data

Ge25809

Figure 72 RBB11_4D Block Diagram

1.2.32 RBB11_4E
RBB11_4E is used for sectors with one TX branch, one RX branch, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 73 shows the RBB11_4E block diagram.

RI Link RF Branch

Data
Data 1: TX A / RX A
Node 1
Data
Radio 1 E

Data

Ge25810

Figure 73 RBB11_4E Block Diagram

1.2.33 RBB11_4F
RBB11_4F is used for sectors with one TX branch, one RX branch, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 74 shows the RBB11_4F block diagram.

RI Link RF Branch

Data
Data 1: TX A / RX A
Node 1
Data
Radio 1 F

Data

Ge25811

Figure 74 RBB11_4F Block Diagram

about:blank 39/268
3/5/24, 9:34 AM Building Blocks

1.2.34 RBB11_4G

RBB11_4G is used for sectors with one TX branch, one RX branch, and four CPRI connections. RF G port is used in this RBB.

RI Link RF Branch

Data

Data
1: TX A / RX A
Node 1 Radio 1 G

Data

Data

Ge28004A

Figure 75 RBB11_4G Block Diagram

1.2.35 RBB11_4H

RBB11_4H is used for sectors with one TX branch, one RX branch, and four CPRI connections. RF H port is used in this RBB.

RI Link RF Branch

Data

Data
1: TX A / RX A
Node 1 Radio 1 G

Data

Data

Ge28004A

Figure 76 RBB11_4H Block Diagram

1.2.36 RBB12_1A
RBB12_1A is used for sectors with one TX branch, two RX branches, and one CPRI connection. This RBB is supported for
MSMM configurations.
For mixed mode and Multi-Operator LTE + LTE configurations, the Data 2 port can be used. For more information, see CPRI
Connections from DU or Baseband to Radio in Fronthaul.
Figure 77 shows the RBB12_1A block diagram.
Figure 78 shows the RBB12_1A block diagram for AIR.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: RX B
Other Node or
Data B
Cascade

Ge13105C

about:blank 40/268
3/5/24, 9:34 AM Building Blocks

Figure 77 RBB12_1A Block Diagram

RI Link
AIR Unit RF Branch
1: TX A / RX A
Node 1 Data A
AIR 1 2: RX B
Other Node or
Data B
Cascade

HW unit including ABB

Ge14132C

Figure 78 RBB12_1A Block Diagram for AIR

1.2.37 RBB12_1C
RBB12_1C is used for sectors with one TX branch, two RX branches, and one CPRI connection. This RBB uses a digital RX
cross-connection. This RBB is supported for MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
One of the radios in this RBB is an RX-only capable radio.
For mixed mode and Multi-Operator RAN LTE + LTE configurations, Data 2 port can be used. For more information, see
CPRI Connections from DU or Baseband to Radio in Fronthaul.
Figure 79 shows the RBB12_1C block diagram.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Radio 1 A
Data

Data
2: RX B
Radio 2 A
Other Node
Data
or Cascade

Ge14133B

Figure 79 RBB12_1C Block Diagram

1.2.38 RBB12_1D
RBB12_1D is used for sectors with one TX branch, two RX branches, and one CPRI connection. This RBB uses a digital RX
cross-connection. This RBB is supported for MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
One of the radios in this RBB is an RX-only capable radio.
RBB12_1D is used together with RBB12_1C.
For mixed mode and Multi-Operator RAN LTE + LTE configurations, Data 2 port can be used. For more information, see
CPRI Connections from DU or Baseband to Radio in Fronthaul.
Figure 80 shows the RBB12_1D block diagram.

about:blank 41/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
Radio 1 B
Data

Data
2: RX B
Radio 2 B
Other Node
Data
or Cascade

Ge14134C

Figure 80 RBB12_1D Block Diagram

1.2.39 RBB12_1E
RBB12_1E is used for sectors with one TX branch, two RX branches, and one CPRI connection. This RBB is supported for
MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB12_1E is used together with RBB12_1F.
Figure 81 shows the RBB12_1E block diagram.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: RX B
C
Other Node Data
or Cascade

Ge14135C

Figure 81 RBB12_1E Block Diagram

1.2.40 RBB12_1F
RBB12_1F is used for sectors with one TX branch, two RX branches, and one CPRI connection. This RBB is supported for
MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB12_1F is used together with RBB12_1E.
Figure 82 shows the RBB12_1F block diagram.

about:blank 42/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
B
Radio 1 2: RX B
D
Other Node Data
or Cascade

Ge14136C

Figure 82 RBB12_1F Block Diagram

1.2.41 RBB12_2A
RBB12_2A is used for sectors with one TX branch, two RX branches, and two CPRI connections.
This RBB is used for ring topology in GSM.
Figure 83 shows the RBB12_2A block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 Radio 1 2: RX B
Data B

Ge13106C

Figure 83 RBB12_2A Block Diagram

1.2.42 RBB12_2B
RBB12_2B is used for sectors with one TX branch, two RX branches, and two CPRI connections. This RBB uses a digital RX
cross-connection. This RBB is supported for MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
One of the radios in this RBB is an RX-only capable radio.
Figure 84 shows the RBB12_2B block diagram.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Radio 1 A
Data

Data
2: RX B
Other
Node(s) or
Radio 2 A
Data
Cascade

Ge14137C

about:blank 43/268
3/5/24, 9:34 AM Building Blocks

Figure 84 RBB12_2B Block Diagram

1.2.43 RBB12_2C
RBB12_2C is used for sectors with one TX branch, two RX branches, and two CPRI connections. This RBB uses a digital RX
cross-connection. This RBB is supported for MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
One of the radios in this RBB is an RX-only capable radio.
RBB12_2C is used together with RBB12_2B.
Figure 85 shows the RBB12_2C block diagram.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Radio 1 B
Data

Data
2: RX B
Other
Node(s) or
Radio 2 B
Data
Cascade

Ge14138C

Figure 85 RBB12_2C Block Diagram

1.2.44 RBB12_2D
RBB12_2D is used for sectors with one TX branch, two RX branches, and two CPRI connections. This RBB is supported for
MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB12_2D is used together with RBB12_2E.
Figure 86 shows the RBB12_2D block diagram.

RI Link RF Branch

Data
1: TX A / RX A
A
Node 1 Radio 1 2: RX B
C
Data

Ge14139C

Figure 86 RBB12_2D Block Diagram

1.2.45 RBB12_2E
RBB24_2D is used for sectors with one TX branch, two RX branches, and two CPRI connections. This RBB is supported for
MSMM configurations.

about:blank 44/268
3/5/24, 9:34 AM Building Blocks
This RBB can be used with the Multi-Sector Per Radio feature.
RBB12_2E is used together with RBB12_2D.
Figure 87 shows the RBB12_2E block diagram.

RI Link RF Branch

Data
1: TX A / RX A
B
Node 1 Radio 1 2: RX B
D
Data

Ge14140C

Figure 87 RBB12_2E Block Diagram

1.2.46 RBB14_1A
RBB14_1A is used for sectors with one TX branch, four RX branches, and one CPRI connection. This RBB uses a digital RX
cross-connection. This RBB is supported for MSMM configurations.
One of the radios in this RBB is an RX-only capable radio.
For mixed mode, the Data 2 port can be used. For more information, see CPRI Connections from DU or Baseband to Radio
in Fronthaul.
Figure 88 shows the RBB14 _1A block diagram

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: RX B
Data B

3: RX C
Data A
Radio 2 4: RX D
Other Node Data B
or Cascade

Ge13119C

Figure 88 RBB14_1A Block Diagram

1.2.47 RBB14_2A
RBB14_2A is used for sectors with one TX branch, four RX branches, and two CPRI connections. This RBB uses a digital RX
cross-connection. This RBB is supported for MSMM configurations.
One of the radios in this RBB is an RX-only capable radio.
Figure 88 shows the RBB14 _2A block diagram

about:blank 45/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: RX B
Data B

3: RX C
Data A
Other
Node(s) or
Radio 2 4: RX D
Data B
Cascade

Ge13120C

Figure 89 RBB14_2A Block Diagram

1.2.48 RBB20_1A
RBB20_1A is used for sectors with two TX branches, two external RX branches for antenna sharing, and one CPRI
connection. This RBB is supported for MSMM configurations.
Figure 90 shows the RBB20_1A block diagram.

RI Link RF Branch

1: TX A
Node 1 Data A

2: TX B
B
Radio 1 3: Ext. RX A
RXA I/O

4: Ext. RX B
Other Node Data RXB I/O
or Cascade

Ge13107C

Figure 90 RBB20_1A Block Diagram

1.2.49 RBB20_1B
RBB20_1B is used for sectors with two TX branches and one CPRI connection.
Figure 91 shows the RBB20_1B block diagram.

RI Link RF Branch

1: TX A
Node 1 Data A
Radio 1 2: TX B
Other Node
Data B
or Cascade

Ge13108C

about:blank 46/268
3/5/24, 9:34 AM Building Blocks

Figure 91 RBB20_1B Block Diagram

1.2.50 RBB20_1C
RBB20_1C is used for sectors with two TX branches and no RX branches, two I/Os for diplexing and one CPRI connection.
The software can model the configuration as if each RBB has its own RF branches.
For examples of connecting other RBBs to the diplexer I/Os, see Radio-Integrated Diplexer in Features for Radio
Configurations.
Figure 92 shows the RBB20_1C block diagram.

Radio(s) in connected
RBB

RF Branch 1
RF Branch 2
RI Link RF Branch
1: TX A
Node 1 Data A

Diplex A IN
Radio 1
Diplex B IN

Other Node 2: TX B
Data B
or Cascade

Ge23007B

Figure 92 RBB20_1C Block Diagram

1.2.51 RBB20_1D
RBB20_1D is used for sectors with two TX branches and one CPRI connection.
Figure 93 shows the RBB20_1D block diagram.

RI Link RF Branch

Node 1 Data
1: TX A
A
Radio 1 2: TX B
B
Other Node Data
or Cascade

Ge25341B

Figure 93 RBB20_1D Block Diagram

1.2.52 RBB20_1E

about:blank 47/268
3/5/24, 9:34 AM Building Blocks
RBB20_1E is used for sectors with two TX branches and one CPRI connection.
Figure 94 shows the RBB20_1E block diagram.

RI Link RF Branch

Node 1 Data
1: TX A
C
Radio 1 2: TX B
D
Other Node Data
or Cascade

Ge25342B

Figure 94 RBB20_1E Block Diagram

1.2.53 RBB20_2A
RBB20_2A is used for sectors with two TX branches, four external RX branches, and two CPRI connections. This RBB is
supported for MSMM configurations.
Figure 95 shows the RBB20_2A block diagram.

RI Link RF Branch

1: TX A
Data A
Node 1
2: Ext. RX A
Radio 1 RXA I/O

3: Ext. RX B
Data RXB I/O

4: TX C
Data A

5: Ext. RX C
Radio 2 RXA I/O

Other Node(s) 6: Ext. RX D

or Cascade Data RXB I/O

Ge13121C

Figure 95 RBB20_2A Block Diagram

1.2.54 RBB20_2B
RBB20_2B is used for sectors with two TX branches and two CPRI connections.
Figure 96 shows the RBB20_2B block diagram.

about:blank 48/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A
Data A
Node 1 Radio 1 2: TX B
Data B

Ge14141C

Figure 96 RBB20_2B Block Diagram

1.2.55 RBB20_2C
RBB20_2C is used for sectors with two TX branches and no RX branches, two I/Os for diplexing and two CPRI connections.
The software can model the configuration as if each RBB has its own RF branches.
For examples of connecting other RBBs to the diplexer I/Os, see Radio-Integrated Diplexer in Features for Radio
Configurations.
Figure 97 shows the RBB20_2C block diagram.

Radio(s) in connected
RBB

RF Branch 1
RF Branch 2

RI Link RF Branch
1: TX A
Data A

Diplex A IN
Node 1 Radio 1
Diplex B IN

2: TX B
Data B

Ge23008B

Figure 97 RBB20_2C Block Diagram

1.2.56 RBB20_2D
RBB20_2D is used for sectors with two TX branches and two CPRI connections.
Figure 98 shows the RBB20_2D block diagram.

about:blank 49/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A
A
Node 1 Radio 1 2: TX B
B
Data

Ge25343B

Figure 98 RBB20_2D Block Diagram

1.2.57 RBB20_2E
RBB20_2E is used for sectors with two TX branches and two CPRI connections.
Figure 99 shows the RBB20_2E block diagram.

RI Link RF Branch

Data
1: TX A
C
Node 1 Radio 1 2: TX B
D
Data

Ge25344B

Figure 99 RBB20_2E Block Diagram

1.2.58 RBB22_1A
RBB22_1A is used for sectors with two TX branches, two RX branches, and one CPRI connection. This RBB uses an analog
RX cross-connection. This RBB is supported for MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
For mixed mode, the port Data 2 can be used. For more information, see CPRI Connections from DU or Baseband to Radio
in Fronthaul.
Figure 100 shows the RBB22_1A block diagram.
Figure 101 shows the RBB22_1A block diagram for AIR.

about:blank 50/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

Radio 1 RXA I/O

Data RXB I/O

RF Branch 2
2: TX B / RX B
Data A

RF Branch 1
Radio 2 RXA I/O

Other Node
Data RXB I/O
or Cascade

Ge13136C

Figure 100 RBB22_1A Block Diagram

RI Link RF Branch
AIR Unit
1: TX A / RX A
Node 1 Data A

AIR 1 RXA I/O

Data RXB I/O

Branch 2
RF

2: TX B / RX B
Data A

AIR 2
Branch 1

RXA I/O
RF

Other Node
Data RXB I/O
or Cascade

HW unit including ABB

Ge13138C

Figure 101 RBB22_1A Block Diagram for AIR

1.2.59 RBB22_1B
RBB22_1B is used for sectors with two TX branches, two RX branches, and one CPRI connection. This RBB is supported for
MSMM configurations.
Note: It is also possible to use only one TX branch.
Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.

For mixed mode and Multi-Operator RAN LTE + LTE configurations, Data 2 port can be used. For more information, see
CPRI Connections from DU or Baseband to Radio in Fronthaul.
about:blank 51/268
3/5/24, 9:34 AM Building Blocks
Figure 102 shows the RBB22_1B block diagram.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Other Node Data B
or Cascade

Ge13109C

Figure 102 RBB22_1B Block Diagram

1.2.60 RBB22_1C
RBB22_1C is used for sectors with two TX branches, two RX branches, and one CPRI connection. This RBB uses a digital
RX cross-connection. This RBB is supported for MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
Figure 103 shows the RBB22_1C block diagram.
Figure 104 shows the RBB22_1C block diagram for AIR.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1
Data

2: TX B / RX B
Data A
Radio 2
Other Node
Data
or Cascade

Ge13122C

Figure 103 RBB22_1C Block Diagram

about:blank 52/268
3/5/24, 9:34 AM Building Blocks

RI Link
AIR Unit RF Branch
1: TX A / RX A
Node 1 Data A
AIR 1
Data

2: TX B / RX B
Data A
AIR 2
Other Node
Data
or Cascade

HW unit including ABB

Ge13124C

Figure 104 RBB22_1C Block Diagram for AIR

1.2.61 RBB22_1F
RBB22_1F is used for sectors with two TX branches, two RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Data
Other Radio 1 2: TX B / RX B
Data B
Node(s) or
Cascade Data

Ge26423A

Figure 105 RBB22_1F Block Diagram

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: TX B / RX B
B
Other Node Data
or Cascade

Ge13144C

Figure 106 Example of RBB22_1F for Radio Units with Two Data Ports

about:blank 53/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch RF Branch

Node 1 Data
1A 1: TX A / RX A
A

2A 2: TX B / RX B
B
Radio 1 1B
(virtual port) E

2B
(virtual port) F
Other Node Data
or Cascade

Ge19670B

Figure 107 RBB22_1F Block Diagram for Radio 4449 B5 B13

1.2.62 RBB22_1G
RBB22_1G is used for sectors with two TX branches, two RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB22_1G is used together with RBB22_1F.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
C
Data
Other Radio 1 2: TX B / RX B
Data D
Node(s) or
Cascade Data

Ge26402A

Figure 108 RBB22_1G Block Diagram

RI Link RF Branch

Node 1 Data
1: TX A / RX A
C
Radio 1 2: TX B / RX B
D
Other Node Data
or Cascade

Ge13145C

Figure 109 Example of RBB22_1G for Radio Units with Two Data Ports

about:blank 54/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch RF Branch

Node 1 Data
1A 1: TX A / RX A
C

2A 2: TX B / RX B
D
Radio 1 1B
(virtual port) G

2B
(virtual port) H
Other Node Data
or Cascade

Ge19671B

Figure 110 RBB22_1G Block Diagram for Radio 4449 B5 B13

1.2.63 RBB22_1H
RBB22_1H is used for sectors with two TX branches, two RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB22_1H is used together with RBB22_1F and RBB22_1G.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
E
Data
Other Radio 1 2: TX B / RX B
Data F
Node(s) or
Cascade Data

Ge26403A

Figure 111 RBB22_1H Block Diagram

RI Link RF Branch

Node 1 Data
1: TX A / RX A
E
Radio 1 2: TX B / RX B
F
Other Node Data
or Cascade

Ge13146C

Figure 112 Example of RBB22_1H for Radio Units with Two Data Ports

1.2.64 RBB22_1J
RBB22_1J is used for sectors with two TX branches, two RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 55/268
3/5/24, 9:34 AM Building Blocks
RBB22_1J is used together with RBB22_1F, RBB22_1G and RBB22_1H.

RI Link RF Branch

Node 1 Data

1: TX A / RX A
Other Node G
Data
or Cascade
Radio 1
Data 2: TX B / RX B
Other H
Node(s)
Data

Ge28006A

Figure 113 RBB22_1J Block Diagram

RI Link RF Branch

Node 1 Data
1: TX A / RX A
G
Radio 1 2: TX B / RX B
H
Other Node Data
or Cascade

Ge13147C

Note: The number of available data ports depends on the used radio.

Figure 114 RBB22_1J with Two Data Ports

1.2.65 RBB22_1K
RBB22_1K is used for sectors with two TX branches, two RX branches, and one CPRI connection. This RBB is used for high
output power mode.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Other Node Data D
or Cascade

Ge13691C

Figure 115 RBB22_1K Block Diagram

about:blank 56/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1A 1: TX A / RX A
Node 1 Data A

2A 2: TX B / RX B
D
Radio 1 1B
(virtual port) E

2B
Other Node Data (virtual port) H
or Cascade

Ge19672B

Figure 116 RBB22_1K Block Diagram for Radio 4449 B5 B13

1.2.66 RBB22_1L
RBB22_1L is used for sectors with two TX branches, two RX branches, and one CPRI connection.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: TX B / RX B
D
Other Node Data
or Cascade

Ge14173C

Figure 117 RBB22_1L Block Diagram

1.2.67 RBB22_1M
RBB22_1M is used for sectors with two TX branches, two RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
E
Radio 1 2: TX B / RX B
H
Other Node Data
or Cascade

Ge14174C

Figure 118 RBB22_1M Block Diagram

1.2.68 RBB22_1N

about:blank 57/268
3/5/24, 9:34 AM Building Blocks
RBB22_1N is used for sectors with two TX branches, two RX branches, and one CPRI connection. This RBB is used for high
output power mode.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Other Node Data C
or Cascade

Ge16133C

Figure 119 RBB22_1N Block Diagram

1.2.69 RBB22_1P
RBB22_1P is used for sectors with two TX branches, two RX branches, and one CPRI connection.
RF A and RF C ports are used in this RBB.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: TX B / RX B
C
Other Node Data
or Cascade

Ge19812B

Figure 120 RBB22_1P Block Diagram

1.2.70 RBB22_1Q
RBB22_1Q is used for sectors with two TX branches, two RX branches, and one CPRI connection.
RF A and RF C ports are used in this RBB.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
B
Radio 1 2: TX B / RX B
D
Other Node Data
or Cascade

Ge19813B

Figure 121 RBB22_1Q Block Diagram

1.2.71 RBB22_1R

RBB22_1R is used for sectors with two TX branches, two RX branches, and one CPRI connection.

about:blank 58/268
3/5/24, 9:34 AM Building Blocks
RF A and RF E ports are used in this RBB.

about:blank 59/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: TX B / RX B
E
Other Node Data
or Cascade

Ge28159A

about:blank 60/268
3/5/24, 9:34 AM Building Blocks

Figure 122 RBB22_1R Block Diagram

1.2.72 RBB22_1S

RBB22_1S is used for sectors with two TX branches, two RX branches, and one CPRI connection.
RF B and RF F ports are used in this RBB.

about:blank 61/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
B
Radio 1 2: TX B / RX B
F
Other Node Data
or Cascade

Ge28160A

about:blank 62/268
3/5/24, 9:34 AM Building Blocks

Figure 123 RBB22_1S Block Diagram

1.2.73 RBB22_1T

RBB22_1T is used for sectors with two TX branches, two RX branches, and one CPRI connection.
RF C and RF G ports are used in this RBB.

about:blank 63/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
C
Radio 1 2: TX B / RX B
G
Other Node Data
or Cascade

Ge28161A

about:blank 64/268
3/5/24, 9:34 AM Building Blocks

Figure 124 RBB22_1T Block Diagram

1.2.74 RBB22_1U

RBB22_1U is used for sectors with two TX branches, two RX branches, and one CPRI connection.
RF D and RF H ports are used in this RBB.

about:blank 65/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
D
Radio 1 2: TX B / RX B
H
Other Node Data
or Cascade

Ge28162A

about:blank 66/268
3/5/24, 9:34 AM Building Blocks

Figure 125 RBB22_1U Block Diagram

1.2.75 RBB22_2A
RBB22_2A is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection. This RBB is supported for MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1
Data

2: TX B / RX B
Data A
Other Node(s) Radio 2
or Cascade Data

Ge13123C

Figure 126 RBB22_2A Block Diagram

RI Link RF Branch
AIR Unit
1: TX A / RX A
Data A
AIR 1

Node 1
2: TX B / RX B
A
AIR 2
Data

HW unit including ABB

Ge26404A

Figure 127 RBB22_2A Block Diagram for AIR

1.2.76 RBB22_2B
RBB22_2B is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB uses an
analog RX cross-connection. This RBB is supported for MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
For mixed mode, Data 2 port can be used. For more information, see CPRI Connections from DU or Baseband to Radio in
Fronthaul.

about:blank 67/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1

Radio 1 RXA I/O

Data RXB I/O

RF Branch 2
2: TX B / RX B
Data A

RF Branch 1
Radio 2 RXA I/O
Other Node(s)
or Cascade Data RXB I/O

Ge13137C

Figure 128 RBB22_2B Block Diagram

RI Link RF Branch
AIR Unit
1: TX A / RX A
Data A

AIR 1 RXA I/O

RXB I/O
RF Branch 2

Node 1
2: TX B / RX B
A
RF Branch 1

AIR 2 RXA I/O

Data RXB I/O

HW unit including ABB

Ge26405A

Figure 129 RBB22_2B Block Diagram for AIR

1.2.77 RBB22_2C
RBB22_2C is used for sectors with two TX branches, two RX branches, and two CPRI connections.
With DUG 20, this RBB is used for ring topology in GSM.
Figure 130 shows the RBB22_2C block diagram.

about:blank 68/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 Radio 1 2: TX B / RX B
Data B

Ge13110C

Figure 130 RBB22_2C Block Diagram

1.2.78 RBB22_2D
RBB22_2D is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB uses an
analog RX cross-connection.
This RBB is used for ring topology in GSM.
Figure 131 shows the RBB22_2D block diagram.

RI Link RF Branch

1: TX A / RX A
Data A

Radio 1 RXA I/O

Data RXB I/O

RF Branch 2

Node 1
2: TX B / RX B
Data A
RF Branch 1

Radio 2 RXA I/O

Data RXB I/O

Ge14175C

Figure 131 RBB22_2D Block Diagram

1.2.79 RBB22_2E
RBB22_2E is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB is supported
for MSMM configurations.
This RBB can be used with the Multi-Sector Per Radio feature.
This RBB is used for Cross-Sector Antenna Sharing Redundancy and cascade configurations.
For mixed mode, Data 2 port can be used. For more information, see CPRI Connections from DU or Baseband to Radio in
Fronthaul.
Figure 132 shows the RBB22_2E block diagram.

about:blank 69/268
3/5/24, 9:34 AM Building Blocks

Shared with
RBB for
previous sector

RI Link RF Branch

Data
Node 1 1: TX A / RX A
Radio 1 A
Data

Data
2: TX B / RX B
Other Node Radio 2 B
or Cascade Data

Shared with
RBB for next
sector
Ge14142C

Figure 132 RBB22_2E Block Diagram

1.2.80 RBB22_2J
RBB22_2J is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB uses an analog
RX cross-connection. This RBB is supported for MSMM configurations.
Figure 133 shows the RBB22_2J block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1

Radio 1 RXA Out

Data RXB I/O

RF Branch 2

2: TX B / RX B
Data A
RF Branch 1

Radio 2 RXA Out

Other Node
or Cascade Data RXB I/O

Ge14143C

Figure 133 RBB22_2J Block Diagram

1.2.81 RBB22_2K
RBB22_2K is used for sectors with two TX branches, two RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
about:blank 70/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
Node 1 A
Data
Radio 1 2: TX B / RX B
Data B
Other
Node(s) or Data
Cascade

Ge26406A

Figure 134 RBB22_2K Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
A
Node 1 Radio 1 2: TX B / RX B
B
Data

Ge14144C

Figure 135 Example of RBB22_2K for Radio Units with Two Data Ports

RI Link RF Branch RF Branch

Data
1A 1: TX A / RX A
A

2A 2: TX B / RX B
B
Node 1 Radio 1 1B
(virtual port) E

2B
(virtual port) F
Data

Ge19673B

Figure 136 RBB22_2K Block Diagram for Radio 4449 B5 B13

1.2.82 RBB22_2L
RBB22_2L is used for sectors with two TX branches, two RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB22_2L is used together with RBB22_2K.

about:blank 71/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
Node 1 C
Data
Radio 1 2: TX B / RX B
Data D
Other
Node(s) or Data
Cascade

Ge26407A

Figure 137 RBB22_2L Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
C
Node 1 Radio 1 2: TX B / RX B
D
Data

Ge14145C

Figure 138 Example of RBB22_2L for Radio Units with Two Data Ports

RI Link RF Branch RF Branch

Data
1A 1: TX A / RX A
C

2A 2: TX B / RX B
D
Node 1 Radio 1 1B
(virtual port) G

2B
(virtual port) H
Data

Ge19674B

Figure 139 RBB22_2L Block Diagram for Radio 4449 B5 B13

1.2.83 RBB22_2M
RBB22_2M is used for sectors with two TX branches, two RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB22_2M is used together with RBB22_2K and RBB22_2L.

about:blank 72/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
Node 1 E
Data
Radio 1 2: TX B / RX B
Data F
Other
Node(s) or Data
Cascade

Ge26408A

Figure 140 RBB22_2M Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
E
Node 1 Radio 1 2: TX B / RX B
F
Data

Ge14146C

Figure 141 Example of RBB22_2M for Radio Units with Two Data Ports

1.2.84 RBB22_2N
RBB22_2N is used for sectors with two TX branches, two RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB22_2N is used together with RBB22_2K, RBB22_2L and RBB22_2M.
Figure 142 shows the RBB22_2N block diagram.

RI Link RF Branch

Data

Node 1 1: TX A / RX A
G
Data
Radio 1
Data 2: TX B / RX B
Other H
Node(s)
Data

Ge28007A

Figure 142 RBB22_2N Block Diagram

Note: The number of available data ports depends on the used radio unit.

about:blank 73/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
G
Node 1 Radio 1 2: TX B / RX B
H
Data

Ge14147C

Figure 143 Example of RBB22_2N for Radio Unit with Two Data Ports

1.2.85 RBB22_2P
RBB22_2P is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB is used for high
output power mode.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 Radio 1 2: TX B / RX B
Data D

Ge13692C

Figure 144 RBB22_2P Block Diagram

RI Link RF Branch
RF Branch
1A 1: TX A / RX A
Data A

2A 2: TX B / RX B
D
Node 1 Radio 1 1B
(virtual port) E

2B
Data (virtual port) H

Ge19675B

Figure 145 RBB22_2P Block Diagram for Radio 4449 B5 B13

1.2.86 RBB22_2Q
RBB22_2Q is used for sectors with two TX branches, two RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 74/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
A
Node 1 Radio 1 2: TX B / RX B
D
Data

Ge14190C

Figure 146 RBB22_2Q Block Diagram

1.2.87 RBB22_2R
RBB22_2R is used for sectors with two TX branches, two RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

RI Link RF Branch

Data
1: TX A / RX A
E
Node 1 Radio 1 2: TX B / RX B
H
Data

Ge14191C

Figure 147 RBB22_2R Block Diagram

1.2.88 RBB22_2S
RBB22_2S is used for sectors with two TX branches, two RX branches, and two CPRI connections. This RBB is used for high
output power mode.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 Radio 1 2: TX B / RX B
Data C

Ge16134C

Figure 148 RBB22_2S Block Diagram

1.2.89 RBB22_2T
RBB22_2T is used for sectors with two TX branches, two RX branches, and two CPRI connections.
RF A and RF C ports are used in this RBB.

about:blank 75/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
A
Node 1 Radio 1 2: TX B / RX B
C
Data

Ge19814B

Figure 149 RBB22_2T Block Diagram

1.2.90 RBB22_2U
RBB22_2U is used for sectors with two TX branches, two RX branches, and two CPRI connections.
RF A and RF C ports are used in this RBB.

RI Link RF Branch

Data
1: TX A / RX A
B
Node 1 Radio 1 2: TX B / RX B
D
Data

Ge19815B

Figure 150 RBB22_2U Block Diagram

1.2.91 RBB22_2V

RBB22_2V is used for sectors with two TX branches, two RX branches, and two CPRI connections.
RF A and RF E ports are used in this RBB.

about:blank 76/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
A
Node 1 Radio 1 2: TX B / RX B
E
Data

Ge28163A

about:blank 77/268
3/5/24, 9:34 AM Building Blocks

Figure 151

1.2.92 RBB22_2W

RBB22_2W is used for sectors with two TX branches, two RX branches, and two CPRI connections.
RF B and RF F ports are used in this RBB.

about:blank 78/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
B
Node 1 Radio 1 2: TX B / RX B
F
Data

Ge28164A

about:blank 79/268
3/5/24, 9:34 AM Building Blocks

Figure 152

1.2.93 RBB22_2X

RBB22_2X is used for sectors with two TX branches, two RX branches, and two CPRI connections.
RF C and RF G ports are used in this RBB.

about:blank 80/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
C
Node 1 Radio 1 2: TX B / RX B
G
Data

Ge28165A

about:blank 81/268
3/5/24, 9:34 AM Building Blocks

Figure 153 RBB22_2X Block Diagram

1.2.94 RBB22_2Y

RBB22_2Y is used for sectors with two TX branches, two RX branches, and two CPRI connections.
RF D and RF H ports are used in this RBB.

about:blank 82/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
D
Node 1 Radio 1 2: TX B / RX B
H
Data

Ge28166A

about:blank 83/268
3/5/24, 9:34 AM Building Blocks

Figure 154 RBB22_2Y Block Diagram

1.2.95 RBB22_3A
RBB22_3A is used for sectors with two TX branches, two RX branches, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 155 shows the RBB22_3A block diagram.

RI Link RF Branch

Data
1: TX A / RX A
A
Node 1 Data
Radio 1 2: TX B / RX B
Data B
Other Node
Data
or Cascade

Ge25812

Figure 155 RBB22_3A Block Diagram

1.2.96 RBB22_3B
RBB22_3B is used for sectors with two TX branches, two RX branches, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 156 shows the RBB22_3B block diagram.

RI Link RF Branch

Data
1: TX A / RX A
C
Node 1 Data
Radio 1 2: TX B / RX B
Data D
Other Node
Data
or Cascade

Ge25813

Figure 156 RBB22_3B Block Diagram

1.2.97 RBB22_3C
RBB22_3C is used for sectors with two TX branches, two RX branches, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 157 shows the RBB22_3C block diagram.

about:blank 84/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
E
Node 1 Data
Radio 1 2: TX B / RX B
Data F
Other Node
Data
or Cascade

Ge25814

Figure 157 RBB22_3C Block Diagram

1.2.98 RBB22_3D

RBB22_3D is used for sectors with two TX branch, two RX branch, and three CPRI connections. RF G and RF H ports are
used in this RBB.

RI Link RF Branch

Data

1: TX A / RX A
G
Node 1 Data
Radio 1
Data 2: TX B / RX B
H

Other Node Data

Ge28008A

Figure 158 RBB22_3D Block Diagram

1.2.99 RBB22_4A
RBB22_4A is used for sectors with two TX branches, two RX branches, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 159 shows the RBB22_4A block diagram.

RI Link RF Branch

Data
1: TX A / RX A
A
Data
Node 1 Radio 1 2: TX B / RX B
Data B

Data

Ge25815

Figure 159 RBB22_4A Block Diagram

1.2.100 RBB22_4B

about:blank 85/268
3/5/24, 9:34 AM Building Blocks
RBB22_4B is used for sectors with two TX branches, two RX branches, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 160 shows the RBB22_4B block diagram.

RI Link RF Branch

Data
1: TX A / RX A
C
Data
Node 1 Radio 1 2: TX B / RX B
Data D

Data

Ge25816

Figure 160 RBB22_4B Block Diagram

1.2.101 RBB22_4C
RBB22_4C is used for sectors with two TX branches, two RX branches, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 161 shows the RBB22_4C block diagram.

RI Link RF Branch

Data
1: TX A / RX A
E
Data
Node 1 Radio 1 2: TX B / RX B
Data F

Data

Ge25817

Figure 161 RBB22_4C Block Diagram

1.2.102 RBB22_4D

RBB22_4D is used for sectors with two TX branch, two RX branch, and four CPRI connections. RF G and RF H ports are
used in this RBB.

RI Link RF Branch

Data

1: TX A / RX A
G
Data
Node 1 Radio 1
Data 2: TX B / RX B
H

Data

Ge28009A

Figure 162 RBB22_4D Block Diagram

about:blank 86/268
3/5/24, 9:34 AM Building Blocks

1.2.103 RBB24_1A
RBB24_1A is used for sectors with two TX branches, four RX branches, and one CPRI connection. This RBB uses a digital
RX cross-connection. This RBB is supported for MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
For mixed mode and Multi-Operator RAN LTE + LTE configurations, Data 2 port can be used. For more information, see
CPRI Connections from DU or Baseband to Radio in Fronthaul.
Figure 163 shows the RBB24_1A block diagram.
Figure 164 shows the RBB24_1A block diagram for AIR.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: RX B
Data B

3: TX C / RX C
Data A
Radio 2 4: RX D
Other Node
Data B
or Cascade

Ge13125C

Figure 163 RBB24_1A Block Diagram

RI Link
AIR Unit RF Branch
1: TX A / RX A
Node 1 Data A
AIR 1 2: RX B
Data B

3: TX C / RX C
Data A
AIR 2 4: RX D
Other Node
Data B
or Cascade

HW unit including ABB

Ge13127C

Figure 164 RBB24_1A Block Diagram for AIR

1.2.104 RBB24_1B
RBB24_1B is used for sectors with two TX branches, four RX branches, and one CPRI connection. This RBB uses a digital
RX cross-connection. This RBB is supported for MSMM configurations.
One of the radios in this RBB is an RX-only capable radio.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.

about:blank 87/268
3/5/24, 9:34 AM Building Blocks
For mixed mode and Multi-Operator RAN LTE + LTE configurations, Data 2 port can be used. For more information, see
CPRI Connections from DU or Baseband to Radio in Fronthaul.
Figure 165 shows the RBB24_1B block diagram.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data B

3: RX C
Data A
Radio 2 4: RX D
Other Node
Data B
or Cascade

Ge13128C

Figure 165 RBB24_1B Block Diagram

1.2.105 RBB24_1C
RBB24_1C is used for sectors with two TX branches, four RX branches, and one CPRI connection. This RBB is supported for
MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
Figure 166 shows the RBB24_1C block diagram.
Figure 167 shows the RBB24_1C block diagram for AIR.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
Radio 1 3: RX C
C

Other Node 4: RX D
Data D
or Cascade

Ge13111C

Figure 166 RBB24_1C Block Diagram

about:blank 88/268
3/5/24, 9:34 AM Building Blocks

RI Link
AIR Unit RF Branch
1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
AIR 1 3: RX C
C

Other Node 4: RX D
Data D
or Cascade

HW unit including ABB

Ge14148C

Figure 167 RBB24_1C Block Diagram for AIR

1.2.106 RBB24_1D
RBB24_1D is used for sectors with two TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 168 shows the RBB block diagram.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: TX B / RX B
B
Data

3: RX C
Data A
Radio 2 4: RX D
Other Node
Data B
or Cascade

Ge17262C

Figure 168 RBB24_1D Block Diagram

1.2.107 RBB24_2A
RBB24_2A is used for sectors with two TX branches, four RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection. This RBB is supported for MSMM configurations.
Figure 169 shows the RBB24_2A block diagram.

about:blank 89/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: RX B
Data B

3: TX C / RX C
Data A
Other
Radio 2 4: RX D
Node(s) or
Data B
Cascade

Ge13126C

Figure 169 RBB24_2A Block Diagram

RI Link
AIR Unit RF Branch
1: TX A / RX A
Data A
AIR 1 2: RX B
B

Node 1
3: TX C / RX C
A
AIR 2 4: RX D
Data B

HW unit including ABB

Ge26409A

Figure 170 RBB24_2A Block Diagram for AIR

1.2.108 RBB24_2B
RBB24_2B is used for sectors with two TX branches, four RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection. This RBB is supported for MSMM configurations.
One of the radios in this RBB is an RX-only capable radio.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
Figure 171 shows the RBB24_2B block diagram.

about:blank 90/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data B

3: RX C
Data A
Other
Radio 2 4: RX D
Node(s) or
Data B
Cascade

Ge13129C

Figure 171 RBB24_2B Block Diagram

1.2.109 RBB24_2D
RBB24_2D is used for sectors with two TX branches, four RX branches, and two CPRI connections. This RBB is supported
for MSMM configurations.
Figure 172 shows the RBB24_2D block diagram.
Figure 173 shows the RBB24_2D block diagram for AIR.

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
B
Node 1 Radio 1 3: RX C
C

4: RX D
Data D

Ge13112C

Figure 172 RBB24_2D Block Diagram

about:blank 91/268
3/5/24, 9:34 AM Building Blocks

RI Link
AIR Unit RF Branch
1: TX A / RX A
Data A

2: TX B / RX B
B
Node 1 AIR 1 3: RX C
C

4: RX D
Data D

HW unit including ABB

Ge14192C

Figure 173 RBB24_2D Block Diagram for AIR

1.2.110 RBB24_2E
RBB24_2E is used for sectors with two TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 174 shows the RBB block diagram.

RI Link RF Branch

Data
Node 1 1: TX A / RX A
A
Radio 1 2: TX B / RX B
B
Data

3: RX C
Data A
Other Node(s) Radio 2 4: RX D
or Cascade Data B

Ge17263C

Figure 174 RBB24_2E Block Diagram

1.2.111 RBB24_2F
RBB24_2F is used for sectors with two TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 175 shows the RBB block diagram.

about:blank 92/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
Node 1 1: TX A / RX A
C
Radio 1 2: TX B / RX B
D

Shared with
RBB for
previous sector 3: RX C
Data A
Radio 2 4: RX D
Other Node
Data B
or Cascade

Ge17264C

Figure 175 RBB24_2F Block Diagram

1.2.112 RBB32_1A
RBB32_1A is used for sectors with three TX branches, two RX branches, and one CPRI connection. This RBB uses an
analog RX cross-connection.
Figure 176 shows the RBB32_1A block diagram.

about:blank 93/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

RXA Out
Radio 1
RXA I/O

Data RXB I/O

RF Branch 2
2: TX B / RX B
Data A

RXA Out
Radio 2

RF Branch 1
RXA I/O

Data RXB I/O

RF Branch 2
3: TX C

Data A

Radio 3 RF Branch 1

RXA I/O

Other Node
Data RXB I/O
or Cascade

Ge14149C

Figure 176 RBB32_1A Block Diagram

1.2.113 RBB32_1B
RBB32_1B is used for sectors with three TX branches, two RX branches and one external RX cross connection, and one
CPRI connection. This RBB uses an analog RX cross-connection.
Figure 177 shows the RBB32_1B block diagram.

about:blank 94/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data 1 A

RXA Out
Radio 1
RXA I/O

RF Branch 1
Data RXB I/O

2: TX B / RX B
Data A

RF Branch 2
Radio 2
RXA I/O

Data RXB I/O

3: TX C

Data A

RF Branch 1
Radio 3
RXA I/O

Other Node 4: RX C
Data RXB I/O
or Cascade

Ge14150C

Figure 177 RBB32_1B Block Diagram

1.2.114 RBB32_3A
RBB32_3A is used for sectors with three TX branches, two RX branches, and three CPRI connections. This RBB uses an
analog RX cross-connection.
Figure 178 shows the RBB32_3A block diagram.

about:blank 95/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
RXA Out
Radio 1
RXA I/O

Data RXB I/O

RF Branch 2
2: TX B / RX B
Data A

RXA Out
Radio 2

RF Branch 1
RXA I/O

Data RXB I/O

RF Branch 2
3: TX C

Data A

RF Branch 1
Radio 3
RXA I/O
Other Node(s)
or Cascade
Data RXB I/O

Ge14151C

Figure 178 RBB32_3A Block Diagram

1.2.115 RBB32_3B
RBB32_3B is used for sectors with three TX branches, two RX branches and one external RX cross connection, and three
CPRI connections. This RBB uses an analog RX cross-connection.
Figure 179 shows the RBB32_3B block diagram.

about:blank 96/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
RXA Out
Radio 1
RXA I/O

RF Branch 1
Data RXB I/O

2: TX B / RX B
Data A

RF Branch 2
Radio 2
RXA I/O

Data RXB I/O

3: TX C

Data A

Radio 3 RF Branch 1

RXA I/O
Other Node(s)
or Cascade 4: RX C
Data RXB I/O

Ge14152C

Figure 179 RBB32_3B Block Diagram

1.2.116 RBB40_1A
RBB40_1A is used for sectors with four TX branches and one CPRI connection.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 180 shows the RBB40_1A block diagram.

about:blank 97/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A
Node 1 Data A

2: TX B
B
Radio 1 3: TX C
C

4: TX D
Other Node Data D
or Cascade

Ge14153C

Figure 180 RBB40_1A Block Diagram

1.2.117 RBB40_1B
RBB40_1B is used for sectors with four TX branches and one CPRI connection.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF branches are
defined in software, are important.
Figure 181 shows the RBB40_1B block diagram.

RI Link RF Branch

1: TX A
Node 1 Data A
Radio 1 2: TX B
Data B

3: TX C
Data A
Radio 2 4: TX D
Other Node
Data B
or Cascade

Ge23009B

Figure 181 RBB40_1B Block Diagram

1.2.118 RBB40_1C
RBB40_1C is used for sectors with four TX branches, four I/Os for diplexing and one CPRI connection.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
For examples of connecting other RBBs to the diplexer I/Os, see Radio-Integrated Diplexer in Features for Radio
Configurations.
Figure 182 shows the RBB40_1C block diagram.

about:blank 98/268
3/5/24, 9:34 AM Building Blocks

Radio(s) in connected
RBB

RF Branch 4

RF Branch 3

RF Branch 2

RF Branch 1
RI Link RF Branch
1: TX A
Node 1 Data A

Diplex A IN
Radio 1
Diplex B IN

2: TX B
Data B

3: TX C
Data A

Diplex A IN
Radio 2
Diplex B IN

Other Node 4: TX D
Data B
or Cascade

Ge23010B

Figure 182 RBB40_1C Block Diagram

1.2.119 RBB40_2A
RBB40_2A is used for sectors with four TX branches and two CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 183 shows the RBB40_2A block diagram.

about:blank 99/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A
Data A

2: TX B
B
Node 1 Radio 1 3: TX C
C

4: TX D
Data D

Ge14155B

Figure 183 RBB40_2A Block Diagram

1.2.120 RBB40_2B
RBB40_2B is used for sectors with four TX branches and two CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 184 shows the RBB40_2B block diagram.

RI Link RF Branch

1: TX A
Data A
Node 1
Radio 1 2: TX B
Data B

3: TX C
Data A
Other Node(s) Radio 2 4: TX D
or Cascade Data B

Ge23011B

Figure 184 RBB40_2B Block Diagram

1.2.121 RBB40_2C
RBB40_2C is used for sectors with four TX branches, four I/Os for diplexing and two CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
For examples of connecting other RBBs to the diplexer I/Os, see Radio-Integrated Diplexer in Features for Radio
Configurations.
Figure 185 shows the RBB40_2C block diagram.

about:blank 100/268
3/5/24, 9:34 AM Building Blocks

Radio(s) in connected
RBB

RF Branch 4

RF Branch 3

RF Branch 2

RF Branch 1
RI Link RF Branch
1: TX A
Data A
Node 1

Diplex A IN
Radio 1
Diplex B IN

2: TX B
Data B

3: TX C
Data A

Diplex A IN
Radio 2
Diplex B IN

4: TX D
Data B

Ge23012B

Figure 185 RBB40_2C Block Diagram

1.2.122 RBB42_1B
RBB42_1B is used for sectors with four TX branches, two RX branches, and one CPRI connection. This RBB uses an analog
RX cross-connection.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.
Figure 186 shows the RBB42_1B block diagram.

about:blank 101/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B
B
Radio 1
RXA I/O

Data RXB I/O

RF Branch 3
3: TX C / RX C

Data A

4: TX D
B
Radio 2

RF Branch 1
RXA I/O

Other Node
Data RXB I/O
or Cascade

Ge13139C

Figure 186 RBB42_1B Block Diagram

1.2.123 RBB42_2D
RBB42_2D is used for sectors with four TX branches, two RX branches and two CPRI connections. This RBB uses an analog
RX cross-connection. This RBB is supported for MSMM configurations.
For mixed mode, Data 2 port can be used. For more information, see Fronthaul.
Note: LTE can use either two or four TX branches with this RBB. When using only two TX branches it must be specified
which of the four TX capable RF branches that are used by setting the rfBranchTxRef attribute for each
SectorCarrier on the branch. Which two to use is freely selectable in order to utilize available power best per each
port in mixed mode. For RX it is advisable to select RF A on each radio unit by using the rfBranchRxRef attribute for
each SectorCarrier on the branch, or by setting the RfBranchId to "any_string"_NO_TX for the branches
connected to RF B, as specified in the LTE MOM for Managed Object RfBranch.
Figure 187 shows the RBB42_2D block diagram.

about:blank 102/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
2: TX B
B
Radio 1
RXA I/O

Data RXB I/O

RF Branch 3
3: TX C / RX C

Data A

4: TX D
B
Radio 2

RF Branch 1
RXA I/O
Other
Node(s) or Data RXB I/O
Cascade

Ge14157C

Figure 187 RBB42_2D Block Diagram

1.2.124 RBB42_2E
RBB42_2E is used for sectors with four TX branches, two RX branches, and two CPRI connections. This RBB uses an
analog RX cross-connection.
This RBB is used for ring topology in GSM.
Figure 188 shows the RBB42_2E block diagram.

about:blank 103/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B
B
Radio 1
RXA I/O

Data RXB I/O

RF Branch 3
Node 1
3: TX C / RX C
Data A

4: TX D
B
Radio 2

RF Branch 1
RXA I/O

Data RXB I/O

Ge14158C

Figure 188 RBB42_2E Block Diagram

1.2.125 RBB43_1A
RBB43_1A is used for sectors with four TX branches, three RX branches, and one CPRI connection. This RBB uses an
analog RX cross-connection.
Figure 189 shows the RBB43_1A block diagram.

about:blank 104/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

RXA Out
Radio 1
RXA I/O

Data RXB I/O

RF Branch 2
2: TX B / RX B
Data A

RXA Out
Radio 2

RF Branch 1
RXA I/O

Data RXB I/O

3: TX C
Data A

RF Branch 1
Radio 3
RXA I/O

Data RXB I/O

4: TX D / RX D
Data A
RF Branch 4

Radio 4
RF Branch 2

RXA I/O

Other Node
Data RXB I/O
or Cascade

Ge14159C

Figure 189 RBB43_1A Block Diagram

1.2.126 RBB43_4A
RBB43_4A is used for sectors with four TX branches, three RX branches, and four CPRI connections. This RBB uses an
analog RX cross-connection.
Figure 190 shows the RBB43_4A block diagram.

about:blank 105/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch
1: TX A / RX A
Data A

Node 1
RXA Out
Radio 1
RXA I/O

Data RXB I/O

RF Branch 2
2: TX B / RX B
Data A

RXA Out
Radio 2

RF Branch 1
RXA I/O

Data RXB I/O

3: TX C
Data A

RF Branch 1
Radio 3
RXA I/O

Data RXB I/O

4: TX D / RX D
Data A
RF Branch 4

Radio 4
RF Branch 2

Other RXA I/O

Node(s) or
Cascade
Data RXB I/O

Ge14160C

Figure 190 RBB43_4A Block Diagram

1.2.127 RBB44_1B
RBB44_1B is used for sectors with four TX branches, four RX branches, and one CPRI connection. This RBB uses digital RX
cross-connection.

about:blank 106/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Other Node
Data B
or Cascade

Ge13130C

Figure 191 RBB44_1B Block Diagram

1.2.128 RBB44_1D
RBB44_1D is used for sectors with four TX branches, four RX branches, and one CPRI connection. This RBB is supported for
MSMM configurations.
Note: Supports flexible carrier allocation. Carriers can be freely allocated to any TX ports.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

Other Node 2: TX B / RX B
Data B
or Cascade
Radio 1
3: TX C / RX C
Data C
Other
Node(s) 4: TX D / RX D
Data D

Ge28012A

Figure 192 RBB44_1D Block Diagram

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
Other Node Data D
or Cascade

Ge13113C

Figure 193 Example of RBB44_1D for Radio Units with Two Data Ports

about:blank 107/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1A 1: TX A / RX A
Node 1 Data A

2A 2: TX B / RX B
B

3A 3: TX C / RX C
C

4A 4: TX D / RX D
Other Node Data D
or Cascade
Radio 1 1B
(virtual port) E

2B
(virtual port) F

3B
(virtual port) G

4B
(virtual port) H

Ge19676B

Figure 194 RBB44_1D Block Diagram for Radio 4449 B5 B13

RI Link RF Branch
AIR Unit
1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
AIR 1 3: TX C / RX C
C

4: TX D / RX D
Other Node Data D
or Cascade

HW unit including ABB

Ge13115C

Figure 195 RBB44_1D Block Diagram for AIR

1.2.129 RBB44_1E
RBB44_1E is used for sectors with four TX branches, four RX branches, and one CPRI connection
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 108/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

Other Node 2: TX B / RX B
Data B
or Cascade
Radio 1
3: TX C / RX C
Data C
Other
Node(s) 4: TX D / RX D
Data D

Ge27990A

Note: Number of available data ports depends on the used radio unit.

Figure 196 RBB44_1E Block Diagram

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A

2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
D
Other Node Data
or Cascade

Ge13148C

Figure 197 Example of RBB44_1E for Radio Unit with Two Data Ports

1.2.130 RBB44_1F
RBB44_1F is used for sectors with four TX branches, four RX branches, and one CPRI connection
This RBB can be used with the Multi-Sector Per Radio feature.
RBB44_1F is used together with RBB44_1E.

RI Link RF Branch

1: TX A / RX A
Node 1 Data E

Other Node 2: TX B / RX B
Data F
or Cascade
Radio 1
3: TX C / RX C
Data G
Other
Node(s) 4: TX D / RX D
Data H

Ge28020A

Figure 198 RBB44_1F Block Diagram

Note: The number of available data ports depends on the used radio unit.
about:blank 109/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
E

2: TX B / RX B
F
Radio 1 3: TX C / RX C
G

4: TX D / RX D
H
Other Node Data
or Cascade

Ge13149C

Figure 199 Example of RBB44_1F for Radio Unit with Two Data Ports

1.2.131 RBB44_1G
RBB44_1G is used for sectors with four TX branches, four RX branches, and one CPRI connection. This RBB uses a digital
RX cross-connection.
Note: Cascading order is chosen for antenna polarization and timing purposes.
Figure 200 shows the RBB44_1G block diagram.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1
Data

2: TX B / RX B
Data A
Radio 2
Data

3: TX C / RX C
Data A
Radio 3
Data

4: TX D / RX D
Data A
Radio 4
Other Node
Data
or Cascade

Ge13132C

Figure 200 RBB44_1G Block Diagram

1.2.132 RBB44_1H
about:blank 110/268
3/5/24, 9:34 AM Building Blocks
RBB44_1H is used for sectors with four TX branches, four RX branches, and one CPRI connection. This RBB uses a digital
RX cross-connection. This RBB is used for high output power mode.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data D

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Other Node
Data D
or Cascade

Ge13693C

Figure 201 RBB44_1H Block Diagram

RI Link RF Branch RF Branch

1A 1: TX A / RX A
Node 1 Data A

2A 2: TX B / RX B
D
Radio 1 1B
(virtual port) E

2B
Data (virtual port) H

3A 3: TX C / RX C
Data A

4A 4: TX D / RX D
D
Radio 2 3B
(virtual port) E

Other Node 4B
Data (virtual port) H
or Cascade

Ge19677B

Figure 202 RBB44_1H Block Diagram for Radio 4449 B5 B13

1.2.133 RBB44_1J
RBB44_1J is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 111/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data D

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Other Node
Data D
or Cascade

Ge14162C

Figure 203 RBB44_1J Block Diagram

1.2.134 RBB44_1K
RBB44_1K is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.

RI Link RF Branch

1: TX A / RX A
Node 1 Data E
Radio 1 2: TX B / RX B
Data H

3: TX C / RX C
Data E
Radio 2 4: TX D / RX D
Other Node
Data H
or Cascade

Ge14163C

Figure 204 RBB44_1K Block Diagram

1.2.135 RBB44_1L
RBB44_1L is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 205 shows the RBB block diagram.
RBB44_1L is intended for use together with RBB44_2Q. For an example of a three sector configuration, see Figure 206.

about:blank 112/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A
Radio 1 2: TX B / RX B
B
Data

3: RX C
Data A
Radio 2 4: RX D
Data B

5: TX C
Data A
Radio 3 6: TX D
Other Node
Data B
or Cascade

Ge17265C

Figure 205 RBB44_1L Block Diagram

about:blank 113/268
3/5/24, 9:34 AM Building Blocks

Radio Antenna
S1-S2
-1
Antenna Sector 1

Radio
S1 - 2 Antenna

Radio
S1 - 3
Antenna

Radio
S2 - 2 Antenna Sector 2
Baseband
Radio
S2 - 3 Antenna

Radio Antenna
S3 - 1

Antenna Sector 3
Radio
S3 - 2
Antenna
Radio
S3 - 3

Ge17266B

Figure 206 A Three Sector Site using RBB44_1L, RBB44_2Q, and RBB44_1L

1.2.136 RBB44_1M
RBB44_1M is used for sectors with four TX branches, four RX branches, and one CPRI connection. This RBB is used for high
output power mode.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 207 shows the RBB44_1M block diagram.

about:blank 114/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data C

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Other Node
Data C
or Cascade

Ge16135C

Figure 207 RBB44_1M Block Diagram

1.2.137 RBB44_1N
RBB44_1N is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

Node 1 Data 1: TX A / RX A
A
Data
Data
Radio 1 2: TX B / RX B
B
Data

Other Data 3: TX C / RX C
A
Node(s) or Data
cascade Data
Radio 2 4: TX D / RX D
B
Data

Ge26412A

Figure 208 RBB44_1N Block Diagram

about:blank 115/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Other Node
Data B
or Cascade

Ge18926B

Figure 209 Example of RBB44_1N for Radio Units with Two Data Ports

1.2.138 RBB44_1P
RBB44_1P is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

Node 1 Data 1: TX A / RX A
C
Data
Data
Radio 1 2: TX B / RX B
D
Data

Other Data 3: TX C / RX C
C
Node(s) or Data
cascade Data
Radio 2 4: TX D / RX D
D
Data

Ge26413A

Figure 210 RBB44_1P Block Diagram

about:blank 116/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data C
Radio 1 2: TX B / RX B
Data D

3: TX C / RX C
Data C
Radio 2 4: TX D / RX D
Other Node
Data D
or Cascade

Ge18927B

Figure 211 Example of RBB44_1P for Radio Units with Two Data Ports

1.2.139 RBB44_1Q

RBB44_1Q is used for sectors with four TX branches, four RX branches, and one CPRI connection.
RF A, RF B, RF E and RF F ports are used in this RBB.
To optimize MIMO performance, consider the following important factors:

– Antenna polarization for each RF Branch

– The order in which the RF Branches are defined in software

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

Other Node 2: TX B / RX B
Data B
or Cascade
Radio 1
3: TX C / RX C
Data E
Other
Node(s) 4: TX D / RX D
Data F

Ge28021A

Figure 212 RBB44_1Q Block Diagram

Note: The number of available data ports depends on the used radio unit.

about:blank 117/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Node 1 Data
1: TX A / RX A
A

2: TX B / RX B
B

Radio 1 3: TX C / RX C
E

4: TX D / RX D
F
Other Node Data
or Cascade

Ge28167B

Figure 213 Example of RBB44_1Q for Radio Unit with Two Data Ports

1.2.140 RBB44_1R

RBB44_1R is used for sectors with four TX branches, four RX branches, and one CPRI connection.
RF C, RF D, RF G and RF H ports are used in this RBB.
To optimize MIMO performance, consider the following factors:

– Antenna polarization for each RF Branch

– The order in which the RF Branches are defined in software

RI Link RF Branch

1: TX A / RX A
Node 1 Data C

Other Node 2: TX B / RX B
Data D
or Cascade
Radio 1
3: TX C / RX C
Data G
Other
Node(s) 4: TX D / RX D
Data H

Ge28022A

Figure 214 RBB44_1R Block Diagram

Note: The number of available data ports depends on the used radio unit.

RI Link RF Branch

Node 1 Data
1: TX A / RX A
C

2: TX B / RX B
D

Radio 1 3: TX C / RX C
G

4: TX D / RX D
H
Other Node Data
or Cascade

Ge28168B

about:blank 118/268
3/5/24, 9:34 AM Building Blocks

Figure 215 Example of RBB44_1R for Radio Unit with Two Data Ports

1.2.141 RBB44_1S
RBB44_1S is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

Node 1 Data 1: TX A / RX A
E
Data
Data
Radio 1 2: TX B / RX B
F
Data

Other Data 3: TX C / RX C
E
Node(s) or Data
cascade Data
Radio 2 4: TX D / RX D
F
Data

Ge26506A

Figure 216 RBB44_1S Block Diagram

RI Link RF Branch

1: TX A / RX A
Node 1 Data E

Radio 1 2: TX B / RX B
Data F

3: TX C / RX C
Data E

Radio 2 4: TX D / RX D
Other node
Data F
or cascade

Ge27044A

Figure 217 Example of RBB44_1S for Radio Unit with Two Data Ports

1.2.142 RBB44_1T
RBB44_1T is used for sectors with four TX branches, four RX branches, and one CPRI connection.
This RBB can be used with the RF C, RF D, RF E, and RF F ports.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

about:blank 119/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data C

Other Node 2: TX B / RX B
Data D
or Cascade
Radio 1
3: TX C / RX C
Data E
Other
Node(s) 4: TX D / RX D
Data F

Ge27991A

Note: Number of available data ports depends on the used radio unit.

Figure 218 RBB44_1T Block Diagram

RI Link RF Branch

1: TX A / RX A
Node 1 Data C

2: TX B / RX B
D
Radio 1
3: TX C / RX C
E

Other Node 4: TX D / RX D
Data F
or Cascade

Ge27319A

Figure 219 Example of RBB44_1T for Radio Unit with Two Data Ports

1.2.143 RBB44_2C
RBB44_2C is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB uses digital
RX cross-connection. This RBB is supported for MSMM configurations.
Figure 220 shows the RBB44_2C block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Other Node(s) Radio 2 4: TX D / RX D
or Cascade Data B

Ge13131C

Figure 220 RBB44_2C Block Diagram

about:blank 120/268
3/5/24, 9:34 AM Building Blocks

1.2.144 RBB44_2F
RBB44_2F is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB is supported
for MSMM configurations.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
2: TX B / RX B
Data B
Radio 1
3: TX C / RX C
Data C
Other
Node(s) 4: TX D / RX D
Data D

Ge28011A

Figure 221 RBB44_2F Block Diagram

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
B
Node 1 Radio 1 3: TX C / RX C
C

4: TX D / RX D
Data D

Ge13114C

Figure 222 Example of RBB44_2F for Radio Units with Two Data Ports

about:blank 121/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1A 1: TX A / RX A
Data A

2A 2: TX B / RX B
B

3A 3: TX C / RX C
C

4A 4: TX D / RX D
D
Node 1 Radio 1 1B
(virtual port) E

2B
(virtual port) F

3B
(virtual port) G

4B
Data (virtual port) H

Ge26415A

Figure 223 RBB44_2F Block Diagram for Radio 4449 B5 B13

RI Link RF Branch
AIR Unit
1: TX A / RX A
Data A

2: TX B / RX B
B
Node 1 AIR 1 3: TX C / RX C
C

4: TX D / RX D
Data D

HW unit including ABB

Ge26416A

Figure 224 RBB44_2F Block Diagram for AIR

1.2.145 RBB44_2G
RBB44_2G is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 122/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

Node 1
2: TX B / RX B
Data B
Radio 1
3: TX C / RX C
Data C
Other
Node(s) 4: TX D / RX D
Data D

Ge27992A

Note: Number of available data ports depends on the used radio unit.

Figure 225 RBB44_2G Block Diagram

RI Link RF Branch

Data
1: TX A / RX A
A

2: TX B / RX B
B
Node 1 Radio 1 3: TX C / RX C
C

4: TX D / RX D
D
Data

Ge14165C

Figure 226 Example of RBB44_2G for Radio Unit with Two Data Ports

1.2.146 RBB44_2H
RBB44_2H is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
RBB44_2H is used together with RBB44_2G.

RI Link RF Branch

1: TX A / RX A
Data E
Node 1
2: TX B / RX B
Data F
Radio 1
3: TX C / RX C
Data G
Other
Node(s) 4: TX D / RX D
Data H

Ge28023A

Figure 227 RBB44_2H Block Diagram

Note: The number of available data ports depends on the used radio unit.
about:blank 123/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
E

2: TX B / RX B
F
Node 1 Radio 1 3: TX C / RX C
G

4: TX D / RX D
H
Data

Ge14166C

Figure 228 Example of RBB44_2H for Radio Unit with Two Data Ports

1.2.147 RBB44_2J
RBB44_2J is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection.
Note: Cascading order is chosen for antenna polarization and timing purposes.
Figure 229 shows the RBB44_2J block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1
Data

2: TX B / RX B
Data A
Radio 2
Data

3: TX C / RX C
Data A
Radio 3
Data

4: TX D / RX D
Data A
Other
Radio 4
Node(s) or
Data
Cascade

Ge13133C

Figure 229 RBB44_2J Block Diagram

1.2.148 RBB44_2K
about:blank 124/268
3/5/24, 9:34 AM Building Blocks
RBB44_2K is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection.
Figure 230 shows the RBB44_2K block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1
Data

2: TX B / RX B
Data A
Radio 2
Data

3: TX C / RX C
Data A
Other
Node(s) or
Radio 3 4: TX D / RX D
Data B
Cascade

Ge13443C

Figure 230 RBB44_2K Block Diagram

1.2.149 RBB44_2L
RBB44_2L is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection.
Figure 231 shows the RBB44_2L block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Radio 2
Data

4: TX D / RX D
Data A
Other
Node(s) or
Radio 3
Data
Cascade

Ge13444C

about:blank 125/268
3/5/24, 9:34 AM Building Blocks

Figure 231 RBB44_2L Block Diagram

1.2.150 RBB44_2M
RBB44_2M is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB uses a digital
RX cross-connection. This RBB is used for high output power mode.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data D

3: TX C / RX C
Data A
Other Node(s) Radio 2 4: TX D / RX D
or Cascade Data D

Ge13694C

Figure 232 RBB44_2M Block Diagram

RI Link RF Branch RF Branch

1A 1: TX A / RX A
Data A
Node 1
2A 2: TX B / RX B
D
Radio 1 1B
(virtual port) E

2B
Data (virtual port) H

3A 3: TX C / RX C
Data A

4A 4: TX D / RX D
D
Radio 2 3B
(virtual port) E
Other
Node(s) or 4B
Data (virtual port) H
Cascade

Ge19678C

Figure 233 RBB44_2M Block Diagram for Radio 4449 B5 B13

1.2.151 RBB44_2N
RBB44_2N is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
about:blank 126/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data D

3: TX C / RX C
Data A
Other
Node(s) or
Radio 2 4: TX D / RX D
Data D
Cascade

Ge14167C

Figure 234 RBB44_2N Block Diagram

1.2.152 RBB44_2P
RBB44_2P is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

RI Link RF Branch

1: TX A / RX A
Data E
Node 1
Radio 1 2: TX B / RX B
Data H

3: TX C / RX C
Data E
Other
Node(s) or
Radio 2 4: TX D / RX D
Data H
Cascade

Ge14168C

Figure 235 RBB44_2P Block Diagram

1.2.153 RBB44_2Q
RBB44_2Q is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 236 shows the RBB block diagram.
RBB44_2Q is intended for use together with RBB44_1L. For an example of a three sector configuration, see Figure 206.

about:blank 127/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
Node 1 1: TX A / RX A
C
Radio 1 2: TX B / RX B
D

Shared with
RBB for
previous sector 3: RX C
Data A
Radio 2 4: RX D
Data B

5: TX C
Data A
Radio 3 6: TX D
Other Node
Data B
or Cascade

Ge17267C

Figure 236 RBB44_2Q Block Diagram

1.2.154 RBB44_2R
RBB44_2R is used for sectors with four TX branches, four RX branches, and two CPRI connections. This RBB is used for
high output power mode.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data C

3: TX C / RX C
Data A
Other
Radio 2 4: TX D / RX D
Node(s) or
Data C
Cascade

Ge16136C

Figure 237 RBB44_2R Block Diagram

1.2.155 RBB44_2S
RBB44_2S is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 128/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data 1: TX A / RX A
Node 1 A
Data
Radio 1 2: TX B / RX B
Data
B
Data

Other Data 3: TX C / RX C
Node(s) or A
Data
Cascade Radio 2
Data
4: TX D / RX D
B
Data

Ge26419A

Figure 238 RBB44_2S Block Diagram

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Other
Node(s) or
Radio 2 4: TX D / RX D
Data B
Cascade

Ge18932B

Figure 239 Example of RBB44_2S for Radio Units with Two Data Ports

1.2.156 RBB44_2T
RBB44_2T is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.

about:blank 129/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data 1: TX A / RX A
Node 1 C
Data
Radio 1 2: TX B / RX B
Data
D
Data

Other Data 3: TX C / RX C
Node(s) or C
Data
Cascade Radio 2
Data
4: TX D / RX D
D
Data

Ge26420A

Figure 240 RBB44_2T Block Diagram

RI Link RF Branch

1: TX A / RX A
Data C
Node 1
Radio 1 2: TX B / RX B
Data D

3: TX C / RX C
Data C
Other
Node(s) or
Radio 2 4: TX D / RX D
Data D
Cascade

Ge18933B

Figure 241 Example of RBB44_2T with Two Data Ports

1.2.157 RBB44_2U

RBB44_2U is used for sectors with four TX branches, four RX branches, and one CPRI connection.
RF A, RF B, RF E and RF F ports are used in this RBB.
To optimize MIMO performance, consider the following factors:

– Antenna polarization for each RF Branch

– The order in which the RF Branches are defined in software

about:blank 130/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
2: TX B / RX B
Data B
Radio 1
3: TX C / RX C
Data E
Other
Node(s) 4: TX D / RX D
Data F

Ge28024A

Figure 242 RBB44_2U Block Diagram

Note: The number of available data ports depends on the used radio unit.

RI Link RF Branch

Data
1: TX A / RX A
A

2: TX B / RX B
B
Node 1 Radio 1 3: TX C / RX C
E

4: TX D / RX D
F
Data

Ge28169B

Figure 243 Example of RBB44_2U for Radio Unit with Two Data Ports

1.2.158 RBB44_2V

RBB44_2V is used for sectors with four TX branches, four RX branches, and one CPRI connection.
RF C, RF D, RF G and RF H ports are used in this RBB.
To optimize MIMO performance, consider the following factors:

– Antenna polarization for each RF Branch

– The order in which the RF Branches are defined in software

RI Link RF Branch

1: TX A / RX A
Data C
Node 1
2: TX B / RX B
Data D
Radio 1
3: TX C / RX C
Data G
Other
Node(s) 4: TX D / RX D
Data H

Ge28025A

Figure 244 RBB44_2V Block Diagram

about:blank 131/268
3/5/24, 9:34 AM Building Blocks

Note: The number of available data ports depends on the used radio unit.

RI Link RF Branch

Data
1: TX A / RX A
C

2: TX B / RX B
D
Node 1 Radio 1 3: TX C / RX C
G

4: TX D / RX D
H
Data

Ge28170B

Figure 245 Example of RBB44_2V for Radio Unit with Two Data Ports

1.2.159 RBB44_2W
RBB44_2W is used for sectors with four TX branches, four RX branches, and two CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 246 shows the RBB44_2W block diagram.
Figure 247 shows an example of RBB44_2W for radio unit with two data ports.

RI Link RF Branch

Data 1: TX A / RX A
Node 1 E
Data
Radio 1 2: TX B / RX B
Data
F
Data

Other Data 3: TX C / RX C
Node(s) or E
Data
Cascade Radio 2
Data
4: TX D / RX D
F
Data

Ge25819B

Figure 246 RBB44_2W Block Diagram

about:blank 132/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data E
Node 1
Radio 1 2: TX B / RX B
Data F

3: TX C / RX C
Data E

Radio 2 4: TX D / RX D
Other node(s)
Data F

Ge27045A

Figure 247 Example of RBB44_2W for Radio Unit with Two Data Ports

1.2.160 RBB44_2AD
RBB44_2W is used for sectors with four TX branches, four RX branches, and two CPRI connections.
RF C, RF D, RF E, and RF F ports are used in this RBB.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data C
Node 1
2: TX B / RX B
Data D
Radio 1
3: TX C / RX C
Data E
Other
Node(s) 4: TX D / RX D
Data F

Ge27993A

Note: Number of available data ports depends on the used radio unit.

Figure 248 RBB44_2AD Block Diagram

RI Link RF Branch

1: TX A / RX A
Data C

2: TX B / RX B
D
Node 1 Radio 1
3: TX C / RX C
E

4: TX D / RX D
Data F

Ge27318A

Figure 249 Example of RBB44_2AD for Radio Unit with Two Data Ports

about:blank 133/268
3/5/24, 9:34 AM Building Blocks

1.2.161 RBB44_3A
RBB44_3A is used for sectors with four TX branches, four RX branches, and three CPRI connections. This RBB uses a digital
RX cross-connection.
Figure 250 shows the RBB44_3A block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 Radio 1
Data

2: TX B / RX B
Data A
Radio 2
Data

3: TX C / RX C
Other Data A
Node(s) or Radio 3 4: TX D / RX D
Cascade Data B

Ge13445C

Figure 250 RBB44_3A Block Diagram

1.2.162 RBB44_3B
RBB44_3B is used for sectors with four TX branches, four RX branches, and three CPRI connections. This RBB uses a digital
RX cross-connection.
Figure 251 shows the RBB44_3B block diagram.

about:blank 134/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Radio 2
Data

4: TX D / RX D
Other Data A
Node(s) or Radio 3
Cascade Data

Ge13446C

Figure 251 RBB44_3B Block Diagram

1.2.163 RBB44_3C
RBB44_3C is used for sectors with four TX branches, four RX branches, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 252 shows the RBB block diagram.
RBB44_3C is intended for use together with RBB44_3D. For an example of a three sector configuration, see Figure 206.

RI Link RF Branch

Data
1: TX A / RX A
Node 1 A
Radio 1 2: TX B / RX B
B
Data

3: RX C
Data A
Radio 2 4: RX D
Data B

5: TX C
Data A
Other Node(s)
or Cascade
Radio 3 6: TX D
Data B

Ge17268C

about:blank 135/268
3/5/24, 9:34 AM Building Blocks

Figure 252 RBB44_3C Block Diagram

1.2.164 RBB44_3D
RBB44_3D is used for sectors with four TX branches, four RX branches, and three CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
Figure 253 shows the RBB block diagram.
RBB44_3D is intended for use together with RBB44_3C. For an example of a three sector configuration, see Figure 206.

RI Link RF Branch

Data
1: TX A / RX A
Node 1 C
Radio 1 2: TX B / RX B
D
Data
Shared with
RBB for
previous sector 3: RX C
Data A
Radio 2 4: RX D
Data B

5: TX C
Data A
Other Node(s) Radio 3
or Cascade 6: TX D
Data B

Ge17269C

Figure 253 RBB44_3D Block Diagram

1.2.165 RBB44_3E
RBB44_3E is used for sectors with four TX branches, four RX branches, and three CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 254 shows the RBB block diagram.

about:blank 136/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
Node 1 Data B
Radio 1 3: TX C / RX C
Data C

Other 4: TX D / RX D
Node(s) or Data D
Cascade
Ge26130A

Figure 254 RBB44_3E Block Diagram

1.2.166 RBB44_3F
RBB44_3F is used for sectors with four TX branches, four RX branches, and three CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software are important.

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
Node 1 Data B
Radio 1
3: TX C / RX C
Data C

Other 4: TX D / RX D
Data D
Node(s)

Ge27994A

Figure 255 RBB44_3F Block Diagram

1.2.167 RBB44_3G
RBB44_3G is used for sectors with four TX branches, four RX branches, and three CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data C

2: TX B / RX B
Node 1 Data D
Radio 1
3: TX C / RX C
Data E

Other 4: TX D / RX D
Data F
Node(s)

Ge27995A

about:blank 137/268
3/5/24, 9:34 AM Building Blocks

Figure 256 RBB44_3G Block Diagram

1.2.168 RBB44_3H

RBB44_3H is used for sectors with four TX branches, four RX branches, and three CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data E

2: TX B / RX B
Node 1 Data F
Radio 1
3: TX C / RX C
Data G

4: TX D / RX D
Other Node Data H

Ge28026A

Figure 257 RBB44_3H Block Diagram

1.2.169 RBB44_3J

RBB44_3J is used for sectors with four TX branches, four RX branches, and three CPRI connection. RF A, RF B, RF E and RF
F ports are used in this RBB.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

Data
1: TX A / RX A
A

Node 1 Data
2: TX B / RX B
B
Radio 1
Data
3: TX C / RX C
E

Other Node Data

4: TX D / RX D
F

Ge28027A

Figure 258 RBB44_3J Block Diagram

1.2.170 RBB44_3K

RBB44_3K is used for sectors with four TX branches, four RX branches, and three CPRI connection. RF C, RF D, RF G and
RF H ports are used in this RBB.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

about:blank 138/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data
1: TX A / RX A
C

Node 1 Data
2: TX B / RX B
D
Radio 1
Data
3: TX C / RX C
G

Other Node Data

4: TX D / RX D
H

Ge28028A

Figure 259 RBB44_3K Block Diagram

1.2.171 RBB44_4A
RBB44_4A is used for sectors with four TX branches, four RX branches, and four CPRI connections. This RBB uses a digital
RX cross-connection.
Figure 260 shows the RBB44_4A block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Radio 1
Node 1
Data

2: TX B / RX B
Data A
Radio 2
Data

3: TX C / RX C
Data A
Radio 3
Data

4: TX D / RX D
Other Data A
Node(s) or
Cascade Radio 4
Data

Ge13134C

Figure 260 RBB44_4A Block Diagram

1.2.172 RBB44_4B
RBB44_4B is used for sectors with four TX branches, four RX branches, and four CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 261 shows the RBB block diagram.
about:blank 139/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
Data B
Node 1 Radio 1 3: TX C / RX C
Data C

4: TX D / RX D
Data D

Ge26131A

Figure 261 RBB44_4B Block Diagram

1.2.173 RBB44_4C
RBB44_4C is used for sectors with four TX branches, four RX branches, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 262 shows the RBB44_4C block diagram.
Figure 263 shows an example of RBB44_4C for radio unit with two data ports.
Number of available data ports depends on the used radio unit.

RI Link RF Branch

Data 1: TX A / RX A
A
Data
Node 1
Data
Radio 1 2: TX B / RX B
B
Data

Data 3: TX C / RX C
Other A
Data
Node(s) or Radio 2 4: TX D / RX D
Data
Cascade B
Data

Ge25823B

Figure 262 RBB44_4C Block Diagram

about:blank 140/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

Radio 1 2: TX B / RX B
Data B

Node 1

3: TX C / RX C
Data A

Radio 2 4: TX D / RX D
Data B

Ge27046A

Figure 263 Example of RBB44_4C for Radio Unit with Two Data Ports

1.2.174 RBB44_4D
RBB44_4D is used for sectors with four TX branches, four RX branches, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 264 shows the RBB44_4D block diagram.
Figure 265 shows an example of RBB44_4D for radio unit with two data ports.
Number of available data ports depends on the used radio unit.

RI Link RF Branch

Data 1: TX A / RX A
C
Data
Node 1 Radio 1 2: TX B / RX B
Data
D
Data

Data 3: TX C / RX C
Other C
Data
Node(s) or Radio 2 4: TX D / RX D
Data
Cascade D
Data

Ge25824B

Figure 264 RBB44_4D Block Diagram

about:blank 141/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data C

Radio 1 2: TX B / RX B
Data D

Node 1

3: TX C / RX C
Data C

Radio 2 4: TX D / RX D
Data D

Ge27047A

Figure 265 Example of RBB44_4D for Radio Unit with Two Data Ports

1.2.175 RBB44_4E
RBB44_4E is used for sectors with four TX branches, four RX branches, and four CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 266 shows the RBB44_4E block diagram.
Figure 267 shows an example of RBB44_4E for radio unit with two data ports.
Number of available data ports depends on the used radio unit.

RI Link RF Branch

Data 1: TX A / RX A
E
Data
Node 1 Radio 1 2: TX B / RX B
Data
F
Data

Data 3: TX C / RX C
Other E
Data
Node(s) or Radio 2 4: TX D / RX D
Data
Cascade F
Data

Ge25825B

Figure 266 RBB44_4E Block Diagram

about:blank 142/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data E

Radio 1 2: TX B / RX B
Data F

Node 1

3: TX C / RX C
Data E

Radio 2 4: TX D / RX D
Data F

Ge27048A

Figure 267 Example of RBB44_4E for Radio Unit with Two Data Ports

1.2.176 RBB44_4F
RBB44_4F is used for sectors with four TX branches, four RX branches, and four CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
Data B
Node 1 Radio 1
3: TX C / RX C
Data C

4: TX D / RX D
Data D

Ge27996A

Figure 268 RBB44_4F Block Diagram

1.2.177 RBB44_4G
RBB44_4G is used for sectors with four TX branches, four RX branches, and four CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data C

2: TX B / RX B
Data D
Node 1 Radio 1
3: TX C / RX C
Data E

4: TX D / RX D
Data F

Ge27997A

about:blank 143/268
3/5/24, 9:34 AM Building Blocks

Figure 269 RBB44_4G Block Diagram

1.2.178 RBB44_4H

RBB44_4H is used for sectors with four TX branches, four RX branches, and four CPRI connections.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data E

2: TX B / RX B
Data F
Node 1 Radio 1
3: TX C / RX C
Data G

4: TX D / RX D
Data H

Ge28029A

Figure 270 RBB44_4H Block Diagram

1.2.179 RBB44_4J

RBB44_4J is used for sectors with four TX branches, four RX branches, and four CPRI connection. RF A, RF B, RF E and RF
F ports are used in this RBB.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
Data B
Node 1 Radio 1
3: TX C / RX C
Data E

4: TX D / RX D
Data F

Ge28030A

Figure 271 RBB44_4J Block Diagram

1.2.180 RBB44_4K

RBB44_4K is used for sectors with four TX branches, four RX branches, and four CPRI connection. RF C, RF D, RF G and RF
H ports are used in this RBB.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

about:blank 144/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data C

2: TX B / RX B
Data D
Node 1 Radio 1
3: TX C / RX C
Data G

4: TX D / RX D
Data H

Ge28031A

Figure 272 RBB44_4K Block Diagram

1.2.181 RBB44_6A
RBB44_6A is used for sectors with four TX branches, four RX branches, and six CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 273 shows the RBB44_6A block diagram.

RI Link RF Branch

Data 1: TX A / RX A
A
Data
Data Radio 1 2: TX B / RX B
Node 1 B
Data

Data 3: TX C / RX C
A
Data
Other Data Radio 2 4: TX D / RX D
Node(s) or B
Data
Cascade

Ge25826B

Figure 273 RBB44_6A Block Diagram

1.2.182 RBB44_6B
RBB44_6B is used for sectors with four TX branches, four RX branches, and six CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 274 shows the RBB44_6B block diagram.

about:blank 145/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data 1: TX A / RX A
C
Data
Data Radio 1 2: TX B / RX B
Node 1 D
Data

Data 3: TX C / RX C
C
Data
Other Data Radio 2 4: TX D / RX D
Node(s) or D
Data
Cascade

Ge25827B

Figure 274 RBB44_6B Block Diagram

1.2.183 RBB44_6C
RBB44_6C is used for sectors with four TX branches, four RX branches, and six CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 275 shows the RBB44_6C block diagram.

RI Link RF Branch

Data 1: TX A / RX A
E
Data
Data
Radio 1 2: TX B / RX B
Node 1 F
Data

Data 3: TX C / RX C
E
Data
Other Data Radio 2 4: TX D / RX D
Node(s) or F
Data
Cascade

Ge25828B

Figure 275 RBB44_6C Block Diagram

1.2.184 RBB44_8A
RBB44_8A is used for sectors with four TX branches, four RX branches, and eight CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 276 shows the RBB44_8A block diagram.
about:blank 146/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data 1: TX A / RX A
A
Data
Data
Radio 1 2: TX B / RX B
B
Node 1 Data

Data 3: TX C / RX C
A
Data
Radio 2 4: TX D / RX D
Data
B
Data

Ge25829

Figure 276 RBB44_8A Block Diagram

1.2.185 RBB44_8B
RBB44_8B is used for sectors with four TX branches, four RX branches, and eight CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 277 shows the RBB44_8B block diagram.

RI Link RF Branch

Data 1: TX A / RX A
C
Data
Data
Radio 1 2: TX B / RX B
D
Node 1 Data

Data 3: TX C / RX C
C
Data
Radio 2 4: TX D / RX D
Data
D
Data

Ge25830

Figure 277 RBB44_8B Block Diagram

1.2.186 RBB44_8C
RBB44_8C is used for sectors with four TX branches, four RX branches, and eight CPRI connections.
This RBB can be used with the Multi-Sector Per Radio feature.
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
Figure 278 shows the RBB44_8C block diagram.
about:blank 147/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

Data 1: TX A / RX A
E
Data
Data
Radio 1 2: TX B / RX B
F
Node 1 Data

Data 3: TX C / RX C
E
Data
Radio 2 4: TX D / RX D
Data
F
Data

Ge25831

Figure 278 RBB44_8C Block Diagram

1.2.187 RBB46_1A
RBB46_1A is used for sectors with four TX branches, six RX branches, and one CPRI connection.
Figure 279 shows the RBB block diagram.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
Data D

5: RX E
Data A
Radio 2 6: RX F
Other Node
Data B
or Cascade

Ge17270C

Figure 279 RBB46_1A Block Diagram

1.2.188 RBB46_2A
RBB46_2A is used for sectors with four TX branches, six RX branches, and two CPRI connections.
Figure 280 shows the RBB block diagram.

about:blank 148/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
Data D

5: RX E
Data A

Other Node(s) Radio 2 6: RX F

or Cascade Data B

Ge17271C

Figure 280 RBB46_2A Block Diagram

1.2.189 RBB66_1A
RBB66_1A is used for sectors with six TX branches, six RX branches, and one CPRI connection.
Figure 281 shows the RBB block diagram.

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D/ RX D
Data D

5: RX E
Data A
Radio 2 6: RX F
Data B

7: TX E
Data A
Radio 3 8: TX F
Other Node Data B
or Cascade

Ge17272C

Figure 281 RBB66_1A Block Diagram

about:blank 149/268
3/5/24, 9:34 AM Building Blocks

1.2.190 RBB66_3A
RBB66_3A is used for sectors with six TX branches, six RX branches, and three CPRI connections.
Figure 282 shows the RBB block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1 2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
Data D

5: RX E
Data A
Radio 2 6: RX F
Data B

7: TX E
Data A
Other Node(s) Radio 3
or Cascade 8: TX F
Data B

Ge17273C

Figure 282 RBB66_3A Block Diagram

1.2.191 RBB88_1A
RBB88_1A is used for sectors with eight TX branches, eight RX branches, and one CPRI connection.
Figure 283 shows the RBB88_1A block diagram.

about:blank 150/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B

3: TX C / RX C
C
Data
4: TX D / RX D
D

Radio 1 5: TX E / RX E
E

Other Node(s) Data 6: TX F / RX F

F

7: TX G / RX G
G

8: TX H / RX H
Data H

Ge28032B

Figure 283 RBB88_1A Block Diagram

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B

3: TX C / RX C
C

4: TX D / RX D
D
Radio 1 5: TX E / RX E
E

6: TX F / RX F
F

7: TX G / RX G
G

Other Node 8: TX H / RX H
Data H
or cascade

Ge13116C

Note: The number of available data ports depends on the used radio unit.

Figure 284 RBB88_1A with Two Data Ports

1.2.192 RBB88_1B
RBB88_1B is used for sectors with eight TX branches, eight RX branches, and one CPRI connection.
Figure 285 shows the RBB88_1B block diagram.

about:blank 151/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A

2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
Data D

5: TX E / RX E
Data A

6: TX F / RX F
B
Radio 2 7: TX G / RX G
C

Other Node 8: TX H / RX H
Data D
or cascade

Ge22115B

Figure 285 RBB88_1B Block Diagram

1.2.193 RBB88_1C
RBB88_1C is used for NR Combined Radio.
Figure 286 shows the RBB88_1C block diagram for NR Combined Radio.

about:blank 152/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Node 1 Data A
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Data B

5: TX E / RX E
Data A
Radio 3 6: TX F / RX F
Data B

7: TX G / RX G
Data A
Radio 4 8: TX H / RX H
Other Node B
Data
or Cascade

Ge26911A

Figure 286 RBB88_1C Block Diagram for NR Combined Radio

1.2.194 RBB88_2A
RBB88_2A is used for sectors with eight TX branches, eight RX branches, and two CPRI connections.
Figure 287 shows the RBB88_2A block diagram.

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
B
Node 1
3: TX C / RX C
C
Data
4: TX D / RX D
D

Radio 1 5: TX E / RX E
E

Data 6: TX F / RX F
F

Other 7: TX G / RX G
Node(s) G

8: TX H / RX H
Data H

Ge28033A

Figure 287 RBB88_2A Block Diagram

Note: The number of available data ports depends on the used radio unit.

about:blank 153/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
B

3: TX C / RX C
C

4: TX D / RX D
D
Node 1 Radio 1 5: TX E / RX E
E

6: TX F / RX F
F

7: TX G / RX G
G

8: TX H / RX H
Data H

Ge13117C

Figure 288 Example of RBB88_2A for Radio Unit with Two Data Ports

1.2.195 RBB88_2B
RBB88_2B is used for sectors with eight TX branches, eight RX branches, and two CPRI connections.
Figure 289 shows the RBB88_2B block diagram.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
2: TX B / RX B
B
Radio 1 3: TX C / RX C
C

4: TX D / RX D
Data D

5: TX E / RX E
Data A

6: TX F / RX F
B
Radio 2 7: TX G / RX G
C
Other Node(s) 8: TX H / RX H
or Cascade Data D

Ge22063B

about:blank 154/268
3/5/24, 9:34 AM Building Blocks

Figure 289 RBB88_2B Block Diagram

1.2.196 RBB88_2C
RBB88_2C is used for NR Combined Radio.
Figure 290 shows the RBB88_2C block diagram for NR Combined Radio.

RI Link RF Branch

1: TX A / RX A
Data A
Node 1
Radio 1 2: TX B / RX B
Data B

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Data B

5: TX E / RX E
Data A
Radio 3 6: TX F / RX F
Data B

7: TX G / RX G
Data A
Other
Node(s) or
Radio 4 8: TX H / RX H
Data B
Cascade

Ge26914A

Figure 290 RBB88_2C Block Diagram for NR Combined Radio

1.2.197 RBB88_3A

RBB88_3A with 3 CPRI links.

To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

about:blank 155/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
B

3: TX C / RX C
C
Node 1 Data
4: TX D / RX D
D

Radio 1 5: TX E / RX E
E

Data 6: TX F / RX F
F

7: TX G / RX G
G

8: TX H / RX H
Other Node Data H

Ge28034A

Figure 291 RBB88_3A Block Diagram

1.2.198 RBB88_4A
RBB88_4A is used for NR Combined Radio.
Figure 292 shows the RBB88_4A block diagram for NR Combined Radio.

RI Link RF Branch

1: TX A / RX A
Data A
Radio 1 2: TX B / RX B
Node 1
Data B

3: TX C / RX C
Data A
Radio 2 4: TX D / RX D
Data B

5: TX E / RX E
Data A
Radio 3 6: TX F / RX F
Data B

7: TX G / RX G
Other Data A
Node(s) or
Cascade Radio 4 8: TX H / RX H
Data B

Ge26916A

Figure 292 RBB88_4A Block Diagram for NR Combined Radio

about:blank 156/268
3/5/24, 9:34 AM Building Blocks

1.2.199 RBB88_4B

RBB88_4B with 3 CPRI links.

To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.

RI Link RF Branch

1: TX A / RX A
Data A

2: TX B / RX B
B

3: TX C / RX C
C
Data
4: TX D / RX D
D
Node 1 Radio 1 5: TX E / RX E
E

Data 6: TX F / RX F
F

7: TX G / RX G
G

8: TX H / RX H
Data H

Ge28035A

Figure 293 RBB88_4B Block Diagram

1.3 RBBs for AAS

Each RBB defines a unique way of combining AIR units in one sector with connections to Baseband units.

RBBs for AAS are named as follows: RBBAIR_[C][V], where:

C Number of CPRI or eCPRI links

V Version

Example: RBBAIR_2A

– Two CPRI or eCPRI links between Baseband and AIR unit

– Version A

1.3.1 RBBAIR_1A
RBBAIR_1A is used for Massive MIMO with AIR units with one CPRI or eCPRI connection.

about:blank 157/268
3/5/24, 9:34 AM Building Blocks

RI Link

Node Data

Data

Other Data AIR 1 Transceiver 1

Node(s) or
Cascade Data

Data

Physical Unit

Logical Unit
Ge18938B

Figure 294 RBBAIR_1A Block Diagram

Note: The number of available data ports depends on the used radio unit.

1.3.2 RBBAIR_1B
RBBAIR_1B is used for Massive MIMO with three AIR units using feature Fronthaul Sharing. For more information, see
Fronthaul Sharing.
Only one AIR unit can transmit and receive at a time. Therefore the CPRI capacity requirement will be the same as if only
one AIR unit was used.
Different geographical relations concerning the service area for the cascaded AIR units are supported, see Fronthaul
Sharing.

about:blank 158/268
3/5/24, 9:34 AM Building Blocks

RI Link

Node Data

Data
AIR 1 Transceiver 1
Data

Data

Data

Data
AIR 2 Transceiver 1
Data

Data

Data

Data
AIR 3 Transceiver 1
Data

Data

Physical Unit

Logical Unit
Ge22519B

Figure 295 RBBAIR_1B Block Diagram

1.3.3 RBBAIR_1C
RBBAIR_1C is used for Massive MIMO with two AIR units using feature Fronthaul Sharing. For more information, see
Fronthaul Sharing.
Only one AIR unit can transmit and receive at a time. Therefore the CPRI capacity requirement will be the same as if only
one AIR unit was used.
Different geographical relations concerning the service area for the cascaded AIR units are supported, see Fronthaul
Sharing

about:blank 159/268
3/5/24, 9:34 AM Building Blocks

RI Link

Node Data

Data
AIR 1 Transceiver 1
Data

Data

Data

Data
AIR 2 Transceiver 1
Data

Data

Physical Unit

Logical Unit
Ge22520B

Figure 296 RBBAIR_1C Block Diagram

1.3.4 RBBAIR_2A
RBBAIR_2A is used for Massive MIMO with AIR units with two CPRI or eCPRI connections.

RI Link

Data
Node
Data

Data AIR 1 Transceiver 1

Other
Node(s) or Data
Cascade
Data

Physical Unit

Logical Unit
Ge18939B

Figure 297 RBBAIR_2A Block Diagram

about:blank 160/268
3/5/24, 9:34 AM Building Blocks

Note: The number of available data ports depends on the used radio unit.

1.3.5 RBBAIR_2B
RBBAIR_2B is used for Massive MIMO with three AIR units using feature Fronthaul Sharing. For more information, see
Fronthaul Sharing.
Only one AIR unit can transmit and receive at a time. Therefore the CPRI capacity requirement will be the same as if only
one AIR unit was used.
Different geographical relations concerning the service area for the cascaded AIR units are supported, see Fronthaul
Sharing.

RI Link

Data

Node Data
AIR 1 Transceiver 1
Data

Data

Data

Data
AIR 2 Transceiver 1
Data

Data

Data

Data
AIR 3 Transceiver 1
Data

Data

Physical Unit

Logical Unit
Ge22521B

Figure 298 RBBAIR_2B Block Diagram

1.3.6 RBBAIR_2C
RBBAIR_2C is used for Massive MIMO with two AIR units using feature Fronthaul Sharing. For more information, see
Fronthaul Sharing.
Only one AIR unit can transmit and receive at a time. Therefore the CPRI capacity requirement will be the same as if only
one AIR unit was used.

about:blank 161/268
3/5/24, 9:34 AM Building Blocks
Different geographical relations concerning the service area for the cascaded AIR units are supported, see Fronthaul
Sharing.

RI Link

Data

Node Data
AIR 1 Transceiver 1
Data

Data

Data

Data
AIR 2 Transceiver 1
Data

Data

Physical Unit

Logical Unit
Ge22522B

Figure 299 RBBAIR_2C Block Diagram

1.3.7 RBBAIR_3A
RBBAIR_3A is used for Massive MIMO with AIR units with three CPRI or eCPRI connections.

RI Link

Data
Node
Data

Data AIR 1 Transceiver 1

Data
Other
Node(s) or
Cascade Data

Physical Unit

Logical Unit
Ge18940B

about:blank 162/268
3/5/24, 9:34 AM Building Blocks

Figure 300 RBBAIR_3A Block Diagram

1.3.8 RBBAIR_4A
RBBAIR_4A is used for Massive MIMO with AIR units with four CPRI or eCPRI connections.
Figure 301 shows the RBBAIR_4A block diagram.

RI Link

Data

Data

Node Data AIR 1 Transceiver 1

Data

Other
Node or Data
Cascade

Physical Unit

Logical Unit
Ge18941B

Figure 301 RBBAIR_4A Block Diagram

1.3.9 RBBAIR_5A
RBBAIR_5A is used for Massive MIMO with AIR units with five CPRI or eCPRI connections.
Figure 302 shows the RBBAIR_5A block diagram.

RI Link

Data

Data

Node Data AIR 1 Transceiver 1

Data

Data

Physical Unit

Logical Unit
Ge23005B

about:blank 163/268
3/5/24, 9:34 AM Building Blocks

Figure 302 RBBAIR_5A Block Diagram

1.4 RBBs for RDS

Introduction
Radio Building Blocks for RDS are split into four parts:

– Fronthaul Building Block (FHB)

– Dot Group Block (DGB)

– Radio Dot Block (RDB)

– Antenna Building Block (ABB)

Node 1
FHB DGB RDB ABB
Node 2 or
cascade
Fronthaul Dot Group Radio Dot Antenna
Building Block Block Building
Block Block
Ge27580A

Figure 303 The Four Parts of an RDS Radio Building Block

1.4.1 Fronthaul Building Blocks for RDS

The Fronthaul Building Block (FHB) for RDS defines the fronthaul connections for one or multiple IRUs.
An FHB with two IRUs is only used when DGBs from both IRUs are sharing the same ABB, see ABBs for RDS and Figure
305.

FHB
Node

IRU DGB
Free data port

Ge27581B

Figure 304 FHB with One IRU

about:blank 164/268
3/5/24, 9:34 AM Building Blocks

FHB
Node

IRU DGB

IRU DGB

ABB

IRU DGB
Free data port

Ge27582B

Figure 305 FHB with Multiple IRUs, where DGBs from All IRUs are Sharing the Same ABB

1.4.1.1 IRU Data Port Group Connectivity

Cascading Rules

– Cascading is only supported from data port group 1 for each IRU in the cascade chain.

– If the IRU that is used to cascade to another IRU has two data port groups, the second data port group becomes
unavailable for any type of connection, as shown in Figure 306.

– The IRU that is used to cascade to another IRU can only be connected to one node.

Connections to Multiple Nodes

– All nodes that are connected to an IRU must be synchronized with Node Group Sync. For details, see Mixed Mode
Synchronization Using Node Group Synchronization.

– The number of nodes that can be connected depends on the synchronization solution and the number of data ports
on an IRU.

• Up to SW 22.Q4, the Sync Receiver (SR) can be synchronized to the Sync Provider (SP) using different data ports
in the same Data Port Group on the IRU. When an IRU has more than one Data Port Group, each Data Port Group
can be used to synchronize between the SP and one SR, as shown in Figure 307.

• From SW 23.Q1, the Sync Receiver (SR) can be synchronized to the Sync Provider (SP) using different data ports
on the same IRU (irrespective of Data Port Group), as shown in Figure 308. The maximum number of nodes that
can be connected to the IRU is the same as the number of data ports on the IRU.

– If the IRU is not used for the synchronization of the different nodes (that is, other IRU(s) or radio unit(s) are used to
synchronize the nodes), all data ports on the IRU can be connected to different nodes. For more information, see
Supported Multi-Node Combinations with RDS.

about:blank 165/268
3/5/24, 9:34 AM Building Blocks

Node
Data Port
Group IRU
Cascading

Node
Data Port
Group 1
Cascading
IRU
Data Port
Group 2

Ge27583A

Figure 306 Cascading for IRUs with One Data Port Group and IRUs with Two Data Port Groups

SP Node
Data Port
Group IRU
SR Node

SP Node Data Port

Group

IRU
SR Node 1
Data Port
Group
SR Node 2

Ge27584A

Figure 307 One SR Nodes is Synchronized from the SP Node for Each Data Port Group

SP Node
Data Port
Group
SR Node 1
IRU
SR Node 2
Data Port
Group
SR Node 3

Ge27585A

Figure 308 From SW 23.Q1: Up to Three SR Nodes are Synchronized from the SP Node with an IRU that has Two Data
Port Groups

about:blank 166/268
3/5/24, 9:34 AM Building Blocks

1.4.1.2 FHB1_1A

From node
Data Port
Group IRU
Free data port

Ge27586A

Figure 309 FHB1_1A Block Diagram

From node
Data Port
Group

IRU
Free data Data Port
ports Group

Ge27587A

Figure 310 FHB1_1A Block Diagram for Two Data Port Groups

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 11 FHB1_1A Connection Definition.

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
IRU 2242
IRU 884x Figure 309
1 1 IRU 888x
IRU 164x Figure 310

Table 12 FHB1_1A Connection Definition for Private 5G

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
IRU 88Rb Figure 309
1 1
IRU 16Fr Figure 310

1.4.1.3 FHB1_2A

FHB1_2A for RDS uses one IRU and two CPRI connections towards the node.

Data Port
From node Group IRU

Ge27588A

about:blank 167/268
3/5/24, 9:34 AM Building Blocks

Figure 311 FHB1_2A Block Diagram

From node Data Port

Group

IRU
Free data Data Port
ports Group

Ge27589A

Figure 312 FHB1_2A Block Diagram with Two Data Port Groups

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 13 FHB1_2A Connection Definition

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
IRU 2242
IRU 8818
IRU 8828 Figure 311
1 2 IRU 884x
IRU 888x
IRU 164x Figure 312

Table 14 FHB1_2A Connection Definition for Private 5G

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
IRU 88Rb Figure 311
1 2
IRU 16Fr Figure 312

1.4.1.4 FHB1_2B

FHB1_2A for RDS uses one IRU and two CPRI connections towards the node.

Data Port
From node Group
IRU
Free data Data Port
ports Group

Ge27590A

Figure 313 FHB1_2B Block Diagram

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 15 FHB1_2B Connection Definition

about:blank 168/268
3/5/24, 9:34 AM Building Blocks

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
2 2 IRU 164x Figure 313

Table 16 FHB1_2B Connection Definition for Private 5G

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
2 2 IRU 16Fr Figure 313

1.4.1.5 FHB1_3A

FHB1_3A for RDS uses one IRU and three CPRI connections towards the node.

Data Port
Node Group
IRU
Data Port
Group
Free data
port

Ge27591A

Figure 314 FHB1_3A Block Diagram with One Free Data Port in Data Port Group 1

Data Port
Node Group
IRU
Data Port
Group
Free data
port

Ge27592A

Figure 315 FHB1_3A Block Diagram with One Free Data Port in Data Port Group 2

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 17 FHB1_3A Connection Definition

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
Figure 314
2 2 IRU 164x
Figure 315

Table 18 FHB1_3A Connection Definition for Private 5G

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
Figure 314
2 2 IRU 16Fr
Figure 315

1.4.1.6 FHB1_4A

about:blank 169/268
3/5/24, 9:34 AM Building Blocks
FHB1_4A for RDS uses one IRU and four CPRI connections towards the node.

Data Port
Group

From node IRU

Data Port
Group

Ge27593A

Figure 316 FHB1_4A Block Diagram

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 19 FHB1_4A Connection Definition

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
2 4 IRU 164x Figure 316

Table 20 FHB1_4A Connection Definition for Private 5G

Number of Data Port Groups Number of Data Ports IRU Type Figure
Used by the Node Connected to the Node
2 4 IRU 16Fr Figure 316

1.4.1.7 FHB2_1A

FHB2_1A for RDS uses two IRUs and one CPRI connection towards the node.

From node
Data Port
Group IRU 1

Data Port
Group IRU 2
Free data
port

Ge27594A

Figure 317 FHB2_1A Block Diagram

about:blank 170/268
3/5/24, 9:34 AM Building Blocks

From node
Data Port
Group IRU 1

Data Port
Free data Group

port
IRU 2
Data Port
Group

Ge27595A

Figure 318 FHB2_1A Block Diagram for Two IRUs, the Second with Two Data Port Groups

From node
Data Port
Group

IRU 1
Data Port
Group

Data Port
Group
IRU 2
Free data
port

Ge27596A

Figure 319 FHB2_1A Block Diagram for Two IRUs, the First with Two Data Port Groups

From node
Data Port
Group

IRU 1
Data Port
Group

Data Port
Free data Group

port
IRU 2
Data Port
Group

Ge27597A

Figure 320 FHB2_1A Block Diagram for two IRUs, Both with Two Data Port Groups

about:blank 171/268
3/5/24, 9:34 AM Building Blocks
For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 21 FHB2_1A Connection Definition with IRU 2242

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
1 1 1 IRU 2242 Figure 317

2 1 1(1) IRU 2242 Figure 317

(1) Connected towards the node through IRU 1.

Table 22 FHB2_1A Connection Definition with IRU 884x, IRU 888x, and IRU 164x

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 884x Figure 317
IRU 888x Figure 318
1 1 1
Figure 319
IRU 164x
Figure 320
IRU 884x Figure 317
IRU 888x Figure 319
2 1 1(2)
Figure 318
IRU 164x
Figure 320
(2) Connected towards the node through IRU 1.

Table 23 FHB2_1A Connection Definition with Private 5G

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
Figure 317
IRU 88Rb
Figure 318
1 1 1
Figure 319
IRU 16Fr
Figure 320
Figure 317
IRU 88Rb
Figure 319
2 1 1(3)
Figure 318
IRU 16Fr
Figure 320
(3) Connected towards the node through IRU 1.

1.4.1.8 FHB2_2A

FHB2_2A for RDS uses two IRUs and two CPRI connections to the node.

about:blank 172/268
3/5/24, 9:34 AM Building Blocks

From node Data Port

Group IRU 1

Data Port
Free data Group IRU 2
ports

Ge27598A

Figure 321 FHB2_2A Block Diagram

Data Port
From node
Group
IRU 1

Data Port
Group
Free data IRU 2
ports Data Port
Group

Ge27599A

Figure 322 FHB2_2A Block Diagram for Two IRUs, the Second with Two Data Port Groups

Data Port
From node Group
IRU 1
Data Port
Group

Free data
Data Port
ports Group IRU 2

Ge27600A

Figure 323 FHB2_2A Block Diagram for Two IRUs, the First with Two Data Port Groups

about:blank 173/268
3/5/24, 9:34 AM Building Blocks

Data Port
From node Group
IRU 1
Data Port
Group

Data Port
Free data Group
ports IRU 2
Data Port
Group

Ge27601A

Figure 324 FHB2_2A Block Diagram for two IRUs, Both with Two Data Port Groups

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 24 FHB2_1A Connection Definition with IRU 2242

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
1 1 1 IRU 2242 Figure 321

2 1 1(1) IRU 2242 Figure 321

(1) Connected towards the node through IRU 1.

Table 25 FHB2_1A Connection Definition with IRU 884x, IRU 888x, and IRU 164x

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 884x Figure 321
IRU 888x Figure 322
1 1 1
Figure 323
IRU 164x
Figure 324
IRU 884x Figure 321
IRU 888x Figure 323
2 1 1
Figure 322
IRU 164x
Figure 324

Table 26 FHB2_1A Connection Definition with Private 5G

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
Figure 321
IRU 88Rb
Figure 322
1 1 1
Figure 323
IRU 16Fr
Figure 324
2 1 1 Figure 321
IRU 88Rb
Figure 323
IRU 16Fr Figure 322

about:blank 174/268
3/5/24, 9:34 AM Building Blocks

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
Figure 324

1.4.1.9 FHB2_3A

FHB2_3A for RDS uses two IRUs and three CPRI connections to the node.

Data Port
Group
From node
IRU 1
Data Port
Group

Data Port
Free data Group IRU 2
ports

Ge27602A

Figure 325 FHB2_3A Block Diagram where the First IRU has Two Data Port Groups

Data Port
Group
From node
IRU 1
Data Port
Group

Data Port
Group
Free data
ports IRU 2
Data Port
Group

Ge27603A

Figure 326 FHB2_3A Block Diagram where Both IRUs have Two Data Port Groups and Only One Data Port Group is Used
by the Node on the Second IRU

From node Data Port

Group IRU 1

Data Port
Group

Free data IRU 2

Data Port
ports Group

Ge27604A

about:blank 175/268
3/5/24, 9:34 AM Building Blocks

Figure 327 FHB2_3A Block Diagram where the Second IRU has Two Data Port Groups

Data Port
Group
From node IRU 1
Data Port
Group

Data Port
Group
Free data
ports IRU 2
Data Port
Group

Ge27605A

Figure 328 FHB2_3A Block Diagram where Both IRUs have Two Data Port Groups and Only One Data Port Group is Used
by the Node on the First IRU

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 27 FHB2_3A Connection Definition

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
Figure 325
Figure 326
1(1) 2 2 IRU 164x
Figure 327
Figure 328
IRU 884x Figure 325
IRU 888x Figure 327
2(1) 1 1
Figure 326
IRU 164x
Figure 328
(1) IRU 1 can be the first IRU and IRU 2 the second IRU or the other way around.

Table 28 FHB2_3A Connection Definition for Private 5G

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
Figure 325
Figure 326
1(2) 2 2 IRU 16Fr
Figure 327
Figure 328
Figure 325
IRU 88Rb
Figure 327
2(2) 1 1
Figure 326
IRU 16Fr
Figure 328
(2) IRU 1 can be the first IRU and IRU 2 the second IRU or the other way around.

1.4.1.10 FHB2_4A

FHB2_4A for RDS uses two IRUs and four CPRI connections to the node.

about:blank 176/268
3/5/24, 9:34 AM Building Blocks

Data Port
Group
From node IRU 1
Data Port
Group

Data Port
Group
Free data IRU 2
ports Data Port
Group

Ge27606A

Figure 329 FHB2_4A Block Diagram

For supported data port groups and availability of free data ports per IRU type, see IRU Data Port Group Connectivity.

Table 29 FHB2_4A Connection Definition

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
1 2 2 IRU 164x Figure 329
2 2 2 IRU 164x Figure 329

Table 30 FHB2_4A Connection Definition for Private 5G

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
1 2 2 IRU 16Fr Figure 329
2 2 2 IRU 16Fr Figure 329

1.4.1.11 FHB4_1A

FHB4_1A for RDS uses four IRUs and one CPRI connection towards the node.

From node
Data Port
Group IRU 1

Data Port
Group IRU 2

Data Port
Group IRU 3

Data Port
Group IRU 4
Free data port

Ge28340A

about:blank 177/268
3/5/24, 9:34 AM Building Blocks

Figure 330 FHB4_1A Block Diagram

From node
Data Port
Group

IRU 1
Data Port
Group

Data Port
Group

IRU 2
Data Port
Group

Data Port
Group

IRU 3
Data Port
Group

Data Port
Group
Free data port
IRU 4
Data Port
Group

Ge28341B

Figure 331 FHB4_1A Block Diagram for four IRUs, All with Two Data Port Groups

Table 31 FHB4_1A Connection Definition with IRU 884x, IRU 888x and IRU 164x.

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 884x
Figure 330
1 1 1 IRU 888x
IRU 164x Figure 331
IRU 884x
Figure 330
2 1 1(1) IRU 888x
IRU 164x Figure 331
IRU 884x
Figure 330
3 1 1(1) IRU 888x
IRU 164x Figure 331
IRU 884x
Figure 330
4 1 1(1) IRU 888x
IRU 164x Figure 331
(1) Connected towards node via IRU 1.

Table 32 FHB4_1A Connection Definition with Private 5G.

about:blank 178/268
3/5/24, 9:34 AM Building Blocks

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 88Rb Figure 330
1 1 1
IRU 16Fr Figure 331
IRU 88Rb Figure 330
2 1 1(2)
IRU 16Fr Figure 331
IRU 88Rb Figure 330
3 1 1(2)
IRU 16Fr Figure 331
IRU 88Rb Figure 330
4 1 1(2)
IRU 16Fr Figure 331
(2) Connected towards node via IRU 1.

1.4.1.12 FHB4_2A

FHB4_2A for RDS uses four IRUs and two CPRI connection towards the node.

From node
Data Port
Group IRU 1

Data Port
Group IRU 2

Data Port
Group IRU 3

Data Port
Free data ports Group IRU 4

Ge28342A

Figure 332 FHB4_2A Block Diagram

about:blank 179/268
3/5/24, 9:34 AM Building Blocks

From node Data Port

Group

IRU 1
Data Port
Group

Data Port
Group

IRU 2
Data Port
Group

Data Port
Group

IRU 3
Data Port
Group

Data Port
Group

IRU 4
Data Port
Free data ports Group

Ge28343A

Figure 333 FHB4_2A Block Diagram for four IRUs, All with Two Data Port Groups

Table 33 FHB4_2A Connection Definition with IRU 884x, IRU 888x and IRU 164x.

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 884x
Figure 332
1 1 1 IRU 888x
IRU 164x Figure 333
IRU 884x
Figure 332
2 1 1 IRU 888x
IRU 164x Figure 333
IRU 884x
Figure 332
3 1 1(1) IRU 888x
IRU 164x Figure 333
IRU 884x
Figure 332
4 1 1(2) IRU 888x
IRU 164x Figure 333
(1) Connected towards node via IRU 1.
(2) Connected towards node via IRU 2.

Table 34 FHB4_2A Connection Definition with Private 5G.

about:blank 180/268
3/5/24, 9:34 AM Building Blocks

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 88Rb Figure 332
1 1 1
IRU 16Fr Figure 333
IRU 88Rb Figure 332
2 1 1
IRU 16Fr Figure 333
IRU 88Rb Figure 332
3 1 1(3)
IRU 16Fr Figure 333
IRU 88Rb Figure 332
4 1 1(4)
IRU 16Fr Figure 333
(3) Connected towards node via IRU 1.
(4) Connected towards node via IRU 2.

1.4.1.13 FHB4_4A

FHB4_4A for RDS uses four IRUs and four CPRI connection towards the node.

From node Data Port

IRU 1
Group

Data Port
Group IRU 2

Data Port
Group IRU 3

Data Port
Free data ports Group IRU 4

Ge28344A

Figure 334 FHB4_4A Block Diagram

about:blank 181/268
3/5/24, 9:34 AM Building Blocks

From node Data Port

Group

IRU 1
Data Port
Group

Data Port
Group

IRU 2
Data Port
Group

Data Port
Group

IRU 3
Data Port
Group

Data Port
Group

IRU 4
Data Port
Free data ports Group

Ge28345A

Figure 335 FHB4_4A Block Diagram for four IRUs, All with Two Data Port Groups

Table 35 FHB4_4A Connection Definition with IRU 884x, IRU 888x and IRU 164x.

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 884x
Figure 334
1 1 1 IRU 888x
IRU 164x Figure 335
IRU 884x
Figure 334
2 1 1 IRU 888x
IRU 164x Figure 335
IRU 884x
Figure 334
3 1 1 IRU 888x
IRU 164x Figure 335
IRU 884x
Figure 334
4 1 1 IRU 888x
IRU 164x Figure 335

Table 36 FHB4_4A Connection Definition with Private 5G.

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
1 1 1 IRU 88Rb Figure 334

about:blank 182/268
3/5/24, 9:34 AM Building Blocks

IRU Number of Data Port Number of Data Ports IRU Type Figure
Groups Used by the Connected to the Node
Node
IRU 16Fr Figure 335
IRU 88Rb Figure 334
2 1 1
IRU 16Fr Figure 335
IRU 88Rb Figure 334
3 1 1
IRU 16Fr Figure 335
IRU 88Rb Figure 334
4 1 1
IRU 16Fr Figure 335

1.4.2 Dot Group Blocks for RDS

A Dot Group Block (DGB) is used to describe the supported topology with the feature Cell Grouping. For general
requirements on Cell Grouping, see Cell Grouping.

FHB

DGB Dot

IRU DGB Dot

DGB Dot

Ge27607A

Figure 336 DGB Overview

Definition of Dot Group Block for RDS:

1. The DGB defines the group of Dots that are used for multicasting the same carriers in one physical area.

2. Only Dots of the same product type is allowed in a DGB.

– Variants with the same basic product number can be mixed, typically internal antenna and external antenna
versions, for example:

• Dot 2272 B1 B7, KRY 901 469/1

• Dot 2282 B1 B7, KRY 901 469/2

3. The DGB defines:

– The Dot type the DGB supports.

– The physical ports on the IRU that are available for the Dots in the DGB.

– To which IRU the DGB is connected, in case of an FHB with more than one IRU.

4. A DGB can only be connected to one IRU in the FHB.

5. When Cell Grouping is used, an IRU can have multiple DGBs.

1.4.2.1 DGB without Cell Grouping

about:blank 183/268
3/5/24, 9:34 AM Building Blocks
DGB1_1A for RDS allocate all available Dot ports on IRU 1 for one Dot group.
DGB2_1A for RDS allocate all available Dot ports on IRU 2 for one Dot group.
DGB3_1A for RDS allocate all available Dot ports on IRU 3 for one Dot group.
DGB4_1A for RDS allocate all available Dot ports on IRU 4 for one Dot group.

FHB

IRU DGB1_1A Dot

Ge27608A

Figure 337 DGB1_1A for FHB with One IRU

FHB

IRU 1 DGB1_1A Dot

IRU 2
DGB Dot

Ge27609A

Figure 338 DGB1_1A for FHB with Two IRUs

FHB

DGB Dot
IRU 1

IRU 2 DGB2_1A Dot

Ge27610A

Figure 339 DGB2_1A Block Diagram

about:blank 184/268
3/5/24, 9:34 AM Building Blocks

FHB

DGB Dot
IRU 2

IRU 3 DGB3_1A Dot

Ge28346A

Figure 340 DGB3_1A Block Diagram

FHB

DGB Dot
IRU 3

IRU 4 DGB4_1A Dot

Ge28347A

Figure 341 DGB4_1A Block Diagram

Table 37 Connection Definition for DGB without Cell Grouping

IRU DGB Supported from IRU Number Rdl Port (Between Dot Type
SW version
IRU and Dots)(1)
DGB1_1A 21.Q4 1 1-8 2-Branch
IRU 2242
DGB2_1A 21.Q4 2 1-8 2-Branch
IRU 8818 4-Branch
DGB1_1A 23.Q4 1 1, 3, 5, 7
IRU 8828 8-Branch
4-Branch
DGB1_1A 21.Q4 1 1-8
8-Branch
IRU 884x 4-Branch
DGB2_1A 21.Q4 2 1-8
IRU 88Rb 8-Branch
DGB3_1A 22.Q4 3 1-8 8-Branch
DGB4_1A 22.Q4 4 1-8 8-Branch
4-Branch
DGB1_1A 21.Q4 1 1-16
8-Branch
4-Branch
IRU 888x DGB2_1A 21.Q4 2 1-16
8-Branch
DGB3_1A 22.Q4 3 1-16 8-Branch
DGB4_1A 22.Q4 4 1-16 8-Branch
IRU 164x 4-Branch
DGB1_1A 21.Q4 1 1-8
IRU 16Fr 8-Branch

about:blank 185/268
3/5/24, 9:34 AM Building Blocks

IRU DGB Supported from IRU Number Rdl Port (Between Dot Type
SW version
IRU and Dots)(1)
4-Branch
DGB2_1A 21.Q4 2 1-8
8-Branch
DGB3_1A 22.Q4 3 1-8 8-Branch
DGB4_1A 22.Q4 4 1-8 8-Branch
(1) Some of the Rdl ports can be unused.

1.4.2.2 DGB with Cell Grouping

DGB1_2A and DGB1_2B for RDS, each allocates a subset of the available Dot ports on IRU 1.
DGB2_2A and DGB2_2B for RDS, each allocates a subset of the available Dot ports on IRU 2.

FHB

DGB Dot

IRU DGB1_2x Dot

DGB Dot

Ge27611A

Figure 342 DGB with Cell Grouping for FHB with One IRU

FHB

DGB Dot

IRU 1 DGB1_2x Dot

DGB Dot

IRU 2
DGB Dot

Ge27612A

Figure 343 DGB with Cell Grouping on IRU 1

about:blank 186/268
3/5/24, 9:34 AM Building Blocks

FHB

DGB Dot
IRU 1

DGB Dot

IRU 2 DGB2_2x Dot

DGB Dot

Ge27613A

Figure 344 DGB with Cell Grouping on IRU 2

Table 38 Connection Definition for DGB with Cell Grouping.

IRU DGB Supported from SW IRU Number Rdl Port (Between IRU Dot Type
version and Dots)(1)

DGB1_2A 23.Q4 1 1, 3 4-Branch

IRU 8818
DGB1_2B 23.Q4 1 5, 7 4-Branch
DGB1_2A 21.Q4 1 1-4 4-Branch
DGB1_2B 21.Q4 1 5-8 4-Branch
IRU 884x
DGB2_2A 21.Q4 2 1-4 4-Branch
DGB2_2B 21.Q4 2 5-8 4-Branch
DGB1_2A 21.Q4 1 1-8 4-Branch
DGB1_2B 21.Q4 1 9-16 4-Branch
IRU 888x
DGB2_2A 21.Q4 2 1-8 4-Branch
DGB2_2B 21.Q4 2 9-16 4-Branch
(1) Some of the Rdl ports can be unused.

1.4.3 Radio Dot Blocks for RDS

Definition of Radio Dot Block (RDB) for RDS:

The RDB defines the transceivers for the Dots in one DGB that support the same ABB.

– A DGB can have one RDB, or many RDBs using the Multi-Sector per Radio feature.

• Example: One RDB connects Transceivers 1 and 2 on a set of Dots to one ABB, and Transceivers 3 and 4 on the
same Dots to another ABB.

– Each RDB can only be connected to one ABB.

Unless the Dot uses external antennas covering different physical areas, consider using a single RDB that covers all
transceivers for the Dot group (RDB4_1A for 4-branch Dots and RDB8_1A for 8-branch Dots).

about:blank 187/268
3/5/24, 9:34 AM Building Blocks

Transceiver 1

Transceiver 2
DGB Dot ABB
Transceiver 3

Transceiver 4

RDB

Ge27614A

Figure 345 One RDB Covering the Dots in One DGB

RDB 1

Transceiver 1 ABB

Transceiver 2
DGB Dot
Transceiver 3

Transceiver 4
ABB

RDB 2
Ge27615A

Figure 346 Multiple RDBs with Multi-Sector per Radio Covering the Dots in One DGB

1.4.3.1 RDB2_1A

RDB2_1A is used for configurations with two Multicast Antenna Branches from Transceiver 1, in one DGB with a 2-branch
Dot. It can also be used with 4-branch Dots and 8-branch Dots using the Multi-Sector per Radio feature.

Connection
to ABB

1
Transceiver 1

DGB Dot

Physical Unit

Logical Unit
Ge27616A

Figure 347 RDB2_1A Block Diagram for 2-branch Dots

about:blank 188/268
3/5/24, 9:34 AM Building Blocks

Connection
to ABB
1
Transceiver 1

DGB
Dot

Physical Unit

Logical Unit
Ge27617A

Figure 348 RDB2_1A Block Diagram for Multi-Sector per Radio

Table 39 RDB2_1A Connection Definition.

Transceiver Connections to ABB

1
1
2

1.4.3.2 RDB2_1B

RDB2_1B is used for configurations with two Multicast Antenna Branches from Transceiver 2, in one DGB for one sector
using the Multi-Sector per Radio feature.

Connection
to ABB
1

DGB Transceiver 2
Dot

Physical Unit

Logical Unit
Ge27618A

Figure 349 RDB2_1B Block Diagram for Multi-sector per Radio

Table 40 RDB2_1B Connection Definition.

about:blank 189/268
3/5/24, 9:34 AM Building Blocks

Transceiver Connections to ABB

1
2
2

1.4.3.3 RDB2_1C

RDB2_1C is used for configurations with two Multicast Antenna Branches from Transceiver 3, in one DGB for one sector
using the Multi-Sector per Radio feature.

Connection
to ABB
1

DGB Dot
Transceiver 3

Physical Unit

Logical Unit
Ge27619A

Figure 350 RDB2_1C Block Diagram for Multi-sector per Radio

Table 41 RDB2_1C Connection Definition.

Transceiver Connections to ABB

1
3
2

1.4.3.4 RDB2_1D

RDB2_1D is used for configurations with two Multicast Antenna Branches for Transceiver 4, in one DGB for one sector using
the Multi-Sector per Radio feature.

about:blank 190/268
3/5/24, 9:34 AM Building Blocks

Connection
to ABB

DGB
Dot

Transceiver 4
2

Physical Unit

Logical Unit
Ge27620A

Figure 351 RDB2_1D Block Diagram for Multi-Sector per Radio

Table 42 RDB2_1D Connection Definition.

Transceiver Connections to ABB

1
4
2

1.4.3.5 RDB4_1A

RDB4_1A is used for configurations with two Multicast Antenna Branches from Transceiver 1 and 2, in one DGB with a 4-
branch Dot. It can also be used with 8-branch Dots using the Multi-Sector per Radio feature.

Connection
to ABB
1

Transceiver 1
2
Transceiver 2
DGB Dot
3

Physical Unit

Logical Unit
Ge27621A

Figure 352 RDB4_1A Block Diagram for 4-branch Dots

about:blank 191/268
3/5/24, 9:34 AM Building Blocks

Connection
to ABB
1

Transceiver 1
2
DGB Transceiver 2
Dot
3

Physical Unit

Logical Unit
Ge27622A

Figure 353 RDB4_1A Block Diagram for Multi-sector per Radio

Table 43 RDB4_1A Connection Definition.

Transceiver Connections to ABB

1
1
2
3
2
4

1.4.3.6 RDB4_1B

RDB4_1B is used for configurations with four Multicast Antenna Branches from Transceiver 3 and 4, in one DGB for one
sector using the Multi-Sector per Radio feature.

Connection
to ABB
1

2
DGB
Dot
Transceiver 3
3

Transceiver 4

Physical Unit

Logical Unit
Ge27623A

about:blank 192/268
3/5/24, 9:34 AM Building Blocks

Figure 354 RDB4_1B Block Diagram for Multi-sector per Radio

Table 44 RDB4_1B Connection Definition.

Transceiver Connections to ABB

1
3
2
3
4
4

1.4.3.7 RDB8_1A

RDB8_1A is used for configurations with eight Multicast Antenna Branches from Transceivers 1, 2, 3, and 4, in one DGB for
one sector.

Connection
to ABB
1

3
Transceiver 1

Transceiver 2
4
DGB Dot
Transceiver 3

Transceiver 4
5

Physical Unit

Logical Unit
Ge27624A

Figure 355 RDB8_1A Block Diagram for Multi-Sector per Radio

Table 45 RDB8_1A Connection Definition

Transceiver Connections to ABB

1
1
2
3
2
4

about:blank 193/268
3/5/24, 9:34 AM Building Blocks

Transceiver Connections to ABB

5
3
6
7
4
8

1.5 ABBs
Each ABB defines a unique way of combining antennas, Tower Mounted Amplifiers (TMAs), and Tower Mounted Frequency
shifters (TMFs) in one sector with connections to RBBs.

ABBs are named as follows: ABB[Rf]_[A][V]-TMA[T]TMF[F], where:

Rf Number of RF branches

A Number of antenna subunits

V Variant

T TMA variant (optional)

F TMF variant (optional)

Example 1: ABB2_2A

– Two RF branches

– Two antenna subunits

– Variant A

Example 2: ABB4_1B-TMA1

– Four RF branches

– One antenna subunit

– Variant B

– With TMA variant 1

Only RF connections are included in the ABB. Connections for control and supervision are not handled by the ABB concept.

The Antenna Unit Port (AU Port) is the antenna feeder port on the antenna unit, where the antenna branch is connected.

There is one antenna subunit per frequency band in one antenna unit, as follows:

– An ABB with two antenna subunits maps to two antenna units, see Figure 356.

– Two ABBs for different frequency bands can share the same dual band antenna, see Figure 357.

– If dual band TMA is used, the ABB contains the part of the TMA that covers the frequency band of the ABBs sector.
Two ABBs for different frequency bands can share the same TMA unit, see Figure 358.

about:blank 194/268
3/5/24, 9:34 AM Building Blocks

ABB

Antenna Unit 1

1 Antenna Subunit 1

Antenna Unit 2

1 Antenna Subunit 2

Ge13094B

Figure 356 ABB With Two Antenna Subunits and Two Antenna Units

Dual Band Antenna Unit

ABB 1
1-
Antenna Subunit
2+
Band A

ABB 2
1-
Antenna Subunit
2+
Band B

Ge13095B

Figure 357 Two Antenna Subunits from Two ABBs in One Dual Band Antenna Unit

about:blank 195/268
3/5/24, 9:34 AM Building Blocks

Dual Band TMA

ABB 1

1-
TMA Antenna Subunit
Band A 2+
Band A

ABB 2

1-
TMA Antenna Subunit
Band B 2+
Band B

Ge13096B

Figure 358 A Dual Band TMA for Two ABBs on Different Frequency Bands

1.5.1 ABBs for RDS

Antenna Building Block for RDS

1. ABB defines the Multicast antennas needed to cover one sector (MO SectorEquipmentFunction).

2. One ABB can be connected to one or multiple RDBs.

– Each RDB can only be connected to one ABB.

– Only one RDB per DGB to the same ABB.

– With multiple RDBs, all RDBs must support at least one common frequency band. It shall be possible to create a
carrier that uses resources from all RDBs.

1.5.1.1 Supported Building Block Combinations for Sectors Covered from One DGB

Sector
DGB RDB ABB Equipment
Function

Ge27570A

Figure 359 ABB for One RDB

The following combinations of ABBs and RDBs are supported:
Table 46 Supported ABB - RDB Combinations with One RDB
ABB RDB Supported from SW version Notes
RDB2_1A
RDB2_1B
ABB2_1B 21.Q4 -
RDB2_1C
RDB2_1D

about:blank 196/268
3/5/24, 9:34 AM Building Blocks
ABB RDB Supported from SW version Notes
RDB4_1A
ABB4_1D 21.Q4 -
RDB4_1B
For dual-band on same band, use 2x
21.Q4
ABB8_1D RDB8_1A ABB4_1D instead.
22.Q4 -

1.5.1.2 Supported Building Block Combinations for Sectors Covered from Two DGBs

Supported Building block combinations for sectors covered from two DGBs:

DGB RDB 1

Sector
ABB Equipment
Function

DGB RDB 2 ABB

Ge27571A

Figure 360 ABBs for Two RDBs

The following combinations of ABBs and RDBs are supported:
Table 47 Supported ABB - RDB Combinations with Two RDBs to the Same ABB
ABB RDB 1 RDB 2 Supported from SW version Notes
21.Q4 Two RD 22xx.
ABB4_2D RDB2_1A RDB2_1A One RD 44xx with one band
22.Q3
per IRU.
One RDB from(1): One RDB from(1):
RDB2_1A RDB2_1A
ABB4_2D RDB2_1B RDB2_1B 21.Q4 4-branch or 8-branch Dots.
RDB2_1C RDB2_1C
RDB2_1D RDB2_1D
For two dual-band
ABB8_2D RDB4_1A RDB4_1A 21.Q4
2T/2R+2T/2R.
One RDB from(1):
RDB8_1A RDB4_1A 21.Q4 -
RDB4_1B
ABB12_2A
One RDB from(1):
RDB4_1A RDB8_1A 21.Q4 -
RDB4_1B
Used for two quad-band
ABB16_2A RDB8_1A RDB8_1A 22.Q4 2T/2R + 2T/2R + 2T/2R +
2T/2R Dots.
(1) One RDB from each DGB. The two DGBs can have different RDBs. The two RDBs support the same frequency band.

Table 48 Supported Building Block Combinations with NR Combined Radio for Cell Grouping Using One ABB with Two
IRUs and One RDB per DGB
ABB RDB Supported from SW version Notes
NR Combined Radio:
ABB8_2D 2× RDB4_1A 22.Q4
One coverage area from each DGB.
NR Combined Radio:
ABB8_2D 2× RDB4_1B 22.Q4
One coverage area from each DGB.

1.5.1.3 Supported Building Block Combinations for Sectors Covered from Four DGBs
about:blank 197/268
3/5/24, 9:34 AM Building Blocks

DGB RDB 1

DGB RDB 2

Sector
ABB Equipment
Function

DGB RDB 3

DGB RDB 4

Ge28348A

Figure 361 ABB for Four RDBs

Supported Building block combinations for sectors covered from four DGBs. The following combinations of ABBs and RDBs
are supported:
Table 49 Supported Building Block Combinations with NR Combined Radio for Cell Grouping Using One ABB with Four
DGBs.
ABB RDB Supported from SW Version Notes
NR Combined Radio:
ABB16_4A 4× RDB4_1A 22.Q4
One coverage area from each DGB.
NR Combined Radio:
ABB16_4A 4× RDB4_1B 22.Q4
One coverage area from each DGB.
NR Combined Radio:
ABB32_4A 4× RDB8_1A 22.Q4
One coverage area from each DGB.

1.5.2 ABB Support per RBB for Radio

One ABB combined with one RBB covers one sector. RBBs and ABBs are connected through corresponding RF ports, see
Figure 362.

RBB RF Branch ABB

1 1
Antenna
Radio
2 2 Subunit

Ge13092B

Figure 362 RBB and ABB for One Sector

RF branches are defined in the ABB and connected to radios through RF port mapping.
If analog cross connection is used, each cross connect cable is marked in the figures with a corresponding RF port. This is to
show which RF branch that is supplying the RF signal for that connection. See Figure 363.

about:blank 198/268
3/5/24, 9:34 AM Building Blocks

RBB RF Branch ABB

1
Antenna
Radio
2 Subunit

RF Branch 3
RF Branch 1
3
Antenna
Radio
4 Subunit

Ge13093B

Figure 363 RBB and ABB with Analog Cross Connection

Table 50 shows which ABBs that are supported for an RBB. Only combinations that are supported by the Equipment
Configuration Tool (ECT) are shown. For more information on ECT, refer to Manage Equipment Configuration Tool in the
Baseband Radio Node library.

Table 50 ABB Support per RBB

RBB(1) ABB(2) ABB with TMA ABB with TMF for Y- or ψ-Coverage

ABB3_1A ABB3_1A-TMA1
RBB10_1A ABB3_2A ABB3_2A-TMA1 -
ABB3_3A ABB3_3A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB11_1A -
ABB2_2A ABB2_2A-TMA1
RBB11_1A for AIR ABB2_1A - -
RBB11_1C ABB1_1A ABB1_1A-TMA1 -
RBB11_1D ABB1_1A ABB1_1A-TMA1 -
RBB11_1E ABB1_1A ABB1_1A-TMA1 -
RBB11_1F ABB1_1A ABB1_1A-TMA1 -
RBB11_1G ABB1_1A ABB1_1A-TMA1 -
RBB11_1H ABB1_1A ABB1_1A-TMA1 -
RBB11_1J ABB1_1A ABB1_1A-TMA1 -
RBB11_1K ABB1_1A ABB1_1A-TMA1 -
RBB11_2A ABB1_1A ABB1_1A-TMA1 -
RBB11_2B ABB1_1A ABB1_1A-TMA1 -
RBB11_2C ABB1_1A ABB1_1A-TMA1 -
RBB11_2D ABB1_1A ABB1_1A-TMA1 -
RBB11_2E ABB1_1A ABB1_1A-TMA1 -
RBB11_2F ABB1_1A ABB1_1A-TMA1 -
RBB11_2G ABB1_1A ABB1_1A-TMA1 -
RBB11_2H ABB1_1A ABB1_1A-TMA1 -
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB12_1A
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
RBB12_1A for AIR ABB2_1A - -
ABB2_1A ABB2_1A-TMA1
RBB12_1C -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB12_1D -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB12_1E
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
ABB2_1A ABB2_1A-TMA1
RBB12_1F -
ABB2_2A ABB2_2A-TMA1

about:blank 199/268
3/5/24, 9:34 AM Building Blocks
RBB(1) ABB(2) ABB with TMA ABB with TMF for Y- or ψ-Coverage

ABB2_1A ABB2_1A-TMA1
RBB12_2A -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB12_2B -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB12_2C -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB12_2D ABB6_3B-TMF1
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB12_2E ABB6_3B-TMF1
ABB2_2A ABB2_2A-TMA1
ABB4_1A ABB4_1A-TMA1
RBB14_1A -
ABB4_2A ABB4_2A-TMA1
ABB4_1A ABB4_1A-TMA1
RBB14_2A -
ABB4_2A ABB4_2A-TMA1
ABB4_1A ABB4_1A-TMA2
RBB20_1A -
ABB4_2A ABB4_2A-TMA2
ABB2_1A
RBB20_1B - -
ABB2_2A
ABB2_1A
RBB20_1C - -
ABB2_2A
ABB2_1A
RBB20_1D - -
ABB2_2A
ABB2_1A
RBB20_1E - -
ABB2_2A
ABB6_1A ABB6_1A-TMA1
ABB6_2A ABB6_2A-TMA1
RBB20_2A -
ABB6_2B ABB6_2B-TMA1
ABB6_3A ABB6_3A-TMA1
ABB2_1A
RBB20_2B - -
ABB2_2A
ABB2_1A
RBB20_2C - -
ABB2_2A
ABB2_1A
RBB20_2D - -
ABB2_2A
ABB2_1A
RBB20_2E - -
ABB2_2A
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_1A
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
RBB22_1A for AIR ABB2_1A - -
ABB2_1A ABB2_2A-TMA1 ABB4_2C-TMF1
RBB22_1B
ABB2_2A ABB2_1A-TMA1 ABB6_3B-TMF1
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_1C
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
RBB22_1C for AIR ABB2_1A - -
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_1F
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
RBB22_1F for AIR ABB2_1A - -
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_1G
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
ABB2_1A ABB2_1A-TMA1
RBB22_1H -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_1J -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_1K -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_1L -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_1M -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_1N -
ABB2_2A ABB2_2A-TMA1

about:blank 200/268
3/5/24, 9:34 AM Building Blocks
RBB(1) ABB(2) ABB with TMA ABB with TMF for Y- or ψ-Coverage

ABB2_1A ABB2_1A-TMA1
RBB22_1P -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_1Q -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_2A
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
RBB22_2A for AIR ABB2_1A - -
ABB2_1A ABB2_1A-TMA1
RBB22_2B -
ABB2_2A ABB2_2A-TMA1
RBB22_2B for AIR ABB2_1A - -
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_2C
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
ABB2_1A ABB2_1A-TMA1
RBB22_2D -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2E -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2J -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_2K
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
ABB2_1A ABB2_1A-TMA1 ABB4_2C-TMF1
RBB22_2L
ABB2_2A ABB2_2A-TMA1 ABB6_3B-TMF1
ABB2_1A ABB2_1A-TMA1
RBB22_2M -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2N -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2P -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2Q -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_2A-TMA1
RBB22_2R -
ABB2_2A ABB2_1A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2S -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2T -
ABB2_2A ABB2_2A-TMA1
ABB2_1A ABB2_1A-TMA1
RBB22_2U -
ABB2_2A ABB2_2A-TMA1
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB24_1A -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
RBB24_1A for AIR ABB4_1B - -
ABB4_1A
RBB24_1B - -
ABB4_2A
ABB4_1A ABB4_1A-TMA1
RBB24_1C -
ABB4_2A ABB4_2A-TMA1
RBB24_1C for AIR ABB4_1A - -
RBB24_1C for AIR-MB ABB4_1A - -
ABB4_1A
RBB24_1D - -
ABB4_2A
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB24_2A -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
RBB24_2A for AIR ABB4_1B - -
ABB4_1A
RBB24_2B - -
ABB4_2A
ABB4_1A ABB4_1A-TMA1
RBB24_2D -
ABB4_2A ABB4_2A-TMA1
RBB24_2D for AIR ABB4_1B - -

about:blank 201/268
3/5/24, 9:34 AM Building Blocks
RBB(1) ABB(2) ABB with TMA ABB with TMF for Y- or ψ-Coverage

RBB24_2D for AIR-MB ABB4_1B - -

ABB4_1A
RBB24_2E - -
ABB4_2A
ABB4_1A
RBB24_2F - -
ABB4_2A
ABB3_1B ABB3_1B-TMA1
RBB32_1A ABB3_2B ABB3_2B-TMA1 -
ABB3_3A ABB3_3A-TMA1
ABB3_1B ABB3_1B-TMA1
RBB32_1B ABB3_2B ABB3_2B-TMA1 -
ABB3_3A ABB3_3A-TMA1
ABB3_1B ABB3_1B-TMA1
RBB32_3A ABB3_2B ABB3_2B-TMA1 -
ABB3_3A ABB3_3A-TMA1
ABB3_1B ABB3_1B-TMA1
RBB32_3B ABB3_2B ABB3_2B-TMA1 -
ABB3_3A ABB3_3A-TMA1
ABB4_1A
RBB40_1A - -
ABB4_2A
ABB4_1B
RBB40_1B - -
ABB4_2B
ABB4_1B
RBB40_1C - -
ABB4_2B
ABB4_1A
RBB40_2A - -
ABB4_2A
ABB4_1B
RBB40_2B - -
ABB4_2B
ABB4_1B
RBB40_2C - -
ABB4_2B
ABB4_1B ABB4_1B-TMA3
RBB42_1B -
ABB4_2B ABB4_2B-TMA3
ABB4_1B ABB4_1B-TMA3
RBB42_2D -
ABB4_2B ABB4_2B-TMA3
ABB4_1B ABB4_1B-TMA3
RBB42_2E -
ABB4_2B ABB4_2B-TMA3
ABB4_1A ABB4_1A-TMA1
RBB43_1A -
ABB4_2A ABB4_2A-TMA1
ABB4_1A ABB4_1A-TMA1
RBB43_4A -
ABB4_2A ABB4_2A-TMA1
ABB4_1A-TMA1
ABB4_1A ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_1B -
ABB4_2A ABB4_2A-TMA1
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
RBB44_1B with quad antenna ABB4_1B ABB4_1B-TMA3
-
feature ABB4_2B ABB4_2B-TMA3
ABB4_1A ABB4_1A-TMA1
RBB44_1D -
ABB4_2A ABB4_2A-TMA1
ABB4_1B ABB4_1B-TMA1
RBB44_1D for Radio 4449 B5 B12A -
ABB4_2B ABB4_2B-TMA1
ABB4_1A ABB4_1A-TMA1
ABB4_1C ABB4_1C-TMA1
RBB44_1D for Radio 4449 B5 B13 -
ABB4_2A ABB4_2A-TMA1
ABB4_2C ABB4_2C-TMA1
RBB44_1D for AIR ABB4_1A - -
RBB44_1D for AIR-MB ABB4_1A - -
ABB4_1A ABB4_1A-TMA1
RBB44_1E -
ABB4_2A ABB4_2A-TMA1
ABB4_1A ABB4_1A-TMA1
RBB44_1F -
ABB4_2A ABB4_2A-TMA1
RBB44_1G ABB4_1A ABB4_1A-TMA1 -

about:blank 202/268
3/5/24, 9:34 AM Building Blocks
RBB(1) ABB(2) ABB with TMA ABB with TMF for Y- or ψ-Coverage

ABB4_2A ABB4_2A-TMA1
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_1H -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_1J -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_1K -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
RBB44_1L ABB6_3C - -
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_1M -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
ABB4_1A
RBB44_1Q - -
ABB4_2A
ABB4_1A
RBB44_1R - -
ABB4_2A
ABB4_1A-TMA1
ABB4_1A ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_2C -
ABB4_2A ABB4_2A-TMA1
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
ABB4_1A ABB4_1A-TMA1
RBB44_2F -
ABB4_2A ABB4_2A-TMA1
ABB4_1B ABB4_1B-TMA1
RBB44_1F for Radio 4449 B5 B12A -
ABB4_2B ABB4_2B-TMA1
ABB4_1A ABB4_1A-TMA1
ABB4_1C ABB4_1C-TMA1
RBB44_1F for Radio 4449 B5 B13 -
ABB4_2A ABB4_2A-TMA1
ABB4_2C ABB4_2C-TMA1
RBB44_1F for AIR ABB4_1A - -
RBB44_1F for AIR-MB ABB4_1A - -
ABB4_1A ABB4_1A-TMA1
RBB44_2G -
ABB4_2A ABB4_2A-TMA1
ABB4_1A ABB4_1A-TMA1
RBB44_2H -
ABB4_2A ABB4_2A-TMA1
ABB4_1A
RBB44_2J - -
ABB4_2A
ABB4_1A
RBB44_2K - -
ABB4_2A
ABB4_1A
RBB44_2L - -
ABB4_2A
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_2M -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_2N -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
ABB4_1B-TMA1
ABB4_1B ABB4_1B-TMA2
RBB44_2P -
ABB4_2B ABB4_2B-TMA1
ABB4_2B-TMA2
RBB44_2Q ABB6_3C - -
RBB44_2R ABB4_1B ABB4_1B-TMA1 -
ABB4_2B ABB4_1B-TMA2
ABB4_2B-TMA1

about:blank 203/268
3/5/24, 9:34 AM Building Blocks
RBB(1) ABB(2) ABB with TMA ABB with TMF for Y- or ψ-Coverage

ABB4_2B-TMA2
ABB4_1A
RBB44_2U - -
ABB4_2A
ABB4_1A
RBB44_2V - -
ABB4_2A
ABB4_1A
RBB44_3A - -
ABB4_2A
ABB4_1A
RBB44_3B - -
ABB4_2A
RBB44_3C ABB6_3C - -
RBB44_3D ABB6_3C - -
ABB4_1A ABB4_1A-TMA1
RBB44_4A -
ABB4_2A ABB4_2A-TMA1
ABB6_2C
RBB46_1A - -
ABB6_3C
ABB6_2C
RBB46_2A - -
ABB6_3C
ABB8_3A
RBB66_1A - -
ABB8_4A
ABB8_3A
RBB66_3A - -
ABB8_4A
ABB8_1A
RBB88_1A for 8TX/8RX radios - -
ABB8_1C
ABB8_1C
RBB88_1A for 4TX/8RX radios - -
ABB8_2C
RBB88_1A for RRUL 81 ABB8_1B - -
ABB8_1A
RBB88_2A for 8TX/8RX radios - -
ABB8_1C
ABB8_1C
RBB88_2A for 4TX/8RX radios - -
ABB8_2C
RBB88_2A for RRUL 81 ABB8_1B - -
(1) AIR does not support ABBs with TMA.
(2) For ABB with NR Combined Radio, see Radio Configurations for NR.

1.5.3 Guidelines for Configuring Sectors with More than Two Antenna Branches

This section shows the guidelines for configuring sectors with more than two antenna branches.

1.5.3.1 Map Physical Antenna Ports to ABB for Radio

Polarization A and B are two different polarizations for the antenna ports. Polarization A can be (+) with polarization B
being (-) or conversely. The AU port numbering is counted from left to right facing the front of the antenna unit. Use the
figure below to map the physical antenna port name to the AU port number and polarization.
Note: The antenna port name is dependent on the manufacturer.

about:blank 204/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port ABB Physical antenna

1 1 z
1 polarization A
Antenna front
2 2
1 polarization B x y

3 3 -45 -45 -45 -45

+45 +45 +45 +45
2 polarization A

4 4
2 polarization B
Antenna
5 5 Subunit 1
3 polarization A

1 polarization A
1 polarization B
2 polarization A
2 polarization B
3 polarization A
3 polarization B
4 polarization A
4 polarization B
6 6
3 polarization B

7 7
4 polarization A

8 8
4 polarization B

AU Port 1 2 3 4 5 6 7 8
Ge23858

Figure 364 Example of Port Numbering - ABB to Physical Antenna

1.5.3.2 Sectors with Eight TX/RX Antenna Branches for the Same Band(s)

This section describes the sectors with eight TX/RX antenna branches for the same band(s).

1.5.3.2.1 Recommended Configuration Using ABB8_1A or ABB8_1C

The recommended configuration for sites with eight TX/RX antenna branches that all support the same band(s) is to use
RBB88_1A or RBB88_2A in combination with ABB8_1A or ABB8_1C.
To optimize performance for 8TX/8RX carriers, one single antenna is used. The choice between ABB8_1A and ABB8_1C
can for example be made for the most practical installation. Both ABBs will give the same performance.

about:blank 205/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch
ABB
1
Node 1 Data 1 A 1 polarization A

2
B 1 polarization B

3
C 2 polarization A

4
D 2 polarization B
Radio 1 5
E 3 polarization A

6
F 3 polarization B

7
G 4 polarization A

8
Data 2 H 4 polarization B

Ge23859

Figure 365 RBB88_1A + ABB8_1A

RI Link RF Branch
RBB ABB
1
Node 1 Data A 1 polarization A

2
B 1 polarization B

3
C 2 polarization A

4
D 2 polarization B
Radio 1 Antenna
5 Subunit 1
E 3 polarization A

6
F 3 polarization B

7
G 4 polarization A

8
Node 2 Data H 4 polarization B

Ge28461A

Figure 366 RBB88_1A + ABB8_1C

The two configurations can be used for 8TX/8RX carriers with any 8-port radio, where all ports support the same band(s).
It is also possible to mix 8TX/8RX carriers with 4TX/4RX carriers. Deterministic Carrier Allocation must be used for the
4TX/4RX carrier to get correct polarization for the antenna branche polarization. This is supported with 8-port radios,
including radios from Radio Group 4 and 5.
Note: RRUL 81 does not support 4TX/4RX carriers.

about:blank 206/268
3/5/24, 9:34 AM Building Blocks

Alt 1.
SectorCarrier::RfBranchTxRef – 1,2,3,4; noOfTxAntennas = 4
SectorCarrier::RfBranchRxRef – 1,2,3,4; noOfRxAntennas = 4

RI Link RF Branch
RBB ABB
1
Node 1 Data 1 A 1 polarization A

2
B 1 polarization B

Antenna Subunit 1
C 2 polarization A

4
D 2 polarization B
Radio 1 5
E 3 polarization A

6
F 3 polarization B

7
G 4 polarization A

8
Node 2 Data 2 H 4 polarization B

Alt 2.
SectorCarrier::RfBranch
Ge23860

Figure 367 Deterministic Carrier Allocation for two 4TX/4RX Carriers with ABB8_1A

Alt 1.
SectorCarrier::RfBranchTxRef – 1,2,3,4; noOfTxAntennas = 4
SectorCarrier::RfBranchRxRef – 1,2,3,4; noOfTxAntennas = 4

RI Link RF Branch
RBB ABB
1
Node 1 Data A 1 polarization A

2
B 1 polarization B

3
C 2 polarization A

4
D 2 polarization B
Radio 1 Antenna
5 Subunit 1
E 3 polarization A

6
F 3 polarization B

7
G 4 polarization A

8
Node 2 Data H 4 polarization B

Alt 2.
SectorCarrier::RfBranchTxRef – 5,7,6,8; noOfTxAntennas = 4
SectorCarrier::RfBranchRxRef – 5,7,6,8; noOfTxAntennas = 4
Ge28462A

Figure 368 Deterministic Carrier Allocation for two 4TX/4RX Carriers with ABB8_1C

about:blank 207/268
3/5/24, 9:34 AM Building Blocks
The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this, the RF Branches must be sorted for each sector when creating the Site Equipment
installation file.
For ABB8_1A, use the following RF Branch sequence:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-5</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-6</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-7</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-8</rfBranchRef>
<userLabel>Sector configured with RBB88_1A and ABB8_1A</userLabel>
</SectorEquipmentFunction>
For ABB8_1C, use the following RF Branch sequence:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-5</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-7</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-6</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-8</rfBranchRef>
<userLabel>Sector configured with RBB88_1A and ABB8_1C</userLabel>
</SectorEquipmentFunction>
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.
LTE can use co-polarized or cross-polarized beam-forming antenna port mapping. NR and LTE+NR must use cross-
polarized, which is the default value.
<AntennaSubunit>
<AntennaSubunitId>1</AntennaSubunitId>
<commonChBeamfrmPortMap>CROSS_POLARIZED</commonChBeamfrmPortMap>
</AntennaSubunit>
See Figure 367, Figure 368 and examples in Deterministic Carrier Allocation for how to configure Deterministic Carrier
Allocation.

1.5.3.2.2 Alternative Configuration Using ABB8_1B

The alternative configuration for sites with eight antenna branches that all support the same band(s) is to use RBB88_1A
or RBB88_2A in combination with ABB8_1B, which uses one single antenna to optimize the performance for 8TX/8RX
carriers.
When used only for 8TX/8RX carriers, the performance is the same as described in Recommended Configuration Using
ABB8_1A or ABB8_1C , but there are limitations when 4TX/4RX carriers are used.

about:blank 208/268
3/5/24, 9:34 AM Building Blocks

RI Link RF Branch
RBB ABB
1
Node 1 Data 1 A 1 polarization A

2
B 1 polarization B

Antenna Subunit 1
C 2 polarization A

4
D 2 polarization B
Radio 1 5
E 3 polarization A

6
F 3 polarization B

7
G 4 polarization A

8
Node 2 Data 2 H 4 polarization B

Ge23861

Figure 369 RBB88_1A + ABB8_1B

This configuration can be used for 8TX/8RX carriers with any 8-port radio. It is also possible to mix 8TX/8RX carriers with
4TX/4RX carriers. Then Deterministic Carrier Allocation, must be used for the 4TX/4RX carrier to get correct polarization
for the antenna branches.
The 4TX/4RX carriers with this antenna configuration are not supported with radios from Radio Group 4 and 5.

about:blank 209/268
3/5/24, 9:34 AM Building Blocks

Alt 1.
SectorCarrier::RfBranchTxRef – 1,2,5,6; noOfTxAntennas = 4
SectorCarrier::RfBranchRxRef – 1,2,5,6; noOfRxAntennas = 4

RI Link RF Branch
RBB ABB
1
Node 1 Data 1 A 1 polarization A

2
B 1 polarization B

Antenna Subunit 1
C 2 polarization A

4
D 2 polarization B
Radio 1 5
E 3 polarization A

6
F 3 polarization B

7
G 4 polarization A

8
Node 2 Data 2 H 4 polarization B

Alt 2.
SectorCarrier::RfBranchTxRef – 3,4,7,8; noOfTxAntennas = 4
SectorCarrier::RfBranchRxRef – 3,4,7,8; noOfRxAntennas = 4
Ge23862

Figure 370 4TX/4RX Carriers with Deterministic Carrier Allocation Using RBB88_1A + ABB8_1B

The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this is to sort the RF Branches for each sector when creating the Site Equipment installation
file.
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-5</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-6</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-7</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-8</rfBranchRef>
<userLabel>Sector configured with RBB88_1A and ABB8_1B</userLabel>
</SectorEquipmentFunction>
For ABB8_1B, use the following RF Branch order:
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.
LTE can use co-polarized or cross-polarized beam-forming antenna port mapping. NR and LTE+NR must use cross-
polarized, which is the default value.
<AntennaSubunit>
<AntennaSubunitId>1</ AntennaSubunitId >
about:blank 210/268
3/5/24, 9:34 AM Building Blocks
<commonChBeamfrmPortMap>CROSS_POLARIZED</commonChBeamfrmPortMap>
</AntennaSubunit>

1.5.3.3 Sectors with Four TX and Eight RX Antenna Branches for the Same Band(s)

This section describes the sectors with four TX/RX and eight TX/RX antenna branches for the same band(s).

1.5.3.3.1 Recommended Configuration Using ABB8_1C or ABB8_2C

The recommended configuration for sites with eight antenna branches, four with TX/RX and four with RX only on the same
band is to use RBB88_1A or RBB88_2A in combination with ABB8_1C or ABB8_2C.
To optimize performance for 4TX/8RX carriers, all TX branches for the same band use the same antenna.

RI Link RF Branch
RBB ABB
TX/RX RX 1
Node 1 Data A 1 polarization A

TX/RX RX 2
B 1 polarization B

TX/RX RX 3
C 2 polarization A

TX/RX RX 4
D 2 polarization B
Radio 1 Antenna
RX TX/RX 5 Subunit 1
E 3 polarization A

RX TX/RX 6
F 3 polarization B

RX TX/RX 7
G 4 polarization A

RX TX/RX 8
Node 2 Data H 4 polarization B

Band(s) A

Band(s) B
Ge28463A

Figure 371 RBB88_1A + ABB8_1C for 4TX/8RX radios

RI Link RF Branch
RBB ABB
TX/RX RX 1
Node 1 Data A 1 polarization A

TX/RX RX 2
B 1 polarization B
Antenna
TX/RX RX 3 Subunit 1
C 2 polarization A

TX/RX RX 4
D 2 polarization B
Radio 1
RX TX/RX 5
E 1 polarization A

RX TX/RX 6
F 1 polarization B
Antenna
RX TX/RX 7 Subunit 2
G 2 polarization A

RX TX/RX 8
Node 2 Data H 2 polarization B

Band(s) A

Band(s) B
Ge28464A

about:blank 211/268
3/5/24, 9:34 AM Building Blocks

Figure 372 RBB88_1A + ABB8_2C for 4TX/8RX radios

It is possible to use 4TX/4RX carriers on a 4TX/8RX radio. This is configured in the same way as on an 8TX/8RX radio.
Deterministic Carrier Allocation is used for the 4TX/4RX carrier according to Deterministic Carrier Allocation for two
4TX/4RX Carriers with ABB8_1C.
The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this, the RF Branches must be sorted for each sector when creating the Site Equipment
installation file.
Use the following RF Branch sequence for both ABB8_1C and ABB8_2C:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-5</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-7</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-6</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-8</rfBranchRef>
<userLabel>User_label_string</userLabel>
</SectorEquipmentFunction>
Where user label string and tags are replaced with one of the following:

– <userLabel>Sector_configured_with_RBB88_1A_and_ABB8_1C</userLabel>

– <userLabel>Sector_configured_with_RBB88_1A_and_ABB8_2C</userLabel>

If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.
LTE can use co-polarized or cross-polarized beam-forming antenna port mapping. NR and LTE+NR must use cross-
polarized, which is the default value.
ABB8_1C
<AntennaSubunit>
<AntennaSubunitId>1</AntennaSubunitId>
<commonChBeamfrmPortMap>CROSS_POLARIZED</commonChBeamfrmPortMap>
</AntennaSubunit>
ABB8_2C
<AntennaSubunit>
<AntennaSubunitId>1</AntennaSubunitId>
<commonChBeamfrmPortMap>CROSS_POLARIZED</commonChBeamfrmPortMap>
</AntennaSubunit>
<AntennaSubunit>
<AntennaSubunitId>2</AntennaSubunitId>
<commonChBeamfrmPortMap>CROSS_POLARIZED</commonChBeamfrmPortMap>
</AntennaSubunit>

1.5.3.4 Sectors with Four Antenna Branches for the Same Band

1.5.3.4.1 Recommended Configuration for Sectors with Four Antenna Branches from One Radio

about:blank 212/268
3/5/24, 9:34 AM Building Blocks
The recommended configuration for sites with four antenna branches that all support the same band(s) is to use
RBB44_1D or RBB44_2F in combination with ABB4_1A, which uses one single antenna to optimize the performance for
4TX/4RX carriers.

RBB RF Branch ABB

1
Node 1

Antenna Subunit
Data 1 A 1 polarization A

2
B 1 polarization B
Radio 1

1
3
C 2 polarization A

4
Node 2 Data 2 D 2 polarization B

Ge23863

Figure 373 RBB44_1D + ABB4_1A

This configuration can be used for 4TX/4RX carriers with any 4-port radio, where all ports support the same band(s). It is
also possible to mix 4TX/4RX carriers with carriers that have only two branches. Then Deterministic Carrier Allocation,
must be used for the carrier with two branches to get correct polarization for the antenna branches.
The exceptions where this configuration is not recommended is for some multiband radios where only specific ports have
the same frequency band support or have the required output power capability. One such radio variant is Radio 4449 B5
B12, where ports RF A and RF C have higher power and must be used for 2TX/4RX carriers. ABB4_1A will use the same
polarization for both TX branches.

2TX/2RX carrier alt. 1

SectorCarrier::RfBranchTxRef – 1,2; noOfTxAntennas = 2
SectorCarrier::RfBranchRxRef – 1,2; noOfRxAntennas = 2

RBB RF Branch ABB

1
Node 1
Antenna Subunit
Data 1 A 1 polarization A

2
B 1 polarization B
Radio 1
1

3
C 2 polarization A

4
Node 2 Data 2 D 2 polarization B

2TX/2RX carrier alt. 2

SectorCarrier::RfBranchTxRef – 3,4; noOfTxAntennas = 2
SectorCarrier::RfBranchRxRef – 3,4; noOfRxAntennas = 2
Ge23864

Figure 374 2TX/2RX Carrier with Deterministic Carrier Allocation Using RBB44_1D + ABB4_1A

The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this is to sort the RF Branches for each sector when creating the Site Equipment installation
file.
For ABB4_1A, use the following RF Branch sequence:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>

about:blank 213/268
3/5/24, 9:34 AM Building Blocks
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<userLabel>Sector configured with RBB44_1C and ABB4_1A</userLabel>
</SectorEquipmentFunction>
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.

1.5.3.4.2 Alternative Configuration for Sectors with Four Antenna Branches from One Radio

An alternative configuration for sites with four antenna branches that all support the same band(s) is to use RBB44_1D or
RBB44_2F in combination with ABB4_1B, which uses one single antenna to optimize the performance for 4TX/4RX
carriers.

Carrier using high power ports

SectorCarrier::RfBranchTxRef – 1,3; noOfTxAntennas = 2

RBB RF Branch ABB

1
Node 1

Antenna Subunit
Data 1 A 1 polarization A

2
B 1 polarization B
Radio 1

1
3
C 2 polarization A

4
Node 2 Data 2 D 2 polarization B

Ge23865

Figure 375 RBB44_1D + ABB4_1B

This configuration is recommended for some multiband radios where only specific ports support the same band(s) or have
the required output power capability. One such radio variant is Radio 4449 B5 B12, where ports RF A and RF C have higher
power and must be used for 2TX/4RX carriers. Deterministic Carrier Allocation must be used to allocate the TX carrier
branches to the correct polarization (see the figure above).
When used with 4TX/4RX carriers, this configuration has the same performance as when ABB4_1A is used. In contrast
with the case below with two radio units, the radio performance is not improved when crossing RF cable 2 and 3.
The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this is to sort the RF Branches for each sector when creating the Site Equipment installation
file.
For ABB4_1B, use the following RF Branch sequence:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<userLabel>Sector configured with RBB44_1C and ABB4_1B</userLabel>
</SectorEquipmentFunction>
about:blank 214/268
3/5/24, 9:34 AM Building Blocks
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.

1.5.3.4.3 Sectors with Four Antenna Branches from Two Radios

The recommended configuration for sites with four antenna branches that all support the same bands from two radio units
is to use RBB44_1B or RBB44_2C in combination with ABB4_1B, which uses one single antenna to optimize the
performance for 4TX/4RX carriers. This configuration is preferred because each pair of branches with the same
polarization will come from the same radio. This optimizes the performance because the timing uncertainty is smaller for
branches from the same radio.

RBB RF Branch ABB

1

Antenna Subunit
Data 1 A 1 polarization A
Node 1 Radio 1 2
Data 2 B 1 polarization B

1
3
Data 1 A 2 polarization A
Node 2 Radio 2 4
Data 2 B 2 polarization B

Ge23866

Figure 376 RBB44_2C + ABB4_1B

It is also possible to mix 4TX/4RX carriers with 2TX/2RX carriers. Then Deterministic Carrier Allocation must be used for
the 2TX/2RX carrier to get correct polarization for the antenna branches.

2TX/2RX carrier alt. 1

SectorCarrier::RfBranchTxRef – 1,3; noOfTxAntennas = 2
SectorCarrier::RfBranchRxRef – 1,3; noOfRxAntennas = 2

RBB RF Branch ABB

1
Antenna Subunit

Data 1 A 1 polarization A
Node 1 Radio 1 2
Data 2 B 1 polarization B
1

3
Data 1 A 2 polarization A
Node 2 Radio 2 4
Data 2 B 2 polarization B

2TX/2RX carrier alt. 2

SectorCarrier::RfBranchTxRef – 2,4; noOfTxAntennas = 2
SectorCarrier::RfBranchRxRef – 2,4; noOfRxAntennas = 2
Ge23867

Figure 377 2TX/2RX Carrier with Deterministic Carrier Allocation Using RBB44_2C + ABB4_1B

The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this is to sort the RF Branches for each sector when creating the Site Equipment installation
file.

about:blank 215/268
3/5/24, 9:34 AM Building Blocks
For ABB4_1B, use the following RF Branch sequence:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<userLabel>Sector configured with RBB44_1C and ABB4_1B</userLabel>
</SectorEquipmentFunction>
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.

1.5.3.4.4 Sectors Connected to Two Nodes Where One Node Uses Two Radios but the Other Node Only Uses One
Radio

The recommended configuration for sites where one node uses antenna branches from two radios that support the same
band, where only one radio is used by the other node is to use RBB44_1B or RBB44_2C + ABB4_1A for node 1 and
RBB22_1B + ABB2_1A for node 2, which uses one single antenna to optimize the performance for 4TX/4RX carriers.

RBB (LTE) RF Branch ABB (LTE)

1

Antenna Subunit
Data 1 A 1 polarization A
Node 1 Radio 1
(LTE) (L+W) 2
B 1 polarization B

1
3
Data 1 A 2 polarization A
Radio 2
(L) 4
B 2 polarization B

Data 1 -45
Baseband Radio 1
LTE (L+W)
Antenna

Data 2 +45

Data 1 -45
Baseband Radio 2
WCDMA (L) +45

RBB (WCDMA) RF Branch ABB (WCDMA)

1
Antenna
Subunit

A 1 polarization A
Radio 1
1

Node 2 (L+W) 2
Data 2 B 1 polarization B
(WCDMA)

Ge23868

Figure 378 Example with LTE Using RBB44_2C + ABB4_1A and WCDMA Using RBB22_1B + ABB2_1A

This configuration is preferred because, although the performance for the 4TX/4RX carrier is not optimized, the 2-branch
carriers from node 2 will have different polarizations for the two receiving branches. This optimizes the RX performance for

about:blank 216/268
3/5/24, 9:34 AM Building Blocks
the 2TX/2RX carriers.
The beam-forming algorithm expects to have all antenna ports for one polarization first and then the antenna ports for the
other polarization. To achieve this is to sort the RF Branches for each sector when creating the Site Equipment installation
file.
For ABB4_1B, use the following RF Branch sequence:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<userLabel>Sector configured with RBB44_2C and ABB4_1B</userLabel>
</SectorEquipmentFunction>
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.

1.5.3.5 Sectors Where Different Antenna Branches Support Different Bands

1.5.3.5.1 Configuration for Radios with RF Ports that Supports Different Frequency Ranges (Multiband Radios
and/or Radios for Different Bands)

The recommended configurations, for radios with multiple antenna branches for the same band(s) is to use one RBB that
covers all bands for the same sector.
To optimize performance for 4TX/4RX carriers, one single antenna per band is preferred: ABB8_2C but using two antennas,
ABB8_4A is also supported.
Radio 8843 with four RF ports for band 2 (band A) and four other RF ports for band 66A (band B) is used as an example
below.

RBB RF Branch ABB

1
Antenna Subunit
1 polarization A
Node 1 Data 1 A
B
2 1 polarization B
A B
N
1

D 3 2 polarization A
C
A 4 2 polarization B
D
Radio 1 5
E
Antenna Subunit

1 polarization A
B
6
A F
N 1 polarization B
D 7
2

G
2 polarization A
B 8
Node 2 Data 2 H
2 polarization B

Ge23869

Figure 379 RBB88_1A + ABB8_2C

about:blank 217/268
3/5/24, 9:34 AM Building Blocks
This is configured as an 8-port single band radio with RBB88_1A + ABB8_1A exactly as in Map Physical Antenna Ports to
ABB for Radio. For carriers that use all available RF ports for the specific band, Deterministic Carrier Allocation is not
needed, since the radio node knows the supported frequency range for each RF port.
With this radio it is possible to support higher output power on two ports (A, D and E, H for the respective bands). Because
all four ports per band are TX capable, Deterministic Carrier Allocation is used to select the two high output power RF ports.

2TX on Band A
SectorCarrier::RfBranchTxRef – 1, 4; noOfTxAntennas = 2

RBB RF Branch ABB

Antenna Subunit
1 polarization A
Node 1 Data 1 A
B
2 1 polarization B
A B
N

1
D 3 2 polarization A
C
A 4 2 polarization B
D
Radio 1 5
E

Antenna Subunit
1 polarization A
B
6
A F
N 1 polarization B
D 7

2
G
2 polarization A
B 8
Node 2 Data 2 H
2 polarization B

2TX on Band B.
SectorCarrier::RfBranchTxRef – 5, 8; noOfTxAntennas = 2
Ge23870

Figure 380 Deterministic Carrier Allocation Using RBB88_1A + ABB8_2C

The beam-forming algorithm expects to have all antenna ports for one polarization first and that the antenna ports for the
other polarization. To achieve this is to sort the RF Branches for each sector when creating the Site Equipment installation
file.
For ABB8_2C, the following RF Branch sequence must be used:
<SectorEquipmentFunction>
<sectorEquipmentFunctionId>1</sectorEquipmentFunctionId>
<administrativeState>UNLOCKED</administrativeState>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-1</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-3</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-5</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-7</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-2</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-4</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-6</rfBranchRef>
<rfBranchRef>ManagedElement=1,Equipment=1,AntennaUnitGroup=1,RfBranch=S1-8</rfBranchRef>
<userLabel>Sector configured with RBB88_1A and ABB8_2C</userLabel>
</SectorEquipmentFunction>

about:blank 218/268
3/5/24, 9:34 AM Building Blocks
If the Equipment Configuration Tool (ECT) is used, the RF Branches will automatically be configured in the correct
sequence.

1.5.4 ABB1_1A
ABB1_1A has one RF branch and one antenna subunit.
Figure 381 shows ABB1_1A.
Figure 382 shows ABB1_1A-TMA1, with TMA.

RF Branch AU Port

1 Antenna
1
Subunit 1

Ge12879B

Figure 381 ABB1_1A Block Diagram

RF Branch RF Branch AU Port

1 1 Antenna
TMA 1 1
Subunit 1

Ge12880B

Figure 382 ABB1_1A-TMA1 Block Diagram, with TMA

1.5.5 ABB2_1A
ABB2_1A has two RF branches and one antenna subunit.
Figure 383 shows ABB2_1A.
Figure 384 shows ABB2_1A-TMA1, with TMA.

RF Branch AU Port
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

Ge12881B

Figure 383 ABB2_1A Block Diagram

about:blank 219/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
TMA 1
2 2
1 polarization B
Subunit 1

Ge12882B

Figure 384 ABB2_1A-TMA1 Block Diagram, with TMA

1.5.6 ABB2_1B for RDS

ABB2_1B is used for a configuration with two Multicast Antenna Branches from one RDB.

Connection
to RDB Multicast Antenna Branch

1
1
RDB 2
2

Ge27572A

Figure 385 ABB2_1B

Table 51 ABB2_1B Connection Definition

RDB Connection to RDB Multicast Antenna Branch
1 1
1
2 2

ABB2_1B can be used with RDBs for RDS according to ABBs for RDS.
Table 52 ABB2_1B Carrier Allocation
Transceivers per Radio Part RAT Supported from SW Version Configuration
GSM
21.Q4 Supported with 2-WRXD.
WCDMA
1 LTE
Supported with up to 2x2 MIMO and
NR 21.Q4
2-WRXD.
ESS

1.5.7 ABB2_2A
ABB2_2A has two RF branches and two antenna subunits.
Figure 386 shows ABB2_2A.
Figure 387 shows ABB2_2A-TMA1, with TMA.

about:blank 220/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port

1 Antenna
1
Subunit 1

2 Antenna
1
Subunit 2

Ge12877B

Figure 386 ABB2_2A Block Diagram

RF Branch RF Branch AU Port

1 1 Antenna
1
Subunit 1

TMA 1

2 2 Antenna
1
Subunit 2

Ge12878B

Figure 387 ABB2_2A-TMA1 Block Diagram, with TMA

1.5.8 ABB3_1A
ABB3_1A has three RF branches and one antenna subunit.
Figure 388 shows ABB3_1A.
Figure 389 shows ABB3_1A-TMA1, with TMA.

RF Branch AU Port
1
1

2 Antenna
2 polarization A
Subunit 1
3
2 polarization B

Ge12834B

Figure 388 ABB3_1A Block Diagram

about:blank 221/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1

2 2 Antenna
2 polarization A
Subunit 1
3 TMA 1 3
2 polarization B

Ge12835B

Figure 389 ABB3_1A-TMA1 Block Diagram, with TMA

1.5.9 ABB3_1B
ABB3_1B has three RF branches and one antenna subunit.
Figure 390 shows ABB3_1B.
Figure 391 shows ABB3_1B-TMA1, with TMA.

RF Branch AU Port
1
1 polarization A

2 Antenna
1 polarization B
Subunit 1
3
2

Ge14438B

Figure 390 ABB3_1B Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 2
1 polarization B
Antenna
Subunit 1
3 3
2

Ge14439B

Figure 391 ABB3_1B-TMA1 Block Diagram, with TMA

1.5.10 ABB3_2A
ABB3_2A has three RF branches and two antenna subunits.
Figure 392 shows ABB3_2A.
Figure 393 shows ABB3_2A-TMA1, with TMA.

about:blank 222/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port

1 Antenna
1
Subunit 1

2
1 polarization A
Antenna
3 Subunit 2
1 polarization B

Ge12836B

Figure 392 ABB3_2A Block Diagram

RF Branch RF Branch AU Port

1 1 Antenna
1
Subunit 1

2 2
1 polarization A
Antenna
3 TMA 1 3
1 polarization B
Subunit 2

Ge12837B

Figure 393 ABB3_2A-TMA1 Block Diagram, with TMA

1.5.11 ABB3_2B
ABB3_2B has three RF branches and two antenna subunits.
Figure 394 shows ABB3_2B.
Figure 395 shows ABB3_2B-TMA1, with TMA.

about:blank 223/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

3 Antenna
1
Subunit 2

Ge14440B

Figure 394 ABB3_2B Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 2
1 polarization B
Subunit 1

3 3 Antenna
1
Subunit 2

Ge14441B

Figure 395 ABB3_2B-TMA1 Block Diagram, with TMA

1.5.12 ABB3_3A
ABB3_3A has three RF branches and three antenna subunits.
Figure 396 shows ABB3_3A.
Figure 397 shows ABB3_3A-TMA1, with TMA.
Figure 398 shows ABB3_3A-TMA2, with TMA.

about:blank 224/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port

1 Antenna
1
Subunit 1

2 Antenna
1
Subunit 2

3 Antenna
1
Subunit 3

Ge12838B

Figure 396 ABB3_3A Block Diagram

RF Branch RF Branch AU Port

1 1 Antenna
1
Subunit 1

2 2 Antenna
1
Subunit 2

TMA 1

3 3 Antenna
1
Subunit 3

Ge12839B

Figure 397 ABB3_3A-TMA1 Block Diagram, with TMA

about:blank 225/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1 Antenna
1
Subunit 1

TMA 1

2 2 Antenna
1
Subunit 2

3 3 Antenna
1
Subunit 3

Ge14443B

Figure 398 ABB3_3A-TMA2 Block Diagram, with TMA

1.5.13 ABB4_1A
ABB4_1A has four RF branches and one antenna subunit. RF ports 1 and 3 have one polarization, while RF ports 2 and 4
have the opposite polarization.
Figure 399 shows ABB4_1A.
Figure 400 shows ABB4_1A-TMA1, with TMA.
Figure 401 shows ABB4_1A-TMA2, with TMA.

RF Branch AU Port
1
1 polarization A

2
1 polarization B
Antenna
3 Subunit 1
2 polarization A

4
2 polarization B

Ge12840B

Figure 399 ABB4_1A Block Diagram

about:blank 226/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 2
1 polarization B
Antenna
3 3 Subunit 1
2 polarization A

4 TMA 2 4
2 polarization B

Ge12841B

Figure 400 ABB4_1A-TMA1 Block Diagram, with TMA

Figure 401 ABB4_1A-TMA2 Block Diagram, with TMA

1.5.14 ABB4_1B
ABB4_1B has four RF branches and one antenna subunit. RF ports 1 and 3 have one polarization, while RF ports 2 and 4
have the opposite polarization.
Figure 402 shows ABB4_1B.
Figure 403 shows ABB4_1B-TMA1, with TMA.
Figure 404 shows ABB4_1B-TMA2, with TMA.
Figure 405 shows ABB4_1B-TMA3, with TMA.

about:blank 227/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A

2
1 polarization B
Antenna
3 Subunit 1
2 polarization A

4
2 polarization B

Ge12842B

Figure 402 ABB4_1B Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 3
1 polarization B
Antenna
3 2 Subunit 1
2 polarization A

4 TMA 2 4
2 polarization B

Ge12843B

Figure 403 ABB4_1B-TMA1 Block Diagram, with TMA

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 3
1 polarization B
Antenna
3 2 Subunit 1
2 polarization A

4 TMA 2 4
2 polarization B

Ge12980B

Figure 404 ABB4_1B-TMA2 Block Diagram, with TMA

about:blank 228/268
3/5/24, 9:34 AM Building Blocks

Figure 405 ABB4_1B-TMA3 Block Diagram, with TMA

1.5.15 ABB4_1D for RDS

ABB4_1D is used for a configuration with four Multicast Antenna Branches from one RDB.

Connection
to RDB Multicast Antenna Branch

1
1
2
2
RDB 3
3
4
4

Ge27573A

Figure 406 ABB4_1D

Table 53 ABB4_1D Connection Definition

RDB Connection to RDB Multicast Antenna Branch
1 1
2 2
1
3 3
4 4

ABB4_1D can be used with RDBs for RDS according to ABBs for RDS.
Table 54 ABB4_1D Carrier Allocation
Transceivers per Radio Part RAT Supported from SW Version Configuration
GSM
21.Q4 Supported with 2-WRXD.
WCDMA
1 LTE
Supported with up to 2x2 MIMO and
NR 21.Q4
2-WRXD.
ESS
Supported with up to 4x4 MIMO and
21.Q4
4-WRXD.
LTE Supported with up to 4x4 MIMO and
2 4-WRXD.
NR
22.Q4
Supported for 2-branch carriers, with
up to 2x2 MIMO and 2-WRXD.(1)

(1) DCA is used to allocate the carrier to a specific transceiver. For details see Deterministic Carrier Allocation in Features for Radio Configurations.

about:blank 229/268
3/5/24, 9:34 AM Building Blocks

1.5.16 ABB4_2A
ABB4_2A has four RF branches and two antenna subunits. RF ports 1 and 3 have one polarization, while RF ports 2 and 4
have the opposite polarization.
Figure 407 shows ABB4_2A.
Figure 408 shows ABB4_2A-TMA1 with TMA.
Figure 409 shows ABB4_2A-TMA2 with TMA.
Figure 410 shows ABB4_2A for NR Combined Radio.

RF Branch AU Port
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

Ge12844B

Figure 407 ABB4_2A Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 2
1 polarization B
Subunit 1

3 3
1 polarization A
Antenna
4 TMA 2 4
1 polarization B
Subunit 2

Ge12845B

Figure 408 ABB4_2A-TMA1 Block Diagram with TMA

about:blank 230/268
3/5/24, 9:34 AM Building Blocks

Figure 409 ABB4_2A-TMA2 Block Diagram with TMA

RF Branch AU Port
Coverage area 1
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

Coverage area 2
3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

Ge26917A

Figure 410 ABB4_2A Block Diagram for NR Combined Radio

1.5.17 ABB4_2B
ABB4_2B has four RF branches and two antenna subunits. RF ports 1 and 3 have one polarization, while RF ports 2 and 4
have the opposite polarization.
Figure 411 shows ABB4_2B.
Figure 412 shows ABB4_2B-TMA1, with TMA.
Figure 413 shows ABB4_2B-TMA2, with TMA.
Figure 414 shows ABB4_2B-TMA3, with TMA.

about:blank 231/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

Ge12846B

Figure 411 ABB4_2B Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 3
1 polarization B
Subunit 1

3 2
1 polarization A
Antenna
4 TMA 2 4
1 polarization B
Subunit 2

Ge12847B

Figure 412 ABB4_2B-TMA1 Block Diagram, with TMA

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 3
1 polarization B
Subunit 1

3 2
1 polarization A
Antenna
TMA 2 4
4
1 polarization B
Subunit 2

Ge12848B

Figure 413 ABB4_2B-TMA2 Block Diagram, with TMA

about:blank 232/268
3/5/24, 9:34 AM Building Blocks

Figure 414 ABB4_2B-TMA3 Block Diagram, with TMA

1.5.18 ABB4_2C
ABB4_2C has four RF branches and two antenna subunits. RF ports 1 and 3 have one polarization, while RF ports 2 and 4
have the opposite polarization.
Figure 415 shows ABB4_2C.
Figure 416 shows ABB4_2C-TMA1, with TMA.
Figure 417 shows ABB4_2C-TMF1, with TMF.

RF Branch RF Branch AU Port

1 1A
1 polarization A
Antenna
2 2A Subunit 1
1 polarization B

1B
1 polarization A
Antenna
2B Subunit 2
1 polarization B

Ge14434B

Figure 415 ABB4_2C Block Diagram

about:blank 233/268
3/5/24, 9:34 AM Building Blocks

Figure 416 ABB4_2C-TMA1 Block Diagram, with TMA

RF Branch RF Branch RF Branch AU Port

1 1A 1A
1 polarization A
Antenna
2A TMF 1 2A
1 polarization B
Subunit 1

1B 1B
1 polarization A
Antenna
2 2B TMF 2 2B
1 polarization B
Subunit 2

Ge14436B

Figure 417 ABB4_2C-TMF1 Block Diagram, with TMF

Figure 418 ABB4_2C-TMA1 Block Diagram with Multi-band TMA

1.5.19 ABB4_2D for RDS

ABB4_2D is used for configuration with four Multicast Antenna Branches from two RDBs, two Multicast Antenna Branches
from each RDB.

Connection
to RDB Multicast Antenna Branch

1
1
RDB 1 2
2
1
3
RDB 2 2
4

Ge27574A

Figure 419 ABB4_2D

Table 55 ABB4_2D Connection Definition

about:blank 234/268
3/5/24, 9:34 AM Building Blocks
RDB Connection to RDB Multicast Antenna Branch
1 1
1
2 2
1 3
2
2 4

ABB4_2D can be used with RDBs for RDS according to ABBs for RDS.
Table 56 ABB4_2D Carrier Allocation
Transceivers per Radio Part and RDB RAT Supported from SW Version Configuration
21.Q4 Supported with 4-WRXD.
GSM Supported with 4-WRXD.
WCDMA 22.Q4 Supported for 2-branch carriers, with
2-WRXD, using DCA.(1)

Supported with up to 4x4 MIMO and

1 21.Q4
4-WRXD.
LTE Supported with up to 4x4 MIMO and
NR 4-WRXD.
ESS 22.Q4 Supported for 2-branch carriers, with
up to 2x2 MIMO and 2-WRXD, using
DCA.(1)
(1) DCA is used to allocate the carrier to a specific transceiver. For details see Deterministic Carrier Allocation in Features for Radio Configurations.

1.5.20 ABB4_4A
ABB4_4A has four RF branches and four antenna subunits.
Figure 420 shows ABB4_4A for NR Combined Radio.

RF Branch AU Port Coverage area 1

1 Antenna
1
Subunit 1
Coverage area 2

2 Antenna
1
Subunit 2
Coverage area 3

3 Antenna
1
Subunit 3
Coverage area 4

4 Antenna
1
Subunit 4

Ge26918A

Figure 420 ABB4_4A Block Diagram for NR Combined Radio

1.5.21 ABB6_1A

about:blank 235/268
3/5/24, 9:34 AM Building Blocks
ABB6_1A has six RF branches and one antenna subunit. RF ports 1, 3, and 5 have one polarization, while RF ports 2, 4, and
6 have the opposite polarization.
Figure 421 shows ABB6_1A.
Figure 422 shows ABB6_1A-TMA1, with TMA.

RF Branch RF Branch AU Port

1 1
1 polarization A

2 4
1 polarization B

3 2
2 polarization A
Antenna
4 3 Subunit 1
2 polarization B

5 5
3 polarization A

6 6
3 polarization B

Ge12849B

Figure 421 ABB6_1A Block Diagram

RBB RF Branch
RF Branch AU Port
1: TX A 1
A 1 polarization A

2: RX A No TMA 4
Radio 1 RXA I/O 1 polarization B

3: RX B
RXB I/O 2
2 polarization A Antenna
TMA 1 3 Subunit 1
1: TX A 2 polarization B
A
5
2: RX A
Radio 2 RXA I/O 3 polarization A

3: RX B TMA 2 6
RXB I/O 3 polarization B

Ge18942A

Figure 422 ABB6_1A-TMA1 Block Diagram, with TMA

1.5.22 ABB6_2A
ABB6_2A has six RF branches and two antenna subunits. RF ports 1, 3, and 5 have one polarization, while RF ports 2, 4,
and 6 have the opposite polarization.
Figure 423 shows ABB6_2A.
Figure 424 shows ABB6_2A-TMA1, with TMA.

about:blank 236/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 4 Subunit 1
1 polarization B

3 2
1 polarization A

4 3
1 polarization B
Antenna
5 5 Subunit 2
2 polarization A

6 6
2 polarization B

Ge12851B

Figure 423 ABB6_2A Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 4
1 polarization B
Subunit 1

3 2
1 polarization A

4 TMA 2 3
1 polarization B

5 Antenna
5 Subunit 2
2 polarization A

6 TMA 3 6
2 polarization B

Ge12852B

Figure 424 ABB6_2A-TMA1 Block Diagram, with TMA

1.5.23 ABB6_2B
ABB6_2B has six RF branches and two antenna subunits. RF ports 1, 3, and 5 have one polarization, while RF ports 2, 4,
and 6 have the opposite polarization.
Figure 425 shows ABB6_2B.
Figure 426 shows ABB6_2B-TMA1, with TMA.

about:blank 237/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A

2 4
1 polarization B
Antenna
3 2 Subunit 1
2 polarization A

4 3
2 polarization B

5 5
1 polarization A
Antenna
6 6 Subunit 2
1 polarization B

Ge12853B

Figure 425 ABB6_2B Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 4
1 polarization B
Antenna
3 2 Subunit 1
2 polarization A

4 TMA 2 3
2 polarization B

5
5
1 polarization A
Antenna
6 TMA 3 6
1 polarization B
Subunit 2

Ge12854B

Figure 426 ABB6_2B-TMA1 Block Diagram, with TMA

1.5.24 ABB6_2C
ABB6_2C has six RF branches and two antenna subunits. RF ports 1, 3, and 5 have one polarization, while RF ports 2, 4,
and 6 have the opposite polarization.

about:blank 238/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A

2
1 polarization B
Antenna
3 Subunit 1
2 polarization A

4
2 polarization B

5
1 polarization A
Antenna
6 Subunit 2
1 polarization B

Ge17274B

Figure 427 ABB6_2C Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 2
1 polarization B
Antenna
3 3 Subunit 1
2 polarization A
4 TMA 2 4
2 polarization B

5
5 1 polarization A
Antenna
6 TMA 3 6
1 polarization B
Subunit 2

Ge17275B

Figure 428 ABB6_2C-TMA1 Block Diagram, with TMA

1.5.25 ABB6_3A
ABB6_3A has six RF branches and three antenna subunits.
Figure 429 shows ABB6_3A.
Figure 430 shows ABB6_3A-TMA1, with TMA.

about:blank 239/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 4 Subunit 1
1 polarization B

3 2
1 polarization A
Antenna
4 3 Subunit 2
1 polarization B

5 5
1 polarization A
Antenna
6 6 Subunit 3
1 polarization B

Ge12855B

Figure 429 ABB6_3A Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 4
1 polarization B
Subunit 1

3 2
1 polarization A
Antenna
4 TMA 2 3
1 polarization B
Subunit 2

5
5
1 polarization A
Antenna
6 TMA 3 6
1 polarization B
Subunit 3

Ge12856B

Figure 430 ABB6_3A-TMA1 Block Diagram, with TMA

1.5.26 ABB6_3B
ABB6_3B has six RF branches and three antenna subunits.

about:blank 240/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1A
1 polarization A
Antenna
2 2A Subunit 1
1 polarization B

1B
1 polarization A
Antenna
2B Subunit 2
1 polarization B

1C
1 polarization A
Antenna
2C Subunit 3
1 polarization B

Ge18957A

Figure 431 ABB6_3B Block Diagram

Figure 432 shows ABB6_3B-TMF1, with TMF.

RF Branch RF Branch RF Branch AU Port

1 1A 1A
1 polarization A
Antenna
2A TMF 1 2A
1 polarization B
Subunit 1

1B 1B
1 polarization A
Antenna
2B TMF 2 2B
1 polarization B
Subunit 2

1C 1C
1 polarization A
Antenna
2 2C TMF 3 2C
1 polarization B
Subunit 3

Ge14437B

Figure 432 ABB6_3B-TMF1 Block Diagram with TMF

about:blank 241/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch RF Branch AU Port

1 1A 1A
1 polarization A
Antenna
2 2A TMA 1 2A
1 polarization B
Subunit 1

1B 1B
1 polarization A
Antenna
2B TMA 2 2B
1 polarization B
Subunit 2

1C 1C
1 polarization A
Antenna
2C TMA 3 2C
1 polarization B
Subunit 3

Ge18959A

Figure 433 ABB6_3B-TMA1 Block Diagram with TMA

RF Branch RF Branch RF Branch AU Port

1 1 1A
1 polarization A
Antenna
2 TMA 1 2 2A
1 polarization B
Subunit 1

1 polarization A
Antenna
2B Subunit 2
1 polarization B

1C
1 polarization A
Antenna
2C Subunit 3
1 polarization B

Ge18958A

Figure 434 ABB6_3B-TMA1 Block Diagram with Multi-band TMA

1.5.27 ABB6_3C
ABB6_3C has six RF branches and three antenna subunits.

about:blank 242/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

5
1 polarization A
Antenna
6 Subunit 3
1 polarization B

Ge17276B

Figure 435 ABB6_3C Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 2
1 polarization B
Subunit 1

3 3
1 polarization A
Antenna
4 TMA 2 4
1 polarization B
Subunit 2

5 5
1 polarization A
Antenna
6 TMA 3 6
1 polarization B
Subunit 3

Ge17277B

Figure 436 ABB6_3C-TMA1 Block Diagram, with TMA

about:blank 243/268
3/5/24, 9:34 AM Building Blocks

Figure 437 ABB6_3C-TMA2 Block Diagram, with TMA

1.5.28 ABB8_1A
ABB8_1A has eigth RF branches and one antenna subunit.
Figure 438 shows ABB8_1A.

RF Branch AU Port
1
1 polarization A

2
1 polarization B

3
2 polarization A

4
2 polarization B
Antenna
5 Subunit 1
3 polarization A

6
3 polarization B

7
4 polarization A

8
4 polarization B

Ge12981B

Figure 438 ABB8_1A Block Diagram

1.5.29 ABB8_1C

ABB8_1C is used for eight RF Branches and one Antenna subunit.

about:blank 244/268
3/5/24, 9:34 AM Building Blocks
To optimize MIMO performance, the antenna polarization for each RF Branch, and the order in which the RF Branches are
defined in software, are important.
ABB8_1C supports 4TX/8RX carriers, 8TX/8RX carriers, and two groups of 4TX/4RX carriers for different frequency ranges
in the same or different bands.

RF Branch AU Port
1
1 polarization A

2
1 polarization B

3
2 polarization A

4
2 polarization B
Antenna
5 Subunit 1
3 polarization A

6
3 polarization B

7
4 polarization A

8
4 polarization B

Ge28460A

Figure 439 ABB8_1C

1.5.30 ABB8_1D for RDS

ABB8_1D is used for configuration with eight Multicast Antenna Branches from one RDB.

Connection
to RDB Multicast Antenna Branch

1
1
2
2
3
3
4
4
RDB
5
5
6
6
7
7
8
8

Ge27575A

Figure 440 ABB8_1D

Table 57 ABB8_1D Connection Definition

about:blank 245/268
3/5/24, 9:34 AM Building Blocks
RDB Connection to RDB Multicast Antenna Branch
1 1
2 2
3 3
4 4
1
5 5
6 6
7 7
8 8

ABB8_1D can be used with RDBs for RDS according to ABBs for RDS.
Table 58 ABB8_1D Carrier Allocation
Transceivers per Radio Part and RDB RAT Supported from SW Version Configuration
GSM
21.Q4 Supported with 2-WRXD.
WCDMA
1 LTE
Supported with up to 2x2 MIMO and
NR 21.Q4
2-WRXD.
ESS
Supported with up to 4x4 MIMO and
21.Q4
4-WRXD.
Supported with up to 4x4 MIMO and
LTE 4-WRXD.
2
NR
22.Q4 Supported for 2-branch carriers, with
up to 2x2 MIMO and 2-WRXD, using
DCA.(1)

Supported for 2-branch carriers, with

up to 2x2 MIMO and 2-WRXD, using
LTE DCA(1).
2 + 2(2) 22.Q4
NR Supported for 4-branch carriers, with
up to 4x4 MIMO and 4-WRXD, using
DCA.(3)

(1) DCA is used to allocate the carrier to a specific transceiver. For details see Deterministic Carrier Allocation in Features for Radio Configurations.
(2) Two radio parts for the same RDB support the same frequency band. For “dual-band on same band”, for example, Dot 4474 B78K B78K.
(3) DCA is used to allocate the carrier to both transceivers in the same radio part. For details see Deterministic Carrier Allocation in Features for Radio
Configurations.

1.5.31 ABB8_2C
ABB8_2C has four RF branches and one antenna subunit.
Figure 441 shows ABB8_2C.
Figure 442 shows ABB8_2C with TMA.
Figure 443 shows ABB8_2C for NR Combined Radio.

about:blank 246/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A

2
1 polarization B
Antenna
3 Subunit 1
2 polarization A

4
2 polarization B

RF Branch AU Port
5
1 polarization A

6
1 polarization B
Antenna
7
2 polarization A

8
2 polarization B

Ge19731

Figure 441 ABB8_2C Block Diagram

about:blank 247/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 2
1 polarization B
Antenna
3 3 Subunit 1
2 polarization A

4 TMA 2 4
2 polarization B

RF Branch RF Branch AU Port

5 5
1 polarization A

6 TMA 3 6
1 polarization B
Antenna
7 7 Subunit 2
2 polarization A

8 TMA 4 8
2 polarization B

Ge19732

Figure 442 ABB8_2C Block Diagram with TMA

about:blank 248/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port

1
1 polarization A

2
1 polarization B
Antenna Coverage area 1
3 Subunit 1
2 polarization A

4
2 polarization B

Coverage area 2
5
1 polarization A

6
1 polarization B
Antenna
7 Subunit 2
2 polarization A

8
2 polarization B

Ge26919A

Figure 443 ABB8_2C Block Diagram for NR Combined Radio

1.5.32 ABB8_2D for RDS

RDB8_2D is used for a configuration with four Multicast Antenna Branches each from two RDBs. The ABB supports NR
Combined Radio.
When used with NR Combined Radio, each RDB covers separate areas with a small overlap. For more information, see NR
Combined Radio Configurations. The Octal Antenna Downlink Performance feature package is used to create two coverage
areas within the sector and possibility to move between the two coverage areas using the same cell.

Connection
to RDB Multicast Antenna Branch

1
1
2
2
RDB 1
3
3
4
4
1
5
2
6
RDB 2
3
7
4
8

Ge27576A

about:blank 249/268
3/5/24, 9:34 AM Building Blocks

Figure 444 ABB8_2D

Connection
to RDB Multicast Antenna Branch

1
1
2 Coverage area 1
2
RDB 1
3
3
4
4

1
5
2 Coverage area 2
6
RDB 2
3
7
4
8

Ge27579A

Figure 445 ABB8_2D for NR Combined Radio

Table 59 ABB8_2D Connection Definition

RDB Connection to RDB Multicast Antenna Branch
1 1
2 2
1
3 3
4 4
1 5
2 6
2
3 7
4 8

For carrier allocation with NR Combined Radio, see Table 61.

ABB8_2D can be used with RDBs for RDS according to ABBs for RDS.
Table 60 ABB8_2D Carrier Allocation
Transceivers per Radio Part and RDB RAT Supported from SW Version Configuration
GSM
21.Q4 Supported with 2-WRXD.
WCDMA
1
in one RDB only LTE
Supported with up to 2x2 MIMO and
NR 21.Q4
2-WRXD.
ESS
GSM
21.Q4 Supported with 4-WRXD.
WCDMA
Supported with up to 4x4 MIMO and
21.Q4
1 4-WRXD.
in each RDB LTE Supported with up to 4x4 MIMO and
NR 4-WRXD.
22.Q4
Supported for 2-branch carriers, with
2-WRXD, using DCA.(1)

2 LTE Supported with up to 4x4 MIMO and

21.Q4
in one RDB only NR 4-WRXD.
2 LTE 22.Q4 Supported for 2-branch carriers, with
in each RDB NR up to 2x2 MIMO and 2-WRXD, using
DCA.(1)

about:blank 250/268
3/5/24, 9:34 AM Building Blocks
Transceivers per Radio Part and RDB RAT Supported from SW Version Configuration
Supported for 4-branch carriers with
up to 4x4 MIMO and 4-WRXD, using
DCA.(2)

(1) DCA is used to allocate the carrier to a specific transceiver. For details see Deterministic Carrier Allocation in Features for Radio Configurations.
(2) DCA is used to allocate the carrier to both transceivers in the same radio part. For details see Deterministic Carrier Allocation in Features for Radio
Configurations.

Table 61 ABB8_2D Carrier Allocation for NR Combined Radio

Transceiver per Radio Part and RDB RAT Supported from SW version Configuration
For NR Combined Radio:
Supported with up to 4x4 MIMO and
2
NR 22.Q4 4-WRXD when configured as an
in each RDB
8TX/8RX carrier(3) but with one RDB
per coverage area.

(3) Configured as 8TX/8RX with the features TM9 8x4 Octal Antenna Downlink Performance Package and Octal Antenna Uplink Performance Package.

1.5.33 ABB8_3A
ABB8_3A has eight RF branches and three antenna subunits.

RF Branch AU Port
1
1 polarization A

2
1 polarization B
Antenna
3 Subunit 1
2 polarization A

4
2 polarization B

5
1 polarization A
Antenna
6 Subunit 2
1 polarization B

7
1 polarization A
Antenna
8 Subunit 3
1 polarization B

Ge17279B

Figure 446 ABB8_3A Block Diagram

about:blank 251/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A

2 TMA 1 2
1 polarization B
Antenna
3 3 Subunit 1
2 polarization A

4 TMA 2 4
2 polarization B

5 5
1 polarization A
Antenna
6 TMA 3 6 Subunit 2
1 polarization B

7 7
1 polarization A
Antenna
8 TMA 4 8 Subunit 3
1 polarization B

Ge17280B

Figure 447 ABB8_3A-TMA1 Block Diagram, with TMA

1.5.34 ABB8_3B
ABB8_3B has eight RF branches and three antenna subunits.

about:blank 252/268
3/5/24, 9:34 AM Building Blocks

RF Branch
AU Port
1

1 polarization A
Antenna
2 Subunit 1
1 polarization B

3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

5
1 polarization A

6
1 polarization B
Antenna
7 Subunit 3
2 polarization A

8
2 polarization B

Ge19733

Figure 448 ABB8_3B Block Diagram

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 2 Subunit 1
1 polarization B

3 3
1 polarization A
Antenna
4 TMA 2 4 Subunit 2
1 polarization B

5 5
1 polarization A

6 TMA 3 6
1 polarization B
Antenna
7 7 Subunit 3
2 polarization A

8 TMA 4 8
2 polarization B

Ge19734

Figure 449 ABB8_3B Block Diagram with TMA

about:blank 253/268
3/5/24, 9:34 AM Building Blocks

1.5.35 ABB8_4A
ABB8_4A has eight RF branches and four antenna subunits.
Figure 450 shows ABB8_4A.
Figure 451 shows ABB8_4A with TMA.
Figure 452 shows ABB8_4A for NR Combined Radio.

RF Branch AU Port
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

5
1 polarization A
Antenna
6 Subunit 3
1 polarization B

7
1 polarization A
Antenna
8 Subunit 4
1 polarization B

Ge17281C

Figure 450 ABB8_4A Block Diagram

about:blank 254/268
3/5/24, 9:34 AM Building Blocks

RF Branch RF Branch AU Port

1 1
1 polarization A
Antenna
2 TMA 1 2
1 polarization B
Subunit 1

3 3
1 polarization A
Antenna
4 TMA 2 4
1 polarization B
Subunit 2

5 5
1 polarization A
Antenna
6 TMA 3 6
1 polarization B
Subunit 3

7 7
1 polarization A
Antenna
8 TMA 4 8
1 polarization B
Subunit 4

Ge17282C

Figure 451 ABB8_4A-TMA1 Block Diagram with TMA

about:blank 255/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
Coverage area 1
1
1 polarization A
Antenna
2 Subunit 1
1 polarization B

Coverage area 2
3
1 polarization A
Antenna
4 Subunit 2
1 polarization B

Coverage area 3
5
1 polarization A
Antenna
6 Subunit 3
1 polarization B

Coverage area 4
7
1 polarization A
Antenna
8 Subunit 4
1 polarization B

Ge26920A

Figure 452 ABB8_4A Block Diagram for NR Combined Radio

1.5.36 ABB8_1B
ABB8_1B has eigth RF branches and two antenna subunits.
Figure 453 shows ABB8_1B.

about:blank 256/268
3/5/24, 9:34 AM Building Blocks

RF Branch AU Port
1
1 polarization A

2
1 polarization B

3
2 polarization A

4
2 polarization B
Antenna
5 Subunit 1
3 polarization A

6
3 polarization B

7
4 polarization A

8
4 polarization B

Ge12982B

Figure 453 ABB8_1B Block Diagram

1.5.37 ABB12_2A for RDS

ABB12_2A is used for configuration with eight Multicast Antenna Branches from one RDB and four Multicast Antenna
Branches from another RDB.

Connection
to RDB Multicast Antenna Branch

1
1
2
2
3
3
4
4
RDB 1
5
5
6
6
7
7
8
8
1
9
2
10
RDB 2
3
11
4
12

Ge27577A

Figure 454 ABB12_2A with 8-branch + 4-branch Dots

about:blank 257/268
3/5/24, 9:34 AM Building Blocks

Connection
to RDB Multicast Antenna Branch

1
1
2
2
RDB 1
3
3
4
4
1
5
2
6
3
7
4
8
RDB 2
5
9
6
10
7
11
8
12

Ge27397A

Figure 455 ABB12_2A with 4-branch + 8-branch Dots

ABB12_2A is used with one 8-branch Dot and one 4-branch Dot. Both 8-branch Dot first and 4-branch Dot first is
supported.

Table 62 ABB12_2A Connection Definition for 8-branch + 4-branch Dots

RDB Connection to RDB Multicast Antenna Branch
1 1
2 2
3 3
4 4
1
5 5
6 6
7 7
8 8
1 9
2 10
2
3 11
4 12

Table 63 ABB12_2A Connection Definition for 4-branch + 8-branch Dots

RDB Connection to RDB Multicast Antenna Branch
1 1
2 2
1
3 3
4 4
2 1 5
2 6
3 7
4 8

about:blank 258/268
3/5/24, 9:34 AM Building Blocks
RDB Connection to RDB Multicast Antenna Branch
5 9
6 10
7 11
8 12

ABB12_2A can be used with RDBs for RDS according to ABBs for RDS.
Table 64 ABB12_2A Carrier Allocation
Transceivers per Radio Part and RDB RAT Supported from SW Version Configuration
GSM
21.Q4 Supported with 2-WRXD.
WCDMA
1
in one RDB only LTE
Supported with up to 2x2 MIMO and
NR 21.Q4
2-WRXD.
ESS
GSM
21.Q4 Supported with 4-WRXD.
WCDMA
Supported with up to 4x4 MIMO and
21.Q4
4-WRXD.
1
Supported with up to 4x4 MIMO and
in each RDB LTE 4-WRXD.
NR
22.Q4 Supported for 2 branch carriers, with
up to 2x2 MIMO and 2-WRXD, using
DCA.(1)

2 LTE Supported with up to 4x4 MIMO and

21.Q4
in one RDB only NR 4-WRXD.
Supported for 2 branch carriers, with
up to 2x2 MIMO and 2-WRXD, using
2 LTE DCA.(1)
22.Q4
in each RDB NR Supported for 4 branch carriers with
up to 4x4 MIMO and 4-WRXD, using
DCA.(2)

(1) DCA is used to allocate the carrier to a specific transceiver. For details see Deterministic Carrier Allocation in Features for Radio Configurations.
(2) DCA is used to allocate the carrier to both transceivers in the same radio part. For details see Deterministic Carrier Allocation in Features for Radio
Configurations.

1.5.38 ABB16_2A for RDS

ABB16_2A is used for configuration with eight Multicast Antenna Branches each from two RDBs.

about:blank 259/268
3/5/24, 9:34 AM Building Blocks

Connection
to RDB Multicast Antenna Branch

1
1
2
2
3
3
4
4
RDB 1
5
5
6
6
7
7
8
8
1
9
2
10
3
11
4
12
RDB 2 5
13
6
14
7
15
8
16

Ge27578A

Figure 456 ABB16_2A

Table 65 ABB16_2A Connection Definition

RDB Connection to RDB Multicast Antenna Branch
1 1
2 2
3 3
4 4
1
5 5
6 6
7 7
8 8
1 9
2 10
3 11
4 12
2
5 13
6 14
7 15
8 16

ABB16_2A can be used with RDBs for RDS according to ABBs for RDS.
Table 66 ABB16_2A Carrier Allocation

about:blank 260/268
3/5/24, 9:34 AM Building Blocks
Transceivers per Radio Part and RDB RAT Supported from SW Version Configuration
GSM
21.Q4 Supported with 2-WRXD.
WCDMA
1
in one RDB only LTE
Supported with up to 2x2 MIMO and
NR 21.Q4
2-WRXD.
ESS
GSM
21.Q4 Supported with 4-WRXD.
WCDMA
Supported with up to 4x4 MIMO and
21.Q4
4-WRXD.
1
Supported with up to 4x4 MIMO and
in each RDB LTE 4-WRXD.
NR
22.Q4 Supported for 2-branch carriers, with
up to 2x2 MIMO and 2-WRXD, using
DCA.(1)

2 LTE Supported with up to 4x4 MIMO and

21.Q4
in one RDB only NR 4-WRXD.
Supported for 2-branch carriers, with
up to 2x2 MIMO and 2-WRXD, using
2 LTE DCA.(1)
22.Q4
in each RDB NR Supported for 4-branch carriers with
up to 4x4 MIMO and 4-WRXD, using
DCA.(2)

(1) DCA is used to allocate the carrier to a specific transceiver. For details see Deterministic Carrier Allocation in Features for Radio Configurations.
(2) DCA is used to allocate the carrier to both transceivers in the same radio part. For details see Deterministic Carrier Allocation in Features for Radio
Configurations.

1.5.39 ABB16_4A for RDS

ABB16_4A is used for configuration with four Multicast Antenna Branches each from four RDBs.

Connection
to RDB
1
1 Coverage area 1
...
RDB 1 ...
4
4

1
5 Coverage area 2
...
RDB 2 ...
4
8

1
9 Coverage area 3
...
RDB 3 ...
4
12

1
13 Coverage area 4
...
RDB 4 ...
4
16

Ge28349A

Figure 457 ABB16_4A

Table 67 ABB16_4A Connection Definition

about:blank 261/268
3/5/24, 9:34 AM Building Blocks

RDB Connection to RDB Multicast Antenna Branch

1 1
2 2
1
3 3
4 4
1 5
2 6
2
3 7
4 8
1 9
2 10
3
3 11
4 12
1 13
2 14
4
3 15
4 16
ABB16_4A can be used with RDBs for RDS according to ABBs for RDS.
Table 68 ABB16_4A Carrier Allocation for NR Combined Radio

Transceiver per Radio RAT Supported from Configuration

Part and RDB SW Version
For NR Combined Radio:
One in each RDB NR 22.Q4 Supported effectively with up to 2x2 MIMO and 2-way RX diversity when
configured as an 8TX/8RX carrier(1) but with one RDB per coverage area.
(1) Configured as 8TX/8RX with the features TM8 8x2 Octal Antenna Downlink Performance Package and Octal Antenna Uplink Performance Package.

1.5.40 ABB32_4A for RDS

ABB32_4A is used for configuration with eight Multicast Antenna Branches each from four RDBs.

about:blank 262/268
3/5/24, 9:34 AM Building Blocks

Connection
to RDB
1
1 Coverage area 1
...
RDB 1 ...
8
8

1
9 Coverage area 2
...
RDB 2 ...
8
16

1
17 Coverage area 3
...
RDB 3 ...
8
24

1
25 Coverage area 4
...
RDB 4 ...
8
32

Ge28350A

Figure 458 ABB32_4A

Table 69 ABB32_4A Connection Definition

RDB Connection to RDB Multicast antenna Branch

1 1
2 2
3 3
4 4
1
5 5
6 6
7 7
8 8
1 9
2 10
3 11
4 12
2
5 13
6 14
7 15
8 16
3 1 17
2 18
3 19
4 20
5 21
6 22
7 23

about:blank 263/268
3/5/24, 9:34 AM Building Blocks

RDB Connection to RDB Multicast antenna Branch

8 24
1 25
2 26
3 27
4 28
4
5 29
6 30
7 31
8 32
ABB32_4A can be used with RDBs for RDS according to ABBs for RDS
Transceiver per Radio RAT Supported from Configuration
Part and RDB SW Version
For NR Combined Radio where each cell covers all four coverage areas:
(1) NR 22.Q4 Supported effectively with up to 2x2 MIMO and 2-way RX diversity when
One in each RDB
configured as an 8TX/8RX carrier(2) but with one RDB per coverage area.
For NR Combined Radio where each cell covers only two coverage areas:
Two in each RDS NR 22.Q4 Supported effectively with up to 4x4 MIMO and 4-way RX diversity when
configured as an 8TX/8RX carrier(2) but with one RDB per coverage area.
(1) Use one transceiver per radio part in each RDB using DCA also for radio parts with 2 transceivers.
(2) Configured as 8TX/8RX with the features TM8 8x2 Octal Antenna Downlink Performance Package and Octal Antenna Uplink Performance Package.

1.6 Building Blocks Used in the Equipment Configuration Tool

This section defines identity for managed objects used when creating a configuration with the Equipment Configuration
Tool (ECT). For more information on ECT refer to Manage Equipment Configuration Tool in the Baseband Radio Node
library.

Figure 459 shows basic object identity for radio and antenna equipment.

Figure 460 shows object identity for radio and antenna equipment with multiple radio units, TMAs, and antennas.

Figure 461 shows object identity for radio and antenna equipment where TMAs and antennas are shared between ABBs.

In the expression Sx-n, as in "S1-1", x represents the sector number covered by ABB. When manually creating configuration
files the recommendation is to follow this convention, though there is no enforcement to do so.

about:blank 264/268
3/5/24, 9:34 AM Building Blocks

RBB ABB
RF Branch
1

Radio 1 TMA 1 Antenna Subunit 1

2

Hardware view of configuration

Id for Managed Objects in SW

RfBranch AntennaNearUnit ”1" AntennaUnit ”1"

Field TmaSubunit
”S1-1"
Replaceable ”S1-1” Antenna
Unit Subunit
TmaSubunit ”S1-1"
”Radio_S1-1" ”S1-2"
”S1-2”

RBB for Sector 1 ABB for Sector 1

Ge13097B

Figure 459 Object Identity for Radio and Antenna Equipment

about:blank 265/268
3/5/24, 9:34 AM Building Blocks

RBB ABB
RF Branch
1

Radio 1 TMA 1 Antenna Subunit 1

2

Radio 2 TMA 2 Antenna Subunit 2

4

Hardware view of configuration

Id for Managed Objects in SW

RfBranch AntennaNearUnit ”1" AntennaUnit ”1"

Field TmaSubunit
”S1-1"
Replaceable ”S1-1” Antenna
Unit Subunit
TmaSubunit ”S1-1"
”Radio_S1-1" ”S1-2"
”S1-2”

AntennaNearUnit ”2" AntennaUnit ”2"

Field TmaSubunit
”S1-3"
Replaceable ”S1-1” Antenna
Unit Subunit
TmaSubunit ”S1-1"
”Radio_S1-2" ”S1-4"
”S1-2”

RBB for Sector 1 ABB for Sector 1

Ge13098B

Figure 460 Object Identity for Radio and Antenna Equipment with Multiple Radio Units, TMAs, and Antennas

about:blank 266/268
3/5/24, 9:34 AM Building Blocks

RBB Band A ABB Band A

RF Branch
1

Radio 1 TMA 1 Antenna Subunit 1

2

RBB Band B ABB Band B

RF Branch
1

Radio 1 TMA 1 Antenna Subunit 1

2

TMA dual-band Antenna dual-band

Hardware view of configuration

Id for Managed Objects in SW

RBB for Sector 1 ABB for Sector 1 (Band A)

(Band A) RfBranch
AntennaNearUnit ”1" AntennaUnit ”1"

Field TmaSubunit
”S1-1"
Replaceable ”S1-1” Antenna
Unit Subunit
TmaSubunit ”S1-1"
”Radio_S1-1" ”S1-2"
”S1-2”

Field TmaSubunit
”S2-1"
Replaceable ”S2-1” Antenna
Unit Subunit
TmaSubunit ”S2-1"
”Radio_S2-1" ”S2-2"
”S2-2”

RBB for Sector 2

(Band B) ABB for Sector 2 (Band B)
Ge13099B

Figure 461 Object Identity for Radio and Antenna Equipment where TMAs and Antennas are Shared Between ABBs

Legal | © Ericsson AB 2020–2024

about:blank 267/268
3/5/24, 9:34 AM Building Blocks

Copyright © Ericsson AB 2020–2024. All rights reserved. No part of this document may be reproduced in any form without
the written permission of the copyright owner.

Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology,
design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the
use of this document.

Trademarks All trademarks mentioned herein are the property of their respective owners. These are shown in the document
Trademark Information.

about:blank 268/268