Apriori information of time-domain data allocation

Abstract

A method, system and apparatus are disclosed According to some embodiments, a network node configured to communicate with a user equipment, UE, is provided. The network node is configured to transmit, to the UE, a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel, PDSCH, transmission. The network node is configured to indicate, to the UE, constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration and, to transmit at least one PDSCH according to the constrained allocation information.

Description

[0001] APRIORI INFORMATION OF TIME-DOMAIN DATA ALLOCATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, for resource allocation between a network node and a user equipment.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and user equipments (UEs), as well as communication between network nodes and between UEs. The 3 GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] UE and network energy consumption are several metrics to consider. In general, significant energy is spent by the UE in Radio Resource Control CONNECTED (RRC CONNECTED) mode on monitoring the Physical Downlink Control Channel (PDCCH) in NR for potentially scheduled Physical Downlink Shared Channel (PDSCH) / Physical Uplink Shared Channel (PUSCH). The UE needs to decode all PDCCH occasions / Time-Frequency (T / F) locations / configurations according to a search space. After decoding according to each blind decoding (BD) option, the UE can check whether the PDCCH was meant for it, based on checking the cyclic redundancy check (CRC) using its cell radio network temporary identifier (C-RNTI). If so, the UE follows the information within the Downlink Control Information (DCI) carried over the PDCCH. Similarly, from the network perspective, significant energy is consumed on scheduling data for various UEs. Techniques that can reduce the transmission and / or reception timelines allow both the UE and network to utilize the gaps in-between the occasions for various sleep states depending on gap length.

[0007] For downlink (DL) data transmission and resource allocation, the network (e.g., network node) schedules the UE for PDSCH reception via PDCCH DCI. In the DCI, the UE is notified about time / frequency (T / F) resources which is going to be used for the PDSCH data transmission. When it comes to the time-domain resources, the UE is preconfigured with the information about the resources via higher layer signaling (either via Radio Resource Control (RRC) signaling or based on prespecified tables in the 3GPP standard specification). Typically though, this is performed by RRC signaling via the information element (IE) PDSCH- TimeDomainAllocationlist. Via this IE, the network can preconfigure the time domain relation between PDCCH (DCI) and PDSCH, including the following parameters (see, e.g., 3GPP TS 38.331 Rel. 17):

[0008] • slot offset (KO),

[0009] • PDSCH Mapping Type (typeA, typeB)

[0010] • starting symbol and a number of allocated symbols (the length).

[0011] From 3GPP TS 38.331 Rel. 17, V17.6.0 (2023-09):

[0012] Later, upon DL data provision, the network indicates in the DL assignment DCI which of the preconfigured time domain allocations the UE applies for that DL assignment. The typeA allocation is sometimes referred to as “slot” based scheduling occupying up to the complete slot in time and typically used for enhanced mobile broadband (eMBB) type of applications, whereas the typeB allocation is sometimes referred to as “Mini-slot” based scheduling and may occupy resources up to 7 symbols and suitable for ultra reliable low latency communication (URLLC) application where critical data needs to be provided to the UEs with minimal latency. Furthermore, typically, the network also configures the slot offset (KO) such that K0=0 is included in the configuration, meaning that PDCCH and PDSCH are provided within the same slot.

[0013] In certain scenarios (e.g., for the sake of network energy savings), the network may in each slot schedule the PDSCH data in fewer symbols than the full slot. Instead, if the system load is low enough and / or if there are enough frequency resources available, the PDSCH timeline is “squeezed” and instead the UE can be scheduled over more frequency resources. As such there is a transmission time gap created (the remaining symbols until the end of the slot) which can be used for putting certain parts of the hardware, such as the Power Amplifier (PA), etc., to sleep.

[0014] Even though the network node can utilize the empty symbols for relaxing / sleeping certain parts of the hardware, the UE cannot necessarily utilize the empty symbols as a sleep opportunity. The reason is that whenever K0=0 and typeA (“slot-based”) with many symbols (typically the complete slot) is configured, the UE has to, within its search space occasions, always be prepared for that a potentially decoded DCI may point to PDSCH occupying the maximum number of configured symbols as shown in FIG. 1, where the top part illustrates an actual transmission from the network and the bottom part illustrates that the UE is actually prepared for the maximum configured symbols / the whole slot.

[0015] Furthermore, as it takes time for the UE to decode the PDCCH, the UE typically needs to keep its receiver open and record potential PDSCH data as illustrated in FIG. 2 and FIG. 3. However, even if the network node only allocated PDSCH in fewer symbols than the maximum values configured, the UE would still not benefit from it as the UE receiver (RX) still needs to record potential PDSCH data for an unnecessarily long time, as shown in FIG. 2 and FIG. 3 which illustrate that the UE needs to receive and record (or read) PDSCH samples at least during the PDCCH (DCI) decoding delay, since the actual number of scheduled PDSCH symbols is only known after DCI decoding. The DCI decoding delay is typically a considerable fraction of the slot duration, up to the full slot duration. The dashed lines illustrate the end of the recording. The UE hence has to process the recorded PDSCH samples according to the largest one of the maximum number of either the configured PDSCH symbols or the PDCCH decoding delay. Specifically, FIG. 3 illustrates an example where the UE in fact has recorded samples for too many potential PDSCH symbols due to a long PDCCH (DCI) decoding delay, although only a small number of these symbols were actually allocated to the current PDSCH transmission.

[0016] Hence, existing systems suffer from one or more inefficiencies that may negatively affect power consumption.

[0017] SUMMARY

[0018] Some embodiments advantageously provide methods, systems, and apparatuses for apriori information for power savings.

[0019] According to one or more embodiments, the network node dynamically provides apriori information (e.g., constrained allocation information) to the UE about PDSCH maximum time domain allocation size for upcoming transmissions. According to this apriori information, the UE is informed about a constrained allocation that is shorter than the total number of available symbols in a slot or another preconfigured / prespecified allocation. As such, the UE can avoid receiving / recording more symbols than necessary, to increase the receiver (RX) sleep opportunities and save power. The network node may then schedule upcoming downlink (DL) transmissions to the UE so that the number of scheduled PDSCH symbols does not exceed the indicated constraint.

[0020] The time domain duration of the transmitted signal is reduced, and as such network energy savings is advantageously provided.

[0021] In one embodiment, this information is provided to the UE via a MAC Control Element (MAC-CE) indicating that, until further notice, the time domain allocation for PDSCH will be confined to a certain value.

[0022] The UE may use the apriori constraint information to configure the receiver to not read / record more PDSCH symbols than the indicated constraint.

[0023] According to one aspect, a network node is provided that is configured to communicate with a user equipment (UE), is configured to transmit, to the UE, a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel (PDSCH) transmission. The network node is configured to indicate, to the UE, constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration. The network node is configured to transmit at least one PDSCH according to the constrained allocation information.

[0024] According to another aspect, a method is provided that is performed by a network node that is configured to communicate with a user equipment, UE. The method comprises transmitting, to the UE, a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel (PDSCH) transmission. The method comprises indicating, to the UE, constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available PDSCH transmission of the first configuration. The method comprises transmitting at least one PDSCH according to the constrained allocation information.

[0025] According to yet another aspect, a user equipment (UE) is provided, that is configured to communicate with a network node. The UE is configured to receive a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel (PDSCH) transmission. The UE is configured to receive constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration. The UE is configured to receive at least one PDSCH transmission according to the constrained allocation information.

[0026] According to still another aspect, a method is provided that is performed by a user equipment (UE) that is configured to communicate with a network node. The method comprises receiving a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel (PDSCH) transmission. The method comprises receiving constrained allocation information that indicates that at least one future allocation of PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration. The method comprises receiving at least one PDSCH transmission according to the constrained allocation information.

[0027] BRIEF DESCRIPTION OF THE DRAWINGS

[0028] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0029] FIG. l is a diagram of an example actual transmission versus what the UE is prepared to receive;

[0030] FIG. 2 is a diagram of an example UE decoding of the PDCCH for recording PDSCH;

[0031] FIG. 3 is a diagram of another example UE decoding of the PDCCH for recording PDSCH; FIG. 4 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein; FIG. 5 is a block diagram of a network node in communication with a UE over a wireless connection according to some embodiments of the present disclosure;

[0032] FIG. 6 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0033] FIG. 7 is a flowchart of an example process in a UE according to some embodiments of the present disclosure; and

[0034] FIG. 8 is a diagram of the effects of the apriori information according to some embodiments of the present disclosure.

[0035] DETAILED DESCRIPTION

[0036] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to apriori (e.g., “a priori”) information for power savings. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0037] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0038] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0039] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0040] The term “apriori information” may denote the time-domain scheduling constraint information provided by the network or network node to the UE. Alternative terms that could be used for this information may include “assistance information”, “configuration information”, “guidance information”, “constraint information”, “constrained allocation information”, etc.

[0041] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a UE or a radio network node.

[0042] In some embodiments, the non-limiting terms wireless device or a user equipment (UE) may be used interchangeably. The UE herein can be any type of UE capable of communicating with a network node or another UE over radio signals, such as UE. The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc. Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0043] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems may also benefit from exploiting the ideas covered within this disclosure.

[0044] Note further, that functions described herein as being performed by a UE or a network node may be distributed over a plurality of UEs and / or network nodes. In other words, it is contemplated that the functions of the network node and UE described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0045] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is 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 unless expressly so defined herein.

[0046] Some embodiments are directed to apriori information for power savings.

[0047] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 4 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first UE 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as UEs 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0048] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTEZE-UTRAN and a gNB for NR / NG-RAN.

[0049] A network node 16 (eNB or gNB) is configured to include an indication unit 24 which is configured to perform one or more network node 16 functions as described herein such as with respect to apriori information. A UE 22 is configured to include a mode unit 26 which is configured to perform one or more UE 22 functions as described herein such as with respect to apriori information for power savings or a power saving mode.

[0050] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 5.

[0051] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0052] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0053] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include indication unit 24 which is configured to perform one or more network node 16 functions as described herein such as with respect to apriori information.

[0054] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0055] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0056] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22. The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the UE 22 may include mode unit 26 which is configured to perform one or more UE 22 functions as described herein such as with respect to apriori information for power savings or a power savings mode.

[0057] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 5 and independently, the surrounding network topology may be that of FIG. 4.

[0058] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may advantageously improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0059] Although FIGS. 4 and 5 show various “units” such as indication unit 24 and mode unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0060] FIG. 6 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the indication unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to transmit (Block 100) to the UE a first configuration of time domain resources that comprise a maximum number of symbols available for physical downlink shared channel (PDSCH) transmission. This first configuration is for example provided according to PDSCH- TimeDomainResourceAllocationList and PDSCH-TimeDomainResourceAllocation of 3GPP TS 38.331 Rel. 17, V17.6.0 (2023-09). Network node 16 is configured to indicate (Block S 101), to the UE 22, constrained allocation information (e.g., apriori information) that indicates that at least one future allocation of a physical downlink shared channel (PDSCH) transmission comprises less or fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration, as described herein. Network node 16 is further configured to transmit, to the UE, (Block SI 02) at least one PDSCH according to the constrained allocation information, as described herein. Accordingly, the network node 16 (e.g., gNB), provides apriori information to the UE 22 about a constrained time domain allocation of symbols for one or more upcoming PDSCH transmissions, which is shorter than the unconstrained maximum possible number of PDSCH symbols per configured transmission.

[0061] According to one or more embodiments, the constrained allocation information further indicates at least one of: a validity timer indicating a time period for which the constrained allocation information is valid, and a number of scheduled PDSCH transmissions for which the constrained allocation information is valid, or a number of scheduling occasions in a search space. For example, the number of scheduling occasions in the search space may correspond to the number of scheduling occasions in the search space, irrespective of whether they are utilized or not.

[0062] The apriori information contents (constrained allocation information) may comprise a maximum number of scheduled PDSCH symbols in a constrained mode or an index to a preconfigured maximum number value.

[0063] The apriori information contents (constrained allocation information) may comprise a validity timer (in e.g. ms or slots) for how long the apriori information is valid before going back to another (e.g. default) configuration, or an index to a preconfigured validity timer value.

[0064] The apriori information contents (constrained allocation information) may comprise a number of actually scheduled transmissions or potential transmissions, or an index to such preconfigured information.

[0065] According to one or more embodiments, the constrained allocation information is indicated to the UE 22 via one of: medium access control-control element (MAC-CE) signaling, downlink control information (DCI) signaling, and radio resource control (RRC), signaling.

[0066] According to one or more embodiments, the constrained allocation information comprises at least one pre-configuration, where the constrained allocation information is valid while the UE 22 is operating according to the at least one preconfiguration, and where the at least one preconfiguration being associated with at least one of: a search space and / or a coreset, a bandwidth part (BWP), a service bearer, or a service with a certain quality of service, QoS (e.g., a 5G QoS identifier (5QI)).

[0067] According to one or more embodiments, the transmitting of at least one PDSCH according to the constrained allocation information comprises transmitting using a number of PDSCH symbols that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

[0068] According to one or more embodiments, the network node 16 is further configured to receive UE capability information associated with the UE 22 and determine the constrained allocation information based at least on the UE capability information. According to one or more embodiments, the network node 16 is further configured to indicate that the constrained allocation information is no longer valid.

[0069] FIG. 7 is a flowchart of an example process in a UE 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of UE 22 such as by one or more of processing circuitry 50 (including the mode unit 26), processor 52, and / or radio interface 46. UE 22 is configured to receive (Block 103) a first configuration of time domain resources. The time domain resources comprise a maximum number of symbols available for physical downlink shared channel (PDSCH) transmission. This first configuration is for example provided according to PDSCH- TimeDomainResourceAllocationList and PDSCH-TimeDomainResourceAllocation of 3GPP TS 38.331 Rel. 17, V17.6.0 (2023-09). The UE 22 is configured to receive (Block S104) constrained allocation information that indicates that at least one future allocation of a physical downlink shared channel (PDSCH) transmission comprises less or fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration, as described herein. The UE 22 is configured to receive (SI 05) at least one PDSCH transmission according to the constrained allocation information, as described herein.

[0070] In some embodiments, UE 22 may further be configured to cause (Block SI 06) a receiver of the UE to temporarily enter a sleep state based on the constrained allocation information, as described herein. In some embodiments, UE 22 may be configured to cause one or more elements (e.g., hardware and / or software elements) to, at least temporally, enter a sleep mode or to operate in low power based on the constrained allocation information.

[0071] According to one or more embodiments, the sleep state occurs at least partially during symbols in the at least one future PDSCH transmission. For example, the sleep state may occur at least partially during later symbols in a slot where an earlier part of the slot contained scheduled PDSCH symbols.

[0072] According to one or more embodiments, the constrained allocation information allows the UE 22 to avoid receiving and / or recording more PDSCH symbols than indicated in the constrained allocation information.

[0073] According to one or more embodiments, the constrained allocation information further indicates at least one of: a validity timer indicating a time period for which the constrained allocation information is valid, and a number of scheduled PDSCH transmissions for which the constrained allocation information is valid, or a number of scheduling occasions in a search space.

[0074] According to one or more embodiments, the constrained allocation information is received via one of: medium access control -control element (MAC-CE) signaling, downlink control information signaling, and radio resource control (RRC) signaling.

[0075] According to one or more embodiments, the constrained allocation information comprises at least one pre-configuration, where the constrained allocation information is valid while the UE is operating according to the at least one preconfiguration, and where the at least one preconfiguration is associated with at least one of: a search space and / or a coreset, a bandwidth part (BWP), a service bearer, or a service with a certain QoS (e.g., 5QI).

[0076] According to one or more embodiments, the UE 22 is further configured to receive at least one PDSCH transmission where a number of PDSCH symbols in the PDSCH transmission that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

[0077] According to one or more embodiments, the UE 22 is further configured to transmit UE capability information to the network node, where the constrained allocation information is based at least on the UE capability information. That is, in some embodiments, the UE capability information can be used by network node 16 for determining the constrained allocation information.

[0078] According to one or more embodiments, the UE 22 is further configured to receive an indication that the constrained allocation information is no longer valid.

[0079] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for apriori information configuration and / or communication.

[0080] Some embodiments provide apriori information configuration and / or communication.

[0081] One or more embodiments described herein helps the UE 22 to conserve energy at occasions in which the network (e.g., network node 16) uses fewer symbols in its PDSCH transmission than the maximum value provided / indicated earlier to the UE 22 via RRC dedicated / broadcast signaling which is static in nature and not frequently updated. This is performed through one or more methods by which the network node dynamically provides apriori information to the UE 22 about PDSCH maximum time domain allocation size for upcoming transmissions. The dynamic signaling described herein is motivated by that notion that the instantaneous strategy of the network node 16 for time-domain symbol allocation may change relatively frequently based on network energy savings (NES) considerations. Via this apriori information, the UE 22 is informed about a constrained allocation that is shorter than the total number of available symbols in a slot and shorter than the maximum value preconfigured and / or prespecified.

[0082] Consider the following example. In a default solution (in a “legacy”, unconstrained operation), any given scheduling DCI instance may allocate anywhere between 1-13 PDSCH symbols. The UE will not know that value ahead of receiving and decoding the PDCCH / DCI, and there are no guarantees even if the network node during some time intervals, e.g. during an energy saving mode operation or low-load operation, only chooses to use e.g. symbols 1-6 for any PDSCH transmission, and not use e. g. symbols 7-13. However, according to the embodiments herein, the UE will receive apriori maximum allocation (upper bound or constraint) information, e.g. that it will be scheduled for between 1 to 6 symbols, but not more than these 6 symbols. The UE may then choose to not operate its receiver and not record or receive additional PDSCH symbols beyond these 6 symbols, in this example. In other examples, the apriori information could be a different maximum allocation, e.g. 2, 4, or any other value up to 12.

[0083] Accordingly, the UE 22 can avoid receiving and / or recording more symbols than necessary, thereby allowing UE 22 to increase the RX sleep opportunities and reduce the receiver activity. The network node 16 then schedules upcoming DL transmissions to UE 22 so that the number of scheduled PDSCH symbols does not exceed the indicated constraint (e.g. the maximum number of scheduled PDSCH symbols). UE 22 may then use the apriori constraint information to configure the receiver (RX) to not read and / or record more PDSCH symbols than the indicated constraint. In various embodiments, the apriori information is provided to UE 22 via lower layer signaling such as via a MAC-CE or DCI.

[0084] The apriori information and / or configuration contents comprise one or more of:

[0085] • a maximum number of scheduled PDSCH symbols in the constrained mode, or an index to a preconfigured value;

[0086] • a validity timer (in ms, seconds, slots, frame, etc.) for how long the apriori information is valid before going back to another (e.g. default) configuration, or an index to a preconfigured validity timer value;

[0087] • a number of actually scheduled transmissions or potential transmissions, or an index to such preconfigured information. For example, the apriori information is valid for the upcoming X (e.g., X=10) transmissions, or the upcoming X valid slots in the search space irrespective of whether transmission occurs. The information and / or configuration may either be carried in the lower layer signaling itself, or preconfigured (e.g., via RRC signaling), and upon the reception of the lower layer signaling, UE 22 retrieves and applies the information and / or configuration.

[0088] Alternately, or additionally, the apriori information is preconfigured (e.g., via RRC signaling) and associated with one or more of: a search space and / or a coreset, a bandwidth part (BWP), a service bearer, or a service with a certain quality of service (QoS) (e.g., a 5G QoS identifier (5QI)), and whereby the apriori information is valid while UE 22 is operating according to the associated configuration. For example, when UE 22 is commanded to a specific BWP, it knows that the maximum number of PDSCH symbols will be according to another configuration while UE 22 is in that BWP.

[0089] In one embodiment, the apriori information is provided to the UE via lower layer signaling (e.g., via MAC-CE or DCI). In another embodiment the apriori information is provided to the UE via higher layer RRC signaling, instead of via lower layer signaling. As such, the UE is RRC reconfigured each time the network (NW) intends to use fewer / more symbols in its PDSCH allocation.

[0090] Based on above apriori information, UE 22 then knows that network node 16 uses a number of symbols for PDSCH allocation that does not exceed the maximum value provided in the apriori information.

[0091] Further, in some embodiments, different UEs 22 may have different capabilities with respect to PDCCH processing timelines. For example, some UEs 22 may be equipped with higher performing hardware that can process PDCCH faster than other UEs 22. Therefore, in some embodiments, the network configuration of the constrained mode and the providing of apriori information is UE- or UE-group-specific, and / or provided to a subset of UEs 22 or UE groups. For example, some UEs 22 may not even need such information in case they are already capable of processing PDCCH faster than the duration of constrained PDSCH symbol set transmission and go to sleep without the need for such apriori information. There could be various methods for the network to become aware of various UEs’ capabilities in relation to PDCCH processing time, and some examples are:

[0092] • The UE capability is provided to the network by UE 22 itself based on UE signaling.

[0093] • The network is configured with various UEs 22s (e.g., models, software (SW) versions, etc.) via a configuration such as via Operation and Maintenance (O&M) systems.

[0094] • The UE capability is obtained based on prespecified implementation type (that may be hardcoded in the implementation, e.g., in a database). For example, the network identifies the UE type when and / or upon connection and within its implementation it knows about the capability of such UE type. The network configures UE 22 to receive the apriori information, comprising whether to monitor the apriori signaling, group allocation (e.g., if the indication is group-specific such as a group-common DCI), etc. In one embodiment, the network receives a UE 22 preference signaling (e.g., via UE Assistance Information (UAI) signaling or via a MAC-CE, or alike) for the maximum number of PDSCH symbols to be used. Optionally, different preferences can be provided for various associated configurations (e.g., BWPs, Search space groups, Carriers, etc.). The UE 22 may hence signal, to the network, preference information (e.g., via UAI signaling) about the preferred number of time-domain PDSCH symbols to allocate, and / or the preferred constrained symbol allocation limit.

[0095] The UE 22 may signal, to the network, capability information that is related PDCCH decoding latency, and / or whether receiving the apriori information is useful.

[0096] In all embodiments above, the network may further indicate to UE 22 that the previously indicated constrained symbol allocation is cancelled and regular (unconstrained) allocation is resumed.

[0097] Based on the received information, UE 22 reduces its receiver activity related to PDSCH sampling even though it still has not completed its PDCCH processing, i.e., upon receiving the apriori information, for scheduling occasions when the information is valid, UE 22 omits its receiver operation during PDSCH symbols that are outside the constrained time-domain allocation. The UE 22 may hence omit its receiver operation during PDSCH symbols that are outside the constrained time-domain allocation upon receiving the apriori information, for scheduling occasions when the information is valid.

[0098] This advantageous effect is illustrated in FIG. 8, where on the left-hand side, the typical UE implementation is depicted, whereas on the right-hand side the beneficial shortening of UE RX activity, according to some embodiments of the present disclosure, is depicted. The left-hand side of FIG. 8 illustrates that the UE receiver needs to record or read the PDSCH unnecessarily long time if the PDSCH was allocated only in a few symbols. On the other hand, the right-hand side illustrates that the UE receiver only records or reads PDSCH symbols (where the dashed line illustrates the end of the PDSCH recording) according to the PDSCH symbol allocation constraint based on the apriori information. According to one or more embodiments, the above signaling steps and contents may be standardized, e.g., in 3GPP, or applied via proprietary coordination between a UE 22 / chipset vendor and a network vendor.

[0099] One or more examples and / or embodiments advantageously allows and / or configures the UE such that it can receive fewer symbols and enter a sleep state, such as micro-sleep, in between the slots, which allows for power savings and rather than keeping the UE receiver open during the entire slot and sample potentially unnecessary symbols. As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0100] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0101] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0102] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0103] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0104] Computer program code for carrying out operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the “C” programming language. The program code may execute entirely on the user’s computer, partly on the user’s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0105] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0106] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

[0107] Further enumerated embodiments:

[0108] Embodiment Al . A network node configured to communicate with a user equipment, UE, the network node configured to: indicate, to the UE, constrained allocation information that indicates at least one future physical downlink shared channel, PDSCH, transmission that comprises less symbols than a previous PDSCH transmission; and transmit at least one PDSCH according to the constrained allocation information.

[0109] Embodiment A2. The network node of Embodiment Al, wherein the constrained allocation information indicates at least one of: a maximum number of scheduled PDSCH symbols; a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space.

[0110] Embodiment A3. The network node of any one of Embodiments A1-A2, wherein the constrained allocation information is indicated to the UE via one of: medium access controlcontrol element, MAC-CE, signaling; downlink control information signaling; and radio resource control, RRC, signaling.

[0111] Embodiment A4. The network node of any one of Embodiments A1-A3, wherein the constrained allocation information comprises at least one preconfiguration, the constrained allocation information is valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

[0112] Embodiment A5. The network node of any one of Embodiments A1-A4, wherein the transmitting of at least one PDSCH according to the constrained allocation information comprises transmitting using a number of PDSCH symbols that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

[0113] Embodiment A6. The network node of any one of Embodiments A1-A5, wherein the network node is further configured to: receive UE capability information associated with the UE; and determine the constrained allocation information based at least on the UE capability information.

[0114] Embodiment A7. The network node of any one of Embodiments A1-A6, wherein the network node is further configured to indicate that the constrained allocation information is no longer valid.

[0115] Embodiment Bl. A method performed by a network node that is configured to communicate with a user equipment, UE, the method comprising: indicating, to the UE, constrained allocation information that indicates at least one future physical downlink shared channel, PDSCH, transmission that comprises less symbols than a previous PDSCH transmission; and transmitting at least one PDSCH according to the constrained allocation information.

[0116] Embodiment B2. The method of Embodiment Bl, wherein the constrained allocation information indicates at least one of: a maximum number of scheduled PDSCH symbols; a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space. Embodiment B3. The method of any one of Embodiments B1-B2, wherein the constrained allocation information is indicated to the UE via one of: medium access controlcontrol element, MAC-CE, signaling; downlink control information signaling; and radio resource control, RRC, signaling.

[0117] Embodiment B4. The method of any one of Embodiments B1-B3, wherein the constrained allocation information comprises at least one pre-configuration, the constrained allocation information is valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

[0118] Embodiment B5. The method of any one of Embodiments B1-B4, wherein the transmitting of at least one PDSCH according to the constrained allocation information comprises transmitting using a number of PDSCH symbols that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

[0119] Embodiment B6. The method of any one of Embodiments B1-B5, further comprising: receiving UE capability information associated with the UE; and determining the constrained allocation information based at least on the UE capability information.

[0120] Embodiment B7. The method of any one of Embodiments B1-B6, further comprising indicating that the constrained allocation information is no longer valid.

[0121] Embodiment Cl. A user equipment, UE, configured to communicate with a network node, the UE configured to: receive constrained allocation information that indicates at least one future physical downlink shared channel, PDSCH, transmission that comprises less symbols than a previous PDSCH transmission; and cause a receiver of the UE to temporarily enter a sleep state based on the constrained allocation information.

[0122] Embodiment C2. The UE of Embodiment Cl, wherein the sleep state occurs at least partially during symbols in the at least one future PDSCH transmission.

[0123] Embodiment C3. The UE of any one of Embodiments C1-C2, wherein the constrained allocation information allows the UE to avoid receiving and / or recording more PDSCH symbols than indicated in the constrained allocation information.

[0124] Embodiment C4. The UE of any one of Embodiments C1-C3, wherein the constrained allocation information indicates at least one of: a maximum number of scheduled PDSCH symbols; a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space. Embodiment C5. The UE of any one of Embodiments C1-C4, wherein the constrained allocation information is received via one of: medium access control -control element, MAC-CE, signaling; downlink control information signaling; and radio resource control, RRC, signaling.

[0125] Embodiment C6. The UE of any one of Embodiments C1-C5, wherein the constrained allocation information comprises at least one pre-configuration, the constrained allocation information being valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

[0126] Embodiment C7. The UE of any one of Embodiments C1-C6, wherein the UE is further configured to receive at least one PDSCH transmission where a number of PDSCH symbols in the PDSCH transmission that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

[0127] Embodiment C8. The UE of any one of Embodiments C1-C7, wherein the UE is further configured to transmit UE capability information to the network node, the constrained allocation information being based at least on the UE capability information.

[0128] Embodiment C9. The UE of any one of Embodiments C1-C7, wherein the UE is further configured to receive an indication that the constrained allocation information is no longer valid.

[0129] Embodiment DI . A method performed by a user equipment, UE, that is configured to communicate with a network node, the method comprising: receiving constrained allocation information that indicates at least one future physical downlink shared channel, PDSCH, transmission that comprises less symbols than a previous PDSCH transmission; and causing a receiver of the UE to temporarily enter a sleep state based on the constrained allocation information.

[0130] Embodiment D2. The method of Embodiment DI, wherein the sleep state occurs at least partially during symbols in the at least one future PDSCH transmission.

[0131] Embodiment D3. The method of any one of Embodiments D1-D2, wherein the constrained allocation information allows the UE to avoid receiving and / or recording more PDSCH symbols than indicated in the constrained allocation information.

[0132] Embodiment D4. The method of any one of Embodiments D1-D3, wherein the constrained allocation information indicates at least one of: a maximum number of scheduled PDSCH symbols; a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space.

[0133] Embodiment D5. The method of any one of Embodiments D1-D4, wherein the constrained allocation information is received via one of: medium access control -control element, MAC-CE, signaling; downlink control information signaling; and radio resource control, RRC, signaling.

[0134] Embodiment D6. The method of any one of Embodiments D1-D5, wherein the constrained allocation information comprises at least one pre-configuration, the constrained allocation information being valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

[0135] Embodiment D7. The method of any one of Embodiments D1-D6, further comprising receiving at least one PDSCH transmission where a number of PDSCH symbols in the PDSCH transmission that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

[0136] Embodiment D8. The method of any one of Embodiments D1-D7, further comprising transmitting UE capability information to the network node, the constrained allocation information being based at least on the UE capability information.

[0137] Embodiment D9. The method of any one of Embodiments D1-D7, further comprising receiving an indication that the constrained allocation information is no longer valid.

Claims

CLAIMS:

1. A network node (16) configured to communicate with a user equipment, UE, (22) the network node configured to: transmit, to the UE, a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel, PDSCH, transmission; indicate, to the UE, constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration; and transmit at least one PDSCH according to the constrained allocation information.

2. The network node of claim 1, wherein the constrained allocation information indicates at least one of: a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space.

3. The network node of any one of claims 1-2, wherein the constrained allocation information is indicated to the UE via one of: medium access control-control element, MAC-CE, signaling; downlink control information, DCI, signaling; and radio resource control, RRC, signaling.

4. The network node of any one of claims 1-3, wherein the constrained allocation information comprises at least one preconfiguration, the constrained allocation information is valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

5. The network node of any one of claims 1-4, wherein the transmitting of at least one PDSCH according to the constrained allocation information comprises transmitting using a number of PDSCH symbols that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

6. The network node of any one of claims 1-5, wherein the network node is further configured to: receive UE capability information associated with the UE; and determine the constrained allocation information based at least on the UE capability information.

7. The network node of any one of claims 1-6, wherein the network node is further configured to indicate that the constrained allocation information is no longer valid.

8. A method performed by a network node (16) that is configured to communicate with a user equipment, UE, the method comprising: transmitting (SI 00), to the UE, a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel, PDSCH, transmission; indicating (SI 01), to the UE, constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available PDSCH transmission of the first configuration; and transmitting (SI 02) at least one PDSCH according to the constrained allocation information.

9. The method of claim 8, wherein the constrained allocation information indicates at least one of: a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space.

10. The method of any one of claims 8-9, wherein the constrained allocation information is indicated to the UE via one of:medium access control -control element, MAC-CE, signaling; downlink control information signaling, DCI; and radio resource control, RRC, signaling.

11. The method of any one of claims 8-10, wherein the constrained allocation information comprises at least one pre-configuration, the constrained allocation information is valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

12. The method of any one of claims 8-11, wherein the transmitting of at least one PDSCH according to the constrained allocation information comprises transmitting using a number of PDSCH symbols that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

13. The method of any one of claims 8-12, further comprising: receiving UE capability information associated with the UE; and determining the constrained allocation information based at least on the UE capability information.

14. The method of any one of claims 8-13, further comprising indicating that the constrained allocation information is no longer valid.

15. A user equipment, UE (22), configured to communicate with a network node, the UE configured to: receive a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel, PDSCH, transmission; receive constrained allocation information that indicates that at least one future allocation of a PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration; and receive at least one PDSCH transmission according to the constrained allocation information.

16. The UE of claim 15, wherein the UE is configured to cause a receiver of the UE to temporarily enter a sleep state based on the constrained allocation information.

17. The UE of claim 16 , wherein the sleep state occurs at least partially during symbols that are indicated as not to be allocated in the at least one future PDSCH transmission.

18. The UE of any one of claims 15-16, wherein the constrained allocation information allows the UE to avoid receiving and / or recording more PDSCH symbols than indicated in the constrained allocation information.

19. The UE of any one of one of claims 15-18, wherein the constrained allocation information indicates at least one of: a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space.

20. The UE of any one of one of claims 15-19, wherein the constrained allocation information is received via one of: medium access control-control element, MAC-CE, signaling; downlink control information, DCI, signaling; and radio resource control, RRC, signaling.

21. The UE of any one of one of claims 15-20, wherein the constrained allocation information comprises at least one pre-configuration, the constrained allocation information being valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

22. The UE of any one of one of claims 15-21, wherein the UE is further configured to receive at least one PDSCH transmission where a number of PDSCH symbols in the PDSCH transmission that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

23. The UE of any one of one of claims 15-22, wherein the UE is further configured to transmit UE capability information to the network node, the constrained allocation information being based at least on the UE capability information.

24. The UE of any one of one of claims 15-23, wherein the UE is further configured to receive an indication that the constrained allocation information is no longer valid.

25. A method performed by a user equipment, UE (22), that is configured to communicate with a network node, the method comprising: receiving (SI 03) a first configuration of time domain resources, comprising a maximum number of symbols available for physical downlink shared channel, PDSCH, transmission; receiving (SI 04) constrained allocation information that indicates that at least one future allocation of PDSCH transmission comprises fewer symbols than the maximum number of symbols available for PDSCH transmission of the first configuration; and receiving (SI 05) at least one PDSCH transmission according to the constrained allocation information.

26. The method of claim 25 further comprising causing (SI 06) a receiver of the UE to temporarily enter a sleep state based on the constrained allocation information.

27. The method of any one of claims 25-26, wherein the sleep state occurs at least partially during symbols that are indicated as not to be allocated in the at least one future PDSCH transmission.

28. The method of any one of any one of claims 25-27, wherein the constrained allocation information allows the UE to avoid receiving and / or recording more PDSCH symbols than indicated in the constrained allocation information.

29. The method of any one of any one of claims 25-28, wherein the constrained allocation information indicates at least one of:a validity timer indicating a time period for which the constrained allocation information is valid; a number of scheduled PDSCH transmissions for which the constrained allocation information is valid; or a number of scheduling occasions in a search space.

30. The method of any one of any one of claims 25-29, wherein the constrained allocation information is received via one of: medium access control-control element, MAC-CE, signaling; downlink control information signaling, DCI; and radio resource control, RRC, signaling.

31. The method of any one of any one of claims 25-30, wherein the constrained allocation information comprises at least one pre-configuration, the constrained allocation information being valid while the UE is operating according to the at least one preconfiguration, the at least one preconfiguration being associated with at least one of: a search space and / or a coreset; a bandwidth part, BWP; a service bearer; or a service with a certain quality of service, QoS.

32. The method of any one of any one of claims 25-31, further comprising receiving at least one PDSCH transmission where a number of PDSCH symbols in the PDSCH transmission that does not exceed a maximum value of PDSCH symbols indicated in the constrained allocation information.

33. The method of any one of any one of claims 25-32, further comprising transmitting UE capability information to the network node, the constrained allocation information being based at least on the UE capability information.

34. The method of any one of any one of claims 25-33, further comprising receiving an indication that the constrained allocation information is no longer valid.

Images