Patent Description:
<NUM> new radio (New Radio, NR) systems support carrier aggregation (Carrier Aggregation, CA), allowing configuration and activation of multiple carriers (Component Carrier, CC) or cells for user equipment (User Equipment, UE) and cross-carrier scheduling under CA. In addition, NR also supports multiple transmission and reception panel (Multiple Transmission and Reception Panel, M-TRP) scenarios, and UE may be scheduled to perform data transmission and reception with multiple TRPs.

In current NR systems, both primary cells (Primary Cells, Pcells) and secondary cells (Secondary Cells, Scells) can be configured to be self-scheduled, but only Scells can be cross-carrier scheduled by a Pcell or another Scell, and Pcells can only be self-scheduled. When an Scell is configured to be cross-carrier scheduled, it is necessary to configure an identifier of a serving cell (serving cell ID) scheduling the cell, and a carrier indicator field (Carrier Indicator Field, CIF for short) value for scheduling by the serving cell.

It can be learned that in existing NR, one cell can be scheduled by only one scheduling cell (meaning that one cell can only be scheduled by the cell itself or another cell). Currently, Pcells can only be self-scheduled. In consideration of enhancing control channel coverage, Pcells are generally deployed on low band carriers (carrier). However, low band carriers have insufficient bandwidth and have been mostly used for deployment of other technologies (for example, LTE).

Therefore, a solution to the problem of limited capacity of Pcell control channels may be configuring high band carriers (carrier) for Scells and using Scell to schedule Pcell, so as to reduce control channel PDCCH overheads. However, no specific scheme has been provided yet as to how a cell scheduling mode is determined for scheduling Pcell by Scell.

D1 (<CIT>) discloses that a cross-carrier scheduling method includes: a network side device sending a high-layer signaling, the high-layer signaling being used for indicating that a primary cell supports cross-carrier scheduling by one or more secondary cells.

D2 ("<NPL>) discloses the discussion for fast Scell activation and dormancy like behavior. In terms of fast Scell activation and dormancy like behavior for activated Scell, D2 provides some proposals respectively. For example, proposal <NUM>: support one of the following two options for fast Scell activation. Option1: support the following aperiodic TRS triggering mechanism; support standalone A-TRS which is not QCL-A with another periodic TRS on the same Scell; support more flexible "aperiodicTriggeringOffset" between the triggering DCI and the RS; support A-TRS transmission after the PUSCH triggered in the same UL grant. Option <NUM>: support MAC CE triggering multiple TRS: in the triggering MAC CE, support to indicate the exact timing of each TRS, which is not QCL-A with another periodic TRS on the same Scell; send LS to RAN2 to specify such MAC CE.

D3 ("<NPL>) discloses the discussion on Scell activation and deactivation. In terms of low latency Scell activation, efficient Scell management, analysis on use of low latency Scell activation vs. efficient Scell management, cross-carrier triggering PDCCH order, and power saving issue in CA. For example, proposal <NUM>: short interval periodic CSI-RS resource and CSI reporting can be supported for low latency of Scell activation.

The objective of embodiments of this application is to provide a method and an apparatus for determining a cell scheduling mode, a terminal, and a network-side device, to determine a cell scheduling mode for scheduling Pcell by Scell.

To resolve the foregoing technical problem, this application is implemented as follows.

According to a first aspect, a method for determining a cell scheduling mode is provided, which is defined in claim <NUM>.

According to a second aspect, an apparatus for determining a cell scheduling mode is provided, which is defined in claim <NUM>.

According to a third aspect, a method for determining a cell scheduling mode is provided, which is defined in claim <NUM>.

According to a fourth aspect, an apparatus for determining a cell scheduling mode is provided, which is defined in claim <NUM>.

According to an eighth aspect, a chip is provided, which is defined in claim <NUM>.

Further advantageous embodiments of the present application are indicated in the dependent claims.

It is to be understood that both the foregoing general description and the following detailed description are exemplary only, and are not restrictive of the present application.

The terms "first", "second", and the like in this specification and claims of this application are used to distinguish between similar objects instead of describing a specific order or sequence. It should be understood that data used in this way is used interchangeably in appropriate circumstances so that the embodiments of this application can be implemented in other orders than the order illustrated or described herein. In addition, objects differentiated by "first" and "second" are usually of a same type. The number of objects is not limited. For example, a first object may indicate one or more objects. In addition, in this specification and claims, "and/or" represents at least one of connected objects, and the symbol "/" generally represents an "or" relationship between the associated objects.

It should be noted that the technologies described in the embodiments of this application are not limited to long term evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) systems, and may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency-division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably. The technology described herein may be used in the foregoing systems and radio technologies as well as other systems and radio technologies. However, in the following descriptions, a new radio (New Radio, NR) system is described for an illustration purpose, and NR terms are used in most of the following descriptions, although these technologies may also be applied to other applications than an NR system application, for example, <NUM>-th generation (<NUM>-th Generation, <NUM>) communication systems.

<FIG> is a block diagram of a wireless communication system to which an embodiment of this application may be applied. The wireless communication system includes a terminal <NUM> and a network-side device <NUM>. The terminal <NUM> may also be referred to as a terminal device or user equipment (User Equipment, UE). The terminal <NUM> may be a terminal-side device such as a mobile phone, a tablet personal computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or an in-vehicle device (VUE), or a pedestrian user equipment (PUE). The wearable device includes a wristband, earphones, glasses, or the like. It should be noted that the terminal <NUM> is not limited to a specific type in the embodiments of this application. The network-side device <NUM> may be a base station or a core network. The base station may be referred to as a NodeB, an evolved NodeB, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a Node B, an evolved node B (eNB), a home NodeB, a home evolved NodeB, a WLAN access point, a Wi-Fi node, a transmission-reception point (Transmitting Receiving Point, TRP), or some other appropriate term in the art. As long as the same technical effect is achieved, the base station is not limited to a specific technical term. It should be noted that the base station in the NR system is used only as an example in the embodiments of this application, and a specific type of the base station is not limited.

The following details the methods for determining a cell scheduling mode provided in the embodiments of this application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.

<FIG> is a schematic flowchart of a method for determining a cell scheduling mode according to an embodiment of this application. The method <NUM> may be performed by a terminal. In other words, the method may be performed by software or hardware installed on the terminal.

Receive scheduling configuration information, where the scheduling configuration information indicates that a second cell of the terminal is scheduled by a first cell of the terminal and that the second cell is capable of self-scheduling.

The first cell is an Scell, and the second cell is a Pcell.

Specifically, the scheduling configuration information may include indication information indicating that the second cell is scheduled by the first cell and that the second cell is capable of self- scheduling.

In a possible implementation, the scheduling configuration information further indicates at least one of the following (<NUM>) to (<NUM>).

In this embodiment of this application, the incomplete USS configuration is a USS configuration that includes only specific fields such as aggregation level and SS ID, and the complete USS configuration can correspond to a specific time-frequency domain USS. If the USS in this application corresponds to an incomplete USS configuration, it must be capable of being mapped for cross-carrier scheduling.

Determine an activity state of the first cell.

In a possible implementation, the activity state of the first cell includes but is not limited to any one of the following:.

It should be noted that although S210 taking place before S212 is used as an example for description in this application, this is not limited thereto. In practical applications, there is no strict time order between S210 and S212.

Determine a scheduling mode for the second cell based on the scheduling configuration information and the activity state.

In a possible implementation, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes:.

In the foregoing possible implementation, a specific RNTI includes but is not limited to at least one of the following: cell RNTI (Cell RNTI, C-RNTI), configured scheduling RNTI (Configured Scheduling RNTI, CS-RNTI), and MCS-C-RNTI.

In the foregoing possible implementation, the search space for cross-carrier scheduling the second cell on the first cell may be a search space that satisfies a specific condition, for example, a search space with a same identifier as a search space in an active BWP of the first cell.

For example, based on an assumption that a Pcell is configured to be scheduled by an Scell <NUM> and that the Pcell is configured with a CSS, if the first cell is in the first target state, it is determined that the Pcell is cross-carrier scheduled by an SS meeting a condition on the Scell <NUM>, but not self-scheduled with scrambling by a specific RNTI (for example, C-RNTI, CS-RNTI, or MCS-C-RNTI) (if the communication device is a terminal, the terminal may not monitor RNTI scrambled self-scheduling on the second cell). In other words, scheduling with a specific RNTI is not performed in the configured CSS and/or USS group <NUM> (if configured). Alternatively, it is determined that the Pcell is cross-carrier scheduled by an SS meeting a condition on the Scell <NUM> and that CSS self-scheduling with scrambling by a specific RNTI is also implemented. In other words, scheduling with a specific RNTI is not performed in the configured USS group <NUM> (if configured), and the terminal may not monitor RNTI scrambled CSS self-scheduling on the second cell.

The determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes:.

According to the foregoing possible implementation, the scheduling mode for the second cell can be determined when the first cell is in the inactive state, the dormancy state, or the state of having no search space capable of scheduling the second cell on the active BWP.

For example, based on an assumption that a Pcell is configured to be scheduled by an Scell <NUM> and that the Pcell is configured with a CSS, if the first cell is in the second target state, it is determined that:.

In the foregoing possible implementation, the some USSs are search spaces in the first UE-specific search space group, and the some USSs have a same identifier as the target search space, where the target search space is a search space in a currently active BWP of the first cell. That is, the some USSs are search spaces in the first USS group that have a same identifier as a search space in a currently active BWP.

For example, it is assumed that the Pcell of the terminal is configured to be scheduled by the Scell <NUM>, and CSS#<NUM>, fully configured USS#<NUM> and USS# <NUM>, and non-fully configured USS#<NUM> and USS#<NUM> (configured with only an SS ID and an aggregation level) are configured on BWP#<NUM>. In addition, the Pcell can be scheduled only by a USS of the Scell corresponding to a non-fully configured USS ID.

USS#<NUM> is configured on BWP#<NUM> of the Scell <NUM>, and USS#<NUM> is configured on BWP#<NUM>. At this time, BWP#<NUM> of the Scell <NUM> is the active BWP. Therefore, in this case, self-scheduling is not performed in USS#<NUM> and USS#<NUM> of the Pcell.

At an effective moment corresponding to a MAC CE for inactivity received by the UE in the Scell <NUM>, or when sCellDeactivationTimer expires, or at an effective moment corresponding to received DCI indicating that the Scell <NUM> enters the dormancy state, self-scheduling function is enabled in USS#<NUM> and USS#<NUM>.

Alternatively, when the UE receives DCI in the Scell <NUM>, where the DCI indicates switching from BWP#<NUM> to BWP#<NUM>, or at an effective moment of BWP switching for switching to BWP#<NUM> after an inactivity timer of BWP#<NUM> expires, self-scheduling function is enabled in USS#<NUM> and USS#<NUM>.

Optionally, CSS#<NUM> may have self-scheduling always on, or may enable or disable self-scheduling like USS#<NUM> and USS#<NUM>.

In still another possible implementation, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state may include:.

In the foregoing possible implementation, the first target information includes but is not limited to any one of the following: deactivation signaling for the first cell, control information indicating transitioning from non-dormancy state to dormancy state, and control information indicating switching from the first BWP to the second BWP.

For example, based on an assumption that a Pcell is configured to be scheduled by an Scell <NUM> and that the Pcell is configured with a CSS, if the first cell is in the second target state, the terminal may determine to enable a function of scheduling with a specific RNTI in the configured CSS and/or a USS group <NUM> (if configured) at a first target moment after deactivation signaling for the Scell <NUM>, or DCI indicating switching from non-dormancy to dormancy, or DCI indicating BWP switching is received.

In a possible implementation, the first target moment includes any one of the following: an effective moment of an event indicated by the first target information; when a predetermined time has elapsed since an effective moment of an event indicated by the first target information; and a moment configured by radio resource control (Radio Resource Control, RRC) signaling. The predetermined time may be configured by a network side or predefined, which is not specifically limited in this embodiment.

For example, the first target moment is a moment when the Scell is inactive, a moment when the Scell enters the dormancy state, or a moment when BWP switching takes effect; or the first target moment is a specific time after the Scell is inactive, a specific time after the Scell enters the dormancy state, or a specific time after an effective moment of BWP switching.

Alternatively, in a possible implementation, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state may include:.

In the foregoing possible implementation, optionally, the target timer includes a cell deactivation timer or a BWP inactivity timer.

In the foregoing possible implementation, optionally, the second target moment includes any one of the following:.

For example, assuming that a Pcell is configured to be scheduled by an Scell <NUM> and that the Pcell is configured with a CSS, expiration of a cell deactivation timer (sCellDeactivationTimer) of the Scell <NUM> triggers the Scell <NUM> to change from the active state to the inactive state, or expiration of a BWP inactivity timer (bwpInactivityTimer) of a current BWP (second BWP) of the Scell <NUM> triggers BWP switching of the Scell <NUM>. A function of scheduling with a specific RNTI is enabled for the configured CSS and/or a USS group <NUM> (if configured) at a specific moment after the Scell <NUM> switches from the active state to the inactive state or the Scell <NUM> performs BWP switching.

The specific moment is an effective moment of Scell deactivation or an effective moment of BWP switching after a timer expires; or.

In a possible implementation, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state may include:.

In the foregoing possible implementation, the third target moment includes any one of the following:.

In foregoing possible implementation, the second target information includes any one of the following:.

For example, it is assumed that a Pcell is configured to be scheduled by an Scell <NUM> and that the Pcell is configured with a CSS. When the Scell <NUM> is switching from the inactive state to the active state, switching from dormancy to non-dormancy, and/or in BWP switching (changing from a BWP capable of scheduling the Pcell to a state of having no BWP capable of scheduling the Pcell), the UE disables a function of scheduling with a specific RNTI in the configured CSS and/or a USS group <NUM> (if configured) at a specific movement after an activation MAC CE for the Scell <NUM>, or DCI indicating switching from dormancy to non-dormancy, or DCI indicating BWP switching (that is, the third target moment) is received.

The specific moment is an effective moment of Scell <NUM> activation, the Scell <NUM> entering the non-dormancy state, or BWP switching.

Alternatively, the specific moment is a moment that is a specific time after an effective moment of Scell activation, a moment that is a specific time after an effective moment of the Scell entering the non-dormancy state, or a moment that is a specific time after an effective moment of BWP switching.

Alternatively, the specific moment is a moment configured by RRC signaling.

In the foregoing possible implementation, the method may further include: in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, determining a behavior undesired by the terminal through pre-negotiation, where the behavior undesired by the terminal includes at least one of the following:.

With the foregoing possible implementations, the UE does not expect the first cell to switch to a state in which the second cell cannot be scheduled, so as to ensure normal scheduling of the second cell by the first cell.

In a possible implementation, the method further includes: in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, ignoring at least one of the following:.

In the foregoing possible implementations, optionally, the execution body may be a terminal. In other words, a network-side device may perform any one of the foregoing operations, but the terminal ignores such operation, that is, such operation does not take effect.

With the technical solutions provided in the embodiments of this application, the scheduling configuration information is received, where the scheduling configuration information indicates that the second cell is scheduled by the first cell and that the second cell is capable of self-scheduling; the activity state of the first cell is determined; and the scheduling mode for the second cell is determined based on the scheduling configuration information and the activity state. With the foregoing technical solutions provided in the embodiments of this application, in a case that the second cell is scheduled by the first cell and that the second cell is capable of self-scheduling, the scheduling mode of the second cell is determined based on the activity state of the first cell and the scheduling configuration information. This provides a solution for determining the scheduling mode for the first cell to schedule the second cell, and addresses the issue of how a cell scheduling mode is determined for Scell to schedule Pcell.

It should be noted that the method for determining a cell scheduling mode in the embodiment of this application may be performed by an apparatus for determining a cell scheduling mode, or a control module for performing the method for determining a cell scheduling mode in an apparatus for determining a cell scheduling mode. The embodiments of this application describe the apparatus for determining a cell scheduling mode provided in an embodiment of this application by using an example in which the apparatus for determining a cell scheduling mode performs the method for determining a cell scheduling mode.

<FIG> is a schematic structural diagram of an apparatus for determining a cell scheduling mode according to an embodiment of this application. As shown in <FIG>, the apparatus <NUM> for determining a cell scheduling mode includes a receiving module <NUM>, a first determining module <NUM>, and a second determining module <NUM>.

The receiving module <NUM> is configured to receive scheduling configuration information, where the scheduling configuration information indicates that a second cell of a terminal is scheduled by a first cell of the terminal and that the second cell is capable of self-scheduling; the first determining module <NUM> is configured to determine an activity state of the first cell; and the second determining module <NUM> is configured to determine a scheduling mode for the second cell based on the scheduling configuration information and the activity state.

In a possible implementation, the scheduling configuration information further indicates at least one of the following:.

In a possible implementation, in a case that one complete UE-specific search space is a search space capable of being mapped for cross-carrier scheduling, the complete UE-specific search space belongs to both the first UE-specific search space group and the second UE-specific search space group.

In a possible implementation, the activity state of the first cell includes any one of the following:.

In a possible implementation, that the second determining module <NUM> determines a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes:.

That the second determining module <NUM> determines a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes:.

In a possible implementation, the some USSs are search spaces in the first UE-specific search space group, and the some USSs have a same identifier as a target search space, where the target search space is a search space in a currently active BWP of the first cell.

In a possible implementation, the first target information includes any one of the following: deactivation signaling for the first cell, control information indicating transitioning from non-dormancy state to dormancy state, and control information indicating switching from the first BWP to the second BWP.

In a possible implementation, the first target moment includes any one of the following:.

In a possible implementation, the target timer includes a cell deactivation timer or a BWP inactivity timer.

In a possible implementation, the second target moment includes any one of the following:.

In a possible implementation, the third target moment includes any one of the following:.

In a possible implementation, the second target information includes any one of the following:.

In a possible implementation, the first determining module <NUM> is further configured to:
in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, determine a behavior undesired by the terminal through pre-negotiation, where the behavior undesired by the terminal includes at least one of the following:.

In a possible implementation, the first determining module <NUM> is further configured to:
in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, ignore at least one of the following:.

The first cell is a secondary cell, and the second cell is a primary cell.

The apparatus for determining a cell scheduling mode in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip of a terminal. The apparatus may be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include but is not limited to types of the terminal <NUM> listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine, a self-service machine, or the like. This is not specifically limited in the embodiments of this application.

The apparatus for determining a cell scheduling mode in this embodiment of this application may be an apparatus having an operating system. The operating system may be an Android (Android) operating system, may be an iOS operating system, or may be another possible operating system. This is not specifically limited in the embodiments of this application.

The apparatus for determining a cell scheduling mode provided in this embodiment of this application can implement the processes implemented in the method embodiment in <FIG>, with the same technical effects achieved. To avoid repetition, details are not described herein again.

<FIG> is a schematic flowchart of a method for determining a cell scheduling mode according to an embodiment of this application. The method <NUM> may be performed by a network-side device. In other words, the method may be performed by software or hardware installed on the network-side device.

Transmit scheduling configuration information, where the scheduling configuration information indicates that a second cell of a terminal is scheduled by a first cell of the terminal and that the second cell is capable of self-scheduling.

Determine an activity state of the first cell.

Determine a scheduling mode for the second cell based on the scheduling configuration information and the activity state.

The method <NUM> is a method for a network-side device corresponding to the method <NUM>, and has similar possible implementations to the method <NUM> except that the scheduling configuration information is transmitted by a network-side device in the method <NUM> and received by a terminal in the method <NUM>. The following mainly describes some implementations of the method <NUM>. For relevant details not described, reference may be made to the descriptions in the method <NUM>.

Optionally, the scheduling configuration information further indicates at least one of the following: a common search space configured on the second cell; a first UE-specific search space group configured on the second cell, where the first UE-specific search space group includes one or more complete UE-specific search spaces; a second UE-specific search space group configured on the second cell, where the second UE-specific search space group includes one or more incomplete UE-specific search spaces, or the second UE-specific search space group includes one or more UE-specific search spaces that are capable of being mapped for cross-carrier scheduling; and a search space configured on the first cell.

Optionally, in a case that one complete UE-specific search space is a search space capable of being mapped for cross-carrier scheduling, the complete UE-specific search space belongs to both the first UE-specific search space group and the second UE-specific search space group.

Optionally, the activity state of the first cell includes any one of the following: the active state; the inactive state; transitioning from the active state to the inactive state; transitioning from the inactive state to the active state; the dormancy state; the non-dormancy state; transitioning from the dormancy state to the non-dormancy state; transitioning from the non-dormancy state to the dormancy state; having a search space capable of scheduling the second cell on an active BWP; having no search space capable of scheduling the second cell on an active BWP; switching from a first BWP to a second BWP, where the first BWP has a search space capable of scheduling the second cell, and the second BWP has no search space capable of scheduling the second cell; and switching from the second BWP to the first BWP.

Optionally, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes: in a case that the first cell is in a first target state, determining that the second cell is cross-carrier scheduled by the search space on the first cell, and that scheduling with scrambling by a specific radio network temporary identifier RNTI is not performed in the CSS configured on the second cell and/or the first UE-specific search space group; or determining that the second cell is cross-carrier scheduled by the search space on the first cell, that scheduling with scrambling by a specific RNTI is performed in the CSS configured on the second cell, and that scheduling with scrambling by a specific RNTI is not performed in the first UE-specific search space group; where the first target state includes at least one of the following: active state; non-dormancy state; and having a search space capable of scheduling the second cell on the active BWP.

The determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes: in a case that the first cell is in a second target state, determining that the first cell is incapable of scheduling the second cell, and that scheduling with scrambling by a specific RNTI is performed in the CSS configured on the second cell and/or some or all USSs in the first UE-specific search space group; or determining that the first cell is incapable of scheduling the second cell, that CSS self-scheduling with scrambling by a specific RNTI is performed on the second cell, and that scheduling with scrambling by a specific RNTI is performed in the CSS configured on the second cell and some or all USSs in the first UE-specific search space group; where the second target state includes at least one of the following: the inactive state; the dormancy state; and having no search space capable of scheduling the second cell on the active BWP.

Optionally, the some USSs are search spaces in the first UE-specific search space group, and the some USSs have the same identifier as the target search space, where the target search space is a search space in a currently active BWP of the first cell.

Optionally, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes: in a case that the first cell is in a third target state, at a first target moment after first target information is transmitted, enabling a function of performing scheduling with scrambling by a specific RNTI in the CSS configured on the second cell and/or the first UE-specific search space group; where
the third target state includes at least one of the following: transitioning from the active state to the inactive state; transitioning from the non-dormancy state to the dormancy state; and switching from the first BWP to the second BWP.

Optionally, the first target information includes any one of the following: deactivation signaling for the first cell, control information indicating transitioning from non-dormancy state to dormancy state, and control information indicating switching from the first BWP to the second BWP.

Optionally, the first target moment includes any one of the following: an effective moment of an event indicated by the first target information; when a predetermined time has elapsed since an effective moment of an event indicated by the first target information; and a moment configured by radio resource control RRC signaling.

Optionally, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes: in a case that the first cell is in a third target state, at a second target moment after a target timer expires, enabling a function of performing scheduling with scrambling by a specific RNTI in the CSS configured on the second cell and/or the first UE-specific search space group; where the third target state includes at least one of the following: transitioning from the active state to the inactive state; transitioning from the non-dormancy state to the dormancy state; and switching from the first BWP to the second BWP.

Optionally, the target timer includes a cell deactivation timer or a BWP inactivity timer.

Optionally, the second target moment includes: an effective moment of an event indicated by the expiration of the target timer; when a predetermined time has elapsed since an effective moment of an event indicated by the expiration of the target timer; or a moment configured by RRC signaling.

Optionally, the determining a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes: in a case that the first cell is in a fourth target state, at a third target moment after second target information is transmitted, disabling a function of performing scheduling with scrambling by a specific RNTI in the CSS configured on the second cell and/or the first UE-specific search space group; where the fourth target state includes at least one of the following: transitioning from the inactive state to the active state; transitioning from the dormancy state to the non-dormancy state; and switching from the second BWP to the first BWP.

Optionally, the third target moment includes any one of the following: an effective moment of an event indicated by the second target information; when a predetermined time has elapsed since an effective moment of an event indicated by the second target information; and a moment configured by RRC signaling.

Optionally, the second target information includes any one of the following: activation signaling for activating the first cell; control information indicating that the first cell transitions from dormancy state to non-dormancy state; and control information indicating that the first cell switches from the second BWP to the first BWP.

Optionally, the method further includes: in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, determining a behavior undesired by the terminal through pre-negotiation, where the behavior undesired by the terminal includes at least one of the following: transmitting control signaling for deactivating the first cell; configuring a cell deactivation timer for the first cell; and configuring a BWP inactivity timer for a BWP of the first cell capable of scheduling the second cell; and
switching from a BWP of the first cell capable of scheduling the second cell to a BWP of the first cell incapable of scheduling the second cell.

Optionally, the method further includes: in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, ignoring at least one of the following: control signaling for deactivating the first cell; configuring a cell deactivation timer for the first cell;
configuring a BWP inactivity timer for a BWP of the first cell capable of scheduling the second cell; and control information indicating switching from a BWP of the first cell capable of scheduling the second cell to a BWP of the first cell incapable of scheduling the second cell.

<FIG> is a schematic structural diagram of an apparatus for determining a cell scheduling mode according to an embodiment of this application. As shown in <FIG>, the apparatus <NUM> includes a transmitting module <NUM>, configured to transmit scheduling configuration information, where the scheduling configuration information indicates that a second cell of a terminal is scheduled by a first cell of the terminal and that the second cell is capable of self-scheduling; a third determining module <NUM>, configured to determine an activity state of the first cell; and a fourth determining module <NUM>, configured to determine a scheduling mode for the second cell based on the scheduling configuration information and the activity state.

In a possible implementation, that a fourth determining module <NUM> determines a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes:.

That a fourth determining module <NUM> determines a scheduling mode for the second cell based on the scheduling configuration information and the activity state includes:.

In a possible implementation, the some USSs are search spaces in the first UE-specific search space group, and the some USSs have the same identifier as the target search space, where the target search space is a search space in a currently active BWP of the first cell.

In a possible implementation, the third determining module <NUM> is further configured to:
in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, determine a behavior undesired by the terminal through pre-negotiation, where the behavior undesired by the terminal includes at least one of the following:.

In a possible implementation, the third determining module <NUM> is further configured to:
in a case that the scheduling configuration information indicates that the second cell is scheduled by the first cell, ignore at least one of the following:.

Optionally, as shown in <FIG>, an embodiment of this application further provides a communication device <NUM>, including a processor <NUM>, a memory <NUM>, and a program or instructions stored in the memory <NUM> and executable on the processor <NUM>. For example, if the communication device <NUM> is a terminal, when the program or the instructions are executed by the processor <NUM>, the processes of the foregoing embodiments of the method for determining a cell scheduling mode are implemented, with the same technical effects achieved. If the communication device <NUM> is a network-side device, when the program or the instructions are executed by the processor <NUM>, the processes of the foregoing embodiments of the method for determining a cell scheduling mode are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein again.

<FIG> is a schematic diagram of a hardware structure of a terminal implementing an embodiment of this application.

The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, and a processor <NUM>.

A person skilled in the art can understand that the terminal <NUM> may further include a power supply (such as a battery) for supplying power to the components. The power supply may be logically connected to the processor <NUM> through a power management system. In this way, functions such as charge management, discharge management, and power consumption management are implemented by using the power management system. The terminal structure shown in <FIG> does not constitute a limitation to the terminal. The terminal may include more or fewer components than shown in the figure, or a combination of some components, or components disposed differently.

It should be noted that in this embodiment of this application, the input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a static picture or a video that is obtained by an image capture apparatus (for example, a camera) in a video capture mode or an image capture mode. The display unit <NUM> may include a display panel <NUM>. The display panel <NUM> may be configured in a form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit <NUM> includes a touch panel <NUM> and other input devices <NUM>. The touch panel <NUM> is also referred to as a touchscreen. The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The other input devices <NUM> may include but are not limited to a physical keyboard, a functional button (for example, a volume control key or a power on/off key), a trackball, a mouse, and a joystick.

In this embodiment of this application, the radio frequency circuit <NUM> transmits downlink data received from a network-side device to the processor <NUM> for processing, and in addition, transmits uplink data to the network-side device. Generally, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory <NUM> may be configured to store software programs or instructions, and various data. The memory <NUM> may mainly include a program or instruction storage area and a data storage area. The program or instruction storage area may store an operating system, an application program or instructions required by at least one function (for example, an audio play function and an image play function), and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may further include a non-volatile memory. 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 erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory, for example, at least one magnetic disk storage device, a flash storage device, or another non-volatile solid-state storage device.

The processor <NUM> may include one or more processing units. Optionally, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, an application program or instructions, and the like. The modem processor mainly processes wireless communication, for example, a baseband processor. It should be understood that alternatively, the modem processor may not be integrated into the processor <NUM>.

The radio frequency unit <NUM> is configured to receive scheduling configuration information, where the scheduling configuration information indicates that a second cell of the terminal is scheduled by a first cell of the terminal and that the second cell is capable of self-scheduling;.

The processor <NUM> determines an activity state of the first cell, and determines a scheduling mode for the second cell based on the scheduling configuration information and the activity state.

The terminal in this embodiment of the present invention further includes instructions or a program stored in the memory <NUM> and executable on the processor <NUM>. The processor <NUM> invokes the instructions or program in the memory <NUM> to perform the method performed by the modules in <FIG>, with the same technical effects achieved. To avoid repetition, details are not described herein again.

Specifically, an embodiment of this application further provides a network-side device. As shown in <FIG>, the network-side device <NUM> includes an antenna <NUM>, a radio frequency apparatus <NUM>, and a baseband apparatus <NUM>. The antenna <NUM> is connected to the radio frequency apparatus <NUM>. In an uplink direction, the radio frequency apparatus <NUM> receives information by using the antenna <NUM>, and transmits the received information to the baseband apparatus <NUM> for processing. In a downlink direction, the baseband apparatus <NUM> processes to-be-transmitted information, and transmits the information to the radio frequency apparatus <NUM>; and the radio frequency apparatus <NUM> processes the received information and then transmits the information by using the antenna <NUM>.

The radio frequency apparatus may be located in the baseband apparatus <NUM>. The method performed by the network-side device in the foregoing embodiment may be implemented by the baseband apparatus <NUM>, and the baseband apparatus <NUM> includes a processor <NUM> and a memory <NUM>.

The baseband apparatus <NUM> may include, for example, at least one baseband processing unit, where a plurality of chips are disposed on the baseband processing unit. As shown in <FIG>, one of the chips, for example, the processor <NUM>, is connected to the memory <NUM>, to invoke the program in the memory <NUM> to perform the operations of the network device shown in the foregoing method embodiment.

The baseband apparatus <NUM> may further include a network interface <NUM>, configured to exchange information with the radio frequency apparatus <NUM>, where the interface is, for example, a common public radio interface (common public radio interface, CPRI for short).

Specifically, the network-side device in this embodiment of the present invention further includes instructions or a program stored in the memory <NUM> and executable on the processor <NUM>. The processor <NUM> invokes the instructions or program in the memory <NUM> to perform the method performed by the modules in <FIG>, with the same technical effects achieved. To avoid repetition, details are not described herein again.

An embodiment of this application further provides a readable storage medium, where the readable storage medium stores a program or instructions, and when the program or instructions are executed by a processor, the processes of the foregoing embodiments of the methods for determining a cell scheduling mode are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein again.

The processor is the processor of the terminal or the network-side device in the foregoing embodiments. The readable storage medium includes a computer-readable storage medium such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disc.

An embodiment of this application further provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions of a network-side device to implement the processes of the foregoing embodiments of the methods for determining a cell scheduling mode, with the same technical effects achieved. To avoid repetition, details are not described herein again.

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

It should be noted that, in this specification, the terms "include", "include", or any of their variants are intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a series of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such a process, method, article, or apparatus. In the absence of more restrictions, an element defined by "including a. " does not exclude another same element in a process, method, article, or apparatus that includes the element. In addition, it should be noted that the scopes of the method and apparatus in the embodiments of this application are not limited to performing functions in the sequence shown or discussed, and may further include performing functions at substantially the same time or in a reverse sequence according to the involved functions. For example, the described method may be performed in a sequence different from the described sequence, and steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

By means of the foregoing description of the embodiments, persons skilled in the art may clearly understand that the method in the foregoing embodiments may be implemented by software with a necessary general hardware platform. Certainly, the method in the foregoing embodiments may also be implemented by hardware. However, in many cases, the former is a preferred embodiment. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art may be implemented in a form of a software product. The software product is stored in a storage medium (for example, ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of this application.

Claim 1:
A method for determining a cell scheduling mode, performed by a terminal (<NUM>) and comprising:
receiving (S210) scheduling configuration information, wherein the scheduling configuration information indicates that a second cell of the terminal (<NUM>) is scheduled by a first cell of the terminal (<NUM>) and that the second cell is capable of self-scheduling;
determining (S212) an activity state of the first cell; wherein the first cell is a secondary cell and the second cell is a primary cell; and characterized in that
determining (S214) a scheduling mode for the second cell based on the scheduling configuration information and the activity state; wherein the determining (S214) the scheduling mode for the second cell based on the scheduling configuration information and the activity state comprises:
in a case that the first cell is in a second target state, determining that the first cell is incapable of scheduling the second cell, determining self-scheduling for the second cell and that scheduling with scrambling by a specific radio network temporary identifier, RNTI, is performed in a common search space, CSS, configured on the second cell and/or some or all UE-specific search spaces, USSs, in a first UE-specific search space group, wherein
the second target state comprises at least one of following: an inactive state; a dormancy state; and having no search space capable of scheduling the second cell on an active bandwidth part, BWP.