UMTS Swapping Strategy Guide

Product Name SWP Product Version 1.
Confidentiality Level INTERNAL Total 69 pages
UMTS Swapping Strategy Guide

(For internal use only)
Prepared by Reviewed by Reviewed by Updated by Reviewed by Approved by
GSM&UMTS Network Performance Research Department
Date Date Date Date
2010-12-31
Huawei Technologies Co., Ltd.

All rights reserved
Internal Open
Revision Records
Date Revis ed Versio n 1.00 Description Author
2010-12-31
Added algorithm difference analysis and handling strategy. Updated the information related to the Iur interface in the intra-frequency and inter-frequency swapping schemes.
Su Yongfeng and Wang Zheng Su Yongfeng, Xu Jing, Shen Gang, He Guoquan, Zou Rong, Bao Rungui, Gong Jie
2012-04-05
1.10
Added and updated the algorithm difference analysis and handling strategy based on NSN RU20.
2013-10-1
Huawei Confidential
Page 2 of 69
Internal Open
Contents
Revision Records............................................................................2 1 Document Description..................................................................6 2 Intra-Frequency/Inter-Frequency Swapping Scheme.......................7
2.1 Introduction.............................................................................................................................................................7 2.2 Network Performance Factor Analysis..................................................................................................................13 2.3 Analysis in Terms of Engineering Workload.........................................................................................................18 2.4 Summary................................................................................................................................................................22 2.5 Suggestions on Selecting a Swapping Scheme......................................................................................................24
3 Analysis and Solution for Algorithm Differences Between Huawei and NSN........................................................................................ 26
3.1 Mapping of NSN Key Features.............................................................................................................................26 3.2 Automatic Neighboring Cell Adding Algorithm...................................................................................................31 3.3 Inter-Frequency Inter-RAT Handover Algorithm..................................................................................................32 3.4 HSPA Compressed Mode.......................................................................................................................................33 3.5 Simultaneous Issuance of Intra- and Inter- Frequency Handover Measurement Reports.....................................35 3.6 Asynchronous Inter-Frequency Hard Handover....................................................................................................36 3.7 Inter-Frequency Handover Preference...................................................................................................................37 3.8 Hierarchical Cell Selection and Reselection..........................................................................................................38 3.9 PS 0K Access.........................................................................................................................................................41 3.10 Proactive Re-establishment of CS Calls..............................................................................................................43 3.11 RRC Call Drop Rate............................................................................................................................................45 3.12 EFD......................................................................................................................................................................46 3.13 Scrambling Code Planning..................................................................................................................................47 3.14 HSPA User Number Restriction..........................................................................................................................47 3.15 Power-Based Uplink Admission Control.............................................................................................................50 3.16 Uplink Admission for Soft Handover..................................................................................................................52 3.17 DRD.....................................................................................................................................................................53 3.18 NRT DCH Rate Set Restriction...........................................................................................................................54 3.19 HSDPA Throughput Counter Definition Analysis...............................................................................................56 3.20 HSUPA Throughput Counter Definition Analysis...............................................................................................58 3.21 HSPA Dynamic DL Control Channel Allocation.................................................................................................63
2013-10-1
Huawei Confidential
Page 3 of 69
Internal Open
3.22 H2F State Transition Mechanism........................................................................................................................64 3.23 SIR ErrorBased H2D Triggering Mechanism...................................................................................................66 3.24 H2D and E2D Mechanisms.................................................................................................................................68 3.25 Multi-Carrier Strategy.........................................................................................................................................69
2013-10-1
Huawei Confidential
Page 4 of 69
Internal Open
UMTS Swapping Strategy GuideKey words

UMTS, Swapping
Abstract
This document analyzes the differences between the algorithms of Huawei and the original network vendor which is to swapped that affect the key performance indicator (KPI) acceptance, and provides countermeasures. Vendors use different algorithms. This document analyzes the difficulties brought by differences of algorithms from the practical aspect of the swapping project, and provides handling strategies. A large number of swapping projects involve NSN, but not Ericsson or Alcatel-Lucent. Therefore, this document mainly describes the strategies for coping with swapping projects that involve NSN. Subsequent changes are supplemented to this document.
Acronyms and abbreviations
2013-10-1
Huawei Confidential
Page 5 of 69
Internal Open
Document Description
This document describes the intra-frequency and inter-frequency swapping schemes, and compares and analyzes the possible problems of several swapping schemes in terms of algorithm, performance, workload, and cooperation with the customer and competitor. In addition, this document provides suggestions on swapping schemes in different scenarios.
2013-10-1
Huawei Confidential
Page 6 of 69
Internal Open
Intra-Frequency/Inter-Frequency Swapping Scheme

Swapping schemes involved in this document are divided into two types: intra-frequency swapping and inter-frequency swapping schemes. Intra-frequency swapping schemes are further divided into two types: swapping with the Iur interface and swapping without the Iur interface. Inter-frequency swapping without the Iur interface is recommended. Intra-frequency swapping with the Iur interface is less recommended. Intra-frequency swapping without the Iur interface is not recommended. Inter-frequency swapping with the Iur interface is only for presentation.
2.1 Introduction
2.1.1 Inter-Frequency Swapping Without the Iur Interface (Recommended)
Most projects use this swapping scheme. 1. Different frequencies before and after swap. That is, the network at Huawei side and the remaining network of the swapped competitor use different frequencies.

In the case of a single carrier, the case is simple. The operator needs to provide another frequency that is not in use in this area. If the original network uses dual carriers, and F1 and F2 frequencies provide continuous coverage, the operator needs to provide another two frequencies that is not in use in this area. If the original network uses dual carriers, and the border between swapped network and remaining network is covered by one of the vendors using frequency F2, swap the F1 frequencies using other frequency, and keep F2 frequencies unchanged. The operator needs to provide another unused frequency. If the original network uses dual carriers, and the border between swapped network and remaining network is not covered by F2 frequencies, F1 frequencies could be used to swap F2 frequencies, and F2 frequencies could be used to swap F1 frequencies in previous projects. From the swap experience, there is interferences in this scenario. The scenarios of three or more carriers are seldom involved, but can be deduced
2013-10-1
Huawei Confidential
Page 7 of 69
Internal Open
through analogy. 2. Huawei radio network controller (RNC) and competitor's RNC are not interconnected through Iur interfaces. The two networks are completely independent, and implement interaction with existing GSM networks separately. Hard inter-frequency handover across RNCs through the core network is not recommended.
The scheme of inter-frequency swap without the Iur interface is to avoid interconnection with the Iur interface of the competitor in terms of workload. This scheme avoids interference with the signals of the original vendor, and possible unfavorable impact when problems happen in Iur interface interconnection. In terms of traffic statistics, this scheme uses the 2G network to bear the traffic volume at the swapping border. Therefore, little impact is made on the access success rate and call drop rate. However, users hand over from the 3G network to the 2G network at the border between Huawei network and remaining network of the competitor. The 3G traffic volume declines. If the settings of inter-RAT handover or cell reselection parameters of the 2G network make it difficult for users to return to the 3G network, the 3G traffic volume declines more sharply. Mobility of packet switched (PS) services is low. Therefore, the decline of the traffic volume mainly involves circuit switched (CS) services. If the original 3G network uses discontinuous coverage, cluster division during swapping is separate in terms of geological location. In this case, the change to the traffic volume is not large. In terms of customer perception, the scheme of inter-frequency swapping without the Iur interface has low impact on voice users. PS users cannot use high-speed PS services in the 2G network. The mobility of PS users is low. Therefore, such impact is not large. The possibility of users in idle state camping on the 2G network increases. This may result in changes to the network icon on the screen of mobile phone of certain users. Sensitive users may feel unsatisfied. If the original 3G network uses discontinuous coverage, cluster division during swapping is separate in terms of geological location. In the original network, users may need to camp on the 2G network for a certain period. After swapping, the user experience will not worsen greatly.
2.1.2 Intra-Frequency Swapping with the Iur Interface (Recommended)

This scheme is also widely used, especially when the operator does not have excessive frequency resources. 1. Frequencies used before and after swapping remain unchanged. That is, the network at Huawei side and the remaining network of the swapped competitor use the same frequencies. Huawei RNC and competitor's RNC are connected through the Iur interface. Users can switch between Huawei network and competitor network through soft/hard handover.
2.
The workload in Iur interface interconnection is heavy with a large number of unexpected factors: 1. 2. If the neighboring cell combination algorithms are not matched, Huawei may need to ask the competitor to modify the neighboring cell configuration. When problems occur in Iur interface interconnection, Huawei needs the competitor to provide assistance. It may take a certain period of time for Huawei to provide patches to solve these problems which may be caused by errors of the competitor. During this period, the customer must tolerate a certain decline in network performance. When no Iur interface interconnection problems exist, this scheme does not have impact on the traffic statistics indexes or customer perception of the original network. A large
2013-10-1
Huawei Confidential
Page 8 of 69
Internal Open
number of differences, however, exist in the Iur interfaces of different vendors. The following table lists the functions not supported by the Iur interfaces of competitors. Vendo r Siemens Support for Iur Interface Functions DSCR is not supported. RAB MODIFY or DCH MODIFY is not supported. Reconfiguration of compressed mode in RL reconfiguration is not supported. RAB queuing is not supported. Node synchronization of the Iur interface is not supported. Relocation is not supported when the Iur interface provides only one RL. Relocation is supported only when the Iur interface provides multiple RLs. Nokia The neighboring GSM cell information is not contained in the RL setup response message. Relocation policies: RELOC is supported when the Iur interface is provided. RELOC but not CM MODIFY is supported at the Iur interface. The RL RESTORE message is not used at the Iur interface. The internal synchronization mode of Nokia is used. Dedicated measurement end message is not sent. Dedicated measurement end is not supported until the RL is deleted. A compressed mode command but not RL reconfiguration is used to enable the compressed mode. Node synchronization of the Iur interface is not supported. Nokia Iur interface does not support network sharing in connected mode. When moving between cells that belong to different location areas of the DRNC, a UE needs to perform location area update. When working as the DRNC, Nokia Iur interface does not support Interfrequency Cell List in the RL SETUP RESPONSE message. Therefore, the inter-frequency inter-RAT neighboring relationship cannot be returned; as a result, the SRNC cannot know the inter-frequency inter-RAT neighboring cells of the DRNC cell, and cannot issue measurement control instructions for interfrequency and inter-RAT handover. F-DPCH, VoIP over HS-DSCH, or signaling radio bearer (SRB) over HSDSCH is not supported. Only "May" is optional in the differential control IE (which controls whether to combine the new RL with the existing RLs), but "Must" and "Must not" are not provided. MBMS Attach or MBMS Detach is not supported at the Iur interface RADIO LINK RECONFIGURATION PREPARE messages are not queued, and these messages are not configured with priority levels. Event-based dedicated measurement is not supported. Only 'On-Demand' and 'Periodic' report characteristics are supported. The Information Exchange procedure is not supported at the Iur interface. As a result, the Iur interface does not support MBMS. Common Transport Channel messages are not supported. Paging (over Iur), Resetting the Iur are not supported.
2013-10-1
Huawei Confidential
Page 9 of 69
Internal Open
Vendo r
Support for Iur Interface Functions HS-DSCH over Iur is not supported. E-DCH over Iur is not supported. SixteenQAM is not supported. F-DPCH is not supported. Diversity Mode is not supported.
Nortel
Inter-frequency hard handover is not supported at the Iur interface. RAB queuing is not supported. Node synchronization of the Iur interface is not supported.
Alcatel
RAB queuing is not supported. Dedicated measurement is supported for only RL but not RLS. No compressed mode command is supported. ALU RNC does not support the event type dedicated channel measurement of sir-error sent over the Iur interface of Huawei RNC. ALU does not support periodic measurement for dedicated channels of the Iur interface. ALU does not support service combination of low-rate CS and high-rate PS, for example: CS(5.9,4.75)+PS 384/384; AMR CS call NB UPV2 configuration (5.9, 4.75)+PS I/B 384/HSDPA not supported; AMR CS call NB UPV2 configuration (4.75)+PS I/B 384/384. ALU does not support co-existence of CS call NB UPV2 configuration (4.75) and PS I/B 8/8. When the CS 4.75 service is accessed, and then the PS 8/8 service is accessed, the CS service is automatically re-configured as 12.2. ALU does not support SRB over EDCH or SRB over HS-DSCH. UL/DL Signaling Transfer procedures are supported only when the ALU RNC works as the SRNC. That is, ALU supports only the SRNC mode for the public channel of the Iur interface. When the ALU RNC works as the SRNC, the Iur interface does not support conversion between dedicated channels and public channels: D to H, H to D, H to F, F to H Relocation with Iur of cell-FACH is not supported. MIMO is not supported. ALU RNC cannot actively shut down SCTP links, or deactivate and shut down ASP links.
ZTE
ZTE RNC cannot set up multiple RLs at one time at the Iur interface. RL SETUP but not RL ADDITION is used to implement inter-frequency hard handover within a NodeB (DRNC). DCH MODIFY is not supported. ZTE uses DCH ADD+DCH DEL to implement this function. DCH MODIFY+CM MODIFY is not supported. RL reconfiguration in the following scenario is not supported: A UE sets up a radio resource controller (RRC) connection in the SRNC, enters into the CELL_DCH state and single signaling state, hands over to the DRNC cell, and
2013-10-1
Huawei Confidential
Page 10 of 69
Internal Open
Vendo r
Support for Iur Interface Functions receives a service setup request from the core network (CN).
Ericsson
RAB queuing is not supported. Node synchronization of the Iur interface is not supported. Common Transport Channel Resources Initialization is not supported. Common Measurement Initiation is not supported. MBMS Procedures is not supported. RADIO LINK SETUP REQUEST: No setting of CFN when requesting serving cell change, if included DRNS will reject the procedure RADIO LINK ADDITION REQUEST: No setting of CFN when requesting serving cell change, if included DRNS will reject the procedure DL Reference Power IE not set by SRNC, IE ignored by DRNS RADIO LINK RECONFIGURATION PREPARE: DL Reference Power IE not set by SRNC, IE ignored by DRNS RADIO LINK RECONFIGURATION REQUEST/RESPONSE are not supported. RADIO LINK RECONFIGURATION RESPONSE/COMMAND/COMMAND are not supported. UPLINK SIGNALLING TRANSFER INDICATION: Cell Capability Container FDD IE and Inter-frequency Cell List IE not included by DRNC in message, if included SRNC will ignore the IEs. RELOCATION COMMIT is not supported. INFORMATION EXCHANGE INITIATION REQUEST is not supported.
In Siemens RNC, relocation is not supported when the Iur interface provides only one RL. Relocation is supported only when the Iur interface provides multiple RLs. When the core network does not support relocation, or the Iur interface has only one RL, PS services may need to consume a large number of Iur interface resources because relocation is not available.
2.1.3 Intra-Frequency Swapping without the Iur Interface (Not Recommended)

Certain projects use this swapping scheme. 1. Frequencies used before and after swapping remain unchanged. That is, the network at Huawei side and the remaining network of the swapped competitor use the same frequencies. Huawei RNC and competitor's RNC are not interconnected through Iur interfaces. The two networks are completely independent 3G networks, and implement interaction, such as handover and reselection, with the existing 2G network separately. Due to the existence of intra-frequency interferences at the border of Huawei network and competitor network, UEs need to be handed over or reselected to the existing 2G network earlier than in inter-frequency swapping without the Iur interface. After relevant configuration is added on the core network side, users can be handed over from one 3G network through the other 3G network under the control of the core network. However, the handover success rate is low, no gain from soft handover is added, and severe
2.
2013-10-1
Huawei Confidential
Page 11 of 69
Internal Open
interference exists. Therefore, this scheme is not recommended. Intra-frequency swapping without the Iur interface avoids interconnection with the competitor RNC through the Iur interface, but has intra-frequency interference compared with interfrequency swapping without the Iur interface. In terms of traffic statistics indexes, if the border between Huawei network and remaining competitor network after swapping is long, the interference at the border increases greatly. This is because the two networks use the same frequency, but do not support handover between each other. As a result, the relevant service quality at the border worsens. Indexes such as the access success rate and call drop rate deteriorate. Take the project in Romania where intra-frequency swapping without the Iur interface is used for example. The call drop rate of a cluster that is completely swapped is about 0.8% to 0.9%. The call drop of a cluster that is not completely swapped (that is, a cluster that is next to intrafrequency cells of the competitor) is about 1%. The inter-RAT handover threshold parameters, especially the EcNo threshold (RSCP and EcNo dual measurement) of the 2D event, need to be properly adjusted to ensure that inter-RAT handover takes place in time, thereby reducing call drops. In this scenario, inter-RAT handover is judged based on the worsening condition of the EcNo quality. For cells at the border, the service-based handover to the 2G network can be used when the customer permits. If the original 3G network uses discontinuous coverage, cluster division during swapping is separate in terms of geological location. For example, if swapping takes place one town after another, and the geological connections between the towns are few, intra-frequency interference is not severe, and may occur only in the areas of the high-way roads that connect the towns. In terms of customer perception, intra-frequency swapping without the Iur interface is basically the same as inter-frequency swapping without the Iur interface. Due to the adjustment of the inter-RAT handover thresholds, users at the border are easier to be handed over to the 2G network. Therefore, the impact on these users is slightly large.
2.1.4 Inter-Frequency Swapping with the Iur Interface (Not Recommended)

The cases of this scheme are rare. 1. 2. Different frequencies before and after swapping are used. That is, the network at Huawei side and the remaining network of the swapped competitor use different frequencies. Huawei RNC and competitor's RNC are connected through the Iur interface. Users can switch between Huawei network and competitor network through hard handover.
Inter-frequency swapping with the Iur interface involves Iur interface interconnection. The success rate of relocation associated with cross-vendor inter-frequency hard handover is low. Performance gain is limited. During swapping of Ericsson network in Egypt, inter-frequency swapping with the Iur interface was used. Huawei RNC and Ericsson RNC implemented inter-frequency hard handover through the Iur interface. The success rate of inter-frequency hard handover was about 90%. Most failures were caused by no response of the UE. As a result, the call drop rate fell below the standard. Huawei recommended the customer to use intra-frequency swapping with the Iur interface. Then, the call drop rate rose to the level on the original network.
2013-10-1
Huawei Confidential
Page 12 of 69
Internal Open
2.2 Network Performance Factor Analysis

2.2.1 Comparison of Performance Between Swapping Schemes
The following table describes the comparison between different swapping schemes in terms of possible performance problems. IntraFrequency Swapping with the Iur Interface Algorithm collaboration Neighboring cell combination Huawei and NSN use different neighboring cell combination algorithms. Huawei needs to optimize neighboring cell configuration. In addition, Huawei may need NSN to modify neighboring cell configuration. InterFrequency Swapping with the Iur Interface IntraInterFrequency Frequency Swapping Swapping Without the Iur Without the Interface Iur Interface
Huawei and NSN use different neighboring cell combination algorithms. Huawei needs to optimize neighboring cell configuration. Check for missing neighboring cells when swapping the networks of other vendors. These three schemes do not need soft handover with the competitor network. Therefore, Huawei does not need the competitor to optimize neighboring cell configuration.
Interaction Vendors have different understanding Not involved across the Iur on the protocol, and different interface implementation and handling methods. Therefore, signaling interaction and certain algorithm processes may fail.
2013-10-1
Huawei Confidential
Page 13 of 69
Internal Open
IntraFrequency Swapping with the Iur Interface Relocation If the core network does not support relocation, or a single RL exists across the Iur interface, mobile users at the border of the Iur interface are always connected to the Iur interface until the service is complete. In this case, Iur interface resources are occupied. In addition, algorithms such as load balancing that can be implemented only in the SRNC cannot be implemented.
InterFrequency Swapping with the Iur Interface Relocation associated with inter-frequency hard handover needs to be supported by the core network. Compared with intra-frequency swapping with the Iur interface, less Iur interface resources are used, but the handover success rate is lower.
IntraInterFrequency Frequency Swapping Swapping Without the Iur Without the Interface Iur Interface In most cases, interaction with the 2G network is used. In this case, relocation is not involved. Relocation associated with hard handover can be used. However, this requires cooperation of the core network, and the relocation success rate is low.
2013-10-1
Huawei Confidential
Page 14 of 69
Internal Open
IntraFrequency Swapping with the Iur Interface Performance Call drop rate
InterFrequency Swapping with the Iur Interface
IntraInterFrequency Frequency Swapping Swapping Without the Iur Without the Interface Iur Interface The inter-RAT handover success rate is much lower than the soft handover success rate. As a result, The inter-RAT handover success the call drop rate of CS and PS rate is much services may lower than the increase. soft handover success rate. As a result, the call drop rate of CS and PS services may increase.
Edge areas lack soft handover gain. The success rate of relocation associated with inter-frequency hard handover is The call drop rate is counted low, and the call drop rate increases only in the (as in the case in SRNC. Therefore, the Egypt). call drop rate may change. Call drops due to problems of cells in the DRNC are counted in the SRNC. When relocation is not enabled, such "unreasonable" statistics take place more often (as in a project in Spain).
Call drops due to missing intra-frequency neighboring cells may increase.
The call drop rate increases because intra-frequency interference increases.
2013-10-1
Huawei Confidential
Page 15 of 69
Internal Open
IntraFrequency Swapping with the Iur Interface Service volume and user perception User camping and service volume before and after swapping remain basically unchanged. If the call drop rate and compatibility are not considered, this scheme barely has any impact on user perception.
InterFrequency Swapping with the Iur Interface User camping and service volume before and after swapping remain basically unchanged. In terms of user perception, in addition to the call drop rate and compatibility, soft handover in the original network turns into relocation associated with inter-frequency handover. The voice quality is worse than that before swapping.
IntraInterFrequency Frequency Swapping Swapping Without the Iur Without the Interface Iur Interface
User inter-RAT handover increases. The time of CS services on the GSM network increases. The CS service traffic on the 3G network declines. If the parameter setting policies on the 2G network make it difficult for users to return to the 3G network, the problem worsens. The possibility of users in idle state camping on the 2G network increases. This may result in dissatisfaction of sensitive users. If a user returns from the 2G network to the 3G network through HPLMN reselection, the problem is more serious. When camping on the 2G network, users cannot use PS services of the 3G network, affecting customer satisfaction.
Others
IOT compatibility problems may result in failure of certain functions, and affect the performance of certain KPIs, such as access success rate, handover success rate, and call drop rate.
IOT compatibility None. problems may result in failure of certain functions, and affect the performance of certain KPIs, such as handover success rate and call drop rate. The two networks are separate, making it easy to locate problems.
None.
Others
Problems occur in the cross Iur interface scenario. It requires cooperation of two vendors to locate complex problems. It takes a long time and great efforts. The Iur interface needs to be configured. Field transmission resources and interface board specifications of the RNC are required.
The two networks are separate, making it easy to locate problems. If the number of available frequencies provided by the customer is insufficient, this scheme cannot be used.
2013-10-1
Huawei Confidential
Page 16 of 69
Internal Open
Refer to the KPI comparison results in the attachment before and after swapping of the following operators: TI of Italy (inter-frequency swapping without the Iur interface), Starhub of Singapore (intra-frequency swapping without the Iur interface), and Telenor of Norway (intra-frequency swapping with the Iur interface). Note that TI provides discontinuous coverage and Starhub provides continuous coverage. In a word, the swapping schemes are sorted in the ascending sequence of negative impact on performance as follows: Intra-frequency swapping with the Iur interface < inter-frequency swapping without the Iur interface < intra-frequency swapping without the Iur interface < inter-frequency swapping with the Iur interface Inter-frequency swapping with the Iur interface does not give priority to handover to the 2G network. Therefore, the negative impact on performance is larger than that of intra-frequency swapping without the Iur interface. The preceding comparison is based on the prerequisite that no interconnection problems exist, interconnection problems have little impact on the performance, or the impact is great but eliminated during intra-frequency swapping with the Iur interface. As such, intra-frequency swapping with the Iur interface has the minimum negative impact on performance.
2.2.2 Iur Interoperation Strategy

For intra-frequency swapping with the Iur interface, cooperation across Iur interfaces of CS services is mature. Therefore, most interconnection problems occur when users move across Iur interfaces during PS services. It is recommended that the Iur interface allow soft handover and hard handover for CS services but not enable relocation, and allow soft handover and hard handover, and enable DSCR for PS services. For swapping without the Iur interface, it is recommended that users be handed over to the 2G network. For inter-frequency swapping with the Iur interface, this swapping scheme is not recommended. For the Iur interface strategy, use relocation associated with inter-frequency hard handover as in the case in Egypt. For the details, see the relevant document: BSC 6900 UMTS Iur Interface Interconnection Guide-20100602-A-V1.0 http://support.huawei.com/support/pages/kbcenter/view/product.do? actionFlag=detailProductSimple&web_doc_id=SC0000585416&doc_type=123-2
2.2.3 Iur Interface Interconnection

The understanding to the protocols and implementation flows of different vendors may vary. In this case, during interaction over the Iur interface, compatibility problems easily occur, leading to flow failure and failure of access and handover. For Iur interface interconnection problems, see the following document: List of Iu and Iur Compatibility Problems in the UMTS Maintenance Manual-20101103-AV2.1 http://support.huawei.com/support/pages/kbcenter/view/product.do? actionFlag=detailProductSimple&web_doc_id=SC0000597254&doc_type=123-2 The BSC6900V912 GU network problem prevention guide will incorporate cases in
2013-10-1
Huawei Confidential
Page 17 of 69
Internal Open
compatibility problems in the future. http://support.huawei.com/support/pages/kbcenter/view/product.do? actionFlag=detailProductSimple&web_doc_id=SC0000562307&doc_type=123-2
2.3 Analysis in Terms of Engineering Workload

2.3.1 Comparison of Swapping Schemes in Terms of Data Making Workload
Neighboring relationship Intra-Frequency Inter-Frequency Intra-Frequency Swapping with Swapping with Swapping the Iur Interface the Iur Interface Without the Iur Interface Huawei side of the 3G network
Inter-Frequency Swapping Without the Iur Interface
Intra-frequency neighboring cells: Use the neighboring cell configuration of the competitor, and convert these cells into neighboring cells of the neighboring RNC. If the neighboring cell combination algorithms are different, optimization of the neighboring cell configuration may be required. Inter-RAT neighboring cells: Use the competitor configuration on the original network.
Inter-frequency neighboring cells: Use the intrafrequency neighboring cell configuration of the competitor, but convert these cells into interfrequency neighboring cells of the neighboring RNC. If the neighboring cell combination algorithms are different, optimization of the neighboring cell configuration may be required. Inter-RAT neighboring cells: Use the competitor configuration on the original network.
Intra-frequency neighboring cells: Use the neighboring cell configuration of the competitor, but convert these cells into cells of Huawei RNC. If the neighboring cell combination algorithms are different, optimization of the neighboring cell configuration may be required. During intrafrequency swapping without the Iur interface, for a neighboring cell that is not swapped yet, use CIO to prohibit UEs from reporting the 1A event of the cell. Inter-RAT neighboring cells: For a network wholly covered by 3G signals, cells at the border of swapping turn from the network center to the
Intra-frequency neighboring cells: Neighboring cells of the competitor do not need to be configured. Inter-RAT neighboring cells: The same as that in intra-frequency swapping with the Iur interface.
2013-10-1
Huawei Confidential
Page 18 of 69
Internal Open
network edge, a large number of 2G network neighboring cells need to be added. For a network with discontinuous 3G coverage, for example, only the network skeleton is built or the network covers areas with natural blocks such as water and mountains, the original network is configured with sufficient 2G neighboring cells. Therefore, use the original configuration if the swapping is fragmented and clusters are loosely connected. Competitor side of the 3G network
Intra-frequency neighboring cells: If the neighboring cell combination algorithms of Huawei and the competitor are different, the neighboring relationship may need to be optimized; otherwise, modify only the RNC to which the sites to be swapped belong. Inter-RAT neighboring cells: No modification is required.
Inter-frequency neighboring cells: If the neighboring cell combination algorithms of Huawei and the competitor are different, the cells where the equipment is swapped to Huawei equipment need to be configured as the inter-frequency neighboring cells of the competitor's neighboring RNC. Inter-RAT neighboring cells: No modification is required.
Intra-frequency neighboring cells: Use CIO to prohibit UEs from reporting the 1A event of Huawei cells that are swapped to. Inter-RAT neighboring cells: For a network wholly covered by 3G signals, cells at the border of swapping turn from the network center to the network edge, a large number of 2G network neighboring cells need to be added. For a network with discontinuous 3G coverage, for example, only the network skeleton
Intra-frequency neighboring cells: No modification is required. Inter-RAT neighboring cells: The same as that in intra-frequency swapping with the Iur interface. After swapping of the whole network, determine whether to modify the original frequencies according to the customer strategy. If 3G frequencies need to be modified, you also need to modify 2G network configuration. When modifying 3G frequencies, you need to
2013-10-1
Huawei Confidential
Page 19 of 69
Internal Open
is built or the network covers areas with natural blocks such as water and mountains, the original network is configured with sufficient 2G neighboring cells. Therefore, use the original configuration if the swapping is fragmented and clusters are loosely connected. 2G network No modification is required. The frequency No modification is information of the required. swapped 3G cell needs to be modified. The original configuration of the competitor can be used. Interference at the border increases. Therefore, users need to hand over to the 2G network early to avoid call drop. Inter-RAT handover parameters need to be optimized. For example, the EcNo threshold of the 2D/2F event needs to be adjusted. For others, see the description of interfrequency swapping.
deactivate the relevant cells, which leads to service interruption.
The frequency information of the swapped 3G cell needs to be modified.
Handover parameters
Interfrequency/interRAT handover parameters
The original configuration of the competitor can be used.
The inter-RAT parameters of the competitor and Huawei may need to be reset. For example, parameters related to voice services need to be adjusted to allow easy handover to the 2G network to maintain the handover success rate and reduce the call drop rate. Parameters related to PS services need to be adjusted to ensure that users camp on the 3G network as long as possible. The possibility that users return from the 2G network to the 3G network increases greatly. Therefore, the inter-RAT cell reselection parameters on the
2013-10-1
Huawei Confidential
Page 20 of 69
Internal Open
2G network may need to be adjusted. Iur interface cooperation Huawei side of the 3G network Cooperation needs to be provided for commissioning and configuration of relevant parameters. Add physical connections. Debug the Iur interface. Provide assistance in identifying Iur interface problems. Configure the core network to support relocation. Engineering experiences Spain Cooperation needs to be provided for commissioning and configuration of relevant parameters. Add physical connections. Debug the Iur interface. Provide assistance in identifying Iur interface problems. Configure the core network to support relocation. Egypt Not involved Not involved
Customer
Configure the core network to support relocation, mainly including users in FACH state and paging channel (PCH) state. For other services, implement mobility by handing over users to the 2G network. Romania and Singapore
Configure the core network to support relocation, mainly including users in FACH state and PCH state. For other services, implement mobility by handing over users to the 2G network.
Italy
2.3.2 Analysis of Huawei Workload

Comparison of daily workload: According to the time reported by current projects, it takes one day to make data, including data making and check, for a cluster of 20 sites. The time consumption of workload varies little. However, in terms of the time consumed in problem locating, swapping with the Iur interface requires much longer time than swapping without the Iur interface. The ascending sequence of the swapping schemes in terms of workload is as follows: Inter-frequency swapping without the Iur interface < intra-frequency swapping without the Iur interface < inter-frequency swapping with the Iur interface < intra-frequency swapping with the Iur interface
2.3.3 Comparison of Swapping Schemes in Terms of Customer Workload and Perception

The ascending sequence of swapping schemes in terms of customer workload, including GSM network cooperation, Iur interface commissioning, and possible unified modification of frequencies, is as follows: Intra-frequency swapping without the Iur interface < inter-frequency swapping without the Iur interface < inter-frequency swapping with the Iur interface < intra-frequency swapping with the Iur interface The following table describes customer perception in different swapping schemes:
2013-10-1
Huawei Confidential
Page 21 of 69
Internal Open
Intra-Frequency Swapping With the Iur interface Customer perception This scheme has no impact on the 2G network. The customer needs to provide assistance for configuration at the Iur interface:
Inter-Frequency Swapping With the Iur interface This scheme has no impact on the 2G network. The customer needs to provide assistance for configuration at the Iur interface:
Without the Iur interface The 2G network of the customer is greatly affected. The customer may feel unsatisfied. The interference is severe, greatly affecting the network KPIs.
Without the Iur interface The 2G network of the customer is greatly affected. The customer may feel unsatisfied. A large number of changes to the 2G network configuration are involved. When the 3G and 2G network maintenance teams of the customer are separated, the customer needs to put great efforts in coordination.
Coordinate personnel for debugging of the Iur interface. Provide assistance in locating Iur interface problems. Coordinate the competitor to modify neighboring cell configuration.
Coordinate personnel for debugging of the Iur interface. Provide assistance in locating Iur interface problems. Coordinate the competitor to modify neighboring cell configuration.
The success rate of inter-frequency hard handover over the Iur interface is low, easily resulting in customer complaints.
2.4 Summary
2.4.1 Information to Be Obtained Through Interaction with the Customer
Frequency resources of the customer. Vendor of the existing core network, and whether relocation is supported. Information about competitor products, including but not limited to: 1. 2. RNC product version to help Huawei analyze the algorithm features and perform the compatibility test Implementation modes of soft handover, inter-frequency handover, and inter-RAT handover, and main KPIs (such as call connection rate and call drop rate)
Policies of interoperation between 3G and 2G networks, including handover and cell reselection policies for CS and PS services between 3G and 2G networks, and interoperation
2013-10-1
Huawei Confidential
Page 22 of 69
Internal Open
policies desired by the customer after swapping
2.4.2 Comparison of Swapping Schemes in Terms of Key Points

IntraFrequency Swapping with the Iur Interface Competitor cooperation
IntraFrequency Swapping Without the Iur Interface When the customer provides continuous coverage of 3G network signals, or cluster division is not separate:
InterFrequency Swapping Without the Iur Interface
InterFrequency Swapping with the Iur Interface Frequency configuration of interRAT neighboring cells at the 2G network side must be modified. The competitor at the 3G network side needs to add Huawei inter-frequency neighboring cells.
Great risks exist in interconnection of Iur interface between vendors. If problems occur, it is probable that Huawei provides patches to solve them. Incompatibility of neighboring cell combination algorithms leads to possible missing neighboring cells. If missing neighboring cells exist, the competitor at the 3G network side needs to modify the neighboring cell configuration, which requires great efforts from Huawei.
The competitor at the 3G network side and the 2G network may need to modify the inter-RAT handover parameters. The competitor at the 3G network side may need to modify the interRAT neighboring cell configuration.
Frequency configuration of inter-RAT neighboring cells at the 2G network side must be modified. When the customer provides continuous coverage of 3G network signals, or cluster division is not separate:
(1) The competitor at the 3G network side and the 2G network may need to modify the inter-RAT handover parameters. (2) The competitor at the 3G network side may need to modify the inter-RAT neighboring cell configuration.
2013-10-1
Huawei Confidential
Page 23 of 69
Internal Open
IntraFrequency Swapping with the Iur Interface Performance The network performance suffers little change when no problems relating to the Iur interface or neighboring cell combination algorithms exist.
IntraFrequency Swapping Without the Iur Interface Compared with interfrequency swapping, performance decline at the border due to increase of intrafrequency interference is obvious, especially for a network with continuous 3G coverage. This swapping scheme has certain impact on the CS traffic volume of the 3G network and perception of users at the border.
InterFrequency Swapping Without the Iur Interface This swapping scheme has great impact on the CS traffic volume of the 3G network and perception of users at the border.
InterFrequency Swapping with the Iur Interface The implementation effects of interfrequency hard handover with the Iur interface are not satisfactory. The perception of users at the border of the 3G network will also be affected.
2.5 Suggestions on Selecting a Swapping Scheme

Based on the preceding analysis, during actual selection of a swapping scheme, consider the following key factors: 1. 2. Cooperation with the competitor, such as neighboring cell combination algorithm Whether problems occur in Iur interface interconnection (if so, Huawei needs the competitor to provide assistance. It may take a certain period of time for Huawei to provide patches to solve these problems which may be caused by errors of the competitor. During this period, the customer must tolerate a certain decline in network performance) Available frequency resources of the customer (if the resources are insufficient, interfrequency swapping cannot be implemented) Efforts taken by the competitor and the customer in modifying the configuration Sensitivity of the customer on decline of the network performance, user perception, and traffic volume (for whole network swapping, such decline is temporary)
3. 4. 5.
For inter-frequency swapping without the Iur interface, factors 3, 4, and 5 need to be considered. For intra-frequency swapping with the Iur interface, factors 1 and 2 need to be considered. For intra-frequency swapping without the Iur interface, factors 4 and 5 need to be considered. For inter-frequency swapping with the Iur interface, factors 1, 2, 3, 4, and 5 need to be considered. When performance factors and engineering workload are considered, the descending sequence
2013-10-1
Huawei Confidential
Page 24 of 69
Internal Open
of swapping schemes in terms of priority level is as follows: Inter-frequency swapping without the Iur interface > intra-frequency swapping with the Iur interface > intra-frequency swapping without the Iur interface > inter-frequency swapping with the Iur interface If frequency resources are sufficient, inter-frequency swapping without the Iur interface is recommended; otherwise, intra-frequency swapping with the Iur interface is recommended. Intra-frequency swapping without the Iur interface is not recommended. Inter-frequency swapping with the Iur interface should be avoided.
2013-10-1
Huawei Confidential
Page 25 of 69
Internal Open
Analysis and Solution for
Algorithm Differences Between Huawei and NSN

This chapter describes the differences on the algorithms provided by Huawei and other vendors. For details about parameter mapping, see the WCDMA RAN 11 Network Performance Parameter Mapping (Huawei and NSN) and WCDMA RAN 11 Network Performance Parameter Mapping (Huawei and Ericsson). For details about the KPI differences and mapping rules, see the WCDMA RAN 11 Network Performance KPI Mapping (Huawei and NSN) and WCDMA RAN 11 Network Performance KPI Mapping (Huawei and Ericsson).
3.1 Mapping of NSN Key Features

The following table lists the key features that require special attention.
2013-10-1
Huawei Confidential
Page 26 of 69
Internal Open
Feature PS 0K access
Parameters on the NSN Side
Remarks
No corresponding switch No DCH 0K switch is found in the parameter associated documents provided by NSN. That is, NSN products may not provide an overall switch for the DCH 0K feature. The High Speed Packet Access (HSPA) resource allocation switch RABDRAEnabled is found in RN5.0. As indicated in the document, if RABDRAEnabled is set to 0, the DCH 0K is established before the HSPA service is established. This switch is not found in the RU20 parameter description document but is found in the RU20 configuration file in XML format. Therefore, you are advised to pay special attention to this switch. The description of RABDRAEnabled when it is set to 0 is as follows: 0 (Disabled): Direct resource allocation for HSPA is not applied but DCH 0/0 kbit/s is allocated and traffic volume measurements started in connection with PS non-realtime (NRT) RAB setup.
Admission algorithm
No corresponding switch No admission algorithm switch is found in the documents provided by NSN. As indicated in the documents provided by NSN, the admission algorithm is enabled by default. Downlink admission of NSN is based on the power, code, and transmission resources, and number of HSPA users. Uplink admission of NSN is based on the combination of power and throughput, number of HSPA users, and base transceiver station (BTS) hardware resources. You are advised to enable the associated resource admission features during swapping. For details about the mapping strategy for admission algorithms, see the Parameter Mapping on Admission Algorithms sheet in the parameter mapping table.
Inter-frequency hard handover Inter-RAT CS handover
No corresponding switch By default, this feature is enabled. RNCoptions The parameter lists the features supported by the RNC. The parameter allows you to query but not set these features. If the query result contains 0, the RNC supports inter-RAT handover. 0 (inter-RAT handover)
2013-10-1
Huawei Confidential
Page 27 of 69
Internal Open
Feature
Parameters on the NSN Side GsmHandoverAMR/Gs mHandoverCS
Remarks The value Yes (1)/Priority (2) indicates that the inter-RAT CS handover is enabled; otherwise, it is disabled. The parameter lists the features supported by the RNC. The parameter allows you to query but not set these features. If the query result contains 0, the RNC supports inter-RAT handover. 0 (inter-RAT handover) The value Yes (1) indicates that the inter-RAT PS handover is enabled; otherwise, it is disabled. The parameter lists the features supported by the RNC. The parameter allows you to query but not set these features. If the query result contains 0, the RNC supports inter-RAT handover. 0 (inter-RAT handover) If the inter-RAT CS handover switch is set to priority (2) or both the inter-RAT PS handover switch and inter-RAT CS handover switch are set to Yes (1), the inter-RAT CS+PS handover is enabled; if not, the inter-RAT CS+PS handover is disabled.
Inter-RAT PS handover
RNCoptions
GsmHandoverNrtPS/Gs mHandoverRtPS Inter-RAT CS+PS handover RNCoptions
GsmHandoverAMR/Gs mHandoverCS
GsmHandoverNrtPS/Gs mHandoverRtPS High Speed Downlink Packet Access (HSDPA) interfrequency hard handover RNCoptions The parameter lists the features supported by the RNC. The parameter allows you to query but not set these features. If the query result contains 77, the RNC supports HSDPA interfrequency hard handover. The value Enabled (1) indicates that the HSDPA serving cell can be changed. The value Used (0) indicates that the compressed mode is enabled.
HSDPAMobility CMmasterSwitch
2013-10-1
Huawei Confidential
Page 28 of 69
Internal Open
Feature HSDPA
Parameters on the NSN Side HSDPAcapability HSDPAenabled HSDSCHOpState
Remarks HSDPAcapability: The value 0 indicates that the HSDPA service is supported. The value 1 indicates that the HSDPA service is disabled. The value 255 indicates that the HSDPA service is not configured. HSDPAenabled: The value 1 indicates that the HSDPA service is enabled. The value 0 indicates that the HSDPA service is disabled. HSDSCHOpState: The value 0 indicates that the HSDPA service is supported. The value 1 indicates that the HSDPA service is disabled. The value 255 indicates that the HSDPA service is not configured. If any of the three parameters is set to 1, the cell does not support HSDPA services. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide.
HSDPA L2 enhancement
FRLCEnabled
FRLCEnabled: The value 1 indicates that the HSDPA L2 enhancement service is enabled. The value 0 indicates that the HSDPA L2 enhancement service is disabled. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide.
HSDPA 64QAM HSDPA64QAMallowed HSDPA64QAMallowed: The value 1 indicates that the HSDPA 64QAM is enabled. The value RNCOptions 0 indicates that the HSDPA 64QAM is disabled. RNCOptions: The options containing the ID 95 indicate that the HSDPA 64QAM is supported. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide. HSDPA MIMO MIMOEnabled RNCOptions MIMOEnabled: No description of the parameter is found in the parameter description documents provided by NSN. According to the basic configuration rules of NSN, the value 1 indicates that MIMO is enabled and the value 0 indicates that MIMO is disabled. RNCOptions: The options containing the ID 104 indicate that the HSDPA MIMO is supported. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide.
2013-10-1
Huawei Confidential
Page 29 of 69
Internal Open
Feature DC HSDPA
Parameters on the NSN Side DCellHSDPAEnable RNCOptions
Remarks DCellHSDPAEnable: No description of the parameter is found in the parameter description documents provided by NSN. According to the basic configuration rules of NSN, the value 1 indicates that dynamic cell (DC) HSDPA is enabled and the value 0 indicates that DC HSDPA is disabled. RNCOptions: The options containing the ID 106 indicate that the DC HSDPA is supported. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide.
HSUPA
EDCHCapability HSUPAEnabled EDCHOpState
EDCHCapability: The value 0 indicates that the High Speed Downlink Packet Access (HSUPA) service is supported. The value 1 indicates that the HSUPA service is disabled. The value 255 indicates that the HSUPA service is not configured. HSUPAEnabled: The value 1 indicates that the HSUPA service is enabled. The value 0 indicates that the HSUPA service is disabled. EDCHOpState: The value 0 indicates that the HSUPA service is supported. The value 1 indicates that the HSUPA service is disabled. The value 255 indicates that the HSUPA service is not configured. If any of the three parameters is set to 1, the cell does not support HSUPA services. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide.
HSUPA 2ms transmission time interval (TTI)
HSUPA2MSTTIEnabled HSUPA2MSTTIEnabled: The value 1 indicates that the 2 ms TTI is enabled. The RNCOptions value 0 indicates that the 2 ms TTI is disabled. RNCOptions: The options containing the ID 94 indicate that the 2 ms TTI is supported. For details about the feature activation and application methods of Huawei, see the RAN Feature Activation Guide.
Proactive reThe value of T314 is not As described in the documents provided by establishment of 0 and the version is NSN, the feature of proactive re-establishment CS calls RU10 or later. of CS calls is mentioned in the T314 parameter and no feature switch is found. When the T314 parameter is set to a value other than 0, the feature is enabled.
2013-10-1
Huawei Confidential
Page 30 of 69
Internal Open
Feature
Parameters on the NSN Side
Remarks
Proactive reThe value of T315 is not As described in the documents provided by establishment of 0 and the version is NSN, the feature of proactive re-establishment PS connections RAS06 or later. of PS connections is mentioned in the T315 parameter and no feature switch is found. When the T315 parameter is set to a value other than 0, the feature is enabled.
3.2 Automatic Neighboring Cell Adding Algorithm

3.2.1 Difference
The NetAct module provided by NSN (similar to Huawei M2000) offers the automatic neighboring cell adding function. The function is different from the neighboring cell combination function provided by Huawei. Huawei plans to provide a similar function in R15.
After the swapping for Greece WIND and Italy WIND that replaces NSN RU10s, the call drop rate increases drastically as the neighboring cells of a large number of cells are not completely configured. The call drop rate decreases to the level before swapping after the neighboring cells are added. The following table describes the positive and negative impact on the KPIs: Function Automatic neighboring cell adding function Benefit on KPIs The CS call drop rate is decreased. Impact on KPIs Not found.
2013-10-1
Huawei Confidential
Page 31 of 69
Internal Open
3.2.2 Solution
The solutions to the impact caused by this difference are as follows: 1. 2. 3. Map the neighboring cell configuration on the original network to the target network. The iSwap is recommended. Use tools such as the U-net to collect the neighboring cell configuration data before swapping. Use the Nastar to optimize the neighboring cell configuration after swapping.
The automatic neighboring cell adding function is planned in R15.
3.3 Inter-Frequency Inter-RAT Handover Algorithm

3.3.1 Difference
The inter-frequency inter-RAT handover algorithm provided by Huawei is similar to that provided by Ericsson, but varies greatly from that provided by NSN. The implementation principles of the inter-frequency inter-RAT handover algorithm provided by NSN are as follows: 1. 2. Events 1F and 1E are used to enable and disable the compressed mode respectively. You can configure only one set of compressed mode enabling and disabling thresholds. However, you can set to trigger the inter-frequency handover or inter-RAT handover based on Ec/Io or RSCP. If a UE in the poorly covered area of the NSN network reports event 1F, the link is turned in to the compressed mode for GSM measurement and handover. Even when the signal becomes better, such as event 1E is reported, the link remains in the compressed mode. The link disables the compressed mode only after the UE cannot detect a GSM cell meeting the conditions after a given time threshold (10 to 20 seconds). According to the customers, the inter-RAT handover is triggered based on the peak and trough values of the GSM signals. However, no clear evidence on the implementation principle is found.
3.
4.
The principles of the inter-frequency inter-RAT handover algorithm provided by Huawei are as follows: 1. 2. Events 2D and 2F are used to enable and disable the compressed mode respectively. The compressed mode enabling and disabling thresholds for the inter-RAT handover and for the inter-frequency handover are configured independently. If the compressed mode enabling and disabling thresholds for both types of handovers are configured, only one set of thresholds can be issued. After a UE reports event 2D, the inter-RAT measurement is triggered. When a UE reports event 2F, the RNC stops the compressed mode and the inter-RAT measurement is stopped on the UE. The 3G signals are preferred for UEs when the signal quality is good. The inter-RAT handover is triggered based on the average value of the GSM signals.
3.
4.
In summary, in the compressed mode algorithm provided by NSN, the GSM measurement and handover is executed on the UE when the signal quality fluctuation of the UE at the cell edge
2013-10-1
Huawei Confidential
Page 32 of 69
Internal Open
meets the compressed mode threshold. On Huawei networks, when the average signal quality on the air interface measured by the UE is lower than the event 2D threshold, the GSM measurement and handover decision is made on the UE. This is because both events 2D and 2F are used. In this case, with same thresholds, the GSM measurement and handover triggered on Huawei networks is later than that triggered on NSN networks.
3.3.2 Solution
In swapping of NSN RAS5, RU10, or RU20, set the inter-frequency inter-RAT handover thresholds same as the original ones because the compressed mode enabling/disabling thresholds of NSN for inter-frequency handovers and for inter-RAT handovers are the same. Set the event 2D/2F threshold 2 to 3 dB higher than the event 1F/1E threshold on the original network. In addition, the equivalent configuration of the HYSTFOR2D/2F parameter on NSN networks is not found. According to the drive test in multiple offices, the value is 0 on NSN networks. The default value is 4 on Huawei networks. You are advised to set it to 0 during swapping. Fine adjustment may be required for the parameter. You are advised to adjust the parameter based on the principle that the number of inter-RAT handover attempts or the handover attempt ratio is close to the original one. In the following office optimization case, the event 2D/2F threshold is configured to -109dbm/-108dbm, which is the same as the original one. After swapping, the traffic volume increases drastically, the inter-RAT handover attempt ratio decreases, the call drop rate increases from 0.25% to 0.33%. After the event 2D/2F threshold is changed to -104 dBm/-101 dBm, the inter-RAT handover attempt ratio is slightly higher than the original one and the CS call drop rate is smaller than the original one.
The handover attempt ratio is the ratio between the number of voice service inter-RAT handover attempts and the number of voice service establishment attempts. In this case, after the event 2D/2F threshold is increased by 5 dB, the handover attempt ratio is higher than the original one. Therefore, you are recommended to increase the event 2D/2F threshold by 2 to 3 dB.
3.4 HSPA Compressed Mode

3.4.1 Difference
The HSPA compressed mode supported by Huawei greatly differs from that supported by NSN. The implementation principles of the compressed mode provided by NSN are as follows: 1. 2. Events 1F and 1E are used to enable and disable the compressed mode respectively. The HSDPA inter-frequency handover is controlled by the license HSDPA InterFrequency Handover as well as the parameters HSDPAMobility and CMmasterSwitch.
Huawei Confidential Page 33 of 69
2013-10-1
Internal Open
If HSDPAMobility is set to 1, CMmasterSwitch is set to 0, and the RNCoptions list contains 77 (HSDPA inter-frequency handover), the HSDPA inter-frequency handover is supported and the HSDPA compressed mode is also supported. If the HSDPA interfrequency handover is not supported, the compressed mode is supported over H2D transition. That is, when a UE in the poorly covered area reports event 1F, the UE is transited to the DCH state. 3. The RU20 and earlier versions do not support the HSUPA compressed mode. The compressed mode is supported over E2D transition. That is, when a UE in the poorly covered area reports event 1F, the UE is transited to the DCH state. The RU20 does not support the UPA compressed mode. For details, see the following quotation from the description of HSDPA inter-frequency handover in NSN documents: If the HSDPA Inter-Frequency Handover feature is enabled, quality and coverage based HSDPA inter-frequency handovers are performed as follows:

If HS-DSCH/DCH with or without AMR is allocated, compressed mode and interfrequency measurement is started directly without transport channel modification. If HS-DSCH/E-DCH with or without AMR is allocated, uplink transport channel modification to HS-DSCH/DCH configuration is performed first and after that compressed mode and inter-frequency measurement are started immediately.
During uplink transport channel modification to HS-DSCH/DCH configuration, DCH(s) are allocated with initial bit rate. 4. According to the test result of the network in Australia, during the E2D transition on the NSN network, the UEs may be transited to the DCH (0/0K) state.
The implementation principles of the compressed mode provided by Huawei are as follows: 1. 2. 3. 4. Events 2D and 2F are used to enable and disable the compressed mode respectively. The HSDPA compressed mode is controlled by the HsdpaCMPermissionInd parameter. The HSUPA compressed mode is controlled by the HsupaCMPermissionInd parameter. During channel state transition, the UEs are not transited to the DCH (0/0k) state.
In summary, if the NSN network does not support the HSDPA compressed mode, the UEs in poorly covered areas trigger event 1F easily and many UEs are transited to the DCH state. This affects the HSDPA handover success ratio and other network KPIs. The following table describes the positive and negative impact on the KPIs: KPI HSDPA Throughp ut HSDPA Throughp ut Number of HSDPA Users HSDPA Call Drop Rate End User Experienc e
Result
indicates a positive impact and indicates a negative impact.
In the default configuration, the HSDPA compressed mode is supported on Huawei networks. In poorly covered areas, UEs are not transited to the DCH state. If the default configuration is used, the HSDPA associated KPIs vary greatly with the original ones. For the HSUPA service, the UEs in poorly covered areas trigger event 1F easily and many UEs are transited to the DCH state. This affects the HSUPA handover success ratio and other
2013-10-1 Huawei Confidential Page 34 of 69
Internal Open
network KPIs. The following table describes the positive and negative impact on the KPIs: KPI HSUPA Throughp ut HSUPA Throughp ut Number of HSUPA Users HSUPA Call Drop Rate End User Experienc e
Result
In the default configuration, the HSUPA compressed mode is supported on Huawei networks. In poorly covered areas, UEs are not transited to the DCH state. If the default configuration is used, the HSUPA associated KPIs vary greatly with the original ones.
3.4.2 Solution
The coverage-based E2D transition is supported by Huawei products. The feature improves the establish success ratio and decreases the overall PS call drop rate. Therefore, you are advised not to disable the HSPA compressed mode function on Huawei products. The following solution is recommended: 1. Guide the customers to understand the differences between the HSPA bearing strategies of Huawei and other vendors, and to focus on the overall PS call drop rate rather than the PS Release 1999 (R99), HSDPA, and HSUPA call drop rates. The coverage-based E2D transition is supported by Huawei products. The HSUPA service in poorly covered areas is switched to the DCH state. This feature improves the establish success ratio and decreases the overall PS call drop rate, but increases the R99 call drops. Obtain the E2D enabling guide from the HQ or R&D contacts. Optimize the associated parameters based on the WCDMA RAN13 Network Performance Parameter Mapping. During the E2D transition on the NSN network, the UEs are be transited to the DCH (0/0K) state without data transmission. This does not improve user experience. On the Huawei network, the DCH (0/0k) is not supported. Therefore, the effect of the E2D function enabled on the NSN network and that of the Huawei network are different. You are advised to guide the customers to focus on the overall PS call drop rate.
2.
3.5 Simultaneous Issuance of Intra- and InterFrequency Handover Measurement Reports

3.5.1 Difference
The drive test proves that the NSN network issues two measurement control reports when the compressed mode is enabled: intra-frequency handover measurement control ID8 and interfrequency handover measurement control ID9. In addition, the ID8 intra-frequency handover measurement report is submitted with the inter-frequency handover measurement report through the additionalMeasurementList in unacknowledged mode in periods of 250 ms. The following table describes the positive and negative impact on the KPIs:
2013-10-1
Huawei Confidential
Page 35 of 69
Internal Open
Benefit on KPIs The inter-frequency handover success ratio and user experience are improved.
Impact on KPIs Not found.
No associated control parameters are found on NSN products. However, according to the statistics obtained during the drive tests on multiple offices, NSN products use this method to improve the inter-frequency handover success ratio and user experience.
3.5.2 Solution
Huawei has improved the inter-frequency hard handover principles on products. The simultaneous issuance of intra-/inter-frequency handover measurement commands is implemented. For example, the solution will be implemented on the commercial network in Canada. Therefore, the commercial verification result in terms of actual benefits of the solution is not available. The solution is not tried during network swapping. If the success ratio of inter-frequency hard handover fails to reach the level before swapping, you are advised to optimize the inter-frequency neighboring cell planning and handover thresholds before using this solution. If this solution is required, follow the feature implementation beta process. The associated settings on the commercial network in Canada are as follows: SET UCORRMPARA: ReservedSwitch0=RESERVED_SWITCH_0_BIT9-1; SET UCORRMPARA: ReservedU8Para1=18; SET UCORRMPARA: ReservedU8Para0=0;
3.6 Asynchronous Inter-Frequency Hard Handover

3.6.1 Difference
The physical channel reconfiguration for inter-frequency hard handover uses the asynchronous mode on NSN products. On Huawei products, the synchronous mode is used. That is, Huawei products search for cells of different frequencies about one second (activation period) after the UE receives the HHO command; and NSN products search for cells of different frequencies directly after the UE receives the HHO command. In the activation period, the signals on the two frequencies may change. The following table describes the positive and negative impact on the KPIs: Benefit on KPIs The handover delay is shorter, and the handover success ratio and call drop rate are improved. Impact on KPIs Not found.
2013-10-1
Huawei Confidential
Page 36 of 69
Internal Open
No associated control parameters are found on NSN products. However, according to the statistics obtained during the drive tests on multiple offices, NSN products use this method to improve handover success ratio and call drop rate.
3.6.2 Solution
Huawei has improved the inter-frequency hard handover principles on UMTS R13 C00SPC550. The asynchronous mode is used for inter-frequency hard handover. For example, the solution will be implemented on the commercial network in Canada. Therefore, the commercial verification result in terms of actual benefits of the solution is not available. If the success ratio of inter-frequency hard handover fails to reach the level before swapping, you are advised to optimize the inter-frequency neighboring cell planning and handover thresholds before using this solution. If this solution is required, follow the feature implementation beta process. The associated settings are as follows: SET URRCTRLSWITCH: CS_HHO_ASYNC_CTRL_SWITCH-1, PS_HHO_ASYNC_CTRL_SWITCH-1, IUR_HHO_ ASYNC_CTRL_SWITCH-1;
3.7 Inter-Frequency Handover Preference

3.7.1 Difference
On NSN products, when both inter-frequency handover and inter-RAT handover are available, the inter-frequency handover is preferred if the RNC does not receive the Service Handover IE message. On Huawei UMTS products earlier than R14, the inter-frequency handover and the inter-RAT handover measurement reports are issued in the preceding case, and the handover action of the first measurement report is executed. On Huawei products, the handover delay is shorter and the UE is easily handed over to a GSM network in special scenarios, such as indoor distribution scenarios. For example, during the swapping for Telenor in Serbia, when a UE moves from the indoor distribution area to the outdoor distribution area, the UE is easily handed over to the neighboring GSM cell even when the 3G inter-frequency neighboring cells have strong signals. Frequent inter-RAT handover may raise customer complaint. The following table describes the positive and negative impact on the KPIs: Benefit on KPIs The ratio of inter-frequency handover to inter-RAT handover is improved. Impact on KPIs The handover success ratio may decrease slightly.
3.7.2 Solution
On Huawei UMTS products earlier than R14, to implement inter-frequency handover preference, modify the TimeToTrigForVerify or TimeToTrigForNonVerify parameter to reduce the ratio of inter-RAT handover. If you modify either of the two parameters, the call drop rate may increase. Therefore, do not set the parameter to a too large value. You can
Internal Open
modify the parameter using the MOD UCELLINTERRATHOCOV command as follows: MOD UCELLINTERRATHOCOV: TimeToTrigForVerify=, TimeToTrigForNonVerify= In Huawei UMTS R14 or later, you can enable the CsHoPrioMeasTimerLen and PsHoPrioMeasTimerLen timers to implement inter-frequency handover preference. The UMTS R14 is not yet released. Therefore, seek help from R&D departments following the version help process if commercial use is required.
3.8 Hierarchical Cell Selection and Reselection

3.8.1 Difference
The hierarchical cell selection (HCS) algorithms of different vendors are implemented based on the protocol and they do not have essential differences, which is similar to the hierarchical cell reselection (HCR) algorithms of different vendors. Few Huawei offices use HCS algorithms and most offices use the HCR reselection parameter offset solution to implement HCS.
3.8.2 Solution
Few Huawei networks use HCS algorithms. If the original network of the swapping project uses the HCS algorithm for reselection, you are advised not to use the HCS solution for swapping. You are advised to use the HCR reselection parameter offset solution to match the objective of the original network or customer requirements. To map or analyze the HCS solution, follow the process through the GTAC. The HCS algorithm can also be implemented with the HCR reselection parameter offset solution. The following is an example on the SFR network in France:
Networking and Customer Requirements

Figure 1.1 Networking in idle mode
2013-10-1
Huawei Confidential
Page 38 of 69
Internal Open
Figure 1.2 Networking in connected mode
As shown in the preceding figures, the GSM full coverage is implemented, the UMTS systems implement R99 and HSXPA services, and the hot spot areas are deployed with the Femto. 1. 2. 3. 4. In networking scenarios with Femto cells and macro cells, the SFR requires the HCS algorithm for cell reselection. In networking scenarios with U2100 F0 and U900 macro cells in blind compensation mode, the HCS algorithm is not required for cell reselection. In networking scenarios with U2100 F0, F1, and F2 macro cells, the U2100 F1 and F2 are barred. Therefore, cell reselection is not involved among multi-carrier U2100 cells. In application scenarios in idle mode with Femto cells and macro cells, the HCS algorithm is required. The SFR requires that the camp-on priority vary with the signal quality of the macro cell. That is, when the RSCP of the macro cell is below the threshold, all the neighboring cells are measured; when the RSCP of the macro cell is greater than the threshold, the neighboring cell with the higher priority is measured. By default, the UEs are in low-speed state.
5.
Configuration of Cell Reselection Parameters on NSN Cells of SFR

The macro network of the SFR in France is constructed based on NSN products before swapping. The configuration of cell reselection parameters on these products is as follows: 6. 7. The HCR algorithm does not differ with the idle or connected mode. In addition, the setting of HCS_Prio is the same for macro cells and Femto cells. The SIB12 and SIB11 are enabled. The SIB11 of macro cells includes Femto cells and the SIB12 of macro cells does not include Femto cells. In this case, reselection from a macro cell to a Femto cell is not implemented for UEs in FACH or PCH state. The Femto network is constructed based on NEC products. The HCS parameters are configured as followings: HCS_Prio=1; QHCS=-12dB; Qrxlevmin=-58(-115dbm);
8.
2013-10-1
Huawei Confidential
Page 39 of 69
Internal Open
SearchHCS=5(-105dBm); UseofHCS=used; The cell reselection solution of NSN achieves the following effect: When the UE camps on the macro network, the inter-frequency measurement is initiated in Femto cells if the RSCP of the macro cell is not greater than -65 dBm. If the Ec/N0 of the Femto cell is greater than -12 dB, the UE camps on the Femto cell. If the RSCP of the macro cell is greater than -65 dBm, the UE camps on the macro cell.
Configuration of Cell Reselection Parameters After Swapping

For smooth swapping, the setting of HCS_Prio must be the same for the macro cells and Femto cells and SIB12 is set to False for the connected mode to prevent the reselection from macro cells to Femto cells for the FACH or PCH state. The following configuration for macro cells is recommended based on the preceding principle: ADD CELLSELRESEL: Qrxlevmin=-58(-115dbm), IdleSintersearch=?, Qqualmin=?; ADD CELLHCS: HCS_Prio=1; QHCS=-24dB; SearchHCS=25(-65dBm); UseofHCS=used; TempOffset2=2dB; TpenaltyHcsReselect=0; ADD INTERFREQNCELL: RncId=HW_RNC, CellId=HW_Cell, NCellRncId=Femto_RNC, NCellId=Femto_Cell, SIB11Ind=TRUE, IdleQoffset2sn= -50, SIB12Ind=FALSE; Under the preceding configuration, when the RSCP of the macro cell is smaller than or equal to -65 dBm or the Ec/N0 is smaller than or equal to IdleSintersearch+Qqualmin, cells of both the same and different frequencies are measured. When the Ec/N0 of the Femto cell is greater than -12 dB, reselection from the macro cell to the Femto cell is implemented. When the RSCP of the macro cell is smaller than or equal to -65 dBm, the UE camps on the UMTS cell unconditionally. In this case, the camp-on priority varies with the signal quality of the macro cell, meeting the requirements of SFR. If the UE does not support the HCS, the requirements of SFR are not satisfied. Therefore, the reselection parameter offset solution is used to guarantee the Qqualmin/Qrxlevmin thresholds of the neighboring cell quality. The parameter settings are as follows: MOD NRNCCELL: NRncId=Femto_RNC, CellId=Femto_CellID, QqualminInd =TRUE, Qqualmin=-12, UseOfHcs=NOT_USED; Or MOD NRNCCELL: NRncId=Femto_RNC, CellId=Femto_CellID, QrxlevminInd=TRUE, Qrxlevmin=-48(-95dbm), QrxlevminExtSup=FALSE, UseOfHcs=NOT_USED; This requires that the Ec/N0 of the Femto cell be greater than 12 dB or its RSCP be greater than -95dBm during the reselection from the macro cell to the Femto cell. In summary, to fulfill the requirements of SFR on HCS-based cell reselection, Huawei uses the following strategies: 9. When the UE supports HCS-based reselection, the preceding settings on the macro cells are used.
10. When the UE does not support HCS-based reselection, to achieve the same effects, the neighboring cell quality (using the Qqualmin/Qrxlevmin thresholds) guarantee solution is used.
2013-10-1
Huawei Confidential
Page 40 of 69
Internal Open
3.9 PS 0K Access
3.9.1 Difference
The PS RAB setup success ratio on the NSN network before swapping is high, even achieving 99.99%. This is because of the PS 0K access feature provided by NSN.
With this feature, the PS RAB is in two steps: First, the RAB of the UE is set up and mapped to the DCH 0/0k. Then, the RAB is allocated to the DCH or H after event 4A. You can check whether this feature is enabled through the UE tracing statistics obtained during a drive test. The PS RAB setup success ratio is greatly improved after this feature is enabled for the following reasons: 1. 2. No admission control is performed for PS 0K requests. In this case, there is no admission failure for PS 0K requests. The size of an RAB message of a PS 0K request is reduced by 2/3. In this case, the required channel quality is lower. If the RAB message is not successfully sent during the
2013-10-1
Huawei Confidential
Page 41 of 69
Internal Open
initial transmission, it can be resent for multiple times. The PS 0K access feature only improves the PS RAB setup success ratio; it increases the delay and does not improve user experience. 1. The delay after the UE initiates an access request and before the applied service is available (for example, the Web page is open) is increased. For example, when the user is browsing news on the Web page, each time a page is displayed, the user needs to wait for at least 10 seconds to open another page. This is because that the UE is transited to the idle mode without data transmission. Each time the user opens a page, the process of RRC request, PS 0K setup, and service volume based channel re-allocation are went through. Therefore, each time a new page is displayed, a 1.2 seconds delay is added. In this case, the Web page is displayed slowly on the user side. (The page is displayed in one to two seconds.) If the admission fails from PS 0K setup to service channel configuration, the UE remains in the PS 0K state without any services available. In this case, the user can make calls but cannot access data services.
2.
No DCH 0K switch is found in the parameter associated documents provided by NSN. That is, NSN products may not provide an overall switch for the DCH 0K feature. The HSPA resource allocation switch RABDRAEnabled is found in RN5.0. As indicated in the document, if RABDRAEnabled is set to 0, the DCH 0K is established before the HSPA service is established. This switch is not found in the RU20 parameter description document but is found in the RU20 configuration file in XML format. Therefore, you are advised to pay special attention to this switch. The description of RABDRAEnabled when it is set to 0 is as follows: 0 (Disabled): Direct resource allocation for HSPA is not applied but DCH 0/0 kbit/s is allocated and traffic volume measurements started in connection with PS NRT RAB setup.
3.9.2 Solution
Based on the preceding analysis, you are advised to make a fair benchmark using the following methods for NSN RU10 or earlier versions with the PS 0K access feature enabled (if the PS RAB setup success ratio is greater than 99.9% during the drive test, the PS 0K access feature is enabled): 1. Disable the PS 0K access feature on the NSN network before making the benchmark. In this case, the PS RAB setup success ratio on the NSN network matches the following baseline formula of Huawei: [(RAB_ACC_COMP_PS_INTER+RAB_ACC_COMP_PS_BACKG)/ (RAB_STP_ATT_PS_INTER+RAB_STP_ATT_PS_BACKG)] 2. If the customer does not agree to method 1, advise the customer to change the formula of NSN to <PS 0K setup success ratio>*<RB re-allocation success ratio> as follows: [(RAB_ACC_COMP_PS_INTER+RAB_ACC_COMP_PS_BACKG)/ (RAB_STP_ATT_PS_INTER+RAB_STP_ATT_PS_BACKG)]*[(D_D_REQ_D_D_AL LO_INT+D_D_REQ_D_D_ALLO_BGR+HS_E_REQ_HS_E_ALLO_INT+HS_E_RE Q_HS_E_ALLO_BGR+HS_E_REQ_HS_D_ALLO_INT+HS_E_REQ_HS_D_ALLO_ BGR+HS_D_REQ_HS_D_ALLO_INT+HS_D_REQ_HS_D_ALLO_BGR+HS_E_REQ _D_D_ALLO_BGR_CELL+HS_E_REQ_D_D_ALLO_INT_CELL+HS_D_REQ_D_D _ALLO_BGR_CELL+HS_D_REQ_D_D_ALLO_INT_CELL)/ (PS_ATT_DCH_DCH_INT+PS_ATT_DCH_DCH_BGR+PS_ATT_HSDSCH_EDCH_I NT+PS_ATT_HSDSCH_EDCH_BGR+PS_ATT_HSDSCH_DCH_INT+PS_ATT_HSD SCH_DCH_BGR)]
2013-10-1
Huawei Confidential
Page 42 of 69
Internal Open
NSN does not provide a dedicated statistical formula for DCH 0/0 kbit/sDCH x/y kbit/s or DCH 0/0 kbit/sHSPA re-allocation. The RB re-allocation success ratio covers the success ratio of FACHDCH x/y or HSPA re-allocations. The calculation result can be treated as an approximate value of the PS RAB setup success ratio. The formula for calculating the PS RAB setup success ratio of Huawei is as follows: (VS.RAB.SuccEstabPS.Bkg + VS.RAB.SuccEstabPS.Inter)/(VS.RAB.AttEstabPS.Bkg + VS.RAB.AttEstabPS.Inter)
3.10 Proactive Re-establishment of CS Calls

3.10.1 Difference
The new feature RRC Re-establishment for Real Time Services in NSN RU10 enables proactive re-establishment of CS calls. The feature description is as follows in NSN feature description documents: Feature RAN1730: RRC re-establishment for real time services is automatically available after RU10 software installation if the T314 parameter is set. The feature is active when the parameter T314 has a value larger than zero. In an office, for example, after the feature is enabled on the NSN network before the swapping, the call drop rate decreases from 0.6% to 0.3%. 1. The following figure shows that all links wait for synchronization timeout after they lose synchronization on the uplink.
2013-10-1
Huawei Confidential
Page 43 of 69
Internal Open
2.
The following figure shows the SRB reset on the RNC side:
In the preceding scenarios, the RNC actively releases the Iu interface (Iu Release Req) and takes it into the calculation of the call drop rate. NSN supports proactive re-establishment of PS services from RAS06 and supports proactive re-establishment of CS calls in RU10. The implementation process is unclear. NSN also supports link re-establishment for UE SRB resets in versions earlier than RU10. In the earlier versions, Huawei does not support re-establishment for UE SRB resets. The cell releases the connection right after it receives an SRB reset signal from the UE. The proactive re-establishment is beneficial for scenarios where signals change suddenly, for example, the user is on a driving car and enters an area that is not covered. In this case, the signal is lost for a short period. Without the proactive re-establishment function, the call drops; with the proactive re-establishment function, the call continues after the UE enters an area that is not covered. However, the feature may cause the following problems: 1. The proactive re-establishment of voice services brings a long mute period, about 8 to 16 seconds. Users may hang up the phone during the mute period even the re-establishment is successful. Though the call drop rate does not take the re-established service into calculation, the user experience is not improved. The feature is beneficial to call drops caused by signal loss due to network problems. However, for these call drops, the proactive re-establishment function is a countermeasure for network problems but may affect long-term network optimization.
2.
3.10.2 Solution
The parameters or commands for enabling the RRC Re-establishment for Real Time Services feature on NSN products are unclear. If T314 is not 0, and the NSN product is RU10 or later, the RRC Re-establishment for Real Time Services feature for CS services may be enabled. If T315 is not 0, and the NSN product is RAS06 or later, the RRC Re-establishment for Real
2013-10-1
Huawei Confidential
Page 44 of 69
Internal Open
Time Services feature for PS services may be enabled. The following solutions are recommended for NSN networks with the proactive re-establishment function enabled: 1. Disable the RRC Re-establishment for Real Time Services feature on the NSN network before making the benchmark. This is because the proactive re-establishment causes a long mute period during which network abnormalities are covered up. This may affect long-term network optimization. The proactive re-establishment function and proactive re-establishment for UE SRB resets are implemented in Huawei V900R011C03 and V900R013C03. If the customer insists on proactive re-establishment and has high requirements on the call drop rate, apply for associated versions and functions. No official documents on describing how to enable the proactive re-establishment function are available. You can obtain suggestions from the GTAC. For details about the associated parameters, see the WCDMA RAN13 Network Performance Parameter Mapping.
2.
3.11 RRC Call Drop Rate

3.11.1 Difference
The NSN network has verification requirements on the RRC call drop rate. The calculation formula is as follows:
sum([RRC_CONN_ACT_REL_P_EMP]+[RRC_CONN_ACT_FAIL_IU]+[RRC_CONN_ACT_FAIL_RADIO]+ [RRC_CONN_ACT_FAIL_BTS]+[RRC_CONN_ACT_FAIL_IUR]+[RRC_CONN_ACT_FAIL_RNC]+ [RRC_CONN_ACT_FAIL_UE])/sum([RRC_CONN_ACT_COMP]+[RRC_CONN_ACT_REL_SRNC]+ [RRC_CONN_ACT_REL_GANHO ]+[RRC_CONN_ACT_REL_HHO ]+[RRC_CONN_ACT_REL_INTRA_HHO ]+ [RRC_CONN_ACT_REL_ISHO ]+[RRC_CONN_ACT_REL_P_EMP]+[RRC_CONN_ACT_FAIL_IU]+ [RRC_CONN_ACT_FAIL_RADIO]+[RRC_CONN_ACT_FAIL_BTS]+[RRC_CONN_ACT_FAIL_IUR] + [RRC_CONN_ACT_FAIL_RNC]+[RRC_CONN_ACT_FAIL_UE])
According to the test statistics from Hongkong, only some abnormalities are counted in the calculation formula on the NSN network. See the following table:
On Huawei products, the RRC connection releases are measured (RRC.Rel.Cell). However, the measurement differs from that of NSN in the following aspects: 1. NSN products count only the abnormal releases of CS services. Huawei products count
2013-10-1
Huawei Confidential
Page 45 of 69
Internal Open
the abnormal releases of both PS and CS services. 2. NSN products do not count the abnormal releases of some CS services, such as the SRB resets triggered by RB setup shown in the red shading in the preceding table. Huawei products count the abnormal releases of both PS and CS services and cannot separate the abnormal releases of different types as NSN products do.
Therefore, the KPIs of Huawei products do not match those of NSN products.
3.11.2 Solution
According to the test statistics from Hongkong, the NSN statistics are measured in an arbitrary manner. As shown in the preceding table, the SRB resets triggered by RB setup requests issued after RRC connection setup on the network side are not counted in the RRC call drop rate. Therefore, the reasons why the statistics of Huawei and NSN do not match must be clarified and the improperness of NSN statistics is better demonstrated to the customer to convince the customer not to use the RRC call drop rate as an assessment and monitoring indicator for swapping.
3.12 EFD
3.12.1 Difference
With the rapid development of smartphones, smartphones take an increasing proportion in the UEs. Smartphones send heartbeat packets frequently, bringing signaling storms This greatly affects the network capacity and signal handling capability on the network equipment side. Huawei offers the enhanced fast dormancy (EFD) function in the UMTS R12 to solve this problem. However, NSN does not offer signaling storm solutions until the release of RU30. The NSN signaling storm solution is described as follows in the NSN RU30 feature development document:
The EFD feature helps to solve network signaling storms but may deteriorate air interface KPIs for light-loaded networks.
3.12.2 Solution
As NSN RU20 and earlier versions do not support the EFD function, and the EFD function affects air interface KPIs and may cause UE compatibility problems, you are advised not to enable the EFD function during swapping. If the signal processing capability on the
Internal Open
equipment side may not satisfy the service needs, confirm with the representative on the product side whether the EFD function is required. Clarify the risks with the customers before the EFD function is enabled. The EFD function is sold as a professional service. If the EFD function is required, follow the professional service process.
3.13 Scrambling Code Planning

3.13.1 Difference
The scrambling code planning varies with the vendors. Huawei allocates scrambling codes in the same group to the neighboring cells of the same site. Some vendors allocate scrambling codes in different groups to the neighboring cells of the same site. See the following figure.
These two different types of scrambling code planning principles cause different performance in cell searching. The UE searches for the PSC in three steps (timeslot synchronization, frame synchronization, and scrambling code searching). For the two types of scrambling code planning, the first two steps are the same and the third step may be different in performance. The scrambling code planning provided by other vendors does not require the comparison of the main scrambling code on the UE side as the scrambling codes of the neighboring cells are in different scrambling code groups. Therefore, other vendors have an edge over Huawei in scrambling code planning.
3.13.2 Solution
Map the scrambling code planning on the original network to the target network during swapping.
3.14 HSPA User Number Restriction

3.14.1 Difference
Both Huawei and NSN offer HSPA user number restriction policies. NSN products allow telecom operators to control the maximum number of HSDPA users in a cell using the HSDPA48UsersEnabled, HSDPA64UsersEnabled, and
2013-10-1
Huawei Confidential
Page 47 of 69
Internal Open
HSPA72UsersPerCell feature switches, and the number of HSDPA users and HSDSCH MACd flows in a cell using the MaxNumberHSDPAUsers and MaxNumberHSDSCHMACdFlows parameters. Huawei products allow telecom operators to control the maximum number of HSDPA users in a cell using the MaxHsdpaUserNum parameter and the maximum number of HSDPA users in a NodeB using the NodeBHsdpaMaxUserNum parameter. In addition, the number of HSDPA users in a cell is also restricted by the RNC and NodeB licenses. Huawei products do not offer restriction based on the number of HSDSCH MACd flows. The restriction policy on the number of HSDPA users provided by NSN is described as follows according to NSN documents:
NSN products restrict the maximum number of HSUPA users in a cell using the MaxNumberEDCHCell parameter, and restrict the number of HSUPA users in a NodeB local cell group using the HSUPAXUsersEnabled and MaxNumberEDCHLCG parameters. In addition, the number of HSUPA users is also restricted by the license. Huawei products offer the MaxHsupaUserNum parameter to control the maximum number of users in a cell and the number of HSUPA users is restricted by the RNC license. Huawei products do not restrict the number of HSUPA users in a NodeB local cell group. The restriction policy on the number of HSUPA users provided by NSN is described as follows according to NSN documents:
2013-10-1
Huawei Confidential
Page 48 of 69
Internal Open
3.14.2 Solution
The restriction on the number of HSPA users does not accurately map after swapping. The specific number of HSPA users can be calculated based on the license and parameters of the NSN. 1. Maximum number of HSDPA users in a cell The maximum number of HSDPA users in a cell can be calculated using the following formula: MaxHsdpaUserNum=min{max(16, HSDPA48UsersEnabled*48, HSDPA64UsersEnable*64, HSPA72UsersPerCell*72), A, B} Where,

MaxHsdpaUserNum indicates the maximum number of HSDPA users in a cell and is of Huawei products. The elements on the right of the formula are the parameter values configured on NSN products. The HSDPA48UsersEnabled, HSDPA64UsersEnable, and HSPA72UsersPerCell parameters define the maximum number of HSDPA users. When they are set to Not in use (0), a maximum of 16 HSDPA users are allowed by default. If they are set to In use (n), a corresponding number of HSDPA users are allowed at the maximum for the cell on the NSN network. max(16, HSDPA48UsersEnabled*48, HSDPA64UsersEnable*64, HSPA72UsersPerCell*72) indicates the maximum number of HSDPA users allowed for a cell. The MaxNumberHSDPAUsers parameter indicates the maximum number of HSDPA users for a cell and MaxNumberHSDPAUsers indicates the maximum number of HSDSCH MACd flows allowed for a cell. When they are set to 0, the number of HSDPA users and the number of HSDSCH MACd flows are not restricted. The definition of parameter A is as follows: If MaxNumberHSDPAUsers=0 or MaxNumberHSDPAUsers>=128, A=128. If 0<MaxNumberHSDPAUsers<128, A=MaxNumberHSDPAUsers.
The definition of parameter B is as follows: If 0<MaxNumberHSDSCHMACdFlows, B=MaxNumberHSDSCHMACdFlows.
2013-10-1
Huawei Confidential
Page 49 of 69
Internal Open
If MaxNumberHSDSCHMACdFlows=0, B=255. Generally, each HSDPA user is assigned only one HSDSCH MACd flow. Therefore, the parameter B is taken into calculation.
MaxHsdpaUserNum indicates the maximum number of HSDPA users in a cell on the live network.
2.
Restriction on the HSDPA users on the NodeB and license control The number of HSPA users is restricted by not only the cell-level parameter MaxHsdpaUserNum, but also the RNC-level parameter NodeBHsdpaMaxUserNum (maximum number of HSDPA users on the NodeB). In addition, the number of HSPA users is restricted by the license. You are advised to check whether the live network supplied by Huawei is restricted.
3.
Maximum number of HSUPA users in a cell The maximum number of HSUPA users in a cell can be calculated using the following formula: MaxHsupaUserNum=MaxNumberEDCHCell The formula indicates that the MaxHsupaUserNum parameter corresponds to the MaxNumberEDCHCell parameter on the live network supplied by NSN.
4.
Maximum number of HSUPA LCG users NSN products restrict not only the number of users in a cell but also the number of HSUPA users in a NodeB local cell group using the HSUPAXUsersEnabled and MaxNumberEDCHLCG parameters. You are advised to check whether the live network supplied by NSN is restricted.
3.15 Power-Based Uplink Admission Control

3.15.1 Difference
In the power-based uplink admission control algorithm developed by NSN, resource admission is controlled based on the cell throughput and received total wideband power (RTWP). This algorithm features enhanced anti-interference capability for admission. When a cell is affected by external interference, if the cell throughput is within the threshold, admission control is not performed on users that are newly accessed. If the cell throughput exceeds the threshold, the RTWP-based admission control is effective. The description provided by NSN about the power-based uplink DCH admission control is as follows:
2013-10-1
Huawei Confidential
Page 50 of 69
Internal Open
The description provided by NSN about the uplink HSUPA admission control is as follows:
Huawei provides three power-based uplink admission algorithms before the release of R14:

ALGORITHM_FIRST: load prediction algorithm ALGORITHM_SECOND: equivalent user number algorithm ALGORITHM_THIRD: loose admission algorithm
The ALGORITHM_FIRST and ALGORITHM_THIRD algorithms are based on the RTWP, but they do not consider the RTWP increase caused by external interference. Compared with the algorithms developed by NSN, the algorithms developed by Huawei feature more admission failures under the same external interference and the same load. As a result, the RAB setup success ratio on the Huawei network is lower than that on the NSN network.
3.15.2 Solution
The RTWP anti-interference algorithm is added in Huawei R11 and later versions. The combination of the ALGORITHM_THIRD algorithm and the RTWP anti-interference
2013-10-1
Huawei Confidential
Page 51 of 69
Internal Open
algorithm is close to the NSN uplink admission algorithm. However, the algorithm is not launched commercially. The following principles are recommended: 1. If the customer does not require algorithm mapping to the original network, or the RAB setup failures caused by uplink power resource congestion in the PS domain (VS.RAB.FailEstabPS.ULPower.Cong) take a negligible or tiny proportion, use the ALGORITHM_SECOND algorithm to implement the power-based uplink admission control. If the RAB setup failures caused by uplink power resource congestion in the PS domain (VS.RAB.FailEstabPS.ULPower.Cong) take a considerable proportion, modify the equivalent number of uplink users (UlTotalEqUserNum) to a larger value. The new value must be based on the power congestion severity and concerned KPIs on the live network. Ensure that the power congestion reduces, the access KPIs are improved, and the call drop rate does not deteriorate. The call drop rate must satisfy the customer requirement. That is, the parameter modification must balance the access and call drop performance. If the proportion of the RAB setup failures caused by uplink power resource congestion in the PS domain (VS.RAB.FailEstabPS.ULPower.Cong) remains high after the parameter is modified, or the customer requires that the admission algorithm provided by NSN be mapped, enable the ALGORITHM_THIRD algorithm and the RTWP antiinterference algorithm. The associated settings are as follows: MOD UCELLALGOSWITCH: CellId=***, NBMUlCacAlgoSelSwitch=ALGORITHM_ THIRD; MOD UCELLALGOSWITCH: CellId=***, NBMCacAlgoSwitch=HSUPA_UU_ADCTRL-1&HSUPA_PBR_MEAS0&HSUPA_EDCH_RSEPS_MEAS-1&RTWP_RESIST_DISTURB-1; MOD UCELLCAC: CELLID=***, CellUlEquNumCapacity=20; For details about how to enable the algorithms, see the RAN Feature Activation Guide. Perform the operations under the guidance of professional engineers.
2.
3.
3.16 Uplink Admission for Soft Handover

3.16.1 Difference
During the swapping for Telenor in Serbia, the RAB setup success ratio is greatly lower than that on the original network due to the external uplink interference. In the RAB setup failure case on the live network, CELL3 is a normal cell, and the RTWP of CELL1 reaches 70 dBm due to strong interference. However, the overload control (OLC) must be enabled according to the policy and KPI requirements. After establishing an RRC connection in CELL3, the UE performs signal-only handover to add CELL1 to the activation set, and then initiates an RAB request. CELL1 denies the admission request in the uplink. When the OLC is enabled, the OLC state is checked. If the UE is in the OLC state, the request is denied.
2013-10-1
Huawei Confidential
Page 52 of 69
Internal Open
On the Huawei network, the RAB setup of the UE fails if one RL in the activation set fails to be established due to OLC admission during soft handover. On the NSN network, the RAB setup of the UE succeeds if one RL in the activation set is established successfully during soft handover. In this scenario, the NSN network has advantages in the performance presentation of the RAB setup success ratio.
3.16.2 Solution
In Huawei UMTS R14, a better policy is offered for the preceding scenario. In the signal-only soft handover process, the admission control based on the channel element (CE), Iub, code, downlink power resources is implemented for links in the activation set. The admission control based on the uplink power and admission deny for RLs with the uplink power in the OLC state are added. When the OLC is enabled and the RL is in the OLC state, the admission is denied; otherwise, the admission is not denied. In this case, the RRC admission is implemented with priority. This ensures that the RL whose admission request is denied is not added in the RAB setup process. If the KPIs reflect network problems in this type of scenarios, follow the algorithm commercial use guarantee process to enable the power-based uplink admission control for the signal-only soft handover.
ADD UCELLALGOSWITCH: CellId=***, NBMCacAlgoSwitch=SIGNALING_SHO_UL_AC_SWITCH-1;
3.17 DRD
3.17.1 Difference
NSN adopts the RRC directed retry decision (DRD) policy for networking. Huawei provides both RRC DRD and RAB DRD algorithms. On the stock networks and swapped networks supplied by Huawei, the RAB DRD is used. The RAB DRD is a mature algorithm. The RRC DRD algorithm is not commercially used on a large scale and may have
2013-10-1
Huawei Confidential
Page 53 of 69
Internal Open
problems. Therefore, the RRC DRD is recommended.
3.17.2 Solution
The RRC DRD is recommended.
3.18 NRT DCH Rate Set Restriction

3.18.1 Difference
NSN allows telecom operators to restrict the NRT DCH rate set for the system using the RNC-level parameters and restrict the maximum rate of the NRT DCH users in the cell using the cell-level parameters. 1. NRT DCH rate set restriction (at the RNC level) NSN predefines a NRT DCH rate set, as shown in the following table. Direction Predefined BitRate Set UL 0 kbit/s 8 kbit/s 64 kbit/s 128 kbit/s DL 0 kbit/s 8 kbit/s 64 kbit/s 128 kbit/s 384 kbit/s
The BitRateSetPSNRT parameter is used to control whether the predefined rate set is used.

If BitRateSetPSNRT is set to 1, only the rates in the predefined rate set can be used. If BitRateSetPSNRT is set to 0, all the rates are supported in the system.
2.
Maximum NRT DCH rate (at the cell level) The MaxBitRateULPSNRT and MaxBitRateDLPSNRT parameters are used to control the maximum rate of the accessed NRT DCH RAB in a cell.
MaxBitRateULPSNRT
This parameter defines the maximum downlink user bit rate allowed in a cell for an NRT PS domain RAB.
MaxBitRateDLPSNRT
This parameter defines the maximum uplink user bit rate allowed in a cell for an NRT PS domain RAB.
2013-10-1
Huawei Confidential
Page 54 of 69
Internal Open
The description of the NRT DCH rate restriction is as follows in the NSN documents:
The typical default uplink/downlink rate set provided by Huawei is as follows: {0kbit/s, 8kbit/s, 16kbit/s, 32kbit/s, 64kbit/s, 128kbit/s, 144kbit/s, 256kbit/s, 384kbit/s} The rate set is configured with the RNC-level parameters and the maximum cell-level rate cannot be set. Controlling the maximum cell-level rate can ease cell congestion for cells with heavy load, but may affect the experience of users in the NRT DCH state.
3.18.2 Solution
The NRT DCH rate set restriction feature provided by NSN can be mapped to the target network during swapping. The NRT DCH maximum bit rate (MBR) cannot be restricted at the cell level. The following table shows the details. Feature Provided by NSN NRT DCH rate set restriction (at the RNC level) Mapping to Huawei Network It can be mapped to the Huawei network during swapping. The user experience is affected. Clarify the impact before mapping. Mapping Strategy
If NSN BitRateSetPSNRT is 0, do not map the restriction to the Huawei network. If NSN BitRateSetPSNRT is 1, map the restriction to the Huawei network as follows: Deactivate the NRT DCH rates for the interactive and background services using the DEA UTYRAB command, that is, deactivate the uplink rate set {16kbit/s, 32kbit/s, 144kbit/s, 256kbit/s, 384kbit/s} and downlink rate set {16kbit/s, 32kbit/s, 144kbit/s, 256kbit/s}. If the value of APPLIEDDIRECT of the corresponding RAB is APPLIED_ON_BOTH, after the RAB is deactivated, modify the APPLIEDDIRECT parameter to a required value before activating the RAB.
2013-10-1
Huawei Confidential
Page 55 of 69
Internal Open
Feature Provided by NSN Maximum NRT DCH rate (at the cell level)
Mapping to Huawei Network It cannot be mapped to the Huawei network during swapping.
Mapping Strategy
None.
3.19 HSDPA Throughput Counter Definition Analysis

3.19.1 Difference
On the Huawei Side The calculation formula of the HSDPA cell throughput varies with the product version. In Huawei UMTS R11, the calculation formula is as follows: HSDPA Throughput=VS.DataOutput.Mean/VS.DataTtiRatio.Mean In Huawei UMTS R12, the calculation formula is as follows: HSDPA Throughput=VS.DataOutput.Mean/(VS.DataTtiRatio.Mean VS.HSDPA.InactiveDataTtiRatio.Mean) The involved counters are defined as follows: VS.DataOutput.Mean is the average HSDPA throughput of the cell in the statistical period. The counter is the sum of the acknowledgement (ACK) scheduling data volumes reported by all users in all TTIs divided by the total time length in the statistical period. VS.DataTtiRatio.Mean is the proportion of time when data exists in the HSDPA queue buffer in the cell in the statistical period. In a TTI in the statistical period, the queue buffer of at least one HSDPA user has data to be transmitted. The counter is the number of such TTIs divided by the total number of TTIs in the statistical period. VS.HSDPA.InactiveDataTtiRatio.Mean is the proportion of time when data exists in the HSDPA queue buffer but the physical layer does not have data transmission in the cell in the statistical period. In a TTI in the statistical period, the queue buffer of at least one HSDPA user has data to be transmitted, but no HSDPA user sends data at the physical layer. The counter is the number of such TTIs divided by the total number of TTIs in the statistical period.
The VS.DataTtiRatio.Mean counter is designed as the proportion of time when data exists in the HSDPA queue buffer and the physical layer has data transmission in the cell in the statistical period, but is developed as the proportion of time when data exists in the HSDPA queue buffer in the cell in the statistical period. This leads to the denominator of the HSDPA throughput calculation formula greater than the actual one. In R12, the VS.HSDPA.InactiveDataTtiRatio.Mean counter is modified and the problem is solved.
Therefore, if the R11 is used during the swapping, clarify the problem in advance.
2013-10-1
Huawei Confidential
Page 56 of 69
Internal Open
On the NSN Side The HSDPA cell throughput is defined with two calculation formulas: Calculation formula 1:
HSDPA Throughput=sum(HS_DATA_ACK_SPI_0 + HS_DATA_ACK_SPI_1 + HS_DATA_ACK_SPI_2 + HS_DATA_ACK_SPI_3 + HS_DATA_ACK_SPI_4 + HS_DATA_ACK_SPI_5 + HS_DATA_ACK_SPI_6 + HS_DATA_ACK_SPI_7 + HS_DATA_ACK_SPI_8 + HS_DATA_ACK_SPI_9 + HS_DATA_ACK_SPI_10 + HS_DATA_ACK_SPI_11 + HS_DATA_ACK_SPI_12 + HS_DATA_ACK_SPI_13 + HS_DATA_ACK_SPI_14 + HS_DATA_ACK_SPI_15)/(SUM (HS_SCCH_PWR_DIST_CLASS_0 + HS_SCCH_PWR_DIST_CLASS_1 + HS_SCCH_PWR_DIST_CLASS_2 + HS_SCCH_PWR_DIST_CLASS_3 + HS_SCCH_PWR_DIST_CLASS_4 + HS_SCCH_PWR_DIST_CLASS_5)/500)
Calculation formula 2:
HSDPA Throughput=SUM (RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS)/(SUM (HS_SCCH_PWR_DIST_CLASS_0 + HS_SCCH_PWR_DIST_CLASS_1 + HS_SCCH_PWR_DIST_CLASS_2 + HS_SCCH_PWR_DIST_CLASS_3 + HS_SCCH_PWR_DIST_CLASS_4 + HS_SCCH_PWR_DIST_CLASS_5)/500)
Difference Analysis Both formulas cannot be strictly mapped to the Huawei network. Formula 1 of NSN differs from the formula in Huawei R12 in terms of numerator. Formula 1 of NSN calculates the MAC-HS packet data unit (PDU), including the MAC-HS head and padding bit. The formula in Huawei R12 calculates the MAC-D PDU, excluding the head and padding bit. Therefore, the calculated throughput provided by NSN is higher than that provided by versions earlier than Huawei R15 on equivalent networks. (CR NPC8607A is mapped over VS.HSDPA.DataActedMAChs.Bits.) Formula 2 of NSN differs from the formula in Huawei R12 in terms of numerator. Formula 2 of NSN calculates the data volume received on the NodeB except for the data packets discarded during flow control. It is Iub interface oriented. The formula in Huawei R12 calculates the data volume confirmed by the UE. It is Uu interface oriented. As the implementation inside NSN products is unclear, the scenarios with calculation differences cannot be precisely identified. However, the following four scenarios are identified, where the throughput calculation result of NSN is higher than that of Huawei:

The serving cell changes in inter-NodeB mode. The number of hybrid automatic repeat request (HARQ) retransmission times exceeds the maximum. The NodeB buffer data is discarded due to timeout. The UE is released. The difference of the calculation results is not clear as the implementation inside NSN products is unclear. Based on the data analysis on traffic statistics of a cluster from VDF in Italy, the difference is about 2.5% in the preceding scenarios. The major factors are that the serving cell changes in inter-NodeB mode and the number of HARQ retransmission times exceeds the maximum. In the scenario where the NodeB buffer data is discarded due to timeout, the impact on the difference is slight. In the scenario where the UE is released, the buffer do not have data generally. The estimation is based on the implementation principles of Huawei. The difference on the NSN side is unclear. In Huawei R15, the counter mapping requirement may be fulfilled.
2013-10-1
Huawei Confidential
Page 57 of 69
Internal Open
3.19.2 Solution
The counters do not match in the preceding scenarios, and the throughput is highly associated with user behaviors. Therefore, you are recommended to convince the customer not to take the HSDPA throughput as a verification indicator. Otherwise, the HSDPA throughput may fail customer requirements.
3.20 HSUPA Throughput Counter Definition Analysis

On the Huawei Side The calculation formula of the HSUPA cell throughput is as follows:
HSUPA Throughput=VS.HSUPA.Thruput/(VS.HSUPA.DataTtiNum*0.002)
Where, The VS.HSUPA.Thruput counter is the sum of the MAC-d PDU bits successfully received from the UPA users in the statistical period (evenly divided for links in softer handover). The VS.HSUPA.DataTtiNum counter calculates the number of TTIs with HSUPA transmission or retransmission in the statistical period. The calculation formula of the single user throughput is as follows: (The R12 and earlier versions do not provide calculation formulas. The corresponding counters are added for the calculation of the single user throughput to the CR NPC8607 NodeB HSPA Throughput Counter Statistics.)
VS .HSUPA.Traffic.TRB VS .HSUPA.2msPDU .TRB.Num * 0.002 +VS .HSUPA.10msPDU .TRB.Num * 0.01

Where, The VS.HSUPA.Traffic.TRB counter is the sum of the MAC-d PDU bits successfully received from HSUPA users in the HSUPA serving cell in the statistical period. The counter of DC HSUPA users is measured on the primary and secondary carriers separately. The VS.HSUPA.2msPDU.TRB.Num counter is the number of 2 ms TTIs when the MACe/MAC-i TRBs (including retransmission) are received from the users in the HSUPA serving cell in the statistical period. The counter of DC HSUPA users is measured on the primary and secondary carriers separately. The VS.HSUPA.10msPDU.TRB.Num counter is the number of 10 ms TTIs when the MACe/MAC-i TRBs (including retransmission) received from the users in the HSUPA serving cell in the statistical period. The counter of DC HSUPA users is measured on the primary and secondary carriers separately. The counter does not count the number of 10 ms PDUs of the MAC-e/MAC-i TRBs received by the WBBPa board.
2013-10-1
Huawei Confidential
Page 58 of 69
Internal Open
On the NSN Side Cell throughput definition 1:
As indicated in the preceding table, the counter is measured on the air interface. The implementation principles are unclear, and further analysis by testing NSN product implementation is required.
2013-10-1
Huawei Confidential
Page 59 of 69
Internal Open
Cell throughput definition 1:
2013-10-1
Huawei Confidential
Page 60 of 69
Internal Open
The calculation formula of the single user throughput is as follows:
2013-10-1
Huawei Confidential
Page 61 of 69
Internal Open
SUM(EDCH _ DATA_ SCEL _UL)*8 = {SUM(MACE _ PDU _ RETR _0 _COUNTER + MACE _ PDU _ RETR_ 01_COUNTER 2* + MACE _ PDU _ RETR _02_COUNTER*3+ MACE _ PDU _ RETR _03_COUNTER 4* + MACE _ PDU _ RETR _04_COUNTER*5+ MACE _ PDU _ RETR _05_COUNTER*6 + MACE _ PDU _ RETR _06_COUNTER*7 + MACE _ PDU _ RETR _07_COUNTER*8+ MACE _ PDU _ RETR _08_COUNTER*9+ MACE _ PDU _ RETR _09_COUNTER*10+ MACE _ PDU _ RETR _10_COUNTER*1 + MACE _ PDU _ RETR _1 _COUNTER*12 + MACE _ PDU _ RETR _12_COUNTER*13)*0.01*(MACE _ PDUS _10MS _T I / (MACE _ PDUS _10MS _T I + MACE _ PDUS 2_ MS _T I) }+ {SUM(MACE _ PDU _ RETR _0 _COUNTER + MACE _ PDU _ RETR_ 01_COUNTER 2* + MACE _ PDU _ RETR _02_COUNTER*3+ MACE _ PDU _ RETR _03_COUNTER 4* + MACE _ PDU _ RETR _04_COUNTER*5+ MACE _ PDU _ RETR _05_COUNTER*6 + MACE _ PDU _ RETR _06_COUNTER*7 + MACE _ PDU _ RETR _07_COUNTER*8+ MACE _ PDU _ RETR _08_COUNTER*9+ MACE _ PDU _ RETR _09_COUNTER*10+
Huawei Confidential
2013-10-1
Page 62 of 69
Internal Open
Difference Analysis The difference on the cell throughput calculation is as follows: On the NSN side, The numerator of the calculation formula is the overall throughput volume of the cell, including the serving cell and non-serving cell. The statistics are collected from the NodeB. The denominator of the calculation formula is the total length of the period when at least one user has uplink packet access (UPA) in the cell (online period). The statistics are collected from the RNC. The calculation formula cannot be mapped to that of Huawei because the denominator of the calculation formula of Huawei measures the length of the period with data transmission and that of NSN measures the length of the online period. The difference on the single-user throughput calculation is as follows: The numerators are different. The numerator of the calculation formula of NSN measures the MAC-e layer and that of Huawei measures the MAC-d layer. The numerators can be mapped roughly; however, the mapping does not properly represent the performance of Huawei networks. You are recommended to measure the throughput volume in dotted way at the MAC-e layer based on the CR process. The denominators are different. NSN does not identify the retransmission proportion between 10ms TTI HSUPA users and 2ms TTI HSUPA users. The difference is difficult to evaluate.
3.20.1 Solution
The counters do not match in the preceding scenarios, and the throughput is highly associated with user behaviors. Therefore, you are recommended to convince the customer not to take the HSUPA throughput as a verification indicator. Otherwise, the HSUPA throughput may fail customer requirements.
3.21 HSPA Dynamic DL Control Channel Allocation

3.21.1 Difference
NSN provides the dynamic DL control channel allocation mechanism for HS-SCCH and ERG/HICH channels based on the number of users in the cell.
2013-10-1
Huawei Confidential
Page 63 of 69
Internal Open
The mechanism helps release some idle code resources when the number of users in cells is small, which increases the cell capacity. Huawei R12 does not provide the mechanism but R13 provides a similar mechanism.
3.21.2 Solution
R13 is recommended for swapping so that the mechanism can be tried. The command for enabling the mechanism is as follows: MOD UCELLHSDPA: DynHsscchAllocSwitch=ON;
The mechanism has not been used for commercial purposes.
3.22 H2F State Transition Mechanism

3.22.1 Difference
NSN triggers H2F for many reasons. The reasons in red rectangles in the following figure are supported by NSN but not supported by Huawei:
Concerning user behaviors, Huawei triggers H2F only based on the service volume whereas NSN provides two H2F mechanisms, one based on the service volume and one based on the throughput. The following figure shows the related description in an NSN document.
2013-10-1
Huawei Confidential
Page 64 of 69
Internal Open
The following figure shows how H2F is triggered.
For users having sustained data transfer in the coverage edge scenario, the power resource of the air interface is limited and the data volume of the radio link control (RLC) is high if the H2F triggering mechanism provided by NSN is used. H2F is triggered based on the throughput. If the H2F triggering mechanism provided by Huawei is used, H2F is not triggered in the preceding situation. As a result, NSN has an edge over Huawei when the HSDPA throughput is measured. Compared with the mechanism provided by Huawei, the mechanism provided by NSN has the following impacts on KPIs.
2013-10-1
Huawei Confidential
Page 65 of 69
Internal Open
KPI
HSDPA Throughp ut
HSDPA Throughp ut
Number of HSDPA Users
HSDPA Call Drop Rate
End User Experience
Result
- (A switchover to the DCH does not obviously affect end user experience when the throughput is low.)
indicates a positive impact, indicates a negative impact, and indicates no difference.
3.22.2 Solution
1. 2. Huawei does not provide the mechanism for triggering H2F based on the throughput or UE exception. Clarify the differences on this feature to the customer in advance. Currently, the state transition duration is specified by the BeH2FStateTransTimer parameter, which is provided by Huawei and mapped to the MACdflowutilTimetoTrigger parameter provided by NSN. For mapping details, see the parameter mapping table. The mapping is inaccurate. After the swapping, change back to the original state transition duration by adjusting the BeH2FStateTransTimer parameter based on the change to the number of times to reconfigure H2F.
3.
3.23 SIR ErrorBased H2D Triggering Mechanism

3.23.1 Difference
The key points of the mechanism provided by NSN are as follows: 1. After HSs are allocated, the signal-to-interference ratio (SIR) error value is measured regularly and the SIR error is reported only when the value changes dramatically. The RNC checks the average of the values contained in the last N reports. If no SIR error value is reported in a measurement cycle, the value reported in the last cycle is used. The SIR error reported by the source cell can trigger a serving cell change. If the target cell is not found, H2D can be triggered. The target cell must meet SIR error restrictions.
2. 3.
The original mechanism description is as follows: In the 29_7_19_RRM_of_HSDPA_dn0638161_3-0_en: P75: The uplink SIRerror measurement P82: The following reasons initiate the serving HS-DSCH cell change:
2013-10-1
Huawei Confidential
Page 66 of 69
Internal Open
The level of the UL SIRerror in the serving cell, which initiates serving HS-DSCH cell change can be configured with HSDPASIRErrorServCell parameter. P80: To execute inter-BTS serving HS-DSCH cell change, the UL SIRerror of the target BTS must exceed the threshold determined by the HSDPASIRErrorTargetCell parameter. SIRerror measurement to be used for evaluation is the latest averaged value. In the case of an intra-BTS serving HS-DSCH cell change, the UL SIRerror does not need to be checked. Huawei does not provide the mechanism. Generally, SIR errors are persistently reported only in scenarios (such as cell edges) where the uplink signal is weak. In these scenarios, the downlink transmission rate is low due to uplink and downlink correlation. As a result, NSN has an edge over Huawei when the HSDPA throughput is measured. Compared with the mechanism provided by Huawei, the mechanism provided by NSN has the following impacts on KPIs. KPI HSDPA Throughp ut HSDPA Throughp ut Number of HSDPA Users HSDPA Call Drop Rate End User Experience
Result
X (If the mechanism provided by NSN is used, many unnecessary interaction processes are implemented in signal conversion areas. In addition, an uplink SIR error does not necessarily indicate weak downlink signal. After H2D is triggered, end user experience is obviously affected.
3.23.2 Solution
Huawei does not provide the mechanism. Clarify the differences on this feature to the customer in advance.
2013-10-1
Huawei Confidential
Page 67 of 69
Internal Open
3.24 H2D and E2D Mechanisms

3.24.1 Difference
According to the NSN document shown in the following figure, NSN supports more H2D triggering factors:
In the case of a single NRT PS RAB, the measurement event 1F (A primary CPICH goes below the absolute threshold) initiates HS-DSCH MAC-d flow release and mapping of a radio bearer to DCH 0/0 kbit/s. The measurement event 1E (A primary CPICH becomes better than an absolute threshold) cancels the measurement event 1F. Each cell of the active set must trigger the measurement event 1F before HS-DSCH MAC-d flow release is started. In the case of an AMR multi-service, the measurement events 1F (A primary CPICH goes below the absolute threshold) and 1E (A primary CPICH becomes better than an absolute threshold) are used to initiate the inter-frequency measurements. The HS-DSCH MAC-d flow is then released before initiation of the inter-frequency measurements for AMR speech CS RAB. The same applies also to the DL Transmitted Code Power measurement. However, if the HSDPA Inter-Frequency Handover optional feature is activated and interfrequency handover triggers are present, HS-DSCH release is not triggered. Instead, an EDCH to DCH switch in uplink is performed if needed and inter-frequency handover measurement is started after that immediately with DL: HS-DSCH/UL: DCH configuration. For more details, see HSDPA inter-frequency handover. These scenarios generally occur at the edge of cells. If the users remain on the HSDPA, the HSDPA throughput is low and the HSDPA traffic statistics are affected. The solution provided by NSN offers a higher HSDPA traffic throughput. In addition, as NSN does not support downlink DCH and uplink EDCH configuration, when the H2D is triggered, the E2D may occur as well. In the solution provided by Huawei, the handover is independent in the uplink and downlink. Compared with the mechanism provided by Huawei, the mechanism provided by NSN has the following impacts on KPIs.
2013-10-1
Huawei Confidential
Page 68 of 69
Internal Open
KPI
HSPA Throughp ut
HSPA Throughp ut Volume
Numbe r of HSPA Users
HSPA Call Drop Rate
End User Experience
Result
(1. The HSDPA rate may not be lower than the DCH rate in scenarios triggering the state transition. The rate may be affected as NSN uses the DCH state. 2. The E2D transition may affect the downlink user experience.
3.24.2 Solution
1. 2. Clarify the difference of H2D triggering factors supported by Huawei and NSN and its impact on the HSPA throughput statistics with customers. Adjust the settings of the E2D transition based on the number of reconfiguration times after swapping to achieve the level before the swapping.
3.25 Multi-Carrier Strategy

3.25.1 Difference
The multi-carrier DRD and handover strategies of NSN, Ericsson, and Alcatel Lucent cannot be mapped to the target network directly during swapping. In the previous swapping cases, the typical dual-carrier strategy of Huawei is used based on the customer requirements. The success swapping stories tell that the multi-carrier strategy of Huawei can match the level of the original network and the customer requirements.
3.25.2 Solution
For details about the multi-carrier strategy, see the following document delivered with this document: UMTS Performance R12 Multi-Band Multi-Carrier Performance Solution V0.9
2013-10-1
Huawei Confidential
Page 69 of 69

UMTS Swapping Strategy Guide

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

UMTS Swapping Strategy Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Product Name SWP Product Version 1.

Confidentiality Level INTERNAL Total 69 pages