Vous êtes sur la page 1sur 36

VoLTE Features Overview

TTI Bundling
TTI Bundling Overview

TTIbundlingenablesadatablocktobetransmittedinfourconsecutiveTTIs,whichareboundtogetherand
treatedasthesameresource.
TTIbundlingimproves HARQcombininggainsandreducesthe numberofretransmissions andRTT.

WhentheUE'schannelqualityispoorandtransmitpowerislimited,TTIbundlingincreasesthecelledge
coverageofthePUSCH.
Thegainsproducedbythisfeaturecanbeobservedwhenvoicequalityismaintainedatacelledgewith
poorRFquality.
TTI Bundling Activation
TheTtiBundlingSwitch optionisenabledbyCellAlgoSwitch.UlSchSwitch parameter
Whenthisoptionisselected,theeNodeB determineswhethertoactivateTTIbundlingbasedonthechannel
quality.
AfteractivatingTTIbundling,theeNodeB determinesthenumberofPRBsandselectsanMCSbasedonthe
channelqualityandtheamountofdatatobetransmitted.
Entry into the TTI Bundling State
WhentheTtiBundlingTriggerStrategy parameterissettoSERVICE_VOIP(SERVICE_VOIP),TTIbundlingappliesto
onlyVoLTE.
EnteringtheTTIbundlingstateareasfollows:
TheTtiBundlingSwitch oftheeNodeB isturnedon.
TheUEsupportsTTIbundling.
TheUEhasonlyoneQCI1dedicatedbearerandstaysinthetalkspurtsstate.Inaddition,theUEdoesnothavedatato
transmitonthedatabearer.
TheULpoweroftheUEislimited.
ThemeasuredSINRislessthanthetargetSINRformultipleconsecutivetimes.

WhentheTtiBundlingTriggerStrategy parameterissettoSERVICE_MULTIAPP(SERVICE_MULTIAPP),TTIbundling
canapplytoVoLTE oracombinationofVoLTE anddata.
EnteringtheTTIbundlingstateareasfollows:
TheTtiBundlingSwitch oftheeNodeB isturnedon.
TheUEsupportsTTIbundling.
TheUEhasaQCI1dedicatedbearer.
TheULpoweroftheUEislimited.
ThemeasuredSINRislessthanthetargetSINRformultipleconsecutivetimes.

ThenumberofconsecutivetimestomeasureSINRisspecifiedbyCellUlschAlgo.StatisticNumThdForTtibTrig.
IftheUEmeetsalltheseconditions,theeNodeB sendstheUEanRRCConnectionReconfiguration message,
instructingtheUEtoentertheTTIbundlingstate.
ThetargetSINRiscontrolledbyCellTtiBundlingAlgo.SinrThdToTrigTtib.
UE in the TTI Bundling State
FortheUEintheTTIbundlingstate,theeNodeB determinesthenumberofPRBsandMCSbasedonchannel
qualityandtheamountofdatatotransmit.Then,theeNodeB transmitsdatablocks.
WhentheUEisintheTTIbundlingstate,themaximumnumberofuplinkHARQretransmissionsisspecifiedby
theCellUlschAlgo.TtiBundlingHarqMaxTxNum parameter.
IntheTTIbundlingstate,thenumberofRLCsegmentsofavoicepacketcannotbegreaterthanthevalue
specifiedbytheCellUlschAlgo.TtiBundlingRlcMaxSegNum.

RestrictionsinTTIBundling
TTIbundlingusesamaximumof3PRBsandadoptsQPSKwiththehighestMCSorderof10.
WithTTIbundlingisenabled,themaximumnumberofTBSthatcanbetransmittedis504bits.Thisrestricts
theuplinkthroughputofTTIbundling.
Exit from TTI Bundling
TheeNodeB doesnotinstructtheUEtoexittheTTIbundlingstateevenwhen
theUEhasdatatotransmitonthedefaultbearer,
needstosetupanewdedicatedbearer,or
stopsthevoiceserviceQCI1.

TheeNodeB instructstheUEtoexittheTTIbundlingstatewhen
theUEmeetstheexitconditions,
experienceshandoveror
servicedrop,or
needstoreestablishanewconnection.

Ifthevoiceserviceisnotreleased
theeNodeB instructstheUEtoexittheTTIbundlingstatethroughanRRCConnectionReconfigurationmessagewhen
themeasuredSINRisgreaterthanthesumofthetargetSINRandtheCellUlschAlgo.HystToExitTtiBundling parameter
valueformultipleconsecutivetimes.ThenumberofconsecutivetimesisspecifiedbytheStatisticNumThdForTtibExit
parameter.

Ifthevoiceserviceisreleased
theeNodeB instructstheUEtoexittheTTIbundlingstatethroughanRRCConnectionReconfigurationmessagewhen
themeasuredSINRisgreaterthanMIN{(targetSINR+CellUlschAlgo.HystToExitTtiBundling),6dB}formultiple
consecutivetimes.ThenumberofconsecutivetimesisspecifiedbytheStatisticNumThdForTtibExit parameter.
Counters for TTI bundling

CountersforobservingwhetherTTIbundlingisactivated
VoLTE Rate Control
VoLTE Rate Control Overview
VoLTE RateControladjusts theAMRNB/AMRWB rateforuplinkvoiceservicesdependingontheuplink
channelqualityandvoicequality.

Whentheuplinkchannelqualityandvoicequalityarefavorable:ahighvoicecodingrateisusedto
furtherimprovevoicequality.

Whentheuplinkchannelqualityandvoicequalityarepoor: alowvoicecodingrateisusedtoreduce
theuplinkpacketlossrateandimproveuplinkvoicecoverage.
Voice Rate Adjustment

TheeNodeB determineswhethertoadjustthevoiceratedependingon
theuplinkchannelqualityand
voicequality.

TheeNodeB orSBCadjuststhevoicerateoftheUE.

VoicerateadjustmentiscontrolledbytheCellAlgoSwitch.UlAmrcMode parameterasfollows:
IfCellAlgoSwitch.UlAmrcMode =ULAMRC_ENB_CONTROL(ULAMRC_ENB_CONTROL),theeNodeB adjusts
thevoicerateoftheUE.
IfCellAlgoSwitch.UlAmrcMode =ULAMRC_SBC_CONTROL(ULAMRC_SBC_CONTROL),theSBCadjuststhe
voicerateoftheUE.
IfIMSsignalingisencrypted,theeNodeB cannotobtaintheratesetsupportedbytheUE.Inthissituation,SBC
canbeusedtoperformvoiceratecontrol
Supported AMR Codec Rates
VoLTE RateControlfeaturesupportsthefollowingratesforAMRNBservices:12.2kbit/s,7.4kbit/s,and4.75kbit/s
VoLTE RateControlfeaturesupportsthefollowingratesforAMRWBservices:23.85kbit/s,12.65kbit/s,and6.6kbit/s

BothratesineachAMRgroupcanbeallocatedtoaUE.
AMRgroupsarecontrolledbythefollowingparameters:
VoiceAmrControl.VoiceAmrCtrlParaGroupId
VoiceAmrControl.HighAmrCodingMode
VoiceAmrControl.LowAmrCodingMode
VoLTE RateControlfeaturesupportsrateadjustmentwithinAMRNBservicesorwithinAMRWBservices,
notbetweenAMRNBandAMRWBservices.
VoLTE Rate Control feature Function

AftertheVoLTE RateControlfeatureisenabled:

TheAMRcodingrateincreasesifthefollowingconditionsarebothmet:
TheTBSoftheUEisgreaterthanTbsUpTh.
TheuplinkpacketlossrateforserviceswithaQCI1<VoiceAmrControl.PlrThdForIncreasingAmr fortwo
consecutivetimes.

TheAMRcodingratedecreasedifthefollowingconditionsarebothmet:
TheTBSoftheUEislessthanTbsDownTh.
TheuplinkpacketlossrateforserviceswithaQCI1>VoiceAmrControl.PlrThdForDecreasingAmr fortwo
consecutivetimes.

IftheUlAmrcExceedingInitialSw(UlAmrcExceedingInitialSw) optionoftheCellAlgoSwitch.AmrcAlgoSwitch
parameterisselected,theincreasedcodingratecanexceedtheinitialcodingrateofthiscall.
Otherwise,theincreasedcodingratecannotexceedtheinitialcodingrateofthiscall.
Counters for VoLTE Rate Control
CountersforobservingwhetherVoLTE RateControlisactivated
DRX
Overview of DRX

With DRX the UE can switch between active and sleep states.
DRX cycle consists:
active state and
sleep state.

In non-DRX mode, the UE always turns on its receiver and stays in the active state.

DRX enables the UE to turn on its receiver and enters active state only when it needs to
receive DL data or signaling.
The UE turns off its receiver and enters sleep state in other situations to reduce power
consumption.
Advantages of DRX
Compared with continuous reception, DRX has the following advantages:

In DRX mode, the UE does not need to continuously monitor the physical downlink control channel
(PDCCH). power consumption is reduced, and battery runtime is prolonged.

As an intermediate state between the RRC_CONNECTED and RRC_IDLE modes, DRX reduces
the probability of transitions from RRC_CONNECTED to RRC_IDLE. reduce signaling
overhead of a network, especially a network with a large number of smart UEs.

UEs can perform automatic neighbor relation (ANR) measurements during the sleep time in DRX.
DRX Mode Entering and Exiting Conditions
DRX Mode Entering Conditions
The DRX functionality is controlled by the general DRX switch DrxAlgSwitch and the EnterDrxSwitch.
After the UE receives an RRC Connection Reconfiguration message it enters the DRX mode.
This message is sent by the eNodeB if all the following conditions are met:
The DrxAlgSwitch parameter is set to ON.
All the bearers for the UE support DRX.
The EnterDRXSwitch parameter of each bearer is set to ON.
The traffic volume of the UE is low.
For the traffic measurement, the traffic volume threshold is specified by the FddEnterDrxThd
parameter, and the measurement period is specified by the DataAmountStatTimer parameter.
DRX Mode Exiting Conditions
A UE exits the DRX mode in any of the following scenarios:
after it receives an RRC Connection Reconfiguration message with release:
This message is sent by the eNodeB if one of the following conditions is met:
The QCI of a new service does not allow the UE to enter the DRX mode.
The EnterDRXSwitch parameter of the QCI is set to OFF.
The traffic volume of the UE is high.
For the traffic measurement, the traffic volume threshold is specified by the FddExitDrxThd parameter,
and the measurement period is specified by the DataAmountStatTimer parameter. However, if the
FddExitDrxThd parameter is set to 100, the UE does not exit the DRX mode.
If the DrxAlgSwitch parameter is set to OFF, the eNodeB instructs the UE to exit the DRX mode
upon DRX reconfiguration originated by the UE.
If the UE in RRC_CONNECTED mode experiences a radio link failure (RLF) when radio conditions
deteriorate, the UE automatically exits the DRX mode.
Concepts Related to the DRX Cycle
On Duration
In DRX mode, a UE continuously monitors the PDCCH for possible signaling for a certain period of time.
This continuous period is called On Duration, and the related timer is OnDurationTimer.

DRX Cycle
A DRX cycle specifies the periodic repetition of the On Duration followed by a possible period of inactivity.

Active Time
In active time, the UE turns on its receiver and monitors the PDCCH. Active time may be an On Duration
period during which the UE needs to turn on its receiver. DRX timers include the DRX Inactivity Timer,
Contention Resolution Timer, and DRX Retransmission Timer.

Sleep Time
In sleep time, the UE turns off its receiver and does not monitor the PDCCH.

Long DRX Cycle


After the UE enters the DRX mode, it must apply a long DRX cycle at the beginning. The duration of a
long DRX cycle is specified by the LongDrxCycle parameter.

Short DRX Cycle


It is not mandatory to apply a short DRX cycle. The ShortDRXCycle parameter specifies the duration of a
short DRX cycle. If a short DRX cycle is configured for the UE, the UE determines when to apply the long or
short DRX cycle.
Switching Between Active Time and Sleep Time

DRX Cycle Switching between active time and sleep time

Switching between active time and sleep time is


determined by DRX timers and service processes.

Conditions for starting active time


Condition Meaning
OD A DRX cycle starts.
IA A PDCCH indicating an initial UL or DL data transmission is received.

R The HARQ RTT Timer expires.


SR A UL scheduling request is sent.
UR A UL negative acknowledgment (NACK) is received, and retransmission is
required.
RAR A non-contention-based random access response is received.
CR Msg3 is sent in a random access procedure.
DRX for VoIP Services
For VoIP services, users can set DRX parameters corresponding to QCI 1.
For VoIP services, a set of special DRX parameter settings is available for reducing UE power
consumption while maintaining VoIP capacity.
Long DRX Cycle
The long DRX cycle is specified by the LongDrxCycle parameter.
The value SF20(20 subframes) is recommended for QCI 1, because VoIP services have a scheduling
period of 20 ms.
If the parameter value is too small, it results in a high proportion of time that the UE is in active state
and therefore less power savings.
If the parameter value is too large, it leads to a possibility of a conflict between the VoIP scheduling
occasion and the silent period. This delays packet transmission and has a negative impact on user experience.
Short DRX Cycle
Short DRX cycles are not available for VoIP services.
On Duration Timer
An eNodeB counts the number of UEs with VoIP services in each cell and set a value for the On
Duration Timer, which is specified by the OnDurationTimer parameter.
If there are a large number of UEs with VoIP services, set a large value for this parameter to ensure
scheduling of the VoIP services. The value PSF10(10 subframes) is recommended for QCI 1.
DRX Inactivity Timer
The DRX Inactivity Timer is specified by the DrxInactivityTimer parameter.
The value PSF3(3subframes) is recommended for QCI 1.
DRX Counters

CounterstoverifywhenDRXtakeeffect. CounterstoobtainoutofsynchronizationdurationsinDRX
L.Traffic.PktInterval.Num.Index0 L.User.UL.Unsync.Dur.Index0
L.Traffic.PktInterval.Num.Index1 L.User.UL.Unsync.Dur.Index1
L.Traffic.PktInterval.Num.Index2 L.User.UL.Unsync.Dur.Index2
L.Traffic.PktInterval.Num.Index3 L.User.UL.Unsync.Dur.Index3
L.Traffic.PktInterval.Num.Index4 L.User.UL.Unsync.Dur.Index4
L.Traffic.PktInterval.Num.Index5 L.User.UL.Unsync.Dur.Index5
L.Traffic.PktInterval.Num.Index6 L.User.UL.Unsync.Dur.Index6
L.Traffic.PktInterval.Num.Index7 L.User.UL.Unsync.Dur.Index7
L.Traffic.PktInterval.Num.Index8 L.User.UL.Unsync.Dur.Index8
Semi-Persistent Scheduling
Semi-Persistent Scheduling Overview
Semi-persistent scheduling feature for small-packet
services that are periodically transmitted such as VoLTE.
Before entering talk spurts, the eNodeB allocates fixed
resources to UEs through the PDCCH message.
Before exiting talk spurts or releasing resources.
The UEs do not need to apply for resource allocation
from the PDCCH again, thereby saving PDCCH
resources.

PDCCH allocation
compared between
Dynamic and SPS
Scheduling

dynamicscheduling
semipersistentscheduling
Comparison between Semi-Persistent Scheduling Dynamic Scheduling
Semi-Persistent Scheduling Selection

During talk spurts, eNodeBs use semi-persistent scheduling in the following scenarios:
The parameters are selected:
The SpsSchSwitch option of the CELLALGOSWITCH.UlSchSwitch parameter in the UL
The SpsSchSwitch option of the CELLALGOSWITCH.DlSchSwitch parameter in the DL.
The UE supports semi-persistent scheduling.
The UE performing voice services is in UL or DL talk spurts.
The UL or DL for the UE has only one dedicated bearer for services with QCI 1. There is no data
transmission on the UL data bearer.
RLC segmentation is not performed in the UL or DL for the UE.
When ROHC is enabled, the UL or DL ROHC is in the stable compression state, the size of the ROHC
header is relatively stable.

During talk spurts, eNodeBs use dynamic scheduling in the following scenarios:
Transmission of large packets, signaling or uncompressed packets generated
Downlink semi-persistent retransmission
Uplink semi-persistent adaptive retransmission
Semi-Persistent Scheduling Selection
UplinkSemiPersistentScheduling DownlinkSemiPersistentScheduling
Duringsemipersistentscheduling,theeNodeB determines Duringsemipersistentscheduling,theeNodeB determines
themodulationandcodingscheme(MCS)and themodulationandcodingscheme(MCS)and
thenumberofPRBs thenumberofPRBs
basedon: basedon:
Voicepacketsize Voicepacketsize
SINR WidebandCQI

Loadbasedscheduling
LoadbasedschedulingallowstheeNodeB toadaptivelyselectdynamicorsemipersistentschedulingbasedon
serviceloadinbothULandDL.
HIGHLOAD:theeNodeB appliessemipersistentschedulingtoavoidPDCCHoverloadandtheimpactonvoicequality
andcapacity.
LOWLOAD: theeNodeB appliesdynamicschedulingtoprovidebetterexperienceonvoiceservicesandimprove
spectralefficiency.
LoadbasedschedulingintheULandDLiscontrolledby:
TheUlVoIPLoadBasedSchSwitch oftheCellUlSchAlgo. UlEnhencedVoipSchSw parametercontrolsLBschedulinginUL.
TheDlVoIPLoadBasedSchSwitch oftheCellDlSchAlgo. DlEnhancedVoipSchSw parametercontrolsLBschedulinginDL.
Power Control in Semi-Persistent Scheduling

SemipersistentschedulingforVoLTE intheDL:PowerControlisnotperformed.
Instead,theeNodeB transmitpowerisevenlysharedbyeachPRB.

SemipersistentschedulingforVoLTE intheUL:ClosedloopPowerControlforthePUSCHcanbeenabledor
disabledbysettingtheCloseLoopSpsSwitch optionoftheCellAlgoSwitch.UlPcAlgoSwitch parameter.

IftheCloseLoopSpsSwitch optionisselected,theeNodeB adjuststransmitpowerforthePUSCH


basedonthemeasuredIBLERofvoiceservices.
IftheCloseLoopSpsSwitch optionisdeselected,theeNodeB usesopenloop(notclosedloop)
powercontrolforthePUSCH.
Counters for Semi-Persistent Scheduling

Toverifywhenadaptivedynamicschedulingandsemipersistentschedulingtakeeffect.
ROHC
ROHC Overview
ROHCprovidesanefficientheadercompressionmechanismfordatapacketstransmittedonradiolinkstosolve
theproblemsofhighbiterrorrates(BERs)andlongroundtriptime(RTT).

ROHChelpsreduceheaderoverheads,lowerthepacketlossrate,andshortenresponsetime.
InthecurrentversionofROHCisusedtocompresstheheadersofonlyvoicepackets(QCIof1andPTTQCI
services).

ROHCreducesthepacketsizeandphysicalresourceblock(PRB)overheads.WhenPRBsareinsufficient,ROHC
helpsincreasesystemcapacity.
ROHC Profiles
ROHCisconsistingofdifferentprofilesforpacketflowscompliantwithdifferentprotocols.
Profilesdefinethecompressionmodesforpacketflowswithdifferenttypesofprotocolheaders.
EachprofileisidentifiedbyaprofileID.Profile0x0000indicatesthatpacketheadersarenotcompressed.
ProfileID Protocol Remarks
0x0001 RTP,UserDatagramProtocol Fordetails,seeRFC3095andRFC4815.
(UDP),andIP
0x0002 UDPandIP Fordetails,seeRFC3095andRFC4815.
0x0003 EncapsulatingSecurityPayload Fordetails,seeRFC3095andRFC4815.
(ESP)andIP
0x0004 IP Fordetails,seeRFC3843andRFC4815.

UECapabilityIE RRCReconfiguration
ROHC Operating Modes
ROHCoperatesin
UnidirectionalMode(UMode),
BidirectionalOptimisticMode(OMode),or
BidirectionalReliableMode(RMode)mode.

OperatingModeTransition

TheinitialoperatingmodeofthecompressorisUMode.Afterconfirmingpacketreceptionbythedecompressor,the
compressorswitchestoOModeorRMode.
Theoperatingmodetransitionisdeterminedbythedecompressor.
WhentheeNodeB isthecompressor,theUEworksasthedecompressor andtriggersoperatingmode
transitionfortheeNodeB.
WhentheeNodeB isthedecompressor,itdeterminesthetargetoperatingmodebasedonthe
PdcpRohcPara.HighestMode parameterandinstructstheUEtochangetheoperatingmode.
IfthePdcpRohcPara.HighestMode parameterissettoR_MODE(BiDirectionalReliableMode),theUE
canswitchtoahighermode(OModeorRMode)andstayinRMode.
IfthePdcpRohcPara.HighestMode parameterissettoO_MODE(BidirectionalOptimisticMode),theUE
canswitchtoandstayinOMode.
ROHC Impacts on Features

FeatureID FeatureName Description


LOFD001016 SemiPersistentScheduling WhenROHCisenabled,compressedpacketsizesfluctuate,evenduringtalk
spurts,duetochangesinthequalityoftheradiochannels,theROHC
operatingmodeused,andvariationsinthedynamicfieldsofthepacket
headersattheapplicationlayer.Therefore,ROHCimpactsLOFD001016
VoIPSemipersistentScheduling.Ifthepacketsizeaftercompressionis
greaterthanthemaximumsizeallowableforsemipersistentscheduling,the
eNodeB usesdynamicschedulingforthedatabeyondthesizelimit.
WhentheULnormalorsmartpreallocation functionisenabled,ULROHC
willyieldfewgainsinresourcesavingifthesizeofpacketsscheduledbythe
eNodeB inpreallocation isgreaterthanthesizeofvoicepackets.
LOFD110225 UplinkDataCompression WhenROHCisenabled,compressedpacketsizesfluctuate,evenduringtalk
spurts,duetochangesinthequalityoftheradiochannels,theROHC
operatingmodeused,andvariationsinthedynamicfieldsofthepacket
headersattheapplicationlayer.Therefore,ROHCimpactsLOFD001016
VoIPSemipersistentScheduling.Ifthepacketsizeaftercompressionis
greaterthanthemaximumsizeallowableforsemipersistentscheduling,the
eNodeB usesdynamicschedulingforthedatabeyondthesizelimit.
WhentheULnormalorsmartpreallocation functionisenabled,ULROHC
willyieldfewgainsinresourcesavingifthesizeofpacketsscheduledbythe
eNodeB inpreallocation isgreaterthanthesizeofvoicepackets.
ROHC Parameters
ParameterName ParameterID SettingNotes
Inlaterversions,thePdcpRohcPara.RohcSwitch parameterwillbereplaced
bytheCellAlgoSwitch.RohcSwitch(N/A,LTE FDD eNodeB) parameter.The
currentversionsupportsconfigurationsynchronizationanddeliveryofeNodeB
levelandcelllevelparameters.IftheeNodeBlevelparameterissettoON(On),
PdcpRohcPara.RohcS
ROHCswitch whetherthefunctionisprovidedincellsisdeterminedbytheeNodeBlevel
witch
switch.IftheeNodeBlevelparameterissettoOFF(Off),whetherthefunctionis
providedincellsisdeterminedbythecelllevelswitch.Therefore,youare
advisedtoswitchtothecelllevelswitch,thenturnofftheeNodeBlevelswitch,
andavoidusingtheeNodeBlevelswitchforROHCafterwards.
Thisparameterappliestotheuplinkonly.ThehighestoperatingmodeofROHC
inthedownlinkiscontrolledbyUEs.

TherecommendedvalueisO_Mode.

Thereasonsareasfollows:
PdcpRohcPara.Highe
ROHCHighestmode
stMode
WhenU_Modeisused,iftheradiolinkqualityispoor,thecompressionwillbe
inefficient.
R_ModeintroducesmorefeedbackdatathanO_Modealthoughthesetwo
modeshavesimilarcompressionefficiency.Inaddition,framelossmayoccur
onsomeVoLTEUEsworkinginR_Mode.

CommercialVoLTE UEsdonotsupportprofiles0x0003and0x0004atpresent.
Asaresult,setthisparametertoProfile0x0001(Profile0x0001) or
PdcpRohcPara.Profile Profile0x0002(Profile0x0002).
Compressionprofiles
s
IfthisparameterisadjustedwhiletheeNodeB isrunning,theadjustment
affectsonlynewservices(notongoingservices).
GLOBALPROCSWITCH ItisrecommendedthatthisparameterissettoON(On) whentheoperator
ROHCswitch .ProtocolSupportSwit providestheIMSbasedVoIPservicesintheLTEnetworkandthemainstream
ch commercialVoLTE UEshavepassedtheinterconnectiontest.
ROHC Counters

Fordownlinktransmission,checkthevaluesof
L.PDCP.DL.RoHC.HdrCompRatio and
L.PDCP.DL.RoHC.PktCompRatio.
Smallervaluesindicatehighercompressionefficiency.

Foruplinktransmission,checkthevaluesofthefollowingcounters:
L.PDCP.UL.RoHC.FailDecompRatio
Asmallervalueindicatesahigherdecompressionsuccessrate.Ifthevalueis0,thedecompression
successrateis100%.

L.PDCP.UL.RoHC.HdrCompRatio and
L.PDCP.UL.RoHC.PktCompRatio.
Smallervaluesindicatehighercompressionefficiency.When ROHCisworkingundernormalradio
conditions,thevaluesofthetwocountersarelessthan100%.

Vous aimerez peut-être aussi