View Full Version : PCpich Power in UMTS
silverlemone
2013-10-17, 04:39 PM
Does anyone know ? if the gap between min pcpich power and pcpich power and gap between max pcpich and pcpich power is not equal to each other
Is it going to effect any problem in UMTS network? Is it about Power control or something?
For example
Max : 343
pcpich : 330
Min :325
ltecity
2013-10-18, 02:53 AM
Which vendor are you asking?
Can explain more for quick understanding?
silverlemone
2013-10-19, 03:09 AM
It's Huawei
It's all about m2000 when im changing pcpich parmeter
the cpichpwr must be in the range between maxcpichpwr and mincpichpwr
So i'm just wondering what if the lower and upper gap is not equal. Does it cause any effect?
ltecity
2013-10-19, 03:34 AM
I think its range of CPICH power which you can define in your system.
Beyond that you cant define.
bawbag11
2013-10-19, 03:56 AM
AFAIK:
MaxPCPICHPower & MinPCPICHPower are only of use when you use LDC/R algo. In my network the setting are left as default as we dont use the PCPICH for load control:
List PCPICH
-----------
Cell ID Cell Name PCPICH ID PCPICH Transmit Power Max Transmit Power of PCPICH Min Transmit Power of PCPICH PCPICH TX Power in Small DSS Coverage
63283 M1 2 330 500 0 330
The Hedex blurb tells you this:
MaxPCPICHPower - Max Transmit Power of PCPICH
Meaning: Maximum TX power of the PCPICH in a cell. This parameter should be set based on the actual system environment such as cell coverage (radius) and geographical environment, and the cell total power. When the ratio of soft handover areas keeps the same, the downlink coverage cannot be promoted by the increase of PCPICH power.
GUI Value Range: -100~500
Unit: 0.1dBm
Actual Value Range: -10~50
MML Default Value: None
Recommended Value: 346
Parameter Relationship: None
Service Interrupted After Modification: No (And no impact on the UE in idle mode)
Impact on Network Performance: None
MinPCPICHPower - Min Transmit Power of PCPICH
Meaning: Minimum TX power of the PCPICH in a cell. This parameter should be set based on the actual system environment such as cell coverage (radius) and geographical environment. Ensure that MinPCPICHPower is set under the condition of a proper proportion of soft handover area, or under the condition that no coverage hole exists.
GUI Value Range: -100~500
Unit: 0.1dBm
Actual Value Range: -10~50
MML Default Value: None
Recommended Value: 313
Parameter Relationship: The value of this parameter must satisfy the following relationship: Min Transmit Power of PCPICH <= Max Transmit Power of PCPICH.
Service Interrupted After Modification: No (And no impact on the UE in idle mode)
Impact on Network Performance: If MinPCPICHPower is excessively small, the cell coverage is affected.
The defaults in hedex are sane so if in doubt use these and check LDC/R actions in your RNC.
BR
rfsupp
2013-10-22, 03:08 AM
Guys,
The Min and Max CPICH will take effect ONLY:
- if the THE LDB algorithm its turned on
- power congestion its happening
But the difference gap between Max/Min wont cause poor performance.
[QUOTE=rfsupp;213858]Guys,
Thanks for the info. I would like to ask how to modify the PCPICH transmit power. MOD UPCPICHPWR only allows you to modify the min and max power (Huawei RAN14)
PCPICH Transmit Power=360;
Max Transmit Power of PCPICH=378;
Min Transmit Power of PCPICH=342
PCPICH TX Power in Small DSS Coverage=330
ravi_4386
2014-07-20, 07:25 PM
in ZTE it is like 36...333...30...27 ....
erastus
2014-07-21, 03:58 AM
You modify the max and min tx power on the node b level.
peanut
2014-11-23, 12:44 AM
The needed command is
MOD UCELL
Here is an example: MOD UCELL: CellId=2450, PCPICHPower=360; // PCPICH POWER is NOW SET to 36dBm
But ensure that the new value is betwwen the Max & Min PCPICH TX Power
Regards,
[QUOTE=rfsupp;213858]Guys,
Thanks for the info. I would like to ask how to modify the PCPICH transmit power. MOD UPCPICHPWR only allows you to modify the min and max power (Huawei RAN14)
PCPICH Transmit Power=360;
Max Transmit Power of PCPICH=378;
Min Transmit Power of PCPICH=342
PCPICH TX Power in Small DSS Coverage=330
vBulletin® v4.2.5, Copyright ©2000-2024, Jelsoft Enterprises Ltd.