WO2022205346A1

WO2022205346A1 - Method for switching search space set group (sssg) by terminal device, and terminal device and network device

Info

Publication number: WO2022205346A1
Application number: PCT/CN2021/085040
Authority: WO
Inventors: 胡奕; 李海涛
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-04-01
Filing date: 2021-04-01
Publication date: 2022-10-06
Also published as: CN116530160A

Abstract

A method for switching a search space set group (SSSG) by a terminal device, and a terminal device and a network device, which help to balance the scheduling requirement and the power saving requirement of the terminal device. The method comprises: in a time period in which a terminal device monitors a physical downlink control channel (PDCCH) on the basis of a first SSSG, the terminal device sending a scheduling request (SR) to a network device, wherein the SR is in a waiting state; and the terminal device switching to a second SSSG in a particular condition, so as to monitor a PDCCH on the basis of the second SSSG, wherein the density of a PDCCH monitoring occasion, which corresponds to the second SSSG, in a time-domain distribution, is greater than the density of a PDCCH monitoring occasion, which corresponds to the first SSSG, in the time-domain distribution.

Description

Method for switching search space set grouping SSSG by terminal device, terminal device and network device

technical field

The embodiments of the present application relate to the field of communications, and in particular, to a method for switching a search space set grouping SSSG by a terminal device, a terminal device, and a network device.

Background technique

In the discontinuous reception (DRX) scenario, in order to reduce the blind detection of the physical downlink control channel (PDCCH) by the terminal equipment, it is considered to use the search space set group (Search Space Set Group, SSSG) switching mechanism to control the The PDCCH monitoring behavior of the terminal. That is, the network device configures two SSSGs for the terminal device, wherein one SSSG corresponds to a relatively dense PDCCH monitoring opportunity, and the other SSSG corresponds to a relatively sparse PDCCH monitoring opportunity. Using dense SSSG to monitor PDCCH can achieve more timely scheduling and reduce service delay; using sparse SSSG to monitor PDCCH can achieve the purpose of terminal power saving.

The network device can instruct the terminal device to monitor the PDCCH based on which SSSG, but in some scenarios, the terminal device will trigger uplink transmission by itself and expect further response from the network device. The uplink resources reported by the Buffer Status Report (BSR) trigger a Scheduling Request (SR). In this case, the terminal device has an urgent need for PDCCH monitoring because the terminal device expects a response from the network device. From the perspective of the network device, the network device can learn the scheduling requirements of the terminal device only after receiving these uplink transmissions from the terminal device. Before the network device receives these uplink transmissions from the terminal device, the network device does not Know the scheduling requirements of the terminal equipment. Therefore, how the terminal equipment performs PDCCH monitoring to balance the scheduling requirement and the power saving requirement of the terminal equipment is an urgent problem to be solved.

SUMMARY OF THE INVENTION

The present application provides a method for switching a search space set group SSSG by a terminal device, a terminal device and a network device, which are beneficial to balance the scheduling requirement and the power saving requirement of the terminal device.

A first aspect provides a method for a terminal device to switch a search space set grouped SSSG, including: in a time period when the terminal device monitors a physical downlink control channel PDCCH based on a first SSSG, the terminal device sends a scheduling request SR to a network device , and the SR is in a waiting state;

The terminal device switches to the second SSSG under certain conditions, and monitors the PDCCH based on the second SSSG;

The density of the PDCCH listening opportunities corresponding to the second SSSG in the time domain distribution is greater than the density of the PDCCH listening opportunities corresponding to the first SSSG in the time domain distribution.

A second aspect provides a method for a terminal device to switch a search space set group SSSG, comprising: a network device sending configuration information to the terminal device, where the configuration information is used to configure the terminal device to send a scheduling request SR and the SR is waiting Whether to perform switching from the first SSSG to the second SSSG and/or switching from the first SSSG to the second SSSG in the state of The density of the opportunities in the time domain distribution is greater than the density of the PDCCH listening opportunities corresponding to the first SSSG in the time domain distribution.

In a third aspect, a terminal device is provided for executing the method in the above-mentioned first aspect or each implementation manner thereof.

Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided for executing the method in the second aspect or each of its implementations.

Specifically, the network device includes functional modules for executing the methods in the second aspect or the respective implementation manners thereof.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the above-mentioned first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or each of its implementations.

In a seventh aspect, a chip is provided for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

Specifically, the chip includes: a processor for invoking and running a computer program from a memory, so that a device in which the device is installed executes any one of the above-mentioned first to second aspects or each of its implementations method.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to execute the method in any one of the above-mentioned first aspect to the second aspect or each of its implementations.

In a ninth aspect, a computer program product is provided, comprising computer program instructions, the computer program instructions causing a computer to execute the method in any one of the above-mentioned first to second aspects or the implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method in any one of the above-mentioned first to second aspects or the respective implementations thereof.

Through the above technical solution, if the terminal device sends an SR and the SR is in the pending state within the time period when the sparse SSSG is used to monitor the PDCCH, the terminal device can switch to the dense SSSG to monitor the PDCCH under certain conditions, which is beneficial to balance the terminal device. scheduling needs and power saving needs.

Description of drawings

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.

FIG. 2 is a schematic diagram of a DRX cycle of a terminal device according to an embodiment of the present application.

FIG. 3 is a schematic interaction diagram of a method for a terminal device to switch a search space set grouping SSSG according to an embodiment of the present application.

FIG. 4 is an example diagram of a terminal device switching an SSSG according to an embodiment of the present application.

FIG. 5 is an example diagram of a terminal device switching an SSSG according to another embodiment of the present application.

FIG. 6 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

FIG. 7 is a schematic block diagram of a network device provided according to an embodiment of the present application.

FIG. 8 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

FIG. 9 is a schematic block diagram of a chip provided according to an embodiment of the present application.

FIG. 10 is a schematic block diagram of a communication system provided according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. With regard to the embodiments in the present application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, Advanced Long Term Evolution (Advanced long term evolution, LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application can also be applied to these communication systems.

Optionally, the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In this embodiment of the present application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).

In this embodiment of the present application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks The network equipment (gNB) in the PLMN network in the future evolution or the network equipment in the NTN network, etc.

As an example and not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc. Optionally, the network device may also be a base station set in a location such as land or water.

In this embodiment of the present application, a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). Pico cell), Femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Exemplarily, a communication system 100 to which this embodiment of the present application is applied is shown in FIG. 1 . The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). The network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. ; The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

It should be understood that the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship. For example, if A indicates B, it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.

In this embodiment of the present application, "predefinition" may be implemented by pre-saving corresponding codes, forms, or other means that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The implementation method is not limited. For example, predefined may refer to the definition in the protocol.

In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, which all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

In some scenarios, the network device may configure the DRX function for the terminal device, so that the terminal device discontinuously monitors the PDCCH, so as to achieve the purpose of saving power of the terminal device. Specifically, the network device can configure the terminal device to wake up at the time predicted by the network (DRX ON) and monitor the PDSCH, and the network can also configure the terminal device to sleep at the time predicted by the network (DRX OFF), that is, the terminal device does not need to monitor the PDCCH. Therefore, if the network device 120 has data to transmit to the terminal device 110, the network device 120 can schedule the terminal device 110 during the time when the terminal device 110 is in DRX ON, and during the DRC OFF time, due to the radio frequency being turned off, it can reduce the Terminal power consumption.

As shown in Figure 2, the DRX cycle configured by the network device for the terminal device consists of an activation period (On Duration) and a sleep period (Opportunity for DRX). In the RRC CONNECTED mode, if the terminal device is configured with the DRX function , during the DRX activation period, the terminal equipment monitors and receives the PDCCH; the terminal equipment does not monitor the PDCCH during the sleep period to reduce power consumption.

It should be understood that the terminal device in the dormant period in this embodiment of the present application does not receive the PDCCH, but can receive data from other physical channels. The embodiments of the present invention are not specifically limited. For example, the terminal device may receive a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), acknowledgment/non-acknowledgment (ACK/NACK), and the like. For another example, in semi-persistent scheduling (Semi-Persistent Scheduling, SPS), the terminal device may receive periodically configured PDSCH data.

In some embodiments, a DRX function may be configured for a media access control (Media Access Control, MAC) entity (entity) through a radio resource control (Radio Resource Control, RRC) to control the behavior of the terminal device to monitor the PDCCH. That is, each MAC entity may correspond to a DRX configuration. Optionally, the DRX configuration may include at least one of the following:

DRX Duration Timer (drx-onDurationTimer): The duration that the terminal device wakes up at the beginning of a DRX Cycle.

DRX slot offset (drx-SlotOffset): the delay for the terminal device to start drx-onDurationTimer.

DRX inactivity timer (drx-InactivityTimer): After the terminal device receives a PDCCH indicating uplink initial transmission or downlink initial transmission, the terminal device continues to monitor the duration of the PDCCH.

DRX downlink retransmission timer (drx-RetransmissionTimerDL): the longest duration for which the terminal device monitors the PDCCH indicating the downlink retransmission scheduling. Each downlink HARQ process except the broadcast HARQ process corresponds to one drx-RetransmissionTimerDL.

DRX uplink retransmission timer (drx-RetransmissionTimerUL): the longest duration for which the terminal device monitors the PDCCH indicating uplink retransmission scheduling. Each uplink HARQ process corresponds to one drx-RetransmissionTimerUL.

Long DRX cycle start offset (longDRX-CycleStartOffset): used to configure the long DRX cycle and the subframe offsets for the start of the long DRX cycle and the short DRX cycle.

Short DRX cycle (drx-ShortCycle): Short DRX cycle, optional configuration.

Short cycle timer (drx-ShortCycleTimer): the duration of the terminal device in the short DRX cycle (and not receiving any PDCCH), which is optional.

Downlink Hybrid Automatic Repeat Request (HARQ) Round Trip Time (RTT) Timer (HARQ RTT Timer): The minimum waiting time that the terminal device expects to receive the PDCCH indicating downlink scheduling. Each downlink HARQ process except the broadcast HARQ process corresponds to one HARQ RTT Timer.

Short TTI DRX retransmission timer (drx-RetransmissionTimerShortTTI): When short TTI is configured, the duration of the downlink retransmission timer.

Short TTI DRX uplink retransmission timer (drx-ULRetransmissionTimerShortTTI): When short TTI is configured, the duration of the uplink retransmission timer.

Uplink Hybrid Automatic Repeat Request (HARQ) Round Trip Time (RTT) Timer (UL HARQ RTT Timer): The minimum waiting time that the terminal device expects to receive the PDCCH indicating the uplink scheduling, each time Each uplink HARQ process corresponds to one UL HARQ RTT Timer.

If the terminal device is configured with DRX, the terminal device needs to monitor the PDCCH at the DRX activation time (Active Time). DRX Active Time includes the following situations:

Any one of drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and random access contention resolution timer (ra-ContentionResolutionTimer) is running;

The terminal device sends a Scheduling Request (SR) on the PUCCH and is in a pending state;

In the contention-based random access process, the terminal device has not received an initial transmission of the PDCCH indication scrambled by the cell radio network temporary identity (Cell RNTI, C-RNTI) after successfully receiving the random access response.

In some embodiments, the terminal device may decide the time to start drx-onDurationTimer according to whether it is currently in a long DRX cycle or a short DRX cycle.

For example, if the short DRX cycle is used, and the current subframe satisfies [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle).

For another example, if a long DRX cycle is used, and the current subframe satisfies [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset.

Among them, modulo represents the modulo operation.

In some embodiments, the terminal device may start the drx-onDurationTimer at a time after drx-SlotOffset slots from the beginning of the current subframe.

In some embodiments, the conditions for starting or restarting the drx-InactivityTimer include, but are not limited to:

If the terminal device receives a PDCCH indicating downlink or uplink initial transmission, the terminal device starts or restarts the drx-InactivityTimer.

In some embodiments, the conditions for starting and stopping drx-RetransmissionTimerDL include, but are not limited to:

When the terminal device receives a PDCCH indicating downlink transmission, or when the terminal device receives a MAC PDU on the configured downlink grant resource, the terminal device stops the drx-RetransmissionTimerDL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process after completing the transmission of the HARQ process feedback for the current downlink transmission.

If the timer drx-HARQ-RTT-TimerDL corresponding to a certain HARQ of the terminal device times out, and the decoding of downlink data transmitted using this HARQ process is unsuccessful, the terminal device starts the drx-RetransmissionTimerDL corresponding to this HARQ process.

In some embodiments, the conditions for the terminal to start and stop drx-RetransmissionTimerUL are:

When the terminal device receives a PDCCH indicating uplink transmission, or when the terminal device sends a MAC PDU on the configured uplink grant resource, the terminal device stops the drx-RetransmissionTimerUL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process after completing the first repetition of the PUSCH.

If the timer drx-HARQ-RTT-TimerUL corresponding to a certain HARQ of the terminal expires, the terminal device starts the drx-RetransmissionTimerUL corresponding to this HARQ process.

In some embodiments, the terminal device applies to the network device for uplink resources through the SR. The network device does not know when the terminal needs to send uplink data, that is, when the terminal device will send the SR. Therefore, the network device can allocate periodic physical uplink control channel (Physical Uplink Control channel, PUCCH) resources for transmitting SR to the terminal device, and then the network device detects whether there is an SR report on the allocated SR resources.

In NR systems, SR is based on logical channels. For each uplink logical channel, the network device may choose whether to configure the PUCCH resource for transmitting the SR for the uplink logical channel. In the case that an uplink logical channel triggers an SR, if the network device configures a PUCCH resource for transmitting an SR for the uplink logical channel, the terminal device sends an SR on the PUCCH resource corresponding to the logical channel for transmitting an SR; Otherwise, the terminal device initiates random access to apply for uplink resources.

In addition, if the terminal device triggers BFR on at least one secondary cell (SCell), and the terminal device currently does not have uplink resources available for initial transmission or the terminal device currently has uplink resources available for initial transmission but the resources are insufficient to carry BFR media The terminal device triggers an SR when it accesses a Media Access Control Control Element (MAC CE) or a truncated (truncated) BSR MAC CE.

In addition, if the terminal device triggers a persistent (Listen Before Talk, LBT) failure on at least one SCell, and the terminal device currently does not have uplink resources available for initial transmission or the terminal device currently has available resources for initial transmission When the transmitted uplink resources are insufficient to carry the LBT failure MAC CE, the terminal device triggers SR.

In some embodiments, the network device may configure the terminal device with multiple PUCCH resources for transmitting SR. For an uplink logical channel, if the network device configures the PUCCH resource for transmitting SR for the uplink logical channel, then on each uplink bandwidth part (Band Width Part, BWP), the network device can configure at most one logical channel for the PUCCH resource. PUCCH resources used to transmit SR.

Each PUCCH resource used to transmit SR corresponds to the following configuration parameters:

1. PUCCH resource period and slot/time symbol offset;

2. PUCCH resource index.

In order to reduce the number of blind detections of the Physical Downlink Control Channel (PDCCH) when the terminal equipment in the connected state is configured with DRX, it is considered to control the PDCCH monitoring behavior of the terminal equipment through the SSSG switching mechanism. That is, the network device configures two SSSGs for the terminal device, wherein one SSSG corresponds to a relatively dense PDCCH monitoring opportunity, and the other SSSG corresponds to a relatively sparse PDCCH monitoring opportunity. Using dense SSSG to monitor PDCCH can achieve more timely scheduling and reduce service delay; using sparse SSSG to monitor PDCCH can achieve the purpose of terminal power saving.

The network device can instruct the terminal device to monitor the PDCCH based on which SSSG, but in some scenarios, the terminal device will trigger uplink transmission by itself and expect further response from the network device. The uplink resources reported by the Buffer Status Report (BSR) trigger a Scheduling Request (SR). In this case, the terminal device has an urgent need for PDCCH monitoring because the terminal device expects a response from the network device. From the perspective of the network device, the network device can learn the scheduling requirements of the terminal device only after receiving these uplink transmissions from the terminal device. Before the network device receives these uplink transmissions from the terminal device, the network device does not Know the scheduling requirements of the terminal equipment. Therefore, how a terminal device can monitor the PDCCH in a straight line to obtain a response from a network device is an urgent problem to be solved.

FIG. 3 is a schematic interaction diagram of a method 200 for a terminal device to switch a search space set grouping SSSG according to an embodiment of the present application. The method 200 may be executed by the terminal device in the communication system shown in FIG. 1 , as shown in FIG. 3 , The method 200 includes the following:

S201, within a time period during which the terminal device monitors the physical downlink control channel PDCCH based on the first SSSG, the terminal device sends a scheduling request SR to a network device, and the SR is in a waiting state;

S202, the terminal device switches to a second SSSG under a specific condition, and monitors the PDCCH based on the second SSSG, wherein the density of the PDCCH monitoring opportunities corresponding to the second SSSG in the time domain distribution is greater than that of the first SSSG The density of the PDCCH listening opportunities corresponding to the SSSG in the time domain distribution.

In this embodiment of the present application, the terminal device is in a connected state, and the terminal device is configured with a DRX function, that is, the terminal device discontinuously monitors the PDCCH.

In some embodiments of the present application, the terminal device may receive configuration information of the network device, where the configuration information is used to configure the first SSSG and the second SSSG, wherein the PDCCH listening opportunity corresponding to the second SSSG is in the time domain The density in the distribution is greater than the density in the time domain distribution of the PDCCH listeners corresponding to the first SSSG.

That is, the first SSSG is a sparse SSSG, and the second SSSG is a dense SSSG. Performing PDCCH monitoring based on the first SSSG is more conducive to power saving of terminal equipment, and performing PDCCH monitoring based on the second SSSG is conducive to realizing timely scheduling of terminal equipment. , reduce service delay.

During the time period when the sparse SSSG is used to monitor the PDCCH, if the terminal device sends an SR and the SR is in the pending state, that is, the response from the network device has not yet been received. In this case, the SSSG switching mechanism needs to be designed to balance the terminal device. scheduling performance and power saving requirements.

That is, the technical solutions of the embodiments of the present application may be designed for the handover mechanism of the SSSG of the terminal device in a specific scenario. For example, the specific scenario may include that the terminal device sends an SR and the SR is in the pending state during the time period when the terminal device uses the sparse SSSG to monitor the PDCCH.

In some embodiments of the present application, during the time period when the terminal device uses the first SSSG to monitor the PDCCH, if the terminal device sends an SR, and the SR is in the pending state, the terminal device switches to the second SSSG to monitor the PDCCH.

That is, in a specific scenario, the terminal device may switch to the second SSSG to monitor the PDCCH regardless of the triggering cause of the SR.

In some embodiments, when the terminal device sends an SR and the SR is in a pending state, switching to a more intensive SSSG to monitor the PDCCH may be determined by the terminal device itself or configured by the network device.

For example, the network device may send first configuration information to the terminal device, where the first configuration information is used to configure whether the terminal device performs the transition from sparse SSSG to Intensive SSSG handover.

That is, the network device can configure whether the terminal device performs handover from the sparse SSSG to the dense SSSG in a specific scenario.

In some embodiments, if the first configuration information configures the terminal device to perform handover from the sparse SSSG to the dense SSSG when the SR is sent and the SR is in the pending state, the terminal device may send the SR , and the SR is pending, and the sparse SSSG is currently used to monitor the PDCCH, switch to the dense SSSG to monitor the PDCCH.

In some other embodiments, if the first configuration information configures the terminal device to not perform the handover from the sparse SSSG to the dense SSSG when the SR is sent and the SR is in the pending state, the terminal device sends the SR. SR, and the SR is pending, and the sparse SSSG is currently used to monitor the PDCCH, the switch from the sparse SSSG to the dense SSSG is not performed, that is, the sparse SSSG continues to be used to monitor the PDCCH.

In some embodiments of the present application, the method 200 further includes:

The terminal device determines whether to perform handover from the first SSSG to the second SSSG according to the triggering cause of the SR and/or the configuration information of the network device.

In the embodiment of the present application, when the terminal device has sent an SR, the SR is in the pending state, and the SSSG currently monitoring the PDCCH by the terminal device is a sparse SSSG, it is beneficial to determine whether to switch to the dense SSSG based on the triggering cause of the SR. Balance the scheduling performance of terminal equipment and the power saving needs of terminal equipment.

For example, when it is determined that the terminal device has an urgent need for PDCCH monitoring according to the triggering cause of the SR, switching to intensive SSSG monitoring of the PDCCH is beneficial to ensure the scheduling performance of the terminal device. When the demand is not urgent, the handover of the SSSG is not performed, which is beneficial to ensure the power saving demand of the terminal equipment.

In some embodiments, if the triggering cause of the SR is the secondary cell beam failure recovery or LBT failure recovery, in this case, it can be considered that the terminal device has an urgent PDCC monitoring requirement, and the terminal device switches from the first SSSG to the second SSSG.

In some embodiments of the present application, when the terminal device sends an SR and the SR is in the pending state, whether to switch to a more intensive SSSG to monitor the PDCCH based on certain judgment conditions may be determined by the terminal device itself, or It can also be configured by a network device.

Optionally, the judgment condition may include, but is not limited to, a triggering cause of the SR, configuration information of a network device, and the like, for example.

In some embodiments, the configuration information of the network device may include second configuration information, where the second configuration information is used to configure the terminal device to send an SR, the SR is in a pending state, and the trigger of the SR is a secondary cell beam Whether to perform handover from the first SSSG to the second SSSG in the case of failure recovery or LBT failure recovery.

As an example, the second configuration information may include 1-bit indication information, where the 1-bit indication information is used to instruct the terminal device that, in a specific scenario, the triggering cause of the SR is the secondary cell beam failure recovery or LBT failure recovery. case, whether to perform a switch from sparse SSSG to dense SSSG.

For example, the value of this 1 bit is 1 to indicate that the handover from the sparse SSSG to the dense SSSG is performed when the triggering cause of the SR is beam failure recovery of the secondary cell or LBT failure recovery, and the value of this 1 bit is 0. The triggering cause of the SR is that the handover from the sparse SSSG to the dense SSSG is not performed when the secondary cell fails to recover the beam or the LBT fails to recover.

That is to say, the triggering cause of the SR by the network device is the beam failure recovery of the secondary cell and the LBT failure recovery, and the network device uniformly controls whether to perform SSSG handover.

In other embodiments, the network device respectively sets corresponding configuration information for different triggering reasons of the SR to control whether to perform handover from the sparse SSSG to the dense SSSG when the SR is triggered by different reasons.

As an example, the configuration information of the network device includes third configuration information and/or fourth configuration information, where the third configuration information is used to instruct the terminal device to send an SR, the SR is in a waiting state and the SR The trigger reason is whether to perform handover from the first SSSG to the second SSSG when the secondary cell beam fails to recover, and the fourth configuration information is used to instruct the terminal device to send an SR, and the SR is waiting Whether to perform handover from the first SSSG to the second SSSG when the triggering cause of the SR is LBT failure recovery.

As an example, the third configuration information includes 1-bit indication information, where the 1-bit indication information is used to indicate whether to perform the transition from sparse SSSG to dense when the SR is triggered by a failure recovery of the secondary cell in a specific scenario. SSSG switching.

For example, if the third configuration information is configured to perform handover from a sparse SSSG to a dense SSSG when the triggering cause of the SR is the secondary cell beam failure recovery, the terminal device is in a specific scenario, and the triggering cause of the SR is the secondary cell. In case of cell beam failure recovery, handover from sparse SSSG to dense SSSG is performed.

As an example, the fourth configuration information may include 1-bit indication information, where the 1-bit indication information is used to indicate whether to perform the transition from sparse SSSG to dense in a specific scenario and the triggering cause of SR is LBT failure recovery SSSG switching.

For example, if the fourth configuration information is configured to perform handover from a sparse SSSG to a dense SSSG when the triggering cause of the SR is the secondary cell beam failure recovery, the terminal device is in a specific scenario, and the triggering cause of the SR is LBT On failure recovery, a switch from sparse SSSG to dense SSSG is performed.

In some embodiments of the present application, if the SR is triggered by the first logical channel, that is, the SR is triggered by the logical channel, in this case, the urgency of the terminal device to monitor the PDCCH is less than that caused by the secondary cell beam failure and LBT failure To restore the urgency for monitoring the PDCCH, as an implementation manner, the terminal device may not perform handover from the sparse SSSG to the dense SSSG.

In other embodiments of the present application, if the SR is triggered by the first logical channel, the terminal device may determine whether to start the first logical channel according to the configuration information of the first logical channel or the services carried by the first logical channel One SSSG switches to the second SSSG.

In some embodiments, the configuration information of the first logical channel includes first indication information, where the first indication information is used to indicate whether to allow the SR when the SR is triggered by the first logical channel The SR triggers the terminal device to switch from the first SSSG to the second SSSG, or in other words, the first indication information is used to indicate whether the SR is triggered by the first logical channel in the above-mentioned specific scenario. SR is allowed to trigger a switch from sparse SSSG to dense SSSG.

Optionally, the first indication information may be configured together with other configuration information of the first logical channel, or may be configured separately.

In some embodiments of the present application, each logical channel corresponds to respective first indication information. For example, when configuring the logical channel, the network device may configure the first indication information corresponding to each logical channel.

In some embodiments, if in the specific scenario, the SR is triggered by the first logical channel, and the first indication information corresponding to the first logical channel indicates that the SR is allowed to trigger the terminal device from the first logical channel. When an SSSG is switched to the second SSSG, the terminal device is switched from the first SSSG to the second SSSG.

In other embodiments, if in the specific scenario, the SR is triggered by the first logical channel, and the first indication information corresponding to the first logical channel indicates that the SR is not allowed to trigger the terminal device from the If the first SSSG is switched to the second SSSG, the terminal device does not switch from the first SSSG to the second SSSG.

Optionally, the content indicated by the first indication information may be determined according to the service corresponding to the first logical channel. For example, if the first logical channel is used to transmit the first type of service, the first indication information corresponding to the first logical channel indicates that the SR triggered by the first logical channel is allowed to trigger the terminal device to switch from the sparse SSSG to the dense SSSG , or, if the first logical channel is used to transmit the second type of service, the first indication information corresponding to the first logical channel indicates that the SR triggered by the first logical channel is not allowed to trigger the terminal equipment to switch from the sparse SSSG to the dense SSSG .

By way of example and not limitation, the first type of services includes delay-sensitive services, and the second type of services includes delay-insensitive services.

In other embodiments, in the specific scenario, and the SR is triggered by the first logical channel, the terminal device may also determine whether to perform the transition from sparse SSSG to Intensive SSSG handover.

As an example, if the service carried by the first logical channel is a service of the first type, it is determined to switch from the first SSSG to the second SSSG.

As another example, if the service carried by the first logical channel is the service of the second type, it is determined not to switch from the first SSSG to the second SSSG.

Optionally, in this embodiment of the present application, switching the terminal device from a sparse SSSG to a dense SSSG to monitor the PDCCH may include: the terminal device stops monitoring the PDCCH based on the first SSSG, and starts to monitor the PDCCH based on the second SSSG. Monitor the PDCCH.

Correspondingly, in this embodiment of the present application, the network device may also switch from sending the PDCCH based on the first SSSG to sending the PDCCH based on the second SSSG according to the aforementioned switching condition of the SSSG.

For example, in the case where the SR of the terminal device is received and the SR is sent during monitoring of the PDCCH based on the first SSSG, the network device switches from sending the PDCCH based on the first SSSG to sending the PDCCH based on the second SSSG.

For another example, when the SR of the terminal device is received, and the SR is sent during the monitoring of the PDCCH based on the first SSSG, and the SR is recovered by the secondary cell beam failure or LBT failure recovery, the network device starts from the first SSSG based on the first SSSG. The SSSG switches to sending the PDCCH based on the second SSSG.

For another example, when an SR of the terminal device is received, the SR is sent during the period of monitoring the PDCCH based on the first SSSG, the SR is triggered by a logical channel, and the first indication information corresponding to the logical channel indicates that the SR is allowed to trigger the terminal device to execute the SSSG. In the case of handover, the network device switches from sending the PDCCH based on the first SSSG to sending the PDCCH based on the second SSSG.

Optionally, the network device may determine the triggering cause of the SR according to the uplink resource used by the terminal device to send the SR.

The terminal device switches to the denser SSSG monitoring PDCCH in order to obtain a faster response from the network device. Therefore, which serving cells to switch from performing the sparse SSSG monitoring PDDC to the dense SSSG monitoring PDCCH is also a problem that needs to be solved. That is, on which serving cells the SSSG handover mechanism of the embodiment of the present application is executed.

The terminal device determines to perform handover from the first SSSG to the second according to a logical channel priority (Logical Channel Priority, LCP) restriction parameter and/or cross-carrier scheduling configuration of the first logical channel that triggers the SR The target serving cell set of the SSSG.

In some embodiments, the terminal device determines, according to a logical channel priority (Logical Channel Priority, LCP) restriction parameter and/or a cross-carrier scheduling configuration of the first logical channel that triggers the SR, to execute the first SSSG from the first SSSG. Handover to the target serving cell set of the second SSSG, including:

determining a first set of serving cells according to the LCP restriction parameter of the first logical channel;

determining a scheduling cell corresponding to each serving cell according to the cross-carrier scheduling configuration of each serving cell in the first serving cell set, where the scheduling cell corresponding to the serving cell can indicate uplink scheduling of the serving cell;

The scheduling cells corresponding to all serving cells in the first serving cell set are determined as the target serving cell set.

It should be understood that if a terminal device wants to obtain uplink scheduling information of a serving cell, it needs to monitor the PDCCH of the scheduling cell corresponding to the serving cell, where the scheduling cell corresponding to the serving cell may refer to a cell capable of sending a PDCCH indicating uplink scheduling of the serving cell.

In some embodiments, if the first logical channel is not configured with an LCP restriction parameter, it is determined that the first serving cell set includes all activated serving cells of the terminal device.

In other embodiments, if the first logical channel is configured with an LCP restriction parameter, determining the first serving cell set includes serving cells that are allowed to transmit the first logical channel.

Taking the first serving cell in the first serving cell set as an example, the manner of determining the scheduling cell corresponding to the serving cell is described.

For example, if the first serving cell is not configured with a cross-carrier scheduling configuration, the first serving cell is determined as the scheduling cell of the first serving cell, that is, the scheduling cell of the first serving cell is the first serving cell itself.

For another example, if the first serving cell is configured with a cross-carrier scheduling configuration, a cell configured in the cross-carrier scheduling configuration of the first serving cell that can indicate the uplink scheduling of the first serving cell is determined as the first serving cell. A scheduling cell for a serving cell.

Further, the terminal device performs handover from the first SSSG to the second SSSG on a target serving cell in the set of target serving cells.

Specifically, the terminal device may first determine the SSSG currently used on each target serving cell, and if the SSSG currently used by the target serving cell is a sparse SSSG, perform handover from the first SSSG to the second SSSG, otherwise do not perform the handover Handover from the first SSSG to the second SSSG.

The following describes the SSSG handover mechanism in a specific scenario according to the embodiment of the present application, and the specific execution process of determining the target serving cell of the SSSG handover mechanism, in conjunction with Embodiment 1 and Embodiment 2, respectively.

Embodiment 1: SSSG switching mechanism in a specific scenario.

step 1:

The terminal device receives the configuration information of the network device, the configuration information is used to configure the first SSSG and the second SSSG, and the PDCCH monitoring timing corresponding to the second SSSG is more distributed in the time domain than the PDCCH monitoring timing corresponding to the first SSSG. dense. That is, the first SSSG is a sparse SSSG, and the second SSSG is a denser SSSG.

Step 2:

The terminal device sends the SR through the PUCCH, and the SR is in the pending state.

If for each serving cell of the terminal device, if the terminal device currently monitors the PDCCH based on the first SSSG, the terminal device may perform the aforementioned SSSG handover mechanism.

As example 1, if the triggering cause of the SR is SCell beam failure recovery, the terminal device stops monitoring the PDCCH based on the first SSSG, and simultaneously starts monitoring the PDCCH based on the second SSSG.

Optionally, the terminal device may perform the SSSG handover in Example 1, which is determined by the terminal device autonomously.

Optionally, the terminal device performs the SSSG handover in Example 1 based on the configuration of the network device. For example, the network device may configure the terminal device to perform the above-mentioned SSSG when the SR triggering reason is the secondary cell beam failure recovery in a specific scenario. switch.

As example 2, if the triggering cause of the SR is LBT failure recovery, the terminal device stops monitoring the PDCCH based on the first SSSG, and simultaneously starts monitoring the PDCCH based on the second SSSG.

Optionally, the terminal device can perform the SSSG handover in Example 2, which is determined by the terminal device autonomously.

Optionally, the terminal device performs the SSSG handover in Example 2 based on the configuration of the network device. For example, the network device can configure the terminal device to perform the above-mentioned SSSG handover when the LBT failure recovery occurs due to the triggering cause of the SR in a specific scenario.

As example 3, if the SR is triggered by the first logical channel, for example, the first logical channel triggers a BSR or a pre-emptive BSR, but there is no uplink resource for BSR reporting, or uplink resources for BSR reporting If the resources are insufficient, the terminal device decides whether to perform SSSG handover according to the configuration information of the first logical channel.

Optionally, the network device may configure, for each uplink logical channel, indication information whether to allow the SR triggered by the uplink logical channel to trigger the terminal device to perform SSSG handover, that is, the first indication information described above.

For example, for a logical channel that transmits delay-sensitive services, the network device is configured to allow the SR triggered by the uplink logical channel to trigger the terminal device to switch to a denser SSSG to monitor the PDCCH.

For another example, for a logical channel that transmits delay-insensitive services, the configuration does not allow the SR triggered by the uplink logical channel to trigger the terminal device to switch to a denser SSSG to monitor the PDCCH.

Optionally, the terminal device determines whether to perform SSSG handover according to the configuration information of the first logical channel, which may include:

If the first logical channel is configured to allow the SR triggered by the first logical channel to trigger the terminal device to switch to monitor the PDCCH on the denser SSSG, the terminal device stops monitoring the PDCCH based on the first SSSG and starts to monitor the PDCCH based on the second SSSG at the same time Monitor the PDCCH.

If the first logical channel is configured not to allow the SR triggered by the first logical channel to trigger the terminal device to switch to monitor the PDCCH on the denser SSSG, the terminal device continues to monitor the PDCCH based on the first SSSG.

For illustration in conjunction with Figure 4, it is assumed that the terminal device is configured with 2 uplink logical channels, denoted as LC1 and LC2, and LC1 is configured to allow the SR triggered by the LC1 to trigger the terminal device to switch to a more dense SSSG to monitor the PDCCH. Configure whether to allow the SR triggered by the LC2 to trigger the terminal device to switch to the denser SSSG to monitor the PDCCH, or the LC2 is configured to not allow the SR triggered by the logical channel to trigger the terminal device to switch to the denser SSSG to monitor the PDCCH. That is, when the logical channel is not configured with the first indication information, it can be considered as not allowed. Alternatively, when the logical channel is not configured with the first indication information, it may also be considered as allowed.

As shown in FIG. 4 , if the LC1 triggers the SR within the time period during which the terminal device monitors the PDCCH based on the first SSSG, and the SR is in the pending state, the terminal device switches to use the second SSSG to monitor the PDCCH.

If the LC2 triggers the SR within the time period during which the terminal device monitors the PDCCH based on the first SSSG, and the SR is in the pending state, the terminal device continues to use the first SSSG to monitor the PDCCH.

Embodiment 2: Determination of the target serving cell for implementing the SSSG handover mechanism

step 1:

The terminal device receives configuration information of the network device, where the configuration information is used to configure at least one of the following:

a), configure the first SSSG and the second SSSG, the PDCCH monitoring opportunities corresponding to the second SSSG are more densely distributed in the time domain than the PDCCH monitoring opportunities corresponding to the first SSSG;

b) For each uplink logical channel of the terminal device, the network device can choose whether to configure the PUCCH resource for transmitting SR for the uplink logical channel.

If the network device chooses to configure the uplink logical channel with PUCCH resources for SR transmission, the network device may configure 0 or 1 PUCCH resources for the uplink logical channel on each uplink BWP of each serving cell of the terminal device for transmission SR's PUCCH resources.

c) For each uplink logical channel of the terminal device, the network device may configure the LCP restriction parameter for the uplink logical channel, or may not configure the LCP restriction parameter for the uplink logical channel, wherein the LCP restriction parameter is used to limit the allowable The serving cell transmitted by the uplink logical channel.

Optionally, the LCP restriction parameters include but are not limited to the following parameters:

Allowed Serving Cells (allowed Serving Cells), that is, a list of serving cells that are allowed to transmit the uplink logical channel;

An allowed subcarrier spacing (Subcarrier spacing, SCS) list (allowedSCS-List), that is, a list of subcarrier spacings allowed to transmit the uplink logical channel.

Step 2:

If the first logical channel of the terminal device triggers the terminal device to send an SR on the PUCCH of the serving cell and the SR is in the pending state, the terminal device determines and executes the aforementioned SSSG handover mechanism according to the LCP restriction parameter of the uplink logical channel that triggers the SR. set of target serving cells.

Specifically, the terminal device first determines, according to the LCP restriction parameter of the first logical channel, the first set of serving cells that allow transmission of the first logical channel.

For example, if the network device does not configure the LCP restriction parameter for the first logical channel that triggers the SR, the terminal device determines that the first serving cell set includes all activated serving cells of the terminal device, that is, all activated serving cells The transmission of the first logical channel is allowed on both.

For another example, if the network device configures an LCP restriction parameter for the first logical channel that triggers the SR, the terminal device may determine a cell that allows transmission of the first logical channel according to the LCP restriction parameter of the first logical channel.

Further, according to the cross-carrier scheduling configuration of the first serving cell set, a target serving cell set for performing SSSG handover is determined.

Specifically, according to the cross-carrier scheduling configuration of each serving cell in the first serving cell set, determine the scheduling cell corresponding to each serving cell, and further determine the scheduling corresponding to all serving cells in the first serving cell set The cells constitute the set of target serving cells.

For example, if the first serving cell in the first serving cell set is not configured with a cross-carrier scheduling configuration, it is determined that the scheduling cell corresponding to the first serving cell is the first serving cell itself, or if the first serving cell is configured with a cross-carrier scheduling configuration carrier scheduling configuration, the scheduling cell corresponding to the first serving cell may be determined according to the cross-carrier scheduling configuration of the first serving cell.

Further, for each serving cell in the target serving cell set, the terminal device determines whether the serving cell currently monitors the PDCCH based on the first SSSG, and if so, the terminal device performs SSSG handover, that is, stops monitoring based on the first SSSG. PDCCH, while starting to monitor PDCCH based on the second SSSG. Otherwise, SSSG handover is not performed.

5, it is assumed that the terminal device is configured with two uplink logical channels, denoted as LC1 and LC2, and all activated serving cells of the network device include the primary cell (PCell) and the secondary cell 1 (Scell 1). The network device is not configured with LCP restriction parameters for LC1. For LC2, the network device is configured with LCP restriction parameters, and according to the LCP restriction parameters of LC2, it is determined that only LC2 is allowed to be transmitted on PCell. For the serving cell of the terminal device, the network device is not configured with a cross-carrier scheduling configuration, that is, for each serving cell, the scheduling cell is the serving cell itself.

As shown in Figure 5, if LC1 triggers SR and SR is in pending state, since LC1 does not configure LCP restriction parameters, it can be determined that the target serving cell set includes PCell and Scell 1. If the terminal device is currently based on PCell and Scell 1 based on The first SSSG monitors the PDCCH, and the terminal device switches to monitor the PDCCH using the second SSSG on PCell and Scell 1.

If the SR is triggered by LC2 and the SR is in the pending state, the LC2 is configured with LCP restriction parameters, and it can be determined according to the LCP restriction parameters that the target serving cell set includes the Pcell, and the terminal device currently monitors the PDCCH based on the first SSSG on the Pcell. Switch on the Pcell to use the second SSSG to monitor the PDCCH, and do not perform the SSSG switch on the Scell 1.

To sum up, if the terminal device sends an SR and the SR is in the pending state during the time period when the sparse SSSG is used to monitor the PDCCH, the terminal device can switch to the dense SR when the SR is triggered by the beam failure recovery of the secondary cell or the LBT failure recovery trigger. The SSSG monitors the PDCCH, which is beneficial to ensure the scheduling requirements of the terminal equipment.

In addition, if the terminal device sends an SR and the SR is in the pending state within the time period when the sparse SSSG is used to monitor the PDCCH, the terminal device can determine whether to switch to the dense SSSG to monitor the PDCCH according to the configuration of the LC when the SR is triggered by the LC. , which is conducive to ensuring the scheduling requirements of terminal equipment and the power saving requirements of terminal equipment.

Further, when the SR is triggered by the logical channel, according to the LCP parameters of the logical channel and the cross-carrier scheduling configuration of the serving cell, the target serving cell set for performing SSSG handover is determined, which is beneficial to ensure that the terminal equipment monitors the PDCCH on the correct cell. In order to obtain the response of the network device in time.

The method embodiments of the present application are described in detail above with reference to FIGS. 3 to 5 , and the device embodiments of the present application are described in detail below with reference to FIGS. 6 to 10 . It should be understood that the device embodiments and the method embodiments correspond to each other, and are similar to For the description, refer to the method embodiment.

FIG. 6 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 6, the terminal device 400 includes:

A communication unit 410, configured to send a scheduling request SR to the network device within the time period when the physical downlink control channel PDCCH is monitored based on the first SSSG, and the SR is in a waiting state;

a processing unit 420, configured to switch to the second SSSG under certain conditions;

The communication unit 410 is further configured to monitor the PDCCH based on the second SSSG;

In some embodiments of the present application, the processing unit 420 is further configured to:

Whether to switch from the first SSSG to the second SSSG is determined according to the triggering cause of the SR and/or the configuration information of the network device.

If the triggering cause of the SR is failure to restore the beam of the secondary cell, determine to switch from the first SSSG to the second SSSG; or

If the triggering cause of the SR is to recover from the failure of the listen-before-talk LBT, it is determined to switch from the first SSSG to the second SSSG.

If the SR is triggered by the first logical channel, determining whether to switch from the first SSSG to the second SSSG according to the configuration information of the first logical channel or the service carried by the first logical channel;

The configuration information of the first logical channel includes first indication information, where the first indication information is used to indicate whether the SR is allowed to trigger the SR when the SR is triggered by the first logical channel The terminal device switches from the first SSSG to the second SSSG.

If the first indication information is used to indicate that the SR is allowed to trigger the terminal device to switch from the first SSSG to the second SSSG, determine to switch from the first SSSG to the second SSSG; or

If the fifth first indication information is used to indicate that the SR is not allowed to trigger the terminal device to switch from the first SSSG to the second SSSG, determine not to switch from the first SSSG to the second SSSG SSSG.

If the service carried by the first logical channel is the first type of service, determine to switch from the first SSSG to the second SSSG; or

If the service carried by the first logical channel is the service of the second type, it is determined not to switch from the first SSSG to the second SSSG.

In some embodiments of the present application, the first type of services includes delay-sensitive services, and the second type of services includes delay-insensitive services.

In some embodiments of the present application, whether the terminal device determines whether to switch from the first SSSG to the second SSSG according to the triggering cause of the SR is determined by the terminal device.

In some embodiments of the present application, the configuration information of the network device includes first configuration information, where the first configuration information is used to configure whether the terminal device sends an SR and the SR is in a waiting state. A handover from the first SSSG to the second SSSG is performed.

In some embodiments of the present application, the configuration information of the network device includes second configuration information, where the second configuration information is used to configure the terminal device to send an SR, the SR is in a waiting state and the SR is triggered The reason is that the handover from the first SSSG to the second SSSG is performed when the secondary cell fails to recover the beam or the LBT fails to recover; or

The configuration information of the network device includes third configuration information and/or fourth configuration information, wherein the third configuration information is used to instruct the terminal device to send an SR, the SR is in a waiting state and the triggering cause of the SR In the case of beam failure recovery of the secondary cell, the handover from the first SSSG to the second SSSG is performed, and the fourth configuration information is used to instruct the terminal device to send an SR, the SR is in a waiting state and the When the triggering cause of the SR is LBT failure recovery, the handover from the first SSSG to the second SSSG is performed.

In some embodiments of the present application, the communication unit 410 is further configured to:

When it is determined to switch from the first SSSG to the second SSSG, the terminal device stops monitoring the PDCCH based on the first SSSG and starts monitoring the PDCCH based on the second SSSG.

A set of target serving cells to perform handover from the first SSSG to the second SSSG is determined according to a logical channel priority LCP restriction parameter and/or cross-carrier scheduling configuration of the first logical channel that triggers the SR.

If the first logical channel is not configured with an LCP restriction parameter, determine that the first serving cell set includes all activated serving cells of the terminal device; or,

If the first logical channel is configured with an LCP restriction parameter, determining that the first serving cell set includes serving cells that are allowed to transmit the first logical channel.

If the first serving cell in the first serving cell set is not configured with a cross-carrier scheduling configuration, determine the first serving cell as the scheduling cell of the first serving cell; or

If the first serving cell in the first serving cell set is configured with a cross-carrier scheduling configuration, determine a cell configured in the cross-carrier scheduling configuration of the first serving cell that can indicate uplink scheduling of the first serving cell is the scheduling cell of the first serving cell.

Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip. The aforementioned processing unit may be one or more processors.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of the various units in the terminal device 400 are respectively for realizing the method shown in FIG. 3 . The corresponding process of the terminal device in 200 is not repeated here for brevity.

FIG. 7 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of FIG. 7 includes:

The communication unit 510 is configured to send configuration information to the terminal device, where the configuration information is used to configure whether the terminal device executes the transition from the first SSSG to the second SSSG when the scheduling request SR is sent and the SR is in a waiting state SSSG switching and/or switching conditions from the first SSSG to the second SSSG, wherein the density of the PDCCH listening opportunities corresponding to the second SSSG in the time domain distribution is greater than that of the PDCCH corresponding to the first SSSG The density of listening timings in the time domain distribution.

In some embodiments of the present application, the configuration information includes second configuration information, where the second configuration information is used to configure the terminal device to send an SR, the SR is in a waiting state, and a triggering cause of the SR is secondary In the case of cell beam failure recovery or LBT failure recovery, handover from the first SSSG to the second SSSG is performed.

In some embodiments of the present application, the configuration information includes third configuration information and/or fourth configuration information, where the third configuration information is used to instruct the terminal device to send an SR, the SR is in a waiting state and all The triggering cause of the SR is that the secondary cell beam fails to recover, perform handover from the first SSSG to the second SSSG, and the fourth configuration information is used to instruct the terminal device to send an SR, and the SR is in In the waiting state and the triggering cause of the SR is LBT failure recovery, the handover from the first SSSG to the second SSSG is performed.

In some embodiments of the present application, the configuration information includes configuration information of a logical channel that triggers SR, and the configuration information of the logical channel that triggers SR includes first indication information, and the first indication information is used to indicate that in the In the case that the SR is triggered by the logical channel, whether to allow the SR to trigger the terminal device to switch from the first SSSG to the second SSSG.

In some embodiments of the present application, when the type of the service carried by the logical channel is the first type, the first indication information is used to indicate that the SR is allowed to trigger the terminal device from the first type the SSSG is switched to the second SSSG;

When the type of the service carried by the logical channel is the second type, the first indication information is used to indicate that the SR is not allowed to trigger the terminal device to switch from the first SSSG to the second SSSG SSSG

In some embodiments of the present application, the communication unit 510 is further configured to:

receiving an SR sent by the terminal device, where the SR is sent within a time period during which the terminal device uses the first SSSG to monitor the PDCCH;

Switch to sending the PDCCH using the second SSSG.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 500 are for realizing the method shown in FIG. 3 respectively. The corresponding process of the network device in 200 is not repeated here for brevity.

FIG. 8 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device 600 shown in FIG. 8 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8 , the communication device 600 may further include a memory 620 . The processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.

The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, as shown in FIG. 8 , the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.

Among them, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of the antennas may be one or more.

Optionally, the communication device 600 may specifically be the network device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .

Optionally, the communication device 600 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.

FIG. 9 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in FIG. 9 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.

Optionally, as shown in FIG. 9 , the chip 700 may further include a memory 720 . The processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.

The memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may further include an input interface 730 . The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740 . The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. For brevity, here No longer.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

FIG. 10 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 10 , the communication system 900 includes a terminal device 910 and a network device 920 .

The terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .

It should be understood that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.

Embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.

The embodiments of the present application also provide a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for switching a search space set grouping SSSG by a terminal device, comprising:

During the time period during which the terminal device monitors the physical downlink control channel PDCCH based on the first SSSG, the terminal device sends a scheduling request SR to the network device, and the SR is in a waiting state;

The terminal device switches to the second SSSG under certain conditions, and monitors the PDCCH based on the second SSSG;

The density of the PDCCH listening opportunities corresponding to the second SSSG in the time domain distribution is greater than the density of the PDCCH listening opportunities corresponding to the first SSSG in the time domain distribution.
The method according to claim 1, wherein the method further comprises:

The terminal device determines whether to switch from the first SSSG to the second SSSG according to the triggering cause of the SR and/or the configuration information of the network device.
The method according to claim 2, wherein the terminal device determines whether to switch from the first SSSG to the second SSSG according to the triggering cause of the SR and/or the configuration information of the network device, comprising: :

If the triggering cause of the SR is failure to restore the beam of the secondary cell, determine to switch from the first SSSG to the second SSSG; or

If the triggering cause of the SR is to recover from the failure of the listen-before-talk LBT, it is determined to switch from the first SSSG to the second SSSG.
The method according to claim 2, wherein the terminal device determines whether to switch from the first SSSG to the second SSSG according to the triggering cause of the SR and/or the configuration information of the network device, comprising: :

If the SR is triggered by the first logical channel, determining whether to switch from the first SSSG to the second SSSG according to the configuration information of the first logical channel or the service carried by the first logical channel;

The configuration information of the first logical channel includes first indication information, where the first indication information is used to indicate whether the SR is allowed to trigger the SR when the SR is triggered by the first logical channel The terminal device switches from the first SSSG to the second SSSG.
The method according to claim 4, wherein determining whether to switch from the first SSSG to the second SSSG according to configuration information of the first logical channel or services carried by the first logical channel Two SSSGs, including:

If the first indication information is used to indicate that the SR is allowed to trigger the terminal device to switch from the first SSSG to the second SSSG, determine to switch from the first SSSG to the second SSSG; or

If the first indication information is used to indicate that the SR is not allowed to trigger the terminal device to switch from the first SSSG to the second SSSG, it is determined not to switch from the first SSSG to the second SSSG.
The method according to claim 4, wherein determining whether to switch from the first SSSG to the second SSSG according to configuration information of the first logical channel or services carried by the first logical channel Two SSSGs, including:

If the service carried by the first logical channel is the first type of service, determine to switch from the first SSSG to the second SSSG; or

If the service carried by the first logical channel is the service of the second type, it is determined not to switch from the first SSSG to the second SSSG.
The method according to claim 6, wherein the first type of services includes delay-sensitive services, and the second type of services includes delay-insensitive services.
The method according to any one of claims 2-7, wherein whether the terminal device determines whether to switch from the first SSSG to the second SSSG according to the triggering cause of the SR is determined by the terminal device of.
The method according to any one of claims 2-7, wherein the configuration information of the network device includes first configuration information, wherein the first configuration information is used to configure the terminal device when sending the SR And whether to perform handover from the first SSSG to the second SSSG when the SR is in a waiting state.
The method according to any one of claims 2-7, wherein the configuration information of the network device includes second configuration information, wherein the second configuration information is used to configure the terminal device to send an SR, and the When the SR is in a waiting state and the triggering cause of the SR is secondary cell beam failure recovery or LBT failure recovery, perform handover from the first SSSG to the second SSSG; or

The configuration information of the network device includes third configuration information and/or fourth configuration information, wherein the third configuration information is used to instruct the terminal device to send an SR, the SR is in a waiting state and the triggering cause of the SR In the case of beam failure recovery of the secondary cell, the handover from the first SSSG to the second SSSG is performed, and the fourth configuration information is used to instruct the terminal device to send an SR, the SR is in a waiting state and the When the triggering cause of the SR is LBT failure recovery, the handover from the first SSSG to the second SSSG is performed.
The method according to any one of claims 1-10, wherein the terminal device switches to the second SSSG under a specific condition, and monitors the PDCCH based on the second SSSG, comprising:

When it is determined to switch from the first SSSG to the second SSSG, the terminal device stops monitoring the PDCCH based on the first SSSG and starts monitoring the PDCCH based on the second SSSG.
The method according to any one of claims 1-11, wherein the method further comprises:

The terminal device determines a set of target serving cells to perform handover from the first SSSG to the second SSSG according to the logical channel priority LCP restriction parameter and/or the cross-carrier scheduling configuration of the first logical channel that triggers the SR .
The method according to claim 12, characterized in that, the terminal device determines, according to a logical channel priority LCP restriction parameter and/or a cross-carrier scheduling configuration of a first logical channel that triggers the SR, to execute the process from the first logical channel. The SSSG is handed over to the target serving cell set of the second SSSG, including:

determining a first set of serving cells according to the LCP restriction parameter of the first logical channel;

determining a scheduling cell corresponding to each serving cell according to the cross-carrier scheduling configuration of each serving cell in the first serving cell set, where the scheduling cell corresponding to the serving cell can indicate uplink scheduling of the serving cell;

The scheduling cells corresponding to all serving cells in the first serving cell set are determined as the target serving cell set.
The method according to claim 13, wherein the determining the first serving cell set according to the LCP restriction parameter of the first logical channel comprises:

If the first logical channel is not configured with an LCP restriction parameter, determine that the first serving cell set includes all activated serving cells of the terminal device; or,

If the first logical channel is configured with an LCP restriction parameter, determining that the first serving cell set includes serving cells that are allowed to transmit the first logical channel.
The method according to claim 13 or 14, wherein the determining the scheduling cell corresponding to each serving cell according to the cross-carrier scheduling configuration of each serving cell in the first serving cell set includes the following steps: :

If the first serving cell in the first serving cell set is not configured with a cross-carrier scheduling configuration, determine the first serving cell as the scheduling cell of the first serving cell; or

If the first serving cell in the first serving cell set is configured with a cross-carrier scheduling configuration, determine a cell configured in the cross-carrier scheduling configuration of the first serving cell that can indicate uplink scheduling of the first serving cell is the scheduling cell of the first serving cell.
A method for switching a search space set grouping SSSG by a terminal device, comprising:

The network device sends configuration information to the terminal device, the configuration information is used to configure whether the terminal device performs the handover from the first SSSG to the second SSSG when the scheduling request SR is sent and the SR is in a waiting state /or a switching condition from the first SSSG to the second SSSG, wherein the density of the PDCCH listening occasions corresponding to the second SSSG in the time domain distribution is greater than that of the PDCCH listening occasions corresponding to the first SSSG Density on the domain distribution.
The method according to claim 16, wherein the configuration information includes second configuration information, wherein the second configuration information is used to configure the terminal device to send an SR, the SR is in a waiting state and the SR The triggering cause of is the case that the secondary cell beam fails to recover or the LBT fails to recover, and the handover from the first SSSG to the second SSSG is performed.
The method according to claim 16 or 17, wherein the configuration information includes third configuration information and/or fourth configuration information, wherein the third configuration information is used to instruct the terminal device to send an SR, and the When the SR is in the waiting state and the trigger of the SR is the secondary cell beam failure recovery, the handover from the first SSSG to the second SSSG is performed, and the fourth configuration information is used to indicate that the terminal equipment An SR is sent, and when the SR is in a waiting state and the triggering cause of the SR is LBT failure recovery, the handover from the first SSSG to the second SSSG is performed.
The method according to any one of claims 16-18, wherein the configuration information includes configuration information of a logical channel that triggers SR, and the configuration information of the logical channel that triggers SR includes first indication information, and the The first indication information is used to indicate whether the SR is allowed to trigger the terminal device to switch from the first SSSG to the second SSSG when the SR is triggered by the logical channel.
The method according to claim 19, wherein when the type of the service carried by the logical channel is the first type, the first indication information is used to indicate that the SR is allowed to trigger the terminal device switching from the first SSSG to the second SSSG;

When the type of the service carried by the logical channel is the second type, the first indication information is used to indicate that the SR is not allowed to trigger the terminal device to switch from the first SSSG to the second SSSG SSSG
The method according to claim 20, wherein the first type of services includes delay-sensitive services, and the second type of services includes delay-insensitive services.
The method according to any one of claims 16 to 21, wherein the method further comprises:

receiving, by the network device, an SR sent by the terminal device, where the SR is sent within a time period during which the terminal device uses the first SSSG to monitor the PDCCH;

The network device switches to sending the PDCCH using the second SSSG.
A terminal device, characterized in that it includes:

a communication unit, configured to send a scheduling request SR to a network device, and the SR is in a waiting state;

The processing unit, if the SR is sent within the time period that monitors the physical downlink control channel PDCCH based on the first SSSG, under certain conditions, switches to the second SSSG;

The communication unit is further configured to monitor the PDCCH based on the second SSSG;

The density of the PDCCH listening opportunities corresponding to the second SSSG in the time domain distribution is greater than the density of the PDCCH listening opportunities corresponding to the first SSSG in the time domain distribution.
A network device, characterized in that it includes:

a communication unit, configured to send configuration information to the terminal device, where the configuration information is used to configure whether the terminal device executes the transition from the first SSSG to the second SSSG when the scheduling request SR is sent and the SR is in a waiting state switching and/or switching conditions from the first SSSG to the second SSSG, wherein the density of the PDCCH monitoring occasions corresponding to the second SSSG in the time domain distribution is greater than that of the PDCCH monitoring corresponding to the first SSSG The density of the timing distribution in the time domain.
A terminal device, characterized in that it comprises: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 15. one of the methods described.
A chip, characterized by comprising: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 15 .
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 15.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 15.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 15.
A network device, characterized in that it comprises: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 16 to 22. one of the methods described.
A chip, characterized by comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 16 to 22.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 16 to 22.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 16 to 22.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 16 to 22.