Professional Documents
Culture Documents
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 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 3
2.3 Architecture.................................................................................................................................................................... 3
3 Technical Description...................................................................................................................5
3.1 Technical Principle......................................................................................................................................................... 5
3.2 Activation and Deactivation........................................................................................................................................... 7
3.3 Flow Control...................................................................................................................................................................9
4 Related Features...........................................................................................................................11
5 Network Impact........................................................................................................................... 12
6 Engineering Guidelines............................................................................................................. 13
6.1 When to Use Uplink Data Acceleration....................................................................................................................... 13
6.2 Required Information................................................................................................................................................... 13
6.3 Deployment.................................................................................................................................................................. 14
6.3.1 Requirements............................................................................................................................................................. 14
6.3.2 Data Preparation and Feature Activation...................................................................................................................14
6.3.2.1 Data Preparation..................................................................................................................................................... 15
6.3.2.2 Using MML Commands......................................................................................................................................... 15
6.3.2.3 MML Command Examples.................................................................................................................................... 15
6.3.2.4 Using the CME....................................................................................................................................................... 16
6.3.3 Activation Observation..............................................................................................................................................16
6.3.4 Deactivation...............................................................................................................................................................17
6.3.4.1 Using MML Commands......................................................................................................................................... 17
6.3.4.2 MML Command Examples.................................................................................................................................... 17
6.3.4.3 Using the CME....................................................................................................................................................... 17
6.4 Performance Monitoring...............................................................................................................................................17
7 Parameters..................................................................................................................................... 19
8 Counters........................................................................................................................................ 43
9 Glossary......................................................................................................................................... 47
10 Reference Documents............................................................................................................... 48
1.1 Scope
This document describes WRFD-181202 Uplink Data Acceleration, including its technical
principles, related features, network impact, and engineering guidelines.
NE Type Model
Micro BTS3911E
RAN18.1 01 (2016-02-29)
This document is created for RAN18.1.
NOTE
N/A indicates that an NE is not involved, that is, a feature does not require the support of the NE.
The feature described in this document is implemented in the same way on macro, micro, and
LampSite base stations.
2 Overview
2.1 Introduction
For web browsing or video streaming services, a large bulk of uplink PS traffic is represented
in the form of HTTP requests and TCP-ACK messages.These contain extensive amounts of
duplicate data. With Uplink Data Acceleration (UDA), uplink PS data can be compressed
before being sent. This downsizes the data volume, decreasing uplink interference and loads.
This feature can further shorten the uplink HTTP request delay for cells experiencing
congestion. This decreases the delay of web browsing or video streaming services for better
experience.
This feature requires support from the RNC and the UE. The UE compresses uplink PS data.
The RNC decompresses data received from the UE and sends the decompressed data to the
packet core network (CN).
2.2 Benefits
This feature provides the following benefits:
l Reduces uplink PS data for UDA-capable UEs, decreasing uplink interference and loads.
This feature provides a high uplink compression gain for web browsing or video
streaming services. Uplink PS data can be reduced by 40% to 70%.
This feature provides a low uplink compression gain for encrypted data services or
compressed data transfer for pictures, videos, and voice services. Uplink PS data
can be reduced by 5% to 20%.
l Shortens the web browsing delay by at least 20% for UDA-capable UEs in the event of
uplink congestion (with an uplink load of above 75%).
2.3 Architecture
The UE compresses the PS data and sends it to the RNC. The RNC decompresses and
transmits the data to the CN. This feature works at the PDCP layer, between the UE and the
RNC. It requires support from both of these NEs. Figure 2-1 shows the overall architecture of
this feature.
3 Technical Description
UDA Procedure
Figure 3-1 shows how this feature works.
NOTE
Some UEs may include the UDA capability response IE in other uplink DT messages.
2. The RNC activates this feature for UDA-capable UEs.
For details about RNC activation, see 3.2 Activation and Deactivation.
3. The UE compresses uplink data.
Before data compression, the UE compares the raw data with data in the UDA memory.
If the raw data is different from data in the UDA memory, the UE sends the raw
data to the RNC.
If the raw data contains data identical to that contained in the UDA memory, the UE
sends the RNC the position of the duplicate information. This includes the position
of the data in the UDA memory and its position in the raw data.
4. The RNC decompresses uplink data.
Upon receiving the compressed data from the UE, the RNC checks the position
information and determines duplicate data in the RNC memory. The RNC reconstructs
the raw data by combining the repetitive content from the RNC UDA memory and the
non-repetitive data.
Activation
The RNC checks whether the UE meets the following requirements to activate this feature:
l The UE initiates a PS service, switches from the CELL_PCH state to the CELL_FACH
or CELL_DCH state, or migrates from another RNC.
l The UE supports UDA.
The RNC sends the UE a PTP_MSG message containing feature parameter configurations,
including UdaMode(BSC6900,BSC6910) and UdaMemSize(BSC6900,BSC6910). The
procedure after the UE receives this message is as follows:
l In normal cases, the UE responds with a PTP_MSG_ACK message. The RNC
decompresses uplink PS data, after receiving the response from the UE.
l If exceptions occur, such as improper RNC configuration or UE faults, the UE responds
with a PTP_MSG_NACK message. If this happens, the RNC does not perform data
decompression.
NOTE
This feature does not support header-only compression. The UE compresses both the header and
payload even when UdaMode(BSC6900,BSC6910) is set to COMPRESS_HEADER_ONLY.
The following figure shows the signaling process to activate the feature.
Deactivation
There are two types of deactivation:
l Automatic deactivation
The RNC and UE automatically deactivate this feature when the UE:
Experiences an RLC reset.
Experiences an uplink RLC reestablishment.
Switches to the CELL_PCH state.
Releases PS services.
In this case, the RNC does not send the UE a UDA deactivation message.
l Deactivation triggered by a configuration/compression failure
The RNC sends the UE a PTP_MSG message to deactivate the feature, if
UDA_SWITCH under ProcessSwitch5(BSC6900,BSC6910) is not selected or data
compression fails. The procedure after the UE receives this message is as follows:
1. The RNC increases the proportion of newly accessed UEs using UDA at a step of 10%
until UDA is applied to all newly accessed UEs if the following formula is true:
For the BSC6900, DPU DSP load < (SSDSPMAXUSAGEALMTHD/100 x 100%
18%)
For the BSC6910, GPU UP load < (SSCPUMAXUSAGEALMTHD/100 x 100%
18%)
2. The RNC decreases the proportion of newly accessed UEs using UDA at a step of 30%
until UDA is no longer applied to any UEs if the following formula is true:
For the BSC6900, DPU DSP load > (SSDSPMAXUSAGEALMTHD/100 x 100%
18%)
For the BSC6910, GPU UP load > (SSCPUMAXUSAGEALMTHD/100 x 100%
18%)
3. The RNC does not apply UDA to newly accessed UEs and stops applying UDA to a
randomly selected 10% of the UEs to which UDA is already applied if the following
formula is true:
For the BSC6900, DPU DSP load > (SSDSPMAXUSAGEALMTHD/100 x 100%
15%)
4 Related Features
Prerequisite Features
None
Impacted Features
Feature ID Feature Name Description
WRFD-011500 PDCP Header Compression This feature does not take effect on UEs
with WRFD-011500 PDCP Header
Compression enabled.
5 Network Impact
System Capacity
This feature reduces uplink PS data for UDA-capable UEs by 40% to 70% compared to the
data that is not compressed, or by 5% to 20% when compared to data that is compressed,
decreasing uplink interference and loads.
Network Performance
In the event of uplink congestion with an uplink load of above 75%, web browsing delays
decrease by at least 20% for UDA-capable UEs, improving the service experience.
For the BSC6900, this feature causes a DPU DSP load increase of less than 10%. For the
BSC6910, this feature causes a GPU UP load increase of less than 10%.
6 Engineering Guidelines
The GPU UP subsystem is one with a system number greater than 8000.
Uplink power load of a cell
Observe the value of the counter
VS.MeanULActualPowerLoad(BSC6900,BSC6910).
6.3 Deployment
6.3.1 Requirements
Feature
None
Hardware
None
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.
----End
NOTE
When configuring the 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 parameters listed in the table in "Data Preparation" section from top to bottom 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.
To check whether a parameter supports batch modification, see the Remarks column in the
table in "Data Preparation" section.
----End
6.3.4 Deactivation
The following table describes the parameters for deactivating this feature.
l Proportion of reduced uplink PS data for UDA-capable UEs after the feature is activated
The larger the proportion, the greater the benefits. This proportion can be calculated
using the following formula:
Proportion of reduced uplink PS data for UDA-capable UEs after the feature is activated
= 1- S.UDA.PS.UL.Traffic.BeforeDec.RNC(BSC6900,BSC6910)/
VS.UDA.PS.UL.Traffic.AfterDec.RNC(BSC6900,BSC6910)
NOTE
Activating this feature reduces the uplink PS data for UDA-capable UEs. Accordingly, the value of
the uplink throughput counter VS.HSUPA.MeanChThroughput(BSC6900,BSC6910) may
decrease.
l Web browsing delay
The shorter the delay, the greater the benefits. Evaluate the web browsing delay for
UDA-capable UEs by performing drive tests or using iDart. The iDart tool is currently
unavailable to customers. For details about this tool, contact Huawei technical support.
6.6 Troubleshooting
None
7 Parameters
8) APP_GRP_RES_RSV_SWITCH (Differentiated
Service Based on Application Resource Reservation
Switch)
Whether the Differentiated Service Based on
Application Resource Reservation feature is enabled.
1: This switch is turned on. The RNC identifies
service types, maps different service types to different
resource groups, and configure different resource
reservation policies for these resource groups. In this
way, resource reservation is performed based on
service types.
0: This switch is turned off. The RNC does not reserve
resources based on service types or service groups.
9)RIM_ON_ECO_SWITCH(Support RIM by
eCoordinator Switch)
Whether the RIM procedure is implemented through
the eCoordinator.
1: This switch is turned on. The RIM procedure is
implemented through the eCoordinator.
0: This switch is turned off. the RIM procedure is
implemented through the CN.
This parameter is an advanced parameter. Therefore,
modify the setting of this parameter under the
instruction of Huawei technical support.
10)SRBCHG_DRD_FAST_RB_SETUP_SWITCH(R
B Fast Setup Switch for RB Setups Accompanied by
DRDs with Changing SRBs)
Whether to use the RB fast setup function for RB
setups accompanied by DRDs with changing SRBs.
1: This switch is turned on. The RB fast setup function
is used for RB setups accompanied by DRDs with
changing SRBs.
0: This switch is turned off. The simultaneous setup
procedure is used for RB setups accompanied by
DRDs with changing SRBs.
11)SRBNOCHG_DRD_FAST_RB_SETUP_SWITC
H(RB Fast Setup Switch for RB Setups Accompanied
by DRDs with Unchanged SRBs)
Whether to use the RB fast setup function for RB
setups accompanied by DRDs with unchanged SRBs.
1: This switch is turned on. The RB fast setup function
is used for RB setups accompanied by DRDs with
unchanged SRBs.
H, UL_EVQI_SWITCH, DL_EVQI_SWITCH,
VIDEO_RATE_ADAPTION_SWITCH,
VOIP_MANAGE_SWITCH,
DIFF_SERVICE_ON_TERMINAL_SWITCH,
APP_GRP_RES_RSV_SWITCH,
RIM_ON_ECO_SWITCH,
PRIMOPER_NONROAM_USER_CN_SA_SWITCH
, SRBCHG_DRD_FAST_RB_SETUP_SWITCH,
SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH,
FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWITCH
, WBAMR_HHO_FAIL_ROLLBACK_SWITCH,
EXTD_LAC_PAGING_SWITCH,
TCP_PROXY_SWITCH,
SEAMLESS_CRYSTAL_VOICE_SWITCH,
CS_RB_PRI_MC_SWITCH,
L2U_SRVCC_PS_TIMEOUT_CS_RELOC_IN_SWI
TCH, CRYSTAL_VOICE_DEEPCOVER_SWITCH,
LOAD_BASED_P2D_SWITCH,
PS_R99_BLER_STAT_OPT_SWITCH,
STATE_FACH_CONSISTENT_OPTI_SWITCH,
D2P_RECFG_REEST_SWITCH,
IMPVD_UL_COVER_FOR_SRB_OVER_DCH_SW
ITCH, UL_DT_SAI_PLMN_CMP_SWITCH,
RRC_CONN_SETUP_MSG_ENH_OPT_SWITCH,
UE_UDA_CAP_QUERY_SWITCH, UDA_SWITCH
Unit: None
Actual Value Range:
INTERRAT_LOAD_SINGLE_RPT_FOR_LTE_SWI
TCH,
INTERRAT_LOAD_REPORT_FROM_LTE_SWITC
H,
UL_EVQI_SWITCH,
DL_EVQI_SWITCH,
VIDEO_RATE_ADAPTION_SWITCH,
VOIP_MANAGE_SWITCH,
DIFF_SERVICE_ON_TERMINAL_SWITCH,
APP_GRP_RES_RSV_SWITCH,
RIM_ON_ECO_SWITCH,
PRIMOPER_NONROAM_USER_CN_SA_SWITCH
,
SRBCHG_DRD_FAST_RB_SETUP_SWITCH,
SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH,
FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWITCH
,
WBAMR_HHO_FAIL_ROLLBACK_SWITCH,
EXTD_LAC_PAGING_SWITCH,
TCP_PROXY_SWITCH,
SEAMLESS_CRYSTAL_VOICE_SWITCH,
CS_RB_PRI_MC_SWITCH,
L2U_SRVCC_PS_TIMEOUT_CS_RELOC_IN_SWI
TCH,
CRYSTAL_VOICE_DEEPCOVER_SWITCH,
LOAD_BASED_P2D_SWITCH,
PS_R99_BLER_STAT_OPT_SWITCH,
STATE_FACH_CONSISTENT_OPTI_SWITCH,
D2P_RECFG_REEST_SWITCH,
IMPVD_UL_COVER_FOR_SRB_OVER_DCH_SW
ITCH,
UL_DT_SAI_PLMN_CMP_SWITCH,
RRC_CONN_SETUP_MSG_ENH_OPT_SWITCH,
UE_UDA_CAP_QUERY_SWITCH,
UDA_SWITCH
Default Value:
INTERRAT_LOAD_SINGLE_RPT_FOR_LTE_SWI
TCH:
0,INTERRAT_LOAD_REPORT_FROM_LTE_SWIT
CH:0,UL_EVQI_SWITCH:0,DL_EVQI_SWITCH:
0,VIDEO_RATE_ADAPTION_SWITCH:
0,VOIP_MANAGE_SWITCH:
0,DIFF_SERVICE_ON_TERMINAL_SWITCH:
0,APP_GRP_RES_RSV_SWITCH:
0,RIM_ON_ECO_SWITCH:
0,PRIMOPER_NONROAM_USER_CN_SA_SWITC
H:0,SRBCHG_DRD_FAST_RB_SETUP_SWITCH:
0,SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH:
0,FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWITC
H:0,WBAMR_HHO_FAIL_ROLLBACK_SWITCH:
0,EXTD_LAC_PAGING_SWITCH:
0,TCP_PROXY_SWITCH:
0,SEAMLESS_CRYSTAL_VOICE_SWITCH:
0,CS_RB_PRI_MC_SWITCH:
0,L2U_SRVCC_PS_TIMEOUT_CS_RELOC_IN_S
WITCH:
0,CRYSTAL_VOICE_DEEPCOVER_SWITCH:
0,LOAD_BASED_P2D_SWITCH:
0,PS_R99_BLER_STAT_OPT_SWITCH:
0,STATE_FACH_CONSISTENT_OPTI_SWITCH:
0,D2P_RECFG_REEST_SWITCH:
18)L2U_SRVCC_PS_TIMEOUT_CS_RELOC_IN_S
WITCH
Whether to support the incoming CS handover during
the single radio voice call continuity (SRVCC) with
simultaneous CS and PS handovers if the PS
RELOCATION REQUEST message times out.
1: When this switch is set to on, the RNC supports the
incoming CS handover after receiving a
RELOCATION REQUEST message from the CS
domain during the SRVCC for CS+PS combined
services, if the RNC does not receive a
RELOCATION REQUEST message from the PS
domain within the period of time specified by
"IRatHoWaitPSRelocReqTmr" parameter in the "SET
USTATETIMER" command.
0: When this switch is set to off, the RNC does not
support the incoming CS handover in the preceding
scenario.
For details, see 3GPP TS 23.216.
19)CRYSTAL_VOICE_DEEPCOVER_SWITCH
Whether the RNC-level Crystal Voice in Deep
Coverage function takes effect.
1: This switch is set to on. The RNC-level Crystal
Voice in Deep Coverage function takes effect.
0: This switch is set to off. The RNC-level Crystal
Voice in Deep Coverage function does not take effect.
20)LOAD_BASED_P2D_SWITCH
Whether the load- and Ec/N0-based P2D state
transition algorithm is enabled.
1: Indicates that this switch is set to ON. If both of the
following conditions are met, the RNC triggers a P2D
state transition. If either of the following conditions is
not met, the RNC triggers a P2F state transition.
(1)The actual uplink cell load enters the state specified
by "ActualloadStateForP2D" or enters a lighter state,
and the downlink non-HSPA transmit power enters the
state specified by "NonHLoadStateForP2D" or enters
a lighter state. The values of the "ActualloadState-
ForP2D" and "NonHLoadStateForP2D" parameters
can be queried by running the RNC MML command
"LST UUESTATETRANS".
(2) The Ec/N0 is greater than or equal to
"P2DEcNoThd". The value of the "P2DEcNoThd"
parameter can be queried by running the RNC MML
command "LST UFRC".
TCH, CRYSTAL_VOICE_DEEPCOVER_SWITCH,
LOAD_BASED_P2D_SWITCH,
PS_R99_BLER_STAT_OPT_SWITCH,
STATE_FACH_CONSISTENT_OPTI_SWITCH,
D2P_RECFG_REEST_SWITCH,
IMPVD_UL_COVER_FOR_SRB_OVER_DCH_SW
ITCH, UL_DT_SAI_PLMN_CMP_SWITCH,
RRC_CONN_SETUP_MSG_ENH_OPT_SWITCH,
UE_UDA_CAP_QUERY_SWITCH, UDA_SWITCH
Unit: None
Actual Value Range:
INTERRAT_LOAD_SINGLE_RPT_FOR_LTE_SWI
TCH,
INTERRAT_LOAD_REPORT_FROM_LTE_SWITC
H,
UL_EVQI_SWITCH,
DL_EVQI_SWITCH,
VIDEO_RATE_ADAPTION_SWITCH,
VOIP_MANAGE_SWITCH,
DIFF_SERVICE_ON_TERMINAL_SWITCH,
APP_GRP_RES_RSV_SWITCH,
RIM_ON_ECO_SWITCH,
PRIMOPER_NONROAM_USER_CN_SA_SWITCH
,
SRBCHG_DRD_FAST_RB_SETUP_SWITCH,
SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH,
FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWITCH
,
WBAMR_HHO_FAIL_ROLLBACK_SWITCH,
EXTD_LAC_PAGING_SWITCH,
TCP_PROXY_SWITCH,
SEAMLESS_CRYSTAL_VOICE_SWITCH,
CS_RB_PRI_MC_SWITCH,
L2U_SRVCC_PS_TIMEOUT_CS_RELOC_IN_SWI
TCH,
CRYSTAL_VOICE_DEEPCOVER_SWITCH,
LOAD_BASED_P2D_SWITCH,
PS_R99_BLER_STAT_OPT_SWITCH,
STATE_FACH_CONSISTENT_OPTI_SWITCH,
D2P_RECFG_REEST_SWITCH,
IMPVD_UL_COVER_FOR_SRB_OVER_DCH_SW
ITCH,
UL_DT_SAI_PLMN_CMP_SWITCH,
RRC_CONN_SETUP_MSG_ENH_OPT_SWITCH,
UE_UDA_CAP_QUERY_SWITCH,
UDA_SWITCH
Default Value:
INTERRAT_LOAD_SINGLE_RPT_FOR_LTE_SWI
TCH:
0,INTERRAT_LOAD_REPORT_FROM_LTE_SWIT
CH:0,UL_EVQI_SWITCH:0,DL_EVQI_SWITCH:
0,VIDEO_RATE_ADAPTION_SWITCH:
0,VOIP_MANAGE_SWITCH:
0,DIFF_SERVICE_ON_TERMINAL_SWITCH:
0,APP_GRP_RES_RSV_SWITCH:
0,RIM_ON_ECO_SWITCH:
0,PRIMOPER_NONROAM_USER_CN_SA_SWITC
H:0,SRBCHG_DRD_FAST_RB_SETUP_SWITCH:
0,SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH:
0,FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWITC
H:0,WBAMR_HHO_FAIL_ROLLBACK_SWITCH:
0,EXTD_LAC_PAGING_SWITCH:
0,TCP_PROXY_SWITCH:
0,SEAMLESS_CRYSTAL_VOICE_SWITCH:
0,CS_RB_PRI_MC_SWITCH:
0,L2U_SRVCC_PS_TIMEOUT_CS_RELOC_IN_S
WITCH:
0,CRYSTAL_VOICE_DEEPCOVER_SWITCH:
0,LOAD_BASED_P2D_SWITCH:
0,PS_R99_BLER_STAT_OPT_SWITCH:
0,STATE_FACH_CONSISTENT_OPTI_SWITCH:
0,D2P_RECFG_REEST_SWITCH:
0,IMPVD_UL_COVER_FOR_SRB_OVER_DCH_S
WITCH:0,UL_DT_SAI_PLMN_CMP_SWITCH:
0,RRC_CONN_SETUP_MSG_ENH_OPT_SWITCH:
0,UE_UDA_CAP_QUERY_SWITCH:
0,UDA_SWITCH:0
UdaMod BSC690 SET WRFD- Uplink Meaning: Uplink data acceleration mode. When the
e 0 UUPCT 180202 Data uplink data acceleration function is enabled, this
RLSWI Accelera parameter can be set to
TCH tion COMPRESS_HEADER_AND_PAYLOAD or
COMPRESS_HEADER_ONLY.
GUI Value Range:
COMPRESS_HEADER_AND_PAYLOAD,
COMPRESS_HEADER_ONLY
Unit: None
Actual Value Range:
COMPRESS_HEADER_AND_PAYLOAD,
COMPRESS_HEADER_ONLY
Default Value:
COMPRESS_HEADER_AND_PAYLOAD
UdaMod BSC691 SET WRFD- Uplink Meaning: Uplink data acceleration mode. When the
e 0 UUPCT 180202 Data uplink data acceleration function is enabled, this
RLSWI Accelera parameter can be set to
TCH tion COMPRESS_HEADER_AND_PAYLOAD or
COMPRESS_HEADER_ONLY.
GUI Value Range:
COMPRESS_HEADER_AND_PAYLOAD,
COMPRESS_HEADER_ONLY
Unit: None
Actual Value Range:
COMPRESS_HEADER_AND_PAYLOAD,
COMPRESS_HEADER_ONLY
Default Value:
COMPRESS_HEADER_AND_PAYLOAD
UdaMe BSC690 SET WRFD- Uplink Meaning: Buffer size for the uplink data acceleration
mSize 0 UUPCT 180202 Data function. When the uplink data acceleration function
RLSWI Accelera is enabled, the RNC compares the value of this
TCH tion parameter and the maximum buffering capability of
the UE and uses the smaller one as the actual buffer
size for storing the repeated uplink PS data. The RNC
uses the repeated uplink PS data to decompress the
uplink PS data.
GUI Value Range: D2048, D4096, D8192, D16384
Unit: byte
Actual Value Range: D2048, D4096, D8192, D16384
Default Value: D4096
UdaMe BSC691 SET WRFD- Uplink Meaning: Buffer size for the uplink data acceleration
mSize 0 UUPCT 180202 Data function. When the uplink data acceleration function
RLSWI Accelera is enabled, the RNC compares the value of this
TCH tion parameter and the maximum buffering capability of
the UE and uses the smaller one as the actual buffer
size for storing the repeated uplink PS data. The RNC
uses the repeated uplink PS data to decompress the
uplink PS data.
GUI Value Range: D2048, D4096, D8192, D16384
Unit: byte
Actual Value Range: D2048, D4096, D8192, D16384
Default Value: D4096
SSDSP BSC690 SET None None Meaning: DSP usage alarm reporting threshold. If the
MAXU 0 CPUTH DSP usage reaches or exceeds the threshold, a DSP
SAGEA D usage alarm is reported, the BE service rate decreases,
LMTHD and BE service packets and CS service packets are
discarded. If the DSP usage is greater than or equal to
the value of DSP Occupancy Alarm Clearance
Threshold but smaller than this threshold, the BE
service rate decreases. The value of DSP Occupancy
Alarm Clearance Threshold must be smaller than the
parameter value. This parameter is an advanced
parameter and must be modified only with the
assistance of Huawei technical support personnel.
GUI Value Range: 30~100
Unit: %
Actual Value Range: 30~100
Default Value: 85
SSCPU BSC691 SET None None Meaning: CPU usage alarm generating threshold.
MAXU 0 CPUTH When the CPU usage of a board reaches or exceeds
SAGEA D the threshold, the ALM-20256 CPU Overload alarm is
LMTHD generated. The value of
"SSCPUAVEUSAGEALMTHD" must be smaller
than "SSCPUMAXUSAGEALMTHD".
GUI Value Range: 30~100
Unit: %
Actual Value Range: 30~100
Default Value: 75
8 Counters
9 Glossary
10 Reference Documents