Systems and methods for dynamic scheduling in new radio with base stations

Abstract

Dynamic scheduling can be performed by a 5G New Radio in licensed or unlicensed bands. A base station can poll a user equipment (UE) by transmitting a downlink control information (DCI) or other downlink communication that indicates resources that the UE can use to send a scheduling request. The resources are dynamic, e.g., they can be updated based on network conditions and allocated to UEs. Other aspects are also described.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless technology, and more specifically to dynamic scheduling in New Radio (NR) and New Radio in Unlicensed Spectrum (NR-U). BACKGROUND

[0002] The fifth generation of mobile networks (5G) is a wireless standard that aims to improve data transmission speed, reliability, availability, and the like. The standard, while still being developed, includes many details related to various aspects of wireless communication, for example, NR and NR in unlicensed spectrum (greater than 52.6 GHz), also referred to as NR-U. SUMMARY

[0003] Aspects of the disclosure relate to 5G New Radio (NR) operating in a licensed band or 5G New Radio (NR-U) operating in an unlicensed band. 5G NR-U operates on a frequency band above 52.6 GHz.

[0004] In some aspects, a method or a device configured to perform the method (e.g., a user equipment or a baseband processor) is described. The method can include receiving configuration information from a base station, where the configuration information includes information for finding a downlink control information (DCI), polling by receiving the DCI including an indication of a physical uplink control channel (PUCCH) resource for the UE to transmit a dynamic scheduling request (SR), finding the DCI based on the configuration information, and transmitting a dynamic SR in a PUCCH message based on the PUCCH resource, where an uplink grant is performed based on the dynamic SR.

[0005] In some aspects, a method can include polling by receiving a downlink control information (DCI) including a bit indicating whether a UE transmits a dynamic scheduling request (SR), transmitting a dynamic SR in a PUCCH message based on a predetermined physical uplink control channel (PUCCH) resource configured in the UE, where an uplink grant is performed based on the dynamic SR.

[0006] In some aspects, a method or network equipment (e.g., a base station or baseband processor) configured to perform the method is described. The method can include generating a downlink control information (DCI) message including an indication of a physical uplink control channel (PUCCH) resource for a UE to transmit a dynamic scheduling request (SR); polling the UE by transmitting the DCI including the PUCCH resource, the PUCCH resource being dynamically updated based on one or more network conditions including network traffic, locations of one or more UEs, or which of one or more UEs have data to transmit; receiving the dynamic SR in a PUCCH message transmitted according to the PUCCH resource; and transmitting an uplink (UL) grant with beam and time scheduling determined based on the dynamic SR.

[0007] In some aspects, a method includes generating downlink control information (DCI) including a bit indicating whether a user equipment (UE) sends a dynamic scheduling request (SR); polling the UE by transmitting the DCI including the bit, the bit being dynamically updated based on one or more network conditions including network traffic, locations of one or more UEs, or which of one or more UEs have data to transmit; receiving the dynamic SR in a physical uplink control channel (PUCCH) message; and transmitting an uplink (UL) grant with beam and time scheduling determined based on the dynamic SR.

[0008] Other methods and apparatus are also described. BRIEF DESCRIPTION OF DRAWINGS

[0009] The application is illustrated in the general context of office documents, and computer usable instructions according to the teachings of the application described herein. Those skilled in the relevant art will appreciate that the application can be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The application can be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

[0010] Figure 1 An exemplary wireless communication system according to some aspects is shown.

[0011] Figure 2 Uplink and downlink communications according to some aspects are shown.

[0012] Figure 3 An exemplary block diagram of a UE according to some aspects is shown.

[0013] Figure 4 An exemplary block diagram of a BS according to some aspects is shown.

[0014] Figure 5 An exemplary block diagram of cellular communication circuitry according to some aspects is shown.

[0015] Figure 6An example sequence for dynamic scheduling in NR or NR-U is shown, in accordance with some aspects.

[0016] Figure 7 An example of dynamic scheduling resource signaling is shown, in accordance with some aspects.

[0017] Figure 8 An example of a scheduling request including UE assistance information is shown, in accordance with some aspects.

[0018] Figure 9 An example of a bit field for dynamic scheduling request with semi-statically configured resources is shown, in accordance with some aspects.

[0019] Figure 10 An example of using multiple UE scheduling requests is shown, in accordance with some aspects.

[0020] Figure 11 An example of a dynamic scheduling request is shown, in accordance with some aspects.

[0021] Figure 12 Dynamic scheduling with mandatory time intervals between communications is shown, in accordance with some aspects. DETAILED DESCRIPTION

[0022] A method and apparatus for a device to determine physical downlink shared channel scheduling resources for user equipment devices and base stations is described. In the following description, numerous specific details are set forth to provide a thorough explanation of aspects of the application. It will be apparent, however, to one skilled in the art that aspects of the application can be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail in order not to obscure the understanding of this description.

[0023] Reference throughout this specification to "some aspects" or "an aspect" means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect of the application. The appearances of the phrase "in some aspects" in various places in the specification are not necessarily all referring to the same aspect.

[0024] In the following description and claims, the terms "coupled" and "connected," along with their derivatives, can be used. It should be understood that these terms are not intended as synonyms for each other. "Coupled" is used to indicate that two or more elements, which can or can not be in physical or electrical contact with each other, co-operate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled with each other.

[0025] The processes depicted in the following figures are performed by processing logic that comprises hardware (e.g. circuitry, dedicated logic, etc.), software (such as is run on a general-purpose computer system or a dedicated machine), or a combination of both. Although the processes are described in a particular sequential order, some of which can be performed in different orders or concurrently, it is intended that this implementation be illustrative. For example, the various operations can be performed in parallel, or can be performed at different times.

[0026] The terms "server," "client," and "device" are intended to refer generally to data processing systems, rather than to specific form factors of servers, clients, and / or devices.

[0027] A method and apparatus of a device for determining physical downlink shared channel scheduling resources for a user equipment device and a base station are described. In some aspects, the device is a user equipment device having a wireless link with a base station. In some aspects, the wireless link is a fifth generation (5G) link. The device further selects component carriers (CCs) from the wireless link and groups them and determines a virtual CC from the group of selected CCs. The device additionally can perform physical downlink resource mapping based on an aggregated resource matching pattern of the group of CCs.

[0028] Frequency bands for 5G networks are divided into two groups: frequency range 1 (FR1) and frequency range 2 (FR2). FR1 covers communications from 450 MHz to 6 GHz, which includes the LTE frequency range. FR2 covers 24.25 GHz to 52.6 GHz. FR2 is referred to as the millimeter wave (mmWave) spectrum. In some aspects, UEs and base stations can communicate on NR in an unlicensed band above FR2, also referred to as NR-U.

[0029] NR-U is an operating mode that defines the technology by which cellular operators integrate unlicensed spectrum (e.g., frequencies greater than 52.6 GHz, such as between 52.6 GHz and 71 GHz) into 5G networks. Radio waves in this frequency band have wavelengths in the so-called millimeter band, and the radiation in this band is referred to as millimeter waves. NR-U enables both uplink and downlink operations in unlicensed bands. NR-U supports new features, such as wide-band carriers, flexible numerology, dynamic TDD, beamforming, and dynamic scheduling / HARQ timing.

[0030] In NR-U, both licensed assisted access and standalone are supported in unlicensed spectrum. Carriers can use the non-standalone mode to aggregate unlicensed bands with licensed 5G frequencies to support capacity (e.g., similar to LAA), and standalone mode where an enterprise can deploy a private cellular network using unlicensed spectrum. It should be understood that aspects described in the present disclosure with reference to NR can also apply to NR-U, and vice versa, unless the context otherwise dictates. While NR-U has been developed, there are issues with dynamic scheduling, as discussed in other sections.

[0031] Figure 1 A simplified exemplary wireless communication system is shown in accordance with some aspects. Note that Figure 1 The system of FIG. 1 is merely one example of a possible system, and features of this disclosure can be implemented in any of various systems, as desired.

[0032] As shown, the exemplary wireless communication system includes a base station 102A that communicates over a transmission medium with one or more user devices 106A, 106B through 106N, etc. Each user device can be referred to herein as a “user equipment” (UE). Thus, the user devices 106 are referred to as UEs or UE devices.

[0033] The base station (BS) 102A can be a base transceiver station (BTS) or cell site (“cell site station”), and can include hardware enabling it to

[0034] The communication area (or coverage area) for the base station can be referred to as a “cell.” The base station 102A and UEs 106 can be configured to communicate

[0035] As shown, base station 102A can also be equipped to communicate with a network 100 (e.g., with a core network of a cellular service provider, a telecommunication network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among various possibilities). As such, base station 102A can facilitate communication between and among user equipment and the network 100. In particular, cellular base station 102A can provide UEs 106 with voice, SMS, and / or data services via one or more wireless communication standards.

[0036] Base station 102A and other like base stations, such as base stations 102B... 102N, operating according to the same or a different cellular communication standard, can thus provide a network of cells that can provide continuous or approximately continuous overlapping service to UEs 106A-106N and like devices via one or more cellular communication standards over a geographic area.

[0037] Thus, while base station 102A can act as a “serving cell” for UEs 106A-106N as shown in Figure 1 each UE 106 can also be capable of receiving signals from one or more other cells (that can be provided by base stations 102B-N and / or any other base stations), which can be referred to as “neighboring cells,” that can be within range of its communication (and possibly of which it is aware). Such cells can also be capable of facilitating communication between and among user equipment and / or between and among user equipment and the network 100. Such cells can include “macro” cells, “micro” cells, “pico” cells, and / or any of various other granularities of service area sizes. For example, base stations 102A-102B can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible. Figure 1

[0038] In some aspects, base station 102A can be a next generation base station, e.g., a 5G New Radio (5G NR) base station or “gNB.” In some aspects, a gNB can connect to a traditional evolved packet core (EPC) network and / or to a NR core (NRC) network. Further, a gNB cell can include one or more transition and reception points (TRPs). Further, a UE capable of operating according to 5G NR can connect to one or more TRPs within one or more gNBs.

[0039] ​Note that the UEs 106 are able to communicate with one another using multiple wireless communication standards. For example, the UEs 106 can be configured to communicate using a cellular communication protocol (such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (such as lxRTT, lxEV-DO, HRPD, eHRPD), etc.), in addition to wireless networking (such as Wi-Fi) and / or peer-to-peer wireless communication protocols (such as Bluetooth, Wi-Fi peer-to-peer, etc.). The UEs 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (such as ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0040] Figure 2 UEs 106A in communication with base stations 102 are illustrated, in accordance with some aspects. The UEs can each be a device with cellular communication capability, such as a mobile phone, a handheld device, a computer or a tablet computer, or virtually any type of wireless device.

[0041] The UEs can include a processor configured to execute program instructions stored in memory. The UEs can perform any of the method aspects described herein by executing such stored instructions. Alternatively, or in addition, the UEs can include programmable hardware elements, such as an FPGA (field programmable gate array), configured to perform any of the method aspects described herein, or any portion of the method aspects described herein.

[0042] A UE can include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some aspects, a UE can be configured to communicate using, for example, CDMA2000 (lxRTT / lxEV-DO / HRPD / eHRPD) or LTE using a single shared radio and / or GSM or LTE using a single shared radio. The shared radio can be coupled to a single antenna, or can be coupled to multiple antennas (e.g., for MIMO) for performing wireless communication. Generally, a radio can include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio can implement one or more receive and transmit chains using the aforementioned hardware. For example, a UE 106 can share one or more portions of receive and / or transmit chains between multiple wireless communication technologies such as those discussed above.

[0043] In some aspects, a UE can include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, a UE can include one or more radio components that are shared between multiple wireless communication protocols, and one or more radio components that are used exclusively by a single wireless communication protocol. For example, a UE can include a shared radio for communicating using either of LTE or 5G NR (or LTE or lxRTT, or LTE or GSM), and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0044] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some aspects is shown. Note that Figure 3 The block diagram of the communication device is merely one example of a possible communication device. According to aspects, the communication device 106 can be a UE device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., laptop, notebook, or portable computing device), a tablet, and / or combinations of devices, among other devices, according to aspects. As shown, the communication device 106 can include a set of components 300 configured to perform core functions. For example, this set of components can be implemented as a system-on-a-chip (SOC), which can include portions for various purposes. Alternatively, this set of components 300 can be implemented to be separate or integrated components for the various purposes. This set of components 300 can be coupled (e.g., communicatively; directly or indirectly) to various other circuitry of the communication device 106.

[0045] For example, the communication device 106 can include various types of memory (e.g., including NAND flash 310), input / output interfaces such as connector I / F 320 (e.g., for connecting to a computer system; a dock; a charging station; an input device such as a microphone, camera, keyboard; an output device such as a speaker; etc.), a display 360 that can be integrated with or external to the communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-to-medium range wireless communication circuitry 329 (e.g., Bluetooth TM and WLAN circuitry). In some aspects, the communication device 106 can include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0046] The cellular communication circuitry 330 can be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as the illustrated antennas 335 and 336. The short-to-medium range wireless communication circuitry 329 can also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as the illustrated antennas 337 and 338. Alternatively, the short-to-medium range wireless communication circuitry 329 can be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to, or instead of, being coupled to antennas 337 and 338. The short-to-medium range wireless communication circuitry 329 and / or the cellular communication circuitry 330 can include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input-multiple-output (MIMO) configuration.

[0047] In some aspects, as described further below, the cellular communication circuitry 330 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) of multiple radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Further, in some aspects, the cellular communication circuitry 330 can include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain as well as a transmit chain shared with additional radio components, such as a second radio component that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain as well as the shared transmit chain.

[0048] The communication device 106 can also include one or more user interface elements and / or be configured to use with one or more user interface elements. The user interface elements can include any of a variety of elements such as a display 360 (which can be a touch screen display), a keyboard (which can be a discrete keyboard or can be implemented as part of the touch screen display), a mouse, a microphone, and / or a speaker, one or more cameras, one or more buttons, and / or a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0049] The communication device 106 can also include one or more smart cards 345 having SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (Universal Integrated Circuit Card) 345.

[0050] As shown, the SOC 300 can include a processor 302, which can execute program instructions for the communication device 106, and a display circuit 304, which can perform graphics processing and provide display signals to the display 360. The processor 302 can also be coupled to a memory management unit (MMU) 340, which can be configured to receive addresses from the processor 302 and translate those addresses to locations in memory (e.g., memory 306, read only memory (ROM) 350, NAND flash memory 310) or to other circuits or devices, such as the display circuit 304, short range wireless communication circuit 229, cellular communication circuit 330, connector I / F 320, and / or the display 360. The MMU 340 can be configured to perform memory protection and page table translation or set up. In some aspects, the MMU 340 can be included as a portion of the processor 302.

[0051] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 can also be configured to determine physical downlink shared channel scheduling resources for user equipment devices and base stations. Further, the communication device 106 can be configured to select CCs from a wireless link and group them, and determine a virtual CC from the selected CC group. The wireless device can also be configured to perform physical downlink resource mapping based on an aggregated resource matching pattern of the CC group.

[0052] As described herein, the communication device 106 can include hardware and software components for implementing the above-described features for determining physical downlink shared channel scheduling resources for the communication device 106 and a base station. For example, the processor 302 of the communication device 106 can be configured to implement some or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 can be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 302 of the communication device 106 can be configured, in conjunction with one or more other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, to implement some or all of the features described herein.

[0053] Further, as described herein, the processor 302 can include one or more processing elements. Thus, the processor 302 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 302. In addition, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the one or more processors 302.

[0054] Further, as described herein, the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 can each include one or more processing elements. In other words, one or more processing elements can be included in the cellular communication circuitry 330 and, similarly, one or more processing elements can be included in the short-range wireless communication circuitry 329. Thus, the cellular communication circuitry 330 can include one or more integrated circuits (ICs) that are configured to perform the functions of the cellular communication circuitry 330. In addition, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the cellular communication circuitry 230. Similarly, the short-range wireless communication circuitry 329 can include one or more ICs that are configured to perform the functions of the short-range wireless communication circuitry 32. In addition, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the short-range wireless communication circuitry 329.

[0055] Figure 4 An example block diagram of a base station 102 according to some aspects is shown. Note that Figure 4The base station 102 can include at least one processor 404 that can execute program instructions for the base station 102. The processor 404 can also be coupled to a memory management unit (MMU) 440, or other circuit or device, that can be configured to receive addresses from the processor 404 and translate those addresses to locations in memory (e.g., memory 460 and read only memory (ROM) 450).

[0056] The base station 102 can include at least one network port 470. The network port 470 can be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figure 1 and Figure 2

[0057] The network port 470 (or an additional network port) can also be, or alternatively be configured to be, coupled to a cellular network, for example, a core network of a cellular service provider. The core network can provide mobility related services and / or other services to a plurality of devices, such as UE devices 106. In some cases, the network port 470 can be coupled to the telephone network via the core network, and / or the core network can provide the telephone network (e.g., among other UE devices served by the cellular service provider).

[0058] In some aspects, the base station 102 can be a next generation base station, for example, a 5G New Radio (5G NR) base station or “gNB.” In such aspects, the base station 102 can connect to a traditional evolved packet core (EPC) network and / or to an NR core (NRC) network. Further, the base station 102 can be considered a 5G NR cell and can include one or more transition and reception points (TRPs). Further, a UE capable of operating according to 5G NR can connect to one or more TRPs within one or more gNBs. In some aspects, the base station can operate in 5G NR-U mode.

[0059] The base station 102 can include at least one antenna 434, and possibly a plurality of antennas. The at least one antenna 434 can be configured to function as a wireless transceiver and can be further configured to communicate with UE devices 106 via radio 430. The antenna 434 communicates with the radio 430 via communication chain 432. The communication chain 432 can be a receive chain, a transmit chain, or both. The radio 430 can be configured to communicate via various wireless communication standards including, but not limited to, 5G NR, 5G NR-U, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0060] ​The base stations 102 can be configured to use multiple wireless communication standards to communicate. In some cases, the base stations 102 can include multiple radios that can enable the base stations 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base stations 102 can include an LTE radio for performing communications according to LTE and a 5G NR radio for performing communications according to 5G NR and 5G NR-U. In this case, the base stations 102 can be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base stations 102 can include a multi-mode radio capable of performing communications according to any of a plurality of wireless communication technologies, such as 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.

[0061] As further described later herein, the BS 102 can include hardware and software components for implementing or supporting implementation of the features described herein. The processor 404 of the base station 102 can be configured, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), to implement or support implementation of part or all of the methods described herein. Alternatively, the processor 404 can be configured as a programmable hardware element, such as an FPGA (field programmable gate array), or as an ASIC (application specific integrated circuit), or a combination thereof. Alternatively (or additionally) in conjunction with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the base station 102 can be configured to implement part or all of the features described herein.

[0062] Further, as described herein, the processor 404 can be composed of one or more processing elements. In other words, one or more processing elements can be included in the processor 404. Thus, the processor 404 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 404. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the one or more processors 404.

[0063] Additionally, as described herein, the radio 430 can be composed of one or more processing elements. In other words, one or more processing elements can be included in the radio 430. Thus, the radio 430 can include one or more integrated circuits (ICs) that are configured to perform the functions of the radio 430. Further, each integrated circuit can include circuitry (e.g., first circuitry, second circuitry, etc.) that is configured to perform the functions of the radio 430.

[0064] Figure 5 An example simplified block diagram of a cellular communication circuit is shown in accordance with some aspects. Note that Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to aspects, the cellular communication circuit 330 can be included in a communication device, such as the communication device 106 described above. As described above, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and / or a combination of devices, among other devices.

[0065] The cellular communication circuit 330 can be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as the antennas 335a-b and 336 shown in FIG. 3. Figure 3 In some aspects, the cellular communication circuit 330 can include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as shown in FIG. 3, the cellular communication circuit 330 can include a modem 510 and a modem 520. The modem 510 can be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 can be configured for communication according to a second RAT (e.g., such as 5G NR). Figure 5

[0066] As shown, the modem 510 can include one or more processors 512 and memory 516 in communication with the processors 512. The modem 510 can be in communication with a radio frequency (RF) front end 530. The RF front end 530 can include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 can include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some aspects, the receive circuitry 532 can be in communication with a downlink (DL) front end 550, which can include circuitry for receiving radio signals via the antenna 335a.

[0067] Similarly, the modem 520 can include one or more processors 522 and memory 526 in communication with the processors 522. The modem 520 can be in communication with an RF front end 540. The RF front end 540 can include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 can include receive circuitry 542 and transmit circuitry 544. In some aspects, the receive circuitry 542 can be in communication with a DL front end 560, which can include circuitry for receiving radio signals via the antenna 335b.

[0068] ​In some aspects, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front-end 572. Also, the switch 570 can couple the transmit circuitry 544 to the UL front-end 572. The UL front-end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported via the modem 510), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front-end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported via the modem 520), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front-end 572).

[0069] As described herein, the modem 510 can include hardware and software components for implementing the features described above or for determining physical downlink shared channels for user equipment devices and base stations, as well as for various other techniques described herein. For example, the processor 512 can be configured to implement part or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 512 can be configured as a programmable hardware element(s) such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512 can be configured, together with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, to implement some or all of the features described herein.

[0070] Further, as described herein, the processor 512 can include one or more processing elements. Thus, the processor 512 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 512. In addition, each integrated circuit can include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor 512.

[0071] As described herein, modem 520 can include hardware and software components for implementing the above-described features for determining physical downlink shared channel scheduling resources for user equipment devices and base stations, as well as for various other techniques described herein. For example, processor 522 can be configured to implement part or all of the feature sets described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 522 can be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336 can be configured to implement part or all of the feature sets described herein.

[0072] Further, as described herein, processor 522 can include one or more processing elements. Thus, processor 522 can include one or more integrated circuits (ICs) that are configured to perform the functions of the processor 522. In addition, each integrated circuit can include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor 522.

[0073] NR-U Listen-Before-Talk (LBT) channel access mechanisms can be based on the ED-based LBT of License Assisted Access (LAA). Two types of LBT channel access mechanisms include Frame Based Equipment (FBE) access, Load Based Equipment (LBE) access. For FBE, the transmit / receive structure has a periodic timing with a period equal to a fixed frame period. For LBE, the transmit / receive structure is not fixed in time but is driven by demand. There are four categories of LBT defined in LAA LBE operation, which can be used as a baseline for NR-U. Category 1 is no LBT (i.e., immediate transmission). Category 2 is LBT without random backoff. Category 3 is LBT with random backoff with a fixed size contention window. Category 4 is LBT with random backoff with a variable size contention window.

[0074] After a successful LBT, the initiating device can access the channel for a duration of a maximum channel occupancy time (MCOT). Sharing of channel occupancy time (COT) can be performed in any direction between the initiating node and the responding node, such as, for example, gNB-acquired COT sharing and UE-acquired COT sharing. There are two MCOT structures including LAA and NR-U. LAA has a single DL-to-UL switch. This provides less overhead due to a single GP, and avoids multiple LBTs. One drawback here is that there can be a large delay for HARQ-ACK feedback.

[0075] NR-U also supports multiple DL-to-UL and UL-to-DL switches. This can result in reduced latency for latency sensitive traffic (e.g., URLLC). In NR-U, if the gap between DL and UL or UL and DL is within 16μ8 (same as SIFS in Wi-Fi), the transmission after the gap can occur without channel sensing, i.e., Cat-1 LBT. If the gap is greater than 16μ8 but less than 25μ8, Cat-2 is allowed.

[0076] For initiation of COT by a gNB (operating as an LBE device), the channel access schemes in the following table can be used.

[0077]

[0078] Table 1 - Channel access schemes for gNB as LBE device

[0079] At least for UL burst following a DL burst by a gNB and in the absence of a gap greater than 25μ8 between any two transmissions in the COT, the channel access schemes in the following table apply.

[0080]

[0081] Table 2 - Channel access schemes for DL burst following gNB as LBE device

[0082] UL burst within initiated COT

[0083] A DL / UL burst is defined as a set of transmissions from a given gNB / UE without a gap or with a gap not exceeding 16μ8. Transmissions from a gNB / UE with a gap greater than 16μ8 are considered as separate DL / UL bursts.

[0084] Within a gNB initiated COT, the channel access schemes for UL burst by a UE consisting of one or more of physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), physical random access channel (PRACH), and sounding reference signal (SRS) follow the table below.

[0085]

[0086] Table 3 - Channel access schemes for gNB initiated UL burst

[0087] For initiation of COT by a UE, the channel access schemes in the following table can be used - Cat-4 LBT is used for PUSCH with UCI only.

[0088]

[0089] Table 4 - Channel access schemes for COT initiation by UE

[0090] Three different channel access mechanisms for hybrid MAC for 60GHz include CSMA / CA, TDMA, and polling. CSMA / CA is suitable for bursty traffic. Ideally, CSMA / CA requires omni transmit and receive beams. In directional CSMA / CA, the gNB is omni and the UE is directional. In pairwise CSMA / CA, the UE switches beams for listening and speaking. (e.g., listening is omni, or in opposite direction). For 802.11ad, during contention-based access period, enhanced 802.11 EDCA includes traffic categories for supporting quality of service, frame aggregation, and block acknowledgement.

[0091] TDMA is suitable for large file transfer or wireless display, and / or when the UE is in a non-interference area. Regarding 802.11ad with TDMA, a service period can be dedicated to a pair of communicating nodes. The HCF is extended.

[0092] Polling can be performed in contention-based period and service period. During polling, the AP performs a ping operation for each UE to get data (directional SR), the UE replies (directional PUCCH), the gNB schedules the UE and the UE transmits. Regarding 802.11ad and polling, dynamic channel time allocation is used. The PCP / AP acquires the medium, the PCP / AP sends a poll frame, the STa sends a service period request (SPR), the PCP / AP applies a grant frame allocating time.

[0093] Hybrid MAC can be a mix of all three channel access mechanisms. Hybrid MAC is used in 802.11ad.

[0094] Regarding channel access frame structure, a beacon interval can include a beacon header interval (BHI) and a data transfer interval (DTI). The BHI uses a sweep of multiple directional transmission frames to facilitate the exchange of management information and network announcements. In the BTI, multiple beacon frames (MCS0) can be applied to perform sector-level sweep. In an associated beamforming training (A-BFT) time slot, a responder sector-level sweep (MCS0) can be performed. In an announcement transfer interval (ATI), the PCP / AP exchanges management information with associated and beam trained stations (MCSx).

[0095] DTI enables different types of medium access. Scheduling can be announced by the PCP / AP. During DTI, multiple contention-based access periods (CBAPs) can be performed using a variant of enhanced distributed coordination function (EDCF). In some cases, multiple service periods (SPs) rather than CBAPs: communication between dedicated node pairs in a contention-free period. Dynamic channel allocation can be supported by the PCP / AP polling STAs within CBAPs or SPs and dynamically allocating resources. In dynamic channel allocation, scheduling can be conveyed by an extended schedule element. In this case, using pseudo-static access, dynamic scheduling repeats with the same relative offset and for the same duration as the target beacon transmission time (TBTT).

[0096] Scheduling / pseudo-static contention-based access can also be performed, such as CSMA / CA for dynamic channel access. Scheduling can be sent in CBAPs. Scheduling can include traffic categories to support quality of service, frame aggregation, and block ACK. This access method supports multiple NAV timers (one per peer STA), e.g., if the NAV for a device is 0, the device can initiate transmission.

[0097] Scheduling / pseudo-static TMDA channel time allocation (TDMA) can be performed. The PCP / AP can broadcast scheduling in a schedule element immediately following a BTI or ATI. Scheduling is sent in service periods (SPs). This access method allows D2D transmissions and supports multiple NAV timers (one per peer STA) for protected mode transmissions.

[0098] Dynamic channel time allocation (polling) can be performed. In this case, STAs can poll to receive a SPR (service period request). An authorization frame is used to allocate time based on the request. This access method can be used for both CBAPs (PCP / AP uses PIFS) and SPs.

[0099] For time periods scheduled by the AP / PCP where any STA can access the channel, access during CBAPs is based on EDCA. All CBAPs are allocated by the AP or PCP, unless allocated by a non-AP and non-PCP STA when transmitting an authorization frame after an SP truncation. There can be multiple CBAPs in a beacon interval. The PCP / AP can initiate frame transmission within a CBAP immediately after the medium is determined to be idle for one PIFS (8 μsec). Operation of the EDCAF is suspended at the end of a CBAP and resumes at the start of the following CBAP. Frames sent by a STA at the start of a TXOP can be an RTS frame or a DMG CTS-to-self frame.

[0100] Within a CBAP, a STA with multiple DMG antennas shall use only one DMG antenna for its frame transmission, CCA and frame reception, unless it is the initiator or responder in SLS (10.42 (DMG beamforming)). In this case, the algorithm for selecting the DMG antenna and switching the active DMG antenna depends on the implementation. Within a CBAP, a STA that changes to a different DMG antenna for transmission shall perform CCA on that DMG antenna until it detects a frame for which it can set its NAV or until a time period equal to dotllDMGNavSync has elapsed, whichever occurs first.

[0101] The service period can be negotiated between the AP / PCP and the STAs or dynamically allocated, where only the specified STAs can access the channel. The service period can be broadcast to multiple STAs, used for D2D transmission, dynamically extended beyond the allocated time in the current SP in specific scenarios, and / or dynamically truncated to release the remaining time in the SP if it is truncatable.

[0102] Regarding the service period recovery procedure; when a non-AP and non-PCP STA fails to receive the extended schedule element for a beacon interval, the non-AP and non-PCP STA does not know the non-pseudo-static SP allocated during the beacon interval indicating that it is the source DMG STA; therefore, it cannot transmit during these SPs. If the destination of the non-pseudo-static SP is the AP or PCP and it does not receive any frames from the source non-AP and non-PCP STA within the super interval, the AP / PCP can truncate the SP and re-allocate the remaining duration of the SP to the source DMG STA of the SP or other STAs, provided that it is a truncatable SP. If it is not truncatable, it can remain idle or enter a sleep state. If the non-AP / non-PCP STA does not receive the extended schedule element from the AP or PCP within the beacon interval, it can switch to a sleep state or can point its receive antenna to the AP or PCP to receive the grant during the non-pseudo-static SP or CBAP in the current beacon interval.

[0103] A protection period can be implemented to minimize interference between pairs of communicating STAs. The protection period can be implemented by limiting frame transmission during the DMG protection period to no more than one pair of potentially interfering communicating stations. Dynamic BW operation can be used to negotiate the BW to be used by the SP. The STAs can be set to listen mode in the interval preceding the SP and transmit only in case of idle (CAT2 type access). In this case, the antennas are in quasi-omni mode or pointed to the peer DMG STA. The protection period can be established by an RTS / DMG CTS signal exchange. Interference can be reported to the PCP / AP.

[0104] Dynamic allocation of service periods can be employed to allocate channel time during scheduled SPs and CBAPs. Dynamic allocation can include an optional Polling Period (PP) phase and a Grant Period (GP) phase.

[0105] With respect to channel access intervals, CAT 4 applies before BI. Fixed intervals apply within BTI and A-BFT. In this case, MBIFS should be used between BTI and A-BFT and between ISS, RSS, SSW feedback and SSW-Ack. MBIFS is equal to 3 x aSIFSTime. A-BFT can use MBIFS between packets in a slot to divide the slot. Between A-BFT and ATI, the larger of (protection time, MBIFS) applies. Within ATI, the AP or PCP can start transmission of request frames immediately upon the start of ATI, or can delay transmission of request frames if the CCA mechanism determines the medium is busy. The response is SIFS from the request frame. The source initiates at the start of SP, unless a protection period needs to be established, i.e., based on RTS / DMG CTS transmission listening to the medium. Reply (SIFS) and / or retransmission (PIFS) can be performed in SP. In CBAP, CAT4 applies. PIFS applies for PCP / AP or other sources. SBIFS and / or SIFS are used for polling.

[0106] For communications operating at >52.6 GHz (e.g., 5G-NRU), it can be desirable for a gNB to perform dynamic polling of all UEs to identify which UEs have data and modify their resource allocation accordingly. This allows for flexible reallocation of time and beam resources in mmWave transmissions.

[0107] Satisfactory communications can require beams in the direction of the UE. Due to beam-based allocation, a UE can only be able to dynamically send an SR when its beam pair is active. If the beam pair is dynamically changing, the UE can not know whether the beam is active to send an SR and request resources. In this case, statically allocating resources can be deficient. Thus, communications can benefit from dynamic SR in an NR or NR-U environment.

[0108] SR using PRI in DCI to indicate a set of semi-statically configured PUCCH resources identified by a first symbol, a number of symbols, and other parameters can lack flexibility. Additional flexibility can be needed to indicate PUCCH resources relative to the DCI and appropriate signaling within the DCI. Thus, dynamic SR configuration can provide improved flexibility.

[0109] If the PUCCH resource is dynamically changed and DCI is used to signal the PUCCH resource, the overhead of signaling the presence of SRI in DCI can be high. To reduce the overhead, in some aspects, the PUCCH resource signaling for dynamic SR can be part of the existing DCI transmission. In some aspects, dedicated PUCCH resource signaling is used for dynamic SR. In some aspects, semi-static configuration can reduce the overhead.

[0110] Based on LBT failure, a method can be needed to enable reliable PUCCH and PUSCH transmission. For example, multiple PUCCH resources can be signaled. To communicate on PUSCH, additional information can also be needed in the SR feedback, enabling the gNB to identify the best resource to send information in, for example, a beam, CC, or BWP. Multiple resources can be signaled for PUSCH transmission.

[0111] In some aspects, there can be a timeline issue for signaling of dynamic resources. A time gap can be implemented between signaling. The gap can be determined based on the number of beams and / or processing time.

[0112] Reference Figure 6 Dynamic scheduling is shown in accordance with some aspects. Dynamic scheduling can be performed on 5G NR or 5G NR-U.

[0113] At operation 602, the base station can transmit configuration information to a user equipment (UE) indicating how to find the DCI. The configuration information describes where the DCI is located (e.g., a location within a COT allocated to the base station).

[0114] In some aspects, the configuration information defines a search space (SS) that the UE can use to locate the DCI (e.g., within the COT). The search space can be an area (e.g., defined as a block of time or data) in downlink resources that is defined for the UE to perform blind decoding to attempt to find data (e.g., the DCI).

[0115] In some aspects, the search space is defined to be fixed relative to the start of the COT. For example, the search space can be defined as “x” resource blocks starting from “y” symbols after the start of the COT. In some aspects, the search space can be defined as part of downlink burst signaling. For example, the search space can be defined as a set of common physical downlink control channel (GC-PDCCH) COTs in a time / frequency domain structure.

[0116] In some aspects, the configuration information can specify the exact location of the DCI rather than defining a search space. The receiving UEs are configured with the exact location of the DCI in the received transmission to decode the DCI accordingly. In some aspects, the configuration information can define the DCI to be located relative to a numerology. For example, the DCI can be defined to have a location relative to a particular resource block and symbol. The symbol can be an OFDM symbol that describes a time slot in a frequency band of a particular channel. The numerology refers to a configuration of waveform parameters. Different numerologies can be considered as OFDM-based subframes with different parameters such as subcarrier spacing / symbol time, CP size, etc.

[0117] In some aspects, the configuration information defines the DCI message to be located relative to the start of the COT. For example, the DCI message can be defined in the configuration information to be “x” resource blocks starting from “y” symbols fixed relative to the start of the COT. In some aspects, the configuration information defines the DCI to be part of downlink burst signaling. For example, the DCI location can be defined in the configuration information to be in a group common physical downlink control channel (GC-PDCCH) COT in a time / frequency domain structure.

[0118] The UE can receive configuration information from the base station that includes details on how to find the DCI message (e.g., in a COT).

[0119] At operation 603, the base station can request network resources, such as a channel occupancy time (COT) or maximum channel occupancy time (MCOT) of a channel, from the network. The network can determine a COT or MCOT to allocate to the base station and send a response including the COT or MCOT to the base station at operation 604. In some aspects, the resource request 603 is performed through a contention-based protocol (e.g., LBT). In some aspects, the network resources are statically configured, e.g., the base station has a statically allocated channel and time. The network can include a mix of network devices sharing bandwidth on a common frequency.

[0120] At operation 604, the network can send a response to the base station allocating channel resources. For example, the response can define a COT or MCOT in which the base station is free to use the channel. It should be understood that operation 602 can occur before and / or after operations 603 and 604.

[0121] At operation 616, the base station can generate a DCI. The DCI can indicate to each of the one or more UEs what PUCCH resource the UE should use to transmit a dynamic SR. The PUCCH resource can include a symbol (e.g., 10, 16, 18) that defines to the UE and the base station through which beam pair and / or time the dynamic SR will be communicated. The PUCCH resource can be dynamically updated based on one or more network conditions, including network traffic, location of the one or more UEs, or which of the one or more UEs has data to transmit. Details of the PUCCH resource are discussed in other sections. The DCI can be of format 2 0, 2 1, 2 2, or other downlink DCI formats that currently exist or are developed in the future.

[0122] At operation 606, the base station can poll the one or more UEs (such as the UE shown) by transmitting a DCI. The PUCCH resource associated with each of the one or more UEs indicated in the DCI can change over time based on network conditions. The DCI transmission can be performed periodically or whenever a network condition changes, which can prompt a change in the PUCCH resource allocation to the one or more UEs. Figure 6

[0123] At operation 618, the UE can receive / decode the DCI and find the DCI based on the configuration information received at operation 602, as described in other sections. The UE can decode the DCI to determine the PUCCH resource to use for transmitting a dynamic SR.

[0124] The PUCCH resource can be signaled to the UE in different ways. In some aspects, the DCI includes a PUCCH resource indicator (PRI) that has a bit field indicating the PUCCH resource to use for a dynamic SR. The PUCCH resource can be a 3-bit indicator included as part of the DCI, which can be of format 1 0 or 1 1. The PUCCH resource for HARQ is typically signaled in the PRI as part of the DCI format 1 1, which can be 3 bits. A new field can be added, or additional bits can be added (e.g., to form a 4-bit PRI), to indicate whether the PRI is associated with a hybrid automatic repeat request (HARQ) or a dynamic SR. In some aspects, the dynamic SR can be multiplexed with a HARQ transmission, rather than having separate PUCCH resources for HARQ and dynamic SR.

[0125] Understanding that a PUCCH resource can be needed for both HARQ and SR, and that the PUCCH resource can be semi-statically configured to identify an absolute first symbol location, a number of symbols, and other parameters, there are a few options below that can use a new table (different from the semi-statically configured look up) or a subset of the semi-statically configured look up.​

[0126] In some aspects, the UE finds the PUCCH resource based on a) a subset of the semi-static PUCCH lookup, and b) a relative first symbol position relative to a location of the PRI in the DCI. For example, if the PRI is received in symbol n and indicates a relative first symbol position x, the PUCCH resource can be in or start from symbol (n+x). The subset can be the first m entries of the table or a configured subset of m entries of the table.

[0127] In some aspects, the UE finds the PUCCH resource based on a) a subset of the semi-static PUCCH lookup, and b) a relative first symbol position relative to a location of the PRI in the DCI. For example, if the PRI is received in symbol n and indicates a relative first symbol position x, the PUCCH resource can be in or start from symbol (n+x). The subset can be the first m entries of the table or a configured subset of m entries of the table.

[0128] In some aspects, the dynamic SR includes or is multiplexed with channel state information (CSI). CSI is a mechanism that allows a UE to report measured radio channel quality to a base station.

[0129] In some aspects, PUCCH resource signaling is performed by allocating a CRC or a scrambled CRC to the UE. The CRC or scrambled CRC can be allocated to one or more UEs. For example, the CRC can be scrambled using a demodulation reference signal (DRS) radio network temporary identifier (RNTI), and the RNTI can be allocated to the UE. The CRC or scrambled CRC can indicate to the UE which bit field in the DCI carries the PUCCH resource indicator for the UE. A single DCI can carry multiple UE-specific bit fields, each of which carries a PUCCH resource for a dynamic SR transmission by a corresponding UE.

[0130] For example, with reference to Figure 7 , the UE (e.g., UE (N)) is one of multiple UEs, and the DCI includes multiple bit fields, each allocated to a corresponding one of the one or more UEs. The PUCCH resource (e.g., one or more symbols) that the UE uses to transmit the dynamic SR is indicated in the bit field allocated to the UE.

[0131] In some aspects, each bit field can be allocated to a corresponding one of the one or more UEs based on a radio network temporary identifier (RNTI). For example, a cyclic redundancy check (CRC) of the entire DCI or each bit field is scrambled using an RNTI, and each RNTI is allocated to each of the one or more UEs.

[0132] The UE can use each RNTI to find a bitfield assigned to the UE. The starting position and number of bits (e.g., if the size is variable) of each bitfield of the plurality of bitfields can be semi-statically configured. In some aspects, only the starting position is sufficient (e.g., if the size bitfield is not variable). The PUCCH resource of the UE is indicated in one of the plurality of bitfields (e.g., as a value), and the PUCCH resources for other UEs of the plurality of UEs are located in other bitfields of the plurality of bitfields. In some aspects, a bitfield dedicated to a single UE can signal more than one PUCCH resource in case of LBT failure of a single resource. In some aspects, the DCI has a format of 2_6 or a group common DCI.

[0133] Upon successfully decoding the PUCCH resource (e.g., the UE finding the PUCCH resource), the UE can transmit the dynamic SR in the designated PUCCH resource. If the decoding of the PUCCH resource is not successful (e.g., the UE fails to find the PUCCH resource), the UE can refrain from transmitting the dynamic SR.

[0134] Referring back to Figure 6 At operation 608, the UE can transmit a dynamic SR in a PUCCH message based on the PUCCH resource indicated in the DCI. For example, the PUCCH resource can include a symbol (e.g., 10, 16, 18) that defines to the UE and gNB which beam pair and / or time will be used to transmit the dynamic SR. The SR is transmitted on the PUCCH message as defined by the symbol (e.g., using a particular beam pair at a particular time). The symbol format and PUCCH format can vary based on the application.

[0135] In some aspects, the dynamic SR transmitted from the UE to the base station can include PUCCH signaling for increased reliability. This can be used to help the base station determine resources for data transmission.

[0136] For example, as Figure 8 shown, the UE can include additional information (e.g., UE assistance for LBT) in the dynamic SR to enable the gNB to identify improved resources to send information in the scheduling phase. This can include, for example, a beam, a listen-before-talk (LBT) band, a time slot to transmit, and a bandwidth part (BWP). In some aspects, the UE transmits the dynamic SR only when the UE wishes to reserve the time slot and / or has data to send to the base station and / or has successfully found and decoded the PUCCH resource.

[0137] At operation 620, the base station can process the SRs to determine which resources the uplink transmissions will use. In other words, the base station determines which PUSCH resources the UE will use for the UL transmission of data. This determination can be based on network traffic, SR requests from other UEs (which can be used to schedule traffic to and from multiple UEs), and information sent back from the UE in the dynamic SR request at operation 608 (e.g., UE assistance for LBT).

[0138] At operation 610, the base station can transmit an UL grant to the user equipment, which can be a scheduling DCI (e.g., format 0_X). At operation 612, the UE can transmit UL data to the base station on the UL resources specified in the UL grant.

[0139] In some aspects, the DCI resources and corresponding dynamic SR resources (e.g., PUCCH resources) can be semi-statically configured together. In this case, a single bit (or a bit field of each bit corresponding to a particular UE) can be configured to indicate whether the UE should transmit a dynamic SR in the predetermined resources. The bit or bit field can be transmitted by the base station to one or more UEs and dynamically updated (e.g., from one time to another, and / or between periodic transmissions of the DCI) based on one or more network conditions, including network traffic, locations of the one or more UEs, or which of the one or more UEs have data to transmit or changes thereto.

[0140] For example, referring to Figure 9 , a bit field 900 is shown, which can be included in a DCI (or other suitable downlink communication), can indicate to one or more UEs whether each of the one or more UEs should transmit a dynamic SR. In this case, the PUCCH resources are semi-statically configured, rather than included in the DCI. In some aspects, the bit field need not be carried in the DCI, but can be carried in another suitable downlink communication from the base station to the UE. In other words, in the case of semi-statically configuring dynamic SR resources, operation 602 of Figure 6 may be bypassed, and operation 606 need not include a polling DCI, but can be any suitable downlink communication that carries the described bit field. The UE need not find the PUCCH resource, as the UE will “know” which PUCCH resource to use for the dynamic SR based on the semi-static configuration. For example, the base station can configure the UE to use symbol 10. As long as the bit corresponding to the UE is set in the received poll, the UE will use symbol 10 to transmit the dynamic SR.

[0141] It should be understood that semi-static configuration (e.g., from the base station to the UE and vice versa) can be performed via Radio Resource Control (RRC) communication between the base station and the UE. The RRC protocol may include connection establishment and release functions, broadcasting of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release, and outer loop power control. The UE is configured via signaling functions (e.g., semi-statically).

[0142] Figure 10 An example of SR scheduling using multiple UEs is shown. During polling period 1001, the base station can poll N UEs. A corresponding SR can be used to respond to some or all UEs. During granting period 1002, the base station can transmit UL grants to the UEs (e.g., in the form of scheduling DCIs). UL transmission can be performed during data transmission period 1003.

[0143] Figure 11 The flowchart illustrates dynamic scheduling based on several aspects. In block 1101, DCI configuration is sent from the base station to the UE. This tells the UE how to find the DCI or where it is expected to be found. In block 1102, the DCI is sent to the UE. In block 1103, a dynamic SR is sent from the UE to the base station. In block 1104, UL authorization is sent from the base station to the UE, and data is sent from the UE to the base station.

[0144] refer to Figure 12 It shows something similar to Figure 11 The flowchart for dynamic scheduling is provided; however, in this case, due to beam switching and processing time, a minimum time interval may be implemented between the elements of dynamic scheduling (e.g., DCI, dynamic SR, scheduled DCI, and / or transmission). Therefore, time intervals may be implemented between some communications between the UE and the base station (e.g., between receiving a DCI and transmitting a dynamic SR, or between receiving a dynamic SR and transmitting a UL grant). The time interval may be greater than or equal to the greater of a) the time required to change from one beam to another (e.g., the time for the UE and / or the base station), or b) the processing time (e.g., the UE's processing time).

[0145] Processing time is either fixed to a value based on 120kHz or modified to account for new subcarrier spacing (SCS) values ​​(e.g., 240kHz, 480kHz, 960kHz, etc.). Beam switching time can be based on (e.g., the UE's) existing beam switching time constraints. The gNB can schedule each element of the process in groups. This scheduling can be transparent to the UE. In some respects, for 120kHz, tproc2 = 20 symbols. Therefore, the interval between DCI and dynamic SR should be at least 20 symbols.

[0146] Portions of what was described above can be implemented with logic circuitry such as a special purpose logic circuitry or microcontroller or other form of processing core that executes program code instructions. Thus, those instructions and their operation can implement the processes taught by the foregoing discussion, and the general principles described above can be implemented alongside the analog circuitry or can be implemented by the analog circuitry itself. The various operations can be performed by processing logic that can be loaded into the processors (or microcontrollers) and caused such a processor to perform the operations described above. One skilled in the art will recognize that the processes taught by the foregoing discussion are capable of implementation using a variety of specific hardware configurations, and that the actual specific processor or microcontroller should not be limiting of the scope of the application. The processes taught by the foregoing discussion can also be implemented by electronic circuitry that is designed using a hardware description language (HDL) such as Verilog, VHDL, or the like, and that is then synthesized onto a semiconductor chip using a synthesis tool such as Synopsys Design Compiler, or the like. The processes taught by the foregoing discussion can also be implemented by a hardware circuit that is designed using a hardware description language (HDL) such as Verilog, VHDL, or the like, and that is then synthesized onto a semiconductor chip using a synthesis tool such as Synopsys Design Compiler, or the like. The processes taught by the foregoing discussion can also be implemented by a hardware circuit that is designed using a hardware description language (HDL) such as Verilog, VHDL, or the like, and that is then synthesized onto a semiconductor chip using a synthesis tool such as Synopsys Design Compiler, or the like.

[0147] The present application also relates to an apparatus for performing the operations described herein. This apparatus can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), RAMs, EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

[0148] The machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes read-only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; etc.

[0149] A baseband processor (also referred to as a baseband radio processor, BP, or BBP) is a device (chip or part of a chip) in a network interface that manages radio functions such as communicating (e.g., TX and RX) on an antenna.

[0150] An article of manufacture can be used to store program code. An article of manufacture that stores program code can be embodied as, but is not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic or other)), optical disks, CD-ROMs, DVDs ROM, EPROMs, EEPROMs, magnetic or optical cards, other type of machine readable media suitable for storing electronic instructions, or properly formatted physical media. Program code can also be downloaded from a remote computer (e.g., server) to a requesting computer (e.g., client) by way of data signals embodied in a transmission medium (e.g., carrier waves).

[0151] The foregoing detailed description has presented the algorithmic aspects of the present application in terms of operations performed by computer memory components. The algorithms describe and represent the steps of the processes of the present application in a manner that is sufficiently enabling for the person of skill in the art to carry out the processes described by the algorithms. The algorithms have been presented in terms of their essential nature, and in a manner that best conveys the principles of the application to others skilled in the art. The algorithms are described and represented in a manner that is most useful for most effectively conveying the principles of the present application to others skilled in the art.

[0152] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as "selecting" "determining" "receiving" "forming" "grouping" "aggregating" "generating" "removing" or the like, refer to the actions and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers, or other such information storage, transmission or display devices.

[0153] The processes and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct more specialized apparatus to perform the operations of the present application. The required structure for a variety of these systems will be apparent from the description below. In addition, the present application is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings of the application as described herein.

[0154] It is well understood that, in all cases where personally identifiable information is used, it should be in compliance with the privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, the personally identifiable information data should be managed and handled in a manner that minimizes risk of unauthorized or unintended access or use. In addition, users should be given an opportunity to opt in or opt out of data collection, sharing, profiling, and / or merging of their personal information with data from third parties.

[0155] The foregoing discussion merely describes some exemplary aspects of the application. Various modifications to these descriptions will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein.

Claims

1. A method performed by network equipment in 5G New Radio (NR) in a licensed or unlicensed spectrum environment, comprising: generating a downlink control information (DCI) message, the DCI message containing an indication of a physical uplink control channel (PUCCH) resource for a UE to use to transmit a dynamic scheduling request (SR); polling the UE by transmitting the DCI including the PUCCH resource, the PUCCH resource being dynamically updated based on one or more network conditions, the one or more network conditions including network traffic, location of one or more UEs, or which of the one or more UEs has data to transmit, wherein the UE is one of the one or more UEs, and the DCI includes a plurality of bit fields, each bit field being assigned to a corresponding one of the one or more UEs, and wherein a starting position and a number of bits of each of the plurality of bit fields is radio resource control (RRC) configured; receiving the dynamic SR in a PUCCH message transmitted according to the PUCCH resource; and transmitting an uplink (UL) grant determined based on the dynamic SR.

2. The method of claim 1, wherein the DCI is transmitted on a channel during a specified channel occupancy time (COT).

3. The method of claim 2, further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines a search space for the UE to use to locate the DCI within the COT.

4. The method of claim 3, wherein the search space is fixed relative to a start of the COT or is defined as part of downlink burst signaling.

5. The method of claim 2, wherein the COT is allocated to the network equipment statically or through a contention-based protocol.

6. The method of claim 2, further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI as being located relative to a start of the COT.

7. The method of claim 1, further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI as being located relative to a numerology.

8. The method of claim 1, further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI as part of downlink burst signaling.

9. The method of claim 1, wherein the DCI includes a PUCCH resource indicator (PRI) having a bit field indicating the PUCCH resource to use for the dynamic SR.

10. The method of claim 9, wherein the bit field indicates whether the PRI is associated with a hybrid automatic repeat request (HARQ) or the dynamic SR.

11. The method of claim 9, wherein the UE finds the PUCCH resource based on a) a resource lookup that is different from a semi-static PUCCH lookup, and b) a relative first symbol position relative to a position of the PRI in the DCI.

12. The method of claim 9, wherein the UE finds the PUCCH resource based on a) a subset of semi-static PUCCH lookups, and b) a relative first symbol position relative to a position of the PRI in the DCI.

13. The method of claim 1, wherein the dynamic SR is multiplexed with a hybrid automatic repeat request, HARQ, transmission.

14. The method of claim 1, wherein the dynamic SR includes channel state information, CSI.

15. The method of claim 1, wherein the PUCCH resource for the UE is indicated in the bitfield allocated to the UE.

16. The method of claim 1, wherein assigning each bit field to the corresponding one of the one or more UEs comprises: the DCI is scrambled using a radio network temporary identifier, RNTI, that is allocated to each of the one or more UEs.

17. The method of claim 1, wherein a number of bits of each of the plurality of bitfields is RRC configured.

18. The method of claim 1, wherein the DCI has a format of 2_6 or is a group common DCI.

19. The method of claim 1, wherein the UE transmits the dynamic SR if the PUCCH resource is successfully found, but does not transmit the dynamic SR if the PUCCH resource is not successfully found.

20. The method of claim 1, wherein UL resources including beam and time scheduling that are included in the UL grant are determined based on information included in the dynamic SR, the information including one or more of: a beam, a listen-before-talk, LBT, band, a time slot to be transmitted, and a bandwidth part, BWP.

21. The method of claim 1, wherein a time interval implemented between receiving the dynamic SR and transmitting the UL grant is greater than or equal to a larger of: a) a time needed to change from one beam to another beam, or b) a processing time.

22. A method performed by network equipment in 5G New Radio in an unlicensed spectrum environment, comprising: generating a downlink control information, DCI, or a downlink communication, the DCI or the downlink communication including a bit indicating whether a user equipment, UE, sends a dynamic scheduling request, SR; polling the UE by transmitting a DCI or the downlink communication including the bit, the bit being dynamically updated based on one or more network conditions, the one or more network conditions including network traffic, location of one or more UEs, or which of the one or more UEs has data to transmit, wherein the UE is one of the one or more UEs, and the DCI includes a plurality of bit fields, each bit field being assigned to a corresponding one of the one or more UEs, and wherein a starting position and a number of bits of each bit field of the plurality of bit fields is radio resource control, RRC, configured; receiving the dynamic SR in a physical uplink control channel, PUCCH, message; and transmitting an uplink, UL, grant determined based on the dynamic SR.

23. The method of claim 22, wherein the DCI or the downlink communication is transmitted on a channel during a designated channel occupancy time, COT.

24. The method of claim 23, wherein the COT is allocated to the network equipment statically or through a contention-based protocol.

25. The method of claim 22, wherein the bit is one of a plurality of bits included in the DCI or the downlink communication, each bit of the plurality of bits being associated with a corresponding UE of a plurality of UEs, and each bit of the plurality of bits indicating to the corresponding UE whether to transmit a corresponding dynamic SR, wherein each UE of the plurality of UEs is configured with a corresponding predetermined PUCCH resource.

26. The method of claim 22, wherein UL resources including beam and time scheduling included in the UL grant are determined based on information contained in the dynamic SR, the information including one or more of: a beam, a listen-before-talk, LBT, frequency band, and a bandwidth part, BWP.

27. The method of claim 22, wherein a time interval implemented between receiving the dynamic SR and transmitting the UL grant is greater than or equal to a greater of: a) a time needed to change from one beam to another beam, or b) a processing time.

28. The method of claim 22, wherein a location of the bit is radio resource control, RRC, configured.

29. The method of claim 22, wherein the PUCCH resource is radio resource control, RRC, configured.

30. A base station comprising a processor or processing circuitry configured to perform operations comprising: generating a downlink control information, DCI, message, the DCI message containing an indication of a physical uplink control channel, PUCCH, resource for a UE to use to transmit a dynamic scheduling request, SR; polling the UE by transmitting the DCI including the PUCCH resource, the PUCCH resource being dynamically updated based on one or more network conditions, the one or more network conditions including network traffic, location of one or more UEs, or which of the one or more UEs has data to transmit, wherein the UE is one of the one or more UEs, and the DCI includes a plurality of bit fields, each bit field being assigned to a corresponding one of the one or more UEs, and wherein a starting position and a number of bits of each bit field of the plurality of bit fields is radio resource control (RRC) configured; receiving the dynamic SR in a PUCCH message transmitted according to the PUCCH resource; and transmitting an uplink (UL) grant determined based on the dynamic SR.

31. The base station of claim 30, wherein the DCI is transmitted on a channel during a designated channel occupancy time (COT).

32. The base station of claim 31, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines a search space used by the UE to locate the DCI within the COT.

33. The base station of claim 32, wherein the search space is fixed relative to a start of the COT or is defined as part of downlink burst signaling.

34. The base station of claim 31, wherein the COT is allocated to the base station statically or through a contention-based protocol.

35. The base station of claim 31, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI as being located relative to a start of the COT.

36. The base station of claim 30, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI as being located relative to a numerology.

37. The base station of claim 30, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI as part of downlink burst signaling.

38. The base station of claim 30, wherein the DCI includes a PUCCH resource indicator (PRI) having a bit field indicating the PUCCH resource to be used for the dynamic SR.

39. The base station of claim 38, wherein the bit field indicates whether the PRI is associated with a hybrid automatic repeat request (HARQ) or the dynamic SR.

40. The base station of claim 38, wherein the UE finds the PUCCH resource based on a) a resource lookup that is different from a semi-static PUCCH lookup, and b) a relative first symbol position relative to a position of the PRI in the DCI.

41. The base station of claim 38, wherein the UE finds the PUCCH resource based on a) a subset of semi-static PUCCH lookups, and b) a relative first symbol position relative to a position of the PRI in the DCI.

42. The base station of claim 30, wherein the dynamic SR is multiplexed with a hybrid automatic repeat request, HARQ, transmission.

43. The base station of claim 30, wherein the dynamic SR includes channel state information, CSI.

44. The base station of claim 30, wherein the PUCCH resource for the UE is indicated in the bitfield assigned to the UE.

45. The base station of claim 30, wherein assigning each bit field to the corresponding one of the one or more UEs comprises: a cyclic redundancy check of the DCI is scrambled using a radio network temporary identifier, RNTI, assigned to each of the one or more UEs.

46. The base station of claim 30, wherein a number of bits of each of the plurality of bitfields is RRC configured.

47. The base station of claim 30, wherein the DCI has a format of 2_6 or is a group common DCI.

48. The base station of claim 30, wherein the UE transmits the dynamic SR if the PUCCH resource is successfully found, but does not transmit the dynamic SR if the PUCCH resource is not successfully found.

49. The base station of claim 30, wherein UL resources including beam and time scheduling included in the UL grant are determined based on information included in the dynamic SR, the information including one or more of: a beam, a listen-before-talk, LBT, band, a time slot to transmit, and a bandwidth part, BWP.

50. The base station of claim 30, wherein a time interval implemented between receiving the dynamic SR and transmitting the UL grant is greater than or equal to a greater of: a) a time needed to change from one beam to another beam, or b) a processing time.

51. A base station comprising a processor or processing circuitry configured to perform operations comprising: generating a downlink control information, DCI, or a downlink communication, the DCI or the downlink communication including a bit indicating whether a user equipment, UE, sends a dynamic scheduling request, SR; polling the UE by transmitting the DCI or the downlink communication including the bit, the bit being dynamically updated based on one or more network conditions, the one or more network conditions including network traffic, a location of one or more UEs, or which of the one or more UEs has data to transmit, wherein the UE is one of the one or more UEs, and the DCI includes a plurality of bitfields, each bitfield assigned to a corresponding one of the one or more UEs, and wherein a starting position and a number of bits of each of the plurality of bitfields is radio resource control, RRC, configured; receiving the dynamic SR in a physical uplink control channel, PUCCH, message; and transmitting an uplink, UL, grant based on the dynamic SR determination.

52. The base station of claim 51, wherein the DCI or the downlink communication is transmitted on a channel during a designated channel occupancy time, COT.

53. The base station of claim 52, wherein the COT is allocated to the base station statically or through a contention-based protocol.

54. The base station of claim 51, wherein the bit is one of a plurality of bits included in the DCI or downlink communication, each of the plurality of bits is associated with a corresponding UE of a plurality of UEs, and each of the plurality of bits indicates to the corresponding UE whether to transmit a corresponding dynamic SR, wherein each UE of the plurality of UEs is configured with a corresponding predetermined PUCCH resource.

55. The base station of claim 51, wherein UL resources including beam and time scheduling included in the UL grant are determined based on information contained in the dynamic SR, the information including one or more of: a beam, a listen-before-talk, LBT, band, and a bandwidth part, BWP.

56. The base station of claim 51, wherein a time interval implemented between receiving the dynamic SR and transmitting the UL grant is greater than or equal to a greater of: a) a time needed to change from one beam to another beam, or b) a processing time.

57. The base station of claim 51, wherein a location of the bit is radio resource control, RRC, configured.

58. The base station of claim 51, wherein the PUCCH resource is radio resource control, RRC, configured.

59. A baseband processor configured to perform operations comprising: generating a downlink control information, DCI, message containing an indication of a physical uplink control channel, PUCCH, resource for a UE to use to transmit a dynamic scheduling request, SR; polling the UE by transmitting the DCI including the PUCCH resource, the PUCCH resource being dynamically updated based on one or more network conditions including network traffic, locations of one or more UEs, or which of the one or more UEs has data to transmit, wherein the UE is one of the one or more UEs, and the DCI includes a plurality of bit fields, each bit field being assigned to a corresponding one of the one or more UEs, and wherein a starting position and a number of bits of each bit field of the plurality of bit fields is radio resource control, RRC, configured; receiving the dynamic SR in a PUCCH message transmitted according to the PUCCH resource; and transmitting an uplink, UL, grant based on the dynamic SR determination.

60. The baseband processor of claim 59, wherein the DCI is transmitted on a channel during a designated channel occupancy time, COT.

61. The baseband processor of claim 60, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines a search space for the UE to locate the DCI within the COT.

62. The baseband processor of claim 61, wherein the search space is fixed relative to a start of the COT or is defined as part of downlink burst signaling.

63. The baseband processor of claim 60, wherein the COT is allocated to a network equipment statically or through a contention-based protocol.

64. The baseband processor of claim 60, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI to be located relative to a start of the COT.

65. The baseband processor of claim 59, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI to be located relative to a numerology.

66. The baseband processor of claim 59, the operations further comprising transmitting configuration information to a user equipment (UE) indicating how to find the DCI, wherein the configuration information defines the DCI to be part of downlink burst signaling.

67. The baseband processor of claim 59, wherein the DCI includes a PUCCH resource indicator (PRI) having a bit field indicating the PUCCH resource to be used for the dynamic SR.

68. The baseband processor of claim 67, wherein the bit field indicates whether the PRI is associated with a hybrid automatic repeat request (HARQ) or the dynamic SR.

69. The baseband processor of claim 67, wherein the UE finds the PUCCH resource based on a) a resource lookup different from a semi-static PUCCH lookup and b) a relative first symbol position relative to a position of the PRI in the DCI.

70. The baseband processor of claim 67, wherein the UE finds the PUCCH resource based on a) a subset of a semi-static PUCCH lookup and b) a relative first symbol position relative to a position of the PRI in the DCI.

71. The baseband processor of claim 59, wherein the dynamic SR is multiplexed with a hybrid automatic repeat request (HARQ) transmission.

72. The baseband processor of claim 59, wherein the dynamic SR includes channel state information (CSI).

73. The baseband processor of claim 59, wherein the PUCCH resource for the UE is indicated in the bit field allocated to the UE.

74. The baseband processor of claim 59, wherein assigning each bit field to the corresponding one of the one or more UEs comprises: a cyclic redundancy check (CRC) of the DCI is scrambled using a radio network temporary identifier (RNTI) allocated to each of the one or more UEs.

75. The baseband processor of claim 59, wherein a number of bits of each bit field of the plurality of bit fields is RRC configured.

76. The baseband processor of claim 59, wherein the DCI has a format of 2_6 or a group common DCI.

77. The baseband processor of claim 59, wherein the UE transmits the dynamic SR if the PUCCH resource is successfully found, but does not transmit the dynamic SR if the PUCCH resource is not successfully found.

78. The baseband processor of claim 59, wherein UL resources including beam and time scheduling included in the UL grant are determined based on information included in the dynamic SR, the information including one or more of: a beam, a listen-before-talk (LBT) band, a time slot to transmit, and a bandwidth part (BWP).

79. The baseband processor of claim 59, wherein a time interval implemented between receiving the dynamic SR and transmitting the UL grant is greater than or equal to a greater of: a) a time needed to change from one beam to another beam, or b) a processing time.

80. A baseband processor configured to perform operations comprising: generating a downlink control information (DCI) or a downlink communication including a bit indicating whether a user equipment (UE) sends a dynamic scheduling request (SR); polling the UE by transmitting the DCI or the downlink communication including the bit, the bit being dynamically updated based on one or more network conditions, the one or more network conditions including network traffic, locations of one or more UEs, or which of the one or more UEs has data to transmit, wherein the UE is one of the one or more UEs, and the DCI includes a plurality of bit fields, each bit field being assigned to a corresponding one of the one or more UEs, and wherein a starting position and a number of bits of each bit field of the plurality of bit fields is radio resource control (RRC) configured; receiving the dynamic SR in a physical uplink control channel (PUCCH) message; and transmitting an uplink (UL) grant determined based on the dynamic SR.

81. The baseband processor of claim 80, wherein the DCI or the downlink communication is transmitted on a channel during a designated channel occupancy time (COT).

82. The baseband processor of claim 81, wherein the COT is allocated to network equipment statically or through a contention-based protocol.

83. The baseband processor of claim 80, wherein the bit is one of a plurality of bits included in the DCI or downlink communication, each bit of the plurality of bits being associated with a corresponding UE of a plurality of UEs, and each bit of the plurality of bits indicating to the corresponding UE whether to transmit a corresponding dynamic SR, wherein each UE of the plurality of UEs is configured with a corresponding predetermined PUCCH resource.

84. The baseband processor of claim 80, wherein UL resources including beam and time scheduling included in the UL grant are determined based on information included in the dynamic SR, the information including one or more of: a beam, a listen-before-talk (LBT) band, and a bandwidth part (BWP).

85. The baseband processor of claim 80, wherein a time interval implemented between receiving the dynamic SR and transmitting the UL grant is greater than or equal to a greater of: a) a time needed to change from one beam to another beam, or b) a processing time.

86. The baseband processor of claim 80, wherein a location of the bits is radio resource control (RRC) configured.

87. The baseband processor of claim 80, wherein the PUCCH resource is radio resource control (RRC) configured.

Images