Patent Description:
Examples of such multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.

<CIT> discloses systems and methods for recommending a data rate on an uplink or downlink communication channel between the network node and a wireless device in a wireless communications system.

3GPP contribution<NPL>) discusses the merits and potential drawbacks of using RRC or MAC signaling for codec adaptation.

3GPP contribution <NPL>) discloses a set of proposed changes to Rel-<NUM> TR <NUM>, reflecting cumulative changes tentatively agreed by MTSI during the course of E-FLUS work to-date.

Certain aspects of the disclosure relate to a method for wireless communication by a user equipment (UE). The method generally includes generating a query message indicating either a requested (uplink or downlink) data rate for streaming services requiring increased data rates or a requested downlink data rate for streaming services requiring increased downlink data rates, wherein the requested increase in either the uplink or downlink data rate is indicated via a media access control (MAC) control element (CE) and sending the query message to a base station.

Certain aspects of the disclosure relate to a method for wireless communication by a network entity. The method generally includes receiving, from a user equipment (UE), a query message indicating either a requested (uplink or downlink) data rate for streaming services requiring increased data rates or a requested downlink data rate for streaming services requiring increased downlink data rates, wherein the requested increase in either the uplink or downlink data rate is indicated via a media access control (MAC) control element (CE) and processing the query message.

Certain aspects of the disclosure relate to a method for wireless communication by a user equipment (UE). The method generally includes, for streaming services, generating a query message indicating either a requested (uplink or downlink) data rate, wherein the requested (uplink or downlink) data rate is indicated via a bit rate field and one or more additional bits and sending the query message to a base station.

Certain aspects of the disclosure relate to a method for wireless communication by a network entity. The method generally includes receiving, from a user equipment (UE), for streaming services, a query message indicating a requested (uplink or downlink) data rate, wherein the requested (uplink or downlink) data rate is indicated via a bit rate field and one or more additional bits and processing the query message.

Certain aspects of the disclosure relate to a method for wireless communication by a user equipment (UE). The method generally includes generating a query message indicating either a requested data rate or a requested downlink data rate, wherein the requested uplink or downlink data rate is indicated via a media access control (MAC) control element (CE) designated for streaming services requiring increase in either the uplink or downlink data rates and sending the query message to a base station.

Certain aspects of the disclosure relate to a method for wireless communication by a network entity. The method generally includes receiving, from a user equipment (UE), a query message indicating either a requested uplink data rate or a requested downlink data rate, wherein the requested uplink or downlink data rate is indicated via a media access control (MAC) control element (CE) designated for streaming services requiring either increased uplink or downlink data rates and processing the query message.

Aspects of the present disclosure also provide various apparatuses, means, and computer readable medium corresponding to (and/or capable of performing) the operations described herein.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for enhanced streaming of uplink data.

<FIG> and <FIG> illustrate an example wireless communication network <NUM> in which aspects of the present disclosure may be performed.

For example, in the scenario of uplink streaming as shown in <FIG>, a UE 120a in the wireless communication network 100A may have a module for generation and/or transmission of an enhanced data rate query, according to one or more of various schemes presented herein. The query may be considered enhanced as it may support a requested (or recommended) bit rate significantly higher than previous supported bit rates. A base station <NUM> may perform complementary processing to process such a query transmitted by the UE 120a. Similarly, for example, in the scenario of downlink as shown in <FIG>, a UE 140a in the wireless communication network 100B may have a module for generation and/or transmission of an enhanced downlink data rate query, according to one or more of various schemes presented herein. The query may be considered enhanced as it may support a requested (or recommended) bit rate significantly higher than previous supported bit rates. A base station <NUM> may perform complementary processing to process such a query transmitted by the UE 140a.

As illustrated in <FIG> and <FIG>, the wireless communication network 100A and 100B, respectively, may include a number of base stations (BSs) <NUM> and other network entities. A BS may be a station that communicates with user equipment (UE). Each BS <NUM> may provide communication coverage for a particular geographic area. In NR systems, the term "cell" and next generation NodeB (gNB or gNodeB), NR BS, SGNB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. Similarly, in the example shown in <FIG>, the BSs 110a, 110b and 110c may be macro BSs for the macro cells 103a, 103b and 103c, respectively. The BS 110x may be a pico BS for a pico cell 103x. The BSs 110y and 110z may be femto BSs for the femto cells 103y and 103z, respectively.

Wireless communication network 100A and wireless communication network 100B may also include relay stations. Similarly, in the example shown in <FIG>, a relay station 110r may communicate with the BS 110a and a UE 140r in order to facilitate communication between the BS 110a and the UE 140r.

Wireless communication network 100A or wireless communication network 100B may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless communication network 100A or wireless communication network 100B.

Wireless communication network 100A or wireless communication network 100B may support synchronous or asynchronous operation.

The network controller <NUM> may communicate with the BSs <NUM> via a backhaul The BSs <NUM> may also communicate with one another (e.g., directly or indirectly) via wireless or wireline backhaul.

The UEs <NUM> (e.g., 120x, 120y, etc.) as shown in <FIG> or the UEs <NUM> (e.g., 140x, 140y, etc.) as shown in <FIG> may be dispersed throughout the wireless communication network 100A or wireless communication network 100B, respectively, and each UE may be stationary or mobile.

The system bandwidth may also be partitioned into sub-bands. For example, a sub-band may cover <NUM> (i.e., <NUM> resource blocks), and there may be <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> sub-bands for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM>, respectively.

Communication systems such as NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD).

In <FIG> and <FIG>, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink.

<FIG> illustrates a diagram showing examples for implementing a communications protocol stack in a RAN (e.g., such as the RAN <NUM>), according to aspects of the present disclosure. The illustrated communications protocol stack <NUM> may be implemented by devices operating in a wireless communication system, such as a <NUM> NR system (e.g., the wireless communication network <NUM>). In various examples, the layers of the protocol stack <NUM> may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device or a UE. As shown in <FIG>, the system may support various services over one or more protocols. One or more protocol layers of the protocol stack <NUM> may be implemented by the AN and/or the UE.

As shown in <FIG>, the protocol stack <NUM> is split in the AN (e.g., BS <NUM> in <FIG>). The RRC layer <NUM>, PDCP layer <NUM>, RLC layer <NUM>, MAC layer <NUM>, PHY layer <NUM>, and RF layer <NUM> may be implemented by the AN. For example, the CU-CP may implement the RRC layer <NUM> and the PDCP layer <NUM>. A DU may implement the RLC layer <NUM> and MAC layer <NUM>. The AU/RRU may implement the PHY layer(s) <NUM> and the RF layer(s) <NUM>. The PHY layers <NUM> may include a high PHY layer and a low PHY layer.

The UE may implement the entire protocol stack <NUM> (e.g., the RRC layer <NUM>, the PDCP layer <NUM>, the RLC layer <NUM>, the MAC layer <NUM>, the PHY layer(s) <NUM>, and the RF layer(s) <NUM>).

In some cases, the MAC layer <NUM> may support (generate and/or process) MAC-CEs as described herein (e.g., and illustrated in FIGs. 12A and <NUM> B).

<FIG> illustrates example components of BS <NUM> and either UE <NUM> or UE <NUM> (as depicted in <FIG> or <FIG>, respectively), which may be used to implement aspects of the present disclosure. For example, antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> may be used to perform the various techniques and methods described herein (e.g., operations shown in <FIG>, <FIG>, and <FIG>).

A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 332a through 332t. Downlink signals from modulators 332a through 332t may be transmitted via the antennas 334a through 334t, respectively.

At the UE <NUM> or <NUM>, the antennas 352a through 352r may receive the downlink signals from the base station <NUM> and may provide received signals to the demodulators (DEMODs) in transceivers 354a through 354r, respectively. Each demodulator <NUM> may condition (e.g., filter, amplify, down-convert, and digitize) a respective received signal to obtain input samples. A MIMO detector <NUM> may obtain received symbols from all the demodulators 354a through 354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor <NUM> may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide decoded data for the UE <NUM> or <NUM> to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

In a MIMO system, a transmitter (e.g., BS <NUM>) includes multiple transmit antennas 354a through 354r, and a receiver (e.g., UE <NUM> or <NUM>) includes multiple receive antennas 352a through 352r. Thus, there are a plurality of signal paths <NUM> from the transmit antennas 354a through 354r to the receive antennas 352a through 352r. Each of the transmitter and the receiver may be implemented, for example, within a UE <NUM>, a BS <NUM>, or any other suitable wireless communication device.

The use of such multiple antenna technology enables the wireless communication system to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data, also referred to as layers, simultaneously on the same time-frequency resource. The data streams may be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams with different weighting and phase shifting) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE(s) with different spatial signatures, which enables each of the UE(s) to recover the one or more data streams destined for that UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of the MIMO system is limited by the number of transmit or receive antennas, whichever is lower. In addition, the channel conditions at the UE, as well as other considerations, such as the available resources at the base station, may also affect the transmission rank. For example, the rank (and therefore, the number of transmission layers) assigned to a particular UE on the downlink may be determined based on the rank indicator (RI) transmitted from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and a measured signal-to-interference-and-noise ratio (SINR) on each of the receive antennas. The RI may indicate, for example, the number of layers that may be supported under the current channel conditions. The base station may use the RI, along with resource information (e.g., the available resources and amount of data to be scheduled for the UE), to assign a transmission rank to the UE.

The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators in transceivers 354a through 354r (e.g., for SC-FDM, etc.), and transmitted to the base station <NUM>.

On the downlink, at UE <NUM>, a receive processor <NUM> may receive and process data (e.g. for a PDCSH from a data source <NUM> of the BS). In some cases, the UE <NUM> (and processors thereof) may be used to process downlink data, for example, as part of a downlink streaming scenario shown in <FIG>.

The controllers/processors <NUM> and <NUM> may direct the operation at the BS <NUM> and the UE <NUM>, respectively. The processor <NUM> and/or other processors and modules at the BS <NUM> may perform or direct the execution of processes for the techniques described herein (e.g., operations shown in <FIG>, <FIG>, and <FIG>). The processor <NUM> and/or other processors and modules at the UE <NUM> may perform or direct the execution of processes for the techniques described herein (e.g., operations shown in <FIG>, <FIG>, and <FIG>). The memories <NUM> and <NUM> may store data and program codes for BS <NUM> and either UE <NUM> or UE <NUM>, respectively.

Certain aspects of the present disclosure provide techniques for supporting higher data rates, such as the higher data rates often associated with certain uplink streaming scenarios. Such data rates may far exceed the maximum supported bit rates of conventional recommended bit rate query mechanisms.

<FIG> illustrates an example scenario for uplink streaming, referred to as Framework for Live Uplink Streaming (FLUS), in which a source (e.g., a UE) streams media to a sink, for example, via a network entity (e.g., an eNB/gNB).

FLUS may include a mechanism for uplink streaming bit rate assistance using radio access network (RAN) signaling. For example, as illustrated in the example scenario of <FIG>, the UE (acting as the FLUS Source) may interact with the RAN whereby the FLUS Source sends, and the eNB/gNB subsequently responds to, a requested boost in uplink streaming data rate.

<FIG> illustrates an example scenario for downlink streaming whereby media content is downloaded from a network-based media server to, and upon request from, a UE-based media player. Such streaming media content may be delivered by an adaptive bit rate mechanism, such as Moving Picture Experts Group (MPEG) dynamic adaptive streaming over HTTP (MPEG-DASH) , or MPEG common media application format (MPEG-CMAF). For example, as illustrated in <FIG>, the UE's Media Session Handler function may interact with the RAN whereby the Media Session Handler sends, and the eNB/gNB subsequently responds to, a requested boost in downlink streaming data rate.

One possible mechanism for fulfilling the above-described functionality is referred to as an Access Network Bitrate Recommendation (ANBR) query/response messaging mechanism. ANBR generally refers to a conceptual message exchange which is mapped to actual message and/or content according to a RAT used for access. For example, in the case of long term evolution (LTE) and/or new radio (NR) access, an ANBR may be mapped to (e.g., correspond to) a "Recommended bit rate" media access control (MAC) Control Element (MAC-CE), and an ANBR Query maybe mapped to a "Recommended bit rate Query" MAC CE.

Currently-defined bit rate values for the ANBR MAC CE are limited in the corresponding bit rate that can be requested/recommend. For example, conventional ANBR MAC CEs were intended to support audio or audio/video conferencing applications and have a maximum value of 8000kbit/s.

It is generally expected that in both uplink streaming (e.g., FLUS) or downlink streaming (e.g., of DASH or CMAF formatted media content), the targeted uplink or downlink streaming applications are expected to support significantly higher data rates associated with High Definition (HD) or Ultra HD (UHD) video streams, associated with professionally generated video content, as well as in the case of (non-professional) user generated content, and as well as support of Extended Reality applications such as virtual reality (VR). As a result, it is expected that the upper range of recommended bit rate values to be specified in the MAC CE should be much higher than the current maximum value of <NUM> kbit/s.

For example, high-quality <NUM> degree VR and UHD-quality video streams are likely to be transmitted with a bit rate as high as <NUM> to <NUM> Mbps. Aspects of the present disclosure may support these bit rates, and even higher bit rates (e.g., up to <NUM> Gbps).

Aspects of the present disclosure provide solutions that may help support the higher data rates associated with various uplink streaming scenarios. In some cases, the solutions propose a query and response mechanism that may be considered enhanced relative to conventional query and response mechanisms.

<FIG> illustrates example operations <NUM> that may be performed by the appropriate controlling entity in UE (e.g., the FLUS Source in uplink streaming, or the Media Session Handler in downlink streaming), in accordance with aspects of the present disclosure. Operations <NUM> may be performed, for example, by UE 120a of <FIG> or by UE 140a of <FIG>.

Operations <NUM> begin, at <NUM>, by generating a query message indicating either a requested uplink or downlink data rate for streaming services requiring increased uplink or downlink data rates wherein the requested increased uplink or downlink data rate is indicated via a media access control (MAC) control element (CE). At <NUM>, the UE sends the query message to a base station.

<FIG> illustrates example operations <NUM> that may be performed by a network entity (e.g., an eNB/gNB), in accordance with aspects of the present disclosure. Operations <NUM> may be performed, for example, by BS <NUM> of <FIG> or <FIG> to receive and process a query sent by a UE in accordance with operations <NUM>.

Operations <NUM> begin, at <NUM>, by receiving, from a user equipment (UE), a query message indicating a requested uplink or downlink data rate for streaming services requiring increased uplink or downlink data rates wherein the requested increased uplink or downlink data rate is indicated via a media access control (MAC) control element (CE). At <NUM>, the network entity processes the query message.

In some cases, a UE may use one or more reserved values of an existing recommended bit rate table, such as the table shown in <FIG> for LTE or the table shown in <FIG> for NR. For example, the MAC CE in a query message may have a bit rate field that indicates one of the (previously) reserved values (e.g., <NUM>-<NUM> for the tables shown in <FIG>). While this option may be relatively straightforward to implement, in some cases, the limited number of reserved values may be insufficient to support the expected range of data rates for FLUS (at least not at a sufficient granularity). Aspects of the present disclosure, however, provide alternative options that may support the expected range of data rates at a sufficient granularity.

For example, <FIG> illustrates example operations <NUM> that may be performed by an uplink streaming source (e.g., a UE 120a of <FIG>) or by a downlink session handler (e.g., a UE 140a of <FIG>), in accordance with aspects of the present disclosure.

Operations <NUM> begin, at <NUM>, by generating a query message indicating a requested uplink or downlink data rate for streaming services, wherein the requested uplink or downlink data rate is indicated via a bit rate field and one or more additional bits. At <NUM>, the UE sends the query message to a base station.

<FIG> illustrates example operations <NUM> that may be performed by a network entity, in accordance with aspects of the present disclosure. For example, operations <NUM> may be performed by an eNB/gNB to receive and process a query sent by a UE in accordance with operations <NUM>.

Operations <NUM> begin, at <NUM>, by receiving, from a user equipment (UE), a query message indicating a requested uplink or downlink data rate for streaming services, wherein the requested uplink or downlink data rate is indicated via a bit rate field and one or more additional bits. At <NUM>, the network entity processes the query message.

As illustrated in the example MAC-CE formats shown in <FIG>, the one or more additional bits may include reserved bits (R) in a recommended bit rate MAC CE. A single (previously reserved) bit "X" may be used to indicate that a multiplier is to be applied to a value indicated by the bit rate field in the MAC CE.

In other words, the bit rate field value may correspond to one of the values in the tables shown in <FIG>, and, if the multiplier bit is set, the recommended/requested bit value may be obtained by multiplying the value in the table by the corresponding multiplier. For example, assuming a multiplier of "<NUM>" if X = <NUM>, then the actual value of the "bit rate" is 40x of the value indicated by the table. Assuming a bit rate field (index) value of <NUM>, the recommended bit rate then would be <NUM> kbit/s for LTE (per <FIG>), and <NUM> kbit/s for NR (per <FIG>).

In certain aspects, more than one bit can be used to define different "multipliers. " For example, assuming a <NUM>-bit multiplier field four values could be specified as follows:.

to be applied to the indicated bit rate by a "Bit Rate" field.

With the use of "multiplier", some of the effective bit rate values that can be signaled may be effectively duplicated. For example, when the "multiplier" is x100, setting the multiplier bit (e.g., X=<NUM>) and specifying a bit rate index of <NUM> has the same meaning as not setting the multiplier bit (X=<NUM>) and indicating a bit rate index of <NUM> in LTE. In the above example (for LTE), both settings (X=<NUM>/index=<NUM> and X=<NUM>/index=<NUM>) may indicate <NUM> kbit/s. In some cases, more than one bit can be used to define different "multipliers," while also trying to avoid duplicated possible signaled values. For example, still with a <NUM>-bit multiplier field XY where X =<NUM> representing multiplier 515x and Y=<NUM> representing 73x, both X and Y could be summed up if both bits are set (X=<NUM> and Y=<NUM>, such that XY=<NUM>). In other words, the values of XY represent the following multiplier values:.

In some cases, the multiplier(s) could be predefined in a standard specification.

In some cases, the multiplier(s) could be signaled/configured by upper layers (e.g., via RRC signaling indicating the bit rate multiplier, e.g. x40, x70, x100, x200 etc.), which may provide additional flexibility and ability to adapt to particular needs. When not configured explicitly, the multiplier can be interpreted to have a default value. This multiplier may be configured per bearer or per UE, based on a type of UE Service. If configured per bearer, then it may be applicable to one PDU session and can be part of one slice. If configured per UE, it may be part of all the PDU sessions across all slices.

In some cases, the network may configure the multiplier to be used with MAC CE formats without any change in the R bits. For example, if the multiplier is configured in this manner, the MAC CE format may be unchanged, but the interpretation of the value is updated accordingly, as described in the paragraphs above.

In some cases, the presence of a configuration (of the multiplier) can be an indication that the network supports this feature.

In some cases, a reserved bit may be used to indicate bit rate values from an extended table (e.g., extended relative to the tables shown in <FIG>). In some cases, one or more of the reserved bits (R) in the recommended bit rate MAC CE may be used to define additional bits for a "bit rate" index and extend the tables shown in <FIG>.

For example, if this extension bit X = <NUM>, then the bit rate index may be interpreted as <NUM> plus an index value indicated by the <NUM> bit "bit rate" field. This may effectively extend the bit rate field to <NUM> bits with the bit rate field value indicating the lower <NUM> bits of the <NUM> bit value. Thus, new values may be defined for indices <NUM> to <NUM>, for example, and with finer granularity.

In certain aspects, more than one bit can be used to effectively extend the "bit rate" field. For example, with a <NUM>-bit extension field, the index can be extended to as large as <NUM> (e.g., effectively allowing new values to be defined for indices <NUM> to <NUM>).

In some cases, for backward compatibility, the extension (X) bit(s) should be considered as MSBs, not LSBs. In other words, devices that only recognize the conventional bit field may still interpret the value properly.

Still, another option to accommodate increased (i.e., a wider range of) data rates is to define a new MAC CE, specifically for the purpose of uplink streaming (e.g., FLUS).

<FIG> illustrates example operations <NUM> that may be performed by an uplink streaming source (e.g., a UE 120a of <FIG> or UW 140a of <FIG>) using a new MAC-CE, in accordance with aspects of the present disclosure.

Operations <NUM> begin, at <NUM>, by generating a query message indicating a requested uplink or downlink data rate, wherein the requested uplink or downlink data rate is indicated via a media access control (MAC) control element (CE) designated for uplink or downlink streaming services requiring increased uplink or downlink data rates. At <NUM>, the UE sends the query message to a base station.

Operations <NUM> begin at <NUM>, by receiving, from a user equipment (UE), a query message indicating a requested uplink or downlink data rate, wherein the requested uplink or downlink data rate is indicated via a media access control (MAC) control element (CE) designated for uplink or downlink streaming services requiring increased uplink or downlink data rates. At <NUM>, the network entity processes the query message.

In some cases, a new MAC CE (e.g., specifically for the purpose of uplink streaming such as FLUS, or downlink streaming such as MPEG-DASH), may have a similar format to the Recommended Bit Rate MAC CE. In some examples, a bit rate value in the new MAC CE may provide an index to a table with FLUS specific values in the "bit rate" table.

In some cases, a new Logical Channel Identifier (LCID) may be defined to indicate this new type of MAC CE. In such cases, an extended LCID (eLCID), may be used.

In some cases, one of the reserved bits (R) in the recommended bit rate MAC CE (shown as "X" in the example LTE and NR MAC CE formats shown in <FIG>) may be used to point to new extended bit rate tables (e.g., new bit rate tables in TS <NUM> Table <NUM>. <NUM>-x for LTE and TS <NUM> Table <NUM>. <NUM>-x for NR). <FIG> illustrates an example of such a table.

For example, if X = <NUM>, then the bit rate index corresponds to the new table. This approach may allow new values to be defined in the new table with finer granularity. As the expected range of data rate to be covered is relatively large, fine granularity can be achieved with this option. If X = <NUM>, the bit rate index may correspond to a previously existing table.

In some cases, a different MAC CE may be used for each logical channel (LC). In such cases, multiple Bitrate Query MAC CEs are possible in one MAC transport block (TB) for different LCs. With an enhanced MAC CE, using one of the R-bit, a Single MAC CE can carry multiple LC related "Bit Rate Queries. " In such cases, the R-bit may indicate, whether the next Byte is an LC related Bit Rate Query or if this is the last Bit Rate Query.

In some cases, to preserve backward compatibility and interoperability (e.g., if the UE supports a newer version of a standard relative to a version supported by a network, or vice-versa), the UE can indicate its capability to support the new feature (i.e., support of extended bit rates in MAC CE) to the network e.g. using a UE capability signaling. Similarly, in some case, the network may indicate capability of (its support of) the new query and response mechanism.

The network may indicate its support of the extended bit rates in MAC CE by broadcast signaling such as system information block (SIB) broadcast. As an alternative, the network may use dedicated signaling to indicate the network capability. Similar to the use of a reserved bit described above, new tables may be defined for indicating extended data rates for LTE and/or NR.

In such cases, the presence of a configuration from the network may indicate that the new table is to be used, instead of (a previously) existing table. In some cases, the network may use dedicated signaling to configure use of extended bit rate MAC CE (e.g., as shown in <FIG>) for the UEs supporting extended bit rate MAC CE. In some cases, the configuration may be part of a MAC configuration (e.g., extendedBitRateMAC-CE = True). If such a flag is configured, the extended bitrate MAC CE table (e.g., as shown in <FIG>) may be used instead of (previously) existing tables. Such a flag may also implicitly serve as the indication that the network is able to support the new table (e.g., the extended bit rate MAC CE).

For example, the various processor shown in <FIG> may be configured to perform operations <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and <FIG>.

In the case of a user terminal <NUM> or <NUM> (see <FIG> or <FIG>, respectively), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus.

For example, such a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein (e.g., instructions for performing the operations described herein and illustrated in <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and <FIG>).

Claim 1:
A method for wireless communications by a wireless device (120a, 140a), comprising:
generating (<NUM>, <NUM>, <NUM>) a query message indicating a requested data rate for streaming services, wherein the requested data rate is indicated via a bit rate field and one or more additional bits, wherein the requested data rate is indicated via a media access control, MAC, control element, CE, that includes the bit rate field and the one or more additional bits, and wherein
a value of the bit rate field corresponds to a bit rate value in a bit rate table, and
the one or more additional bits indicate that a multiplier is to be applied to the requested bit rate value corresponding to the value of the bit rate field; and
sending (<NUM>, <NUM>, <NUM>) the query message to a base station.