UE behavior during cell DTX / DRX

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 from the network node (16), the cell DTX configuration specifying a cell DTX active time. The WD (22) may transmit a hybrid automatic repeat request (HARQ) negative acknowledgement (NACK) for a downlink (DL) radio transmission from the network node (16). In response to the HARQ NACK, the WD (22) may monitor for DL ​​retransmissions from the network node (16) after the cell DTX active time has expired. Furthermore, the WD (22) may receive a cell discontinuous reception (cell DRX) configuration from the network node (16), the cell DRX configuration specifying a cell DRX active time. The WD (22) receives DL radio transmissions from the network node (16) and, if the DL radio transmissions are received during the cell DRX active time, may receive HARQ feedback for the DL radio transmissions after the cell DRX active time has ended.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communications, and more particularly to wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission (DTX) and / or discontinuous reception (DRX). [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) wireless communication systems (also known as Long Term Evolution (LTE)) and fifth-generation (5G) wireless communication systems (also known as New Radio (NR)). Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WDs), as well as communication between network nodes and between WDs. 3GPP is also developing standards for sixth-generation (6G) wireless communication networks.

[0003] Radio Device C-DRX: Wireless device connected mode DRX (C-DRX) allows a wireless device to transition to a low power state when the wireless device is not required to receive transmissions from a network node. There is a periodic "onDuration" during which the wireless device wakes up and monitors a control channel, and if no control messages are detected by the wireless device, the wireless device may stop receiving transmissions from the network node until the next onDuration opportunity (e.g., no control signal monitoring). For uplink (UL) transmissions, the wireless device is not limited to onDuration opportunities and may transmit on a physical uplink control channel (PUCCH) or physical random access channel (PRACH) for UL transmission requests.

[0004] FIG. 1 is an exemplary diagram of a DRX cycle.

[0005] Network node energy consumption Network node energy consumption in NR increases relative to LTE due to more complex hardware, e.g., higher bandwidth (BW) and a larger number of antennas. This is especially evident when network nodes operate at higher frequencies. Therefore, it is important for network nodes to turn on / off unused hardware modules during inactivity times. For example, in FR2, up to 64 beams can be configured in an NR network node, and the NR network node can transmit up to 64 SSBs. This implies 64 ports with many transceiver chains. Such SSBs are transmitted every 20 ms within a 5 ms window to provide coverage to potential wireless devices even when no wireless devices are present in the cell. Another example of energy cost is the always-on broadcast transmission in SIB1, which is typically transmitted every 20 / 40 ms (per beam).

[0006] Cell DTX / DRX: Network node or network DTRX or cell DTX / DRX has been proposed in 3GPP Release 18 (Rel18) as a solution to help networks save more power. The idea is that the network in a known T / F resource can be active or inactive similar to the C-DRX or DRX mechanism on the wireless device side, thereby entering a sleep mode during the inactive time. Furthermore, it is expected that the wireless device and the network node will be coordinated during this operation.

[0007] However, the specific wireless device behavior when both wireless device DRX and cell DTX / DRX are configured is currently not specified. Summary of the Invention

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

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

[0010] According to one embodiment, a method is provided for implementation by a wireless device (WD). The WD is configured to communicate with a network node. According to the method, the WD receives a cell discontinuous transmission (cell DTX) configuration from the network node. The cell DTX configuration specifies a cell DTX active time. Furthermore, the WD transmits a hybrid automatic repeat request (HARQ) negative acknowledgement (NACK) for a downlink (DL) radio transmission from the network node. In response to the HARQ NACK, the WD monitors DL retransmissions from the network node after the cell DTX active time expires.

[0011] According to a further embodiment, there is provided a method implemented by a WD. 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. Furthermore, the WD receives a DL radio transmission from the network node and transmits HARQ feedback for the DL radio transmission. If the DL radio transmission is received during the cell DRX active time, the WD transmits the HARQ feedback after the cell DRX active time expires.

[0012] According to a further embodiment, there is provided a method implemented by a network node. The network node is configured to communicate with a WD. According to the method, the network node provides the WD with a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. Furthermore, the network node receives from the WD a HARQ NACK for a DL radio transmission from the network node. In response to the HARQ NACK, the network node sends a DL retransmission to the WD after the cell DTX active time expires.

[0013] According to a further embodiment, there is provided a method implemented by a network node. The network node is configured to communicate with a WD. According to the method, the network node provides the WD with a cell DRX configuration of the network node. The cell DRX configuration defines a cell DRX active time. Furthermore, the network node transmits a DL radio transmission to the WD. Furthermore, the network node receives HARQ feedback for the DL radio transmission. If the DL radio transmission was transmitted during the cell DRX active time, the network node expects the HARQ feedback after the cell DRX active time has expired.

[0014] According to a further embodiment, there is provided a WD. The WD is configured to communicate with a network node. The WD is further configured to receive a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. The WD is further configured to transmit a HARQ NACK for a DL radio transmission from the network node. The WD is further configured to monitor DL ​​retransmissions from the network node after the cell DTX active time expires in response to the HARQ NACK.

[0015] According to a further embodiment, a wireless driver configured to communicate with a network node is provided. The wireless driver includes a processing circuit and a memory storing program instructions that, when executed by the processing circuit, cause the wireless driver to receive a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. Execution of the program instructions further causes the wireless driver to transmit a HARQ NACK for a DL radio transmission from the network node. Execution of the program instructions further causes the wireless driver to monitor for DL ​​retransmissions from the network node after the cell DTX active time expires in response to the HARQ NACK.

[0016] According to a further embodiment, there is provided a WD, the WD configured to communicate with a network node, the WD configured to receive a cell DRX configuration of the network node, the cell DRX configuration defining a cell DRX active time, the WD configured to receive DL radio transmissions from the network node, and, if the DL radio transmissions are received during the cell DRX active time, to transmit HARQ feedback for the DL radio transmissions after the cell DRX active time expires.

[0017] According to a further embodiment, there is provided a WD configured to communicate with a network node, the WD comprising: a processing circuit; and a memory storing program instructions that, when executed by the processing circuit, cause the WD to receive a cell DRX configuration of the network node. The cell DRX configuration defines a cell DRX active time. Execution of the program instructions further causes the WD to receive a DL radio transmission from the network node and, if the DL transmission is received during the cell DRX active time, to transmit HARQ feedback for the DL radio transmission after the cell DRX active time expires.

[0018] According to a further embodiment, there is provided a network node, the network node configured to communicate with a WD, the network node configured to provide the WD with a cell DTX configuration of the network node, the cell DTX configuration defining a cell DTX active time, the network node configured to receive from the WD a HARQ NACK for a DL radio transmission from the network node, the network node configured to send a DL retransmission to the WD after the cell DTX active time expires in response to the HARQ NACK.

[0019] According to a further embodiment, a network configured to communicate with a WD is provided. The network node comprises a processing circuit and a memory storing program instructions that, when executed by the processing circuit, 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. Execution of the program instructions further causes the network node to receive, from the WD, a HARQ NACK for a DL radio transmission from the network node. Execution of the program instructions further causes the network node to send a DL retransmission to the WD in response to the HARQ NACK after the cell DTX active time has expired.

[0020] According to a further embodiment, there is provided a network node, the network node configured to communicate with a WD, the network node configured to provide the WD with a cell DRX configuration of the network node, the cell DRX configuration defining a cell DRX active time, the network node configured to send DL radio transmissions to the WD, the network node configured to receive HARQ feedback for the DL radio transmissions and to expect the HARQ feedback after the cell DRX active time has expired if the DL radio transmissions were transmitted during the cell DRX active time.

[0021] According to a further embodiment, there is provided a network node configured to communicate with a WD. The network node comprises a processing circuit and a memory storing program instructions that, when executed by the processing circuit, 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. Execution of the program instructions further causes the network node to send a DL radio transmission to the WD. Execution of the program instructions further causes the network node to receive HARQ feedback for the DL radio transmission and, if the DL radio transmission was transmitted during the cell DRX active time, to expect the HARQ feedback after the cell DRX active time expires.

[0022] 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, comprising program instructions that, when executed by a processing circuit 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. Execution of the program instructions further causes the WD to send a HARQ NACK for a DL radio transmission from the network node. Execution of the program instructions further causes the WD to monitor DL ​​retransmissions from the network node after the cell DTX active time has expired in response to the HARQ NACK.

[0023] 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, comprising 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. Execution of the program instructions further causes the WD to receive DL radio transmissions from the network node and, if the DL radio transmissions are received during the cell DRX active time, to transmit HARQ feedback for the DL radio transmissions after the cell DRX active time has expired.

[0024] 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, comprising program instructions that, when executed by processing circuitry of a network for communication with a WD, cause a network node to provide the WD with a cell DTX configuration of the network node. The cell DTX configuration defines a cell DTX active time. Execution of the program instructions further causes the network node to receive, from the WD, a HARQ NACK for a DL radio transmission from the network node. Execution of the program instructions further causes the network node to send a DL retransmission to the WD in response to the HARQ NACK after the cell DTX active time has expired.

[0025] According to a further embodiment, a computer program or computer program product is provided, for example in the form of a non-transitory computer-readable medium, comprising program instructions that, when executed by processing circuitry of a network for communication with a WD, cause a network node to provide the WD with a cell DRX configuration of the network node. The cell DRX configuration defines a cell DRX active time. Execution of the program instructions further causes the network node to send DL radio transmissions to the WD. Execution of the program instructions further causes the network node to receive HARQ feedback for the DL radio transmissions and, if the DL radio transmissions were transmitted during the cell DRX active time, to expect the HARQ feedback after the cell DRX active time has expired.

[0026] A more complete understanding of the present embodiments, and their attendant advantages and features, will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which: [Brief explanation of the drawings]

[0027] [Figure 1] FIG. 1 is an exemplary diagram of a DRX cycle. [Figure 2] FIG. 10 is a diagram illustrating an example of onDuration of a wireless device. [Figure 3] 1 is a schematic diagram of an exemplary network architecture illustrating a communication system connected to a host computer through an intermediate network in accordance with principles of the present disclosure; [Figure 4] 1 is a block diagram of a host computer communicating with a wireless device via a network node, at least partially over a wireless connection, in accordance with some embodiments of the present disclosure. FIG. [Figure 5] 1 is a flowchart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for executing a client application on a wireless device, according to some embodiments of the present disclosure. [Figure 6] 1 is a flowchart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at a wireless device, in accordance with some embodiments of the present disclosure. [Figure 7] 1 is a flowchart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at a host computer from a wireless device, in accordance with some embodiments of the present disclosure. [Figure 8] 1 is a flowchart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at a host computer, in accordance with some embodiments of the present disclosure. [Figure 9] 1 is a flowchart of an example process in a network node, in accordance with some embodiments of the present disclosure. [Figure 10] 1 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure. [Figure 11] FIG. 10 is a diagram of an example of a wireless device C-DRX active time and a cell DTX active time and a resulting active time in accordance with some embodiments of the present disclosure. [Figure 12] 10A-10C are diagrams illustrating examples of extending active time according to some embodiments of the present disclosure. [Figure 13] 1 is a flowchart illustrating an example method in a wireless device, according to some embodiments of the present disclosure. [Figure 14] 1 is a flowchart illustrating an example method in a network node, according to some embodiments of the present disclosure. [Figure 15] 10 is a flowchart illustrating a further exemplary method in a wireless device, according to some embodiments of the present disclosure. [Figure 16]10 is a flowchart illustrating a further exemplary method in a network node, according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0028] As described above, the specific wireless device behavior when both wireless device DRX and cell DTX / DRX are configured is not currently specified. For example, in a certain system, how should a wireless device behave when both wireless device DRX and cell DTX / DRX are configured as broadly described?

[0029] For example, the portion in the network node onDuration that may be used for UL or downlink (DL) is based on the wireless device C-DRX onDuration setting (i.e., not specifically configured for network node DTRX active time). In another example, the portion in the network node onDuration that may be used for UL or DL ​​is the same as the wireless device C-DRX onDuration opportunity that overlaps / coincides with the network node onDuration opportunity (i.e., the wireless device's C-DRX opportunity is masked by the network node onDuration opportunity).

[0030] FIG. 2 is a diagram of a wireless device's onDuration overlapping with a network node's DTRX onDuration, with outlying onDuration masked.

[0031] A rough mechanism of wireless device behavior with C-DRX and cell DTX / DRX configured is shown in FIG. 2, the details of which are yet to be further determined, especially in boundary cases such as when the wireless device C-DRX active time falls partially between the cell DTX / DRX active time and the inactive time as shown in FIG. 2.

[0032] Before describing the exemplary embodiments in detail, it should be noted that the embodiments reside primarily in a combination 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, where appropriate, components are represented by conventional symbols in the drawings, and only those specific details relevant to understanding the embodiments are shown, so as not to obscure the present disclosure with details that will be readily apparent to those skilled in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0033] As used herein, relational terms such as “first” and “second,” “upper” and “lower,” etc., may be used merely to distinguish one entity or element from another, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is merely for the purpose of describing particular embodiments and is not intended to limit the concepts described herein. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly dictates otherwise. Furthermore, as used herein, the terms “comprises,” “comprising,” “includes,” and / or “including” will be understood to specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0034] In the embodiments described herein, joining terms such as "in communication with" may be used to indicate electrical or data communication that may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that multiple components may interoperate and that modifications and variations are possible in achieving electrical and data communication.

[0035] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection, although not necessarily a direct connection, and may include a wired and / or wireless connection.

[0036] The term "network node" as used herein may be any kind of network node provided in a wireless network, which may further comprise any of a base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), gNodeB (gNB), evolved node B (eNB or eNodeB), Node B, MSR radio node such as a multi-standard radio (MSR) BS, multi-cell / multicast coordination entity (MCE), integrated radio access backhaul (IAB) node, relay node, donor node controlled relay, radio access point (AP), transmission point, transmitting node, remote radio unit (RRU), remote radio head (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third party node, node outside the current network), node in a distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. The network node may also include test equipment. As used herein, the term "wireless node" may also be used to refer to a wireless device (WD) such as a wireless device (WD) or a wireless network node.

[0037] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. A WD herein may be any type of wireless device capable of communicating with a network node or another WD via wireless signals, such as a wireless device (WD). A WD may also be a wireless communication device, a target device, a device-to-device (D2D) WD, a machine-type WD or a WD capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0038] Also, in some embodiments, the general term "radio network node" is used. The radio network node may be any type of radio network node, which may comprise a base station, a radio base station, a base transceiver station, a base station controller, a network controller, an RNC, an evolved Node B (eNB), a Node B, a gNB, a multi-cell / multicast coordination entity (MCE), an IAB node, a relay node, an access point, a radio access point, a remote radio unit (RRU), or a remote radio head (RRH).

[0039] It should be noted that while terminology from one particular wireless system, such as 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be considered to limit the scope of this disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas covered within this disclosure.

[0040] It should be further noted that functionality described herein as being performed by a wireless device or network node may be distributed over multiple wireless devices and / or network nodes. In other words, it is contemplated that the functionality of the network nodes and wireless devices described herein is not limited to implementation by a single physical device, but may in fact be distributed among several physical devices.

[0041] In some embodiments, a general description element of the form "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 corresponds to one or more of A and B, or corresponds 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 combinations thereof.

[0042] Unless otherwise specified, 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 the terms used herein should be interpreted as having a meaning in accordance with the meaning of those terms in the context of this specification and related art, and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

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

[0044] Referring again to the drawings, where like elements are referred to by like reference numerals, FIG. 3 shows a schematic diagram of a communication system 10, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), comprising an access network 12, such as a wireless access network, and a core network 14, according to one embodiment. The access network 12 comprises multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in the 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 corresponding network node 16b. While multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only one WD is in a coverage area or where only one WD connects to a corresponding network node 16. For convenience, only two WDs 22 and three network nodes 16 are shown, but it should be noted that a communication system may include many more WDs 22 and network nodes 16.

[0045] It is also contemplated that the WD 22 may be in simultaneous and / or configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, the WD 22 may have dual connectivity with a network node 16 supporting LTE and the same or different network node 16 supporting NR. As an example, the WD 22 may be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0046] The communication system 10 may itself be connected to a host computer 24, which may be embodied in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 24 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. 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 through an optional intermediate network 30. The intermediate network 30 may be one of a public network, a private network, or a hosted network, or a combination of two or more thereof. The intermediate network 30, if present, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more subnetworks (not shown).

[0047] 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 networks 30, and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of the uplink and downlink communications. For example, the network node 16 may not be or need not be informed regarding the past routing of incoming downlink communications involving data originating from the host computer 24 that is to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of outgoing uplink communications originating from the WD 22a and destined for the host computer 24.

[0048] The network node 16 is configured to include a discontinuous unit 32 configured to implement 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 wireless device 22 is configured to include a DRX unit 34 configured to implement one or more wireless device 22 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).

[0049] An exemplary implementation of the WD 22, network node 16, and host computer 24 described in the previous paragraph, according to one embodiment, will now be described with reference to FIG. 4. In communication system 10, host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of communication system 10. Host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. Processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor and memory, such as a central processing unit, processing circuitry 42 may comprise integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits), adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) the memory 46, which may include any type of volatile and / or non-volatile memory, such as 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).

[0050] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed by, for example, host computer 24. Processor 44 corresponds to one or more processors 44 for performing the host computer 24 functions described herein. Host computer 24 includes memory 46 configured to store data, programmatic software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause 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 host computer 24.

[0051] Software 48 may be executable by processing circuitry 42. Software 48 includes a host application 50. Host application 50 may be operable to provide services to remote users, such as WD 22, connecting via an OTT connection 52 that terminates at WD 22 and host computer 24. In providing services to remote users, host application 50 may provide user data that is transmitted using OTT connection 52. "User data" may be data and information, as described herein as implementing described functionality. In one embodiment, host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. Processing circuitry 42 of host computer 24 may enable host computer 24 to observe, monitor, control, transmit to, and / or receive from network nodes 16 and / or wireless devices 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, configure, 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).

[0052] The communication system 10 further includes a network node 16 provided therein, the network node 16 including hardware 58 that enables the network node 16 to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 10, as well as a wireless interface 62 for setting up and maintaining at least a wireless connection 64 with the WD 22 located within the coverage area 18 served by the network node 16. The wireless interface 62 may be formed as or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct, or the connection 66 may pass through the core network 14 of the communication system 10 and / or one or more intermediate networks 30 external to the communication system 10.

[0053] 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 and memory, such as a central processing unit, the processing circuitry 68 may comprise integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits), adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may include any type of volatile and / or non-volatile 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).

[0054] Thus, network node 16 further has software 74 stored, for example, internally in memory 72 or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 may be executable by processing circuitry 68. Processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. Memory 72 is configured to store data, programmatic software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform processes described herein with respect to network node 16. For example, the processing circuitry 68 of the network node 16 may include an intermittent unit 32 configured to perform one or more network node 16 functions as described herein, such as with respect to wireless device connected mode intermittent reception (C-DRX) during cell intermittent transmission (DTX) and / or intermittent reception (DRX).

[0055] The communication system 10 further includes the previously mentioned WD 22. The WD 22 may have hardware 80 that may include a wireless interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 that serves the coverage area 18 in which the WD 22 is currently located. The wireless interface 82 may be formed as or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0056] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and a memory 88. In particular, in addition to or instead of a processor and memory such as a central processing unit, the processing circuitry 84 may comprise integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) the memory 88, which may include any type of volatile and / or non-volatile 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).

[0057] Thus, the WD 22 may further comprise software 90, which may be stored, for example, in memory 88 in the WD 22 or in an external memory accessible by the WD 22 (e.g., a database, a storage array, a network storage device, etc.). 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 services to a human or non-human user via the WD 22 with the support of the host computer 24. On the host computer 24, a running host application 50 may communicate with the running client application 92 via an OTT connection 52 that terminates at the WD 22 and the host computer 24. In providing services 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 the client application 92 provides.

[0058] 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, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 configured to store data, programmatic software code, and / or other information described herein. In some embodiments, the software 90 and / or client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuitry 84, cause the processor 86 and / or the processing circuitry 84 to perform the processes described herein with respect to the 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 herein, such as with respect to cell discontinuous transmission (DTX) and / or wireless device connected mode discontinuous reception (C-DRX) during DRX.

[0059] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as shown in FIG. 4, and separately, the surrounding network topology may be that of FIG.

[0060] 4, OTT connection 52 is depicted abstractly to show communication between host computer 24 and wireless device 22 via network nodes 16, without explicit reference to intermediary devices and the precise routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from WD 22, the service provider operating host computer 24, or both. While OTT connection 52 is active, the network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0061] The wireless connection 64 between the WD 22 and the network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the WD 22 using the OTT connection 52, of which the wireless connection 64 may form the final segment. More precisely, the teachings of some of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed limits on file size, better responsiveness, extended battery life, etc.

[0062] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to fluctuations in the measurement results. The measurement procedures 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 associated with the communication devices through which the OTT connection 52 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above or other physical quantities from which the software 48, 90 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include changes to message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the network node 16, and the reconfiguration may be unknown or imperceptible to the network node 16. Some such procedures and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary WD signaling that facilitates host computer 24 measurements of throughput, propagation time, latency, etc. In some embodiments, the measurements may be implemented in that software 48, 90 causes messages, particularly empty or "dummy" messages, to be sent using OTT connection 52 while software 48, 90 monitors propagation time, errors, etc.

[0063] Thus, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and a communications interface 40 configured to forward the user data to the cellular network for transmission to WD 22. In some embodiments, the cellular network also includes network node 16 having a wireless interface 62. In some embodiments, network node 16 is configured to implement, and / or processing circuitry 68 of network node 16 is configured to implement, the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to WD 22 and / or preparing / terminating / maintaining / supporting / terminating in receipt of transmissions from WD 22.

[0064] In some embodiments, host computer 24 includes processing circuitry 42 and communications interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to implement and / or comprises a wireless interface 82 and / or processing circuitry 84 configured to implement the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16 and / or preparing / terminating / maintaining / supporting / terminating in reception of transmissions from network node 16.

[0065] 3 and 4 show various "units," such as intermittent unit 32 and DRX unit 34, as being within their respective processors, it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, the units may be implemented in hardware or a combination of hardware and software within the processing circuitry.

[0066] 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication systems of FIGS. 3 and 4, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be as described with reference to FIG. 4. In a first step of the method, the host computer 24 provides user data (block S100). In an optional sub-step of the first step, the host computer 24 provides the user data by executing a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S104). In an optional third step, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the WD 22 (block S106), in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step, the WD 22 executes a client application, such as client application 92, associated with the host application 50 executed by the host computer 24 (block S108).

[0067] 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of FIG. 3, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be as described with reference to FIGS. 3 and 4. In a first step of the method, the host computer 24 provides user data (block S110). In an optional sub-step (not shown), the host computer 24 provides the user data by executing a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S112). The transmission may proceed 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 S114).

[0068] 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of FIG. 3, according to 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 S116). In an optional sub-step of the first step, the WD 22 executes a client application 92, which provides user data in response to the received input data provided by the host computer 24 (block S118). Additionally or alternatively, in an optional second step, the WD 22 provides the user data (block S120). In an optional sub-step of the second step, the WD provides the user data by executing a client application, such as the client application 92 (block S122). In providing the user data, the executed client application 92 may further take into account user input received from a user. Regardless of the particular manner in which the user data was provided, in an optional third substep, WD 22 may initiate transmission of the user data to host computer 24 (block S124). In a fourth step of the method, host computer 24 receives the user data transmitted from WD 22 (block S126) in accordance with the teachings of the embodiments described throughout this disclosure.

[0069] In the context of this disclosure, the cell DTX / DRX mechanism may involve the following: Cell DTX / DRX may be UE-specifically configured using RRC signaling. Thus, different UEs or groups of UEs may be configured with different cell DTX / DRX patterns or settings. Therefore, it may be desirable for there to be no requirement for the network to ensure that the same cell DTX / DRX pattern applies to all UEs and is always communicated to all UEs.

[0070] Furthermore, it should be noted that despite the designation "cell DTX / DRX," there may be implications to UE behavior, and UE behavior may need to be specified for specific signals / channels when cell DTX / DRX is configured. Below, some examples of such UE behavior are addressed.

[0071] There are some channels / signals, e.g., PDCCH or PDSCH, that the gNB already controls and can decide whether to transmit or not. Furthermore, assuming that cell DTX / DRX should not affect idle / inactive UEs, some channels, such as SI / paging and idle mode RACH, should not be affected. On the other hand, there are some channels, especially in connected mode, e.g., SR or connected mode PRACH, that can be explicitly controlled by cell DTX / DRX, e.g., periodic transmissions, e.g., periodic CSI-RS, TRS, or periodic UL resources. Each of these channels / signals is described in more detail below.

[0072] Regarding the impact of cell DTX / DRX on UL channels / signals, it can be expected that this is where the main strength of cell DTX / DRX comes into play, particularly for periodic UL resources, e.g., periodic SR or connected mode PRACH, as opposed to simply aligning UE DRX opportunities, which can be done using existing mechanisms. In this case, the network does not know whether the UE will transmit something on the UL; it must listen anyway, preventing it from entering a deeper sleep mode. Therefore, cell DTX / DRX can be used to provide a configuration for the UE so that it knows whether it can transmit a particular SR or PRACH during cell DRX inactive time. Typically, it can be assumed that the UE should avoid transmitting on the UL while in connected mode and during cell DRX inactive time. This also applies to periodic SRS transmissions unless configured otherwise. However, some exemptions may apply, for example, if SR is scheduled aperiodically by the network.

[0073] UEs in connected mode should be able to be configured not to transmit SR or PRACH during cell DRX off times. For example, all configured grants, or semi-persistent or periodic CSI reporting or SRS transmissions are canceled. RAN1 can discuss and decide on an exemption, for example, if UL PUSCH or SR is scheduled by the NW using aperiodic PDCCH.

[0074] Regarding the impact on ongoing HARQ processes, note that HARQ processes are important to ensure that the UE correctly receives data packets and that delivery is terminated. Therefore, entering a cell DTX / DRX inactive period should not result in a stoppage of an ongoing HARQ process if that HARQ process is not terminated. Therefore, even if cell DTX / DRX is not active but a HARQ process and retransmission is initiated due to a packet being scheduled during an active period, the UE should still monitor the relevant PDCCH and transmit the relevant UL signal, i.e., PUCCH / PUSCH. Currently running HARQ processes should continue even during cell DTX / DRX inactive periods if the relevant process was initiated during cell DTX / DRX active time, i.e., the UE should monitor the relevant PDCCH or transmit the required ACK / NACK. FFS: Where the maximum number of retransmissions can be configured.

[0075] Regarding the impact on periodic transmissions, it should be noted that periodic transmissions, such as periodic CSI-RS and TRS, or DL ​​SPS, may prevent the network from entering a deeper sleep mode even during cell DTX / DRX inactive times. Therefore, it may be beneficial for the network to have control to configure not to transmit them during inactive times. According to one example, a UE in connected mode should not expect periodic transmissions during cell DTX / DRX off times, except for SSBs, e.g., CSI-RS, TRS, DL SPS, etc.

[0076] For activation / deactivation of the cell DTX / DRX pattern, L1 / L2-based activation / deactivation of the cell DTX / DRX pattern may be considered. For example, the cell DTX / DRX pattern may be configured using UE-specific RRC signaling, but the cell DTX / DRX pattern may potentially be turned on / off using L1 / L2 signaling. L2 signaling, which mostly refers to MAC-CE, may have the advantage of being more robust due to the acknowledgement required by the UE. However, it may happen that conventional L2 signaling is not much faster than RRC signaling. Therefore, it may be preferable to use L1- or DCI-based signaling to activate and deactivate the cell DTX / DRX, while considering that the mechanism should be designed as robust as possible to ensure that mismatches between the UE and the network are extremely rare. However, it may be useful if a cell DTX / DRX mechanism that does not rely on explicit L1 / L2 activation / deactivation is specified. DCI-based activation / deactivation of cell DTX / DRX may be considered.

[0077] In addition to the L1-based mechanism for activating or deactivating cell DTX / DRX, as described above, it may also be useful to ensure that current packet delivery to the UE is not interrupted by the cell DTX / DRX inactivity time. Therefore, a mechanism similar to the UE C-DRX inactivity timer may be considered for the cell DTX / DRX inactivity timer. For the UE C-DRX inactivity timer, implicit signaling is typically used to restart the inactivity timer, i.e., to schedule new data. A similar approach may be used for cell DTX / DRX, but with a shorter inactivity timer, so that the network can return to off time as quickly as possible. Alternatively or additionally, explicit indication using L1-based signaling may be used, where the network can explicitly instruct the UE that it should start the cell DTX / DRX inactivity timer and for how long. Therefore, at least implicit L1-based signaling may be used to trigger the cell DTX / DRX inactivity timer. Explicit L1 signaling may also be considered. Implicit signaling may schedule new data and trigger a restart of the inactivity timer for a default or configured value, and explicit L1-based signaling may be used to trigger the inactivity timer at a value chosen between multiple configured values.

[0078] In the previous section, the following observations and suggestions were made. - Regardless of the cell DTX status, there are DCIs that the UE should monitor, such as DCI scheduling SIB1, or SI updates or PWS. - It is necessary to determine the PDCCH signals that need to be monitored by the UE regardless of the cell DTX status, e.g., SI updates, PWSs, or PDCCHs in response to SRs sent by the UE, or PDCCHs related to ongoing HARQ processes. - UEs in connected mode should be able to be configured not to transmit SR or PRACH during cell DRX off times. For example, all configured grants, periodic reports, or SRS transmissions are canceled. RAN1 can discuss and decide on an exemption, for example, if UL PUSCH or SR is scheduled by the NW using aperiodic PDCCH. - A currently running HARQ process should continue even during cell DTX / DRX inactive periods if the associated process was started during cell DTX / DRX active time, i.e. the UE should monitor the associated PDCCH or transmit the required ACK / NACK. FFS: Where the maximum number of retransmissions can be configured. - UEs in connected mode should not expect periodic transmissions during cell DTX / DRX off times, except for SSB, e.g., CSI-RS, TRS, etc. FFS: CSI-RS for mobility? - When the UE is able to perform inter-frequency / inter-RAT measurements in the cell DTX period, measurement gaps may be used for normal communication. FFS: Detailed conditions on when measurement gaps may be used for normal communication. - DCI based activation / deactivation of cell DTX / DRX may be considered. FFS: Detailed design. Both implicit and explicit L1-based signaling can be used to trigger the cell DTX / DRX inactivity timer: implicit signaling can schedule new data and trigger a restart of the inactivity timer for a default or configured value, and explicit L1-based signaling can be used to trigger the inactivity timer with a value chosen between multiple configured values.

[0079] For higher layer procedures related to cell DTX / RTX, the following may be considered:

[0080] Cell DTX / DRX applies at least to UEs in RRC_CONNECTED state. Periodic cell DTX / DRX (i.e., active and inactive periods) can be configured by the gNB via UE-specific RRC signaling per serving cell. The following examples for cell DTX / DRX behavior during inactive periods are assumed to be possible options, and the UE behavior / impact is further evaluated below:

[0081] Example 1: The gNB is expected to turn off all transmission and reception for data traffic and reference signals during cell DTX / DRX inactivity periods.

[0082] Example 2: The gNB is expected to turn off gNB transmission / reception only for data traffic during cell DTX / DRX inactivity periods (i.e., the gNB will still transmit / receive reference signals).

[0083] Example 3: The gNB is expected to turn off its dynamic data transmission / reception during cell DTX / DRX inactivity periods (i.e., the gNB is expected to still transmit / receive during periodic resources, including SPS, CG-PUSCH, SR, RACH, and SRS).

[0084] Example 4: The gNB is expected to transmit only reference signals (e.g., CSI-RS for measurements).

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

[0086] The cell DTX / DRX mode can be activated / deactivated via dynamic L1 / L2 signaling and UE-specific RRC signaling. Both UE-specific L1 / L2 signaling and common L1 / L2 signaling can be considered for activating / deactivating the cell DTX / DRX mode.

[0087] The cell DTX mode and the cell DRX mode may be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). The cell DTX / DRX may also be configured and operated together. At least the following parameters may be configured for each cell DTX / DRX configuration: periodicity, start slot / offset, on duration. Support for multiple cell DTX / DRX configurations may be considered as well.

[0088] It may be beneficial to coordinate UE DRX with cell DTX and DRX coordination among multiple UEs.

[0089] Furthermore, it may be beneficial to design that the cell DTX / DRX mechanism should be designed so that the impact on legacy UEs is minimized.

[0090] Regarding configuration and signaling aspects, for example, 3GPP TR38.864 V18.0.0(2022-12) describes that the network can configure cell DTX and cell DRX through RRC signaling 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.

[0091] At least parameters such as periodicity, start slot / offset, and on-duration may be configured for each cell DTX / DRX configuration. While these parameters enable basic functionality of cell DTX / DRX, they do not specify a policy for extending the cell DTX and cell DRX on-duration time if needed to accommodate possible additional transmissions on the DL and UL, respectively. In the absence of such a policy, adhering to nominal on-duration and off-duration times may lead to an inability to maintain responsive traffic patterns or meet relevant QoS / QoE requirements for individual UEs. Therefore, it may be observed that a mechanism for extending the cell DTX and cell DRX on-duration time may help maintain responsive traffic patterns and meet relevant QoS / QoE requirements for individual UEs. Furthermore, there may be a need for cell DTX and cell DRX inactivity timers, which would enable energy savings on the network side.

[0092] In view of the rough cell DTX / DRX parameters as captured for example in 3GPP TR38.864 V18.0.0 and the above-described needs for cell DTX and cell DRX inactivity timers, the following set 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 also be considered. For cell DRX: cell drxPeriodicity, cell drxStartOffset, cell drxOnDurationTimer, and cell drxInactivityTimer. Other parameters may also be considered.

[0093] As for how to activate / deactivate cell DTX / DRX, 3GPP TR38.864 V18.0.0 proposed that cell DTX / DRX mode can be activated / deactivated via dynamic L1 / L2 signaling and UE-specific RRC signaling.

[0094] Therefore, given that there may be different ways to activate / deactivate cell DTX / DRX, it may be necessary to make the UE aware of how the NW intends to activate / deactivate the provided cell DTX / DRX RRC configuration. The latter way of activating cell DTX / DRX (i.e., using RRC signaling) implies that cell DTX / DRX can be realized using RRC without dynamic signaling, and our opinion is that this is the simplest way to support cell DTX / DRX (e.g., similar to UE C-DRX) that should be guaranteed and prioritized by RAN2. For example, the NW can use the cell dtxStartOffset and cell drxStartOffset parameters to easily indicate to the UE the time at which cell DTX and cell DRX will be activated, respectively (i.e., the UE should not expect cell DTX / DRX activation via L1 / L2 signaling). Alternatively, new fields in the cell DTX and cell DRX RRC configuration can be used for the same purpose.

[0095] Therefore, it may be necessary to further define how to enable full functionality of cell DTX and cell DRX features based on the received RRC configuration. Furthermore, it may be beneficial to introduce lower layer signaling (e.g., dynamic L1 / L2 signaling) as cell DTX and cell DRX enhancements.

[0096] Regarding the coexistence of cell DTX / DRX and UE C-DRX, one of the aspects that needs to be addressed is how the cell DTX / DRX mechanism and the UE C-DRX mechanism interact with each other when both are configured simultaneously in the UE. For example, a solution in which the UE C-DRX active period dominates the cell DTX inactive period (i.e., the UE C-DRX active period extends the cell DTX inactive period) may be disadvantageous in terms of network energy saving. When specifying how the UE C-DRX mechanism and the cell DTX / DRX mechanism interact with each other when configured simultaneously, a solution that maximizes the opportunity for network sleep may be preferable.

[0097] Therefore, the following observations can be made. - The cell DTX / DRX mechanism should be designed to minimize the impact on legacy UEs. Since it is possible to configure cell DTX and cell DRX separately, two sets of RRC parameters may need to be specified for configuring cell DTX and cell DRX respectively. A mechanism for extending the Cell DTX and Cell DRX on duration may be introduced to maintain responsive traffic patterns and 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 met for all UEs in the cell. The inactivity timer approach used for UE C-DRX may not be suitable for cell DTX / DRX context, as this approach may lead to unnecessary energy consumption on the network side and on the UE side. When specifying how the UE C-DRX mechanism and the cell DTX / DRX mechanism interact with each other when configured simultaneously, a solution that maximizes the opportunities for network sleep while taking UE power consumption into account may be preferable. - If both UE C-DRX and cell DTX are configured in a UE at the same time, cell DTX may overwrite UE C-DRX. This may imply that the UE C-DRX active period remains intact during the cell DTX active period and / or that the UE C-DRX active period is cancelled during the cell DTX inactive period (i.e. the UE should not expect to transmit on the DL unless instructed otherwise by the network).

[0098] 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of FIG. 3, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be as described with reference to FIGS. 3 and 4. In an optional first step of the method, the network node 16 receives user data from the WD 22 (block S128), in accordance with the teachings of embodiments described throughout this disclosure. 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 a transmission initiated by the network node 16 (block S132).

[0099] 9 is a flowchart of an example process in network node 16, in accordance with some embodiments of the present disclosure. One or more blocks described herein may be implemented by one or more elements of network node 16, such as by one or more of processing circuitry 68 (including intermittent unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured to set a connected mode discontinuous reception (C-DRX) onDuration for wireless device 22 (block S134) as described herein. Network node 16 is configured to communicate with wireless device 22 in C-DRX based on a obtained onDuration that is based on the set C-DRX onDuration for wireless device 22 and the cell DTX onDuration as described herein (block S136).

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

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

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

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

[0104] According to one or more embodiments, the resulting onDuration is set to at least partially overlap the cell DTX onDuration.

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

[0106] According to one or more embodiments, the C-DRX onDuration for the wireless device is one of having a shorter time period than the cell DTX onDuration and having a longer time period than the cell DTX onDuration.

[0107] According to one or more embodiments, the C-DRX inactivity timer is used to extend the resulting onDuration within the cell DTX onDuration.

[0108] According to one or more embodiments, the cell DTX inactivity timer is used to extend the resulting onDuration outside of the cell DTX onDuration.

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

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

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

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

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

[0114] According to one or more embodiments, the resulting onDuration is set to at least partially overlap the cell DTX onDuration.

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

[0116] According to one or more embodiments, the C-DRX onDuration for the wireless device 22 is one of having a shorter time period than the cell DTX onDuration and having a longer time period than the cell DTX onDuration.

[0117] According to one or more embodiments, the C-DRX inactivity timer is used to extend the resulting onDuration within the cell DTX onDuration.

[0118] According to one or more embodiments, the cell DTX inactivity timer is used to extend the resulting onDuration outside of the cell DTX onDuration.

[0119] Having described the general process flow of the configurations of the present disclosure and provided example hardware and software configurations for implementing the processes and functionality of the present disclosure, the following sections provide configuration details and examples for wireless device connected mode discontinuous reception (C-DRX) during cell discontinuous transmission (DTX) and / or discontinuous reception (DRX).

[0120] 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 the 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 the DRX unit 34, processor 86, processing circuitry 84, radio interface 82, etc.

[0121] Figure 11 is a diagram of possible combinations of wireless device 22C-DRX active time and cell DTX active time, as defined by the C-DRX onDurationtimer and the cell DTX onDurationtimer, respectively, as well as examples of possible resulting active times defined by taking into account both the active times specified by both the wireless device 22C-DRX setting and the cell DTX setting.

[0122] The different cases shown in Figure 11 are explained as follows. Case a: The wireless device 22C-DRX active time and the cell DTX active time partially overlap, and the wireless device 22C-DRX active time starts earlier than the cell DTX active period. Case b: The wireless device 22C-DRX active time is a proper subset of the cell DTX active time. Case c: The wireless device 22C-DRX active time and the cell DTX active time partially overlap, and the cell DTX active time starts earlier than the wireless device 22C-DRX active time. Case d: The cell DTX active time is a proper subset of the wireless device 22C-DRX active time. Case e: The wireless device 22C-DRX active period and the cell DTX active period do not intersect, and the wireless device 22C-DRX active period is shorter than the cell DTX active period. Case f: The wireless device 22C-DRX active period and the cell DTX active period do not intersect, and the wireless device 22C-DRX active period is longer than the cell DTX active period.

[0123] FIG. 12 is a diagram of an example of a possible extension of the active time defined by the inactivity timer of the C-DRX and the inactivity timer of the cell DTX.

[0124] The different cases shown in FIG. 12 are explained as follows. Case A: The inactivity timer of the C-DRX is used to extend the active period within the active time specified by the onDuration timer of the cell DTX. Case B: Cell DTX's inactivity timer is used to extend the active period outside of the active time specified by Cell DTX's onDuration timer.

[0125] Some examples A method in a wireless device 22: 1. The wireless device 22 receives only one of network node DTRX or cell DTX / DRX, or DTX or DRX configuration from the network node 16 while in an RRC connected or other state, for example through higher layer signaling such as a system information (SI) broadcast, or dedicated signaling such as an RRC configuration. C-DRX is further configured in the wireless device 22. 2. The wireless device 22 starts the C-DRX onDuration timer (or the cell DTRX onDuration timer if configured to use it instead of the C-DRX onDuration) if that onDuration timer can be started while the cell DTX / DRX is in the active state or if that portion of the onDuration timer falls within the cell DTX / DRX active time, Example 1. In other cases, the wireless device 22 does not start the onDuration timer. Examples of possible combinations of the wireless device 22 C-DRX active time and the cell DTX active time, as defined by the C-DRX onDuration timer and the cell DTX onDuration timer, respectively, are shown in FIG. 11. 3. Any one of the above examples in which the wireless device 22 restarts the C-DRX DRX inactivity timer (or the cell DTRX inactivity timer if configured to use it instead of the C-DRX inactivity timer) if it can be started while the cell DTX / DRX is in the active state. In other cases, the wireless device 22 does not (re)start the DRX inactivity timer. Examples of possible extensions of the active times defined by the C-DRX inactivity timer and the cell DTX inactivity timer, respectively, are shown in Figure 12. 4. Any one of the above examples, where the wireless device 22 is configured to stop the duration timer or the DRX inactivity timer, or any other active time related timer for C-DRX, when the cell (with DTX and / or DRX) enters an inactivity period. While this may be a general rule, the wireless device 22 may be configured differently by the network node 16, if necessary, by providing an overriding configuration. Possible alternatives / options / exceptions for the stopping criteria: a. Stop the timer when both cell DTX and DRX enter the inactive period (i.e. do not stop when one of them is active) b. Stop the timer at least when the cell DTX enters the inactive period c. If the wireless device is configured to complete the conduit duration timer or DRX inactivity timer duration regardless of the cell DTX / DRX state (see below), the timer is not stopped. Possible top priority settings: d. The wireless device 22 completes the conduit duration timer or DRX inactivity timer duration regardless of the cell DTX / DRX state [network node 16 may itself reserve the option to cease cell DTX in case of "important" data] i. This may apply only to some types of DCI, e.g., the inactivity timer is completed only for "real" new data [not BSR] (e.g., new transmissions), or for some 5QI settings or traffic types. e. The wireless device 22 ignores the cell DTX state and always completes the timer [effectively a per-wireless device 22 deactivation of cell DTRX that requires no system signaling and does not affect other wireless devices 22 that continue to assume the globally configured cell DTRX]. 5. Any of the above examples, including any timers where the active state of the cell DTX / DRX indicates that a transmission is expected from the cell or that the cell is listening for UL transmissions, e.g., a conduit timer or inactivity timer associated with the cell DTX / DRX. 6. Any of the above examples in which the wireless device 22 may transmit HARQ feedback after the cell DRX active time has expired if a DL transmission was received during the active time, and / or monitor for DL ​​retransmissions after the cell DTX active time has expired if a recent HARQ NACK was transmitted (e.g., this may be a general rule or may be set individually for each wireless device 22). a. The wireless device 22 may transmit HARQ feedback after the cell DRX active time has expired if a DL transmission was received during the active time, but only if fewer HARQ retransmissions than the maximum configured (e.g., pre-configured via RRC) number have occurred for the current DL message. b. The wireless device 22 may monitor DL ​​retransmissions after the cell DTX active time has expired if a recent HARQ NACK was transmitted, but only if there have been fewer HARQ retransmissions than the maximum configured (e.g., pre-configured via RRC) number for the current UL message. The duration of the HARQ transmission allowance window and the duration of the DL retransmission monitoring may be configured by the network node 16, and whether this rule should apply to the current transmission may be indicated in the scheduling DCI. c. An offset is defined that extends or delays the start of the HARQ transmission permission window. The offset may correspond to or be relative to the cell inactive time. It may also be any configured value. When this offset is applied, both the wireless device 22 and the network node 16 wait during the inactive time and, for example, do not flush the HARQ buffers. After the cell becomes available again, the wireless device 22 (or network node 16) may continue to terminate its transmission. In one embodiment, several offsets are defined and configured for the wireless device 22, and then a DCI or group DCI from the network node 16 instructs the wireless device 22 which offset to apply. It may be a field in the DCI scheduling DL or UL. 7. Any of the above examples in which wireless device 22 may be configured to monitor downlink messages (e.g., DCI on a PDCCH with a CRC scrambled by a C-RNTI) in slots with one or more SSB transmissions. 8. Any of the above examples in which wireless device 22 may monitor for 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 22C-DRX) is running. a. The wireless device 22 may transmit on the uplink after the cell DRX active time expires if a UL transmission was scheduled for the wireless device 22 according to the downlink control message. 9. Any of the above examples, in which the wireless devices 22 may be configured to transmit scheduling requests (SRs) according to their configured SR opportunity schedule during all or part of the cell DRX inactive time, e.g., the network / network node 16 may enable SR transmissions for a subset of important wireless devices 22 (e.g., for a subset of multiple wireless devices 22) while they are in connected mode without reconfiguring cell DRX for all wireless devices 22. a. Any of the above examples in which the wireless device 22 may be configured / enabled to monitor downlink messages during cell DTX inactive time if the wireless device 22 has sent a scheduling request and it is pending. b. Any of the above examples in which the wireless device 22 may be configured / enabled to transmit on the uplink (e.g., data transmission on the Physical Uplink Shared Channel (PUSCH)) in accordance with a detected downlink message even if the associated uplink transmission opportunity overlaps with a cell DRX inactive time. c. Any of the above examples in which the wireless device 22 may be configured / enabled to transmit on the uplink (e.g., data transmission on a PUSCH) in accordance with a detected downlink message even if the associated uplink transmission opportunity overlaps with a cell DRX inactive time. d. Any of the above examples in which the wireless device 22 may be configured / enabled to transmit on the uplink (e.g., data transmission on a PUSCH) in accordance with a detected downlink message even if the associated uplink transmission opportunity overlaps with a cell DRX inactive time. e. Any of the above examples in which the wireless device 22 may be configured / enabled to transmit a scheduling request multiplexed with the HARQ-ACK on the uplink (e.g., SR+HARQ-ACK on the PUCCH) if the wireless device 22 is configured to transmit a HARQ-ACK on the PUCCH during cell DRX inactive time. f. Any of the above examples in which the wireless device 22 may be configured / enabled to transmit SRS (e.g., SR+HARQ-ACK on PUCCH) in a slot / symbol on the uplink if the wireless device 22 is scheduled to transmit PUCCH / HARQ-ACK in a slot / symbol during cell DRX inactive time. g. Any of the above examples in which the wireless device 22 may be configured to be able to request or indicate the wireless device 22's preferences for any of the above specific settings or other settings described herein, including wireless device assistance information regarding the wireless device 22's preferences for specific settings of cell DTX / DRX parameters. 10. Any of the above examples where the wireless device 22 is configured with a serving cell that has cell DTX / DRX configured more than once. 11. Any of the above examples where this behavior is applicable to cell groups, i.e., MCG only, SCG only, or both MCG and SCG. a. Only the wireless device DRX for the corresponding cell group will be affected as described above according to the cell DTX / DRX if there are any cells in that cell group with DTX / DRX configured.

[0126] Therefore, one or more embodiments described herein advantageously provide a mechanism by which cell DTX / DRX and wireless device C-DRX or DRX can coexist, thus providing energy savings to both the wireless device and the network node.

[0127] The wireless device 22 and the network node 16 may be coordinated during the above operations. For example, the network node may send a DL retransmission after the cell DTX active time expires if a recent HARQ NACK was sent by the WD 22. Furthermore, if the network node 16 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 expires.

[0128] 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 may be implemented in a WD 22, which may be configured to communicate with 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 the processing circuitry 84 (including the DRX unit 34), the processor 86, and / or the radio interface 82. C-DRX may be configured in the WD.

[0129] In the method of Figure 13, the WD receives a cell DTX configuration from a network node (block 140). The cell DTX configuration specifies 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 an RRC connected state. The WD may receive the cell DTX configuration through an RRC configuration or through an SI broadcast.

[0130] Furthermore, the WD sends a HARQ NACK for the DL radio transmission from the network node (block 142). In response to the HARQ NACK, the WD monitors for DL ​​retransmission(s) from the network node after the cell DTX active time expires (block 144). The WD may perform the monitoring of DL retransmissions after the cell DTX active time expires only if fewer HARQ retransmissions than a maximum number have been performed for the DL radio transmission. The maximum number may be configured by the RRC. The duration of the HARQ transmission allowance window and the duration of the monitoring of DL retransmissions may be configured by the network node, for example, by the RRC. A rule by which the WD performs the monitoring of DL retransmissions after the cell DTX active time is configured individually for the WD. Furthermore, the rule by which the WD performs the monitoring of DL retransmissions after the cell DTX active time and / or whether the rule should be applied may be indicated in the scheduling DCI for the DL radio transmission.

[0131] 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 may be implemented in network node 16, which may be configured to communicate with 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 intermittent unit 32), processor 70, radio interface 62, and / or communication interface 60. C-DRX may be configured in the WD.

[0132] In the method of Figure 14, the network node provides the WD with its cell DTX configuration (block 150). The cell DTX configuration specifies a cell DTX active time. The network node may provide the cell DTX configuration while the WD is in an RRC connected state. The network node may provide the cell DTX configuration through an RRC configuration or through an SI broadcast.

[0133] Additionally, the network node may send a DL wireless transmission to the WD (block 152).

[0134] Additionally, the network node receives from the WD a HARQ NACK for the DL radio transmission from the network node, for example for the DL radio transmission of block 154 .

[0135] In response to the HARQ NACK, the network node sends a DL retransmission to the WD after the cell DTX active time has expired (block 156). In some scenarios, the network node sends a DL retransmission after the cell DTX active time has expired only if fewer than a maximum number of HARQ retransmissions have been made for the DL radio transmission. The maximum number may be configured by RRC. The duration of the HARQ transmission grant window and the duration of said monitoring for DL ​​retransmissions are configured by the network node.

[0136] A rule implementing the WD's monitoring of DL retransmissions after a cell DTX active time is configured individually for the WD. Furthermore, the rule implementing the WD's monitoring of DL retransmissions after a cell DTX active time and / or whether the rule should be applied may be indicated in a scheduling DCI for DL ​​radio transmissions.

[0137] 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 may be implemented in a WD 22, which may be configured to communicate with 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 the processing circuitry 84 (including the DRX unit 34), the processor 86, and / or the radio interface 82. C-DRX may be configured in the WD.

[0138] In the method of Figure 15, the WD receives a cell DRX configuration from a network node (block 160). The cell DRX configuration specifies 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 an RRC connected state. The WD may receive the cell DRX configuration through an RRC configuration or through an SI broadcast.

[0139] Additionally, the WD may receive DL wireless transmissions from the network node (block 162).

[0140] Furthermore, the WD sends HARQ feedback for a DL radio transmission from the network node, e.g., for the DL radio transmission of block 162 (block 164). The WD transmits HARQ feedback after the cell DRX active time has expired if the DL radio transmission was received during the cell DRX active time. The WD may transmit HARQ feedback after the cell DRX active time has expired only if fewer HARQ retransmissions than a maximum number have been performed for the DL radio transmission. The maximum number may be configured by the RRC. A rule by which the WD implements the transmission of HARQ feedback after the cell DRX active time may be configured individually for the WD, e.g., by the RRC. Furthermore, the rule by which the WD implements the transmission of HARQ feedback after the cell DRX active time and / or whether the rule should be applied may be indicated in the scheduling DCI for the DL radio transmission.

[0141] 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 may be implemented in network node 16, which may be configured to communicate with 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 intermittent unit 32), processor 70, radio interface 62, and / or communication interface 60. C-DRX may be configured in the WD.

[0142] In the method of Figure 16, the network node provides the WD with its cell DRX configuration (block 170). The cell DRX configuration specifies a cell DRX active time. The network node may provide the cell DRX configuration while the WD is in an RRC connected state. The network node may provide the cell DRX configuration through an RRC configuration or through an SI broadcast.

[0143] Additionally, the network node may send a DL wireless transmission to the WD (block 172).

[0144] Furthermore, the network node receives from the WD HARQ feedback for a DL radio transmission from the network node, e.g., for the DL radio transmission of block 174. The network node expects HARQ feedback after the cell DRX active time has expired if the DL radio transmission was received during the cell DRX active time. The network node may expect HARQ feedback after the cell DRX active time has expired only if fewer HARQ retransmissions than a maximum number have been performed for the DL radio transmission. The maximum number may be configured by RRC. A rule for the WD to transmit HARQ feedback after the cell DRX active time may be configured individually for the WD, e.g., by RRC. Furthermore, the rule for the WD to transmit HARQ feedback after the cell DRX active time and / or whether the rule should apply may be indicated in the scheduling DCI for the DL radio transmission.

[0145] It should be noted that the methods of Figures 13-16 may be combined in various ways. For example, if a network node is configured with both cell DTX and cell DRX, a WD may implement both the method of Figure 13 and the method of Figure 15. Furthermore, the method of Figure 13 and the method of Figure 14 may be combined in a system including a WD operating according to the method of Figure 13 and a network node operating according to the method of Figure 14. Similarly, the method of Figure 15 and the method of Figure 16 may be combined in a system including a WD operating according to the method of Figure 15 and a network node operating according to the method of Figure 16.

[0146] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as a method, a data processing system, a computer program product, and / or a computer storage medium 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 of which may be generally referred to herein as a “circuit” or “module.” Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the present 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 a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0147] Some embodiments have been 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 can be provided to a processor of a general-purpose computer (to thereby create a special-purpose computer), a special-purpose computer, or other programmable data processing apparatus to create a machine, such that the instructions, executing via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0148] 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 create an article of manufacture that includes instruction means that implement the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0149] Computer program instructions may also be loaded into 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 create a computer-implemented process, whereby the instructions executing on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0150] It should 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 on the functions / acts involved. While some of the figures include arrows on communication paths to indicate the primary direction of communication, it should be understood that communication may occur in the opposite direction to that of the illustrated arrows.

[0151] Computer program code for performing operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java, or C++. However, computer program code for performing operations of the present 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, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or wide area network (WAN), or the connection may be to an external computer (e.g., through the Internet using an Internet Service Provider).

[0152] Many different embodiments have been disclosed herein with reference to the above description and drawings. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and unclear. Accordingly, all embodiments may be combined in any manner and / or combination, and the specification, including the drawings, should be construed as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, and of all combinations and subcombinations of the modes and processes for making and using them, and is intended to support any claim to any such combination or subcombination.

[0153] It will be appreciated by those skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described hereinabove. Further, unless otherwise noted above, it should be noted that all of the accompanying drawings are not to scale. Various modifications and variations are possible in light of the above teachings.

[0154] Further embodiments are described below. Embodiment A1. A network node configured to communicate with a wireless device, wherein a cell discontinuous transmission (DTX) onDuration is configured in the network node, and the network node: Configuring a connected mode discontinuous reception (C-DRX) onDuration on the wireless device; communicating with the wireless device in C-DRX based on a determined onDuration that is based on a configured C-DRX onDuration for the wireless device and a cell DTX onDuration; a network node configured to perform the above and / or comprising a wireless interface configured to perform the above and / or comprising processing circuitry configured to perform the above. Embodiment A2. The network node of embodiment A1, 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 A1, wherein the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration. Embodiment A4. The network node of embodiment A1, 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 A1, wherein the cell DTX onDuration is a subset of the C-DRX onDuration for the wireless device. Embodiment A6. A network node according to any one of embodiments A1 to A5, wherein the obtained onDuration is configured to at least partially overlap the cell DTX onDuration. Embodiment A7. The network node of embodiment A1, wherein the C-DRX onDuration for the wireless device does not overlap with the cell DTX onDuration. Embodiment A8. The C-DRX onDuration for a wireless device comprises: has a time duration shorter than the cell DTX onDuration, and Cell DTX onDuration has a longer time period, The network node of embodiment A7, wherein the network node is one of: Embodiment A9. The network node of any one of embodiments A1 to A8, wherein a C-DRX inactivity timer is used to extend the resulting onDuration within the cell DTX onDuration. Embodiment A10. The network node of embodiment A10, wherein an inactivity timer of the cell DTX is used to extend the obtained onDuration outside of the cell DTX onDuration. Embodiment B1. A method implemented by a network node configured to communicate with a wireless device, the method comprising: configuring the network node with a cell discontinuous transmission (DTX) onDuration; Configuring a connected mode discontinuous reception (C-DRX) onDuration on the wireless device; communicating with the wireless device in C-DRX based on a determined onDuration that is based on a configured C-DRX onDuration for the wireless device and a cell DTX onDuration; A method comprising: Embodiment B2. The method of embodiment B1, in which the C-DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration. Embodiment B3. The method of embodiment B1, in which the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration. Embodiment B4. The method of embodiment B1, in which the cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device. Embodiment B5. The method of embodiment B1, in which 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 to B5, wherein the resulting onDuration is set to at least partially overlap the cell DTX onDuration. Embodiment B7. The method of embodiment B1, wherein the C-DRX onDuration for the wireless device does not overlap with the cell DTX onDuration. Embodiment B8. The C-DRX onDuration for a wireless device comprises: has a time duration shorter than the cell DTX onDuration, and Cell DTX onDuration has a longer time period, The method of embodiment B7, wherein the method is one of: Embodiment B9. The method of any one of embodiments B1 to B8, wherein a C-DRX inactivity timer is used to extend the resulting onDuration within the cell DTX onDuration. Embodiment B10. The method of embodiment B9, wherein an inactivity timer of the cell DTX is used to extend the resulting onDuration outside of the cell DTX onDuration. Embodiment C1. A non-transitory computer-readable medium storing program instructions that, when executed by a processor, configure the processor to implement a method according to any one of embodiments B1 to B10. Embodiment D1. A wireless device (WD) configured to communicate with a network node, the wireless device comprising: and operating in connected mode discontinuous reception (C-DRX) according to a derived onDuration based on a configured C-DRX onDuration and a cell discontinuous transmission (DTX) onDuration for the wireless device. A wireless device (WD) configured to perform the above and / or comprising a wireless interface configured to perform the above and / or comprising processing circuitry configured to perform the above. Embodiment D2. The WD of embodiment D1, wherein the C-DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration. Embodiment D3. The WD of embodiment D1, wherein the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration. Embodiment D4. The WD of embodiment D1, wherein the cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device. Embodiment D5. The WD of embodiment D1, 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 D1 to D5, wherein the resulting onDuration is configured to at least partially overlap the cell DTX onDuration. Embodiment D7. The WD of embodiment D1, wherein the C-DRX onDuration for the wireless device does not overlap with the cell DTX onDuration. Embodiment D8. The C-DRX onDuration for a wireless device comprises: has a time duration shorter than the cell DTX onDuration, and Cell DTX onDuration has a longer time period, The WD according to embodiment D7, wherein the WD is one of: Embodiment D9. The WD of any one of embodiments D1 to D8, wherein a C-DRX inactivity timer is used to extend the resulting onDuration within the cell DTX onDuration. Embodiment D10. The WD of embodiment D9, wherein an inactivity timer of the cell DTX is used to extend the resulting onDuration outside of the cell DTX onDuration. Embodiment E1. A method implemented by a wireless device (WD) configured to communicate with a network node, the method comprising: and operating in connected mode discontinuous reception (C-DRX) according to a derived onDuration based on a configured C-DRX onDuration and a cell discontinuous transmission (DTX) onDuration for the wireless device. A method comprising: Embodiment E2. The method of embodiment E1, in which the C-DRX onDuration for the wireless device starts earlier in time than the cell DTX onDuration. Embodiment E3. The method of embodiment E1, in which the C-DRX onDuration for the wireless device is a subset of the cell DTX onDuration. Embodiment E4. The method of embodiment E1, in which the cell DTX onDuration starts earlier in time than the C-DRX onDuration for the wireless device. Embodiment E5. The method of embodiment E1, 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 to E5, wherein the resulting onDuration is set to at least partially overlap the cell DTX onDuration. Embodiment E7. The method of embodiment E1, wherein the C-DRX onDuration for the wireless device does not overlap with the cell DTX onDuration. Embodiment E8. The C-DRX onDuration for a wireless device comprises: has a time duration shorter than the cell DTX onDuration, and Cell DTX onDuration has a longer time period, The method of embodiment E7, wherein the method is one of: Embodiment E9. The method of any one of embodiments E1 to E8, wherein a C-DRX inactivity timer is used to extend the resulting onDuration within the cell DTX onDuration. Embodiment E10. The method of embodiment E9, wherein an inactivity timer of the cell DTX is used to extend the resulting onDuration outside of the cell DTX onDuration. Embodiment F1. 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 E1 to E10.

Claims

1. 1. A method implemented by a wireless device (WD) (22) configured to communicate with a network node (16), said method comprising: - said WD (22) receiving a cell discontinuous transmission (cell DTX) configuration of said network node (16), said 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) radio transmission from the network node (16); - in response to said HARQ NACK, said WD (22) monitors DL retransmissions from said network node (16) after said cell DTX active time has expired; A method comprising:

2. The WD (22) is set to connected mode discontinuous reception (C-DRX), The method of claim 1.

3. The WD (22) performs the monitoring of DL retransmissions after the cell DTX active time has expired only if fewer than a maximum number of HARQ retransmissions have been performed for the DL radio transmission. The method according to claim 1 or 2.

4. the duration of a HARQ transmission grant window and the duration of said monitoring for DL ​​retransmissions are set by said network node (16); 4. The method according to any one of claims 1 to 3.

5. A rule for the WD (22) to monitor DL ​​retransmission after the cell DTX active time is individually set for the WD (22); 5. The method according to any one of claims 1 to 4.

6. A rule for the WD (22) to monitor DL ​​retransmissions after the cell DTX is active and / or whether the rule should be applied is indicated in a scheduling DL control information (DCI) of the DL radio transmission.

6. The method according to any one of claims 1 to 5.

7. The WD (22) receives the cell DTX setting from the network node (16).

7. The method according to any one of claims 1 to 6.

8. the WD (22) receives the cell DTX configuration while in a Radio Resource Control (RRC) connected state; The method of claim 7.

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

10. The WD (22) receives the cell DTX setting through a system information (SI) broadcast.

10. The method according to any one of claims 7 to 9.

11. 1. A method implemented by a wireless device (WD) (22) configured to communicate with a network node (16), said method comprising: - said WD (22) receiving a cell discontinuous reception (cell DRX) configuration of said network node (16), said cell DRX configuration defining a cell DRX active time; said WD (22) receiving a downlink (DL) radio transmission from said network node (16); the WD (22) transmitting Hybrid Automatic Repeat Request (HARQ) feedback for the DL radio transmission; Including, The WD (22) transmits the HARQ feedback after the cell DRX active time ends if the DL radio transmission is received during the cell DRX active time.

12. The WD (22) is set to connected mode discontinuous reception (C-DRX), The method of claim 11.

13. the WD (22) transmits the HARQ feedback after the cell DRX active time expires only if fewer than a maximum number of HARQ retransmissions have been performed for the DL radio transmission.

13. The method of claim 11 or 12.

14. A rule for the WD (22) to transmit the HARQ feedback after the cell DRX active time is individually set for the WD (22); 14. The method according to any one of claims 11 to 13.

15. A rule for the WD (22) to transmit the HARQ feedback after the cell DRX active time and / or whether the rule should be applied is indicated in scheduling DL control information (DCI) of the DL radio transmission.

15. The method according to any one of claims 11 to 14.

16. The WD (22) receives the cell DRX configuration from the network node (16).

16. The method according to any one of claims 11 to 15.

17. The WD (22) receives the cell DRX configuration while in a Radio Resource Control (RRC) connected state.

17. The method of claim 16.

18. The WD (22) receives the cell DRX configuration through an RRC configuration; 18. The method of claim 16 or 17.

19. The WD (22) receives a cell DTX setting through a system information (SI) broadcast.

19. The method of any one of claims 16 to 18.

20. 1. A method implemented by a network node (16) configured to communicate with a wireless device (22), the method comprising: - the network node (16) providing to the WD (22) a cell discontinuous transmission (cell DTX) configuration of the network node (16), the cell DTX configuration defining a cell DTX active time; - said network node (16) receiving from said WD (22) a Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgement (NACK) for a Downlink (DL) radio transmission from said network node (16); - in response to said HARQ NACK, said network node (16) sends a DL retransmission to said WD (22) after said cell DTX active time has expired; A method comprising:

21. The WD (22) is set to connected mode discontinuous reception (C-DRX), 21. The method of claim 20.

22. the WD (22) sends the DL retransmission after the cell DTX active time expires only if fewer than a maximum number of HARQ retransmissions have been performed for the DL radio transmission.

22. The method of claim 20 or 21.

23. the duration of the HARQ transmission grant window and the duration of monitoring for DL ​​retransmissions are set by the network node (16); 23. The method of any one of claims 20 to 22.

24. A rule for the WD (22) to monitor DL ​​retransmission after the cell DTX active time is individually set for the WD (22); 24. The method of any one of claims 20 to 23.

25. A rule for the WD (22) to monitor DL ​​retransmissions after the cell DTX is active and / or whether the rule should be applied is indicated in a scheduling DL control information (DCI) of the DL radio transmission.

25. The method of any one of claims 20 to 24.

26. The network node (16) provides the cell DTX configuration while the WD (22) is in a Radio Resource Control (RRC) connected state.

26. The method of any one of claims 20 to 25.

27. the network node (16) providing the cell DTX configuration through an RRC configuration; 27. The method of any one of claims 20 or 26.

28. the network node (16) providing the cell DTX setting through a system information (SI) broadcast; 28. The method of any one of claims 20 to 27.

29. 1. A method implemented by a network node (16) configured to communicate with a wireless device (WD) (22), the method comprising: - the network node providing to the WD (22) a cell DRX configuration of the network node (16), the cell DRX configuration defining a cell DRX active time; - said network node (16) sending a downlink (DL) radio transmission to said WD (22); - said network node (16) receiving Hybrid Automatic Repeat Request (HARQ) feedback for said DL radio transmission; Including, The network node (16) anticipates 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 WD (22) is set to connected mode discontinuous reception (C-DRX), 30. The method of claim 29.

31. the network node (16) expects the HARQ feedback after the cell DRX active time has expired only if fewer than a maximum number of HARQ retransmissions have been performed for the DL radio transmission.

31. The method of claim 29 or 30.

32. A rule for the WD (22) to transmit the HARQ feedback after the cell DRX active time is individually set for the WD (22); 32. The method of any one of claims 29 to 31.

33. A rule for the WD (22) to transmit 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 radio transmission.

33. The method of any one of claims 29 to 32.

34. The network node (22) provides the cell DRX configuration while the WD (22) is in a Radio Resource Control (RRC) connected state.

34. The method of any one of claims 29 to 33.

35. the network node (16) providing the cell DRX configuration through an RRC configuration; 35. The method of claim 29 or 34.

36. the network node (16) providing the cell DTX setting through a system information (SI) broadcast; 19. The method of any one of claims 16 to 18.

37. A wireless device (WD) (22) configured to communicate with a network node (16), said WD (22) comprising: receiving a cell discontinuous transmission (cell DTX) configuration of said network node (16), said cell DTX configuration defining a cell DTX active time; - transmitting a Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgement (NACK) for a Downlink (DL) radio transmission from said network node (16); - in response to said HARQ NACK, monitoring DL retransmissions from said network node (16) after said cell DTX active time has expired; a wireless device (WD) (22) further configured to:

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

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

40. A wireless device (WD) (22) configured to communicate with a network node (16), said WD (22) comprising: receiving a cell discontinuous reception (cell DRX) configuration of said network node (16), said cell DRX configuration defining a cell DRX active time; receiving a downlink (DL) radio transmission from said network node (16); if the DL radio transmission was received during the cell DRX active time, transmitting Hybrid Automatic Repeat Request (HARQ) feedback for the DL radio transmission after the cell DRX active time has expired; a wireless device (WD) (22) further configured to:

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

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

43. A network node (16) configured to communicate with a wireless device (WD) (22), said network node (22) comprising: - providing said WD (22) with a cell DTX configuration of said network node (16), said cell DTX configuration defining a cell DTX active time; receiving from said WD (22) a Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgement (NACK) for a Downlink (DL) radio transmission from said network node (16); - in response to the HARQ NACK, sending a DL retransmission to the WD (22) after the cell DTX active time has expired; a network node (16) further configured to:

44. A network node (16) according to claim 43, configured to implement a method according to any one of claims 21 to 28.

45. a processing circuit (68); and a memory (72) storing program instructions that, when executed by the processing circuit (68), cause the network node (16) to perform a method according to any one of claims 20 to 28.

45. A network node (16) according to claim 43 or 44, comprising:

46. A network node (16) configured to communicate with a wireless device (WD) (22), said network node (22) comprising: - providing said WD (22) with a cell DRX configuration of said network node (16), said cell DRX configuration defining a cell DRX active time; - sending a downlink (DL) radio transmission to said WD (22); receiving Hybrid Automatic Repeat Request (HARQ) feedback for said DL radio transmission; and is further configured to The network node (16) is configured to expect the HARQ feedback after the cell DRX active time has ended if the DL transmission was transmitted during the cell DRX active time.

47. A network node (16) according to claim 43, configured to implement a method according to any one of claims 30 to 36.

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

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

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

Images