Tuesday, 30 August 2016

Physical Channel Resource Management Feature

An LTE network has several types of physical channels and each type has its own resource management algorithm as listed in Table 2-1. This document also describes the sounding reference signal (SRS) resource management algorithm because SRSs are scheduled and managed separately.
Table 2-1 Resource management algorithms for physical channels
Category
Physical Channel
Resource Management Algorithm
Downlink physical channels
Physical Broadcast Channel (PBCH)
PBCH resource allocation does not require manual configurations. For details about power configurations for the PBCH, see Power Control Feature Parameter Description.
Physical Control Format Indicator Channel (PCFICH)
PCFICH resource allocation does not require manual configurations. For details about power configurations for the PCFICH, see Power Control Feature Parameter Description.
Physical Downlink Control Channel (PDCCH)
Physical Hybrid ARQ Indicator Channel (PHICH)
Physical Downlink Shared Channel (PDSCH)
See Scheduling Feature Parameter Description.
Physical Multicast Channel (PMCH)
eNodeBs do not support the PMCH.
Uplink physical channels
Physical Uplink Control Channel (PUCCH)
Physical Uplink Shared Channel (PUSCH)
See Scheduling Feature Parameter Description.
Physical Random Access Channel (PRACH)
See Connection Management Feature Parameter Description.

2.2 Benefits

By controlling signaling resources, physical channel resource management minimizes control signaling overheads, ensures demodulation performance of control signaling, and therefore increases data throughput.

3 PHICH Resource Management


3.1 Functions

The PHICH carries hybrid automatic repeat request (HARQ) ACK or NACK feedback on uplink data.

3.2 Resource Allocation

The PHICH resource positions for each UE in the uplink are determined by the PUSCH information, PHICH duration, and PHICH group quantity of this UE. For details, see section a40 6.9 in 3GPP TS 36.211.
The PhichDuration parameter specifies the type of PHICH duration.
  • If this parameter is set to NORMAL, the PHICH is allocated only the first orthogonal frequency division multiplexing (OFDM) symbol, and the number of OFDM symbols occupied by the PDCCH adaptively adjusts.
  • If this parameter is set to EXTENDED, the PHICH is allocated the first three OFDM symbols, each of which has a resource element group (REG) to obtain time diversity gain. However, the PDCCH can occupy only a fixed number of OFDM symbols and therefore PDCCH symbol adaption cannot take effect. For the mapping between the type and the duration, see 3GPP TS 36.211.
    • If the system bandwidth is 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz, the PDCCH can occupy a maximum of three OFDM symbols.
    • If the system bandwidth is 1.4 MHz, the PDCCH can occupy three or four OFDM symbols.
Subframes 1 and 6 are allocated two OFDM symbols, and the other subframes are allocated three OFDM symbols.
The PhichResource parameter is used to calculate the number of PHICH groups in a cell. This parameter corresponds to the Ng parameter specified in 3GPP TS 36.211.
  • If this parameter is set to ONE_SIXTH, Ng is 1/6.
  • If this parameter is set to HALF, Ng is 1/2.
  • If this parameter is set to ONE, Ng is 1.
  • If this parameter is set to TWO, Ng is 2.
If Ng is 1/6, the number of PHICH groups is the minimum, and therefore the number of symbols occupied by control channels is also the minimum. However, the number of code division multiplexing UEs in each group increases and the PHICH demodulation performance deteriorates to worst. In addition, the number of UEs that can be scheduled in each TTI may decrease due to the limit on the maximum number of code division multiplexing UEs in each PHICH group. If the normal cyclic prefix (CP) is used, the maximum number of code division multiplexing UEs in each PHICH group is eight. If the extended CP is used, the maximum number of such UEs is four.
If Ng is 2, the number of PHICH groups is the maximum, the number of code division multiplexing UEs in each PHICH group is the minimum, and the PHICH demodulation performance is the best. However, the number of symbols occupied by control channels is also the maximum or the number of scheduling indications sent by the PDCCH decreases.
For details about the Ng parameter, see section a40 6.9 in 3GPP TS 36.211.

4 PDCCH Resource Management

PDCCHs transmit downlink control information (DCI). For details about DCI, see 4.1 PDCCH Information Types.
To increase DCI transmission efficiency, the eNodeB manages PDCCH resources by using the following functions:
  • PDCCH aggregation level adaptation
  • PDCCH symbol adaptation
  • Closed-Loop adjustment to the PDCCH aggregation level
  • Downlink PDCCH power control
By default, the eNodeB adaptively selects a PDCCH aggregation level. The PdcchSymNumSwitch parameter specifies whether the eNodeB supports PDCCH symbol adaptation.
The PdcchAggLvlCLAdjustSwitch parameter for closed-loop adjustment to the PDCCH aggregation level is set to ON(On) by default. With this setting, the signal to interference plus noise ratio (SINR) for pilot signals can be adjusted for CCE aggregation level selection.

4.1 PDCCH Information Types

PDCCHs carry the following types of DCI:
  • Downlink grant
    This DCI includes the PDSCH resource indicator, modulation and coding scheme (MCS), HARQ information, and PUCCH power control commands. This DCI has multiple formats, such as formats 1, 1A, 1B, 1C, 1D, 2, and 2A. For details about information bits in each format, see section a40 5.3.3 in 3GPP TS 36.212.
  • Uplink grant
    This DCI includes the PUSCH resource indicator, MCS, HARQ information, and PUSCH power control commands. This DCI has only format 0. For details about information bits in format 0, see section a40 5.3.3 in 3GPP TS 36.212.
  • Power control command
    This DCI is a group of PUSCH power control commands for a UE, which supplement PUSCH power control commands in an uplink grant. This DCI has formats 3 and 3A. For details about information bits in each format, see section a40 5.3.3 in 3GPP TS 36.212.
    As shown in Figure 4-1, the PDCCH occupies the first or first several symbols of a subframe. If the system bandwidth is 1.4 MHz, the PDCCH occupies a maximum of four symbols. In the case of other bandwidths, the PDCCH occupies a maximum of three symbols. CCEs are basic allocation units.
    Figure 4-1 Position of the PDCCH

4.2 PDCCH Aggregation Level Adaptation

PDCCH aggregation level adaptation minimizes the resources occupied by the PDCCH and simultaneously ensures the PDCCH demodulation performance. Working with PDCCH symbol adaptation, PDCCH aggregation level adaptation enables the PDSCH to have more resources, improving the system throughput. If PDCCH symbol adaptation is disabled and a small number of UEs are to be scheduled within a transmission time interval (TTI), the PDCCH load decreases, reducing interference to neighboring cells and improving system performance.
The MCS for PDCCHs is quadrature phase shift keying (QPSK). The eNodeB can select an aggregation level, among four available aggregation levels, to ensure that block error rates (BLERs) on PDCCHs are less than 1%, as stipulated in 3GPP specifications.
A CCE is the smallest resource unit for transmission on PDCCHs. Each CCE contains nine REGs with each REG containing four resource elements (REs) and carries 72-bit information. Based on coding rates, the eNodeB can aggregate one, two, four, or eight CCEs to constitute a PDCCH, which corresponds to aggregation level 1, 2, 4, or 8, as stipulated in 3GPP specifications. The aggregation level indicates the number of CCEs occupied by a PDCCH. For example, if the aggregation level is 1, the PDCCH occupies one CCE; if the aggregation level is 2, the PDCCH occupies two CCEs.
  • PDCCHs with aggregation level 8 have the lowest coding rate and best demodulation performance.
    If PDCCH aggregation levels for all UEs in a cell are set to 8, CCE resources for PDCCHs are wasted for UEs in the cell center.
  • PDCCHs with aggregation level 1 have the highest coding rate but the worst demodulation performance.
    If PDCCH aggregation levels for all UEs in a cell are set to 1, PDCCHs may not be correctly demodulated for UEs close to the cell edge.
Figure 4-2 shows the procedure for PDCCH aggregation level adaptation.
Figure 4-2 Procedure for PDCCH aggregation level adaptation
  1. The channel quality indicator (CQI) adjustment algorithm calculates the CQI value.
    The basic feature for CQI adjustment is TDLOFD-00101501 CQI Adjustment. For details, see Scheduling Feature Parameter Description.
  2. The eNodeB calculates the SINR of downlink reference signals based on the CQI value.
  3. The eNodeB calculates the SINR of the PDCCH based on the SINR of the downlink reference signals.
  4. The eNodeB calculates the demodulation thresholds for various coding rates or aggregation levels based on the DCI formats.
  5. The eNodeB compares the PDCCH SINR with the demodulation threshold for each aggregation level and selects an appropriate PDCCH aggregation level.
SINRrs indicates the SINR of downlink reference signals.
SINRpdcch indicates the SINR of the PDCCH.
SINR1 indicates the demodulation threshold for aggregation level 1.
SINR2 indicates the demodulation threshold for aggregation level 2.
SINR4 indicates the demodulation threshold for aggregation level 4.
SINR8 indicates the demodulation threshold for aggregation level 8.
The eNodeB provides the aggregation level adaptation function for the PDCCH carrying the uplink and downlink scheduling grant DCIs. This maximizes the demodulation performance and capacity of the PDCCH. This function enables the eNodeB to select an appropriate PDCCH aggregation level based on channel quality, which is derived from the CQI. An appropriate PDCCH aggregation level is the lowest aggregation level that ensures a BLER of less than 1%.
Aggregation level adaptation does not apply to a PDCCH used for power control or for indicating the transmission positions of random access response, paging, and system information messages on the PDCCH.
An appropriate aggregation level must be set for the PDCCH so that all UEs in the cell can successfully interpret the control information. The ComSigCongregLv parameter specifies the PDCCH aggregation level.
  • If this parameter is set to CONGREG_LV4, the CCE aggregation level is 4.
  • If this parameter is set to CONGREG_LV8, the CCE aggregation level is 8.

4.3 PDCCH Symbol Adaptation

PDCCH symbol adaptation enables the eNodeB to adjust the number of symbols occupied by a PDCCH based on the number of required CCEs.
  • When a PDCCH requires fewer CCEs, the eNodeB decreases the number of symbols occupied by the PDCCH and provides idle time-frequency resources for PDSCHs.
  • When a PDCCH requires more CCEs, the eNodeB increases the number of symbols occupied by the PDCCH until the number reaches the maximum permissible value. If the bandwidth is 1.4 MHz, the PDCCH can occupy a maximum of four symbols. In the case of other bandwidths, the PDCCH occupies a maximum of three symbols.
  • In time division duplex (TDD) mode, the PDCCH occupies different quantities of symbols in subframes 1 and 6.
    • If the bandwidth is 1.4 MHz, the PDCCH occupies two symbols.
    • If the bandwidth is not 1.4 MHz and the PHICH Duration parameter is set to NORMAL, the PDCCH adaptively occupies the required number of symbols.
    • If the bandwidth is not 1.4 MHz and the PHICH Duration parameter is set to EXTENDED, the PDCCH occupies two symbols.
To rapidly provide sufficient CCEs when more CCEs are required and prevent ping-pong adjustments to the number of symbols occupied by a PDCCH, the eNodeB rapidly increases and then slowly decreases the number of symbols occupied by the PDCCH.
CCE usage within a certain time period must be measured to determine whether more CCEs are required and whether there are remaining CCEs available for use.
  • If uplink or downlink CCEs fail to be allocated or there are no available CCEs left within a TTI, more CCEs are required. In this situation, the number of symbols occupied by the PDCCH needs to be increased.
    NOTE:
    Uplink CCEs transmit uplink scheduling grants, and downlink CCEs transmit downlink scheduling grants.
  • If there are remaining CCEs left after uplink and downlink scheduling is complete within a certain time period, the number of required CCEs is less than the number of available symbols. In this situation, the number of symbols occupied by the PDCCH needs to be decreased.
Figure 4-3 shows the procedure for PDCCH symbol adaptation.
Figure 4-3 Procedure for PDCCH symbol adaptation
The PdcchSymNumSwitch parameter specifies whether to enable PDCCH symbol adaptation on the eNodeB. The InitPdcchSymNum parameter specifies the number of symbols initially occupied by a PDCCH.
  • If the PdcchSymNumSwitch parameter is set to ON(On), the eNodeB enables PDCCH symbol adaptation.
  • If the PdcchSymNumSwitch parameter is set to OFF(Off), the eNodeB disables PDCCH symbol adaptation and allocates resources to a PDCCH. The allocation is based on the number of symbols specified by the InitPdcchSymNum parameter.
If the PucchAlgoSwitch parameter is set to OFF(Off), do not change the value of the InitPdcchSymNum parameter online. Otherwise, the eNodeB performance deteriorates because of the conflict between PUCCH resources and other resources.

4.4 Closed-Loop Adjustment to the PDCCH Aggregation Level

In PDCCH aggregation level adaptation, the CQI adjustment algorithm for the PDSCH is used to calculate the PDCCH aggregation level. If interference with the PDSCH differs from that with the PDCCH, the calculation result may be inaccurate. In addition, the periodic CQI adjustment may be slower than channel condition changes, and the PDCCH aggregation level selected based on the CQI may be inaccurate. If an inaccurate PDCCH aggregation level is used, service drops may occur. Closed-loop adjustment to the PDCCH aggregation level is introduced to address this problem.
In addition to the adjusted CQI, the eNodeB considers the PDCCH BLER in closed-loop adjustment to the PDCCH aggregation level:
  • If the PDCCH BLER is greater than the target BLER, the closed-loop adjustment raises the aggregation level to improve PDCCH coverage performance.
  • If the PDCCH BLER is less than the target BLER, the closed-loop adjustment lowers the aggregation level to reduce PDCCH resource usage.
The PdcchAggLvlCLAdjustSwitch parameter specifies whether to enable closed-loop adjustment to the PDCCH aggregation level.
  • If the PdcchAggLvlCLAdjustSwitch parameter is set to ON(On), the eNodeB supports closed-loop adjustment to the PDCCH aggregation level.
  • If the PdcchAggLvlCLAdjustSwitch parameter is set to OFF(Off), the eNodeB does not support closed-loop adjustment to the PDCCH aggregation level.

4.5 Downlink PDCCH Power Control

If a PDCCH aggregation level as high as 8 still fails to ensure the PDCCH demodulation performance, PDCCH power can be increased to ensure correct PDCCH demodulation. If the PDCCH BLER is larger than the target BLER, increase the power for CCE resources. If the PDCCH BLER is less than the target BLER, decrease the PDCCH power to the initial value. If a PDCCH aggregation level as low as 1 can ensure PDCCH demodulation performance and the PDCCH BLER is less than the target BLER, decrease the PDCCH power to reduce interference. The downlink PDCCH power control enhances PDCCH coverage.
The DlPcAlgoSwitch parameter specifies whether to enable downlink PDCCH power control.
  • If this parameter is set to ON, the eNodeB supports downlink PDCCH power control.
  • If this parameter is set to Off, the eNodeB does not support downlink PDCCH power control.

5 PUCCH Resource Management

PUCCHs transmit uplink control signaling.

5.1 PUCCH Information Types

PUCCHs carry the following types of control signaling:
  • Acknowledgment (ACK), negative acknowledgement (NACK), or discontinuous transmission (DTX) to downlink HARQ
  • Scheduling request indicator (SRI)
  • Channel state information (CSI), including the CQI, precoding matrix indication (PMI), and rank indicator (RI)
PUCCHs support six formats, as listed in Table 5-1.
Table 5-1 PUCCH formats
PUCCH Format
Control Signaling
Modulation Scheme
Number of Bits per Subframe
1
SRI
N/A
N/A
1a
1bit ACK
BPSK
1
1b
2bit ACK
QPSK
2
2
CSI
QPSK
20
2a
CSI+1bit ACK
QPSK+BPSK
21
2b
CSI+2bit ACK
QPSK+QPSK
22
  • Format 1 is used for SRI transmission.
  • Format 1a is used for ACK to downlink HARQ for single-codeword transmission.
  • Format 1b is used for ACK to downlink HARQ for two-bit transmission, or ACK and scheduling request (SR) for HARQ for two-bit transmission.
  • For a normal CP, format 2 is used for carrying CSI reports only. For an extended CP, format 2 can be used for carrying both CSI reports and ACK to HARQ.
  • Format 2a is used for carrying both CSI reports and ACK to HARQ for one-bit transmission when a normal CP is used.
  • Format 2b is used for carrying both CSI reports and ACK to HARQ for two-bit transmission when a normal CP is used.
If CSI reports and ACK to HARQ are to be transmitted simultaneously in TDD mode, ACK to HAQR has a fixed length of two bits. Therefore, format 2a does not apply to this scenario.
PUCCHs occupy resource blocks (RBs) at two ends of an uplink cell bandwidth and use frequency hopping to achieve frequency diversity gains. Figure 5-1 shows the mapping to physical resource blocks for a PUCCH. In this figure, m is specified in 3GPP TS 36.211 and indicates the index of an RB used by the PUCCH.
Figure 5-1 Mapping to physical RBs for a PUCCH

5.1.1 ACK

A UE uses an ACK to indicate PDSCH decoding success. If the UE successfully receives data from the eNodeB, it sends an ACK to the eNodeB. If the UE fails to receive data from the eNodeB, it sends a NACK. If the UE cannot demodulate data received from the eNodeB, it does not send data. Then, DTX occurs.
Uplink and downlink subframes are asymmetrical in TDD mode. Therefore, two information feedback modes, HARQ-ACK bundling and HARQ-ACK multiplexing, are defined in 3GPP TS 36.213. They provide ACK to HARQ information about downlink subframes on one uplink subframe. Table 5-2 lists a downlink subframe set K provided by an uplink subframe n. The value range of the set is {ko,kl,....km-1} and the letter M represents the number of elements in the set K.
Table 5-2 Downlink subframe set {ko,kl,....km-1} for TDD
UL-DL
Configuration
Subframe n
0
1
2
3
4
5
6
7
8
9
0
-
-
6
-
4
-
-
6
-
4
1
-
-
7, 6
4
-
-
-
7, 6
4
-
2
-
-
8, 7, 4, 6
-
-
-
-
8, 7, 4, 6
-
-
3
-
-
7, 6, 11
6, 5
5, 4
-
-
-
-
-
4
-
-
12, 8, 7, 11
6, 5, 4, 7
-
-
-
-
-
-
5
-
-
13, 12, 9, 8, 7, 5, 4, 11, 6
-
-
-
-
-
-
-
6
-
-
7
7
5
-
-
7
7
-
  • HARQ-ACK bundling
    In this mode, all ACK to HARQ information about downlink subframes in a set K has an AND operation on each codeword, and is transmitted on a corresponding ACK code channel. For a single codeword, ACK to HARQ information has one bit. For two codewords, ACK to HARQ information has two bits.
  • HARQ-ACK multiplexing
    In this mode, all codewords transmitted in each downlink subframe in a set K have an AND operation. UEs choose a proper code channel and bit information based on the mapping between codewords and the bit information defined in 3GPP TS 36.213.
The mode for transmitting ACK to HARQ information is a UE-specific parameter, and it is transmitted in the RRC signaling message.

5.1.2 SRI

A UE uses an SRI to request an uplink bandwidth to be allocated by the eNodeB. Figure 5-2 shows the scheduling request procedure.
Figure 5-2 Scheduling request procedure
The UE sends an SRI in the same format as an ACK when new uplink data needs to be scheduled. SRIs and ACKs can share the same RBs. Table 5-3 lists SR periodicity and subframe offset configuration, as stipulated in 3GPP specifications.
Table 5-3 SR periodicity and subframe offset configuration
SR Configuration Index
SR Periodicity (ms)
SR Subframe Offset
0 – 4
5
5 – 14
10
15 – 34
20
35 – 74
40
75 – 154
80
155
OFF
N/A
SRIs occupy PUCCH resources, and their occupancy is represented by SRI loads. A UE sends SRIs to the eNodeB every SRI period. The SriAdaptiveSwitch parameter specifies whether a fixed or adaptive SRI period is used.

Fixed SRI Period

If the SriAdaptiveSwitch parameter is set to OFF(Off), users can set an SRI period for services of a QoS class identifier (QCI) by using the SriPeriod parameter. QoS is short for quality of service.
  • If a UE requests a single-service connection, the SRI period for the UE is the same as that for the service QCI.
  • If a UE requests a multi-service connection, the SRI period for the UE is the minimum value among the SRI periods for all QCIs of the services on the UE.
If a shorter SRI period is set for services with different QCIs, a UE can send more SRIs during the SRI period, which causes fewer UEs to access the cell. This decreases the average uplink scheduling delay for the UE and improves user experience.

Adaptive SRI Period

The eNodeB adaptively adjusts an SRI period based on SRI loads, which is called SRI adaptation. The SriAdaptiveSwitch parameter determines whether to enable or disable SRI adaptation.
If the SriAdaptiveSwitch parameter is set to ON(On), the eNodeB adaptively adjusts the SRI period for a newly admitted UE based on SRI loads.
SRI loads are classified into low, medium, and high.
A higher SRI load results in a larger SRI period set for a newly admitted UE. When SRI loads are light, an SRI period of 5 ms (10 ms for TDD mode with a ratio of 5) can be configured for all admitted UEs. In this way, a smaller SRI period can be configured for more newly admitted UEs. This decreases the average uplink scheduling delay for the UEs and improves user experience accordingly. However, cell SRI capacity decreases.
  • For low SRI loads, set small SRI periods for all admitted UEs.
    The SriLowLoadThd parameter specifies the threshold for the low load state of SRI resources. The value range is 0 to 50, indicating the number of UEs that can be admitted under the low load state. After the number of admitted UEs reaches the specified threshold, the low load state changes to the medium load state. The SRI period for the next admitted UE will be configured based on the medium load state.
  • For medium SRI loads, set an SRI period for an admitted UE based on the QCI of a service.
    If a UE performs a multi-service connection, set an SRI period for the UE to the minimum value among the SRI periods set for all services of the UE.
    Table 5-4 SRI periods for medium SRI loads
    QCI
    SRI Period (ms)
    3
    10
    1, 2, 5, 7
    10
    4, 6, 8, 9
    20
  • For high SRI loads, set an SRI period for an admitted UE based on the QCI of a service.
    Table 5-5 SRI periods for high SRI loads
    QCI
    SRI Period (ms)
    3
    20
    1, 2, 5, 7
    40
    4, 6, 8, 9
    80
If a UE performs a multi-service connection, set an SRI period for the UE to the minimum value among the SRI periods set for all services of the UE. A higher SRI load results in a larger SRI period set for a newly admitted UE.
The eNodeB does not adjust SRI periods for the admitted UEs that have been allocated SRI resources based on SRI loads.
If the SriAdaptiveSwitch parameter is set to ON(On), SRI loads increase when more UEs access a cell. The SRI periods for newly admitted UEs also increase. This increases SRI capacity but results in large average uplink scheduling delays for some UEs.

5.1.3 CQI, PMI, and RI

CQI

CQI indicates downlink channel quality. A UE reports a CQI to the eNodeB periodically, or in event-triggered mode. Periodic reporting takes precedence over event-triggered reporting if they are both configured.
CQIs reported periodically are sent to the eNodeB over a PUCCH or PUSCH.
CQIs reported in event-triggered mode are sent to the eNodeB over a PUSCH.

PMI

A PMI indicates a precoding matrix.
Signals received by the same antenna cause interference to each other. To prevent this, layer data is multiplied by a precoding matrix before transmission at the antenna port. The layer data, after being precoded and passed through spatial channels, is equivalent to a group of independent parallel data and no interference will occur. For details, see MIMO Feature Parameter Description.

RI

RI indicates the rank of a spatial channel matrix. For details, see MIMO Feature Parameter Description.

5.2 Cyclic Shift Interval for a PUCCH

PUCCH formats 1, 1a, and 1b use cyclic shifts of a sequence in each symbol. Each RB can use multiple cyclic shift sequences. The number of cyclic shift sequences is determined by the DeltaShift parameter, which specifies the cyclic shift interval. The DeltaShift parameter corresponds to in section a40 5.4 in 3GPP TS 36.211. The parameter value ranges from 1 to 3. If this parameter has a large value, the multipath delay increases and the number of code division multiplexing UEs on a PUCCH RB decreases.
  • If this parameter is set to DS1_DELTA_SHIFT(ds1), is 1. For a normal CP, each RB has 36 code channels. For an extended CP, each RB has 24 code channels.
  • If this parameter is set to DS2_DELTA_SHIFT(ds2), is 2. For a normal CP, each RB has 18 code channels. For an extended CP, each RB has 12 code channels.
  • If this parameter is set to DS3_DELTA_SHIFT(ds3), is 3. For a normal CP, each RB has 12 code channels. For an extended CP, each RB has 8 code channels.
For a normal CP
The LTE baseband processing unit (LBBPd) requires that the value of range from 1 to 3, and the LBBPc requires that the value of be 2 or 3.
For an extended CP
The LBBPc and LBBPd require that the value of be 3.
The cyclic shift interval for formats 2, 2a, and 2b of PUCCH is similar to that for formats 1, 1a, and 1b. The cyclic shift interval is UE-specific. The value of the cyclic shift interval is 2 or 3: If the UE-specific cyclic shift interval is 2, each RB has six code channels. If the UE-specific cyclic shift interval is 3, each RB has four code channels.

5.3 Dynamic PUCCH Resource Adjustment

The eNodeB dynamically adjusts PUCCH resources based on PUCCH load requirements. The eNodeB either reduces the overhead so that more resources can be used for PUSCH transmissions, or increases the PUCCH resources so that more UEs can be admitted. The PucchAlgoSwitch parameter specifies whether to enable PUCCH resource adjustment.
  • If the PucchAlgoSwitch parameter is set to PucchSwitch-1, the eNodeB adaptively increases or decreases PUCCH resources based on PUCCH load requirements. Half-static ACK/SRI resources and CQI resources are increased or decreased independently.
    • If the number of required PUCCH resources is greater than a specified threshold, the eNodeB increases PUCCH resources to ensure that UEs successfully access a cell.
    • If the number of required PUCCH resources is smaller than another specified threshold, the eNodeB decreases PUCCH resources to prevent a waste in uplink RBs due to large PUCCH resource overheads.
      The eNodeB adjusts PUCCH resources based on PUCCH load requirements to minimize PUCCH resource overheads. This adjustment increases RBs available on PUSCHs and increases PUSCH capacity.
  • If the PucchAlgoSwitch parameter is set to PucchSwitch-0, the number of PUCCH resources remains unchanged. In this case, PUCCH resource overheads remain a small value, which is set during cell initialization. However, PUCCH resources cannot be increased when the number of remaining code channels decreases. Therefore, the number of UEs to be scheduled is restricted in a cell.
  • The PUSCHMaxRBPUCCHAdjSwitch parameter determines PUCCH resource adjustment. If the PUSCHMaxRBPUCCHAdjSwitch parameter is set, the eNodeB reduces PUCCH resource overheads to increase RBs available on PUSCHs when there is a small number of UEs. This adjustment, however, does not meet all attempt per second (CAPS) requirements. If the PUSCHMaxRBPUCCHAdjSwitch parameter is not set, PUCCH resource adjustment can meet CAPS requirements.

6 SRS Resource Management

In the LTE system, a UE periodically sends SRSs across as nearly the entire PUSCH frequency band as possible. After receiving the SRSs, the eNodeB processes them and measures SINRs and time synchronization values on subcarriers in the PUSCH frequency band for each UE. SINRs are used for frequency selective scheduling of uplink channels, link adaptation, and power control.
  • In frequency selective scheduling, PUSCHs used for scheduling UEs use the optimal subcarrier.
  • Time synchronization values are used for uplink time synchronization of UEs.
The SrsCfgInd parameter specifies whether SRS resources are configured for UEs.
  • If this parameter is set to BOOLEAN_TRUE(True), SRS resources need to be configured for UEs in a cell. Compared with demodulation reference signals (DMRSs), SRSs reduce the PDCCH overhead and therefore increase the downlink capacity.
  • If this parameter is set to BOOLEAN_FALSE(False), SRS resources are not configured for UEs in a cell. As a result, there is no SRS overhead, increasing the uplink capacity.

6.1 SRS-related Concepts

SRS Subframe Configuration Index

An SRS subframe configuration index defines a subframe period and a subframe offset, which are contained in a group of subframe configuration data, as listed in the first column of Table 6-1.

SRS Subframe Period

If SRSs are transmitted every T ms, T is the SRS subframe period.

SRS Subframe Offset

The SRS subframe offset indicates the position (subframe number) where SRSs are transmitted in the time-frequency domain within a certain time period. SRSs are always transmitted in the last symbol of the subframe. The uplink pilot time slot (UpPTS) in a subframe for the TDD mode can have two SRS symbols.
For details about these concepts, see 3GPP TS 36.211.

6.2 Cell-Specific SRS


6.2.1 Cell-Specific SRS Subframe

A cell-specific SRS subframe indicates time-frequency domain resources that can be used by all UEs in a cell.

Configurations

3GPP TS 36.211 defines cell-specific SRS subframe configurations, as listed in Table 6-1.
Table 6-1 Cell-specific SRS subframe configurations
Cell-Specific SRS Subframe Configuration Index
Cell-Specific SRS Subframe Configuration Index (Binary)
SRS Subframe Period (ms)
SRS Subframe Offset
0
0000
5
{1}
1
0001
5
{1, 2}
2
0010
5
{1, 3}
3
0011
5
{1, 4}
4
0100
5
{1, 2, 3}
5
0101
5
{1, 2, 4}
6
0110
5
{1, 3, 4}
7
0111
5
{1, 2, 3, 4}
8
1000
10
{1, 2, 6}
9
1001
10
{1, 3, 6}
10
1010
10
{1, 6, 7}
11
1011
10
{1, 2, 6, 8}
12
1100
10
{1, 3, 6, 9}
13
1101
10
{1, 4, 6, 7}
14
1110
Inf
N/A
15
1111
Reserved
Reserved
SRSs are transmitted in UpPTS or common uplink subframes. As listed in Table 6-1, the cell-specific SRS subframe period can only be 5 ms or 10 ms, which is determined by the special TDD frame structure.
The SrsSubframeCfg parameter specifies the index for a cell-specific SRS subframe configuration. Each index corresponds to a subframe period and a subframe offset. If the SrsSubframeCfg parameter is set to SC5(5), the cell-specific SRS subframe period is 5 ms and the subframe offset is {1, 2, 4}. That is, cell-specific SRSs are transmitted on subframes 1, 2, and 4 every 5 ms.

Dynamic Adjustment

The TddSrsCfgMode parameter specifies the TDD SRS configuration to be used. It can be set to Experience_First, Experience_Enhanced, or Access_First. The default value is Access_First. The eNodeB dynamically adjusts cell-specific SRS resources based on cell loads only when the TddSrsCfgMode parameter is set to Experience_First or Experience_Enhanced.
  • The eNodeB allocates more time-frequency domain resources to the UEs in the cell when the cell loads are increasing.
  • When the cell loads are decreasing, the eNodeB reduces SRS time-frequency domain resources and at the same time reduces the consumption of PUSCH resources. In addition, the eNodeB increases resource allocation success rates by reshuffling bandwidth fragments.
When the SrsAlgoSwitch parameter is set to SrsSubframeRecfSwitch-1 and the TddSrsCfgMode parameter is set to Experience_First or Experience_Enhanced, the eNodeB adaptively adjusts SRS subframe configurations based on cell loads. When the SrsAlgoSwitch parameter is set to SrsSubframeRecfSwitch-0, the eNodeB always uses the subframe configuration specified by the SrsSubframeCfg parameter to allocate time-frequency domain resources for SRSs.

6.2.2 Cell-specific SRS Bandwidth

Cell-specific SRS bandwidths indicate frequency-domain resources for SRSs allocated to all UEs in a cell.
3GPP specifications define a maximum of four levels of SRS bandwidths which correspond to b=0, b=1, b=2, and b=3 in the cell-specific SRS bandwidth configuration. Figure 6-1 shows a cell-specific SRS bandwidth configuration tree. An SRS bandwidth can be 32 RBs, 16 RBs, 8 RBs, or 4 RBs.
Figure 6-1 Cell-specific SRS bandwidth configuration tree
To prevent overlaps between the SRS bandwidth, PUCCH bandwidth, and PRACH bandwidth, the cell-specific SRS bandwidth must be in a different bandwidth range from the PUCCH and PRACH bandwidths.
Table 6-2 through Table 6-5 list cell-specific SRS bandwidth configurations for different uplink bandwidths. In these tables, mSRS,0 indicates the cell-specific SRS bandwidth.
Table 6-2 Cell-specific SRS bandwidth configuration (6 RBs < Uplink bandwidth ≤ 40 RBs)
SRS Bandwidth Configuration Index
b=0
b=1
b=2
b=3
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
0
36
1
12
3
4
3
4
1
1
32
1
16
2
8
2
4
2
2
24
1
4
6
4
1
4
1
3
20
1
4
5
4
1
4
1
4
16
1
4
4
4
1
4
1
5
12
1
4
3
4
1
4
1
6
8
1
4
2
4
1
4
1
7
4
1
4
1
4
1
4
1
Table 6-3 Cell-specific SRS bandwidth configuration (40 RBs < Uplink bandwidth ≤ 60 RBs)
SRS Bandwidth Configuration Index
b=0
b=1
b=2
b=3
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
0
48
1
24
2
12
2
4
3
1
48
1
16
3
8
2
4
2
2
40
1
20
2
4
5
4
1
3
36
1
12
3
4
3
4
1
4
32
1
16
2
8
2
4
2
5
24
1
4
6
4
1
4
1
6
20
1
4
5
4
1
4
1
7
16
1
4
4
4
1
4
1
Table 6-4 Cell-specific SRS bandwidth configuration (60 RBs < Uplink bandwidth ≤ 80 RBs)
SRS Bandwidth Configuration Index
b=0
b=1
b=2
b=3
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
0
72
1
24
3
12
2
4
3
1
64
1
32
2
16
2
4
4
2
60
1
20
3
4
5
4
1
3
48
1
24
2
12
2
4
3
4
48
1
16
3
8
2
4
2
5
40
1
20
2
4
5
4
1
6
36
1
12
3
4
3
4
1
7
32
1
16
2
8
2
4
2
Table 6-5 Cell-specific SRS bandwidth configuration (80 RBs < Uplink bandwidth ≤ 110 RBs)
SRS Bandwidth Configuration Index
b=0
b=1
b=2
b=3
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
mSRS,b
Nb
0
96
1
48
2
24
2
4
6
1
96
1
32
3
16
2
4
4
2
80
1
40
2
20
2
4
5
3
72
1
24
3
12
2
4
3
4
64
1
32
2
16
2
4
4
5
60
1
20
3
4
5
4
1
6
48
1
24
2
12
2
4
3
7
48
1
16
3
8
2
4
2
b: indicates the level of the bandwidth tree.
mSRS,b: indicates the SRS bandwidth on level b.
Nb: indicates the number of leaf nodes on level b. The number is a multiple of the SRS bandwidth on level (b-1) relative to the SRS bandwidth on level b. The system bandwidth determines cell-specific SRS bandwidth configuration that a cell uses. You can run the CellSrsBandwidthCfg command to obtain the cell-specific SRS bandwidth configuration.
Based on the PUCCH bandwidth, the eNodeB selects a cell-specific SRS bandwidth configuration from Table 6-2, Table 6-3, Table 6-4, or Table 6-5. Based on radio conditions, the eNodeB adaptively allocates an SRS bandwidth to a UE. For example, if the system bandwidth of a cell is 50 RBs, the eNodeB selects the cell-specific SRS bandwidth configuration corresponding to SRS bandwidth configuration index 4 listed in Table 6-3 for the cell. Then, the eNodeB allocates an SRS bandwidth of 32 RBs, 16 RBs, 8 RBs, or 4 RBs to a UE in the cell.
In TDD mode:
  • If the AnSrsSimuTrans parameter is set to BOOLEAN_FALSE(False), the eNodeB adaptively configures the cell-specific SRS bandwidth based on the maximum PUCCH bandwidth.
    • If the PUCCH bandwidth increases, the eNodeB reduces the cell-specific SRS bandwidth. This avoids bandwidth conflict.
    • If the PUCCH bandwidth decreases, the eNodeB increases the cell-specific SRS bandwidth, and the frequency-selective scheduling bandwidth becomes large as well. This increases uplink gains.
      Based on the PUCCH bandwidth, the eNodeB selects a cell-specific SRS bandwidth configuration from Table 6-2, Table 6-4, or Table 6-5.
  • If the AnSrsSimuTrans parameter is set to BOOLEAN_TRUE(True), the eNodeB configures the SRS bandwidth based on the maximum bandwidth for the CQI on the PUCCH.

6.3 UE-Specific SRS


6.3.1 UE-Specific SRS Subframe

A UE sends SRSs on a subframe. The subframe is called a UE-specific SRS subframe.
3GPP TS 36.213 defines UE-specific SRS periodicities of 2 ms, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms, and 320 ms. UE-specific SRS subframes are a subset of cell-specific SRS subframes because UEs must transmit SRSs on configured cell-specific SRS subframes. UE-specific SRS periodicities and subframe offsets are jointly coded. The 10-bit ISRS parameter indicates UE-specific SRS periodicity and subframe offset configuration. Table 6-6 lists UE-specific SRS subframe configuration.
Table 6-6 UE-specific SRS subframe configuration
UE-specific SRS Subframe Configuration Index ISRS
SRS Periodicity (ms)
SRS Subframe Offset
0
2
0, 1
1
2
0, 2
2
2
1, 2
3
2
0, 3
4
2
1, 3
5
2
0, 4
6
2
1, 4
7
2
2, 3
8
2
2, 4
9
2
3, 4
10 – 14
5
ISRS– 10
15 – 24
10
ISRS– 15
25 – 44
20
ISRS– 25
45 – 84
40
ISRS– 45
85 – 164
80
ISRS– 85
165 – 324
160
ISRS– 165
325 – 644
320
ISRS– 325
645 – 1023
reserved
reserved
UE-specific SRS periodicity and subframe offset configuration requires 10 bits, of which 1 bit indicates a single SRS transmission or a periodic SRS transmission. UE-specific SRS subframe periodicity and offset are configured by radio resource control (RRC) signaling. Signaling overheads are reduced by jointly coding UE-specific SRS periodicities and subframe offsets.

6.3.2 UE-Specific SRS Period Adaptation

The eNodeB adaptively adjusts an SRS period based on SRS loads. This process is also known as SRS period adaptation. The SrsPeriodAdaptive parameter determines whether to enable or disable SRS period adaptation.
When the TddSrsCfgMode parameter is set to EXPERIENCE_FIRST(Experience First), TDD SRS loads are classified into lightly loaded, properly loaded, moderately congested, seriously congested, and extremely congested. A higher SRS load results in a longer SRS period for a newly admitted UE.
  • If the SrsPeriodAdaptive parameter is set to ON(On), the eNodeB adaptively adjusts the SRS period for a newly admitted UE based on SRS loads.
    • When SRS resources are lightly loaded, the eNodeB adaptively adjusts the SRS period for all admitted UEs in a cell to 5 ms. This reduces the SRS measurement interval for better user experience but lowers the SRS capacity of the cell.
    • When SRS resources are properly loaded, the eNodeB adaptively adjusts the SRS period for all admitted UEs in a cell to 10 ms. This reduces the SRS measurement interval for better user experience but lowers the SRS capacity of the cell.
    • When SRS resources are moderately congested, the eNodeB adaptively adjusts the SRS period for all admitted UEs in a cell to 20 ms. This allows more UEs to access the cell but degrades user experience.
    • When SRS resources are seriously congested, the eNodeB adaptively adjusts the SRS period for all admitted UEs in a cell to 40 ms. This allows more UEs to access the cell and achieves a tradeoff between the cell capacity and performance.
    • When SRS resources are extremely congested, the eNodeB adaptively adjusts the SRS period for all admitted UEs in a cell to 160 ms. This allows more UEs to access the cell and achieves a tradeoff between the cell capacity and performance.
  • When the SrsPeriodAdaptive parameter is set to OFF(Off), the eNodeB uses a fixed SRS period for all admitted UEs in a cell. The SRS period can be specified by the UserSrsPeriodCfg parameter and can be set to 5 ms, 10 ms, 20 ms, or 40 ms.
When the TddSrsCfgMode parameter is set to ACCESS_FIRST(Access First), only UE-specific SRS period adaptation is supported and the eNodeB preferentially uses the short SRS period.
When the TddSrsCfgMode parameter is set to EXPERIENCE_ENHANCED(Experience Enhanced), only UE-specific SRS period adaptation is supported. The eNodeB adaptively adjusts the SRS period based on the number of admitted UEs. That is, the eNodeB uses the short SRS period when there is a small number of admitted UEs and uses the long SRS period when there is a large number of admitted UEs.

6.3.3 UE-Specific SRS Bandwidth

A UE sends SRSs within a bandwidth. The bandwidth is called a UE-specific SRS bandwidth. 3GPP specifications define a maximum of four levels of SRS bandwidths which correspond to b=0, b=1, b=2, and b=3 in the cell-specific SRS bandwidth configuration.

6.4 SRS and ACK or NACK Processing

For the same UE, if SRSs and PUCCH ACKs or NACKs are simultaneously transmitted, Huawei eNodeB discards the SRSs or shortens the ACKs or NACKs.
  • If the AnSrsSimuTrans parameter is set to BOOLEAN_TRUE(True), SRSs and PUCCH ACKs or NACKs can be simultaneously transmitted. In this situation, PUCCH ACKs, NACKs, or SRs are transmitted in the shortened format.
  • If the AnSrsSimuTrans parameter is set to BOOLEAN_FALSE(False), SRSs and PUCCH ACKs or NACKs cannot be simultaneously transmitted. UEs discard SRSs and transmit only PUCCH ACKs, NACKs, or SRs.

6.5 SRS Multiplexing

An SRS multiplexing mode determines how UEs transmit SRSs using time-frequency resources. SRS multiplexing modes are classified into frequency division multiplexing (FDM) modes and code division multiplexing (CDM) modes.

FDM

The FDM mode allows UEs to transmit SRSs using different frequencies. FDM is classified into localized frequency division multiplexing (LFDM) and distributed frequency division multiplexing (DFDM).
  • L-FDM
    Different frequency-domain resources are used for different SRSs.
  • D-FDM
    SRS sequences are transmitted on subcarriers at intervals. If the repetition factor (RPF) is 2, SRS sequences are transmitted only on even-numbered or odd-numbered subcarriers. SRSs have a comb transmission interval, which is specified by the comb parameter. If the comb parameter is set to 0, SRS sequences are transmitted on even-numbered subcarriers. If the comb parameter is set to 1, SRS sequences are transmitted on odd-numbered subcarriers.

CDM

The CDM mode allows SRSs with the same subframe, bandwidth, and comb value to occupy the same time-frequency position. Codewords use cyclic shift sequences generated from the same Zadoff-Chu sequence. CDM supports a maximum of eight cyclic shift sequences.

6.6 SRS Frequency Hopping

SRS frequency hopping enables a UE to transmit SRSs on a small frequency band at one time and to transmit SRSs on another frequency band at a subsequent time. In this way, the eNodeB achieves sounding on the entire system bandwidth. SRS frequency hopping achieves channel quality measurements in the entire system bandwidth by using a small sounding bandwidth.

7 Related Features


7.1 Required Features

PHICH resource management is related to PHICH power control. If the channel quality is poor and PHICH power control is disabled, adjust the PHICH power first. If the PHICH demodulation performance does not improve, increase the number of PHICH groups by adjusting the PHICH configuration parameters and set the PhichDuration parameter to EXTENDED.

7.2 Mutually Exclusive Features

Physical resource management is a basic feature and can be used with all other features.
If the PhichDuration parameter is set to EXTENDED, the PDCCH symbol adaptation function does not take effect.

7.3 Impacted Features

If both PDCCH aggregation level adaptation and PDCCH power control are enabled, PDCCH power control takes effect only when the aggregation level decreases to one CCE or increases to eight CCEs.
PDCCH symbol adaptation assigns the remaining resources to the downlink scheduler. The scheduler then allocates the resources to the PDSCH.
Dynamic PUCCH resource adjustment assigns the remaining resources to the uplink scheduler. The scheduler then allocates the resources to the PUSCH.
Dynamic cell-specific SRS subframe adjustment assigns the remaining resources to the uplink scheduler. The scheduler then allocates the resources to the PUSCH.

8 Network Impact


8.1 System Capacity

  • PHICH
    PHICH resource overheads are determined by the PHICH duration and PHICH group quantity of a UE. A longer duration or a larger quantity requires more PHICH resources, thereby decreasing downlink system capacity.
  • PDCCH
    • The number of symbols occupied by a PDCCH determines the downlink system capacity. If a PDCCH occupies a larger number of symbols, causing higher PDCCH resource overheads, the available downlink system capacity decreases.
    • PDCCH aggregation level adaptation and closed-loop adjustment to the PDCCH aggregation level determine the uplink and downlink system capacity. If the eNodeB uses a proper aggregation level, the eNodeB can have optimal PDCCH demodulation performance and larger uplink and downlink system capacity.
    • CCE ratio adaptation determines the uplink and downlink system capacity. If the number of allocated CCEs is less than the required number, the uplink and downlink system capacity decreases.
  • PUCCH
    The CQI/SRI reporting period for PUCCH determines the user experience of downlink services and uplink system capacity. A short CQI/SRI reporting period ensures good user experience but reduces the uplink system capacity due to the increase of PUCCH resource overheads.
  • SRS
    SRS resource configuration determines the uplink system capacity. A short SRS period ensures good user experience. If the number of SRS UEs in a cell is set to a large value, SRS resources cause higher PUSCH resource overheads, and therefore the uplink system capacity decreases.

8.2 Network Performance

  • PHICH
    The PHICH group quantity determines PHICH demodulation performance. If the number of PHICH groups is set to a large value, the PHICH demodulation performance deteriorates, which may result in uplink-data transmission failures.
  • PDCCH
    After PDCCH symbol adaptation is enabled, the eNodeB ensures optimal uplink and downlink performance by adjusting the number of symbols occupied by a PDCCH based on the number of required CCEs. After PDCCH aggregation level adaptation and closed-loop adjustment to the PDCCH aggregation level are enabled, the NodeB has optimal PDCCH demodulation performance, which increases cell throughput and edge coverage.
  • PUCCH
    SRI resource configuration for the PUCCH determines user experience with uplink services, for example, delay. A short SRI period ensures good user experience. CQI period and ACK to downlink HARQ determine downlink performance. A short CQI period improves user experience with downlink AMC services.
  • SRS
    The SRI period determines uplink AMC services and timing. A short SRS period improves user experience with uplink AMC services and ensures accurate timing.

9 Engineering Guidelines for PDCCH Resource Management


9.1 When to Use PDCCH Resource Management

PDCCH Aggregation Level Adaptation

PDCCH aggregation level adaptation is enabled by default. No manual parameter setting is required. The default aggregation level for common control signaling is 4.

PDCCH Symbol Adaptation

PDCCH symbol adaptation is disabled by default. The number of initial symbols is 3 by default and can be changed based on the number of online UEs.

Closed-Loop Adjustment to the PDCCH Aggregation Level

Closed-loop adjustment to the PDCCH aggregation level is enabled by default. This is the recommended setting.

9.3 Deployment


9.3.2 Requirements

Operating Environment

N/A

Transmission Networking

N/A

License

N/A

Other Features

Before PDCCH symbol adaptation can be enabled, the PhichDuration parameter must be set to NORMAL.

9.3.3 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
  • Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
  • Network plan (negotiation not required): parameter values planned and set by the operator
  • User-defined: parameter values set by users

Required Data

The following table describes the parameters that must be set in the CellPdcchAlgo MO to configure PDCCH-related features in cells.
Parameter Name
Parameter ID
Setting Description
Source
Local cell ID
Set this parameter based on the network plan. This parameter specifies the local identity of a cell. Ensure that this parameter has been set in the related Cell MO.
Network plan (negotiation not required)
SignalCongregateLevel
This parameter specifies the CCE aggregation level for common control signaling. The value CONGREG_LV4 is recommended.
Network plan (negotiation not required)
PDCCH Aggregation Level CL Switch
This parameter specifies whether to enable closed-loop adjustment to the PDCCH aggregation level. The value ON(On) is recommended.
Network plan (negotiation not required)
Cce Ratio Adjust Switch
This parameter specifies whether to enable CCE ratio adaptation for the PDCCH. The value ON(On) is recommended.
Network plan (negotiation not required)
PDCCH Symbol Number Adjust Switch
The value ON(On) is recommended for non-ultra-high speed mobility scenarios in frequency division duplex (FDD) mode.
Network plan (negotiation not required)
PDCCH Initial Symbol Number
This parameter specifies the number of symbols initially occupied by a PDCCH. The value 1 is recommended when the PDCCH Symbol Number Adjust Switch parameter is set to ON(On).
Network plan (negotiation not required)

Scenario-specific Data

N/A

9.3.4 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 9-1 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
  • The MOs in Table 9-1 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs and then verify and save the file.
  • Some MOs in Table 9-1 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 9-1 Parameters related to PDCCH resource management
MO
Sheet in the Summary Data File
Parameter Group
Remarks
CELLPDCCHALGO
CELLPDCCHALGO
Local cell ID, Cce Ratio Adjust Switch, PDCCH Initial Symbol Number, PDCCH Symbol Number Adjust Switch, PDCCH Aggregation Level CL Switch
User-defined template

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
  1. Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000 client, or choose Advanced > Customize Summary Data File from the main menu of a CME client, to customize a summary data file for batch reconfiguration.
    NOTE:
    For context-sensitive help on a current task in the client, press F1.
  2. Choose CME > LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the CME client, to export the eNodeB data stored on the CME into the customized summary data file.
  3. In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and close the file.
  4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application> Import Data > Import Base Station Bulk Configuration Data from the main menu of the CME client, to import the summary data file into the CME.
  5. Choose CME > Planned Area > Export Incremental Scripts from the main menu of the M2000 client, or choose Area Management > Planned Area > Export Incremental Scripts from the main menu of the CME client, to export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
  1. In the planned data area, click Base Station in the upper left corner of the configuration window.
  2. In area 1 shown in Figure 9-1, select the eNodeB to which the MOs belong.
    Figure 9-1 MO search and configuration window
  3. On the Search tab page in area 2, enter an MO name, for example, CELL.
  4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
  5. Set the parameters in area 4 or 5.
  6. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

Using MML Commands

Run the MOD CELLPDCCHALGO command to set the Cce Ratio Adjust Switch, PDCCH Initial Symbol Number, PDCCH Symbol Number Adjust Switch, and PDCCH Aggregation Level CL Switch parameters.
NOTE:
The parameters mentioned in the preceding steps can be set based on the network plan. Unless otherwise specified, default values are recommended.

9.3.5 Activation Observation

PDCCH Aggregation Level Adaptation

The verification procedure is as follows:
  1. Use a single UE to access a cell with a 10 MHz bandwidth from the cell center and inject uplink and downlink User Datagram Protocol (UDP) packets at 60 Mbit/s.
  2. On the M2000 client, start DCI statistics monitoring by choosing Monitor > Signaling Trace > Signaling Trace Management > Cell Performance Monitoring > DCI Statistic Monitoring. Observe the real-time values of the following items:
    • PDCCH Use 1 CCE Num
    • PDCCH Use 2 CCE Num
    • PDCCH Use 4 CCE Num
    • PDCCH Use 8 CCE Num
    When the UE is at the cell center, the eNodeB prefers aggregation levels that lead to high code rates. Therefore, the expected result is that PDCCH Use 1 CCE Num or PDCCH Use 2 CCE Num has larger values than PDCCH Use 4 CCE Num and PDCCH Use 8 CCE Num. Figure 9-2 shows an example.
    Figure 9-2 DCI Statistic Monitoring (1)
  3. Move the UE to the cell edge and observe the real-time values of the following items:
    • PDCCH Use 1 CCE Num
    • PDCCH Use 2 CCE Num
    • PDCCH Use 4 CCE Num
    • PDCCH Use 8 CCE Num
    When the UE is at the cell edge, the eNodeB prefers aggregation levels that lead to low code rates. If the value of PDCCH Use 4 CCE Num or PDCCH Use 8 CCE Num increases, PDCCH aggregation level adaptation is activated. Figure 9-3 shows an example.
    Figure 9-3 DCI Statistic Monitoring (2)

Number of Initial Symbols

The verification procedure is as follows:
  1. Use a single UE to access a cell with a 10 MHz bandwidth from the cell center and inject uplink and downlink UDP packets at 60 Mbit/s.
  2. On the M2000 client, start DCI statistics monitoring by choosing Monitor > Signaling Trace > Signaling Trace Management > Cell Performance Monitoring > DCI Statistic Monitoring. Observe the real-time values of the following items:
    • CFI Engross 1 Symbol Stat. Num
    • CFI Engross 2 Symbol Stat. Num
    • CFI Engross 3 Symbol Stat. Num
    • CFI Engross 4 Symbol Stat. Num
    If the maximum number of symbols occupied by the PDCCH is the same as the configured value, the configuration takes effect. Figure 9-4 shows an example.
    Figure 9-4 DCI Statistic Monitoring (3)

9.3.6 Reconfiguration

The following table describes the parameters that must be set the CellPdcchAlgo MO to adjust the number of PDCCH symbols.
Parameter Name
Parameter ID
Source
Setting Description
PDCCH Initial Symbol Number
Network plan (negotiation not required)
The value can be changed based on the number of online UEs. This parameter specifies the number of symbols initially occupied by a PDCCH. The value 1 is recommended when the PDCCH Symbol Number Adjust Switch parameter is set to ON(On). When the PDCCH Symbol Number Adjust Switch parameter is set to OFF(Off), the value 4 is recommended for the 1.4 MHz bandwidth, and the value 3 is recommended for other bandwidth values.
PDCCH Symbol Number Adjust Switch
Network plan (negotiation not required)
The value ON(On) is recommended for non-ultra-high speed FDD scenarios, and the value OFF(Off) is recommended for other scenarios.

9.3.7 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 9.3.4 Initial Configuration. In the procedure, modify parameters according to Table 9-2.
Table 9-2 Parameters related to PDCCH resource management
MO
Sheet in the Summary Data File
Parameter Group
Recommended Value
CELLPDCCHALGO
CELLPDCCHALGO
Cce Ratio Adjust Switch
OFF(Off)
CELLPDCCHALGO
CELLPDCCHALGO
PDCCH Symbol Number Adjust Switch
OFF(Off)
CELLPDCCHALGO
CELLPDCCHALGO
PDCCH Aggregation Level CL Switch
OFF(Off)

Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 9-2. For detailed instructions, see 9.3.4 Initial Configuration.

Using MML Commands

Deactivating PDCCH symbol adaptation
Run the MOD CELLPDCCHALGO command with the PDCCH Symbol Number Adjust Switch parameter set to OFF(Off).
Deactivating closed-loop adjustment to the PDCCH aggregation level
Run the MOD CELLPDCCHALGO command with the PDCCH Aggregation Level CL Switch parameter set to OFF(Off).

9.3.8 MML Command Examples

NOTE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
// To check whether closed-loop adjustment to the PDCCH aggregation level has been enabled, run the following command:
LST CELLPDCCHALGO: LocalCellId=0;
// To activate closed-loop adjustment to the PDCCH aggregation level, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, PdcchAggLvlCLAdjustSwitch=ON;
// To activate CCE ratio adaptation, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, CceRatioAdjSwitch=ON;
// To activate PDCCH symbol adaptation, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=ON;
// To set the number of OFDM symbols initially occupied by a PDCCH, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, InitPdcchSymNum=3;
// To deactivate closed-loop adjustment to the PDCCH aggregation level, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, PdcchAggLvlCLAdjustSwitch=OFF;
// To deactivate PDCCH symbol adaptation, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch=OFF;
// To deactivate CCE ratio adaptation, run the following command:
MOD CELLPDCCHALGO: LocalCellId=0, CceRatioAdjSwitch=OFF;

10 Engineering Guidelines for PUCCH Resource Management


10.1 When to Use PUCCH Resource Management

SRI Period Adaptation

It is recommended that SRI period adaptation be enabled.

Dynamic PUCCH Resource Adjustment

Dynamic PUCCH resource adjustment is enabled by default. It is recommended that this feature be disabled in ultra-high speed mobility scenarios.

10.3 Deployment


10.3.2 Requirements

Operating Environment

N/A

Transmission Networking

N/A

License

N/A

10.3.3 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
  • Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
  • Network plan (negotiation not required): parameter values planned and set by the operator
  • User-defined: parameter values set by users

Required Data

The following table describes the parameters that must be set in the PUCCHCfg MO to configure PUCCH data.
Parameter Name
Parameter ID
Setting Description
Source
Delta shift
Set this parameter to DS2_DELTA_SHIFT(ds2) for a cell configured with the LBBPc and the normal CP.
Set this parameter to DS1_DELTA_SHIFT(ds1) for a cell configured with the LBBPd and the normal CP.
Set this parameter to DS3_DELTA_SHIFT(ds3) for a cell configured with the LBBPc, LBBPd, and the extended CP.
Network plan (negotiation not required)
The following table describes the parameter that must be set in the GlobalProcSwitch MO to configure SRI adaptation.
Parameter Name
Parameter ID
Setting Description
Source
SRI adaptive switch
The value ON(On) is recommended.
This parameter specifies whether to enable SRI adaptation.
Network plan (negotiation not required)
The following table describes the parameter that must be set in the CellPucchAlgo MO to configure the SRI light-load threshold.
Parameter Name
Parameter ID
Setting Description
Source
SRI Low Load Threshold
If the SubframeAssignment parameter is set to SA0 or SA1, the recommended value is 0 for bandwidths of 1.4 MHz and 3 MHz, and 5 for bandwidths of 5 MHz, 10 MHz, 15 MHz, and 20 MHz.
If the SubframeAssignment parameter is set to SA2 or SA5, the recommended value is 0 for all bandwidths.
Network plan (negotiation not required)
The following table describes the parameter that must be set in the CellStandardQci MO to configure the SRI period for disabled SRI adaptation.
Parameter Name
Parameter ID
Setting Description
Source
SRI Period
This parameter specifies the SRI period and is valid when the SriAdaptiveSwitch parameter is set to OFF(Off). For detailed setting suggestions, see section 5.1.2 SRI in PUCCH resource management.
Network plan (negotiation not required)

Scenario-specific Data

Scenario 1: Ultra-High-Speed Mobility
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure the PUCCH algorithm switch.
Parameter Name
Parameter ID
Setting Description
Source
PUCCH algorithm switch
It is recommended that the PucchSwitch check box under this parameter be cleared to disable dynamic PUCCH resource adjustment.
Network plan (negotiation not required)
Scenario 2: Non-Ultra-High-Speed Mobility
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure the PUCCH algorithm switch.
Parameter Name
Parameter ID
Setting Description
Source
PUCCH algorithm switch
It is recommended that the PucchSwitch check box under this parameter be selected to enable dynamic PUCCH resource adjustment.
Network plan (negotiation not required)

10.3.4 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 10-1 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
  • The MOs in Table 10-1 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs and then verify and save the file.
  • Some MOs in Table 10-1 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 10-1 Parameters related to PUCCH resource management
MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellPucchAlgo
CellPucchAlgo
Local cell ID, SRI Low Load Threshold
User-defined template
GlobalProcSwitch
GlobalProcSwitch
SRI adaptive switch
User-defined template
CellStandardQci
CellStandardQci
Local cell ID, QoS Class Indication, SRI Period
User-defined template
PUCCHCfg
PUCCHCfg
Local cell ID, Delta shift, ACK/SRI Channel Number, PUCCH Extended RB Number
User-defined template
CellAlgoSwitch
CellAlgoSwitch
Local cell ID, PUCCH algorithm switch
User-defined template

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
  1. Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000 client, or choose Advanced > Customize Summary Data File from the main menu of a CME client, to customize a summary data file for batch reconfiguration.
    NOTE:
    For context-sensitive help on a current task in the client, press F1.
  2. Choose CME > LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the CME client, to export the eNodeB data stored on the CME into the customized summary data file.
  3. In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and close the file.
  4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application> Import Data > Import Base Station Bulk Configuration Data from the main menu of the CME client, to import the summary data file into the CME.
  5. Choose CME > Planned Area > Export Incremental Scripts from the main menu of the M2000 client, or choose Area Management > Planned Area > Export Incremental Scripts from the main menu of the CME client, to export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
  1. In the planned data area, click Base Station in the upper left corner of the configuration window.
  2. In area 1 shown in Figure 10-1, select the eNodeB to which the MOs belong.
    Figure 10-1 MO search and configuration window
  3. On the Search tab page in area 2, enter an MO name, for example, CELL.
  4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
  5. Set the parameters in area 4 or 5.
  6. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

Using MML Commands

  1. Run the MOD CELLPUCCHALGO command to set the SRI Low Load Threshold parameter.
  2. Run the MOD GLOBALPROCSWITCH command to set the SRI adaptive switch parameter.
  3. Run the MOD CELLSTANDARDQCI command to set the SRI Period parameter.
  4. Run the MOD PUCCHCFG command to set the Delta shift parameter.
  5. Run the MOD CELLALGOSWITCH command with the PucchAlgoSwitch(PucchAlgoSwitch) check box selected or cleared under the PUCCH algorithm switch parameter.
    NOTE:
    The parameters mentioned in the preceding steps can be set based on the network plan. Unless otherwise specified, default values are recommended.

10.3.5 Activation Observation

Cyclic Shift Interval for the PUCCH

  1. Run the LST PUCCHCFG command and record the value of Delta shift. Figure 10-2 shows a sample command output.
    Figure 10-2 LST PUCCHCFG command output
  2. On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > Uu Interface Trace and click New to start Uu signaling tracing in a cell.
  3. Deactivate the cell, and activate the cell again. Then, check the IE deltaPUCCH-Shift in the first RRC_SYS_INFO message traced on the Uu interface. Figure 10-3 shows a sample RRC_SYS_INFO message. If the value of this IE is the same as the value of Delta shift recorded in Step 1, the configuration of the cyclic shift interval takes effect.
    Figure 10-3 RRC_SYS_INFO message

Dynamic PUCCH Resource Adjustment

  1. Run the MOD CELL command with the UlBandWidth and DlBandWidth parameters set to CELL_BW_N50, the FddTddInd parameter set to CELL_TDD, the SubframeAssignment parameter set to SA2, and the SpecialSubframePatterns parameter set to SSP7. Run the MOD CELLPDCCHALGO command with the PDCCH Initial Symbol Number parameter set to 1 and the PDCCH Symbol Number Adjust Switch parameter set to OFF(Off). Run the LST CELLPDCCHALGO command and record the values of PDCCH Initial Symbol Number and PDCCH Symbol Number Adjust Switch. Figure 10-4 shows a sample command output.
    Figure 10-4 LST CELLPDCCHALGO command output
  2. On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring and click New to start RB usage monitoring. Monitor the value of Uplink Pucch RB Num as shown in Figure 10-5.
    Figure 10-5 Uplink Pucch RB number (1)
  3. Run the MOD CELLPDCCHALGO command with the PDCCH Initial Symbol Number parameter set to 3 and the PDCCH Symbol Number Adjust Switch parameter set to OFF(Off).
  4. On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring and click New to start RB usage monitoring. Monitor the value of Uplink Pucch RB Num as shown in Figure 10-6. If the value of Uplink Pucch RB Num is greater than that observed in Step 2, dynamic PUCCH resource adjustment takes effect.
    Figure 10-6 Uplink Pucch RB number (2)

10.3.7 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 10.3.4 Initial Configuration. In the procedure, modify parameters according to Table 10-2.
Table 10-2 Parameters related to PUCCH resource management
MO
Sheet in the Summary Data File
Parameter Group
Recommended Value
GlobalProcSwitch
GlobalProcSwitch
SRI adaptive switch
OFF(Off)
CellAlgoSwitch
CellAlgoSwitch
PUCCH algorithm switch
PucchSwitch check box under this parameter cleared

Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 10-2. For detailed instructions, see 10.3.4 Initial Configuration.

Using MML Commands

Deactivating SRI transmission period adaptation
Run the MOD GLOBALPROCSWITCH command with the SRI adaptive switch set to OFF(Off).
Deactivating dynamic PUCCH resource adjustment
Run the MOD CELLALGOSWITCH command with the PucchSwitch(PucchSwitch) check box cleared under the PucchAlgoSwitch parameter.

10.3.8 MML Command Examples

NOTE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
// To modify the SRI period, run the following command:
MOD CELLSTANDARDQCI: LocalCellId=0, Qci=QCI9, SriPeriod=ms20;
// To deactivate SRI adaptation, run the following command:
MOD GLOBALPROCSWITCH: SriAdaptiveSwitch=OFF;
// To modify the cyclic shift interval for the PUCCH, the number of resource indexes allocated to SRIs and ACKs to downlink semi-persistent scheduling, the number of RBs for CQI reporting, and the number of extended PUCCH RBs, run the following command:
MOD PUCCHCFG: LocalCellId=0, DeltaShift=DS1_DELTA_SHIFT, NaSriChNum=6, CqiRbNum=1, PucchExtendedRBNum=1;
// To deactivate the PUCCH algorithm, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, PucchAlgoSwitch=PucchSwitch-0;

10.5 Parameter Optimization

To optimize the network performance in non-ultra-high-speed mobility scenarios, enable SRI period adaptation and dynamic PUCCH resource adjustment.

11 Engineering Guidelines for SRS Resource Management


11.1 When to Use SRS Resource Management

The following functions are enabled by default (the recommended setting):
  • SRS configuration indicator
  • Dynamic adjustment to the cell-specific SRS subframe configuration
  • UE-specific SRS period adaptation
The latter two functions can be used only when the SRS configuration indicator is enabled. In addition, the SRS configuration indicator must be enabled for the use of closed- and open-loop MIMO adaptation and beamforming.

11.3 Deployment


11.3.2 Requirements

Operating Environment

N/A

Transmission Networking

N/A

License

N/A

Other Features

N/A

11.3.3 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
  • Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
  • Network plan (negotiation not required): parameter values planned and set by the operator
  • User-defined: parameter values set by users

Required Data

The following table describes the parameters that must be set in the SRSCfg MO to configure SRS data.
Parameter Name
Parameter ID
Setting Description
Source
SRS ACK/NACK simultaneous transmission
The value BOOLEAN_TRUE(True) is recommended.
Network plan (negotiation not required)
SRS subframe configuration
The value SC0(0) is recommended for an eNodeB working in TDD mode.
Network plan (negotiation not required)
SRS Configuration Indicator
The value BOOLEAN_TRUE(True) is recommended. If this value is used, SRS resources are available in the cell and can be allocated to UEs.
Network plan (negotiation not required)
TDD SRS Configuration Mode
The value ACCESS_FIRST(Access First) is recommended. If this value is used, the number of UEs and the call attempt per second (CAPS) are preferentially ensured.
Network plan (negotiation not required)
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure the SRS algorithm switch.
Parameter Name
Parameter ID
Setting Description
Source
SoundingRS algorithm switch
It is recommended that the SrsSubframeRecfSwitch check box under this parameter be selected to enable dynamic cell-specific SRS subframe adjustment.
Network plan (negotiation not required)
The following table describes the parameter that must be set in the SrsAdaptiveCfg MO to configure SRS period adaptation and the UE-specific SRS period.
Parameter Name
Parameter ID
Setting Description
Source
SRS period adaptive switch
This parameter specifies whether to enable SRS period adaptation. The value ON(On) is recommended.
Network plan (negotiation not required)
User SRS period config
This parameter specifies the UE-specific SRS period. This parameter is valid when SrsPeriodAdaptive is set to OFF(Off). The value ms40(40ms) is recommended.
Network plan (negotiation not required)

Scenario-specific Data

N/A

11.3.4 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 11-1 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
  • The MOs in Table 11-1 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs and then verify and save the file.
  • Some MOs in Table 11-1 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 11-1 Parameters related to SRS resource management
MO
Sheet in the Summary Data File
Parameter Group
Remarks
SRSCfg
SRSCfg
Local cell ID, SRS subframe configuration, SRS ACK/NACK simultaneous transmission, SRS Configuration Indicator, TDD SRS Configuration Mode
A List sheet is recommended
CellAlgoSwitch
CellAlgoSwitch
Local cell ID, SoundingRS algorithm switch
A List sheet is recommended
SrsAdaptiveCfg
SrsAdaptiveCfg
SRS period adaptive switch, User SRS period config
A List sheet is recommended

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
  1. Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000 client, or choose Advanced > Customize Summary Data File from the main menu of a CME client, to customize a summary data file for batch reconfiguration.
    NOTE:
    For context-sensitive help on a current task in the client, press F1.
  2. Choose CME > LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the CME client, to export the eNodeB data stored on the CME into the customized summary data file.
  3. In the summary data file, set the parameters in the MOs listed in "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and close the file.
  4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application> Import Data > Import Base Station Bulk Configuration Data from the main menu of the CME client, to import the summary data file into the CME.
  5. Choose CME > Planned Area > Export Incremental Scripts from the main menu of the M2000 client, or choose Area Management > Planned Area > Export Incremental Scripts from the main menu of the CME client, to export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
  1. In the planned data area, click Base Station in the upper left corner of the configuration window.
  2. In area 1 shown in Figure 11-1, select the eNodeB to which the MOs belong.
    Figure 11-1 MO search and configuration window
  3. On the Search tab page in area 2, enter an MO name, for example, CELL.
  4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
  5. Set the parameters in area 4 or 5.
  6. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

Using MML Commands

  1. Run the MOD SRSCFG command to set the SRS subframe configuration, SRS ACK/NACK simultaneous transmission, SRS Configuration Indicator, and TDD SRS Configuration Mode parameters.
  2. Run the MOD CELLALGOSWITC command to set the SoundingRS algorithm switch parameter.
  3. Run the MOD SRSADAPTIVECFG command to set the SRS period adaptive switch and User SRS period config parameters.
    NOTE:
    The parameters mentioned in the preceding steps can be set based on the network plan. Unless otherwise specified, default values are recommended.

11.3.5 Activation Observation

SRS Function

  1. On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > Uu Interface Trace and click New to start Uu signaling tracing in a cell.
  2. Run the MOD SRSCFG command with the SRS Configuration Indicator parameter set to BOOLEAN_TRUE(True) and the TDD SRS Configuration Mode parameter set to EXPERIENCE_FIRST.
  3. Deactivate the cell, and activate the cell again. Then, check the value of setup IE in the soundingRS-UL-ConfigCommon IE of the first RRC_SYS_INFO message. If the soundingRS-UL-ConfigCommon IE contains the setup IE, the SRS function is enabled. Figure 11-2 shows a sample RRC_SYS_INFO message.
  4. Run the MOD SRSCFG command with the SRS Configuration Indicator parameter set to BOOLEAN_TRUE(True) and the TDD SRS Configuration Mode parameter set to ACCESS_FIRST.
    Figure 11-2 RRC_SYS_INFO message

Simultaneous Transmission of SRS and ACK/NACK

  1. On the M2000 client, run the LST SRSCFG command and record the value of SRS ACK/NACK simultaneous transmission. Figure 11-3 shows a sample command output.
    Figure 11-3 LST SRSCFG command output
  2. On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > Uu Interface Trace and click New to start Uu signaling tracing in a cell.
  3. Deactivate the cell, and activate the cell again. Then, check the value of the ackNackSRS-SimultaneousTransmission IE in the first RRC_SYS_INFO message traced on the Uu interface as shown in Figure 11-4. If the value of this IE is the same as the value of SRS ACK/NACK simultaneous transmission recorded in Step 1, the parameter setting takes effect.
    Figure 11-4 RRC_SYS_INFO message

11.3.7 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 11.3.4 Initial Configuration. In the procedure, modify parameters according to Table 11-2.
Table 11-2 Parameters related to SRS resource management
MO
Sheet in the Summary Data File
Parameter Group
Recommended Value
CellAlgoSwitch
CellAlgoSwitch
SoundingRS algorithm switch
SrsSubframeRecfSwitch check box under this parameter cleared
SrsAdaptiveCfg
SrsAdaptiveCfg
SRS period adaptive switch
OFF(Off)
SRSCFG
SRSCFG
SRS Configuration Indicator
BOOLEAN_FALSE(False)

Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 11-2. For detailed instructions, see 11.3.4 Initial Configuration.

Using MML Commands

  • Deactivating SRS-related features
    • Scenario 1: The LBBPd is used as the baseband unit.
      Run the MOD SRSCFG command with the SRS Configuration Indicator parameter set to BOOLEAN_FALSE(False).
      Adjusting the SRS Configuration Indicator parameter will interrupt the communication for a short period. After the deactivation, the eNodeB does not allocate SRS resources for UEs in the cell, and other SRS-related functions do not work. In addition, the performance open-loop and closed-loop MIMO adaptation are adversely affected.
    • Scenario 2: The LBBPc is used as the baseband unit.
      In this scenario, SRS resource allocation cannot be deactivated.
  • Deactivating dynamic adjustment to cell-specific SRS subframe configuration
    On the M2000 client, run the MOD CELLALGOSWITCH command with the SrsSubframeRecfSwitch(SrsSubframeRecfSwitch) check box cleared under the SoundingRS algorithm switch parameter.
  • Deactivating UE-specific SRS period adaptation
    Run the MOD SRSADAPTIVECFG command to set the User SRS period config parameter and deactivate UE-specific SRS period adaptation.

11.3.8 MML Command Examples

NOTE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
// To modify the SRS configuration, run the following command:
MOD SRSCFG: LocalCellId=0, SrsSubframeCfg=SC0, AnSrsSimuTrans=BOOLEAN_TRUE, SrsCfgInd=TRUE, TddSrsCfgMode=EXPERIENCE_FIRST;
// To activate dynamic adjustment to the cell-specific SRS subframe configuration, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, SrsAlgoSwitch=SrsSubframeRecfSwitch-1;
// To deactivate SRS period adaptation and set the UE specific SRS period, run the following command:
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=OFF, UserSrsPeriodCfg=ms40;
// To deactivate SRS-related features, run the following command:
MOD SRSCFG: LocalCellId=0, SrsCfgInd=FALSE;
// To deactivate dynamic cell-specific SRS subframe adjustment, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, SrsAlgoSwitch=SrsSubframeRecfSwitch-0;
// To deactivate UE specific SRS period adaptation, run the following command:
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=OFF, UserSrsPeriodCfg=ms40;

11.4 Performance Monitoring

If the SRS Configuration Indicator parameter is set to BOOLEAN_TRUE(True), SRS monitoring can be performed.

Cell-Specific SRS Bandwidth

  1. Run the LST CELL command to query the cell uplink bandwidth.
  2. Run the DSP SRSCFG command to query the current cell-specific SRS bandwidth configuration, as shown in Figure 11-5.
    Figure 11-5 Querying cell-specific SRS bandwidth configuration
  3. Based on the cell uplink, search 6.2.2 Cell-specific SRS Bandwidth for the actual cell-specific SRS bandwidth corresponding to the current cell-specific SRS bandwidth configuration.
Check the ratio of the cell-specific SRS bandwidth to the cell uplink bandwidth. A higher ratio indicates that this bandwidth provides higher uplink coverage, which benefits uplink frequency-selective scheduling, link adaptation, and power control.

Cell-Specific SRS Subframe

  1. On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > Uu Interface Trace and click New to start Uu signaling tracing in the cell, as shown in Figure 11-6.
    Figure 11-6 Querying cell-specific SRS Subframe configuration
  2. Search Table 6-1 for the cell-specific SRS subframe period and subframe offset corresponding to the value of srs-SubframeConfig.
Check the ratio of the number of cell-specific SRS subframes to the total number of subframes in the cell during a period of time. A higher ratio indicates more resources occupied by SRSs, more resources available in the cell, but less resources allocated for the PUSCH. Check where the number of cell-specific SRS subframes changes during the tracing. If there is no RRC_SYS_INFO message in the Uu tracing result, the number does not change.

11.5 Parameter Optimization

To optimize the network performance, enable the SRS configuration indicator, dynamic adjustment to the cell-specific SRS subframe configuration, and UE-specific SRS period adaptation features in all scenarios.

12 Parameters

Table 12-1 Parameter description
MO Parameter ID MML Command Feature ID Feature Name Description
CellAlgoSwitch PUSCHMaxRBPUCCHAdjSwitch MOD CELLALGOSWITCH
LST CELLALGOSWITCH
None None Meaning: Indicates the switch used to control whether PUCCH resources are allocated based on the UL peak rate. If this switch is turned on, resources are flexibly allocated to PUCCH. When there is only a few UEs, the PUCCH is allocated with less RBs. This maximizes the number of PUSCH RBs available to each UE.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
PHICHCfg PhichDuration MOD PHICHCFG
LST PHICHCFG
LBFD-002003 / TDLBFD-002003
LBFD-002009 / TDLBFD-002009
Physical Channel Management
Broadcast of system information
Meaning: Indicates the type of the PHICH duration. If this parameter is set to NORMAL, the number of OFDM symbols occupied by the PDCCH can be automatically adjusted. If this parameter is set to EXTENDED, the number of OFDM symbols occupied by the PDCCH cannot be automatically adjusted. For a cell with a 1.4 MHz bandwidth, the number of OFDM symbols occupied by the PDCCH can be 3 or 4. For a cell with other bandwidths, the number of OFDM symbols occupied by the PDCCH is 3.
GUI Value Range: NORMAL, EXTENDED
Unit: None
Actual Value Range: NORMAL, EXTENDED
Default Value: NORMAL
PHICHCfg PhichResource MOD PHICHCFG
LST PHICHCFG
LBFD-002003 / TDLBFD-002003
LOFD-001051
LBFD-002009 / TDLBFD-002009
Physical Channel Management
Compact Bandwidth
Broadcast of system information
Meaning: Indicates a coefficient that is used to calculate the resources used by the PHICH for the cell. It corresponds to the Ng parameter in the protocol. For details on the usage of the Ng parameter, see 3GPP TS 36.211.
GUI Value Range: ONE_SIXTH, HALF, ONE, TWO
Unit: None
Actual Value Range: ONE_SIXTH, HALF, ONE, TWO
Default Value: ONE
CellPdcchAlgo PdcchSymNumSwitch MOD CELLPDCCHALGO
LST CELLPDCCHALGO
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates the switch that is used to control whether to enable or disable dynamic adjustment of the number of OFDM symbols occupied by the PDCCH.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
CellPdcchAlgo CceRatioAdjSwitch MOD CELLPDCCHALGO
LST CELLPDCCHALGO
LBFD-001001 / TDLBFD-001001
TDLOFD-009004
3GPP R8 Specifications
ADAPATIVE CCE AGGREGATION
Meaning: Indicates the CCE ratio adjustment switch for the PDCCH. If this switch is turned on, the resource allocation algorithm of the PDCCH dynamically adjusts the UL and DL CCE ratios within each transmission time interval (TTI) based on CCE usages in UL and DL. If this switch is turned off, the UL and DL CCE ratios are not dynamically adjusted.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
CellPdcchAlgo PdcchAggLvlCLAdjustSwitch MOD CELLPDCCHALGO
LST CELLPDCCHALGO
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates the switch used to enable or disable closed-loop adjustment to the PDCCH aggregation level. If this switch is turned on, PDCCH aggregation level is adjusted based on the block error rate (BLER) of the PDCCH. If this switch is turned off, PDCCH aggregation level is not adjusted based on the BLER of the PDCCH.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
CellPdcchAlgo ComSigCongregLv MOD CELLPDCCHALGO
LST CELLPDCCHALGO
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates the CCE aggregation level for common signaling.
GUI Value Range: CONGREG_LV4, CONGREG_LV8
Unit: None
Actual Value Range: CONGREG_LV4, CONGREG_LV8
Default Value: CONGREG_LV4
CellPdcchAlgo InitPdcchSymNum MOD CELLPDCCHALGO
LST CELLPDCCHALGO
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates the number of OFDM symbols initially occupied by the PDCCH. If the switch for dynamic adjustment of the number of OFDM symbols occupied by the PDCCH is turned off, this parameter indicates the number of OFDM symbols that are always occupied by the PDCCH. If the switch is turned on and the bandwidth is 1.4 MHz or 3 MHz, the PDCCH occupies 4 or 3 OFDM symbols, in this scenario, this parameter cannot be manually set.. If the switch is turned on and the bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz, the eNodeB adjusts the number of OFDM symbols in the range of 1, 2, and 3 when this parameter is set to the default value 1, or in the range of 2 and 3 when this parameter is set to 2 or 3.
GUI Value Range: 1~4
Unit: None
Actual Value Range: 1~4
Default Value: 1
CellAlgoSwitch PucchAlgoSwitch MOD CELLALGOSWITCH
LST CELLALGOSWITCH
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: PucchSwitch: Indicates the switch used to enable or disable the PUCCH resource adjustment algorithm. If this switch is turned on, PUCCH resource adjustment is initiated when the PUCCH resources are insufficient or excessive. If this switch is turned off, PUCCH resource adjustment is disabled. PucchFlexCfgSwitch: Indicates whether to enable the PUCCH flexible configuration function. The switch setting does not take effect if the LBBPc is configured or the cell bandwidth is 1.4 MHz or 3 MHz.When PUCCH flexible configuration is enabled, UL ICIC and UL frequency hopping scheduling cannot be used. If this switch is turned on, the system allocates more RBs at the two ends of the frequency band for the PUCCH. The number of allocated RBs at each end equals the result of the PucchExtendedRBNum parameter value divided by 2. If this switch is turned off, this function is disabled. This parameter is valid only in FDD mode.
GUI Value Range: PucchSwitch(PucchSwitch), PucchFlexCfgSwitch(PucchFlexCfgSwitch)
Unit: None
Actual Value Range: PucchSwitch, PucchFlexCfgSwitch
Default Value: PucchSwitch:On, PucchFlexCfgSwitch:Off
CellAlgoSwitch DlPcAlgoSwitch MOD CELLALGOSWITCH
LST CELLALGOSWITCH
LBFD-002003 / TDLBFD-002003
LBFD-002009 / TDLBFD-002009
LBFD-002016 / TDLBFD-002016
Physical Channel Management
Broadcast of system information
Dynamic Downlink Power Allocation
Meaning: Indicates the switches used to enable or disable power control for PDSCH, PDCCH, and PHICH. PdschSpsPcSwitch: Indicates the switch for power control during semi-persistent scheduling on the PDSCH. If the switch is turned off, power is allocated evenly during semi-persistent scheduling on the PDSCH. If the switch is turned on, power control is applied during semi-persistent scheduling on the PDSCH, ensuring communication quality (indicated by IBLER) of VoIP services in the QPSK modulation scheme. PhichInnerLoopPcSwitch: Indicates the switch for PHICH inner-loop power control. If the switch is turned off, only the initial transmit power for the PHICH is set. If the switch is turned on, the eNodeB controls the physical channel transmit power to enable the receive SINR to converge to the target SINR. PdcchPcSwitch: Indicates the switch for PDCCH power control. If the switch is turned off, power is allocated evenly to PDCCH. If the switch is turned on, power allocated to PDCCH is adjusted dynamically. EDlMaxTXPwrSwitch: Indicates the switch for enhanced maximum TX power of the cell. If this switch is turned off, the maximum TX power of the cell is determined by the reference signal (RS) power and the scaling factor indexes Pa and Pb. If this switch is turned on, the maximum TX power of the cell can be increased to improve the RB usage in the cell. This switch has no impact on the TDD 20M or 10M cell.
GUI Value Range: PdschSpsPcSwitch, PhichInnerLoopPcSwitch, PdcchPcSwitch, EDlMaxTXPwrSwitch
Unit: None
Actual Value Range: PdschSpsPcSwitch, PhichInnerLoopPcSwitch, PdcchPcSwitch, EDlMaxTXPwrSwitch
Default Value: PdschSpsPcSwitch:Off, PhichInnerLoopPcSwitch:Off, PdcchPcSwitch:On, EDlMaxTXPwrSwitch:Off
CellPdcchAlgo CceUseRatio MOD CELLPDCCHALGO
LST CELLPDCCHALGO
LBFD-001001 / TDLBFD-001001
TDLOFD-009005
3GPP R8 Specifications
REDUCE SCHEDULE USER IN EACH TTI
Meaning: Indicates the upper limit for the CCE usage within each transmission time interval (TTI). When the switch for dynamically adjusting the number of OFDM symbols on the PDCCH is turned on, the parameter setting is invalid, that is, the CCE usage within each TTI cannot be limited. This parameter is valid only in TDD mode.
GUI Value Range: 1~100
Unit: %
Actual Value Range: 1~100
Default Value: 100
GlobalProcSwitch SriAdaptiveSwitch MOD GLOBALPROCSWITCH
LST GLOBALPROCSWITCH
LBFD-002025 / TDLBFD-002025
LOFD-001015 / TDLOFD-001015
Basic Scheduling
Enhanced Scheduling
Meaning: Indicates whether to enable scheduling request indication (SRI) adaptation. If this switch is turned on, the SRI period adaptively changes based on the SRI algorithm. If this switch is turned off, the SRI period is the value of the SriPeriod parameter in the CellStandardQci MO.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
CellStandardQci SriPeriod MOD CELLSTANDARDQCI
LST CELLSTANDARDQCI
LBFD-002025 / TDLBFD-002025
LOFD-001015 / TDLOFD-001015
LBFD-002003 / TDLBFD-002003
Basic Scheduling
Enhanced Scheduling
Physical Channel Management
Meaning: Indicates the interval at which scheduling request indicators are sent.
GUI Value Range: ms5(SRI 5ms), ms10(SRI 10ms), ms20(SRI 20ms), ms40(SRI 40ms), ms80(SRI 80ms)
Unit: None
Actual Value Range: ms5, ms10, ms20, ms40, ms80
Default Value: ms10(SRI 10ms)
CellPucchAlgo SriLowLoadThd MOD CELLPUCCHALGO
LST CELLPUCCHALGO
None None Meaning: Indicates the threshold for the low load state of the SRI resources. The SRI resources enter the low load state if the PUCCH resource allocation algorithm detects that the number of admitted UEs is smaller than the value of this parameter.
GUI Value Range: 0~50
Unit: None
Actual Value Range: 0~50
Default Value: 10
PUCCHCfg DeltaShift MOD PUCCHCFG
LST PUCCHCFG
LBFD-001001 / TDLBFD-001001
LBFD-002003 / TDLBFD-002003
3GPP R8 Specifications
Physical Channel Management
Meaning: Indicates the interval between cyclic shifts used for the PUCCH. The interval between cyclic shifts used for the PUCCH can be acquired based on the average delay spread in the cell, where the average delay spread is acquired based on the networking environment. The parameter value DS1_DELTA_SHIFT is not supported by the LBBPc. If a cell is established on an LBBPc but this parameter is set to DS1_DELTA_SHIFT, the value of this parameter is automatically changed to DS2_DELTA_SHIFT when this parameter takes effect. For details, see 3GPP TS 36.211.
GUI Value Range: DS1_DELTA_SHIFT(ds1), DS2_DELTA_SHIFT(ds2), DS3_DELTA_SHIFT(ds3)
Unit: None
Actual Value Range: DS1_DELTA_SHIFT, DS2_DELTA_SHIFT, DS3_DELTA_SHIFT
Default Value: DS1_DELTA_SHIFT(ds1)
SRSCfg SrsCfgInd MOD SRSCFG
LST SRSCFG
LBFD-001001 / TDLBFD-001001
LBFD-002003 / TDLBFD-002003
3GPP R8 Specifications
Physical Channel Management
Meaning: Indicates whether to configure SRSs for UEs in a cell. The parameter value TRUE indicates that SRS resources are available in the cell and SRSs can be configured for UEs in the cell. The parameter value FALSE indicates that SRS resources are not available in the cell and SRSs cannot be configured for any UE in the cell. This parameter value is valid only for cells established on an LBBPd. If a cell is established on an LBBPc and SRS resources are available in the cell, SRSs can be configured for UEs in the cell.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)
SRSCfg SrsSubframeCfg MOD SRSCFG
LST SRSCFG
LBFD-001001 / TDLBFD-001001
LBFD-002003 / TDLBFD-002003
3GPP R8 Specifications
Physical Channel Management
Meaning: Indicates the index of the SRS subframe configuration for the cell. The value SCn, where n is variable, represents configuration n. For example, the value SC0 indicates subframe configuration 0, and the value SC1 indicates subframe configuration 1. If the cell operates in FDD mode, the value SC15 is reserved. If the cell operates in TDD mode, the values SC14 and SC15 are reserved. The reserved values cannot be used. For the relationship between the subframe configuration index and the cell-specific subframe cycle/offset, see 3GPP TS 36.211. In FDD mode, this parameter is permanently valid. In TDD mode, this parameter is valid only if TddSrsCfgMode is set to EXPERIENCE_FIRST.
GUI Value Range: SC0(0), SC1(1), SC2(2), SC3(3), SC4(4), SC5(5), SC6(6), SC7(7), SC8(8), SC9(9), SC10(10), SC11(11), SC12(12), SC13(13), SC14(14)
Unit: None
Actual Value Range: SC0, SC1, SC2, SC3, SC4, SC5, SC6, SC7, SC8, SC9, SC10, SC11, SC12, SC13, SC14
Default Value: SC3(3)
SRSCfg TddSrsCfgMode MOD SRSCFG
LST SRSCFG
LBFD-001001 / TDLBFD-001001
LBFD-002003 / TDLBFD-002003
3GPP R8 Specifications
Physical Channel Management
Meaning: Indicates the TDD SRS configuration to be used. If this parameter is set to ACCESS_FIRST, the TDD SRS configuration that is designed to preferentially guarantee the specifications (for example, accessed UEs and CAPS) is used. If this parameter is set to EXPERIENCE_FIRST, the TDD SRS configuration that is designed to preferentially guarantee user experience (for example, beamforming performance) is used. CAPS is short for call attempt per second. If this parameter is set to EXPERIENCE_ENHANCED, users can get better DL user experience than that in EXPERIENCE_FIRST mode. This parameter cannot be set to EXPERIENCE_ENHANCED if the LBBPc is used. If a cell is established on an LBBPc but this parameter is set to EXPERIENCE_ENHANCED, EXPERIENCE_ENHANCED is automatically changed to EXPERIENCE_FIRST when this parameter takes effect. This parameter is valid only in TDD mode.
GUI Value Range: ACCESS_FIRST(Access First), EXPERIENCE_FIRST(Experience First), EXPERIENCE_ENHANCED(Experience Enhanced)
Unit: None
Actual Value Range: ACCESS_FIRST, EXPERIENCE_FIRST, EXPERIENCE_ENHANCED
Default Value: ACCESS_FIRST(Access First)
CellAlgoSwitch SrsAlgoSwitch MOD CELLALGOSWITCH
LST CELLALGOSWITCH
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates the switch used to enable or disable change in the cell-specific SRS subframe configuration (that is, the adjustment on the setting of the SrsSubframeCfg parameter). If the switch is turned on, the algorithm dynamically adjusts the SRS subframe configuration based on the usage of cell resources. If the switch is turned off, the algorithm uses the initial configuration and does not perform dynamic switching.
GUI Value Range: SrsSubframeRecfSwitch(SrsSubframeRecfSwitch)
Unit: None
Actual Value Range: SrsSubframeRecfSwitch
Default Value: SrsSubframeRecfSwitch:On
SRSCfg CellSrsBandwidthCfg DSP SRSCFG LBFD-002003 / TDLBFD-002003 Physical Channel Management Meaning: Indicates the cell-specific SRS bandwidth. It corresponds to the srs-BandwidthConfig parameter in the protocol. For details, see 3GPP TS 36.211.
GUI Value Range: BW0(BW0), BW1(BW1), BW2(BW2), BW3(BW3), BW4(BW4), BW5(BW5), BW6(BW6), BW7(BW7), INVALID_BANDWIDTH(Invalid bandwidth)
Unit: None
Actual Value Range: BW0, BW1, BW2, BW3, BW4, BW5, BW6, BW7, INVALID_BANDWIDTH
Default Value: None
SRSCfg AnSrsSimuTrans MOD SRSCFG
LST SRSCFG
LBFD-001001
LBFD-002003
3GPP R8 Specifications
Physical Channel Management
Meaning: Indicates whether the sounding reference signal (SRS) of a UE and the ACK/NACK or scheduling request (SR) on the PUCCH are allowed to use the same time resources for simultaneous transmission. If this parameter is set to BOOLEAN_FALSE, simultaneous transmission is not allowed. In this situation, the UE discards the SRS and only transmits the ACK/NACK or SR on the PUCCH. If this parameter is set to BOOLEAN_TRUE, simultaneous transmission is allowed. In this situation, the UE transmits truncated ACK/NACK or SR. For details, see 3GPP TS 36.211.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)
SrsAdaptiveCfg SrsPeriodAdaptive MOD SRSADAPTIVECFG
LST SRSADAPTIVECFG
LBFD-002025 / TDLBFD-002025 Basic Scheduling Meaning: Indicates whether to enable or disable SRS period adaptation. If this parameter is set to ON, the SRS period adaptively changes based on the SRS algorithm. If this parameter is set to OFF, the SRS period is the specified by the UserSrsPeriodCfg parameter.If the parameter TddSrsCfgMode is set to ACCESS_FIRST or EXPERIENCE_ENHANCED,this parameter setting is invalid.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
SrsAdaptiveCfg UserSrsPeriodCfg MOD SRSADAPTIVECFG
LST SRSADAPTIVECFG
LBFD-002025 / TDLBFD-002025 Basic Scheduling Meaning: Indicates the fixed SRS period. A fixed SRS period is used when SRS period adaptation is disabled.
GUI Value Range: ms5(5ms), ms10(10ms), ms20(20ms), ms40(40ms)
Unit: ms
Actual Value Range: ms5, ms10, ms20, ms40
Default Value: ms40(40ms)
CellPdcchAlgo LocalCellId LST CELLPDCCHALGO
MOD CELLPDCCHALGO
None None Meaning: Indicates the Local ID of the cell. It uniquely identifies a cell within a BS.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
Default Value: None
Cell SubframeAssignment ADD CELL
MOD CELL
LST CELL
LBFD-002009 / TDLBFD-002009
TDLBFD-00100701
TDLOFD-00102601
Broadcast of system information
uplink-downlink subframe configuration type1&2
uplink-downlink subframe configuration type 0/5
Meaning: Indicates the ratio of UL subframes to DL subframes in a TDD cell. For details, see 3GPP TS 36.211.
GUI Value Range: SA0(SA0), SA1(SA1), SA2(SA2), SA3(SA3), SA4(SA4), SA5(SA5), SA6(SA6)
Unit: None
Actual Value Range: SA0, SA1, SA2, SA3, SA4, SA5, SA6
Default Value: SA0(SA0)

Budi Prasetyo

About Budi Prasetyo

All About LTE

Subscribe to this Blog via Email :