Directed Retry Decision

Directed Retry Decision
http://localhost:7890/pages/GEB02251/02/GEB02251/02/resources/F...
WCDMA RAN

Feature Parameter Description Copyright Huawei Technologies Co., Ltd. 2012. 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 commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
1 de 51
22/07/2013 10:55 p.m.
2 de 51
22/07/2013 10:55 p.m.
Contents
1 Introduction
1.1 Scope 1.2 Intended Audience 1.3 Change History
2 Overview of DRD 3 RRC DRD

3.1 Overview 3.2 Procedure
4 Non-Periodic DRD
4.1 Overview 4.2 Blind-Handover-Based Non-Periodic DRD 4.2.1 Inter-Frequency DRD 4.2.2 Inter-Frequency DRD for Device Type Steering 4.2.3 Inter-Frequency DRD for Technological Satisfaction 4.2.4 Inter-Frequency DRD for Service Steering 4.2.5 Inter-Frequency DRD for Load Balancing 4.2.6 Inter-RAT DRD 4.3 Measurement-Based Non-Periodic DRD 4.3.1 Overview 4.3.2 MBDR Procedure
5 Periodic DRD
5.1 Overview 5.1.1 Switches for Periodic DRD 5.1.2 Conditions of Periodic DRD 5.2 Periodic DRD Procedure 5.2.1 Blind-Handover-based Periodic DRD 5.2.2 Measurement-Based Periodic DRD
6 Engineering Guidelines
6.1 WRFD-01061112 HSDPA DRD 6.1.1 When to Use 6.1.2 Information to Be Collected 6.1.3 Feature Deployment 6.2 WRFD-02040001 Intra System Direct Retry 6.3 WRFD-02040002 Inter System Direct Retry 6.4 WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup 6.5 WRFD-020402 Measurement Based Direct Retry
7 Parameters 8 Counters 9 Glossary 10 Reference Documents
3 de 51
22/07/2013 10:55 p.m.
1 Introduction
1.1 Scope
This document describes the Directed Retry Decision (DRD) feature. It covers both the RRC DRD and the RAB DRD, and also provides parameter descriptions for both functions.
1.2 Intended Audience

This document is intended for:
l Personnel l Personnel l Personnel
who are familiar with WCDMA basics who need to understand DRD who work with Huawei products
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:
l Feature l Editorial
change: refers to a change in the DRD feature.
change: refers to a change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issue is as follows:
l 02 l 01
(2012-07-20) (2012-04-30) A (2012-02-15)
l Draft
02 (2012-07-20)
This is the second commercial version of the document in RAN14.0. Compared with 01(2012-04-30), this issue incorporates the changes described in the following table. Change Type Feature change Change Description Parameter Change
Added the following parameter: Optimized the conditions for determinging a non-overloaded cell l HRetryTargCellLoadStusInd in periodic DRD. For details, see section 5.2.1 "BlindHandover-based Periodic DRD" and section 5.2.2 Measurement-Based Periodic DRD." The description about None. measurement-based non-periodic DRD (MBDR) is optimized. For details, see section 4.3.1"Overview" and MBDR Target Cell Selection in section 4.3.2 "MBDR Procedure." Added the description about how a None. UE selects the target cell when conditions 1 and 2 of power-based DRD for load balancing are met. For details, see "Power-Based DRD for Load Balancing" in section 4.2.5 "Inter-Frequency DRD for Load Balancing." Added the procedures for deploying None. features used in this document. For details, see 6 "Engineering Guidelines. "
Editorial change
01 (2012-04-30)
4 de 51 22/07/2013 10:55 p.m.
This is the first commercial version of the document in RAN14.0. Compared with Draft A (2012-02-15), this issue incorporates the changes described in the following table. Change Type Feature change Change Description Parameter Change
Added descriptions about how to Added the following parameter: determine the cell service priority l based on the uplink and downlink ReservedSwitch1: RESERVED_SWITCH_1_BIT16 l ReservedSwitch1: RESERVED_SWITCH_1_BIT17 service channels for UEs. For details, see section 4.2.4 InterFrequency DRD for Service Steering." None. None.
Editorial change
Draft A (2012-02-15)
This is the first draft of the document for RAN14.0. Compared with issue 01 (2011-04-30) of RAN13.0, this issue incorporates the changes described in the following table. Change Change Description Type Feature change Added a switch for enabling/disabling HSPA+ technological satisfaction in the DRD procedure. Parameter Change The added parameter is listed as follows:
l HSPAPlusSatisSwitch
Editorial The document description is change optimized to improve the readability.
None.
5 de 51
22/07/2013 10:55 p.m.
2 Overview of DRD
DRD is used to select a suitable cell for a UE to access. Different types of DRD can be adopted during different phases of service processing. In this way, the system capacity is maximized, and better services are provided. Figure 2-1 shows the different types of DRD. Figure 2-1 Types of DRD
As show in Figure 2-1, RRC DRD is performed during RRC setup phase, which starts with RRC connection request and ends with RRC connection setup complete. As show in Figure 2-1, RAB DRD is performed during the RAB phase, which starts with RAB setup processing and ends with RAB release. There are two types of RAB DRD:
l Non-periodic
DRD
Non-periodic DRD is available during RAB setup, RAB modification, or DCCC channel reconfiguration.
l Periodic
DRD.
Periodic DRD is available after RAB setup or after the bearer scheme is changed.
6 de 51
22/07/2013 10:55 p.m.
3 RRC DRD
3.1 Overview
The RNC preferably selects the serving cell for the UE to access, if the serving cell does not support SRB over HSPA when it is selected as the bearer scheme, or RRC connection setup fails in the serving cell, RRC DRD is performed and RNC instructs the UE to try to set up an RRC connection in a suitable inter-frequency neighboring cell on the same frequency band. The causes of RRC connection setup failure contain the call admission failure in the RNC side and the RL setup failure for the resources insufficient in the NodeB side. RRC DRD can make the UE preferably setting up RRC connection in the cell that supports the preferred type of channel for carrying SRBs and improving RRC connection setup success rate. The DR_ RRC_DRD_SWITCH sub-parameter of the DrSwitch parameter determines whether RRC DRD is enabled.
3.2 Procedure
Figure 3-1 The RRC DRD procedure
The RRC DRD procedure is as follows: 1. When receiving an RRC connection request, the RNC determines whether to process RRC connection setup in the serving cell based on the preferred type of channel for carrying SRBs. Details are as follows:
If
the serving cell supports the preferred type of channel for carrying SRBs, the RRC connection is set up in the serving cell. If the RRC connection setup fails in the serving cell, the RNC proceeds with the operation specified in step 2. the serving cell does not support the preferred type of channel for carrying SRBs, the RNC proceeds with the operation specified in step 2. The SrbChlType parameter specifies the preferred type of channel for carrying SRBs, DCH(Uplink_DCH, Downlink_DCH), HSDPA(Uplink _DCH, Downlink _HSDSCH), HSUPA(Uplink _EDCH, Downlink _DCH), or HSPA(Uplink EDCH, Downlink_HSDSCH) can be configured as the preferred type of channel for carrying SRBs. During RRC connection setup phase, this parameter is valid only when the SrbChlTypeRrcEffectFlag parameter is set to true.
If
7 de 51
22/07/2013 10:55 p.m.
2. Determine whether the serving cell has an inter-frequency co-coverage neighboring cell running on the same frequency band for blind handovers.
If
the serving cell has such neighboring cells and, a. Some of these cells support the preferred type of channel for carrying SRBs, the neighboring cells that support the preferred type of channel for carrying SRBs are DRD candidate cells. In this case, the RNC proceeds with the operation specified in step 3.
b. None of these neighboring cells supports the preferred type of channel for carrying SRBs, the RRC connection is set up in the serving cell by channel fallback. If the RRC connection setup fails, all inter-frequency neighboring cells running on the same frequency band for blind handovers are DRD candidate cells, and the RNC proceeds with the operation specified in step 3.
If
the serving cell does not have such a neighboring cell, the RRC connection is set up in the serving cell by channel fallback. If the RRC connection setup fails, the algorithm goes to step 5. Whether the neighboring cells support blind handovers is specified by the parameter BlindHoFlag.
3. The RNC generates a list of inter-frequency candidate cells that support DRD according to the following condition: (CPICH_EcNo)RACH > DRD_EcNOnbcell Here:
(CPICH_EcNo)RACH
is the cached CPICH Ec/N0 value included in the RACH measurement report. Note that this value
is for the current cell.

DRD_EcNOnbcell
is the DRD threshold (specified by the DRDEcN0Threshhold parameter of cell level) of the
neighboring cell. 4. The RNC selects a target cell from the candidate cells for UE access. If the candidate cell list contains more than one cell, the RNC selects the target cell randomly.
If
the UE is granted access, the RNC sends the UE an RRC Connection Setup message, containing the information about the target cell. The UE sends the RNC an RRC Connection Setup Complete message, indicating that UE access is complete.
If
the UE is not granted access, the RNC instructs the UE to try to access another cell in the candidate cell list until it successfully accesses a cell. If all access attempts fail, the algorithm goes to step 5.
5. If the function of RRC redirection after DRD failure is enabled, the RNC performs RRC redirection. Otherwise, the RRC connection setup fails. For details about RRC redirection after the DRD failure, see the Load Control Feature Parameter Description.
8 de 51
22/07/2013 10:55 p.m.
4 Non-Periodic DRD
This section covers the following features:
l WRFD-02040001 l WRFD-02040002 l WRFD-01061112 l WRFD-020402
Intra System Direct Retry Inter System Direct Retry HSDPA DRD
Measurement-based Direct Retry
4.1 Overview
Non-periodic DRD is used to select a suitable cell for UE access. It can be performed during a RAB setup, RAB modification, or DCCC channel reconfiguration. Non-periodic DRD can be measurement-based or blind-handover-based.
l
Blind-handover-based non-periodic DRD is used to select a suitable cell for a UE to access according to device type priority, HSPA+ technological satisfaction, service priority, and cell load. It enables the UE to be served with the best technological satisfaction and implements service steering and load balancing. Measurement-based non-periodic DRD (MBDR) is used to select a cell with qualifying signals for a UE to access according to the measurement result of signal quality. Compared with blind-handover-based non-periodic DRD, MBDR increases DRD success rate when the current cell and the DRD target cell cover different areas, however, increase the UE access delay.
Blind-handover-based non-periodic DRD and measurement-based non-periodic DRD (MBDR) cannot be used simultaneously. When MBDR is enabled, blind-handover-based non-periodic DRD is automatically disabled. When MBDR is disabled, the following parameters determine whether to enable blind-handover-based non-periodic DRD:
l For l For
a single service, blind-handover-based non-periodic DRD is enabled by the DR_RAB_SING_DRD_SWITCH sub-parameter of the DrSwitch parameter.
combined services, blind-handover-based non-periodic DRD is enabled by the DR_RAB_COMB_DRD_SWITCH sub-parameter of the DrSwitch parameter.
Note that if the measurement-based periodic DRD switch BasedOnMeasHRetryDRDSwitch is set to ON, blindhandover-based non-periodic DRD is also controlled by the BlindDrdExceptHRetrySwitch parameter. For example, if MBDR is disabled, the DR_RAB_SING_DRD_SWITCH sub-parameter of the DrSwitch parameter is set to ON, and the BasedOnMeasHRetryDRDSwitch parameter is set to ON, then blind-handover-based non-periodic DRD for a single service is enabled only if the BlindDrdExceptHRetrySwitch parameter is also set to ON. For detailed information about blind-handover-based non-periodic DRD, see section 4.2 "Blind-Handover-Based Non-Periodic DRD." For detailed information about measurement-based non-periodic DRD, see section 4.3 "Measurement-Based Non-Periodic DRD."
4.2 Blind-Handover-Based Non-Periodic DRD

Blind-handover-based non-periodic DRD consists of inter-frequency DRD (WRFD-02040001 Intra System Direct Retry) and inter-RAT DRD (WRFD-02040002 Inter System Direct Retry). For detailed information about inter-frequency DRD, see section 4.2.1 "Inter-Frequency DRD." For detailed information about inter-RAT DRD, see section 4.2.6 "Inter-RAT DRD."
4.2.1 Inter-Frequency DRD

Overview
An inter-frequency DRD procedure consists of DRD for device type steering, DRD for technological satisfaction, DRD for service steering, and DRD for load balancing. The RNC performs these DRDs in sequence. Table 4-1 describes the parameters that control the corresponding DRD functions. Table 4-1 Parameters that control the corresponding DRD functions DRD Function Description of Control Switches
DRD for device type steering DRD for device type steering is controlled by the parameter DPGDRDSwitch.
9 de 51
22/07/2013 10:55 p.m.
DRD for HSPA+ technological DRD for HSPA+ technological satisfaction is controlled by the parameter HSPAPlusSatisSwitch. satisfaction DRD for HSPA+ technological satisfaction is applicable only to UEs requesting HSPA+ services. DRD for service steering DRD for load balancing DRD for service steering is controlled by the parameter ServiceDiffDrdSwitch The availability of DRD for load balancing is specified by associated parameters as follows:
l
The availability of power-based DRD for load balancing for DCH services is specified by the LdbDRDSwitchDCH parameter. The availability of power-based DRD for load balancing for HSDPA services is specified by the LdbDRDSwitchHSDPA parameter. The availability of code-based DRD for load balancing is specified by the CodeBalancingDrdSwitch parameter.
If one of the DRD functions is disabled, the RNC does not consider the conditions based on which this type of DRD is performed. For example, if DRD for load balancing is disabled, the RNC does not consider the cell load when selecting a cell based on inter-frequency DRD.
Procedure
Figure 4-1 shows the algorithm procedure of inter-frequency DRD when one of DRD functions is available at least, that is the UE requesting HSPA+ Service or the UE requesting non-HSPA+ Service and one of DRD functions (DRD for device type steering, DRD for service steering and DRD for load balancing) enabled at least.
Note: DRD for HSPA+ technological satisfaction is applicable only to UEs requesting HSPA+ services.
Figure 4-1 Inter-Frequency DRD procedure when at least one DRD function is available
10 de 51
22/07/2013 10:55 p.m.
As show in Figure 4-1, when one of DRD functions is available at least, the inter-frequency DRD procedure is as follows: 1. The RNC determines the candidate cells to which blind handovers can be performed. Whether the neighboring cells support blind handovers is specified by the parameter BlindHoFlag. A candidate cell must meet the following conditions:
The The The
candidate cell supports the requested service. frequency of the candidate cell is in the band supported by the UE. current cell meets the quality requirements of inter-frequency DRD. For details, see chapter 3 "RRC DRD."
The current cell is also considered as a candidate cell if it supports the requested service.
2. The RNC selects a target cell from the candidate cells for UE access as follows: (a) When DRD for device type steering is enabled, the RNC selects a cell with the highest device type steering priority as described in section 4.2.2 "Inter-Frequency DRD for Device Type Steering." If multiple cells have the highest device type steering priority, proceed to step (b). Otherwise, proceed to step 3. (b) When DRD for HSPA+ technological satisfaction is enabled and the UE requests HSPA+ services. the RNC selects a cell with the highest technological satisfaction as described in section 4.2.3 "Inter-Frequency DRD for Technological Satisfaction." If multiple cells have the highest technological satisfaction, proceed to step (c). Otherwise, proceed to step 3.. (c) when DRD for service steering is enabled, the RNC selects a cell based on DRD for service steering as described in section 4.2.4 "Inter-Frequency DRD for Service Steering." If multiple cells have the highest service priority, proceed to step (d). Otherwise, proceed to step 3. (d) When DRD for load balancing is enabled, the RNC selects a cell based on DRD for load balancing as described in section4.2.5 Inter-Frequency DRD for Load Balancing".If multiple cells have the lightest load, the RNC selects the target cell randomly from the candidate cells of the lightest load. Otherwise, the RNC selects the target cell randomly from the candidate cells of the highest priority. Proceed to step 3.
When none of DRD functions is available, that is DRD for device type steering, DRD for service steering, DRD for HSPA+ technological satisfaction and DRD for load balancing are disabled, the RNC firstly instructs the UE to try to access the current cell. If the access fails, the RNC selects a target cell randomly from the candidate cells for the UE, proceed to step 3.
3. The call admission control (CAC) algorithm makes an admission decision based on the resource status of the cell.
If If
the admission attempt is successful, the RNC initiates an inter-frequency blind handover to the cell.
the admission attempt fails, the RNC removes the cell from the list of candidate cells and then checks whether all candidate cells have been tried. a. If there is any candidate cell that has not been tried, the algorithm goes back to step 2 to try this cell. b. If all candidate cells have been tried and
When
the service request is an HSPA one, the HSPA request is demoted to a DCH request and the algorithm goes back to step 1 to retry admission based on R99 service requests. the service request is a DCH one, the RNC initiates an inter-RAT DRD as described in section 4.2.6 "Inter-RAT
When
DRD."
4.2.2 Inter-Frequency DRD for Device Type Steering

Inter-Frequency DRD for device type steering belongs to the feature WRFD-020135 Intelligent Inter-Carrier Layered Management, which allows the RAN to intelligently distinguish between user equipment (UEs) and data cards in multi-carrier scenarios and set up services on different carriers based on terminal type priority. The availability of DRD for device type steering is specified by the DPGDRDSwitch parameter through MML command SET UDRD (RNC level switch) or ADD UCELLDRD (cell level switch). For details, see the Intelligent Inter-Carrier Layered Management on UEs and Data Cards Feature Parameter Description.
4.2.3 Inter-Frequency DRD for Technological Satisfaction

Overview
Technological satisfaction refers to determining whether a candidate cell satisfies the technical specifications for certain services, such as HSPA+ services. DRD for technological satisfaction is used to select a suitable cell and HSPA+ technologies for a UE based on the HSPA+ technologies supported by the UE and the attributes of the requested service, such as the bearer channel, service type, and service rate. DRD for HSPA+ technological satisfaction is applicable only to UEs requesting HSPA+ services. DRD for HSPA+ technological satisfaction consists of the following processes: 1. The RNC determines the HSPA+ technologies that can be configured on the UE, based on the HSPA+ technologies supported by the UE and attributes of the requested service, as described in the Radio Bearers Feature Parameter Description. 2. The RNC determines the HSPA+ technological satisfaction of each candidate cell based on the priorities of HSPA+ technologies as well as the HSPA+ technologies that can be both configured on the UE and supported by the cell. 3. The RNC selects a suitable cell for the UE based on the priority sequence of HSPA+ technologies. The RNC also
11 de 51
22/07/2013 10:55 p.m.
determines the HSPA+ technologies for the UE, which are the HSPA+ technologies that can be both configured on the UE and supported by the cell.
Priority Sequence of HSPA+ Technologies

The HSPAPlusSatisSwitch parameter specifies whether HSPA+ technological satisfaction is considered in the DRD procedure. When this parameter is set to ON, HSPA+ technological satisfaction is considered in the DRD procedure for the HSPA+ services. The technological satisfaction of a cell is determined by the HSPA+ technologies that can be both configured on the UE and supported by the cell. If these HSPA+ technologies have a high priority, the cell is considered to have a high technological satisfaction. The HSPA+ technologies comprise DC-HSDPA, enhanced layer 2 (L2), MIMO, 64QAM, DTX+DRX, E-DPCCH Boosting, UL 16QAM, and HS-SCCH Less Operation. The priority sequences of the technologies in a cell supporting HSPA+ are as follows: Table 4-2 Priority sequences of the technologies in a cell supporting HSPA+ Configuration of MIMO64QAMorDCHSDPASwitch DC-HSDPA Configuration of MIMOor64QAMSwitch MIMO Priority Sequence
DC-HSUPA+DC-HSDPA > DC-HSDPA +MIMO > DC-HSDPA (with downlink 64QAM activated in at least one cell) > MIMO+64QAM > DC-HSDPA (with downlink 16QAM activated in at least one cell) > MIMO+DL 16QAM > DL 64QAM > DL enhanced L2 > E-DPCCH Boosting > UL 16QAM > UL enhanced L2 > DTX+DRX > HS-SCCH Less Operation DC-HSUPA+DC-HSDPA > DC-HSDPA+MIMO > DC-HSDPA (with downlink 64QAM activated in at least one cell) > MIMO+64QAM > DC-HSDPA (with downlink 16QAM activated in at least one cell) > DL 64QAM > MIMO+DL 16QAM > DL enhanced L2 > E-DPCCH Boosting >UL 16QAM > UL enhanced L2 > DTX+DRX > HS-SCCH Less Operation DC-HSUPA+DC-HSDPA > DC-HSDPA+MIMO > MIMO+64QAM > DC-HSDPA (with downlink 64QAM activated in at least one cell) > MIMO+DL 16QAM > DL 64QAM > DC-HSDPA (with downlink 16QAM activated in at least one cell) > DL enhanced L2 > E-DPCCH Boosting > UL 16QAM > UL enhanced L2 > DTX+DRX > HS-SCCH Less Operation DC-HSUPA+DC-HSDPA > DC-HSDPA+MIMO > MIMO+64QAM > DC-HSDPA (with downlink 64QAM activated in at least one cell) > DL 64QAM > MIMO+DL 16QAM > DC-HSDPA (with downlink 16QAM activated in at least one cell) > DL enhanced L2 > E-DPCCH Boosting > UL 16QAM > UL enhanced L2 > DTX+DRX > HS-SCCH Less Operation
DC-HSDPA
64QAM
MIMO_64QAM
MIMO
MIMO_64QAM
64QAM
One or two DC-HSDPA cells may support MIMO, depending on the configuration of the DC-HSDPA cells. Gains also vary according to whether the DC-HSDPA or MIMO technique is used. DC-HSDPA UEs have higher throughput in low-traffic cells, whereas MIMO UEs have higher throughput in high-traffic cells. Therefore, when both DC-HSDPA and MIMO are available, Huawei introduces the DC-HSDPA and MIMO dynamic selection algorithm to determine what technique will carry incoming services according to the current number of HSDPA UEs and the downlink load status of the cell. This algorithm selects the optimal technique for carrying services, thereby achieving higher throughput and improving user experience. For details about DC-HSDPA and MIMO dynamic selection, see the MIMO Feature Parameter Description.
4.2.4 Inter-Frequency DRD for Service Steering

Overview
This section describes the feature WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup. If the UE requests a service in an area covered by multiple frequencies, the RNC selects the cell with the highest service priority for UE access, based on the RAB service type and the service priorities in the cells. The availability of DRD for service steering is specified by the ServiceDiffDrdSwitch parameter through MML command SET UDRD (RNC level switch) or ADD UCELLDRD (cell level switch).
12 de 51
22/07/2013 10:55 p.m.
Inter frequency DRD for service steering can also be called inter-frequency DRD for traffic steering.
Cell Service Priorities

A cell service priority is a service-specific priority for a cell among cells in the same coverage area. Cell service priorities help achieve traffic absorption in a hierarchical way. The service priorities of a cell are set as follows: 1. Run the ADD USPG command to add a service priority group, which is identified by SpgId. This group includes the service priorities of a cell. 2. Run the ADD UCELLSETUP, MOD UCELLSETUP, or ADD UCELLQUICKSETUP command to assign the SPG identity to the cell, that is, to set the service priorities for the cell.
The SPG to which a cell belongs is independent of DRD for service steering. For example, if the priority of a service is set to 0 in an SPG, this service cannot be established in the cells belonging to the SPG, regardless of whether DRD for service steering is activated or not.
When selecting a target cell for RAB processing, the RNC selects a cell with a high priority, that is, a cell that has a low service priority value. The service priority groups given in the following table are defined on the RNC. Cell SPG Service Service Service Identity Priority of R99 Priority of R99 Priority of RT Service NRT Service HSDPA Service A B 1 2 2 1 1 2 1 0 Service Priority Service Priority of of HSUPA Extension Services Service 1 0 0 0
As shown in the following figure, cell B has a higher service priority for the R99 RT service than cell A. If the UE requests an R99 RT service in cell A, the RNC preferably selects cell B for the UE to access. Figure 4-2 Example of DRD for service steering
If the requested service is a combined service, the RAB with the highest priority is used when a cell is selected for RAB processing. In addition, the target cell must support all of the necessary services. For details about the priority of a RAB, see the Load Control Feature Parameter Description.
The service priority of a DC-HSDPA /DC-HSUPA cell group is determined by the highest service priority of the two cells. The RNC determines the cell service priority based on the uplink and downlink service channels of the UE. The UE selects a cell with a higher service priority to access.
l For
UEs whose uplink and downlink services are both carried on HSPA channels:
When
ReservedSwitch1: RESERVED_SWITCH_1_BIT16 of the SET UCORRMALGOSWITCH command is set to 1, the RNC first considers the HSDPA service priority of candidate cells when determining the cell service priority. If the HSDPA service priority of candidate cells is the same, the RNC considers the HSUPA service priority. ReservedSwitch1: RESERVED_SWITCH_1_BIT16 of the SET UCORRMALGOSWITCH command is set to 0, the RNC first considers the HSUPA service priority of candidate cells when determining the cell service priority. If the HSUPA service priority of candidate cells is the same, the RNC considers the HSDPA service priority. UEs whose either uplink or downlink services (but not both) are carried on HSPA channels: ReservedSwitch1: RESERVED_SWITCH_1_BIT17 of the SET UCORRMALGOSWITCH command is set to 1,
When
l For
When
13 de 51
22/07/2013 10:55 p.m.
the RNC only considers the HSUPA or HSDPA service priority (but not both) when determining the cell service priority.
When
ReservedSwitch1: RESERVED_SWITCH_1_BIT17 of the SET UCORRMALGOSWITCH command is set to 0, the RNC first considers the HSUPA or HSDPA service priority (but not both) when determining the cell service priority. If the HSUPA or HSDPA service priority of candidate cells is the same, the RNC considers the R99 service priority. Among R99 services, RT services and NRT services are assigned different priorities.
4.2.5 Inter-Frequency DRD for Load Balancing

This section describes the feature WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup. If the UE requests a service setup or channel reconfiguration in an area covered by multiple frequencies, the RNC sets up the service on a carrier with a light load to balance out the load among the cells on the different frequencies. Inter-frequency DRD for load balancing also can be called inter-frequency DRD for load sharing.
"Inter-frequency DRD for load balancing" is called "DRD for load balancing" for short in this section. This section describes the procedure for performing DRD for load balancing when DRD for service steering is disabled.
Overview
DRD for load balancing concerns two resources: power and code. The availability of DRD for load balancing is specified by associated parameters as follows:
l The l The l The
availability of power-based DRD for load balancing for DCH services is specified by the LdbDRDSwitchDCH parameter. availability of power-based DRD for load balancing for HSDPA services is specified by the LdbDRDSwitchHSDPA parameter. availability of code-based DRD for load balancing is specified by the CodeBalancingDrdSwitch parameter.
It is recommended that only power-based DRD for load balancing or code-based DRD for load balancing be activated. When both are activated, power-based DRD for load balancing takes precedence over code-based DRD for load balancing. Code-based DRD for load balancing is applicable to only R99 services because HSDPA services use reserved codes.
Power-Based DRD for Load Balancing

For Non-DC-HSDPA/ Non-DC-HSUPA Services The following two algorithms are available for power-based load balancing. The algorithm used is specified by the LdbDRDchoice parameter.
l Algorithm 1:
DRD for load balancing is performed according to the cell measurement values for the DL non-HSDPA power and DL HS-DSCH GBP. The PowLoadDRDOptSwitch parameter has been added to specify whether DRD for load balancing considers the load caused by non-HSPA services and the GBP load caused by HSDPA services. When the PowLoadDRDOptSwitch parameter is set to OFF,
The
RNC sets up DCH services on a carrier with a light non-HSDPA power load to achieve load balancing among the cells at different frequencies. RNC sets up the HSDPA services on a carrier with a light HS-DSCH GBP load to achieve load balancing among the cells at different frequencies. RNC sets up DCH or HSDPA services on a carrier with a light (non-HSDPA power + HS-DSCH GBP) load to achieve load balancing among the cells at different frequencies.
The
When the PowLoadDRDOptSwitch parameter is set to ON,

The
l Algorithm 2: The
DRD for load balancing is performed according to the DCH equivalent number of users (ENU) and HSDPA user number. RNC sets up DCH services on a carrier with a light DCH ENU load to achieve load balancing among the cells at different frequencies. RNC sets up HSDPA services on a carrier with a light HSDPA user load to achieve load balancing among the cells at different frequencies.
The
Figure 4-3 shows the procedure for power-based DRD for load balancing. Figure 4-3 Procedure for power-based DRD for load balancing
14 de 51
22/07/2013 10:55 p.m.
The procedure for power-based DRD for load balancing is as follows: 1. The RNC determines the candidate cells. A candidate cell must meet the following conditions: (Note that target cell selection is also based on the resources of the DC-HSDPA cell group when the cell group is involved).
The The The The
candidate cell supports blind handover. Whether the neighboring cells support blind handovers is specified by the parameter BlindHoFlag. candidate cell supports the requested service. frequency of the candidate cell is in the band supported by the UE. current cell meets the quality requirements of inter-frequency DRD. For details, see chapter 3 "RRC DRD."
The current cell is also considered as a candidate cell if it supports the requested service.
2. If the current cell is a candidate cell, the RNC proceeds to step 3. Otherwise, the RNC selects the cell with lightest load from the candidate cell list and goes to step 5. 3. The RNC determines whether the current cell meets the following condition (condition 1). If the current cell meets condition 1, the load margin of the current cell is large and the UE accesses the current cell without attempting to access an inter-frequency neighboring cell.
For
algorithm 1, condition 1 is as follows:
a. For DCH services When the PowLoadDRDOptSwitch parameter is set to OFF, (ThdAMR,cutcell - Pnon-H,cutcell) > Thdnon-H When the PowLoadDRDOptSwitch parameter is set to ON, (Thdtotal,cutcell - Pnon-H,cutcell - PGBP,cutcell) > Thdnon-H Here,
ThdAMR,cutcell is specified by DlConvAMRThd of the current cell. Pnon-H,cutcell is the ratio of the non-HSDPA power load of the current cell to the total downlink load. Thdnon-H is specified by LdbDRDLoadRemainThdDCH.
Thdtotal.cutcell is the total power load threshold DlCellTotalThd. b. For HSDPA services When the PowLoadDRDOptSwitch parameter is set to OFF,
15 de 51
22/07/2013 10:55 p.m.
(Thdtotal,cutcell - PGBP,cutcell) > ThdH When the PowLoadDRDOptSwitch parameter is set to ON, (Thdtotal,cutcell - Pnon-H,cutcell - PGBP,cutcell) > ThdH Here,
Thdtotal,cutcell is specified by DlCellTotalThd of the current cell. PGBP,cutcell is the ratio of the HS-DSCH GBP load of the current cell to the total downlink load. ThdH is specified by LdbDRDLoadRemainThdHSDPA.
For
algorithm 2, condition 1 is as follows:
a. For DCH services (ThdAMR,cutcell - PD-enu,cutcell) > Thdnon-H Here, PD-enu,cutcell is the ratio of the DCH ENU load of the current cell to the total downlink ENU load. The total equivalent user number corresponding to the total downlink load is specified by DlTotalEqUserNum . b. For HSDPA services (ThdH-ue,cutcell - PH-ue,cutcell) / ThdH-ue,cutcell > ThdH Here,
ThdH-ue,cutcell is specified by MaxHsdpaUserNum of the current cell. PH-ue,cutcell is the total number of HSDPA users of the current cell.
If condition 1 is met, go to step 5. If condition 1 is not met, go to step 4. 4. The RNC selects a target cell for the UE to access. The RNC determines whether any inter-frequency neighboring cell meets the following condition (condition 2). If an interfrequency neighboring cell meets condition 2, the load margin of this inter-frequency neighboring cell is large and the UE attempts to access this inter-frequency neighboring cell.
l For
algorithm 1, condition 2 is as follows: DCH services
For
When the PowLoadDRDOptSwitch parameter is set to OFF, (ThdAMR,nbcell - Pnon-H,nbcell) - (ThdAMR,cutcell - Pnon-H,cutcell) > ThdD,loadoffset (Thdtotal,cutcell - Pload,cutcell) - (Thdtotal,nbcell - Pload,nbcell) < Thdtotal,loadoffset When the PowLoadDRDOptSwitch parameter is set to ON, (Thdtotal, nbcell - Pnon-H, nbcell - PGBP, nbcell) - (Thdtotal,cutcell - Pnon-H,cutcell - PGBP,cutcell) > ThdD,loadoffset Here, ThdAMR,nbcell is specified by DlConvAMRThd of the neighboring cell. Pnon-H,nbcell is the ratio of the non-HSDPA power load of the neighboring cell to the total downlink load. ThdD,loadoffset is specified by LdbDRDOffsetDCH.
Pload,cutcell is the ratio of the sum of the non-HSDPA power and the HS-DSCH GBP load of the current cell to the total
downlink load. The HS-DSCH GBP load of the current cell is the sum of the HSDPA service GBPs in the current cell. GBP for a HSDPA service is the minimum power required to ensure the GBR on HS-DSCH. If there is no data transmitting for a HSDPA service, the GBP for this HSDPA service is zero.
Thdtotal,nbcell is specified by DlCellTotalThd of the neighboring cell. Pload,nbcell is the ratio of the sum of the non-HSDPA power and the GBP load of the neighboring cell to the total downlink
load.
Thdtotal,loadoffset is specified by LdbDRDTotalPwrProThd.

For HSDPA services When the PowLoadDRDOptSwitch parameter is set to OFF, (Thdtotal,nbcell - PGBP,nbcell) - (Thdtotal,cutcell - PGBP,cutcell) > ThdH,loadoffset (Thdtotal,cutcell - Pload,cutcell) - (Thdtotal,nbcell - Pload,nbcell) < Thdtotal,loadoffset When the PowLoadDRDOptSwitch parameter is set to ON, (Thdtotal, nbcell - Pnon-H, nbcell - PGBP, nbcell) - (Thdtotal,cutcell - Pnon-H,cutcell - PGBP,cutcell) > ThdH,loadoffset Here,
PGBP,nbcell is the HS-DSCH GBP load of the neighboring cell. ThdH,loadoffset is specified by LdbDRDOffsetHSDPA.
l For
algorithm 2, condition 2 is as follows: DCH services
For
(ThdAMR,nbcell - PD-enu,nbcell) - (ThdAMR,cutcell - PD-enu,cutcell) > ThdD,loadoffset Here, PD-enu,nbcell is the ratio of the DCH ENU load of the neighboring cell to the total downlink ENU load.
For
HSDPA services
16 de 51
22/07/2013 10:55 p.m.
(ThdH-ue,nbcell - PH-ue,nbcell) / ThdH-ue,nbcell - (ThdH-ue,cutcell - PH-ue,cutcell) / ThdH-ue,cutcell > ThdH,loadoffset Here, ThdH-ue,nbcell is specified by MaxHsdpaUserNum of the neighboring cell. PH-ue,nbcell is the total number of HSDPA users of the neighboring cell. Then, the RNC selects the target cell as follows:
l If
there is only one inter-frequency neighboring cell that meets condition 2, the RNC selects this cell as the target cell. If there are multiple such cells:
For
DCH services
a. If algorithm 1 is used, When the PowLoadDRDOptSwitch parameter is set to OFF, the RNC selects the cell with the lightest non-HSDPA load as the target cell. When the PowLoadDRDOptSwitch parameter is set to ON, the RNC sets up DCH services on a carrier with a light (non-HSDPA power + HS-DSCH GBP) load to achieve load balancing among the cells at different frequencies. b. If algorithm 2 is used, the RNC selects the cell with the lightest DCH ENU load as the target cell.
For
HSDPA services
a. If algorithm 1 is used, When the PowLoadDRDOptSwitch parameter is set to OFF, the RNC selects the cell with the lightest load of HS-DSCH required power as the target cell. When the PowLoadDRDOptSwitch parameter is set to ON, the RNC sets up HSDPA services on a carrier with a light (non-HSDPA power + HS-DSCH GBP) load to achieve load balancing among the cells at different frequencies. b. If algorithm 2 is used, the RNC selects the cell with the lightest HSDPA user load as the target cell.
l If
there no cell meets condition 2, the RNC selects the current cell as the target cell. the admission attempt is successful, the RNC accepts the service request. the admission attempt fails, the RNC checks whether admission decisions have been made for all the candidate interfrequency neighboring cells.
If If
5. The CAC algorithm makes an admission decision based on the status of the target cell.
l If l If
there is any candidate cell that has not been tried, the algorithm goes back to step 2 to try this cell. admission decisions have been made for all the candidate cells:
a. When the service request is an HSPA one, the HSPA request falls back to a DCH one. Then, the algorithm goes back to step 1 to retry admission based on R99 service request. b. When the service request is a DCH one, the RNC initiates an inter-RAT DRD. For DC-HSDPA Services If multiple DC-HSDPA cell groups are available after DRD for technological satisfaction and DRD for service steering, the RNC performs DRD for load balancing. DRD for load balancing for DC-HSDPA services is similar to that of non-DC-HSDPA services. The difference is that the former considers cell groups (not individual cells), calculates their load factors, and finally selects a suitable cell group. After the RNC selects a suitable DC-HSDPA cell group, it determines the primary cell based on the technological satisfaction and service priorities of the two cells. If the two cells have the same technological satisfaction and service priority, the RNC performs the following operations:
l If l If
the uplink load balancing switch ULLdbDRDSwitchDcHSDPA is turned off, the RNC selects either of the two cells as the primary cell. this switch is turned on, the RNC determines the primary cell based on uplink load balancing.
The uplink load balancing mechanism is introduced to prevent RNC from selecting the same cell as the primary cell for multiple UEs requesting DC-HSDPA services. Uplink load balancing between the two cells is performed based on the uplink ENU. The procedure for uplink power-based DRD for load balancing is as follows: 6. If the current cell is not in the target DC-HSDPA cell group, the RNC selects a primary cell with a lighter load. 7. If the current cell is in the target DC-HSDPA cell group, the RNC checks whether the UL load margin of the current cell is higher than the value of ULLdbDRDLoadRemainThdDCHSDPA:
l If l If
the margin is higher, the RNC selects the current cell as the primary cell. the margin is not higher, the RNC calculates the difference between the UL load margin of the target cell and that of the current cell. Then,
If
the difference is greater than the value of ULLdbDRDOffsetDcHSDPA, the RNC selects the target cell as the primary cell. the RNC selects the current cell as the primary cell.
Otherwise,
For DC-HSUPA Services
17 de 51
22/07/2013 10:55 p.m.
The RNC determines only the primary carrier in the DC-HSUPA DRD procedure. The secondary carrier is automatically determined after the primary carrier is determined. The configuration of the primary DC-HSUPA carrier is the same as that of the primary DC-HSDPA carrier. Therefore, the DRD procedures of DC-HSUPA and DC-HSDPA are the same.
Code-Based DRD for Load Balancing

Code-based DRD for load balancing is similar to power-based DRD for load balancing. The difference is that the RNC considers code resources when selecting a target cell. The following figure shows the procedure for code-based DRD for load balancing. Figure 4-4 Procedure for code-based DRD for load balancing
The procedure is as follows: 1. The RNC determines whether the minimum remaining SF of the current cell is smaller than the minimum SF threshold of DRD for code balancing (CodeBalancingDrdMinSFThd).
l If l If
the minimum remaining SF is smaller than this threshold, the RNC requests access to the current cell. the minimum remaining SF is not smaller than this threshold, the RNC goes to the next step. For handovers, the minimum remaining SF indicates the minimum spreading factor available in a cell. For other services, the minimum remaining SF indicates the minimum spreading factor available in a cell based on the assumption that another handover reservation code (set by the DlHoCeCodeResvSf parameter) is allocated.
Calculating the minimum remaining SF considers HSDPA dynamic code allocation. The minimum code allocated to an HSDPA user is considered as occupied and the other allocated dynamic codes are considered as vacant when the minimum remaining SF is calculated. For details about HSDPA dynamic code allocation, see the HSDPA Feature Parameter Description. 2. The RNC determines whether the code load of the current cell is lower than the code occupation rate threshold of DRD for code balancing (CodeBalancingDrdCodeRateThd).
l If l If
the code load is lower than this threshold, the service tries to access the current cell. the code load is higher than or equal to this threshold, the RNC selects the cell as follows:
If
the minimum SF supported by the cell with the lightest code load is the same as that supported by the current cell, and the difference between the code resource occupancies of the two is greater than or equal to the value of DeltaCodeOccupiedRate, the RNC selects the cell with the lightest code load as the target cell. Otherwise, the RNC selects the current cell as the target cell.
If
the minimum SF supported by the cell with the lightest code load is smaller than the minimum SF supported by the current cell, the RNC selects the cell with the lightest code load as the target cell.
18 de 51
22/07/2013 10:55 p.m.
4.2.6 Inter-RAT DRD

Overview
When all admission attempts for inter-frequency DRD during RAB processing fail, the RNC determines whether to initiate an inter-RAT DRD. The DR_INTER_RAT_DRD_SWITCH sub-parameter of the DrSwitch parameter determines whether RRC DRD is enabled.
Procedure
The following figure shows the inter-RAT DRD procedure. Figure 4-5 Inter-RAT DRD procedure
The inter-RAT DRD procedure is as follows: 1. If the current cell is configured with any neighboring GSM cell suitable for blind handover and if the "service handover" IE in the RAB assignment signaling assigned by the CN is set to "handover to GSM should be performed" or "handover to GSM should not be performed", then the RNC performs step 2. Otherwise, the service request undergoes preemption and queuing as described in the Load Control Feature Parameter Description. Whether the neighboring cells support blind handovers is specified by the parameter BlindHoFlag. 2. The RNC generates a list of candidate inter-RAT cells that support DRD and fulfill the quality requirement. For details, see chapter 3 "RRC DRD." If the candidate cell list is empty, the service request undergoes preemption and queuing. 3. The RNC selects target GSM cells for the service request according to the blind handover priority. The blind handover priority of the cell is specified by the parameter BlindHOPrio. 4. If all admission attempts fail or the number of inter-RAT handover retries exceeds the value of DRMaxGSMNum , the service request undergoes preemption and queuing.
The inter-RAT DRD is not applicable to RABs of combined services, R99 PS services, and HSPA services.
Figure 4-6 shows the inter-RAT DRD signaling procedure. Figure 4-6 Inter-RAT DRD signaling procedure
19 de 51
22/07/2013 10:55 p.m.
1. The CN initiates establishment of the radio access bearer by a RAB Assignment Request message. 2. The RNC decides to perform the Relocation procedure (the UMTS-to-GSM direct retry). The RNC sends the CN a RAB Assignment Response message, containing the failure cause of "directed retry". The CN stops the RAB assignment procedure. 3. The RNC sends the CN a Relocation Required message, containing the request cause of "directed retry" and the information about the target GSM cell for the handover. Then, the RNC performs the Relocation procedure.
4.3 Measurement-Based Non-Periodic DRD

This section describes the feature WRFD-020402 measurement-based non-periodic DRD, or measurement-based direct retry (MBDR).
4.3.1 Overview
Measurement-based non-periodic DRD (MBDR) is a feature introduced in RAN12.0. It can increase the success rate of DRD, reduce the service drops caused by blind-handover-based non-periodic DRD. This feature involves inter-frequency DRD and inter-RAT DRD. When an RAB is set up, the DRD algorithm uses a blind handover to achieve load balancing and service steering. If the current cell and the DRD target cell cover different areas, the UE DRD may fail. With the MBDR function, the success rate of inter-frequency or inter-RAT DRD can be ensured even if the current cell and the DRD target cell cover different areas. The UE access delay, however, is increased. When an RRC connection is set up and MBDR is implemented, the RNC decides whether to establish the requested service in an inter-frequency or inter-RAT neighboring cell based on the current cell load and the type of service being established. If the RNC decides to establish the service in such a neighboring cell, the RNC sends an inter-frequency or inter-RAT measurement control message to the UE, instructing it to measure the signal quality of the neighboring cells. If the signal quality of a neighboring cell meets the requirements, the RNC establishes the service in that cell. Otherwise, the RNC attempts to establish the service in the current cell. Whether the MBDR algorithm is enabled is specified by the InterFreqActiveType or InterRatActiveType parameters.
l The
following service types support inter-frequency MBDR: AMR non-AMR R99 HSPA
CS CS PS PS
20 de 51
22/07/2013 10:55 p.m.
Only CS AMR services support inter-RAT MBDR.

l Inter-frequency
DRD for MBDR does not support inter-frequency DRD for device type steering, inter-frequency DRD for technological satisfaction, service steering, or load balancing. MBDR is activated for a specific service, the blind-handover-based non-periodic DRD for this service automatically becomes ineffective.
l If
l MBDR
does not support channel fallback, including HSUPA channel fallback and HSDPA channel fallback. Before activating MBDR, configure all intra-frequency cells served by a NodeB within an uplink resource group and a downlink resource group, respectively. If these cells are not within the same uplink or downlink resource group, HSUPA services may fail to be set up when multiple links are available. As a result, service setup fails because of channel fallback failure.
4.3.2 MBDR Procedure

Overview
The procedure for the inter-frequency MBDR algorithm is as follows: 1. After an RRC connection setup, the MBDR algorithm triggers the measurement of an inter-frequency MBDR cell if the corresponding MBDR algorithm switch is turned on and the current cell load exceeds the MBDR congestion decision threshold. 2. The RNC sends the UE an inter-frequency measurement control message, instructing the UE to measure the signal quality of the inter-frequency MBDR neighboring cells. If the signal quality of the inter-frequency MBDR cell meets the requirements, the RNC establishes services in this cell. If several inter-frequency MBDR cells qualify, the RNC prioritizes these cells and establishes services in the cell with the highest priority based on the value of the MBDRPrio parameter. 3. If services are established successfully, the RAB is set up successfully. Otherwise, the RNC attempts to establish services in the cell with the second highest priority.
MBDR neighboring cells are specified by the MBDRFlag parameter.
The procedure for the inter-RAT MBDR algorithm is similar to that for the inter-frequency MBDR algorithm. When the service type is CS AMR and the inter-frequency MBDR algorithm switch and inter-RAT MBDR algorithm switch are enabled, the UE selects the neighboring cell whose measurement report is reported first. If the first received measurement report contains the inter-frequency cell information, the UE selects the inter-frequency cell as the target cell. If the first received measurement report contains inter-RAT cell information, the UE selects the inter-RAT cell as the target cell.
Triggering MBDR
After an RRC connection setup, if the MBDR algorithm is enabled for the service type to which this RAB belongs, the RNC triggers MBDR when either of the following conditions is met:
l The
uplink admission control switch NBMUlCacAlgoSelSwitch is not set to ALGORITHM_OFF, and the cell is in the MBDR congestion state. That is: Uplink admission threshold MBDR congestion decision threshold Current cell load factor Uplink admission threshold
l The
downlink admission control switch NBMDlCacAlgoSelSwitch is not set to ALGORITHM_OFF, and the cell is in the MBDR congestion state. That is: Downlink admission threshold MBDR congestion decision threshold Current cell load factor Downlink admission threshold uplink admission threshold is specified by the UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, or UlNonCtrlThdForOther parameter. The downlink admission threshold is specified by the DlConvAMRThd, DlConvNonAMRThd, or DlOtherThd parameter. MBDR congestion decision threshold is specified by the InterFreqUlMbdrTrigThreshold, InterFreqDlMbdrTrigThreshold, InterRatUlMbdrTrigThreshold, or InterRatDlMbdrTrigThreshold parameter. current cell load factor indicates the ratio of the used cell capacity to the total cell capacity. The current cell load factor for both the uplink and downlink is calculated by the RNC according to the cell load measurement results reported by NodeB. For details, see the Load Control Feature Parameter Description.
In the above two formulas:

l The
l The l The
In the case of inter-RAT MBDR, the RNC triggers MBDR for only a certain percentage of UEs that meet the trigger conditions. This percentage is specified by the UserPercentage parameter.
MBDR Target Cell Selection

After MBDR is triggered, the RNC starts target cell selection. If the current cell has only one MBDR neighboring cell, the RNC sends the UE a measurement request, instructing the UE to measure the signal quality of the neighboring cell. If the signal quality meets the requirements, the RNC establishes services in that cell. If service establishment fails, the RNC establishes services in the current cell. If the current cell has more than one MBDR neighboring cell, the following procedure is triggered: 1. The RNC sends the UE a measurement request, instructing the UE to measure the signal quality of all the MBDR neighboring cells.
2. According to the measurement results, the RNC selects the neighboring cells that meet the requirements as target cells.
21 de 51
22/07/2013 10:55 p.m.
Note that a neighboring cell in the MBDR congestion state cannot be selected as a target cell.
If If
only one neighboring cell meets the requirements, the RNC establishes services in this neighboring cell.
more than one neighboring cell meets the requirements, the RNC prioritizes these cells based on the value of the MBDRPrio parameter and then establishes services in the cell with the highest priority. If these cells have the same priority, the RNC selects one of them with highest Ec/No or largest RSCP (based on the reported measurement control items) and then establishes services in it. The smaller value of MBDRPrio, the higher its priority.
3. The RNC attempts to set up a service in a neighboring cell with the highest service priority. If the service fails to be set up, the RNC will attempt to set up the service in other neighboring cells in descending order of priorities until the service is set up successfully or the number of service setup attempts exceeds the value specified by the MaxAttNum parameter. If the service fails to be set up in all neighboring cells, the RNC sets up the service in the current cell. If the service fails to be set up in the current cell, service setup fails. If the current service is HSPA service, the HSPA channel cannot be switched to a DCH for service setup. As a result, service setup fails.
Measurement Control Items

After MBDR is triggered, the RNC sends the UE a measurement control message, instructing the UE to measure the signal quality of the target cell. The UE reports the measurement results to the RNC. The parameters associated with measurement control items, for example, the measurement report mode and trigger threshold, can be configured by running the ADD UCELLMBDRINTERFREQ or ADD UCELLMBDRINTERRAT command. In the case of inter-frequency MBDR, you can:
l Set
the InterFreqReportMode parameter to PERIODICAL_REPORTING or EVENT_TRIGGER.
With
the setting PERIODICAL_REPORTING, the UE reports measurement results to the RNC at an interval specified by PrdReportInterval. Then, the RNC determines whether the signal quality of this inter-frequency cell meets the requirements according to the measurement results and the trigger conditions. the setting EVENT_TRIGGER, the UE sends the RNC a measurement report (indicating that the signal quality of the inter-frequency cell meets the inter-frequency handover requirements) when the signal quality of the inter-frequency cell is higher than the trigger threshold for the period specified by TrigTime2C. the InterFreqMeasQuantity parameter to Ec/No, RSCP, or BOTH. the setting Ec/No, the Ec/No value of the target cell must reach the inter-frequency handover trigger threshold, which is specified by the HOThdEcN0 parameter.
With
l Set
With
With With
the setting RSCP, the RSCP value of the target cell must reach the inter-frequency handover trigger threshold, which is specified by the HOThdRscp parameter. the setting BOTH, both the Ec/No and RSCP values of the target cell must reach the corresponding interfrequency handover trigger threshold.
Note: The InterFreqMeasQuantity parameter cannot be set to BOTH if the InterFreqReportMode parameter is set to EVENT_TRIGGER.
In the case of inter-RAT MBDR, you can set the InterRatReportMode parameter to PERIODICAL_REPORTING or EVENT_TRIGGER.
l With
the setting PERIODICAL_REPORTING, the UE reports measurement results to the RNC at an interval specified by InterRATPeriodReportInterval. Then, the RNC compares the measurement results with InterRATHOThd to determine whether the signal quality of this inter-RAT cell meets the requirements. the setting EVENT_TRIGGER, the UE sends the RNC a measurement report (indicating that the signal quality of the inter-RAT cell meets the inter-RAT handover requirements) when the signal quality of the inter-RAT cell is higher than the trigger threshold for the period specified by TrigTime3C.
l With
The measurement mechanism for inter-frequency or inter-RAT MBDR is the same as that for handover. For details about the measurement mechanism, see the Handover Feature Parameter Description.
22 de 51
22/07/2013 10:55 p.m.
5 Periodic DRD
5.1 Overview
Periodic DRD is used to select a suitable cell according to device type priority, HSPA/HSPA+ technological satisfaction, and service priority. It can be performed when the RNC determines that the UE can be served by a better HSPA/HSPA+ technology or when a neighboring cell has a higher device type priority or service priority than the current cell. After periodic DRD is triggered, it can be performed in either of the following ways:
l
Blind-handover-based periodic DRD: This mainly applies to the inter-frequency co-coverage scenario. It selects the target cell that supports blind handovers and does not consider the signal quality of the target cell. Measurement-based periodic DRD: This applies to both the inter-frequency different-coverage and the inter-frequency co-coverage scenarios. It selects the target cell according to the signal measurement results. Note that only measurement-based periodic DRD is based on cell service priority.
Blind-handover-based periodic DRD and measurement-based periodic DRD cannot work concurrently. When the latter is enabled, the former is automatically disabled.
5.1.1 Switches for Periodic DRD

The DR_RAB_SING_DRD_SWITCH and DR_RAB_COMB_DRD_SWITCH sub-parameters of the DrSwitch parameter determine whether to enable RAB DRD for a single service and a combined service, respectively. The BasedOnMeasHRetryDRDSwitch parameter further determines whether to enable blind-handover-based non-periodic DRD, blind-handover-based periodic DRD, or measurement-based periodic DRD. When the sub-parameter DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH is set to ON, the functions of the BasedOnMeasHRetryDRDSwitch parameter are as follows:
l When
the BasedOnMeasHRetryDRDSwitch parameter is set to ON: periodic DRD is enabled. periodic DRD is disabled. non-periodic DRD is controlled by the BlindDrdExceptHRetrySwitch parameter.
Measurement-based
Blind-handover-based Blind-handover-based l When
the BasedOnMeasHRetryDRDSwitch parameter is set to OFF: periodic DRD is disabled. periodic DRD is enabled if the ChannelRetryTimerLen parameter is not set to 0. non-periodic DRD is enabled.
Measurement-based
Blind-handover-based Blind-handover-based
5.1.2 Conditions of Periodic DRD

1. HSPA/HSPA+ technology satisfaction Periodic DRD is mainly triggered by the HSPA/HSPA+ retry. An HSPA/HSPA+ retry can be performed after a RAB setup or when the bearer scheme of a service is changed, for example, after RAB modification, a soft handover, hard handover, or cell change. After the RAB is set up or the bearer scheme of a service is changed, the RNC determines whether the UE can be served by a better HSPA/HSPA+ technology by considering the technological satisfaction. If a better HSPA/HSPA+ technology can be used, the HSPA/HSPA+ retry is performed periodically and consequently periodic DRD is triggered. In this way, a suitable cell can be selected to serve the UE with a better HSPA/HSPA+ technology. and the RNC can also try to make the UE be served a better HSPA/HSPA+ technology in current cell, which is not configured by some reason except for the capability of UE or cell when traffic is set up or reconfigured. In different situations, the HSPA/HSPA+ technologies that trigger HSPA/HSPA+ retry are different. The conditions under which an HSPA/HSPA+ technology can trigger HSPA/HSPA+ retry are as follows:
l The
HSPA+ technology is selected through RetryCapability parameter.
This condition does not apply to HSPA technologies.

l The
HSPA/HSPA+ technology is supported by periodic DRD.
Note that different types of periodic DRD support different HSPA/HSPA+ technologies.
Blind-handover-based Measurement-based
periodic DRD supports the following HSPA/HSPA+ technologies: HSUPA, HSDPA, 64QAM, MIMO, DC-HSUPA, DC-HSDPA, DC-HSDPA+MIMO, and E-DPCCH Boosting. periodic DRD supports the following HSPA/HSPA+ technologies: HSDPA, HSUPA, uplink enhanced L2, uplink 16QAM, downlink enhanced L2, CPC, 64QAM, DC-HSDPA, MIMO, DC-HSDPA+MIMO, and E-DPCCH Boosting.
2. Device type priority
23 de 51
22/07/2013 10:55 p.m.
If the parameter DPGDRDSwitch is set to ON, periodic DRD can also be triggered when a neighboring cell has a higher device type priority than the current cell, according to device type steering. If the parameter DPGDRDSwitch is set to OFF, device type priority is not considered during periodic DRD procedure. For details about the device type priority of the cell, see the Intelligent Inter-Carrier Layered Management on UEs and Data Cards Feature Parameter Description. 3. Service priority Measurement-based periodic DRD can also be triggered when a neighboring cell has a higher service priority than the current cell, according to service steering.
Measurement-based periodic DRD considers HSPA/HSPA+ technology satisfaction, device type priority, and service priority. Blind-handover-based periodic DRD considers only HSPA/HSPA+ technology satisfaction and device type priority.
Periodic DRD selects the target cell based on these priorities. The priority sequence is the same as that for blindhandover-based non-periodic DRD. For details, see section 4.2.1 "Inter-Frequency DRD."
5.2 Periodic DRD Procedure

5.2.1 Blind-Handover-based Periodic DRD
Blind-handover-based periodic DRD applies to the inter-frequency co-coverage scenarios. It is performed at regular intervals, which is called DRD period. The DRD period is specified by the ChannelRetryTimerLen parameter. If the ChannelRetryTimerLen parameter is set to 0, Blind-handover-based periodic DRD is disabled. Figure 5-1 shows the procedure for blind-handover-based periodic DRD. Figure 5-1 Procedure for blind-handover-based periodic DRD
The procedure for blind-handover-based periodic DRD is as follows: 1. The RNC decides whether there are candidate cells that the UE can attempt to access. The candidate cells are selected from the co-coverage neighboring cells of the current best cell. A candidate cell must meet the following conditions:
The The The
candidate cell supports blind handover. Whether the neighboring cells support blind handovers is specified by the parameter BlindHoFlag. frequency of the cell is in the band supported by the UE. cell supports the requested service.
When
HRetryTargCellLoadStusInd is set to OFF, the cell is not overloaded; when HRetryTargCellLoadStusInd is set to ON, the cell is not in the LDR state and is not overloaded.
When the LDR switch is turned on and the basic congestion of a cell is caused by insufficient resources, the cell enters the LDR state. For details, see section 8.1 "Basic Congestion Triggering" in the Load Control Feature Parameter Description.
The
technological satisfaction or device type priority of the cell is higher than that of the current cell.
If there are no such candidate target cells, blind-handover-based periodic DRD fails, and the RNC waits for the next DRD period. If there are any candidate target cells, the following steps are performed. 2. The RNC prioritizes the candidate target cells according to device type, technological satisfaction, service priority and load. The sorting method is the same as that for Blind-Handover-Based Non-Periodic DRD. For details, see section 4.2
24 de 51
22/07/2013 10:55 p.m.
"Blind-Handover-Based Non-Periodic DRD." 3. The RNC attempts to access the target cell with the highest specifications for UE access. 4. The CAC algorithm makes an admission decision based on the status of the target cell.
l If l If
the admission attempt is successful, the RNC accepts the service request. the admission attempt fails, the RNC removes the cell from the list of candidate cells and then checks whether all candidate cells have been tried.
If If
there are any candidate cells where no admission decision has been made, the algorithm goes back to step 3.
none of the candidate cells meet the requirements, blind-handover-based periodic DRD fails and the RNC waits for the next DRD period.
5.2.2 Measurement-Based Periodic DRD

In a multi-band network, cells that use different frequency bands have different coverage areas. When a UE needs to perform an inter-frequency handover in a multi-band network, it normally does not perform a blind handover, as the success rate of the blind handover is relatively low. Instead, the UE performs a handover decision according to the signal of each inter-frequency cell. Measurement-based periodic DRD is introduced to select a signal-qualified cell for the UE to access. Measurement-based periodic DRD applies to both the inter-frequency same-coverage and the inter-frequency differentcoverage scenarios and can increase the DRD success rate of both. Figure 5-2 shows the procedure for measurement-based periodic DRD. Figure 5-2 Procedure for measurement-based periodic DRD
The procedure for measurement-based periodic DRD is as follows: 1. Based on technological satisfaction and cell service priority, the RNC decides whether there are candidate cells that the UE can attempt to access. The candidate cells are selected from the best cell and its neighboring cells. A candidate cell must meet the following conditions:
The The The The
frequency of the cell is in the band supported by the UE. cell supports the requested service. DrdOrLdrFlag parameter of the cell is set to True, indicating that the cell can be measured.
technological satisfaction of the cell is higher than that of the current cell, or the service priority of the cell is higher than or equal to that of the current cell, or the device type priority of the cell is higher than that of current cell.
The current cell is also considered as a candidate when the technological satisfaction is taken into consideration.
For details about the technological satisfaction and service priority, see section 4.2 "Blind-Handover-Based Non-Periodic DRD." For details about the device type priority of the cell, see the Intelligent Inter-Carrier Layered Management on UEs and Data Cards Feature Parameter Description. If there are any candidate target cells, the following steps are performed. Otherwise, the measurement-based periodic DRD fails. 2. The RNC starts the timer for periodic DRD. The length of the timer is specified by the HRetryTimerLength parameter.
25 de 51
22/07/2013 10:55 p.m.
If
there is only one candidate target cell and it is the current cell, the UE retries higher HSPA+ technologies in the current cell when the timer expires. the RNC issues a measurement control message, requesting the UE to measure the signal quality of all candidate cells.
Otherwise,
3. The UE measures the RSCP and Ec/No of the candidate target cells and periodically reports the measurement results to the RNC. The reporting period is specified by the PrdReportInterval parameter. 4. Based on the received measurement results, the RNC selects the candidate target cells. A candidate target cell must meet the following requirements:
When
HRetryTargCellLoadStusInd is set to OFF, the cell is not overloaded; when HRetryTargCellLoadStusInd is set to ON, the cell is not in the LDR state and is not overloaded.
When the LDR switch is turned on and the basic congestion of a cell is caused by insufficient resources, the cell enters the LDR state. For details, see section 8.1 "Basic Congestion Triggering" in the Load Control Feature Parameter Description.
The The
measured RSCP is higher than the RSCP threshold specified by the TargetFreqThdRscp parameter. measured Ec/No is higher than the Ec/No threshold specified by the TargetFreqThdEcN0 parameter.
If there are not candidate target cells, measurement-based periodic DRD fails. In such a case, the RNC waits for the DRD timer to expire. If there are any candidate target cells, the following steps are performed. 5. The RNC prioritizes the candidate target cells according to device type, technological satisfaction, and service priority. 6. The RNC attempts to access the target cell with the highest specifications for UE access. 7. The CAC algorithm makes an admission decision based on the status of the candidate target cell.
l If l If
the admission attempt is successful, the RNC accepts the service request. the admission attempt fails, the RNC removes the cell from the list of candidate cells and then checks whether all candidate cells have been tried.
If If
there are any candidate cells where no admission decision has been made, the algorithm goes back to step 6.
none of the candidate target cells meets the requirements, measurement-based periodic DRD fails and the RNC waits for the DRD timer to expire.
If the measurement or retry fails during measurement-based periodic DRD, a failure penalty timer starts when the DRD timer expires. During the penalty time, the preceding procedure cannot be performed and the UE can attempt to access only the current cell. When the failure penalty timer expires, the RNC retries the preceding procedure on one candidate cell each time until measurement-based periodic DRD succeeds or there are no more available candidate cells. The measurement-based periodic DRD procedure ends. The length of the penalty timer is specified by multiplying the value of the HRetryTimerLength parameter by the value of the DrdFaiPenaltyPeriodNum parameter.
26 de 51
22/07/2013 10:55 p.m.
6 Engineering Guidelines
6.1 WRFD-01061112 HSDPA DRD
6.1.1 When to Use
None
6.1.2 Information to Be Collected

None
6.1.3 Feature Deployment

Requirements
l Dependencies
on Hardware on Other Features
This feature does not depend on the hardware.

l Dependencies
The following features must be configured before this feature is activated: WRFD-010610 HSDPA Introduction Package and WRFD-020400 DRD Introduction Package.
l License
The licenses "HSDPA DRD" on the RNC side have been activated. For details about the license items and how to activate the license, see License Management Feature Parameter Description.
Data Preparation
None
Feaute Activation
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration > Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC Parameters in Batches). In this step, set Direct retry switch to DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH according to the network plan.
The DR_RAB_SING_DRD_SWITCH and the DR_RAB_COMB_DRD_SWITCH can be turned on at the same time according to the network plan.
Activation Check
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to check whether DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH is set to ON. Expected result: The value of DR_RAB_SING_DRD_SWITCH or DR_RAB_COMB_DRD_SWITCH is ON. 2. Run the BSC6900 MML command LST UINTERFREQNCELL to query the inter-frequency neighboring cells of cell 1 and whether Blind handover flag is set to TRUE. If Blind handover flag is set to FALSE, run the BSC6900 MML command MOD UINTERFREQNCELL. In this step, set Blind Handover Flag of cell 2 (inter-frequency neighboring cell of cell 1) to TRUE. If Blind handover flag is set to TRUE, go to 3 3. Run the BSC6900 MML command SET UFRCCHLTYPEPARA. In this step, set DL BE traffic threshold on HSDPA to an appropriate value. 4. Run the BSC6900 MML command MOD UCELLCAC. In this step, set Maximum HSDPA user number of cell 1 to 0. 5. Run the BSC6900 MML command MOD UCELLALGOSWITCH. In this step, set HSDPA_UU_ADCTRL(HSDPA UU Load Admission Control Algorithm) to Cell CAC algorithm switch.
6. Enable the UE in cell 1 to originate a PS FTP download service. The value of Maximum HSDPA user number in cell 1 is 0; therefore, the UE is handed over to cell 2 by using directed retry. The Uu message tracing or the UE CDT tracing shows that the RRC_RB_RECFG/RRC_RB_SETUP message is sent to the UE in cell 1 and the RRC_RB_RECFG_CMP/RRC_RB_SETUP_CMP message is sent to the RNC in cell 2.
This feature also supports the following scenario: If a UE in an R99 cell (cell 1) originates HSDPA streaming services or BE services, the UE can camp on an HSDPA cell (cell 2) through directed retry. In this scenario, cell 2 is the inter-frequency neighboring cell for blind handover of cell 1 and admission to cell 2 is allowed.
Feature Deactivation
The feature does not need to be deactivated.
Example
//Activating HSDPA DRD
27 de 51
22/07/2013 10:55 p.m.
SET UCORRMALGOSWITCH: DrSwitch= DR_RAB_SING_DRD_SWITCH-1; SET UCORRMALGOSWITCH: DrSwitch= DR_RAB_COMB_DRD_SWITCH-1; //Verifying HSDPA DRD MOD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=2, NCellId=2, BlindHoFlag=TRUE; SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D384; MOD UCELLCAC: CellId=1, MaxHsdpaUserNum=0; MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1;
6.2 WRFD-02040001 Intra System Direct Retry

Requirements
l Dependencies

l Dependencies
The feature WRFD-020400 DRD Introduction Package must be configured before this feature is activated.
l License
The licenses "Intra System Direct Retry" on the RNC side have been activated. For details about the license items and how to activate the license, see License Management Feature Parameter Description.
Data Preparation
None
Feaure Activation
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration > Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC Parameters in Batches). In this step, set Direct retry switch to DR_RRC_DRD_SWITCH, DR_RAB_SING_DRD_SWITCH, and DR_RAB_COMB_DRD_SWITCH.
2. Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In this step, turn on the RNC-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, Measurement-Based DRD Switch, and Device Type Steering DRD Switch. 3. Optional: Run the BSC6900 MML command ADD UCELLDRD (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented DRD Algorithm Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, turn on the cell-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, and Device Type Steering DRD Switch.
If
a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter settings take effect. Therefore, do not modify the parameters to default values when you are configuring the cell-level parameters. system direct retry does not select the inter-frequency neighboring cell under the DRNC as the target cell. DRD and redirection at RRC connection setup do not select the inter-frequency neighboring cell that uses a different frequency band from the cell where the RRC connection is to access.
Intra
Activation Check
1. Method 1: Verifying this feature during RRC connection setup
Start The
Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive service.
UE sends an RRC_RRC_CONNECT_REQ message from cell 1 to the BSC6900. The BSC6900 sends the UE an RRC_RRC_CONN_SETUP message containing the scrambling code of cell 2. UE sends an RRC_RRC_CONNECT_SETUP_CMP message from cell 2 to the BSC6900. This indicates that this feature has been activated. Uu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive service.
The
2. Method 2: Verifying this feature during radio bearer (RB) setup

Start The
BSC6900 sends an RRC_RB_SETUP message from cell 1 to the UE. The UE sends an RRC_RB_SETUP_CMP message from cell 2 to the BSC6900. If the service is set up successfully in cell 2 and the data transmission is normal, this feature has been activated.
1. Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches) to turn off the RNC-level switches.
28 de 51
22/07/2013 10:55 p.m.
2. Optional: Run the BSC6900 MML command MOD UCELLDRD (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented DRD Algorithm Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches) to turn off the cell-level switches.
Example
//Activating Intra System Direct Retry SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1&DR_RAB_SING_DRD_SWITCH1&DR_RAB_COMB_DRD_SWITCH-1; SET UDRD: ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, BasedOnMeasHRetryDRDSwitch=ON, DPGDRDSwitch=ON; ADD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, DPGDRDSwitch=ON; //Deactivating Intra System Direct Retry SET UDRD: ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, BasedOnMeasHRetryDRDSwitch=OFF, DPGDRDSwitch=OFF; MOD UCELLDRD: CellId=10, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF
6.3 WRFD-02040002 Inter System Direct Retry

Requirements
l Dependencies

l Dependencies
l License
The licenses "Intra System Direct Retry" on the RNC side have been activated. For details about the license items and how to activate the license, see License Management Feature Parameter Description.
Data Preparation
None
Feature Activation
1. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration > Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC Parameters in Batches). In this step, set Direct retry switch to DR_RAB_SING_DRD_SWITCH, DR_RAB_COMB_DRD_SWITCH, and DR_INTER_RAT_DRD_SWITCH.
2. Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In this step, set the RNC-level parameter Max inter-RAT direct retry number to a value other than zero, and turn on the following RNC-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, Measurement-Based DRD Switch, and Device Type Steering DRD Switch. 3. Optional: Run the BSC6900 MML command MOD UCELLDRD (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented DRD Algorithm Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set the cell-level parameter Max inter-RAT direct retry number to a value other than zero. Turn on the following cell-level switches: Service Steering DRD Switch, Load balance DRD switch for DCH, Load balance DRD switch for HSDPA, Code Balancing DRD Switch, Uplink load balance DRD Switch for DC-HSDPA, and Device Type Steering DRD Switch.
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter settings take effect. Therefore, do not modify the parameters to default values when you are configuring the cell-level parameters.
Activation Check
1. Start Iu interface tracing on the BSC6900 LMT. Use a UE to initiate a PS interactive service. 2. In the Iu Interface Trace dialog box, view the following procedure:
The
core network (CN) sends a RAB_ASSIGNMENT_REQ message to the BSC6900.
29 de 51
22/07/2013 10:55 p.m.
The The
BSC6900 responds to the CN with a RAB_ASSIGNMENT_RSP message containing the cause value "direct retry." BSC6900 sends the CN a RELOCATION REQUIRED message containing the cause value "direct retry."
1. Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In this step, set Max Inter-RAT direct retry number to 0. Turn off the RNC-level switches. 2. Optional: Run the BSC6900 MML command MOD UCELLDRD (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented DRD Algorithm Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set Max inter-RAT direct retry number to 0. Turn off the cell-level switches.
Example
//Activating Inter System Direct Retry SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1&DR_RAB_COMB_DRD_SWITCH1&DR_INTER_RAT_DRD_SWITCH-1; SET UDRD: DRMaxGSMNum=3, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, BasedOnMeasHRetryDRDSwitch=ON, DPGDRDSwitch=ON; ADD UCELLDRD: CellId=11, DRMaxGSMNum=3, ServiceDiffDrdSwitch=ON, LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, CodeBalancingDrdSwitch=ON, ULLdbDRDSwitchDcHSDPA=ON, DPGDRDSwitch=ON; //Deactivating Inter System Direct Retry SET UDRD: DRMaxGSMNum=0, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, BasedOnMeasHRetryDRDSwitch=OFF, DPGDRDSwitch=OFF; MOD UCELLDRD: CellId=11, DRMaxGSMNum=0, ServiceDiffDrdSwitch=OFF, LdbDRDSwitchDCH=OFF, LdbDRDSwitchHSDPA=OFF, CodeBalancingDrdSwitch=OFF, ULLdbDRDSwitchDcHSDPA=OFF, DPGDRDSwitch=OFF;
6.4 WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup
Requirements
l Dependencies

l Dependencies
l License
This feature is not under license control.
Data Preparation
None
Feauture Activation
1. Run the BSC6900 MML command ADD UINTERFREQNCELL (CME single configuration: UMTS Cell Configuration Express > Neighboring Cell > Inter-frequency Neighboring Cell; CME batch modification center: not supported). In this step, add an inter-frequency cell by setting the related parameters according to the network plan. 2. Run the BSC6900 MML command ADD USPG (CME single configuration: UMTS Global Configuration Express > Radio Basic Data Configuration > Service Priority Group; CME batch modification center: not supported). In this step, add a service priority group and set the service priority of each type of service according to the network plan. 3. Run the BSC6900 MML command MOD UCELL (CME single configuration: UMTS Cell Configuration Express > Cell Basic Information > Cell Basic Information; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set the cell service priority by setting the related parameters according to the network plan. 4. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration > Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC Parameters in Batches). In this step, set Direct Retry Switch to DR_RAB_SING_DRD_SWITCH.
5. Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In this step, turn on Service differential drd switch and Measurement-Based DRD Switch.
Activation Check
30 de 51
22/07/2013 10:55 p.m.
1. Start Uu interface tracing on the BSC6900 LMT. 2. Use a UE in a cell to initiate a PS interactive service. This cell carries low-priority services. The target inter-frequency neighboring cell has light load and carries high-priority services. In the Uu Interface Trace dialog box, view the following procedure:
After The The The
the UE in a cell sends an RRC_RB_SETUP_CMP message, the BSC6900 sends an RRC_PH_CH_RECFG message to the UE. UE responds with an RRC_PH_CH_RECFG_CMP message. BSC6900 enters the compressed mode.
UE in periodical mode sends an RRC_MEAS_CTRL message to the BSC6900 to measure the signal quality of the target cell. BSC6900 sends the UE an RRC_RB_RECFG message containing the primary scrambling code and frequency of the inter-frequency neighboring cell. UE sends an RRC_RB_RECFG_CMP message from the inter-frequency neighboring cell.
The The
1. Run the BSC6900 MML command SET UDRD (CME single configuration: UMTS Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In this step, turn off Service differential drd switch and Measurement-Based DRD Switch.
Example
//Activating Service Steering and Load Sharing During RAB Setup ADD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=1, NCellId=2, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, NPrioFlag=FALSE, DrdOrLdrFlag=TRUE, InterNCellQualReqFlag=FALSE; ADD USPG: SpgId=1, PriorityServiceForR99RT=2, PriorityServiceForR99NRT=2, PriorityServiceForHSDPA=2, PriorityServiceForHSUPA=2, PriorityServiceForExtRab=1; ADD USPG: SpgId=2, PriorityServiceForR99RT=1, PriorityServiceForR99NRT=1, PriorityServiceForHSDPA=1, PriorityServiceForHSUPA=1, PriorityServiceForExtRab=1; MOD UCELL: CellId=1, SpgId=1; MOD UCELL: CellId=2, SpgId=2; SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1; SET UDRD: ServiceDiffDrdSwitch=ON, BasedOnMeasHRetryDRDSwitch=ON; //Deactivating Service Steering and Load Sharing During RAB Setup SET UDRD: ServiceDiffDrdSwitch=OFF, BasedOnMeasHRetryDRDSwitch=OFF;
6.5 WRFD-020402 Measurement Based Direct Retry

Requirements
l Dependencies
None
l Dependencies
The feature WRFD-020400 DRD Introduction Package has been configured before this feature is activated.
l License
The licenses "Measurement Based Direct Retry Function" on the RNC side have been activated. For details about the license items and how to activate the license, see License Management Feature Parameter Description.
Data Preparation
None
Feature Activation
1. Run the BSC6900 MML command ADD UCELLMBDRINTERFREQ (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented Inter-frequency Measurement Parameters for MBDR Algorithm; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set MBDR Switch, Inter-freq Measure Quantity, and other parameters related to MBDR inter-frequency measurements.
2. Run the BSC6900 MML command SET UNBMPARA (CME single configuration: UMTS Radio Global Configuration Express > NodeB Management Configuration > Algorithm Parameters Related to NodeB Configuration and Maintenance; CME batch modification center: not supported). In this step, select PERFENH_MBDR_LOADCOND_OPT_SWITCH under Performance Enhancement Switch. 3. Run the BSC6900 MML command SET UCORRMPARA (CME single configuration: UMTS Radio Global Configuration
31 de 51
22/07/2013 10:55 p.m.
Express > Connection_Oriented RRM Switch Configuration > the connection-oriented algorithm parameters of an RNC; CME batch modification center: Modifying RNC Parameters in Batches). In this step, select PERFENH_MBDR_TARCELLSEL_OPT_SWITCH under Performance Enhancement Switch, and preferentially select a cell with the optimum signal quality as the target cell.
When selecting the target cell after the MBDR algorithm is enabled, sort the candidate cells based on Inter-freq Measure Quantity of MBDR (by running the ADD UCELLMBDRINTERFREQ (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented Inter-frequency Measurement Parameters for MBDR Algorithm ; CME batch modification center: Modifying UMTS Cell Parameters in Batches) command), and select a cell with the optimum signal quality as the target cell.
4. Run the BSC6900 MML command ADD UCELLMBDRINTERRAT (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented Inter-RAT Measurement Parameters for MBDR Algorithm; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set MBDR switch in the parameters related to MBDR inter-RAT measurements. 5. Run the BSC6900 MML command ADD UINTERFREQNCELL (CME single configuration: UMTS Cell Configuration Express > Neighboring Cell > Inter-frequency Neighboring Cell; CME batch modification center: not supported). In this step, set Flag of MBDR Cell to TRUE(send), and set MBDR Cell Priority based on the network plan.
Activation Check
1. Congestion may occur when a large number of UEs access a cell. If a handover based on inter-frequency measurements is used to achieve load reshuffling (LDR), you can view the inter-frequency measurement control information on the Uu interface. After a UE sends the inter-frequency measurement report, the UE will be handed over to another cell.
1. Run the BSC6900 MML command MOD UCELLMBDRINTERFREQ (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented Inter-frequency Measurement Parameters for MBDR Algorithm; CME batch modification center: Modifying UMTS Cell Parameters in Batches) to clear the MBDR Switch check box.
Example
//Activating the feature Measurement-based Direct Retry //Enabling the MBDR algorithm ADD UCELLMBDRINTERFREQ: CellId=1, InterFreqActiveType=CSAMR_INTERFREQ-1&CSNONAMR_INTERFREQ1;&PSR99_INTERFREQ-1;&PSHSPA_INTERFREQ-1; InterFreqReportMode=EVENT_TRIGGER; SET UNBMPARA: PerfEnhanceSwitch=PERFENH_MBDR_LOADCOND_OPT_SWITCH-1; SET UCORRMPARA: PerfEnhanceSwitch=PERFENH_MBDR_TARCELLSEL_OPT_SWITCH-1; //Setting the parameters related to cell-level MBDR inter-RAT measurements ADD UCELLMBDRINTERRAT: CellId=1, InterRatActiveType=CSAMR_INTERRAT-1; //Setting the MBDR cell flag of the inter-frequency neighboring cell and the MBDR cell priority ADD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=2, NCellId=2, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE, NPrioFlag=FALSE, MBDRFlag=TRUE, MBDRPrio=2, InterNCellQualReqFlag=FALSE; //Deactivating the feature Measurement-based Direct Retry //Disabling the MBDR algorithm MOD UCELLMBDRINTERFREQ: CellId=1,InterFreqActiveType=CSAMR_INTERFREQ-0&CSNONAMR_INTERFREQ0;&PSR99_INTERFREQ-0;&PSHSPA_INTERFREQ-0;
32 de 51
22/07/2013 10:55 p.m.
7 Parameters
Table 7-1 Parameter description Parameter ID BasedOnMeasHRetryDRDSwitch NE MML Command Feature ID Feature Name Description
BSC6900SET UDRD
WRFD-02040002 Inter System Direct Retry WRFD-020402 Measurement WRFD-02040004 Based Direct Retry
Meaning:Controls the validi GUI Value Range:OFF, ON
Actual Value Range:OFF, O Unit:None
Traffic Steering Default Value:OFF and Load Sharing During RAB Setup BlindDrdExceptHRetrySwitch BSC6900ADD UCELLMCDRD MOD UCELLMCDRD WRFD-02040002Inter System Direct Retry
Meaning:When the measur
If this parameter is set to "O
If this switch is set to "OFF GUI Value Range:OFF, ON
Actual Value Range:OFF, O Unit:None Default Value:ON BlindHoFlag BSC6900ADD U2GNCELL MOD U2GNCELL WRFD-020103 WRFD-021200 Inter Frequency Load Balance
Meaning:Whether to perfor
The value FALSE indicates HCS (Hierarchical GUI Value Range:FALSE, T Cell Structure)
Actual Value Range:FALSE Unit:None Default Value:False BlindHoFlag BSC6900ADD UINTERFREQNCELL MOD UINTERFREQNCELL WRFD-020103 WRFD-021200 Inter Frequency Load Balance
Meaning:Whether to perfor
The value FALSE indicates HCS (Hierarchical GUI Value Range:FALSE, T Cell Structure)
Actual Value Range:FALSE Unit:None Default Value:False BlindHOPrio BSC6900ADD U2GNCELL MOD U2GNCELL WRFD-020310
3G/2G Common Meaning:Priority of the neig Load Management The value 0 represents the GUI Value Range:0~30 Actual Value Range:0~30 Unit:None Default Value:None
ChannelRetryTimerLen
BSC6900SET UCOIFTIMER
WRFD-01061008 Interactive and Background WRFD-01061112 Traffic Class on WRFD-01061206 HSDPA WRFD-01061403 HSDPA DRD WRFD-010630 WRFD-010632 Interactive and Background Traffic Class on HSUPA
Meaning:This parameter sp GUI Value Range:0~180 Actual Value Range:0~180 Unit:s Default Value:5
33 de 51
22/07/2013 10:55 p.m.
Parameter ID
NE
MML Command
Feature ID WRFD-010636 WRFD-010652 WRFD-010683 WRFD-010684 WRFD-010685 WRFD-010686 WRFD-010687 WRFD-021101
Feature Name HSUPA 2ms TTI Streaming Traffic Class on HSDPA Streaming Traffic Class on HSUPA SRB over HSUPA SRB over HSDPA Downlink 64QAM 2x2 MIMO Downlink Enhanced L2 CPC - DTX / DRX CPC - HS-SCCH less operation Dynamic Channel Configuration Control (DCCC)
Description
CodeBalancingDrdCodeRateThd
BSC6900ADD UCELLDRD MOD UCELLDRD
WRFD-020400
DRD Introduction Meaning:One of the triggeri Package GUI Value Range:0~100 Actual Value Range:0~100 Unit:% Default Value:13
CodeBalancingDrdMinSFThd
WRFD-020400
DRD Introduction Meaning:One of the triggeri Package GUI Value Range:SF4, SF8
Actual Value Range:SF4, S Unit:None Default Value:SF8 CodeBalancingDrdSwitch BSC6900ADD UCELLDRD MOD UCELLDRD WRFD-020400
DRD Introduction Meaning:Whether to activa Package When this switch is turned When this switch is turned
GUI Value Range:ON, OFF
Actual Value Range:ON, OF Unit:None Default Value:OFF DeltaCodeOccupiedRate BSC6900SET UDRD WRFD-020400
DRD Introduction Meaning:Threshold for chec Package Code resource usage of th GUI Value Range:0~100 Actual Value Range:0~100 Unit:% Default Value:7
DlCellTotalThd
BSC6900ADD UCELLCAC MOD UCELLCAC
WRFD-020101
Admission Control Meaning:Admission thresho GUI Value Range:0~100 Actual Value Range:0~1 Unit:%
34 de 51
22/07/2013 10:55 p.m.
Parameter ID
NE
MML Command
Feature ID
Feature Name
Description Default Value:90
DlConvAMRThd
WRFD-020101
Admission Control Meaning:1. The percentage
2. The DL load factor thres GUI Value Range:0~100 Actual Value Range:0~1 Unit:% Default Value:80
DlConvNonAMRThd
WRFD-020101
DlHoCeCodeResvSf
WRFD-020101
Admission Control Meaning:This parameter de
GUI Value Range:SF4(SF4
Actual Value Range:SF4, S Unit:None Default Value:SF32(SF32) DlOtherThd BSC6900ADD UCELLCAC MOD UCELLCAC WRFD-020101
DlTotalEqUserNum
WRFD-020101
Admission Control Meaning:When the ENU-ba GUI Value Range:1~200 Actual Value Range:1~200 Unit:None Default Value:80
DPGDRDSwitch
WRFD-020135
Intelligent InterCarrier UE Layered Management
Meaning:Whether to activa When this switch is turned When this switch is turned
GUI Value Range:ON, OFF
Actual Value Range:ON, OF Unit:None Default Value:OFF DRDEcN0Threshhold BSC6900ADD UINTERFREQNCELL MOD UINTERFREQNCELL WRFD-02040001Intra System Direct Retry
Meaning:DRD Ec/No thresh GUI Value Range:-24~0 Actual Value Range:-24~0 Unit:dB
35 de 51
22/07/2013 10:55 p.m.
Parameter ID
NE
MML Command
Feature ID
Feature Name
Description Default Value:-18
DrdFaiPenaltyPeriodNum
BSC6900ADD UCELLMCDRD MOD UCELLMCDRD
WRFD-02040002Inter System Direct Retry
Meaning:Number of retry pe
GUI Value Range:1~65535
Actual Value Range:1~6553 Unit:None Default Value:10 DrdOrLdrFlag BSC6900ADD UINTERFREQNCELL MOD UINTERFREQNCELL WRFD-020160 Enhanced Multiband Management
Meaning:Specify the flags o
GUI Value Range:FALSE(D
Actual Value Range:FALSE Unit:None
Default Value:FALSE(Do no DRMaxGSMNum BSC6900ADD UCELLDRD MOD UCELLDRD WRFD-02040002Inter System Direct Retry Meaning:Maximum number GUI Value Range:0~5 Actual Value Range:0~5 Unit:None Default Value:2 DrSwitch BSC6900SET WRFD-01061112 HSDPA DRD UCORRMALGOSWITCH WRFD-020120 Service Steering and Load Sharing WRFD-02040001 in RRC WRFD-02040002 Connection Setup WRFD-02040003 Intra System Direct Retry WRFD-02040004 Inter System Direct Retry Inter System Redirect Traffic Steering and Load Sharing During RAB Setup HOThdEcN0 BSC6900ADD WRFD-020402 UCELLMBDRINTERFREQ MOD UCELLMBDRINTERFREQ Measurement Based Direct Retry
Meaning:Direct retry switch
1) DR_RRC_DRD_SWITC
2) DR_RAB_SING_DRD_S
3) DR_RAB_COMB_DRD_
4) DR_INTER_RAT_DRD_S
GUI Value Range:DR_RRC
Actual Value Range:DR_RR Unit:None
Default Value:DR_RRC_DR
Meaning:Threshold of signa If the mode is set to event
If the mode is set to period GUI Value Range:-24~0 Actual Value Range:-24~0 Unit:dB Default Value:-16
HOThdRscp
BSC6900ADD WRFD-020402 UCELLMBDRINTERFREQ MOD UCELLMBDRINTERFREQ
Measurement Based Direct Retry
Meaning:Threshold of signa If the mode is set to event
If the mode is set to period
GUI Value Range:-115~-25
Actual Value Range:-115~-2 Unit:dB Default Value:-92
36 de 51
22/07/2013 10:55 p.m.
37 de 51
22/07/2013 10:55 p.m.
8 Counters
Table 8-1 Counter description Counter Counter Name ID 67189400VS.RRC.Estab.DRDOut.Att Counter Description NE Feature ID Feature Name
Number of RRC BSC6900WRFD-02040001Intra System Direct Retry Connection Setup Attempts with DRD out for Cell Number of BSC6900WRFD-02040001 Intra System Successful RRC Direct Retry WRFD-010510 Connection 3.4/6.8 Setups with /13.6/27.2Kbps DRD out for Cell RRC Connection and Radio Access Bearer Establishment and Release Number of Successful CS Outgoing Inter-RAT Handovers Based on Directed Retry for Cell BSC6900WRFD-02040002Inter System Direct Retry
67189401VS.RRC.Estab.DRDOut.Succ
67189729VS.IRATHO.SuccOutCS.DR
67189730VS.IRATHO.AttRelocPrepOutCS.DR
Number of BSC6900WRFD-02040002Inter System Preparation Direct Retry Attempts for CS Outgoing Inter-RAT Handover Based on Directed Retry for Cell Number of BSC6900WRFD-02040002Inter System Successful Direct Retry Preparations for CS Outgoing Inter-RAT Handover Based on Directed Retry for Cell Number of BSC6900WRFD-02040002 Inter System Preparation Direct Retry WRFD-020303 Attempts for CS Inter-RAT Outgoing WRFD-020305 Handover Inter-RAT Handover for WRFD-020306 Based on Coverage Cell Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189732VS.IRATHO.SuccRelocPrepOutCS.DR
67189749IRATHO.AttRelocPrepOutCS
38 de 51
22/07/2013 10:55 p.m.
Counter Counter Name ID 67189750IRATHO.SuccRelocPrepOutCS
Counter Description
NE
Feature ID
Feature Name
Number of BSC6900WRFD-02040002 Inter System Successful Direct Retry WRFD-020303 Preparations for Inter-RAT CS Outgoing WRFD-020305 Handover Inter-RAT Handover for WRFD-020306 Based on Coverage Cell Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189751IRATHO.FailRelocPrepOutCS.TAlExp
Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Outgoing Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell WRFD-020306 Based on Coverage (TRELOCalloc expiry) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189752IRATHO.FailRelocPrepOutCS.TgtFail
Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Outgoing Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell (Relocation WRFD-020306 Based on Coverage Failure in Target CN/RNC or Target System) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189753IRATHO.FailRelocPrepOutCS.ReloNoSup
Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Outgoing Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell (Relocation WRFD-020306 Based on Coverage not supported in Target RNC or Target system) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189754IRATHO.AttOutCS
Number of CS Outgoing Inter-RAT Handover Attempts
BSC6900WRFD-02040002 Inter System Direct Retry WRFD-020303 Inter-RAT WRFD-020305 Handover Based on
39 de 51
22/07/2013 10:55 p.m.
Counter Counter Name ID
Counter Description
NE
Feature ID
Feature Name Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
WRFD-020306
67189755IRATHO.SuccOutCS
Number of Successful CS Outgoing Inter-RAT Handovers for Cell
BSC6900WRFD-02040002 Inter System Direct Retry WRFD-020303 Inter-RAT WRFD-020305 Handover WRFD-020306 Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189756IRATHO.FailOutCS.CfgUnsupp
Number of Failed BSC6900WRFD-02040002 Inter System CS Outgoing Direct Retry WRFD-020303 Inter-RAT Inter-RAT Handovers for WRFD-020305 Handover Cell (Configuration WRFD-020306 Based on Coverage Unsupported) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189757IRATHO.FailOutCS.PhyChFail
Number of Failed BSC6900WRFD-02040002 Inter System CS Outgoing Direct Retry WRFD-020303 Inter-RAT Inter-RAT Handovers for WRFD-020305 Handover Cell (Physical Channel Failure) WRFD-020306 Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67189758VS.IRATHO.AttRelocPrepInCS
Number of BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Incoming Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell WRFD-020306 Based on Coverage Inter-RAT Handover Based on Service
40 de 51
22/07/2013 10:55 p.m.
Counter Description
NE
Feature ID
Feature Name
Inter-RAT Handover Based on Load 67189759VS.IRATHO.SuccInCS Number of Successful CS Incoming Inter-RAT Handovers for Cell BSC6900WRFD-02040002 Inter System Direct Retry WRFD-020303 Inter-RAT WRFD-020305 Handover WRFD-020306 Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load 67189760VS.IRATHO.FailRelocPrepInCS.TRNCSysFailReloc Number of Failed BSC6900WRFD-02040002 Inter System Direct Retry Preparations for WRFD-020303 CS Incoming Inter-RAT Inter-RAT WRFD-020305 Handover Handover WRFD-020306 Based on (Relocation Coverage failure in target CN/RNC or Inter-RAT target system) Handover Based on Service Inter-RAT Handover Based on Load 67189761VS.IRATHO.FailRelocPrepInCS.TRNCSysRelocUnsupp Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Incoming Inter-RAT Inter-RAT WRFD-020305 Handover Handover (Relocation not WRFD-020306 Based on Coverage supported in target RNC or target system) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load 67189762VS.IRATHO.FailRelocPrepInCS.ResUnavail Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Incoming Inter-RAT Inter-RAT WRFD-020305 Handover Handover (No resource WRFD-020306 Based on Coverage available) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
41 de 51
22/07/2013 10:55 p.m.
Counter Counter Name ID 67190410VS.IRATHO.FailInCS.NoReply
Counter Description
NE
Feature ID
Feature Name
Number of Failed BSC6900WRFD-02040002 Inter System CS Inter-RAT Direct Retry WRFD-020303 Incoming Inter-RAT Handovers Due WRFD-020305 Handover to No Response from UE for Cell WRFD-020306 Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67190414VS.IRATHO.SuccRelocPrepInCS
Number of BSC6900WRFD-02040002 Inter System Successful Direct Retry WRFD-020303 preparations for Inter-RAT CS Incoming WRFD-020305 Handover Inter-RAT Handovers for WRFD-020306 Based on Coverage Cell Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67192186IRATHO.FailRelocPrepOutCS.HigherTrafficLod
Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Outgoing Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell (Traffic WRFD-020306 Based on Coverage Load In The Target Cell Higher Than In The Source Cell) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67192187VS.IRATHO.FailRelocPrepInCS.TgtHighLoad
Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Incoming Inter-RAT Inter-RAT WRFD-020305 Handover Handover (Traffic Load In WRFD-020306 Based on Coverage The Target Cell Higher Than In The Source Cell) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67192389VS.DRD.RBSetup.AttOut
Number of RB BSC6900WRFD-02040001Intra System Setup Attempts Direct Retry for Outgoing Inter-Frequency Directed Retry
42 de 51
22/07/2013 10:55 p.m.
Counter Description for Cell
NE
Feature ID
Feature Name
67192390VS.DRD.RBSetup.SuccOut
Number of Successful RB Setup for Outgoing InterFrequency Directed Retry for Cell
BSC6900WRFD-02040001Intra System Direct Retry
67192391VS.DRD.RBSetup.AttIn
Number of RB BSC6900WRFD-02040001Intra System Setup Attempts Direct Retry for Incoming Inter-Frequency Directed Retry for Cell Number of Successful RB Setup for Incoming InterFrequency Directed Retry for Cell BSC6900WRFD-02040001Intra System Direct Retry
67192392VS.DRD.RBSetup.SuccIn
67192393VS.DRD.RBRecfg.AttOut
Number of RB BSC6900WRFD-02040001Intra System Reconfiguration Direct Retry Attempts for Outgoing InterFrequency Directed Retry for Cell Number of BSC6900WRFD-02040001Intra System Successful RB Direct Retry Reconfiguration for Outgoing Inter-Frequency Directed Retry for Cell Number of RB BSC6900WRFD-02040001Intra System Reconfiguration Direct Retry Attempts for Incoming InterFrequency Directed Retry for Cell Number of BSC6900WRFD-02040001Intra System Successful RB Direct Retry Reconfiguration for Incoming Inter-Frequency Directed Retry for Cell Number of BSC6900WRFD-01061112 HSDPA DRD Outgoing WRFD-02040001 Intra System DCH-to-HSDPA Direct Retry Directed Retry Attempts for Cell Number of BSC6900WRFD-01061112 HSDPA DRD Successful WRFD-02040001 Intra System Outgoing Direct Retry DCH-to-HSDPA Directed Retry
67192394VS.DRD.RBRecfg.SuccOut
67192395VS.DRD.RBRecfg.AttIn
67192396VS.DRD.RBRecfg.SuccIn
67192440VS.DRD.RB.D2H.AttOut
67192441VS.DRD.RB.D2H.SuccOut
43 de 51
22/07/2013 10:55 p.m.
NE
Feature ID
Feature Name
67192442VS.DRD.RB.D2H.AttIn
Number of BSC6900WRFD-01061112 HSDPA DRD Incoming WRFD-02040001 Intra System DCH-to-HSDPA Direct Retry Directed Retry Attempts for Cell Number of BSC6900WRFD-01061112 HSDPA DRD Successful WRFD-02040001 Intra System Incoming Direct Retry DCH-to-HSDPA Directed Retry for Cell Number of BSC6900WRFD-01061112 HSDPA DRD DCH-to-HSDPA WRFD-02040001 Intra System Directed Retry Direct Retry Attempts for RNC Number of BSC6900WRFD-01061112 HSDPA DRD Successful WRFD-02040001 Intra System DCH-to-HSDPA Direct Retry Directed Retry for RNC Number of RRC BSC6900WRFD-02040001 Intra System Connection Direct Retry WRFD-010510 Setup Attempts 3.4/6.8 with DRD in for /13.6/27.2Kbps Cell RRC Connection and Radio Access Bearer Establishment and Release Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Outgoing Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell (No WRFD-020306 Based on Coverage Resource Available) Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67192443VS.DRD.RB.D2H.SuccIn
67192444VS.DRD.RB.D2H.Att.RNC
67192445VS.DRD.RB.D2H.Succ.RNC
67192607VS.RRC.Estab.DRDIn
67192658IRATHO.FailRelocPrepOutCS.NoResAvail
67192659IRATHO.FailRelocPrepOutCS.UKnowRNC
Number of Failed BSC6900WRFD-02040002 Inter System Preparations for Direct Retry WRFD-020303 CS Outgoing Inter-RAT Inter-RAT WRFD-020305 Handover Handover for Cell (Unknown WRFD-020306 Based on Coverage Target RNC) Inter-RAT Handover Based on Service Inter-RAT Handover
44 de 51
22/07/2013 10:55 p.m.
Counter Description
NE
Feature ID
Feature Name Based on Load
67192660VS.IRATHO.FailOutCS.NoReply
Number of Times BSC6900WRFD-02040002 Inter System Direct Retry that the Timer WRFD-020303 Waiting for Iu Inter-RAT Release WRFD-020305 Handover Command Expires in CS WRFD-020306 Based on Coverage Outgoing Inter-RAT Inter-RAT Handover for Handover Cell Based on Service Inter-RAT Handover Based on Load
67195503VS.DRD.RB.D2E.AttOut
Number of BSC6900WRFD-02040001Intra System Outgoing Direct Retry DCH-to-HSUPA Directed Retry Attempts for Cell Number of BSC6900WRFD-02040001Intra System Successful Direct Retry DCH-to-HSUPA Directed Retry for Cell Number of BSC6900WRFD-02040001Intra System Incoming Direct Retry DCH-to-HSUPA Directed Retry Attempts for Cell Number of BSC6900WRFD-02040001Intra System Successful Direct Retry Incoming DCH-to-HSUPA Directed Retry for Cell Number of CS BSC6900WRFD-020103 Voice Directed WRFD-020402 Retry Attempts Based on InterFrequency Measurement for Cell Number of BSC6900WRFD-020103 Successful CS WRFD-020402 Voice Directed Retry Based on Inter-Frequency Measurement for Cell Number of PS BSC6900WRFD-020103 R99 Directed WRFD-020402 Retry Attempts Based on InterFrequency Measurement for Cell Inter Frequency Load Balance Measurement Based Direct Retry Inter Frequency Load Balance Measurement Based Direct Retry Inter Frequency Load Balance Measurement Based Direct Retry
67195504VS.DRD.RB.D2E.SuccOut
67195505VS.DRD.RB.D2E.AttIn
67195506VS.DRD.RB.D2E.SuccIn
67196293VS.DRD.IFREQ.CS.MBDR.RBSetup.AttOut
67196294VS.DRD.IFREQ.CS.MBDR.RBSetup.SuccOut
67196295VS.DRD.IFREQ.PS.MBDR.R99.RBSetup.AttOut
45 de 51
22/07/2013 10:55 p.m.
Counter Counter Name ID 67196296VS.DRD.IFREQ.PS.MBDR.R99.RBSetup.SuccOut
Counter Description
NE
Feature ID
Feature Name
Number of BSC6900WRFD-020103 Successful PS WRFD-020402 R99 Directed Retry Based on Inter-Frequency Measurement for Cell Number of BSC6900WRFD-020103 HSDPA PS WRFD-020402 Directed Retry Attempts Based on InterFrequency Measurement for Cell
Inter Frequency Load Balance Measurement Based Direct Retry Inter Frequency Load Balance Measurement Based Direct Retry
67196297VS.DRD.IFREQ.PS.MBDR.HResCong.RBSetup.AttOut
67196298VS.DRD.IFREQ.PS.MBDR.HResCong.RBSetup.SuccOutNumber of BSC6900WRFD-020103 Successful WRFD-020402 HSDPA PS Directed Retry Based on InterFrequency Measurement for Cell 67196299VS.IRATHO.AttOutCS.MBDR
Inter Frequency Load Balance Measurement Based Direct Retry
Number of CS BSC6900WRFD-02040002 Inter System Outgoing Direct Retry WRFD-020402 Inter-RAT Measurement Handover Based Direct Attempts Based Retry on Measurement for Cell Number of BSC6900WRFD-02040002 Inter System Successful CS Direct Retry WRFD-020402 Outgoing Measurement Inter-RAT Based Direct Handovers Retry Based on Measurement for Cell Number of CS BSC6900WRFD-02040002 Inter System Incoming Direct Retry WRFD-020303 Inter-RAT Inter-RAT Handover WRFD-020305 Handover Attempts for Cell WRFD-020306 Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
67196300VS.IRATHO.SuccOutCS.MBDR
73394014VS.IRATHO.AttInCS
73394035VS.IRATHO.AttRelocPrepOutCS.DR.GCell
Number of CS BSC6900WRFD-02040002 Inter System Outgoing Direct Retry WRFD-020303 Inter-RAT Inter-RAT Handover WRFD-020305 Handover Preparation Attempts WRFD-020306 Based on Coverage (Directed retry) Inter-RAT Handover
46 de 51
22/07/2013 10:55 p.m.
Counter Description
NE
Feature ID
Feature Name Based on Service Inter-RAT Handover Based on Load
73394053VS.DRD.PhyRecfg.AttOut
Number of BSC6900WRFD-020103 Inter Outgoing DRD Frequency WRFD-02040001 Load Balance Attempts through Physical Intra System Channel Direct Retry Reconfiguration for Cell Number of BSC6900WRFD-020103 Inter Successful Frequency WRFD-02040001 Load Balance Outgoing DRDs through Physical Intra System Channel Direct Retry Reconfiguration for Cell Number of BSC6900WRFD-020103 Inter Incoming DRD Frequency WRFD-02040001 Load Balance Attempts through Physical Intra System Channel Direct Retry Reconfiguration for Cell Number of BSC6900WRFD-020103 Inter Successful Frequency WRFD-02040001 Load Balance Incoming DRDs through Physical Intra System Channel Direct Retry Reconfiguration for Cell Number of RB BSC6900WRFD-02040001Intra System Setup Attempts Direct Retry After the RB Setup DRD Rollback Number of BSC6900WRFD-02040001Intra System successful RB Direct Retry Setups After the RB Setup DRD Rollback Number of RB BSC6900WRFD-02040001Intra System Reconfiguration Direct Retry Attempts After the RB Reconfiguration DRD Rollback Number of BSC6900WRFD-02040001Intra System Successful RB Direct Retry Reconfigurations After the RB Reconfiguration DRD Rollback Number of Physical Channel BSC6900WRFD-02040001Intra System Direct Retry
73394054VS.DRD.PhyRecfg.SuccOut
73394055VS.DRD.PhyRecfg.AttIn
73394056VS.DRD.PhyRecfg.SuccIn
73421487VS.DRD.RBSetup.AttEstab.RollBack
73421488VS.DRD.RBSetup.SuccEstab.RollBack
73421489VS.DRD.RBRecfg.AttEstab.RollBack
73421490VS.DRD.RBRecfg.SuccEstab.RollBack
73421491VS.DRD.PhyRecfg.AttEstab.RollBack
47 de 51
22/07/2013 10:55 p.m.
Counter Description Reconfiguration Attempts After the Physical Channel Reconfiguration DRD Rollback
NE
Feature ID
Feature Name
73421492VS.DRD.PhyRecfg.SuccEstab.RollBack
Number of BSC6900WRFD-02040001Intra System Direct Retry Successful Physical Channel Reconfigurations After the Physical Channel Reconfiguration DRD Rollback Number of BSC6900WRFD-01061112 HSDPA DRD Outgoing WRFD-02040001 Intra System FACH-to-HSDPA Direct Retry Directed Retry Attempts for Cell Number of BSC6900WRFD-01061112 HSDPA DRD Successful WRFD-02040001 Intra System Outgoing Direct Retry FACH-to-HSDPA Directed Retries for Cell Number of BSC6900WRFD-02040001Intra System Outgoing Direct Retry FACH-to-HSUPA Directed Retry Attempts for Cell Number of BSC6900WRFD-02040001Intra System Successful Direct Retry Outgoing FACH-to-HSUPA Directed Retries for Cell Number of BSC6900WRFD-01061112 HSDPA DRD Incoming WRFD-02040001 Intra System FACH-to-HSDPA Direct Retry Directed Retry Attempts for Cell Number of BSC6900WRFD-01061112 HSDPA DRD Successful WRFD-02040001 Intra System Incoming Direct Retry FACH-to-HSDPA Directed Retries for Cell Number of BSC6900WRFD-02040001Intra System Incoming Direct Retry FACH-to-HSUPA Directed Retry Attempts for Cell Number of BSC6900WRFD-02040001Intra System Successful Direct Retry Incoming FACH-to-HSUPA Directed Retries
73421842VS.DRD.RB.F2H.AttOut
73421843VS.DRD.RB.F2H.SuccOut
73421844VS.DRD.RB.F2E.AttOut
73421845VS.DRD.RB.F2E.SuccOut
73421846VS.DRD.RB.F2H.AttIn
73421847VS.DRD.RB.F2H.SuccIn
73421848VS.DRD.RB.F2E.AttIn
73421849VS.DRD.RB.F2E.SuccIn
48 de 51
22/07/2013 10:55 p.m.
NE
Feature ID
Feature Name
73424972VS.RRC.Rej.Redir.Dist.IntraRat
Number of BSC6900WRFD-02040005InterDistance-Based Frequency RRC InterRedirection frequency Based on Redirections for Distance Cell
49 de 51
22/07/2013 10:55 p.m.
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
50 de 51
22/07/2013 10:55 p.m.
10 Reference Documents
[1] Call Admission Control Feature Parameter Description [2] Load Control Feature Parameter Description [3] BSC6900 UMTS Performance Counter Reference
51 de 51
22/07/2013 10:55 p.m.

Directed Retry Decision

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Directed Retry Decision

Caricato da

Copyright:

Formati disponibili

Directed Retry Decision