OEB537110 LTE ERAN15.1 VoLTE Service Activation and Data Configuration

LTE eRAN15.
1 VoLTE Service Activation and Data Configuration
Confidential Information of Huawei. No Spreading Without Permission

LTE eRAN15.1 VoLTE Service Activation and Data Configuration



 Disadvantage
 IMS deployment and development involves deployment and reconstruction of
a large number of NEs, leading to high costs.

 The preceding figure shows the network architecture of the VoLTE solution. As a
standard VoIP solution defined by 3GPP and IR.92 (GSMA), VoLTE has E2E
standards guarantee.
 Interworking with other networks as well as roaming scenario support (various
VoIP applications in mobile and fixed networks)
 E2E QoS support: PCC-based QoS policy
 SRVCC/eSRVCC for inter-RAT voice call continuity


4G has a shorter delay.

 The call setup delay is shortened to less than 2s. The delay between two VoLTE
sessions is only 0.8s.
 The user-experienced delay is less than 0.05s, which is only one fourth of that on the
3G network.
4G has a lower cost.
 Compared with 2G networks, the cost of 3G networks is greatly reduced. Likewise,
the cost of 4G networks is greatly reduced compared with that of 3G networks.
4G has higher spectral efficiency.
It is estimated that the radio network in the 5G era will transmit data at the same rate as
that of optical fibers without any delay, and be able to connect hundreds of billions of
devices.
720P (750P): 1280 x 720 (720 horizontal lines, progressive scanning)
1080P (1125P): 1920 x 1080 (1080 horizontal lines, progressive scanning). The highest
standard for civil HD videos is 1920 x 1080P/60 Hz with a line frequency of 67.5 kHz.

 Hi-Fi call, multimedia call, and video communication

 AT&T commented that VoLTE provides users with crystal clear voice.
 In mean opinion score (MOS) evaluation, a score of 0 indicates the worst quality, and
5 indicates the best quality. The quality standard of PCM is about 4.4.
 The following are common coding schemes and their MOS values:
 G.711: 4.8;
 G.721/G.723/G.726: 4.2;
 G.728: 4.2;
 G.729: 4.2;
 G.723.1 (5.3): 3.5;
 G.723.1 (6.3): 3.98
 During MOS value evaluation in a drive test, a voice box unit is usually used to
connect the voice links of the calling and called UEs. The MOS values of the calling
and called UEs are the same. To evaluate the downlink MOS value of the calling UE,
enable the called UE to send a standard voice waveform, which will be transmitted on
the network and reach the calling UE. The test software compares the received
waveform with the transmitted waveform and calculates the downlink MOS value. The
process for evaluating uplink MOS is similar except that the voice waveform is sent
from the calling UE to the called UE.

 QCI: QoS class identifier

 GBR: guaranteed bit rate



 However, IMS-based VoLTE is not appropriate for the following scenarios:

 Transmission delay is too severe.
 Voice services are not allowed in certain frequency bands.
 Voice services are not allowed on certain frequencies.
 To prevent UEs from initiating voice services in VoLTE-prohibited areas or prevent
VoLTE UEs from being handed over to VoLTE-prohibited areas, it is recommended
that the following parameters or option be set:
ENodeBAlgoSwitch.EutranVoipSupportSwitch, the VoipHoControlSwitch option
of ENodeBAlgoSwitch.HoAlgoSwitch, and EutranInterNFreq.VolteHoTargetInd.



 Radio links have a high bit error rate and a long round-trip latency. To maximize the
performance of the header compression technology on radio links, ROHC was
proposed in the industry. It can be used to compress multiple types of headers, such
as RTP/UDP/IP, UDP/IP, and ESP/IP headers. In actual applications, it can compress
a 40-byte RTP/UDP/IP header to 1-3 bytes for transmission, greatly improving the
radio bandwidth efficiency.

 In radio systems, the resources on the LTE-Uu interface are far more precious than
the processing capability of processors. Therefore, ROHC is suitable for radio links,
even though it is more complex than other header compression schemes. It is mainly
used for VoIP services.


 Packet flow: A packet flow is a series of data packets using the same compression
algorithm and associated with a single context. Each DRB can carry one or more
packet flows.
 Context: A context contains the information about compression and decompression
characteristics of a packet header. Each context is identified by a unique context
identifier (CID). The number of concurrently activated contexts depends on the
processing capabilities of the compressor and decompressor. Each context consists
of static and dynamic fields. Static fields, such as the source and destination IP
addresses, remain unchanged within a particular packet flow. Static fields are sent
only when the compressor is in the Initialization and Refresh (IR) state. Dynamic
fields, such as the serial number, change based on certain rules. Dynamic fields need
to be updated in real time.
 Why can packet headers be compressed?
 Information in some packet header fields is redundant. For example, many fields are
duplicate between adjacent packets in a specific packet flow, such as the source and
destination IP addresses in the IP headers. Information is also redundant within a
packet header, such as the length field and checksum field in an IP header. The
purpose of ROHC is to eliminate such redundant information.
 Profile: ROHC is an extensible framework consisting of different profiles for packet
flows compliant with different protocols. Profiles define the compression modes for
packet flows with different types of protocol headers. Each profile is identified by a

LTE eRAN15.1 VoLTE Service Activation and Data
Configuration
profile ID. Profile 0x0000 indicates that packet headers are not compressed.

 If both the compressor and the decompressor support ROHC, ROHC is started by
default when a VoIP service bearer is set up but is not started for non-VoIP services
during initial access of a UE.
 ROHC is enabled by setting CellAlgoSwitch.RohcSwitch or
PdcpRohcPara.RohcSwitch to ON(On). You are advised to use
CellAlgoSwitch.RohcSwitch, because PdcpRohcPara.RohcSwitch will be
removed from later versions.
 The ROHC capability of a UE includes the maximum number of concurrent
activated contexts (MAX_CID) and the profiles supported by the UE. The UE
informs the EPC about its ROHC capability during the initial registration. The
eNodeB can acquire the profiles supported by the UE from the EPC or directly
from the UE. After the RRC connection is set up, the EPC sends an Initial
Context Setup Request message over the S1 interface to inform the eNodeB
of the UE's radio capability reported by the UE during initial registration. If the
eNodeB fails to obtain the UE's ROHC capability information from the EPC,
the eNodeB sends a UE Capability Enquiry message over the Uu interface to
query the UE's ROHC capability.
 The eNodeB compares the MAX_CID in the ROHC capability information
reported by the UE with the eNodeB-supported maximum number of
concurrently active contexts per UE, and chooses the smaller one as the

LTE eRAN15.1 VoLTE Service Activation and Data
Configuration
maximum number of concurrent contexts supported by the UE.


 During an inter-eNodeB handover within the E-UTRAN, the source eNodeB informs
the target eNodeB of the ROHC capability of the UE, and the target eNodeB
recalculates the capability of the UE. After the handover, the UE and the target
eNodeB operate with the new ROHC parameters.
 The UE sends a measurement report in the source cell.
 The source eNodeB makes a handover decision. If the eNodeB decides to
perform the handover, it sends a Handover Request message including the
UE's ROHC capability information to the target eNodeB.
 After deciding to admit the handed-over UE, the target eNodeB calculates the
ROHC parameters, which specify the maximum number of concurrently active
contexts and the profiles supported by both the UE and the target eNodeB.
Then, the target eNodeB sends a Handover Request Acknowledge message
carrying the new ROHC parameters to the source eNodeB.
 The source eNodeB sends an RRC Connection Reconfiguration message to
instruct the UE to perform the handover. The message carries the new ROHC
parameters sent by the target eNodeB.
 The UE attempts to access the target cell.
 After the UE successfully accesses the target cell, the UE and eNodeB begin
data transmission on the user plane using the new ROHC parameters.

 The operating mode of ROHC

 In Unidirectional Mode (U-Mode), packets are sent only from the compressor
to the decompressor, and a feedback channel is not mandatory. Therefore, U-
Mode is less reliable than Bidirectional Optimistic Mode (O-Mode) and
Bidirectional Reliable Mode (R-Mode), but its feedback-induced overhead is
minimum compared with the overhead in O-Mode and R-Mode.
 In O-Mode, the decompressor can send feedback messages to the
compressor to indicate decompression failures or successful context updates.
O-Mode is more reliable than U-Mode and requires a smaller amount of
feedback than R-Mode.
 In R-Mode, the reliability of context synchronization between the compressor
and the decompressor is higher than that in any other mode. However,
because of frequent feedback, R-Mode causes the largest amount of link
overhead.

 Note: If the PdcpRohcPara.Profiles parameter is adjusted during eNodeB operation,

the adjustment affects only new services instead of ongoing services.

 In scenarios with limited uplink coverage, the average gain of Huawei ROHC is 6 dB
and 2 dB for SD and HD services, meeting the expectations.
 ROHC improves both coverage and capacity. Uplink RB resources are saved by 26%
and 23% for SD and HD services on average.


 Services such as VoLTE use a relatively fixed packet size, and the intervals between
these packets follow a given pattern. For these services, 3GPP has introduced semi-
persistent scheduling (SPS). During SPS, system resources (both UL and DL) need
to be allocated or assigned only once through the PDCCH. These time-frequency
resources can then be periodically used for these services. SPS is configured using
upper-layer RRC signaling. Its interval is specified at the same time. SPS is activated
by allocating resources through the PDCCH. The UE stores the resource allocation.
These resources are used repeatedly during the subsequent scheduling periods.
They are not re-allocated through the PDCCH unless adaptive retransmissions occur.
 SPS plays a critical role in increasing VoLTE capacity. That is because VoLTE
capacity is primarily subject to the PDCCH, rather than the PDSCH and PUSCH.

 The size of a data packet for a VoLTE service has a significant difference in the talk
spurts and silent period. Therefore, the eNodeB determines the talk spurts and silent
period for the service by checking the size of the data packet. In uplink scheduling,
the eNodeB checks the size of the decompressed data packet at the PDCP layer and
determines whether the VoLTE service is in talk spurts or silent period. The data
packet consists of the voice frame, IP header, UDP header, and RTP header. In
downlink scheduling, the eNodeB checks the PDCP SDU size before header
compression and determines whether the VoLTE service is in talk spurts or silent
period. If there is no data transmission on the SPS resources for a number of
consecutive times, the eNodeB determines that the VoLTE service is in the silent
period.
 SPS is recommended for VoLTE services because SPS maximizes VoLTE capacity
while ensuring service quality. Upon initial scheduling for data transmission, the
eNodeB sends a scheduling indicator through the PDCCH to the UE. If the UE
identifies SPS, the UE stores the scheduling information and transmits and receives
data using the specified resources at a fixed interval. In SPS, UEs can use resources
periodically once the permission is granted. This mode reduces the PDCCH
resources used for scheduling indications and enables the system resources to serve
more UEs without affecting voice quality and system performance. The eNodeB
instructs the UE to release the semi-persistently allocated time-frequency resources
also through the PDCCH.

 This is an example of UL SPS configuration. This message contains the SPS C-RNTI,
SPS interval, implicit release time, power control parameters, and TDD-specific dual-
interval indicator.






 RLC segmentation lowers the requirements for cell-edge throughput. It is crucial to

coverage.
 This table indicates that the requirement for cell-edge throughput is lower when RLC
segmentation is used. This function improves coverage. The larger the number of
segments, the better the coverage.
 An excessive number of RLC segments inevitably affects delay, to which VoLTE
services are sensitive. In addition, the number of segments affects HARQ
retransmissions. The larger the number of segments, the smaller the number of
available HARQ retransmissions. The number of RLC segments is controlled by the
eNodeB.

 Loss of UL VoLTE packets: because VoLTE packets wait in the UE buffer so long that
the packet discard timer expires

 In LTE TDD cells, the recommended values vary with uplink-downlink subframe
configurations:
 12 for uplink-downlink subframe configuration 0;



 TTI bundling enables a transport block (TB) to be transmitted in consecutive TTIs and
makes full use of the combining gain provided by HARQ to shorten the round trip time
(RTT) and enhance UL coverage.
 When the UE is located at the cell edge, RLC segmentation in collaboration with TTI
bundling produces fewer RLC segments than RLC segmentation without TTI
bundling. This reduces PDCCH overheads.


 The following shows an example of the message.
 The 28th bit with a value of 0 (from left to right) in the characters in the red box
indicates that the UE does not support TTI bundling, and the 29th bit with a value of 0
indicates that the UE does not support semi-persistent scheduling.


 Currently, only a small number of UEs support TTI bundling, and the coverage gain is
small. Therefore, it is recommended that TTI bundling be disabled.
 Percentage of voice service UEs = L.Traffic.User.VoIP.Avg/L.Traffic.User.Avg
 Percentage of uplink voice packets from the cell edge =
L.Traffic.UL.FarUE.PktLoss.Tot.QCI.1/L.Traffic.UL.PktLoss.Tot.QCI.1
 Loss rate of uplink voice packets from the cell edge =
L.Traffic.UL.FarUE.PktLoss.Loss.QCI.1/L.Traffic.UL.FarUE.PktLoss.Tot.QCI.1




 The eNodeB selects a pattern for voice rate control and performs voice rate control
when the corresponding triggering conditions are fulfilled. For details about how voice
rate control works, see slides "Types of Voice Rate Control" and "Mechanisms of
Voice Rate Control".

 Cell-level parameter: CellAlgoSwitch.UlAmrcMode

 Operator-level parameter: CellOp.UlAmrcMode



 //Enabling AMR or EVS rate control

 MOD CELLALGOSWITCH: LocalCellId=0,
UlAmrcMode=ADAPTIVE_ENB_CONTROL;
 //Enabling operator-level AMR or EVS rate control (The cell-level voice rate control
function must also be enabled.)
 MOD CELLOP: LocalCellId=0, TRACKINGAREAID=0,
UlAmrcMode=ADAPTIVE_ENB_CONTROL;
 //Setting the parameters related to load-based voice rate control
 MOD CELLRACTHD: LocalCellId=0, CceThdforVolteLoadAmrc=80,
UlRbThdforVolteLoadAmrc=60;
 //Setting the parameters related to uplink-quality-based voice rate control
 ADD VOICEAMRCONTROL: LocalCellId=0, VoiceAmrCtrlParaGroupId=0,
HighAmrCodingMode=AMR_WB_23_85kbps,
LowAmrCodingMode=AMR_WB_12_65kbps, PlrThdForDecreasingAmr=6,
PlrThdForIncreasingAmr=2, RsnThdForDecreasingAmr=14,
RsnThdForIncreasingAmr=5;


 CCE usage = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +
L.ChMeas.CCE.DLUsed)/L.ChMeas.CCE.Avail
 Uplink RB usage of GBR services = (L.ChMeas.PRB.UL.DrbUsed.Avg.VoIP +
L.ChMeas.PRB.UL.DrbUsed.Avg.QCI2)/L.ChMeas.PRB.UL.Avail
 Uplink Packet Loss Rate (VoIP) =
L.Traffic.UL.PktLoss.Loss.QCI.1/L.Traffic.UL.PktLoss.Tot.QCI.1










 Coverage-based VoLTE experience optimization is controlled by the

CellHoParaCfg.FlashSrvccSwitch parameter.

 Flash SRVCC is controlled by the CellHoParaCfg.FlashSrvccSwitch parameter.

 The signaling procedure for UEs in weak-coverage areas is as follows:

 The eNodeB receives an E-RAB SETUP REQUEST message from the IMS.
The message contains a request to set up a dedicated voice bearer of QCI 1
for a UE.
 After determining that the UE is in a weak-coverage area, the eNodeB returns
an E-RAB SETUP RESPONSE message with the cause value of Radio
Resource Not Available to the IMS, declining to set up a dedicated voice
bearer.
 Depending on the role of the UE:
 If the UE is the caller, the IMS sends an SIP message (SIP
500/380/503) to the UE, instructing the UE to initiate a CSFB
procedure.
 If the UE is the callee, the IMS initiates a mobile-terminated procedure
in the 2G CS domain, instructing the UE to initiate a CSFB procedure.








 According to the VoLTE traffic model, a voice frame is sent every 20 ms. UL data
transmission relies on the SRs sent by UEs. If an eNodeB fails to detect SRs, the
scheduling may be delayed, causing the UL packet loss rate to increase. To resolve
packet loss caused by missing SR detection, UL compensation scheduling has been
introduced. With this function, the eNodeB identifies voice service UEs and measures
the length of time a UE is not scheduled. If the duration reaches a certain threshold,
the eNodeB actively sends a UL Grant to the UE to relieve packet loss in this situation.
 This function is controlled by the UlVoipSchOptSwitch option of the
CellUlschAlgo.UlEnhencedVoipSchSw parameter.
 The CellUlschAlgo.UlCompenSchPeriodinSpurt and
CellUlschAlgo.UlCompenSchPeriodinSilence parameters control the minimum
intervals for compensation scheduling during talk spurts and silent periods,
respectively.

 //Setting the parameters related to UL compensation scheduling

 MOD CELLULSCHALGO: LOCALCELLID=0,
ULENHENCEDVOIPSCHSW=UlVoipSchOptSwitch-
1&UlVoipServStateEnhancedSw-1,
ULCOMPENSCHPERIODINSPURT=INTERVAL_20,
ULCOMPENSCHPERIODINSILENCE=INTERVAL_160;




 Compared with VoIP Service Delay Scheduling introduced in eRAN8.1, VoIP and
Data Delay Scheduling introduced in eRAN11.0 further classifies SR-based
scheduling. The eNodeB identifies control-plane, voice, and data SRs based on the
DL SRB scheduling and bearer types, and assigns emergency, high, and low
priorities to these types of SR-based scheduling. This function relatively lifts control-
plane and voice SR/BSR scheduling priorities and lowers data SR priorities, reducing
the voice packet loss rate.
 The CellUlSchAlgo.UlDelaySchStrategy parameter controls the uplink delay-based
scheduling policy.
 If this parameter is set to VOIP_DELAYSCH, the eNodeB assigns scheduling
priorities to voice services based on their wait time.
 If this parameter is set to VOIP_AND_DATA_DELAYSCH, the eNodeB sorts
the UL scheduling priorities of the following objects in descending order:
control signaling > SR and BSR of VoLTE services > SR of data services >
BSR of data services. When there is a high load of both voice and data
services, voice services are preferentially scheduled to ensure voice quality.
 If this parameter is set to NO_DELAYSCH, the eNodeB sorts the priorities of
scheduling triggered by SR and BSR of VoLTE services. A longer wait time
indicates a higher scheduling priority.

 Uplink VoLTE volume estimation for dynamic scheduling allows the eNodeB to
estimate the uplink service volume so that scheduling can be performed at a time. If
this function is not used, the eNodeB can obtain an accurate downlink service volume
but cannot obtain an accurate uplink service volume.

 Uplink VoLTE volume estimation for dynamic scheduling makes the calculation of
uplink VoLTE data volume for dynamic scheduling more accurate, and shortens the
additional delay of voice packets in case the calculated volume is less than the actual
volume. This function improves voice quality when a cell is heavily loaded and DRX is
enabled.
 This function is controlled by the UlVoLTEDataSizeEstSwitch option of the
CellUlschAlgo.UlEnhencedVoipSchSw parameter.
 As shown in the figure, this function saves the BSR scheduling within T1, shortening
voice delay and improving voice quality.
 With this function disabled, the amount of scheduled data after T cannot afford
the two voice packets generated within T. BSR-triggered scheduling is
required for the remaining data after T1.
 With this function enabled, the eNodeB learns that there are two voice packets
within T, and allocates the amount of data that can afford the two voice
packets after T.



 Smart AMR voice frame recovery resolves loss of class B bits only. It cannot
compensate for loss of class A bits.
 Class A bits are used to convey the basic meaning of voice, and class B bits are used
to deliver tones.

 //Activating uplink delay-based dynamic scheduling

ULDELAYSCHSTRATEGY=VOIP_AND_DATA_DELAYSCH;
 //Activating uplink VoLTE volume estimation for dynamic scheduling
ULENHENCEDVOIPSCHSW=UlVoLTEDataSizeEstSwitch-1;
 //Activating uplink VoLTE continuous scheduling - active scheduling of voice service
UEs
 (FDD) MOD CELLULSCHALGO: LOCALCELLID=0,
ULENHENCEDVOIPSCHSW=UlVoLTEContinuousSchSw-
1&UlVoipSchOptSwitch-1;
 (TDD) MOD CELLULSCHALGO: LOCALCELLID=0,
ULENHENCEDVOIPSCHSW=UlEdgeActiveSchSwitch-
 //Activating uplink VoLTE continuous scheduling - uplink service status determination
ULENHENCEDVOIPSCHSW=UlVoLTEContinuousSchSw-



 The DRX technology described in this document refers to DRX for

RRC_CONNECTED UEs. When there is no data, the UEs only need to periodically
monitor the PDCCH, saving their power.

 With increasingly rich LTE applications and the extended use of smartphones, the
standby time and operating time of mobile phones have gradually become a major
concern of users. To reduce UE power consumption, 3GPP specifications for LTE
introduced DRX. Huawei eNodeBs support the C-DRX feature defined in 3GPP
specifications. (The related Huawei feature is LBFD-002017 DRX.)


 The following factors affect DRX state transition in RRC_CONNECTED mode:

 QoS parameters, such as QCI
 Parameter configuration, such as time alignment timer and DRX parameters
 MAC traffic
 UL and DL scheduling
 Handover
 ANR
 Special UE
 DRX state transition also affects scheduling and handovers, as shown in the figure.

 The DRX functionality is jointly controlled by the general DRX switch

CellDrxPara.DrxAlgSwitch and the QCI-specific DRX switch
DrxParaGroup.EnterDrxSwitch.
 After the UE receives an RRC Connection Reconfiguration message with the DRX-
Configuration IE set to setup, it enters DRX.
 Note:
 If a UE is not in DRX mode (for example, when it continuously performs gap-
assisted measurements), the eNodeB does not instruct the UE to enter DRX.
This may occur if fast ANR is enabled, UE information reporting is subscribed
to on the U2020, or the UE is located at the cell edge where signal strength is
low.
 UEs in the TTI bundling state will not enter DRX.
 The traffic volume threshold for entry into DRX is specified by the following
parameters:
FDD: CellDrxPara.FddEnterDrxThd
TDD: CellDrxPara.TddEnterDrxThdUl and CellDrxPara.TddEnterDrxThdDl


 On Duration
 When DRX is used, the UE does not keep its receiver off. It periodically turns
on its receiver to monitor the PDCCH for incoming signaling. This period is
called On Duration and defined by the On Duration Timer. Its length is
determined by the DrxParaGroup.OnDurationTimer parameter.
 DRX cycle
 A DRX cycle is the interval between the beginnings of two On Duration
instances. A DRX cycle includes an On Duration and possible sleep time, as
shown in the figure.
 A DRX cycle consists of active time and sleep time, during which the UE stays
in the active state and sleep state, respectively.

 SR: scheduling request


 On Duration Timer
This timer specifies the time during which the UE

Function
monitors the PDCCH.
Start This timer starts at the first subframe of a DRX cycle.
Timing is based on the number of consecutive PDCCH

On Duration Timing
subframes.
Timer
• The UE receives a DRX Command MAC CE.
Stop
• This timer expires.
After this timer expires, the UE enters the sleep state,

Expiry
no longer monitoring the PDCCH.

 DRX Inactivity Timer
This timer specifies the time during which the UE

determines whether to extend its active time because of
Function
the arrival of new data. This timer provides a reference for
the UE to use a short cycle.
This timer starts or restarts when the UE successfully
Start decodes a PDCCH indicating an initial uplink grant or
downlink user data for this UE.
DRX
Inactivity Timing Timing is based on the number of consecutive PDCCH
Timer subframes.
• The UE receives a DRX Command MAC CE.
Stop
• This timer expires.
After this timer expires, the UE uses a short cycle if the
cycle is configured, and the DRX Short Cycle Timer starts
Expiry
or restarts. Alternatively, the UE uses a long cycle if no
short cycle is configured.

 HARQ RTT Timer and DRX Retransmission Timer
This timer specifies the interval between the initial DL data

transmission and the first DL HARQ retransmission. This timer
Function
is used to determine when to start the DRX Retransmission
Timer.
This timer starts and the DRX Retransmission Timer stops in
either of the following situations:
• At the beginning of the subframe when semi-persistent DL
HARQ Start
data transmission may take place.
RTT
• The UE decodes a PDCCH and knows that a HARQ process
Timer
will have a DL transmission in a new subframe.
Timing Timing is based on the number of PDCCH subframes.
Stop This timer expires.
After this timer expires, if the UE detects that DL data has been
Expiry received correctly, the UE takes no further action; otherwise, the
DRX Retransmission Timer starts.

 Switching from a long DRX cycle to a short DRX cycle

The UE exits the long DRX cycle and enters a short DRX cycle if either of the
following occurs:
 The DRX Inactivity Timer expires.
If there is data to transmit, the eNodeB starts the DRX Inactivity Timer. When
the DRX Inactivity Timer expires, the short DRX cycle starts.
 The UE receives the DRX command MCE.
After the UE receives the DRX command MCE, the UE enters a short DRX
cycle if the eNodeB has assigned the short DRX cycle for the UE. Otherwise,
the UE still uses the long DRX cycle.
 Switching from a short DRX cycle to a long DRX cycle
 If the UE does not receive new data during a specified period after entering a
short DRX cycle, it will switch to a long DRX cycle to save power.
 The period before the UE switches to a long DRX cycle is called the lifetime of
the short DRX cycle. The lifetime is measured by the number of times the
short DRX cycle repeats. The DRX Short Cycle Timer, specified by the
DrxParaGroup.DrxShortCycleTimer parameter, determines how long the
short DRX cycle runs. After the DRX Short Cycle Timer expires, the UE uses
the long DRX cycle.

 The eNodeB calculates the ratio of the number of TTIs with DL data transmission to
the total number of TTIs within each measurement period. It then compares the ratio
with the DRX entry and exit thresholds. If the ratio meets a threshold-related
condition, the eNodeB instructs the UE to enter or exit DRX accordingly.
Parameter
ID Meaning
Name
Indicates the threshold for UEs to enter the discontinuous reception
(DRX) mode in a cell that operates in FDD mode. This threshold is
FDD enter
used in the DRX algorithm. It is expressed as a proportion of the
DRX FddEnte
transmission time intervals (TTIs) with data transmission to the total
threshold rDrxThd
TTIs. If the measurement result of UE traffic is equal to or lower than
this threshold, the eNodeB determines that the UE should remain in
DRX mode or the UE should be triggered to enter DRX mode.
Indicates the threshold for UEs to exit the discontinuous reception
(DRX) mode in a cell that operates in FDD mode. This threshold is
FDD exit used in the DRX algorithm. It is expressed as a proportion of the
FddExit
DRX transmission time intervals (TTIs) with data transmission to the total
DrxThd
threshold TTIs. If the measurement result of UE traffic is higher than this
threshold, the eNodeB determines that the UE should remain in the
non-DRX mode or the UE should be triggered to exit the DRX mode.
Data Indicates the length of the UE traffic measurement period. The traffic
DataAm
amount volume of a UE during this period is measured. Based on the
ountStat
Statistic measurement result, the DRX algorithm decides whether the UE
Timer
timer should enter or exit DRX.

Parameter Name ID Meaning

Indicates the length of the On Duration Timer.
On Duration
OnDurationTimer A larger timer value indicates a longer time UEs
Timer
stay in active time and results in a shorter delay.
DRX Inactivity
DrxInactivityTimer Indicates the length of the DRX Inactivity Timer.
Timer
DRX
Indicates the length of the DRX Retransmission
Retransmission DrxReTxTimer
Timer.
Timer
Long DRX Cycle LongDrxCycle Indicates the length of the long DRX cycle.
Short-Cycle DRX
Supported SupportShortDrx Indicates whether short DRX cycles are enabled.
Indication
Short DRX Cycle ShortDrxCycle Indicates the length of the short DRX cycle.
Indicates the length of the DRX Short Cycle
Timer. If this parameter is set to 1, the length of
this timer is one short DRX cycle. If this
DRX Short Cycle
DrxShortCycleTimer parameter is set to 2, the length of this timer is
Timer
two short DRX cycles. If this parameter is set to a
large value, a UE for which short DRX cycles are
enabled stays in short-cycle DRX for a long time.




 The SRVCC procedure includes:

 PS handover between RANs
 Session transfer at IMS
 The Sv interface is introduced between the MME and the MSC server that is
enhanced for SRVCC. The overall SRVCC procedure is as follows:
 1. The MME informs the SRVCC MSC server through the Sv interface that a
VoIP service is to be handed over to the CS domain.
 2. The SRVCC MSC server instructs the UTRAN or GERAN to prepare for the
handover.
 3. The SRVCC MSC server requests that the media gateway (MGW) provide
the new media-plane information, including the IP address and port number. It
then notifies the service centralization and continuity application server (SCC
AS) that the media stream is to be changed. The SCC AS is a control point for
the IMS session transfer.
 4. The SCC AS notifies the UE of the new media-plane information. The UE
establishes a new VoIP media stream to the MGW and releases the original
VoIP media stream.
 5. The MGW may need to convert the established VoIP media stream to
achieve interworking between the CS voice stream and VoIP voice stream.
The conversion occurs in protocol stacks and voice coding.



 This document focuses on eNodeB functions, which are the same for SRVCC and
eSRVCC. Therefore, SRVCC and eSRVCC are not differentiated in subsequent
slides. On live networks, eSRVCC is used.


 CS+PS SRVCC can be triggered if the following requirements are met:

 SRVCC to GERAN is enabled. This function is controlled by the
GeranSrvccSwitch option of the CellHoParaCfg.HoModeSwitch parameter.
 PS handover from E-UTRAN to GERAN is enabled. This function is controlled
by the GeranPsHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch
parameter.
 SRVCC and PS handover are specified as QCI-specific handover policies.
SRVCC and PS handover are controlled by the SRVCC and PS_HO options
of the InterRatPolicyCfgGroup.GeranGprsEdgeHoCfg parameter,
respectively. These handover policies can be associated with a specific QCI
by setting the QciPara.InterRatPolicyCfgGroupId parameter. If services with
different QCIs exist, the handover policy for the highest-priority QCI prevails.
The handover policy priority for each QCI is specified by the
CellQciPara.QciPriorityForHo parameter. It is recommended that the
handover policy priority be set to the highest priority (1) for QCI 1 and the
lowest priority (9) for QCI 5.
 The GeranExternalCell.CsPsHOInd parameter, which specifies whether an
external GERAN cell supports CS+PS SRVCC, is set to BOOLEAN_TRUE.
 The GeranExternalCell.DtmInd parameter, which specifies whether a
GERAN cell supports dual transmission mode (DTM), is set to
DTM_AVAILABLE.

1. After triggering an SRVCC procedure, the eNodeB delivers the inter-RAT

measurement configuration to the UE.
2. The UE responds to the eNodeB with an RRC Connection Reconfiguration Complete
message.
3. After detecting that a neighboring cell meets the condition for triggering an inter-RAT
handover, the UE sends a measurement report to the eNodeB.
4. The eNodeB determines that a handover should be performed and sends a Handover
Required message containing an SRVCC HO Indication to the MME.
5. The MME separates the voice bearer from non-voice bearers and then sends a
Relocation Request message to both the SRVCC MSC server and target SGSN.
6. After receiving the Relocation Request message, the SRVCC MSC server identifies
the target MSC server based on the target cell ID contained within the message. The
SRVCC MSC server communicates with the target MSC server on a handover. Then,
the target MSC server instructs the target radio network controller (RNC) or base
station controller (BSC) to prepare for the handover. Once the resources are ready,
the target RNC or BSC responds to the target MSC server. Meanwhile, the target
SGSN prepares for a handover of PS services, which is the same as an inter-RAT PS
handover procedure. The UE media plane is then transferred on the IMS.



 Add neighbor relationships with GERAN:

 ADD GERANNFREQGROUP
 ADD GERANNFREQGROUPARFCN
 ADD GERANEXTERNALCELL
 ADD GERANNCELL

 InterRAT policy config group ID: Indicates the group ID of common parameters
related to inter-RAT handovers.

Event Threshold Action

The eNodeB stops inter-frequency or inter-RAT
The signal quality of the
measurements. However, in frequency-priority-
A1 serving cell is higher than a
based handovers, event A1 is used to start
threshold.
inter-frequency measurements.
The eNodeB starts inter-frequency or inter-RAT
The signal quality of the
measurements. However, in frequency-priority-
A2 serving cell is lower than a
based handovers, event A2 is used to stop
threshold.
inter-frequency measurements.
The quality signal of an intra-
or inter-frequency The source eNodeB initiates an intra- or inter-
A3
neighboring cell is higher frequency handover request.
than that of the serving cell.
The signal quality of an inter-
The source eNodeB initiates an inter-frequency
A4 frequency neighboring cell is
handover request.
higher than a threshold.
The source eNodeB initiates an inter-frequency
A5 A2 + A4
handover request.
The signal quality of an inter-
The source eNodeB initiates an inter-RAT
B1 RAT neighboring cell is
handover request.
higher than a threshold.
The source eNodeB initiates an inter-RAT
B2 A2 + B1
handover request.


 Discard timer: This parameter specifies the PDCP discard timer.


 Answer to question 1: Voice over LTE (VoLTE) is an IMS-based voice solution

defined by 3GPP.
 Answer to question 2: Yes.
 Answer to question 3: VoLTE capacity enhancement, VoLTE coverage improvement,
VoLTE quality improvement, VoLTE power saving, and VoLTE mobility management
enhancement



OEB537110 LTE ERAN15.1 VoLTE Service Activation and Data Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OEB537110 LTE ERAN15.1 VoLTE Service Activation and Data Configuration

Uploaded by

Copyright:

Available Formats

LTE eRAN15.

1 VoLTE Service Activation and Data Configuration

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

4G has a shorter delay.

Confidential Information of Huawei. No Spreading Without Permission

 Hi-Fi call, multimedia call, and video communication

Confidential Information of Huawei. No Spreading Without Permission

 QCI: QoS class identifier

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 However, IMS-based VoLTE is not appropriate for the following scenarios:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The operating mode of ROHC

Confidential Information of Huawei. No Spreading Without Permission

 Note: If the PdcpRohcPara.Profiles parameter is adjusted during eNodeB operation,

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 RLC segmentation lowers the requirements for cell-edge throughput. It is crucial to

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The following shows an example of the message.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Cell-level parameter: CellAlgoSwitch.UlAmrcMode

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission