Delay-sensitive uplink transmissions

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can transmit an uplink request to a base station, the uplink request including an indication that data associated with the uplink request is delay sensitive. The UE can receive, from the base station, an uplink grant associated with a logical channel group, the logical channel group including a logical channel for the data, where the logical channel group is associated with a higher priority than one or more other logical channel groups. The UE can transmit, to the base station, the data using the logical channel based at least in part on the uplink grant. Numerous other aspects are provided.

Description

[0001] open field

[0002] Various aspects of this disclosure generally relate to wireless communication, and specifically to techniques and apparatus for transmitting and receiving delay-sensitive uplink transmissions.

[0003] background

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include 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, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include several base stations (BSs) capable of supporting communication between several user equipments (UEs). UEs can communicate with the base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5G B-node, etc.

[0006] The multiple access technologies mentioned above have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the city, country, region, and even global levels. New Radio (NR) (also known as 5G) is an enhancement set to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL), and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to grow.

[0007] Overview

[0008] In some aspects, a wireless communication method performed by a user equipment (UE) includes: transmitting an uplink request to a base station, the uplink request including an indication that data associated with the uplink request is latency-sensitive; receiving from the base station an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and transmitting the data to the base station using the logical channels, at least in part based on the uplink grant.

[0009] In some aspects, a wireless communication method performed by a base station includes: receiving an uplink request from a UE, the uplink request including an indication that data associated with the uplink request is latency-sensitive; transmitting to the UE an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and receiving data from the UE using the logical channels, at least in part, based on the uplink grant.

[0010] In some aspects, a UE for wireless communication includes a memory and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: transmit an uplink request to a base station, the uplink request including an indication that data associated with the uplink request is latency-sensitive; receive from the base station an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and transmit data to the base station using the logical channels, at least in part based on the uplink grant.

[0011] In some aspects, a base station for wireless communication includes a memory and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive an uplink request from a UE, the uplink request including an indication that data associated with the uplink request is latency-sensitive; transmit to the UE an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and receive data from the UE using the logical channels, at least in part based on the uplink grant.

[0012] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a UE, cause the UE to: transmit an uplink request to a base station, the uplink request including an indication that data associated with the uplink request is latency-sensitive; receive from the base station an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and transmit data to the base station using the logical channels, at least in part based on the uplink grant.

[0013] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a base station, cause the base station to: receive an uplink request from a UE, the uplink request including an indication that data associated with the uplink request is latency-sensitive; transmit to the UE an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and receive data from the UE using the logical channels, at least in part based on the uplink grant.

[0014] In some aspects, an apparatus for wireless communication includes: means for transmitting an uplink request to a base station, the uplink request including an indication that data associated with the uplink request is latency-sensitive; means for receiving from the base station an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and means for transmitting the data to the base station using the logical channels, at least in part based on the uplink grant.

[0015] In some aspects, an apparatus for wireless communication includes: means for receiving an uplink request from a UE, the uplink request including an indication that data associated with the uplink request is latency-sensitive; means for transmitting to the UE an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; and means for receiving data from the UE using the logical channels, at least in part, based on the uplink grant.

[0016] The aspects generally include, as substantially described herein with reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, base stations, wireless communication equipment, and / or processing systems.

[0017] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described thereafter. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not for defining limitations on the claims. Brief description of the attached diagram

[0019] To gain a more detailed understanding of the features described above in this disclosure, reference can be made to various aspects of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. Identical reference numerals in different drawings may identify the same or similar elements.

[0020] Figure 1 This is a diagram illustrating examples of wireless networks according to various aspects of this disclosure.

[0021] Figure 2 This is a diagram illustrating an example of communication between a base station and a UE in a wireless network according to various aspects of this disclosure.

[0022] Figure 3A and 3B This is a diagram illustrating examples of delay sensitivity according to various aspects of this disclosure.

[0023] Figure 4 This is a diagram illustrating an example of uplink transmission that is sensitive to transmission and reception delays according to various aspects of this disclosure.

[0024] Figure 5A and 5B This is a diagram illustrating an example of a buffer status report (BSR) associated with delay-sensitive uplink transmissions according to various aspects of this disclosure.

[0025] Figure 6 and 7 This is a diagram illustrating an example process associated with transmission and reception delay-sensitive uplink transmission according to various aspects of this disclosure.

[0026] Figure 8 and 9 This is a block diagram of an example device for wireless communication according to various aspects of this disclosure.

[0027] Detailed description

[0028] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as being limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

[0029] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and explained in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] It should be noted that although the aspects herein may be described using terms commonly associated with 5G or NR radio access technology (RAT), the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0031] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to various aspects of this disclosure. The wireless network 100 may be a 5G (NR) network, an LTE network, etc., or may include elements thereof. The wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, B-node, gNB, 5G B-node (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0032] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with a service subscription. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1In the example shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” are used interchangeably herein.

[0033] In some respects, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.).

[0034] The wireless network 100 may also include a relay station. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting those data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay, etc.

[0035] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0036] Network controller 130 can be coupled to a set of BSs and can provide coordination and control over these BSs. Network controller 130 can communicate with each BS via backhaul. These BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0037] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), entertainment device (e.g., music or video device, or satellite radio), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0038] Some UEs can be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network) for example, via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components, memory components, etc. In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, etc.

[0039] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0040] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this scenario, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as performed by base station 110.

[0041] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1) and / or an operating band with a second frequency range (FR2), where the first frequency range (FR1) spans from 410 MHz to 7.125 GHz and the second frequency range (FR2) spans from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency bands. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz band." Similarly, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to as the "millimeter wave" band. Therefore, unless otherwise stated, it should be understood that, if used herein, the terms "sub-6 GHz" and the like can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that, if used herein, the terms "millimeter wave" and the like can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25 GHz). It is conceivable that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] As indicated above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0043] Figure 2This is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to various aspects of this disclosure. The base station 110 may be equipped with T antennas 234a to 234t, while the UE 120 may be equipped with R antennas 252a to 252r, wherein generally T ≥ 1 and R ≥ 1.

[0044] At base station 110, transmit processor 220 can receive data destined for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on the channel quality indicator (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.), and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0045] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine the Reference Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Received Quality (RSRQ), Channel Quality Indicator (CQI), and so on. In some respects, one or more components of the UE 120 may be included in the housing 284.

[0046] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0047] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, CQI, etc.). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded by TX MIMO processor 266 where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein, for example, as referenced Figure 4-7 As described.

[0048] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule UE 120 for downlink and / or uplink communication. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein, for example, as referenced Figure 4-7 As described.

[0049] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with transmission and reception delay-sensitive uplink transmissions, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 6 Process 600 Figure 7 The operation of process 700 and / or other processes as described herein. Memory 242 and 282 may store data and program code for use by base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include: a non-transitory computer-readable medium storing one or more instructions (e.g., code, program code, etc.) for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, interpretation, etc.), the one or more processors, UE 120, and / or base station 110 may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 6 Process 600 Figure 7 The process 700, and / or other processes as described herein. In some respects, the execution instructions may include run instructions, translate instructions, compile instructions, interpret instructions, etc.

[0050] In some aspects, UE (e.g., UE 120, Figure 8 The device 800, etc., may include: a means for transmitting information to a base station (e.g., base station 110, etc.). Figure 9 The apparatus includes: means for transmitting an uplink request (such as device 900), the uplink request including an indication that data associated with the uplink request is latency-sensitive; means for receiving from a base station an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; means for transmitting data to a base station using the logical channels, at least in part based on the uplink grant; and so on. In some aspects, such means may include a combination of... Figure 2 One or more components of the UE120 described herein, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0051] In some aspects, base stations (e.g., base station 120, Figure 9 The device 900, etc., may include: a means for receiving signals from a UE (e.g., UE120, etc.). Figure 8 The apparatus (such as device 800) includes means for receiving an uplink request, the uplink request including an indication that data associated with the uplink request is latency-sensitive; means for transmitting to a UE an uplink grant associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; means for receiving data from the UE using the logical channels, at least in part based on the uplink grant; and so on. In some aspects, such means may include a combination of Figure 2 One or more components of the described base station 110, such as antenna 234, DEMOD 232, MIMO detector 236, receiver processor 238, controller / processor 240, transmitter processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.

[0052] although Figure 2 The boxes in the diagram are interpreted as different components, but the functions described above with respect to these boxes can be implemented by a single hardware component, software component, or combination of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0053] As indicated above, Figure 2This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0054] Figure 3A This is a diagram illustrating example 300 of the delay sensitivity according to various aspects of this disclosure. For example... Figure 3A As shown, source device 305a can transmit delay-sensitive messages to target device 305b. In some respects, source device 305a and target device 305b can communicate on a wireless network (such as wireless network 100).

[0055] like Figure 3A As shown, when the network is working ( Figure 3A If the network is not working (indicated by "Running"), the message can be successfully transmitted. Figure 3A (This is indicated as "Out of Service"), messages may fail to receive, for example, when the target device 305b is unable to receive a message due to low signal strength, etc. Therefore, when the target device 305b receives a message, the network or other communication services may experience an uptime period, while when the target device 305b loses or otherwise fails to receive a message, the network or other communication services may experience an downtime period.

[0056] The applications executed by the source device 305a and / or the target device 305b can be latency-sensitive. Accordingly, for a specific operation, messages can be time-sensitive, such that if a message reception deadline is not met, the application transitions to an downtime or fault state. For example... Figure 3A As shown, the deadline can be indicated by the lifetime between the last received message and the transition to an downtime or fault state. The lifetime can be a period of time or the number of messages that the target device 305b incorrectly receives (e.g., the target device 305b cannot decode) or does not receive (e.g., indicated by a negative acknowledgment (NACK) signal from the target device 305b).

[0057] As indicated above, Figure 3A This is provided as an example. Other examples may differ from the one provided. Figure 3A The example described.

[0058] Figure 3B This is a diagram illustrating example 350 of the delay sensitivity according to various aspects of this disclosure. For example... Figure 3B As shown, application 355a on the source device can transmit latency-sensitive messages to target application 355b on the target device. In some respects, source application 355a and target application 355b can communicate on a wireless network (such as wireless network 100).

[0059] like Figure 3BAs shown, in a strict use case, source application 355a and / or target application 355b can be latency-sensitive. Accordingly, the lifetime can be a delivery interval (e.g., the cycle time for cyclical traffic between source application 355a and target application 355b, etc.) or a single failed message. In some aspects, target application 355b and / or source application 355a can take into account the end-to-end latency (“E2E latency”) between the source application 355a transmitting a message and the target application 355b receiving that message in determining the lifetime associated with strict latency sensitivity.

[0060] The base station can know when an application executed by the UE is latency-sensitive for downlink communication. However, the base station may not know when an application is latency-sensitive for uplink communication. Consequently, the base station may be unable to grant uplink permission to the UE, and thus latency-sensitive applications on the uplink may transition to an inactive or fault state. The application may then consume additional processing and / or network resources to transition out of the inactive or fault state after uplink permission is granted to the UE.

[0061] The technologies and apparatus described herein allow UEs (e.g., UE 120, Figure 8 Device 800, etc.) transmits data to the base station (e.g., base station 110, etc.). Figure 9 The device 900, etc., indicates that the uplink request is associated with one or more latency-sensitive messages. Accordingly, UE 120 and base station 110 can reduce the latency-sensitive uplink communication latency (e.g., associated with lifetime). Additionally, in some aspects, UE 120 can request uplink permission without a BSR, and base station 110 can grant uplink permission without a BSR. Accordingly, UE 120 and base station 110 can further reduce the latency and signaling overhead for latency-sensitive uplink communication.

[0062] As indicated above, Figure 3B This is provided as an example. Other examples may differ from the one provided. Figure 3B The example described.

[0063] Figure 4 This is a diagram illustrating an example 400 associated with a transmission and reception delay-sensitive uplink transmission according to various aspects of this disclosure. (See diagram for example.) Figure 4 As shown, Example 400 includes communication between base station 110 and UE 120. In some aspects, base station 110 and UE 120 may be included in a wireless network (such as wireless network 100).

[0064] like Figure 4As shown, an event can trigger UE 120 to request uplink permission from base station 110. For example, an application executed by UE 120 may have data to transmit to base station 110 (e.g., to transmit to a remote server and / or other destination using wireless network 100 including base station 110) and request UE 120's modem, other hardware and / or other software to establish an uplink channel for transmitting data.

[0065] In some aspects, UE 120 can transmit an uplink request, and base station 110 can receive the uplink request, which includes an indication that the data associated with the uplink request is latency-sensitive. UE 120 can transmit the uplink request at least in part based on the aforementioned triggering event. In some aspects, the data may have an associated time-to-live (e.g., as described above in conjunction with...). Figure 3A and 3B (As described).

[0066] As shown in conjunction with reference numeral 405 in the accompanying drawings, an uplink request may include a scheduling request. In some aspects, a scheduling request may be associated with a first data structure that differs from a second data structure associated with an uplink request for non-latency-sensitive data. For example, a scheduling request may be a schedulingRequestIDForTR (scheduling request ID for TR) data structure (e.g., as defined in 3GPP specifications, etc.), which differs from a schedulingRequestID (scheduling request ID) data structure (e.g., as defined in 3GPP specifications, etc.). In some aspects, the first and second data structures may have the same format but remain different in classification.

[0067] In some respects, a scheduling request can be a single bit indicating whether the request is affirmative or negative. Alternatively, a scheduling request can include multiple bits. Accordingly, the scheduling request can indicate whether the data is latency-sensitive, the size associated with the data, the remaining time for data transmission, etc. For example, one bit can indicate whether the scheduling request is affirmative or negative, another bit can indicate whether the data is latency-sensitive, one or more additional bits can indicate the size of the data, and one or more additional bits can indicate the remaining time for data transmission (e.g., as combined above). Figure 3A and 3B The remaining time of the described survival time, etc.

[0068] In some aspects, a scheduling request may include two or more bits indicating whether the data is latency-sensitive and the relative size associated with the data. For example, a scheduling request "00" may indicate a negative scheduling request, a scheduling request "11" may indicate a positive scheduling request with no latency sensitivity, a scheduling request "01" may indicate a positive scheduling request for small-sized data with latency sensitivity (e.g., less than 1 MB), and a scheduling request "10" may indicate a positive scheduling request for large-sized data with latency sensitivity (e.g., more than 1 MB). Additionally or alternatively, a scheduling request may include two or more bits indicating the degree of latency sensitivity associated with the data. For example, a scheduling request "00" may indicate a negative scheduling request, a scheduling request "11" may indicate a positive scheduling request with no latency sensitivity, a scheduling request "01" may indicate a positive scheduling request for data with high latency sensitivity (e.g., lifetime less than 10 ms), and a scheduling request "10" may indicate a positive scheduling request for data with low latency sensitivity (e.g., lifetime greater than 10 ms).

[0069] In another example, scheduling request "000" can indicate a negative scheduling request, scheduling request "100" can indicate a positive scheduling request with no latency sensitivity, scheduling request "001" can indicate a positive scheduling request for data with high latency sensitivity (e.g., lifetime less than 10ms, etc.) and small size (e.g., less than 1MB, etc.), scheduling request "010" can indicate a positive scheduling request for data with high latency sensitivity and medium size (e.g., between 1MB and 5MB, etc.), scheduling request "011" can indicate a positive scheduling request for data with high latency sensitivity and large size (e.g., greater than 5MB, etc.), scheduling request "101" can indicate a positive scheduling request for data with low latency sensitivity (e.g., lifetime greater than 10ms, etc.) and small size, scheduling request "110" can indicate a positive scheduling request for data with low latency sensitivity and medium size, and scheduling request "111" can indicate a positive scheduling request for data with low latency sensitivity and large size.

[0070] In another example, scheduling request "000" can indicate a negative scheduling request, scheduling request "100" can indicate a positive scheduling request with no latency sensitivity, scheduling request "001" can indicate a positive scheduling request for data with a small size (e.g., less than 1MB) and low latency sensitivity (e.g., lifetime greater than 20ms), scheduling request "010" can indicate a positive scheduling request for data with a small size and medium latency sensitivity (e.g., lifetime between 10ms and 20ms), scheduling request "011" can indicate a positive scheduling request for data with a small size and high latency sensitivity (e.g., lifetime less than 10ms), scheduling request "101" can indicate a positive scheduling request for data with a large size (e.g., greater than 1MB) and low latency sensitivity, scheduling request "110" can indicate a positive scheduling request for data with a large size and medium latency sensitivity, and scheduling request "111" can indicate a positive scheduling request for data with a large size and high latency sensitivity. Accordingly, based at least in part on the number of bits included in the scheduling request, UE 120 may indicate the relative delay sensitivity in two, three, four, and / or more bins, and / or the relative size associated with the data in two, three, four, and / or more bins.

[0071] In some respects, scheduling requests can be encoded according to a Physical Uplink Control Channel (PUCCH) format comprising two or fewer bits. For example, a scheduling request can be encoded according to PUCCH format 0 or PUCCH format 1 for uplink control information (UCI) (e.g., as defined in 3GPP specifications, etc.). Alternatively, scheduling requests can be encoded according to a PUCCH format comprising more than two bits. For example, a scheduling request can be encoded according to PUCCH format 2, PUCCH format 3, or PUCCH format 4 for uplink control information (UCI) (e.g., as defined in 3GPP specifications, etc.) and / or according to a new PUCCH format (e.g., as defined in 3GPP specifications, etc.).

[0072] In any of the aspects described above, a scheduling request may be associated with a Logical Channel (LCH). As used herein, an LCH may be a channel between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer that facilitates downlink communication from base station 110 to UE 120 and uplink communication from UE 120 to base station 110. An LCH may reside in the control plane and carry control information, or it may reside in the user plane and carry data.

[0073] As an alternative to a scheduling request, an uplink request may include a BSR. For example, UE 120 may transmit a BSR after receiving uplink grant for a BSR from base station 110. The BSR may indicate that the data associated with the uplink request is latency-sensitive, as described below. Figures 5A-5B As described.

[0074] As shown in conjunction with reference numeral 410, base station 110 can transmit uplink permission associated with a logical channel group (LCG) that includes an LCH for data, and UE 120 can receive this uplink permission. As used herein, an LCG can group LCHs together so that base station 110 and UE 120 can reduce overhead by using indexes for LCGs rather than individual LCHs. In some respects, the LCG is associated with a higher priority than one or more other LCGs. For example, each LCH can be associated with two LCGs, one of which is associated with a higher priority and is used when the data intended for that LCH is latency-sensitive.

[0075] In some respects, base station 110 can transmit uplink grants without receiving a BSR from UE 120. Accordingly, the size of the uplink grant may be at least partially based on the size associated with data previously transmitted using that LCH. For example, base station 110 may determine the average and / or median size of one or more previous uplink transmissions on the LCH and / or LCG with higher priority. Accordingly, base station 110 can provide uplink grants with sizes at least partially based on that average and / or median size.

[0076] As shown in conjunction with reference numeral 415, using this LCH and at least partially based on uplink permission, UE 120 can transmit data and base station 110 can receive that data. For example, UE 120 can transmit data on a PUCCH within a higher-priority LCG. Figure 4 As further shown, UE 120 can reuse data at least in part based on the LCH and the higher priority based on the LCG.

[0077] In some respects, data can be associated with periodic uplink transmissions from UE 120. For example, an application can schedule periodic transmissions using the wireless network 100, including base station 110, to remote servers and / or other entities. Accordingly, base station 110 can use the average and / or median size of the periodic uplink transmissions to determine the size of the uplink grant.

[0078] By using combination Figure 4According to the described technology, UE 120 can reduce the waiting time for receiving uplink permission from base station 110. Furthermore, UE 120 can transmit data to base station 110 without transmitting BSR, thereby further reducing the waiting time.

[0079] As indicated above, Figure 4 This is provided as an example. Other examples may differ from the one provided. Figure 4 The example described.

[0080] Figures 5A-5B These are illustrations of examples 500 and 550 associated with a BSR for delay-sensitive uplink transmission according to various aspects of this disclosure. Figure 5A As shown, Example 500 is a short BSR, which includes one bit to indicate that the data associated with the short BSR is latency-sensitive. Similarly, Example 550 is a long BSR, which includes one or more bits to indicate that some or all of the data associated with the long BSR is latency-sensitive.

[0081] like Figure 5A As shown, a short BSR may include an LCG (e.g., an LCG with higher priority, as described above). Figure 4 The identifier (e.g., index, etc.) of the BSR. Additionally, the short BSR may include a bit to indicate whether the data associated with that BSR is latency-sensitive (e.g., a time-to-live indicator or STI, such as...). Figure 5A (As shown).

[0082] In some respects, this bit may be included in the first bit reserved for the buffer size, so that the buffer size bit is coarse. Alternatively, the table defining the buffer size for the BSR (e.g., as provided in 3GPP specifications) may be adjusted to allow space in the buffer size bit for indicating whether the data associated with the BSR is latency-sensitive.

[0083] like Figure 5B As shown, a long BSR may include identifiers of multiple LCGs (e.g., indices, etc.) (e.g., LCG0, LCG1, LCG2, LCG3, LCG4, LCG5, LCG6, LCG7, etc.). Figure 5B (As shown). Additionally, the long BSR may include one bit for each LCG to indicate whether the data associated with that LCG is latency-sensitive (e.g., a time-to-live indicator or STI, such as...). Figure 5B (As shown).

[0084] As a supplement or replacement to the aforementioned bits, UE 120 may use parameters configured using Radio Resource Control (RRC) to indicate that the data associated with the BSR is latency-sensitive. For example, UE 120 may include LCGIDforTR (e.g., as defined by 3GPP specifications, etc.) and / or another similar parameter to indicate that the LCG identified by the BSR is used for latency-sensitive data.

[0085] By using combination Figures 5A-5B According to the described technique, UE 120 can reduce the waiting time for receiving uplink permission from base station 110. Additionally, UE 120 can use BSR to indicate the latency sensitivity of non-periodic or otherwise unpredictable traffic volumes.

[0086] As indicated above, Figures 5A-5B This is provided as an example. Other examples may differ from the one provided. Figures 5A-5B The example described.

[0087] Figure 6 This is a diagram illustrating, for example, an example process 600 performed by a UE according to various aspects of this disclosure. Example process 600 is wherein a UE (e.g., UE 120, ...) is... Figure 8 Examples of devices (such as 800) performing operations associated with uplink transmissions that are sensitive to transmission delays.

[0088] like Figure 6 As shown, in some aspects, process 600 may include sending data to a base station (e.g., base station 110, ...). Figure 9 The device 900, etc., transmits an uplink request, which includes an indication that the data associated with the uplink request is latency-sensitive (box 610). For example, the UE (e.g., using...) transmits an uplink request. Figure 8 The transmission component 804 depicted can transmit an uplink request to the base station, which includes an indication that the data associated with the uplink request is latency-sensitive, as described above.

[0089] like Figure 6 As further shown, in some aspects, process 600 may include receiving uplink permission from a base station associated with a logical channel group, which includes logical channels for the data (block 620). For example, a UE (e.g., using...) Figure 8 The receiving component 802 depicted can receive uplink permission associated with a logical channel group from the base station, the logical channel group including logical channels for the data, as described above. In some aspects, this logical channel group is associated with a higher priority than one or more other logical channel groups.

[0090] like Figure 6As further shown, in some aspects, process 600 may include transmitting data to the base station using the logical channel, at least in part based on the uplink permission (block 630). For example, a UE (e.g., using transmission component 804) may transmit data to the base station using the logical channel, at least in part based on the uplink permission, as described above.

[0091] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0092] In the first respect, the data has an associated lifespan.

[0093] In the second aspect, either alone or in combination with the first aspect, uplink requests include scheduling requests.

[0094] In the third aspect, either alone or in combination with one or more of the first and second aspects, the scheduling request is associated with a first data structure, which is different from the second data structure associated with the uplink request for non-latency-sensitive data.

[0095] In the fourth aspect, the scheduling request is associated with the logical channel, either alone or in combination with one or more of the first to third aspects.

[0096] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the scheduling request comprises multiple bits.

[0097] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the scheduling request indicates at least one of the following: that the data is delay-sensitive, the size associated with the data, and the remaining time available for transmitting the data.

[0098] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the scheduling request includes two or more bits that indicate whether the data is latency-sensitive and the relative size associated with the data.

[0099] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the scheduling request includes two or more bits that indicate the degree of latency sensitivity associated with the data.

[0100] In the ninth aspect, either alone or in combination with one or more of the first through eighth aspects, the scheduling request is encoded according to a PUCCH format comprising two or fewer bits (e.g., using...). Figure 8 The encoding component 808 is depicted in the text.

[0101] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the scheduling request is encoded according to a PUCCH format comprising two or more bits (e.g., using encoding component 808).

[0102] In the eleventh aspect, data is transmitted to the base station, either alone or in combination with one or more of the first to tenth aspects, without transmitting the BSR.

[0103] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the size of the uplink permission is at least partially based on the size associated with the data previously transmitted using that logical channel.

[0104] In the thirteenth aspect, the data is associated with periodic uplink transmissions from the UE, either alone or in combination with one or more of the first to twelfth aspects.

[0105] In the fourteenth aspect, uplink requests include BSRs, either alone or in combination with one or more of the first to thirteenth aspects.

[0106] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the BSR includes a parameter indicating that the data is latency-sensitive.

[0107] In the sixteenth aspect, this parameter is configured using RRC, either alone or in combination with one or more of the first to fifteenth aspects.

[0108] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the BSR includes at least one bit indicating that the data is delay-sensitive.

[0109] In the eighteenth aspect, the at least one bit is included, alone or in combination with one or more of the first to seventeenth aspects, together with the buffer size indicated in the BSR.

[0110] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 600 can be executed in parallel.

[0111] Figure 7 This is a diagram illustrating, for example, an example process 700 performed by a base station according to various aspects of this disclosure. Example process 700 is wherein a base station (e.g., base station 110, ...) is... Figure 9 Examples of devices (such as 900) performing operations associated with receiving delay-sensitive uplink transmissions.

[0112] like Figure 7 As shown, in some aspects, process 700 may include data from a UE (e.g., UE 120, ...). Figure 8 The device 800, etc., receives an uplink request, which includes an indication that the data associated with the uplink request is latency-sensitive (box 710). For example, a base station (e.g., using...) Figure 9 The receiving component 902 depicted may receive an uplink request from the UE, which includes an indication that the data associated with the uplink request is latency sensitive, as described above.

[0113] like Figure 7 As further shown, in some aspects, process 700 may include transmitting uplink permission to the UE associated with a logical channel group, which includes logical channels for the data (block 720). For example, a base station (e.g., using...) Figure 9 The transmission component 904 depicted can transmit uplink permission to the UE associated with a logical channel group, which includes logical channels for the data, as described above. In some respects, this logical channel group is associated with a higher priority than one or more other logical channel groups.

[0114] like Figure 7 As further shown, in some aspects, process 700 may include receiving data from the UE using the logical channel, at least in part based on the uplink permission (block 730). For example, a base station (e.g., using receiving component 902) may receive data from the UE using the logical channel, at least in part based on the uplink permission, as described above.

[0115] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0116] In the first respect, the data has an associated lifespan.

[0117] In the second aspect, either alone or in combination with the first aspect, uplink requests include scheduling requests.

[0118] In the third aspect, either alone or in combination with one or more of the first and second aspects, the scheduling request is associated with a first data structure, which is different from the second data structure associated with the uplink request for non-latency-sensitive data.

[0119] In the fourth aspect, the scheduling request is associated with the logical channel, either alone or in combination with one or more of the first to third aspects.

[0120] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the scheduling request comprises multiple bits.

[0121] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the scheduling request indicates at least one of the following: that the data is delay-sensitive, the size associated with the data, and the remaining time available for transmitting the data.

[0122] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the scheduling request includes two or more bits that indicate whether the data is latency-sensitive and the relative size associated with the data.

[0123] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the scheduling request includes two or more bits that indicate the degree of latency sensitivity associated with the data.

[0124] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the scheduling request is encoded according to a PUCCH format comprising two or fewer bits.

[0125] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the scheduling request is encoded according to a PUCCH format comprising two or more bits.

[0126] In the eleventh aspect, data is transmitted to the base station, either alone or in combination with one or more of the first to tenth aspects, without transmitting the BSR.

[0127] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the size of the uplink permission is at least partially based on the size associated with the data previously transmitted using that logical channel.

[0128] In the thirteenth aspect, the data is associated, either alone or in combination with one or more of the first to twelfth aspects, with periodic uplink transmissions to the base station.

[0129] In the fourteenth aspect, uplink requests include BSRs, either alone or in combination with one or more of the first to thirteenth aspects.

[0130] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the BSR includes a parameter indicating that the data is latency-sensitive.

[0131] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, this parameter is configured using RRC (e.g., using...). Figure 9 The configuration component 908 is described.

[0132] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the BSR includes at least one bit indicating that the data is delay-sensitive.

[0133] In the eighteenth aspect, the at least one bit is included, alone or in combination with one or more of the first to seventeenth aspects, together with the buffer size indicated in the BSR.

[0134] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 700 can be executed in parallel.

[0135] Figure 8 This is a block diagram of an example device 800 for wireless communication. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802 and a transmitting component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 800 may use the receiving component 802 and the transmitting component 804 to communicate with another device 806 (such as a UE, a base station, or another wireless communication device). As further shown, device 800 may include an encoding component 808 and other examples.

[0136] In some respects, device 800 can be configured to perform the functions described herein. Figure 4-5B The described one or more operations. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein (such as...). Figure 6 The process 600), or a combination thereof. In some aspects, the device 800 and / or Figure 8 One or more components shown may include the above combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 8 One or more components shown can be combined as described above. Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0137] Receiver 802 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from device 806. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 806. In some aspects, receiver 802 may include combinations thereof. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0138] Transmission component 804 can transmit communications (such as reference signals, control information, data communications, or combinations thereof) to device 806. In some aspects, one or more other components of device 806 can generate communications and provide the generated communications to transmission component 804 for transmission to device 806. In some aspects, transmission component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, and other examples) on the generated communications and can transmit the processed signals to device 806. In some aspects, transmission component 804 can include combinations of the above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 804 may coexist with the receive component 802 in a transceiver.

[0139] In some aspects, the transmission component 804 may transmit an uplink request to the device 806, including an indication that the data associated with the uplink request is latency-sensitive. The receiving component 802 may receive from the device 806 an uplink grant associated with a logical channel group, which includes logical channels for the data. In some aspects, this logical channel group is associated with a higher priority than one or more other logical channel groups. Accordingly, the transmission component 804 may transmit data to the device 806 using the logical channels, at least in part, based on the uplink grant.

[0140] In some aspects, the uplink request includes a scheduling request. Accordingly, encoding component 808 may encode the scheduling request according to a first data structure, which differs from the second data structure associated with the uplink request for non-latency-sensitive data. In some aspects, encoding component 808 may include the combination of the above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof.

[0141] In some aspects, the encoding component 808 may encode a scheduling request using multiple bits. For example, a scheduling request may include two or more bits indicating that the data is latency-sensitive and the relative size associated with the data. Additionally or alternatively, a scheduling request may include two or more bits indicating the degree of latency sensitivity associated with the data. In some aspects, the encoding component 808 may encode a scheduling request according to a PUCCH format comprising two or fewer bits. Alternatively, the encoding component 808 may encode a scheduling request according to a PUCCH format comprising more than two bits.

[0142] In some aspects, the uplink request includes a BSR. Accordingly, the encoding component 808 can encode the BSR using a parameter indicating that the data is latency-sensitive. Alternatively, the encoding component 808 can encode the BSR using at least one bit indicating that the data is latency-sensitive.

[0143] Figure 8 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 8 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The collection of components shown (e.g., one or more components) can be executed as described by Figure 8 The other set of components shown in the diagram performs one or more functions.

[0144] Figure 9 This is a block diagram of an example device 900 for wireless communication. Device 900 may be a base station, or a base station may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 may use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a base station, or another wireless communication device). As further shown, device 900 may include a configuration component 908 and other examples.

[0145] In some respects, device 900 can be configured to perform the functions described herein. Figure 4-5B The described one or more operations. Additionally or alternatively, the device 900 may be configured to perform one or more processes described herein (such as...). Figure 7The process 700), or a combination thereof. In some aspects, the device 900 and / or Figure 9 One or more components shown may include the above combination Figure 2 One or more components of the described base station. Additional or alternative. Figure 9 One or more components shown can be combined as described above. Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0146] Receiver 902 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from device 906. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 906. In some aspects, receiver 902 may include combinations thereof. Figure 2 The described base station includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0147] The transmission component 904 can transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 906. In some aspects, one or more other components of the device 906 can generate communications and provide the generated communications to the transmission component 904 for transmission to the device 906. In some aspects, the transmission component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, and other examples) on the generated communications and can transmit the processed signals to the device 906. In some aspects, the transmission component 904 can include combinations of the above. Figure 2 The described base station includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may coexist with the receive component 902 in a transceiver.

[0148] In some aspects, receiving component 902 may receive an uplink request from device 906, which includes an indication that the data associated with the uplink request is latency-sensitive. Transmitting component 904 may transmit to device 906 an uplink grant associated with a logical channel group, which includes logical channels for the data. In some aspects, this logical channel group is associated with a higher priority than one or more other logical channel groups. Accordingly, receiving component 902 may receive data from device 906 using the logical channels, at least in part, based on the uplink grant.

[0149] In some aspects, the uplink request includes a scheduling request. Alternatively, the uplink request includes a BSR. Accordingly, configuration component 908 can configure (e.g., using RRC signaling, etc.) parameters to be included in the BSR, indicating that the data is latency-sensitive. In some aspects, configuration component 908 may include the above-mentioned combination... Figure 2 The described base station includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof.

[0150] Figure 9 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of components shown (e.g., one or more components) can be executed as described by Figure 9 The other set of components shown in the diagram performs one or more functions.

[0151] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be obtained through practice.

[0152] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented using hardware, firmware, and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or hardware and software combinations. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in any aspect. Therefore, the operation and behavior of these systems and / or methods are described herein without reference to any specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on the description herein.

[0153] As used in this article, depending on the context, satisfying the threshold can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0154] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below may be directly dependent on only one claim, the disclosure of aspects includes each dependent claim being combined with each other claim in this set of claims. The phrase “at least one of” refers to any combination of these items, including single members. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0155] The elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “a certain” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Moreover, as used herein, the terms “have,” “contain,” “include,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Moreover, as used herein, the term “or” is intended to be inclusive when used in a sequence and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., in combination with “either of” or “only one of”).

Claims

1. A wireless communication method performed by a user equipment (UE), comprising: Transmit an uplink request, the uplink request including an indication that the data associated with the uplink request has an associated time-to-live (TTL), wherein the associated TTL corresponds to at least one of the following: The time period before transitioning to the downtime or fault state; or The number of messages incorrectly received before the transition to the downtime or fault state; Receive uplink permission associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; as well as The data is transmitted using the logical channel, at least in part based on the uplink permission.

2. The method of claim 1, wherein the uplink request includes a scheduling request.

3. The method as described in claim 2, wherein, The scheduling request is associated with a first data structure, which is different from the second data structure associated with uplink requests for non-latency-sensitive data.

4. The method of claim 2, wherein, The scheduling request is associated with the logical channel.

5. The method of claim 2, wherein, The scheduling request consists of multiple bits.

6. The method of claim 5, wherein, The scheduling request indicates at least one of the following: The indication regarding the associated lifetime of the data, The size associated with the data, or The remaining time is used to transmit the data.

7. The method of claim 5, wherein the scheduling request comprises two or more bits indicating that the data has an associated time to live and a relative size associated with the data.

8. The method of claim 5, wherein, The scheduling request includes two or more bits that indicate the degree of latency sensitivity associated with the data.

9. The method of claim 5, wherein, The scheduling request is encoded according to the Physical Uplink Control Channel (PUCCH) format, which includes two or fewer bits.

10. The method of claim 5, wherein, The scheduling request is encoded according to a PUCCH format consisting of two or more bits.

11. The method of claim 1, wherein, The data is transmitted without transmitting a buffer status report (BSR).

12. The method of claim 1, wherein, The size of the uplink permission is at least in part based on the size associated with the data previously transmitted using the logical channel.

13. The method of claim 1, wherein, The data is associated with periodic uplink transmissions from the UE.

14. The method of claim 1, wherein, The uplink request includes a buffer status report (BSR).

15. The method of claim 14, wherein, The BSR includes parameters that indicate the associated lifetime of the data.

16. The method of claim 15, wherein, The parameters are configured using radio resource control.

17. The method of claim 14, wherein, The BSR includes at least one bit indicating that the data has an associated time to live.

18. The method of claim 17, wherein, The at least one bit is included together with the buffer size indicated in the BSR.

19. A wireless communication method performed by a network node, comprising: Receive an uplink request, the uplink request including an indication that the data associated with the uplink request has an associated time-to-live, wherein the associated time-to-live corresponds to at least one of the following: The time period before transitioning to the downtime or fault state; or The number of messages incorrectly received before the transition to the downtime or fault state; Uplink permission is granted for transmission associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; as well as The data is received using the logical channel, at least in part based on the uplink permission.

20. The method of claim 19, wherein the uplink request includes a scheduling request.

21. The method of claim 20, wherein, The scheduling request: Associated with a first data structure, which differs from the second data structure associated with uplink requests for non-latency-sensitive data, Associated with the logical channel, Including multiple bits, Or a combination thereof.

22. The method of claim 21, wherein, The scheduling request indicates at least one of the following: The indication that the data has an associated lifetime, The size associated with the data, or The remaining time is used to transmit the data.

23. The method of claim 21, wherein the scheduling request comprises two or more bits indicating that the data has an associated time to live and a relative size associated with the data.

24. The method of claim 21, wherein, The scheduling request includes two or more bits that indicate the degree of latency sensitivity associated with the data.

25. The method of claim 21, wherein, The scheduling request is encoded according to the Physical Uplink Control Channel (PUCCH) format, which includes two or fewer bits.

26. The method of claim 21, wherein, The scheduling request is encoded according to a PUCCH format consisting of two or more bits.

27. The method of claim 19, wherein, The data is transmitted without transmitting a buffer status report (BSR).

28. The method of claim 19, wherein, The size of the uplink permission is at least in part based on the size associated with the data previously transmitted using the logical channel.

29. The method of claim 19, wherein, The data is associated with periodic uplink transmissions to the network node.

30. The method of claim 19, wherein, The uplink request includes a buffer status report (BSR).

31. The method of claim 30, wherein the BSR includes parameters configured using radio resource control, the parameters indicating that the data has an associated lifetime.

32. The method of claim 30, wherein, The BSR includes at least one bit indicating that the data has an associated time to live.

33. The method of claim 32, wherein the at least one bit is included together with the buffer size indicated in the BSR.

34. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors are operatively coupled to the memory, and the memory and the one or more processors are configured to: Transmit an uplink request, the uplink request including an indication that the data associated with the uplink request has an associated time-to-live (TTL), wherein the associated TTL corresponds to at least one of the following: The time period before transitioning to the downtime or fault state; or The number of messages incorrectly received before the transition to the downtime or fault state; Receive uplink permission associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; as well as The data is transmitted using the logical channel, at least in part based on the uplink permission.

35. The UE of claim 34, wherein the one or more processors are further configured to perform the method of any one of claims 2-18.

36. A network node for wireless communication, comprising: Memory; as well as One or more processors are operatively coupled to the memory, and the memory and the one or more processors are configured to: Receive an uplink request, the uplink request including an indication that the data associated with the uplink request has an associated time-to-live, wherein the associated time-to-live corresponds to at least one of the following: The time period before transitioning to the downtime or fault state; or The number of messages incorrectly received before the transition to the downtime or fault state; Uplink permission is granted for transmission associated with a logical channel group, the logical channel group including logical channels for the data, wherein the logical channel group is associated with a higher priority than one or more other logical channel groups; as well as The data is received using the logical channel, at least in part based on the uplink permission.

37. The network node of claim 36, wherein the one or more processors are further configured to perform the method of any one of claims 20-33.

Images