Method and apparatus for scheduling application delays

Abstract

Certain aspects of the present disclosure provide techniques for managing scheduling of wireless communications. A method that may be performed by a user equipment (UE) includes receiving one or more configurations indicating a plurality of minimum scheduling offset values ​​from a base station; receiving a signal from the base station indicating one of the minimum scheduling offset values ​​as an updated value to be used for communicating with the base station and indicating a scheduling type; determining a delay based on the scheduling type; and upon receiving the signal, communicating with the base station using the updated value based on the determined delay.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 039,610, filed on September 30, 2020, which claims the benefit of and priority to U.S. Provisional Application No. 62 / 909,223, filed on October 1, 2019, U.S. Provisional Application No. 62 / 911,164, filed on October 4, 2019, and U.S. Provisional Application No. 62 / 976,856, filed on February 14, 2020, each of which is hereby expressly incorporated herein by reference in its entirety. Background Art

[0003] Public domain

[0004] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for managing transmission schedules.

[0005] Related technical description

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include Third 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, to name just a few.

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed 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). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0008] However, as the demand for mobile broadband access continues to grow, 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.

[0009] Overview

[0010] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide advantages including the desired scheduling of wireless communications.

[0011] Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes receiving one or more configurations indicating a plurality of minimum scheduling offset values ​​from a base station and receiving a signal from the base station indicating one of the minimum scheduling offset values ​​as an updated value to be used for communication with the base station and indicating a scheduling type. The method also includes determining a delay based on the scheduling type and, after receiving the signal, communicating with the base station using the updated value based on the determined delay.

[0012] Certain aspects provide a method for wireless communication by a base station (BS). The method generally includes selecting one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a UE and transmitting a signal indicating the updated value and a scheduling type to the UE. The method further includes determining a delay based on the scheduling type and, after transmitting the signal, communicating with the UE using the updated value based on the determined delay.

[0013] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes a transceiver, a memory, and a processor. The transceiver is configured to receive one or more configurations indicating a plurality of minimum scheduling offset values ​​from a base station and to receive a signal from the base station indicating one of the minimum scheduling offset values ​​as an updated value to be used for communication with the base station and indicating a scheduling type. The processor is coupled to the memory, and the processor and the memory are configured to determine a delay based on the scheduling type. The transceiver is further configured to communicate with the base station using the updated value based on the determined delay.

[0014] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes a memory, a processor, and a transceiver. The processor is coupled to the memory, and the processor and the memory are configured to select one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a UE. The transceiver is configured to transmit a signal indicating the updated value and a scheduling type to the UE. The processor and the memory are further configured to determine a delay based on the scheduling type. After transmitting the signal, the transceiver is configured to communicate with the UE using the updated value based on the determined delay.

[0015] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes means for receiving from a base station one or more configurations indicating a plurality of minimum scheduling offset values; means for receiving from the base station a signal indicating one of the minimum scheduling offset values ​​as an updated value to be used for communication with the base station and indicating a scheduling type; means for determining a delay based on the scheduling type; and means for communicating with the base station using the updated value based on the determined delay after receiving the signal.

[0016] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes means for selecting one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a UE; means for transmitting a signal to the UE indicating the updated value and a scheduling type; means for determining a delay based on the scheduling type; and means for communicating with the UE using the updated value based on the determined delay after transmitting the signal.

[0017] Certain aspects provide a computer-readable medium having stored thereon instructions for receiving one or more configurations indicating a plurality of minimum scheduling offset values ​​from a base station; receiving a signal from the base station indicating one of the minimum scheduling offset values ​​as an updated value to be used for communicating with the base station and indicating a scheduling type; determining a delay based on the scheduling type; and upon receiving the signal, communicating with the base station using the updated value based on the determined delay.

[0018] Certain aspects provide a computer-readable medium having instructions stored thereon for selecting one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a UE; transmitting a signal to the UE indicating the updated value and a scheduling type; determining a delay based on the scheduling type; and after transmitting the signal, communicating with the UE using the updated value based on the determined delay.

[0019] To achieve the foregoing and related purposes, one or more aspects include the features that are fully described hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of one or more aspects. However, these features are merely indicative of the many ways in which the principles of the various aspects may be employed. Brief Description of the Drawings

[0021] For a more particular description of the ways in which the above-recited features of the present disclosure can be understood, reference may be made to the aspects, some of which are illustrated in the drawings. It is to be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, for the description may admit to other equally effective aspects.

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

[0023] Figure 2 is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) in accordance with certain aspects of the present disclosure.

[0024] Figure 3 illustrates an example frame format for a telecommunications system in accordance with certain aspects of the present disclosure.

[0025] Figure 4A illustrates an example cross-slot scheduling for downlink communication in accordance with certain aspects of the present disclosure.

[0026] Figure 4B illustrates an example in-slot scheduling for uplink communication in accordance with certain aspects of the present disclosure.

[0027] Figure 5 illustrates an example cross-bandwidth part (BWP) scheduling for downlink communication in accordance with certain aspects of the present disclosure.

[0028] Figure 6 illustrates an example cross-carrier scheduling for downlink communication in accordance with certain aspects of the present disclosure.

[0029] Figure 7 illustrates an example diagram of the minimum scheduling offset value according to BWP in accordance with certain aspects of the present disclosure.

[0030] Figure 8 illustrates an example cross-carrier scheduling for downlink communication in accordance with certain aspects of the present disclosure, wherein the application delay is defined according to the parameters of the target BWP.

[0031] Fig. 9AExample self-carrier scheduling of downlink communications in accordance with certain aspects of the present disclosure is illustrated, wherein application delay is defined according to parameter design of an active BWP.

[0032] Fig. 9B Example self-carrier scheduling of downlink communications in accordance with certain aspects of the present disclosure is illustrated, wherein application delay is defined according to parameter design of a target BWP.

[0033] Fig. 10A Diagram illustrating multiple time slots of a scheduling carrier overlapping a single time slot of a scheduled carrier in accordance with certain aspects of the present disclosure.

[0034] Fig. 10B Diagram illustrating a single time slot of a scheduling carrier overlapping multiple time slots of a scheduled carrier in accordance with certain aspects of the present disclosure.

[0035] Fig.11 is a flow diagram illustrating example operations for wireless communications by a UE in accordance with certain aspects of the present disclosure.

[0036] Fig.12 is a flow diagram illustrating example operations for wireless communications by a BS in accordance with certain aspects of the present disclosure.

[0037] Fig.13A An example of scheduling of downlink communications in which a minimum scheduling offset is updated is illustrated in accordance with certain aspects of the present disclosure.

[0038] Fig. 13B Another example of scheduling of downlink communications in which a minimum scheduling offset is updated is illustrated in accordance with certain aspects of the present disclosure.

[0039] Fig.14 Illustrated are communications devices (eg, UEs) that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0040] Fig.15 A communication device (eg, a BS) according to aspects of the present disclosure is illustrated that may include various components configured to perform operations for the techniques disclosed herein.

[0041] 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.

[0042] Detailed Description

[0043] Various aspects of the present disclosure provide devices, methods, processing systems, and computer-readable media for scheduling wireless transmissions, including, for example, a framework for determining when to apply an updated value of a minimum scheduling offset. This scheduling framework can improve the efficiency of wireless communications, including reduced power consumption and / or reduced signaling overhead.

[0044] The following description provides an example of managing transmission scheduling in a communication system, without limiting the scope, applicability or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionalities, or structures and functionalities as supplements to the various aspects of the present disclosure set forth herein or in addition. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or explanation". Any aspect described as "exemplary" herein is not necessarily to be interpreted as being superior to or superior to other aspects.

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

[0046] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. For example, the wireless communication network 100 may be an NR system (e.g., a 5G NR network). As shown, the BS 110a includes a scheduling manager 112 that determines when to apply an updated value of a minimum scheduling offset (e.g., based on application delays) and / or performs various other operations for managing scheduled transmissions in accordance with aspects of the present disclosure. The UE 120a includes a scheduling manager 122 that determines when to apply an updated value of a minimum scheduling offset (e.g., based on application delays) and / or performs various other operations for managing scheduled transmissions in accordance with aspects of the present disclosure.

[0047] NR access (e.g., 5G NR) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmWave) targeting high carrier frequency (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission-critical services targeting 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 corresponding quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0048] like Figure 1 As illustrated in , the wireless communication network 100 may include several base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively referred to as BS 110) and other network entities. BS 110 may provide communication coverage for a specific geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 using any suitable transport network via various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.). Figure 1 In the example shown in , BS110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS110x may be a pico BS for a pico cell 102x. BS110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. The BS may support one or more cells. BS110 communicates with user equipment (UE) 120a-y (each also individually referred to herein as UE 120 or collectively referred to as UE 120) in the wireless communication network 100. UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.

[0049] The wireless communication network 100 may also include a relay station (e.g., relay station 110r) (also referred to as a relay, etc.) that receives transmissions of data and / or other information from an upstream station (e.g., BS110a or UE 120r) and sends transmissions of the data and / or other information to a downstream station (e.g., UE 120 or BS110), or relays transmissions between UEs 120 to facilitate communication between the devices.

[0050] A network controller 130 may couple to a set of BSs 110 and provide coordination and control for the BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0051] Figure 2 1 and 120a (eg, in a BS 110a and a UE 120a) that can be used to implement various aspects of the present disclosure are illustrated. Figure 1 Example components of the wireless communication network 100).

[0052] At BS 110a, a transmit processor 220 may receive data from a data source 212 and control information from a controller / processor 240. 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), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 220 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH demodulation reference signal (DMRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide output symbol streams to modulators (MODs) 232a-232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 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 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0053] At UE 120a, antennas 252a-252r may receive downlink signals from BS 110a and may provide received signals to demodulators (DEMODs) 254a-254r in the transceiver, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 260, and provide decoded control information to a controller / processor 280.

[0054] On the uplink, at the UE 120a, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by a demodulator 254a-254r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signal from the UE 120a may be received by the antenna 234, processed by the modulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120a. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240 .

[0055] Memories 242 and 282 may store data and program codes for BS 110a and UE 120a, respectively.A scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0056] The controller / processor 280 and / or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. Figure 2As shown, the controller / processor 280 of UE 120a has a scheduling manager 281, which determines when to apply the updated value of the minimum scheduling offset and / or performs various other operations for managing scheduled transmissions in accordance with various aspects described herein. The controller / processor 240 of BS110a has a scheduling manager 241, which determines when to apply the updated value of the minimum scheduling offset and / or performs various other operations for managing scheduled transmissions in accordance with various aspects described herein. Although shown as being at the controller / processor, other components of UE 120a and BS110a may also be used to perform the operations described herein.

[0057] Figure 3 300 is a diagram showing an example of a frame format 300 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 with indices 0 to 9, each subframe being 1 ms. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7, 12, or 14 symbols), depending on the subcarrier spacing. An index may be assigned to the symbol period in each slot. A mini slot (which may be referred to as a subslot structure) refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

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

[0059] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and two-symbol PBCH. The SS block can be in a fixed time slot position (such as Figure 3) is transmitted in the codewords 0-3 shown in . PSS and SSS can be used by UE 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 a radio frame, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam sweeping. Further system information (such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI)) can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes. SS blocks can be transmitted up to 64 times, for example, for mmW, up to 64 different beam directions are used to transmit. Up to 64 transmissions of SS blocks are called SS burst sets. SS blocks in SS burst sets are transmitted in the same frequency region, while SS blocks in different SS burst sets can be transmitted at different frequency positions.

[0060] In certain wireless communication networks (e.g., 5G NR), scheduling events (such as DL / UL resource grants or non-periodic triggers) can be supported on a cross-slot basis or on an intra-slot (i.e., the same slot) basis. For example, under cross-slot scheduling, a UE may receive downlink control signaling (e.g., downlink control information (DCI) message) in a slot that schedules the UE to receive DL transmissions in another slot. Under intra-slot scheduling, a UE may receive DCI in a slot that schedules the UE to receive DL transmissions later in the same slot. Switching from intra-slot scheduling to cross-slot scheduling enables the UE to reduce power consumption. For example, cross-slot scheduling may facilitate longer micro-sleep periods (e.g., when the radio interface is temporarily disabled but signal processing is enabled), such as when PDCCH processing is outside a critical timeline. A longer scheduling offset under cross-slot scheduling may give the UE enough time to wake up from sleep and enable the radio interface. Scheduling events via cross-slot scheduling or intra-slot scheduling may be applicable to DL / UL resource grants (eg, PDSCH / PUSCH) and other DCI-triggered events such as aperiodic channel state information reference signal (A-CSI-RS) monitoring and reporting.

[0061] Figure 4A 402 may be a time slot in which a UE receives a DCI 402 from a BS via a control channel such as a PDCCH. n is received and indicates the scheduling time slot n+1The DL scheduling offset parameter k0 is greater than zero and provides a delay between a DL grant (DCI 402) and corresponding DL data reception (e.g., via PDSCH). In some aspects, the delay between control signaling (DCI 402) and data transmission 404 may enable the UE to enter a micro-sleep state to reduce power consumption. In this example, in a time slot (e.g., time slot n+1 ), the UE may not wait for the PDCCH processing to complete before entering the micro-sleep state because the UE has already received the PDCCH from the previous time slot (e.g., time slot n ) received in the PDCCH to know the gNB for the time slot (e.g., time slot n+1 ) whether PDSCH will be transmitted.

[0062] Figure 4B 406. Example time slot scheduling of downlink communications in accordance with certain aspects of the present disclosure is illustrated. The UE may receive DCI 406 from the BS via a control channel such as the PDCCH. The DCI 406 may be in the time slot n+1 is received and indicates scheduling the same time slot n+1 408 in the timeslot in which the UE sends a micro-sleep signal (e.g., via parameter k0). In this case, the DL scheduling offset parameter k0 is zero and does not provide a delay between the DL grant (DCI 406) and the corresponding DL data transmission (e.g., via PDSCH). In order to enter the micro-sleep state within a timeslot, the UE must wait for the PDCCH processing to complete to ensure that PDSCH is not scheduled for the same timeslot, while still keeping receiving and buffering Rx samples in the event that the DL scheduling DCI is decoded to indicate a PDSCH transmission in the same timeslot by the BS. Therefore, the timeslot portion that allows micro-sleep is different from the cross-slot scheduling scenario (e.g., Figure 4A ) is much smaller than that of the UE, which may result in less power savings. In some cases, intra-slot scheduling may enable UEs to communicate via URLLC services due to the smaller delay between control signaling (DCI 402) and data transmission 404.

[0063] In some wireless communication networks (e.g., 5G NR), bandwidth parts (BWPs) provide a flexible framework for dividing frequency domain resources in a given carrier. Using bandwidth parts, carriers can be subdivided into different bandwidth segments. For example, BWPs can overlap each other or can be non-contiguous (i.e., separated from each other by guard bands, for example). BWPs can also be used for various purposes or functions. For example, during a period of low data activity (e.g., low throughput requirements), the UE can communicate with a narrower BWP, while during a period of high data activity (e.g., high throughput requirements), the UE can communicate with a wider BWP. Compared with a wider BWP, a narrower BWP can provide a more energy-efficient solution for wireless communication. That is, the UE can switch from a wider BWP to a narrower BWP to enable the power consumption of wireless communication to be reduced. As another example, different BWPs can be used for different services or functions, such as eMBB or URLLC transmission. In some cases, different BWPs can enable the coexistence of other systems or networks.

[0064] Figure 5 5 illustrates example cross-BWP scheduling of downlink communications in accordance with certain aspects of the present disclosure. The UE may receive DCI 502 from the BS via a control channel on a first BWP (eg, a narrow BWP). The DCI 502 may be in a time slot m+1 A BWP identifier received in the BWP and indicating a second BWP (eg, a wider BWP) and a time slot for scheduling the second BWP m+2 The BWP identifier may be a value (integer value) used to refer to a BWP in the BWP configured on the UE. After a certain duration, the UE may, for example, x A DCI 506 is received in the process, the DCI indicating that a switch to a first BWP (eg, a narrow BWP) is to be performed.

[0065] In certain wireless communication networks (e.g., 5G NR), a minimum scheduling offset may be used to determine various actions associated with downlink scheduled events (such as DL / UL grants, cross-BWP scheduling, or cross-carrier scheduling). In some aspects, the minimum scheduling offset may be the minimum applicable value for k0, k2, and A-CSI-RS triggering. In the event that k0 / k2 is lower than the minimum scheduling offset, the UE may invalidate the DCI based on the indicated k0 / k2 or adjust the indicated k0 / k2 according to the minimum scheduling offset. In other cases, when the UE receives an indication of a minimum scheduling offset for k0 / k2, the UE may not expect an entry in the active DL (UL) time domain resource allocation (TDRA) table with a k0(k2) value less than the indicated minimum value.

[0066] One or more values ​​of the minimum scheduling offset may be configured via downlink control signaling, such as radio resource control (RRC) signaling and / or DCI. For example, the UE may be directly assigned a minimum scheduling offset value via DCI signaling. In other cases, the UE may receive an indication of the minimum scheduling offset value from one or more values ​​preconfigured by RRC signaling. The L1-based adaptation of the minimum scheduling offset may be in addition to the time domain resource allocation adaptation based on BWP switching. A non-zero A-CSI-RS triggering offset may be used for non-type D quasi-co-location (QCL) monitoring and reporting. The minimum A-CSI-RS triggering offset may be implicitly indicated based on the minimum value of k0. The L1-based adaptation of the minimum applicable value of k0 may not be applicable to SI / RA / TC / P-RNTI in the type 0 / 0A / 1 / 2 common search space, respectively. The L1-based adaptation of the minimum applicable value of k2 may not be applicable to PUSCH scheduled by MAC RAR for contention-based and contention-free RACH or PUSCH scheduled by TC-RNTI.

[0067] In a multi-carrier or multi-BWP configuration, the minimum scheduling offset value may be ambiguous based on different parameter designs associated with the carriers and / or BWPs. For example, a UE configured with a minimum scheduling offset value may misunderstand the minimum scheduling offset value for cross-BWP scheduling when the target BWP has a different parameter design than the active BWP that receives the cross-BWP scheduling instruction. For example, assume that the target BWP has a subcarrier spacing (SCS) of 30kHz, the active BWP has an SCS of 15kHz, and the minimum scheduling offset is defined by time slot. In this scenario, the time slot duration of the active BWP is 1ms, while the time slot duration of the target BWP is 0.5ms, which may cause the UE to attempt to apply the minimum scheduling offset at half of the expected duration. As a result, the misunderstood minimum scheduling offset may result in lost transmissions and / or increased power consumption. In other cases, the minimum scheduling offset may be updated to handle different parameter designs, but this approach may result in increased downlink signaling / overhead.

[0068] Base stations and / or UEs may use various frameworks to determine the minimum scheduling offset for downlink triggering events under multi-carrier and / or multi-BWP configurations. This scheduling framework may improve the efficiency of wireless communications, including reduced power consumption and overhead signaling. As an example, the minimum scheduling offset may be given by time domain resources (e.g., number of time slots) according to parameter design of active BWP, reference parameter design, or a set of values ​​associated with various BWPs. In other cases, the minimum scheduling offset may be set according to units of k0 or k2. As another example, the minimum scheduling offset may be set according to an absolute time value. Under cross-BWP and / or cross-carrier scheduling, the minimum scheduling offset may be defined by component carrier (CC) (e.g., shared across BWPs in a given CC) or by BWP, as further described herein. The UE may be configured with various values ​​of the minimum scheduling offset via downlink control signaling (including downlink control information (DCI), media access control (MAC) control element (CE), or radio resource control (RRC) configuration).

[0069] In the case where the minimum scheduling offset is defined per CC, the minimum scheduling offset may be defined per a specified parameter design for a BWP (e.g., 15kHz SCS). In various aspects, the minimum scheduling offset may have a value associated with each BWP in a CC (e.g., minimum scheduling offset parameter, X=2 slots for 15kHz SCS, and X=4 slots for 30kHz SCS). In other aspects, the minimum scheduling offset may be defined as an absolute time value (e.g., 2 milliseconds). When applied to k0 or k2, the minimum scheduling offset may be converted to the corresponding SCS of the PDSCH or PUSCH.

[0070] In some cases, a per-CC defined minimum scheduling offset may not be well suited in the case of a BWP for different data usage scenarios, such as a narrow BWP for low data usage and low power consumption. For example, when switching to a narrower BWP, it may be desirable to also change the minimum scheduling offset that facilitates power savings (e.g., a longer minimum scheduling offset). As another example, when switching to a wider BWP, it may be desirable to have a shorter minimum scheduling offset to facilitate lower latency communications. If the minimum scheduling offset is shared across CCs, this may result in higher signaling overhead, for example, to update the minimum scheduling offset when switching BWPs. The minimum scheduling offset may instead be defined per BWP to account for changes in parameter design or functionality of the BWP.

[0071] In certain aspects, the minimum scheduling offset may be defined per BWP according to various frameworks. For example, when the UE is instructed to switch from an active BWP to a target BWP (e.g., triggered by cross-BWP scheduling), the minimum scheduling offset may be defined according to the parameter design of the active BWP. In other cases, the minimum scheduling offset may be defined according to the parameter design of the target BWP. In various aspects, the minimum scheduling offset may be defined according to the maximum of the minimum value associated with the active BWP and the minimum value associated with the target BWP. In various aspects, the minimum scheduling offset may be defined according to the sum of the minimum value associated with the active BWP and the minimum value associated with the target BWP. In other aspects, the minimum scheduling offset may be defined independently for cross-BWP scheduling.

[0072] In the case where the minimum scheduling offset is defined according to the parameter design of the active BWP, the minimum scheduling offset provides the same delay as scheduling within the same BWP before the BWP switch. If the current BWP and the target BWP have different parameter designs, and if the minimum scheduling offset is defined in terms of the number of time slots in the parameter design of the current BWP, then the conversion of this offset to the parameter design of the target BWP can be applied to the cross-BWP scheduling. For example, the minimum scheduling offset conversion can be given by the following formula:

[0073]

[0074] Where X' is the converted minimum schedule offset, X is the minimum schedule offset being converted, such as the minimum offset associated with an active BWP, and μ BWP,target is the parameter design of the target BWP, μ BWP,curr It is the parameter design of active BWP.

[0075] In various aspects, the DL / UL grant parameters (k0, k2) can be checked according to the following formula:

[0076] {K0|K2}≥X′ or X (2)

[0077] Where X' is the converted minimum schedule offset for cross-BWP scheduling for triggering BWP switching between BWPs with different parameter designs. For intra-BWP scheduling, X is the minimum schedule offset per active BWP.

[0078] In some aspects, a UE may receive a cross-carrier schedule on a component carrier that schedules transmission on another component carrier. Figure 6An example cross-carrier scheduling of downlink communications is illustrated. Assuming that the BWPs have the same parameter design, the BWP switching delay is configured to 1 slot, the minimum scheduling offset (X) associated with BWP0 on CC1 is set to 3 slots, the minimum scheduling offset (X) associated with BWP1 on CC1 is set to 1 slot, and BWP0 and BWP1 can each be configured with various values ​​of k0. As shown, the UE can receive DCI 602 from the BS via a control channel (such as PDCCH) on CC0. The DCI 602 can be in the slot n is received and indicates a scheduling offset (e.g., k0=3) which is received in time slot n+3 A cross-carrier DL data transmission 604 on BWP0 of CC1 is scheduled.

[0079] When the minimum scheduling offset value for BWP0 (minimum k0=3) is active based on the received DCI 602, if the UE is in the time slot n+1 DCI 606 is received from the BS on CC0 and DCI 606 indicates that n+2 If the scheduling offset k0=1 for the cross-carrier DL data transmission 608 on BWP1 of CC1 is scheduled, this does not satisfy the minimum scheduling offset of 3 time slots for the active BWP, and the UE may take various actions, such as treating the DCI as invalid (e.g., ignoring the scheduling grant) or applying a default scheduling offset value, as further described herein.

[0080] As another example, the UE n+3 In the embodiment, DCI 610 is received from the BS on CC0 and DCI 610 indicates a scheduling offset of k0=4, which is in the time slot n+7 612, which sets the minimum scheduling offset value (minimum k0=1) for BWP1 to the current value. When the minimum scheduling offset value (minimum k0=1) for BWP1 is active based on receiving DCI 610, the UE performs cross-carrier DL data transmission on BWP1 of CC1 in time slot n+7 In the example, DCI 614 is received from the BS on CC0 and DCI 614 indicates a scheduling offset of k0=1, which is in the time slot n+8 The cross-carrier DL data transmission 616 on BWP1 of CC1 is scheduled in. The DL scheduling of DCI 614 satisfies the currently active minimum scheduling offset value of BWP1.

[0081] Example Scheduling Application Delay

[0082] In certain wireless communication systems (e.g., 5G NR), in order to adapt the minimum applicable value of k0(k2) for the active DL(UL) BWP for a carrier in which PDSCH (PUSCH) is transmitted, the UE may be configured with multiple minimum scheduling offset values ​​(e.g., up to two RRC-configured values ​​for DL ​​and UL grants). Figure 7 An example diagram illustrating minimum scheduling offset values ​​by BWP in accordance with certain aspects of the present disclosure is shown. Figure 7 , the UE may be configured with two minimum scheduling offset values ​​(minimum k0=0 or 1) for DL ​​BWP 702 and two minimum scheduling offset values ​​(e.g., minimum k2=1 and 2) for UL BWP 704. In this example, the control signaling (e.g., DCI) may have a 1-bit indication 706 which of the minimum scheduling offset values ​​for the UE is selected for communication.

[0083] In some cases, a configuration with only one minimum scheduling offset value may be considered as configuring one of two values, with the other value being considered a default value. The RRC configuration of the minimum scheduling offset value may be per BWP. The minimum scheduling offset value may be based on the parameter design of the BWP associated with the RRC configuration. If there are multiple RRC configured minimum scheduling offset values ​​for a BWP, a bit flag (e.g., a 1-bit indication) may activate one value from multiple candidate values. A bit flag in DCI format 1_1 or format 0_1 ​​may be used to jointly select the minimum applicable k0 for an active DL BWP and the minimum applicable k2 value for an active UL BWP, both of which will be applied at least after an application delay.

[0084] When a BWP is activated without selecting a minimum scheduling offset value, a default value may be used as the current minimum scheduling offset value until a 1-bit indication is received. For a BWP that is activated without receiving a 1-bit indication in the DCI (for adapting the minimum applicable value of k0(k2) for the BWP when there are one or two RRC-configured values ​​for the BWP) (e.g., due to BWP switching triggered by expiration of a BWP timer, etc.), the value applied to the BWP may be determined by selecting any suitable value if there is only one RRC-configured value or by selecting the lowest indexed RRC-configured value if there are multiple RRC-configured values. In other cases, when a BWP is activated without selecting a minimum scheduling offset value, the value applied to the BWP may be determined by selecting the configured value if one value is RRC-configured or by selecting the lowest indexed RRC-configured value if multiple values ​​are RRC-configured. In other cases, when a BWP is activated without selecting a minimum scheduling offset value, the value applied to the BWP may be determined by selecting any suitable value. Although to facilitate understanding, the examples provided herein are described with reference to a 1-bit indicator flag that selects one of two minimum scheduling offset values, aspects of the present disclosure may also be applicable to a bitmap or index that selects one of multiple minimum scheduling offset values.

[0085] In certain wireless communication systems (e.g., 5G NR), the UE may determine when to apply an updated value of the minimum scheduling offset, as described herein. As an example, if a bit flag in the DCI indicates a change in the minimum scheduling offset value, the UE may apply the change after a certain application delay expires. For example, for active DL BWP and active UL BWP, when the UE is instructed to change the minimum scheduling offset value of k0 and / or k2 through L1-based signaling (s) in time slot n, the UE may not expect to apply the new minimum scheduling offset value before the time slot value given by:

[0086]

[0087] where X = max(Y, Z) may be in the parameter design for scheduling PDCCH, and Y is the minimum scheduling offset value of k0(k2) in the parameter design for the scheduled transmission before the indicated change (which may be converted to a conversion factor =Y+Z is another way to ensure that X is at least as large as the minimum feasible non-zero application delay. In some cases, this mechanism to determine when to apply a new minimum scheduling offset may not be appropriate for certain scheduling scenarios (e.g., cross-carrier scheduling) or may result in inefficiencies such as increased latency or inefficient power consumption.

[0088] In some cases, the minimum scheduling offset of k0 (or k2) that determines the value of Y may not be configured for the active DL (or UL) BWP, and the application delay may be based on various default values ​​of the minimum scheduling offset. In one example, a fixed value (e.g., zero) may be assumed as the value of Y. In another example, the minimum k0 (or k2) configured for the active DL (or UL) BWP in the TDRA table may be assumed to be the value of Y. In some cases, the UE may anticipate the configuration of the minimum scheduling offset for k0 (or k2), and the application delay may be determined without the default value of the minimum scheduling offset.

[0089] Certain aspects of the present disclosure provide an enhancement scheme to improve the framework for updating the minimum scheduling offset based on the application delay when the updated minimum scheduling offset is applied. In general, the actual start time of the updated minimum value may not be earlier than the current minimum value. Considering that cross-BWP scheduling may trigger BWP switching with different parameter designs, it will be more general to define the application delay in terms of the earliest time slot in which transmission can be scheduled by applying the updated minimum value, rather than defining the starting time slot for applying the updated minimum value with respect to the parameter design for scheduling PDCCH. Under this definition, the earliest time slot that can be scheduled when k0 (or k2) satisfies the updated minimum value, as defined in the parameter design of k0 (or k2), can be expressed as:

[0090]

[0091] where μ BWP,target is the parameter design of the target BWP (e.g., scheduled PDSCH or PUSCH) and μ BWP,curris the parameter design of the active BWP before the BWP switching (e.g., for DL ​​BWP, the PDCCH on which control signaling is received). Note that one difference compared to equations (3) and (4) is that n is defined in units of time slots of k0 or k2 (i.e., scheduled PDSCH / PUSCH), rather than in units of time slots of PDCCH. Similar to equations (3) and (4), X=max(Y,Z), Y can be the minimum scheduling offset value of k0 (or k2) before the indicated change, and Z can be the minimum feasible non-zero application delay (e.g., 1). In some aspects, Y with reference to equations (3) and (4) can be the minimum of the minimum scheduling offset value from k0 and the minimum scheduling offset value of k2. In other aspects, the application delay can be determined based on an absolute time value, the number of time domain resources (e.g., time slots), or a BWP switching delay value. In other aspects, if the scheduled transmission is for PDSCH (e.g., DCI format 1_1 (DL scheduled DCI) is received on PDCCH), then Y with reference to equations (3) and (4) can be the minimum value of the minimum scheduling offset value from k0, and if the scheduled transmission is for PUSCH (e.g., DCI format 0_1 ​​(UL scheduled DCI) is received on PDCCH), then Y with reference to equations (3) and (4) can be the minimum value of the minimum scheduling offset value from k2.

[0092] Since the application delay can be derived according to equations (3) and (4) by the minimum scheduling offset value per time domain resource (e.g., number of time slots) according to the parameter design of a specific BWP (e.g., the parameter design of a BWP configured with the minimum scheduling offset), there may be uncertainty based on different parameter designs associated with carriers and / or BWPs, especially in cross-carrier scheduling scenarios. For example, assume that the target BWP has a subcarrier spacing (SCS) of 30kHz, the active BWP has an SCS of 15kHz, and the minimum scheduling offset is defined per time slot. In this scenario, the time slot duration of the active BWP is 1ms, while the time slot duration of the target BWP is 0.5ms, which may cause the UE to attempt to apply the minimum scheduling offset and / or application delay at half of the expected duration. As a result, the misunderstood minimum scheduling offset and / or application delay may result in lost transmissions and / or increased power consumption. In other cases, the minimum scheduling offset and / or application delay may be updated to handle different parameter designs between the active BWP and the target BWP, but this approach may result in increased downlink signaling / overhead.

[0093] Aspects of the present disclosure generally relate to a framework for determining when to apply an updated value of a minimum scheduling offset. This scheduling framework can improve the efficiency of wireless communications, including reduced power consumption and / or reduced signaling overhead. In some aspects, the application delay for cross-carrier scheduling can be defined according to the parameter design of the scheduling CC or the parameter design of the active BWP or target BWP of the scheduled CC. In other aspects, the application delay for self-carrier scheduling can be defined according to the parameter design of the active BWP or the target BWP.

[0094] In certain aspects, the application delay for cross-carrier scheduling may be defined according to the parameter design of the active BWP of the scheduling CC (i.e., the parameter design of the scheduling PDCCH). Since the transitional application delay value may be in accordance with the parameter design of the scheduled CC (e.g., the parameter design of the scheduled PDSCH or PUSCH), the application delay may be converted into the parameter design of the scheduling CC according to the following formula:

[0095]

[0096] Where X may be a transition value based on the application delay of at least one of the minimum scheduling offset values ​​described herein with reference to equations (3) and (4), for example.

[0097] Assume that the current value of the application delay is X=3, the PDSCH has an SCS of 120kHz on the scheduled CC, and the PDCCH has an SCS of 30kHz on the scheduling CC. In this example, equation (7) provides an application delay of 3 / 4 (which may be rounded to 1). In this case, the updated scheduling offset is applied in the next time slot of the scheduling CC from the receipt of the PDCCH.

[0098] In certain aspects, the application delay for cross-carrier scheduling can be defined according to the parameter design of the target BWP of the scheduled CC. This technique avoids the conversion step to the parameter design of the scheduling CC. In other words, the application delay can remain in the parameter design domain of the scheduled CC.

[0099] Figure 8 An example cross-carrier scheduling of downlink communications in accordance with certain aspects of the present disclosure is illustrated, where an application delay is defined according to a parameter design of a target BWP of a scheduled CC. Assume that BWP0 of CC0 has a parameter design associated with a 30kHz SCS, BWP0 of CC1 has a parameter design associated with a 120kHz SCS, and the current minimum scheduling offset (X) associated with BWP0 on CC1 is set to 3 slots. As shown, the UE may communicate with the time slot of CC1 via a control channel (such as a PDCCH) on CC0. nThe DCI 802 is received from the BS in accordance with the above. The DCI 802 indicates an updated value of the minimum scheduling offset (eg, minimum k0=1). As an example, the DCI 802 may also be used to schedule the 3-slot scheduling offset in the time slot. n+3 The UE may schedule cross-carrier DL data transmission on BWP0 of CC1 at 804. As another example, the UE may also schedule cross-carrier DL data transmission on BWP0 of CC1 at 804. n+2 In the embodiment, DCI 806 is received from the BS on CC0, wherein the DCI 806 provides cross-carrier scheduling for DL ​​data transmission 804.

[0100] The UE may apply the application delay to the parameter design of the target BWP of the scheduled CC, where in this example, the value of the application delay may be the current minimum scheduling offset value (e.g., 3 time slots). Thus, based on the parameter design of the target BWP (e.g., BWP0 on CC1), the time slot n To time slot n+2 The time slot may be scheduled at a scheduling offset that is greater than or equal to the current minimum scheduling offset, and a subsequent time slot may be scheduled at a scheduling offset that is greater than or equal to the updated value of the minimum scheduling offset.

[0101] In other aspects, the value of the applied delay can be based on the current minimum scheduling offset and the adjustment term. For example, the applied value can be the sum of the current minimum scheduling offset and the adjustment term, which in some aspects can be an updated value of the minimum scheduling offset. Figure 8 , the current minimum scheduling offset can be used for time slot n To time slot n＝3 , and the updated value of the minimum scheduling offset will be used during subsequent time slots.

[0102] For a time slot on CC1 that can be scheduled by applying the updated value of the minimum scheduling offset (eg, minimum k0=1), the UE may receive DCI 808 from the BS on CC0, where the DCI 808 is scheduled in the time slot n+5 A cross-carrier DL data transmission 810 on CC1 is scheduled at (e.g., DCI 808 indicates k0=1). According to the parameter design of CC1, the UE applies the updated minimum scheduling offset value to determine various actions for the data transmission 810 (e.g., ignoring the scheduled grant if the corresponding grant parameter (k0 or k2) is less than or equal to the updated minimum scheduling offset value).

[0103] In certain aspects, the application delay for self-carrier (i.e., intra-carrier) scheduling may be defined according to the parameter design of the active BWP. In other words, the time slot definition for the application delay may be defined according to the scheduling PDCCH. Since the transition application delay value may be according to the parameter design of the scheduled CC, the application delay may be converted into the parameter design of the scheduling CC according to equation (7).

[0104] Fig. 9A An example self-carrier scheduling of downlink communications in accordance with certain aspects of the present disclosure is illustrated, wherein an application delay is defined according to a parameter design of an active BWP. Assume that the BWP switching delay is configured as 1 slot at 15kHz SCS and 2 slots at 30kHz SCS, the minimum scheduling offset (X) associated with BWP0 (15kHz SCS) is set to 2 slots, the minimum scheduling offset (X) associated with BWP1 (30kHz SCS) is set to 0 slots, and BWP0 and BWP1 may each be configured with various values ​​of k0. As shown, the UE may receive DCI 902 from the BS via a control channel such as a PDCCH. The DCI 902 may be in slots n is received and indicates a scheduling offset (e.g., k0=2) which is received in time slot n+2 In some aspects, the application delay may be based on the current minimum scheduling offset of 2 time slots. Under the parameter design of the active BWP, the UE may allow the application delay of 2 time slots in accordance with the parameter design of the active BWP. n+2 The time expires at which point the updated value of the minimum scheduling offset may take effect.

[0105] In certain aspects, application delay for self-carrier (ie, intra-carrier) scheduling may be defined according to parameter design of a target BWP. Fig. 9B An example self-carrier scheduling of downlink communications according to certain aspects of the present disclosure is illustrated, where application delay is defined according to parameter design of a target BWP. Assume that the same assumptions apply to this example as described herein with reference to Fig. 9A As shown, the UE may receive DCI 906 from the BS via a control channel (such as PDCCH). DCI 906 indicates the time slot of BWP1. n+4 908 (e.g., k0=4). In addition, the DCI 906 indicates that the updated value of the minimum scheduling offset changes the value to zero. In some aspects, the application delay may be based on the current minimum scheduling offset of 2 slots. Under the parameter design of the target BWP, the UE may allow the expiration of the application delay of 2 slots that may be set according to the parameter design of the active BWP to be converted to the target BWP, which provides a 4-slot application delay according to equation (5) or (6). For example, the time slot of BWP1 n+4 The UE can be scheduled by applying the updated minimum scheduling offset. n+6 A DCI 910 is received at the time, wherein the DCI 910 schedules a DL data transmission 912 within a time slot, which satisfies the updated value of the minimum scheduling offset.

[0106] For cross-carrier scheduling with the same parameter design between the scheduling carrier and the scheduled carrier, the time slots for the scheduling carrier and the scheduled carrier are aligned. The parameter design of the scheduled carrier may change when its active BWP switches between two BWPs with different parameter designs. There may be no difference from self-carrier scheduling except for the DCI on the scheduling carrier.

[0107] For cross-carrier scheduling with different parameter designs between the scheduling carrier and the scheduled carrier, there is a problem of how to define the minimum scheduling offset for k0 and k2 and how to define the application delay for the minimum scheduling offset change. In some wireless communication networks (e.g., 5G NR), the current definition of k0 and k2 is that when k0=0 and k2=0, the time slot on the scheduled carrier starts aligned with the time slot of the scheduling carrier for determining the time slot of the scheduling offset. For the case where a carrier with a larger SCS (e.g., 120kHz SCS) schedules a carrier with a smaller SCS (e.g., 30kHz SCS), multiple time slots of the scheduling carrier overlap with one time slot of the scheduled carrier. For example, Fig. 10A A diagram illustrating multiple time slots of a scheduling carrier 1002 overlapping a single time slot of a scheduled carrier 1004. In this example, a DCI received in any of the time slots (slots 0-3) of the scheduling carrier 1002 with a scheduling offset of k0=0 may schedule transmission within a time slot of the scheduled carrier 1004.

[0108] For the case where a carrier with a smaller SCS schedules transmission on a carrier with a larger SCS, one time slot of the scheduling carrier overlaps with multiple time slots of the scheduled carrier. Fig. 10B A diagram illustrating a single time slot of the scheduling carrier 1006 overlapping with multiple time slots of the scheduled carrier 1008. In some cases where the k0 / k2 definition is aligned with the beginning of the time slot of the scheduled carrier, if the PDCCH is in the later part of the time slot (e.g., aligned with the time slot of the scheduled carrier 1008), n+1 If the scheduling offset is greater than zero (e.g., k0=3) to satisfy the minimum scheduling offset, since k0=0 is already in the time slot of the scheduling carrier 1008. n Therefore, in some cases, a single minimum k0 configured for a scheduled CC may not be efficient because the minimum scheduling offset is for earlier in the time slot of the scheduled CC (e.g., in the time slot of the scheduled carrier 1008). n The received PDCCH may be over-provisioned (e.g., too long, which increases latency). Fig. 10B, PDSCH / PUSCH may not be scheduled within 2 slots after the scheduled PDCCH. For this reason, k0 must be 3 slots or longer for the later PDCCH 1012. In other cases, k0 may be 2 or greater for the earlier PDCCH 1010. Therefore, in general, the single "minimum k0" that works across all PDCCH positions is 3 slots. However, this minimum scheduling offset may be over-provisioned for some situations, which results in increased power consumption and / or increased signaling to manage the minimum scheduling offset value.

[0109] Various aspects of the present disclosure relate to various techniques for determining a scheduling offset in situations where the SCS is different between a scheduling carrier and a scheduled carrier. Such techniques described herein may improve power consumption of a UE and / or reduce signaling overhead for managing a minimum scheduling offset value to accommodate different SCSs. In some aspects, a PDCCH may be received only in the first half of a time slot of a scheduling carrier (e.g., only within the first three symbols of the time slot of the scheduling carrier). In other aspects, the starting position from which the minimum scheduling offset runs may be relative to a time slot of a scheduled carrier that intersects with the last symbol of the PDCCH on the scheduling carrier. For example, referring to Fig. 10B , the minimum scheduling offset can be from the time slot of the scheduled carrier 1008 n+1 Start running because in the time slot n+1 PDCCH 1012 is received at.

[0110] As another example, if the end position of PDCCH 1010 is in the time slot of scheduled carrier 1008 n and the minimum DL scheduling offset is 2 slots (per PDSCH SCS), then the earliest schedulable PDSCH can start at slot n+2 Therefore, the minimum scheduling offset may be at least 1 time slot.

[0111] In still other aspects, the minimum scheduling offset can be defined in terms of symbols of the scheduled carrier from the last symbol of the scheduled PDCCH.For example, the minimum scheduling offset and scheduling offset k0 / k2 can be given as the number of symbols from the last symbol of the PDCCH 1012.

[0112] The UE may take various actions if the scheduling offset is less than or equal to the minimum scheduling offset value. In certain aspects, if the k0 (or k2) indicated in the TDRA field in DCI format 1_0 (or 0_0) is less than or equal to the current minimum scheduling offset value currently in use, the UE may implicitly switch to a default value of the minimum scheduling offset (e.g., corresponding to '0' as a 1-bit indication value).

[0113] In certain aspects, a base station may implement various techniques for error handling if the base station detects that the UE has not applied the updated minimum scheduling offset according to the application delay as described herein. For example, the base station may retransmit the updated value of the minimum scheduling offset if the base station determines that the UE has not properly implemented the updated value.

[0114] According to certain aspects, there may be an upper limit on the minimum scheduling offset value. For example, the minimum k0 / k2 may provide sufficient delay for modem warm-up (e.g., for cross-carrier wake-up), and 3 milliseconds may be sufficient, which may be approximately 24 time slots at 120kHz SCS. That is, the upper limit on the minimum scheduling offset value may be 24 time slots. In other aspects, the minimum scheduling offset value may be greater than 1 time slot, without an upper limit.

[0115] Fig.11 1 is a flow diagram illustrating example operations 1100 for wireless communication in accordance with certain aspects of the present disclosure. Operations 1100 may be performed, for example, by a UE (e.g., UE 120a in wireless communication network 100). Operations 1100 may be implemented as a processor on one or more processors (e.g., Figure 2 In addition, signal transmission and reception by the UE in operation 1100 may be performed by one or more antennas (e.g., Figure 2 In some aspects, the transmission and / or reception of signals by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 280).

[0116] Operations 1100 may begin at 1102, where a UE may receive a signal from a base station (eg, BS 110a) indicating a plurality of minimum scheduling offset values ​​(eg, as referred to herein). Figure 7 At 1104, the UE may receive a signal (e.g., control signaling, including RRC, DCI, and / or MAC-CE signaling) from the base station indicating one of the minimum scheduling offset values ​​as an updated value to be used for communication with the base station and indicating a scheduling type (e.g., cross-carrier scheduling or self-carrier scheduling). At 1106, the UE may determine a delay based on the scheduling type (e.g., an application delay determined according to equation (5), (6), or (7)). At 1108, the UE may communicate with the base station using the updated value based on the determined time delay after receiving the signal.

[0117] At 1108, communicating with the base station using the updated value may include the UE communicating with the base station based on the updated value, for example, determining whether the scheduling offset (k0 or k2) satisfies the updated value according to equation (2). As used herein, communicating with a base station may include, for example, the UE receiving a DL data transmission from the base station. In other cases, the UE may transmit an UL data transmission to the base station. In various aspects, the updated value may be used to communicate with the base station after the signal is received and the delay (e.g., the application delay) expires, as described herein. As an example, the time domain resources may include a time domain resource offset from the last time domain resource of the signal by the delay (e.g., a time slot designed according to parameters of a PDCCH or PDSCH / PUSCH), and the delay may be determined as described herein.

[0118] In certain aspects, an application delay for cross-carrier scheduling may be defined according to a parameter design of an active BWP. As an example, referring to operation 1100, the scheduling type indicated in the signal may be cross-carrier scheduling, such that the signal is received via a first BWP (e.g., a DL BWP on a PDCCH) within a first carrier (e.g., a component carrier), and the signal further indicates a scheduling offset to be used to communicate with the base station via a second BWP (e.g., a DL or ULBWP on a PDSCH or PUSCH) within a second carrier different from the first carrier. At 1106, the delay (e.g., application delay) may be determined in terms of a time domain unit (e.g., a symbol, a slot, a frame, etc.) associated with the first BWP, for example, according to a parameter design of an active BWP.

[0119] Since the transition value of the application delay can be designed according to the parameters of the target BWP (e.g., the second BWP), the UE may convert the value (e.g., the transition value of the application delay) into a time domain unit associated with the first BWP. For example, the conversion may include converting X according to equation (7). In certain aspects, the value may be based on at least one of the minimum scheduling offset values, such as the minimum scheduling offset value used for communicating with the base station before the updated value. In various aspects, the value may be based on a default value of the minimum scheduling offset for communicating with the base station. For example, since X=max(Y,Z), Y may be a default value of the minimum scheduling offset, such as a fixed value or a minimum value for an active DL (or UL) BWP in a TDRA table. In various aspects, the value may be determined according to various methods for determining X as described herein with reference to equations (5) or (6). For example, if the scheduled transmission is for PDSCH (e.g., DCI format 1_1 (DL scheduling DCI) is received on PDCCH), then Y in reference to equations (5) and (6) can be the minimum value of the minimum scheduling offset value from k0, and if the scheduled transmission is for PUSCH (e.g., DCI format 0_1 ​​(UL scheduling DCI) is received on PDCCH), then Y in reference to equations (5) and (6) can be the minimum value of the minimum scheduling offset value from k2.

[0120] In some aspects, the application delay for cross-carrier scheduling can be defined according to the parameter design of the target BWP. As an example, referring to operation 1100, the scheduling type indicated in the signal (e.g., Figure 8 The signal may be cross-carrier scheduled such that the signal is received via a first BWP within a first carrier, and the signal further indicates a scheduling offset to be used to communicate with the base station via a second BWP within a second carrier different from the first carrier. In some cases, the UE may communicate with the base station based on the scheduling offset. At 1106, the delay (e.g., application delay) may be determined based on a value in time domain units associated with the second BWP (e.g., a transition value of the application delay), for example, according to a parameter design of a target BWP.

[0121] Since the value of the application delay may already be in time domain units of the second BWP, the value is not converted according to equation (7). In other words, the UE may directly apply the value of the application delay in time domain units of the target BWP without any conversion step. In some aspects, the value may be based on at least one of the minimum scheduling offset values, such as the minimum scheduling offset value used to communicate with the base station before the updated value. For example, the value may be determined according to various methods for determining X as described herein with reference to equations (5) or (6). In various aspects, the value may be based on a default value of the minimum scheduling offset for communicating with the base station. In various aspects, the value may be based on at least one of an adjustment item or at least one minimum scheduling offset value. For example, the value may be the sum of the adjustment item and at least one minimum scheduling offset value. In some aspects, the adjustment item may be the updated value indicated in the signal.

[0122] In certain aspects, an application delay for self-carrier (i.e., intra-carrier) scheduling may be defined according to a parameter design of an active BWP. For example, with reference to operation 1100, the scheduling type indicated in the signal may be self-carrier scheduling so that the signal is received via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used to communicate with a base station via a second BWP within the same carrier. In some cases, the UE may communicate with the base station based on the scheduling offset. At 1106, the delay (e.g., application delay) may be determined in time domain units associated with the first BWP, for example, according to a parameter design of an active BWP.

[0123] Since the transition value of the application delay can be designed according to the parameters of the target BWP (e.g., the second BWP), the UE can convert the value (e.g., the transition value of the application delay) into a time domain unit associated with the first BWP based on the parameter designs of the first BWP and the second BWP. For example, the application delay can be converted into a parameter design of the scheduling CC according to equation (7). In certain aspects, the value can be based on at least one of the minimum scheduling offset values, such as the minimum scheduling offset value used for communicating with the base station before the updated value. For example, the value can be determined according to various methods for determining X as described herein with reference to equations (5) or (6). In various aspects, the value can be based on a default value of the minimum scheduling offset used for communicating with the base station.

[0124] In certain aspects, the application delay for self-carrier scheduling may be defined according to the parameter design of the target BWP. For example, with reference to operation 1100, the scheduling type indicated in the signal may be self-carrier scheduling so that the signal is received via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used to communicate with the base station via a second BWP within the same carrier. In some cases, the UE may communicate with the base station based on the scheduling offset. At 1106, the delay (e.g., the application delay) may be determined based on a value in time domain units associated with the second BWP (e.g., a transition value of the application delay).

[0125] Since the value of the application delay may already be in time domain units of the second BWP, the value is not converted according to equation (7). In other words, the UE may directly apply the value of the application delay in time domain units of the target BWP without any conversion step. In some aspects, the value may be based on at least one of the minimum scheduling offset values, such as the minimum scheduling offset value used to communicate with the base station before the updated value. For example, the value may be determined according to various methods for determining X as described herein with reference to equations (5) or (6). In various aspects, the value may be based on a default value of the minimum scheduling offset for communicating with the base station. In various aspects, the value may be based on at least one of an adjustment item or at least one minimum scheduling offset value. For example, the value may be the sum of the adjustment item and at least one minimum scheduling offset value. In some aspects, the adjustment item may be the updated value indicated in the signal.

[0126] Aspects of the present disclosure relate to various techniques for determining a scheduling offset in a scenario where the SCS differs between a scheduling carrier and a scheduled carrier, as described herein with reference to Fig. 10A and 10B Described. In some aspects, the PDCCH may be received only in the first half of the time slot of the scheduled carrier (e.g., only in the first three symbols of the time slot of the scheduled carrier). As an example, referring to operation 1100, at 1104, the UE may receive the signal via the first BWP in the first half of the time slot of the first BWP, wherein the signal further indicates a scheduling offset to be used for communicating with the base station via the second BWP. In various aspects, the UE may receive the signal via three symbols (e.g., the first three symbols) in the time slot of the first BWP. In some cases, the first BWP may have a parameter design different from the parameter design of the second BWP. In some cases, the UE may communicate with the base station based on the scheduling offset.

[0127] In various aspects, the starting position of the minimum scheduling offset may be a time slot of the scheduled carrier that intersects with the last symbol of the PDCCH on the scheduling carrier, such as Fig. 10BAs an example, referring to operation 1100, at 1104, the UE may receive the signal via a first BWP having a first parameter design, wherein the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP having a second parameter design different from the first parameter design. The UE may communicate with the base station based on a scheduling offset of a time domain resource (e.g., a time slot, a mini-time slot, a symbol, etc.) relative to the second BWP, wherein the time domain resource intersects with a last time domain resource of the signal (e.g., a last symbol of a PDCCH).

[0128] According to certain aspects, the minimum scheduling offset may be defined in terms of symbols of the scheduled carrier from the last symbol of the scheduled PDCCH. As an example, referring to operation 1100, at 1104, the UE may receive the signal via a first BWP having a first parameter design, wherein the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP having a second parameter design different from the first parameter design. The UE may communicate with the base station based on the scheduling offset and at least one minimum scheduling offset value (e.g., the minimum scheduling offset value currently being used before the update), wherein the scheduling offset and at least one minimum scheduling offset are in terms of symbols from the last time domain resource of the signal (e.g., the last symbol of the PDCCH).

[0129] The UE may take various actions when the scheduling offset is less than or equal to the minimum scheduling offset value. As an example, referring to operation 1100, the signal may further indicate a scheduling offset to be used for communicating with the base station. The UE may identify a minimum scheduling offset value for communicating with the base station among multiple minimum scheduling offset values. The UE may determine the value of the scheduling offset based at least in part on the minimum scheduling offset value for communicating with the base station (e.g., the value currently in use before the update). The UE may communicate with the base station based on a default value (e.g., a value corresponding to '0' (zero) as a 1-bit indication) when the value of the scheduling offset is less than or equal to at least one minimum scheduling offset value (e.g., the value currently in use before the update).

[0130] Fig.12 1 is a flow diagram illustrating example operations 1200 for wireless communication in accordance with certain aspects of the present disclosure. Operations 1200 may be performed, for example, by a BS (e.g., BS 110a in wireless communication network 100). Operations 1200 may be complementary to operations 1100 performed by a BS. Operations 1200 may be implemented as a processor on one or more processors (e.g., Figure 2 In addition, signal transmission and reception by the BS in operation 1200 may be performed by one or more antennas (e.g., Figure 2In some aspects, signal transmission and / or reception by the BS may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 240).

[0131] Operation 1200 may begin at 1202, where a base station (e.g., BS 110a) may select one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a UE (e.g., UE 120a). At 1204, the base station may transmit a signal (e.g., control signaling, including RRC, DCI, and / or MAC-CE signaling) indicating the updated value and a scheduling type (e.g., cross-carrier scheduling or self-carrier scheduling) to the UE. At 1206, the base station may determine a delay based on the scheduling type (e.g., an application delay determined according to equation (5), (6), or (7)). At 1208, the base station may communicate with the UE using the updated value based on the determined delay after transmitting the signal.

[0132] At 1208, communicating with the UE using the updated value may include the UE communicating with the base station based on the updated value, for example, determining whether the scheduling offset (k0 or k2) satisfies the updated value according to equation (2). As used herein, communicating with the UE may include, for example, the base station transmitting a DL data transmission to the UE. In other cases, the base station may receive an UL data transmission from the UE. In various aspects, the updated value may be used to communicate with the UE after the signal is received and a delay (e.g., an application delay) expires, as described herein. As an example, the time domain resources may include time domain resources offset from the last time domain resource of the signal by the delay (e.g., a time slot designed according to parameters of a PDCCH or PDSCH / PUSCH), and the delay may be determined as described herein. In other aspects, operation 1200 may include the base station transmitting to the UE an indication of the multiple minimum scheduling offset values ​​(e.g., as referred to herein). Figure 7 One or more configurations (e.g., RRC configurations) described herein.

[0133] In certain aspects, an application delay for cross-carrier scheduling may be defined according to a parameter design of an active BWP. As an example, with reference to operation 1200, the scheduling type may be cross-carrier scheduling such that the signal is transmitted via a first BWP (e.g., a DL BWP on a PDCCH) within a first carrier (e.g., a component carrier), and the signal further indicates a scheduling offset to be used to communicate with the UE via a second BWP (e.g., a DL or UL BWP on a PDSCH or PUSCH) within a second carrier different from the first carrier. In some cases, the base station may communicate with the UE based on the scheduling offset. At 1206, the delay may be determined in time domain units associated with the first BWP, for example, according to a parameter design of an active BWP.

[0134] Since the transition value of the application delay can be designed according to the parameters of the target BWP (e.g., the second BWP), the base station can convert the value (e.g., the transition value of the application delay) into a time domain unit associated with the first BWP. For example, the conversion may include converting X according to Equation (7). In some aspects, the value may be based on at least one minimum scheduling offset value (e.g., the value currently in use before the update). In various aspects, the value may be based on a default value of the minimum scheduling offset for communicating with the UE. In some aspects, the value may be based on the minimum scheduling offset value used for communicating with the base station before the updated value. In various aspects, the value may be determined according to various methods for determining X as described herein with reference to Equation (5) or (6). For example, if the scheduled transmission is for the PDSCH (e.g., DCI format 1_1 (DL scheduling DCI) is received on the PDCCH), then Y with reference to Equations (5) and (6) may be the minimum value of the minimum scheduling offset values from k0, and if the scheduled transmission is for the PUSCH (e.g., DCI format 0_1 (UL scheduling DCI) is received on the PDCCH), then Y with reference to Equations (5) and (6) may be the minimum value of the minimum scheduling offset values from k2.

[0135] In some aspects, the application delay for cross-carrier scheduling may be defined according to the parameter design of the target BWP. As an example, referring to operation 1200, the scheduling type may be cross-carrier scheduling such that the signal is transmitted via the first BWP within the first carrier, and the signal further indicates a scheduling offset to be used for communicating with the UE via the second BWP within a second carrier different from the first carrier. In some cases, the base station may communicate with the UE based on the scheduling offset. At 1206, the delay may be determined based on a value in the time domain unit associated with the second BWP (e.g., the transition value of the application delay), e.g., according to the parameter design of the target BWP.

[0136] Since the value of the application delay may already be in the time domain unit of the second BWP, the value is not converted according to Equation (7). In other words, the base station can directly apply the value of the application delay in the time domain unit of the target BWP without any conversion steps. In some aspects, the value may be based on at least one of the minimum scheduling offset values, e.g., the minimum scheduling offset value used for communicating with the base station before the updated value. For example, the value may be determined according to various methods for determining X as described herein with reference to Equation (5) or (6). In various aspects, the value may be based on a default value of the minimum scheduling offset for communicating with the UE. In various aspects, the value may be based on an adjustment term or at least one of the minimum scheduling offset values. For example, the value may be the sum of the adjustment term and at least one minimum scheduling offset value. In some aspects, the adjustment term may be the updated value indicated in the signal.

[0137] In certain aspects, the application delay for self-carrier (i.e., intra-carrier) scheduling may be defined according to the parameter design of the active BWP. For example, with reference to operation 1200, the scheduling type may be self-carrier scheduling so that the signal may be transmitted via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used to communicate with the UE via a second BWP within the same carrier. In some cases, the base station may communicate with the UE based on the scheduling offset. At 1206, the delay may be determined in time domain units associated with the first BWP, for example, according to the parameter design of the active BWP.

[0138] Since the transition value of the application delay can be designed according to the parameters of the target BWP (e.g., the second BWP), the base station can convert the value (e.g., the transition value of the application delay) into a time domain unit associated with the first BWP based on the parameter designs of the first BWP and the second BWP. For example, the application delay can be converted into a parameter design of the scheduling CC according to equation (7). In certain aspects, the value can be based on at least one of the minimum scheduling offset values, such as the minimum scheduling offset value used for communicating with the base station before the updated value. For example, the value can be determined according to various methods for determining X as described herein with reference to equations (5) or (6). In various aspects, the value can be based on a default value of the minimum scheduling offset for communicating with the UE.

[0139] In certain aspects, the application delay for self-carrier scheduling may be defined according to the parameter design of the target BWP. For example, with reference to operation 1100, the scheduling type may be self-carrier scheduling so that the signal is transmitted via a first BWP within a carrier and further indicates a scheduling offset to be used to communicate with the UE via a second BWP within the same carrier. In some cases, the base station may communicate with the UE based on the scheduling offset. At 1206, the delay may be determined based on a value in time domain units associated with the second BWP, for example, according to the parameter design of the target BWP.

[0140] Since the value of the application delay may already be in time domain units of the second BWP, the value is not converted according to equation (7). In other words, the base station may directly apply the value of the application delay in time domain units of the target BWP without any conversion step. In some aspects, the value may be based on at least one of the minimum scheduling offset values, such as the minimum scheduling offset value used to communicate with the base station before the updated value. For example, the value may be determined according to various methods for determining X as described herein with reference to equations (5) or (6). In various aspects, the value may be based on a default value of the minimum scheduling offset for communicating with the UE. In various aspects, the value may be based on at least one of an adjustment item or at least one minimum scheduling offset value. For example, the value may be the sum of the adjustment item and at least one minimum scheduling offset value. In some aspects, the adjustment item may be the updated value indicated in the signal.

[0141] Aspects of the present disclosure relate to various techniques for determining a scheduling offset in a scenario where the SCS differs between a scheduling carrier and a scheduled carrier, as described herein with reference to Fig. 10A and 10B Described. In some aspects, the PDCCH may be transmitted only in the first half of the time slot of the scheduled carrier (e.g., only in the first three symbols of the time slot of the scheduled carrier). As an example, referring to operation 1200, the base station may transmit the signal via the first BWP in the first half of the time slot of the first BWP, wherein the signal further indicates a scheduling offset for communicating with the UE via the second BWP. In various aspects, the base station may transmit the signal via three symbols (e.g., the first three symbols) in the time slot of the first BWP. In some cases, the first BWP may have a parameter design different from the parameter design of the second BWP. In some cases, the base station may communicate with the UE based on the scheduling offset.

[0142] In various aspects, the starting position of the minimum scheduling offset may be a time slot of the scheduled carrier that intersects with the last symbol of the PDCCH on the scheduling carrier, such as Fig. 10B As an example, referring to operation 1200, at 1204, the base station may transmit the signal via a first BWP having a first parameter design, wherein the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP having a second parameter design different from the first parameter design. The base station may communicate with the UE based on a scheduling offset of a time domain resource (e.g., a time slot, a mini-time slot, a symbol, etc.) relative to the second BWP, wherein the time domain resource intersects with a last time domain resource of the signal (e.g., a last symbol of a PDCCH).

[0143] According to certain aspects, the minimum scheduling offset may be defined in terms of symbols of the scheduled carrier from the last symbol of the scheduled PDCCH. As an example, referring to operation 1200, at 1204, the base station may transmit the signal via a first BWP having a first parameter design, wherein the signal further indicates a scheduling offset to be used for communicating with the UE via a second BWP having a second parameter design different from the first parameter design. The base station may communicate with the UE based on the scheduling offset and at least one minimum scheduling offset value (e.g., the minimum scheduling offset value currently being used before the update), wherein the scheduling offset and at least one minimum scheduling offset are in terms of symbols from the last time domain resource of the signal (e.g., the last symbol of the PDCCH).

[0144] The base station may take various actions if it determines that the scheduling offset is less than or equal to the minimum scheduling offset value. As an example, referring to operation 1200, the signal may further indicate a scheduling offset to be used for communicating with the UE. The base station may determine the value of the scheduling offset based at least in part on the minimum scheduling offset value used to communicate with the UE (e.g., the value currently in use before the update). The base station may communicate with the UE based on a default value (e.g., a value corresponding to '0' (zero) as a 1-bit indication) if the value of the scheduling offset is less than or equal to at least one minimum scheduling offset value (e.g., the value currently in use before the update).

[0145] In certain aspects, a base station may implement various techniques for error handling in the event that the base station detects that the UE has not applied the updated minimum scheduling offset according to the application delay as described herein. As an example, with reference to operation 1200, the base station may determine that the UE failed to decode a signal indicating an updated value, for example, due to hybrid automatic repeat request (HARQ) operation. Based on the determination, the base station may retransmit the signal indicating the updated value to the UE.

[0146] Additional example scheduling application delay

[0147] In certain aspects, for a DL (or UL) scheduling DCI indicating an update to the minimum scheduling offset(s) for an active DL BWP and / or an active UL BWP, the earliest time slot that may be scheduled based on the updated minimum scheduling offset(s) is given by:

[0148] n'+X(8)

[0149] in:

[0150] X = max(Y, Z) + A (9)

[0151] Y can be at least one of the configured minimum scheduling offset values, such as the current minimum k0 (or k2). A can be an adjustment term, such as an updated minimum scheduling offset value. Z can be a value that ensures that the total application delay is not too small. For example, the value of Z can be (1, 1, [2], [2]) for SCSs of (15, 30, 60, 120) KHz, respectively. In some aspects, X=Y+A+Z or X=max(Y,Z)+max(A,Z) can also provide suitable values ​​for X. In equation (8), n' can be the time slot index in the parameter design of the scheduled transmission (e.g., PUSCH or PDSCH), and the relationship between n' and the time slot index in the scheduling PDCCH parameter design can be given by the following equation:

[0152]

[0153] Fig.13AAn example scheduling of downlink communications according to certain aspects of the present disclosure is illustrated, wherein the minimum scheduling offset changes from a larger value to a smaller value, and the application delay is determined according to equation (8). As shown, the UE can be in the time slot n The DCI 1302 is received from the BS via a control channel (such as PDCCH) in the time slot. The DCI 1302 indicates an updated value of the minimum scheduling offset (e.g., from the current value of minimum k0=2 to minimum k0=1). The DCI 1302 may also be in the time slot n+2 DL data transmission on BWP0 is scheduled at 1304. In certain aspects, referring to equations (8) and (9), Y=2 and A=1, so X=sum(2,1)=3. As a result, in this example, the earliest time slot that can be scheduled when k0=1 is time slot n+3. The UE can n+2 The DCI 1306 is received from the BS via a control channel (such as PDCCH) in the time slot, and the DCI 1306 with a scheduling offset value of 1 can be n+3 DL data transmission on BWP0 is scheduled 1308.

[0154] Fig. 13B An example scheduling of downlink communications according to certain aspects of the present disclosure is illustrated, wherein the minimum scheduling offset changes from a smaller value to a larger value, and the application delay is determined according to equation (8). As shown, the UE can be in the time slot n The DCI 1310 is received from the BS via a control channel (such as PDCCH) in the time slot. The DCI 1310 indicates an updated value of the minimum scheduling offset (eg, from the current value of minimum k0=0 to minimum k0=1). The DCI 1310 may also be in the time slot n DL data transmission on BWP0 is scheduled at 1312. In certain aspects, referring to equations (8) and (9), since the current minimum scheduling offset is zero, assuming Z = 1 results in X = max(0,1) + 1 = 2. In this example, the earliest time slot that can be scheduled based on the minimum k0 = 1 is time slot n + 2 (i.e., the scheduling PDCCH will have to be transmitted in time slot n + 1). The UE can n+1 The DCI 1314 is received from the BS via the control channel in the time slot, and the DCI 1314 with the scheduling offset value 1 can be n+2 DL data transmission on BWP0 is scheduled 1316.

[0155] For BWP switching, it may be very useful to indicate the minimum scheduling offset to be used for the target BWP, and this indication may be in the same scheduling DCI that triggers the BWP switching. The presence of the 1-bit field may be based on the RRC configuration of the current BWP, it may be expected that this 1-bit field is present in the DCI for most scenarios, and it may be wasteful not to allow the use of the BWP switching triggering DCI. In various aspects, the DCI that triggers the BWP switching may also indicate the minimum scheduling offset to be used for the target BWP, if this 1-bit field is present in the DCI.

[0156] Continuous Update of Minimum Schedule Offset

[0157] With respect to application delay, continuous variation of the minimum scheduling offset may be supported. In certain aspects, such as minimum time scales (e.g., URLLC communications), the minimum scheduling offset may be updated to accommodate traffic changes such as high bandwidth bursts. In other cases, if the update of the minimum scheduling offset is enabled and a non-zero minimum scheduling offset is used, this means that the additional latency introduced is at least temporarily tolerable. In such cases, continuous updating of the minimum scheduling offset may be disabled or not desired.

[0158] In certain aspects, the base station may refrain from signaling a continuous change to the minimum scheduling offset before the time at which the previous change is expected to be applied and / or confirmed by the UE. For example, if the previous indication is waiting to be applied, the UE may not expect another indication of the minimum scheduling offset change in the scheduling DCI. In another example, the UE may not expect to receive another indication of the minimum scheduling offset change in the scheduling DCI for the same active BWP before confirming the receipt of the previous indication of the minimum scheduling offset change. If the previous change indication is carried in the DL scheduling DCI, the time of confirmation is when the HARQ-ACK for the scheduled PDSCH is sent. If the previous change indication is carried in the UL scheduling DCI, the time of confirmation is when the scheduled PUSCH is sent. Waiting until the time of the HARQ-ACK or PUSCH transmission corresponding to the DCI carrying the previous change indication is robust because this can give the base station and the UE a chance to synchronize on the minimum scheduling offset change before moving to another change.

[0159] Fig.14 The following describes operations that may include being configured to perform the techniques disclosed herein (such as Fig.111400 (e.g., UE 120a) includes various components (e.g., corresponding to means plus function components) of the operations illustrated in FIG. 1400 . The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or a receiver). The transceiver 1408 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1400 via an antenna 1410. The processing system 1402 may be configured to perform processing functions for the communication device 1400, including processing signals received and / or to be transmitted by the communication device 1400.

[0160] The processing system 1402 includes a processor 1404 coupled to a computer readable medium / memory 1412 via a bus 1406. In some aspects, the computer readable medium / memory 1412 is configured to store programs that, when executed by the processor 1404, cause the processor 1404 to execute Fig.11 , or instructions (e.g., computer executable code) for performing the operations explained in or other operations for managing the various techniques discussed herein for managing scheduled transmissions. In some aspects, the computer-readable medium / memory 1412 stores code 1414 for receiving, code 1416 for identifying, code 1418 for determining (including code for converting), and / or code 1420 for using (including code for communicating, code for receiving, and / or code for transmitting). In some aspects, the processor 1404 has a circuit system configured to implement the code stored in the computer-readable medium / memory 1412. The processor 1404 includes circuit systems 1422 for receiving, circuit systems 1424 for identifying, circuit systems 1426 for determining (including circuit systems for converting), and / or circuit systems 1428 for using (including circuit systems for communicating, circuit systems for receiving, and / or circuit systems for transmitting).

[0161] Fig.15 The description may include instructions configured to perform operations for the techniques disclosed herein (such as, Fig.12 1500 (e.g., BS 110a) includes various components (e.g., corresponding to means-plus-function components) of the operations illustrated in 1500. The communication device 1500 includes a processing system 1502 coupled to a transceiver 1508 (e.g., a transmitter and / or a receiver). The transceiver 1508 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1500 via an antenna 1510. The processing system 1502 may be configured to perform processing functions for the communication device 1500, including processing signals received and / or to be transmitted by the communication device 1500.

[0162] The processing system 1502 includes a processor 1504 coupled to a computer readable medium / memory 1512 via a bus 1506. In some aspects, the computer readable medium / memory 1512 is configured to store programs that, when executed by the processor 1504, cause the processor 1504 to execute Fig.12 1504 includes circuitry 1522 for transmitting, circuitry 1524 for selecting, circuitry 1526 for determining (including circuitry for converting), and / or circuitry 1528 for using (including circuitry for communicating, circuitry for receiving, and / or circuitry for transmitting). In some aspects, processor 1504 has circuitry configured to implement the code stored in computer-readable medium / memory 1512. Processor 1504 includes circuitry 1522 for transmitting, circuitry 1524 for selecting, circuitry 1526 for determining (including circuitry for converting), and / or circuitry 1528 for using (including circuitry for communicating, circuitry for receiving, and / or circuitry for transmitting).

[0163] The techniques described herein may be used for various wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks 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), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and 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). NR is an emerging wireless communication technology under development.

[0164] The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations.

[0165] In 3GPP, the term "cell" may refer to the coverage area of ​​a B node (NB) and / or a NB subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and BS, next-generation B node (gNB or g B node), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. The BS 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., a radius of several thousand meters) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS.

[0166] 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, appliance, 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.), transportation 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 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 BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0167] 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 often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for 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 subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.8 MHz (e.g., 6 RBs), 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. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0168] NR can utilize OFDM with CP on the uplink and downlink and includes support for half-duplex operation using TDD. In NR, a subframe is still 1ms, but the basic TTI is called a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16...time slots), depending on the subcarrier spacing. NR RB is 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and time slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. In some examples, the MIMO configuration in the DL can support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. In some examples, multi-layer transmission of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.

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

[0170] In some examples, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world 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 that is communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

[0171] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other without departing from the scope of the claims. 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 changed without departing from the scope of the claims.

[0172] 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. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

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

[0174] 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 easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to those of ordinary skill in the art and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Any element of the claim should not be interpreted under the provisions of 35 U.S.C. § 112 (f), unless the element is explicitly stated using the phrase "device for..." or in the case of a method claim, the element is stated using the phrase "step for...".

[0175] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices 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 there are operations illustrated in the accompanying drawings, these operations may have corresponding paired device-plus-function components with similar numbers.

[0176] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable 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 in the alternative, 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.

[0177] 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. Depending on the specific application of the processing system and the overall design constraints, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In user equipment 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, and the like, which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0178] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both 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 general 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 and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include 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 implemented in a computer program product.

[0179] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, distributed between different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a 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 describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0180] Likewise, 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 technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is 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 Disks, where disks often reproduce data magnetically, and discs reproduce data optically with 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 transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0181] Thus, certain 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 stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein, such as for performing the operations described herein and in Fig.11 and / or Fig.12 Instructions for the operations explained in .

[0182] In addition, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means 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 once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0183] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in 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, comprising: receiving one or more configurations indicating a plurality of minimum scheduling offset values; receiving a signal indicating one of the minimum scheduling offset values as an updated value to be used for communication with a base station and indicating a scheduling type, wherein the scheduling type is cross-carrier scheduling, such that the signal is received via a first bandwidth part (BWP) within a first carrier, and the signal further indicates a scheduling offset to be used for communication with the base station via a second BWP within a second carrier different from the first carrier; determining a delay based on the scheduling type; and after receiving the signal, communicating with the base station using the updated value based on the determined delay, wherein the updated value is used for communication with the base station after receiving the signal and after the delay expires.

2. The method according to claim 1, wherein: the delay is in a time domain unit associated with the first BWP; the method further comprises communicating with the base station based on the scheduling offset.

3. The method according to claim 2, wherein determining the delay further comprises: converting the delay into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

4. The method according to claim 3, wherein the delay is based on a default value of a minimum scheduling offset for communication with the base station.

5. The method according to claim 3, wherein the delay is based on at least one of the minimum scheduling offset values.

6. The method according to claim 1, wherein: the delay is in a time domain unit associated with the second BWP; the method further comprises communicating with the base station based on the scheduling offset.

7. The method according to claim 6, wherein the delay is based on a default value of a minimum scheduling offset for communication with the base station.

8. The method according to claim 6, wherein the delay is based on at least one of the minimum scheduling offset values.

9. A method for wireless communication by a user equipment, comprising: receiving one or more configurations indicating a plurality of minimum scheduling offset values; receiving a signal indicating one of the minimum scheduling offset values as an updated value to be used for communication with a base station and indicating a scheduling type, wherein the scheduling type is self-carrier scheduling, such that the signal is received via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used for communication with the base station via a second BWP within the same carrier; determining a delay based on the scheduling type; and after receiving the signal, communicating with the base station using the updated value based on the determined delay, the updated value being used for communication with the base station after receiving the signal and after the delay expires.

10. The method according to claim 9, wherein the delay is in a time domain unit associated with the first BWP, the method further comprises communicating with the base station based on the scheduling offset.

11. The method according to claim 10, wherein determining the delay further comprises: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

12. The method of claim 11, wherein the delay is based on a default value of a minimum scheduling offset for communicating with the base station.

13. The method of claim 9, in: The delay is in time domain units associated with the second BWP; The method further includes communicating with the base station based on the scheduling offset.

14. A method for wireless communication by a base station, include: selecting one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a user equipment UE; transmitting a signal indicating the updated value and a scheduling type, wherein the scheduling type is cross-carrier scheduling such that the signal is transmitted via a first bandwidth part (BWP) within a first carrier, and the signal further indicates a scheduling offset to be used for communicating with the UE via a second BWP within a second carrier different from the first carrier; determining a delay based on the scheduling type; and After transmitting the signal and expiration of the delay, communicating with the UE using the updated value.

15. The method of claim 14, in: The delay is in time domain units associated with the first BWP; The method further includes communicating with the UE based on the scheduling offset.

16. The method of claim 15, wherein determining the delay further comprises: include: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

17. The method of claim 16, wherein the delay is based on a default value of a minimum scheduling offset for communicating with the UE.

18. The method of claim 16, wherein the delay is based on at least one of the minimum scheduling offset values.

19. The method of claim 14, in: The delay is in time domain units associated with the second BWP; The method further includes communicating with the UE based on the scheduling offset.

20. The method of claim 19, wherein the delay is based on a default value of a minimum scheduling offset for communicating with the UE.

21. The method of claim 19, wherein the delay is based on at least one of the minimum scheduling offset values.

22. A method for wireless communication by a base station, include: selecting one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a user equipment UE; transmitting a signal indicating the updated value and a scheduling type, wherein the scheduling type is self-carrier scheduling such that the signal is transmitted via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used for communicating with the UE via a second BWP within the same carrier; determining a delay based on the schedule type; as well as The updated value is used to communicate with the UE after the signal is transmitted and the delay expires.

23. The method of claim 22, in: The delay is in time domain units associated with the first BWP, The method further includes communicating with the UE based on the scheduling offset.

24. The method of claim 23, wherein determining the delay further comprises: include: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

25. The method of claim 24, wherein the delay is based on a default value of a minimum scheduling offset for communicating with the UE.

26. The method of claim 22, in: The delay is in time domain units associated with the second BWP.

27. An apparatus for wireless communication, include: A transceiver configured to: receiving one or more configurations indicating a plurality of minimum scheduling offset values, and receiving a signal indicating one of the minimum scheduling offset values ​​as an updated value to be used for communicating with a base station and indicating a scheduling type, wherein the scheduling type is cross-carrier scheduling such that the signal is received via a first bandwidth part (BWP) within a first carrier, and the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP within a second carrier different from the first carrier; Memory; as well as a processor coupled to the memory, and the processor and the memory configured to determine a delay based on the schedule type; Wherein the transceiver is further configured to communicate with the base station using the updated value after receiving the signal and expiration of the delay.

28. The device according to claim 27, in: The delay is in time domain units associated with the first BWP; and The transceiver is further configured to: Communicating with the base station based on the scheduling offset.

29. The apparatus of claim 28, wherein determining the delay further comprises: include: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

30. The apparatus of claim 29, wherein the delay is based on a default value for a minimum scheduling offset for communicating with the base station.

31. The apparatus of claim 29, wherein the delay is based on at least one of the minimum scheduling offset values.

32. The device of claim 27, in: The delay is in time domain units associated with the second BWP; The transceiver is further configured to communicate with the base station based on the scheduling offset.

33. The apparatus of claim 32, wherein the delay is based on a default value for a minimum scheduling offset for communicating with the base station.

34. The apparatus of claim 32, wherein the delay is based on at least one of the minimum scheduling offset values.

35. An apparatus for wireless communication, include: A transceiver configured to: receiving one or more configurations indicating a plurality of minimum scheduling offset values, and receiving a signal indicating one of the minimum scheduling offset values ​​as an updated value to be used for communicating with a base station and indicating a scheduling type, wherein the scheduling type is self-carrier scheduling, such that the signal is received via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP within the same carrier; and Memory; as well as a processor coupled to the memory, and the processor and the memory configured to determine a delay based on the schedule type; The transceiver is further configured to: The updated value is used to communicate with the base station after the signal is received and the delay expires.

36. The apparatus of claim 35, wherein the delay is in time domain units associated with the first BWP, and The transceiver is further configured to communicate with the base station based on the scheduling offset.

37. The apparatus of claim 36, wherein determining the delay further comprises: include: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

38. The apparatus of claim 37, wherein the delay is based on a default value for a minimum scheduling offset for communicating with the base station.

39. The device of claim 35, in: The delay is in time domain units associated with the second BWP; The transceiver is further configured to communicate with the base station based on the scheduling offset.

40. An apparatus for wireless communication, include: Memory; a processor coupled to the memory, and the processor and the memory configured to select one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a user equipment UE; as well as a transceiver configured to transmit a signal indicating the updated value and a scheduling type, wherein the scheduling type is cross-carrier scheduling, such that the signal is transmitted via a first bandwidth part (BWP) within a first carrier, and the signal further indicates a scheduling offset to be used for communicating with the UE via a second BWP within a second carrier different from the first carrier, wherein: The processor and the memory are further configured to determine a delay based on the schedule type; as well as After transmitting the signal and expiration of the delay, the transceiver is configured to communicate with the UE using the updated value.

41. The device of claim 40, in: The delay is in time domain units associated with the first BWP; The transceiver is further configured to: Communicating with the UE based on the scheduling offset.

42. The apparatus of claim 41, wherein determining the delay further comprises: include: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

43. The apparatus of claim 42, wherein the delay is based on a default value for a minimum scheduling offset for communicating with the UE.

44. The apparatus of claim 42, wherein the delay is based on at least one of the minimum scheduling offset values.

45. The device of claim 40, in: The delay is in time domain units associated with the second BWP; The transceiver is further configured to communicate with the UE based on the scheduling offset.

46. ​​The apparatus of claim 45, wherein the delay is based on a default value for a minimum scheduling offset for communicating with the UE.

47. The apparatus of claim 45, wherein the delay is based on at least one of the minimum scheduling offset values.

48. An apparatus for wireless communication, include: Memory; a processor coupled to the memory, and the processor and the memory configured to select one of a plurality of minimum scheduling offset values ​​as an updated value to be used for communicating with a user equipment UE; as well as a transceiver configured to transmit a signal indicating the updated value and a scheduling type, wherein the scheduling type is self-carrier scheduling, such that the signal is transmitted via a first BWP within a carrier, and the signal further indicates a scheduling offset to be used for communicating with the UE via a second BWP within the same carrier; The processor and the memory are further configured to determine a delay based on the schedule type; and The transceiver is further configured to: The updated value is used to communicate with the UE after the signal is transmitted and the delay expires.

49. The device of claim 48, in: The delay is in time domain units associated with the first BWP, The transceiver is further configured to communicate with the UE based on the scheduling offset.

50. The apparatus of claim 49, wherein determining the delay further comprises: include: The delay is converted into a time domain unit associated with the first BWP based on parameter designs of the first BWP and the second BWP.

51. The apparatus of claim 48, wherein the delay is based on a default value for a minimum scheduling offset for communicating with the UE.

52. The device of claim 48, in: The delay is in time domain units associated with the second BWP.

Images