Uplink Data and VoLTE Service Concurrency Optimization

※ Background
During resource allocation to UEs simultaneously performing VoLTE and data services, the following may happen:
 For VoLTE services, the eNodeB allocates uplink instantaneous RBs far more than required, which decreases resources available
to other VoLTE UEs.
 Uplink RB allocation considers only the VoLTE packet size. That is, the eNodeB does not ensure enough resources for uplink
TCP/RLC feedback of downlink data services especially when the VoLTE uplink is congested, which may significantly decrease
the downlink throughput.
※ Principles
If the UlMixVoLTEOptSwitch and UlVoLTEDataSizeEstSwitch UE eNodeB Estimated voice traffic
options are selected, the uplink PRB usage is greater than the volume + Total volume of
traffic in the UE's buffer
threshold (30% by default), and the uplink equivalent CCE usage is SR
less than the threshold (70% by default), then:
 After the eNodeB receives a voice scheduling request (SR), Allocated resources After
the eNodeB allocates resources according to the volume of for a specific traffic optimization
volume
to-be-scheduled voice traffic (instead of the total volume of
to-be-scheduled voice traffic and data traffic) to the UE. UL Grant
Including the allowed volume Estimated voice traffic
This ensures that the scheduling priority of VoLTE services volume + Volume of voice
of to-be-scheduled traffic
is higher than that of data services, improving uplink voice traffic in the UE's buffer +
Estimated volume of
quality on the entire network. PUSCH Scheduling
TCP/RLC feedback
 After the eNodeB receives a voice SR, it also allocates
resources for uplink TCP/RLC feedback. This reduces the
impact on the downlink throughput when the VoLTE uplink
is congested.