Carrier switching in drx with dcp
By introducing carrier switching mode and DCP-based DRX mode into terminal equipment, efficient scheduling of low-frequency carriers is achieved, solving the problems of spectrum congestion and increased energy consumption, improving communication accuracy and reducing the power consumption of terminal equipment.
Patent Information
- Application Number
- CN202610635528.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-09
- Publication Date
- 2026-11-10
AI Technical Summary
In existing technologies, the use of low-frequency carriers in urban and rural areas leads to spectrum congestion and increased energy consumption. Furthermore, low-to-low frequency carrier aggregation schemes present UE support challenges and are difficult to effectively reduce the power consumption of terminal devices.
By introducing carrier switching mode and DCP-based DRX mode, terminal devices switch between different carriers, perform control information monitoring and data communication on only one carrier, and use DCP to indicate the sleep or non-sleep state of the DRX cycle to achieve efficient carrier scheduling.
It improves communication accuracy, reduces power consumption of terminal devices, solves spectrum congestion and energy consumption problems of low-frequency carriers, and optimizes the implementation of low-low frequency carrier aggregation.
Smart Images

Figure CN123075685A_ABST
Abstract
Description
Cross-reference to related applications
[0001] This application claims priority and benefit to Indian Patent Application No. 202541045028, filed on May 9, 2025, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0002] Various example embodiments of this disclosure generally relate to the telecommunications field, and more specifically to carrier handover in discontinuous reception (DRX) with downlink control information (DCP) for power saving. Background Technology
[0003] In the field of wireless communication, with the increasing number of terminal devices and the growing demand for data transmission, improving communication efficiency and reducing device energy consumption have become challenges. DRX (also known as Connected Discontinuous Receive (C-DRX)) is an important energy-saving technology that allows terminal devices to enter a sleep state during periods when there is no data transmission demand, thereby avoiding continuous monitoring of downlink signals and effectively reducing power consumption. Summary of the Invention
[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receive first configuration information from a second apparatus, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; receive second configuration information from the second apparatus, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; monitor a DCP from the second apparatus on a first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; and, based on the carrier switching mode, perform control information monitoring on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0005] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: transmit first configuration information to a first apparatus, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; transmit second configuration information to the first apparatus, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; transmit a DCP to the first apparatus on the first carrier based on the at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; and, based on the carrier switching mode, perform control information transmission on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the transmitted DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0006] In a third aspect of this disclosure, a method is provided. The method includes: receiving first configuration information from a second device, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; receiving second configuration information from the second device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; monitoring a DCP from the second device on the first carrier based on the at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; and, based on the carrier switching mode, performing control information monitoring on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: transmitting first configuration information to a first device, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; transmitting second configuration information to the first device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; transmitting a DCP to the first device on the first carrier based on the at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; and, based on the carrier switching mode, performing control information transmission on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the transmitted DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0008] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: means for receiving first configuration information from a second apparatus, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; means for receiving second configuration information from the second apparatus, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DRX mode based on DCP indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; means for monitoring a DCP from the second apparatus on a first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; and means for performing control information monitoring on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, based on the carrier switching mode, according to the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0009] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: means for transmitting first configuration information to a first apparatus, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; means for transmitting second configuration information to the first apparatus, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DRX mode based on DCP indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; means for transmitting a DCP to the first apparatus on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; and means for performing control information transmission on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, based on the carrier switching mode, according to the transmission of the DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0010] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to a third aspect.
[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the fourth aspect.
[0012] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0013] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 A schematic diagram illustrating the application of different carriers based on different distances from the cell center is shown; Figures 3A-3C A schematic diagram illustrating the application of different carriers based on different distances from the cell center is shown; Figure 4 An example scenario of switching between carriers is shown; Figure 5-6 Some frequency band combinations applicable to low-low frequency band CA are shown; Figure 7 A schematic diagram of an example DRX process is shown; Figure 8 A schematic diagram of PDCCH timing during the DRX on-time is shown; Figure 9 A schematic diagram of scheduling during the DRX enable duration is shown; and Figure 10 A schematic diagram of per-carrier component (per-CC) scheduling is shown; Figure 11 A schematic diagram of cross-carrier scheduling is shown; Figure 12 An example DRX mode with DCP is shown; Figure 13 An example downlink control information (DCI) format is shown; Figure 14 The signaling flow for an example procedure for carrier handover in DCP-based DRX is shown according to some example embodiments of the present disclosure; Figure 15 A schematic diagram of LBCA switching mode using DCP-based DRX is shown; Figure 16 Example signaling flows for carrier handover in DCP-based DRX are shown according to some example embodiments of this disclosure; Figure 17 The signaling flow for an example procedure for carrier switching in DRX according to some other example embodiments of this disclosure is shown; Figure 18 A schematic diagram illustrating example DRX mode and LBCA switching mode according to some example embodiments of the present disclosure is shown; Figure 19 The signaling flow for carrier switching in a DRX with DCP according to some example embodiments of this disclosure is shown; Figure 20 A schematic diagram illustrating example DRX mode and LBCA switching mode according to some other example embodiments of the present disclosure is shown; Figure 21 The signaling flow for carrier switching in a DRX with DCP according to some example embodiments of this disclosure is shown; Figure 22 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 23 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 24 A flowchart is shown of a method implemented at a first device according to some other exemplary embodiments of the present disclosure; Figure 25A flowchart is shown illustrating a method implemented at a second device according to some other exemplary embodiments of the present disclosure; Figure 26 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 27 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.
[0014] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0015] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.
[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0017] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments, whether explicitly described or not, to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.
[0018] It should be understood that although terms such as "first," "second," etc., preceding nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0019] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.
[0020] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.
[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. 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, when used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0022] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementations in analog, digital, and / or quantum circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog, digital, and / or quantum hardware circuitry with software / firmware, and (ii) Any or all portions of a hardware processor (including digital and / or quantum signal processors(s) with software), and memory that works together to enable devices such as mobile devices, computing devices, or servers to perform various functions, and (c) Any or all parts of the hardware circuitry, such as microprocessors, processors and / or quantum processors, that require software (e.g., firmware) to operate, but which may not exist when no software is required to operate.
[0023] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers implementations of hardware circuitry or processors (or processors in general) and their accompanying software and / or firmware. The term "circuit" also covers, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0024] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. The scope of this disclosure should not be construed as limited to the aforementioned systems.
[0025] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header End (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN) or non-terrestrial network device (such as a satellite network device), a low Earth orbit (LEO) satellite and a geostationary Earth orbit (GEO) satellite, a spacecraft network device, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves as a UE toward the parent node, and the DU portion of the IAB node behaves as a base station toward the next-hop IAB node.
[0026] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal equipment may also correspond to the mobile termination (MT) portion of a WAB node or IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.
[0027] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.
[0028] Figure 1 A schematic diagram of an example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. In the communication environment 100, multiple communication devices, including terminal device 110 and network device 120, can communicate with each other.
[0029] exist Figure 1In the example, terminal device 110 may be a UE, and network device 120 may be a base station serving that UE. The service area of network device 120 may be referred to as a cell. A cell may include PCell 102-1 and SCell 102-2. It should be understood that although one SCell is provided, more than one SCell may exist associated with one PCell. Network device 120 operates in a radio access network (RAN) and is therefore also referred to as a RAN network device.
[0030] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in PCell 102-1 and SCell 102-2, and one or more additional cells may be deployed in communication environment 100. Note that although shown as a network device, network device 120 may be another device besides a network device. Although illustrated as a terminal device, terminal device 110 may be another device besides a terminal device.
[0031] In the following description, for illustrative purposes, some example embodiments are described in which terminal device 110 operates as a UE and network device 120 operates as a base station (e.g., gNB). However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other devices, and the operations described in connection with the network device can be implemented at the terminal device or other devices.
[0032] In some example embodiments, the communication direction from network device 120 to terminal device 110 is referred to as DL, while the communication direction from terminal device 110 to network device 120 is referred to as UL. In DL, network device 120 is a transmitting (TX) device (or transmitter), and terminal device 110 is a receiving (RX) device (or receiver). In UL, terminal device 110 is a TX device (or transmitter), and network device 120 is an RX device (or receiver).
[0033] Communication in communication environment 100 can be implemented according to 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), fifth-generation (5G), and sixth-generation (6G), wireless local network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can 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 Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.
[0034] Low-frequency (LB) carriers typically refer to carriers with relatively low frequencies used to carry communication signals. LB carriers emit electromagnetic waves at 1 GHz. Their long wavelength and low propagation loss allow signals to travel long distances. This makes them advantageous for long-distance communication, such as in rural areas. Additionally, LB carriers penetrate buildings relatively well, making them suitable for scenarios where signals need to overcome obstacles, such as indoor communication in urban areas.
[0035] Mid-band (MB) carriers, high-band (HB) carriers, and ultra-high-band (UHB) carriers also have corresponding advantages in specific scenarios, most often providing higher channel bandwidth. Figure 2 and Figures 3A-3C A schematic diagram illustrating the application of different carriers based on different distances from the cell center is shown. For example... Figure 2 As shown, MB carriers are more useful near base stations, while LB carriers are more useful in areas far from base stations and are used for indoor communication in urban areas. Figure 3A As shown, in the near field, the LB, MB, and HB carriers have approximately the same activity level, and the UHB carrier is also active. Figure 3B As shown, in the transition region, the LB, MB, and HB carriers are also active. However, as Figure 3C As shown, in the far field, almost only the LB carrier is active.
[0036] Operators typically hold 10 to 20 times more mid-band spectrum than low-band spectrum. Therefore, in both urban (indoor) and rural areas, load balancers (LBs) carry a large volume of traffic, leading to low-band congestion and severely degrading customer experience.
[0037] Low-low band carrier aggregation (CA) could be one way to address this issue, but no such solution exists because original equipment manufacturers (OEMs) face challenges in supporting it. While low-band supplemental downlink (SDL) bands cover most poorly covered areas, the problem of supporting all low-band combinations (some of which even overlap) makes the use of existing CA problematic.
[0038] To address this, a solution has been proposed. This solution enables the utilization of SDL via a low-low band CA method with minimal impact on the UE. In this solution, the UE switches its configuration between two states of the radio frequency (RF) front-end (defined as Case 1 and Case 2). In Case 1, one-way transmission (Tx) and two-way reception (Rx) operations are performed on the FDD carrier, while there is no transmission or reception on the SDL carrier. In Case 2, two-way reception operations are performed on the SDL carrier, and there is no transmission or reception on the FDD carrier.
[0039] The following will refer to Figure 4 Further describe the switching between the two carriers. For example... Figure 4 As shown, the UE's transceiver switches between the FDD and SDL bands according to the Transmission Time Interval (TTI). In TTI N1, the transceiver performs transmission and reception on the FDD band. In TTI N2, the transceiver switches to perform reception on the SDL band. There is no UL transmission on the SDL band. After the SDL-scheduled receive interval is completed, the transceiver switches back to the FDD duplexer to perform transmission and reception in TTI N3.
[0040] To implement this solution, several requirements are imposed on the UE. The UE needs to support inter-carrier scheduling. It monitors the FDD downlink (DL), Physical Downlink Control Channel (PDCCH), and Downlink Control Information (DCI), which includes both FDD and SDL scheduling. The UE needs to support TTI-level handover. When an SCell is scheduled, the UE needs to switch to the SCell filter. During the scheduling period, there should be no simultaneous Tx / Rx between the PCell and SCell.
[0041] Figures 5 to 6Some band combinations applicable to low-low frequency CA are shown. For CA_n12A-n29A, note that in some regions, there is no existing narrowband service in the bandgap between n29 and n12 DL (728-729 MHz). For CA_n28A-n67A, in some regions, the spectrum of band n28 is limited to 703-733 MHz UL and 758-788 MHz DL. And assuming a full-band duplexer architecture, requirements will be introduced for band n28. CA_n5A-n29A has been specified. The fractional bandwidth of a single antenna supporting this combination represents a practical implementation challenge. CA_n29A-n71A is also specified. The fractional bandwidth of a single antenna supporting this combination is 16.5%, and represents a practical implementation challenge.
[0042] As mentioned above, DRX allows terminal devices to enter a sleep state during periods when there is no data transmission demand, thereby avoiding continuous monitoring of downlink signals and effectively reducing power consumption.
[0043] Figure 7 A schematic diagram of an example DRX process is shown. (For example...) Figure 7 As shown, the UE can monitor the PDCCH during the on-duration period within each long DRX cycle. The on-duration period may include one or more PDCCH opportunities for PDCCH reception. If the UE is scheduled during the on-duration period, an inactivity timer can be started. During the inactivity timer's operation, the UE can continue monitoring the PDCCH. If the UE is rescheduled during the inactivity timer's operation, the inactivity timer can be restarted.
[0044] If a UE is configured with both short and long DRX periods, and if the UE has already been scheduled during the on-duration of a long DRX period, the UE can also monitor the on-duration defined by the on-duration of the short DRX period. For each long DRX period, multiple short DRX periods can be defined, and the number of periods is part of the configuration.
[0045] Figure 8 The diagram illustrates the PDCCH timing during the DRX enable duration. The PDCCH may carry control information from the network (e.g., DCI), which may or may not schedule downlink and potential uplink data scheduling for the UE.
[0046] Figure 9The diagram illustrates the scheduling during the DRX enabled duration. Scheduling can be indicated by PDCCH reception during the DRX enabled duration. This scheduling means the UE can start a DRX inactivity timer, during which the UE can also monitor the PDCCH. Scheduling may include downlink scheduled PDSCH data and potentially uplink scheduled PUSCH data, or uplink acknowledgment or negative acknowledgment (ACK / NACK) during the inactivity timer's operation.
[0047] In some cases, when more than one carrier is configured, dynamic scheduling between different carriers can be implemented in different ways, such as... Figure 10 and Figure 11 As shown. Figure 10 A schematic diagram of per-carrier component (per-CC) scheduling is shown, in which each carrier (e.g., CC1 or CC2) can be configured with a PDCCH timing and can be scheduled individually by monitoring DCI during the PDCCH timing. Figure 11 A schematic diagram of cross-carrier scheduling is shown, where the DCI in CC1 can schedule PDSCH data in both CC1 and CC2. The PCell can always be scheduled on its own channel via the PDCCH. Therefore, if one of the LBCA carriers is a PCell carrier, then the PCell carrier can carry the PDCCH. In the case of cross-carrier scheduling, only one LBCA carrier may need to carry the PDCCH, and if there are more carriers besides this pair of LBCA carriers, the PDCCH could very well be located outside of this pair of LBCA carriers.
[0048] In communication systems, an advanced signal is called Downlink Control Information (DCP) for power saving. Energy-critical equipment can save more energy by shutting down the receiver module for an extended period based on DCP instructions from a next-generation base station (gNB). However, potential failure of DCP can lead to additional power consumption or packet loss. To address this issue, it allows the gNB to configure default behavior when DCP is not detected.
[0049] The UE receives the DCP only when it is in sleep mode. The DCP is scrambled with a power-saving radio network temporary identifier (ps-RNTI) and uses DCI format 2_6. Possible DCP locations are indicated by the search space and control resource set.
[0050] Because the power used for DCP reception is relatively low, the UE can save energy by skipping the entire DRX cycle.
[0051] In each DRX cycle, there is at least one DCP monitoring instance (or timing), which is a pre-configured resource for DCP transmission. At the DCP instance, if the UE is in sleep mode, the gNB transmits the DCP to the UE; otherwise, it does not transmit the DCP.
[0052] DCPs are configured to fall into a "sleep" period. After the first DCP transmitted in a DRX cycle, the gNB can transmit several other DCPs thereafter (at pre-configured times) to ensure reliability.
[0053] After the UE enters sleep mode, it continues to blindly decode the DCP at the qualified DCP instance until the DCP is successfully decoded. After a successful DCP reception, it skips the remaining DCP instances because all DCPs carry the same indication. Figure 12 An example DRX mode with DCP is shown. As shown, at the beginning of cycle 1, sleep begins, and the UE can only wake up during cycle 1 and cycle 2 to monitor DCP.
[0054] In such Figure 12 During some cycles of cycle 3, the UE can remain active until the last DCP instance and no qualified DCP instance is available. In this case, the start of the next DRX cycle's on-time duration will be the active period.
[0055] The communication specification has defined the SCell Sleep and Sleep Bandwidth Part (BWP) features to help save power.
[0056] DCI format DCI_2_6 in Figure 13 As shown, it can indicate the sleep time of one or more UEs' SCell groups outside of their DRX activity time. The structure of DCI_2_6 scrambled using PS-RNTI is as follows.
[0057] The following table provides the definitions of wake-up indicators and SCell sleep indicators in DCP.
[0058]
[0059] If the higher-level parameter dormancyGroupWithinActiveTime is not configured, the SCell sleep indicator in the DCI formats DCI_1_1 and DCI_1_0 may include 0 bits. Otherwise, the SCell sleep indicator may include a bitmap of 1, 2, 3, 4, or 5 bits, determined by the number of different DormancyGroupIDs provided by the higher-level parameter dormancyGroupWithinActiveTime, where each bit corresponds to one of the SCell groups configured by the higher-level parameter dormancyGroupWithinActiveTime, and the MSB to LSB of the bitmap corresponds to the first to last SCell groups in ascending order of DormancyGroupID. This format exists only if it is carried by the PDCCH on the primary cell during DRX activity time and the UE is configured with at least two DL BWPs for the SCell.
[0060] In some cases, UE capability information can indicate support for DCP-based wake-up. As mentioned above, the gNB can configure DCP parameters to the UE based on the aforementioned UE capability information. Currently, it is proposed to define a handover mode between two carriers (e.g., two LB carriers). In this scenario, the UE can only activate one carrier at a time, including receiving and / or transmitting data and performing measurements.
[0061] During C-DRX, there are many defined time periods, on-time durations, DRX-activity timers, DRX off times, etc. Furthermore, for C-DRX, there is typically a DRX mode for each carrier.
[0062] With the introduction of DCP over DRX, a DCP signal and a new low-power wake-up signal LP-WUS were introduced. DCP is designed to be received only on PCC, indicating to the UE which carriers it should wake up for and monitoring the on-time duration / PDCCH.
[0063] It is intended to determine when LBCA switching mode can be used during DCP-based DRX, and if enabled / disabled, when LBCA switching mode can be started compared to the defined DCP and DRX cycles.
[0064] According to example embodiments of this disclosure, a solution is proposed for configuring a carrier switching mode and a DCP-based DRX mode for a terminal device (e.g., a UE). The carrier switching mode indicates a switch between the activation of a first carrier and a second carrier. The DRX mode indicates at least the on-time duration of a DRX cycle and at least one DCP monitoring opportunity. The on-time duration of the DRX cycle is aligned with the carrier scheduling modes of the two carriers. Based on the carrier switching mode and the DCP-based DRX mode, the terminal device performs DCP monitoring and control information monitoring on the correct carrier during the active time of the DRX cycle, and then performs data communication with network devices (e.g., a gNB) on the correct carrier.
[0065] Using the solutions in the example embodiments of this disclosure, the carrier pair is special in the sense that only one carrier can be scheduled at a time. Therefore, from the perspective of DRX, the LBCA carrier set can be considered a single carrier. By doing so, regardless of the given DRX configuration, the on-time duration can be maintained on the correct carrier by simply following the LBCA switching pattern on the two carriers. This allows terminal devices and network devices to switch to the correct carrier during different periods of the DRX cycle. Terminal devices and network devices can determine when and on which carrier to monitor / transmit DCP, control information, and subsequently schedule downlink and / or uplink (e.g., PDSCH / PUSCH) transmissions. Therefore, communication accuracy can be improved, and power consumption of terminal devices can be reduced.
[0066] Some example signaling flows between terminal devices and network devices will now be described. In the following description, although operations are depicted in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or sequentially, or to perform all shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific embodiment details are contained in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0067] Figure 14 Signaling flow 1400 is shown as an example procedure for carrier handover in DCP-based DRX according to some example embodiments of this disclosure. For example... Figure 14 As shown, signaling flow 1400 involves terminal device 110 and network device 120. For discussion purposes, reference will be made to... Figure 1 Discuss signaling flow 1400.
[0068] like Figure 14 As shown, network device 120 transmits (1405) first configuration information to terminal device 110. The first configuration information may indicate a carrier switching mode that switches between the activation of a first carrier and the activation of a second carrier. In an example embodiment of this disclosure, the first carrier may be referred to as carrier component 1 (CC1), and the second carrier may be referred to as carrier component 2 (CC2). In some examples, the carrier switching mode may include a mode bitmap, where each bit corresponds to a time slot or a subframe. Bits corresponding to a time slot or subframe may have a value of 0 to indicate that the first carrier is active during the corresponding time slot or subframe, and a value of 1 to indicate that the second carrier is active.
[0069] In some example embodiments, terminal device 110 may report its carrier switching capability to network device 120. For example... Figure 14 As shown, terminal device 110 can transmit (1402) capability information to network device 120, the capability information indicating whether terminal device 110 is capable of carrier switching. Network device 120 can receive (1404) capability information. If the capability information indicates that terminal device 110 is capable of carrier switching, then network device 120 can transmit (1405) first configuration information indicating the carrier switching mode to terminal device 110.
[0070] In some example embodiments, the first carrier and the second carrier can be LB carriers. Therefore, the carrier switching mode can be referred to as LBCA switching mode.
[0071] In some example embodiments, the first carrier can be an FDD carrier, and the second carrier can be an SDL carrier. The FDD carrier can support both UL and DL data transmission in separate frequency bands. The SDL carrier can support only DL transmission.
[0072] In some example embodiments, a first carrier may be associated with a PCell of network device 120, and a second carrier may be associated with an SCell of network device 120. For example, the first carrier may be an FDD carrier and associated with PCell 102-1. The second carrier may be an SDL carrier and associated with SCell 102-2. Since SDL does not have UL capability, it may not typically be configured as a PCell carrier.
[0073] It should be understood that the types and characteristics of the first and second carriers are for illustrative purposes only and do not imply any limitations. The first and second carriers may also be other possible carriers.
[0074] continue Figure 14Terminal device 110 receives (1410) first configuration information from network device 120. Based on the carrier switching mode indicated by the first configuration information, terminal device 110 can determine which carrier to switch to during a specific time period.
[0075] In addition to carrier switching modes, network device 120 can also configure terminal device 110 with DCP-based DRX mode or DCP-based C-DRX mode. For example... Figure 12 As shown, network device 120 transmits (1415) second configuration information to terminal device 110. The second configuration information may indicate a DCP-based DRX mode. The DCP-based DRX mode may at least indicate the duration of the DRX cycle and at least one DCP monitoring event. Terminal device 110 receives (1420) the second configuration information from network device 120. Based on the DCP-based DRX mode indicated by the second configuration information, terminal device 110 can determine when to monitor DCP from network device 120 and when to perform control information monitoring.
[0076] Based on carrier switching mode and DCP-based DRX mode, terminal device 110 and network device 120 can determine when and in which carrier to monitor / transmit DCP and control information, and subsequently schedule UL / DL data transmission.
[0077] like Figure 14 As shown, network device 120 transmits (1430) a DCP to terminal device 110 on a first carrier based on at least one DCP monitoring opportunity. The DCP can indicate whether the first on-duration of the first DRX cycle after the transmission of the DCP is sleep or non-sleep. That is, the DCP can indicate whether terminal device 110 monitors control information during the subsequent on-duration period. The DCP can be transmitted only when terminal device 110 is sleep. The DCP can always be transmitted on the first carrier (e.g., an FDD carrier).
[0078] Terminal device 110 monitors (1425) the DCP from network device 120 on the first carrier based on at least one DCP monitoring opportunity. Terminal device 110 may monitor the DCP only when it is in sleep mode (e.g., during DRX shutdown). DCP monitoring is always performed on the first carrier. That is, terminal device 110 may not need to switch between the first and second carriers to perform DCP monitoring.
[0079] If terminal device 110 receives a DCP and the received DCP indicates that the first on duration of the first DRX cycle is non-dormant, then terminal device 110 performs (1435) control information monitoring on at least one of the first carrier or the second carrier during the first on duration of the first DRX cycle. Network device 120 performs (1440) control information transmission on at least one of the first carrier or the second carrier during the on duration of the DRX cycle, based on the carrier switching mode and the DRX mode. The carrier to be activated for control information monitoring and transmission can be determined based on the carrier switching mode.
[0080] In some example embodiments, although the DCP is always transmitted on the first carrier, the associated on-duration is aligned with the carrier scheduling patterns of the two carriers. In the case of a non-sleep-on-duration scenario, the DCI and PDCCH can be received on the correct active carrier by simply following the LBCA switching pattern on both carriers.
[0081] Terminal device 110 can determine, based on the carrier switching mode, whether the first carrier or the second carrier is active during the first on-duration of the first DRX cycle. Based on this determination, terminal device 110 can perform control information monitoring on the active carrier during the first on-duration of the first DRX cycle. For example, if the first carrier is active during the first on-duration, terminal device 110 can monitor control information on the first carrier. Otherwise, if the second carrier is active during the first on-duration, terminal device 110 can monitor control information on the second carrier. In some cases, if carrier switching between the two carriers is configured by the carrier switching mode during the first on-duration, terminal device 110 can switch between the first carrier and the second carrier for control information monitoring.
[0082] Therefore, on the network side, network device 120 can also determine whether the first carrier or the second carrier is active during the first on-duration period of the first DRX cycle based on the carrier switching mode. Based on this determination, and if data needs to be scheduled to terminal device 110, network device 120 can transmit control information on the active carrier during the first on-duration period.
[0083] In some example embodiments, the DCP-based DRX mode can also indicate the active time of the DRX cycle. If there is data to be scheduled for terminal device 110, network device 120 can perform (1450) data communication with terminal device 110 on at least one of the first carrier or the second carrier based on a carrier switching mode during the active time of the first DRX cycle. Therefore, based on the received control information, terminal device 110 can perform (1445) data communication with network device 120 on at least one of the first carrier or the second carrier based on a carrier switching mode during the active time of the first DRX cycle.
[0084] In some example embodiments, network device 120 and terminal device 110 can determine whether a first carrier or a second carrier is active during the active period of a first DRX cycle based on the carrier switching mode. Based on this determination, network device 120 and terminal device 110 can perform data communication with each other on the active carrier during the active period of the first DRX cycle. If the FDD carrier is active, UL and DL data transmission can be scheduled. If the SDL carrier is active, only DL data transmission can be scheduled.
[0085] In some example embodiments, if one of the first and second carriers is active at the start of the active period of the first DRX cycle, network device 120 may perform data communication with terminal device 110 on the active carrier from the start of the active period. In some example embodiments, based on a carrier switching mode, network device 120 may switch from an active carrier to another carrier among the first and second carriers during the active period of the first DRX cycle, and perform data communication with terminal device 110 on the other active carrier during the active period of the first DRX cycle. The switching between the first and second carriers may occur in multiple rounds during the active period of the first DRX cycle.
[0086] Therefore, in some example embodiments, if one of the first carrier and the second carrier is active at the start of the active time of the first DRX cycle, the terminal device 110 can perform data communication with the network device 120 on the active carrier from the start of the active time. In some example embodiments, based on a carrier switching mode, the terminal device 110 can switch from the active carrier to the other carrier of the first carrier and the second carrier during the active time of the first DRX cycle, and perform data communication with the network device 120 on the other active carrier during the active time of the first DRX cycle. Multiple rounds of switching between the first carrier and the second carrier can occur during the active time of the first DRX cycle.
[0087] In some example embodiments, if no DCP is transmitted, or if the transmitted DCP indicates that the first on-duration of the first DRX cycle is dormant, network device 120 may skip control information transmission during the first on-duration of the first DRX cycle. Therefore, if terminal device 110 does not receive a DCP from network device 120, or if the received DCP indicates that the first on-duration of the first DRX cycle is dormant, terminal device 120 may skip control information monitoring during the first on-duration of the first DRX cycle. If the DCP does not indicate non-dormant for that carrier pair, terminal device 110 may need to switch to the first carrier for the cancelled on-duration. Terminal device 120 may then monitor for a DCP from network device 120 on the first carrier during a second DRX cycle following the first DRX cycle, based on at least one DCP monitoring opportunity.
[0088] Figure 15 A schematic diagram of LBCA switching modes with DRX based on DCP is shown. For example... Figure 15 As shown, the DCP-based DRX mode 1301 can indicate at least one on-time duration with a PDCCH timing and at least one DCP monitoring timing. Terminal device 110 can monitor DCP at at least one DCP monitoring timing and monitor DCI from network device 120 at a PDCCH timing. The LBCA handover mode 1302 can indicate an active handover between CC1 and CC2. The LBCA handover mode with DCP-based DRX can combine these two modes.
[0089] like Figure 15 As shown, in one example, if terminal device 110 receives DCP 1504, terminal device 110 can activate LBCA handover mode. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active and monitor DCI during the subsequent on-time duration on CC2. If DCI 1505 is received, terminal device 110 can perform data communication with network device 120 during the active time of the same DRX cycle. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active during the active time and perform data communication with network device 120 on CC2.
[0090] In another example, if terminal device 110 receives DCP 1506, terminal device 110 can activate LBCA handover mode. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active and monitor DCI during the subsequent on-time duration on CC2. If DCI 1507 is received, terminal device 110 can perform data communication with network device 120 during the active time of the same DRX cycle. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active during the active time and perform data communication with network device 120 on CC2. If terminal device 110 determines to switch from CC2 to CC1 based on LBCA handover mode, it can continue to perform data communication with network device 120 on CC1. Multiple handovers can occur between CC1 and CC2 before the active time of the DRX cycle expires. When terminal device 110 is active, terminal device 110 may not monitor DCP 1508 during the DCP monitoring period.
[0091] Figure 16 Example signaling stream 1600 for carrier handover in DCP-based DRX is shown according to some example embodiments of this disclosure. Signaling stream 1600 can be considered as Figure 14 Example of signaling flow 1400. Signaling flow 1600 may involve terminal device 110 and network device 120. Figure 16 In the example, it is assumed that the first carrier is an FDD carrier (also known as a PCell carrier) associated with PCell 102-1, and the second carrier is an SDL carrier (also known as a SCell carrier) associated with SCell 102-2. It would be appropriate for the two carriers involved in the carrier switching mode to include other types of carriers.
[0092] like Figure 16 As shown, at 1601, terminal device 110 can indicate its capabilities related to LBCA handover, i.e., the aforementioned capability information. At 1602, network device 120 can transmit first configuration information to terminal device 110 to configure terminal device 110 using an LBCA handover mode (e.g., '001110…'). "0" can represent a time slot on the PCell carrier, and "1" can represent a time slot on the SCell carrier.
[0093] At 1603, network device 120 can transmit second configuration information to terminal device 110 and configure terminal device 110 using a DCP-based DRX mode. The DCP-based DRX mode can at least indicate the duration of the DRX cycle, and the duration of the cycle can follow the LBCA handover mode.
[0094] At 1604, terminal device 110 and network device 120 can remain on the PCell carrier when the time slot falls into the DRX off period.
[0095] At 1605, terminal device 110 and network device 120 can remain on the PCell carrier. Network device 120 can transmit a DCP to terminal device 110, which indicates that the subsequent on duration is dormant. At 1606, the PDCCH timing during the on duration can be cancelled. At 1607, terminal device 110 and network device 120 can remain on the PCell carrier. At 1608, since network device 120 has not transmitted a DCI for PDSCH scheduling, terminal device 110 can move to DRX off. At 1609, the DRX cycle can end according to the DCP-based DRX mode.
[0096] At 1610, network device 120 can transmit a DCP to the terminal device to indicate the duration of non-sleep on. Subsequently, a handover between the PCell carrier and the SCell carrier will be triggered at 1611.
[0097] At 1612, based on the carrier switching mode, the PDCCH timing can be on the SCell carrier during the open duration. At 1613, network device 120 can use DCI to schedule PDSCH data transmission on the SCell carrier. At 1614, the open duration can expire. At 1615, network device 120 can perform data communication with terminal device 110 on the SCell carrier. At 1616, terminal device 110 and network device 120 can switch from the SCell carrier to the PCell carrier.
[0098] At 1617, network device 120 can perform data communication with terminal device 110 on the PCell carrier until the activity time expires at 1618. At 1619, terminal device 110 and network device 120 can remain on the PCell carrier. At 1620, the DRX cycle can end.
[0099] Then, at 1621, network device 120 can transmit a DCP indicating the duration of sleep on start to terminal device 110. At 1622, terminal device 110 can stop monitoring DCI during PDCCH timing. At 1623, terminal device 110 and network device 120 can remain in PCell based on carrier switching mode.
[0100] Figure 14 Signaling flow 1400 is shown as an example procedure for carrier handover in DCP-based DRX according to some example embodiments of this disclosure. For example... Figure 14As shown, signaling flow 1400 involves terminal device 110 and network device 120. For discussion purposes, reference will be made to... Figure 1 Discuss signaling flow 1400.
[0101] like Figure 14 As shown, network device 120 transmits (1405) first configuration information to terminal device 110. The first configuration information may indicate a carrier switching mode that switches between the activation of a first carrier and the activation of a second carrier. In an example embodiment of this disclosure, the first carrier may be referred to as carrier component 1 (CC1), and the second carrier may be referred to as carrier component 2 (CC2). In some examples, the carrier switching mode may include a mode bitmap, where each bit corresponds to a time slot or a subframe. Bits corresponding to a time slot or subframe may have a value of 0 to indicate that the first carrier is active during the corresponding time slot or subframe, and a value of 1 to indicate that the second carrier is active.
[0102] In some example embodiments, terminal device 110 may report its carrier switching capability to network device 120. For example... Figure 14 As shown, terminal device 110 can transmit (1402) capability information to network device 120, the capability information indicating whether terminal device 110 is capable of carrier switching. Network device 120 can receive (1404) capability information. If the capability information indicates that terminal device 110 is capable of carrier switching, then network device 120 can transmit (1405) first configuration information indicating the carrier switching mode to terminal device 110.
[0103] In some example embodiments, the first carrier and the second carrier can be LB carriers. Therefore, the carrier switching mode can be referred to as LBCA switching mode.
[0104] In some example embodiments, the first carrier can be an FDD carrier, and the second carrier can be an SDL carrier. The FDD carrier can support both UL and DL data transmission in separate frequency bands. The SDL carrier can support only DL transmission.
[0105] In some example embodiments, a first carrier may be associated with a PCell of network device 120, and a second carrier may be associated with an SCell of network device 120. For example, the first carrier may be an FDD carrier and associated with PCell 102-1. The second carrier may be an SDL carrier and associated with SCell 102-2. Since SDL does not have UL capability, it may not typically be configured as a PCell carrier.
[0106] It should be understood that the types and characteristics of the first and second carriers are for illustrative purposes only and do not imply any limitations. The first and second carriers may also be other possible carriers.
[0107] continue Figure 14 Terminal device 110 receives (1410) first configuration information from network device 120. Based on the carrier switching mode indicated by the first configuration information, terminal device 110 can determine which carrier to switch to during a specific time period.
[0108] In addition to carrier switching modes, network device 120 can also configure terminal device 110 with DCP-based DRX mode or DCP-based C-DRX mode. For example... Figure 12 As shown, network device 120 transmits (1415) second configuration information to terminal device 110. The second configuration information may indicate a DCP-based DRX mode. The DCP-based DRX mode may at least indicate the duration of the DRX cycle and at least one DCP monitoring event. Terminal device 110 receives (1420) the second configuration information from network device 120. Based on the DCP-based DRX mode indicated by the second configuration information, terminal device 110 can determine when to monitor DCP from network device 120 and when to perform control information monitoring.
[0109] Based on carrier switching mode and DCP-based DRX mode, terminal device 110 and network device 120 can determine when and in which carrier to monitor / transmit DCP and control information, and subsequently schedule UL / DL data transmission.
[0110] like Figure 14 As shown, network device 120 transmits (1430) a DCP to terminal device 110 on a first carrier based on at least one DCP monitoring opportunity. The DCP can indicate whether the first on-duration of the first DRX cycle after the transmission of the DCP is sleep or non-sleep. That is, the DCP can indicate whether terminal device 110 monitors control information during the subsequent on-duration period. The DCP can be transmitted only when terminal device 110 is sleep. The DCP can always be transmitted on the first carrier (e.g., an FDD carrier).
[0111] Terminal device 110 monitors (1425) the DCP from network device 120 on the first carrier based on at least one DCP monitoring opportunity. Terminal device 110 may monitor the DCP only when it is in sleep mode (e.g., during DRX shutdown). DCP monitoring is always performed on the first carrier. That is, terminal device 110 may not need to switch between the first and second carriers to perform DCP monitoring.
[0112] If terminal device 110 receives a DCP and the received DCP indicates that the first on duration of the first DRX cycle is non-dormant, then terminal device 110 performs (1435) control information monitoring on at least one of the first carrier or the second carrier during the first on duration of the first DRX cycle. Network device 120 performs (1440) control information transmission on at least one of the first carrier or the second carrier during the on duration of the DRX cycle, based on the carrier switching mode and the DRX mode. The carrier to be activated for control information monitoring and transmission can be determined based on the carrier switching mode.
[0113] In some example embodiments, although the DCP is always transmitted on the first carrier, the associated on-duration is aligned with the carrier scheduling patterns of the two carriers. In the case of a non-sleep-on-duration scenario, the DCI and PDCCH can be received on the correct active carrier by simply following the LBCA switching pattern on both carriers.
[0114] Terminal device 110 can determine, based on the carrier switching mode, whether the first carrier or the second carrier is active during the first on-duration of the first DRX cycle. Based on this determination, terminal device 110 can perform control information monitoring on the active carrier during the first on-duration of the first DRX cycle. For example, if the first carrier is active during the first on-duration, terminal device 110 can monitor control information on the first carrier. Otherwise, if the second carrier is active during the first on-duration, terminal device 110 can monitor control information on the second carrier. In some cases, if carrier switching between the two carriers is configured by the carrier switching mode during the first on-duration, terminal device 110 can switch between the first carrier and the second carrier for control information monitoring.
[0115] Therefore, on the network side, network device 120 can also determine whether the first carrier or the second carrier is active during the first on-duration period of the first DRX cycle based on the carrier switching mode. Based on this determination, and if data needs to be scheduled to terminal device 110, network device 120 can transmit control information on the active carrier during the first on-duration period.
[0116] In some example embodiments, the DCP-based DRX mode can also indicate the active time of the DRX cycle. If there is data to be scheduled for terminal device 110, network device 120 can perform (1450) data communication with terminal device 110 on at least one of the first carrier or the second carrier based on a carrier switching mode during the active time of the first DRX cycle. Therefore, based on the received control information, terminal device 110 can perform (1445) data communication with network device 120 on at least one of the first carrier or the second carrier based on a carrier switching mode during the active time of the first DRX cycle.
[0117] In some example embodiments, network device 120 and terminal device 110 can determine whether a first carrier or a second carrier is active during the active period of a first DRX cycle based on the carrier switching mode. Based on this determination, network device 120 and terminal device 110 can perform data communication with each other on the active carrier during the active period of the first DRX cycle. If the FDD carrier is active, UL and DL data transmission can be scheduled. If the SDL carrier is active, only DL data transmission can be scheduled.
[0118] In some example embodiments, if one of the first and second carriers is active at the start of the active period of the first DRX cycle, network device 120 may perform data communication with terminal device 110 on the active carrier from the start of the active period. In some example embodiments, based on a carrier switching mode, network device 120 may switch from an active carrier to another carrier among the first and second carriers during the active period of the first DRX cycle, and perform data communication with terminal device 110 on the other active carrier during the active period of the first DRX cycle. The switching between the first and second carriers may occur in multiple rounds during the active period of the first DRX cycle.
[0119] Therefore, in some example embodiments, if one of the first carrier and the second carrier is active at the start of the active time of the first DRX cycle, the terminal device 110 can perform data communication with the network device 120 on the active carrier from the start of the active time. In some example embodiments, based on a carrier switching mode, the terminal device 110 can switch from the active carrier to the other carrier of the first carrier and the second carrier during the active time of the first DRX cycle, and perform data communication with the network device 120 on the other active carrier during the active time of the first DRX cycle. Multiple rounds of switching between the first carrier and the second carrier can occur during the active time of the first DRX cycle.
[0120] In some example embodiments, if no DCP is transmitted, or if the transmitted DCP indicates that the first on-duration of the first DRX cycle is dormant, network device 120 may skip control information transmission during the first on-duration of the first DRX cycle. Therefore, if terminal device 110 does not receive a DCP from network device 120, or if the received DCP indicates that the first on-duration of the first DRX cycle is dormant, terminal device 120 may skip control information monitoring during the first on-duration of the first DRX cycle. If the DCP does not indicate non-dormant for that carrier pair, terminal device 110 may need to switch to the first carrier for the cancelled on-duration. Terminal device 120 may then monitor for a DCP from network device 120 on the first carrier during a second DRX cycle following the first DRX cycle, based on at least one DCP monitoring opportunity.
[0121] Figure 15 A schematic diagram of LBCA switching modes with DRX based on DCP is shown. For example... Figure 15 As shown, the DCP-based DRX mode 1301 can indicate at least one on-time duration with a PDCCH timing and at least one DCP monitoring timing. Terminal device 110 can monitor DCP at at least one DCP monitoring timing and monitor DCI from network device 120 at a PDCCH timing. The LBCA handover mode 1302 can indicate an active handover between CC1 and CC2. The LBCA handover mode with DCP-based DRX can combine these two modes.
[0122] like Figure 15 As shown, in one example, if terminal device 110 receives DCP 1504, terminal device 110 can activate LBCA handover mode. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active and monitor DCI during the subsequent on-time duration on CC2. If DCI 1505 is received, terminal device 110 can perform data communication with network device 120 during the active time of the same DRX cycle. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active during the active time and perform data communication with network device 120 on CC2.
[0123] In another example, if terminal device 110 receives DCP 1506, terminal device 110 can activate LBCA handover mode. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active and monitor DCI during the subsequent on-time duration on CC2. If DCI 1507 is received, terminal device 110 can perform data communication with network device 120 during the active time of the same DRX cycle. Based on LBCA handover mode, terminal device 110 can determine that CC2 is active during the active time and perform data communication with network device 120 on CC2. If terminal device 110 determines to switch from CC2 to CC1 based on LBCA handover mode, it can continue to perform data communication with network device 120 on CC1. Multiple handovers can occur between CC1 and CC2 before the active time of the DRX cycle expires. When terminal device 110 is active, terminal device 110 may not monitor DCP 1508 during the DCP monitoring period.
[0124] Figure 16 Example signaling stream 1600 for carrier handover in DCP-based DRX is shown according to some example embodiments of this disclosure. Signaling stream 1600 can be considered as Figure 14 Example of signaling flow 1400. Signaling flow 1600 may involve terminal device 110 and network device 120. Figure 16 In the example, it is assumed that the first carrier is an FDD carrier (also known as a PCell carrier) associated with PCell 102-1, and the second carrier is an SDL carrier (also known as a SCell carrier) associated with SCell 102-2. It would be appropriate for the two carriers involved in the carrier switching mode to include other types of carriers.
[0125] like Figure 16 As shown, at 1601, terminal device 110 can indicate its capabilities related to LBCA handover, i.e., the aforementioned capability information. At 1602, network device 120 can transmit first configuration information to terminal device 110 to configure terminal device 110 using an LBCA handover mode (e.g., '001110…'). "0" can represent a time slot on the PCell carrier, and "1" can represent a time slot on the SCell carrier.
[0126] At 1603, network device 120 can transmit second configuration information to terminal device 110 and configure terminal device 110 using a DCP-based DRX mode. The DCP-based DRX mode can at least indicate the duration of the DRX cycle, and the duration of the cycle can follow the LBCA handover mode.
[0127] At 1604, terminal device 110 and network device 120 can remain on the PCell carrier when the time slot falls into the DRX off period.
[0128] At 1605, terminal device 110 and network device 120 can remain on the PCell carrier. Network device 120 can transmit a DCP to terminal device 110, which indicates that the subsequent on duration is dormant. At 1606, the PDCCH timing during the on duration can be cancelled. At 1607, terminal device 110 and network device 120 can remain on the PCell carrier. At 1608, since network device 120 has not transmitted a DCI for PDSCH scheduling, terminal device 110 can move to DRX off. At 1609, the DRX cycle can end according to the DCP-based DRX mode.
[0129] At 1610, network device 120 can transmit a DCP to the terminal device to indicate the duration of non-sleep on. Subsequently, a handover between the PCell carrier and the SCell carrier will be triggered at 1611.
[0130] At 1612, based on the carrier switching mode, the PDCCH timing can be on the SCell carrier during the open duration. At 1613, network device 120 can use DCI to schedule PDSCH data transmission on the SCell carrier. At 1614, the open duration can expire. At 1615, network device 120 can perform data communication with terminal device 110 on the SCell carrier. At 1616, terminal device 110 and network device 120 can switch from the SCell carrier to the PCell carrier.
[0131] At 1617, network device 120 can perform data communication with terminal device 110 on the PCell carrier until the activity time expires at 1618. At 1619, terminal device 110 and network device 120 can remain on the PCell carrier. At 1620, the DRX cycle can end.
[0132] Then, at 1621, network device 120 can transmit a DCP indicating the duration of sleep on start to terminal device 110. At 1622, terminal device 110 can stop monitoring DCI during PDCCH timing. At 1623, terminal device 110 and network device 120 can remain in PCell based on carrier switching mode.
[0133] According to some other example embodiments of this disclosure, when both a carrier switching mode and a DCP-based DRX mode are configured, the terminal device monitors the DCP on the first carrier during the configured DCP monitoring opportunities(s). If a DCP is received and the DCP indicates that the first on duration of the first DRX cycle is non-dormant, the terminal device monitors control information on the first carrier during the first on duration of the first DRX cycle. Otherwise, the terminal device may remain dormant. If control information is received, the terminal device then activates the carrier switching mode for performing data communication with the network device during the active time of the first DRX cycle indicated by the DCP-based DRX mode.
[0134] In this solution, the DCP is always transmitted on the first carrier (e.g., the PCell carrier), and the associated control information monitoring during the on-duration period is also located on the first carrier. If no DCP or control information is received, the terminal device may not switch. In one option, carrier switching is activated when control information for cross-carrier scheduling is present during the on-duration period of the DRX cycle, and it continues as long as DRX activity exists. Once the scheduled transmission ends, the carrier switching mode is canceled. According to this embodiment, the DRX on-duration mode is only on one carrier, making the scheduling solution simpler on the network side. Compared to the example embodiment described above, carrier switching is further minimized. In addition to the DCP indicating sleep, the on-duration period of unscheduled data communication also allows the terminal device to remain on the first carrier without switching to another carrier.
[0135] Figure 17 Signaling flow 1700 for an example procedure for carrier switching in DRX according to some example embodiments of this disclosure is shown. For example... Figure 17 As shown, signaling flow 1700 involves terminal device 110 and network device 120.
[0136] like Figure 17 As shown, network device 120 transmits (1705) first configuration information to terminal device 110, the first configuration information indicating a carrier switching mode that switches between the activation of a first carrier and the activation of a second carrier. Terminal device 110 receives (1710) the first configuration information.
[0137] In addition, network device 120 transmits (1715) second configuration information to terminal device 110, the second configuration information indicating a DCP-based DRX mode. Terminal device 110 receives (1720) the second configuration information. The DCP-based DRX mode can indicate the activation duration and the activity time of the DRX cycle, and can also indicate at least one DCP monitoring opportunity.
[0138] Details of the first and second configuration information can be found in the reference. Figure 14 For the sake of brevity, I will not repeat the similar points discussed here.
[0139] In some example embodiments, terminal device 110 may report its carrier switching capability to network device 120. For example... Figure 17 As shown, terminal device 110 can transmit (1702) capability information indicating whether terminal device 110 is capable of carrier switching to network device 120. The network device can receive (1704) the capability information. If the capability information indicates that terminal device 110 is capable of carrier switching, then network device 120 can transmit first configuration information indicating the carrier switching mode to terminal device 110. Typically, it is assumed that terminal device 110 supports DRX and DCP.
[0140] With carrier switching mode and DCP-based DRX mode configured, terminal device 110 monitors (1730) DCP on the first carrier based on at least one DCP monitoring opportunity. DCP can indicate whether the on-duration of the DRX cycle after receiving DCP is sleep or non-sleep. For ease of discussion, such on-duration and DRX cycle can be referred to as first on-duration and first DRX cycle.
[0141] On the network side, network device 120 always transmits (1725) DCP (if needed) on the first carrier based on the configured (multiple) DCP monitoring timing, because it knows that terminal device 110 will monitor DCP on the first carrier.
[0142] According to the received DCP and the received DCP indicating that the first on duration of the first DRX cycle is non-dormant, the terminal device 110 monitors (1740) control information on the first carrier during the first on duration of the first DRX cycle.
[0143] On the network side, after network device 120 transmits a DCP indicating a non-sleep state for the first on-duration of the first DRX cycle to terminal device 110, network device 120 always transmits control information (1735) on the first carrier during the first on-duration of the first DRX cycle. Network device 120 can determine the control information transmission based on the DCP-based DRX mode. If network device 120 determines that data needs to be scheduled for terminal device 110, network device 120 can transmit the DCP in advance to indicate a non-sleep state for the subsequent on-duration of the DRX cycle. Then, network device 120 can also transmit control information (e.g., DCI) on the first carrier during the on-duration of the DRX cycle indicated by the DCP-based DRX mode (e.g., during PDCCH timing).
[0144] In Figure 17 In related example embodiments, it is assumed that control information monitoring in DCP and DRX is always performed on one of the carriers (i.e., the first carrier used herein). In some examples, between the first and second carriers, a carrier supporting both UL and DL, or a carrier associated with the PCell, may be selected as the carrier on which control information is monitored. In some example embodiments, the first carrier on which DCP and control information are monitored may be assigned to terminal device 110 and is also known to network device 120. In some example embodiments, the simultaneous configuration of DCP-based DRX mode and carrier switching mode will implicitly instruct terminal device 110 to follow the proposed behavior, i.e., to monitor DCP at (multiple) DCP monitoring times, and to monitor control information during the on-duration of the DRX cycle after receiving DCP, and then activate carrier switching when scheduled by control information.
[0145] In some example embodiments, network device 120 may specifically instruct terminal device 110 to perform DCP monitoring and control information monitoring on a first carrier and to apply carrier handover during the active period of the DRX cycle. For example, second configuration information may also instruct to perform DCP monitoring and control information monitoring on a first carrier and to apply carrier handover during the active period of the DRX cycle when scheduled by control information.
[0146] In some example embodiments, if no DCP is received or a DCP indication to sleep (i.e., the first on-duration of the first DRX cycle following the DCP is a sleep period), the terminal device 110 may remain on the first carrier and will not skip control information monitoring during the first on-duration of the first DRX cycle. The terminal device 110 may still monitor the DCP on the first carrier at subsequent DCP monitoring opportunities (e.g., during DCP monitoring in the second DRX cycle following the first DRX cycle).
[0147] If the DCP indication is received as non-sleep but no control information is received during the first on duration of the first DRX cycle, or if the received control information indicates no scheduling (e.g., no PDSCH or PUSCH data scheduling), the carrier switching mode may remain inactive, and the terminal device 110 may remain on the first carrier without switching to another carrier.
[0148] Based on the detection that control information is received on the first carrier during the first on duration of the first DRX cycle, terminal device 110 activates (1745) carrier switching mode to perform data communication with network device 120 during the active time of the first DRX cycle indicated by the DCP-based DRX mode. Similarly, on the network side, when network device 120 transmits control information to terminal device 110 during the first on duration of the first DRX cycle, network device 120 also activates (1750) carrier switching mode during the active time of the first DRX cycle.
[0149] In an example embodiment, cross-carrier scheduling can be applied so that control information received on the first carrier can be scheduled for data transmission on the first carrier and / or the second carrier (e.g., UL / DL data transmission).
[0150] In some example embodiments, depending on whether a carrier switching mode is activated, i.e., control information is detected during the active duration of the DRX cycle, the terminal device 110 and the network device 120 may perform (1755, 1760) data communication with each other on at least one of the first carrier or the second carrier during the active time of the first DRX cycle based on the carrier switching mode.
[0151] Specifically, terminal device 110 can determine whether the first carrier or the second carrier is active during the active period of the first DRX cycle based on the carrier switching mode; and based on this determination, perform data communication with network device 120 on the active carrier during the active period of the first DRX cycle. Network device 120 can follow the same rules to determine the active carrier of terminal device 110 so as to transmit data with terminal device 110 on the active carrier.
[0152] According to the carrier switching mode, one of the first and second carriers can be determined to be active at the start of the active period of the first DRX cycle. Terminal device 110 and network device 120 can then perform data communication with each other on the active carrier starting from the start of the active period of the first DRX cycle. During the active period of the first DRX cycle, the activation between the first and second carriers can be switched. Then, terminal device 110 and network device 120 can also switch from the active carrier to the other carrier among the first and second carriers based on the carrier switching mode, to determine that the other carrier is active during the active period of the first DRX cycle. Then, terminal device 110 and network device 120 can perform data communication with each other on the other active carrier during the active period of the first DRX cycle.
[0153] In some example embodiments, if no data is scheduled for terminal device 110 (e.g., no control information is received), or if the active time of the DRX cycle expires (in the case of data scheduled via control information), terminal device 110 may maintain the activation of the first carrier. If terminal device 110 performs data communication on the second carrier according to the carrier switching mode, terminal device 110 may switch from the second carrier to the first carrier to activate the first carrier for DCP and control information monitoring. Furthermore, terminal device 110 may monitor DCP again on the first carrier during a second on-duration period of the second DRX cycle following the first DRX cycle, at multiple DCP monitoring opportunities.
[0154] Figure 18 The diagram illustrates example LBCA switching mode 1801 and DCP-based DRX mode 1802, wherein the LBCA switching mode is enabled or activated after data is scheduled in accordance with a non-sleeping DCP instructing the LBCA carrier pair (CC1 and CC2).
[0155] like Figure 18 As shown, the DCP, its corresponding DRX on-time duration, and its PDCCH symbol are located on CC1 (e.g., the FDDPCell carrier). When no DCP is provided and no PDSCH is scheduled, LBCA handover mode 1801 is disabled. Once PDSCH transmission is scheduled via cross-carrier scheduling, carrier handover begins between CC1 and CC2 according to LBCA handover mode. Once PDSCH transmission ends, LBCA handover mode is canceled or deactivated.
[0156] like Figure 18 As shown in the example, according to the LBCA handover mode 1803 with DRX, if terminal device 110 receives a DCP indicating non-sleep during the DCP monitoring time 1804 on CC1, it can continue monitoring DCI during the PDCCH time during the on-duration 1805 of the same DRX cycle. If the received DCI indicates PDSCH scheduling for terminal device 110, the LBCA handover mode is activated. At this time, according to the active LBCA handover mode, CC2 is active during the active time 1806 of the current DRX cycle. Terminal device 110 can perform PDSCH transmission on CC2. Once the PDSCH transmission ends, for example, when the active time 1806 expires, the LBCA handover mode is canceled or deactivated.
[0157] Similarly, the PDSCH scheduling trigger for handover operations on CC1 (e.g., FDD (PCell) carrier) is terminated, any handover timing in the LBCA handover mode is canceled, and DCP monitoring is maintained for further scheduling. In the following, terminal device 110 may perform DCP monitoring on the PDSCH timing during the DRX on-duty period indicated by DCP-based DRX mode 1801. If no DCP is received, the subsequent on-duty period is also skipped or canceled.
[0158] Furthermore, if a DCP is received again during DCP monitoring time 1807 and a DCI is received during PDCCH time 1808, which instructs terminal device 110 to schedule PDSCH, the LBCA handover mode is reactivated. At this time, according to the active LBCA handover mode, CC2 is active from the start of the active time of the current DRX cycle. Terminal device 110 can perform PDSCH transmission on CC2. According to LBCA handover mode 1802, CC1 becomes active during the active time of the same DRX cycle. Therefore, terminal device 110 switches to PDSCH transmission on active CC1 and then switches back to CC2, as indicated by the activation handover of LBCA handover mode 1802. A similar principle applies to the following time slots.
[0159] It should also be noted that DCP-based DRX mode can be used on SDL, but this will have the disadvantage that the uplink is punctured during each DRX-enabled duration. This means that if only the uplink is scheduled, there will be a delay until LBCA mode returns to FDD before the scheduled transmission begins.
[0160] Figure 19 Signaling flow 1900 for carrier switching in a DRX according to some example embodiments of this disclosure is shown. Signaling flow 1900 can be considered as an example of signaling flow 1700, and may also relate to terminal device 110 and network device 120. Figure 19 In the example, it is assumed that the first carrier is an FDD carrier (also known as a PCell carrier) associated with PCell 102-1, and the second carrier is an SDL carrier (also known as a SCell carrier) associated with SCell 102-2. It is appropriate that the two carriers involved in the carrier switching mode may include other types of carriers.
[0161] At 1901, terminal device 110 indicates its capabilities related to LBCA handover to network device 120, namely, the capability information described above.
[0162] At 1902, network device 120 can transmit first configuration information to terminal device 110 to configure terminal device 110 using LBCA switching mode (e.g., '001110…'). "0" can represent a time slot on the PCell carrier, and "1" can represent a time slot on the SCell carrier.
[0163] At 1903, network device 120 can transmit second configuration information to terminal device 110 and configure terminal device 110 using a DCP-based DRX mode. The DCP-based DRX mode can at least indicate the duration of the DRX cycle and at least one DCP monitoring event. LBCA handover mode is followed only during DRX activity periods. This can be specifically indicated to terminal device 110 in the configuration, or simultaneous configuration of the DCP-based DRX mode and the LBCA handover mode will implicitly mean that terminal device 110 should follow the proposed behavior.
[0164] At 1904, terminal device 110 remains on the PCell carrier when the time slot falls into the DRX off period.
[0165] At 1905, network device 120 sends a DCP indicating the duration of sleep mode activation to terminal device 110 on the PCell carrier DCP. Terminal device 110 can monitor and receive the DCP during the DCP monitoring period on the PCell carrier.
[0166] At 1906, due to the sleep indicated by DCP, it now corresponds to the timing of the canceled PDCCH on the PCell carrier during the DRX on-duration period.
[0167] At 1907-1908, since network device 120 did not send DCI for PDSCH scheduling, terminal device 110 remained in the PCell carrier (i.e., without switching) and moved to the DRX off period.
[0168] At 1909, the DRX cycle ends according to the network configuration in the DCP-based DRX mode.
[0169] At 1910, network device 120 sends a DCP indicating the duration of non-sleep on to terminal device 110. Subsequently, a switch between PCell and SCell carriers can be triggered for scheduled transmission.
[0170] At 1911, it now corresponds to the PDCCH timing on the PCell carrier during the DRX on-duration period, and the terminal device 110 can monitor the DCI on the PDCCH timing due to the non-sleep state indicated by the DCP.
[0171] At 1912, network device 120 uses DCI (cross-carrier scheduling) on the PCell carrier to schedule PDSCH data transmission during the DRX enabled duration 1913.
[0172] From 1914 to 1915, it involves a transition from the PCell to the SCell carrier, which is related to the handover time. At 1915, terminal device 110 remains on the SCell carrier to communicate with network device 120.
[0173] Between 1915 and 1919, network device 120 follows a handover mode to send data to terminal device 110 via the SCell carrier and downlink PCell carrier, and receives data from terminal device 110 via the uplink PCell carrier. The LBCA handover mode is canceled after data transmission is complete.
[0174] At 1918, the DRX activity time ends and the LBCA switchover is canceled, which can occur after the inactivity timer expires.
[0175] At 1920, the DRX cycle ends according to the network configuration in the DCP-based DRX mode.
[0176] At 1921, network device 120 transmits a DCP indicating the duration of sleep-on to terminal device 110. At 1922, it now corresponds to the timing of the cancellation of the PDCCH on the PCell carrier during the DRX-on duration. At 1923, terminal device 110 remains on the PCell carrier and can monitor potential DCPs on the PCell carrier.
[0177] In some example embodiments, the DCP received on the first carrier may also indicate the sleep state of the second carrier during the first DRX cycle. The sleep state can indicate whether the second carrier is in sleep mode. If the sleep state of the second carrier indicated in the DCP is in sleep mode during the first DRX cycle, the terminal device 110 can deactivate the carrier switching mode during the first DRX cycle. The terminal device 110 can monitor control information in the first carrier. Then, if control information is received during the first on-duration of the first DRX cycle, the terminal device 110 can perform data communication with the second device on the first carrier during the active time of the first DRX cycle.
[0178] In this specific scenario, a DCP transmitted on a first carrier (e.g., a PCell carrier) indicates that another carrier is dormant (possibly for power saving purposes), but there is data to be scheduled by the network. In this case, carrier switching is not required, and network device 120 can schedule data transmission on the first carrier without switching to the other carrier used for data scheduling. According to such an embodiment, switching is further avoided compared to a specific DCP that can disable switching during the active time used for data scheduling. In addition to the DCP indicating dormancy on the second carrier, the network device can also apply an on-duration period with data scheduling to remain on the first carrier without switching to the other carrier.
[0179] In some example embodiments, if the sleep state of the second carrier indicated by the DCP is not sleepy during the first DRX cycle, and control information is received during the first on duration of the first DRX cycle, then a carrier switching mode is enabled or activated for that DRX cycle. Terminal device 110 can perform data communication with network device 120 on the active carrier indicated by the carrier switching mode during the active time of the current DRX cycle, as described above. Network device 120 can operate in a similar manner because it knows whether the second carrier is indicated to be sleepy.
[0180] Figure 20 The diagram illustrates example LBCA handover mode 2001 and DCP-based DRX mode 2002, wherein the LBCA handover mode is enabled or activated after following non-sleeping DCP scheduling data instructing the LBCA carrier pair (CC1 and CC2).
[0181] like Figure 20 As shown, when the DCP sent via CC1 contains a sleep indication for CC2 and an activity indication for CC1 (e.g., indicating that the subsequent on duration is non-sleep), LBCA handover will not be enabled because the terminal device 110 can remain on CC1. Once the PDSCH transmission is complete, the LBCA pair can be considered to trigger the handover mode in the next DCP instance.
[0182] like Figure 20As shown in the example, according to the LBCA handover mode 2003 with DRX, terminal device 110 receives a specific DCP during the DCP monitoring timing 2004 on CC1. In addition to indicating the non-sleep on-duration duration, the DCP also includes a CC2 sleep indication to indicate that CC2 is in sleep mode. At this time, terminal device 110 can continue monitoring DCI during the PDCCH timing in the on-duration 2005 of the same DRX cycle. If the received DCI indicates PDSCH scheduling for terminal device 110, then terminal device 110 can perform PDSCH transmission on CC1 during the active time of the current DRX cycle without enabling the LBCA handover mode to switch to CC2.
[0183] However, in Figure 20 In the example, the DCP received during DCP monitoring in 2007 and 2008 does not include a CC2 sleep indication, therefore CC2 is not put into sleep mode. When terminal device 110 receives a DCI indicating PDSCH scheduling, it can still follow the LBCA handover mode and perform PDSCH scheduling on active CC2 during the active time of the corresponding DRX cycle, such as... Figure 18 In the example.
[0184] Figure 21 Signaling flow 2100 for carrier switching in a DRX according to some example embodiments of this disclosure is shown. Signaling flow 2100 can be considered as an example of signaling flow 1700, and may also relate to terminal device 110 and network device 120. Figure 21 In the example, it is assumed that the first carrier is an FDD carrier (also known as a PCell carrier) associated with PCell 102-1, and the second carrier is an SDL carrier (also known as a SCell carrier) associated with SCell 102-2. It is appropriate that the two carriers involved in the carrier switching mode may include other types of carriers.
[0185] The actions from 2101 to 2101 are similar Figure 19 The actions from 1901 to 1901 in the text.
[0186] At point 2103, network device 120 can transmit second configuration information to terminal device 110 and configure terminal device 110 using a DCP-based DRX mode. The DCP-based DRX mode can at least indicate the duration of the DRX cycle and at least one DCP monitoring event. The LBCA switching mode is followed only during DRX activity periods, or DRX activation follows a specific pattern. Figure 14 The LBCA switching mode is shown in the example.
[0187] The actions from 2104 to 2109 are similar Figure 19The actions in 1904 to 1909.
[0188] At point 2110, network device 120 sends a DCP to terminal device 110, which indicates a non-sleep indication for a non-duration period on the PCell carrier and a sleep indication for the SCell carrier. Subsequently, no handover between carriers will be triggered for scheduled transmissions; instead, the scheduled transmissions will occur on the PCell carrier.
[0189] At 2111, it now corresponds to the PDCCH timing on the PCell carrier during the DRX enable duration, and the terminal device 110 can monitor the DCI on the PDCCH timing due to the non-sleep state indicated by the DCP.
[0190] At 2112, network device 120 uses DCI (cross-carrier scheduling) on the PCell carrier to schedule PDSCH data transmission during the DRX enabled duration 2113.
[0191] From 2114 to 2115, it includes scheduled transmission between terminal device 110 and network device 120 via PCell carrier without any handover.
[0192] At point 2116, the DRX activity period ends based on the network configuration in DRX mode.
[0193] At 2120, the DRX cycle ends according to the network configuration in the DCP-based DRX mode.
[0194] At 2119, network device 120 transmits a DCP indicating the duration of sleep-on to terminal device 110. At 2120, it now corresponds to the timing of the PDCCH cancellation on the PCell carrier during the DRX-on duration. At 2121, terminal device 110 remains on the PCell carrier and can monitor potential DCPs on the PCell carrier.
[0195] Figure 22 A flowchart of an example method 2200 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Angle description method 2200 for terminal device 110 in the middle.
[0196] At box 2210, the first device receives first configuration information from the second device, the first configuration information indicating a carrier switching mode that switches between the activation of the first carrier and the activation of the second carrier.
[0197] At box 2220, the first device receives second configuration information from the second device. The second configuration information indicates a discontinuous reception DRX mode based on downlink control information (DCP) for power saving. The DCP-based DRX mode indicates at least the duration of the DRX cycle and at least one DCP monitoring opportunity.
[0198] At block 2230, the first device monitors a DCP from the second device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether the first on duration of the first DRX cycle after receiving the DCP is dormant or non-dormant.
[0199] At box 2240, based on the received DCP and the received DCP indicating that the first on duration of the first DRX cycle is non-dormant, the terminal device 110 performs control information monitoring on at least one of the first carrier or the second carrier during the first on duration of the first DRX cycle, according to the carrier switching mode.
[0200] In some example embodiments, method 2200 further includes: determining, based on the carrier switching mode, whether a first carrier or a second carrier is active during a first on-duration period of the first DRX cycle; and based on the determination, performing control information monitoring on the active carrier during the on-duration period of the first DRX cycle.
[0201] In some example embodiments, method 2200 further includes: based on the determination that control information is received from the second device during a first on-duration period of the first DRX cycle, performing data communication with the second device on at least one of the first carrier or the second carrier during the active period of the first DRX cycle, according to a carrier switching mode.
[0202] In some example embodiments, method 2200 further includes: determining, based on a carrier switching mode, whether a first carrier or a second carrier is active during the active period of a first DRX cycle; and based on the determination, performing data communication with the second device on the active carrier during the active period of the first DRX cycle.
[0203] In some example embodiments, method 2200 further includes: performing data communication with the second device on the active carrier from the start of the active time of the first DRX cycle, based on determining that one of the first carriers and the second carrier is active at the beginning of the active time of the first DRX cycle.
[0204] In some example embodiments, method 2200 further includes: switching from an active carrier to another carrier among a first carrier and a second carrier based on a carrier switching mode, to activate the other carrier during the active time of a first DRX cycle; and performing data communication with the second device on the other active carrier during the active time of the first DRX cycle.
[0205] In some example embodiments, method 2200 further includes: skipping control information monitoring during the first on-duration of the first DRX cycle based on determining that no DCP is received, or based on determining that the received DCP indicates that the first on-duration of the first DRX cycle is dormant; and monitoring DCP from the second device on the first carrier based on at least one DCP monitoring opportunity during a second DRX cycle following the first DRX cycle.
[0206] In some example embodiments, the first carrier and the second carrier are low-frequency band (LB) carriers.
[0207] In some example embodiments, the first carrier is a frequency division duplex (FDD) carrier, and the second carrier is a supplementary downlink (SDL) carrier.
[0208] In some example embodiments, the first carrier is associated with the primary cell PCell of the second device, and the second carrier is associated with the secondary cell SCell of the second device.
[0209] In some example embodiments, the first device is or is included in the terminal device, and the second device is or is included in the network device.
[0210] Figure 23 A flowchart of an example method 2300 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 2300 is described from the perspective of network device 120.
[0211] At frame 2310, the second device transmits first configuration information to the first device, the first configuration information indicating a carrier switching mode that switches between the activation of the first carrier and the activation of the second carrier.
[0212] At box 2320, the second device transmits second configuration information to the first device. The second configuration information indicates a discontinuous reception DRX mode based on downlink control information (DCP) for power saving. The DCP-based DRX mode indicates at least the duration of the DRX cycle and at least one DCP monitoring opportunity.
[0213] At block 2330, the second device transmits a DCP to the first device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether the first on duration of the first DRX cycle after the transmission of the DCP is dormant or non-dormant.
[0214] At box 2340, based on the transmitted DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant, the second device performs control information transmission on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the carrier switching mode.
[0215] In some example embodiments, method 2300 further includes: determining, based on a carrier switching mode, whether a first carrier or a second carrier is active during a first on-duration period of a first DRX cycle, according to the determination that data is to be scheduled for a first device; and, based on the determination, performing control information transmission on the active carrier during the first on-duration period of the first DRX cycle.
[0216] In some example embodiments, method 2300 further includes: based on determining that control information is transmitted to the first device during a first on-duration period of the first DRX cycle, performing data communication with the first device on at least one of a first carrier or a second carrier during the active period of the first DRX cycle, according to a carrier switching mode.
[0217] In some example embodiments, method 2300 further includes: determining, based on a carrier switching mode, whether a first carrier or a second carrier is active during the active period of a first DRX cycle; and, based on the determination, performing data communication with the first device on the active carrier during the active period of the first DRX cycle.
[0218] In some example embodiments, method 2300 further includes: performing data communication with the first device on the active carrier from the start of the active time of the first DRX cycle, based on determining that one of the first carriers and the second carrier is active at the beginning of the active time of the first DRX cycle.
[0219] In some example embodiments, method 2300 further includes: switching from an active carrier to another carrier among a first carrier and a second carrier based on a carrier switching mode, to activate the other carrier during the active time of a first DRX cycle; and performing data communication with the first device on the other active carrier during the active time of the first DRX cycle.
[0220] In some example embodiments, method 2300 further includes: skipping control information transmission during the first on-duration of the first DRX cycle based on determining that no DCP is transmitted, or based on determining that the transmitted DCP indicates that the first on-duration of the first DRX cycle is dormant.
[0221] In some example embodiments, the first carrier is a frequency division duplex (FDD) carrier, and the second carrier is a supplementary downlink (SDL) carrier.
[0222] In some example embodiments, the first carrier is associated with the primary cell PCell of the second device, and the second carrier is associated with the secondary cell SCell of the second device.
[0223] In some example embodiments, a first means capable of performing any of method 2200 (e.g., Figure 1 The terminal device 110 may include components for performing corresponding operations of method 2200. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In terminal device 110.
[0224] In some example embodiments, the first device includes: components for receiving first configuration information from the second device, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; components for receiving second configuration information from the second device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DRX mode based on DCP indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; components for monitoring a DCP from the second device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; and components for performing control information monitoring on at least one carrier of the first carrier or the second carrier during the first on-duration of the first DRX cycle, based on the carrier switching mode, according to the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0225] In some example embodiments, any method 2300 can be executed (e.g., Figure 1 The second means of the network device 120 may include components for performing the corresponding operations of method 2300. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second means may be implemented as or included in... Figure 1 Among the network devices in 120.
[0226] In some example embodiments, the second device includes: components for transmitting first configuration information to the first device, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; components for transmitting second configuration information to the first device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DRX mode based on DCP indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; components for transmitting a DCP to the first device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; and components for performing control information transmission on at least one of the first carriers or the second carrier during the first on-duration of the first DRX cycle, based on the carrier switching mode, according to the transmission of the DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0227] Figure 24 A flowchart of an example method 2400 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 The angle description method of the terminal device 110 in the 2400.
[0228] At box 2410, the first device receives first configuration information from the second device, the first configuration information indicating a carrier switching mode that switches between the activation of the first carrier and the activation of the second carrier.
[0229] At box 2420, the first device receives second configuration information from the second device. The second configuration information indicates a discontinuous reception DRX mode based on downlink control information (DCP) for power saving. The DCP-based DRX mode indicates the on-time duration and activity time of the DRX cycle and at least one DCP monitoring opportunity.
[0230] At box 2430, the first device monitors a DCP from the second device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether the first on duration of the first DRX cycle after receiving the DCP is dormant or non-dormant.
[0231] At box 2440, based on the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant, the first device monitors control information on the first carrier during the first on-duration of the first DRX cycle.
[0232] At box 2450, based on the detection that control information has been received, the first device activates a carrier switching mode for performing data communication with the second device during the active time of the first DRX cycle indicated by the DRX mode.
[0233] In some example embodiments, method 2400 further includes: determining that a carrier switching mode is activated, and performing data communication with the second device on at least one of the first carrier or the second carrier during the active time of the first DRX cycle based on the carrier switching mode.
[0234] In some example embodiments, method 2400 further includes: determining, based on a carrier switching mode, whether a first carrier or a second carrier is active during the active period of a first DRX cycle; and based on the determination, performing data communication with the second device on the active carrier during the active period of the first DRX cycle.
[0235] In some example embodiments, method 2400 further includes: performing data communication with the second device on the active carrier from the start of the active time of the first DRX cycle, based on determining that one of the first carriers and the second carrier is active at the beginning of the active time of the first DRX cycle.
[0236] In some example embodiments, method 2400 further includes: switching from an active carrier to another carrier among a first carrier and a second carrier based on a carrier switching mode, to activate the other carrier during the active time of a first DRX cycle; and performing data communication with the second device on the other active carrier during the active time of the first DRX cycle.
[0237] In some example embodiments, method 2400 further includes: skipping control information monitoring during the first on-duration of the first DRX cycle based on determining that the DCP has not been received, or based on determining that the received DCP indicates that the first on-duration of the first DRX cycle is dormant; and monitoring the DCP from the second device on the first carrier based on at least one DCP monitoring opportunity during a second DRX cycle following the first DRX cycle.
[0238] In some example embodiments, method 2400 further includes: maintaining the activation of the first carrier or switching from a second carrier to the first carrier to activate the first carrier based on determining that no control information is received on the first carrier during the first on-duration of the first DRX cycle, or based on the expiration of the active time of the first DRX cycle; and during a second DRX cycle following the first DRX cycle, monitoring DCP from the second device on the first carrier based on at least one DCP monitoring opportunity.
[0239] In some example embodiments, method 2400 further includes: deactivating the carrier switching mode during the first DRX period based on determining that the sleep state of the second carrier is sleep during the first DRX period; and performing data communication with the second device on the first carrier based on detecting that control information is received.
[0240] In some example embodiments, the first device is configured to activate a carrier switching mode based on determining that the sleep state of the second carrier is non-sleep during the first DRX period and based on detecting that control information is received. The carrier switching mode is used to perform data communication with the second device on at least one of the first carrier or the second carrier.
[0241] In some example embodiments, the first carrier is a frequency division duplex (FDD) carrier, and the second carrier is a supplementary downlink (SDL) carrier.
[0242] In some example embodiments, the first carrier is associated with the primary cell PCell of the second device, and the second carrier is associated with the secondary cell SCell of the second device.
[0243] In some example embodiments, the first device is or is included in the terminal device, and the second device is or is included in the network device.
[0244] Figure 25 A flowchart of an example method 2500 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 2500 describes the network device 120 from the perspective of network device 120.
[0245] At frame 2510, the second device transmits first configuration information to the first device, the first configuration information indicating a carrier switching mode that switches between the activation of the first carrier and the activation of the second carrier.
[0246] At box 2520, the second device transmits second configuration information to the first device. The second configuration information indicates a discontinuous reception DRX mode based on downlink control information (DCP) for power saving. The DCP-based DRX mode indicates the on-time duration and activity time of the DRX cycle and at least one DCP monitoring opportunity.
[0247] At box 2530, based on the determination that the first device is in a dormant state, the second device transmits a DCP to the first device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether the first on duration of the first DRX cycle after the transmission of the DCP is in a dormant state or not in a dormant state.
[0248] At box 2540, according to the transmitted DCP and the transmitted DCP indicating that the first on duration of the first DRX cycle is non-dormant and that data is to be scheduled for the first device, the second device transmits control information to the first device on the first carrier during the first on duration of the first DRX cycle.
[0249] At box 2550, the second device activates a carrier switching mode for performing data communication with the first device during the active time of the first DRX cycle.
[0250] In some example embodiments, method 2500 further includes: based on determining that a carrier switching mode is activated, the second device performs data communication with the first device on at least one of the first carrier or the second carrier during the active time of the first DRX cycle, according to the carrier switching mode.
[0251] In some example embodiments, method 2500 further includes: determining, based on a carrier switching mode, whether a first carrier or a second carrier is active during the active period of a first DRX cycle; and based on the determination, performing data communication with the first device on the active carrier during the active period of the first DRX cycle.
[0252] In some example embodiments, method 2500 further includes: performing data communication with the first device on the active carrier from the start of the active time of the first DRX cycle, based on determining that one of the first carriers and the second carrier is active at the beginning of the active time of the first DRX cycle.
[0253] In some example embodiments, method 2500 further includes: switching from an active carrier to another carrier among a first carrier and a second carrier based on a carrier switching mode, to activate the other carrier during the active time of a first DRX cycle; and performing data communication with the first device on the other active carrier during the active time of the first DRX cycle.
[0254] In some example embodiments, the first device is further configured to skip control information transmission during the first on-duration of the first DRX cycle based on determining that a DCP has not been transmitted, or based on determining that a transmitted DCP indicates that the first on-duration of the first DRX cycle is dormant.
[0255] In some example embodiments, method 2500 further includes: maintaining the activation of the first carrier or switching from the second carrier to the first carrier to activate the first carrier based on determining that no data needs to be scheduled for the first device, or based on the expiration of the activity time of the first DRX cycle.
[0256] In some example embodiments, method 2500 further includes: deactivating the carrier switching mode during the first DRX period based on determining that the sleep state of the second carrier is sleep during the first DRX period; and performing data communication with the first device on the first carrier based on detecting that control information is received.
[0257] In some example embodiments, method 2500 further includes: activating a carrier switching mode based on determining that the sleep state of the second carrier during the first DRX period is non-sleep and based on determining that data is to be scheduled for the first device, the carrier switching mode being used to perform data communication with the first device on at least one of the first carrier or the second carrier. (Corresponding method claims, device claims with device plus functional limitations, and medium claims will be added after the above device claims are confirmed.) In some example embodiments, a first device capable of performing any of method 2400 (e.g., Figure 1 The terminal device 110 may include components for performing corresponding operations of method 2400. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In terminal device 110.
[0258] In some example embodiments, the first device includes: components for receiving first configuration information from the second device, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; components for receiving second configuration information from the second device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DRX mode based on DCP indicating an on-duration and active period of a DRX cycle and at least one DCP monitoring opportunity; components for monitoring a DCP from the second device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; components for monitoring control information on the first carrier during the first on-duration of the first DRX cycle based on receiving the DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant; and components for activating a carrier switching mode for performing data communication with the second device during the active period of the first DRX cycle indicated by the DRX mode, based on detecting that control information has been received.
[0259] In some example embodiments, any method 2500 can be executed (e.g., Figure 1The second means of the network device 120 may include components for performing the corresponding operations of method 2500. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second means may be implemented as or included in... Figure 1 Among the network devices in 120.
[0260] In some example embodiments, the second device includes: components for transmitting first configuration information to the first device, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; components for transmitting second configuration information to the first device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DRX mode based on DCP indicating the on-duration and active time of a DRX cycle and at least one DCP monitoring opportunity; components for transmitting a DCP to the first device on the first carrier based on at least one DCP monitoring opportunity, depending on whether the first device is determined to be dormant, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; components for transmitting control information to the first device on the first carrier during the first on-duration of the first DRX cycle, depending on the transmission of the DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant and data is to be scheduled for the first device; and components for activating a carrier switching mode for performing data communication with the first device during the active time of the first DRX cycle.
[0261] Figure 26 This is a simplified block diagram of a device 2600 suitable for implementing an example embodiment of the present disclosure. The device 2600 can be provided to implement a communication device, for example, such as... Figure 1 The terminal device 110 or network device 120 shown. As shown, device 2600 includes one or more processors 2610, one or more memories 2620 coupled to processor 2610, and one or more communication modules 2640 coupled to processor 2610.
[0262] Communication module 2640 is used for bidirectional communication. Communication module 2640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 2640 may include at least one antenna.
[0263] As a non-limiting example, processor 2610 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 2600 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.
[0264] Memory 2620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 2624, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 2622 and other volatile memories that will not persist for the duration of a power outage.
[0265] Computer program 2630 includes computer-executable instructions that are executed by an associated processor 2610. The instructions of program 2630 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 2630 may be stored in memory (e.g., ROM 2624). Processor 2610 can perform any suitable actions and processes by loading program 2630 into RAM 2622.
[0266] Example embodiments of this disclosure can be implemented by program 2630, enabling device 2600 to execute as described in the reference. Figures 2 to 21 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.
[0267] In some example embodiments, program 2630 may be tangibly contained in a computer-readable medium, which may be included in device 2600 (such as memory 2620) or other storage device accessible by device 2600. Device 2600 may load program 2630 from the computer-readable medium into RAM 2622 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).
[0268] Figure 27An example of a computer-readable medium 2700 is shown, which may be in the form of a CD, DVD, or other optical storage disc. Program 2630 is stored on the computer-readable medium 2700.
[0269] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0270] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.
[0271] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0272] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.
[0273] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having 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 optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0274] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0275] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.
[0276] Furthermore, various implementations of this disclosure can be described with reference to the following entries, and their features can be combined in any reasonable manner.
[0277] Item 1. A first means for communication, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first means to at least: receive first configuration information from a second means, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; receive second configuration information from the second means, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; monitor a DCP from the second means on a first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; and, based on the carrier switching mode, perform control information monitoring on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0278] Item 2. The first means according to Item 1, wherein the first means is configured to: determine, based on a carrier switching mode, whether a first carrier or a second carrier is active during a first on-duration period of a first DRX cycle; and based on the determination, perform control information monitoring on the active carrier during the on-duration period of the first DRX cycle.
[0279] Item 3. The first device according to Item 1, wherein the DCP-based DRX mode further indicates the active time of the DRX cycle, and the first device is further configured to: receive control information from the second device during a first on-time of the first DRX cycle, and perform data communication with the second device on at least one of the first carrier or the second carrier during the active time of the first DRX cycle based on a carrier switching mode.
[0280] Item 4. The first means according to Item 3, wherein the first means is configured to: determine, based on a carrier switching mode, whether a first carrier or a second carrier is active during the active period of a first DRX cycle; and based on the determination, perform data communication with the second means on the active carrier during the active period of the first DRX cycle.
[0281] Item 5. The first means according to Item 4, wherein the first means is configured to: perform data communication with the second means on the active carrier from the beginning of the active time of the first DRX cycle, based on determining that one of the first carriers and the second carrier is active at the beginning of the active time of the first DRX cycle.
[0282] Item 6. The first device according to Item 5, wherein the first device is configured to: switch from an active carrier to another carrier of the first carrier and the second carrier based on a carrier switching mode, to activate the other carrier during the active time of the first DRX cycle; and to perform data communication with the second device on the other active carrier during the active time of the first DRX cycle.
[0283] Item 7. The first means according to Item 1, wherein the first means is configured to: skip control information monitoring during the first on-duration of the first DRX period based on determining that no DCP is received, or based on determining that the received DCP indicates that the first on-duration of the first DRX period is dormant; and during a second DRX period following the first DRX period, monitor the DCP from the second means on the first carrier based on at least one DCP monitoring opportunity.
[0284] Item 8. A first device according to any one of items 1 to 7, wherein the first carrier and the second carrier are low-frequency band (LB) carriers.
[0285] Item 9. A first device according to any one of items 1 to 7, wherein the first carrier is a frequency division duplex (FDD) carrier and the second carrier is a supplementary downlink (SDL) carrier.
[0286] Item 10. A first device according to any one of items 1 to 7, wherein a first carrier is associated with the primary cell PCell of the second device, and a second carrier is associated with the secondary cell SCell of the second device.
[0287] Item 11. A second means for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second means to at least: transmit first configuration information to a first means, the first configuration information indicating a carrier switching mode that switches between activation of a first carrier and activation of a second carrier; transmit second configuration information to the first means, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; transmit a DCP to the first means on the first carrier based on the at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; and, based on the carrier switching mode, perform control information transmission on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the transmission of the DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0288] Item 12. The second means according to Item 11, wherein the second means is configured to: determine, based on the determined data to be scheduled for the first means, whether the first carrier or the second carrier is active during the first on-duration of the first DRX cycle; and based on the determination, perform control information transmission on the active carrier during the first on-duration of the first DRX cycle.
[0289] Item 13. The second device according to Item 11 or 12, wherein the DRX mode further indicates the active time of the DRX cycle, and the second device is further configured to: transmit control information to the first device according to a determination of a first on-time duration of the first DRX cycle, and perform data communication with the first device on at least one of the first carrier or the second carrier during the active time of the first DRX cycle based on a carrier switching mode.
[0290] Item 14. A method for communication, comprising: receiving first configuration information from a second device, the first configuration information indicating a carrier switching mode switching between activation of a first carrier and activation of a second carrier; receiving second configuration information from the second device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; monitoring a DCP from the second device on a first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after receiving the DCP is dormant or non-dormant; and, based on the carrier switching mode, performing control information monitoring on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
[0291] Item 15. A method for communication, comprising: transmitting first configuration information to a first device, the first configuration information indicating a carrier switching mode switching between activation of a first carrier and activation of a second carrier; transmitting second configuration information to the first device, the second configuration information indicating a discontinuous reception DRX mode based on downlink control information (DCP) for power saving, the DCP-based DRX mode indicating at least an on-duration of a DRX cycle and at least one DCP monitoring opportunity; transmitting a DCP to the first device on the first carrier based on at least one DCP monitoring opportunity, the DCP indicating whether a first on-duration of a first DRX cycle after the transmission of the DCP is dormant or non-dormant; and, based on the carrier switching mode, performing control information transmission on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the transmitted DCP and the transmitted DCP indicating that the first on-duration of the first DRX cycle is non-dormant.
Claims
1. A first device for communication, comprising: At least one processor; as well as At least one memory stores instructions, which, when executed by the at least one processor, cause the first device to at least: Receive first configuration information from the second device, the first configuration information indicating a carrier switching mode that switches between the activation of the first carrier and the activation of the second carrier; The second device receives second configuration information, which indicates a discontinuous reception DRX mode based on downlink control information (DCP) for power saving. The DCP-based DRX mode indicates at least the on-time duration of the DRX cycle and at least one DCP monitoring opportunity. Based on the at least one DCP monitoring timing, a DCP from the second device is monitored on the first carrier, the DCP indicating whether the first on-duration of the first DRX cycle after receiving the DCP is sleep or non-sleep; and Based on the received DCP and the received DCP indicating that the first on-duration of the first DRX cycle is non-dormant, control information monitoring is performed on at least one of the first carrier or the second carrier during the first on-duration of the first DRX cycle, according to the carrier switching mode.
2. The first device according to claim 1, wherein the first device is configured to: Based on the carrier switching mode, determine whether the first carrier or the second carrier is active during the first on-duration period of the first DRX cycle; and Based on the determination, control information monitoring is performed on the active carrier during the on-duration period of the first DRX cycle.
3. The first apparatus of claim 1, wherein the DCP-based DRX mode further indicates the active time of the DRX cycle, and the first apparatus is further configured such that: Based on the control information received from the second device during the first on-duration period of the first DRX cycle, and the carrier switching mode, data communication with the second device is performed on at least one of the first carrier or the second carrier during the active period of the first DRX cycle.
4. The first device according to claim 3, wherein the first device is configured to: Based on the carrier switching mode, determine whether the first carrier or the second carrier is active during the active time of the first DRX cycle; and Based on the determination, data communication with the second device is performed on the active carrier during the active time of the first DRX cycle.
5. The first device according to claim 4, wherein the first device is configured to: Based on the determination that one of the first carrier and the second carrier is active at the beginning of the active time of the first DRX cycle, data communication with the second device is performed on the active carrier from the beginning of the active time of the first DRX cycle.
6. The first device according to claim 5, wherein the first device is configured to: Based on the carrier switching mode, switching from the active carrier to another carrier among the first carrier and the second carrier to activate the other carrier during the active time of the first DRX cycle; and During the active time of the first DRX cycle, data communication with the second device is performed on the other active carrier.
7. The first device according to claim 1, wherein the first device is configured such that: Based on the determination that no DCP is received, or based on the determination that the received DCP indicates that the first on duration of the first DRX cycle is dormant, the control information monitoring is skipped during the first on duration of the first DRX cycle; and During the second DRX period following the first DRX period, the DCP from the second device is monitored on the first carrier based on the at least one DCP monitoring opportunity.
8. The first device according to any one of claims 1 to 7, wherein the first carrier and the second carrier are low-frequency (LB) carriers.
9. The first apparatus according to any one of claims 1 to 7, wherein the first carrier is a frequency division duplex (FDD) carrier and the second carrier is a supplementary downlink (SDL) carrier.
10. The first apparatus according to any one of claims 1 to 7, wherein the first carrier is associated with the primary cell PCell of the second apparatus, and the second carrier is associated with the secondary cell SCell of the second apparatus.
