CN114286429B - A communication method and device - Google Patents

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

A communication method and device

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on September 27, 2020, with application number 202011032366.9 and application name “A DCP monitoring method, terminal and network device”, the entire contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a communication method and device.

Background technique

In the fifth generation mobile communication technology (5G), user equipment (UE) needs to further save power consumption. To this end, an indication signal is introduced under the current discontinuous reception (DRX) mechanism, and the indication signal is the physical downlink control channel wake-up signal (PDCCH-WUS). The indication signal can indicate whether the UE needs to be awakened or whether it can sleep during the subsequent DRX "activation time". PDCCH-WUS is also called downlink control information with cyclic redundancy check scrambled by PS-radio network temporary identity (DCP) scrambled by power saving radio network tempory identity (PS-RNTI) in the standard, and the signal form of DCP can be DCI. At present, it is stipulated that when a monitoring opportunity arrives, if all DCP monitoring occasions (DCP occasion(s)) included in this monitoring opportunity are within the DRX active time (active time), the UE does not monitor in this monitoring opportunity, and the UE wakes up by default within the duration (On Duration) of the DRX cycle associated with this monitoring opportunity; and if at least one DCP monitoring occasion included in this monitoring opportunity is within the DRX non-active time (non-active time), the UE monitors in the DCP monitoring occasion within the DRX non-active time. Among them, a monitoring opportunity can include one or more DCP monitoring occasions (DCP occasion(s)).

Currently, user equipment (UE) in a radio resource control (RRC) connected state can support two discontinuous reception (DRX) configurations. However, the two DRX configuration technologies are not currently used in combination with wake-up signals, which affects the flexibility of base station configuration. In addition, the introduction of two DRX configurations is to save functions, and the purpose of the wake-up signal is also to save power consumption. If the two cannot be combined, the purpose of further reducing UE power consumption cannot be achieved.

Summary of the invention

The embodiments of the present application provide a communication method and device for reducing the power consumption of a UE.

In a first aspect, a first communication method is provided, which can be executed by a terminal device, or by a chip system, and the chip system can realize the functions of the terminal device. The terminal device is configured with a first group of carriers and a second group of carriers, the first group of carriers belongs to FR1, the first group of carriers includes 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 belongs to FR2, the second group of carriers includes one or more carriers configured to the terminal device, the second group of carriers applies a second DRX configuration, and the second DRX duration corresponds to the second DRX configuration. The method includes: when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, and the first DCP monitoring opportunity is configured on the first group of carriers. On a first group of carriers, the terminal device wakes up within a first DRX duration associated with the first DCP listening opportunity, and, on a second group of carriers, the terminal device wakes up or sleeps within a second DRX duration associated with the first DCP listening opportunity 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 a network device; or, in a case where the time domain position of the first DCP listening opportunity is not located within or partially located within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP listening opportunity, then the terminal device monitors the DCP within the first DCP listening opportunity; the terminal device sleeps or wakes up within the first DRX duration on the first group of carriers according to an indication of the monitored DCP, and sleeps or wakes up within the second DRX duration on the second group of carriers.

In an embodiment of the present application, the two DRX configuration technologies can be used in combination with the wake-up signal, which helps to further reduce the power consumption of the terminal device. And the behavior of the terminal device in the combined case is specified, for example, the monitoring of the DCP monitoring opportunity corresponding to the first group of carriers by the terminal device 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, which reduces the power consumption of the terminal device monitoring the DCP. Moreover, the monitoring situation of the terminal device on one group of carriers can be applied to two groups of carriers, so that both groups of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two groups of carriers.

In a first aspect, a first communication method is provided, which can be executed by a terminal device or by a chip system, and the chip system can realize the functions of the terminal device. The method includes: the terminal device determines whether to monitor the DCP within a first DCP monitoring opportunity; when the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, on a first group of carriers, the terminal device wakes up within a first DRX duration associated with the first DCP monitoring opportunity, and, on a second group of carriers, the terminal device wakes up or sleeps within a second DRX duration associated with the first DCP monitoring opportunity, wherein the first group of carriers includes 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 includes one or more carriers configured to the terminal device, the second group of carriers applies a second DRX configuration, and the second DRX duration corresponds to the second DRX configuration.

In an embodiment of the present application, two DRX configuration technologies can be used in combination with a wake-up signal, and the behavior of the terminal device in the combined case is specified. For example, the monitoring of the DCP monitoring timing corresponding to the first group of carriers by the terminal device 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, thereby reducing the power consumption of the terminal device monitoring the DCP. Moreover, the monitoring of the terminal device on one group of carriers can be applied to two groups of carriers, so that both groups of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two groups of carriers.

In combination with the second aspect, in a first optional implementation of the second aspect, the first DCP monitoring opportunity is configured on the first group of carriers.

The network device does not need to configure the DCP monitoring opportunity for the second group of carriers. The terminal device only needs to monitor during the DCP monitoring opportunity on the first group of carriers, and the monitoring result can be applied to both groups of carriers. In this way, both groups of carriers can use the DCP mechanism to reduce the power consumption of the terminal device. In addition, the terminal device does not need to monitor the DCP on the second group of carriers, which further reduces the power consumption of the terminal device monitoring the DCP.

In combination with the second aspect or the first optional implementation of the second aspect, in a second optional implementation of the second aspect, the first DRX duration is located after the first DCP monitoring opportunity in the time domain.

On the first group of carriers, one or more DRX cycles located after the first DCP listening opportunity in the time domain can be associated with the first DCP listening opportunity. As for which DRX cycles the first DCP listening opportunity is associated with, it can be specified by the protocol or configured by the network device. If the first DCP listening opportunity is associated with multiple DRX cycles, these multiple DRX cycles can be continuous or discontinuous in the time domain. The first DRX duration may include the duration of all or part of the DRX cycles associated with the first DCP listening opportunity under the first DRX configuration, or in other words, the first DRX duration may include the duration of all or part of the DRX cycles associated with the first DCP listening opportunity on the first group of carriers.

In combination with 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 terminal device determines whether to monitor the DCP within the first DCP monitoring opportunity, including:

In a case where the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, in a case where the time domain position of the first DCP monitoring opportunity is not within or partially within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein the first DRX activation time is the DRX activation time corresponding to the first DRX configuration; or,

In a case where the maximum number of sizes of DCIs that can be monitored is greater than or equal to the number of sizes of DCIs that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, in a case where the maximum number of sizes of DCIs that can be monitored is less than the number of sizes of DCIs that the terminal device needs to monitor, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or,

When the time domain position of the first DCP monitoring opportunity is within the first DRX activation time and the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time and the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; wherein, the first DRX activation time is the DRX activation time corresponding to the first DRX configuration.

The terminal device may have different determination methods to determine whether to listen to the DCP within the first DCP listening opportunity. For example, the terminal device may determine it based on the time domain position of the first DCP listening opportunity. This determination method is easy to implement for the terminal device and is also compatible with existing technologies. Alternatively, the terminal device may determine it based on the size budget of the DCI. This determination method is relatively simple and reasonable. Alternatively, the terminal device may also combine these two determination methods to make a determination together, which can make the determination result more accurate. The embodiments of the present application provide a variety of determination methods. Which determination method to choose can be decided by the terminal device itself, or configured by the network device, or by default, or by protocol regulations, etc.

In combination with the first aspect or any optional implementation manner from 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 also includes: the terminal device receives configuration information from a network device, and the configuration information is used to configure: when the terminal device does not listen during the DCP listening opportunity, the terminal device wakes up or sleeps during the second DRX duration associated with the DCP listening opportunity.

If the terminal device does not monitor during a DCP monitoring period on the first group of carriers, whether the terminal device wakes up or sleeps during the DRX duration associated with the DCP monitoring period may be a default rule, or may be specified by a protocol, or may be configured by a network device. If configured by a network device, the network device may be configured according to the service transmission situation of the terminal device on the second group of carriers, so that the sleep or wake-up of the terminal device on the second group of carriers better meets the service needs of the terminal device.

In combination with the first aspect or any optional implementation manner from the first optional implementation manner to the fourth optional implementation manner of the first aspect, in the fifth optional implementation manner of the first aspect, the method also includes: when the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, the terminal device monitors the DCP within the first DCP monitoring opportunity; the terminal device sleeps or wakes up within the first DRX duration on the first group of carriers according to the monitoring situation of the DCP, and sleeps or wakes up within the second DRX duration on the second group of carriers.

If the terminal device listens during the first DCP listening opportunity, the terminal device sleeps or wakes up on the two groups of carriers according to the instructions of the DCP listened during the first DCP listening opportunity. That is, the listening result of the terminal device during the first DCP listening opportunity can guide the behavior of the terminal device on the two groups of carriers, reducing the process of the terminal device listening to DCP and saving power consumption.

In combination with the fifth optional implementation of the first aspect, in the sixth optional implementation of the first aspect, the terminal device sleeps during the first DRX duration on the first group of carriers and sleeps during the second DRX duration on the second group of carriers according to the monitoring status of the DCP, including: when the terminal device receives the first DCP from the network device during the first DCP monitoring opportunity and the first DCP indicates sleep, the terminal device sleeps during the first DRX duration on the first group of carriers and the terminal device sleeps during the second DRX duration on the second group of carriers; or, when the terminal device does not receive the DCP from the network device during the first DCP monitoring opportunity, the terminal device sleeps during the first DRX duration on the first group of carriers and the terminal device sleeps during the second DRX duration on the second group of carriers.

In combination with the fifth optional implementation of the first aspect, in the seventh optional implementation of the first aspect, the terminal device wakes up on the first group of carriers within the first DRX duration and wakes up on the second group of carriers within the second DRX duration according to the monitoring of the DCP, including: when the terminal device receives the first DCP from the network device within the first DCP monitoring opportunity and the first DCP indicates wake-up, the terminal device wakes up on the first group of carriers within the first DRX duration and the terminal device wakes up on the second group of carriers within the second DRX duration; or, when the terminal device receives the first DCP from the network device within the first DCP monitoring opportunity, the terminal device wakes up on the first group of carriers within the first DRX duration and the terminal device wakes up on the second group of carriers within the second DRX duration.

In combination with the fifth optional implementation manner of the first aspect, in the eighth optional implementation manner of the first aspect, the terminal device sleeps or wakes up on the first group of carriers during the first DRX duration, and sleeps or wakes up on the second group of carriers during the second DRX duration according to the monitoring status of the DCP, including: the terminal device receives a first DCP from the network device during the first DCP monitoring opportunity, and the first DCP includes first indication information and second indication information; wherein, when the first indication information indicates wakeup, and the second indication information indicates wakeup, on the first group of carriers, the terminal device wakes up during the first DRX duration, and, on the second group of carriers, the terminal device wakes up during the second DRX duration; or, when the first indication information indicates wakeup In the case where the first indication information indicates sleep, and the second indication information indicates sleep, on the first group of carriers, the terminal device sleeps during the first DRX duration, and, on the second group of carriers, the terminal device sleeps during the second DRX duration; or, in the case where the first indication information indicates wakeup, and the second indication information indicates sleep, on the first group of carriers, the terminal device wakes up during the first DRX duration, and, on the second group of carriers, the terminal device sleeps during the second DRX duration; or, in the case where the first indication information indicates sleep, and the second indication information indicates wakeup, on the first group of carriers, the terminal device sleeps during the first DRX duration, and, on the second group of carriers, the terminal device wakes up during the second DRX duration.

In combination with any optional implementation of the fifth optional implementation of the first aspect to the eighth optional implementation of the first aspect, in the ninth optional implementation of the first aspect, on the first group of carriers, the terminal device sleeps during the first DRX duration, including: the terminal device does not start and restart the first DRX duration timer at the starting time of the first DRX duration, and the first DRX duration timer corresponds to the first DRX configuration.

In combination with any optional implementation of the fifth optional implementation of the first aspect to the ninth optional implementation of the first aspect, in the tenth optional implementation of the first aspect, on the first group of carriers, the terminal device wakes up within the first DRX duration, including: the terminal device starts or restarts a first DRX duration timer at the start time of the first DRX duration, and the first DRX duration timer corresponds to the first DRX configuration.

In combination with any optional implementation of the fifth optional implementation of the first aspect to the tenth optional implementation of the first aspect, in the eleventh optional implementation of the first aspect, on the second group of carriers, the terminal device sleeps during the second DRX duration, including: the terminal device does not start and restart the second DRX duration timer at the starting time of the second DRX duration, and the second DRX duration timer corresponds to the second DRX configuration.

In combination with any optional implementation of the fifth optional implementation of the first aspect to the eleventh optional implementation of the first aspect, in the twelfth optional implementation of the first aspect, on the second group of carriers, the terminal device wakes up within the second DRX duration, including: the terminal device starts or restarts a second DRX duration timer at the start time of the second DRX duration, and the second DRX duration timer corresponds to the second DRX configuration.

Through the above solution, a method for waking up or sleeping the terminal device within the DRX duration is provided.

In combination with the first aspect or any optional implementation manner from the first optional implementation manner to the twelfth optional implementation manner of the first aspect, in the thirteenth optional implementation manner of the first aspect, the frequency range to which the first group of carriers belongs is different from the frequency range to which the second group 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 of the two groups of carriers configured for the terminal device are different, so that the terminal device can work in a larger frequency range. For example, 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 frequency of the second group of carriers is greater than the frequency of the first group of carriers, the power consumption of the terminal device when working on the second group of carriers will be greater. Therefore, the embodiment of the present application allows the terminal device to only monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, thereby saving the power consumption caused by the terminal device working on the second group of carriers. In addition, the network device may send DCI on the first group of carriers, and the DCI is used to schedule data on the second group of carriers. Therefore, the terminal device may need to receive scheduling information for the second group of carriers on the first group of carriers. To this end, the length of the DRX activation time corresponding to the first group of carriers can be made greater than or equal to the length of the DRX activation time corresponding to the second group of carriers. 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 device can receive the scheduling information corresponding to the second group of carriers within the DRX activation time of the first group of carriers, reducing the probability that the terminal device cannot receive data or send data on the second group of carriers due to the inability to receive scheduling information, and reducing service transmission delay.

In a second aspect, a second communication method is provided, which can be executed by a terminal device or by a chip system, and the chip system can realize the function of the terminal device. The method includes: when the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity, the terminal device determines whether to monitor the DCP in the second DCP monitoring opportunity, the first DCP monitoring opportunity is configured on a first group of carriers, the second DCP monitoring opportunity is configured on a second group of carriers, the first group of carriers includes one or more carriers configured to the terminal device, the first group of carriers apply a first DRX configuration, the second group of carriers includes one or more carriers configured to the terminal device, and the second group of carriers apply a second DRX configuration; when the terminal device determines to monitor the DCP in the second DCP monitoring opportunity, the terminal device monitors the DCP in the second DCP monitoring opportunity, and according to the monitoring situation of the DCP, on the second group of carriers, sleeps or wakes up in the second DRX duration associated with the second DCP monitoring opportunity, and the second DRX duration corresponds to the second DRX configuration.

In an embodiment of the present application, two DRX configuration technologies can be used in combination with a wake-up signal, and the behavior of the terminal device in the combined case is specified. For example, the UE preferentially monitors the first DCP listening opportunity. If it can monitor the first DCP listening opportunity, the UE does not need to monitor the second DCP listening opportunity, so as to save the power consumption caused by the UE monitoring the DCP listening opportunity. If the UE cannot monitor the first DCP listening opportunity, the UE can also determine whether it can monitor the second DCP listening opportunity, so that the UE's behavior is carried out as much as possible under the indication of the monitoring result, so as to better meet the requirements of the network device. In an embodiment of the present application, the network device can configure the second DCP listening opportunity for the second group of carriers, so that the network device has stronger control over the behavior of the UE on the second group of carriers, and also increases the flexibility of the network device scheduling.

In combination with the second aspect, in a first optional implementation of the second aspect, the method further includes: the terminal device determines whether to monitor the DCP within the first DCP monitoring opportunity.

In combination with the second aspect or the first optional implementation of the second aspect, in the second optional implementation of the second aspect, the method also includes: when the terminal device determines not to listen to the DCP during the second DCP listening opportunity, the terminal device wakes up within the second DRX duration on the second group of carriers.

If the terminal device does not monitor the DCP during the second DCP monitoring period, the behavior of the terminal device on the second group of carriers may be a default behavior or may be specified by the protocol. For example, the terminal device may wake up during the second DRX duration on the second group of carriers to transmit services. Alternatively, the terminal device may also sleep during the second DRX duration on the second group of carriers to reduce the power consumption of the terminal device.

In combination with the second aspect or the first optional implementation of the second aspect or the second optional implementation of the second aspect, in a third optional implementation of the second aspect, the method also includes: when the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, the terminal device sleeps or wakes up within the first DRX duration associated with the first DCP monitoring opportunity on the first group of carriers according to the monitoring situation of the DCP, and sleeps or wakes up within the second DRX duration on the second group of carriers, and the first DRX duration corresponds to the first DRX configuration.

In combination with the second aspect or any optional implementation manner from 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: when the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, on the second group of carriers, the terminal device does not monitor within the second DCP monitoring opportunity.

If the terminal device is able to monitor the DCP during the first DCP monitoring opportunity, the terminal device can determine the behavior on the first group of carriers and the behavior on the second group of carriers according to the indication of the DCP monitored during the first DCP monitoring opportunity. In this case, the terminal device does not need to monitor the second DCP monitoring opportunity, thereby reducing the power consumption of the terminal device due to monitoring the DCP.

In combination with the second aspect or any optional implementation manner from the first optional implementation manner to the fourth optional implementation manner of the second aspect, in the fifth optional implementation manner of the second aspect, the method also includes: when the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, on the first group of carriers, the terminal device wakes up within a first DRX duration associated with the first DCP monitoring opportunity, and the first DRX duration corresponds to the first DRX configuration.

If the terminal device does not monitor the DCP during the first DCP monitoring period, the behavior of the terminal device on the first group of carriers may be a default behavior or may be specified by a protocol. For example, the terminal device wakes up during the first DRX duration to transmit services. For another example, the terminal device may also sleep during the first DRX duration to save power consumption of the terminal device.

In combination with the first optional implementation manner of the second aspect, in a sixth optional implementation manner of the second aspect, the terminal device determines whether to monitor the DCP within the first DCP monitoring opportunity, including: when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, when the time domain position of the first DCP monitoring opportunity is not within or partially within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein the first DRX activation time is the DRX activation time corresponding to the first DRX configuration; or, when the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, at the maximum In the case that the number of sizes of DCI that can be monitored is smaller than the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines not to monitor DCP during the first DCP monitoring opportunity; or, when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, and the maximum number of sizes of DCI that can be monitored is greater than or equal to the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines to monitor DCP during the first DCP monitoring opportunity; or, when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, and the maximum number of sizes of DCI that can be monitored is smaller than the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines not to monitor DCP during the first DCP monitoring opportunity; wherein, the first DRX activation time is the DRX activation time corresponding to the first DRX configuration.

The terminal device may have different determination methods to determine whether to listen to the DCP within the first DCP listening opportunity. For example, the terminal device may determine it based on the time domain position of the first DCP listening opportunity. This determination method is easy to implement for the terminal device and is also compatible with existing technologies. Alternatively, the terminal device may determine it based on the size budget of the DCI. This determination method is relatively simple and reasonable. Alternatively, the terminal device may also combine these two determination methods to make a determination together, which can make the determination result more accurate. The embodiments of the present application provide a variety of determination methods. Which determination method to choose can be decided by the terminal device itself, or configured by the network device, or by default, or by protocol regulations, etc.

In combination with the second aspect or any optional implementation manner from the first optional implementation manner to the sixth optional implementation manner of the second aspect, in the seventh optional implementation manner of the second aspect, the terminal device determines whether to monitor the DCP within the second DCP monitoring opportunity, including: when the time domain position of the second DCP monitoring opportunity is within the second DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, when the time domain position of the second DCP monitoring opportunity is not within or partially within the second DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein the second DRX activation time is the DRX activation time corresponding to the second DRX configuration; or, when the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor. , the terminal device determines to monitor the DCP during the second DCP monitoring opportunity; or, when the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor the DCP during the second DCP monitoring opportunity; or, when the time domain position of the second DCP monitoring opportunity is within the second DRX activation time, and the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP during the second DCP monitoring opportunity; or, when the time domain position of the second DCP monitoring opportunity is within the second DRX activation time, and the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor the DCP during the second DCP monitoring opportunity.

The terminal device may have different determination methods to determine whether to listen to the DCP within the second DCP listening opportunity. For example, the terminal device may determine it based on the time domain position of the second DCP listening opportunity. This determination method is easy to implement for the terminal device and is also compatible with existing technologies. Alternatively, the terminal device may determine it based on the size budget of the DCI. This determination method is relatively simple and reasonable. Alternatively, the terminal device may also combine these two determination methods to make a determination together, which can make the determination result more accurate. The embodiments of the present application provide a variety of determination methods. Which determination method to choose can be decided by the terminal device itself, or configured by the network device, or by default, or by protocol regulations, etc.

In combination with the second aspect or any optional implementation manner from the first optional implementation manner to the seventh optional implementation manner of the second aspect, in the eighth optional implementation manner of the second aspect, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, and determines to monitor the DCP within the second DCP monitoring opportunity, including: when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, and the time domain position of the second DCP monitoring opportunity is not within or partially within the second DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, and determines to monitor the DCP within the second DCP monitoring opportunity.

In a third aspect, a third communication method is provided, which can be executed by a terminal device, or by a chip system, and the chip system can realize the functions of the terminal device. The method includes: the terminal device receives a DCI from a network device on a first carrier, the first carrier belongs to a first group of carriers, the first group of carriers includes one or more carriers configured for the terminal device, and the first group of carriers applies a first DRX configuration; the terminal device determines to sleep or wake up on a second group of carriers within a second DRX duration associated with the DCI according to the second indication information included in the DCI, the second DRX duration corresponds to a second DRX configuration, the second group of carriers applies the second DRX configuration, and the second group of carriers includes one or more carriers configured for the terminal device, wherein when the value of the second field included in the DCI is a first value, it is used to indicate that the DCI includes the second indication information.

In the embodiment of the present application, the two DRX configuration technologies can be used in combination with the wake-up signal, and the embodiment of the present application does not need to configure DCP, but implements the function of DCP through ordinary DCI, reducing the number of DCI sizes that the UE needs to monitor, or enabling the UE to monitor more DCI sizes, and also simplifying the implementation of network equipment and UE. Moreover, the network equipment can indicate the wake-up or sleep of the UE on the carrier group through corresponding indication information. The indication method is more flexible, more in line with the service transmission requirements of the UE, and also increases the flexibility of network equipment scheduling. In addition, the embodiment of the present application also avoids the default method of requiring the UE to wake up during the second DRX duration on the second group of carriers, which can reduce the power consumption of the UE.

In combination with the third aspect, in a first optional implementation of the third aspect, when the value of the second field is a second value, it is used to indicate that the DCI does not include the second indication information.

If it is a DCI for implementing the DCP function, the second field with the first value can be used to indicate that the DCI also includes second indication information. If it is not a DCI for implementing the DCP function, the value of the second field may not be the first value, for example, it may be a normal value. In this case, the terminal device can determine whether the DCI includes the second indication information based on the value of the second field. The indication is clearer and there is no need to add other indication information, which helps to be compatible with existing technologies.

In combination with the third aspect or the first optional implementation of the third aspect, in the first optional implementation of the third aspect, the second field includes one or more of the following fields: an FDRA field, an MCS field, an NDI field, an RV field, a HARQ process number field, an antenna port field, or a 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 not include the above fields but include other fields. The other fields are, for example, other existing fields included in the DCI in addition to the above fields, or may also be newly added fields in the DCI.

In combination with the third aspect or the first optional implementation manner of the third aspect or the second optional implementation manner of the third aspect, in the third optional implementation manner of the third aspect, the method also includes: the terminal device determines, based on the first indication information included in the DCI, to sleep or wake up on the first group of carriers within a first DRX duration associated with the DCI, the first DRX duration corresponding to the first DRX configuration, wherein when the value of the second field is the first value, it is also used to indicate that the DCI includes the first indication information.

If the value of the second field is the first value, the DCI may also include the first indication information, and if the value of the second field is not the first value, the DCI does not include the first indication information. In this implementation, the network device indicates the sleep or wake-up of the two groups of carriers through the second indication information and the first indication information, respectively, so that the behavior of the UE is clearer and more in line with business needs.

In combination with 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 fourth optional implementation manner of the third aspect,

The method further includes: the terminal device sleeping or waking up on the first group of carriers within a first DRX duration associated with the DCI, the first DRX duration corresponding to the first DRX configuration;

or,

The terminal device determines, according to the second indication information included in the DCI, to sleep or wake up on the second group of carriers within the second DRX duration associated with the DCI, including: when the terminal device determines not to monitor the DCP on the first group of carriers, the terminal device determines, according to the second indication information included in the DCI, to sleep or wake up on the second group of carriers within the second DRX duration associated with the DCI;

The method also includes: the terminal device sleeps or wakes up on the first group of carriers within a first DRX duration associated with the DCI, and the first DRX duration corresponds to the first DRX configuration.

The DCI may not indicate the behavior of the UE on the first group of carriers. In this case, it may be assumed (or specified by the protocol) that the UE wakes up on the first group of carriers during the first DRX duration associated with the DCI. Because if the second indication information indicates that the UE wakes up on the second group of carriers during the second DRX duration, and the network device needs to schedule the data transmission of the UE on the second group of carriers on the first group of carriers, then if the UE sleeps on the first group of carriers during the first DRX duration, it may not be able to receive the scheduling information from the network device, and thus cannot perform data transmission on the second group of carriers. Therefore, it may be assumed (or specified by the protocol) that the UE sleeps on the first group of carriers during the first DRX duration to reduce the probability of the UE missing the scheduling information and reduce the transmission delay of the service. Alternatively, it may be assumed (or specified by the protocol) that the UE sleeps on the first group of carriers during the first DRX duration associated with the DCI. In this way, the power consumption of the UE can be saved.

In a fourth aspect, a fourth communication method is provided. The method may be executed by a network device, or by a chip system, which can implement the functions of the network device. Exemplarily, the network device is an access network device. Exemplarily, the access network device is a base station. The method includes: the network device sends a DCI to a terminal device on a first carrier, the first carrier belongs to a first group of carriers, the first group of carriers includes one or more carriers configured to the terminal device, and the first group of carriers applies a first DRX configuration, wherein when the value of the second field included in the DCI is a first value, it is used to indicate that the DCI includes second indication information, and the second indication information is used to indicate that on a second group of carriers, sleep or wake up within a second DRX duration associated with the DCI, the second DRX duration corresponds to a second DRX configuration, the second group of carriers applies the second DRX configuration, and the second group of carriers includes one or more carriers configured to the terminal device.

In combination with the fourth aspect, in a first optional implementation of the fourth aspect, when the value of the second field is a second value, it is used to indicate that the DCI does not include the second indication information.

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

In combination with the fourth aspect or the first optional implementation manner of the fourth aspect or the second optional implementation manner of the fourth aspect, in the third optional implementation manner of the fourth aspect, when the value of the second field is the first value, it is also used to indicate that the DCI includes the first indication information, and the first indication information is used to indicate sleep or wake-up on the first group of carriers within the first DRX duration associated with the DCI, and the first DRX duration corresponds to the first DRX configuration.

Regarding the technical effects brought about by the fourth aspect or various optional implementations of the fourth aspect, reference may be made to the introduction to the technical effects of the third aspect or corresponding implementations.

In a fifth aspect, a fifth communication method is provided, which can be executed by a terminal device, or by a chip system, and the chip system can realize the functions of the terminal device. The method includes: the terminal device receives a second DCI on a first carrier, the first carrier belongs to a first group of carriers, and the second DCI is used to schedule data on a second group of carriers, wherein the first group of carriers applies a first DRX configuration, the second group of carriers applies a second DRX configuration, the first group of carriers includes one or more carriers configured for the terminal device, and the second group of carriers includes one or more carriers configured for the terminal device; the terminal device starts or restarts a second DRX inactive timer, and sets the duration of the second DRX inactive timer to the duration of the DRX inactive timer configured by the second DRX configuration.

In the embodiment of the present application, the two DRX configuration technologies can be used in combination with the cross-carrier scheduling technology. When implementing cross-carrier scheduling, the UE can receive DCI from the network device on the first group of carriers for scheduling data on the second group of carriers, and the UE can also receive data or send data on the second group of carriers, so that the cross-carrier scheduling technology can be implemented under the background of the two DRX configuration technologies. Moreover, the embodiment of the present application can set the duration of the first DRX inactive timer corresponding to the first group of carriers to different durations according to different situations, so that the duration of the first DRX inactive timer is more in line with the current service transmission requirements and also saves more power consumption of the UE.

In combination with the fifth aspect, in a first optional implementation of the fifth aspect, the terminal device starts or restarts the second DRX inactivity timer, including: the terminal device starts or restarts the second DRX inactivity timer in the first time domain symbol after the second DCI is received.

The time domain symbol is, for example, an orthogonal frequency division multiplexing (OFDM) symbol.

In combination with the fifth aspect or the first optional implementation of the fifth aspect, in a second optional implementation of the fifth aspect, the second DCI includes second indication information, and the second indication information is used to indicate the start or restart of the second DRX inactivity timer.

The second indication information may be carried by an existing field in the second DCI. For example, if there is a reserved bit in the existing field included in the second DCI, the second indication information may be carried by the reserved bit; or one or more bits may be added to the second DCI to carry the second indication information. Indicating by the second DCI allows the UE to more clearly understand the UE's behavior.

In combination with the fifth aspect or the first optional implementation manner of the fifth aspect or the second optional implementation manner of the fifth aspect, in the third optional implementation manner of the fifth aspect, after the terminal device receives the second DCI on the first carrier, the method also includes: the terminal device starts or restarts a first DRX inactivity timer, and sets the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the first DRX configuration, or to the duration of the DRX inactivity timer configured by the second DRX configuration, and the first DRX inactivity timer corresponds to the first DRX configuration.

Since there is data transmission on the second group of carriers, and the second DCI is cross-carrier scheduling, the subsequent network device may also schedule the data on the second group of carriers by cross-carrier scheduling. In addition, the network device may also schedule the data on the first group of carriers on the first group of carriers. Therefore, the DRX activation time of the UE on the first group of carriers can be extended to receive the DCI for scheduling data. If the UE wants to extend the DRX activation time of the UE on the first group of carriers, one implementation method is to extend it through the first DRX inactive timer. For example, the UE can set the duration of the first DRX inactive timer to the original duration of the first DRX inactive timer, that is, the duration of the DRX inactive timer configured by the first DRX configuration. This setting method is relatively simple and is also a setting that is easy for the UE to implement. For another example, the UE can also set the duration of the first DRX inactive timer to the duration of the DRX inactive timer configured by the second DRX configuration, which can be understood as the UE setting the duration of the first DRX inactive timer to the duration of the second DRX inactive timer. If this method is adopted, the duration of the DRX activation time of the UE on the first group of carriers may be consistent with the duration of the DRX activation time of the UE on the second group of carriers. The UE can receive the DCI for scheduling data of the second group of carriers on the first group of carriers, and will not consume too much power due to the long DRX activation time on the first group of carriers.

In combination with the third optional implementation of the fifth aspect, in the fourth optional implementation of the fifth aspect, when the terminal device sets the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration, the method further includes: before the terminal device restarts the first DRX inactivity timer, determining that the first DRX inactivity timer is in a running state, and determining that 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 does not need to start or restart the first DRX inactivity timer under any circumstances, but can first determine whether it is necessary to start or restart the first DRX inactivity timer. For example, before the UE starts or restarts the first DRX inactivity timer, if the first DRX inactivity timer is in a running state, the UE can determine the size relationship between the remaining duration of the first DRX inactivity timer and the duration of the DRX inactivity timer configured by the second DRX configuration. 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 can set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration; or, 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, the UE does not need to restart the first DRX inactivity timer. In this way, the duration of the first DRX inactivity timer is prevented from being long or short, and the complexity of UE processing is reduced.

In combination with the third optional implementation of the fifth aspect, in the fifth optional implementation of the fifth aspect, before the terminal device starts or restarts the first DRX inactivity timer and sets the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the first DRX configuration, the method also includes: the terminal device receives a first DCI on the first group of carriers, and the first DCI is used to schedule data on the first group of carriers.

If the UE receives a first DCI on the first group of carriers before starting or restarting the first DRX inactivity timer, and the first DCI is used to schedule the UE to receive or send data on the first group 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 UE's need to receive or send data on the first group of carriers, and also meet the UE's need to schedule receiving data corresponding to the first group of carriers on the first group of carriers.

In combination with the third optional implementation of the fifth aspect, in a sixth optional implementation of the fifth aspect, the second DCI includes first indication information, and the first indication information is used to indicate starting or restarting the first DRX inactivity timer.

Whether the UE should start the first DRX inactivity timer can be determined by default, specified by a protocol, or indicated by a network device. For example, the second DCI may include the first indication information, and the first indication information may indicate starting or restarting the first DRX inactivity timer. Indicating through the second DCI allows the UE to more clearly understand the UE's behavior.

In combination with the sixth optional implementation of the fifth aspect, in the seventh optional implementation of the fifth aspect, the first indication information is also used to indicate that the timing duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the first DRX configuration, or to indicate that the timing duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the second DRX configuration.

If the second DCI includes the first indication information, then the first indication information may indicate how to set the duration of the first DRX inactivity timer in addition to instructing the UE to start or restart the first DRX inactivity timer. The UE does not need to determine how to set the duration of the first DRX inactivity timer by itself, thus simplifying the implementation of the UE.

In combination with the fifth aspect or the first optional implementation of the fifth aspect or the second optional implementation of the fifth aspect, in the eighth optional implementation of the fifth aspect, the method also includes: the terminal device extends the end time of the DRX activation time of the terminal device on the first group of carriers to the same as the end time of the DRX activation time of the terminal device on the second group of carriers.

If the UE wants to extend the DRX activation time of the UE on the first group of carriers, one implementation method is to extend it through the first DRX inactivation timer, while another implementation method does not need to use the first DRX inactivation timer, but can directly extend the end time of the DRX activation time on the first group of carriers, for example, the end time of the DRX activation time of the UE on the first group of carriers is extended to be the same as the end time of the DRX activation time of the UE on the second group of carriers. If this method is adopted, the duration of the DRX activation time of the UE on the first group of carriers is consistent with the duration of the DRX activation time of the UE on the second group of carriers. The UE can receive the DCI for scheduling the data of the second group of carriers on the first group of carriers, and will not consume too much power due to the long DRX activation time on the first group of carriers. Moreover, this method does not need to use the first DRX inactivation time timer, which reduces the power consumption caused by the UE maintaining the first DRX inactivation time timer.

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

In a sixth aspect, a communication device is provided. The communication device may include a module for executing the method in the first aspect or any optional implementation of the first aspect, for example, including a transceiver unit and a processing unit. Optionally, the communication device may also include a storage unit.

In a seventh aspect, a communication device is provided. The communication device may include a module for executing the method in the second aspect or any optional implementation of the second aspect, for example, including a transceiver unit and a processing unit. Optionally, the communication device may also include a storage unit.

In an eighth aspect, a communication device is provided. The communication device may include a module for executing the method in the third aspect or any optional implementation of the third aspect, for example, including a transceiver unit and a processing unit. Optionally, the communication device may also include a storage unit.

In a ninth aspect, a communication device is provided. The communication device may include a module for executing the method in the fourth aspect or any optional implementation of the fourth aspect, for example, including a transceiver unit and a processing unit. Optionally, the communication device may also include a storage unit.

In a tenth aspect, a communication device is provided. The communication device may include a module for executing the method in the fifth aspect or any optional implementation of the fifth aspect, for example, including a transceiver unit and a processing unit. Optionally, it may also include a storage unit.

In an eleventh aspect, a chip system is provided, the chip system comprising one or more processors and a communication interface, the processor being coupled to the communication interface to implement the method provided in any one of the above aspects. Optionally, the chip system may also include a memory, for example, the processor may read and execute a software program stored in the memory 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 includes the communication device described in the sixth aspect or the chip system described in the eleventh aspect (used to implement the method provided in the first aspect or any optional implementation of the first aspect).

In a thirteenth aspect, a second communication system is provided. The second communication system comprises the communication device described in the seventh aspect or the chip system described in the eleventh aspect (used to implement the method provided in the second aspect or any optional implementation of the second aspect).

In the fourteenth aspect, a third communication system is provided. The second communication system includes the communication device described in the eighth aspect or the chip system described in the eleventh aspect (used to implement the method provided by the third aspect or any optional implementation of the third aspect), and includes the communication device described in the ninth aspect or the chip system described in the eleventh aspect (used to implement the method provided by the fourth aspect or any optional implementation of the fourth aspect).

In a fifteenth aspect, a fourth communication system is provided. The second communication system comprises the communication device described in the tenth aspect or the chip system described in the eleventh aspect (used to implement the method provided in the fifth aspect or any optional implementation of the fifth aspect).

In the sixteenth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium is used to store a computer program. When the computer program is run on a computer, the computer executes the method provided in any one of the above aspects.

In the seventeenth aspect, a computer program product comprising instructions is provided, wherein the computer program product is used to store a computer program, and when the computer program is run on a computer, the computer executes the method provided in any one of the above aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a DRX mechanism;

FIG2 is a schematic diagram of the time domain position of a DCP;

FIG3 is a schematic diagram of two groups of DRX configurations;

FIG4 is a schematic diagram of an application scenario of an embodiment of the present application;

FIG5 is a flow chart of a first communication method provided in an embodiment of the present application;

FIG6 is a schematic diagram showing that the monitoring result of the UE at the first DCP monitoring opportunity can determine the behavior of the UE on two groups of carriers in an embodiment of the present application;

FIG7 is a schematic diagram of cross-carrier scheduling of network devices in an embodiment of the present application;

FIG8 is a flow chart of a second communication method provided in an embodiment of the present application;

9 is a schematic diagram showing that a monitoring result of a UE at a first DCP monitoring opportunity can determine a behavior of the UE on a first group of carriers, and a monitoring result of a UE at a second DCP monitoring opportunity can determine a behavior of the UE on a second group of carriers in an embodiment of the present application;

FIG10 is a flow chart of a third communication method provided in an embodiment of the present application;

FIG11 is a schematic diagram showing that the DCI received by the UE on the first group of carriers can indicate the sleep or wake-up of the UE on two groups of carriers in an embodiment of the present application;

FIG12 is a flow chart of a fourth communication method provided in an embodiment of the present application;

FIG13 is a schematic diagram showing that the duration of the first DRX inactivity timer is greater than the duration of the second DRX inactivity timer in an embodiment of the present application;

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

FIG15 is a schematic diagram of extending the DRX activation time of the UE on the first group of carriers in an embodiment of the present application;

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

FIG17 is a schematic block diagram of another communication device provided in an embodiment of the present application.

Detailed ways

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

Below, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

In the embodiment of the present application, the terminal device is a device with wireless transceiver function, which can be a fixed device, a mobile device, a handheld device, a wearable device, a vehicle-mounted device, or a wireless device built into the above device (for example, a communication module or a chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), vehicle to everything (vehicle to everything, V2X), machine-to-machine/machine-type communication (machine-to-machine/machine-type communications, M2M/MTC), Internet of Things (Internet of Things, IoT), virtual reality (virtual reality, VR), augmented reality (augmented reality, AR), industrial control (industrial control), self-driving, remote medical, smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation, smart city (smart city), drones, robots and other scenarios of terminal devices. The terminal device may sometimes be referred to as UE, terminal, access station, UE station, remote station, wireless communication equipment, or user device, etc. For the convenience of description, the terminal device is described using UE as an example in the embodiments of the present application.

The network device in the embodiment of the present application includes, for example, an access network device and/or a core network device. The access network device is a device with a wireless transceiver function, which is used to communicate with the terminal device. The access network device includes but is not limited to the base station (BTS, Node B, eNodeB/eNB, or gNodeB/gNB) in the above-mentioned communication system, a transmission reception point (TRP), a base station of the subsequent evolution of the third generation partnership project (3GPP), an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. The base station can be: a macro base station, a micro base station, a micro-micro base station, a small station, a relay station, etc. Multiple base stations can support the networks of the same access technology mentioned above, or they can support the networks of the different access technologies mentioned above. The base station can include one or more co-station or non-co-station transmission and reception points. The network device can also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. The network device can also be a server, a wearable device, or a vehicle-mounted device. For example, the network equipment in the vehicle to everything (V2X) technology may be a road side unit (RSU). The following description of the access network equipment takes the base station as an example. The multiple network devices in the communication system may be base stations of the same type or different types. The base station may communicate with the terminal device or communicate with the terminal device through a relay station. The terminal device may communicate with multiple base stations in different access technologies. The core network equipment is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of the devices that implement the core network functions in systems with different access technologies may be different, and this application does not limit this. Taking the 5G system as an example, the core network equipment may include an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF), etc. Taking the 4G system as an example, the core network equipment may include a mobility management entity, etc.

In the embodiment of the present application, the device for realizing the function of the network device may be a network device, or may be a device capable of supporting the network device to realize the function, such as a chip system, which may be installed in the network device. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for realizing the function of the network device as an example that the network device is used as the device.

In addition, because the embodiments of the present application are more related to access network equipment, unless otherwise specified, the "network equipment" mentioned below refers to access network equipment.

In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. For example, A/B means: A or B. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

Furthermore, unless otherwise specified, ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, sequence, timing, priority or importance of multiple objects. For example, the first DCI and the second DCI can be the same DCI or different DCIs, and such a name does not indicate the difference in the time length, transmission order, content, priority or importance of the two DCIs.

In order to better understand the technical solutions of the embodiments of the present application, some technical features involved in the embodiments of the present application are introduced below.

1.DRX.

The 5G new radio (NR) technology uses the discontinuous reception (DRX) mechanism in the long term evolution (LTE) technology. The DRX mechanism is mainly introduced to save power consumption. Among them, the DRX cycle configured by the base station for the UE can be a long DRX cycle or a short DRX cycle, where the long DRX cycle is the default configuration and the short DRX cycle is an optional configuration. If a UE is configured with a long DRX cycle but not a short DRX cycle, the UE will use a long DRX cycle or a short DRX cycle at the same time, that is, the UE will not use both DRX cycles at the same time. The UE will start the DRX short cycle timer (drx-ShortCycleTimer) when using the short DRX cycle. When the drx-ShortCycleTimer times out, the UE implicitly converts to using a long DRX cycle. Among them, the unit of drx-ShortCycleTimer is the number of short DRX cycles.

The DRX cycle consists of the "On Duration" part and the "DRX opportunity (Opportunity for DRX)" part. During the "On Duration" time, the UE monitors and receives the PDCCH. During the "Opportunity for DRX" time, the UE may not monitor or receive the PDCCH to reduce power consumption. For this, please refer to Figure 1. Among them, monitoring and receiving the PDCCH can be understood as monitoring and receiving the DCI carried on the PDCCH. The DRX mechanism includes a DRX duration timer (drx-onDurationTimer). At the beginning of each DRX cycle (that is, the On Duration of each DRX cycle begins), the UE needs to start the drx-onDurationTimer. When the drx-onDurationTimer times out, it means that the "On Duration" time ends, and the UE enters the "Opportunity for DRX" time in the DRX cycle.

The DRX mechanism also includes a DRX inactivity timer (drx-InactivityTimer). When the UE receives a PDCCH indicating a new data transmission, since the UE is likely to continue to be scheduled by the base station in the following period of time, the UE needs to start the drx-InactivityTimer. During the running time of the drx-InactivityTimer, the UE needs to monitor and receive the PDCCH.

The DRX mechanism also includes a DRX retransmission timer (drx-RetransmissionTimer), which is specifically divided into an uplink drx-RetransmissionTimer and a downlink drx-RetransmissionTimer. Since the base station may schedule the UE's retransmission within the running time of the drx-RetransmissionTimer, the UE needs to monitor and receive the PDCCH within the running time of the drx-RetransmissionTimer.

In summary, the UE needs to monitor and receive PDCCH during the operation of drx-onDurationTimer, drx-InactivityTimer, uplink drx-RetransmissionTimer, and downlink drx-RetransmissionTimer. Therefore, the operation time of these timers is considered as DRX "activation time". During the DRX activation time, the UE needs to wake up and prepare to receive signaling or data. In addition to the operation time of all the above timers, if none of the above timers are running at a certain moment, the UE may not need to monitor and receive PDCCH at that moment. This time is called DRX "sleep time". During the DRX sleep time, the UE can sleep. Generally speaking, the power consumption of UE in DRX "activation time" is higher than that in DRX "sleep time". It should be noted that in some other functions outside the DRX mechanism, it may also be limited that the UE needs to be in "activation time" or "sleep time" in certain cases. This does not conflict with the DRX mechanism, but takes the relationship of union. Therefore, whether the UE is actually in "activation time" or "sleep time" in the end needs to be determined from the overall functions of the UE.

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

Carrier aggregation technology can aggregate multiple (for example, two or more) component carriers (CC) together to increase the transmission bandwidth and improve the uplink and downlink transmission rates. In the carrier aggregation scenario, multiple CCs include a main carrier and one or more auxiliary carriers. Among them, the main carrier is the carrier on which the primary cell (PCell) works, and the auxiliary carrier is the carrier on which the secondary cell (SCell) works. After the UE accesses the network, the UE will always maintain communication on the main carrier under one base station, and the base station can add one or more auxiliary carriers for the UE according to the service situation.

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

In the carrier aggregation scenario, there are same-carrier scheduling and cross-carrier scheduling. The base station schedules the UE to receive or send data by sending DCI on the PDCCH, that is, indicating the physical downlink shared channel (PDSCH) used to schedule data reception in the DCI, or indicating the physical uplink shared channel (PUSCH) used to schedule data transmission in the DCI. If the carrier receiving the DCI and the carrier receiving (or sending) the data are the same carrier, it is same-carrier scheduling; if the carrier receiving the DCI and the carrier receiving (or sending) the data are different carriers, it is cross-carrier scheduling. For the FR1+FR2 CA scenario, FR1 can schedule FR2 across carriers, that is, DCI is received on the FR1 carrier, and the DCI schedules the reception or transmission of data on the FR2 carrier.

3. Wake-up signal.

In 5G technology, 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 used to schedule the UE during the DRX activation time, so the UE just consumes the power consumption of monitoring the PDCCH in vain. Therefore, it is proposed to introduce an indication signal (PDCCH-WUS), or a wake-up signal, which can indicate whether the UE needs to wake up or sleep during the subsequent DRX activation time based on the current DRX mechanism. The PDCCH-WUS is also called DCP in the standard, and the signal form of DCP can be DCI. The time domain position of DCP can be: an offset position before the "On Duration" time of the DRX cycle. For this, please refer to Figure 2. The bold vertical line in Figure 2 represents DCP. In the carrier aggregation scenario, DCP is only configured on the primary carrier, but the wake-up or sleep indicated by DCP can act on all carriers participating in the carrier aggregation.

It should be noted that in the embodiments of the present application, "carrier" and "cell" can be considered the same concept without considering the supplementary uplink (SUL), and the two concepts can be interchanged. For example, the primary carrier can also be called the primary service cell, or the primary cell; the secondary carrier can also be called the secondary service cell, or the secondary cell.

4. Two groups of DRX.

At present, a UE in an RRC connected state can support two groups of DRX configurations. All carriers using the first group of DRX configurations belong to one frequency range (frequency range, FR), such as FR1, and all carriers using the second group of DRX configurations belong to another frequency range, such as FR2. The first group of DRX configurations can be considered as a primary configuration, and the second group of DRX configurations can be considered as a secondary configuration. Compared with the first group of DRX configurations, the second group of DRX configurations can be configured with shorter timing durations of drx-onDurationTimer and drx-InactivityTimer, for example, see Figure 3. In Figure 3, the dotted box indicates the duration of the DRX inactivity time timer. The two groups of DRX configurations can be understood as being maintained and operated separately. The carriers belonging to the first frequency range use the first group of DRX configurations together, maintaining drx-onDurationTimer1 and drx-InactivityTimer1; the carriers belonging to the second frequency range use the second group of DRX configurations together, maintaining drx-onDurationTimer2 and drx-InactivityTimer2. Optionally, except for drx-onDurationTimer and drx-InactivityTimer, other parameters configured by the first DRX configuration may be the same as corresponding parameters configured by the second DRX configuration. For example, carriers belonging to the first frequency range use the first group of DRX configurations together and maintain drx-RetransmissionTimer 1, and carriers belonging to the first frequency range use the second group of DRX configurations together and maintain drx-RetransmissionTimer 2, and the durations of drx-RetransmissionTimer 1 and drx-RetransmissionTimer 2 may be the same.

The above-mentioned cross-carrier scheduling, wake-up signal and two-group DRX configuration technologies are currently used separately and are not used in combination. For example, the combination of two-group DRX configuration and wake-up signal, or the combination of two-group DRX configuration and cross-carrier scheduling, etc., are not currently supported, which will affect the flexibility of base station configuration. In addition, the use of two-group DRX configuration is mainly to reduce the power consumption of UE on the carrier corresponding to the second group of DRX configuration (such as FR2), and cross-carrier scheduling or wake-up signal itself is helpful to reduce UE power consumption. If the two-group DRX configuration can be used in combination with these technologies, the UE power consumption can be further reduced.

In view of this, a technical solution of an embodiment of the present application is provided. In an embodiment of the present application, the two DRX configuration technologies can be used in combination with a wake-up signal, and the behavior of the terminal device in the combined case is specified. For example, the monitoring of the DCP monitoring timing corresponding to the first group of carriers by the terminal device 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, which reduces the power consumption of the terminal device monitoring the DCP and increases the flexibility of network device scheduling. Moreover, the monitoring situation of the terminal device on one group of carriers can be applicable to two groups of carriers, so that both groups of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two groups of carriers.

The technical solution provided in the embodiment of the present application can be applied to a 4G system, such as an LTE system, or can be applied to a 5G system, such as an NR system, or can also be applied to a next-generation mobile communication system or other similar communication systems, without specific limitation. For example, when a terminal device (such as a smart phone, a smart watch, or a smart bracelet, etc.) has a need for energy saving, for example, the battery level of the mobile phone is already less than 20%, then the mobile phone has a very strong need to save power consumption. In this case, after adopting the method provided in the embodiment of the present application, the power consumption of the terminal device can be further reduced, that is, the battery power consumed is reduced, and the standby time of the terminal device is extended.

Please refer to Figure 4, which is an application scenario of an embodiment of the present application. Figure 4 includes an access network device, a core network device and a UE, and the access network device can configure one or more carriers for the UE. The access network device, for example, works in an evolved UMTS terrestrial radio access (E-UTRA) system, or works in an NR system, or works in a next-generation communication system or other communication system. The access network device is, for example, a base station. Among them, the access network device corresponds to different devices in different systems, for example, it can correspond to eNB in a 4G system, and corresponds to an access network device in 5G in a 5G system, such as gNB. Of course, the technical solution provided in the embodiment of the present application can also be applied to future mobile communication systems, so the access network device in Figure 4 can also correspond to a network device in a future mobile communication system. Figure 4 takes the access network device as a base station as an example. In fact, referring to the introduction in the previous text, the access network device can also be a device such as RSU. In addition, the UE in Figure 4 takes a mobile phone as an example. In fact, according to the introduction to the UE in the previous text, it can be known that the UE in the embodiment of the present application is not limited to a mobile phone.

In addition, for the sake of ease of introduction, each embodiment to be introduced below is taken as an example of application in the architecture shown in Figure 4. For example, the network device described in each embodiment below is, for example, an access network device in the network architecture shown in Figure 4, and the UE described in each embodiment below can be a UE in the network architecture shown in Figure 4.

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

The embodiment of the present application provides a first communication method. Please refer to FIG5 , which is a flowchart of the method.

S51. The UE determines whether to monitor the DCP within a first DCP monitoring opportunity. In other words, the UE determines whether to monitor within the first DCP monitoring opportunity.

For example, the network device sends the first DRX configuration and the second DRX configuration to the UE, and the UE is 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. The first group of carriers applies the first DRX configuration, and the second group of carriers applies the second DRX configuration. The first group of carriers includes one or more carriers configured by the UE, and the second group of carriers also includes one or more carriers configured by the UE. The first DRX configuration can configure the DRX cycle, DRX duration timer, DRX inactivity timer, and DRX retransmission timer, etc. The second DRX configuration can also configure the DRX cycle, DRX inactivity timer, and DRX retransmission timer, etc. The first DRX configuration and the second DRX configuration are different DRX configurations, for example, the DRX duration timer configured by the first DRX configuration is different from the DRX duration timer configured by the second DRX configuration, for example, the duration (or timing duration) of the DRX duration timer configured by the first DRX configuration is different from the duration of the DRX duration timer configured by the second DRX configuration. For another example, the DRX inactive timer configured by the first DRX configuration is different from the DRX inactive timer configured by the second DRX configuration, for example, the duration (or timing duration) of the DRX inactive timer configured by the first DRX configuration is different from the duration of the DRX inactive timer configured by the second DRX configuration. However, the other contents configured by the first DRX configuration and the second DRX configuration, such as the DRX cycle or the DRX retransmission timer, except for the DRX duration timer and the DRX inactive timer, may be the same or different.

For example, the first group of carriers belongs to the first frequency range, and the second group of carriers belongs to the second frequency range, and the first frequency range and the second frequency range may be different frequency ranges. As an optional implementation, for example, the frequency of the second frequency range is greater than the frequency of the first frequency range, which can be understood as the minimum frequency included in the second frequency range is greater than the maximum frequency included in the first frequency range, for example, the first frequency range is FR1, and the second frequency range is FR2. In fact, when the network device configures carriers for the UE, it may not distinguish which carrier belongs to which group, that is, the concepts of "first group" and "second group" may not exist. The descriptions of "first group of carriers" and "second group of carriers" are used here to distinguish between carriers using different DRX configurations.

The first DCP monitoring opportunity is a DCP monitoring opportunity configured on the first group of carriers, and the first DCP monitoring opportunity applies the first DRX configuration. Under the first DRX configuration, there are multiple On Duration times, so the DCP monitoring opportunity may also appear multiple times, for example, there may be a DCP monitoring opportunity before the start of each DRX cycle. Then, the first DCP monitoring opportunity is, for example, the current monitoring opportunity for the UE, for example, the first DCP monitoring opportunity is located before the start of the On Duration time of a DRX cycle under the first DRX configuration, or in other words, the first DCP monitoring opportunity is located before the start of the On Duration time of a DRX cycle on the first group of carriers. The first DCP monitoring opportunity may include one or more DCP monitoring opportunities, and it can be understood that a DCP monitoring opportunity may include one or more DCP monitoring opportunities, and the first DCP monitoring opportunity is a DCP monitoring opportunity.

In an embodiment of the present application, the network device may send a DCP on a first carrier, and the first carrier belongs to a first group of carriers. For example, the network device configures a DCP for one or more carriers included in the first group 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 a DCP for the main carrier, and the first carrier is the main carrier of the UE. The network device may send a DCP on the main carrier without configuring a DCP on other carriers to save transmission overhead. If the UE needs to monitor on the first group of carriers, it may monitor on all carriers included in the first group of carriers, or the network device may pre-configure which carriers to send the DCP on, and the UE only needs to monitor on these carriers. However, the network device does not configure a DCP for the second group of carriers, so the network device does not need to send a DCP on the second group of carriers, and the UE does not need to monitor the DCP on the second group of carriers.

The UE needs to determine whether to monitor during the first DCP monitoring opportunity. There are multiple ways to determine this, which are described below with examples.

The first determination method: determining according to the time domain position of the first DCP monitoring opportunity.

For example, the UE determines whether the time domain position of the first DCP monitoring opportunity is within the first DRX activation time. If the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, it indicates that the UE may have data transmission on the first group of carriers within the first DCP monitoring opportunity (for example, the UE needs to receive data or send data on the first group of carriers). In this case, the UE may not monitor at the first DCP monitoring opportunity, but may wake up on the first group of carriers within the DRX duration associated with the first DCP monitoring opportunity.

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

Alternatively, if the partial time domain position corresponding to the first DCP listening opportunity is not within the first DRX activation time, the UE may not monitor within the DCP listening opportunities within the first DRX activation time included in the first DCP listening opportunity, and the UE may still monitor the DCP listening opportunities that are included in the first DCP listening opportunity and are not within the first DRX activation time. That is, in this case, the UE does not monitor within the partial DCP listening opportunities included in the first DCP listening opportunity, but monitors within the remaining DCP listening opportunities included in the first DCP listening opportunity, so this situation can also be regarded as the UE monitoring within the first DCP listening opportunity. The partial time domain position corresponding to the first DCP listening opportunity includes the time domain position of the partial DCP listening opportunities included in the first DCP listening opportunity. The first DRX activation time is the DRX activation time corresponding to the first DRX configuration, and the first DRX activation time is located on the first group of carriers.

This determination method is relatively easy to implement for the UE.

The second determination method: determining according to a DCI size budget (DCI size budget).

For the UE, there is a DCI size budget, that is, the maximum number of DCI sizes that the UE can monitor is limited. For example, if the maximum number of DCI sizes that the UE can monitor is 4, then the UE can monitor a maximum of 4 sizes of DCI. If there is a fifth size of DCI, the UE cannot monitor it. DCP is regarded as a size of DCI. The network device can configure the total number of DCI sizes that the UE needs to monitor to the UE. Then the UE can determine whether it needs to monitor the DCP within the first DCP monitoring opportunity based on the maximum number of DCI sizes that can be monitored and the number of DCI sizes that the UE needs to monitor.

For example, if DCP is not considered as the DCI that the UE needs to monitor, then if the maximum number of DCI sizes that the UE can monitor 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, because at this time, even if the UE monitors DCP, it can meet the requirements of the DCI size budget. If the maximum 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, then the UE may not monitor in the first DCP monitoring opportunity, because if the UE monitors DCP at this time, it exceeds the DCI size budget, which may cause the UE's monitoring behavior to be wrong. For example, the maximum number of DCI sizes that the UE can monitor is 4, 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 DCP in the first DCP monitoring opportunity; or, the maximum number of DCI sizes that the UE can monitor is 4, and the number of DCI sizes that the UE needs to monitor is 4, then the UE does not monitor DCP in the first DCP monitoring opportunity.

Alternatively, if DCP is regarded as the DCI that the UE needs to monitor, then if the maximum number of DCI sizes that the UE can monitor is greater than or equal to the number of DCI sizes that the UE needs to monitor, then the UE can monitor during the first DCP monitoring opportunity, and if the maximum number of DCI sizes that the UE can monitor is less than the number of DCI sizes that the UE needs to monitor, then the UE may not monitor during the first DCP monitoring opportunity. For example, if the maximum number of DCI sizes that the UE can monitor is 4, 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 during the first DCP monitoring opportunity; or, if the maximum number of DCI sizes that the UE can monitor is 4, the number of DCI sizes that the UE needs to monitor is 5, and the DCI that the UE needs to monitor includes DCP, then the UE does not monitor the DCP during the first DCP monitoring opportunity.

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

The third determination method is to determine according to the time domain position of the first DCP monitoring opportunity and the DCI size budget.

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

Alternatively, if the maximum number of DCI sizes that the UE can monitor is less than the number of DCI sizes that the UE needs to monitor (considering 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 opportunity, but may determine that the UE does not monitor the DCP during the first DCP monitoring opportunity.

For another example, the UE determines whether the time domain position of the first DCP monitoring opportunity is within the first DRX activation time. If the time domain position of the first DCP monitoring opportunity is not within or partially within the first DRX activation time, the UE determines the maximum number of DCI sizes that the UE can monitor and the number of DCI sizes that the UE needs to monitor. If the maximum number of DCI sizes that the UE can monitor is greater than or equal to the number of DCI sizes that the UE needs to monitor (the DCP is regarded as the DCI that the UE needs to monitor), the UE monitors the DCP during the first DCP monitoring opportunity, or, if the maximum number of DCI sizes that the UE can monitor is less than the number of DCI sizes that the UE needs to monitor, the UE does not monitor the DCP during the first DCP monitoring opportunity.

Alternatively, if the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the UE may not need to determine the maximum number of DCI sizes that the UE can monitor and the number of DCI sizes that the UE needs to monitor, but can determine that the UE does not monitor the DCP within the first DCP monitoring opportunity.

The third determination method is equivalent to combining the first determination method with the second determination method, which can make the determination result more reasonable.

As for which of the above three methods the UE uses to determine whether to monitor within the first DCP monitoring opportunity, it can be determined by the UE itself, or configured by the network device, or can also be stipulated by the protocol, etc.

Optionally, in various embodiments of the present application, the UE may not have a process of determining whether it needs to monitor the DCP monitoring opportunity. For example, for the embodiment shown in FIG. 5, the UE may not execute S51. For example, when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the UE does not monitor the first DCP monitoring opportunity, or when all the time domain positions corresponding to the first DCP monitoring opportunity are not within the first DRX activation time, the UE monitors the first DCP monitoring opportunity, or when some of the time domain positions corresponding to the first DCP monitoring opportunity are not within the first DRX activation time, the UE does not monitor the DCP monitoring opportunity included in the first DRX activation time, but monitors the DCP monitoring opportunity included in the first DCP monitoring opportunity that is not within the first DRX activation time. For another example, when the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, the UE monitors the first DCP monitoring opportunity, and when the maximum 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 does not monitor the first DCP monitoring opportunity. For ease of understanding, each embodiment of the present application takes the UE having a determination process as an example.

Optionally, according to the first determination method as described above, S51 may be replaced by the UE determining whether the time domain position of the first DCP monitoring opportunity is within the first DRX activation time.

Alternatively, according to the first determination method as described above, S51 may be replaced by the UE determining whether the maximum number of DCI sizes that the UE can monitor 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 method as described above.

S52. If the UE determines not to monitor within the first DCP monitoring opportunity, the UE wakes up within the first DRX duration associated with the first DCP monitoring opportunity, and wakes up or sleeps within the second DRX duration associated with the first DCP monitoring opportunity. In other words, if the UE does not monitor within the first DCP monitoring opportunity, the UE wakes up within the first DRX duration associated with the first DCP monitoring opportunity on the first group of carriers, and wakes up or sleeps within the second DRX duration associated with the first DCP monitoring opportunity on the second group of carriers.

Optionally, if S51 is replaced according to the first determination method as above, then S52 can also be replaced by, if the time domain position of the first DCP listening opportunity is within the first DRX activation time, the UE wakes up within the first DRX duration associated with the first DCP listening opportunity, and wakes up or sleeps within the second DRX duration associated with the first DCP listening opportunity.

Alternatively, if S51 is replaced according to the first determination method as above, then S52 can also be replaced by, if the maximum 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 wakes up within the first DRX duration associated with the first DCP monitoring opportunity, and wakes up or sleeps within the second DRX duration associated with the first DCP monitoring opportunity.

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

On the first group of carriers, according to the first DRX configuration, the first DCP monitoring opportunity can be associated with one or more DRX cycles. The DRX cycle associated with the first DCP monitoring opportunity is later than the first DCP monitoring opportunity in the time domain, and if the first DCP monitoring opportunity is associated with multiple DRX cycles, these multiple DRX cycles can be continuous or discontinuous in the time domain. In addition, the first DRX duration corresponds to the first DRX configuration, and the first DRX duration is located on the first group of carriers. For example, the first DRX duration may include the On Duration time within all or part of the DRX cycle associated with the first DCP monitoring opportunity under the first DRX configuration, or in other words, the first DRX duration may include the On Duration time within all or part of the DRX cycle associated with the first DCP monitoring opportunity on the first group of carriers. If the UE determines not to monitor within the first DCP monitoring opportunity, the UE does not monitor within the first DCP monitoring opportunity. In this case, in order to reduce the probability that the UE misses the PDCCH that the network device may send on the first group of carriers, the UE can wake up within the first DRX duration.

On the second group of carriers, according to the second DRX configuration, the first DCP monitoring opportunity can also be associated with one or more DRX cycles. Because the first DCP monitoring opportunity is not configured on the second group of carriers, this association is an association in the time domain position. For example, on the second group of carriers, one or more DRX cycles that are later than the first DCP monitoring opportunity in the time domain can be associated with the first DCP monitoring opportunity. And if the first DCP monitoring opportunity is associated with multiple DRX cycles, these multiple DRX cycles can be continuous or discontinuous in the time domain. In addition, the second DRX duration corresponds to the second DRX configuration, and the second DRX duration is located on the second group of carriers. The second DRX duration may include the On Duration time within all or part of the DRX cycles associated with the first DCP monitoring opportunity under the second DRX configuration, or in other words, the second DRX duration may include the On Duration time within all or part of the DRX cycles associated with the first DCP monitoring opportunity on the second group of carriers. For example, it can be set by default (or specified by the protocol) that if the UE determines not to monitor within the first DCP monitoring opportunity, the UE can sleep within the second DRX duration associated with the first DCP monitoring opportunity to save the power consumption of the UE; or it can be set by default (or specified by the protocol) that if the UE determines not to monitor within the first DCP monitoring opportunity, the UE can wake up within the second DRX duration associated with the first DCP monitoring opportunity to reduce the probability that the UE misses the data that the network device may send on the second group of carriers. In this case, the behavior of the UE on the second group of carriers is set by default or by the protocol, and no additional configuration of the network device is required, nor is it required for the UE to determine it in other ways, which can simplify the implementation of the network device and the UE.

Alternatively, the UE may sleep or wake up during the second DRX duration, which may also be instructed by the network device. For example, the network device sends configuration information to the UE, and correspondingly, the UE receives the configuration information from the network device, which may be sent, for example, via an RRC message, a system message, or other message. The configuration information may be sent on one or more carriers included in the first group of carriers. For example, if the main carrier configured by the network device for the UE belongs to the first group of carriers, the configuration information may be sent on the main carrier; or, the configuration information may also be sent on one or more carriers included in the second group of carriers. The configuration information may be configured such that: when the UE does not monitor during the DCP monitoring opportunity, the UE wakes up on the second group of carriers during the DRX duration associated with the DCP monitoring opportunity; or, the configuration information may be configured such that: when the UE does not monitor during the DCP monitoring opportunity, the UE sleeps on the second group of carriers during the DRX duration associated with the DCP monitoring opportunity. In this case, the network device can configure the UE to sleep or wake up on the second group of carriers through configuration information according to factors such as data transmission. For example, if the network device schedules the UE to send data or receive data in the DRX cycle associated with the first DCP listening opportunity on the second group of carriers, the network device can instruct the UE to wake up through configuration information, and if the network device does not schedule the UE to send data and receive data in the DRX cycle associated with the first DCP listening opportunity on the second group of carriers, the network device can instruct the UE to sleep through configuration information. In this way, the sleep or wake-up of the UE can meet the data transmission requirements.

S53: If the UE determines to monitor within the first DCP monitoring opportunity, the UE determines to sleep or wake up on the first group of carriers and determines to sleep or wake up on the second group of carriers according to the monitoring situation.

Optionally, if S51 is replaced according to the first determination method as above, then S53 can also be replaced by, if all or part of the time domain position corresponding to the first DCP monitoring opportunity is not within the first DRX activation time, the UE monitors the DCP within the first DCP monitoring opportunity, and determines the sleep or wake-up on the first group of carriers according to the monitoring situation, and determines the sleep or wake-up on the second group of carriers.

Alternatively, if S51 is replaced according to the second determination method as above, then S53 can also be replaced by, if the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, the UE monitors the DCP within the first DCP monitoring period, and determines the sleep or wake-up on the first group of carriers according to the monitoring situation, and determines the sleep or wake-up on the second group of carriers.

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

If the UE needs to monitor during the first DCP monitoring opportunity, the UE monitors during the first DCP monitoring opportunity, and determines whether to sleep or wake up on the first group of carriers and the second group of carriers based on the monitoring situation of the DCP during the first DCP monitoring opportunity, that is, the monitoring situation of the UE during the first DCP monitoring opportunity can determine the behavior of the UE on the first group of carriers, and can also determine the behavior of the UE on the second group of carriers. For example, refer to Figure 6, in which the rectangular box with slashes in Figure 6 represents the first DCP monitoring opportunity, and the DCP monitoring opportunity is not configured on FR2. The monitoring situation of the UE at the first DCP monitoring opportunity can determine the behavior of the UE on the first group of carriers, and can also determine the behavior of the UE on the second group of carriers.

As an optional implementation, the DCP is implemented in such a way that 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 is woken up in the DRX cycle associated with the DCP, and if the DCP is not monitored, it is sleep in the DRX cycle associated with the DCP. If the DCP is implemented in this way, then if the UE receives the DCP from the network device in the first DCP listening opportunity, the UE wakes up in the first DRX duration associated with the first DCP listening opportunity on the first group of carriers, and the UE wakes up in the second DRX duration associated with the first DCP listening opportunity on the second group of carriers; and if the UE does not receive the DCP from the network device in the first DCP listening opportunity, the UE sleeps in the first DRX duration associated with the first DCP listening opportunity on the first group of carriers, and the UE sleeps in the second DRX duration associated with the first DCP listening opportunity on the second group of carriers.

As another optional implementation, the DCP is implemented in such a way that the DCP includes indication information. If the network device sends the DCP and the indication information included in the DCP indicates wake-up, the UE is indicated to wake up within the DRX cycle associated with the DCP. If the network device sends the DCP and the indication information included in the DCP indicates sleep, the UE is indicated to sleep within 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 within the DRX cycle associated with the DCP. If the DCP is monitored and received and the indication information included in the DCP indicates sleep, the UE sleeps within the DRX cycle associated with the DCP. If DCP adopts this implementation method, then, if the UE receives a DCP from a network device within a first DCP listening opportunity, and the indication information included in the DCP indicates wake-up, the UE wakes up on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity, and the UE wakes up on the second group of carriers within the second DRX duration associated with the first DCP listening opportunity; and if the UE receives a DCP from a network device within the first DCP listening opportunity, and the indication information included in the DCP indicates sleep, the UE sleeps on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity, and the UE sleeps on the second group of carriers within the second DRX duration associated with the first DCP listening opportunity.

As another optional implementation, the DCP is implemented in such a way that the DCP includes first indication information and second indication information, the first indication information corresponds to the first group of carriers, or corresponds to the first DRX configuration, and the second indication information corresponds to the second group of carriers, or corresponds to the second DRX configuration. If the network device sends a DCP, and the first indication information included in the DCP indicates wake-up, then the UE is instructed to wake up within the DRX cycle of the first DRX configuration associated with the DCP. If the network device sends a DCP, and the first indication information included in the DCP indicates sleep, then the UE is instructed to sleep within the DRX cycle of the first DRX configuration associated with the DCP. The indication method of the second indication information is 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 within the DRX cycle of the first DRX configuration associated with the DCP. If the DCP is monitored and received, and the first indication information included in the DCP indicates sleep, the UE sleeps within the DRX cycle of the first DRX configuration associated with the DCP. The UE's understanding of the second indication information is also similar. If DCP is implemented in this way, then, if the UE receives a DCP from a network device within a first DCP listening opportunity, and the first indication information included in the DCP indicates wake-up, the UE wakes up on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity; and if the UE receives a DCP from a network device within the first DCP listening opportunity, and the first indication information included in the DCP indicates sleep, the UE sleeps on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity. Similarly, if the UE receives a DCP from a network device within the first DCP listening opportunity, and the second indication information included in the DCP indicates wake-up, the UE wakes up on the second group of carriers within the second DRX duration associated with the first DCP listening opportunity; and if the UE receives a DCP from a network device within the first DCP listening opportunity, and the second indication information included in the DCP indicates sleep, the UE sleeps on the second group of carriers within the second DRX duration associated with the first DCP listening opportunity. In this way, DCP can use different indication information to indicate sleep or wake-up within different DRX durations. For example, the network equipment can determine whether the corresponding indication information indicates wake-up or sleep based on the information transmission conditions on the two groups of carriers, so that the UE's sleep or wake-up behavior is more in line with business transmission requirements.

As another optional implementation, the DCP is implemented in such a way that two groups of carriers have corresponding DCPs respectively, for example, the DCP may include an identifier of a carrier group to distinguish DCPs of different carrier groups, or the formats of DCPs of different carrier groups are different. For one group of carriers, if the network device sends the DCP corresponding to the group of carriers, and the DCP indicates wake-up, then the UE is instructed to wake up on the group of carriers within the DRX cycle associated with the DCP; if the network device sends the DCP corresponding to the group of carriers, and the DCP indicates sleep, then the UE is instructed to sleep on the group of carriers within the DRX cycle associated with the DCP. If the DCP adopts this implementation, then, if the UE receives the DCP from the network device within the first DCP listening opportunity, and the DCP corresponds to the first group of carriers, if the DCP indicates wake-up, then the UE wakes up on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity, or, if the DCP indicates sleep, then the UE sleeps on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity. For the second group of carriers, the operation process of the network device and the UE is the same.

As another optional implementation, the DCP is implemented in such a way that two groups of carriers have corresponding DCPs respectively, for example, the DCP may include an identifier of the carrier group to distinguish the DCPs of different carrier groups, or the formats of the DCPs of different carrier groups are different. For one 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 within the DRX cycle 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 within the DRX cycle associated with the DCP. If the DCP adopts this implementation, then, if the UE receives the DCP from the network device during the first DCP listening opportunity, and the DCP corresponds to the first group of carriers, the UE wakes up on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity, or if the UE does not receive the DCP corresponding to the first group of carriers from the network device during the first DCP listening opportunity, the UE sleeps on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity. For the second group of carriers, the operation process of the network device and the UE is the same.

In an embodiment of the present application, the UE sleeps during the first DRX duration, which can be implemented in the following manner: the UE does not start or restart the first DRX duration timer at the start time of the first DRX duration. The first DRX duration timer is configured by the first DRX configuration, and the first DRX duration timer corresponds to the first group of carriers. If the first DRX duration timer is not started, the UE does not start the first DRX duration timer at the start time of the first DRX duration, and if the first DRX duration timer is in a running state, the UE does not restart the first DRX duration timer at the start time of the first DRX duration, so that the UE can sleep during the first DRX duration. The implementation method of the UE sleeping during the second DRX duration is also similar, for example, it is implemented in the following manner: the UE does not start or restart the second DRX duration timer at the start time of the second DRX duration. The second DRX duration timer is configured by the second DRX configuration, and the second DRX duration timer corresponds to the second group of carriers.

UE wakes up within the first DRX duration, which can be achieved in the following manner: 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 start time of the first DRX duration, and if the first DRX duration timer is in a running state, the UE restarts the first DRX duration timer at the start time of the first DRX duration, so that the UE can wake up within the first DRX duration. The implementation method of UE waking up within the second DRX duration is similar, for example, it is achieved in the following manner: 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 the second DRX configuration, and the second DRX duration timer corresponds to the second group of carriers.

S52 and S53 are two parallel solutions and will not be executed at the same time.

In an embodiment of the present application, two DRX configuration technologies can be used in combination with a wake-up signal, and the behavior of the terminal device in the combined case is specified. For example, when 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 can be specified by default, protocol specification, or network configuration; and when the terminal device monitors the DCP monitoring opportunity corresponding to the first group of carriers, the monitoring situation of the terminal device on the DCP monitoring opportunity corresponding to the first group of carriers 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, which reduces the power consumption of the terminal device monitoring the DCP and increases the flexibility of network device scheduling. The monitoring situation of the terminal device on one group of carriers can be applied to two groups of carriers, so that both groups of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two groups of carriers. In addition, the network device does not need to configure DCP for the second group of carriers, which can also save signaling overhead.

An embodiment of the present application provides a second communication method. Please refer to FIG8 , which is a flowchart of the method.

S81. The UE determines whether to monitor the DCP within the first DCP monitoring opportunity. In other words, the UE determines whether to monitor within the first DCP monitoring opportunity.

Optionally, S81 may also be replaced by the UE determining whether the time domain position of the first DCP monitoring opportunity is within the first DRX activation time.

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

For more information about S81, such as how the UE determines whether to perform monitoring within the first DCP monitoring opportunity, etc., please refer to S51 in the embodiment shown in FIG. 5 .

S82: If the UE determines to monitor within the first DCP monitoring opportunity, the UE determines to sleep or wake up on the first group of carriers and determines to sleep or wake up on the second group of carriers according to the monitoring situation.

Alternatively, if S81 is replaced by the UE determining whether the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, then S82 can be replaced by if all or part of the time domain position corresponding to the first DCP monitoring opportunity is not within the first DRX activation time, the UE monitors the DCP within the first DCP monitoring opportunity, and determines the sleep or wake-up on the first group of carriers according to the monitoring situation, and determines the sleep or wake-up on the second group of carriers.

Alternatively, if S81 is replaced by the UE determining whether the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, then S82 can be replaced by if the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, the UE monitors the DCP within the first DCP monitoring opportunity, and determines to sleep or wake up on the first group of carriers based on the monitoring situation, and determines to sleep or wake up on the second group of carriers.

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

In an embodiment of the present application, the network device can send a DCP on a first carrier, and the first carrier belongs to a first group of carriers. For example, the network device configures a DCP for one or more carriers included in the first group 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 can configure a DCP for the main carrier, and the first carrier is the main carrier of the UE. The network device can send the DCP on the main carrier without configuring the DCP on other carriers to save transmission overhead. If the UE needs to monitor on the first group of carriers, it can monitor on all carriers included in the first group of carriers, or the network device can pre-configure which carriers to send the DCP on, and the UE only needs to monitor on these carriers.

The network device can send a DCP on a second carrier, and the second carrier belongs to the second group of carriers. For example, the network device configures a DCP for one or more carriers included in the second group of carriers, and the second carrier includes the one or more carriers. If the UE needs to monitor on the second group of carriers, it can monitor on all carriers included in the second group of carriers, or the network device can pre-configure which carriers to send the DCP on, and the UE only needs to monitor on these carriers. That is to say, in an embodiment of the present application, the network device configures a DCP for the first group of carriers and also configures a DCP for the second group of carriers.

Although DCP is configured for both the first group of carriers and the second group of carriers, the UE first determines whether to monitor on the first group of carriers. If it is possible to monitor on the first group of carriers, the UE monitors on the first group of carriers, for example, monitors within the first DCP monitoring opportunity, and determines whether to sleep or wake up on the first group of carriers and the second group of carriers according to the monitoring result. In this case, the UE does not need to monitor on the second group of carriers, for example, the UE does not monitor within the second DCP monitoring opportunity. The second DCP monitoring opportunity is a DCP monitoring opportunity configured on the second group of carriers, and the second DCP monitoring opportunity applies the second DRX configuration. Under the second DRX configuration, there are multiple On Duration times, so the DCP monitoring opportunity may also appear multiple times, for example, there may be a DCP monitoring opportunity before each DRX cycle starts. Then, the second DCP monitoring opportunity is, for example, the current monitoring opportunity for the UE, for example, the second DCP monitoring opportunity is located before the start of the OnDuration time of a DRX cycle under the second DRX configuration, or the second DCP monitoring opportunity is located before the start of the OnDuration time of a DRX cycle on the second group of carriers. In the case that the UE is able to monitor on the first group of carriers, since the UE does not need to monitor on the second group of carriers, the power consumption of the UE due to monitoring can be reduced.

For more information about S82, such as how the UE determines whether to sleep or wake up on the first group of carriers and the second group of carriers according to the monitoring situation, please refer to S53 in the embodiment shown in FIG. 5 .

It should be noted that, for the introduction of the first DRX duration associated with the first DCP monitoring opportunity, etc., reference may be made to S52 in the embodiment shown in FIG5. In addition, the time domain positions of the first DCP monitoring opportunity and the second DCP monitoring opportunity may be the same, or the time domain position of the first DCP monitoring may be earlier than the time domain position of the second DCP monitoring opportunity. Therefore, when referring to S52, the second DRX duration associated with the first DCP monitoring opportunity described in S52 may also be considered as the DRX duration associated with the second DCP monitoring opportunity on the second group of carriers in the embodiment of the present application.

S83. If the UE determines not to monitor the DCP within the first DCP monitoring opportunity, the UE determines whether to monitor the DCP within the second DCP monitoring opportunity. In other words, the UE determines whether to monitor the DCP within the second DCP monitoring opportunity.

Alternatively, if S81 is replaced by the UE determining whether the time domain position of the first DCP listening opportunity is within the first DRX activation time, then S83 can be replaced by if the time domain position of the first DCP listening opportunity is within the first DRX activation time, the UE determines whether to listen to DCP within the second DCP listening opportunity, or in other words, the UE determines whether to listen within the second DCP listening opportunity.

Alternatively, if S81 is replaced by the UE determining whether the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, then S83 can be replaced by if the maximum 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 determines whether to monitor the DCP within the second DCP monitoring opportunity, or in other words, the UE determines whether to monitor within the second DCP monitoring opportunity.

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

In addition, as described in S83, the UE determines whether to monitor within the second DCP monitoring opportunity, and corresponding replacements may also be performed. For specific replacement methods, reference may be made to the introduction to the replacement method of S81.

The way in which the UE determines whether to monitor during the second DCP monitoring opportunity is similar to the way in which the UE determines whether to monitor during the first DCP monitoring opportunity. Please refer to the foregoing introduction of the embodiments of the present application, or refer to S51 in the embodiment shown in Figure 5.

In addition, if the UE does not monitor within the first DCP monitoring opportunity, then optionally, the UE may wake up within the first DRX duration on the first group of carriers to avoid missing the PDCCH.

S84: If the UE determines to monitor within the second DCP monitoring opportunity, the UE determines to sleep or wake up on the second group of carriers according to the monitoring situation. As described in S84, the UE determines to monitor within the second DCP monitoring opportunity, and corresponding replacements may also be performed. For specific replacement methods, reference may be made to the introduction of the replacement methods of S82.

If the UE determines to monitor within the second DCP monitoring opportunity, the UE can monitor within the second DCP monitoring opportunity. At this time, the monitoring result of the second DCP monitoring opportunity can be used to determine whether the UE sleeps or wakes up on the second group of carriers. For example, refer to Figure 9, in which the rectangular box with "\" represents the first DCP monitoring opportunity, and the rectangular box with "/" represents the second DCP monitoring opportunity. If the UE can monitor the first DCP monitoring opportunity, the UE can determine whether to sleep or wake up on the first group of carriers according to the monitoring situation of the first DCP monitoring opportunity, and can determine whether to sleep or wake up on the second group of carriers; if the UE cannot monitor the first DCP monitoring opportunity, but can monitor the second DCP monitoring opportunity, the UE can determine whether to sleep or wake up on the second group of carriers according to the monitoring situation of the second DCP monitoring opportunity.

As an optional implementation, DCP is implemented in such a way that if the network device sends a DCP, the UE is instructed to wake up within the DRX cycle associated with the DCP; if the network device does not send a DCP, the UE is instructed to sleep within the DRX cycle associated with the DCP. For the UE, if it monitors and receives the DCP, it wakes up within the DRX cycle associated with the DCP; if it does not monitor the DCP, it sleeps within the DRX cycle associated with the DCP. If DCP is implemented in this way, then if the UE receives a DCP from the network device within the second DCP listening opportunity, the UE wakes up within the second DRX duration associated with the second DCP listening opportunity on the second group of carriers; and if the UE does not receive a DCP from the network device within the second DCP listening opportunity, the UE sleeps within the second DRX duration associated with the second DCP listening opportunity on the second group of carriers.

As another optional implementation, the DCP is implemented in such a way that the DCP includes indication information. If the network device sends the DCP and the indication information included in the DCP indicates wake-up, the UE is instructed to wake up in the DRX cycle associated with the DCP. If the network device sends the DCP and the indication information included in the DCP indicates 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. 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 is implemented in this way, then if the UE receives the DCP from the network device in the second DCP listening opportunity and the indication information included in the DCP indicates wake-up, the UE wakes up in the second DRX duration associated with the second DCP listening opportunity on the second group of carriers; and if the UE receives the DCP from the network device in the second DCP listening opportunity and the DCP indicates sleep, the UE sleeps in the second DRX duration associated with the second DCP listening opportunity on the second group of carriers.

In the above two implementations, the monitoring result of the second DCP monitoring opportunity is not used to determine whether the UE sleeps or wakes up on the first group of carriers.

As another optional implementation, the DCP is implemented in such a way that the DCP includes third indication information and fourth indication information, the third indication information corresponds to the first group of carriers, or corresponds to the first DRX configuration, and the fourth indication information corresponds to the second group of carriers, or corresponds to the second DRX configuration. If the network device sends a DCP, and the third indication information included in the DCP indicates wake-up, then the UE is instructed to wake up within the DRX cycle of the first DRX configuration associated with the DCP; if the network device sends a DCP, and the third indication information included in the DCP indicates sleep, then the UE is instructed to sleep within the DRX cycle of the first DRX configuration associated with the DCP. The indication method of the fourth indication information is also similar. 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 within the DRX cycle of the first DRX configuration associated with the DCP; if the DCP is monitored and received, and the third indication information included in the DCP indicates sleep, the UE sleeps within the DRX cycle of the first DRX configuration associated with the DCP. The UE's understanding of the fourth indication information is also similar. If DCP is implemented in this way, the monitoring result of the second DCP monitoring opportunity can be used to determine whether the UE sleeps or wakes up on the second group of carriers, and can also be used to determine whether the UE sleeps or wakes up on the first group of carriers. For example, if the UE receives a DCP from a network device during the second DCP monitoring opportunity, and the third indication information included in the DCP indicates wake-up, the UE wakes up on the first group of carriers during the first DRX duration associated with the first DCP monitoring opportunity (or, the second DCP monitoring opportunity); and if the UE receives a DCP from a network device during the second DCP monitoring opportunity, and the third indication information included in the DCP indicates sleep, the UE sleeps on the first group of carriers during the first DRX duration associated with the first DCP monitoring opportunity (or, the second DCP monitoring opportunity). Similarly, if the UE receives a DCP from the network device within the second DCP listening opportunity, and the fourth indication information included in the DCP indicates wake-up, the UE wakes up on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity; and if the UE receives a DCP from the network device within the second DCP listening opportunity, and the fourth indication information included in the DCP indicates sleep, the UE sleeps on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity.

In this way, DCP can use different indication information to indicate sleep or wake-up within different DRX durations. For example, the network equipment can determine whether the corresponding indication information indicates wake-up or sleep based on the information transmission conditions on the two groups of carriers, so that the UE's sleep or wake-up behavior is more in line with business transmission requirements.

As another optional implementation, the DCP is implemented in such a way that two groups of carriers have corresponding DCPs respectively, for example, the DCP may include an identifier of the carrier group to distinguish the DCPs of different carrier groups, or the formats of the DCPs of different carrier groups are different. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, and the DCP indicates wake-up, then the UE is instructed to wake up on the group of carriers within the DRX cycle associated with the DCP; if the network device sends the DCP corresponding to the group of carriers, and the DCP indicates sleep, then the UE is instructed to sleep on the group of carriers within the DRX cycle associated with the DCP. If the DCP adopts this implementation, then, if the UE receives the DCP from the network device during the second DCP listening opportunity, and the DCP corresponds to the second group of carriers, if the DCP indicates wake-up, then the UE wakes up on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity, or, if the DCP indicates sleep, then the UE sleeps on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity.

As another optional implementation, the DCP is implemented in such a way that two groups of carriers have corresponding DCPs respectively, for example, the DCP may include an identifier of the carrier group to distinguish the DCPs of different carrier groups, or the formats of the DCPs of different carrier groups are different. 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 within the DRX cycle 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 within the DRX cycle associated with the DCP. If the DCP adopts this implementation, then, if the UE receives the DCP from the network device during the second DCP listening opportunity, and the DCP corresponds to the second group of carriers, the UE wakes up on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity, or, if the UE does not receive the DCP corresponding to the second group of carriers from the network device during the second DCP listening opportunity, the UE sleeps on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity.

S85. If the UE determines not to monitor during the second DCP monitoring opportunity, the UE wakes up or sleeps during the second DRX duration associated with the second DCP monitoring opportunity on the second group of carriers. For S85, the UE determines not to monitor during the second DCP monitoring opportunity, and corresponding replacements may also be performed. For specific replacement methods, reference may be made to the introduction to the replacement methods of S83.

If the UE determines not to monitor during the second DCP monitoring opportunity, the UE does not monitor during the second DCP monitoring opportunity. In the case of S85, the UE monitors neither the first DCP monitoring opportunity nor the second DCP monitoring opportunity. In this case, in order to reduce the probability that the UE misses the PDCCH that the network device may send on the first group of carriers, the UE can be awakened during the first DRX duration on the first group of carriers.

For the second group of carriers, for example, it can be set by default (or specified by the protocol) that if the UE determines not to monitor within the second DCP monitoring opportunity (or if the UE determines not to monitor within the first DCP monitoring opportunity and not to monitor within the second DCP monitoring opportunity), the UE can sleep within the second DRX duration associated with the second DCP monitoring opportunity on the second group of carriers to save the power consumption of the UE; or, it can be set by default (or specified by the protocol) that if the UE determines not to monitor within the second DCP monitoring opportunity (or if the UE determines not to monitor within the first DCP monitoring opportunity and not to monitor within the second DCP monitoring opportunity), the UE can wake up within the second DRX duration associated with the second DCP monitoring opportunity on the second group of carriers to reduce the probability that the UE misses the data that the network device may send on the second group of carriers. In this case, the behavior of the UE on the second group of carriers is set by default or by the protocol, and no additional configuration of the network device is required, nor is it required for the UE to determine it in other ways, which can simplify the implementation of the network device and the UE.

Alternatively, the sleep or wake-up of the UE on the second group of carriers within the second DRX duration may also be indicated by the network device. For example, the network device sends configuration information to the UE, and correspondingly, the UE receives the configuration information from the network device, which may be sent, for example, via an RRC message, a system message, or other message. The configuration information may be sent on one or more carriers included in the first group of carriers. For example, if the main carrier configured by the network device for the UE belongs to the first group of carriers, the configuration information may be sent on the main carrier; or, the configuration information may also be sent on one or more carriers included in the second group of carriers. The configuration information may be configured such that: when the UE does not monitor within the DCP monitoring opportunity, the UE wakes up on the second group of carriers within the DRX duration associated with the DCP monitoring opportunity; or, the configuration information may be configured such that: when the UE does not monitor within the DCP monitoring opportunity, the UE sleeps on the second group of carriers within the DRX duration associated with the DCP monitoring opportunity. In this case, the network device can configure the UE to sleep or wake up on the second group of carriers through configuration information according to factors such as data transmission. For example, if the network device schedules the UE to send data or receive data in the DRX cycle associated with the second DCP listening opportunity on the second group of carriers, the network device can instruct the UE to wake up through configuration information, and if the network device does not schedule the UE to send data and receive data in the DRX cycle associated with the second DCP listening opportunity on the second group of carriers, the network device can instruct the UE to sleep through configuration information. In this way, the sleep or wake-up of the UE can meet the data transmission requirements.

For other contents, such as how to implement the UE to sleep during the DRX duration, or how to implement the UE to wake up during the DRX duration, etc., please refer to the relevant introduction of the embodiment shown in Figure 5.

In an embodiment of the present application, two DRX configuration technologies can be used in combination with a wake-up signal, and the behavior of the terminal device in the combined case is specified. For example, the UE preferentially monitors the first DCP listening opportunity. If it can monitor the first DCP listening opportunity, the UE does not need to monitor the second DCP listening opportunity, so as to save the power consumption caused by the UE monitoring the DCP listening opportunity. If the UE cannot monitor the first DCP listening opportunity, the UE can also determine whether it can monitor the second DCP listening opportunity, so that the UE's behavior is carried out as much as possible under the indication of the monitoring result, so as to better meet the requirements of the network device. In an embodiment of the present application, the network device can configure the second DCP listening opportunity for the second group of carriers, so that the network device has stronger control over the behavior of the UE on the second group of carriers, and also increases the flexibility of the network device scheduling.

An embodiment of the present application provides a third communication method. Please refer to FIG. 10 , which is a flowchart of the method.

S101. A network device sends DCI to a UE on a first carrier, and correspondingly, the UE receives DCI from the network device on the first carrier. The first carrier may include one or more carriers, and the first carrier may belong to a first group of carriers or a second group of carriers. The first group of carriers applies a first DRX configuration, and the second group of carriers applies a second DRX configuration.

DCP is also a type of DCI and is also subject to the limitations of the DCI size budget. In an embodiment of the present application, the network device does not need to configure DCP for the UE, or in other words, the network device does not need to send DCP, but implements the function of DCP through other DCIs other than DCP. The size of DCP is generally different from the size of other ordinary DCIs. According to the DCI size budget of the UE, DCP occupies a size, which reduces the types of DCI that the UE can receive. However, in an embodiment of the present application, the network device does not need to send DCP, but sends ordinary DCI, then DCP will not occupy the DCI size overhead, so that the UE can receive more types of DCI.

Alternatively, in an embodiment of the present application, the network device may also configure DCP for the UE, for example, the network device configures DCP for the first group of carriers. However, in some cases, the UE cannot monitor the DCP, for example, due to the limitation of the DCI size budget, the UE determines not to monitor the DCP, or because the corresponding DCP monitoring opportunity is within the DRX activation time, the UE determines not to monitor the DCP. In these cases, the network device may also implement the DCP function by sending other DCIs. For an introduction to the first group of carriers, the second group of carriers, the first DRX configuration, the second DRX configuration, and the DRX activation time, please refer to the embodiment shown in Figure 5 or the embodiment shown in Figure 8.

Optionally, in an embodiment of the present application, regardless of whether the network device is configured with DCP, or in other words, regardless of whether the network device sends DCP, the network device can send DCI with DCP function within the DCP listening opportunity. For example, the network device can send DCI with DCP function within the first DCP listening opportunity, and the UE can receive DCI with DCP function within the first DCP listening opportunity. For the first DCP listening opportunity and other contents, please refer to the introduction of the embodiment shown in Figure 5. Alternatively, the network device may not send DCI with DCP function within the DCP listening opportunity, but send DCI with DCP function at other times. For example, the network device sends DCI with DCP function within the On Duration time of the DRX cycle.

Exemplarily, if the network device is configured with DCP, or the network device sends DCI with DCP function within the DCP listening opportunity, then the UE can determine whether to listen to DCP within the first DCP listening opportunity. If the UE determines to listen to DCP within the first DCP listening opportunity, the UE can listen to DCP within the first DCP listening opportunity, or listen to DCI with DCP function. Regarding the way in which the UE determines whether to listen to DCP within the first DCP listening opportunity, please refer to S51 in the embodiment shown in Figure 5. For example, the first determination method is to determine according to the time domain position of the first DCP listening opportunity; for example, the second determination method is to determine according to the DCI size budget; for example, the third determination method is to determine according to the time domain position of the first DCP listening opportunity and the DCI size budget, etc. For this, please refer to the description of S51 of the embodiment shown in Figure 5.

If the DCI is used to implement the function of DCP, then optionally, the DCI can indicate that the DCI is used to implement the DCP function through a second field included in the DCI. The second field, for example, includes one or more of the following fields: frequency domain resource assignment (FDRA) field, modulation and coding scheme (MCS) field, new data indicator (NDI) field, redundancy version (RV) field, hybrid automatic repeat request process number (hybrid automatic repeat request process number), antenna port (a ntenna port (s)), or, demodulation reference signal sequence initialization (demodulation reference signal sequence initialization) field. In DCI, the MCS field occupies 5 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 the FDRA field; or, the second field is the MCS field; or, the second field includes the MCS field and the NDI field; or, the second field includes the FDRA field, the MCS field, and the RV field, and so on.

If DCI is used for normal data scheduling but not for implementing the DCP function, the values of the above fields included in the DCI are related to the scheduled data, for example, the value of the MCS field can indicate the MCS of the scheduled data. If DCI is used to implement the DCP function, the value of the second field can be the first value, which can be specified by the protocol, or can be defaulted, or can be configured by the network device. For example, the first value is all 0s, or all 1s, etc. Through this value, the UE can clearly understand that the current DCI is used to implement the DCP function.

If the value of the second field is the first value, the DCI may also include the second indication information, and if the value of the second field is not the first value, the DCI does not include the second indication information. For example, the value of the second field is not the first value, but the normal value of the second field. At this time, the DCI is not used to implement the DCP function, but to implement the normal function of the DCI, such as scheduling data, etc., so the DCI naturally does not need to include the second indication information. Therefore, if the value of the second field is the first value, it can be indicated that the DCI also includes the second indication information. The second indication information can indicate that the DCI is dormant on the second group of carriers during the second DRX duration associated with the DCI, or indicate that the DCI is awakened on the second group of carriers during the second DRX duration associated with the DCI. Among them, on the second group of carriers, according to the second DRX configuration, the DCI used to implement the DCP function can be associated with one or more DRX cycles. If the DCI is configured on the first group of carriers and not configured on the second group of carriers, this association is an association in the time domain position. For example, on the second group of carriers, one or more DRX cycles that are later than the DCI in the time domain can be associated with the DCI. If the DCI is associated with multiple DRX cycles, the multiple DRX cycles may be continuous or discontinuous in the time domain. In addition, the second DRX duration corresponds to the second DRX configuration, and the second DRX duration is located on the second group of carriers. The second DRX duration may include the On Duration time within all or part of the DRX cycles associated with the DCI under the second DRX configuration, or in other words, the second DRX duration may include the On Duration time within all or part of the DRX cycles associated with the DCI on the second group of carriers.

For example, the second indication information may occupy one or more bits. Taking the second indication information occupying one bit as an example, for example, if the value of the bit is "1", it indicates waking up on the second group of carriers during the second DRX duration associated with the DCI; if the value of the bit is "0", it indicates sleeping on the second group of carriers during the second DRX duration associated with the DCI. Alternatively, if the second indication information occupies more bits, there may be other indication methods. The second indication information included in the DCI indicates the sleep or wake-up of the UE on the second group of carriers. The UE does not need to monitor the DCP, which reduces the number of DCI sizes that the UE needs to monitor, and also regulates the sleep or wake-up of the UE on the second group of carriers. Moreover, if the network device instructs the UE to sleep or wake up on the second group of carriers, the network device can indicate according to the service of the UE on the second group of carriers, so that the sleep or wake-up behavior of the UE on the second group of carriers is more in line with the service needs of the UE.

There are different implementations for the sleep or wake-up of the UE on the first group of carriers, which are described below with examples.

As an optional implementation, it can be set by default (or specified by the protocol) that the UE wakes up on the first group of carriers during the first DRX duration associated with the DCI. Because if the second indication information indicates that the UE wakes up on the second group of carriers during the second DRX duration, and the network device needs to schedule the data transmission of the UE on the second group of carriers on the first group of carriers, then if the UE sleeps on the first group of carriers during the first DRX duration, it may not be able to receive the scheduling information from the network device, and thus cannot perform data transmission on the second group of carriers. Therefore, it can be set by default (or specified by the protocol) that the UE wakes up on the first group of carriers during the first DRX duration to reduce the probability of the UE missing the scheduling information and reduce the transmission delay of the service. Alternatively, it can be set by default (or specified by the protocol) that the UE sleeps on the first group of carriers during the first DRX duration associated with the DCI, which can save the power consumption of the UE. In this way, the first carrier can belong to the first group of carriers, or to the second group of carriers, that is, the network device can send the DCI on the first group of carriers, or send the DCI on the second group of carriers.

Among them, on the first group of carriers, according to the first DRX configuration, the DCI used to implement the DCP function can be associated with one or more DRX cycles. For example, on the first group of carriers, one or more DRX cycles that are later than the DCI in the time domain can be associated with the DCI. And if the DCI is associated with multiple DRX cycles, these multiple DRX cycles can be continuous or discontinuous in the time domain. In addition, the first DRX duration corresponds to the first DRX configuration, and the first DRX duration is located on the first group of carriers. The first DRX duration may include the On Duration time within all or part of the DRX cycle associated with the DCI under the first DRX configuration, or in other words, the first DRX duration may include the On Duration time within all or part of the DRX cycle associated with the DCI on the first group of carriers.

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

As another optional implementation, if the value of the second field is the first value, then the DCI may also include the first indication information, and if the value of the second field is not the first value, or in other words, if the value of the second field is the second value, then the DCI does not include the first indication information. The second value may be any value of the second field except the first value. For example, the value of the second field is not the first value, but the ordinary value of the second field. At this time, the DCI is not used to implement the DCP function, but to implement the normal function of the DCI, such as scheduling data, etc., then the DCI naturally does not need to include the first indication information. Therefore, if the value of the second field is the first value, it can indicate that the DCI also includes the first indication information. The first indication information may indicate sleeping on the first group of carriers within the first DRX duration associated with the DCI, or indicating waking up on the first group of carriers within the first DRX duration associated with the DCI. Reference may be made to Figure 11, taking the example of DCI configuration on the first group of carriers, the first group of carriers belonging to FR1, and the second group of carriers belonging to FR2. The DCI received by the UE on FR1 can indicate the sleep or wake-up of the UE on the second group of carriers, and optionally, can also indicate the sleep or wake-up of the UE on the first group of carriers. The dotted arrows represent optional processes. In this way, the first carrier can belong to the first group of carriers, or to the second group of carriers, that is, the network device can send the DCI on the first group of carriers, or send the DCI on the second group of carriers.

For example, the first indication information may occupy one or more bits. Taking the first indication information occupying one bit as an example, for example, if the value of the bit is "1", it indicates waking up on the first group of carriers within the first DRX duration associated with the DCI; if the value of the bit is "0", it indicates sleeping on the first group of carriers within the first DRX duration associated with the DCI. Alternatively, if the first indication information occupies more bits, there may be other indication methods. The first indication information included in the DCI indicates the sleep or wake-up of the UE on the first group of carriers. The UE does not need to monitor the DCP, which reduces the number of DCI sizes that the UE needs to monitor, and also regulates the sleep or wake-up of the UE on the first group of carriers. Moreover, if the network device instructs the UE to sleep or wake up on the first group of carriers, the network device can indicate according to the service of the UE on the first group of carriers, so that the sleep or wake-up behavior of the UE on the first group of carriers is more in line with the service needs of the UE.

In this implementation manner, the network device indicates the sleep or wake-up of the two groups of carriers respectively through the second indication information and the first indication information, so that the behavior of the UE is clearer and more in line with business requirements.

As another optional implementation, if the DCI includes second indication information, the second indication information may indicate the behavior of the UE on the first group of carriers in addition to indicating the behavior of the UE on the second group of carriers. That is, the second indication information may indicate sleep or wake-up on the second group of carriers during the second DRX duration associated with the DCI, and indicate sleep or wake-up on the first group of carriers during the first DRX duration associated with the DCI. Alternatively, the second indication information indicates sleep or wake-up during the DRX duration associated with the DCI. In this way, the first carrier may belong to the first group of carriers, or to the second group of carriers, that is, the network device may send the DCI on the first group of carriers, or send the DCI on the second group of carriers.

For example, the second indication information occupies one or more bits. Taking the second indication information occupying 1 bit as an example, if the value of the bit is "1", it indicates waking up on the first group of carriers during the first DRX duration associated with the DCI, and indicating waking up on the second group of carriers during the second DRX duration associated with the DCI; if the value of the bit is "0", it indicates sleeping on the first group of carriers during the first DRX duration associated with the DCI, and indicating sleeping on the second group of carriers during the second DRX duration associated with the DCI. Or, taking the second indication information occupying 2 bits as an example, the 2 bits indicate the first group of carriers and the second group of carriers respectively. For example, the high-order bit of the 2 bits indicates the first group of carriers, and the low-order bit indicates the second group of carriers. If the value of the high-order bit of the 2 bits is "1", it indicates waking up on the first group of carriers during the first DRX duration associated with the DCI; if the value of the high-order bit of the 2 bits is "0", it indicates sleeping on the first group of carriers during the first DRX duration associated with the DCI. The low-order bit of the 2 bits also indicates the behavior of the UE on the second group of carriers in a similar way.

In this way, the network device can indicate the behavior of the UE on the first group of carriers and the second group of carriers through the second indication information, without more indication information, which can save signaling overhead and make the behavior of the UE clearer.

As another optional implementation, the first carrier may include at least two carriers, and the at least two carriers include both carriers belonging to the first group of carriers and carriers belonging to the second group of carriers. For example, the first carrier includes the second carrier and the third carrier, the second carrier belongs to the first group of carriers, and the third carrier belongs to the second group of carriers. This situation can be understood as that the network device sends DCI on both the first group of carriers and the second group of carriers, so the DCI may also include at least two, taking the DCI including the first DCI and the second DCI as an example, the first DCI is sent on the second carrier, and the second DCI is sent on the third carrier. Then, the first DCI may indicate the behavior of the UE on the first group of carriers, and the second DCI may indicate the behavior of the UE on the second group of carriers. For example, the first DCI may indicate that the UE sleeps on the first group of carriers during the first DRX duration associated with the DCI, or indicates that the UE wakes up on the first group of carriers during the first DRX duration associated with the DCI. The second DCI may indicate that the UE sleeps on the second group of carriers during the second DRX duration associated with the DCI, or indicates that the UE wakes up on the second group of carriers during the second DRX duration associated with the DCI. In this case, it can also be considered that the first DCI includes the first indication information, and the second DCI includes the second indication information. Then, the second DCI may include the second field, and the first DCI may also include the first field. For example, if the value of the second field is the first value, the second DCI may also include the 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. If the value of the first field is the third value, the first DCI may also include the first indication information, and if the value of the first field is not the third value, the first DCI does not include the first indication information. For an introduction to this implementation method, please refer to the previous text. In addition, for the indication method of the second indication information for the behavior of the UE on the second group of carriers, and the indication method of the first indication information for the behavior of the UE on the first group of carriers, please refer to the introduction in the previous text.

In this way, the network device can instruct the UE's behavior on different carriers respectively through DCI carried on different carriers, and the instruction is clearer.

S102. The UE determines, according to the second indication information included in the DCI, whether to sleep or wake up on the second group of carriers within the second DRX duration associated with the DCI. Alternatively, there may be no determination process. For example, S102 may be replaced by the UE determining, according to the second indication information included in the DCI, whether to sleep or wake up on the second group of carriers within the second DRX duration associated with the DCI. Alternatively, according to the introduction in S101, if the DCI includes the first DCI and the second DCI, then S102 may be replaced by the UE determining, according to the second indication information included in the second DCI, whether to sleep or wake up on the second group of carriers within the second DRX duration associated with 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 the second indication information. Then, if the second indication information indicates to sleep on the second group of carriers within the second DRX duration associated with the DCI, the UE determines to sleep on the second group of carriers within the second DRX duration associated with the DCI, and the UE sleeps on the second group of carriers within the second DRX duration; or, if the second indication information indicates to wake up on the second group of carriers within the second DRX duration associated with the DCI, the UE determines to wake up on the second group of carriers within the second DRX duration associated with the DCI, and the UE sleeps on the first group of carriers within the first DRX duration.

S103, the UE determines to sleep or wake up on the first group of carriers within the first DRX duration associated with the DCI. Alternatively, there may be no determination process, for example, S103 may also be replaced by the UE sleeping or waking up on the first group of carriers within the first DRX duration associated with the DCI. Alternatively, according to the introduction in S101, if the DCI includes the first DCI and the second DCI, then S103 may be replaced by the UE determining to sleep or wake up on the first group of carriers within the first DRX duration associated with the first DCI.

If by default (or as specified by the protocol), the UE wakes up on the first group of carriers during the first DRX duration associated with the DCI, then if the network device is not configured with DCP, the UE wakes up on the first group of carriers during the first DRX duration; or if the network device is configured with DCP, then if the UE does not monitor the DCP on the first group of carriers, the UE wakes up on the first group of carriers during the first DRX duration. Or, if by default (or as specified by the protocol), the UE sleeps on the first group of carriers during the first DRX duration associated with the DCI, then if the network device is not configured with DCP, the UE sleeps on the first group of carriers during the first DRX duration; or if the network device is configured with DCP, then if the UE does not monitor the DCP on the first group of carriers, the UE wakes up on the first group of carriers during the first DRX duration. For the circumstances under which the UE does not monitor the DCP on the first group of carriers, reference may be made to the introduction of the embodiment shown in FIG. 5.

Alternatively, if the DCI also includes first indication information, and the first indication information indicates to sleep on the first group of carriers within the first DRX duration associated with the DCI. Then, if the DCI includes the first indication information, the UE sleeps on the first group of carriers within the first DRX duration; or, if the DCI does not include the first indication information, the UE sleeps on the first group of carriers within the first DRX duration. Alternatively, if the first indication information included in the DCI indicates to wake up on the first group of carriers within the first DRX duration associated with the DCI, the UE wakes up on the first group of carriers within the first DRX duration; or, if the first indication information included in the DCI indicates to sleep on the first group of carriers within the first DRX duration associated with the DCI, the UE sleeps on the first group of carriers within the first DRX duration.

Alternatively, if the second indication information indicates both the behavior of the UE on the first group of carriers and the behavior of the UE on the second group of carriers, then if the second indication information indicates sleeping within the DRX duration associated with the DCI, the UE sleeps within the first DRX duration on the first group of carriers and sleeps within the second DRX duration on the second group of carriers; or, if the second indication information indicates waking up within the DRX duration associated with the DCI, the UE wakes up within the first DRX duration on the first group of carriers and wakes up within the second DRX duration on the second group of carriers.

Alternatively, if the DCI includes a first DCI and a second DCI, the first DCI includes first indication information, the second DCI includes second indication information, the second indication information indicates the behavior of the UE on the second group of carriers, and the first indication information indicates the behavior of the UE on the first group of carriers. Then, if the first indication information included in the first DCI indicates waking up on the first group of carriers within the first DRX duration associated with the first DCI, the UE wakes up on the first group of carriers within the first DRX duration; or, if the first indication information included in the first DCI indicates sleeping on the first group of carriers within the first DRX duration associated with the first DCI, the UE sleeps on the first group of carriers within the first DRX duration. If the second indication information included in the second DCI indicates waking up on the second group of carriers within the second DRX duration associated with the second DCI, the UE wakes up on the second group of carriers within the second DRX duration; or, if the second indication information included in the second DCI indicates sleeping on the second group of carriers within the second DRX duration associated with the second DCI, the UE sleeps on the second group of carriers within the second DRX duration.

For the network device, if DCP is not configured, the network device does not need to send DCP, and the UE does not need to monitor DCP. If DCP is configured, for example, DCP is configured for the first group of carriers, the network device can send DCP normally on the first group of carriers, and in order to avoid the UE sometimes being unable to monitor DCP, the network device also sends DCI that can implement the DCP function. If this is the case, the UE can determine whether it can monitor DCP on the first group of carriers. If the UE can monitor DCP, the UE can determine the sleep or wake-up on the first group of carriers based on the monitoring results of DCP, without determining the sleep or wake-up on the first group of carriers according to the default (or protocol-specified) rules, the second indication information, or the first indication information. Alternatively, if the UE cannot monitor DCP, the UE can determine the sleep or wake-up on the first group of carriers according to the default (or protocol-specified) rules or according to the first indication information.

For other contents, such as how to implement the UE to sleep during the DRX duration, or how to implement the UE to wake up during the DRX duration, etc., please refer to the relevant introduction of the embodiment shown in Figure 5.

In the embodiment of the present application, the two DRX configuration technologies can be used in combination with the wake-up signal, and the embodiment of the present application does not need to configure DCP, but implements the function of DCP through ordinary DCI, reducing the number of DCI sizes that the UE needs to monitor, or enabling the UE to monitor more DCI sizes, and also simplifying the implementation of network equipment and UE. Moreover, the network equipment can indicate the wake-up or sleep of the UE on the carrier group through corresponding indication information. The indication method is more flexible, more in line with the service transmission requirements of the UE, and also increases the flexibility of network equipment scheduling. In addition, the embodiment of the present application also avoids the default method of requiring the UE to wake up during the second DRX duration on the second group of carriers, which can reduce the power consumption of the UE.

The embodiment shown in any of FIG. 5, FIG. 7 or FIG. 10 mainly considers the problem of combining two sets of DRX configurations with the wake-up signal. According to the above description, cross-carrier scheduling and two sets of DRX configurations are not currently used in combination. Then the fourth communication method is provided below to combine cross-carrier scheduling with two sets of DRX configurations, thereby further reducing the power consumption of the UE.

Please refer to FIG. 12 , which is a flow chart of the method.

S121. The network device sends a second DCI on a 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, and the first group of carriers includes one or more carriers configured for the UE. The first carrier is, for example, part of the carriers or all of the carriers included in the first group of carriers. For example, if the primary carrier configured by the network device for the UE belongs to the first group 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 group of carriers. For example, 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 send data on the second group of carriers, that is, the second DCI implements cross-carrier scheduling. For an introduction to concepts such as the first group of carriers and the second group of carriers, reference may be made to the embodiments shown in any one of FIG. 5 , FIG. 7 , or FIG. 10 .

S122: The UE starts or restarts a second DRX inactivity timer, and sets the duration of the second DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration.

Since the second DCI schedules data on the second group of carriers, data may be transmitted on the second group of carriers subsequently. Therefore, the DRX activation time of the UE on the second group of carriers needs to be extended to ensure that the UE can receive or send data on the second group of carriers. In addition, it can also ensure that the UE performs corresponding behaviors within the DRX activation time, such as sending a periodic uplink sounding reference signal (SRS), or reporting channel status information (CSI) through PUCCH, or reporting semi-periodic channel status information (CSI) through PUSCH, and so on.

To extend the DRX activation time of the UE on the second group of carriers, one implementation method is to start or restart the second DRX inactivity timer. For example, the UE may start or restart the second DRX inactivity timer in the first time domain symbol after the second DCI is received. Wherein, at 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, at the first time domain symbol after the second DCI is received, if the second DRX inactivity timer is in a running state, the UE restarts the second DRX inactivity timer.

The second group of carriers applies the second DRX configuration, and the second DRX configuration can configure the DRX cycle, DRX inactivity timer, and DRX retransmission timer, etc. The second DRX inactivity timer corresponds to the second group of carriers, or corresponds to the second DRX configuration. It can be understood that the DRX inactivity timer configured by the second DRX configuration is the second DRX inactivity timer. Then in S122, the UE can set the duration of the second inactivity timer to the original duration of the second DRX inactivity timer, that is, 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 group of carriers is extended, so that the UE can receive or send data on the second group of carriers.

The UE starts or restarts the second DRX inactivity timer. One implementation is that the UE starts or restarts the second DRX inactivity timer by default (or as specified by the protocol) after receiving the second DCI. This method does not require additional notification from the network device, and can save signaling overhead.

Alternatively, the UE starts or restarts the second DRX inactive timer, and another implementation method is that it is indicated by the network device. For example, the second DCI may include the second indication information, and the second indication information may indicate starting or restarting the second DRX inactive timer. If this is the case, there may be two situations. In one case, if the second DCI includes the second indication information, it indicates starting or restarting the second DRX inactive timer, and the UE starts or restarts the second DRX inactive timer; and if the second DCI does not include the second indication information, it indicates not starting or restarting the second DRX inactive timer, and the UE does not start or restart the second DRX inactive timer. In this case, the second DCI may include the second indication information or may not include the second indication information, which can save the signaling overhead of the second DCI. Alternatively, in another case, if the second indication information included in the second DCI indicates starting or restarting the second DRX inactive timer, the UE starts or restarts the second DRX inactive timer; and if the second indication information included in the second DCI indicates not starting or restarting the second DRX inactive timer, the UE does not start or restart the second DRX inactive timer. Indicating through the second DCI allows the UE to be more clear about the UE's behavior.

The second indication information may be carried through an existing field in the second DCI. For example, if there are reserved bits in the existing fields included in the second DCI, the second indication information may be carried through the reserved bits; or, one or more bits may be added to the second DCI to carry the second indication information.

S123: The UE extends the DRX activation time of the UE on the first group of carriers.

Since there is data transmission on the second group of carriers, and the second DCI is cross-carrier scheduling, the subsequent network device may also schedule the data on the second group of carriers by cross-carrier scheduling. In addition, the network device may also schedule the data on the first group of carriers on the first group of carriers. Therefore, the DRX activation time of the UE on the first group of carriers can be extended to receive the DCI for scheduling data.

If the UE wants to extend the DRX activation time of the UE on the first group of carriers, there may be different implementation methods, which are described below with examples.

1. The first method: prolonging the DRX activation time of the UE on the first group of carriers through the first DRX inactivation timer.

The first group of carriers applies the first DRX configuration, and the first DRX configuration can configure the DRX cycle, DRX inactivity timer, and DRX retransmission timer, etc. The first DRX inactivity timer corresponds to the first group of carriers, or corresponds to the first DRX configuration. It can be understood that the DRX inactivity timer configured by the first DRX configuration is the first DRX inactivity timer. Then in S123, the UE can start or restart the first DRX inactivity timer. In this way, the DRX activation time of the UE on the first group of carriers can be extended, so that the UE can receive DCI on the first group of carriers.

The UE also needs to set the duration of the first DRX inactivity timer. As an optional implementation, the UE can set the duration of the first DRX inactivity timer to the original duration of the first DRX inactivity timer, that is, the duration of the DRX inactivity timer configured by the first DRX configuration. This setting method is relatively simple and is also easy for the UE to implement.

Taking the case where the frequency of the first group of carriers belongs to FR1 and the frequency of the second group of carriers belongs to FR2 as an example, since the UE consumes more power when working in FR2, the UE may work more on the first group of carriers, and therefore, the duration of the DRX inactive timer configured by the first DRX configuration may be relatively long. If the duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the first DRX configuration, the DRX active time of the UE on the first group of carriers may be extended too long. For example, the network device may no longer schedule data of the second group of carriers, and the UE may have entered the DRX inactive time on the second group of carriers, but the UE is still in the DRX active time on the first group of carriers, which may increase the power consumption of the UE on the first group of carriers. Referring to FIG. 13, the running time of the first DRX inactive timer corresponding to FR1 is longer than the running time of the second DRX inactive timer corresponding to FR2, and after the second DRX inactive timer has stopped running, the UE is still in the DRX active time on FR1. There is a solution to this problem, and the network device may send a first signaling, and the first signaling may instruct the UE to stop the first DRX inactive timer. After receiving the first signaling, the UE may stop running the first DRX inactivity timer. The first signaling may be, for example, DCI, or may also be radio resource control (RRC) signaling, etc. However, this requires consumption of additional signaling.

In order to solve the above problem, as another optional implementation, when the UE needs to set the duration of the first DRX inactivity timer, for example, when starting the first DRX inactivity timer, or before starting the first DRX inactivity timer, 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 setting the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration, it can 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 method is adopted, the duration of the DRX activation time of the UE on the first group of carriers may be consistent with the duration of the DRX activation time of the UE on the second group of carriers, and the UE can receive DCI for scheduling data of the second group of carriers on the first group of carriers, and will not consume too much power due to the excessively long DRX activation time on the first group of carriers. 14 , the running time of the first DRX inactivity timer corresponding to FR1 is the same as the running time of the second DRX inactivity timer corresponding to FR2.

The duration of the first DRX inactive timer set by the UE may be set by default or by a protocol. Alternatively, the UE may also determine the duration of the first DRX inactive timer according to the corresponding situation. For example, if the UE receives a first DCI on the first group of carriers before starting or restarting the first DRX inactive timer, and the first DCI is used to schedule the UE to receive data or send data on the first group of carriers, then the UE may set the duration of the first DRX inactive timer to the duration of the DRX inactive timer configured by the first DRX configuration, so as to meet the UE's need to receive data or send data on the first group of carriers, and also meet the UE's need to schedule the reception of data corresponding to the first group of carriers on the first group of carriers.

Consider a problem. Before the UE starts or restarts the first DRX inactivity timer, if the first DRX inactivity timer is in a running 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, then if the UE restarts the first DRX inactivity timer, the duration of the first DRX inactivity timer will be long and short, increasing the complexity of UE processing. Therefore, as an optional implementation, the UE does not have to start or restart the first DRX inactivity timer under any circumstances, but can first determine whether it is necessary to start or restart the first DRX inactivity timer. For example, before the UE starts or restarts the first DRX inactivity timer, if the first DRX inactivity timer is in a running state, the UE can determine the size relationship between the remaining duration of the first DRX inactivity timer and the duration of the DRX inactivity timer configured by the second DRX configuration. 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; or, 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, the UE may not need to restart the first DRX inactivity timer. In this case, although the UE does not restart the first DRX inactivity timer, since the first DRX inactivity timer is in the running 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 group of carriers does not need to be extended additionally, but can already meet the demand.

Whether the UE should start the first DRX inactive timer can be determined by default or specified by the protocol. For example, the protocol stipulates that if the UE receives a DCI for scheduling data on the second group of carriers on the first group of carriers, the UE starts the first DRX inactive timer. Alternatively, whether the UE should start the first DRX inactive timer can also be configured by the network device. For example, the second DCI may include the first indication information, and the first indication information may indicate starting or restarting the first DRX inactive timer. If this is the case, there may be two situations. In one case, if the second DCI includes the first indication information, it indicates starting or restarting the first DRX inactive timer, and the UE starts or restarts the first DRX inactive timer; and if the second DCI does not include the first indication information, it indicates not starting or restarting the first DRX inactive timer, and the UE does not start or restart the first DRX inactive timer. In this case, the second DCI may include the first indication information or may not include the first indication information, which can save the signaling overhead of the second DCI. Alternatively, in another case, if the first indication information included in the second DCI indicates starting or restarting 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 not starting or restarting the first DRX inactivity timer, the UE does not start or restart the first DRX inactivity timer. Indicating through the second DCI allows the UE to more clearly understand the UE's behavior.

Optionally, if the second DCI includes the first indication information, the first indication information may indicate how to set the duration of the first DRX inactive timer in addition to indicating that the UE starts or restarts the first DRX inactive timer. For example, the first indication information may indicate that the timing duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the first DRX configuration, or indicate that the timing duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the second DRX configuration, and the UE may set the duration of the first DRX inactive timer according to the first indication information. Alternatively, the second DCI may also indicate how to set the duration of the first DRX inactive timer through other information, for example, the second DCI may also include the third indication information, and the third indication information may indicate that the timing duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the first DRX configuration, or indicate that the timing duration of the first DRX inactive timer is set to the duration of the DRX inactive timer configured by the second DRX configuration. By indicating the setting method of the duration of the first DRX inactivity timer through the corresponding indication information, the UE does not need to determine how the duration of the first DRX inactivity timer should be set by itself, thereby simplifying the implementation of the UE.

2. The second method: the UE extends the DRX activation time of the UE on the first group of carriers.

In the second mode, there is no need to use the first DRX inactive timer. Since the UE knows the end time of the second DRX inactive timer, or in other words, the UE knows the end time of the DRX activation time of the UE on the second group of carriers, the UE can extend the DRX activation time of the UE on the first group of carriers, for example, extending the end time of the DRX activation time of the UE on the first group of carriers to the same end time as the DRX activation time of the UE on the second group of carriers. If this method is adopted, the duration of the DRX activation time of the UE on the first group of carriers is consistent with the duration of the DRX activation time of the UE on the second group of carriers. The UE can receive the DCI for scheduling the data of the second group of carriers on the first group of carriers, and will not consume too much power due to the long DRX activation time on the first group of carriers. Moreover, this method does not need to use the first DRX inactive time timer, which reduces the power consumption caused by the UE maintaining the first DRX inactive time timer.

With reference to FIG15, the UE extends the DRX activation time of the UE on the first group of carriers (the dotted box in FIG15 indicates the extended time), so that the running time of the first DRX inactivation timer corresponding to FR1 is the same as the running time of the second DRX inactivation timer corresponding to FR2. It can be understood that the embodiment of the present application defines the DRX activation time on the first group of carriers (i.e., the DRX activation time of the first DRX configuration) as the union of the DRX activation time corresponding to the first DRX configuration on the first group of carriers and the DRX activation time corresponding to the second DRX configuration on the second group of carriers.

Among them, S122 and S123 can be executed simultaneously, or S122 can be executed before S123, or S122 can be executed after S123.

In the embodiment of the present application, the two DRX configuration technologies can be used in combination with the cross-carrier scheduling technology. When implementing cross-carrier scheduling, the UE can receive DCI from the network device on the first group of carriers for scheduling data on the second group of carriers, and the UE can also receive data or send data on the second group of carriers, so that the cross-carrier scheduling technology can be implemented under the background of the two DRX configuration technologies. Moreover, the embodiment of the present application can set the duration of the first DRX inactive timer corresponding to the first group of carriers to different durations according to different situations, so that the duration of the first DRX inactive timer is more in line with the current service transmission requirements and also saves more power consumption of the UE.

For example, if a UE (such as a smart phone, a smart watch or a smart bracelet, etc.) has an energy-saving requirement, the UE may send energy-saving capability information or an energy-saving indication to a network device, and the energy-saving capability information indicates that the UE supports a first solution, and the energy-saving indication is used to indicate that the UE has an energy-saving requirement, or to indicate that the UE requests to apply the first solution. Alternatively, if the UE requests to apply the first solution that can save energy, the UE may also send the energy-saving capability information or the energy-saving indication to the network device. Among them, the first solution is a solution provided by an embodiment shown in any one of Figures 5, 8, 10 or 12. After the network device receives the energy-saving capability information or the energy-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 solution. Optionally, the network device may send energy-saving permission information or configuration information related to the first solution to the UE to indicate that the UE is allowed to save energy, or to indicate that the UE is allowed to apply the first solution. After the UE receives the energy-saving permission information or the configuration information related to the first solution from the network device, it can apply the first solution. Alternatively, after the network device receives the energy-saving capability information or the energy-saving indication from the UE, if the network device has only configured the first DRX configuration for the UE, the network device may send the second DRX configuration to the UE. After the UE receives the second DRX configuration, the first solution can be applied. After applying the first solution, the UE can further reduce power consumption, that is, reduce battery power consumption, and extend the standby time of the UE.

In addition, the following three rules are introduced.

Rule 1: The duration of the first DRX activation time is greater than or equal to the duration of the second DRX activation time.

Optionally, the first group of carriers corresponds to a first DRX activation time, and the first DRX activation time includes, for example, all or part of the DRX activation time of the UE on the first group of carriers under the first DRX configuration. The second group of carriers corresponds to a second DRX activation time, and the second DRX activation time includes, for example, all or part of the DRX activation time of the UE on the second group of carriers under the second DRX configuration. Considering that the network device may schedule the UE on the first group of carriers to receive data or send data on the second group of carriers, the UE needs to receive scheduling information corresponding to the second group of carriers on the first group of carriers, and the scheduling information is carried in the DCI sent through the PDCCH, for example. Then, if the time length of the first DRX activation time is less than the time length of the second DRX activation time, a situation may occur in which the UE enters a dormant state on the first group of carriers, but the network device sends a DCI on the first group of carriers for scheduling data transmission on the second group of carriers. At this time, the UE may not be able to receive the DCI due to dormancy, resulting in the UE being unable to transmit data on the second group of carriers. In order to reduce the probability of this situation occurring, an embodiment of the present application proposes to make the time length of the first DRX activation time greater than or equal to the time length of the second DRX activation time. In addition, the first DRX activation time can also cover the second DRX activation time in the time domain, for example, the second DRX activation time is within the first DRX activation time in the time domain, or the second DRX activation time coincides with the first DRX activation time in the time domain, so that the UE can receive scheduling information from the network device on the first group of carriers.

Make the duration of the first DRX activation time greater than or equal to the duration of the second DRX activation time. For example, one implementation is to make the duration of all or part of the timers configured by the first DRX configuration greater than or equal to the duration of the corresponding timer configured by the second DRX configuration. For example, make the duration of the first DRX duration timer greater than or equal to the duration of the second DRX duration timer, the first DRX duration timer is configured by the first DRX configuration, and the second DRX duration timer is configured by the second DRX configuration. For another example, make the duration of the first DRX duration timer greater than or equal to the duration of the second DRX duration timer, and make the duration of the first DRX inactive timer greater than or equal to the duration of the second DRX inactive timer, the first DRX inactive timer is configured by the first DRX configuration, and the second DRX inactive timer is configured by the second DRX configuration. For another example, the duration of the first DRX duration timer is set to be greater than or equal to the duration of the second DRX duration timer, the duration of the first DRX inactivity timer is set to be greater than or equal to the duration of the second DRX inactivity timer, and the duration of the first DRX retransmission timer is set to be greater than or equal to the duration of the second DRX retransmission timer. The first DRX retransmission timer is configured by the first DRX configuration, and the second DRX retransmission timer is configured by the second DRX configuration.

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

Rule 2: DCI on the first group of carriers is configured to schedule data transmission on the second group of carriers, but DCI on the second group of carriers is not configured to schedule data transmission on the first group of carriers.

The frequency of the second frequency range is greater than the frequency of the first frequency range, for example, the frequency of the second group of carriers belongs to FR2, and the frequency of the first group of carriers belongs to FR1. Since the frequency of FR2 is greater than the frequency of FR1, the UE will consume more power when working on the carrier of FR2. Therefore, optionally, if cross-carrier scheduling is configured in the embodiment of the present application, the second group of carriers can be configured to be scheduled by the first group of carriers, that is, the DCI on the first group of carriers is configured to schedule the data transmission of the second group of carriers, and the DCI on the second group of carriers is not configured to schedule the data transmission of the first group of carriers. In this way, the UE only needs to monitor the DCI on the first group of carriers to complete the data transmission on the second group of carriers, and there is no need to monitor the DCI on the second group of carriers, thereby saving the power consumption of the UE. Rule 2 can be specified by a protocol, or can be defaulted, or can be configured by a network device.

Rule 3: The data transmission time on the second group of carriers scheduled on the first group of carriers is within the DRX activation time of the UE on the second group of carriers.

If cross-carrier scheduling is supported, another situation may occur. For example, if the DCI on the first group of carriers is configured to schedule data transmission on the second group of carriers, then the transmission time of the data on the second group of carriers scheduled by the DCI sent by the network device on the first group of carriers may be within the DRX inactive time of the UE on the second group of carriers. For example, referring to Figure 7, the network device sends a DCI on the carrier of FR1, and the DCI schedules data transmission on the carrier of FR2. The UE receives the DCI on the first group of carriers within the On Duration time within a DRX cycle. The data transmission time scheduled by the DCI is, for example, the T1 time in Figure 7. At T1 time, the DRX inactive timer of the UE on the second group of carriers has timed out, so T1 is within the DRX inactive time of the UE on the second group of carriers. If this is the case, the UE also needs to receive PUSCH or PDSCH during the DRX inactive time, which will bring additional power consumption to the UE. Therefore, optionally, the embodiment of the present application stipulates that the data transmission time on the second group of carriers scheduled by the network device on the first group of carriers needs to be within the DRX activation time of the UE on the second group of carriers, so that the UE does not need to receive PUSCH or PDSCH during the DRX inactive time on the second group of carriers, but can enter a dormant state to save power consumption. Rule 3 can be specified by a protocol, or can be defaulted, or can be configured by a network device.

The above three rules can be applied in combination with the embodiment shown in FIG. 5 , or can be applied in combination with the embodiment shown in FIG. 8 , or can be applied in combination with the embodiment shown in FIG. 10 , or can be applied in combination with the embodiment shown in FIG. 12 . Alternatively, the above three rules can also be applied alone, without being combined with any of the aforementioned method embodiments. In addition, when applied alone, one or more of the above rules can be applied, that is, any two or three of the above three rules can be applied in combination, or the above three rules can also be applied separately instead of being combined. For example, Rule 1 can be applied without applying Rule 2 and Rule 3; or, Rule 2 can be applied without applying Rule 1 and Rule 3; or, Rule 3 can be applied without applying Rule 1 and Rule 2; or, Rule 1 and Rule 2 can be applied without applying Rule 3; or, Rule 1 and Rule 3 can be applied without applying Rule 2; or, Rule 2 and Rule 3 can be applied without applying Rule 1; or, Rule 1, Rule 2, and Rule 3 can be applied.

The following describes the device used to implement the above method in the embodiment of the present application in conjunction with the accompanying drawings. Therefore, the above content can be used in subsequent embodiments, and the repeated content will not be repeated.

FIG16 is a schematic block diagram of a communication device 1600 provided in an embodiment of the present application. Exemplarily, the communication device 1600 is, for example, a terminal device, or a network device. Exemplarily, the communication device 1600 can implement the functions of the UE described in the embodiment shown in FIG5 , the embodiment shown in FIG8 , the embodiment shown in FIG10 , or the embodiment shown in FIG12 . Alternatively, the communication device 1600 can implement the functions of the network device described in the embodiment shown in FIG10 .

The communication device 1600 includes a transceiver unit 1620 and a processing unit 1610. Optionally, the communication device 1600 may also include a storage unit, which can communicate with the processing unit 1610, but is not shown in FIG. 16. Alternatively, the communication device 1600 may not include a storage unit, and the storage unit may also be located outside the communication device 1600. Exemplarily, the communication device 1600 may be a UE, or a chip applied to a UE, or other combined devices, components, etc. having the above-mentioned UE functions, or the communication device 1600 may be a network device, or a chip applied to a network device, or other combined devices, components, etc. having the above-mentioned network device functions. When the communication device 1600 is a UE or a network device, the processing unit 1610 may include a processor, such as a baseband processor, and the baseband processor may include one or more central processing units (CPUs); the transceiver unit 1620 may be a transceiver, and the transceiver may include an antenna and a radio frequency circuit, etc. Among them, the transceiver may include a transmitter and a receiver, and the transceiver may realize the functions of the transmitter and the receiver, or the transmitter and the receiver may also be two functional modules deployed separately, but the embodiment of the present application refers to these two functional modules as a transceiver. When the communication device 1600 is a component having the above-mentioned UE or network device functions, the transceiver unit 1620 may be a radio frequency unit, and the processing unit 1610 may be a processor, such as a baseband processor. When the communication device 1600 is a chip system, the transceiver unit 1620 may be an input and output interface of a chip (such as a baseband chip), and the processing unit 1610 may be a processor of a chip system, which may include one or more central processing units. It should be understood that the processing unit 1610 in the embodiment of the present application may be implemented by a processor or a processor-related circuit component, and the transceiver unit 1620 may be implemented by a transceiver or a transceiver-related circuit component.

In one implementation, when the communication device 1600 is used to implement the functions of the UE described in the embodiment shown in FIG. 5, the processing unit 1610 may be used to perform all operations except the transceiver operation performed by the UE in the embodiment shown in FIG. 5, such as S51 to S53, and/or other processes for supporting the technology described herein. The transceiver unit 1620 may be used to perform all the receiving operations and the sending operations performed by the UE in the embodiment shown in FIG. 5, such as the operation of monitoring the DCP, and/or other processes for supporting the technology described herein.

In one implementation, when the communication device 1600 is used to implement the functions of the UE described in the embodiment shown in FIG8, the processing unit 1610 may be used to perform all operations except the transceiver operation performed by the UE in the embodiment shown in FIG8, such as S81 to S85, and/or other processes for supporting the technology described herein. The transceiver unit 1620 may be used to perform all the receiving operations and the sending operations performed by the UE in the embodiment shown in FIG8, such as the operation of monitoring the DCP, and/or other processes for supporting the technology described herein.

In one implementation, when the communication device 1600 is used to implement the functions of the UE described in the embodiment shown in FIG. 10, the processing unit 1610 may be used to perform all operations except the transceiver operations performed by the UE in the embodiment shown in FIG. 10, such as S102 to S103, and/or other processes for supporting the technology described herein. The transceiver unit 1620 may be used to perform all the receiving operations and the sending operations performed by the UE in the embodiment shown in FIG. 10, such as S101, and/or other processes for supporting the technology described herein.

In one implementation, when the communication device 1600 is used to implement the functions of the network device described in the embodiment shown in FIG. 10, the processing unit 1610 may be used to perform all operations except the transceiver operation performed by the network device in the embodiment shown in FIG. 10, and/or to support other processes of the technology described herein. The transceiver unit 1620 may be used to perform all the receiving operations and sending operations performed by the network device in the embodiment shown in FIG. 10, such as S101, and/or to support other processes of the technology described herein.

In one implementation, when the communication device 1600 is used to implement the functions of the UE described in the embodiment shown in FIG. 12, the processing unit 1610 may be used to perform all operations except the transceiver operations performed by the UE in the embodiment shown in FIG. 12, such as S122 to S123, and/or other processes for supporting the technology described herein. The transceiver unit 1620 may be used to perform all the receiving operations and the sending operations performed by the UE in the embodiment shown in FIG. 12, such as S121, and/or other processes for supporting the technology described herein.

In addition, the transceiver unit 1620 may be a functional module that can perform both the sending operation and the receiving operation. For example, the transceiver unit 1620 may be used to perform all the sending operations and receiving 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 FIG5 , the embodiment shown in FIG8 , the embodiment shown in FIG10 , or the embodiment shown in FIG12 . For example, when performing a receiving operation, the transceiver unit 1620 may be considered to be a receiving unit, and when performing a sending operation, the transceiver unit 1620 may be considered to be a sending unit. Alternatively, the transceiver unit 1620 may be two functional modules, and the transceiver unit 1620 may be regarded as a general term for the two functional modules, which include a receiving unit and a sending unit. The sending unit is used to complete the sending operation, for example, the sending unit may be used to execute all the sending operations performed by the first terminal device or the network device in the embodiment shown in FIG. 5 , the embodiment shown in FIG. 8 , the embodiment shown in FIG. 10 , or the embodiment shown in FIG. 12 ; the receiving unit is used to complete the receiving operation, for example, the receiving unit may be used to execute all the receiving operations performed by the first terminal device or the network device in the embodiment shown in FIG. 5 , the embodiment shown in FIG. 8 , the embodiment shown in FIG. 10 , or the embodiment shown in FIG. 12 .

Regarding the specific functions that the processing unit 1610 and the transceiver unit 1620 can be specifically implemented, reference can be made to the description of the operations performed by the terminal device in the embodiment shown in FIG5 , the embodiment shown in FIG8 , the embodiment shown in FIG10 , or the embodiment shown in FIG12 , or reference can be made to the description of the operations performed by the network device (for example, an access network device or a core network device) in the embodiment shown in FIG5 , the embodiment shown in FIG8 , the embodiment shown in FIG10 , or the embodiment shown in FIG12 , and no further details will be given.

The embodiment of the present application further provides a communication device, which can be a terminal device or a circuit. The communication device can be used to execute the actions executed by the terminal device in the above-mentioned various method embodiments.

When the communication device is a terminal device, FIG17 shows a simplified schematic diagram of the structure of the terminal device. For ease of understanding and illustration, in FIG17, a mobile phone is used as an example of the terminal device. As shown in FIG17, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used to process communication protocols and communication data, as well as to control the terminal device, execute software programs, process software program data, etc. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of radio frequency signals. The antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input-output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal devices may not have input-output devices.

When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, only one memory and processor are shown in Figure 17. In an actual terminal 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 a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.

In the embodiment of the present application, the antenna and the radio frequency circuit with transceiver function can be regarded as the transceiver unit of the terminal device (the transceiver unit can be a functional unit that can realize the sending function and the receiving function; or, the transceiver unit can also include two functional units, namely, a receiving unit that can realize the receiving function and a sending unit that can realize the sending function), and the processor with processing function can be regarded as the processing unit of the terminal device. As shown in FIG17, the terminal device includes a transceiver unit 1710 and a processing unit 1720. The transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver device, etc. The processing unit can also be referred to as a processor, a processing board, a processing module, a processing device, etc. Optionally, the device used to realize the receiving function in the transceiver unit 1710 can be regarded as a receiving unit, and the device used to realize the sending function in the transceiver unit 1710 can be regarded as a sending unit, that is, the transceiver unit 1710 includes a receiving unit and a sending unit. The transceiver unit can sometimes also be referred to as a transceiver, a transceiver, or a transceiver circuit, etc. The receiving unit can sometimes also be referred to as a receiver, a receiver, or a receiving circuit, etc. The sending unit can sometimes also be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

It should be understood that the transceiver unit 1710 is used to perform sending operations and receiving operations on the terminal device side in the embodiment shown in Figure 5 or the embodiment shown in Figure 8 or the embodiment shown in Figure 10 or the embodiment shown in Figure 12, and the processing unit 1720 is used to perform other operations on the first terminal device side except for the sending and receiving operations in the embodiment shown in Figure 5 or the embodiment shown in Figure 8 or the embodiment shown in Figure 10 or the embodiment shown in Figure 12.

When the communication device is a chip-type device or circuit, the device may include a transceiver unit and a processing unit, wherein the transceiver unit may be an input/output circuit and/or a communication interface; and the processing unit may be an integrated processor or microprocessor or integrated circuit.

It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

It should be noted 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 component, the memory (storage module) is integrated in the processor.

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

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, 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 units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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 into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media may include 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 (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer. In addition, by way of example but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), or direct rambus RAM (DR RAM).

The above is only a specific implementation of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims (26)

1. A communication method, comprising: The terminal device determines whether to monitor the DCP within the first downlink control information DCP monitoring opportunity with cyclic redundancy check scrambled by using the energy-saving wireless network temporary identifier; In a case where the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, on a first group of carriers, the terminal device wakes up within a first discontinuous reception DRX duration associated with the first DCP monitoring opportunity, and, on a second group of carriers, the terminal device wakes up or sleeps within a second DRX duration associated with the first DCP monitoring opportunity, wherein the first group of carriers includes one or more carriers configured for the terminal device, the first group of carriers applies a first DRX configuration, the first DRX duration corresponds to the first DRX configuration, and the second group of carriers includes one or more carriers configured for the terminal device, the second group of carriers applies a second DRX configuration, and the second DRX duration corresponds to the second DRX configuration. 2. The method according to claim 1 is characterized in that the first DCP monitoring opportunity is configured on the first group of carriers. 3. The method according to claim 1 or 2 is characterized in that the first DRX duration is located after the first DCP monitoring opportunity in the time domain. 4. The method according to claim 1 or 2, characterized in that the terminal device determines whether to monitor the DCP within the first DCP monitoring opportunity, comprising: In a case where the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, in a case where the time domain position of the first DCP monitoring opportunity is not within or partially within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein the first DRX activation time is the DRX activation time corresponding to the first DRX configuration; or, In a case where the maximum number of sizes of downlink control information DCI that can be monitored is greater than or equal to the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines to monitor DCP within the first DCP monitoring opportunity; or, in a case where the maximum number of sizes of DCI that can be monitored is less than the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines not to monitor DCP within the first DCP monitoring opportunity; or, When the time domain position of the first DCP monitoring opportunity is within the first DRX activation time and the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time and the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; wherein, the first DRX activation time is the DRX activation time corresponding to the first DRX configuration. 5. The method according to claim 1 or 2, characterized in that the method further comprises: The terminal device receives configuration information from a network device, where the configuration information is used to configure: when the terminal device does not listen during a DCP listening opportunity, the terminal device wakes up or sleeps during the second DRX duration associated with the DCP listening opportunity. 6. The method according to claim 1 or 2, characterized in that the method further comprises: In a case where the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, the terminal device monitors the DCP within the first DCP monitoring opportunity; The terminal device sleeps or wakes up on the first group of carriers during the first DRX duration, and sleeps or wakes up on the second group of carriers during the second DRX duration, according to the monitoring status of the DCP. 7. The method according to claim 6, wherein the terminal device sleeps on the first group of carriers for the first DRX duration and sleeps on the second group of carriers for the second DRX duration according to the monitoring status of the DCP, comprising: In a case where the terminal device receives a first DCP from a network device during the first DCP listening opportunity, and the first DCP indicates sleep, the terminal device sleeps during the first DRX duration on the first group of carriers, and sleeps during the second DRX duration on the second group of carriers; or In a case where the terminal device does not receive the DCP from the network device during the first DCP listening opportunity, the terminal device sleeps during the first DRX duration on the first group of carriers, and sleeps during the second DRX duration on the second group of carriers. 8. The method according to claim 6, wherein the terminal device wakes up on the first group of carriers within the first DRX duration according to the monitoring of the DCP, and wakes up on the second group of carriers within the second DRX duration, comprising: In a case where the terminal device receives a first DCP from a network device during the first DCP listening opportunity and the first DCP indicates wake-up, the terminal device wakes up during the first DRX duration on the first group of carriers, and wakes up during the second DRX duration on the second group of carriers; or In a case where the terminal device receives a first DCP from a network device during the first DCP listening opportunity, the terminal device wakes up during the first DRX duration on the first group of carriers, and wakes up during the second DRX duration on the second group of carriers. 9. The method according to claim 6, wherein the terminal device sleeps or wakes up on the first group of carriers during the first DRX duration, and sleeps or wakes up on the second group of carriers during the second DRX duration according to the monitoring of the DCP, comprising: The terminal device receives a first DCP from a network device during the first DCP listening opportunity, and the first DCP includes first indication information and second indication information; wherein, In a case where the first indication information indicates wake-up, and the second indication information indicates wake-up, on the first group of carriers, the terminal device wakes up within the first DRX duration, and, on the second group of carriers, the terminal device wakes up within the second DRX duration; or, In the case where the first indication information indicates sleep, and the second indication information indicates sleep, on the first group of carriers, the terminal device sleeps during the first DRX duration, and, on the second group of carriers, the terminal device sleeps during the second DRX duration; or, In a case where the first indication information indicates wake-up, and the second indication information indicates sleep, on the first group of carriers, the terminal device wakes up within the first DRX duration, and, on the second group of carriers, the terminal device sleeps within the second DRX duration; or, In a case where the first indication information indicates sleep, and the second indication information indicates wake-up, on the first group of carriers, the terminal device sleeps during the first DRX duration, and, on the second group of carriers, the terminal device wakes up during the second DRX duration. 10. The method according to claim 6, characterized in that, on the first group of carriers, the terminal device sleeps within the first DRX duration, comprising: The terminal device does not start or restart a first DRX duration timer at the start time of the first DRX duration, and the first DRX duration timer corresponds to the first DRX configuration. 11. The method according to claim 6, characterized in that, on the first group of carriers, the terminal device wakes up within the first DRX duration, comprising: The terminal device starts or restarts a first DRX duration timer at the start time of the first DRX duration, and the first DRX duration timer corresponds to the first DRX configuration. 12. The method according to claim 6, wherein, on the second group of carriers, the terminal device sleeps within the second DRX duration, comprising: The terminal device does not start or restart the second DRX duration timer at the start time of the second DRX duration, and the second DRX duration timer corresponds to the second DRX configuration. 13. The method according to claim 6, characterized in that, on the second group of carriers, the terminal device wakes up within the second DRX duration, comprising: The terminal device starts or restarts a second DRX duration timer at the start time of the second DRX duration, and the second DRX duration timer corresponds to the second DRX configuration. 14. The method according to any one of claims 1, 2, 7 to 13, characterized in that: The frequency range to which the first group of carriers belongs is different from the frequency range to which the second group 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. 15. A communication method, comprising: In a case where the terminal device determines not to monitor the DCP within a first downlink control information DCP monitoring opportunity with cyclic redundancy check encrypted using an energy-saving wireless network temporary identifier, the terminal device determines whether to monitor the DCP within a second DCP monitoring opportunity, the first DCP monitoring opportunity is configured on a first group of carriers, the second DCP monitoring opportunity is configured on a second group of carriers, the first group of carriers includes one or more carriers configured for the terminal device, the first group of carriers applies a first discontinuous reception DRX configuration, the second group of carriers includes one or more carriers configured for the terminal device, and the second group of carriers applies a second DRX configuration; In a case where the terminal device determines to monitor the DCP within the second DCP monitoring opportunity, the terminal device monitors the DCP within the second DCP monitoring opportunity, and according to the monitoring situation of the DCP, sleeps or wakes up within the second DRX duration associated with the second DCP monitoring opportunity on the second group of carriers, and the second DRX duration corresponds to the second DRX configuration. 16. The method according to claim 15, characterized in that the method further comprises: The terminal device determines whether to monitor the DCP during the first DCP monitoring opportunity. 17. The method according to claim 15 or 16, characterized in that the method further comprises: In a case where the terminal device determines not to monitor the DCP during the second DCP monitoring opportunity, the terminal device wakes up during 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 a case where the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, the terminal device sleeps or wakes up within a first DRX duration associated with the first DCP monitoring opportunity on the first group of carriers according to the monitoring situation of the DCP, and sleeps or wakes up within the second DRX duration on the second group of carriers, where 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 a case where the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, the terminal device does not monitor the DCP within the second DCP monitoring opportunity on the second group of carriers. 20. The method according to claim 15 or 16, characterized in that the method further comprises: In a case where the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, on the first group of carriers, the terminal device wakes up within a first DRX duration associated with the first DCP monitoring opportunity, and the first DRX duration corresponds to the first DRX configuration. 21. The method according to claim 16, wherein the terminal device determines whether to monitor the DCP within the first DCP monitoring opportunity, comprising: In a case where the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, in a case where the time domain position of the first DCP monitoring opportunity is not within or partially within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein the first DRX activation time is the DRX activation time corresponding to the first DRX configuration; or, In a case where the maximum number of sizes of downlink control information DCI that can be monitored is greater than or equal to the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines to monitor DCP within the first DCP monitoring opportunity; or, in a case where the maximum number of sizes of DCI that can be monitored is less than the number of sizes of DCI that the terminal device needs to monitor, the terminal device determines not to monitor DCP within the first DCP monitoring opportunity; or, When the time domain position of the first DCP monitoring opportunity is within the first DRX activation time and the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time and the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; wherein the first DRX activation time is the DRX activation time corresponding to the first DRX configuration. 22. The method according to any one of claims 15, 16 and 21, characterized in that the terminal device determines whether to monitor the DCP in the second DCP monitoring opportunity, comprising: In a case where the time domain position of the second DCP monitoring opportunity is within the second DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, in a case where the time domain position of the second DCP monitoring opportunity is not within or partially within the second DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein the second DRX activation time is the DRX activation time corresponding to the second DRX configuration; or, In a case where the maximum number of sizes of DCIs that can be monitored is greater than or equal to the number of sizes of DCIs that the terminal device needs to monitor, the terminal device determines to monitor the DCP during the second DCP monitoring opportunity; or, in a case where the maximum number of sizes of DCIs that can be monitored is less than the number of sizes of DCIs that the terminal device needs to monitor, the terminal device determines not to monitor the DCP during the second DCP monitoring opportunity; or, When the time domain position of the second DCP monitoring opportunity is within the second DRX activation time and the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the second DCP monitoring opportunity; or, when the time domain position of the second DCP monitoring opportunity is within the second DRX activation time and the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor the DCP within the second DCP monitoring opportunity. 23. The method according to any one of claims 15, 16, and 21, wherein the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity and determines to monitor the DCP in the second DCP monitoring opportunity, comprising: When the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, and the time domain position of the second DCP monitoring opportunity is not within or partially within the second DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity, and determines to monitor the DCP within the second DCP monitoring opportunity. 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, and the one or more computer programs include instructions, which, when executed by one or more processors of the terminal device, cause the terminal device to execute the method as described in any one of claims 1 to 14, or cause the terminal device to execute the method as described in any one of claims 15 to 23. 25. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program, and when the computer program is run on a computer, the computer executes the method as described in any one of claims 1 to 14, or the computer executes the method as described in any one of claims 15 to 23. 26. A chip, characterized in that it comprises one or more processors and a communication interface, wherein the one or more processors are used to read instructions to execute the method as claimed in any one of claims 1 to 14, or to execute the method as claimed in any one of claims 15 to 23.