CN113287360B - Selective cross-slot scheduling for NR user equipment - Google Patents

Abstract

Embodiments include a method performed by a User Equipment (UE) for communicating with a network node in a Radio Access Network (RAN). The method comprises the following steps: an indication is received from a network node that a minimum scheduling offset between a scheduling Physical Downlink Control Channel (PDCCH) and a signal or channel scheduled via the scheduling PDCCH will change after a first duration. The method further comprises: then during a first duration, monitoring a scheduling PDCCH based on a first operational configuration; and monitoring the scheduling PDCCH based on the second operating configuration in response to the end of the first duration. The first duration may relate to a time required for the UE to switch from the first operating configuration to the second operating configuration. Embodiments also include a UE configured to perform such a method.

Description

Selective inter-slot scheduling for NR user equipment

Technical Field

The present invention relates generally to wireless communication networks and, in particular, to improvements in power consumption of wireless devices (also referred to as user equipment or UE) operating in wireless communication networks.

Background technique

Generally, all terms used in this article will be interpreted according to their common meaning in the relevant technical field, unless different meanings are clearly given and/or different meanings are implied in the context of using it. Unless otherwise clearly stated, all references to elements, devices, components, methods, steps, etc. will be openly interpreted as referring to at least one instance of elements, devices, components, methods, steps, etc. The steps of any method disclosed herein are not necessarily performed in the exact order disclosed, unless the steps are clearly described as after or before another step and/or imply that the steps must be after or before another step. As long as it is appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. According to the following description, other purposes, features and advantages of the disclosed embodiments will be obvious.

Long Term Evolution (LTE) is an umbrella term for the so-called fourth generation (4G) radio access technologies developed within the 3rd Generation Partnership Project (3GPP) and initially standardized in Release 8 (Rel-8) and Release 9 (Rel-9), also known as Evolved UTRAN (E-UTRAN). LTE targets various licensed frequency bands and is accompanied by improvements to non-radio aspects, often referred to as System Architecture Evolution (SAE), which includes an Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases.

3GPP LTE Release 10 (Rel-10) supports bandwidths greater than 20MHz. An important requirement for Rel-10 is to ensure backward compatibility with LTE Release 8. This should also include spectrum compatibility. Therefore, a broadband LTE Rel-10 carrier (e.g., wider than 20MHz) should appear as multiple carriers to a LTE Rel-8 ("legacy") terminal. Each such carrier may be referred to as a component carrier (CC). In order to effectively use the wide carrier for legacy terminals as well, legacy terminals may be scheduled in all parts of a broadband LTE Rel-10 carrier. An exemplary way to achieve this is by means of carrier aggregation (CA), whereby a Rel-10 terminal can receive multiple CCs, each CC preferably having the same structure as a Rel-8 carrier. Similarly, one of the enhancements in LTE Rel-11 is an enhanced physical downlink control channel (ePDCCH), which has the goal of increasing capacity and improving spatial multiplexing of control channel resources, improving inter-cell interference coordination (ICIC), and supporting antenna beamforming and/or transmit diversity for control channels.

FIG1 shows an overall exemplary architecture of an LTE network. E-UTRAN 100 includes one or more evolved Node Bs (eNBs), such as eNBs 105, 110, and 115, and one or more user equipments (UEs), such as UE 120. As used within the 3GPP specifications, "user equipment" (or "UE") may refer to any wireless communication device (e.g., a smartphone or computing device) capable of communicating with network equipment compatible with 3GPP standards (which, in some cases, includes E-UTRAN and earlier generation RANs (e.g., UTRAN/"3G" and/or GERAN/"2G") as well as later generation RANs).

As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic resource allocation to UEs in uplink (UL) and downlink (DL), as well as security of communications with UEs. These functions reside in eNBs (such as eNBs 105, 110, and 115), which communicate with each other via an X2 interface. The eNB is also responsible for the E-UTRAN interface to EPC 130, specifically, the S1 interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW) (shown collectively as MME/S-GW 134 and 138 in FIG. 1).

Typically, the MME/S-GW handles the overall control of the UE and the data flow between the UE (such as UE 120) and the rest of the EPC. More specifically, the MME handles the signaling (e.g., control plane CP) protocol between the UE and the EPC 130, which is called the non-access stratum (NAS) protocol. The S-GW handles all Internet Protocol (IP) data packets (e.g., user plane UP) between the UE and the EPC 130, and serves as a local mobility anchor point for data bearers when the UE moves between eNBs (such as eNBs 105, 110, and 115).

The EPC 130 may also include a Home Subscriber Server (HSS) 131, which manages user-related information and subscriber-related information. The HSS 131 may also provide support functions in mobility management, call and session setup, user authentication, and access authorization. The functions of the HSS 131 may be related to the functions of the traditional Home Location Register (HLR) and Authentication Center (AuC) functions or operations.

In some embodiments, HSS 131 may communicate with a user data repository (UDR) (labeled as EPC-UDR 135 in FIG. 1 ) via a Ud interface. EPC-UDR 135 may store user credentials after they have been encrypted by an AuC algorithm. These algorithms are not standardized (i.e., are vendor-specific) such that the encrypted credentials stored in EPC-UDR 135 are not accessible by any other vendor other than the vendor of HSS 131.

FIG. 2A shows a high-level block diagram of an exemplary LTE architecture divided into an access stratum (AS) and a non-access stratum (NAS) according to its constituent entities (UE, E-UTRAN, and EPC) and high-level functions. FIG. 2A also shows two specific interface points, namely, Uu (UE/E-UTRAN radio interface) and S1 (E-UTRAN/EPC interface), each using a specific set of protocols (i.e., radio protocols and S1 protocols). Although not shown in FIG. 2A, each protocol set can be further divided into user plane and control plane protocol functions. The user plane and the control plane are also referred to as the U-plane and the C-plane, respectively. On the Uu interface, the U-plane carries user information (e.g., data packets), while the C-plane carries control information between the UE and the E-UTRAN.

FIG. 2B shows a block diagram of an exemplary C-plane protocol stack between a UE, an eNB, and an MME. The exemplary protocol stack includes a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer between the UE and the eNB. The PHY layer is related to how and what characteristics are used to transmit data through a transport channel on an LTE radio interface. The MAC layer provides data transmission services on logical channels, maps logical channels to PHY transport channels, and reallocates PHY resources to support these services. The RLC layer provides error detection and/or correction, concatenation, segmentation, reorganization, and reordering of data transmitted to or from an upper layer. The PHY layer, the MAC layer, and the RLC layer perform the same functions for both the U-plane and the C-plane. The PDCP layer provides encryption/decryption and integrity protection for both the U-plane and the C-plane, and provides other functions for the U-plane, such as header compression. The exemplary protocol stack also includes a non-access stratum (NAS) signaling between the UE and the MME.

FIG2C shows a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY layer. The interface between the layers is provided by service access points (SAPs), which are indicated by ovals in FIG2C. As described above, the PHY layer interfaces with the MAC and RRC protocol layers. In the figure, the PHY, MAC, and RRC are also referred to as layers 1-3, respectively. The MAC provides different logical channels (also as described above) to the RLC protocol layer, characterized by the type of information being transmitted, whereas the PHY provides the MAC with transport channels, characterized by how the information is transmitted over the radio interface. In providing this transport service, the PHY performs various functions, including: error detection and correction; rate matching and mapping of the encoded transport channels to the physical channels; power weighting, modulation, and demodulation of the physical channels; transmit diversity; and beamforming multiple-input multiple-output (MIMO) antenna processing. The PHY layer also receives control information (e.g., commands) from the RRC and provides various information to the RRC, such as radio measurement results.

In general, a physical channel corresponds to a set of resource elements that carry information from higher layers. The downlink (i.e., eNB to UE) physical channels provided by LTE PHY include the physical downlink shared channel (PDSCH), physical multicast channel (PMCH), physical downlink control channel (PDCCH), relay physical downlink control channel (R-PDCCH), physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), and physical hybrid ARQ indicator channel (PHICH). In addition, the LTE PHY downlink includes various reference signals (e.g., channel state information reference signal CSI-RS), synchronization signals, and discovery signals.

The PDSCH is the primary physical channel used for unicast downlink data transmission and for transmission of RAR (Random Access Response), specific system information blocks, and paging information. The PBCH carries basic system information required for the UE to access the network. The PDCCH is used to send downlink control information (DCI), including scheduling information for DL messages on the PDSCH, grants for UL transmissions on the PUSCH, and channel quality feedback (e.g., CSI) for UL channels. The PHICH carries HARQ feedback (e.g., ACK/NAK) for UL transmissions of the UE.

The uplink (i.e., UE to eNB) physical channels provided by the LTE PHY include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). In addition, the LTE PHY uplink includes various reference signals, including: a demodulation reference signal (DM-RS), which is sent to assist the eNB in receiving the associated PUCCH or PUSCH; and a sounding reference signal (SRS), which is not associated with any uplink channel.

PUSCH is the uplink counterpart of PDSCH. PUCCH is used by UE to send uplink control information (UCI), including HARQ feedback for eNB DL transmission, channel quality feedback for DL channels (e.g., CSI), scheduling request (SR), etc. PRACH is used for random access preamble transmission.

As briefly mentioned above, the LTE RRC layer (shown in Figures 2B-C) controls the communication between the UE and the eNB at the radio interface and the mobility of the UE between cells in the E-UTRAN. Typically, after the UE is powered on, it will be in the RRC_IDLE state until an RRC connection is established with the network, at which point it will transition to the RRC_CONNECTED state where data transfer can occur. After the connection is released, the UE returns to RRC_IDLE. In the RRC_IDLE state, the UE's receiver is active on a discontinuous reception (DRX) schedule configured by upper layers. During the DRX activation period, the RRC_IDLE UE receives system information (SI) broadcast by the serving cell, performs measurements of neighboring cells to support cell reselection, and monitors paging from the EPC via the eNB on the paging channel on the PDCCH. The RRC_IDLE UE is known in the EPC and has an assigned IP address, but it is unknown to the serving eNB (e.g., there is no stored context). In LTE Rel-13, a mechanism was introduced whereby the UE is placed in a suspended state by the network similar to RRC_IDLE, but with certain advantages of transitioning back to RRC_CONNECTED.

The multiple access scheme for LTE PHY is based on orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) in the downlink and single carrier frequency division multiple access (SC-FDMA) with a cyclic prefix in the uplink. To support transmission in paired and unpaired spectrum, LTE PHY supports both frequency division duplex (FDD) (including both full-duplex and half-duplex operation) and time division duplex (TDD). Figure 3A shows an exemplary radio frame structure ("Type 1") for LTE FDD downlink (DL) operation. The DL radio frame has a fixed duration of 10 ms and includes 20 time slots labeled 0 to 19, each time slot having a fixed duration of 0.5 ms. A 1 ms subframe includes two consecutive time slots, for example, subframe i includes time slots 2i and 2i+1. Each FDD DL time slot includes N ^DL _symb OFDM symbols, where each OFDM symbol includes N _sc OFDM subcarriers. Example values of N ^DL _symb may be 7 (with normal CP) or 6 (with extended length CP) for a subcarrier spacing (SCS) of 15 kHz. The value of N _sc is configurable based on the available channel bandwidth. Since those skilled in the art are familiar with the principles of OFDM, further details are omitted in this specification.

As shown in FIG. 3A , the combination of a particular subcarrier in a particular symbol is called a resource element (RE). Each RE is used to send a specific number of bits according to the type of modulation and/or bit mapping constellation used for the RE. For example, some REs may carry two bits using QPSK modulation, while other REs may carry four or six bits using 16-QAM or 64-QAM, respectively. The radio resources of LTE PHY are also defined in terms of physical resource blocks (PRBs). A PRB spans N ^RB _sc subcarriers during the duration of a slot (i.e., N ^DL _symb symbols), where N ^RB _sc is typically 12 (using a 15kHz subcarrier bandwidth) or 24 (7.5kHz bandwidth). A PRB that spans the same N ^RB _sc subcarriers during the entire subframe (i.e., 2N ^DL _symb symbols) is called a PRB pair. Therefore, the resources available in a subframe of LTE PHY DL include N ^DL _RB PRB pairs, each of which includes 2N ^DL _symb ·N ^RB _sc REs. For normal CP and 15KHz SCS, a PRB pair includes 168 REs.

One exemplary characteristic of PRBs is that consecutively numbered PRBs (e.g., PRB _i and PRB _i+1 ) include consecutive subcarrier blocks. For example, with normal CP and 15KHz subcarrier bandwidth, PRB ₀ includes subcarriers 0 to 11, and PRB ₁ includes subcarriers 12 to 23. LTE PHY resources can also be defined in terms of virtual resource blocks (VRBs), which have the same size as PRBs, but can be of a centralized type or a distributed type. Centralized VRBs can be mapped directly to PRBs so that VRB n _VRB corresponds to PRB n _PRB = n _VRB . On the other hand, distributed VRBs can be mapped to non-contiguous PRBs according to various rules, as described in 3GPP TS 36.213 or otherwise known to those of ordinary skill in the art. However, the term "PRB" should be used in this disclosure to refer to both physical resource blocks and virtual resource blocks. In addition, unless otherwise specified, the term "PRB" will be used from now on to refer to resource blocks for the duration of a subframe, i.e., PRB pairs.

Figure 3B shows an exemplary LTE FDD uplink (UL) radio frame configured in a similar manner to the exemplary FDD DL radio frame shown in Figure 3 A. Using terminology consistent with the DL description above, each UL slot includes N ^UL _symb OFDM symbols, each of which includes N _sc OFDM subcarriers.

LTE PHY maps various DL and UL physical channels to the resources shown in Figures 3A and 3B, respectively. Both PDCCH and PUCCH can be transmitted on an aggregation of one or several consecutive control channel elements (CCEs), and CCEs are mapped to physical resources based on resource element groups (REGs), each of which includes multiple REs.

Figure 4 shows an exemplary technique for mapping CCEs and REGs to physical resources (e.g., PRBs). As shown in Figure 4, REGs including CCEs for the PDCCH may be mapped into the first n symbols of a subframe, while the remaining symbols may be used for other physical channels carrying user data, such as the PDSCH or PUSCH. Typically, n=1-4 and is communicated to the UE via a control format indication (CFI) carried by the PCFICH in the first symbol of the control region. In the arrangement of Figure 4, n=3. Each REG includes four REs (represented by small dashed rectangles), and each CCE includes nine (9) REGs. Although Figure 4 shows two CCEs, the number of CCEs may vary depending on the required PDCCH capacity, which may be determined based on the number of users, the number of measurements, and/or control signaling, among other things. On the uplink, the PUCCH may be similarly configured.

Research projects on the new radio interface for 5G have been completed, and 3GPP is now standardizing this new radio interface, often abbreviated as NR (New Radio). While LTE was primarily designed for user-to-user communications, 5G/NR networks are designed to support both high single-user data rates (e.g., 1 Gb/s) and massive machine-to-machine communications involving short burst transmissions from many different devices sharing a frequency bandwidth.

NR shares many similarities with LTE. For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and uses both CP-OFDM and DFT-Spread OFDM (DFT-S-OFDM) in the UL. As another example, in the time domain, the NR DL and UL physical resources are organized into equal-sized 1ms subframes. The subframes are further divided into a plurality of slots of equal duration, where each slot includes a plurality of OFDM-based symbols. As another example, the NR RRC layer includes an RRC_IDLE state and an RRC_CONNECTED state, but adds an additional state called RRC_INACTIVE, which has some characteristics similar to the suspension conditions of LTE.

In the RRC_CONNECTED state, the UE monitors the PDCCH for scheduled PDSCH/PUSCH and other purposes. In LTE, depending on the discontinuous reception (DRX) configuration, the UE may spend a large portion of its energy decoding the PDCCH without detecting the PDSCH/PUSCH scheduled for it. If a DRX setting similar to traffic modeling is used, the situation is similar in NR, as the UE will need to perform blind detection to identify whether there is a PDCCH targeted at it. Therefore, techniques that can reduce unnecessary PDCCH monitoring, allow the UE to go to sleep more frequently, and/or allow the UE to wake up less frequently can be beneficial.

Summary of the invention

Embodiments of the present disclosure provide certain improvements to communications between user equipment (UE) and network nodes in a wireless communication network, such as by prompting solutions to overcome the exemplary problems described above.

Some exemplary embodiments of the present disclosure include methods (e.g., processes) for managing energy consumption of a user equipment (UE) in connection with communications with a network node in a radio access network (RAN). These exemplary methods may be performed by a user equipment (UE, e.g., a wireless device, an IoT device, a modem, etc., or a component thereof) communicating with a network node (e.g., a base station, an eNB, a gNB, etc., or a component thereof) in a RAN (e.g., an E-UTRAN, a NG-RAN).

These exemplary methods may include receiving an indication from a network node that a minimum scheduling offset will change after a first duration. The minimum scheduling offset may be between a scheduling PDCCH and a signal or channel scheduled via the scheduling PDCCH. In some embodiments, the first duration may be related to a time required for the UE to switch from the first operating configuration to the second operating configuration. In some embodiments, the first operating configuration may consume less energy than the second operating configuration.

In other embodiments, the first duration may be based on an initial scheduled PDCCH for the UE after receiving the indication; or based on an initial plurality of scheduled PDCCHs for the UE after receiving the indication.

In other embodiments, the first duration may include a second plurality of PDCCH monitoring opportunities associated with the UE during one of: after receiving the indication; or a third plurality of PDCCH monitoring opportunities associated with the UE after receiving the indication, wherein the third plurality is greater than the second plurality.

In some embodiments, these exemplary methods may further include: sending an indication of a processing time required for PDCCH decoding to the network node. In such embodiments, the received indication may identify a minimum scheduling offset applicable after the first duration ends that is greater than or equal to the indicated processing time.

In some embodiments, these example methods may further include: receiving a configuration message from the network node identifying one or more candidate scheduling offsets. In such embodiments, the received indication may identify one of the candidate scheduling offsets as a minimum scheduling offset applicable after the first duration ends. In some embodiments, the configuration message may be a radio resource control (RRC) message, and the indication may be received via a medium access control (MAC) control element (CE) or a physical layer (PHY) downlink control information (DCI).

These exemplary methods may also include: subsequently during the first duration, monitoring the scheduling PDCCH based on the first operating configuration. These exemplary methods may also include: in response to the end of the first duration, monitoring the scheduling PDCCH based on the second operating configuration. In some embodiments, the first operating configuration and the second operating configuration may differ in one or more of the following parameters: the proportion of time spent in sleep mode; the portion of bandwidth used; and the number of receive chains used.

In some embodiments, these example methods may further include: during monitoring based on the first operating configuration, detecting a scheduling signal or channel for a first scheduling PDCCH for the UE; and sending or receiving the signal or channel at a first scheduling offset after the first scheduling PDCCH.

In some embodiments, these example methods may further include: during monitoring based on the second operating configuration, detecting a scheduling signal or channel for a second scheduling PDCCH for the UE; and sending or receiving the signal or channel at a second scheduling offset after the second scheduling PDCCH.

In some embodiments, the first scheduling offset (e.g., applicable during the first duration) is greater than the second scheduling offset (e.g., applicable at the end of the first duration). In some of these embodiments, the second scheduling offset may include zero or more symbols in the same time slot as the second scheduled PDCCH, and the first scheduling offset includes one or more time slots or one or more symbols in the same time slot (e.g., relative to the first scheduled PDCCH occurring during the first duration). In other of these embodiments, the second scheduling offset includes one or more time slots after the second scheduled PDCCH, and the first scheduling offset includes two or more time slots (e.g., relative to the first scheduled PDCCH occurring during the first duration).

In various embodiments, one of the following may apply:

The signal or channel is a physical downlink shared channel (PDSCH) and the first scheduling offset is K0;

The signal or channel is a Physical Uplink Shared Channel (PUSCH) and the first scheduling offset is K2; or

• The signal or channel is a channel state information reference signal (CSI-RS), and the first scheduling offset is an aperiodic triggering offset.

Other exemplary embodiments of the present disclosure include methods (e.g., processes) for managing UE energy consumption with respect to communications between a user equipment (UE) and a network node. These exemplary methods may be performed by a network node (e.g., a base station, eNB, gNB, etc., or a component thereof) of a radio access network (RAN, e.g., E-UTRAN, NG-RAN) communicating with a user equipment (UE, e.g., a wireless device, an IoT device, a modem, etc., or a component thereof).

These exemplary methods may include sending an indication to the UE that the minimum scheduling offset will change after a first duration. The minimum scheduling offset may be between a scheduling PDCCH and a signal or channel scheduled via the scheduling PDCCH. In some embodiments, the first duration may be related to a time required for the UE to switch from the first operating configuration to the second operating configuration. In some embodiments, when the UE is configured with the first operating configuration, the UE consumes less energy than when configured with the second operating configuration.

In other embodiments, the first duration may be based on an initial scheduled PDCCH for the UE after the indication is sent; or based on an initial plurality of scheduled PDCCHs for the UE after the indication is sent.

In other embodiments, the first duration may include a second plurality of PDCCH monitoring opportunities associated with the UE during one of: after sending the indication; or a third plurality of PDCCH monitoring opportunities associated with the UE after sending the indication, wherein the third plurality is greater than the second plurality.

In some embodiments, these exemplary methods may further include receiving an indication of a processing time required for PDCCH decoding from the UE. In such embodiments, the transmitted indication may identify a minimum scheduling offset applicable after the first duration ends that is greater than or equal to the indicated processing time.

In some embodiments, these example methods may further include: sending a configuration message to the UE identifying one or more candidate scheduling offsets. In such embodiments, the sent indication may identify one of the candidate scheduling offsets as a minimum scheduling offset applicable after the first duration ends. In some embodiments, the configuration message may be a radio resource control (RRC) message, and the indication may be sent via a medium access control (MAC) control element (CE) or a physical layer (PHY) downlink control information (DCI).

The exemplary methods may also include sending a scheduling signal or channel to the UE for a scheduled PDCCH of the UE. The scheduled PDCCH may be sent after an indication that the minimum scheduling offset will change after the first duration. The exemplary methods may also include determining the scheduling offset based on whether the scheduled PDCCH is sent during the first duration or after the first duration. The exemplary methods may also include sending or receiving a signal or channel at the determined scheduling offset after the scheduled PDCCH.

In some embodiments, determining the scheduling offset may include: selecting a first scheduling offset if the scheduled PDCCH is transmitted during the first duration; and selecting a second scheduling offset if the scheduled DPCCH is transmitted after the first duration.

In some embodiments, the first scheduling offset (e.g., applicable during the first duration) is greater than the second scheduling offset (e.g., applicable at the end of the first duration). In some of these embodiments, the second scheduling offset may include zero or more symbols in the same time slot as the second scheduled PDCCH, and the first scheduling offset includes one or more time slots or one or more symbols in the same time slot (e.g., relative to the first scheduled PDCCH occurring during the first duration). In other of these embodiments, the second scheduling offset includes one or more time slots after the second scheduled PDCCH, and the first scheduling offset includes two or more time slots (e.g., relative to the first scheduled PDCCH occurring during the first duration).

In various embodiments, one of the following may apply:

The signal or channel is a physical downlink shared channel (PDSCH) and the first scheduling offset is K0;

The signal or channel is a Physical Uplink Shared Channel (PUSCH) and the first scheduling offset is K2; or

• The signal or channel is a channel state information reference signal (CSI-RS), and the first scheduling offset is an aperiodic triggering offset.

Other embodiments include user equipment (UE, such as a wireless device, an IoT device, or a component thereof, such as a modem) and a network node (e.g., a base station, eNB, gNB, CU/DU, controller, etc.) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include a non-transitory computer-readable medium storing program instructions that, when executed by a processing circuit, configure such a network node or UE to perform operations corresponding to any of the exemplary methods described herein.

These and other aspects, features, benefits and/or advantages of embodiments of the present disclosure will become apparent after reading the following detailed description in light of the accompanying drawings briefly described below.

BRIEF DESCRIPTION OF THE DRAWINGS

1 is a high-level block diagram of an exemplary architecture of a Long Term Evolution (LTE) Evolved-UTRAN (E-UTRAN) and Evolved Packet Core (EPC) network as standardized by 3GPP.

2A is a high-level block diagram of an exemplary E-UTRAN architecture in terms of its constituent components, protocols, and interfaces.

2B is a block diagram of exemplary protocol layers for a control plane portion of a radio (Uu) interface between a user equipment (UE) and an E-UTRAN.

2C is a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY layer.

3A and 3B are block diagrams of exemplary downlink and uplink LTE radio frame structures, respectively, for frequency division duplex (FDD) operation.

FIG. 4 shows an example manner in which LTE CCEs and REGs may be mapped to physical resources.

FIG5 shows an exemplary time-frequency resource grid for a New Radio (NR) timeslot.

6A-6B illustrate two exemplary NR time slot configurations.

Figure 7 shows various timing offsets between PDCCH, PDSCH, PUSCH, HARQ and CSI-RS for NR.

8 shows a timing diagram illustrating exemplary UE discontinuous reception (DRX) operation.

9 illustrates various timing diagrams for the selective cross-slot scheduling mode of operation according to various embodiments of the present disclosure.

10 illustrates a flowchart of an exemplary method (eg, process) performed by a user equipment (UE, such as a wireless device, an MTC device, an NB-IoT device, a modem, etc. or a component thereof) according to various embodiments of the present disclosure.

Figure 11 shows a flowchart of an exemplary method (e.g., process) performed by a network node (e.g., base station, gNB, eNB, ng-eNB, etc. or a component thereof) in a radio access network (RAN, such as E-UTRAN, NG-RAN) according to various embodiments of the present disclosure.

FIG12 illustrates a high-level view of an exemplary 5G network architecture.

FIG. 13 is a block diagram of an exemplary wireless device or UE according to various embodiments of the present disclosure.

FIG. 14 is a block diagram of an exemplary network node according to various embodiments of the present disclosure.

15 is a block diagram of an exemplary network configured to provide over-the-top (OTT) data services between a host computer and a UE according to various embodiments of the present disclosure.

Detailed ways

Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art. In addition, the following terms are used throughout the description given below:

Radio node: As used herein, a “radio node” may be a “radio access node” or a “wireless device.”

Radio access node: As used herein, a "radio access node" (or equivalently, a "radio network node", "radio access network node" or "RAN node") may be any node in a radio access network (RAN) of a cellular communication network that operates to wirelessly send and/or receive signals. Some examples of radio access nodes include, but are not limited to, base stations (e.g., new radio (NR) base stations (gNBs) in 3GPP fifth generation (5G) NR networks or enhanced or evolved Node Bs (eNBs) in 3GPP LTE networks), base station distributed components (e.g., CUs and DUs), high power or macro base stations, low power base stations (e.g., micro base stations, pico base stations, femto base stations, or home base stations, etc.), integrated access backhaul (IAB) nodes, transmission points, remote radio units (RRUs or RRHs), and relay nodes.

Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a mobility management entity (MME), a serving gateway (SGW), a packet data network gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a service capability exposure function (SCEF), etc.

Wireless device: As used herein, a "wireless device" (or "WD" for short) is any type of device that accesses a cellular communication network (i.e., served by a cellular communication network) by wirelessly communicating with a network node and/or other wireless devices. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through the air to send and/or receive wireless signals. Unless otherwise specified, the term "wireless device" is used interchangeably with "user equipment" (or "UE" for short) herein. Some examples of wireless devices include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premise equipment (CPEs), mobile type communication (MTC) devices, Internet of Things (IoT) devices, vehicle-mounted wireless terminal devices, etc.

Network node: As used herein, a "network node" is any node that is part of a radio access network of a cellular communication network (e.g., the radio access node or equivalent names discussed above) or any node that is part of a core network (e.g., the core network node discussed above). Functionally, a network node is a device that is capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or devices in a cellular communication network to enable and/or wireless access to a wireless device and/or perform other functions (e.g., management) in the cellular communication network.

Note that the description herein focuses on 3GPP cellular communication systems, and therefore, 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems. In addition, although the term "cell" is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells, and therefore, the concepts described herein are equally applicable to both cells and beams.

As briefly mentioned above, techniques that can reduce unnecessary PDCCH monitoring, allow the UE to go to sleep more frequently, and/or allow the UE to wake up less frequently can be beneficial. This is discussed in more detail below.

While LTE is primarily designed for user-to-user communications, 5G (also referred to as "NR") cellular networks are designed to support both high single-user data rates (e.g., 1 Gb/s) and large-scale machine-to-machine communications involving short burst transmissions from many different devices sharing a frequency bandwidth. The 5G radio standard currently targets a wide variety of data services, including eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), and machine-type communications (MTC). These services may have different requirements and goals. For example, URLLC aims to provide data services with extremely strict error and delay requirements, e.g., error probabilities as low as 10 ^-5 or less, and end-to-end delays of 1 ms or less. For eMBB, the requirements on delay and error probability may be less stringent, while the required supported peak rates and/or spectral efficiency may be higher. In contrast, URLLC requires low latency and high reliability, but has less stringent data rate requirements.

In Rel-15 NR, a UE may be configured with up to four carrier bandwidth parts (BWPs) in the downlink, where a single downlink carrier BWP is active at a given time. A UE may be configured with up to four carrier BWPs in the uplink, where a single uplink carrier BWP is active at a given time. If the UE is configured with a supplementary uplink, the UE may be configured with up to four additional carrier BWPs in the supplementary uplink, where a single supplementary uplink carrier BWP is active at a given time.

Figure 5 shows an exemplary time-frequency resource grid for an NR timeslot. As shown in Figure 5, for a duration of a 14-symbol timeslot, a resource block (RB) includes a group of 12 consecutive OFDM subcarriers. Like in LTE, a resource element (RE) includes one subcarrier in a timeslot. Common RBs (CRBs) are numbered from 0 to the end of the system bandwidth. Each BWP configured for a UE has a common reference CRB 0 so that a specifically configured BWP can start at a CRB greater than zero. In this way, a UE can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g., 100 MHz), each BWP starting at a specific CRB, but only one BWP can be active for the UE at a given point in time.

Within a BWP, RBs are defined in the frequency domain and range from 0 to are numbered, where i is the index of the specific BWP used for the carrier. Similar to LTE, each NR resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval. NR supports various SCS values Δf=(15×2 ^μ )kHz, where μ∈(0,1,2,3,4) are called "parameter sets". Parameter set μ=0 (i.e., Δf=15kHz) provides the basic (or reference) SCS also used in LTE. The slot length is inversely related to the SCS or parameter set according to 1/2 ^μ ms. For example, for Δf=15kHz, there is one (1ms) slot per subframe, for Δf=30kHz, there are two 0.5ms slots per subframe, and so on. In addition, the RB bandwidth is directly related to the parameter set according to 2 ^μ *180kHz.

The following Table 1 summarizes the supported NR parameter sets and associated parameters. Different DL and UL parameter sets can be configured by the network.

Table 1

An NR slot may include 14 OFDM symbols for a normal cyclic prefix and 12 symbols for an extended cyclic prefix. FIG6A shows an exemplary NR slot configuration including 14 symbols, where the slot duration and symbol duration are denoted as _Ts and _Tsymb , respectively. In addition, NR includes type B scheduling, also known as "mini slots". These are shorter than slots, typically ranging from one symbol to one less than the number of symbols in the slot (e.g., 13 or 11), and can start at any symbol in the slot. Mini slots can be used if the transmission duration of a slot is too long and/or the occurrence of the next slot start (slot alignment) is too late. Applications of mini slots include unlicensed spectrum and delay-critical transmissions (e.g., URLLC). However, mini slots are not service-specific and can also be used for eMBB or other services.

FIG6B shows another exemplary NR slot structure including 14 symbols. In this arrangement, the PDCCH is restricted to a region containing a specific number of symbols and a specific number of subcarriers, referred to as a control resource set (CORESET). In the exemplary structure shown in FIG6B, the first two symbols contain the PDCCH, and each of the remaining 12 symbols contains a physical data channel (PDCH), i.e., PDSCH or PUSCH. However, depending on the specific CORESET configuration, the first two slots may also carry PDSCH or other information as needed.

A CORESET includes multiple RBs (i.e., multiples of 12 REs) in the frequency domain and 1-3 OFDM symbols in the time domain, as further defined in 3GPP TS 38.211 §7.3.2.2. A CORESET is functionally similar to a control region in an LTE subframe, such as shown in Figure 4. However, in NR, each REG includes all 12 REs of one OFDM symbol in an RB, while an LTE REG includes only four REs, as shown in Figure 4. Like in LTE, the CORESET time domain size can be indicated by the PCFICH. In LTE, the frequency bandwidth of the control region is fixed (i.e., for the total system bandwidth), while in NR, the frequency bandwidth of the CORESET is variable. CORESET resources can be indicated to the UE by RRC signaling.

The smallest unit used to define a CORESET is a REG, which spans one PRB in frequency and one OFDM symbol in time. In addition to the PDCCH, each REG contains a demodulation reference signal (DM-RS) to assist in the estimation of the radio channel on which the REG is transmitted. When sending a PDCCH, a precoder can be used to apply weights at the transmit antennas based on some knowledge of the radio channel before transmission. If the precoder used at the transmitter for the REG is the same, the channel estimation performance at the UE can be improved by estimating the channel over multiple REGs that are similar in time and frequency. To assist the UE in channel estimation, multiple REGs can be grouped together to form a REG bundle, and the REG bundle size for the CORESET (i.e., 2, 3, or 5 REGs) can be indicated to the UE. The UE can assume that any precoder used for the transmission of the PDCCH is the same for all REGs in the REG bundle.

The NR control channel element (CCE) consists of six REGs. These REGs can be continuous or distributed in frequency. When the REGs are distributed in frequency, the CORESET is considered to use an interleaved mapping of REGs to CCEs, while if the REGs are continuous in frequency, non-interleaved mapping is considered to be used. Interleaving can provide frequency diversity. Not using interleaving is beneficial for situations where knowledge of the channel allows the use of precoders in specific parts of the spectrum to improve the SINR at the receiver.

Similar to LTE, NR data scheduling is done on a per-slot basis. In each slot, the base station (e.g., gNB) sends downlink control information (DCI) through PDCCH, which indicates which UE is scheduled to receive data in that slot and which RBs will carry the data. The UE first detects and decodes the DCI, and if the DCI includes DL scheduling information for the UE, the UE receives the corresponding PDSCH based on the DL scheduling information. DCI formats 1_0 and 1_1 are used to convey PDSCH scheduling.

Likewise, the DCI on the PDCCH may include a UL grant indicating which UE is scheduled to send data on the PUCCH in the time slot and which RBs will carry the data. The UE first detects and decodes the DCI, and if the DCI includes an uplink grant for the UE, the UE sends the corresponding PUSCH on the resources indicated by the UL grant. DCI formats 0_0 and 0_1 are used to convey UL grants for PUSCH, while other DCI formats (2_0, 2_1, 2_2, and 2_3) are used for other purposes, including transmission of slot format information, reserved resources, transmit power control information, etc.

The DCI includes a payload supplemented with a cyclic redundancy check (CRC) of the payload data. Since the DCI is sent on the PDCCH received by multiple UEs, the identifier of the target UE needs to be included. In NR, this is done by scrambling the CRC with the Radio Network Temporary Identifier (RNTI) assigned to the UE. Most commonly, the cell RNTI (C-RNTI) assigned to the target UE by the serving cell is used for this purpose.

The DCI payload is encoded and sent on the PDCCH along with a CRC scrambled by an identifier. Given a previously configured search space, each UE attempts to detect the PDCCH addressed to it based on multiple hypotheses (also referred to as "candidates") in a process known as "blind decoding." PDCCH candidates can span 1, 2, 4, 8, or 16 CCEs, where the number of CCEs is called the aggregation level (AL) of the PDCCH candidates. If more than one CCE is used, the information in the first CCE is repeated in the other CCEs. By changing the AL, the PDCCH can be made more robust or less robust for a specific payload size. In other words, PDCCH link adaptation can be performed by adjusting the AL. Depending on the AL, the PDCCH candidates can be located at various time-frequency positions in the CORESET.

Once the UE decodes the DCI, it descrambles the CRC with the RNTI(s) assigned to it and/or associated with the specific PDCCH search space. In case of a match, the UE considers the detected DCI to be addressed to it and follows the instructions (e.g., scheduling information) in the DCI.

A hash function can be used to determine the CCE corresponding to the PDCCH candidate that the UE must monitor within the search space set. Hashing is performed differently for different UEs so that the CCE used by the UE is randomized, thereby reducing the probability of collision between multiple UEs for which PDCCH messages are included in the CORESET. The monitoring period is also configured for different PDCCH candidates. In any particular time slot, the UE can be configured to monitor multiple PDCCH candidates in multiple search spaces that can be mapped to one or more CORESETs. PDCCH candidates may need to be monitored multiple times within a time slot, once per time slot or once in multiple time slots.

DCI may also include information about various timing offsets (e.g., in units of time slots or subframes) between PDCCH and PDSCH, PUSCH, HARQ and/or CSI-RS. Figure 7 shows various timing offsets between PDCCH, PDSCH, PUSCH, HARQ and CSI-RS for NR. For example, offset K0 represents the number of time slots between the UE's PDCCH reception of PDSCH-scheduled DCI (e.g., format 1_0 or 1_1) and subsequent PDSCH transmission. Similarly, offset K1 represents the number of time slots between the PDSCH transmission and the UE's responsive HARQ ACK/NACK transmission on PUSCH. In addition, offset K3 represents the number of time slots between the responsive ACK/NACK and the corresponding data retransmission on PDSCH. In addition, offset K2 represents the number of time slots between the UE's PDCCH reception of PUSCH-granted DCI (e.g., format 0_0 or 0_1) and subsequent PUSCH transmission. Each of these offsets can have values of zero and positive integers.

Finally, DCI format 0_1 may also include a network request for UE reporting of channel state information (CSI) or channel quality information (CQI). Before sending the report, the UE receives and measures the CSI-RS sent by the network. The parameter aperiodicTriggeringOffset represents the integer number of time slots between the UE's reception of the DCI including the CSI request and the network's transmission of the CSI-RS. This parameter can have values 0-4.

As indicated above, for NR, these scheduling offsets may be greater than zero, which facilitates both intra-slot (zero offset) and inter-slot (non-zero offset) scheduling. Inter-slot scheduling may be desirable to facilitate UE energy conservation, for example, by adaptively changing between upper and lower BWPs for PDCCH and PDSCH, respectively.

Discontinuous Reception (DRX) is another technique that has been used to reduce UE energy consumption and extend UE battery life. At a high level, DRX allows the UE to transition to a low power state as long as it does not need to receive any transmissions from the network (e.g., gNB). FIG. 8 shows a timing diagram illustrating an exemplary DRX operation. As shown in FIG. 8, DRX operation is based on a DRX cycle, an activation period (Onduration), and an inactivity timer (other parameters may be used but are omitted here for simplicity of illustration). During the activation period, the UE wakes up and monitors the PDCCH. If no valid DCI addressed to the UE is detected during the activation period, the UE starts the inactivity timer but continues to monitor the PDCCH until the UE detects a valid DCI addressed to it or the inactivity timer expires. The period from the start of the activation period until the inactivity timer expires may be referred to as "active time". If the UE receives a valid DCI, it extends the inactivity timer and continues to monitor the PDCCH. On the other hand, if the inactivity timer expires, the UE may stop PDCCH monitoring until the end of the DRX cycle and go to sleep until the start of the next DRX cycle.

Typically, the inactivity timer counts the number of consecutive (one or more) PDCCH subframes/slots following a subframe/slot in which the PDCCH indicates an initial UL, DL or secondary link (SL, i.e., UE to UE) user data transmission for a Media Access Control (MAC) entity. Typically, there is one MAC entity per configured cell group, e.g., one for a Master Cell Group (MCG) and another for a Secondary Cell Group (SCG).

Furthermore, DRX parameters are typically configured by RRC, which typically operates at a slower or longer time scale than lower layers (such as MAC and PHY). Therefore, the DRX parameters discussed above cannot be adaptively changed via RRC, especially if the UE has a mix of traffic types.

Typically, the UE is configured via RRC with a set of possible (or candidate) values for each scheduling offset (i.e., K0, K1, K2, and aperiodicTriggeringOffset). However, even if the UE knows the set of candidate offsets, it only finds a specific offset associated with a specific PDCCH (e.g., DCI) after decoding the PDCCH (e.g., K0 for PDSCH). Therefore, if the UE has configured a specific energy-saving operating mode, the UE may not have enough time to change to another operating mode to comply with the offset sent by the PDCCH.

This problem may be particularly evident for changing the UE's mode of operation between PDCCH and PDSCH or CSI-RS reception. For example, the UE may be able to save power by using a narrower BWP for PDCCH and a wider BWP for PDSCH, or by modifying the active bandwidth setting for PDCCH based solely on search space information. As another example, it may be desirable for the UE to turn off its receive chain between PDCCH and PDSCH/CSI-RS, or to monitor PDCCH with a single antenna and receive chain and receive PDSCH with multiple antennas and receive chains.

This adaptation can be performed only for K0>0 (PDCCH/PDSCH) and/or aperiodicTriggeringOffset>0 (PDCCH/CSI-RS), which gives the UE enough time to reconfigure the receiver accordingly. Otherwise, for zero-value offsets, the UE must maintain the receiver in full-power PDSCH-compatible operation even when receiving PDCCH. Similar problems exist for offsets K1 and K2. Unfortunately, the UE does not know the specific offset until it decodes the PDCCH.

However, although a fixed non-zero offset value can help the UE reduce energy consumption, having such a fixed offset value may not be possible when the load is high and/or multiple consecutive time slots need to be scheduled. Then, having a non-zero offset between PDCCH and PDSCH can lead to additional power consumption and delay. In summary, ensuring a minimum (e.g., non-zero) offset or delay between PDCCH and PDSCH/PUSCH/PUCCH can promote energy reduction when the UE is almost inactive, but can increase energy consumption during a series of multiple PDSCH transmissions.

Exemplary embodiments of the present disclosure solve these and other problems and/or disadvantages by providing techniques and/or mechanisms for configuring, enabling and/or disabling UE cross-slot scheduling with an offset between PDCCH and PDSCH/PUSCH/PUCCH before the first or Nth scheduled PDCCH, while providing an unguaranteed scheduling offset (including simultaneous slot scheduling) during other PDCCH opportunities. These embodiments can promote the reduction of UE energy consumption by allowing the UE operating mode to change between PDCCH monitoring and subsequent PDSCH/PUSCH/PUCCH depending on the process of sending multiple PDSCHs. Moreover, by adapting between simultaneous slot scheduling and cross-slot scheduling in this manner, the embodiments reduce the delay imposed by average scheduling compared to the case where cross-slot scheduling is used in all slots. More generally, the disclosed embodiments provide enhanced cross-slot scheduling that achieves UE energy consumption reduction without imposing the delay and/or throughput cost associated with applying the cross-slot configuration to all PDSCH transmissions in a traditional manner.

Although the description of the embodiments is given in terms of inter-slot offsets, the principles of these embodiments may also be applied to intra-slot offsets, e.g., symbols within the same slot. For example, the current 3GPP specification provides for the possibility of starting PDSCH/PUSCH transmissions at multiple symbols after the PDCCH even within the same slot (e.g., based on time domain resource allocation (TDRA) configuration). Because in the case of cross-slot scheduling, the offset is only known after DCI decoding.

Figure 9 shows various timing diagrams of selective cross-slot scheduling operation modes (labeled A-G) during the DRX activation period of a UE according to various embodiments of the present disclosure. PDCCH monitoring opportunities (MO) according to the configured (one or more) UE search spaces are indicated by dotted lines, and actual (one or more) PDCCH transmissions are indicated by solid lines. The opportunities where the UE can adopt cross-slot scheduling with a certain (or minimum) scheduling offset are indicated by a single vertical solid line, while the opportunities where such adoption is not made are indicated by pairs of vertical solid lines with small spacing. Wake-up signal (WUS) transmissions are indicated by cross-hatching lines (e.g., in mode D).

In the various inter-slot scheduling modes shown in Figure 9, the network can configure the UE to expect inter-slot scheduling with a known scheduling offset (or a scheduling offset range with a known minimum value) before the first scheduling PDCCH. In the various embodiments or modes shown in Figure 9, the "first scheduling PDCCH" can be the first PDCCH sent after an event in a PDCCH MO of the UE, and carries scheduling information for the UE (for example, for subsequent PDSCH or PUSCH). In mode A, the first scheduling PDCCH is the first PDCCH after the start of the DRX activation period of the UE. Alternatively, in mode B, the first scheduling PDCCH is the first PDCCH after the latest PDSCH/PUSCH/PUCCH reception/transmission ends. Alternatively, the first scheduling PDCCH can be the first PDCCH after a specific number K of inactive slots or time periods (mode C, where K=2), or the first PDCCH after receiving a WUS signal (mode D, other WUS mechanisms are also possible).

In other embodiments, the UE may expect cross-slot scheduling from the first scheduled PDCCH to the Nth scheduled PDCCH, where the parameter N is configured by the network (e.g., via RRC). In some embodiments, the parameter N may refer to the number of scheduled PDCCHs actually sent (mode E, N=3) or to the number of PDCCH MOs configured based on the search space (mode F, N=3). The UE may also be configured to adopt a cross-slot configuration for N PDCCH opportunities that occur during a specific time interval (e.g., up to K PDCCH opportunities) after the most recently received PDCCH (mode G, K=2, N=3).

In some embodiments, in addition to being configured with respect to cross-slot PDSCH scheduling, the UE may also be configured (e.g., via RRC) to assume that it will not be scheduled for non-periodic CSI reporting in the middle so that the UE may change its receiver operation mode without maintaining preparation for CSI measurements.

Other exemplary embodiments are discussed below, which are generally divided into two groups: 1) UE configuration via RRC signaling; or 2) UE configuration via MAC CE or DCI. Although these examples are provided in terms of first scheduling PDCCH and cross-slot scheduling, the principles associated with these examples can also be applied to embodiments involving N-th scheduling PDCCH and involving simultaneous slot scheduling with multiple symbols between PDCCH and PDSCH/PUSCH/PUCCH.

In a first set of embodiments, the UE may be configured via RRC signaling to expect and/or assume that cross-slot scheduling will be used for the first PDCCH, and that a minimum scheduling offset (eg, a minimum of K0 or K2 slots) may be used for cross-slot scheduling.

In some embodiments of this group, the UE may send a capability report to the network including the UE PDCCH decoding processing time capability (e.g., in units of time slots). Upon receiving the report, the network may take into account the UE's processing time capability so that the network does not consider any lower scheduling offset values for scheduling across time slots. Knowing that the network will not schedule before this minimum offset, the UE may select a different operating mode, such as micro-sleep, during this time.

Typically, the network can achieve an acceptable, appropriate, and/or optimal balance between reducing UE energy consumption and keeping latency low by selecting the minimum processing (or mode switching time) as the offset value. However, the network may consider other parameters and/or values when selecting the offset. In some embodiments, in addition to or instead of the processing time, the UE may also send additional performance capabilities to the network, such as the time required to turn on and/or turn off the UE's receive chain, the time required to switch between active and sleep states, the time required to switch between BWP configurations, etc. The network may consider any of these received parameters and/or values when selecting the scheduling offset. Even so, the network is not required to base the selection of the scheduling offset on these capabilities and/or preferences received from the UE.

In some embodiments, if the network decides not to base the selection on these values, the network may respond to the UE with an indication of the result. Given the response, the UE may adjust its expectations for the cross-slot scheduling offset accordingly. Alternatively, the network may inform the UE of the actual (or minimum) scheduling offset without explicitly informing the UE whether the capabilities and/or preferences it provides are considered in selecting the actual (or minimum) scheduling offset. Likewise, the network may subsequently reconfigure the actual (or minimum) scheduling offset value through RRC signaling (e.g., a reconfiguration procedure).

In other embodiments, the network may configure the UE to always or with a periodic or aperiodic DRX cycle expect cross-slot scheduling for the first scheduled PDCCH (e.g., PDSCH). The mode may be pre-configured by the network during RRC configuration. Similarly, the network may configure the UE to expect cross-slot scheduling for the first scheduled PDCCH until instructed otherwise (e.g., via RRC reconfiguration).

In a second group of embodiments, the network may use MAC control elements (CE) and/or DCI signaling to enable, disable, and/or reconfigure the UE configuration for cross-slot scheduling of the first scheduling PDCCH. For example, the network may use MAC CE and/or DCI to enable, disable, and/or reconfigure the UE configuration previously performed by the network through RRC.

In some embodiments of the group, MAC CE and/or DCI signaling may indicate that the UE should apply (e.g., via RRC) pre-configured cross-slot scheduling for the first PDCCH after the last PDSCH/PUSCH/PUCCH or a specific number of inactive time durations/time slots. In other embodiments, MAC CE and/or DCI signaling may also be used to overwrite and/or reconfigure previously configured parameters related to cross-slot scheduling for the first scheduled PDCCH. In addition, MAC CE and/or DCI signaling may be used to disable the UE's assumption of cross-slot scheduling for the first scheduled PDCCH. For example, if the network has or expects to have downlink data to be sent to the UE, the network may disable the UE's assumption of cross-slot scheduling. Upon receiving the disabling configuration, the UE may prepare its receive chain and other processing capabilities accordingly (e.g., receiving the same-slot PDSCH).

In some embodiments of this group, the network may configure the UE (e.g., via RRC) with multiple explicit cross-slot scheduling configurations prior to the first scheduling PDCCH, and then use MAC CE and/or DCI signaling to enable and/or disable specific ones of these configurations and/or switch between various configurations.

In some embodiments of the group, a MAC CE command for enabling, disabling, or reselecting a cross-slot scheduling configuration may be multiplexed in the last PDSCH message sent to the UE before the first PDCCH to which it applies. Alternatively, the MAC CE command may be sent in its own PDSCH message before the first PDCCH. It may also be multiplexed in the first PDSCH or between, particularly when explicit cross-slot scheduling needs to be disabled. The same applies to DCI signaling, and information for enabling, disabling, and/or reselecting may be included in the last scheduled DCI, the first scheduled DCI, and/or the intermediate scheduled DCI, or even as an independent DCI. For example, within the DCI, any reserved bit or any bit involving a reserved or invalid value (e.g., an invalid MCS row index) of a specific field may be used to enable, disable, or reselect a cross-slot scheduling configuration.

Various exemplary embodiments have been discussed above with respect to explicit cross-slot scheduling for a first scheduling PDCCH for a UE currently operating in DRX mode, such as illustrated by the example shown in Figure 9. However, the principles of these embodiments may also be applicable to situations in which wake-up (WUS)/sleep (GTS) signaling is used to indicate wake-up or sleep during or before an activation period/inactivity timer. For example, in some embodiments, the WUS signal itself can be used to indicate the start (e.g., enable) or end (e.g., disable) of explicit cross-slot scheduling that was previously configured (e.g., via RRC). Alternatively, an explicit command carried by the WUS can be used for this purpose. GTS signaling can be used in a similar manner.

In addition to configuring the UE to expect cross-slot scheduling for the first PDCCH, the network can also configure the UE to change the scheduling mode after the first PDCCH. For example, the UE can be configured to change to a same-slot mode or a different cross-slot mode before the first PDCCH. As a specific example, the network can facilitate a significant reduction in energy consumption of the UE by scheduling all PDSCH/PUSCH/PUCCH associated with the UE in the same slot after the first PDCCH.

In other embodiments, the network does not explicitly configure the UE to expect cross-slot scheduling for the first (or up to the Nth) scheduled PDCCH in the manner discussed above, but still uses cross-slot scheduling for the UE. In such an embodiment, the UE can collect historical data related to the network's cross-slot scheduling configuration. Based on the collected data, the UE can determine that the network may use cross-slot scheduling for PDCCH in an upcoming scenario that is consistent with or corresponding to the historical data. Based on this determination, the UE can change its operating mode to reduce energy consumption. If the network does not use cross-slot scheduling in the upcoming scenario, as predicted and/or determined by the UE, the UE can send a NACK in the allocated PUCCH/PUSCH resources, which does not add much delay while promoting UE energy consumption reduction.

The embodiments described above may be further described with reference to Figures 10 to 11, which depict exemplary methods (eg, processes) performed by a UE and a network node, respectively. In other words, various features of the operations described below correspond to the various embodiments described above.

In particular, FIG. 10 shows a flowchart of an exemplary method (e.g., process) for managing energy consumption of a user equipment (UE) in communication with a network node in a radio access network (RAN) according to various exemplary embodiments of the present disclosure. The exemplary method may be performed by a user equipment (UE, such as a wireless device, IoT device, modem, etc., or a component thereof) communicating with a network node (e.g., a base station, eNB, gNB, etc., or a component thereof) in a RAN (e.g., E-UTRAN, NG-RAN). For example, the exemplary method shown in FIG. 10 may be implemented by a UE configured as described herein with reference to other figures. In addition, the exemplary method shown in FIG. 10 may be used in cooperation with other exemplary methods described herein (e.g., FIG. 11) to provide various benefits and/or advantages, including those described herein. Although FIG. 10 shows specific blocks in a specific order, the operations of the blocks may be performed in a different order than shown, and may be combined and/or divided into blocks having different functions than shown. Optional blocks or operations are indicated by dashed lines.

An exemplary method may include the operation of block 1030, wherein the UE may receive an indication from the network node that the minimum scheduling offset will change after a first duration. The minimum scheduling offset may be between a scheduling PDCCH and a signal or channel scheduled via the scheduling PDCCH. In some embodiments, the first duration may be related to the time required for the UE to switch from a first operating configuration to a second operating configuration. In some embodiments, the first operating configuration may consume less energy than the second operating configuration. In some embodiments, the first operating configuration and the second operating configuration may differ in one or more of the following parameters: the proportion of time spent in sleep mode; the bandwidth part (BWP) used; and the number of receive chains used. Thus, the first duration may be related to or based on the time required to turn on/off the UE's receive chain, the time required to transition between an active state and a sleep state, the time required to switch between BWP configurations, and the like.

In other embodiments, the first duration may be based on an initial scheduled PDCCH for the UE after receiving the indication; or based on an initial plurality of scheduled PDCCHs for the UE after receiving the indication.

In other embodiments, the first duration may include a second plurality of PDCCH monitoring opportunities associated with the UE during one of: after receiving the indication; or a third plurality of PDCCH monitoring opportunities associated with the UE after receiving the indication, wherein the third plurality is greater than the second plurality.

In some embodiments, the exemplary method may further include the operation of block 1010, wherein the UE may send an indication of the processing time required for PDCCH decoding to the network node. In such an embodiment, the received indication may identify a minimum scheduling offset applicable after the end of the first duration that is greater than or equal to the indicated processing time (e.g., in block 1030).

In some embodiments, the example method may further include the operation of block 1020, wherein the UE may receive a configuration message from the network node identifying one or more candidate scheduling offsets. In such embodiments, the indication received (e.g., in block 1030) may identify one of the candidate scheduling offsets as a minimum scheduling offset applicable after the first duration ends. In some embodiments, the configuration message is a radio resource control (RRC) message, and the indication is received via a medium access control (MAC) control element (CE) or a physical layer (PHY) downlink control information (DCI).

The exemplary method may also include the operation of block 1040, where the UE may then monitor the scheduling PDCCH based on the first operating configuration during the first duration. The exemplary method may also include the operation of block 1070, where the UE may monitor the scheduling PDCCH based on the second operating configuration in response to the end of the first duration. In some embodiments, the first operating configuration and the second operating configuration may differ in one or more of the following parameters: the proportion of time spent in sleep mode; the portion of bandwidth used; and the number of receive chains used.

In some embodiments, the exemplary method may further include the operations of blocks 1050-1060. In block 1050, the UE may detect a scheduling signal or channel for a first scheduled PDCCH of the UE during monitoring based on the first operating configuration. In block 1060, the UE may send or receive a signal or channel at a first scheduling offset after the first scheduled PDCCH.

In some embodiments, the exemplary method may further include the operations of blocks 1080-1090. In block 1080, the UE may detect a scheduling signal or channel for a second scheduling PDCCH of the UE during monitoring based on the second operating configuration. In block 1060, the UE may send or receive a signal or channel at a second scheduling offset after the second scheduling PDCCH.

In some embodiments, the first scheduling offset (e.g., applicable during the first duration) is greater than the second scheduling offset (e.g., applicable at the end of the first duration). In some of these embodiments, the second scheduling offset may include zero or more symbols in the same slot as the second scheduled PDCCH, and the first scheduling offset may include one or more slots or one or more symbols in the same slot (e.g., relative to the first scheduled PDCCH occurring during the first duration). For example, in such embodiments, the second scheduling offset may facilitate same-slot scheduling (e.g., in the same or subsequent symbol as the PDCCH), and the first scheduling offset may facilitate cross-slot scheduling or cross-symbol scheduling within a mini-slot (e.g., during the first duration).

In other of these embodiments, the second scheduling offset may include one or more time slots after the second scheduling PDCCH, and the first scheduling offset may include two or more time slots (e.g., relative to the first scheduling PDCCH occurring during the first duration). In other words, although both the first scheduling offset and the second scheduling offset facilitate cross-time slot scheduling, the second scheduling offset has fewer time slots than the first scheduling offset.

In various embodiments, one of the following may apply:

The signal or channel is a physical downlink shared channel (PDSCH), and the first scheduling offset is K0;

The signal or channel is a physical uplink shared channel (PUSCH) and the first scheduling offset is K2; or

The signal or channel is a channel state information reference signal (CSI-RS), and the first scheduling offset is an aperiodic trigger offset.

In addition, FIG. 11 shows a flowchart of an exemplary method (e.g., process) for managing UE energy consumption regarding communication between a user equipment (UE) and a network node according to various exemplary embodiments of the present disclosure. The exemplary method may be performed by a network node (e.g., base station, eNB, gNB, etc. or its components) of a radio access network (RAN, such as E-UTRAN, NG-RAN) that communicates with a user equipment (UE, such as a wireless device, IoT device, modem, etc. or its components). For example, the exemplary method shown in FIG. 11 may be implemented in a network node configured as described herein with reference to other figures. In addition, the exemplary method shown in FIG. 11 may be used in cooperation with other exemplary methods described herein (e.g., FIG. 10) to provide various exemplary benefits and/or advantages, including those described herein. Although FIG. 11 shows specific blocks in a specific order, the operations of the exemplary method may be performed in a different order than shown, and may be combined and/or divided into blocks having different functions than shown. Optional blocks or operations are shown by dotted lines.

An exemplary method may include the operation of block 1130, wherein the network node may send an indication to the UE that the minimum scheduling offset will change after a first duration. The minimum scheduling offset may be between a scheduling PDCCH and a signal or channel scheduled via the scheduling PDCCH. In some embodiments, the first duration may be related to the time required for the UE to switch from a first operating configuration to a second operating configuration. In some embodiments, when configured with the first operating configuration, the UE consumes less energy than when configured with the second operating configuration. In some embodiments, the first operating configuration and the second operating configuration may differ in one or more of the following parameters: the proportion of time spent in sleep mode; the bandwidth part (BWP) used; and the number of receive chains used. Thus, the first duration may be related to or based on the time required to turn on/off the UE's receive chain, the time required to transition between an active state and a sleep state, the time required to switch between BWP configurations, and the like.

In other embodiments, the first duration may be based on an initial scheduled PDCCH for the UE after the indication is sent; or based on an initial plurality of scheduled PDCCHs for the UE after the indication is sent.

In other embodiments, the first duration may include a second plurality of PDCCH monitoring opportunities associated with the UE during one of: after sending the indication; or a third plurality of PDCCH monitoring opportunities associated with the UE after sending the indication, wherein the third plurality is greater than the second plurality.

In some embodiments, the exemplary method may further include the operation of block 1110, wherein the network node may receive an indication of the processing time required for PDCCH decoding from the UE. In such an embodiment, the indication sent (e.g., in block 1130) may identify a minimum scheduling offset applicable after the end of the first duration that is greater than or equal to the indicated processing time.

In some embodiments, the example method may further include the operation of block 1120, where the network node may send a configuration message to the UE identifying one or more candidate scheduling offsets. In such embodiments, the indication sent (e.g., in block 1130) may identify one of the candidate scheduling offsets as a minimum scheduling offset applicable after the first duration ends. In some embodiments, the configuration message is a radio resource control (RRC) message, and the indication is sent via a medium access control (MAC) control element (CE) or a physical layer (PHY) downlink control information (DCI).

The exemplary method may also include the operation of block 1140, where the network node may send a scheduling signal or channel to the UE for a scheduled PDCCH of the UE. The scheduled PDCCH may be sent after the indication sent in block 1140. The exemplary method may also include the operation of block 1150, where the network node may determine a scheduling offset based on whether the scheduled PDCCH is sent during the first duration or after the first duration. The exemplary method may also include the operation of block 1160, where the network node may send or receive a signal or channel at the determined scheduling offset after the scheduled PDCCH.

In some embodiments, the determining operation of block 1150 may include the operations of sub-blocks 1151-1152. In sub-block 1151, if the scheduling PDCCH is sent during the first duration, the network node may select a first scheduling offset. In sub-block 1152, if the scheduling PDCCH is sent after the first duration, the network node may select a second scheduling offset.

In some embodiments, the first scheduling offset (e.g., applicable during the first duration) is greater than the second scheduling offset (e.g., applicable at the end of the first duration). In some of these embodiments, the second scheduling offset may include zero or more symbols in the same slot as the second scheduled PDCCH, and the first scheduling offset may include one or more slots or one or more symbols in the same slot (e.g., relative to the first scheduled PDCCH occurring during the first duration). For example, in such embodiments, the second scheduling offset may facilitate same-slot scheduling (e.g., in the same or subsequent symbol as the PDCCH), and the first scheduling offset may facilitate cross-slot scheduling or cross-symbol scheduling within a mini-slot (e.g., during the first duration).

In other of these embodiments, the second scheduling offset may include one or more time slots after the second scheduling PDCCH, and the first scheduling offset may include two or more time slots (e.g., relative to the first scheduling PDCCH occurring during the first duration). In other words, although both the first scheduling offset and the second scheduling offset facilitate cross-time slot scheduling, the number of time slots of the second scheduling offset is less than that of the first scheduling offset.

In various embodiments, one of the following may apply:

The signal or channel is a physical downlink shared channel (PDSCH), and the first scheduling offset is K0;

The signal or channel is a physical uplink shared channel (PUSCH) and the first scheduling offset is K2; or

The signal or channel is a channel state information reference signal (CSI-RS), and the first scheduling offset is an aperiodic trigger offset.

Although various embodiments are described hereinabove in terms of methods, a person of ordinary skill in the art will recognize that such methods may be implemented through various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, devices, computer-readable media, computer program products, etc.

As an example, FIG12 shows a high-level view of a 5G network architecture, including a next generation RAN (NG-RAN) 1299 and a 5G core (5GC) 1298. The NG-RAN 1299 may include a set of gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 1200, 1250 connected via interfaces 1202, 1252, respectively. In addition, the gNBs may be connected to each other via one or more Xn interfaces, such as an Xn interface 1240 between gNBs 1200 and 1250. With respect to the NR interface with the UE, each gNB may support frequency division duplex (FDD), time division duplex (TDD), or a combination thereof.

The NG RAN logical nodes shown in FIG. 12 (and described in TS 38.401 and TR 38.801) include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, the gNB 1200 in FIG. 12 includes a gNB-CU 1212 and gNB-DUs 1220, 1230. A CU (e.g., gNB-CU 1212) is a logical node that hosts high-level protocols and performs various gNB functions (such as controlling the operation of the DU). Each DU is a logical node that hosts low-level protocols and may include various subsets of gNB functions depending on the functional partitioning. Therefore, each of the CU and DU may include various circuits required to perform its respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power supply circuits. In addition, the terms "central unit" and "centralized unit" are used interchangeably herein, as are the terms "distributed unit" and "decentralized unit".

The gNB-CU is connected to the gNB-DU via a corresponding F1 logical interface (such as interfaces 1222 and 1232 shown in Figure 3). The gNB-CU and the connected gNB-DU are only visible to other gNBs and the 5GC as a gNB, for example, the F1 interface is not visible outside the gNB-CU. As briefly mentioned above, the CU may host high-level protocols such as, for example, the F1 Application Part Protocol (F1-AP), the Stream Control Transmission Protocol (SCTP), the GPRS Tunneling Protocol (GTP), the Packet Data Convergence Protocol (PDCP), the User Datagram Protocol (UDP), the Internet Protocol (IP), and the Radio Resource Control (RRC) protocol. In contrast, the DU may host low-level protocols such as, for example, the Radio Link Control (RLC) protocol, the Media Access Control (MAC) protocol, and the Physical Layer (PHY) protocol.

However, there may be other variations of the distribution of protocols between the CU and the DU, such as hosting RRC, PDCP, and a portion of the RLC protocol (e.g., automatic repeat request (ARQ) functionality) in the CU, while hosting the remainder of the RLC protocol along with the MAC and PHY in the DU. In some embodiments, the CU may host RRC and PDCP, where the PDCP is assumed to handle both UP traffic and CP traffic. However, other exemplary embodiments may utilize other protocol splits by hosting certain protocols in the CU and certain other protocols in the DU. Exemplary embodiments may also locate centralized control plane protocols (e.g., PDCP-C and RRC) in different CUs relative to centralized user plane protocols (e.g., PDCP-U).

FIG13 shows a block diagram of an exemplary wireless device or user equipment (UE) 1300 (hereinafter referred to as "UE 1300") according to various embodiments of the present disclosure (including the embodiments described above with reference to other figures). For example, UE 1300 can be configured to perform operations corresponding to one or more of the exemplary methods and/or processes described above by the execution of instructions stored on a computer-readable medium.

UE 1300 may include a processor 1310 (also referred to as a "processing circuit") that may be operably connected to a program memory 1320 and/or a data memory 1330 via a bus 1370, which may include a parallel address and data bus, a serial port, or other methods and/or structures known to those of ordinary skill in the art. Program memory 1320 may store software codes, programs, and/or instructions (collectively shown as computer program product 1361 in FIG. 13) that, when executed by processor 1310, may configure UE 1300 and/or facilitate the UE to perform various operations, including operations corresponding to the various exemplary methods described herein. As part of or in addition to such operations, execution of such instructions may configure UE 1300 to and/or facilitate UE 1300 to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as those commonly referred to as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, lxRTT, CDMA2000, 802.11WiFi, HDMI, USB, Firewire, etc., or any other current or future protocol that may be used in conjunction with radio transceiver 1340, user interface 1350, and/or control interface 1360.

As another example, the processor 1310 may execute program code stored in the program memory 1320, which corresponds to MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and/or LTE). As a further example, the processor 1310 may execute program code stored in the program memory 1320, which together with the radio transceiver 1340 implements corresponding PHY layer protocols, such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). As another example, the processor 1310 may execute program code stored in the program memory 1320, which together with the radio transceiver 1340 implements device-to-device (D2D) communication with other compatible devices and/or UEs.

The program memory 1320 may also include software codes executed by the processing UE 1310 to control the functions of the UE 1300, including configuring and controlling various components, such as the radio transceiver 1340, the user interface 1350, and/or the host interface 1360. The program memory 1320 may also include one or more applications and/or modules, including computer executable instructions that embody any exemplary method and/or process described herein. Such software code may be specified or written using any known or future developed programming language, such as, for example, Java, C++, C, Objective C, HTML, XHTML, machine code, and assembler, as long as, for example, the desired functionality defined by the implemented method steps is retained. In addition or as an alternative, the program memory 1320 may include an external storage device (not shown) remote from the UE 1300, from which instructions may be downloaded to the program memory 1320 within or removably coupled to the UE 1300, so as to enable execution of such instructions.

The data memory 1330 may include a memory area for the processor 1310 to store variables used in protocols, configurations, controls, and other functions of the UE 1300, including operations corresponding to or including any exemplary methods and/or processes described herein. In addition, the program memory 1320 and/or the data memory 1330 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. In addition, the data memory 1330 may include a storage slot into which a removable memory card (e.g., SD card, memory stick, compact flash, etc.) in one or more formats may be inserted and removed.

Those of ordinary skill in the art will recognize that the processor 1310 may include multiple individual processors (including, for example, a multi-core processor), each of which implements a portion of the functionality described above. In such a case, the multiple individual processors may be connected to the program memory 1320 and the data memory 1330 together or individually connected to multiple individual program memories and/or data memories. More generally, those of ordinary skill in the art will recognize that the various protocols and other functions of the UE 1300 may be implemented in many different computer arrangements including different combinations of hardware and software, but not limited to application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and/or programmable digital circuits, analog baseband circuits, radio frequency circuits, software, firmware, and middleware.

The radio transceiver 1340 may include radio frequency transmitter and/or receiver functionality that facilitates the UE 1300 to communicate with other devices supporting similar wireless communication standards and/or protocols. In some exemplary embodiments, the radio transceiver 1340 includes one or more transmitters and one or more receivers that enable the UE 1300 to communicate according to various protocols and/or methods proposed for standardization by 3GPP and/or other standards bodies. For example, such functionality may operate in cooperation with the processor 1310 to implement a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technology, such as described herein with respect to other figures.

In some exemplary embodiments, the radio transceiver 1340 includes one or more transmitters and one or more receivers that can facilitate the UE 1300 to communicate with various LTE, LTE-Advanced (LTE-A), and/or NR networks in accordance with standards promulgated by 3GPP. In some exemplary embodiments of the present disclosure, the radio transceiver 1340 includes circuits, firmware, etc. required for the UE 1300 to communicate with various NR, NR-U, LTE, LTE-A, LTE-LAA, UMTS, and/or GSM/EDGE networks also in accordance with 3GPP standards. In some embodiments, the radio transceiver 1340 may include circuits to support D2D communications between the UE 1300 and other compatible UEs.

In some embodiments, radio transceiver 1340 includes circuits, firmware, etc. required for UE 1300 to communicate with various CDMA2000 networks according to 3GPP2 standards. In some embodiments, radio transceiver 1340 can use radio technology (such as IEEE802.11WiFi operated using frequencies in the region of 2.4, 5.6, and/or 60GHz) to communicate. In some embodiments, radio transceiver 1340 may include a transceiver capable of wired communication, such as by using IEEE802.3 Ethernet technology. Functions specific to each of these embodiments can be coupled with other circuits in UE 1300 and/or controlled by other circuits in UE 1300, such as processor 1310 that executes program codes stored in program memory 1320 and/or supported by data memory 1330 in conjunction with data memory 1330.

Depending on the specific embodiment of UE 1300, user interface 1350 may take various forms or may be completely absent from UE 1300. In some embodiments, user interface 1350 may include a microphone, a speaker, a slidable button, a depressible button, a display, a touch screen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and/or any other user interface features typically found on a mobile phone. In other embodiments, UE 1300 may include a tablet computing device that includes a larger touch screen display. In such an embodiment, one or more of the mechanical features of user interface 1350 may be replaced by comparable or functionally equivalent virtual user interface features (e.g., virtual keypads, virtual buttons, etc.) implemented using a touch screen display. In other embodiments, UE 1300 may be a digital computing device, such as a laptop computer, a desktop computer, a workstation, etc., which includes an integrated, detachable, or detachable mechanical keyboard depending on a specific exemplary embodiment. Such a digital computing device may also include a touch screen display. Many exemplary embodiments of UE 1300 with a touch screen display are capable of receiving user input, such as input related to the exemplary methods and/or processes described herein or otherwise known to those of ordinary skill in the art.

In some embodiments, UE 1300 may include an orientation sensor that can be used in various ways by the features and functions of UE 1300. For example, UE 1300 can use the output of the orientation sensor to determine when a user has changed the physical orientation of the touch screen display of UE 1300. The indication signal from the orientation sensor can be used for any application executed on UE 1300 so that the application can automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates an approximately 90-degree change in the physical orientation of the device. With this exemplary approach, the application can maintain the screen display in a manner that can be read by the user, regardless of the physical orientation of the device. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.

The control interface 1360 of the UE 1300 may take various forms, depending on the specific exemplary embodiment of the UE 1300 and the specific interface requirements of other devices with which the UE 1300 is intended to communicate and/or control. For example, the control interface 1360 may include an RS-232 interface, an RS-4135 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, an I ² C interface, a PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, the control interface 1360 may include an IEEE 802.3 Ethernet interface such as described above. In some exemplary embodiments of the present disclosure, the control interface 1360 may include an analog interface circuit, which includes, for example, one or more digital-to-analog (D/A) and/or analog-to-digital (A/D) converters.

Those of ordinary skill in the art will recognize that the above-mentioned features, interfaces, and the list of radio frequency communication standards are only exemplary and do not limit the scope of the present disclosure. In other words, UE 1300 may include more functions than those shown in Figure 13, including, for example, video and/or still image cameras, microphones, media players, and/or video recorders, etc. In addition, the radio transceiver 1340 may include circuits required for communication using additional radio frequency communication standards (including Bluetooth, GPS, and/or others). In addition, the processor 1310 may execute software codes stored in the program memory 1320 to control such additional functions. For example, the directional speed and/or position estimation output from the GPS receiver can be used for any application executed on the UE 1300, including various exemplary methods and/or computer-readable media according to various exemplary embodiments of the present disclosure.

14 shows a block diagram of an exemplary network node 1400 according to various embodiments of the present disclosure (including the embodiments described above with reference to other figures). For example, the exemplary network node 1400 may be configured to perform operations corresponding to one or more of the exemplary methods and/or processes described above by the execution of instructions stored on a computer-readable medium. In some exemplary embodiments, the network node 1400 may include a base station, an eNB, a gNB, or one or more components thereof. For example, according to the NR gNB architecture specified by 3GPP, the network node 1400 may be configured as a central unit (CU) and one or more distributed units (DU). More generally, the functions of the network node 1400 may be distributed across various physical devices and/or functional units, modules, etc.

Network node 1400 may include a processor 1410 (also referred to as a "processing circuit") operably connected to a program memory 1420 and a data memory 1430 via a bus 1470, which may include a parallel address and data bus, a serial port, or other methods and/or structures known to those of ordinary skill in the art.

Program memory 1420 may store software codes, programs, and/or instructions (collectively illustrated in FIG. 14 as computer program product 1421) that, when executed by processor 1410, may configure and/or facilitate network node 1400 to perform various operations, including operations corresponding to various exemplary methods described herein. As part of and/or in addition to such operations, program memory 1420 may also include software code executed by processor 1410 that may configure and/or facilitate network node 1400 to communicate with one or more other UEs or network nodes using other protocols or protocol layers (such as one or more of the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and/or NR, or any other higher layer (e.g., NAS) protocols used in conjunction with radio network interface 1440 and/or core network interface 1450). By way of example, the core network interface 1450 may include an S1 or NG interface, and the radio network interface 1440 may include a Uu interface as standardized by 3GPP. The program memory 1420 may also include software code that is executed by the processor 1410 to control the functionality of the network node 1400, including configuring and controlling various components, such as the radio network interface 1440 and the core network interface 1450.

The data memory 1430 may include a memory area for the processor 1410 to store variables used in the protocols, configurations, controls, and other functions of the network node 1400. Therefore, the program memory 1420 and the data memory 1430 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage, or a combination thereof. Those of ordinary skill in the art will recognize that the processor 1410 may include a plurality of separate processors (not shown), each of which implements a portion of the functions described above. In this case, the plurality of separate processors may be connected to the program memory 1420 and the data memory 1430 in common or connected to a plurality of separate program memories and/or data memories individually. More generally, those of ordinary skill in the art will recognize that the various protocols and other functions of the network node 1400 may be implemented in many different hardware and software combinations, including but not limited to application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuits, programmable digital circuits, analog baseband circuits, radio frequency circuits, software, firmware, and middleware.

The radio network interface 1440 may include a transmitter, a receiver, a signal processor, an ASIC, an antenna, a beamforming unit, and other circuits that enable the network node 1400 to communicate with other devices (in some embodiments, such as multiple compatible user equipment (UE)). In some embodiments, the interface 1440 may also enable the network node 1400 to communicate with compatible satellites of a satellite communication network. In some exemplary embodiments, the radio network interface 1440 may include various protocols or protocol layers, such as PHY, MAC, RLC, PDCP, and/or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc.; such as improvements thereto described above; or any other high-level protocol used in conjunction with the radio network interface 1440. According to further exemplary embodiments of the present disclosure, the radio network interface 1440 may include a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technology. In some embodiments, the functionality of such a PHY layer may be provided cooperatively by the radio network interface 1440 and the processor 1410 (including program code in the memory 1420).

The core network interface 1450 may include a transmitter, a receiver, and other circuits that enable the network node 1400 to communicate with other devices in a core network (in some embodiments, such as a circuit switched (CS) and/or packet switched (PS) core network). In some embodiments, the core network interface 1450 may include an S1 interface standardized by 3GPP. In some embodiments, the core network interface 1450 may include an NG interface standardized by 3GPP. In some exemplary embodiments, the core network interface 1450 may include one or more interfaces with one or more AMF, SMF, SGW, MME, SGSN, GGSN, and other physical devices, which include functions found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks known to those of ordinary skill in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 1450 may include one or more of the following: asynchronous transfer mode (ATM), Ethernet Internet Protocol (IP), fiber optic SDH, copper wire T1/E1/PDH, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.

In some embodiments, the network node 1400 may include hardware and/or software that configures and/or facilitates the network node 1400 to communicate with other network nodes in the RAN, such as other eNBs, gNBs, ng-eNBs, en-gNBs, IAB nodes, etc. Such hardware and/or software may be part of the radio network interface 1440 and/or the core network interface 1450 or may be a separate functional unit (not shown). For example, such hardware and/or software may configure and/or facilitate the network node 1400 to communicate with other RAN nodes via an X2 or Xn interface as standardized by 3GPP.

The OA&M interface 1460 may include transmitters, receivers, and other circuits that enable the network node 1400 to communicate with external networks, computers, databases, etc. for operation, management, and maintenance of the network node 1400 or other network devices operatively connected thereto. The lower layers of the OA&M interface 1460 may include one or more of the following: asynchronous transfer mode (ATM), Ethernet Internet Protocol (IP), fiber optic SDH, copper wire T1/E1/PDH, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art. Additionally, in some embodiments, one or more of the radio network interface 1440, the core network interface 1450, and the OA&M interface 1460 may be multiplexed together on a single physical interface, such as the examples listed above.

15 is a block diagram of an exemplary communication network configured to provide an over-the-top (OTT) data service between a host computer and a user equipment (UE) according to one or more exemplary embodiments of the present disclosure. UE 1510 can communicate with a radio access network (RAN) 1530 via a radio interface 1520, which can be based on the protocols described above, including, for example, LTE, LTE-A, and 5G/NR. For example, UE 1510 can be configured and/or arranged as shown in the other figures discussed above.

The RAN 1530 may include one or more terrestrial network nodes (e.g., base stations, eNBs, gNBs, controllers, etc.) operable in licensed bands and one or more network nodes operable in unlicensed spectrum (using, for example, LAA or NR-U technology), such as 2.4 GHz and/or 5 GHz bands. In this case, the network nodes including the RAN 1530 may operate cooperatively using licensed and unlicensed spectrum. In some embodiments, the RAN 1530 may include or be capable of communicating with one or more satellites (including a satellite access network).

The RAN 1530 may also communicate with the core network 1540 according to the various protocols and interfaces described above. For example, one or more devices (e.g., base stations, eNBs, gNBs, etc.) including the RAN 1530 may be delivered to the core network 1540 via the core network interface 1650 described above. In some exemplary embodiments, the RAN 1530 and the core network 1540 may be configured and/or arranged as shown in the other figures discussed above. For example, an eNB including the E-UTRAN 1530 may communicate with the EPC core network 1540 via an S1 interface, such as shown in FIG. 1. As another example, a gNB including the NR RAN 1530 may communicate with the 5GC core network 1530 via an NG interface.

The core network 1540 may also communicate with an external packet data network (shown as the Internet 1550 in FIG. 15 ) according to various protocols and interfaces known to those of ordinary skill in the art. Many other devices and/or networks may also be connected and communicate via the Internet 1550, such as an exemplary host computer 1560. In some exemplary embodiments, the host computer 1560 may use the Internet 1550, the core network 1540, and the RAN 1530 as intermediate networks to communicate with the UE 1510. The host computer 1560 may be a server (e.g., an application server) under the ownership and/or control of a service provider. The host computer 1560 may be operated by an OTT service provider or by another entity on behalf of the service provider.

For example, the host computer 1560 may provide over-the-top (OTT) packet data services to the UE 1510 using the facilities of the core network 1540 and the RAN 1530, which may be unaware of the routing of outgoing/incoming communications to/from the host computer 1560. Similarly, the host computer 1560 may be unaware of the routing of transmissions from the host computer to the UE, e.g., the routing of transmissions through the RAN 1530. Various OTT services may be provided using the exemplary configuration shown in FIG. 15 , including, for example, streaming (one-way) audio and/or video from the host computer to the UE, interactive (two-way) audio and/or video between the host computer and the UE, interactive messaging or social networking, interactive virtual or augmented reality, and the like.

The exemplary network shown in FIG. 15 may also include measurement processes and/or sensors that monitor network performance metrics, including data rates, delays, and other factors that are improved by the exemplary embodiments disclosed herein. The exemplary network may also include functionality for reconfiguring links between endpoints (e.g., a host computer and a UE) in response to changes in measurement results. Such processes and functionality are known and practiced; if the network hides or abstracts the radio interface from the OTT service provider, measurements can be facilitated by dedicated signaling between the UE and the host computer.

The exemplary embodiments described herein provide effective techniques for enhanced cross-slot scheduling (e.g., PDCCH to PDSCH or PUSCH) that achieve UE energy consumption reduction without imposing the delay and/or throughput costs associated with applying the cross-slot configuration to all PDSCH/PUSCH transmissions in a conventional manner. When used in NR and/or LTE UEs (e.g., UE 1510) and eNBs and/or gNBs (e.g., including RAN 1530), the exemplary embodiments described herein can reduce UE energy consumption for PDCCH monitoring, thereby facilitating such UEs to use their stored energy capacity (e.g., in a battery) for other operations, such as receiving and/or sending data via OTT services (e.g., via PDSCH or PUSCH). Such improvements can lead to increased use of such OTT services without the need to recharge the UE battery.

The foregoing merely illustrates the principles of the present disclosure. In view of the teachings herein, various modifications and variations to the described embodiments will be apparent to those skilled in the art. Therefore, it will be appreciated that those skilled in the art will be able to design many systems, arrangements, and processes that, although not explicitly shown or described herein, embody the principles of the present disclosure and may therefore be within the spirit and scope of the present disclosure. Various exemplary embodiments may be used together with each other and interchangeably with each other, as should be understood by those of ordinary skill in the art.

As used herein, the term "unit" may have the conventional meaning in the field of electronic devices, electrical equipment, and/or electronic equipment, and may include, for example, electrical and/or electronic circuits, devices, modules, processors, memories, logical solid-state and/or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output, and/or display functions, etc., such as those described herein.

Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include many of these functional units. These functional units may be implemented via processing circuits (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). The processing circuit may be configured to execute program codes stored in a memory, and the memory may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and/or data communication protocols and instructions for executing one or more of the techniques described herein. In some embodiments, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function according to one or more embodiments of the present disclosure.

As described herein, equipment and/or devices can be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not exclude the possibility that the function of the equipment or device is implemented as a software module instead of being implemented by hardware, and the software module is such as a computer program or a computer program product, which includes an executable software code portion for executing or running on a processor. In addition, the function of the equipment or device can be implemented by any combination of hardware and software. The equipment or device can also be considered as an assembly of multiple equipment and/or devices, whether functionally cooperating with each other or independent. In addition, the equipment and device can be implemented in a distributed manner throughout the system, as long as the function of the equipment or device is retained. This and similar principles are considered to be known to technicians.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will also be understood that, unless explicitly defined herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense.

In addition, some terms used in the present disclosure (including specification, drawings and exemplary embodiments thereof) may be used synonymously in some instances, including but not limited to, for example, data and information. It should be understood that, although these words and/or other words that may be synonymous with each other may be used synonymously herein, there are instances where such words may be intended not to be used synonymously. Further, to the extent that prior art knowledge has not been explicitly incorporated herein by reference above, prior art knowledge is explicitly incorporated herein with its entire contents. All publications cited are incorporated herein by reference in their entirety.

Exemplary embodiments of the techniques and devices described herein include, but are not limited to, the following examples:

1. A method for managing energy consumption of a user equipment (UE) with respect to receiving a physical downlink control channel (PDCCH) transmission from a network node in a radio access network (RAN), the method comprising:

receiving an indication of a first scheduling offset between a scheduling PDCCH and a corresponding signal or channel scheduled via the scheduling PDCCH, wherein the first scheduling offset is applicable for a first duration;

receiving, during a first duration, a first scheduled PDCCH based on a first operating configuration;

switching to a second operating configuration during a first scheduling offset after receiving a first scheduling PDCCH; and

Based on the second operation configuration, a corresponding first signal or channel scheduled via the first scheduling PDCCH is transmitted or received.

2. The method according to embodiment 1, wherein the first scheduling offset includes multiple consecutive time slots or multiple consecutive symbols within a time slot.

3. The method of any one of embodiments 1 to 2 further comprises: after the first duration ends, receiving another scheduled PDCCH based on the second operation configuration.

4. The method according to embodiment 3 further includes: sending or receiving a corresponding another signal or channel scheduled via another scheduling PDCCH after a second scheduling offset after another scheduling PDCCH, wherein the second scheduling offset is smaller than the first scheduling offset.

5. The method of embodiment 4, wherein the second scheduling offset comprises a single time slot or a single symbol within a time slot.

6. The method of any one of embodiments 1 to 5, wherein the first duration is extended until one of the following is received:

A first scheduled PDCCH after receiving the indication; and

A first plurality of scheduled PDCCHs after receiving the indication.

7. The method of any one of embodiments 1 to 5, wherein the first duration includes a second plurality of PDCCH reception opportunities during one of the following time periods:

Upon receipt of instructions; and

A third plurality of PDCCH reception opportunities after receiving the indication, wherein the third plurality is greater than the second plurality.

8. The method of any one of embodiments 1 to 7, wherein the first scheduled PDCCH is an initial scheduled PDCCH during one of the following time periods:

Discontinuous reception (DRX) activation period;

After sending or receiving one of the signals or channels;

After periods of inactivity; and

After receiving the wake-up signal (WUS).

9. The method of any one of embodiments 1 to 8, wherein the first operating configuration consumes less energy than the second operating configuration.

10. The method according to any one of embodiments 1 to 9 further includes: sending an indication of a processing time required for PDCCH decoding to a network node, wherein the received first scheduling offset is greater than the indicated processing time.

11. The method according to any one of embodiments 1 to 10 further includes: receiving a configuration message identifying one or more possible scheduling offset configurations including a first scheduling offset, wherein the received indication enables the first scheduling offset.

12. The method of embodiment 11, wherein:

The configuration message is a Radio Resource Control (RRC) message; and

The indication is received via one of: a medium access control (MAC) control element (CE);

and downlink control information (DCI).

13. The method of any one of embodiments 11 to 12, further comprising: receiving another indication to disable the first scheduling offset.

14. A method for managing energy consumption of a user equipment (UE) with respect to receiving a physical downlink control channel (PDCCH) transmission from a network node in a radio access network (RAN), the method comprising:

sending an indication of a first scheduling offset between a scheduling PDCCH and a corresponding signal or channel scheduled via the scheduling PDCCH to the UE, wherein the first scheduling offset is applicable to a first duration;

During a first duration, sending a first scheduling PDCCH;

After a first scheduling offset after the first scheduling PDCCH, a corresponding first signal or channel scheduled via the first scheduling PDCCH is transmitted or received.

15. The method of embodiment 14, wherein the first scheduling offset comprises a plurality of consecutive time slots or a plurality of consecutive symbols within a time slot.

16. The method according to any one of embodiments 14 to 15, further comprising:

After the first duration ends, sending another scheduling PDCCH; and

After a second scheduling offset after another scheduling PDCCH, a corresponding another signal or channel scheduled via another scheduling PDCCH is transmitted or received, wherein the second scheduling offset is smaller than the first scheduling offset.

17. The method of embodiment 16, wherein the second scheduling offset is a single time slot or a single symbol within a time slot.

18. The method of any one of embodiments 14 to 17, wherein the first duration is extended until transmission of one of:

A first scheduled PDCCH after the transmission indication; and

The first plurality of scheduled PDCCHs after the indication is sent.

19. The method of any one of embodiments 14 to 18, wherein the first duration includes a second plurality of PDCCH reception opportunities associated with the UE during one of the following time periods:

After sending the instruction; and

A third plurality of PDCCH reception opportunities after the sending indication, wherein the third plurality is greater than the second plurality.

20. The method of any one of embodiments 14 to 19, wherein the first scheduled PDCCH is an initial scheduled PDCCH during one of the following time periods:

Discontinuous Reception (DRX) activation period for UE;

After sending or receiving one of the signals or channels;

After a plurality of periods of inactivity by the UE; and

After sending a wake-up signal (WUS) to the UE.

21. The method according to any one of embodiments 14 to 20, further comprising:

receiving an indication of the processing time required for PDCCH decoding from the UE; and

The first schedule offset is selected to be greater than the indicated processing time.

22. The method according to any one of embodiments 14 to 21 further includes: sending a configuration message to the UE identifying one or more possible scheduling offset configurations including a first scheduling offset, wherein the sent indication enables the first scheduling offset.

23. The method of embodiment 22, wherein:

The configuration message is a Radio Resource Control (RRC) message; and

The indication is sent via one of: a medium access control (MAC) control element (CE);

and downlink control information (DCI).

24. The method of any one of embodiments 22 to 23, further comprising sending another indication to disable the first scheduling offset.

25. A user equipment (UE) configured to manage energy consumption in relation to receiving a physical downlink control channel (PDCCH) transmission from a network node in a radio access network (RAN), the UE comprising:

communications circuitry configured to communicate with a network node; and

A processing circuit is operatively associated with the communication circuit and is configured to perform operations corresponding to the method described in any one of exemplary embodiments 1 to 13.

26. A network node in a radio access network (RAN) configured to manage user equipment (UE) energy consumption with respect to physical downlink control channel (PDCCH) transmissions from the network node, wherein the network node comprises:

a communication circuit configured to communicate with one or more UEs; and

A processing circuit is operatively associated with the communication circuit and is configured to perform operations corresponding to the method described in any one of exemplary embodiments 14 to 24.

27. A user equipment (UE) configured to manage energy consumption in relation to receiving a physical downlink control channel (PDCCH) transmission from a network node in a radio access network (RAN), the UE being arranged to perform operations corresponding to the method of any one of exemplary embodiments 1 to 13.

28. A network node in a radio access network (RAN) configured to manage user equipment (UE) energy consumption with respect to physical downlink control channel (PDCCH) transmissions, the network node being arranged to perform operations corresponding to the method of any one of exemplary embodiments 14 to 24.

29. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by at least one processor of a user equipment (UE), configure the UE to perform operations corresponding to the method of any one of exemplary embodiments 1 to 13.

30. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by at least one processor of a network node, configure the network node to perform operations corresponding to the method of any one of exemplary embodiments 14 to 24.

Claims (34)

1. A method performed by a user equipment, UE, in communication with a network node in a radio access network, RAN, the method comprising:

-receiving (1030) from the network node an indication that a minimum scheduling offset between a scheduling physical downlink control channel, PDCCH, and a signal or channel scheduled via the scheduling PDCCH will change after a first duration;

Then monitoring (1040) a scheduling PDCCH based on a first operating configuration during the first duration; and

In response to the end of the first duration, the scheduling PDCCH is monitored (1070) based on a second operational configuration.

2. The method of claim 1, wherein the first operational configuration and the second operational configuration differ in one or more of the following parameters:

the proportion of time spent in sleep mode;

the bandwidth portion used; and

The number of receive chains used.

3. The method of claim 1, wherein the first duration relates to a time required for the UE to switch from the first operating configuration to the second operating configuration.

4. A method according to any one of claims 1 to 3, further comprising:

detecting (1080) a second scheduling PDCCH for scheduling the signal or channel for the UE during monitoring based on the second operational configuration; and

The signal or channel is transmitted or received (1090) at a second scheduling offset subsequent to the second scheduling PDCCH.

5. The method of claim 4, wherein the second scheduling offset is less than a first scheduling offset applicable during the first duration.

6. The method of claim 5, wherein,

The second scheduling offset includes zero or more symbols within the same slot as the second scheduling PDCCH; and

The first scheduling offset includes one or more slots or one or more symbols within the same slot.

7. The method of claim 5, wherein,

The second scheduling offset includes one or more time slots; and

The first scheduling offset includes two or more slots.

8. A method according to any one of claims 1 to 3, further comprising:

during monitoring based on the first operating configuration, detecting (1050) a first scheduling PDCCH that schedules the signal or channel for the UE; and

The signal or channel is transmitted or received (1060) at a first scheduling offset after the first scheduling PDCCH.

9. A method according to any one of claims 1 to 3, wherein the first duration is based on one of:

An initial scheduling, PDCCH, for the UE after receiving the indication; and

An initial plurality of scheduling PDCCHs for the UE after receiving the indication.

10. The method of any of claims 1-3, wherein the first duration comprises a second plurality of PDCCH monitoring occasions associated with the UE during one of:

after receiving the indication; or alternatively

A third plurality of PDCCH monitoring occasions associated with the UE after receiving the indication, wherein the third plurality is greater than the second plurality.

11. A method according to any one of claim 1 to 3, wherein,

The method further comprises the steps of: -sending (1010) an indication of a processing time required for PDCCH decoding to the network node; and

The received indication identifies a minimum scheduling offset applicable after the end of the first duration, the minimum scheduling offset being greater than or equal to the indicated processing time.

12. A method according to any one of claim 1 to 3, wherein,

The method further comprises the steps of: -receiving (1020) a configuration message identifying one or more candidate scheduling offsets from the network node; and

The received indication identifies one of the candidate scheduling offsets as the minimum scheduling offset applicable after the end of the first duration.

13. The method of claim 12, wherein,

The configuration message is a radio resource control, RRC, message; and

The indication is received via one of:

A medium access control MAC control element CE; or (b)

Physical layer PHY downlink control information DCI.

14. The method of any one of claims 5 to 7, wherein one of the following applies:

The signal or channel is a physical downlink shared channel, PDSCH, and the first scheduling offset is K0;

The signal or channel is a physical uplink shared channel, PUSCH, and the first scheduling offset is K2; or (b)

The signal or channel is a channel state information reference signal, CSI-RS, and the first scheduling offset is an aperiodic trigger offset.

15. A method performed by a network node in a Radio Access Network (RAN) in communication between a UE and the network node, the method comprising:

transmitting (1130) to the UE an indication that a minimum scheduling offset between a scheduling physical downlink control channel, PDCCH, and a signal or channel scheduled via the scheduling PDCCH will change after a first duration;

then transmitting (1140) a scheduling PDCCH to schedule the signal or channel to the UE for the UE;

determining (1150) a scheduling offset based on whether the scheduling PDCCH is transmitted during or after the first duration; and

The signal or channel is transmitted or received (1160) at the determined scheduling offset after the scheduling PDCCH.

16. The method of claim 15, wherein the first duration relates to a time required for the UE to switch from a first operating configuration to a second operating configuration.

17. The method of claim 15, wherein determining (1150) the scheduling offset comprises:

Selecting (1151) a first scheduling offset if the scheduling PDCCH is transmitted during the first duration; and

If the scheduling PDCCH is transmitted after the first duration, a second scheduling offset is selected (1152).

18. The method of claim 17, wherein the second scheduling offset is less than the first scheduling offset.

19. The method of claim 18, wherein,

The second scheduling offset includes zero or more symbols within the same slot as the scheduling PDCCH; and

The first scheduling offset includes one or more slots or one or more symbols within the same slot.

20. The method of claim 18, wherein,

The second scheduling offset includes one or more time slots; and

The first scheduling offset includes two or more slots.

21. The method of any of claims 15 to 20, wherein the first duration is based on one of:

an initial scheduling, PDCCH, for the UE after transmitting the indication; and

An initial plurality of scheduling PDCCHs for the UE after transmitting the indication.

22. The method of any of claims 15-20, wherein the first duration is based on a second plurality of PDCCH monitoring occasions associated with the UE during one of:

After sending the indication; or alternatively

A third plurality of PDCCH monitoring occasions associated with the UE after the indication is sent,

Wherein the third plurality is greater than the second plurality.

23. The method according to any one of claims 15 to 20, wherein,

The method further comprises the steps of: receiving (1110) an indication of a processing time required for PDCCH decoding from the UE; and

The minimum scheduling offset is greater than the indicated processing time.

24. The method according to any one of claims 15 to 20, wherein,

The method further comprises the steps of: -sending (1120) a configuration message identifying one or more candidate scheduling offsets to the UE;

the transmitted indication identifies one of the candidate scheduling offsets as the minimum scheduling offset applicable after the end of the first duration.

25. The method of claim 24, wherein,

The configuration message is a radio resource control, RRC, message; and

The indication is sent via one of:

A medium access control MAC control element CE; or (b)

Physical layer PHY downlink control information DCI.

26. The method of any one of claims 17 to 20, wherein one of the following applies:

The signal or channel is a physical downlink shared channel, PDSCH, and the first scheduling offset is K0;

The signal or channel is a physical uplink shared channel, PUSCH, and the first scheduling offset is K2; or (b)

The signal or channel is a channel state information reference signal, CSI-RS, and the first scheduling offset is an aperiodic trigger offset.

27. A user equipment, UE, (120, 1300, 1510) configured for communication with a network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530), the UE comprising:

transceiver circuitry (1340) configured to communicate with the network node; and

A processing circuit (1310) operatively coupled to the transceiver circuit, whereby the

The processing circuitry and the transceiver circuitry are configured to perform operations corresponding to the method of any one of claims 1 to 14.

28. A user equipment, UE, (120, 1300, 1510) configured for communication with a network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530), the UE being further arranged to perform operations corresponding to the method of any of claims 1 to 14.

29. A non-transitory computer readable medium (1320) storing computer executable instructions which, when executed by a processing circuit (1310) of a user equipment, UE, (120, 1300, 1510) configured for communication with a network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530), configure the UE to perform operations corresponding to the method of any of claims 1 to 14.

30. A computer program product (1321) comprising computer executable instructions which, when executed by processing circuitry (1310) of a user equipment, UE, (120, 1300, 1510) configured for communication with a network node (105, 110, 115, 1200, 1250, 1400) in a radio point access network, RAN, (100, 1299, 1530), configure the UE to perform operations corresponding to the method of any of claims 1 to 14.

31. A network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530) configured for communication between a UE and the network node, the network node comprising:

radio network interface circuitry (1440) configured to communicate with the UE; and

Processing circuitry (1410) operatively coupled to the radio network interface circuitry, whereby the processing circuitry and the radio network interface circuitry are configured to perform operations corresponding to the method of any of claims 15 to 26.

32. A network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530) configured for communication between a UE and the network node, the network node further being arranged to perform operations corresponding to the method of any of claims 15 to 26.

33. A non-transitory computer-readable medium (1420) storing computer-executable instructions which, when executed by a processing circuit (1410) of a network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530) configured for communication between a UE and the network node, configure the network node to perform operations corresponding to the method of any of claims 15 to 26.

34. A computer program product (1421) comprising computer executable instructions which, when executed by processing circuitry (1410) of a network node (105, 110, 115, 1200, 1250, 1400) in a radio access network, RAN, (100, 1299, 1530) configured for communication between a UE and the network node, configure the network node to perform operations corresponding to the method of any of claims 15 to 26.