TMA Use Cases

Sacramento RF Engineering

T-Mobile Confidential
 SINR Weekly Report – Talking Points

➢ Focus on Cell Category and Issue

✓ L21 and L19 are easier to troubleshoot
✓ L7 (& L6) are more challenging and usually require FOPs field support
✓ Sites with TMA configuration issue will typically have multiple offending cells

➢ Huge imbalances between antenna branches may still exist although N+I trending on PUCC and PUSCH are still
within the target thresholds if you compare the per RF Branch Ave N+I versus sector level PUCCH & PUSCH N+I
trending

➢ Always check current site configuration – latest version of RFDS for the site, paying attention to the following
✓ What type of TMA is used and how it is shared between the technologies
✓ Number of feeder lines per sector, type and length and how the lines are shared between technologies
✓ RU/RRU placement, ground based or installed at the antennas

➢ Don’t ignore dlAttenuation settings → affects EIRP (maximumTransmissionPower)

➢ Ask FOPs to visually check TMAs and RU connections for verification

Slide / 2 T-Mobile Confidential

 SINR Weekly Report – Talking Points
➢ Golden Feeder Concept – when to use and what values to use
✓ Scenario 1: Style 3 defined @ L21→ L19 always assume (-) attenuation computed as – (TMA Gain – line loss)
✓ Scenario 2: When RF Branch 2 rfPortRef is set to RfPort=RXB_IO with attenuation values depending on RBB

Slide / 3 T-Mobile Confidential

 SINR Weekly Report – Talking Points
➢ Understand the MOs associated with TMAs
✓ All antenna related components are grouped into AntennaUnitGroup MO, i.e. TMA, RET
✓ TMA HW MO → AntennaNearUnit, typically set to 2
✓ TmaSubUnit → logical address, that specify signal paths for different technologies inside the TMA HW
✓ See next slides for TMA MO modelling

Slide / 4 T-Mobile Confidential

 TMA MO Modelling in the Ericsson System - Examples
Style 1B (KRY112144/1) – Twin AWS/AWS

TmaSubUnit=1 TmaSubUnit=2

Slide / 5 T-Mobile Confidential

 TMA MO Modelling in the Ericsson System - Examples
➢ Another Example – Style 3CX

Slide / 6 T-Mobile Confidential

 TMA MO Modelling in the Ericsson System - Examples
➢ Another Example – Style 4 (2 per Sector)

AntennaNearUnit=2 AntennaNearUnit=4

TmaSubUnit=1 TmaSubUnit=2 TmaSubUnit=1 TmaSubUnit=2

Slide / 7 T-Mobile Confidential

 Cheat Sheet
Vendor Product Number Style Type Modularity TmaSubUnit=1 TmaSubUnit=2 TmaSubUnit=3 TmaSubUnit=4
RFS ATM1900D-1A20 Style 1A Uniplex Twin PCS PCS - -
RFS ATM700LD-1A20 Style 1C Uniplex Twin 700 700 - -
RFS ATMA3P4-1A20 Style 4 Diplex Single AWS PCS - -
RFS ATMA4P4-1A20 Style 4 Diplex Single AWS PCS - -
Commscope E15S08P80 Style 1B Uniplex Twin AWS AWS - -
Commscope E15S09P84 Style 4 Diplex Single AWS PCS - -
Commscope E15S09P91 Style 3B Diplex Single AWS PCS - -
Commscope E15S09P94 Style 1A Uniplex Twin PCS PCS - -
Commscope E15Z01P23 Style 3C Diplex Twin PCS AWS PCS AWS
Commscope E15Z01P33 Style 3C Diplex Twin PCS AWS PCS AWS
Commscope E25A01P02 (E15Z01P39) Style 3CX Diplex Twin PCS AWS PCS AWS
Ericsson KRY112489/2 Style 1A Uniplex Twin PCS PCS - -
Ericsson KRY112144/1 Style 1B Uniplex Twin AWS AWS - -
Ericsson KRY112144/2 Style 1BX Uniplex Twin AWS AWS - -
Ericsson KRY112212/1 Style 1C Uniplex Twin 700 700 - -
Ericsson KRY112214/1 Style 3C Diplex Twin PCS PCS - -
Filtronic SXC050-V1 Style 4 Diplex Twin AWS/PCS AWS/PCS - -
Commscope E15S07P29 Style 1B Uniplex Twin AWS AWS
Commscope E15S08P78 Style 2 Diplex Single AWS PCS
Commscope E14R00P13 Style 1B Twin Twin PCS PCS

Slide / 8 T-Mobile Confidential

 TMA Commands - MO locked state vs. On-Line Modifications
➢ 2 Levels of resets (bl & deb)
✓ Sector Equipment Function Level → service affecting
✓ TMA HW Level → non-service affecting

➢ Situations where you don’t have to do a reset (at any level)

✓ When changing UL & DL attenuations (ulAttenuation, dlAttenuation)
✓ When changing UL & DL traffic delay (ulTrafficDelay, dlTrafficDelay)
✓ Activating rfPort where rfPortRef for AntennaNearUnit is connected

➢ Changes that require bl/deb procedures

✓ When defining TMA from scratch → TMA HW Level, sometimes SectorEquipment Function needs to be
locked to
✓ When changing TMA specific parameters → dlAttenuation, ulTrafficDelay, dlTrafficDelay
✓ After assigning tmaRef to each cell/sector

Slide / 9 T-Mobile Confidential

 Troubleshooting Commands
▪ st antennaNearUnit Check status of TMA (physical)
▪ get antennaNearUnit=[2,4] productNumber Type of TMA, use next slide
▪ get antennaNearUnit=[2,4] iuantDeviceType Make sure is defined as TMA (2)
▪ get antennaNearUnit=[2,4] rfPortRef Check which port is powering TMA
▪ hget antennaNearUnit=[2,4] operationalState|productNumber|iuantDeviceType|rfPortRef
▪ st tmaSubUnit Check status of internal TMA (logical)
▪ get tmaSubUnit iuantTmaSubunitFreqRange Check TMA supported Frequency Rx/Tx
▪ get rfBranch tmaRef Validate reference to tmaSubUnit supported freq
▪ st rfPort=A Verify the path of radios by doing "st rfPort=A“
▪ lh ru fui get devstat Check board level level ulGain
▪ lh ru fui get vswr Check board level level VSWR
▪ invxrf RU, DU, Board level info
▪ pmxeh -m 1 fdd Int_RadioRecInterferencePwr$|Int_RadioRecInterferencePucchPwr$ Sector level RSSI

Slide / 10 T-Mobile Confidential

 TMA Configuration Scenarios/Cases
Case Description
Non AWS cells mapped to AWS TMA
1 Non PCS cells mapped to PCS TMA
Non 700 cells mapped to 700 TMA
2 Node with defined TMA and Attenuation = 0
3 Node with defined TMA and Negative (-) Attenuation
4 Node with no TMA defined and TMA physically installed
5 Node with Ground Based RRUs but attenuation is 0 or 3
6 Node converted to AIR but attenuation not set to 0
7 Node converted to 794ARV2 (Ground Based 794AR V2)
8 Node with AntennaNearUnit defined but no TmaSubUnits
9 Nodes with TMA definition but missing tmaRef on RF Branches
10 Node with correct TMA configuration but rfPort set to DISABLED state
11 Node with diplexed lines (L21 & L19) with TMA defined at L21 with no TmaSubUnits for L19
12 Node with incorrect TMA parameters (all set to 0)
13 Node with correct TMA Configuration but TMA HW not providing gain
14 Disabled TmaSubUnits that can be resolved by resetting AntennaNearUnit (TMA HW)

Slide / 11 T-Mobile Confidential

 Case 1 : Non AWS cells mapped to AWS TMA
Non PCS cells mapped to PCS TMA
Non 700 cells mapped to 700 TMA
– Common issue for Style 3 or Style 4 TMAs where TmaSubUnits for AWS and PCS are distinct – refer to Cheat Sheet
– Check the following:
✓ TMA supported Frequency Rx/Tx
✓ TMA Type and the associated TmaSubUnit
Example is SC90322M that was corrected on 9/17/2018
✓ tmaRef for each RF Branch
✓ Needs to reset AntennaNearUnit
✓ No need to bl/deb EutranCells

Slide / 12 T-Mobile Confidential

 Case 2 : Node with defined TMA and Attenuation=0

– Normally due to incorrect scripting

– Suggested troubleshooting process:
✓ Check RFDS for Feeder Type and Length
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology
✓ Change both UL and DL attenuation – based on TMA Set-up, i.e. Style 3 TMA defined at L21 shared with
L19 will have (+) attenuation at L21 and (-) attenuation at L19
✓ Check board level ulGain by using lh ru fui get devstat to make sure the configured attenuations are
working
✓ No need to reset TMA HW or EutranCells

Slide / 13 T-Mobile Confidential

 Case 3 : Node with defined TMA and Negative (-) Attenuation
– Typical issue on Nodes that had been converted to Non MM configurations or due to scripting errors
– Suggested troubleshooting process:
✓ Check latest RFDS and verify site configuration in OSS, i.e., EutranCells, RF Branch 2 connections, etc.
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology
✓ Change both UL and DL attenuation
✓ Check board level ulGain by using lh ru fui get devstat
✓ No need to reset TMA HW or EutranCells

✓ An example is site SC10149A with TMA defined at L21 but ulAttenuation set to (-) values. Correction was done 0n 8/22/2018.

Slide / 14 T-Mobile Confidential

 Case 4 : Node with no TMA defined and TMA physically installed
– Typically flagged as P1 – Hot RSSI
– Check the following:
✓ Check RFDS for latest configuration
✓ Check actual TMA HW installed by creating the TMA MOs, as well as TmaSubUnits & tmaRef
✓ Setting rfPortRef for each AntennaNearUnit may require you to block the SectorEquipmentFunction depending on the RU version
✓ Make sure that the RfPort (A) of the RU that connects to the TMA HW is UNLOCKED
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology
✓ Change both UL and DL attenuation
✓ Re-start AntennaNearUnit MOs
✓ Check board level ulGain by using lh ru fui get devstat
✓ No need to bl/deb EutranCell

– Example is node SC90328M corrected on 2/13/19 and SC90365M corrected on 2/7/19

Slide / 15 T-Mobile Confidential

 Case 5 : Node with Ground Based RRUs but attenuation is 0 or 3

– Common for sites with ground based RRUs that share feeder lines with other
technologies
– Nodes with RRUs at the antenna commonly have 0 or 3 for attenuation
– Check the following:
✓ Check RFDS for latest site configuration and get Feeder Type and Length
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology
✓ Change both UL and DL attenuation
✓ Check board level ulGain by using lh ru fui get devstat
✓ No need to reset TMA HW or EutranCells

B12 RRU at the

Cabinet
ulAttenuation &
dlAttenuation should
not be 3 or 0

Slide / 16 T-Mobile Confidential

 Case 6 : Node converted to AIR but attenuation not set to 0
– Normally flagged as Hot RSSI
– Check the following:
✓ Check RFDS for latest configuration
✓ Change both UL and DL attenuation to 0 after verification that node has been converted to AIR
✓ No need to reset TMA HW or EutranCells
– Example below is node SC07258A, converted to AIR 32 but L19 UL & DL Attenuation not adjusted to 0

Corrected on 1/26

Slide / 17 T-Mobile Confidential

 Case 7 : Node converted to 794ARV2 (Ground Based 794AR V2)
– Normally flagged as Hot RSSI
– L19 used to share Twin Style TMA with 2G/U19 but now shares Style 3 TMA with L21 (TMA defined @ L21) after conversion to RRUS2217B2
– Check the following:
✓ Check RFDS for latest configuration
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology Corrected on 11/01
✓ Set ulAttenuation to – (TMA Gain – Attenuation)
✓ No need to reset TMA HW or EutranCells
– Example below is node SC06970A

Post conversion L19

shares Style 3 TMA with
L21 (-) attenuation

Before conversion Twin

Style TMA defined at L19
(+) attenuation
Slide / 18 T-Mobile Confidential
 Case 8 : Nodes with AntennaNearUnit defined but no TmaSubUnits
– Do the following:
✓ Check RFDS latest site configuration
✓ Check TMA type defined so you can define the correct TmaSubUnits
✓ Assign tmaRef to each RF Branch
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology if you
need to change the attenuation values
✓ Check board level ulGain by using lh ru fui get devstat
✓ Reset TMA HW needed

AntennaNearUnit defined
with no children MO

Slide / 19 T-Mobile Confidential

 Case 9 : Nodes with TMA definition but no assigned tmaRef on RF Branches
– TMA defined and enable but RF Branches are missing tmaRef
– Leads to high RSSI since the RUs do not realize that there is a TMA at the line/antenna
– You may find nodes where only RF Branch 1 has tmaRef or RF Branches that have tmaRef for another AntennaUnitGroup
– Simply set the tmaRef for each RF Branch per sector to the corresponding ANU-TmaSubUnit combo
– Reset the AntennaNearUnit (parent MO of TmaSubUnits) on each sector for the changes to take effect
TMA MOs as well as attenuation are set correctly

Pre settings Post settings

RF Branches have no TMA

visibility since tmaRef for
each RF Branch is blank

Slide / 20 T-Mobile Confidential

 Case 10 : Node with correct TMA configuration but rfPort set to DISABLED state
– Check the following:
✓ Check the AdministrativeState and availabilityStatus of the parent MO of the DISABLED TmaSubUnits
✓ If AdministrativeState is UNLOCKED and availabilityStatus is DEPENDENCY_LOCKED, then check the AdministrativeState of the rfPortRef
✓ Unlock the RfPort of the RU
✓ No need to reset TMA HW or EutranCells

Status of AntennaUnitGroup=2 → MO of TmaSubUnits

Slide / 21 T-Mobile Confidential

 Case 11 : Nodes with L21 &L19 on diplexed lines with Style 4 TMA at L21 but missing TmaSubUnits for L19
– Check the following:
✓ Check RFDS for Feeder Type and Length
✓ Use Feeder Loss and Delay Calculator to get the loss and delay values for each technology
✓ Change both UL and DL attenuation
✓ Check board level ulGain by using lh ru fui get devstat
✓ No need to reset TMA HW or EutranCells

Slide / 22 T-Mobile Confidential

 Case 12 : Node with incorrect TMA parameters (all set to 0)
– TMA specific parameters (dlattenuation, dlTrafficDelay, ulTrafficDelay)
– Settings are
✓ dlAttenuation – 5
✓ ulTrafficDelay - 300
✓ dlTrafficDelay - 150
– Reset AntennaUnitGroup after changing parameters

EMPTY

Slide / 23 T-Mobile Confidential

 Case 13 : Node with correct TMA Configuration but TMA HW not providing gain
– Typically flagged as Hot RSSI
– TMA MOs correctly defined, dependencies are good, attenuation set correctly but node still has high RSSI
– Re-set AntennaUnitGroup on each sector
– Check the board level UL gain to see how the RU is providing the additional gain
Pre re-set of AntennaUnitGroup Post re-set of AntennaUnitGroup

Slide / 24 T-Mobile Confidential

 Case 14 : Disabled TmaSubUnits that can be resolved by re-setting AntennaNearUnit (TMA HW)
– Could possibly be bad TMA HW or RUs not able to power the TMA HW
– Check parent MO for possible dependency issues
– TmaSubUnit dependency is the AntennaNearUnit
– If ANU is fine, then the next level of dependency is the RfPort
– If both dependencies are good, then reset the AntennaNearUnit (TMA HW)

First dependency

Second dependency

avaialabilityStatus of TmaSubUnit

After ANU re-set

Slide / 25 T-Mobile Confidential

 Case 15 : Style 3 on TMA (shared with U19, L21&L19 on AIR 32)
– Common for sites with L21 & L19 that have been converted to AIR 32 but used to share Style 3 TMA with L7
– Causes COLD RSSI if tmaRef is defined at L7 RF Branches
– Check if L7 RUs are ground based, then adjust ul & dl attenuation

Change – L7 has
Ground based RU

Slide / 26 T-Mobile Confidential

 Case 16 : L19 SIMO with ATMA at LTE
– L19 SIMO with TMA defined at L19 and RX2 from RXB_IO of 2G/U19
– Remove tmaRef at L19 RF Branch 2 and apply Golden Feeder for ulAttenuation (-168)
– Commonly not flagged as RSSI or SINR issue but imbalances of > 6dB between RF Branches

Change – L7 has
Ground based RU

Slide / 27 T-Mobile Confidential