Terminal device method, network device method, terminal device, and network device

Abstract

In the signaling flow for inter-device communication, the terminal device receives multiple discontinuous receive (DRX) settings for a serving cell or serving cell group from the network device, detects a power saving instruction signal within a monitoring window, and starts an on-time interval timer based on the detection of the power saving instruction signal. [Effect] Power consumption is reduced in terminal devices that receive multiple DRX settings.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to communication methods, devices, and computer storage media.

Background Art

[0002] Several techniques have been proposed to improve communication performance. Discontinuous reception (DRX) is a method adopted in various radio technologies to enable a terminal device to turn off its receiver during inactive periods. DRX can be adopted in both the RRC idle mode and the RRC connected mode. In a communication system, a terminal device is configured to use DRX to reduce power consumption, and the terminal device is expected to monitor one paging occasion (PO) per DRX cycle. In the RRC idle mode, the DRX cycle is based on the paging cycle because the terminal device is expected to receive only paging messages. In the RRC connected mode, the terminal device needs to monitor the physical downlink control channel (PDCCH) search space for possible indications of incoming traffic.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Generally, embodiments of the present disclosure provide a method, a device, and a computer storage media for communication.

Means for Solving the Problems

[0004] In a first embodiment, a method of communication is provided. The method includes: a terminal device receiving a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device; the terminal device determining one set of target DRX timers or one set of target DRX settings from the plurality of DRX settings; and the terminal device monitoring a physical downlink control channel (PDCCH) based on the one set of target DRX timers or one set of target DRX settings.

[0005] In a second embodiment, a terminal device is provided. The terminal device comprises a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the terminal device to perform operations including: receiving a plurality of discontinuous reception (DRX) settings from a network device for a serving cell or a group of serving cells; determining one set of target DRX timers or one set of target DRX settings from the plurality of DRX settings; and monitoring a physical downlink control channel (PDCCH) based on the one set of target DRX timers or the one set of target DRX settings.

[0006] In a third embodiment, a method of communication is provided. The method includes a terminal device receiving a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device; the terminal device detecting a power saving instruction signal within a monitoring window associated with one or more of the plurality of DRX settings; and, based on the detection of the power saving instruction signal, starting a DRX on time interval timer for the plurality of DRX settings.

[0007] In a fourth embodiment, a method of communication is provided. The method includes: a terminal device receiving a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device; a terminal device receiving a search space set group (SSSG) setting for each DRX setting from the network device; and a terminal device monitoring a physical downlink control channel (PDCCH) based on one or more search space set groups (SSSGs) within overlapping on-time interval windows of the plurality of DRX settings.

[0008] In a fifth embodiment, a terminal device is provided. The terminal device comprises a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, include: the terminal device receiving a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device; the terminal device detecting a power saving instruction signal within a monitoring window associated with one or more of the plurality of DRX settings; and, based on the detection of the power saving instruction signal, starting a DRX on time interval timer for the plurality of DRX settings.

[0009] In a sixth embodiment, a terminal device is provided. The terminal device comprises a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the terminal device to perform operations including: receiving a plurality of discontinuous reception (DRX) settings from a network device for a serving cell or serving cell group; receiving a search space set group (SSSG) setting from the network device for each DRX setting; and monitoring a physical downlink control channel (PDCCH) based on one or more search space set groups (SSSGs) within overlapping on-time interval windows of the plurality of DRX settings.

[0010] In a seventh embodiment, a method of communication is provided. The method includes, in a network device, transmitting a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group, and transmitting a search space set group (SSSG) setting for each DRX setting.

[0011] In an eighth embodiment, a network device is provided. The network device comprises a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the network to perform an operation including transmitting a plurality of discontinuous receive (DRX) settings for a serving cell or serving cell group in the network device, and transmitting a search space set group (SSSG) setting for each DRX setting.

[0012] In a ninth embodiment, a computer-readable medium storing instructions is provided. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform the method according to the first, third, fourth, or seventh embodiment of the present disclosure.

[0013] Other features of this disclosure should be easily understood from the following explanation. [Brief explanation of the drawing]

[0014] The above-mentioned and other objectives, features, and advantages of this disclosure will be further clarified by describing in more detail some embodiments of this disclosure in the attached drawings.

[0015] [Figure 1] This is a schematic diagram of a communication environment in which the embodiments of this disclosure can be implemented.

[0016] [Figure 2] This figure shows a signaling flow for inter-device communication according to some embodiments of the present disclosure.

[0017] [Figure 3] This is a schematic diagram of the DRX settings according to some embodiments of the present disclosure.

[0018] [Figure 4] This is a schematic diagram of the DRX settings according to some embodiments of the present disclosure.

[0019] [Figure 5] This is a schematic diagram of the DRX settings according to some embodiments of the present disclosure.

[0020] [Figure 6] This is a schematic diagram of the DRX settings according to some embodiments of the present disclosure.

[0021] [Figure 7]A diagram showing a signaling flow for inter-device communication according to some embodiments of the present disclosure.

[0022] [Figure 8] A schematic diagram of a DRX setting according to some embodiments of the present disclosure.

[0023] [Figure 9] A schematic diagram of a DRX setting according to some embodiments of the present disclosure.

[0024] [Figure 10] A diagram showing a signaling flow for inter-device communication according to some embodiments of the present disclosure.

[0025] [Figure 11] A schematic diagram of a DRX setting according to some embodiments of the present disclosure.

[0026] [Figure 12] A flowchart of an exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0027] [Figure 13] A flowchart of an exemplary communication method implemented in a network device according to some embodiments of the present disclosure.

[0028] [Figure 14] A flowchart of an exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0029] [Figure 15] A flowchart of an exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0030] [Figure 16]This is a flowchart of an exemplary communication method implemented in a network device according to some embodiments of the present disclosure.

[0031] [Figure 17] This is a flowchart of an exemplary communication method implemented in a network device according to some embodiments of the present disclosure.

[0032] [Figure 18] This is a schematic block diagram of a device suitable for implementing an embodiment of the present disclosure.

[0033] In the diagram, identical or similar reference numbers represent identical or similar elements. [Modes for carrying out the invention]

[0034] The principles of this disclosure will now be explained with reference to several embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, and should be understood as not to imply any limitation on the scope of this disclosure. The disclosures described herein can be implemented in a variety of ways other than those described below.

[0035] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by those skilled in the art.

[0036] As used herein, the term “Terminal Device” refers to any device having wireless or wired communication capabilities. Examples of Terminal Devices include, but are not limited to, user devices (UEs), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Things (IoE) devices, machine-type communication (MTC) devices, and in-vehicle devices for V2X communication, where the “X” in V2X represents pedestrians, vehicles or infrastructure / networks, or image acquisition devices such as digital cameras, game devices, music storage and playback devices, or internet-connected home appliances that enable wireless or wired internet access and browsing. The term “Terminal Device” may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. The term “Network Device” refers to a device that can provide or host a cell or coverage on which a Terminal Device can communicate. Examples of network devices include, but are not limited to, low-power nodes such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), transmit / receive points (TRP), remote radio units (RRU), radio heads (RH), remote radio heads (RRH), femtonodes, and piconodes.

[0037] In one embodiment, a terminal device can be connected to a first network device and a second network device. One of the first and second network devices may be a master node and the other a secondary node. The first and second network devices may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information regarding different RATs may be transmitted to the terminal device from at least one of the first and second network devices. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information regarding the settings of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of terminal devices set by the second network device may be transmitted from the second network device directly to the terminal devices or via the first network device.

[0038] As used herein, the singular forms “one” and “the foregoing” also include the plural form unless explicitly indicated in the context. The term “including” and its variations should be understood as open-ended terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” Terms such as “first,” “second,” etc., may refer to different or identical subjects. The following may include other explicit and implicit definitions.

[0039] In some examples, values, procedures, or devices are referred to as “best,” “worst,” “highest,” “minimum,” “maximum,” etc. Such descriptions are intended to show that a choice can be made from among many usable functional alternatives, and it should be understood that such a choice does not need to be better, smaller, higher, or otherwise more desirable than other choices.

[0040] As used herein, the term “circuit” may mean a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of an analog and / or digital hardware circuit and software / firmware. In yet another example, a circuit may be any part of a hardware processor having a digital signal processor, software and one or more memories, which work together to cause a device such as a terminal or network device to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor such as a microprocessor or a part thereof that requires software / firmware for operation, but the software may not be present if it is not required for operation. As used herein, the term “circuit” also includes the implementation of a hardware circuit or one or more processors alone, or a part of a hardware circuit or one or more processors and their (or their) accompanying software and / or firmware.

[0041] As described above, DRX is proposed. If a terminal device is configured to have a DRX setting for a serving cell, the terminal device monitors the PDCCH in each DRX cycle based on that DRX setting. The drx-on-durationTimer defines a time interval at the start of a DRX cycle in which the terminal device should monitor the PDCCH, and this time interval is also referred to as the on-time interval window. After the on-time interval window in a DRX cycle is a time interval for opportunities regarding DRX in which the terminal device may sleep without monitoring the PDCCH for battery-saving purposes. If the terminal device receives a PDCCH indicating a new data transmission (DL or UL) on a serving cell, the terminal device starts or restarts the drx-InactivityTimer of the DRX setting in the first symbol after the completion of PDCCH reception and monitors the PDCCH in each subframe while the drx-InactivityTimer is running. As used herein, “DRX” refers to a method used in mobile communications to conserve the battery of a mobile device. The mobile device and the network negotiate the stages in which data transfer occurs. During other times, the device turns off its receiver and enters a low-power state. As used herein, the term “resource” includes resources in the frequency domain and resources in the time domain that are available for transmission between communication devices. As used herein, the term “on time interval” refers to the period during which a terminal device can monitor the downlink channel. As used herein, the term “opportunity for DRX” or “off time interval” refers to the period during which a terminal device does not monitor the downlink channel and does not receive data or control information on the downlink channel. As used herein, the term “DRX cycle” includes an on time interval window during which a terminal device should monitor the downlink channel and a time interval window for opportunities for DRX during which the terminal device can skip receiving downlink channels.

[0042] Since many augmented reality (XR) devices have limited power, power saving is one important topic. The term "XR" as used herein may include virtual reality (VR) and augmented reality (AR). Actual XR applications may include multiple traffic flows that may have different traffic characteristics, for example, different flows may have different periods, latency requirements, and data packets. Regarding periods, the period for video may be 16.67 ms, the period for audio may be 20 ms, and the period for data streams may be 10 ms. Regarding data rates, the data rate for video may be greater than 10 Mbps, and the data rate for audio / data may be about 1 Mbps.

[0043] If a UE is configured to have dual connectivity (DC), two DRX settings can be configured for the UE, each DRX setting being for a cell group. For XR services with multiple traffic flows having different traffic characteristics, following the current mechanism which only allows one DRX setting for a UE within a cell or cell group results in less sleep time for the UE.

[0044] Therefore, a solution is needed for multiple DRX settings for UEs within a cell or cell group to match multiple XR flows with different traffic characteristics in order to save UE power. According to embodiments of this disclosure, a terminal device receives multiple DRX settings for a serving cell or serving cell group from a network device. The terminal device monitors the PDCCH based on one or more of the multiple DRX settings. In this way, power is reduced in the terminal device.

[0045] Figure 1 is a schematic diagram of a communication system that can implement an embodiment of the present disclosure. The communication system 100, which is part of a communication network, comprises terminal device 110-1, terminal device 110-2, ..., terminal device 110-N, which can be collectively referred to as "terminal device 110". The number N may be any appropriate integer.

[0046] The communication system 100 further includes a network device 120. In the communication system 100, the network device 120 and the terminal device 110 can communicate data and control information with each other. The number of devices shown in Figure 1 is for illustrative purposes only and does not imply any limitation.

[0047] Communication in the communication system 100 can be implemented in accordance with any suitable communication protocol, including but not limited to, cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication may utilize any suitable wireless communication technology, including but not limited to code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multi-input multiple-output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technologies currently known or to be developed in the future.

[0048] Embodiments of the present disclosure can be applied to any suitable scenario. For example, embodiments of the present disclosure can be implemented in NR IIoT / URLLC. Alternatively, embodiments of the present disclosure may be implemented in one of the following: reduced-capacity NR equipment, NR multi-input multi-output (MIMO), NR sidelink enhancement, NR systems with frequencies above 52.6 GHz, extended NR operations up to 71 GHz, narrowband Internet of Things (NB-IOT) / extended machine-type communications (eMTC) on non-terrestrial networks (NTN), NTN, UE power saving enhancement, NR coverage enhancement, NB-IOT and LTE-MTC, integrated access and backhaul (IAB), NR multicast and broadcast services, or multi-radio dual connectivity enhancement.

[0049] Figure 2 shows a signaling diagram illustrating the inter-device process 200 according to some exemplary embodiments of the present disclosure. For illustrative purposes only, the process 200 will be described with reference to Figure 1. The process 200 may involve the terminal device 110-1 and the network device 120 shown in Figure 1. It should be noted that the process 200 is merely an example and not an limitation.

[0050] The network device 120 transmits multiple DRX settings for a serving cell or serving cell group to the terminal device 110-1 (2010). The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which the UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects permission for DL ​​HARQ retransmission, (11)(12) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (13) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (14) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0051] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0052] The terminal device 110-1 determines one set of target DRX timers or one set of target DRX settings from the plurality of DRX settings (2020). The set of target DRX timers may include one or more of the following: a DRX on time interval timer, a DRX inactive timer, or a DRX retransmission timer.

[0053] The terminal device 110-1 monitors the PDCCH based on the set of target DRX timers or the set of target DRX settings (2030). An embodiment of determining the set of target DRX timers and / or the set of target DRX settings will be described using the following diagram.

[0054] In some embodiments, the multiple DRX settings may be implemented independently. That is, terminal device 110-1 can maintain the DRX timers of the multiple DRX settings simultaneously. Terminal device 110-1 can monitor PDCCH separately according to the set of target DRX timers of the set of DRX settings. In this case, terminal device 110-1 can monitor PDCCH when one or more of the set of target DRX timers are running. In other words, when multiple DRX settings are configured, the active time for a serving cell in a DRX group includes the following time: - When the configured drx-onDurationTimer or drx-InactivityTimer of each of the multiple DRX configurations for a DRX group is running, or - When the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL of each of the multiple DRX configurations is running on any serving cell in the DRX group, or - When the ra-ContentionResollutionTimer or msgB-ResponseWindow is running (as described in Clause 5.1.4a), or - When a scheduling request has been sent on PUCCH and is pending, or - When a PDCCH indicating a new transmission from a MAC entity to C-RNTI has not been received after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among the random access preambles based on contention. Thus, implementation becomes easier. Refer to Figure 3, which shows a schematic diagram of a DRX configuration.

[0055] As shown in Figure 3, terminal device 110-1 may have two DRX settings: DRX setting #0 and DRX setting #1. Within one DRX cycle 311, there is an on-time interval window 310-1 and a time interval 312 for opportunities regarding DRX. The DRX on-time interval timer for DRX setting #0 runs within on-time interval windows 310-1 and 310-2. Similarly, within one DRX cycle 321, there is an on-time interval window 320-1 and a time interval 322 for opportunities regarding DRX. The DRX on-time interval timer for DRX setting #1 runs within on-time interval windows 320-1 and 320-2. In this case, terminal device 110-1 can monitor PDCCH within a time interval 330-1 determined based on on-time interval windows 310-1 and 320-1. Terminal device 110-1 may also monitor PDDCH within time interval 330-2, which corresponds to the on-time interval time window 310-2 of DRX setting #0. Terminal device 110-1 may also monitor PDCCH within time interval 330-3, which corresponds to the on-time interval time window 320-2 of DRX setting #1. Terminal device 110-1 may sleep within time interval 332.

[0056] In some embodiments, the on-time interval windows of two or more DRX settings may overlap. In this case, terminal device 110-1 may receive a PDCCH scheduling a new transmission within such overlapping on-time interval time windows. Terminal device 110-1 may start the target DRX inactive timer of a DRX setting from the multiple DRX settings (2040). In this case, if a PDCCH for scheduling a new data transmission is received within the overlapping time windows, it is unknown to the terminal device which DRX setting's associated DRX timer to start. As used herein, “start a timer” can mean starting a timer for the first time or restarting a timer. For example, as shown in Figure 4, on-time interval time windows 310-1 and 320-1 overlap. Terminal device 110-1 may receive a PDCCH 410 within the overlapping on-time interval time window 430. PDCCH 410 may schedule a PDSCH 420. Terminal device 110-1 may start / restart the DRX inactive timer for DRX setting #0 or DRX setting #1. Note that Table 4 shows only examples and not limitations.

[0057] The terminal device 110-1 may select a target DRX inactive timer based on a predetermined instruction. In some embodiments, the terminal device 110-1 may start a target DRX inactive timer having a minimum / smaller value. For example, if the value of the DRX inactive timer for DRX setting #0 is 2ms and the value of the DRX inactive timer for DRX setting #1 is 4ms, the terminal device 110-1 may start the DRX inactive timer for DRX setting #0. Alternatively, the terminal device 110-1 may start a target DRX inactive timer having a maximum / larger value. In this case, if the value of the DRX inactive timer for DRX setting #0 is 2ms and the value of the DRX inactive timer for DRX setting #1 is 4ms, the terminal device 110-1 may start the DRX inactive timer for DRX setting #1. In some embodiments, the terminal device 110-1 may start a target DRX inactive timer having the highest / higher DRX setting index. In this case, terminal device 110-1 may start the DRX inactive timer for DRX setting #1. Alternatively, terminal device 110-1 may start the target DRX inactive timer with the lowest / lower DRX setting index. In this case, terminal device 110-1 may start the DRX inactive timer for DRX setting #0. In some other embodiments, terminal device 110-1 may start the target DRX inactive timer with the shortest / shortest period. For example, if the period of DRX setting #0 is shorter than the period of DRX setting #1, terminal device 110-1 may start the DRX inactive timer for DRX setting #0. Alternatively, terminal device 110-1 may start the target DRX inactive timer with the longest / shortest period. For example, if the period of DRX setting #0 is shorter than the period of DRX setting #1, terminal device 110-1 may start the DRX inactive timer for DRX setting #1. In some embodiments, terminal device 110-1 may start a target DRX inactive timer associated with the lowest / lower priority XR flow.For example, if the priority of XR flow #0 associated with DRX setting #0 is lower than the priority of XR flow #1 associated with DRX setting #1, terminal device 110-1 may start the DRX inactivity timer for DRX setting #0. Alternatively, terminal device 110-1 may start the target DRX inactivity timer associated with the XR flow with the highest / higher priority. For example, if the priority of XR flow #0 associated with DRX setting #0 is lower than the priority of XR flow #1 associated with DRX setting #1, terminal device 110-1 may start the DRX inactivity timer for DRX setting #1.

[0058] In some embodiments, the network device 120 may transmit an RRC setting to the terminal device 110-1. In this case, if the RRC setting indicates an index for a target DRX setting, the terminal device 110-1 may select the DRX inactive timer for the target DRX setting based on the RRC setting. For example, if the RRC setting indicates an index for DRX setting #0, the terminal device 110-1 may start the DRX inactive timer for DRX setting #0.

[0059] Alternatively, the network device 120 may transmit downlink control information (DCI) to the terminal device 110-1. Based on the received DCI, the terminal device 110-1 may select a DRX inactive timer for the target DRX configuration. In this case, in some embodiments, the DCI may explicitly indicate the target DRX configuration. For example, the DCI carried within the scheduling PDCCH may include a field indicating the index of the target DRX configuration. In this case, the terminal device 110-1 may start the DRX inactive timer for the target DRX configuration. In some other embodiments, the DCI may implicitly indicate the target DRX configuration. For example, the DCI may include traffic flow information associated with the target DRX configuration. In this case, the terminal device 110-1 may start the DRX inactive timer associated with the traffic flow.

[0060] In some embodiments, the terminal device 110-1 may select a DRX inactive timer for a target DRX setting based on the DCI and RRC settings. For example, the RRC settings may represent a table of the multiple DRX settings, and the DCI may represent an index for the target DRX setting. In this case, the terminal device 110-1 may start the DRX inactive timer for the target DRX setting based on the DCI and RRC settings. Embodiments for determining a target timer or target DRX setting are also applicable to determining a DRX retransmission timer.

[0061] In some embodiments, terminal device 110-1 may receive MAC control elements (CEs) carrying DRX commands from network device 120 within the execution time of the multiple DRX timers of the multiple DRX settings. The term "DRX command" as used herein may also refer to a long DRX command. In some embodiments, the multiple DRX timers may be DRX on-time interval timers. Alternatively, the multiple DRX timers may be DRX inactive timers. Alternatively, the multiple DRX timers may be DRX inactive timers and DRX on-time interval timers. For example, as shown in Figure 4, the on-time interval time window 310-1 and the on-time interval time window 320-1 overlap when the drx-onDurationTimers of DRX setting #0 and DRX setting #1 are running simultaneously. Terminal device 110-1 can receive MAC CEs within the overlapping on-time interval time windows 430. In this case, it is unknown to the terminal device which DRX setting the received DRX command MAC CE applies to. It should be noted that Table 4 shows only examples and not limitations. In some embodiments, the MAC CE may indicate an index of the target DRX setting. For example, the MAC CE may include a field for indicating an index of the target DRX setting. In this case, terminal device 110-1 can apply DRX commands to the target DRX setting. Terminal device 110-1 can stop the DRX on-time interval timer and / or DRX inactive timer for the target DRX setting. For example, if terminal device 110-1 receives a long DRX command MAC CE with the index of DRX setting #0, terminal device 110-1 may stop the DRX on-time interval timer and / or DRX inactive timer for DRX setting #0. In this case, the execution time of DRX setting #1 is not affected. Alternatively, if terminal device 110-1 receives a DRX command MAC CE with the index of DRX setting #0, terminal device 110-1 may stop the DRX on-time interval timer and / or DRX inactive timer for DRX setting #0.In this case, in some embodiments, if DRX setting #0 has a short DRX cycle, the terminal device 110-1 may be modified to use the short DRX cycle of DRX setting index #0.

[0062] Alternatively, terminal device 110-1 can apply DRX commands to the multiple DRX settings. Terminal device 110-1 can stop all of the DRX on-time interval timers and / or DRX inactive timers for the multiple DRX settings. For example, terminal device 110-1 may stop all running DRX on-time interval timers and / or DRX inactive timers for DRX setting #0 and DRX setting #1. In some embodiments, the running timers for DRX setting #0 and DRX setting #1 may be DRX on-time interval timers. Alternatively, the running timers for DRX setting #0 and DRX setting #1 may be DRX inactive timers. In other embodiments, one of the running timers may be a DRX on-time interval timer and the other running timer may be a DRX inactive timer.

[0063] In some other embodiments, the network device 120 may send a DCI to the terminal device 110-1 scheduling a PDSCH for a traffic flow. In this case, if the terminal device 110-1 receives a MAC CE associated with the PDSCH carrying the DRX command within the execution time of the multiple DRX timers of the multiple DRX settings, the terminal device 110-1 may stop the DRX on-time interval timer and / or DRX inactive timer of the target DRX setting associated with the traffic flow.

[0064] In some other embodiments, the multiple DRX settings may be implemented jointly. For example, the multiple DRX settings may include a first DRX setting that includes a first DRX on-time interval timer and a second DRX setting that includes a second DRX on-time interval timer. In this case, terminal device 110-1 can monitor PDCCH during the execution time of the first DRX on-time interval timer. If the time offset between the end symbol of the first DRX timer and the start symbol of the second DRX timer does not exceed a predetermined or set interval, terminal device 110-1 skips the second DRX timer. In other words, terminal device 110-1 does not start the second DRX timer. In other words, if multiple DRX settings are configured, and the drx-onDurationTimer of the first DRX setting is running, and the time gap between the end time of the drx-onDurationTimer of the first DRX setting and the start time of the drx-onDurationTimer of the second DRX setting is smaller than the gap value m, the terminal device will not start the drx-onDurationTimer of the second DRX setting within this DRX cycle. The active time for a serving cell in a DRX group includes the following times: - When a drx-onDurationTimer or drx-InactivityTimer configured for a DRX group is running, or - when a drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell within a DRX group, or - when a ra-ContentionResolutionTimer or msgB-ResponseWindow is running, or - when a scheduling request has been sent on a PUCCH and is pending, or - when a PDCCH indicating a new transmission from a MAC entity to a C-RNTI has not been received after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity from among the random access preambles based on contention. In this way, more sleep time is provided to the terminal device and overlapping on-time interval time windows do not occur.

[0065] Referring to Figure 5, which shows a schematic diagram of a DRX setting, terminal device 110-1 may have two DRX settings: DRX setting #0 and DRX setting #1. Within one DRX cycle 511, there is an on-time interval time window 510-1 and a time interval 512 for opportunities for DRX. The DRX on-time interval timer for DRX setting #0 can run within on-time interval time windows 510-1 and 510-2. Similarly, within one DRX cycle 521, there is an on-time interval time window 520-1 and a time interval 522 for opportunities for DRX. The DRX on-time interval timer for DRX setting #1 can run within on-time interval time windows 520-1 and 520-2. In this case, as shown in Figure 5, terminal device 110-1 can receive PDCCH 523 within on-time interval time window 520-1. Terminal device 110-1 can start the DRX inactive timer 525 for DRX setting #1 within the first symbol after the completion of PDCCH reception 523. Since the start symbol of the DRX on-time interval timer for DRX setting #0 is within the on-time interval window for DRX setting #1, this means that the time offset between the two DRX on-time interval timers of the two DRX settings is 0. Terminal device 110-1 does not have to start the DRX on-time interval timer for DRX cycle 511. The active time (e.g., 530-1) for terminal device 110-1 can be extended by the network device 120 setting an appropriate DRX inactive timer, thereby ensuring data transmission of the XR flow associated with DRX setting #0. Similarly, terminal device 110-1 can receive PDCCH 513 within the on-time interval time window 510-2. Terminal device 110-1 may start the DRX inactive timer 515 for DRX setting #0 within the first symbol after the completion of PDCCH reception 513. If the time offset 540 between the end symbol of the on-time interval time window 510-2 and the start symbol of the on-time interval time window 520-2 does not exceed a predetermined gap, terminal device 110-1 does not need to start the on-time interval timer for the on-time interval time window 520-2.Alternatively, if the time offset 540 between the end symbol of the on-time interval time window 510-2 and the start symbol of the on-time interval time window 520-2 exceeds a predetermined gap, the terminal device 110-1 may start the on-time interval timer for the on-time interval time window 520-2.

[0066] In some other embodiments, the multiple DRX settings may be implemented jointly. For example, the multiple DRX settings may include a first DRX setting including a first DRX on-time interval timer and a second DRX setting including a second DRX on-time interval timer. If the start time of the second DRX on-time interval timer falls within the execution time of the first DRX on-time interval timer, the terminal device 110-1 may monitor the PDCCH based on a third DRX on-time interval timer generated based on the first and second DRX on-time interval timers. The start time of the third DRX on-time interval timer is the same as the first DRX on-time interval timer having an earlier start point. The end time of the third DRX on-time interval timer is the same as the DRX on-time interval timer having the latest end point among the first and second DRX on-time interval timers.

[0067] In some embodiments, one of the multiple DRX settings may be implemented. In other words, terminal device 110-1 can maintain the timers of one DRX setting. Terminal device 110-1 can switch the active DRX setting among the multiple DRX settings. For example, the multiple DRX settings may include a first DRX setting including a first set of DRX timers and a second DRX setting including a second set of DRX timers. In this case, terminal device 110-1 can monitor PDCCH while the first set of DRX timers is running. In some embodiments, if terminal device 110-1 receives a DCI from network device 120 including a switching instruction, terminal device 110-1 may switch to the second set of DRX timers. Alternatively, if the switching timer in terminal device 110-1 expires, terminal device 110-1 may switch to the second set of DRX timers. In this case, terminal device 110-1 can monitor PDCCH while the second set of DRX timers are running. Thus, the terminal device is provided with more sleep time and there are no overlapping on-time interval time windows.

[0068] Referring to Figure 6, which shows a schematic diagram of a DRX setting, terminal device 110-1 may have two DRX settings: DRX setting #0 and DRX setting #1. Within one DRX cycle 611, there is an on-time interval time window 610-1 and a time interval 612 for opportunities for DRX. The DRX on-time interval timer of DRX setting #0 can run within on-time interval time windows 610-1 and 610-2. Similarly, within one DRX cycle 621, there is an on-time interval time window 620-1 and a time interval 622 for opportunities for DRX. The DRX on-time interval timer of DRX setting #1 can run within on-time interval time windows 620-1 and 620-2. When DRX setting #1 is running, terminal device 110-1 can receive DCI 640 within on-time interval time window 620-1. The DCI 640 may include a switch instruction indicating whether the running / active DRX configuration has been switched to a different DRX configuration for the next cycle. If the switch instruction includes "0", terminal device 110-1 cannot switch to DRX configuration #0, and terminal device 110-1 can start the DRX on-time interval timer for the on-time interval time window 620-2. Alternatively, if the switch instruction includes "1", terminal device 110-1 can switch to DRX configuration #0, and terminal device 110-1 can start the DRX on-time interval timer for the on-time interval time window 610-2. It should be noted that the values ​​of the switch instruction are examples only and not limiting. The delay 630 may be acceptable depending on the delay requirements of the traffic flow for DRX configuration #0.

[0069] As described above, terminal device 110-1 may switch to a second set of DRX timers based on the switching timer. In this case, the switching timer can be set via the RRC setting. The value of the switching timer may be based on the period of the traffic flow.

[0070] Figure 7 shows a signaling diagram illustrating a process 700 between devices according to some exemplary embodiments of the present disclosure. For illustrative purposes only, the process 700 will be described with reference to Figure 1. The process 700 may involve terminal device 110-1 and network device 120 shown in Figure 1. It should be noted that the process 700 is merely an example and not an limitation.

[0071] The network device 120 transmits multiple DRX settings for a serving cell or serving cell group to the terminal device 110-1 (7010). The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which the UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects permission for DL ​​HARQ retransmission, (11)(12) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (13) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (14) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0072] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0073] Terminal device 110-1 detects a power saving instruction signal within a monitoring window (7020). The monitoring window is associated within one or more DRX settings among the plurality of DRX settings. In some embodiments, the power saving instruction signal may be a wake-up signal (WUS). Alternatively, the power saving instruction signal may be a low-power WUS. In some other embodiments, the power saving instruction signal may be a PDDCH skip instruction included in a DCI. A DCI including a PDDCH skip instruction can indicate that the terminal device can skip monitoring of the PDCCH for a certain time interval. A DCI also indicates the length of a certain time interval in the time domain. Such a time interval may include a set of symbols, a set of slots, or a set of DRX cycles. It should be noted that the power saving instruction signal may be any suitable signal. For illustrative purposes only, embodiments of the present disclosure will be described below with reference to the case where the power saving instruction signal is a WUS.

[0074] A Wake-Up Signal (WUS) instruction, transmitted via DCI signaling with DCI format 2_6 scrambled with a Power Saving Radio Network Temporary Identifier (PS-RNTI), can be used to notify a terminal device whether to start the DRX on-time interval timer for the next DRX cycle for potential data scheduling. The WUS detection window (search space set) may be set before the on-time interval of the DRX setting for PDCCH monitoring for WUS, and one or more PDCCH occasions within the WUS window should be detected. The terminal device can detect the WUS DCI before the DRX on-time interval. If the Wake-Up instruction is set to "1", the terminal device should start the DRX on-time interval timer. Otherwise, the terminal device does not need to start the timer.

[0075] Referring to Figure 8, the WUS window 810 for DRX setting #0 and the WUS window 820 for DRX setting #1 may overlap. Terminal device 110-1 may receive the WUS within the overlapping portion 830. For the terminal device, it is unclear whether the received WUS is used to indicate whether or not to start the DRX on-time interval timer for which DRX setting. If the network device sends a PDCCH to schedule the transmission of data for the XR flow, but the terminal device fails to detect the PDCCH because it failed to detect the WUS, this may degrade the transmission performance of the XR flow. In some embodiments, the network device 120 may send an RRC setting to terminal device 110-1 (7030). For example, the RRC setting may indicate a target DRX setting. In this case, if the received WUS instruction is set to "1", terminal device 110-1 may start the DRX on-time interval timer for the target DRX setting based on the RRC setting (7040). In this way, the terminal device can distinguish which DRX setting's DRX-on time interval timer to execute when WUS detection windows overlap.

[0076] Alternatively, different frequency domain resources (e.g., control resource sets (CORESET)) can be configured for different WUS monitoring occasions with different DRX settings. In this case, terminal device 110-1 may determine the frequency domain resources for the monitoring window. Terminal device 110-1 may determine the target DRX setting based on the frequency domain resources associated with the received WUS. Terminal device 110-1 can then start the DRX on time interval timer for the target DRX setting (7040). In this way, terminal device can distinguish which DRX setting's DRX on time interval timer to run in the event of overlapping WUS detection windows.

[0077] Alternatively, WUS with different DRX settings can be scrambled using different sequences. In this case, several sequences may be pre-configured for scrambling WUS for different DRX settings. Terminal device 110-1 may determine the sequence for scrambling the WUS based on blind detection. Terminal device 110-1 may determine the target DRX setting based on the sequence associated with the received WUS. Terminal device 110-1 can then start the DRX-on time interval timer for the target DRX setting (7040). In this way, the terminal device can distinguish which DRX setting's DRX-on time interval timer to run in the event of overlapping WUS detection windows.

[0078] In some other embodiments, terminal device 110-1 may start a DRX on-time interval timer based on predetermined information (7040). For example, terminal device 110-1 may start a DRX on-time interval timer having a maximum / greater value. As shown in Figure 8, if the DRX on-time interval timer for DRX setting #1 is greater than the DRX on-time interval timer for DRX setting #0, terminal device 110-1 may start the DRX on-time interval timer for DRX setting #1. Alternatively, terminal device 110-1 may start a DRX on-time interval timer having a minimum / smaller value. For example, if the DRX on-time interval timer for DRX setting #1 is greater than the DRX on-time interval timer for DRX setting #0, terminal device 110-1 may start the DRX on-time interval timer for DRX setting #0. In some other embodiments, terminal device 110-1 may start a DRX on-time interval timer having a start time closer to / nearest to the WUS. For example, as shown in Figure 8, the start time of the DRX on-time interval timer for DRX setting #1 is closer to the WUS than the start time of the DRX on-time interval timer for DRX setting #0. In this case, terminal device 110-1 may start the DRX on-time interval timer for DRX setting #1. In this way, the terminal device can distinguish which DRX setting's DRX on-time interval timer to execute when the WUS detection windows overlap.

[0079] In some embodiments, the network device 120 may transmit the PDCCH for the WUS to the terminal device 110-1 (7050). If the PDCCH indicates that the DRX on-time interval timer should be started, the terminal device 110-1 may stop monitoring the PDCCH within the monitoring window. Alternatively, if the PDCCH indicates that the DRX on-time interval timer should not be started, the terminal device 110-1 may stop monitoring the PDCCH within the monitoring window and not start any on-time interval timers. In this way, the terminal device does not need to continue monitoring the PDCCH, and power consumption is reduced.

[0080] In some embodiments, the WUS can be configured separately for each DRX configuration. In this case, the WUS monitoring occasion for the first DRX configuration may fall within the on-time interval window of the second DRX configuration. For example, the multiple DRX configurations may include the first DRX configuration and the second DRX configuration. The first monitoring window for detecting the WUS for the first DRX configuration may fall within the execution time of the on-time interval timer of the second DRX configuration. For example, as shown in Figure 9, the WUS detection windows for DRX configuration #0 and DRX configuration #1 are 910 and 920, respectively. The WUS detection window 910 falls within the on-time interval time window of DRX configuration #1. The network device may transmit the WUS within the WUS detection windows 910 and / or 920. However, under the current WUS detection rules, if a network device sends a group common WUS within the WUS detection window 910 while the DRX on-time interval timer for DRX configuration #1 is running, the terminal device will not detect the DCI format 2_6 for the WUS within the WUS detection window 910 because the terminal device is active during the WUS detection window 910. The terminal device will miss the WUS instruction for DRX configuration #0, which degrades the performance of the XR flow associated with DRX configuration #0.

[0081] In some embodiments, the network device 120 may transmit a PDCCH containing group common downlink control information for WUS within the first WUS monitoring window. For example, terminal device 110-1 may monitor a PDCCH for the group common DCI format of the first DRX configuration within the WUS detection window 910. Alternatively, the network device 120 may transmit a PDCCH containing specific downlink control information for WUS within the execution time of the on-time interval timer of the second DRX configuration. In this case, terminal device 110-1 does not need to monitor a PDCCH for the DCI format 2_6 for the WUS instruction of the first DRX configuration. The WUS instruction of the first DRX configuration can be carried within the UE-specific DCI. Terminal device 110-1 may monitor a PDCCH with the UE-specific DCI for the WUS instruction of the first DRX configuration within the active time resulting from the execution of the on-time interval timer of the second DRX configuration. The specific DCI format may be a scheduling DCI format such as DCI format 0_1 / 1_1, 0_2 / 1_2, etc. In some other embodiments, there may be a new or unused field in the DCI to indicate wake-up information to indicate whether or not to start the on-time interval timer for the first DRX setting. In some other embodiments, a WUS indication for the second DRX setting may be carried in the UE-specific scheduling DCI 930 that schedules the PDSCH 940. If WUS indicates "1", the terminal device 110-1 may start the on-time interval timer for the first DRX setting.

[0082] Alternatively, network device 120 may transmit MAC CE to terminal device 110-1 (7060). MAC CE may indicate a WUS instruction for a first DRX configuration. For example, MAC CE carried on PDSCH 940 may include a mapping between WUS and an index for the target DRX configuration.

[0083] In some embodiments, if the DRX-on time interval windows of two DRX settings overlap in the time domain, or if the time offset between the DRX-on time interval windows is less than the value x, the terminal device 110-1 may fall back and skip the WUS monitoring of the first DRX setting.

[0084] According to the above embodiment, if the WUS monitoring occasion of the first DRX setting falls within the on-time interval window of the second DRX setting, the UE can decide whether or not to start the on-time interval timer of the first DRX setting, thereby improving system performance.

[0085] Figure 10 shows a signaling diagram illustrating inter-device process 1000 according to some exemplary embodiments of the present disclosure. For illustrative purposes only, process 1000 will be described with reference to Figure 1. Process 1000 may involve terminal device 110-1 and network device 120 shown in Figure 1. It should be noted that process 1000 is merely an example and not an limitation.

[0086] The network device 120 transmits multiple DRX settings for a serving cell or serving cell group to the terminal device 110-1 (1010). The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which the UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects permission for DL ​​HARQ retransmission, (11)(12) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (13) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (14) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0087] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0088] The network device 120 transmits a configuration for the Search Space Set Group (SSSG) for each DRX configuration (1020). If multiple DRX configurations are configured for different XR flows, and each DRX configuration has a corresponding SSSG, the terminal device 110-1 can monitor the PDCCH within the DRX-on time interval of the DRX configuration based on the SSSG configuration. The terminal device 110-1 can determine the association between the DRX configuration index and the SSSG index based on the RRC configuration. The SSSG may be implicitly switched between multiple SSSGs based on the running DRX configuration index for the next active time interval. For example, if SSSG#0 is configured for DRX setting #1, and SSSG#1 is configured for DRX setting #0, and the DRX on-time interval timer for DRX setting #1 is running, the terminal device will monitor the PDCCH according to SSSG#0, and after the DRX on-time interval timer for DRX setting #1 expires, the terminal device will start monitoring the PDCCH according to SSSG#1, and will stop monitoring the PDCCH according to SSSG#0 for the serving cell x ms before the start of the DRX on-time interval for DRX setting #0. However, if the on-time interval time windows of the two DRX settings overlap, it is unclear to the terminal device which SSSG to monitor the PDCCH according to within the overlapping on-time interval time window, because the overlapping on-time interval time windows are associated with the two SSSGs.

[0089] In some embodiments, the network device 120 may transmit an RRC setting to the terminal device 110-1 (1030). The RRC setting may indicate the index of the target SSSG. The terminal device 110-1 may monitor the PDCCH within overlapping on-time interval time windows based on the target SSSG (1050). For example, if the RRC setting indicates the index of SSSG 111, the terminal device 110-1 may monitor the PDCCH within overlapping on-time interval time windows based on SSSG 111.

[0090] Alternatively, the network device 120 may transmit a DCI to the terminal device 110-1 (1040). The DCI may indicate the index of the target SSSG. The terminal device 110-1 may monitor the PDCCH within overlapping on-time interval time windows based on the target SSSG (1050). For example, if the DCI indicates the index of SSSG 112, the terminal device may monitor the PDCCH based on SSSG 112. In some other embodiments, the terminal device 110-1 may monitor the PDCCH based on predetermined information (1050). For example, the SSSG may be pre-configured, and the terminal device 110-1 may always monitor the PDCCH within overlapping on-time interval time windows according to SSSG#0.

[0091] In other embodiments, overlapping on-time interval windows may be associated with a first DRX setting and a second DRX setting. In this case, the terminal device 110-1 can monitor the PDCCH within the overlapping on-time interval window based on a first SSSG associated with the first DRX setting and a second SSSG associated with the second DRX setting. For example, the terminal device may monitor the PDCCH according to both SSSG 111 and SSSG 112.

[0092] The embodiments described with reference to Figure 2, Figure 7, and Figure 10 may be implemented separately. Alternatively, the embodiments described with reference to Figure 2, Figure 7, and Figure 10 may be combined.

[0093] Figure 12 is a flowchart of an exemplary method 1200 according to an embodiment of the present disclosure. For illustrative purposes only, method 1200 can be implemented in a terminal device 110-1 as shown in Figure 1.

[0094] In block 1210, terminal device 110-1 receives multiple DRX settings for a serving cell or serving cell group from network device 120. The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which a UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission.(11) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (12) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (13) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0095] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0096] In block 1220, terminal device 110-1 determines one set of target DRX timers or one set of target DRX settings from the plurality of DRX settings. The set of target DRX timers may include one or more of the following: DRX on time interval timer, DRX inactive timer, or DRX retransmission timer.

[0097] In block 1230, terminal device 110-1 monitors PDCCH based on the set of target DRX timers or the set of target DRX settings. An embodiment of determining the set of target DRX timers and / or the set of target DRX settings will be explained using the following diagram.

[0098] In some embodiments, the multiple DRX settings may be implemented independently. That is, terminal device 110-1 can maintain the DRX timers of the multiple DRX settings simultaneously. Terminal device 110-1 can monitor PDCCH separately according to the set of target DRX timers of the set of DRX settings. In this case, terminal device 110-1 can monitor PDCCH when one or more of the set of target DRX timers are running. In other words, when multiple DRX settings are configured, the active time for a serving cell in a DRX group includes the following time: - When the configured drx-onDurationTimer or drx-InactivityTimer of each of the multiple DRX settings for a DRX group is running, or - When the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL of each of the multiple DRX settings is running on any serving cell in the DRX group, or - When the ra-ContentionResolutionTimer or msgB-ResponseWindow is running, or - When a scheduling request has been sent on PUCCH and is pending, or - When a PDCCH indicating a new transmission from a MAC entity to C-RNTI has not been received after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among the random access preambles based on contention. This makes implementation easier.

[0099] In some embodiments, the on-time interval windows of two or more DRX settings may overlap. In this case, terminal device 110-1 may receive a PDCCH to schedule a new transmission within such overlapping on-time interval time windows. Terminal device 110-1 may start the target DRX inactive timer of a DRX setting from the multiple DRX settings (2040). In this case, if a PDCCH to schedule a new data transmission is received within an overlapping time window, it is unknown to the terminal device which DRX setting's associated DRX timer to start.

[0100] The terminal device 110-1 may select a target DRX inactive timer based on a predetermined instruction. In some embodiments, the terminal device 110-1 may start a target DRX inactive timer having a minimum value. Alternatively, the terminal device 110-1 may start a target DRX inactive timer with a maximum value. In some embodiments, the terminal device 110-1 may start a target DRX inactive timer having the highest DRX setting index. Alternatively, the terminal device 110-1 may start a target DRX inactive timer having the lowest DRX setting index. In some other embodiments, the terminal device 110-1 may start a target DRX inactive timer having the shortest period. Alternatively, the terminal device 110-1 may start a target DRX inactive timer having the longest period. In some embodiments, the terminal device 110-1 may start a target DRX inactive timer associated with an XR flow having the lowest priority. Alternatively, terminal device 110-1 may start a target DRX inactive timer associated with the highest / higher priority XR flow.

[0101] In some embodiments, the network device 120 may transmit the RRC setting to the terminal device 110-1. In this case, if the RRC setting indicates an index for the target DRX setting, the terminal device 110-1 may select the DRX inactive timer for the target DRX setting based on the RRC setting.

[0102] Alternatively, the network device 120 may transmit downlink control information (DCI) to the terminal device 110-1. Based on the received DCI, the terminal device 110-1 may select a DRX inactive timer for the target DRX configuration. In this case, in some embodiments, the DCI may explicitly indicate the target DRX configuration. For example, the DCI carried within the scheduling PDCCH may include a field indicating the index of the target DRX configuration. In this case, the terminal device 110-1 may start the DRX inactive timer for the target DRX configuration. In some other embodiments, the DCI may implicitly indicate the target DRX configuration. For example, the DCI may include traffic flow information associated with the target DRX configuration. In this case, the terminal device 110-1 may start the DRX inactive timer associated with the traffic flow.

[0103] In some embodiments, the terminal device 110-1 may select a DRX inactive timer for a target DRX setting based on the DCI and RRC settings. For example, the RRC settings may represent a table of the multiple DRX settings, and the DCI may represent an index for the target DRX setting. In this case, the terminal device 110-1 may start the DRX inactive timer for the target DRX setting based on the DCI and RRC settings. Embodiments for determining a target timer or target DRX setting are also applicable to determining a DRX retransmission timer.

[0104] In some embodiments, terminal device 110-1 may receive a MAC control element (CE) carrying a DRX command from network device 120 within the execution time of the DRX timers of the DRX settings. The term "DRX command" as used herein may also refer to a long DRX command. In some embodiments, the DRX timers may be DRX on-time interval timers. Alternatively, the DRX timers may be DRX inactive timers. Alternatively, the DRX timers may be DRX inactive timers and DRX on-time interval timers. In some embodiments, the MAC CE may indicate an index of the target DRX settings. For example, the MAC CE may include a field for indicating an index of the target DRX settings. In this case, terminal device 110-1 can apply a DRX command to the target DRX settings. Terminal device 110-1 can stop the DRX on-time interval timers and / or DRX inactive timers of the target DRX settings.

[0105] Alternatively, terminal device 110-1 can apply DRX commands to the multiple DRX settings. Terminal device 110-1 can stop all of the DRX on-time interval timers and / or DRX inactive timers for the multiple DRX settings.

[0106] In some other embodiments, the network device 120 may send a DCI to the terminal device 110-1 scheduling a PDSCH for a traffic flow. In this case, if the terminal device 110-1 receives a MAC CE associated with the PDSCH carrying the DRX command within the execution time of the multiple DRX timers of the multiple DRX settings, the terminal device 110-1 may stop the DRX on-time interval timer and / or DRX inactive timer of the target DRX setting associated with the traffic flow.

[0107] In some other embodiments, the multiple DRX settings may be implemented jointly. For example, the multiple DRX settings may include a first DRX setting that includes a first DRX timer on-time interval and a second DRX setting that includes a second on-time interval DRX timer. In this case, terminal device 110-1 can monitor PDCCH during the execution time of the first DRX on-time interval timer. If the time offset between the end symbol of the first DRX timer and the start symbol of the second DRX timer does not exceed a predetermined or set interval, terminal device 110-1 skips the second DRX timer. In other words, terminal device 110-1 does not start the second DRX timer. In other words, if multiple DRX settings are configured, and the drx-onDurationTimer of the first DRX setting is running, and the time gap between the end time of the drx-onDurationTimer of the first DRX setting and the start time of the drx-onDurationTimer of the second DRX setting is smaller than the gap value m, the terminal device will not start the drx-onDurationTimer of the second DRX setting within this DRX cycle. The active time for a serving cell in a DRX group includes the following times: - When a drx-onDurationTimer or drx-InactivityTimer configured for a DRX group is running, or - when a drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell within a DRX group, or - when a ra-ContentionResolutionTimer or msgB-ResponseWindow is running, or - when a scheduling request has been sent on a PUCCH and is pending, or - when a PDCCH indicating a new transmission from a MAC entity to a C-RNTI has not been received after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity from among the random access preambles based on contention. In this way, more sleep time is provided to the terminal device and overlapping on-time interval time windows do not occur.

[0108] In some other embodiments, the multiple DRX settings may be implemented jointly. For example, the multiple DRX settings may include a first DRX setting including a first DRX on-time interval timer and a second DRX setting including a second DRX on-time interval timer. If the start time of the second DRX on-time interval timer falls within the execution time of the first DRX on-time interval timer, the terminal device 110-1 may monitor the PDCCH based on a third DRX on-time interval timer generated based on the first and second DRX on-time interval timers. The start time of the third DRX on-time interval timer is the same as the first DRX on-time interval timer having an earlier start point. The end time of the third DRX on-time interval timer is the same as the DRX on-time interval timer having the latest end point among the first and second DRX on-time interval timers.

[0109] In some embodiments, one of the multiple DRX settings may be implemented. In other words, terminal device 110-1 can maintain the timers of one DRX setting. Terminal device 110-1 can switch the active DRX setting among the multiple DRX settings. For example, the multiple DRX settings may include a first DRX setting including a first set of DRX timers and a second DRX setting including a second set of DRX timers. In this case, terminal device 110-1 can monitor PDCCH while the first set of DRX timers is running. In some embodiments, if terminal device 110-1 receives a DCI from network device 120 including a switching instruction, terminal device 110-1 may switch to the second set of DRX timers. Alternatively, if the switching timer in terminal device 110-1 expires, terminal device 110-1 may switch to the second set of DRX timers. In this case, terminal device 110-1 can monitor PDCCH while the second set of DRX timers is running. Thus, the terminal device is provided with more sleep time and there are no overlapping on-time intervals. As described above, terminal device 110-1 may switch to the second set of DRX timers based on the switching timer. In this case, the switching timer can be set via the RRC setting. The value of the switching timer may be based on the period of the traffic flow.

[0110] Figure 13 is a flowchart of an exemplary method 1300 according to an embodiment of the present disclosure. For illustrative purposes only, method 1300 may be implemented in a network device 120-1 as shown in Figure 1.

[0111] In block 1310, the network device 120 transmits multiple DRX settings for a serving cell or serving cell group to the terminal device 110-1. The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which a UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission.(11) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (12) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (13) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0112] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0113] Figure 14 is a flowchart of an exemplary method 1400 according to an embodiment of the present disclosure. For illustrative purposes only, method 1400 can be implemented in a terminal device 110-1 as shown in Figure 1.

[0114] In block 1410, terminal device 110-1 receives multiple DRX settings for a serving cell or serving cell group from network device 120. The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which a UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission.(11) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (12) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (13) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0115] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0116] In block 1420, terminal device 110-1 detects a power saving instruction signal within a monitoring window. The monitoring window is associated within one or more of the DRX settings. In some embodiments, the power saving instruction signal may be a wake-up signal (WUS). Alternatively, the power saving instruction signal may be a low-power WUS. In some other embodiments, the power saving instruction signal may be a PDDCH skip instruction included in the DCI. A DCI including a PDDCH skip instruction can indicate that the terminal device can skip monitoring of the PDCCH for a certain time interval. The DCI also indicates the length of a certain time interval in the time domain. Such a time interval may include a set of symbols, a set of slots, or a set of DRX cycles. It should be noted that the power saving instruction signal may be any suitable signal. For illustrative purposes only, below, the power saving instruction signal may refer to a wake-up signal (WUS).

[0117] A Wake-Up Signal (WUS) instruction, transmitted via DCI signaling with DCI format 2_6 scrambled with a Power Saving Radio Network Temporary Identifier (PS-RNTI), can be used to notify a terminal device whether to start the DRX on-time interval timer for the next DRX cycle for potential data scheduling. The WUS detection window (search space set) may be set before the on-time interval of the DRX setting for PDCCH monitoring for WUS, and one or more PDCCH occasions within the WUS window should be detected. The terminal device can detect the WUS DCI before the DRX on-time interval. If the Wake-Up instruction is set to "1", the terminal device should start the DRX on-time interval timer. Otherwise, the terminal device does not need to start the timer.

[0118] Alternatively, different frequency domain resources (e.g., control resource sets (CORESET)) can be configured for different WUS monitoring occasions with different DRX settings. In this case, terminal device 110-1 may determine the frequency domain resources for the monitoring window. Terminal device 110-1 may determine the target DRX setting based on the frequency domain resources associated with the received WUS. Terminal device 110-1 can then start the DRX on time interval timer for the target DRX setting (7040). In this way, terminal device can distinguish which DRX setting's DRX on time interval timer to run in the event of overlapping WUS detection windows.

[0119] Alternatively, WUS with different DRX settings can be scrambled using different sequences. In this case, several sequences may be pre-configured for scrambling WUS for different DRX settings. Terminal device 110-1 may determine the sequence for scrambling the WUS based on blind detection. Terminal device 110-1 may determine the target DRX setting based on the sequence associated with the received WUS. Terminal device 110-1 can start the DRX-on time interval timer for the target DRX setting. In this way, the terminal device can distinguish which DRX setting's DRX-on time interval timer to run in the event of overlapping WUS detection windows.

[0120] In block 1430, terminal device 110-1 may start a DRX on time interval timer. In some other embodiments, terminal device 110-1 may start a DRX on time interval timer based on predetermined information. For example, terminal device 110-1 may start a DRX on time interval timer having a maximum / greater value. Alternatively, terminal device 110-1 may start a DRX on time interval timer having a minimum / smaller value. In some other embodiments, terminal device 110-1 may start a DRX on time interval timer having a start time closer to / nearest to WUS.

[0121] In some embodiments, the network device 120 may transmit a PDCCH for the WUS to the terminal device 110-1. If the PDCCH indicates that the DRX on-time interval timer should be started, the terminal device 110-1 may stop monitoring the PDCCH within the monitoring window. Alternatively, if the PDCCH indicates that the DRX on-time interval timer should not be started, the terminal device 110-1 may stop monitoring the PDCCH within the monitoring window and not start any on-time interval timers. In this way, the terminal device does not need to continue monitoring the PDCCH, and power consumption is reduced.

[0122] In some embodiments, WUS can be configured separately for each DRX setting. In this case, the WUS monitoring occasion for the first DRX setting may fall within the on-time interval window of the second DRX setting. For example, the multiple DRX settings may include a first DRX setting and a second DRX setting. The first monitoring window for detecting WUS for the first DRX setting may fall within the execution time of the on-time interval timer of the second DRX setting.

[0123] In some embodiments, the network device 120 may transmit a PDCCH containing group common downlink control information for the WUS within a first WUS monitoring window. For example, terminal device 110-1 may monitor a PDCCH for the group common DCI format of the first DRX configuration. Alternatively, the network device 120 may transmit a PDCCH containing specific downlink control information for the WUS within the execution time of the on-time interval timer of the second DRX configuration. In this case, terminal device 110-1 does not need to monitor a PDCCH for the DCI format 2_6 for the WUS instruction of the first DRX configuration. The WUS instruction of the first DRX configuration can be carried within the UE-specific DCI. Terminal device 110-1 may monitor a PDCCH with the UE-specific DCI for the WUS instruction of the first DRX configuration within the active time resulting from the execution of the on-time interval timer of the second DRX configuration. The specific DCI format may be a scheduling DCI format such as, for example, DCI format 0_1 / 1_1, 0_2 / 1_2, etc. In some other embodiments, there may be a new or unused field in the DCI to indicate wake-up information to indicate whether or not to start the on-time interval timer for the first DRX setting.

[0124] Alternatively, network device 120 may transmit a MAC CE to terminal device 110-1. The MAC CE may indicate a WUS instruction for a first DRX configuration. For example, a MAC CE carried on PDSCH may include a mapping between the WUS and the index of the target DRX configuration.

[0125] In some embodiments, if the DRX-on time interval windows of two DRX settings overlap in the time domain, or if the time offset between the DRX-on time interval windows is less than the value x, the terminal device 110-1 may fall back and skip the WUS monitoring of the first DRX setting.

[0126] According to the above embodiment, if the WUS monitoring occasion of the first DRX setting falls within the on-time interval window of the second DRX setting, the UE can decide whether or not to start the on-time interval timer of the first DRX setting, thereby improving system performance.

[0127] Figure 15 is a flowchart of an exemplary method 1500 according to an embodiment of the present disclosure. For illustrative purposes only, method 1500 can be implemented in a terminal device 110-1 as shown in Figure 1.

[0128] In block 1510, terminal device 110-1 receives multiple DRX settings for a serving cell or serving cell group from network device 120. The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which a UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission.(11) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (12) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (13) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0129] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0130] In block 1520, terminal device 110-1 receives settings for the Search Space Set Group (SSSG) for each DRX setting. If multiple DRX settings are configured for different XR flows, and each DRX setting has a corresponding SSSG, terminal device 110-1 can monitor the PDCCH within the DRX-on time interval of the DRX setting based on the SSSG settings. Terminal device 110-1 can determine the association between the DRX setting index and the SSSG index based on the RRC settings. The SSSG may be implicitly switched between multiple SSSGs based on the running DRX setting index for the next active time interval. For example, if SSSG#0 is configured for DRX setting #1, and SSSG#1 is configured for DRX setting #0, and the DRX on-time interval timer for DRX setting #1 is running, the terminal device will monitor the PDCCH according to SSSG#0, and after the DRX on-time interval timer for DRX setting #1 expires, the terminal device will start monitoring the PDCCH according to SSSG#1, and will stop monitoring the PDCCH according to SSSG#0 for the serving cell x ms before the start of the DRX on-time interval for DRX setting #0. However, if the on-time interval time windows of the two DRX settings overlap, it is unclear to the terminal device which SSSG to monitor the PDCCH according to within the overlapping on-time interval time window, because the overlapping on-time interval time windows are associated with the two SSSGs.

[0131] In block 1530, terminal device 110 may monitor PDCCH based on the target SSSG. In some embodiments, network device 120 may transmit RRC settings to terminal device 110-1. The RRC settings may indicate the index of the target SSSG. Terminal device 110-1 may monitor PDCCH based on the target SSSG within overlapping on-time interval time windows (1050).

[0132] Alternatively, the network device 120 may send a DCI to the terminal device 110-1. The DCI may indicate the index of the target SSSG. The terminal device 110-1 may monitor the PDCCH within overlapping on-time interval time windows based on the target SSSG. For example, the SSSG may be pre-configured.

[0133] In other embodiments, overlapping on-time interval windows may be associated with a first DRX setting and a second DRX setting. In this case, the terminal device 110-1 can monitor the PDCCH within the overlapping on-time interval window based on a first SSSG associated with the first DRX setting and a second SSSG associated with the second DRX setting.

[0134] Figure 16 is a flowchart of an exemplary method 1600 according to an embodiment of the present disclosure. For illustrative purposes only, method 1600 may be implemented in a network device 120-1 as shown in Figure 1.

[0135] In block 1610, the network device 120 transmits multiple DRX settings for a serving cell or serving cell group to the terminal device 110-1. The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which a UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission.(11) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (12) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (13) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0136] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0137] In some embodiments, in block 1620, the network device 120 may transmit a PDCCH for the WUS to the terminal device 110-1. If the PDCCH indicates that the DRX on-time interval timer should be started, the terminal device 110-1 may stop monitoring the PDCCH within the monitoring window. Alternatively, if the PDCCH indicates that the DRX on-time interval timer should not be started, the terminal device 110-1 may stop monitoring the PDCCH within the monitoring window and not start any on-time interval timers. In this way, the terminal device can distinguish which DRX configuration's DRX on-time interval timer to run in the event of overlapping WUS detection windows.

[0138] In some embodiments, WUS can be configured separately for each DRX setting. In this case, the WUS monitoring occasion for the first DRX setting may fall within the on-time interval window of the second DRX setting. For example, the multiple DRX settings may include a first DRX setting and a second DRX setting. The first monitoring window for detecting WUS for the first DRX setting may fall within the execution time of the on-time interval timer of the second DRX setting.

[0139] In some embodiments, the network device 120 may transmit a PDCCH containing group common downlink control information for the WUS within a first WUS monitoring window. For example, terminal device 110-1 may monitor a PDCCH for the group common DCI format of the first DRX configuration within a WUS detection window. Alternatively, the network device 120 may transmit a PDCCH containing specific downlink control information for the WUS within the execution time of the on-time interval timer of the second DRX configuration. In this case, terminal device 110-1 does not need to monitor a PDCCH for the DCI format 2_6 for the WUS instruction of the first DRX configuration. The WUS instruction of the first DRX configuration can be carried within the UE-specific DCI. Terminal device 110-1 may monitor a PDCCH with the UE-specific DCI for the WUS instruction of the first DRX configuration within the active time resulting from the execution of the on-time interval timer of the second DRX configuration. The specific DCI format may be a scheduling DCI format such as, for example, DCI format 0_1 / 1_1, 0_2 / 1_2, etc. In some other embodiments, there may be a new or unused field in the DCI to indicate wake-up information to indicate whether or not to start the on-time interval timer for the first DRX setting.

[0140] Alternatively, network device 120 may transmit a MAC CE to terminal device 110-1. The MAC CE may indicate a WUS instruction for a first DRX configuration. For example, a MAC CE carried on PDSCH may include a mapping between the WUS and the index of the target DRX configuration.

[0141] In some embodiments, if the DRX-on time interval windows of two DRX settings overlap in the time domain, or if the time offset between the DRX-on time interval windows is less than the value x, the terminal device 110-1 may fall back and skip the WUS monitoring of the first DRX setting.

[0142] According to the above embodiment, if the WUS monitoring occasion of the first DRX setting falls within the on-time interval window of the second DRX setting, the UE can decide whether or not to start the on-time interval timer of the first DRX setting, thereby improving system performance.

[0143] Figure 17 is a flowchart of an exemplary method 1700 according to an embodiment of the present disclosure. For illustrative purposes only, method 1700 may be implemented in a network device 120-1 as shown in Figure 1.

[0144] In block 1710, terminal device 110-1 receives multiple DRX settings for a serving cell or serving cell group from network device 120. The DRX settings may include one or more of the following parameters: (1) DRX on-duration timer: Time interval at the start of a DRX cycle, (2) DRX slot offset: Delay before the DRX on-duration timer starts, (3) DRX inactivity timer: Time interval after a PDCCH occasion in which the Physical Downlink Control Channel (PDCCH) indicates a new uplink (UL) or downlink (DL) transmission for a Media Access Control (MAC) entity, (4) DRX retransmission timer DL (per DL Hybrid Automatic Retransmission Request (HARQ) process, excluding broadcast processes): Maximum time interval until a DL retransmission is received, (5) DRX retransmission timer UL (per UL HARQ process): Maximum time interval until permission for a DL retransmission is received, (6) DRX long cycle start offset: Long DRX cycle and DRX start offset that define the subframes in which long and short DRX cycles begin, (7) DRX short cycle (8) DRX short cycle timer: the time interval at which a UE should follow the short DRX cycle, (9) DRA HARQ round trip time (RTT) timer DL (per DL HARQ process excluding broadcast processes): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission, (10) DRX HARQ RTT timer UL (per UL HARQ process): the minimum time interval before a MAC entity expects a DL allocation for HARQ retransmission.(11) PS wake up: A setting to start the associated DRX on time interval timer if DCP is monitored but not detected. (12) PS transmit other periodic CSI: A setting to report periodic channel status information (CSI) on the physical uplink control channel (PUCCH) that is not Layer 1 reference signal received power (L1-RSRP) during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started. (13) PS transmit periodic L1-RSRP: A setting to report periodic CSI that is L1-RSRP on the PUCCH during the time interval indicated by the DRX on time interval timer, when DCP is set but the associated DRX on time interval timer has not been started.

[0145] In some embodiments, each of the multiple DRX settings may be configured separately. For example, the parameters described above can be configured separately for each DRX setting. Alternatively, each of the multiple DRX settings may include a set of RRC parameters common to the multiple DRX settings and another set of RRC parameters specific to that DRX setting. In other words, some of the parameters described above can be configured separately for each setting, while other parameters can be common to the multiple DRX settings within a serving cell or serving cell group. For example, one or more of the parameters, such as the DRX slot offset, DRX long cycle start offset, and DRX short cycle, can be configured separately for different DRX settings. Thus, the configuration of multiple DRX settings for a single serving cell or serving cell group is achieved.

[0146] In block 1720, the network device 120 transmits the settings for the Search Space Set Group (SSSG) for each DRX setting to the terminal device 110-1. If multiple DRX settings are configured for different XR flows, and each DRX setting has a corresponding SSSG, the terminal device 110-1 can monitor the PDCCH within the DRX-on time interval of the DRX setting based on the SSSG settings. The terminal device 110-1 can determine the association between the DRX setting index and the SSSG index based on the RRC settings. The SSSG may be implicitly switched between multiple SSSGs based on the running DRX setting index for the next active time interval. For example, if SSSG#0 is configured for DRX setting #1, and SSSG#1 is configured for DRX setting #0, and the DRX on-time interval timer for DRX setting #1 is running, the terminal device will monitor the PDCCH according to SSSG#0, and after the DRX on-time interval timer for DRX setting #1 expires, the terminal device will start monitoring the PDCCH according to SSSG#1, and will stop monitoring the PDCCH according to SSSG#0 for the serving cell x ms before the start of the DRX on-time interval for DRX setting #0. However, if the on-time interval time windows of the two DRX settings overlap, it is unclear to the terminal device which SSSG to monitor the PDCCH according to within the overlapping on-time interval time window, because the overlapping on-time interval time windows are associated with the two SSSGs.

[0147] In some embodiments, the network device 120 may transmit an RRC setting to the terminal device 110-1. The RRC setting may indicate the index of the target SSSG. Alternatively, the network device 120 may transmit a DCI to the terminal device 110-1. The DCI may indicate the index of the target SSSG. In other embodiments, overlapping on-time interval windows may be associated with a first DRX setting and a second DRX setting.

[0148] In some embodiments, the terminal device includes a circuit that receives a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device, and the terminal device determines one set of target DRX timers or one set of target DRX settings from the plurality of DRX settings, and the terminal device is configured to monitor a physical downlink control channel (PDCCH) based on the set of target DRX timers or the set of target DRX settings.

[0149] In some embodiments, the terminal device comprises a circuit configured to maintain a plurality of DRX timers for the plurality of DRX settings, and the terminal device comprises a circuit configured to monitor the PDCCH by monitoring the PDCCH during the execution time of one or more DRX timers from the set of target DRX timers.

[0150] In some embodiments, the one or more DRX timers include at least one of a DRX on-time interval timer, a DRX inactive timer, or a DRX retransmission timer.

[0151] In some embodiments, the terminal device comprises a circuit configured to receive the PDCCH on the serving cell within an on-time interval time window based on a plurality of DRX on-time interval timers associated with the plurality of DRX settings, and the terminal device comprises a circuit configured to determine the set of target DRX timers by determining the target DRX inactive timers of the DRX settings from the plurality of DRX settings and starting the target DRX inactive timers.

[0152] In some embodiments, the terminal device comprises a circuit configured to determine the target DRX inactive timer by selecting the target DRX inactive timer based on predetermined information, wherein the predetermined information indicates one of the following: the target DRX inactive timer having the minimum or maximum value among a plurality of DRX inactive timers; the target DRX inactive timer for the DRX setting having the highest or lowest setting index among a plurality of DRX settings; the target DRX inactive timer for the DRX setting having the longest or shortest DRX period among a plurality of DRX settings; or the target DRX inactive timer for the DRX setting associated with the traffic flow having the highest or lowest priority value among a plurality of traffic flows.

[0153] In some embodiments, the terminal device comprises a circuit configured to determine the target DRX inactive timer by determining the target DRX inactive timer based on at least one of radio resource control (RRC) settings or downlink control information.

[0154] In some embodiments, the RRC setting indicates an index of the target DRX setting, or the downlink control information indicates one of the index of the target DRX setting or a traffic flow associated with the DRX setting, the RRC setting indicates a table of the multiple DRX settings, and the downlink control information indicates an index of the target DRX setting.

[0155] In some embodiments, the terminal device comprises a circuit configured to receive a media access control element (MAC CE) indicating the index of a target DRX setting that carries a DRX command within the execution time of the plurality of DRX timers of the plurality of DRX settings, each including a DRX on-time interval timer or a DRX inactive timer, apply the DRX command to the target DRX setting, and stop the DRX on-time interval timer or DRX inactive timer of the target DRX setting.

[0156] In some embodiments, the terminal device comprises a circuit configured to receive a media access control element (MAC CE) carrying a DRX command within the execution time of the plurality of DRX timers, each of which includes a DRX on-time interval timer or a DRX inactive timer, and to stop the plurality of DRX timers.

[0157] In some embodiments, the terminal device comprises a circuit which receives downlink control information for scheduling physical downlink shared channel (PDSCH) transmissions for a third traffic flow, and is configured to receive MAC CEs carrying DRX commands within the execution time of the plurality of DRX timers of the plurality of DRX settings, each including a DRX on-time interval timer or a DRX inactive timer, and to stop the DRX on-time interval timer or DRX inactive timer of a target DRX setting associated with the third traffic flow.

[0158] In some embodiments, the plurality of DRX settings include a first DRX setting and a second DRX setting, wherein the first DRX setting includes a first DRX timer and the second setting includes a second DRX timer, and the terminal device comprises a circuit configured to monitor the PDCCH based on at least one DRX setting by monitoring the PDCCH during the execution time of the first DRX timer and skipping the second DRX timer upon determination that the time offset between the end symbol of the first DRX timer and the start symbol of the second DRX timer does not exceed a predetermined or set gap.

[0159] In some embodiments, the plurality of DRX settings include a first DRX setting and a second DRX setting, wherein the first DRX setting includes a first set of DRX timers and the second setting includes a second set of DRX timers, and the terminal device includes a circuit configured to monitor the PDCCH based on the at least one DRX setting by monitoring the PDCCH during the execution time of the first set of DRX timers, switching to the second set of DRX timers in accordance with a determination that downlink control information received from the network device includes a switching instruction, and monitoring the PDCCH during the execution time of the second set of DRX timers.

[0160] In some embodiments, the plurality of DRX settings include a first DRX setting and a second DRX setting, wherein the first DRX setting includes a first set of DRX timers and the second setting includes a second set of DRX timers, and the terminal device comprises a circuit configured to monitor the PDCCH based on the at least one DRX setting by monitoring the PDCCH during the execution time of the first set of DRX timers, switching to the second set of DRX timers in accordance with a determination that the switching timer has expired, and monitoring the PDCCH during the execution time of the second set of DRX timers.

[0161] In some embodiments, each of the multiple DRX settings includes a set of dedicated RRC parameters.

[0162] In some embodiments, each of the plurality of DRX settings includes a first set of common RRC parameters and a second set of dedicated RRC parameters.

[0163] In some embodiments, the terminal device comprises a circuit that receives a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device, and is configured to detect a power saving instruction signal within a monitoring window associated with one or more of the plurality of DRX settings, and to start a DRX on time interval timer for one of the plurality of DRX settings based on the detection of the power saving instruction signal.

[0164] In some embodiments, the terminal device comprises a circuit configured to determine the frequency domain resources of the monitoring window and, based on the frequency domain resources, determine a target DRX setting from the plurality of DRX settings, and the terminal device comprises a circuit configured to start the DRX on time interval timer by starting the DRX on time interval timer for the target DRX setting.

[0165] In some embodiments, the terminal device comprises a circuit configured to determine a sequence for scrambling the power saving instruction signal and, based on the sequence, determine a target DRX setting from a plurality of DRX settings, and the terminal device comprises a circuit configured to start the DRX on time interval timer by starting the DRX on time interval timer for the target DRX setting.

[0166] In some embodiments, the DRX on time interval timer is one of the following: the DRX on time interval timer having a maximum value, the DRX on time interval timer having a minimum value, or the DRX on time interval timer having the start time closest to the WUS.

[0167] In some embodiments, the terminal device includes a circuit configured to receive radio resource control (RRC) settings indicating target DRX settings from the network device, and the terminal device includes a circuit configured to start the DRX on time interval timer by starting the DRX on time interval timer for the target DRX settings.

[0168] In some embodiments, the terminal device includes a circuit configured to stop monitoring the PDCCH within the monitoring window in accordance with a determination that downlink control information for the power saving instruction signal indicates that the DRX on time interval timer should start.

[0169] In some embodiments, the terminal device includes a circuit configured to stop monitoring the PDCCH within the monitoring window and skip the DRX on-time interval timer for the multiple DRX settings, in accordance with the determination that the PDCCH for the power saving instruction signal indicates not to start the DRX on-time interval timer.

[0170] In some embodiments, the plurality of DRX settings include a first DRX setting and a second DRX setting, wherein the first monitoring window of the first DRX setting for detecting the power saving instruction signal is within the execution time of the on-time interval timer of the second DRX setting.

[0171] In some embodiments, the terminal device includes a circuit configured to receive a PDCCH having group common downlink control information for the power saving instruction signal within the first monitoring window.

[0172] In some embodiments, the terminal device comprises a circuit configured to receive a PDCCH having specific downlink control information for the power saving instruction signal within the execution time of the on-time interval timer of the second DRX setting.

[0173] In some embodiments, the terminal device comprises a circuit configured to receive a media access control element (MAC CE) from the network device indicating a mapping between the power saving instruction signal and the index of the target DRX setting.

[0174] In some embodiments, the terminal device comprises a circuit that receives multiple discontinuous reception (DRX) settings for a serving cell or serving cell group from a network device, the terminal device receives settings for a search space set group (SSSG) for each DRX setting from the network device, and the terminal device is configured to monitor a physical downlink control channel (PDCCH) based on one or more search space set groups (SSSGs) within overlapping on-time interval windows of the multiple DRX settings.

[0175] In some embodiments, the terminal device includes a circuit configured to monitor the PDCCH by monitoring the PDCCH based on a predetermined SSSG.

[0176] In some embodiments, the terminal device comprises a circuit configured to receive a radio resource control setting from the network device indicating the index of a target SSSG, and the terminal device comprises a circuit configured to monitor the PDCCH by monitoring the PDCCH based on the target SSSG.

[0177] In some embodiments, the terminal device includes a circuit configured to receive downlink control information from the network device indicating the index of a target SSSG, and the terminal device also includes a circuit configured to monitor the PDCCH by monitoring the PDCCH based on the target SSSG.

[0178] In some embodiments, the overlapping on-time interval windows are associated with a first DRX setting and a second DRX setting, and the terminal device includes a circuit configured to monitor the PDCCH within the overlapping on-time interval windows by monitoring the PDCCH based on a first SSSG associated with the first DRX setting and a second SSSG associated with the second DRX setting.

[0179] In some embodiments, the network device includes a circuit that transmits a plurality of discontinuous reception (DRX) settings for a serving cell or serving cell group to a terminal device, and the network device is configured to transmit a search space set group (SSSG) setting for each DRX setting to the terminal device.

[0180] In some embodiments, the network device includes a circuit configured to transmit a radio resource control setting indicating the index of the target SSSG to the terminal device.

[0181] In some embodiments, the network device includes a circuit configured to transmit downlink control information indicating the index of the target SSSG to the terminal device.

[0182] Figure 18 is a schematic block diagram of a device 1800 suitable for implementing an embodiment of the present disclosure. The device 1800 can be considered as another exemplary embodiment of the network device 120 or terminal device 110 shown in Figure 1. Thus, the device 1800 may be implemented in or as part of the terminal device 110 or network device 120.

[0183] As illustrated, the device 1800 comprises a processor 1810, a memory 1820 coupled to the processor 1810, a suitable transmitter (TX) and receiver (RX) 1840 coupled to the processor 1810, and a communication interface coupled to the TX / RX 1840. The memory 1820 stores at least a portion of the program 1830. The TX / RX 1840 is used for bidirectional communication. The TX / RX 1840 has at least one antenna to facilitate communication, although the access node referred to herein may actually have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0184] It is assumed that program 1830 includes program instructions that, when executed by the associated processor 1810, enable the device 1800 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 2 to 17. Embodiments of the present disclosure may be implemented by computer software executable by the processor 1810 of the device 1800, by hardware, or by a combination of software and hardware. The processor 1810 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1810 and memory 1820 may form a processing means suitable for implementing various embodiments of the present disclosure.

[0185] Memory 1820 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. Although only one memory 1820 is shown in device 1800, several physically different memory modules may be present in device 1800. Processor 1810 may be of any type suitable for a local technology network and may include, as non-limiting examples, one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. Device 1800 may have multiple processors, for example, application-specific integrated circuit chips that are temporally dependent on a clock that synchronizes the main processor.

[0186] Overall, various embodiments of the Disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various embodiments of the Disclosure are illustrated and described using block diagrams, flowcharts, or any other pictorial representation, it should be understood that any blocks, devices, systems, techniques, or methods described herein may be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0187] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in a program module, which are executed within a device on a target real or virtual processor to perform the processes or methods described above with reference to Figures 2-12. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or realize a specific abstract data type. In various embodiments, the functions of program modules may be combined or separated among program modules as needed. The machine-executable instructions of a program module may be executed within a local or distributed device. In a distributed device, the program module may reside in both local and remote storage media.

[0188] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when executed by the processor or controller, the program code may implement the functions / operations specified in the flowcharts and / or block diagrams. The program code may run entirely on a machine, partially on a machine, as an independent software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0189] The program code described above may be implemented on a machine-readable medium, which may be any tangible medium that can contain or store programs used by or associated with an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatus, or any suitable combination of the aforementioned mediums. More specific examples of machine-readable storage media may include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0190] While the operations have been described in a specific order, it should not be understood that, in order to obtain the desired results, these operations must be performed in the specific order shown, or in a sequential order, or that all of the described operations must be performed. In some cases, multitasking and parallel processing may be advantageous. Similarly, while some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some features described in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately or in any suitable subcombination in multiple embodiments.

[0191] While this disclosure has been described in language specific to structural features and / or methodological behavior, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and behaviors described above are disclosed as exemplary forms of implementing the claims.

[0192] As used herein, the term “terminal device” refers to any device having wireless or wired communication capabilities. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable low-latency communication (URLLC) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, in-vehicle devices for V2X communication where X represents pedestrians, vehicles, or infrastructure / networks, devices for integrated access and integrated access and backhaul (IAB), satellite-borne or aircraft-borne vehicles within non-terrestrial networks (NTN) including high-altitude platforms (HAP) encompassing satellites and unmanned aircraft systems (UAS), extended reality (XR) devices including different types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR), and unmanned aerial vehicles (UAVs), which are aircraft without human pilots and are commonly referred to as drones. This includes, but is not limited to, devices on a vehicle, a high-speed train (HST), or image acquisition devices such as digital cameras, sensor game devices, music storage and playback devices, or internet-connected home appliances that enable wireless or wired internet access and browsing. A “terminal device” may further have “multicast / broadcast” capabilities to support V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, smart TV, wireless services, wireless software distribution, group communications, and IoT applications, where public safety and mission are of paramount importance. It may also incorporate one or more Subscriber Identity Modules (SIMs), known as multi-SIMs.The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or radio device.

[0193] The term "network device" refers to a device that can provide or host a cell or coverage on which terminal devices can communicate. Examples of network devices include, but are not limited to, low-power nodes such as Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), Next Generation Node B (gNB), Transmit / Receive Point (TRP), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), IAB node, Femtonode, Piconode, and Reconfigurable Intelligent Surface (RIS).

[0194] Terminal devices or network devices may possess artificial intelligence (AI) or machine learning capabilities. Generally, this includes a trained model derived from a large amount of data collected for a specific function, which can be used to predict certain information.

[0195] Terminal or network devices may operate on several frequency ranges, such as FR1 (410 MHz to 7125 MHz), FR2 (24.25 GHz to 71 GHz), frequency bands greater than 100 GHz, and terahertz (THz). Furthermore, they can operate on permitted / unpermitted / shared spectrum. Terminal devices may have two or more connections to network devices under Multi-Radio Dual Connectivity (MR-DC) application scenarios. Terminal or network devices can operate in full-duplex, flexible-duplex, or cross-split-duplex modes.

[0196] Embodiments of this disclosure may be implemented, for example, in test equipment such as signal generators, signal analyzers, spectrum analyzers, network analyzers, test terminal devices, test network devices, and channel emulators.

[0197] Embodiments of the present disclosure may be implemented in accordance with any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or sixth-generation (6G) networks.

Claims

1. A means for receiving a Radio Resource Control (RRC) message from a network device indicating at least one Discontinuous Reception (DRX) setting from a list of DRX settings for a serving cell, wherein each of the at least one DRX settings is associated with a Radio Network Temporary Identifier (RNTI), and the receiving means When a DRX command medium access control (MAC) control element (CE) is received, indicated by a physical downlink control channel (PDCCH) associated with a first DRX setting among the at least one DRX setting, means for stopping the DRX on-time timer of the first DRX setting, A terminal device equipped with the following features.

2. The means for stopping the DRX on-time timer is, When the DRX command MAC CE, indicated by the PDCCH, is received and addressed to the RNTI associated with the first DRX setting, the system includes means for stopping the DRX on-time timer of the first DRX setting. The terminal device according to claim 1.

3. The system further includes means for stopping the DRX inactive timer of the first DRX setting when the DRX command MAC CE, indicated by the PDCCH, is received and addressed to the RNTI associated with the first DRX setting among the at least one DRX setting. The terminal device according to claim 1.

4. The DRX operation for each DRX setting of the aforementioned at least one DRX setting is performed independently. The terminal device according to claim 1.

5. A first means for transmitting a Radio Resource Control (RRC) message to a terminal device, the RRC message indicating at least one Discontinuous Reception (DRX) setting from a serving cell's DRX setting list, wherein each of the at least one DRX setting is associated with a Radio Network Temporary Identifier (RNTI), and the transmitting first means: A second means for transmitting a DRX command medium access control (MAC) control element (CE) to the terminal device, which is indicated by a physical downlink control channel (PDCCH) associated with a first DRX setting among the at least one DRX setting, wherein the DRX command MAC CE is used by the terminal device to stop the DRX on-time timer of the first DRX setting, and the second means for transmitting, A network device equipped with the following features.

6. The first means that transmits the DRX command MAC CE is The terminal device is sent the DRX command MAC CE, indicated by the PDCCH, addressed to the RNTI associated with the first DRX setting. The network device according to claim 5.

7. The DRX command MAC CE is further used by the terminal device to stop the DRX inactive timer of the first DRX setting. The network device according to claim 5.

8. The DRX operation for each DRX setting of the aforementioned at least one DRX setting is performed independently. The network device according to claim 5.

9. A method of communication performed by a terminal device, Receiving a Radio Resource Control (RRC) message from a network device indicating at least one Discontinuous Reception (DRX) setting from a list of DRX settings for a serving cell, wherein each of the at least one DRX settings is associated with a Radio Network Temporary Identifier (RNTI), and the receiving When a DRX command medium access control (MAC) control element (CE) is received, indicated by the physical downlink control channel (PDCCH) associated with the first DRX setting among the at least one DRX setting, the DRX on time timer of the first DRX setting is stopped. A method that includes this.

10. Stopping the DRX ON time timer means When the DRX command MAC CE, indicated by the PDCCH, is received and addressed to the RNTI associated with the first DRX setting, the DRX on-time timer of the first DRX setting is stopped. The method according to claim 9.

11. If the DRX command MAC CE, indicated by the PDCCH, is received and is addressed to the RNTI associated with the first DRX setting among the at least one DRX setting, the DRX inactive timer of the first DRX setting is further stopped. The method according to claim 9.

12. The DRX operation for each DRX setting of the aforementioned at least one DRX setting is performed independently. The method according to claim 9.

13. A method of communication performed by a network device, A first transmission to a terminal device, which involves transmitting a Radio Resource Control (RRC) message indicating at least one Discontinuous Reception (DRX) setting from a serving cell's DRX setting list, wherein each of the at least one DRX settings is associated with a Radio Network Temporary Identifier (RNTI), A second transmission to the terminal device, wherein the DRX command Medium Access Control (MAC) control element (CE) is indicated by a Physical Downlink Control Channel (PDCCH) associated with a first DRX setting among the at least one DRX setting, and the DRX command MAC CE is used by the terminal device to stop the DRX on-time timer of the first DRX setting. A method that includes this.

14. The first transmission of the DRX command MAC CE is The terminal device is sent the DRX command MAC CE, indicated by the PDCCH, addressed to the RNTI associated with the first DRX setting. The method according to claim 13.

15. The DRX command MAC CE is further used by the terminal device to stop the DRX inactive timer of the first DRX setting. The method according to claim 13.

Images