RBS 6000 Radio Blocks v1_5

RBS 6000 Radio Blocks

Version 1.5

Tim Verdonk Verdonk January, 2013

 Agenda • Radio Block Introduction •  Analog & Digital Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

Radio Block Naming Convention RBB22_1C Radio Block Version Version Radio Building Block 2 Tx Branches

1 CPRI Link to Digital Unit (DU) 2 Rx Branches

Supported Radio Blocks •

•

•

Not all Radio Blocks are supported for a given RAN technology, or for a given RBS type, or for a given software release  –

The RBS 6000 Configurations document covers WCDMA, LTE, GSM, and CDMA

 –

The RBS 6000 Configurations Configurations document provides a section section on “Supported Radio Radio Configurations” which shows the supported combinations of Radio Block and Baseband Configuration and the number of supported carriers for each configuration

Radio Blocks support specific radio hardware type and 3GPP frequency band for a given software release. Examples:  –

RBB22_2A supports RRUS 01 on W12B, but not on W 11B

 –

RBB22_2A supports WCDMA 2-way power split, not 3 or 4-way power split

 –

RBB22_2B not supported for WCDMA (W13A candidate)

 –

RBB24_2A for LTE supports only band class 3 & 9

 –

Dual-RRU radio blocks using the 2.4m Analog Rx Cross-Connect cables are not supported for RRU22 (no Rx I/O ports on RRU22)

Multi-standard Mode has a dedicated section in the RBS Configurations document  –

Multi-Standard Mixed Mode (MSMM) supporting WCDMA/LTE on the same radio is not supported in W/L12B for 850 or 1900 MHz

 –

Specific MSMM radio blocks are supported for specific combinations of RAN type and frequency band

RBS Configurations Document •

“Supported Radio Configurations” tells you what radio blocks are supported with what baseband configuration for each RAN type, how many sectors and how many carriers  –

•

Example below for W12B, similar table exists for Cascaded Configurations

“Sector Configurations” table will tell you which radio hardware types (RRUW, RRUS 01, RRUS 11) a radio block supports

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

 Analog Rx Cross-Connect •

Radio Blocks consisting of 2 RRU use either Digital or Analog Rx Cross-Connect  –  –  –

•

From an RBS scripting perspective, for RRUW & RRUS 01 there are only two branches: Branch A is on RRU #1 and Branch B is on RRU #2. Obviously, the two R/RU must be same band in order to cross-connect Rx The radio block constitutes a single logical sector on the baseband pool

 Analog Rx Cross-Connect uses the Ericsson 2.4 m co-site cable to supply an Rx signal from RxA I/O on one RRU to RxB I/O of the other RRU  –

2.4m cable part number RPM919665/02400 (CEQ.10387) •

 –

DO NOT substitute with 3 rd party cosite cables!! •

 –  –

•

Cable is purposely short to limit RF loss, since Rx I/O ports by-pass the internal LNA and connect directly to the radio Radio block compensates for branch B loss of the Ericsson 2.4m cosite c able, not the unknown loss of a 3rd party cable

LNA internal to the RRU has a Rx splitter which supplies the internal radio, the RxA I/O port & Rx Out port Entire receive band is passed through to the Rx I/O port

Each RRU is responsible for converting branch A & B analog Rx into CPRI baseband I/Q for the carriers hosted by the RRU  –  –

One baseband I/Q stream for each Rx branch of each carrier hosted by a RRU One baseband I/Q stream for each Tx branch of each carrier hosted by a RRU

2.4m cosite cables pass analog Rx signal from main antenna branch A on each RRU to diversity branch B on the other RRU.

Digital Rx Cross-Connect (Preferred over Analog Rx Cross-Connect) •

Radio Blocks consisting of 2 R/RU use either Digital or Analog Rx Cross-Connect  –  –  –

•

From an RBS scripting perspective, for RRUW & RRUS 01 there are only two antenna branches: Branch A is on RRU #1 and Branch B is on RRU #2. Obviously, the two R/RU must be same band in order to cross-connect Rx The radio block constitutes a single logical sector on the baseband pool

Digital Rx Cross-Connect does not use analog co-site cables  –

Fewer RF cables is better from a maintenance perspective, especially for tower-top RRU •

 –

•

No chance of water ingress, mechanical wind stress on cosite cables t hat do not exist

The Rx I/O ports are open and available to support analog cosite with other RRU supporting additional carriers

RRU #1 Antenna RF A port supplies baseband I/Q for branch A Rx for all carriers, while RRU #2  Antenna RF A port supplies CPRI baseband I/Q for branch B Rx for all carriers  –  –

Receive bandwidth of RRUW, RRUS, and RRU22 is 20 MHz, so all carriers must be within 20 MHz edge-toedge (note that for split-power transmit configurations, the RRU22 transmit bandwidth is 15 MHz) Branch B receiver of each RRU is unused and potentially available for future 4-branch Rx diversity if RxB I/O can be supplied with Rx3 / Rx4 signals from another RRU (e.g., from a LT E RRU in the same band, or from GSM in the same band if radio block RBB24_2A were eventually supported for WCDMA) Branch A rides on RRU #1 (RRU RF B receiver unused)

Branch B rides on RRU #2 (RRU RF B receiver unused)

RRU Radio Block Sets Rx I/O as Input or Output

The assigned Radio Block configuration determines if the internal LNA is connected to the RRU radio. If the radio block is configured to connect Rx signal on th e R/RU Antenna port, this switch is closed and the Rx I/O port is configured as an Output port. If the radio block is configured to connect Rx on the Rx I/O port, this switch is open and the Rx I/O port is configured as an Input port. Using a Rx I/O port that is configured as an Output port to input the Rx signal to the R/RU will result in very poor RF performance, since the internal LNA is still connected to the radio and injecting amplified thermal noise into the radio, as well as back through the Rx I/O port to the co-sited radio that is supplying the Rx signal. There is no RBS 3000 radio block equivalent to the RBS 6000 RBB11_1A or RBB10_1A radio block.

RBS 3x18 RRU Analog Cross-Connect 1 9 0 0

1 9 0 0

1 9 0 0

1 9 0 0

1 9 0 0

1 9 0 0

RxA I/O connects to RF B  Antenna Port on other RRU (RF B port is act ually on the bottom of the RRU)

RRUW 1C

2C

1C

2C

1C

2C

No RBS 3000 Radio Block exists to support direct RxA I/O to RxB I/O between RRU hosted by different RBS 3000 Baseband Pools

RBS 3x18

• •

Branch B LNA remains connected to RxB I/O Port, adding uplink noise (less impact with TMA, s ince Branch B LNA gain is reduced) Radio block does not compensate for 2.4m cosite cable RF loss (unbalanced branch A & B RSSI)

1C

2C

1C

2C

1C

2C

RBS 3x18

RRU Branch B gain and delay compensation set the same as for FU Branch B connected to RRU RxA I/O

Other RBS 3x18 RRU Analog Cross-Connect Options 1 9 0 0

1 9 0 0

1 9 0 0

1 9 0 0

1 9 0 0

1 9 0 0

1C RRU Branch B gain and delay compensation same as for FU connected to RxA I/O

RRUW

1C

2C

RBS 3x18

1C

2C

1C

2C

RxA I/O to RxB I/O supported with RRB 05 Radio Block for two RRU on the same Baseband Pool

2C RRU RxB I/O connected to 1C RRU RxA I/O via 2.4m cosite cable

1C

2C

1C

2C

1C

2C

RBS 3x18 RBS 6601 DUW

RBS 6000 Radio Block RBB11_1A supports diversity Rx on 2C RRU by connecting 1C RxA I/O to 2C RxB I/O (W12B required if RBB11_1A configured with TMA)

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

WCDMA Dual-Tx Configurations •

Table below shows WCDMA Dual Tx Configurations  –  –  –

•

For WCDMA Ericsson does not support Tx Diversity (STTD) due to major performance impact on legacy UE that do not support Tx Diversity  AT&T has not purchased WCDMA 2x2 MIMO feature Only WCDMA dual transmit option is simulcast with Common Pre-coder power balancing

Leave parameter transmissionScheme set to 0 (Single_Antenna) and script the RRUS 11 radio block (or dual-R/RU radio block) with two Tx branches

Dual Transmit Simulcast (a.k.a., Common Pre-Coder Load Balancing) •

Radio Blocks with two Tx branches and can support MIMO, Tx Diversity, or Simulcast  –  –

Radio blocks supporting RRUS 11 Radio blocks supporting two RRUW or RRUS 01 •

•

Simulcast on opposite +45 and -45 Antenna Polarities  –

•

Transmitting on same polarization can cause Fresnel fading (same reason why it is a good idea to transmit the same carrier frequency on opposite polarities of adjacent sectors)

RRUS 11 only supports Dual-Tx Simulcast on W11B  –  –

FFA in South Florida completed with Dual-Tx Simulcast W12B supports assigning carriers to separate branches of the RRUS 11 •

•

Only use for dual-RRU radio blocks using Digital Rx Cross-Connect, so that the RRU that remains alive continues to support one Rx branch for all carriers. With Analog Rx Cross-Connect, both receive branches are down on the failed RRU.

Why configure without Dual-Tx Simulcast given the advantages of Dual-Tx Simulcast (see next slide)?

No FFA completed for Dual-Tx Simulcast for Dual-RRU radio blocks on DUW  –

Dual-Tx Simulcast also supported on RBS 3000 for radio blocks with 2 Tx branches (no FFA completed)

Dual Transmit Simulcast Advantages •

WCDMA Simulcast improves reliability  –  –

If one PA fails on a RRUS 11, the other PA continues to transmit all carriers at half power If one RRU in a dual-RRU radio block fails, the other RRU continues to transmit all carriers •

 –  –

•

 –

If one RF path fades, it is unlikely the other RF signal on the opposite antenna polarity has also faded UE puts a rake finger on separate multipath rays, co-phases the output of each rake finger to sum the downlink power (i.e., 2x30W is equivalent to 1x60W but has the advantage of path diversity) Unlikely to result in any noticeable performance improvement, since most RF environments already have a great deal of RF multi-path scattering

WCDMA Simulcast is useful for power balancing  –  –

•

CPICH is also at half power, causing traffic to shed to neighboring sites Similar philosophy to LTE Cross-Sector-Antenna-Sharing-Redundancy for LTE, which goes one step further and ensure that each sector continues to operate if an entire RRU fails (e.g., due to failure of a common component like internal power supply, CPRI port, etc.)

WCDMA Simulcast creates more downlink multipath  –  –

•

Only use for dual-RRU radio blocks using Digital Rx Cross-Connect, so that the RRU t hat remains alive continues to support one Rx branch for all carriers. With Analog Rx Cross-Connect, both receive branches are down on the failed RRU.

Example: Two 60W RRUW in 3-way power split supporting 3 carriers @ 2x20W / carrier Example: WCDMA/LTE Multi-standard Mixed Mode on RRUS 11 with an odd number of WCDMA carriers

WCDMA Simulcast can simplify RF plumbing for >2 carriers in a band  –  –

Two 2x40W RRUS 11 on one antenna require two CCI Low-Loss Combiners (LLC) to couple four Tx branches onto two antenna feeders. Outdoor sites require cabinets for the combiners, and complex Rx co-site plumbing. Two 1x80W RRUS 01 on one antenna supply the same total RF power as two 2x40W RRUS 11 without the need for LLC Tx combiners or complex Rx co-site plumbing.

Example 1: Dual Tx Simulcast Power Pooling (three carriers band 1, one carrier band 2) RBB22_1C with two RRUW 2x20W/carrier or two RRUS 01 2x26.6W/carrier Antenna Branch A

Antenna Branch B

F1 / F2 / F3 TxA F1 / F2 / F3 RxA

F1 / F2 / F3 TxB F1 / F2 / F3 RxB

First RRU continues to transmit all carriers if cascaded RRU fails (without Rx Diversity)

Notes: 1. RBB22_1C supports up 3-way Split-Power on W11B, and up to 4-way Split-Power on W12B 2. Dual Tx Simulcast has not yet been FFA with 2 RRU (W11B FFA complete on RRUS 11) 3. 3x3 + 3x1 Configuration shown requires W12B Flexible Configuration Feature

S1 Band 1 F4

S4 Band 2

Inter-DUW CPRI Link

IDL Link

Primary DUW Hosts F1 / F2

DBB21_01 F3 Tx Baseband I/Q F3 Rx Baseband I/Q

Secondary DUW Hosts F3 / F4

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

DUW Star & Cascade Configurations •

Star configuration connects logical sectors directly to the baseband.

•

Cascade configuration daisy-chains logical sectors (e.g., to reduce optical fiber lease cost for baseband hotels supporting RRU on utility poles). Drawing shows RRUS, but can be RRUW or RRU22.

•

Up to 16 WCDMA baseband I/Q streams are supported in each direction (8 carriers with Rx Diversity & Tx Simulcast) on the 2457.6 Mbps CPRI link.

•

 A DUW 30 supports 12 baseband I/Q streams Rx, and 12 baseband I/Q streams Rx.  –

•

DUW 41 roadmap supports up to 24 baseband I/Q streams in each direction

Max CPRI distance on single mode 1310 nm dark fiber is 40 km for WCDMA, 15 km for LTE  –

 AT&T CTO has approved WCDMA SFPs supporting up to 20 km for WCDMA

 –

CPRI on multiplexed CWDM fiber is not supported

Single DU Configurations •

Multiple logical sectors assigned to the same DU CPRI port indicates a Cascade Configuration  –

Maximum 8 WCDMA Tx and Rx Baseband I/Q streams in each direction (4 carriers with Rx diversity)

•

DBB10_01 used for radio blocks with 2 CPRI connections to DUW (e.g., RBB22_2A)

•

W12B Flexible Configuration feature adds DBB10_99 with user -defined mapping of logical sectors to DUW port (FFA not planned)

W12B Flexible Configuration RBB10_99

Star

Cascade

Star

Example: 3x1+3x1 Cascade  Any UARFCN can be assigned to each logical sector (each RRU)

S6 1900

S4 1900

S2 1900

S5 850

S3 850

S1 850

Maximum 16 Tx & 16 Rx WCDMA Baseband I/Q Streams on one CPRI link using 2.5 Gbps SFP (8 carriers max with 2 Rx/carrier or 2 Tx/carrier). Half as many Baseband I/Q streams & carriers with 1.2 Gbps SFP.

DBB10_23

Dual-DUW Configurations •

Dual-DUW is a single RBS (single Site ID) with one transport connection to the primary DUW

•

Supports intra-RBS load balancing across all carriers (e.g., dual-band 3x2 + 3x2)  –

•

For 3x2 + 3x2 configurations, put the two 850 carriers on the primary DUW and connect the 850 RRU to the primary DUW  –

 –

 Avoids the need to use HS & non-HS IFLS to load ba lance between carriers on different RBS

If the unlikely event the secondary DUW fails, the two good-coverage 850 carriers remain on-air

W12B Flexible Configuration feature adds DBB21_99 with user-defined mapping of logical sectors to DUW port (FFA not planned) W12B Flexible Configuration RBB21_99

Dual-DUL Configurations (RBB20_02) •

Can be used in cases where there are insufficient SIAD ports to support separate connections to two DUL (e.g., a large DAS system)  –

FFA planned for February 2013

 –

Cannot cascade a DUL20 with DUS41 (must be two DUL20 or two DUS41)

SFP Guidelines •

DUW ships with RDH 102 45/3  –

• •

Prior to 10/15/2012 shipped with RDH 102 45/1

RRUW ships with RDH 102 47/1 RRUS ships with RDH 102 47/3

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

EUL on DUW •

DUW supports 256 EUL users, classic baseband 96  –

 –

With 6 cells on a busy site, the DUL flat-lines at 256/6 = 42.6 EUL users/cell, while classic flat-lines at 96/6 = 16 EUL users/cell Traffic that cannot be handled as EUL overflows to R99, which puts a lot more demand on available R99 uplink CE resources

•

With W12B, DUW handles 96 EUL users/cell, while classic remains at 32 EUL users/cell

•

 Anecdotal reports indicate that the RBS 6601 DAS system in AT&T Center in San Antonio is performing significantly better than comparable venues using classic baseband  –

Heavy uplink traffic in Arenas & Stadiums due to everyone taking and e-mailing photos leverages higher EUL capacity of DUW

 –

Results in lower uplink noise rise than classic baseband for similar venue & uplink traffic volume

 –

Uplink packet ACK/NACK throughput affects downlink throughput

800 RAX

700

DUW W12B

  s   r 600   e   s   u    f 500   o   r   e    b400   m   u   n300    l   a    t   o    T200 100 0 0

100

200 # EUL 2ms users

300

400

R99 UL CE Improvements in W12A SF

Current Uplink DCH CE Ladder 

W12A Uplink DCH CE Ladder 

Service (Example)

256

1

1

SRB(Stand-alone)3.4kbps

128

1

1

AMR4.75, AMR5.9

64

1

1

SRB(Stand-alone)13.6  AMR7.95  AMR12.2  AMR12.2 + PS0 PS16

32

2

1

PS32

16

4

2

PS64  AMR12.2 + PS64

8

8

4

PS128  AMR12.2 + PS128/HS

4

16

8

PS384

• W12A introduces an improved UL CE ladder for R99 on DUW − Not supported on RBS 3000 CPP baseband

• Increased CE efficiency by a factor of 2 for services running on SF4, 8, 16 and 32

DUW Downlink R99 CE Capacity •

DUW uses 0.5 CE DL for A-DCH, classic baseband requires 1 R99 DL CE  – Each HS user consumes less downlink R99 CE resources on DUW

•  AT&T typical DUW provisioning  – 1 EUL Resource_ID & 2 HS Resource_ID leaving 5 Resource_ID for R 99 CE (5 x 128 = 640 DL R99 CE) •

Each HS Resource_ID supports 128 HS users & 30 HS Codes across up to 6 cells

 – Each HS Resource_ID supports 128 HS users, so with 30% soft handoff overhead, we reserve 2 x 128 x 1.3 x 0.5 = 167 CE downlink reserved for A DCH, leaving 640 – 167 = 473 CE remaining for R99 traffic

•  AT&T typical classic baseband provisioning  – With 2 Tx60 cards, allocate 1 EUL Resource_ID & 5 HS Resource_IDs •

Each HS Resource_ID supports 96 HS users & 15 HS Codes across up to 3 cells

 –  AT&T Field Alert Guide 05.0-E-001 recommends reserving 375 CE for A-DCH (each A-DCH needs 1 CE) for this configuration, leaving 768 – 375 = 393 downlink R99 CE remaining for R99 downlink traffic  –

With current AT&T baseband provisioning, DUW has more R99 downlink CE than classic baseband

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

Configuration Definitions •

Band  –  –  –

•

B1 B2

Carrier  –  –

•

Frequency band, e.g. 2100 MHz, 900 MHz Possible to support within IBW of one Radio Unit Denomination B1, B2, B3, etc.

f1

One 5 MHz slot of the frequency band Denomination f1, f2, f3, etc.

f2

Cell-carrier  –

One WCDMA carrier in one physical direction • •

f1

3GPP defines this as a “cell” AT&T DAS team calls this a “sector -carrier”

f2 S1

•

RBS Sector (Logical)  –  Associated with a single RBS Radio Block  – Nomenclature used: S1, S2, S3, etc.  – RBS configuration sectors are logical sectors

•

RF Sector (Physical)

S2

S3

f1 f2

S1 S4 S3

S2

 –  All logical sectors/radio blocks in the same physical direction  – Multiple logical sectors can be associated with one RF sector

S6

S5

B1 B2

W11B Configuration Rules • One baseband pool supports a maximum of 6 cell-carriers  –

 AT&T DAS team calls a cell-carrier a “sector -carrier” (means the same thing)

• A logical sector can be assigned a maximum of 2 carriers  –

UARFCNs assigned to a logical sector must be in the same band

• A maximum of 3 logical sectors can be supported on a baseband pool if any sector is assigned 2 carriers (i.e., 3x2 max configuration)  –

Different sectors can be assigned to different bands (e.g., dual-band 1x2 + 1x2 configuration with two split-power RRU or four non-split-power RRU)

• A maximum of 6 logical sectors can be supported on a baseband pool if each logical sector is assigned a single carrier (i.e., 6x1 max configuration)  –

Each sector can have a different UARFCN belonging to either 850 or 1900 band

• Dual-DUW configurations can be viewed as summing the carrier counts on two individual DUW  –  –

Maximum of 6 logical sectors supported on W11A Dual-DUW configuration. A 6x2 configuration can be considered as a 2 x (6x1) with each DUW supporting 6x1. 3 & 4-way power-split RRU supported. A 3x4 can be considered 2 x (3x2) with each DUW supporting 3x2.

• No soft or softer handoff between two baseband pools belonging to the same RBS  –  –  –  –

 All carriers with the same UARFCN must be on the same baseband pool RNC expects to be able to use softer handoff between any two carriers on the same RBS assigned the same UARCN (no soft handoff between carriers with the same UARFCN) Baseband pool CE resources are not pooled, therefore no softer handoff between carriers on different baseband W13A supports soft handoff between carriers with the same UARFCN hosted by different baseband pools of the same RBS

W12B Flexible Configuration Feature (1/2) •

Flexible carrier mapping will make it possible to support configuration that were not possible previously due to the predefined set of rules that controlled carrier allocation to DUs and RUs

•

Previously, when carriers were created in an RBS, they were created according to configuration rules. With Flexible carrier mapping, the wireless operator can control carrier allocation to baseband units, frequency planes or radio units

•

With Flexible carrier mapping, the operator can control the allocation completely. The configuration checks will only verify that the configuration can be supported by the hardware, and that the same carrier UARFCN does not reside on two different baseband pools of the same RBS (will be allowed in W13A)

W12B Flexible Configuration Feature (2/2) •

Feature only applies to RBS 6000 DUW, not RBS 3000

•

W12B allows >2 carriers per logical sector  – Previously, each logical sector could have up to 2 carriers provided there were not more than 3 logical sectors on the DUW • With W11B, a Dual-DUW could support 3-way or 4-way power spli t by effectively configuring the primary DUW as 3x2, and the secondary DUW as either 3x1 (3-way split) or 3x2 (4-way split)

 – W12B supports 4+2, 3+1+2, etc. on a single DUW

•

W12B allows >1 carrier per logical sector with >3 logical sectors  – Example: 2+1+1+2, 1+1+3+1, etc. on a single DUW  – Prior to W12B, this type of configuration would be built up as a 6x1 configuration with two logical sectors assigned to the two RF sectors that had two carriers

Examples of W12B Flexible Configurations

W12B Flexible Configuration Rules

W12B Flexible Configurations Benefits

Dual-DUW Flexible Configuration Examples

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

RBB12_1A •

The most Basic of all Radio Blocks  –  –

•

One Transmit branch RxA on Antenna RF A, diversity RxB on Antenna RF B

RxA I/O and RxB I/O are configured as Output ports  –

Do NOT use for Rx input !!!

RBB22_1A •

 Analog Rx Cross-Connect between two RRU  –  –

•

Use if carriers separated by more than 20 MHz edge-to-edge (> 15 MHz between center frequencies)  –  –  –

•

RxA I/O is configured as Output RxB I/O is configured as Input

Can support up to 4 carriers (2 carriers assigned to each RRU) Each RRU can be assigned to cover any 20 MHz block of spectrum within the band  Analog Rx cross-connect used, so no RRU redundancy advantage of Dual Tx Simulcast (if cascaded RRU fails, we lose RxA and RxB for the carriers assigned to that RRU)

CPRI Cascade  –

Useful for Dual-DUW configurations which support a maximum of 6 direct connect CPRI links

RxA I/O to RxB I/O (Ericsson 2.4m cables, CEQ.10387)

RBB22_1B •

Basic Radio Block for RRUS 11  –

•

Two Tx branches on one RRU

RxA I/O and RxB I/O ports are configured as Output

RBB22_1C •

First supported on W11B CP2 IP5  –

•

Digital Rx Cross-Connect between two RRU  –  –  –

•

No analog cosite cables required RxA I/O is configured as Output  Antenna RF B receiver not used on either RRU

CPRI Cascade  –

•

Note that RBS 6000 DUWs cannot be re-homed between RNCs with W11B CP2 IP5 (fixed in W12B). Do not use RBB22_1C on W11B CP2 IP5 if you plan to re-home the RBS to a different RNC prior to W 12B upgrade.

Use for Dual-DUW configurations which support a maximum of 6 direct connect CPRI links

Supports 4-way Split-Power

RBB22_2A •

Same as RBB22_1C, except direct CPRI links from each RRU to baseband  –  Avoids the cascade CPRI in which an outage of the first RRU in the chain takes out the second RRU in the chain

•

Supports 4-way Split-Power (not 2-way as indicated in W12B documentation)  –

Digital Rx Cross-Connect with Dual-Tx simulcast supports RRU redundancy •

 –

Simulcast configuration has not been FFA on this radio block

Radio block requires 2 CPRI links, so not useful for Dual-DUW since Dual-DUW can only terminate 6 direct CPRI links (i.e., maximum 6 cell-carriers supported on a Dual-DUW with this radio block)

RBB22_2A Example RBB22_2A with two RRUW 2x30W/carrier or two RRUS 01 2x40W/carrier Antenna Branch A

Antenna Branch B

F1/F2F3/F4 TxA F1/F2/F3/F4 RxA

F1/F2/F3/F4 TxB F1/F2/F3/F4 RxB

One RRU continues to transmit all carriers if other RRU fails (without Rx Diversity)

Notes: 1. Configuration shown might be used for very high traffic site 2. RRUS 01 first supported on W12B (RRU22 & RRUW supported on W11B) 3. Also supported on one DUW with DBB10_01

S1

Inter-DUW CPRI Link

IDL Link

Primary DUW Hosts F1

DBB21_02 F2 Tx Baseband I/Q F1 Rx Baseband I/Q F1 Tx Baseband I/Q F2 Rx Baseband I/Q

Secondary DUW Hosts F2

RBB22_2B •

First supported on W13A

•

Same as RBB22_2A, except uses Analog Rx Cross-Connect  –  –

•

Uses Ericsson 2.4m cosite cable to inter-connect Rx I/O ports Use this radio rather than RBB22_2A if any of the carriers hosted by the radio block are more than 20 MHz apart edge-to-edge (more than 15 MHz spacing between UARFCN)

Two CPRI links required  –

Dual-DUW can connect a maximum of 6 CPRI links

RBB22_2B Work-around (prior to W13A) RBB22_2B

RxA I/O to RxB I/O

RBB22_2B Not Supported for WCDMA prior to W13A

RBB11_1A

RxA I/O to RxB I/O (Ericsson 2.4m cables, CEQ.10387)

RBB11_1A as Alternative to RBB22_2B - More complex to calculate branch B feeder ulAttenuation & electricalUlDelay than with RBB22_2B - RBB11_1A does not work with a TMA defined on W11B (fixed in W12B)

RBB42_1B •

First supported on W12B

•

Cosite two RRUS 11  –

•

Example: Each RRUS 11 operating Spilt-Power supporting 2 carriers

Can use CCI Low-Loss Combiner to combine RRU #1 TxA with RRU #2 TxB, and RRU #2 TxA with RRU #1 TxB  –

Low-Loss Combiner available with either 5 MHz or 10 MHz band-pass

 –

10 MHz band-pass needed if operating each RRUS 11 with Split-Power Dual-Tx Simulcast with adjacent 5 MHz carriers

 –

5 MHz band-pass OK if one 5 MHz carrier allocated per Tx branch

RxA I/O to RxB I/O (Ericsson 2.4m cables, CEQ.10387)

RBB42_1B Example Beta

 Alpha

Gamma

DC By-Pass for TMA (if required)

CCI Tunable Low-Loss Combiner

Tx Only

RRUS 11

RRUS 11

RRUS 11

RxA I/O to RxB I/O (Ericsson 2.4m cables, CEQ.10387)

1C/2C

DBB21_01

3C/4C

RBB11_1A •

RxB I/O configured as Input  –  –

Internal branch B LNA disconnected to avoid injecting amplified thermal noise into the radio and onto the Rx B I/O port RxB I/O by-passes the internal 17 dB gain LNA, so external Rx gain must be supplied to RxB I/O to maintain the cascaded NF performance on branch B

•

RxA I/O configured as Output

•

Do not use with TMA defined on R/RU until W12B  –

Reports wrong RSSI with TMA defined until W12B

RBB10_1A •

RxA I/O & RxB I/O configured as Input  –  –

•

Internal branch A & B LNA disconnected to avoid injecting amplified thermal noise into the radio and onto the Rx I/O ports Rx I/O ports by-passes the internal 17 dB gain LNA, so external Rx gain must be supplied to Rx I/O ports maintain the cascaded NF performance

Do not use with TMA defined on R/RU until W12B  –

Reports wrong RSSI with TMA defined until W12B

RBB10_1A Example 1 9 0 0

1 9 0 0

1 9 0 0

DC By-Pass for TMA (if required)

CCI Tunable Low-Loss Combiner Tx Only 1C

3C

2C

4C

1C

3C

2C

4C

1C

3C

2C

4C

Ericsson 2.4m cables (CEQ.10387) 1C & 2C RRU RBB22_2A Digital Rx Cross-Connect 1C/2C

3C/4C

The two DUW cannot be configured as a Dual-DUW for this scenario, since there is no Radio Block that supports 3C/4C RRU with cascaded CPRI with both RxA I/O and RxB I/O configured as input ports.

3C & 4C RRU use Radio Block RBB10_1A. 1C RxA I/O connects to 3C RxA I/O, 1C RxA Out connects to 4C RxA I/O. 2C RxA I/O connects to 3C RxB I/O, 2C RxA Out connects to 4C RxB I/O.

RBB11_1A & RBB10_1A Co-Site Parameters •

Cosite calculations for RBB11_1A and RBB10_1A do not follow standard cosite practices because signals input to the Rx I/O ports by-pass the internal LNA  –  –

•

Without TMA Defined on RRU  –  –  –

•

RRU is optimized for ≈17 dB of LNA gain without TMA gain (LNA gain is backed off by an amount equal to TMA gain – uplink feeder loss when TMA is defined) Unlike the “standard” cosite configurations that supply Rx signal to the antenna RF B port of the RRU, we do not use a 5 dB SMA attenuator to reduce gain if the calculated value of feeder ulAttenuation is more negative than -12 dB (i.e., when external gain exceeds 12 dB)

 All gain/loss and delay from the antenna to the Rx I/O port is entered as feeder gain/loss and delay (MO class antFeederCable) Include gain and delay through the radio that supplies the Rx signal Feeder ulAttenuation is a loss parameter, so gain is entered as a negative value

With TMA Defined on RRU (supported on W12B)  –  –  –

Enter the usual TMA parameters to account for TMA uplink gain, downlink attenuation, and uplink/downlink delay Calculate uplink gain/loss and delay from output of TMA to Rx I/O port. Subtract 12 dB from feeder ulAttenuation to account for TMA gain. Enter the resulting gain/loss and delay values as feeder uplink gain/loss and delay For radio blocks on which the Rx signal arrives on the R/RU antenna connector, the LNA would decrease its gain to offset TMA gain, but with these two radio blocks the Rx signal input to the Rx I/O port by-passes the LNA and therefore the gain of the TMA needs to be accounted for via antFeederCable_ulAttenuation

Rx I/O Delay This table gives the delay through the RRU or FU that supplies the Rx signal to a R/RU configured with RBB11_1A or RBB10_1A

Entry 0 1 2 3 4 0 1 2 3 4 5 6 7 8 9 10 11

Frequency Range 850 MHz 824 - 829 829 - 834 834 - 839 839 - 844 844 - 849 1900 MHz 1850 - 1855 1855 - 1860 1860 - 1865 1865 - 1870 1870 - 1875 1875 - 1880 1880 - 1885 1885 - 1890 1890 - 1895 1895 - 1900 1900 - 1905 1905 - 1910

FU / RRU Delay (ns) 108 91 91 99 136 51 46 43 42 42 42 41 45 46 50 58 71

Example: RBB11_1A Co-site Parameter (work-around solution for RBB22_2B until W13A) •

RBB11_1A

Branch B ulAttenuation (with TMA):  –  –

RBB11_1A RBB11_1A does not work with T MA defined until W12B Gain thru RxA I/O port of RRU supplying Rx signal to RxB I/O port is:

 –

Branch B ulAttenuation is set to the to tal loss from the TMA input to the RxB I/O port (gain is a negative value, since ulAttenuation is a loss parameter):

17 – 17 – TMA  TMA Gain + Uplink Feeder Loss

= -TMA Gain + Branch A ulAttenuation (of other RRU) – RRU) – RxA  RxA I/O Gain + cosite cable loss = - TMA gain + Branch A ulAttenuation – ulAttenuation – [17  [17 –  – TMA  TMA Gain + Uplink Feeder Loss] + cosite cable loss = -17 + cosite cable loss = -17 + 3.0 = -14.0 dB

•

Branch B ulAttenuation (no TMA):  –  –

RxA I/O to RxB I/O (Ericsson 2.4m cables, CEQ.10387)

 –

 Assume uplink feeder loss = 2.5 dB Ericsson 2.4m cosite cable has 3.0 dB loss at 1900 MHz, and 1.9 dB at 850 MHz Branch B ulAttenuation: = -17 + Branch A ulAttenuation (of other RRU) + cosite c able loss = -17 + 2.5 + 3.0 = -11.5 dB

•

Branch B electricalUlDelay  –  –

Feeder uplink Delay + Rx I/O Delay + cosite cable Delay 2.4m cosite cable @ 70% propagation constant has delay of 11.4 ns

 Agenda • Radio Block Introduction •  Analog & Digital Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

RBB22_2E (RRUS 11) •

Use for LTE Cross-Sector Antenna Redundancy  – Half of each RRUS 11 is assigned to a sector, the other half to a different sector

•

See AT&T document ATT-002-290-580 ATT-002-290-580 “Cross Sector Redundancy R edundancy Feature”

L12B AIR Radio Blocks Radio blocks supporting 4-branch Rx applicable for AT&T (RBB24_1A & RBB24_2C)

 AIR 21 Configuration

 AIR 21 B4A RRUS 11 B12

Multi-fiber CPRI cable

RBB24_1A (AIR) •  AIR looks like two 30W RRUS 01 to the DU • CPRI cascade internal to AIR

RBB24_2C (AIR) •

Dual CPRI connection to DU  – Single DUL uses DBB10_01 or dual-DUL uses DBB20_02, capable of terminating two CPRI links per logical sector

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

MSMM Roadmap •

x13B supports MSMM on AIR Antenna (x = LTE or WCDMA)  – With LTE MIMO, WCDMA carriers must be on one of the two 30W branches

•

x14 supports full AIR MSMM with WCDMA dual-Tx Simulcast balancing RF power across the two 30W branches

•

W13A supported MSMM Frequencies shown in the table below

x13A MSMM Radio Blocks Table below shows mix of WCDMA & LTE carriers supported on various radio blocks in x13A

RBB22_2C • RRUS 11 supporting MSMM

RBB22_2C Example (1 WCMDA & 5 MHz LTE)

 AIR may use this radio block in x13A & x14 (TBC) RRUS 11

S1

DUW DBB10_01

2x20W WCDMA Dual-Tx Simulcast 2x20W LTE MIMO

DUL DBB10_01

RBB22_4B • RRUS 01 supporting MSMM

RBB22_4B Example (3 WCMDA & 5 MHz LTE) RBB22_4B with two RRUS 01 (160W total RF Power) Antenna Branch A

Antenna Branch B

F1 / F2 / F3 / LTE TxA F1 / F2 RxA/B LTE RxA

F1 / F2 / F3 / LTE TxB F3 RxA/B LTE RxB

RBB22_4B requires  Analog Cosite Cables for WCDMA (LTE uses Digital Rx CrossConnect)

Notes: 1. MSMM not supported for 850 or 1900 MHz on any radio block in x12B 2. Up to 6 dB difference in power allocation between WCDMA and LTE (i.e., one RAN access technology can be allocated up to 4X more RF power than the other RAN type)

S1 DUL/DUS DBB10_01 Inter-DUW CPRI Link

IDL Link

Primary DUW Hosts F1 / F2

DBB21_01 F3 Tx Baseband I/Q F1 / F2 Tx Baseband I/Q

Secondary DUW Hosts F3

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

 AT&T Script Tool: Dual-RRU Radio Blocks •

For RBS 3000 & RBS 6000 radio blocks that consist of two RU or RRU, the script tool presents carrier RSSI information in vertical columns. The script tool output appears as follows:  –

The script tool output compares the RSSI on the same br anch of the dual-RRU radio block, but for different carriers

RBS RUIF_SLOT RU_PORT RSSI_A RSSI_B DELTA POWER SAMPLES SERIAL SECTOR CID RU_SLOT ---------------------------------------------------------------------------------DXU5263 1 00 -103.6 -102.7 00.9 35.8 A:46/B:47 DXU5263 1 01 -104.8 -103.2 01.6 34.8 A:46/B:47 DXU5263 1 02 -101.6 -102.2 00.6 35.6 A:47/B:47 DXU5263 1 03 -103.7 -102.4 01.3 35.6 A:46/B:47 DXU5263 1 04 -105.0 -104.3 00.7 35.0 A:46/B:47 DXU5263 1 05 -099.3 -102.6 03.2 35.9 A:47/B:47

•

The RSSI values need to be interpreted as shown in the table below  –

Carrier 1 transmits on branch A of the dual-RRU radio block, carrier 2 transmits on branch B of the dual RRU radio block

RU_Slot

•

RSSI_A

RSSI_B

00

-103.6 RX branch A of S1C1

-102.7 RX branch A of S1C2

01

-104.8 RX branch A of S2C1

-103.2 RX branch A of S2C2

02

-101.6 RX branch A of S3 C1

-102.2 RX branch A of S3C2

03

-103.7 RX branch B of S1C1

-102.4 RX branch B of S1C2

04

-105.0 RX branch B of S2C1

-104.3 RX branch B of S2C2

05

-99.3 RX branch B of S3C1

-102.6 RX branch B of S3C2

The RSSI Script Tool works OK for radio blocks consisting of a single RU or RRU

Locking Branch B for Active DAS Systems •

RBS supporting active DAS systems that do not have Rx diversity must lock branch B Antenna Interface (AiDevice =2) to inform that EUL scheduler that the RBS does not have Rx diversity  – Failure to lock branch B can result in EUL power rushes, since the EUL scheduler assumes it has the benefit of Rx diversity whereas in fact it does not  – Do not attempt to “Disconnect” branch B in OSS, as it will corrupt the software. The radio will be out-of-service following the next restart  – Do not provide the radio with fake diversity using an R x splitter to provide the same Rx signal on both R/RU branches, as this will disrupt layer 1 processing and result in very poor RF performance and uplink throughput  – Standard RF practice is to terminate unused radio ports with a 50 ohm terminator to prevent spurious signals from entering the radio

 AT&T Script Tool: Locking Branch B •

Example below shows a split-power R/RU supporting 2 carriers, with no coax cable connected to branch B  – With branch B Antenna Interface (AiDevice = 2) unlocked, the Script tool properly shows RSSI readings for branch A of both carriers, with branch B down at the noise floor  – Locking branch B causes the Script tool to present the 2 nd carrier branch A RSSI as branch B RSSI of the 1 st carrier

AIDEVICE=2 UNLOCKED: RBS RUIF_SLOT RU_PORT RSSI_A1 RSSI_B1 RSSI_A2 RSSI_B2 DELTA POWER_A1/A2 SERIAL SECTOR CID RU_SLOT UTRANCELL -----------------------------------------------------------------------------------------------------------------GSVLFLU0189 01 00 -103.0 -105.5 -102.8 -105.5 02.5/02.5 34.1/34.1 GSVLFLU0189 01 01 -103.8 -105.5 -104.0 -105.6 01.7/01.7 34.1/34.1 GSVLFLU0189 01 02 -103.5 -105.3 -103.1 -105.4 01.8/01.8 34.1/34.1

AFTER LOCKING AIDEVICE=2: RBS RUIF_SLOT RU_PORT RSSI_A RSSI_B DELTA POWER SAMPLES SERIAL SECTOR CID RU_SLOT UTRANCELL ----------------------------------------------------------------------------------------------------------------------------GSVLFLU0189 01 00 -103.1 -102.9 00.2 34.0 A:70 /B:70 GSVLFLU0189 01 01 -103.8 -104.0 00.2 33.9 A:70 /B:70 GSVLFLU0189 01 02 -103.6 -103.4 00.3 34.0 A:69 /B:70

RSSI-by-Branch Daily Report •

RSSI-by-Branch Daily report almost certainly uses the same logic as the script tool, hence the RSSI report compares branch A & B RSSI of different carriers for sites using radio blocks with two RRU or RUS/RU22, and for split-power R/RU with branch B locked

•  AT&T CTO has a MRD requesting per-branch RSSI counters, which would then allow for an accurate RSSI report

 Absolute versus Relative RSSI •

Chart below is uplink RSSI rise-over-thermal (RoT) noise floor for San Francisco Area 10B  –

Uplink RSSI varies strongly by time of day

•

Sites with low traffic can have high noise rise, sites with high traffic can have low noise rise => implies most interference is external to the site, not self-interference

•

For New Site Builds, absolute RSSI as a measure of a properly commissioned site is not very useful. Instead, aim to balance branch A & B RSSI within 2.0 dB (typically better than 1.5 dB)

F2 RoT vs UL ASE Load 30

25

5AM 12PM

20

      )       B       d       ( 15       T     o       R 10

5

0 0

20

40

60 ASE

80

100

 Agenda • Radio Block Introduction •  Analog & Digital Rx Cross-Connect • WCDMA Dual-Tx Simulcast • Baseband Configurations • DUW & Classic Baseband Capacity • WCMDA Configuration Rules • WCMDA Radio Blocks • LTE Radio Blocks • Multi-Standard Mixed Mode Radio Blocks • RSSI Script Tool Issues • RF Power Parameters & Licenses

RF Power Output •

tpaDevice = Transmit Power Amplifier  –

•

•

One tpaDevice on the RRUW & RRUS 01, two tpaDevices on RRUS 11

maxTotalOutputPower (MO class tpaDevice)  –

The maximum total output power of the TPA device. W hen set to the undefined value of -1, the output power is set by the RBS to the highest value the HW supports without the need for a capacity license, i.e. 20 W (10 W in case of a dual TX RRUW).

 –

When maxTotalOutputPower is set above 20 up to 40 W, the capacity license ‘Number of 40 W Power  Amplifiers' is required. When set above 40 up to 60 W, the capacity licenses for 40 and 60 W power amplifiers are required. When set above 60 up to 80 W , the capacity licenses for 40, 60 and 80 W power amplifiers are required. When set above 80 up to 100 W , the capacity licenses for 40, 60, 80 and 100 W power amplifiers are required. When set above 100 up to 120 W, the capacity licenses for 40, 60, 80, 100 and 120 W power amplifiers are required.

 –

When using a dual TX RRUW (an RRU with two T PA devices) this attribute can only be set up to half of the licensed power. For example, if set to 40W on each tpaDevice of a RRUS 11, capacity licenses for 40, 60, 80W power amplifiers are required. The capacity license power applies to the RRUS 11 as a whole, and each tpaDevice on the RRUS 11 is allocated half of the licensed power.

 AT&T configuration of maxTotalOutputPower  –

Power licenses do not apply to RBS 3000 RU22 or RRU22, so maxTotalOuputPower is set to -1 (undefined)

 –

For RRUW, set to 60W

 –

For RRUS 01 set to 80W

 –

For 2x40W RRUS 11 set to 40W on each tpaDevice (30W per tapDevice for 2x30W RRUS 11)

License RF Capacity •

For RBS 6601 AT&T did a buy-out of RF power licenses  – Set number of 40W, 60W, 80W power licenses equal to the maximum number of RRU supported by the DUW or dual-DUW (6 for single DUW, 12 for Dual-DUW) • licenseCapacityNum40WPowerAmplifiers • licenseCapacityNum60WPowerAmplifiers • licenseCapacityNum80WPowerAmplifiers

•

For indoor RBS 6202 or 6201 default is no licenses (maxTotalOutputPower = -1) which sets RUS output power at 20W  – Still too much power for Active DAS systems, which need ≈1 W for RF -to-optical conversion  – For non-DAS macro network sites, RF power licenses can be purchased with exception approval from AT&T CTO (Rob Taylor) • WCDMA order code CEQ.12547 (20W to 80W) • LTE order code CEQ.12548 (20W to 80W)

maxDlPowerCapability (MO class RbsLocalCell) •

•

•

Without TMA, some markets include top  jumper loss in feeder loss (reference point at the antenna connector), and some markets do not (reference point at the connection point between main feeder & top jumper). System calculates maxDlPowerCapability as the maximum supported RF power per carrier at the antenna reference point. This is the max possible carrier power at the DIN connector on the radio, minus downlink feeder loss, minus TMA downlink insertion loss (AT&T uses 0.5 dB as TMA downlink insertion loss). For RRUS 11 operating with MIMO or Tx simulcast, the per carrier power is the sum of the carrier power on both tpaDevices (e.g., a RRUS 11 supporting two carriers at 2x20W has maximum per-carrier power out of the RRUS 11 of 40W).

Config A

Config B

(no TMA)

(with TMA)

ANT

ANT

ANT port

ANT jumper  OR

Ref. Pt. TX/RX power 

Ref. Pt. TX/RX power 

TMA ant port TMA

TMA rbs port

ANT feeder 

ANT feeder 

RBS ant port

RBS

RBS

maximumTransmissionPower (MO class RbsLocalCell) •

•

•

maximumTransmissionPower allows the wireless operator to li mit RF power per carrier at the antenna reference point to less than maxDlPowerCapability  –

Ever since an issue in P6 software prevented the radio from going service if maximumTranmissionPower was set greater than maxDlPowerCapability, the Ericsson RNDCIQ team has ensured that maximumTranmisssionPower does not exceed maxDlPowerCapability

 –

Unknown if the original P6 issue has been resolved (i.e., will the radio go into service if maximumTransmissionPower is set to its maximum value?)

For RRUW expansion of macro RBS 3x06, the original FFA set maximumTranmissionPower based on allowing the RRUW to operate at maximum 40W  –

Set to 40W – downlink feeder loss – TMA downlink insertion loss (if TMA present)

 –

Designed to ensure that the 60W RRUW did not cause an unfair share of downlink interference into neighboring sites that were using RBS 3x06 40W RU22

 –

Ericsson RNDCIQ continues to use this method to calculate maximumTransmissionPower for RRUW expansion of macro RBS 3x06

For unknown reasons, maximumTransmissionPower for RBS 3x06 and RBS 6601 main/remote is calculated assuming 60W RF power out of the RRUW (30W/carrier for split-power RRUW)  –

Not consistent with how maximumTransmissionPower is calculated for RRUW expansion of RBS 3x06

 –

 Allows the RRUW to cause unfair interference into neighboring sites

1/SINR = 1/SNR + 1/SIR •

 At 6 dB Rise-over-Thermal, interference power is 100.6= 4 times greater than thermal noise power, meaning that thermal noise power is 20% of total thermal noise + interference power, and interference is 80% of total thermal noise + interference power

•

When signal power is well above the thermal noise floor, SNR >>1 and 1/SNR