Академический Документы
Профессиональный Документы
Культура Документы
Version: V4.11.20
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
1-1
1-2
Hardware Requirement
Hardware requirement is shown in Table 2-1.
NE Requirement
RNC None
NodeB None
Software Requirement
Software requirement is shown in Table 2-2.
2-1
Topology
Topology is shown in Figure 2-1.
2-2
MSC/MGW - ZTE
N/A
HLR ZTE
UE1 subscribes background service, MBR= UL 2Mbps/ DL 2Mbps
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_backgro
und
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 2048000
RNC
l HSPA Support Method: Support HSUPA, HSDPA and DCH
Path: View > Configuration Management > Managed Element > UMTS Logical
Function Configuration > UTRAN Cell > UTRAN Cell xxx > HSPA Support Method
l
3-1
3-2
So according to the information which listed above, the "power control related to
service and diversity mode" is "txDivMod=0,srvType=180,UsrvPcProfile=0" in our
test, it should coincide with real environments.
3-3
Path: View > Configuration Management > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function
> Power Control Profile Related to Service > Power Control Related
to Service > Power Control Related to Service and Diversity Mode >
txDivMod=X,srvType=X,USrvPcProfile=X > Uplink Initial SIR Target / Maximum
Uplink SIR Target / Minimum Uplink SIR Target
l Basic Priority
3-4
3-5
Path: View > Configuration Management > Managed Element > UMTS Logical
Function Configuration > Service Configuration > Service Function > Power
Control Profile Related to Service > Power Control Related to Service > Power
Control Related to Service and Diversity Mode > srvType=X,USrvPcProfile=X >
UNHR Threshold to Adjust SIR Target Upward (10ms E-TTI) / NHR Threshold
to Adjust SIR Target Downward(10ms E-TTI) / Threshold of Sample Number to
Adjust SIR Target Downward (10ms E-TTI) / Threshold of Sample Number to
Adjust SIR Target Upward (10ms E-TTI) / Threshold of HARQ Failure Indication
Number to Adjust SIR Target Upward (10ms E-TTI)
NodeB
N/A
3-6
2. Adjust the signal strength to trigger the outer loop power control. From the internal
message "ptOlpcParaInfo", we can find the related information of outer loop power
control. The first figure as follows is about the information of SIRtarget, and the second
figure is about the threshold used to trigger outer loop power control.
4-1
3. Use the FPX tool(which can be found in folder "tools" of LMT tool) to analysis the IUB
packets which captured by wireshark. We can see the change of SIRTarget because
of outer loop power control.
4-2
4. From the EPMS of NODE-B, the adjustment of SIRtarget can also be observed.
4-3
4-4
5-1