Power saving methods for user equipment in a cell group and its network nodes

Abstract

The method includes: communicating with a first group of cells and receiving a first indicator that notifies a user equipment (UE) to enable scheduling with at least one second group of cells. The method further includes: based on the first indicator, starting a first inactivity timer associated with at least one second group of cells, and scheduling communication with at least one second group of cells after the start of the first inactivity timer. A network node performs the method.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Application No. 62 / 985,456, filed March 5, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] One or more example embodiments relate to wireless communication networks. Background Technology

[0004] Fifth-generation (5G) wireless communication networks are the next generation of mobile communication networks. 5G communication network standards are currently being developed by the 3rd Generation Partnership Project (3GPP). These standards are known as the 3GPP New Radio (NR) standards. Summary of the Invention

[0005] At least one example embodiment relates to a method.

[0006] In one example embodiment, the method includes: communicating with a first group of cells by at least one processor of a user equipment (UE); receiving a first indicator by at least one processor of the user equipment (UE), the first indicator notifying the UE to enable scheduling with at least one second group of cells; starting a first inactivity timer associated with at least one second group of cells by at least one processor based on the first indicator; and scheduling communication with at least one second group of cells by at least one processor after the start of the first inactivity timer.

[0007] In one example embodiment, the first group of cells is a primary discontinuous reception (P-DRX) cell group, and at least one second group of cells is a secondary discontinuous reception (S-DRX) cell group.

[0008] In one example embodiment, P-DRX cell groups use a lower frequency range for transmission compared to S-DRX cell groups.

[0009] In one example embodiment, the first inactive timer is a DRX inactive timer for the discontinuous reception (DRX) cycle of the S-DRX cell group.

[0010] In one example embodiment, the S-DRX group includes a first physical downlink control channel (PDCCH) monitoring scheme with a first repeated discontinuous reception (DRX) period, the first repeated DRX period including a first uplink / downlink traffic period and a first OnDuration period; the P-DRX group includes a second physical downlink control channel (PDCCH) monitoring scheme with a second repeated discontinuous reception (DRX) period, the second repeated DRX period including a second uplink / downlink traffic period and a second OnDuration period, and the first downlink period and the first OnDuration period are respectively shorter than the second downlink period and the second OnDuration period.

[0011] In one example embodiment, the first length of the first repeating DRX cycle is the same as the second length of the second repeating DRX cycle.

[0012] In one example embodiment, the scheduling of communications includes activating one or more cells from at least one second group of cells.

[0013] In one example embodiment, the scheduling of communications includes sending a command to one or more cells in at least one second group of cells to cause one or more cells to switch from a dormant state to a non-dormant state.

[0014] In one example embodiment, the method further includes: receiving a second indicator indicating that at least one second group of cells is in a dormant state; and based on the receipt of the second indicator, stopping a first inactive timer and a DRXOnDuration timer.

[0015] In one example embodiment, the method further includes: receiving a second indicator indicating that at least one second group of cells is in a dormant state; and based on the receipt of the second indicator, ensuring that the DRX OnDuration timer is not started.

[0016] At least another example embodiment includes a network node.

[0017] In one example embodiment, the network node includes: a memory containing computer-readable instructions; and at least one processor configured to read and execute the computer-readable instructions to communicate with a first group of cells, receive a first indicator that notifies the network node to enable scheduling with at least one second group of cells, start a first inactivity timer associated with at least one second group of cells based on the first indicator, and schedule communication with at least one second group of cells after the start of the first inactivity timer.

[0018] In one example embodiment, the first group of cells is a primary discontinuous reception (P-DRX) cell group, and at least one second group of cells is a secondary discontinuous reception (S-DRX) cell group.

[0019] In one example embodiment, P-DRX cell groups use a lower frequency range for transmission compared to S-DRX cell groups.

[0020] In one example embodiment, the first inactive timer is a DRX inactive timer for the discontinuous reception (DRX) cycle of the S-DRX cell group.

[0021] In one example embodiment, the S-DRX group includes a first physical downlink control channel (PDCCH) monitoring scheme with a first repeated discontinuous reception (DRX) period, the first repeated DRX period including a first uplink / downlink traffic period and a first OnDuration period; the P-DRX group includes a second physical downlink control channel (PDCCH) monitoring scheme with a second repeated discontinuous reception (DRX) period, the second repeated DRX period including a second uplink / downlink traffic period and a second OnDuration period, and the first downlink period and the first OnDuration period are respectively shorter than the second downlink period and the second OnDuration period.

[0022] In one example embodiment, the first length of the first repeating DRX cycle is the same as the second length of the second repeating DRX cycle.

[0023] In one example embodiment, at least one processor is also configured to schedule communications by activating one or more cells in at least one second group of cells.

[0024] In one example embodiment, at least one processor is further configured to schedule communication by sending commands to one or more cells in at least one second group of cells to cause one or more cells to switch from a dormant state to a non-dormant state.

[0025] In one example embodiment, at least one processor is further configured to: receive a second indicator indicating that at least one second group of cells is in a dormant state, and based on the receipt of the second indicator, stop a first inactive timer and a DRX OnDuration timer.

[0026] In one example embodiment, at least one processor is further configured to: receive a second indicator indicating that at least one second group of cells is in a dormant state, and based on the receipt of the second indicator, ensure that the DRXOnDuration timer is not started. Attached Figure Description

[0027] Exemplary embodiments will be more fully understood from the detailed description and accompanying drawings given below, wherein similar elements are indicated by similar reference numerals, which are given by way of illustration only and therefore do not limit this disclosure.

[0028] Figure 1 A simplified diagram is shown to illustrate a portion of the 3GPP New Radio (NR) access deployment used to explain an example embodiment;

[0029] Figure 2 A block diagram of a gNB according to an example embodiment is shown;

[0030] Figure 3 A block diagram of a user equipment (UE) according to an example embodiment is shown;

[0031] Figure 4 The discontinuous reception (DRX) cycle of the UE in the example embodiment is shown;

[0032] Figure 5 A configuration involving multiple DRX groups according to an example embodiment is shown; and

[0033] Figure 6 A power-saving method for a UE using multiple DRX groups in an example embodiment is shown.

[0034] It should be noted that these figures are intended to illustrate the general characteristics of the methods, structures, and / or materials utilized in some exemplary embodiments and to supplement the written description provided below. However, these figures are not drawn to scale and may not accurately reflect the precise structural or performance characteristics of any given embodiment, and should not be construed as defining or limiting the range of values ​​or characteristics contained in the exemplary embodiments. The use of similar or identical reference numerals in the various figures is intended to indicate the presence of similar or identical elements or features. Detailed Implementation

[0035] Various exemplary embodiments will now be described more fully with reference to the accompanying drawings, some of which illustrate exemplary embodiments.

[0036] Detailed illustrative embodiments are disclosed herein. However, the specific structural and functional details disclosed herein are representative only for the purpose of describing exemplary embodiments. Furthermore, exemplary embodiments may be embodied in many alternative forms and should not be construed as being limited to the embodiments set forth herein.

[0037] It should be understood that the exemplary embodiments are not intended to limit the specific forms disclosed. Rather, the exemplary embodiments will cover all modifications, equivalents, and substitutions falling within the scope of this disclosure. Throughout the description of the drawings, the same numbers refer to the same elements.

[0038] While one or more example embodiments may be described from the perspective of radio network elements (e.g., gNB), user equipment, etc., it should be understood that one or more example embodiments discussed herein can be executed by one or more processors (or processing circuitry) at an applicable device. For example, according to one or more example embodiments, at least one memory may include or store computer program code, and at least one memory and computer program code may be configured, together with at least one processor, to cause the radio network element (or user equipment) to perform the operations discussed herein.

[0039] It should be understood that multiple example embodiments can be used in combination.

[0040] Figure 1 A simplified diagram is shown as a portion of a 3GPP New Radio (NR) access network 10 used to explain an example embodiment. The 3GPP NR radio access deployment includes a base station (e.g., gNB 102) with transmit and receive points (TRPs) 102a, 102b, 102c. Each TRP 102a, 102b, 102c may be, for example, a remote radio headend (RRH) or remote radio unit (RRU), including at least, for example, a radio frequency (RF) antenna (or multiple antennas) or antenna panel, and a radio transceiver for transmitting and receiving data within a geographic area. In the example embodiment, from the perspective that TRPs 102a, 102b, 102c are smaller cells communicating with a larger cell (e.g., gNB 102), TRPs 102a, 102b, 102c can be considered as secondary cells (SCells). TRPs 102a, 102b, and 102c provide cellular resources for User Equipment (UE) 106a, 106b, and 106c within their geographical coverage area. In some cases, baseband processing can be partitioned between TRPs 102a, 102b, and 102c and gNB 102 within a fifth-generation (5G) cell. Alternatively, baseband processing can be performed at gNB 102. Figure 1 In the example shown, TRPs 102a, 102b, and 102c are configured to communicate with the UE (e.g., UE 106a) via one or more transmit (TX) / receive (RX) beam pairs. gNB 102 communicates with network core 1, which is referred to as the new core in 3GPP NR.

[0041] TRP 102a, 102b, and 102c can have independent schedulers, or gNB 102 can perform joint scheduling among TRP 102a, 102b, and 102c.

[0042] It should be understood that gNB 102 and TRPs 102a, 102b, 102c can provide communication services to a relatively large number of UEs 106a, 106b, 106c within the coverage area of ​​TRPs 102a, 102b, 102c. For clarity of the illustrative embodiments, the communication services (including the transmission and reception of radio signals) between gNB 102, TRP 102a, and / or UE 106a will be discussed primarily, although it should be understood that signals can be transmitted between any of gNB 102, TRPs 102a, 102b, 102c, and any of UEs 106a, 106b, 106c.

[0043] Figure 2 The gNB 102 according to an example embodiment is shown. Figure 1 The block diagram shown is illustrated. As shown, gNB 102 includes: a memory 240; a processor 220 connected to the memory 240; various interfaces 260 connected to the processor 220; and one or more antennas or antenna panels 265 connected to the various interfaces 260. The various interfaces 260 and antennas 265 can constitute a transceiver for transmitting / receiving data from / to gNB 102 via multiple wireless beams, or transmitting / receiving data from / to multiple TRPs 102a, 102b, 102c, etc. It should be understood that, depending on the implementation of gNB 102, gNB 102 may include more than Figure 2 The components shown are far more numerous than those shown. However, it is not necessary to show all of these components for the purpose of disclosing illustrative example embodiments.

[0044] Memory 240 may be a computer-readable storage medium, typically including random access memory (RAM), read-only memory (ROM), and / or permanent mass storage devices such as disk drives. Memory 240 also stores the operating system and any other routines / modules / applications used to provide the functionality of gNB 102 (e.g., gNB functionality, methods according to example embodiments, etc.) for execution by processor 220. These software components may also be loaded into memory 240 from a separate computer-readable storage medium using a drive mechanism (not shown). Such a separate computer-readable storage medium may include a disk, magnetic tape, DVD / CD-ROM drive, memory card, or other similar computer-readable storage medium (not shown). In some example embodiments, software components may be loaded into memory 240 via one of various interfaces 260 instead of via a computer-readable storage medium.

[0045] Processor 220 can be configured to execute instructions of a computer program by performing arithmetic, logical, and input / output operations of the system. Instructions can be provided to processor 220 by memory 240.

[0046] Various interfaces 260 may include components that interface the processor 220 with the antenna 265, or other input / output components. It should be understood that the various interfaces 260 and programs stored in memory 240 to describe the specific functions of gNB 102 will vary depending on the implementation of gNB 102.

[0047] Interface 260 may also include one or more user input devices (e.g., keyboard, keypad, mouse, etc.) and user output devices (e.g., display, speaker, etc.).

[0048] Although not specifically discussed in this article, Figure 2 The configuration shown can also be used to implement TRPs 102a, 102b, 102c, other radio access and backhaul network elements and / or devices, etc. In this regard, for example, memory 240 can store the operating system and any other routines / modules / applications, etc., used to provide the functionality of the TRP (e.g., the functionality of these elements, methods according to the example embodiment, etc.) to be executed by processor 220.

[0049] Figure 3 A block diagram of a user equipment (UE) 106a according to an example embodiment is shown. It should be understood that other UEs 106b, 106c have the same structure. UE 106a is used by the end user to... Figure 1 The equipment shown communicates via the 3GPP NR radio access deployment. Examples of UEs include cellular phones, smartphones, tablets, computers, laptops, etc.

[0050] As shown in the figure, UE 106a includes: a memory 340; a processor 320 connected to the memory 340; various interfaces 360 connected to the processor 320; and one or more antennas or antenna panels 365 connected to the various interfaces 360. The various interfaces 360 and antennas 365 can constitute a transceiver for transmitting / receiving data to / from gNB 102 via multiple wireless beams, or transmitting / receiving data to / from multiple TRPs 102a, 102b, 102c, etc. It should be understood that, depending on the implementation of UE 106a, UE 106a may include more than Figure 3 The components shown are far more numerous than those shown. However, it is not necessary to show all of these generally conventional components in order to disclose illustrative example embodiments.

[0051] Memory 340 may be a computer-readable storage medium, typically including random access memory (RAM), read-only memory (ROM), and / or permanent mass storage devices such as disk drives. Memory 340 also stores the operating system and any other routines / modules / applications used to provide the functionality of UE 106a (e.g., the functions of the UE, methods according to example embodiments, etc.) to be executed by processor 320. These software components may also be loaded into memory 340 from a separate computer-readable storage medium using a drive mechanism (not shown). Such a separate computer-readable storage medium may include a disk, magnetic tape, DVD / CD-ROM drive, memory card, or other similar computer-readable storage medium (not shown). In some example embodiments, software components may be loaded into memory 340 via one of various interfaces 360 instead of via a computer-readable storage medium.

[0052] Processor 320 can be configured to execute instructions of a computer program by performing arithmetic, logical, and input / output operations of the system. Instructions can be provided to processor 320 by memory 340.

[0053] Various interfaces 360 may include components that interface the processor 320 with the antenna 365, or other input / output components. It should be understood that the various interfaces 360 and programs stored in the memory 340 to describe the specific functions of the UE 106a will vary depending on the implementation of the UE 106a.

[0054] Interface 360 ​​may also include one or more user input devices (e.g., keyboard, keypad, mouse, etc.) and user output devices (e.g., display, speaker, etc.).

[0055] General concept:

[0056] In the example embodiment, when there is no data transmission to be transmitted, the Wake-up Signal (WUS) allows UE 106a to skip Physical Downlink Control Channel (PDCCH) monitoring during the planned monitoring period ('OnDuration' period). If the core 1 of the network (NW) 10 intends to schedule UE 106a, the core 1 needs to send a Wake-up Signal (WUS) to UE 106a during multiple WUS times to initiate a drx-onDurationTimer for UE 106a. Once notified of the WUS timer via WUS, UE 106a will monitor the PDCCH normally to schedule data during the upcoming OnDuration period.

[0057] In 3GPP, WUS is an indicator of Downlink Control Information (DCI) referred to as DCP, which has Cyclic Redundancy Check (CRC) scrambled by Power Saving Radio Network Temporary Identity (PS-RNTI). In alternative expressions, WUS or DCP may refer to a Physical Downlink Control Channel (PDCCH) transmission carrying a wake-up indication. This wake-up indication may include an indication for the UE to determine whether to start (or not start) the drx-onDurationTimer at the next occurrence of the timer, and it may additionally include indications regarding the sleep state of (multiple) SCells and / or (multiple) SCell groups.

[0058] When DRX is configured, the terminal device does not need to continuously monitor the PDCCH. DRX has the following characteristics:

[0059] - On-duration: The duration for which the UE waits to receive the PDCCH after being woken up. If the UE successfully decodes the PDCCH, the UE remains awake and starts an inactive timer;

[0060] - Inactive Timer: The duration for which the UE waits for a successful PDCCH decoding, starting from the last successful decoding. If it fails, the UE can re-enter sleep mode. The UE will restart the inactive timer after a single successful PDCCH decoding, and it is only used for the first transmission (i.e., not for retransmission).

[0061] - Retransmission timer: until the duration for which a retransmission can be expected;

[0062] - Period: Specifies the periodic repetition of the on-duration, followed by possible periods of inactivity;

[0063] -Active Duration: The total duration for which the UE monitors the PDCCH. This includes the "on-duration" of the DRX cycle, the time during which the UE performs continuous reception but the inactive timer has not yet expired, and the time during which the UE performs continuous reception while waiting for a retransmission opportunity.

[0064] Furthermore, when configured accordingly, the UE can be informed whether PDCCH monitoring is required during the next occurrence of the on-duration period by the DCP received on the active BWP. By default, if no DCP is detected on the active BWP, the UE will not monitor the PDCCH during the next occurrence of the on-duration period. However, in this case, it can also be configured to have the opposite behavior, i.e., to monitor the PDCCH during the next occurrence of the on-duration period.

[0065] The UE can only be configured to monitor DCP at multiple times at the configuration offset prior to the on-duration period, when connected mode DRX is configured. Multiple monitoring times can be configured prior to the on-duration period. The UE will not monitor DCP at times occurring during active periods, measurement gaps, or BWP handovers; in these cases, it will monitor PDCCH during the next on-duration period. If DCP is not configured in the active BWP, the UE follows normal DRX operation.

[0066] Discontinuous reception (DRX) period:

[0067] Figure 4 The discontinuous reception (DRX) cycle 400 of UE 106a in the example embodiment is shown. PDCCH monitoring occurs during these DRX cycles 400. Specifically, the PDCCH monitoring activity of UE 106a in Radio Resource Control (RRC) connection mode is dominated by DRX cycle 400, Bandwidth Adaptation (BA), and DCP govern.

[0068] In the example embodiment, when DRX period 400 is configured, UE 106a does not need to continuously monitor the PDCCH, thus saving power. DRX period 400 is characterized by several elements, including: an on-duration 402, an inactive timer, a retransmission timer, and an on-duration period. The on-duration 402 is the duration during which UE 106a waits to receive its PDCCH after waking up. If UE 106a successfully decodes the PDCCH, it remains awake and starts the inactive timer. In the example embodiment, the inactive timer is a timer that governs the duration during which UE 106a waits for successful PDCCH decoding, starting from the last successful decoding; if it fails, UE 106a returns to sleep. UE 106a will restart the inactive timer after a single successful decoding of the PDCCH, only for the first transmission (i.e., not for retransmissions). The retransmission timer is a timer that governs the duration until a retransmission can be expected. The active period is the total duration during which UE106a monitors the PDCCH. This includes the "on duration" 402 of DRX cycle 400, the time during which UE106a performs continuous reception but the inactive timer has not yet expired, and the time during which UE106a performs continuous reception while waiting for a retransmission opportunity. DRX cycle 400 is a periodic repetition of the on duration 402, followed by a possible inactive period 404.

[0069] In the example embodiment, the BA is configured such that UE 106a only needs to monitor the PDCCH on one active bandwidth portion (BWP). That is, UE 106a does not need to monitor the PDCCH across the entire downlink (DL) frequency of the cell. In the example embodiment, a BWP inactivity timer (independent of the aforementioned DRX inactivity timer) is used to switch the active BWP to the default BWP: the timer restarts upon successful PDCCH decoding, and the handover to the default BWP occurs upon its expiration. In 5G, a BWP is a set of contiguous physical resource blocks (PRBs) on a given carrier.

[0070] In the example embodiment, UE 106a is notified via a DCP received on the active BWP whether to monitor or not monitor the PDCCH during the next occurrence of the on-duration 402. In the example embodiment, by default, if UE 106a does not detect a DCP on the active BWP, UE 106a does not monitor the PDCCH during the next occurrence of the on-duration 402. However, in the example embodiment, UE 106a may alternatively be configured to monitor the PDCCH during the next occurrence of the on-duration.

[0071] In the example embodiment, UE 106a is configured to monitor DCP only at multiple points during the configuration offset prior to the on-duration 402, when the connection mode DRX is configured. In the example embodiment, more than one monitoring point may be configured prior to the on-duration. In the example embodiment, UE 106a does not monitor DCP at points occurring during active time, measurement gaps, or BWP handover; in such cases, UE 106a monitors PDCCH during the next on-duration. It should be understood that DCP is a wake-up indication to start or not start the DRX "on-duration" timer in UE 106a. In the example embodiment, if DCP is not configured in the active BWP, UE 106a follows normal DRX operation.

[0072] In the example embodiment, when carrier aggregation (CA) is configured, DCP is configured only on SpCell, where SpCell refers to the primary cell (PCell) of the primary cell group (MCG) or the primary and secondary cell (PSCell) of the secondary cell group (SCG).

[0073] In the example embodiment, a DCP is configured to independently control PDCCH monitoring during the on-duration 402 of one or more UEs 106.

[0074] In the example embodiment, when UE 106a determines that it is in a low-mobility scenario, or when UE 106a is not at the cell edge, UE 106a can relax the neighboring cell radio resource measurement (RRM) to achieve power saving in Radio Resource Control Idle mode (RRC_IDLE) and Radio Resource Control Inactive mode (RRC_INACTIVE). In the example embodiment, DCP can be configured to RRC_INACTIVE or RRC_IDLE mode.

[0075] In the example embodiment, UE 106a achieves power saving by using BWP handover to adapt to the maximum number of DLs in the Multiple-Input Multiple-Output (MIMO) layer.

[0076] In the example embodiment, power saving is enabled during the active period via cross-timeslot scheduling, which helps UE 106a achieve power saving, assuming that UE 106a will not be scheduled to receive the Physical Downlink Shared Channel (PDSCH), triggered to receive Channel State Information (A-CSI), or transmit the Physical Uplink Control Channel (PUSCH) scheduled by the PDCCH, until the minimum scheduling offsets K0 and K2. In the example embodiment, the dynamic adaptation of the minimum scheduling offsets K0 and K2 is controlled by the PDCCH.

[0077] SCell's hibernation BWP:

[0078] In the example embodiment, the "sleep" behavior involves multiple BWPs. In the example embodiment, for example, the sleep behavior includes at most one BWP as a sleep BWP and one BWP as a non-sleep BWP (or the first BWP after sleep, or the BWP from which the UE switches from the sleep BWP), or alternatively, it includes one BWP as a sleep BWP and other BWPs as regular BWPs. A sleep BWP is a BWP without PDCCH monitoring and has limited or no UL operation. In the example embodiment, network core 1 can switch between sleep BWPs and non-sleep BWPs using a "bit indication" (bit identifier, or indicator), which can be transmitted during active time or outside of active time (with slightly different signals). In other words, in the example embodiment, when network core 1 sends an indicator to UE 106a via processor 220 of gNB 102 to notify UE 106a to switch from a sleep BWP to a non-sleep BWP, UE 106a switches from the sleep BWP to the first non-sleep BWP ID (for PDCCH monitoring). The first non-dormant BWP ID can be different during the active period compared to the active period.

[0079] Monitor hibernation / non-hibernation:

[0080] In the example embodiment, the sleep / non-sleep behavior of PDCCH monitoring and SCell includes the following:

[0081] UE 106a is configured to operate in DRX mode via PCell or SCell.

[0082] The position of the wake-up indicator bit in DCI format 2_6 is in PSPositionDCI2-6, where:

[0083] - When the value of the "PDCCH Monitoring" bit is "0", UE 106a does not start the drx-onDurationTimer for the next long DRX cycle 400, and

[0084] - When the value of the “PDCCH monitoring” bit is “1”, UE 106a starts the drx-onDurationTimer for the next long DRX cycle 400.

[0085] In the example embodiment, when UE 106a is provided with multiple configured SCell groups via SCell-groups-for-dormancy-outside-active-time, the bitmap occurs in the following cases:

[0086] - The bitmap position immediately follows the "PDCCH Monitoring" bit position.

[0087] - The bitmap size is equal to the number of configured SCell groups, where each bit of the bitmap corresponds to a set of configured SCells from that number of configured SCell groups.

[0088] - The "0" value of a bit in the bitmap indicates the active DL BWP provided by the dormant BWP for UE 106a for each active SCell in the corresponding configured SCell group, and

[0089] - The "1" value of the bit in the bitmap indicates the active DLBWP provided for UE 106a by first-non-dormant-BWP-ID-for-DCI-outside-active-time for each active SCell in the corresponding configured SCell group.

[0090] The DCP is a wake-up indication for enabling or disabling the drx-onDurationTimer in UE 106a, and the bitmap is an indication of the sleep states of a set of SCells 102a, 102b, and 102c configured when the drx-onDurationTimer is enabled. The bitmap indication of the sleep states can be configurable and can be configured when the UE is configured to sleep with SCells enabled.

[0091] In the example embodiment, UE 106a can be configured with up to five groups of SCells 102a, 102b, 102c for dedicated sleep behavior—each group can consist of a number of SCells (one or more). In one example, UE 106a can also be configured with more than five groups.

[0092] Multiple DRX groups:

[0093] Figure 5 A configuration involving multiple DRX groups according to an example embodiment is illustrated. In the example embodiment, the configuration may include a first group of PCells and zero or more SCells 102y, and a second group of one or more SCells 102z. In the example embodiment, the PCells and possible SCells 102y transmit using a first frequency range FR1, and the SCells 102z transmit using a second frequency range FR2. In the example embodiment, the first frequency range FR1 uses a lower frequency range compared to the second frequency range FR2. In the example embodiment, the PCell may also be associated with the second group of 102z.

[0094] In the example embodiment, both FR1 and FR2 cells are configured via carrier aggregation. In the example embodiment, FR2 cells can be configured with separate (and shorter) drx-inactivityTimer (406b) and drx-onDurationTimer (402b) compared to the drx-InactivityTimer (406a) and drx-OnDurationTimer (402a) of FR1 cells. The length of the long DRX period 400a / b and the length of the short DRX period (if configured) are common to both FR1 and FR2. In the example embodiment, FR2 cells enter sleep mode faster than FR1 cells, thus reducing power consumption. In the example embodiment, the first group of PCells and zero or more SCells can be referred to as the primary DRX group, while the second group of one or more SCells can be referred to as the secondary DRX group.

[0095] In the example embodiment, separate drx-InactivityTimer (406b) and drx-onDurationTimer (402b) can be configured for the secondary DRX group (FR2 cell). In the example embodiment, the combination of cross-carrier scheduling and secondary DRX group 102z is not supported.

[0096] In the example embodiment, the timer (406b / 402b) used for the FR2 DRX configuration is shorter than the timer (406a / 402a) used for the FR1 DRX configuration. In the example embodiment, the secondary DRX configuration can be applied to the existing DRX configurations of both FR2 and FR1 cells. It should be noted that a DRX group can also consist of a configured PCell and one or more SCells, or it can be configured in other ways regardless of frequency range.

[0097] Technical problems solved by some example embodiments:

[0098] In the example embodiment, the second group of one or more SCells 102z is a secondary DRX (S-DRX) group, and the first group of PCells and zero or more SCells 102y is a primary DRX (P-DRX) group. In the example embodiment, compared to the primary DRX (P-DRX) group configuration, the S-DRX group configuration operates with shorter drx-InactivityTimer 406b and drx-onDurationTimer 402b values, and the S-DRX group can be in a sleep state before the P-DRX group. In the example embodiment, because cross-carrier scheduling above the DRX group may not be supported, NW 10 cannot restart drx-InactivityTimer 406b for the S-DRX group, for example, when DL data suddenly becomes available for transmission after drx-InactivityTimer 406b expires. In the example implementation, this will force data transmission over cell 102z in the P-DRX group until the data is fully transmitted or the next drx-onDurationTimer opportunity becomes available so that cells in the S-DRX group can be scheduled.

[0099] An overview of some example embodiments:

[0100] In some example embodiments, when network 10 instructs at least one SCell group 102z to switch from a dormant BWP to a non-dormant BWP via primary DRX group 102y, the processor 320 of UE 106a starts / restarts the drx-InactivityTimer 406b associated with secondary DRX group 102z. In example embodiments, this is implemented to enable scheduling with S-DRX group 102z if UE 106a is no longer active, or if UE 106a will enter DRX during a BWP handover period in the S-DRX group.

[0101] In some embodiments, the drx-InactivityTimer 406b associated with the S-DRX group 102z is started / rebooted by the processor 320 of the UE 106a only when one or more SCell 102z associated with the S-DRX group switches from a dormant BWP to a non-dormant BWP.

[0102] In some example embodiments, by instructing (notifying) SCell group 102z to move to a non-sleeping BWP, NW 10 can also trigger the start / restart of drx-InactivityTimer 406b associated with the S-DRX group by SCell group 102z already operating on a non-sleeping BWP (or any other BWP that is not a sleeping BWP). In some example embodiments, in this case, UE 106a's processor 320 either switches the BWP of each associated SCell 102z to a non-sleeping BWP or keeps the current BWP active in each associated SCell 102z.

[0103] In some example embodiments, when network 10 instructs (notifies) all(multiple) SCell groups 102z associated with the S-DRX group to switch from BWP (non-dormant, regular, etc.) to dormant BWP, the processor 320 of UE 106a stops the drx-onDurationTimer 402b and drx-inactivityTimer 406b associated with the S-DRX group.

[0104] In some example embodiments, if the WUS instructs (notifies) all SCell groups 102z associated with the S-DRX group to remain / switch to a dormant BWP, then the processor 320 of the UE 106a does not start the drx-onDurationTimer 402b associated with the S-DRX group at the next drx-onDurationTimer 406b timing.

[0105] In some example embodiments, if UE 106a misses WUS because P-DRX group 102y is active and all SCell groups 102z associated with S-DRX group are configured to sleep BWP, then UE 106a's processor 320 does not start the S-DRX group's drx-onDurationTimer 402b at the next timing. Alternatively, UE 106a's processor 320 starts the drx-onDurationTimer 402b and switches (multiple) SCells / (multiple) SCell groups 102z to non-sleeping BWPs, for example, according to the method proposed in application 62 / 975,356 "Method for Enabling Secondary Cell Dormancy for User Equipment Power Savings" filed February 12, 2020.

[0106] In some example embodiments, all SCell(s) / SCell groups 102z associated with an S-DRX group are implicitly assumed to be in a dormant state after the drx-InactivityTimer 406b associated with the S-DRX group expires. In example embodiments, drx-InactivityTimer 406a may also be associated with the main DRX group 102y.

[0107] In some example implementations, when an SCell 102z belonging to an S-DRX group is configured but not activated, and the SCell 102z becomes activated via a cell in the primary DRX group by a network indicator (DCI command, MAC activation / deactivation command, etc.) (or is implicitly activated based on a timer), the drx-InactivityTimer 406b of the secondary DRX group is started.

[0108] In some example embodiments, when all SCell 102z belonging to the S-DRX group are deactivated (either by means of an explicit indication of NW10 or via the SCell deactivation timer), the processor 320 of UE 106a stops the drx-onDurationTimer 402b and drx-inactivityTimer 406b associated with the S-DRX group.

[0109] In some example embodiments, NW 10 can configure UE 106a according to the various options described above (by sending instructions to processor 320 that will be stored in memory 340).

[0110] In an example embodiment, during the period when P-DRX group 102y has not yet switched to DRX, while S-DRX group 102z has switched to DRX, S-DRX group 102z can be activated by NW 10 using existing signaling (activation of at least one of drx-onDurationTimer 402b and drx-inactivityTimer 406b associated with S-DRX group) during data activity.

[0111] In the example embodiment, additional power savings can be achieved if the SCell 102z associated with the S-DRX group can remain in a dormant state for a period of time.

[0112] Example methods based on some example embodiments:

[0113] Figure 6 A power-saving method for a UE using multiple DRX groups in an example embodiment is shown. It should be understood that these steps are performed by the processor 320 of the UE 106a.

[0114] In one embodiment, as shown in step S500, the processor 320 of UE 106a communicates with the first group of cells. In the example embodiment, the first group of cells is... Figure 5 PCell and zero or more SCell 102y.

[0115] In one embodiment, as shown in step S502, the processor 320 of UE 106a receives a first indicator that notifies the UE to enable scheduling with at least one second group of cells. In an example embodiment, at least one second group of cells is Figure 5 The SCell 102z.

[0116] In one embodiment, as shown in step S504, the processor 320 of UE 106a initiates a first inactive timer 406b associated with at least one second group of cells 102z based on a first indicator (see [link]). Figure 5 ).

[0117] In one embodiment, as shown in step S506, the processor 320 of UE 106a schedules communication with at least one second group of cells 102z after the start of the first inactive timer 406b.

[0118] Although the terms first, second, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of this disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0119] When an element is described as "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there may be an intermediate element. Conversely, when an element is described as "directly connected" or "directly coupled" to another element, there is no intermediate element. Other words used to describe the relationship between elements should be interpreted in a similar way (e.g., "between" and "directly between", "adjacent to" and "directly adjacent to", etc.).

[0120] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and / or “including” as used herein specify the presence of the stated features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0121] It should also be noted that in some alternative implementations, the indicated functions / actions may not occur in the order shown in the diagram. For example, depending on the functions / actions involved, two diagrams shown consecutively may actually be executed substantially simultaneously or sometimes in reverse order.

[0122] Specific details are set forth in the following description to provide a thorough understanding of the exemplary embodiments. However, those skilled in the art will understand that the exemplary embodiments can be practiced without these specific details. For example, a system may be illustrated as a block diagram to avoid obscuring the exemplary embodiments due to unnecessary detail. In other instances, well-known processes, structures, and techniques may be shown without unnecessary detail to avoid obscuring the exemplary embodiments.

[0123] As discussed herein, illustrative embodiments will be described with reference to the actions and symbolic representations of operations (e.g., in the form of flowcharts, diagrams, data flow graphs, structural diagrams, block diagrams, etc.). These operations can be implemented as program modules, or functional processes including routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types, and can be implemented using existing hardware such as existing user equipment, base stations, evolved Node Bs (eNBs), remote radio heads (RRHs), 5G base stations (gNBs), femtocells, network controllers, computers, etc. Such existing hardware can be processing or control circuitry systems, such as, but not limited to, one or more processors, one or more central processing units (CPUs), one or more controllers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field-programmable gate arrays (FPGAs), one or more system-on-a-chip (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more application-specific integrated circuits (ASICs), or any one or more other devices capable of responding to and executing instructions in a defined manner.

[0124] Although flowcharts can describe operations as a sequential process, many operations can be executed in parallel, concurrently, or simultaneously. Furthermore, the order of operations can be rearranged. A process can terminate when its operations are completed, but it can also have other steps not included in the diagram. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, its termination can correspond to the function returning from its calling function or the main function.

[0125] As disclosed herein, the terms "storage medium," "computer-readable storage medium," or "non-transitory computer-readable storage medium" can refer to one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, disk storage media, optical storage media, flash memory devices, and / or other tangible machine-readable media for storing information. The term "computer-readable medium" can include, but is not limited to, portable or fixed storage devices, optical storage devices, and a variety of other media capable of storing, containing, or carrying instructions and / or data.

[0126] Furthermore, the example embodiments can be implemented using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, program code or code segments for performing the necessary tasks can be stored in a machine or computer-readable medium, such as a computer-readable storage medium. When implemented in software, one or more processors will perform the necessary tasks. For example, as described above, according to one or more example embodiments, at least one memory may include or store computer program code, and at least one memory and computer program code may be configured, together with at least one processor, to cause a network element or network device to perform the necessary tasks. Furthermore, the processor, memory, and example algorithms encoded as computer program code serve as components for providing or causing the execution of the operations discussed herein.

[0127] A code segment of computer program code can represent any combination of procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or instructions, data structures, or program statements. A code segment can be coupled to another code segment or hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., can be passed, forwarded, or transmitted via any suitable technology, including memory sharing, message passing, token passing, network transmission, etc.

[0128] As used herein, the terms “including” and / or “having” are defined as comprising (i.e., open language). As used herein, the term “coupling” is defined as a connection, but not necessarily direct or mechanical. Terms derived from “indicating” (e.g., “indicates” and “indication”) are intended to encompass all the various techniques that can be used to transmit or reference indicated objects / information. Some (but not all) examples of techniques that can be used to transmit or reference indicated objects / information include the transmission of indicated objects / information, the transmission of identifiers of indicated objects / information, the transmission of information used to generate indicated objects / information, the transmission of a part or portion of indicated objects / information, the transmission of some derivative of indicated objects / information, and the transmission of some symbol representing indicated objects / information.

[0129] According to the example embodiments, user equipment, base stations, eNBs, RRHs, gNBs, femtocells, network controllers, computers, etc., can be (or include) hardware, firmware, hardware-executed software, or any combination thereof. Such hardware may include processing or control circuitry systems, such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device capable of responding to and executing instructions in a defined manner.

[0130] The benefits, other advantages, and solutions to problems have been described above with respect to specific embodiments of this disclosure. However, the benefits, advantages, and solutions to problems, as well as any element(s) that may cause or lead to such benefits, advantages, or solutions, or cause such benefits, advantages, or solutions to become more apparent, shall not be construed as key, essential, or essential features or elements of any or all claims.

Claims

1. A method for communication, comprising: At least one processor of the user equipment (UE) communicates with the first group of cells; The at least one processor receives a first indicator, which notifies the UE to enable scheduling with at least one second group of cells; The at least one processor initiates a first inactive timer associated with the at least one second group of cells based on the first indicator; as well as The at least one processor schedules communication with the at least one second group of cells after the first inactivity timer is started. in The first group of cells is a primary discontinuous reception (P-DRX) cell group, and The at least one second group of cells is a secondary discontinuous reception S-DRX cell group; The P-DRX cell group uses a lower frequency range for transmission compared to the S-DRX cell group; The S-DRX group includes a first physical downlink control channel (PDCCH) monitoring scheme with a first repeated discontinuous reception DRX period, wherein the first repeated DRX period includes a first uplink traffic period or a first downlink traffic period and a first OnDuration period. The P-DRX group includes a second PDCCH monitoring scheme with a second repeated DRX period, wherein the second repeated DRX period includes a second uplink traffic period or a second downlink traffic period and a second OnDuration period. The first downlink service period and the first OnDuration period are shorter than the second downlink service period and the second OnDuration period, respectively. The first length of the first repeating DRX cycle is the same as the second length of the second repeating DRX cycle; as well as The first inactive timer is a DRX inactive timer used for discontinuous reception DRX cycles of the S-DRX cell group; The method further includes: Receive a second indicator, which indicates that at least one second group of cells is in a dormant state; as well as Based on the receipt of the second indicator, the first inactive timer and the DRX OnDuration timer are stopped.

2. The method according to claim 1, wherein the scheduling of the communication comprises: Activate one or more cells from the at least one second group of cells.

3. The method according to claim 1, wherein the scheduling of the communication comprises: Send a command to one or more cells in the at least one second group of cells to cause the one or more cells to switch from a dormant state to a non-dormant state.

4. The method according to claim 1, further comprising: Receive a second indicator, which indicates that at least one second group of cells is in a dormant state; as well as Based on the receipt of the second indicator, ensure that the DRX OnDuration timer is not started.

5. A device for communication, comprising: Components used for communicating with the first group of cells; A component for receiving a first indicator, the first indicator notifying the user equipment to enable scheduling with at least one second group of cells; A component for activating a first inactive timer associated with the at least one second group of cells based on the first indicator; as well as A component for scheduling communication with the at least one second group of cells after the start of the first inactive timer. in The first group of cells is a primary discontinuous reception (P-DRX) cell group, and The at least one second group of cells is a secondary discontinuous reception S-DRX cell group. The P-DRX cell group uses a lower frequency range for transmission compared to the S-DRX cell group; The S-DRX group includes a first physical downlink control channel (PDCCH) monitoring scheme with a first repeated discontinuous reception DRX period, wherein the first repeated DRX period includes a first uplink traffic period or a first downlink traffic period and a first OnDuration period. The P-DRX group includes a second PDCCH monitoring scheme with a second repeated DRX period, wherein the second repeated DRX period includes a second uplink traffic period or a second downlink traffic period and a second OnDuration period. The first downlink service period and the first OnDuration period are shorter than the second downlink service period and the second OnDuration period, respectively. The first length of the first repeating DRX cycle is the same as the second length of the second repeating DRX cycle; as well as The first inactive timer is a DRX inactive timer used for discontinuous reception DRX cycles of the S-DRX cell group; The device further includes: A component for receiving a second indicator, the second indicator indicating that the at least one second group of cells is in a dormant state; as well as A component for stopping the first inactive timer and the DRX OnDuration timer based on the receipt of the second indicator.

6. A user equipment, comprising: Memory, containing computer-readable instructions; as well as At least one processor is configured to read and execute the computer-readable instructions so that, Communicate with the first group of cells. Receive a first indicator, which notifies the user equipment to enable scheduling with at least one second group of cells. Based on the first indicator, a first inactive timer associated with the at least one second group of cells is started, and After the first inactive timer is started, communication with the at least one second group of cells is scheduled. in The first group of cells is a primary discontinuous reception (P-DRX) cell group, and The at least one second group of cells is a secondary discontinuous reception S-DRX cell group. The P-DRX cell group uses a lower frequency range for transmission compared to the S-DRX cell group; The S-DRX group includes a first physical downlink control channel (PDCCH) monitoring scheme with a first repeated discontinuous reception DRX period, wherein the first repeated DRX period includes a first uplink traffic period or a first downlink traffic period and a first OnDuration period. The P-DRX group includes a second PDCCH monitoring scheme with a second repeated DRX period, wherein the second repeated DRX period includes a second uplink traffic period or a second downlink traffic period and a second OnDuration period. The first downlink service period and the first OnDuration period are shorter than the second downlink service period and the second OnDuration period, respectively. as well as The first length of the first repeating DRX cycle is the same as the second length of the second repeating DRX cycle; Wherein the first inactive timer is a DRX inactive timer used for discontinuous reception DRX cycles of the S-DRX cell group; and The at least one processor is further configured to: Receive a second indicator, the second indicator indicating that at least one second group of cells is in a dormant state; and Based on the receipt of the second indicator, the first inactive timer and the DRX OnDuration timer are stopped.

7. The user equipment of claim 6, wherein the at least one processor is further configured to schedule the communication in such a manner as follows: Activate one or more cells from the at least one second group of cells.

8. The user equipment of claim 6, wherein the at least one processor is further configured to schedule the communication in the following manner: Send a command to one or more cells in the at least one second group of cells to cause the one or more cells to switch from a dormant state to a non-dormant state.

9. The user equipment of claim 6, wherein the at least one processor is further configured to: Receive a second indicator, the second indicator indicating that at least one second group of cells is in a dormant state, and Based on the receipt of the second indicator, ensure that the DRX OnDuration timer is not started.

Images