EUL Multi-Carrier

Contents
1 Introduction
1.1 Basic Characteristics
1.2 Benefits

2 Feature Operational Description

2.1 Network Requirements

3 Parameters
3.1 Introduced Parameters
3.2 Affected Parameters

4 Network Impact
4.1 Subscriber Capacity
4.2 Network Performance
4.3 Hardware
4.4 Inter-Node Interface
4.5 Other Network Elements

5 Associated Features and Affected Functions

5.1 Prerequisite Features
5.2 Affected Features
5.3 Related Features
5.4 Affected System Functions

6 Performance
6.1 KPIs
6.2 Counters
6.3 Events

7 Operation and Maintenance

7.1 Activating the Feature
7.2 Deactivating the Feature
7.3 Engineering Guidelines

Reference List

1 Introduction

This document describes the EUL Multi-Carrier feature, its main benefits and impacts in
the WCDMA RAN.

The EUL Multi-Carrier feature corresponds to DC-HSUPA in the 3GPP Rel-9 standard.

The feature introduces support for User Equipment (UE) to use Enhanced Uplink (EUL) on
two adjacent carriers. This means that uplink Enhanced Dedicated Channel (E-DCH)
transmission from the given UE is supported simultaneously on two adjacent carriers.
This is therefore, the uplink equivalence to the HSDPA Multi-Carrier support in downlink.

1.1 Basic Characteristics

This section describes the basic characteristics of the feature.

Feature FAJ 121 1491: EUL Multi-Carrier

identity:

Release: Introduced in W14.1

Dependencies

This feature requires the following RAN features to be active:

 FAJ 121 1516: Improved Layer 2.

 FAJ 121 1441: HSDPA Multi-Carrier.
 FAJ 121 1320/FAJ 121 1481: SRB on HSDPA/F-DPCH.
 FAJ 121 1317: EUL 2-ms TTI.

To achieve a maximum UE bit rate in uplink, the following Core Network feature is
recommended to be activated:

 FAJ 121 1808/1: Enhanced Uplink Sup Exp2, 8-11 Mbps. For more
information about this feature, see Reference [1] and Reference [2].

For affected features, see Section 5.2.

1.2 Benefits
This section describes the benefits of this feature.

EUL Multi-Carrier enables UE compatible with 3GPP Rel-9 DC-HSUPA to operate on two
uplink carriers simultaneously. This brings the following benefits:

 Up to 100% higher L1 peak data rate.

 Up to 100% higher average RLC throughput.
 Shorter transmission time.
 Reduced risk of low bit rate.
 Decreased web download time.
 Lower UE transmission power.
 Increased uplink resource utilization efficiency.

The feature enables increased carrier use in uplink because of independent scheduling on
two carriers.

2 Feature Operational Description

This section describes the EUL Multi-Carrier feature in more detail, including network
configuration requirements and operation flows.

The EUL Multi-Carrier feature gives the UE possibility to send user data on EUL on two
Uplink (UL) adjacent Cell Carriers. The two carriers must be in the same sector and band.
In addition, the two carriers must also be handled by the same Baseband Pool (BBP).

The two E-DCH cells involved in the EUL Multi-Carrier connection of the given UE are
referred to as the primary serving E-DCH cell and the secondary serving E-DCH cell. For
another UE in the same sector the roles can be reversed.

EUL transmission in the UL and Downlink (DL), for each of the cell carriers, works with
the same set of EUL UL and DL physical channels transmitted independently for each
carrier. However, HS-DPCCH is only transmitted on the primary carrier according to
design base. Moreover SRB data is only transmitted on the primary carrier.

Secondary Carrier Activation

The secondary uplink carrier can be activated or deactivated for an EUL Multi-Carrier UE.
The UE has the possibility to transmit on the secondary uplink carrier only when it is
activated. The UE receives information about the activation or deactivation through
signaling on HS-SCCH.

The secondary uplink carrier for an EUL Multi-Carrier UE is by default in deactivated

state. The serving RBS decides if the secondary uplink carrier has to be activated or
deactivated. Activation can be done to maximize UE throughput in uplink. Deactivation
can be done because of inactivity in uplink. It can also be done to reduce UE output
power, to minimize uplink interference in a cell or because of resource limitations.

The inactivity in uplink is evaluated periodically. An inactivity timer is started when a user
that is set up as EUL Multi-Carrier, with secondary uplink carrier activated, becomes
inactive on both the primary and secondary serving radio links. If the user remains
inactive at the timer expiry, the UL secondary carrier is deactivated. The inactivity timer
is defined by parameter eulMcInactivityTime.

Supported RAB Combinations

The EUL Multi-Carrier is only supported for N × PS Interactive RAB combinations (N = 1,

2, 3) on EUL/HS with EUL 2ms TTI. Combinations with, for example, CS Speech or PS
Streaming are therefore not supported.

Reconfiguration to or from EUL Multi-Carrier

The EUL Multi-Carrier configuration can be retained in the following cases:

 RAB establishment or RAB release: if the target RAB combination supports

the EUL Multi-Carrier.
 Serving E-DCH/HS-DSCH cell change: if the target cell supports the EUL
Multi-Carrier.
 Soft and Softer handover: if the target cells support the EUL Multi-Carrier.

A reconfiguration from EUL Multi-Carrier to non-EUL Multi-Carrier is performed in the

following cases:
  RAB establishment or RAB release: if the target RAB combination does not
support the EUL Multi-Carrier.
 Channel switch: to URA_PCH or CELL_FACH.
 Soft and Softer handover: if the target primary or it's corresponding
secondary cell does not support EUL Multi-Carrier.
 At IFHO.
 If Iur handover is performed.
 When entering Compressed Mode.

A reconfiguration from non-EUL Multi-Carrier to EUL Multi-Carrier can be performed in

the following cases:

 RAB establishment or RAB release: if the target RAB combination supports

the EUL Multi-Carrier.
 Channel switch: from URA_PCH, CELL_FACH, DCH/DCH or DCH/HS to
EUL/HS.

Note:
No throughput-based upswitch or downswitch is available for triggering a
reconfiguration between EUL single carrier and EUL Multi-Carrier.

For non-EUL Multi-Carrier connections UE operation is not affected by the

introduction of this feature.

EUL Multi-Carrier is not supported:

 Over Iur.
 With Compressed Mode (CM).
 On RNC 3810.
 In combination with CS speech and PS streaming.

2.1 Network Requirements

The following must be fulfilled at feature activation:

 The license key for FAJ 121 1491, EUL Multi-Carrier, must be
installed in the RBSs before feature activation.
 FAJ 121 1516: Improved Layer 2 is activated.
 FAJ 121 1441: HSDPA Multi-Carrier is activated.
 FAJ 121 1320: SRB on HSDPA is activated.
 FAJ 121 1481: F-DPCH is activated.
 FAJ 121 1317: EUL 2-ms TTI is activated.
 Two carriers used for EUL Multi-Carrier connection belong to the
same BBP.

3 Parameters

This section describes parameters introduced by the EUL Multi-Carrier

feature and parameters affected by activating the feature.

3.1 Introduced Parameters

 Table 1 describes the parameters introduced by the feature.

Table 1 Introduced Parameters

Parameter Description
RNC Parameters
MultiCarrier::eulMultiCarrierSupport Indicates if all conditions to support EUL Multi-Carrier
connections in the RBS are met for this cell.
Handover::hsIflsPrio.eulMc Configures the priority order in which cell and UE
capabilities are evaluated by IFLS.
UtranCell::eulMcServingCellUsersAdmTti2 Operator parameter configuring admission threshold for
the number of EUL Multi-Carrier users having this cell
as serving cell on primary carrier. Applicable at RAB
establishment and at reconfiguration to EUL Multi-
Carrier. For EUL/HS Cell Change, this parameter is
applicable only if
RncFunction::eulUsersAdmEulHsCcEnabled is set to
TRUE.
UeMeasControl::reportingRange1aOffsetSecondary System constant for the reporting range for the RRC
secondary event 1a, defining an offset to be added to
the reporting range for the (primary) event 1a.
Reporting range for secondary event 1a =
reportingRange1a + reportingRange1aOffsetSecondary.
Handover::eulMcSohoSupp The parameter indicating if the RNC supports soft and
softer handover for UE connections using EUL Multi-
Carrier. When set to FALSE, a reconfiguration to EUL
single carrier takes place before handover if the UE is
using EUL Multi-Carrier.
RBS Parameters
NodeBFunction::licenseStateEulMc License state indicating if the license is ENABLED or
DISABLED. That is, if a valid license key for the feature
is installed.
RbsLocalCell::featureStateEulMc Feature state for the licensed feature EUL Multi-Carrier,
indicating if the feature is ACTIVATED or DEACTIVATED
for this cell.
RbsLocalCell::eulMcActivationDelayTime When an activation of a secondary UL carrier for an EUL
Multi-Carrier user is triggered by an initial EUL Multi-
Carrier setup or reconfiguration to EUL Multi-Carrier,
the execution of the activation is delayed by
eulMcActivationDelayTime. The purpose of the delay
parameter is to give the RNC time to make secondary
carrier measurements before the execution of the
secondary UL carrier activation in the serving RBS. The
delay is applicable for all EUL Multi-Carrier users having
their primary serving E-DCH cell in this cell.
RbsLocalCell::eulMcCapability Indicates if the cell can act as a serving cell for an EUL
Multi-Carrier connection.

3.2 Affected Parameters

Table 2 describes the parameters affected by the feature.

Table 2 Affected Parameters

Parameter
RNC Parameters
Rcs::hsDschRcLostT
UeMeasControl::reportingRange1a
UtranCell::reportingRange1a
Description
Also controls the RCS timer for supervision of uplink synch of RLS
containing the secondary serving E-DCH radio link.
These parameters are also used by UE functions for intra-frequency
measurement reporting (in CELL_DCH) on secondary frequency.
For more details check reportingRange1aOffsetSecondary.
RBS Parameters
Carrier::hsdpaMcInactivityTimer
The DL secondary serving HS-DSCH cell cannot be deactivated if a
corresponding UL secondary cell carrier exists and is activated. If the
UL secondary cell carrier is activated and the
hsdpaMcInactivityTimer expires, the deactivation of the DL
secondary serving HS-DSCH cell must wait until the UL secondary cell
carrier is deactivated.

4 Network Impact

This section describes how the EUL Multi-Carrier feature affects the network
functions and capabilities.

4.1 Subscriber Capacity

This section provides information on the impact of the feature on subscriber
capacity.

EUL Multi-Carrier can provide up to 100% increase in maximum achievable

EUL user throughput compared to EUL single carrier, therefore UE can finish
data transfer faster and can be downswitched to common channel earlier.

4.2 Network Performance

This section provides information on the impact of the feature on network
performance.

The feature affects the network performance in the following ways:

 EUL peak user throughput can be increased by EUL scheduling on

two carriers simultaneously.
 Increased system throughput can be achieved. The feature can
increase the efficiency of the use of uplink resources.
 The RNC processor load is slightly increased as an expected
consequence of the 3GPP standard.

An EUL Multi-Carrier user allocates additional resources for the secondary

UL carrier.

RBS:

 Additional hardware (uplink channel elements).

 Additional EUL scheduling processing resources (number of EUL
users or E-DCH Radio Links).
 Signalling resources.
 Transport bearers.
 F-DPCH resources.

RNC:

 UL scrambling code.
 F-DPCH resources.
4.3 Hardware
This section provides information on the impact of the feature on hardware.

The feature needs the following hardware to be installed:

 RNC 3820, Evo Controller 8200/RNC or later.

 RBS 6000 family, as the feature requires DUW.

EUL Multi-Carrier is supported for both IP and AAL2 transport.

4.4 Inter-Node Interface

Affected interfaces when feature is activated:

 Iub
 Mur
 Mub

4.5 Other Network Elements

For the feature to work, the following conditions must be fulfilled:

 UE supports EUL Multi Carrier (3GPP HSUPA category 8-9 compliant

UE).
 OSS-RC O15.2.5 software is required.

5 Associated Features and Affected Functions

This section describes how the EUL Multi-Carrier feature affects other
features and functions.

5.1 Prerequisite Features

Table 3 lists prerequisite features to the EUL Multi-Carrier feature, that is,
they must be active before introducing the EUL Multi-Carrier.

Table 3 Prerequisite Features

Feature Description
Improved layer 2 This feature enables a configurable RLC Protocol Data Unit (PDU)
size and supports MAC-i/is on a single carrier.
HSDPA Multi-Carrier This feature enables simultaneous downlink HSDPA transmission
on two cells.
SRB on HSDPA/F-DPCH This feature enables establishment of downlink Signalling Radio
Bearer (SRB) on the HS-DSCH channel and use of F-DPCH
channels.
EUL 2-ms TTI This feature enables EUL 2 ms TTI.

5.2 Affected Features

 This feature affects no other feature.

5.3 Related Features

Table 4 lists features that are related to the EUL Multi Carrier feature.

Table 4 Related Features

Feature Description
HSDPA Multi-Carrier 3 Carriers In combination with EUL Multi-Carrier the HSDPA Multi-Carrier 3
Carriers feature can achieve even better performance in DL.
Data Acceleration When Data Acceleration feature is activated user can achieve higher
UL throughput
HSDPA IFLS Capability and Priority For the HS IFLS to consider the EUL Multi-Carrier capability, the
Handling HSDPA IFLS Capability and Priority Handling feature must be
activated and the priority must be set for the EUL Multi-Carrier
capability. For more information, refer to Load Sharing

5.4 Affected System Functions

Table 5 lists functions affected by the EUL Multi-Carrier feature.

Table 5 Affected System Functions

Function Description
Licenses and Hardware To activate the EUL Multi-Carrier feature, the license for the feature must be
Activation Codes installed and enabled.
EUL User Plane If the EUL Multi-Carrier feature is activated, EUL user throughput can increase up
to 100%.
EUL Migration and If the EUL Multi-Carrier feature is activated, EUL user throughput can increase up
Activation to 100%.
Enhanced UL Scheduler If the EUL Multi-Carrier feature is activated, EUL user throughput can increase up
to 100%.
Load Sharing The new EUL Multi-Carrier capability is included in the HSDPA IFLS Capability and
Priority Handling feature.
Connection Handling The EUL Multi-Carrier introduces a new type of connection capability.

Power Control New independent outer and inner loop power control functions are introduced for
secondary carrier.
Handover New intra frequency measurements are introduced for secondary carrier.
Admission control New admission control parameter is introduced to control the maximum number
of allowed EUL Multi-Carrier users in a cell.

6 Performance

This section describes performance indicators, counters, and events

associated with the EUL Multi-Carrier feature.

6.1 KPIs
This feature has no associated Key Performance Indicators (KPIs).

6.2 Counters
 Table 6 lists the counters introduced and affected by the EUL Multi-Carrier
feature.

Table 6 Counters
Counter Description
UtranCell::pmSumEulMcConn New counter. Sum of all sample values recorded during a ROP
for the number of established EUL Multi-Carrier connections.
UtranCell::pmSamplesEulMcConn New counter. Number of samples recorded within the ROP for
pmSumEulMcConn.
UtranCell::pmNoReqDeniedAdmEulMc New counter. Number of admission requests denied because
the number of EUL Multi-Carrier users is above the admission
threshold defined in attribute eulMcServingCellUsersAdmTti2
in MO: UtranCell, when requesting the cell as serving cell on
primary carrier.

Eul::pmEulRlcUserPacketThp Affected counter. For Multi-Carrier connections, this counter is

reported in the best cell in the primary active set (the active
set connected to the primary carrier), new bins added.
UtranCell::pmTotNoRrcConnectUeCapability Affected counter. The new FDD E-DCH Physical Layer Category
8 and 9 supporting EUL Multi-Carrier were included. Two new
bins added.

More information about counters can be found in Managed Object Model

RNC and Managed Object Model RBS.

6.3 Events
Table 7 lists modified events.

Table 7 Modified events

Event Added parameters
INTERNAL_UE_MOVE EVENT_PARAM_SECONDARY_ACTIVE_SET_C_ID_1,

EVENT_PARAM_SECONDARY_ACTIVE_SET_C_ID_2,

EVENT_PARAM_SECONDARY_ACTIVE_SET_C_ID_3,

EVENT_PARAM_SECONDARY_ACTIVE_SET_C_ID_4
INTERNAL_RAB_ESTABLISHMENT EVENT_PARAM_E_DCH_PHYSICAL_LAYER_CATEGORY_2
INTERNAL_SYSTEM_UTILIZATION EVENT_PARAM_NUMBER_OF_EUL_MULTI_CARRIER_USERS_IN_SERVING_
INTERNAL_CELL_LOAD_MONITOR_UPDATE EVENT_PARAM_NUMBER_OF_EUL_MULTI_CARRIER_USERS_IN_SERVING_

Table 8 lists new events.

Table 8 New events

New events
NBAP_SECONDARY_UL_FREQUENCY_UPDATE_INDICATION
NBAP_SECONDARY_UL_FREQUENCY_REPORT
NBAP_RADIO_LINK_PREEMPTION_REQUIRED_INDICATION

7 Operation and Maintenance

This section provides Operation and Maintenance (O&M) information for the
EUL Multi-Carrier feature.
7.1 Activating the Feature

7.1.1 Preconditions

This feature requires the following RAN features to be active:

 FAJ 121 1516: Improved Layer 2.

 FAJ 121 1441: HSDPA Multi-Carrier.
 FAJ 121 1320: SRB on HSDPA.
 FAJ 121 1481: F-DPCH.
 FAJ 121 1317: EUL 2-ms TTI.

Two cells configured for EUL Multi-Carrier have to fulfill following conditions:

 The cells are configured to be handled by the same Sector MO in the

RBS. This is done by referencing from the RbsLocalCells MO to the
carriers, (the Carrier MO), that belong to the same sector.
 The cells configured for EUL Multi-Carrier are configured on the same
BBP.
 Either both or none of cells support FAJ 121 1128: Transmit
Diversity feature.
 The cells need to be configured with adjacent frequencies.
 The UtranCell::tCell values for the cells capable of acting as a
primary HS-DSCH cell and as a secondary HS-DSCH cell pairs are
equal.

7.1.2 Activating

The feature is activated by:

 Ordering and installing FAJ 121 1491: EUL Multi-Carrier with license
key CXC 402 0037.
 Setting the RBS parameter RbsLocalCell::featureStateEulMc to
ACTIVATED on cells in which Eul Multi-Carrier should be activated.

Activation of the feature takes effect immediately.

The Handover::eulMcSohoSupp parameter indicates if the RNC supports

soft and softer handover for EUL Multi-Carrier connections. The default
value of this parameter is 1 (TRUE), which means that EUL Multi-Carrier can
be retained during soft and softer handover. Otherwise, the connection is
reconfigured away from EUL Multi-Carrier.

To check if EUL Multi-Carrier is activated, the following read-only

parameters can be used:

 If the NodeBFunction::licenseStateEulMc RBS parameter is set to

ENABLED, the license is valid.
 The MultiCarrier::eulMultiCarrierSupport RNC parameter
indicates if the cell supports EUL Multi-Carrier.

More information about licenses can be found in Licenses and Hardware

Activation Codes.
7.2 Deactivating the Feature

7.2.1 Preconditions

This feature has no preconditions for deactivating.

7.2.2 Deactivating

The feature is deactivated by setting the RBS parameter

RbsLocalCell::featureStateEulMc to DEACTIVATED for the selected cells.

More information about licenses can be found in Licenses and Hardware

Activation Codes.

7.3 Engineering Guidelines

The purpose of this section is to provide additional information on practical
engineering aspects about how to use parameters to achieve certain
behaviors.

7.3.1 Secondary Uplink Carrier Activation Delay

When UE is configured with EUL Multi-Carrier and the secondary uplink

carrier is activated immediately after setup, UL inter-cell interference can
occur on the secondary carrier. This applies to heterogeneous networks. To
avoid interference, the secondary carrier activation can be delayed in the
serving RBS. It enables the RNC and the UE to perform measurements on
the secondary carrier. The following
RbsLocalCell::eulMcActivationDelayTime RBS parameter is used to set
the delay value.

7.3.2 UE Measurements on Secondary Uplink Frequnecy

UE measurements on the secondary frequency are performed to avoid

interference in cells on secondary frequency that have no corresponding cell
in the primary frequency. Those measurements, containing secondary event
1a, introduce additional processing in the RNC.

Reporting range for secondary event 1a is calculated using following

formula:

 Reporting range for secondary event 1a = reportingRange1a +

reportingRange1aOffsetSecondary .

The value of reportingRange1aOffsetSecondary can be tuned to trade-off

between interference and the number of secondary events 1a. Lower values
of the parameter result in higher interference and lower number of
secondary events 1a.

7.3.3 Network Settings

 To improved network performance the following settings can be considered:

 Activate the FAJ 121 2444: Uplink Fast Congestion Control feature in
RBS by setting NodeBFunction::featureStateUlFcc to 1.
 Activate the FAJ 121 1714: Interference Suppression feature by
setting NodeBFunction::featureStateInterferenceSuppression
to 1.

7.3.4 HSDPA MC Inter DU Joint Scheduling with EUL Multi-Carrier

The HSDPA MC Inter DU Joint Scheduling feature makes it possible to run

HSDPA Multi-Carrier with RBS configurations that distribute two carriers into
two Digital Units (DUs). However, since the system does not support Joint
Scheduling for EUL Multi-Carrier, all cells from two carriers need to be
allocated on the same DU and on the same Baseband Pool (BBP) to run EUL
Multi-Carrier. It also means that a certain HSDPA MC Inter DU Joint
Scheduling configuration can be incapable of EUL Multi-Carrier.

Table 9 shows some possible HSDPA MC Inter DU Joint Scheduling

configurations and if they are supported by EUL Multi-Carrier.

Table 9 Examples of HSDPA MC Inter DU Joint Scheduling Configurations

Secondary
Dual-DUW configurations Primary DUW Support for EUL Multi-Carrier
DUW
3×2 (4-way RX diversity) s1f1 s1f2 No

s2f1 s2f2

s3f1 s3f2
3×4 (2-way RX diversity) s1f1, s1f2 s1f3, s1f4 Yes (f1+f2 on primary DUW; f3+f4 on
secondary DUW)
s2f1, s2f2 s2f3, s2f4

s3f1, s3f2 s3f3, s3f4

6×2 (2-way RX diversity) s1f1, s4f1 s1f2, s4f2 No

s2f1, s5f1 s2f2, s5f2

s3f1, s6f1 s3f2, s6f2

3×3 (2-way RX diversity) + 3×1 (2-way s1f1, s1f2 s1f3, s1f1 Yes (f1+f2 on primary DUW)
RX diversity)
s2f1, s2f2 s2f3, s2f1

s3f1, s3f2 s3f3, s3f1

3×2 (2-way RX diversity) + 3×2 (2-way s1f1, s1f2 s4f1, s4f2 Yes (f1+f2 on primary DUW; f1+f2 on
RX diversity) secondary DUW)
s2f1, s2f2 s5f1, s5f2

s3f1, s3f2 s6f1, s6f2

When HSDPA MC Inter DU Joint Scheduling is not used, the HSDPA Multi-
Carrier feature is supported only on the two frequencies allocated to the
same BBP and a single HSDPA processing resource. For more information,
refer to Configuring HSDPA and EUL. EUL Multi-Carrier can run with HSDPA
Multi-Carrier in this case.
7.3.5 Increased Cell Carrier Support for DUW with EUL Multi-Carrier

The Increased Cell Carrier Support for DUW feature can be used with the
HSDPA MC Inter DU Joint Scheduling feature to support HSDPA Multi-
Carrier on one DUW and two BBPs. Unlike HSDPA Multi-Carrier, EUL Multi-
Carrier cannot run on one DUW and two BBPs, since the system does not
support Joint Scheduling for EUL Multi-Carrier.

EUL Multi-Carrier can run over the cell carriers in the same BBP if they are
configured with two adjacent frequencies from the same frequency band.

Table 10 shows some possible configurations supported with HSDPA Multi-

Carrier and if they are supported by EUL Multi-Carrier.

Table 10 Examples of HSDPA MC Inter DU Joint Scheduling Configurations with Increased Cell
Carrier Support
Support
Secondary for EUL
Primary DUW
Configurations DUW Multi-
Carrier
BBP1 BBP3 BBP2
Single-DUW 3×2 (4-way RX diversity) s1f1 s1f2 No
configurations
s2f1 s2f2

s3f1 s3f2
3×4 (2-way RX diversity) s1f1, s1f2 s1f3, s1f4 Yes
(f1+f2
s2f1, s2f2 s2f3, s2f4 on
BBP1;
f3+f4 on
s3f1, s3f2 s3f3, s3f4
BBP3)
6×2 (2-way RX diversity) s1f1, s4f1 s1f2, s4f2 No

s2f1, s5f1 s2f2, s5f2

s3f1, s6f1 s3f2, s6f2

3×3 (2-way RX diversity) + 3×1 (2- s1f1, s1f2 s1f3, s4f1 Yes
way RX diversity) (f1+f2
s2f1, s2f2 s2f3, s5f1 on
BBP1)
s3f1, s3f2 s3f3, s6f1
3×2 (2-way RX diversity) + 3×2 (2- s1f1, s1f2 s4f1, s4f2 Yes
way RX diversity) (f1+f2
s2f1, s2f2 s5f1, s5f2 on
BBP1;
f1+f2 on
s3f1, s3f2 s6f1, s6f2
BBP3)
Dual-DUW 6×3 (2-way RX diversity) s1f1, s4f1 s1f2, s4f2 s1f3, s4f3 No
configurations
s2f1, s5f1 s2f2, s5f2 s2f3, s5f3

s3f1, s6f1 s3f2, s6f2 s3f3, s6f3

3×4 (2-way RX diversity) + 3×2 (2- s1f1, s1f2 s1f3, s1f4 s4f1,s4f2 Yes
way RX diversity) (f1+f2
s2f1, s2f2 s2f3, s2f4 s5f1,s5f2 on
BBP1;
f3+f4 on
s3f1, s3f2 s3f3, s3f4 s6f1,s6f2
BBP3;
f1+f2 on
BBP2)
 3×3 (4-way RX diversity) s1f1 s1f2 s1f3 No

s2f1 s2f2 s2f3

s3f1 s3f2 s3f3

Reference List

[1] GGSN-MPG 2011A Network Impact, 3/109 48-AXB 250 12

[2] EPG Feature, 19/221 02-AXB 250 12-V1