Patent Description:
A base station in some wireless communications systems (e.g., LTE or NR deployments) may transmit to a UEs using different length transmission time intervals (TTIs) that may be vary in length relative to TTIs in other communications systems. For example, a TTI in an NR system may have a shorter duration than a TTI in an LTE system. Such a shorter duration TTI may be referred to as a shortened TTI (sTTI) and may be utilized by UEs (or other devices) to support low latency communications. An sTTI may be a subset of one or more subframes that correspond to subframes of a TTI. A base station may allocate transmission resources for sTTIs to a UE that may include time resources (e.g., subframes), frequency resources (e.g., sub-carriers), and one or more component carriers (CCs) to be used for sTTI transmissions.

In some wireless communications systems, a UE may indicate to a base station that it has uplink data to transmit by sending a BSR. However, if sufficient uplink resources are not available to transmit the BSR (at least at a given time), the UE may transmit a SR requesting a grant of resources to transmit the BSR. In some aspects (e.g., low latency applications), such signaling may result in unnecessary overhead, and reduced system performance.

<NPL> and <NPL>, disclose details regarding a discussion on SR and BSR in NR.

The invention made is disclosed in the attached set of claims.

The invention made is disclosed in the embodiments relating to <FIG> and <FIG>.

A base station may transmit a grant to a user equipment (UE) that indicates uplink resources for transmission of pending data at a UE. The uplink resources may include uplink resources associated with transmission time intervals (TTIs) and/or shortened TTIs (sTTIs). A UE may identify pending data associated with a data type (e.g., low latency data, internet traffic, etc.) and transmit a scheduling request (SR) for a grant of uplink resources. As further described below, the data type of the pending data (e.g., the logic channel group identification (LCG ID) associated with a buffer status) may be indicated such that uplink resources may be granted to the UE to reduce latency (e.g., arising from buffer status report (BSR) round trip times) for low latency communications.

Latencies associated with round trip times of BSR transmissions may be reduced via a shortened (sBSR) threshold. For example, an sBSR threshold may be configured as a predefined buffer size associated with a LCG ID. In some aspects, if a buffer size of the LCG ID buffer size is below a threshold (e.g., such that sTTIs are appropriate for transmission of the pending data), base station may size the grant according to the sBSR threshold. In such aspects, the sBSR threshold sized grant may ensure the grant is large enough to handle the pending data (e.g., the sBSR threshold may be analogous to a maximum grant size associated with sTTIs that may accommodate LCG ID buffer sizes small enough to benefit from sTTI usage). In this example, an sBSR may not be transmitted at all (e.g., the round trip time for BSR transmission may be eliminated, as an sBSR threshold sized grant may always be used when sTTIs are appropriate for pending data).

Alternatively, the usage of either a sBSR or a BSR may be used to indicate whether a sBSR threshold sized grant, or a grant of a size indicated by the BSR may be requested. In some aspects, a base station may configure (e.g., via control messages) a UE to allow some bearers, traffic flows, LCG IDs, etc. to trigger sBSRs. If the buffer size of an LCG ID is above a sBSR threshold (e.g., configured by the base station), a regular BSR transmission procedure may be used, as TTIs may be more efficient for large payloads. If the buffer size of the LCG ID is below the sBSR threshold, low latency sBSR may be used (e.g., BSR may be sent over sTTI, such as sPUSCH for example). In aspects where a sBSR threshold sized grant is used in response to an sBSR transmission, round trip times associated with BSR transmission may still be reduced due to the resulting grant being set as the size of the sBSR threshold.

In some examples, an SR may include a signal containing an on/off information bit indicating whether a grant is needed for a BSR transmission. According to techniques described herein, the SR may be transmitted using physical uplink control channel (PUCCH) resources (e.g., via a TTI having a <NUM> duration). The SR may be modified to include an explicit indication of or a request for an sTTI (e.g., using the on-off information bit). Alternatively, SR and/or BSR transmission may implicitly request one or more sTTIs for transmission of pending data. For instance, an SR or a BSR may be transmitted over one or more sTTIs (e.g., via shortened PUCCH (sPUCCH) resources) that may indicate the presence of low latency uplink traffic. Such an indication may be used to request a grant for sTTI resources for the uplink traffic (e.g., rather than a TTI grant). In such aspects, the base station may transmit a grant for shortened PUSCH (sPUSCH) according to sTTIs.

Aspects of the disclosure are initially described in the context of a wireless communications system. Example BSR formats and process flows supporting improved SRs and BSRs for low latency wireless communications are then described. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to scheduling requests and buffer status reports for low latency wireless communications.

<FIG> illustrates an example of a wireless communications system <NUM> in accordance with various aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a long term evolution (LTE) (or LTE-Advanced (LTE-A)) network, or a New Radio (NR) network. In some aspects, wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (i.e., mission critical) communications, ultra-low latency (ULL) communications, etc. Transmissions between base stations <NUM> and UEs <NUM> may use sTTIs associated with low latency communications according to techniques as discussed herein.

Each base station <NUM> may provide communication coverage for a respective geographic coverage area <NUM>. Control information and data may be multiplexed on an uplink channel or downlink according to various techniques. Control information and data may be multiplexed on a downlink channel, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.

A UE <NUM> may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may also be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, a drone, or the like.

In some aspects, a UE <NUM> may also be able to communicate directly with other UEs (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol).

In some aspects, an MTC device may operate using half-duplex (one-way) communications at a reduced peak rate. MTC devices may also be configured to enter a power saving "deep sleep" mode when not engaging in active communications. In some aspects, MTC or IoT devices may be designed to support mission critical functions and wireless communications system may be configured to provide ultra-reliable and low latency communications for these functions.

Base stations <NUM> may be an example of a LTE eNB, an eLTE eNB, an NR gNB, an NR Node-B, an NR access node, and may include an access node controller (ANC).

A base station <NUM> may interface with the core network <NUM> through backhaul links <NUM> (e.g., S1, S2, NG-<NUM>, NG-<NUM>, NG-<NUM>, NG-C, NG-U etc.) and may perform radio configuration and scheduling for communication with the UEs <NUM> within an associated coverage area <NUM>. In various examples, the network devices may communicate, either directly or indirectly (e.g., through core network <NUM>), with each other over backhaul links <NUM> (e.g., X1, X2, Xn etc.) that may be wired or wireless communication links. Each base station <NUM> may also communicate with a number of UEs <NUM> through a number of other network devices, where a network device may be an example of a transmission reception point (TRP), a distributed unit (DU), a radio head (RH), a remote radio head (RRH), or a smart radio head.

In some aspects, wireless communications system <NUM> may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communications system <NUM> may employ LTE License Assisted Access (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NR technology in an unlicensed band such as the <NUM> Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, wireless devices such as base stations <NUM> and UEs <NUM> may employ listen-before-talk (LBT) procedures to ensure the channel is clear before transmitting data. In some aspects, operations in unlicensed bands may be based on a carrier aggregation (CA) configuration in conjunction with component carriers (CCs) operating in a licensed band. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, or both. Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD) or a combination of both.

Wireless communications system <NUM> may support operation on multiple cells or carriers, a feature which may be referred to as CA or multi-carrier operation. A carrier may also be referred to as a CC, a layer, a channel, etc. The terms "carrier," "component carrier," "cell," and "channel" may be used interchangeably herein. A UE <NUM> may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation.

Time intervals in LTE or NR may be expressed in multiples of a basic time unit (which may be a sampling period of Ts = <NUM>/<NUM>,<NUM>,<NUM> seconds). Time resources in LTE/LTE-A may be organized according to radio frames of length of <NUM> (Tf = 307200Ts), which may be identified by a system frame number (SFN) ranging from <NUM> to <NUM>. Each frame may include ten <NUM> subframes numbered from <NUM> to <NUM>. A subframe may be further divided into two <NUM> slots, each of which contains <NUM> or <NUM> modulation symbol periods (depending on the length of the cyclic prefix prepended to each symbol). Excluding the cyclic prefix, each symbol contains <NUM> sample periods. In some aspects the subframe may be the smallest scheduling unit, also known as a TTI. Other time units and resource configurations may be considered without departing from the scope of the disclosure.

In some aspects, wireless communications system <NUM> may utilize enhanced component carriers (eCCs). An eCC may be characterized by one or more features including: wider bandwidth, shorter symbol duration, and sTTIs. For example, an sTTI may be shorter than a subframe or may be dynamically selected (e.g., in sTTI bursts or in selected CCs using sTTIs). Selected CCs may, in some cases be associated with a different subcarrier spacing or a different numerology (e.g., type of physical resources determined based on at least the sTTI length and subcarrier spacing) than CCs associated with TTIs. In some aspects, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link). In some aspects, an eCC may utilize a different symbol duration than other CCs, which may include use of a reduced symbol duration as compared with symbol durations of the other CCs. A shorter symbol duration may be associated with increased subcarrier spacing. A device, such as a UE <NUM> or base station <NUM>, utilizing eCCs may transmit wideband signals (e.g., <NUM>, <NUM>, <NUM>, <NUM>, etc.) at reduced symbol durations (e.g., <NUM> microseconds). A TTI in eCC may consist of one or multiple symbols. In some aspects, the TTI duration (that is, the number of symbols in a TTI) may be variable. A <NUM> or NR carrier may be considered an eCC.

A UE <NUM> may trigger transmission of an SR to a base station <NUM> indicating the UE <NUM> has pending (e.g., buffered) traffic. In response to the SR, the base station <NUM> may send the UE <NUM> a grant for a BSR. A UE <NUM> may send transmissions to a base station <NUM>, such as a BSR, to indicate an amount of pending data to be sent (e.g., a buffer size). The base station <NUM> may identify the size of pending data at UE <NUM>, and may transmit a second grant to the UE <NUM> based on the pending data (e.g., buffer size). The UE <NUM> may then transmit pending data according to resources of the grant received in response to the BSR.

In some aspects, the SR may be in response to an event at the UE <NUM>. For example, a change in BSR or uplink data arrival from a logical channel group (LCG) may trigger a SR. In some examples, the SR may include a physical (PHY) layer signal (e.g., containing an on/off information bit) contained in PUCCH (e.g., PUCCH formats <NUM>/1a/1b). SRs may be configured to be sent periodically (e.g., every <NUM>-<NUM>) via radio resource control (RRC) signaling. In some aspects, the periodicity may be configured on a per-operator basis. Further, PUCCH resources (e.g., tones) for SRs may also be configured via RRC signaling.

A UE <NUM> may determine that it has uplink data to transmit, and transmit a BSR to a base station <NUM> (e.g., via a grant received in response to the transmitted SR) to obtain uplink resources for the uplink data (e.g., to obtain PUSCH for pending data). In some aspects, the UE <NUM> may utilize previously allocated PUSCH to transmit the BSR. However, there may not be enough resources available to transmit the BSR when a UE <NUM> has an opportunity to do so. As a result, the UE <NUM> may send a SR seeking an uplink grant (e.g., additional PUSCH for the BSR) from the base station <NUM> as discussed above. After receiving the BSR, a base station <NUM> may determine a size (e.g., in number of bits) of a second grant for the UE <NUM> based on the BSR. Upon receiving the second grant, the UE <NUM> may send data using the number of bits. In some aspects, if the UE <NUM> does not have enough data to fill the all the number of bits grant, the remainder may be filled via padding.

In some aspects, a BSR may refer to a one byte media access control (MAC) layer control element (CE) that indicates a LCG identification (ID) and a buffer size. A logic channel may refer to a traffic type (e.g., voice over LTE (VoLTE), internet, etc.). One or more logic channels may be grouped in to LCGs. For example, voice and internet traffic may be associated with different types of radio bearers. At the MAC layer, each bearer may be associated with a LCG ID. As such, UEs <NUM> may report buffer size separately for different traffic types via the MAC layer CE (e.g., the BSR). Each LCG ID associated with pending data may thus be indicated by separate bytes of information.

In some aspects, a transmitter, such as a UE <NUM>, may identify one or more sTTIs for transmissions of some wireless communication services (e.g., an ULL service, an ultra-reliable low-latency communication (URLLC) service, etc.). A sTTI may be identified based on a duration of a TTI associated with the first wireless service being below a threshold duration (e.g., a TTI duration of less than <NUM> may be identified as a sTTI). As an example, a <NUM> TTI may be divided into six periods (e.g., sTTIs). In some aspects, TTIs and sTTIs may overlap in time.

According to techniques described herein, wireless communications system <NUM> may support SR and BSR transmission techniques utilizing sTTIs to reduce uplink data transmission latencies (e.g., associated with ULL communications).

SRs may be transmitted using an uplink control channel (e.g., a PUCCH). Alternatively, if control channel resources are not allocated to the UE <NUM> or the control channel is not configured for a scheduling request, a random access procedure may be used by the UE <NUM> (e.g., where a random sequence or preamble is transmitted to enable the base station to identify the UE). UEs <NUM> may use random access procedures to establish a connection and communicate with a network. For example, a UE <NUM> may determine that it has data to send and use random access procedures to initiate a data transfer with a base station <NUM>. In some aspects, one or more UEs <NUM> may seek resources to send data and subsequently transmit a random access sequence or preamble to the base station. The base station <NUM> may detect the random access sequence transmissions from the one or more UEs <NUM> and assign resources for communication. Random access message transmissions may be based on the synchronization signal received from a base station <NUM>. For example, the transmission of synchronization symbols from a base station may be used by a UE <NUM> to identify timing and/or frequency resources to send the random access message.

<FIG> illustrates an example of a wireless communications system <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with various aspects of the present disclosure. Wireless communications system <NUM> includes base station <NUM>-a and UE <NUM>-a, which may be examples of aspects of a UE <NUM> as described above with reference to <FIG>. In the example of <FIG>, the wireless communications system <NUM> may support operation utilizing sTTIs associated with low latency communications according to techniques as discussed herein, although such techniques may be applied to other communication types, TTI lengths, uplink channel types, etc..

According to some aspects, UE <NUM>-a may identify pending data associated with a data type (e.g., low latency data, internet traffic, etc.) and transmit a SR for a grant <NUM> of uplink resources <NUM>. In response, base station <NUM>-a may transmit a grant <NUM> to UE <NUM>-a, indicating uplink resources <NUM> for transmission of pending data at UE <NUM>-a. As shown, uplink resources <NUM> may include sTTI resources <NUM>-a and TTI resources <NUM>-b. In some cases, sTTI resources <NUM>-a and TTI resources <NUM>-b may be associated with different time resources (e.g., subframe numerology, TTI or subframe length, etc.), frequency resources (e.g., such as subcarrier spacing, subcarrier numerology), or both. For example, TTI resources <NUM>-b may be associated with a numerology defined by the TTI length and a first subcarrier spacing, while sTTI resources <NUM>-a may be associated with a different numerology defined by the sTTI length and a second subcarrier spacing. The data type of the pending data (e.g., the LCG ID associated with a buffer status) may be indicated such that uplink resources <NUM>-a associated with sTTIs and/or uplink resources <NUM>-b associated with TTIs may be granted to UE <NUM>-a to reduce latency (e.g., arising from BSR round trip times) for some communications (e.g., ULL communications).

In some aspects, an SR may include a PHY signal containing an on/off information bit indicating whether grant is needed for a BSR transmission. Further, UE <NUM>-a may implicitly or explicitly request a sTTI for uplink transmissions (e.g., sTTI resources <NUM>-a for pending ULL data). SR and/or BSR transmission on sTTI PUCCH resources (e.g., shortened SR (sSR) and or shortened BSR (sBSR)) may implicitly request one or more sTTIs for transmission of pending data. That is, transmission of sSRs and/or sBSRs may indicate the presence of low latency uplink traffic, and may further indicate a request for a sTTI grant for the uplink traffic (e.g., compared to a TTI grant). In some aspects, UE <NUM>-a may explicitly request sTTIs by modifying the SR transmission (e.g., on <NUM> TTI PUCCH resources) to include an indication of or request for a sTTI. In the scenarios described above, base station <NUM>-a may transmit a grant <NUM> (e.g., for sPUSCH, sPUCCH, etc.) according to sTTIs.

Latencies associated with round trip times of BSR transmissions may be reduced via a sBSR threshold. For example, a sBSR threshold may be configured as a predefined buffer size associated with a LCG ID. In some aspects, if the buffer size of the LCG ID is below a threshold (e.g., such that sTTIs are appropriate for transmission of the pending data), base station <NUM>-a may size the grant according to the sBSR threshold. In such aspects, the sBSR threshold sized grant may ensure the grant is large enough to handle the pending data (e.g., the sBSR threshold may be analogous to a maximum grant size associated with sTTIs). In this example, a sBSR may not be transmitted at all (e.g., the round trip time for BSR transmission may be eliminated, as a sBSR threshold sized grant may always be used when sTTIs are appropriate for pending data).

Alternatively, the usage of either a sBSR or a BSR may be used to indicate whether a sBSR threshold sized grant, or a grant of a size indicated by the BSR may be requested. In some aspects, base station <NUM>-a may configure (e.g., via control messages) the UE <NUM>-a to allow some bearers, traffic flows, LCG IDs etc. to trigger sBSRs. If the buffer size of an LCG ID is above a sBSR threshold (e.g., configured by base station <NUM>-a), a regular BSR transmission procedure may be used. If the buffer size of the LCG ID is below the sBSR threshold, low latency sBSR may be used (e.g., BSR may be sent over sTTI, using sPUSCH, for example). In aspects where a sBSR threshold sized grant is used in response to a sBSR transmission, round trip times associated with BSR transmission may still be reduced, as the resulting grant again may always be set as the size of the sBSR threshold.

For example, pending ULL traffic at UE <NUM>-a may trigger an sSR. sSR may be transmitted on sPUCCH. Upon reception of sSR, base station <NUM>-a may provide a sPUSCH grant. According to techniques described above, when base station <NUM>-a receives an sSR, base station <NUM>-a may determine UE <NUM>-a may have pending data (e.g., buffer size) below a sBSR threshold. Therefore, base station <NUM>-a may transmit a sBSR threshold sized grant to UE <NUM>-a, which may eliminate the need for UE <NUM>-a to transmit sBSR and/or BSR, hence reducing latency associated with sBSR/BSR round trip times.

Upon reception of a sPUSCH grant after transmission of a sSR, UE <NUM>-a may prioritize usage of the grant based on the grant size in addition to the type and amount of pending data. If the grant is equal to or greater than the sBSR threshold, UE <NUM>-a may prioritize data for the grant usage such that UE <NUM>-a may not send sBSR or BSR unless the grant can accommodate all uplink data in addition to the sBSR or BSR. For example, if the grant can accommodate all the uplink traffic that is allowed to send on sPUSCH, UE <NUM>-a may prioritize data for the grant usage and may not send sBSR or BSR unless the grant can accommodate all uplink data in addition to the sBSR or BSR. In some instances, UE <NUM>-a may receive more ULL data after UE <NUM>-a sends the sSR such that the total ULL data size exceeds the sBSR threshold. If the grant can accommodate all the uplink traffic that is allowed to send on sPUSCH, UE <NUM>-a may prioritize sBSR or a BSR to use the grant, and UE <NUM>-a may include as much ULL data as possible. If the grant is smaller than the sBSR threshold and cannot accommodate all the uplink traffic that is allowed to send on sPUSCH, UE <NUM>-a may prioritize sBSR for the grant usage and include as much data as possible in the grant.

In some aspects, base station <NUM>-a may configure UE <NUM>-a to allow data from a bearer (e.g., LCG ID) to be transmitted on sTTIs only, TTIs only, or both sTTIs and TTIs. UE <NUM>-a may trigger sSR for sTTI only bearers in aspects where base station <NUM>-a configures UE <NUM>-a for sTTI data transmissions. UE <NUM>-a may trigger sSR for any bearers that can be transmitted on sTTI. That is, if a data radio bearer (DRB) is sTTI only, the bearer may be low latency. If DRB is both TTIs and sTTIs, low latency communications may be utilized. In aspects where base station <NUM>-a configures UE <NUM>-a for both sTTIs and TTIs or TTIs only, UE <NUM>-a may trigger SR. UE <NUM>-a and/or base station <NUM>-a may send a message to base station <NUM>-a to indicate which behavior described above UE <NUM>-a will use, for one or more bearers.

UE <NUM>-a may utilize multiple bearers and, in some aspects, a ULL bearer may trigger sSR for a sTTI grant and an internet (or other) bearer may trigger SR for a TTI grant. In such aspects, if sSR is triggered, any triggered SR may be canceled. Alternatively, if sSR is triggered, other triggered SR may not be canceled. If both sSR and SR are triggered, UE <NUM>-a may only send sSR. When the grant (e.g., for sPUCCH resources, for sPUSCH resources, etc.) is received, the contents of the grant may be prioritized. If the grant can accommodate the BSR which contains the non-ULL bearer buffer size information (e.g., of internet data), UE <NUM>-a may prioritize the BSR for the grant usage and as much additional data from the bearers that triggered the sSR may also be included. In other aspects, ULL data may be prioritized over ULL data. In such aspects, the BSR may be included in the grant only if space is available. In yet other aspects, if BSR can be included, UE <NUM>-a may cancel the SR, or otherwise postpone the SR to the next opportunity.

In some examples, UE <NUM>-a may transmit the sSR for ULL and the SR for non-ULL simultaneously during a subframe. If PUCCH is of a certain format (e.g., PUCCH format 1a/1b, etc.) sSR for ULL may take precedence over SR for non-ULL (e.g., which may be dropped). If PUCCH is of other formats (e.g., formats <NUM>/<NUM>/<NUM>), UE <NUM>-a may transmit both or only sSR for ULL.

<FIG> illustrates an example of a BSR format <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with various aspects of the present disclosure. In some cases, BSR format may refer to an example of a 3GPP TS. <NUM> LTE frame. Techniques described with reference to BSR format <NUM> may be utilized by UEs <NUM> as described above with reference to <FIG> and <FIG>. BSR format <NUM> may convey information about a buffer status (e.g., a LCG ID, buffer size). In the present example, the BSR format <NUM> may represent an octet of information (e.g., the LCG ID and buffer size may be conveyed using a byte or <NUM> bits of information). BSR format <NUM> may include a LCG ID field <NUM> and a buffer size field <NUM>. The LCG ID field <NUM> may indicate one or more logic channels associated with a traffic type (e.g., VoLTE, internet, etc.). A UE <NUM> may report the buffer size separately (e.g., individually) for different traffic types. That is, a UE <NUM> may use multiple BSR formats (e.g., similar to BSR format <NUM>) to convey information associated with different traffic types (e.g., ULL data or voice data). In such aspects, additional bytes may be used for each additional LCG ID or traffic type associated with the buffer.

<FIG> illustrates an example of a process flow <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with various aspects of the present disclosure. Process flow <NUM> includes base station <NUM>-b and UE <NUM>-b, which may be examples of aspects of a base station <NUM> or a UE <NUM> as described above with reference to <FIG> and <FIG>. At <NUM>, UE <NUM>-b may identify data of a data type (e.g., pending ULL data, etc.). In some aspects, UE <NUM>-b may further determine a data size corresponding to the pending data (e.g., the size of a buffer).

At <NUM>, UE <NUM>-b may transmit an SR for a grant of resources associated with the data type. Resources associated with different data types may have TTIs of different durations, frequencies, etc. For example, an SR for a grant of resources associated with low latency data types may request sTTI resources, while an SR for a grant of resources associated with other data types (e.g., internet) may request TTI resources. In some aspects, the SR may be transmitted using a TTI associated with a control channel (e.g., PUCCH) and the SR may indicate a sTTI associated with the data type identified in <NUM> (e.g., via sPUCCH transmission). Further, the SR may be based on a comparison between a determined data size (e.g., of the pending data) and a buffer threshold, etc..

At <NUM>, bases station <NUM>-b may transmit an uplink grant indicating a set of resources (e.g., sPUCCH resources, sPUSCH resources for low latency data, etc.) to UE <NUM>-b in response to the SR received at <NUM>. In some aspects, base station <NUM>-b may transmit an indication of a buffer threshold (e.g., that is configured by base station <NUM>-b). In some aspects, UE <NUM>-b may receive a radio bearer configuration indicating at least one radio bearer configured for communications of a first data type (e.g., low latency data), a second data type (e.g., internet traffic), or both.

In some aspects, UE <NUM>-b may transmit, using the set of resources indicated by the uplink grant, a BSR based on an identification of additional data of the data type identified at <NUM> (e.g., low latency data) or identification of additional data of a different data type.

At <NUM>, UE <NUM>-b may transmit the data (e.g., of the identified data type determined at <NUM>) to base station <NUM>-b. The data may be transmitted using the set of resources indicated by the uplink grant received at <NUM>. In aspects where additional data is identified following <NUM>, the additional data may be transmitted using the set of resources indicated by the uplink grant. In such aspects, the identified data of <NUM> and a BSR corresponding to the additional data may be prioritized. The identified data of <NUM> and the additional data may be transmitted using the resources indicated by the uplink grant according to the prioritization.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a UE <NUM> as described with reference to <FIG>. Wireless device <NUM> may include receiver <NUM>, UE communications manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to SRs and BSRs for low latency wireless communications, etc.). Information may be passed on to other components of the device. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

UE communications manager <NUM> may be an example of aspects of the UE communications manager <NUM> described with reference to <FIG>. UE communications manager <NUM> and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the UE communications manager <NUM> and/or at least some of its various sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The UE communications manager <NUM> and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices. In some examples, UE communications manager <NUM> and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, UE communications manager <NUM> and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

UE communications manager <NUM> may identify data of a first data type, transmit a scheduling request for a grant of resources associated with the first data type, where the resources associated with the first data type and resources associated with a second data type have TTIs of different durations, receive, in response to the scheduling request, an uplink grant indicating a set of resources associated with the first data type, and transmit, using the set of resources indicated by the uplink grant, the identified data of the first data type, or the BSR, or both.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a wireless device <NUM> or a UE <NUM> as described with reference to <FIG> and <FIG>. Wireless device <NUM> may include receiver <NUM>, UE communications manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

UE communications manager <NUM> may be an example of aspects of the UE communications manager <NUM> described with reference to <FIG>. UE communications manager <NUM> may also include data identifier <NUM>, SR component <NUM>, grant component <NUM>, and data transmission component <NUM>. Data identifier <NUM> may identify data of a first data type. In some aspects, the first data type may be associated with low latency communications.

SR component <NUM> may transmit a scheduling request for a grant of resources associated with the first data type, where the resources associated with the first data type and resources associated with a second data type have TTIs of different durations. In some aspects, transmitting the scheduling request includes transmitting the scheduling request using a TTI associated with a control channel of the second data type. In some aspects, the scheduling request indicates a sTTI associated with the first data type. In some aspects, transmitting the scheduling request includes transmitting the scheduling request using a control channel over a sTTI. In some aspects, the control channel may be a PUCCH. Alternatively, the control channel may be a sPUCCH. In some aspects, the resources associated with the first data type includes sPUSCH resources.

Grant component <NUM> may receive, in response to the scheduling request, an uplink grant indicating a set of resources associated with the first data type.

Data transmission component <NUM> may transmit, using the set of resources indicated by the uplink grant, the identified data of the first data type, or the BSR, or both and transmit, using the set of resources indicated by the uplink grant, additional data of the first data type or the second data type.

<FIG> shows a block diagram <NUM> of a UE communications manager <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. The UE communications manager <NUM> may be an example of aspects of a UE communications manager <NUM>, a UE communications manager <NUM>, or a UE communications manager <NUM> described with reference to <FIG>, <FIG>, and <FIG>. The UE communications manager <NUM> may include data identifier <NUM>, SR component <NUM>, grant component <NUM>, data transmission component <NUM>, data size component <NUM>, BSR component <NUM>, prioritization component <NUM>, and radio bearer component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Data identifier <NUM> may identify data of a first data type. In some aspects, the first data type may be associated with low latency communications.

SR component <NUM> may transmit a scheduling request for a grant of resources associated with the first data type, where the resources associated with the first data type and resources associated with a second data type have TTIs of different durations. In some aspects, transmitting the scheduling request includes: transmitting the scheduling request using a TTI associated with a control channel of the second data type. In some aspects, the scheduling request indicates a sTTI associated with the first data type. In some aspects, the control channel may be a PUCCH. In some aspects, transmitting the scheduling request includes: transmitting the scheduling request using a control channel over an sTTI. In some aspects, the control channel may be a sPUCCH. In some aspects, the resources associated with the first data type includes sPUSCH resources.

Data size component <NUM> may determine a data size corresponding to the identified data of the first data type, where transmission of the identified data of the first data type, or the BSR, or both is based on a comparison between the determined data size and a buffer threshold. Data size component <NUM> may receive, from a base station, an indication of the buffer threshold configured by the base station, and determine a data size corresponding to the identified data of the first data type, where transmission of the identified data of the first data type, or the BSR, or both may be based on a comparison between the determined data size and an uplink grant size.

BSR component <NUM> may transmit, using the set of resources indicated by the uplink grant, a buffer status report based on an identification of additional data of the first data type or the second data type.

Prioritization component <NUM> may prioritize the identified data of the first data type and a buffer status report corresponding to additional data of the first data type or the second data type. In some aspects, the identified data of the first data type and the additional data of the first data type or the second data type may be transmitted using the set of resource indicated by the uplink grant based on the prioritizing.

Radio bearer component <NUM> may receive, from a base station, a radio bearer configuration indicating at least one radio bearer configured for communications of the first data type, the second data type, or both.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. Device <NUM> may be an example of or include the components of wireless device <NUM>, wireless device <NUM>, or a UE <NUM> as described above, e.g., with reference to <FIG>, <FIG> and <FIG>. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including UE communications manager <NUM>, processor <NUM>, memory <NUM>, software <NUM>, transceiver <NUM>, antenna <NUM>, and I/O controller <NUM> These components may be in electronic communication via one or more busses (e.g., bus <NUM>). Device <NUM> may communicate wirelessly with one or more base stations <NUM>.

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some aspects, processor <NUM> may be configured to operate a memory array using a memory controller. In other aspects, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting SRs and BSRs for low latency wireless communications).

In some aspects, the memory <NUM> may contain, among other things, a basic input/output system (BIOS) which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.

Software <NUM> may include code to implement aspects of the present disclosure, including code to support SRs and BSRs for low latency wireless communications. Software <NUM> may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some aspects, the software <NUM> may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

In some aspects, the wireless device may include a single antenna <NUM>. However, in some aspects the device may have more than one antenna <NUM>, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

In some aspects, I/O controller <NUM> may represent a physical connection or port to an external peripheral. In some aspects, I/O controller <NUM> may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/<NUM>®, UNIX®, LINUX®, or another known operating system. In other aspects, I/O controller <NUM> may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some aspects, I/O controller <NUM> may be implemented as part of a processor. In some aspects, a user may interact with device <NUM> via I/O controller <NUM> or via hardware components controlled by I/O controller <NUM>.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a base station <NUM> as described with reference to <FIG>. Wireless device <NUM> may include receiver <NUM>, base station communications manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Base station communications manager <NUM> may be an example of aspects of the base station communications manager <NUM> described with reference to <FIG>. Base station communications manager <NUM> and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the base station communications manager <NUM> and/or at least some of its various sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The base station communications manager <NUM> and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices. In some examples, base station communications manager <NUM> and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, base station communications manager <NUM> and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

Base station communications manager <NUM> may receive, from a UE, a scheduling request for a grant of resources associated with a first data type, where the resources associated with the first data type and resources associated with a second data type have TTIs of different durations, determine, in response to the scheduling request, a set of resources associated with the first data type, and transmit, to the UE, an uplink grant that indicates the determined set of resources.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a wireless device <NUM> or a base station <NUM> as described with reference to <FIG> and <FIG>. Wireless device <NUM> may include receiver <NUM>, base station communications manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Base station communications manager <NUM> may be an example of aspects of the base station communications manager <NUM> described with reference to <FIG>. Base station communications manager <NUM> may also include SR component <NUM>, resource component <NUM>, and uplink grant component <NUM>.

SR component <NUM> may receive, from a UE, a scheduling request for a grant of resources associated with a first data type, where the resources associated with the first data type and resources associated with a second data type have TTIs of different durations. In some aspects, receiving the scheduling request includes: receiving the scheduling request via a TTI associated with a control channel of the second data type. In some aspects, the scheduling request indicates a sTTI associated with the first data type. In some aspects, the control channel may be a PUCCH. In some aspects, receiving the scheduling request includes: receiving the scheduling request via a control channel over a sTTI. In some aspects, the control channel may be a sPUCCH. In some aspects, the first data type may be associated with low latency communications.

Resource component <NUM> may determine, in response to the scheduling request, a set of resources associated with the first data type. In some aspects, the determined set of resources includes sPUSCH resources.

Uplink grant component <NUM> may transmit, to the UE, an uplink grant that indicates the determined set of resources.

<FIG> shows a block diagram <NUM> of a base station communications manager <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. The base station communications manager <NUM> may be an example of aspects of a base station communications manager <NUM> described with reference to <FIG>, <FIG>, and <FIG>. The base station communications manager <NUM> may include SR component <NUM>, resource component <NUM>, uplink grant component <NUM>, data reception component <NUM>, BSR component <NUM>, grant size component <NUM>, threshold component <NUM>, and radio bearer component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

SR component <NUM> may receive, from a UE, a scheduling request for a grant of resources associated with a first data type, where the resources associated with the first data type and resources associated with a second data type have TTIs of different durations. In some aspects, receiving the scheduling request includes receiving the scheduling request via a TTI associated with a control channel of the second data type. In some aspects, the scheduling request indicates a sTTI associated with the first data type. In some aspects, the control channel may be a PUCCH. In some aspects, receiving the scheduling request includes receiving the scheduling request via a control channel over a sTTI. In some aspects, the control channel may be a sPUCCH. In some aspects, the first data type may be associated with low latency communications.

Data reception component <NUM> may receive, from the UE, data of the first data type via the determined set of resources.

BSR component <NUM> may receive, via the determined set of resources, a buffer status report for additional data of the first data type or the second data type.

Grant size component <NUM> may determine an uplink grant size based on a buffer threshold that is known to both the UE and base station, where the uplink grant indicates the uplink grant size. In some aspects, the uplink grant size indicates number of bits contained in the uplink grant.

Threshold component <NUM> may transmit, to the UE, an indication of a buffer threshold, where the scheduling request is based on the buffer threshold.

Radio bearer component <NUM> may transmit, to the UE, a radio bearer configuration indicating at least one radio bearer configured for communications of the first data type, the second data type, or both.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. Device <NUM> may be an example of or include the components of base station <NUM> as described above, e.g., with reference to <FIG>. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including base station communications manager <NUM>, processor <NUM>, memory <NUM>, software <NUM>, transceiver <NUM>, antenna <NUM>, network communications manager <NUM>, and inter-station communications manager <NUM>. These components may be in electronic communication via one or more busses (e.g., bus <NUM>). Device <NUM> may communicate wirelessly with one or more UEs <NUM>.

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some aspects, processor <NUM> may be configured to operate a memory array using a memory controller. In other aspects, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting SRs and BSRs for low latency wireless communications).

In some aspects, the memory <NUM> may contain, among other things, a BIOS which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.

Inter-station communications manager <NUM> may manage communications with other base station <NUM>, and may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>. In some examples, inter-station communications manager <NUM> may provide an X2 interface within an Long Term Evolution (LTE)/LTE-A wireless communication network technology to provide communication between base stations <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> for SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a UE communications manager as described with reference to <FIG>. In some examples, a UE <NUM> may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects of the functions described below using special-purpose hardware.

At block <NUM> the UE <NUM> may identify data of a first data type. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a data identifier as described with reference to <FIG>.

At block <NUM> the UE <NUM> may transmit a scheduling request for a grant of resources associated with the first data type, wherein the resources associated with the first data type and resources associated with a second data type have TTIs of different durations. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a SR component as described with reference to <FIG>.

At block <NUM> the UE <NUM> may receive, in response to the scheduling request, an uplink grant indicating a set of resources associated with the first data type. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a grant component as described with reference to <FIG>.

At block <NUM> the UE <NUM> may transmit, using the set of resources indicated by the uplink grant, the identified data of the first data type, or the BSR, or both. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a data transmission component as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> for SRs and BSRs for low latency wireless communications in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a base station communications manager as described with reference to <FIG>. In some examples, a base station <NUM> may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station <NUM> may perform aspects of the functions described below using special-purpose hardware.

At block <NUM> the base station <NUM> may receive, from a UE, a scheduling request for a grant of resources associated with a first data type, wherein the resources associated with the first data type and resources associated with a second data type have TTIs of different durations. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a SR component as described with reference to <FIG>.

At block <NUM> the base station <NUM> may determine, in response to the scheduling request, a set of resources associated with the first data type. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a resource component as described with reference to <FIG>.

At block <NUM> the base station <NUM> may transmit, to the UE, an uplink grant that indicates the determined set of resources. The uplink grant may indicate an uplink grant size (e.g., the uplink grant size may indicate a number of bits contained in the uplink grant). In some cases, the uplink grant size may be determined based on a buffer threshold that is known to both the UE and base station. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a uplink grant component as described with reference to <FIG>.

At block <NUM> the base station <NUM> may receive, from the UE, data of the first data type via the determined set of resources. The operations of block <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of block <NUM> may be performed by a data reception component as described with reference to <FIG>.

The terms "system" and "network" are often used interchangeably. A code division multiple access (CDMA) system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-<NUM>, IS-<NUM>, and IS-<NUM> standards.

In LTE/LTE-A networks, including such networks described herein, the term evolved node B (eNB) may be generally used to describe the base stations. The wireless communications system or systems described herein may include a heterogeneous LTE/LTE-A or NR network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB, next generation NodeB (gNB), or base station may provide communication coverage for a macro cell, a small cell, or other types of cell. The term "cell" may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

Base stations may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNodeB (eNB), gNB, Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area for a base station may be divided into sectors making up only a portion of the coverage area. The wireless communications system or systems described herein may include base stations of different types (e.g., macro or small cell base stations). The UEs described herein may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.

For example, an exemplary that is described as "based on condition A" may be based on both a condition A and a condition B without departing from the scope of the present disclosure.

Claim 1:
A method for wireless communications at a user equipment (<NUM>), comprising:
identifying (<NUM>, <NUM>), at the UE, pending data, wherein pending data includes data of at least one of a first data type or a second data type;
transmitting (<NUM>, <NUM>) a scheduling request for a grant of resources associated with the pending data, wherein resources associated with the first data type and resources associated with the second data type have transmission time intervals, TTIs, of different durations;
receiving (<NUM>, <NUM>), in response to the scheduling request, an uplink grant indicating a set of resources associated with the pending data; and
transmitting (<NUM>, <NUM>), using the set of resources indicated by the uplink grant at least one of the identified data of the first data type, or a buffer status report, BSR;
the method further comprising, after the receiving of the uplink grant, identifying additional data of the first type or the second type; and
transmitting, using the set of resources indicated by the uplink grant, the additional data of the first data type or the second data type, wherein transmitting comprises prioritizing the identified data of the first data type and a buffer status report corresponding to additional data of the first data type or the second data type, wherein the identified data of the first data type and the additional data of the first data type or the second data type are transmitted using the set of resources indicated by the uplink grant based at least in part on the prioritizing.