Brief Overview AAS Radio Systems

Brief Overview
AAS Radio Systems

Layers, Transmission Modes, Performance ….
2018-07-03
2018-07-05 | Commercial in confidence | Page 1
Overview
— Review of AAS concepts and operation
— Deep dive into performance of some cells
— Recommendations for performance monitoring

Review of AAS concepts
and operation
LTE Transmission Modes in 3GPP
Downlink Multiple Antenna Transmission Modes
— The TDD LTE AAS introduces TM8 for beamforming

— This PPT investigates transmission mode performance from two active cells with commercial traffic
Rel-8 — TM2 Transmit diversity ”Legacy” LTE

— TM3 Open Loop Spatial Multiplexing transmission modes
— TM4 Closed loop spatial multiplexing
— TM5 Codebook based MU-MIMO
— TM6 Rank-1 closed loop spatial multiplexing
— TM7 Single layer transmission (only for TDD)
Rel-9 — TM8 Dual layer transmission (TDD, FDD optional)

UE-specific
— MU-MIMO possible (reciprocity based)
reference signals
— Possible for 1 and 2 Layer transmissions
for demodulation
Spatial Multiplexing
2x2 Data Transmissions 𝑤11 Antenna port 0
𝑾= 𝑤
12 Antenna port 1
Codeword 1
IQ IQ
Layer 1
codeword
ഥ w11 w12
𝑿 ഥ =𝑾∙𝑿
ഥ
𝒀
𝑤11 𝑤21 Antenna port 0
𝑾= 𝑤
Layer 2
codeword
12 𝑤22 Antenna port 1
w21 w22
Codeword 1 Codeword 2
— Weights determine the directionality of each antenna’s beam

— For Rank 1 (eg Tx diversity), the Layer 2 (red) path is not applicable
LTE Transmission Modes
— The AAS can transmit using a number of modes

— Transmit diversity (TM2 - 1 layer)
— Open Loop MIMO Rank 1 (TM3 - 1 layer)
— Open Loop MIMO Rank 2 (TM3 - 2 layer)
— Beamformed Rank 1 (TM8 - 1 layer)
— Beamformed Rank 2 (TM8 - 2 layer)
— TM8 beamforming introduces additional Reference Symbol 14 REs
overheads (DM-RS) which reduces the peak throughput
12 sub-carriers
— For CFI3 TM8 as 10% less REs available for PDSCH
than does TM3
— The TM8 beamformed PDCCH will have a better SINR
which can lead to higher throughputs than TM3/TM2 at
medium to low SINR
RS0 RS1
PDCCH PDSCH PDCCH or PDSCH based on CFI
R7 & R8 UE-specific (DM-RS)
AAS Cell Coverage
— Broadcast beam defines the cell coverage
— RSRP and SINR measurements (in TM3 and TM8) are

based on the Reference Symbols transmitted on the
broadcast beam
— In TM8 mode the PDSCH is transmitted on the traffic beam

— Data can be transmitted using 1 or 2 layers Traffic beam
— TM8 uses additional demodulation RS (DMRS) which
are transmitted on the traffic beam
— In TM3 mode the PDSCH is transmitted using the Broadcast beam

broadcast beam pattern

AAS Macro Cell Shape Macro Broadcast Beam
3D Pattern
Antenna Beam Patterns Electrical tilt = 8°
— Reference Symbols and Control Channels transmitted on

the broadcast beam
— UEs with an SRS resource will receive TM8 transmissions on

a beamformed Traffic beam
— Traffic beam falls within the Traffic Beam Envelope
— UEs without an SRS resource will receive TM3

transmissions on the broadcast beam
— MU-MIMO is not possible on TM3 transmissions
Spatial characteristics of beam Macro Traffic – TM8 Traffic - TM3
EIRP max per broadcast beam 2 x 64.5 dBm 2 x 71.5 dBm 2 x 64.5 dBm
Horizontal pattern, HPBW 65 ± 5° 12 ± 3° 65 ± 5°
Vertical pattern, HPBW 10 ± 1° 10 ± 1° 10 ± 1°
Digital downtilt
2018-07-05 | Commercial in confidence | Page 8 -8° to +8° n/a n/a
AAS Antenna Beam Examples
AIR6468 Band 42 Horizontal Vertical
Macro Broadcast Beam, Vtilt= 8
Scenario: Macro Beam
Parameter BrM1, BrM2
Vertical Beamwidth 10±1
Horizontal beamwidth 65±5
Digital downtilt [-8,8]
Vertical beam pointing error ≤1
Horizontal beam pointing 0±5
EIRP (max) 2x64.5 dBm
Vertical side lobe suppression 16 dB
Front to back ratio 25 dB
Beam parallellity (BrM1•BrM2) ≤-10 dB
Traffic Beam, Htilt=0,Vtilt= 3
Uniform traffic beams Direction

Parameter H0 V3 deg H55 V3 deg H0 V18 deg
Vertical Beamwidth 9.5 9.5 10
Horizontal beamwidth 12 22 12
Minimum peak EIRP 2x71.5 dBm 2x68 dBm 2x70 dBm

DL MU-MIMO
Intra-Cell Interference A
B
— An increased number of MU-MIMO users increases the
interference between users/layers
— Since power is shared by the co-scheduled layers the
power per layer reduces as the number of users MU-
MIMO increases EIRP
— SINR reduces as the number of MU-MIMO co-scheduled
users increases A B
SINR
Frequency reuse
(MU-MIMO)
SINR q
(MCS per MIMO layer)
Interference from B into A
Typically # layers
~8 layers
Antenna Pattern
Multiple Traffic Beams Horizontal Pattern
Single Traffic Single Traffic beam

beam uses all uses all available
available power power
For two Traffic For five Traffic beams

beams the EIRP the EIRP per beam is
per beam is reduced by 7dB
reduced by 3dB
The grating lobes of
the ±60° Traffic
beams can be seen in
this graph

TM3 Transmissions
Impact of CFI on Maximum Throughput RS0 RS1 RS2 RS3
PDCCH PDSCH PDCCH or PDSCH based on CFI
14 REs
12 sub-carriers
MCS Modulation TBS Physical Resource Blocks (RB)
Index Index
TBS 1 2 .. 50 .. 100
0 QPSK 0
0 16 32 1384 2792
15 16QAM 14
14 256 552 14112 28336
27 64QAM 25
28 64QAM 26
25 616 1256 31704 63776 2 Tx antenna – CFI = 1 4 Tx antenna – CFI = 1
26 712 1480 36696 75376
1 RB = 144 RE for PDSCH 1 RB = 136 RE for PDSCH
L1 Peak Throughput – 2 layers 100 RB = 14,400 REs 100 RB = 13,600 REs

75,376 x 2 x 0.74 = 111.6 Mbps Coding rate ≈ [75376+24] / [14400x6] ≈ 0.87 Coding rate ≈ [75376+24] / [13600x6] ≈ 0.92
Peak rates use MCS 28
64QAM Modulation & MIMO
Transmission 2 Tx antenna – CFI = 2 4 Tx antenna – CFI = 2
1 RB = 132 RE for PDSCH 1 RB = 128 RE for PDSCH
L1 Peak Throughput – 2 layers 100 RB = 13,200 REs 100 RB = 12,800 REs


CFI3
CFI2
TM8 Transmissions CFI1 14 REs
Impact of DMRS & CFI on Peak Throughputs
12 sub-carriers
— TM8 introduces DMRS to assist with the UE with demodulation of the
beamformed PDSCH
— The PDSCH and DMRS are transmitted on the traffic beam
— The DMRS reduces the RE available for PDSCH limiting the peak rate RS0 RS1
— The UE does not demodulate a coding rate > 0.93 PDCCH PDSCH PDCCH or PDSCH based on CFI
R7 & R8 UE-specific (DM-RS)

3GPP TS 36.211 V12.2.0 (2014-06)
2 Tx antenna – CFI = 1 (shown above)

MCS Mod TBS Physical Resource Blocks 1 RB = 132 RE for PDSCH → 100 RB = 13,200 REs L1 Peak Throughput – 2 layers
Index Index 75,376 x 2 x 0.74 = 111.6 Mbps
TBS 26 ≈ [75376+24] / [13200x6] Coding rate ≈ 0.95
TBS 1 . 50 . 100
0 QPSK 0 TBS 25 ≈ [63776+24] / [13200x6] Coding rate ≈ 0.81 63,776 x 2 x 0.74 = 94.4 Mbps
0 16 1384 2792
2 Tx antenna – CFI = 2
15 16QAM 14
1 RB = 108 RE for PDSCH → 100 RB = 12,000 REs L1 Peak Throughput – 2 layers
23 552 28336 57336
TBS 26 ≈ [75376+24] / [12000x6] Coding rate ≈ 1.04 75,376 x 2 x 0.74 = 111.6 Mbps
24 584 30576 61664
27 64QAM 25
25 616 31704 63776
28 64QAM 26
26 712 36696 75376 2 Tx antenna – CFI = 3
1 RB = 108 RE for PDSCH → 100 RB = 10,800 REs L1 Peak Throughput – 2 layers
Peak rates use MCS 28
Bits / TTI
64QAM Modulation
2018-07-05 | Commercial in confidence& | Page 14 TBS 23 ≈ [57336+24] / [10800x6] Coding rate ≈ 0.88 57,336 x 2 x 0.74 = 84.9 Mbps
MIMO Transmission
Transmission Modes
Scheduling SU-MIMO & MU-MIMO
The following applies when a cell is configured for TM8 transmissions and
transmission mode switching is not activated >15°
— The eNB checks the UE pairs with data in the buffer for beam-weight
orthogonality and the assignment of SRS resources >15°
— If MU-MIMO is not required for “capacity” reasons and the UEs have SRS >15°
resources assigned then the data is scheduled as TM8 Dual Layer
— The eNB “estimates” the beam weights for the other polarization
— If MU-MIMO is required for “capacity” reasons and the UEs have SRS resources
UEs need angular separation in order to be
then the data is scheduled as TM8 Single Layer scheduled for MU-MIMO, otherwise there
— The UEs co-scheduled on the same PRB/TTI resources have different beam weights would be “traffic beam overlap” leading to
applied to the transmissions of the PDSCH and DMRS high levels of intra-cell interference.
— If the UEs don’t have SRS resources assigned then data is transmitted as TM3
— TM3 and TM8 can’t be scheduled in the same TTI

• Note: This is an extremely high level description of the scheduling process
Example of AAS Sites
Transmission Formats AAS AAS
SRS configured UEs with angular separation in a UEs in an AAS cell which is not configured
cell requiring MU-MIMO for capacity may be co- for TM8 beamforming will receive DL
scheduled on the same TTI/PRB resources. These transmissions in TM3 MIMO or Tx Diversity.
UEs will equally share the power available for The UEs will share the PRBs &/or TTIs.
PDSCH and DMRS REs and will have orthogonal
beam-weights applied to their transmissions.
AAS
Non-AAS
UEs in a non-AAS cell will receive DL
transmissions in TM3 MIMO or Tx Diversity. A UE in a AAS cell configured for TM8 which does not required
MU-MIMO transmissions for “capacity” reasons will have data
scheduled in TM8 Dual Layer (provided there is sufficient data to
required 2 layers and the SINR is high enough for 2 layer
transmission, otherwise TM8 Single Layer will be used).
Demonstrating Peak Throughput
Maximizing MU-MIMO Performance
— How to demonstrate the maximum MU-MIMO capabilities for showcase demos
— UEs are separated so that the angular separation between the UEs is ≥ the half power
beamwidth of the traffic beam
— Ideally an single cell scenario is used do UEs wont connect to another sector of the same Front view
site
Side view
— Distance between BTS and UEs is very small >10°

>15°
(usually less than ~120m)
>10°
>10°

UE8
196m 107°
152m 121°
UE6
UE7
166m 117°
UE5
147m 126°
UE3
89m 93°
UE2
85m 113°
UE Number TM3 – MU- TM8 – MU- UE4
MIMO OFF MIMO ON 85m 173°
1 13 45 UE1
2 15 42 47m 150°
3 14 45
4 12 45
5 15 40
6 13 46 AAS
7 13 42
8 15 45
Total 110 Mbps 351 Mbps
Cell Performance
Monitoring
Throughput - Experience
Reliability of Throughput
measurement to show potential
Throughput for a user
Very small burst like TCP ACKs and 32B Pings etc.
How is throughput measured for a 54B Ping that is
sent in 1 TTI ?
- 432 Kilobits/s?
Samples from this traffic

makes a measurement
result hard to interpret.
Larger burst, like 1MB
Medium burst, Facebook download etc.
updates etc that fits in
2→15~20 TTIs
Samples from this traffic
is well representative for
potential Throughput for
a user.

Burst Size
DL Definitions
User Throughput & Cell Throughput
Successful transmission,
buffer not empty
pmPdcpLatTimeDl pmUeThpTime
Failed transmission (”Block
The last TTI with data
error”)
shall always be
Successful transmission, removed. This since the
buffer empty coding can be selected
based on size, not radio
No transmission, buffer not conditions, hence not
empty (e.g. due to contention) end-user impacting.
Data arrives to First data is Time (ms)

empty DL buffer The send buffer is
transmitted to the UE
again empty
pmPdcpVolDlDrb = Σ + pmPdcpVolDlDrbLastTTI = Σ
pmUeThpTimeDl = count ( , ) pmSchedActivityCellDl = count ( , , )
DL User Throughput KPI = (pmPdcpVolDlDrb – pmPdcpVolDlDrbLastTTI) / pmUeThpTimeDl [Mbps]

DL Cell Throughput KPI = pmPdcpVolDlDrb / pmSchedActivityCellDl [Mbps]
UL Definitions
User Throughput & Cell Throughput
Successful transmission, buffer not empty
First 4 receptions removed
Receptions excluded from Throughput Calculations
Time and Vol used The last TTI with data
Failed transmission (”Block error”) for calculation shall always be
removed. This since the
Successful transmission, buffer empty coding can be selected
based on size, not radio
No transmission, buffer not conditions, hence not
empty (e.g. due to contention) end-user impacting.
Data arrives to
Grant sent to UE Time (ms)
empty UL buffer First data is The send buffer is
Scheduler request transmitted to the eNB again empty
sent to eNB
pmUeThpVolUl = Σ pmPdcpVolUlDrb = Σ + +
pmUeThpTimeUl = count ( , ) pmSchedActivityCellUl = count ( , , , )
UL User Throughput KPI = pmUeThpVolUl / pmUeThpTimeUl [Mbps]

UL Cell Throughput KPI = pmPdcpVolUlDrb / pmSchedActivityCellUl [Mbps]
Cell Deep Dive
Cell with Busy Hour ~40 RRC Connected Users
— Cell B48752
— Date: Friday 29/06/2018, hourly data
— Busy hour RRC Connected Users ≈ 40 users
— DL Cell throughput > 30 Mbps
— DL UE throughput generally ~ 10 Mbps
— At 20:00 dropped to around 6 Mbps
— Max RRC Connected Users close to average
Counters
Ave RRC Conn User = EUtranCellTDD.pmRrcConnLevSum / EUtranCellTDD.pmRrcConnLevSamp

Max RRC Conn User = EUtranCellTDD.pmRrcConnMax
DL UE Tput = (EUtranCellTDD.pmPdcpVolDlDrb - EUtranCellTDD.pmPdcpVolDlDrbLastTTI)/EUtranCellTDD.pmUeThpTimeDl
DL Cell Tput = EUtranCellTDD.pmPdcpVolDlDrb / EUtranCellTDD.pmSchedActivityCellDl
Cell Deep Dive
Cell DL Active Users
— Busy hour RRC Connected Users ≈ 40 users
— DL Cell throughput > 30 Mbps
— DL Active users is the number of users will data in

the buffer
Counters
Ave DL Active UE = EUtranCellTDD.pmActiveUeDlSum / (min(720000,EUtranCellTDD.pmSchedActivityCellDl))

DL UE Tput = (EUtranCellTDD.pmPdcpVolDlDrb - EUtranCellTDD.pmPdcpVolDlDrbLastTTI)/EUtranCellTDD.pmUeThpTimeDl
DL Cell Tput = EUtranCellTDD.pmPdcpVolDlDrb / EUtranCellTDD.pmSchedActivityCellDl
Note:720000 = max DL TTI for TDD Frame config 2 in a 15 min ROP
Cell Deep Dive
Data Volume
— DL data volume transmitted peaks at about 14 GB in

the busiest hours
— UL data volume is < 800 MB at this time
— A general “rule of thumb” is that the ratio DL:UL

volume will be between 8 and 12 for TCP traffic
— A high ratio of DL:UL volume, here peaking at close to

30, indicates applications optimized for DL
throughput (most likely video streaming)
Counters
DL Vol (GB) = EUtranCellTDD.pmPdcpVolDlDrb/8000000

UL Vol (GB) = EUtranCellTDD.pmPdcpVolUlDrb/8000000
Ratio DL to UL Vol = DL Vol / UL Vol
YouTube Video Streaming
Comparison of Different Video Quality Data Volume vs Time - 1.04 min Youtube 360p Video
5.0
4.5
Cumulative Data Volume [MB]

4.0
— The video was 1.04 min in duration, streamed on a commercial mobile 3.5
3.0
network 2.5
2.0
— The Chrome browser was used and the protocol used in the video stream 1.5
1.0
was QUIC (Quick UDP Internet Connections, pronounced quick) which is an 0.5
experimental transport layer network protocol designed by at Google 0.0
0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75
Elapsed Time [Sec]
— Total data volume for 360p
Inbound 4.66 MB, Data Volume vs Time - 1.04 min Youtube 1080p Video
24
Outbound 198.5 kB 22
Ratio DL:UL 23.5
Cumulative Data Volume [MB]

20
18
16
— Total data volume for 1080p 14
12
Inbound 22.88 MB 10
Outbound 748 kB 8
6
Ratio DL:UL 30.6 4
2
0
0 5 10 15 20 25 30 35 40 45 50 55 60 65 70
2018-07-05 | Commercial in confidence | Page 27 Elapsed Time [sec]
Cell Deep Dive
DL Throughput – Last TTI
— A relatively high proportion of the DL throughput Data in Last TTI Counter

volume is considered “Last TTI”
— This means that when it is transmitted to the UE it

empties the buffer
— This volume (and transmit time) will not contribute to

the DL UE throughput KPI calculation
— Looking at some later some later stats it is possible to

estimate potential throughput for these UEs served in
the last TTI
Counters
Percent Last TTI Util = EUtranCellTDD.pmPdcpVolDlDrbLastTTI / EUtranCellTDD.pmPdcpVolDlDrb

Cell Deep Dive
DL Air Interface Resource Utilization
— Observation about the air interface utilization
— Firstly the TTIs are utilized

— Then the number of PRBs used increases
— Then the “PRB utilization” increases; a value above 100%
indicates that PRBs are being used for ≥ 2 layers
— During hour of lowest throughput not all PRBs were used;

potentially due to
— Short period of demand (not spread over whole hour)
— Possibly UEs in poorer coverage demanding more resources
Counters
Percent DL TTI Util = min(720000, pmSchedActivityCellDl)/720000

Percent DL PRB Used = ΣpmPrbUsedMimoLayersDlDistr[x])/pmPrbAvailDl
Percent DL PRB Util = Σ(x+1)*pmPrbUsedMimoLayersDlDistr[x])/pmPrbAvailDl
Note:720000 = max DL TTI for TDD Frame config 2 in a 15 min ROP
Cell Deep Dive
A Quiet Cell
— Max 18 RRC Connected Users

— DL User Throughput is close to Cell throughput in the busy
hours
— Only about 40% of RE’s used
— ~60% of traffic volume not included in UE Throughput
counter
Data in Last TTI Counter

Cell Deep Dive
DL Layers
— Cell was configured for a maximum of 4 DL Layers
— During peak hours there was some 3 and 4 Layer

transmissions indicating MU-MIMO operation
— 2 Layer operation may be:

— SU-MIMO dual layer to a single UE, or
— MU-MIMO single layer to 2 UEs
Counters
Layer1 = EUtranCellTDD.pmPrbUsedMimoLayersDlDistr[0]
Cell Deep Dive
DL Transmission Modes
— Transmission mode was mainly TM8 Rank 1 –

SU-MIMO
— Used for single UE Tx diversity or MU-MIMO
scheduling
— TM8 Rank 2 reports are high, up to 50% during

the quiet hours indicating SU-MIMO dual layer
operation
— Some TM3 and TM2 indicating a small number of

UEs don’t have SRS resources available
Counters
Tm2 = EUtranCellTDD.pmRadioTxRankDistr[0]
Tm3_Rank1 = EUtranCellTDD.pmRadioTxRankDistr[1]
Mapping CQI to SINR
Values Based on Field Testing from a Network
Typical mappings This is a typical mapping of CQI to SINR based
CQI index SINR [dB] on field test of an early LTE terminal.
0 out of range
1 -7.23 Chipset manufacturers can have different
2 -5.48 mapping as this mapping is not standardized.
3 -3.43
4 -1.37
5 0.55
6 2.47
7 4.58 Example CQI stats for a FDD three
8 6.39 sector site in a MBB network
9 8.34
10 10.44
11 12.39
12 14.15
13 16.02
14 17.61
15 18.95
Cell Deep Dive
UE CQI Reports
— UE CQI reports provide an indication of DL

channel quality
— The exact CQI to DL SINR translation is not

standardized
— This allows UE vendor differentiation
— The common lookup has been used to convert the

CQI to a DL SINR dB
— Percentile values have been taken from the PDF

counters
— 90th percentile and average CQI are good,

Counters
however 10th percentile shows some low values
indicating users in poor SINR locations CQI1 = EUtranCellTDD.pmRadioUeRepCqiDistr [0 .. 15]
CQI2 = EUtranCellTDD.pmRadioUeRepCqiDistr2 [0 .. 15]
Cell Deep Dive
UE CQI Reports
Entel Massive MIMO cell
— Comparison provided of Entel network CQI

values compared to a TM3 FWA cell in another
network
— Entel TM8 (beamforming) network shows improved

SINR for CQI1 indicating benefits of SU-MIMO
transmissions with beamforming
— TM3 network shows CQI1 and CQI2 almost the same

value
Traditional TM3 FWA cell

Cell Deep Dive
Data Bits per Resource Element
Entel Massive MIMO cell
— The top graph shows the number of data bits per

Resource Element
— Provides an indication as to the radio quality and is

linked to CQI reporting
— Bits per RE can be used to estimate throughput

potential
— Scheduling Entities per TTI indicates the number of

simultaneously scheduled users per TTI
Counters
Traditional TM3 FWA cell
DL Bits Per RE = EUtranCellTDD.pmRadioThpVolDl / EUtranCellTDD.pmRadioThpResDl
UL Bits Per RE = EUtranCellTDD.pmRadioThpVolUl / EUtranCellTDD.pmRadioThpResUl

Cell Deep Dive 64QAM
Modulation Format
— The UE CQI reports are used to determine the MCS that the
BTS uses to transmit to the UE 16QAM
— An average of 3 bits per RE indicates 64QAM modulation is
used on average which matches the modulation format QPSK
indicator from the counters
— For TM8 CFI3 there are 10,800 REs in 100 RB CQI index modulation code rate x 1024 efficiency
0 out of range
— So potential TM8 Rank 2 transmission at 3 bits/RE is: 1 QPSK 78 0.1523
2 QPSK 120 0.2344
2 x 10,800 x 3 = 64,800 bits in 1 ms 3 QPSK 193 0.3770
4 QPSK 308 0.6016
5 QPSK 449 0.8770
6 QPSK 602 1.1758
7 16QAM 378 1.4766
Counters 8 16QAM 490 1.9141
9 16QAM 616 2.4063
QPSK = EUtranCellTDD. pmMacHarqDlAckQpsk
10 64QAM 466 2.7305
16 QAM = EUtranCellTDD. pmMacHarqDlAck16qam 11 64QAM 567 3.3223
64 QAM = EUtranCellTDD. pmMacHarqDlAck64qam 12 64QAM 666 3.9023
13 64QAM 772 4.5234
According to 3GPP TS 36.213 a CQI of 10 maps to a code rate of 466 or an efficiency of 14 64QAM 873 5.1152
2.7305, while a CQI of 11 maps to a code rate of 567 or an efficiency of 3.3223. 15 64QAM 948 5.5547
It should be noted however, that CQI calculation may vary from different UE vendors.
Cell Deep Dive
PDCCH CFI Format
— The PDCCH CFI format indicates the number of symbols

(CFI value) that are required for PDCCH signaling
— If more symbols are required for PDCCH then less are

available for PDSCH data
— A higher PDCCH allocation will limit peak throughputs
— More PDCCH resources are required when MU-MIMO is

scheduled, are more users are scheduled in each PRB
Counters
Percent PDCCH CFI1 = EUtranCellTDD.pmPdcchCfiUtil[0]/ Σ EUtranCellTDD.pmPdcchCfiUtil[x]

Cell Deep Dive
UL RSSI Counters
— UL RSSI counters can be used to find cells experiencing

UL interference
— A basic wideband counter is available
— PUCCH RSSI counters can be used to identify issues on

the UL control channel
— Subframe counters are useful in TDD LTE for identifying

Cross Link Interference (CLI)
— CLI is DL BTS transmissions interfering with co-channel
BTS UL due to propagation delays

Cell Deep Dive
UL RSSI PRB Counters
— UL PRB counters are also useful in identifying issues
pmRadioRecInterferencePwrPrb0 … 99

Cell Deep Dive
UL RSSI Counters
— Wide band measurements – one sample every 1ms placed into the PDF bin ranges shown, a weighted average
is taken using a linear value for the bin ranges
— RSSI_WAve = 10*log10(WeightedAverage(EUtranCellTDD.pmRadioRecInterferencePwr,[Linear Bin Ranges]) / 1000000000000)

— RSSI_WAve_PUCCH = 10*log10(WeightedAverage(EUtranCellTDD.pmRadioRecInterferencePwrPucch,[Linear Bin Ranges]/ 1000000000000)
— Linear Bin Ranges = [0.39716,0.89716,1.12946,1.42191,1.79008,2.25357,2.83708,3.57167,4.49647,5.66072,11.07925,27.82982,69.90536,175.59432,441.07,1107.92]
— Sub frame measurements – one sample taken every 1ms and the power level placed in an accumulation counter.
The accumulation value is in pW (1 x 10-9) with 90,000 samples taken in a 15 minute measurement period. Counters are
available for all possible UL subframes.
— RSSI_SF = 10*log10(((EUtranCellTDD.pmRadioRecInterferencePwrSf1))/(EUtranCellTDD. pmRadioRecInterferencePwrSfSamp*1000000000))
— PRB measurements – one sample taken every 40ms for each PRB and the power level placed in an accumulation counter for
each PRB. The PRB counters are numbered 0 to 99. The unit of the counter is 1 mW * 2^(-44).
— pmRadioRecInterferencePwrPrb0 .. 99

Cell Deep Dive
UL Pathloss Counters
— UL pathloss counters can be used to estimate UE locations

UL Pathloss Estimate
within the cell based on pathloss
— PDF counter is incremented for each UE scheduled in the UL
— Pathloss estimate is based on UE max Tx power, power

headroom reports, PRB assignment in the UL and received
power
— The counter can then be used to estimate the DL RSRP for

UEs
— For a 2 x 40W cell the RSRP EIRP is ~ 31 dBm
— Power per RS is 15 dBm + 16 dBi broadcast beam
— Ave RSRP at UE location is 31 dBm – 115 dB = -86 dBm Counters
PL Counter =EUtranCellTDD.pmUlPathlossDistr[0 .. 20]

20 bin ranges in 5 dB steps from 50 dB to 145 dB
Very Busy Cell Review – C28082



Data in Last TTI Counter

Conclusion
— When considering performance it is important evaluate a number of indicators
— Considerations are:
— Number of RRC Connected and Active users
— Air interface utilization - TTIs, PRBs, Layers
— UE radio conditions (SINR, pathloss/signal strength ….)
— Interference levels – DL and UL
— Monitor throughput – primarily cell level
— Other FWA networks monitored for:

— RRC Connected users (control), Active users (measure) & Cell Throughput (measure)
— Dimensioning Users to cells is vital for guaranteeing performance in FWA networks

— Ensuring that the number of users is controlled
— User spread is important for maximizing AAS capability
— Interference control is a key to maximizing end user performance

Brief Overview AAS Radio Systems

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Brief Overview AAS Radio Systems

Загружено:

Авторское право:

Доступные форматы

Brief Overview

AAS Radio Systems

— Review of AAS concepts and operation

— Deep dive into performance of some cells

— Recommendations for performance monitoring

2018-07-05 | Commercial in confidence | Page 2

— The TDD LTE AAS introduces TM8 for beamforming

Rel-8 — TM2 Transmit diversity ”Legacy” LTE

Rel-9 — TM8 Dual layer transmission (TDD, FDD optional)

— Weights determine the directionality of each antenna’s beam

— The AAS can transmit using a number of modes

— TM8 beamforming introduces additional Reference Symbol 14 REs

overheads (DM-RS) which reduces the peak throughput

— Broadcast beam defines the cell coverage

— RSRP and SINR measurements (in TM3 and TM8) are

— In TM8 mode the PDSCH is transmitted on the traffic beam

— In TM3 mode the PDSCH is transmitted using the Broadcast beam

2018-07-05 | Commercial in confidence | Page 7

Antenna Beam Patterns Electrical tilt = 8°

— Reference Symbols and Control Channels transmitted on

— UEs with an SRS resource will receive TM8 transmissions on

— UEs without an SRS resource will receive TM3

Spatial characteristics of beam Macro Traffic – TM8 Traffic - TM3

Horizontal pattern, HPBW 65 ± 5° 12 ± 3° 65 ± 5°

Vertical pattern, HPBW 10 ± 1° 10 ± 1° 10 ± 1°

Uniform traffic beams Direction

2018-07-05 | Commercial in confidence | Page 9

Single Traffic Single Traffic beam

For two Traffic For five Traffic beams

2018-07-05 | Commercial in confidence | Page 12

PDCCH PDSCH PDCCH or PDSCH based on CFI

L1 Peak Throughput – 2 layers 100 RB = 14,400 REs 100 RB = 13,600 REs

L1 Peak Throughput – 2 layers 100 RB = 13,200 REs 100 RB = 12,800 REs

2018-07-05 | Commercial in confidence | Page 13

TM8 Transmissions CFI1 14 REs

Impact of DMRS & CFI on Peak Throughputs

R7 & R8 UE-specific (DM-RS)

2 Tx antenna – CFI = 1 (shown above)

— TM3 and TM8 can’t be scheduled in the same TTI

— Distance between BTS and UEs is very small >10°

2018-07-05 | Commercial in confidence | Page 17

Samples from this traffic

2018-07-05 | Commercial in confidence | Page 21

Data arrives to First data is Time (ms)

DL User Throughput KPI = (pmPdcpVolDlDrb – pmPdcpVolDlDrbLastTTI) / pmUeThpTimeDl [Mbps]

UL User Throughput KPI = pmUeThpVolUl / pmUeThpTimeUl [Mbps]

Ave RRC Conn User = EUtranCellTDD.pmRrcConnLevSum / EUtranCellTDD.pmRrcConnLevSamp

— Busy hour RRC Connected Users ≈ 40 users

— DL Cell throughput > 30 Mbps

— DL Active users is the number of users will data in

Ave DL Active UE = EUtranCellTDD.pmActiveUeDlSum / (min(720000,EUtranCellTDD.pmSchedActivityCellDl))

— DL data volume transmitted peaks at about 14 GB in

— UL data volume is < 800 MB at this time

— A general “rule of thumb” is that the ratio DL:UL

— A high ratio of DL:UL volume, here peaking at close to

DL Vol (GB) = EUtranCellTDD.pmPdcpVolDlDrb/8000000

Cumulative Data Volume [MB]

Cumulative Data Volume [MB]

— A relatively high proportion of the DL throughput Data in Last TTI Counter

— This means that when it is transmitted to the UE it

— This volume (and transmit time) will not contribute to

— Looking at some later some later stats it is possible to

Percent Last TTI Util = EUtranCellTDD.pmPdcpVolDlDrbLastTTI / EUtranCellTDD.pmPdcpVolDlDrb

— Observation about the air interface utilization

— RSSI_SF = 10log10(((EUtranCellTDD.pmRadioRecInterferencePwrSf1))/(EUtranCellTDD. pmRadioRecInterferencePwrSfSamp1000000000))