SRNS Relocation Parameter Description PDF

RAN
SRNS Relocation
Parameter Description
Issue 02
Date 2009-06-30
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd
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.
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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Huawei Proprietary and Confidential

RAN
SRNS Relocation Contents
Contents
1 Introduction to This Document...............................................................................................1-1

1.1 Scope.............................................................................................................................................................1-1
1.2 Intended Audience.........................................................................................................................................1-1
1.3 Change History..............................................................................................................................................1-1
2 Overview of SRNS Relocation ................................................................................................2-1

2.1 Basic Types of SRNS Relocation ..................................................................................................................2-1
2.1.1 Static Relocation ..................................................................................................................................2-1
2.1.2 SRNS Relocation due to Hard Handover.............................................................................................2-2
2.1.3 SRNS Relocation due to Cell or URA Update.....................................................................................2-2
2.2 DSCR ............................................................................................................................................................2-3
3 SRNS Relocation Algorithms ..................................................................................................3-1

3.1 SRNS Relocation Algorithms........................................................................................................................3-1
3.1.1 Algorithm of Static Relocation.............................................................................................................3-2
3.1.2 Algorithm of Relocation due to Hard Handover ..................................................................................3-3
3.1.3 Algorithm of Relocation due to Cell or URA Update ..........................................................................3-3
3.2 Signaling Procedure of SRNS Relocation.....................................................................................................3-3
3.2.1 Signaling Procedure of Static Relocation.............................................................................................3-3
3.2.2 Signaling Procedure of Relocation due to Hard Handover ..................................................................3-5
3.2.3 Signaling Procedure of SRNS Relocation due to Cell or URA Update ...............................................3-7
4 DSCR Initiation and Signaling Procedure............................................................................4-1

4.1 DSCR Initiation.............................................................................................................................................4-1
4.1.1 DSCR Initiation due to Cell Update of Radio Link Failure .................................................................4-1
4.1.2 DSCR Initiation due to Cell Update of Non-Iur Interface ...................................................................4-1
4.1.3 DSCR Initiation due to Cell Update of Non-HSPA-Supportive Iur Interface......................................4-1
4.2 Signaling Procedure of DSCR.......................................................................................................................4-2
5 Parameters ...................................................................................................................................5-1
6 Counters .......................................................................................................................................6-1
7 Glossary .......................................................................................................................................7-1
8 Reference Documents ...............................................................................................................8-1
Issue 02 (2009-06-30) Huawei Proprietary and Confidential iii

RAN
SRNS Relocation 1 Introduction to This Document
1 Introduction to This Document
1.1 Scope
This document describes the basic types of SRNS Relocation, the algorithms and signaling
procedure of SRNS Relocation and DSCR initiation and signaling procedure.
1.2 Intended Audience

It is assumed that users of this document are familiar with WCDMA basics and have a
working knowledge of 3G telecommunication.
This document is intended for:
z Personnel working on Huawei WCDMA products or systems
z System operators who need a general understanding of the SRNS Relocation feature
1.3 Change History

This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
z Feature change: refers to the change in the SRNS Relocation feature.
z Editorial change: refers to the change in wording or the addition of the information that
was not described in the earlier version.
Document Issues
The document issues are as follows:
z 02 (2009-06-30)
z 01 (2009-03-30)
z Draft (2009-03-10)
z Draft (2009-01-15)
Issue 02 (2009-06-30) Huawei Proprietary and Confidential 1-1

RAN
1 Introduction to This Document SRNS Relocation
02 (2009-06-30)
This is the document for the second commercial release of RAN11.0.
Compared with 01 (2009-03-30) of RAN11.0, this issue adjusts the structure of the document.
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 Type Change Description Parameter Change
Feature change None. None.

Editorial change The title of the document is changed from The added parameter is as
SRNS Relocation Description to SRNS follows:
Relocation Parameter Description. z SrnsRabCnDomainType
Parameter names are replaced with
parameter IDs.
1-2 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

RAN
SRNS Relocation 2 Overview of SRNS Relocation
2 Overview of SRNS Relocation
When the UE moves from the coverage area of one RNC to another, the UE context can be
relocated accordingly in two ways: one is through SRNS relocation and the other is through
DSCR.
Serving Radio Network System (SRNS) relocation is a process where the serving RNC
(SRNC) of a UE changes from one RNC to another RNC. The SRNC manages the connection
between the UE and the UTRAN. With the relocation of the SRNC, the management over the
connection between the UE and the UTRAN transfers from one RNC to another RNC.
Based on relocation causes, SRNS relocation consists of the following types:
z Static relocation (UE not involved)
z Relocation due to hard handover (UE involved)
z Relocation due to cell or URA update (UE not involved)
Static relocation and relocation due to cell or URA update require that the Iur interface is
available.
The relocation due to hard handover can be performed regardless of whether the Iur interface
is available or not.
2.1 Basic Types of SRNS Relocation

2.1.1 Static Relocation
When the Iur interface is available, the UE may use the radio resources of one RNC (DRNC)
and be connected to the CN through another RNC (SRNC).
After a UE in CELL_DCH state adds or removes radio links during movement, static
relocation occurs if all the radio links are in the DRNC instead of the SRNC.
Figure 2-1 shows the static relocation.

RAN
2 Overview of SRNS Relocation SRNS Relocation
Figure 2-1 Static relocation
After SRNS relocation, Iur resources for the UE are released. The Target RNC (TRNC) not
only provides radio resources for the UE but also connects the UE to the CN.
The purposes of the static relocation are as follows:
z To reduce the bandwidth occupied by the Iur interface: Before relocation, the UE
forwards the data from the SRNC to the DRNC, occupying the Iur bandwidth; after
relocation, the UE no longer forwards data over the Iur interface, and therefore the
originally occupied Iur bandwidth can be released.
z To shorten the transmission delay of the user plane: Before relocation, the UE forwards
the data from the SRNC to the DRNC, which leads to longer transmission delay on the
user plane.
2.1.2 SRNS Relocation due to Hard Handover

This type of relocation occurs when a UE in CELL_DCH state is handed over from one RNC
to another RNC. This is a process of relocating the UE context from the SRNC to the DRNC.
Figure 2-2 shows the SRNS relocation due to hard handover.
Figure 2-2 SRNS relocation due to hard handover
2.1.3 SRNS Relocation due to Cell or URA Update

This type of relocation occurs when a UE in CELL_PCH, CELL_FACH, or URA_PCH state
performs a cell reselection to another RNC.

RAN
SRNS Relocation 2 Overview of SRNS Relocation
Figure 2-3 shows the SRNS relocation due to cell or URA update.
Figure 2-3 SRNS relocation due to cell or URA update
2.2 DSCR
Directed Signalling Connection re-establishment (DSCR) is a process where the RNC
requests the UE to re-establish RRC connections as well as services immediately after it
automatically releases the current RRC connection that carries the non-real-time RABs. When
the RNC sends the UE an RRC CONN REL message with a cause value of "Directed
Signalling Connection re-establishment", this process enables the UE to initiate an RRC
re-establishment and immediately perform a URA update.
The benefits of DSCR are as follows:
z When the NEs involved do not support SRNS relocation
DSCR can ensure that communications are not interrupted when the UE moves to the
coverage area of another RNC.
z When the Iur interface involved does not support HSPA
If HSPA carries RABs but Iur does not support HSPA, the SRNC must be degraded to
the DCH first before the relocation procedure. After relocation to the DRNC, the SRNC
is then upgraded to the HS-DSCH or E-DCH. The direct re-establishment through DSCR,
however, avoids the degrade or upgrade of channels, reduces the consumption of
transmission resources on the Uu interface, and improves user experience.
When the UE moves from the coverage area of one RNC to another RNC:
z When the conditions for initiating relocation are met, the SRNC triggers the DSCR
procedure in the case that PSBEPROCTYPE (handover type of PS BE service) in
ADD NRNC is set to CORRM_SRNSR_PSBE_DSCR.
z Otherwise, the SRNC triggers the relocation procedure.
z If the relocation fails, the RNC continues to trigger the DSCR procedure.
The relocation procedure mentioned above can be triggered by any causes, such as hard
handover, static relocation, and cell or URA update.
Figure 2-4 shows the relation between SRNS relocation and DSCR.

RAN
2 Overview of SRNS Relocation SRNS Relocation
Figure 2-4 Relationship between SRNS relocation and DSCR.

RAN
SRNS Relocation 3 SRNS Relocation Algorithms
3 SRNS Relocation Algorithms
Handover, including intra-frequency soft handover, intra- or inter-frequency hard handover is

introduced here because:
z The static relocation may occur after handover over Iur
z The relocation due to hard handover may occur if handover over Iur is not allowed
When the target cell under the target RNC fulfils the criteria for intra-frequency soft handover,
intra- or inter-frequency hard handover, the conditions that the handover over Iur is triggered
are as follows:
z Whether the Iur interface is available depends on the setting of the following two
parameters according to handover types:
− Whether intra- or inter- frequency hard handover is allowed over the Iur interface
depends on the setting of the HHOTRIG parameter.
− Whether soft handover is allowed over the Iur interface depends on the setting of the
SHOTRIG parameter.
The SHOTRIG parameter consists of three subswitches:
z CS_SHO_SWTICH
If CS_SHO_SWTICH is checked, soft handover for CS service over the Iur interface is
allowed.
z HSPA_SHO_SWTICH
If HSPA_SHO_SWTICH is checked, soft handover for HSPA service over the Iur
interface is allowed.
z NON_HSPA_SHO_SWTICH
If NON_HSPA_SHO_SWTICH is checked, soft handover for non-HSPA PS service
over the Iur interface is allowed.
3.1 SRNS Relocation Algorithms

This section describes the algorithms of static relocation, relocation due to hard handover, and
relocation due to cell or URA update.

RAN
3 SRNS Relocation Algorithms SRNS Relocation
3.1.1 Algorithm of Static Relocation

intra- or inter-frequency hard handover, if the handover procedure over Iur is allowed and the
UE is in CELL_DCH state, then the SRNC will trigger soft or hard handover procedures to
move all radio links from the SRNC to the Target RNC (TRNC).
If the radio links of a UE in CELL_DCH state are provided only by the TRNC, the static
relocation can be triggered in one of the following four situations:
z SRNS relocation based on delay optimization
The SRNC uses the SRNSRDELAYOFFSET parameter to calculate the transmission
delay on the user plane.
To enable SRNS relocation in this situation, set subparameter
SRNSR_DSCR_PROPG_DELAY_SWITCH of SrnsrSwitch to ON, and set the
PSBEPROCTYPE parameter of the DRNC to CORRM_SRNSR_PSBE_RELOC.
z SRNS relocation based on transmission optimization
The SRNC calculates the bandwidth occupancy of the Iur interface. If the occupancy
exceeds the threshold FWDCONGBW, the SRNC calculates each interval
(SRNSRIURRESELECTTIMERLEN), selects the three UEs with max bitrates on the
congested path one time, and then triggers relocation. The SRNC does not stop to select
the UEs on the congested path until the occupancy becomes lower than the threshold
BWDCONGBW or there is no UE that SRNS relocation applies to.
To enable SRNS relocation in this situation, set the subparameter
SRNSR_DSCR_IUR_RESRCE_SWITCH of SrnsrSwitch to ON, and set the
z SRNS relocation or DSCR based on time separation
If the radio links of a UE in CELL_DCH state are provided only by the TRNC for a
period of time that exceeds the value of SRNSRSEPARATEDURATION, the SRNC
triggers SRNS relocation.
SRNSR_DSCR_SEPRAT_DUR_SWITCH of SrnsrSwitch to ON, and set the
z SRNS relocation based on location separation
The SRNC initiates SRNS relocation if the UE moves to an area controlled by the
DRNC that contains all the links and if all the intra-frequency neighboring cells of the
current best cell do not belong to the SRNC.
SRNSR_DSCR_LOC_SEPRAT_SWITCH of SrnsrSwitch to ON, and set the

RAN
z If a UE in CELL_FACH state or CELL_PCH state, or CELL_URA state are under the Target RNC
for a period of time that exceeds the value of 60s, the SRNC initiates SRNS relocation.
z SRNS relocation-allowed traffic type (SrnsRabCnDomainType) determines the bearing policy over
the Iur interface. If the parameter is set to RT, only the real-time service can trigger the static
relocation; if the parameter is set to NRT, only the non-real-time service can trigger the static
relocation; if the parameter is set to ALL, all services can trigger the static relocation.
3.1.2 Algorithm of Relocation due to Hard Handover

intra- or inter-frequency hard handover, if the handover procedure over Iur is not allowed and
the UE is in CELL_DCH state, then the SRNC will trigger SRNS relocation due to hard
handover.
3.1.3 Algorithm of Relocation due to Cell or URA Update

The target cell of cell or URA update is the DRNC cell. If the update succeeds, the UE
initiates static relocation due to cell update after the UE stays in the DRNC cell for 60s.
The target cell of cell or URA update is the DRNC cell. If the update fails and the failure
cause is that SuppIurCch of the DRNC is OFF, then relocation due to cell update is
triggered.
In either case, when the relocation due to cell or URA update meets the requirement and
PSBEPROCTYPE of the DRNC is set to CORRM_SRNSR_PSBE_RELOC, the
relocation procedure is triggered.
The cell or URA update mentioned above refers to the update when the UE is in CELL_FACH,
CELL_PCH, or CELL_URA state.
3.2 Signaling Procedure of SRNS Relocation

This section describes the signaling procedures of static relocation, relocation due to hard
handover, and relocation due to cell/URA update.
3.2.1 Signaling Procedure of Static Relocation

Figure 3-1 shows the signaling procedure of static relocation when the UE is in CELL_DCH
state.

RAN
Figure 3-1 Signaling procedure of static relocation when the UE is in CELL_DCH state
The UE sets up an RRC connection to RNC 1, which is the SRNC. During the relocation,
RNC 1 is the source RNC and RNC 2 is the target RNC.
The signaling procedure of static relocation based on delay optimization is as follows:
Step 1 When all radio connections are provided by RNC 2, and RNC 1 detects that the transmission
delay is higher than the threshold, then RNC 1 sends the CN a RELOCATION REQUIRED
message, requesting SRNS relocation.
Except for the triggering conditions, the signaling procedure is identical for all types of static relocation,
that is, static relocation based on delay optimization, transmission optimization, time separation, and
location separation.
Step 2 The CN sends a RELOCATION REQUEST message to RNC 2 and forwards the SRNS
relocation request to RNC 1.
Step 3 RNC 2 prepares L2 resources for the relocation and then sends a RELOCATION REQUEST
ACKNOWLEDGE message to the CN.
Step 4 The CN sends RNC 1 a RELOCATION COMMAND message, notifying RNC 1 that SRNS
relocation starts.
Step 5 RNC 1 completes related preparations, such as stopping signaling and traffic RLCs, and then
sends a RELOCATION COMMIT message, requesting RNC 2 to start the relocation.

RAN
Step 6 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.
Step 7 During this period, RNC 2 sends the UE a UTRAN MOBILITY INFORMATION message in
unacknowledged mode (UM), notifying the UE of the new UTRAN information.
Step 8 The UE sends RNC 2 a UTRAN MOBILITY INFORMATION CONFIRM message in
acknowledged mode (AM).
Step 9 RNC 2 sends a RELOCATION COMPLETE message to the CN. RNC 2 becomes the SRNC.
Step 10 RNC 2 sends the UE a UE CAPABILITY ENQUIRY message to query the UE capability
information.
Step 11 The UE sends RNC 2 a UE CAPABILITY INFORMATION message, which contains the UE
capability information.
Step 12 RNC 2 reads the UE capability information and then sends a UE CAPABILITY
INFORMATION CONFIRM message to the UE.
Step 13 The CN sends RNC 1 an IU RELEASE COMMAND message, requesting RNC 1 to release
the Iu interface resources related to this UE.
Step 14 RNC 1 sends an IU RELEASE COMPLETE message to the CN after completing SRNS
relocation.
----End
3.2.2 Signaling Procedure of Relocation due to Hard Handover

Figure 3-2 shows the signaling procedure of relocation due to hard handover.

RAN
Figure 3-2 Signaling procedure of relocation due to hard handover
The signaling procedure is as follows:
Step 1 After receiving the hard handover measurement report, RNC 1 sends the CN a
RELOCATION REQUIRED message, requesting SRNS relocation.
Step 2 The CN sends a RELOCATION REQUEST message to RNC 2.
Step 3 RNC 2 sends a RADIO LINK SETUP REQUEST message, instructing the NodeB to set up a
radio link.
Step 4 The NodeB sets up a radio link and then responds with a RADIO LINK SETUP RESPONSE
message.
Step 5 RNC 2 prepares for SRNS relocation and then sends a RELOCATION REQUEST
ACKNOWLEDGE message to the CN.

RAN
Step 6 The CN sends RNC 1 a RELOCATION COMMAND message, instructing RNC 1 to start
SRNS relocation.
Step 7 RNC 1 sends the CN a FORWARD SRNS CONTEXT message, notifying the CN of the
context related to the SRNS.
Step 8 RNC 1 sends the UE a RADIO BEARER RECONFIGURATION message, requesting the UE
to reconfigure a physical channel.
Step 9 The CN sends a FORWARD SRNS CONTEXT message to RNC 2.
Step 10 The NodeB sends a RADIO LINK RESTORE INDICATION message to RNC 2.
Step 11 RNC 2 sends a RELOCATION DETECT message to the CN.
Step 12 The UE sends a RADIO BEARER RECONFIGURATION COMPLETE message to RNC 2.
Step 13 RNC 2 sends a RELOCATION COMPLETE message to the CN. RNC 2 becomes the SRNC.
Step 14 RNC 2 sends the UE a UTRAN MOBILITY INFORMATION message, notifying the UE of
the new UTRAN information.
Step 15 The UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to RNC 2.
Step 16 The CN sends RNC 1 an IU RELEASE COMMAND message, requesting RNC 1 to release
the Iu interface resources.
Step 17 RNC 1 sends an IU RELEASE COMPLETE message to the CN.
Step 18 RNC 2 sends the UE a UE CAPABILITY ENQUIRY message to query the UE capability
information.
Step 19 The UE sends RNC 2 a UE CAPABILITY INFORMATION message, which contains the UE
capability information.
Step 20 RNC 2 reads the UE capability information and then sends a UE CAPABILITY
INFORMATION CONFIRM message to the UE.
----End
3.2.3 Signaling Procedure of SRNS Relocation due to Cell or URA

Update
For details, see the URA/Cell Update Parameter Description.

RAN
SRNS Relocation 4 DSCR Initiation and Signaling Procedure
4 DSCR Initiation and Signaling Procedure
4.1 DSCR Initiation

The RNC releases the RRC connection that carries non-real-time RABs through the DSCR
procedure. Then, the RNC immediately requests the UE to re-establish RRC connections and
services. The DSCR procedure can be initiated only by the non-real-time RABs. That is, if the
RRC connection does not carry non-real-time RABs, the RNC cannot release the RRC
connection through DSCR.
4.1.1 DSCR Initiation due to Cell Update of Radio Link Failure

If the UE in CELL_DCH state detects that the downlink radio link fails to be established, the
UE will perform cell update with the cause of "radio link failure". The target cell of the update
is the DRNC cell, but at this time SuppIurCch of the DRNC is OFF, and therefore the
DSCR procedure is initiated.
4.1.2 DSCR Initiation due to Cell Update of Non-Iur Interface

The RNC receives the information about cell update of the UE and finds that the reported
SRNC ID is not the local RNC ID. In addition, no Iur interface is available between this RNC
and the SRNC, and therefore the DSCR procedure is initiated in the DRNC.
4.1.3 DSCR Initiation due to Cell Update of

Non-HSPA-Supportive Iur Interface
If a HSPA service exists, the UE is handed over to the cell of the DRNC that supports HSPA.
The DSCR is directly performed in the cell of the DRNC to re-establish the HSPA service
because Iur does not support HSPA.
If a HSPA service exists but Iur does not support HSPA, all types of handovers for HSPA and
HSPA serving cell change procedure are forbidden.
Whether Iur supports the HSPA service depends on the following parameters:
z When IurHsdpaSuppInd of the DRNC is set to OFF, Iur does not support the HSDPA
service. Otherwise, Iur supports the HSDPA service.
z When IurHsupaSuppInd of the DRNC is set to OFF, Iur does not support the HSUPA
service. Otherwise, Iur supports the HSUPA service.
If Iur supports the HSPA service, the RNC triggers a handover procedure for HSPA or an
HSPA serving cell change procedure when the target cell under the target RNC fulfils the
criteria for handover.

RAN
4 DSCR Initiation and Signaling Procedure SRNS Relocation
Otherwise, the RNC triggers DSCR or handover procedure by degrading the HSPA service to
DCH service if handover over Iur is allowed.
For a UE with non-real-time PS RABs on the HS-DSCH or E-DCH, the SRNC initiates
DSCR regardless of whether the value of PSBEPROCTYPE for the DRNC is set to
CORRM_SRNSR_PSBE_RELOC or CORRM_SRNSR_PSBE_DSCR if the following
conditions are both met:
z The current best cell is an HSPA-supportive cell under the DRNC, that is,
HSDSCH_SUPPORT or EDCH_SUPPORT of the subswitch CellCapContainerFdd
is selected. The non-real-time RABs exist on the HS-DSCH and E-DCH concurrently, or
the best cell supports HS-DSCH or E-DCH.
z The serving cell in the source SRNC needs to be removed or the requirement for intra- or
inter-frequency hard handover of the UE from the SRNC cell to the DRNC cell is
satisfied.
If neither of the above conditions is met:
z If soft handover procedure over Iur is allowed, HSPA services that the Iur interface does
not support are degraded to the DCH and then soft handover is triggered.
z If intra- or inter- frequency hard handover procedure over Iur is allowed, HSPA services
that the Iur interface does not support are degraded to the DCH and then hard handover
is triggered.
If the non-real-time RABs exist on the HS-DSCH and E-DCH concurrently, or if the Iur interface of the
neighboring RNC supports the HSDPA or HSUPA service, the DSCR procedure is not initiated.
4.2 Signaling Procedure of DSCR

Figure 4-1 shows the signaling procedure of DSCR.
Figure 4-1 Signaling procedure of DSCR

RAN
SRNS Relocation 4 DSCR Initiation and Signaling Procedure
The signaling procedure is as follows:

Step 1 RNC 1 decides to initiate a DSCR procedure.
Step 2 RNC 1 sends RNC 2 a DOWNLINK SIGNALLING TRANSFER REQUEST message,
requesting RNC 2 to send an RRC CONNECTION RELEASE message to the UE.
Step 3 RNC 2 sends the UE an RRC CONNECTION RELEASE message with "Release cause" of
"directed signalling connection re-establishment".
Step 4 After receiving the message, the UE releases the current RAB and RRC connection and then
enters the idle mode. The UE performs a cell reselection procedure to find a suitable cell.
Then, the UE re-establishes an RRC connection immediately.
Step 5 The UE sends RNC 2 a ROUTE AREA UPDATE message to initiate a URA update.
Step 6 The SGSN requests data forwarding from RNC 1. Then, RNC 1 forwards data packets, except
those unacknowledged, to the SGSN.
Step 7 The UE sends the SGSN a DIRECT TRANSFER message to request setup of a service.
Step 8 The SGSN initiates an RAB establishment procedure.
----End

RAN
SRNS Relocation 5 Parameters
5 Parameters
The following describes the parameters related to SRNS Relocation.

For the meaning of each parameter, see Table 5-1. For the default value, value ranges, and
MML commands of each parameter, see 0.
Table 5-1 SRNS relocation parameter description (1)

Parameter Id Description
SHOTRIG Indicating whether to trigger soft handover cross the Iur interface between the RNC
and the neighboring RNC:
1) CS_SHO_SWITCH. Indicating whether to trigger hard handover for CS cross the
Iur interface.
2) HSPA_SHO_SWITCH. Indicating whether to trigger hard handover for HSPA cross
the Iur interface.
3) NON_HSPA_SHO_SWITCH. Indicating whether to trigger hard handover for
PS(R99) cross the Iur interface.
SRNSRDELAYOFFSE When [Measurement transfer delay by FP Node synchronization between SRNC and
T DRNC ]+[Estimated non-measurement delay offset] > [transfer delay provided by
the Qos of the current traffic], the relocation will be triggered. The value of this
parameter should be set according to the time delay concerned requirements of the
most common services over the Iur interface. If the value is too small, unnecessary
relocation will occur; if the value is too large, the QoS of the services over the Iur
interface will be affected.
The transfer delay provided by the Qos of the current traffic is the parameter set at the
CN and is notified to the RNC through an RAB ASSIGNMENT REQUEST message.
SRNSRIURRESELEC Time interval between two SRNS relocations based on Iur resource optimization. For
TTIMERLEN each time interval, the RNC specifies several UEs to perform the relocation based on
Iur resource optimization. The parameter should be set according to the the time
interval of the Iur source congestion report. The difference between the previous two
values cannot be too large. Individually changing a parameter will cause the time
difference in the congestion report and the relocation triggering, and thus the algorithm
cannot be efficiently performed.

RAN
5 Parameters SRNS Relocation
SRNSRSEPARATEDU If SRNSR_DSCR_SEPRAT_DUR_SWITCH of [SrnsrSwitch] in SET

RATION CORRMALGOSWITCH is on, after the separation of the SRNC and the CRNC, a
timer starts. After the time is expired, the SRNS relocation is triggered. This parameter
determines the number of UEs over the Iur interface. If this parameter is set too large,
it will cause too much unnecessary occupied Iur resources; if the parameter is set too
small, ping-pong relocation may occur.
SRNSRABCNDOMAI SRNS relocation-allowed traffic type. This parameter determines the bearing policy
NTYPE over the Iur interface. If the parameter is set to RT, only the real-time service can
trigger the static relocation; if the parameter is set to NRT, only the non-real-time
service can trigger the static relocation; if the parameter is set to ALL, all services can
trigger the static relocation.
PSBEPROCTYPE Indicating whether to replace relocation procedure with DSCR procedure between the
RNC and the neighboring RNC for PS BE Traffic.
HHOTRIG Indicating whether to trigger hard handover cross the Iur interface between the RNC
and the neighboring RNC.
SuppIurCch Indicating whether to support establishing IUR-CCH between the RNC and the
neighboring RNC.
IurHsdpaSuppInd Indicating whether to support Hsdpa over Iur interface of the neighboring RNC.
IurHsupaSuppInd Indicating whether to support Hsupa over Iur interface of the neighboring RNC.
IurExistInd Indicating whether to config neighbouring RNC's DSP index.

RAN
CellCapContainerFdd 1)DELAY_ACTIVATION_SUPPORT (delay activation support indicator):when the

indicator is TRUE, it means that the cell support delay activation. Delayed Activation
IE indicates that the activation of the DL power shall be delayed until an indicated
CFN or until a separate activation indication is received.
2)HSDSCH_SUPPORT(HSDSCH support indicator):when the indicator is TRUE, it
means that the cell support HSDSCH and enable downlink traffic to be established in
HSDSCH.
3)FDPCH_SUPPORT(F-DPCH support indicator):when the indicator is TRUE, it
means that the cell support F-DPCH and enable downlink signal to be established in
F-DPCH, but the cell can not support F-DPCH if it does not support HSDSCH.
4)EDCH_SUPPORT(E-DCH support indicator):when the indicator is TRUE, it means
that the cell support E-DCH.
5)EDCH_2MS_TTI_SUPPORT(E-DCH 2ms TTI support indicator):when the
indicator is TRUE, it means that the cell support E-DCH 2ms TTI.
6)EDCH_2SF2_AND_2SF4_SUPPORT(E-DCH max SF support 2SF2+2SF4
indicator):when the indicator is TRUE, it means that the cell has E-DCH SF capability
of 2SF2+2SF4.
7)EDCH_2SF2_SUPPORT(E-DCH max SF support 2SF indicator):when the indicator
is TRUE, it means that the cell has E-DCH SF capability of 2SF2.
8)EDCH_2SF4_SUPPORT(E-DCH max SF support 2SF4 indicator):when the
indicator is TRUE, it means that the cell has E-DCH SF capability of 2SF4.
9)EDCH_SF4_SUPPORT(E-DCH max SF support SF4 indicator):when the indicator
is TRUE, it means that the cell has E-DCH SF capability of SF4.
10)EDCH_SF8_SUPPORT(E-DCH max SF support SF8 indicator):when the indicator
is TRUE, it means that the cell has E-DCH SF capability of SF8.
11)EDCH_HARQ_IR_COMBIN_SUPPORT(E-DCH support HARQ IR Combining
indicator):when the indicator is TRUE, it means that the cell use IR combine Mode
when MAC-e PDUs are received more than one time in E-DCH.
12)EDCH_HARQ_CHASE_COMBIN_SUPPORT(E-DCH support HARQ CHASE
Combining indicator): when the indicator is TRUE, it means that the cell use CHASE
combine Mode when MAC-e PDUs are received more than one time in E-DCH.
13) CPC_DTX_DRX_SUPPORT (CPC DTX-DRX support indicator): when the
indicator is TRUE, it indicates that the cell supports CPC DTX_DRX.
14) CPC_HS_SCCH_LESS_OPER_SUPPORT (CPC HS-SCCH less operation
support indicator): when the indicator is TRUE, it indicates that the cell supports CPC
HS-SCCH less operation.
15) HSPAPLUS_MIMO_SUPPORT (MIMO support indicator): when the indicator is
TRUE, it indicates that the cell supports MIMO.
16) HSPAPLUS_UL_16QAM_SUPPORT (uplink 16QAM support indicator): when
the indicator is TRUE, it indicates that the cell supports uplink 16QAM.
17) FLEX_MACD_PDU_SIZE_SUPPORT (flexible MAC-d PDU Size support
indicator): when the indicator is TRUE, it indicates that the cell supports flexible
MAC-d PDU Size.
18) FDPCH_SLOT_FORMAT_SUPPORT (F-DPCH slot format support indicator):
when the indicator is TRUE, it indicates that the cell supports F-DPCH slot format.
19) HSPAPLUS_DL_64QAM_SUPPORT (downlink 64QAM support indicator):
when the indicator is TRUE, it indicates that the cell supports downlink 64QAM.

RAN
SrnsrSwitch SRNSR algorithm switch.

1) SRNSR_DSCR_IUR_RESRCE_SWITCH: When the switch is on, relocation for
transmission optimization over the Iur interface is allowed. When there is congestion
over the Iur interface, the UE may be selected to initiate relocation or DSCR if the UE
has only a radio link over the Iur interface and the link have the same attributes as the
congested link. Based on DSCRInd of ADD NRNC, the RNC decides whether to
initiate relocation or DSCR. When the RRC CONN REL message with the cause value
"Directed Signalling Connection re-establishment" is sent to the UE, the UE initiates
RRC reestablishment and updates the routing area once immediately.
2) SRNSR_DSCR_LOC_SEPRAT_SWITCH: When the switch is on, the RNC
initiates static relocation or DSCR if the optimal cell and the intra-frequency
neighboring cell of the optimal cell are not on the SRNC (the SRNC and the CRNC are
separated). Based on DSCRInd of ADD NRNC, the RNC decides whether to initiate
relocation or DSCR.
3) SRNSR_DSCR_PROPG_DELAY_SWITCH: When the switch is on, the RNC
initiates static relocation or DSCR if the delay over a link cannot meet QoS
requirements (the SRNC and the CRNC are separated). Thus, delay over the link is
reduced on the network side and the QoS is enhanced. Based on DSCRInd of ADD
NRNC, the RNC decides whether to initiate relocation or DSCR.
4) SRNSR_DSCR_SEPRAT_DUR_SWITCH: When the switch is on, the RNC
initiates static relocation or DSCR if the duration of separation between the SRNC and
the CRNC exceeds a configured threshold. Based on DSCRInd of ADD NRNC, the
RNC decides whether to initiate relocation or DSCR.
FWDCONGBW If the available forward bandwidth is less than or equal to this value, the forward
congestion alarm is emitted.
BWDCONGBW If the available backward bandwidth is less than or equal to this value, the backward
congestion alarm is emitted.
Table 5-2 SRNS relocation parameter description (2)
Parameter Id Default GUI Value Range Actual Value Unit MML NE

Value Range Command
SHOTRIG - CS_SHO_SWITCH, CS_SHO_SWITCH, None ADD NRNC RNC

HSPA_SHO_SWITC HSPA_SHO_SWIT (Mandatory)
H, CH,
NON_HSPA_SHO_S NON_HSPA_SHO_
WITCH SWITCH

RAN

Value Range Command
SRNSRDELA - 0~400 0~400 ms SET SRNSR RNC

Y OFFSET (Optional)
SRNSRIURR - 1~100 1~100 s SET SRNSR RNC

E SELECT (Optional)
TIMERLEN
SRNSRSEPA - 1~255 1~255 s SET SRNSR RNC

RATEDURA (Optional)
TION
SRNSRABCN - RT(Real time RT,NRT,ALL None SET SRNSR RNC
DO service), NRT Non (Optional)
MAINTYPE real time service),
ALL (All service)
PSBEPROCT CORRM_ CORRM_SRNSR_PS CORRM_SRNSR_P None ADD NRNC RNC
YPE SRNSR BE_RELOC, SBE_RELOC, (Optional)
_PSBE_R CORRM_SRNS CORRM_SRNSR_P
ELOC R_PSBE_DSCR SBE_DSCR
HHOTRIG - OFF, ON OFF,ON None ADD NRNC RNC
(Mandatory)
SuppIurCch NO NO, YES NO, YES None ADD NRNC RNC

(Optional)
IurHsdpaSupp OFF OFF, ON OFF, ON None ADD NRNC RNC

Ind (Optional)
IurHsupaSupp OFF OFF, ON OFF, ON None ADD NRNC RNC

Ind (Optional)
IurExistInd - TRUE, FALSE TRUE, FALSE None ADD NRNC RNC

(Mandatory)

RAN

Value Range Command
CellCap - DELAY_ACTIVATI DELAY_ACTIVAT None ADD RNC

Container Fdd ON_ SUPPORT ION_ SUPPORT, NRNCCELL
(delay activation HSDSCH_SUPPOR (Mandatory)
support indication), T,
HSDSCH_SUPPORT FDPCH_SUPPORT,
(HSDSCH support EDCH_SUPPORT,
indication), EDCH_2MS_TTI_S
FDPCH_SUPPORT UPPORT,
(F-DPCH support EDCH_2SF2_AND
indication), _2SF4_SUPPORT,
EDCH_SUPPORT(E- EDCH_2SF2_SUPP
DCH support ORT,
indication), EDCH_2SF4_SUPP
EDCH_2MS_TTI_S ORT,
UPPORT(E-DCH EDCH_SF4_SUPPO
2ms TTI support RT,
indicator), EDCH_SF8_SUPPO
EDCH_2SF2_AND_ RT,
2SF4_SUPPORT(E- EDCH_HARQ_IR_
DCH max SF support COMBIN_SUPPOR
2SF2+2SF4 T,
indicator), EDCH_HARQ_CH
EDCH_2SF2_SUPPO ASE_
RT(E-DCH max SF COMBIN_SUPPOR
support 2SF2 T,
indicator), CPC_DTX_DRX_S
EDCH_2SF4_SUPPO UPPORT,
RT(E-DCH max SF CPC_HS_SCCH_L
support 2SF4 ESS_
indicator), OPER_SUPPORT,
EDCH_SF4_SUPPO HSPAPLUS_MIMO
RT(E-DCH max SF _SUPPORT,
support SF4 HSPAPLUS_UL_16
indicator), QAM_SUPPORT,
EDCH_SF8_SUPPO FLEX_MACD_PD
RT(E-DCH max SF U_SIZE_SUPPORT
support SF8 ,
indicator), FDPCH_SLOT_FO
EDCH_HARQ_IR_C RMAT_SUPPORT,
OMBIN_SUPPORT( HSPAPLUS_DL_64
E-DCH support QAM_SUPPORT
HARQ IR Combining
indicator),
EDCH_HARQ_CHA
SE_COMBIN_SUPP
ORT(E-DCH support
HARQ CHASE
Combining indicator),
CPC_DTX_DRX_SU
PPORT(CPC
DTX-DRX support

RAN

Value Range Command
indicator),
CPC_HS_SCCH_LE
SS_OPER_SUPPOR
T(CPC HS-SCCH
less operation support
indicator),
HSPAPLUS_MIMO_
SUPPORT(MIMO
support indicator),
HSPAPLUS_UL_16
QAM_SUPPORT(upl
ink 16QAM support
indicator),
FLEX_MACD_PDU
_SIZE_SUPPORT(fle
xible MAC-d PDU
Size support
indicator),
FDPCH_SLOT_FOR
MAT_SUPPORT(F-
DPCH slot format
support indicator),
HSPAPLUS_DL_64
QAM_SUPPORT(do
wnlink 64QAM
support indicator)
SrnsrSwitch - SRNSR_DSCR_IUR SRNSR_DSCR_IU None SET RNC

_ R_RESRCE_SWIT CORRMALG
RESRCE_SWITCH, CH, OSWITCH
SRNSR_DSCR_LOC SRNSR_DSCR_LO (Optional)
_ C_SEPRAT_SWIT
SEPRAT_SWITCH, CH,
SRNSR_DSCR_PRO SRNSR_DSCR_PR
PG_ OPG_DELAY_SWI
DELAY_SWITCH, TCH,
SRNSR_DSCR_SEP SRNSR_DSCR_SE
RAT_ PRAT_DUR_SWIT
DUR_SWITCH CH
FWDCONGB 0 0~320000 0~320000 kbit/s ADD RNC
W AAL2PATH
(Optional)
BWDCONGB 0 0~320000 0~320000 kbit/s ADD RNC
W AAL2PATH
(Optional)
The Default Value column is valid for only the optional parameters.

RAN
The "-" symbol indicates no default value.

RAN
SRNS Relocation 6 Counters
6 Counters
The following describes the counters related to SRNS Relocation.

For details, see the RNC Performance Counter Reference.

RAN
SRNS Relocation 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

RAN
SRNS Relocation 8 Reference Documents
8 Reference Documents
The following lists the reference documents related to the feature:

1. 3GPP TR 21.905 "Vocabulary for 3GPP Specifications"
2. 3GPP TS 25.331 "Radio Resource Control (RRC); protocol specification"
3. 3GPP TS 25.413 "UTRAN Iu interface RANAP signaling"
4. Basic Feature Description of Huawei UMTS RAN11.0 V1.5
5. Optional Feature Description of Huawei UMTS RAN11.0 V1.5


SRNS Relocation Parameter Description PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SRNS Relocation Parameter Description PDF

Загружено:

Авторское право:

Доступные форматы

RAN

Huawei Proprietary and Confidential

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

1 Introduction to This Document...............................................................................................1-1

2 Overview of SRNS Relocation ................................................................................................2-1

3 SRNS Relocation Algorithms ..................................................................................................3-1

4 DSCR Initiation and Signaling Procedure............................................................................4-1

Issue 02 (2009-06-30) Huawei Proprietary and Confidential iii

1 Introduction to This Document

1.2 Intended Audience

1.3 Change History

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 1-1

Change Type Change Description Parameter Change

Feature change None. None.

1-2 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

2 Overview of SRNS Relocation

2.1 Basic Types of SRNS Relocation

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 2-1

Figure 2-1 Static relocation

2.1.2 SRNS Relocation due to Hard Handover

Figure 2-2 SRNS relocation due to hard handover

2.1.3 SRNS Relocation due to Cell or URA Update

2-2 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

Figure 2-3 SRNS relocation due to cell or URA update

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 2-3

Figure 2-4 Relationship between SRNS relocation and DSCR.

2-4 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

3 SRNS Relocation Algorithms

Handover, including intra-frequency soft handover, intra- or inter-frequency hard handover is

3.1 SRNS Relocation Algorithms

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 3-1

3.1.1 Algorithm of Static Relocation

3-2 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

3.1.2 Algorithm of Relocation due to Hard Handover

3.1.3 Algorithm of Relocation due to Cell or URA Update

3.2 Signaling Procedure of SRNS Relocation

3.2.1 Signaling Procedure of Static Relocation

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 3-3

3-4 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

3.2.2 Signaling Procedure of Relocation due to Hard Handover

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 3-5

Figure 3-2 Signaling procedure of relocation due to hard handover

3-6 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

3.2.3 Signaling Procedure of SRNS Relocation due to Cell or URA

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 3-7

4 DSCR Initiation and Signaling Procedure

4.1 DSCR Initiation

4.1.1 DSCR Initiation due to Cell Update of Radio Link Failure

4.1.2 DSCR Initiation due to Cell Update of Non-Iur Interface

4.1.3 DSCR Initiation due to Cell Update of

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 4-1

4.2 Signaling Procedure of DSCR

Figure 4-1 Signaling procedure of DSCR

4-2 Huawei Proprietary and Confidential Issue 02 (2009-06-30)

The signaling procedure is as follows:

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 4-3

The following describes the parameters related to SRNS Relocation.

Table 5-1 SRNS relocation parameter description (1)

Issue 02 (2009-06-30) Huawei Proprietary and Confidential 5-1

SRNSRSEPARATEDU If SRNSR_DSCR_SEPRAT_DUR_SWITCH of [SrnsrSwitch] in SET

IurExistInd Indicating whether to config neighbouring RNC's DSP index.