CN117015081A - Method and apparatus for handling discontinuous reception configuration for augmented reality - Google Patents

Abstract

Methods and apparatus are provided for handling discontinuous reception configurations for augmented reality. The method comprises the following steps: receiving a first signaling configuring at least one value of a discontinuous reception parameter; receiving second signaling in the serving cell indicating a first value of the discontinuous reception parameter or a second value of at least one value of the discontinuous reception parameter; and performing at least one of: adjusting discontinuous reception parameters for the first discontinuous reception group or the second discontinuous reception group of the user equipment based on the target discontinuous reception group indicated in the second signaling or based on whether the serving cell is assigned to the first discontinuous reception group or the second discontinuous reception group; restarting the drx-onduration timer at a timing calculated based on the first value or the second value of the discontinuous reception parameter indicated in the second signaling in response to receiving the second signaling; stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing in response to receiving the second signaling; or stopping and starting the drx-onduration timer at or after transmitting an acknowledgement in response to the receipt of the second signaling.

Description

Method and apparatus for handling discontinuous reception configurations for extended reality

Technical Field

The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for handling DRX configuration for augmented reality in a wireless communication system.

Background Art

With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) packets. This IP packet communication can provide IP-bearing voice, multimedia, multicast and on-demand communication services for users of mobile communication devices.

An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-bearing voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards.

Summary of the invention

Methods, systems, and devices are provided for handling discontinuous reception (DRX) configuration for extended reality in a wireless communication system, wherein a user equipment (UE) can reduce physical downlink control channel (PDCCH) monitoring for extended reality (XR) downlink (DL) services in a radio resource control (RRC) connected mode, the UE can be configured with various DRX configurations to meet the XR service, the UE can be instructed to use an appropriate DRX configuration from the various DRX configurations to meet the XR service, and/or the UE can appropriately report or transmit a sounding reference signal (SRS) and/or channel state information (CSI) when a dynamic DRX configuration is applied for the XR service.

In various embodiments, a method for a UE in a wireless communication system includes: receiving first signaling configuring at least one value of a DRX parameter; receiving second signaling indicating a first value of the DRX parameter or a second value of the at least one value of the DRX parameter in a serving cell; and performing at least one of the following: adjusting the DRX parameter of a first DRX group or a second DRX group for the UE based on a target DRX group indicated in the second signaling or based on whether the serving cell is assigned to the first DRX group or the second DRX group; restarting a drx-onDurationTimer at a timing calculated based on the first value or the second value of the DRX parameter indicated in the second signaling in response to receiving the second signaling; stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing in response to receiving the second signaling; or stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing in response to or after receiving a transmission confirmation of the second signaling.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing a wireless communication system according to an embodiment of the present invention.

2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention.

FIG. 3 is a functional block diagram of a communication system according to an embodiment of the present invention.

FIG. 4 is a functional block diagram of the program code of FIG. 3 according to an embodiment of the present invention.

Figure 5 is a reproduction of Figure 5.1.1-1: Single stream DL traffic model from 3GPP TR 38.838 V17.0.0 “Study on Extended Reality (XR) Evaluation for NR”.

FIG. 6 is a diagram illustrating an example of a DRX operation for an on-duration according to an embodiment of the present invention.

7 is an example diagram illustrating that an on-duration may be shifted due to a modification of a start offset (eg, drx-SlotOffset) to an on-duration according to an embodiment of the present invention.

8 is an example diagram illustrating an on-duration that may be shifted due to modification of a start offset to an on-duration (eg, drx-SlotOffset), according to an embodiment of the present invention.

9 is an example diagram illustrating that an on-duration may be shifted due to modification of the length of the on-duration (eg, drx-onDurationTimer) according to an embodiment of the present invention.

10 is an example diagram illustrating that an on-duration may be shifted due to modification of the length of the on-duration (eg, drx-onDurationTimer) according to an embodiment of the present invention.

FIG. 11 is an example diagram showing that an on-duration may be shifted due to a modification of the length of a DRX cycle (eg, drx-ShortCycle, drx-LongCycle) according to an embodiment of the present invention.

12 is an example diagram showing that an on-duration may be shifted due to a modification of the length of a DRX cycle (eg, drx-ShortCycle, drx-LongCycle) according to an embodiment of the present invention.

13 is a flowchart of a UE receiving an RRC message including a DRX configuration, receiving a first indication and/or a second indication, and adjusting the DRX configuration based on the first indication and/or the second indication according to an embodiment of the present invention.

Figure 14 is a flowchart of a UE receiving a first signaling configuring at least one value of a DRX parameter for a first DRX group, receiving a second signaling indicating a first value or a second value of the DRX parameter in a serving cell, and adjusting the DRX parameters for the first DRX group or the second DRX group according to an embodiment of the present invention.

15 is a flowchart of a UE receiving first signaling configuring at least one value of a DRX parameter for a first DRX group according to an embodiment of the present invention.

FIG. 16 is a diagram showing an example in which a UE may start a drx-onDurationTimer at a timing indicated by an L1/L2 indication according to an embodiment of the present invention.

FIG. 17 is an example diagram showing that a UE may receive an L1/L2 indication for adjusting a DRX parameter (eg, drx-StartOffset, drx-SlotOffset) according to an embodiment of the present invention.

18 is a flowchart of a UE receiving an RRC message including multiple DRX configurations, receiving an indication of one or more DRX configurations, and performing PDCCH monitoring using the one or more DRX configurations according to an embodiment of the present invention.

19 is an example diagram illustrating that a UE may not transmit SRS and/or CSI when an indication is received before a specific timing (eg, a time interval from when the UE receives the indication to symbol n is longer than the duration) according to an embodiment of the present invention.

20 is an example diagram showing that a UE may transmit SRS and/or CSI when an indication is received after a specific timing (eg, a time interval from when the UE receives the indication to symbol n is shorter than the duration) according to an embodiment of the present invention.

Figure 21 is a flowchart of a UE receiving an RRC message including a DRX configuration, receiving an indication of one or more DRX configurations, applying the indication to the one or more DRX configurations to perform PDCCH monitoring, and determining whether to transmit SRS and/or CSI in symbol n based on the indication according to an embodiment of the present invention.

Figure 22 is a flowchart of a UE receiving a first signaling for configuring at least one value of a DRX parameter according to an embodiment of the present invention, receiving a second signaling indicating a first value of the DRX parameter or a second value of the at least one value of the DRX parameter in a serving cell, and performing at least one of the following: adjusting the DRX parameters for the first DRX group or the second DRX group, restarting or starting the drx-onDurationTimer at a timing, stopping the drx-onDurationTimer in response to receiving the second signaling, or stopping the drx-onDruationTimer when or after transmitting a confirmation.

DETAILED DESCRIPTION

The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. In addition, the present invention is mainly described in the context of the 3GPP architecture reference model. However, it should be understood that with the help of the disclosed information, those skilled in the art can easily adapt and use and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by a consortium named “3rd Generation Partnership Project”, referred to herein as 3GPP, including: [1] RP-213587, “Study of XR enhancements for NR”; [2] 3GPP TR 38.838 V17.0.0, “Study of Extended Reality (XR) Evaluation for NR”; [3] 3GPP TS 38.321 V17.0.0, “NR, Medium Access Control (MAC) Protocol Specification”; and [4] 3GPP TS 38.331 V17.0.0, “NR, Radio Resource Control (RRC) Protocol Specification”. The standards and documents listed above are hereby expressly and completely incorporated herein by reference in their entirety.

FIG. 1 shows a multiple access wireless communication system according to an embodiment of the present invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and another including 112 and 114. In FIG. 1, each antenna group shows only two antennas, however, each antenna group may utilize more or fewer antennas. An access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency then that used by reverse link 118 .

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

In communicating via forward links 120 and 126, the transmit antennas of access network 100 utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Additionally, an access network that transmits to access terminals randomly dispersed throughout its coverage area using beamforming causes less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals via a single antenna.

AN may be a fixed station or base station for communicating with a terminal, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other term. AT may also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.

2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted through a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for the data stream to provide modulation symbols. Instructions executed by processor 230 may determine the data rate, coding, and modulation for each data stream. Memory 232 is coupled to processor 230.

The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 220 then provides _NT modulation symbol streams to _NT transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. The _NT modulated signals from transmitters 222a through 222t are then transmitted from _NT antennas 224a through 224t, respectively.

At receiver system 250, the transmitted modulated signals are received by _NR antennas 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

The RX data processor 260 then receives and processes the NR received symbol streams from the _NR receivers 254 based on a particular receiver processing technique to provide _NT "detected" symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for _the data stream. The processing by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may include various types of information about the communication link and/or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives traffic data for a number of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

At the transmitter system 210, the modulated signal from the receiver system 250 is received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

The memory 232 may be used to temporarily store some buffer/calculated data from 240 or 242 via the processor 230, store some buffer data from 212, or store some specific program codes. Also, the memory 272 may be used to temporarily store some buffer/calculated data from 260 via the processor 270, store some buffer data from 236, or store some specific program codes.

Turning to FIG. 3, this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. As shown in FIG. 3, a communication device 300 in a wireless communication system can be used to implement the UE (or AT) 116 and 122 in FIG. 1, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive a signal input by a user through an input device 302 (e.g., a keyboard or a keypad), and can output images and sounds through an output device 304 (e.g., a monitor or a speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signal to the control circuit 306, and wirelessly output the signal generated by the control circuit 306.

FIG4 is a simplified block diagram of the program code 312 shown in FIG3 according to an embodiment of the present invention. In this embodiment, the program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. The layer 3 portion 402 generally performs radio resource control. The layer 2 portion 404 generally performs link control. The layer 1 portion 406 generally performs physical connectivity.

For LTE, LTE-A or NR systems, the layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each invention may be logically, reasonably and appropriately combined to form a specific method.

Any sentence, paragraph, (sub) bullet, key point, action or claim described in each of the following invention paragraphs or sections can be implemented independently and individually to form a specific method or device. The following disclosure of the present invention, such as "based on", "more specifically", "example", etc., is only a possible embodiment that does not limit a specific method or device.

The Release 18 research project for Extended Reality (XR) in NR is described in [1] RP-213587 “Research on XR Enhancements for NR”:

**************** Quote starts [1]****************

3 Reasons

RAN1 Rel-17 study project "Study on XR Evaluation for NR" has shown that Extended Reality (XR) and Cloud Gaming (CG) are considered important use cases and services for NR in Rel-18 and later releases. In general, XR and CG are broad terms referring to various types of augmented, virtual and hybrid environments, where human-machine communication and human-human communication are performed with the assistance of handheld and wearable end-user devices (UE).

- Cloud Gaming (CG) refers to a group of use cases where the vast majority of computations associated with a game (single-player or multi-player) are offloaded from the UE to an edge or remote server.

- Extended Reality (XR) is a broad umbrella for multiple heterogeneous use cases and services studied and outlined in SA1, SA2, and SA4, including but not limited to TR 22.842 and TR 26.928. These XR use cases can be roughly divided into: (i) Augmented Reality (AR); (ii) Virtual Reality (VR), and (iii) Mixed Reality (MR).

While XR and CG present an attractive set of use cases for future mobile systems, they also bring a set of challenges to NR that need to be studied and potentially solved.

Many XR and CG use cases are characterized by quasi-periodic traffic (with possible jitter) with high data rates in the DL (i.e., video streaming) combined with frequent UL (i.e., attitude/control updates) and/or UL video streaming. The DL and UL traffic are also characterized by relatively tight packet delay budgets (PDBs). Therefore, there is a need to study and potentially specify possible solutions that better support such challenging services.

Many end-user XR and CG devices are expected to be mobile and small-scale, and therefore have limited battery power resources. Therefore, additional power enhancements may be needed to reduce overall UE power consumption when running XR and CG services, and thus extend effective UE battery life. It should be appreciated that current DRX configurations are not suitable for (i) non-integer XR traffic periodicity, (ii) variable XR data rates, and (iii) quasi-periodic XR periodicity, and therefore enhancements in this area would be beneficial.

It is expected that the set of XR and CG services has some diversity, and the characteristics of the data streams (i.e., video) may change “on the fly” while the services are running on NR. Therefore, additional information about the running services from higher layers, such as QoS flow association, frame level QoS, ADU-based QoS, XR-specific QoS, etc., may be beneficial to facilitate the selection of informed radio parameters. Obviously, XR application awareness through UE and gNB will improve the user experience, improve NR system capacity in supporting XR services, and reduce UE power consumption. It is expected that the SA working group will lead the work on identifying the necessary enhancements to improve XR awareness, and the RAN will be aware of these enhancement parameters and can potentially adjust the radio processing of XR traffic.

4. Goals

4.1 Objectives of SI or core WI or test WI

The research is based on Release 17 TR 38.838, based on the corresponding Release 17 work from SA4 (according to SP-210043), and based on Release 18 work from SA2 (according to SP-211166).

Regarding the goals of XR perception in RAN (RAN2):

- Study and identify XR service (UL and DL) characteristics, QoS metrics, and application layer attributes that would be useful for the gNB to understand.

- Study how the above information can assist XR-specific business processing.

Regarding XR specific power saving targets (RAN1, RAN2):

-Study XR power saving techniques to adapt to XR service characteristics (periodicity, multiple streams, jitter, latency, reliability, etc...). Focus on the following technologies:

○C-DRX enhancement.

○PDCCH monitoring enhancement.

****************END OF QUOTE*****************

The single-stream and multi-stream DL service models for XR are specified in TS 38.838 (e.g., [2] 3GPP TR 38.838 V17.0.0, “Study on Extended Reality (XR) Evaluation for NR”) as follows:

**************** Quote starts [2]****************

5.1 General DL Business Model

5.1.1 Single-stream DL service model

This clause provides a parameterized generic single-stream DL traffic model. In this model, as shown in Figure 5.1-1, XR DL traffic is modeled as a sequence of video frames arriving at the gNB according to the considered video frame rate and random jitter. The size of each frame is also random according to a certain distribution.

Figure 5 is a reproduction of Figure 5.1.1-1: Single stream DL traffic model from 3GPP TR 38.838 V17.0.0 “Study on Extended Reality (XR) Evaluation for NR”.

5.1.1.1 Packet Size

In this model, a packet models a collection of IP packets belonging to the same video frame. A video frame contains left-eye and right-eye frames sharing the same buffer, which is referred to as 'single stream for both eye buffers' or 'mono-eye buffer' throughout this document.

The size of the packet is determined by the given data rate and frame rate, which are modeled as random variables following a truncated Gaussian distribution with the following statistical parameters.

Table 5.1.1.1-1: Statistical parameters for packet sizes following a truncated Gaussian distribution

[…]

5.1.1.2 Packet Arrival

In this model, the packet arrival rate is determined by the frame generation rate, e.g. 60fps. Therefore, the average packet arrival periodicity is given by the inverse of the frame rate, e.g. 16.6667ms = 1/60fps. Jitter-free periodic arrival gives the arrival time at the gNB for packets with index k (= 1, 2, 3....) as

k/F*1000[ms],

Where F is the given frame generation rate (per second).

It should be noted that this periodic packet arrival implicitly assumes fixed delays contributed from the network side, including fixed video encoding time, fixed network transmission delay, etc.

However, in real systems, varying frame coding delays and network transfer times introduce jitter in the packet arrival times at the gNB. In this model, the jitter is modeled as a random variable added on top of the periodic arrivals. The jitter follows a truncated Gaussian distribution with the following statistical parameters shown in Table 5.1-2.

Table 5.1.1.2-1: Statistical parameters for jitter

It should be noted that the given parameter values and the considered frame generation rate (60 or 120 in this model) ensure that the packet arrivals are in order (ie, the arrival time of the next packet is always greater than the arrival time of the previous packet).

Therefore, periodic arrival with jitter gives the arrival time of the packet with index k (=1, 2, 3....) as

Offset + k/F*1000 + J [ms],

Where F is the given frame generation rate (per second) and J is a random variable that captures jitter. It should be noted that the actual traffic arrival timing of traffic for each UE may be shifted by an arbitrary offset that is UE specific.

5.1.1.3 Packet Delay Budget

The latency requirement of XR services in the RAN side (i.e., air interface) is modeled as a Packet Delay Budget (PDB). The PDB is a finite time budget for a packet to stay in the air for transmission from the gNB to the UE.

For a given packet, the delay of the packet induced in the air interface is measured from the time the packet arrives at the gNB to the time the packet is successfully delivered to the UE. If the delay is greater than the given PDB for the packet, then the packet is said to violate the PDB, otherwise the packet is said to be successfully delivered.

The value of PDB may vary for different applications and business types.

[…]

5.1.2 Multi-stream DL service model

This clause provides an optional multi-stream model for XR DL services.

-Option 1: I frame + P frame

- Option 1A: Slice-based business model

- Option 1B: Group of Pictures (GOP) based service model

- Option 2: Video + Audio/Data

-Option 3: FOV + Omnidirectional Flow

5.1.2.1 Option 1 (I+P)

For Option 1, two flows (I flow and P flow) are modeled according to Table 5.1-5.

- Stream 1: I stream

- Stream 2: P stream

Depending on the video coding scheme, two additional sub-models are defined: a slice-based model, and a group of pictures (GOP)-based model.

- Slice-based: In this coding scheme, a single video frame is divided into N slices. Of these N, one slice is an I slice and the remaining N-1 slices are P slices. N packets (one I and N-1 P) packets correspond to one video frame arriving at the same time.

- GOP-based: In this coding scheme, a single video frame is either an I-frame or a P-frame. I-frames are transmitted every K frames, where K is the GOP size, i.e., each group of pictures. One video frame arrives as a packet at a time.

Table 5.1.2.1-1: Statistical parameters for Option 1 multi-stream DL traffic model

5.1.2.2 Option 2 (Video + Audio/Data)

For option 2, two streams (video + audio/data) are modeled.

- Stream 1: Video

- Stream 2: Audio/Data

Stream 1 - Video stream follows the general single stream model given in clause 5.1.1. Stream 2 - Audio/Data Periodic service with the following parameters.

Table 5.1.2.2-1: Statistical parameter values for Option 2 multi-stream model

parameter unit Baseline value for evaluation Optional value for evaluation Periodic P ms 10 Data rate: R Mbps 0.756, 1.12 Packet size byte R×1e6×P/1000/8 PDB ms 30 Other values may optionally be evaluated Packet success rate % 99 99.9

5.1.2.3 Option 3 (FOV + Omnidirectional View)

For option 3, model the following two flows.

- Stream 1: FOV

- Stream 2: Omnidirectional view stream

****************END OF QUOTE*****************

Discontinuous Reception (DRX) is specified in TS 38.321 (e.g., [3] 3GPP TS 38.321 V17.0.0, “NR, Medium Access Control (MAC) Protocol Specification”) as follows:

**************** Quote starts [3]****************

5.7 Discontinuous Reception (DRX)

The MAC entity may be configured by RRC with DRX functionality, wherein the DRX functionality controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI and SL semi-persistent scheduling V-RNTI. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements present in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, then for all activated serving cells, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this section; otherwise, the MAC entity shall monitor the PDCCH as specified in TS 38.213 [6].

RRC controls DRX operation by configuring the following parameters:

-drx-onDurationTimer: duration when the DRX cycle starts;

-drx-SlotOffset: Delay before starting drx-onDurationTimer;

-drx-InactivityTimer: duration after the PDCCH opportunity where the PDCCH indicates a new UL or DL transmission by the MAC entity;

-drx-RetransmissionTimerDL (per DL HARQ process, except broadcast process): maximum duration until a DL retransmission is received;

-drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a grant for UL retransmission is received;

-drx-LongCycleStartOffset: long DRX cycle and drx-StartOffset of the subframe that defines the start of the long and short DRX cycles;

-drx-ShortCycle (optional): short DRX cycle;

-drx-ShortCycleTimer (optional): duration of the short DRX cycle that the UE will follow;

-drx-HARQ-RTT-TimerDL (per DL HARQ process, except broadcast process): minimum duration before the MAC entity expects a DL assignment of a HARQ retransmission;

-drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before the MAC entity expects a UL HARQ retransmission grant;

-drx-RetransmissionTimerSL (per SL HARQ process): maximum duration until a grant for SL retransmission is received;

-drx-HARQ-RTT-TimerSL (per SL HARQ process): minimum duration before the MAC entity expects a SL retransmission grant;

-ps-Wakeup (optional): Starts the configuration of the associated drx-onDurationTimer when a DCP is monitored but not detected;

-ps-TransmitOtherPeriodicCSI (optional): configuration to report periodic CSI other than L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer is not started;

-ps-TransmitPeriodicL1-RSRP (optional): configuration to transmit periodic CSI for L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer is not started;

-uplinkHARQ-Mode (optional): sets the configuration of the HARQ mode per UL HARQ process.

The service cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all service cells belong to the one DRX group. When two DRX groups are configured, each service cell is uniquely assigned to either of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX groups are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL and uplinkHARQ-Mode (optional).

When DRX is configured, the action time for the serving cells in the DRX group includes the following times:

- the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

-drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on any serving cell in the DRX group; or

-ra-ContentionResolutionTimer (as described in clause 5.1.5) or msgB-ResponseWindow (as described in clause 5.1.4a) is running; or

- A Scheduling Request is sent on PUCCH and is pending (as described in clauses 5.4.4 or 5.22.15). If this serving cell is part of a non-terrestrial network, then the action time starts after the first Scheduling Request transmission plus the UE-gNB RTT; or

- No new transmitted PDCCH indicating a C-RNTI addressed to the MAC entity is received after successful reception of a random access response for a random access preamble that was not selected by the MAC entity among contention-based random access preambles (as described in clauses 5.1.4 and 5.1.4a).

When DRX is configured, the MAC entity shall:

1> If a MAC PDU is received in a configured downlink assignment, then:

2> Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends;

[…]

2> Stop the drx-RetransmissionTimerDL corresponding to the HARQ process.

1> If a MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from lower layers:

2> If the serving cell is not configured with uplinkHARQ-Mode; or

2> If the serving cell is configured with uplinkHARQ-Mode and the corresponding HARQ process is configured as HARQ mode A, then:

3> Start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process in the first symbol after the first transmission (within the cluster) of the corresponding PUSCH transmission ends;

2> Stop the drx-RetransmissionTimerUL of the corresponding HARQ process at the first transmission (within the bundle) of the corresponding PUSCH transmission.

1> If drx-HARQ-RTT-TimerDL expires:

2> If the data corresponding to the HARQ process is not successfully decoded:

3> Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

1> If drx-HARQ-RTT-TimerUL expires:

2> Start the drx-RetransmissionTimerUL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerUL expires.

1> If drx-HARQ-RTT-TimerSL expires:

2> if HARQ NACK feedback for the corresponding HARQ process is transmitted on PUCCH; or

2> If HARQ NACK feedback for the corresponding HARQ process is not transmitted on PUCCH due to UL/SL prioritization:

3> Start the drx-RetransmissionTimerSL for the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerSL expires.

2> Otherwise, if PUCCH resources are not configured and PSFCH is configured for SL grant, then:

3> Start the drx-RetransmissionTimerSL for the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerSL expires.

NOTE 1c: When sl-PUCCH-Config is configured by RRC, the UE handles drx-RetransmissionTimerSL operation, but when sl-PUCCH-Config is not configured, PUCCH resources are not scheduled in the same way.

1> If a DRX command MAC CE or a long DRX command MAC CE is received:

2> Stop drx-onDurationTimer for each DRX group;

2> Stop the drx-InactivityTimer for each DRX group.

1> If the drx-InactivityTimer for the DRX group expires:

2> If short DRX cycle is configured:

3> Start or restart the drx-ShortCycleTimer for this DRX group in the first symbol after expiration of the drx-InactivityTimer;

3> Use short DRX cycle for this DRX group.

2> Otherwise:

3> Use long DRX cycle for this DRX group.

1> If DRX command MAC CE is received:

2> If short DRX cycle is configured:

3> Start or restart the drx-ShortCycleTimer for each DRX group in the first symbol after the end of DRX command MAC CE reception;

3> Use short DRX cycle for each DRX group.

2> Otherwise:

3> Use a long DRX cycle for each DRX group.

1> If the drx-ShortCycleTimer for the DRX group expires:

2> Use long DRX cycle for this DRX group.

1> If a long DRX command MAC CE is received:

2> Stop the drx-ShortCycleTimer for each DRX group;

2> Use a long DRX cycle for each DRX group.

1> If a short DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle):

2> Start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

1> If a long DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset:

2> If DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6] clause 10.3:

3> if a DCP indication is received from lower layers indicating to start the drx-onDurationTimer associated with the current DRX cycle, as specified in TS 38.213 [6]; or

3> If all DCP opportunities in the time domain associated with the current DRX cycle occur in the active time as specified in TS 38.213 [6], consider the Grant/Assignment/DRX Command MAC CE/Long DRX Command MAC CE received and the Scheduling Request sent 4 ms before the start of the last DCP opportunity, or during a Measurement Gap, or when the MAC entity monitors PDCCH transmissions on the search space indicated by recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is in operation (as specified in clause 5.1.4); or

3> If ps-Wakeup is configured with a value of true and no DCP indication associated with the current DRX cycle is received from lower layers:

4> Start drx-onDurationTimer after drx-SlotOffset from the start of the subframe.

2> Otherwise:

3> Start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

NOTE 2: In case of unaligned SFN across carriers in a cell group, the SFN of the SpCell is used to calculate the DRX duration.

1> If the DRX group is in the active time:

2> monitor the PDCCH on the serving cells in this DRX group as specified in TS 38.213 [6];

2> if PDCCH indicates DL transmission; or

2> if the PDCCH indicates single HARQ feedback, as specified in clause 9.1.4 of TS 38.213 [6]; or

2> If the PDCCH indicates retransmission of HARQ feedback, as specified in clause 9.1.5 of TS 38.213 [6]:

3> after the corresponding transmission carrying DL HARQ feedback ends, start or restart the drx-HARQ-RTT-TimerDL for the corresponding HARQ process, the HARQ feedback report of which is in the first symbol;

NOTE 3: When HARQ feedback is deferred by PDSCH to HARQ feedback timing indicating that k1 value is not applicable, as specified in TS 38.213 [6], the corresponding transmission opportunity for sending DL HARQ feedback is indicated in a later PDCCH requesting HARQ-ACK feedback.

3> Stop the drx-RetransmissionTimerDL for the corresponding HARQ process, where the HARQ feedback of the HARQ process is reported.

3> If the PDSCH to HARQ feedback timing indicates that the k1 value is not applicable, as specified in TS 38.213 [6]:

4> Start drx-RetransmissionTimerDL in the first symbol after (the end of) the (last) PDSCH transmission (in the bundle) for the corresponding HARQ process.

2> If PDCCH indicates UL transmission:

3> If the serving cell is not configured with uplinkHARQ-Mode; or

3> If the serving cell is configured with uplinkHARQ-Mode and the corresponding HARQ process is configured as HARQ mode A, then:

4> Start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process in the first symbol after the first transmission (in the cluster) of the corresponding PUSCH transmission ends;

3> Stop the drx-RetransmissionTimerUL corresponding to the HARQ process.

2> If PDCCH indicates SL transmission:

3> If PUCCH resources are configured, then:

4> starting the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH transmission carrying the SL HARQ feedback ends; or

4> When PUCCH is not transmitted due to UL/SL prioritization, drx-HARQ-RTT-TimerSL for the corresponding HARQ process is started in the first symbol after the end of the corresponding PSFCH resource for SL HARQ feedback;

4> Stop the drx-RetransmissionTimerSL corresponding to the HARQ process.

3> Otherwise:

4> After the PDCCH event ends, start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol;

4> Stop the drx-RetransmissionTimerSL corresponding to the HARQ process.

2> If PDCCH indicates a new transmission (DL, UL or SL) on a serving cell in this DRX group:

3> Start or restart the drx-InactivityTimer for this DRX group in the first symbol after the end of PDCCH reception.

NOTE 3a: A PDCCH indicating activation of SPS, a configured grant type 2, or a configured sidelink grant of configured grant type 2 is considered to indicate a new transmission.

NOTE 3b: If a PDCCH reception contains two PDCCH candidates from the corresponding search space, as described in clause 10.1 in 38.213, then the drx-InactivityTimer for this DRX group is started or restarted in the first symbol after the later ending PDCCH candidate ends.

2> If the HARQ process receives downlink feedback information and indicates confirmation:

3> Stop the drx-RetransmissionTimerUL corresponding to the HARQ process.

1> if DCP monitoring is configured for the active DL BWP as specified in clause 10.3 of TS 38.213 [6]; and

1> If the current symbol n occurs within the duration of drx-onDurationTimer; and

1> If the drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:

2> If, while evaluating all DRX action time conditions specified in this clause, the MAC entity will not be in action time, taking into account the Grant/Assignment/DRX Command MAC CE/Long DRX Command MAC CE received 4 ms before symbol n and the Scheduling Request sent, then:

3> Periodic SRS and semi-persistent SRS are not transmitted, as defined in TS 38.214 [7];

3> Do not report the semi-persistent CSI configured on PUSCH;

3> If ps-TransmitPeriodicL1-RSRP is not configured with a value of true:

4> Periodic CSI as L1-RSRP on PUCCH is not reported.

3> If ps-TransmitOtherPeriodicCSI is not configured with a value of true:

4> Do not report periodic CSI other than L1-RSRP on PUCCH.

1> Otherwise:

2> In the current symbol n, if, when evaluating all DRX action time conditions specified in this clause, the grant/assignment and DRX command MAC CE/long DRX command MAC CE scheduled on the serving cells in this DRX group received 4 ms before symbol n and the scheduling request sent, the DRX group shall not be in action time; and

2> In the current symbol n, if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or when evaluating all DRX action time conditions specified in clause 5.7b, taking into account the multicast allocation and DRX command MAC CE for MBS multicast received 4 ms before symbol n, all multicast DRX will not be in action time, then:

3> Periodic SRS and semi-persistent SRS defined in TS 38.214 [7] are not transmitted in this DRX group;

3> CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group are not reported.

2> If CSI mask (csi-Mask) is set by the upper layer, then:

3> In the current symbol n, if, in evaluating all DRX action time conditions specified in this clause, the grant/assignment and DRX command MAC CE/long DRX command MAC CE scheduled on the serving cell in this DRX group received 4 ms before symbol n are taken into account, the drx-onDurationTimer of the DRX group shall not be running; and

4> CSI on PUCCH is not reported in this DRX group.

NOTE 4: If the UE multiplexes CSI configured on PUCCH with other overlapping UCI according to the procedure specified in clause 9.2.5 of TS 38.213 [6], and this CSI multiplexed with other UCI is to be reported on PUCCH resources outside the DRX action time of the DRX group in which this PUCCH is configured or outside the On Duration period of the DRX group in which this PUCCH is configured if CSI masking is set by upper layers, it is up to the UE implementation to decide whether to report this CSI multiplexed with other UCI.

Regardless of whether the MAC entity monitors the PDCCH on the serving cells in the DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on the PUSCH, and aperiodic SRS as defined in TS 38.214 [7] on the serving cells in the DRX group in anticipation of this situation.

If the PDCCH opportunity is incomplete (eg, the active time starts or ends in the middle of a PDCCH opportunity), then the MAC entity does not need to monitor the PDCCH.

****************END OF QUOTE*****************

The configuration of DRX is specified in TS 38.331 (e.g., [4] 3GPP TS 38.331 V17.0.0, “NR, Radio Resource Control (RRC) Protocol Specification”) as follows:

**************** Quote starts [4]****************

-DRX-Config

IEDRX-Config is used to configure DRX related parameters.

DRX-Config Information Elements

-DRX-ConfigSecondaryGroup

IEDRX-ConfigSecondaryGroup is used to configure DRX related parameters for the second DRX group, as specified in TS38.321 [3].

DRX-ConfigSecondaryGroup Information Element

****************Next Quote*****************

-MAC-CellGroupConfig IEMAC-CellGroupConfig is used to configure the MAC parameters of the cell group, including DRX. MAC-CellGroupConfig information element

****************END OF QUOTE*****************

The activation/deactivation of SRS and CSI reporting is specified in TS 38.321 (e.g., [3] 3GPP TS 38.321 V17.0.0, “NR, Medium Access Control (MAC) Protocol Specification”) as follows:

**************** Quote starts [3]****************

5.18.6 Activation/deactivation of semi-persistent CSI reporting on PUCCH

The network may activate and deactivate configured semi-persistent CSI reporting on the PUCCH of the serving cell by sending SPCSI reports on the PUCCH activation/deactivation MAC CE described in clause 6.1.3.16. Configured semi-persistent CSI reporting on PUCCH is initially deactivated after (re)configuration by upper layers and after reconfiguration with synchronization.

The MAC entity will:

1> If the MAC entity receives the SP CSI report on the PUCCH activation/deactivation MAC CE on the serving cell:

2> Indicates to lower layers information about PUCCH activation/deactivation of SP CSI reporting on MAC CE.

5.18.7 Activation/deactivation of semi-persistent SRS and indication of spatial relationship of SP/AP SRS

The network may activate and deactivate the configured semi-persistent SRS resource set of the serving cell by sending the SP SRS Activation/Deactivation MAC CE described in clause 6.1.3.17. The network may also activate and deactivate the configured semi-persistent SRS resource set of the serving cell by sending the Enhanced SP/AP SRS Spatial Relationship Indication MAC CE described in clause 6.1.3.26. The configured semi-persistent SRS resource set is initially deactivated after (re)configuration by upper layers and after reconfiguration with synchronization. The network may indicate the spatial relationship information of the SP/AP SRS resource set of the serving cell by sending the Enhanced SP/AP SRS Spatial Relationship Indication MAC CE described in clause 6.1.3.26.

The MAC entity will:

1> If the MAC entity receives the SP SRS activation/deactivation MAC CE on the serving cell, then:

2> Indicates information about SP SRS activation/deactivation MAC CE to lower layers.

1> If the MAC entity receives an enhanced SP/AP SRS spatial relationship indication MAC CE on the serving cell, then:

2>Indicates information about the enhanced SP/AP SRS spatial relationship indication MAC CE to the lower layer.

****************END OF QUOTE*****************

Extended reality (XR) includes different types of reality (e.g., augmented reality (AR), mixed reality (MR), virtual reality (VR), and areas interpolated therein). XR may refer to all real and virtual combined environments and human-computer interactions generated by computer technology and wearables. XR services and/or technologies can be applied in various aspects, such as entertainment, simulation, product design, real estate, training, education, and/or remote work. In applications, XR will have quasi-periodic traffic (with possible jitter) with high data rates in the downlink (DL) (e.g., video streaming) and frequent traffic in the uplink (UL) (e.g., gesture/control updates). XR traffic will have strict packet delay budgets (PDBs) and variable XR data rates. In order to better support such XR services in new radio (NR), a research project for XR is introduced ([1] RP-213587, “Research on XR Enhancements for NR”). For more details on XR, see TR 38.838 ([2] 3GPP TR 38.838 V17.0.0, “Study on evaluation of extended reality (XR) for NR”).

In addition, user equipment (UE) for XR is expected to be mobile and small-scale, which may have limited battery power resources. It may be necessary to reduce the overall UE power consumption when running XR services and thereby extend the battery life of the UE. Based on system information (SI) ([1] RP-213587) and TR ([2] 3GPP TR 38.838 V17.0.0), in order to adapt to XR service characteristics (e.g., periodicity, multiple streams, jitter, latency, reliability), enhancements to the physical downlink control channel (PDCCH) monitoring and/or (C-) discontinuous reception (DRX) mechanism may be required. In order to reduce PDCCH monitoring and thereby reduce power consumption for XR services, it may be necessary to appropriately align the on-duration and/or DRX cycle with the XR DL service arrival time (e.g., with jitter).

On the other hand, based on [3] 3GPP TS 38.321 V17.0.0, the network (NW) may configure one or two DRX groups for the UE. The service cells of the media access control (MAC) entity may be configured in one or two DRX groups. When two DRX groups are configured, each service cell of the MAC entity is configured/assigned to either of the two groups. The UE may receive a DRX configuration related to the on-duration (time), DRX cycle, inactive time and/or retransmission time. If the UE is configured with DRX functionality, the UE monitors the PDCCH discontinuously using DRX operation in radio resource control (RRC) connected mode.

The DRX configuration for the on-duration (time) (e.g., for a DRX group) may be and/or may include a length/duration of the on-duration (e.g., drx-onDurationTimer) and/or a start offset to the on-duration (e.g., drx-SlotOffset). The length/duration of the on-duration (e.g., drx-onDurationTimer) may be (represented by and/or referred to by) an on-duration timer. The start offset to the on-duration (e.g., drx-SlotOffset) may be applied to the start of the on-duration timer (e.g., drx-onDurationTimer). The UE may start the on-duration timer (e.g., drx-onDurationTimer) after the start offset to the on-duration (e.g., drx-SlotOffset) for each DRX cycle. The UE may start the on-duration timer (e.g., drx-onDurationTimer) after the start offset to the on-duration (e.g., drx-SlotOffset) from the start of a subframe of the DRX cycle. The UE may monitor the PDCCH when an on-duration timer (e.g., drx-onDurationTimer) is running. The on-duration may be the duration when the on-duration timer (e.g., drx-onDurationTimer) is running. Throughout this disclosure, "on-duration" may be referred to, supplemented and/or replaced by "on-duration", "DRX on-duration" and/or "on-duration cycle".

The DRX configuration for a DRX cycle (e.g., for a DRX group) may be and/or may include the length/duration of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle), the start offset of the DRX cycle (e.g., drx-StartOffset), and/or the duration of using a short DRX cycle (e.g., drx-ShortCycleTimer). The duration of using a short DRX cycle (e.g., drx-ShortCycleTimer) may be (represented by and/or referred to by) a short cycle timer. The UE may use a short DRX cycle when a short cycle timer (e.g., drx-ShortCycleTimer) is running. The UE may use a long DRX cycle when a short cycle timer (e.g., drx-ShortCycleTimer) is not running. The UE may use a long DRX cycle when a short cycle timer (e.g., drx-ShortCycleTimer) is not configured. The UE may determine the DRX cycle based on a formula using the length/duration of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) and the start offset of the DRX cycle (e.g., drx-StartOffset). The start of the DRX cycle may be a subframe determined by a predefined formula. drx-LongCycleStartOffset may include the length of the long cycle (e.g., drx-LongCycle) and the start offset of the (long and/or short) DRX cycle (e.g., drx-StartOffset). The length of the long DRX cycle (e.g., drx-LongCycle) and/or the start offset of the (long and/or short) DRX cycle (e.g., drx-StartOffset) may be or may be included in drx-LongCycleStartOffset. Throughout this disclosure, a "DRX cycle" may include and/or be referred to as a "short DRX cycle" and/or a "long DRX cycle".

The DRX configuration for the inactivity time (e.g., for a DRX group) may be and/or may include the length/duration of the inactivity time (e.g., drx-InactivityTimer). The length/duration of the inactivity time (e.g., drx-InactivityTimer) may be (represented by and/or referred to by) an inactivity timer. The UE may start or restart the inactivity timer (e.g., drx-InactivityTimer) when the PDCCH indicates a new transmission. The UE may monitor the PDCCH when the inactivity timer (e.g., drx-InactivityTimer) is in operation. The inactivity time may be the duration when the inactivity timer (e.g., drx-InactivityTimer) is in operation.

The DRX configuration for the retransmission time (e.g., for the DRX group) may be and/or may include the length/duration of the round trip time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) and/or the length/duration of the retransmission time (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL). HARQ = Hybrid Automatic Repeat Request; RTT = Round Trip Time. The length/duration of the round trip time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) may be (represented by and/or referred to as) an RTT timer. The length/duration of the retransmission time (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) may be (represented by and/or referred to as) a retransmission timer. The UE may start an RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) when indicating (or performing) transmission. The UE may start a retransmission timer (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) after the RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) expires. The UE may monitor the PDCCH when the retransmission timer (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) is running. The retransmission time may be the duration when the retransmission timer (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) is running.

Throughout the present disclosure, a DRX configuration may be, may refer to and/or may include the above-mentioned (DRX) configuration, (DRX) parameters and/or (DRX) timers, for example, drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, and/or drx-RetransmissionTimerUL. Throughout the present disclosure, a DRX configuration may be and/or be referred to as a DRX group (configuration), for example, DRX-Config, DRX-ConfigSecondaryGroup and/or information elements of a DRX configuration.

Based on the NR MAC specification (e.g., [3] 3GPP TS 38.321 V17.0.0), the UE will monitor the PDCCH discontinuously based on the DRX cycle and the on-duration. The UE will enter the on-duration of each DRX cycle. The UE will monitor the PDCCH regularly for a certain time period based on the DRX configuration for the on-duration and the DRX cycle. The UE can use the length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) and the start offset of the DRX cycle (e.g., drx-StartOffset) to determine the subframe to start the DRX cycle based on a formula. As shown in Figure 6, for each DRX cycle (e.g., the first DRX cycle, the second DRX cycle), the UE can start the on-duration timer (e.g., drx-onDurationTimer) after the start offset (e.g., drx-SlotOffset) to the on-duration. The UE can enter the on-duration when the on-duration timer (e.g., drx-onDurationTimer) is running. The UE shall monitor the PDCCH during the OnDuration of each DRX cycle.The UE shall not monitor the PDCCH during the duration other than the OnDuration of each DRX cycle.

Throughout this disclosure, the following words may be interchangeable: modify, adjust, switch, reconfigure and/or change.

Indications (e.g., L1/L2 indications) may be used to change, reconfigure and/or (de)activate DRX parameters. Indications may be transmitted from the NW to the UE. The UE may change, reconfigure and/or (de)activate DRX parameters in response to receiving the indication. The UE may be (pre)configured with multiple DRX configurations (e.g., for DRX parameters) via RRC messages. When the UE receives a (L1/L2) indication, it is not yet clear how the UE determines in which DRX group the DRX parameters are to be modified, reconfigured or (de)activated.

In addition, it is possible that the DRX timer associated with the DRX parameter is running when the UE receives the (L1/L2) indication for the DRX parameter. As shown in Figure 16, the UE may receive an (L1/L2) indication that changes the offset (e.g., drx-StartOffset or drx-SlotOffset) to delay the on-duration, for example, due to jitter (-4 to +4 ms) of the XR service. In response to receiving the (L1/L2) indication, it is not yet clear how to handle the running drx-onDurationTimer that should be defined.

To resolve the problem, the UE may receive a first indication to modify/adjust/reconfigure the DRX configuration (e.g., for a specific/indicated DRX group). The first indication is not an RRC message, for example, an RRC reconfiguration message (e.g., RRCReconfiguration). The first indication may be L1 and/or L2 signaling/indication (e.g., downlink control information (DCI), MAC CE). The UE may receive one or more DRX configurations in an RRC message (e.g., RRCSetup, RRCResume, or RRCReconfiguration). The first indication may indicate a value of a preconfigured DRX configuration or a DRX parameter.

The first indication may be applied to one or more DRX groups. The first indication may indicate which DRX group (e.g., an index of a DRX group) is to be applied. The UE may reconfigure and/or adjust one or more DRX configurations based on the first indication (e.g., for a specific/indicated DRX group). The UE may reconfigure and/or adjust some DRX configurations (e.g., a first DRX configuration) but may not reconfigure and/or adjust some other DRX configurations (e.g., a second DRX configuration). The DRX configuration (e.g., a first DRX configuration, a second DRX configuration) may be (or include) drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle, and/or drx-ShortCycleTimer. In response to receiving the first indication, the UE may reconfigure and/or adjust the on-duration and/or DRX cycle (e.g., for a specific/indicated DRX group). In response to receiving the first indication, the UE may reconfigure and/or adjust values of parameters related to the on-duration and/or DRX cycle (e.g., for a specific/indicated DRX group). In response to receiving the first indication, the UE may reconfigure and/or adjust a start offset to the on-duration (e.g., drx-SlotOffset), a length of the on-duration (e.g., drx-onDurationTimer), a length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle (of drx-LongCycleStartOffset), a start offset of the DRX cycle (e.g., drx-StartOffset (of drx-LongCycleStartOffset), and/or a duration of using a short DRX cycle (e.g., drx-ShortCycleTimer).

The first indication may not be allowed/used to modify/adjust/reconfigure an inactivity timer (e.g., drx-InactivityTimer), a retransmission timer (e.g., drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL), and/or an RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL).

The UE may use the reconfigured/adjusted value of the DRX configuration, for example based on the first indication, until the DRX configuration is released and/or reconfigured/adjusted.

The UE may receive a first value for the DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may receive a second value for the DRX configuration in a first indication, for example, after receiving the first value for the DRX configuration. The first indication may include and/or indicate one or more values of the DRX configuration. The UE may use the received/indicated value as the DRX configuration. The UE may replace the value of the DRX configuration with the received/indicated value.

For example, the UE may receive a first value for the DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may receive a second value for the DRX configuration in a first indication. In response to receiving the first indication, the UE may reconfigure the DRX configuration with the second value. The UE may replace the first value with the second value for the DRX configuration. The DRX configuration may be and/or referred to as drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle, and/or drx-ShortCycleTimer.

For example, the UE may receive a first value for a first DRX configuration and a second value for a second DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may receive a third value for the first DRX configuration and a fourth value for the second DRX configuration in a first indication. In response to receiving the first indication, the UE may reconfigure the first DRX configuration with the third value and reconfigure the second DRX configuration with the fourth value. The UE may replace the first value with the third value for the first DRX configuration and replace the second value with the fourth value for the second DRX configuration. The first DRX configuration may be and/or be referred to as drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle, and/or drx-ShortCycleTimer. The second DRX configuration may be and/or be referred to as drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle, drx-ShortCycleTimer. The first DRX configuration and the second DRX configuration may be different.

The UE may receive a first value for a DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may receive an offset (e.g., a relative value) and/or a scale for the DRX configuration in a first indication, for example, after receiving the first value for the DRX configuration. The first indication may include and/or indicate a relative value (e.g., an offset and/or a scale) to be applied to one or more DRX configurations. The UE may apply the relative value (e.g., an offset) and/or a scale to the DRX configuration. The UE may add the relative value (e.g., an offset) to the first value of the DRX configuration. The UE may multiply the first value of the DRX configuration by the scale.

For example, the UE may receive a first value for the DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may receive an offset for the DRX configuration in a first indication. In response to receiving the first indication, the UE may add the offset to the first value for the DRX configuration. The UE may reconfigure the DRX configuration with the first value plus the offset. The UE may replace the first value with the first value for the DRX configuration plus the offset. The UE may receive a scale for the DRX configuration in the first indication. In response to receiving the first indication, the UE may multiply the first value by the scale for the DRX configuration. The UE may reconfigure the DRX configuration with the first value multiplied by the scale. The UE may replace the first value with the first value for the DRX configuration multiplied by the scale. The DRX configuration may be and/or referred to as drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle, and/or drx-ShortCycleTimer.

For example, the UE may receive a first value for a first DRX configuration and a second value for a second DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may receive a first offset and a second offset in a first indication. In response to receiving the first indication, the UE may add the first offset to the first value for the first DRX configuration and add the second offset to the second value for the second RRC configuration. The UE may reconfigure the first DRX configuration with the first value plus the first offset and reconfigure the second DRX configuration with the second value plus the second offset. The UE may replace the first value with the first value for the first DRX configuration plus the first offset and replace the second value with the second value for the second DRX configuration plus the second offset. The UE may receive a first scale and a second scale in the first indication. In response to receiving the first indication, the UE may multiply the first value by the first scale for the first DRX configuration and multiply the second value by the second scale for the second DRX configuration. The UE may reconfigure the first DRX configuration by multiplying the first value by the first scale and reconfigure the second DRX configuration by multiplying the second value by the second scale. The UE may replace the first value with the first value for the first DRX configuration multiplied by the first scale, and replace the second value with the second value for the second DRX configuration multiplied by the second scale. The UE may receive the offset and the scale in the first indication. In response to receiving the first indication, the UE may add the offset to the first value for the first DRX configuration and multiply the second value by the scale for the second DRX configuration. The UE may reconfigure the first DRX configuration with the first value plus the offset, and reconfigure the second DRX configuration with the second value multiplied by the scale. The UE may replace the first value with the first value for the first DRX configuration plus the offset, and replace the second value with the second value for the second DRX configuration multiplied by the second scale. The first DRX configuration may be and/or be referred to as drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle, and/or drx-ShortCycleTimer. The second DRX configuration may be and/or be referred to as drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-ShortCycle, drx-LongCycle and/or drx-ShortCycleTimer. The first DRX configuration and the second DRX configuration may be different.

To solve the problem, the UE may receive a second indication to (dynamically/temporarily) modify/shift/adjust the DRX configuration. The second indication is not an RRC message, for example, an RRC reconfiguration message (e.g., RRCReconfiguration). The second indication may be L1 and/or L2 signaling/indication (e.g., DCI, MAC CE). The UE may receive the DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may shift/adjust one or more DRX configurations, for example, as indicated by the second indication. In response to receiving the second indication, the UE may apply the information indicated/included by the second indication to the DRX configuration. In response to receiving the second indication, the UE may shift/adjust (part of) the on-duration and/or the DRX cycle (based on the information indicated/included by the second indication). In response to receiving the second indication, the UE may shift/adjust the values of parameters related to the on-duration and/or the DRX cycle (based on the information indicated/included by the second indication). In response to receiving the second indication, the UE may shift/adjust the start offset of the on-duration (e.g., drx-SlotOffset), the length of the on-duration (e.g., drx-onDurationTimer), the start offset of the DRX cycle (e.g., drx-StartOffset), the length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) and/or the duration of using a short DRX cycle (e.g., drx-ShortCycleTimer) (based on the information indicated/included by the second indication).

The second indication may not be allowed/used to modify/shift/adjust an inactivity timer (e.g., drx-InactivityTimer), a retransmission timer (e.g., drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL), and/or an RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL).

The second indication may indicate an offset (e.g., a relative value) and/or a scale to be (temporarily) applied. The second indication may indicate one or more offsets/scales and/or an indication of (a set of) preconfigured offsets/scales. The second indication may indicate a value to be used as a value for the DRX configuration (e.g., to (temporarily) replace a value for the DRX configuration). The second indication may instruct the UE to suspend and/or resume a timer, e.g., drx-onDurationTimer. The second indication may indicate which DRX configuration(s) and/or DRX group (e.g., an index of a DRX group) will (temporarily) apply the second indication (e.g., DRX group number, DRX configuration, DRX parameter).

The second indication may indicate a duration (e.g., amount/on-duration of DRX cycles, timer, specific time/timing) for which the second indication is to be applied. The second indication may be applied/used (several times) during the duration (e.g., for the on-duration and/or DRX cycle in the duration). The second indication may not be applied/used during the duration. (Each of) the second indication may be applied/used (only) once (e.g., for a single/specific on-duration and/or DRX cycle). The second indication may indicate a time delay (e.g., amount/on-duration of DRX cycles, timer, specific time/timing) for which the second indication is to be applied. Alternatively, the duration and/or time delay may be configured by the network, e.g., via an RRC message (for configuring the DRX configuration), before receiving the second indication.

The value of the DRX configuration before receiving the second indication to adjust the DRX configuration may be restored/used after an applicable time of the second indication, for example after a duration or after a single/specific on-duration and/or DRX cycle.

The second indication may include and/or indicate (at least one of) the following information (for one or more DRX configurations):

- offset;

-scale;

- (absolute) value to DRX configuration;

- an indication of a preconfigured configuration (e.g., offset, scale, value to DRX configuration, timer value and/or duration);

- an indication to suspend and/or resume the DRX timer;

- indication of DRX configuration and/or DRX group; and/or

- the applicability duration of the second indication (e.g., the time period during which the information indicated in the second indication will be applied), for example:

- Amount of DRX cycles, on-duration, DL transmissions and/or PDCCH opportunities;

- the value of the timer;

- indicated/specific PDCCH occasions; and/or

-Time delay/duration (e.g. in milliseconds).

The second indication may include/indicate an offset (as a relative value to the DRX configuration). The UE may add the offset to the DRX configuration. The UE may use the modified DRX configuration for a certain time period. The second indication may include/indicate a number of offsets (e.g., a list of offsets). The UE may sequentially add the offset to the DRX configuration and use the modified DRX configuration for a certain time period. The offset may be a value in milliseconds, time slots, and/or integers. The offset may be greater than zero or less than zero.

The second indication may include/indicate a scale. The UE may multiply the DRX configuration (value) by a scale. The UE may use the modified DRX configuration for a certain time period. The second indication may include/indicate a number of scales (e.g., a list/set of scales). The UE may sequentially multiply the DRX configuration (value) by a scale and use the modified DRX configuration for a certain time period. The scale may be an integer. The scale may be a value less than one (e.g., between zero and one), greater than one (e.g., between one and two), or zero.

The second indication may include/indicate a value to the DRX configuration (e.g., an absolute value to the DRX configuration). The UE may apply/use the value as (the value of) the DRX configuration. The UE may use the modified DRX configuration for a certain time period. The second indication may include/indicate a number of values (e.g., a list/set of values). The UE may sequentially use the value as (the value of) the DRX configuration and use the modified DRX configuration for a certain time period.

The second indication may indicate one or more offsets, scales and/or values from a preconfigured configuration. The second indication may indicate a set of offsets, scales and/or values from a preconfigured configuration. The UE may (sequentially) add the offset to the DRX configuration and/or (sequentially) multiply the DRX configuration (value) by the scale. The UE may (sequentially) use the value as the DRX configuration. The UE may use the modified DRX configuration for a certain time period. The second indication may include the number of (a set of) preconfigured configurations. The preconfigured configuration may be a list of offsets, scales and/or values of the DRX configuration.

The second indication may include/indicate an indication to suspend (e.g., deactivate) and/or resume (e.g., activate) a DRX timer (e.g., drx-onDurationTimer). The UE may suspend and/or stop the DRX timer (e.g., drx-onDurationTimer) in response to receiving the second indication (e.g., if the DRX timer is not suspended). The UE may resume and/or start the DRX timer (e.g., drx-onDurationTimer) in response to receiving the second indication (e.g., if the DRX timer is suspended). If the second indication indicates suspension/deactivation (of the DRX timer), the UE may suspend and/or stop the DRX timer (e.g., drx-onDurationTimer) in response to receiving the second indication. If the second indication indicates resumption/activation (of the DRX timer), the UE may resume and/or start the DRX timer (e.g., drx-onDurationTimer) in response to receiving the second indication. If the DRX timer (e.g., drx-onDurationTimer) is suspended and/or not resumed, the UE may stop the DRX timer (e.g., drx-onDurationTimer), may consider the DRX timer (e.g., drx-onDurationTimer) not to be running, and/or may not start the DRX timer (e.g., drx-onDurationTimer) for the DRX cycle. If the DRX timer (e.g., drx-onDurationTimer) is resumed and/or not suspended, the UE may start the DRX timer (e.g., drx-onDurationTimer) for the DRX cycle.

The second indication may include/indicate a DRX configuration (eg, for a DRX cycle and/or an on-duration). The UE may apply (the information of) the second indication to the indicated DRX configuration.

The second indication may include/indicate a DRX configuration (e.g., for a DRX group) and/or a DRX group (number). The UE may apply the second indication (information) to the indicated DRX group. The UE may apply the second indication (information) to the first DRX group. The UE may apply the second indication (information) to the second DRX group. The UE may not apply the second indication (information) to the first DRX group. The UE may not apply the second indication (information) to the second DRX group. The UE may apply the second indication (information) to the first DRX group and the second DRX group.

The second indication may include/indicate a value as the amount of DRX cycles, the on-duration, the DL transmission and/or the PDCCH opportunity. The UE may apply/use the second indication (information) of the amount of DRX cycles, the on-duration, the DL transmission and/or the PDCCH opportunity. The UE may continue to apply/use the second indication (information) until the amount of DRX cycles, the on-duration, the DL transmission and/or the PDCCH opportunity. The UE may apply/use the second indication (information) to the subsequent DRX cycles, the on-duration, the DL transmission and/or the PDCCH opportunity indicated by the second indication. The UE may increase the counter for each DRX cycle, the on-duration, the PDCCH opportunity and/or the DL reception after receiving/applying the second indication. The UE may apply/use the second indication (information) when the counter is less than and/or not greater than the indicated value. The amount of DRX cycles, the on-duration, the DL transmission and/or the PDCCH opportunity may be the time period during which the UE will use the modified DRX configuration.

The second indication may include/indicate (the duration/length of) a timer value. The second indication may indicate one or more timer values from a preconfigured configuration. The second indication may indicate a set of timer values from a preconfigured configuration. The UE may start a timer set to the timer value in response to receiving the second indication. The UE may start the timer in response to applying the second indication (information). The UE may start the timer at a specific timing indicated by the second indication. The UE may apply/use the second indication (information) when the timer is in operation. The duration of the timer may be a time period during which the UE uses the modified DRX configuration. The UE may apply/use the second indication (information) after/when the timer expires. The duration of the timer may be a time delay for the UE to use the modified DRX configuration.

The second indication may include/indicate a PDCCH opportunity. The UE may apply/use the second indication (information) until the PDCCH opportunity. The PDCCH opportunity may indicate the time period during which the UE uses the modified DRX configuration. The UE may apply/use the second indication (information) starting from (or after) the PDCCH opportunity. The PDCCH opportunity may indicate the time delay for the UE to use the modified DRX configuration.

The second indication may include/indicate a duration (e.g., in milliseconds). The second indication may indicate one or more durations from a preconfigured configuration. The second indication may indicate a set of durations from a preconfigured configuration. The UE may apply/use the second indication (information) duration. The UE may apply/use the second indication (information) in the duration from receiving the second indication to the duration. The UE may apply/use the second indication (information) in the duration from applying the second indication (information) to the duration. The UE may apply/use the second indication (information) in the duration from a specific timing indicated by the second indication to the duration. The duration may be a time period during which the UE uses the modified DRX configuration. The UE may apply/use the second indication (information) from the beginning (or after) of the duration. The duration may be a time delay for the UE to use the modified DRX configuration.

The second indication may include and/or indicate one or more of the above information. The specific timing, time period and/or time delay for the UE to use the modified DRX configuration may be indicated by one or more of the above information. The UE may use the modified DRX configuration for the time period. The UE may not use the modified DRX configuration after the time period. The UE may not use the modified DRX configuration before the time period. After the time period, the UE may use/restore the previous DRX configuration (value) (e.g., the DRX configuration (value) received in the RRC message, the DRX configuration (value) before receiving/applying the second indication).

For example, the UE may receive a second indication with an offset and/or scale for a start offset to the on-duration (e.g., drx-SlotOffset). The UE may add the offset to the start offset to the on-duration (e.g., drx-SlotOffset). The UE may multiply the start offset to the on-duration (e.g., drx-SlotOffset) by the scale. The UE may use the modified start offset to the on-duration (e.g., drx-SlotOffset) for the next on-duration and/or DRX cycle (e.g., after the UE receives the second indication). If the second indication indicates a duration to which the offset/scale will be applied, the UE may use the modified start offset to the on-duration (e.g., drx-SlotOffset) for the next on-duration and/or DRX cycle (e.g., after the UE receives the second indication).

In one instance, the offset may be greater than zero and/or the scale may be greater than one. As shown in FIG. 7 , the UE may extend the start offset (e.g., drx-SlotOffset) to the on-duration. The start timing of the on-duration timer (e.g., drx-onDurationTimer) will be shifted from t1 to t2. The UE may receive the second indication prior to the first DRX cycle. The UE may use the modified start offset (e.g., drx-SlotOffset) to the on-duration for the first DRX cycle. If the second indication indicates two DRX cycles to which the offset and/or scale will be applied, the UE may use the modified start offset (e.g., drx-SlotOffset) to the on-duration for the first DRX cycle and the second DRX cycle.

In one instance, the offset may be less than zero and/or the scale may be less than one. As shown in FIG. 8 , the UE may shrink to a start offset (e.g., drx-SlotOffset) of the on-duration. The start timing of the on-duration timer (e.g., drx-onDurationTimer) may be shifted from t2 to t1. The UE may receive a second indication prior to the first DRX cycle. The UE may use a modified start offset (e.g., drx-SlotOffset) to the on-duration for the on-duration of the first DRX cycle. If the second indication indicates two on-durations to which the offset and/or scale are to be applied, the UE may use a modified start offset (e.g., drx-SlotOffset) to the on-duration for the first DRX cycle and the second DRX cycle.

For example, the UE may receive a second indication with an offset and/or scale for the length of the on-duration (e.g., drx-onDurationTimer). The UE may add the offset to the length of the on-duration (e.g., drx-onDurationTimer). The UE may multiply the length of the on-duration (e.g., drx-onDurationTimer) by the scale. The UE may use the modified length of the on-duration (e.g., drx-onDurationTimer) for the current on-duration and/or DRX cycle (e.g., when the UE receives the second indication). The UE may use the modified length of the on-duration (e.g., drx-onDurationTimer) for the next on-duration and/or DRX cycle (e.g., after the UE receives the second indication). If the second indication indicates a duration to which the offset/scale will be applied, the UE may use the modified length of the on-duration (e.g., drx-onDurationTimer) for the next on-duration and/or DRX cycle (e.g., after the UE receives the second indication).

In one instance, the offset may be greater than zero and/or the scale may be greater than one. As shown in Figure 9, the UE may extend the length of the on-duration and/or the on-duration (e.g., drx-onDurationTimer). The end timing of the on-duration timer (e.g., drx-onDurationTimer) will be shifted from t1 to t2. The UE may receive a second indication before and/or during the first DRX cycle. The UE may use the modified length of the on-duration and/or the on-duration (e.g., drx-onDurationTimer) for the on-duration of the first DRX cycle. If the second indication indicates a timer having the length of two DRX cycles, the UE may use the modified length of the on-duration and/or the on-duration (e.g., drx-onDurationTimer) for the on-duration of the first DRX cycle and the second DRX cycle.

In one instance, the offset may be less than zero and/or the scale may be less than one. As shown in Figure 10, the UE may shrink the length of the on-duration and/or the on-duration (e.g., drx-onDurationTimer). The end timing of the on-duration timer (e.g., drx-onDurationTimer) will be shifted from t2 to t1. The UE may receive a second indication before and/or during the first DRX cycle. The UE may use the modified length of the on-duration and/or the on-duration (e.g., drx-onDurationTimer) for the on-duration of the first DRX cycle. If the second indication indicates a PDCCH opportunity after the start of the second DRX cycle, the UE may use the modified on-duration length and/or the on-duration (e.g., drx-onDurationTimer) for the on-duration of the first DRX cycle and the second DRX cycle.

For example, the UE may receive a second indication with an offset and/or scale for the length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle). The UE may add the offset to the length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle). The UE may multiply the length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) by the scale. The UE may use the modified length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) for the current DRX cycle (e.g., when the UE receives the second indication). The UE may use the modified length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) for the next DRX cycle (e.g., after the UE receives the second indication). If the second indication indicates the duration for which the offset/scale is to be applied, the UE may use the modified length of the DRX cycle (eg, drx-ShortCycle, drx-LongCycle) for the next DRX cycle (eg, after the UE receives the second indication).

In one example, the offset may be greater than zero and/or the scale may be greater than one. As shown in Figure 11, the UE may extend the first DRX cycle (length) (e.g., drx-ShortCycle, drx-LongCycle). The start timing of the second DRX cycle will be shifted from t1 to t2. The on-duration in the second DRX cycle will shift accordingly. The UE may receive a second indication before and/or during the first DRX cycle. The UE may use a modified DRX cycle (length) (e.g., drx-ShortCycle, drx-LongCycle) for the first DRX cycle. If the second indication indicates a PDCCH timing after the end of the second DRX cycle, the UE may use a modified DRX cycle (length) (e.g., drx-ShortCycle, drx-LongCycle) for the first DRX cycle and the second DRX cycle.

In one example, the offset may be less than zero and/or the scale may be less than one. As shown in Figure 12, the UE may shrink the first DRX cycle (length) (e.g., drx-ShortCycle, drx-LongCycle). The start timing of the second DRX cycle will be shifted from t2 to t1. The on-duration in the second DRX cycle will be shifted accordingly. The UE may receive a second indication before and/or during the first DRX cycle. The UE may use a modified DRX cycle (length) (e.g., drx-ShortCycle, drx-LongCycle) for the first DRX cycle. If the second indication includes the duration of the end of the second DRX cycle, the UE may use a modified DRX cycle (length) (e.g., drx-ShortCycle, drx-LongCycle) for the first DRX cycle and the second DRX cycle.

Combinations of the examples, embodiments, and concepts above and herein may be applicable to or possible for the second indication.

The first/second indication may include/indicate and/or instruct the UE to shift/adjust the values of drx-SlotOffset, drx-onDurationTimer, drx-ShortCycle, drx-LongCycle, drx-LongCycleStartOffset, drx-StartOffset, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL. The first/second indication may not include/indicate and/or instruct the UE to shift/adjust the values of drx-SlotOffset, drx-onDurationTimer, drx-ShortCycle, drx-LongCycle, drx-LongCycleStartOffset, drx-StartOffset, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL.

In response to receiving the first indication and/or the second indication, the UE may transmit an acknowledgement (eg, an acknowledgement (ACK) to the NW). The acknowledgement may be uplink control information (UCI), MAC CE, and/or UE assistance information (UAI).

The UE may monitor the first indication and/or the second indication during the DRX action time of the DRX group associated with the first indication and/or the second indication. Alternatively, the UE may monitor the first indication and/or the second indication when the drx-onDurationTimer of the DRX group associated with the first indication and/or the second indication is in operation. The UE may not monitor the first indication and/or the second indication outside the DRX action time of the DRX group associated with the first indication and/or the second indication. Alternatively, the UE may not monitor the first indication and/or the second indication when the drx-onDurationTimer of the DRX group associated with the first indication and/or the second indication is not in operation.

The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after receiving the first indication and/or the second indication. The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after transmitting an acknowledgement of the first indication and/or the second indication. The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after applying the first indication and/or the second indication. The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after using a new and/or modified DRX configuration.

The association between the DRX group and the first/second indication may be indicated by the first/second indication. The UE may determine the DRX group to which the first/second indication will be applied based on the DRX group indicated by the first/second indication. Alternatively, the association between the DRX group and the first/second indication may be based on the serving cell on which the first/second indication is received. The UE may determine the DRX group to which the first/second indication will be applied based on the serving cell in which the first/second indication is received. The DRX group is the DRX group of the serving cell. Alternatively, the association between the DRX group and the first/second indication may be based on the time and/or frequency resources on which the first/second indication is received. Alternatively, the association between the DRX group and the first/second indication may be configured by the network.

The UE may receive configurations related to DRX and/or DRX groups. The UE may receive one or more DRX configurations (e.g., DRX-Config, DRX-ConfigSecondaryGroup) for a DRX group. A DRX group may be a group of cells (e.g., one or more cells) to which the same DRX configuration is applied. The group of cells may belong to the same MAC entity. The DRX configuration (e.g., DRX-Config, DRX-ConfigSecondaryGroup) for a DRX group may include configurations for on-duration, DRX cycle, inactive time, and/or retransmission time. The DRX configuration for the DRX group (e.g., DRX-Config, DRX-ConfigSecondaryGroup) may include (at least) drx-SlotOffset, drx-onDurationTimer, drx-ShortCycle, drx-LongCycle, drx-LongCycleStartOffset, drx-StartOffset, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL. The UE may receive a preconfigured configuration (for the DRX group) to adjust the DRX configuration. The preconfiguration may include (at least) one or more offsets, scales, values to the DRX configuration, timer values and/or durations. The UE may receive the DRX configuration and/or the pre-configured configuration from an RRC message (eg, RRCSetup, RRCResume, RRCReconfiguration) and/or the first/second indication.

The UE may receive an RRC message (e.g., RRCSetup, RRCesume, RRCReconfiguration) in an RRC inactive mode, an RRC idle mode, and/or an RRC connected mode. The UE may receive an RRC message before the UE is configured with DRX functionality (e.g., to configure the DRX functionality). The UE may receive an RRC message after the UE is configured with DRX functionality (e.g., to reconfigure the DRX functionality). The UE may receive an RRC message when the UE is in/during the active time and/or the on-duration. The UE may receive an RRC message when the UE is not in/during the active time and/or the on-duration.

The UE may receive the first indication and/or the second indication in RRC connected mode. The UE may receive the first indication and/or the second indication after the UE is configured with DRX functionality. The UE may receive the first indication and/or the second indication when the UE is in/during the active time and/or the on-duration. The UE may receive the first indication and/or the second indication when the UE is not in/during the active time and/or the on-duration.

Examples of the present invention are described below.

13 , regarding such and other concepts, systems, and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: receiving an RRC message including a DRX configuration (step 1002); receiving a first indication and/or a second indication (step 1004); and adjusting the DRX configuration based on the first indication and/or the second indication (step 1006).

Referring now to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, an apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive an RRC message including a DRX configuration; (ii) receive a first indication and/or a second indication; and (iii) adjust the DRX configuration based on the first indication and/or the second indication. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring to Figure 14, regarding such and other concepts, systems and methods of the present invention, a method 1010 for a UE in a wireless communication system includes: receiving first signaling configuring at least one value of a DRX parameter for a first DRX group and at least one value of a DRX parameter for a second DRX group (step 1012); receiving second signaling indicating the first value of the DRX parameter or the second value of the at least one value of the DRX parameter in a serving cell (step 1014); and adjusting the DRX parameters for the first DRX group or the second DRX group based on the target DRX group indicated in the second signaling or based on whether the serving cell is assigned to the first DRX group or the second DRX group (step 1016).

In various embodiments, the DRX parameter is drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-InactivityTimer, drx-ShortCycle, drx-LongCycle and/or drx-ShortCycleTimer.

In various embodiments, the first signaling is an RRC message.

In various embodiments, the second signaling is a DCI or a MAC CE.

In various embodiments, the target DRX group is indicated in the second signaling.

In various embodiments, if the target DRX group is the first DRX group, the UE adjusts DRX parameters for the first DRX group, and/or if the target DRX group is the second DRX group, the UE adjusts DRX parameters for the second DRX group.

In various embodiments, if the serving cell is assigned to the first DRX group, the UE adjusts DRX parameters for the first DRX group, and/or if the serving cell is assigned to the second DRX group, the UE adjusts DRX parameters for the second DRX group.

In various embodiments, the UE adjusts the DRX parameter by applying the first value or the second value to the DRX parameter.

In various embodiments, the UE adjusts the DRX parameter by activating or deactivating the DRX parameter with the first value or the second value.

In various embodiments, whether the serving cell is assigned to the first DRX group or the second DRX group is indicated in the first signaling.

In various embodiments, the first DRX group and the second DRX group are associated with the same MAC entity.

Referring now to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive first signaling configuring at least one value of a DRX parameter for a first DRX group and at least one value of a DRX parameter for a second DRX group; (ii) receive second signaling in a serving cell indicating a first value of the DRX parameter or a second value of the at least one value of the DRX parameter; and (iii) adjust the DRX parameter for the first DRX group or the second DRX group based on a target DRX group indicated in the second signaling or based on whether the serving cell is assigned to the first DRX group or the second DRX group. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

To solve the problem, the UE may receive multiple DRX configurations (sets), for example, associated with different (types of) on-durations and/or DRX cycles. The UE may be (pre) configured with more than one DRX configuration (set) (e.g., for different on-durations and/or DRX cycles). The multiple DRX configurations (sets) and/or more than one DRX configuration (set) may include a default DRX configuration (set) and/or an additional DRX configuration (set). The UE may be configured with a default DRX configuration (set). The UE may be configured with one or more additional DRX configurations (sets). The UE may use the default DRX configuration (set) when the UE is not configured with an additional DRX configuration (set). The additional DRX configuration (set) may be used by the UE simultaneously with the default DRX configuration (set). The additional DRX configuration (set) may be a DRX configuration different from the default DRX configuration (set). The (set of) default DRX configurations and/or the (set of) additional DRX configurations may include drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer.

The (set of) default DRX configurations may include at least one parameter not included in the (set of) additional DRX configurations. The at least one parameter may include drx-InactivityTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL.

For example, in DRX operation, the UE uses a first parameter in the additional DRX configuration (set), such as drx-StartOffset, and a second parameter in the default DRX configuration (set), such as drx-HARQ-RTT-TimerDL. The UE may or may not use the first parameter in the default DRX configuration (set) for DRX operation.

The UE may receive and/or be (pre-)configured with (a set of) multiple DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The UE may receive the DRX parameters/configurations in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration).

The UE may receive and/or be (pre) configured with a list of DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The UE may receive and/or be (pre) configured with a list of first DRX parameters/configurations. The UE may receive and/or be (pre) configured with a list of second DRX parameters/configurations. The UE may receive and/or be (pre) configured with a list of third DRX parameters/configurations. The first, second and/or third DRX parameters/configurations may be configured individually in an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The first, second and/or third DRX parameters/configurations may be drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer. The first, second and third DRX parameters/configurations may be different DRX parameters/configurations.

For example, the UE may be configured with a DRX group and/or a drx-SlotOffset and/or a list of drx-SlotOffset in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a drx-onDurationTimer and/or a list of drx-onDurationTimers in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a drx-StartOffset and/or a list of drx-StartOffset in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a drx-LongCycle and/or a list of drx-LongCycle in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a list of drx-LongCycleStartOffset and/or drx-LongCycleStartOffset in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a list of drx-ShortCycle and/or drx-ShortCycle in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a list of drx-ShortCycle and/or drx-ShortCycle in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a DRX group and/or a list of drx-ShortCycleTimer and/or drx-ShortCycleTimer in an information element (e.g., DRX-Config) (of a DRX configuration).

The UE may receive and/or be (pre) configured with a list of combinations of DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The UE may receive and/or be (pre) configured with a list of a first set of DRX parameters/configurations. The UE may receive and/or be (pre) configured with a list of a second set of DRX parameters/configurations. The first set of DRX parameters/configurations and/or the second set of DRX parameters/configurations may include drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer. The set of DRX parameters/configurations may refer to or may be a combination of DRX parameters/configurations. The DRX configuration may be configured in combination in an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration.

For example, the UE may be configured with drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer in a DRX group and/or in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a list of sets of DRX configurations related to on-duration and/or DRX cycle in a DRX group and/or in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a list of sets of drx-SlotOffset and drx-onDurationTimer in a DRX group and/or in an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a list of sets of drx-StartOffset, drx-LongCycle and/or drx-LongCycle in a DRX group and/or an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a list of sets of drx-ShortCycle and drx-ShortCycleTimer in a DRX group and/or an information element (e.g., DRX-Config) (of a DRX configuration). The UE may be configured with a list of sets of drx-onDurationTimer, drx-LongCycle and/or drx-LongCycle in a DRX group and/or an information element (e.g., DRX-Config) (of a DRX configuration).

The UE may be configured with a single drx-InactivityTimer (e.g., not a list) in the DRX group and/or the information element (e.g., DRX-Config) (of the DRX configuration). The UE may be configured with a single drx-HARQ-RTT-TimerDL (e.g., not a list) in the DRX group and/or the information element (e.g., DRX-Config) (of the DRX configuration). The UE may be configured with a single drx-HARQ-RTT-TimerUL (e.g., not a list) in the DRX group and/or the information element (e.g., DRX-Config) (of the DRX configuration). The UE may be configured with a single drx-RetransmissionTimerDL (e.g., not a list) in the DRX group and/or the information element (e.g., DRX-Config) (of the DRX configuration). The UE may be configured with a single drx-RetransmissionTimerUL (e.g., not a list) in the DRX group and/or the information element (e.g., DRX-Config) (of the DRX configuration).

The UE may receive and/or be (pre-)configured with different DRX parameters/configurations in information elements of multiple DRX groups and/or DRX configurations. The information elements of the DRX group and/or DRX configuration may be DRX-Config, DRX-ConfigSecondaryGroup and/or new information elements (e.g., third DRX group, additional DRX group). The UE may receive the DRX configuration in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration).

The UE may receive and/or be (pre) configured with multiple DRX groups and/or (DRX configured) information elements and/or lists thereof. The DRX group may be and/or refer to an information element (DRX configured) configured by the network. The UE may receive and/or be (pre) configured with a first DRX group (e.g., DRX-Config). The UE may receive and/or be (pre) configured with more than one first DRX group (e.g., DRX-Config). The UE may receive and/or be (pre) configured with a second DRX group (e.g., DRX-ConfigSecondaryGroup). The UE may receive and/or be (pre) configured with more than one second DRX group (e.g., DRX-ConfigSecondaryGroup). The UE may receive and/or be (pre) configured with an additional DRX group (e.g., a third DRX group). The UE may receive and/or be (pre) configured with more than one additional DRX group (e.g., a third DRX group). The additional DRX group may be a DRX group/configuration for XR.

The first DRX group (e.g., DRX-Config), the second DRX group (e.g., DRX-ConfigSecondaryGroup), and/or the additional DRX group (e.g., the third DRX group) can be used for the same service cell, on the same bandwidth part (BWP), and/or in the same frequency range. The service cell can be configured to the first DRX group (e.g., DRX-Config), the second DRX group (e.g., DRX-ConfigSecondaryGroup), and/or the additional DRX group (e.g., the third DRX group) at the same time. The service cell can be a primary cell (PCell), a primary secondary cell (PSCell), and/or a secondary cell (SCell). The first DRX group (e.g., DRX-Config), the second DRX group (e.g., DRX-ConfigSecondaryGroup), and/or the additional DRX group (e.g., the third DRX group) can be used for different service cells, on different BWPs, and/or in different frequency ranges.

One or more of the first DRX group (e.g., DRX-Config) may include DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycle (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer). The DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycle (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer) may be (configured to be) optional in the first DRX group (e.g., DRX-Config).

One or more of the first DRX group (e.g., DRX-Config) may not include DRX parameters/configurations related to inactivity time (e.g., drx-InactivityTimer) and/or retransmission time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL). DRX parameters/configurations related to inactivity time (e.g., drx-InactivityTimer) and/or retransmission time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) may be (configured to be) optional in the first DRX group (e.g., DRX-Config).

One or more of the second DRX groups (e.g., DRX-ConfigSecondaryGroup) may include DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycles (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer). DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycles (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer) may be (configured to be) optional in the second DRX group (e.g., DRX-ConfigSecondaryGroup). DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycle (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer) may be (configured to be) mandatory in the second DRX group (e.g., DRX-ConfigSecondaryGroup).

One or more of the second DRX groups (e.g., DRX-ConfigSecondaryGroup) may not include DRX parameters/configurations related to inactivity time (e.g., drx-InactivityTimer) and/or retransmission time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL). The DRX parameters/configurations related to inactivity time (e.g., drx-InactivityTimer) may be (configured to be) optional in the second DRX group (e.g., DRX-ConfigSecondaryGroup).

One or more of the additional DRX groups may include DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycle (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer). DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycle (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer) may be (configured to be) optional in the additional DRX groups. DRX parameters/configurations related to on-duration (e.g., drx-SlotOffset, drx-onDurationTimer) and/or DRX cycle (e.g., drx-StartOffset, drx-LongCycle, drx-ShortCycle, drx-ShortCycleTimer) may be (configured to be) mandatory in an additional DRX group.

One or more of the additional DRX groups may not include DRX parameters/configurations related to inactivity time (e.g., drx-InactivityTimer) and/or retransmission time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL). DRX parameters/configurations related to inactivity time (e.g., drx-InactivityTimer) and/or retransmission time (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) may not be configured in the additional DRX groups.

Multiple DRX parameters/configurations (sets) (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may be applied to all serving cells of the corresponding MAC entity. Multiple DRX parameters/configurations (sets) (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may be applied to a specific serving cell. Multiple of the multiple DRX parameters/configurations (sets) and/or multiple of the multiple DRX groups may be (simultaneously) applied to a serving cell.

A specific service cell may be a service cell for an XR service. A specific service cell may be configured and/or indicated in each DRX parameter/configuration (set) (e.g., in a DRX group and/or in an information element) and/or in each DRX group (e.g., an information element). A specific service cell may be configured and/or indicated as being associated with one or more DRX parameters/configurations (sets) (e.g., in a DRX group and/or in an information element) and/or a DRX group (e.g., an information element). A service cell may be a PCell, a PSCell and/or an SCell. Different service cells may be associated with different streams of an XR service or an XR DL service having multiple streams. Different service cells may be associated with different XR services.

Throughout this disclosure, different (sets of) DRX configurations and/or different DRX groups may correspond to (or be associated with or used for) different flows of an XR service or XR DL service with multiple flows. Different (sets of) DRX configurations and/or different DRX groups may correspond to (or be associated with or used for) different XR services.

Multiple DRX parameters/configurations (sets) (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may be applied to an XR service. Multiple DRX parameters/configurations (sets) (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may be applied to all HARQ processes of a corresponding MAC entity. Multiple DRX parameters/configurations (sets) (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may be applied to a specific HARQ process.

A specific HARQ process may be a HARQ process for an XR service. A specific HARQ process may be configured and/or indicated in each DRX parameter/configuration (set) (e.g., in a DRX group and/or in an information element) and/or in each DRX group (e.g., an information element). A specific HARQ process may be configured and/or indicated as being associated with one or more DRX parameters/configurations (sets) (e.g., in a DRX group and/or in an information element) and/or a DRX group (e.g., an information element). Different HARQ processes may be associated with different streams of an XR service or an XR DL service having multiple streams. Different HARQ processes may be associated with different XR services.

(Sets of) multiple DRX parameters/configurations (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may apply to all BWPs. (Sets of) multiple DRX parameters/configurations (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may apply to a specific BWP.

A specific BWP may be a BWP for an XR service. A specific BWP may be configured and/or indicated in each DRX parameter/configuration (set) (e.g., in a DRX group and/or an information element) and/or in each DRX group (e.g., an information element). A specific BWP may be configured and/or indicated as being associated with one or more DRX parameters/configurations (sets) (e.g., in a DRX group and/or an information element) and/or a DRX group (e.g., an information element). Different BWPs may be associated with different streams of an XR service or an XR DL service having multiple streams. Different BWPs may be associated with different XR services.

(Sets of) multiple DRX parameters/configurations (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may apply to all logical channels (LCHs) and/or data radio bearers (DRBs). (Sets of) multiple DRX parameters/configurations (e.g., in one DRX group and/or one information element) and/or multiple DRX groups (e.g., information elements) may apply to a specific LCH or DRB.

A specific LCH and/or DRB may be an LCH and/or DRB for an XR service. A specific LCH and/or DRB may be configured and/or indicated in each DRX parameter/configuration (set) (e.g., in a DRX group and/or an information element) and/or in each DRX group (e.g., an information element). A specific LCH and/or DRB may be configured and/or indicated as being associated with one or more DRX parameters/configurations (sets) (e.g., in a DRX group and/or an information element) and/or a DRX group (e.g., an information element). Different LCHs and/or DRBs may be associated with different streams of an XR service or an XR DL service having multiple streams. Different LCHs and/or DRBs may be associated with different XR services.

15 , in connection with such and other concepts, systems and methods of the present invention, a method 1020 for a UE in a wireless communication system includes receiving an RRC message including a plurality of DRX configurations (step 1022 ).

In various embodiments, the plurality of DRX configurations comprises one or more lists of DRX parameters in (or associated with) DRX groups and/or information elements.

In various embodiments, the plurality of DRX configurations comprises one or more lists of combinations of DRX parameters in (or associated with) DRX groups and/or information elements.

In various embodiments, the plurality of DRX configurations include one or more DRX groups and/or information elements.

Referring now to Figures 3 and 4, in one or more embodiments from the perspective of a UE, an apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive an RRC message including a plurality of DRX configurations. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

To solve the problem, the UE can use and/or switch the DRX configuration through network indication. The UE can receive a (network) indication of using and/or switching the DRX configuration. The UE can receive, for example, multiple DRX configurations (sets) associated with different (types of) on-durations and/or DRX cycles. The UE can be (pre-) configured with more than one DRX configuration (set) (for example, for different on-durations and/or DRX cycles) in an RRC message (for example, RRCSetup, RRCResume, RRCReconfiguration). The DRX configuration (set) can be associated with the same serving cell, for example, for controlling PDCCH monitoring in the serving cell. The UE can receive an indication, activation and/or deactivation of the DRX configuration through L1/L2 signaling/indication (for example, DCI, MAC CE). The indication can be L1/L2 signaling/indication (for example, DCI, MAC CE), for example, for activation and/or deactivation of the DRX configuration. The UE can use (or switch to) the indicated (activated) DRX configuration, for example, based on the indication. The UE may, for example, activate and/or deactivate the indicated DRX configuration based on the indication. More than one of the (set of) multiple DRX configurations may be activated. The UE may use the indicated DRX configuration for the XR service. The UE may use the indicated DRX configuration for a specific flow of the XR service, for example, as indicated by the indication.

The multiple (sets of) DRX configurations and/or more than one DRX configuration (sets) may be and/or may be referred to as (sets of) multiple DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The UE may receive and/or be (pre) configured with a list of DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The DRX parameters/configurations may be drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer. The UE may receive and/or be (pre) configured with a list of combinations of DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The DRX parameters/configurations may be configured in combination in the information element of the DRX group and/or DRX configuration (e.g., DRX-Config). The combination of DRX parameters/configurations may include drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle, and/or drx-ShortCycleTimer.

The multiple DRX configurations (sets) and/or more than one DRX configuration (sets) may be and/or be referred to as information elements (different DRX parameters/configurations) of multiple/different DRX groups and/or DRX configurations. The information elements of the DRX group and/or DRX configuration may be DRX-Config, DRX-ConfigSecondaryGroup and/or new information elements (e.g., a third DRX group, an additional DRX group). The UE may receive and/or be (pre) configured with multiple DRX groups and/or (DRX configuration) information elements and/or lists thereof. The DRX group may be and/or refer to an information element (DRX configuration) configured by the network. The additional DRX group may be a DRX group/configuration for XR. The first DRX group (e.g., DRX-Config), the second DRX group (e.g., DRX-ConfigSecondaryGroup) and/or the additional DRX group (e.g., the third DRX group) may be used for the same serving cell, on the same BWP and/or in the same frequency range. The serving cell may be configured to the first DRX group (eg, DRX-Config), the second DRX group (eg, DRX-ConfigSecondaryGroup) and/or the additional DRX group (eg, the third DRX group) simultaneously (eg, simultaneously). The serving cell may be a PCell, a PSCell and/or a SCell.

The UE may use some or all of the (sets of) multiple DRX configurations simultaneously, e.g., for a serving cell. The UE may use more than one (set of) DRX configurations simultaneously, e.g., for a serving cell. More than one (set of) DRX configurations may be activated simultaneously. The UE may use only one (set of) multiple DRX configurations simultaneously, e.g., for a serving cell.

The multiple DRX configurations (sets) and/or more than one DRX configuration (set) may include a default DRX configuration (set) and/or an additional DRX configuration (set). The UE may be configured with one default DRX configuration (set). The UE may be configured with one or more additional DRX configurations (sets). The additional DRX configuration (set) may be used by the UE simultaneously with the default DRX configuration (set). The default DRX configuration (set) may be deactivated by the network. The default DRX configuration (set) may not (be allowed to) be deactivated by the network, for example, by indication.

The UE may use the default DRX configuration (set) when the UE is not configured with an additional DRX configuration (set). The UE may use the default DRX configuration (set) when multiple DRX configurations (set) are configured. The UE may use the default DRX configuration (set) when the UE is instructed to use the default DRX configuration (set). The UE may use the default DRX configuration (set) when the default DRX configuration (set) is activated by the network. The UE may not use the default DRX configuration (set) when the UE is not instructed to use the default DRX configuration (set) and/or the UE is instructed not to use the default DRX configuration (set). The UE may not use the default DRX configuration (set) when the default DRX configuration (set) is deactivated by the network. The UE may not use the default DRX configuration (set) when receiving an indication to switch from the default DRX configuration (set) to the additional DRX configuration (set). The UE may use the default DRX configuration (set) at any time.

The UE may use the additional DRX configuration (set) when the UE is instructed to use the additional DRX configuration (set). The UE may use the additional DRX configuration (set) when the additional DRX configuration (set) is activated by the network. The UE may not use the additional DRX configuration (set) when the UE is not instructed to use the additional DRX configuration (set) and/or the UE is instructed not to use the additional DRX configuration (set). The UE may not use the additional DRX configuration (set) when the additional DRX configuration (set) is deactivated by the network. The UE may not use the additional DRX configuration (set) when multiple DRX configurations (sets) are configured.

The default DRX configuration (set) and/or the additional DRX configuration (set) may include drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer. The additional DRX configuration (set) may be a DRX configuration different from the default DRX configuration (set). The default DRX configuration (set) may include at least one parameter not included in the additional DRX configuration (set). The at least one parameter may include drx-InactivityTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL. For example, in DRX operation, the UE uses a first parameter in the additional DRX configuration (set), such as drx-StartOffset, and a second parameter in the default DRX configuration (set), such as drx-HARQ-RTT-TimerDL. The UE may or may not use the first parameter in the default DRX configuration (set) for DRX operation.

For example, the UE may use and/or switch to the indicated DRX configuration (set) to perform DRX operations, such as PDCCH monitoring in the serving cell. The UE may receive and/or be (pre-)configured with multiple DRX configurations (sets), such as in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may perform DRX operations using a first DRX configuration (set), such as a default DRX configuration (set), such as after receiving the DRX configuration.

The UE may receive an indication of one of a plurality of DRX configurations (sets) (e.g., via a DCI and/or a MAC CE). The UE may receive a first indication indicating a second DRX configuration (set) (e.g., via a DCI and/or a MAC CE). The UE may perform DRX operation using the second DRX configuration (set) in response to receiving the first indication. The UE may perform DRX operation using the first DRX configuration (set) and the second DRX configuration (set). The UE may not perform DRX operation using the first DRX configuration (set) in response to receiving the first indication. The UE may receive a second indication indicating a third DRX configuration (set). The UE may perform DRX operation using the third DRX configuration (set) in response to receiving the second indication. The UE may not perform DRX operation using the second DRX configuration (set) in response to receiving the second indication.

The UE may receive an indication of multiple of the multiple DRX configurations (sets) (e.g., via DCI and/or MAC CE). The UE may receive a first indication indicating a second and/or third DRX configuration (set). The UE may perform DRX operation using the second and/or third DRX configuration (set) in response to receiving the first indication. The UE may or may not perform DRX operation using the first DRX configuration (set) in response to receiving the first indication. The UE may receive a second indication indicating a fourth and/or fifth DRX configuration (set). The UE may perform DRX operation using the fourth and/or fifth DRX configuration (set) in response to receiving the second indication. The UE may not perform DRX operation using the second and/or third DRX configuration (set) in response to receiving the second indication.

For example, the UE may activate the indicated DRX configuration (set) to perform DRX operation (e.g., PDCCH monitoring in the serving cell), and/or deactivate the current DRX configuration (set) (e.g., the DRX configuration (set) used by the UE before receiving the activation). The UE may receive and/or be (pre-)configured with multiple DRX configurations (sets), for example in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may perform DRX operation using a first DRX configuration (set) (e.g., a default DRX configuration (set)), for example, after receiving the DRX configuration.

The UE may receive (an indication of) activation of one of (a set of) multiple DRX configurations (for example, via a DCI and/or a MAC CE). The UE may receive (an indication of) a first activation indicating (a set of) a second DRX configuration. The UE may activate (a set of) the second DRX configuration in response to receiving (an indication of) the first activation. The UE may or may not deactivate (a set of) the first DRX configuration in response to receiving (an indication of) the first activation. The UE may perform DRX operation using (a set of) the second DRX configuration in response to activating (a set of) the second DRX configuration. The UE may or may not perform DRX operation using (a set of) the first DRX configuration in response to activating (a set of) the second DRX configuration. The UE may receive (an indication of) a second activation indicating (a set of) a third DRX configuration. The UE may activate (a set of) the third DRX configuration in response to receiving (an indication of) the second activation. The UE may deactivate (a set of) the second DRX configuration in response to receiving (an indication of) the second activation. The UE may perform DRX operation using the third DRX configuration (the set of) in response to activating the third DRX configuration (the set of) .

The UE may receive activation (indication) of multiple of the multiple DRX configurations (sets) (e.g., via DCI and/or MAC CE). The UE may receive a first activation (indication) indicating a second and/or third DRX configuration (set). The UE may activate the second and/or third DRX configuration (set) in response to receiving the first activation (indication). The UE may or may not deactivate the first DRX configuration (set) in response to receiving the first activation (indication). The UE may perform DRX operation using the second and/or third DRX configuration (set) in response to activating the second and/or third DRX configuration (set). The UE may or may not perform DRX operation using the first DRX configuration (set) in response to activating the second and/or third DRX configuration (set). The UE may receive a second activation (indication) indicating a fourth and/or fifth DRX configuration (set). The UE may activate the fourth and/or fifth DRX configuration (set) in response to receiving the second activation (indication). The UE may deactivate the second and/or third DRX configurations (sets) in response to receiving (an indication of) the second activation. The UE may perform DRX operations using the fourth and/or fifth DRX configurations (sets) in response to activating (a set of) the fourth and/or fifth DRX configurations.

For example, the UE may activate and/or deactivate the indicated DRX configuration (set) to perform DRX operation, such as PDCCH monitoring in the serving cell. The UE may receive and/or be (pre-)configured with multiple DRX configurations (sets), such as in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may perform DRX operation using a first DRX configuration (set), such as a default DRX configuration (set), such as after receiving the DRX configuration.

The UE may receive (an indication of) activation of one of (a set of) multiple DRX configurations (for example, via a DCI and/or a MAC CE). The UE may receive (an indication of) a first activation indicating (a set of) a second DRX configuration. The UE may activate (a set of) a second DRX configuration in response to receiving (an indication of) the first activation. The UE may perform DRX operations using the first and/or second DRX configurations (sets) in response to activating (a set of) the second DRX configuration. The UE may receive (an indication of) a second activation indicating (a set of) a third DRX configuration. The UE may activate (a set of) a third DRX configuration in response to receiving (an indication of) the second activation. The UE may perform DRX operations using the first, second and/or third DRX configurations (sets) in response to activating (a set of) the third DRX configuration. The UE may receive (an indication of) a third deactivation indicating (a set of) a second DRX configuration. The UE may deactivate (a set of) the second DRX configuration in response to receiving (a indication of) the third activation. The UE may perform DRX operation using the first and/or third DRX configuration (set) in response to deactivating the second DRX configuration (set).

The UE may receive activation (indication) of multiple of the multiple DRX configurations (sets) (e.g., via DCI and/or MAC CE). The UE may receive a first activation (indication) indicating a second and/or third DRX configuration (set). The UE may activate the second and/or third DRX configuration (set) in response to receiving the first activation (indication). The UE may perform DRX operation using the first, second and/or third DRX configuration (set) in response to activating the second and/or third DRX configuration (set). The UE may receive a second activation (indication) indicating a fourth and/or fifth DRX configuration (set). The UE may activate the fourth and/or fifth DRX configuration (set) in response to receiving the second activation (indication). The UE may perform DRX operation using the first, second, third, fourth and/or fifth DRX configuration (set) in response to activating the fourth and/or fifth DRX configuration (set). The UE may receive a third deactivation (indication) indicating the second and/or fourth DRX configuration (set). The UE may deactivate the second and/or fourth DRX configuration (set) in response to receiving (an indication of) the third activation. The UE may perform DRX operation using the first, third and/or fifth DRX configuration (set) in response to deactivating the second and/or fourth DRX configuration (set).

In response to receiving the indication and/or the indication of activation/deactivation, the UE may transmit an acknowledgement (eg, ACK) to the NW. The acknowledgement may be UCI, MAC CE and/or UAI.

In response to receiving the indication and/or the indication of activation/deactivation, the UE may use and/or activate the indication/corresponding DRX configuration (set) at or after (at least one of) the following first timings:

- Receipt of said indication and/or indication of activation/deactivation (first symbol thereafter);

- the transmission of said acknowledgement (first symbol thereafter);

- a specific PDCCH opportunity (e.g. indicated in the indication predefined in the standard and/or in the indication of activation/deactivation);

- a time delay (e.g. indicated in said indication predefined in the standard and/or in the indication for activation/deactivation); and/or

- When a timer associated with the DRX configuration is (re)started.

The (set of) DRX configurations used before receiving the indication and/or the indication of activation/deactivation may be activated/used after the applicable time of the indication and/or the indication of activation/deactivation. The (set of) DRX configurations indicated/activated in the indication and/or the indication of activation/deactivation may be deactivated after the applicable time of the indication and/or the indication of activation. The (set of) DRX configurations deactivated in the indication and/or the indication of activation/deactivation may be activated after the applicable time of the indication of deactivation. The applicable time of the indication and/or the indication of activation/deactivation may be a duration between the first timing sequence and the second timing sequence.

In response to receiving the indication and/or the indication of activation/deactivation, the UE may stop applying the indication and/or the indication of activation/deactivation at or after (at least one of) the following second timings:

- a specific PDCCH opportunity (e.g. indicated in the indication predefined in the standard and/or in the indication of activation/deactivation);

- a time delay (e.g. indicated in said indication predefined in the standard and/or in the indication for activation/deactivation);

-Timer expires;

- several DL receptions; and/or

- A number of DRX cycles or On-Durations.

The UE may use the indicated/corresponding DRX configuration (set) before (at least) the above timing. The UE may not use the indicated /corresponding DRX configuration (set) after (at least) the above timing. The UE may use the last used DRX configuration (set) (for example, the DRX configuration (set) used by the UE before receiving the indication and/or the indication of activation/deactivation) at or after (at least) the above timing. In response to (at least) the above timing (for example, the UE stops using the indicated/corresponding DRX configuration (set)), the UE may use, activate and/or switch to the last used DRX configuration (set) (for example, the DRX configuration (set) used by the UE before receiving the indication and/or the indication of activation/deactivation).

The UE may increase the counter for each DRX cycle, on-duration, PDCCH opportunity and/or DL reception after using/activating/deactivating the indicated/corresponding DRX configuration (set). The UE may use the indicated/corresponding DRX configuration (set) when the counter is less than and/or not greater than the indicated value. The UE may not use the indicated/corresponding DRX configuration (set) when the counter is less than and/or not greater than the indicated value.

In one example, in response to receiving a first indication indicating a second DRX configuration (set), the UE may perform DRX operation using the second DRX configuration (set) upon reception of (the first symbol after) the first indication. The UE may stop performing DRX operation using the second DRX configuration (set) upon/after a predefined number of PDCCH opportunities after (the first symbol after) the reception of the first indication. The UE may perform DRX operation using the first DRX configuration (set) upon/after a predefined number of PDCCH opportunities after (the first symbol after) the reception of the first indication.

In one example, in response to receiving a second indication indicating a third DRX configuration (set), the UE may perform DRX operation using the third DRX configuration (set) at (the first symbol after) the confirmed transmission. The UE may stop performing DRX operation using the second DRX configuration (set) at an indicated number of PDCCH opportunities after (the first symbol after) the confirmed transmission. The UE may perform DRX operation using the second DRX configuration (set) at an indicated number of PDCCH opportunities after (the first symbol after) the confirmed transmission.

In one example, in response to receiving a first indication indicating a second and/or third DRX configuration (set), the UE may perform DRX operation using the second and/or third DRX configuration (set) at/after a predefined number of PDCCH opportunities (e.g., after receiving the first indication). The UE may stop performing DRX operation using the second and/or third DRX configuration (set) at a predefined time delay (e.g., in milliseconds) after the UE starts using the second and/or third DRX configuration (set). The UE may perform DRX operation using the first DRX configuration (set) at a predefined time delay (e.g., in milliseconds) after the UE starts using the second and/or third DRX configuration (set).

In one example, in response to receiving a second indication indicating a fourth and/or fifth DRX configuration (set), the UE may perform DRX operation using the fourth and/or fifth DRX configuration (set) at the PDCCH timing indicated in the second indication. The UE may stop performing DRX operation using the fourth and/or fifth DRX configuration (set) at an indicated time delay (e.g., in milliseconds) after the UE starts using the fourth and/or fifth DRX configuration (set). The UE may perform DRX operation using the second and/or third DRX configuration (set) at an indicated time delay (e.g., in milliseconds) after the UE starts using the second and/or third DRX configuration (set).

In one example, in response to receiving a first activation (indication) indicating a second DRX configuration (set), the UE may activate the second DRX configuration (set) to perform DRX operation at/after an indicated number of PDCCH opportunities (e.g., indicated in the first activation (indication)), e.g., after receiving the first activation (indication). The UE may start a timer in response to activating the second DRX configuration (set). Upon expiration of the timer, the UE may stop using the second DRX configuration (set) and/or deactivate the second DRX configuration (set). Upon expiration of the timer, the UE may perform DRX operation using the first and/or third DRX configuration (set).

In one example, in response to receiving (an indication of) a second activation indicating a third DRX configuration (set), the UE may activate (a set of) the third DRX configuration to perform DRX operation at/after a predefined time delay (e.g., after receiving (an indication of) the second activation). The UE may increase a counter for each DL reception after using/activating (a set of) the third DRX configuration. The UE may stop using (a set of) the third DRX configuration to perform DRX operation and/or deactivate (a set of) the third DRX configuration after a number of DL receptions (e.g., the counter is greater than the indicated value/threshold). The UE may perform DRX operation using (a set of) the second DRX configuration after a number of DL receptions (e.g., the counter is greater than the indicated value/threshold).

In one example, in response to receiving a third deactivation (indication of) indicating a second DRX configuration (set), the UE may deactivate the second DRX configuration (set) to perform DRX operation at/after an indicated time delay (e.g., indicated in the first activation (indication)), e.g., after receiving the third deactivation (indication of). The UE may increase a counter for each DRX cycle after deactivating the second DRX configuration (set). The UE may activate the second DRX configuration (set) to perform DRX operation after a number of DRX cycles (e.g., the counter is greater than the indicated value/threshold). The UE may activate and/or perform DRX operation using the second DRX configuration (set) after a number of DRX cycles (e.g., the counter is greater than the indicated value/threshold).

The UE may monitor the indication and/or the indication of activation/deactivation during the DRX action time of the associated DRX group and/or DRX configuration. Alternatively, the UE may monitor the indication and/or the indication of activation/deactivation when the drx-onDurationTimer of the associated DRX group and/or DRX configuration is in operation. The UE may not monitor the indication and/or the indication of activation/deactivation outside the DRX action time of the associated DRX group and/or DRX configuration. Alternatively, the UE may not monitor the indication and/or the indication of activation/deactivation when the drx-onDurationTimer of the associated DRX group and/or DRX configuration is not in operation.

In response to receiving the indication and/or the indication of activation/deactivation, the UE may stop one or more DRX timers of the associated DRX group and/or DRX configuration. In response to receiving the indication and/or the indication of activation/deactivation, the UE may stop the on-duration timer (e.g., drx-onDurationTimer). In response to receiving the indication and/or the indication of activation/deactivation, the UE may not stop the on-duration timer (e.g., drx-onDurationTimer), for example, keeping the timer running. In response to receiving the indication and/or the indication of activation/deactivation, the UE may restart the on-duration timer (e.g., drx-onDurationTimer). The UE may determine the DRX cycle based on a formula using the length/duration of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) and the start offset of the DRX cycle (e.g., drx-StartOffset). In other words, the UE may restart the on-duration timer at a timing calculated based on the information indicated by the indication and/or the indication of activation/deactivation (e.g., with the start offset) in association (e.g., using the information indicated by the indication and/or the indication of activation/deactivation based on a formula). In response to receiving the indication and/or the indication of activation/deactivation, the UE may stop (all) inactive timers (e.g., drx-InactivityTimer). In response to receiving the indication and/or the indication of activation/deactivation, the UE may not stop (any of) the inactive timer (e.g., drx-InactivityTimer), for example, keeping the timer running. In response to receiving the indication and/or the indication of activation/deactivation, the UE may restart (all) inactive timers (e.g., drx-InactivityTimer). In response to receiving the indication and/or the indication of activation/deactivation, the UE may start the inactive timer (e.g., drx-InactivityTimer).

In response to receiving the indication and/or the indication of activation/deactivation, the UE may not stop (either of) the retransmission timer (e.g., drx-RetransmissionTimerDL and/or drx-RetransmissionTimerUL), for example, keep the timer running. In response to receiving the indication and/or the indication of activation/deactivation, the UE may not stop (either of) the RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL), for example, keep the timer running.

The UE may, in response to receiving an indication to activate another DRX configuration (set), not stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) associated with the DRX configuration (set), for example by keeping the timer running.

The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) associated with (a set of) DRX configurations in response to:

- receiving an indication to deactivate a (set of) DRX configurations or switch from a (set of) DRX configurations to another (set of) DRX configurations; or

- transmitting a confirmation of said indication.

The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after receiving the indication and/or the indication of activation/deactivation. The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after transmitting a confirmation of the indication and/or the indication of activation/deactivation. The UE may stop an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) after using/activating/deactivating the indicated DRX configuration (set).

For example, as shown in FIG. 17 , the UE may receive an L1/L2 indication to adjust a DRX parameter (e.g., drx-StartOffset, drx-SlotOffset), for example, at timing a. The UE may transmit an acknowledgement (e.g., ACK) in response to receiving the L1/L2 indication, for example, at timing b. The UE may stop or (re)start the DRX timer in response to receiving the L1/L2 indication or transmitting the ACK.

In one example, the UE may restart the DRX timer (e.g., drx-onDurationTimer) at a timing indicated by the L1/L2 indication (e.g., timing c in FIG. 17 ). The timing c is calculated based on the value of drx-StartOffset or drx-SlotOffset indicated by the L1/L2 indication.

In one example, the UE may stop a DRX timer (e.g., drx-onDurationTimer and/or drx-InactivityTimer) in response to (or at/after) receipt of an L1/L2 indication. The UE may stop a DRX timer (e.g., drx-onDurationTimer and/or drx-InactivityTimer) at timing a in FIG. 17 . The UE may start drx-onDurationTimer at a timing indicated by the L1/L2 indication (e.g., timing c in FIG. 17 ). Timing c is calculated based on the value of drx-StartOffset or drx-SlotOffset indicated by the L1/L2 indication.

In one example, the UE may stop the DRX timer (e.g., drx-onDurationTimer and/or drx-InactivityTimer) in response to the transmission of the ACK (or at this time/after). The UE may stop the DRX timer (e.g., drx-onDurationTimer and/or drx-InactivityTimer) at timing b in FIG. 17 . The UE may start the drx-onDurationTimer at a timing indicated by the L1/L2 indication (e.g., timing c in FIG. 17 ). The timing c is calculated based on the value of the drx-StartOffset or drx-SlotOffset indicated by the L1/L2 indication.

All concepts, embodiments and examples described above and herein may be combined into new concepts and/or new concept combinations.

The multiple DRX parameters/configurations (sets) may be used for unicast. The multiple DRX parameters/configurations (sets) may not be used by multicast. The multiple DRX parameters/configurations (sets) may be used for downlink. The multiple DRX parameters/configurations (sets) may not be related to the sidelink.

The DRX configurations, sets of (multiple) DRX configurations, default DRX configurations (sets) and/or additional DRX configurations (sets) mentioned above and herein may be configured for (the same) serving cell (sets). The DRX configurations, sets of (multiple) DRX configurations, default DRX configurations (sets) and/or additional DRX configurations (sets) mentioned above and herein may be configured for one or more XR services.

The UE may receive DRX-related parameters and/or configurations, for example, in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration) from the network. The UE may receive RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration) in RRC inactive mode, RRC idle mode, and/or RRC connected mode.

The UE in this document may refer to the UE, a MAC entity of the UE, a HARQ entity of the UE, or an RRC entity of the UE.

The UE herein may be a NR device. The UE herein may be a NR light device. The UE herein may be a device with insufficient capabilities. The UE herein may be a mobile phone. The UE herein may be a wearable device. The UE herein may be a sensor. The UE herein may be a fixed device. The UE herein may be a head mounted display (HMD).

The network in this article may be a network node. The network in this article may be a base station. The network in this article may be an access point. The network in this article may be an eNB. The network in this article may be a gNB. The network in this article may be a gateway.

18 , regarding such and other concepts, systems, and methods of the present invention, a method 1030 for a UE in a wireless communication system includes receiving an RRC message including multiple DRX configurations (step 1032), receiving an indication of one or more DRX configurations from the multiple DRX configurations (step 1034), and performing PDCCH monitoring using the one or more DRX configurations (step 1036).

In various embodiments, the plurality of DRX configurations comprises one or more lists of DRX parameters in (or associated with) DRX groups and/or information elements.

In various embodiments, the plurality of DRX configurations comprises one or more lists of combinations of DRX parameters in (or associated with) DRX groups and/or information elements.

In various embodiments, the plurality of DRX configurations include one or more DRX groups and/or information elements.

In various embodiments, the indication is a DCI and/or a MAC CE.

In various embodiments, in response to receiving the indication, the UE switches to the one or more DRX configurations.

In various embodiments, in response to receiving the indication, the UE activates the one or more DRX configurations.

Referring now to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, an apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive an RRC message including a plurality of DRX configurations; (ii) receive an indication of one or more DRX configurations from the plurality of DRX configurations; and (iii) perform PDCCH monitoring using the one or more DRX configurations. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

Referring now to FIGS. 3 and 4 , in one or more embodiments from the perspective of the NW, the apparatus 300 includes a program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) transmit an RRC message including a plurality of DRX configurations to the UE; (ii) transmit an indication of one or more DRX configurations from the plurality of DRX configurations to the UE; and (iii) wherein the UE performs PDCCH monitoring using the one or more DRX configurations. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

The UE may be configured to transmit a sounding reference signal (SRS) for the network to estimate the UL channel state, and may be configured to report channel state information (CSI) for the network to adapt DL transmission. Based on [3] 3GPP TS 38.321 V17.0.0, if the UE will not be in the DRX action time, the UE may not transmit periodic SRS and semi-persistent SRS. If the UE will not be in the DRX action time, the UE may not report the semi-persistent CSI configured on the PUSCH. When CSI masking (e.g., csi-Mask) is set to true, if the UE will not be in the on-duration, the UE may not report CSI on the physical uplink control channel (PUCCH). When CSI masking (e.g., csi-Mask) is set to false, if the UE will not be in the DRX action time, the UE may not report CSI on the PUCCH. The DRX action time may include at least an on-duration, an inactive time, a retransmission time, an RA contention resolution time (e.g., when ra-ContentionResolutionTimer or msgB-ResponseWindow is running), a duration during which a PDCCH indicating a new transmission addressed to a cell radio network temporary identifier (C-RNTI) has not been received after successful reception of a random access response for contention-free random access, and/or a duration during which a scheduling request is sent on a PUCCH and is pending. The conditions for the DRX action time may include at least the following:

- The drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running;

-drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on any serving cell in the DRX group;

-ra-ContentionResolutionTimer or msgB-ResponseWindow is running;

- a scheduling request is sent on the PUCCH and is pending; and/or

- Indicating that a newly transmitted PDCCH addressed to the C-RNTI of the MAC entity has not been received after successfully receiving a random access response of a random access preamble that was not selected by the MAC entity among contention-based random access preambles.

For symbol n, if the UE is not in DRX action time (for a DRX group) considering the (received) UL grant, DL assignment, DRX command and/or scheduling request (SR) transmission until 4 ms before symbol n, then the UE will not transmit/report periodic SRS, semi-persistent SRS, semi-persistent CSI configured on the physical uplink shared channel (PUSCH) and/or CSI on PUCCH (for a DRX group).

For symbol n, if the UE will not be in the On-Duration (for the DRX group) considering the (received) UL grants, DL assignments, DRX commands and/or SR transmissions up to 4 ms before symbol n, the UE will not report CSI (for the DRX group) on the PUCCH.

When determining the conditions for transmitting SRS and/or CSI reports and/or evaluating the DRX action time, the UE may consider DL reception (e.g., UL grant, DL assignment, DRX command) and/or SR transmission up to 4 ms before symbol n to determine whether the UE is in the DRX action time and/or on duration. The UE may start an inactivity timer (e.g., drx-InactivityTimer) and/or an RTT timer (e.g., drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL) in response to receiving an UL grant and/or a DL assignment. The UE may enter the inactivity time and/or retransmission time after (or in response to) receiving an UL grant and/or a DL assignment. The UE may stop (all) inactivity timers (e.g., drx-InactivityTimer) and/or on duration timers (e.g., drx-onDurationTimer) in response to receiving a DRX command (e.g., DRX command MAC CE, long DRX command MAC CE). The UE may leave the inactive time and/or the on-duration after (or in response to) receiving a DRX command (eg, a DRX command MAC CE, a long DRX command MAC CE).

Considering XR service characteristics (e.g., periodicity, jitter, latency, and/or reliability), XR is beneficial over power saving techniques. In order to reduce PDCCH monitoring and thus reduce power consumption for XR services, it may be necessary to properly align the on-duration and/or DRX cycle with the XR DL traffic arrival time (e.g., with jitter). The network may dynamically modify the DRX configuration for XR services, which may result in unexpected on-durations for UEs to transmit SRS and/or CSI reports.

To solve the problem, the UE may determine whether to transmit (periodic and/or semi-persistent) SRS (in the DRX group) based on the indication (associated with the DRX group). The UE may determine whether to report (periodic and/or semi-persistent) CSI (in the DRX group) based on the indication (associated with the DRX group). When evaluating the DRX action time and/or the on-duration, or when determining to transmit the SRS and/or CSI report (in symbol n), the UE may consider the indication (e.g., the first indication, the second indication, the third indication) received until the duration before symbol n (e.g., for the serving cell). When evaluating the DRX action time and/or the on-duration, or when determining to transmit the SRS and/or CSI report (in symbol n), the UE may not consider the indication received in the duration before symbol n (e.g., for the serving cell). The indication may be (at least) the first indication, the second indication and/or the third indication. The indication (e.g., the first indication, the second indication, the third indication) may instruct the UE to adjust, modify, reconfigure, switch, activate and/or deactivate one or more DRX configurations (sets). The indication (e.g., the first indication, the second indication, the third indication) may indicate that the UE applies/uses one or more DRX configurations (sets) different from the DRX configurations (sets) used by the UE before receiving the indication. The indication (e.g., the first indication, the second indication, the third indication) may be a DCI, a MAC CE, and/or an RRC message. The indication (e.g., the first indication, the second indication, the third indication) may be used for an XR service. The indication (e.g., the first indication, the second indication, the third indication) may be used for a specific flow of an XR service.

The UE may receive one or more DRX configurations (sets), for example in an RRC message (e.g., RRCSetup, RRCResume, RRCReconfiguration). The UE may be (pre-)configured with one or more DRX configurations (sets) (e.g., for different on-durations and/or DRX cycles). The DRX configurations (sets) may be associated with the same serving cell, for example, for controlling PDCCH monitoring in the serving cell. The UE may use some or all of the multiple DRX configurations (sets) simultaneously, for example, for a serving cell. The UE may use more than one DRX configuration (set) simultaneously, for example, for a serving cell. More than one DRX configuration (set) may be activated simultaneously. The UE may use only one DRX configuration (set) simultaneously, for example, for a serving cell.

The (set of) multiple DRX configurations may be and/or be referred to as (set of) multiple DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The UE may receive and/or be (pre) configured with a list of DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The UE may receive and/or be (pre) configured with a list of combinations of DRX parameters/configurations in (or associated with) an information element (e.g., DRX-Config) of a DRX group and/or DRX configuration. The DRX parameter/configuration may be drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer. The combination of DRX parameters/configurations may include drx-SlotOffset, drx-onDurationTimer, drx-StartOffset, drx-LongCycle, drx-ShortCycle and/or drx-ShortCycleTimer. The (set of) multiple DRX configurations may be and/or referred to as multiple/different DRX groups and/or information elements of DRX configurations. A DRX group may be and/or referred to as an information element (DRX configuration) configured by the network (e.g., DRX-Config, DRX-ConfigSecondaryGroup and/or additional DRX group).

The multiple DRX configurations (sets) may include a default DRX configuration (set) and/or an additional DRX configuration (set). The additional DRX configuration (set) may be used by the UE simultaneously with the default DRX configuration (set). The default DRX configuration (set) may be deactivated by the network. The default DRX configuration (set) may not (be allowed to) be deactivated by the network, for example, through a third indication. The default DRX configuration (set) may be used by the UE after configuration. The default DRX configuration (set) may include at least one parameter (e.g., drx-InactivityTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) that is not included in the additional DRX configuration (set). For example, in DRX operation, the UE uses a first parameter (e.g., drx-StartOffset) in the additional DRX configuration (set) and a second parameter (e.g., drx-HARQ-RTT-TimerDL) in the default DRX configuration (set). The UE may or may not use the first parameter in the default DRX configuration (set) for DRX operation.

The UE may receive a first indication (e.g., via DCI, MAC CE) to modify and/or reconfigure a (set of) DRX configurations (e.g., for a DRX group). In response to receiving the first indication, the UE may reconfigure and/or adjust an on-duration and/or a DRX cycle (e.g., for a DRX group). In response to receiving the first indication, the UE may reconfigure and/or adjust a start offset to the on-duration (e.g., drx-SlotOffset), a length of the on-duration (e.g., drx-onDurationTimer), a length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle (of drx-LongCycleStartOffset), a start offset of the DRX cycle (e.g., drx-StartOffset (of drx-LongCycleStartOffset), and/or a duration of using a short DRX cycle (e.g., drx-ShortCycleTimer). The first indication may include and/or indicate a value of one or more (sets of) DRX configurations. The UE may replace the value of the (set of) DRX configurations with the indicated value. The first indication may include and/or indicate a relative value (e.g., an offset and/or a scale) to be applied to the (set of) one or more DRX configurations. The UE may add an offset to the value of the (set of) one or more DRX configurations. The UE may multiply the value of the (set of) one or more DRX configurations by a scale.

The UE may receive a second indication (e.g., via DCI, MAC CE) to (dynamically/temporarily) modify, shift, and/or adjust a (set of) DRX configurations. In response to receiving the second indication, the UE may apply the information indicated/included by the second indication to the (set of) DRX configurations. In response to receiving the second indication, the UE may shift/adjust the on-duration and/or (part of) the DRX cycle (based on the information indicated/included by the second indication). In response to receiving the second indication, the UE may shift/adjust the start offset (e.g., drx-SlotOffset) of the on-duration, the length of the on-duration (e.g., drx-onDurationTimer), the start offset (e.g., drx-StartOffset) of the DRX cycle, the length of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle), and/or the duration of using a short DRX cycle (e.g., drx-ShortCycleTimer). The UE may replace the value of the (set of) DRX configuration with the indicated value in the second indication. The UE may add the offset indicated in the second indication to the value of the (set of) DRX configuration. The UE may multiply the value of the (set of) DRX configuration by the scale indicated in the second indication. The value of the (set of) DRX configuration before receiving the second indication may be restored/used after the applicable time of the second indication, for example after the duration or after a single/specific on-duration and/or DRX cycle.

The UE may receive a third indication (e.g., via DCI, MAC CE) to switch, activate and/or deactivate a (set of) DRX configurations. The UE may use (or switch to) the indicated (activated) DRX configuration (set) based on the third indication. The UE may use and/or switch to the indicated DRX configuration (set) to perform DRX operations, such as PDCCH monitoring in a serving cell. The UE may activate and/or deactivate the indicated DRX configuration (set) based on the third indication. The DRX configuration (set) used before receiving the third indication to switch the DRX configuration (set) may be activated/used after the applicable time of the third indication, such as after the duration or after a single/specific on-duration and/or DRX cycle.

In response to receiving the indication (eg, the first indication, the second indication, the third indication), the UE may transmit an acknowledgement (eg, ACK) to the NW. The acknowledgement may be UCI, MAC CE and/or UAI.

The UE may monitor the indication (e.g., the first indication, the second indication, the third indication) during the DRX action time of the associated DRX group and/or DRX configuration. Alternatively, the UE may monitor the indication (e.g., the first indication, the second indication, the third indication) when the drx-onDurationTimer of the associated DRX group and/or DRX configuration is in operation. The UE may not monitor the indication (e.g., the first indication, the second indication, the third indication) outside the DRX action time of the associated DRX group and/or DRX configuration. Alternatively, the UE may not monitor the indication (e.g., the first indication, the second indication, the third indication) when the drx-onDurationTimer of the associated DRX group and/or DRX configuration is not in operation.

In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may stop one or more DRX timers of the associated DRX group and/or DRX configuration. In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may stop the on-duration timer (e.g., drx-onDurationTimer). In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may not stop the on-duration timer (e.g., drx-onDurationTimer), for example, keeping the timer running. In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may restart the on-duration timer (e.g., drx-onDurationTimer). The UE may determine the DRX cycle based on a formula using the length/duration of the DRX cycle (e.g., drx-ShortCycle, drx-LongCycle) and the start offset of the DRX cycle (e.g., drx-StartOffset). In other words, the UE may restart the on-duration timer at a timing calculated based on the information indicated by the indication (e.g., associated with the start offset) (e.g., based on a formula using the information indicated by the indication). In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may suspend the on-duration timer (e.g., drx-onDurationTimer) (for the timer duration, and then resume the timer). In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may stop (all) inactive timers (e.g., drx-InactivityTimer). In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may not stop (any of) the inactive timer (e.g., drx-InactivityTimer), for example, keep the timer running. In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may restart (all) inactive timers (e.g., drx-InactivityTimer). In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may start an inactivity timer (e.g., drx-InactivityTimer). The UE may stop the on-duration timer (e.g., drx-onDurationTimer) and/or the inactivity timer (e.g., drx-InactivityTimer) after receiving the indication (e.g., the first indication, the second indication, the third indication). The UE may stop the on-duration timer (e.g., drx-onDurationTimer) and/or the inactivity timer (e.g., drx-InactivityTimer) after transmitting a confirmation of the indication (e.g., the first indication, the second indication, the third indication).

In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may not stop the retransmission timer (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) (any one of them), for example, keep the timer running. In response to receiving the indication (e.g., the first indication, the second indication, the third indication), the UE may not stop the RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) (any one of them), for example, keep the timer running.

When the UE determines to transmit the SRS and/or CSI report in symbol n or not, the UE may consider (at least) the indication (e.g., the first indication, the second indication, the third indication) received and/or applied (e.g., for the serving cell) until/before a specific timing. When the UE determines to transmit the SRS and/or CSI report in symbol n or not, the UE may not consider (at least) the indication (e.g., the first indication, the second indication, the third indication) received and/or applied (e.g., for the serving cell) within/after a specific timing. When the UE evaluates the DRX action time and/or the on-duration for determining to transmit the SRS and/or CSI report or not, the UE may consider (at least) the indication (e.g., the first indication, the second indication, the third indication) received and/or applied (e.g., for the serving cell) until/before a specific timing. When the UE evaluates the DRX action time and/or the on-duration for determining whether to transmit an SRS and/or CSI report or not, the UE may not consider (at least) an indication (e.g., a first indication, a second indication, a third indication) received and/or applied (e.g., for a serving cell) within/after a specific timing. The specific timing may be a duration before symbol n. The duration may be 4 ms. The duration may be longer than 4 ms. The duration may be indicated in the indication (e.g., a first indication, a second indication, a third indication). The duration may be preconfigured by the network.

The UE may determine whether to transmit the SRS and/or CSI report based on the reception of an indication (e.g., a first indication, a second indication, a third indication). The UE may determine whether to transmit the SRS and/or CSI report based on the information of the indication (e.g., a first indication, a second indication, a third indication). The UE may not determine whether to transmit the SRS and/or CSI report based on the reception of the indication (e.g., a first indication, a second indication, a third indication). The UE may determine whether symbol n is in the DRX action time and/or the on-duration based on the reception of the indication (e.g., a first indication, a second indication, a third indication). The UE may determine whether symbol n is in the DRX action time and/or the on-duration based on the information of the indication (e.g., a first indication, a second indication, a third indication). The UE may not determine whether symbol n is in the DRX action time and/or the on-duration based on the reception of the indication (e.g., a first indication, a second indication, a third indication).

If symbol n is (deemed/determined to be) in the DRX active time and/or the on-duration, the UE may determine to transmit the SRS and/or CSI report. If symbol n is not (deemed/determined to be) in the DRX active time and/or the on-duration, the UE may determine not to transmit the SRS and/or CSI report.

For example, if the indication (e.g., first indication, second indication, third indication) is received and/or applied (e.g., for a serving cell) before a specific timing, the UE can determine, consider and/or evaluate that symbol n is not in the DRX action time and/or the on-duration. As shown in Figure 19, the UE can receive or apply the indication before a specific timing (e.g., the duration before symbol n). The time interval from the UE receiving or applying the indication to symbol n can be longer than and/or equal to the duration. The UE may not transmit SRS and/or CSI reports in symbol n. Alternatively, if the indication (e.g., first indication, second indication, third indication) is received and/or applied after a specific timing (e.g., for a serving cell), the UE can determine, consider and/or evaluate that symbol n is in the DRX action time and/or the on-duration. As shown in Figure 20, the UE can receive or apply the indication after a specific timing (e.g., the duration before symbol n). The time interval from the UE receiving or applying the indication to symbol n can be shorter than the duration. The UE can transmit SRS and/or CSI reports in symbol n. The UE may stop, for example, an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) associated with the DRX configuration in response to receiving/applying the indication (e.g., the first indication, the second indication, the third indication).

For example, if the indication (e.g., first indication, second indication, third indication) is received and/or applied (e.g., for a serving cell) before a specific timing, the UE may determine, consider and/or evaluate that symbol n is in the DRX action time and/or the on-duration. The UE may transmit an SRS and/or CSI report in symbol n. Alternatively, if the indication (e.g., first indication, second indication, third indication) is received and/or applied (e.g., for a serving cell) after a specific timing, the UE may determine, consider and/or evaluate that symbol n is not in the DRX action time and/or the on-duration. The UE may not transmit an SRS and/or CSI report in symbol n. The UE may restart, for example, an on-duration timer (e.g., drx-onDurationTimer) and/or an inactivity timer (e.g., drx-InactivityTimer) associated with the DRX configuration in response to receiving/applying the indication (e.g., first indication, second indication, third indication). The UE may start, in response to receiving/applying the indication (eg, the first indication, the second indication, the third indication), an inactivity timer (eg, drx-InactivityTimer) associated with, for example, the DRX configuration.

For example, if a second indication is received indicating that the UE activates and/or resumes an on-duration timer (e.g., drx-onDurationTimer) associated with, for example, a DRX configuration, then the UE may determine, consider, and/or evaluate that symbol n is in the DRX action time and/or on-duration. The UE may start the on-duration timer (e.g., drx-onDurationTimer) in response to receiving the second indication. The UE may transmit an SRS and/or CSI report in symbol n.

For example, if a second indication is received indicating that the UE deactivates and/or suspends an on-duration timer (e.g., drx-onDurationTimer), the UE may determine, consider, and/or evaluate that symbol n is not in the DRX action time and/or on-duration. The UE may stop the on-duration timer (e.g., drx-onDurationTimer) in response to receiving the second indication. The UE may transmit an SRS and/or CSI report in symbol n.

For example, the UE may be configured to transmit (periodic and/or semi-persistent) SRS in symbol n in the serving cell. If, in response to an indication received until a duration before symbol n, the MAC entity associated with the serving cell will not be in action time, the UE may not transmit SRS in symbol n in the serving cell. If an indication associated with the serving cell is not received until a duration before symbol n, but is received within a duration before symbol n, the UE may transmit SRS in symbol n in the serving cell.

For example, the UE may be configured to report (periodically and/or semi-persistently) CSI in symbol n in the serving cell. If, in response to an indication received until a duration before symbol n, the MAC entity associated with the serving cell will not be in action time, the UE may not transmit CSI in symbol n in the serving cell. If an indication associated with the serving cell is not received until a duration before symbol n, but is received within a duration before symbol n, the UE may transmit CSI in symbol n in the serving cell.

For a MAC entity, one or more or all of the following conditions may be met:

-DCP monitoring can be configured for active DL BWP;

- symbol n may occur within the duration of drx-onDurationTimer (e.g., while drx-onDurationTimer is running);

- The drx-onDurationTimer associated with the current DRX cycle may not be started;

-ps-TransmitPeriodicL1-RSRP may not be configured with a value of true; and/or

-ps-TransmitOtherPeriodicCSI may not be configured with a value of true.

For example, the UE may be configured to transmit (periodic and/or semi-persistent) SRS in symbol n in the serving cell. If, in response to an indication received until a duration before symbol n, the DRX group associated with the serving cell will not be in an active time, the UE may not transmit SRS in symbol n in the serving cell. If an indication associated with the serving cell is not received until a duration before symbol n, but is received within a duration before symbol n, the UE may transmit SRS in symbol n in the serving cell.

For example, the UE may be configured to report (periodic and/or semi-persistent) CSI in symbol n in the serving cell. If, in response to an indication received until a duration before symbol n, the DRX group associated with the serving cell will not be in an active time, the UE may not transmit CSI in symbol n in the serving cell. If an indication associated with the serving cell is not received until a duration before symbol n, but is received within a duration before symbol n, the UE may transmit CSI in symbol n in the serving cell.

For example, the UE may be configured to report (periodic and/or semi-persistent) CSI in symbol n in the serving cell. If, in response to an indication received until a duration before symbol n, the drx-onDurationTimer of the DRX group associated with the serving cell will not be running, then the UE may not transmit CSI in symbol n in the serving cell. If an indication associated with the serving cell is not received until a duration before symbol n, but is received within a duration before symbol n, then the UE may transmit CSI in symbol n in the serving cell.

For a DRX group, one or more or all of the following conditions may not be met:

- DCP monitoring can be configured for active DL BWP;

- symbol n may occur within the drx-onDurationTimer duration (e.g., while drx-onDurationTimer is running); and/or

- The drx-onDurationTimer associated with the current DRX cycle may not be started.

For a DRX group, one or more or all of the following conditions may be met:

-CSI mask (csi-Mask) can be set;

- allowCSI-SRS-Tx-MulticastDRX-Active may not be configured; and/or

- All multicast DRX may not be in active time in symbol n.

The UE may determine, consider and/or evaluate whether the symbol n is in the DRX active time and/or the on-duration based on the information of the indication (eg, the first indication, the second indication, the third indication).

The UE may apply the information of the indication (eg, the first indication, the second indication, the third indication) and determine/consider/evaluate whether the symbol n is in the DRX action time and/or the on-duration based on at least the following:

- the indicated value of (a set of) one or more DRX configurations in the first/second indication;

- the value of (the set of) one or more DRX configurations in the first/second indication plus an offset;

- the value of (the set of) one or more DRX configurations in the first/second indication is multiplied by a scale;

-(a set of) DRX configurations indicated/activated/deactivated by a third indication; and/or

- The time when the second and/or third instructions apply.

For example, the UE may determine, consider and/or evaluate whether symbol n is in the DRX action time and/or the on-duration based on the modified/reconfigured/indicated DRX configuration (set). The UE may modify/reconfigure/switch the DRX configuration (set) based on the information of the indication (e.g., the first indication, the second indication, the third indication).

In response to receiving the first indication, the UE may use/apply the new configuration and/or adjust/reconfigure the DRX configuration at or after the first timing. In response to receiving the second indication, the UE may apply the information of the second indication and/or shift/adjust the DRX configuration at or after the first timing (start (temporarily)). In response to receiving the third indication, the UE may use and/or activate/deactivate the indicated/corresponding DRX configuration (set) at or after (at least one of) the first timing. The first timing may be (at least one of) the following:

- Receipt of a (first/second/third) indication (first symbol thereafter);

- the transmission of said acknowledgement (first symbol thereafter);

- a specific PDCCH opportunity (e.g. indicated in a (first/second/third) indication predefined in the standard);

- a time delay (afterwards) (e.g. indicated in a (first/second/third) indication predefined in the standard); and/or

- When a timer associated with the DRX configuration is (re)started.

The UE may use the received/indicated value in the first indication as (the value of) the DRX configuration after receiving the first indication, after transmitting an acknowledgment of the first indication and/or from/after a specific PDCCH opportunity. The UE may use the received/indicated value in the first indication as (the value of) the DRX configuration after a time delay from the reception of the first indication and/or the transmission of the acknowledgment.

The UE may apply the offset and/or scale to the DRX configuration (value) after receiving the first indication, after transmitting an acknowledgement of the first indication, and/or from a specific PDCCH opportunity. The UE may apply the offset and/or scale to the DRX configuration (value) after a time delay from the reception of the first indication and/or the transmission of the acknowledgement.

The UE may apply the information indicated/included by the second indication to the DRX configuration (eg, shifting/adjusting the on-duration and/or the DRX cycle) after receiving the second indication, after transmitting a confirmation of the second indication and/or from a specific timing.

In response to receiving the second indication and/or the third indication, the UE may stop applying the information of the second indication and/or the third indication at or after (at least one of) the following second timing sequences:

-Specific PDCCH occasions (e.g. indicated in an indication predefined in the standard);

- time delay (e.g. indicated in an indication predefined in a standard);

-Timer expires;

- several DL receptions; and/or

- A number of DRX cycles or On-Durations.

The applicable time of the second indication and/or the third indication may be the duration between the first timing sequence and the second timing sequence.

The UE may determine, consider and/or evaluate whether the symbol n is in the DRX active time and/or the on-duration without considering the information of the indication (eg, the first indication, the second indication, the third indication).

For example, the UE may determine, consider and/or evaluate whether symbol n is in the DRX action time and/or on-duration based on the (set of) DRX configurations before receiving the indication (e.g., the first indication, the second indication, the third indication). The UE may determine, consider and/or evaluate whether symbol n is in the DRX action time and/or on-duration based on a value of the (set of) DRX configuration that is different from the value of the (set of) DRX configuration used in symbol n.

For example, the UE may determine, consider and/or evaluate whether symbol n is in the DRX action time and/or on-duration based on the (set of) default DRX configurations. The UE may determine, consider and/or evaluate whether symbol n is in the DRX action time and/or on-duration based on the value of the (set of) default DRX configurations.

The UE may transmit SRS and/or CSI reports for one or more (sets of) DRX configurations in a DRX group, for example, for a serving cell. The UE may transmit SRS and/or CSI reports for multiple (sets of) DRX configurations in a DRX group, for example, for a serving cell. The UE may transmit SRS and/or CSI reports for a default DRX configuration (set) in a DRX group, for example, for a serving cell. The UE may transmit SRS and/or CSI reports for (all) activated DRX configurations (sets) in a DRX group, for example, for a serving cell. The UE may transmit SRS and/or CSI reports for a specific DRX configuration (set) (e.g., indicated by the indication), for example, for a serving cell.

The multiple DRX parameters/configurations (sets) may be used for unicast. The multiple DRX parameters/configurations (sets) may not be used by multicast. The multiple DRX parameters/configurations (sets) may be used for downlink. The multiple DRX parameters/configurations (sets) may not be related to the sidelink. The UE may receive parameters and/or configurations related to SRS (e.g., SRS-Config) and/or CSI reports (e.g., CSI-ReportConfig, csi-Mask).

Throughout the present disclosure, SRS may include and/or be referred to as periodic SRS and/or semi-persistent SRS. Periodic SRS and/or semi-persistent SRS may be configured by an RRC message. Semi-persistent SRS may be activated and/or deactivated by a MAC CE (e.g., SP SRS activation/deactivation MAC CE).

Throughout this disclosure, "CSI report" may be, may refer to and/or may be replaced by "CSI". CSI (report) may include CSI (report) on PUCCH and/or (semi-persistent) CSI (report) configured on PUSCH. CSI (report) on PUCCH may include and/or be referred to as periodic CSI (report) on PUCCH and/or semi-persistent CSI (report) on PUCCH. Periodic CSI (report) on PUCCH and/or semi-persistent CSI (report) on PUCCH may be configured by RRC message. Semi-persistent CSI (report) on PUCCH may be activated and/or deactivated by MAC CE (e.g., PUCCH activates/deactivates SP CSI report on MAC CE). Semi-persistent CSI (report) configured on PUSCH may be indicated by DCI.

The following describes an example of the invention based on [3] 3GPP TS 38.321 V17.0.0:

1> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213 clause 10.3; and

1> If the current symbol n occurs within the duration of drx-onDurationTimer; and

1> If the drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:

2> If, when evaluating all DRX action time conditions specified in this clause, the MAC entity will not be in action time, taking into account the grant/assignment/DRX command MAC CE/long DRX command MAC CE /indication (mentioned above) received 4 ms before symbol n and the scheduling request sent, then:

3> Periodic SRS and semi-persistent SRS defined in TS 38.214 are not transmitted;

3> Do not report the semi-persistent CSI configured on PUSCH;

[…]

1> Otherwise:

2> In the current symbol n, if, when evaluating all DRX action time conditions specified in this clause, the DRX group shall not be in action time, taking into account the grant/assignment scheduled on the serving cell in this DRX group received 4 ms before symbol n and the DRX command MAC CE/long DRX command MAC CE /(mentioned above) indication and scheduling request sent; and

2> In the current symbol n, if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or when evaluating all DRX action time conditions specified in clause 5.7b, taking into account the multicast allocation and DRX command MAC CE for MBS multicast received 4 ms before symbol n, all multicast DRX will not be in action time, then:

3> Periodic SRS and semi-persistent SRS defined in TS 38.214 are not transmitted in this DRX group;

3> CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group are not reported.

2> If CSI mask (csi-Mask) is set by the upper layer, then:

3> In the current symbol n, if, while evaluating all DRX action time conditions specified in this clause, the grant/assignment scheduled on the serving cell in this DRX group and the DRX command MAC CE/long DRX command MAC CE /indication (mentioned above) received 4 ms before symbol n are taken into account, the drx-onDurationTimer of the DRX group shall not be running; and

4> CSI on PUCCH is not reported in this DRX group.

Another example of the invention based on [3] 3GPP TS 38.321 V17.0.0 is described below:

1> If a short DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle):

2> Start or restart the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

1> If a long DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset:

2> If DCP monitoring is configured for the active DL BWP as specified in TS 38.213 clause 10.3:

3> if a DCP indication is received from lower layers indicating to start the drx-onDurationTimer associated with the current DRX cycle, as specified in TS 38.213; or

3> If all DCP opportunities in the time domain associated with the current DRX cycle occur in the active time as specified in TS 38.213, consider the Grant/Assignment/DRX Command MAC CE/Long DRX Command MAC CE received and the Scheduling Request sent 4 ms before the start of the last DCP opportunity, or during a Measurement Gap, or when the MAC entity monitors PDCCH transmissions on the search space indicated by recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is in operation (as specified in clause 5.1.4); or

3> If ps-Wakeup is configured with a value of true and no DCP indication associated with the current DRX cycle is received from lower layers:

4> Start drx-onDurationTimer after drx-SlotOffset from the start of the subframe.

2> Otherwise:

3> Start or restart the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

21 , regarding such and other concepts, systems, and methods of the present invention, a method 1040 for a UE in a wireless communication system includes receiving an RRC message including a DRX configuration (step 1042), receiving an indication of one or more DRX configurations (step 1044), applying the indication to the one or more DRX configurations to perform PDCCH monitoring (step 1046), and determining whether to transmit SRS and/or CSI in symbol n based on the indication (step 1048).

In various embodiments, the UE determines whether to transmit SRS and/or CSI based on the timing when the indication is received and/or applied.

In various embodiments, if the indication is received and/or applied before the duration before symbol n, the UE does not transmit SRS and/or CSI.

In various embodiments, the UE transmits SRS and/or CSI if the indication is received and/or applied after a duration before symbol n.

In various embodiments, the duration is 4 ms.

Referring now to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, an apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive an RRC message including a DRX configuration; (ii) receive an indication of one or more DRX configurations; (iii) apply the indication to the one or more DRX configurations to perform PDCCH monitoring; and (iv) determine whether to transmit SRS and/or CSI in symbol n based on the indication. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

22 , regarding such and other concepts, systems, and methods of the present invention, a method 1050 for a UE in a wireless communication system includes: receiving first signaling configuring at least one value of a discontinuous reception (DRX) parameter (step 1052), receiving second signaling in a serving cell indicating a first value of the DRX parameter or a second value of the at least one value of the DRX parameter (step 1054), and performing at least one of the following (step 1056): adjusting a first DRX group or a second DRX group for the UE based on a target DRX group indicated in the second signaling or based on whether the serving cell is assigned to the first DRX group or the second DRX group; The method further comprises: step 1054 of: step 1055 , wherein the drx-onDurationTimer is restarted at a timing calculated based on a first value or a second value of the DRX parameter indicated in the second signaling in response to receiving the second signaling, stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing in response to receiving the second signaling, or stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing when or after transmitting an acknowledgment in response to receiving the second signaling (step 1058 ).

In various embodiments, the first signaling is a Radio Resource Control (RRC) message and/or the second signaling is downlink control information or a Medium Access Control (MAC) Control Element (CE).

In various embodiments, the DRX parameter is drx-StartOffset or drx-SlotOffset.

In various embodiments, restarting the drx-onDurationTimer is performed after transmitting the confirmation.

In various embodiments, the method further includes stopping the drx-InactivityTimer upon or after receiving the second signaling or upon or after transmitting the confirmation.

In various embodiments, the method further comprises adjusting the DRX parameter by applying the first value or the second value to the DRX parameter and/or activating or deactivating the DRX parameter with the first value or the second value.

In various embodiments, adjusting the DRX parameters is performed upon or after at least one of: receipt of the second signaling, transmission of an acknowledgment, a physical downlink control channel (PDCCH) timing indicated in the second signaling, or a time delay indicated in the second signaling.

In various embodiments, the method further comprises: if the target DRX group is the first DRX group, adjusting the DRX parameters for the first DRX group, and/or if the target DRX group is the second DRX group, adjusting the DRX parameters for the second DRX group.

In various embodiments, the method further comprises: if the serving cell is assigned to the first DRX group, adjusting the DRX parameters for the first DRX group, and/or if the serving cell is assigned to the second DRX group, adjusting the DRX parameters for the second DRX group.

In various embodiments, whether the serving cell is assigned to the first DRX group or the second DRX group is indicated in the first signaling.

In various embodiments, the first DRX group and the second DRX group are associated with the same MAC entity.

Referring now to FIGS. 3 and 4 , in one or more embodiments from the perspective of a UE, an apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. CPU 308 can execute program code 312 to: (i) receive first signaling configuring at least one value of a discontinuous reception (DRX) parameter; (ii) receive second signaling indicating a first value of the DRX parameter or a second value of the at least one value of the DRX parameter in a serving cell; and (iii) perform at least one of the following: (iv) adjust the DRX parameter of the first DRX group or the second DRX group for the UE based on the target DRX group indicated in the second signaling or based on whether the serving cell is assigned to the first DRX group or the second DRX group; restart the drx-onDurationTimer at a timing calculated based on the first value or the second value of the DRX parameter indicated in the second signaling in response to receiving the second signaling; stop the drx-onDurationTimer and start the drx-onDurationTimer at the timing in response to receiving the second signaling; or stop the drx-onDurationTimer and start the drx-onDurationTimer at the timing when or after transmitting a confirmation in response to receiving the second signaling. Furthermore, CPU 308 may execute program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

Any combination of the above concepts or teachings can be combined or formed into new embodiments. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.

It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and/or in combination with multiple methods, alternatives, steps, examples and embodiments.

Various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with a software module executed by a processor, or with a combination of the two. Software modules (e.g., including executable instructions and related data) and other data can reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of a computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer/processor (for convenience, the machine can be referred to as a "processor" in this article) so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium can be integrated with a processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium, and the computer-readable medium includes a code related to one or more of the various aspects of the present invention. In some aspects, a computer program product may include packaging materials.

Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63/339,274 filed on May 6, 2022, U.S. Provisional Patent Application No. 63/339,310 filed on May 6, 2022, U.S. Provisional Patent Application No. 63/339,339 filed on May 6, 2022, and U.S. Provisional Patent Application No. 63/339,354 filed on May 6, 2022, each of which is incorporated herein by reference in its entirety.

Claims (20)

1. A method for user equipment, characterized in that it includes: receiving first signaling configuring at least one value of the discontinuous reception parameter; receiving second signaling in the serving cell indicating the first value of the discontinuous reception parameter or the second value of the at least one value of the discontinuous reception parameter; and Do at least one of the following: Adjusting the DRX signal for the user equipment based on the target discontinuous reception group indicated in the second signaling or based on whether the serving cell is assigned to the first discontinuous reception group or the second discontinuous reception group. the discontinuous reception parameters of the first discontinuous reception group or the second discontinuous reception group; Responsive to receiving the second signaling, restart drx-onDurationTimer at a timing calculated based on the first value or the second value of the discontinuous reception parameter indicated in the second signaling; stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing in response to receiving the second signaling; or The drx-onDurationTimer is stopped and started at the timing when or after an acknowledgment is transmitted in response to receipt of the second signaling. 2. The method according to claim 1, characterized in that the first signaling is a radio resource control message and/or the second signaling is downlink control information or a media access control control element. 3. The method according to claim 1, characterized in that the discontinuous reception parameter is drx-StartOffset or drx-SlotOffset. 4. The method of claim 1, wherein restarting the drx-onDurationTimer is performed after transmitting the acknowledgment. 5. The method of claim 1, further comprising stopping drx-InactivityTimer when or after receiving the second signaling or when or after transmitting the acknowledgment. 6. The method of claim 1, further comprising applying said first value or said second value to said discontinuous reception parameter and/or activating or deactivating said first value. value or the second value of the discontinuous reception parameter to adjust the discontinuous reception parameter. 7. The method of claim 1, wherein adjusting the discontinuous reception parameters is performed when or after at least one of the following: Reception of the second signaling; Transmission of said confirmation; The physical downlink control channel timing indicated in the second signaling; or The time delay indicated in the second signaling. 8. The method of claim 1, further comprising, if the target discontinuous reception group is the first discontinuous reception group, adjusting for the first discontinuous reception group the discontinuous reception parameters, and/or if the target discontinuous reception group is the second discontinuous reception group, then adjusting the discontinuous reception for the second discontinuous reception group parameter. 9. The method of claim 1, further comprising, if the serving cell is assigned to the first discontinuous reception group, adjusting all signals for the first discontinuous reception group. the discontinuous reception parameters, and/or if the serving cell is assigned to the second discontinuous reception group, adjusting the discontinuous reception parameters for the second discontinuous reception group. 10. The method of claim 1, wherein whether the serving cell is assigned to the first discontinuous reception group or the second discontinuous reception group is determined in the first signaling indicated in. 11. The method of claim 1, wherein the first discontinuous reception group and the second discontinuous reception group are associated with the same media access control entity. 12. A user equipment, characterized in that it includes: memory; and a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: receiving first signaling configuring at least one value of the discontinuous reception parameter; receiving second signaling in the serving cell indicating the first value of the discontinuous reception parameter or the second value of the at least one value of the discontinuous reception parameter; and Do at least one of the following: Adjusting the DRX signal for the user equipment based on the target discontinuous reception group indicated in the second signaling or based on whether the serving cell is assigned to the first discontinuous reception group or the second discontinuous reception group. the discontinuous reception parameters of the first discontinuous reception group or the second discontinuous reception group; Responsive to receiving the second signaling, restart drx-onDurationTimer at a timing calculated based on the first value or the second value of the discontinuous reception parameter indicated in the second signaling; stopping the drx-onDurationTimer and starting the drx-onDurationTimer at the timing in response to receiving the second signaling; or The drx-onDurationTimer is stopped and started at the timing when or after an acknowledgment is transmitted in response to receipt of the second signaling. 13. The user equipment according to claim 12, wherein the first signaling is a radio resource control message and/or the second signaling is downlink control information or a media access control control element. 14. The user equipment according to claim 12, characterized in that the discontinuous reception parameter is drx-StartOffset or drx-SlotOffset. 15. The user equipment of claim 12, wherein restarting the drx-onDurationTimer is performed after transmitting the confirmation. 16. The user equipment of claim 12, wherein the processor is further configured to execute program code to stop on or after receiving the second signaling or on or after transmitting the acknowledgment. drx-InactivityTimer. 17. The user equipment of claim 12, wherein the processor is further configured to execute program code to generate the discontinuous reception parameter by applying the first value or the second value to the discontinuous reception parameter and the second value. /Or activate or deactivate the discontinuous reception parameter using the first value or the second value to adjust the discontinuous reception parameter. 18. The user equipment according to claim 12, characterized in that adjusting the discontinuous reception parameters is performed when or after at least one of the following: Reception of the second signaling; Transmission of said confirmation; The physical downlink control channel timing indicated in the second signaling; or The time delay indicated in the second signaling. 19. The user equipment of claim 12, wherein the processor is further configured to execute program code to: If the target discontinuous reception group is the first discontinuous reception group, adjusting the discontinuous reception parameters for the first discontinuous reception group; and/or If the target discontinuous reception group is the second discontinuous reception group, adjusting the discontinuous reception parameters for the second discontinuous reception group; and/or If the serving cell is assigned to the first discontinuous reception group, adjusting the discontinuous reception parameters for the first discontinuous reception group; and/or If the serving cell is assigned to the second discontinuous reception group, the discontinuous reception parameters for the second discontinuous reception group are adjusted. 20. The user equipment according to claim 12, characterized in that whether the serving cell is assigned to the first discontinuous reception group or the second discontinuous reception group is in the first signal. indicated in the order, and/or the first discontinuous reception group and the second discontinuous reception group are associated with the same medium access control entity.