Method and apparatus for scheduling application delays

Abstract

The invention discloses a method and apparatus for scheduling application delays. Certain aspects of the present disclosure provide techniques for managing scheduling of wireless communications. A method, which may be performed by a user equipment (UE), includes receiving, from a base station, one or more configurations indicating a plurality of minimum scheduling offset values; 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; 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.

Description

[0001] This application is a divisional application of a Chinese patent application with an application date of October 1, 2020, an application number of 202080067787.7 (PCT international application number PCT / US2020 / 053780), and an invention title of "Scheduling Application Latency".

[0002] Cross-reference to Related Applications

[0003] This application claims the priority of U.S. Application No. 17 / 039,610, filed on September 30, 2020, which claims the benefit and priority of 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 these applications is hereby incorporated by reference in its entirety. Technical Field

[0004] Aspects of the present disclosure relate to wireless communication, and more particularly to techniques for managing transmission scheduling. Background Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasting, 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, Advanced LTE (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 examples.

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

[0007] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that employ these technologies. SUMMARY OF THE INVENTION

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

[0009] Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes receiving, from a base station, one or more configurations indicating a plurality of minimum scheduling offset values, and 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. The method further includes determining a latency based on the scheduling type, and after receiving the signal, communicating with the base station using the updated value based on the determined latency.

[0010] 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 communication with a UE, and transmitting to the UE a signal indicating the updated value and a scheduling type. The method further includes determining a latency based on the scheduling type, and after transmitting the signal, communicating with the UE using the updated value based on the determined latency.

[0011] 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, from a base station, one or more configurations indicating a plurality of minimum scheduling offset values, and receive, 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. The processor is coupled to the memory, and the processor and the memory are configured to determine a latency based on the scheduling type. The transceiver is further configured to communicate with the base station using the updated value based on the determined latency.

[0012] 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 to the UE indicating the updated value and a scheduling type. The processor and the memory are further configured to determine a latency 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 latency.

[0013] 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 communicating with the base station and indicating a scheduling type; means for determining a latency based on the scheduling type; and means for, after receiving the signal, communicating with the base station using the updated value based on the determined latency.

[0014] 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 to the UE a signal indicating the updated value and a scheduling type; means for determining a latency based on the scheduling type; and means for, after transmitting the signal, communicating with the UE using the updated value based on the determined latency.

[0015] Certain aspects provide a computer-readable medium having instructions stored thereon for receiving from a base station one or more configurations indicating a plurality of minimum scheduling offset values; receiving from the base station a signal 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 latency based on the scheduling type; and, after receiving the signal, communicating with the base station using the updated value based on the determined latency.

[0016] 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 to the UE a signal indicating the updated value and a scheduling type; determining a latency based on the scheduling type; and, after transmitting the signal, communicating with the UE using the updated value based on the determined latency.

[0017] To achieve the foregoing and related purposes, one or more aspects include the features that are fully described below 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 only indicative of several ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] For a more particular description of the ways in which the above-recited features of the present disclosure can be used, reference may be made to the aspects, some of which are illustrated in the drawings. It should 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, as the description may admit of other equally effective aspects.

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

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

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

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

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

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

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

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

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

[0028] Figure 9AIllustrated is an example of self-carrier scheduling for downlink communication according to certain aspects of the present disclosure, where the application delay is defined according to the parameter design of the active BWP.

[0029] Figure 9B Illustrated is an example of self-carrier scheduling for downlink communication according to certain aspects of the present disclosure, where the application delay is defined according to the parameter design of the target BWP.

[0030] Figure 10A Illustrated is a diagram in which multiple time slots of a scheduled carrier overlap with a single time slot of a scheduled carrier according to certain aspects of the present disclosure.

[0031] Figure 10B Illustrated is a diagram in which a single time slot of a scheduled carrier overlaps with multiple time slots of a scheduled carrier according to certain aspects of the present disclosure.

[0032] Figure 11 Is a flowchart illustrating example operations for wireless communication by a UE according to certain aspects of the present disclosure.

[0033] Figure 12 Is a flowchart illustrating example operations for wireless communication by a BS according to certain aspects of the present disclosure.

[0034] Figure 13A Illustrated is an example of the scheduling of downlink communication according to certain aspects of the present disclosure, where the minimum scheduling offset is updated.

[0035] Figure 13B Illustrated is another example of the scheduling of downlink communication according to certain aspects of the present disclosure, where the minimum scheduling offset is updated.

[0036] Figure 14 Illustrated is a communication device (e.g., a UE) according to aspects of the present disclosure that may include various components configured to perform operations for the techniques disclosed herein.

[0037] Figure 15 Illustrated is a communication device (e.g., a BS) according to aspects of the present disclosure that may include various components configured to perform operations for the techniques disclosed herein.

[0038] For the sake of facilitating understanding, the same reference numerals are used, where possible, to designate identical elements common to the various figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. Detailed Description

[0039] Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium 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 communication, including reduced power consumption and / or reduced signaling overhead.

[0040] The following description provides examples of managing transmission scheduling in a communication system, and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functionality and arrangement of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, substitute, or add various procedures or components. For example, the methods described may be performed in a different order than described, and various steps may be added, omitted, or combined. Also, 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 an apparatus or practice a method. Additionally, the scope of the present disclosure is intended to cover such apparatus or methods practiced using other structures, functionality, or a combination of structures and functionality that supplement or are additional to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as superior or better than other aspects.

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

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

[0043] NR access (e.g., 5G NR) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeted at wide bandwidths (e.g., 80 MHz or higher), millimeter wave (mmWave) targeted at high carrier frequencies (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeted at non-backward compatible MTC technologies, and / or mission-critical services targeted at ultra-reliable low latency communication (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTIs) to meet the corresponding quality of service (QoS) requirements. Additionally, these services can coexist in the same subframe.

[0044] As Figure 1 illustrated, the wireless communication network 100 can include several base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively as BS 110) and other network entities. The BS 110 can provide communication coverage for a particular geographical area (sometimes referred to as a “cell”), which can be stationary or can move according to the location of the mobile BS 110. In some examples, the BS 110s can be interconnected with each other and / or with 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.). In Figure 1 the example shown, BSs 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BSs 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more cells. The BS 110 communicates with user equipment (UEs) 120a-y (each also individually referred to herein as UE 120 or collectively as UE 120) in the wireless communication network 100. The UEs 120 (e.g., 120x, 120y, etc.) can be dispersed throughout the wireless communication network 100, and each UE 120 can be stationary or mobile.

[0045] The wireless communication network 100 can also include relay stations (e.g., relay station 110r) (also referred to as relays, etc.), which receive transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and send the transmissions of the data and / or other information to a downstream station (e.g., UE 120 or BS 110), or relay transmissions between the UEs 120 to facilitate communication between the devices.

[0046] The network controller 130 may be coupled to a set of BSs 110 and provide coordination and control of these BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other via a wireless or wired backhaul (e.g., directly or indirectly).

[0047] Figure 2 Illustrated are example components of BS 110a and UE 120a (e.g., in Figure 1 the wireless communication network 100) that may be used to implement aspects of the present disclosure.

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

[0049] At UE 120a, antennas 252a - 252r may receive downlink signals from BS110a and may provide the received signals to demodulators (DEMOD) 254a - 254r in the transceiver, respectively. Each demodulator 254 may condition (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all demodulators 254a - 254r, perform MIMO detection on these received symbols when applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate, de-interleave, and decode) these detected symbols, provide the decoded data for UE 120a to the data sink 260, and provide the decoded control information to the controller / processor 280.

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

[0051] Memories 242 and 282 may store data and program codes for BS110a and UE 120a, respectively. The scheduler 244 may schedule the UE for data transmission on the downlink and / or uplink.

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

[0053] Figure 3 FIG. is a diagram illustrating an example of a frame format 300 for NR. The transmission timeline for each of the downlink and uplink may be divided into 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 time slots, depending on the subcarrier spacing. Each time 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 periods in each time slot. A mini-slot (which may be referred to as a sub-slot structure) refers to a transmission time interval having a duration less than that of a time slot (e.g., 2, 3, or 4 symbols).

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

[0055] In NR, synchronization signal (SS) blocks are transmitted. The SS block includes PSS, SSS, and a two-symbol PBCH. The SS block may be at a fixed time slot position (such as Figure 3The symbols 0-3 shown in are transmitted. The PSS and SSS can be used by the UE for cell search and acquisition. The PSS can provide half-frame timing, and the SSS can provide the CP length and frame timing. The PSS and SSS can provide cell identity. The PBCH carries some basic system information, such as the downlink system bandwidth, timing information within the radio frame, SSS burst set periodicity, system frame number, etc. The SS blocks can be organized into SS bursts to support beam sweeping. Further system information (such as, the 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. The SS blocks can be transmitted up to 64 times. For example, for mmW, they are transmitted up to 64 different beam directions. The up to 64 transmissions of the SS blocks are called an SS burst set. The SS blocks in an SS burst set are transmitted in the same frequency region, while the SS blocks in different SS burst sets can be transmitted at different frequency positions.

[0056] In some wireless communication networks (e.g., 5G NR), scheduling events (such as DL / UL resource grants or aperiodic triggers) can be supported on a cross-slot basis or within a slot (i.e., the same slot) basis. For example, under cross-slot scheduling, the UE can receive downlink control signaling (e.g., downlink control information (DCI) message) in one slot that schedules the UE to receive a DL transmission in another slot. Under in-slot scheduling, the UE can receive DCI in one slot that schedules the UE to receive a DL transmission later in the same slot. Switching from in-slot scheduling to cross-slot scheduling can enable the UE to reduce power consumption. For example, cross-slot scheduling can 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 the critical timeline. The longer scheduling offset under cross-slot scheduling can give the UE enough time to wake up from sleep and enable the radio interface. Scheduling events via cross-slot scheduling or in-slot scheduling can apply to DL / UL resource grants (e.g., PDSCH / PUSCH) and other DCI-triggered events, such as aperiodic channel state information reference signal (A-CSI-RS) monitoring and reporting.

[0057] Figure 4A Illustrates an example of cross-slot scheduling for downlink communication according to certain aspects of the present disclosure. The UE can receive DCI 402 from the BS via a control channel (such as the PDCCH). DCI 402 can be received in slot n and indicates the scheduling slot n+1The scheduling offset for cross-slot DL data transmission 404 (e.g., via parameter k0). The DL scheduling offset parameter k0 is greater than zero and provides a delay between the DL grant (DCI 402) and the corresponding DL data reception (e.g., via PDSCH). In some aspects, the delay between the control signaling (DCI 402) and the data transmission 404 enables 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 already knows from the PDCCH received in the previous time slot (e.g., time slot n ) whether the gNB will transmit a PDSCH for this time slot (e.g., time slot n+1 ).

[0058] Figure 4B Illustrates an example in-slot scheduling of downlink communication according to certain aspects of the present disclosure. The UE may receive DCI 406 from the BS via a control channel such as the PDCCH. DCI 406 may be received in time slot n+1 and indicate the scheduling offset for in-slot UL data transmission 408 in the same time slot n+1 (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). To enter the micro-sleep state within a time slot, the UE must wait for the PDCCH processing to complete to ensure that no PDSCH is scheduled for the same time slot, while still receiving and buffering Rx samples in the case where the DL scheduling DCI is decoded to indicate a PDSCH transmission by the BS in the same time slot. Therefore, the portion of the time slot allowing micro-sleep is much smaller compared to the cross-slot scheduling scenario (e.g., Figure 4A ), which may result in less power savings. In some cases, in-slot scheduling may enable the UE to communicate via URLLC services due to the smaller delay between the control signaling (DCI 402) and the data transmission 404.

[0059] In some wireless communication networks (e.g., 5G NR), a bandwidth part (BWP) provides a flexible framework for partitioning the frequency domain resources in a given carrier. Using the bandwidth part, a carrier can be subdivided into different bandwidth segments. For example, BWPs can overlap with each other or can be non - contiguous (i.e., separated from each other by a guard band, for example). BWPs can also be used for various purposes or functions. For example, during periods of low data activity (e.g., low throughput requirements), a UE can communicate using a narrower BWP, while during periods of high data activity (e.g., high throughput requirements), the UE can communicate using 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 a reduction in the power consumption of wireless communication. As another example, different BWPs can be used for different services or functions, such as eMBB or URLLC transmissions. In some cases, different BWPs can enable the co - existence of other systems or networks.

[0060] Figure 5 An example of downlink communication cross - BWP scheduling in accordance with certain aspects of the present disclosure is illustrated. A UE can receive DCI 502 from a BS via a control channel on a first BWP (e.g., a narrow BWP). DCI 502 can be received in a time slot m+1 and indicates the BWP identifier of a second BWP (e.g., a wider BWP) and the scheduling offset (e.g., via parameter k0) of a cross - slot DL data transmission 504 in the time slot m+2 . The BWP identifier can be a value (integer value) used to refer to one of the BWPs configured on the UE. After a certain duration, the UE can receive DCI 506, for example, in a time slot x , which indicates to switch to the first BWP (e.g., a narrow BWP).

[0061] In some wireless communication networks (e.g., 5G NR), a minimum scheduling offset can be used to determine various actions related to downlink - scheduled events such as DL / UL grants, cross - BWP scheduling, or cross - carrier scheduling. In certain aspects, the minimum scheduling offset can be the minimum applicable value for k0, k2, and A - CSI - RS triggering. In the case where k0 / k2 is below the minimum scheduling offset, the UE can 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 the 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.

[0062] 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 via RRC signaling. The L1-based adaptation of the minimum scheduling offset may be appended 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 apply 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 apply to the PUSCH scheduled by the MAC RAR for contention-based and contention-free RACH or the PUSCH scheduled by the TC-RNTI.

[0063] In a multi-carrier or multi-BWP configuration, the minimum scheduling offset value may not be clear based on different parameter designs associated with the carrier and / or BWP. For example, a UE configured with a minimum scheduling offset value may misinterpret the minimum scheduling offset value for cross-BWP scheduling when the target BWP has a different parameter design from the active BWP that receives the cross-BWP scheduling instruction. For example, assume that the target BWP has a subcarrier spacing (SCS) of 30 kHz, the active BWP has an SCS of 15 kHz, and the minimum scheduling offset is defined in terms of slots. In this scenario, the slot duration of the active BWP is 1 ms, while the slot duration of the target BWP is 0.5 ms, which may cause the UE to attempt to apply the minimum scheduling offset at half of the expected duration. Thus, the misinterpreted 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 solution would result in increased downlink signaling / overhead.

[0064] A base station and / or a UE may use various frameworks to determine a minimum scheduling offset for a downlink trigger event in a multi-carrier and / or multi-BWP configuration. This scheduling framework may improve the efficiency of wireless communication, including reduced power consumption and overhead signaling. As an example, the minimum scheduling offset may be given in terms of time domain resources (e.g., number of slots) according to the parameter design of the active BWP, reference parameter design, a set of values associated with various BWPs. In other cases, the minimum scheduling offset may be set according to the unit 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 per component carrier (CC) (e.g., shared across BWPs in a given CC) or per 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.

[0065] In the case where the minimum scheduling offset is defined per CC, the minimum scheduling offset may be defined according to the specified parameter design of the BWP (e.g., 15 kHz SCS). In various aspects, the minimum scheduling offset may have a value associated with each BWP in the CC (e.g., minimum scheduling offset parameter, X = 2 slots for 15 kHz SCS, and X = 4 slots for 30 kHz SCS). In other aspects, the minimum scheduling offset may be defined according to 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.

[0066] In some cases, the minimum scheduling offset defined per CC may not be very suitable when the BWP is 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 promotes 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 enable lower latency communication. If the minimum scheduling offset is shared across CCs, this may result in higher signaling overhead, such as to update the minimum scheduling offset when switching BWPs. The minimum scheduling offset may instead be defined per BWP to account for changes in the parameter design or function of the BWP.

[0067] In some aspects, the minimum scheduling offset can be defined per BWP according to various frameworks. For example, when a UE is instructed to switch from an active BWP to a target BWP (e.g., triggered by cross-BWP scheduling), the minimum scheduling offset can be defined according to the parameter design of the active BWP. In other cases, the minimum scheduling offset can be defined according to the parameter design of the target BWP. In various aspects, the minimum scheduling offset can 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 can 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 some other aspects, the minimum scheduling offset can be independently defined for cross-BWP scheduling.

[0068] 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 latency 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 applicable to cross-BWP scheduling. For example, the minimum scheduling offset conversion can be given by:

[0069]

[0070] where X’ is the converted minimum scheduling offset, X is the minimum offset being converted, such as the minimum offset associated with the active BWP, μ BWP,target is the parameter design of the target BWP, μ BWP,curr is the parameter design of the active BWP.

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

[0072] {k0|k2} ≥ X' or X (2)

[0073] where X’ is the converted minimum scheduling offset for cross-BWP scheduling that triggers a BWP switch between BWPs with different parameter designs. For in-BWP scheduling, X is the minimum scheduling offset according to the active BWP.

[0074] In some aspects, a UE can receive cross-carrier scheduling that schedules transmissions on another component carrier on a component carrier. For example, Figure 6An example of cross-carrier scheduling for downlink communication is explained. Assuming that the BWPs have the same parameter design, the BWP switching delay is configured to 1 time slot, the minimum scheduling offset (X) associated with BWP0 on CC1 is set to 3 time slots, the minimum scheduling offset (X) associated with BWP1 on CC1 is set to 1 time 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. DCI 602 can be received in time slot n and indicates a scheduling offset (e.g., k0 = 3), which schedules cross-carrier DL data transmission 604 on BWP0 of CC1 in time slot n+3 .

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

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

[0077] Example scheduling application delay

[0078] In some wireless communication systems (e.g., 5G NR), to adapt the minimum applicable value of k0 (k2) for the active DL (UL) BWP of the carrier over which PDSCH (PUSCH) is transmitted, a 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 of minimum scheduling offset values per BWP in accordance with some aspects of the present disclosure is illustrated. Referring to Figure 7 , the UE may be configured with two minimum scheduling offset values for DL BWP 702 (minimum k0 = 0 or 1) and two minimum scheduling offset values for UL BWP 704 (e.g., minimum k2 = 1 and 2). In this example, control signaling (e.g., DCI) may have a 1-bit indication 706 that selects which one of the UE's minimum scheduling offset values to use for communication.

[0079] 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 as the 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 the multiple candidate values. The bit flag in DCI format 1_1 or format 0_1 may be used to jointly select the minimum applicable k0 for the active DL BWP and the minimum applicable k2 value for the active UL BWP, and these two values will be applied at least after application latency.

[0080] When a BWP is activated without selecting a minimum scheduling offset value, a default value can 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 is one or two RRC-configured values for the BWP), e.g., a BWP switch triggered due to expiration of the BWP timer, etc., the value applied to the BWP can be determined by selecting any suitable value when there is only one RRC-configured value or the lowest-index RRC-configured value when 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 can be determined by selecting the configured value when one value is RRC-configured or the lowest-index RRC-configured value when multiple values are RRC-configured. In some other situations, when a BWP is activated without selecting a minimum scheduling offset value, the value applied to the BWP can be determined by selecting any suitable value. Although the examples provided herein are described with reference to a 1-bit indication flag for selecting one of two minimum scheduling offset values for the sake of facilitating understanding, aspects of the present disclosure can also be applicable to a bit mapping or index for selecting one of multiple minimum scheduling offset values.

[0081] In some wireless communication systems (e.g., 5G NR), a UE can 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 can apply the change after a certain application delay has expired. For example, for an active DL BWP and an active UL BWP, when the UE is signaled to change the minimum scheduling offset value of k0 and / or k2 via (a) L1-based signaling in slot n, the UE may not expect to apply the new minimum scheduling offset value before the slot value given by:

[0082]

[0083] where X = max(Y,Z) can be in the parameter design of the scheduled PDCCH, Y is the minimum scheduling offset value of k0 (k2) in the parameter design of the scheduled transmission before the indicated change (which can be converted and quantized to the next PDCCH slot using a conversion factor ), and Z is the minimum feasible non-zero application delay (e.g., 1). In another example, X = 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 for determining when to apply a new minimum scheduling offset may not be suitable for certain scheduling scenarios (e.g., cross-carrier scheduling) or may result in inefficiencies such as increased latency or inefficient power consumption.

[0084] In some cases, the minimum scheduling offset of k0 (or k2) for determining 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 this 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 in the TDRA table for the active DL (or UL) BWP may be assumed as the value of Y. In some cases, the UE may expect the configuration of the minimum scheduling offset for k0 (or k2), and the application delay may be determined without the default value of this minimum scheduling offset.

[0085] Certain aspects of the present disclosure provide an enhanced scheme to improve the framework for updating the minimum scheduling offset according to the application delay of when to apply the updated minimum scheduling offset. Generally, 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 would be more general to define the application delay according to the earliest time slot in which the transmission can be scheduled by applying the updated minimum value, rather than defining the start time slot for applying the updated minimum value according to the parameter design of scheduling the PDCCH. Under this definition, the earliest time slot that can be scheduled when k0 (or k2) meets the updated minimum value defined in the parameter design of k0 (or k2) can be expressed as:

[0086]

[0087] where μ BWP,target is the parameter design of the target BWP (e.g., the scheduled PDSCH or PUSCH) and μ BWP,currIt is the parameter design of the active BWP before BWP switching (e.g., for the DL BWP, it is the PDCCH that receives the control signaling). Note that one difference compared to equations (3) and (4) is that n is defined in terms of the time slots of k0 or k2 (i.e., the scheduled PDSCH / PUSCH), rather than in terms of the time slots of the PDCCH. Similar to equations (3) and (4), X = max(Y, Z), where 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, with reference to equations (3) and (4), Y can be the minimum of the minimum scheduling offset value from k0 and the minimum scheduling offset value from 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 still other aspects, if the scheduled transmission is for a PDSCH (e.g., DCI format 1_1 (DL scheduling DCI) is received on the PDCCH), then with reference to equations (3) and (4), Y can be the minimum of the minimum scheduling offset values from k0, and if the scheduled transmission is for a PUSCH (e.g., DCI format 0_1 (UL scheduling DCI) is received on the PDCCH), then with reference to equations (3) and (4), Y can be the minimum of the minimum scheduling offset values from k2.

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

[0089] 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 communication, including reduced power consumption and / or reduced signaling overhead. In some aspects, the application latency 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 latency for self-carrier scheduling can be defined according to the parameter design of the active BWP or target BWP.

[0090] In some aspects, the application latency for cross-carrier scheduling can 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 latency value can be according to the parameter design of the scheduled CC (e.g., the parameter design of the scheduled PDSCH or PUSCH), this application latency can be converted to the parameter design of the scheduling CC according to the following formula:

[0091]

[0092] where X can be a transitional value of the application latency based on at least one of the minimum scheduling offset values described, for example, with reference to equations (3) and (4) herein.

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

[0094] In some aspects, the application latency 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 latency can remain in the parameter design domain of the scheduled CC.

[0095] Figure 8 An example cross-carrier scheduling of downlink communication according to some aspects of the present disclosure is illustrated, where the application latency is defined according to the parameter design of the target BWP of the scheduled CC. Assume that BWP0 of CC0 has a parameter design associated with an SCS of 30 kHz, BWP0 of CC1 has a parameter design associated with an SCS of 120 kHz, and the current minimum scheduling offset (X) associated with BWP0 on CC1 is set to 3 time slots. As shown, the UE can communicate with the time slot of CC1 via a control channel (such as a PDCCH) on CC0 nReceive DCI 802 from the BS accordingly. DCI 802 indicates an updated value of the minimum scheduling offset (e.g., minimum k0 = 1). As an example, DCI 802 may also schedule cross-carrier DL data transmission 804 on BWP0 of CC1 at the scheduling offset of 3 time slots. As another example, the UE may also receive DCI806 from the BS on CC0 in the time slot of CC1 n+3 where DCI 806 provides cross-carrier scheduling for DL data transmission 804. n+2 In the time slot of CC1, the UE may receive DCI806 from the BS on CC0, where DCI 806 provides cross-carrier scheduling for DL data transmission 804.

[0096] The UE may apply an application delay to the parameter design of the target BWP of the scheduled CC. 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 the time slot n+2 may be scheduled at a scheduling offset greater than or equal to the current minimum scheduling offset, and subsequent time slots may be scheduled at a scheduling offset greater than or equal to the updated value of the minimum scheduling offset.

[0097] In other aspects, the value of the application delay may be based on the current minimum scheduling offset and an adjustment item. For example, the applied value may be the sum of the current minimum scheduling offset and the adjustment item, and the adjustment item may be the updated value of the minimum scheduling offset in some aspects. Referring to Figure 8 the current minimum scheduling offset may be used for the time slot n to the time slot n＝3 and the updated value of the minimum scheduling offset will be used during subsequent time slots.

[0098] For the time slots on CC1 that can be scheduled by applying the updated value of the minimum scheduling offset (e.g., minimum k0 = 1), the UE may receive DCI 808 from the BS on CC0, where DCI 808 schedules cross-carrier DL data transmission 810 on CC1 at the time slot n+5 (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 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).

[0099] In some aspects, the application delay for in-carrier scheduling may be defined according to the parameter design of the active BWP. In other words, the time slot definition of the application delay may be defined by the scheduled 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 scheduled CC according to Equation (7).

[0100] Figure 9A An example of self-carrier scheduling for downlink communication according to certain aspects of the present disclosure is illustrated, where the application delay is defined according to the parameter design of the active BWP. Assuming that the BWP switching delay is configured as 1 time slot at 15 kHz SCS and 2 time slots at 30 kHz SCS, the minimum scheduling offset (X) associated with BWP0 (15 kHz SCS) is set to 2 time slots, the minimum scheduling offset (X) associated with BWP1 (30 kHz SCS) is set to 0 time slots, and each of BWP0 and BWP1 can be configured with various values of k0. As shown, the UE can receive DCI 902 from the BS via a control channel (such as PDCCH). DCI 902 can be received in a time slot n and indicates a scheduling offset (e.g., k0 = 2), which schedules the DL data transmission 904 within the BWP in a time slot n+2 . Additionally, DCI 902 indicates that the updated value of the minimum scheduling offset changes the value to zero. In some aspects, the application delay can be based on the current minimum scheduling offset of 2 time slots. Under the parameter design of the active BWP, the UE can allow the application delay of 2 time slots to expire at a time slot n+2 where the updated value of the minimum scheduling offset can take effect.

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

[0102] For cross-carrier scheduling with the same parameter design between a scheduling carrier and a scheduled carrier, the time slots for the scheduling carrier and the scheduled carrier are aligned. The parameter design of the scheduled carrier can change in the case where its active BWP switches between two BWPs with different parameter designs. Except for the DCI on the scheduling carrier, it may not be different from self-carrier scheduling.

[0103] For cross-carrier scheduling with different parameter designs between a scheduling carrier and a scheduled carrier, there are issues of how to define the minimum scheduling offset for k0 and k2 and how to define the application delay for 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 on the scheduling carrier for the time slot used to determine the scheduling offset. For the case of scheduling a carrier with a smaller SCS (e.g., 30 kHz SCS) by a carrier with a larger SCS (e.g., 120 kHz SCS), multiple time slots of the scheduling carrier overlap with one time slot of the scheduled carrier. For example, Figure 10A A diagram illustrating that multiple time slots of a scheduling carrier 1002 overlap with a single time slot of a scheduled carrier 1004 is shown. In this example, DCI with a scheduling offset of k0 = 0 received in any of the time slots (time slots 0 - 3) of the scheduling carrier 1002 can schedule a transmission within the time slot of the scheduled carrier 1004.

[0104] For the case of scheduling a transmission on a carrier with a larger SCS by a carrier with a smaller SCS, one time slot of the scheduling carrier overlaps with multiple time slots of the scheduled carrier. For example, Figure 10B A diagram illustrating that a single time slot of a scheduling carrier 1006 overlaps with multiple time slots of a scheduled carrier 1008 is shown. In some cases where the k0 / k2 definition is aligned with the start of the time slot of the scheduled carrier, if the PDCCH is received in a later part of the time slot (e.g., consistent with the timing of the time slot of the scheduled carrier 1008), the scheduling offset will have to be greater than zero (e.g., k0 = 3) to meet the minimum scheduling offset, because k0 = 0 is already at the time slot of the scheduling carrier 1008 n+1 location. Therefore, in some cases, a single minimum k0 configured for the scheduled CC may not be efficient because this minimum scheduling offset may be over-provisioned (e.g., too long, which increases the waiting time) for a PDCCH received earlier in the time slot of the scheduling CC (e.g., at the time slot of the scheduled carrier 1008 n location). Refer to n Figure 10B ​, the PDSCH / PUSCH may not be scheduled within 2 time slots after the scheduling PDCCH. For this reason, for the later PDCCH 1012, k0 must be 3 time slots or longer. In other cases, for the earlier PDCCH 1010, k0 can be 2 or greater. Thus, overall, a single "minimum k0" that works across all PDCCH positions is 3 time slots. However, this minimum scheduling offset may be over-provisioned for some cases, which results in increased power consumption and / or increased signaling to manage the minimum scheduling offset value.

[0105] Aspects of the present disclosure relate to various techniques for determining a scheduling offset in cases where the SCS is different between the scheduling carrier and the scheduled carrier. Such techniques described herein can improve the power consumption of the UE and / or reduce the signaling overhead for managing the minimum scheduling offset value to accommodate different SCSs. In some aspects, the PDCCH may be received only in the first half of the time slot of the 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 can be relative to the time slot of the scheduled carrier that intersects the last symbol of the PDCCH on the scheduling carrier. For example, referring to Figure 10B , the minimum scheduling offset can run from the time slot of the scheduled carrier 1008 n+1 since the PDCCH 1012 is received at time slot n+1 .

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

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

[0108] The UE can take various actions when the scheduling offset is less than or equal to the minimum scheduling offset value. In some aspects, if 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 in current use, the UE can implicitly switch to the default value of the minimum scheduling offset (e.g., the value corresponding to '0' as a 1-bit indication).

[0109] In some aspects, a base station may implement various techniques for error handling in the case where the base station detects that a UE has not applied an updated minimum scheduling offset according to the application latency described herein. For example, the base station may retransmit the updated value of the minimum scheduling offset in the case where the base station determines that the UE has not properly implemented the updated value.

[0110] According to some aspects, there may be an upper limit to the minimum scheduling offset value. For example, the minimum k0 / k2 may provide sufficient latency for the modem to warm up (e.g., for cross-carrier wake-up), 3 milliseconds may be sufficient, which may be approximately 24 time slots at 120 kHz SCS. That is, the upper limit of 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 and have no upper limit.

[0111] Figure 11 is a flow chart illustrating example operation 1100 for wireless communication according to some aspects of the present disclosure. Operation 1100 may be performed, for example, by a UE (e.g., UE 120a in wireless communication network 100). Operation 1100 may be implemented as a software component executed and run on one or more processors (e.g., Figure 2 controller / processor 280). Additionally, the signal transmission and reception performed by the UE in operation 1100 may be implemented, for example, by one or more antennas (e.g., Figure 2 antenna 252). In some aspects, the transmission and / or reception of signals by the UE may be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., controller / processor 280).

[0112] Operation 1100 may begin at 1102, where the UE may receive from a base station (e.g., BS110a) one or more configurations (e.g., RRC configuration) indicating a plurality of minimum scheduling offset values (e.g., as described herein with reference to Figure 7 ). At 1104, the UE may receive from the base station a signal (e.g., control signaling, including RRC, DCI, and / or MAC-CE signaling) indicating one of these minimum scheduling offset values as the 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 latency (e.g., an application latency determined according to Equation (5), (6), or (7)) based on the scheduling type. At 1108, the UE may communicate with the base station using the updated value based on the determined time latency after receiving the signal.

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

[0114] In some aspects, the applied delay for cross-carrier scheduling may be defined according to the parameter design of the 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 the PDCCH) within a first carrier (e.g., a component carrier), and the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP (e.g., a DL or UL BWP on the PDSCH or PUSCH) within a second carrier different from the first carrier. In 1106, the delay (e.g., the applied delay) may be determined in time-domain units (e.g., symbols, time slots, frames, etc.) associated with the first BWP, such as according to the parameter design of the active BWP.

[0115] 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. For example, the conversion may include converting X according to Equation (7). 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 for communicating with the base station before the updated value. In various aspects, the value may be based on the default value of the minimum scheduling offset for communicating with the base station. For example, since X = max(Y, Z), Y may be the default value of the minimum scheduling offset, such as a fixed value or the minimum value in the TDRA table for the active DL (or UL) BWP. 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 Equation (5) and (6) may be the minimum value of the minimum scheduling offset value 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 Equation (5) and (6) may be the minimum value of the minimum scheduling offset value from k2.

[0116] 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 1100, the scheduling type indicated in the signal (e.g., as described herein with reference to Figure 8 described) may be cross-carrier scheduling, such that the signal is received via the first BWP within the first carrier, and the signal further indicates a scheduling offset to be used for communicating with the base station via the 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., the application delay) may be determined based on a value (e.g., the transition value of the application delay) in the time domain unit associated with the second BWP, e.g., according to the parameter design of the target BWP.

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

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

[0119] Since the transition value of the application delay can be in the parameter design 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 the time domain units 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 the parameter design of the scheduling CC according to Equation (7). In some aspects, this 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, this value can be determined according to various methods for determining X as described herein with reference to Equation (5) or (6). In various aspects, this value can be based on the default value of the minimum scheduling offset used for communicating with the base station.

[0120] In some aspects, the application delay for self-carrier scheduling can be defined according to the parameter design of the target BWP. For example, referring to operation 1100, the scheduling type indicated in the signal can be 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. In some cases, the UE can communicate with the base station based on the scheduling offset. At 1106, the delay (e.g., application delay) can 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).

[0121] Since the value of the application delay may already be in the time domain unit of the second BWP, this value is not converted according to Equation (7). In other words, the UE 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 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 Equation (5) or (6). In various aspects, the value can be based on the default value of the minimum scheduling offset for communicating with the base station. In various aspects, the value can be based on an adjustment term or at least one of the minimum scheduling offset values. For example, the value can be the sum of the adjustment term and at least one minimum scheduling offset value. In some aspects, the adjustment term can be the updated value indicated in the signal.

[0122] Aspects of the present disclosure relate to various techniques for determining a scheduling offset in cases where the SCS is different between the scheduling carrier and the scheduled carrier, as referred to herein Figure 10A and 10B described. In some aspects, the PDCCH can be received only in the first half of the time slot of the scheduling carrier (e.g., only within the first three symbols of the time slot of the scheduling carrier). As an example, referring to operation 1100, at 1104, the UE can receive the signal via the first BWP within the first half of the time slot of the first BWP, where 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 can 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 can have a parameter design different from that of the second BWP. In some cases, the UE can communicate with the base station based on the scheduling offset.

[0123] In various aspects, the start position of the minimum scheduling offset can be the time slot of the scheduled carrier that intersects with the last symbol of the PDCCH on the scheduling carrier, such as referred to herein Figure 10BAs described. As an example, referring to operation 1100, at 1104, the UE may receive the signal via a first BWP with a first parameter design, where the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP with a second parameter design different from the first parameter design. The UE may communicate with the base station based on the scheduling offset with respect to the time-domain resources (e.g., time slots, mini-slots, symbols, etc.) of the second BWP, where the time-domain resources intersect with the last time-domain resource of the signal (e.g., the last symbol of the PDCCH).

[0124] According to some aspects, the minimum scheduling offset may be defined in terms of the symbols of the scheduled carrier starting 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 with a first parameter design, where the signal further indicates a scheduling offset to be used for communicating with the base station via a second BWP with 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 in use before an update), where the scheduling offset and at least one minimum scheduling offset are in terms of the symbols starting from the last time-domain resource of the signal (e.g., the last symbol of the PDCCH).

[0125] 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 the 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 an update). The UE may communicate with the base station based on a default value (e.g., corresponding to a value of '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 an update).

[0126] Figure 12 is a flow chart illustrating an example operation 1200 for wireless communication according to some aspects of the present disclosure. Operation 1200 may be performed, for example, by a BS (e.g., BS110a in the wireless communication network 100). Operation 1200 may be complementary to operation 1100 performed by the BS. Operation 1200 may be implemented as a software component executed and run on one or more processors (e.g., Figure 2 the controller / processor 240). Additionally, the signal transmission and reception performed by the BS in operation 1200 may be, for example, by one or more antennas (e.g., Figure 2implemented by the antenna 234). In some aspects, signal transmission and / or reception by the BS can be implemented by obtaining and / or outputting signals via the bus interface of one or more processors (e.g., the controller / processor 240).

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

[0128] At 1208, communicating with the UE using the updated value can include the UE communicating with the base station based on the updated value, e.g., determining whether the scheduling offset (k0 or k2) satisfies the updated value according to Equation (2). As used herein, communicating with the UE can include, for example, the base station transmitting a DL data transmission to the UE. In other cases, the base station can receive a UL data transmission from the UE. In various aspects, the updated value can be used to communicate with the UE after receiving the signal and after the delay (e.g., the application delay) expires, as described herein. As an example, the time-domain resource can 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 the parameters of the PDCCH or PDSCH / PUSCH), and the delay can be determined as described herein. In other aspects, operation 1200 can include the base station transmitting to the UE one or more configurations (e.g., RRC configuration) indicating the plurality of minimum scheduling offset values (e.g., as described herein with reference to Figure 7 described).

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

[0130] 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 the 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 Equation (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 Equation (5) and (6) may be the minimum value of the minimum scheduling offset values from k2.

[0131] 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), for example, according to the parameter design of the target BWP.

[0132] 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 the default value of the minimum scheduling offset for communicating with the UE. In various aspects, the value may be based on the 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.

[0133] In some aspects, the application latency for self-carrier (i.e., within-carrier) scheduling can be defined according to the parameter design of the active BWP. For example, referring to operation 1200, this scheduling type can be self-carrier scheduling such that the signal can be 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. In some cases, the base station can communicate with the UE based on this scheduling offset. At 1206, the latency can be determined in time domain units associated with the first BWP, e.g., according to the parameter design of the active BWP.

[0134] Since the transitional value of the application latency can be according to the parameter design of the target BWP (e.g., the second BWP), the base station can convert a value (e.g., the transitional value of the application latency) into time domain units associated with the first BWP based on the parameter designs of the first BWP and the second BWP. For example, the application latency can be converted into the parameter design of the scheduling CC according to Equation (7). In some aspects, the value can 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 can be determined according to various methods for determining X as described herein with reference to Equation (5) or (6). In various aspects, the value can be based on the default value of the minimum scheduling offset for communicating with the UE.

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

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

[0137] Aspects of the present disclosure relate to various techniques for determining a scheduling offset in scenarios where the SCS is different between a scheduling carrier and a scheduled carrier, as described herein with reference to Figure 10A and 10B described. In some aspects, the PDCCH may be transmitted only in the first half of the time slot of the scheduling carrier (e.g., only within the first three symbols of the time slot of the scheduling carrier). As an example, referring to operation 1200, the base station may transmit the signal within the first half of the time slot of the first BWP via the first BWP, where the signal further indicates a scheduling offset for communicating with the UE via the second BWP. In 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 different parameter configuration from that of the second BWP. In some cases, the base station may communicate with the UE based on the scheduling offset.

[0138] In aspects, the starting position of the minimum scheduling offset may be the time slot of the scheduled carrier that intersects with the last symbol of the PDCCH on the scheduling carrier, as described herein with reference to Figure 10B described. As an example, referring to operation 1200, at 1204, the base station may transmit the signal via the first BWP having a first parameter configuration, where the signal further indicates a scheduling offset to be used for communicating with the base station via the second BWP having a second parameter configuration different from the first parameter configuration. The base station may communicate with the UE based on the scheduling offset with respect to the time domain resources (e.g., time slots, mini-slots, symbols, etc.) of the second BWP, where the time domain resources intersect with the last time domain resource (e.g., the last symbol of the PDCCH) of the signal.

[0139] According to some aspects, the minimum scheduling offset may be defined in terms of the symbols of the scheduled carrier starting 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 the first BWP having a first parameter configuration, where the signal further indicates a scheduling offset to be used for communicating with the UE via the second BWP having a second parameter configuration different from the first parameter configuration. 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 in use before the update), where the scheduling offset and at least one minimum scheduling offset are in terms of the symbols starting from the last time domain resource (e.g., the last symbol of the PDCCH) of the signal.

[0140] The base station may take various actions when 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 the scheduling offset to be used for communicating with the UE. The base station may determine the value of the scheduling offset at least in part based on the minimum scheduling offset value used for communicating with the UE (e.g., the value currently being used before the update). The base station may communicate with the UE based on a default value (e.g., corresponding to '0' (zero) as the value of 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 being used before the update).

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

[0142] Additional example scheduling application delays

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

[0144] n’+X(8)

[0145] Where:

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

[0147] Y may be at least one of the configured minimum scheduling offset values such as the current minimum k0 (or k2). A may be an adjustment term such as the updated minimum scheduling offset value. Z may be a value that ensures the total application delay is not too small. For example, the value of Z may be (1,1,[2],[2]) for SCS of (15,30,60,120) KHz respectively. In some aspects, X = Y + A + Z or X = max(Y,Z) + max(A,Z) may also provide a suitable value for X. In equation (8), n’ may 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 parameter design of the scheduling PDCCH may be given by:

[0148]

[0149] Figure 13AAn example scheduling of downlink communication in accordance with certain aspects of the present disclosure is illustrated, where 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 may receive DCI 1302 from the BS via a control channel (such as PDCCH) in a time slot n The DCI 1302 indicates an updated value of the minimum scheduling offset (e.g., from the current minimum k0 = 2 to the minimum k0 = 1). The DCI 1302 may also schedule a DL data transmission 1304 on BWP0 in the time slot n+2 At 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 in the case of k0 = 1 is time slot n+3. The UE may receive DCI 1306 from the BS via a control channel (such as PDCCH) in the time slot n+2 And the DCI 1306 with a scheduling offset value of 1 may schedule a DL data transmission 1308 on BWP0 in the time slot n+3 .

[0150] Figure 13B An example scheduling of downlink communication in accordance with certain aspects of the present disclosure is illustrated, where 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 may receive DCI 1310 from the BS via a control channel (such as PDCCH) in a time slot n The DCI 1310 indicates an updated value of the minimum scheduling offset (e.g., from the current minimum k0 = 0 to the minimum k0 = 1). The DCI 1310 may also schedule a DL data transmission 1312 on BWP0 in the time slot n At 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 may receive DCI 1314 from the BS via a control channel in the time slot n+1 And the DCI 1314 with a scheduling offset value of 1 may schedule a DL data transmission 1316 on BWP0 in the time slot n+2 .

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

[0152] Continuous update of the minimum scheduling offset

[0153] Regarding application latency, continuous changes to the minimum scheduling offset can be supported. In some aspects, such as for a minimum time scale (e.g., URLLC communication), the minimum scheduling offset can be updated to adapt to traffic variations 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 waiting time introduced is at least temporarily tolerable. In such cases, the continuous update of the minimum scheduling offset can be disabled or not desired.

[0154] In some aspects, the base station can suppress signaling the continuous change of the minimum scheduling offset before the time when the previous change is expected to be applied and / or acknowledged by the UE. For example, if the previous indication is waiting to be applied, the UE may not expect another indication of the change of the minimum scheduling offset in the scheduling DCI. In another example, the UE may not expect to receive another indication of the change of the minimum scheduling offset in the scheduling DCI for the same active BWP before the time of acknowledging the receipt of the previous indication of the change of the minimum scheduling offset. If the previous change indication is carried in the DL scheduling DCI, the time of acknowledgment 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 acknowledgment 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 the opportunity to synchronize on the change of the minimum scheduling offset before moving to another change.

[0155] Figure 14 Illustrated can include operations configured to perform the techniques disclosed herein, such as Figure 11A communication device 1400 (e.g., UE 120a) of various components (e.g., corresponding to apparatus-plus-function components) for the operations illustrated in []. 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 for the communication device 1400 (such as various signals described herein) 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.

[0156] 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 instructions (e.g., computer-executable code) that, when executed by the processor 1404, cause the processor 1404 to perform Figure 11 the operations illustrated in [] or other operations for performing 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 circuitry configured to implement the code stored in the computer-readable medium / memory 1412. The processor 1404 includes circuitry 1422 for receiving, circuitry 1424 for identifying, circuitry 1426 for determining (including circuitry for converting), and / or circuitry 1428 for using (including circuitry for communicating, circuitry for receiving, and / or circuitry for transmitting).

[0157] Figure 15 illustrates a communication device 1500 (e.g., BS 110a) that may include various components (e.g., corresponding to apparatus-plus-function components) configured to perform operations for the techniques disclosed herein, such as Figure 12 the operations illustrated in []. 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 for the communication device 1500 (such as various signals described herein) 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.

[0158] 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 instructions (e.g., computer-executable code) that, when executed by the processor 1504, cause the processor 1504 to perform the operations illustrated in Figure 12 or other operations for performing the various techniques for managing scheduled transmissions discussed herein. In some aspects, the computer-readable medium / memory 1512 stores code 1514 for transmitting, code 1516 for selecting, code 1518 for determining (including code for converting), and / or code 1520 for using (including code for communicating, code for receiving, and / or code for transmitting). In some aspects, the processor 1504 has circuitry configured to implement the code stored in the computer-readable medium / memory 1512. The 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).

[0159] The techniques described herein can be used in a variety of wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE-Advanced (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. CDMA networks may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks may 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 part of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "Third Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "Third Generation Partnership Project 2" (3GPP2). NR is an emerging wireless communication technology under development.

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

[0161] In 3GPP, the term "cell" may refer to the coverage area of a Node B (NB) and / or the NB subsystem serving that coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and BS, next-generation Node B (gNB or g Node B), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. A BS may provide communication coverage for macro cells, picocells, femtocells, and / or other types of cells. A macro cell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unconstrained access by UEs with a service subscription. A picocell may cover a relatively small geographical area and may allow unconstrained access by UEs with a service subscription. A femtocell may cover a relatively small geographical area (e.g., a residence) and may allow constrained access by UEs associated with that femtocell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). The BS for a macro cell may be referred to as a macro BS. The BS for a picocell may be referred to as a pico BS. The BS for a femtocell may be referred to as a femto BS or a home BS.

[0162] A UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premise equipment (CPE), cellular phone, smartphone, 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 equipment, biometric sensor / device, wearable device (such as a smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired media. 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 may communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to a network (e.g., a wide area network such as the Internet or a cellular network) or provide connectivity to the 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.

[0163] 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 tones, frequency bins, etc. Each subcarrier can be modulated with data. Generally, modulation symbols are transmitted 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 subcarrier spacing can be 15 kHz, and the minimum resource allocation (referred to as a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Thus, 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 can also be divided into subbands. For example, a subband can cover 1.8 MHz (e.g., 6 RBs), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively. In LTE, the basic Transmission Time Interval (TTI) or packet duration is a 1 ms subframe.

[0164] NR can utilize OFDM with CP on both the uplink and downlink and includes support for half-duplex operation using TDD. In NR, a subframe is still 1 ms, but the basic TTI is referred to as a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16... slots), which depends on the subcarrier spacing. An NR RB is 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15 kHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. Symbol and 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 configured dynamically. 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 with up to 2 streams per UE can be supported. Up to 8 serving cells can be used to support the aggregation of multiple cells.

[0165] In some examples, access to an air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all of the devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for the scheduled communication, the subordinate entities utilize the 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 the other UEs may utilize the 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.

[0166] 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 communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Everything (IoE) communication, IoT communication, mission-critical mesh, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is conveyed from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., a UE or a BS), even though a scheduling entity may be used for scheduling and / or control purposes. In some examples, sidelink signals may be conveyed using licensed spectrum (different from wireless local area networks, which typically use unlicensed spectrum).

[0167] The methods disclosed herein include one or more steps or acts for implementing the methods. These method steps and / or acts may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of the steps or acts is specified, the order and / or use of the specific steps and / or acts may be altered without departing from the scope of the claims.

[0168] As used herein, a phrase that recites “at least one of” a list of items refers to any combination of those items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a - b, a - c, b - c, and a - b - c, as well as any combination with multiple identical elements (e.g., a - a, a - a - a, a - a - b, a - a - c, a - b - b, a - c - c, b - b, b - b - b, b - b - c, c - c, and c - c - c, or any other ordering of a, b, and c).

[0169] As used herein, the term "determine" encompasses a variety of actions. For example, "determine" can include computing, calculating, processing, deriving, researching, looking up (e.g., looking up in a table, database, or other data structure), ascertaining, and the like. Also, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determine" can include parsing, selecting, choosing, establishing, and the like.

[0170] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein the recitation of a singular element is not intended to mean "one and only one" (unless specifically so stated) but "one or more." Unless specifically stated otherwise, the term "some / a" means one or more. Elements of the various aspects described throughout this disclosure that are presently known or later come to be known to those of ordinary skill in the art as all structural and functional equivalents thereof are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. No element of a claim should be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the phrase "step for."

[0171] The various operations of the methods described above can be performed by any suitable means capable of performing the corresponding functions. These means can 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 figures, these operations may have corresponding paired means-plus-function components with similar numbers.

[0172] The various illustrative logical blocks, modules, and circuits described in connection with the present disclosure may be implemented or performed 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, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0173] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented with a bus architecture. Depending on the particular application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, machine-readable media, 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 the case of user equipment 120 (see Figure 1 ), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as a timing source, peripherals, voltage regulators, power management circuits, and similar circuits that are well known in the art and will not be described further herein. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Depending on the particular application and overall design constraints imposed on the overall system, those of ordinary skill in the art will recognize how best to implement the functionality described with respect to the processing system.

[0174] If implemented in software, each function can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Software should be broadly construed to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program 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. The computer-readable storage medium may be coupled to the processor such that the processor can read from and write to the storage medium. In an alternative, the storage medium may be integrated into the processor. By way of example, machine-readable media may include transmission lines, carrier waves modulated with data, and / or computer-readable storage media separate from a wireless node that stores instructions thereon, all of which may be accessed by the processor via a bus interface. Alternatively or additionally, machine-readable media or any part thereof may be integrated into the processor, such as may be the case with a cache and / or a general register file. By way of example, examples of machine-readable 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 medium, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0175] Software modules may include a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media may include several software modules. These software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. These software modules may include a transmission module and a reception module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During the execution of a software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may then be loaded into the general register file for execution by the processor. When referring to the functionality of a software module hereinafter, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0176] Similarly, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a web site, 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 the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and disc, where disk typically reproduces data magnetically, while disc reproduces data optically with a laser. Thus, in some aspects, a computer-readable medium may include a non-transitory computer-readable medium (e.g., a tangible medium). Additionally, for other aspects, a computer-readable medium may include a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

[0177] Accordingly, certain aspects may include a computer program product for performing the operations given herein. For example, such a computer program product may include a computer-readable medium having (and / or encoded thereon) instructions that can be executed by one or more processors to perform the operations described herein, such as instructions for performing the operations described and illustrated in Figure 11 and / or Figure 12 herein.

[0178] Furthermore, it should be appreciated that modules and / or other suitable means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or a base station where applicable. For example, such devices 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 floppy disk, etc.) such that once the storage device is coupled to or provided to the user terminal and / or base station, the device can obtain the various methods. Additionally, any other suitable technology adapted to provide the methods and techniques described herein to a device can be utilized.

[0179] It will be understood that the claims are not limited to the exact configurations and components described above. Various changes, substitutions, and alterations can be made in the layout, operation, and details of the methods and apparatuses described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment, comprising: Receiving, from a base station, one or more configurations indicating a plurality of minimum scheduling offset values; Receiving, via a first bandwidth part BWP within a first carrier, a signal from the base station, the signal indicating one of the minimum scheduling offset values as an updated value to be used for communication with the base station, and indicating to communicate with the base station via a second BWP within a second carrier different from the first carrier; Determining a delay based on parameter designs of the first BWP and the second BWP; And Based on expiration of the delay, communicating with the base station via the second BWP using the updated value.

2. The method according to claim 1, wherein the delay is in a time domain unit associated with the first BWP.

3. The method according to claim 2, wherein determining the delay further comprises: Converting the delay into the time domain unit associated with the first BWP based on the 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 3, wherein the delay is based on a ratio of a first parameter design of the first BWP to a second parameter design of the second BWP.

7. The method according to claim 6, wherein the delay is further based on a product of at least one of the minimum scheduling offset values and the ratio.

8. A method for wireless communication by a base station, comprising: Selecting one of a plurality of minimum scheduling offset values as an updated value to be used for communication with a user equipment UE; Transmitting, via a first bandwidth part BWP within a first carrier, a signal to the UE, the signal indicating the updated value and indicating to communicate with the UE via a second BWP within a second carrier different from the first carrier; Determining a delay based on parameter designs of the first BWP and the second BWP; And Based on expiration of the delay, communicating with the UE via the second BWP using the updated value.

9. The method according to claim 8, wherein the delay is in a time domain unit associated with the first BWP.

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

11. The method according to claim 10, wherein the delay is based on a default value of a minimum scheduling offset for communication with the UE.

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

13. The method according to claim 10, wherein the delay is based on a ratio of a first parameter design of the first BWP to a second parameter design of the second BWP.

14. The method according to claim 13, wherein the delay is further based on a product of at least one of the minimum scheduling offset values and the ratio.

15. An apparatus for wireless communication, comprising: A transceiver configured to: Receive one or more configurations indicating multiple minimum scheduling offset values from a base station, and Receive a signal from the base station via a first bandwidth part (BWP) within a first carrier, the signal indicating one of the minimum scheduling offset values as an updated value to be used for communication with the base station, and indicating to communicate with the base station via a second BWP within a second carrier different from the first carrier; A memory; And One or more processors coupled to the memory, the one or more processors and the memory being configured to determine a delay based on parameter designs of the first BWP and the second BWP; Wherein the transceiver is further configured to communicate with the base station via the second BWP using the updated value based on expiration of the delay.

16. The apparatus according to claim 15, wherein the delay is in a time domain unit associated with the first BWP.

17. The apparatus according to claim 16, wherein, to determine the delay, the one or more processors and the memory are further configured to convert the delay into the time domain unit associated with the first BWP based on the parameter designs of the first BWP and the second BWP.

18. The apparatus according to claim 17, wherein the delay is based on a default value of a minimum scheduling offset for communicating with the base station.

19. The apparatus according to claim 17, wherein the delay is based on at least one of the minimum scheduling offset values.

20. The apparatus according to claim 17, wherein the delay is based on a ratio of a first parameter design of the first BWP to a second parameter design of the second BWP.

21. The apparatus according to claim 20, wherein the delay is further based on a product of at least one of the minimum scheduling offset values and the ratio.

22. An apparatus for wireless communication, comprising: A memory; One or more processors coupled to the memory, the one or more processors and the memory being configured to select one of a plurality of minimum scheduling offset values as an updated value to be used for communication with a user equipment (UE); And A transceiver configured to transmit a signal to the UE via a first BWP within a first carrier, the signal indicating the updated value and indicating to communicate with the UE via a second BWP within a second carrier different from the first carrier, wherein: The one or more processors and the memory are further configured to determine a delay based on parameter designs of the first BWP and the second BWP; and The transceiver is further configured to communicate with the UE via the second BWP using the updated value based on expiration of the delay.

23. The apparatus according to claim 22, wherein the delay is in a time domain unit associated with the first BWP.

24. The apparatus according to claim 23, wherein determining the delay further comprises: Convert the delay into the time domain unit associated with the first BWP based on the parameter designs of the first BWP and the second BWP.

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

26. The apparatus according to claim 24, wherein the delay is based on at least one of the minimum scheduling offset values.

27. The apparatus according to claim 24, wherein the delay is based on a ratio of a first parameter design of the first BWP to a second parameter design of the second BWP.

28. The apparatus according to claim 27, wherein the delay is further based on a product of at least one of the minimum scheduling offset values and the ratio.

Images