Professional Documents
Culture Documents
WWW - Tech Tools - Me
WWW - Tech Tools - Me
Feature Description
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
Contents
2 Feature Operation 2
2.1 Network Requirements 2
2.2 Feature Operation 2
2.3 Process Steps 2
2.4 Supported Bandwidth 3
3 Parameters 4
3.1 Introduced Parameters 4
3.2 Affected Parameters 4
4 Network Impact 5
4.1 Capacity 5
4.2 Coverage 5
6 Performance 7
6.1 KPIs 7
6.2 Counters 7
6.3 Events 8
Summary
The PDCCH Power Boost feature benefits the user in the following ways:
• Increased cell coverage for, for example beam-forming (TM7 and TM8)
and heterogeneous network scenarios due to increased PDCCH
coverage.
• Power Control
• Radio Network
2 Feature Operation
This section describes the PDCCH Power Boost feature in more detail,
including network configuration requirements and operation flows.
2.3.2 Boost Value and PDCCH Power per OFDM Symbol Checking
The requested maximum boost power level, given by the MOM parameter
pdcchPowerBoostMax, is validated against the available PDCCH power in the
control region.
The boost is for UE specific search space rather than common search space.
3 Parameters
• EUtranCellFDD.pdcchPowerBoostMax
• EUtranCellTDD.pdcchPowerBoostMax
4 Network Impact
This section describes how the PDCCH Power Boost feature impacts the
network functions and capabilities.
4.1 Capacity
This section provides information on the impact of the feature on network
capacity.
If the feature is activated, the cell capacity measured as the average number
of scheduled PDCCHs per Transmission Time Interval (TTI) is increased in
typical high load VoIP scenarios/conditions.
4.2 Coverage
This section provides information on the impact of the feature on network
coverage.
This section describes how the PDCCH Power Boost feature affects other
features and functions.
6 Performance
6.1 KPIs
This feature has no associated Key Performance Indicators (KPI).
6.2 Counters
Table 3 lists the counters associated with the PDCCH Power Boost feature.
Table 3 Counters
Counter Description
pmPdcchTxAggressive FDD only: Counts the total number of times where the PDCCH
transmissions are considered to be aggressive, that is, the
number of CCEs allocated is much lower than the number of
CCEs required.
pmPdcchTxConservative FDD only: Counts the total number of times where PDCCH
transmissions are considered to be conservative, that is, (the
number of CCEs allocated is much higher than the number of
CCEs required.
pmPdcchCceAggregationDistr This counter indicates the distribution of PDCCH CCE
aggregation levels selected during the PDCCH allocation phase.
Counts the number of samples with corresponding PDCCH CCE
aggregration level.
Exists for MO classes:
• EUtranCellFDD.pmPdcchTxAggressive
• EUtranCellTDD.pmPdcchTxAggressive
pmPdcchSym0PwrUtil This counter counts the Physical Downlink Control Channel
(PDCCH) symbol 0 power utilization for PDCCHs transmitted on
the air interface. It counts the PDCCH power % utilized in OFDM
symbol 0, compared to the total available PDCCH power in the
same symbol, while considering bandwidth and antenna
configuration.
Exists for MO classes:
• EUtranCellFDD.pmPdcchTxAggressive
• EUtranCellTDD.pmPdcchTxAggressive
pmPdcchSym1PwrUtil This counter counts the Physical Downlink Control Channel
(PDCCH) symbol 1 power utilization for PDCCHs transmitted on
the air interface. It counts the PDCCH power % utilized in OFDM
symbol 1, compared to the total available PDCCH power in the
same symbol, while considering bandwidth and antenna
configuration.
Exists for MO classes:
• EUtranCellFDD.pmPdcchTxAggressive
• EUtranCellTDD.pmPdcchTxAggressive
Counter Description
pmPdcchSym2PwrUtil This counter counts the Physical Downlink Control Channel
(PDCCH) symbol 2 power utilization for PDCCHs transmitted on
the air interface. It counts the PDCCH power % utilized in OFDM
symbol 2, compared to the total available PDCCH power in the
same symbol, while considering bandwidth and antenna
configuration.
Exists for MO classes:
• EUtranCellFDD.pmPdcchTxAggressive
• EUtranCellTDD.pmPdcchTxAggressive
pmPdcchSym3PwrUti1 This counter counts the Physical Downlink Control Channel
(PDCCH) symbol 3 power utilization for PDCCHs transmitted on
the air interface. It counts the PDCCH power % utilized in OFDM
symbol 3, compared to the total available PDCCH power in the
same symbol, while considering bandwidth and antenna
configuration.
Exists for MO classes:
• EUtranCellFDD.pmPdcchTxAggressive
• EUtranCellTDD.pmPdcchTxAggressive
6.3 Events
Table 4 lists the events are introduced by PDCCH Power Boost feature.
Table 4 Events
Event Event Parameter Description
INTERNAL_PER_CELL_TR EVENT_PARAM_PDCCH_CCE_REQU Counter the number of times each
AFFIC_REPORT ESTED_DISTR_0..11 PDCCH requested CCEs range
used during the PDCCH allocation
phase in the current TTI.
This PDF counter is instantiated per
Cell.
[0]: PDCCH required number of
CCEs*100 in the range of (0,50].
[1]: PDCCH required number of
CCEs*100 in the range of (50,75].
[2]: PDCCH required number of
CCEs*100 in the range of (75,100].
[3]: PDCCH required number of
CCEs*100 in the range of
(100,150].
[4]: PDCCH required number of
CCEs*100 in the range of
(150,200].
[5]: PDCCH required number of
CCEs*100 in the range of
(200,300].
[6]: PDCCH required number of
CCEs*100 in the range of
(300,400].
[7]: PDCCH required number of
CCEs*100 in the range of
(400,600].
[8]: PDCCH required number of
CCEs*100 in the range of
(600,800].
For a full list with detailed information about PM events, see the list files in the
List Files library folder.
Prerequisites
Steps
Let the CCTR be active for one week, for continued collection of
troubleshooting data.
Prerequisites
Continuous Cell Trace Recording (CCTR) is activated since at least one week.
This ensures there is troubleshooting data available if something goes wrong.
Steps
Let the CCTR be active for one week, for continued collection of
troubleshooting data.