800 MHz Self-Interference Cancellation(ERAN7.0_01)

eRAN

800 MHz Self-interference Cancellation Feature Parameter Description Issue

01

Date

2014-04-26

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2014-04-26)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

eRAN 800 MHz Self-interference Cancellation Feature Parameter Description

Contents

Contents 1 About This Document..................................................................................................................1 1.1 Scope..............................................................................................................................................................................1 1.2 Intended Audience..........................................................................................................................................................1 1.3 Change History...............................................................................................................................................................1 1.4 Differences Between eNodeB Types..............................................................................................................................2

2 Overview.........................................................................................................................................3 3 Technical Description...................................................................................................................4 4 Related Features.............................................................................................................................6 5 Network Impact.............................................................................................................................7 6 Engineering Guidelines...............................................................................................................8 6.1 When to Use 800 MHz Self-interference Cancellation..................................................................................................8 6.2 Required Information.....................................................................................................................................................8 6.3 Planning..........................................................................................................................................................................8 6.4 Deployment....................................................................................................................................................................9 6.4.1 Requirements...............................................................................................................................................................9 6.4.2 Data Preparation..........................................................................................................................................................9 6.4.3 Precautions.................................................................................................................................................................10 6.4.4 Activation..................................................................................................................................................................10 6.4.5 Activation Observation..............................................................................................................................................12 6.4.6 Reconfiguration.........................................................................................................................................................13 6.4.7 Deactivation...............................................................................................................................................................13 6.5 Performance Monitoring...............................................................................................................................................14 6.6 Parameter Optimization................................................................................................................................................14 6.7 Troubleshooting............................................................................................................................................................14

7 Parameters.....................................................................................................................................15 8 Counters........................................................................................................................................20 9 Glossary.........................................................................................................................................21 10 Reference Documents...............................................................................................................22 Issue 01 (2014-04-26)


ii


1

1 About This Document

About This Document

1.1 Scope This document describes LOFD-001067 800M Self-interference Cancellation, including its technical principles, related features, network impact, and engineering guidelines. This document applies to the following types of eNodeBs. eNodeB Type

Model

Macro

3900 series eNodeB

Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases. This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB.

1.2 Intended Audience This document is intended for personnel who: l

Need to understand the features described herein

l

Work with Huawei products

1.3 Change History This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows: l Issue 01 (2014-04-26)

Feature change Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

1


1 About This Document

Changes in features and parameters of a specified version as well as the affected entities l

Editorial change Changes in wording or addition of information and any related parameters affected by editorial changes. Editorial change does not specify the affected entities.

eRAN7.0 01 (2014-04-26) This issue does not include any changes.

eRAN7.0 Draft B (2014-03-07) This issue includes the following changes. Change Type

Change Description

Parameter Change

Affected Entity

Feature change

None

None

N/A

Editorial change

Added 1.4 Differences Between eNodeB Types, which describes differences in feature support between eNodeB types.

None

N/A

eRAN7.0 Draft A (2014-01-20) Compared with Issue 01 (2013-04-28) of eRAN6.0, Draft A (2014-01-20) of eRAN7.0 includes the following changes. Change Type

Change Description

Parameter Change

Feature change

None

None

Changed the name of Huawei mobile element management system from M2000 to U2000.

None

Revised Engineering Guidelines.

None

Editorial change

1.4 Differences Between eNodeB Types The features described in this document apply only to macro eNodeBs.

Issue 01 (2014-04-26)


2


2 Overview

2

Overview

This document describes the optional feature LOFD-001067 800M Self-interference Cancellation, which only applies to 3900 series base stations in frequency division duplex (FDD) mode. NOTE

This feature does not apply to the LampSite solution.

A cell that operates in the 800 MHz frequency band (band 20) has an 11 MHz duplex frequency separation, as shown in Figure 2-1. Therefore, when a UE simultaneously transmits and receives data, the uplink causes interference to the downlink and the interference leads to deterioration in the downlink receiver sensitivity. The degrees of interference and deterioration depend on the UE's duplex frequency separation, transmit power, and positions of uplink and downlink physical resource blocks (PRBs). The degrees also depend on the UE's transmit power and radio frequency (RF) component specifications. Figure 2-1 shows the 800 MHz frequency band. Figure 2-1 800 MHz frequency band

The 800 MHz self-interference cancellation feature applies to the following scenario: l

UEs perform uplink and downlink services at the same time.

l

UEs have low specifications.

l

UEs' uplink signals cause intolerant interference to their downlink signals.

This feature does not apply to scenarios where there is no self-interference. Issue 01 (2014-04-26)


3


3

3 Technical Description

Technical Description

800 MHz self-interference is the interference that a UE's signal transmission induces on the UE's signal reception (that is, uplink-to-downlink interference) in a cell that operates in the 800 MHz frequency band. Self-interference is restricted by the RF component specifications of the UE and the narrow duplex frequency separation of the 800 MHz frequency band. Self-interference mainly consists of intermodulation (IM) interference, including IM2, IM3, IM5, and IM7, which correspond to IM orders. The strength of self-interference is determined by the UE's transmit power and intermediate frequency (IF) performance, mainly referring to the duplex frequency separation and non-linear power amplifier. NOTE

l IM interference occurs when two or more interfering signals reach a UE's receiver at the same time. The frequency combination of these interfering signals is close or even identical to the frequency of a wanted signal because the power amplifier of the UE is non-linear. As a result, the UE cannot filter out these interfering signals, and these signals interfere with wanted signals. Different frequency combinations cause different IM interference. l Downlink-to-uplink interference is due to the eNodeB and can be mitigated by selecting RF components with good performance, which is usually done before network construction. By contrast, uplink-todownlink interference is due to UEs, but the UEs' types, models, and RF component specifications are uncontrollable. Therefore, the eNodeB needs to use some algorithms to reduce uplink-to-downlink interference. l In this document, self-interference refers to uplink-to-downlink interference on the UE side.

The impact of 800 MHz self-interference varies according to the bandwidth: l

A cell with a 5 MHz bandwidth has a wide frequency separation, and therefore the impact of self-interference caused by a narrow duplex frequency separation is small enough to ignore.

l

A cell with a 10 MHz, 15 MHz, or 20 MHz bandwidth has a narrow frequency separation and therefore self-interference exists. Downlink PRBs at any positions in the spectrum may experience interference from the uplink. When the UE is not tolerant of the interference, 800 MHz self-interference cancellation is required. NOTE

A cell operating in the 800 MHz frequency band (band 20) does not support a 1.4 MHz or 3 MHz bandwidth, according to 3GPP specifications.

Assume that a UE in a cell with a bandwidth of 20 MHz is allocated 50 PRBs for uplink transmission. In this case, the start position of uplink PRBs is at 836.5 MHz (831 MHz + 25 x 180 kHz = 836.5 MHz). Then, the red curve in Figure 3-1 represents self-interference. Issue 01 (2014-04-26)


4


3 Technical Description

Figure 3-1 Self-interference in the 800 MHz frequency band

NOTE

Figure 3-1 is only a schematic diagram because the result is obtained without the duplexer's suppression.

800 MHz self-interference cancellation is controlled by ImIcSwitch(ImIcSwitch) under CellAlgoSwitch.UlSchSwitch. If ImIcSwitch(ImIcSwitch) is selected, the eNodeB mitigates self-interference and increases downlink capacity by limiting the number of allocated uplink PRBs. For details, see Engineering Guidelines.

Issue 01 (2014-04-26)


5


4 Related Features

4

Related Features

Prerequisite Features The 800 MHz self-interference cancellation feature depends on LBFD-002025 Basic Scheduling.

Mutually Exclusive Features None

Impacted Features The 800 MHz self-interference cancellation feature has impacts on LBFD-002025 Basic Scheduling. With the 800 MHz self-interference cancellation feature, the eNodeB limits the number of allocated uplink PRBs to mitigate self-interference but this method reduces uplink throughput. The reduction degree of uplink throughput has a positive correlation with the reduction degree of uplink PRBs.

Issue 01 (2014-04-26)


6


5 Network Impact

5

Network Impact

System Capacity The 800 MHz self-interference cancellation feature limits the number of allocated uplink PRBs to mitigate self-interference and to increase downlink capacity. However, this method has a negative impact on uplink capacity. The reduction degree of uplink capacity has a positive correlation with the reduction degree of uplink PRBs.

Network Performance When the conditions for deploying the 800 MHz self-interference cancellation feature are fulfilled, this feature prevents a decrease in downlink throughput caused by self-interference but leads to a reduction in uplink throughput. The reduction degree of uplink throughput has a positive correlation with the reduction degree of uplink PRBs.

Issue 01 (2014-04-26)


7


6

6 Engineering Guidelines

Engineering Guidelines

6.1 When to Use 800 MHz Self-interference Cancellation Operators can use the 800 MHz self-interference cancellation feature to increase downlink throughput in the following scenario: l

The 800 MHz frequency band (band 20) is deployed to provide a bandwidth of 10 MHz, 15 MHz, or 20 MHz.

l

There are not more than one, two, or three UEs in a cell with the bandwidth of 10 MHz, 15 MHz, or 20 MHz, respectively.

l

UEs perform uplink and downlink services at the same time, and the uplink causes interference to the downlink.

l

A decrease in uplink throughput is acceptable.

6.2 Required Information Before deploying the 800 MHz self-interference cancellation feature, collect the following information: l

UE transmit power The transmit power of UEs can be obtained usually from section 6.2.2 in 3GPP TS 36.101 V10.6.0.

l

UE performance, including the duplex frequency separation, modulator performance, and non-linear power amplifier performance The performance of UEs can be obtained by analyzing and taking statistics on the performance indicators and specifications of the RF components that cause selfinterference.

6.3 Planning This feature does not require special network planning. Perform network planning for cells operating in the 800 MHz frequency band in the same way as you do for other cells. That is, Issue 01 (2014-04-26)


8



perform network planning based on information such as the inter-site spacing, eNodeB transmit power, UE transmit power, and throughput of CEUs.

6.4 Deployment 6.4.1 Requirements The operator has purchased and activated the license for the feature listed in Table 6-1. Table 6-1 License information for 800 MHz self-interference cancellation Feature ID

Feature Name

License Control Item

NE

Sales Unit

LOFD-001067

800M Selfinterference Cancellation

800M Selfinterference Cancellation (FDD)

eNodeB

per cell

l

Required information has been collected.

l

Cells that operate in the 800 MHz frequency band are likely to experience IM interference, a major component of uplink-to-downlink interference.

6.4.2 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: l

Network plan (negotiation required): parameter values planned by the operator and negotiated with the evolved packet core (EPC) or peer transmission equipment

l

Network plan (negotiation not required): parameter values planned and set by the operator

l

User-defined: parameter values set by users.

Required Data The following table describes the parameter that must be set in the CellAlgoSwitch MO.

Issue 01 (2014-04-26)


9



Parameter Name

Parameter ID

Data Source

Setting Notes

Uplink schedule switch

CellAlgoSwitch. UlSchSwitch

Network plan (negotiation not required)

This parameter specifies the switch ImIcSwitch for the 800 MHz selfinterference cancellation feature. If ImIcSwitch is turned on, the feature is enabled. If ImIcSwitch is turned off, the feature is disabled.

Scenario-specific Data None

6.4.3 Precautions When this feature is in effect, the GBR may not be ensured for uplink services.

6.4.4 Activation Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in Table 6-2 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 Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "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: l

The managed objects (MOs) in Table 6-2 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.

l

Some MOs in Table 6-2 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 6-2 Parameters related to 800 MHz self-interference cancellation

Issue 01 (2014-04-26)

MO

Sheet in the Summary Data File

Parameter Group

Remarks

CellAlgoSwitch

User-defined sheet

LocalCellID, CellAlgoSwitch

None


10



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: Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode), to customize a summary data file for batch reconfiguration. NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs listed in Table 6-2 and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME. Step 5 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

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: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.

Issue 01 (2014-04-26)


11



Figure 6-1 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

Using MML Commands Run the MOD CELLALGOSWITCH command with the ImIcSwitch check box selected under the CellAlgoSwitch.UlSchSwitch parameter.

MML Command Examples MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=ImIcSwitch-1;

6.4.5 Activation Observation This section describes how to verify the activation when the UEs in the cell center or on the cell edge are experiencing high traffic in both the uplink and downlink. The observation procedure is as follows: l Issue 01 (2014-04-26)

Starting cell performance monitoring on the U2000 client Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

12



Step 1 Choose Monitoring > Signaling Trace > Signaling Trace Management. Step 2 In the navigation tree on the left of the Signaling Trace Management window, choose Cell Performance Monitoring > General Throughput Monitoring and click New. This task measures the downlink data throughput at the RLC layer, which is indicated by Cell Downlink RLC Throughput(bps). Step 3 Compare the measurement results before and after deploying 800 MHz self-interference cancellation. If the counter value increases, the feature is successfully activated. ----End l

Starting UE performance monitoring on the U2000 client

Step 1 Choose Monitoring > Signaling Trace > Signaling Trace Management. Step 2 In the navigation tree on the left of the Signaling Trace Management window, choose User Performance Monitoring > Throughput Monitoring and click New. This task measures the downlink data throughput at the RLC layer, which is indicated by Downlink RLC Throughput(bps). Step 3 Compare the measurement results before and after deploying 800 MHz self-interference cancellation. If the counter value increases, the feature is successfully activated. ----End

6.4.6 Reconfiguration None

6.4.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 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 6-3. Table 6-3 Parameters related to 800 MHz self-interference cancellation

Issue 01 (2014-04-26)

MO

Sheet in the Summary Data File

Parameter Group

Setting Notes

CellAlgoSwitch

User-defined sheet

LocalCellIDCellAlgoSwitch

Turn off ImIcSwitch.


13



Using the CME to Perform Single Configuration On the CME, set parameters according to Table 6-3. For detailed instructions, see Using the CME to Perform Single Configuration for feature activation.

Using MML Commands Run the MOD CELLALGOSWITCH command with the ImIcSwitch check box cleared under the CellAlgoSwitch.UlSchSwitch parameter.

MML Command Examples MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=ImIcSwitch-0;

6.5 Performance Monitoring None

6.6 Parameter Optimization N/A

6.7 Troubleshooting If this feature cannot work correctly, perform the following steps for troubleshooting: Step 1 Check that the license is correct and does not exceed the validity period. Step 2 Check that the conditions for using this feature are met. For details, see When to Use 800 MHz Self-interference Cancellation. Step 3 Check that the deployment requirements are fulfilled. For details, see 6.4.1 Requirements. Step 4 Check that the feature is activated successfully. For details, see 6.4.5 Activation Observation. Step 5 If this feature still fails to work after the preceding checks, contact Huawei technical support. ----End

Issue 01 (2014-04-26)


14


7 Parameters

7

Parameters

Table 7-1 Parameter description MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

CellAlg oSwitch

UlSchS witch

MOD CELLA LGOSW ITCH

LOFD-0 01016 / TDLOF D-00101 6

VoIP Semipersisten t Scheduli ng

Meaning: Indicates the switches related to uplink (UL) scheduling in the cell. The switches are used to enable or disable specific UL scheduling functions. SpsSchSwitch: Indicates the switch used to enable or disable semi-persistent scheduling during talk spurts of VoIP services. If this switch is turned on, semipersistent scheduling is applied during talk spurts of VoIP services. If this switch is turned off, dynamic scheduling is applied during talk spurts of VoIP services. SinrAdjustSwitch: Indicates whether to adjust the measured signal to interference plus noise ratio (SINR) based on ACK/NACK in UL hybrid automatic repeat request (HARQ) processes. PreAllocationSwitch: Indicates whether to enable preallocation in the uplink. When this switch is on: (1) if SmartPreAllocationSwitch is off and a UE is in the discontinuous reception (DRX) state, preallocation is disabled for the UE in the uplink; (2) if SmartPreAllocationSwitch is off and the UE is not in the DRX state, preallocation is enabled for the UE in the uplink; (3) if SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is greater than 0, smart preallocation is enabled for the UE in the uplink; (4) if SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is 0, preallocation is disabled for the UE in the uplink. If this switch is off, preallocation is disabled for the UE in the uplink. If bearer-level preallocation or bearer-level smart preallocation is enabled for a QCI, cell-level preallocation and cell-level smart preallocation do not apply to UEs with the QCI.

LST CELLA LGOSW ITCH

LOFD-0 01048 / TDLOF D-00104 8 LOFD-0 0101502 / TDLOF D-00101 502 TDLBF D-00202 5 LBFD-0 70102 / TDLBF D-07010 2

Issue 01 (2014-04-26)

TTI Bundlin g Dynami c Scheduli ng Basic Scheduli ngTDL OFD-07 0224:Sc heduling Based on Max Bit Rate MBR>G BR Configu ration


15


MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

7 Parameters

Description

UlVmimoSwitch: Indicates the switch used to enable or disable multi-user MIMO (MU-MIMO) in the UL. If this switch is turned on, the eNodeB performs MUMIMO pairing among UEs based on related principles. UEs forming a pair transmit data using the same timefrequency resources, which improves system throughput and spectral efficiency. TtiBundlingSwitch: Indicates the switch used to enable or disable transmission time interval (TTI) bundling. If TTI bundling is enabled, more transmission opportunities are available to UEs within the delay budget for VoIP services on the Uu interface, thereby improving uplink coverage. ImIcSwitch: Indicates the switch to enable or disable the intermodulation interference (IM) cancellation for UEs. When data is transmitted in both UL and DL, two IM components are generated symmetrically beside the Direct Current (DC) subcarrier on the DL receive channel due to interference from UL radio signals. If this switch is turned on, IM component elimination is performed on UEs. If this switch is turned off, IM component elimination is not performed on UEs. This switch applies only to FDD cells working in frequency band 20. SmartPreAllocationSwitch: Indicates the switch used to enable or disable uplink smart preallocation when preallocation is enabled (by turning on PreAllocationSwitch). If both PreAllocationSwitch and SmartPreAllocationSwitch are turned on, and SmartPreAllocationDuration is set to a value greater than 0, uplink smart preallocation is enabled; otherwise, uplink smart preallocation is disabled. PuschDtxSwitch: Indicates whether the eNodeB uses the physical uplink shared channel (PUSCH) discontinuous transmission (DTX) detection result during uplink (UL) scheduling. For FDD cells, if this switch is turned on, based on the PUSCH DTX detection result, the eNodeB determines whether to perform adaptive retransmission during UL scheduling and also adjusts the control channel element (CCE) aggregation level of the physical downlink control channel (PDCCH) carrying downlink control information (DCI) format 0. This switch takes effect only on FDD cells. If an FDD cell is established on an LBBPc, this switch takes effect only when the cell uses less than four RX antennas and normal cyclic prefix (CP) in the uplink, and the SrsCfgInd parameter in the SRSCfg MO is set to BOOLEAN_TRUE. Note that the LBBPc does not support PUSCH DTX detection for Issue 01 (2014-04-26)


16


MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

7 Parameters

Description

UEs with multi-user MIMO (MU-MIMO) applied. For TDD cells, this switch takes effect only when subframe configuration 2 or 5 is adopted. If this switch is turned on, the eNodeB adjusts the aggregation level of the PDCCH based on the PUSCH DTX detection result. If a TDD cell is established on an LBBPc, PUSCH DTX detection is not supported. UlIblerAdjustSwitch: Indicates the switch used to enable or disable uplink initial block error rate (IBLER) adjustment algorithm. If this switch is turned on, IBLER convergence target is adjusted to increase the cell edge throughput. UlEnhancedFssSwitch: Indicates the switch used to enable or disable uplink load-based enhanced frequency selection. This switch applies only to FDD cells. UlIicsAlgoSwitch:Indicates the switch used to enable or disable the UL IICS algorithm. If this switch is turned on, interference can be reduced based on accurate detection of user attributes and resource scheduling coordination, thereby increasing the cell edge throughput. UlEnhancedSrSchSwitch: Indicates whether uplink re-scheduling is performed only when the On Duration timer for the DRX long cycle starts. Uplink re-scheduling is required if the number of HARQ retransmissions for a scheduling request (SR) reaches the maximum value but the scheduling still fails. If this switch is turned on, uplink re-scheduling is performed only when the On Duration timer for the DRX long cycle starts. If this switch is turned off, uplink re-scheduling is performed immediately after the number of HARQ retransmissions for SR reaches the maximum value but the scheduling still fails. It is recommended that the switch be turned on in live networks. SchedulerCtrlPowerSwitch: Indicates whether the uplink scheduler performs scheduling without considering power control restrictions. If this switch is turned on, the uplink scheduler performs scheduling without considering power control restrictions, which ensures full utilization of the transmit power for all UEs. If this switch is turned off, the uplink scheduler considers power control restrictions while performing scheduling, which prevents full utilization of the transmit power for UEs at far or medium distances from the cell center. UlMinGbrSwitch: Indicates the switch used to enable or disable uplink minimum guaranteed bit rate (GBR). If this switch is turned on, the minimum GBR of nonGBR services are ensured by increasing the scheduling Issue 01 (2014-04-26)


17


MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

7 Parameters

Description

priority of UEs whose non-GBR service rates are lower than the minimum GBR of GBR services. UlMbrCtrlSwitch: Indicates the switch used to enable or disable uplink scheduling based on the maximum bit rate (MBR) and guaranteed bit rate (GBR) on the GBR bearer. If this switch is turned on, the eNodeB performs uplink scheduling on GBR bearers based on the MBR and GBR. If this switch is turned off, the eNodeB performs uplink scheduling on GBR bearers based on the GBR only. MbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on MBR. If this switch is turned on, the eNodeB prioritizes UEs based on the MBRs during uplink scheduling. This parameter applies only to LTE TDD cells. UeAmbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If this switch is turned on, the eNodeB prioritizes UEs based on the AMBRs during uplink scheduling. This parameter applies only to LTE TDD cells. UlEnhancedDopplerSwitch: Indicates whether to enable enhanced uplink scheduling based on mobility speed. If this switch is turned on, the eNodeB determines whether a UE is a low-mobility UE based on the Doppler measurement in the physical layer, and then improves uplink frequency selective scheduling performance for low-mobility UEs. If this switch is turned off, enhanced uplink scheduling based on mobility speed is disabled. This switch takes effect only when the UlEnhancedDopplerSwitch parameter is set to CLASS_1. This switch does not take effect on cells established on an LBBPc. UlRaUserSchOptSw: Indicates whether the eNodeB raises the scheduling priority of UEs sending uplink access signaling, including MSG5 and the RRC Connection Reconfiguration Complete message. If this switch is on, the eNodeB raises the scheduling priority of UEs sending uplink access signaling. If this switch is off, the eNodeB does not raise the scheduling priority of UEs sending uplink access signaling. GUI Value Range: SpsSchSwitch(SpsSchSwitch), SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationSwitch(PreAllocationSwitch), UlVmimoSwitch (UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingSwitch), ImIcSwitch(ImIcSwitch), SmartPreAllocationSwitch(SmartPreAllocationSwitch), PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustS-

Issue 01 (2014-04-26)


18


MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

7 Parameters

Description

witch(UlIblerAdjustSwitch), UlEnhancedFssSwitch (UlEnhancedFssSwitch), UlEnhancedSrSchSwitch (UlEnhancedSrSchSwitch), SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch (UlIicsAlgoSwitch), UlMinGbrSwitch (UlMinGbrSwitch), UlMbrCtrlSwitch (UlMbrCtrlSwitch), MbrUlSchSwitch (MbrUlSchSwitch), UeAmbrUlSchSwitch (UeAmbrUlSchSwitch), UlEnhancedDopplerSwitch (UlEnhancedDopplerSwitch), UlRaUserSchOptSw (UlRaUserSchOptSw) Unit: None Actual Value Range: SpsSchSwitch, SinrAdjustSwitch, PreAllocationSwitch, UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch, SmartPreAllocationSwitch, PuschDtxSwitch, UlIblerAdjustSwitch, UlEnhancedFssSwitch, UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch, UlMinGbrSwitch, UlMbrCtrlSwitch, MbrUlSchSwitch, UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch, UlRaUserSchOptSw Default Value: SpsSchSwitch:Off, SinrAdjustSwitch:On, PreAllocationSwitch:On, UlVmimoSwitch:Off, TtiBundlingSwitch:Off, ImIcSwitch:Off, SmartPreAllocationSwitch:Off, PuschDtxSwitch:On, UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On, UlEnhancedSrSchSwitch:Off, SchedulerCtrlPowerSwitch:Off, UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off, UeAmbrUlSchSwitch:Off, UlEnhancedDopplerSwitch:Off, UlRaUserSchOptSw:Off

Issue 01 (2014-04-26)


19


8 Counters

8

Counters

There are no specific counters associated with this feature.

Issue 01 (2014-04-26)


20


9 Glossary

9

Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2014-04-26)


21


10 1.

Issue 01 (2014-04-26)

10 Reference Documents

Reference Documents

3GPP TS 36.101, "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception"


22

800 MHz Self-Interference Cancellation(ERAN7.0_01)

Recommend Documents