System and methods for dynamic scheduling in new radio with user equipment

Dynamic scheduling can be performed by 5G new radio in the licensed or unlicensed band. A UE can be polled by receiving a DCI that indicates dynamically updated resources. UE can be configured to find the DCI and use the resources to send a scheduling request (SR). Other aspects are described.

RELATED APPLICATIONS

The present application is the national phase of International Application No. PCT/CN2020/107213, filed on Aug. 5, 2020 and the disclosure of which is hereby incorporated herein by reference in its entirety.

FIELD OF INVENTION

This invention relates generally to wireless technology and more particularly to dynamic scheduling in new radio (NR) and new radio in the unlicensed spectrum (NR-U).

BACKGROUND OF THE INVENTION

Fifth generation mobile network (5G) is a wireless standard that aims to improve upon data transmission speed, reliability, availability, and more. This standard, while still developing, includes numerous details relating to various aspects of wireless communication, for example, NR and NR in the unlicensed spectrum (greater than 52.6 GHz), also known as NR-U.

SUMMARY OF THE DESCRIPTION

Aspects of the present disclosure relate to 5G new radio (NR) operating in the licensed band or in the unlicensed band (NR-U). 5G NR-U operates above the 52.6 GHz band.

In some aspects, a method or a device (e.g., user equipment or a baseband processor) configured to perform the method is described. The method can include receiving configuration information from a base station, wherein the configuration information comprises information for finding downlink control information (DCI); being polled by receiving the DCI that includes 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 the dynamic SR in a PUCCH message based on the PUCCH resource, wherein uplink grant is performed based on the dynamic SR.

In some aspects, a method can include being polled by receiving a downlink control information (DCI) that includes a bit that instructs the UE whether or not to send a dynamic scheduling request (SR); and transmitting the dynamic SR in a PUCCH message based on a predetermined physical uplink control channel (PUCCH) resource configured in the UE, wherein uplink grant is performed based on the dynamic SR.

In some aspects, a method or network equipment (e.g., a base station or baseband processor) that is configured to perform the method is described. The method can include 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 that includes the PUCCH resource which is dynamically updated based on one or more network conditions including network traffic, location of one or more UE, or which of the one or more UE have data to transmit; receiving the dynamic SR in a PUCCH message that is transmitted according to the PUCCH resource; and transmitting an uplink (UL) grant having beam and time scheduling determined based on the dynamic SR.

In some aspects, a method includes generating a downlink control information (DCI) that includes a bit that instructs a user equipment (UE) whether or not to send a dynamic scheduling request (SR); polling the UE by transmitting the DCI that includes the bit which is dynamically updated based on one or more network conditions including network traffic, location of one or more UE, or which of the one or more UE have data to transmit; receiving the dynamic SR in a physical uplink control channel (PUCCH) message; and transmitting an uplink (UL) grant having beam and time scheduling determined based on the dynamic SR.

Other methods and apparatuses are also described.

DETAILED DESCRIPTION

A method and apparatus of a device that determines a physical downlink shared channel scheduling resource for a user equipment device and a base station is described. In the following description, numerous specific details are set forth to provide thorough explanation of aspects of the present invention. It will be apparent, however, to one skilled in the art, that aspects of the present invention may 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.

Reference in the specification to “some aspects” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect can be included in at least one aspect of the invention. The appearances of the phrase “in some aspects” in various places in the specification do not necessarily all refer to the same aspect.

The terms “server,” “client,” and “device” are intended to refer generally to data processing systems rather than specifically to a particular form factor for the server, client, and/or device.

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

The frequency bands for 5G networks come in two sets—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 known as the millimeter wave (mmWave) spectrum. In some aspects, the UE and base station can communicate over NR in the unlicensed band which is above FR2, also known as NR-U.

NR-U is a mode of operation that defines technology for cellular operators to integrate the unlicensed spectrum (e.g., frequencies greater than 52.6 GHz, such as, for example, between 52.6 GHz and 71 GHz) into 5G networks. Radio waves in this band have wavelengths in the so-called millimeter band, and radiation in this band is known as millimeter waves. NR-U enables both uplink and downlink operation in unlicensed bands. NR-U supports new features, for example, wideband carriers, flexible numerologies, dynamic TDD, beamforming, and dynamic scheduling/HARQ timing.

In NR-U, license-assisted use as well as standalone use are supported in the unlicensed spectrum. Operators can use a non-standalone mode to aggregate the unlicensed bands with licensed 5G frequencies to bolster capacity (e.g., similar to LAA), as well as a standalone mode wherein an enterprise could use unlicensed spectrum to deploy a private cellular network. 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 context dictates otherwise. Although NR-U has developed, problems exist regarding dynamic scheduling, as are discussed in other sections.

FIG.1illustrates a simplified example wireless communication system, according to some aspects. It is noted that the system ofFIG.1is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

The base station (BS)102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs106A through106N.

As shown, the base station102A may also be equipped to communicate with a network100(e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station102A may facilitate communication between the user devices and/or between the user devices and the network100. In particular, the cellular base station102A may provide UEs106with various telecommunication capabilities, such as voice, SMS and/or data services.

In some aspects, base station102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some aspects, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

FIG.2illustrates UE106A that can be in communication with a base station102through uplink and downlink communications, according to some aspects. The UEs may each be a device with cellular communication capability such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

The UE may include a processor that is configured to execute program instructions stored in memory. The UE may perform any of the method aspects described herein by executing such stored instructions. Alternatively, or in addition, the UE may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method aspects described herein, or any portion of any of the method aspects described herein.

In some aspects, the UE may 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 a further possibility, the UE may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE might include a shared radio for communicating using either of LTE or 5G NR (or LTE or 1×RTT or LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

FIG.3illustrates an example simplified block diagram of a communication device106, according to some aspects. It is noted that the block diagram of the communication device ofFIG.3is only one example of a possible communication device. According to aspects, communication device106may 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., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices. As shown, the communication device106may include a set of components300configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components300may be implemented as separate components or groups of components for the various purposes. The set of components300may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device106.

For example, the communication device106may include various types of memory (e.g., including NAND flash310), an input/output interface such as connector I/F320(e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display360, which may be integrated with or external to the communication device106, and cellular communication circuitry330such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry329(e.g., Bluetooth™ and WLAN circuitry). In some aspects, communication device106may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335and336as shown. The short to medium range wireless communication circuitry329may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas337and338as shown. Alternatively, the short to medium range wireless communication circuitry329may couple (e.g., communicatively; directly or indirectly) to the antennas335and336in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas337and338. The short to medium range wireless communication circuitry329and/or cellular communication circuitry330may 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.

The communication device106may further include one or more smart cards345that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards345.

As shown, the SOC300may include processor(s)302, which may execute program instructions for the communication device106and display circuitry304, which may perform graphics processing and provide display signals to the display360. The processor(s)302may also be coupled to memory management unit (MMU)340, which may be configured to receive addresses from the processor(s)302and translate those addresses to locations in memory (e.g., memory306, read only memory (ROM)350, NAND flash memory310) and/or to other circuits or devices, such as the display circuitry304, short range wireless communication circuitry229, cellular communication circuitry330, connector I/F320, and/or display360. The MMU340may be configured to perform memory protection and page table translation or set up. In some aspects, the MMU340may be included as a portion of the processor(s)302.

As noted above, the communication device106may be configured to communicate using wireless and/or wired communication circuitry. The communication device106may also be configured to determine a physical downlink shared channel scheduling resource for a user equipment device and a base station. Further, the communication device106may be configured to group and select CCs from the wireless link and determine a virtual CC from the group of selected CCs. The wireless device may also be configured to perform a physical downlink resource mapping based on an aggregate resource matching patterns of groups of CCs.

As described herein, the communication device106may include hardware and software components for implementing the above features for determining a physical downlink shared channel scheduling resource for a communications device106and a base station. The processor302of the communication device106may be configured to implement part or all of the features 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), processor302may 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 processor302of the communication device106, in conjunction with one or more of the other components300,304,306,310,320,329,330,340,345,350,360may be configured to implement part or all of the features described herein.

Further, as described herein, cellular communication circuitry330and short range wireless communication circuitry329may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry330and, similarly, one or more processing elements may be included in short range wireless communication circuitry329. Thus, cellular communication circuitry330may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry330. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry230. Similarly, the short range wireless communication circuitry329may include one or more ICs that are configured to perform the functions of short range wireless communication circuitry32. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short range wireless communication circuitry329.

In some aspects, base station102may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such aspects, base station102may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, base station102may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. In some aspects, the base station can operate in 5G NR-U mode.

In addition, as described herein, processor(s)404may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s)404. Thus, processor(s)404may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)404. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)404.

Further, as described herein, radio430may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio430. Thus, radio430may include one or more integrated circuits (ICs) that are configured to perform the functions of radio430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio430.

The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335a-band336as shown (inFIG.3). In some aspects, cellular communication circuitry330may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown inFIG.5, cellular communication circuitry330may include a modem510and a modem520. Modem510may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem520may be configured for communications according to a second RAT, e.g., such as 5G NR.

In some aspects, a switch570may couple transmit circuitry534to uplink (UL) front end572. In addition, switch570may couple transmit circuitry544to UL front end572. UL front end572may include circuitry for transmitting radio signals via antenna336. Thus, when cellular communication circuitry330receives instructions to transmit according to the first RAT (e.g., as supported via modem510), switch570may be switched to a first state that allows modem510to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry534and UL front end572). Similarly, when cellular communication circuitry330receives instructions to transmit according to the second RAT (e.g., as supported via modem520), switch570may be switched to a second state that allows modem520to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry544and UL front end572).

As described herein, the modem510may include hardware and software components for implementing the above features or for determining a physical downlink shared channel scheduling resource for a user equipment device and a base station, as well as the various other techniques described herein. The processors512may be configured to implement part or all of the features 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), processor512may 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 processor512, in conjunction with one or more of the other components530,532,534,550,570,572,335and336may be configured to implement part or all of the features described herein.

In addition, as described herein, processors512may include one or more processing elements. Thus, processors512may include one or more integrated circuits (ICs) that are configured to perform the functions of processors512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors512.

As described herein, the modem520may include hardware and software components for implementing the above features for determining a physical downlink shared channel scheduling resource for a user equipment device and a base station, as well as the various other techniques described herein. The processors522may be configured to implement part or all of the features 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), processor522may 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 processor522, in conjunction with one or more of the other components540,542,544,550,570,572,335and336may be configured to implement part or all of the features described herein.

In addition, as described herein, processors522may include one or more processing elements. Thus, processors522may include one or more integrated circuits (ICs) that are configured to perform the functions of processors522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors522.

NR-U listen before talk (LBT) channel access mechanism can be based on ED-based LBT of license assisted access (LAA). Two types of LBTs channel access mechanisms include a frame based equipment (FBE) access load based equipment (LBE) access. For FBE, a transmit/receive structure has a periodic timing with a periodicity equal to the fixed frame period. For LBE, a transmit/receive structure is not fixed in time but demand-driven. There are four categories of LBT that are defined in LAA LBE operations 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 fixed size contention window. Category 4 is LBT with random backoff with variable size contention window.

After a successful LBT, an initiating device can access a channel at most for a duration of a maximum channel occupancy time (MCOT). Sharing of channel occupancy time (COT) can be performed between an initiating and responding node in any direction, such as, for example, gNB-acquired COT sharing and UE-acquired COT sharing. Two MCOT structures include LAA and NR-U. LAA has a single DL to UL switch. This provides for less overhead due to one single GP, and avoids multiple LBT. One setback here is that larger latency may be present for HARQ-ACK feedback.

NR-U also supports multiple DL to UL switch and UL to DL switch. This can result in reduced latency for delay-sensitive traffic, e.g. URLLC. In NR-U, if the gap between DL and UL or UL and DL is within 16 us (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 larger than 16 us but less than 25 us, Cat-2 is allowed.

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

At least for the case where a DL burst follows a UL burst within a gNB-initiated COT and there is no gap larger than 25 μs between any two transmissions in the COT, the channel access schemes in the table below apply.

TABLE 2Channel access schemes for a DL burst follows aUL burst within a gNB-initiated COT as LBE deviceCat 1 Immediate transmissionCat 2 LBTWhen the gap from the end of theWhen the gap from the end of thescheduled UL transmission to thescheduled UL transmission to thebeginning of the DL burst is up tobeginning of the DL burst is larger16 μsecthan 16 μsec but not more than25 μsec

A DL/UL burst is defined as a set of transmissions from a given gNB/UE having no gaps or gaps of no more than 16 us. Transmissions from gNB/UE having a gap of more than 16 us are considered as separate DL/UL bursts.

Within a gNB-initiated COT, an UL burst for 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) follows the channel access schemes in the table below.

TABLE 3Channel access schemes for a UL burst within a gNB-initiatedCat 1 Immediate transmissionCat 2 LBTCat 4 LBTWhen the gap from the end ofFor any of the followingN/Athe DL transmission to thecases:beginning of the UL burst isa) When the gap between anynot more than 16 msec.two successivescheduled/grantedtransmissions in the COT isnot greater than 25 msecb) For the case where a ULtransmission in the gNBinitiated COT is not followedby a DL transmission in thesame COTNote: the duration from thestart of the first transmissionwithin the channel occupancyuntil the end of the lasttransmission in the samechannel occupancy shall notexceed 20 ms.

For initiation of a COT by the UE, the channel access schemes in the below table can be used—using Cat-4 LBT for UCI-only PUSCH.

TABLE 4Channel access schemes for initiating a COT by UECat 2 LBTCat 4 LBTPUSCH (includingN/A exceptChannel access priorityat least UL-SCHfor the casesclass is selectedwith user planediscussed inaccording to the datadata)Note 2 belowSRS-onlyN/ACat4 with lowest channelaccess priority class value(as in LTE eLAA)RACH-onlyN/ACat4 with lowest channelaccess priority class valuePUCCH-only(see Note 2)Cat4 with lowest channelaccess priority class value

Three different channel access mechanisms for Hybrid MAC for 60 GHz includes CSMA/CA, TDMA, and polling. CSMA/CA is suitable for bursty traffic. Ideally CSMA/CA needs omni-directional transmit and receive beams. In directional CSMA/CA, gNB is omni, and UE is directional. In paired CSMA/CA, UE switches beams for listen vs talk. For example, listen is omni, or in opposite direction). For 802.11ad. during the Contention Based Access Period, enhanced 802.11 EDCA includes traffic categories to support quality of service, frame aggregation and block acknowledgments.

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

Polling can be performed in contention based period and service period. During polling, an AP pings each UE for data (directional SR), UE replies (directional PUCCH), gNB schedules UE and UE transmits. Regarding 802.11ad and polling, Dynamic Channel Time Allocation is used. PCP/AP acquires medium, PCP/AP sends polling frames, STas send Service Period Requests (SPRs), PCP/AP allocates time with grant frames.

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

Regarding channel access frame structure, a beacon interval can include a beacon header interval (BHI) and data transmission interval (DTI). The BHI facilitates the exchange of management information and network announcements using a sweep of multiple directionally transmitted frame. In a BTI, a sector level sweep can be performed with multiple beacon frames (MCSO). In an Association Beamforming Training (A-BFT) timeslot, a responder sector level sweep (MCSO) can be performed. In an Announcement Transmission Interval (ATI), a PCP/AP exchanges management information with an associated and beamtrained station (MCSx).

A DTI implements different types of medium access. Schedule can be announced by PCP/AP. During the DTI, multiple contention based access periods (CBAP) can be performed using a variation of enhanced distributed coordination function (EDCF). In some cases, rather than CBAP, multiple service periods (SP): communication between a dedicated pair of nodes in a contention free period. Dynamic channel allocation can be supported through polling of STAs within CBAP or SP by PCP/AP and dynamic allocation of resources. In dynamic channel allocation, a schedule can be communicated by extended schedule element. In this case, pseudo-static access is used, the dynamic schedule recurs at the same relative offset to target beacon transmission time (TBTT) and within the same duration.

Scheduled/pseudo-static Contention Based Access can also be performed, such as CSMA/CA, for dynamic channel access. The schedule can be sent in a CBAP. The schedule can include traffic categories to support quality of service, frame aggregation and block ACKs. This access method supports multiple NAV timers (one per peer STA), e.g., a transmission can be initiated with device if NAV for device is 0.

Scheduled/pseudo-static TMDA channel time allocation (TDMA) can be performed. A schedule can be broadcast by PCP/AP in schedule element next to BTI or ATI. The schedule is sent in the Service Period (SP). This access method allows D2D transmission and supports multiple NAV timers (one per peer STA) for protected mode transmission.

Dynamic channel time allocation (polling) can be performed. In such a case, STA can poll to receive SPR (Service Period Request). Time is allocated based on request using grant frames. This access method can be used in both CBAP (PCP/AP uses PIFS) and SP.

For periods of time that are scheduled by the AP/PCP, where any STA can access the channel, access during the CBAP is based on EDCA. All CBAPs are allocated by AP or PCP, except when allocated by a non-AP and non-PCP STA with the transmission of a grant frame following an SP truncation. There may be multiple CBAPs present in a beacon interval. PCP/AP may initiate a frame transmission within the CBAP immediately after the medium is determined to be idle for one PIFS (8 usecs). Operation of EDCAF is suspend at the end of a CBAP and resumed at beginning of following CBAP. The frame sent by the STA at the beginning of the TXOP may be an RTS frame or a DMG CTS-to-self frame.

Within a CBAP a STA with multiple DMG antennas should use only one DMG antenna in its frame transmission, CCA and frame reception, except if it is the initiator or responder in an SLS (10.42 (DMG beamforming)). In such a case, the algorithm to select a DMG antenna and switch the active DMG antenna is implementation dependent. Within CBAPs a STA that changed to a different DMG antenna in order to transmit should perform CCA on that DMG antenna until a frame is detected by which it can set its NAV, or until a period of time equal to the dot11DMGNavSync has transpired, whichever is earlier.

A service period can be negotiated between AP/PCP and STA or dynamically allocated, where only prescribed 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 truncatable)

Regarding 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 has no knowledge of the non-pseudo-static SPs allocated during the beacon interval that indicate it is the source DMG STA; therefore, it fails to transmit during those SPs. If the destination of the non-pseudo-static SP is an AP or PCP and it does not receive any frames from the source on-AP and non-PCP STA for a timeout interval, the AP/PCP may truncate the SP and reallocate the remaining duration of the SP to the source DMG STA of the SP or other STAs provided it is a truncatable SP. If not truncatable, it may stay awake or go into doze state. If non-AP/non-PCP STA does not receive an extended schedule element from the AP or PCP for that beacon interval, it may switch to doze state or may direct its receive antenna toward the AP or PCP to receive a grant during non-pseudo-static SPs or CBAPs in the current beacon interval.

A protected period can be enforced to minimize interference between pairs of communicating STAs. This protected period can be enforced by limiting the transmission of frames during the DMG protected period to not more than one pair of potentially interfering pairs of communicating stations. Dynamic BW operation to can be used to negotiate BW to be used by this SP. STA can be set to listening mode for an interval before SP and only transmit if clear (CAT2 type access). In this case, antennas are in Quasi-omni mode or directed towards peer DMG STA. The protected period can be established through a RTS/DMG CTS handshake. Interference can be reported to PCP/AP.

Dynamic allocation of a service period can be employed to allocate channel time during scheduled SPs and CBAPs. The dynamic allocation can include an optional polling period (PP) phase and a grant period (GP) phase.

Regarding channel access intervals, before BI, CAT 4 applies. Within BTI and A-BFT, fixed intervals apply. In such a case, the MBIFS shall be used between the BTI and the A-BFT and between the ISS, RSS, SSW-Feedback, and SSW-Ack. MBIFS is equal to 3×aSIFSTime. A-BFT can be slotted with MBIFS between packets in a slot. Between A-BFT and ATI the larger of (guard time, MBIFS) applies. Within ATI, once the ATI starts, the AP or PCP may start transmission of a request frame immediately or it may delay the transmission of the request frame if the medium is determined by the CCA mechanism to be busy. Response is SIFS from request frame. Source initiates at start of SP except if protected period needs to be established i.e. listens to medium based on RTS/DMG CTS transmission. A reply (SIFS) and/or retransmit (PIFS) can be performed in SP. In CBAP, CAT4 applies. For PCP/AP or other sources, PIFS applies. For polling SBIFS and/or SIFS is used.

For communications (e.g., 5G-NRU) that operate at >52.6 GHz, it may be desirable for a gNB to perform a dynamic polling of all the UEs to identify which UEs have data and modify its resource allocation accordingly. This allows flexible reassignment of time and beam resources in mmWave transmission.

Satisfactory communications could require beams in direction of UE. Due to beam based allocation, a UE may only be able to send an SR dynamically only when its beam pair is active. If dynamic change in beam pair, UE may not know if beam is active to send SR and request for resources. Statically allocate resources, in this case, may be deficient. Thus, communications can benefit from a dynamic SR in an NR or NR-U environment.

A SR that uses a PRI in the DCI to indicate a set of semi-statically configured PUCCH resources identified by a first symbol, a number of symbols and other parameters may lack flexibility. Additional flexibility may be needed to indicate the PUCCH resource(s) relative to the DCI and appropriate signaling within the DCI. Thus, a dynamic SR configuration may provide improved flexibility.

Overhead of signaling the presence of an SRI in a DCI can be high if PUCCH resources are dynamically changed and DCI is used to signal the PUCCH resource. To reduce overhead, in some aspects, PUCCH resource signaling for Dynamic SR can be part of an existing DCI transmission. In some aspects, dedicated PUCCH resource signaling for Dynamic SR. In some aspects, a semi-static configuration can reduce overhead.

Based on LBT failure, a methodology could be required to enable reliable PUCCH and PUSCH transmission. For example, multiple PUCCH resources can be signaled. To communicate over PUSCH, additional information may also be needed in the SR feedback to enable the gNB identify the best resource to send information in e.g. beam, CC, or BWP. Multiple resources can be signaled for PUSCH transmission.

In some aspects, with signaling of dynamic resources, there may be timeline issues. Time gaps may be enforced between signaling. The gap can be determined based on the number of beams and/or processing time.

Referring toFIG.6, dynamic scheduling is shown according to some aspects. The dynamic scheduling can be performed over 5G NR or 5G NR-U.

At operation602, the base station can transmit configuration information to a user equipment (UE) that indicates how to find a DCI. The configuration information describes where the DCI is located (e.g., a location within a COT allocated to the base station).

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

In some aspects, the search space is defined as fixed relative to a start of the COT. For example, the search space can be defined as being ‘x’ number of resource blocks that begins ‘y’ symbols after the beginning of a 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 group common physical downlink control channel (GC-PDCCH) COT in time/frequency domain structure.

In some aspects, rather than define a search space, the configuration information can specify a precise location of the DCI. The receiving UE is configured with the exact location of the DCI in a received transmission to decode the DCI accordingly. In some aspects, configuration information can define the DCI as positioned relative to numerology. For example, the DCI can be defined as having a location relative to specific resource blocks and symbols. A symbol can be an OFDM symbol describing a time slot in a frequency band for a particular channel. Numerology refers to the configuration of waveform parameters. Different numerologies can be considered as OFDM-based sub-frames having different parameters such as subcarrier spacing/symbol time, CP size, etc.

In some aspects, the configuration information defines the DCI message as positioned relative to a start of the COT. For example, the DCI message can be defined in the configuration information as being ‘x’ number of resource blocks ‘y’ symbols fixed relative to the beginning of the COT. In some aspects, configuration information defines the DCI as being part of downlink burst signaling. For example, the DCI location can be defined in the configuration information as being located in a group common physical downlink control channel (GC-PDCCH) COT in time/frequency domain structure.

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

At operation603, a base station can request network resources, such as a channel occupancy time (COT) or maximum channel occupancy time (MCOT) of a channel, from a network. The network can determine the COT or MCOT to be allocated for the base station, and at operation604send a response to the base station that includes COT or MCOT. In some aspects, the resource request603is 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 assigned channel and time. The network can include a mix of network devices that share bandwidth over common frequencies.

At operation604, the network can send a response to the base station that allocates channel resources. For example, the response can define a COT or MCOT with which the base station is free to use a channel. It should be understood that operation602can occur before and/or after operations603and604.

At operation616, the base station can generate a DCI. The DCI can indicate to each of the one or more UEs what PUCCH resources should be used by a UE to send a dynamic SR. The PUCCH resource can include a symbol (e.g., 10, 16, 18), that defines to the UE and base station which beam pair and/or time the dynamic SR will be communicated over. The PUCCH resources can be dynamically updated based on one or more network conditions including network traffic, location of one or more UE, or which of the one or more UE have data to transmit. Details of the PUCCH resource are discussed in other sections. The DCI can have a format 2_0, 2_1, 2_2, or other downlink DCI format currently existing or developed in the future.

At operation606, the base station can poll the UE by transmitting a DCI can be to one or more UEs (such as the one shown inFIG.6). The PUCCH resources that are associated with each of the one or more UEs, which are indicated in the DCI, can change over time based on network conditions. The DCI transmissions can be performed periodically, or whenever a change to the network conditions occurs which can prompt a change to the allocation of PUCCH resources to the one or more UEs.

At operation618, the UE can receive/decode the DCI, and find the DCI based on the configuration information received at operation602, as described in other sections. The UE can decode the DCI to determine the PUCCH resource to be used to send the dynamic SR.

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

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

In some aspects, 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 location that is relative to a position of the PRI in the DCI. For example, if the PRI is received in symbol n and indicates a relative first symbol location x, the PUCCH resource can be in or start from the symbol (n+x).

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

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

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

For example, referring toFIG.7, the UE (e.g., UE(N)) is one of a plurality of UEs, and the DCI includes a plurality of bit fields, each bit field being assigned to a corresponding one of the one or more UE. The PUCCH resource (e.g., one or more symbols) for the UE to use for transmitting the dynamic SR is indicated in the bit field assigned to the UE.

In some aspects, each bit field can be assigned to the corresponding one of the one or more UE based on a radio network temporary identifier (RNTI). For example, a check record sum of the entire DCI or each bit field is scrambled with RNTI, and each RNTI is assigned to each of the one or more UE.

Each RNTI can be used by the UE to find the bit field that is assigned to a UE. A starting position and number of bits (e.g., if the size is variable) of each of the plurality of bit fields can be semi-statically configured. In some aspects, the starting position alone is enough (e.g., if the size bit field is not variable). The PUCCH resource for the UE is indicated in one of the plurality of bit fields (e.g., as a value), and PUCCH resources for others of the plurality of UEs are located in others of the plurality of bit fields. In some aspects, a bit field dedicated to a single UE can signal more than one PUCCH resource in case there may be an LBT failure of the single resource. In some aspects, the DCI has a format of 2_6 or a group common DCI.

Upon successful decoding of the PUCCH resource (e.g., the PUCCH resource is found by the UE), the UE may send a dynamic SR in the specified PUCCH resource. If decoding of the PUCCH resource is unsuccessful (e.g., the UE cannot find the PUCCH resource), then the UE can decline to send the dynamic SR.

Referring back toFIG.6, at operation608, the UE can transmit the dynamic SR in a PUCCH message based on the PUCCH resource that was 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 the dynamic SR will be communicated over. The SR is communicated over a PUCCH message as defined by the symbol (e.g., at a particular time using a particular beam pair). Symbol format and PUCCH format can vary based on application.

In some aspects, the dynamic SR that is transmitted from the UE to the base station can include PUCCH signaling for increased reliability. This can be used to assist the base station in determining resources for data transfer.

For example, as shown inFIG.8, the UE may include, in the dynamic SR, additional information (e.g., UE assistance for LBT) to enable the gNB to identify an improved resource 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 bandwidth parts (BWPs). In some aspects, the UE sends the dynamic SR only if the UE wishes to reserve a slot and/or has data to send to the base station and/or has successfully found and decoded the PUCCH resource.

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

At oration610, the base station can send an UL grant to the user equipment, which can be a scheduling DCI (e.g., format 0_X). At operation612, the UE can transmit UL data to the base station, over UL resources that are specified in the UL grant.

In some aspects, the DCI resource and the corresponding dynamic SR resource (e.g., the PUCCH resource) may be semi-statically configured together. In this case, a single bit (or a field of bits where each bit corresponds to a particular UE) may be configured to indicate if the UE should send a dynamic SR in a predetermined resource. The bit or field of bits 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, location of one or more UE, or which of the one or more UE have data to transmit or changes thereof.

For example, referring toFIG.9a bit field900is shown, which can be included in the DCI (or other suitable downlink communication), can indicate to one or more UEs whether or not each of the one or more UEs should transmit a dynamic SR. In this case, rather than including the PUCCH resource in the DCI, the PUCCH resource is semi-statically configured. In some aspects, the bit field need not be carried in DCI, but can be carried in another suitable downlink communication from the base station the UE. In other words, where the dynamic SR resources are semi-statically configured, operation602ofFIG.6can be bypassed, and operation606need not include a polled DCI, but can be any suitable downlink communication carrying the described bit-field. The UE need not find the PUCCH resource because 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 symbol10. So long as the bit corresponding to the UE is set in a received poll, the UE will send a dynamic SR using symbol10.

It should be understood that semi-static configuration can be performed through radio resource control (RRC) communications between a base station and a UE (e.g., from a base station to the UE, and vice versa). RRC protocol can include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release and outer loop power control. By means of the signaling functions, the RRC configure a UE (e.g., semi-statically).

FIG.10shows an example of SR scheduling with multiple UEs. During polling period1001, a base station can poll N number of UEs. Some or all of the UEs can respond with a corresponding SR. During a grant period1002, the base station can transmit UL grants (e.g., in the form of a scheduling DCI) to the UEs. UL transmission can be performed during data transfer period1003.

FIG.11shows a flow diagram of dynamic scheduling, according to some aspects. DCI configuration can be sent from the base station to the UE at block1101. This tells the UE how to find the DCI or where to expect to find the DCI. The DCI is sent to the UE at block1102. At block1103, the dynamic SR is sent from the UE to the base station. At block1104, a UL grant is sent from the base station to the UE and data is sent from the UE to the base station.

Referring toFIG.12shows a flow diagram of dynamic scheduling similar toFIG.11, however, in this case, due to beam switching and processing times, a minimum time interval can be enforced between the elements of the dynamic scheduling (e.g., the DCI, dynamic SR, scheduling DCI and/or transmission). Thus, a time interval can be enforced between some of the communications between the UE and the base station (e.g., between receiving the DCI and transmitting the dynamic SR, or between receiving the dynamic SR and transmitting the UL grant). The time interval can be greater than or equal to a larger of a) a time required to change from one beam to another (e.g., of the UE and/or the base station), or b) a processing time (e.g., of the UE).

The processing time either be fixed to a value based on 120 kHz, or modified to account for new sub carrier spacing (SCS) values (e.g., 240 kHz, 480 kHz, 960 kHz, etc.). The beam switching time may be based on existing beam switching time limits (e.g., of a UE). The gNB may schedule each element of the procedure in groups. This scheduling may be transparent to the UE. In some aspects, for 120 kHz, tproc2=20 symbols. As such, the interval between DCI and dynamic SR should be at least 20 symbols.

A 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.

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

It should be kept 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 action 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.

The foregoing discussion merely describes some exemplary aspects of the present invention. One skilled in the art will readily recognize from such discussion, the accompanying drawings and the claims that various modifications can be made without departing from the spirit and scope of the invention.