CN114286429B

CN114286429B - Communication method and device

Info

Publication number: CN114286429B
Application number: CN202011231197.1A
Authority: CN
Inventors: 邝奕如; 薛祎凡; 薛丽霞; 徐海博
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-09-27
Filing date: 2020-11-06
Publication date: 2024-04-16
Anticipated expiration: 2040-11-06
Also published as: CN114286429A

Abstract

The application relates to a communication method and equipment. In the event that the terminal device determines not to listen to the DCP for the first DCP listening occasion, the terminal device wakes up on the first set of carriers for a first DRX duration associated with the first DCP listening occasion and wakes up or sleeps on the second set of carriers for a second DRX duration associated with the first DCP listening occasion. The first group of carriers comprises one or more carriers configured to the terminal device, the first group of carriers applies a first DRX configuration, the first DRX duration corresponds to the first DRX configuration, the second group of carriers comprises one or more carriers configured to the terminal device, the second group of carriers applies a second DRX configuration, the second DRX duration corresponds to the second DRX configuration. The two techniques of DRX configuration can be used in combination with a wake-up signal, helping to further reduce the power consumption of the terminal device.

Description

Communication method and device

Cross Reference to Related Applications

The present application claims priority from chinese patent application filed on month 27 of 2020, filed in chinese national intellectual property office, application number 202011032366.9, application name "a DCP monitoring method, terminal and network device", the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a communications method and apparatus.

Background

In the fifth generation mobile communication technology (the 5th generation,5G) technology, a User Equipment (UE) needs to further save power consumption. For this purpose, an indication signal is introduced under the current discontinuous reception (discontinuous reception, DRX) mechanism, and the indication signal is a physical downlink control channel wake-up signal (PDCCH-WUS). The indication signal can indicate whether the UE needs to wake up or whether it can sleep within a subsequent DRX "activation time". PDCCH-WUS is also known in the standard as downlink control information (downlink control information with cyclic redundancy check scrambled by PS-radio network tempory identity, DCP) with cyclic redundancy check, scrambled using a power saving radio network temporary identity (power saving radio network tempory identity, PS-RNTI), the DCP may be in the form of a signal in DCI. At present, when a monitoring opportunity arrives, if all DCP monitoring opportunities (DCP occisions) included in the monitoring opportunity arrive at one time, the UE does not monitor in the monitoring opportunity, and the UE wakes up by default in a Duration (On Duration) time in a DRX cycle associated with the monitoring opportunity; and if at least one DCP monitoring opportunity included in the monitoring opportunity is located in the DRX non-active time, the UE monitors in the DCP monitoring opportunity located in the DRX non-active time. Wherein the one-time listening occasion may include one or more DCP listening occasions (DCP occasin (s)).

Currently, a User Equipment (UE) in a radio resource control (radio resource control, RRC) connected state may support two discontinuous reception (discontinuous reception, DRX) configurations. However, no two DRX configuration techniques are currently used in combination with the wake-up signal, which affects the flexibility of the base station configuration. And two DRX configurations are introduced to save functions, and the purpose of the wake-up signal is also to save power consumption, and if the two cannot be combined, the purpose of further reducing the power consumption of the UE cannot be achieved.

Disclosure of Invention

The embodiment of the application provides a communication method and equipment for reducing power consumption of UE.

In a first aspect, a first communication method is provided, which is executable by a terminal device or by a chip system, which is capable of implementing the functions of the terminal device. The terminal equipment is configured with a first group of carriers and a second group of carriers, the first group of carriers belong to FR1, the first group of carriers comprise one or more carriers configured to the terminal equipment, the first group of carriers apply a first DRX configuration, the first DRX duration corresponds to the first DRX configuration, the second group of carriers belong to FR2, the second group of carriers comprise one or more carriers configured to the terminal equipment, the second group of carriers apply a second DRX configuration, and the second DRX duration corresponds to the second DRX configuration. The method comprises the following steps: in the case that the time domain position of the first DCP listening occasion is within a first DRX activation time, the terminal device determines not to listen to the DCP for a first DCP listening occasion that is configured on the first set of carriers. On a first group of carriers, the terminal device wakes up in a first DRX duration associated with the first DCP monitoring occasion, and on a second group of carriers, the terminal device wakes up or sleeps in a second DRX duration associated with the first DCP monitoring occasion according to a first rule, wherein the first DRX duration corresponds to the first DRX configuration, the second DRX duration corresponds to the second DRX configuration, the first rule is a preset rule, or the first rule is a rule configured by configuration information from network devices; or in the case that the time domain position of the first DCP monitoring opportunity is not located or is partially located in the first DRX activation time, the terminal device determines to monitor the DCP in the first DCP monitoring opportunity, and then monitors the DCP in the first DCP monitoring opportunity; the terminal device sleeps or wakes up on the first set of carriers for the first DRX duration and sleeps or wakes up on the second set of carriers for the second DRX duration according to the monitored indication of the DCP.

In the embodiment of the application, two DRX configuration technologies can be used in combination with a wake-up signal, which is helpful for further reducing the power consumption of the terminal device. And prescribes the behavior of the terminal device in case of combining, for example, the monitoring situation of the terminal device on the DCP monitoring occasion corresponding to the first set of carriers, which applies to both the first set of carriers and the second set of carriers. In this way, the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, so that the power consumption of the terminal equipment for monitoring the DCP is reduced. And the monitoring condition of the terminal equipment on one group of carriers can be suitable for two groups of carriers, so that the DCP mechanism can be used by both groups of carriers, and the power consumption of the terminal equipment on the two groups of carriers can be further reduced.

In a first aspect, a first communication method is provided, which is executable by a terminal device or by a chip system, which is capable of implementing the functions of the terminal device. The method comprises the following steps: the terminal equipment determines whether to monitor the DCP in the first DCP monitoring time; in the case that the terminal device determines not to monitor the DCP during the first DCP monitoring occasion, on a first set of carriers, the terminal device wakes up during a first DRX duration associated with the first DCP monitoring occasion, and on a second set of carriers, the terminal device wakes up or sleeps during a second DRX duration associated with the first DCP monitoring occasion, wherein the first set of carriers includes one or more carriers configured to the terminal device, the first set of carriers applies a first DRX configuration, the first DRX duration corresponds to the first DRX configuration, the second set of carriers includes one or more carriers configured to the terminal device, the second set of carriers applies a second DRX configuration, and the second duration corresponds to the second DRX configuration.

In the embodiment of the present application, two techniques of DRX configuration can be used in combination with a wake-up signal, and specify the behavior of the terminal device in the case of combination, for example, the terminal device monitors the DCP monitoring occasion corresponding to the first set of carriers, which is applicable to both the first set of carriers and the second set of carriers. In this way, the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, so that the power consumption of the terminal equipment for monitoring the DCP is reduced. And the monitoring condition of the terminal equipment on one group of carriers can be suitable for two groups of carriers, so that the DCP mechanism can be used by both groups of carriers, and the power consumption of the terminal equipment on the two groups of carriers can be further reduced.

With reference to the second aspect, in a first optional implementation manner of the second aspect, the first DCP listening occasion is configured on the first set of carriers.

The network device may not have to configure DCP listening occasions for the second set of carriers and the terminal device only has to listen within DCP listening occasions on the first set of carriers, the listening result being applicable to both sets of carriers. Thus, the DCP mechanism can be used by both groups of carriers, and the power consumption of the terminal equipment is reduced. And the terminal equipment does not need to monitor the DCP on the second group of carriers, so that the power consumption of the terminal equipment for monitoring the DCP is further reduced.

With reference to the second aspect or the first optional implementation manner of the second aspect, in a second optional implementation manner of the second aspect, the first DRX duration is located after the first DCP listening occasion in a time domain.

On the first set of carriers, one or more DRX cycles temporally following the first DCP listening occasion may be associated with the first DCP listening occasion, as to which DRX cycles the first DCP listening occasion is associated with, may be specified by a protocol, or may be configured by the network device. The first DCP listening occasion may or may not be continuous in the time domain if it is associated with multiple DRX cycles. The first DRX duration may include a duration within all or part of a DRX cycle associated with the first DCP listening occasion in the first DRX configuration, or alternatively, the first DRX duration may include a duration within all or part of a DRX cycle associated with the first DCP listening occasion on the first set of carriers.

With reference to the second aspect or the first optional implementation manner of the second aspect or the second optional implementation manner of the second aspect, in a third optional implementation manner of the second aspect, the determining by the terminal device whether to monitor the DCP in the first DCP monitoring occasion includes:

In the case that the time domain position of the first DCP monitoring opportunity is located in a first DRX activation time, the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity; or in the case that the time domain position of the first DCP monitoring opportunity is not located or is partially located in the first DRX activation time, the terminal device determines to monitor the DCP in the first DCP monitoring opportunity; the first DRX activation time is a DRX activation time corresponding to the first DRX configuration; or alternatively, the first and second heat exchangers may be,

when the number of the sizes of the DCIs which can be monitored at most is larger than or equal to the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the monitoring opportunity of the first DCP; or under the condition that the number of the sizes of the DCIs which can be monitored at most is smaller than the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines not to monitor the DCP in the monitoring time of the first DCP; or alternatively, the first and second heat exchangers may be,

when the time domain position of the first DCP monitoring opportunity is located in a first DRX activation time and the number of the size of DCI which can be monitored at most is larger than or equal to the number of the size of DCI which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the first DCP monitoring opportunity; or when the time domain position of the first DCP monitoring opportunity is located in a first DRX activation time and the number of the sizes of the DCI that can be monitored at most is smaller than the number of the sizes of the DCI that the terminal device needs to monitor, the terminal device determines that the DCP is not monitored in the first DCP monitoring opportunity; the first DRX activation time is a DRX activation time corresponding to the first DRX configuration.

The terminal device may have different manners of determining whether to monitor the DCP in the first DCP monitoring occasion. For example, the terminal device may determine from the time domain position of the first DCP listening occasion in a manner that is easy for the terminal device to implement and that is also advantageous for compatibility with existing technologies. Alternatively, the terminal device may be determined according to the size budget of the DCI, and this determination is simpler and more reasonable. Or the terminal equipment can also combine the two determination modes to determine, so that the determination result is more accurate. The embodiment of the application provides a plurality of determination modes, and the determination modes can be selected at any time, can be decided by the terminal equipment, or can be configured by the network equipment, or can be defaulted, or can be regulated by a protocol, and the like.

With reference to the first aspect or any one of the first optional implementation manner to the third optional implementation manner of the first aspect, in a fourth optional implementation manner of the first aspect, the method further includes: the terminal device receives configuration information from the network device, wherein the configuration information is used for configuring: in case the terminal device does not listen during a DCP listening occasion, the terminal device wakes up or sleeps during the second DRX duration associated with the DCP listening occasion.

If the terminal device does not listen during a DCP listening occasion on the first set of carriers, the terminal device wakes up or sleeps during the DRX duration associated with the DCP listening occasion, which may be a default rule, or may be specified by a protocol, or may be configured by the network device. If configured by the network device, the network device can be configured according to the service transmission condition of the terminal device on the second group of carriers, so that the dormancy or the awakening of the terminal device on the second group of carriers better meets the service requirement of the terminal device.

With reference to the first aspect or any one of the first optional implementation manner to the fourth optional implementation manner of the first aspect, in a fifth optional implementation manner of the first aspect, the method further includes: in the case that the terminal device determines to monitor a DCP in the first DCP monitoring occasion, the terminal device monitors the DCP in the first DCP monitoring occasion; the terminal device sleeps or wakes up in the first DRX duration on the first group of carriers and sleeps or wakes up in the second DRX duration on the second group of carriers according to the monitoring condition of the DCP.

If the terminal device monitors in the first DCP monitoring occasion, the terminal device sleeps or wakes up on two groups of carriers according to the indication of the DCP monitored in the first DCP monitoring occasion, namely, the monitoring result of the terminal device in the first DCP monitoring occasion can guide the behavior of the terminal device on the two groups of carriers, so that the process of monitoring the DCP by the terminal device is reduced, and the power consumption is saved.

With reference to the fifth optional implementation manner of the first aspect, in a sixth optional implementation manner of the first aspect, the dormancy unit sleeps on the first set of carriers for the first DRX duration and on the second set of carriers for the second DRX duration according to a listening situation on the DCP, including: in the event that the terminal device receives a first DCP from the network device within the first DCP listening occasion and the first DCP indicates sleep, on the first set of carriers, the terminal device sleeps for the first DRX duration and, on the second set of carriers, the terminal device sleeps for the second DRX duration; or, in case the terminal device does not receive a DCP from the network device within the first DCP listening occasion, the terminal device sleeps for the first DRX duration on the first set of carriers and the terminal device sleeps for the second DRX duration on the second set of carriers.

With reference to the fifth optional implementation manner of the first aspect, in a seventh optional implementation manner of the first aspect, the waking up by the terminal device during the first DRX duration on the first set of carriers and during the second DRX duration on the second set of carriers according to a listening situation on a DCP includes: in the case where the terminal device receives a first DCP from the network device within the first DCP listening occasion and the first DCP indicates a wakeup, on the first set of carriers, the terminal device wakes up for the first DRX duration, and on the second set of carriers, the terminal device wakes up for the second DRX duration; or, in case the terminal device receives a first DCP from the network device within the first DCP listening occasion, the terminal device wakes up during the first DRX duration on the first set of carriers, and the terminal device wakes up during the second DRX duration on the second set of carriers.

With reference to the fifth optional implementation manner of the first aspect, in an eighth optional implementation manner of the first aspect, the terminal device sleeps or wakes up on the first set of carriers for the first DRX duration and sleeps or wakes up on the second set of carriers for the second DRX duration according to a listening situation on the DCP, including: receiving a first DCP from the network device in the first DCP monitoring occasion by the terminal device, wherein the first DCP comprises first indication information and second indication information; wherein, when the first indication information indicates wake-up and the second indication information indicates wake-up, on the first set of carriers, the terminal device wakes up within the first DRX duration, and on the second set of carriers, the terminal device wakes up within the second DRX duration; or, in a case where the first indication information indicates sleep and the second indication information indicates sleep, on the first set of carriers, the terminal device sleeps for the first DRX duration and, on the second set of carriers, the terminal device sleeps for the second DRX duration; or, in case the first indication information indicates wake-up and the second indication information indicates sleep, on the first set of carriers, the terminal device wakes up for the first DRX duration and, on the second set of carriers, the terminal device sleeps for the second DRX duration; or, in case the first indication information indicates sleep and the second indication information indicates wake-up, the terminal device sleeps for the first DRX duration on the first set of carriers and the terminal device wakes up for the second DRX duration on the second set of carriers.

With reference to any one of the fifth optional implementation manner to the eighth optional implementation manner of the first aspect, in a ninth optional implementation manner of the first aspect, the terminal device sleeps on the first set of carriers for the first DRX duration, including: the terminal device does not start and does not restart a first DRX duration timer at a starting time of the first DRX duration, the first DRX duration timer corresponding to the first DRX configuration.

With reference to any one of the fifth optional implementation manner to the ninth optional implementation manner of the first aspect, in a tenth optional implementation manner of the first aspect, the terminal device wakes up within the first DRX duration on the first set of carriers, including: and the terminal equipment starts or restarts a first DRX duration timer at the starting moment of the first DRX duration, wherein the first DRX duration timer corresponds to the first DRX configuration.

With reference to any one of the fifth optional implementation manner of the first aspect to the tenth optional implementation manner of the first aspect, in an eleventh optional implementation manner of the first aspect, the terminal device sleeps on the second set of carriers for the second DRX duration, including: the terminal device does not start and does not restart a second DRX duration timer at the starting time of the second DRX duration, where the second DRX duration timer corresponds to the second DRX configuration.

With reference to any one of the fifth optional implementation manner to the eleventh optional implementation manner of the first aspect, in a twelfth optional implementation manner of the first aspect, the terminal device wakes up within the second DRX duration on the second set of carriers, including: and the terminal equipment starts or restarts a second DRX duration timer at the starting moment of the second DRX duration, wherein the second DRX duration timer corresponds to the second DRX configuration.

By the scheme, the terminal device wakes up or sleeps in the DRX duration.

With reference to the first aspect or any one of the first optional implementation manner to the twelfth optional implementation manner of the first aspect, in a thirteenth optional implementation manner of the first aspect, a frequency range to which the first set of carriers belongs is different from a frequency range to which the second set of carriers belongs; or, the frequency corresponding to the frequency range to which the second group of carriers belongs is greater than the frequency corresponding to the frequency range to which the first group of carriers belongs; or the length of the DRX activation time corresponding to the first group of carriers is greater than or equal to the length of the DRX activation time corresponding to the second group of carriers.

For example, the frequency ranges to which the two sets of carriers configured for the terminal device belong are different, thereby enabling the terminal device to operate in a larger frequency range. For example, the frequencies of the first set of carriers belong to FR1 and the frequencies of the second set of carriers belong to FR2. Because the frequency of the second group carrier is greater than that of the first group carrier, the power consumption of the terminal equipment when working on the second group carrier is greater, so the embodiment of the application can ensure that the terminal equipment only needs to monitor the DCP on the first group carrier and does not need to monitor the DCP on the second group carrier, thereby saving the power consumption brought by the terminal equipment when working on the second group carrier. In addition, the network device may transmit DCI on the first set of carriers that is used to schedule data on the second set of carriers, and thus the terminal device may need to receive scheduling information for the second set of carriers on the first set of carriers. Therefore, the length of the DRX activation time corresponding to the first group of carriers is greater than or equal to that of the DRX activation time corresponding to the second group of carriers, and optionally, the DRX activation time corresponding to the first group of carriers can cover the DRX activation time corresponding to the second group of carriers, so that the terminal equipment can receive the scheduling information corresponding to the second group of carriers in the DRX activation time of the first group of carriers, the probability that the terminal equipment cannot receive data or transmit data on the second group of carriers due to the fact that the scheduling information cannot be received is reduced, and service transmission delay is reduced.

In a second aspect, a second communication method is provided, which is executable by a terminal device or by a chip system, which is capable of implementing the functions of the terminal device. The method comprises the following steps: in the case where a terminal device determines not to monitor a DCP within a first DCP monitoring occasion, the terminal device determines whether to monitor the DCP within a second DCP monitoring occasion, the first DCP monitoring occasion configured on a first set of carriers, the second DCP monitoring occasion configured on a second set of carriers, the first set of carriers including one or more carriers configured to the terminal device, the first set of carriers applying a first DRX configuration, the second set of carriers including one or more carriers configured to the terminal device, the second set of carriers applying a second DRX configuration; and under the condition that the terminal equipment determines to monitor the DCP in the second DCP monitoring occasion, the terminal equipment monitors the DCP in the second DCP monitoring occasion and sleeps or wakes up on the second group of carriers in a second DRX duration time associated with the second DCP monitoring occasion according to the monitoring condition of the DCP, wherein the second DRX duration time corresponds to the second DRX configuration.

In the embodiments of the present application, two techniques of DRX configuration can be used in combination with a wake-up signal and prescribe the behavior of the terminal device in case of combination. For example, the UE preferentially listens to the first DCP listening occasion, and if the UE is able to listen to the first DCP listening occasion, the UE does not need to listen to the second DCP listening occasion, so as to save power consumption caused by the UE listening to the DCP listening occasion. If the UE cannot monitor the first DCP monitoring occasion, the UE may also determine whether to monitor the second DCP monitoring occasion, so that the UE acts as far as possible under the indication of the monitoring result, so as to more meet the requirements of the network device. In the embodiment of the application, the network device can configure the second DCP monitoring opportunity for the second group of carriers, so that the network device has stronger control force on the behavior of the UE on the second group of carriers, and the scheduling flexibility of the network device is also increased.

With reference to the second aspect, in a first optional implementation manner of the second aspect, the method further includes: the terminal device determines whether to listen to a DCP within the first DCP listening occasion.

With reference to the second aspect or the first optional implementation manner of the second aspect, in a second optional implementation manner of the second aspect, the method further includes: and in the case that the terminal equipment determines not to monitor the DCP in the second DCP monitoring occasion, the terminal equipment wakes up in the second DRX duration on the second group of carriers.

If the terminal device does not listen to the DCP during the second DCP listening occasion either, the behavior of the terminal device on the second set of carriers may be default or may be specified by the protocol. For example, the terminal device may wake up on a second set of carriers for a second DRX duration for traffic transmission. Alternatively, the terminal device may sleep on the second set of carriers for the second DRX duration to reduce the power consumption of the terminal device.

With reference to the second aspect or the first alternative implementation manner of the second aspect or the second alternative implementation manner of the second aspect, in a third alternative implementation manner of the second aspect, the method further includes: in the case that the terminal device determines to monitor the DCP in the first DCP monitoring occasion, the terminal device sleeps or wakes up on the first group of carriers in a first DRX duration associated with the first DCP monitoring occasion according to the monitoring situation of the DCP, and sleeps or wakes up on the second group of carriers in the second DRX duration, wherein the first DRX duration corresponds to the first DRX configuration.

With reference to the second aspect or any one of the first optional implementation manner to the third optional implementation manner of the second aspect, in a fourth optional implementation manner of the second aspect, the method further includes: in the event that the terminal device determines to monitor DCP during the first DCP monitoring occasion, the terminal device does not monitor during the second DCP monitoring occasion on the second set of carriers.

If the terminal device is able to monitor the DCP during the first DCP listening occasion, the terminal device may determine behavior on the first set of carriers and determine behavior on the second set of carriers based on the indication of the DCP monitored during the first DCP listening occasion. In this case, the terminal device does not need to monitor the second DCP monitoring occasion, so that the power consumption of the terminal device due to the monitoring of the DCP is reduced.

With reference to the second aspect or any one of the first optional implementation manner to the fourth optional implementation manner of the second aspect, in a fifth optional implementation manner of the second aspect, the method further includes: and under the condition that the terminal equipment determines not to monitor the DCP in the first DCP monitoring occasion, on the first group of carriers, the terminal equipment wakes up in a first DRX duration time associated with the first DCP monitoring occasion, wherein the first DRX duration time corresponds to the first DRX configuration.

If the terminal device does not listen to the DCP during the first DCP listening occasion, the behavior of the terminal device on the first set of carriers may be default or may be specified by a protocol. For example, the terminal device wakes up for the first DRX duration for traffic transmission. For another example, the terminal device may also sleep during the first DRX duration to save power consumption of the terminal device.

With reference to the first optional implementation manner of the second aspect, in a sixth optional implementation manner of the second aspect, the determining, by the terminal device, whether to monitor the DCP in the first DCP monitoring opportunity includes: in the case that the time domain position of the first DCP monitoring opportunity is located in a first DRX activation time, the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity; or in the case that the time domain position of the first DCP monitoring opportunity is not located or is partially located in the first DRX activation time, the terminal device determines to monitor the DCP in the first DCP monitoring opportunity; the first DRX activation time is a DRX activation time corresponding to the first DRX configuration; or, in the case that the number of the sizes of the DCIs which can be monitored at most is greater than or equal to the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the first DCP monitoring opportunity; or under the condition that the number of the sizes of the DCIs which can be monitored at most is smaller than the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines not to monitor the DCP in the monitoring time of the first DCP; or when the time domain position of the first DCP monitoring opportunity is located in a first DRX activation time and the number of the size of DCI which can be monitored at most is greater than or equal to the number of the size of DCI which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the first DCP monitoring opportunity; or when the time domain position of the first DCP monitoring opportunity is located in a first DRX activation time and the number of the sizes of the DCI that can be monitored at most is smaller than the number of the sizes of the DCI that the terminal device needs to monitor, the terminal device determines that the DCP is not monitored in the first DCP monitoring opportunity; the first DRX activation time is a DRX activation time corresponding to the first DRX configuration.

With reference to the second aspect or any one of the first optional implementation manner to the sixth optional implementation manner of the second aspect, in a seventh optional implementation manner of the second aspect, the determining, by the terminal device, whether to monitor the DCP in the second DCP monitoring occasion includes: in the case that the time domain position of the second DCP monitoring opportunity is located in a second DRX activation time, the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity; or, in the case that the time domain position of the second DCP monitoring opportunity is not located or is partially located in the second DRX activation time, the terminal device determines to monitor the DCP in the first DCP monitoring opportunity; the second DRX activation time is a DRX activation time corresponding to the second DRX configuration; or, in the case that the number of the sizes of the DCIs which can be monitored at most is greater than or equal to the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the second DCP monitoring opportunity; or under the condition that the number of the sizes of the DCIs which can be monitored at most is smaller than the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines not to monitor the DCP in the second DCP monitoring time; or when the time domain position of the second DCP monitoring opportunity is located in a second DRX activation time and the number of the size of DCI which can be monitored at most is greater than or equal to the number of the size of DCI which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the second DCP monitoring opportunity; or when the time domain position of the second DCP monitoring opportunity is located in the second DRX activation time and the number of the sizes of the DCI that can be monitored at most is smaller than the number of the sizes of the DCI that the terminal device needs to monitor, the terminal device determines that the DCP is not monitored in the second DCP monitoring opportunity.

The terminal device may have different manners of determining whether to monitor the DCP in the second DCP monitoring occasion. For example, the terminal device may determine from the time domain position of the second DCP listening occasion in a manner that is easy for the terminal device to implement and that is also advantageous for compatibility with existing technologies. Alternatively, the terminal device may be determined according to the size budget of the DCI, and this determination is simpler and more reasonable. Or the terminal equipment can also combine the two determination modes to determine, so that the determination result is more accurate. The embodiment of the application provides a plurality of determination modes, and the determination modes can be selected at any time, can be decided by the terminal equipment, or can be configured by the network equipment, or can be defaulted, or can be regulated by a protocol, and the like.

With reference to the second aspect or any one of the first optional implementation manner to the seventh optional implementation manner of the second aspect, in an eighth optional implementation manner of the second aspect, the determining, by the terminal device, not to monitor the DCP in the first DCP monitoring occasion and determining to monitor the DCP in the second DCP monitoring occasion includes: in the case that the time domain position of the first DCP listening occasion is located within a first DRX activation time and the time domain position of the second DCP listening occasion is not located or is partially located within a second DRX activation time, the terminal device determines not to listen to the DCP within the first DCP listening occasion and determines to listen to the DCP within the second DCP listening occasion.

In a third aspect, a third communication method is provided, which may be performed by a terminal device or by a chip system, which is capable of implementing the functionality of the terminal device. The method comprises the following steps: the terminal equipment receives DCI from the network equipment on a first carrier, wherein the first carrier belongs to a first group of carriers, the first group of carriers comprises one or more carriers configured to the terminal equipment, and the first group of carriers apply a first DRX configuration; the terminal equipment determines that the DCI is dormant or wakes up in a second DRX duration time associated with the DCI according to second indication information included in the DCI, the second DRX duration time corresponds to a second DRX configuration, the second group of carriers apply the second DRX configuration, the second group of carriers comprise one or more carriers configured to the terminal equipment, and the second group of carriers are used for indicating that the DCI comprises the second indication information when a value of a second field included in the DCI is a first value.

In the embodiment of the application, two DRX configuration technologies can be combined with a wake-up signal, and the embodiment of the application does not need to configure DCP, but realizes the function of DCP through common DCI, so that the number of DCI size to be monitored by UE is reduced, or the UE can monitor more DCI size, and the realization of network equipment and the UE is simplified. And the network equipment can instruct the UE to wake up or sleep on the carrier group through the corresponding indication information, the indication mode is more flexible, the service transmission requirement of the UE is more met, and the scheduling flexibility of the network equipment is also increased. In addition, the embodiment of the application also avoids the situation that the UE wakes up in the second DRX duration on the second group of carriers by default, and can reduce the power consumption of the UE.

With reference to the third aspect, in a first optional implementation manner of the third aspect, when the value of the second field is a second value, the DCI is used to indicate that the DCI does not include the second indication information.

If the DCP function is DCI, the DCI can be indicated to further comprise second indication information through a second field with a first value, and if the DCI is not DCP function, the second field can be different from the first value, for example, the DCP function is a common value, and the terminal equipment can determine whether the DCI comprises the second indication information according to the value of the second field, so that the indication is clear, and other indication information is not required to be additionally added, thereby being beneficial to being compatible with the existing technology.

With reference to the third aspect or the first optional implementation manner of the third aspect, in a first optional implementation manner of the third aspect, the second field includes one or more of the following fields: FDRA field, MCS field, NDI field, RV field, HARQ process number field, antenna port field, or demodulation reference signal sequence initialization field.

The second field may include one or more fields as above, or the second field may include other fields in addition to the above fields, or the second field may include other fields instead of the above fields. The other fields may be, for example, other existing fields included in the DCI other than the above fields, or may be fields newly added to the DCI.

With reference to the third aspect or the first optional implementation manner of the third aspect or the second optional implementation manner of the third aspect, in a third optional implementation manner of the third aspect, the method further includes: and the terminal equipment determines that the terminal equipment sleeps or wakes up on the first group of carriers within a first DRX duration time associated with the DCI according to first indication information included in the DCI, wherein the first DRX duration time corresponds to the first DRX configuration, and the terminal equipment is further used for indicating that the DCI includes the first indication information when the value of the second field is the first value.

The DCI may further include first indication information if the value of the second field is the first value, and the DCI does not include the first indication information if the value of the second field is not the first value. In this embodiment, the network device indicates sleep or wake-up of the two groups of carriers through the second indication information and the first indication information, so that the UE has a more definite behavior and meets the service requirement.

With reference to the third aspect or the first alternative embodiment of the third aspect or the second alternative embodiment of the third aspect, in a fourth alternative embodiment of the third aspect,

The method further comprises the steps of: the terminal equipment sleeps or wakes up on the first group of carriers within a first DRX duration associated with the DCI, wherein the first DRX duration corresponds to the first DRX configuration;

or alternatively, the first and second heat exchangers may be,

the terminal equipment determines to sleep or wake up on a second group of carriers according to second indication information included in the DCI, and the terminal equipment comprises: when the terminal equipment determines that the DCP is not monitored on the first group of carriers, the terminal equipment determines to sleep or wake up on the second group of carriers according to second indication information included in the DCI and within the second DRX duration time associated with the DCI;

the method further comprises the steps of: the terminal device sleeps or wakes up on the first set of carriers within a first DRX duration associated with the DCI, the first DRX duration corresponding to the first DRX configuration.

The DCI may not indicate the UE's behavior on the first set of carriers, and then may default (or protocol specifies) that the UE wake up on the first set of carriers for a first DRX duration associated with the DCI. Because if the second indication information indicates that the UE wakes up on the second set of carriers for the second DRX duration and the network device needs to schedule data transmission of the UE on the second set of carriers on the first set of carriers, the scheduling information from the network device may not be received if the UE sleeps on the first set of carriers for the first DRX duration, and thus data transmission on the second set of carriers may not be possible. Therefore, the UE may default (or protocol specifies) to sleep on the first set of carriers for the first DRX duration, so as to reduce the probability that the UE misses the scheduling information and reduce the transmission delay of the traffic. Alternatively, the UE may be dormant on the first set of carriers for a first DRX duration associated with the DCI by default (or as specified by the protocol), in which way power consumption of the UE can be saved.

In a fourth aspect, a fourth communication method is provided. The method may be performed by a network device or by a chip system capable of implementing the functions of the network device. Illustratively, the network device is an access network device. The access network device is illustratively a base station. The method comprises the following steps: the network device sends DCI to the terminal device on a first carrier, wherein the first carrier belongs to a first group of carriers, the first group of carriers comprises one or more carriers configured to the terminal device, the first group of carriers apply a first DRX configuration, when a value of a second field included in the DCI is a first value, the first carrier is used for indicating that the DCI comprises second indication information, the second indication information is used for indicating that the DCI sleeps or wakes up on a second group of carriers within a second DRX duration associated with the DCI, the second DRX duration corresponds to a second DRX configuration, the second group of carriers apply the second DRX configuration, and the second group of carriers comprises one or more carriers configured to the terminal device.

With reference to the fourth aspect, in a first optional implementation manner of the fourth aspect, when the value of the second field is a second value, the DCI is used to indicate that the DCI does not include the second indication information.

With reference to the fourth aspect or the first optional implementation manner of the fourth aspect, in a second optional implementation manner of the fourth aspect, the second field includes one or more of the following fields: FDRA field, MCS field, NDI field, RV field, HARQ process number field, antenna port field, or demodulation reference signal sequence initialization field.

With reference to the fourth aspect or the first optional implementation manner of the fourth aspect or the second optional implementation manner of the fourth aspect, in a third optional implementation manner of the fourth aspect, when the value of the second field is the first value, the DCI is further used to indicate that the DCI includes the first indication information, where the first indication information is used to indicate that the DCI is dormant or wakes up on the first set of carriers within a first DRX duration associated with the DCI, where the first DRX duration corresponds to the first DRX configuration.

Regarding the technical effects brought about by the fourth aspect or the various alternative embodiments of the fourth aspect, reference may be made to the description of the technical effects of the third aspect or the corresponding embodiments.

In a fifth aspect, a fifth communication method is provided, which is executable by a terminal device or by a chip system, which is capable of implementing the functions of the terminal device. The method comprises the following steps: the terminal equipment receives second DCI on a first carrier, wherein the first carrier belongs to a first group of carriers, the second DCI is used for scheduling data on a second group of carriers, the first group of carriers apply a first DRX configuration, the second group of carriers apply a second DRX configuration, the first group of carriers comprise one or more carriers configured to the terminal equipment, and the second group of carriers comprise one or more carriers configured to the terminal equipment; and the terminal equipment starts or restarts a second DRX inactivity timer, and sets the duration of the second DRX inactivity timer as the duration of the DRX inactivity timer configured by the second DRX configuration.

In the embodiment of the present application, two techniques of DRX configuration can be used in combination with a cross-carrier scheduling technique, and when implementing cross-carrier scheduling, the UE can receive DCI from the network device on a first set of carriers for scheduling data on a second set of carriers, and the UE can also receive data or send data on the second set of carriers, so that the cross-carrier scheduling technique is implemented in the context of the two DRX configuration techniques. In addition, according to the embodiment of the application, the duration of the first DRX inactivity timer corresponding to the first group of carriers can be set to be different durations according to different conditions, so that the duration of the first DRX inactivity timer meets the current service transmission requirement more and the power consumption of the UE is saved more.

With reference to the fifth aspect, in a first optional implementation manner of the fifth aspect, the starting or restarting, by the terminal device, the second DRX inactivity timer includes: and the terminal equipment starts or restarts the second DRX inactivity timer at the first time domain symbol after the second DCI is received.

The time domain symbols are, for example, orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) symbols.

With reference to the fifth aspect or the first optional implementation manner of the fifth aspect, in a second optional implementation manner of the fifth aspect, the second DCI includes second indication information, where the second indication information is used to indicate to start or restart the second DRX inactivity timer.

The second indication information may be carried through an existing field in the second DCI, for example, if there is a reserved bit in an existing field included in the second DCI, the second indication information may be carried through the reserved bit; alternatively, one or more bits may be newly added to the second DCI to carry the second indication information. And the indication is carried out through the second DCI, so that the UE is more clear of the behavior of the UE.

With reference to the fifth aspect or the first optional implementation manner of the fifth aspect or the second optional implementation manner of the fifth aspect, in a third optional implementation manner of the fifth aspect, after the terminal device receives the second DCI on the first carrier, the method further includes: the terminal equipment starts or restarts a first DRX inactivity timer, and sets the duration of the first DRX inactivity timer as the duration of the DRX inactivity timer configured by the first DRX configuration or as the duration of the DRX inactivity timer configured by the second DRX configuration, wherein the first DRX inactivity timer corresponds to the first DRX configuration.

Since there is data transmission on the second set of carriers and the second DCI is cross-carrier scheduling, it is also possible for the subsequent network device to schedule data on the second set of carriers by means of cross-carrier scheduling. In addition, the network device may also schedule data on the first set of carriers. Accordingly, the DRX activation time of the UE on the first set of carriers may be prolonged to receive DCI for scheduling data. The UE may extend the DRX activation time of the UE on the first set of carriers by a first DRX inactivity timer. For example, the UE may set the duration of the first DRX inactivity timer to the original duration of the first DRX inactivity timer, i.e., the duration of the DRX inactivity timer configured by the first DRX configuration. The setting mode is simpler and is easy to realize by the UE. For another example, the UE may also set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration, which may be understood that the UE sets the duration of the first DRX inactivity timer to the duration of the second DRX inactivity timer. If this is done, the duration of the DRX activation time of the UE on the first set of carriers may be consistent with the duration of the DRX activation time of the UE on the second set of carriers, and the UE may not receive DCI on the first set of carriers for scheduling data for the second set of carriers nor cause excessive power consumption due to excessive DRX activation time on the first set of carriers.

With reference to the third optional implementation manner of the fifth aspect, in a fourth optional implementation manner of the fifth aspect, in a case where the terminal device sets a duration of the first DRX inactivity timer to a duration of a DRX inactivity timer configured by the second DRX configuration, the method further includes: before restarting the first DRX inactivity timer, the terminal equipment determines that the first DRX inactivity timer is in an operating state, and determines that the residual duration of the first DRX inactivity timer is shorter than the duration of the DRX inactivity timer configured by the second DRX configuration.

The UE may not have to start or restart the first DRX inactivity timer in any case, but may first determine whether the first DRX inactivity timer needs to be started or restarted. For example, before starting or restarting the first DRX inactivity timer, the UE may determine a size relationship between a remaining duration of the first DRX inactivity timer and a duration of the DRX inactivity timer configured by the second DRX configuration if the first DRX inactivity timer is in an active state. If the remaining duration of the first DRX inactivity timer is shorter than the duration of the DRX inactivity timer configured by the second DRX configuration, the UE may set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration; alternatively, the UE may not have to restart the first DRX inactivity timer if the remaining duration of the first DRX inactivity timer is longer than or equal to the duration of the DRX inactivity timer configured by the second DRX configuration. In this way, the duration of the first DRX inactivity timer is prevented from being neglected and shortened, and the complexity of UE processing is reduced.

With reference to the third optional implementation manner of the fifth aspect, in a fifth optional implementation manner of the fifth aspect, before the terminal device starts or restarts a first DRX inactivity timer and sets a duration of the first DRX inactivity timer to a duration of a DRX inactivity timer configured by the first DRX configuration, the method further includes: the terminal device receives a first DCI on the first set of carriers, the first DCI being used to schedule data on the first set of carriers.

If the UE receives the first DCI on the first set of carriers before starting or restarting the first DRX inactivity timer, and the first DCI is used to schedule the UE to receive data or transmit data on the first set of carriers, the UE may set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the first DRX configuration to meet the requirement of the UE to receive data or transmit data on the first set of carriers, and also to meet the requirement of the UE to receive scheduling of data corresponding to the first set of carriers on the first set of carriers.

With reference to the third optional implementation manner of the fifth aspect, in a sixth optional implementation manner of the fifth aspect, the second DCI includes first indication information, where the first indication information is used to indicate starting or restarting the first DRX inactivity timer.

Whether the UE is to start the first DRX inactivity timer may be by default, or specified by a protocol, or may also be indicated by the network device. For example, the second DCI may include first indication information, which may indicate to start or restart the first DRX inactivity timer. And the indication is carried out through the second DCI, so that the UE is more clear of the behavior of the UE.

With reference to the sixth optional implementation manner of the fifth aspect, in a seventh optional implementation manner of the fifth aspect, the first indication information is further used to indicate setting a timing duration of the first DRX inactivity timer to a duration of a DRX inactivity timer configured by the first DRX configuration, or to indicate setting a timing duration of the first DRX inactivity timer to a duration of a DRX inactivity timer configured by the second DRX configuration.

If the second DCI includes the first indication information, the first indication information may indicate how to set a duration of the first DRX inactivity timer in addition to the UE starting or restarting the first DRX inactivity timer. The UE does not need to determine how the duration of the first DRX inactivity timer should be set by itself, simplifying the implementation of the UE.

With reference to the fifth aspect or the first optional implementation manner of the fifth aspect or the second optional implementation manner of the fifth aspect, in an eighth optional implementation manner of the fifth aspect, the method further includes: and the terminal equipment prolongs the ending time of the DRX activation time of the terminal equipment on the first group of carriers to be the same as the ending time of the DRX activation time of the terminal equipment on the second group of carriers.

The UE may extend the DRX activation time of the UE on the first set of carriers, one implementation by the first DRX inactivity timer, while another implementation may directly extend the end time of the DRX activation time on the first set of carriers without the first DRX inactivity timer, e.g., extend the end time of the DRX activation time of the UE on the first set of carriers to the same end time of the DRX activation time of the UE on the second set of carriers. In this way, the duration of the DRX activation time of the UE on the first set of carriers is consistent with the duration of the DRX activation time of the UE on the second set of carriers, and the UE can receive DCI on the first set of carriers for scheduling data of the second set of carriers, nor can it consume too much power due to too much DRX activation time on the first set of carriers. And the mode also does not need to resort to the first DRX inactivity time timer, so that the power consumption caused by the maintenance of the first DRX inactivity time timer by the UE is reduced.

With reference to the fifth aspect or the first optional implementation manner of the fifth aspect to the eighth optional implementation manner of the fifth aspect, in a ninth optional implementation manner of the fifth aspect, the second DCI is used to indicate a new transmission of downlink data or a new transmission of uplink data.

In a sixth aspect, a communication device is provided. The communication device may comprise means for performing the method of the first aspect or any alternative implementation of the first aspect, e.g. comprising a transceiver unit and a processing unit. Optionally, a storage unit may be further included.

In a seventh aspect, a communication device is provided. The communication device may comprise means for performing the method of the second aspect or any alternative implementation of the second aspect, e.g. comprising a transceiver unit and a processing unit. Optionally, a storage unit may be further included.

In an eighth aspect, a communication device is provided. The communication device may comprise means for performing the method of the third aspect or any alternative embodiment of the third aspect, e.g. comprising a transceiver unit and a processing unit. Optionally, a storage unit may be further included.

In a ninth aspect, a communication apparatus is provided. The communication device may comprise means for performing the method of the fourth aspect or any alternative implementation of the fourth aspect, e.g. comprising a transceiver unit and a processing unit. Optionally, a storage unit may be further included.

In a tenth aspect, a communication device is provided. The communication device may comprise means for performing the method of the fifth aspect or any alternative implementation of the fifth aspect, e.g. comprising a transceiver unit and a processing unit. Optionally, a storage unit may be further included.

In an eleventh aspect, there is provided a chip system comprising one or more processors and a communication interface, the processors being coupled to the communication interface for implementing the method provided in any of the above aspects. Optionally, the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the method provided in any one of the above aspects.

In a twelfth aspect, a first communication system is provided. The first communication system comprises a communication device according to the sixth aspect or a chip system according to the eleventh aspect (for implementing the method provided by any of the alternative embodiments of the first aspect or the first aspect described above).

In a thirteenth aspect, a second communication system is provided. The second communication system comprises the communication device of the seventh aspect or the system-on-chip of the eleventh aspect (for implementing the method provided by the second aspect or any of the optional embodiments of the second aspect).

In a fourteenth aspect, a third communication system is provided. The second communication system includes a communication device according to the eighth aspect or a chip system according to the eleventh aspect (for implementing the method provided by any of the optional embodiments of the third aspect or the third aspect) and includes a communication device according to the ninth aspect or a chip system according to the eleventh aspect (for implementing the method provided by any of the optional embodiments of the fourth aspect or the fourth aspect).

In a fifteenth aspect, a fourth communication system is provided. The second communication system comprises the communication device of the tenth aspect or the system on chip of the eleventh aspect (for implementing the method provided by the fifth aspect or any optional implementation of the fifth aspect).

In a sixteenth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method provided in any one of the above aspects.

In a seventeenth aspect, there is provided a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method provided in any of the above aspects.

Drawings

FIG. 1 is a schematic diagram of a DRX mechanism;

fig. 2 is a schematic diagram of a time domain position of a DCP;

FIG. 3 is a schematic diagram of two sets of DRX configurations;

fig. 4 is a schematic diagram of an application scenario in an embodiment of the present application;

fig. 5 is a flowchart of a first communication method provided in an embodiment of the present application;

fig. 6 is a schematic diagram of a UE's behavior on two groups of carriers determined by a monitoring result of the UE at a first DCP monitoring occasion in the embodiment of the present application;

fig. 7 is a schematic diagram of cross-carrier scheduling of a network device in an embodiment of the present application;

fig. 8 is a flowchart of a second communication method provided in an embodiment of the present application;

fig. 9 is a schematic diagram of a case where a monitoring result of a UE at a first DCP monitoring occasion in the embodiment of the present application can determine a behavior of the UE on a first group of carriers, and a monitoring result of the UE at a second DCP monitoring occasion can determine a behavior of the UE on a second group of carriers;

fig. 10 is a flowchart of a third communication method provided in an embodiment of the present application;

fig. 11 is a schematic diagram showing that DCI received by a UE on a first set of carriers in an embodiment of the present application can indicate sleep or wake-up of the UE on two sets of carriers;

fig. 12 is a flowchart of a fourth communication method provided in an embodiment of the present application;

Fig. 13 is a schematic diagram of a time period of a first DRX inactivity timer being longer than a time period of a second DRX inactivity timer in an embodiment of the present application;

fig. 14 is a schematic diagram of setting a duration of a first DRX inactivity timer to a duration of a DRX inactivity timer configured by a second DRX configuration in an embodiment of the present application;

fig. 15 is a schematic diagram of extending DRX activation time of a UE on a first set of carriers in an embodiment of the present application;

FIG. 16 is a schematic block diagram of a communication device provided in an embodiment of the present application;

fig. 17 is a schematic block diagram of yet another communication apparatus provided in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

In the following, some terms in the embodiments of the present application are explained for easy understanding by those skilled in the art.

In this embodiment of the present application, the terminal device is a device with a wireless transceiver function, and may be a fixed device, a mobile device, a handheld device, a wearable device, a vehicle-mounted device, or a wireless apparatus (for example, a communication module or a chip system) that is built in the above device. The terminal device is used for connecting people, objects, machines and the like, and can be widely used in various scenes, including but not limited to the following scenes: cellular communication, device-to-device (D2D), vehicle-to-everything (vehicle to everything, V2X), machine-to-machine/machine-to-machine-type communications, M2M/MTC), internet of things (internet of things, ioT), virtual Reality (VR), augmented reality (augmented reality, AR), industrial control (industrial control), unmanned driving (self driving), remote medical (remote media), smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation, smart city (smart city), drone, robot, and other end devices. The terminal device may sometimes be referred to as a UE, a terminal, an access station, a UE station, a remote station, a wireless communication device, or a user equipment, etc., and for convenience of description, the terminal device will be described in the embodiment of the present application by taking the UE as an example.

The network device in the embodiment of the application comprises an access network device and/or a core network device, for example. The access network equipment is equipment with a wireless receiving and transmitting function and is used for communicating with the terminal equipment. The access network device includes, but is not limited to, a base station (BTS, node B, eNodeB/eNB, or gndeb/gNB) in the above communication system, a transceiver point (transmission reception point, TRP), a base station for a subsequent evolution of the third generation partnership project (3rd generation partnership project,3GPP), an access Node in a WiFi system, a wireless relay Node, a wireless backhaul Node, and the like. The base station may be: macro base station, micro base station, pico base station, small station, relay station, etc. Multiple base stations may support networks of the same access technology as mentioned above, or may support networks of different access technologies as mentioned above. A base station may comprise one or more co-sited or non-co-sited transmission reception points. The network devices may also be wireless controllers, centralized Units (CUs), and/or Distributed Units (DUs) in the context of a cloud wireless access network (cloud radio access network, CRAN). The network device may also be a server, a wearable device, or an in-vehicle device, etc. For example, the network device in the vehicle-to-everything (vehicle to everything, V2X) technology may be a Road Side Unit (RSU). An access network device will be described below taking a base station as an example. The plurality of network devices in the communication system may be the same type of base station or different types of base stations. The base station may communicate with the terminal device or may communicate with the terminal device through the relay station. A terminal device may communicate with multiple base stations in different access technologies. The core network device is used for realizing the functions of mobile management, data processing, session management, policy and charging, etc. The names of devices implementing the core network function in the systems of different access technologies may be different, and this application is not limited thereto. Taking the 5G system as an example, the core network device may include access and mobility management functions (access and mobility management function, AMF), session management functions (session management function, SMF), or user plane functions (user plane function, UPF), etc. Taking the 4G system as an example, the core network device may comprise a mobility management entity (mobility management entity) or the like.

In the embodiment of the present application, the means for implementing the function of the network device may be the network device, or may be a means capable of supporting the network device to implement the function, for example, a chip system, and the apparatus may be installed in the network device. In the technical solution provided in the embodiments of the present application, the device for implementing the function of the network device is exemplified by the network device, and the technical solution provided in the embodiments of the present application is described.

In addition, since the embodiments of the present application relate more to access network devices, the "network devices" described below refer to access network devices unless otherwise specified.

In the embodiments of the present application, the number of nouns, unless otherwise indicated, means "a singular noun or a plural noun", i.e. "one or more". "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. For example, A/B, means: a or B. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c, represents: a, b, c, a and b, a and c, b and c, or a and b and c, wherein a, b, c may be single or plural.

And, unless otherwise indicated, the terms "first," "second," and the like in the embodiments herein are used for distinguishing between multiple objects and are not used for limiting the size, content, order, timing, priority, importance, or the like of the multiple objects. For example, the first DCI and the second DCI may be the same DCI or different DCIs, and the names do not indicate the difference in time length, transmission order, content, priority, importance, or the like between these two DCIs.

In order to better understand the technical solutions of the embodiments of the present application, some technical features related to the embodiments of the present application are described below.

1、DRX。

The 5G New Radio (NR) technology has adopted a discontinuous reception (Discontinuous Reception, DRX) mechanism in long term evolution (long term evolution, LTE), which is mainly introduced to save power consumption. The DRX cycle configured by the base station for the UE may be a long DRX cycle or a short DRX cycle, where the long DRX cycle is a default configuration and the short DRX cycle is an optional configuration. If one UE is configured with a long DRX cycle and is not configured with a short DRX cycle, the UE may use the long DRX cycle or use the short DRX cycle at the same time, i.e., the UE may not use both DRX cycles at the same time. The UE may start a DRX short cycle timer (DRX-short cycle timer) when using the short DRX cycle, and when DRX-short cycle timer times out, the UE implicitly transitions to using the long DRX cycle. The unit of the DRX-short cycle timer is the number of short DRX cycles.

The DRX cycle consists of an "On Duration" part and a "DRX occasion (Opportunity for DRX)" part. During the "On Duration" time, the UE listens (monitor) and receives the PDCCH, and during the "Opportunity for DRX" time, the UE may not listen or receive the PDCCH to reduce power consumption, for which reference may be made to fig. 1. The PDCCH is monitored and received, which can be understood as monitoring and receiving DCI carried on the PDCCH. The DRX mechanism includes a DRX Duration timer (DRX-onduration timer) that the UE needs to turn On at the beginning of each DRX cycle (i.e., on Duration of each DRX cycle). When the DRX-onduration timer times out, it indicates that the "On Duration" time ends, and the UE enters the "Opportunity for DRX" time in the DRX cycle.

The DRX mechanism further includes a DRX inactivity timer (DRX-inactivity timer), when the UE receives a PDCCH for indicating data initial transmission (new transmission), since the UE is likely to continue to be scheduled by the base station in the next time, the UE needs to turn on the DRX-inactivity timer, and during the DRX-inactivity timer running time, the UE needs to monitor and receive the PDCCH.

The DRX mechanism also comprises a DRX retransmission timer (DRX-retransmission timer), and the DRX-retransmission timer is specifically divided into an uplink DRX-retransmission timer and a downlink DRX-retransmission timer. Since the base station may schedule retransmission of the UE in the drx-retransmission timer run time, the UE needs to monitor and receive the PDCCH in the drx-retransmission timer run time.

To sum up, the UE needs to monitor and receive the PDCCH during the operation of DRX-onDurationTimer, DRX-incavitytimer, uplink DRX-retransmission timer, and downlink DRX-retransmission timer, and thus the operation time of these timers is considered as DRX "active time", during which the UE needs to wake up to receive signaling or data. However, if the timer is not running at a certain time except for the running time of all the timers, the UE may not need to monitor and receive the PDCCH at the certain time, and this time is called as DRX "sleep time", during which the UE may sleep. In general, the power consumption of a UE at DRX "active time" is higher than at DRX "sleep time". It should be noted that in some other functions than the DRX mechanism, it may be defined that in some cases the UE needs to be in an "active time" or "sleep time", which does not conflict with the DRX mechanism, but takes the union relationship. Thus, whether the UE is ultimately actually at "active time" or "sleep time" needs to be determined entirely from the various functions of the UE.

2. Carrier aggregation (carrier aggregation, CA) and cross-carrier scheduling (cross-carrier scheduling).

The carrier aggregation technology can aggregate a plurality of (e.g., two or more) member carriers (component carrier, CC) together, thereby realizing the effects of increasing transmission bandwidth and improving uplink and downlink transmission rate. In the carrier aggregation scenario, one primary carrier is included in the multiple CCs, and one or more secondary carriers are included. The primary carrier is a carrier operated by a primary cell (PCell), and the secondary carrier is a carrier operated by a secondary cell (SCell). After the UE accesses the network, the UE will keep communication on the primary carrier under one base station all the time, and the base station may add one or more secondary carriers to the UE according to the service condition.

The frequency range of 5G NR includes FR1 and FR2.FR1 is a so-called 5G Sub-6GHz (below 6 GHz) band, and FR2 is a band greater than or equal to 6GHz, for example, the 5G millimeter wave band. One carrier configured for the UE may belong to the FR1 band or the FR2 band, so there is a CA scenario of FR1+fr2, that is, there is at least one FR2 CC and FR1 CC for carrier aggregation.

In the carrier aggregation scenario, there are co-carrier scheduling and cross-carrier scheduling. The base station schedules the UE to receive data or transmit data by transmitting DCI on the PDCCH, i.e., indicates a physical downlink shared channel (physical downlink shared channel, PDSCH) for scheduling data reception in the DCI or indicates a physical uplink shared channel (physical uplink shared channel, PUSCH) for scheduling data transmission in the DCI. If the carrier for receiving DCI and the carrier for receiving (or transmitting) data are the same carrier, the same carrier is scheduled; if the carrier receiving DCI and the carrier receiving (or transmitting) data are different carriers, i.e. cross-carrier scheduling. For the CA scenario of FR1+ FR2, FR2 may be cross-carrier scheduled by FR1, i.e., receiving DCI on the FR1 carrier, which schedules receiving data or transmitting data on the FR2 carrier.

3. A wake-up signal.

In the 5G technology, the UE needs to further save power consumption. For the current DRX mechanism, the UE needs to monitor and receive the PDCCH during the DRX activation time, but in many cases, the UE cannot actually monitor the PDCCH for scheduling the UE during the DRX activation time, and the UE simply consumes the power consumption of monitoring the PDCCH. It is therefore proposed to introduce an indication signal (PDCCH-WUS), alternatively called wake-up signal, which can indicate whether the UE needs to wake-up or whether it can sleep during a subsequent DRX activation time based on the current DRX mechanism. The PDCCH-WUS is also referred to as DCP in the standard, and the signal form of the DCP may be DCI. The time domain position of the DCP may be: the position of an offset (offset) before the "On Duration" time of the DRX cycle can be referred to for this purpose in fig. 2, with the vertical line bolded in fig. 2 representing the DCP. In the carrier aggregation scenario, the DCP is configured only on the primary carrier, but the wakeup or sleep indicated by the DCP may be applied to all carriers participating in carrier aggregation.

It should be noted that in the embodiments of the present application, the terms "carrier" and "cell" may be considered as the same concept, and may be interchanged, without considering the supplementary uplink (supplementary uplink, SUL,). For example, the primary carrier may also be referred to as a primary serving cell, or as a primary cell; the secondary carrier may also be referred to as a secondary serving cell, or as a secondary cell.

4. Two sets of DRX.

Currently, a UE in RRC connected state may support two sets of DRX configurations. All carriers configured using the first set of DRX belong to one Frequency Range (FR), e.g. FR1, and all carriers configured using the second set of DRX belong to another frequency range, e.g. FR2. The first set of DRX configurations may be considered primary (primary) configurations and the second set of DRX configurations may be considered secondary (secondary) configurations. The second set of DRX configurations may be configured with a shorter timing duration of DRX-onduration timer and DRX-Inactigytimer than the first set of DRX configurations, for example, see FIG. 3. In fig. 3, a dotted line box indicates the duration of the DRX inactivity time timer. The two sets of DRX configurations can be understood to be maintained and operated independently, and the carriers belonging to the first frequency range commonly use the first set of DRX configurations to maintain DRX-onduration timer1 and DRX-InactivityTimer1; the carriers belonging to the second frequency range commonly use the second set of DRX configurations, maintaining DRX-onduration timer2 and DRX-incarvitytimer 2. Alternatively, other parameters configured by the first DRX configuration may be the same as corresponding parameters configured by the second DRX configuration, except for DRX-onduration timer and DRX-incarvitytimer. For example, carriers belonging to the first frequency range commonly use the first set of DRX configurations, maintain DRX-retransmission timer1, carriers belonging to the first frequency range commonly use the second set of DRX configurations, maintain DRX-retransmission timer2, and the duration of DRX-retransmission timer1 and DRX-retransmission timer2 may be the same.

Several techniques such as cross-carrier scheduling, wake-up signals, and two sets of DRX configurations, as described above, are currently used alone and are not used in combination. For example, two sets of DRX configurations are used in combination with wake-up signals, or two sets of DRX configurations are used in combination with cross-carrier scheduling, etc., which are not currently supported and affect the flexibility of the base station configuration. In addition, the two sets of DRX configurations are adopted mainly for reducing the power consumption of the UE on the carrier (such as FR 2) corresponding to the second set of DRX configurations, and the cross-carrier scheduling or wake-up signal is helpful to reduce the power consumption of the UE, if the two sets of DRX configurations can be used in combination with the technologies, the power consumption of the UE can be further reduced.

In view of this, a technical solution of the embodiments of the present application is provided. In the embodiment of the present application, two techniques of DRX configuration can be used in combination with a wake-up signal, and specify the behavior of the terminal device in the case of combination, for example, the terminal device monitors the DCP monitoring occasion corresponding to the first set of carriers, which is applicable to both the first set of carriers and the second set of carriers. In this way, the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, so that the power consumption of the terminal equipment for monitoring the DCP is reduced, and the scheduling flexibility of the network equipment is also improved. And the monitoring condition of the terminal equipment on one group of carriers can be suitable for two groups of carriers, so that the DCP mechanism can be used by both groups of carriers, and the power consumption of the terminal equipment on the two groups of carriers can be further reduced.

The technical solution provided in the embodiments of the present application may be applied to a 4G system, for example, an LTE system, or may be applied to a 5G system, for example, an NR system, or may also be applied to a next generation mobile communication system or other similar communication systems, which is not specifically limited. For example, when a terminal device (such as a smart phone, a smart watch, or a smart bracelet) has a power saving requirement, for example, the power of the mobile phone is already lower than 20%, the mobile phone has a very strong requirement of saving power consumption. In this case, after the method provided by the embodiment of the application is adopted, the power consumption of the terminal equipment can be further reduced, namely, the consumed battery power is reduced, and the standby time of the terminal equipment is prolonged.

Fig. 4 is an application scenario of the embodiment of the present application. Fig. 4 includes an access network device, a core network device, and a UE for which the access network device may configure one or more carriers. The access network device operates, for example, in an evolved universal mobile telecommunications system terrestrial radio access (evolved UMTS terrestrial radio access, E-UTRA) system, or in an NR system, or in a next generation or other communication system. The access network device is for example a base station. The access network device corresponds to different devices in different systems, for example, may correspond to an eNB in a 4G system, and corresponds to an access network device in 5G in a 5G system, for example, a gNB. Of course, the technical solution provided in the embodiment of the present application may also be applied to a future mobile communication system, so that the access network device in fig. 4 may also correspond to a network device in a future mobile communication system. Fig. 4 illustrates an example in which the access network device is a base station, and actually, referring to the foregoing description, the access network device may also be an RSU or the like. In addition, the UE in fig. 4 is taken as an example of a mobile phone, and in fact, as can be seen from the foregoing description of the UE, the UE in the embodiments of the present application is not limited to the mobile phone.

In addition, for convenience of description, various embodiments to be described later are exemplified as an architecture applied to fig. 4. For example, the network device described in the following embodiments is, for example, an access network device in the network architecture shown in fig. 4, and the UE described in the following embodiments may be a UE in the network architecture shown in fig. 4.

The method provided by the embodiments of the present application is described below with reference to the accompanying drawings. In the drawings corresponding to the embodiments of the present application, all steps indicated by dotted lines are optional steps.

An embodiment of the present application provides a first communication method, please refer to fig. 5, which is a flowchart of the method.

S51, the UE determines whether to monitor the DCP in the first DCP monitoring occasion, or the UE determines whether to monitor in the first DCP monitoring occasion.

For example, the network device sends the first DRX configuration and the second DRX configuration to the UE, which is then equivalent to being configured with the first DRX configuration and the second DRX configuration. For example, the network device may send the first DRX configuration and the second DRX configuration to the UE through one message, or the network device may send the first DRX configuration and the second DRX configuration to the UE through different messages, respectively. Wherein the first set of carriers applies a first DRX configuration, the second set of carriers applies a second DRX configuration, the first set of carriers comprises one or more carriers configured by the UE, and the second set of carriers also comprises one or more carriers configured by the UE. The first DRX configuration may configure a DRX cycle, a DRX duration timer, a DRX inactivity timer, a DRX retransmission timer, etc., and the second DRX configuration may also configure a DRX cycle, a DRX inactivity timer, a DRX retransmission timer, etc. The first DRX configuration and the second DRX configuration are different DRX configurations, e.g., the first DRX configuration configured DRX duration timer is different from the second DRX configuration configured DRX duration timer, e.g., in that the duration (or timing duration) of the first DRX configuration configured DRX duration timer is different from the duration of the second DRX configuration configured DRX duration timer. For another example, the DRX inactivity timer configured by the first DRX configuration is different from the DRX inactivity timer configured by the second DRX configuration, e.g., in that the duration (or referred to as the timing duration) of the DRX inactivity timer configured by the first DRX configuration is different from the duration of the DRX inactivity timer configured by the second DRX configuration. The other content than the DRX duration timer and the DRX inactivity timer, such as the DRX cycle or the DRX retransmission timer, configured by the first DRX configuration and the second DRX configuration may be the same or different.

For example, the first set of carriers belongs to a first frequency range and the second set of carriers belongs to a second frequency range, which may be different frequency ranges. As an alternative embodiment, for example, the frequency of the second frequency range is greater than the frequency of the first frequency range, for which purpose it is understood that the minimum frequency comprised by the second frequency range is greater than the maximum frequency comprised by the first frequency range, for example the first frequency range is FR1 and the second frequency range is FR2. In practice the network device may not distinguish which carrier belongs to which packet when configuring the carrier for the UE, i.e. the concept of "first group" and "second group" may not exist. The description of the "first set of carriers" and the "second set of carriers" is used herein to distinguish between carriers using different DRX configurations.

The first DCP listening occasion is a DCP listening occasion configured on a first set of carriers, the first DCP listening occasion applying a first DRX configuration. In the first DRX configuration, there are multiple On Duration times, and the DCP listening occasion may also occur multiple times, for example, one DCP listening occasion before each DRX cycle begins. The first DCP listening occasion is then, for example, the current listening occasion for the UE, e.g. the first DCP listening occasion is located before the start of the On Duration time of one DRX cycle in the first DRX configuration, or the first DCP listening occasion is located before the start of the On Duration time of one DRX cycle On the first set of carriers. The first DCP listening occasion may comprise one or more DCP listening occasions, it being understood that a DCP listening occasion may comprise one or more DCP listening occasions, and the first DCP listening occasion is a DCP listening occasion.

In the embodiment of the present application, the network device may send the DCP on a first carrier, where the first carrier belongs to the first group of carriers. For example, the network device configures a DCP for one or more carriers included in the first set of carriers, and the first carrier includes the one or more carriers. For another example, if the main carrier configured by the network device for the UE belongs to the first group of carriers, the network device may configure the DCP for the main carrier, and if the first carrier is the main carrier of the UE, the network device may send the DCP on the main carrier, without configuring the DCP on other carriers, so as to save transmission overhead. If the UE needs to monitor on the first set of carriers, it may monitor on all the carriers comprised by the first set of carriers, or the network device may be preconfigured on which carriers to send the DCP, the UE only needs to monitor on these carriers. The network device does not configure the DCP for the second set of carriers, so the network device does not have to transmit the DCP on the second set of carriers nor does the UE have to monitor the DCP on the second set of carriers.

The UE determines whether to listen in the first DCP listening occasion in a number of ways, as described by way of example below.

The first determination mode is as follows: and determining according to the time domain position of the first DCP monitoring occasion.

For example, the UE determines whether the time domain location of the first DCP listening occasion is within the first DRX activation time, and if the time domain location of the first DCP listening occasion is within the first DRX activation time, it indicates that the UE may have data to transmit on the first set of carriers within the first DCP listening occasion (e.g., the UE needs to receive data or transmit data on the first set of carriers), in which case the UE may not listen on the first DCP listening occasion, but may wake up on the first set of carriers for the DRX duration associated with the first DCP listening occasion.

Or if all time domain positions corresponding to the first DCP monitoring opportunity are not located in the first DRX activation time, the UE may monitor at the first DCP monitoring opportunity. All time domain positions corresponding to the first DCP listening occasion include time domain positions of all DCP listening occasions included in the first DCP listening occasion. At this time, the UE may listen within all DCP listening opportunities included in the first DCP listening opportunity.

Or if the partial time domain position corresponding to the first DCP monitoring opportunity is not located in the first DRX activation time, the UE may not monitor in the DCP monitoring opportunity included in the first DCP monitoring opportunity and located in the first DRX activation time, and for the DCP monitoring opportunity included in the first DCP monitoring opportunity and not located in the first DRX activation time, the UE may still monitor. That is, in this case, the UE does not monitor in a portion of the DCP monitoring occasions included in the first DCP monitoring occasion, but monitors in the remaining DCP monitoring occasions included in the first DCP monitoring occasion, and thus this case can also be regarded as the UE monitoring in the first DCP monitoring occasion. And the time domain positions of the part of the DCP monitoring opportunities included in the first DCP monitoring opportunities are included in the part of the time domain positions of the first DCP monitoring opportunities corresponding to the first DCP monitoring opportunities. The first DRX activation time is a DRX activation time corresponding to the first DRX configuration, where the first DRX activation time is located on the first set of carriers.

This manner of determination is easier for the UE to implement.

The second determination mode: determined from a DCI size budget (DCI size).

For a UE, there is a DCI size budget, i.e., there is a limit to the number of DCI sizes that the UE can monitor at most. For example, if the number of DCI sizes that the UE can monitor is set to be 4 at most, the UE can monitor DCI of 4 kinds of sizes, and if DCI of the fifth size is available, the UE cannot monitor. DCP is considered as a size DCI. And the UE needs to monitor DCI of how many kinds of size, which can be configured by the network device to the UE, the UE can determine whether to monitor the DCP in the first DCP monitoring opportunity according to the number of DCI sizes that can be monitored at most and the number of DCI sizes that the UE needs to monitor.

For example, if the DCP is not considered as DCI that the UE needs to monitor, then if the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor, then the UE can monitor in the first DCP monitoring opportunity, since even if the UE monitors the DCP, the requirement of the DCI size budget can be met at this time. If the number of DCI sizes that the UE can monitor is less than or equal to the number of DCI sizes that the UE needs to monitor, the UE may not monitor in the first DCP monitoring opportunity, because if the UE monitors the DCP, the DCI size budget is exceeded at this time, which may cause an error in the monitoring behavior of the UE. For example, if the number of DCI sizes that the UE can monitor is 4 at most, the number of DCI sizes that the UE needs to monitor is 3, and the DCI that the UE needs to monitor does not include DCP, then the UE can monitor the DCP in the first DCP monitoring opportunity; or, if the number of DCI sizes that the UE can monitor is 4 at most and the number of DCI sizes that the UE needs to monitor is 4, the UE does not monitor the DCP in the first DCP monitoring opportunity.

Alternatively, if the DCP is considered as DCI that the UE needs to monitor, then if the number of DCI sizes that the UE can monitor at most is greater than or equal to the number of DCI sizes that the UE needs to monitor, then the UE can monitor in the first DCP monitoring occasion, and if the number of DCI sizes that the UE can monitor at most is less than the number of DCI sizes that the UE needs to monitor, then the UE can not monitor in the first DCP monitoring occasion. For example, if the number of DCI sizes that the UE can monitor is 4 at most, the number of DCI sizes that the UE needs to monitor is 4, and the DCI that the UE needs to monitor includes DCP, then the UE can monitor the DCP in the first DCP monitoring opportunity; or, if the number of DCI sizes that the UE can monitor is 4 at most, the number of DCI sizes that the UE needs to monitor is 5, and the DCI that the UE needs to monitor includes the DCP, the UE does not monitor the DCP in the first DCP monitoring opportunity.

The DCI size budget is adopted to determine whether to monitor the first DCP monitoring occasion, so that the monitoring behavior of the UE can meet the requirement of the DCI size budget, and the monitoring of the UE is more flexible.

Third determination mode: and determining according to the time domain position of the first DCP monitoring occasion and the DCI size budget.

For example, the UE determines the number of DCI sizes that the UE can monitor at most and the number of DCI sizes that the UE needs to monitor. If the number of DCI sizes that the UE can monitor at most is greater than or equal to the number of DCI sizes that the UE needs to monitor (regarding DCP as DCI that the UE needs to monitor), the UE determines whether the time domain position of the first DCP monitoring occasion is located within the first DRX activation time. If the time domain position of the first DCP listening occasion is located within the first DRX activation time, the UE does not listen to the DCP in the first DCP listening occasion, or if the time domain position of the first DCP listening occasion is not located or is partially located within the first DRX activation time, the UE listens to the DCP in the first DCP listening occasion.

Alternatively, if the number of DCI sizes that the UE is able to monitor at most is less than the number of DCI sizes that the UE needs to monitor (regarding the DCP as the DCI that the UE needs to monitor), the UE may not need to determine the time domain position of the first DCP monitoring occasion, but may instead determine that the UE does not monitor the DCP within the first DCP monitoring occasion.

For another example, the UE determines whether the time domain position of the first DCP listening occasion is within the first DRX activation time, and if the time domain position of the first DCP listening occasion is not or is partially within the first DRX activation time, the UE determines the number of DCI sizes that the UE can at most listen to and the number of DCI sizes that the UE needs to listen to. If the number of DCI sizes that the UE can monitor at most is greater than or equal to the number of DCI sizes that the UE needs to monitor (regarding the DCP as DCI that the UE needs to monitor), the UE monitors the DCP in the first DCP monitoring occasion, or if the number of DCI sizes that the UE can monitor at most is less than the number of DCI sizes that the UE needs to monitor, the UE does not monitor the DCP in the first DCP monitoring occasion.

Alternatively, if the time domain position of the first DCP listening occasion is located within the first DRX activation time, the UE may not need to determine the number of DCI sizes that the UE can monitor at most and the number of DCI sizes that the UE needs to monitor, but may instead determine that the UE does not monitor the DCP during the first DCP listening occasion.

The third determination mode is equivalent to the combination of the first determination mode and the second determination mode, so that the determination result is more reasonable.

As to which of the above three ways the UE determines whether to listen in the first DCP listening occasion, it may be determined by the UE itself, or configured by the network device, or may be specified by a protocol, etc.

Alternatively, in various embodiments of the present application, the UE may not have a procedure of determining whether to monitor the DCP listening occasion, e.g., for the embodiment shown in fig. 5, the UE may not perform S51. For example, in the case that the time domain position of the first DCP listening occasion is located within the first DRX activation time, the UE does not listen at the first DCP listening occasion, or in the case that all the time domain positions corresponding to the first DCP listening occasion are not located within the first DRX activation time, the UE listens at the first DCP listening occasion, or in the case that part of the time domain positions corresponding to the first DCP listening occasion are not located within the first DRX activation time, the UE does not listen at the DCP listening occasion included in the first DCP listening occasion that is located within the first DRX activation time, but does not listen at the DCP listening occasion included in the first DCP listening occasion that is not located within the first DRX activation time. For another example, if the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor, then the UE monitors in the first DCP monitoring occasion, and if the number of DCI sizes that the UE can monitor at most is less than or equal to the number of DCI sizes that the UE needs to monitor, then the UE does not monitor in the first DCP monitoring occasion. For ease of understanding, various embodiments of the present application take UE presence determination as an example.

Alternatively, according to the first determination manner as above, S51 may be replaced by the UE determining whether the time domain position of the first DCP listening occasion is within the first DRX activation time.

Alternatively, according to the first determination manner as described above, S51 may be replaced by the UE determining whether the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor.

Alternatively, S51 may be replaced accordingly according to the third determination as above.

S52, if the UE determines not to monitor in the first DCP listening occasion, the UE wakes up in a first DRX duration associated with the first DCP listening occasion and wakes up or sleeps in a second DRX duration associated with the first DCP listening occasion. Alternatively, if the UE does not monitor for the first DCP listening occasion, the UE wakes up on the first set of carriers for a first DRX duration associated with the first DCP listening occasion and wakes up or sleeps on the second set of carriers for a second DRX duration associated with the first DCP listening occasion.

Alternatively, if S51 is replaced according to the first determination as above, S52 may also be replaced by waking up or hibernating in a first DRX duration associated with the first DCP listening occasion and in a second DRX duration associated with the first DCP listening occasion if the time domain position of the first DCP listening occasion is within the first DRX activation time.

Alternatively, if S51 is replaced according to the first determination manner as above, S52 may also be replaced by waking up or hibernating in a first DRX duration associated with a first DCP listening occasion and waking up or hibernating in a second DRX duration associated with the first DCP listening occasion if the number of DCI sizes that the UE is able to monitor at most is less than or equal to the number of DCI sizes that the UE needs to monitor.

Alternatively, if S51 is replaced according to the third determination as above, S52 may be replaced accordingly.

On the first set of carriers, the first DCP listening occasion may be associated with one or more DRX cycles in accordance with the first DRX configuration. The DRX cycle associated with the first DCP listening occasion is later in the time domain than the first DCP listening occasion, and if the first DCP listening occasion is associated with multiple DRX cycles, the multiple DRX cycles may or may not be continuous in the time domain. In addition, the first DRX duration corresponds to a first DRX configuration, the first DRX duration being on a first set of carriers. For example, the first DRX Duration may include On Duration in all or part of the DRX cycle associated with the first DCP listening occasion in the first DRX configuration, or the first DRX Duration may include On Duration in all or part of the DRX cycle associated with the first DCP listening occasion On the first set of carriers. If the UE determines not to monitor in the first DCP monitoring occasion, the UE does not monitor in the first DCP monitoring occasion. In this case, to reduce the probability that the UE misses a PDCCH that the network device may transmit on the first set of carriers, the UE may wake up within the first DRX duration.

The first DCP listening occasion may also be associated with one or more DRX cycles on a second set of carriers in accordance with a second DRX configuration. Because the first DCP listening occasion is not configured on the second set of carriers, such an association is an association in a time domain location, e.g., one or more DRX cycles on the second set of carriers that are later in the time domain than the first DCP listening occasion may be associated with the first DCP listening occasion. And the first DCP listening occasion may or may not be continuous in the time domain if it is associated with multiple DRX cycles. In addition, a second DRX duration corresponds to a second DRX configuration, the second DRX duration being on a second set of carriers. The second DRX Duration may include On Duration in all or part of the DRX cycle associated with the first DCP listening occasion in the second DRX configuration, or alternatively, the second DRX Duration may include On Duration in all or part of the DRX cycle associated with the first DCP listening occasion On the second set of carriers. For example, it may default (or protocol specify) that if the UE determines not to monitor within the first DCP listening occasion, the UE may sleep for a second DRX duration associated with the first DCP listening occasion to save power consumption of the UE; alternatively, it may default (or protocol specifies) that if the UE determines not to monitor for the first DCP listening occasion, the UE may wake up for a second DRX duration associated with the first DCP listening occasion to reduce the probability that the UE misses data that the network device may transmit on the second set of carriers. In this case, the UE's behavior on the second set of carriers is default or specified by the protocol, without additional configuration of the network device, or otherwise determined by the UE, which can simplify the implementation of the network device and UE.

Alternatively, the UE sleeps or wakes up for the second DRX duration, which may also be indicated by the network device. For example, the network device sends configuration information to the UE, and accordingly, the UE receives configuration information from the network device, which may be sent, for example, through RRC messages, system messages, or other messages. The configuration information may be sent on one or more carriers included in the first set of carriers, e.g. a primary carrier configured by the network device for the UE belongs to the first set of carriers, and the configuration information may be sent on the primary carrier; alternatively, the configuration information may be transmitted on one or more carriers included in the second set of carriers. The configuration information may configure: in the case that the UE is not listening within a DCP listening occasion, the UE wakes up on a second set of carriers within a DRX duration associated with the DCP listening occasion; alternatively, the configuration information may configure: in the event that the UE is not listening within a DCP listening occasion, the UE sleeps on a second set of carriers for a DRX duration associated with the DCP listening occasion. In this case, the network device may configure the UE to sleep or wake up on the second set of carriers through the configuration information according to factors such as data transmission, for example, if the network device would schedule the UE to transmit data or receive data during the DRX cycle associated with the first DCP listening occasion on the second set of carriers, the network device may instruct the UE to wake up through the configuration information, and if the network device would not schedule the UE to transmit data and receive data during the DRX cycle associated with the first DCP listening occasion on the second set of carriers, the network device may instruct the UE to sleep through the configuration information. In this way, the dormancy or wake-up of the UE can be made to meet the data transmission requirements.

S53, if the UE determines to monitor in the first DCP monitoring occasion, the UE determines to sleep or wake up on the first set of carriers and determines to sleep or wake up on the second set of carriers according to the monitoring situation.

Alternatively, if S51 is replaced according to the first determination manner as above, S53 may also be replaced by that if all or part of the time domain positions corresponding to the first DCP listening occasion are not located within the first DRX activation time, the UE listens to the DCP within the first DCP listening occasion, determines sleep or wake-up on the first set of carriers according to the listening situation, and determines sleep or wake-up on the second set of carriers.

Alternatively, if S51 is replaced according to the second determination manner as above, S53 may also be replaced by if the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor, the UE monitors the DCP in the first DCP monitoring occasion, determines sleep or wake-up on the first set of carriers according to the monitoring situation, and determines sleep or wake-up on the second set of carriers.

Alternatively, if S51 is replaced according to the third determination as above, S53 may be replaced accordingly.

If the UE needs to monitor in the first DCP monitoring occasion, the UE monitors in the first DCP monitoring occasion, and determines dormancy or wake-up on the first set of carriers and the second set of carriers according to the monitoring condition of the DCP in the first DCP monitoring occasion, that is, the monitoring condition of the UE in the first DCP monitoring occasion, so that the behavior of the UE on the first set of carriers can be determined, and the behavior of the UE on the second set of carriers can also be determined. For example, referring to fig. 6, the hatched rectangle in fig. 6 indicates that the first DCP listening occasion is not configured on FR2, and the UE's listening situation on the first DCP listening occasion can determine the UE's behavior on the first set of carriers or the UE's behavior on the second set of carriers.

As an alternative implementation manner of the DCP, if the network device sends the DCP, the UE is instructed to wake up in the DRX cycle associated with the DCP, and if the network device does not send the DCP, the UE is instructed to sleep in the DRX cycle associated with the DCP. For the UE, if the DCP is monitored and received, it wakes up in the DCP-associated DRX cycle, and if the DCP is not monitored, it sleeps in the DCP-associated DRX cycle. If the DCP employs such an implementation, then if the UE receives a DCP from the network device within a first DCP listening occasion, the UE wakes up on a first set of carriers for a first DRX duration associated with the first DCP listening occasion, and on a second set of carriers for a second DRX duration associated with the first DCP listening occasion; and if the UE does not receive the DCP from the network device within the first DCP listening occasion, the UE sleeps on the first set of carriers for a first DRX duration associated with the first DCP listening occasion and the UE sleeps on the second set of carriers for a second DRX duration associated with the first DCP listening occasion.

As another alternative implementation manner, the DCP includes indication information, if the network device sends the DCP and the indication information included in the DCP indicates to wake up, the UE is instructed to wake up in the DRX cycle associated with the DCP, and if the network device sends the DCP and the indication information included in the DCP indicates to sleep, the UE is instructed to sleep in the DRX cycle associated with the DCP. For the UE, if the DCP is monitored and received, and the indication information included in the DCP indicates wake-up, the UE wakes up in the DRX cycle associated with the DCP, and if the DCP is monitored and received, and the indication information included in the DCP indicates sleep, the UE sleeps in the DRX cycle associated with the DCP. If the DCP employs such an implementation, then if the UE receives a DCP from the network device within a first DCP listening occasion and the DCP includes indication information indicating a wakeup, the UE wakes up on a first set of carriers for a first DRX duration associated with the first DCP listening occasion and the UE wakes up on a second set of carriers for a second DRX duration associated with the first DCP listening occasion; and if the UE receives a DCP from the network device within the first DCP listening occasion and the DCP includes indication information indicating dormancy, the UE sleeps on the first set of carriers for a first DRX duration associated with the first DCP listening occasion and the UE sleeps on the second set of carriers for a second DRX duration associated with the first DCP listening occasion.

As yet another alternative embodiment, the DCP is implemented such that the DCP includes first indication information and second indication information, where the first indication information corresponds to a first set of carriers, or corresponds to a first DRX configuration, and the second indication information corresponds to a second set of carriers, or corresponds to a second DRX configuration. If the network device sends the DCP and the first indication information included in the DCP indicates to wake up, the UE is indicated to wake up in the DRX period under the first DRX configuration associated with the DCP, and if the network device sends the DCP and the first indication information included in the DCP indicates to sleep, the UE is indicated to sleep in the DRX period under the first DRX configuration associated with the DCP. The manner of indication of the second indication information is also similar. For the UE, if the DCP is monitored and received, and the first indication information included in the DCP indicates wake-up, the UE wakes up in the DRX cycle under the first DRX configuration associated with the DCP, and if the DCP is monitored and received, and the first indication information included in the DCP indicates sleep, the UE sleeps in the DRX cycle under the first DRX configuration associated with the DCP. The way the UE understands the second indication information is similar. If the DCP employs such an implementation, then if the UE receives a DCP from the network device within a first DCP listening occasion and the DCP includes first indication information indicating a wake-up, the UE wakes up on a first set of carriers within a first DRX duration associated with the first DCP listening occasion; and if the UE receives a DCP from the network device within the first DCP listening occasion and the DCP includes first indication information indicating sleep, the UE sleeps on the first set of carriers for a first DRX duration associated with the first DCP listening occasion. Similarly, if the UE receives a DCP from the network device within the first DCP listening occasion and the DCP includes second indication information indicating wake-up, the UE wakes up on a second set of carriers within a second DRX duration associated with the first DCP listening occasion; and if the UE receives a DCP from the network device within the first DCP listening occasion and the DCP includes second indication information indicating sleep, the UE sleeps on a second set of carriers for a second DRX duration associated with the first DCP listening occasion. In this way, the DCP may indicate sleep or wake-up in different DRX durations through different indication information, for example, the network device may determine whether the corresponding indication information indicates wake-up or sleep according to information transmission conditions on two sets of carriers, so that sleep or wake-up behavior of the UE better meets service transmission requirements.

As a further alternative embodiment, the DCP is implemented in such a way that the two sets of carriers have corresponding DCPs, for example, the DCP may include identifiers of the sets of carriers, so as to distinguish between DCPs of different sets of carriers, or the DCPs of different sets of carriers have different formats. For a group of carriers, if the network device sends a DCP corresponding to the group of carriers and the DCP indicates to wake up, the UE is instructed to wake up on the group of carriers in the DRX cycle associated with the DCP, and if the network device sends a DCP corresponding to the group of carriers and the DCP indicates to sleep, the UE is instructed to sleep on the group of carriers in the DRX cycle associated with the DCP. If the DCP employs such an implementation, then the UE wakes up on the first set of carriers for a first DRX duration associated with the first DCP listening occasion if the UE receives the DCP from the network device within the first DCP listening occasion and the DCP corresponds to the first set of carriers, if the DCP indicates to wake up, or sleeps on the first set of carriers for the first DRX duration associated with the first DCP listening occasion if the DCP indicates to sleep. The operation of the network device and the UE is also the same for the second set of carriers.

As a further alternative embodiment, the DCP is implemented in such a way that the two sets of carriers have corresponding DCPs, for example, the DCP may include identifiers of the sets of carriers, so as to distinguish between DCPs of different sets of carriers, or different formats of DCPs of different sets of carriers. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, the UE is instructed to wake up on the group of carriers in the DRX period associated with the DCP, and if the network device does not send the DCP corresponding to the group of carriers, the UE is instructed to sleep on the group of carriers in the DRX period associated with the DCP. If the DCP employs such an implementation, then the UE wakes up on the first set of carriers for a first DRX duration associated with the first DCP listening occasion if the UE receives the DCP from the network device within the first DCP listening occasion and the DCP corresponds to the first set of carriers, or sleeps on the first set of carriers for a first DRX duration associated with the first DCP listening occasion if the UE does not receive the DCP from the network device corresponding to the first set of carriers within the first DCP listening occasion. The operation of the network device and the UE is also the same for the second set of carriers.

In the embodiment of the present application, the UE sleeps in the first DRX duration, which may be implemented as follows: the UE does not start nor restart the first DRX duration timer at the start of the first DRX duration. The first DRX duration timer is configured by a first DRX configuration, the first DRX duration timer corresponding to a first set of carriers. If the first DRX duration timer is not started, the UE does not start the first DRX duration timer at the starting time of the first DRX duration, and if the first DRX duration timer is in an operating state, the UE does not restart the first DRX duration timer at the starting time of the first DRX duration, so that the UE can sleep in the first DRX duration. The implementation of the UE to sleep for the second DRX duration is also similar, for example, by: the UE does not start nor restart the second DRX duration timer at the start of the second DRX duration. The second DRX duration timer is configured by a second DRX configuration, the second DRX duration timer corresponding to a second set of carriers.

The UE wakes up in the first DRX duration, which may be implemented as follows: the UE starts or restarts the first DRX duration timer at the start time of the first DRX duration. If the first DRX duration timer is not started, the UE starts the first DRX duration timer at the starting time of the first DRX duration, and if the first DRX duration timer is in an operating state, the UE restarts the first DRX duration timer at the starting time of the first DRX duration, so that the UE can wake up in the first DRX duration. The implementation of the UE waking up during the second DRX duration is also similar, for example, by: the UE starts or restarts the second DRX duration timer at the start time of the second DRX duration. The second DRX duration timer is configured by a second DRX configuration, the second DRX duration timer corresponding to a second set of carriers.

S52 and S53 are two schemes in parallel, and are not executed simultaneously.

In the embodiments of the present application, two techniques of DRX configuration can be used in combination with a wake-up signal and prescribe the behavior of the terminal device in case of combination. For example, in the case that the terminal device does not monitor the DCP monitoring opportunity corresponding to the first group of carriers, the behavior of the terminal device on the second group of carriers may be specified by default, by protocol specification, or by network configuration, etc.; and under the condition that the terminal equipment monitors the DCP monitoring time corresponding to the first group of carriers, which is applicable to both the first group of carriers and the second group of carriers. In this way, the terminal device only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, so that the power consumption of the terminal device for monitoring the DCP is reduced, and the scheduling flexibility of the network device is also increased. The monitoring condition of the terminal equipment on one group of carriers can be suitable for two groups of carriers, so that the DCP mechanism can be used by both groups of carriers, and the power consumption of the terminal equipment on the two groups of carriers can be further reduced. And the network device does not need to configure the DCP for the second group of carriers, so that signaling overhead can be saved.

The embodiment of the application provides a second communication method, please refer to fig. 8, which is a flowchart of the method.

S81, the UE determines whether to monitor the DCP in the first DCP monitoring opportunity, or the UE determines whether to monitor in the first DCP monitoring opportunity.

Alternatively, S81 may also be replaced by the UE determining whether the time domain position of the first DCP listening occasion is within the first DRX activation time.

Alternatively, S81 may be replaced by the UE determining whether the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor. Alternatively, S81 may be replaced accordingly according to the third determination method described in the embodiment shown in fig. 5.

Regarding more of S81, e.g., how the UE determines whether to listen within the first DCP listening occasion, etc., reference may be made to S51 in the embodiment shown in fig. 5.

S82, if the UE determines to listen in the first DCP listening occasion, the UE determines to sleep or wake up on the first set of carriers and determines to sleep or wake up on the second set of carriers according to the listening situation.

Alternatively, if S81 is replaced by the UE determining whether the time domain position of the first DCP listening occasion is within the first DRX activation time, S82 may be replaced by the UE listening to the DCP in the first DCP listening occasion and determining sleep or wake-up on the first set of carriers and determining sleep or wake-up on the second set of carriers according to the listening situation if all or part of the time domain position corresponding to the first DCP listening occasion is not within the first DRX activation time.

Alternatively, if S81 is replaced by the UE determining whether the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor, S82 may be replaced by the UE monitoring the DCP in the first DCP monitoring occasion and determining sleep or wake-up on the first set of carriers and determining sleep or wake-up on the second set of carriers according to the monitoring situation if the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor.

Alternatively, if S81 is replaced accordingly according to the third determination method described in the embodiment shown in fig. 5, S82 may be replaced accordingly according to S81.

In the embodiment of the present application, the network device may send the DCP on a first carrier, where the first carrier belongs to the first group of carriers. For example, the network device configures a DCP for one or more carriers included in the first set of carriers, and the first carrier includes the one or more carriers. For another example, if the main carrier configured by the network device for the UE belongs to the first group of carriers, the network device may configure the DCP for the main carrier, and if the first carrier is the main carrier of the UE, the network device may send the DCP on the main carrier, without configuring the DCP on other carriers, so as to save transmission overhead. If the UE needs to monitor on the first set of carriers, it may monitor on all the carriers comprised by the first set of carriers, or the network device may be preconfigured on which carriers to send the DCP, the UE only needs to monitor on these carriers.

The network device may transmit the DCP on a second carrier that belongs to a second group of carriers. For example, the network device configures a DCP for one or more carriers included in the second set of carriers, and the second carrier includes the one or more carriers. If the UE needs to monitor on the second set of carriers, it may monitor on all the carriers comprised by the second set of carriers, or the network device may be preconfigured on which carriers the DCP is sent on, the UE only needs to monitor on these carriers. That is, in the embodiment of the present application, the network device configures the DCP for the first set of carriers and also configures the DCP for the second set of carriers.

Although DCPs are configured for both the first and second sets of carriers, the UE first determines whether to monitor on the first set of carriers, if so, then the UE monitors on the first set of carriers, e.g., within a first DCP monitoring opportunity, and determines sleep or wake-up on the first and second sets of carriers based on the monitoring results. In this case, the UE does not need to monitor on the second set of carriers, e.g., the UE does not monitor for a second DCP monitoring occasion. The second DCP listening occasion is a DCP listening occasion configured on a second group of carriers, the second DCP listening occasion applying a second DRX configuration. In the second DRX configuration, there are multiple On Duration times, and the DCP listening occasion may also occur multiple times, for example, one DCP listening occasion before each DRX cycle begins. The second DCP listening occasion is then, for example, the current listening occasion for the UE, e.g., the second DCP listening occasion is located before the start of the On Duration time of one DRX cycle in the second DRX configuration, or the second DCP listening occasion is located before the start of the On Duration time of one DRX cycle On the second set of carriers. In case the UE is able to monitor on the first set of carriers, the power consumption of the UE due to the monitoring can be reduced since the UE does not need to monitor on the second set of carriers.

For more content of S82, e.g. how the UE determines dormancy or wake-up on the first and second sets of carriers according to the listening situation, reference may be made to S53 in the embodiment shown in fig. 5.

Note that, for an introduction of the content such as the first DRX duration associated with the first DCP listening occasion, reference may be made to S52 in the embodiment shown in fig. 5. In addition, the time domain positions of the first DCP listening occasion and the second DCP listening occasion may be the same, or the time domain position of the first DCP listening occasion may be earlier than the time domain position of the second DCP listening occasion, so that when referring to S52, the second DRX duration associated with the first DCP listening occasion described in S52 may also be considered as the DRX duration associated with the second DCP listening occasion on the second set of carriers in the embodiments of the present application.

S83, if the UE determines not to monitor in the first DCP monitoring occasion, the UE determines whether to monitor the DCP in the second DCP monitoring occasion, or in other words, whether to monitor in the second DCP monitoring occasion.

Alternatively, if S81 is replaced with the UE determining whether the time domain position of the first DCP listening occasion is within the first DRX activation time, S83 may be replaced with the UE determining whether to listen to the DCP in the second DCP listening occasion, or whether to listen in the second DCP listening occasion, if the time domain position of the first DCP listening occasion is within the first DRX activation time.

Alternatively, if S81 is replaced with the UE determining whether the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor, S83 may be replaced with the UE determining whether to monitor the DCP in the second DCP monitoring occasion, or whether to monitor in the second DCP monitoring occasion, if the number of DCI sizes that the UE can monitor at most is less than or equal to the number of DCI sizes that the UE needs to monitor.

Alternatively, if S81 is replaced accordingly according to the third determination method described in the embodiment shown in fig. 5, S83 may also be replaced accordingly according to S81.

In addition, for S83, the UE determines whether to monitor in the second DCP monitoring opportunity, and may also perform corresponding replacement, where a specific replacement manner may refer to the description of the replacement manner of S81.

The manner in which the UE determines whether to listen in the second DCP listening occasion is similar to the manner in which the UE determines whether to listen in the first DCP listening occasion, may be referred to the description earlier in the embodiments of the present application, or may be referred to S51 in the embodiment shown in fig. 5.

In addition, if the UE does not listen during the first DCP listening occasion, the UE may optionally wake up on the first set of carriers for the first DRX duration to avoid missing PDCCHs.

And S84, if the UE determines to monitor in the second DCP monitoring occasion, the UE determines dormancy or awakening on the second group carrier according to the monitoring condition. For S84, the UE determines to monitor in the second DCP monitoring occasion, and may also perform corresponding replacement, and for a specific replacement, reference may be made to the description of the replacement of S82.

If the UE determines to monitor during the second DCP monitoring occasion, the UE may monitor during the second DCP monitoring occasion, at which point the monitoring result of the second DCP monitoring occasion may be used to decide whether the UE is dormant or awake on the second set of carriers. For example, referring to fig. 9, the rectangular box drawn "\" in fig. 9 represents a first DCP listening occasion, and the rectangular box drawn "/" represents a second DCP listening occasion. If the UE is able to monitor the first DCP monitoring occasion, the UE can determine sleep or wake-up on the first set of carriers and can determine sleep or wake-up on the second set of carriers according to the monitoring condition of the first DCP monitoring occasion; if the UE cannot monitor the first DCP listening occasion but can monitor the second DCP listening occasion, the UE may determine to sleep or wake up on the second set of carriers based on the listening situation of the second DCP listening occasion.

As an alternative implementation manner of the DCP, if the network device sends the DCP, the UE is instructed to wake up in the DRX cycle associated with the DCP, and if the network device does not send the DCP, the UE is instructed to sleep in the DRX cycle associated with the DCP. For the UE, if the DCP is monitored and received, it wakes up in the DCP-associated DRX cycle, and if the DCP is not monitored, it sleeps in the DCP-associated DRX cycle. If the DCP employs such an implementation, then if the UE receives a DCP from the network device within a second DCP listening occasion, the UE wakes up on a second set of carriers for a second DRX duration associated with the second DCP listening occasion; and if the UE does not receive the DCP from the network device within the second DCP listening occasion, the UE sleeps on a second set of carriers for a second DRX duration associated with the second DCP listening occasion.

As another alternative implementation manner, the DCP includes indication information, if the network device sends the DCP and the indication information included in the DCP indicates to wake up, the UE is instructed to wake up in the DRX cycle associated with the DCP, and if the network device sends the DCP and the indication information included in the DCP indicates to sleep, the UE is instructed to sleep in the DRX cycle associated with the DCP. For the UE, if the DCP is monitored and received, and the indication information included in the DCP indicates wake-up, the UE wakes up in the DRX cycle associated with the DCP, and if the DCP is monitored and received, and the indication information included in the DCP indicates sleep, the UE sleeps in the DRX cycle associated with the DCP. If the DCP employs such an implementation, then if the UE receives a DCP from the network device within a second DCP listening occasion and the DCP includes indication information indicating a wake-up, the UE wakes up on a second set of carriers for a second DRX duration associated with the second DCP listening occasion; and if the UE receives a DCP from the network device within a second DCP listening occasion and the DCP indicates sleep, the UE sleeps on a second set of carriers for a second DRX duration associated with the second DCP listening occasion.

In both embodiments above, the listening result of the second DCP listening occasion is not used to decide whether the UE is dormant or awake on the first set of carriers.

As yet another alternative embodiment, the DCP is implemented in such a way that the DCP includes third indication information and fourth indication information, where the third indication information corresponds to the first set of carriers, or corresponds to the first DRX configuration, and the fourth indication information corresponds to the second set of carriers, or corresponds to the second DRX configuration. If the network device sends the DCP and the third indication information included in the DCP indicates to wake up, the UE is indicated to wake up in the DRX period under the first DRX configuration associated with the DCP, and if the network device sends the DCP and the third indication information included in the DCP indicates to sleep, the UE is indicated to sleep in the DRX period under the first DRX configuration associated with the DCP. The fourth indication information is indicated in a similar manner. For the UE, if the DCP is monitored and received, and the third indication information included in the DCP indicates wake-up, the UE wakes up in the DRX cycle under the first DRX configuration associated with the DCP, and if the DCP is monitored and received, and the third indication information included in the DCP indicates sleep, the UE sleeps in the DRX cycle under the first DRX configuration associated with the DCP. The UE's understanding of the fourth indication information is also similar. If the DCP adopts this implementation, the listening result of the second DCP listening occasion may be used to determine the UE to sleep or wake up on the second set of carriers, and may also be used to determine the UE to sleep or wake up on the first set of carriers. For example, if the UE receives a DCP from the network device within a second DCP listening occasion and the DCP includes third indication information indicating a wake-up, the UE wakes up on the first set of carriers for a first DRX duration associated with the first DCP listening occasion (or the second DCP listening occasion); and if the UE receives a DCP from the network device within the second DCP listening occasion and the DCP includes third indication information indicating sleep, the UE sleeps on the first set of carriers for a first DRX duration associated with the first DCP listening occasion (or the second DCP listening occasion). Similarly, if the UE receives a DCP from the network device in a second DCP listening occasion and the fourth indication information included in the DCP indicates to wake up, the UE wakes up on a second set of carriers within a second DRX duration associated with the second DCP listening occasion; and if the UE receives a DCP from the network device within the second DCP listening occasion and the fourth indication information included in the DCP indicates sleep, the UE sleeps on the second set of carriers for a second DRX duration associated with the second DCP listening occasion.

In this way, the DCP may indicate sleep or wake-up in different DRX durations through different indication information, for example, the network device may determine whether the corresponding indication information indicates wake-up or sleep according to information transmission conditions on two sets of carriers, so that sleep or wake-up behavior of the UE better meets service transmission requirements.

As a further alternative embodiment, the DCP is implemented in such a way that the two sets of carriers have corresponding DCPs, for example, the DCP may include identifiers of the sets of carriers, so as to distinguish between DCPs of different sets of carriers, or the DCPs of different sets of carriers have different formats. For a group of carriers, if the network device sends a DCP corresponding to the group of carriers and the DCP indicates to wake up, the UE is instructed to wake up on the group of carriers in the DRX cycle associated with the DCP, and if the network device sends a DCP corresponding to the group of carriers and the DCP indicates to sleep, the UE is instructed to sleep on the group of carriers in the DRX cycle associated with the DCP. If the DCP employs such an implementation, then the UE wakes up on the second set of carriers for a second DRX duration associated with the second DCP listening occasion if the UE receives the DCP from the network device within the second DCP listening occasion and the DCP corresponds to the second set of carriers, if the DCP indicates to wake up, or sleeps on the second set of carriers for a second DRX duration associated with the second DCP listening occasion, if the DCP indicates to sleep.

As a further alternative embodiment, the DCP is implemented in such a way that the two sets of carriers have corresponding DCPs, for example, the DCP may include identifiers of the sets of carriers, so as to distinguish between DCPs of different sets of carriers, or different formats of DCPs of different sets of carriers. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, the UE is instructed to wake up on the group of carriers in the DRX period associated with the DCP, and if the network device does not send the DCP corresponding to the group of carriers, the UE is instructed to sleep on the group of carriers in the DRX period associated with the DCP. If the DCP employs such an implementation, then the UE wakes up on the second set of carriers for a second DRX duration associated with the second DCP listening occasion if the UE receives the DCP from the network device during the second DCP listening occasion and the DCP corresponds to the second set of carriers, or sleeps on the second set of carriers for a second DRX duration associated with the second DCP listening occasion if the UE does not receive the DCP from the network device corresponding to the second set of carriers during the second DCP listening occasion.

S85, if the UE determines not to monitor in the second DCP monitoring occasion, the UE wakes up or sleeps on the second group of carriers for a second DRX duration associated with the second DCP monitoring occasion. For S85, the UE determines that listening is not performed in the second DCP listening occasion, and may also perform corresponding replacement, and for a specific replacement, reference may be made to the description of the replacement of S83.

If the UE determines not to monitor in the second DCP monitoring occasion, the UE does not monitor in the second DCP monitoring occasion. S85 is the case in which the UE listens neither at the first DCP listening occasion nor at the second DCP listening occasion. In this case, to reduce the probability that the UE misses a PDCCH that the network device may transmit on the first set of carriers, the UE may wake up on the first set of carriers for the first DRX duration.

For the second set of carriers, for example, it may default (or protocol specifies), if the UE determines not to monitor within the second DCP monitoring occasion (or if the UE determines not to monitor within the first DCP monitoring occasion and not to monitor within the second DCP monitoring occasion), the UE may sleep on the second set of carriers for a second DRX duration associated with the second DCP monitoring occasion to save power consumption of the UE; alternatively, it may default (or be protocol defined) that if the UE determines not to monitor for the second DCP monitoring occasion (or if the UE determines not to monitor for the first DCP monitoring occasion and not to monitor for the second DCP monitoring occasion), the UE wakes up on the second set of carriers for a second DRX duration associated with the second DCP monitoring occasion to reduce the probability that the UE misses data that the network device may transmit on the second set of carriers. In this case, the UE's behavior on the second set of carriers is default or specified by the protocol, without additional configuration of the network device, or otherwise determined by the UE, which can simplify the implementation of the network device and UE.

Alternatively, the UE may be asleep or awake on the second set of carriers for the second DRX duration, as indicated by the network device. For example, the network device sends configuration information to the UE, and accordingly, the UE receives configuration information from the network device, which may be sent, for example, through RRC messages, system messages, or other messages. The configuration information may be sent on one or more carriers included in the first set of carriers, e.g. a primary carrier configured by the network device for the UE belongs to the first set of carriers, and the configuration information may be sent on the primary carrier; alternatively, the configuration information may be transmitted on one or more carriers included in the second set of carriers. The configuration information may configure: in the event that the UE is not listening within a DCP listening occasion, the UE wakes up on a second set of carriers for a DRX duration associated with the DCP listening occasion; alternatively, the configuration information may configure: in the event that the UE is not listening within a DCP listening occasion, the UE sleeps on a second set of carriers for a DRX duration associated with the DCP listening occasion. In this case, the network device may configure the UE to sleep or wake up on the second set of carriers through the configuration information according to factors such as data transmission, for example, if the network device may schedule the UE to transmit data or receive data during the DRX cycle associated with the second DCP listening occasion on the second set of carriers, the network device may instruct the UE to wake up through the configuration information, and if the network device may not schedule the UE to transmit data and receive data during the DRX cycle associated with the second DCP listening occasion on the second set of carriers, the network device may instruct the UE to sleep through the configuration information. In this way, the dormancy or wake-up of the UE can be made to meet the data transmission requirements.

For other matters, for example, how the UE should sleep during the DRX duration, how the UE should wake during the DRX duration, etc., reference is made to the relevant description of the embodiment shown in fig. 5.

The embodiment of the application provides a third communication method, please refer to fig. 10, which is a flowchart of the method.

And S101, the network equipment sends DCI to the UE on the first carrier, and correspondingly, the UE receives the DCI from the network equipment on the first carrier. The first carrier may comprise one or more carriers, which may belong to a first group of carriers or to a second group of carriers. The first set of carriers applies a first DRX configuration and the second set of carriers applies a second DRX configuration.

DCP is also a type of DCI, and is also limited by the DCI size budget. In the embodiment of the present application, the network device does not need to configure a DCP for the UE, or the network device does not need to send the DCP, but rather, the function of the DCP is implemented through other DCIs besides the DCP. The size of the DCP is generally different from that of other general DCIs, and the DCP occupies a size according to the DCI size budget of the UE, which reduces the kinds of DCIs that the UE can receive. In the embodiment of the present application, however, the network device does not need to send the DCP, but sends the normal DCI, so that the DCP does not occupy the overhead of DCI size, so that the UE can receive more kinds of DCIs.

Alternatively, in the embodiment of the present application, the network device may also configure the DCP for the UE, for example, the network device configures the DCP for the first set of carriers. However, in some cases, the UE cannot monitor the DCP, for example, because of the restriction of the DCI size budget, the UE determines not to monitor the DCP, or because the corresponding DCP monitor occasion is within the DRX activation time, the UE determines not to monitor the DCP, and in these cases, the network device may also implement the DCP function by sending other DCIs. For description of the contents of the first group carrier, the second group carrier, the first DRX configuration, the second DRX configuration, and the DRX activation time, reference may be made to the embodiment shown in fig. 5 or the embodiment shown in fig. 8.

Alternatively, in the embodiment of the present application, whether the network device configures the DCP or whether the network device transmits the DCP, the network device may transmit the DCI with the DCP function in the DCP listening occasion, for example, the network device may transmit the DCI with the DCP function in the first DCP listening occasion, and the UE may receive the DCI with the DCP function in the first DCP listening occasion. For the content of the first DCP listening occasion, etc., reference is made to the description of the embodiment shown in fig. 5. Alternatively, the network device may not transmit DCI with DCP function in the DCP listening occasion, but transmit DCI with DCP function at other times. For example, the network device transmits DCI with DCP function during On Duration of the DRX period.

For example, if the network device configures a DCP, or the network device would transmit DCP-capable DCI during a DCP listening occasion, the UE may determine whether to listen to the DCP during the first DCP listening occasion, and if the UE determines to listen to the DCP during the first DCP listening occasion, the UE may listen to the DCP during the first DCP listening occasion, or to DCP-capable DCI. As to the manner in which the UE determines whether to listen to the DCP within the first DCP listening occasion, reference may be made to S51 in the embodiment shown in fig. 5. For example, the first determination is based on the time domain position of the first DCP listening occasion; for example, the second determination is based on DCI size budget; for example, the third determination is based on the time domain position of the first DCP listening occasion and the DCI size budget, etc., which can be described with reference to S51 of the embodiment shown in fig. 5.

If the DCI is used to implement the functionality of the DCP, the DCI may optionally indicate that the DCI is used to implement the DCP functionality via a second field included in the DCI. The second field includes, for example, one or more of the following: a frequency domain resource allocation (frequency domain resource assignment, FDRA) field, a modulation and coding scheme (modulation and coding scheme, MCS) field, a new data indication (new data indicator, NDI) field, a redundancy version (redundancy version, RV) field, a hybrid automatic repeat request process number (hybrid automatic repeat request process number), an antenna port (a ntenna port (s)), or a demodulation reference signal sequence initialization (demodulation reference signal sequence initialization) field. In DCI, the MCS field occupies 5 bits (bits), the NDI field occupies 1 bit, the RV field occupies 2 bits, the HARQ process number field occupies 4 bits, the antenna port field occupies at least 4 bits, and the DMRS sequence number initialization field occupies 1 bit. For example, the second field is an FDRA field; alternatively, the second field is an MCS field; alternatively, the second field includes an MCS field and an NDI field; alternatively, the second field includes an FDRA field, an MCS field, and an RV field, and so on.

If the DCI is used to normally schedule data and not to implement the DCP function, the values of the fields as above included in the DCI are related to the scheduled data, e.g., the values of the MCS field may indicate the MCS of the scheduled data. Whereas if DCI is used to implement DCP functionality, the value of the second field may be a first value, which may be specified by a protocol, or may be default, or may also be configured by the network device. For example, the first value is all 0, or all 1, etc. By this value, the UE can be made clear, and the current DCI is used to implement the DCP function.

The DCI may further include second indication information if the value of the second field is the first value, and the DCI does not include the second indication information if the value of the second field is not the first value. For example, the value of the second field is not the first value, but a normal (normal) value of the second field, where the DCI is not used to implement the DCP function, but implements a normal function of the DCI, such as scheduling data, the DCI does not naturally need to include the second indication information. Therefore, if the value of the second field is the first value, the DCI may be indicated to further include second indication information. The second indication information may indicate to sleep for a second DRX duration associated with the DCI on a second set of carriers or to wake up for the second DRX duration associated with the DCI on the second set of carriers. Wherein, on the second set of carriers, the DCI for implementing the DCP function may be associated with one or more DRX cycles according to a second DRX configuration. If the DCI is configured on a first set of carriers and not on a second set of carriers, such an association is an association in a time domain location, e.g., one or more DRX cycles later in time domain than the DCI on the second set of carriers may be associated with the DCI. And the DCI may be continuous or discontinuous in the time domain if it is associated with a plurality of DRX cycles. In addition, a second DRX duration corresponds to a second DRX configuration, the second DRX duration being on a second set of carriers. The second DRX Duration may include On Duration in all or part of the DRX cycle associated with the DCI in the second DRX configuration, or the second DRX Duration may include On Duration in all or part of the DRX cycle associated with the DCI On the second set of carriers.

For example, the second indication information may occupy 1 or more bits. Taking the example that the second indication information occupies 1 bit, for example, if the value of the bit is "1", then the second indication information indicates that the second carrier is awakened in the second DRX duration associated with the DCI; if the bit has a value of "0," it indicates that the DCI is dormant for a second DRX duration associated with the DCI on a second set of carriers. Alternatively, if the second indication information occupies more bits, other indication manners are also possible. The second indication information included by the DCI indicates the dormancy or the awakening of the UE on the second group carrier, the UE does not need to monitor the DCP, the number of DCI size to be monitored by the UE is reduced, and the dormancy or the awakening of the UE on the second group carrier is standardized. And the network equipment indicates the dormancy or the awakening of the UE on the second group of carriers, so that the network equipment can indicate according to the service of the UE on the second group of carriers, and the dormancy or the awakening of the UE on the second group of carriers and other behaviors are more in line with the service requirements of the UE.

There are different implementations for the UE to sleep or wake up on the first set of carriers, as exemplified below.

As an alternative embodiment, the UE may wake up on the first set of carriers for a first DRX duration associated with the DCI by default (or as specified by the protocol). Because if the second indication information indicates that the UE wakes up on the second set of carriers for the second DRX duration and the network device needs to schedule data transmission of the UE on the second set of carriers on the first set of carriers, the scheduling information from the network device may not be received if the UE sleeps on the first set of carriers for the first DRX duration, and thus data transmission on the second set of carriers may not be possible. Therefore, the UE may wake up on the first set of carriers within the first DRX duration by default (or by protocol rule) to reduce the probability that the UE misses the scheduling information and reduce the transmission delay of the traffic. Alternatively, the UE may be dormant on the first set of carriers for a first DRX duration associated with the DCI by default (or as specified by the protocol), in which way power consumption of the UE can be saved. In this way, the first carrier may belong to the first set of carriers or to the second set of carriers, i.e. the network device may transmit the DCI on the first set of carriers or the DCI on the second set of carriers.

Wherein, on the first set of carriers, the DCI for implementing the DCP function may be associated with one or more DRX cycles according to the first DRX configuration. For example, one or more DRX cycles, which are later in the time domain than the DCI, may be associated with the DCI on the first set of carriers. And the DCI may be continuous or discontinuous in the time domain if it is associated with a plurality of DRX cycles. In addition, the first DRX duration corresponds to a first DRX configuration, the first DRX duration being on a first set of carriers. The first DRX Duration may include On Duration in all or part of the DRX cycle associated with the DCI in the first DRX configuration, or the first DRX Duration may include On Duration in all or part of the DRX cycle associated with the DCI On the first set of carriers.

In this case, the DCI need only include the second indication information, and need not include indication information for indicating wake-up or sleep of the first group of carriers, contributing to saving signaling overhead.

As another alternative embodiment, if the value of the second field is the first value, the DCI may further include the first indication information, and if the value of the second field is not the first value, or if the value of the second field is the second value, the DCI does not include the first indication information. The second value may be any value of the second field other than the first value. For example, the value of the second field is not the first value, but is a normal value of the second field, where the DCI is not used to implement the DCP function, but implements a normal function of the DCI, such as scheduling data, etc., and the DCI does not need to include the first indication information naturally. Therefore, if the value of the second field is the first value, the DCI may be indicated to further include the first indication information. The first indication information may indicate to sleep for a first DRX duration associated with the DCI on a first set of carriers or to wake up for the first DRX duration associated with the DCI on the first set of carriers. Referring to fig. 11, DCI is configured on a first group of carriers, the first group of carriers belongs to FR1, and a second group of carriers belongs to FR 2. DCI received by the UE on FR1 can indicate that the UE is dormant or awake on the second set of carriers, and optionally, also indicates that the UE is dormant or awake on the first set of carriers. Wherein the dashed arrows represent optional processes. In this way, the first carrier may belong to the first set of carriers or to the second set of carriers, i.e. the network device may transmit the DCI on the first set of carriers or the DCI on the second set of carriers.

For example, the first indication information may occupy 1 or more bits. Taking the example that the first indication information occupies 1 bit, for example, if the value of the bit is "1", then the first indication information indicates that the first carrier is awakened in the first DRX duration associated with the DCI; if the bit has a value of "0," it indicates that the DCI is dormant for a first DRX duration associated with the first set of carriers. Alternatively, if the first indication information occupies more bits, other indication manners are also possible. The first indication information included by the DCI indicates the dormancy or the awakening of the UE on the first group of carriers, the UE does not need to monitor the DCP, the number of DCI size to be monitored by the UE is reduced, and the dormancy or the awakening of the UE on the first group of carriers is standardized. And the network equipment indicates the dormancy or the awakening of the UE on the first group of carriers, so that the network equipment can indicate according to the service of the UE on the first group of carriers, and the dormancy or the awakening of the UE on the first group of carriers and other behaviors are more in line with the service requirements of the UE.

In this embodiment, the network device indicates sleep or wake-up of the two groups of carriers through the second indication information and the first indication information, so that the UE has a more definite behavior and meets the service requirement.

As yet another alternative embodiment, if the DCI includes second indication information, the second indication information may indicate the UE's behavior on the first set of carriers in addition to the behavior on the second set of carriers. That is, the second indication information may indicate that on the second set of carriers, the DCI associated second DRX duration is dormant or awake, and that on the first set of carriers, the DCI associated first DRX duration is dormant or awake. Alternatively, the second indication information indicates sleep or wake-up for the DRX duration associated with the DCI. In this way, the first carrier may belong to the first set of carriers or to the second set of carriers, i.e. the network device may transmit the DCI on the first set of carriers or the DCI on the second set of carriers.

For example, the second indication information occupies one or more bits. Taking the example that the second indication information occupies 1 bit, if the value of the bit is '1', the first indication information is indicated to be awakened in the first DRX duration time associated with the DCI on the first group of carriers, and the second indication information is indicated to be awakened in the second DRX duration time associated with the DCI on the second group of carriers; if the bit has a value of "0," it is indicated to sleep for a first DRX duration associated with the DCI on a first set of carriers and to sleep for a second DRX duration associated with the DCI on a second set of carriers. Alternatively, taking the example that the second indication information occupies 2 bits, these 2 bits indicate the first set of carriers and the second set of carriers, respectively. For example, the upper bits of the 2 bits indicate the first set of carriers and the lower bits indicate the second set of carriers. If the upper bit of the 2 bits has a value of "1", then the method indicates that the DCI wakes up on the first group of carriers within a first DRX duration associated with the DCI; if the upper bit of the 2 bits has a value of "0", it indicates that the DCI is dormant for the first DRX duration associated with the first set of carriers. The lower order bits of these 2 bits are also similar in the manner of indication of the behavior of the UE on the second set of carriers.

In this way, the network device can instruct the UE to act on the first set of carriers and the second set of carriers through the second indication information, so that no more indication information is needed, signaling overhead can be saved, and the UE acts more explicitly.

As yet another alternative embodiment, the first carrier may include at least two carriers, and the at least two carriers include carriers belonging to both the first group of carriers and the second group of carriers. For example, the first carrier includes a second carrier and a third carrier, the second carrier belongs to the first group of carriers, and the third carrier belongs to the second group of carriers. This is to be understood as a case where the network device transmits DCI on both the first set of carriers and the second set of carriers, and the DCI may also include at least two, for example, the DCI includes a first DCI and a second DCI, where the first DCI is transmitted on the second carrier and the second DCI is transmitted on the third carrier. Then, the first DCI may indicate the behavior of the UE on the first set of carriers and the second DCI may indicate the behavior of the UE on the second set of carriers. For example, the first DCI may indicate to sleep for a first DRX duration associated with the DCI on a first set of carriers or to wake up for the first DRX duration associated with the DCI on the first set of carriers. The second DCI may indicate to sleep for a second DRX duration associated with the DCI on a second set of carriers or to wake up for the second DRX duration associated with the DCI on the second set of carriers. In this case, it may be considered that the first DCI includes first indication information and the second DCI includes second indication information. Then, the second DCI may include a second field, and the first DCI may also include a first field. For example, if the value of the second field is the first value, the second DCI may further include second indication information, and if the value of the second field is not the first value, the second DCI does not include the second indication information. The first DCI may further include first indication information if the value of the first field is a third value, and the first DCI does not include the first indication information if the value of the first field is not the third value. Reference is made to the foregoing for an introduction to this implementation. In addition, reference may also be made to the foregoing description regarding the manner in which the second indication information indicates the behavior of the UE on the second set of carriers, and the manner in which the first indication information indicates the behavior of the UE on the first set of carriers.

In this way, the network device can indicate the behavior of the UE on different carriers respectively through DCI carried on different carriers, so that the indication is more clear.

And S102, the UE determines according to second indication information included in the DCI, and sleeps or wakes up on a second group of carriers within a second DRX duration associated with the DCI. Or there may be no determined procedure, for example, S102 may be replaced by that the UE sleeps or wakes up on the second set of carriers for the second DRX duration associated with the DCI according to the second indication information included in the DCI. Alternatively, according to the introduction in S101, if the DCI includes a first DCI and a second DCI, S102 may be replaced by determining, by the UE, that the UE is dormant or wakes up on a second set of carriers for a second DRX duration associated with the second DCI according to second indication information included in the second DCI.

If the value of the second field included in the DCI is the first value, the UE determines that the DCI includes second indication information. Then, if the second indication information indicates to sleep on the second set of carriers for a second DRX duration associated with the DCI, the UE determines to sleep on the second set of carriers for the second DRX duration associated with the DCI, and the UE sleeps on the second set of carriers for the second DRX duration; alternatively, if the second indication information indicates that on the second set of carriers, the UE wakes up during the second DRX duration associated with the DCI, determines that on the second set of carriers, the UE wakes up during the second DRX duration associated with the DCI, and sleeps during the first DRX duration on the first set of carriers.

S103, the UE determines to sleep or wake up on the first set of carriers for the first DRX duration associated with the DCI. Or there may be no determined procedure, e.g., S103, instead the UE sleeps or wakes up on the first set of carriers for the first DRX duration associated with the DCI. Alternatively, according to the introduction in S101, if the DCI includes a first DCI and a second DCI, S103 may be replaced by the UE determining to sleep or wake up on the first set of carriers for a first DRX duration associated with the first DCI.

If the UE wakes up on the first set of carriers for a first DRX duration associated with the DCI by default (or protocol specification), if the network device is not configured with the DCP, the UE wakes up on the first set of carriers for the first DRX duration; alternatively, if the network device configures the DCP, the UE wakes up on the first set of carriers for a first DRX duration if the UE does not monitor the DCP on the first set of carriers. Alternatively, if the UE sleeps on the first set of carriers for a first DRX duration associated with the DCI by default (or protocol specification), then if the network device is not configured with the DCP, the UE sleeps on the first set of carriers for the first DRX duration; alternatively, if the network device configures the DCP, the UE wakes up on the first set of carriers for a first DRX duration if the UE does not monitor the DCP on the first set of carriers. Reference is made to the description of the embodiment shown in fig. 5 as to what situation the UE does not listen to the DCP on the first set of carriers.

Alternatively, if the DCI further includes first indication information and the first indication information indicates dormancy for a first DRX duration associated with the DCI on a first set of carriers. Then, if the DCI includes the first indication information, the UE sleeps on the first set of carriers for a first DRX duration; alternatively, if the DCI does not include the first indication information, the UE sleeps on the first set of carriers for the first DRX duration. Or if the first indication information included in the DCI indicates that the UE wakes up on a first set of carriers within a first DRX duration associated with the DCI, the UE wakes up on the first set of carriers within the first DRX duration; alternatively, if the DCI includes first indication information indicating that the UE is dormant on a first set of carriers for a first DRX duration associated with the DCI, the UE is dormant on the first set of carriers for the first DRX duration.

Alternatively, if the second indication information indicates both the behavior of the UE on the first set of carriers and the behavior of the UE on the second set of carriers, then if the second indication information indicates to sleep for the DRX duration associated with the DCI, the UE sleeps for the first DRX duration on the first set of carriers and for the second DRX duration on the second set of carriers; alternatively, if the second indication information indicates to wake up during the DRX duration associated with the DCI, the UE wakes up during the first DRX duration on the first set of carriers and wakes up during the second DRX duration on the second set of carriers.

Alternatively, if the DCI includes a first DCI including first indication information and a second DCI including second indication information indicating a behavior of the UE on the second set of carriers, the first indication information indicating a behavior of the UE on the first set of carriers. Then, if the first indication information included in the first DCI indicates that the UE wakes up on the first set of carriers within a first DRX duration associated with the first DCI, the UE wakes up on the first set of carriers within the first DRX duration; alternatively, if the first indication information included in the first DCI indicates to sleep on the first set of carriers for a first DRX duration associated with the first DCI, the UE sleeps on the first set of carriers for the first DRX duration. If the second indication information included in the second DCI indicates that the UE wakes up on the second group of carriers within a second DRX duration associated with the second DCI, the UE wakes up on the second group of carriers within the second DRX duration; alternatively, if the second indication information included in the second DCI indicates to sleep on the second set of carriers for a second DRX duration associated with the second DCI, the UE sleeps on the second set of carriers for the second DRX duration.

For a network device, if the DCP is not configured, the network device does not have to send the DCP nor does the UE have to monitor the DCP. If the DCP is configured, for example, the DCP is configured for the first set of carriers, the network device may normally transmit the DCP on the first set of carriers, and, to avoid that the UE sometimes cannot monitor the DCP, the network device also transmits DCI capable of implementing the DCP function. If this is the case, the UE may determine whether the DCP can be listened to on the first set of carriers, and if the DCP can be listened to by the UE, the UE may determine to sleep or wake up on the first set of carriers based on the listening result of the DCP without determining to sleep or wake up on the first set of carriers based on default (or protocol-specified) rules, second indication information, or first indication information, etc. Alternatively, if the UE is unable to listen to the DCP, the UE may determine to sleep or wake-up on the first set of carriers according to rules of default (or protocol specification) or according to the first indication information.

The embodiments shown in any of fig. 5, 7 or 10 mainly take into account the problem of combining two sets of DRX configurations with a wake-up signal. As can be seen from the foregoing description, the cross-carrier scheduling and the two-group DRX configuration are not used in combination. A fourth communication method is provided below to use cross-carrier scheduling in combination with two sets of DRX configurations to further reduce the power consumption of the UE.

Please refer to fig. 12, which is a flowchart of the method.

S121, the network device sends the second DCI on the first carrier, and correspondingly, the UE receives the second DCI from the network device on the first carrier.

The first carrier belongs to a first group of carriers, which includes one or more carriers configured for the UE, and is, for example, a part of carriers or all carriers included in the first group of carriers. For example, if the primary carrier configured by the network device for the UE belongs to a first set of carriers, the first carrier may be the primary carrier of the UE, and the network device may send the second DCI on the primary carrier.

The second DCI may be used to schedule data on the second set of carriers, e.g., the second DCI schedules new transmission data, or the second DCI may indicate new transmission of downlink data, or the second DCI may indicate new transmission of uplink data. The second DCI may schedule the UE to receive data or transmit data on a second set of carriers, that is, the second DCI enables cross-carrier scheduling. For an introduction to concepts of the first set of carriers and the second set of carriers, reference may be made to the embodiments shown in any of the figures 5, 7 or 10.

S122, the UE starts or restarts a second DRX inactivity timer, and the duration of the second DRX inactivity timer is set as the duration of the DRX inactivity timer configured by the second DRX configuration.

Since the second DCI schedules data on the second set of carriers, there may be data to be transmitted on the second set of carriers subsequently, so that it is necessary to prolong the DRX activation time of the UE on the second set of carriers to ensure that the UE can receive data or transmit data on the second set of carriers, and further ensure that the UE performs corresponding actions within the DRX activation time, for example, transmitting periodic uplink sounding reference signals (sounding reference signal, SRS), reporting channel state information (channel status information, CSI) through the PUCCH, reporting channel state information (channel status information, CSI) through the PUSCH, or reporting half-period, and so on.

To extend the DRX activation time of the UE on the second set of carriers, one implementation is to start or restart a second DRX inactivity timer. For example, the UE may start or restart the second DRX inactivity timer at the first time domain symbol after the second DCI is received. Wherein, in the first time domain symbol after the second DCI is received, if the second DRX inactivity timer is not running, the UE starts the second DRX inactivity timer; or if the second DRX inactivity timer is in an operation state in the first time domain symbol after the second DCI is received, the UE restarts the second DRX inactivity timer.

The second set of carriers applies a second DRX configuration, which may configure a DRX cycle, a DRX inactivity timer, a DRX retransmission timer, etc. The second DRX inactivity timer corresponds to the second set of carriers, or corresponds to the second DRX configuration, which may be understood as the DRX inactivity timer configured by the second DRX configuration is the second DRX inactivity timer. Then in S122, the UE may set the duration of the second inactivity timer to the original duration of the second DRX inactivity timer, i.e., the duration of the DRX inactivity timer configured by the second DRX configuration. By starting or restarting the second DRX inactivity timer, the DRX activation time of the UE on the second set of carriers is prolonged, so that the UE can receive data or transmit data on the second set of carriers.

The UE starts or restarts the second DRX inactivity timer, one implementation is that the UE defaults (or protocol specifies) and starts or restarts the second DRX inactivity timer upon receiving the second DCI. This approach can save signaling overhead without requiring additional notification by the network device.

Alternatively, the UE starts or restarts the second DRX inactivity timer, as indicated by the network device. For example, the second DCI may include second indication information, which may indicate to start or restart the second DRX inactivity timer. If this is the case, two situations are possible. One case is that if the second DCI includes second indication information, the second DRX inactivity timer is indicated to be started or restarted, and the UE starts or restarts the second DRX inactivity timer; and if the second DCI does not include the second indication information, indicating that the second DRX inactivity timer is not started and restarted, and the UE does not start and restart the second DRX inactivity timer. In this case, the second DCI may or may not include the second indication information, and signaling overhead of the second DCI can be saved. Or, in another case, if the second indication information included in the second DCI indicates to start or restart the second DRX inactivity timer, the UE starts or restarts the second DRX inactivity timer; and if the second indication information included in the second DCI indicates that the second DRX inactivity timer is not started and restarted, the UE does not start and restart the second DRX inactivity timer. And the indication is carried out through the second DCI, so that the UE is more clear of the behavior of the UE.

The second indication information may be carried through an existing field in the second DCI, for example, the second DCI includes an existing field having reserved (reserved) bits therein, and may be carried through reserved bits; alternatively, one or more bits may be newly added to the second DCI to carry the second indication information.

S123, the UE prolongs the DRX activation time of the UE on the first group of carriers.

Since there is data transmission on the second set of carriers and the second DCI is cross-carrier scheduling, it is also possible for the subsequent network device to schedule data on the second set of carriers by means of cross-carrier scheduling. In addition, the network device may also schedule data on the first set of carriers. Accordingly, the DRX activation time of the UE on the first set of carriers may be prolonged to receive DCI for scheduling data.

The UE may have different implementations to extend the DRX activation time of the UE on the first set of carriers, as will be described by way of example.

1. The first way is: and prolonging the DRX activation time of the UE on the first group of carriers through a first DRX deactivation timer.

The first set of carriers applies a first DRX configuration, which may configure a DRX cycle, a DRX inactivity timer, a DRX retransmission timer, etc. The first DRX inactivity timer corresponds to the first set of carriers, or corresponds to the first DRX configuration, which may be understood as the DRX inactivity timer configured by the first DRX configuration is the first DRX inactivity timer. Then in S123, the UE may start or restart the first DRX inactivity timer, in this way, the DRX activation time of the UE on the first set of carriers may be prolonged, enabling the UE to receive DCI on the first set of carriers.

The UE also needs to set the duration of the first DRX inactivity timer. As an alternative embodiment, the UE may set the duration of the first DRX inactivity timer to the original duration of the first DRX inactivity timer, i.e., the duration of the DRX inactivity timer configured by the first DRX configuration. The setting mode is simpler and is easy to realize by the UE.

Taking the example that the frequency of the first group of carriers belongs to FR1 and the frequency of the second group of carriers belongs to FR2, since the power consumption is larger when the UE operates in FR2, the UE may operate more on the first group of carriers, and thus the duration of the DRX inactivity timer configured by the first DRX configuration may be longer. If the duration of the first DRX inactivity timer is set to the duration of the DRX inactivity timer configured by the first DRX configuration, this may result in the UE's DRX activation time on the first set of carriers being prolonged too long, e.g., the network device may no longer schedule data for the second set of carriers, the UE may have entered DRX inactivity time on the second set of carriers, but the UE is still at DRX activation time on the first set of carriers, which may result in increased power consumption of the UE on the first set of carriers. Referring to fig. 13, the first DRX inactivity timer corresponding to FR1 is run longer than the second DRX inactivity timer corresponding to FR2, and the UE is still at DRX activation time on FR1 after the second DRX inactivity timer has stopped running. One solution to this is that the network device may send a first signaling, which may instruct the UE to stop the first DRX inactivity timer. The UE may stop running the first DRX inactivity timer after receiving the first signaling. The first signaling is, for example, DCI, or may be radio resource control (radio resource control, RRC) signaling or the like. But this requires additional signaling.

To solve the above problem, as another alternative embodiment, when the UE needs to set the duration of the first DRX inactivity timer, for example, when the first DRX inactivity timer is started, or before the first DRX inactivity timer is started, the UE does not set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the first DRX configuration, but sets the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration. For the UE to set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration, it may also be understood that the UE sets the duration of the first DRX inactivity timer to the duration of the second DRX inactivity timer. If this is done, the duration of the DRX activation time of the UE on the first set of carriers may be consistent with the duration of the DRX activation time of the UE on the second set of carriers, and the UE may not receive DCI on the first set of carriers for scheduling data for the second set of carriers nor cause excessive power consumption due to excessive DRX activation time on the first set of carriers. Referring to fig. 14, the operation time of the first DRX inactivity timer corresponding to FR1 is the same as the operation time of the second DRX inactivity timer corresponding to FR 2.

The UE may default or be specified by the protocol as to what duration the first DRX inactivity timer is to be. Alternatively, the UE may also determine, according to the corresponding situation, which duration to set the duration of the first DRX inactivity timer. For example, if the UE receives the first DCI on the first set of carriers before starting or restarting the first DRX inactivity timer, and the first DCI is used to schedule the UE to receive data or transmit data on the first set of carriers, the UE may set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the first DRX configuration to meet the requirement of the UE to receive data or transmit data on the first set of carriers, and also to meet the requirement of the UE to receive scheduling of data corresponding to the first set of carriers on the first set of carriers.

Considering a problem, before starting or restarting the first DRX inactivity timer, if the first DRX inactivity timer is in an operation state and if the remaining duration of the first DRX inactivity timer is longer than the duration of the DRX inactivity timer configured by the second DRX configuration, if the UE restarts the first DRX inactivity timer, the duration of the first DRX inactivity timer may be ignored, and complexity of UE processing may be increased. Thus, as an alternative embodiment, the UE does not have to start or restart the first DRX inactivity timer in any case, but may first determine whether the first DRX inactivity timer needs to be started or restarted. For example, before starting or restarting the first DRX inactivity timer, the UE may determine a size relationship between a remaining duration of the first DRX inactivity timer and a duration of the DRX inactivity timer configured by the second DRX configuration if the first DRX inactivity timer is in an active state. If the remaining duration of the first DRX inactivity timer is shorter than the duration of the DRX inactivity timer configured by the second DRX configuration, the UE may set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration; alternatively, the UE may not have to restart the first DRX inactivity timer if the remaining duration of the first DRX inactivity timer is longer than or equal to the duration of the DRX inactivity timer configured by the second DRX configuration. In this case, although the UE does not restart the first DRX inactivity timer, since the first DRX inactivity timer is in an active state and the remaining duration of the first DRX inactivity timer is longer than or equal to the duration of the DRX inactivity timer configured by the second DRX configuration, it indicates that the DRX activation time of the UE on the first set of carriers does not need to be prolonged additionally, but can already meet the requirements.

Whether the UE is to start the first DRX inactivity timer or not may be by default or specified by the protocol. For example, the protocol specifies that if the UE receives DCI on a first set of carriers for scheduling data on a second set of carriers, the UE starts a first DRX inactivity timer. Alternatively, whether the UE is to start the first DRX inactivity timer or not may also be configured by the network device. For example, the second DCI may include first indication information, which may indicate to start or restart the first DRX inactivity timer. If this is the case, two situations are possible. In one case, if the second DCI includes first indication information, the first DRX inactivity timer is indicated to be started or restarted, and the UE starts or restarts the first DRX inactivity timer; and if the second DCI does not include the first indication information, indicating that the first DRX inactivity timer is not started and restarted, and the UE does not start and restart the first DRX inactivity timer. In this case, the second DCI may or may not include the first indication information, and signaling overhead of the second DCI can be saved. Or, in another case, if the first indication information included in the second DCI indicates to start or restart the first DRX inactivity timer, the UE starts or restarts the first DRX inactivity timer; and if the first indication information included in the second DCI indicates that the first DRX inactivity timer is not started and restarted, the UE does not start and restart the first DRX inactivity timer. And the indication is carried out through the second DCI, so that the UE is more clear of the behavior of the UE.

Alternatively, if the second DCI includes the first indication information, the first indication information may indicate how to set the duration of the first DRX inactivity timer in addition to the UE starting or restarting the first DRX inactivity timer. For example, the first indication information may indicate that a timing duration of the first DRX inactivity timer is set to a duration of the DRX inactivity timer configured by the first DRX configuration, or indicate that a timing duration of the first DRX inactivity timer is set to a duration of the DRX inactivity timer configured by the second DRX configuration, and the UE may set the duration of the first DRX inactivity timer according to the first indication information. Alternatively, the second DCI may indicate how to set the duration of the first DRX inactivity timer by other information, for example, the second DCI may further include third indication information, which may indicate that the timing duration of the first DRX inactivity timer is set to the duration of the DRX inactivity timer configured by the first DRX configuration, or that the timing duration of the first DRX inactivity timer is set to the duration of the DRX inactivity timer configured by the second DRX configuration. The UE does not need to determine how the duration of the first DRX inactivity timer should be set by itself by indicating the setting mode of the duration of the first DRX inactivity timer through corresponding indication information, and the implementation of the UE is simplified.

2. The second way is: the UE extends the DRX activation time of the UE on the first set of carriers.

In the second manner, without the aid of the first DRX inactivity timer, the UE may extend the DRX activation time of the UE on the first set of carriers, e.g., extend the end time of the DRX activation time of the UE on the first set of carriers to be the same as the end time of the DRX activation time of the UE on the second set of carriers, since the end time of the second DRX inactivity timer, or the end time of the DRX activation time of the UE on the second set of carriers, is known to the UE. In this way, the duration of the DRX activation time of the UE on the first set of carriers is consistent with the duration of the DRX activation time of the UE on the second set of carriers, and the UE can receive DCI on the first set of carriers for scheduling data of the second set of carriers, nor can it consume too much power due to too much DRX activation time on the first set of carriers. And the mode also does not need to resort to the first DRX inactivity time timer, so that the power consumption caused by the maintenance of the first DRX inactivity time timer by the UE is reduced.

Referring to fig. 15, the UE lengthens the DRX activation time of the UE on the first set of carriers (the dotted box in fig. 15 represents the prolonged time) such that the operation time of the first DRX inactivity timer corresponding to FR1 is the same as the operation time of the second DRX inactivity timer corresponding to FR 2. It can be understood that, in the embodiment of the present application, the DRX activation time on the first set of carriers (i.e., the DRX activation time of the first DRX configuration) is defined as a union of the DRX activation time corresponding to the first DRX configuration on the first set of carriers and the DRX activation time corresponding to the second DRX configuration on the second set of carriers.

Wherein S122 and S123 may be performed simultaneously, or S122 may be performed before S123, or S122 may be performed after S123.

For example, if the UE (e.g., smart phone, smart watch, or smart bracelet, etc.) has a power saving requirement, the UE may send power saving capability information or a power saving indication to the network device, the power saving capability information indicating that the UE supports the first scheme, the power saving indication indicating that the UE has a power saving requirement, or indicating that the UE requests the first scheme to be applied. Alternatively, if the UE requests the application of the first scheme capable of saving energy, the UE may also send the energy saving capability information or the energy saving indication to the network device. Wherein the first scheme is a scheme provided by the embodiment shown in any one of fig. 5, 8, 10 or 12. After the network device receives the power saving capability information or the power saving indication from the UE, if the network device has configured the first DRX configuration, the second DRX configuration, and the DCP (or DCI) for the UE, the network device determines that the UE applies the first scheme. Alternatively, the network device may send power saving enable information or configuration information related to the first scheme to the UE to indicate that the UE is allowed to save power or to indicate that the UE is allowed to apply the first scheme. The UE can apply the first scheme after receiving the power saving enable information or the configuration information related to the first scheme from the network device. Or after the network device receives the power saving capability information or the power saving indication from the UE, if the network device configures only the first DRX configuration for the UE, the network device may send a second DRX configuration to the UE. After the UE receives the second DRX configuration, the first scheme can be applied. After the first scheme is applied, the UE can further reduce power consumption, namely reduce the consumed battery power and prolong the standby time of the UE.

In addition, the following three rules are introduced.

Rule 1, the time length of the first DRX activation time is greater than or equal to the time length of the second DRX activation time.

Optionally, the first set of carriers corresponds to a first DRX activation time, which for example includes all or part of the DRX activation time of the UE in the first DRX configuration on the first set of carriers. The second set of carriers corresponds to a second DRX activation time, which includes, for example, all or part of the DRX activation time of the UE on the second set of carriers in the second DRX configuration. Considering that a network device may schedule a UE to receive data or transmit data on a first set of carriers on a second set of carriers, the UE needs to receive scheduling information corresponding to the second set of carriers on the first set of carriers, e.g., carried in DCI transmitted over PDCCH. Then, if the time length of the first DRX active time is less than the time length of the second DRX active time, a situation may occur that the UE enters a dormant state on the first set of carriers, but the network device sends DCI for scheduling data transmission on the second set of carriers on the first set of carriers, at which time the UE may not receive the DCI due to dormancy, resulting in the UE being unable to transmit data on the second set of carriers. In order to reduce the probability of occurrence of such a situation, the embodiment of the present application proposes that the time length of the first DRX activation time is greater than or equal to the time length of the second DRX activation time, and in addition, the first DRX activation time may be enabled to cover the second DRX activation time in the time domain, for example, so that the second DRX activation time is located in the first DRX activation time in the time domain, or the second DRX activation time is enabled to coincide with the first DRX activation time in the time domain, so that the UE can receive the scheduling information from the network device on the first set of carriers.

The time length of the first DRX activation time is made to be greater than or equal to the time length of the second DRX activation time, for example, in one implementation, the duration of all or part of the timers configured by the first DRX configuration is made to be greater than or equal to the duration of the corresponding timers configured by the second DRX configuration. For example, the time length of the first DRX duration timer is made greater than or equal to the time length of the second DRX duration timer, the first DRX duration timer being configured by the first DRX configuration and the second DRX duration timer being configured by the second DRX configuration. For another example, the time period of the first DRX duration timer is made greater than or equal to the time period of the second DRX duration timer, and the time period of the first DRX inactivity timer is made greater than or equal to the time period of the second DRX inactivity timer, the first DRX inactivity timer being configured by the first DRX configuration and the second DRX inactivity timer being configured by the second DRX configuration. For another example, the time length of the first DRX duration timer is made greater than or equal to the time length of the second DRX duration timer, the time length of the first DRX inactivity timer is made greater than or equal to the time length of the second DRX inactivity timer, and the time length of the first DRX retransmission timer is made greater than or equal to the time length of the second DRX retransmission timer, the first DRX retransmission timer being configured by the first DRX configuration, and the second DRX retransmission timer being configured by the second DRX configuration.

Rule 1 may be specified by a protocol, or may be default, or may be configured by a network device.

Rule 2, configuring DCI on a first set of carriers to schedule data transmissions for a second set of carriers, and not configuring DCI on a second set of carriers to schedule data transmissions for the first set of carriers.

Wherein the frequencies of the second frequency range are larger than the frequencies of the first frequency range, e.g. the frequencies of the second set of carriers belong to FR2 and the frequencies of the first set of carriers belong to FR1. Since the frequency of FR2 is greater than that of FR1, the power consumption of the UE will be greater when the UE operates on the carrier of FR2, and thus, alternatively, if cross-carrier scheduling is configured, in this embodiment of the present application, the second set of carriers may be configured to be scheduled by the first set of carriers, that is, the DCI on the first set of carriers is configured to schedule the data transmission of the second set of carriers, and the DCI on the second set of carriers is not configured to schedule the data transmission of the first set of carriers. Therefore, the UE can complete data transmission on the second group of carriers only by monitoring the DCI on the first group of carriers, and does not need to monitor the DCI on the second group of carriers, so that the power consumption of the UE is saved. Rule 2 may be specified by a protocol, or may be default, or may be configured by a network device.

Rule 3, data transmission time on the second set of carriers scheduled on the first set of carriers, is within DRX activation time of the UE on the second set of carriers.

A situation may also occur if cross-carrier scheduling is supported. For example, if DCI on a first set of carriers is configured to schedule data transmission on a second set of carriers, then the transmission time of data on the second set of carriers scheduled by the DCI sent by the network device on the first set of carriers may be within DRX inactivity time of the UE on the second set of carriers. For example, referring to fig. 7, the network device transmits DCI on the carrier of FR1, which schedules data transmission on the carrier of FR 2. The UE receives the DCI On the first set of carriers in an On Duration of one DRX cycle, and the data transmission time scheduled by the DCI is, for example, T1 time in fig. 7, and at T1 time, the DRX inactivity timer of the UE On the second set of carriers has expired, so T1 is located in the DRX inactivity time of the UE On the second set of carriers. If this is the case, the UE also needs to receive PUSCH or PDSCH during the DRX inactivity time, which may bring additional power consumption to the UE. Therefore, optionally, the embodiments of the present application provide that the data transmission time of the network device on the second set of carriers scheduled on the first set of carriers needs to be located within the DRX activation time of the UE on the second set of carriers, so that the UE does not need to receive the PUSCH or PDSCH again on the second set of carriers within the DRX inactivity time, but can enter the sleep state to save power consumption. Rule 3 may be specified by a protocol, or may be default, or may be configured by a network device.

The three rules above may be applied in connection with the embodiment shown in fig. 5, or may be applied in connection with the embodiment shown in fig. 8, or may be applied in connection with the embodiment shown in fig. 10, or may be applied in connection with the embodiment shown in fig. 12. Alternatively, the three rules above may be applied separately, without combining with any of the method embodiments described above. In addition, when applied alone, one or more of the above rules may be applied, that is, any two or three of the above three rules may be applied in combination, or the above three rules may not be applied in combination, but may be applied separately. For example, rule 1 may be applied instead of rule 2 and rule 3; alternatively, rule 2 may be applied instead of rule 1 and rule 3; alternatively, rule 3 may be applied instead of rule 1 and rule 2; alternatively, rule 1 and rule 2 may be applied and rule 3 may not be applied; alternatively, rule 1 and rule 3 may be applied and rule 2 may not be applied; alternatively, rule 2 and rule 3 may be applied instead of rule 1; alternatively, rule 1, rule 2, and rule 3 may be applied.

The apparatus for implementing the above method in the embodiments of the present application is described below with reference to the accompanying drawings. Therefore, the above contents can be used in the following embodiments, and repeated contents are not repeated.

Fig. 16 is a schematic block diagram of a communication device 1600 provided in an embodiment of the present application. The communication apparatus 1600 is illustratively a terminal device, or a network device. Illustratively, the communications apparatus 1600 is capable of implementing the functionality of a UE described in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12. Alternatively, the communication apparatus 1600 can implement the functions of the network device described in the embodiment shown in fig. 10.

The communication device 1600 includes a transceiver unit 1620 and a processing unit 1610. Optionally, the communication device 1600 may further comprise a storage unit, which is capable of communicating with the processing unit 1610, not shown in fig. 16. Alternatively, communication device 1600 may not include a storage unit, which may be external to communication device 1600. Illustratively, the communication apparatus 1600 may be a UE, a chip applied to the UE or other combination device, component, etc. with the UE function, or the communication apparatus 1600 may be a network device, or a chip applied to the network device or other combination device, component, etc. with the network device function. When the communication apparatus 1600 is a UE or a network device, the processing unit 1610 may include a processor, for example, a baseband processor, which may include one or more central processing units (central processing unit, CPU) therein; the transceiver unit 1620 may be a transceiver, which may include an antenna, radio frequency circuitry, and the like. The transceiver may include a transmitter and a receiver, and the transceiver may implement functions of the transmitter and the receiver, or the transmitter and the receiver may be two functional modules separately deployed, which are collectively referred to as a transceiver in the embodiments of the present application. When the communication apparatus 1600 is a component having the above-mentioned UE or network device function, the transceiver unit 1620 may be a radio frequency unit, and the processing unit 1610 may be a processor, for example, a baseband processor. When the communication device 1600 is a chip system, the transceiver unit 1620 may be an input/output interface of a chip (e.g., a baseband chip), and the processing unit 1610 may be a processor of the chip system and may include one or more central processing units. It is to be appreciated that the processing unit 1610 in the embodiments of the present application may be implemented by a processor or processor-related circuit component, and the transceiver unit 1620 may be implemented by a transceiver or transceiver-related circuit component.

In one implementation, when the communication device 1600 is used to implement the functionality of a UE as described in the embodiment illustrated in fig. 5, the processing unit 1610 may be used to perform all operations performed by the UE in the embodiment illustrated in fig. 5, such as S51-S53, and/or other processes for supporting the techniques described herein. The transceiving unit 1620 may be configured to perform all of the receive and transmit operations performed by the UE in the embodiment illustrated in fig. 5, such as listening to a DCP, and/or other processes for supporting the techniques described herein.

In one implementation, when the communication device 1600 is used to implement the functionality of a UE as described in the embodiment shown in fig. 8, the processing unit 1610 may be used to perform all operations performed by the UE in the embodiment shown in fig. 8, except for transceiving operations, e.g., S81-S85, and/or other procedures for supporting the techniques described herein. The transceiving unit 1620 may be configured to perform all of the receive and transmit operations performed by the UE in the embodiment illustrated in fig. 8, such as listening to a DCP, and/or other processes for supporting the techniques described herein.

In one implementation, when the communication device 1600 is used to implement the functionality of a UE described in the embodiment shown in fig. 10, the processing unit 1610 may be used to perform all operations performed by the UE in the embodiment shown in fig. 10, except for transceiving operations, such as S102-S103, and/or other procedures for supporting the techniques described herein. The transceiving unit 1620 may be configured to perform all of the receive and transmit operations performed by the UE in the embodiment illustrated in fig. 10, e.g., S101, and/or other processes for supporting the techniques described herein.

In one implementation, when the communications apparatus 1600 is used to implement the functionality of a network device described in the embodiment illustrated in fig. 10, the processing unit 1610 may be used to perform all operations performed by the network device in the embodiment illustrated in fig. 10, except for transceiving operations, and/or other procedures used to support the techniques described herein. The transceiving unit 1620 may be configured to perform all of the receive and transmit operations performed by the network device in the embodiment illustrated in fig. 10, e.g., S101, and/or other processes for supporting the techniques described herein.

In one implementation, when the communication device 1600 is used to implement the functionality of a UE described in the embodiment shown in fig. 12, the processing unit 1610 may be used to perform all operations performed by the UE in the embodiment shown in fig. 12, except for transceiving operations, such as S122-S123, and/or other procedures for supporting the techniques described herein. The transceiving unit 1620 may be configured to perform all of the receiving and transmitting operations performed by the UE in the embodiment illustrated in fig. 12, e.g., S121, and/or other procedures for supporting the techniques described herein.

In addition, the transceiver unit 1620 may be a functional module capable of performing both transmission and reception operations, for example, the transceiver unit 1620 may be configured to perform all transmission and reception operations performed by the first terminal device or the network device (e.g., the core network device or the access network device) in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12. For example, the transceiving unit 1620 may be considered to be a receiving unit when a receiving operation is performed, and the transceiving unit 1620 may be considered to be a transmitting unit when a transmitting operation is performed. Alternatively, the transceiver unit 1620 may be two functional modules, where the transceiver unit 1620 may be regarded as a generic term of the two functional modules, and the two functional modules include a receiving unit and a transmitting unit, where the transmitting unit is configured to perform a transmitting operation, for example, the transmitting unit may be configured to perform all the transmitting operations performed by the first terminal device or the network device in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12; the receiving unit is configured to perform the receiving operation, for example, the receiving unit may be configured to perform all the receiving operations performed by the first terminal device or the network device in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12.

Regarding the functions that the processing unit 1610 and the transceiver unit 1620 can specifically implement, reference may be made to the description of the operations performed by the terminal device in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12, or the description of the operations performed by the network device (for example, the access network device or the core network device) in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12, which are not repeated.

The embodiment of the application also provides a communication device which can be a terminal device or a circuit. The communication means may be adapted to perform the actions performed by the terminal device in the various method embodiments described above.

Fig. 17 shows a simplified schematic diagram of the structure of a terminal device when the communication device is a terminal device. The terminal device is illustrated as a mobile phone in fig. 17 for easy understanding and convenient illustration. As shown in fig. 17, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used for processing communication protocols and communication data, controlling the terminal equipment, executing software programs, processing data of the software programs and the like. The memory is mainly used for storing software programs and data. The radio frequency circuit is mainly used for converting a baseband signal and a radio frequency signal and processing the radio frequency signal. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used for receiving data input by a user and outputting data to the user. It should be noted that some kinds of terminal apparatuses may not have an input/output device.

When data need to be sent, the processor carries out baseband processing on the data to be sent and then outputs a baseband signal to the radio frequency circuit, and the radio frequency circuit carries out radio frequency processing on the baseband signal and then sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data. For ease of illustration, only one memory and processor is shown in fig. 17. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, which is not limited by the embodiments of the present application.

In the embodiment of the present application, the antenna and the radio frequency circuit with the transmitting and receiving functions may be regarded as a transmitting and receiving unit of the terminal device (the transmitting and receiving unit may be one functional unit, which can implement the transmitting function and the receiving function, or the transmitting and receiving unit may also include two functional units, which are a receiving unit capable of implementing the receiving function and a transmitting unit capable of implementing the transmitting function, respectively), and the processor with the processing function may be regarded as a processing unit of the terminal device. As shown in fig. 17, the terminal device includes a transceiving unit 1710 and a processing unit 1720. The transceiver unit may also be referred to as a transceiver, transceiver device, etc. The processing unit may also be called a processor, a processing board, a processing module, a processing device, etc. Alternatively, a device for implementing a receiving function in the transceiver 1710 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiver 1710 may be regarded as a transmitting unit, i.e., the transceiver 1710 includes a receiving unit and a transmitting unit. The transceiver unit may also be referred to as a transceiver, transceiver circuitry, or the like. The receiving unit may also be referred to as a receiver, or receiving circuit, among others. The transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

It should be understood that the transceiver 1710 is configured to perform the transmitting operation and the receiving operation on the terminal device side in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12, and the processing unit 1720 is configured to perform other operations on the first terminal device side than the transmitting operation in the embodiment shown in fig. 5 or the embodiment shown in fig. 8 or the embodiment shown in fig. 10 or the embodiment shown in fig. 12.

When the communication device is a chip-like device or circuit, the device may comprise a transceiver unit and a processing unit. The receiving and transmitting unit can be an input and output circuit and/or a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit.

It should be appreciated that the processors referred to in the embodiments of the present application may be CPUs, but may also be other general purpose processors, digital signal processors (digital signal processor, DSPs), application specific integrated circuits (application specific integrated circuit, ASICs), off-the-shelf programmable gate arrays (field programmable gate array, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Note that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) is integrated into the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The foregoing computer-readable storage media can be any available media that can be accessed by a computer. Taking this as an example but not limited to: the computer readable medium may include random access memory (random access memory, RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read only memory, EEPROM), compact disc read-only memory (compact disc read-only memory, CD-ROM), universal serial bus flash disk (universal serial bus flash disk), a removable hard disk, or other optical disk storage, magnetic disk storage media, or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. In addition, by way of example and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), or direct memory bus RAM (DR RAM).

The foregoing is merely specific embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art may easily think about changes or substitutions within the technical scope of the embodiments of the present application, and the changes or substitutions are intended to be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

the terminal equipment determines whether to monitor the DCP in a first monitoring opportunity of the downlink control information DCP with the cyclic redundancy check, which is scrambled by using the energy-saving wireless network temporary identifier;

in the case that the terminal device determines not to monitor the DCP in the first DCP monitoring occasion, on a first set of carriers, the terminal device wakes up in a first Discontinuous Reception (DRX) duration associated with the first DCP monitoring occasion, and on a second set of carriers, the terminal device wakes up or sleeps in a second DRX duration associated with the first DCP monitoring occasion, wherein the first set of carriers includes one or more carriers configured to the terminal device, the first set of carriers applies a first DRX configuration, the first DRX duration corresponds to the first DRX configuration, the second set of carriers includes one or more carriers configured to the terminal device, the second set of carriers applies a second DRX configuration, and the second DRX duration corresponds to the second DRX configuration.

2. The method of claim 1, wherein the first DCP listening occasion is configured on the first set of carriers.

3. The method of claim 1 or 2, wherein the first DRX duration is located temporally after the first DCP listening occasion.

4. The method of claim 1 or 2, wherein the terminal device determining whether to listen to the DCP within the first DCP listening occasion comprises:

when the number of the sizes of the downlink control information DCI which can be monitored at most is larger than or equal to the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the first DCP monitoring time; or under the condition that the number of the sizes of the DCIs which can be monitored at most is smaller than the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines not to monitor the DCP in the monitoring time of the first DCP; or alternatively, the first and second heat exchangers may be,

5. The method according to claim 1 or 2, characterized in that the method further comprises:

the terminal device receives configuration information from the network device, wherein the configuration information is used for configuring: in case the terminal device does not listen during a DCP listening occasion, the terminal device wakes up or sleeps during the second DRX duration associated with the DCP listening occasion.

6. The method according to claim 1 or 2, characterized in that the method further comprises:

In the case that the terminal device determines to monitor a DCP in the first DCP monitoring occasion, the terminal device monitors the DCP in the first DCP monitoring occasion;

the terminal device sleeps or wakes up in the first DRX duration on the first group of carriers and sleeps or wakes up in the second DRX duration on the second group of carriers according to the monitoring condition of the DCP.

7. The method of claim 6, wherein the terminal device sleeps on the first set of carriers for the first DRX duration and on the second set of carriers for the second DRX duration based on listening to a DCP, comprising:

in the event that the terminal device receives a first DCP from a network device within the first DCP listening occasion and the first DCP indicates sleep, on the first set of carriers, the terminal device sleeps for the first DRX duration and, on the second set of carriers, the terminal device sleeps for the second DRX duration; or alternatively, the first and second heat exchangers may be,

in the event that the terminal device does not receive DCP from a network device within the first DCP listening occasion, the terminal device sleeps for the first DRX duration on the first set of carriers and the terminal device sleeps for the second DRX duration on the second set of carriers.

8. The method of claim 6, wherein the terminal device wakes up on the first set of carriers for the first DRX duration and on the second set of carriers for the second DRX duration based on listening to a DCP, comprising:

in the case where the terminal device receives a first DCP from a network device within the first DCP listening occasion and the first DCP indicates a wakeup, on the first set of carriers, the terminal device wakes up for the first DRX duration, and on the second set of carriers, the terminal device wakes up for the second DRX duration; or alternatively, the first and second heat exchangers may be,

in case the terminal device receives a first DCP from a network device within the first DCP listening occasion, the terminal device wakes up during the first DRX duration on the first set of carriers and the terminal device wakes up during the second DRX duration on the second set of carriers.

9. The method of claim 6, wherein the terminal device sleeps or wakes up for the first DRX duration on the first set of carriers and sleeps or wakes up for the second DRX duration on the second set of carriers according to a listening situation to a DCP, comprising:

Receiving a first DCP from a network device in the first DCP monitoring occasion by the terminal device, wherein the first DCP comprises first indication information and second indication information; wherein,

in case the first indication information indicates wake-up and the second indication information indicates wake-up, on the first set of carriers, the terminal device wakes up within the first DRX duration and, on the second set of carriers, the terminal device wakes up within the second DRX duration; or alternatively, the first and second heat exchangers may be,

in the case where the first indication information indicates sleep and the second indication information indicates sleep, on the first set of carriers, the terminal device sleeps for the first DRX duration and, on the second set of carriers, the terminal device sleeps for the second DRX duration; or alternatively, the first and second heat exchangers may be,

in the case that the first indication information indicates wake-up and the second indication information indicates sleep, on the first set of carriers, the terminal device wakes up for the first DRX duration and, on the second set of carriers, the terminal device sleeps for the second DRX duration; or alternatively, the first and second heat exchangers may be,

In case the first indication information indicates sleep and the second indication information indicates wake-up, the terminal device sleeps for the first DRX duration on the first set of carriers and the terminal device wakes up for the second DRX duration on the second set of carriers.

10. The method of claim 6, wherein the terminal device sleeps for the first DRX duration on the first set of carriers, comprising:

the terminal device does not start and does not restart a first DRX duration timer at a starting time of the first DRX duration, the first DRX duration timer corresponding to the first DRX configuration.

11. The method of claim 6, wherein the terminal device wakes up during the first DRX duration on the first set of carriers, comprising:

and the terminal equipment starts or restarts a first DRX duration timer at the starting moment of the first DRX duration, wherein the first DRX duration timer corresponds to the first DRX configuration.

12. The method of claim 6, wherein the terminal device sleeps for the second DRX duration on the second set of carriers, comprising:

The terminal device does not start and does not restart a second DRX duration timer at the starting time of the second DRX duration, where the second DRX duration timer corresponds to the second DRX configuration.

13. The method of claim 6, wherein on the second set of carriers, the terminal device wakes up during the second DRX duration, comprising:

and the terminal equipment starts or restarts a second DRX duration timer at the starting moment of the second DRX duration, wherein the second DRX duration timer corresponds to the second DRX configuration.

14. The method according to any one of claim 1, 2, 7 to 13, wherein,

the frequency range to which the first set of carriers belongs is different from the frequency range to which the second set of carriers belongs; or alternatively, the first and second heat exchangers may be,

the frequency corresponding to the frequency range of the second group of carriers is larger than the frequency corresponding to the frequency range of the first group of carriers; or alternatively, the first and second heat exchangers may be,

the length of the DRX activation time corresponding to the first group of carriers is greater than or equal to the length of the DRX activation time corresponding to the second group of carriers.

15. A method of communication, comprising:

in the case that the terminal device determines not to monitor the DCP in a first downlink control information, DCP, monitoring occasion with cyclic redundancy check using power saving wireless network temporary identity scrambling, the terminal device determines whether to monitor the DCP in a second DCP monitoring occasion, the first DCP monitoring occasion being configured on a first set of carriers, the second DCP monitoring occasion being configured on a second set of carriers, the first set of carriers comprising one or more carriers configured to the terminal device, the first set of carriers applying a first discontinuous reception, DRX, configuration, the second set of carriers comprising one or more carriers configured to the terminal device, the second set of carriers applying a second DRX configuration;

And under the condition that the terminal equipment determines to monitor the DCP in the second DCP monitoring occasion, the terminal equipment monitors the DCP in the second DCP monitoring occasion and sleeps or wakes up on the second group of carriers in a second DRX duration time associated with the second DCP monitoring occasion according to the monitoring condition of the DCP, wherein the second DRX duration time corresponds to the second DRX configuration.

16. The method of claim 15, wherein the method further comprises:

the terminal device determines whether to listen to a DCP within the first DCP listening occasion.

17. The method according to claim 15 or 16, characterized in that the method further comprises:

and in the case that the terminal equipment determines not to monitor the DCP in the second DCP monitoring occasion, the terminal equipment wakes up in the second DRX duration on the second group of carriers.

18. The method according to claim 15 or 16, characterized in that the method further comprises:

in the case that the terminal device determines to monitor the DCP in the first DCP monitoring occasion, the terminal device sleeps or wakes up on the first group of carriers in a first DRX duration associated with the first DCP monitoring occasion according to the monitoring situation of the DCP, and sleeps or wakes up on the second group of carriers in the second DRX duration, wherein the first DRX duration corresponds to the first DRX configuration.

19. The method according to claim 15 or 16, characterized in that the method further comprises:

in the event that the terminal device determines to monitor DCP during the first DCP monitoring occasion, the terminal device does not monitor during the second DCP monitoring occasion on the second set of carriers.

20. The method according to claim 15 or 16, characterized in that the method further comprises:

and under the condition that the terminal equipment determines not to monitor the DCP in the first DCP monitoring occasion, on the first group of carriers, the terminal equipment wakes up in a first DRX duration time associated with the first DCP monitoring occasion, wherein the first DRX duration time corresponds to the first DRX configuration.

21. The method of claim 16, wherein the terminal device determining whether to listen to a DCP within the first DCP listening occasion comprises:

22. The method of any of claims 15, 16, 21, wherein the terminal device determining whether to listen to the DCP within the second DCP listening occasion comprises:

in the case that the time domain position of the second DCP monitoring opportunity is located in a second DRX activation time, the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity; or, in the case that the time domain position of the second DCP monitoring opportunity is not located or is partially located in the second DRX activation time, the terminal device determines to monitor the DCP in the first DCP monitoring opportunity; the second DRX activation time is a DRX activation time corresponding to the second DRX configuration; or alternatively, the first and second heat exchangers may be,

when the number of the sizes of the DCIs which can be monitored at most is larger than or equal to the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the second DCP monitoring occasion; or under the condition that the number of the sizes of the DCIs which can be monitored at most is smaller than the number of the sizes of the DCIs which the terminal equipment needs to monitor, the terminal equipment determines not to monitor the DCP in the second DCP monitoring time; or alternatively, the first and second heat exchangers may be,

when the time domain position of the second DCP monitoring opportunity is located in a second DRX activation time and the number of the size of DCI which can be monitored at most is larger than or equal to the number of the size of DCI which the terminal equipment needs to monitor, the terminal equipment determines to monitor the DCP in the second DCP monitoring opportunity; or when the time domain position of the second DCP monitoring opportunity is located in the second DRX activation time and the number of the sizes of the DCI that can be monitored at most is smaller than the number of the sizes of the DCI that the terminal device needs to monitor, the terminal device determines that the DCP is not monitored in the second DCP monitoring opportunity.

23. The method of any of claims 15, 16, 21, wherein the terminal device determining not to listen to DCP for the first DCP listening occasion and determining to listen to DCP for the second DCP listening occasion comprises:

in the case that the time domain position of the first DCP listening occasion is located within a first DRX activation time and the time domain position of the second DCP listening occasion is not located or is partially located within a second DRX activation time, the terminal device determines not to listen to the DCP within the first DCP listening occasion and determines to listen to the DCP within the second DCP listening occasion.

24. A terminal device, comprising:

one or more processors;

one or more memories;

and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, the one or more computer programs comprising instructions, which when executed by the one or more processors of the terminal device, cause the terminal device to perform the method of any of claims 1-14, or cause the terminal device to perform the method of any of claims 15-23.

25. A computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 14 or causes the computer to perform the method of any one of claims 15 to 23.

26. A chip comprising one or more processors and a communication interface, the one or more processors configured to read instructions to perform the method of any one of claims 1-14 or to perform the method of any one of claims 15-23.