Training Course - 5G RAN2.1 Beam Management

5G RAN2.
1 Beam Management
www.huawei.com
Date: October 2018
Copyright © 2018 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Describe principles of Basic Beam Management.
 Understand basic functions of 3D Coverage Pattern.
 Figure out enhanced functions of 3D Coverage Pattern. (Confidential! Only for internal
study, NOT for External Communication!)
 Know the parameter configuration of beam management.
Copyright © 2018 Huawei Technologies Co., Ltd. All rights reserved. Page 3
Change History
19B introduces the following changes to 19A:
 Added scenario-based beam densification
 Added scenario-based beam customization.
 Added MOs and parameters.
 Supported scenario-based beams by 8T RRUs.
Contents
1. Basic Beam Management
2. 3D Coverage Pattern
3. Feature Activation
4. Related Monitoring Items
Beam Management Overview
Beam management definition
Beam management refers to the management of scanning, reporting, and maintenance of static beams. It
enhances cell coverage and reduces system overhead. The purpose of beam management is to select
appropriate static beams for each channel.
Beamforming and beam management
Beamforming (BF) uses weighting for transmit signals and forms them into narrow beams directed at target UEs
or in other specific directions. If the weighting used for beamforming is preset, beam management is required. If
dynamic weighting is used, beam management is not required. For details about beamforming, see MIMO.
Channel Technology Reference Document

Broadcast channels: physical broadcast channel (PBCH) and 4.1.1 Beam Management of Cell-Level
Beam management
synchronization signal (SS) Broadcast Channels in Beam Management
• Data channels: physical downlink shared channel
(PDSCH) and physical uplink shared channel (PUSCH)
• Control channels: physical uplink control channel • 4.1.2 User-Level Static Beam
Beam management
(PUCCH) and physical downlink control channel Management in Beam Management
and beamforming
(PDCCH) • MIMO
• Channel state information-reference signal (CSI-RS) and
tracking reference signal (TRS)
Page 6
Beam Management and Its Subitems
In an LTE TDD network, a single, wide beam is used to
cover an entire cell. In an NR network, the cell is
covered using a series of narrow beams broadcast at
Cell-Level different angles at different moments, as shown in the
Beam figure on the right. The UE scans each of these
Management individual narrow beams to identify the best beam to
use for synchronization and system message
demodulation.
Beam
Management
 Static beams for uplink channels

Multiple narrow beams are used at the user level. The
User-Level (PUCCH/PUSCH) are selected based
best possible narrow beam set needs to be selected on SRS measurements. After SRS
Beam first for the PUCCH, PUSCH, PDCCH, PDSCH, and measurement, the reference signal
Management CSI-RS. The UE needs to scan these narrow beams to received power (RSRP) values are
identify the best beam set. The gNodeB then maintains organized and the beams with the
largest RSRP values are selected for
the best beam set reported by the UE and selects the
these channels.
best beam set for each channel.
 SRSs are used to measure the RSRPs
Note: of static beams for downlink channels
1. Currently, TRS beams belong to cell-level beams. (PDCCH/PDSCH/CSI-RS/TRS). The
2. User-level beams cannot be adjusted on the customer interface. beams with the largest RSRP values
are selected for downlink channels.
Contents
Contents
2.1 Scenario-based Broadcast Beams
2.2 Tilt and Azimuth Adjustment
2.3 Broadcast Beam Densification
2.4 Customized Beam Scenarios
2.5 Online Scenario-based Beam Adjustment
2.6 SSB Power Aggregation
Scenario-based Broadcast Beams
Broadcast beams can be used in various scenarios, such as buildings or public squares.
In public squares, wide beams are used near the

cell center to ensure the access. Narrow beams are
For high-rise buildings, beams with wide vertical
used at the cell edge to improve coverage.
coverage are used to improve the vertical coverage.
Massive MIMO cell

Neighboring cell
In business districts, there are both public In inter-cell interference scenarios, beams with
squares and high-rise buildings. Beams providing narrow horizontal scanning scope are used to
large horizontal and vertical coverage are used. avoid strong interference sources.
Broadcast Beam Protocol
The NR control channel supports narrow beams, greatly improving coverage.
Full BCH, SCH, and CSI-RS channels support beamforming.

Compared with LTE wide beams, the control channel
coverage is significantly improved.
Wide LTE PBCH beam
NR beamforming
and scanning
NR broadcast channel:
 The sweeping of a maximum of 8
beams is supported on C-band or
2.6 GHz band.
 The scanning of a maximum of 64
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 beams is supported on high
frequency bands.
DL DL DL DL UL
Beam Beam Beam Beam Beam Beam Beam

0 1 2 3 4 5 6 When NR beam scanning uses narrow beam polling, broadcast beams can be
combined to provide different coverage scopes but the same maximum gains.
5G RAN2.1 supports a large number of AAUs. The following table lists supported coverage scenarios except the DEFAULT scenario.
Horizontal Vertical 3 Tilt
Coverage
Scenario ID Scenario Description 3 dB dB Adjustment Azimuth Adjustment Range
Scenario
Beamwidth Beamwidth Range
Non-standard 3-sector networking is used to provide wide horizontal coverage.
This type of configuration is suitable for public squares or large buildings. The
SCENARIO_1 Square horizontal coverage in this scenario is better than that in SCENARIO_2. The 110° 6° –2° to +9° 0°
coverage near the cell center in this scenario is slightly poorer than that in
SCENARIO_2.
Non-standard 3-sector networking is used. When there are strong interference
sources in neighboring cells, the horizontal coverage of a cell can be reduced to
SCENARIO_2 Interference 90° 6° –2° to +9° –10° to +10°
mitigate the interference from neighboring cells. This configuration is suitable for
low-rise coverage as the vertical coverage angle is the smallest.
Non-standard 3-sector networking is used. When there are strong interference  –22° to +22°
sources in neighboring cells, the horizontal coverage of a cell can be reduced to  32T 8H4V (AAU5310): The azimuth
SCENARIO_3 Interference 65° 6° –2° to +9°
mitigate the interference from neighboring cells. This configuration is suitable for cannot be adjusted in this scenario.
low-rise coverage as the vertical coverage angle is the smallest.  8T 8H1V (RRU5258): –10° to +10°
 –32° to +32°
SCENARIO_4 Building This configuration is for low-rise buildings and hotspot coverage. 45° 6° –2° to +9°
 8T 8H1V (RRU5258): –22° to +22°
 –42° to +42°
SCENARIO_5 Building This configuration is for low-rise buildings and hotspot coverage. 25° 6° –2° to +9°
 8T 8H1V (RRU5258): –32° to +32°
Mid-rise coverage Non-standard 3-sector networking is used to provide coverage for mid-rise
SCENARIO_6 110° 12° 0° to 6° 0°
and public square buildings. This configuration provides the best horizontal coverage.
sources in neighboring cells, the horizontal coverage of a cell can be reduced to  –10° to +10°
Mid-rise coverage
SCENARIO_7 mitigate the interference from neighboring cells. This configuration is suitable for 90° 12° 0° to 6°  32T 16H2V (AAU5324): The azimuth
with interference
covering mid-rise buildings as the vertical coverage angle is larger than that in cannot be adjusted in this scenario.
SCENARIO_1 to SCENARIO_5.
Horizontal Vertical 3 Tilt
Coverage Azimuth Adjustment
Scenario ID Scenario Description 3 dB dB Adjustment
Scenario Range
Beamwidth Beamwidth Range
sources in neighboring cells, the horizontal coverage of a cell can be reduced
Mid-rise coverage
SCENARIO_8 to mitigate the interference from neighboring cells. This configuration is suitable 65° 12° 0° to 6° –22° to +22°
with interference
for covering mid-rise buildings as the vertical coverage angle is larger than that
in SCENARIO_1 to SCENARIO_5.
SCENARIO_9 Mid-rise building This configuration is for mid-rise buildings and hotspot coverage. 45° 12° 0° to 6° –32° to +32°
Non-standard 3-sector networking is used to provide coverage for high-rise
Public square and
SCENARIO_12 buildings and the best horizontal coverage. This configuration is recommended 110° 25° 6° 0°
high-rise building
when broadcast channels are required to reflect the coverage of data channels.
 –22° to +22°
 32T 16H2V (AAU5324):
–10° to +10°
High-rise coverage sources in neighboring cells, the horizontal coverage of a cell can be reduced
SCENARIO_13 65° 25° 6°  32T 8H4V (AAU5310):
with interference to mitigate the interference from neighboring cells. This configuration is suitable
The azimuth cannot be
for high-rise coverage as the vertical coverage angle is the largest.
adjusted in this
scenario.
 –32° to +32°
SCENARIO_14 High-rise building This configuration is for high-rise buildings and hotspot coverage. 45° 25° 6°  32T 16H2V (AAU5324):
–22° to +22°
 –42° to +42°
SCENARIO_15 High-rise building This configuration is for high-rise buildings and hotspot coverage. 25° 25° 6°  32T 16H2V (AAU5324):
–32° to +32°
SCENARIO_16 High-rise building This configuration is for high-rise buildings and hotspot coverage. 15° 25° 6° –47° to +47°
AAU/RRU Model Coverage Scenario Supporting Selection for Coverage Scenarios of Broadcast Beams or Not
 DEFAULT
8T (RRU5258) Yes
 SCENARIO_3 to SCENARIO_5
 DEFAULT
 SCENARIO_1
 SCENARIO_6
 SCENARIO_7
32T 16H2V (AAU5310 and AAU5313)  SCENARIO_8 Yes
 SCENARIO_12
 SCENARIO_13
 SCENARIO_14
 SCENARIO_15
 DEFAULT
 SCENARIO_7
 SCENARIO_8
32T 16H2V (AAU5324)
 SCENARIO_13
 SCENARIO_14
 SCENARIO_15
 DEFAULT
32T 8H4V (AAU5310) Yes
 SCENARIO_3 and SCENARIO_13
64T:
 AAU5612 N77/N78
 DEFAULT
 AAU5613 N77/N78 Yes
 SCENARIO_1 to SCENARIO_16
 AAU5257 N41
 AAU5619 N41
64T (AAU5613 N79) DEFAULT No
Users can configure coverage as required based on the details of the live network. Coverage can be configured for the scenarios using the
NRDUCellTrpBeam.CoverageScenario parameter. Setting notes are as follows:
 Generally, it is recommended that this parameter be set to DEFAULT, which is suitable for typical 3-sector networking.
 When significant horizontal coverage is required, SCENARIO_1, SCENARIO_6, or SCENARIO_12 is recommended. With the setting, cell edge UEs can obtain
higher beam gains and cell edge coverage is improved.
 If there are any fixed interference sources at the cell edge, SCENARIO_2, SCENARIO_3, SCENARIO_7, SCENARIO_8, or SCENARIO_13 can be used to
narrow down the horizontal coverage area and avoid the interference.
 When there are only isolated buildings, SCENARIO_4, SCENARIO_5, SCENARIO_9, SCENARIO_10, SCENARIO_11, SCENARIO_14, SCENARIO_15, or
SCENARIO_16 is recommended to provide small horizontal coverage. These scenarios are not suitable for continuous coverage.
 When there are only low-rise buildings, you can set the parameter to a value from SCENARIO_1 to SCENARIO_5.
 When there are mid-rise buildings, you can set the parameter to a value from SCENARIO_6 to SCENARIO_11.
 When there are high-rise buildings, you can set the parameter to a value from SCENARIO_12 to SCENARIO_16.
If the base station needs to cover floors below 30 m (H) and a horizontal scope within 30 m (B), perform the following steps to
calculate the ID of the scenario to be configured:
Step 1: Calculate the vertical Step 2: Calculate the horizontal

scanning scope of the beam. scanning scope of the beam.
If D is 70 m and h is 15 m, C If B is 30 m and D is 70 m, β is
is 15 m (C = H - h). Then, α 25°. According to configurations
is 25°. According to in non-default scenarios, the
configurations in non-default horizontal 3 dB beamwidth in
scenarios, the vertical 3 dB SCENARIO_5,
beamwidth in SCENARIO_10, and
SCENARIO_12 to SCENARIO_15 is 25°.
SCENARIO_16 is 25°.
Step 3 Based on the intersection of scenario choices in Step 1 and Step 2, SCENARIO_15 can meet both horizontal and vertical coverage requirements.
Contents
Broadcast Beam Tilt and Azimuth
To reduce the difficulty in site selection planning and site optimization and to save optimization and coordination
costs, remote downtilt adjustment is required. The tilts and azimuths of broadcast channel narrow beams can be
entirely adjusted in the unit of 1°through the parameter setting.
In scenarios where the interference from neighboring cells is severe, users can adjust the tilt and azimuth to
make the beams target at users in the local cell. This reduces the overlapped coverage in neighboring cells. In
addition, more beam directions can be achieved by adjusting the tilt and azimuth, meeting different coverage
requirements and implementing flexible networking.
Part of the
The beam gain
The beam gain is The beam gain beam gain
is the greatest
the greatest decreases when decreases
when the
when the preset the preset downtilt when the
preset azimuth
downtilt is used. is not used. preset azimuth
is used.
is not used.
Tilt adjustment is not supported (in scenarios 12 to 16) because the vertical scanning range has reached the
upper limit.
Azimuth adjustment is not supported (in scenarios 0, 1, 6, and 12) because the horizontal scanning range has
reached the upper limit.
The adjustment range is based on the parameter setting. Then, the parameter is substituted into the steering
vector. The steering vector is multiplied by the initial weight matrix to obtain the final steering vector, which is then
sent to the baseband part.
Note: Only the maximum adjustment capability is provided here. In actual situations, when the tilt is adjusted to a
certain degree, the side lobe suppression may not be sufficient. The adjustment range varies according to the
specific requirements.
If the upper side lobe meets the suppression requirement of 12 dB, the preset downtilt (6°) is used as the
reference. For digital RET, the increase range is 8° and the decrease range is 3°.
 The tilt adjustment range in scenarios 1 to 5 (with a vertical 3 dB beamwidth of 6°) is –2°to 9°.
 The tilt adjustment range in scenarios 6 to 11 (with a vertical 3 dB beamwidth of 12°) is 0° to 6°.
The method for calculating the actual direction angle of a broadcast beam is as follows:
Actual direction angle of a broadcast beam (vertical) = Value of NRDUCellTrpBeam.Tilt + Mechanical tilt
Default value of NRDUCellTrpBeam.Tilt = Preset tilt (The preset tilts of different AAUs are different.)
That is, the actual direction angle of a broadcast beam is calculated as described in the following table. (The
azimuth is similar, and the default value is 0°.).
Feature Purchasing Actual Direction Angle of a Broadcast Beam
The operator has not purchased the FOFD-010100 3D Actual direction angle of a broadcast beam = Default
Coverage Pattern feature. value of NRDUCellTrpBeam.Tilt + Mechanical tilt
The operator has purchased the FOFD-010100 3D Actual direction angle of a broadcast beam = Value of
Coverage Pattern feature. NRDUCellTrpBeam.Tilt + Mechanical tilt
Note:
1. The direction angle of a broadcast beam does not affect that of a traffic beam. That is, the direction of a traffic beam
envelope or a user-level static beam (SRS/CSI beam) is not affected by NRDUCellTrpBeam.Tilt (except for
AAU5310/AAU5313).
2. If the setting DEFAULT, SCENARIO_1, SCENARIO_6, or SCENARIO_12 is used, horizontal azimuth adjustment is not
supported because the horizontal scanning scope has reached its upper limit.
3. If SCENARIO_12 to SCENARIO_16 are used, tilt adjustment is not supported because the vertical scanning scope has
reached its upper limit. In scenarios where the interference from neighboring cells is severe, tilts and azimuths can be
adjusted to make the beams target users in a local cell. This reduces the overlapped coverage in neighboring cells.
Contents
2.3 Broadcast Beam Densification (Confidential! Only for internal study, NOT for External
Communication!)
Broadcast Beam Densification
Broadcast beam densification is added to 5G RAN2.1. In some scenarios, the number of broadcast beams can be maximized to 7 or
8. Broadcast beam densification can improve coverage at the junction of beams with an overhead of less than 1%.
Confidential!
Only for Internal Study. NOT for
External Communication!
Avoid to divulge secrets and
decrease the
NR traffic beams are dynamic (red envelope Competitiveness ！
without coverage deterioration at the beam
junction).
Before the densification After the densification
Broadcast beam densification can reduce the
probability of abrupt coverage deterioration and
is more suitable for traffic channels. The junction of beams is filled.
Note: In 5G RAN2.1, when the broadcast beam densification switch is turned on, no cell needs to be reestablished for scenario
modification. In addition, no UE is disconnected from the network (except for handovers caused by coverage scope changes and
when the UE does not meet camping conditions).
The following slides will introduce the scenario when the switch is turned off.
Broadcast Beam Densification
64T 32T (16H2V) 32T (16H2V) 32T (8H4V)
Scenario ID 8T (8H1V) (RRU5258)
(AAU5612/AAU5613/AAU5257/AAU5619) AAU5313/AAU5310 AAU5324 AAU5310
H105V6 H105V6 H90V6 H65V12 H90V6*

DEFAULT Tilt: –2° to +9° Tilt: –2° to +9° Tilt: –2° to +9° Tilt: 0° to 6° Tilt: 0°
Azimuth: 0° Azimuth: 0° Azimuth: 0° Azimuth: 0° Azimuth: 0°
SCENARIO_1 Y Y N N N
SCENARIO_2 Y* N N N N
SCENARIO_3 Y* N
Confidential!
N Y Y*
SCENARIO_4 Y* N N N Y*
SCENARIO_5 Y* N Only for
N Internal Study.
N NOT for Y*
SCENARIO_6 Y Y External
N Communication!N N
SCENARIO_7 Y* Y* Y N N
SCENARIO_8 Y* Y*
AvoidYto divulge secrets
N
and N
SCENARIO_9 Y N decrease
N the N N
SCENARIO_10
SCENARIO_11
Y*
Y*
N
N
Competitiveness
N
N
！N
N
N
N
SCENARIO_12 Y Y N N N
SCENARIO_13 Y* Y* Y* Y N
SCENARIO_14 Y* Y* Y N N
SCENARIO_15 Y Y* Y* N N
SCENARIO_16 Y* N N N N
Note:
• "Y" indicates that beam densification is supported in this scenario.
• "N" indicates that beam densification is not supported in this scenario.
• "N/A" indicates that densificaiton is supported in the scenario but there is no coverage gains.
Contents
2.4 Customized Beam Scenarios (Confidential! Only for internal study, NOT for External
Communication!)
Customized Beam Scenarios
In 5G RAN2.1, beam scenarios can be customized by customers using the parameter
NRDuCellTrpCustBeam. The tilt and azimuth of a single beam can be set. In RAN2.1, the
customized beam scenario can take effect only after all beam directions are configured.
Confidential!
Only for Note:
Internal Study. NOT for
In 5G RAN2.1, customized beam
scenarios are only supported by 64T
AAUs. They can work with mAOS AI smart
decrease the
O&M.
Competitiveness ！table shows the adjustment
The following
range of a beam.
Default Adjustment Range
64T Azimuth –47° to +47°

16H4V
The tilt and azimuth of each beam can be defined Tilt –3° to +15°
separately to form a new broadcast beam pattern.
Customized Beam Scenarios
In addition to automatic tools, customized scenarios support manual and batch configuration by
customers.
For example: Run the following commands when the beam coverage scope is required to be 90°
and 6° in horizontal and vertical planes, respectively. The beams also need to cover the high
Confidential!
buildings in the normal direction of the base station.
External
//Changing the broadcast scenario to a customized Communication!
one when slot configuration is 4:1
ADD NRDUCELLTRPCUSTBEAM: NrDuCellTrpId=1, BeamId=0,
Avoid Tilt=6,
to divulge Azimuth=-40;
secrets and
ADD NRDUCELLTRPCUSTBEAM: NrDuCellTrpId=1, BeamId=1,
decrease the Tilt=6, Azimuth=-22;
ADD NRDUCELLTRPCUSTBEAM: NrDuCellTrpId=1, BeamId=2, Tilt=6,
Competitiveness ！Azimuth=-7;
ADD NRDUCELLTRPCUSTBEAM: NrDuCellTrpId=1, BeamId=3, Tilt=6, Azimuth=7;
ADD NRDUCELLTRPCUSTBEAM: NrDuCellTrpId=1, BeamId=6, Tilt=-2, Azimuth=0;
MOD NRDUCELLTRPBEAM: NrDuCellTrpId=1, CoverageScenario=

CUSTOMIZED_BEAM_SCENARIO, Tilt=0 ， Azimuth=0, MaxSsbPwrOffset=0;
Contents
Online Scenario-based Beam Adjustment
5G RAN2.1 supports online adjustment of scenario-based beams without cell reestablishment. (For
beam scenario modification in RAN1.0/RAN2.0, cell deactivation is required. As a result, all users are
disconnected from the network.)
When the broadcast beam coverage scenario (specified by NRDUCellTrpBeam.CoverageScenario)
and the broadcast beam densification switch (specified by
NRDUCellTrpBeam.ScenarioBeamAlgoSw) are modified, the following performance losses occur:
 The incoming handover success rate of handover or resynchronized UEs decreases.
 Resynchronized UEs will experience call drops.
 The peak performance deteriorates.
 UEs perform random access again.
The preceding issues are temporary. It is recommended that the interval between two scenario
modifications be longer than 10 minutes.
Contents
2.6 SSB Power Aggregation (Confidential! Only for internal study, NOT for External
Communication!)
SSB Power Aggregation
5G RAN2.1 supports SSB power aggregation. (This function is removed from Full-Channel Coverage
Enhancement and added to 3D Coverage Pattern.)
PSD
PSD Power
PDSCH SSB PDSCH Confidential!

PDSCH SSB PDSCH
F Only for Internal Study. NOT for F
 Principle: The power of some PDSCHs can be transferred to the SSB.
 The quantity of transferred power depends on thedecrease the
configuration of a cell parameter (MaxSsbPwrOffset).
 Selection of PDSCH RBGs depends on scheduling. Competitiveness
Scheduled RBGs consume！ power first. If the RB has
no power, scheduling is not performed.
 Scenario: It is recommended that SSB power aggregation be enabled in scenarios where the SSB power is
limited caused by large inter-site distance and supplementary uplink (SUL) or where the vertical half-power
bandwidth is greater than 6.
 Gain: The gain depends on the configuration. For example, if the loss of PDSCH PRBs is 3% to 5%, the gain
in SSB RSRP will be 3 to 6 dB, given a bandwidth of 80 MHz and slot configuration of 4:1.
Feature Configuration
 Recommended scenarios
 It is recommended that SSB power aggregation be enabled in scenarios where the SSB power is limited
Confidential!
caused by large inter-site distance and SUL or where the vertical half-power bandwidth is greater than 6.
 Feature activation External Communication!
 //Configuring maximum SSB power offset decrease the
MOD NRDUCellTrpBeam: MaxSsbPwrOffset=3; Competitiveness ！
 Feature deactivation
 MOD NRDUCellTrpBeam: MaxSsbPwrOffset=0;
Contents
2. 3D Coverage
Beam Management Parameters
3D Coverage Pattern (scenario-based broadcast beams)
Parameter Meaning Parameter ID Setting Notes
TRP ID NRDUCellTrpBeam.NrDuCellTrpId This parameter is set to the TRP ID.
By default, only the default scenario is supported. Licenses are required

for the configuration of other scenarios.
Scenario NRDUCellTrpBeam.CoverageScenario Before the configuration, run the DSP NRDUCELLTRP command to
query the scenarios supported by the AAU.
Changing the scenario will cause the cell to reset.
For low frequency bands, it is recommended that this parameter be set to

Tilt NRDUCellTrpBeam.Tilt
the preset downtilt (255) to obtain the maximum beam gains.
Azimuth NRLoCellRsvdParam.Azimuth It is recommended that this parameter be set to 0°.
Power NRDUCellTrpBeam. MaxSsbPwrOffset It specifies maximum SSB power offset.
It is recommended that this switch be turned on when the scenario is

Algorithm switch NRDUCellTrpBeam. ScenarioBeamAlgoSw frequently modified and when weak beam coverage areas exist in the
target coverage scenario.
NR DU cell TRP ID NRDUCellTrpCustBeam.NrDuCellTrpId This parameter must be configured.

Beam ID NRDUCellTrpCustBeam.BeamId This parameter must be configured.
Tilt NRDUCellTrpCustBeam.Tilt None
Azimuth NRDUCellTrpCustBeam.Azimuth None
Beam Management Feature Observation
This feature is enabled by default. You can run LST NRDUCELLTRPBEAM command to query the configured beam scenario and tilt.
Trace the UE and observe the RSRP corresponding to the optimal beam. Then, determine whether the beam scenario takes effect.
For example, if the UE locates at the normal direction of the vertical beam as shown in the following figure, when the H105V6 scenario is
changed to the H45V25 scenario, you can observe that the RSRP reported by the UE after the change is higher than the RSRP reported by
the UE before the change.
The beam ID is also changed from 3 to 1.
2 3 4
1 5 1 2
0 3
0 6
H105V6 H45V25
Contents
2. 3D Coverage
Beam Management External CHR
Cell Tracing Event Description
Recording Mode Event Name Event & Parameter Meaning
Event ID and Parameters
Statistics on downlink service traffic at the MAC layer collected based

Private event |
PERIOD_PRIVATE_B Fixed period: 15 on beams (including initial transmission and retransmission service
0x01008002 real-time stream |
EAM_TRAFFIC CELL minutes traffic, which is calculated based on cell-level beams) (TDD only)
SIG log
For unused beams, this field is set to an invalid value.
Private event |
BEAM_NOISE_TRAC Fixed period: 15 Average and maximum values of beam-based interference (cell-level)
KING minutes (TDD only)
SIG log
Private event |
PERIOD_PRIVATE_B Fixed period: 15 Number of synchronized UEs using the static beams ID0 to ID127.
EAM_SYN_UE_NUM minutes Each UE is counted only in the optimal beam.
SIG log
User-defined periodic L2 measurement event in a gNodeB

After the event is subscribed, the measurement results of the following
will be recorded based on the L2 user instance period.
Private period |
　 BeamSwitchNum: optimal beam handover times (The optimal beams
PERIOD_PRIVATE_U obtained through TRX sorting are selected on high frequency bands.)
E_MEASUREMENT CsiRs_Beam1_ID: ID of the first beam reported by the UE (four in total)
SIG log
CsiRs_Beam1_Rsrp: RSRP of the first beam reported by the UE (four
in total)
Ssb_Beam_ID: ID of the SSB beam reported by the UE
Ssb_Rsrp: RSRP of the SSB beam reported by the UE
Beam Management-related Monitoring Items
(Performance Monitoring)
Optimal beam ID and RSRP of each TRX on high frequency bands
Monitoring Item English Name Description

Indicates the ID of the optimal downlink beam at
TRX0DlOptBeamID TRX0_DlOptBeamID
the detection reporting time.
Indicates the RSRP corresponding to the optimal
TRX0DlOptBeamRsrp TRX0_DlOptBeamRsrp
downlink beam at the detection reporting time.
Indicates the ID of the optimal uplink beam at the
TRX0UlOptBeamID TRX0_UlOptBeamID
detection reporting time.
Indicates the RSRP corresponding to the optimal
TRX0UlOptBeamRsrp TRX0_UlOptBeamRsrp
uplink beam at the detection reporting time.
Thank You
www.huawei.com

Training Course - 5G RAN2.1 Beam Management

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Training Course - 5G RAN2.1 Beam Management

Uploaded by

Copyright:

Available Formats

5G RAN2.

Date: October 2018

Copyright © 2018 Huawei Technologies Co., Ltd. All rights reserved.

Channel Technology Reference Document

 Static beams for uplink channels

In public squares, wide beams are used near the

Massive MIMO cell

Full BCH, SCH, and CSI-RS channels support beamforming.

Wide LTE PBCH beam

Beam Beam Beam Beam Beam Beam Beam

Step 1: Calculate the vertical Step 2: Calculate the horizontal

H105V6 H105V6 H90V6 H65V12 H90V6*

64T Azimuth –47° to +47°

MOD NRDUCELLTRPBEAM: NrDuCellTrpId=1, CoverageScenario=

PDSCH SSB PDSCH Confidential!

 MOD NRDUCellTrpBeam: MaxSsbPwrOffset=0;

By default, only the default scenario is supported. Licenses are required

For low frequency bands, it is recommended that this parameter be set to

It is recommended that this switch be turned on when the scenario is

NR DU cell TRP ID NRDUCellTrpCustBeam.NrDuCellTrpId This parameter must be configured.

Statistics on downlink service traffic at the MAC layer collected based

User-defined periodic L2 measurement event in a gNodeB

Monitoring Item English Name Description

You might also like