c03_bsc6900 umts v900r016c00spc650 release notes

Release Notes

DOCPROPERTY PartNumber

BSC6900 UMTSV900R016C00SPC650Release Notes

Issue01

Date2014-12-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders.NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:Huawei Industrial BaseBantian, LonggangShenzhen 518129People's Republic of China

Website:http://www.huawei.com

Email:[email protected]

About This DocumentAuthorPrepared byWang Erli, Xu Qigang, Hou Wei, Li Jian, Zhu JiangboDate2014-12-01

Reviewed byLiu Yong, Liu Qi, Xu Yousong, Wang Jun, Wang Qingyan, Chen Yiwen, Zhang Peng, Wu XiuliangDate2014-12-10

Tested byZheng HangDate2014-12-17

Approved byWang DongDate2014-12-31

OverviewThis document provides only the changes between adjacent patch versions for BSC6900V900R016C00SPC600.If a BSC earlier than BSC6900V900R016C00SPC600 on the live network is upgraded to the current patch version, obtain the release documentation matching BSC6900V900R016C00SPC600 and use the obtained release documentation together with this document.If an intermediate version is required for the upgrade on the live network (for details, see section 1.2 "Version Requirements" in the upgrade guide), obtain the release documentation matching BSC6900V900R014C00SPC500 of the intermediate version and its patch BSC6900V900R014C00SPH552.The "Known Issues" chapter in each version describes the status of all known issues. If a known issue has been resolved, the progress of this known issue will be displayed in the "Resolved Issues" chapter in a later version.Users can check the progress of a known issue according to its trouble ticket number.Change HistoryIssueDateAuthorDescription

012014-12-31Wang Erli, Xu Qigang, Hou Wei, Li Jian, Zhu JiangboThis is the first commercial release.

IntroductionThis document is intended for system engineers. It provides the following information: Version RequirementsThis chapter lists all information about this product version, for example, software, hardware, operating system (OS), database, documentation, and any other required products. This chapter also provides important notes and virus scan results for this product version. Version CompatibilityThis chapter describes the compatibility between this product version and earlier versions, including their software and hardware versions. Change DescriptionThis chapter describes the changes in the current version compared with the previous version, including the change summary, feature changes, resolved issues, and known issues. Where, The feature summary includes information about capacity and performance, hardware, features, resolved issues, operation and maintenance, and related documentation, as described in Table 1 Section description.Table 1 Section descriptionSectionDescription

Capacity and performanceDescribes the possible impact of a specific product version on system capacity and network performance.

HardwareDescribes any hardware addition and modification in a specific product version. The hardware end of marketing (EOM) and end of service (EOS) information does not map onto the software version. For details, see the corresponding PCN.

FeaturesProvides a summary of all feature changes in a specific product version. Users can select desired features by "Impact on Capacity and Performance", "Hardware Dependency", "Parameter Control?", or "Parameter Control?".

Resolved issuesProvides a summary of all resolved issues in a specific product version. Users can select desired resolved issues by "Solution Impact", "Parameter Control?", or "Post-Upgrade Value".

Operation and maintenanceDescribes the changes to configuration management, performance management, fault management, license management, and their management mechanisms and rules in a specific product version.

Related documentationDescribes the changes to related documentation of a specific product version.

Figure 1 Relationships among sections in Change Summary shows the relationships among the preceding sections.Figure 1 Relationships among sections in Change Summary

Feature Changes: details feature changes. Resolved Issues: details resolved issues by severity. Known Issues: details known issues in this product version by severity. Operation and Maintenance ChangesThis chapter describes changes to MML commands, parameters, alarms, events, counters, and licenses. AppendixThe appendixes describe how to obtain related documentation and provide acronyms and abbreviations involved.ContentsiiAbout This Document

11 Version Requirements

11.1 Product Version

11.2 Software Versions

11.3 Hardware Versions

31.4 Related Product Versions

41.5 OS and Database Versions

51.6 Related Documentation

71.7 Virus Scan Result

71.8 Important Notes

82 Version Compatibility

82.1 Software Version Compatibility

82.2 Hardware Version Compatibility

103 Changes from V900R016C00SPC630 to V900R016C00SPC650

103.1 Change Summary

113.1.1 Capacity and Performance

113.1.2 Hardware

113.1.3 Features

123.1.4 Resolved Issues

123.1.5 Operation and Maintenance

123.1.5.1 Configuration Management

123.1.5.2 Performance Management

123.1.5.3 Fault Management

133.1.5.4 License Management

133.1.6 Related Documentation

133.2 Feature Changes

133.2.1 New Features

133.2.2 Modified Features

133.2.2.1 Considering the Power Load of Multi-carrier HSDPA UEs in the CLB Algorithm

153.2.2.2 Iur-p Link Loopback Detection Self-Healing

163.2.2.3 Enhanced UMTS-to-LTE Fast Return Based on Combined Services

183.2.2.4 Exporting Configuration Information in the SET LICENSE Command

193.2.2.5 Global Tracing of IMSI Messages in the CS Domain

223.2.2.6 Optimization of NIC Information Collection Based on SOP

233.2.2.7 LAI and SAI IEs Supported in the DIRECT TRANSFER Message in the CS Domain

253.2.2.8 Support notifying the information of UEs capable of downlink DC-HSDPA throughput optimization to the NodeB

263.2.2.9 Support for Checking Resources of License Resource Items During a Pre-upgrade

283.2.2.10 Optimized Features for RACH Keepalive Function

293.2.2.11 Optimizing Reporting of EVT-22915 SCTP Link Destination IP Changeover

313.2.2.12 Enhancement of Active/Standby Status Consistency of Interface Boards and Ports Before and After an Upgrade

323.2.2.13 Optimizing Information Displayed at the Start of an Upgrade Phase on the Upgrade Tool

343.2.2.14 Adding the Prompt Message for Configuration Data Change During a Rollback on the Upgrade Tool

353.2.2.15 Changing Backup IP Address on the U_creator Tool

373.2.2.16 OMU Capacity Evaluation

393.2.2.17 Support for Querying Manually Cleared Alarms

403.2.2.18 Changing the Default Value of Automatic Synchronization Switch

423.2.2.19 Enhanced Support for Editing of Batch Configuration Parameters on the Web LMT

433.2.2.20 Fan Box Noise Rectification at a High Fan Speed

443.2.3 Deleted Features

443.3 Resolved Issues

443.3.1 Critical

443.3.1.1 The call drop rate increases when the satellite card cannot properly trace GPS satellite signals.

453.3.2 Major

453.3.2.1 The value of Number of Received CREF in ALM-21522 Low SCCP Setup Success Rate is incorrect.

453.3.2.2 Configuration data on the OMU is different from that on the SPU after the command RMV UEXT3GCELL, MOD UCELLFREQUENCY, or RMV UNRELATION is consecutively executed.

463.3.2.3 When an RNC sends inter-frequency measurement control messages to UEs, some UEs experience call drops.

473.3.2.4 The number of transmitted HS-DSCH Capacity Request messages is not controlled when UEs in the CELL_DCH state have no HSDPA service data to transmit within a certain period of time.

483.3.2.5 Logs are not recorded if the RNC receives a SECURITY MODE COMMAND message during other procedures.

493.3.2.6 Downlink data transmission for PS services is interrupted.

503.3.2.7 Services fail to be set up if an RB setup procedure during an F2D state transition overlaps with a cell update procedure.

513.3.2.8 ALM-22501 DSP CPU Overload is suppressed.

523.3.2.9 A large number of UEs unexpectedly initiate registration requests and the RNC control-plane CPU usage suddenly reaches an high value.

533.3.2.10 After the MOD UCELLID command is executed, performance objects are repeated.

543.3.2.11 UEs in a LAC area cannot be paged after the cell LAC information has been modified using the CME.

543.3.2.12 Changing the GTP-U local IP address at the transport layer causes service releases after the PS core network modifies the service type.

573.3.2.13 The RNC fails to initiate a channel fallback in the event of service setup or reconfiguration failures in some scenarios.

583.3.2.14 The SPU on a Huawei DRNC restarts if messages received from a non-Huawei SRNC over the Iur interface carry protocol-incompliant IEs.

593.3.2.15 The RL reconfiguration fails when an ATM/IP dual stack is applied over the Iub interface.

603.3.2.16 N7DPC specified by DPX is inconsistent with that specified by NI, SPC/SPCDNF, and DPC/DPCDNF in the configuration of the UCNNODE or UNRNC MO.

613.3.2.17 Configuration commands cannot be delivered to a board because the board is mistakenly inhibited.

613.3.2.18 Vulnerability CVE-2014-3511 exists.


633.3.2.20 The XPU board may abnormally report counters in GU mode.

633.3.2.21 Service setup fails after a BSC6900 is upgraded from V900R013C00SPC586 to V900R015C00SPH565.

643.3.2.22 An interface board unexpectedly resets because of logical remote loopback detection failures.

653.3.2.23 Logical remote loopback detection on an interface board becomes unavailable.

653.3.2.24 The level-1 clock source becomes unavailable after the clock cable to the GCGa/GCUa board panel is removed and installed.

663.3.3 Minor

663.3.3.1 WPS UEs initiate preemption during soft handovers, increasing the call drop rate.

673.3.3.2 The information element "Support for UE assisted GPS measurement validity in CELL_PCH and URA_PCH states" contained in the POSITION INITIATION REQUEST message is assigned an incorrect value.

673.3.3.3 Some alarms are incorrectly reported after the master and backup RNCs of a logical RNC are switched over when RNC in Pool Node Redundancy is enabled.

693.3.3.4 The relocation process fails when the Iur interface-based common channel function is enabled.

713.3.3.5 The CPU usage instantaneously increases when message tracing over the Iur-p interface is enabled.

723.3.3.6 Uplink BLER-related counters return inaccurate values when the AMRC feature is activated.

723.3.3.7 The RNC improperly processes security mode in incoming inter-RAT relocations for combined services or PS services.

743.3.3.8 Counters related to Multiband Direct Retry Based on UE Location return inaccurate values if measurement-based periodic DRD is triggered.

753.3.3.9 Parameter configuration for power control is inappropriate if PS services are set up following an AMR service reconfiguration.

763.3.3.10 The RNC fails to add secondary carrier links for the DC-HSUPA UE after a serving cell change failure.

773.3.3.11 Some UEs fail to run CS services when CS fallback is triggered.

783.3.3.12 The RNC incorrectly measures certain performance counters for the MBDR-based inter-RAT handovers.

793.3.3.13 Some IEs in the INITIAL UE MESSAGE message are not parsed during signaling tracing.

793.3.3.14 In a PDP deactivation procedure, the RNC sends the core network a RAB RELEASE REQUEST message.

803.3.3.15 The IE "TargetCellId" contained in a DIRECT INFORMATION TRANSFER message is incorrectly examined in a RIM procedure.

813.3.3.16 Incorrect license control item usage and false alarms are reported for some features.

843.3.3.17 The SRNC does not send the DRNC a RESET REQUEST message after the SRNC is restarted on RNC in Pool networking.

853.3.3.18 CS service setup fails when the coverage is strong and the delay over the Iub interface is large.

853.3.3.19 UEs experience PS service drops when the RNC initiates a PS RAB modification.


873.3.3.21 The automatic switchover of the active and standby OMUs cannot be performed when the hard disk of the active OMU is abnormal and that of the standby OMU is normal.

873.3.3.22 TCP ISN security risks are found during CSEC scan.

883.3.3.23 The base station controller does not report ALM-21541 SCTP Link Fault when an SCTP link whose Application type is BBAP(BBAP) and Signalling link mode is SERVER(SERVER MOD) becomes faulty.

893.3.3.24 The GPS satellite health check function is not controlled by commands.

893.3.4 Suggestion

893.3.4.1 When the SRB over HSDPA feature takes effect, single HSUPA BE services are dropped.

903.3.4.2 CS and PS combined services do not allow service-based inter-RAT handovers.

913.3.4.3 Some UEs report false measurement results or experience call drops after they start neighboring LTE cell measurement.

933.3.4.4 User access delay is greater than expected because of redundant IEs in the RADIO BEARER SETUP message.

943.3.4.5 The MC-HSDPA UE can still use the DTX/DRX feature even when the MC-HSDPA secondary carrier does not support this feature.

943.3.4.6 The RNC cannot accurately control the percentage of UEs during outgoing inter-RAT handovers in the MBDR algorithm.

953.3.4.7 The RNC cannot recognize the UE-sent packets with IE "Header Extension Type" of 2.

963.3.4.8 UEs are handed over or redirected from a UMTS network to an LTE network before the penalty duration ends

973.3.4.9 The RNC does not penalize service-based UMTS-to-LTE redirections or handovers on UEs redirected from the LTE network to the UMTS network.

983.3.4.10 In some scenarios, the RNC does not perform a penalty of service-based UMTS-to-LTE blind redirections.

993.3.4.11 UEs redirected from an LTE network to a UMTS network cannot be handed over or redirected back to an LTE network.

1003.3.4.12 The LST ULTENCELL or LST U2GNCELL command output displays undesired neighbor relationship information.

1013.3.4.13 CPC reconfiguration messages transmitted over the Uu interface are added two more bytes.

1023.3.4.14 The Differentiated Service Based on SPI Weight feature is not provided with a control switch.

1023.4 Known Issues

1023.4.1 Critical

1033.4.2 Major

1033.4.3 Minor

1033.4.4 Suggestion

1044 Changes from V900R016C00SPH621 to V900R016C00SPC630



1054.1.2 Hardware

1054.1.3 Features











1074.2.2.1 Coexistence Between the Single HARQ Process Scheduling and CPC Features

1084.2.2.2 Optimized PS BE Service Setup Process

1124.2.2.3 Optimized Distance-based Access Control

1144.2.2.4 Optimization Against State Inconsistency for UEs in the CELL_FACH State

1174.2.2.5 Support for RRC Reestablishment Through a D2P Procedure

1204.2.2.6 Optimization of OMU Disk IO Flow Control



1214.3.1 Critical

1214.3.2 Major

1224.3.2.1 PS BE Service Rate of Incoming Inter-RAT Handover UEs Are Limited.

1234.3.2.2 Peer AMR UEs are muted after the call reestablishment when the AMRC feature is activated.

1244.3.2.3 Peer UEs are muted because local UEs have not received the TFC CTRL message.

1254.3.2.4 AMR voice quality deteriorates when the protocol CR0125 takes effect.

1274.3.2.5 The value of VS.IRATHO.FailOutPS.UEGen is incorrect.

1274.3.2.6 Values returned by counters related to the uplink BLER of PS R99 services are greater than expected.

1294.3.2.7 Call drops occur if SRB over HSDPA or SRB over HSPA is enabled.

1304.3.2.8 The number of RAB setup attempts for HSPA services are incorrectly counted as that for R99 services.

1314.3.2.9 An SAAL link cannot be established after it is removed and then added again.

1324.3.2.10 An AOUa board may reset in some scenarios.

1324.3.3 Minor

1324.3.3.1 The HSUPA throughput rises slowly if a DRD procedure is triggered during service reconfiguration.

1334.3.3.2 The SAI-based location fails because the RNC sends an SAI-based location report to the CN during the UE relocation process.

1344.3.3.3 The CS service is abnormally released in the case of CS+PS combined services

1354.3.3.4 ALM-22206 UMTS Cell Setup Failed is reported again at 03:00 a.m..

1364.3.3.5 The UE transmit power increases due to AMR service reconfiguration in AMR+PS combined service scenarios.

1374.3.3.6 The PS service setup success rate is low.

1384.3.4 Suggestion

1384.3.4.1 In the case of insufficient HSPA users, CS services are released when UEs performing CS+PS combined services experience a combined incoming hard handover and SRNS relocation.

1394.3.4.2 UEs experience call drops if the RNC does not receive an IU RELEASE COMMAND message within a specified time in specific scenarios.

1404.3.4.3 PS service drops occur after a cell update with SRNS relocation is complete.

1414.3.4.4 UEs experience call drops when an automatic link reestablishment procedure and an inter-RAT cell reselection procedure are triggered concurrently.

1424.3.4.5 No performance counter provides data rate increase for 0 kbit/s PS services.

1444.3.4.6 In the single-signaling scenario where DRNC links exist, new PS services fail to be established in an E-DCH-to-DCH SRB fallback procedure.

1454.3.4.7 A moving UE in the connected state cannot update the RA or LA.

1474.3.4.8 No counter is provided to measure the number of times a UE in the CELL_PCH or URA_PCH state re-initiates an RRC connection setup request.

1484.3.4.9 Downlink code resources of the AMR+PS combined service cannot be saved.

1494.3.4.10 A UE abnormally exits from the large retransmission state at an extremely low rate during the RB reconfiguration for CS services.

1504.3.4.11 Data is inconsistent between the active OMU and the standby OMU after an upgrade.

1504.4 Known Issues

1504.4.1 Critical

1504.4.2 Major

1504.4.3 Minor

1514.4.4 Suggestion

1525 Changes from V900R016C00SPC620 to V900R016C00SPH621



1535.1.2 Hardware

1535.1.3 Features











1555.2.2.1 Configuration Script Browsing and Editing by using the Batch Configuration function of the WebLMT



1565.3.1 Critical

1565.3.2 Major

1565.3.3 Minor

1575.3.4 Suggestion

1575.4 Known Issues

1575.4.1 Critical

1575.4.2 Major

1575.4.3 Minor

1575.4.4 Suggestion

1586 Changes from V900R016C00SPH609 to V900R016C00SPC620



1596.1.2 Hardware

1596.1.3 Features











1616.2.2.1 IP Transmission Path Status Detection over the Iu and Iur Interfaces on the Backup RNC in RNC in Pool Scenarios

1636.2.2.2 The POSITION ACTIVATION RESPONSE Message over the Iu-PC Interface Containing the Value of the Path Loss

1646.2.2.3 Calibration of the Maximum Downlink Transmit Power for Special UEs

1676.2.2.4 UOIP Loopback Detection Function Supported by DPUe Boards

1686.2.2.5 RRC Connections Established on FACHs When NodeB Resources Become Unavailable

1706.2.2.6 Anti-Ping-Pong Mechanism for RRC Redirections Caused by Admission Failures

1716.2.2.7 Optimized Features for AMR Services

1766.2.2.8 Optimization of How an RNC Handles the SIGNALLING CONNECTION RELEASE INDICATION Message in the PS Domain for UEs Enabled with the Enhanced Fast Dormancy Feature

1786.2.2.9 RL Reestablishment Event Blocks Now Added to RNC PCHR Logs

1796.2.2.10 CN-Initiated Service Awareness Specific for Non-Roaming Users of the Primary Operator

1816.2.2.11 CS and PS Non-Service Direct Transfer Message Blocks Now Added to RNC PCHR Logs

1846.2.2.12 Layer 2 Release Blocks Now Added to RNC PCHR Logs

1856.2.2.13 Support for Subrack DIP Switch Status Check

1876.2.2.14 Upgrade Tool Reliability Optimization

1896.2.2.15 Replacing SCUa with SCUb Online



1916.3.1 Critical

1916.3.2 Major

1916.3.2.1 PS services fail to be set up due to insufficient memory for the IP address pair table on the Iu-PS interface board.

1926.3.2.2 Services fail to be set up after a cell update with SRNS relocation is complete.

1926.3.2.3 The RNC does not process INITIAL DIRECT TRANSFER messages in an RRC connection release procedure.

1936.3.2.4 The uplink SRB fails to be reconfigured again after it is reconfigured from the DCH to the E-DCH.

1946.3.2.5 The relocation preparation procedure fails when the target cell is not configured as an external neighboring UMTS cell of the source cell.

1956.3.2.6 A cell cannot be selected as the target cell for CLB-triggered inter-frequency handover because this cell is not configured with the CLB algorithm.

1966.3.2.7 Configuration information about intelligent optimization-related features is not displayed in the MML configuration script.

1976.3.2.8 The RNC fails to deactivate the CPC-DTX/DRX function for non-serving radio links in soft handover scenarios.

1986.3.2.9 A UE cannot trigger the RB Parking function after a queuing failure.

1986.3.2.10 The DSP experiences a reset for self-healing due to a communication failure between the SPU subsystem and the DSP.

1996.3.2.11 Link configuration fails due to high maximum downlink transmit power of a UE.

1996.3.2.12 PS streaming services cannot be established if the RAN does not support the MBR assigned by the CN.

2006.3.2.13 The RMV UEXT3GCELL, MOD UCELLFREQUENCY, or RMV UNRELATION command fails to be executed.

2016.3.2.14 SRBs fail be carried on the HSDPA channel if UEs in the CELL_PCH or URA_PCH state switch to the CELL_DCH state.

2026.3.2.15 PS services experience call drops during the CS service release after a CS service reconfiguration.

2036.3.2.16 UEs experience mute voices after the AMR-WB code reconfiguration function takes effect.

2046.3.2.17 Operator indexes of GSM cells served by all logical RNCs belonging to a physical RNC are modified after the ADD UCNOPERATOR, RMV UCNOPERATOR, ADD UCNOPEREXTPLMN, or RMV UCNOPEREXTPLMN command is executed.

2056.3.2.18 PTT service setup fails when Downlink Enhanced L2 is enabled.

2066.3.2.19 The overflow RNC becomes faulty in RNC in Pool load sharing networking, and KPIs deteriorate significantly.

2096.3.2.20 The DRNC fails to identify platinum users.

2096.3.2.21 The RL reconfiguration over the Iur interface fails due to compatibility issues.

2116.3.2.22 The RNC sends SPID-specific dedicated priority to UEs that does not support LTE.

2116.3.2.23 The UE experiences a call drop during a UE-not-involved relocation.

2126.3.2.24 Services are interrupted after RL reestablishment.

2136.3.2.25 RL reconfiguration fails when a service is reconfigured from an HSUPA+ channel to an HSUPA channel.

2146.3.2.26 The point-to-point short message service cannot be disabled on a per cell basis.

2156.3.2.27 The number of hash indexes used on an interface board exceeds the maximum value during the ADD IPPATH or ADD SCTPLNK command execution.

2156.3.3 Minor

2156.3.3.1 The RNC fails to encode RRC-related messages during a combined cell update and SRNS relocation.

2166.3.3.2 The CELL ID+RTT positioning calculation fails.

2176.3.3.3 There is a possibility that the interval between two paging messages for a PTT service is 640 ms.

2186.3.3.4 The UE occasionally experiences a CS service setup failure after it initiates a cell update procedure during the security mode command procedure.

2196.3.3.5 The values of the VS.GTPU.Pkt.Tx and VS.GTPU.BytesPkt.Tx counters are incorrect.

2196.3.3.6 Links become out of synchronization due to the large transmission delay difference between cells in the active set.

2206.3.3.7 SAAL link-related counter is abnormal for AOUa, AEUa, and ATM-based UOIa boards.

2216.3.3.8 The CBSADDR and RNCCBCPUID objects cannot be synchronized from the backup RNC to the master RNC.

2226.3.3.9 The SPU CPU usage rises instantaneously due to the execution of the SET UCHRSCOPE or SET UMRSCOPE command.

2236.3.3.10 No statistics are available for UE transitions from common channels to dedicated channels that are triggered by data transmission requirements.

2256.3.3.11 The RNC delivers MR A-GPS measurement control messages to UEs in the MR A-GPS blacklist immediately after an incoming relocation.

2266.3.3.12 Some SAAL links to an AOUa board become faulty after ATM overbooking is enabled or disabled.

2276.3.3.13 The causes for signaling link interruption or transmission faults cannot be quickly identified.

2276.3.3.14 The value of the Hosted domain queried in the DSP OPC command output is incorrect.

2286.3.3.15 Optical port numbers are incorrect in ALM-21398 Optic Power Abnormal reported by a GOUa board.

2296.3.4 Suggestion

2296.3.4.1 The RNC fails to reset the Iu interface in Iu-Flex scenarios.

2316.3.4.2 An inappropriate message is displayed when the pre-upgrade check item "Operating system version" fails.

2316.3.4.3 ALM-22302 KPI Exceed Threshold is not reported for KPI deterioration caused by DPUe hardware faults.

2326.3.4.4 The RNC fails to respond to the CN with the RAB ASSIGNMENT RESPONSE message.

2336.3.4.5 When LDR is triggered due to cell code resource congestion, no UE cannot be selected for LDR because the proportions of code resources utilized by all operators do not exceed the preset limit.

2346.3.4.6 The call drop rate of UEs in the CELL_FACH state increases due to SRB resets.

2356.3.4.7 The RNC cannot initiate redirections, handovers, or fast return to E-UTRAN cells on frequency band 28.

2376.3.4.8 The RNC sends the UE EARFCNs that the UE does not support when initiating blind redirections or fast return.

2386.3.4.9 The RNC incorrectly calculates the GSM cell load when triggering a service-based or load-based UMTS-to-GSM handover.

2396.3.4.10 The RNC fails to update the number of RB Parking UEs in a cell in time when the number of RB Parking UEs in the cell reaches the maximum value.

2396.3.4.11 The RNC incorrectly sets the offset of the maximum FACH transmit power to 0 after the execution of the MOD USCCPCH command.

2406.3.4.12 The NodeB returns a failure message for RL setup or reconfiguration when the DC-HSDPA+MIMO and CPC-DTX/DRX features are both configured or the DB-HSDPA+MIMO and CPC-DTX/DRX features are both configured.

2426.3.4.13 The RNC incorrectly determines whether WRFD-160208 160 HSPA Users per Cell and WRFD-160209 192 HSPA Users per Cell are enabled.

2436.3.4.14 FAM data differs from BAM data if the MOD UCELLNAME command is executed after cell relocation.

2436.3.4.15 Some terminals display the GPS icon that should not be displayed.

2456.3.4.16 Power consumption of some terminals increases because they fail to disable the A-GPS function.

2466.3.4.17 The SPU subsystem is reset due to excess soft handover messages.

2476.3.4.18 The RNC fails to clear the timer as excepted after UEs whose resources are preempted enter the RB Parking state.

2486.3.4.19 The block status of cells and NodeBs cannot be synchronized from the master RNC to the backup RNC.

2486.3.4.20 The MR function does not take effect for UEs whose best cells are DRNC cells.

2496.3.4.21 Call drops occur because soft handovers cannot be triggered in time after incoming static relocations over the Iur interface are complete.

2506.3.4.22 Service groups that are added for a differentiated services code point (DSCP) after the digital signal processor (DSP) is successfully loaded do not take effect.

2516.3.4.23 The "Cell Load Information Group" IE in the RELOCATION REQUIRED message cannot be parsed.

2546.3.4.24 A UE in the CELL_FACH state fails to initiate CS services.

2546.3.4.25 There are no license control items in the license file for features that are changed from trial features.

2566.3.4.26 The RNC does not support measurements of downlink PS service quality related to multiple throughput thresholds during the same period.

2596.3.4.27 The UE experiences a call drop due to RL failures caused by reasons other than synchronization failures.

2596.3.4.28 Services or cells cannot be established on the DSP subsystem whose KPIs deteriorate.

2606.3.4.29 The SPU CPU usage rises instantaneously due to the execution of the SET UCHRSCOPE or SET UMRSCOPE command.

2626.3.4.30 The queried OMUc board electronic label is incorrect.

2636.3.4.31 The alarm location information in some transmission alarms is insufficient.

2646.3.4.32 The failure cause cannot be quickly identified when an IP continuity check fails.

2646.3.4.33 No information is available for locating the fault when a chip of the signaling processing board, service processing board, service identification board, or interface processing board fails to be initialized.

2656.3.4.34 The setting of the Check active/standby status consistency option is inconsistent with the actual function implementation.

2666.4 Known Issues

2666.4.1 Critical

2666.4.2 Major

2666.4.3 Minor

2666.4.4 Suggestion

2677 Changes from V900R016C00SPH608 to V900R016C00SPH609



2687.1.2 Hardware

2687.1.3 Features













2707.3.1 Critical

2707.3.2 Major

2707.3.2.1 The WebLMT displays a message "Internal error" if the file name of an uploaded file contains Chinese characters in batch configuration.

2707.3.2.2 Multicast configuration fails after an SCU board has been running for an excessively long period of time.

2717.3.3 Minor

2717.3.4 Suggestion

2717.4 Known Issues

2717.4.1 Critical

2717.4.2 Major

2727.4.3 Minor

2727.4.4 Suggestion




2748.1.2 Hardware

2748.1.3 Features













2768.3.1 Critical

2768.3.2 Major

2768.3.2.1 The CN or the neighboring RNC signaling points become unavailable when the signaling point code is expressed in segments.

2778.3.2.2 The RNC incorrectly unblocks cells when processing the NBAP audit response message.

2788.3.2.3 The AOUc or UOIc boards are switched over after SAAL link loopback detection is enabled on these boards.

2798.3.2.4 The service awareness-based user experience evaluation function becomes unavailable after the NIUa board has been running for more than 24 consecutive days.

2798.3.3 Minor

2798.3.4 Suggestion

2798.4 Known Issues

2798.4.1 Critical

2808.4.2 Major

2808.4.3 Minor

2808.4.4 Suggestion




2829.1.2 Hardware

2829.1.3 Features











2849.2.2.1 Optimization of the Inter-Frequency DRD Function During PS Service Setup

2859.2.2.2 PCHR, MR, and VIP Files Generated Within a Full Hour

2879.2.2.3 Inter Frequency Load Balance Feature Considering HSDPA User Number in Candidate Cells

2899.2.2.4 Transmission Requirements-based Channel Reconfiguration for the PS Service in CS+PS Combined Services Considering RF Quality

2929.2.2.5 Uplink Rate of PS BE Services Not Reduced to the Initial Access Rate After HSUPA Reconfiguration

2949.2.2.6 Added the G_NIC Command Group for Encapsulating All Commands for the NIC Function

2959.2.2.7 Enhanced Anti-Attack Protection for Fragmented Packets Received by the Interface Board



2979.3.1 Critical

2979.3.1.1 Measurement control hampers the CS RB setup, leading to incorrect adjustment of encryption parameters.

2989.3.2 Major

2989.3.2.1 The Huawei DRNC does not support radio link addition with serving cell changes.

2999.3.2.2 The measured value of the VS.AMR.Erlang.Equiv.PLMN.RNC counter is incorrect in MOCN scenarios.

3009.3.2.3 The IDs of six counters in RAN16.0 are inconsistent with the IDs of these counters in RAN15.0.

3009.3.2.4 UEs that cannot be handed over to the LTE network still start RSCP measurements after the function of service-based UMTS-to-LTE handover requiring RSCP measurement is enabled.

3019.3.2.5 Services cannot be set up after a large number of event 1J reports fail to be processed.

3029.3.2.6 Services carried on a port of the SCUa board are affected due to inconsistency between the detection result and actual status of the port.

3029.3.2.7 KPIs related to the CS CDR and PS CDR deteriorate when the active port is on the GOUe working in standby mode and the NodeB enables the FPMUX function.

3039.3.3 Minor

3039.3.3.1 The integrity of RNC configuration data may be damaged when the "easy-in, difficult-out" principle is used to configure intra-frequency neighboring cells on the CME.

3049.3.3.2 Synchronization between the controller and the U2000/CME has not been performed for a long time because configuration synchronization times out for several times.

3059.3.3.3 The AOUc/POUc/UOIc/PEUc/SPUb/DPUe/NIUa/FG2c/GOUc board incorrectly reports ALM-20280 Board Temperature Abnormal.

3069.3.4 Suggestion

3069.3.4.1 The UMTS cell load information sent by the RNC to the eNodeB is delayed.

3079.3.4.2 The call drop rate increases after the Fast Radio Bearer Setup feature is enabled in weak coverage areas.

3089.3.4.3 A cell enabled with the Downlink Enhanced CELL_FACH feature accommodates a lesser number of DCH UEs than the configuration allows due to a large number of FACH UEs are admitted.

3099.3.4.4 The solution for the problem that the channel type of a UE frequently switches between HSPA and DCH when the UE performs LTE measurement without starting the compressed mode is not controlled by any MML parameter.

3099.3.4.5 SRBs cannot be carried on HS-DSCHs when the SRB D2H enhancement algorithm is enabled and the uplink admission fails.

3109.3.4.6 Cross-Iur handovers fail when SRBs are carried on E-DCHs in the uplink.

3119.3.4.7 The permissions of local users are lost when the BSC database is abnormal.

3129.3.4.8 Instantaneous traffic is too heavy after the FTP upload and download performance is optimized.

3129.3.4.9 The value of a single bit in the FPGA of the AOUc/POUc/UOIc/PEUc/DPUe/NIUa/FG2c/GOUc board is changed and the FPGA cannot recover through self-healing.

3139.4 Known Issues

3139.4.1 Critical

3139.4.2 Major

3139.4.3 Minor

3139.4.4 Suggestion

31410 Changes from V900R016C00SPC600 to V900R016C00SPH602



31510.1.2 Hardware

31510.1.3 Features











31710.2.2.1 Optimized Load Based Dynamic Adjustment of PCPICH

31910.2.2.2 Inter-RAT DRD for Combined Services

32010.2.2.3 Control on the Scope of Intra-Frequency Periodic Measurement Reports

32210.2.2.4 Control on the Number of Intra-Frequency Periodic Measurement Reports

32310.2.2.5 Immediately Notifying the Peer End of the Receive Buffer Space Update

32510.2.2.6 Upgrade Tool Supporting Risk Check Before an Upgrade

32710.2.2.7 Removed the FTP Text Box from the Batch Configuration Module

32810.2.2.8 Support for Feature-based Information Display in the LST LICENSE Command Output



32910.3.1 Critical

32910.3.2 Major

32910.3.2.1 The measurement scopes are incomplete for counters measuring the number of successful CS service establishments initiated by UEs.

33310.3.2.2 The RNC continues to allocate services to the DPU boards when the service subrack accommodating these boards is being removed.

33410.3.2.3 GPS data is redundantly broadcast among SPU subsystems.

33510.3.2.4 Users cannot log in to the WebLMT on the PC where JRE of a specific version is installed.

33510.3.2.5 The FG2a or GOUa board does not perform BFD in compliance with RFC 5880.

33610.3.2.6 The High-Risk Command List in MML Command Reference includes some non-risky commands.

33710.3.3 Minor

33710.3.3.1 Cell user number on Cell Performance Monitoring is still greater than 0 after the NodeB is powered off.

33710.3.3.2 PS services whose resources cannot be preempted have their resources preempted.

33810.3.3.3 The RNC does not record PCHR logs for online users in a certain scenario.

33910.3.3.4 The distribution of DC-HSDPA users is inconsistent before and after the upgrade.

34010.3.3.5 The excessively long MML command outputs cannot be completely displayed on the U2000.

34110.3.3.6 The BSC occasionally reports ALM-20241 Board Unavailable with Slot No. set to EMU.

34210.3.4 Suggestion

34210.3.4.1 Configuration data in the OMU buffer may be inconsistent with that in the OMU database after the SET UKPIALMTHD command is executed.

34210.3.4.2 The functions of code resource preemption for HSPA common channels forcibly take effect in upgrade scenarios.

34310.3.4.3 The number of failed preparations for LTE-to-UMTS handovers increases due to incorrect calculation of DC carrier group load on the RNC side.

34410.3.4.4 The measurement points of counters measuring the RRC and RAB setups of CSFB UEs have been changed.

34510.3.4.5 The call drop rate is high during SRB bearer channel reconfiguration.

34710.3.4.6 The combined cell update and relocation procedure fails when a UE has a single CS signaling connection.

34810.3.4.7 The alarm location information in ALM-21521, ALM-21503, and ALM-21553 is insufficient.

34810.3.4.8 The counter values measured during a patch upgrade are incorrect.

34910.4 Known Issues

34910.4.1 Critical

34910.4.2 Major

34910.4.3 Minor

34910.4.4 Suggestion

35011 Operation and Maintenance Changes

35011.1 MML Command Changes

35011.2 Parameter Changes

35011.3 Alarm Changes

35011.4 Event Changes

35011.5 Counter Changes

35111.6 License Changes

35111.7 Other Changes

352A Obtaining Documentation

354B Acronyms and Abbreviations

1 Version Requirements1.1 Product VersionProduct NameHUAWEI BSC6900

Product ModelHUAWEI BSC6900

Product VersionV900R016C00SPC650

1.2 Software VersionsSoftwareVersion

LMTV900R016C00SPC650

BAMV900R016C00SPC650

U2000 MediationBSC6900 UMTS:iManagerOSS_BSC6900UMTS_MATCH_ENG_V200R014C00SPC650

1.3 Hardware VersionsPhysical Board NameLogical Board NameBar Code LabelPCB VersionBIOS/Extended BIOS VersionBootROM Upgrade Required (Yes/No)

SCUaSCUaWP11SCUaVer.D269Yes

GCUaGCUaWP11GCUaVer.BVer.CVer.FVer.G269Yes

GCGaGCGaQW21WGCGaVer.BVer.CVer.FVer.G269Yes

SPUaSPUa/UCPSPUa/RUCPWP11SPUaVer.BVer.C269Yes

DPUbDPUb/UUPWP13DPUbVer.C269Yes

AEUaAEUa/ATMWP11AEUaVer.A120Yes

AOUaAOUa/ATMWP11AOUaVer.A120Yes

UOIaUOIa/ATMUOIa/IPWP11UOIaVer.A120Yes

PEUaPEUa/IPWP11PEUaVer.A120Yes

POUaPOUa/IPWP11POUaVer.A120Yes

FG2aFG2a/IPWP11FG2aVer.A120Yes

GOUaGOUa/IPWP11GOUaVer.A120Yes

SPUbSPUb/UCPSPUb/RUCPSPUb/NASPWP11SPUbVer.BVer.CVer.DVer.EVer.F140Yes

DPUeDPUe/UUPWP11DPUeVer.BVer.CVer.E141Yes

AOUcAOUc/ATMWP11AOUcVer.BVer.CVer.E141Yes

UOIcUOIc/ATMWP11UOIcVer.BVer.CVer.E141Yes

POUcPOUc/IPWP11POUcVer.BVer.CVer.E141Yes

FG2cFG2c/IPWP11FG2cVer.BVer.CVer.E141Yes

GOUcGOUc/IPWP11GOUcVer.BVer.CVer.E141Yes

OMUaOMUaWP11OMUa-042-

OMUcOMUcWP13OMUcVer.B102Yes

SCUbSCUbWP11SCUbVer.BVer.C133Yes

NIUaNIUaWP11NIUaVer.E141Yes

PEUcPEUcWP11PEUcVer.A141Yes

GCUbGCUbWP11GCUbVer.C137Yes

GCGbGCGbQW11WGCGbVer.C137Yes

SPUcSPUc/UCPSPUc/RUCPSPUc/NASPWP11SPUcVer.A106Yes

GOUeGOUe/IPWP11GOUeVer.A106Yes

1.4 Related Product VersionsProduct NameProduct ModelProduct VersionRemarks

U2000U2000iManager U2000 V200R014C00SPC200 or laterN/A

CMECMEiManager U2000-CME V200R014C00SPC200 or later

PRSPRSiManager PRS V100R014C00 or later

ECO6910ECO6910ECO6910 V100R003C00SPC600 or later

ToolsINSIGHT SHARPINSIGHT SHARP V100R002C00SPC700 or later

NASTARGENEX Nastar V600R014C00SPC100 or later.NOTE If you need to configure two SAU boards, the version of the two SAU boards must be GENEX Nastar V600R011C00SPC201 or later. If the GNFD-201220 UMTS Data Service Resource Analysis or GNFD-201230 UMTS Terminal Traffic Model Analysis feature of the GENEX Nastar needs to be enabled, the GENEX Nastar in V600R014C00SPC230 or later is required.

NodeBNodeB V1DBS3800 V100R016C00SPC100BTS3812E V100R016C00SPC100RAN16.0

NodeB V2BTS3900 V100R009C00SPC100 or laterRAN16.0

1.5 OS and Database VersionsOS/Database VersionPatch Package VersionRemarks

Windows 2003 Server Standard Edition SP2Patch package:Win2k3ENx8620xxBasic(Basic patch package) + win2k3ENx8620xxyy(Increment patch package)NOTEInstall the increment patch package only when it exists.Only the installation can be performed.Contact Huawei engineers who can obtain the patch package by performing the following operation:1. Access http://support.huawei.com.2. After a successful login, choose Software Center > Version Software > Wireless Product Line > SingleRAN > MBSC.3. Download the newest patch version.NOTEThe detailed information about the patch is listed in the Patches information list.

SUSE Linux 9NoneOnly the installation can be performed.

DOPRA Linux V100R001C03NoneThe installation and upgrade can be performed.

DOPRA Linux V200R003DOPRA Linux V200R003C08SPC080NOTEPatch packages of earlier versions can still be used, but you are advised to use the DOPRA Linux patch package of the latest version.The installation can be performed, and some versions can be upgraded to the latest patch version. For details about these versions, see section 1.1 "Environment Requirements for Upgrade" in Guide to Dopra Linux Operating System Remote Patch Upgrade.NOTEContact Huawei engineers who can obtain Guide to Dopra Linux Operating System Remote Patch Upgrade by performing the following operation:1. Access http://support.huawei.com.2. After a successful login, choose Software Center > Version Software > Wireless Product Line > SingleRAN > MBSC.3. Download Guide to Dopra Linux Operating System Remote Patch Upgrade.

MySQL5.0.96NoneOnly the installation can be performed.

1.6 Related DocumentationSolution VersionProduct VersionDocumentationWebsite

RAN16.0BSC6900 V900R016C00SPC650(For Customer)BSC6900 UMTS Product Documentation(V900R016C00_06)-ENA Obtaining Documentation

(For Customer)RAN16.0 Feature Documentation 06 (HDX)-EN

RAN16.0BSC6900 V900R016C00SPC630(For Customer)BSC6900 UMTS Product Documentation(V900R016C00_05)-EN


RAN16.0BSC6900 V900R016C00SPH621BSC6900 V900R016C00SPC620(For Customer)BSC6900 UMTS Product Documentation(V900R016C00_04)-EN


RAN16.0BSC6900 V900R016C00SPH608BSC6900 V900R016C00SPH605(For Customer)BSC6900 UMTS Product Documentation(V900R016C00_03)-EN


RAN16.0BSC6900 V900R016C00SPH602(For Customer)BSC6900 UMTS Product Documentation(V900R016C00_02)-EN


RAN16.0BSC6900 V900R016C00SPC600(For Customer)BSC6900 UMTS Product Documentation(V900R016C00_01)-EN


1.7 Virus Scan ResultThis software package has been scanned by the following antivirus software and no risks were found. The following table lists the virus scan results.Antivirus Software NameAntivirus Software VersionAntivirus Database VersionTime of ScanResult

Kav10.1.0.86720141227-0600132014-12-31No risks were found.

Avira8.03.28.0047.11.198.0202014-12-31No risks were found.

Symantec12.1.2015.20152014-12-25r32014-12-31No risks were found.

McAfee5600:10677662:02014-12-31No risks were found.

OSCE9.750.100711369002014-12-31No risks were found.

1.8 Important NotesTable 1-1 Important notes for using BSC6900 V900R016C00SPC650No.EventRemarks

1Time restrictionsNone

2Region/site restrictionsNone

3Other restrictionsThe restricted features must be tested on one site before the commercial release.

4Version terminationThe time that a version terminates depends on the version lifecycle management.

2 Version Compatibility2.1 Software Version CompatibilityRNC version compatibility: The current version supports all the features of BSC6900V900R015C00, BSC6900V900R014C00 and earlier versions.2.2 Hardware Version CompatibilityThe following table describes compatibility between the hardware and the software versions.

Y indicates that the current product version is compatible with an earlier board software version, and N indicates that the current product version is incompatible with an earlier board software version.Board NameBSC6900V900R015C00BSC6900V900R014C00

SCUaYY

SCUbYY

GCUaYY

GCGaYY

SPUaYY

SPUbYY

DPUbYY

DPUeYY

AEUaYY

AOUaYY

AOUcYY

UOIaYY

UOIcYY

PEUaYY

POUaYY

POUcYY

FG2aYY

FG2cYY

GOUaYY

GOUcYY

OMUaYY

OMUcYY

NIUaYY

PEUcYN

GCUbNN

GCGbNN

SPUcNN

GOUeNN

3 Changes from V900R016C00SPC630 to V900R016C00SPC6503.1 Change SummaryCapacity and PerformanceCompared with those in BSC6900 V900R016C00SPC630, capacity and performance remain unchanged in V900R016C00SPC650.HardwareCompared with that in BSC6900 V900R016C00SPC630, hardware remains unchanged in V900R016C00SPC650.FeaturesCompared with those in BSC6900 V900R016C00SPC630, 20 features have been modified, but no features have been added or deleted in V900R016C00SPC650.3.1.3 Features provides the following information about new or modified features: Whether this feature has any impact on capacity and performance Whether this feature is license-controlled Whether this feature requires hardware support Whether data configurations are required to enable this featureResolved IssuesCompared with those in BSC6900 V900R016C00SPC630, 1 critical issues, 24 major issues, 24 minor issues, and 14 suggestion-level issues have been resolved in V900R016C00SPC650.3.1.4 Resolved Issues provides the following information about resolved issues: Whether there is any impact of this solution Whether this solution is controlled by a parameter Default value of the parameter that controls the solution after an upgradeOperation and Maintenance Configuration managementCompared with those in BSC6900 V900R016C00SPC630, configuration management functions remain unchanged in V900R016C00SPC650. For details, see 11.1 MML Command Changes and 11.2 Parameter Changes. Performance managementCompared with those in BSC6900 V900R016C00SPC630, performance management functions remain unchanged in V900R016C00SPC650. For details about counter changes, see 11.5 Counter Changes. Fault managementCompared with those in BSC6900 V900R016C00SPC630, fault management functions remain unchanged in V900R016C00SPC650. For details about alarm and event changes, see 11.3 Alarm Changes and 11.4 Event Changes, respectively. License managementCompared with those in BSC6900 V900R016C00SPC630, license management functions remain unchanged in V900R016C00SPC650. For details, see 11.6 License Changes.Related DocumentationCompared with those in BSC6900 V900R016C00SPC630, document organization and document templates remain unchanged in V900R016C00SPC650. For details, see 3.1.6 Related Documentation.3.1.2 Capacity and PerformanceThis section describes the general impact of this versin on system capacity and network performance.Compared with those in BSC6900 V900R016C00SPC630, capacity and performance remain unchanged in BSC6900 V900R016C00SPC650.3.1.3 HardwareThis section describes any hardware addition and modification. The hardware end of marketing (EOM) and end of service (EOS) information does not map onto the software version. For details, see the corresponding product change notice (PCN).New HardwareNoneModified HardwareNone3.1.4 FeaturesThis section provides a summary of all features changes from BSC6900 V900R016C00SPC630 to V900R016C00SPC650.The summary provides the following information: Change type Feature description Impact on capacity and performance Whether this feature is license-controlled Hardware support required by this feature Whether this feature requires hardware support Whether data configurations are required to enable this featureFor a summary of these changes, see Summary of Feature Changes in BSC6900 UMTS V900R016C00SPC650.xls, or see the V900R016C00SPC650 vs V900R016C00SPC630 sheet in Summary of Feature Changes delivered with the release notes for a version later than BSC6900 V900R016C00SPC650.For details, see 3.2 Feature Changes.3.1.5 Resolved IssuesThis section provides the summary of the known issues in BSC6900 V900R016C00SPC630 that have been resolved in V900R016C00SPC650. Trouble ticket number Issue description Severity Solution impact Parameter control Default value of the parameter that controls the solution after an upgrade.For a summary of these issues, see Summary of Resolved Issues in BSC6900 UMTS V900R016C00SPC650.xls, or see the the V900R016C00SPC650 vs V900R016C00SPC630 sheet in Summary of Resolved Issues delivered with the release notes for a version later than BSC6900 V900R016C00SPC650.For details about these issues, see 3.3 Resolved Issues.3.1.6 Operation and Maintenance3.1.6.2 Configuration ManagementCompared with V900R016C00SPC630, configuration management functions remain unchanged in V900R016C00SPC650. For details about configuration management, see 11.1 MML Command Changes and 11.2 Parameter Changes.3.1.6.3 Performance ManagementCompared with V900R016C00SPC630, performance management functions remain unchanged in V900R016C00SPC650. For details about counter changes, see 11.5 Counter Changes.3.1.6.4 Fault ManagementCompared with V900R016C00SPC630, fault management functions remain unchanged in V900R016C00SPC650. For details about changes to alarms and events, see 11.3 Alarm Changes and 11.4 Event Changes.3.1.6.5 License ManagementCompared with V900R016C00SPC630, license management functions remain unchanged in V900R016C00SPC650. For details about license changes, see 11.6 License Changes.3.1.7 Related DocumentationFor details about documentation updates, see (For Customer)BSC6900 UMTS Product Documentation (V900R016C00_06)(HDX)-EN.3.2 Feature Changes3.2.1 New FeaturesNone3.2.2 Modified Features3.2.2.6 Considering the Power Load of Multi-carrier HSDPA UEs in the CLB AlgorithmDescriptionThis feature allows the RNC to perform the following for a cell that supports multi-carrier HSDPA: Consider the power load of multi-carrier HSDPA UEs when making decisions on enabling CLB for the cell based on downlink power. Trigger inter-frequency handovers for multi-carrier HSDPA UEs after CLB has been enabled for the cell.ImplementationRESERVED_SWITCH_13_BIT18 under the RsvSwitch13 parameter in the SET UALGORSVPARA command controls whether to enable this feature. By default, this feature is disabled (default value: 0) for both new networks and upgrade scenarios.When this feature is enabled, the RNC performs the following for a cell that supports multi-carrier HSDPA: Considers the power load of multi-carrier HSDPA UEs when making decisions on enabling CLB for the cell based on downlink power. Triggers inter-frequency handovers for multi-carrier HSDPA UEs after CLB has been enabled for the cell.Impact on Capacity and PerformanceAfter this feature is enabled:The probability of enabling CLB for a cell increases.Inter-frequency outgoing hard handover attempts (indicated by counter VS.HHO.AttInterFreqOut.CS.TotalTxPwr and counter VS.HHO.AttInterFreqOut.PS.TotalTxPwr) triggered by downlink power congestion increase. The number of successful attempts (indicated by counter VS.HHO.SuccInterFreqOut.CS.TotalTxPwr and counter VS.HHO.SuccInterFreqOut.PS.TotalTxPwr) increases.The call drop rate increases.The RNC can evaluate cell load more accurately and balances inter-frequency load more effectively, improving resource utilization.Impact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license management:None Impact on configuration managementRESERVED_SWITCH_13_BIT18 under the RsvSwitch13 parameter in the SET UALGORSVPARA command is used to control whether to enable this feature. Impact on performance managementNone Impact on fault management:NoneImpact on Other FeaturesNoneRelated OperationsTo enable this feature, run the following MML command:SET UALGORSVPARA: RsvSwitch13 = RESERVED_SWITCH_13_BIT18-1;To disable this feature, run the following MML command:SET UALGORSVPARA: RsvSwitch13 = RESERVED_SWITCH_13_BIT18-0;Trouble Ticket NumberDTS: DTS2014111402733Feature IDWRFD-1402173.2.2.7 Iur-p Link Loopback Detection Self-HealingDescriptionIf an interface board that carries Iur-p links is improperly running, these links will be faulty for a long time. This feature supports Iur-p link detection in this scenario and enables the RNC to switch over or reset the faulty interface board once the Iur-p link fault in the interface board is detected.ImplementationIf an Iur-p link becomes faulty, the RNC will automatically initiate a detection from the control plane subsystem where the link is configured to the interface board that carries the link and checks whether the interface board is running properly. If the interface board is improperly running, the RNC will automatically switch over or reset the interface board.SW19 of Reserved Switch Parameter1 in the SET TNRSVDPARA controls whether to enable Iur-p link detection. By default, Iur-p link detection is enabled (default value: 0) for both new networks and upgrade scenarios. 0: Iur-p link detection is enabled. If the interface board that carries Iur-p links are improperly running, the base station controller will switch over or reset the interface board. 1: Iur-p link detection is disabled.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementEnabled SW19 of Reserved Switch Parameter1 in the SET TNRSVDPARA to control whether to enable Iur-p link detection. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated Operations To enable Iur-p link detection, run the following command:SET TNRSVDPARA: RSVDSW1=SW19-0; To disable Iur-p link detection, run the following command:SET TNRSVDPARA: RSVDSW1=SW19-1;Trouble Ticket NumberDTS:DTS2014110900149Feature IDNone3.2.2.8 Enhanced UMTS-to-LTE Fast Return Based on Combined ServicesDescriptionIn a UMTS-to-LTE fast return process, instead of triggering an RB release procedure, the RNC directly sends an RRC CONNECTION RELEASE message to release CS services. As a result, the delay in UMTS-to-LTE fast return is reduced.ImplementationWhen the CS service is terminated on a CSFB UE that is running combined services, the UE sends a DISCONNECT message to the RNC and the CS CN delivers an IU RELEASE COMMAND message to the RNC. Upon receiving the IU RELEASE COMMAND message, the RNC triggers a fast return procedure. After this feature takes effect, the RNC directly sends the UE an RRC CONNECTION RELEASE message that contains the frequency information about neighboring E-UTRAN cells. In this way, the delay caused by the RB release is reduced.RESERVED_SWITCH_12_BIT12 under the RsvSwitch12 parameter in the SET UALGORSVPARA command controls whether to enable this solution. By default, this solution is disabled (default value: 0) for both new networks and upgrade scenarios.Impact on Capacity and Performance The delay for a UE to return to the LTE network decreases. Service drops decrease.Impact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementRESERVED_SWITCH_12_BIT12 under the RsvSwitch12 parameter in the SET UALGORSVPARA command controls whether to enable this solution. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsTo enable this solution, run the following MML command:SET UALGORSVPARA: RsvSwitch12=RESERVED_SWITCH_12_BIT12-1;To disable this solution, run the following MML command:SET UALGORSVPARA: RsvSwitch12=RESERVED_SWITCH_12_BIT12-0;Trouble Ticket NumberDTS: DTS2014111706998Feature IDWRFD-1402263.2.2.9 Exporting Configuration Information in the SET LICENSE CommandDescriptionThis feature exports the configuration information in the SET LICENSE command to save the license allocation information of each operator.Implementation The enumerated value LIC_CFG_MML(The Allocated Information File of License) is added to the Log File Type parameter in the COL LOG command. When the COL LOG: LOGTYPE=LIC_CFG_MML-1; command is executed, the licensed values assigned to each operator can be saved to the setlicense.zip file in the OMU active workspace directory bam\version_x\ftp\COLLOGINFO\CFG-LOG\ExportLicCfgmml. During a patch rollback, the base station controller automatically exports the configuration information in the SET LICENSE command to the setlicense.zip file and saves this file in the OMU active workspace directory bam\version_x\ftp\operator_log\exp_log.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementAdded the enumerated value LIC_CFG_MML(The Allocated Information File of License) to the Log File Type parameter in the COL LOG command. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsTo export the license configuration information, run the following command:COL LOG: LOGTYPE=LIC_CFG_MML-1;Trouble Ticket NumberDTS: DTS2014080103737Feature IDNone3.2.2.10 Global Tracing of IMSI Messages in the CS DomainDescriptionThe RNC supports global tracing of the international mobile subscriber identity (IMSI) messages in the CS domain.Implementation1. The RNC initiates global tracing after receiving a CN_Invoke_Trace message over the Iu-CS interface, as shown in the following figure:

After an Iu-CS interconnection is established and the RNC receives a CN INVOKE TRACE message from the CN, the RNC initiates global tracing and the RNC can report the RRC CONNECTION REQUEST, RADIO LINK SETUP REQUEST, and CN INVOKE TRACE messages. When the signaling connection over the Iu-CS interface is released, the RNC stops the global tracing. The RNC OMU generates a trace files and sends the files to the U2000. The U2000 receives the trace files from the RNC OMU. The trace file is named A_XXXXXXXX_XXXXXX+YYYY_RNC_RRRR_TT.tmf. In the file name, XXXXXXXX_XXXXXX indicates the date_time zone offset, YYYY indicates the daylight saving time (DST), RRRR indicates the tracing reference, and TT indicates the transaction ID.2. Specifications and restrictions: If the RNC has initiated UE tracing, RAN integrated tracing, or DTMF tracing, the RNC cannot initiate global tracing on the UE. In this case, if the RNC has initiated global tracing for the UE, the RNC can initiate UE tracing, RAN integrated tracing, and DTMF tracing but reports no tracing results. The RNC can initiate single-user tracing (such as the UE tracing, RAN integrated tracing, and global tracing of IMSI signaling messages) for a maximum of 12 UEs at a time.RESERVED_SWITCH_0_BIT1 under the RSVSWITCH0 parameter in the SET UCNNODERSVPARA command controls whether to enable this solution. By default, this solution is disabled (default value: 0) for both new networks and upgrade scenarios. When this solution is enabled, the RNC initiates global tracing. When this solution is disabled, the RNC does not initiates global tracing.Impact on Capacity and PerformanceCPU usage of the SPU subsystem surges and the RRC connection setup success rate decreases during peak hours.Impact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated Operations To enable this solution, run the following MML command:SET UCNNODERSVPARA:CnOpIndex=X, CNId= X, RSVSWITCH0=RESERVED_SWITCH_0_BIT1-1; To disable this solution, run the following MML command:SET UCNNODERSVPARA:CnOpIndex= X, CNId= X, RSVSWITCH0=RESERVED_SWITCH_0_BIT1-0;Trouble Ticket NumberDTS: DTS2014110406934Feature IDNone3.2.2.11 Optimization of NIC Information Collection Based on SOPDescriptionWhen network information is collected using the NIC tool and UMTS_BSC6900_SOP is selected as the collection scenario, input parameters of some collection items need to be manually specified. This operation is not suitable for collecting large amount of information and affects O&M efficiency. This feature enables the NIC tool to automatically collect information about each collection item without manually specifying parameters.ImplementationAfter the NIC tool delivers the command for querying collection item information to an NE, the NIC tool parses the scripts sent from the NE to automatically obtain the required parameter settings. In this way, users do not need to manually specify these parameters.For example, before this feature is introduced, users need to manually specify Subrack No. and Slot No. to collect board common information, as shown in the following figure.

After this feature is introduced, when network information is collected using the NIC tool and UMTS_BSC6900_SOP is selected as the collection scenario, the parameters shown in the preceding figure are no longer displayed and do not need to be manually specified. The NIC tool can automatically collect information about each collection item.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014120801457Feature IDNone3.2.2.12 LAI and SAI IEs Supported in the DIRECT TRANSFER Message in the CS DomainDescriptionWith this solution, the DIRECT TRANSFER message sent to the CN by the RNC can carry the SAI and LAI IEs, which provides location information during CS service implementation.ImplementationWhen a UE initiates CS services, the RNC sends the CN a DIRECT TRANSFER message that does not carry the LAI or SAI IE by default.RESERVED_SWITCH_0_BIT2 under the RSVSWITCH0 parameter in the SET UCNNODERSVPARA command controls whether the DIRECT TRANSFER message carries the LAI and SAI IEs.

The SET UCNNODERSVPARA command takes effect only after the CnOpIndex and CNId parameters are set.By default, this solution is disabled (default value: 0) for both new networks and upgrade scenarios.When this solution is enabled, the DIRECT TRANSFER message sent to the CN by the RNC carries the SAI and LAI IEs.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsRun the following MML command to enable this solution:SET UCNNODERSVPARA: CnOpIndex=X, CNId=X, RSVSWITCH0=RESERVED_SWITCH_0_BIT2-1;Run the following MML command to disable this solution:SET UCNNODERSVPARA: CnOpIndex=X, CNId=X, RSVSWITCH0=RESERVED_SWITCH_0_BIT2-0;Trouble Ticket NumberDTS: DTS2014111910118Feature IDNone3.2.2.13 Support notifying the information of UEs capable of downlink DC-HSDPA throughput optimization to the NodeBDescriptionFor UEs that support downlink DC-HSDPA throughput optimization, the RNC includes the proprietary extended IE reserved3-private with the value of 1 in the RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and RADIO LINK RECONFIGURATION PREPARE messages sent to the NodeB over the Iub interface.

Corresponding modification is also made on the NodeB side. For details, see the description of DTS2014112107374 in BTS3900 V100R009C00SPC186 Release Notes.ImplementationRESERVED_SWITCH_BIT25 under the RsvSwitch parameter in the ADD UIMEITAC and MOD UIMEITAC commands controls whether to enable this solution. By default, this solution is disabled (default value: 0) for both new networks and upgrade scenarios. When this solution is enabled, the RNC includes the reserved3-private IE in the three messages. When this solution is disabled, the RNC does not include the reserved3-private IE in the three messages.Run the following MML command to enable this solution:ADD/MOD UIMEITAC: TAC_FUNC=Special_User_Enhance, TAC=*, Description="*", RsvSwitch=RESERVED_SWITCH_BIT25-1;Run the following MML command to disable this solution:ADD/MOD UIMEITAC: TAC_FUNC=Special_User_Enhance, TAC=*, Description="*", RsvSwitch= RESERVED_SWITCH_BIT25-0;

In order for the solution to take effect, all UEs must report their international mobile equipment identities (IMEIs) in either of the following ways: The CN can query the IMEI of a UE running PS services. Run the following command to query the IMEI of a UE on the RNC:SET URRCTRLSWITCH: PROCESSSWITCH2=RNC_PS_QUERY_UE_IMEI_SWITCH-1;Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementRESERVED_SWITCH_BIT25 under the RsvSwitch parameter in ADD UIMEITAC and MOD UIMEITAC commands is used. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsTo enable this feature, run the following command:ADD/MOD UIMEITAC: TAC_FUNC=Special_User_Enhance, TAC=*, Description="*", RsvSwitch=RESERVED_SWITCH_BIT25-1;Trouble Ticket NumberDTS: DTS2014111910125Feature IDNone3.2.2.14 Support for Checking Resources of License Resource Items During a Pre-upgradeDescriptionThis feature adds a license file check mechanism to the upgrade tool during a pre-upgrade of the base station controller. If the number of resources of feature resource items in the license file does not meet the license sales principles, a message is displayed on the upgrade tool indicating that resources allocated to license resource items are insufficient.ImplementationDuring a pre-upgrade to BSC6900 V900R016SPC620BSC6910 V100R016SPC620 or later, the upgrade tool checks the number of resources of feature resource items in the license file. If the licensed number of resources is less than the reference number of resources in the license sales principles, a message is displayed indicating that resources allocated to license resource items are insufficient. After the upgrade, ALM-20259 Number of Resources Used Exceeding Threshold Specified by License may be reported, and you are advised to apply for licenses according to the license sales principles as soon as possible. For details about the reference number of resources of license resource items, see License Control Item Lists.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014073002842Feature IDNone3.2.2.15 Optimized Features for RACH Keepalive FunctionDescriptionIf the transmission link for the random access channel (RACH) is disconnected, the RNC negotiates with the NodeB to determine whether to enable the RACH keepalive function.ImplementationThe field "PRIVATE RACHKEEPALIVEDETECT CAPABILITY" has been added to the audit response message so that the NodeB proactively reports whether a cell supports the RACH keepalive function. If the NodeB reports that the cell supports the keepalive function and the switch is also turned on, the RNC enables the RACH keepalive function. In other cases, the RNC does not enable the RACH keepalive function.RsvdSwitch1_Bit31 of the RsvdSwitch1 parameter in the SET UDPUCFGDATA command controls whether to enable this solution. By default, this solution is enabled (default value: 0) for both new networks and upgrade scenarios.Run the following command to enable this solution:SET UDPUCFGDATA: RsvdSwitch1=RsvdSwitch1_Bit31-0;Run the following command to disable this solution:SET UDPUCFGDATA: RsvdSwitch1=RsvdSwitch1_Bit31-1;

If RACH_SYNC_CHK_EFFECT_MODE_SWITCH and the preceding new switch are both turned on, the RACH keepalive function is enabled. RACH_SYNC_CHK_EFFECT_MODE_SWITCH can be turned on only when the NodeB supports the RACH keepalive function. If the RNC receives a synchronization frame from the NodeB, the RNC enables the RACH keepalive function.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementRsvdSwitch1_Bit31 in the SET UDPUCFGDATA command is used. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated Operations3. Run the following command to enable this solution:SET UDPUCFGDATA: RsvdSwitch1=RsvdSwitch1_Bit31-0;Trouble Ticket NumberDTS: DTS2014111204865Feature IDNone3.2.2.16 Optimizing Reporting of EVT-22915 SCTP Link Destination IP ChangeoverDescriptionIf an SCTP link is configured with two local IP addresses and one peer IP address and intermediate transmission becomes faulty, ALM-21541 SCTP Link Fault and EVT-22915 SCTP Link Destination IP Changeover are reported simultaneously. As a result, operation and maintenance (O&M) are affected. This feature optimizes the mechanism for reporting EVT-22915 SCTP Link Destination IP Changeover to reduce the impact of EVT-22915 on other key events.ImplementationSW18 of Reserved Switch Parameter1 in the SET TNRSVDPARA command controls whether to report EVT-22915 SCTP Link Destination IP Changeover when an SCTP link is configured with two local IP addresses and one peer IP address. 0: EVT-22915 SCTP Link Destination IP Changeover is reported. 1: EVT-22915 SCTP Link Destination IP Changeover is not reported.By default, this feature is disabled (default value: 0) for both new networks and upgrade scenarios.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementEnabled SW18 of Reserved Switch Parameter1 in the SET TNRSVDPARA command. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsTo enable this feature, run the following command:SET TNRSVDPARA: RSVDSW1=SW18-1;Trouble Ticket NumberDTS: DTS2014102701712Feature IDNone3.2.2.17 Enhancement of Active/Standby Status Consistency of Interface Boards and Ports Before and After an UpgradeDescriptionBy default, the Check active/standby status consistency option is not selected. Therefore, users need to manually select this option. If it is not manually selected, transmission interruption triggered by a board switchover after an upgrade may occur. With this feature, the Check active/standby status consistency option in the Input Step 3 window of the upgrade tool is selected by default. This feature reduces risks of transmission interruption triggered by a board switchover after an upgrade.ImplementationIn the Input Step 3 window of the upgrade tool, the Check active/standby status consistency option is selected by default, as shown in the following figure.

Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014092004984Feature IDNone3.2.2.18 Optimizing Information Displayed at the Start of an Upgrade Phase on the Upgrade ToolDescriptionWhen the pre-upgrade is complete on the upgrade tool, the Next button and the message "Are you sure ?" displayed on the upgrade tool are the same as those in other steps. By viewing this information, users are likely to perform an upgrade caused by misoperation. This feature is introduced to optimize the information displayed in this scenario.ImplementationWhen the pre-upgrade is complete, the Execute Upgrade button is displayed instead of the Next button. In addition, the message "You will step into upgrade execution, and you cannot cancel during execution. Are you sure ?" is displayed instead of the message "Are you sure ?", as shown in the following figure.

Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014102107316Feature IDNone3.2.2.19 Adding the Prompt Message for Configuration Data Change During a Rollback on the Upgrade ToolDescriptionWhen users perform a version rollback using the upgrade tool after ever modifying configuration data, this feature enables the upgrade tool to prompt users that configuration data is ever changed and the configuration data may be lost after the rollback.ImplementationA rollback pre-check item "Whether the system configuration data is ever changed after an upgrade" is added to the upgrade tool. If system configuration data is ever modified after an upgrade, the check result of this item is "Warning" and prompts users to perform relevant operations.If system configuration data remains unchanged after an upgrade, the item passes the check.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014110701204Feature IDNone3.2.2.20 Changing Backup IP Address on the U_creator ToolDescriptionWhen the OMU OS is switched using the U_creator tool, this feature allows users to directly change the backup IP address on the tool interface instead of changing it by following steps in OMU Administration Guide, thereby improving tool usability.ImplementationIf Operate Type is set to Switch on the U_creator tool, the backup IP address input box can be edited. If the backup IP address is in the same network segment as other IP addresses, users can directly change the backup IP address on the U_creator tool interface. After the OMU OS is switched using the U_creator tool, the OMU backup IP address is the same as that configured on the U_creator tool.

If Operating System Type is set to DopraLinux, the (1)Backup network IP and (2)Backup network IP input boxes can be edited, as shown in the following figure.

If Operating System Type is set to EulerLinux, the Backup network IP input box can be edited, as shown in the following figure.

Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014070814183Feature IDNone3.2.2.21 OMU Capacity EvaluationDescriptionThis feature enables the OMU to record its capacity monitoring log. This log is used to evaluate the OMU performance.ImplementationThe OMU Capacity Monitoring Log Switch parameter in the SET OMUPARA command controls whether to enable this feature. By default, this feature is disabled (default value: OFF) for new networks, and the status of this feature is inherited after upgrades.When OMU Capacity Monitoring Log Switch is set to ON(On), the OMU records its capacity monitoring logs, and the name of the log file is capacity.csv. The log file is compressed and backed up each time its size reaches 20 MB. A maximum of ten backup log files are saved.The OMU capacity is recorded every other 2s in the capacity monitoring log. The following table describes the monitoring items.Monitoring ItemDescription

Cpu UtilCPU usage

Load averageNumber of tasks to be processed by the CPU

Free MemoryAvailable memory

Swap UsageNumber of memory pages using the swap partition

IO UtilI/O usage

AwaitI/O waiting queue length in the Windows operating system;I/O waiting delay in the Linux operating system

IOPSNumber of read and write operations every second

Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementAdded the OMU Capacity Monitoring Log Switch parameter to the SET OMUPARA command. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated Operations To enable this feature, run the following command:SET OMUPARA:CAPMONLOGSW=ON; To disable this feature, run the following command:SET OMUPARA:CAPMONLOGSW=OFF;Trouble Ticket NumberDTS: DTS2014112104386Feature IDNone3.2.2.22 Support for Querying Manually Cleared AlarmsDescriptionThis feature enables users to query manually cleared alarms and provides reference for users to handle currently reported alarms.Implementation The LST MANRESALMLOG command is added and used to query manually cleared alarms. The specifications for manually cleared alarms are as follows:A maximum of 2000 manually cleared alarms can be saved. If the number of manually cleared alarms exceeds 2000, only the latest 1600 alarms are saved and other alarms are deleted.Manually cleared alarms can be saved for 365 days. If the saving time of an alarm exceeds 365 days, this alarm will be deleted.The base station controller checks whether the recorded alarms exceed the specifications on a daily basis. The deleted alarms are backed up and generated as a compressed file and saved in ftp/manresalmlog. Users can run the COL LOG: LOGTYPE=HISTORY_ALARM-1; command to collect the manually cleared alarms.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementAdded the LST MANRESALMLOG command. Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS:DTS2014071408266Feature IDNone3.2.2.23 Changing the Default Value of Automatic Synchronization SwitchDescriptionBefore this feature is introduced, the automatic synchronization switch is turned off (default value: OFF) for both new networks and upgrade scenarios by default and customers need to manually enable this function by running the SET SYNSWITCH command.With this feature, the automatic synchronization switch is turned on (default value: ON) for both new networks and upgrade scenarios by default.If the scheduled task triggered by running the ACT CRC command detects that the OMU configuration data is inconsistent with the SCU/XPU configuration data and automatic synchronization is enabled, the system will synchronize the configuration data from the OMU to the SCU/XPU board. In this way, some data inconsistency problems can be resolved.ImplementationBy default, the automatic synchronization switch is turned on (default value: ON) for both new networks and upgrade scenarios.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014121303252Feature IDNone3.2.2.24 Enhanced Support for Editing of Batch Configuration Parameters on the Web LMTDescriptionThis feature allows users to edit the following batch configuration parameters on the Web LMT to improve O&M efficiency: Capability of CN Node[k] in the CNNODE MO Feature Supporting Mode of PS Domain, Length of PS NRI in bits, and NullNRI VALUE in the OPERATORCFGPARA MOImplementationThis feature allows users to edit the preceding parameters when using the batch configuration function on the Web LMT. After importing configuration scripts, users can click the Edit button to edit the preceding parameters.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014111706009Feature IDNone3.2.2.25 Fan Box Noise Rectification at a High Fan SpeedDescriptionWhen the fan speed is high, the speed of fans in few fan boxes is unstable without affecting services. This feature optimizes the fan speed precision controlled by software to prevent unstable noise and fan speed in the preceding scenario.ImplementationThe fan speed adjustment precision is optimized. When the fan speed is high, the step in which the fan speed is adjusted is decreased. This optimization helps ensure that the fan speed is adjusted stably.Impact on Capacity and PerformanceNoneImpact on NEsNoneImpact on HardwareNoneImpact on Inter-NE InterfacesNoneImpact on Operation and Maintenance Impact on license managementNone Impact on configuration managementNone Impact on performance managementNone Impact on fault managementNoneImpact on Other FeaturesNoneRelated OperationsNoneTrouble Ticket NumberDTS: DTS2014121400421Feature IDNone3.2.3 Deleted FeaturesNone3.3 Resolved Issues3.3.1 Critical3.3.1.26 The call drop rate increases when the satellite card cannot properly trace GPS satellite signals.Trouble Ticket NumberiCare: 3741437DTS: DTS2014111110358

DescriptionCondition: The satellite card cannot properly trace GPS satellite signals.Symptom: The call drop rate increases.Impact: Some KPIs deteriorate.

SeverityCritical

Root CauseWhen the number of messages sent by the satellite card increases because of external GPS signal deterioration, communication congestion will occur. In this situation, the time information in the GCK board is frequently adjusted because time-related messages sent by the satellite card cannot be processed in a timely manner. As a result, the ongoing call is interrupted.

SolutionNow, the time information in the GCK board is not adjusted based on the messages sent by the satellite card.

Solution ImpactThe call drop rate decreases and service setup success rate increases in the preceding scenario.

Test CaseCASE_Commercial_PR_Regression_R016C00SPC650_501

3.3.2 Major3.3.2.27 The value of Number of Received CREF in ALM-21522 Low SCCP Setup Success Rate is incorrect.Trouble Ticket NumberiCare: 3146707DTS: DTS2014102302913

DescriptionCondition: After sending a CR packet to the peer end, the SCCP module of the base station controller receives another packet instead of a CC or CREF packet from the peer end. When this happens, service setup fails and ALM-21522 Low SCCP Setup Success Rate is reported.Symptom: The value of Number of Receiv

c03_bsc6900 umts v900r016c00spc650 release notes

Documents