RADIO CONDITION TRIGGERING OF BITRATE REQUEST FOR CODEC RATE ADAPTATION
A first user equipment (UE) device receives Packet Loss Rate (PLR) threshold configuration information from a base station that is serving the first UE device. The first UE device also receives a recommended bitrate from the base station. The recommended bitrate is to be used for a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call between the first UE device and a second UE device. The first UE device determines the radio condition of the first UE device by measuring the PLR at the first UE device. If the measured PLR is below the lower PLR threshold value or above the upper PLR threshold value, the first UE device transmits a bitrate query to the base station.
The present application claims priority to Provisional Application No. 62/454,469, entitled “TRIGGERING OF BITRATE REQUEST FOR CODEC RATE ADAPTATION”, filed Feb. 3, 2017, assigned to the assignee hereof and hereby expressly incorporated by reference in its entirety.
FIELDThis invention generally relates to wireless communications and more particularly to rate adaptation in a radio access network.
BACKGROUND3rd Generation Partnership Project (3GPP) specified a new voice codec named EVS (Enhanced Voice Services). A codec is a device or program that (1) encodes data for transmission and/or storage, and (2) decodes received data for playback, storage, and/or editing. EVS provides high voice quality over a wide range of rates, which allows the low EVS codec rates to still have sufficient quality, and may be used in poor coverage environments and overload scenarios. However, it is still desirable to use the higher codec rates for enhanced audio quality whenever possible. EVS has the flexibility, with a wider rate range and full audio bandwidth, to deliver speech quality that matches other audio inputs, such as stored music, while offering high robustness to delay, jitter, and packet losses.
Radio conditions may also impact the codec mode and codec rate. For example, under poor radio conditions, a lower codec rate may be used to reduce the packet loss, whereas a higher codec rate can be used in good radio conditions to ensure a better user experience. Therefore, a flexible and efficient codec modification mechanism is needed that accounts for the voice codec, network capacity, radio conditions, and user experience.
SUMMARYA first user equipment (UE) device receives Packet Loss Rate (PLR) threshold configuration information from a base station that is serving the first UE device. The first UE device also receives a recommended bitrate from the base station. The recommended bitrate is to be used for a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call between the first UE device and a second UE device. The first UE device determines the radio condition of the first UE device by measuring the PLR at the first UE device. If the measured PLR is below the lower PLR threshold value or above the upper PLR threshold value, the first UE device transmits a bitrate query to the base station.
Voice-over-LTE (VoLTE) is a key feature for the 3GPP Long Term Evolution (LTE) communication specification to provide voice service and is being deployed and launched by operators all over the world, which makes VoLTE capability extremely important for operators. One of the critical factors that may impact the user experience of VoLTE service is the voice codec configuration. For example, a higher Adaptive Multi-Rate (AMR) voice code rate may provide a higher-definition voice call and accordingly a better user experience. When a higher AMR voice code rate is used, the higher codec rate requires more radio resource allocation, which implies less available network capacity.
The base station (e.g., eNB) of the Radio Access Network (RAN) is in the best position to trigger voice codec rate adaptation. Thus, an eNB-assisted (or RAN-assisted) codec rate adaptation solution should be considered. In order to support eNB-assisted codec rate adaptation, one of the main questions to consider is if the eNB needs to have the information on the specific codec rates for each type of supported codec. If we assume the eNB has specific information about the codec rates, we should also consider if the eNB would also need to know the codec type, the frame aggregation, the redundancy level, and the redundancy offset. This would imply the eNB could essentially serve as the end point for codec rate adaptation in place of the user equipment (UE) device.
However, if the eNB only has the codec rate information, it is unclear how much weight the UE device should give to the eNB's recommended codec rate as one of the inputs to the UE device's application layer. Note that traditionally eNBs do not handle any application layer signaling. Rather, they only handle the Access Stratum (AS) part of the LTE system. Adding application layer signaling within the eNB would drastically change the existing paradigm of how the network architecture is structured. Thus, the following examples describe techniques and system configurations that enable the eNB to facilitate rate adaptation despite not having codec rate information.
Moreover, as the UE device moves in and out of coverage, the eNB's selection of a recommended rate for the UE device should be a function of the UE device's radio condition and whether the recommended rate is applicable to the UE device when the UE device is handed over to a target eNB.
Although most of the examples discussed herein focus on VoLTE applications, any of the following examples may be modified for Video-over-LTE (ViLTE) applications.
In the interest of clarity and brevity, communication system 100 is shown as having only two base stations 102, 103. Initially, first base station 102 provides wireless services to UE device 106, and second base station 103 provides wireless services to UE device 108. However, in other examples, communication system 100 could have any suitable number of base stations. Base stations 102, 103, which are sometimes referred to as an eNodeB or eNB, communicate with the wireless user equipment (UE) devices 106, 108 by transmitting downlink signals 104, 109 to the UE devices 106, 108, respectively. Base stations 102, 103 receive uplink signals 116, 111 transmitted from the UE devices 106, 108, respectively. The UE devices 106, 108 are any wireless communication devices such as mobile phones, transceiver modems, personal digital assistants (PDAs), and tablets, for example.
Base stations 102, 103 are connected to the network through a backhaul (not shown) in accordance with known techniques. As shown in
For the example shown in
The controller 204 includes any combination of hardware, software, and/or firmware for executing the functions described herein as well as facilitating the overall functionality of the base station 102. An example of a suitable controller 204 includes code running on a microprocessor or processor arrangement connected to memory. The transmitter 206 includes electronics configured to transmit wireless signals. In some situations, the transmitter 206 may include multiple transmitters. The receiver 208 includes electronics configured to receive wireless signals. In some situations, the receiver 208 may include multiple receivers. The receiver 208 and transmitter 206 receive and transmit signals, respectively, through an antenna 210. The antenna 210 may include separate transmit and receive antennas. In some circumstances, the antenna 210 may include multiple transmit and receive antennas.
The transmitter 206 and receiver 208 in the example of
The transmitter 206 includes a modulator (not shown), and the receiver 208 includes a demodulator (not shown). The modulator modulates the signals to be transmitted as part of the downlink signals 104 and can apply any one of a plurality of modulation orders. The demodulator demodulates any signals, including uplink signals 116, received at the base station 102 in accordance with one of a plurality of modulation orders.
Returning to
The controller 216 includes any combination of hardware, software, and/or firmware for executing the functions described herein as well as facilitating the overall functionality of a UE device. An example of a suitable controller 216 includes code running on a microprocessor or processor arrangement connected to memory. The transmitter 218 includes electronics configured to transmit wireless signals. In some situations, the transmitter 218 may include multiple transmitters. The receiver 214 includes electronics configured to receive wireless signals. In some situations, the receiver 214 may include multiple receivers. The receiver 214 and transmitter 218 receive and transmit signals, respectively, through antenna 212. The antenna 212 may include separate transmit and receive antennas. In some circumstances, the antenna 212 may include multiple transmit and receive antennas.
The transmitter 218 and receiver 214 in the example of
The transmitter 218 includes a modulator (not shown), and the receiver 214 includes a demodulator (not shown). The modulator can apply any one of a plurality of modulation orders to modulate the signals to be transmitted as part of the uplink signals 116, which are shown in
In some of the examples described herein, it is assumed that base stations 102, 103 are agnostic to codec rate information, which means that the base stations 102, 103 are not aware of which bitrates match with the codec rates available to the UE devices 106, 108 in the application layer. Therefore, the base station 102 must be informed regarding which bitrates are appropriate to recommend to the UE device 106; for purposes of rate adaptation, this is an important detail since the UE device 106 cannot autonomously decide which bitrate to use without permission from the base station 102.
In operation, one or more triggering events will cause a base station 102 to determine a bitrate to recommend to the UE device 106. In some examples, the base station 102 receives a bitrate query, which is a request for an unspecified rate increase or decrease for a particular communication link (e.g., downlink 104 or uplink 116). In other examples, the bitrate query comprises a request for a specific rate, which may, in some cases, be based on a rate negotiation request from a second UE device 108. If the base station 102 is codec rate agnostic, the bitrate query will be a request for a specific bitrate rather than for a specific codec rate.
The base station 102 utilizes controller 204 to determine a bitrate to recommend to the UE device 106. The recommended bitrate takes into account, among other factors, any previously received bitrate query, the radio condition of the first UE device 106, and the current level of network congestion measured by the base station 102. Of course, any other suitable criteria may be used by the base station 102 in selecting a recommended bitrate. In some cases, the recommended bitrate is a bitrate supported by the base station 102. The bitrate recommendation, in some examples, is a recommendation for a higher rate. In other examples, the bitrate recommendation is a recommendation for a lower rate.
After determining which bitrate to recommend to the UE device 106, the base station 102 transmits, via transmitter 206 and antenna 210, the recommended bitrate to be used for a call between the first UE device 106 and a second UE device 108. The call may be a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call. The UE device 106 receives the recommended bitrate via antenna 212 and receiver 214. The recommended bitrate is represented in
In addition to the recommended bitrate, the base station 102 transmits Packet Loss Rate (PLR) threshold configuration information to the UE device 106, in some examples. The PLR threshold configuration information, which comprises a lower PLR threshold value and/or an upper PLR threshold value, may be transmitted with the recommended bitrate or in a separate transmission. The PLR threshold configuration information is represented in
The PLR is calculated at the application layer of the UE device 106 and reflects the packet errors for the application layer. Based on the PLR, the UE device 106 can determine whether the radio condition of the UE device 106 has changed sufficiently enough to require a change in bitrate. By specifying the particular PLR threshold values that should be used by the UE device 106, the base station 102, or the application layer of the UE device 106, configures the degree to which the radio condition of the UE device 106 must change in order to trigger the UE device 106 to transmit a bitrate query to the base station 102.
In response to receiving the recommended bitrate from the base station 102, the controller 216 of first UE device 106 determines whether to (1) implement (e.g., accept) the recommended bitrate, (2) reject the recommended bitrate, (3) request a different bitrate than the recommended bitrate, (4) negotiate the bitrate with second UE device 108, or (5) perform any combination of two or more of the foregoing options. If the UE device 106 chooses to initiate a bitrate negotiation with the second UE device 108 to determine a bitrate to be used for the VoLTE call between the first and second UE devices 106, 108, the first UE device 106 and the second UE device 108 use their respective transmitters 218, controllers 216, and antennas 212 to negotiate the bitrate via the application layer. This bitrate negotiation occurs via communication link 112 in
In other examples, the first UE device 106 may already know which bitrate the second UE device 108 is capable of using for the VoLTE call, and thus, no negotiation is required. Once the bitrate negotiation between the first and second UE devices 106, 108 concludes, or is skipped, the first and second UE devices 106, 108 implement a bitrate for the VoLTE call, or the first UE device 106 may determine that a bitrate query should be sent to the base station 102.
In determining whether to transmit a bitrate query, the UE device 106 determines the radio condition of the UE device 106 by measuring the PLR at the UE device 106 and through the bitrate negotiation with UE device 108. If the measured PLR is below the lower PLR threshold value, the UE device 106 may transmit a bitrate query to the base station 102. In some examples, this bitrate query is a request to decrease the bitrate used for the downlink communication link 104. However, in some cases, the UE device 106 may be configured to refrain from sending this bitrate query if the UE device 106 is already operating at the minimum Guaranteed Bit Rate (GBR).
If the measured PLR is above the upper PLR threshold value, the UE device 106 may transmit a bitrate query to the base station 102. In some examples, this bitrate query is a request to increase the bitrate used for the downlink communication link 104. However, in some cases, the UE device 106 may be configured to refrain from sending this bitrate query if the UE device 106 is already operating at the Maximum Bit Rate (MBR).
In addition to sending bitrate queries regarding the downlink communication link 104, the UE device 106 is capable of sending bitrate queries regarding the uplink communication link 116, in some examples. In these examples, the UE device 106 determines whether to the send the bitrate query based on the radio condition of the uplink communication link 116. The UE device 106 determines the radio condition of the uplink communication link 116 by the number of Hybrid Automatic Repeat Request (HARQ) retransmissions based on Acknowledgement (ACK) or Negative-ACK (NACK) signals received from the base station 102.
If the UE device 106 determines that a bitrate query should be sent to the base station 102, the UE device 106 transmits, via transmitter 218 and antenna 212, a bitrate query to the base station 102. The bitrate query can be a request for an unspecified rate increase or decrease or for a specific rate, which may be an increase or a decrease from the current rate or the recommended rate. In the examples in which the base station 102 is codec rate agnostic, any specific rate request will be a request for a specific bitrate rather than for a specific codec rate.
In addition to the rate request, the bitrate query may also include a cause value, in some examples, which indicates the reason that the UE device 106 sent the bitrate query. For example, the cause value could indicate that the bitrate query is being sent due to a change in radio condition. More specifically, the cause value could represent any of the following: “Radio Condition Change,” “Bad PLR,” “High PLR,” “Low PLR,” “Rate Negotiation Received from Peer UE Device,” or “About to Re-Negotiate Rate with Peer UE Device.” Of course, any other suitable cause values may be included in the bitrate query in order to assist the base station 102 in determining what bitrate to recommend to the UE device 106.
In other examples, the bitrate query may also include a direction of the bitrate query. For example, the bitrate query could include a request for a higher (or lower) rate than (1) a currently configured bitrate, or (2) the rate that was recommended by the base station 102 (e.g., signal 304 in
In still other examples, the bitrate query may include a cause value, as mentioned above, and a request for a specific bitrate. The combination of the cause value and the specific bitrate indicate the direction of the bitrate query (e.g., whether the request is for a rate increase or decrease). For example, the bitrate query would include the cause value and a request for a specific rate that is higher (or lower) than (1) a currently configured bitrate, or (2) the rate that was recommended by the base station 102.
In further examples, the bitrate query may also include the measured PLR. In still further examples, the bitrate query may also include an indicator of the severity of the change in radio condition (e.g., “high,” “medium,” or “low) that triggered the UE device 106 to transmit the bitrate query. The base station 102 can utilize the measured PLR and/or the indicator of the severity of the change in radio condition to determine whether to recommend a large or a small change in the bitrate in order to address the change in radio condition.
Regardless of the exact contents of the bitrate query, the UE device 106 transmits, via transmitter 218 and antenna 212, the bitrate query to the base station 102. The base station 102 receives the bitrate query via antenna 210 and receiver 208. The bitrate query is represented in
The base station 102 determines a recommended bitrate based on any number of suitable factors. After determining which bitrate to recommend to the UE device 106, the base station 102 transmits a recommended bitrate to be used for a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call between the first UE device 106 and a second UE device 108. The recommended bitrate is represented in
After receiving the recommended bitrate, the UE device 106 may elect to initiate a bitrate negotiation with the second UE device 108 to determine a bitrate to be used for the call between the first and second UE devices 106, 108. This bitrate negotiation, if it occurs, is represented in
In the example shown in
In the example shown in
At step 404, the UE device 106 receives a recommended bitrate from the base station 102. The recommended bitrate is to be used for a call between the first UE device 106 and the second UE device 108. The call can be a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call.
At step 406, the UE device 106 determines the radio condition of the UE device 106 by measuring the PLR at the UE device 106.
At step 408, if the UE device 106 determines that the measured PLR is below the lower PLR threshold value or above the upper PLR threshold value, the UE device 106 transmits a bitrate query to the base station 102. As described above, the bitrate query may be a request for an unspecified rate increase or decrease. In other examples, the bitrate query is a request for a specific bitrate. In still other examples, the bitrate query may include a cause value, a direction of the bitrate query, the measured PLR, and/or an indicator of the severity of the change in radio condition of the UE device 106.
Clearly, other embodiments and modifications of this invention will occur readily to those of ordinary skill in the art in view of these teachings. The above description is illustrative and not restrictive. This invention is to be limited only by the following claims, which include all such embodiments and modifications when viewed in conjunction with the above specification and accompanying drawings. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents.
Claims
1. A method comprising:
- receiving, at a first user equipment (UE) device, a recommended bitrate from a base station serving the first UE device, the recommended bitrate to be used for a call between the first UE device and a second UE device, the call being either a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call;
- determining a radio condition of the first UE device by measuring a Packet Loss Rate (PLR) at the first UE device; and
- if the measured PLR is below a lower PLR threshold value or is above an upper PLR threshold value, transmitting a bitrate query to the base station.
2. The method of claim 1, wherein the bitrate query includes a cause value that indicates a reason for the bitrate query.
3. The method of claim 2, wherein the cause value is an indication of a change in the radio condition of the first UE device.
4. The method of claim 1, wherein the bitrate query includes a direction of a requested bitrate change.
5. The method of claim 4, wherein a bitrate increase is determined by the inclusion of a bitrate value in the bitrate query that exceeds a currently configured bitrate value.
6. The method of claim 4, wherein a bitrate decrease is determined by the inclusion of a bitrate value in the bitrate query that is below a currently configured bitrate value.
7. The method of claim 1, wherein the bitrate query includes the measured PLR.
8. The method of claim 1, further comprising:
- configuring, by the base station, the lower PLR threshold value and the upper PLR threshold value.
9. The method of claim 1, further comprising:
- configuring, by an application layer of the first UE device, the lower PLR threshold value and the upper PLR threshold value.
10. A system comprising:
- a base station; and
- a first user equipment (UE) device being served by the base station, the first UE device comprising: a receiver configured to: receive a recommended bitrate from the base station, the recommended bitrate to be used for a call between the first UE device and a second UE device, the call being either a Voice over Long-Term Evolution (VoLTE) call or a Video over Long-Term Evolution (ViLTE) call, a controller coupled to the receiver, the controller configured to: determine a radio condition of the first UE device by measuring a Packet Loss Rate (PLR) at the first UE device, and a transmitter coupled to the controller, the transmitter configured to: transmit a bitrate query to the base station, if the measured PLR is below a lower PLR threshold value or is above an upper PLR threshold value.
11. The system of claim 10, wherein the bitrate query includes a cause value that indicates a reason for the bitrate query.
12. The system of claim 11, wherein the cause value is an indication of a change in the radio condition of the first UE device.
13. The system of claim 10, wherein the bitrate query includes a direction of a requested bitrate change.
14. The system of claim 13, wherein a bitrate increase is determined by the inclusion of a bitrate value in the bitrate query that exceeds a currently configured bitrate value.
15. The system of claim 13, wherein a bitrate decrease is determined by the inclusion of a bitrate value in the bitrate query that is below a currently configured bitrate value.
16. The system of claim 10, wherein the bitrate query includes the measured PLR.
17. The system of claim 10, wherein the base station further comprises:
- a transmitter configured to transmit a lower PLR threshold value and an upper PLR threshold value to the first UE device.
18. The system of claim 10, wherein the controller of the first UE device is further configured to:
- receive, from an application layer of the first UE device, a lower PLR threshold value and an upper PLR threshold value.
Type: Application
Filed: Feb 2, 2018
Publication Date: Dec 19, 2019
Inventors: Henry CHANG (San Diego, CA), Masato FUJISHIRO (Yokohama)
Application Number: 16/477,432