Professional Documents
Culture Documents
Multi Beam
Antennas Planning-
Limitations &
Solutions
Wireless Network
Engineering
August 2015
I. Introduction 3
II. After Upgrade Coverage Gaps 3
Antenna Azimuth Plans 4
Coverage holes with twin beam antennas 4
Coverage holes with Tri beam antenna 4
Coverage holes with a twin beam surrounded by 3 sectored sites 4
III. PCI Planning 5
Background 5
LTE Air Interface 5
The Resource Block (RB) 5
Why PCI mod 3? 6
Reference Signals-RS Vs. Users Traffic 6
The Physical Cell Identity (PCI) 6
Intra site PCI v-shift planning 7
Problem Description 7
Possible 6-sectors Sites arrangements 7
Possible 9-sectors Sites arrangements 7
Inter site PCI v-shift planning 8
LTE-FDD case 8
Current Networks Situations 8
C-RAN case 8
PCI-vshift neighbors plan for tessellation deployments 8
IV. Multi beam antennas and Neighbor lists Limitations 9
Background 9
Neighbors’ limitations in 3GPP 9
SIB11 limitations and 3GPP releases (Idle mode) 10
SIB11 dimensioning 10
SIB11 Calculations 10
SIB11 example 11
3GPP releases Solution 11
Vendors Proprietary Solutions 11
Multi Carrier Vs Multi Beam expansions 11
Expansion types 11
Neighbor lists load calculations 11
Automatic Neighbor Relations (ANR) 12
Historical 12
LTE case 13
V. Conclusion 13
VI. References 13
2
I. Introduction
As mobile data traffic continues to rise, there are three main dimensions to expand networks’
capacities: Sites’ densification, Additional spectrum and efficiency enhancements by
technology upgrades. While the second and third dimensions are costly, operators tend more
to densify their networks infrastructures. In mature networks, densification is achievable by a
number of techniques, such as small cells and macro sectors addition. While the latter is easier
to impellent, it faces interference risks as a result of sectors overlap.
1
Two single beam Vs. twin beam antenna overlap
The Multi beam antennas add instantaneous cost efficient capacity, eliminating the need
for new spectrum and sites build, in a minimized overlap pattern design. In this application
note we highlight some of the major challenges and concerns with Multi Beam Antennas
deployment, together with recommended solutions.
For maintaining beam bores (Inherited Beam Azimuth), a slight change in the new antenna
panel bore is made, such that one of its twin beams inherits the former single beam’s direction.
This deployment might be appealing for adding capacity with minimal disruptions.
3
Coverage holes with twin beam antennas
As a result of deploying dual beam antennas with “Inherited Beam Azimuth”, some coverage
gaps might arise. Rotating ALL sectors by 20 o, for the twin beam antennas case, solves this
problem as shown below.
10o
In case of “Inherited Panel Azimuth” antenna upgrade, below right figure, no sectors are
shooting at each other but 3 null areas are created.
4
Inherited Beam Azimuth Swap Inherited Panel Azimuth Swap
The first arrangement (Inherited Beam Azimuth) is thus recommended, after necessary tilts
adjustments, to overcome the direct shooting bores.
Background
LTE Air Interface
To better understand the PCI planning concerns, let us remind ourselves with the LTE radio frame
structure
Now the system needs to insert Cell Reference Signals (RS) into fixed predetermined Time
(symbol) and Frequency (subcarrier) locations. These are marked in red in the following
diagram; depicting a system with 1 antenna port.
Notice that
• Time locations are at symbols 0 and 4.
• Frequency locations depend on v and v-shift.
5
v-Shift is used to shift the RS frequency allocations between neighboring sectors, reducing
interference.
The v-shift = PCI mod 6 for systems with 1 antenna port (v+0 to v+5)
= PCI mod 3 for systems with 2 or 4 antenna ports (v+0 to v+2)
Where PCI is Physical Cell Identity (to be discussed in a while).
This shows 168 groups (Sites) with 3 sectors per Site (group) such that each sector has unique
PCI mod3. For example the highlighted Group1 has sectors PCI = 3, 4 and 5.
6
Two arrangements are further proposed for better PCI spreading, preserving mod3 uniqueness
between sectors
The PCI ID (0 to 2) is used to derive the Primary Sync Sequence and the PCI Group is used to
derive the Secondary Sync Sequence (0 to 167).
The figure below shows possible arrangements of assigning 2 PCI groups to each site.
The sector color indicates same PCI group and the numbers reflect PCImod3 v-shift values…
7
Inter site PCI v-shift planning
Further to the v-shift planning for the same site’s sectors, some concerns were raised for possible
conflicts between neighboring sites as well, especially in the 9 sectored sites cases.
LTE-FDD case
The LTE-FDD neighboring sites are not phase synchronized. Consequently the OFDM symbols
0 and 4, carrying the Reference Signal (RS), won’t be in sync and have much less chances to
collide in the neighbor sites v-shift conflicts’ case.
In the example shown in figure above, Site1 SectorA and Site2 SectorC have the same PCI
v-shift values and are direct neighbors. Since they are not phase synchronized, Symbol 0 of
Site1-A lands on Symbol 5 of Site2-C. Chances to land on the same OFDM symbol are much
less in this case. As a result, PCI v-shift planning will be more useful for the same site’s sectors,
which are in exact phase sync.
C-RAN case
With the C-RAN concept, Baseband units (BBU) are centralized as a shared pool resource
for their connected Remote Radio Units (RRU). Not only will such concept improve hardware
utilization efficiency, it also enables some of the long anticipated LTE-A features, such as the DL
COMP. Here, C-RAN deployments will imply neighboring RRUs synchronization, as if they are
from the same base station. Eventually, PCI-vshift planning for neighbors might be then required
as follows next.
8
With such a distribution, using arrangement #4 pattern, direct neighbors are not conflicting
and there is at least one sector in-between each two neighbors’ sectors (dominant server).
9
Neighbor relations are sent to UE over System Information Block SIB11 (idle mode state),
SIB11/12 (Cell_FACH, Cell_PCH, URA_PCH) and over measurement control (dedicated
Cell_DCH state). As shown in figure below
SIB11 dimensioning
SIB11 data load is not fixed, but is dimensioned based on the below requirements:
Neighbor Relations
• Each intra-frequency neighbor 2 bytes (16 bits)
• Each inter-frequency neighbor 6 bytes (48 bits)
• Each FEMTO neighbor 7 bytes (56 bits)
• Each IRAT/GSM neighbor 5 bytes (40 bits)
• Parameters
• Each neighbor QQUALMIN that deviates from serving cell 1 byte (8 bits)
• Each neighbor QRXLEVMIN that deviates from serving cell 1 byte (8 bits)
• Use of QOFFSET 1 byte (8 bits)
• Header: e.g. 192 bits Ericsson, 287 bits ZTE…etc
SIB11 Calculations
Ericsson formula (source: internet blogs)
10
SIB11 example
Assuming Ericsson case without parameters’ deviation and no femtos
48*interfreq (31) + 16*intrafreq (32) + 40*iRat (32) + 192 = 3472 (<3552)
HSDPA Code congestion can be expanded by adding more carriers (spectrum) or more sectors
(multi-beam). In case of spectrum constrains, the multi-beam antennas are the best way forward
for adding sectors
Power congestion can be solved by additional radios and redistributing the carriers among
all radios. Here too, in case of spectrum shortages, multi beam antennas can make a good
remedy.
The diagram above, illustrates two expansion methods: Additional Carriers and Multi Beams.
11
Expanding with carriers (F1/F2/F3) will utilize both the 32 intraFreq relations (F1→F1) and
the 32 interFreq relations pools (F1→F2 + F1→F3). Referring to the figure above, each
existing (F1) will get additional x2 interFreq relations (F2, F3). Note that we can add only 32
more interFreq relations to the existing 32 intraFreq max relations.
→ That is neighbor relations loading for interFreq relations is multiplied x2 compared to the
intraFreq case.
(F1→F2 + F1→F3) / 32 → 2x (F1→F1) /32
On the other hand, expanding by tri beam antennas using the same carriers, has only 1 pool
of 32 intraFreq relations to utilize (No additional 32 interFreq in this case). However, the
neighbors relations do not triple as the new sectors in between provide sufficient isolation and
not all new sectors need to be defined as neighbors.
From the below figures, immediate defined neighbors counts, for the serving sector shown in
red arrow, jump from 8 to 17 after deploying tri beam antennas.
Comparing both expansion scenarios, we see that the neighbor list loading is doubled in
both cases.
Optimizers used to periodically check attempted handover counts. The defined relations with
least handovers, over a certain span, made good candidates for deletion.
On the other hand, drive tests with UEs and attached scanners, are used to identify missing
relations.
Then came some advanced features, like the Mobile Assisted Frequency Allocation (MAFA).
The feature modifies neighbor lists sent to UEs, forcing to measure and report on non-defined
neighbors for assessment.
12
LTE case
When LTE was introduced, it came along with its SON concepts. So this time ANR resides
in the eNodeB. The serving cells’ eNodeB can instruct its UEs to report on certain cells PCI.
(Similar to the 2G MAFA concept). Such systems have also some intelligence in detecting
conflicting PCIs and reassigning proper values. More details are in 4
V. Conclusion
Out of the two common antenna upgrade bore planning techniques, the “inherited beam
Azimuth” is seen less disruptive. However, a calculated uniform azimuth shift will be required to
eliminate coverage gaps in case of multi-beam antennas tessellation deployments.
Moreover, PCI planning is crucial in optimizing LTE networks’ performance. The v-shift values
are intended to reduce inter-sector interferences at low load conditions. v-shift values run
from 0 to 5 (PCI mod6) for antenna systems with 1 port (SISO), and from 1 to 2 (PCImod3)
for antenna systems of 2 and 4 ports (MIMO). Since having unique v-shifts is impossible for
sites with 6 or 9 sectors deploying 2x2 MIMO. A number of v-shift arrangements have been
proposed to avoid direct neighbors conflicts. Impact for conflicting PCI-vshift values, for direct
neighbors, is found more sever in case of intra site than it is in the inter site cases.
And finally, capacity expansions by multi beam antennas and multi carriers’ effects on neighbor
lists capacity loading were studied and found comparable.
VI. References
1
Philip Sorrells, White Paper, Twin Beam technology adds immediate capacity without additional antennas
2
Harri Holma and Antti Toskala, WCDMA for UMTS, 4th Edition, John Wiley and Sons
3
http://www.telecomsource.net/showthread.php?3936-SIB11-calculation/page2
4
3GPP 36.300, sub-clause 22.3.2a
13
We’re proud to be a part
of your network’s story.
Here at CommScope, we embrace our role as a
trusted resource, partner, and facilitator. We create the
infrastructure that connects the world and evolves with
every advance in technology. By investing all of our
capabilities, resources, relationships, and products into
your toughest challenges, we continue our long history
of solving problems together—paving the way for new
ideas and fresh ways of thinking.
www.commscope.com
Visit our website or contact your local CommScope representative for more information.