Methods and communication devices for stopping monitoring of the physical downlink control channel

Abstract

This application provides a method and communication apparatus for stopping monitoring the Physical Downlink Control Channel (PDCCH). When a network device is simultaneously configured with a skip PDCCH monitoring mechanism and a BWP handover mechanism, the time for stopping PDCCH monitoring can be determined, reducing the power consumption of the terminal device. The method includes: the network device sending a first DCI to the terminal device on an activated DL BWP; the terminal device running a timer for BWP handover; the terminal device stopping PDCCH monitoring for a first duration based on the first DCI and pausing the timer's operation; after the first duration, the terminal device resuming the timer's operation; when the timer expires, the terminal device performing a DL BWP handover; the network device running the timer, pausing its operation for a first duration, and resuming its operation after the first duration; when the timer expires, the network device performing a DL BWP handover.

Description

[0001] This application claims priority to Chinese Patent Application No. 202111164061.8, filed on September 30, 2021, entitled “Method and Communication Apparatus for Stopping Monitoring of Physical Downlink Control Channel”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a method and communication apparatus for stopping the monitoring of the physical downlink control channel. Background Technology

[0003] The physical downlink control channel (PDCCH) can be used to carry scheduling information for uplink or downlink data. Terminal devices can periodically listen to the PDCCH to obtain scheduling information. When scheduling information is detected on the PDCCH, the terminal device can receive downlink data via the physical downlink shared channel (PDSCH) or send uplink data via the physical uplink shared channel (PUSCH) according to the scheduling information. However, when there is no service transmission between the network device and the terminal device, the network device will not send the PDCCH to the terminal device. The terminal device still periodically listens to the PDCCH, which leads to wasted power consumption.

[0004] Currently, within an active downlink bandwidth part (BWP), network devices can reduce PDCCH monitoring by skipping the PDCCH monitoring mechanism or using the search space setgroup (SSSG) handover mechanism, thereby reducing the power consumption of terminal devices. For each cell, network devices can configure multiple downlink BWPs and / or multiple uplink BWPs for terminal devices, and the network devices can dynamically switch between active BWPs.

[0005] However, when a terminal device supports both the skip PDCCH listening mechanism and the BWP switching mechanism, there is no clear definition on how the terminal device should stop listening to the PDCCH. Summary of the Invention

[0006] This application provides a method and communication apparatus for stopping monitoring the Physical Downlink Control Channel (PDCCH). When the terminal device simultaneously supports the skip PDCCH monitoring mechanism and the BWP handover mechanism, the time for stopping PDCCH monitoring can be determined, which helps to reduce the power consumption of the terminal device.

[0007] In a first aspect, this application provides a method for stopping listening to the Physical Downlink Control Channel (PDCCH). The method includes: a terminal device receiving first downlink control information (DCI) from a network device on an active downlink (DL) BWP, the first DCI instructing the terminal device to stop listening to the PDCCH within a first duration, the PDCCH to be stopped including PDCCH in the Type 3 common search space set and PDCCH in the terminal device's dedicated search space set; the terminal device running a timer for BWP handover, wherein the timer expires before the end of the first duration; the terminal device stopping listening to the PDCCH within the first duration and before the timer expires; when the timer expires, the terminal device performing a DL BWP handover and listening to the PDCCH on the DL BWP after the handover.

[0008] The first DCI can be carried in the PDCCH. The terminal device can detect the first DCI in the PDCCH and stop listening to the PDCCH for a first duration based on the first DCI. After the first duration, the terminal device can continue listening to the PDCCH. The PDCCH that is stopped from being listened to includes PDCCH in the type 3 common search space set and PDCCH in the terminal device-specific search space set. For other types of common search space sets, such as type 0, type 0A, type 1, and type 2 common search space sets, the UE can skip or not skip the PDCCH listening of DCIs scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI. The embodiments of this disclosure are not limited. For type 0, type 0A, type 1, and type 2 common search space sets, whether the UE listens to SI-RNTI, RA-RNTI, TC-RNTI, or P-RNTI is not limited in the embodiments of this disclosure.

[0009] If the terminal device is also configured with the C-DRX mechanism, the first DCI can be used to instruct the terminal device to stop listening to the PDCCH for a first duration during the C-DRX activation period. During the C-DRX activation period, the terminal device stops listening to the PDCCH for the first duration, and after the first duration, the terminal device can continue listening to the PDCCH during the activation period.

[0010] The unit of the first duration can be seconds, milliseconds, frames, subframes, time slots, PDCCH listening periods, the number of PDCCH listening opportunities, a set of time slots consisting of several consecutive time slots, etc., which are not limited in this disclosure. For example, the first duration can be 8 time slots, and the terminal device can stop listening to the PDCCH within 8 time slots.

[0011] The start time of the first duration can be the beginning of the time slot where the first DCI is located, or the beginning of the next time slot of the first DCI, or the beginning of the next symbol after the end symbol of the first DCI. This application does not limit the time slot.

[0012] Optionally, the length of the first duration can be configured by RRC or indicated by the first DCI. The specific RRC configuration or DCI indication method is not limited in this embodiment.

[0013] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH for a first duration, and indicates the length of the first duration.

[0014] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The network device also sends an RRC signaling message to the terminal device on the activated DL BWP. The RRC signaling message is used to indicate the length of the first duration.

[0015] Optionally, the length of the first duration can be predefined by the protocol.

[0016] The timer duration can be configured by the network device via RRC signaling or predefined by the protocol. The timer duration unit can be seconds, milliseconds, frames, subframes, time slots, etc., and this application embodiment does not limit this. For example, the timer duration can be 3 milliseconds.

[0017] When the conditions for starting or restarting the timer are met (e.g., scheduling information is included in the first DCI), the terminal device starts or restarts the timer and runs it, i.e., decrements by each subframe or each half-subframe. After the timer expires, the terminal device performs a DL BWP handover. If the conditions for restarting the timer are met before the timer expires, the timer restarts, i.e., it resumes operation.

[0018] The timer expires before the end of the first duration, for example, the first duration is longer than the timer's expiration duration. For instance, the first duration can be 8 time slots, and the timer's duration can be 3 milliseconds, or 6 time slots.

[0019] The specific time position for starting or restarting the timer can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application embodiment does not limit this.

[0020] The first duration ends after the timer's expiration time. When the timer expires, the period for stopping PDCCH listening does not end, but the terminal device can still listen to PDCCH on the switched-in DL BWP. The switched-in DL BWP is the newly activated DL BWP. The switched-in DL BWP can also be called the default DL BWP.

[0021] The method for stopping PDCCH listening provided in this application embodiment involves a network device instructing a terminal device to stop listening to PDCCH within a first duration and configuring a timer for switching BWPs. The terminal device can simultaneously run the timer and start stopping PDCCH listening. Within the first duration, and before the timer expires, it stops listening to PDCCH and listens to PDCCH on the switched BWP. This method can run the timer and start stopping PDCCH listening simultaneously without changing the timer's running time, thus having minimal impact on the protocol and being simple to implement.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the terminal device runs a timer, including: when the terminal device receives indication information from the network device on the activated DL BWP, the terminal device starts or restarts the timer; wherein the indication information is used to schedule the terminal device to transmit PDSCH or PUSCH, or the indication information is used to instruct the terminal device to perform DL BWP switching, and the indication information is carried in the first DCI or other DCIs different from the first DCI.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the length of the first duration is configured by the RRC or indicated by the first DCI.

[0024] In conjunction with the first aspect, in certain implementations of the first aspect, the terminal device determines the start time of the first duration based on at least one of the following: the time offset between the start time of the first duration and the first DCI; the minimum time slot offset being the minimum time slot offset between the PDCCH carrying the first DCI and the PDSCH that the first DCI is allowed to schedule; the first DCI scheduling the PDSCH after the hybrid automatic repeat request (HARQ) corresponding to the PDSCH is fed back; or, the first DCI scheduling the PUSCH after the PUSCH is transmitted.

[0025] The method for stopping PDCCH listening provided in this application embodiment can be determined based on at least one of the following: the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum timeslot offset and the duration of parsing the second DCI; or the second DCI scheduling PDSCH and the HARQ feedback corresponding to the PDSCH. It does not require consideration of whether there is overlap between the first duration and the BWP handover delay, which can reduce the processing complexity of the terminal device.

[0026] Secondly, this application provides a method for stopping listening to the Physical Downlink Control Channel (PDCCH). The method includes: a terminal device receiving a first downlink control information (DCI) from a network device on an active downlink bandwidth portion (BWP). The first DCI instructs the terminal device to stop listening to the PDCCH for a first duration. The PDCCH to be stopped includes PDCCHs in the Type 3 common search space set and PDCCHs in the terminal device's dedicated search space set. The terminal device runs a timer for BWP handover. Based on the first DCI, the terminal device stops listening to the PDCCH for the first duration and suspends the timer. After the first duration, the terminal device continues to run the timer. When the timer expires, the terminal device performs a DL BWP handover.

[0027] The start time of the first duration can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application embodiment does not limit this.

[0028] Optionally, the length of the first duration can be configured by RRC or indicated by the first DCI. The specific RRC configuration or DCI indication method is not limited in this embodiment.

[0029] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH for a first duration, and indicates the length of the first duration.

[0030] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The network device also sends an RRC signaling message to the terminal device on the activated DL BWP. The RRC signaling message is used to indicate the length of the first duration.

[0031] Optionally, the length of the first duration can be predefined by the protocol.

[0032] The timer duration can be configured by the network device via RRC signaling or predefined by the protocol. The timer duration unit can be seconds, milliseconds, frames, subframes, time slots, etc., and this application embodiment does not limit this. For example, the timer duration can be 3 milliseconds.

[0033] When the conditions for starting or restarting the timer are met (e.g., scheduling information is included in the first DCI), the terminal device starts or restarts the timer and runs it, i.e., decrements by each subframe or each half-subframe. After the timer expires, the terminal device performs a DL BWP handover. If the conditions for restarting the timer are met before the timer expires, the timer restarts, i.e., it resumes operation.

[0034] The specific time position for starting or restarting the timer can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application embodiment does not limit this.

[0035] The terminal device pauses the timer during the period when it stops listening to the PDCCH. That is, during the period when it stops listening to the PDCCH, the timer pauses in increments of each subframe or half-frame.

[0036] After the terminal device performs a DL BWP switch, it can listen to the PDCCH on the switched DL BWP.

[0037] The method for stopping PDCCH listening provided in this application embodiment involves a network device instructing a terminal device to stop listening to the PDCCH within a first duration and configuring a timer for switching BWPs. The terminal device pauses the timer's operation while stopping PDCCH listening, and resumes operation after the first duration. This means that stopping PDCCH listening and running the timer occur at different times, avoiding the problem of timer expiration due to stopping PDCCH listening. Furthermore, the fact that the terminal device can stop listening to the PDCCH within the first duration reduces its power consumption.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, the terminal device runs a timer, including: when the terminal device receives indication information from the network device on the activated DL BWP, the terminal device starts or restarts the timer; wherein the indication information is used to schedule the terminal device to transmit PDSCH or PUSCH, or the indication information is used to instruct the terminal device to perform DL BWP switching, and the indication information is carried in the first DCI or other DCIs different from the first DCI.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the first DCI.

[0040] In conjunction with the second aspect, in certain implementations of the second aspect, the terminal device determines the start time of the first duration based on at least one of the following information: the time offset between the start time of the first duration and the first DCI; the minimum time slot offset is the minimum time slot offset between the PDCCH carrying the first DCI and the PDSCH that the first DCI is allowed to schedule, based on the maximum value between the minimum time slot offset and the duration of parsing the first DCI; the first DCI schedules the PDSCH, after the HARQ feedback corresponding to the PDSCH; or, the first DCI schedules the PUSCH, after the PUSCH transmission.

[0041] The method for stopping PDCCH listening provided in this application embodiment can be determined based on at least one of the following: the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum timeslot offset and the duration of parsing the second DCI; or the second DCI scheduling PDSCH and the HARQ feedback corresponding to the PDSCH. It does not require consideration of whether there is overlap between the first duration and the BWP handover delay, which can reduce the processing complexity of the terminal device.

[0042] Thirdly, this application provides a method for stopping listening to the Physical Downlink Control Channel (PDCCH). The method includes: a terminal device receiving a second DCI from a network device on an active DL BWP. The second DCI is used to indicate DL BWP handover and to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes PDCCHs in the Type 3 common search space set and PDCCHs in the terminal device's dedicated search space set. The second DCI is used to schedule the transmission of the PDSCH. Based on the second DCI, the terminal device performs a DL BWP handover and stops listening to the PDCCH on the handed-over DL BWP. The start time of the first duration is determined according to at least one of the following: the next time slot after the BWP handover delay; the time slot in which the PDSCH is transmitted on the handed-over DL BWP; and the time slot in which the PDSCH is transmitted on the handed-over DL BWP. The next time slot in the time slot where the PDSCH is transmitted on the BWP; the time offset between the start time of the first duration and the second DCI; based on the maximum value between the minimum time slot offset and the duration of parsing the second DCI, the minimum time slot offset is the minimum time slot offset between the PDCCH carrying the second DCI and the PDSCH that the second DCI is allowed to schedule; or, the second DCI schedules the PDSCH, and the HARQ corresponding to the PDSCH is fed back.

[0043] The second DCI can be carried in the PDCCH. The terminal device can detect the second DCI in the PDCCH on the active DL BWP, and based on the second DCI, stop listening to the PDCCH within a first duration and perform a DL BWP handover. The PDCCH that is stopped from listening includes PDCCH in the type 3 common search space set and PDCCH in the terminal device's dedicated search space set.

[0044] The BWP indication field in the second DCI indicates the DL BWP switch and instructs the device to stop listening to the PDCCH within a first duration, while simultaneously scheduling the transmission of the PDSCH. Specifically, the second DCI may carry PDSCH scheduling information, and the BWP indication field in the second DCI indicates the ID of the DL BWP, which is different from the ID of the currently active DL BWP. The terminal device switches to the DL BWP indicated in the second DCI indication field based on the second DCI.

[0045] The start time of the first duration can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application does not limit the time slot.

[0046] Optionally, the length of the first duration can be configured by RRC or indicated by the first DCI. The specific RRC configuration or DCI indication method is not limited in this embodiment.

[0047] For example, the network device sends a second DCI to the terminal device on the activated DL BWP. The second DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration, and indicates the length of the first duration.

[0048] For example, the network device sends a second DCI to the terminal device on the activated DL BWP. The second DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The network device also sends RRC signaling to the terminal device on the activated DL BWP. The RRC signaling is used to indicate the length of the first duration.

[0049] Optionally, the length of the first duration can be predefined by the protocol.

[0050] The start time of the first duration can be the next time slot after the BWP handover delay, the time slot in which the PDSCH is transmitted on the switched DLBWP, or the time slot following the time slot in which the PDSCH is transmitted on the switched DLBWP.

[0051] The start time of the first duration can be determined based on at least one of the following: the time offset between the start time of the first duration and the second DCI, the maximum value between the minimum time slot offset and the duration of parsing the second DCI, or the second DCI scheduling PDSCH and the HARQ feedback corresponding to the PDSCH.

[0052] The method for stopping PDCCH listening provided in this application embodiment starts at the next time slot after the BWP handover delay. The PDSCH is transmitted on the DL BWP in the time slot following the handover, or on the DLBWP in the time slot following the handover. This ensures that the first duration does not overlap with the BWP handover delay, allowing the terminal device to stop listening to PDCCH for a longer period and reducing power consumption. Furthermore, the time offset between the start time of the first duration and the second DCI can be determined based on at least one of the following: the time offset between the start time of the first duration and the second DCI, the maximum value between the minimum time slot offset and the duration of parsing the second DCI, or the second DCI scheduling PDSCH and the feedback from the corresponding hybrid automatic repeat request (HARQ). This eliminates the need to consider whether there is overlap between the first duration and the BWP handover delay, reducing the processing complexity of the terminal device.

[0053] In conjunction with the third aspect, in some implementations of the third aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the second DCI.

[0054] In conjunction with the third aspect, in some implementations of the third aspect, the second DCI is also used to instruct the terminal device to switch to the first search space set, which is the search space set on the switched DL BWP; the method further includes: the terminal device switching to the first search space set on the switched DL BWP.

[0055] In conjunction with the third aspect, in some implementations of the third aspect, the time when the terminal device switches to the first search space set on the switched DL BWP is: the next time slot or the next symbol after the first duration, or the same time slot or symbol as the start time of the first duration.

[0056] In conjunction with the third aspect, in some implementations of the third aspect, the time when the terminal device switches to the first search space set on the switched DL BWP is determined based on at least one of the following information, and is different from the start time of the first duration: the next time slot after the BWP handover delay; the time slot in which the PDSCH is transmitted on the switched DL BWP; the next time slot in which the PDSCH is transmitted on the switched DL BWP; the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or, after the second DCI schedules the PDSCH and the HARQ corresponding to the PDSCH is fed back.

[0057] Fourthly, this application provides a method for stopping listening to the Physical Downlink Control Channel (PDCCH). The method includes: a network device sending a first downlink control information (DCI) to a terminal device on the activated downlink bandwidth portion (BWP). The first DCI instructs the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes PDCCHs in the Type 3 common search space set and PDCCHs in the terminal device's dedicated search space set. The network device runs a timer for BWP handover. The network device suspends the timer's operation within the first duration. After the first duration, the network device resumes running the timer. When the timer expires, the network device performs a DL BWP handover.

[0058] The method for stopping PDCCH listening provided in this application embodiment involves a network device instructing a terminal device to stop listening to PDCCH within a first duration and configuring a timer for switching BWPs. While stopping PDCCH listening, the network device pauses the timer and resumes running the timer after the first duration. That is, stopping PDCCH listening and running the timer are done in different time periods, avoiding the problem that stopping PDCCH listening can cause the timer to expire easily.

[0059] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the first DCI.

[0060] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the network device determines the start time of the first duration based on at least one of the following: the time offset between the start time of the first duration and the first DCI; the first DCI schedules PDSCH after the Hybrid Automatic Repeat Request (HARQ) corresponding to the PDSCH is fed back; or, the first DCI schedules PUSCH after the PUSCH is transmitted.

[0061] Fifthly, this application provides a method for stopping listening to the Physical Downlink Control Channel (PDCCH). The method includes: a network device sending a second downlink control information (DCI) to a terminal device on the active downlink bandwidth portion (BWP). The second DCI is used to instruct the DL BWP to switch over and the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes PDCCHs in the Type 3 common search space set and PDCCHs in the terminal device's dedicated search space set. The second DCI is used to schedule the transmission of the Physical Downlink Shared Channel (PDSCH). The network device performs a DL BWP switch based on the second DCI. The start time of the first duration is determined based on at least one of the following: the next time slot after the BWP switchover delay; the time slot in which the PDSCH is transmitted on the switched DL BWP; and the time slot in which the PDSCH is transmitted on the switched DL BWP. The next time slot in the time slot where the PDSCH is transmitted on the BWP; the time offset between the start time of the first duration and the second DCI; based on the maximum value between the minimum time slot offset and the duration of parsing the second DCI, the minimum time slot offset is the minimum time slot offset between the PDCCH carrying the second DCI and the PDSCH that the second DCI is allowed to schedule; or, the second DCI schedules the PDSCH, and the corresponding HARQ for the PDSCH is fed back.

[0062] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the second DCI.

[0063] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the second DCI is also used to instruct the terminal device to switch to the first search space set, which is the search space set on the switched DL BWP; the above method also includes: the network device switching to the first search space set on the switched DL BWP.

[0064] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the time when the network device switches to the first search space set on the DL BWP after the handover is: the next time slot or the next symbol after the first duration, or the same time slot or symbol as the start time of the first duration.

[0065] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the time when the network-end device switches to the first search space set on the switched DL BWP is determined based on at least one of the following information, and is different from the start time of the first duration: the next time slot after the BWP handover delay; the time slot in which the PDSCH is transmitted on the switched DL BWP; the next time slot in which the PDSCH is transmitted on the switched DL BWP; the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or, after the second DCI schedules the PDSCH and the HARQ corresponding to the PDSCH is fed back.

[0066] Sixthly, this application provides a communication apparatus, comprising: a transceiver unit configured to receive first downlink control information (DCI) from a network device on an activated downlink bandwidth portion (BWP), the first DCI instructing the apparatus to stop listening to PDCCH within a first duration, the PDCCH to be stopped including PDCCH in a type 3 common search space set and PDCCH in a device-specific search space set; a processing unit configured to run a timer for BWP handover, wherein the timer expires before the end of the first duration; to stop listening to PDCCH within the first duration and before the timer expires; and to perform a DL BWP handover when the timer expires, and to listen to PDCCH on the DL BWP after the handover.

[0067] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the processing unit is further configured to: when receiving indication information from a network device on an activated DLBWP, start or restart a timer; wherein the indication information is used to schedule the device to perform transmission of a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), or the indication information is used to instruct the device to perform DLBWP switching, and the indication information is carried in a first DCI or another DCI different from the first DCI.

[0068] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the first DCI.

[0069] In conjunction with the sixth aspect, in certain implementations of the sixth aspect, the apparatus determines the start time of the first duration based on at least one of the following: the time offset between the start time of the first duration and the first DCI; the minimum time slot offset being the minimum time slot offset between the PDCCH carrying the first DCI and the PDSCH that the first DCI is allowed to schedule; the first DCI scheduling the PDSCH after the HARQ feedback corresponding to the PDSCH; or, the first DCI scheduling the PUSCH after the PUSCH transmission.

[0070] In a seventh aspect, this application provides a communication apparatus, comprising: a transceiver unit configured to receive first downlink control information (DCI) from a network device on an activated downlink bandwidth portion (BWP), the first DCI instructing the apparatus to stop listening to PDCCH for a first duration, the PDCCH to be stopped including PDCCH in the type 3 common search space set and PDCCH in the device-specific search space set; a processing unit configured to run a timer for BWP handover; based on the first DCI, stop listening to PDCCH for the first duration and pause the timer's operation; after the first duration, continue running the timer; and when the timer expires, perform a DL BWP handover.

[0071] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the processing unit is further configured to: when receiving indication information from a network device on an activated DLBWP, start or restart a timer; wherein the indication information is used to schedule the device to perform transmission of a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), or the indication information is used to instruct the device to perform DLBWP switching, and the indication information is carried in a first DCI or another DCI different from the first DCI.

[0072] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the first DCI.

[0073] In conjunction with the seventh aspect, in certain implementations of the seventh aspect, the apparatus determines the start time of the first duration based on at least one of the following: the time offset between the start time of the first duration and the first DCI; the minimum time slot offset being the minimum time slot offset between the PDCCH carrying the first DCI and the PDSCH that the first DCI is allowed to schedule, based on the maximum value between the minimum time slot offset and the duration of parsing the first DCI; the first DCI scheduling the PDSCH after the HARQ feedback corresponding to the PDSCH; or, the first DCI scheduling the PUSCH after the PUSCH transmission.

[0074] Eighthly, this application provides a communication apparatus, comprising: a transceiver unit, configured to receive second downlink control information (DCI) from a network device on an activated downlink bandwidth portion (BWP), the second DCI being configured to instruct DL BWP handover and to stop listening to PDCCH within a first duration, the PDCCH to be stopped including PDCCH in a type 3 common search space set and PDCCH in a device-specific search space set, the second DCI being configured to schedule the transmission of physical downlink shared channel (PDSCH); and a processing unit, configured to perform DL BWP handover based on the second DCI and stop listening to PDCCH on the DL BWP after handover, the start time of the first duration being determined according to at least one of the following: the next time slot after the BWP handover delay; the time slot in which the PDSCH is transmitted on the DL BWP after handover; and the time slot in which the PDSCH is transmitted on the DL BWP after handover. The next time slot in the time slot where the PDSCH is transmitted on the BWP; the time offset between the start time of the first duration and the second DCI; based on the maximum value between the minimum time slot offset and the duration of parsing the second DCI, the minimum time slot offset is the minimum time slot offset between the PDCCH carrying the second DCI and the PDSCH that the second DCI is allowed to schedule; or, the second DCI schedules the PDSCH, and the corresponding HARQ for the PDSCH is fed back.

[0075] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the first DCI.

[0076] In conjunction with aspect eight, in some implementations of aspect eight, the second DCI is also used to instruct the terminal device to switch to the first search space set, the first search space set being the search space set on the switched DL BWP; the method further includes: the terminal device switching to the first search space set on the switched DL BWP.

[0077] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the time when the terminal device switches to the first search space set on the switched DL BWP is: the next time slot or the next symbol after the first duration, or the same time slot or symbol as the start time of the first duration.

[0078] In conjunction with aspect eight, in some implementations of aspect eight, the time when the terminal device switches to the first search space set on the DL BWP after the handover is determined based on at least one of the following information, and is different from the start time of the first duration: the next time slot after the BWP handover delay; the time slot in which the PDSCH is transmitted on the DL BWP after the handover; the next time slot in which the PDSCH is transmitted on the DL BWP after the handover; the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or, after the second DCI schedules the PDSCH and the HARQ corresponding to the PDSCH is fed back.

[0079] Ninthly, this application provides a communication apparatus, comprising: a transceiver unit configured to send a first downlink control information (DCI) to a terminal device on an activated downlink bandwidth portion (BWP), the first DCI being configured to instruct the terminal device to stop listening to a PDCCH within a first duration, the PDCCH to be stopped including PDCCHs in the type 3 common search space set and PDCCHs in the terminal device's dedicated search space set; a processing unit configured to run a timer for BWP handover; suspend the timer's operation within the first duration; and resume the timer's operation after the first duration; the processing unit is further configured to perform a DL BWP handover when the timer expires.

[0080] In conjunction with the ninth aspect, in some implementations of the ninth aspect, the length of the first duration is configured by the Radio Resource Control (RRC) or indicated by the first DCI.

[0081] In conjunction with aspect nine, in certain implementations of aspect eight, the network device determines the start time of the first duration based on at least one of the following: the time offset between the start time of the first duration and the first DCI; after the first DCI schedules PDSCH and the corresponding Hybrid Automatic Repeat Request (HARQ) is fed back; or, after the first DCI schedules PUSCH and PUSCH is transmitted.

[0082] Tenthly, this application provides an apparatus for stopping monitoring of the Physical Downlink Control Channel (PDCCH). The apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to: transmit a second downlink control information (DCI) to a terminal device on the active downlink bandwidth portion (BWP). The second DCI is used to instruct the DL BWP to switch and to stop monitoring the PDCCH within a first duration. The PDCCH to be stopped includes PDCCHs in the Type 3 common search space set and PDCCHs in the terminal device's dedicated search space set. The second DCI is used to schedule the transmission of the Physical Downlink Shared Channel (PDSCH). The processing unit is configured to: perform a DL BWP switch based on the second DCI. The start time of the first duration is determined according to at least one of the following: the next time slot after the BWP switchover delay; the time slot in which the PDSCH is transmitted on the switched DL BWP; and the time slot in which the PDSCH is transmitted on the switched DL BWP. The next time slot in the time slot where the PDSCH is transmitted on the BWP; the time offset between the start time of the first duration and the second DCI; based on the maximum value between the minimum time slot offset and the duration of parsing the second DCI, the minimum time slot offset is the minimum time slot offset between the PDCCH carrying the second DCI and the PDSCH that the second DCI is allowed to schedule; or, the second DCI schedules the PDSCH, and the corresponding HARQ for the PDSCH is fed back.

[0083] In conjunction with aspect ten, in some implementations of aspect ten, the length of the first duration is configured by Radio Resource Control (RRC) or indicated by a second DCI.

[0084] In conjunction with the tenth aspect, in some implementations of the tenth aspect, the second DCI is further used to instruct the terminal device to switch to the first search space set, the first search space set being the search space set on the switched DL BWP; the aforementioned processing unit is further used to: switch to the first search space set on the switched DL BWP.

[0085] In conjunction with aspect ten, in some implementations of aspect ten, the time at which the above-mentioned device switches to the first search space set on the switched DL BWP is: the next time slot or the next symbol after the first duration, or the same time slot or symbol as the start time of the first duration.

[0086] In conjunction with the tenth aspect, in certain implementations of the tenth aspect, the time at which the aforementioned apparatus switches to the first search space set on the switched DL BWP is determined based on at least one of the following information, and is different from the start time of the first duration: the next time slot after the BWP switching delay; the time slot in which the PDSCH is transmitted on the switched DL BWP; the next time slot in which the PDSCH is transmitted on the switched DL BWP; the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or, after the second DCI schedules the PDSCH and the HARQ corresponding to the PDSCH is fed back.

[0087] In one aspect, this application provides a communication apparatus for executing the methods in the foregoing aspects or any possible implementations thereof. Specifically, the apparatus includes units for executing the methods in the foregoing aspects or any possible implementations thereof.

[0088] In one design, the device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects one by one. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0089] In another design, the device is a communication chip, which may include input circuitry or interface for transmitting information or data, and output circuitry or interface for receiving information or data.

[0090] In another design, the device is a communication device, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0091] In another design, the device is used to perform the methods in any of the above aspects or any possible implementations of the above aspects. The device may be configured in the above terminal device or network device, or the device itself may be the above terminal device or network device.

[0092] In a twelfth aspect, this application provides another communication device, including a processor and a memory for storing a computer program, the processor for calling and running the computer program from the memory, such that the device performs the method in any possible implementation of any of the above aspects.

[0093] Optionally, there may be one or more processors and one or more memories.

[0094] Alternatively, the memory can be integrated with the processor, or the memory can be set up separately from the processor.

[0095] Optionally, the communication device also includes a transmitter and a receiver, which can be set separately or integrated together and referred to as a transceiver.

[0096] In a thirteenth aspect, a communication system is provided, including means for implementing any of the above aspects or any possible implementation of the method.

[0097] In one possible design, the communication system may also include other devices that interact with the terminal device and / or network device as provided in the embodiments of this application.

[0098] In a fourteenth aspect, a computer-readable medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any possible implementation of any of the above aspects.

[0099] In a fifteenth aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform a method in any possible implementation of any of the foregoing aspects. Attached Figure Description

[0100] Figure 1 This is a schematic diagram illustrating a method to bypass the PDCCH listening mechanism;

[0101] Figure 2 This is a schematic diagram of the PDCCH listening cycle of an SS set associated with SSSG 0 and SSSG 1;

[0102] Figure 3 This is a schematic diagram of a BWP switching process;

[0103] Figure 4 This is a diagram illustrating another type of BWP switching;

[0104] Figure 5 This is a schematic diagram of a communication system provided in an embodiment of this application;

[0105] Figure 6 This is a schematic flowchart illustrating a method for stopping PDCCH monitoring provided in an embodiment of this application;

[0106] Figure 7 This is a schematic diagram illustrating how to stop monitoring the PDCCH according to an embodiment of this application;

[0107] Figure 8 This is a schematic flowchart illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0108] Figure 9 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0109] Figure 10 This is a schematic flowchart illustrating another method for stopping PDCCH monitoring provided in the embodiments of this application;

[0110] Figure 11 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0111] Figure 12 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0112] Figure 13 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0113] Figure 14 This is a schematic flowchart of a communication device provided in an embodiment of this application;

[0114] Figure 15 This is a schematic flowchart of another communication device provided in the embodiments of this application;

[0115] Figure 16 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0116] Figure 17 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0117] Figure 18 This is a schematic flowchart illustrating another method for stopping PDCCH monitoring provided in the embodiments of this application;

[0118] Figure 19 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0119] Figure 20 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0120] Figure 21 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0121] Figure 22 This is a schematic diagram illustrating another method for stopping PDCCH monitoring provided in an embodiment of this application;

[0122] Figure 23 This is a schematic diagram of another method for stopping PDCCH monitoring provided in an embodiment of this application. Detailed Implementation

[0123] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0124] The technical solutions of this application can be applied to various communication systems, such as LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5th generation (5G) systems, new radio (NR) systems, or other evolved communication systems.

[0125] The terminal equipment in this application embodiment can also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0126] Terminal devices can be devices that provide voice / data connectivity to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0127] Furthermore, in this embodiment of the application, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0128] Furthermore, the network device in this application embodiment can be a device used to communicate with terminal devices. This network device can also be called an access network device or a wireless access network device. It can be a transmission reception point (TRP), an evolved NodeB (eNB or eNodeB) in an LTE system, a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless controller in a cloud radio access network (CRAN) scenario. Alternatively, the network device can be a relay station, access point, vehicle-mounted device, wearable device, or a network device in a 5G network or a network device in a future evolved PLMN network. It can be an access point (AP) in a WLAN, a gNB in ​​a new radio (NR) system, or a satellite base station in a satellite communication system. This application embodiment is not limited to these categories.

[0129] In a network architecture, network devices may include centralized unit (CU) nodes, distributed unit (DU) nodes, RAN devices including CU nodes and DU nodes, or RAN devices including control plane CU nodes (CU-CP nodes), user plane CU nodes (CU-UP nodes), and DU nodes.

[0130] Network equipment provides services to cells. Terminal devices communicate with cells through transmission resources (e.g., frequency domain resources, or spectrum resources) allocated by the network equipment. The cell can belong to a macro base station (e.g., macro eNB or macro gNB) or to a base station corresponding to a small cell. Small cells can include: metrocell, microcell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0131] In this embodiment, the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

[0132] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0133] To facilitate understanding of the embodiments of this application, the relevant terms involved in the embodiments of this application will be introduced.

[0134] 1. Skip PDCCH monitoring mechanism

[0135] The PDCCH skipping mechanism refers to the network device instructing the terminal device to skip PDCCH listening for a period of time via downlink control information (DCI). In other words, the terminal device can stop listening to the PDCCH for a certain period or not listen to the PDCCH at all. The terminal device reduces power consumption by entering a sleep state (also known as a hibernation state) during the period of not listening to the PDCCH.

[0136] For example, Figure 1 This is a schematic diagram illustrating a method to bypass the PDCCH listening mechanism. (Example) Figure 1 As shown, the terminal device can periodically listen to the PDCCH in two time slots. The squares filled with black patterns in the figure represent the PDCCH listening times that should be listened to.

[0137] When a terminal device receives a DCI instruction to stop listening to the PDCCH for a certain period of time, the terminal device may stop listening to the PDCCH for that period of time after receiving the DCI. The duration of this period is the PDCCH listening stop duration. After the PDCCH listening stop duration, the terminal device may resume listening to the PDCCH. The PDCCH listening stop duration can be indicated by the DCI, configured by radio resource control (RRC) signaling, or predefined by the protocol. Specifically, when a network device configures multiple PDCCH listening stop durations via RRC signaling, the network device can use the DCI to indicate one of these multiple PDCCH listening stop durations as the current PDCCH listening stop duration.

[0138] It should be understood that Figure 1 The duration of stopping PDCCCH monitoring, which includes 8 time slots, is merely an example, and this application does not limit the scope of the embodiments.

[0139] Type 3 common search space set can be primarily used to monitor the PDCCH of DCIs carrying any of the following radio network temporary identifiers (RNTIs): Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Transmit Power Control-Physical Uplink Shared Channel RNTI (TPC-PUSCH-RNTI), Transmit Power Control-Physical Uplink Control Channel RNTI (TPC-PUCCH-RNTI), Transmit Power Control-Sounding Reference Symbols RNTI (TPC-SRS-RNTI), or Cancellation Indication RNTI (CI-RNTI), Cell-RNTI (C-RNTI), and Modulation and Coding Strategy RNTI (C-RNTI). Scheme-Cell-RNTI (MCS-C-RNTI), configured scheduling-RNTI (CS-RNTI), power saving-RNTI (PS-RNTI), etc. The user equipment-specific search space set can be used to monitor PDCCHs carrying DCIs scrambled by any of the following RNTIs: C-RNTI, MCS-C-RNTI, semi-persistent-channel state indication-RNTI (SP-CSI-RNTI), CS-RNTI, side-link-RNTI (SL-RNTI), SL-CS-RNTI, and SL semi-persistent scheduling V-RNTI, etc.

[0140] Type 0 and Type 0A common search space sets can be used to listen to the PDCCH of DCI scrambled with system information RNTI (SI-RNTI); Type 1 common search space set can be used to listen to the PDCCH of DCI scrambled with random access RNTI (RA-RNTI), message b RNTI (MsgB-RNTI), or temporary cell RNTI (TC-RNTI); Type 2 common search space set can be used to listen to the PDCCH of DCI scrambled with paging RNTI (P-RNTI). For the common search space sets of type 0, type 0A, type 1, and type 2, when the UE is listening to the PDCCH of DCI scrambled by SI-RNTI, RA-RNTI, MsgB-RNTI, or P-RNTI, the UE can listen to the PDCCH of DCI scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI (DCI format 0_0 and DCI format 1_0).

[0141] It should be noted that the terminal device skipping PDCCH listening can also be referred to as stopping PDCCH listening, not listening to PDCCH, etc., and the embodiments of this disclosure do not limit the terminology.

[0142] When the terminal device is also configured with connected mode-discontinuous reception (C-DRX) mechanism, the skip PDCCH listening mechanism can also be used during the C-DRX activation period, that is, the terminal device can stop listening to PDCCH for a period of time during the C-DRX activation period.

[0143] 2. Search Space Set Group (SSSG) Switching Mechanism

[0144] The SSSG handover mechanism refers to the ability of network devices to instruct terminal devices to switch from the current search space group to another search space group to listen for the PDCCH. When the PDCCH listening period of the switched search space group is longer than that of the previous search space group, that is, when the PDCCH listening time of the switched search space group is relatively sparse compared to that of the previous search space group, the power consumption of the terminal devices can be reduced.

[0145] For a downlink BWP, the network device can configure multiple searchspace sets (SS sets) for the terminal device, and can group the configured SS sets. The specific number of groups is not limited in this embodiment. For example, the network device can divide the configured SS sets into 2 or 3 groups.

[0146] For example, the network device divides the configured multiple SS sets into two groups, namely SSSG 0 and SSSG 1. The network device can configure the SS set to belong to SSSG 0 or SSSG 1 in the configuration information of the SS set. The terminal device can listen to the PDCCH according to the SS set of SSSG 0 or SSSG 1. Here, SSSG 0 can also be described as SSSG0, and SSSG 1 can also be described as SSSG1, which is not limited in this embodiment of the application.

[0147] It should be understood that SSSG 0 can be interpreted as SSSG index 0, and SSSG 1 can be interpreted as SSSG index 1.

[0148] Optionally, an SS set can belong to multiple SSSGs, that is, it can belong to SSSG 0 and at the same time belong to SSSG 1.

[0149] Optionally, the SS set configuration information may not include the SSSG parameter, indicating that the SS set has not been grouped and belongs neither to SSSG0 nor SSSG1. For SS sets that are not grouped within the DL BWP, the UE listens to the PDCCH according to the SS set configuration information, which is not limited in the embodiments of this disclosure.

[0150] The PDCCH listening timing of different SSSGs associated with the SS set on a downlink BWP can be different, that is, the sparsity of the PDCCH listening timing of different SSSGs can be different.

[0151] For example, the network device divides the SS set into two SSSGs, namely SSSG 0 and SSSG 1, based on the SS set configuration information. Figure 2 This is a diagram illustrating the PDCCH listening cycle of the SS sets associated with SSSG 0 and SSSG 1. (See diagram below.) Figure 2 As shown, the PDCCH listening time of the SS set associated with SSSG 0 is periodically monitored with a period of 1 time slot, while the PDCCH listening time of the SS set associated with SSSG1 is periodically monitored with a period of 2 time slots. It should be understood that the PDCCH listening time of SSSG 1 is relatively sparse compared to that of SSSG 0.

[0152] The terminal device listens to the PDCCH according to the SS set of SSSG 0. When it receives the information from the network device instructing the terminal device to switch to SSSG 1, the terminal device switches to SSSG 1 and listens to the PDCCH according to the SS set of SSSG 1.

[0153] The terminal device switches to SSSG 1, which has a sparser PDCCH listening time, reducing PDCCH listening and thus reducing the power consumption of the terminal device.

[0154] The SSSG switching mechanism can be applied to both the Type 3 common search space set (CSSset) and the User-Specific Search Space Set (USS set), meaning that the USS set and the Type 3 CSS set can be grouped.

[0155] Terminal devices can dynamically switch SSSGs, and network devices can explicitly indicate or implicitly indicate SSSG switching to terminal devices through bit fields in DCI.

[0156] For example, there are two search space sets, SSSG 0 and SSSG 1. The explicit indication of the bit field in the DCI can be as follows: when the terminal device listens to the PDCCH according to the SS set of SSSG 1 and the field indication in the received DCI is 0, the terminal device switches to SSSG 0, ​​that is, it listens to the PDCCH according to the SS set of SSSG 0 and stops listening to the PDCCH according to the SS set of SSSG 1; when the terminal device listens to the PDCCH according to the SS set of SSSG 0 and the field indication in the received DCI is 1, the terminal device switches to SSSG 1.

[0157] For implicit DCI indication, in one possible implementation, when the terminal device listens to the PDCCH according to the SS set in SSSG1, if the terminal device detects any DCI format or a specific DCI format, the terminal device switches to SSSG 0. Alternatively, this method can be used to switch from SSSG0 to SSSG1.

[0158] In another possible implementation, when the terminal device listens to the PDCCH according to the SS set in SSSG 1, the terminal device starts a timer for SSSG switching. When the timer expires, the terminal device switches to SSSG 0. Alternatively, this method can be used to switch from SSSG0 to SSSG1.

[0159] Network devices can be configured with both the search space set group (SSSG) switching mechanism and the skip PDCCH monitoring mechanism. In this case, the terminal device can stop monitoring the PDCCH for a period of time and then monitor the PDCCH according to the SS set of one of the SSSGs.

[0160] 3. BWP switching mechanism

[0161] For a given cell, network equipment can configure multiple downlink (DL) BWPs and / or multiple uplink (UL) BWPs for terminal devices. The frequency domain resources of different BWPs may or may not overlap. At any given time, one DL BWP and one UL BWP are active within a cell.

[0162] In time division duplex (TDD) scenarios (or unpaired spectrum scenarios), DL BWPs and UL BWPs with the same ID are associated. The center frequency of each pair of associated DL BWPs and UL BWPs is the same. When a DL BWP switches, a corresponding UL BWP will also switch; when a UL BWP switches, a corresponding UL BWP will also switch.

[0163] There are two implementation methods for the BWP handover mechanism. In one possible implementation, the network device can dynamically switch between the DL BWP and the UL BWP via the PDCCH. For example, the network device can dynamically switch between the DL BWP via the PDCCH. Figure 3 This is a schematic diagram of a DL BWP switching method. (Example) Figure 3 As shown, the network device is configured with two BWPs, BWP 1 and BWP 2. BWP 1 has a subcarrier spacing of 30 kHz, while BWP 2 has a subcarrier spacing of 60 kHz. Currently, BWP 1 is active. When the terminal device detects that the BWP indicator field in the DCI indicates BWP 2, the terminal device performs a BWP handover. After the BWP handover delay, it listens for the PDCCH on BWP 2.

[0164] The DCI also schedules the PDSCH, and the terminal device can receive the PDSCH on BWP 2 according to the scheduling information of the DCI. The time slot offset K0 (i.e., the time slot offset between the PDCCH and the scheduled PDSCH) indicated by the time domain resource allocation field of the DCI should not be less than the BWP handover delay. Figure 3As shown, K0 has one more time slot than the BWP handover delay. The terminal device starts receiving PDSCH on BWP 2 at the time slot corresponding to the time slot offset K0 indicated by the DCI, and continues to listen to PDCCH. After the DCI end symbol and before the time slot offset indicated by the DCI, the terminal device does not need to receive or send data, and at the same time, the terminal device does not need to listen to PDCCH.

[0165] It should be understood that different subcarrier intervals correspond to different time slot lengths. Figure 2 The BWP handover delay includes 2 time slots, the length of which is the time slot length corresponding to a subcarrier spacing of 30kHz. K0 includes 5 time slots, the length of which is the time slot length corresponding to a subcarrier spacing of 60kHz. K0 has one more time slot than the BWP handover delay, the length of which is the time slot length corresponding to a subcarrier spacing of 60kHz.

[0166] It should also be understood that the BWP handover delay including 2 time slots and K0 including 5 time slots is merely an example, and the embodiments of this application do not limit this.

[0167] In another possible implementation, the network device can configure a timer (bwp-InactivityTimer) for BWP handover to the terminal device. This timer is used for the terminal device to fall back from the currently active BWP to the default BWP. The network device can configure the identity (ID) of the default BWP via RRC signaling, allowing the terminal device to fall back from the currently active BWP to the BWP corresponding to the default BWP identity. Alternatively, if the network device does not configure a default BWP identity, the terminal device can fall back to the initial BWP configured by the network device.

[0168] For example, Figure 4 This is a schematic diagram of another type of DL BWP switching. (Example) Figure 4 As shown, the terminal device listens to the PDCCH on the currently active BWP 1, where the subcarrier spacing of BWP 1 can be 60kHz. Under the condition that the timer is enabled or restarted, the timer is enabled or restarted and runs. If the timer restart condition is not met, the timer decrements every subframe or every half-subframe. When the timer expires (i.e., the timer is 0), the terminal device performs a BWP handover. After the BWP handover delay, it listens to the PDCCH on the default BWP. It should be understood that the subcarrier spacing of the default BWP is 30kHz, and the terminal device does not listen to the PDCCH during the BWP handover delay.

[0169] BWP 1 has a subcarrier spacing of 60kHz, with one subframe corresponding to four time slots. Figure 4The timer duration consists of 8 time slots, meaning the timer's duration is 2 milliseconds, or two subframes. When the timer is running, it can decrement by subframe or half-frame until it expires.

[0170] It should be understood that Figure 4 The duration of the timer, which includes 6 time slots, and the BWP switching delay, which includes 4 time slots, are merely examples, and this application does not limit them.

[0171] It should also be understood that different BWPs can correspond to different subcarrier intervals, and different subcarrier intervals correspond to different time slot lengths. Figure 4 The subcarrier spacing of BWP 1 and the default BWP are different, therefore the time slot lengths corresponding to BWP 1 and the default BWP are different.

[0172] The conditions for starting or restarting the timer used for BWP handover in cell 1 may include any of the following:

[0173] 1) The terminal device receives a PDCCH scrambled by C-RNTI or CS-RNTI on the BWP activated in cell 1, indicating downlink scheduling or uplink scheduling.

[0174] 2) The terminal device receives a PDCCH indication scrambled by C-RNTI or CS-RNTI in a cell other than cell 1, indicating downlink or uplink scheduling on the BWP activated in cell 1.

[0175] This condition applies to both cross-carrier scheduling and TDD scenarios.

[0176] 3) The terminal device sends uplink semi-persistent scheduling or receives downlink semi-persistent scheduling in cell 1.

[0177] 4) The terminal device receives a PDCCH instruction for BWP handover in cell 1.

[0178] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 5 The communication system applicable to the embodiments of this application will be described in detail.

[0179] Figure 5 This is a schematic diagram of a communication system 500 provided in an embodiment of this application. Figure 5 As shown, the communication system 500 may include a network device 501 and at least one terminal device 502. The network device 501 and the at least one terminal device 502 are capable of wireless communication. Specifically, the network device 501 may send a PDCCH carrying scheduling information for uplink or downlink data to the terminal device 502, and the terminal device 502 may periodically listen to the PDCCH to obtain the scheduling information.

[0180] When terminal device 502 detects scheduling information on the PDCCH, it receives data via PDSCH or sends data via PUSCH according to the scheduling information. In many cases, network device 501 does not always schedule data to terminal device 502, but terminal device 502 periodically listens to the PDCCH to determine if scheduling is possible. When there is no service transmission between network device 501 and terminal device 502, network device 501 may not need to send PDCCH to terminal device 502. If terminal device 502 still periodically listens to the PDCCH, it will result in wasted power consumption. To reduce the power consumption of terminal device 502, one approach is to minimize unnecessary PDCCH listening.

[0181] Currently, within an active DL BWP, network devices can reduce PDCCH monitoring and thus lower terminal device power consumption by using the skipPDCCH monitoring mechanism or the search space set group (SSSG) switching mechanism. For each cell, network devices can configure multiple downlink BWPs and / or multiple uplink BWPs for terminal devices, and can dynamically switch between active BWPs.

[0182] However, when a terminal device is configured to skip both the PDCCH listening mechanism and the BWP switching mechanism, there is no clear definition on how the terminal device should stop listening to the PDCCH.

[0183] For example, a network device instructs a terminal device to stop listening to the PDCCH for a certain period of time via a DCI. The terminal device can stop listening to the PDCCH for this period based on the DCI. The network device also configures a timer for BWP handover to the terminal device, which starts when certain conditions are met. The terminal device stopping listening to the PDCCH during this period can cause the timer to fail to meet the restart conditions, making it more likely to expire and resulting in frequent BWP handovers.

[0184] For example, a network device instructs a terminal device to stop listening to the PDCCH for a period of time and perform a BWP handover. The terminal device performs a BWP handover according to the instruction of the DCI and stops listening to the PDCCH for a period of time. However, there is currently no clear definition of the start time for stopping listening to the PDCCH.

[0185] In view of this, embodiments of this application provide a method and communication device for stopping PDCCH monitoring. When the terminal device simultaneously supports skipping the PDCCH monitoring mechanism and the BWP switching mechanism, the time for stopping PDCCH monitoring is clearly defined, which is beneficial to reducing the power consumption of the terminal device.

[0186] To facilitate understanding of the embodiments of this application, the following points are provided.

[0187] 1. In the embodiments of this application, "for indicating" can include both direct and indirect indication, as well as explicit and implicit indication. The information indicated by a certain piece of information is called the information to be indicated. In specific implementation, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also indirectly indicate the information to be indicated by indicating other information, where there is a correlation between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of the information to be indicated can be achieved by pre-agreed upon (e.g., by a protocol specifying) the existence of a certain information element, thereby reducing the indication overhead to some extent.

[0188] 2. In the embodiments shown below, the first, second, third, and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, distinguishing different downlink control information, etc.

[0189] 3. In the embodiments shown below, "predefined" can be a protocol definition. "Predefined" can be implemented by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method.

[0190] 4. The “protocol” mentioned in the embodiments of this application may refer to standard protocols in the field of communication, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols applied to future communication systems. This application does not limit this.

[0191] The various embodiments provided in this application will now be described in detail.

[0192] This application describes terminal devices and network devices as examples. It should be understood that terminal devices can be replaced with devices or chips that can perform similar functions to terminal devices, and network devices can also be replaced with devices or chips that can perform similar functions to network devices. The names of these devices are not limited in this application.

[0193] Figure 6 This is a schematic flowchart illustrating a method 600 for stopping PDCCH monitoring, provided in an embodiment of this application. Method 600 can be applied to... Figure 5The communication system 500 shown is not limited to this embodiment. Figure 6 As shown, the method 600 may include the following steps:

[0194] S601. The network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's private search space set. Correspondingly, the terminal device receives the first DCI on the activated DL BWP.

[0195] The first DCI can be carried in the PDCCH. The terminal device can detect the first DCI in the PDCCH and stop listening to the PDCCH for a first duration based on the first DCI. After the first duration, the terminal device can continue listening to the PDCCH. The PDCCH that is stopped from being listened to includes PDCCH in the type 3 common search space set and PDCCH in the terminal device-specific search space set. For other types of common search space sets, such as type 0, type 0A, type 1, and type 2 common search space sets, the UE can skip or not skip the PDCCH listening of DCIs scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI. The embodiments of this disclosure are not limited. For type 0, type 0A, type 1, and type 2 common search space sets, whether the UE listens to SI-RNTI, RA-RNTI, TC-RNTI, or P-RNTI is not limited in the embodiments of this disclosure.

[0196] If the terminal device is also configured with the C-DRX mechanism, the first DCI can be used to instruct the terminal device to stop listening to the PDCCH for a first duration during the C-DRX activation period. During the C-DRX activation period, the terminal device stops listening to the PDCCH for the first duration, and after the first duration, the terminal device can continue listening to the PDCCH during the activation period.

[0197] The unit of the first duration can be seconds, milliseconds, frames, subframes, time slots, PDCCH listening periods, the number of PDCCH listening opportunities, a set of time slots consisting of several consecutive time slots, etc., which are not limited in this disclosure. For example, the first duration can be 8 time slots, and the terminal device can stop listening to the PDCCH within 8 time slots.

[0198] The start time of the first duration can be the beginning of the time slot where the first DCI is located, or the beginning of the next time slot of the first DCI, or the beginning of the next symbol after the end symbol of the first DCI. This application does not limit the time slot.

[0199] Optionally, the length of the first duration can be configured by RRC or indicated by the first DCI. The specific RRC configuration or DCI indication method is not limited in this embodiment.

[0200] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH for a first duration, and indicates the length of the first duration.

[0201] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The network device also sends an RRC signaling message to the terminal device on the activated DL BWP. The RRC signaling message is used to indicate the length of the first duration.

[0202] Optionally, the length of the first duration can be predefined by the protocol.

[0203] S602, The terminal device runs a timer, which is used for BWP handover. The timer expires before the end of the first duration.

[0204] It should be understood that during the BWP handover process, i.e., within the BWP handover delay, the terminal device does not need to listen to the PDCCH. Therefore, it can also be described as the terminal device running a timer for BWP handover, where the timer's expiration time and the BWP handover delay are both before the end of the first duration. This can be understood as the BWP handover delay ending before the end of the first duration.

[0205] The timer duration can be configured by the network device via RRC signaling or predefined by the protocol. The timer duration unit can be seconds, milliseconds, frames, subframes, time slots, etc., and this application embodiment does not limit this. For example, the timer duration can be 3 milliseconds.

[0206] The terminal device can start and run the timer before S601.

[0207] When the conditions for starting or restarting the timer are met (e.g., scheduling information is included in the first DCI), the terminal device starts or restarts the timer and runs it, i.e., decrements by each subframe or each half-subframe. After the timer expires, the terminal device performs a DL BWP handover. If the conditions for restarting the timer are met before the timer expires, the timer restarts, i.e., it resumes operation.

[0208] For example, the timer duration is 3 milliseconds. After the timer is started or restarted, if the conditions for starting or restarting the timer are not met, the terminal device runs the timer, that is, the timer decreases by one subframe each time. When the timer is 0, the terminal device performs DL BWP switching. If the conditions for restarting the timer are met when the timer is 2 milliseconds, the timer becomes 3 milliseconds again and decreases by one subframe each time, repeating the above steps.

[0209] The timer expires before the end of the first duration, for example, the first duration is longer than the timer's expiration duration. For instance, the first duration can be 8 time slots, and the timer's duration can be 3 milliseconds, or 6 time slots.

[0210] The specific time position for starting or restarting the timer can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application embodiment does not limit this.

[0211] Correspondingly, the network device starts or restarts the timer and runs it.

[0212] S603. The terminal device stops listening to the PDCCH within the first duration and before the timer expires.

[0213] It should be understood that the PDCCHs that are no longer being monitored include PDCCHs in the Type 3 public search space set and PDCCHs in the terminal device-specific search space set.

[0214] Accordingly, the network device will not send PDCCH to the terminal device within the first time period and before the timer expires, including the PDCCH in the type 3 public search space set and the PDCCH in the terminal device private search space set.

[0215] It should be understood that during the BWP handover process, i.e., within the BWP handover delay, the terminal device does not need to listen to the PDCCH. Therefore, step S603 can also be described as the terminal device stopping listening to the PDCCH within the first duration, before the timer expires and before the BWP handover delay ends. This can be understood as the terminal device stopping listening to the PDCCH within the first duration, before the BWP handover delay ends.

[0216] S604. When the timer expires, the terminal device performs a DL BWP switch and listens for PDCCH on the switched DL BWP.

[0217] The first duration ends after the timer's expiration time. When the timer expires, the period for stopping PDCCH listening does not end, but the terminal device can still listen to PDCCH on the switched-in DL BWP. The switched-in DL BWP is the newly activated DL BWP. The switched-in DL BWP can also be called the default DL BWP.

[0218] For example, Figure 7 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 7 As shown, the black-filled squares represent the PDCCH listening opportunities that the terminal device can monitor. The network device is configured with DL BWP 1 and a default DL BWP in a cell. The subcarrier spacing of DL BWP 1 can be 30kHz, the timer duration can be 6 time slots, and the first duration can be 11 time slots, with the first duration being longer than the timer duration. The subcarrier spacing of the default DL BWP can be 15kHz. The BWP handover delay can be 2 time slots. It should be understood that different subcarrier spacings correspond to different time slot lengths. The time slot lengths included in the timer duration, the first duration, and the BWP handover delay are all time slot lengths corresponding to a subcarrier spacing of 30kHz. It should also be understood that the timer duration, the first duration, and the number of time slots included in the BWP handover delay are merely an example, and this application embodiment does not limit this.

[0219] When the subcarrier spacing of DL BWP 1 is 30kHz, one subframe corresponds to two time slots. Figure 7 The timer duration is 6 time slots, which is equivalent to 3 subframes. When the timer is running, it can decrement every subframe or every half-subframe until it expires.

[0220] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The network device instructs the terminal device to stop listening to the PDCCH within a first duration through the PDCCH carrying the first DCI. The terminal device listens to the PDCCH carrying the first DCI and obtains the indication of the first DCI by detecting the PDCCH carrying the first DCI. Figure 7 As shown, under the condition that the timer is enabled or restarted, the terminal device can start running the timer in the time slot where the first DCI is located, and stop listening to PDCCH in the next time slot of the first DCI. When the timer expires (after 3 subframes), the terminal device performs DL BWP switching. After the BWP switching delay (2 time slots), the terminal device switches to the default DL BWP to listen to PDCCH.

[0221] It should be understood that the duration of stopping PDCCH listening has not ended at this time, but the terminal device can listen to PDCCH on the default DL BWP, which can also be understood as terminating the duration of stopping PDCCH listening in advance.

[0222] Correspondingly, when the timer expires, the network device performs a DL BWP handover and can send PDCCH on the switched DL BWP. The method for stopping PDCCH listening provided in this application embodiment involves the network device instructing the terminal device to stop listening to PDCCH within a first duration and configuring a timer for BWP switching. The terminal device can simultaneously run the timer and begin stopping PDCCH listening. Within the first duration, and before the timer expires, it stops listening to PDCCH and listens to PDCCH on the switched BWP. This method allows for simultaneous running of the timer and starting to stop PDCCH listening without altering the timer's operation, resulting in minimal impact on the protocol and simple implementation. It is understood that in the method for stopping PDCCH listening provided in this application embodiment, the BWP is switched via a timer, and the default behavior of the terminal device on the switched BWP is to listen to PDCCH. Optionally, SSSG can be configured on the switched DLBWP, or it can be left unconfigured. This embodiment does not limit the method by which the network device configures SSSG.

[0223] If no SSSG is configured on the switched-over BWP, the terminal device will listen to the PDCCH according to the configured SSset on the switched-over BWP.

[0224] When an SSSG is configured on the BWP after handover, the terminal device listens to the PDCCH based on the SS set in one of the SSSGs. For example, if the network device is configured with SSSGs on the BWP after handover, there can be two SSSGs: SSSG0 (SSSG index 0) and SSSG1 (SSSG index 1). The terminal device can listen to the PDCCH based on the SS set of SSSG0 or the SS set of SSSG1.

[0225] Optionally, the number of SSSGs can be three, namely SSSG0 (SSSG index 0), SSSG1 (SSSG index 1), and SSSG2 (SSSG index 2). The terminal device can listen to the PDCCH according to the SS set of SSSG0, SSSG1, or SSSG2. One possible implementation is that an SSSG is configured on the BWP after handover, and the terminal device listens to the PDCCH on the BWP according to the SS set of the SSSG agreed upon in the protocol. The agreed SSSG can be SSSG0, SSSG1, or SSSG2. For example, if an SSSG is configured on the BWP after handover, the protocol stipulates that the terminal device listens to the PDCCH on the BWP according to the SS set of SSSG0. Another possible implementation is that the network device can configure one SSSG as the SSSG for the terminal device to listen to the PDCCH on the BWP after handover. For example, if the network device configures SSSG0, the terminal device listens to the PDCCH on the BWP according to the SS set of SSSG0.

[0226] Optionally, the aforementioned activated DL BWP can be configured in the first cell, and the terminal device can listen to the PDCCH on the activated DL BWP in the first cell. The network device can configure the duration of the timer on the first cell.

[0227] It should be understood that when multiple cells exist, network devices can configure the duration of timers on each of those cells separately.

[0228] The terminal device can receive the first DCI on the active DL BWP of the first cell. The first DCI is used to instruct the terminal device to stop listening to the PDCCH for a first duration. In a multi-cell scenario, the terminal device can also receive the first DCI on the active DL BWP of cells other than the first cell. The first DCI is used to instruct the terminal device to stop listening to the PDCCH on the active DL BWP of the first cell, and the duration of stopping listening to the PDCCH is the first duration.

[0229] Optionally, the first DCI can also be used to schedule the transmission of PDSCH or PUSCH.

[0230] For example, the terminal device can receive a first DCI on the active DL BWP of the first cell. This first DCI instructs the terminal device to stop listening to the PDCCH for a first duration and schedule the transmission of PDSCH or PUSCH. In a scenario with multiple cells, the terminal device can also receive a first DCI on the active DL BWP of cells other than the first cell. This first DCI instructs the terminal device to stop listening to the PDCCH on the active DL BWP of the first cell for a first duration and simultaneously schedule the transmission of PDSCH or PUSCH.

[0231] It should be understood that when the first DCI includes scheduling information and the network device is configured with a timer for switching BWP, the terminal device starts running the timer.

[0232] Optionally, the terminal device can listen to the PDCCH according to the SS set configured on the active DL BWP. If multiple SSSGs are configured on the BWP, the terminal device can listen to the PDCCH according to the SS set of one of the SSSGs. Therefore, if no SSSG is configured on the switched-over DL BWP, the terminal device will perform a DL BWP handover when the timer expires, and listen to the PDCCH on the switched-over DL BWP according to the configured SS set. That is, the default behavior of the terminal device on the switched-over BWP is to listen to the PDCCH according to the configured SS set. If an SSSG is configured on the switched-over DL BWP, the terminal device will perform a DL BWP handover when the timer expires, and listen to the PDCCH on the switched-over DL BWP according to the SS set of one of the SSSGs. That is, the default behavior of the terminal device on the switched-over BWP is to listen to the PDCCH according to the SS set of one of the SSSGs. This SSSG can be protocol-defined or configured by the network device. This SSSG can be SSSG0, SSSG1, or SSSG2. For example, the terminal device listens to the PDCCH on the switched-over BWP according to the SS set with SSSG index 0.

[0233] Optionally, when the network device initially configures or reconfigures the parameters for skipping the PDCCH listening mechanism and / or the parameters for the SSSG switching mechanism via RRC signaling, the behavior of the terminal device on the activated DL BWP can be the same as above. That is, when no SSSG is configured on the activated DL BWP, the terminal device listens to the PDCCH according to the configured SS set on the activated DL BWP. In other words, the default behavior of the terminal device on the activated DL BWP is to listen to the PDCCH according to the configured SS set. When an SSSG is configured on the activated DL BWP, the terminal device listens to the PDCCH according to the SS set of one of the SSSGs on the activated DL BWP. That is, the default behavior of the terminal device on the activated DL BWP is to listen to the PDCCH according to the SS set of one of the SSSGs. This SSSG can be protocol-defined or configured by the network device. This SSSG can be SSSG0, SSSG1, or SSSG2. For example, the terminal device listens to the PDCCH according to the SS set with SSSG index 0 on the activated DL BWP.

[0234] In the above method 600, the terminal device stops listening to the PDCCH while running the timer. This application embodiment proposes another method 800 to stop listening to the PDCCH. Method 800 is a scheme parallel to method 600, in which the terminal device stops running the timer while stopping listening to the PDCCH.

[0235] Specifically, Figure 8 This is a schematic flowchart illustrating another method 800 for stopping PDCCH monitoring provided in this application embodiment. Method 800 can be applied to... Figure 5 The communication system 500 shown is not limited to this embodiment. Figure 8 As shown, the method 800 may include the following steps:

[0236] S801. The network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI instructs the terminal device to stop listening to PDCCH for a first duration. The PDCCH to be stopped includes PDCCH in the Type 3 common search space set and PDCCH in the terminal device's dedicated search space set. Correspondingly, the terminal device receives the first DCI on the activated DL BWP. The start time of the first duration can be the beginning of the time slot where the first DCI is located, or the beginning of the next time slot of the first DCI, or the beginning of the next symbol after the end symbol of the first DCI. This embodiment of the application does not limit this.

[0237] Optionally, the length of the first duration can be configured by RRC or indicated by the first DCI. The specific RRC configuration or DCI indication method is not limited in this embodiment.

[0238] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH for a first duration, and indicates the length of the first duration.

[0239] For example, the network device sends a first DCI to the terminal device on the activated DL BWP. The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The network device also sends an RRC signaling message to the terminal device on the activated DL BWP. The RRC signaling message is used to indicate the length of the first duration.

[0240] Optionally, the length of the first duration can be predefined by the protocol.

[0241] This step can be referred to as S601 in method 600 above, and will not be repeated here.

[0242] S802, Terminal device runs a timer, which is used for BWP handover.

[0243] The timer duration can be configured by the network device via RRC signaling or predefined by the protocol. The timer duration unit can be seconds, milliseconds, frames, subframes, time slots, etc., and this application embodiment does not limit this. For example, the timer duration can be 3 milliseconds.

[0244] The terminal device can start and run the timer before S801.

[0245] When the conditions for starting or restarting the timer are met (e.g., scheduling information is included in the first DCI), the terminal device starts or restarts the timer and runs it, i.e., decrements by each subframe or each half-subframe. After the timer expires, the terminal device performs a DL BWP handover. If the conditions for restarting the timer are met before the timer expires, the timer restarts, i.e., it resumes operation.

[0246] The specific time position for starting or restarting the timer can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application embodiment does not limit this.

[0247] Correspondingly, the network device starts or restarts the timer and runs it.

[0248] S803: The terminal device, based on the first DCI, stops listening to the PDCCH within the first duration and pauses the timer.

[0249] The terminal device pauses the timer during the period when it stops listening to the PDCCH. That is, during the period when it stops listening to the PDCCH, the timer pauses in increments of each subframe or half-frame.

[0250] Optionally, the terminal device may pause the operation of the timer from the time slot or subframe where the first DCI is located, or from the next time slot or the next subframe of the first DCI.

[0251] Optionally, the terminal device may pause the timer from the start time of the first duration.

[0252] S804. After the first duration, the terminal device continues to run the timer. The terminal device pauses the timer's operation, and after the first duration, it can resume running the timer, either by decrementing by each subframe or by decrementing by each half-subframe. After the first duration, if the timer restart condition is met, the terminal device can restart the timer and begin running it.

[0253] For example, the timer duration can be 3 milliseconds. When the timer decreases to 2 milliseconds, the terminal device receives the PDCCH carrying the first DCI. Based on the first DCI, it stops listening to the PDCCH. At the same time, the timer will remain for 2 milliseconds. After the first duration has elapsed, the terminal device can continue to run the timer, decreasing by one subframe each time, until the timer expires.

[0254] S805. When the timer expires, the terminal device performs a DL BWP switch.

[0255] After a terminal device performs a DL BWP switch, it can listen to the PDCCH on the new DL BWP. The new DL BWP can be referred to as the default BWP. For example, Figure 9 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 9 As shown, the black-filled squares represent the PDCCH listening opportunities that the terminal device can monitor. The network device is configured with DL BWP 1 and a default DL BWP in a cell. The subcarrier spacing of DL BWP 1 can be 30kHz, the timer duration can be 6 time slots, and the first duration can be 10 time slots. The subcarrier spacing of the default DL BWP can be 15kHz. The BWP handover delay can be 2 time slots. It should be understood that different subcarrier spacings correspond to different time slot lengths. The time slot lengths included in the timer duration, the first duration, and the BWP handover delay are all time slot lengths corresponding to a subcarrier spacing of 30kHz. It should also be understood that the timer duration, the first duration, and the number of time slots included in the BWP handover delay are merely an example, and this application embodiment does not limit this.

[0256] When the subcarrier spacing of DL BWP 1 is 30kHz, one subframe corresponds to two time slots. Figure 9 The timer duration is 6 time slots, which is equivalent to 3 subframes. When the timer is running, it can decrement every subframe or every half-subframe until it expires.

[0257] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The network device instructs the terminal device to stop listening to the PDCCH within a first duration through the PDCCH carrying the first DCI. The terminal device listens to the PDCCH carrying the first DCI and obtains the indication of the first DCI by detecting the PDCCH carrying the first DCI. Figure 9 As shown, under the condition that the timer is enabled or restarted, the terminal device can start running the timer in the time slot where the first DCI is located. The timer decrements by each subframe. At the same time, it stops listening to the PDCCH and pauses the timer at the start time of the first duration. At this time, the duration of the timer is 4 time slots, or two subframes.

[0258] The terminal device stops listening to the PDCCH within 10 time slots. After 10 time slots, the terminal device resumes listening to the PDCCH and continues running the timer, which decrements every subframe from two subframes until it expires. When the timer expires, the terminal device performs a DL BWP handover. After the BWP handover delay (2 time slots), the terminal device switches to the default DLBWP to listen to the PDCCH.

[0259] S806, Network Device Run Timer.

[0260] While the terminal device is running its timer, the network device can also run its timer accordingly.

[0261] Optionally, the protocol can stipulate that the terminal device and the network device run timers simultaneously.

[0262] S807. The network device suspends the operation of the timer within the first duration.

[0263] While the terminal device pauses the timer's operation within the first duration, the network device can also pause the timer's operation within the first duration.

[0264] Optionally, the protocol may stipulate that the terminal device and the network device simultaneously suspend the operation of the timer within a first duration.

[0265] S808: After the first duration, the network device continues to run the timer.

[0266] After the initial duration, while the terminal device is running its timer, the network device can also continue running its timer.

[0267] Optionally, the protocol may stipulate that after the first duration, both the terminal device and the network device continue to run the timer.

[0268] S809. When the timer expires, the network device performs a DL BWP switch.

[0269] When the timer expires, the network device can switch BWPs and send PDCCHs on the switched BWPs. The terminal devices can listen to the PDCCHs on the switched BWPs.

[0270] As another possible implementation, S803 allows the terminal device to stop listening to the PDCCH and terminate the timer within a first duration based on the first DCI. S804 allows the terminal device to restart the timer and run it after the first duration. Correspondingly, in S807, the network device can terminate the timer within the first duration. S808 allows the network device to restart the timer and run it after the first duration.

[0271] The method for stopping PDCCH listening provided in this application embodiment involves a network device instructing a terminal device to stop listening to the PDCCH within a first duration and configuring a timer for switching BWPs. The terminal device pauses the timer's operation while stopping PDCCH listening, and resumes operation after the first duration. This means that stopping PDCCH listening and running the timer occur at different times, avoiding the problem of timer expiration due to stopping PDCCH listening. Furthermore, the fact that the terminal device can stop listening to the PDCCH within the first duration reduces its power consumption.

[0272] Optionally, SSSG can be configured on the switched DL BWP, or it can be left unconfigured.

[0273] If no SSSG is configured on the switched BWP, the terminal device listens to the PDCCH according to the configured SS set on the switched BWP.

[0274] When an SSSG is configured on the switched-over BWP, the terminal device listens to the PDCCH based on the SS set in one of the SSSGs. For example, if the network device configures SSSGs on the switched-over BWP, the number of SSSGs can be two: SSSG0 (SSSG index 0) and SSSG1 (SSSG index 1). The terminal device can listen to the PDCCH based on the SS set of SSSG0 or SSSG1. Optionally, the number of SSSGs can be three: SSSG0 (SSSG index 0), SSSG1 (SSSG index 1), and SSSG2 (SSSG index 2). The terminal device can listen to the PDCCH based on the SS set of SSSG0, SSSG1, or SSSG2. One possible implementation is that an SSSG is configured on the switched-over BWP, and the terminal device listens to the PDCCH based on the SS set of the SSSGs specified in the protocol. The specified SSSGs can be SSSG0, SSSG1, or SSSG2. For example, if an SSSG is configured on the BWP after handover, the protocol stipulates that the terminal device on the BWP will listen to the PDCCH according to the SS set of SSSG0. Alternatively, the network device can configure an SSSG as the SSSG for the terminal device to listen to the PDCCH on the BWP after handover. For example, if the SSSG configured on the network device is SSSG0, then the terminal device on the BWP will listen to the PDCCH according to the SS set of SSSG0.

[0275] Optionally, when the network device initially configures or reconfigures the parameters for skipping the PDCCH listening mechanism and / or the parameters for the SSSG switching mechanism via RRC signaling, the behavior of the terminal device on the activated DL BWP can be the same as above. That is, when no SSSG is configured on the activated DL BWP, the terminal device listens to the PDCCH according to the configured SS set on the activated DL BWP. In other words, the default behavior of the terminal device on the activated DL BWP is to listen to the PDCCH according to the configured SS set. When an SSSG is configured on the activated DL BWP, the terminal device listens to the PDCCH according to the SS set of one of the SSSGs on the activated DL BWP. That is, the default behavior of the terminal device on the activated DL BWP is to listen to the PDCCH according to the SS set of one of the SSSGs. This SSSG can be protocol-defined or configured by the network device. This SSSG can be SSSG0, SSSG1, or SSSG2. For example, the terminal device listens to the PDCCH according to the SS set with SSSG index 0 on the activated DL BWP.

[0276] In methods 600 and 800 above, the terminal device runs a timer, including: when the terminal device receives indication information from the network device on an active DLBWP, the terminal device starts or restarts the timer; wherein, the indication information is used to schedule the terminal device to transmit PDSCH or PUSCH, or, the indication information is used to instruct the terminal device to perform DLBWP switching, and the indication information is carried in the first DCI or other DCIs different from the first DCI.

[0277] The instruction information can be carried in the first DCI or in other DCIs different from the first DCI. This application does not limit this.

[0278] In one possible implementation, the indication information is used to schedule the terminal device to transmit PDSCH or PUSCH, and is carried in the first DCI, which may be carried in a PDCCH scrambled by C-RNTI or CS-RNTI.

[0279] The terminal device receives a PDCCH scrambled with C-RNTI carrying a first DCI on the DL BWP activated in the first cell. The first DCI is used to schedule the transmission of PDSCH or PUSCH. The terminal device starts or restarts a timer. Alternatively, the terminal device receives a PDCCH scrambled with C-RNTI carrying a different DCI than the first DCI in a cell other than the first cell. This DCI is used to indicate the transmission of PDSCH or PUSCH on the DL BWP activated in the first cell. The terminal device starts or restarts a timer.

[0280] In another possible implementation, the indication information is used to instruct the terminal device to perform a DL BWP switch, and the indication information is carried in a different DCI than the first DCI.

[0281] The terminal device receives a different DCI than the first DCI. This different DCI is used to instruct the terminal device to perform a DL BWP handover. The terminal device performs a BWP handover based on the DCI and starts a timer in the BWP after the handover.

[0282] The start time of the first duration is not explicitly defined in methods 600 and 800 described above. This application provides a method 1000 for stopping PDCCH monitoring, which can clearly define the start time of the first duration.

[0283] Specifically, Figure 10 This is a schematic flowchart illustrating another method 1000 for stopping PDCCH monitoring provided in this application embodiment. Method 1000 can be applied to... Figure 5 The communication system 500 shown is not limited to this embodiment. Figure 10 As shown, the method 1000 may include the following steps:

[0284] S1001. The network device sends a second DCI to the terminal device on the activated DL BWP. The second DCI is used to instruct the DLBWP to switch and stop listening to PDCCH within a first duration. The PDCCH to be stopped includes PDCCH in the type 3 common search space set and PDCCH in the terminal device's dedicated search space set. The second DCI is used to schedule the transmission of PDSCH. Correspondingly, the terminal device receives the second DCI on the activated DL bandwidth portion BWP.

[0285] The second DCI can be carried in the PDCCH. The terminal device can detect the second DCI in the PDCCH on the activated DL BWP, and based on the second DCI, stop listening to the PDCCH within a first duration and perform DL BWP handover. The PDCCH to be stopped includes PDCCHs in the Type 3 common search space set and PDCCHs in the terminal device-specific search space set. For other types of common search space sets, such as Type 0, Type 0A, Type 1, and Type 2 common search space sets, the UE may or may not skip listening to PDCCHs scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI; the embodiments of this disclosure are not limited. For Type 0, Type 0A, Type 1, and Type 2 common search space sets, whether the UE listens to SI-RNTI, RA-RNTI, TC-RNTI, or P-RNTI is not limited in the embodiments of this disclosure.

[0286] The BWP indication field in the second DCI indicates the DL BWP switch and instructs the device to stop listening to the PDCCH within a first duration, while simultaneously scheduling the transmission of the PDSCH. Specifically, the second DCI may carry PDSCH scheduling information, and the BWP indication field in the second DCI indicates the ID of the DL BWP, which is different from the ID of the currently active DL BWP. The terminal device switches to the DL BWP indicated in the second DCI indication field based on the second DCI.

[0287] The start time of the first duration can be at the beginning of the time slot where the first DCI is located, or at the beginning of the next time slot of the first DCI, or at the beginning of the next symbol after the end symbol of the first DCI. This application does not limit the time slot.

[0288] Optionally, the length of the first duration can be configured by RRC or indicated by the first DCI. The specific RRC configuration or DCI indication method is not limited in this embodiment.

[0289] For example, the network device sends a second DCI to the terminal device on the activated DL BWP. The second DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration, and indicates the length of the first duration.

[0290] For example, the network device sends a second DCI to the terminal device on the activated DL BWP. The second DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The network device also sends RRC signaling to the terminal device on the activated DL BWP. The RRC signaling is used to indicate the length of the first duration.

[0291] Optionally, the length of the first duration can be predefined by the protocol.

[0292] S1002. The terminal device performs a DL BWP handover based on the second DCI and stops listening to the PDCCH on the DL BWP after the handover. The start time of the first duration is determined based on at least one of the following: the next time slot after the BWP handover delay; the time slot in which the PDSCH is transmitted on the DL BWP after the handover; the next time slot in which the PDSCH is transmitted on the DL BWP after the handover; the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration for parsing the second DCI, where the minimum time slot offset is the minimum time slot offset between the PDCCH carrying the second DCI and the PDSCH that the second DCI is allowed to schedule; or, after the second DCI schedules the PDSCH and the HARQ feedback corresponding to the PDSCH.

[0293] The start time of the first duration can be the next time slot after the BWP handover delay, the time slot in which the PDSCH is transmitted on the switched DLBWP, or the time slot following the time slot in which the PDSCH is transmitted on the switched DL BWP. The latter, "the time slot following the time slot in which the PDSCH is transmitted on the switched DL BWP," can also be understood as the time slot following the time slot in which the PDSCH is transmitted on the switched DL BWP.

[0294] The start time of the first duration can be determined based on at least one of the following: the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or the information obtained after the second DCI schedules the PDSCH and the HARQ feedback corresponding to the PDSCH. For ease of description, the start time of the first duration determined by one of these methods is denoted as the start time 2 of the first duration.

[0295] The method for stopping PDCCH listening provided in this application embodiment starts at the next time slot after the BWP handover delay, either in the time slot where the PDSCH is transmitted on the switched DL BWP, or in the next time slot after the time slot where the PDSCH is transmitted on the switched DLBWP. This ensures that there is no overlap between the first duration and the BWP handover delay, allowing the terminal device to stop listening to PDCCH for a longer period and reducing the power consumption of the terminal device. Furthermore, the start time of the first duration is determined based on at least one of the following: the time offset between the start time of the first duration and the second DCI; the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or the second DCI scheduling PDSCH and the feedback from the corresponding hybrid automatic repeat request (HARQ). It does not require consideration of whether there is overlap between the first duration and the BWP handover delay. The start time of the first duration in the BWP handover scenario can be determined in the same way as in the same BWP scenario, reducing the processing complexity of the terminal device.

[0296] Below, we will introduce in detail the various possible implementation methods for the start time of the first duration.

[0297] In the first possible implementation, the start time of the first duration is the next time slot after the BWP handover delay.

[0298] For example, Figure 11 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 11 As shown, the black-filled squares represent the PDCCH listening opportunities that the terminal device can monitor. The network equipment is configured with DL BWP 1 and DL BWP 2 in a cell. DL BWP 1 has a subcarrier spacing of 30kHz and a BWP handover delay of 2 time slots. DL BWP 2 has a subcarrier spacing of 60kHz, a first duration of 6 time slots, and a time slot offset K0 between the PDCCH carrying the second DCI and the PDSCH scheduled by the second DCI, which can be 5 time slots. It should be understood that K0 is greater than or equal to the BWP handover delay. It should also be understood that different subcarrier spacings correspond to different time slot lengths. The length of the time slots included in the first duration and K0 is the time slot length corresponding to the subcarrier spacing of the BWP after handover, i.e., the time slot length corresponding to a subcarrier spacing of 60kHz. The length of the time slots included in the BWP handover delay is the time slot length corresponding to a subcarrier spacing of 30kHz. It should also be understood that the first duration, K0, and the number of time slots included in the BWP handover delay are merely examples, and the embodiments of this application do not limit this.

[0299] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The terminal device detects that the BWP indication field in the second DCI indicates DL BWP 2. The second DCI instructs the terminal device to stop listening to the PDCCH within a first duration, and the second DCI is used to schedule the transmission of PDSCH, such as... Figure 11 As shown, based on the second DCI, after a time slot offset of K0 (5 time slots), the terminal device transmits PDSCH on DL BWP 2. The terminal device stops listening to PDCCH starting from the next time slot after the BWP handover delay, and starts listening to PDCCH after the first duration (6 time slots). Alternatively, "after a time slot offset of K0 (5 time slots)" can be replaced with "after a time slot offset of K0 (5 time slots), the terminal device transmits PDSCH on DL BWP 2 based on the second DCI, after a time slot offset of K0 (5 time slots), and then transmits PDSCH in the time slot corresponding to the time slot offset of K0."

[0300] In the second possible implementation, the start time of the first duration is the time slot in which the PDSCH is transmitted on the DL BWP after the handover.

[0301] For example, Figure 12 This diagram illustrates another method for stopping PDCCH monitoring. (See diagram for example.) Figure 12 As shown, the black-filled squares represent the PDCCH listening opportunities that the terminal device can monitor. The network device is configured with DL BWP1 and DL BWP2 in a cell. The subcarrier spacing of DL BWP1 can be 30kHz, and the BWP handover delay can be 2 time slots. The subcarrier spacing of DL BWP2 can be 60kHz, the first duration can be 6 time slots, and the time slot offset K0 between the PDCCH carrying the second DCI and the PDSCH scheduled by the second DCI can be 5 time slots. It should be understood that K0 is greater than the BWP handover delay. It should also be understood that different subcarrier spacings correspond to different time slot lengths. The length of the time slots included in the first duration and K0 is the time slot length corresponding to a subcarrier spacing of 60kHz, and the length of the time slots included in the BWP handover delay is the time slot length corresponding to a subcarrier spacing of 30kHz. It should also be understood that the first duration, K0, and the number of time slots included in the BWP handover delay are merely examples, and this application embodiment does not limit this.

[0302] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The terminal device detects that the BWP indication field in the second DCI indicates DL BWP 2. The second DCI instructs the terminal device to stop listening to the PDCCH within a first duration, and the second DCI is used to schedule the transmission of PDSCH, such as... Figure 12 As shown, based on the second DCI, after a time slot offset of K0 (5 time slots), the terminal device transmits PDSCH on DL BWP 2. The terminal device stops listening to PDCCH in the time slot corresponding to the PDSCH transmission on DL BWP 2, and after a first duration (6 time slots), it starts listening to PDCCH again. Alternatively, "after a time slot offset of K0 (5 time slots)" can be replaced with "after a time slot offset of K0 (5 time slots), the terminal device, based on the second DCI, transmits PDSCH on DL BWP 2 after a time slot offset of K0 (5 time slots), and the terminal device stops listening to PDCCH in the time slot corresponding to the PDSCH transmission on DL BWP 2."

[0303] If the PDSCH scheduled by the second DCI occupies multiple time slots, the start time of the first duration is the beginning of the first time slot occupied by the PDSCH. The data transmitted by the PDSCH occupying multiple time slots can be repeatedly sent within the same transport block or in different transport blocks.

[0304] In the third possible implementation, the start time of the first duration is the next time slot after the time slot in which the PDSCH is transmitted on the switched DL BWP.

[0305] For example, Figure 13 This illustrates yet another method for stopping PDCCH monitoring. (Example) Figure 13 As shown, the black-filled squares represent the PDCCH listening opportunities that the terminal device can monitor. In a cell, the network device is configured with DL BWP1 and DL BWP2. The subcarrier spacing of DL BWP1 can be 30kHz, in which case the BWP handover delay can be 2 time slots 1. The subcarrier spacing of DL BWP2 can be 60kHz, in which case the first duration can be 6 time slots 2. The time slot offset K0 between the PDCCH carrying the second DCI and the PDSCH scheduled by the second DCI can be 5 time slots 2. It should be understood that K0 is greater than the BWP handover delay. Different subcarrier spacings correspond to different time slot lengths. The length of the time slots included in the first duration and K0 is the time slot length corresponding to a subcarrier spacing of 60kHz. The length of the time slots included in the BWP handover delay is the time slot length corresponding to a subcarrier spacing of 30kHz. It should also be understood that the first duration, K0, and the number of time slots included in the BWP handover delay are merely examples, and this application embodiment does not limit this.

[0306] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The terminal device detects that the BWP indication field in the second DCI indicates DL BWP 2. The second DCI instructs the terminal device to stop listening to the PDCCH within a first duration, and the second DCI is used to schedule the transmission of PDSCH, such as... Figure 13 As shown, based on the second DCI, after a time slot offset of K0 (5 time slots), the terminal device transmits PDSCH on DL BWP 2. The terminal device stops listening to PDCCH in the time slot following the time slot in which the PDSCH is transmitted on DL BWP 2. After a first duration (6 time slots), it starts listening to PDCCH. Alternatively, "after a time slot offset of K0 (5 time slots)" can be replaced with "after a time slot offset of K0 (5 time slots), the terminal device transmits PDSCH on DL BWP 2 based on the second DCI, after a time slot offset of K0 (5 time slots), the terminal device transmits PDSCH in the time slot corresponding to time slot offset K0, and the terminal device stops listening to PDCCH in the time slot following the time slot in which the PDSCH is transmitted on DL BWP 2."

[0307] If the PDSCH scheduled by the second DCI occupies multiple time slots, the start time of the first duration is the next time slot after the first time slot occupied by the PDSCH, or the next time slot after the end of the multiple time slots occupied by the PDSCH. The data transmitted by the PDSCH occupying multiple time slots can be repeatedly transmitted within the same transport block or in different transport blocks.

[0308] In the fourth possible implementation, the time offset between the start time of the first duration and the second DCI.

[0309] The time offset between the start time of the first duration and the second DCI can be predefined or configured by the network device via RRC signaling.

[0310] The time offset between the start time of the first duration and the second DCI can be predefined. The unit of the time offset between the start time of the first duration and the second DCI can be a symbol or a time slot.

[0311] Different BWPs can have different subcarrier spacings. The protocol can predefine different time offsets corresponding to different subcarrier spacings, or the protocol can predefine different subcarrier spacings corresponding to the same time offset. The time offset between the start time of the first duration and the second DCI can be based on the time slot offset corresponding to the subcarrier spacing of the currently active DL BWP, or based on the time slot offset corresponding to the subcarrier spacing of the DL BWP after the handover.

[0312] For example, the time offset between the start time of the first duration and the second DCI can be greater than or equal to 0.

[0313] For example, the protocol can predefine different subcarrier intervals corresponding to the same time offset. Table 1 shows one such correspondence between subcarrier intervals and time offsets.

[0314] Table 1

[0315] Subcarrier spacing μ (kHz) Time offset (symbol) 15 25 30 25 60 25 120 25

[0316] As shown in Table 1, the subcarrier spacing can be 15kHz, 30kHz, 60kHz and 120kHz. Different subcarrier spacings can correspond to the same time offset, that is, 25 symbols.

[0317] For example, the protocol can predefine different subcarrier intervals corresponding to different time offsets. Table 2 shows one such correspondence between subcarrier intervals and time offsets.

[0318] Table 2 shows another correspondence between subcarrier spacing and time offset.

[0319] Table 2

[0320] Subcarrier spacing μ (kHz) Time offset (symbol) 15 10 30 12 60 22 120 25

[0321] As shown in Table 2, the subcarrier spacing can be 15kHz, 30kHz, 60kHz, and 120kHz. Different subcarrier spacings correspond to different time offsets. When the subcarrier spacing is 15kHz, the time offset can be 10 symbols; when the subcarrier spacing is 30kHz, the time offset can be 12 symbols; when the subcarrier spacing is 60kHz, the time offset can be 22 symbols; and when the subcarrier spacing is 120kHz, the time offset can be 25 symbols.

[0322] The time offsets shown in Tables 1 and 2 above are in units of signs; time offsets can also be in units of time slots.

[0323] For example, Table 3 shows another correspondence between subcarrier spacing and time offset.

[0324] Table 3

[0325] Subcarrier spacing μ (kHz) Time offset (time slot) 15 1 30 1 60 2 120 2

[0326] As shown in Table 2, the subcarrier spacing can be 15kHz, 30kHz, 60kHz and 120kHz. When the subcarrier spacing is 15kHz or 30kHz, the time offset can be 1 time slot; when the subcarrier spacing is 60kHz or 120kHz, the time offset can be 2 time slots.

[0327] It should be understood that the correspondence between subcarrier spacing and time offset shown in Tables 1, 2 and 3 above is merely an example, and the embodiments of this application do not limit it.

[0328] The start time of the first duration can be determined based on the time offset between the start time of the first duration and the start of the symbol occupied by the second DCI, or the start time of the first duration can be determined based on the time offset between the start time of the first duration and the time offset after the symbol occupied by the second DCI. If the time determined based on the time offset is not the start of a time slot, the start time of the first duration can be the start of the next time slot of the time offset.

[0329] For example, the second DCI occupies 3 symbols, the time offset between the start time of the first duration and the second DCI is 25 symbols, the first symbol occupied by the second DCI can be the first symbol of 25 symbols, or the fourth symbol after the third symbol occupied by the second DCI is the first symbol of 25 symbols.

[0330] The starting time of the first duration can be determined based on the time offset between the starting time of the first duration and the start of the time slot where the second DCI is located, or the starting time of the first duration can be determined based on the time offset between the starting time of the first duration and the time slot where the second DCI is located.

[0331] For example, the second DCI occupies one time slot, the time offset between the start time of the first duration and the second DCI is one time slot, the time slot occupied by the second DCI can be a time slot with time offset, or the next time slot of the time slot where the second DCI is located is a time slot with time offset.

[0332] In the fifth possible implementation, the terminal device can determine the start time of the first duration based on the maximum value between the minimum timeslot offset and the duration of parsing the second DCI. The minimum timeslot offset is the minimum timeslot offset between the PDCCH carrying the second DCI and the PDSCH that the second DCI is allowed to schedule.

[0333] Minimum time slot offset can be represented by K 0min K indicates 0min The value of can be greater than or equal to 0. The maximum value between the minimum time slot offset and the duration of resolving the second DCI can be expressed as max(K). 0min The duration of parsing the second DCI is Z. For a specific subcarrier interval, Z is a constant. The value of Z can be found in Table 3 above.

[0334] Optionally, in cross-carrier scheduling scenarios, the terminal device can use the formula... Determine the time offset between the start time of the first duration and the second DCI. Where K... 0min For the activated DL BWP of the tuned cell, the valid K 0min Z μ The value of μ corresponding to the activation DL BWP of the main cell (Z) μ The values ​​can be found in Table 3 above. μPDCCH is the subcarrier spacing parameter of the active DL BWP of the master cell, and μPDSCH is the subcarrier spacing parameter of the active DL BWP of the modulated cell.

[0335] The above implementation method can ensure that the terminal device can parse the information of the second DCI before stopping listening to the PDCCH, which is beneficial to improving the communication efficiency between the terminal device and the network device.

[0336] In the sixth possible implementation, the start time of the first duration is after the HARQ feedback corresponding to the second DCI scheduling PDSCH.

[0337] HARQ feedback can include acknowledgment (ACK) feedback or nonacknowledgment (NACK) feedback.

[0338] After receiving the PDSCH, the terminal device also sends an ACK or NACK feedback. The start time of the first duration can be after the terminal device sends an ACK or NACK feedback. The second DCI can indicate the time slot where the HARQ feedback occurs.

[0339] Optionally, the start time of the first duration can be the beginning of the time slot in which the terminal device transmits ACK or NACK, or the beginning of the next time slot. The start time of the first duration can be the beginning or the end of the symbol in which the terminal device transmits ACK or NACK.

[0340] Optionally, the terminal device will stop listening to the PDCCH for a first duration only when it sends an ACK. The start time of the first duration can be after the terminal device sends the ACK. Optionally, the start time of the first duration can be the beginning of the time slot in which the terminal device transmits the ACK or the beginning of the next time slot. The start time of the first duration can be the beginning or the end of the symbol in which the terminal device transmits the ACK.

[0341] In the above implementation, the terminal device stops listening to the PDCCH after transmitting the PDSCH, which is beneficial for the terminal device and the network device to communicate.

[0342] Optionally, the start time of the first duration may also be a later time determined by at least two of the first to sixth possible implementations. For example, the start time of the first duration may be a later time determined by at least one of the first to third possible implementations and at least one of the fourth to sixth possible implementations.

[0343] For example, the start time of the first duration is determined by comparing the BWP handover delay in the first possible implementation with the time offset in the fourth possible implementation, and the larger of the two is used. As another example, the start time of the first duration is determined by comparing the BWP handover delay in the first possible implementation with the maximum value between the minimum timeslot offset in the fifth possible implementation and the duration of parsing the second DCI, and the larger of the two is used. As another example, the start time of the first duration is determined by comparing the BWP handover delay in the first possible implementation with the ACK or NACK feedback time in the sixth possible implementation, and the larger of the two is used. As yet another example, the start time of the first duration is determined by comparing the timeslot offset K0 of the PDSCH indicated by the second DCI in the second possible implementation (used to indicate the timeslot in which the PDSCH is transmitted on the DL BWP after handover) with the time offset in the fourth possible implementation, and the larger of the two is used. For example, the time slot offset K0 of the PDSCH indicated by the second DCI in the second possible implementation (used to indicate the time slot in which the PDSCH is transmitted on the DL BWP after the handover) is compared with the maximum value between the minimum time slot offset and the duration of parsing the second DCI in the fifth possible implementation, and the start time of the first duration is determined according to the larger of the two. For example, the time slot offset K0 of the PDSCH indicated by the second DCI in the second possible implementation is compared with the ACK or NACK feedback time in the sixth possible implementation, and the start time of the first duration is determined according to the larger of the two. Typically, the symbol position for transmitting ACK or NACK is after the symbol position for transmitting PDSCH, and the time slot for transmitting ACK or NACK can be in the same time slot as the time slot for transmitting PDSCH, or in a different time slot.

[0344] When the start time of the first duration is after the end time of the BWP handover delay, or after the start time of the first duration is after the time slot in which the PDSCH scheduled by the second DCI is transmitted on the DL BWP after the handover, the behavior of the terminal device listening to the PDCCH after the BWP handover delay and before the start time of the first duration may include:

[0345] If no SSSG is configured on the switched-over BWP, the terminal device will listen to the PDCCH according to the configured SSset on the switched-over BWP.

[0346] When an SSSG is configured on the BWP after handover, the terminal device listens to the PDCCH based on the SS set in one of the SSSGs. For example, if the network device is configured with SSSGs on the BWP after handover, there can be two SSSGs: SSSG0 (SSSG index 0) and SSSG1 (SSSG index 1). The terminal device can listen to the PDCCH based on the SS set of SSSG0 or the SS set of SSSG1.

[0347] Optionally, the number of SSSGs can be 3, namely SSSG0 (i.e., SSSG index is 0), SSSG1 (i.e., SSSG index is 1) and SSSG2 (i.e., SSSG index is 2). The terminal device can listen to the PDCCH according to the SS set of SSSG0, the SS set of SSSG1 or the SS set of SSSG2.

[0348] One possible approach is to configure an SSSG on the new BWP. On the new BWP, the terminal device listens to the PDCCH according to the SS set of the SSSG as specified in the protocol. The SSSG can be SSSG0, SSSG1, or SSSG2. For example, if an SSSG is configured on the new BWP, the protocol stipulates that the terminal device listens to the PDCCH on the new BWP according to the SS set of SSSG0. Another possible approach is for the network device to configure an SSSG as the SSSG for the terminal device to listen to the PDCCH on the new BWP. For example, if the network device configures SSSG0, then the terminal device listens to the PDCCH on the new BWP according to the SS set of SSSG0. Since the terminal device listens to the PDCCH from the time slot where the PDSCH scheduled by the second DCI is located on the BWP after the handover, the terminal device's behavior of listening to the PDCCH after the BWP handover delay and before the start of the first duration can include the above method. It can also be understood that the terminal device's behavior of listening to the PDCCH from the time slot where the PDSCH scheduled by the second DCI is located and before the start of the first duration can include the above method.

[0349] For example, Figure 16 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 16As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with DL BWP 1 and DL BWP 2 in a cell. The subcarrier spacing of DL BWP 1 can be 30kHz, and the BWP handover delay can be 2 time slots. The subcarrier spacing of DL BWP 2 can be 60kHz, and the time slot offset K0 between the PDCCH carrying the second DCI and the PDSCH scheduled by the second DCI can be 4 time slots. It should be understood that K0 can be greater than or equal to the BWP handover delay. It should also be understood that different subcarrier spacings correspond to different time slot lengths. The length of the time slots included in the first duration and K0 is the time slot length corresponding to the subcarrier spacing of the BWP after handover, i.e., the time slot length corresponding to a subcarrier spacing of 60kHz, and the length of the time slots included in the BWP handover delay is the time slot length corresponding to a subcarrier spacing of 30kHz. It should also be understood that the first duration, K0, and the number of time slots included in the BWP handover delay are merely examples, and this application embodiment does not limit this.

[0350] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The terminal device detects that the BWP indication field in the second DCI indicates DL BWP 2 and instructs to stop listening to the PDCCH within the first duration. Simultaneously, the second DCI is used to schedule the transmission of PDSCH. Furthermore, the terminal device needs to send an ACK or NACK response to the network device. The first duration begins after the ACK or NACK response duration. It should be understood that ACK or NACK in the diagram only indicates that the timing is after PDSCH, and does not mean that ACK or NACK is on the same BWP as PDSCH.

[0351] like Figure 16 As shown, based on the second DCI, after the BWP handover delay (2 time slots), the terminal device transmits PDSCH on DL BWP 2 and provides ACK or NCK feedback.

[0352] Without SSSG configured on DL BWP 2, the terminal device can listen to PDCCH according to the configured SS set after the BWP handover delay and before the start of the first duration.

[0353] For the above method 1000, if the parameters of the SSSG switching mechanism and / or the parameters of the skip PDCCH listening mechanism are not configured on the activated DL BWP, and there is no bit field in the above second DCI for indicating SSSG switching and / or skipping PDCCH listening within the first duration, then the above second DCI can be used to indicate DL BWP switching, but not for indicating SSSG switching and / or skipping PDCCH listening within the first duration.

[0354] The terminal device receives the second DCI on the activated DL BWP, performs DL BWP switching, and listens for PDCCH on the switched DL BWP.

[0355] The terminal device listens to the PDCCH on the switched DL BWP, including:

[0356] If no SSSG is configured on the switched-over BWP, the terminal device will listen to the PDCCH according to the configured SSset on the switched-over BWP.

[0357] When an SSSG is configured on the switched-over BWP, the terminal device listens to the PDCCH based on the SS set in one of the SSSGs. For example, if the network device is configured with SSSGs on the switched-over BWP, there can be two SSSGs, namely SSSG0 and SSSG1. The terminal device can listen to the PDCCH based on the SS set of SSSG0 or the SS set of SSSG1.

[0358] Optionally, the number of SSSGs can be 3, namely SSSG0, SSSG1 and SSSG2. The terminal device can listen to the PDCCH according to the SS set of SSSG0, the SS set of SSSG1 or the SS set of SSSG2.

[0359] One possible approach is to configure an SSSG on the new BWP. On the new BWP, the terminal device listens to the PDCCH according to the SS set of the SSSG as specified in the protocol. The SSSG can be SSSG0, SSSG1, or SSSG2. For example, if an SSSG is configured on the new BWP, the protocol stipulates that the terminal device listens to the PDCCH on the new BWP according to the SS set of SSSG0. Another possible approach is for the network device to configure an SSSG as the SSSG for the terminal device to listen to the PDCCH on the new BWP. For example, if the network device configures SSSG0, then the terminal device listens to the PDCCH on the new BWP according to the SS set of SSSG0.

[0360] Optionally, the network device can send a third DCI to the terminal device on the currently active DL BWP. The third DCI can also carry PUSCH scheduling information. In a TDD scenario, the terminal device switches to the UL BWP in the third DCI indication field based on the third DCI, and at the same time switches the DL BWP. That is, the terminal device switches both the UL BWP and the DL BWP simultaneously. The terminal device stops listening to the PDCCH within a first duration based on the third DCI instruction, and stops listening to the PDCCH on the DL BWP after handover. Simultaneously, the start time of the first duration is determined according to at least one of the following methods: the next time slot after the UL BWP handover delay; the time slot on the UL BWP where the PUSCH is transmitted; the next time slot on the UL BWP where the PUSCH is transmitted; the time offset between the start time of the first duration and the third DCI; the maximum value between the minimum time slot offset and the duration of parsing the third DCI (the description of the duration of parsing the third DCI refers to the duration of parsing the second DCI); or, after the third DCI schedules the PUSCH and the PUSCH is transmitted; or, after the uplink retransmission timer (UL retransmissiontimer) in C-DRX ends. Optionally, at least two of these methods can be compared to determine the later time as the start time of the first duration, as described in the previous paragraph, and will not be repeated here.

[0361] The BWP indication field in the third DCI indicates the identifier of the UL BWP (UL BWP 2), which is different from the identifier of the currently active UL BWP (UL BWP 1). According to the third DCI, network devices and terminal devices can switch from the currently active UL BWP 1 to UL BWP 2, treating UL BWP 2 as the newly active UL BWP. The terminal device receives the PUSCH scheduled by the third DCI on UL BWP 2.

[0362] In TDD scenarios, UL BWP and DL BWP are associated. DL BWP and UL BWP with the same identifier have the same center frequency. Therefore, in TDD scenarios, when UL BWP switches, DL BWP also switches accordingly. That is, when a terminal device switches from UL BWP 1 to UL BWP 2, the terminal device can also switch from DL BWP 1 to DL BWP 2.

[0363] In a TDD scenario, the terminal device can determine the start time of the first duration based on at least one of the following information: the next time slot after the UL BWP handover delay, the time slot in which the PUSCH is transmitted on the UL BWP after the handover, the next time slot in which the PUSCH is transmitted on the UL BWP after the handover, the time offset between the start time of the first duration and the third DCI, the maximum value between the minimum time slot offset and the duration of parsing the third DCI, the third DCI scheduling of the PUSCH, and the PUSCH transmission.

[0364] Optionally, if the terminal device is configured with a Search Space Group (SSSG) handover mechanism, when the second or third DCI indicates SSSG handover (i.e., the second or third DCI instructs the terminal device to listen to the PDCCH according to one of the search space groups and instructs the BWP to handover), the method in method 1000 above also applies. The start time of the first duration is the time when the SSSG indicated by the second or third DCI begins to take effect on the DL BWP after handover. It can be understood that the start time of SSSG (or the effective time of SSSG), that is, the start time when the terminal device listens to the PDCCH according to the SSSG indicated by the second or third DCI on the DL BWP after handover, can be determined according to the method in method 1000 above. The difference is that the start time of the first duration is replaced with the effective time of SSSG, which will not be elaborated further. Optionally, the implementation method of the start time of the terminal device listening to the PDCCH according to the SSSG indicated by the second or third DCI on the DL BWP after handover (which can be simply referred to as the start time of SSSG) can be different from the implementation method of determining the start time of the first duration.

[0365] The aforementioned second or third DCI can indicate SSSG handover and BWP handover. When the start time of SSSG is after the end time of BWP handover delay, or when the start time of SSSG is after the time slot where PDSCH is scheduled by the second DCI, the behavior of the terminal device listening to PDCCH after the BWP handover delay and before the start time of SSSG can be that the terminal device listens to PDCCH according to the SS set in one of the SSSGs.

[0366] For example, the network device is configured with SSSG on the BWP after the handover. There can be two SSSGs, namely SSSG0 (i.e., SSSG index is 0) and SSSG1 (i.e., SSSG index is 1). The terminal device can listen to PDCCH according to the SS set of SSSG0 or the SS set of SSSG1.

[0367] Optionally, the number of SSSGs can be 3, namely SSSG0 (i.e., SSSG index is 0), SSSG1 (i.e., SSSG index is 1) and SSSG2 (i.e., SSSG index is 2). The terminal device can listen to the PDCCH according to the SS set of SSSG0, the SS set of SSSG1 or the SS set of SSSG2.

[0368] One possible approach is to configure an SSSG on the new BWP. On the new BWP, the terminal device listens to the PDCCH according to the SS set of the SSSG as specified in the protocol. The SSSG can be SSSG0, SSSG1, or SSSG2. For example, if an SSSG is configured on the new BWP, the protocol stipulates that the terminal device listens to the PDCCH on the new BWP according to the SS set of SSSG0. Another possible approach is for the network device to configure an SSSG as the SSSG for the terminal device to listen to the PDCCH on the new BWP. For example, if the network device configures SSSG0, then the terminal device listens to the PDCCH on the new BWP according to the SS set of SSSG0.

[0369] Since the terminal device listens to the PDCCH starting from the time slot where the PDSCH scheduled by the second DCI is located on the BWP after the handover, the terminal device's behavior of listening to the PDCCH after the BWP handover delay and before the SSSG takes effect can include the above method. It can also be understood that the terminal device's behavior of listening to the PDCCH starting from the time slot where the PDSCH scheduled by the second DCI is located and before the SSSG takes effect can include the above method. For example, Figure 17 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 17 As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with DL BWP 1 and DL BWP2 in a cell. The subcarrier spacing of DL BWP 1 can be 30kHz, and the BWP handover delay can be 2 time slots. The subcarrier spacing of DL BWP 2 can be 60kHz, and the time slot offset K0 between the PDCCH carrying the second DCI and the PDSCH scheduled by the second DCI can be 4 time slots. It should be understood that K0 is equal to the BWP handover delay. It should also be understood that different subcarrier spacings correspond to different time slot lengths. The length of the time slots included in K0 is the time slot length corresponding to the subcarrier spacing of the BWP after handover, i.e., the time slot length corresponding to a subcarrier spacing of 60kHz. The length of the time slots included in the BWP handover delay is the time slot length corresponding to a subcarrier spacing of 30kHz. It should also be understood that K0 and the number of time slots included in the BWP handover delay are merely examples, and this application embodiment does not limit this.

[0370] DL BWP 1 is the currently active BWP. The terminal device listens to the PDCCH on the active DL BWP 1. The terminal device detects that the BWP indication field in the second DCI indicates DL BWP 2, the second DCI instructs the terminal device to perform SSSG handover, and the second DCI is used to schedule PDSCH transmission. In addition, the terminal device needs to send ACK or NACK feedback to the network device. The start time of SSSG is after the ACK or NACK feedback duration.

[0371] like Figure 17 As shown, based on the second DCI, after the BWP handover delay (2 time slots), the terminal device transmits PDSCH on DL BWP 2 and sends ACK or NCK feedback, while simultaneously performing SSSG handover. DL BWP2 is configured with the SSSG mechanism. It should be understood that ACK or NACK in the diagram only indicates that the timing is after PDSCH, and does not mean that ACK or NACK is on the same BWP as PDSCH.

[0372] After the BWP handover delay and before the start time of the SSSG, the terminal device can listen to the PDCCH according to the SS set of one of the SSSGs.

[0373] Optionally, the terminal device involved in the above method 1000 can determine the start time of the first duration based on at least one of the following information: the time offset between the start time of the first duration and the first DCI, the maximum value between the minimum timeslot offset and the duration of parsing the first DCI, the first DCI scheduling PDSCH, the feedback of the Hybrid Automatic Repeat Request (HARQ) corresponding to the PDSCH, or the first DCI scheduling PUSCH, after the PUSCH transmission. This method is also applicable to the above methods 600 and 800, and will not be described again here.

[0374] Terminal devices can support skipping the PDCCH listening mechanism but not the SSSG switching mechanism, or they can support the SSSG switching mechanism but not skipping the PDCCH listening mechanism. Alternatively, terminal devices can support both skipping the PDCCH listening mechanism and the SSSG switching mechanism.

[0375] In the case of multiple DL BWPs, network devices can configure the same or different mechanisms on different DL BWPs for terminal devices.

[0376] For example, in the case of three DL BWPs, these three DL BWPs are DL BWP 1, DL BWP 2, and DL BWP 3. DL BWP 1, DL BWP 2, and DL BWP 3 can all support skipping the PDCCH listening mechanism but do not support the SSSG switching mechanism. Alternatively, DL BWP 1 supports skipping the PDCCH listening mechanism but does not support the SSSG switching mechanism, DL BWP 2 supports the SSSG switching mechanism but does not support skipping the PDCCH listening mechanism, and DL BWP 3 supports skipping the PDCCH listening mechanism and supports the SSSG switching mechanism.

[0377] Optionally, DL BWP may not support skipping the PDCCH listening mechanism and may not support the SSSG mechanism.

[0378] Terminal devices can report the mechanisms they support (skipping the PDCCH listening mechanism and / or the SSSG handover mechanism) to the network device explicitly or implicitly. The network device can then configure the terminal device according to the reported mechanisms. For example, the network device can configure the terminal device to skip the PDCCH listening mechanism and / or the SSSG handover mechanism via RRC signaling. This application does not limit the specific reporting method of the terminal device, nor does it limit the specific configuration method of the network device.

[0379] For example, the terminal device reports the supported mechanism to the network device as the skip PDCCH listening mechanism, and the network device can configure the terminal device to skip the PDCCH listening mechanism.

[0380] Once the supported mechanisms are determined for both network devices and terminal devices, the network devices can further instruct the behavior of the terminal devices through DCI.

[0381] In one possible implementation, the mechanism determined by the network device and the terminal device on the activated DL BWP is a skip PDCCH listening mechanism. The network device can instruct the terminal device's behavior through bit values ​​in the DCI. This can be understood as the network device configuring the skip PDCCH listening mechanism on the activated DL BWP for the terminal device.

[0382] For example, if the number of first durations T in the skipped PDCCH listening mechanism is one, the network device can instruct the terminal device's behavior according to the mapping relationship shown in Table 4. If the number of first durations T in the skipped PDCCH listening mechanism is greater than one (e.g., three), the network device can instruct the terminal device's behavior according to the mapping relationship shown in Table 5. Different first durations T can be represented by subscript numbers, such as T1, T2, and T3, etc. The network device can configure one or more first durations to the terminal device via RRC signaling. The tables described are merely examples; the mapping relationship between bits in the DCI and the terminal device's behavior can also take other forms, and this invention is not limited thereto.

[0383] Table 4

[0384]

[0385]

[0386] Table 5

[0387]

[0388] As shown in Table 4, the number of first durations T in the skip PDCCH listening mechanism is 1. The network device can use 1 bit in DCI to instruct the behavior of the terminal device. When the value of this 1 bit is 0, DCI is used to instruct the terminal device to listen to PDCCH (i.e. listen to PDCCH according to the configured SS set), which can also be understood as the terminal device not skipping PDCCH listening. When the value of this 1 bit is 1, DCI is used to instruct the terminal device to stop listening to PDCCH within the first duration.

[0389] As shown in Table 5, the number of first durations T in the skip PDCCH listening mechanism is equal to 3, and these 3 first durations are T1, T2, and T3 respectively. The network device can instruct the terminal device's behavior through 2 bits in the DCI. When the value of these 2 bits is 00, the DCI is used to instruct the terminal device to listen to the PDCCH (i.e., listen to the PDCCH according to the configured SS set). When the value of these 2 bits is 01, the DCI is used to instruct the terminal device to stop listening to the PDCCH within the first duration T1. When the value of these 2 bits is 10, the DCI is used to instruct the terminal device to stop listening to the PDCCH within the first duration T2. ​​When the value of these 2 bits is 11, the DCI is used to instruct the terminal device to stop listening to the PDCCH within the first duration T3. Optionally, when the network device does not configure the first duration T3, the value of 11 for the 2 bits is reserved and has no meaning.

[0390] In another possible implementation, the mechanism determined by the network device and the terminal device on the activated DL BWP is the SSSG handover mechanism. The network device can instruct the terminal device's behavior through bit values ​​in the DCI. This can be understood as the network device configuring the SSSG handover mechanism for the terminal device on this activated DL BWP.

[0391] For example, if the network device is configured with two SSSGs, the network device can instruct the behavior of the terminal device according to the mapping relationship shown in Table 6. If the network device is configured with three SSSGs, the network device can instruct the behavior of the terminal device according to the mapping relationship shown in Table 7.

[0392] Table 6

[0393]

[0394]

[0395] Table 7

[0396]

[0397] As shown in Table 6, the network device is configured with two SSSGs, namely SSG0 and SSSG1. The network device can use one bit in the DCI to instruct the behavior of the terminal device. When the value of this bit is 0, the DCI is used to instruct the terminal device to listen to the PDCCH in the SS set of SSSG0 and not to listen to the PDCCH in the SS set of SSSG1. When the value of this bit is 1, the DCI is used to instruct the terminal device to listen to the PDCCH in the SS set of SSSG1 and not to listen to the PDCCH in the SS set of SSSG0.

[0398] As shown in Table 7, the network device is configured with three SSSGs, namely SSG0, SSSG1, and SSSG2. The network device can use two bits in the DCI to instruct the behavior of the terminal device. When the value of these two bits is 00, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG0, but not in the SS sets of SSSG1 and SSSG2. When the value of these two bits is 01, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG1, but not in the SS sets of SSSG0 and SSSG2. When the value of these two bits is 10, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG2, but not in the SS sets of SSSG0 and SSSG1. The value of these two bits is 11, which is reserved.

[0399] In another possible implementation, the mechanism determined by the network device and the terminal device on the activated DL BWP is to skip the PDCCH listening mechanism and the SSSG handover mechanism. The network device can instruct the terminal device's behavior through bit values ​​in the DCI. This can be understood as the network device configuring the terminal device to skip the PDCCH listening mechanism and the SSSG handover mechanism on this activated DL BWP.

[0400] For example, the mechanism determined by the network device and the terminal device is to skip the PDCCH listening mechanism and the SSSG handover mechanism. The network device is configured with two SSSGs, namely SSSG0 and SSSG1, and the first duration T is one. The network device can instruct the behavior of the terminal device according to the mapping relationship shown in Table 8 or Table 9. Alternatively, the network device can be configured with two SSSGs, namely SSSG0 and SSSG1, and the first duration T is two. The network device can instruct the behavior of the terminal device according to the mapping relationship shown in Table 10 or Table 11.

[0401] Table 8

[0402]

[0403]

[0404] Table 9

[0405]

[0406] Table 10

[0407]

[0408] Table 11

[0409]

[0410] As shown in Table 8, network devices can use two bits in the DCI to instruct the behavior of terminal devices. When the value of these two bits is 00, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG0, but not in the SS set of SSSG1. When the value of these two bits is 01, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG1, but not in the SS set of SSSG0. When the value of these two bits is 10, the DCI instructs the terminal device to stop listening to the PDCCH within the first duration T. The terminal device can remain in the current SSSG without switching SSSGs. The value of these two bits is 11, which is reserved.

[0411] As shown in Table 9, network devices can use two bits in the DCI to instruct the behavior of terminal devices. When the value of these two bits is 00, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG0, but not in the SS set of SSSG1. When the value of these two bits is 01, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG1, but not in the SS set of SSSG0. When the value of these two bits is 10, the DCI instructs the terminal device to switch to or remain in SSSG0 and stop listening to the PDCCH within a first duration T. When the value of these two bits is 11, the DCI instructs the terminal device to switch to or remain in SSSG1 and stop listening to the PDCCH within a first duration T.

[0412] As shown in Table 10, network devices can use two bits in the DCI to instruct the behavior of terminal devices. When the value of these two bits is 00, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG0 and not to listen to the PDCCH in the SS set of SSSG1. When the value of these two bits is 01, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG1 and not to listen to the PDCCH in the SS set of SSSG0. When the value of these two bits is 10, the DCI instructs the terminal device to switch to or remain in SSSG0 and stop listening to the PDCCH within the first duration T1. When the value of these two bits is 11, the DCI instructs the terminal device to switch to or remain in SSSG0 and stop listening to the PDCCH within the first duration T2.

[0413] As shown in Table 11, network devices can use two bits in the DCI to instruct the behavior of terminal devices. When the value of these two bits is 00, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG0, but not in the SS set of SSSG1. When the value of these two bits is 01, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG1, but not in the SS set of SSSG0. When the value of these two bits is 10, the DCI instructs the terminal device to stop listening to the PDCCH within the first duration T1, and the terminal device can remain in the current SSSG without switching SSSGs. When the value of these two bits is 11, the DCI instructs the terminal device to stop listening to the PDCCH within the first duration T2, and the terminal device can remain in the current SSSG without switching SSSGs.

[0414] For example, the mechanism determined by the network device and the terminal device is to skip the PDCCH listening mechanism and the SSSG switching mechanism, and the number of SSSGs configured by the network device is 3, namely SSSG0, SSSG1 and SSSG2, with a first duration of T. The network device can instruct the behavior of the terminal device according to any of the mapping relationships shown in Table 12.

[0415] Table 12

[0416]

[0417] As shown in Table 12, network devices can use two bits in the DCI to instruct the behavior of terminal devices. When the value of these two bits is 00, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG0, but not in the SS sets of SSSG1 and SSSG2. When the value of these two bits is 01, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG1, but not in the SS sets of SSSG0 and SSSG2. When the value of these two bits is 10, the DCI instructs the terminal device to listen to the PDCCH in the SS set of SSSG2, but not in the SS sets of SSSG0 and SSSG1. When the value of these two bits is 11, the DCI instructs the terminal device to stop listening to the PDCCH within the first duration T. The terminal device can remain in the current SSSG without switching SSSGs.

[0418] In this embodiment of the application, 1 bit or 2 bits in the mapping relationship shown in Tables 4 to 12 above are referred to as the "first field". This embodiment of the application does not limit the name.

[0419] In methods 600, 800, and 1000, the behavior of the terminal device on the BWP after handover can be determined based on the mapping relationship between the value of the first field in the DCI and the first field in the BWP after handover.

[0420] For example, in methods 600, 800 and 1000, the terminal device supports skipping the PDCCH listening mechanism. The terminal device can determine the behavior of the terminal device corresponding to the value of the first field in the second DCI or the third DCI in Tables 4 to 12, respectively, and thus determine the behavior on the BWP after the handover, that is, stop listening to PDCCH at the start time of the first duration or listen to PDCCH at the start time of SSSG according to the SSSG indicated by the second DCI or the third DCI.

[0421] Optionally, when a terminal device listens to the PDCCH on the switched BWP, the network device can send a DCI on the switched BWP to instruct the terminal device's behavior, i.e., instruct the terminal device to switch the SSSG and / or skip PDCCH listening. The terminal device can perform corresponding actions based on the received DCI.

[0422] Optionally, based on the first domain mentioned above, the behavior of the terminal device listening to the PDCCH after the BWP handover delay and before the start of the first duration or the start of the SSSG can be assumed to be the behavior of the terminal device corresponding to "0" or "00" in the mapping relationship of the first domain in the DCI. The mapping relationship of the first domain can be understood as stipulated in the aforementioned protocol.

[0423] Optionally, the network device configures a timer for the terminal device to perform BWP handover. When the timer expires, the terminal device performs DL BWP handover, and correspondingly, the network device can also perform DL BWP handover. On the switched DL BWP, the default behavior of the terminal device listening to the PDCCH can be the behavior of the terminal device corresponding to "0" or "00" in the mapping relationship of the first field in DCI.

[0424] Optionally, in the above method 1000, if the second or third DCI does not have a first field, but can indicate BWP switching, the terminal device performs DL BWP switching based on the second or third DCI. On the switched DL BWP, the default behavior of the terminal device listening to PDCCH can be the behavior of the terminal device corresponding to "0" or "00" in the mapping relationship of the first field in the DCI.

[0425] Terminal devices can simultaneously support skipping the PDCCH listening mechanism and the SSSG handover mechanism. Network devices can use a DCI to simultaneously instruct the terminal device to stop listening to the PDCCH within a first duration and instruct the terminal device to perform an SSSG handover.

[0426] For example, Figure 18 This is a schematic flowchart illustrating another method 1800 for stopping PDCCH monitoring provided in an embodiment of this application. Method 1800 can be applied to... Figure 5 The communication system 500 shown is not limited to this embodiment. Figure 18 As shown, the method 1800 may include the following steps:

[0427] S1801. The network device sends a fourth DCI to the terminal device on the activated DL BWP. The fourth DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration and to instruct the SSSG to be switched. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's private search space set. Correspondingly, the terminal device receives the fourth DCI on the activated DL BWP.

[0428] The fourth DCI can instruct the terminal device to switch to the first search space set. For example, the fourth DCI can instruct the terminal device to switch to SSSG0, SSSG1, or SSSG2.

[0429] The terminal device can currently listen to the PDCCH in the SS set of SSSG0, the SS set of SSSG1, or the SS set of SSSG2. This embodiment does not limit the specific implementation. If the SSSG currently used by the terminal device is the same as the SSSG indicated by the fourth DCI, it means that the SSSG used by the terminal device has not been switched.

[0430] S1802. The terminal device determines the start time of the first duration and the start time of the SSSG based on the fourth DCI, and stops listening to the PDCCH within the first duration and listens to the PDCCH according to the SSSG indicated by the fourth DCI at the start time of the SSSG.

[0431] S1803, The network device determines the start time of the first duration and the start time of the SSSG.

[0432] S1802 and S1803 are not distinguished by any order.

[0433] Network devices do not send PDCCH during the first duration, and may send PDCCH on the SSSG indicated by the fourth DCI after the start time of the SSSG.

[0434] The method by which network devices determine the start time of the first duration and the start time of the SSSG can be the same as the method by which terminal devices determine the start time of the first duration and the start time of the SSSG.

[0435] Optionally, in a scenario with multiple DL BWPs, the fourth DCI can simultaneously instruct the cessation of PDCCH monitoring, SSSG switching, and BWP switching within the first duration.

[0436] If the second DCI in the above method 1000 adds the function of indicating the switching of SSSG, it can be understood as being the same as the fourth DCI.

[0437] There are several possible implementations for the terminal device to determine the start time of the first duration and the start time of the SSSG.

[0438] In one possible implementation, the terminal device first determines the start time of the first duration. The terminal device can determine the start time of the first duration according to the implementation method described in method 1000 above. Then, after the first duration, the terminal device listens for the PDCCH according to the SS set of the SSSG indicated by the DCI (e.g., the fourth DCI mentioned above). This can be understood as follows: before the end of the first duration, the terminal device remains in the current SSSG; after the first duration, the terminal device listens for the PDCCH according to the SS set of the SSSG indicated by the fourth DCI. Correspondingly, the network device can determine the start time of the first duration using the same implementation method, and after the first duration, the network device can send the PDCCH to the terminal device according to the SS set of the SSSG indicated by the fourth DCI. It should be understood that in this method, the start time of the SSSG is the time after the first duration. Alternatively, it can be understood that the start time of the SSSG is the next time slot or symbol after the first duration.

[0439] Specifically, the methods for determining the start time of the first duration can include:

[0440] 1) The time offset between the start time of the first duration and the fourth DCI;

[0441] 2) The start time of the first duration is the maximum value between the minimum time slot offset and the duration of parsing the fourth DCI. The minimum time slot offset is the minimum time slot offset between the PDCCH carrying the fourth DCI and the PDSCH that the fourth DCI is allowed to schedule.

[0442] 3) The fourth DCI schedules PDSCH, and the corresponding HARQ is fed back after PDSCH;

[0443] 4) The fourth DCI schedules PUSCH, either after PUSCH transmission or after the uplink retransmission timer (ULretransmission timer) in C-DRX ends.

[0444] For a detailed explanation of these four implementation methods, please refer to the descriptions of the fourth to sixth possible implementation methods mentioned above; they will not be repeated here.

[0445] Terminal devices and network devices can use at least one of these four methods to determine the start time of the first duration.

[0446] For example, Figure 19 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 19As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with SSSG0 and SSSG1 on the active DL BWP. The PDCCH listening time for the SS set of SSSG0 is in a period of one time slot, while the PDCCH listening time for the SS set of SSSG1 is in a period of two time slots. It should be understood that the PDCCH listening time for SSSG1 is sparser than that for SSSG0. The first duration can be six time slots.

[0447] The terminal device listens to the PDCCH on the active DL BWP and also listens to the PDCCH in the SS set of SSSG0. The network device instructs the terminal device to stop listening to the PDCCH within a first duration and instructs the terminal device to switch to SSSG1 via the PDCCH carrying the fourth DCI. The terminal device then listens to the PDCCH carrying the fourth DCI. Figure 19 As shown, the terminal device determines the start time of the first duration based on the fourth DCI, with a time offset of 1 time slot from the fourth DCI. During the first duration (6 time slots), the terminal device does not listen to the PDCCH. After the first duration, the terminal device listens to the PDCCH according to the SS set of SSSG1. During the first duration (6 time slots), the terminal device remains in SSSG0.

[0448] Optionally, in a multi-DL BWP scenario, the fourth DCI can simultaneously instruct the cessation of PDCCH listening, SSSG switching, and BWP switching within the first duration. The terminal device can first determine the start time of the first duration. On the switched BWP, the terminal device stops listening to PDCCH within the first duration. After the first duration, the terminal device listens to PDCCH according to the SS set of the SSSG indicated by the fourth DCI. On the switched BWP, before the end of the first duration, the terminal device can use one of the SSSGs, for example, it can be SSSG0 or an SSSG with the same index as the SSSG used by the terminal device on the BWP before the switch.

[0449] In another possible implementation, the start time of the first duration is the same as the start time of the SSSG. Specific methods may include: Method 1: determining the start time of the first duration and using it as the start time of the SSSG; or Method 2: determining the start time of the SSSG and using it as the start time of the first duration; or Method 3: determining the start time of the first duration and the start time of the SSSG separately, and using the later of the two as the start time of both the first duration and the SSSG.

[0450] The methods for determining the start time of the SSSG can include:

[0451] 1) The time offset between the start time of SSSG and the fourth DCI;

[0452] 2) The start time of SSSG is the maximum value between the minimum time slot offset and the time to parse the fourth DCI. The minimum time slot offset is the minimum time slot offset between the PDCCH carrying the fourth DCI and the PDSCH that the fourth DCI is allowed to schedule.

[0453] 3) The fourth DCI schedules PDSCH, and the corresponding HARQ is fed back after PDSCH;

[0454] 4) The fourth DCI schedules PUSCH, either after PUSCH transmission or after the uplink retransmission timer (ULretransmission timer) in C-DRX ends.

[0455] For example, Figure 20 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 20 As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with SSSG0 and SSSG1 on the active DL BWP. The PDCCH listening time for the SS set of SSSG0 is in a period of one time slot, while the PDCCH listening time for the SS set of SSSG1 is in a period of two time slots. It should be understood that the PDCCH listening time for SSSG1 is sparser than that for SSSG0. The first duration can be six time slots.

[0456] The terminal device listens to the PDCCH on the active DL BWP and also listens to the PDCCH in the SS set of SSSG0. The network device instructs the terminal device to stop listening to the PDCCH within a first duration and instructs the terminal device to switch to SSSG1 via the PDCCH carrying the fourth DCI. The terminal device then listens to the PDCCH carrying the fourth DCI. Figure 20 As shown, taking Method 1 as an example, the terminal device determines the start time of the first duration based on the fourth DCI, with a time offset of 1 time slot from the fourth DCI. This start time is then used as the start time of the SSSG. Both the start time of the first duration and the start time of the SSSG are offset by 1 time slot from the fourth DCI. The terminal device switches to SSSG1 at the start time of the first duration and stops listening to the PDCCH within the first duration (6 time slots). After the first duration (6 time slots), the terminal device listens to the PDCCH in the SS set of SSSG1. This can be understood as the terminal device being located in SSSG1 within the first duration (6 time slots).

[0457] Optionally, the specific implementation method in which the start time of the first duration and the start time of the SSSG are the same also includes method 3: the start time of the first duration can be determined by the above implementation method, and the start time of the SSSG can also be determined by the above implementation method. When the determined start time of the first duration is different from the determined start time of the SSSG, the later time of the two is selected as the start time of the first duration and the start time of the SSSG.

[0458] Optionally, in a multi-DL BWP scenario, the fourth DCI can simultaneously instruct the cessation of PDCCH monitoring, SSSG switching, and BWP switching within the first duration. The terminal device determines that the start time of the first duration and the start time of the SSSG are the same. Specific methods may include: Method 1: determining the start time of the first duration and using it as the start time of the SSSG; or Method 2: determining the start time of the SSSG and using it as the start time of the first duration; or Method 3: determining the start time of the first duration and the start time of the SSSG separately, and using the later of the two as the start time of both the first duration and the SSSG. The determination of the start time of the first duration and the determination of the start time of the SSSG can be referred to the explanation in Method 1000 above, and will not be repeated here.

[0459] For example, the implementation of determining the start time of the first duration or the start time of the SSSG may also include at least one of the following methods:

[0460] 1) The next time slot after the BWP handover delay;

[0461] 2) Transmit the time slot containing the PDSCH on the switched DL BWP;

[0462] 3) Transmit the next time slot of the time slot where PDSCH is located on the switched DL BWP.

[0463] The terminal device can determine the start time of the first duration and the start time of the SSSG using at least one of the three methods described above.

[0464] In another possible implementation, the start time of the first duration and the start time of the SSSG are determined separately. The start time of the first duration can be determined using the method described in method 1800 above, and the start time of the SSSG can also be determined using the method described in method 1800 above. The determined start time of the first duration and the determined start time of the SSSG can be different. For example, the start time of the first duration can be determined by the time offset between the start time of the first duration and the fourth DCI, and the start time of the SSSG can be determined by the HARQ feedback time corresponding to the PDSCH scheduled by the fourth DCI. The resulting start time of the first duration is different from the determined start time of the SSSG.

[0465] For example, Figure 21 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 21 As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with SSSG0 and SSSG1 on the active DL BWP. The PDCCH listening time for the SS set of SSSG0 is in a period of one time slot, while the PDCCH listening time for the SS set of SSSG1 is in a period of two time slots. It should be understood that the PDCCH listening time for SSSG1 is sparser than that for SSSG0. The first duration can be six time slots.

[0466] The terminal device listens to the PDCCH on the active DL BWP and also listens to the PDCCH in the SS set of SSSG0. The network device instructs the terminal device to stop listening to the PDCCH, switch to SSSG1, and schedule the PDSCH within a first duration via the PDCCH carrying the fourth DCI. The terminal device then listens to the PDCCH carrying the fourth DCI. Figure 21 As shown, the terminal device, based on the fourth DCI, determines that the start time of the first duration is offset from the time of the fourth DCI by one time slot. PDSCH is transmitted in the time slot where the start time of the first duration occurs. The terminal device also determines that the start time of SSSG is after transmitting the ACK, meaning it stops listening to PDCCH within the first duration (6 time slots). Within the first duration, the valid SSSG is SSSG0, meaning the terminal device is still in SSSG0. After transmitting the ACK, the terminal device listens to PDCCH according to the SS set of SSSG1. This can be understood as the terminal device's valid SSSG remaining unchanged before the start time of SSSG.

[0467] Optionally, in a multi-DL BWP scenario, the start time of the first duration and the start time of the SSSG can also be determined separately. The start time of the first duration can use the implementation method described in Method 1000 above, and the start time of the SSSG can also use the implementation method described in Method 1000 above. The determined start time of the first duration and the determined start time of the SSSG can be different. Before the start time of the SSSG, the valid SSSG of the terminal device remains unchanged.

[0468] In another possible implementation, the terminal device can first determine the start time of the first duration. The method for determining the start time of the first duration can be referred to the description in method 1000 above, and will not be repeated here. Then, after the first duration, the terminal device determines the start time of the SSSG. Before the start time of the SSSG, no SSSG handover is performed. After the start time of the SSSG, the terminal device listens to the PDCCH according to the SS set of the SSSG indicated by the DCI. This can be understood as the terminal device and network device using the end time of the first duration as a reference point to determine the start time of the SSSG.

[0469] The start time of SSSG can be determined based on the time offset between the start time of SSSG and the end time of the first duration. The time offset between the start time of SSSG and the end time of the first duration can be predefined or configured by the network device. The value of the time offset can refer to the value of the time offset between the start time of the first duration and DCI in the above method 1000, which will not be repeated here.

[0470] For example, Figure 22 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 22 As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with SSSG0 and SSSG1 on the active DL BWP. The PDCCH listening time of SSSG0's SS set is in a period of one time slot, while the PDCCH listening time of SSSG1's SS set is in a period of two time slots. It should be understood that the PDCCH listening time of SSSG1 is sparser than that of SSSG0. The first duration can be six time slots.

[0471] The terminal device listens to the PDCCH on the active DL BWP and also listens to the PDCCH in the SS set of SSSG0. The network device instructs the terminal device to stop listening to the PDCCH within a first duration and instructs the terminal device to switch SSSG1 via the PDCCH carrying the fourth DCI. The terminal device then listens to the PDCCH carrying the fourth DCI. Figure 22As shown, based on the fourth DCI, the terminal device determines that the start time of the first duration is offset from the time of the fourth DCI by one time slot. During the first duration (6 time slots), it stops listening to the PDCCH. The terminal device determines that the start time of the SSSG is offset from the end time of the first duration by two time slots. That is, two time slots after the end time of the first duration, the terminal device switches to the SS set of SSSG1 to listen to the PDCCH. Specifically, after the end time of the first duration but before the start time of the SSSG, the terminal device listens to the PDCCH in the SS set of SSSG0.

[0472] Optionally, in a multi-DL BWP scenario, the fourth DCI can simultaneously instruct the device to stop listening to the PDCCH, switch to SSSG1, and perform BWP switching within the first duration. The terminal device can refer to the description in method 1000 above for determining the start time of the first duration, which will not be repeated here.

[0473] In another possible implementation, the terminal device can first determine the start time of the SSSG. The method for determining the start time of the SSSG can be referred to the description in method 1000 above, and will not be repeated here. Then, the terminal device determines the start time of the first duration. Before the start time of the first duration, the terminal device listens to the PDCCH in the SS set of the SSSG indicated by the DCI. After the start time of the first duration, the terminal device stops listening to the PDCCH within the first duration. This can be understood as the terminal device and the network device using the start time of the SSSG as a reference point to determine the start time of the first duration.

[0474] The start time of the first duration can be determined based on the time offset between the start time of the SSSG and the start time of the first duration. The time offset between the start time of the SSSG and the start time of the first duration can be predefined or configured by the network device. The value of the time offset can refer to the value of the time offset between the start time of the first duration and the DCI in the above method 1000, which will not be repeated here.

[0475] For example, Figure 23 A schematic diagram illustrating how to stop listening to the PDCCH is shown. (For example...) Figure 23 As shown, the black-filled squares represent the PDCCH listening times that the terminal device needs to monitor. The network device is configured with SSSG0 and SSSG1 on the active DL BWP. The PDCCH listening time of SSSG0's SS set is in a period of one time slot, while the PDCCH listening time of SSSG1's SS set is in a period of two time slots. It should be understood that the PDCCH listening time of SSSG1 is sparser than that of SSSG0. The first duration can be six time slots.

[0476] The terminal device listens to the PDCCH on the active DL BWP and also listens to the PDCCH in the SS set of SSSG0. The network device instructs the terminal device to stop listening to the PDCCH within a first duration and instructs the terminal device to switch to SSSG1 via the PDCCH carrying the fourth DCI. The terminal device then listens to the PDCCH carrying the fourth DCI. Figure 22 As shown, based on the fourth DCI, the terminal device determines that the start time of SSSG is offset from the time of the fourth DCI by 1 time slot. The terminal device switches to SS set of SSSG1 to listen to PDCCH. The terminal device determines that the start time of the first duration is offset from the start time of SSSG by 2 time slots. That is, after 2 time slots after the start time of SSSG, the terminal device stops listening to PDCCH within the first duration, and continues to listen to PDCCH in SS set of SSSG1 after the first duration.

[0477] Optionally, in a multi-DL BWP scenario, the fourth DCI can simultaneously instruct the device to stop listening to the PDCCH, switch to SSSG1, and perform BWP switching within the first duration. The terminal device's determination of the SSSG start time can be found in the description of method 1000 above, and will not be repeated here.

[0478] The sequence number of each process does not imply 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 this application.

[0479] The above text combines Figures 1 to 13 The method for stopping PDCCH monitoring according to embodiments of this application is described in detail below, and will be combined with 14 and Figure 15 This application describes in detail the communication device according to embodiments of the present application.

[0480] Figure 14 An embodiment of this application illustrates a communication apparatus 1400. The apparatus 1400 includes a transceiver unit 1410 and a processing unit 1420.

[0481] In an optional example, those skilled in the art will understand that device 1400 may specifically be the terminal device in method 600, method 800, or method 1000 described above; or, the functions of the terminal device in method 600, method 800, method 1800, or method 1000 may be integrated into device 1400. The aforementioned functions may be implemented in hardware or by hardware executing corresponding software. The hardware or software may include one or more modules corresponding to the aforementioned functions. Device 1400 may be used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments.

[0482] For example, device 1400 may be specifically the terminal device in method 600 described above. Transceiver unit 1410 is configured to: receive first downlink control information (DCI) from a network device on the activated downlink DL bandwidth portion (BWP), the first DCI being used to instruct the device to stop listening to PDCCH within a first duration, the PDCCH to be stopped including PDCCH in the type 3 common search space set and PDCCH in the device-specific search space set; processing unit 1420 is configured to: run a timer for BWP handover, wherein the timer expires before the end of the first duration; stop listening to PDCCH within the first duration and before the timer expires; and when the timer expires, perform DL BWP handover and listen to PDCCH on the DL BWP after handover.

[0483] Optionally, the processing unit 1420 is further configured to: when receiving indication information from a network device on an activated DL BWP, start or restart a timer; wherein the indication information is used to schedule the device to perform transmission of Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH), or the indication information is used to instruct the device to perform DL BWP switching, and the indication information is carried in the first DCI or other DCIs different from the first DCI.

[0484] Optionally, the length of the first duration is configured by Radio Resource Control (RRC) or indicated by the first DCI.

[0485] Optionally, the device 1400 determines the start time of the first duration based on at least one of the following: the time offset between the start time of the first duration and the first DCI; the minimum time slot offset being the minimum time slot offset between the PDCCH carrying the first DCI and the PDSCH that the first DCI is allowed to schedule; the first DCI scheduling the PDSCH after the HARQ feedback corresponding to the PDSCH; or, the first DCI scheduling the PUSCH after the PUSCH transmission.

[0486] For example, device 1400 can be specifically the terminal device in method 800 described above. Transceiver unit 1410 is used to execute the transmit / receive actions corresponding to the terminal device in S801 of method 800, and processing unit 1420 is used to execute the processing actions corresponding to the terminal device in method 800. In an optional example, those skilled in the art will understand that device 1400 can be specifically the network device in method 600, method 800, method 1800, or method 1000, or the functions of the network device in method 600, method 800, method 1800, or method 1000 can be integrated into device 1400. The above functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. Device 1400 can be used to execute various processes and / or steps corresponding to the network device in the above method embodiments.

[0487] For example, the device 1400 may specifically be the network device in the method 800 described above. The transceiver unit 1410 is used to perform the transceiver action corresponding to the network device in S801 of the method 800, and the processing unit 1420 is used to perform the processing action corresponding to the network device in the method 800.

[0488] It should be understood that the aforementioned apparatus 1400 is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that apparatus 1400 may specifically be a terminal device or network device in the above method embodiments, or the functions of the terminal device or network device in the above method embodiments may be integrated into apparatus 1400. Apparatus 1400 may be used to execute the various processes and / or steps corresponding to the terminal device or network device in the above method embodiments; to avoid repetition, these will not be described further here.

[0489] The aforementioned device 1400 has the function of implementing the corresponding steps performed by the terminal device or network device in the above method embodiments; the above functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0490] In the embodiments of this application, Figure 14 The communication device in the text can also be a chip or a chip system, such as a system on a chip (SoC).

[0491] Figure 15 This is a schematic block diagram of another communication device 1500 provided in an embodiment of this application. The device 1500 includes a processor 1510, a transceiver 1520, and a memory 1530. The processor 1510, transceiver 1520, and memory 1530 communicate with each other via internal interconnection paths. The memory 1530 is used to store instructions, and the processor 2140 is used to execute the instructions stored in the memory 1530 to control the transceiver 1520 to transmit and / or receive signals.

[0492] It should be understood that device 1500 may specifically be a terminal device or network device in methods 600, 800, 1800, or 1000 described above; or, the functions of the terminal device or network device in methods 600, 800, 1800, or 1000 may be integrated into device 1500. Device 1500 may be used to execute the various steps and / or processes in methods 600, 800, 1800, or 1000 corresponding to the terminal device or network device. Optionally, memory 1530 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. Processor 1510 may be used to execute instructions stored in memory, and when the processor executes the instructions, the processor may execute the various steps and / or processes in methods 600, 800, 1800, or 1000 corresponding to the terminal device or network device.

[0493] It should be understood that, in the embodiments of this application, the processor 1510 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0494] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0495] This application also provides a computer-readable storage medium for storing a computer program that implements the methods corresponding to the terminal device or network device in the above method embodiments.

[0496] This application also provides a computer program product, which includes a computer program (also known as code or instructions). When the computer program is run on a computer, the computer can execute the methods corresponding to the terminal device or network device shown in the above method embodiments.

[0497] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0498] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0499] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0500] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0501] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0502] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for stopping monitoring of the Physical Downlink Control Channel (PDCCH), characterized in that, include: The terminal device receives a first downlink control information (DCI) from the network device on the activated downlink bandwidth portion (BWP). The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's dedicated search space set. The terminal device runs a timer for BWP handover, wherein the expiration time of the timer and the BWP handover delay are before the end time of the first duration. The terminal device stops listening to the PDCCH within the first time period and before the BWP handover delay ends; When the timer expires, the terminal device performs a DL BWP switch and listens for PDCCH on the switched DL BWP.

2. The method according to claim 1, characterized in that, The terminal device runs a timer, including: When the terminal device receives an indication from the network device on the activated DL BWP, the terminal device starts or restarts the timer; The indication information is used to schedule the terminal device to transmit Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH), or the indication information is used to instruct the terminal device to perform DL BWP switching. The indication information is carried in the first DCI or in a different DCI than the first DCI.

3. The method according to claim 1 or 2, characterized in that, The length of the first duration is configured by Radio Resource Control (RRC) or indicated by the first DCI.

4. The method according to claim 1 or 2, characterized in that, The start time of the first duration is the start of the next time slot of the first DCI.

5. The method according to claim 1 or 2, characterized in that, The method further includes: If no search space set is configured on the switched DL BWP, the terminal device listens to the PDCCH on the switched DL BWP according to the configured search space set; or, When a search space set is configured on the switched DL BWP, the terminal device listens to the PDCCH on the switched DL BWP according to the search space set in the configured search space set, wherein the index of the configured search space set is 0.

6. A method for stopping monitoring of the Physical Downlink Control Channel (PDCCH), characterized in that, include: The terminal device receives a first downlink control information (DCI) from the network device on the activated downlink bandwidth portion (BWP). The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's dedicated search space set. The terminal device runs a timer, which is used for BWP switching; Based on the first DCI, the terminal device stops listening to the PDCCH within the first duration and pauses the operation of the timer; After the first duration, the terminal device continues to run the timer; When the timer expires, the terminal device performs a DL BWP switch.

7. The method according to claim 6, characterized in that, The terminal device runs a timer, including: When the terminal device receives an indication from the network device on the activated DL BWP, the terminal device starts or restarts the timer; The indication information is used to schedule the terminal device to transmit Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH), or the indication information is used to instruct the terminal device to perform DL BWP switching. The indication information is carried in the first DCI or in a different DCI than the first DCI.

8. The method according to claim 6 or 7, characterized in that, The length of the first duration is configured by Radio Resource Control (RRC) or indicated by the first DCI.

9. The method according to claim 6 or 7, characterized in that, The start time of the first duration is the start of the next time slot of the first DCI.

10. The method according to claim 6 or 7, characterized in that, The method further includes: If no search space set is configured on the switched DL BWP, the terminal device listens to the PDCCH on the switched DL BWP according to the configured search space set; or, When a search space set is configured on the switched DL BWP, the terminal device listens to the PDCCH on the switched DL BWP according to the search space set in the configured search space set, wherein the index of the configured search space set is 0.

11. A method for stopping monitoring of the Physical Downlink Control Channel (PDCCH), characterized in that, include: The terminal device receives a second downlink control information (DCI) from the network device on the activated downlink bandwidth portion (BWP). The second DCI is used to instruct the DL BWP to switch and stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's dedicated search space set. The second DCI is used to schedule the transmission of the physical downlink shared channel (PDSCH). The terminal device performs DL BWP switching based on the second DCI, and stops listening to the PDCCH on the switched DL BWP; The start time of the first duration is determined based on at least one of the following: The next time slot after the BWP handover delay; The time slot containing the PDSCH is transmitted on the switched DL BWP; The next time slot of the time slot where the PDSCH is located is transmitted on the switched DL BWP; The time offset between the start time of the first duration and the second DCI; The minimum timeslot offset is the maximum value between the minimum timeslot offset and the time required to parse the second DCI, where the minimum timeslot offset is the minimum timeslot offset between the PDCCH carrying the second DCI and the PDSCH for which the second DCI is allowed to be scheduled; or... The second DCI schedules the PDSCH, and the corresponding Hybrid Automatic Repeat Request (HARQ) is fed back after the PDSCH.

12. The method according to claim 11, characterized in that, The length of the first duration is configured by Radio Resource Control (RRC) or indicated by the second DCI.

13. The method according to claim 11 or 12, characterized in that, The second DCI is also used to instruct the terminal device to switch to the first search space set, which is the search space set on the switched DL BWP; The method further includes: The terminal device switches to the first search space set on the switched DL BWP.

14. The method according to claim 13, characterized in that, The time when the terminal device switches to the first search space set on the switched DL BWP is: the next time slot or the next symbol after the first duration, or the same time slot or symbol as the start time of the first duration.

15. The method according to claim 13, characterized in that, The time at which the terminal device switches to the first search space set on the switched DL BWP is determined based on at least one of the following information, and is different from the start time of the first duration: The next time slot after the BWP handover delay; The time slot containing the PDSCH is transmitted on the switched DL BWP; The next time slot of the time slot where the PDSCH is located is transmitted on the switched DL BWP; The time offset between the start time of the first duration and the second DCI; Based on the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or, The second DCI schedules the PDSCH, and the corresponding Hybrid Automatic Repeat Request (HARQ) is fed back after the PDSCH.

16. A method for stopping monitoring of the Physical Downlink Control Channel (PDCCH), characterized in that, include: The network device sends a first downlink control information (DCI) to the terminal device on the activated downlink bandwidth portion (BWP). The first DCI is used to instruct the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's dedicated search space set. The network device runs a timer, which is used for BWP handover; The network device pauses the operation of the timer during the first duration; After the first duration, the network device continues to run the timer; When the timer expires, the network device performs a DL BWP handover.

17. The method according to claim 16, characterized in that, The length of the first duration is configured by Radio Resource Control (RRC) or indicated by the first DCI.

18. The method according to claim 16 or 17, characterized in that, The network device determines the start time of the first duration based on at least one of the following information: The time offset between the start time of the first duration and the first DCI; The first DCI schedules the PDSCH, and the corresponding Hybrid Automatic Repeat Request (HARQ) is fed back after the PDSCH; or... The first DCI schedules the PUSCH, after which the PUSCH is transmitted.

19. A method for stopping monitoring of the Physical Downlink Control Channel (PDCCH), characterized in that, include: The network device sends a second downlink control information (DCI) to the terminal device on the activated downlink bandwidth portion (BWP). The second DCI is used to instruct the DL BWP to switch and the terminal device to stop listening to the PDCCH within a first duration. The PDCCH to be stopped includes the PDCCH in the type 3 common search space set and the PDCCH in the terminal device's dedicated search space set. The second DCI is used to schedule the transmission of the physical downlink shared channel (PDSCH). The network device performs DL BWP handover based on the second DCI; The start time of the first duration is determined based on at least one of the following: The next time slot after the BWP handover delay; The time slot containing the PDSCH is transmitted on the switched DL BWP; The next time slot of the time slot where the PDSCH is located is transmitted on the switched DL BWP; The time offset between the start time of the first duration and the second DCI; The minimum timeslot offset is the maximum value between the minimum timeslot offset and the time required to parse the second DCI, where the minimum timeslot offset is the minimum timeslot offset between the PDCCH carrying the second DCI and the PDSCH for which the second DCI is allowed to be scheduled; or... The second DCI schedules the PDSCH, and the corresponding Hybrid Automatic Repeat Request (HARQ) is fed back after the PDSCH.

20. The method according to claim 19, characterized in that, The length of the first duration is configured by Radio Resource Control (RRC) or indicated by the second DCI.

21. The method according to claim 19 or 20, characterized in that, The second DCI is also used to instruct the terminal device to switch to the first search space set, which is the search space set on the switched DL BWP; The method further includes: The network device switches to the first search space set on the switched DL BWP.

22. The method according to claim 21, characterized in that, The time when the network device switches to the first search space set on the switched DL BWP is: the next time slot or the next symbol after the first duration, or the same time slot or symbol as the start time of the first duration.

23. The method according to claim 21, characterized in that, The time at which the network device switches to the first search space set on the switched DL BWP is determined based on at least one of the following information, and is different from the start time of the first duration: The next time slot after the BWP handover delay; The time slot containing the PDSCH is transmitted on the switched DL BWP; The next time slot of the time slot where the PDSCH is located is transmitted on the switched DL BWP; The time offset between the start time of the first duration and the second DCI; Based on the maximum value between the minimum time slot offset and the duration of parsing the second DCI; or, The second DCI schedules the PDSCH, and the corresponding Hybrid Automatic Repeat Request (HARQ) is fed back after the PDSCH.

24. A communication device, characterized in that, It includes modules for performing the method as described in any one of claims 1 to 10, the method as described in any one of claims 11-15, the method as described in any one of claims 16 to 18, or the method as described in any one of claims 19-23.

25. A communication device, characterized in that, include: A processor and a transceiver, the transceiver communicating with other devices, the processor being coupled to a memory for storing a computer program, which, when invoked by the processor, causes the device to perform the method as claimed in any one of claims 1 to 10, any one of claims 11-15, any one of claims 16 to 18, or any one of claims 19-23.

26. A chip, characterized in that, include: A processor for reading instructions stored in memory, and when the processor executes the instructions, causing the chip to implement the method as claimed in any one of claims 1 to 10, the method as claimed in any one of claims 11-15, the method as claimed in any one of claims 16 to 18, or the method as claimed in any one of claims 19-23.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a computer, causes the method of any one of claims 1 to 10, any one of claims 11 to 15, any one of claims 16 to 18, or any one of claims 19 to 23 to be performed.

28. A computer program product, characterized in that, The computer program product includes instructions that, when executed, cause the method of any one of claims 1 to 10, any one of claims 11 to 15, any one of claims 16 to 18, or any one of claims 19 to 23 to be performed.

Images