RAN
URA/Cell Update Parameter Description
Issue01
Date2009-03-30
Huawei Technologies Co., Ltd. provides customers with
comprehensive technical support and service. For any assistance,
please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address:Huawei Industrial BaseBantian, LonggangShenzhen
518129People's Republic of China
Website:http://www.huawei.com
Email:[email protected]
Copyright Huawei Technologies Co., Ltd. 2009. 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.
NoticeThe 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 the warranty of any kind, express or implied.
Huawei Proprietary and Confidential Copyright Huawei
Technologies Co., Ltd
About This DocumentAuthorPrepared byGao
LonglongDate2008-10-21
Edited bySun JingshuDate2008-10-30
Reviewed byDate
Translated byXie WensiDate2008-11-30
Tested byGao WeiqiDate2009-01-10
Approved byDuan ZhongyiDate2009-03-30
RANURA/Cell Update Parameter DescriptionAbout This Document
Issue 01 (2009-03-30)Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltdiii
Contents1 Change History1-22 Introduction2-23 URA/Cell Update
Principles3-23.1 Basic Types of URA/Cell Update3-23.1.1 Periodical
URA/Cell Update3-23.1.2 URA/Cell Update due to Cell
Reselection3-23.1.3 Cell Update due to Paging Response3-23.1.4 Cell
Update due to Uplink Data Transmission3-23.1.5 Cell Update due to
Radio Link Failure3-23.1.6 Cell Update due to Re-entering Service
Area3-23.1.7 Cell Update due to RLC Unrecoverable Error3-23.1.8
Cell Update due to MBMS PtP RB Request3-23.1.9 Cell Update due to
MBMS Reception3-23.2 Signaling Procedure of URA/Cell Update3-23.2.1
Signaling Procedure of URA Update3-23.2.2 Signaling Procedure of
Cell Update3-24 URA/Cell Update Parameters4-24.1 Description4-24.2
Values and Ranges4-25 Reference Documents5-2
RANURA/Cell Update Parameter DescriptionContents
Issue 01 (2009-03-30)Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltdv
Change HistoryThe change history provides information on the
changes in different document versions.Document and Product
VersionsDocument and Product VersionsDocument VersionRAN
Version
01 (2009-03-30)11.0
Draft (2009-03-10)11.0
Draft (2009-01-15)11.0
This document is based on the BSC6810 and 3900 series NodeBs.The
available time of each feature is subject to the RAN product
roadmap.There are two types of changes, which are defined as
follows:Feature change: refers to the change in the URA/cell
update.Editorial change: refers to the change in the information
that was inappropriately described or the addition of the
information that was not described in the earlier version.01
(2009-03-30)This is the document for the first commercial release
of RAN11.0.Compared with draft (2009-03-10), this issue optimizes
the description.Draft (2009-03-10)This is the second draft of the
document for RAN11.0. Compared with draft (2009-01-15), draft
(2009-03-10) optimizes the description.Draft (2009-01-15)This is
the initial draft of the document for RAN11.0.Compared with issue
02 (2008-07-30) of RAN10.0, draft (2009-01-15) incorporates the
following changes:Change TypeFeature DescriptionParameter
Change
Feature changeNone.None.
Editorial changeThe title of the document is changed from
URA/Cell Update Description to URA/Cell Update Parameter
Description.Parameter names are replaced with parameter
IDs.None.
Error! Use the Home tab to apply 1 to the text that you want to
appear here.Error! Use the Home tab to apply 1 to the text that you
want to appear here.RANURA/Cell Update Parameter Description
RANURA/Cell Update Parameter DescriptionError! Use the Home tab
to apply 1 to the text that you want to appear here.Error! Use the
Home tab to apply 1 to the text that you want to appear here.
2-2Huawei Proprietary and Confidential Copyright Huawei
Technologies Co., LtdIssue 01 (2009-03-30)
Issue 01 (2009-03-30)Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd2-2
IntroductionThe URA is the UTRAN registration area. A URA
consists of multiple cells. URA update happens only in the URA_PCH
state. The purpose of making a UE switching to the URA_PCH state is
to prevent a UE that has no data to transmit (especially those
moving at a high speed) from frequently initiating cell
reselection. The functions and basic processes of cell update and
URA update are similar. The only difference lies in the range of
triggering the update. URA/cell update is used by the UE to report
the location information and status of the UE. The reporting method
is classified into two types: periodical URA/cell update and
cell-reselection-triggered update. URA update occurs when the UE is
in URA_PCH state, and cell update occurs when the UE is in CELL_PCH
or CELL_FACH state.Additionally, cell update is also used to
perform some other functions, such as UE state transition and radio
link re-establishment on the DCH. As a result, cell update may
happen when the UE is in CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH
state.URA/cell update enables the UTRAN to manage the UE behaviors.
It can be applied to mobility management, cell reselection, and
paging procedures. URA/cell update has the following functions:The
URA update:Enables the UTRAN to periodically monitor the status of
the UE in URA_PCH state.Enables the UTRAN to know in time the URA
where the UE is camping if URA changes after cell
reselection.Enables the UE to retrieve a new URA identity after
reselecting a cell that does not belong to the currently assigned
URA.The cell update:Enables the UTRAN to periodically monitor the
status of the UE in CELL_FACH or CELL_PCH state.Enables the UTRAN
to know the cell where the UE is camping after the UE in CELL_PCH,
URA_PCH or CELL_FACH state re-enters the service area.Enables the
UTRAN to know in time the new cell of UE after cell
reselection.Enables the UE to transit from CELL_PCH or URA_PCH
state to CELL_FACH state when the network is paging the UE.Enables
the UE to require the uplink data transmission to transit from
CELL_PCH or URA_PCH state to CELL_FACH state.Enables the UE that is
out of synchronization on the dedicated radio link channel to
re-establish a new dedicated channel.Enables the RNC to release the
RRC connection of the UE or to re-establish an RLC entity in case
of RLC unrecoverable error.Enables the UTRAN to count the number of
UEs that are in URA_PCH, CELL_PCH, and CELL_FACH states and are
interested in receiving an MBMS transmission.Notifies the UTRAN of
the UEs that are interested in receiving an MBMS service when the
UE is triggered in URA_PCH, CELL_PCH or CELL_FACH state.Enables the
UEs to request the MBMS PtP RB setup when the UEs are in CELL_PCH,
URA_PCH, or CELL_FACH state.Intended AudienceThis document is
intended for:System operators who need a general understanding of
URA/cell update.Personnel working on Huawei products or
systems.ImpactImpact on system performanceFrequent cell update may
increase the signaling load of a network and consume more power
supply from the battery of a UE.Impact on other
featuresNone.Network Elements InvolvedTable 2-1 lists the Network
Elements (NEs) involved in URA/cell update.NEs involved in URA/cell
updateUENodeBRNCMSC ServerMGWSGSNGGSNHLR
NOTE: : not involved: involvedUE = User Equipment, RNC = Radio
Network Controller, MSC Server = Mobile Service Switching Center
Server, MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN
= Gateway GPRS Support Node, HLR = Home Location Register
RANURA/Cell Update Parameter DescriptionError! Use the Home tab
to apply 1 to the text that you want to appear here.Error! Use the
Home tab to apply 1 to the text that you want to appear here.
URA/Cell Update PrinciplesBasic Types of URA/Cell UpdateThis
section describes the basic types of URA/cell update, including the
periodical URA/cell update and the cell-reselection-triggered
update. Besides, cell update also has several other
types.Periodical URA/Cell UpdateOnce the UE enters the CELL_FACH,
CELL_PCH or URA_PCH state, it starts the timer T305. If the timer
T305 expires, the UE performs URA/cell update with the cause
"periodical URA/Cell update". The value of T305 is set through the
parameter Timer 305 on the RNC side. The UE obtains the value of
T305 from SIB1 and the message UTRAN MOBILITY INFO
CONF.Accordingly, the RNC starts an internal timer for the UE in
CELL_FACH, CELL_PCH or URA_PCH state. The value of this timer is
greater than that of T305. When the RNC receives a URA/CELL UPDATE
message with the cause "periodical URA/cell update", it restarts
the internal timer. If the RNC does not receive a URA/CELL UPDATE
message before expiry of the internal timer, the RNC decides that
the UE is out of service, and then initiates the RRC connection
release procedure.
Internal timer length = T305 + T302 x N302 + T307 +
usIubRTDelayusIubRTDelay is the real path transfer delay on the Iub
interface. The value is variable and automatically detected.The
parameters involved are T305, T302, T307 and N302.URA/Cell Update
due to Cell ReselectionIf a UE in CELL_FACH or CELL_PCH state
reselects a new cell, the UE performs cell update with the cause
"cell reselection". If a UE in URA_PCH state reselects a new cell
of a different URA, the UE performs URA update with the cause
"change of URA". Upon reception of a URA/CELL UPDATE message with
the cause "Change of URA/Cell reselection", the RNC updates the
URA/cell where the UE camps.The URA ID can be assigned to a cell
through the parameter URA ID. The URA ID should be created through
the MML command ADD URA before being assigned to a cell.The main
parameters involved in the cell reselection algorithm when the UE
is in CELL_FACH, CELL_PCH, or URA_PCH state are listed as
follows:Hysteresis 1 for connect mode: ConnQhyst1sHysteresis 2 for
connect mode: ConnQhyst2sCell Sel-reselection quality measure:
QualMeasMin quality level: QqualminIf you want to set cell
reselection parameters for each UE state (URA_PCH, CELL_PCH,
CELL_FACH) respectively, you can use the MML command ADD
CELLSELRESEL to set them.Hysteresis 1 for UE in CELL_PCH or URA_PCH
state: Qhyst1spchHysteresis 1 for UE in CELL_FACH state:
Qhyst1sfachHysteresis 2 for UE in CELL_PCH or URA_PCH state:
Qhyst2spchHysteresis 2 for UE in CELL_FACH state:
Qhyst2sfachReselection delay time for UE in PCH state:
TreselectionspchReselection delay time for UE in CELL_FACH state:
TreselectionsfachFor details about the cell reselection procedure,
see Cell Reselection in the UE Behaviors in Idle Mode Parameter
Description.On some occasions, the UE in Cell_PCH state performs
cell reselection frequently and initiates the cell update procedure
frequently. When the RNC detects this status of the UE, it enables
the UE to transfer to the URA_PCH state through the message "CELL
UPDATE CONFIRM".If the number of cell update procedures initiated
by the UE within an evaluation period exceeds the threshold of cell
reselection, the RNC judges that the UE is in frequent cell
reselection state.Cell Update due to Paging ResponseIf the UE in
URA_PCH or CELL_PCH state receives a PAGING TYPE 1 message, it
performs cell update with the cause "paging response". Upon
reception of a CELL UPDATE message with this cause, the RNC sends a
CELL UPDATE CONFIRM message to the UE and switches the UE to the
CELL_FACH state.Cell Update due to Uplink Data TransmissionIf the
UE in URA_PCH or CELL_PCH state has uplink data to be transmitted,
it performs cell update with the cause "uplink data transmission".
Upon reception of a CELL UPDATE message with this cause, the RNC
sends a CELL UPDATE CONFIRM message to the UE and switches the UE
to the CELL_FACH state.Cell Update due to Radio Link FailureIf the
UE in CELL_DCH state detects that the criteria for radio link
downlink failure are met, the UE performs cell update with the
cause "radio link failure". Upon reception of a CELL UPDATE message
with this cause, the RNC deletes the current radio link,
re-establishes a new radio link, and sends a CELL UPDATE CONFIRM
message to the UE with the parameters of the new radio link to the
cell that receives the CELL UPDATE message. Then, the UE
re-establishes the RRC connection on the new radio link.The
criteria for radio link failure involve some timers and constants.
A timer (T313) is started after the UE detects a certain number
(N313) of consecutive "out of sync" indications from layer 1 (L1).
If there is no enough number (N315) of consecutive "in sync"
indications received from L1 before the timer (T313) expires, the
UE considers radio link failure. Related parameters are as
follows:Timer 313: T313Constant 313: N313Constant 315: N315Cell
Update due to Re-entering Service AreaWhen the UE is in CELL_FACH,
CELL_PCH, or URA_PCH state is out of service area and re-enters the
service area before T307 or T317 expires, the UE performs cell
update with the cause "re-entering service area". Upon reception of
a CELL UPDATE message with this cause, the RNC updates the cell
where the UE camps.T305 is started as soon as the UE enters the
CELL_FACH, CELL_PCH, or URA_PCH state. T307 is started when T305
expires and the UE detects "out of service area". The length of
T307 is determined by the parameter Timer 307.T316 is started after
the UE in URA_PCH or CELL_PCH state detects "out of service area".
T317 is started when T316 expires or the UE that enters the
CELL_FACH state detects "out of service area". T317 never expires
and so this parameter need not be set. The length of T316 is
determined by the parameter Timer 316.Cell Update due to RLC
Unrecoverable ErrorIf the UE detects an RLC unrecoverable error in
an AM RLC entity, the UE performs cell update with the cause "RLC
unrecoverable error".If the CELL UPDATE message indicates that this
error occurred on RB2, RB3, or RB4 in the UE, the RNC releases the
RRC connection of the UE.If the CELL UPDATE message indicates that
this error occurred on RBn (n>4) in the UE, the RNC
re-establishes an RLC entity for the corresponding RBn.Cell Update
due to MBMS PtP RB RequestIf the UE is in Cell_FACH, Cell_PCH or
URA_PCH state and the UE shall perform cell update for MBMS ptp
radio bearer request, the UE performs cell update with the cause
"MBMS ptp RB request".Cell Update due to MBMS ReceptionIf the UE is
in Cell_FACH, Cell_PCH, or URA_PCH state and shall perform cell
update for MBMS counting, the UE performs cell update with the
cause "MBMS reception".Signaling Procedure of URA/Cell UpdateThe
signaling procedures of URA update and cell update are
similar.Signaling Procedure of URA UpdateBasic Signaling Procedure
of URA UpdateFigure 3-1 shows the basic signaling procedure of URA
update.Basic signaling procedure of URA update
The basic signaling procedure is as follows:0. The UE sends the
RNC a URA UPDATE message with either of the following update causes
in the "URA update cause" information element (IE): "periodical URA
update" or "change of URA"The RNC responds to the "URA update
cause" IE and then sends a URA UPDATE CONFIRM message to the
UE.----EndSignaling Procedure of URA Update with SRNS
RelocationFigure 3-2 shows the signaling procedure of the inter-RNS
URA update with SRNS relocation from RNC 1 to RNC 2.Signaling
procedure of URA update with SRNS relocation
The UE in URA_PCH state establishes an RAB on RNC 1. In this
procedure, RNC 1 is the Serving RNC (SRNC) and RNC 2 is the Drift
RNC (DRNC).The signaling procedure is as follows:0. The UE in
URA_PCH state sends RNC 2 a URA UPDATE message after URA
reselection.The RNC 2 receives the URA UPDATE message from CCCH.
Then, RNC 2 sends RNC 1 an UPLINK SIGNALLING TRANSFER INDICATION
message, which includes target RNC-ID, allocated C-RNTI, and
D-RNTI.RNC 1 sends the CN a RELOCATION REQUIRED message, requesting
SRNS relocation.The CN sends a RELOCATION REQUEST message to RNC
2.RNC 2 prepares L2 resources for RNC 1 relocation and then sends a
RELOCATION REQUEST ACKNOWLEDGE message to the CN.The CN sends RNC 1
a RELOCATION COMMAND message, notifying RNC 1 that SRNS relocation
starts.RNC 1 completes related preparations such as stopping
signaling and traffic RLCs. Then, RNC 1 sends a RELOCATION COMMIT
message to RNC 2.RNC 2 sends the CN a RELOCATION DETECT message,
notifying the CN that the relocation starts. Then, RNC 2 performs
related operations such as L2 configuration.RNC 2 sends the UE a
URA UPDATE CONFIRM message in the new cell. The message includes
the old S-RNTI and SRNC ID as well as the new S-RNTI, and
C-RNTI.The UE sends a RRC message UTRAN MOBILITY INFORMATION
CONFIRM to RNC 2.RNC 2 sends a RELOCATION COMPLETE message to the
CN.RNC 2 sends the UE a UE CAPABILITY ENQUIRY message, querying the
capability information about the UE.The UE sends RNC 2 a UE
CAPABILITY INFORMATION message, including the capability
information about the UE.RNC 2 receives the UE CAPABILITY
INFORMATION message and sends a UE CAPABILITY INFORMATION CONFIRM
message to the UE.RNC 2 sends the UE a UTRAN MOBILITY INFORMATION
message, notifying the UE of the new UTRAN information.The UE sends
a UTRAN MOBILITY INFORMATION CONFIRM message to RNC 2.The CN sends
RNC 1 an IU RELEASE COMMAND message, requesting RNC 1 to release
the Iu interface resource related to this UE.RNC 1 sends an IU
RELEASE COMPLETE message to the CN.----EndSignaling Procedure of
Cell UpdateBasic Signaling Procedure of Cell UpdateFigure 3-3 shows
the basic signaling procedure of cell update.Basic signaling
procedure of cell update
The basic signaling procedure is described as follows:0. The UE
sends the RNC a CELL UPDATE message with a cause in the "cell
update cause" IE.The RNC performs the corresponding processing, and
then sends the UE a CELL UPDATE CONFIRM message.According to
related IEs in the received message, the UE may respond with
messages or not. If the UE responds, the messages can be one of the
following messages:UTRAN MOBILITY INFORMATION CONFIRMPHYSICAL
CHANNEL RECONFIGURATION COMPLETETRANSPORT CHANNEL RECONFIGURATION
COMPLETERADIO BEARER RECONFIGURATION COMPLETERADIO BEARER RELEASE
COMPLETE----EndIf the UE changes from CELL_PCH state to URA_PCH
state through cell update, the procedure is as follows:0. The UE is
in CELL_PCH state and sends a CELL UPDATE message with the cause
"cell reselection".If the RNC decides to switch the state of this
UE from CELL_PCH to URA_PCH, the RNC sends the CELL UPDATE CONFIRM
message to the UE and sets the "RRC State Indicator" IE as URA_PCH.
The UE enters the URA_PCH state upon reception of the CELL UPDATE
CONFIRM message.----EndSignaling Procedure of Cell Update with SRNS
RelocationFigure 3-4 shows the signaling procedure of the inter-RNS
cell update with SRNS relocation from RNC 1 to RNC 2.Signaling
procedure of cell update with SRNS relocation
The UE sets up an RRC connection on RNC 1. The UE is in
CELL_FACH or CELL_PCH state. In this case, RNC 1 is the serving RNC
(SRNC) and RNC 2 is the drift RNC (DRNC).The signaling procedure is
described as follows:0. The UE reselects a cell under RNC 2 and
sends RNC 2 a CELL UPDATE message.RNC 2 allocates a C-RNTI and a
D-RNTI for the UE. RNC 2 forwards the CELL UPDATE message received
from the CCCH to RNC 1 through an UPLINK SIGNALLING TRANSFER
INDICATION message.RNC 1 sends the CN a RELOCATION REQUIRED
message, requesting SRNS relocation.The CN sends a RELOCATION
REQUEST message to RNC 2.RNC 2 prepares L2 resources for RNC 1
relocation, and then sends the CN a RELOCATION REQUEST ACKNOWLEDGE
message.The CN sends RNC 1 a RELOCATION COMMAND message, notifying
RNC 1 that SRNS relocation starts.RNC 1 completes related
preparations such as stopping signaling and traffic RLCs, and then
sends RNC 2 a RELOCATION COMMIT message, requesting RNC 2 to start
the relocation.RNC 2 sends the CN a RELOCATION DETECT message,
notifying the CN that the relocation starts. Then, RNC 2 performs
related operations such as L2 configuration.RNC 2 sends the UE a
CELL UPDATE CONFIRM message in the new cell, including the new
C-RNTI and D-RNTI.The UE sends RNC 2 a RRC message PHYSICAL CHANNEL
RECONFIGURATION COMPLETE, confirming that the relocation
succeeds.RNC 2 sends a RELOCATION COMPLETE message to the CN.RNC 2
sends the UE a UE CAPABILITY ENQUIRY message, querying the
capability information about the UE.The UE sends RNC 2 a UE
CAPABILITY INFORMATION message, including the capability
information about the UE.RNC 2 receives the UE CAPABILITY
INFORMATION message and sends a UE CAPABILITY INFORMA CONFIRM
message to the UE.RNC 2 sends the UE a UTRAN MOBILITY INFORMATION
message, notifying the UE of the new UTRAN information.The UE sends
a UTRAN MOBILITY INFORMATION CONFIRM message to RNC 2.The CN sends
RNC 1 an IU RELEASE COMMAND message, requesting RNC 1 to release
the Iu interface resource related to this UE.RNC 1 sends the CN an
IU RELEASE COMPLETE message.----EndSignaling Procedure of Cell
Update due to Radio Link FailureFigure 3-5 shows the signaling
procedure of cell update due to radio link failure.Signaling
procedure of cell update due to radio link failure
When receiving a cell update message, the RNC establishes a new
RL and deletes the old RL. The new RL is specified in the cell
update message.If the first attempt to re-establish the RL fails,
the RRC connection will be released.This procedure is supported for
both CS and PS RAB.For PS RAB, this procedure is supported for both
DCH and HSDPA bearer.More detailed description of this procedure is
as follows:0. The UE initiates the re-establishment of the RRC
connection in the new cell by sending a CELL UPDATE message on the
CCCH.The RNC allocates radio resources in the new cell and sends an
NBAP message RADIO LINK SETUP REQUEST to the new NodeB.The NodeB
allocates resources and responds with an NBAP message RADIO LINK
SETUP RESPONSE.The RNC initiates the setup of Iub data transport
bearer by using the ALCAP protocol.The RNC initiates the release of
Iub data transport bearer by using the ALCAP protocol and also the
release of Iub radio resource by performing the NBAP RADIO LINK
DELECTION procedure.The RNC prepares a CELL UPDATE CONFIRM message
and sends it to the UE on the DCCH.The UE re-establishes radio
connection in the new cell and sends the PHYSICAL CHANNEL
RECONFIGURATION COMPLETE, RADIO REARER RECONFIGURATION COMPLETE,
RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION
COMPLETE message to the RNC.----End
Error! Use the Home tab to apply 1 to the text that you want to
appear here.Error! Use the Home tab to apply 1 to the text that you
want to appear here.RANURA/Cell Update Parameter Description
RANURA/Cell Update Parameter DescriptionError! Use the Home tab
to apply 1 to the text that you want to appear here.Error! Use the
Home tab to apply 1 to the text that you want to appear here.
4-4Huawei Proprietary and Confidential Copyright Huawei
Technologies Co., LtdIssue 01 (2009-03-30)
Issue 01 (2009-03-30)Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd5-1
URA/Cell Update Parameters0. DescriptionURA/cell update
parameter descriptionParameter IDDescription
URAIdID of the URA in a cell. The URA is only used by the UTRAN
and the CN does not know the URA. The URA consists of multiple
cells. When the UE enters the URA-PCH state, the location of the UE
is identified with the URA ID. For details, refer to the 3GPP TS
25.331 protocol.
T313T313 is started after the UE detects consecutive N313 "out
of sync" indications from L1. T313 is stopped after the UE detects
consecutive N315 "in sync" indications from L1. It indicates Radio
Link (RL) failure upon expiry. Protocol default value is 3.
N313Maximum number of successive "out of sync" indications
received from L1. Protocol default value is 20.
N315Maximum number of successive "in sync" indications received
from L1 when T313 is activated. Protocol default value is 1.
CellReSelectCounterIf the times the UE in the CELL_PCH state
performs cell reselection is greater than or equal to the
threshold, it is regarded that the cell reselection is frequent.
When the timer expires, the target state is set to URA_PCH. In the
next cell update procedure, the UE is informed of state transition
to URA_PCH in the CELL_UPDATE_CONFIRM message.
T305T305 is started after the UE receives CELL UPDATE
CONFIRM/URA UPDATE CONFIRM in CELL_FACH, URA_PCH or CELL_PCH state.
It is stopped after the UE enters another state. CELL UPDATE will
be transmitted upon the expiry of this timer if T307 is not
activated and the UE detects "in service area"; otherwise, T307
will be started. Protocol default value is 30. "Infinity" means the
cell will not be updated.
T302T302 is started after the UE transmits the CELL UPDATE/URA
UPDATE message and stopped after the UE receives the CELL UPDATE
CONFIRM/URA UPDATE CONFIRM message. CELL UPDATE/URA UPDATE will be
resent upon the expiry of the timer if V302 less than or equal to
N302; otherwise, the UE will enter idle mode. Protocol default
value is 4000.
N302Maximum number of retransmissions of CELL UPDATE/URA
UPDATE.Protocol default value is 3.
T307T307 is started after T305 has expired and the UE detects
"out of service area". It is stopped after the UE detects "in
service area". The UE will enter idle mode upon expiry. Protocol
default value is 30.
T316T316 is started after the UE detects "out of service area"
in URA_PCH or CELL_PCH state.T316 is stopped after the UE detects
"in service area". The cell update procedure will be initiated upon
the expiry of the timer if "in service area" is detected;
otherwise, T317 will be started. The UE will enter CELL_FACH state
and initiate cell update procedure when the UE detects "in service
area". Protocol default value is 30.
ConnQhyst1sThe hysteresis value of the serving FDD cells in
connected mode in case the quality measurement for cell selection
and reselection is set to CPICH RSCP. It is related to the slow
fading feature of the area where the cell is located. The greater
the slow fading variance is, the greater this parameter. According
to the R regulation, the current serving cell involves in cell
selection after the measurement value is added with the hysteresis
value. The measurement hysteresis aims to prevent the ping-pong
effect of the cell reselection, which is caused by the slow fading
when the UE is on the edge of the cell. The ping-pong effect may
trigger frequent location updates (idle mode), URA updates
(URA_PCH), or cell updates (CELL_FACH, CELL_PCH), and thus increase
the load of network signaling and the consumption of UE batteries.
Set a proper measurement hysteresis to reduce as much as possible
effect of the slow fading as well as ensuring timely cell updates
of the UE. According to the CPICH RSCP emulation report of
inter-frequency hard handovers, the measurement hysteresis ranges 4
dBm to 5 dBm and is set to 4 dBm by default when the slow fading
variance is 8 dB and the relative distance is 20 m. In the cells
where the slow fading variance is low and the average moving speed
of UEs is high, for example the suburbs and countryside, reduce the
measurement hysteresis to guarantee timely location updates of UEs.
The higher the measurement hysteresis is, the less likely it is for
various types of cell reselections to occur, and the better the
slow fading resistance capability is, but the slower the system
reacts to the environment changes. For detailed information of this
parameter, refer to 3GPP TS 25.304.
ConnQhyst2sThe hysteresis value of the serving FDD cells in
connected mode in case the quality measurement for cell selection
and reselection is set to CPICH Ec/No. It is related to the slow
fading feature of the area where the cell is located. The greater
the slow fading variance is, the greater this parameter. This
parameter is not configured when its value is 255. According to the
R regulation, the current serving cell involves in cell selection
after the measurement value is added with the hysteresis value. The
measurement hysteresis aims to prevent the ping-pong effect of the
cell reselection, which is caused by the slow fading when the UE is
on the edge of the cell. The ping-pong effect may trigger frequent
location updates (idle mode), URA updates (URA_PCH), or cell
updates (CELL_FACH, CELL_PCH), and thus increase the load of
network signaling and the consumption of UE batteries. Set a proper
measurement hysteresis to reduce as much as possible effect of the
slow fading as well as ensuring timely cell updates of the UE.
According to the CPICH RSCP emulation report of inter-frequency
hard handovers, the measurement hysteresis ranges 4 dBm to 5 dBm
and is set to 4 dBm by default when the slow fading variance is 8
dB and the relative distance is 20 m. In the cells where the slow
fading variance is low and the average moving speed of UEs is high,
for example the suburbs and countryside, reduce the measurement
hysteresis to guarantee timely location updates of UEs. The higher
the measurement hysteresis is, the less likely it is for various
types of cell reselections to occur, and the better the slow fading
resistance capability is, but the slower the system reacts to the
environment changes. For detailed information of this parameter,
refer to 3GPP TS 25.304.
QualMeasMeasurement quantity of cell selection and reselection.
It can be set to CPICH Ec/N0 or CPICH RSCP. For detailed
information of this parameter, refer to 3GPP TS 25.304.
QqualminThe minimum required quality threshold corresponding to
CPICH Ec/No. The UE can camp on the cell only when the measured
CPICH Ec/No is greater than the value of this parameter. The higher
the parameter value is, the more difficult it is for the UE to
reside in the cell. The lower parameter value is, the easier it is
for the UE to reside in the cell, but it is possible that the UE
cannot receive the system messages that are sent through the
PCCPCH. For detailed information, refer to the 3GPP TS 25.304.
Qhyst1spchThis parameter indicates that in the CELL_PCH or
URA_PCH connection mode, the measurement hysteresis of the UE is 1.
It is used when CPICH RSCP is used in cell selection and
reselection measurement. This parameter is not configured when the
value is 255.Otherwise, the greater the parameter value is, the
harder the cell selection happens. For detailed inforamtion, refer
to 3GPP TS 25.304.
Qhyst1sfachThis parameter indicates that in the CELL_FACH
connection mode, the measurement hysteresis of the UE is 1. It is
used when CPICH RSCP is used in cell selection and reselection
measurement. This parameter is not configured when the value is
255.Otherwise, the greater the parameter value is, the harder the
cell selection happens. For detailed inforamtion, refer to 3GPP TS
25.304.
Qhyst2spchThis parameter indicates that in the CELL_PCH or
URA_PCH connection mode, the measurement hysteresis of the UE is 2.
It is used when CPICH Ec/No is used in cell selection and
reselection measurement. This parameter is not configured when the
value is 255.Otherwise, the greater the parameter value is, the
harder the cell selection happens. For detailed information, refer
to 3GPP TS 25.304.
Qhyst2sfachThis parameter indicates that in the CELL_FACH
connection mode, the measurement hysteresis of the UE is 2. It is
used when CPICH Ec/No is used in cell selection and reselection
measurement. This parameter is not configured when the value is
255.Otherwise, the greater the parameter value is, the harder the
cell selection happens. For detailed information, refer to 3GPP TS
25.304.
TreselectionspchThis parameter indicates the UE reselection
delay in the CELL_PCH or URA_PCH connection mode. This parameter is
not configured when the value is 255. Instead, the Treselections
parameter is used. For detailed information, refer to 3GPP TS
25.304.
Values and RangesURA/cell update parameter values and parameter
rangesParameter IDDefault ValueGUI Value RangeActual Value
RangeUnitMML CommandNE
URAId-0~655350~65535NoneADD URA(Mandatory)ADD
CELLURA(Mandatory)ADD NRNCURA(Mandatory)RNC
T313-0~151~15sSET CONNMODETIMER(Optional)RNC
N313-D1, D2, D4, D10, D20, D50, D100, D200D1, D2, D4, D10, D20,
D50, D100, D200NoneSET CONNMODETIMER(Optional)RNC
N315-D1, D2, D4, D10, D20, D50, D100, D200, D400, D600, D800,
D1000D1, D2, D4, D10, D20, D50, D100, D200, D400, D600, D800,
D1000NoneSET CONNMODETIMER(Optional)RNC
CellReSelectCounter-1~655351~65535NoneSET
UESTATETRANS(Optional)RNC
T305-INFINITY, D5, D10, D30, D60, D120, D360, D720INFINITY, D5,
D10, D30, D60, D120, D360, D720minSET
CONNMODETIMER(Optional)RNC
T302-D100, D200, D400, D600, D800, D1000, D1200, D1400, D1600,
D1800, D2000, D3000, D4000, D6000, D8000D100, D200, D400, D600,
D800, D1000, D1200, D1400, D1600, D1800, D2000, D3000, D4000,
D6000, D8000msSET CONNMODETIMER(Optional)RNC
N302-0~70~7NoneSET CONNMODETIMER(Optional)RNC
T307-D5, D10, D15, D20, D30, D40, D50D5, D10, D15, D20, D30,
D40, D50sSET CONNMODETIMER(Optional)RNC
T316-D0, D10, D20, D30, D40, D50, INFINITYD0, D10, D20, D30,
D40, D50, INFINITYsSET CONNMODETIMER(Optional)RNC
ConnQhyst1s20~200~40, step:2dBADD CELLSELRESEL(Optional)RNC
ConnQhyst2s-0~20,255{0~40},{255}, step:2dBADD
CELLSELRESEL(Optional)RNC
QualMeasCPICH_ECNOCPICH_ECNO(CPICH Ec/N0), CPICH_RSCP(CPICH
RSCP)CPICH_ECNO, CPICH_RSCPNoneADD CELLSELRESEL(Optional)RNC
Qqualmin-18(ADD CELLSELRESEL)-(ADD NRNCCELL)-24~0-24~0dBADD
CELLSELRESEL(Optional) ADD NRNCCELL(Mandatory)RNC
Qhyst1spch2550~40,255{0~40},{255}dBADD
CELLSELRESEL(Optional)RNC
Qhyst1sfach2550~40,255{0~40},{255}dBADD
CELLSELRESEL(Optional)RNC
Qhyst2spch2550~40,255{0~40},{255}dBADD
CELLSELRESEL(Optional)RNC
Qhyst2sfach2550~40,255{0~40},{255}dBADD
CELLSELRESEL(Optional)RNC
Treselectionspch2550~31,255{0~31},{255}sADD
CELLSELRESEL(Optional)RNC
Treselectionsfach2550~31,255{0~6.2},{255}, step:0.2sADD
CELLSELRESEL(Optional)RNC
The Default Value column is valid for only the optional
parameters.The "-" symbol indicates no default value.
Reference DocumentsThe following lists the reference documents
related to the feature:3GPP TS 25.331 "Radio Resource Control
(RRC); protocol specification"3GPP TS 25.931 "UTRAN Functions,
Examples on Signaling Procedures"3GPP TS 25.413 "UTRAN Iu interface
RANAP signaling"Basic Feature Description of Huawei UMTS RAN11.0
V1.5Optional Feature Description of Huawei UMTS RAN11.0 V1.5
