Beruflich Dokumente
Kultur Dokumente
Issue Draft A
Date 2016-06-23
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the 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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 3
2.1 Background.....................................................................................................................................................................3
2.2 Introduction.................................................................................................................................................................... 3
2.3 Benefits........................................................................................................................................................................... 3
3 Technical Description...................................................................................................................4
3.1 Principles........................................................................................................................................................................ 4
3.2 Selection of Virtual CPC Users...................................................................................................................................... 5
3.3 Collaboration Between Virtual CPC and Uplink Control Channel OLPC..................................................................... 5
4 Related features............................................................................................................................. 8
5 Network Impact........................................................................................................................... 10
6 Engineering Guidelines............................................................................................................. 11
6.1 When to Use Virtual CPC.............................................................................................................................................11
6.2 Required Information....................................................................................................................................................11
6.3 Deployment.................................................................................................................................................................. 12
6.3.1 Requirements............................................................................................................................................................. 12
6.3.2 Activation.................................................................................................................................................................. 13
6.3.2.1 Using MML Commands......................................................................................................................................... 13
6.3.2.2 MML Command Examples.................................................................................................................................... 13
6.3.2.3 Using the CME....................................................................................................................................................... 14
6.3.3 Activation Observation..............................................................................................................................................14
6.3.4 Deactivation...............................................................................................................................................................14
6.3.4.1 Using MML Commands......................................................................................................................................... 14
6.3.4.2 MML Command Examples.................................................................................................................................... 14
6.3.4.3 Using the CME....................................................................................................................................................... 15
6.4 Performance Monitoring...............................................................................................................................................15
6.5 Parameter Optimization................................................................................................................................................ 16
6.6 Troubleshooting............................................................................................................................................................ 16
7 Parameters..................................................................................................................................... 17
8 Counters........................................................................................................................................ 22
9 Glossary......................................................................................................................................... 28
10 Reference Documents............................................................................................................... 29
1.1 Scope
This document describes the WRFD-171207 Virtual CPC feature, including its technical
principles, related features, network impact, and engineering guidelines.
NE Type NE Model
Micro BTS3911E
WRFD-17 Virtual NA NA Y Y Y
1207 CPC
NOTE
Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE is
not involved, that is, a feature does not require the support of the NE.
2 Overview
2.1 Background
As the smartphone penetration rate and data transmission requirements increase, there is an
increase in the number of HSUPA users on live networks. This increase causes the proportion
of power consumption on uplink control channels to increase as well, resulting in insufficient
uplink capacity.
To increase uplink capacity, Huawei introduced the continuous packet connectivity (CPC)
feature in RAN11.0. However, there is a lack of CPC-capable UEs on live networks. The CPC
feature cannot significantly reduce power consumption of uplink control channels. Huawei
has introduced the Virtual CPC feature in RAN17.1 to resolve this issue. This feature reduces
the transmit power of non-CPC terminals when there is no data transmission, further reducing
the power consumption of control channels on the air interface and improving uplink capacity.
NOTE
For details about the CPC feature, see CPC Feature Parameter Description.
2.2 Introduction
The Turbo IC Phase 2 feature introduces single hybrid automatic repeat request (HARQ)
technology. For an HSUPA user with a 2 ms transmission time interval (TTI), single HARQ
technology activates only one process for uplink data transmission and uses inactive processes
for transmitting control channel data.
The Virtual CPC feature is intended for HSUPA users that use single HARQ technology. With
this feature, the NodeB differentiates active and inactive processes to perform power control,
decreasing the power of uplink control channels for inactive processes, and increasing uplink
capacity.
2.3 Benefits
This feature can increase uplink capacity by 5%15% in scenarios where uplink power
resources are insufficient and there are a large number of HSUPA 2 ms TTI users.
3 Technical Description
3.1 Principles
The Virtual CPC feature takes effect only for HSUPA users who use the single HARQ
technology (single-HARQ HSUPA users for short). The Turbo IC Phase 2 feature triggers
HSUPA users with 2 ms TTI to enter into the single HARQ scheduling state when uplink
power resources are insufficient.
Active processes of single-HARQ HSUPA users are controlled by the network side. The
NodeB can automatically identify active and inactive processes of HSUPA users and calculate
SIRTarget values by using different outer loop power control (OLPC) policies.
NOTE
The SIRTarget values calculated through OLPC are used to control inner loop power control. Based on
the comparison result of SIREst (the measured SIR value) and SIRTarget (the target SIR value), inner
loop power control uses the TPC command to rapidly adjust UE transmit power so that SIREst values
converge at the SIRTarget. For details about power control, see Power Control Feature Parameter
Description.
The solid line shown in Figure 3-1 indicates the SIRTarget when the Virtual CPC feature is
enabled.
l For active processes, inner loop power control is performed using the SIRtarget
calculated through OLPC on the RNC side. This SIRtarget is recorded as
DCHSIRTarget.
l For inactive processes, the SIRTarget is calculated based on signal quality on control
channels. This SIRTarget is recorded as DCHVCPCSIRTarget. Generally,
DCHVCPCSIRTarget is lower than DCHSIRTarget.
To ensure that the SIR of an active process can restore the SIRTarget calculated through
OLPC, the NodeB will restore the SIR to DCHSIRTNarget one or two TTIs before the active
process arrives.
NOTE
Control channels refer to the Dedicated Physical Control Channel (DPCCH) and High Speed Dedicated
Physical Control Channel (HS-DPCCH).
The dotted line shown in Figure 3-1 indicates the SIRTarget when the Virtual CPC feature is
disabled. When the Virtual CPC feature is disabled, DCHSIRTarget is used for both active and
inactive processes.
Figure 3-1 OLPC performed on single-HARQ HSUPA users with 2 ms TTIs after the Virtual
CPC feature is introduced
l The user is an HSUPA user with 2 ms TTI and uses the single HARQ technology.
l Downlink services of the user are carried on HSDPA channels, the CQI feedback period
(specified by the CQIFbCk(BSC6900,BSC6910) parameter) is less than or equal to 8
ms, and the CQI repetition factor (specified by the CQIReF(BSC6900,BSC6910)
parameter) is 1.
l SRB over HSUPA is applied to the user.
l Services of the user are carried by a WBBPf, UBBPd, UBBPe, or UBBPei.
l The user is not a special user.
For the special user definition, see Impacted Features.
l The user is not configured with non-scheduled services.
Virtual CPC cannot be enabled on HSUPA users configured with non-scheduled services
to ensure the performance of transmitting non-scheduled data in deactivated processes.
Set the scheduled or non-scheduled transmission mode of services using the parameters
UlIMSTransModeOnHsupa(BSC6900,BSC6910),
UlSRBTransModeOnHsupa(BSC6900,BSC6910),
UlPttTransModeOnHsupa(BSC6900,BSC6910), and
UlStrTransModeOnHsupa(BSC6900,BSC6910). When the parameter is set to
SCHEDULED, the corresponding service is transmitted in scheduled mode. When the
parameter is set to NON-SCHEDULED, the corresponding service is transmitted in
non-scheduled mode.
When the Uplink Control Channel OLPC feature is enabled, HSUPA users can be in the CCH
OLPC state or DCH OLPC state.
NOTE
For descriptions of the CCH OLPC and DCH OLPC states, see Uplink Control Channel OLPC Feature
Parameter Description.
Figure 3-2 shows state transitions after the Virtual CPC and Uplink Control Channel OLPC
features are enabled.
Figure 3-2 State transitions after the Virtual CPC and Uplink Control Channel OLPC features
are enabled
Table 3-1 describes the conditions of state transitions shown in Figure 3-2.
State transition 1 The HARQ state of the user is changed from full HARQ to single
HARQ. Full HARQ indicates that all processes of the user are active.
Table 3-2 describes the SIRTarget adjustment mechanism for different states.
4 Related features
Prerequisite Features
Feature ID Feature Name Description
Impacted Features
Feature ID Feature Name Description
WRFD-150250 3C-HSDPA
WRFD-010610 Improvement of
20 User Experience in
Low Traffic Service
WRFD-171209 Coverage
Improvement for
HSUPA 2ms TTI
UEs
5 Network Impact
System Capacity
This feature can increase uplink capacity by 5%15% in scenarios in which there are a large
number of HSUPA 2 ms TTI users and uplink power resources are insufficient. If a large
number of users access a cell, this feature can increase the number of radio links by 5%-15%.
Network Performance
No impact.
6 Engineering Guidelines
- VS.HSUPA.UE.Mean.CAT6(BSC6900,BSC6910)
- VS.HSUPA.UE.Mean.CAT7(BSC6900,BSC6910)
- VS.HSUPA.UE.Mean.CAT8(BSC6900,BSC6910)
- VS.HSUPA.UE.Mean.CAT9(BSC6900,BSC6910)
Uplink cell load:
Cell RTWP measured on the RNC side: VS.MeanRTWP(BSC6900,BSC6910)
Cell average RoT measured on the NodeB side: VS.HSUPA.LoadOutput.0
through VS.HSUPA.LoadOutput.25
l Collect information about the following counters about HSUPA data volume and
throughput to evaluate the capacity gains:
VS.HSUPA.MeanChThroughput.TotalBytes(BSC6900,BSC6910)
VS.HSUPA.MeanChThroughput(BSC6900,BSC6910)
6.3 Deployment
6.3.1 Requirements
Other Features
For details, see 4 Related features.
Hardware
BTS3911Es support this feature. 3900 series base stations and LampSite base stations support
this feature when meeting the following requirements:
l 3900 series base stations are configured with the WBBPf, UBBPd, UBBPe, or UBBPei
board.
l LampSite base stations are configured with the WBBPf, UBBPd, UBBPe, or UBBPei
board.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the License Allocation for Multiple Operators
parameter.
Method 2: some license control items, such as UL CE Num, can be allocated through both the
common group and private groups. In this case, the licensed values specified by the private
group are preferentially used, and the licensed value specified by the common group is used
on a first-come, first-served basis. For the NodeB license allocation among multiple operators,
see License Management Feature Parameter Description.
Others
This feature requires that the PwrCtrlAlg(BSC6900,BSC6910) parameter in the inner loop
power control algorithm on the RNC side be set to ALGORITHM1. Before enabling this
feature, set PwrCtrlAlg(BSC6900,BSC6910) to ALGORITHM1. Do not enable this feature
if this parameter has to be set to another value.
Before enabling this feature, check whether the CQIReF(BSC6900,BSC6910) parameter is
set to 1 on the RNC side. This feature cannot take effect if the value of this parameter is not 1.
6.3.2 Activation
----End
When configuring the Virtual CPC feature on the CME, perform a single configuration first, and then
perform a batch modification if required. Configure the parameters of a single object before a batch
modification. Perform a batch modification before logging out of the parameter setting interface.
Set the parameter described in Table 6-2 on the CME. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard.
For instructions on how to perform a batch modification through the CME batch modification
center, press F1 while running the wizard to obtain online help.
----End
6.3.4 Deactivation
----End
To modify objects in batches, click on the CME to start the batch modification wizard.
For instructions on how to perform a batch modification through the CME batch modification
center, press F1 while running the wizard to obtain online help.
----End
NOTE
6.6 Troubleshooting
After this feature is enabled in a cell, if the license controlling this feature is not activated or
the baseband board serving the cell does not support this feature, the local cell will not
support this feature and an ALM-28206 Local Cell Capability Decline alarm is reported.
7 Parameters
VIRTU BTS390 ADD WRFD- Virtual Meaning: Indicates whether the virtual CPC feature is
ALCPC 0, ULOCE 171207 CPC supported by the cell.
BTS390 LL GUI Value Range: FALSE(FALSE), TRUE(TRUE)
0 MOD
WCDM Unit: None
ULOCE
A LL Actual Value Range: FALSE, TRUE
CQIFbC BSC690 SET WRFD- HSDPA Meaning: Duration of a CQI feedback cycle when the
k 0 UHSDP 010610 Introduc UE is in the single-RLS state. In each CQI feedback
CCH tion cycle, the UE retransmits CQI for N times repeatedly,
Package where N represents the value of CQI repetition factor
"CQIRef". The value 0 indicates no CQI information
sent from the UE. For details about this parameter, see
3GPP TS 25.214.
GUI Value Range: D0, D2, D4, D8, D10, D20, D40,
D80, D160
Unit: ms
Actual Value Range: 0, 2, 4, 8, 10, 20, 40, 80, 160
Default Value: D2
CQIFbC BSC691 SET WRFD- HSDPA Meaning: Duration of a CQI feedback cycle when the
k 0 UHSDP 010610 Introduc UE is in the single-RLS state. In each CQI feedback
CCH tion cycle, the UE retransmits CQI for N times repeatedly,
Package where N represents the value of CQI repetition factor
"CQIRef". The value 0 indicates no CQI information
sent from the UE. For details about this parameter, see
3GPP TS 25.214.
GUI Value Range: D0, D2, D4, D8, D10, D20, D40,
D80, D160
Unit: ms
Actual Value Range: 0, 2, 4, 8, 10, 20, 40, 80, 160
Default Value: D2
CQIReF BSC690 SET WRFD- HSDPA Meaning: Number of CQI retransmissions when the
0 UHSDP 010610 Introduc UE is in the single-RLS state. Assume that the CQI
CCH tion repetition factor is N. The receiver performs soft
Package combining on N results before decoding. For details
about this parameter, see 3GPP TS 25.214.
GUI Value Range: 1~4
Unit: None
Actual Value Range: 1~4
Default Value: 1
CQIReF BSC691 SET WRFD- HSDPA Meaning: Number of CQI retransmissions when the
0 UHSDP 010610 Introduc UE is in the single-RLS state. Assume that the CQI
CCH tion repetition factor is N. The receiver performs soft
Package combining on N results before decoding. For details
about this parameter, see 3GPP TS 25.214.
GUI Value Range: 1~4
Unit: None
Actual Value Range: 1~4
Default Value: 1
UlIMST BSC690 SET WRFD- IMS Meaning: E-DCH data transfer mode of IMS signaling
ransMod 0 UFRC 010618 Signalin services. It is valid only when IMS signaling services
eOnHsu g over are mapped onto the E-DCH.
pa HSPA GUI Value Range: SCHEDULED, NON-
SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: SCHEDULED
UlIMST BSC691 SET WRFD- IMS Meaning: E-DCH data transfer mode of IMS signaling
ransMod 0 UFRC 010618 Signalin services. It is valid only when IMS signaling services
eOnHsu g over are mapped onto the E-DCH.
pa HSPA GUI Value Range: SCHEDULED, NON-
SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: SCHEDULED
UlSRBT BSC690 SET WRFD- SRB Meaning: Data transmission mode for the 2 ms TTI E-
ransMod 0 UFRC 010636 over DCH carrying SRBs. When this parameter is set to
eOnHsu HSUPA SCHEDULED, the 2 ms TTI E-DCH carrying SRBs
pa uses the scheduling mode. When this parameter is set
to NON-SCHEDULED, the 2 ms TTI E-DCH
carrying SRBs uses the non-scheduling mode.
GUI Value Range: SCHEDULED, NON-
SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: SCHEDULED
UlSRBT BSC691 SET WRFD- SRB Meaning: Data transmission mode for the 2 ms TTI E-
ransMod 0 UFRC 010636 over DCH carrying SRBs. When this parameter is set to
eOnHsu HSUPA SCHEDULED, the 2 ms TTI E-DCH carrying SRBs
pa uses the scheduling mode. When this parameter is set
to NON-SCHEDULED, the 2 ms TTI E-DCH
carrying SRBs uses the non-scheduling mode.
GUI Value Range: SCHEDULED, NON-
SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: SCHEDULED
UlPttTra BSC690 SET WRFD- Streami Meaning: E-DCH data transfer mode of PTT services.
nsMode 0 UFRC 010632 ng It is valid only when PTT services are mapped onto
OnHsup WRFD- Traffic the E-DCH.
a 020134 Class on GUI Value Range: SCHEDULED, NON-
HSUPA SCHEDULED
Push to Unit: None
Talk
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: NON-SCHEDULED
UlPttTra BSC691 SET WRFD- Streami Meaning: E-DCH data transfer mode of PTT services.
nsMode 0 UFRC 010632 ng It is valid only when PTT services are mapped onto
OnHsup WRFD- Traffic the E-DCH.
a 020134 Class on GUI Value Range: SCHEDULED, NON-
HSUPA SCHEDULED
Push to Unit: None
Talk
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: NON-SCHEDULED
UlStrTra BSC690 SET WRFD- Streami Meaning: E-DCH data transfer mode of streaming
nsMode 0 UFRC 010632 ng services. It is valid only when streaming services are
OnHsup Traffic mapped onto the E-DCH.
a Class on GUI Value Range: SCHEDULED, NON-
HSUPA SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: NON-SCHEDULED
UlStrTra BSC691 SET WRFD- Streami Meaning: E-DCH data transfer mode of streaming
nsMode 0 UFRC 010632 ng services. It is valid only when streaming services are
OnHsup Traffic mapped onto the E-DCH.
a Class on GUI Value Range: SCHEDULED, NON-
HSUPA SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: NON-SCHEDULED
PwrCtrl BSC690 SET WRFD- Inner Meaning: This parameter specifies how the UE
Alg 0 UFRC 020504 Loop interprets the received Transmit Power Control (TPC)
Power commands, that is, selecting a UL inner-loop power
Control control algorithm. Two different algorithms (denoted
ALGORITHM1 and ALGORITHM2) are available,
related to this parameter. When the parameter is set to
ALGORITHM1, the UE adjusts the uplink transmit
power once every timeslot. When the parameter is set
to ALGORITHM2, the UE adjusts the uplink transmit
power once every five timeslots. For details about this
parameter, see 3GPP TS 25.214.
GUI Value Range: ALGORITHM1, ALGORITHM2
Unit: None
Actual Value Range: ALGORITHM1,
ALGORITHM2
Default Value: ALGORITHM1
PwrCtrl BSC691 SET WRFD- Inner Meaning: This parameter specifies how the UE
Alg 0 UFRC 020504 Loop interprets the received Transmit Power Control (TPC)
Power commands, that is, selecting a UL inner-loop power
Control control algorithm. Two different algorithms (denoted
ALGORITHM1 and ALGORITHM2) are available,
related to this parameter. When the parameter is set to
ALGORITHM1, the UE adjusts the uplink transmit
power once every timeslot. When the parameter is set
to ALGORITHM2, the UE adjusts the uplink transmit
power once every five timeslots. For details about this
parameter, see 3GPP TS 25.214.
GUI Value Range: ALGORITHM1, ALGORITHM2
Unit: None
Actual Value Range: ALGORITHM1,
ALGORITHM2
Default Value: ALGORITHM1
8 Counters
DC-HSUPA
Adaptive
Configuration
of Traffic
Channel Power
offset for
HSUPA
Flexible Power
Control for
Uplink Low
Data Rate
Transmission
Adaptive
RACH
9 Glossary
10 Reference Documents