Method, device, and system for discontinuous data transmission and reception in a wireless network

Abstract

The present disclosure generally relates to methods, devices, and systems for discontinuous data transmission and reception in wireless networks. One method implemented by a wireless device is disclosed. The method may include receiving, from a network node, a first message comprising a first connection state discontinuous reception (DRX) configuration or an indicator indicating the first connection state DRX configuration, where the first connection state DRX configuration is assigned to a first target associated with a first service of the wireless device, the first target comprising one of the following: a data radio bearer (DRB), a logical channel, a semi-persistent scheduling (SPS), a configuration grant (CG), or a hybrid automatic repeat request (HARQ) process; and applying the first connection state DRX configuration to the first target.

Description

[Technical Field]

[0001] (Technical field) The present disclosure relates generally to wireless communications, and more particularly to methods, devices, and systems for discontinuous data transmission and discontinuous data reception in wireless networks. [Background technology]

[0002] (background) Controlling power consumption and reducing energy costs is important for developing and deploying wireless communication networks. Energy-saving techniques are important to achieve this goal. With the development of wireless communication technology, more and more services, applications, and various power-saving mechanisms are being added, thereby increasing the complexity of power control. It is important to have the ability to control the power consumption of various network elements, such as base stations and UEs, while still meeting performance requirements. Summary of the Invention [Means for solving the problem]

[0003] (overview) The present disclosure is directed to methods, devices, and systems for discontinuous data transmission and discontinuous data reception in wireless networks.

[0004] In some embodiments, a method implemented by a wireless device is disclosed. The method may include receiving, from a network node, a first message comprising a first connection state discontinuous reception (DRX) configuration or an indicator indicative of the first connection state DRX configuration, the first connection state DRX configuration being assigned to a first target associated with a first service of the wireless device, the first target comprising one of the following: a data radio bearer (DRB), a logical channel, a semi-persistent scheduling (SPS), a configuration grant (CG), or a hybrid automatic repeat request (HARQ) process; and applying the first connection state DRX configuration to the first target.

[0005] In some embodiments, a method implemented by a wireless device is disclosed. The method may include: transmitting, to a network node, an indicator indicating radio capabilities of the wireless device, the radio capabilities indicating whether the wireless device supports HARQ Mode B when a serving cell of the wireless device is a terrestrial network cell, wherein a HARQ round trip time (RTT) timer and a HARQ retransmission timer are not started in HARQ Mode B; and receiving, from the network node, a HARQ mode indicator instructing the wireless device to apply HARQ Mode B when the wireless device is within the terrestrial network cell.

[0006] In some embodiments, a method implemented by a wireless device is disclosed. The method may include receiving, from a network node, a first message indicating deactivation of a DRX HARQ round-trip time timer (drx-HARQ-RTT-Timer), the drx-HARQ-RTT-Timer applying to a target comprising one of the following: a data radio bearer (DRB), a logical channel, a semi-persistent scheduling (SPS), a configuration grant (CG), or a hybrid automatic repeat request (HARQ) process.

[0007] In some embodiments, a method implemented by a wireless device is disclosed. The method may include receiving, via a UE-specific message targeted to the wireless device, an indicator indicating whether discontinuous cell operation is activated in a cell, the discontinuous cell operation comprising at least one of discontinuous cell transmission (DTX) or discontinuous cell reception (DRX), and activating a configuration related to the discontinuous cell operation in response to the indicator indicating that discontinuous cell operation is activated in the cell.

[0008] In some embodiments, a method implemented by a network node is disclosed. The method may include transmitting, to a wireless device, a first message comprising a first connection state discontinuous reception (DRX) configuration or an indicator indicating the first connection state DRX configuration, the first connection state DRX configuration being assigned to a first target associated with a first service of the wireless device, the first target comprising one of the following: a data radio bearer (DRB), a logical channel, a semi-persistent scheduling (SPS), a configuration grant (CG), or a hybrid automatic repeat request (HARQ) process.

[0009] In some embodiments, a method implemented by a network node is disclosed that may include receiving, from a wireless device, an indicator indicating a radio capability of the wireless device, the radio capability indicating whether the wireless device supports HARQ Mode B when a serving cell of the wireless device is a terrestrial network cell, wherein in HARQ Mode B, a HARQ round trip time (RTT) timer and a HARQ retransmission timer are not started; and transmitting, to the wireless device served by the terrestrial network cell, a HARQ mode indicator that instructs the wireless device to apply HARQ Mode B.

[0010] In some embodiments, a method implemented by a network node is disclosed. The method may include transmitting, to a wireless device, a first message instructing the wireless device to deactivate a DRX HARQ round-trip time timer (drx-HARQ-RTT-Timer), the drx-HARQ-RTT-Timer being applied to a target of the wireless device, the target comprising one of the following: a data radio bearer (DRB), a logical channel, a semi-persistent scheduling (SPS), a configuration grant (CG), or a hybrid automatic repeat request (HARQ) process.

[0011] In some embodiments, a method is disclosed that is implemented by a network node. The method may include transmitting, via a UE-specific message targeted to a wireless device, an indicator that indicates whether discontinuous cell operation is activated in a cell of the network node, the discontinuous cell operation comprising at least one of discontinuous cell transmission (DTX) or discontinuous cell reception (DRX).

[0012] In some embodiments there is a wireless device or network node comprising a processor and a memory, the processor configured to read code from the memory and to implement any method described in any of the embodiments.

[0013] In some embodiments, a computer program product comprises computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to perform any of the methods described in any of the embodiments.

[0014] The above embodiments and other aspects and alternatives of their implementations are described in more detail in the drawings, description, and claims that follow. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 illustrates an exemplary wireless communication network.

[0016] [Figure 2] FIG. 2 illustrates an exemplary wireless network node.

[0017] [Figure 3] FIG. 3 illustrates an exemplary user equipment.

[0018] [Figure 4] 4a-4c show exemplary resource (DRB, LC, SPS, CG) to HARQ process mappings.

[0019] [Figure 5] FIG. 5 shows a common (fits all) connected state DRX configuration that applies to all HARQ services under a cell or DRB group.

[0020] [Figure 6-1] 6a-6f show exemplary connection state DRX configurations specific to or targeted to a resource or HARQ process. [Figure 6-2] 6a-6f show exemplary connection state DRX configurations specific to or targeted to a resource or HARQ process.

[0021] [Figure 7] FIG. 7 shows an example message flow for configuring the connected state DRX configuration for a particular service of a UE.

[0022] [Figure 8] FIG. 8 shows an example message flow for configuring a HARQ mode for a UE according to the UE capability for supporting the HARQ mode mechanism in the TN network.

[0023] [Figure 9] FIG. 9 illustrates a scenario in which the UE misses cell DTX and / or cell DRX activation.

[0024] [Figure 10] FIG. 10 shows an example message flow for activating cell DTX and / or cell DRX in the case of a UE handover or a UE RRC connection setup.

[0025] [Figure 11] FIG. 11 shows an example of a combined cell DTX and cell DRX configuration sent to a UE with a cell DTX and / or cell DRX activation indicator.

[0026] [Figure 12] FIG. 12 shows another example of separate cell DTX and cell DRX configurations sent to a UE with a cell DTX and / or cell DRX activation indicator. DETAILED DESCRIPTION OF THE INVENTION

[0027] (Detailed explanation) (Wireless communication network) FIG. 1 illustrates an exemplary wireless communication network 100 including a core network 110 and a wireless access network (RAN) 120. The core network 110 further includes at least one mobility management entity (MME) 112 and / or at least one access and mobility management function (AMF). Other functions that may be included in the core network 110 are not shown in FIG. 1. The RAN 120 further includes multiple base stations, e.g., base stations 122 and 124. The base stations may include at least one evolved NodeB (eNB) for 4G LTE, enhanced LTE eNB (ng-eNB), or next-generation NodeB (gNB) for 5G New Radio (NR), or any other type of signal transmission and reception device, such as a UMTS NodeB. The eNB 122 communicates with the MME 112 via an S1 interface. Both the eNB 122 and the gNB 124 may connect to the AMF 114 via an Ng interface. Each base station manages and supports at least one cell. For example, base station gNB124 may be configured to manage and support cell 1, cell 2, and cell 3.

[0028] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU). The CU and DU may be co-located or separated into different locations. The CU and DU may be connected via an F1 interface. Alternatively, for eNBs that can connect to a 5G network, they may be similarly separated into a CU and at least one DU, referred to as an ng-eNB-CU and an ng-eNB-DU, respectively. The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface.

[0029] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1, labeled 140, includes cell 1, cell 2, and cell 3, and may further include more cells that may be managed by other base stations, not shown in FIG. 1 . The wireless communication network 100 may also include at least one UE 160. The UE may select a cell from among multiple cells supported by the base station to communicate with the base station via an over-the-air (OTA) wireless communication interface and resources, and as the UE 160 travels within the wireless communication network 100, the UE may reselect a cell for communication. For example, the UE 160 may initially select cell 1 to communicate with the base station 124 and then reselect cell 2 at a later point in time. Cell selection or reselection by the UE 160 may be based on wireless signal strength / quality in the various cells and other factors.

[0030] The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as 2G base stations, 3G NodeBs, LTE eNBs, or 5G NR gNBs. The UE 160 may be implemented as a mobile or fixed communication device capable of accessing the wireless communication network 100. The UE 160 may include, but is not limited to, a mobile phone, a laptop computer, a tablet, a personal digital assistant, a wearable device, an Internet of Things (IoT) device, an MTC / eMTC device, a distributed remote sensor device, a roadside assistance device, an XR device, and a desktop computer. The UE 160 may also be generally referred to as a wireless communication device or a wireless terminal. The UE 160 may support sidelink communication with another UE via a PC5 interface.

[0031] Although the following description focuses on cellular wireless communication systems such as that shown in Figure 1, the underlying principles are applicable to other types of wireless communication systems for paging wireless devices. These other wireless systems may include, but are not limited to, Wi-Fi, Bluetooth, ZigBee, and WiMax networks.

[0032] 2 illustrates an example of an electronic device 200 for implementing a network base station (e.g., a wireless access network node), a core network (CN), and / or operations and maintenance (OAM). Optionally, in one implementation, the exemplary electronic device 200 may include radio transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with UEs and / or other base stations. Optionally, in one implementation, the electronic device 200 may also include network interface circuitry 209 for communicating the base station with other base stations and / or a core network, e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may also include an input / output (I / O) interface 206 for communicating with an operator, etc., as needed.

[0033] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may configure one or more of processors 221 to perform the functions of a network node. Parameters 228 may include parameters to support execution of instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0034] FIG. 3 illustrates an example of an electronic device for implementing a terminal device 300 (e.g., user equipment (UE)). The UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. The UE 300 may include some or all of a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a memory device 309. The display circuit may include a user interface 310. The system circuit 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuit 304 may be implemented, for example, with one or more systems-on-chips (SoCs), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system circuit 304 may be part of the implementation of any desired function in the UE 300. In this regard, system circuitry 304 may include, by way of example, logic to facilitate decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV, running applications, accepting user input, storing and retrieving application data, establishing, maintaining, and terminating data connections for cellular phone calls or, by way of example, Internet connections, establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections, and displaying related information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements.Further examples of I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0035] 3, the communications interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that handles the transmission and reception of signals via one or more antennas 314. The communications interface 302 may include one or more transceivers. A transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving via one or more antennas or (for some devices) over a physical (e.g., wired) medium. The transmitted and received signals may conform to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and coding. As one specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether arising from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partnership or standards body.

[0036] 3 , the system circuitry 304 may include one or more processors 321 and memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to perform desired functions for the UE 300. The parameters 328 may provide and specify configuration and operation options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 sends or receives via the communication interface 302. In various implementations, system power for the UE 300 may be provided by a power storage device, such as a battery or a transformer.

[0037] (Connection State Discontinuous Reception (CDRX)) In a wireless communication network, a UE may constantly listen / monitor the network (e.g., a base station) to check whether there is new downlink data. The UE may also need to wait for an uplink grant to transmit uplink data. Notifications about scheduled downlink data or uplink transmission grants that the UE needs to monitor may arrive via a physical downlink control channel (PDCCH). Constantly listening / monitoring the network is not power-efficient and quickly drains the UE's battery. For example, even when there is light or no traffic for the UE and there is no downlink reception or uplink transmission for the UE, the UE still needs to stay awake to monitor the PDCCH, e.g., for one or more subframes. To reduce UE power consumption, a connected state (or mode) discontinuous reception (CDRX) function is introduced. When CDRX is configured for a UE in a connected state, each CDRX cycle may include one "ON" period and one "OFF" period. The UE does not need to continuously monitor the PDCCH, but only monitors the PDCCH during the "ON" periods and switches to sleep mode during the "OFF" periods. In sleep mode, the UE may turn off certain hardware circuits, such as the radio frequency (RF) chain, to reduce power consumption.

[0038] In an example implementation, a UE may be configured (e.g., by a base station) with a set of CDRX parameters. These CDRX parameters may be selected based on the type of service or application, for example, so that power and resource savings are maximized while quality of service (QoS) requirements are still met for the service or application. Note that the CDRX parameters may affect service performance metrics such as latency.

[0039] For example, the UE may be in an OFF period when data arrives at the base station (e.g., gNB), and the base station may need to wait until the UE is in an ON state, so there may be a delay in receiving the data. Therefore, the CDRX parameters may need to be carefully selected to find a balance between power saving and impact on QoS.

[0040] (Discontinuous Cell Transmission (DTX) and Discontinuous Cell Reception (DRX)) To further reduce the energy consumption of base stations such as gNBs, a base station-side discontinuous transmission (DTX) mode may be implemented. The base station-side DTX mode may be applied at various levels, such as the cell level, cell group level, DU level, DU group level, or the entire base station level. Using a cell as an example, when the DTX mode is applied to a cell, the cell may be configured with a cell DTX cycle. Within each cell DTX cycle, there are "ON" and "OFF" periods. To reduce power consumption, a cell may transmit downlink data to its served UEs only during the "ON" periods and suspend data transmission during the "OFF" periods. In some embodiments, during the cell DTX "OFF" period, downlink signals or downlink channels are disabled, i.e., the cell does not transmit downlink signals or channels during the cell DTX OFF period. Meanwhile, the UE does not receive downlink signals or channels during the cell DTX OFF period. For example, the UE does not monitor the PDCCH and PDSCH via semi-persistent scheduling (SPS) during the cell DTX OFF period.

[0041] A similar concept may also be applied to data reception at a base station. A base station-side discontinuous reception (DRX) mode may be implemented. The base station-side DRX mode may also be applied at various levels, such as the cell level, cell group level, DU level, DU group level, or the entire base station level. Using a cell as an example, when the DRX mode is applied to a cell, the cell may be configured with a cell DRX cycle. Within each cell DRX cycle, there may be an "ON" period and an "OFF" period. To further reduce power consumption, the cell may receive uplink data from the UE only during the "ON" period and suspend data reception during the OFF period. In some embodiments, during the cell DRX OFF period, the uplink signal or uplink channel is disabled, i.e., the UE does not transmit an uplink signal or channel during the cell DRX OFF period, and the cell does not receive an uplink signal or channel during the cell DRX OFF period. For example, the UE does not transmit a PUSCH via a configuration grant (CG) during the cell DRX OFF period.

[0042] The above description uses cells as an example. The same basic concept can be applied to cell groups, DUs, DU groups, and base stations.

[0043] In this disclosure, various embodiments are disclosed with the aim of reducing power consumption in base stations and UEs. These embodiments cover at least the following: · Configuring CDRX parameters at a more granular level, i.e., per DRB, per logical channel, per Semi-Persistent Scheduling (SPS), per Configuration Grant (CG), or per Hybrid Automatic Repeat Request (HARQ) process CDRX configuration. · Configuring HARQ mode for UE in Terrestrial Network (TN). Deactivating HARQ timers at a more granular level, i.e. per DRB, per logical channel, per Semi-Persistent Scheduling (SPS), per Configuration Grant (CG) or per Hybrid Automatic Repeat Request (HARQ) process. · Cell DTX and / or Cell DRX activation indication.

[0044] Details of these embodiments are described below. Embodiment 1: CDRX configuration parameters set for each service

[0045] In a wireless network, a UE may support various types of services, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). eMBB services offer greater data bandwidth and may include augmented reality (AR), virtual reality (VR), UltraHD, or 360-degree streaming video, and more. mMTC services may include narrowband Internet of Things (NB-IoT). URLLC services offer high reliability and low latency and may include mission-critical applications such as autonomous driving, vehicle-to-everything (V2X), remote diagnostics / surgery, and smart energy and grid.

[0046] Each service may be associated with specific service characteristics such as a packet delay budget, a packet error rate, a maximum data burst volume, a priority level, reliability requirements, and a tolerable retransmission delay. For example, a packet delay budget defines an upper limit on the amount of time a packet can be delayed between the UE and the network (e.g., a User Plane Function (UPF)). Different services may have different characteristics and QoS requirements. For example, a URLLC service may have strict low latency requirements and may tolerate minimal packet delay, but may not require high bandwidth. On the other hand, an eMBB service may require higher bandwidth but may be less sensitive to packet delay.

[0047] Under CDRX, a UE may be prepared with one or more connected state DRX configurations. Each connected state DRX configuration may include at least one of the following parameters: DRX Downlink Retransmission Timer (drx-RetransmissionTimerDL): The maximum duration for which a DL retransmission is received. Each downlink Hybrid Automatic Repeat Request (HARQ) process (except the broadcast process) may correspond to a drx-RetransmissionTimerDL. DRX Uplink Retransmission Timer (drx-RetransmissionTimerUL): The maximum duration until a grant for UL retransmission is received. Each uplink HARQ process may correspond to a drx-RetransmissionTimerUL. DRX Downlink HARQ Round Trip Time (RTT) Timer (drx-HARQ-RTT-TimerDL): The minimum waiting time that the UE expects to receive the PDCCH indicating downlink scheduling. Each downlink HARQ process (except the broadcast process) may correspond to one drx-HARQ-RTT-TimerDL. DRX Uplink HARQ RTT Timer (drx-HARQ-RTT-TimerUL): The minimum waiting time that the UE expects to receive a PDCCH indicating uplink scheduling. Each uplink HARQ process may correspond to a drx-HARQ-RTT-TimerUL.

[0048] These parameters may affect the allowed retransmission delay of a UE service and the time when the UE enters a CDRX off period. In a wireless network, a UE may support different services / sessions, such as different protocol data unit (PDU) sessions, different QoS flows, etc. These services may be mapped to different resources based on the service requirements. For example, these services may Different Data Radio Bearers (DRBs), Different Logical Channels (LC), Different resources allocated by semi-persistent scheduling (SPS), or · It can be mapped to different resources allocated by Configuration Grant (CG).

[0049] The above configurations / resources (DRB, LC, SPS, CG) may use independent HARQ processes.

[0050] 4a shows an example resource-to-HARQ process mapping. As shown in FIG. 4a, DRB1 and DRB2 are mapped to LC1, and LC1 is configured with HARQ process n to HARQ process (n+m), where n and m are non-negative integers.

[0051] 4b shows another example of resource-to-HARQ process mapping. As shown in FIG. 4b, one or more DRBs may be mapped to an LC, one or more LCs may be configured with one SPS resource, and one SPS resource may be configured with one or more HARQ processes.

[0052] 4c shows another example of resource to HARQ process mapping. As shown in FIG. 4c, one or more DRBs may be mapped to an LC, one or more LCs may be configured with one CG resource, and one CG resource may be configured with one or more HARQ processes.

[0053] The connection state DRX timers included within the connection state DRX configuration as described above (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL) may be started or stopped per HARQ process, i.e., each HARQ process may have its own set of timers.

[0054] In some example implementations, a "one-size-fits-all" connected state DRX configuration applies to all HARQ processes (and all UE services). As shown in FIG. 5, a common connected state DRX configuration 502 applies to multiple HARQ processes (or resources allocated to multiple services). The "one-size-fits-all" connected state DRX configuration may be, for example, at the cell level or DRX group level, in which the connected state DRX configuration applies to all HARQ processes in a cell or cell group. Thus, the granularity (or target level) of the connected state DRX configuration is at the cell level or DRX group level.

[0055] In some example implementations, rather than using a "one size fits all" connection state DRX configuration that applies to all types of services, each service may be configured with a connection state DRX configuration, i.e., the granularity (or target level) of the connection state DRX configuration is raised to one or more of the service level, or the DRB level, the LC level, the SPS level, the CG level, or the HARQ process level.

[0056] As explained above, the connection state DRX configuration may include at least one of the following parameters: ·drx-RetransmissionTimerDL, ·drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, or ·drx-HARQ-RTT-TimerUL.

[0057] In this embodiment, the connected state DRX configuration may be configured for UEs at different levels and with different granularity.

[0058] In some example implementations, the connection state DRX configuration may be configured on a per-DRB basis. As shown in Figure 6a, different DRBs may be configured with different connection state DRX configurations.

[0059] In some example implementations, the connection state DRX setting may be configured on a per-LC basis. As shown in Figure 6b, different LCs may be configured with different connection state DRX settings.

[0060] In some example implementations, a connection state DRX configuration may be configured for each SPS (i.e., a service that uses resources allocated by the SPS). As shown in Figure 6c, different SPSs may be configured with different connection state DRX configurations.

[0061] In some example implementations, the connection state DRX setting may be configured per CG (i.e., the service that uses the resources allocated by the CG). As shown in Figure 6d, different CGs may be configured with different connection state DRX settings.

[0062] In some example implementations, the connected state DRX configuration may be configured for each HARQ process, and different HARQ processes may be configured with different connected state DRX configurations, as shown in FIG. 6e.

[0063] FIG. 6f shows another example of a connected state DRX setting assignment.

[0064] FIG. 7 further shows a sample message flow for a base station to configure a connection state DRX configuration for a UE, where the connection state DRX configuration is on a per service / resource or per HARQ process basis.

[0065] In some example implementations, the connected state DRX configuration may be preconfigured in the UE via a network (e.g., a base station in the network) via messages of various layers (e.g., Layer 3, Layer 2, and Layer 1), such as, for example, a Radio Resource Control (RRC) message, a Medium Access Control - Control Element (MAC CE) message, a Downlink Control Information (DCI) message, a System Information message, a Broadcast message, etc. For example, the UE may receive a System Information message carrying a list of connected state DRX configurations.

[0066] In some implementations, the UE may receive an indicator indicating which particular connected state DRX configuration should be selected for a particular service (e.g., DRB, LC, SPS, CG, or HARQ process to which the service is mapped) from a list of connected state DRX configurations. The indicator may be, for example, an index into the list of connected state DRX configurations. The UE may then apply the selected connected state DRX configuration of the particular target (e.g., DRB, LC, SPS resources, CG resources, HARQ process). In this scenario, each service is individually assigned to a connected state DRX configuration (or connected state DRX configuration assignment is made to each target individually).

[0067] In some implementations, the UE may receive a connected state DRX configuration and an indication of which targets the configuration applies to.

[0068] In some implementations, it is possible to combine multiple assignments in one message. For example, referring back to Figure 6a, a single message may carry an indicator indicating that Connected State DRX Setting 1 is assigned to DRB1 and Connected State DRX Setting 2 is assigned to DRB2. Note that the assignment of settings is per target (e.g., DRB, LC, SPS resources, CG resources, or HARQ process).

[0069] In some implementations, multiple assignments can be combined in one message, and one connection state DRX configuration may be assigned to multiple targets, for example, one connection state DRX configuration may be assigned to a group of DRBs, a group of LCs, a group of HARQ processes, etc.

[0070] In some implementations, multiple services can use the same connected state DRX configuration. For example, one group of DRBs may use connected state DRX configuration 1, another group of DRBs may use connected state DRX configuration 2, and another group of HARQ processes may use connected state DRX configuration 3. In this case, note that connected state DRX configurations 1, 2, and 3 are not "one size fits all" connected state DRX configurations, even though each of them may apply to multiple services. Illustratively, for each service, the network may need to indicate separately which connected state DRX configuration to use.

[0071] In some example implementations, the UE may still be configured with a "fits all" connected state DRX configuration, such as a cell level, or a DRX group level connected state DRX configuration. The "fits all" connected state DRX configuration may serve as a default configuration. In this case, the service-specific connected state DRX configuration, if configured, has higher priority. That is, if a service-specific connected state DRX configuration is configured for a DRB, LC, SPS, CG, or HARQ process, the current service-specific connected state DRX configuration applies to, for example, the DRB, LC, SPS, CG, or HARQ process. Otherwise, the cell level or DRX group level connected state DRX configuration may apply.

[0072] In this embodiment, the connected state DRX configuration is specific to a service (or target, such as a resource or HARQ process), rather than being "one size fits all." For each service, the network can specify the connected state DRX configuration. Thus, the network can gain precise control over the transmission characteristics of the service based on service requirements, e.g., QoS requirements. The connected state DRX configuration provided in this embodiment has higher precision compared to the "one size fits all" configuration.

[0073] Embodiment 2: HARQ mode configuration in terrestrial networks In non-terrestrial networks (NTNs), different HARQ modes may be supported, including HARQ Mode A and HARQ Mode B, which aim to improve UE data rates and avoid HARQ stalls in large round-trip time (RTT) use cases. In HARQ Mode A, the HARQ RTT timer and retransmission timer may be started (e.g., retransmission is activated). However, in HARQ Mode B, the HARQ RTT timer and retransmission timer are not started. For example, for a UE in an NTN, if the HARQ process is configured in HARQ Mode B, the UE is not expected to start the HARQ RTT timer and / or the retransmission timer.

[0074] In some example implementations, in NTN, the base station may indicate to the UE whether to start a HARQ RTT timer and / or a retransmission timer for a HARQ process associated with a service based on the service characteristics of the service (e.g., service type, QoS requirements, service pattern, etc.).

[0075] However, in a terrestrial network (TN) environment, the HARQ mode as described above for NTN networks is not supported. However, using the HARQ mode can still be beneficial in TN networks. For example, a UE may carry a service with short periodicity (e.g., 4 ms periodicity), and power saving is important to the UE (e.g., CG and / or CDRX may be configured / activated for this UE). In this case, if the HARQ RTT timer and retransmission timer are started, it may be difficult or even impossible for the UE to enter the CDRX off state for power saving. On the other hand, for services with short periodicity, retransmission may be performed at the next CG opportunity or scheduling grant, if necessary. Therefore, the HARQ timer and retransmission timer do not need to be started, thereby improving UE power saving.

[0076] In this embodiment, the aforementioned HARQ mode may be added to a TN network. However, the UE may or may not have the capability to support this feature. For example, legacy or low-end UEs may not support this feature. This may cause some problems on the base station side. Because the base station does not know the UE's capability regarding support for the HARQ mode, the base station may not utilize its knowledge of the service characteristics of the UE service. For example, in this case, the base station cannot instruct the UE not to start the HARQ RTT timer and / or retransmission timer for the HARQ process, even though the base station knows that it is beneficial to do so. This behavior may further adversely affect the UE's power consumption because the timers must be started unconditionally.

[0077] In this embodiment, when the UE is in the TN, the UE may report its UE capability regarding support of HARQ mode to the base station. For example, the UE may report whether it supports the HARQ mode mechanism (or whether it supports HARQ Mode B) as described above. Only when the UE supports the HARQ mode mechanism in the TN may the base station configure the UE with a HARQ mode (e.g., HARQ Mode A or HARQ Mode B) when the UE is served by a terrestrial network cell. An exemplary process is shown in FIG. 8.

[0078] 8, the UE capabilities may be sent in a Radio Resource Control (RRC) message such as RRC Msg3 / Msg5, UE Capability Information message, Uplink Medium Access Control - Control Element (UL MAC CE) message (e.g., as found in the random access procedure and / or the RRC connection setup procedure), or the UE capabilities may be implicitly indicated by the UL LC_ID (Logical Channel ID) in the MAC CE header.

[0079] In some implementations, the HARQ mode configuration applies to uplink HARQ mode (uplinkHARQ-Mode) when the UE is in (or served by) a TN cell.

[0080] The HARQ mode setting may be set, for example, by an uplinkHARQ-Mode in an RRC message for a UE in a TN cell. For example, the uplink HARQ-Mode bit of an HARQ process may be set to HARQ-Mode B.

[0081] Table 1 below shows an example logic flow for starting the relevant HARQ RTT timers in the NTN and NT networks. In Table 1, if the timer name ends with "-NTN", this indicates that the timer applies to the NTN network. Otherwise, the time applies to the TN network. [Table 1]

[0082] Embodiment 3: HARQ timer deactivation indicator In this embodiment, an indication for deactivating (or not starting) the drx-HARQ-RTT-Timer may be set per UE, per DRB, per logical channel, per SPS, per CG, and / or per HARQ process. The drx-HARQ-RTT-Timer may include a drx-HARQ-RTT-TimerDL and a drx-HARQ-RTT-TimerUL as previously described. When a timer is deactivated, the UE is not expected to start the timer.

[0083] In an example implementation, a base station (e.g., a gNB) may decide to deactivate the drx-HARQ-RTT-Timer (for DL ​​and / or UL) using a service-specific indicator based on the service characteristics of a service associated with one of the DRB, logical channel, SPS, CG, or HARQ process.

[0084] Specifically, if an indication for deactivating the drx-HARQ-RTT-Timer is configured per UE, per DRB, per logical channel, per SPS, per CG, and / or per HARQ process, the UE does not start or is not expected to start the drx-HARQ-RTT-Timer when sending or receiving data for the DRB, logical channel, SPS, CG, and / or HARQ process accordingly, i.e., the precision (or target level) for deactivating the drx-HARQ-RTT-Timer is raised to one or more of the UE level, DRB level, LC level, SPS level, CG level, or HARQ process level.

[0085] The indication to deactivate the drx-HARQ-RTT-Timer (UL and DL) may be set by an RRC message, a MAC CE message, or a DCI message.

[0086] An indication to deactivate the drx-HARQ-RTT-Timer may also be conveyed via a HARQ feedback disable indicator, for example, to disable HARQ feedback. When HARQ feedback is disabled, the drx-HARQ-RTT-Timer may be deactivated.

[0087] In some example implementations, the UE may or may not support the DRX HARQ RTT timer deactivation function, or the UE may or may not support the DRX HARQ feedback deactivation function. In this case, the UE may send an indicator to the base station, where the indicator indicates the radio capability of the UE. The radio capability indicates whether the UE supports the DRX HARQ RTT timer deactivation function or whether the UE supports the HARQ feedback deactivation function. Based on the indicator, the base station may determine whether to deactivate the UE's DRX HARQ RTT timer or to be enabled to deactivate HARQ feedback.

[0088] Embodiment 4: Cell DTX / DRX Activation Indication As described in the above sections, cell DTX and / or cell DRX may be used to conserve network energy consumption (e.g., to conserve gNB energy). The cell DTX / DRX function may be activated or deactivated based on, for example, cell load or other traffic patterns that may affect cell signal transmission and / or reception. The cell load may include real-time measured cell load or predicted cell load based on historical data, for example, via an artificial intelligence (AI) model. The cell DTX / DRX function may be activated when there is no traffic in the cell or when the cell load is light (e.g., below a threshold, below occupancy, etc.) and deactivated when the cell is under heavy load (e.g., above a threshold, above occupancy, etc.). Furthermore, because cell load is a variable, cell DTX / DRX may be activated / deactivated as needed, and the corresponding cell DTX / DRX settings (e.g., the periodicity, start time, and / or start offset used to determine the DTX / DRX “ON” and “OFF” periods, etc.) may also be dynamically updated. As an example, when the cell load is within a first range, a cell DTX / DRX setting of 1 may be set, and when the cell load is within a second range, a cell DTX / DRX setting of 2 may be set.

[0089] In some exemplary implementations, the cell DTX and / or cell DRX mechanism is a two-step process. In a first step, the cell DTX and / or cell DRX settings may be preconfigured in the UE when the UE's RRC connection is set up or reconfigured. In a second step, once the conditions for activating the cell DTX and / or cell DRX functionality are met (e.g., based on cell load conditions), the base station may activate the cell DTX and / or cell DRX functionality via Layer 1 common signaling, such as a DCI message. Note that this common signaling may target all UEs that are in an RRC connected (RRC_CONNECTED) state and are covered / served by the cell.

[0090] Note that in the above implementations, common signaling is sent to UEs in an RRC connected state when the cell DTX and / or cell DRX configuration is first configured in a cell. However, for UEs that are not in an RRC connected state (e.g., UEs in an idle or inactive state), these UEs may miss the common signaling to activate the DTX and / or cell DRX functionality.

[0091] FIG. 9 shows an example of the scenario described above.

[0092] At t0, all UEs in RRC connected state may receive the cell DTX and / or cell DRX configuration. The configuration has not yet been activated. Note that UE4 is in the deactivated or idle state.

[0093] At t1, it is determined that the cell DTX and / or cell DRX function needs to be activated, and common signaling indicating the function activation is sent to all UEs in an RRC connected state.

[0094] At t2, UE4 transitions to the RRC connected state. Note that UE4 missed the signaling sent at t1 and does not recognize or apply the cell DTX and / or cell DRX feature activation.

[0095] Similarly, the problems described above may occur during a UE handover procedure. Still referring to Figure 9, at t2, UE 5 is handed over from cell 2 to cell 1. Because the handover occurs after the initial cell DTX and / or cell DRX function activation occurs at t1, UE 5 does not recognize and does not apply the cell DTX and / or cell DRX function activation.

[0096] In this disclosure, various solutions are described below to solve the above-mentioned problems.

[0097] Solution 1: Referring to FIG. 10 , when a UE is handed over to cell 1 with cell DTX activated and / or cell DRX already activated, or when the UE is in an RRC connection setup procedure (the UE is in an inactive or idle state when cell DTX and / or cell DRX functionality is first activated), the UE may receive cell DTX and / or cell DRX configurations as shown in step S1001 of FIG. 10 . For example, the UE may receive one or more cell DTX and / or cell DRX configurations (e.g., a list of configurations). The indicator may be sent together with the configurations or via a separate message. The indicator may indicate that cell DTX and / or cell DRX functionality is activated or which configurations apply and need to be activated. When the UE receives this indicator, the UE immediately activates the cell DTX and / or cell DRX functionality using the indicated configurations.

[0098] In some example implementations, the list of configurations may include configurations for both cell DTX settings and cell DRX settings.

[0099] In some example implementations, there may be two lists, one for cell DTX settings and the other for cell DRX settings. Correspondingly, there may be two indicators, one for indicating the cell DTX configuration and the other for indicating the cell DRX settings. In this way, the cell DTX and cell DRX functions may be activated separately. The underlying principle is that an indication may be sent to the UE to indicate which functions (i.e., cell DTX and / or cell DRX) should be activated using the indicated configuration.

[0100] If the UE is handed over to cell 1 with the cell DTX and / or cell DRX functionality deactivated, the indicators will indicate accordingly so that the UE does not activate the cell DTX and / or cell DRX functionality immediately after the handover. If the cell DRX and cell DTX functionality is subsequently activated, layer 1 common signaling may be sent to the UE to indicate the functionality activation.

[0101] In some example implementations, the indicator may be required. Illustratively, a value of 1 may indicate activation of the feature, and a value of 0 may indicate that the feature is not activated.

[0102] In some example implementations, the indicator may be optional: if the indicator is present, it indicates that the feature is activated, and if the indicator is not present, it indicates that the feature is not activated.

[0103] FIG. 11 shows exemplary cell DTX / DRX configurations. In FIG. 11, cell DTX configurations and cell DRX configurations may be transmitted in combination. FIG. 11 shows three combined configurations 1102, 1104, and 1106. To indicate the combination, an indicator 1108 may be attached to the selected configuration. Alternatively, an index may be sent to indicate which element in the list of configurations was selected. For example, an indicator equal to 2 indicates (cell DTX configuration 2 + cell DRX configuration 2).

[0104] Note that the cell DTX configuration and the cell DRX configuration may be sent separately, as shown in Figure 12. Cell DTX configurations 1202, 1204, and 1206 and cell DRX configurations 1212, 1214, and 1216 may be transmitted to the UE. An indicator 1208 may be used to indicate the cell DTX configuration to be activated, and another indicator 1218 may be used to indicate the cell DRX configuration to be activated.

[0105] In some example implementations, step S1001 may occur during a handover procedure or an RRC connection setup procedure. For example, the UE may receive the message S1001 from cell 2, which is the source cell in the handover procedure. That is, the cell DTX and / or cell DRX settings and / or the feature activation indicator may be sent by the source cell. Because the feature activation is part of the handover procedure or the RRC connection setup procedure, advantages may include quick feature activation. When the UE is handed over or the UE RRC connection is set up, the cell DTX and / or cell DRX features are already activated using the indicated settings.

[0106] Solution 2: In this solution, both Layer 1 common signaling (e.g., common DCI) and UE-specific signaling (e.g., MAC CE, or UE-specific DCI, or dedicated RRC signaling) may be used to activate the cell DTX and / or cell DRX functionality.

[0107] When cell DTX and / or cell DRX are first activated, Layer 1 common signaling (e.g., common DCI) may be sent to UEs in RRC_CONNECTED state for cell DTX and / or cell DRX activation.

[0108] When cell DTX and / or cell DRX are already activated for a cell and the UE is handed over to the cell, if the UE is in an RRC connection setup procedure to set up an RRC connection with the cell, UE-specific signaling (e.g., MAC CE, or UE-specific DCI, or dedicated RRC signaling) may be sent to the UE for cell DTX and / or cell DRX activation. The indicators may be implemented similarly to those provided in Solution 1 above.

[0109] In some example implementations, the UE may or may not support the functionality of cell DTX operation and / or cell DRX operation. In this case, the UE may send an indicator to the base station, where the indicator indicates the radio capabilities of the UE. The radio capabilities indicate whether the UE supports cell DTX operation and / or cell DRX operation. Based on the indicator, the base station may determine whether to be enabled to configure and / or activate cell DTX operation and / or cell DRX operation for the UE.

[0110] The above description and accompanying drawings provide specific exemplary embodiments and implementations. However, the described subject matter may be embodied in a variety of different forms, and therefore, it is intended that the covered or claimed subject matter not be construed as limited to any exemplary embodiments set forth herein. A reasonably broad scope of claimed or covered subject matter is intended. Among other things, for example, the subject matter may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Accordingly, embodiments may take the form of, for example, hardware, software, firmware, a storage medium, or any combination thereof. For example, the method embodiments described above may be implemented by a component, device, or system including a memory and a processor by executing computer code stored in the memory.

[0111] Throughout this specification and the claims, terms may have subtly different meanings suggested or implied in context beyond their explicitly stated meaning. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, claimed subject matter is intended to include, in whole or in part, a combination of the example embodiments.

[0112] Generally, terminology can be understood, at least in part, from its usage in context. For example, terms such as "and," "or," or "and / or" as used herein can include a variety of meanings that may depend, at least in part, on the context in which such terms are used. Typically, "or" when used to relate a list such as A, B, or C is intended to mean A, B, and C, which are used herein in an inclusive sense, as well as A, B, or C, which are used herein in an exclusive sense. Additionally, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in a singular sense, or may be used to describe a combination of features, structures, or characteristics in a plural sense, depending, at least in part, on the context. Similarly, terms such as "a," "an," or "the" may be understood to convey either a singular usage or a plural usage, depending, at least in part, on the context. Additionally, the term "based on" may be understood as not necessarily intended to convey an exclusive set of factors, but instead may allow for the existence of additional factors not necessarily explicitly described, again depending at least in part on the context.

[0113] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages that may be realized using the present solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that the particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of features and advantages and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0114] Furthermore, the described features, advantages, and characteristics of the solution may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in particular embodiments that may not be present in all embodiments of the solution.

Claims

1. 1. A method for wireless communication implemented by a wireless device, comprising: receiving, from a network node, a first message comprising a first connected state discontinuous reception (DRX) setting or an indicator indicative of the first connected state DRX setting, the first connected state DRX setting being assigned to a first target associated with a first service of the wireless device, the first target being one of: Data Radio Bearer (DRB), logical channels, Semi-persistent scheduling (SPS), Configuration Grant (CG), or Hybrid Automatic Repeat Request (HARQ) Process and applying the first connected state DRX setting to the first target; A method comprising:

2. The connected state DRX configuration includes the following parameters for downlink or uplink data retransmission: drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, or drx-HARQ-RTT-TimerUL The method of claim 1 , comprising at least one of:

3. the first message further comprises a second connected state DRX setting or an indicator indicating the second connected state DRX setting; the second connected state DRX setting is assigned to a second target associated with a second service of the wireless device; the second target is different from the first target; The method of claim 1 , wherein the second connected state DRX setting is different from the first connected state DRX setting.

4. The method of claim 1 , wherein the indicator displays the first connected state DRX setting from a list of connected state DRX settings.

5. said list of connected state DRX settings being: RRC messages, MAC CE message, System information messages, or Broadcast Message The method of claim 4 , wherein the wireless device is preconfigured via one of the following:

6. The method of claim 1 , wherein the first connected state DRX setting has a higher priority than a cell-level connected state DRX setting.

7. the network node: gNodeB (gNB), eNodeB (eNB), ng-eNodeB (ng-eNB), or Node B The method of claim 1 , comprising at least one of:

8. 1. A method for wireless communication implemented by a wireless device, comprising: transmitting, to a network node, an indicator indicating a radio capability of the wireless device, the radio capability indicating whether the wireless device supports HARQ Mode B when a serving cell of the wireless device is a terrestrial network cell, wherein in HARQ Mode B, a HARQ round trip time (RTT) timer and a HARQ retransmission timer are not started; receiving a HARQ mode indicator from the network node when the wireless device is within the terrestrial network cell, the HARQ mode indicator instructing the wireless device to apply the HARQ mode B; A method comprising:

9. the radio capability further indicates whether the wireless device supports a HARQ mechanism in which either the HARQ Mode B or the HARQ Mode A can be configured in the wireless device; The method of claim 8 , wherein in the HARQ mode A, the HARQ RTT timer and the HARQ retransmission timer are enabled to be started.

10. The indicator: Radio Resource Control (RRC) Msg3, RRC Msg5, UE Capability Information message, an uplink medium access control - control element (UL MAC CE) message, or Uplink Logical Channel Identifier (UL LC-ID) in MAC CE message header 9. The method of claim 8, wherein the signal is delivered via at least one of:

11. The HARQ mode indicator instructs the wireless device to apply the HARQ mode B to a transmission level, the transmission level comprising: Per wireless device level, By DRB level, Per logical channel level, For each SPS level, By CG level, or Per HARQ process level The method of claim 8 , comprising at least one of:

12. The HARQ mode indicator: RRC messages, MAC CE message, a Downlink Control Information (DCI) message, or Uplink HARQ Feedback Disable Indicator 12. The method of claim 11, wherein the signal is sent via at least one of:

13. The method of claim 11 , wherein the wireless device is not expected to start the HARQ RTT timer for a HARQ process associated with the transmission level according to the HARQ mode indicator.

14. 1. A method for wireless communication implemented by a wireless device, comprising: receiving a first message from a network node indicating deactivation of a DRX HARQ round trip timer (drx-HARQ-RTT-Timer), wherein the drx-HARQ-RTT-Timer: Data Radio Bearer (DRB), logical channels, Semi-persistent scheduling (SPS), Configuration Grant (CG), or Hybrid Automatic Repeat Request (HARQ) Process The method is applied to a target comprising one of:

15. Before receiving the first message, the method further comprises:

15. The method of claim 14, further comprising: transmitting, to the network node, an indicator indicating a radio capability of the wireless device, the radio capability indicating whether the wireless device supports deactivation of a DRX HARQ RTT timer.

16. 15. The method of claim 14, wherein in response to receiving the first message, the wireless device is not expected to start the drx-HARQ-RTT-Timer associated with the target.

17. The drx-HARQ-RTT-Timer uplink drx-HARQ-RTT-Timer, or Downlink drx-HARQ-RTT-Timer The method of claim 14 , comprising at least one of:

18. The first message: RRC messages, MAC CE message, DCI message, or an indicator that uplink HARQ feedback is disabled for the target; 15. The method of claim 14, wherein the signal is sent via one of:

19. 1. A method for wireless communication implemented by a wireless device, comprising: receiving an indicator, via a UE-specific message targeted at the wireless device, indicating whether discontinuous cell operation is activated in a cell, the discontinuous cell operation comprising at least one of discontinuous cell transmission (DTX) or discontinuous cell reception (DRX); and activating a setting associated with the cell discontinuity operation in response to the indicator indicating that the cell discontinuity operation is activated in the cell; and A method comprising:

20. Prior to receiving the UE-specific message targeted at the wireless device, the method further comprises:

20. The method of claim 19, further comprising: transmitting, to a network node, an indicator indicating a radio capability of the wireless device, the radio capability indicating whether the wireless device supports cellular DTX or DRX operation.

21. the UE-specific message RRC messages, a MAC CE message, or a UE-specific DCI message targeted to the wireless device 20. The method of claim 19, comprising at least one of:

22. receiving the indicator indicating whether the cell discontinuity operation is activated in the cell; 20. The method of claim 19, comprising receiving the indicator, indicating whether the cell discontinuity operation is activated in the cell, via the UE-specific message targeted at the wireless device when the wireless device is in one of the following procedures: an RRC connection setup procedure, or a handover procedure in which the wireless device is handed over to the cell from a source cell.

23. receiving the indicator indicating whether the discontinuous cell operation is activated in the cell includes receiving, via the UE-specific message targeted at the wireless device, a list of candidate configurations for discontinuous cell operation and the indicator indicating whether a configuration in the list of candidate configurations is activated; 20. The method of claim 19, wherein activating the setting associated with the cell discontinuity operation comprises activating the setting in response to activation of the indicator indicating the setting in the list of candidate settings.

24. The settings associated with the cell discontinuity operation include the following parameters: a cell DTX periodicity parameter for determining the cell DTX "ON" period and the cell DTX "OFF" period; a cell DTX start time parameter for determining the cell DTX "ON" period and the cell DTX "OFF" period; a cell DTX start offset parameter for determining the cell DTX "ON" period and the cell DTX "OFF" period; a cell DRX periodicity parameter for determining the cell DRX "ON" period and the cell DRX "OFF" period; a cell DRX start time parameter for determining the cell DRX "ON" period and the cell DRX "OFF" period; or a cell DRX start offset parameter for determining the cell DRX "ON" period and the cell DRX "OFF" period; 20. The method of claim 19, comprising at least one of:

25. activating the setting associated with the cell discontinuity operation; Receiving a downlink signal or a downlink channel during a cell DTX OFF period; or Transmitting an uplink signal or an uplink channel during a cell DRX OFF period 20. The method of claim 19, comprising disabling at least one of:

26. 1. A method for wireless communication implemented by a network node, comprising: transmitting, to a wireless device, a first message comprising a first connected-state discontinuous reception (DRX) setting or an indicator indicative of the first connected-state DRX setting, the first connected-state DRX setting being assigned to a first target associated with a first service of the wireless device, the first target being one of: Data Radio Bearer (DRB), logical channels, Semi-persistent scheduling (SPS), Configuration Grant (CG), or Hybrid Automatic Repeat Request (HARQ) Process The method comprises one of:

27. The connected state DRX configuration includes the following parameters for downlink or uplink data retransmission: drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, or drx-HARQ-RTT-TimerUL 27. The method of claim 26, comprising at least one of:

28. the first message further comprises a second connected state DRX setting or an indicator indicating the second connected state DRX setting; the second connected state DRX setting is assigned to a second target associated with a second service of the wireless device; the second target is different from the first target; 27. The method of claim 26, wherein the second connected state DRX setting is different from the first connected state DRX setting.

29. 27. The method of claim 26, wherein the indicator displays the first connected state DRX setting from a list of connected state DRX settings.

30. said list of connected state DRX settings being: RRC messages, MAC CE message, System information messages, or Broadcast Message 30. The method of claim 29, wherein the wireless device is preconfigured via one of:

31. 27. The method of claim 26, wherein the first connected state DRX setting has a higher priority than a cell-level connected state DRX setting.

32. the network node: gNodeB (gNB), eNodeB (eNB), ng-eNodeB (ng-eNB), or Node B 27. The method of claim 26, comprising at least one of:

33. 1. A method for wireless communication implemented by a network node, comprising: receiving, from a wireless device, an indicator indicating a radio capability of the wireless device, the radio capability indicating whether the wireless device supports a HARQ Mode B when a serving cell of the wireless device is a terrestrial network cell, wherein in the HARQ Mode B, a HARQ round trip time (RTT) timer and a HARQ retransmission timer are not started; transmitting a HARQ mode indicator to the wireless device served by the terrestrial network cell, the HARQ mode indicator instructing the wireless device to apply the HARQ mode B; A method comprising:

34. the radio capability further indicates whether the wireless device supports a HARQ mechanism in which either the HARQ Mode B or the HARQ Mode A can be configured in the wireless device; 34. The method of claim 33, wherein the HARQ Mode A is enabled to start the HARQ RTT timer and the HARQ retransmission timer.

35. The indicator: Radio Resource Control (RRC) Msg3, RRC Msg5, UE Capability Information message, an uplink medium access control - control element (UL MAC CE) message, or Uplink Logical Channel Identifier (UL LC-ID) in MAC CE message header 34. The method of claim 33, wherein the delivery is via at least one of:

36. The HARQ mode indicator instructs the wireless device to apply the HARQ mode B to a transmission level, the transmission level comprising: Per wireless device level, By DRB level, Per logical channel level, For each SPS level, By CG level, or Per HARQ process level 34. The method of claim 33, comprising one of:

37. The HARQ mode indicator: RRC messages, MAC CE message, a Downlink Control Information (DCI) message, or Uplink HARQ Feedback Disable Indicator 37. The method of claim 36, wherein the signal is transmitted via at least one of:

38. 37. The method of claim 36, wherein the wireless device is not expected to start the HARQ RTT timer for a HARQ process associated with the transmission level according to the HARQ mode indicator.

39. 1. A method for wireless communication implemented by a network node, comprising: transmitting a first message to a wireless device instructing the wireless device to deactivate a DRX HARQ round trip timer (drx-HARQ-RTT-Timer), the drx-HARQ-RTT-Timer being applied to a target for the wireless device, the target being one of: Data Radio Bearer (DRB), logical channels, Semi-persistent scheduling (SPS), Configuration Grant (CG), or Hybrid Automatic Repeat Request (HARQ) Process The method comprises one of:

40. Before transmitting the first message, the method further comprises:

40. The method of claim 39, further comprising receiving, from the wireless device, an indicator indicative of a radio capability of the wireless device, the radio capability indicating whether the wireless device supports deactivation of a DRX HARQ RTT timer.

41. 40. The method of claim 39, wherein in response to receiving the first message, the wireless device is not expected to start the drx-HARQ-RTT-Timer associated with the target.

42. The drx-HARQ-RTT-Timer uplink drx-HARQ-RTT-Timer, or Downlink drx-HARQ-RTT-Timer 40. The method of claim 39, comprising at least one of:

43. The first message: RRC messages, MAC CE message, DCI message, or an indicator that uplink HARQ feedback is disabled for the target; 40. The method of claim 39, wherein the signal is transmitted via one of:

44. 1. A method for wireless communication implemented by a network node, comprising:

1. A method comprising: transmitting, via a UE-specific message targeted at a wireless device, an indicator indicating whether discontinuous cell operation is activated in a cell of the network node, the discontinuous cell operation comprising at least one of discontinuous cell transmission (DTX) or discontinuous cell reception (DRX).

45. Prior to receiving the UE-specific message targeted at the wireless device, the method further comprises:

45. The method of claim 44, further comprising receiving, from the wireless device, an indicator indicating a radio capability of the wireless device, the radio capability indicating whether the wireless device supports cellular DTX or DRX operation.

46. 45. The method of claim 44, wherein in response to the indicator indicating that the discontinuous cell operation is activated in the cell, the wireless device activates a setting associated with the discontinuous cell operation.

47. The settings related to the cell discontinuous operation include the following parameters: a cell DTX periodicity parameter for determining the cell DTX "ON" period and the cell DTX "OFF" period; a cell DTX start time parameter for determining the cell DTX "ON" period and the cell DTX "OFF" period; a cell DTX start offset parameter for determining the cell DTX "ON" period and the cell DTX "OFF" period; a cell DRX periodicity parameter for determining the cell DRX "ON" period and the cell DRX "OFF" period; a cell DRX start time parameter for determining the cell DRX "ON" period and the cell DRX "OFF" period; or a cell DRX start offset parameter for determining the cell DRX "ON" period and the cell DRX "OFF" period; 47. The method of claim 46, comprising at least one of:

48. the UE-specific message RRC messages, a MAC CE message, or a UE-specific DCI message targeted to the wireless device 45. The method of claim 44, comprising at least one of:

49. transmitting the indicator indicating whether the cell discontinuity operation is activated in the cell; 45. The method of claim 44, comprising transmitting the indicator, indicating whether the cell discontinuity operation is activated in the cell, via the UE-specific message targeted at the wireless device when the wireless device is in one of the following procedures: an RRC connection setup procedure, or a handover procedure in which the wireless device is handed over to the cell from a source cell.

50. transmitting the indicator indicating whether the cell discontinuity operation is activated in the cell; 45. The method of claim 44, comprising transmitting, via the UE-specific message targeted to the wireless device, a list of candidate configurations for discontinuous cell operation and the indicator indicating whether a configuration in the list of candidate configurations is activated.

51. the indicator indicating that the discontinuous cell operation is activated in the cell of the network node; The method comprises: Transmitting a downlink signal or a downlink channel during a cell DTX OFF period; or Receiving an uplink signal or an uplink channel during a cell DRX OFF period 45. The method of claim 44, further comprising disabling at least one of:

52. 52. A device for wireless communication comprising a memory for storing computer instructions and a processor in communication with said memory, wherein when said processor executes said computer instructions, said processor is configured to implement a method according to any one of claims 1 to 51.

53. 52. A computer program product comprising a non-transitory computer readable program medium with computer code stored thereon, the computer code, when executed by one or more processors, causing the one or more processors to implement the method of any one of claims 1 to 51.

Images