Wireless communication scheduling

Abstract

Aspects of the present disclosure relate to an apparatus configured for wireless communication. In certain aspects, the apparatus is configured to generate data (e.g., generate uplink data and store the data in a buffer until an uplink resource is granted for transmission of the data). In certain aspects, the apparatus is configured to send a scheduling request (SR) to a network node that includes an indication of a size of the generated data, where the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 047,224, entitled “WIRELESS COMMUNICATION SCHEDULING” and filed on October 17, 2022, which is expressly incorporated herein by reference in its entirety. Background Art Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to methods and techniques for uplink scheduling in wireless networks.

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0008] Certain aspects relate to a method for wireless communication at an apparatus. In some examples, the method includes generating data. In some examples, the method includes outputting a scheduling request (SR) including an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0009] Certain aspects relate to a method for wireless communication at an apparatus. The method may include generating data. In some examples, the method includes outputting a communication including a scheduling request (SR) and an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0010] Certain aspects relate to an apparatus configured for wireless communication, the apparatus comprising: a memory comprising instructions; and one or more processors configured to execute the instructions. In some examples, the one or more processors are configured to generate data. In some examples, the one or more processors are configured to output a scheduling request (SR) including an indication of the size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold.

[0011] Certain aspects relate to an apparatus configured for wireless communication, the apparatus comprising: a memory comprising instructions; and one or more processors configured to execute the instructions. In some examples, the one or more processors are configured to generate data. In some examples, the one or more processors are configured to output a communication including a scheduling request (SR) and an indication of the size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold.

[0012] Certain aspects relate to an apparatus for wireless communication. In some examples, the apparatus includes means for generating data. In some examples, the apparatus includes means for outputting a scheduling request (SR) including an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold.

[0013] Certain aspects relate to an apparatus for wireless communication. The apparatus may include means for generating data. In some examples, the apparatus includes means for outputting a communication including a scheduling request (SR) and an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold.

[0014] Certain aspects relate to a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform a method. In some examples, the method includes generating data. In some examples, the method includes outputting a scheduling request (SR) including an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold.

[0015] Certain aspects relate to a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform a method. The method may include generating data. In some examples, the method includes outputting a communication including a scheduling request (SR) and an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold.

[0016] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0018] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0019] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0020] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0021] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0022] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0023] Figure 4 is a block diagram illustrating an example decomposed base station architecture.

[0024] Figure 5 is a diagram illustrating available cyclic shifts (CS) (in the time domain) for a sequence of length 12 symbols (eg, Zadoff-Chu (ZC)).

[0025] Figure 6 is a schematic diagram illustrating two example time slot configurations and example SR and BSR communications.

[0026] Figure 7 is a diagram illustrating an example mapping between a coarse BSR value range and a cyclic shift value.

[0027] Figure 8 is a diagram illustrating an example mapping between SR values, BSR values, and cyclic shift values.

[0028] Fig. 9 is a diagram illustrating an example mapping between SR values, BSR values, and cyclic shift values.

[0029] Fig.10 is a diagram illustrating an example mapping between SR values, BSR values, and cyclic shift values.

[0030] Fig.11 is a diagram illustrating an example mapping between SR values, BSR values, and cyclic shift values.

[0031] Fig.12 is a block diagram illustrating an example PUCCH.

[0032] Fig.13 is a block diagram illustrating an alternative example PUCCH.

[0033] Fig.14 is a flow chart of a wireless communication method.

[0034] Fig.15 is a diagram illustrating an example of a hardware implementation of an example apparatus.

[0035] Fig.16 is a flow chart of a wireless communication method.

[0036] Fig.17 is a diagram illustrating another example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

[0037] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0038] In order to send uplink data to a network node in conventional wireless communications, a user equipment (UE) may be required to wait for an uplink timeslot to send a positive scheduling request (SR) to the network node (e.g., via a physical uplink communication channel (PUCCH)). The UE then waits for the next uplink timeslot to send a buffer status report (BSR) to the network node, and then waits for the next uplink timeslot scheduled according to the BSR to send uplink data. Such a process, if performed in a downlink-downlink-downlink-downlink-uplink (DDDDU) communication configuration, may result in a delay of at least 10 milliseconds (ms) in uplink data transmission at a 15kHz subcarrier spacing (SCS). For low-latency applications (e.g., extended reality (XR), etc.), this delay may be problematic given the strict delay budgets associated with such applications.

[0039] A "positive SR" is an SR sent by a UE and includes at least one bit (e.g., 1 or 0) indicating that the UE has data stored in its buffer for uplink transmission. In contrast, a "negative SR" is an SR in which the UE sends nothing (e.g., the UE has no data for uplink transmission). Various aspects of the present disclosure relate to enhanced SR and / or BSR communications that are configured to quickly provide uplink grants to UEs, thereby reducing the amount of time required to obtain uplink grants. Certain aspects relate to SR communication enhancements to reduce or eliminate the need for separate BSR communications. Certain aspects provide methods and techniques for providing a BSR on an SR resource and multiplexing between an SR and an initial BSR indication.

[0040] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0041] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

[0042] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software or any combination thereof. If implemented in software, the function can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage device, magnetic disk storage device, other magnetic storage devices, a combination of computer-readable media of the above type, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0043] Figure 11 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0044] The base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) via the third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0045] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in the carrier aggregation for up to a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use spectrum with a bandwidth of up to Y megahertz (MHz) (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0046] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0047] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 gigahertz (GHz) unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0048] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0049] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is typically (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0050] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" or the like can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this article, it can broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0051] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0052] Base station 180 may transmit beamformed signals in one or more transmit directions 182′ to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182″. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or different. The transmit direction and receive direction of UE 104 may be the same or different.

[0053] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0054] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides quality of service (QoS) flows and session management. All user IP packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IMS, a packet switching (PS) streaming media service, and / or other IP services.

[0055] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceivers, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, 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 communication 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.

[0056] See again Figure 1 In certain aspects, the UE 104 may include an uplink scheduling module 198 configured to generate data and output a scheduling request (SR) including an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0057] In some examples, the uplink scheduling module 198 may be configured to generate data and output communications including a scheduling request (SR) and an indication of the size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0058] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of an UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 34 (most of which are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0059] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μtime slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15 kilohertz (kHz), where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15 kHz, and the subcarrier spacing for parameter set μ=4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific set of parameters.

[0060] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include beam measurement RS (BRS), beam refinement RS (BRRS) and phase tracking RS (PT-RS).

[0062] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the position of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0063] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0064] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0065] Figure 3 3 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0067] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0069] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0071] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0072] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] Figure 4 4 is a block diagram illustrating an example decomposed base station 400 architecture. The decomposed base station 400 architecture may include one or more CUs 410, which may communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more decomposed base station units (such as a near real-time (RT) RIC 425 via an E2 link, or a non-RT RIC 415 associated with a service management and orchestration (SMO) framework 405, or both). The CU 410 may communicate with one or more DUs 430 via corresponding midhaul links, such as an F1 interface. The DU 430 may communicate with one or more RUs 440 via corresponding fronthaul links. The RU 440 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 440 simultaneously.

[0074] Each of the units, namely, CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405, may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. In addition, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0075] In some aspects, CU 410 may host higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 410. CU 410 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 410 may be implemented to communicate with DU 430 for network control and signal transmission.

[0076] DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

[0077] The lower layer functionality may be implemented by one or more RUs 440. In some deployments, a RU 440 controlled by a DU 430 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the DU 430 and the CU 410 to be implemented in a cloud-based RAN architecture such as a virtual RAN (vRAN) architecture.

[0078] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud 490) 652) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 411, via the O1 interface. In addition, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

[0079] The non-RT RIC 415 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 425. The non-RT RIC 415 may be coupled to or in communication with the near-RT RIC 425 (such as via an A1 interface). The near-RT RIC 425 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 410, one or more DUs 430, or both, and O-eNBs to the near-RT RIC 425 (such as via an E2 interface).

[0080] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 425, the non-RT RIC 415 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 425 and may be received from a non-network data source or network function at the SMO framework 405 or the non-RT RIC 415. In some examples, the non-RT RIC 415 or the near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 415 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 405 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0081] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The 198 came to execute all aspects.

[0082] Figure 5 5 is a diagram 500 illustrating available cyclic shifts (CS) (in the time domain) for a sequence of length 12 symbols (e.g., Zadoff-Chu (ZC)). It should be noted that the orthogonality between different code channels varies greatly; Figure 5 The best orthogonality is achieved between the code channels with the largest difference in cyclic shift #0 and cyclic shift #6).

[0083] In some aspects of wireless communication, two UEs (e.g., Figure 1 UEs 104) may be allocated to the same physical (e.g., time / frequency) resources, and due to these different channel conditions (e.g., different physical locations), their transmissions may be managed by network nodes (e.g., Figure 1 The "same" resources may be overlapping rather than identical. In order to distinguish multiplexed UEs sharing the same physical resources at the receiver side, there should be a sufficiently low cross-correlation between the reference signals. This can be arranged by assigning different cyclic shifts of the same reference signal to different MU-MIMO terminals. In this case, dynamic channel state information (CSI) included in the UL grant may be used for signaling of the cyclic shift.

[0084] In some examples, the UE may send a 2-bit HARQ ACK (e.g., PUCCH format 0) by sending a base sequence S with a specific amount of cyclic shift. The amount of cyclic shift may depend on the HARQ bit. For example, one or more cyclic shift values ​​may be mapped to a 2-bit HARQ value. In some examples, the first bit may correspond to the SR, and the second bit may correspond to an indication of the size of the uplink data transmission (e.g., the amount of data stored in the UE buffer). As illustrated, the HARQ ACK value {0,0} is mapped to cyclic shift 0, the HARQ ACK value {0,1} is mapped to cyclic shift 3, the HARQ ACK value {1,1} is mapped to cyclic shift 6, and the HARQ ACK value {1,0} is mapped to cyclic shift 9. These are examples, and other mapping schemes are contemplated as shown below.

[0085] Example of a multi-function dispatch request (SR)

[0086] If a UE (e.g. Figure 1 If a UE 104 has data for uplink transmission, it may send a request to a network node (e.g., Figure 1 102 / 180) to request an uplink grant. When the SR is not multiplexed with the HARQ ACK, the UE 104 may then send a 1-bit SR (e.g., 0 or 1). Alternatively, if the UE 104 does not have data, the UE 104 will refrain from sending any SR. That is, the UE 104 may utilize the SR to inform the network node that the UE 104 has data for uplink transmission to the node, and to request an uplink grant.

[0087] In certain aspects, the UE 104 may use the SR to provide additional information to the network node 102 , including information regarding the buffer status of the UE 104 . Figure 6 is a schematic diagram illustrating two example time slot configurations 650 / 660 and example SR and BSR communications. Although both time slot configurations are examples of downlink-downlink-downlink-special uplink (DDDSU) time slot configurations, any suitable configuration is contemplated.

[0088] The first example timeslot configuration 650 illustrates a first phase BSR transmission, wherein the SR 652 transmitted within the first uplink timeslot 656 is configured to provide an indication of the buffer status of the UE 104 to the network node 102. Here, the SR 652 includes a 1-bit value (e.g., a value of 0 or a value of 1). The "value of 0" may be configured to indicate to the network node 102 that the UE 104 is requesting an uplink grant (e.g., the UE 104 has data for uplink transmission) and the amount of uplink data stored in the UE's buffer (e.g., a BSR value) is less than a threshold BSR value. The "value of 1" may be configured to indicate that the UE 104 is requesting an uplink grant and the BSR value is greater than a threshold BSR value. In this example, it should be noted that if the SR is not transmitted, the UE 104 does not request an uplink grant (e.g., the UE 104 does not have data for uplink transmission).

[0089] If the value of the transmitted SR 652 = 0, the network node 102 may continue to allocate uplink resources to the UE 104 via uplink grants without requiring the UE 104 to send a BSR report. For example, if the threshold BSR value is equal to 1 slot, the network node may provide the necessary uplink resources to the UE so that it can send uplink data 654 at the next uplink slot 658. In this way, latency is reduced by eliminating the need for the UE 104 to send a separate BSR to the network node before sending uplink data.

[0090] The second example timeslot configuration 660 illustrates an example scenario in which the value of the transmitted SR 662 = 1 and is transmitted in the first uplink timeslot 670. In this example, the network node 102 may allocate uplink resources (e.g., the next uplink timeslot 672) to the UE 104 via a partial uplink grant. For example, the network node 102 may provide the UE 104 with an uplink grant that allocates a portion of the next uplink timeslot 672 for transmission of uplink data 666. The UE 104 may also transmit a partial BSR 664 in the same uplink timeslot as the partial uplink grant, the partial BSR being configured to indicate an amount of resources required to transmit the remaining uplink data (e.g., the amount of uplink data stored in the buffer minus the amount of uplink data 666 transmitted in the next uplink timeslot 672). The network node may then provide another uplink grant to the UE 104 for sending the remaining uplink data 668 at a subsequent uplink timeslot 674. In this manner, fewer bits are required to send the BSR 664 relative to a legacy BSR because the SR 662 includes information about the buffer status.

[0091] The threshold BSR value may be configured by the network node 102 or the UE 104. For example, the network node 102 or the UE 104 may configure the threshold using L3 / L2 / L1 signaling (e.g., radio resource control (RRC) messaging, MAC-CE, DCI, or piggyback signal on PDSCH / PDCCH).

[0092] Figure 7 700 is a diagram illustrating an example mapping between a coarse BSR value range and a cyclic shift value. As illustrated, the cyclic shift may be any value from 0 to 11, where 0, 3, 6, and 9 are each mapped to a BSR value range. That is, if the UE has M bits of data stored in a buffer for uplink transmission, the UE may transmit the PUCCH using a cyclic shift value indicating a value range including M. Because there are four cyclic shift values, the value range associated with each cyclic shift provides greater granularity relative to a 1-bit SR value.

[0093] Therefore, when the UE uses a specific cyclic shift to send PUCCH, the base station can receive the base sequence of PUCCH, determine the cyclic shift, and map the shift to the BSR range. As illustrated in the figure, cyclic shift 0 is mapped to the range of 1 to X bits of uplink data; cyclic shift 3 is mapped to X+1 to Y bits of uplink data; cyclic shift 6 is mapped to Y+1 to Z bits of uplink data; and cyclic shift 9 is mapped to more than Z bits of uplink data.

[0094] In some aspects, a HARQ ACK transmission may overlap with an SR transmission, potentially causing the ACK signal and the SR signal to collide. In such a scenario, the UE and the base station may be configured to change the meaning of the SR value. Here, when an ACK overlaps with an SR, an SR value of 1 may be changed to mean that the UE has uplink data to send, and an SR value of 0 may be changed to mean that the UE has no uplink data to send.

[0095] Example of Scheduling Request (SR) and Buffer Status Request (BSR)

[0096] As discussed, the UE and the base station may be configured to send and receive SRs and / or BSRs that allow the base station to quickly configure and schedule uplink grants to the UE relative to examples where the base station is required to wait for a complete BSR. Conventionally, when the UE has no data or no high priority data to send, the UE may transmit nothing. Therefore, to enhance reliability, the UE may send a "0" value SR if the UE has no uplink data to send, and may send a "1" value SR when the UE has uplink data to send to the base station.

[0097] In some examples, the cyclic shift may indicate a specific HARQ ACK value. Figure 5As illustrated, a cyclic shift of 0 may correspond to (eg, map to) a 2-bit HARQ ACK value {0,0}, etc. As described below, a cyclic shift may also (or alternatively) be used to indicate a specific RS value and BSR value.

[0098] Figure 8 800 is a schematic diagram illustrating an example mapping between SR values ​​and BSR values ​​and cyclic shift values. As illustrated, the cyclic shift may be any value from 0 to 11, where 0, 3, 6, and 9 are each mapped to an SR value and a BSR value. That is, the UE may send a PUCCH using a cyclic shift value indicating an SR value and a BSR value. It should be noted that the UE may not use cyclic shift = 3, because in the case of BSR = 1 (e.g., indicating that the UE has an amount within the range of uplink data in the buffer), SR = 0 (e.g., indicating that the UE has no uplink data to send) may not be reasonable. PUCCH may not be a HARQ ACK. Table 1 below illustrates example code points for SR values ​​and BSR values.

[0099]

[0100] Table 1

[0101] In a first example, for one symbol PUCCH format 0, the UE may multiplex the SR bit and the BSR bit before encoding and sending the PUCCH using a joint cyclic shift. That is, the PUCCH may be sent using one cyclic shift value to indicate both the SR value and the BSR value, such as Figure 8 exemplified.

[0102] In a second example, instead of using a joint cyclic shift, the UE may send two separate signals: one signal for the SR bit and another signal for the BSR bit. Here, the UE may send the SR bit at a different power level than the BSR bit to separate the two signals. For example, the SR may be sent at a higher power level than the BSR so that the base station can separate the two values.

[0103] In a third example, the UE may indicate to the base station whether there is new high priority data based on whether the UE sends the SR completely. For example, instead of sending SR=0 to indicate that there is no new uplink data, the UE may refrain from sending the SR. For example, Table 2 below illustrates such an example.

[0104]

[0105] Table 2

[0106] Thus, in this example, the UE only sends a SR = 1 value when there is new high priority data in the UE buffer for uplink transmission. When the UE has data in the buffer but it is not high priority, the UE sends SR = 0. The BSR value indicates whether the amount of data is greater than or less than a threshold (e.g., in bits).

[0107] Example of multi-symbol PUCCH transmission

[0108] Certain aspects relate to using multi-symbol PUCCH (eg, PUCCH format 1) to send SR and BSR.

[0109] In some examples, the UE may assign a priority to either the SR or the BSR relative to the other. For example, if the SR involves data that is not high priority (e.g., as in Table 2), the BSR may be a higher priority than the SR. Conversely, if the SR is configured to indicate high priority data, the SR may be a higher priority than the BSR. In this example, the SR / BSR with a higher priority may be sent by the UE in the earliest symbol of the PUCCH, while the other of the SR / BSR is sent in a subsequent symbol of the PUCCH.

[0110] For example, if the SR is a higher priority, the SR is sent using one or more of the earliest symbols of the PUCCH. Subsequent symbols of the PUCCH carrying the BSR may be sent, and in some examples, may also carry repetitions of the SR. If the BSR is a higher priority, the BSR may be sent using one or more of the earliest symbols of the PUCCH. In this example, the UE may not need to send the SR because the sending of the BSR implicitly indicates that the UE has information to send. In addition, if the BSR has priority, the base station may determine that the uplink data is not a high priority. It should be noted that the symbols of the PUCCH may be sent with a cyclic value mapped to the appropriate SR / BSR value.

[0111] Fig. 9 is a schematic diagram illustrating an example mapping between SR values ​​and BSR values ​​and cyclic shift values. As illustrated, a first symbol 900 may be sent using a cyclic shift to indicate an SR value, and a second symbol 950 may be sent using a cyclic shift to indicate a BSR value. A cyclic shift of 3 may indicate an SR value of 0 in the first symbol 900 and a BSR value of 0 in the second symbol 950. A cyclic shift of 9 may indicate an SR value of 1 in the first symbol 900 and a BSR value of 1 in the second symbol 950. It should be noted that any cyclic shift value may be mapped to an SR value and a BSR value.

[0112] Here, the first symbol 900 of the PUCCH may be used to indicate an SR value, and the second symbol 950 of the PUCCH may be used to indicate a BSR value. The same cyclic shift mapping may be used for both SR and BSR (e.g., a value of 0 maps to the same cyclic shift, and a value of 1 maps to another cyclic shift), or the mapping may be different for SR and BSR. For example, cyclic shift values ​​{3,9} may correspond to SR values, while cyclic shift values ​​{0,6} may correspond to BSR values.

[0113] Fig.10 1 is a schematic diagram illustrating an example mapping between SR values ​​and BSR values ​​and cyclic shift values. As illustrated, a first mapping 1000 may be used to send a first symbol using a cyclic shift to indicate an SR value, and a second mapping 1050 may be used to send a second symbol using a cyclic shift to indicate both an SR value and a BSR value. Here, as described above, the SR value may be a higher priority than the BSR value. It should be noted that any cyclic shift value may be mapped to an SR value and a BSR value. In this example, there is an equal distance between the cyclic shift values ​​mapped to the SR value and the BSR value.

[0114] Fig.11 1 is a diagram illustrating an example mapping 1100 between SR values ​​and BSR values ​​and cyclic shift values. The illustrated mapping may be used for Fig.10 Although cyclic shift values ​​0, 2, 6, and 8 are used in this example, other cyclic shift values ​​may be used instead. For example, cyclic shift values ​​0, 4, 6, and 10.

[0115] In certain aspects, the UE may use PUCCH format 2 for uplink transmissions indicating one or more of the SR and / or BSR. The UE may use PUCCH format 2 to send more than 2 bits in one or more symbols. In an example where the number of resource blocks (RBs) is 1, the UE may multiplex a 1-bit SR and a 1-bit BSR on the PUCCH. These bits may be encoded at a resource element (RE) granularity, or the two bits may be jointly encoded. In an example where the number of RBs is greater than 1, the SR bit and the BSR bit may be encoded at the RE or RB granularity, or jointly encoded. The UE may dedicate more RE / RBs to higher priority bits (e.g., SR or BSR). For example, because PUCCH format 2 can be used to send more than 2 bits, the UE may send a 1-bit SR and use the remaining bits for the BSR.

[0116] In certain aspects, PUCCH format 1 may be used to send a 1-bit or 2-bit payload using 4 to 14 OFDM symbols. For a given cell-specific sequence S (e.g., length 12), a 1-bit or 2-bit payload (b) may be sent, where the sequence S includes a DMRS on even OFDM symbols, and where S includes a modulation b on odd OFDM symbols. The UE may use BPSK modulation for b=1-bit payload and QPSK modulation for b=2-bit payload.

[0117] Fig.12 1 is a block diagram illustrating an example PUCCH 1200 (e.g., Format 1) in which an SR and a BSR are multiplexed with a base sequence S (e.g., time domain multiplexing (TDM)). Here, the PUCCH 1200 may include a plurality of OFDM symbols (e.g., N=14 OFDM symbols), in which even-numbered symbols are defined by S and odd-numbered symbols are defined by S(b) (e.g., multiplexing the product of S and b). The SR 1202 may be indicated on the first Z symbols of the PUCCH 1200, and a combination of the SR and the BSR 1204 may be indicated on the last symbols (e.g., NZ symbols).

[0118] Here, SR and BSR are TDMed with a base sequence to indicate the values ​​of SR and BSR. The UE may use the first Z OFDM symbols to send a 1-bit high priority SR, while using the remaining NZ OFDM symbols to send SR and BSR. The value of Z may be configured by the base station and sent to the UE via RRC or DCI. In some examples, b may be equal to the SR value in SR 1202, and b may be equal to the SR and BSR of SR and BSR 1204.

[0119] Fig.13 1 is a block diagram illustrating an alternative example PUCCH 1300 (e.g., Format 1). In which the SR and BSR are multiplexed with a base sequence S (e.g., time domain multiplexing (TDM)). Here, the SR can be sent using a first portion 1302 of the PUCCH and a second portion 1304 of the PUCCH 1300, while the BSR can be sent using a third portion 1306 of the PUCCH 1300. In some examples, the third portion can include a combination of the SR and the BSR.

[0120] Fig.14 1400 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104; Fig.15 Device 1502) is executed.

[0121] At 1402, the UE may obtain a configuration message including an indication of a threshold from a network node. For example, 1402 may be Fig.15For example, the threshold value may indicate a buffer threshold value, which the UE may use to determine whether to indicate a 1 or a 0 to the network node to indicate its buffer status.

[0122] At 1404, the UE may obtain authorization from the network node for resources via which the generated data is to be output for transmission, wherein the resources are based on a threshold value. Fig.15 For example, the SR may indicate that the size of the generated data is less than or equal to a threshold, thereby indicating that the UE buffer contains a relatively low amount of data.

[0123] At 1406, the UE may obtain a grant from the network node for resources via which the generated data may be output for transmission, wherein the resources are based on the actual size of the data. For example, 1406 may be Fig.15 For example, the UE may provide the network node with an actual value of the BSR, and provide authorized resources for the actual value of the BSR.

[0124] At 1408, the UE may generate data. For example, 1408 may be performed by Fig.15 The generation component 1542 of the UE is executed. For example, the UE may generate data for uplink transmission to the network node and may store the generated data in a buffer.

[0125] At 1410, the UE may output a scheduling request (SR) including an indication of the size of the generated data for transmission to the network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold. For example, 1410 may be Fig.15 For example, the UE may send an SR to the network node, wherein the SR is configured to indicate whether the generated uplink data is greater than or less than a threshold amount.

[0126] At 1412, the UE may output a short buffer status report (BSR) configured to indicate the actual size of the generated data for transmission to the network node. For example, 1412 may be Fig.15 The sending component 1544 of the UE may execute. For example, the UE may generate data for uplink transmission to the network node and may store the generated data in a buffer.

[0127] In certain aspects, the SR is output for transmission in a first time slot, and wherein the short BSR is output for transmission in a second time slot following the first time slot.

[0128] In certain aspects, the configuration message is obtained via a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), downlink control information (DCI), or a physical downlink shared channel (PDSCH).

[0129] In some aspects, the indication of the size of the generated data is a 1-bit value.

[0130] In certain aspects, the indication of the size of the generated data includes a first value indicated by a bit obtained based on the SR and a second value indicated by a cyclic shift of the SR.

[0131] Fig.15 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1502. The apparatus 1502 is a UE and includes a cellular baseband processor 1504 (also referred to as a modem) coupled to a cellular RF transceiver 1522 and one or more subscriber identity modules (SIM) cards 1520, an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510, a Bluetooth module 1512, a wireless local area network (WLAN) module 1514, a global positioning system (GPS) module 1516, and a power source 1518. The cellular baseband processor 1504 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1522. The cellular baseband processor 1504 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1504 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1504, causes the cellular baseband processor 1504 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1504 when executing the software. The cellular baseband processor 1504 also includes a receiving component 1530, a communication manager 1532, and a sending component 1534. The communication manager 1532 includes one or more of the illustrated components. The components within the communication manager 1532 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1504. The cellular baseband processor 1504 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1502 may be a modem chip and include only the baseband processor 1504, and in another configuration, the device 1502 may be the entire UE (e.g., see Figure 3 350), and includes the aforementioned additional modules of device 1502.

[0132] The communication manager 1532 includes a receiving component 1540 configured to obtain authorization from a network node for resources via which the generated data is to be output for transmission, wherein the resources are based on an actual size of the data; obtain authorization from a network node for resources via which the generated data is to be output for transmission, wherein the resources are based on a threshold; and obtain a configuration message from the network node including an indication of the threshold; for example, as in conjunction with Fig.14 As described in 1402, 1404 and 1406.

[0133] The communication manager 1532 also includes a generation component 1542, which is configured to output a scheduling request (SR) including an indication of the size of the generated data for transmission to the network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold; and output a short buffer status report (BSR) configured to indicate the actual size of the generated data for transmission to the network node; for example, as combined with Fig.14 As described in 1410 and 1412.

[0134] The apparatus may include executing Fig.14 The additional components of each box in the box of the algorithm in the aforementioned flowchart. Therefore, each box in the above flowchart can be performed by a component, and the device may include one or more of these components. These components can be one or more hardware components, which are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0135] In one configuration, the apparatus 1502, and in particular the cellular baseband processor 1504, includes means for obtaining from a network node a configuration message including an indication of a threshold value; means for obtaining from the network node an authorization for resources via which the generated data is to be output for transmission, wherein the resources are based on the threshold value; means for obtaining from the network node an authorization for resources via which the generated data is to be output for transmission, wherein the resources are based on an actual size of the data; means for generating data; means for outputting, for transmission to the network node, a scheduling request (SR) including an indication of the size of the generated data, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to the threshold value or less than or equal to the threshold value; means for transmitting to the network node a short buffer status report (BSR) configured to indicate the actual size of the generated data.

[0136] The aforementioned means may be one or more of the aforementioned components of the apparatus 1502 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1502 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0137] Fig.16 1600 is a flow chart of a wireless communication method. The method may be performed by a UE (eg, UE 104; device 1602).

[0138] At 1602, the UE may generate data. For example, 902 may be performed by the generating component 1740. Here, the UE may generate data for uplink transmission to the network node and store the generated data in a buffer.

[0139] At 1604, the UE may output a communication including a scheduling request (SR) and an indication of the size of the generated data for transmission to the network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold. For example, 1604 may be performed by the transmission component 1742.

[0140] In certain aspects, both the SR and the indication of the size are indicated via the communicated cyclic shift.

[0141] In certain aspects, the cyclic shift is mapped to a value comprising a first bit and a second bit, wherein the first bit corresponds to the SR and wherein the second bit corresponds to an indication of the size.

[0142] In certain aspects, the communication is a base sequence that is output for transmission to a network node on a physical uplink control channel.

[0143] In certain aspects, the SR is a bit value configured to indicate that the generated data is stored in the buffer and whether the generated data includes high priority data.

[0144] In certain aspects, the SR is output for transmission via a first symbol, wherein an indication of the size of the generated data is output for transmission via a second symbol, and wherein if the generated data includes high priority data, the first symbol is preceding in time relative to the second symbol.

[0145] In certain aspects, the communication is a Physical Uplink Control Channel (PUCCH).

[0146] Fig.171700 is a diagram illustrating an example of a hardware implementation for an apparatus 1702. The apparatus 1702 is a UE and includes a cellular baseband processor 1704 (also referred to as a modem) coupled to a cellular RF transceiver 1722 and one or more subscriber identity modules (SIM) cards 1720, an application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710, a Bluetooth module 1712, a wireless local area network (WLAN) module 1714, a global positioning system (GPS) module 1716, and a power source 1718. The cellular baseband processor 1704 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1722. The cellular baseband processor 1704 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1704 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1704, causes the cellular baseband processor 1704 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1704 when executing the software. The cellular baseband processor 1704 also includes a receiving component 1730, a communication manager 1732, and a sending component 1734. The communication manager 1732 includes one or more of the illustrated components. The components within the communication manager 1732 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1704. The cellular baseband processor 1704 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1702 may be a modem chip and include only the baseband processor 1704, and in another configuration, the device 1702 may be the entire UE (e.g., see Figure 3 350), and includes the aforementioned additional modules of device 1702.

[0147] The communication manager 1732 includes a generation component 1740 configured to generate data, for example, as described in conjunction with Fig.16 The communication manager 1732 also includes a sending component 1742 configured to output a communication including a scheduling request (SR) and an indication of the size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to a threshold, for example, as described in conjunction with 1604.

[0148] The apparatus may include executing Fig.16The additional components of each box in the box of the algorithm in the aforementioned flowchart. Therefore, each box in the above flowchart can be performed by a component, and the device may include one or more of these components. These components can be one or more hardware components, which are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0149] In one configuration, the apparatus 1702, and in particular the cellular baseband processor 1704, includes means for generating data, and means for outputting a communication including a scheduling request (SR) and an indication of the size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0150] The aforementioned means may be one or more of the aforementioned components of the apparatus 1702 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1702 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0151] Additional considerations

[0152] The means for receiving or the means for obtaining may include a receiver (such as the receive processor 338) or the antenna 352 or the receive processor 356 of the UE 350. The means for transmitting or the means for outputting for transmission may include Figure 3 A transmitter (such as a transmit processor 368) or antenna 352 of the illustrated UE 350. Means for generating may include a processing system, which may include one or more processors, such as Figure 3 The receive processor 356 , transmit processor 368 , TX MIMO processor 354 , and / or controller 359 of the illustrated UE 350 .

[0153] In some cases, a device may have an interface (a component for outputting) for outputting a frame for transmission, rather than actually transmitting the frame. For example, a processor may output a frame to a radio frequency (RF) front end via a bus interface for transmission. Similarly, a device may have an interface (a component for obtaining) for obtaining a frame received from another device, rather than actually receiving the frame. For example, a processor may obtain (or receive) a frame from an RF front end for reception via a bus interface.

[0154] As used herein, the term "generating" (or any variation thereof, such as "generate") encompasses a variety of actions. For example, "generating" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), determining, etc.

[0155] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy provided.

[0156] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein unless otherwise specified, the elements mentioned in the singular are not intended to represent "one and only one", but "one or more". Terms such as "if", "when ..." and "while ..." should be interpreted as "under the conditions of ...", rather than meaning an instantaneous time relationship or reaction. That is, these phrases, such as "when ...", do not mean an instantaneous action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or instantaneous time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be construed as part-plus-function unless the element is explicitly recited using the phrase "component for..."

[0157] Example aspects

[0158] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein, but are not limited thereto.

[0159] Embodiment 1 is a method for performing wireless communication at a device, the method comprising: generating data; and outputting a scheduling request (SR) including an indication of the size of the generated data for sending to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0160] Embodiment 2 is a method according to embodiment 1, wherein the SR indicates that the size of the generated data is greater than or equal to the threshold, and wherein the method further includes: outputting a short buffer status report (BSR) configured to indicate the actual size of the generated data for sending to the network node.

[0161] Embodiment 3 is a method according to embodiment 2, wherein the SR is output for transmission in a first time slot, and wherein the short BSR is output for transmission in a second time slot after the first time slot.

[0162] Embodiment 4 is a method according to any one of embodiments 2 and 3, wherein the method further comprises: obtaining authorization for resources from the network node, and outputting the generated data for transmission via the authorization, wherein the resources are based on the actual size of the data.

[0163] Embodiment 5 is a method according to any one of embodiments 1 to 4, wherein the size of the generated data indicated by the SR is less than or equal to the threshold, and wherein the method further includes: obtaining authorization for resources from the network node, and outputting the generated data for sending via the authorization, wherein the resources are based on the threshold.

[0164] Embodiment 6 is a method according to any one of embodiments 1 to 5, wherein the method further comprises: obtaining a configuration message including an indication of the threshold from the network node.

[0165] Embodiment 7 is a method according to embodiment 6, wherein the configuration message is obtained via a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), downlink control information (DCI) or a physical downlink shared channel (PDSCH).

[0166] Embodiment 8 is the method of any one of embodiments 1 to 7, wherein the indication of the size of the generated data is a 1-bit value.

[0167] Embodiment 9 is a method according to any one of embodiments 1 to 8, wherein the indication of the size of the generated data includes a first value indicated by a bit obtained based on the SR and a second value indicated by a cyclic shift of the SR.

[0168] Embodiment 10 is a method for wireless communication at a device, the method comprising:

[0169] generating data; and outputting a communication comprising a scheduling request (SR) and an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

[0170] Embodiment 11 is the method of embodiment 10, wherein both the SR and the indication of the size are indicated via a cyclic shift of the communication.

[0171] Embodiment 12 is the method of embodiment 11, wherein the cyclic shift is mapped to a value comprising a first bit and a second bit, wherein the first bit corresponds to the SR, and wherein the second bit corresponds to the indication of the size.

[0172] Embodiment 13 is a method according to any one of embodiments 10 to 12, wherein the communication is a base sequence output for transmission to the network node on a physical uplink control channel.

[0173] Embodiment 14 is the method according to any one of embodiments 10 to 13, wherein the SR is a bit value configured to indicate whether the generated data is stored in the buffer and whether the generated data includes high priority data.

[0174] Embodiment 15 is a method according to any one of embodiments 10 to 14, wherein the SR is output for transmission via a first symbol, wherein the indication of the size of the generated data is output for transmission via a second symbol, and wherein if the generated data includes high priority data, the first symbol is ahead in time relative to the second symbol.

[0175] Embodiment 16 is a method according to any one of embodiments 10 to 15, wherein the communication is a physical uplink control channel (PUCCH).

[0176] Embodiment 17 is a UE, which comprises: a transceiver; a memory, the memory comprising instructions; and one or more processors, the one or more processors being configured to execute the instructions so that the UE performs a method according to any one of embodiments 1 to 9, wherein the transceiver is configured to: send the SR.

[0177] Embodiment 18 is a UE, comprising: a transceiver; a memory, the memory comprising instructions; and one or more processors, the one or more processors being configured to execute the instructions so that the UE performs a method according to any one of embodiments 10 to 16, wherein the transceiver is configured to: send the communication comprising the SR and the indication of the size of the generated data.

[0178] Embodiment 19 is a device for wireless communication, the device comprising: a component for executing the method according to any one of embodiments 1 to 9.

[0179] Embodiment 20 is a device for wireless communication, comprising: a component for executing a method according to any one of Embodiments 10 to 16.

[0180] Embodiment 21 is a non-transitory computer-readable medium, which includes instructions, which when executed by a device cause the device to perform the method according to any one of embodiments 1 to 9.

[0181] Embodiment 22 is a non-transitory computer-readable medium, which includes instructions, which when executed by a device cause the device to perform the method according to any one of embodiments 10 to 16.

[0182] Embodiment 23 is a device for wireless communication, the device comprising: a memory, the memory comprising instructions; and one or more processors, the one or more processors being configured to execute the instructions so that the device performs a method according to any one of Embodiments 1 to 9.

[0183] Embodiment 24 is a device for wireless communication, the device comprising: a memory, the memory comprising instructions; and one or more processors, the one or more processors being configured to execute the instructions so that the device performs a method according to any one of Embodiments 10 to 16.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: a memory including instructions; and one or more processors configured to execute the instructions and cause the apparatus to: Generate data; as well as Output a scheduling request (SR) including an indication of the size of the generated data for sending to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

2. The apparatus of claim 1 , wherein the SR indicates that the size of the generated data is greater than or equal to the threshold, and wherein the one or more processors are further configured to cause the apparatus to: A short buffer status report (BSR) configured to indicate an actual size of the generated data is output for transmission to the network node.

3. The apparatus of claim 2, wherein the SR is output for transmission in a first time slot, and wherein the short BSR is output for transmission in a second time slot following the first time slot.

4. The apparatus of claim 2, wherein the one or more processors are further configured to cause the apparatus to: A grant is obtained from the network node for resources via which the generated data is to be output for transmission, wherein the resources are based on the actual size of the data.

5. The apparatus of claim 1 , wherein the SR indicates that the size of the generated data is less than or equal to the threshold, and wherein the one or more processors are further configured to cause the apparatus to: An authorization is obtained from the network node for resources via which the generated data is to be output for transmission, wherein the resources are based on the threshold value.

6. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: A configuration message including an indication of the threshold value is obtained from the network node.

7. The apparatus of claim 6, wherein the configuration message is obtained via a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), downlink control information (DCI), or a physical downlink shared channel (PDSCH).

8. The apparatus of claim 1, wherein the indication of the size of the generated data is a 1-bit value.

9. The apparatus of claim 1, wherein the indication of the size of the generated data comprises a first value indicated by a bit obtained based on the SR and a second value indicated by a cyclic shift of the SR.

10. An apparatus configured for wireless communication, the apparatus comprising: a memory including instructions; and one or more processors configured to execute the instructions and cause the apparatus to: Generate data; as well as Outputting a communication comprising a scheduling request (SR) and an indication of a size of the generated data for transmission to a network node, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

11. The apparatus of claim 10, wherein a cyclic shift via the communication indicates both the SR and the indication of the size.

12. The apparatus of claim 11, wherein the cyclic shift is mapped to a value comprising a first bit and a second bit, wherein the first bit corresponds to the SR, and wherein the second bit corresponds to the indication of the size.

13. The apparatus of claim 10, wherein the communication is a base sequence output for transmission to the network node on a physical uplink control channel. 14 . The apparatus of claim 10 , wherein the SR is a bit value configured to indicate whether the generated data is stored in a buffer and whether the generated data includes high priority data.

15. The apparatus of claim 10, wherein the SR is output for transmission via a first symbol, wherein the indication of the size of the generated data is output for transmission via a second symbol, and wherein if the generated data includes high priority data, the first symbol is preceding in time relative to the second symbol.

16. The apparatus of claim 10, wherein the communication is a physical uplink control channel (PUCCH).

17. The apparatus of claim 10, further comprising a transceiver, wherein the transceiver is configured to: The scheduling request (SR) is sent, wherein the apparatus is configured as a user equipment (UE).

18. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: Transceiver; a memory including instructions; and one or more processors configured to execute the instructions and cause the UE to: Generate data; as well as A scheduling request (SR) including an indication of a size of the generated data is sent via the transmitter, wherein the indication of the size of the generated data is configured to indicate whether the size of the generated data is greater than or equal to a threshold or less than or equal to the threshold.

19. The UE of claim 18, wherein the SR indicates that the size of the generated data is greater than or equal to the threshold, and wherein the one or more processors are further configured to cause the UE to: A short buffer status report (BSR) configured to indicate an actual size of the generated data is transmitted via the transmitter.

20. The UE of claim 18, wherein the SR indicates that the size of the generated data is less than or equal to the threshold, and wherein the one or more processors are further configured to cause the UE to: An authorization is received via the transmitter for a resource via which the generated data is to be output for transmission, wherein the resource is based on the threshold.

Images