Uplink Timing Control (ERAN12.1 - 04)

eRAN
Uplink Timing Control Feature

Parameter Description
Issue 04
Date 2018-08-07
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. 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: support@huawei.com
Issue 04 (2018-08-07) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Uplink Timing Control Feature Parameter Description Contents
Contents
1 About The Document................................................................................................................... 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between eNodeB Types.............................................................................................................................. 3
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
3 Technical Description...................................................................................................................5
3.1 Uplink Timing Control During RA................................................................................................................................ 6
3.2 Uplink Timing Control After a Successful RA.............................................................................................................. 7
3.3 Timers........................................................................................................................................................................... 10
3.3.1 Uplink Time Alignment Timer.................................................................................................................................. 10
3.3.2 Uplink Synchronization Timer.................................................................................................................................. 13
3.3.3 UE Inactivity Timer................................................................................................................................................... 14
4 Related Features...........................................................................................................................16
5 Network Impact........................................................................................................................... 19
6 Engineering Guidelines............................................................................................................. 20
6.1 When to Use................................................................................................................................................................. 20
6.2 Required Information................................................................................................................................................... 20
6.3 Planning........................................................................................................................................................................ 21
6.4 Deployment.................................................................................................................................................................. 21
6.4.1 Requirements............................................................................................................................................................. 21
6.4.2 Data Preparation........................................................................................................................................................ 21
6.4.3 Initial Configuration.................................................................................................................................................. 23
6.4.4 Activation Observation..............................................................................................................................................24
6.4.5 Deactivation...............................................................................................................................................................25
6.4.6 Reconfiguration......................................................................................................................................................... 25
6.5 Performance Monitoring...............................................................................................................................................26
6.6 Parameter Optimization................................................................................................................................................ 27
6.7 Possible Issues.............................................................................................................................................................. 27
Issue 04 (2018-08-07) Huawei Proprietary and Confidential ii

eRAN
Uplink Timing Control Feature Parameter Description Contents
7 Parameters..................................................................................................................................... 28
8 Counters........................................................................................................................................ 39
9 Glossary......................................................................................................................................... 42
10 Reference Documents............................................................................................................... 43
Issue 04 (2018-08-07) Huawei Proprietary and Confidential iii

eRAN
Uplink Timing Control Feature Parameter Description 1 About The Document
1 About The Document
1.1 Scope
This document describes LBFD-070101 Uplink Timing Based on PUCCH and uplink timing
control, including their technical principles, related features, network impact, and engineering
guidelines.
Feature compatibility with specific terminal models is not presented in this document. For
compatibility information, contact Huawei engineers.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
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:
l Feature change
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.
Issue 04 (2018-08-07) Huawei Proprietary and Confidential 1

eRAN
eRAN12.1 04 (2018-08-07)
This issue includes the following changes.
Change Change Description Parameter Affected

Type Change Entity
Feature None None N/A

change
Editorial Revised descriptions in 3.2 Uplink None N/A

change Timing Control After a Successful
RA.
eRAN12.1 03 (2018-04-02)

Type Change Entity

change
Editorial Revised descriptions in 3.2 Uplink None N/A

change Timing Control After a Successful
RA.
eRAN12.1 02 (2017-10-23)

Type Change Entity

change
Editorial Modified the following sections: Added the N/A

change l Timer Settings in 3.3.2 Uplink following
Synchronization Timer parameters:
l Timer Settings in 3.3.3 UE l QCIPARA.UlSy
Inactivity Timer nTimerForQci
l QCIPARA.UeI
nactiveTimerFo
rQci

eRAN
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
eRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of eRAN12.1 introduces the following changes to Issue 02
(2016-04-20) of eRAN11.1.

Type Change Entity

change
Editorial l Revised descriptions in this None N/A

change document.
l Revised 6.4.3 Initial
Configuration.
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, LampSite, and Pico eNodeBs
Feature ID Description Supported by Supported by Supported by
Macro Micro LampSite
eNodeBs eNodeBs eNodeBs
LBFD-070101 Uplink Timing Yes Yes (supported Yes

Based on only by
PUCCH BTS3203E,
BTS3911E,
and
BTS3912E)
Function Implementation in Macro, Micro, LampSite, and Pico eNodeBs

The functions described in this document are implemented in the same way on macro, micro,
and LampSite eNodeBs.

eRAN
Uplink Timing Control Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
During uplink timing control, the eNodeB calculates the timing offset after measuring uplink
signals received from a UE. The eNodeB then converts the timing offset into a Timing
Advance Command and issues the command to the UE. After receiving the command, the UE
adjusts the time to transmit uplink signals. The entire process shown in Figure 2-1 ensures
time synchronization between the UE and the eNodeB.
Figure 2-1 Uplink timing control
2.2 Benefits
With uplink timing control enabled, the eNodeB adjusts the time to transmit uplink signals
from each UE so that the time for uplink signals from different UEs to reach the eNodeB is
aligned. This ensures orthogonality of uplink signals transmitted by different UEs, mitigates
intra-cell interference, and maintains the demodulation performance of the eNodeB.

eRAN
Uplink Timing Control Feature Parameter Description 3 Technical Description
3 Technical Description
Uplink timing control can be performed during or after random access (RA), as shown in
Figure 3-1.
l Uplink timing control during RA
Non-synchronized UEs (including UEs that are newly powered on or handed over to the
cell, UEs in RRC_IDLE mode, and out-of-synchronization UEs) establish or restore
uplink synchronization based on RA. For details, see 3.1 Uplink Timing Control
During RA.
l Uplink timing control after RA
A synchronized UE maintains the synchronization state based on periodic uplink timing
adjustment. For details, see 3.2 Uplink Timing Control After a Successful RA.
When a UE is in the synchronization state, the uplink time alignment timer, uplink
synchronization timer, and UE inactivity timer maintain and manage the UE states. For
details about working principles and settings of these timers, see 3.3.1 Uplink Time
Alignment Timer, 3.3.2 Uplink Synchronization Timer, and 3.3.3 UE Inactivity
Timer.
– If the uplink time alignment timer expires, an uplink-synchronized UE enters the
out-of-synchronization state.
– If the uplink synchronization timer expires, this causes the uplink time alignment
timer to expire, which further makes an uplink-synchronized UE enter the out-of-
synchronization state.
– If the UE inactivity timer expires, an uplink-synchronized UE enters the
RRC_IDLE mode.
Non-synchronized UEs will enter the synchronization state by initiating the RA
procedure again.

eRAN
Figure 3-1 Timers maintaining UE states
3.1 Uplink Timing Control During RA

A UE achieves uplink synchronization with the eNodeB based on uplink timing control
during RA. Figure 3-2 shows the procedure for uplink timing control during RA.

eRAN
Figure 3-2 Uplink timing control during RA
NOTE
After receiving the Timing Advance Command, the UE adjusts the time to transmit uplink signals. For
details about timing adjustment, see section 4.2.3 "Transmission timing adjustments" in 3GPP TS
36.213 V10.10.0.
3.2 Uplink Timing Control After a Successful RA

After a successful RA, an uplink-synchronized UE maintains the synchronization state based
on periodic uplink timing adjustment. Figure 3-3 shows the procedure for periodic uplink
timing adjustment.

eRAN
Figure 3-3 Periodic uplink timing adjustment
1. The eNodeB allocates uplink resources to a UE. Resources allocated to the UE can be
used for reporting sounding reference signals (SRSs), physical uplink shared channel
demodulation reference signals (PUSCH DMRSs), or channel quality indicators (CQIs)
on PUCCH.
2. The UE transmits uplink signals.
3. The eNodeB measures the timing offset of the UE based on the uplink signals received
from the UE.
The timing offset can be measured based on the SRSs, PUSCH DMRSs, or CQIs on
PUCCH. The method for measuring uplink timing offsets can be specified by the
TimeAlignmentTimer.TimingMeasMode parameter.
– If this parameter is set to INVALID, then:
n If the eNodeB has allocated SRS resources to the UE, the eNodeB measures
the timing offset of the UE based on SRSs.
n If the eNodeB has not allocated SRS resources to the UE, the eNodeB
measures the timing offset of the UE based on PUSCH DMRSs. If the UE

eRAN
does not have any PUSCH resources, the eNodeB allocates PUSCH resources
to the UE and then measures the timing offset based on PUSCH DMRSs.
– If this parameter is set to ALLMEASMODE, then:
n If the eNodeB has allocated SRS resources to the UE, the eNodeB measures
the timing offset of the UE based on SRSs. If the UE has PUSCH resources,
the eNodeB measures the timing offset of the UE based on both SRSs and
PUSCH DMRSs, but the timing offset measured based on PUSCH DMRSs is
preferentially used.
n If the eNodeB has not allocated SRS resources to the UE, the eNodeB
measures the timing offset of the UE based on CQIs on PUCCH. If the UE has
PUSCH resources, the eNodeB measures the timing offset of the UE based on
both CQIs on PUCCH and PUSCH DMRSs, but the timing offset measured
based on PUSCH DMRSs is preferentially used.
NOTE
The eNodeB measures the timing offset of the UE based on CQIs on PUCCH only
after the eNodeB allocates resources for periodic CQI reporting. For UEs that are
newly powered on, UEs that are handed over to the cell, and UEs in RRC_IDLE mode,
the eNodeB performs periodic CQI resource allocation. For out-of-synchronization
UEs, the eNodeB reconfigures periodic CQI resources during resynchronization.
It is recommended that the TimeAlignmentTimer.TimingResOptSwitch parameter be
set to ON to reduce the resources allocated by the eNodeB for timing offset
measurements based on PUSCH DMRSs in heavy traffic scenarios. This will decrease
the UE moving speed supported by the uplink timing control based on PUSCH DMRSs.
If the TimeAlignmentTimer.TimingResOptSwitch parameter is set to ON, selecting the
TaEnhancePuschDmrs option of the TimeAlignmentTimer.TaEnhance parameter
reduces PUSCH DMRS resources allocated by the eNodeB to UEs to a larger extent.
4. The eNodeB converts the measured timing offset into a Timing Advance Command.
5. The eNodeB delivers the Timing Advance Command to the UE.
The TimeAlignmentTimer.TimingAdvCmdOptSwitch parameter specifies the policy of
sending the Timing Advance Command to UEs.
– If this parameter is set to OFF, then:
The eNodeB periodically sends the Timing Advance Command. The length of the
Timing Advance Command sending period is calculated by the formula
"floor(Length of the uplink time alignment timer/2 – 32 ms)" and cannot be
manually set.
When the TimeAlignmentTimer.TimeAlignmentTimer is set to INFINITY, the
length of the Timing Advance Command sending period is 32735 ms, which is
calculated by the formula "floor(65535 ms/2 – 32 ms)".
– If this parameter is set to ON, then:
The eNodeB sends the Timing Advance Command based on the periodic
determination and event triggering policy. It periodically checks whether a timing
offset occurs on the UE. The eNodeB sends a Timing Advance Command to the UE
only when a timing offset occurs on the UE.
The period is specified by the TimeAlignmentTimer.TACmdSendPeriod
parameter.
n A smaller value of this parameter indicates that the eNodeB sends the Timing
Advance Commands to UEs more frequently. As a result, more air interface
resources are consumed and a higher moving speed can be supported.

eRAN
n If this parameter is set to INVALID, the period that the eNodeB adopts to send
Timing Advance Commands is min(928 ms,
TimeAlignmentTimer.TimeAlignmentTimer/2 – 32 ms).
The TimeAlignmentTimer.TACmdSendPeriod parameter value may impact the
L.ChMeas.PUSCH.DmrsTaSch counter value.
n If TimeAlignmentTimer.TACmdSendPeriod is set to a value equal to the
value of TimeAlignmentTimer.TimeAlignmentTimer, then:
○ When the number of UEs in the cell is not greater than 150
The value of L.ChMeas.PUSCH.DmrsTaSch remains unchanged.
○ When the number of UEs in the cell is greater than 150
The value of L.ChMeas.PUSCH.DmrsTaSch decreases.
n If TimeAlignmentTimer.TACmdSendPeriod is set to a value smaller than the
value of TimeAlignmentTimer.TimeAlignmentTimer, then:
The value of L.ChMeas.PUSCH.DmrsTaSch may increase.
NOTE
If no timing offset occurs on a UE before the uplink time alignment timer expires, the UE
will not receive the Timing Advance Command for a long time. In this case, the eNodeB will
send the Timing Advance Command to the UE before this timer expires.
If the TimeAlignmentTimer.TimingMeasMode parameter is set to ALLMEASMODE
or the TimeAlignmentTimer.TimingResOptSwitch parameter is set to ON, the eNodeB
sends the Timing Advance Command based on the periodic determination and event
triggering policy regardless of the TimeAlignmentTimer.TimingAdvCmdOptSwitch
parameter setting.
6. After receiving the Timing Advance Command, the UE adjusts the time to transmit
uplink signals.
For details about timing adjustment, see section 4.2.3 "Transmission timing adjustments"
in 3GPP TS 36.213 V10.10.0.
7. Uplink timing offset measurements and uplink timing adjustments are performed
periodically by following steps 1 to 6.
3.3 Timers
3.3.1 Uplink Time Alignment Timer

Working Principles
Uplink synchronization between a UE and the eNodeB is performed using their respective
time alignment timers.
l The UE uses its uplink time alignment timer to determine whether it is in the
synchronization state. Before the timer expires, the UE considers itself to be in the
synchronization state. After the timer expires, the UE considers itself to be in the out-of-
synchronization state.
l The eNodeB uses its uplink time alignment timer to determine whether the UE is in the
uplink synchronization state. Before the timer expires, the eNodeB determines that the
UE is in the synchronization state. After the timer expires, the eNodeB determines that
the UE is in the out-of-synchronization state and stops sending the Timing Advance

eRAN
Command to the UE, excluding the Timing Advance Command included in the Random
Access Response during RA.
Table 3-1 describes the working principles of the uplink time alignment timers on the UE side
and the eNodeB side.
Table 3-1 Working principles of uplink time alignment timers

Timer Action Description
Uplink time Start l When the UE receives the Timing Advance

alignment Command included in the Random Access
timer on the Response during RA:
UE side – For a non-contention-based RA, the UE starts
or restarts the timer.
– For a contention-based RA, if the timer has not
started, the UE starts the timer. If the timer has
started, the UE does not need to restart the
timer. The timer stops if the contention-based
RA fails.
NOTE
For definitions about the non-contention-based RA and
contention-based RA, see Random Access Control and
RACH Optimization.
l Upon receiving the Timing Advance Command
after experiencing a successful RA, the UE starts
or restarts the timer.
Expired l If the UE does not receive the Timing Advance

Command from the eNodeB, the UE does not
restart the timer. As a result, the timer will expire.
l After the uplink synchronization timer expires, the
eNodeB no longer sends the Timing Advance
Command to the UE, and therefore the UE does
not restart the timer. As a result, the timer will
expire. For details about the uplink
synchronization timer, see 3.3.2 Uplink
Synchronization Timer.
Uplink time Start l During RA:

alignment – For a non-contention-based RA, the eNodeB
timer on the starts or restarts the timer after receiving an
eNodeB side ACK from the UE that replies to the delivered
Random Access Response.
– For a contention-based RA, the eNodeB starts
or restarts the timer for the UE that has
successfully accessed the network.
l After the UE experiences a successful RA, the
eNodeB starts or restarts the timer after receiving
the ACK from the UE that replies to the delivered
Timing Advance Command.

eRAN
Timer Action Description
Expired l If the eNodeB does not receive an ACK from the

UE after delivering the Timing Advance
Command, the eNodeB does not restart the timer.
As a result, the timer will expire.
l After the uplink synchronization timer expires, the
eNodeB no longer sends the Timing Advance
Command to the UE, and therefore the eNodeB
does not restart the timer. As a result, the timer
will expire. For details about the uplink
synchronization timer, see 3.3.2 Uplink
Synchronization Timer.
Both the uplink time alignment timer on the UE side and that on the eNodeB side can be
restarted before expiration to prolong the duration of uplink synchronization. As shown in
Figure 3-4, the eNodeB restarts its uplink time alignment timer upon receiving the ACK
responding to the delivered Timing Advance Command. The UE restarts its uplink time
alignment timer after receiving the Timing Advance Command for the eNodeB.
Figure 3-4 Time to restart the uplink time alignment timers
Timer Settings
The uplink time alignment timers on the UE and eNodeB sides are controlled independently.
The TimeAlignmentTimer.TimeAlignmentTimer parameter specifies the uplink time
alignment timer length on the eNodeB side. After being set, the timer length is sent to the UE
through air interface signaling.
l If the eNodeB adopts the periodic policy:

– It is recommended that the TimeAlignmentTimer.TimeAlignmentTimer parameter
be set to SF1920(1920 subframes).
– A smaller value of the TimeAlignmentTimer.TimeAlignmentTimer parameter
indicates that the eNodeB sends the Timing Advance Command to the UE more
frequently, more radio resources are consumed, and a higher mobility speed of the
UE is supported.
– A larger value of this parameter results in the opposite effects.
l If the eNodeB adopts the "periodic evaluation and event-triggering" policy:

eRAN
– It is recommended that the TimeAlignmentTimer.TimeAlignmentTimer parameter

be set to SF10240(10240 subframes).
– In heavy traffic scenarios where the TimeAlignmentTimer.TimingResOptSwitch
parameter is set to ON(On), it is recommended that the
TimeAlignmentTimer.TimeAlignmentTimer parameter be set to
INFINITY(Infinity).
– A smaller value of the TimeAlignmentTimer.TimeAlignmentTimer parameter (for
example, smaller than SF5120(5120 subframes)) leads to a higher probability of
UEs in the discontinuous reception (DRX) state entering the out-of-synchronization
state.
NOTE
For details about the relationship between the TimeAlignmentTimer.TimeAlignmentTimer

parameter value and the DRX state, see DRX and Signaling Control.
3.3.2 Uplink Synchronization Timer
Working Principles
The uplink synchronization timer controls whether the eNodeB continues to maintain uplink
synchronization between a UE and the eNodeB. The eNodeB maintains an uplink
synchronization timer for each UE. Table 3-2 describes the working principles of this timer.
Table 3-2 Working principles of the uplink synchronization timer
Action Description
Start The eNodeB starts or restarts the timer for a UE while sending data
radio bearer (DRB) data to or receiving DRB data from the UE.
Before the uplink synchronization timer for a UE expires, the eNodeB
continuously sends the Timing Advance Command to the UE.
Expire After the uplink synchronization timer for a UE expires, the eNodeB
no longer sends the Timing Advance Command to the UE, and
determines that the UE enters the out-of-synchronization state after the
uplink time alignment timer on the eNodeB side expires.
Timer Settings
Configure the parameter for the uplink synchronization timer based on Table 3-3. This
parameter is maintained only on the eNodeB side.
Table 3-3 Parameter for the uplink synchronization timer
Value of Parameter for the Uplink Description

GLOBALPROCSWITCH Synchronization Timer
.QciParaEffectFlag
ON QCIPARA.UlSynTimerFor The
Qci QCIPARA.UlSynTimerFor

eRAN
Value of Parameter for the Uplink Description

GLOBALPROCSWITCH Synchronization Timer
.QciParaEffectFlag
OFF RrcConnStateTim- Qci parameter is

er.UlSynTimer recommended.
l A smaller value of the parameter for the uplink synchronization timer results in a higher
probability of the UE entering the out-of-synchronization state, a shorter time for the UE
to occupy PUCCH and SRS resources, and a larger number of RA requests initiated by
the UE.
l A larger value of the parameter for the uplink synchronization timer results in a lower
probability of the UE entering the out-of-synchronization state, a longer time for the UE
to occupy PUCCH and SRS resources, and a smaller number of RA requests initiated by
the UE.
l If the parameter for the uplink synchronization timer is set to 0, the parameter does not
take effect, which means the uplink synchronization timer will never expire.
3.3.3 UE Inactivity Timer
Working Principles
The eNodeB determines whether a UE is in RRC_CONNECTED mode based on the state of
the UE inactivity timer. Table 3-4 describes the working principles of this timer.
Table 3-4 Working principles of the UE inactivity timer

Action Description
Start The eNodeB starts or restarts the timer for a UE while sending data to
or receiving data from the UE. Before the UE inactivity timer expires,
the eNodeB determines that the UE is in RRC_CONNECTED mode.
Expire After the UE inactivity timer expires, the eNodeB sends an RRC
Connection Release message to the UE; the UE is then released and
enters the RRC_IDLE mode. This prevents an inactive UE from
occupying radio resources for a long time.
NOTE
If the UE inactivity timer for an out-of-synchronized UE expires, the UE enters the synchronization state
first. Then, the eNodeB sends an RRC Connection Release message to the UE, and the UE enters the
RRC_IDLE mode.
Timer Settings
Configure the parameter for the UE inactivity timer based on Table 3-5. This parameter is
maintained only on the eNodeB side. If the parameter setting is changed, the change applies to
UEs that access the network afterwards.

eRAN
Table 3-5 Parameter for the UE inactivity timer

Value of Parameter for the UE Description
GLOBALPROCSWITCH Inactivity Timer
.QciParaEffectFlag
ON QCIPARA.UeInactiveTime The
rForQci QCIPARA.UeInactiveTime
rForQci parameter is
OFF RrcConnStateTim- recommended.
er.UeInactiveTimer
When a UE does not send data to or receive data from the eNodeB:
l If the parameter for the UE inactivity timer is set to a smaller value, the UE will be
released earlier, and the UE sends the RRC connection setup requests to the eNodeB
more frequently. Because the number of UEs released normally increases, the service
drop rate decreases.
l If the parameter for the UE inactivity timer is set to a larger value, the UE will be
released later, the RRC connection between the UE and the eNodeB maintains for a
longer time, and the UE occupies radio resources for a longer time as well. Because the
number of UEs released normally decreases, the service drop rate increases.
l If the parameter for the UE inactivity timer is set to 0, the parameter does not take effect,
which means the UEs are always in RRC_CONNECTED mode.
If the length of the uplink synchronization timer specified by QCIPARA.UlSynTimerForQci
or RrcConnStateTimer.UlSynTimer is greater than the length of the UE inactivity timer
specified by QCIPARA.UeInactiveTimerForQci or RrcConnStateTimer.UeInactiveTimer,
the UE enters the RRC_IDLE mode directly.

eRAN
Uplink Timing Control Feature Parameter Description 4 Related Features
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features

Feature ID Feature Name Description
LOFD-001008 Ultra High Speed LOFD-001008 Ultra High Speed Mobility

Mobility takes priority over LBFD-070101 Uplink
Timing Based on PUCCH. If the
Cell.HighSpeedFlag parameter is set to
ULTRA_HIGH_SPEED(Ultra high speed
cell flag) or
EXTRA_HIGH_SPEED(Extra high speed
cell flag), LBFD-070101 Uplink Timing
Based on PUCCH does not take effect.
NOTE
LOFD-001008 Ultra High Speed Mobility does
not apply to micro eNodeBs. Therefore, the
mutually exclusive relationship between
LBFD-070101 Uplink Timing Based on PUCCH
and LOFD-001008 Ultra High Speed Mobility
does not involve micro eNodeBs.
LOFD-001031 Extended CP LOFD-001031 Extended CP takes priority

over LBFD-070101 Uplink Timing Based on
PUCCH. If the Cell.UlCyclicPrefix
parameter is set to
EXTENDED_CP(Extended),
LBFD-070101 Uplink Timing Based on
PUCCH does not take effect.
NOTE
LOFD-001031 Extended CP does not apply to
micro eNodeBs. Therefore, the mutually
exclusive relationship between LBFD-070101
Uplink Timing Based on PUCCH and
LOFD-001031 Extended CP does not involve
micro eNodeBs.

eRAN
Impacted Features
LBFD-002017 DRX l When LBFD-002017 DRX is enabled,

parameters related to DRX are restrained
by uplink timing. For details, see DRX
and Signaling Control Feature
Parameter Description. When both
LBFD-002017 DRX and LBFD-070101
Uplink Timing Based on PUCCH are
enabled, parameters related to DRX are
no longer restrained by uplink timing,
and therefore the power consumption of
UEs can be further reduced.
l If LBFD-002017 DRX is enabled, the
eNodeB receives CQIs in PUCCH from
UEs only when the UEs are in the DRX
active time. The timing offset
measurement accuracy depends on the
number of CQIs in PUCCH received by
the eNodeB. If the long DRX cycle
duration is greater than or equal to 160
ms, to ensure that the eNodeB can
measure a timing offset accurately before
delivering the Timing Advance
Command, the Timing Advance
Command sending period must be
extended to enable the eNodeB to obtain
sufficient CQIs in PUCCH. However,
extending the Timing Advance
Command sending period decreases the
supported mobility speed of UEs.
l If the eNodeB does not receive a valid
periodic CQI report within eight
consecutive periodic CQI reporting
periods from a UE in DRX sleep time,
the eNodeB instructs the UE to send an
aperiodic CQI report in the DRX active
time. The aperiodic CQI report must be
sent based on CQI_ONLY scheduling if
the UE does not have uplink data to
transmit. CQI_ONLY scheduling
consumes air interface resources and
reduces gains offered by LBFD-070101
Uplink Timing Based on PUCCH.

eRAN
LOFD-00110501 Dynamic DRX The impact of LBFD-070101 Uplink Timing

Based on PUCCH on LOFD-00110501
Dynamic DRX is the same as that on
LBFD-002017 DRX.

eRAN
Uplink Timing Control Feature Parameter Description 5 Network Impact
5 Network Impact
System Capacity
In LBFD-070101 Uplink Timing Based on PUCCH, when the eNodeB adopts the periodic
decision and event triggering policy in the Timing Advance Command, fewer control channel
elements (CCEs) in the PDCCH are consumed for measuring uplink timing offsets based on
the DMRS for PUSCH, and therefore the PDCCH can support more UEs. The number of
reduced CCEs varies according to the number of users in a network, user distribution, and
service type, and therefore cannot be quantified.
Network Performance
In LBFD-070101 Uplink Timing Based on PUCCH, when the eNodeB adopts the periodic
decision and event triggering policy in the Timing Advance Command, fewer physical
resource blocks (PRBs) in the PUSCH are consumed for measuring uplink timing offsets
based on the DMRS for PUSCH, and the usage of PRB in the PUSCH decreases. However, if
a large number of UEs exist in a cell, the number of service drops and the number of E-RAB
setup failures may increase slightly. The changes in the previously mentioned counters vary
according to the number of users in a network, user distribution, and service type, and
therefore cannot be quantified.

eRAN
Uplink Timing Control Feature Parameter Description 6 Engineering Guidelines
6 Engineering Guidelines
6.1 When to Use

It is recommended that Uplink Timing Based on PUCCH be enabled when both the following
conditions are met:
l The SRS resources cannot support uplink timing required by all the UEs in a cell.
For example:
– The average number of uplink synchronized UEs is greater than the average number
of UEs allocated with SRS resources (the value of the L.Traffic.User.Ulsync.Avg
counter is greater than the value of the L.Traffic.User.SRS.Avg counter).
– No SRS resources are available in the cell (the SRSCfg.SrsCfgInd parameter is set
to BOOLEAN_FALSE).
l Pre-scheduling does not take effect.
When pre-scheduling or intelligent pre-scheduling is enabled, the eNodeB actively
initiates uplink scheduling for UEs that are not allocated SRS resources. In this situation,
the eNodeB measures timing offsets of UEs based on PUSCH DMRSs. If Uplink Timing
Based on PUCCH is enabled in this scenario, the eNodeB measures timing offsets of
UEs based on both PUSCH DMRSs and CQIs on PUCCH. However, timing offsets
calculated based on PUSCH DMRSs are prioritized for uplink timing adjustment. In this
situation, Uplink Timing Based on PUCCH offers smaller gains.
6.2 Required Information

Collect the counters listed in Table 6-1 to monitor the operation of this feature.
Table 6-1 Counters related to uplink timing control

Counter ID Counter Name Description
1526728764 L.ChMeas.PRB.PUSCH.Avg Average number of used PUSCH

PRBs

eRAN
1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used for

uplink DCI in a measurement
period
1526727412 to L.ChMeas.PUSCH.MCS.0 to Number of times MCS index 0 is

1526727443 L.ChMeas.PUSCH.MCS.31 selected for scheduling on the
PUSCH ~ Number of times MCS
index 31 is selected for scheduling
on the PUSCH
6.3 Planning
N/A
6.4 Deployment
6.4.1 Requirements
Operating Environment
The LBBPd or UBBPd must be used.
Transmission Networking
None
License
None
6.4.2 Data Preparation

Required Data
The following table describes the parameters that must be set in the TimeAlignmentTimer
MO to configure the timing measurement mode and uplink time alignment timer length.

eRAN
Parameter Name Parameter ID Setting Notes
Timing Measurement TimeAlignmentTim- This parameter specifies the method

Mode er.TimingMeasMode of measuring uplink timing offsets.
l When this parameter is set to
INVALID(Invalid Timing
Measurement Mode), the
eNodeB measures the timing
offset of the UE based on the
SRS or the DMRS for PUSCH.
l When this parameter is set to
ALLMEASMODE(All Timing
Measurement Mode), the
eNodeB measures the timing
offset of the UE based on both
the SRS and DMRS for PUSCH
or based on both the CQIs in
PUCCH and DMRS for PUSCH.
When LBFD-070101 Uplink
Timing Based on PUCCH is
enabled, the value
ALLMEASMODE(All Timing
Measurement Mode) is
recommended.
Uplink time alignment TimeAlignmentTim- This parameter specifies the length

timer er.TimeAlignmentTimer of the uplink time alignment timer
for UEs in the cell.
When the TimeAlignmentTim-
er.TimingAdvCmdOptSwitch
parameter is set to ON, the eNodeB
adopts the "periodic evaluation and
event-triggering" policy. In this
case, the value SF10240(10240
subframes) is recommended.
Scenario-specific Data
Scenario 1: DRX is disabled, or DRX is enabled and the long DRX cycle is less than 160
ms.
MO to configure the uplink Timing Advance Command optimization switch and TA
command sending period.

eRAN
Uplink timing TimeAlignmentTim- If this parameter is set to ON(On), the

advance command er.TimingAdvCmdOpt eNodeB sends fewer Timing Advance
optimization switch Switch Commands to motionless or low-mobility
UEs to save air interface resources and
reduce power consumption for UEs in
DRX mode. Therefore, the value
ON(On) is recommended.
TA Command TimeAlignmentTim- This parameter takes effect only when the

Sending Period er.TACmdSendPeriod TimeAlignmentTim-
er.TimingAdvCmdOptSwitch parameter
is set to ON(On). The default value
SF928(928 subframes) is recommended.
Scenario 2: DRX is enabled and the long DRX cycle is greater than or equal to 160 ms.
MO to configure the uplink Timing Advance Command optimization switch and TA
command sending period.
Uplink timing TimeAlignmentTim- If this parameter is set to ON(On), the

advance command er.TimingAdvCmdOpt eNodeB sends fewer Timing Advance
optimization switch Switch Commands to motionless or low-mobility
UEs to save air interface resources and
reduce power consumption for UEs in
DRX mode. Therefore, the value
ON(On) is recommended.
TA Command TimeAlignmentTim- This parameter takes effect only when the

Sending Period er.TACmdSendPeriod TimeAlignmentTim-
er.TimingAdvCmdOptSwitch parameter
is set to ON(On). The value
SF5088(5088 subframes) is
recommended.
6.4.3 Initial Configuration

Using the CME
This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME. For
detailed operations, see CME-based Feature Configuration.
Using MML Commands

ms.

eRAN
Step 1 Run the MOD TATIMER command to configure the timing measurement mode, length of
the uplink time alignment timer, uplink Timing Advance Command optimization switch, and
TA command sending period.
----End
the uplink time alignment timer, uplink Timing Advance Command optimization switch, and
TA command sending period.
----End
MML Command Examples

ms.
MOD TATIMER: LocalCellId=0, TimingMeasMode=ALLMEASMODE,
TimeAlignmentTimer=SF10240, TimingAdvCmdOptSwitch=ON, TACmdSendPeriod=SF928;
MOD TATIMER: LocalCellId=0, TimingMeasMode=ALLMEASMODE,
TimeAlignmentTimer=SF10240, TimingAdvCmdOptSwitch=ON, TACmdSendPeriod=SF5088;
6.4.4 Activation Observation
Using MML Commands

Run the LST TATIMER command on the eNodeB to verify that the TimingMeasMode
parameter value is ALLMEASMODE, preliminarily determining that Uplink Timing Based
on PUCCH has taken effect.
Using Performance Counters

If the value of neither of the counters listed in Table 6-2 is zero, Uplink Timing Based on
PUCCH takes effect.
Table 6-2 Counters related to Uplink Timing Based on PUCCH
1526730143 L.Traffic.User.TAMeas.PUC Average number of UEs whose uplink

CH.Avg timing offsets are measured based on
the PUCCH
1526730144 L.Traffic.User.TAMeas.PUC Maximum number of UEs whose uplink

CH.Max timing offsets are measured based on
the PUCCH

eRAN
6.4.5 Deactivation
Using the CME
For detailed operations, see CME-based Feature Configuration.
Using MML Commands

ms.
Step 1 Run the MOD TATIMER command to configure the timing measurement mode and the
length of the uplink time alignment timer.
----End
the uplink time alignment timer, and uplink Timing Advance Command optimization switch.
----End

ms.
If the Uplink timing advance command optimization switch parameter is set to OFF(Off),
SF1920(1920 subframes) is recommended for the Uplink time alignment timer parameter.
MOD TATIMER: LocalCellId=0, TimingMeasMode=INVALID, TimeAlignmentTimer=SF1920;
If the Uplink timing advance command optimization switch parameter is set to ON(On),
SF10240(10240 subframes) is recommended for the Uplink time alignment timer
parameter.
MOD TATIMER: LocalCellId=0, TimingMeasMode=INVALID, TimeAlignmentTimer=SF10240;
MOD TATIMER: LocalCellId=0, TimingMeasMode=INVALID, TimeAlignmentTimer=SF10240,
TimingAdvCmdOptSwitch=OFF;
6.4.6 Reconfiguration
The following table describes the parameters that must be set in the RrcConnStateTimer
MO to configure the uplink synchronization timer length and UE inactivity timer length.

eRAN
Uplink Sync Timer RrcConnStateTim- This parameter indicates the timer used
er.UlSynTimer to govern the period in which the
eNodeB maintains uplink
synchronization for a UE. After this timer
expires, the eNodeB does not send
Timing Advance Command to the UE.
The value 180 is recommended.
Ue inactive timer RrcConnStateTim- This parameter indicates the length of the

er.UeInactiveTimer UE inactivity timer for UEs that do not
have QCI 1 bearers. The value 20 is
recommended.

MOD RRCCONNSTATETIMER: UlSynTimer=180, UeInactiveTimer=20;
6.5 Performance Monitoring

The operation of Uplink Timing Based on PUCCH can be monitored based on the counters in
Table 6-3.
Table 6-3 Counters related to Uplink Timing Based on PUCCH

1526730143 L.Traffic.User.TAMeas.PUCCH Average number of UEs whose

.Avg uplink timing offsets are measured
based on the PUCCH
1526730144 L.Traffic.User.TAMeas.PUCCH Maximum number of UEs whose

.Max uplink timing offsets are measured
based on the PUCCH
1526728764 L.ChMeas.PRB.PUSCH.Avg Average number of used PUSCH

PRBs
1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used for

uplink DCI in a measurement
period
1526727412 to L.ChMeas.PUSCH.MCS.0 to Number of times MCS index 0 is

1526727443 L.ChMeas.PUSCH.MCS.31 selected for scheduling on the
PUSCH to number of times MCS
index 31 is selected for scheduling
on the PUSCH

eRAN
After Uplink Timing Based on PUCCH is enabled, the uplink timing offsets of some UEs in a
cell are measured based on CQIs on PUCCH, which reduces air interface resources consumed
by uplink timing offset measurement based on PUSCH DMRSs. Therefore, do as follows:
l Observe the L.Traffic.User.TAMeas.PUCCH.Avg counter to obtain the average number
of users whose uplink timing offsets are measured based on the PUCCH.
l Observe the L.Traffic.User.TAMeas.PUCCH.Max counter to obtain the maximum
number of users whose uplink timing offsets are measured based on the PUCCH.
l Observe the L.ChMeas.PRB.PUSCH.Avg counter to learn that the average number of
used PUSCH PRBs decreases.
l Observe the L.ChMeas.CCE.ULUsed counter to learn that the number of PDCCH
CCEs used for uplink DCI in a measurement period decreases.
l Observe counters L.ChMeas.PUSCH.MCS.0 to L.ChMeas.PUSCH.MCS.31 to learn
that the number of scheduling times on the PUSCH decreases. The number of scheduling
times on the PUSCH is equal to the sum of L.ChMeas.PUSCH.MCS.0 to
L.ChMeas.PUSCH.MCS.31 counter values.
6.6 Parameter Optimization

When DRX is enabled, scheduling request (SR) false detection causes unnecessary uplink
scheduling, which consumes air interface resources and reduces gains generated by
LBFD-070101 Uplink Timing Based on PUCCH.
PUSCH DTX detection helps avoid unnecessary uplink scheduling caused by SR false
detection. Therefore, if both DRX and LBFD-070101 Uplink Timing Based on PUCCH are
enabled, you are also advised to enable PUSCH DTX detection.
6.7 Possible Issues

None

eRAN
Uplink Timing Control Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
QciPara UlSynTi ADD LBFD-0 RRC Meaning: Indicates the timer used to govern the
merFor QCIPA 02007 / Connect period in which the eNodeB maintains uplink
Qci RA TDLBF ion synchronization for UEs that have bearers of a QCI.
MOD D-00200 Manage After this timer expires, the eNodeB does not send the
QCIPA 7 ment Timing Advance Command to the UE. This parameter
RA LOFD-0 Enhance does not take effect when set to 0. That is, the eNodeB
81218 d will constantly send the Timing Advance Command to
LST the UE to maintain uplink synchronization for the UE.
QCIPA TDLOF Extende
d QCI If a UE has bearers of several QCIs, the eNodeB
RA D-11023 selects the longest uplink synchronization timer of
0 Enhance bearers with the highest QCI-specific priority
LTROF d QoS specified by the UeInactiveTimerPri parameter as the
D-11120 for uplink synchronization timer for the UE. This
1/ MCPTT parameter applies only to LTE FDD and LTE TDD.
TDLOF (Trial)
GUI Value Range: 0~3600
D-12110 MCPTT
3 QoS Unit: s
TDLOF Manage Actual Value Range: 0~3600
D-12110 ment Default Value: 180
5 RRC
and
DRX
Policy
for
Public
Safety

eRAN

nd
QciPara UeInacti ADD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
veTimer QCIPA 02007 / Connect timer for UEs that have bearers of a QCI. If the
ForQci RA TDLBF ion eNodeB detects that a UE has neither received nor
MOD D-00200 Manage sent data for a period exceeding the value of this
QCIPA 7 ment parameter, the eNodeB releases the RRC connection
RA LOFD-0 Enhance for this UE. If this parameter is set to 0, the UE
81218 d inactivity timer is not used. This parameter takes
LST effect only for UEs that will access the network after
QCIPA TDLOF Extende
d QCI this parameter is set. If a UE has bearers of several
RA D-11023 QCIs, the eNodeB selects the longest UE Inactivity
0 Enhance Timer of bearers with the highest QCI-specific
LOFD-0 d QoS priority specified by the UeInactiveTimerPri
81229 / for parameter as the UE inactivity timer for the UE. This
TDLOF MCPTT parameter applies only to LTE FDD and LTE TDD.
D-08122 (Trial)
9 Voice
Characte Unit: s
LTROF
D-11120 ristic Actual Value Range: 0~3600
1/ Awarene Default Value: 20
TDLOF ss
D-12110 Scheduli
3 ng
TDLOF MCPTT
D-12110 QoS
4 Manage
ment
LTROF
D-11120 Congesti
3/ on
TDLOF Control
D-12110 for
5 Public
Safety
RRC
and
DRX
Policy
for
Public
Safety

eRAN

nd
TimeAli Timing MOD LBFD-0 Uplink Meaning: Indicates the method of measuring uplink
gnment MeasMo TATIM 70101 Timing timing offsets. If this parameter is set to INVALID,
Timer de ER Based uplink timing offsets are measured based on the
LST on demodulation reference signal (DMRS) for PUSCH or
TATIM PUCCH sounding reference signal (SRS). If this parameter is
ER set to ALLMEASMODE, uplink timing offsets are
measured based on the DMRS for PUSCH and SRS or
based on the DMRS for PUSCH and channel quality
indicator (CQI) in PUCCH. In addition, the value ON
of the TimingAdvCmdOptSwitch parameter takes
effect regardless of the actual parameter setting. That
is, the eNodeB always sends the Timing Advance
Command to UEs. In this case, it is recommended that
the TimeAlignmentTimer parameter be set to
SF10240. The value ALLMEASMODE applies only
to LTE FDD cells. The parameter value INVALID
takes effect in a cell regardless of the actual parameter
setting in any of the following scenarios: (1) The cell
is established on an LBBPc. (2) The UlCyclicPrefix
parameter is set to EXTENDED_CP. (3) The
HighSpeedFlag parameter is set to HIGH_SPEED,
ULTRA_HIGH_SPEED, or EXTRA_HIGH_SPEED.
(4) The TX/RX mode of the cell is 2T8R. This
parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: INVALID(Invalid Timing
Measurement Mode), ALLMEASMODE(All Timing
Measurement Mode)
Unit: None
Actual Value Range: INVALID, ALLMEASMODE
Default Value: INVALID(Invalid Timing
Measurement Mode)

eRAN

nd
TimeAli Timing MOD LEOFD- Breathin Meaning: Indicates whether to enable the mechanism
gnment ResOptS TATIM 111306 / g Pilot of optimized resource scheduling for uplink timing. If
Timer witch ER TDLOF this parameter is set to OFF, the eNodeB adopts the
LST D-12020 existing resource scheduling policy for uplink timing,
TATIM 5 which consumes a large amount of resources used for
ER delivering Timing Advance Commands in large traffic
scenarios.If this parameter is set to ON, the eNodeB
adopts the mechanism of optimized resource
scheduling for uplink timing, which reduces the
number of unnecessary Timing Advance Commands
to be delivered and reduces resources allocated for
uplink timing in large traffic scenarios. The parameter
value ON is recommended in heavily loaded cells
where there is a large number of UEs. This parameter
applies only to LTE FDD.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)

eRAN

nd
TimeAli TaEnhan MOD None None Meaning:

gnment ce TATIM Indicates whether to enable enhanced TA.
Timer ER TaEnhancePuschDmrs: If this option is selected,
LST enhanced TA is enabled, and uplink-synchronization-
TATIM induced overloads over the air interface decrease. If
ER this option is deselected, enhanced TA is disabled.
This option applies only to LTE FDD. This parameter
does not take effect in the following scenarios:
1. The FddTddInd parameter in the Cell MO is set to
CELL_TDD(TDD).
2. The baseband processing unit type is the LBBPc.
3. The HoppingMode parameter in the PUSCHCfg
MO is set to
INTRA_AND_INTER_SUB_FRAME(Inter And
Intra).
4. The HighSpeedFlag parameter in the Cell MO is set
to HIGH_SPEED(High speed cell flag),
ULTRA_HIGH_SPEED(Ultra high speed cell flag), or
EXTRA_HIGH_SPEED(Extra high speed cell flag).
5. The TimingResOptSwitch parameter in the
TimeAlignmentTimer MO is set to OFF.
GUI Value Range:
TaEnhancePuschDmrs(TaEnhancePuschDmrs)
Unit: None
Actual Value Range: TaEnhancePuschDmrs
Default Value: TaEnhancePuschDmrs:Off

eRAN

nd
TimeAli Timing MOD TDLOF RRC Meaning:

gnment AdvCm TATIM D-12110 and Indicates whether optimization of the mechanism for
Timer dOptSwi ER 5 DRX delivering the uplink time alignment command takes
tch LST Policy effect. If the optimization takes effect, the number of
TATIM for unnecessary uplink time alignment commands
ER Public delivered to motionless or low-mobility UEs can be
Safety reduced to save air interface resources and reduce
power consumption of UEs in DRX mode. This
ensures the uplink time alignment performance if the
length of the uplink time alignment timer is set to a
large value.
If this parameter is set to ON, it is recommended that
the TimeAlignmentTimer parameter be set to
SF10240. A smaller value of the TimeAlignmentTim-
er parameter, such as SF5120, leads to a higher
probability of becoming out-of-synchronization in the
uplink for UEs in DRX mode.
If this parameter is set to ON, it is recommended that
the LongDrxCycle parameter be smaller than or equal
to SF320. Otherwise, the uplink time alignment
performance of UEs in DRX mode is affected. This
parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
TimeAli TimeAli MOD LBFD-0 RRC Meaning: Indicates the length of the uplink time
gnment gnment TATIM 02007 Connect alignment timer for UEs in the cell. A UE is
Timer Timer ER TDLBF ion considered not time-aligned in the uplink if the timer
LST D-00201 Manage expires. This parameter applies only to LTE FDD and
TATIM 7 ment LTE TDD.
ER LEOFD- DRX GUI Value Range: SF500(500 subframes), SF750(750
111306 / Breathin subframes), SF1280(1280 subframes), SF1920(1920
TDLOF g Pilot subframes), SF2560(2560 subframes), SF5120(5120
D-12020 subframes), SF10240(10240 subframes),
RRC INFINITY(Infinity)
5 and
TDLOF DRX Unit: None
D-12110 Policy Actual Value Range: SF500, SF750, SF1280, SF1920,
5 for SF2560, SF5120, SF10240, INFINITY
Public Default Value: INFINITY(Infinity)
Safety

eRAN

nd
TimeAli TACmd MOD None None Meaning: Indicates the interval for sending Timing
gnment SendPer TATIM Advance Commands to UEs. This parameter must be
Timer iod ER set only when the TimingAdvCmdOptSwitch
LST parameter is set to ON. If this parameter is set to
TATIM INVALID, none of the parameter settings in the MML
ER Command window takes effect. This parameter
applies only to LTE FDD.
GUI Value Range: INVALID(NULL), SF218(218
subframes), SF343(343 subframes), SF608(608
subframes)
Unit: None
Actual Value Range: INVALID, SF218, SF343,
SF608, SF928, SF1248, SF2528, SF5088
Default Value: SF928(928 subframes)

eRAN

nd
GlobalP QciPara MOD LBFD-0 Radio Meaning: Indicates whether parameters in QciPara,
rocSwitc EffectFl GLOBA 02008 Bearer CellQciPara, and CnOperatorQciPara MOs take
h ag LPROC TDLBF Manage effect. The parameters take effect by default. If this
SWITC D-00201 ment parameter is set to OFF, parameters in StandardQci,
H 7 DRX ExtendedQci, CellStandardQci, CellExtendedQci,
LST CnOperatorStandardQci, and CnOperatorExtendedQci
LBFD-0 Mobility MOs take effect and parameters in QciPara,
GLOBA 02018 / Manage
LPROC CellQciPara, and CnOperatorQciPara MOs do not
TDLBF ment take effect. If this parameter is set to ON, parameters
SWITC D-00201
H Coverag in QciPara, CellQciPara, and CnOperatorQciPara
8 e Based MOs take effect and parameters in StandardQci,
TDLBF Intra- ExtendedQci, CellStandardQci, CellExtendedQci,
D-00201 frequenc CnOperatorStandardQci, and CnOperatorExtendedQci
801 y MOs do not take effect. This parameter applies only to
LBFD-0 Handov LTE FDD and LTE TDD.
0201802 er GUI Value Range: OFF(Off), ON(On)
/ Coverag Unit: None
TDLBF e Based
D-00201 Inter- Actual Value Range: OFF, ON
802 frequenc Default Value: ON(On)
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
0301101 y
/ Handov
TDLOF er
D-00301 Transpo
101 rt
LOFD-0 Overboo
0301102 king
/ Transpo
TDLOF rt
D-00301 Differen
102 tiated
LOFD-0 Flow
0301103 Control
/ Transpo
TDLOF rt
D-00301 Resourc
103 e
Overloa
d
Control

eRAN

nd
RrcCon UlSynTi MOD LBFD-0 RRC Meaning: Indicates the timer used to govern the
nStateTi mer RRCCO 02007 / Connect period in which the eNodeB maintains uplink
mer NNSTA TDLBF ion synchronization for UEs. After this timer expires, the
TETIM D-00200 Manage eNodeB does not send Timing Advance Command to
ER 7 ment the UE. This parameter does not take effect if it is set
LST to 0. That is, the eNodeB will constantly send Timing
RRCCO Advance Command to the UE to maintain uplink
NNSTA synchronization for the UE. If the QciParaEffectFlag
TETIM parameter in the GlobalProcSwitch MO is set to
ER ON(On), the UlSynTimerForQci parameter in the
QciPara MO, rather than this parameter takes effect.
This parameter applies only to LTE FDD and LTE
TDD.
Unit: s
Actual Value Range: 0~3600
Default Value: 180
RrcCon UeInacti MOD LBFD-0 RRC Meaning: Indicates the length of the UE Inactivity
nStateTi veTimer RRCCO 02007 / Connect Timer for UEs that do not have QCI-1 services. If the
mer NNSTA TDLBF ion eNodeB detects that such a UE has neither received
TETIM D-00200 Manage nor sent data for a period exceeding the value of this
ER 7 ment parameter, the eNodeB releases the RRC connection
LST for the UE. If this parameter is set to 0, the UE
RRCCO Inactivity Timer is not used. This parameter takes
NNSTA effect only for such UEs that will access the network
TETIM after the parameter is set. If the QciParaEffectFlag
ER parameter in the GlobalProcSwitch MO is set to
ON(On), the UeInactiveTimerForQci parameter in the
QciPara MO, rather than this parameter takes effect.
This parameter applies only to LTE FDD and LTE
TDD.
Unit: s
Actual Value Range: 0~3600
Default Value: 20

eRAN

nd
Cell HighSpe ADD LOFD-0 High Meaning: Indicates the speed flag of the cell. Set this
edFlag CELL 01007 / Speed parameter to HIGH_SPEED if the cell is used to
MOD TDLOF Mobility provide coverage for a high-speed railway. Set this
CELL D-00100 Ultra parameter to LOW_SPEED in other scenarios. TDD
7 High cells with a bandwidth of 5 MHz or in 8T8R mode can
LST only be configured as low-speed cells. TDD cells
CELL LOFD-0 Speed
01008 / Mobility cannot be configured as ultra-high-speed cells. This
TDLOF parameter applies only to LTE FDD and LTE TDD.
D-00100 GUI Value Range: LOW_SPEED(Low speed cell
8 flag), HIGH_SPEED(High speed cell flag),
ULTRA_HIGH_SPEED(Ultra high speed cell flag),
EXTRA_HIGH_SPEED(Extra high speed cell flag)
Unit: None
Actual Value Range: LOW_SPEED, HIGH_SPEED,
ULTRA_HIGH_SPEED, EXTRA_HIGH_SPEED
Default Value: LOW_SPEED(Low speed cell flag)
Cell UlCycli ADD LBFD-0 Normal Meaning: Indicates the UL cyclic prefix length of a
cPrefix CELL 0100401 CP cell. A cyclic prefix can be a common or extended
MOD / Extende cyclic prefix. An extended cyclic prefix is generally
CELL TDLBF d CP used in a complex environment with a strong multi-
D-00100 path effect and long delay. In a cell, the UL cyclic
LST 401 Broadca prefix length can be different from the DL one. In
CELL st of addition, the UL or DL cyclic prefix length of a cell
LOFD-0 system
01031 / must be the same as that of the cell set up on the same
informat BBP. For details, see 3GPP TS 36.211.
TDLOF ion
D-00103 GUI Value Range: NORMAL_CP(Normal),
1 EXTENDED_CP(Extended)
LBFD-0 Unit: None
02009 / Actual Value Range: NORMAL_CP,
TDLBF EXTENDED_CP
D-00200
9/ Default Value: NORMAL_CP(Normal)
MLBFD
-120002
29

eRAN

nd
SRSCfg SrsCfgI MOD LBFD-0 Physical Meaning: Indicates whether to configure sounding
nd SRSCF 02003 / Channel reference signal (SRS) resources for UEs in a cell.
G TDLBF Manage The value BOOLEAN_TRUE indicates that SRS
LST D-00200 ment resources are available in the cell and can be
SRSCF 3 DL 4- configured for UEs in the cell. The value
G TDLAO Layer BOOLEAN_FALSE indicates that no SRS resource is
FD-081 MIMO available in the cell, and therefore no UE in the cell is
409 Based configured with SRS resources. This parameter does
on TM9 not take effect on: (1) FDD cell that is established on
TDLEO an LBBPc and uses four or more RX antennas. (2)
FD-121 DL FDD cell that is established on an LBBPc and uses
615 Flexible extended cyclic prefix (CP) in the uplink. (3) TDD
TDLOF 3D- cell established on an LBBPc. If this parameter does
D-00104 Beamfor not take effect on a cell but SRS resources are
9 ming available in the cell, SRS resources can be configured
Single for UEs in the cell. This parameter applies only to
Streami LTE FDD and LTE TDD.
ng GUI Value Range: BOOLEAN_FALSE(False),
Beamfor BOOLEAN_TRUE(True)
ming
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)

eRAN
Uplink Timing Control Feature Parameter Description 8 Counters
8 Counters
Table 8-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526727412 L.ChMeas.PUSCH. Number of times Multi-mode: None Basic Scheduling

MCS.0 MCS index 0 is GSM: None Modulation: DL/UL
scheduled on the QPSK, DL/UL
PUSCH UMTS: None
16QAM, DL
LTE: 64QAM
LBFD-002025
Basic Scheduling
LBFD-001005
Modulation: DL/UL
TDLBFD-002025 QPSK, DL/UL
TDLBFD-001005 16QAM, DL
64QAM
1526727443 L.ChMeas.PUSCH. Number of times Multi-mode: None Basic Scheduling

MCS.31 MCS index 31 is GSM: None Basic Scheduling
scheduled on the
PUSCH UMTS: None Modulation: DL/UL
QPSK, DL/UL
LTE:
16QAM, DL
LBFD-002025
64QAM
TDLBFD-002025 Modulation: DL/UL
LBFD-001005 QPSK, DL/UL
16QAM, DL
TDLBFD-001005
64QAM
LOFD-001006
UL 64QAM
TDLOFD-001006 UL 64QAM

eRAN

Description
1526728304 L.ChMeas.CCE.UL Number of PDCCH Multi-mode: None Physical Channel

Used CCEs used for GSM: None Management
uplink DCI in a Physical Channel
measurement period UMTS: None
Management
LTE:
LBFD-002003
TDLBFD-002003
1526728333 L.Traffic.User.Ulsy Average number of Multi-mode: None RRC Connection

nc.Avg UL synchronized GSM: None Management
users in a cell RRC Connection
UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526728481 L.Traffic.User.SRS. Average number of Multi-mode: None RRC Connection

Avg UEs configured GSM: None Management
with sounding RRC Connection
reference signal UMTS: None
Management
(SRS) resources in LTE:
a cell LBFD-002007
TDLBFD-002007
1526728764 L.ChMeas.PRB.PU Average number of Multi-mode: None Basic Scheduling

SCH.Avg used PUSCH PRBs GSM: None Basic Scheduling
UMTS: None Adaptive SFN/
LTE: SDMA
LBFD-002025
TDLBFD-002025
LOFD-070205
1526730143 L.Traffic.User.TAM Average number of Multi-mode: None Uplink Timing

eas.PUCCH.Avg UEs whose uplink GSM: None Based on PUCCH
timing offsets are
measured based on UMTS: None
the PUCCH LTE:
LBFD-070101
1526730144 L.Traffic.User.TAM Maximum number Multi-mode: None Uplink Timing

eas.PUCCH.Max of UEs whose GSM: None Based on PUCCH
uplink timing
offsets are UMTS: None
measured based on LTE:
the PUCCH LBFD-070101

eRAN

Description
1526730842 L.ChMeas.PUSCH. Number of initial Multi-mode: None Basic Scheduling

DmrsTaSch uplink GSM: None Basic Scheduling
transmissions of
DMRS TA in a cell UMTS: None
LTE:
LBFD-002025
TDLBFD-002025

eRAN
Uplink Timing Control Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Uplink Timing Control Feature Parameter Description 10 Reference Documents
10 Reference Documents
1. 3GPP TS 36.213 V10.10.0, 4.2.3 "Transmission timing adjustments"

2. 3GPP TS 36.213, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical
layer procedures"
3. 3GPP TS 36.321, "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium
Access Control"
4. DRX and Signaling Control
5. Random Access Control and RACH Optimization
6. Connection Management


Uplink Timing Control (ERAN12.1 - 04)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Uplink Timing Control (ERAN12.1 - 04)

Uploaded by

Copyright:

Available Formats

eRAN

Uplink Timing Control Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2018-08-07) Huawei Proprietary and Confidential i

1 About The Document................................................................................................................... 1

Issue 04 (2018-08-07) Huawei Proprietary and Confidential ii

Issue 04 (2018-08-07) Huawei Proprietary and Confidential iii

1 About The Document

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 1

Change Change Description Parameter Affected

Feature None None N/A

Editorial Revised descriptions in 3.2 Uplink None N/A

Change Change Description Parameter Affected

Feature None None N/A

Editorial Revised descriptions in 3.2 Uplink None N/A

Change Change Description Parameter Affected

Feature None None N/A

Editorial Modified the following sections: Added the N/A

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 2

eRAN12.1 Draft A (2016-12-30)

Change Change Description Parameter Affected

Feature None None N/A

Editorial l Revised descriptions in this None N/A

1.4 Differences Between eNodeB Types

LBFD-070101 Uplink Timing Yes Yes (supported Yes

Function Implementation in Macro, Micro, LampSite, and Pico eNodeBs

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 3

Figure 2-1 Uplink timing control

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 4

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 5

Figure 3-1 Timers maintaining UE states

3.1 Uplink Timing Control During RA

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 6

Figure 3-2 Uplink timing control during RA

3.2 Uplink Timing Control After a Successful RA

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 7

Figure 3-3 Periodic uplink timing adjustment

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 8

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 9

3.3.1 Uplink Time Alignment Timer

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 10

Table 3-1 Working principles of uplink time alignment timers

Uplink time Start l When the UE receives the Timing Advance

Expired l If the UE does not receive the Timing Advance

Uplink time Start l During RA:

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 11

Timer Action Description

Expired l If the eNodeB does not receive an ACK from the

Figure 3-4 Time to restart the uplink time alignment timers

l If the eNodeB adopts the periodic policy:

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 12

– It is recommended that the TimeAlignmentTimer.TimeAlignmentTimer parameter

For details about the relationship between the TimeAlignmentTimer.TimeAlignmentTimer

3.3.2 Uplink Synchronization Timer

Table 3-2 Working principles of the uplink synchronization timer

Table 3-3 Parameter for the uplink synchronization timer

Value of Parameter for the Uplink Description

Issue 04 (2018-08-07) Huawei Proprietary and Confidential 13