Beruflich Dokumente
Kultur Dokumente
Issue 06
Date 2017-10-23
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 6
2.1 Introduction.................................................................................................................................................................... 6
2.2 Benefits........................................................................................................................................................................... 7
5 Related Features...........................................................................................................................30
5.1 LBFD-002007 RRC Connection Management............................................................................................................ 30
5.2 LBFD-002008 Radio Bearer Management...................................................................................................................30
6 Network Impact........................................................................................................................... 32
6.1 LBFD-002007 RRC Connection Management............................................................................................................ 32
7 Engineering Guidelines............................................................................................................. 33
7.1 When to Use................................................................................................................................................................. 33
7.2 Required Information................................................................................................................................................... 33
7.3 Planning........................................................................................................................................................................ 33
7.4 Deployment.................................................................................................................................................................. 33
7.4.1 Precautions.................................................................................................................................................................33
7.4.2 Data Preparation and Feature Activation...................................................................................................................33
7.4.2.1 Data Preparation..................................................................................................................................................... 33
7.4.2.2 Using the CME....................................................................................................................................................... 34
7.4.2.3 Using MML Commands......................................................................................................................................... 34
7.4.3 Activation Observation..............................................................................................................................................34
7.4.4 Deactivation...............................................................................................................................................................35
7.4.5 Reconfiguration......................................................................................................................................................... 35
7.5 Performance Monitoring...............................................................................................................................................35
7.6 Parameter Optimization................................................................................................................................................ 37
7.7 Possible Issues.............................................................................................................................................................. 37
8 Parameters..................................................................................................................................... 40
9 Counters........................................................................................................................................ 71
10 Glossary..................................................................................................................................... 514
11 Reference Documents............................................................................................................. 515
1.1 Scope
This document describes connection management, including its technical principles, related
features, network impact, and engineering guidelines. This document covers the following
features:
Micro BTS3202E
BTS3203E
BTS3911E
BTS3912E
LampSite DBS3900
DBS5900
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.
eRAN12.1 06 (2017-10-23)
This issue includes the following changes.
eRAN12.1 05 (2017-09-15)
This issue includes the following changes.
eRAN12.1 04 (2017-08-30)
This issue includes the following changes.
eRAN12.1 03 (2017-05-31)
This issue includes the following changes.
eRAN12.1 02 (2017-04-26)
This issue includes the following changes.
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
2 Overview
2.1 Introduction
In a Long Term Evolution (LTE) system, connection management involves the setup of
dedicated connections between user equipment (UE), eNodeBs, and mobility management
entities (MMEs); and the release of these connections after services are complete.
Figure 2-1 shows the random access, signaling connection management, and radio bearer
management procedures involved in connection management.
NOTE
For details about security mode control shown in Figure 2-1, see Radio Security Feature Parameter
Description.
1. Random access: The UE performs a random access procedure when it needs to set up a
connection with the network for service requests, location updates, paging, or other
reasons. For details about this procedure, see Random Access Control and RACH
Optimization Feature Parameter Description.
2. Signaling connection setup: Signaling connections are established between the UE and
the MME. Signaling connections are set up before the security mode control. There are
two types of signaling connections:
– RRC connections: signaling connections between the eNodeB and UE over the air
interface
– Dedicated S1 connection: signaling connection between the eNodeB and MME
3. E-RAB setup: When the UE requests a service, the MME instructs the eNodeB to set up
an E-UTRAN radio access bearer (E-RAB), including a radio bearer.
2.2 Benefits
Connection management is a basic network feature. It is a prerequisite for UEs to access the
network and perform services on established bearers.
1. The UE sends the eNodeB an RRC Connection Request message containing the reason
for the RRC connection setup.
NOTE
l The reason for RRC connection setup is related to the NAS process and NAS session types.
For details, see 3GPP TS 24.301 V8.1.0.
l The RRC Connection Request message contains the UE_ID field. If the upper layer provides
the S-TMSI, the UE signals the S-TMSI to the eNodeB. If no S-TMSI is available, the UE
signals a random value ranging from 0 to 240-1 to the eNodeB. The international mobile
subscriber identity (IMSI) of the UE is unknown to the eNodeB.
2. The eNodeB sets up the context for the UE.
If the eNodeB receives multiple RRC Connection Request messages from a UE within a
length of time equal to that specified by the
RrcConnStateTimer.FilterReptRrcConnReqTimer and UeTimerConst.T300
parameters, combined, the eNodeB handles only the last message.
Within a length of time equal to that specified by the UeTimerConst.T300 and
RrcConnStateTimer.FilterReptRrcConnReqTimer parameters, combined, the eNodeB
measures the number of RRC Connection Request messages sent by a UE, except in
high-priority access and emergency call scenarios. If the number of RRC Connection
Request messages sent by a UE is greater than the value of the
GlobalProcSwitch.RrcConnPunishThd parameter, the eNodeB responds to the UE
with an RRC Connection Reject message containing the wait time IE. The value of this
wait time is determined by the RRCCONNSTATETIMER.T302 parameter. Upon
receiving the message, the UE sends another RRC Connection Request message only
after the wait time expires.
3. The eNodeB admits the connection without any judgment and allocates SRB1 resources
to the UE.
– The procedure continues if any of the following conditions is met:
n The admission is successful.
n The admission fails, but resource pre-emption is enabled for the UE.
NOTE
To determine whether the number of UEs exceeds the UE quantity license, see 3.4
Dedicated S1 Connection Setup. For UE admission and resource pre-emption, see
Admission and Congestion Control Feature Parameter Description.
– If admission fails and there is no resource pre-emption enabled, the eNodeB sends
an RRC Connection Reject message to the UE.
n If an RRC connection setup request is rejected, the UE needs to wait for a
period before sending another RRC connection setup request. The length of
this period is determined by a timer specified by the
RrcConnStateTimer.T302 parameter. This timer starts when the UE receives
an RRC Connection Reject message and stops when the UE enters
RRC_CONNECTED mode or cell reselection is performed.
n The eNodeB instructs the UE to lower the cell reselection priority by sending
the UE an RRC Connection Reject message containing the deprioritisationReq
IE. Upon receiving the message, the UE attempts to access the network from
other cells, thereby relieving the cell overload. The RRC Connection Reject
message contains the deprioritisationReq IE when the
CELLALGOSWITCH.DeprioritisationDeliverInd parameter is not set to
UNDELIVER. When the RRC Connection Reject message contains the
deprioritisationReq IE and the UE supports the IE, the timer specified by the
UETIMERCONST.T325 parameter starts. The following table lists the
possible circumstances in this case.
Scenario Action
NOTE
The deprioritisationReq IE has been introduced since 3GPP Release 11. For details,
see 3GPP TS 36.331.
4. The eNodeB sends an RRC Connection Setup message containing SRB1 resource
configurations to the UE.
5. The UE configures radio resources based on the SRB1 resource information indicated in
the RRC Connection Setup message, and then sends an RRC Connection Setup
Complete message to the eNodeB. After the eNodeB receives the RRC Connection
Setup Complete message, the RRC connection is set up.
The timer for the eNodeB to wait for an RRC Connection Setup Complete message is
specified by the ENodeBConnStateTimer.WaitRrcConnSetupCmpTimer parameter.
The eNodeB starts another timer to wait for the UE to send other messages over the Uu
interface. The timer is specified by the following parameters:
– ENodeBConnStateTimer.UuMessageWaitingTimer if the UE is not running QCI
1 services
– ENodeBConnStateTimer.UuMessageWaitingTimerQci1 if the UE is running QCI
1 services
A UE starts the timer specified by the UeTimerConst.T310 parameter when both of the following
conditions are met:
1. The number of out-of-sync indications consecutively received by the UE from lower layers has
reached the upper limit specified by the UeTimerConst.N310 parameter.
2. None of the timers specified by the following parameters are running:
l UeTimerConst.T300
l UeTimerConst.T301
l RrcConnStateTimer.T304ForEutran
l RrcConnStateTimer.T304ForGeran
l UeTimerConst.T311
When the timer specified by the UeTimerConst.T310 parameter is running and the number of in-
sync indications consecutively received from lower layers has reached the upper limit specified by
the UeTimerConst.N311 parameter, the UE stops the timer specified by the UeTimerConst.T310
parameter.
l A handover fails.
A QCI-specific RLF timer and constants can be configured in the RlfTimerConstGroup MO
to satisfy the requirements of different services for such a timer and constants if bearers with
different QCIs are set up for UEs. The eNodeB delivers the RLF timer and constants to a UE
in the RRCConnectionSetup, RRCConnectionReconfiguration, and
RRCConnectionReestablishment messages. For details, see 3GPP TS 36.331. The following
table lists recommended parameter values.
The cause value contained in the message depends on the reason for the RRC connection
reestablishment.
l An RRC connection reconfiguration failure
The message contains the cause value "reconfigurationFailure".
l A handover failure
The message contains the cause value "handoverFailure".
l A radio link failure
The message contains the cause value "otherFailure".
In the cause value, the C-RNTI and physCellId IEs indicate the C-RNTI and physical cell ID of
the serving cell, respectively.
2. The eNodeB checks whether there is a UE context.
If there is, the eNodeB proceeds to 3.
If there is not, the target eNodeB sends an RLF Indication message to the source eNodeB
based on the cell information contained in the RRC Connection Reestablishment Request
message. If the source eNodeB has the UE context, the source eNodeB initiates the
handover process. In the handover, the source eNodeB transfers the UE context to the
target eNodeB. The GlobalProcSwitch.RrcReestOptSwitch parameter specifies whether
the target eNodeB can implement RRC connection reestablishment without UE contexts.
3. The eNodeB authenticates the UE. If the security authentication data in the UE is
consistent with that in the eNodeB, the UE passes authentication. After the
authentication, the eNodeB releases original resources and then performs admission and
resource allocation again.
– If the GlobalProcSwitch.EnhancedRRCReestProtectThd parameter is set to 0 and
the number of RRC Connection Reestablishment Request messages containing the
cause value "reconfigurationFailure" sent by a UE within 1 minute exceeds the
threshold specified by the GlobalProcSwitch.RrcReestProtectThd parameter, the
eNodeB rejects subsequent RRC connection reestablishment requests containing the
same cause value sent by the UE and the UE enters the RRC idle mode. The
GlobalProcSwitch.RrcReestProtectThd parameter will be disused in later versions.
– The GlobalProcSwitch.RrcReestProtectThd parameter is invalid if the
GlobalProcSwitch.EnhancedRRCReestProtectThd parameter is set to a non-zero
value. In this situation, RRC connection reestablishment protection is enabled. If
the number of RRC connection reestablishment requests sent by a UE to an eNodeB
exceeds the threshold specified by the
GlobalProcSwitch.EnhancedRRCReestProtectThd parameter, the eNodeB
releases the UE and the UE enters the RRC idle mode.
If the UE fails the authentication, the eNodeB rejects the RRC connection
reestablishment request of the UE.
4. The eNodeB sends the UE an RRC Connection Reestablishment message containing
information about the allocated resources. The UE reconfigures radio resources based on
the message, and then starts encryption and integrity protection again.
5. The UE sends an RRC connection reestablishment complete message to the eNodeB,
indicating that RRC connection reestablishment is completed.
l Connected mode
A UE that has set up an RRC connection with the eNodeB is considered to be in
connected mode. The connected mode is further classified by its synchronization state:
– Synchronized
A UE is considered to be in the synchronization state when it is in connected mode
and has established uplink synchronization with the eNodeB. The eNodeB allocates
physical uplink control channel (PUCCH), sounding reference signal (SRS), and
other resources for these UEs.
– Out-of-synchronization
A UE is considered to be in the out-of-synchronization state when it is in connected
mode, but currently has not established uplink synchronization with the eNodeB.
The eNodeB releases physical uplink control channel (PUCCH), sounding reference
signal (SRS), and other resources for these UEs.
l Idle mode
A UE that has not set up an RRC connection with the eNodeB is considered to be in idle
mode. These UEs monitor the paging channel of the eNodeB. For details about UE
behaviors in idle mode, see Idle Mode Management Feature Parameter Description.
l To maintain uplink timing for a UE, the eNodeB delivers timing advance commands to
the UE. Each time the eNodeB receives an ACK message from the UE, the eNodeB
starts or restarts the uplink time alignment timer specified by the
TimeAlignmentTimer.TimeAlignmentTimer parameter. If the timer expires, the
eNodeB considers the UE to have entered the out-of-synchronization state.
l For each UE, the eNodeB also maintains an uplink synchronization timer specified by
the RrcConnStateTimer.UlSynTimer parameter to control whether to deliver a Timing
Advance Command message to the UE. The eNodeB starts or restarts the timer for a UE
when sending data to or receiving data from the UE.
– The eNodeB continuously sends Timing Advance Command messages to the UE
until the timer expires.
– Once it has expired, the eNodeB stops sending the messages, and the UE stops
providing ACK responses. In this situation, the uplink alignment timer expires, and
the eNodeB regards that the UE is in the out-of-synchronization state.
If the UE inactivity timer is shorter than the timer specified by the
RrcConnStateTimer.UlSynTimer parameter, the RRC connection is released for the UE
and the UE enters idle mode.
l Since eRAN12.1, if the InactReSyncCompatSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter is selected when the UE inactivity
timer expires and the resynchronization procedure is ongoing, the eNodeB restarts the
UE inactivity timer and preferentially handles the resynchronization procedure. If the
InactReSyncCompatSwitch option is deselected, the eNodeB releases UEs when the
UE inactivity timer expires, and the UEs enter idle mode.
l The eNodeB instructs the UE to initiate a random access procedure when the eNodeB
needs to transmit data to the UE.
l The UE initiates a random access procedure to restore uplink synchronization if it needs
to transmit data to the eNodeB.
Table 3-1 Parameters specifying the UE inactivity timer when PTT services are ongoing
Value of the Parameter Specifying the UE Inactivity Timer
CELLALGOSWITCH.DynD
rxSwitch Parameter
DynDrxSwitch(DynDrxSwitch QciPara.UeInactivityTimerDynDrxQci
) check box selected
DynDrxSwitch(DynDrxSwitch QciPara.UeInactiveTimerForQci
) check box cleared
Table 3-2 Parameters specifying the UE inactivity timer when voice services are ongoing
GLOBALPR CELLALGOS License Parameter Specifying the UE
OCSWITCH. WITCH.DynD from Table Inactivity Timer
QciParaEffec rxSwitch 3-3
tFlag Setting Setting Activated
No RrcConnStateTim-
er.UeInactiveTimer
NOTE
The preceding license has an impact on the configuration of the UE inactivity timer only when the UE is
performing voice services and the DynDrxSwitch(DynDrxSwitch) check box is cleared under the
CELLALGOSWITCH.DynDrxSwitch parameter.
Table 3-4 Parameters specifying the UE inactivity timer used in other situations
Value of the Value of the Parameter Specifying the UE
GlobalProcSwitch.Qc CELLALGOSWIT Inactivity Timer
iParaEffectFlag CH.DynDrxSwitc
Parameter h Parameter
DynDrxSwitch(Dy RrcConnStateTimer.UeInactiveTimer
nDrxSwitch) check
box cleared
NOTE
The timer expires l The eNodeB instructs the UE to initiate random access when the
eNodeB needs to transmit data to the UE.
l The UE initiates random access when the UE needs to transmit
data to the eNodeB.
– If the synchronization is successful, the radio link of the UE
recovers.
– If the synchronization fails, an RLF has occurred. In this case,
the eNodeB releases the RRC connection for the UE.
1. The UE sends the eNodeB an RRC Connection Setup Complete message containing a
NAS message. Upon receiving the message, the eNodeB allocates a dedicated S1AP ID
to the UE, encapsulates the NAS message and S1AP ID in an Initial UE Message, and
sends the message to the MME.
NOTE
For details about how to select an MME when the eNodeB is connected to multiple MMEs, see
S1-Flex Feature Parameter Description.
2. The MME obtains the cause for this connection setup from the NAS message contained
in the Initial UE Message, handles the UE service request, and assigns a dedicated S1AP
ID to the UE.
– If the UE is not running QCI 1 services, the timer controlling how long the eNodeB
waits for S1AP-related messages from the MME is specified by the
ENodeBConnStateTimer.S1MessageWaitingTimer parameter.
The eNodeB selects a security algorithm supported by both the eNodeB and UE and then sends the
algorithm to the UE using a Security Mode Command message. For details about the security
mode handling mechanism, see Radio Security Feature Parameter Description.
5. The eNodeB performs admission based on the UE quantity license, implements resource
pre-emption for the UE, makes service admission decisions, and allocates resources to
the UE.
– If the UE is successfully admitted, the procedure continues.
– If the admission fails, the eNodeB sends an INITIAL CONTEXT SETUP
FAILURE message to the UE.
NOTE
For admission based on the UE quantity license and UE resource pre-emption, see
Admission and Congestion Control Feature Parameter Description.
6. The eNodeB sends a Security Mode Command message, instructing the UE to start
integrity protection and encryption. At this moment, downlink encryption is started.
7. The eNodeB sends an RRC Connection Reconfiguration message to the UE for the setup
of SRB2 and DRB. Encryption and integrity protection have been performed for this
message.
8. After receiving the Security Mode Command message from the eNodeB, the UE uses the
encryption algorithm specified by the eNodeB to generate security keys for both service
bearers and signaling connections. Then, the UE sends a Security Mode Complete
message, which is not encrypted. After the eNodeB receives this message, uplink
encryption is started.
9. The UE sets up a dedicated S1 connection based on the RRC Connection
Reconfiguration message and then sends an RRC Connection Reconfiguration Complete
message to the eNodeB.
10. The eNodeB sends an Initial Context Setup Response message to the MME.
The eNodeB simultaneously sends security parameters and bearer parameters to the UE. The
security mode setup starts first. The RRC Connection Reconfiguration message can be sent
before the security mode setup ends. This mechanism reduces the delay from the initial UE
access to the bearer setup.
The MME can also release the dedicated S1 connection to simultaneously release all the E-RABs.
For eNodeBs:
l When a UE becomes inactive and the signaling link has been released, the UE may have
lost connections with the network. When the GlobalProcSwitch.UeRelChkLostSwitch
parameter is set to ON(On), the eNodeB checks the connection between the UE and
network.
– If the connection is abnormal, the UE Context Release Request message contains
the cause value "Radio Connection With UE Lost."
– If the connection is proper, the UE Context Release Request message contains the
cause value "User inactivity."
l If a UE in the uplink out-of-synchronization state needs to transmit downlink data, the
eNodeB instructs the UE to initiate random access to restore uplink synchronization with
the eNodeB. The UE can try the restoration for many times. If the restoration fails for the
number of times specified by the GlobalProcSwitch.UeRelReSynTimes parameter, the
eNodeB releases the UE. The release is executed after a delay so that the UE has a
chance to reestablish the RRC connection with the serving cell. The delay is specified by
the CellStandardQci.TrafficRelDelay parameter and is service (QCI) specific. The
CellStandardQci.TrafficRelDelay parameter will be replaced by the
CellQciPara.TrafficRelDelay parameter in later versions.
Figure 4-1 Radio bearer in the E2E service in the overall service architecture
Radio bearers are classified into signaling radio bearers (SRBs) and data radio bearers
(DRBs).
l SRBs carry signaling in the control plane. There are three types of SRBs:
– SRB0: carries RRC signaling through a common control channel (CCCH) in
transparent mode (TM) at the radio link control (RLC) layer before the RRC
connection is successfully set up.
– SRB1: carries RRC signaling messages after the RRC connection is successfully set
up, and carries NAS messages before SRB2 is set up. SRB1 is transmitted through a
dedicated control channel (DCCH) in acknowledged mode (AM) at the RLC layer.
– SRB2: carries NAS signaling through a DCCH in AM mode at the RLC layer.
SRB2 has a lower priority than SRB1, and SRB2 can be set up only after the
security mode is activated.
NOTE
l For details about SRB0, SRB1, and SRB2, see section 6.2.2 in 3GPP TS 36.331 V9.16.0.
l For details about NAS, see 3GPP TS 24.301.
l DRBs carry data in the user plane. A maximum of eight DRBs can be set up between the
UE and the eNodeB. The actual number depends on different QoS classes.
l In this document, radio bearer management refers to SRB2 and DRB management by the
eNodeB after the security mode is set up. It involves the setup, modification, and release
of SRB2 and DRBs.
During radio bearer management, the UE communicates with the eNodeB using the RRC
Connection Reconfiguration message. The RRC connection is reconfigured when a radio
bearer needs to be set up, modified, or released and when handover measurement information
needs to be configured or modified. The application scenarios are differentiated using
different IEs in the RRC Connection Reconfiguration message.
5 Related Features
Impacted Features
None
Impacted Features
None
6 Network Impact
Network Performance
The setting of the GLOBALPROCSWITCH.RrcConnPunishThd parameter increases the
RRC connection setup success rate, prolongs the network reaccess delay, and reduces
resource consumption when abnormal UEs fail to access the network repeatedly.
The RRC connection reject-triggered cell reselection function improves the RRC connection
setup success rate and decreases the network access delay in big events when the number of
RRC connections in a multi-band or multi-RAT cell is far below the upper limit. This function
increases the number of network access attempts when the number of RRC connections in a
multi-band or multi-RAT cell is close to the upper limit. In this situation, the RRC connection
setup success rate and network access delay may decrease. The impact on network
performance increases with the number of UEs that support the deprioritisationReq IE.
Network Performance
None
7 Engineering Guidelines
7.3 Planning
N/A
7.4 Deployment
7.4.1 Precautions
None
Step 2 Run the MOD UETIMERCONST command with the T325 parameter set to a desired value.
MOD UETIMERCONST: LocalCellId=0, T325=MIN5_T325;
----End
Step 3 View the Uu interface tracing result. If the result contains the RRC_CONN_REQ and
RRC_CONN_SETUP_CMP messages, as shown in Figure 7-1, signaling connection
management has been activated.
Step 4 View the S1 interface tracing result. If the result contains the S1AP_INITIAL_UE_MSG and
S1AP_INITIAL_CONTEXT_SETUP_RSP messages as shown in Figure 7-2, radio bearer
management has been activated.
----End
7.4.4 Deactivation
Connection management is a basic function and cannot be deactivated.
7.4.5 Reconfiguration
N/A
1526728217 L.RRC.ConnReq.Att.Emc
1526728218 L.RRC.ConnReq.Att.HighPri
1526728219 L.RRC.ConnReq.Att.Mt
1526728221 L.RRC.ConnReq.Att.MoData
1526728357 L.RRC.ConnReq.Att.DelayTol
1526745657 L.RRC.ConnReq.Att.MoVoiceCall
1526728222 L.RRC.ConnReq.Succ.Emc
1526728223 L.RRC.ConnReq.Succ.HighPri
1526728224 L.RRC.ConnReq.Succ.Mt
1526728226 L.RRC.ConnReq.Succ.MoData
1526728358 L.RRC.ConnReq.Succ.DelayTol
1526745658 L.RRC.ConnReq.Succ.MoVoiceCall
1526728220 L.RRC.ConnReq.Att.MoSig
1526728225 L.RRC.ConnReq.Succ.MoSig
1526726668 L.E-RAB.AttEst.QCI.1
1526726669 L.E-RAB.SuccEst.QCI.1
1526739741 L.E-RAB.FailEst.X2AP.VoIP
1526727545 L.E-RAB.AttEst
1526727544 L.E-RAB.SuccEst
1526739740 L.E-RAB.FailEst.X2AP
1526726686 L.E-RAB.AbnormRel.QCI.1
1526726687 L.E-RAB.NormRel.QCI.1
1526741743 L.E-RAB.NormRel.IRatHOOut.QCI.1
1526727546 L.E-RAB.AbnormRel
1526727547 L.E-RAB.NormRel
1526741752 L.E-RAB.NormRel.IRatHOOut
NOTE
If the RRC setup success rate deteriorates significantly, contact Huawei for technical support.
Fault Handling
Step 1 On the U2000 client, start S1 interface tracing and obtain the tracing result.
Step 2 View the tracing result to check whether there are a large number of
S1AP_INITIAL_CONTEXT_SETUP_FAIL messages. If yes, proceed to the next step. If no,
contact Huawei for technical support.
Step 4 Run the MOD GTPU command with the STATICCHK parameter set to ENABLE(Enable)
to enable the GTP-U tunnel detection function.
Step 5 Run the ADD ENODEBPATH command to add the application type of the IP path
corresponding to the S1 interface. In this step, set the Application Type parameter to S1(S1).
Step 6 Run the DSP IPPATH command to check whether the value of the IP Path Check Result
parameter is Fault. If yes, adjust the IP path according to the network plan. If no, contact
Huawei for technical support.
----End
Alarm
Alarm ID Alarm Name
8 Parameters
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch,
PaDistributeMechOptSwitch, InactReSyncCompatS-
witch, VolteX2HoDelayOptSwitch,
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch
Unit: None
Actual Value Range: RrcSetupOptSwitch,
IucsRrcRecfgMcCombSwitch,
RcrpRrcRecfgMcCombSwitch,
RrcRecfgMcOptSwitch, IdleCsfbRedirectOptSwitch,
UlNasBufferSwitch, IratMeasCfgTransSwitch,
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch,
PaDistributeMechOptSwitch, InactReSyncCompatS-
witch, VolteX2HoDelayOptSwitch,
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch
Default Value: RrcSetupOptSwitch:Off,
IucsRrcRecfgMcCombSwitch:Off,
RcrpRrcRecfgMcCombSwitch:Off,
RrcRecfgMcOptSwitch:Off, IdleCsfbRedirectOptS-
witch:Off, UlNasBufferSwitch:On,
IratMeasCfgTransSwitch:Off,
GeranAnrMcOptSwitch:Off, InactDiscardSwitch:Off,
SRVCCHoBasedUeCapSwitch:Off,
L2GPLMNChooseOptSwitch:Off,
HoInRrcRecfgMcCombSwitch:Off,
UeCapEnquiryCombSwitch:Off,
UeTraceOptSwitch:Off, PaDistributeMechOptS-
witch:On, InactReSyncCompatSwitch:Off,
VolteX2HoDelayOptSwitch:Off, UeUtranCapEnquir-
yOptSwitch:Off, FreqRandomOptSwitch:Off,
MrMdtMeasOptSwitch:Off
RrcCon FilterRe MOD LBFD-0 RRC Meaning: Indicates the length of the timer for the
nStateTi ptRrcCo RRCCO 02007 / Connect eNodeB to filter repeated RRC Connection Request
mer nnReqTi NNSTA TDLBF ion messages. The actually used timer length is the sum of
mer TETIM D-00200 Manage T300 length and the value of this parameter.
ER 7 ment GUI Value Range: 0~15
LST Unit: s
RRCCO
NNSTA Actual Value Range: 0~15
TETIM Default Value: 15
ER
GlobalP RrcCon MOD LBFD-0 RRC Meaning: Indicates the threshold for an RRC
rocSwitc nPunish GLOBA 02007 / Connect connection penalty. Certain UEs may repeatedly fail
h Thd LPROC TDLBF ion to access networks because of incompatibility issues.
SWITC D-00200 Manage If the number of RRC connection setup requests that
H 7 ment the eNodeB receives from a UE within the period
LST specified by T300+FilterReptRrcConnReqTimer
GLOBA exceeds the threshold (a non-zero value), the eNodeB
LPROC imposes a penalty on the UE, rejecting RRC
SWITC connection setup requests from the UE. If this
H parameter is set to 0, the penalty does not take effect.
GUI Value Range: 0~3600
Unit: None
Actual Value Range: 0~3600
Default Value: 0
CellAlg Depriori MOD LBFD-0 RRC Meaning: Indicates whether the RRCConnectionRe-
oSwitch tisation CELLA 02007 / Connect ject message includes the IE deprioritisationReq and
DeliverI LGOSW TDLBF ion the setting of the IE deprioritisationType in the
nd ITCH D-00200 Manage message. If this parameter is set to
LST 7 ment UNDELIVER(UNDELIVER), the
CELLA RRCConnectionReject message does not include the
LGOSW IE deprioritisationReq. If this parameter is set to
ITCH FREQUENCY(FREQUENCY), the
RRCConnectionReject message includes the IE
deprioritisationReq and the value of the IE
deprioritisationType is FREQUENCY. In this case,
after the UE receives an RRCConnectionReject
message, the lowest cell reselection priority is
configured for the serving frequency and the
frequencies contained in the RRCConnectionReject
messages that have been received and include the IE
deprioritisationReq. If this parameter is set to
EUTRA(EUTRA), the RRCConnectionReject
message includes the IE deprioritisationReq and the
value of the IE deprioritisationType is EUTRA. In this
case, after the UE receives an RRCConnectionReject
message, the lowest cell reselection priority is
configured for all E-UTRAN frequencies. For details
about the IEs, see 3GPP 36.331. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: UNDELIVER(UNDELIVER),
FREQUENCY(FREQUENCY), EUTRA(EUTRA)
Unit: None
Actual Value Range: UNDELIVER, FREQUENCY,
EUTRA
Default Value: UNDELIVER(UNDELIVER)
UeTime T325 MOD LBFD-0 RRC Meaning: Indicates the length of timer 325. For
rConst UETIM 02007 / Connect details, see 3GPP TS 36.331. This timer starts when a
ERCON TDLBF ion UE receives an RRCConnectionReject message
ST D-00200 Manage containing the deprioritisationReq IE. When the timer
LST 7 ment expires, the cell reselection priorities that have been
UETIM reduced using RRCConnectionReject for E-UTRAN
ERCON frequencies are restored. This parameter applies only
ST to LTE FDD and LTE TDD.
GUI Value Range: MIN5_T325(MIN5_T325),
MIN10_T325(MIN10_T325),
MIN15_T325(MIN15_T325),
MIN30_T325(MIN30_T325)
Unit: None
Actual Value Range: MIN5_T325, MIN10_T325,
MIN15_T325, MIN30_T325
Default Value: MIN5_T325(MIN5_T325)
ENodeB WaitRrc MOD LBFD-0 RRC Meaning: Indicates the timer for the eNodeB to wait
ConnSta ConnSet ENODE 02007/ Connect for a RRC Connection Setup Complete message.
teTimer upCmpT BCONN TDLBF ion GUI Value Range: 3~15
imer STATET D-00200 Manage
IMER 7 ment Unit: s
ENodeB UuMess MOD LBFD-0 RRC Meaning: Indicates the timer governing the period the
ConnSta ageWaiti ENODE 02007 / Connect eNodeB waits for a response message from a UE
teTimer ngTimer BCONN TDLBF ion when the UE is running non-QCI1 services. If the
STATET D-00200 Manage timer expires, the eNodeB initiates a UE context
IMER 7 ment release over the S1 interface.
LST GUI Value Range: 1~200
ENODE Unit: s
BCONN
STATET Actual Value Range: 1~200
IMER Default Value: 35
ENodeB UuMess MOD LBFD-0 RRC Meaning: Indicates the timer governing the period the
ConnSta ageWaiti ENODE 02007 / Connect eNodeB waits for a response message from a UE
teTimer ngTimer BCONN TDLBF ion when the UE is running services with the QCI of 1. If
Qci1 STATET D-00200 Manage the timer expires, the eNodeB initiates a UE context
IMER 7 ment release over the S1 interface. This parameter applies
LST TDLBF Support only to LTE FDD and LTE TDD.
ENODE D-08110 of GUI Value Range: 1~200
BCONN 1 VoLTE Unit: s
STATET
IMER Actual Value Range: 1~200
Default Value: 35
RrcCon T304For MOD None None Meaning: Indicates the length of the timer T304 for
nStateTi Eutran RRCCO intra-RAT handover. If the UE does not complete the
mer NNSTA handover before this timer expires, the UE reverts
TETIM back to the associated configuration and initiates an
ER RRC connection reestablishment procedure. This
LST parameter applies only to LTE FDD and LTE TDD.
RRCCO GUI Value Range: ms50(50), ms100(100),
NNSTA ms150(150), ms200(200), ms500(500),
TETIM ms1000(1000), ms2000(2000)
ER Unit: ms
Actual Value Range: ms50, ms100, ms150, ms200,
ms500, ms1000, ms2000
Default Value: ms500(500)
RrcCon T304For MOD None None Meaning: Indicates the length of the timer T304 for
nStateTi Geran RRCCO inter-RAT handover to GERAN by CCO. If the UE
mer NNSTA does not complete the handover before this timer
TETIM expires, the UE reverts to the associated configuration
ER and initiates an RRC connection reestablishment
LST procedure. For details, see 3GPP TS 36.331. This
RRCCO parameter applies only to LTE FDD and LTE TDD.
NNSTA GUI Value Range: ms100(100), ms200(200),
TETIM ms500(500), ms1000(1000), ms2000(2000),
ER ms4000(4000), ms8000(8000)
Unit: ms
Actual Value Range: ms100, ms200, ms500, ms1000,
ms2000, ms4000, ms8000
Default Value: ms8000(8000)
RlcPdcp UeMax ADD LBFD-0 Radio Meaning: Indicates the UE-specific maximum number
ParaGro RetxThr RLCPD 02008 / Bearer of RLC ARQ retransmissions, namely the maximum
up eshold CPPAR TDLBF Manage number of AM PDU retransmissions. When the
AGROU D-00200 ment number of retransmissions reaches the value of this
P 8 Data parameter, RRC connection re-establishment is
MOD MLBFD over initiated.
RLCPD -121002 User GUI Value Range: Maxretx_Threshold_t1(1),
CPPAR 05 Plane Maxretx_Threshold_t2(2), Maxretx_Threshold_t3(3),
AGROU Maxretx_Threshold_t4(4), Maxretx_Threshold_t6(6),
P Maxretx_Threshold_t8(8),
LST Maxretx_Threshold_t16(16),
RLCPD Maxretx_Threshold_t32(32)
CPPAR Unit: None
AGROU Actual Value Range: Maxretx_Threshold_t1,
P Maxretx_Threshold_t2, Maxretx_Threshold_t3,
Maxretx_Threshold_t4, Maxretx_Threshold_t6,
Maxretx_Threshold_t8, Maxretx_Threshold_t16,
Maxretx_Threshold_t32
Default Value: Maxretx_Threshold_t32(32)
UeTime N310 MOD LBFD-0 Broadca Meaning: Indicates the maximum number of
rConst UETIM 02009 / st of successive "out of sync" indications received from L1.
ERCON TDLBF system For details, see 3GPP TS 36.331.
ST D-00200 informat GUI Value Range: n1(1), n2(2), n3(3), n4(4), n6(6),
LST 9 ion n8(8), n10(10), n20(20)
UETIM Unit: None
ERCON
ST Actual Value Range: n1, n2, n3, n4, n6, n8, n10, n20
Default Value: n10(10)
UeTime N311 MOD LBFD-0 Broadca Meaning: Indicates the maximum number of
rConst UETIM 02009 / st of successive "in sync" indications received from L1. For
ERCON TDLBF system details, see 3GPP TS 36.331.
ST D-00200 informat GUI Value Range: n1(1), n2(2), n3(3), n4(4), n5(5),
LST 9 ion n6(6), n8(8), n10(10)
UETIM Unit: None
ERCON
ST Actual Value Range: n1, n2, n3, n4, n5, n6, n8, n10
Default Value: n1(1)
RlfTime RlfTime ADD LBFD-0 RRC Meaning: Indicates the RLF timer and constants group
rConstG rConstG RLFTI 02007 / Connect ID. This parameter applies only to LTE FDD and LTE
roup roupId MERCO TDLBF ion TDD.
NSTGR D-00200 Manage GUI Value Range: 0~9
OUP 7 ment
Unit: None
LST
RLFTI Actual Value Range: 0~9
MERCO Default Value: None
NSTGR
OUP
MOD
RLFTI
MERCO
NSTGR
OUP
RMV
RLFTI
MERCO
NSTGR
OUP
RlfTime T301 ADD LBFD-0 RRC Meaning: Indicates the length of the timer T301. For
rConstG RLFTI 02007 / Connect details, see 3GPP TS 36.331. This parameter applies
roup MERCO TDLBF ion only to LTE FDD and LTE TDD.
NSTGR D-00200 Manage GUI Value Range: MS100_T301(100ms),
OUP 7 ment MS200_T301(200ms), MS300_T301(300ms),
MOD MS400_T301(400ms), MS600_T301(600ms),
RLFTI MS1000_T301(1000ms), MS1500_T301(1500ms),
MERCO MS2000_T301(2000ms)
NSTGR Unit: None
OUP
Actual Value Range: MS100_T301, MS200_T301,
LST MS300_T301, MS400_T301, MS600_T301,
RLFTI MS1000_T301, MS1500_T301, MS2000_T301
MERCO
NSTGR Default Value: MS200_T301(200ms)
OUP
RlfTime T310 ADD LBFD-0 RRC Meaning: Indicates the length of the timer T310. For
rConstG RLFTI 02007 / Connect details, see 3GPP TS 36.331. This parameter applies
roup MERCO TDLBF ion only to LTE FDD and LTE TDD.
NSTGR D-00200 Manage GUI Value Range: MS0_T310(0ms),
OUP 7 ment MS50_T310(50ms), MS100_T310(100ms),
MOD MS200_T310(200ms), MS500_T310(500ms),
RLFTI MS1000_T310(1000ms), MS2000_T310(2000ms)
MERCO Unit: None
NSTGR
OUP Actual Value Range: MS0_T310, MS50_T310,
MS100_T310, MS200_T310, MS500_T310,
LST MS1000_T310, MS2000_T310
RLFTI
MERCO Default Value: MS1000_T310(1000ms)
NSTGR
OUP
RlfTime T311 ADD LBFD-0 RRC Meaning: Indicates the length of the timer T311. For
rConstG RLFTI 02007 / Connect details, see 3GPP TS 36.331. This parameter applies
roup MERCO TDLBF ion only to LTE FDD and LTE TDD.
NSTGR D-00200 Manage GUI Value Range: MS1000_T311(1000ms),
OUP 7 ment MS3000_T311(3000ms), MS5000_T311(5000ms),
MOD MS10000_T311(10000ms),
RLFTI MS15000_T311(15000ms),
MERCO MS20000_T311(20000ms),
NSTGR MS30000_T311(30000ms)
OUP
Unit: None
LST
Actual Value Range: MS1000_T311, MS3000_T311,
RLFTI
MS5000_T311, MS10000_T311, MS15000_T311,
MERCO
MS20000_T311, MS30000_T311
NSTGR
OUP Default Value: MS10000_T311(10000ms)
RlfTime N310 ADD LBFD-0 RRC Meaning: Indicates the maximum number of
rConstG RLFTI 02007 / Connect successive "out of sync" indications received from L1.
roup MERCO TDLBF ion For details, see 3GPP TS 36.331. This parameter
NSTGR D-00200 Manage applies only to LTE FDD and LTE TDD.
OUP 7 ment GUI Value Range: n1(1), n2(2), n3(3), n4(4), n6(6),
MOD n8(8), n10(10), n20(20)
RLFTI Unit: None
MERCO
NSTGR Actual Value Range: n1, n2, n3, n4, n6, n8, n10, n20
OUP Default Value: n10(10)
LST
RLFTI
MERCO
NSTGR
OUP
RlfTime N311 ADD LBFD-0 RRC Meaning: Indicates the maximum number of
rConstG RLFTI 02007 / Connect successive "in sync" indications received from L1. For
roup MERCO TDLBF ion details, see 3GPP TS 36.331. This parameter applies
NSTGR D-00200 Manage only to LTE FDD and LTE TDD.
OUP 7 ment GUI Value Range: n1(1), n2(2), n3(3), n4(4), n5(5),
MOD n6(6), n8(8), n10(10)
RLFTI Unit: None
MERCO
NSTGR Actual Value Range: n1, n2, n3, n4, n5, n6, n8, n10
OUP Default Value: n1(1)
LST
RLFTI
MERCO
NSTGR
OUP
S1_HANDOVER_REEST_SWITCH(S1_HANDOVE
R_REEST_SWITCH),
NO_CONTEXT_REEST_SWITCH(NO_CONTEXT
_REEST_SWITCH),
SEC_CMD_REEST_SWITCH(SEC_CMD_REEST_
SWITCH),
WITH_X2_NO_NCELL_REEST_SWITCH(WITH_
X2_NO_NCELL_REEST_SWITCH)
Unit: None
Actual Value Range:
PCI_CONFUSION_REEST_SWITCH,
S1_HANDOVER_REEST_SWITCH,
NO_CONTEXT_REEST_SWITCH,
SEC_CMD_REEST_SWITCH,
WITH_X2_NO_NCELL_REEST_SWITCH
Default Value:
PCI_CONFUSION_REEST_SWITCH:On,
S1_HANDOVER_REEST_SWITCH:On,
NO_CONTEXT_REEST_SWITCH:Off,
SEC_CMD_REEST_SWITCH:On,
WITH_X2_NO_NCELL_REEST_SWITCH:Off
GlobalP Enhance MOD LBFD-0 RRC Meaning: Indicates the protection threshold of the
rocSwitc dRRCR GLOBA 02007 Connect number of RRC connection reestablishments initiated
h eestProt LPROC ion by the same UE in an eNodeB. UE manufacturers may
ectThd SWITC Manage have different understanding of protocols, and
H ment therefore UE compliance with protocols varies and
LST may be different from eNodeB compliance with the
GLOBA same protocols. Some UEs may initiate the same RRC
LPROC connection reestablishments repeatedly. When this
SWITC parameter is set to a non-zero value, the RRC
H connection reestablishment protection function is
enabled. This function releases a UE when the number
of RRC connection reestablishment procedures
initiated by the UE in an eNodeB exceeds the
threshold. In this case, the RrcReestProtectThd
parameter does not take effect. When this parameter is
set to 0, the RRC connection reestablishment
protection function is disabled. This parameter applies
only to LTE FDD and LTE TDD.
GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: 0
GlobalP RrcRees MOD LBFD-0 Transpo Meaning: Indicates the RRC connection
rocSwitc tProtect GLOBA 02007 rt reestablishment protection threshold. UE
h Thd LPROC TDLBF Resourc manufacturers may have different understanding of
SWITC D-00200 e protocols, and therefore UE compliance with
H 8 Overloa protocols varies and may be different from eNodeB
LST d compliance with the same protocols. After a UE
GLOBA Control initiates an RRC connection reestablishment
LPROC Radio procedure due to a reconfiguration failure and the
SWITC Bearer reestablishment is complete, the subsequent RRC
H Manage connection reconfiguration may fail again. As a result,
ment the UE initiates an RRC connection reestablishment
procedure again. If this repeatedly happens, the UE
repeatedly initiates RRC connection reestablishment.
If this parameter is set to 0, the function of RRC
connection reestablishment protection is not used. If
this parameter is set to a value other than 0, the
eNodeB rejects the RRC connection reestablishment
request due to a reconfiguration failure from a UE
when the number of RRC connection reestablishment
requests initiated by the UE served by the eNodeB due
to reconfiguration failures has exceeded the parameter
value within 1 minute. This parameter applies only to
LTE FDD and LTE TDD.
GUI Value Range: 0~6000
Unit: None
Actual Value Range: 0~6000
Default Value: 0
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
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.
GUI Value Range: 0~3600
Unit: s
Actual Value Range: 0~3600
Default Value: 180
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
QciPara UeInacti ADD LBFD-0 RRC Meaning: Indicates the length of the UE inactivity
vityTim QCIPA 02007 / Connect timer for UEs that have entered DRX mode and have
erDynDr RA TDLBF ion bearers of the QCI when dynamic DRX is enabled. If
xQci MOD D-00200 Manage the eNodeB detects that a UE has neither received nor
QCIPA 7 ment sent data for a period exceeding the value of this
RA LOFD-0 Dynami parameter, the eNodeB releases the RRC connection
0110501 c DRX for this UE. If this parameter is set to a large value, the
LST amount of signaling is reduced but UE power
QCIPA / Enhance
TDLOF consumption increases. You are advised to set this
RA d parameter to a value greater than that of
D-00110 Extende
501 UlSynTimerDynDrx. In power saving mode, you are
d QCI advised to set this parameter significantly different to
LOFD-0 Enhance the value of the UlSynTimerDynDrx parameter, for
81218 d QoS example a gap of 10 seconds, to avoid power
TDLOF for consumption increase due to the increase of signaling.
D-11023 MCPTT If a UE has bearers of several QCIs, the eNodeB
0 (Trial) selects the longest UE Inactivity Timer of bearers with
LOFD-0 Voice the highest QCI-specific priority specified by the
81229 / Characte UeInactiveTimerPri parameter as the UE inactivity
TDLOF ristic timer for the UE. This parameter applies only to LTE
D-08122 Awarene FDD and LTE TDD.
9 ss GUI Value Range: 10~3600
LTROF Scheduli Unit: s
D-11120 ng
Actual Value Range: 10~3600
1/ MCPTT
TDLOF QoS Default Value: 200
D-12110 Manage
3 ment
TDLOF Congesti
D-12110 on
4 Control
LTROF for
D-11120 Public
3/ Safety
TDLOF RRC
D-12110 and
5 DRX
Policy
for
Public
Safety
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)
GUI Value Range: 0~3600
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
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
CellAlg UEInact MOD LOFD-0 Voice Meaning: Indicates whether the UeInactiveTimerQci1
oSwitch iveTime CELLA 81229 / Characte parameter takes effect. If UEInactiveTimerQ-
rQCI1S LGOSW TDLOF ristic CI1Switch is on, UeInactiveTimerQci1 takes effect;
witch ITCH D-08122 Awarene when there are QCI 1 services, the UE inactivity timer
LST 9 ss length is specified by UeInactiveTimerQci1. If
CELLA LBFD-0 Scheduli UEInactiveTimerQCI1Switch is off,
LGOSW 02007 ng UeInactiveTimerQci1 does not take effect and the UE
ITCH RRC inactivity timer length is specified by
Connect UeInactiveTimer. This parameter applies only to LTE
ion FDD and LTE TDD.
Manage GUI Value Range: OFF(Off), ON(On)
ment Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
RrcCon UeInact MOD LBFD-0 RRC Meaning: Indicates the length of the UE Inactivity
nStateTi TimerD RRCCO 02007/ Connect Timer for UEs that have entered DRX mode and have
mer ynDrxQ NNSTA TDLBF ion QCI-1 services when dynamic DRX is enabled. If the
ci1 TETIM D-00200 Manage eNodeB detects that such a UE has neither received
ER 7 ment nor sent data for a period exceeding the value of this
LST LOFD-0 Dynami parameter, the eNodeB releases the RRC connection
RRCCO 0110501 c DRX for the UE. This parameter takes effect only for such
NNSTA UEs that will access the network after the parameter is
TETIM set. If the QciParaEffectFlag parameter in the
ER GlobalProcSwitch MO is set to ON(On), the
UeInactivityTimerDynDrxQci parameter in the
QciPara MO for QCI 1, rather than this parameter
takes effect. This parameter applies only to LTE FDD
and LTE TDD.
GUI Value Range: 10~3600
Unit: s
Actual Value Range: 10~3600
Default Value: 200
RrcCon UeInacti MOD LBFD-0 RRC Meaning: Indicates the length of the UE Inactivity
nStateTi veTimer RRCCO 02007 / Connect Timer for UEs that have QCI-1 services. If the
mer Qci1 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 TDLBF Support for the UE. If this parameter is set to 0, the UE
RRCCO D-08110 of Inactivity Timer is not used. This timer takes effect
NNSTA 1 VoLTE during the setup of QCI-1 bearers. During a handover
TETIM or RRC connection reestablishment to a new cell, the
ER eNodeB determines whether the timer takes effect
based on whether the UE has QCI-1 bearers. If yes,
the timer takes effect; otherwise, the timer defined by
UeInactiveTimer takes effect. If the QciParaEffectFlag
parameter in the GlobalProcSwitch MO is set to
ON(ON), this parameter does not take effect. In this
case, the CiotUeInactiveTimer parameter in the
QciPara MO for QCI 1 takes effect for eMTC UEs,
MTC UEs, and UEs with the RRC connection setup
cause delayToleran, and the UeInactiveTimerForQci
parameter in the QciPara MO for QCI 1 takes effect
for other types of UEs. This parameter applies only to
LTE FDD and LTE TDD.
GUI Value Range: 0~3600
Unit: s
Actual Value Range: 0~3600
Default Value: 20
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.
GUI Value Range: 0~3600
Unit: s
Actual Value Range: 0~3600
Default Value: 20
QciPara UeInacti ADD LBFD-0 RRC Meaning: Indicates the priority of the QCI-specific
veTimer QCIPA 02007 / Connect UE Inactivity Timer. A larger value of this parameter
Pri RA TDLBF ion indicates a higher priority. The eNodeB selects the
MOD D-00200 Manage longest UE Inactivity Timer with the highest QCI-
QCIPA 7 ment specific priority as the UE Inactivity Timer for UEs
RA LOFD-0 Voice running services with the specific QCI. The UE
81229 / Characte Inactivity Timer for QCI 69 is taken as the UE
LST Inactivity Timer for the MCPTT UEs. This parameter
QCIPA TDLOF ristic
D-08122 Awarene applies only to LTE FDD and LTE TDD.
RA
9 ss GUI Value Range: 0~255
Scheduli Unit: None
ng
Actual Value Range: 0~255
Default Value: 0
RrcCon UeInacti MOD LOFD-0 Dynami Meaning: Indicates the length of the UE Inactivity
nStateTi vityTim RRCCO 0110501 c DRX Timer for UEs that have entered DRX mode and have
mer erDynDr NNSTA / High- no QCI-1 services when dynamic DRX is enabled. If
x TETIM TDLOF Mobility the eNodeB detects that such a UE has neither
ER D-00110 - received nor sent data for a period exceeding the value
LST 501 Triggere of this parameter, the eNodeB releases the RRC
RRCCO LOFD-0 d Idle connection for the UE. If this parameter is set to a
NNSTA 0110502 Mode large value, the amount of signaling is reduced but UE
TETIM / power consumption increases. You are advised to set
RRC this parameter to a value greater than that of
ER TDLOF Connect
D-00110 UlSynTimerDynDrx. In power saving mode, you are
ion advised to set this parameter significantly different
502 Manage from the value of the UlSynTimerDynDrx parameter,
LBFD-0 ment for example a difference of 10 seconds, to avoid
02007 power consumption increase due to the increase of
signaling. If the QciParaEffectFlag parameter in the
GlobalProcSwitch MO is set to ON(On), the
UeInactivityTimerDynDrxQci parameter in the
QciPara MO, rather than this parameter takes effect.
This parameter applies only to LTE FDD and LTE
TDD.
GUI Value Range: 10~3600
Unit: s
Actual Value Range: 10~3600
Default Value: 200
GlobalP UeLink MOD LBFD-0 RRC Meaning: Indicates the UE link fault detection switch.
rocSwitc Abnorm GLOBA 02007 / Connect If this switch is turned on, link fault detection is
h alDetect LPROC TDLBF ion enabled for synchronized UEs. If this switch is turned
Switch SWITC D-00200 Manage off, link fault detection is not enabled for
H 7 ment synchronized UEs. This parameter applies only to
LST LTE FDD and LTE TDD.
GLOBA GUI Value Range: OFF(Off), ON(On)
LPROC Unit: None
SWITC
H Actual Value Range: OFF, ON
Default Value: OFF(Off)
ENodeB S1Mess MOD LBFD-0 RRC Meaning: Indicates the timer governing the period that
ConnSta ageWaiti ENODE 02007 / Connect the eNodeB waits for a response message from the
teTimer ngTimer BCONN TDLBF ion MME when the eNodeB performs an S1-based
STATET D-00200 Manage handover for a UE running non-QCI1 services. If the
IMER 7 ment timer expires, the eNodeB initiates a UE context
LST release over the S1 interface. If the eNodeB performs
ENODE an S1-based handover for a UE running services with
BCONN a QCI of 1, the S1MsgWaitingTimerQci1 parameter
STATET controls the period that the eNodeB waits for a
IMER response message from the MME.
GUI Value Range: 1~200
Unit: s
Actual Value Range: 1~200
Default Value: 20
ENodeB S1Msg MOD LBFD-0 RRC Meaning: Indicates the timer governing the period that
ConnSta Waiting ENODE 02007 / Connect the eNodeB waits for a response message from the
teTimer TimerQ BCONN TDLBF ion MME when the UE is running services with the QCI
ci1 STATET D-00200 Manage of 1. If the timer expires, the eNodeB initiates a UE
IMER 7 ment context release over the S1 interface. This parameter
LST TDLBF Support applies only to LTE FDD and LTE TDD.
ENODE D-08110 of GUI Value Range: 1~200
BCONN 1 VoLTE Unit: s
STATET
IMER Actual Value Range: 1~200
Default Value: 20
GlobalP UeRelC MOD LBFD-0 RRC Meaning: Indicates whether to perform the radio link
rocSwitc hkLostS GLOBA 02007 / Connect failure (RLF) detection for a UE when the RRC
h witch LPROC TDLBF ion connection for the UE is released because of UE
SWITC D-00200 Manage inactivity. This parameter applies only to LTE FDD
H 7 ment and LTE TDD.
LST GUI Value Range: OFF(Off), ON(On)
GLOBA Unit: None
LPROC
SWITC Actual Value Range: OFF, ON
H Default Value: OFF(Off)
GlobalP UeRelR MOD LBFD-0 RRC Meaning: Indicates the number of resynchronization
rocSwitc eSynTi GLOBA 02007 / Connect failures after which the UE release timer is started in
h mes LPROC TDLBF ion scenarios where the RRC connection is released for a
SWITC D-00200 Manage UE caused by resynchronization failure. This
H 7 ment parameter applies only to LTE FDD and LTE TDD.
LST GUI Value Range: r1(1), r2(2), r3(3), r4(4), r5(5),
GLOBA Infinity(Infinity)
LPROC Unit: None
SWITC
H Actual Value Range: r1, r2, r3, r4, r5, Infinity
Default Value: Infinity(Infinity)
CellStan TrafficR MOD LBFD-0 Radio Meaning: Indicates the waiting duration for the
dardQci elDelay CELLS 02008 / Bearer eNodeB to release services with a specific QCI after
TANDA TDLBF Manage the eNodeB detects that the radio link is abnormal.
RDQCI D-00200 ment When the eNodeB detects that the radio link is
LST 8 abnormal, the eNodeB waits for the UE to initiate an
CELLS RRC connection reestablishment procedure to restore
TANDA services. If the waiting duration times out, the eNodeB
RDQCI releases the services. This parameter applies only to
LTE FDD and LTE TDD.
GUI Value Range: 0~65000
Unit: ms
Actual Value Range: 0~65000
Default Value: 30000
CellQci TrafficR ADD LBFD-0 Radio Meaning: Indicates the waiting duration for the
Para elDelay CELLQ 02008 / Bearer eNodeB to release services with a specific QCI after
CIPAR TDLBF Manage the eNodeB detects that the radio link is abnormal.
A D-00200 ment When the eNodeB detects that the radio link is
MOD 8 abnormal, the eNodeB waits for the UE to initiate an
CELLQ RRC connection reestablishment procedure to restore
CIPAR services. If the waiting duration times out, the eNodeB
A releases the services. This parameter applies only to
LTE FDD and LTE TDD.
LST
CELLQ GUI Value Range: 0~65000
CIPAR Unit: ms
A Actual Value Range: 0~65000
Default Value: 30000
CellExte TrafficR ADD LBFD-0 Radio Meaning: Indicates the waiting duration for the
ndedQci elDelay CELLE 02008 / Bearer eNodeB to release services with a specific QCI after
XTEND TDLBF Manage the eNodeB detects that the radio link is abnormal.
EDQCI D-00200 ment When the eNodeB detects that the radio link is
MOD 8 abnormal, the eNodeB waits for the UE to initiate an
CELLE RRC connection reestablishment procedure to restore
XTEND services. If the waiting duration times out, the eNodeB
EDQCI releases the services. This parameter applies only to
LTE FDD and LTE TDD.
LST
CELLE GUI Value Range: 0~65000
XTEND Unit: ms
EDQCI Actual Value Range: 0~65000
Default Value: 30000
9 Counters
10 Glossary
11 Reference Documents