Minimum Scheduling Delay Signaling

Abstract

Certain aspects of the present disclosure generally relate to methods and apparatus for minimum scheduling delay signaling.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 16 / 584,833, filed on September 26, 2019, which claims priority to U.S. Provisional Patent Application No. 62 / 739,084, filed on September 28, 2018, U.S. Provisional Patent Application No. 62 / 791,445, filed on January 11, 2019, U.S. Provisional Patent Application No. 62 / 828,220, filed on April 2, 2019, and U.S. Provisional Patent Application No. 62 / 847,045, filed on May 13, 2019, all of which are assigned to the present assignee, are considered a part of this patent application, and are incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems and, more particularly, to signaling scheduling delays. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcast, etc. These systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth and transmit power). Examples of such multiple access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] In some examples, a wireless multiple access communication system may include multiple base stations (BSs), each of which may simultaneously support communications for multiple communication devices (also referred to as user equipment (UE)). In an LTE or LTE-A network, a set of one or more gNBs may define an eNodeB (eNB). In other examples (e.g., in a next generation new radio (NR) or 5G network), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more distributed units communicating with the central unit may define an access node (e.g., NR BSs, NR NBs, network nodes, 5G NBs, next generation NBs (gNBs), etc.). A gNB or DU may communicate with a set of UEs on a downlink channel (e.g., for transmissions from a base station or to a UE) and an uplink channel (e.g., for transmissions from a UE to a gNB or DU).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the municipal, national, regional, and even global levels. NR (e.g., 5G radio access) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP. It aims to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to increase, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies. Summary of the invention

[0008] The systems, methods, and devices of the present disclosure each have several aspects, no single aspect being solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description of the Invention," it will be understood how the features of the present disclosure provide advantages for improved communication between access points and stations included in a wireless network.

[0009] Certain aspects of the present disclosure generally relate to methods and apparatus for signaling scheduling information.

[0010] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes receiving a physical downlink control channel (PDCCH) having downlink control information (DCI), the downlink control information (DCI) signaling a scheduling parameter, the scheduling parameter indicating a scheduling delay between an end of a PDCCH transmission and a start of a transmission scheduled by the PDCCH, determining that a value of the scheduling parameter is below a minimum threshold, and taking at least one action in response to the determination.

[0011] Certain aspects of the present disclosure provide a method for wireless communication by a network entity. The method generally includes determining a minimum threshold for a scheduling parameter indicating a scheduling delay between an end of a physical downlink control channel (PDCCH) transmission and a start of a transmission scheduled by the PDCCH, and configuring a user equipment (UE) with the minimum threshold.

[0012] Aspects generally include methods, apparatus, systems, computer-readable media, and processing systems substantially as described herein with reference to and as illustrated in the accompanying figures.

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

[0014] In order that the manner in which the above-mentioned features of the present disclosure are understood in detail, a more particular description of what has been briefly summarized above may be made by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the description may admit of other equally effective aspects.

[0015] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0016] Figure 2 is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) in accordance with certain aspects of the present disclosure.

[0017] Figure 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0018] Figure 4 is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

[0019] Figure 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

[0020] Figure 6 and Figure 7 An example of a frame format for a New Radio (NR) system is shown, in accordance with certain aspects of the present disclosure.

[0021] Figure 8 An example downlink communication with a bandwidth part (BWP) is shown.

[0022] Fig. 9 Example downlink communications with multiple BWPs with downlink control information (DCI) are shown.

[0023] Fig.10

[0013] Example operations for wireless communications by a base station are illustrated in accordance with certain aspects of the present disclosure.

[0024] Fig.11 Example operations for wireless communications by a user equipment (UE) are illustrated, in accordance with certain aspects of the present disclosure.

[0025] Fig. 12A and Fig. 12B Example bandwidth portion scheduling parameters according to aspects of the present disclosure are shown.

[0026] Fig.13 An example downlink communication with a bandwidth part (BWP) is shown.

[0027] Fig.14 An example scheduling offset with aperiodic channel state information (A-CSI) is shown.

[0028] Fig.15 An example scheduling offset with multiple bandwidth parts (BWPs) is shown.

[0029] Fig.16 An example scheduling offset with cross-carrier scheduling is shown.

[0030] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. DETAILED DESCRIPTION

[0031] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for NR (new radio access technology or 5G technology). NR can support various wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., above 80MHz), millimeter wave (mmW) for high carrier frequency (e.g., above 27GHz), massive machine type communication (mMTC) for non-backward compatible MTC technology, and / or mission critical ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet various quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0032] In some systems (e.g., 3GPP Release 13 Long Term Evolution (LTE) networks), enhanced machine type communications (eMTC) for low-cost devices is supported, typically at the expense of reduced throughput. eMTC may involve half-duplex (HD) operation, in which uplink transmissions and downlink transmissions may be performed, but not both at the same time. Some eMTC devices (e.g., eMTC UEs) may view (e.g., be configured with a monitor or be a monitor) no more than about 1 MHz or six resource blocks (RBs) of bandwidth at any given time. The eMTC UE may be configured to receive no more than about 1000 bits per subframe. For example, these eMTC UEs may support a maximum throughput of about 300 kilobits per second. This throughput may be sufficient for some eMTC use cases that may consist of infrequent transmissions of small amounts of data, such as some activity tracking, smart meter tracking, and / or updates, etc.; however, for other cases, such as some Internet of Things (IoT) use cases, wearable devices such as smart watches, etc., higher throughput may be desired for eMTC devices.

[0033] The following description provides examples and does not limit the scope, applicability or examples set forth in the claims. Without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may appropriately omit, replace or add various processes or components. For example, the described method may be performed in an order different from that described, and various steps may be added, omitted or combined. Moreover, the features described in some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice method. In addition, the scope of the present disclosure is intended to cover such an apparatus or method, which is practiced using other structures, functions, or structures and functions other than or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily to be interpreted as being preferred or advantageous over other aspects.

[0034] The technology described herein can be used in various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are generally used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applied to other communication systems based on generations, such as 5G and beyond, including NR technology.

[0035] Example Wireless Communication System

[0036] Figure 1 An example wireless network 100 is shown in which aspects of the present disclosure may be implemented. For example, the wireless network 100 may include a network configured to perform Fig.10 A network entity (e.g., gNB 110) of operation 1000 may provide a UE 120 (configured to perform Fig.11 Operation 1100) signals a minimum scheduling delay.

[0037] UE 120 may be configured for enhanced machine type communication (eMTC). UE 120 may be considered a low-cost device, a low-cost UE, an eMTC device, and / or an eMTC UE. UE 120 may be configured to support higher bandwidths and / or data rates (e.g., greater than 1 MHz). UE 120 may be configured with multiple narrowband regions (e.g., 24 resource blocks (RBs) or 96 RBs). UE 120 may receive a resource allocation from gNB 110 to allocate frequency hopping resources within the system bandwidth for UE 120 to use for monitoring and / or transmission. The resource allocation may indicate non-contiguous narrowband frequency resources for uplink transmission in at least one subframe. The resource allocation may indicate that the frequency resources are not included in the bandwidth capability of the UE for monitoring downlink transmissions. UE 120 may determine, based on the resource allocation, a narrowband different from the resources indicated in the resource allocation from gNB 110 for uplink transmission or for monitoring. A resource allocation indication (e.g., such as an indication included in downlink control information (DCI)) may include a set of allocated subframes, frequency hopping related parameters, and an explicit resource allocation on a first subframe of the allocated subframes. Frequency hopping resource allocations on subsequent subframes are obtained by applying a frequency hopping procedure based on frequency hopping related parameters (which may also be included in part in the DCI and configured in part through radio resource control (RRC) signaling) starting with the resources allocated on the first subframe of the allocated subframes.

[0038] like Figure 1 As shown, the wireless network 100 may include a number of gNBs 110 and other network entities. A gNB may be a station that communicates with a UE. Each gNB 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a Node B and / or NB subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and NB, next generation NB (gNB), 5G NB, access point (AP), BS, NR BS, or transmission reception point (TRP) may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile gNB. In some examples, the gNBs may be interconnected with each other and / or with one or more other gNBs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, or similar methods using any suitable transport networks, etc.).

[0039] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, tone, subband, subcarrier, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0040] The gNB may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). A gNB for a macro cell may be referred to as a macro gNB. A gNB for a pico cell may be referred to as a pico gNB. A gNB for a femto cell may be referred to as a femto gNB or a home gNB. In Figure 1 In the example shown, gNBs 110a, 110b, and 110c may be macro gNBs for macro cells 102a, 102b, and 102c, respectively. gNB 110x may be a pico gNB for pico cell 102x. gNBs 110y and 110z may be femto gNBs for femto cells 102y and 102z, respectively. A gNB may support one or more (e.g., three) cells.

[0041] The wireless network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a gNB or UE) and sends transmissions of data and / or other information to a downstream station (e.g., a UE or gNB). A relay station may also be a UE that relays transmissions for other UEs. Figure 1 In the example shown, a relay station 110r may communicate with a gNB 110a and a UE 120r to facilitate communication between the gNB 110a and the UE 120r. A relay station may also be referred to as a relay gNB, a relay, etc.

[0042] The wireless network 100 may be a heterogeneous network including different types of gNBs (e.g., macro gNBs, pico gNBs, femto gNBs, relays, etc.). These different types of gNBs may have different transmission power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro gNB may have a higher transmission power level (e.g., 20 Watts), while a pico gNB, a femto gNB, and a relay may have a lower transmission power level (e.g., 1 Watt).

[0043] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the gNBs may have similar frame timing, and transmissions from different gNBs may be approximately aligned in time. For asynchronous operation, the gNBs may have different frame timing, and transmissions from different gNBs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0044] The network controller 130 may be coupled to a group of gNBs and provide coordination and control for these gNBs. The network controller 130 may communicate with the gNBs 110 via a backhaul. The gNBs 110 may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0045] UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, medical device or medical equipment, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered as evolved or machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a gNB, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices or Narrowband IoT (NB-IoT) devices.

[0046] exist Figure 1 In the figure, a solid line with double arrows indicates a desired transmission between a UE and a serving gNB, which is a gNB designated to serve the UE on the downlink and / or uplink. A thin dashed line with double arrows indicates an interfering transmission between a UE and a gNB.

[0047] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are sent in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (e.g., RB) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size is equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.8 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0048] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR.

[0049] NR can utilize OFDM with CP on both the uplink and downlink, and includes support for half-duplex operation using TDD. A single component carrier bandwidth of 100 MHz can be supported. NR resource blocks can span 12 subcarriers with a subcarrier bandwidth of 75 kHz in a duration of 0.1 milliseconds (ms). Each radio frame can consist of two half-frames, each half-frame consists of 5 subframes and has a length of 10 ms. Therefore, each subframe can have a length of 1 ms. Each subframe can indicate the link direction (i.e., DL or UL) used for data transmission, and the link direction of each subframe can be switched dynamically. Each subframe can include DL / UL data and DL / UL control data. The UL and DL subframes of NR can refer to the following Figure 6 and Figure 7 Described in more detail. Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas with up to 8 streams and multi-layer DL transmission of up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported with up to 8 serving cells.

[0050] In LTE, the basic transmission time interval (TTI) or packet duration is 1 subframe. In NR, the subframe is still 1ms, and the basic TTI is called a slot. A subframe contains a variable number of slots (e.g. 1, 2, 4, 8, 16, ... slots), depending on the tone spacing (e.g. 15, 30, 60, 120, 240 ... kHz).

[0051] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a gNB) allocates resources for communication between some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. The gNB is not the only entity that can act as a scheduling entity. That is, in some examples, a UE may act as a scheduling entity to schedule resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE acts as a scheduling entity, and other UEs utilize the resources scheduled by the UE for wireless communication. The UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity, the UEs may optionally communicate directly with each other.

[0052] Thus, in a wireless communication network having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more slave entities may communicate using the scheduled resources.

[0053] Figure 2 It shows that it can be Figure 1 An example logical architecture of a distributed radio access network (RAN) 200 implemented in a wireless communication system is shown. A 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be a central unit (CU) of the distributed RAN 200. A backhaul interface to a next generation core network (NG-CN) 204 may terminate at the ANC 202. A backhaul interface to an adjacent next generation access node (NG AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more TRPs 208 (also referred to as BSs, NR BSs, gNBs, or other terms).

[0054] The TRP 208 may be a DU. The TRP may be connected to one ANC (ANC 202) or more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, the TRP 208 may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRP may be configured to serve traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., joint transmission).

[0055] The logical architecture of the distributed RAN 200 can support fronthaul solutions across different deployment types. For example, the logical architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter). The logical architecture can share features and / or components with LTE. The NG-AN 210 can support dual connectivity with NR. The NG-AN 210 can share a common fronthaul for LTE and NR. The logical architecture can enable cooperation between TRPs 208. For example, cooperation can be pre-set within and / or across TRPs via the ANC 202. An inter-TRP interface may exist.

[0056] The logical architecture of the distributed RAN 200 can support dynamic configuration of split logical functions. Figure 5 As described in more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer may be appropriately placed at the DU or CU (e.g., TRP or ANC, respectively).

[0057] Figure 3 An example physical architecture of a distributed RAN 300 according to aspects of the present disclosure is shown. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU 302 may be centrally deployed. To handle peak capacity, C-CU functions may be offloaded (e.g., to Advanced Wireless Services (AWS)).

[0058] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. The C-RU 304 may host core network functions locally. The C-RU 304 may have a distributed deployment. The C-RU 304 may be closer to the network edge.

[0059] The DU 306 may host one or more TRPs (eg, edge nodes (EN), edge units (EU), radio heads (RH), smart radio heads (SRH), etc.) The DU may be located at the edge of the network with radio frequency (RF) capabilities.

[0060] Figure 4 Shows Figure 1 Example components 400 of gNB 110 and UE 120 are shown, which may be used to implement aspects of the present disclosure for frequency hopping with large bandwidth allocations. For example, antenna 452, Tx / Rx 222, processor 466, 458, 464, and / or controller / processor 480 of UE 120 may be configured to perform Fig.11 Operation 1100 of gNB 110, and / or antenna 434, processor 460, 420, 438 and / or controller / processor 440 of gNB 110 may be configured to perform Fig.10 Operation 1000.

[0061] Figure 4 A block diagram shows a design of gNB 110 and UE 120, which may be Figure 1 For restricted association scenarios, gNB 110 may be Figure 1 1 , UE 120 may be UE 120y. gNB 110 may also be some other type of gNB. gNB 110 may be equipped with antennas 434a to 434t, and UE 120 may be equipped with antennas 452a to 452r.

[0062] At the gNB 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller / processor 440. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, e.g., for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols (if applicable), and may provide output symbol streams to modulators (MODs) 432a to 432t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

[0063] At the UE 120, antennas 452a through 452r may receive downlink signals from the gNB 110 and may provide received signals to demodulators (DEMODs) 454a through 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 454 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller / processor 480.

[0064] On the uplink, at the UE 120, the transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for reference signals. The symbols from the transmit processor 464 may be precoded by the TX MIMO processor 466, if applicable, further processed by the demodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the gNB 110. At the gNB 110, the uplink signals from the UE 120 may be received by the antennas 434, processed by the modulators 432, detected by the MIMO detector 436 (if applicable), and further processed by the receive processor 438 to obtain decoded data and control information transmitted by the UE 120. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller / processor 440 .

[0065] Controllers / processors 440 and 480 may direct operations at gNB 110 and UE 120, respectively. Processor 440 and / or other processors and modules at gNB 110 may perform or direct the execution of various processes, such as the techniques described herein. Processor 480 and / or other processors and modules at UE 120 may also perform or direct, for example, Fig. 9 and Fig.11 The processor 440 and / or other processors and modules at the gNB 110 may also perform or direct, for example, the execution of the functional blocks shown and / or other processing of the techniques described herein. Fig.10Execution of the functional blocks shown in and / or other processing of the techniques described herein. Memories 442, 482 may store data and program codes for gNB 110 and UE 120, respectively. Scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0066] Figure 5 A diagram 500 is shown illustrating an example for implementing a communication protocol stack according to aspects of the present disclosure. The communication protocol stack shown may be implemented by a device operating in a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communication protocol stack, including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, the layers of the protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-colocated devices connected by a communication link, or various combinations thereof. For example, co-located and non-co-located implementations may be used in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

[0067] The first option 505-a shows a split implementation of the protocol stack, where the implementation of the protocol stack is performed on a centralized network access device (e.g., Figure 2 ANC 202 in ) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, and the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by the DU. In various examples, the CU and the DU may be co-located or not co-located. The first option 505-a may be useful in macro cell, micro cell, or pico cell deployments.

[0068] The second option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), new radio node B (NR NB), network node (NN), etc.). In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 can all be implemented by the AN. The second option 505-b may be useful in femtocell deployment.

[0069] Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (eg, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).

[0070] Figure 6 600 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes, each of 1 ms, indexed from 0 to 9. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Depending on the subcarrier spacing, each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols). The symbol periods in each slot may be assigned indices. A small slot (which may be referred to as a subslot structure) refers to a transmission time interval (e.g., 2, 3, or 4 symbols) whose duration is less than a slot.

[0071] Each symbol in a slot may indicate the link direction (e.g., DL, UL, or flexible) used for data transmission, and the link direction may be switched dynamically for each subframe. The link direction may be based on the slot format. Each slot may include DL / UL data as well as DL / UL control information.

[0072] In NR, the synchronization signal (SS) block is transmitted. Figure 7 As shown, the SS block includes PSS, SSS and two PBCH symbols. Figure 6 Symbols 0-3 shown in the figure) transmit SS blocks. UE can use PSS and SSS for cell search and acquisition. PSS can provide half-frame timing, and SS can provide CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam scanning. Additional system information (such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI)) can be sent on the physical downlink shared channel (PDSCH) in certain subframes. SS blocks can be transmitted up to 64 times, for example, up to 64 different beam directions can be transmitted for mmW. The transmission of up to 64 SS blocks is called an SS burst set.

[0073] In some cases, two or more slave entities (e.g., UEs) may communicate with each other using sidelink signals. Practical applications of such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal transmitted from one slave entity (e.g., UE1) to another slave entity (e.g., UE2) (without relaying the communication through a scheduling entity (e.g., UE or gNB)), although the scheduling entity may be used for scheduling and / or control purposes. In some examples, licensed spectrum (unlike wireless local area networks that typically use unlicensed spectrum) may be used to transmit sidelink signals.

[0074] The UE may operate in various radio resource configurations, including a configuration associated with sending a pilot using a dedicated resource set (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with sending a pilot using a common resource set (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated resource set for sending a pilot signal to the network. When operating in the RRC common state, the UE may select a common resource set for sending a pilot signal to the network. In either case, the pilot signal sent by the UE may be received by one or more network access devices (such as an AN or DU or a portion thereof). Each receiving network access device may be configured to receive and measure the pilot signal sent on the common resource set, and for a network access device that is a member of a monitoring set of network access devices of the UE, also receive and measure the pilot signal sent on the dedicated resource set allocated to the UE. One or more receiving network access devices or a CU to which (one or more) receiving network access devices send measurement values ​​of pilot signals may use these measurement values ​​to identify the serving cell of the UE, or initiate a change to the serving cell of one or more UEs.

[0075] Various aspects of the present disclosure provide apparatus, methods, processing systems, and computer program products for new radio (NR) (new radio access technology or 5G technology). New radio (NR) may refer to a radio configured to operate according to a new air interface (e.g., different from an air interface based on orthogonal frequency division multiple access (OFDMA)) or a fixed transport layer (e.g., different from the Internet Protocol (IP)). NR may include enhanced mobile broadband (eMBB) services for broadband (e.g., above 80MHz), millimeter waves (mmW) for high carrier frequencies (e.g., 60GHz), large-scale MTC (mMTC) for non-backward compatible MTC technologies, and / or ultra-reliable low latency communications (URLLC) services for critical missions. A RAN may include a central unit (CU) and a distributed unit (DU). A NR node B (e.g., a 5G node B) may correspond to one or more transmission reception points (TRPs).

[0076] Example Techniques for Minimum Scheduling Delay Signaling

[0077] The bandwidth part (BWP) used for NR provides a way to operate the UE with a smaller bandwidth compared to the wider system bandwidth configuration. This use of BWP helps make NR an energy-efficient solution despite supporting wideband operation.

[0078] BWP adaptation can be used to support switching between cross-slot scheduling for power saving (e.g., DCI in one slot schedules events in another slot) and same-slot scheduling (e.g., DCI in one slot schedules events in the same slot), but it may be cumbersome. In addition, cross-slot scheduling for power saving may not work if non-Type-D Quasi Co-Location (QCL) aperiodic Channel State Information (CSI) requests are supported.

[0079] Figure 8 Example downlink communications for BWPs are shown. For example, time slots 802 for BWP0 may be narrowband (e.g., default BWP), time slots 804 for BWP1 may be wideband and may employ the same time slot scheduling, and time slots 806 for BWP2 may be wideband with cross-time slot scheduling. Different BWPs may correspond to different power consumptions. Thus, power may be saved by switching between BWPs (e.g., switching from a BWP with a higher corresponding power consumption to a BWP with a lower power consumption).

[0080] Fig. 9An example downlink communication with multiple BWPs with DCI is shown. As shown, the DCI in BWP0 of time slot 902 may indicate a BWP ID of 1 (eg, indicating BWP1), and select the first row (k0=2) of the table (Table 1) for k0 to schedule data in time slot 903.

[0081] The parameter k0 generally indicates the delay between a DL grant and the corresponding DL data (PDSCH) reception. As shown, the third row of Table 1 may not be addressable. In time slot 904, the DCI may indicate that the BWP ID is 1 and select the third row (k0=0) to schedule downlink data in the same time slot 904. In time slot 906, the DCI may indicate that the BWP ID is 2 (e.g., indicating BWP2) and select the second row of another table (Table 2), indicating that k0 is 1, to schedule data in time slot 908. In addition, in time slot 910, the DCI may indicate that the BWP ID is 0 and select the first row of another table (Table 0), indicating that k0=2, so as to schedule data in time slot 912. Certain aspects of the present disclosure provide enhancements by implementing a minimum k0 threshold that can be dynamically updated or explicitly configured to improve cross-slot scheduling configuration. For example, the UE may invalidate the DCI based on the indicated k0 or adjust the indicated k0 according to the minimum k0 threshold. Aspects described herein may also benefit carrier aggregation (CA) power for cross-carrier scheduling.Similar techniques may also be applied to parameter k2, which is used to indicate the delay between UL grant reception and UL data (PUSCH) transmission in DL.

[0082] Fig.10 Example operations 1000 for wireless communications are illustrated, in accordance with certain aspects of the present disclosure. Operations 1000 may be performed by a base station, such as base station 110.

[0083] Operations 1000 begin at block 1002 by determining a minimum threshold for a scheduling parameter indicating a scheduling delay between the end of a physical downlink control channel (PDCCH) transmission and the start of a transmission scheduled by the PDCCH. At 1004, the base station configures a user equipment (UE) with the minimum threshold.

[0084] In some cases, the minimum threshold can be specified in the standard, rather than the base station configuring the UE with the minimum threshold.

[0085] Fig.11 Example operations 1100 for wireless communications are shown, in accordance with certain aspects of the present disclosure. Operations 1100 may be performed by a UE, such as UE 120. Operations 1100 correspond to operations 1000, but are from the perspective of UE 120.

[0086] At block 1102, operations 1100 begin by receiving a physical downlink control channel (PDCCH) with downlink control information (DCI) signaling a scheduling parameter indicating a scheduling delay between an end of a PDCCH transmission and a start of a transmission scheduled by the PDCCH. At 1104, the UE determines that a value of the scheduling parameter is below a minimum threshold. At 1106, the UE takes at least one action in response to the determination.

[0087] In some aspects, the minimum k0 threshold may be semi-statically signaled per scheduled CC or per UE via DCI, medium access control (MAC)-control element (CE), or radio resource control (RRC) configuration. In some aspects, the minimum k0 threshold may be explicitly RRC configured per BWP. For example, entries in a PDSCH symbol allocation table with k0 less than a threshold, or entries in a PUSCH symbol allocation table with k2 less than a threshold may be implicitly considered invalid or unavailable. If an invalid entry is still indicated by scheduling, or no entry in the table is valid, an error condition may occur.

[0088] In some aspects, the DCI may indicate a value of k0 that is less than a minimum threshold, which will be considered invalid by the UE. How the UE handles this situation may be determined by the UE implementation. For example, since the UE is not expected to process a PDSCH scheduled with a k0 less than a threshold, it may discard (e.g., ignore) the DCI.

[0089] In some aspects, a threshold may be added to the k0 indication in the scheduling DCI. For example, the UE may calculate k0' based on the sum of the k0 indicated in the DCI and the k0 threshold. In this case, all entries in the PDSCH-symbol allocation table are still available and the UE may not need to discard the DCI.

[0090] In certain aspects, the minimum of the indicated k0 and the k0 threshold may be used. For example, instead of discarding the DCI, the UE may set k0 to the threshold k0 (serving as a minimum value or "floor").

[0091] In some aspects, the minimum threshold may be defined in the specification. For example, the minimum k0 threshold may be defined directly in the specification rather than being defined by explicit configuration. In some aspects, the minimum threshold may be associated with connected mode discontinuous reception (C-DRX). For example, a larger minimum k0 threshold may be used during the ON duration of the C-DRX mode, and a smaller minimum k0 threshold (or no minimum k0 threshold) may be used when the DRX inactivity timer is counting.

[0092] In certain aspects, the minimum k0 threshold may be applied not only to PDSCH scheduling, but may also be generalized to other DL scheduling, including but not limited to CSI-RS transmitted on the DL after an A-CSI request is triggered by the network. Currently, CSI-RS is transmitted in the same time slot as the A-CSI request DCI for non-type D-QCL. Although the examples provided herein have described the minimum threshold for k0 and PDSCH scheduling to facilitate understanding, aspects of the present disclosure may be similarly applied to the UL counterpart of k0, minimum k2, and PUSCH scheduling.

[0093] As described above, there are various limitations on cross-slot scheduling in current systems. One limitation is related to fast adaptation between cross-slot scheduling with BWP adaptation and same-slot scheduling. Since the time domain resource allocation (TDRA) table (i.e., PDSCH-symbol allocation table and PUSCH-symbol allocation table) is BWP-specific, some BWPs may be configured with all entries with k0>0, while some (other) BWPs may be configured with entries containing k0=0. As a result, switching between BWPs can achieve a result that adapts between minimum k0>0 and minimum k0=0.

[0094] A rather subtle issue is that during a BWP switch, for the DCI that triggers the BWP switch, the TDRA table configured for the target BWP is usually used. Since the UE does not know a priori when it will receive a BWP switch DCI, it may be difficult to guarantee that the schedulable k0 is always greater than zero even if the minimum k0 is configured to be greater than zero for the current BWP. Various approaches to address this issue are provided below.

[0095] One approach is that, for BWPs other than the current BWP (intended to support cross-time slot scheduling), if a k0=0 entry should be configured in the corresponding TDRA table, a higher index is assigned to the entry so that it cannot be addressed by the bit width of the frequency domain RA field of the current BWP. For example, assuming that for the current BWP, the frequency domain RA (FDRA) field has a bit width of 1 bit, for other BWPs, the table can be configured to ensure that the k0=0 entry (if any) is assigned an index of 2 or greater.

[0096] The BWP transition time defined in the standard specification can be made large enough so that k0=0 entries in other BWPs are considered unschedulable from the current BWP. This can meet the need for k0 indicated by cross-BWP scheduling to adjust the BWP transition time (which is defined by RAN4 to be slightly greater than 2 milliseconds for Type 2 handovers and shorter for Type 1).

[0097] For cross-BWP scheduling (which triggers BWP switching), the management of different minimum k0 values ​​across BWPs presents a challenge, since the target BWP TDRA table is usually used. As mentioned above, the minimum k0 is a function of all entries in the TDRA table, but the UE does not know a priori when a BWP will be triggered and which BWP to switch to (in the case of more than two BWPs configured). The minimum k0 that the UE must be prepared to handle can be expressed as follows:

[0098]

[0099] in:

[0100] min_k0(BWPx) is the minimum value k0 among all entries in the TDRA table of BWPx, where x={0, ..., numBWP-1}; and

[0101] numBWP is the number of configured DL BWPs.

[0102] Without loss of generality, BWP0 in the above equation can be assumed to be the current BWP. The above discussion can also be extended to the minimum value of k2. In general, the minimum k0 and minimum k2 can be more generally discussed as "minimum DL scheduling offset" and "minimum UL scheduling offset" to cover transmission requirements other than PDSCH and PUSCH (such as non-periodic CSI triggering, etc.).

[0103] For the reasons discussed above, it may be important to ensure proper support for the minimum scheduling offset configuration. A relatively simple approach is to have an explicit configuration of the minimum DL scheduling offset. This minimum DL scheduling offset can accomplish the following:

[0104] which explicitly controls the minimum value k0 that a UE is expected to handle for PDSCH scheduling, even for cross-BWP scheduling (i.e. triggering a BWP switch); and

[0105] It defines the minimum timing offset for aperiodic CSI-RS triggering

[0106] As mentioned above, more generally, such a configuration may define a minimum timing offset for all other DL channels / signals scheduled by the DCI.Similarly, a minimum UL scheduling offset may be explicitly configured to serve UL scheduling usage.

[0107] The constraints described herein may require special consideration for DCI monitored in a common search space (CSS). For DCI scrambled with an ID (e.g., SI / P / RA / TC-RNTI) and monitored with a type 0 / 0A / 1 / 2 CSS, a default or common TDRA table may be used. In addition, for DCI scrambled with CS / MCS-C / C-RNTI in the CSS in CORESET 0, a public TDRA table may be used. The default TDRA table may be fixed in the standard specification and may contain a k0=0 entry. For example, in a common configuration for PDSCH (e.g., PDSCH-ConfigCommon), a public TDRA table may be configured and provided. As a result, there may be exceptions for PDSCH scheduled under the above conditions, and the minimum DL scheduling offset may not apply to ensure proper fallback operation. The duty cycle for monitoring DCI scrambled with SI / P / RA / TC-RNTI may be set to be very small so that processing k0=0 can be avoided in most cases. For DCI scrambled with the C-RNTI detected in the CSS (if not in CORESET 0), the UE-specific TDRA table may be used (if available) so that the minimum scheduling offset may still be used.

[0108] The minimum DL / UL scheduling offset may be a property of the BWP configuration.The minimum DL / UL scheduling offset in use may be the set of values ​​associated with the currently active BWP.

[0109] like Fig. 12A and Fig. 12B As shown, in addition to the TDRA table configuration for each DL BWP, each DL BWP can be configured with one or more minimum DL scheduling offsets. Fig. 12A In the example shown, there are multiple minimum DL scheduling offsets for BWP0, and different DL scheduling offsets for BWP1. Fig. 12B In the example shown, both BWP0 and BWP1 have multiple minimum DL scheduling offsets (with the same value). The same usage of multiple values ​​can be used for minimum UL scheduling offset and UL BWP.

[0110] In the case where a particular BWP supports multiple minimum scheduling offsets, such as in Fig. 12A and Fig. 12B In the example shown, additional signaling may be used to choose which offset to select.

[0111] For example, BWP1 can be configured with minimum scheduling offsets corresponding to large and small delays. In some cases, semi-static signaling (e.g., via RRC signaling) can convey multiple values, and AC CE or DCI signaling can select which of the minimum scheduling offsets to use. For time periods with little traffic, a larger minimum scheduling offset can be selected to maximize power saving benefits. In some cases, there may be an initial minimum scheduling offset for BWP (e.g., designated as one of the configured minimum scheduling offsets). When the BWP becomes active, the initial minimum scheduling offset is implicitly selected for use. Alternatively, the minimum scheduling offset implicitly selected for use when the BWP becomes active may also be the value most recently selected for use when the BWP was last active. After (re)configuring the BWP, it may still be necessary to specify a default value when the BWP becomes active for the first time. The parameter set configured by BWP is not limited to the minimum scheduling offset, but can also be extended to include other parameters.

[0112] When signaling (e.g., DCI) changes the minimum scheduling offset value currently in use to a new value, the application time of the new value can take into account the time spent on receiving and processing the signaling. For example, for DCI signaling, the current minimum scheduling offset defines the latest time when DCI processing must be completed. Therefore, the application time of the new value can be such that it is no earlier than the current minimum scheduling offset from the time slot in which the DCI indicating the change is received. Otherwise, a stricter processing timeline may have to be imposed on the DCI processing, and power savings may be reduced. In other words, for a DCI indication of a change in the minimum scheduling offset (X), the start time of the new minimum value (X_new) can be applied in a time slot that is the maximum number of time slots (X, Z) after the DCI indicating the change is received. In this case, Z is a positive integer (e.g., Z=1) for the minimum number of time slots for applying the change.

[0113] Fig.13 An example of operation with a minimum DL scheduling offset for PDSCH is shown. As shown, a DCI indicated with a k0 less than the minimum DL scheduling offset can be considered invalid. A TDRA table entry with a k0 less than the minimum DL scheduling offset is essentially a "dummy value". Explicitly controlling the minimum scheduling offset can provide greater flexibility when configuring the TDRA table. In some cases, for tables of different BWPs, the tables can be configured with the same contents while still having different minimum scheduling offsets between the BWPs.

[0114] Fig.14An example of operation with a minimum DL / UL scheduling offset for A-CSI is shown. The minimum DL scheduling offset can also be used as at least a lower limit for the triggering offset of the aperiodic CSI-RS. The timing of the CSI-RS can be a function of the configured CSI triggering offset (fixed to zero for non-QCL-Type-D in Rel-15) and the minimum DL scheduling offset. Two examples of such a function include:

[0115] max(CSI trigger offset, minimum DL scheduling offset); or

[0116] CSI trigger offset + minimum DL scheduling offset.

[0117] Alternatively, the CSI triggering offset can be made into a parameter notified by DCI signaling and may be required to follow the minimum DL scheduling offset rule.For combined A-CSI triggering and BWP switching triggering, the network can indicate a larger CSI triggering offset to adjust the DL BWP switching waiting time.

[0118] like Fig.15 As shown in , the minimum scheduling offset can be applied with scheduling across multiple BWPs. The example shown assumes that the BWP switching wait time is 1 time slot, for BWP0, k0 is the value (2) of a single TDRA configuration, and for BWP1, k0 is the value (0, 2) of two TDRA configurations. As shown in the figure, even when the BWP switching wait time is met, the minimum DL scheduling offset may need to be met (or the PDSCH scheduled by the DCI may be discarded, as shown in the figure).

[0119] The techniques described herein may also be applied to cross-carrier scheduling (e.g., DCI received in one BWP schedules transmission in another BWP). According to certain systems, the search space configuration for cross-carrier scheduling may be based on the currently active BWP on the scheduled carrier. For the search space defined for the scheduled carrier, a linking rule may be defined for the scheduled carrier. Similar to self-scheduling, the minimum value k0 may be determined based on the TDRA table of all schedulable BWPs across the scheduled carriers and any other conditions, such as the BWP transition wait time.

[0120] For cross-carrier scheduling, there may be a greater motivation to introduce an explicit minimum scheduling offset. For example, if the traffic on the secondary cell (Scell) is small, there may be long inactivity gaps on the SCell. In this case, the UE can save more power by operating in a lower power mode (e.g., with a reduced baseband clock / voltage). The UE may even choose to suspend SCell-related processing when not scheduled, for example, with reduced CSI measurements and reporting and / or SRS transmissions.

[0121] However, in order for such power savings to be feasible, it may be necessary to ensure that the scheduling delay from the scheduling carrier (e.g., primary cell or PCell) to the scheduled carrier (e.g., SCell) is a prerequisite so that the hardware has enough time to transition to a higher power mode to handle the planned operations on the SCell. Similar to self-scheduling, this can be achieved by carefully configuring the minimum k0 of the BWP across scheduled carriers. However, there is still a potential problem in making the A-CSI trigger offset consistent with the minimum value k0. An explicit minimum scheduling offset applied to cross-carrier scheduling can help solve this problem while simplifying configuration and operation.

[0122] Fig.16 It shows how the minimum scheduling offset can be applied to cross-carrier scheduling operations. The example shown assumes that the BWP switching waiting time is 1 time slot, for BWP0, k0 is the value (3) of a single TDRA configuration, and for BWP1, k0 is the value (1, 3) of two TDRA configurations. As shown, the minimum scheduling offset of the active BWP on the scheduled carrier guarantees a certain scheduling delay. In the example shown, since BWP0 of CC1 is configured with a larger minimum DL scheduling offset, it can be a "power saving BWP". It can be used most of the time when traffic is sparse. When there is more traffic, BWP1 of CC1 can become the active BWP, and a smaller minimum DL scheduling offset can be used to reduce waiting time.

[0123] In some cases, the minimum scheduling offset can be used as UE feedback (e.g., implicitly indicating UE capabilities). For cross-carrier scheduling with different parameter sets, since additional buffering may be required and to meet the causal conditions of scheduling, a non-zero minimum DL scheduling offset may need to be configured, but the offset may depend on the UE capabilities (e.g., the ability of the buffering it is designed to support).

[0124] In this case, it may make sense for the UE to effectively report the expected minimum scheduling offset as an indication of the UE capabilities. Expanding on this point, having a sufficiently large minimum scheduling offset for cross-carrier scheduling (regardless of whether the parameter set is the same or not) may have power saving benefits. The amount of scheduling delay required to achieve power savings may depend on the UE implementation. The UE capability framework described in this article can be generalized to any cross-carrier scheduling configuration.

[0125] In some cases, a UE-based assistance framework (to report the desired minimum scheduling offset) can be used instead of the UE capability framework. In this case, the UE can report the preferred value of the minimum scheduling offset. The network can then decide how to configure the final minimum scheduling offset based on the preferred value reported by the UE.

[0126] The minimum UL scheduling offset described herein can be applied to a variety of different uplink transmissions. A sounding reference signal (SRS) is an example of such a transmission. In some cases, the minimum UL scheduling offset can be applied to an aperiodic SRS (A-SRS) sent on the uplink after a (A-SRS) request is triggered (e.g., via a DCI conveyed in a PDCCH). In this case, the A-SRS configuration can be signaled via RRC signaling and triggered via DCI.

[0127] The time granularity and / or minimum threshold of the scheduling parameters in the DCI may vary. For example, granularity in symbol resolution or time slot resolution may be used. In some cases, symbol level resolution may be derived from the scheduling parameters (e.g., as indicated in the TDRA table). In some cases, the granularity may be quantified as time slot resolution.

[0128] In some cases, the granularity may be based on the parameter set of the transmission scheduled by the PDCCH, if it is different from the parameter set of the PDCCH. In other cases, the granularity may be based on the PDCCH. In some other cases, the granularity may be based on the parameter set of the currently active BWP or a reference parameter set. As used herein, the term numerology generally refers to waveform parameters such as cyclic prefix length and subcarrier spacing (SCS). Typically, the duration of an OFDM symbol is inversely proportional to the subcarrier spacing.

[0129] The method disclosed herein includes one or more steps or actions for implementing the described method. Without departing from the scope of the claims, the method steps and / or actions can be interchangeable with each other. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0130] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, and c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as combinations with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc or any other order of a, b, and c).

[0131] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing with a computer, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), determining, etc. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Also, "determining" may include resolving, selecting, choosing, establishing, etc.

[0132] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be given a full scope consistent with the language claims, wherein, unless explicitly stated, reference to an element in the singular is not intended to mean "one and only one", but "one or more". Unless otherwise explicitly stated, the term "some" refers to one or more. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure, which are known or will be known to those of ordinary skill in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, regardless of whether such disclosure is explicitly stated in the claims, nothing disclosed herein is intended to be dedicated to the public. According to the provisions of the sixth paragraph of 35 U.S.C. § 112, unless an element is explicitly stated using the phrase "a component for...", or in the case of a method claim, an element is stated using the phrase "a step for...", no essential content shall be interpreted.

[0133] The various operations of the above methods may be performed by any suitable device capable of performing the corresponding functions. The device may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors. Generally, where operations are shown in the accompanying drawings, those operations may have corresponding corresponding device-plus-function components.

[0134] In conjunction with the various illustrative logic blocks, modules and circuits described in this disclosure, they may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable controller gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0135] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. Among other things, the bus interface may be used to connect a network adapter to the processing system via the bus. The network adapter may be used to implement signal processing functions at the PHY layer. In the UE 120 (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and will not be described in detail. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize how to best implement the described functionality for the processing system depending on the specific application and the overall design constraints imposed on the entire system.

[0136] If implemented in software, the functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Software should be broadly interpreted as referring to instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and routine processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. For example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium on which instructions separated from a wireless node are stored, all of which may be accessed by the processor through a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as where a cache and / or general register file may exist. Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0137] A software module may include a single instruction or multiple instructions and may be distributed across several different code segments, between different programs, and across multiple storage media. The computer-readable medium may include multiple software modules. The software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard drive into a RAM. During execution of a software module, the processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of the software module below, it will be understood that such functionality is implemented by the processor when instructions are executed from the software module.

[0138] Additionally, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Optical disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data using lasers. Thus, in some aspects, computer readable media may include non-transitory computer readable media (e.g., tangible media). Additionally, for other aspects, computer readable media may include transitory computer readable media (e.g., signals). Combinations of the above should also be included within the scope of computer readable media.

[0139] Thus, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded) thereon, which may be executed by one or more processors to perform the operations described herein.

[0140] In addition, it should be understood that, when applicable, the user terminal and / or base station can download and / or otherwise obtain modules and / or other appropriate devices for performing the methods and techniques described herein. For example, such a device can be coupled to a server to facilitate the transfer of devices for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.), so that the user terminal and / or base station can obtain the various methods after the storage tool is coupled or provided to the device. Moreover, any other suitable technology for providing the methods and techniques described herein to the device can be utilized.

[0141] It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made to the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment UE, comprising: receiving a physical downlink control channel, PDCCH, transmission with downlink control information, DCI, the downlink control information signaling a scheduling parameter indicating a scheduling delay between an end of the PDCCH transmission and a start of a transmission scheduled by the PDCCH; determining whether the value of the scheduling parameter is below a minimum threshold, wherein the minimum threshold is determined based on at least a parameter set of a currently active BWP; If the value of the scheduling parameter is lower than the minimum threshold, a channel state information (CSI) trigger associated with the DCI is considered invalid; and If the value of the scheduling parameter is not lower than the minimum threshold, transmitting the transmission scheduled by the PDCCH, wherein the scheduled transmission includes at least one channel state information reference signal CSI-RS sent on the downlink after an aperiodic CSI request is triggered.

2. The method according to claim 1, wherein: The value of the minimum threshold is signaled per scheduled component carrier CC or per UE via at least one of the following: DCI, Medium Access Control MAC Control Element CE or Radio Resource Control RRC configuration.

3. The method according to claim 1, wherein: One or more values ​​of the minimum threshold are configured per bandwidth part BWP.

4. The method according to claim 1, further comprising: Based on determining that the value of the scheduling parameter is lower than the minimum threshold, an entry in at least one of a physical downlink shared channel (PDSCH) symbol allocation table or a physical uplink shared channel (PUSCH) symbol allocation table whose corresponding scheduling parameter is lower than the minimum threshold is determined to be at least one of invalid or unavailable.

5. The method according to claim 1, further comprising: Signaling indicating the minimum threshold is received.

6. The method according to claim 5, wherein: The signaling indicates a selection from a set of values ​​for the minimum threshold.

7. The method according to claim 6, wherein: The set of values ​​is signaled via radio resource control (RRC) signaling; and One of the set of values ​​is selected via at least one of: a Medium Access Control MAC Control Element CE or DCI signaling.

8. The method according to claim 6, further comprising: One of the values ​​is selected based on traffic load.

9. The method according to claim 1, wherein: The value of the minimum threshold is signaled per BWP.

10. The method according to claim 1, wherein: The determination of whether the value of the scheduling parameter is below a minimum threshold is performed at an Orthogonal Frequency Division Multiplexing (OFDM) symbol resolution or a time slot resolution.

11. A method for wireless communication by a network entity, comprising: determining a minimum threshold for a scheduling parameter indicating a scheduling delay between an end of a physical downlink control channel (PDCCH) transmission and a start of a transmission scheduled by the PDCCH, wherein the minimum threshold is determined based on at least a parameter set for a currently active BWP; and The user equipment (UE) is configured with the minimum threshold value so that if the value of the scheduling parameter is lower than the minimum threshold value, the channel state information (CSI) trigger associated with the DCI is considered invalid by the UE, wherein the scheduled transmission includes at least one channel state information reference signal (CSI-RS) sent on the downlink after the non-periodic CSI request is triggered.

12. The method according to claim 11, wherein: One or more values ​​of the minimum threshold are configured per bandwidth part BWP.

13. The method according to claim 11, further comprising: Signaling is provided indicating the minimum threshold.

14. The method according to claim 13, wherein: The signaling indicates a selection from a set of values ​​for the minimum threshold.

15. The method according to claim 14, wherein: The set of values ​​is indicated via Radio Resource Control (RRC) signaling; as well as The method further comprises: Signaling selecting one of the set of values ​​is provided via at least one of: a Medium Access Control MAC Control Element CE or a DCI signaling.

16. The method of claim 15, further comprising selecting one of the values ​​based on traffic load.

17. The method according to claim 11, wherein: The value of the minimum threshold is signaled per BWP.

18. The method according to claim 11, wherein: The determination of the minimum threshold is performed with an Orthogonal Frequency Division Multiplexing (OFDM) symbol resolution or a time slot resolution.

19. An apparatus for wireless communication by a user equipment UE, comprising: means for receiving a physical downlink control channel, PDCCH, transmission with downlink control information, DCI, signalling scheduling parameters indicating a scheduling delay between an end of said PDCCH transmission and a start of a transmission scheduled by said PDCCH; means for determining whether the value of the scheduling parameter is below a minimum threshold, wherein the minimum threshold is determined based on at least a parameter set of a currently active BWP; If the value of the scheduling parameter is below the minimum threshold, a channel state information (CSI) trigger associated with the DCI is considered invalid; and If the value of the scheduling parameter is not below the minimum threshold, means for transmitting the transmission scheduled by the PDCCH, wherein the scheduled transmission comprises at least one channel state information reference signal CSI-RS sent on the downlink after an aperiodic CSI request is triggered.

20. An apparatus for wireless communication by a network entity, comprising: means for determining a minimum threshold for a scheduling parameter indicating a scheduling delay between an end of a Physical Downlink Control Channel, PDCCH, transmission and a start of a transmission scheduled by the PDCCH, wherein the minimum threshold is determined based on at least a parameter set for a currently active BWP; and A means for configuring a user equipment UE with the minimum threshold value so that if the value of the scheduling parameter is below the minimum threshold value, a channel state information CSI trigger associated with the DCI is considered invalid by the UE, wherein the scheduled transmission includes at least one channel state information reference signal CSI-RS sent on the downlink after the aperiodic CSI request is triggered.

21. An apparatus for wireless communication at a user equipment, comprising: processor; a memory coupled to the processor; as well as Instructions stored in the memory, when executed by the processor, are operable to cause the apparatus to perform operations including: receiving a physical downlink control channel, PDCCH, transmission with downlink control information, DCI, the downlink control information signaling a scheduling parameter indicating a scheduling delay between an end of the PDCCH transmission and a start of a transmission scheduled by the PDCCH; determining whether the value of the scheduling parameter is below a minimum threshold, wherein the minimum threshold is determined based on at least a parameter set of a currently active BWP; If the value of the scheduling parameter is lower than the minimum threshold, a channel state information (CSI) trigger associated with the DCI is considered invalid; and If the value of the scheduling parameter is not lower than the minimum threshold, transmitting the transmission scheduled by the PDCCH, wherein the scheduled transmission includes at least one channel state information reference signal CSI-RS sent on the downlink after an aperiodic CSI request is triggered.

22. An apparatus for wireless communication at a network entity, comprising: processor; a memory coupled to the processor; as well as Instructions stored in the memory, when executed by the processor, are operable to cause the apparatus to perform operations including: determining a minimum threshold for a scheduling parameter indicating a scheduling delay between an end of a physical downlink control channel (PDCCH) transmission and a start of a transmission scheduled by the PDCCH, wherein the minimum threshold is determined based on at least a parameter set for a currently active BWP; and The user equipment (UE) is configured with the minimum threshold value so that if the value of the scheduling parameter is lower than the minimum threshold value, the channel state information (CSI) trigger associated with the DCI is considered invalid by the UE, wherein the scheduled transmission includes at least one channel state information reference signal (CSI-RS) sent on the downlink after the non-periodic CSI request is triggered.

23. A non-transitory computer-readable medium having instructions stored thereon, which when executed by a processor of a user device, perform operations comprising: receiving a physical downlink control channel, PDCCH, transmission with downlink control information, DCI, the downlink control information signaling a scheduling parameter indicating a scheduling delay between an end of the PDCCH transmission and a start of a transmission scheduled by the PDCCH; determining whether the value of the scheduling parameter is below a minimum threshold, wherein the minimum threshold is determined based on at least a parameter set of a currently active BWP; If the value of the scheduling parameter is lower than the minimum threshold, a channel state information (CSI) trigger associated with the DCI is considered invalid; and If the value of the scheduling parameter is not lower than the minimum threshold, transmitting the transmission scheduled by the PDCCH, wherein the scheduled transmission includes at least one channel state information reference signal CSI-RS sent on the downlink after an aperiodic CSI request is triggered.

24. A non-transitory computer-readable medium having instructions stored thereon, which when executed by a processor of a network entity, perform operations comprising: determining a minimum threshold for a scheduling parameter indicating a scheduling delay between an end of a physical downlink control channel (PDCCH) transmission and a start of a transmission scheduled by the PDCCH, wherein the minimum threshold is determined based on at least a parameter set for a currently active BWP; and The user equipment (UE) is configured with the minimum threshold value so that if the value of the scheduling parameter is lower than the minimum threshold value, the channel state information (CSI) trigger associated with the DCI is considered invalid by the UE, wherein the scheduled transmission includes at least one channel state information reference signal (CSI-RS) sent on the downlink after the non-periodic CSI request is triggered.

Images