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

eRAN

800 MHz Self-interferenceCancellation Feature ParameterDescription

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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2014-04-26) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................11.4 Differences Between eNodeB Types..............................................................................................................................2

2 Overview.........................................................................................................................................3

3 Technical Description...................................................................................................................4

4 Related Features.............................................................................................................................6

5 Network Impact.............................................................................................................................7

6 Engineering Guidelines...............................................................................................................86.1 When to Use 800 MHz Self-interference Cancellation..................................................................................................86.2 Required Information.....................................................................................................................................................86.3 Planning..........................................................................................................................................................................86.4 Deployment....................................................................................................................................................................96.4.1 Requirements...............................................................................................................................................................96.4.2 Data Preparation..........................................................................................................................................................96.4.3 Precautions.................................................................................................................................................................106.4.4 Activation..................................................................................................................................................................106.4.5 Activation Observation..............................................................................................................................................126.4.6 Reconfiguration.........................................................................................................................................................136.4.7 Deactivation...............................................................................................................................................................136.5 Performance Monitoring...............................................................................................................................................146.6 Parameter Optimization................................................................................................................................................146.7 Troubleshooting............................................................................................................................................................14

7 Parameters.....................................................................................................................................15

8 Counters........................................................................................................................................20

9 Glossary.........................................................................................................................................21

10 Reference Documents...............................................................................................................22

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription Contents


ii

1 About This Document

1.1 ScopeThis document describes LOFD-001067 800M Self-interference Cancellation, including itstechnical 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 tothe software release delivered with this document. Any future updates will be described in theproduct 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 AudienceThis document is intended for personnel who:

l Need to understand the features described herein

l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:

l Feature change

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 1 About This Document


1

Changes in features and parameters of a specified version as well as the affected entitiesl Editorial change

Changes in wording or addition of information and any related parameters affected byeditorial 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 ParameterChange

AffectedEntity

Feature change None None N/A

Editorial change Added 1.4 DifferencesBetween eNodeB Types,which describes differences infeature support betweeneNodeB 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 includesthe following changes.

Change Type Change Description Parameter Change

Feature change None None

Changed the name of Huaweimobile element managementsystem from M2000 toU2000.

None

Editorial change Revised EngineeringGuidelines.

None

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

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 1 About This Document


2

2 Overview

This document describes the optional feature LOFD-001067 800M Self-interferenceCancellation, 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 frequencyseparation, as shown in Figure 2-1. Therefore, when a UE simultaneously transmits and receivesdata, the uplink causes interference to the downlink and the interference leads to deteriorationin the downlink receiver sensitivity. The degrees of interference and deterioration depend on theUE's duplex frequency separation, transmit power, and positions of uplink and downlinkphysical resource blocks (PRBs). The degrees also depend on the UE's transmit power and radiofrequency (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.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 2 Overview


3

3 Technical Description

800 MHz self-interference is the interference that a UE's signal transmission induces on the UE'ssignal reception (that is, uplink-to-downlink interference) in a cell that operates in the 800 MHzfrequency band. Self-interference is restricted by the RF component specifications of the UEand the narrow duplex frequency separation of the 800 MHz frequency band. Self-interferencemainly consists of intermodulation (IM) interference, including IM2, IM3, IM5, and IM7, whichcorrespond to IM orders. The strength of self-interference is determined by the UE's transmitpower and intermediate frequency (IF) performance, mainly referring to the duplex frequencyseparation 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 awanted signal because the power amplifier of the UE is non-linear. As a result, the UE cannot filterout these interfering signals, and these signals interfere with wanted signals. Different frequencycombinations cause different IM interference.

l Downlink-to-uplink interference is due to the eNodeB and can be mitigated by selecting RF componentswith good performance, which is usually done before network construction. By contrast, uplink-to-downlink interference is due to UEs, but the UEs' types, models, and RF component specifications areuncontrollable. Therefore, the eNodeB needs to use some algorithms to reduce uplink-to-downlinkinterference.

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 impactof self-interference caused by a narrow duplex frequency separation is small enough toignore.

l A cell with a 10 MHz, 15 MHz, or 20 MHz bandwidth has a narrow frequency separationand therefore self-interference exists. Downlink PRBs at any positions in the spectrum mayexperience 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 uplinktransmission. In this case, the start position of uplink PRBs is at 836.5 MHz (831 MHz + 25 x180 kHz = 836.5 MHz). Then, the red curve in Figure 3-1 represents self-interference.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 3 Technical Description


4

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) underCellAlgoSwitch.UlSchSwitch. If ImIcSwitch(ImIcSwitch) is selected, the eNodeB mitigatesself-interference and increases downlink capacity by limiting the number of allocated uplinkPRBs. For details, see Engineering Guidelines.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 3 Technical Description


5

4 Related Features

Prerequisite FeaturesThe 800 MHz self-interference cancellation feature depends on LBFD-002025 BasicScheduling.

Mutually Exclusive FeaturesNone

Impacted FeaturesThe 800 MHz self-interference cancellation feature has impacts on LBFD-002025 BasicScheduling.

With the 800 MHz self-interference cancellation feature, the eNodeB limits the number ofallocated 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 degreeof uplink PRBs.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 4 Related Features


6

5 Network Impact

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

Network PerformanceWhen the conditions for deploying the 800 MHz self-interference cancellation feature arefulfilled, this feature prevents a decrease in downlink throughput caused by self-interference butleads to a reduction in uplink throughput. The reduction degree of uplink throughput has apositive correlation with the reduction degree of uplink PRBs.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 5 Network Impact


7

6 Engineering Guidelines

6.1 When to Use 800 MHz Self-interference CancellationOperators can use the 800 MHz self-interference cancellation feature to increase downlinkthroughput 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, 15MHz, or 20 MHz, respectively.

l UEs perform uplink and downlink services at the same time, and the uplink causesinterference to the downlink.

l A decrease in uplink throughput is acceptable.

6.2 Required InformationBefore deploying the 800 MHz self-interference cancellation feature, collect the followinginformation:

l UE transmit power

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

l UE performance, including the duplex frequency separation, modulator performance, andnon-linear power amplifier performance

The performance of UEs can be obtained by analyzing and taking statistics on theperformance indicators and specifications of the RF components that cause self-interference.

6.3 PlanningThis feature does not require special network planning. Perform network planning for cellsoperating in the 800 MHz frequency band in the same way as you do for other cells. That is,

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 6 Engineering Guidelines


8

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

6.4 Deployment

6.4.1 RequirementsThe 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 LicenseControl Item

NE Sales Unit

LOFD-001067 800M Self-interferenceCancellation

800M Self-interferenceCancellation(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 PreparationThis section describes the data that you need to collect for setting parameters. Required data isdata that you must collect for all scenarios. Collect scenario-specific data when necessary for aspecific feature deployment scenario.

There are three types of data sources:

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

l Network plan (negotiation not required): parameter values planned and set by the operatorl User-defined: parameter values set by users.

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



9

Parameter Name Parameter ID Data Source Setting Notes

Uplink scheduleswitch

CellAlgoSwitch.UlSchSwitch

Network plan(negotiation notrequired)

This parameterspecifies the switchImIcSwitch for the800 MHz self-interferencecancellation feature.If ImIcSwitch isturned on, the featureis enabled. IfImIcSwitch isturned off, the featureis disabled.

Scenario-specific Data

None

6.4.3 PrecautionsWhen 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 containsother data for the new eNodeBs to be deployed. Then, import the summary data file into theConfiguration 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 customizedfile, depending on the following conditions:

l The managed objects (MOs) in Table 6-2 are contained in a scenario-specific summarydata 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 thissituation, customize a summary data file to include the MOs before you can set theparameters.

Table 6-2 Parameters related to 800 MHz self-interference cancellation

MO Sheet in theSummary DataFile

Parameter Group Remarks

CellAlgoSwitch User-defined sheet LocalCellID,CellAlgoSwitch

None



10

Using the CME to Perform Batch Configuration for Existing eNodeBsBatch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure is as follows:

Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or chooseAdvanced > Customize Summary Data File (CME client mode), to customize a summary datafile 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 ConfigurationData (U2000 client mode), or choose LTE Application > Export Data > Export Base StationBulk Configuration Data (CME client mode), to export the eNodeB data stored on the CMEinto 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 ConfigurationData (U2000 client mode), or choose LTE Application > Import Data > Import Base StationBulk 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 chooseArea Management > Planned Area > Export Incremental Scripts (CME client mode), toexport and activate the incremental scripts.

----End

Using the CME to Perform Single ConfigurationOn 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.



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 aredisplayed 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 chooseArea Management > Planned Area > Export Incremental Scripts (CME client mode), toexport and activate the incremental scripts.

----End

Using MML Commands

Run the MOD CELLALGOSWITCH command with the ImIcSwitch check box selectedunder the CellAlgoSwitch.UlSchSwitch parameter.

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

6.4.5 Activation ObservationThis section describes how to verify the activation when the UEs in the cell center or on the celledge are experiencing high traffic in both the uplink and downlink.

The observation procedure is as follows:

l Starting cell performance monitoring on the U2000 client



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 CellPerformance Monitoring > General Throughput Monitoring and click New.

This task measures the downlink data throughput at the RLC layer, which is indicated by CellDownlink RLC Throughput(bps).

Step 3 Compare the measurement results before and after deploying 800 MHz self-interferencecancellation.

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 UserPerformance Monitoring > Throughput Monitoring and click New.

This task measures the downlink data throughput at the RLC layer, which is indicated byDownlink RLC Throughput(bps).

Step 3 Compare the measurement results before and after deploying 800 MHz self-interferencecancellation.

If the counter value increases, the feature is successfully activated.

----End

6.4.6 ReconfigurationNone

6.4.7 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature oneNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure for feature deactivation is similar to that forfeature activation described in Using the CME to Perform Batch Configuration for ExistingeNodeBs. In the procedure, modify parameters according to Table 6-3.

Table 6-3 Parameters related to 800 MHz self-interference cancellation

MO Sheet in theSummary DataFile

Parameter Group Setting Notes

CellAlgoSwitch User-defined sheet LocalCellIDCellAl-goSwitch

Turn offImIcSwitch.



13

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

Using MML CommandsRun the MOD CELLALGOSWITCH command with the ImIcSwitch check box cleared underthe CellAlgoSwitch.UlSchSwitch parameter.

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

6.5 Performance MonitoringNone

6.6 Parameter OptimizationN/A

6.7 TroubleshootingIf 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 MHzSelf-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 ActivationObservation.

Step 5 If this feature still fails to work after the preceding checks, contact Huawei technical support.

----End



14

7 Parameters

Table 7-1 Parameter description

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellAlgoSwitch

UlSchSwitch

MODCELLALGOSWITCHLSTCELLALGOSWITCH

LOFD-001016 /TDLOFD-001016LOFD-001048 /TDLOFD-001048LOFD-00101502/TDLOFD-00101502TDLBFD-002025LBFD-070102 /TDLBFD-070102

VoIPSemi-persistentSchedulingTTIBundlingDynamicSchedulingBasicSchedulingTDLOFD-070224:SchedulingBasedon MaxBit RateMBR>GBRConfiguration

Meaning: Indicates the switches related to uplink (UL)scheduling in the cell. The switches are used to enableor disable specific UL scheduling functions.SpsSchSwitch: Indicates the switch used to enable ordisable semi-persistent scheduling during talk spurts ofVoIP services. If this switch is turned on, semi-persistent scheduling is applied during talk spurts ofVoIP services. If this switch is turned off, dynamicscheduling is applied during talk spurts of VoIPservices. SinrAdjustSwitch: Indicates whether to adjustthe measured signal to interference plus noise ratio(SINR) based on ACK/NACK in UL hybrid automaticrepeat request (HARQ) processes. PreAllocationS-witch: Indicates whether to enable preallocation in theuplink. When this switch is on: (1) if SmartPreAlloca-tionSwitch is off and a UE is in the discontinuousreception (DRX) state, preallocation is disabled for theUE in the uplink; (2) if SmartPreAllocationSwitch is offand the UE is not in the DRX state, preallocation isenabled for the UE in the uplink; (3) if SmartPreAlloca-tionSwitch is on and the SmartPreAllocationDurationparameter value is greater than 0, smart preallocation isenabled for the UE in the uplink; (4) if SmartPreAlloca-tionSwitch is on and the SmartPreAllocationDurationparameter value is 0, preallocation is disabled for theUE in the uplink. If this switch is off, preallocation isdisabled for the UE in the uplink. If bearer-levelpreallocation or bearer-level smart preallocation isenabled for a QCI, cell-level preallocation and cell-levelsmart preallocation do not apply to UEs with the QCI.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 7 Parameters


15

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

UlVmimoSwitch: Indicates the switch used to enable ordisable multi-user MIMO (MU-MIMO) in the UL. Ifthis switch is turned on, the eNodeB performs MU-MIMO pairing among UEs based on related principles.UEs forming a pair transmit data using the same time-frequency resources, which improves systemthroughput and spectral efficiency. TtiBundlingSwitch:Indicates the switch used to enable or disabletransmission time interval (TTI) bundling. If TTIbundling is enabled, more transmission opportunitiesare available to UEs within the delay budget for VoIPservices on the Uu interface, thereby improving uplinkcoverage. ImIcSwitch: Indicates the switch to enable ordisable the intermodulation interference (IM)cancellation for UEs. When data is transmitted in bothUL and DL, two IM components are generatedsymmetrically beside the Direct Current (DC)subcarrier on the DL receive channel due to interferencefrom UL radio signals. If this switch is turned on, IMcomponent elimination is performed on UEs. If thisswitch is turned off, IM component elimination is notperformed on UEs. This switch applies only to FDDcells working in frequency band 20. SmartPreAlloca-tionSwitch: Indicates the switch used to enable ordisable uplink smart preallocation when preallocationis enabled (by turning on PreAllocationSwitch). If bothPreAllocationSwitch and SmartPreAllocationSwitchare turned on, and SmartPreAllocationDuration is set toa value greater than 0, uplink smart preallocation isenabled; otherwise, uplink smart preallocation isdisabled. PuschDtxSwitch: Indicates whether theeNodeB uses the physical uplink shared channel(PUSCH) discontinuous transmission (DTX) detectionresult during uplink (UL) scheduling. For FDD cells, ifthis switch is turned on, based on the PUSCH DTXdetection result, the eNodeB determines whether toperform adaptive retransmission during UL schedulingand also adjusts the control channel element (CCE)aggregation level of the physical downlink controlchannel (PDCCH) carrying downlink controlinformation (DCI) format 0. This switch takes effectonly on FDD cells. If an FDD cell is established on anLBBPc, this switch takes effect only when the cell usesless than four RX antennas and normal cyclic prefix(CP) in the uplink, and the SrsCfgInd parameter in theSRSCfg MO is set to BOOLEAN_TRUE. Note that theLBBPc does not support PUSCH DTX detection for



16

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

UEs with multi-user MIMO (MU-MIMO) applied. ForTDD cells, this switch takes effect only when subframeconfiguration 2 or 5 is adopted. If this switch is turnedon, the eNodeB adjusts the aggregation level of thePDCCH based on the PUSCH DTX detection result. Ifa TDD cell is established on an LBBPc, PUSCH DTXdetection is not supported. UlIblerAdjustSwitch:Indicates the switch used to enable or disable uplinkinitial block error rate (IBLER) adjustment algorithm.If this switch is turned on, IBLER convergence target isadjusted to increase the cell edge throughput.UlEnhancedFssSwitch: Indicates the switch used toenable or disable uplink load-based enhanced frequencyselection. This switch applies only to FDD cells.UlIicsAlgoSwitch:Indicates the switch used to enableor disable the UL IICS algorithm. If this switch is turnedon, interference can be reduced based on accuratedetection of user attributes and resource schedulingcoordination, thereby increasing the cell edgethroughput. UlEnhancedSrSchSwitch: Indicateswhether uplink re-scheduling is performed only whenthe On Duration timer for the DRX long cycle starts.Uplink re-scheduling is required if the number ofHARQ retransmissions for a scheduling request (SR)reaches the maximum value but the scheduling stillfails. If this switch is turned on, uplink re-scheduling isperformed only when the On Duration timer for theDRX long cycle starts. If this switch is turned off, uplinkre-scheduling is performed immediately after thenumber of HARQ retransmissions for SR reaches themaximum value but the scheduling still fails. It isrecommended that the switch be turned on in livenetworks. SchedulerCtrlPowerSwitch: Indicateswhether the uplink scheduler performs schedulingwithout considering power control restrictions. If thisswitch is turned on, the uplink scheduler performsscheduling without considering power controlrestrictions, which ensures full utilization of thetransmit power for all UEs. If this switch is turned off,the uplink scheduler considers power controlrestrictions while performing scheduling, whichprevents full utilization of the transmit power for UEsat far or medium distances from the cell center.UlMinGbrSwitch: Indicates the switch used to enableor disable uplink minimum guaranteed bit rate (GBR).If this switch is turned on, the minimum GBR of non-GBR services are ensured by increasing the scheduling



17

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

priority of UEs whose non-GBR service rates are lowerthan the minimum GBR of GBR services.UlMbrCtrlSwitch: Indicates the switch used to enableor disable uplink scheduling based on the maximum bitrate (MBR) and guaranteed bit rate (GBR) on the GBRbearer. If this switch is turned on, the eNodeB performsuplink scheduling on GBR bearers based on the MBRand GBR. If this switch is turned off, the eNodeBperforms uplink scheduling on GBR bearers based onthe GBR only. MbrUlSchSwitch: Indicates whether theeNodeB performs uplink scheduling based on MBR. Ifthis switch is turned on, the eNodeB prioritizes UEsbased on the MBRs during uplink scheduling. Thisparameter applies only to LTE TDD cells.UeAmbrUlSchSwitch: Indicates whether the eNodeBperforms uplink scheduling based on the aggregatemaximum bit rate (AMBR) of UEs. If this switch isturned on, the eNodeB prioritizes UEs based on theAMBRs during uplink scheduling. This parameterapplies only to LTE TDD cells. UlEnhancedDopplerS-witch: Indicates whether to enable enhanced uplinkscheduling based on mobility speed. If this switch isturned on, the eNodeB determines whether a UE is alow-mobility UE based on the Doppler measurement inthe physical layer, and then improves uplink frequencyselective scheduling performance for low-mobilityUEs. If this switch is turned off, enhanced uplinkscheduling based on mobility speed is disabled. Thisswitch takes effect only when the UlEnhancedDop-plerSwitch parameter is set to CLASS_1. This switchdoes not take effect on cells established on an LBBPc.UlRaUserSchOptSw: Indicates whether the eNodeBraises the scheduling priority of UEs sending uplinkaccess signaling, including MSG5 and the RRCConnection Reconfiguration Complete message. If thisswitch is on, the eNodeB raises the scheduling priorityof UEs sending uplink access signaling. If this switch isoff, the eNodeB does not raise the scheduling priorityof UEs sending uplink access signaling.GUI Value Range: SpsSchSwitch(SpsSchSwitch),SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationS-witch(PreAllocationSwitch), UlVmimoSwitch(UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingS-witch), ImIcSwitch(ImIcSwitch), SmartPreAlloca-tionSwitch(SmartPreAllocationSwitch),PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustS-



18

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

witch(UlIblerAdjustSwitch), UlEnhancedFssSwitch(UlEnhancedFssSwitch), UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch), SchedulerCtrlPowerS-witch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch(UlIicsAlgoSwitch), UlMinGbrSwitch(UlMinGbrSwitch), UlMbrCtrlSwitch(UlMbrCtrlSwitch), MbrUlSchSwitch(MbrUlSchSwitch), UeAmbrUlSchSwitch(UeAmbrUlSchSwitch), UlEnhancedDopplerSwitch(UlEnhancedDopplerSwitch), UlRaUserSchOptSw(UlRaUserSchOptSw)Unit: NoneActual Value Range: SpsSchSwitch, SinrAdjustSwitch,PreAllocationSwitch, UlVmimoSwitch, TtiBundlingS-witch, ImIcSwitch, SmartPreAllocationSwitch,PuschDtxSwitch, UlIblerAdjustSwitch,UlEnhancedFssSwitch, UlEnhancedSrSchSwitch,SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch,UlMinGbrSwitch, UlMbrCtrlSwitch,MbrUlSchSwitch, UeAmbrUlSchSwitch,UlEnhancedDopplerSwitch, UlRaUserSchOptSwDefault 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



19

8 Counters

There are no specific counters associated with this feature.

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 8 Counters


20

9 Glossary

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

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 9 Glossary


21

10 Reference Documents

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

eRAN800 MHz Self-interference Cancellation Feature ParameterDescription 10 Reference Documents


22