METHODS FOR DETERMINING MINIMUM DELAY IN APPLYING SCHEDULING COMPENSATION

Abstract

A method, system, and apparatus for methods for determining a minimum scheduling offset application delay are described. According to one aspect, a method at a network node (16) includes determining (S142) an application delay based at least in part on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of scheduling component carrier, wherein the application delay is associated with at least one of the first and second minimum scheduling offsets.According to another aspect, a method in a wireless device (22) includes receiving (S144) an indication of an application delay from a network node (16), wherein the application delay is based at least partly on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of programming component carrier, and the application delay is associated with at least one of the first and second minimum programming offsets.

Description

The present invention relates to wireless communications and, in particular, to the determination of the minimum delay of the scheduling compensation application. BACKGROUND OF THE INVENTION One of the power-consuming activities of a wireless device in RRC_CONNECTED mode is monitoring the physical downlink control channel (PDCCH). Therefore, PDCCH monitoring must be performed efficiently. One method for effective PDCCH monitoring is to configure scheduling in cross-interval mode. When using cross-interval scheduling, the wireless device does not need to buffer the physical downlink shared channel (PDSCH) after the last PDCCH symbol and can enter micro-sleep earlier in the respective interval. In Version (Rei.) 16 of the Third Generation Partnership Project (3GPP), this function is supported by the introduction of the minimumSchedulingOffset parameter, which is configured in the Bandwidth Part Radio Resource Control (BWP). On the downlink (DL), the minimumSchedulingOffset represents the minimum offset between the scheduling PDCCH and its scheduled PDSCH or aperiodic Channel Status Information Reference (CSI-RS) signals. On the uplink, the minimumSchedulingOffset represents the minimum offset between the scheduling PDCCH and its scheduled physical uplink shared channel (PUSCH) or aperiodic Polling Reference Signal (SRS). With this configuration, the wireless device can know in advance whether it will always be scheduled using cross-interval scheduling. While beneficial from an energy consumption perspective, always using cross-interval scheduling is not advantageous when a data burst occurs. From the network node's perspective, having a minimumSchedulingOffset value greater than 0 will limit scheduling flexibility. From the wireless device's perspective, this can introduce additional latency. Therefore, it can be beneficial if the wireless device and network node can switch between cross-interval mode (i.e., minimumSchedulingOffset > 0) and same-interval mode (i.e., minimumSchedulingOffset = 0 or disabled). In 3GPP Rei. 16, an additional bit field is introduced into the Downlink Control Information (DCI). Using this bit field, the wireless device can switch between cross-range mode and same-range mode, thus achieving optimal power consumption and latency compensation. However, the existing provisions are lacking. BRIEF DESCRIPTION OF THE INVENTION Some modalities adequately provide methods, network nodes, and wireless devices for methods to determine the minimum scheduling compensation application delay. According to one aspect of the present invention, a method carried out by a network node is provided. The method is for the transition between a first minimum offset and a second minimum offset, in which various numerologies are applied. The method includes determining an application delay based at least in part on a first subcarrier separation (SCS) associated with a bandwidth portion (BWP) of the programming component carrier, where the application delay is associated with at least one of the first and second minimum programming offsets. ancefrn / zznz / q / uιλι In some embodiments of this aspect, determining the application delay includes determining the application delay based at least in part on the first minimum compensation, where the first minimum compensation is a currently applied minimum compensation. In some embodiments of this aspect, the application delay corresponds to the conversion between a second scheduling mode and a first scheduling mode, the first and second scheduling modes differing at least in their respective minimum scheduling compensation. In some embodiments of this aspect, the second scheduling mode is a cross-interval mode in which the minimum scheduling compensation is greater than zero, and the first scheduling mode is a same-interval mode in which the minimum compensation parameter is equal to zero. In some forms of this aspect, the determination of the application delay for scheduling between carriers with a mixed numerology comprises, when the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programming component carrier BWP are different, determining a normalized value for the first minimum scheduling offset of the programmed component carrier BWP with respect to the first SCS associated with the programming component carrier BWP. In some forms of this aspect, the normalized value, minX', is determined by: 2^ROOOOH min / U — min / C · -----2FPDSCH where minK is a minimum compensation currently applied; ^pdcch is associated with the first SCS, wherein the first SCS is associated with a physical programming downlink control channel, PDCCH; and Ppdsch is associated with the second SCS, where the second SCS is associated with a shared physical downlink channel, planned PDSCH. In some embodiments of this aspect, determining the application delay comprises determining a minimum feasible application delay, Z; and when an associated physical downlink control channel, PDCCH, the monitoring occasion occurs after a specific symbol within an interval, increasing the minimum feasible application delay by a specified amount. In some embodiments of this aspect, the specified amount is 1 interval. In some embodiments of this aspect, determining the application delay comprises determining a minimum offset currently applied as the application delay based at least in part on the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programmed component carrier BWP. In some embodiments of this aspect, the method also includes transmitting an indication of the determined application delay to the wireless device. In some embodiments of this aspect, the determined application delay indicates when to begin applying the second minimum scheduling offset after the wireless device receives a change indication, where the change indication signals that a new minimum scheduling offset should be applied.In some embodiments of this aspect, determining the application delay comprises determining the application delay based, at least in part, on a minimum offset currently applied in the scheduled component carrier BWP, a minimum feasible application delay, Z, of the scheduling component carrier BWP, the first SCS associated with the carrier of the scheduling component carrier BWP, and a second subcarrier separation, SCS, associated with a scheduled component carrier BWP. In some embodiments of this aspect, the determined application delay is based, at least in part, on a type of physical downlink control channel monitoring case, PDCCH. According to another aspect of the present invention, a method carried out by a wireless device is provided. The method is for the transition between a first minimum offset and a second minimum offset in which various numerologies are applied. The method includes receiving an indication of an application delay from a network node; the application delay is based at least in part on a first subcarrier separation (SCS) associated with a bandwidth portion (BWP) of the programming component carrier, and the application delay is associated with at least one of the first and second minimum programming offsets; and beginning to apply the second minimum offset based at least in part on the received application delay. In some forms of this aspect, the application delay is also based, at least in part, on the first minimum compensation, where the first minimum compensation is a currently applied minimum compensation. In some forms of this aspect, the application delay corresponds to the conversion between a second scheduling mode and a first scheduling mode, the first and second scheduling modes differing at least in their respective minimum scheduling compensation. In some forms of this aspect, the second scheduling mode is a cross-interval mode in which the minimum scheduling compensation is greater than zero, and the first scheduling mode is a same-interval mode in which the minimum compensation parameter is equal to zero. In some forms of this aspect, the application delay is for inter-carrier programming with mixed numerology; and when the first SCS associated with the programming component carrier BWP and a second inter-carrier separation, SCS, associated with a programming component carrier BWP are different, the application delay is further based, at least in part, on a normalized value for the first programmed component carrier BWP in relation to the first SCS associated with the programming component carrier BWP. In some forms of this aspect, the normalized value, minK', is determined by: 2^PDCCH min / <' = min / C-2 / zPDSCH where minK is a minimum compensation currently applied; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a physical programming downlink control channel, PDCCH; and Ppdsch is associated with the second SCS, where the second SCS is associated with a shared physical downlink channel, planned PDSCH. In some embodiments of this aspect, the application delay is based at least in part on a minimum feasible application delay, Z; and when an associated physical downlink control channel monitoring (PDCCH) occasion follows a specific symbol within an interval, the minimum feasible application delay is increased by a specified amount. In some embodiments of this aspect, the specified amount is 1 interval. In some embodiments of this aspect, the application delay is a minimum offset currently applied based at least in part on the first subcarrier separation (SCS) associated with the programming component carrier bandwidth (BWP) and a second subcarrier separation (SCS) associated with a programming component carrier bandwidth (BWP).In some forms of this aspect, the determined application delay indicates when to begin applying the second minimum scheduling compensation after the wireless device receives a change indication, where the change indication signals that a new minimum scheduling compensation should be applied. In some embodiments of this aspect, the ancefrn / zznz / q / uli method also includes receiving the change indication via a downlink control information (DCI) message. In some embodiments of this aspect, the application delay is based, at least in part, on a minimum offset currently applied to the scheduled component carrier BWP, a minimum feasible application delay, Z, of the scheduling component carrier BWP, the first subcarrier separation (SCS) associated with the scheduling component carrier BWP, and a second subcarrier separation (SCS) associated with a scheduled component carrier BWP. In some embodiments of this aspect, the application delay is based, at least in part, on a type of physical downlink control channel monitoring (PDCCH) case. According to another aspect of the present invention, a network node is provided for the transition between a first minimum offset and a second minimum offset in which various numerologies are applied. The network node includes a processing circuit. The processing circuit is configured to cause the network node to determine an application delay based at least in part on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of the programming component carrier, wherein the application delay is associated with at least one of the first and second minimum programming offsets. In some embodiments of this aspect, the processing circuit is configured to determine the application delay by having the network node determine the application delay based at least in part on the first minimum offset, where the first minimum offset is a currently applied minimum scheduling offset. In some embodiments of this aspect, the application delay corresponds to the conversion between a second scheduling mode and a first scheduling mode, where the first and second scheduling modes differ at least in their respective minimum scheduling offsets. In some embodiments of this aspect, the second scheduling mode is a cross-interval mode in which the minimum scheduling offset is greater than zero, and the first scheduling mode is a same-interval mode in which the minimum offset parameter is equal to zero. In some modalities of this aspect, the processing circuit is configured to determine the application delay for cross-carrier scheduling with a mixed numerology by being configured to make the network node, when the first SCS associated with the BWP of programming component carrier and a second subcarrier separation, SCS, associated with a programmed component carrier BWP are different, determine a normalized value for the first minimum scheduling offset of the programmed component carrier BWP in relation to the first SCS associated with the programming component carrier BWP. In some forms of this aspect, the normalized value, minK', is determined by: 2ííPDCCH min / U = minK-2^pdsch where minK is a minimum compensation currently applied; gpDccH is associated with the first SCS, where the first SCS is associated with a scheduling physical downlink control channel, PDCCH; and gpDscH is associated with the second SCS, where the second SCS is associated with a planned physical downlink shared channel, PDSCH. In some embodiments of this aspect, the processing circuitry is configured to determine the application delay by having the network node determine a minimum feasible application delay, Z; and when an associated physical downlink control channel monitoring occasion, PDCCH, occurs after a specific symbol within an interval, increase the minimum feasible application delay by a specified amount. In some embodiments of this aspect, the specified amount is 1 interval.In some modalities of this aspect, the processing circuit is configured to determine the application delay by being configured to cause the network node to determine a currently applied minimum offset as the application delay based at least in part on the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programmed component carrier BWP. In some embodiments of this aspect, the processing circuitry is configured to have the network node transmit an indication of the determined application delay to the wireless device. In some embodiments of this aspect, the determined application delay indicates when to begin applying the second minimum scheduling offset after the wireless device receives a change indication, where the change indication signals that a new minimum scheduling offset should be applied. In some embodiments of this aspect, the processing circuitry is configured to determine the application delay by having the network node determine the application delay based, at least in part, on a minimum scheduling offset currently applied to the scheduled component carrier BWP, a minimum feasible application delay, Z, of the scheduling component carrier BWP, the first SCS associated with the carrier of the scheduling component carrier BWP, and a second subcarrier separation, SCS, associated with a scheduled component carrier BWP. In some embodiments of this aspect, the determined application delay is based, at least in part, on a type of physical downlink control channel monitoring case, PDCCH. According to another aspect of the present invention, a wireless device is provided for the transition between a first minimum offset and a second minimum offset in which various numerologies are applied. The wireless device includes processing circuitry. The processing circuitry is configured to cause the wireless device to receive an indication of an application delay from a network node, the application delay being based at least in part on a first subcarrier separation (SCS) associated with a bandwidth portion of the programming component carrier's bandwidth (BWP), and wherein the application delay is associated with at least one of the first and second minimum programming offsets; and to begin applying the second minimum offset based at least in part on the received application delay. In some embodiments of this aspect, the application delay is also based, at least in part, on the first minimum compensation, where the first minimum compensation is a currently applied minimum compensation. In some embodiments of this aspect, the application delay corresponds to the conversion between a second scheduling mode and a first scheduling mode, the first and second scheduling modes differing at least in their respective minimum scheduling compensation. In some embodiments of this aspect, the second scheduling mode is a cross-interval mode in which the minimum scheduling compensation is greater than zero, and the first scheduling mode is a same-interval mode in which the minimum compensation parameter is equal to zero. In some forms of this aspect, the application delay is for programming between carriers with a mixed numerology; and when the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programmed component carrier BWP are different, the application delay is further based, at least in part, on a normalized value for the first programming component carrier BWP of the programmed component carrier BWP in relation to the first SCS associated with the programming component carrier BWP. In some forms of this aspect, the normalized value, minK', is determined by: 2APDCCH minK' = minÁ'-2 / / pdsch where ininK is a minimum compensation currently applied; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a physical programming downlink control channel, PDCCH; and Ppdsch is associated with the second SCS, where the second SCS is associated with a shared physical downlink channel, planned PDSCH. In some embodiments of this aspect, the application delay is based at least in part on a minimum feasible application delay, Z; and when an associated physical downlink control channel monitoring occasion, PDCCH, occurs after a specific symbol within an interval, the minimum feasible application delay is incremented by a specified amount. In some embodiments of this aspect, the specified amount is 1 interval. In some embodiments of this aspect, the application delay is a minimum offset currently ancefrn / zznz / q / uli applied based at least in part on the first SCS associated with the component programming carrier BWP and a second subcarrier separation, SCS, associated with a component programming carrier BWP programming. In some embodiments of this aspect, the predetermined application delay indicates when to begin applying the second minimum scheduling offset after the wireless device receives a change indication, where the change indication signals that a new minimum scheduling offset should be applied. In some embodiments of this aspect, the processing circuitry is further configured to have the network node receive the change indication via a Downlink Control Information (DCI) message.In some embodiments of this aspect, the application delay is based, at least in part, on a minimum offset currently applied to the scheduled component carrier BWP, a minimum feasible application delay, Z, of the scheduling component carrier BWP, the first SCS associated with the scheduling component carrier BWP, and a second subcarrier separation, SCS, associated with a scheduled component carrier BWP. In some embodiments of this aspect, the application delay is based, at least in part, on a type of physical downlink control channel monitoring case, PDCCH. ancefrn / zznz / q / uιλι BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present modalities, and their corresponding advantages and characteristics, will be more easily grasped with reference to the following detailed description when considered together with the accompanying drawings in which: Figure 1 is a schematic diagram of an example network architecture illustrating a communication system connected through an intermediate network to a main computer in accordance with the principles of the present invention. Figure 2 is a block diagram of a main computer communicating through a network node with a wireless device via a connection that is at least partially wireless according to some embodiments of the present invention. Figure 3 is a flowchart illustrating examples of methods implemented in a communication system that includes a main computer, a network node, and a wireless device to run a client application on a wireless device in accordance with some embodiments of the present invention. Figure 4 is a flowchart illustrating examples of methods implemented in a communication system that includes a main computer, a network node, and a wireless device for receiving user data in a wireless device according to some embodiments of the present invention. Figure 5 is a flowchart illustrating exemplary methods implemented in a communication system that includes a main computer, a network node, and a wireless device for receiving user data from the wireless device on a main computer according to some embodiments of the present invention. Figure 6 is a flowchart illustrating examples of methods implemented in a communication system that includes a main computer, a network node, and a wireless device for receiving user data on a main computer according to some embodiments of the present invention. Figure 7 is a flow diagram of an exemplary process at a network node for methods to determine the minimum scheduling compensation application delay according to some embodiments of the present invention. Figure 8 is a flowchart of an example process on a wireless device for methods to determine the minimum scheduling offset application delay. Figure 9 is a flow diagram of an exemplary process at a network node for methods to determine the minimum scheduling compensation application delay according to some embodiments of the present invention. Figure 10 is a flowchart of an exemplary process on a wireless device for methods to determine the minimum scheduling offset application delay. DETAILED DESCRIPTION OF THE INVENTION As discussed earlier, while switching between cross-interval mode and same-interval mode can be beneficial, the mode used by the wireless device and the network node within a given interval generally needs to be agreed upon (i.e., there should be no misalignment between the network node and the wireless device). Otherwise, a PDCCH decoding error could occur. For example, the wireless device might receive a schedule with a K0 or K2 value lower than the minimum schedule offset. To achieve alignment, the wireless device and the network node can agree on when to apply a certain mode (i.e., cross-interval mode or same-interval mode) during transmission. While the network node might apply the mode change directly in the next interval, the wireless device might not be able to. This can be because the wireless device needs time to decode the PDCCH received during the PDCCH's monitoring occasion (MO). This decoding process can finish at any time between the last received PDCCH symbol and the first PDSCH symbol programmed by the PDCCH.Therefore, a certain application delay can be specified so that the network node and the wireless device agree on when to start applying a certain mode (cross-range mode or same-range mode, i.e., a minimum scheduling offset greater than zero or a minimum scheduling offset equal to zero). The application delay can only be specified by considering a programming case with the same numerology (i.e., same-carrier programming or programming between carriers with the same numerology), for example, with the PDCCH 1-1 monitoring case. However, the wireless device can be configured, for example, with the PDCCH 1-2 monitoring case or the PDCCH 2 monitoring case. Alternatively, the network node can program the wireless device using cross-carrier programming with mixed numerology. Some embodiments of the present invention provide methods and arrangements for determining the application delay of a new minimum offset (e.g., a change / switch between a first minimum scheduling offset value and a second minimum scheduling offset value). Some embodiments may accommodate cross-carrier scheduling and / or Case 1-2 and Case 2 PDCCH monitoring. In cross-carrier scheduling, a scheduling PDCCH in a given interval may schedule a PxSCH (i.e., PUSCH, PDSCH) in a different interval. This document describes various aspects related to determining the application delay for, for example, scheduling cross-intervals to the same interval and vice versa, for a wireless device configured with minimumSchedulingOffset. Specifically, several mechanisms for determining the application delay are presented, considering the following examples: • Programming of cross-carriers or of the same carriers; • Possibility of multiple PDCCH monitoring cases, i.e., where PDCCH MOs fall within a range; • Possibility of having a plurality of SCSs between the programming PDCCH and the programmed PxSCH (i.e., PUSCH, PDSCH); and • Minimum feasible application delay, i.e., the minimum time required by or allocated to the wireless device to switch between cross-interval scheduling and same-interval scheduling, or alternatively to switch between two different minimum scheduling offset values ​​(e.g., a first and second minimum scheduling offset values). Before describing exemplary embodiments in detail, it should be noted that the embodiments consist primarily of combinations of apparatus components and processing steps related to determining the minimum programming compensation application delay. Accordingly, the components have been represented, where applicable, by conventional symbols in the drawings, which show only the specific details relevant to understanding the embodiments so as not to obscure the invention with details that will be readily apparent to those skilled in the art who benefit from the description contained herein. Similar numbers refer to similar elements throughout the description. As they are currently used, relational terms such as first and second, superior and inferior, and the like, can only be used for In some of the modalities described in this document, the terms coupled, connected, and similar terms may be used here to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections. The term network node as used herein may be any type of network node comprising a radio network, which may further comprise any base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), gB node (gNB), evolved B node (eNB or eNodeB), B node, multi-standard radio (MSR) node such as MSR BS, multicast / multicell coordination entity (MCE), integrated access and backoff (IAB) node, relay node, donor node control relay, radio access point (AP), transmit points, transmit nodes, remote radio unit (RRU), remote radio head (RRH), a core network node (e.g., mobile management entity (MME)), self-organizing network node (SON), a coordination node, a positioning node, a node MDT, etc.), an external node (e.g., a third-party node, a node external to the current network), nodes in the distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include test equipment. The term radio node used herein may also refer to a wireless device, such as a wireless device or a radio network node. In some modalities, the non-limiting terms wireless device or user equipment (UE) are used interchangeably. The wireless device described herein may be any type of wireless device capable of communicating with a network node or another wireless device via radio signals, such as a wireless device.The wireless device can also be a radio communication device, a target device, a device-to-device (D2D) wireless device, a machine-type wireless device or a wireless device with machine-to-machine (M2M) communication capability, a low-cost and / or low-complexity device, a sensor equipped with a wireless device, a tablet, mobile terminals, a smartphone, a wearable embedded equipment (LEE), a laptop-mounted equipment (LME), USB dongles, customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc. In addition, in some modalities the generic term ancefrn / zznz / q / uili is used for radio network node. It can be any type of radio network node, which may include any base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multicell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), or remote radio head (RRH). Note that although the terminology of a particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this invention, this should not be seen as limiting the scope of the invention to only the systems mentioned above. Other wireless systems, including, but not limited to, Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Ultra Mobile Broadband (UMB), and the Global System for Mobile Communications (GSM), may also benefit from the exploitation of the ideas covered within this invention. It should also be noted that the functions described herein, when performed by a wireless device or network node, can be distributed among multiple wireless devices and / or network nodes. In other words, the network node and wireless device functions described herein are not limited to the performance of a single physical device and can, in fact, be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by a person skilled in the art to which this invention pertains. It is further understood that terms used herein should be interpreted in a way that is consistent with their meaning in the context of this specification and the relevant art, and not in an idealized or overly formal sense unless expressly defined herein. Some modes provide methods for determining the minimum scheduling compensation application delay. In some modes, the minimum scheduling compensation application delay can be determined even for PDCCH 2 monitoring or PDCCH 1-2 monitoring, and for cross-carrier scheduling with mixed numerologies. This allows the wireless device and the network node to agree on when to initiate a specific mode (i.e., cross-range mode or same-range mode) or, alternatively, to initiate the new minimum scheduling compensation value for those cases, thus avoiding misalignment. With reference now to the figures in the drawings, in which similar elements are referenced with similar reference numbers, Figure 1 shows a schematic diagram of a communication system 10, according to a modality, such as a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), comprising an access network 12, such as a radio network access network and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage areas 18). Each network node 16a, 16b, 16c can be connected to the central network 14 via a wired or wireless connection 20.A first wireless device 22a located in coverage area 18a is configured to connect wirelessly to, or be discovered by, the corresponding network node 16a. A second wireless device 22b in coverage area 18b can connect wirelessly to the corresponding network node 16b. Although this example illustrates a plurality of wireless devices 22a, 22b (collectively referred to as wireless devices 22), the described modes are equally applicable to a situation where only one wireless device is in the coverage area or where a single wireless device is connecting to the corresponding network node 16. Note that although only two wireless devices 22 and three network nodes 16 are shown for convenience, the communication system may include many more wireless devices 22 and network nodes 16. Furthermore, it is envisaged that a wireless device 22 may be in simultaneous communication and / or configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, a wireless device 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, the wireless device 22 may be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN. The communication system 10 itself may be connected to a main computer 24, which may be incorporated into the hardware and / or software of a standalone server, a cloud-deployed server, a distributed server, or as processing resources in a server farm. The main computer 24 may be owned or controlled by a service provider, or it may be operated by the service provider on behalf of the service provider. The connections 26, 28 between the communication system 10 and the main computer 24 may extend directly from the core network 14 to the main computer 24 or may extend through an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private, or hosted network. The intermediate network 30, if any, may be a core network or the Internet.In some configurations, the intermediate network 30 may comprise two or more subnetworks (not shown). The communication system in Figure 1, as a whole, enables connectivity between one of the connected wireless devices 22a, 22b and the main computer 24. This connectivity can be described as an over-the-top (OTT) connection. The main computer 24 and the connected wireless devices 22a, 22b are configured to communicate data and / or signaling over the OTT connection, using the access network 12, the core network 14, any intermediate networks 30, and any additional infrastructure (not shown) as intermediaries. The OTT connection can be transparent in that at least some of the participating communication devices through which the OTT connection passes are unaware of the uplink and downlink routing.For example, a network node 16 ancefrn / zznz / q / uli may or may not need to be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to forward (e.g., deliver) it to a connected wireless device 22a. Similarly, network node 16 does not need to be aware of the future routing of an outgoing uplink communication originating from the wireless device 22a to the host computer 24. A network node 16 is configured to include an application delay determinator 32 that is configured to determine an application delay based at least in part on a first subcarrier separation (SCS) associated with a bandwidth portion (BWP) of a scheduling component carrier, where the application delay is associated with at least one of the first and second minimum scheduling offsets. In some modes, the network node 16 is configured to include an application delay determinator 32 that is configured to determine an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode in which the minimum scheduling offset parameter is equal to zero. ancefrn / zznz / q / uιλι A wireless device 22 is configured to include a mode determination unit 34 that is configured to receive an indication of an application delay from a network node. The application delay is based at least in part on a first subcarrier separation (SCS) associated with a bandwidth portion (BWP) of the scheduling component carrier, and the application delay is associated with at least one of the first and second minimum scheduling offsets. The device then begins to apply the second minimum offset based at least in part on the received application delay. In some modes, a wireless device 22 is configured to include a mode determination unit 34 that is configured to initiate either a same-range mode or a cross-range mode depending on whether the application delay is zero or greater than zero. Example implementations, according to one modality, of the wireless device 22, network node 16, and host computer 24 discussed in the preceding paragraphs will now be described with reference to Figure 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 that includes a communication interface 40 configured to establish and maintain a wired or wireless connection with an interface of a communication device other than the communication system 10. The host computer 24 further comprises a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and memory 46.In particular, in addition to or instead of a processor, such as a central processing unit and memory, the processing circuit 42 may comprise an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 44 may be configured to access (for example, write and / or read) memory 46, which may comprise any type of volatile and / or non-volatile memory, for example, cache and / or buffer and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory). The processing circuit 42 can be configured to control any of the methods and / or processes described in this document and / or to cause such methods and / or processes to be carried out, for example, by a main computer 24. The processor 44 corresponds to one or more processors 44 for carrying out the functions of the main computer 24 described in this document. The main computer 24 includes a memory 46 that is configured to store data, programmatic software code, and / or other information described in this document. In some embodiments, the software 48 and / or the main application 50 may include instructions that, when executed by the processor 44 and / or the processing circuit 42, cause the processor 44 and / or the processing circuit 42 to carry out the processes described in this document with respect to the main computer 24.The instructions may be software associated with the main computer 24. Software 48 can be executable by processing circuit 42. Software 48 includes a main application 50. The main application 50 can function to provide a service to a remote user, such as a wireless device 22 that connects via an OTT connection 52 terminating at the wireless device 22 and the main computer 24. In providing the service to the remote user, the main application 50 can provide user data that is transmitted via the OTT connection 52. The user data can be data and information described herein as implementing the described functionality. In one mode, the main computer 24 can be configured to provide control and functionality to a service provider and can be operated by or on behalf of the service provider.The processing circuit 42 of the main computer 24 can allow the main computer 24 to observe, monitor, control, transmit and / or receive from the network node 16 and / or the wireless device 22. The communication system 10 further includes a network node 16 provided in a communication system 10 and includes hardware 58 that enables it to communicate with the main computer 24 and with the wireless device 22. The hardware 58 may include a communication interface 60 for configuring and maintaining a wired or wireless connection with an interface of a communication device other than the communication system 10, as well as a radio interface 62 for establishing and maintaining at least one wireless connection 64 with a wireless device 22 located within a coverage area 18 served by the network node 16. The radio interface 62 may consist of, or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the main computer 24.Connection 66 can be direct or can pass through a central network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside of the communication system 10. In the configuration shown, the hardware 58 of network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and memory 72. In particular, in addition to or instead of a processor, such as a central processing unit and memory, the processing circuit 68 may comprise an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 70 may be configured to access (for example, write and / or read) the memory 72, which may comprise any type of volatile and / or non-volatile memory, for example, cache and / or buffer and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory). Therefore, network node 16 also has software 74 stored internally, for example, in memory 72, or stored in external memory (for example, database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 can be executable by processing circuit 68. Processing circuit 68 can be configured to control any of the methods and / or processes described in this document and / or to cause such methods and / or processes to be carried out, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for carrying out the functions of network node 16 described in this document. Memory 72 is configured to store data, programmatic software code, and / or other information described in this document.In some configurations, software 74 may include instructions that, when executed by processor 70 and / or processing circuit 68, cause processor 70 and / or processing circuit 68 to perform the processes described in this document with respect to network node 16. For example, processing circuit 68 of network node 16 may include an application delay determinator 32 that is configured to determine an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode in which the minimum scheduling offset parameter is equal to zero. The communication system 10 further includes the wireless device 22 already mentioned. The wireless device 22 may have hardware 80 which may include a radio interface 82 configured for ancefrn / zznz / q / uli in the memory 88 of the wireless device 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the wireless device 22. The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may operate to provide a service to a human or non-human user through the wireless device 22, with support from the host computer 24.On the main computer 24, a running main application 50 can communicate with a running client application 92 via an OTT connection 52 that terminates at wireless device 22 and the main computer 24. In providing service to the user, the client application 92 can receive request data from the main application 50 and provide user data in response. The OTT connection 52 can transfer both request data and user data. The client application 92 can interact with the user to generate the user data they provide. The processing circuit 84 can be configured to control any of the methods and / or processes described in this document and / or cause such methods and / or processes to be carried out, for example, by the wireless device 22. The processor 86 corresponds to one or more processors 86 to carry out the functions of the wireless device 22 described in this document. The wireless device 22 includes a memory 88 that is configured to store data, programmatic software code, and / or other information described in this document. In some modalities, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to carry out the processes described in this document with respect to the wireless device 22.For example, the processing circuit 84 of the wireless device 22 may include a mode determination unit 34 that is configured to initiate either a same-interval mode or a cross-interval mode depending on whether the application delay is zero or greater than zero. In some modalities, the internal operation of network node 16, wireless device 22, and main computer 24 may be as shown in Figure 2, and independently, the surrounding network topology may be that of Figure 1. In Figure 2, OTT connection 52 is drawn abstractly to illustrate communication between host computer 24 and wireless device 22 via network node 16, without explicit reference to any intermediary devices, and the precise routing of messages through these devices. The network infrastructure can determine the routing, which can be configured to hide from wireless device 22, the service provider operating host computer 24, or both. While OTT connection 52 is active, the network infrastructure can also make decisions that dynamically change the routing (for example, based on load balancing or network reconfiguration). The wireless connection 64 between wireless device 22 and network node 16 is in accordance with the principles of the modes described throughout this document. One or more of the various modes enhance the performance of the OTT services provided to wireless device 22 using the OTT connection 52, in which the wireless connection 64 can form the final segment. More specifically, the principles of some of these modes can improve data rates, latency, and / or power consumption, and thus provide benefits such as reduced user wait times, relaxed file size restrictions, improved responsiveness, longer battery life, etc. ancefrn / zznz / q / uιλι In some modes, a measurement procedure may be provided to monitor data rate, latency, and other factors that improve one or more modes. Additionally, there may be optional network functionality to reconfigure the OTT connection 52 between the host computer 24 and the wireless device 22 in response to variations in measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the host computer 24's software 48, the wireless device 22's software 90, or both.In some modalities, sensors (not shown) may be implemented in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 52 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect network node 16, and may be unknown or imperceptible to network node 16. Some of such procedures and functionalities may be known and practiced in the art.In certain modes, measurements may involve signaling proprietary wireless devices that facilitate measurements of performance, propagation times, latency, and the like from the host computer.24 In some modes, measurements may be implemented so that the software 48, 90 causes messages, in particular empty or 'dummy' messages, to be transmitted using the OTT connection 52 while monitoring propagation times, errors, etc. Therefore, in some modes, the main computer 24 includes a processing circuit 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the wireless device 22. In some modes, the cellular network also includes the network node 16 with a radio interface 62. In some modes, the network node 16 is configured and / or the processing circuit 68 of the network node 16 is configured to carry out the functions and / or methods described in this document to initiate / maintain / support / terminate a transmission to the wireless device 22, and / or prepare / terminate / maintain / support / terminate the reception of a transmission from the wireless device 22. In some embodiments, the main computer 24 ancefrn / zznz / q / uli includes a processing circuit 42 and a communication interface 40 that is configured to receive user data originating from a transmission from a wireless device 22 to a network node 16. In some embodiments, the wireless device 22 is configured for, and / or comprises, a radio interface 82 and / or a processing circuit 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating a transmission to network node 16, and / or preparing / terminating / maintaining / supporting / terminating the reception of a transmission from network node 16. Although Figures 1 and 2 show various units, such as the application delay determinator 32 and the mode determinator 34 within a respective processor, it is envisaged that these units can be implemented so that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, the units can be implemented in hardware or in a combination of hardware and software within the processing circuit. Figure 3 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figures 1 and 2, according to a specific modality. The communication system may include a main computer 24, a network node 16, and a wireless device 22, which may be those described with reference to Figure 2. In the first step of the method, the main computer 24 provides user data (Block S100). In an optional sub-step of the first step, the main computer 24 provides the user data by executing a main application, such as the main application 50 (Block S102). In the second step, the main computer 24 initiates a transmission that carries the user data to the wireless device 22 (Block S104).In an optional third step, network node 16 transmits to wireless device 22 the user data that was carried in the transmission initiated by the host computer 24, in accordance with the teachings of the modes described throughout this description (Block S106). In an optional fourth step, wireless device 22 runs a client application, such as, for example, client application 92, associated with the host application 50 run by the host computer 24 (Block S108). Figure 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 1, according to a modality. The communication system may include a main computer 24, a network node 16, and a wireless device 22, which may be those described with reference to Figures 1 and 2. In the first step of the method, the main computer 24 provides user data (Block S110). In an optional substep (not shown), the main computer 24 provides the user data by running a main application, such as main application 50. In the second step, the main computer 24 initiates a transmission that carries the user data to the wireless device 22 (Block S112).The transmission can pass through network node 16, in accordance with the modalities described throughout this document. In an optional third step, wireless device 22 receives the user data carried in the transmission (Block S114). Figure 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 1, according to a modality. The communication system may include a main computer 24, a network node 16, and a wireless device 22, which may be those described with reference to Figures 1 and 2. In an optional first step of the method, the wireless device 22 receives input data provided by the main computer 24 (Block S116). In an optional sub-step of the first step, the wireless device 22 runs the client application 92, which provides user data in response to the received input data provided by the main computer 24 (Block S118). Additionally, or alternatively, in an optional second step, the wireless device 22 provides user data (Block S120).In an optional sub-step of the second step, the wireless device provides the user data by running a client application, such as, for example, client application 92 (Block S122). When providing the user data, the running client application 92 may also consider user input received from the user. Regardless of the specific way in which the user data was provided, the wireless device 22 may initiate, in a third optional sub-step, the transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the wireless device 22, in accordance with the teachings of the modalities described throughout this description (Block S126). Figure 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 1, according to a specific modality. The communication system may include a host computer 24, a network node 16, and a wireless device 22, which may be those described with reference to Figures 1 and 2. In an optional first step of the method, in accordance with the principles of the modalities described throughout this document, network node 16 receives user data from wireless device 22 (Block S128). In an optional second step, network node 16 initiates the transmission of the received user data to host computer 24 (Block S130). In a third step, host computer 24 receives the user data carried in the transmission initiated by network node 16 (Block S132). Figure 7 is a flowchart of an exemplary process at a network node 16 for methods to determine the minimum scheduling offset application delay. One or more blocks described in this document may be carried out by one or more elements of network node 16, such as by one or more of the processing circuit 68 (including the application delay determinator 32), the processor 70, the radio interface 62 and / or the communication interface 60. Network node 16, such as through the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60, is configured to determine an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode in which the minimum scheduling offset parameter is equal to zero (Block S134).The process also optionally includes transmitting the determined application delay to the wireless device (S136 Block). Figure 8 is a flowchart of an exemplary process in a wireless device 22 according to certain embodiments of the present invention. One or more blocks described herein may be carried out by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the mode determination unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22, as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82, is configured to receive an application delay from the network node (Block S138). The process also includes initiating a same-interval mode or a cross-interval mode according to whether the application delay is zero or greater than zero (Block S140). Figure 9 is a flowchart of an example process at a network node 16 for the transition between a first minimum compensation and a second minimum compensation where various numerologies are applied. One or more blocks described in this document may be carried out by one or more elements of the network node 16, such as by one or more of the processing circuit 68 (including the application delay determinator 32), the processor 70, the radio interface 62, and / or the communication interface 60.Network node 16, as via processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to determine (Block S142) an application delay based at least in part on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of programming component carrier where the application delay is associated with at least one of the first and second minimum programming offsets. In some modes, network node 16, such as through processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to determine the application delay by being configured to have the network node determine the application delay based, at least in part, on the first minimum scheduling offset, where the first minimum scheduling offset is a currently applied minimum scheduling offset. In some modes, the application delay corresponds to the conversion between a second scheduling mode and a first scheduling mode, the first and second scheduling modes differing at least in their respective minimum scheduling offsets.In some modes, the second programming mode is a cross-interval mode in which the minimum programming offset is greater than zero, and the first programming mode is a same-interval mode in which the minimum offset parameter is equal to zero. In some modalities, network node 16, such as through processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to determine the application delay for cross-carrier scheduling with mixed numerology by being configured to make the network node, when the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programmed component carrier BWP are different, determine a normalized value for the first minimum offset of the programmed component carrier BWP in relation to the first SCS associated with the programming component carrier BWP. In some modalities, the normalized value, minK', is determined by: 24PDCCH min / U = min / f-2ZíPDSCH where ininK is a minimum compensation currently applied; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a physical programming downlink control channel, PDCCH; and Ppdsch is associated with the second SCS, where the second SCS is associated with a shared physical downlink channel, planned PDSCH. In some modes, network node 16, such as through processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to determine the application delay by being configured to have the network node determine a minimum feasible application delay, Z; and when an associated physical downlink link control channel monitoring occasion, PDCCH, comes after a specific symbol within an interval, increase the first minimum offset by a specific amount. In some modes, the specific amount is 1 interval. In some modes, network node 16, such as through processing circuit 68 and / or processor and / or radio interface 62 and / or communication interface 60, is configured to determine the application delay by being configured to determine a minimum applied scheduling offset as the application delay based at least in part on the first subcarrier separation (SCS) associated with a programming component carrier bandwidth (BWP) and a second subcarrier separation (SCS) associated with a programming component carrier bandwidth (BWP). In some modes, network node 16, such as through processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to transmit an indication of the determined application delay to wireless device 22. In some modes, the determined application delay indicates when to begin applying the second minimum scheduling offset after the wireless device receives a change indication, where the change indication signals that a new minimum scheduling offset should be applied.In some modes, network node 16, such as through processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to determine the application delay by being configured to have the network node determine the application delay based, at least in part, on a minimum offset currently applied to the programmed component carrier BWP, an application delay, Z, of the programming component carrier BWP, the first SCS associated with the programming component carrier BWP, and a second subcarrier separation, SCS, associated with a programmed component carrier BWP. In some modes, the determined application delay is based, at least in part, on a type of physical downlink control channel monitoring case, PDCCH. Figure 10 is a flowchart of an exemplary process in a wireless device 22 according to certain embodiments of the present invention, such as for the transition between a first minimum compensation and a second minimum compensation where various numerologies are applied. One or more blocks described herein may be carried out by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the mode determination unit 34), the processor 86, the radio interface 82, and / or the communication interface 60.The wireless device 22, as via processing circuit 84 and / or processor 86 and / or radio interface 82, is configured to receive (Block S144) an indication of an application delay from a network node. The application delay is based at least in part on a first subcarrier separation (SCS) associated with a bandwidth portion (BWP) of the programming component carrier, and the application delay is associated with at least one of the first and second minimum programming offsets. The wireless device 22, as via processing circuit 84 and / or processor 86 and / or radio interface 82, is configured to begin (Block S146) applying the second minimum programming offset based, at least in part, on the received application delay. In some modes, the application delay is also based, at least in part, on the first minimum compensation, where the first minimum compensation is a currently applied minimum compensation. In some modes, the application delay corresponds to the conversion between a second programming mode and a first programming mode, the first and second programming modes differing at least in their respective minimum programming compensation. In some modes, the second programming mode is a cross-interval mode in which the minimum programming compensation is greater than zero, and the first programming mode is a same-interval mode in which the minimum compensation parameter is equal to zero. ancefrn / zznz / q / uιλι In some modes, the application delay is for scheduling between carriers with a mixed numerology; and when the first SCS associated with the programming component carrier BWP of the carrier and a second subcarrier separation, SCS, associated with a programmed component carrier BWP are different, the application delay is further based, at least in part, on a normalized value for the first minimum scheduling offset of the programmed component carrier BWP relative to the first SCS associated with the programming component carrier BWP. In some modalities, the normalized value, minK', is determined by: 2AíPDCCH min / C' = min / C-2Aípdsch where minK is a minimum compensation currently applied; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a physical programming downlink control channel, PDCCH; and Dpdsch is associated with the second SCS, where the second SCS is associated with a shared physical downlink channel, planned PDSCH. In some modes, the application delay is based, at least in part, on a minimum feasible application delay, Z; and when an associated physical downlink control channel monitoring (PDCCH) occasion follows a specific symbol within an interval, the first minimum scheduling offset is increased by a specified amount. In some modes, the specified amount is 1 interval. In some modes, the application delay is a minimum offset currently applied based, at least in part, on the first subcarrier separation (SCS) associated with the programming component carrier bandwidth (BWP) and a second subcarrier separation (SCS) associated with a programming component carrier bandwidth (BWP). In some modes, the predetermined application delay indicates when to begin applying the second minimum programming offset after the wireless device receives a change indication, where the change indication signals that a new minimum programming offset should be applied. In some modes, the wireless device 22, for example, via processing circuit 84 and / or processor 86 and / or radio interface 82, is configured to receive the change indication via a downlink control information (DCI) message.In some modes, the application delay is based, at least in part, on a minimum compensation currently applied to the scheduled component carrier BWP, an application delay, Z, of the scheduling component carrier BWP, the first SCS associated with the scheduling scheduled component carrier BWP, and a second subcarrier separation, SCS, associated with a scheduled component carrier BWP. In some modes, the application delay is based, at least in part, on a type of physical downlink control channel monitoring case, PDCCH. Having described the general flow of the process of arrangements of the invention and having provided examples of hardware and software arrangements to implement the processes and functions of the invention, the sections below provide details and examples of arrangements and methods for determining the minimum delay of applying scheduling compensation, which can be implemented by the network node 16 and / or the wireless device 22. A scenario is considered where network node 16 and wireless device 22 currently apply a certain minimumSchedulingOffset1 value and wish to transition to another value, minimumSchedulingOffset2 (for example, after receiving a mode change instruction from network node 16). Here, the currently applied minimumSchedulingOffset will be indicated as minK. The following describes aspects related to determining the application delay for the transition between modes (CS mode and SS mode) or, alternatively, the transition from applying the currently applied minK to applying the new minK value. When determining application delay, network node 16 and / or wireless device 22 may consider one or more of several aspects: 1) The minimumSchedulingOffset value before the change, minK. In some modes, the minK value represents the minimum interval distance between the programming PDCCH and the programming PDSCH. For example, the minK value could represent the maximum number of intervals used by the wireless device 22 to complete the reception and decoding of the PDCCH, or the processing time of the PDCCH. The minK value can also be determined based on the specific cell, BWP, or SCS. In yet another example, wireless device 22 can provide support information that helps network node 16 configure minK for different scenarios, for example, if and how minK should be configured for different BWPs or different SCSs. Furthermore, the minK can be determined based on a trade-off between energy savings gain and the performance of the wireless device 22. For example, if the wireless device 22 can process PDCCHs within an interval and, for example, the 1-1 PDCCH monitoring case is used, a minK of 1 interval can provide a good energy savings gain and minimal performance loss for the wireless device 22. In another example, if, for instance, the minK value is not less than a minimum feasible application delay, and / or, for example, PDCCH monitoring case 1-1 is used, and / or, for example, the same numerology scheduling is applied, the new minK application delay can be equal to the currently applied minK value. However, if, for example, other PDCCH monitoring cases are used, the configured minK can be incremented, for example, at network node 16 and / or wireless device 22. For example, when PDCCH monitoring case 1-2 or 2 is used and / or the PDCCH monitoring occasion (MO) falls after a specific symbol, network node 16 can increment the minK by a certain amount, and so on. 2) Minimum feasible application delay, Z. In one example, the value of Z represents the minimum time required and / or allocated to wireless device 22 to receive and decode PDCCHs. The value of Z can, for example, be determined based on an interval. The value of Z can also be determined by assuming a certain PDCCH monitoring case (e.g., ancefrn / zznz / q / uili PDCCH monitoring case 1-1). Furthermore, or alternatively, the value of Z can depend on the numerology (or subcarrier spacing (SCS)) used by the component carrier (CC) programming BWP. For example, programming the CC BWP with small SCSs (e.g., 15 and 30 kHz) and the 1-1 PDCCH monitoring case might have Z = 1, while programming the CC BWP with larger SCSs (e.g., 60 and 120 kHz) might have Z = 2, and so on. The Z value can be useful because a wireless device 22 might currently be applying a minK value that is smaller than Z. For example, when the same interval mode is currently running, the minK value is disabled or set to 0. In that case, the wireless device 22 might not apply the new minK value in the minK-th interval after receiving a minK change indication. Instead, the wireless device 22 might only apply the new minK value in the Z-th interval after receiving the minK change indication. 3) The SCS of the BWP of the programming CC and the SCS of the BWP of the programmed CC. In one example, if the BWP SCS of both CCs is the same, network node 16 can consider the currently applied minK as the application delay, particularly if, for example, the PDCCH 1-1 monitoring case is used. ancefrn / zznz / q / uιλι However, to save energy, reduce the possibility of misalignment, or for any other reason, network node 16 may consider a longer application delay. In another example, if, for instance, inter-carrier scheduling with mixed numerology is used, in which case the SCS of the BWP of the scheduling CCs and the BWP of the scheduled CCs are different, network node 16 can use a normalized minK value of the scheduled CCs. BWP relative to the SCS of the BWP of the scheduling CC. For example, the following normalization can be used: minK' = minK · 2^PDCCH Z^PDSCH ' ancefrn / zznz / q / υιλι Network node 16 may also apply an additional weighting factor for other reasons, for example, to provide more energy-saving opportunities to wireless device 22, reduce the possibility of misalignment, etc. 4) PDCCH monitoring case. In some configurations, network node 16 may configure wireless device 22 with PDCCH monitoring case 1-2, case 2, or any other PDCCH monitoring case where the PDCCH MO can be expected to fall anywhere within the range. Alternatively, network node 16 may configure wireless device 22 with the minK value and agree with wireless device 22 on the Z value, assuming PDCCH monitoring case 1-1 as the typical PDCCH monitoring case. Therefore, network node 16 and wireless device 22 can also determine which type of PDCCH monitoring case is being used for transmission. In one example, if, for instance, the PDCCH 1-2 monitoring case is used and / or the associated PDCCH MO comes after a specific symbol within the interval, network node 16 may decide to increase the minimum scheduling offset by a specific amount, for example, 1 additional interval. Similarly, if, for example, the PDCCH 2 monitoring case is employed, and / or the last PDCCH MO in an interval comes after a specific symbol within the interval, network node 16 can determine to increase the minimum scheduling offset by a specific amount, for example, 1 additional interval. Taking into account one or more of the above factors, some or all of the following methods can be used to determine the new minK application delay. In one example, a method can be used to determine the new application delay of minK when using the same carrier schedule and / or applying a PDCCH monitoring case that differs from the reference PDCCH monitoring case. The method may include one or more of the following: • Store the current minK value where the current minK value is associated with the current BWP and / or for a reference PDCCH control case (e.g., PDCCH control case 1-1); • Store the Z value where the value is associated with the BWP SCS and / or for a reference PDCCH monitoring case (e.g., PDCCH monitoring case 1-1); • Calculate the new-minK application delay for the second PDCCH monitoring case (e.g., PDCCH monitoring case 1-2); • Where the derived value is based on at least one or more of: a) Current minK value; b) The applied Z value; c) An additional factor (for example, a) that depends on the PDCCH monitoring case and the last symbol of a reference PDCCH monitoring case. The value of a may further be based on the final symbol of the second PDCCH monitoring case; and / or c) Alternatively, the value of a can also be based on a standardized processing time required by the scheduling CC to program a CC with a higher SCS. In this option, the value of a depends, at least, on the scheduling of the SCS and PDCCH monitoring case. • Apply the application delay. For example, network node 16 programs wireless device 22 with K0, K2, etc. values ​​no less than the new minK value after the application delay. Wireless device 22 can then be ready for programming using K0, K2, etc. values ​​no greater than the minK value. Note that because the minK value is per BWP, the minK value for the downlink (DL) and uplink (UL) can be different (i.e., it limits the K0 and K2 values ​​differently). In another example, a method described below can be used to determine the new application delay minK when using cross-carrier scheduling (particularly for the mixed numerology case) and / or a PDCCH monitoring case that is the same with the reference "The PDCCH monitoring case applies." This method may include one or more of the following: • Store the current minK value, where the current minK value is associated with the BWP of the current scheduled CC and / or for a reference PDCCH monitoring case (e.g., PDCCH monitoring case 1-1). ancefrn / zznz / q / uili • Store the Z value where the value is associated with the BWP SCS of the programming CC and / or for a reference PDCCH monitoring case (e.g., PDCCH monitoring case 1-1). • Calculate the new-minK application delay for the scheduling CC. • Where the derived value is based on at least one or more of: a) Current minK value; b) The applied Z value; c) The numerology (or SCS) of the BWP of the CC of programming; and / or d) The numerology (or SCS) of the BWP of the programmed CC. • Apply the application delay. For example, on network node 16, network node 16 programs wireless device 22 with K0, K2, etc. values ​​no less than the new minK value after the application delay. Wireless device 22 can then be ready for programming using K0, K2, etc. values ​​no greater than the minK value. Note that because the minK value is per BWP, the minK value for DL ​​and UL can be different (i.e., it limits the K0 and K2 values ​​differently). In another example, combinations of the previous methods can be used to determine the delay of applying the new minK when cross-carrier scheduling is used and / or PDCCH monitoring is applied that differs from the reference PDCCH monitoring case. In one example, this can be done by inserting the third and fourth elements of the first method's example as a factor in the fourth element of the second method's example. As an example, using the methods described above, the following formula can be used to determine the new-minK application delay of a programming CC with numerology p_CC1 in your BWP, which programs a CC with numerology p_CC2 in your BWP configuration. Note that the formula and the following steps are only an example. Derivation, modification, etc., based on the methods above are not excluded. Q2^CC11 X min / C · —— ,Z + a]. 2^CC2 |' J. Specifically, the above formula can be explained as: • Store the configured minK value in the scheduled CC's BWP; • Store the applied Z value from the programming CC BWP; and • Determine the value of parameter a. In one example, the value of 'a' can be based on the standardized processing time required by the scheduling CC to schedule CCs with a higher SCS. In this option, the value of 'a' depends, at least, on the scheduling of the SCS and PDCCH monitoring case. In another example, network node 16 might decide to minimize the performance loss of wireless device 22 and thus consider this value to be zero. In yet another example, network node 16 might decide to consider a higher number, for example, to provide a greater opportunity for energy savings for wireless device 22 or to reduce the possibility of misalignment, etc. In another example, when using case 1-2 or case 2 of PDCCH monitoring in transmission, the value of a can be further derived from the location of the last PDCCH monitoring symbol relative to the third symbol as the last possible monitored PDCCH reception symbol in case 1-1 of PDCCH monitoring. In another example, the value of 'a' can be set to 0 or 1. The decision to use 0 or 1 is based on the PDCCH monitoring case used in CC programming. For example: 1) If the PDCCH 1-1 monitoring case is used, the value of a can be set to 0. 2) If the PDCCH 2 monitoring case is used, the value of a can be set to 1. 3) If the PDCCH 1-2 monitoring case is used, network node 16 can further check which symbols in an interval the PDCCH monitoring will end at. Then, wireless device 22 could determine the value of 'a' based on this information and the programming CC numerology. For example: a) For a programming CC with numerology 0 and 1 (SCS = 15kHz and 30kHz), the value of a can be set to 0 if the PDCCH monitoring ends on the tenth symbol or less. Otherwise, set the value of a to 1. b) For a programming CC with numerology 2 (SCS = 60kHz), the value of a can be set to 0 if the PDCCH monitoring ends on the 7th symbol or less. Otherwise, set the value of a to 1. c) For a programming CC with numerology 3 (SCS = 120kHz), the value of a can be set to 0 if the PDCCH monitoring ends on symbol 11 or less. Otherwise, set the value of a to 1. • It is noted that the value obtained from step 3 can be normalized and quantified to the numerology of the BWP of the programmer CC. 4. Add the parameter a to the Z value. 5. Check if the value obtained in step 4 is less than the value obtained in step 5. If the value obtained in step 4 is greater, the value obtained in step 4 is used as the new application delay for minK. Otherwise, the value obtained in step 5 is used as the application delay. Additional aspects: In the previous example modalities, a scenario was considered where network node 16 configures the associated parameters, particularly the application delay, for an individual wireless device 22. Network node 16 may further consider adjusting the application delay or other parameters such as minK after considering all the underlying wireless devices 22 in a cell, BWP, etc. In this way, network node 16 may wish to align these parameters across all wireless devices 22 or a subset of them. Network node 16 may also decide to choose different values ​​for different wireless devices 22 to gain scheduling flexibility.Alternatively, if a specific paradigm is to be used, such as multiple users, multiple inputs, multiple outputs (MU-MIMO), where network node 16 can serve different wireless devices 22 at the same time, network node 16 may need to align parameters to avoid possible misalignments between different wireless devices 22. Wireless Device 22 can be expected to switch from cross-interval mode to same-interval mode after an application delay has elapsed. Depending on other underlying conditions, Wireless Device 22 may choose an appropriate power-saving mode. For example, if cross-carrier scheduling is used and Wireless Device 22 does not need to buffer the PDSCH for at least minK, Wireless Device 22 may achieve greater power savings if the application delay is longer than minK. Therefore, Wireless Device 22 may adjust its power-saving strategy accordingly and consider powering down additional modules beyond those determined based on minK to achieve even greater savings. In some modes, network node 16 can increase the application delay of the new minK to prevent misalignment, particularly when transitioning from a larger to a smaller minK value (or alternatively, transitioning from CS mode, where minK is enabled, to same interval mode, where minK is disabled). The additional delay can be, for example, cX, where c is an integer and X is the application delay obtained through any of the methods described above. The decision to implement the additional delay can be based, for example, on the channel quality. For instance, if the channel quality is below a certain threshold, the additional delay is implemented. Conversely, when the channel quality is above a certain threshold, the additional delay is not implemented. In the methods described above, the application delay of the new minK is calculated using the BWP numerology of the scheduled CC. Alternatively, it is also possible to calculate the application delay of the new-minK value using the BWP numerology of the scheduled CC. This can be done by multiplying the application delay obtained from the previous methods by the ratio between the BWP numerology of the scheduled CC and the BWP numerology of the scheduled CC. In the methods described above, it can be assumed that network node 16 and wireless device 22 agree on the Z value in a reference PDCCH monitoring case (e.g., PDCCH monitoring case 1-1). If wireless device 22 and network node 16 can mutually understand that the other PDCCH monitoring case will be used during transmission, they can agree on the Z value (which may be different from the Z value when using PDCCH monitoring case 1-1) in advance. In this case, the parameter 'a' can be omitted from the methods above and / or the formula. ancefrn / zznz / q / uιλι According to one aspect, some modalities include a method for determining a new minK application delay that includes factors such as one or more of: • minimalSchedulingOffset configured for the scheduled CC BWP; • the numerology of the BWP of the programmer CC and the BWP of the programmed CC; • Additional factor related to the PDCCH monitoring case; and / or • Minimum feasible application delay. According to one aspect, a network node 16 is configured to communicate with a wireless device 22. The network node 16 includes a radio interface 62 and / or a processing circuit 68 configured to determine an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode in which the minimum scheduling offset parameter is equal to zero, and optionally transmit the determined application delay to the wireless device 22. Accordingly, in some modes, the determined application delay is based at least in part on a type of physical downlink control (PDCCH) channel monitoring case. In some modes, the transmission also includes transmitting when to initiate cross-interval mode or same-interval mode. According to another aspect, a method implemented in a network node 16 includes determining, through the application delay determinator 32, an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode, in which the minimum scheduling offset parameter is equal to zero, and optionally transmitting the determined application delay to the wireless device 22. Accordingly, in some modes, the determined application delay is based at least in part on a type of physical downlink control channel (PDCCH) monitoring case. In some modes, the transmission also includes transmitting when to initiate cross-interval mode or same-interval mode. According to another aspect, a wireless device (wireless device 22) is configured to communicate with a network node 16. Wireless device 22 includes a radio interface 82 and / or a processing circuit 84 configured to receive an application delay from network node 16 and initiate a same-interval mode or a cross-interval mode depending on whether the application delay is zero or greater than zero. According to this aspect, wireless device 22, the radio interface, and the processing circuit are further configured to receive an indication of when to initiate the same-interval mode or the cross-interval mode. According to another aspect, a method implemented in a wireless device (wireless device 22) includes receiving, via radio interface 82, an application delay from network node 16 and initiating, via processing circuit 84, either a same-interval mode or a cross-interval mode depending on whether the application delay is zero or greater than zero. According to this aspect, in some modes, the method further includes receiving an indication of when to initiate the same-interval mode or the cross-interval mode. Some options may include one or more of the following: Example A1. A network node configured to communicate with a wireless device, the network node configured to and / or comprising a radio interface and / or comprising processing circuitry configured to: ancefrn / zznz / q / uli determine an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode in which the minimum scheduling offset parameter is equal to zero; and optionally, transmit the determined application delay to the wireless device. Example Ά2. The network node of Example Ά1, where the determined application delay is based, at least in part, on a type of physical downlink control channel (PDCCH) monitoring case. Example A3. The network node of Example A1, where the transmission also includes transmitting when to start cross-interval mode or same-interval mode. Example B1. A method implemented on a network node, where the method comprises: determine an application delay corresponding to the conversion between a cross-interval mode in which a minimum scheduling offset parameter is greater than zero and a same-interval mode in which the minimum scheduling offset parameter is equal to zero; and optionally, transmit the determined application delay to the wireless device. Example B2. The method of Example B1, wherein the determined application delay is based, at least in part, on a type of downlink physical control channel (PDCCH) monitoring case. Example B3. The method of example B1, where the transmission also includes transmitting when to start cross-interval mode or same-interval mode. Example Cl. A wireless device configured to communicate with a network node, configured and / or comprising a radio interface and / or processing circuitry configured to: receive an application delay from the network node; Start a same interval mode or a cross interval mode depending on whether the application delay is zero or greater than zero. Example C2. The wireless device of Example C1L, wherein the wireless device, radio interface, and processing circuitry are further configured to receive an indication of when to initiate same-interval mode or cross-interval mode. Example DI. A method implemented on a wireless device, wherein the method comprises: receive an application delay from the node of ancefrn / zznz / q / uli network; Start a same interval mode or a cross interval mode depending on whether the application delay is zero or greater than zero. Example D2. The method of example DI, which also includes receiving an indication of when to start the same interval mode or the cross interval mode. As anyone skilled in the art will appreciate, the concepts described herein can be incorporated as a method, a data processing system, a software product, and / or a computer storage medium that stores an executable software program. Consequently, the concepts described herein can take the form of a purely hardware implementation, a purely software implementation, or a combination of both, all of which are generally referred to herein as a circuit or module. Any process, step, action, and / or functionality described herein can be carried out and / or associated with a corresponding module, which can be implemented in software, firmware, and / or hardware.Furthermore, the invention may take the form of a computer program product on a tangible, computer-readable storage medium having computer program code embedded in the medium that can be executed by a computer. Any suitable tangible, computer-readable medium may be used, including hard drives, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices. Some modalities are described here with reference to flowchart illustrations and / or block diagrams of computer program methods, systems, and products. It is understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions.These computer program instructions can be provided to a processor of a general-purpose computer (to thereby create a special-purpose computer), a special-purpose computer, or other programmable data-processing apparatus to produce a machine, such that the instructions, being executed through the processor of the computer or other programmable data-processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or the block or blocks of the block diagram. These computer program instructions can also be stored in computer-readable memory or on a storage medium that can direct a computer or other programmable data-processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce a manufactured item that includes instruction means that implement the function / action specified in the flowchart and / or the block or blocks of the block diagram. Computer program instructions can also be loaded into a computer or other programmable data processing device to cause a series of operational steps to be carried out in the computer or other programmable device to produce a computer-implemented process in such a way that the instructions executed in the computer or other programmable devices provide steps to implement the functions / acts specified in the flowchart and / or the block or blocks of the block diagram. It should be understood that the functions / actions described in the blocks may occur outside the order shown in the operational illustrations. For example, two blocks shown in succession may, in fact, execute substantially at the same time, or, on occasion, the blocks may execute in the reverse order, depending on the functionality / actions involved. ancefrn / zznz / q / uιλι Although some of the diagrams include arrows on the communication routes to show a main direction of communication, it should be understood that communication can occur in the opposite direction to the arrows depicted. The computer program code for carrying out the operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java®, or Cf+. However, the computer program code for carrying out the operations of the invention may also be written in conventional procedural programming languages, such as the C programming language. The program code may be executed entirely on the user's computer, partly on the user's computer (such as a standalone software package), partly on the user's computer and partly on a remote computer, or entirely on the remote computer.In the last scenario, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (e.g., via the Internet using an Internet service provider). This document describes many different modalities, in relation to the preceding description and drawings. It would be unduly repetitive and confusing to describe and illustrate verbatim every combination and subcombination of these modalities. Accordingly, all modalities may be combined in any way and / or combination, and this descriptive memorandum, including the drawings, shall be construed as a complete written description of all combinations and subcombinations of the modalities described herein, and of the manner and process of manufacturing and using them, and shall support claims for such combination or subcombination. Those skilled in the art will appreciate that the embodiments described herein are not limited to what has been shown and described in particular herein. Furthermore, unless otherwise stated above, it should be noted that all accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the foregoing teachings without departing from the scope of the following claims.

Claims

1. A method carried out by a network node (16) for the transition between a first minimum scheduling offset and a second minimum scheduling offset in which various numerologies are applied, the method comprising: determining (S142) an application delay based at least partly on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of scheduling component carrier in which the application delay is associated with at least one of the first and second minimum scheduling offsets.

2. The method according to claim 1, wherein determining the application delay comprises: determining the application delay based further on the first minimum scheduling offset, wherein the first minimum scheduling offset is a currently applied minimum scheduling offset.

3. The method according to any of claims 1 and 2, wherein the application delay corresponds to the conversion between a second programming mode and a first programming mode, wherein the first and second programming modes differ at least in their respective minimum programming offset.

4. The method according to claim 3, wherein the second programming mode is a cross-interval mode in which the minimum programming offset is greater than zero, and the first programming mode is a same-interval mode in which the minimum offset parameter is equal to zero.

5. The method according to any of claims 1-4, wherein determining the application delay for inter-carrier programming with mixed numerology comprises: when the first SCS associated with the programming component carrier BWP and a second inter-carrier separation, SCS, associated with a programmed component carrier BWP are different, determining a normalized value for the first minimum programming offset of the programmed component carrier BWP relative to the first SCS associated with the programming component carrier BWP.

6. The method according to claim 5, wherein the normalized value, minK', is determined by: 2^PDCCH minK' = minK-2 / ípdsch where minK is a currently applied minimum offset; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a scheduling physical downlink control channel, PDCCH; and qposcH is associated with the second SCS, wherein the second SCS is associated with a planned physical downlink shared channel, PDSCH.

7. The method according to any of claims 1-5, wherein determining the application delay comprises: determining a minimum feasible application delay, Z; and when an associated Physical Downlink Control Channel Monitoring (PDCCH) occasion comes after a specified symbol within an interval, increasing the minimum feasible application delay by a specified amount.

8. The method according to claim 7, wherein the specific quantity is 1 interval.

9. The method according to any of claims 1-4, wherein determining the application delay comprises: determining a minimum offset currently applied as the application delay based at least in part on the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programming component carrier BWP.

10. The method according to any of claims 1-9, further comprising: transmitting an indication of the determined application delay to a wireless device (22).

11. The method according to any of claims 1-10, wherein the determined application delay indicates when to start applying the second minimum scheduling offset after a wireless device (22) receives a change indication, wherein the change indication indicates that a new minimum scheduling offset should be applied.

12. The method according to any of claims 1-11, wherein determining the application delay comprises: determining the application delay based, at least in part, on a minimum offset currently applied in the programming component carrier BWP, a minimum feasible application delay, Z, of the programming component carrier BWP, the first SCS associated with the programming component carrier BWP, and a second subcarrier separation, SCS, associated with a programmed component carrier BWP.

13. The method according to any of claims 1-12, wherein the determined application delay is based at least in part on a case type of physical downlink control channel monitoring, PDCCH.

14. A method carried out by a wireless device (22) for the transition between a first minimum scheduling offset and a second minimum scheduling offset in which various numerologies are applied, the method comprising: receiving (S144) an indication of an application delay from a network node (16), wherein the application delay is based at least partly on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of programming component carrier, and the application delay being associated with at least one of the first and second minimum scheduling offsets; and beginning (S146) to apply the second minimum offset based at least partly on the received application delay.

15. The method according to claim 14, wherein the application delay is further based, at least in part, on the first minimum compensation, wherein the first minimum compensation is a currently applied minimum compensation.

16. The method according to any of claims 14 and 15, wherein the application delay corresponds to the conversion between a second programming mode and a first programming mode, wherein the first and second programming modes differ at least in their respective minimum programming offset.

17. The method according to claim 16, wherein the second programming mode is a cross-interval mode in which the minimum programming offset is greater than zero, and the first programming mode is a same-interval mode in which the minimum offset parameter is equal to zero.

18. The method according to any of claims 14-17, wherein: the application delay is for inter-carrier programming with mixed numerology; and when the first SCS associated with the programming component carrier BWP and a second subcarrier separation SCS associated with a component of the programmed carrier BWP are different, the application delay is further based, at least in part, on a normalized value for the first minimum programming offset of the programmed component carrier BWP relative to the first SCS associated with the programming component carrier BWP.

19. The method according to claim 18, wherein the normalized value, minK', is determined by: 2APDCCH minK' = minK-2ZíPDSCH where minK is a currently applied minimum offset; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a scheduling physical downlink control channel, PDCCH; and Ppdsch is associated with the second SCS, wherein the second SCS is associated with a planned physical downlink shared channel, PDSCH.

20. The method according to any of claims 14-18, wherein: the application delay is based, at least in part, on a minimum feasible application delay, Z; and when an associated physical downlink control channel monitoring occasion, PDCCH, comes after a specified symbol within an interval, the minimum feasible application delay is increased by a specified amount.

21. The method according to claim 20, wherein the specific quantity is 1 interval.

22. The method according to any of claims 14-17, wherein the application delay is a minimum offset currently applied based at least in part on the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programmed component carrier BWP.

23. The method according to any of claims 14-22, wherein the application delay indicates when to start applying the second minimum scheduling offset after a wireless device (22) receives a change indication, wherein the change indication indicates that a new minimum scheduling offset should be applied.

24. The method according to claim 23, further comprising: receiving the change indication via a downlink control information (DCI) message.

25. The method according to any of claims 14-24, wherein the application delay is based, at least in part, on a minimum offset currently applied in the programmed component carrier BWP, a minimum feasible application delay, Z, of the programming component carrier BWP, the first SCS associated with the programming component carrier BWP, and a second subcarrier separation, SCS, associated with a programmed component carrier BWP.

26. The method according to any of claims 14-25, wherein the application delay is based, at least in part, on a physical downlink control channel monitoring case type, PDCCH.

27. A network node (16) for the transition between a first minimum offset and a second minimum offset in which various numerologies are applied, wherein the network node (16) comprises a processing circuit (68), the processing circuit (68) configured to cause the network node (16): to determine an application delay based at least partly on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of programming component carrier, wherein the application delay is associated with at least one of the first and second minimum programming offsets.

28. The network node (16) according to claim 27, wherein the processing circuit (68) is configured to carry out any of the methods of claims 2 to 13.

29. A wireless device (22) for the transition between a first minimum offset and a second minimum offset in which various numerologies are applied, wherein the wireless device (22) comprises a processing circuit (84), the processing circuit (84) configured to cause the wireless device (22): to receive an indication of an application delay from a network node (16), the application delay being based at least partly on a first subcarrier separation, SCS, associated with a bandwidth portion, BWP, of programming component carrier, and the application delay being associated with at least one of the first and second minimum programming offsets; and to begin applying the second minimum offset based, at least partly, on the received application delay.

30. The wireless device (22) according to claim 29, wherein the application delay is further based, at least in part, on the first minimum compensation, wherein the first minimum compensation is a currently applied minimum compensation.

31. The wireless device (22) according to any of claims 29 and 30, wherein the application delay corresponds to the conversion between a second programming mode and a first programming mode, the first and second programming modes being different at least in their respective minimum programming offset.

32. The wireless device (22) according to claim 31, wherein the second programming mode is a cross-interval mode in which the minimum programming offset is greater than zero, and the first programming mode is a same-interval mode in which the minimum programming offset parameter is equal to zero.

33. The wireless device (22) according to any of claims 29-32, wherein: the application delay is for programming between carriers with a mixed numerology; and when the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, associated with a programmed component carrier BWP are different, the application delay is further based, at least in part, on a normalized value for the first minimum programming offset of the programmed component carrier BWP relative to the first SCS associated with the programming component carrier BWP.

34. The wireless device (22) according to claim 33, wherein the normalized value, minK', is determined by: 2AíPDCCH min / U — min / C · -----2Aípdsch wherein minK is a minimum offset currently applied; Ppdcch is associated with the first SCS, wherein the first SCS is associated with a scheduling physical downlink control channel, PDCCH; and úpdsch is associated with the second SCS, wherein the second SCS is associated with a planned physical downlink shared channel, PDSCH.

35. The wireless device (22) according to any of claims 29-32, wherein: the application delay is based, at least in part, on a minimum feasible application delay, Z; and when an associated physical downlink control channel monitoring occasion, PDCCH, comes after a specified symbol within an interval, the minimum feasible application delay is increased by a specified amount.

36. The wireless device (22) according to claim 35, wherein the specified quantity is 1 interval.

37. The wireless device (22) according to any of claims 29-32, wherein the application delay is a minimum offset currently applied based, at least in part, on the first SCS associated with the programming component carrier BWP and a second subcarrier separation, SCS, ancefrn / zznz / q / uli associated with a programmed component carrier BWP.

38. The wireless device (22) according to any of claims 29-37, wherein the application delay indicates when to start applying the second minimum scheduling offset after a wireless device (22) receives a change indication, wherein the change indication indicates to apply a new minimum scheduling offset.

39. The wireless device (22) according to claim 38, wherein the processing circuit (84) is further configured to cause the network node (16): to receive the change indication via a downlink control information (DCI) message.

40. The wireless device (22) according to any of claims 29-39, wherein the application delay is based, at least in part, on a minimum scheduling offset currently applied in the programmed component carrier BWP, a feasible minimum application delay, Z, of the programming component carrier BWP, the first SCS associated with the programming component carrier BWP, and a second subcarrier separation, SCS, associated with a programmed component carrier BWP.

41. The wireless device (22) conforming to any of claims 29-40, wherein the application delay is based, at least in part, on a type of physical downlink control channel monitoring case, PDCCH.

Images