srns relocation.docx

RAN

SRNS Relocation Parameter Description

Issue 01

Date 2009-03-30

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.,

Ltd

any assistance, please contact our local office or company headquarters.

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

Bantian, 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.


Ltd

mailto:[email protected]

http://www.huawei.com/

RANSRNS Relocation Parameter Description

About This Document

About This Document

AuthorPrepared by Tong Lili Date 2008-10-20

Edited by Sun Jingshu Date 2008-10-30

Reviewed by DateTranslated by Tong Aruna Date 2008-12-10

Tested by Zhang Shasha Date 2009-01-10

Approved by Duan Zhongyi Date 2009-03-30


Ltd


Contents

Contents

1 Change History...........................................................................1-22 Introduction...............................................................................2-23 SRNS Relocation Principles..........................................................3-2

3.1 Basic Types of SRNS Relocation...................................................................................................................3-23.1.1 Static Relocation...................................................................................................................................3-23.1.2 SRNS Relocation due to Hard Handover..............................................................................................3-23.1.3 SRNS Relocation due to Cell or URA Update......................................................................................3-2

3.2 DSCR..............................................................................................................................................................3-2

4 SRNS Relocation and DSCR Algorithms........................................4-24.1 SRNS Relocation Algorithms.........................................................................................................................4-2

4.1.1 Algorithm of Static Relocation..............................................................................................................4-24.1.2 Algorithm of Relocation due to Hard Handover...................................................................................4-24.1.3 Algorithm of Relocation due to Cell or URA Update...........................................................................4-2

4.2 Signaling Procedure of SRNS Relocation......................................................................................................4-24.2.1 Signaling Procedure of Static Relocation..............................................................................................4-24.2.2 Signaling Procedure of Relocation due to Hard Handover...................................................................4-24.2.3 Signaling Procedure of SRNS Relocation due to Cell or URA Update................................................4-2

5 DSCR Initiation and Signaling Procedure......................................5-25.1 DSCR Initiation..............................................................................................................................................5-2

5.1.1 DSCR Initiation due to Cell Update of Radio Link Failure..................................................................5-25.1.2 DSCR Initiation due to Cell Update of Non-Iur Interface....................................................................5-25.1.3 DSCR Initiation due to Cell Update of Non-HSPA-Supportive Iur Interface......................................5-2

5.2 Signaling Procedure of DSCR........................................................................................................................5-2

6 SRNS Relocation Parameters.......................................................6-26.1 Description.....................................................................................................................................................6-26.2 Values and Ranges..........................................................................................................................................6-2

7 Reference Documents.................................................................7-2

Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.,

Ltd

i


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.

1 Change History

The change history provides information on the changes in different document versions.

Document and Product Versions

Table 1-1 Document and product versions

Document Version RAN 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 SRNS relocation. 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.


Ltd

1




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 SRNS Relocation Description to SRNS Relocation Parameter Description.Parameter names are replaced with parameter IDs.

The added parameter is as follows: SrnsRabCnDomainType


Ltd

2




2 Introduction

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:

Static relocation (UE not involved) Relocation due to hard handover (UE involved) 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.

The benefits of SRNS relocation are as follows:

Static relocation and relocation due to cell or URA updateSRNS relocation can avoid data forwarding on the Iur interface, thus reducing the bandwidth occupied by the Iur interface and shortening the transmission delay of the user plane.

Relocation due to hard handoverSRNS relocation can ensure that communications are not interrupted when the UE moves to the coverage area of another RNC.

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:

When the NEs involved do not support SRNS relocationDSCR can ensure that communications are not interrupted when the UE moves to the coverage area of another RNC.


Ltd

1




When the Iur interface involved does not support HSPAIf 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.

Intended AudienceThis document is intended for:

System operators who need a general understanding of SRNS relocation. Personnel working on Huawei products or systems.

Impact Impact on System Performance

None. Impact on Other Features

None.

Network Elements InvolvedTable 2-1 lists the NEs involved in SRNS relocation.

Table 2-1 NEs involved in SRNS relocation

UE NodeB RNC MSC Server

MGW SGSN GGSN HLR

√ √ √ √ √ √ – –

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


Ltd

2




3 SRNS Relocation Principles

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.

3.1 Basic Types of SRNS RelocationBased on the relocation causes, SRNS relocation consists of three types: static relocation, relocation due to hard handover, and relocation due to cell or URA update.

3.1.1 Static RelocationWhen 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, if all the radio links are in the DRNC instead of the SRNC, static relocation occurs.

Figure 3-1 shows the static relocation.

Figure 3-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:


Ltd

1




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.

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.

3.1.2 SRNS Relocation due to Hard HandoverThis 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 3-1 shows the SRNS relocation due to hard handover.

Figure 3-1 SRNS relocation due to hard handover

3.1.3 SRNS Relocation due to Cell or URA UpdateThis type of relocation occurs when a UE in CELL_PCH, CELL_FACH, or URA_PCH state performs a cell reselection to another RNC.

Figure 3-1 shows the SRNS relocation due to cell or URA update.


Ltd

2




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

3.2 DSCRWhen the UE moves from the coverage area of one RNC to another RNC:

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.

Otherwise, the SRNC triggers the relocation procedure. 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 3-1 shows the relationship between SRNS relocation and DSCR.


Ltd

3




Figure 3-1 Relationship between SRNS relocation and DSCR.

Conditions for staticrelocation are met

Handover conditions aremet but Iur does notsupport handover

Cell/URA updateto the DRNC cell

Updatesucceeds?

Initiate relocationprecedure

DSCR

Relocation

Relocationprecedure fails

UE in CELL_DCHstate?

Yes

Yes

No No

In the DRNC cell, the timew hen the UE is not in

CELL_DCH state is 60s.

No

Yes

Handover type ofPS BE service?

Initiate DSCRprecedure


Ltd

4




4 SRNS Relocation and DSCR Algorithms

Handover, including intra-frequency soft handover, intra- or inter-frequency hard handover is introduced here because:

The static relocation may occur after handover over Iur 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:

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:

CS_SHO_SWTICHIf CS_SHO_SWTICH is checked, soft handover for CS service over the Iur interface is allowed.

HSPA_SHO_SWTICHIf HSPA_SHO_SWTICH is checked, soft handover for HSPA service over the Iur interface is allowed.

NON_HSPA_SHO_SWTICHIf NON_HSPA_SHO_SWTICH is checked, soft handover for non-HSPA PS service over the Iur interface is allowed.

4.1 SRNS Relocation AlgorithmsThis section describes the algorithms of static relocation, relocation due to hard handover, and relocation due to cell or URA update.


Ltd

1




4.1.1 Algorithm of Static RelocationWhen the target cell under the target RNC fulfils the criteria for intra-frequency soft handover, 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:

SRNS relocation based on delay optimizationThe 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.

SRNS relocation based on transmission optimizationThe 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 PSBEPROCTYPE parameter of the DRNC to CORRM_SRNSR_PSBE_RELOC.

SRNS relocation or DSCR based on time separationIf 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.To enable SRNS relocation in this situation, set the subparameter SRNSR_DSCR_SEPRAT_DUR_SWITCH of SrnsrSwitch to ON, and set the PSBEPROCTYPE parameter of the DRNC to CORRM_SRNSR_PSBE_RELOC.

SRNS relocation based on location separationThe 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.To enable SRNS relocation in this situation, set the subparameter SRNSR_DSCR_LOC_SEPRAT_SWITCH of SrnsrSwitch to ON, and set the PSBEPROCTYPE parameter of the DRNC to CORRM_SRNSR_PSBE_RELOC.


Ltd

2




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.

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.

4.1.2 Algorithm of Relocation due to Hard HandoverWhen the target cell under the target RNC fulfils the criteria for intra-frequency soft 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.

4.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.

4.2 Signaling Procedure of SRNS RelocationThis section describes the signaling procedures of static relocation, relocation due to hard handover, and relocation due to cell/URA update.

4.2.1 Signaling Procedure of Static RelocationFigure 4-1 shows the signaling procedure of static relocation when the UE is in CELL_DCH state.


Ltd

3




Figure 4-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.


Ltd

4




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

4.2.2 Signaling Procedure of Relocation due to Hard Handover

Figure 4-1 shows the signaling procedure of relocation due to hard handover.


Ltd

5




Figure 4-1 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.


Ltd

6




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

4.2.3 Signaling Procedure of SRNS Relocation due to Cell or URA Update

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


Ltd

7




5 DSCR Initiation and Signaling Procedure

5.1 DSCR InitiationThe 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.

5.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.

5.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, there is no Iur interface available between this RNC and the SRNC, and therefore the DSCR procedure is initiated in the DRNC.

5.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:


Ltd

1




When IurHsdpaSuppInd of the DRNC is set to OFF, Iur does not support the HSDPA service. Otherwise, Iur supports the HSDPA service.

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.

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:

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.

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:

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.

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.


Ltd

2




5.2 Signaling Procedure of DSCRFigure 5-1 shows the signaling procedure of DSCR.

Figure 5-1 Signaling procedure of DSCR


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


Ltd

3




6 SRNS Relocation Parameters

6.1 DescriptionTable 6-1 SRNS relocation parameter description

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.

SRNSRDELAYOFFSET

When [Measurement transfer delay by FP Node synchronization between SRNC and 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.

SRNSRIURRESELECTTIMERLEN

Time interval between two SRNS relocations based on Iur resource optimization. For 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.

SRNSRSEPARATEDURATION

If SRNSR_DSCR_SEPRAT_DUR_SWITCH of [SrnsrSwitch] in SET 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


Ltd

1





small, ping-pong relocation may occur.

SrnsRabCnDomainType

This parameter 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.

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.

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


Ltd

2





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.

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.


Ltd

3




6.2 Values and RangesTable 6-1 SRNS relocation parameter values and parameter ranges

Parameter ID

Default Value

GUI Value Range

Actual Value Range

Unit MML Command NE

SHOTRIG - CS_SHO_SWITCH, HSPA_SHO_SWITCH, NON_HSPA_SHO_SWITCH

CS_SHO_SWITCH, HSPA_SHO_SWITCH, NON_HSPA_SHO_SWITCH

None ADD NRNC(Mandatory)

RNC

SRNSRDELAYOFFSET

- 0~400 0~400 ms SET SRNSR(Optional) RNC

SRNSRIURRESELECTTIMERLEN

- 1~100 1~100 s SET SRNSR(Optional) RNC

SRNSRSEPARATEDURATION

- 1~255 1~255 s SET SRNSR(Optional) RNC

SrnsRabCnDomainType

- RT (Real time service), NRT (Non real time service), ALL (All service)

RT,NRT,ALL None SET SRNSR RNC

PSBEPROCTYPE

CORRM_SRNSR_PSBE_RELOC

CORRM_SRNSR_PSBE_RELOC, CORRM_SRNSR_PSBE_DSCR

CORRM_SRNSR_PSBE_RELOC, CORRM_SRNSR_PSBE_DSCR

None ADD NRNC(Optional) RNC

HHOTRIG - OFF, ON OFF,ON None ADD NRNC(Mandatory)

RNC

SuppIurCch NO NO, YES NO, YES None ADD NRNC(Optional) RNC

IurHsdpaSuppInd

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

IurHsupaSuppInd

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

IurExistInd - TRUE, FALSE TRUE, FALSE None ADD NRNC(Mandatory)

RNC

CellCapContainerFdd

- DELAY_ACTIVATION_SUPPORT, HSDSCH_SUP

DELAY_ACTIVATION_SUPPORT, HSDSCH_SUPP

None ADD NRNCCELL(Mandatory)

RNC


Ltd

4




Parameter ID

Default Value

GUI Value Range

Actual Value Range

Unit MML Command NE

PORT, FDPCH_SUPPORT, EDCH_SUPPORT, EDCH_2MS_TTI_SUPPORT, EDCH_2SF2_AND_2SF4_SUPPORT, EDCH_2SF2_SUPPORT, EDCH_2SF4_SUPPORT, EDCH_SF4_SUPPORT, EDCH_SF8_SUPPORT, EDCH_HARQ_IR_COMBIN_SUPPORT, EDCH_HARQ_CHASE_COMBIN_SUPPORT, CPC_DTX_DRX_SUPPORT, CPC_HS_SCCH_LESS_OPER_SUPPORT, HSPAPLUS_MIMO_SUPPORT, HSPAPLUS_UL_16QAM_SUPPORT, FLEX_MACD_PDU_SIZE_SUPPORT, FDPCH_SLOT_FORMAT_SUPPORT, HSPAPLUS_DL_64QAM_SUPPORT

ORT, FDPCH_SUPPORT, EDCH_SUPPORT, EDCH_2MS_TTI_SUPPORT, EDCH_2SF2_AND_2SF4_SUPPORT, EDCH_2SF2_SUPPORT, EDCH_2SF4_SUPPORT, EDCH_SF4_SUPPORT, EDCH_SF8_SUPPORT, EDCH_HARQ_IR_COMBIN_SUPPORT, EDCH_HARQ_CHASE_COMBIN_SUPPORT, CPC_DTX_DRX_SUPPORT, CPC_HS_SCCH_LESS_OPER_SUPPORT, HSPAPLUS_MIMO_SUPPORT, HSPAPLUS_UL_16QAM_SUPPORT, FLEX_MACD_PDU_SIZE_SUPPORT, FDPCH_SLOT_FORMAT_SUPPORT, HSPAPLUS_DL_64QAM_SUPPORT

SrnsrSwitch - SRNSR_DSCR_IUR_RESRCE_SWITCH, SRNSR_DSCR

SRNSR_DSCR_IUR_RESRCE_SWITCH, SRNSR_DSCR_

None SET CORRMALGOSWITCH(Optional)

RNC


Ltd

5




Parameter ID

Default Value

GUI Value Range

Actual Value Range

Unit MML Command NE

_LOC_SEPRAT_SWITCH, SRNSR_DSCR_PROPG_DELAY_SWITCH, SRNSR_DSCR_SEPRAT_DUR_SWITCH

LOC_SEPRAT_SWITCH, SRNSR_DSCR_PROPG_DELAY_SWITCH, SRNSR_DSCR_SEPRAT_DUR_SWITCH

FWDCONGBW

0 0~320000 0~320000 kbit/s ADD AAL2PATH(Optional)

RNC

BWDCONGBW

0 0~320000 0~320000 kbit/s ADD AAL2PATH(Optional)

RNC

The Default Value column is valid for only the optional parameters.The "-" symbol indicates no default value.


Ltd

6




7 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.55. Optional Feature Description of Huawei UMTS RAN11.0 V1.5


Ltd

1