WO2024170743A1

WO2024170743A1 - Ue behavior during cell dtx/drx

Info

Publication number: WO2024170743A1
Application number: PCT/EP2024/053996
Authority: WO
Inventors: Ali Nader; Sladana JOSILO; Lian ARAUJO; Helka-Liina MÄÄTTÄNEN; Andres Reial; Ajit Nimbalker; Ravikiran Nory; Sina MALEKI
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-16
Filing date: 2024-02-16
Publication date: 2024-08-22
Anticipated expiration: 2025-08-16
Also published as: EP4666477A1; KR20250145691A

Abstract

A method, system and apparatus are disclosed. In one or more embodiments, a wireless device, WD, (22) configured to communicate with a network node (16) is provided. The WD may receive a cell Discontinuous Transmission, cell DTX, configuration of the network node (16), the cell DTX configuration defining a cell DTX active time. The WD (22) may transmit a Hybrid Automatic Repeat Request, HARQ, negative acknowledgement, NACK, for a downlink, DL, wireless transmission from the network node (16). In response to the HARQ NACK, the WD (22) may monitor for DL re-transmissions from the network node (16) after the cell DTX active time has ended. Further, the WD (22) may receive a cell Discontinuous Reception, cell DRX, configuration of the network node (16), the cell DRX configuration defining a cell DRX active time. The WD (22) may receive a DL wireless transmission from the network node (16) and HARQ feedback for the DL wireless transmission after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time.

Description

UE BEHAVIOR DURING CELL DTX/DRX

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

BACKGROUND

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 mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

Wireless device C-DRX:

Wireless device connected mode DRX (C-DRX) allows the wireless device to transition to a lower power state when it is not required to receive any transmission from the network node. There is an “onDuration” on a periodic basis during which the wireless device is awake and monitors for control channels, and if there is no control message detected by the wireless device, the wireless device can stop receiving transmissions from network node (e.g., no control signal monitoring) until a next onDuration occasion. In case of uplink (UL) transmission, the wireless device is not limited to the onDuration occasions and may transmit on physical uplink control channel (PUCCH) or physical random access channel (PRACH) for UL transmission request.

FIG. 1 is an example diagram of DRX cycles.

Network node energy consumption

Network node energy consumption in NR increases with respect to LTE due to more complex hardware, e.g., higher bandwidth (BW) and a greater number of antennas. This is particularly more evident when the network node operates in higher frequencies. Hence it is important for the network node to turn ON/OFF unused hardware modules during inactivity times. For example, in FR2, an NR network node can be configured with up to 64 beams and transmit up to 64 SSBs. This implies 64 ports with many transceiver chains involved. Such SSBs are transmitted every 20ms in during 5ms windows for providing coverage to potential wireless devices even if there are no wireless devices present in the cell. Another example of energy cost is always- on broadcast transmissions is SIB1 which is typically transmitted (per beam) every 20/40 ms.

Cell DTX/DRX:

Network node or network DTRX or cell DTX/DRX is proposed in 3GPP Release 18 (Rel 18) as a solution in order to help the network to save more power. The idea is that the network in known T/F resources is active or inactive resembling the C- DRX or DRX mechanisms at the wireless device side, and thereby can go into sleep mode during inactive time. Furthermore, it is expected that the wireless device and network node are aligned during this operation.

However, the specific wireless device behavior when both wireless device DRX and cell DTX/DRX are configured is currently not defined.

SUMMARY

Some embodiments advantageously provide methods, systems, and apparatuses for wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

One or more embodiments relate to methods and mechanisms related to wireless device behavior when both cell DTX/DRX and wireless device C-DRX are configured.

According to an embodiment, a method implemented by a wireless device (WD) is provided. The WD is configured to communicate with a network node. According to the method, the WD receives a cell Discontinuous Transmission (cell DTX) configuration of the network node. The cell DTX configuration defines a cell DTX active time. Further, the WD transmits a Hybrid Automatic Repeat Request (HARQ) negative acknowledgement (NACK) for a downlink (DL) wireless transmission from the network node. In response to the HARQ NACK, the WD monitors for DL retransmissions from the network node after the cell DTX active time has ended.

According to a further embodiment, a method implemented by a WD is provided. The WD is configured to communicate with a network node. According to the method, the WD receives a cell Discontinuous Reception (cell DRX) configuration of the network node. The cell DRX configuration defines a cell DRX active time. Further, the WD receives a DL wireless transmission from the network node and transmits HARQ feedback for the DL wireless transmission. The WD transmits the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time.

According to a further embodiment, a method implemented by a network node is provided. The network node is configured to communicate with a WD. According to the method, the network node provides a cell DTX configuration of the network node to the WD. The cell DTX configuration defines a cell DTX active time. Further, the network node receives, from the WD, a HARQ NACK for a DL wireless transmission from the network node. In response to the HARQ NACK, the network node sends a DL re-transmission to the WD after the cell DTX active time has ended.

According to a further embodiment, a method implemented by a network node is provided. The network node is configured to communicate with a WD. According to the method, the network node provides a cell DRX configuration of the network node to the WD. The cell DRX configuration defines a cell DRX active time. Further, the network node transmits a DL wireless transmission to the WD. Further, the network node receives HARQ feedback for the DL wireless transmission. The network node expects the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was transmitted during the cell DRX active time.

According to a further embodiment, a WD is provided. The WD is configured to communicate with a network node. Further, the WD is configured to receive a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. Further, the WD is configured to transmit a HARQ NACK for a DL wireless transmission from the network node. Further, the WD is configured to, in response to the HARQ NACK, the WD monitors for DL re-transmissions from the network node after the cell DTX active time has ended.

According to a further embodiment, a WD configured to communicate with a network node is provided. The WD comprises processing circuitry and a memory storing program instructions that, when executed by a processing circuity, cause the WD to receive a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. Further, execution of the program instructions causes the WD to transmit a HARQ NACK for a DL wireless transmission from the network node. Further, execution of the program instructions causes the WD to, in response to the HARQ NACK, the WD monitors for DL re-transmissions from the network node after the cell DTX active time has ended.

According to a further embodiment, a WD is provided. The WD is configured to communicate with a network node. Further, the WD is configured to receive a cell DRX configuration of the network node. The cell DRX configuration defines a cell DRX active time. Further, the WD is configured to receive a DL wireless transmission from the network node and transmit HARQ feedback for the DL wireless transmission after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time.

According to a further embodiment, a WD configured to communicate with a network node is provided. The WD comprises processing circuitry and a memory storing program instructions that, when executed by a processing circuity, cause the WD to receive a cell DRX configuration of the network node. The cell DRX configuration defines a cell DRX active time. Further, execution of the program instructions causes the WD to receive a DL wireless transmission from the network node and transmit HARQ feedback for the DL wireless transmission after the cell DRX active time has ended if the DL transmission was received during the cell DRX active time.

According to a further embodiment, a network node is provided. The network node is configured to communicate with a WD. Further, the network node is configured to provide a cell DTX configuration of the network node to the WD. The cell DTX configuration defines a cell DTX active time. Further, the network node is configured to receive, from the WD, a HARQ NACK for a DL wireless transmission from the network node. Further, the network node is configured to, in response to the HARQ NACK, send a DL re-transmission to the WD after the cell DTX active time has ended.

According to a further embodiment, a network configured to communicate with a WD is provided. The network node comprises processing circuitry and a memory storing program instructions that, when executed by a processing circuity, cause the network node to provide a cell DTX configuration of the network node to the WD. The cell DTX configuration defines a cell DTX active time. Further, execution of the program instructions causes the network node to receive, from the WD, a HARQ NACK for a DL wireless transmission from the network node. Further, execution of the program instructions causes the network node to, in response to the HARQ NACK, send a DL re-transmission to the WD after the cell DTX active time has ended.

According to a further embodiment, a network node is provided. The network node is configured to communicate with a WD. Further, the network node is configured to provide a cell DRX configuration of the network node to the WD. The cell DRX configuration defines a cell DRX active time. Further, the network node is configured to transmit a DL wireless transmission to the WD. Further, the network node is configured to receive HARQ feedback for the DL wireless transmission and expect the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was transmitted during the cell DRX active time.

According to a further embodiment, a network node configured to communicate with a WD is provided. The network node comprises processing circuitry and a memory storing program instructions that, when executed by a processing circuity, cause the network node to provide a cell DRX configuration of the network node to the WD. The cell DRX configuration defines a cell DRX active time. Further, execution of the program instructions causes the network node to transmit a DL wireless transmission to the WD. Further, execution of the program instructions causes the network node to receive HARQ feedback for the DL wireless transmission and expect the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was transmitted during the cell DRX active time.

According to a further embodiment, a computer program or computer program product is provided, e.g., in the form of a non-transitory computer readable medium, which comprises program instructions that, when executed by processing circuitry of a WD for communication with a network node, cause the WD to receive a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. Further, execution of the program instructions causes the WD to transmit a HARQ NACK for a DL wireless transmission from the network node. Further, execution of the program instructions causes the WD to, in response to the HARQ NACK, the WD monitors for DL re-transmissions from the network node after the cell DTX active time has ended.

According to a further embodiment, a computer program or computer program product is provided, e.g., in the form of a non-transitory computer readable medium, which comprises program instructions that, when executed by processing circuitry of a WD for communication with a network node, cause the WD to receive a cell DRX configuration of the network node. The cell DRX configuration defines a cell DRX active time. Further, execution of the program instructions causes the WD to receive a DL wireless transmission from the network node and transmit HARQ feedback for the DL wireless transmission after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time.

According to a further embodiment, a computer program or computer program product is provided, e.g., in the form of a non-transitory computer readable medium, which comprises program instructions that, when executed by processing circuitry of a network for communication with a WD, cause the network node to provide a cell DTX configuration of the network node to the WD. The cell DTX configuration defines a cell DTX active time. Further, execution of the program instructions causes the network node to receive, from the WD, a HARQ NACK for a DL wireless transmission from the network node. Further, execution of the program instructions causes the network node to, in response to the HARQ NACK, send a DL re-transmission to the WD after the cell DTX active time has ended.

According to a further embodiment, a computer program or computer program product is provided, e.g., in the form of a non-transitory computer readable medium, which comprises program instructions that, when executed by processing circuitry of a network for communication with a WD, cause the network node to provide a cell DRX configuration of the network node to the WD. The cell DRX configuration defines a cell DRX active time. Further, execution of the program instructions causes the network node to transmit a DL wireless transmission to the WD. Further, execution of the program instructions causes the network node to receive HARQ feedback for the DL wireless transmission and expect the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was transmitted during the cell DRX active time.

BRIEF DESCRIPTION OF THE DRAWINGS

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:

FIG. 1 is an example diagram of DRX cycles;

FIG. 2 is an example of wireless devices' onDurations; FIG. 3 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 4 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 8 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 9 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

FIG. 10 is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure.

FIG. 11 is a diagram of examples of wireless device C-DRX actives times and cell DTX active times and resulting active times according to some embodiments of the present disclosure; and

FIG. 12 is a diagram of examples of extensions of active times according to some embodiments of the present disclosure.

FIG. 13 is a flowchart for illustrating an exemplary method in a wireless device according to some embodiments of the present disclosure. FIG. 14 is a flowchart for illustrating an exemplary method in a network node according to some embodiments of the present disclosure.

FIG. 15 is a flowchart for illustrating a further exemplary method in a wireless device according to some embodiments of the present disclosure.

FIG. 16 is a flowchart for illustrating a further exemplary method in a network node according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

As discussed above, the specific wireless device behavior when both wireless device DRX and cell DTX/DRX are configured is currently not defined. For example, in one system, how the wireless device should behave when both wireless device DRX and cell DTX/DRX are configured as described at a high level.

For example, the parts during the network node onDuration that may be used for UL or downlink (DL) are based on wireless device C-DRX onDuration configuration (i.e., not specifically configured for network node DTRX active time). In another example, the parts during the network node onDuration that may be used for UL or DL are the same as wireless device C-DRX onDuration occasions which overlap/coincide with network node onDuration occasions (i.e., wireless device’s C- DRX occasions are masked out by network node onDuration occasions).

FIG. 2 is a diagram of wireless device's onDurations that overlap with network node DTRX onDurations where the onDurations that fall outside are masked out.

While the high level mechanisms of wireless device behavior configured with C-DRX and cell DTX/DRX are illustrated in FIG. 2, the details are yet to be determined further, particularly in boundary cases such as when wireless device C-DRX active time falls partly between the cell DTX/DRX active time and inactive time as illustrated in FIG. 2.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX. 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. Like numbers refer to like elements throughout the description.

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.

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.

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), integrated access and backhaul (IAB) node, 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 wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, 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), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

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, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or to one or both of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and/or A, B, C or a combination thereof.

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.

Some embodiments provide wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 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 wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16. Also, it is contemplated that a WD 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 WD 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, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more subnetworks (not shown).

The communication system of FIG. 3 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include a discontinuous unit 32 which is configured to perform one or more network node 16 functions as described herien such as with respect to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX. A wireless device 22 is configured to include a DRX unit 34 which is configured to perform one or more wireless device 22 functions described herein such as with respect to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 4. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 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 44 may be configured to access (e.g., write to and/or read from) memory 46, 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).

Processing circuitry 42 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 host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24. The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to process, store, configuration, forward, relay, communicate, analyze, etc. information related to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 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 communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 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 70 may be configured to access (e.g., write to and/or read from) the memory 72, 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).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, 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 74 may be executable by the processing circuitry 68. The processing circuitry 68 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 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include discontinuous unit 32 configured to perform one or more network node 16 functions as described herein such as with respect to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 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 hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 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 86 may be configured to access (e.g., write to and/or read from) memory 88, 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).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 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 WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a DRX unit 34 configured to perform one or more wireless device 22 functions as described herien such as with respect to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX. In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

In FIG. 4, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may 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. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 3 and 4 show various “units” such as discontinuous unit 32, and DRX unit 34 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.

FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 3 and 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 4. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application

50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block S108).

FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block

5118). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

In the context of the present disclosure, a Cell DTX/DRX mechanism may involve the following:

Cell DTX/DRX may be configured on a UE specific basis using RRC signaling. Therefore, different UEs or group of UEs can be configured with different cell DTX/DRX patterns or configurations. Therefore, it may be desirable that there is no requirement for the network to ensure that same cell DTX/DRX pattern applies for all UEs and is always communicated to all the UEs.

Furthermore, it should be noted that despite the designation “cell DTX/DRX”, there may be an impact on UE behavior, and UE behavior may need to be specified with respect to specific signals/channels when the cell DTX/DRX is configured. Below some examples of such UE behavior are addressed.

There are some channel s/signals that gNB is already in control and can decide to transmit or not, e.g., PDCCH or PDSCH. Furthermore, when assuming that cell DTX/DRX should not impact idle/inactive UEs, some channels such as Sl/paging and idle mode RACH should not be impacted. On the other hand, there are some channels particularly in connected mode, which can be controlled explicitly by cell DTX/DRX, ,e.g., periodic transmissions, e.g., periodic CSI-RS, TRS, or periodic UL resources, e.g., SR or connected mode PRACH. Below, each of these channel s/signals are discussed in more detail.

As regards the impact of cell DTX/DRX on UL channel s/signals, it can be expected that this is where the main edge of cell DTX/DRX comes to effect with respect to just aligning UE DRX occasions, which can be done using existing mechanisms, particularly when it comes to periodic UL resources, e.g., periodic SR or connected mode PRACH. This is where network does not know if the UE would transmit something in the UL or not and it has to listen anyways, depriving it of going to deeper sleep modes. As such, cell DTX/DRX can be used in order to provide a configuration such that the UE knows if it can transmit a specific SR or PRACH during inactive time of cell DRX or not. As a general rule, it can be considered that the UE should avoid transmitting in UL while in connected mode and during inactive time of cell DRX. This also applies to periodic SRS transmissions unless it is configured otherwise. Nevertheless, some exemptions may apply, e.g., if a SR is scheduled by the network aperiodically.

The UE in connected mode should be able to be configured to not transmit a SR or PRACH during off time of cell DRX. E.g., all configured grants, or semi persistent, or periodic CSI reporting, or SRS transmissions are cancelled. RANI can discuss and determine exemptions, e.g., if an UL PUSCH or SR is scheduled by the NW using an aperiodic PDCCH.

As regards impact on an on-going HARQ process, it is to be noted that HARQ processes are important to make sure the UE receives the data packets correctly and delivery are finished. Entering a cell DTX/DRX inactive period thus should not lead to a stop in an on-going HARQ process if it is not fished. As such even if the cell DTX/DRX is not active, but he HARQ process and retransmissions started due to a packet being scheduled during active period, the UE should still monitor for the related PDCCHs and transmit the related UL signals, i.e., PUCCH/PUSCH. The currently running HARQ process should go on even during cell DTX/DRX inactive period if the associated process is started during cell DTX/DRX active time, i.e., UE should monitor the associated PDCCH or transmit the required ACK/NACKs. FFS: If the number of maximum retransmissions can be configured.

As regards impact on periodic transmissions, it is to be noted that periodic transmissions, such as periodic CSLRS and TRS, or DL SPS, can prevent the network from entering deeper sleep modes even during cell DTX/DRX inactive times. Therefore, it may be beneficial that the network is in control of configuring not transmitting them during inactive time. According to an example, a UE in connected mode should not expect periodic transmissions except SSBs, e.g., CSLRS, TRS, DL SPS, etc., during off time of cell DTX/DRX.

As regards activation/deactivation of cell DTX/DRX pattern, L1/L2 based activation/deactivation of cell DTX/DRX pattern can be considered. For example, cell DTX/DRX patterns may be configured using UE specific RRC signaling, but they can be turned on/off potentially using L1/L2 signaling. L2 signaling, mostly referring to MAC-CE, may have the benefit that it comes with a robustness due to acknowledgement required by the UE. However, it may occur that practice L2 signaling is not much faster than RRC signaling. It may thus be preferable to use LI or DCI based signaling to activate and deactivate cell DTX/DRX while considering the mechanism should be designed as robust as possible to make sure that the misalignment between the UE and the network is very rare. Nevertheless, may be useful if a cell DTX/DRX mechanism is specified which does not rely on explicit L1/L2 activation/deactivation. DCI based activation/deactivation of cell DTX/DRX can be considered.

In addition to LI based mechanisms to activate or deactivate cell DTX/DRX, as mentioned before, it may also be useful to make sure the current packet delivery to the UE is not disrupted by cell DTX/DRX inactive time. As such, a mechanism similar to the UE C-DRX inactivity timer can be considered for the cell DTX/DRX inactivity timer. For the UE C-DRX inactivity timer, typically implicit signaling is used to restart the inactivity timer, i.e., scheduling a new data. A similar approach can be used for cell DTX/DRX, however with a shorter inactivity timer, so that the network can go back to off time as fast as possible. Alternatively, or additionally, an explicit indication using LI based signaling can be used, where the network can indicate to the UE explicitly that the UE should start cell DTX/DRX inactivity timer and for how long. Accordingly, At least implicit LI based signaling can be used to trigger a cell DTX/DRX inactivity timer. Explicit LI signaling can be considered as well. Implicit signaling may schedule new data and can trigger restart of inactivity timer for a default or configured value, while explicit LI based signalling can be used to trigger inactivity timer with a value chosen among multiple configured values.

In previous sections, the following observations and proposals were made:

- There are DCIs which the UE should monitor such as DCI scheduling SIB1, or SI update or PWS irrespective of cell DTX status.

- There is a need to determine PDCCH signals which needs to be monitored by the UE irrespective of the cell DTX status, e.g., SI update, PWS, or a PDCCH in response to a SR sent by the UE, or a PDCCH related to an on-going HARQ process.

- The UE in connected mode, should be able to be configured to not transmit a SR or PRACH during off time of cell DRX. E.g., all configured grants, or periodic reporting, or SRS transmissions are cancelled. RANI can discuss and determine exemptions, e.g., if an UL PUSCH or SR is scheduled by the NW using an aperiodic PDCCH. - The currently running HARQ process should go on even during cell DTX/DRX inactive period if the associated process is started during cell DTX/DRX active time, i.e., UE should monitor the associated PDCCH or transmit the required ACK/NACKs. FFS: If the number of maximum retransmissions can be configured.

- The UE in connected mode should not expect periodic transmissions except SSBs, e.g., CSI-RS, TRS, etc., during off time of cell DTX/DRX. FFS: CSI-RS for mobility?

- A measurement gap can be used for normal communication when UE can do inter-frequency/inter-RAT measurement in cell DTX period. FFS: the detailed condition about when measurement gap can be used for normal communication.

- DCI based activation/deactivation of cell DTX/DRX can be considered. FFS: detail design.

- Both implicit and explicit LI based signaling can be used to trigger cell DTX/DRX inactivitytimer. Implicit signaling is scheduling new data and can trigger restart of inactivity timer for a default or configured value, while explicit LI based signalling can be used to trigger inactivity timer with a value chosen among multiple configured values.

As regards higher layer procedures related to Cell DTX/RTX, the following may be considered:

Cell DTX/DRX is applied to at least UEs in RRC CONNECTED state. A periodic Cell DTX/DRX (i.e., active and non-active periods) can be configured by gNB via UE-specific RRC signalling per serving cell. Below examples on Cell DTX/DRX behaviour during non-active periods are assumed to be possible options, and the UE behaviour/impact will be further assessed below:

Example 1 : gNB is expected to turn off all transmission and reception for data traffic and reference signal during Cell DTX/DRX non-active periods.

Example 2: gNB is expected to turn off its transmission/reception only for data traffic during Cell DTX/DRX non-active periods (i.e., gNB will still transmit/receive reference signals)

Example 3 : gNB is expected to turn off its dynamic data transmission/reception during Cell DTX/DRX non-active periods (i.e., gNB is expected to still perform transmission/reception in periodic resources, including SPS, CG-PUSCH, SR, RACH, and SRS). Example 4: gNB is expected to only transmit reference signals (e.g., CSI-RS for measurement).

The following considerations focus on UE behavior when at any point in time the cell activates a single DTX/DRX configuration. It is up to the network whether legacy UEs can access cells with Cell DTX/DRX.

The Cell DTX/DRX mode can be activated/de-activated via dynamic L1/L2 signalling and UE-specific RRC signaling. Both UE specific and common L1/L2 signalling can be considered for activating/deactivating the Cell DTX/DRX mode.

Cell DTX and Cell DRX modes can be configured and operated separately (e.g., one RRC configuration set for DL and another for UL). Cell DTX/DRX can also be configured and operated together. At least the following parameters can be configured per Cell DTX/DRX configuration: periodicity, start slot/offset, on duration. Support of multiple Cell DTX/DRX configurations can be considered as well.

It may be beneficial to align UE DRX with Cell DTX and DRX alignment among multiple UEs.

Further, it may be beneficial to design Cell DTX/DRX mechanisms should be designed such that the impact on the legacy UEs is minimized.

As regards configuration and signalling aspects, 3GPP TR 38.864 V18.0.0 (2022-12) for example describes that the network can configure through RRC signalling Cell DTX and Cell DRX separately (e.g., one RRC configuration set for DL and another for UL) or together as found appropriate by the network in different scenarios. To achieve this, two sets of RRC parameters (i.e., one for Cell DTX and one for Cell DRX) may need to be specified.

At least parameters like periodicity, start slot/offset, and on duration can be configured per Cell DTX/DRX configuration. Although these parameters allow for a basic functionality of the Cell DTX/DRX, they do not specify policies for extending Cell DTX and Cell DRX on duration times in cases when it is needed to accommodate possible additional transmissions on the DL and UL, respectively. Without such policies, following the nominal on duration and off duration times may lead to inability to maintain responsive traffic patterns or meet relevant QoS/QoE requirements for individual UEs. Accordingly, it can be observed that mechanisms for extending Cell DTX and Cell DRX on duration times may help to maintain responsive traffic patterns and to meet relevant QoS/QoE requirements for individual UEs. Further, there may a need for Cell DTX and Cell DRX inactivity timers that would enable energy savings at the network side.

In view of high-level Cell DTX/DRX parameters as for example captured in 3GPP TR 38.864 V18.0.0 and the above-described need for Cell DTX and Cell DRX inactivity timers, the following sets of RRC parameters for configuring Cell DTX and Cell DRX may be useful. For Cell DTX: cell-dtxPeriodicity, cell-dtxStartOffset, cell- dtxOnDurationTimer, and cell-dtxInactivityTimer. Other parameters may be considered as well. For Cell DRX: cell-drxPeriodicity, cell-drxStartOffset, cell- drxOnDurationTimer, and cell-drxInactivityTimer. Other parameters may be considered as well.

As regards the ways of activating/deactivating Cell DTX/DRX, 3GPP TR 38.864 V18.0.0 proposed that the Cell DTX/DRX mode can be activated/de-activated via dynamic L1/L2 signalling and UE-specific RRC signaling.

Therefore, given that there may be different ways of activating/deactivating Cell DTX/DRX, there may be a need to make the UE aware of the way the NW intends to activate/deactivate provided Cell DTX/DRX RRC configurations. The latter way of activating Cell DTX/DRX (i.e., using RRC signalling) implies that the Cell DTX/DRX is feasible using RRC without dynamic signalling, and our opinion is that this is the simplest way of supporting the Cell DTX/DRX (e.g., similar to UE C-DRX) that should be ensured and prioritized by RAN2. For example, the NW can use cell-dtxStartOffset and cell-drxStartOffset parameters to easily indicate to the UE the time at which the Cell DTX and Cell DRX will be activated, respectively (i.e., that the UE should not expect Cell DTX/DRX activation via L1/L2 signalling). Alternatively, a new field in the Cell DTX and Cell DRX RRC configuration can be used for the same purpose.

Accordingly, there may be nned to further define how to enable the full functionality of Cell DTX and Cell DRX features based on the received RRC configuration. Further, it may be beneficial to introduce lower layer signalling (e.g., dynamic L1/L2 signalling) as Cell DTX and Cell DRX enhancements.

As regards coexistence of Cell DTX/DRX and UE C-DRX, one of the aspects that needs to be addressed is how Cell DTX/DRX and UE C-DRX mechanisms interact with each other when the UE is configured with both Cell DTX/DRX and UE C-DRX at the same time. Solutions according to which, for example, UE C-DRX active period dominates Cell DTX non-active period (i.e., UE C-DRX active period extends the Cell DTX non-active period) may be unfavourable in terms of network energy savings. When specifying how the UE C-DRX and the Cell DTX/DRX mechanisms interact with each other when configured at the same time, solutions that maximize opportunities for the network sleep may be preferable.

Accordingly, the following observations can be made:

- The Cell DTX/DRX mechanisms should be designed such that the impact on the legacy UEs is minimized.

- In order to be able to configure Cell DTX and Cell DRX separately, two sets of RRC parameters for configuting Cell DTX and Cell DRX, respectively, may need to be specified.

- Mechanisms for extending Cell DTX and Cell DRX on duration times may be introduced to maintain responsive traffic patterns and to meet relevant QoS/QoE requirements for individual UEs.

- The inactivity timer approach used for UE C-DRX is not directly applicable to the Cell DTX/DRX context since the Cell DTX/DRX assumptions need to be compatible for all UEs in a cell.

- The inactivity timer approach used for UE C-DRX may not be suitable for the Cell DTX/DRX context since it may lead to unnecessary energy consumption at the network and the UE side.

- When specifying how the UE C-DRX and the Cell DTX/DRX mechanisms interact with each other when configured at the same time, solutions that maximize opportunities for the network sleep while taking into consideration the UE power consumption may be preferable. If a UE is configured with both UE C-DRX and Cell DTX at the same time, may Cell DTX overwrite UE C-DRX. This may imply that the UE C-DRX active periods remain intact during Cell DTX active periods and/or that the UE C-DRX active periods are cancelled during Cell DTX non-active periods (i.e., the UE should not expect the transmissions on the DL unless otherwise indicated by the network).

FIG. 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block SI 28). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

FIG. 9 is a flowchart of an exemplary 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 68 (including the discontinuous unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configured to configure (Block SI 34) a wireless device 22 with a connected mode discontinuous reception, C-DRX, onDuration, as described herein. Network node 16 is configured to communicate (block SI 36) with the wireless device 22 in C-DRX based on a resulting onDuration that is based on the configured C-DRX onDuration for the wireless device 22 and the cell DTX onDuration, as described herein.

According to one or more embodiments, the C-DRX onDuration for the wireless device 22 starts earlier in time than the cell DTX onDuration.

According to one or more embodiments, the C-DRX onDuration for the wireless device 22 is a subset of the cell DTX onDuration.

According to one or more embodiments, the Cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device 22.

According to one or more embodiments, the Cell DTX onDuration is a subset of the C-DRX onDuration for the wireless device 22.

According to one or more embodiments, the resulting onDuration is configured to at least partially overlap the cell DTX onDuration.

According to one or more embodiments, the C-DRX onDuration for the wireless device 22 does not overlap with the Cell DTX onDuration.

According to one or more embodiments, the C-DRX onDuration for the wireless device one of: has a shorter time period than the cell DTX onDuration, and has a longer time period than the cell DTX onDuration.

According to one or more embodiments, an inactivity timer of C-DRX is used to extend the resulting onDuration within the Cell DTX onDuration.

According to one or more embodiments, the inactivity timer of Cell DTX is used to extend the resulting onDuration outside of the Cell DTX onDuration.

FIG. 10 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the DRX unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 is configured to operate (Block S138) in connected mode discontinuous reception, C-DRX according to a resulting onDuration that is based on a configured C-DRX onDuration for the wireless device 22 and a cell discontinuous transmission, DTX, onDuration, as described herein.

According to one or more embodiments, the C-DRX onDuration for the wireless device 22 one of has a shorter time period than the cell DTX onDuration; and has a longer time period than the cell DTX onDuration.

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 wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX.

Some embodiments provide wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission, DTX, and/or discontinuous reception, DRX. One or more network node 16 functions described below may be performed by one or more of discontinuous unit 32, processor 70, processing circuitry 68, radio interface 62, etc. One or more wireless device 22 functions described below may be performed by one or more of DRX unit 34, processor 86, processing circuitry 84, radio interface 82, etc.

FIG. 11 is a diagram of examples of possible combinations of the wireless device 22 C-DRX active times and Cell DTX active times defined by onDurationtimer of C-DRX and onDurationtimer of Cell DTX, respectively, and possible resulting active times defined by taking into consideration both the active times specified by both the wireless device 22 C-DRX and the Cell DTX configurations.

Different cases that are illustrated in FIG. 11 are described as follows:

• Case a: wireless device 22 C-DRX and Cell DTX active times partially intersect, and wireless device 22 C-DRX active time starts earlier than Cell DTX active period.

• Case b: wireless device 22 C-DRX active time is a proper subset of Cell DTX active time.

• Case c: wireless device 22 C-DRX and Cell DTX active times partially intersect, and Cell DTX active time starts earlier than wireless device 22 C- DRX active time.

• Case d: Cell DTX active time is a proper subset of wireless device 22 C-DRX active time.

• Case e: wireless device 22 C-DRX and Cell DTX active times do not intersect, and wireless device 22 C-DRX active time is shorter than Cell DTX active time.

• Case f: wireless device 22 C-DRX and Cell DTX active times do not intersect, and wireless device 22 C-DRX active time is longer than Cell DTX active time.

FIG. 12 is a diagram of examples of possible extensions of active times that are defined by inactivitytimer of C-DRX and inactivitytimer of Cell DTX.

Different cases illustrated in FIG. 12 are described as follows:

• Case A: inactivitytimer of C-DRX is used to extend the active period within the active time defined by onDurationtimer of Cell DTX.

• Case B: inactivitytimer of Cell DTX is used to extend the active period outside the active time defined by onDurationtimer of Cell DTX.

Some Examples Methods in wireless device 22 in which:

1. The wireless device 22 receives a network node DTRX or cell DTX/DRX or just one of the DTX or DRX configuration from the network node 16 while in RRC connected state, or other states, e.g., through higher layer signaling such as system information (SI) broadcast, or dedicated signaling such as RRC configuration. The wireless device 22 is additionally configured with C-DRX.

2. Example 1 where the wireless device 22 starts the onDurationtimer of C-DRX (or onDuration timer of Cell DTRX if configured to use it instead of the C-DRX onDuration) if its onDuration timer can be started while Cell DTX/DRX is in active state or that part of the ondurationtimer falls within the cell DTX/DRX active time. Otherwise, the wireless device 22 does not start the ondurationtimer. Examples of possible combinations of the wireless device 22 C-DRX active times and Cell DTX active times defined by onDurationtimer of C-DRX and onDurationtimer of Cell DTX, respectively, are illustrated in FIG. 11.

3. Any one of the above Examples where the wireless device 22 restarts DRXinactivitytimer of C-DRX (or inactivityTimer of Cell DTRX if configured to use it instead of the C-DRX inactivity timer) if it can be started while the cell DTX/DRX is in active state. Otherwise, the wireless device 22 does not (re)start the DRXinactivitytimer. Examples of possible extensions of active times that are defined by inactivitytimer of C-DRX and inactivitytimer of Cell DTX, respectively, are illustrated in FIG. 12.

4. Any one of the above Examples where the wireless device 22 is configured to stop the ondurationtimer or DRXinactivitytimer, or any other active time related timer of C-DRX when the cell (with DTX and/or DRX) enters inactive period. This may be the general rule but a wireless device 22 can be configured otherwise by the network node 16 if necessary by providing an overriding configuration.

Possible altematives/options/exceptions for stopping criteria: a. Stop the timer when both cell DTX and DRX enter inactive period (i.e. do not stop when one of them is active) b. Stop the timer when at least cell DTX enters inactive period c. In case, the wireless device is configured to complete the ondurationtimer or DRXinactivitytimer duration regardless of the cell DTX/DRX state (see below), the timer is not stopped

Possible overriding configurations: d. The wireless device 22 completes the ondurationtimer or DRXinactivitytimer duration regardless of the cell DTX/DRX state [the network node 16 may leave itself an option to break the cell DTX in case of “important” data] i. This may apply to only certain types of DCIs, e.g. the inactivity timer is completed only for “real” new data [not BSR] (e.g., new transmissions), or in case of certain 5QI settings or traffic types. e. The wireless device 22 ignores the cell DTX state and always complete the timer [effectively a per-wireless device 22 deactivation of cell DTRX that does not require system signaling and does not affect other wireless devices 22 that continue to assume the globally configured cell DTRX], Any of the above examples where the active state of cell DTX/DRX includes any timer indicating that a transmission from the cell is expected or the cell listens to UL transmissions, e.g., onduration timer or inactivitytimer associated with the cell DTX/DRX. Any of the above examples where the wireless device 22 may transmit HARQ feedback after cell DRX active time has ended if the DL transmission was received during the active time, and/or monitor for DL re-transmissions after cell DTX active time has ended if a recent HARQ NACK was transmitted ( e.g., this could be a general rule or configured individually per wireless device 22). Additional one or more of a. the wireless device 22 may transmit HARQ feedback after cell DRX active time has ended if the DL transmission was received during the active time, but only if fewer than a maximum configured (e.g., preconfigured via RRC) number of HARQ retransmissions for the current DL message has taken place. b. the wireless device 22 may monitor for DL re-transmissions after cell DTX active time has ended if a recent HARQ NACK was transmitted, but only if fewer than a maximum configured (e.g., preconfigured via RRC) number of HARQ retransmissions for the current UL message has taken place. The duration of a HARQ transmission permission window and the duration of DL re-transmission monitoring may be configured by the network node 16, and whether to apply the rule to the current transmission may be indicated in the scheduling DCI. c. An offset is defined which extends or delays the start of HARQ transmission permission window. The offset may correspond to the CELL inactive time or be relative to that time. It may also be any configured value. When this offset is applied, wireless device 22 and network node 16 both wait during the inactive time and do not, e.g., flush HARQ buffers. After the cell becomes available again, wireless device 22 (or network node 16) may continue to finish that transmission. In one embodiment, several offsets are defined and configured for the wireless device 22, then a DCI or group DCI from the network node 16 indicates to the wireless devices 22 which offset to apply. It can be a field in the DCI scheduling DL or UL.

7. Any of the above Examples where the wireless device 22 may be configured to monitor downlink messages (e.g., DCI on PDCCH with CRC scrambled by C- RNTI, etc.) in slots with one or more SSB transmissions.

8. Any of the above Examples where the wireless device 22 may monitor downlink messages (e.g., DCI on PDCCH with CRC scrambled by C-RNTI, etc.) during cell DTX inactive time if a corresponding UL HARQ retransmission timer (e.g., configured as part of wireless device 22 C-DRX) is running. a. the wireless device 22 may transmit on the uplink after cell DRX active time has ended if an UL transmission is scheduled for the wireless device 22 according to a downlink control message.

9. Any of the above Examples where a wireless device 22 may be configured to transmit Scheduling Requests (SRs) according to its configured SR occasion schedule during all or part of cell DRX inactive time, e.g., the network/network node 16 may allow SR transmission for a subset of critical wireless devices 22 (e.g., for a subset of a plurality of wireless devices 22) while those are in connected mode without reconfiguring cell DRX for all wireless devices 22. a. Any of the above Examples where a wireless device 22 may be configured/allowed to monitor downlink messages during cell DTX inactive time if the wireless device 22 transmits a scheduling request and it is pending. b. Any of the above Examples where a wireless device 22 may be configured/allowed to transmit on the uplink (e.g., data transmission on physical uplink shared channel (PUSCH)) according to a detected downlink message even if the associated uplink transmission occasion overlaps cell DRX inactive time. c. Any of the above Examples where a wireless device 22 may be configured/allowed to transmit on the uplink (e.g. data transmission on PUSCH) according to a detected downlink message even if the associated uplink transmission occasion overlaps cell DRX inactive time. d. Any of the above Examples where the wireless device 22 may be configured/allowed to transmit on the uplink (e.g., data transmission on PUSCH) according to a detected downlink message even if the associated uplink transmission occasion overlaps cell DRX inactive time. e. Any of the above Examples where the wireless device 22 may be configured/allowed to transmit scheduling request multiplexed with a HARQ-ACK on the uplink (e g., SR+HARQ-ACK on PUCCH) if the wireless device 22 is configured to transmit HARQ-ACK on PUCCH during cell DRX inactive time. f. Any of the above Examples where the wireless device 22 may be configured/allowed to transmit SRS in a slot/symbol on the uplink (e.g., SR+HARQ-ACK on PUCCH) if the wireless device 22 is scheduled to transmit PUSCH/HARQ-ACK in the slot/symbol during cell DRX inactive time. g. Any of the above Examples where the wireless device 22 may be configured to be able to request or indicate its preference for any of the specific configurations above, or other configurations described herein, including wireless device assistance information on the wireless device 22’ s preference on specific configuration of cell DTX/DRX parameters. Any of the above Examples where the wireless device 22 is configured with more than once serving cell configured with cell DTX/DRX. 11. Any of the above Examples where the behavior is applicable to a cell group, i.e., only MCG, only SCG or both MCG and SCG. a. The wireless device DRX for the corresponding cell group will only be affected as described above according to cell DTX/DRX if there is any cell within that cell group configured with DTX/DRX.

Hence, one or more embodiments described herein advantageously provides mechanisms where cell DTX/DRX and wireless device C-DRX or DRX can coexist and thus provide energy savings to both wireless device and network node.

The wireless device 22 and the network node 16 may be aligned during the above operations. For example, the network node may send a DL re-transmission after the cell DTX active time has ended if a recent HARQ NACK was transmitted by the WD 22. Further, if the network node 16 has sent a DL transmission during the cell DRX active time, the network node 16 may expect HARQ feedback from the WD 22 after the cell DRX active time has ended.

FIG. 13 is a flowchart of an exemplary method according to some embodiments of the present disclosure. The method may be implemented in a WD for communication with a network node. For example, the method could be implemented in the WD 22, and the WD 22 could be configured to communicate with the network node 16. One or more blocks described herein may be performed by one or more elements of the WD, such as by one or more of processing circuitry 84 (including the DRX unit 34), processor 86, and/or radio interface 82. The WD may be configured with C-DRX.

In the method of FIG. 13, the WD receives a cell DTX configuration of the network node (block 140). The cell DTX configuration defines a cell DTX active time. The WD may receive the cell DTX configuration from the network node. The WD may receive the cell DTX configuration while in RRC connected state. The WD may receive the cell DTX configuration through RRC configuration or through SI broadcast.

Further, the WD sends HARQ NACK for a DL wireless transmission from the network node (block 142). In response to the HARQ NACK, the WD monitors for DL re-transmission(s) from the network node after the cell DTX active time has ended (block 144). The WD may perform said monitoring for DL re-transmissions after the cell DTX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place. The maximum number may be configured by RRC. Duration of a HARQ transmission permission window and duration of said monitoring for DL re-transmissions may be configured by the network node, e.g., by RRC. A rule according to which the WD performs said monitoring for DL re-transmissions after the cell DTX active time is configured individually for the WD. Further, a rule according to which the WD performs said monitoring for DL re-transmissions after the cell DTX active and/or whether to apply the rule may be indicated in the scheduling DCI of the DL wireless transmission.

FIG. 14 is a flowchart of an exemplary method according to some embodiments of the present disclosure. The method may be implemented in a network node for communication with a WD. For example, the method could be implemented in the network node 16, and the network node 16 could be configured to communicate with the WD 22. 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 68 (including the discontinuous unit 32), processor 70, radio interface 62 and/or communication interface 60. The WD may be configured with C-DRX.

In the method of FIG. 14, the network node provides a cell DTX configuration of the network node to the WD (block 150). The cell DTX configuration defines a cell DTX active time. The network node may provide the cell DTX configuration while the WD is in RRC connected state. The network node may provide the cell DTX configuration through RRC configuration or through SI broadcast.

Further, the network node may send a DL wireless transmission to the WD (block 152).

Further, the network node receives, from the WD, a HARQ NACK for a DL wireless transmission from the network node, e.g., for the DL wireless transmission of block 154).

In response to the HARQ NACK, the network node sends a DL re-transmission to the WD after the cell DTX active time has ended (block 156). In some scenarios, the network node sends the DL re-transmission after the cell DTX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place. The maximum number may be configured by RRC. Duration of a HARQ transmission permission window and duration of said monitoring for DL re-transmissions are configured by the network node.

A rule according to which the WD performs said monitoring for DL retransmissions after the cell DTX active time is configured individually for the WD. Further, a rule according to which the WD performs said monitoring for DL re- transmissions after the cell DTX active and/or whether to apply the rule may be indicated in the scheduling DCI of the DL wireless transmission.

FIG. 15 is a flowchart of an exemplary method according to some embodiments of the present disclosure. The method may be implemented in a WD for communication with a network node. For example, the method could be implemented in the WD 22, and the WD 22 could be configured to communicate with the network node 16. One or more blocks described herein may be performed by one or more elements of the WD, such as by one or more of processing circuitry 84 (including the DRX unit 34), processor 86, and/or radio interface 82. The WD may be configured with C-DRX.

In the method of FIG. 15, the WD receives a cell DRX configuration of the network node (block 160). The cell DRX configuration defines a cell DRX active time. The WD may receive the cell DRX configuration from the network node. The WD may receive the cell DRX configuration while in RRC connected state. The WD may receive the cell DRX configuration through RRC configuration or through SI broadcast.

Further, the WD may receive a DL wireless transmission from the network node (block 162).

Further, the WD sends HARQ feedback for a DL wireless transmission from the network node (block 164), e.g., for the DL wireless transmission of block 162. The WD transmits the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time. The WD may transmit the HARQ feedback after the cell DRX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place. The maximum number may be configured by RRC. A rule according to which the WD performs said transmitting of the HARQ feedback after the cell DRX active time may configured individually for the WD, e.g., by RRC. Further, a rule according to which the WD performs said transmitting of the HARQ feedback after the cell DRX active time and/or whether to apply the rule may be indicated in scheduling DCI of the DL wireless transmission.

FIG. 16 is a flowchart of an exemplary method according to some embodiments of the present disclosure. The method may be implemented in a network node for communication with a WD. For example, the method could be implemented in the network node 16, and the network node 16 could be configured to communicate with the WD 22. 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 68 (including the discontinuous unit 32), processor 70, radio interface 62 and/or communication interface 60. The WD may be configured with C-DRX.

In the method of FIG. 16, the network node provides a cell DRX configuration of the network node to the WD (block 170). The cell DRX configuration defines a cell DRX active time. The network node may provide the cell DRX configuration while the WD is in RRC connected state. The network node may provide the cell DRX configuration through RRC configuration or through SI broadcast.

Further, the network node may send a DL wireless transmission to the WD (block 172).

Further, the network node receives, from the WD, HARQ feedback for a DL wireless transmission from the network node, e.g., for the DL wireless transmission of block 174). The network node expects the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time. The network node may expect the HARQ feedback after the cell DRX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place. The maximum number may be configured by RRC. A rule according to which the WD transmits the HARQ feedback after the cell DRX active time may configured individually for the WD, e.g., by RRC. Further, a rule according to which the WD transmits of the HARQ feedback after the cell DRX active time and/or whether to apply the rule may be indicated in scheduling DCI of the DL wireless transmission.

It is noted that the methods of FIGS. 13 to 16 may be combined in various ways. For example, a WD could implement both the method of FIG. 13 and the method of FIG. 15 if the network node is configured with both cell DTX and cell DRX. Further, the method of FIG. 13 and the method of FIG. 14 could be combined in a system which includes a WD operating according to the method of FIG: 13 and a network node operating according to the method of FIG. 14. Similarly, the method of FIG. 15 and the method of FIG. 16 could be combined in a system which includes a WD operating according to the method of FIG: 15 and a network node operating according to the method of FIG. 16.

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.

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.

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.

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.

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.

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).

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.

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. In the following, further embodiments are described:

Embodiment Al. A network node configured to communicate with a wireless device, the network node being configured with a cell discontinuous transmission, DTX, onDuration, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: configure a wireless device with a connected mode discontinuous reception, C- DRX, onDuration; and communicate with the wireless device in C-DRX based on a resulting onDuration that is based on the configured C-DRX onDuration for the wireless device and the cell DTX onDuration.

Embodiment A2. The network node of Embodiment Al, wherein the C- DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration.

Embodiment A3. The network node of Embodiment Al, wherein the C- DRX onDuration for the wireless device is a subset of the cell DTX onDuration.

Embodiment A4. The network node of Embodiment Al, wherein the Cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device.

Embodiment A5. The network node of Embodiment Al, wherein the Cell DTX onDuration is a subset of the C-DRX onDuration for the wireless device.

Embodiment A6. The network node of any one of Embodiments A1-A5, wherein the resulting onDuration is configured to at least partially overlap the cell DTX onDuration.

Embodiment A7. The network node of Embodiment Al, wherein the C- DRX onDuration for the wireless device does not overlap with the Cell DTX onDuration. Embodiment A8. The network node of Embodiment A7, wherein the C- DRX onDuration for the wireless device one of: has a shorter time period than the cell DTX onDuration; and has a longer time period than the cell DTX onDuration.

Embodiment A9. The network node of any one of Embodiments A1-A8, wherein an inactivity timer of C-DRX is used to extend the resulting onDuration within the Cell DTX onDuration.

Embodiment Al 0. The network node of Embodiment A10, wherein the inactivity timer of Cell DTX is used to extend the resulting onDuration outside of the Cell DTX onDuration.

Embodiment B 1. A method implemented by a network node that is configured to communicate with a wireless device, the network node being configured with a cell discontinuous transmission, DTX, onDuration, the method comprising: configuring a wireless device with a connected mode discontinuous reception, C-DRX, onDuration; and communicating with the wireless device in C-DRX based on a resulting onDuration that is based on the configured C-DRX onDuration for the wireless device and the cell DTX onDuration.

Embodiment B2. The method of Embodiment Bl, wherein the C-DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration.

Embodiment B3. The method of Embodiment Bl, wherein the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration.

Embodiment B4. The method of Embodiment Bl, wherein the Cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device.

Embodiment B5. The method of Embodiment Bl, wherein the Cell DTX onDuration is a subset of the C-DRX onDuration for the wireless device. Embodiment B6. The method of any one of Embodiments B1-B5, wherein the resulting onDuration is configured to at least partially overlap the cell DTX onDuration.

Embodiment B7. The method of Embodiment Bl, wherein the C-DRX onDuration for the wireless device does not overlap with the Cell DTX onDuration.

Embodiment B8. The method of Embodiment B7, wherein the C-DRX onDuration for the wireless device one of: has a shorter time period than the cell DTX onDuration; and has a longer time period than the cell DTX onDuration.

Embodiment B9. The method of any one of Embodiments B1-B8, wherein an inactivity timer of C-DRX is used to extend the resulting onDuration within the Cell DTX onDuration.

Embodiment BIO. The method of Embodiments B9, wherein the inactivity timer of Cell DTX is used to extend the resulting onDuration outside of the Cell DTX onDuration.

Embodiment Cl. A non-transitory computer readable medium storing program instructions that, when executed by a processor, configure the processor to implement the method of any one of Embodiments Bl to BIO.

Embodiment DI. A wireless device (WD) configured to communicate with a network node, the wireless device configured to, and/or comprising a radio interface and/or processing circuitry configured to: operate in connected mode discontinuous reception, C-DRX according to a resulting onDuration that is based on a configured C-DRX onDuration for the wireless device and a cell discontinuous transmission, DTX, onDuration.

Embodiment D2. The WD of Embodiment DI, wherein the C-DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration. Embodiment D3. The WD of Embodiment DI, wherein the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration.

Embodiment D4. The WD of Embodiment DI, wherein the Cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device.

Embodiment D5. The WD of Embodiment DI, wherein the Cell DTX onDuration is a subset of the C-DRX onDuration for the wireless device.

Embodiment D6. The WD of any one of Embodiments DI -D5, wherein the resulting onDuration is configured to at least partially overlap the cell DTX onDuration.

Embodiment D7. The WD of Embodiment DI, wherein the C-DRX onDuration for the wireless device does not overlap with the Cell DTX onDuration.

Embodiment D8. The WD of Embodiment D7, wherein the C-DRX onDuration for the wireless device one of: has a shorter time period than the cell DTX onDuration; and has a longer time period than the cell DTX onDuration.

Embodiment D9. The WD of any one of Embodiments D1-D8, wherein an inactivity timer of C-DRX is used to extend the resulting onDuration within the Cell DTX onDuration.

Embodiment DIO. The WD of Embodiments D9, wherein the inactivity timer of Cell DTX is used to extend the resulting onDuration outside of the Cell DTX onDuration.

Embodiment El. A method implemented by a wireless device (WD) that is configured to communicate with a network node, the method comprising: operating in connected mode discontinuous reception, C-DRX according to a resulting onDuration that is based on a configured C-DRX onDuration for the wireless device and a cell discontinuous transmission, DTX, onDuration. Embodiment E2. The method of Embodiment El, wherein the C-DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration.

Embodiment E3. The method of Embodiment El, wherein the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration.

Embodiment E4. The method of Embodiment El, wherein the Cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device.

Embodiment E5. The method of Embodiment El, wherein the Cell DTX onDuration is a subset of the C-DRX onDuration for the wireless device.

Embodiment E6. The method of any one of Embodiments E1-E5, wherein the resulting onDuration is configured to at least partially overlap the cell DTX onDuration.

Embodiment E7. The method of Embodiment El, wherein the C-DRX onDuration for the wireless device does not overlap with the Cell DTX onDuration.

Embodiment E8. The method of Embodiment E7, wherein the C-DRX onDuration for the wireless device one of: has a shorter time period than the cell DTX onDuration; and has a longer time period than the cell DTX onDuration.

Embodiment E9. The method of any one of Embodiments E1-E8, wherein an inactivity timer of C-DRX is used to extend the resulting onDuration within the Cell DTX onDuration.

Embodiment E10. The method of Embodiment E9, wherein the inactivity timer of Cell DTX is used to extend the resulting onDuration outside of the Cell DTX onDuration. Embodiment Fl. A non-transitory computer readable medium storing program instructions that, when executed by a processor, configure the processor to implement the method of any one of Embodiments El to E10.

Claims

1. A method implemented by a wireless device, WD, (22) that is configured to communicate with a network node (16), the method comprising:

- the WD (22) receiving a cell Discontinuous Transmission, cell DTX, configuration of the network node (16), the cell DTX configuration defining a cell DTX active time;

- the WD (22) transmitting a Hybrid Automatic Repeat Request, HARQ, negative acknowledgement, NACK, for a downlink, DL, wireless transmission from the network node (16); and

- in response to the HARQ NACK, the WD (22) monitoring for DL re-transmissions from the network node (16) after the cell DTX active time has ended.

2. The method according to claim 1, wherein the WD (22) is configured with connected mode Discontinuous Reception, C- DRX.

3. The method according to claim 1 or 2, wherein the WD (22) performs said monitoring for DL re-transmissions after the cell DTX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place.

4. The method according to any of the preceding claims, wherein duration of a HARQ transmission permission window and duration of said monitoring for DL re-transmissions are configured by the network node (16).

5. The method according to any of the preceding claims, wherein a rule according to which the WD (22) performs said monitoring for DL retransmissions after the cell DTX active time is configured individually for the WD (22).

6. The method according to any of the preceding claims, wherein a rule according to which the WD (22) performs said monitoring for DL retransmissions after the cell DTX active and/or whether to apply the rule is indicated in the scheduling DL Control Information, DCI, of the DL wireless transmission.

7. The method according to any of the preceding claims, wherein the WD (22) receives the cell DTX configuration from the network node (16).

8. The method according to claim 7, wherein the WD (22) receives the cell DTX configuration while in Radio Resource Control, RRC, connected state.

9. The method according to claim 7 or 8, wherein the WD (22) receives the cell DTX configuration through RRC configuration.

10. The method according to any of claims 7 to 9, wherein the WD (22) receives the cell DTX configuration through system information, SI, broadcast.

11. A method implemented by a wireless device, WD, (22) that is configured to communicate with a network node (16), the method comprising:

- the WD (22) receiving a cell Discontinuous Reception, cell DRX, configuration of the network node (16), the cell DRX configuration defining a cell DRX active time;

- the WD (22) receiving a downlink, DL, wireless transmission from the network node (16); and

- the WD (22) transmitting Hybrid Automatic Repeat Request, HARQ, feedback for the DL wireless transmission, wherein the WD (22) transmits the HARQ feedback after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time.

12. The method according to claim 11, wherein the WD (22) is configured with connected mode Discontinuous Reception, C- DRX.

13. The method according to claim 11 or 12, wherein the WD (22) transmits the HARQ feedback after the cell DRX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place.

14. The method according to any of claims 11 to 13, wherein a rule according to which the WD (22) transmits the HARQ feedback after the cell DRX active time is configured individually for the WD (22).

15. The method according to any of claims 11 to 14, wherein a rule according to which the WD (22) transmits the HARQ feedback after the cell DRX active time and/or whether to apply the rule is indicated in scheduling DL Control Information, DCI, of the DL wireless transmission.

16. The method according to any of claims 11 to 15, wherein the WD (22) receives the cell DRX configuration from the network node (16).

17. The method according to claim 16, wherein the WD (22) receives the cell DRX configuration while in Radio Resource Control, RRC, connected state.

18. The method according to claim 16 or 17, wherein the WD (22) receives the cell DRX configuration through RRC configuration.

19. The method according to any of claims 16 to 18, wherein the WD (22) receives the cell DTX configuration through system information, SI, broadcast.

20. A method implemented by a network node (16) that is configured to communicate with a wireless device (22), the method comprising:

- the network node (16) providing a cell Discontinuous Transmission, cell DTX, configuration of the network node (16) to the WD (22), the cell DTX configuration defining a cell DTX active time;

- the network node (16) receiving, from the WD (22), a Hybrid Automatic Repeat Request, HARQ, negative acknowledgement, NACK, for a downlink, DL, wireless transmission from the network node (16); and

- in response to the HARQ NACK, the network node (16) sending a DL re-transmission to the WD (22) after the cell DTX active time has ended.

21. The method according to claim 20, wherein the WD (22) is configured with connected mode Discontinuous Reception, C- DRX.

22. The method according to claim 20 or 21, wherein the WD (22) sends the DL re-transmission after the cell DTX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place.

23. The method according to any of claims 20 to 22, wherein duration of a HARQ transmission permission window and duration of said monitoring for DL re-transmissions are configured by the network node (16).

24. The method according to any of claims 20 to 23, wherein a rule according to which the WD (22) performs said monitoring for DL retransmissions after the cell DTX active time is configured individually for the WD (22).

25. The method according to any of claims 20 to 24, wherein a rule according to which the WD (22) performs said monitoring for DL retransmissions after the cell DTX active and/or whether to apply the rule is indicated in the scheduling DL Control Information, DCI, of the DL wireless transmission.

26. The method according to any of claims 20 to 25, wherein the network node (16) provides the cell DTX configuration while the WD (22) is in Radio Resource Control, RRC, connected state.

27. The method according to any of claims 20 or 26, wherein the network node (16) provides the cell DTX configuration through RRC configuration.

28. The method according to any of claims 20 to 27, wherein the network node (16) provides the cell DTX configuration through system information, SI, broadcast.

29. A method implemented by a network node (16) that is configured to communicate with a wireless device, WD, (22), the method comprising:

- the network node providing a cell Discontinuous Reception, cell DRX, configuration of the network node (16) to the WD (22), the cell DRX configuration defining a cell DRX active time;

- the network node (16) transmitting a downlink, DL, wireless transmission to the WD (22); and

- the network node (16) receiving Hybrid Automatic Repeat Request, HARQ, feedback for the DL wireless transmission, wherein the network node (16) expects the HARQ feedback after the cell DRX active time has ended if the DL transmission was transmitted during the cell DRX active time.

30. The method according to claim 29, wherein the WD (22) is configured with connected mode Discontinuous Reception, C- DRX.

31. The method according to claim 29 or 30, wherein the network node (16) expects the HARQ feedback after the cell DRX active time has ended only if fewer than a maximum number of HARQ retransmissions for the DL wireless transmission has taken place.

32. The method according to any of claims 29 to 31, wherein a rule according to which the WD (22) performs said transmitting of the HARQ feedback after the cell DRX active time is configured individually for the WD (22).

33. The method according to any of claims 29 to 32, wherein a rule according to which the WD (22) performs said transmitting of the HARQ feedback after the cell DRX active time and/or whether to apply the rule is indicated in the scheduling DL Control Information, DCI, of the DL wireless transmission.

34. The method according to any of claims 29 to 33, wherein the network node (22) provides the cell DRX configuration while the WD (22) is in Radio Resource Control, RRC, connected state.

35. The method according to claim 29 or 34, wherein the network node (16) provides the cell DRX configuration through RRC configuration.

36. The method according to any of claims 16 to 18, wherein the network node (16) provides the cell DTX configuration through system information, SI, broadcast.

37. A wireless device, WD, (22) configured to communicate with a network node (16), the WD (22) being further configured to:

- receive a cell Discontinuous Transmission, cell DTX, configuration of the network node (16), the cell DTX configuration defining a cell DTX active time;

- transmit a Hybrid Automatic Repeat Request, HARQ, negative acknowledgement, NACK, for a downlink, DL, wireless transmission from the network node (16); and

- in response to the HARQ NACK, monitor for DL re-transmissions from the network node (16) after the cell DTX active time has ended.

38. The WD (22) according to claim 37, configured to perform the method of any of claims 2 to 10.

39. The WD (22) according to claim 37 or 38, comprising: processing circuitry (84) and a memory (88) storing program instructions that, when executed by a processing circuity (84), cause the WD (22) to perform the method of any of claims 1 to 10.

40. A wireless device, WD, (22) configured to communicate with a network node (16), the WD (22) being further configured to:

- receive a cell Discontinuous Reception, cell DRX, configuration of the network node (16), the cell DRX configuration defining a cell DRX active time;

- receive a downlink, DL, wireless transmission from the network node (16); and

- transmit Hybrid Automatic Repeat Request, HARQ, feedback for the DL wireless transmission after the cell DRX active time has ended if the DL wireless transmission was received during the cell DRX active time.

41. The WD (22) according to claim 40, configured to perform the method of any of claims 12 to 19.

42. The WD (22) according to claim 37 or 38, comprising: processing circuitry (84) and a memory (88) storing program instructions that, when executed by a processing circuity (84), cause the WD (22) to perform the method of any of claims 11 to 19.

43. A network node (16) configured to communicate with wireless device, WD, (22), the network node (22) being further configured to:

- provide a cell Discontinuous Transmission, cell DTX, configuration of the network node (16) to the WD (22), the cell DTX configuration defining a cell DTX active time;

- receive, from the WD (22), a Hybrid Automatic Repeat Request, HARQ, negative acknowledgement, NACK, for a downlink, DL, wireless transmission from the network node (16); and

- in response to the HARQ NACK, send a DL re-transmission to the WD (22) after the cell DTX active time has ended.

44. The network node (16) according to claim 43, configured to perform the method of any of claims 21 to 28.

45. The network node (16) according to claim 43 or 44, comprising: processing circuitry (68) and a memory (72) storing program instructions that, when executed by a processing circuity (68), cause the network node (16) to perform the method of any of claims 20 to 28.

46. A network node (16) configured to communicate with wireless device, WD, (22), the network node (22) being further configured to:

- provide a cell Discontinuous Reception, cell DRX, configuration of the network node (16) to the WD (22), the cell DRX configuration defining a cell DRX active time;

- transmit a downlink, DL, wireless transmission to the WD (22); and

-receive Hybrid Automatic Repeat Request, HARQ, feedback for the DL wireless transmission, wherein the network node (16) expects the HARQ feedback after the cell DRX active time has ended if the DL transmission was transmitted during the cell DRX active time.

47. The network node (16) according to claim 43, configured to perform the method of any of claims 30 to 36.

48. The network node (16) according to claim 43 or 44, comprising: processing circuitry (68) and a memory (72) storing program instructions that, when executed by a processing circuity (68), cause the network node (16) to perform the method of any of claims 29 to 36.

49. A computer program comprising program instructions that, when executed by processing circuitry of a wireless device, WD, (22), cause the WD (22) to perform a method according to any of claims 1 to 19.

50. A computer program comprising program instructions that, when executed by processing circuitry of a network node (16), cause the network node (16) to perform a method according to any of claims 20 to 28.