Aggregation:

[0056] Specifically, an eNodeB as the LTE base station has to signal on the PDCCH per TTI to all
scheduled UEs the corresponding allocation for UL and DL. In addition, also broadcast, paging and other
common signaling is transmitted. In order to comply with these tasks, the PDCCH is partitioned into a
common search space (CSS) and a UE specific search space (USS). Every active UE in the cell listens to
the PDCCH (excluding the configured DRX periods). Though, a UE listens only on specific search
positions according to its hashing function, which relies on RNTI and a sub frame number and the
aggregation selected for the message. An aggregation defines the code-rate selected for the message,
which is derived from CQI/radio quality measurements such that typically a target of 1% BLER
(TARGET_BLER) is maintained. Unfortunately, the higher the aggregation, the lower is the number of
potential search positions on the PDCCH. There are aggregations AGG1 (QPSK-2/3), AGG2 (QPSK 1/3),
AGG4 (QPSK-1/6) and AGG8 (QPSK-1/12) possible with six potential search positions, six potential
search positions, two potential search positions, and two potential search positions, respectively, on
PDCCH available. Moreover, a high aggregation occupies more capacity on PDCCH, i.e. the terminal
might suffer from higher blocking probability due to PDCCH hashing. Furthermore, depending on the
message size, every aggregation level has a certain SNIR requirement for achieving the TARGET BLER,
i.e. a large MIMO message (e.g. DCI format 2/2a) requires higher SNIR than a small conventional
message (e.g. DCI format 0, 1, 1a, . . . , 1d).

[0057] Thus, it is apparent that having several UEs allocated in a cell with different aggregations leads to
a high probability that collisions occur, i.e. the colliding UE cannot be served in that particular TTI if the
required search position on the PDCCH is already occupied by another UE. Such UEs may be termed as
blocked. Moreover, it can happen that already scheduled UEs cannot be served due to collisions which
are caused if the scheduler of a eNodeB does not take into account the PDCCH hashing, when selecting
the UEs, i.e. the scheduling information for a specific UE is arranged in a search position, which has
already been occupied by another UE. This leads to loss on the air interface by unused resources.

[0058] PDCCH also supports power control. By means of power relocation from one DCI message to
another one a fine tuning of the target BLER can be achieved within certain power ranges of +/-4 to 5 dB
as long as the maximum output power constraint of the eNB is maintained.

[0059] The total PDCCH capacity in terms of channel coding elements (CCEs) depends on the number of
OFDM symbols reserved per TTI. For example, in 10 MHz bandwidth 1, 2 or 3 OFDM symbols can be
allocated in a TTI for PDCCH

Read more: http://www.faqs.org/patents/app/20120039170#ixzz3pAPrXqnf

Downlink Power Allocation

If you look into the downlink signal, you would notice that it is made up of many different components. For e
Reference Signal, PDCCH, PDSCH etc.
Then you would have a question saying "How do we allocate power to each of the those channels ?". The sim
for our understanding would be to allocate the same power to all of the these channels, but this would be on
sake of our understanding.
For decoding any downlink data, the first step is to detect/decode reference signal. If the power of this refere
is same as all other channel power, it would not be easy (though not impossible) to detect it. So more practi
implementation is to make Reference Signal outstanding comparing to other channels as shown in the red b
following plot (you see a certain degree of offset, P_A between Reference Signal and other channel power).
However there is a complication with this method and it is because the reference channels occurs only in sp
symbols, not in every symbols. It means that there are some symbols with reference signal in it and there ar
other symbols without reference signal in it. It implies, if you measure the power of each symbol, some symb
(symbol with reference signal) has higher power than the other symbols (symbol without reference signal). T
cause some complication on the implementation of reciever equalizer.
To solve this problem of power difference between two groups of symbols, we can put lesser power to the no
reference signal channels at the symbol carrying reference signal. Due to this, you see another type of offse
the plot shown below.
Combining all of these factors, we have pretty complicate peak-and-valley type of power terrain rather than
plain terrain in downlink power allocation.

Power offset between PDSCH channel in the symbols with reference signal and PDSCH channel in the symbo
reference signal (P_B) is specified in SIB2 as follows.

+-sib-TypeAndInfo ::= SEQUENCE OF SIZE(1..maxSIB[32]) [1]

| +- ::= CHOICE [sib2]
| +-sib2 ::= SEQUENCE [00]
| +-ac-BarringInfo ::= SEQUENCE OPTIONAL:Omit
| +-radioResourceConfigCommon ::= SEQUENCE
| | +-rach-Config ::= SEQUENCE
 | | +-bcch-Config ::= SEQUENCE
| | +-pcch-Config ::= SEQUENCE
| | +-prach-Config ::= SEQUENCE
| | +-pdsch-Config ::= SEQUENCE
| | | +-referenceSignalPower ::= INTEGER (-60..50) [18]
| | | +-p-b ::= INTEGER (0..3) [0]

Power offset between the Reference Signal and PDSCH channel in the symbols without reference signal (P_A
specified in RRC Connection Setup as follows. P_A is UE specific power offset. This is why this is specified by
Connection Setup message.

+-c1 ::= CHOICE [rrcConnectionSetup-r8]

+-rrcConnectionSetup-r8 ::= SEQUENCE [0]
+-radioResourceConfigDedicated ::= SEQUENCE [100101]
| +-srb-ToAddModList ::= SEQUENCE OF SIZE(1..2) [1] OPTIONAL:Exist
| +-drb-ToAddModList ::= SEQUENCE OF OPTIONAL:Omit
| +-drb-ToReleaseList ::= SEQUENCE OF OPTIONAL:Omit
| +-mac-MainConfig ::= CHOICE [explicitValue] OPTIONAL:Exist
| +-sps-Config ::= SEQUENCE OPTIONAL:Omit
| +-physicalConfigDedicated ::= SEQUENCE [1111001011] OPTIONAL:Exist
| +-pdsch-ConfigDedicated ::= SEQUENCE OPTIONAL:Exist
| | +-p-a ::= ENUMERATED [dB-3]
| +-pucch-ConfigDedicated ::= SEQUENCE [0] OPTIONAL:Exist
| +-pusch-ConfigDedicated ::= SEQUENCE OPTIONAL:Exist
| +-uplinkPowerControlDedicated ::= SEQUENCE [1] OPTIONAL:Exist
| +-tpc-PDCCH-ConfigPUCCH ::= CHOICE OPTIONAL:Omit
| +-tpc-PDCCH-ConfigPUSCH ::= CHOICE OPTIONAL:Omit
| +-cqi-ReportConfig ::= SEQUENCE [10] OPTIONAL:Exist
| +-soundingRS-UL-ConfigDedicated ::= CHOICE OPTIONAL:Omit
| +-antennaInfo ::= CHOICE [defaultValue] OPTIONAL:Exist
| +-schedulingRequestConfig ::= CHOICE [setup] OPTIONAL:Exist
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

In Physical Layer performance test, we set Rho A, Rho B as a test condition and the relationship between Rh
and P_a/P-b is as follows.

Normally P_B is specified first by SIB2 and P_A is determined by following table and specified in RRC messag
RRC Connection Setup, RRC Connection Reconfiguration) according to following table.
For further details, refer to 36.213 5.2 Downlink power allocation