Service cell status management

Abstract

The present invention relates to methods, systems and devices related to digital wireless communication, and more particularly to technologies related to maintaining the state of a serving cell. In one exemplary aspect, a wireless communication method includes detecting the occurrence of an event. The method also includes modifying the state configuration of a serving cell based on the occurrence of the event.

Description

Technical Field

[0001] This patent document relates generally to wireless communications. Background Art

[0002] Mobile communication technologies are driving the world towards an increasingly connected and networked society. The rapid development and technological advancement of mobile communications have led to greater demands for capacity and connectivity. Other aspects, such as energy consumption, equipment cost, spectrum efficiency and latency, are also important to meet the needs of various communication scenarios. Various technologies are being discussed, including new methods to provide higher quality of service. Summary of the invention

[0003] This document discloses methods, systems, and devices related to digital wireless communications, and more particularly, discloses techniques related to maintaining serving cell status.

[0004] In one exemplary aspect, a wireless communication method is disclosed. The method includes detecting an occurrence of an event. The method also includes modifying a state configuration of a serving cell based on the occurrence of the event.

[0005] In another exemplary aspect, a wireless communication device including a processor is disclosed. The processor is configured to implement the methods described herein.

[0006] In yet another exemplary aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

[0007] The details of one or more embodiments are set forth in the accompanying appendix, the drawings, and the description below. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 An exemplary schematic diagram of a system architecture for dual connectivity (DC) is shown.

[0009] Figure 2 A block diagram illustrating a method of managing the status of a serving cell.

[0010] Figure 3 A block diagram of a method of restoring a failed beam of a serving cell is shown.

[0011] Figure 4 A block diagram of configuring and activating a TCI state configuration is shown.

[0012] Figure 5 A block diagram of a method of managing a serving cell is shown.

[0013] Figure 6An example of a wireless communication system to which the technology according to one or more embodiments of the present technology can be applied is shown.

[0014] Figure 7 A block diagram representation of a portion of a hardware platform. DETAILED DESCRIPTION

[0015] The development of the next generation of wireless communications - 5G New Radio (NR) communications - is part of the continuous mobile broadband evolution process to meet the requirements of growing network demand. NR will provide greater throughput to allow more users to connect simultaneously. Other aspects such as energy consumption, equipment cost, spectrum efficiency and latency are also important to meet the needs of various communication scenarios.

[0016] With the rise of NR in the wireless world, UEs will be able to support both protocols simultaneously. Figure 1 An exemplary schematic diagram of a system architecture for dual connectivity (DC) is shown. The current base station in the core network 103 (referred to as the first network element 101) can select a suitable base station for the UE 100 to serve as the second network element 102. For example, a suitable base station can be selected by comparing the channel quality of the base station with a predetermined threshold. Both base stations can provide the UE 100 with radio resources for data transmission on the user plane. On the wired interface side, the first network element 101 and the core network 103 establish a control plane interface 104 for the UE 100. The second network element 102 and the core network 103 can establish a user plane interface 105 for the UE 100. An interface 106 (e.g., an Xn interface) interconnects the two network elements. On the wireless interface side, the first and second network elements (101 and 102) can use the same or different radio access technologies (RATs) to provide radio resources. Each network element can independently schedule transmissions with the UE 100. A network element having a control plane connection to the core network is referred to as a primary node (e.g., first network element 101), and a network element having only a user plane connection to the core network is referred to as a secondary node (e.g., second network element 102). In some cases, UE 100 may be connected to more than two nodes, with one node acting as the primary node and the remaining nodes acting as secondary nodes.

[0017] In some embodiments, the UE may support LTE-NR dual connectivity (DC). For example, one of the typical LTE-NR dual connectivity architectures may be established as follows: the primary node is an LTE RAN node (e.g., eNB), and the secondary node is an NR RAN node (e.g., gNB). The eNB and gNB are simultaneously connected to an evolved packet core (EPC) network (e.g., LTE core network). Figure 1The architecture shown in can also be modified to include various primary / secondary node configurations. For example, the NR RAN node can be the primary node and the LTE RAN node can be the secondary node. In this case, the core network for the primary NR RAN node is the next generation converged network (NG-CN).

[0018] The UE functions for the LTE protocol and the NR protocol in LTE-NR DC include two parts: the common functions of the UE for the LTE and NR protocols applicable to single connection scenarios, and the band combination functions of the UE related to dual connection scenarios. When the UE has multiple simultaneous connections with a network node, the frequency bands used for different network nodes must cooperate with each other regardless of the RAT type used. Here, the term "cooperation" means that the UE can operate in the frequency band without any conflict or substantial interference, that is, the frequency bands can coexist. For example, the Third Generation Partnership Project (3GPP) standard specifies a set of frequency band combinations that can cooperate with each other. If Band 1 and Band 2 are not designated as valid band combinations, the UE cannot simultaneously use Band 1 to communicate with Node 1 and use Band 2 to communicate with Node 2.

[0019] This patent document describes techniques that can be implemented to manage the configuration state of a serving cell. In some cases, a base station (or "network node") can add a secondary cell (SCell) to an activated cell group. A UE (or "terminal") can start monitoring a physical downlink control channel (PDCCH) on the SCell and, after the terminal receives an RRC message containing configuration information for adding the SCell, prepare for uplink transmission (e.g., physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH)).

[0020] In some systems, the SCell can be configured as any of an activated state, a deactivated state, or a dormant state based on the reception of a media access control (MAC) control element (CE) or an RRC message. When the SCell is in the dormant state, the SCell can be configured with a dormant state-specific channel quality indication (CQI) resource. The UE can perform channel monitoring and CQI reporting without monitoring the PDCCH. If the SCell is in the deactivated state, the UE may not perform CQI reporting or PDCCH monitoring on the SCell. In the case of CQI reporting in the dormant state, the time domain delay required to activate the SCell in the dormant state may be less than the time domain delay required from the deactivated state.

[0021] However, some systems do not address issues when implementing similar functionality to 5G New Radio (NR) systems. These issues may include bandwidth part (BWP) operation, beam management, uplink time alignment when transitioning or switching a serving cell from a dormant state or keeping a serving cell in a dormant state.

[0022] In any exemplary embodiment of the present disclosure, the base station may configure the serving cell as a cell group in one of an activated, deactivated or dormant state through an RRC message or a MAC CE. The base station may configure one or more timers to control the state transition of the serving cell. Specifically, the base station may configure a deactivation timer that controls whether the serving cell state is switched to a deactivated state, or a dormancy timer that controls whether the serving cell state is switched to a dormant state. For example, if the deactivation timer associated with the serving cell expires, the UE may convert / modify the serving cell state to a deactivated state. Similarly, if the dormancy timer associated with the serving cell expires, the UE may convert / modify the serving cell to a dormant state when the serving cell is in an activated state.

[0023] In any exemplary embodiments of the present disclosure, the configuration configured for the serving cell may be serving cell specific, ie common to all UEs and / or UE specific, ie different UEs may be configured with a configuration specific to the serving cell.

[0024] Example embodiment 1:

[0025] Exemplary embodiment 1 relates to BWP operation when adding a serving cell and modifying the status of a serving cell. Typically, a BWP may be a frequency domain segment within the cell carrier bandwidth. The BS may configure one or more BWPs for a serving cell via an RRC message or system information. In one embodiment, each BWP may include at least one of an uplink BWP configuration and a downlink BWP configuration, and each BWP may be assigned a BWP identifier (or BWP ID).

[0026] Figure 2A block diagram of a method for managing the state of a serving cell is shown. The state of a serving cell included in a cell group may be configured by one of a base station or a terminal (block 202). The BS may configure a serving cell with one of a default BWP, an initial BWP, and a first active BWP by allocating a BWP ID to each BWP or by configuring a set of parameters for the BWP. Specifically, a default downlink BWP ID (defaultDownlinkBWP-Id), a default uplink BWP ID, an initial downlink BWP (initialDownlinkBWP), an initial uplink BWP (initialUplinkBWP), a first active downlink BWP ID (firstActiveDownlinkBWP-Id), and a first active uplink BWP ID (firstActiveUplinkBWP-Id) may be configured for the serving cell.

[0027] For a serving cell, one or more BWPs may be activated by the UE, which may be referred to as active BWPs. Active BWPs may include active uplink BWPs and active downlink BWPs. The UE may be configured with a BWP inactivity timer associated with an active BWP. In one embodiment, when the BWP inactivity timer expires, the UE may modify / switch the active BWP to one of the following: if a default downlink BWP is configured for the serving cell, modify / switch to the default BWP (indicated by defaultDownlinkBWP-Id), or if a default downlink BWP is not configured for the serving cell, modify / switch to the initial BWP (indicated by initialDownlinkBWP). As part of the active BWP switching / modification, the BWP inactivity timer associated with the new active BWP may be started or restarted if the timer has already started.

[0028] The terminal may modify the state configuration of the serving cell (block 204).

[0029] In the first case, when the serving cell is added to the cell group, the serving cell may be configured in a dormant state. In one embodiment, the terminal may activate a downlink (DL) BWP or an uplink (UL) BWP according to the first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and the first active uplink BWP (indicated by firstActiveUplinkBWP-Id) configured for the serving cell, respectively.

[0030] In one embodiment, the UE may activate the DL BWP or UL BWP according to the first active downlink BWP for the dormant state and the first active uplink BWP for the dormant state. The base station may configure the serving cell with the first active downlink BWP for the dormant state or the first active uplink BWP for the dormant state via an RRC message or system information for the serving cell. The first active BWP configuration for modifying the serving cell state to the dormant state may be different from the configuration for modifying the serving cell state to the activated state.

[0031] In one embodiment, if a default BWP configuration is configured by the BS for this serving cell, the UE may activate DL BWP or UL BWP according to the default downlink BWP configuration or the default uplink BWP configuration. If no default BWP is configured in the serving cell, the DL BWP and UL BWP may be activated according to the initial BWP configuration configured for the serving cell.

[0032] In one embodiment, the UE may activate the DL BWP or the ULBWP according to the initial BWP configuration configured for the serving cell.

[0033] In the second case, the serving cell may be modified from an activated state to a dormant state. In this case, the UE may maintain the current active BWP for the serving cell. The UE may maintain the associated BWP inactivity timer running or restart the associated BWP inactivity timer if the timer is running. This may indicate that when the serving cell state is modified from an activated state to a dormant state, no BWP modification / switching may be performed until the associated BWP inactivity timer expires or signaling via PDCCH is received to switch the active BWP for this serving cell.

[0034] In one embodiment, the currently active BWP of the serving cell may remain active. The UE may also stop the BWP inactivity timer associated with the active BWP if the BWP inactivity timer is running. If the serving cell is modified / switched from an activated state to a dormant state, the active BWP of the serving cell may be the same as when it was in an activated state. The BWP switch may be triggered by receiving a message, receiving a MAC CE, or a PDCCH DCI indicating a BWP modification of the serving cell.

[0035] In one embodiment, the active BWP may be modified / switched to a BWP used when the serving cell is switched / modified from an activated state to a dormant state. The BWP may include a downlink BWP or an uplink BWP. The BWP may be configured to be activated when the associated serving cell is switched / modified from an activated state to a dormant state. The BWP may be configured by the base station via an RRC message or system information, or indicated by a MAC CE or PDCCH DCI used to modify the serving cell to a dormant state. The UE may start or restart the BWP inactivity timer when the BWP is switched.

[0036] In one embodiment, if a default BWP is configured for the serving cell, the active BWP may be switched to the default BWP. Otherwise, if an initial BWP is configured for the serving cell, the UE may perform a BWP switch to the initial BWP. If the serving cell state transitions / switches from active to dormant, the active BWP of the serving cell may be different from the active BWP before the serving cell state transition.

[0037] If the serving cell is configured with uplink radio resources for channel quality information (CQI) or channel state information (CSI) reported on another serving cell, the UE may deactivate any active uplink BWP associated with the serving cell and, if the BWP inactivity timer is running, stop any BWP inactivity timer associated with the active uplink BWP. In this case, the base station may control the UE behavior regarding whether to deactivate any active uplink BWP via an indicator included in a MAC CE, an RRC message, or a PDCCH DCI.

[0038] In the third case, the serving cell state can be modified / transferred from the deactivated state to the dormant state. In this case, the terminal can activate the DL BWP or UL BWP according to the first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and the first active uplink BWP (indicated by firstActiveUplinkBWP-Id) configured for the serving cell. The UE can start the BWP inactivity timer when the DL BWP or UL BWP is activated.

[0039] In some embodiments, the terminal may activate the DL BWP or UL BWP according to the first active downlink BWP for the dormant state and the first active uplink BWP for the dormant state, respectively, which may be configured by the base station via an RRC message or system information for the serving cell. The first active BWP configuration for modifying the serving cell to the dormant state may be different from the configuration for modifying the serving cell state to the activated state. The UE may start the BWP inactivity timer when activating the DL BWP or the UL BWP.

[0040] In some embodiments, if a default BWP for a serving cell is configured, the terminal may activate a DL BWP or a UL BWP according to the configured default BWP, or if a default BWP for the serving cell is not configured, the terminal may activate a DL BWP or a UL BWP according to the initial BWP configured for the serving cell. More specifically, if a default downlink BWP is configured, the terminal may activate the UL BWP according to the configured default downlink BWP. If a default downlink BWP is not configured, the terminal may activate the downlink BWP according to the initial downlink BWP. The terminal may activate the uplink BWP according to the initial uplink BWP.

[0041] In some embodiments, if uplink resources for CQI / CSI reporting of a serving cell are configured on another serving cell, the terminal may not activate uplink BWP for the serving cell.

[0042] In the fourth case, the serving cell state may be modified from dormant to deactivated upon receipt of a MAC CE or upon expiration of a timer. In this case, if the timer is running, the UE may deactivate any active BWP associated with the serving cell and stop the BWP inactivity timer.

[0043] In the fifth case, the serving cell state may be modified from the dormant state to the activated state. In this case, if the previous active UL BWP in dormancy or the active DL BWP in dormancy is not the configured first active downlink BWP or the first active uplink BWP, respectively, the UE may perform BWP switching to the first active downlink BWP and the first active uplink BWP according to the first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and the first active uplink BWP (indicated by firstActiveUplinkBWP-Id) respectively configured for the serving cell. The UE may start or restart the BWP inactivity timer.

[0044] In some embodiments, if there is no active BWP before the serving cell state transition, the UE may activate the DL BWP or UL BWP according to the first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and the first active uplink BWP (indicated by firstActiveUplinkBWP-Id), respectively. The UE may start a BWP inactivity timer.

[0045] In some embodiments, when the serving cell is in a dormant state and before the cell state is modified, the UE may keep or maintain an active BWP for the serving cell and start a BWP inactivity timer associated with the active BWP if the BWP inactivity timer is not running, or restart the BWP inactivity timer if the BWP inactivity timer is running, or in some embodiments, keep the BWP inactivity timer associated with the active BWP running.

[0046] In some embodiments, the UE may perform a BWP switch to a first active downlink BWP or a first active uplink BWP, which is defined as being activated when the serving cell state transitions from a dormant state to an activated state and is configured by the base station via an RRC message or system information. If the serving cell state transitions / modifies from a dormant state to an activated state, the first active BWP may be different from the BWP when the serving cell transitions from a deactivated state to an activated state. The UE may start / restart the BWP inactivity timer.

[0047] If the UE starts or restarts the BWP inactivity timer when the UE is in the dormant state, or when the serving cell state changes to the dormant state, the UE may use the BWP inactivity timer length dedicated to the dormant state, that is, the base station may configure the BWP inactivity timer length for the serving cell in the active state and the dormant state respectively by including a separate information IE in the RRC message or system information.

[0048] If the serving cell is in a dormant state, or if the serving cell is modified from an activated state or a deactivated state to a dormant state, the UE may perform steps on the active BWP. One such step may include reporting CQI or CSI for the active BWP via the configured uplink resources for CQI or CSI reporting. If PUCCH is configured on the active BWP, another such step may include transmitting PUCCH on the active BWP. Another such step may include suspending any configured uplink grants of grant type 1 or type 2 on the active BWP. The UE may stop monitoring the PDCCH on the active BWP. If a PRACH opportunity is configured on the active BWP, the UE may transmit a random access channel (RACH) on the BWP.

[0049] This embodiment may provide a solution for how to perform a BWP operation when the serving cell state is modified to or from a dormant state.

[0050] This embodiment can reduce the scheduling delay caused by the BWP switching performed on the serving cell state transition. When the serving cell state changes from the dormant state to the activated state, some methods in this embodiment can be applied without changing / switching the BWP. For example, when the serving cell state is modified from the activated state to the dormant state, and from the deactivated state to the dormant state, and when the serving cell state is configured to be dormant via an RRC message, the UE activates or switches the active CL WP or UL BWP according to the BWP configuration activated or switched when the serving cell is activated from the dormant state. The BWP configuration can be the first active downlink BWP and the first uplink BWP, or the first active BWP in the dormant state and the first active uplink BWP in the dormant state, or the initial downlink and uplink BWP. In this way, the active BWP is the same before and after the serving cell state is modified from the dormant state to the activated state. Therefore, after the serving cell state transition, the CSI / CQI measurement on the downlink active BWP can be valid. The BS can schedule on the active BWP according to the CSI / CQI reported before the cell state transition, ie, there is no need to wait for new CSI / CQI measurement and reporting, since the active BWP changes before and after the serving cell state transition.

[0051] Example embodiment 2:

[0052] Exemplary embodiment 2 relates to how to handle configured uplink grants and configured downlink allocations when adding a serving cell in a dormant state (including serving cell state transitions between dormant states).

[0053] Configuration Grant Type 1 and Configuration Grant Type 2 may be a set of periodic uplink resources. The UE may utilize these uplink resources without dynamic scheduling signaling to save data transmission delay.

[0054] In the first case, when the serving cell is added to the cell group, the serving cell may be configured in a dormant state. The UE may store a configuration grant type 1 configuration associated with the BWP of the serving cell or associated with the serving cell provided by an RRC message from the base station. The UE may suspend any configuration grant type 1 associated with the BWP of the serving cell or associated with the serving cell.

[0055] In the second case, the serving cell state may be modified from an activated state to a dormant state. In this case, the UE may clear any configured downlink allocation associated with any BWP of the serving cell. The UE may suspend configured downlink allocation associated with any BWP of the serving cell. Configured downlink allocations may not be cleared / released when the serving cell is modified from an activated state to a dormant state.

[0056] The UE may clear any configured uplink grant type 2 associated with any BWP of the serving cell. The UE may suspend any configured uplink grant type 2 associated with any BWP of the serving cell. Suspending any configured uplink grant type 2 may mean that when the serving cell is modified from an activated state to a dormant state, a configured uplink grant type 2 associated with a BWP or associated with the serving cell is not released.

[0057] The UE may suspend any configured uplink grant Type 1 associated with the previously active BWP or any BWP of the serving cell.

[0058] In the third case, the serving cell may be modified from dormant state to active state. In this case, the UE may initiate (or re-initiate) any suspended configured uplink grants of configured grant type 1 associated with the active BWP of the serving cell. The UE may initiate (or re-initiate) any suspended configured uplink grants of configured grant type 2 associated with the active BWP of the serving cell. The UE may initiate (or re-initiate) any suspended configured downlink allocations associated with the active BWP of the serving cell.

[0059] In a fourth case, the serving cell may be modified from a dormant state to a deactivated state. In this case, the UE may clear any stored configured uplink grant type 2 configuration associated with any BWP of the serving cell. The UE may clear any stored configured downlink allocation associated with any BWP of the serving cell. The UE may also keep suspended any configured uplink grant type 1 associated with any BWP of the serving cell.

[0060] If there are any configured downlink allocations, configured uplink grant type 1, or configured uplink type 2 associated with the BWP, or associated with a serving cell to be initiated due to the associated serving cell state transitioning from a dormant state to an activated state or due to the serving cell being added as an active or dormant state, the UE may perform one of various steps. Such steps may include the UE starting to receive downlink transmissions on the configured downlink allocations no earlier than when the UE is ready to perform PUCCH transmissions for the serving cell. Such steps may include the UE starting to perform uplink transmissions on the configured uplink grants no earlier than when the UE is ready to perform PDCCH monitoring on the serving cell.

[0061] In some embodiments, when the UE is in dormant state, it may suspend the configured grant type 1 or the configured grant type 2 or the configured allocation instead of clearing them. When the BS activates the serving cell, the UE may activate / re-initiate the suspended configured grant type 1 or the configured grant type 2 or the configured allocation, i.e., the delay required for an additional MAC to re-initiate the configured grant or the configured allocation may be saved.

[0062] When the serving cell is in dormant state, the configured downlink allocation and the configured uplink grant may be suspended but not cleared. Therefore, when the serving cell is activated from dormant state, the UE may resume (re-initiate) the suspended configured downlink allocation and the configured uplink grant without delay caused by reconfiguration of the configured allocation or the configured uplink grant.

[0063] Example embodiment 3:

[0064] Example embodiment 3 relates to UE behavior when beam failure is detected on a reference signal (eg, SSB or CSI-RS) on a serving cell in a dormant state. Figure 3 A block diagram of a method for recovering a failed beam of a serving cell is shown.

[0065] The terminal may detect a beam failure of a serving cell (block 302). For a serving cell in a dormant state, the UE may perform beam failure detection of the serving cell by counting beam failure instance indications from the lower layer to the MAC entity. If the number of beam failure instances from the lower layer reaches a predetermined maximum number within a preconfigured timer duration, the UE may detect a beam failure.

[0066] In some embodiments, if the dormant serving cell detects a beam failure, the UE may perform at least one of various steps. Such steps may include the UE indicating to the base station that a beam failure is detected on the serving cell (block 304). The UE may indicate the beam failure by transmitting an RRC message or a MAC CE to the base station. The RRC message may be transmitted from the UE to the base station via the cell group to which the serving cell belongs, or via a different cell group to which the serving cell belongs. The MAC CE may be transmitted from the UE to the base station via another serving cell of the cell group to which the serving cell belongs, or via another serving cell of a different cell group to which the serving cell belongs.

[0067] Such steps may include the UE changing the serving cell state to the deactivated state autonomously or after receiving an MCE CE or RRC message indicating a request to modify the serving cell to the deactivated state. The UE may keep the serving cell in the dormant state before receiving an RRC message or MAC CE that configures the serving cell with another state.

[0068] Such steps may include the UE autonomously triggering a beam failure recovery procedure on the serving cell. The base station may transmit an indication to the terminal to initiate a beam failure recovery procedure (box 306). The terminal may initiate a beam failure recovery procedure (box 308). The base station may configure whether the UE can trigger a beam failure recovery procedure for this dormant serving cell. By default, if the serving cell is the primary cell (SpCell) of the cell group, the UE may trigger a beam failure recovery procedure when a beam failure is detected on the serving cell. If beam failure recovery is allowed for a dormant serving cell, the UE may initiate beam failure recovery, and the UE initiates a beam failure recovery procedure on the serving cell immediately after the serving cell is activated. In some embodiments, when a beam failure is detected on the serving cell, the UE immediately initiates a beam failure recovery procedure.

[0069] When the UE receives a PDCCH command via another serving cell of the same cell group or via another serving cell of a different cell group, the UE may trigger a beam failure recovery procedure on the serving cell. In this case, when the BS receives an RRC message or MAC CE transmitted from the UE to the BS to indicate that a beam failure is detected on this serving cell, the base station (BS) may instruct the UE to trigger beam failure recovery for the serving cell.

[0070] If beam failure recovery is allowed for a dormant serving cell, the UE may initiate a beam failure recovery procedure on the serving cell immediately after the serving cell is activated. When a beam failure is detected on the serving cell, the UE may immediately initiate a beam failure recovery procedure.

[0071] If a default BWP is configured for the serving cell, the UE may perform a BWP switch to switch the active BWP to the default BWP, or to the initial downlink BWP or initial uplink BWP if no default BWP is configured for the serving cell or keep the current active BWP and the associated BWP inactivity timer if it is running. The UE may stop CQI / CSI reporting for the serving cell.

[0072] In one embodiment, the beam failure recovery process may be implemented through a random access procedure for beam failure recovery (RA for beam failure recovery).

[0073] If the UE indicates to the BS through an RRC message or a MAC CE that a beam failure has been detected on a serving cell, the RRC message or the MAC CE may include a cell group ID of a cell group to which the serving cell belongs, an indicator indicating whether the serving cell belongs to a secondary cell group, an indicator indicating whether the serving cell belongs to a primary cell group, an indicator indicating whether the serving cell belongs to a cell group different from the cell transmitting the MAC CE, a serving cell ID or a serving cell index for identifying a serving cell in a cell group, or all cell groups configured for the UE.

[0074] The message may also include a measurement result of the serving cell, which may include a cell-level measurement result or a beam-level measurement result. The beam-level measurement result may include a list of reference signal IDs (including SSB indexes and CSI-RS indexes), and the measured quality of the reference signal.

[0075] When a beam failure is detected on a serving cell in a dormant state, the BS may be notified of the beam failure. Therefore, when the BS intends to activate for data scheduling, it may be possible to avoid activating the serving cell with a beam failure. Otherwise, if the BS activates the serving cell with a beam failure, more delays may be incurred to perform beam failure recovery, such as by triggering a RACH procedure. On the other hand, when a beam failure occurs, this embodiment may provide a method for triggering a beam failure recovery procedure to recover the beam of the serving cell.

[0076] Example embodiment 4:

[0077] Example embodiment 4 relates to the transmission configuration indicator (TCI) state configuration when adding a serving cell in an activated or dormant state. Figure 4 A block diagram for configuring and activating TCI state configuration is shown.

[0078] In many cases, TCI status information is used to indicate the beam used for UE monitoring PDCCH or PDSCH by associating one or two downlink reference signals (SSB or CSI-RS in NR) with the corresponding quasi co-location (QCL) type.

[0079] A set of TCI state information may include a TCI state ID, a cell ID of a serving cell in which a reference signal is configured, a BWP ID of a downlink BWP in which a downlink reference signal is located, a QCL type, and a reference signal ID (SSB index, or CSI-RS resource ID). When a serving cell ID is not configured in the TCI state information, the reference signal may be located in a serving cell in which the TCI state information is configured.

[0080] In many cases, the configured TCI state for PDCCH and PDSCH reception can be deactivated when configured via RRC configuration. Moreover, in many cases, in order to configure TCI state information for PDCCH monitoring, the BS can first configure a candidate TCI state information list configured for the CORSET configured by the downlink BWP of the serving cell via an RRC message. Secondly, the BS can indicate to the UE which TCI state information is used for PDCCH monitoring on a specific CORSET configured by the downlink BWP for the serving cell through a MAC CE transmitted from the BS to the UE, and the MAC CE includes a serving cell ID used to indicate which serving cell the MAC CE applies to, a control resource set ID (CORESET ID) of the CORESET used to indicate the TCI state indication, and a TCI state ID of one of the candidate PDCCH TCI states configured via an RRC message. The UE can apply the indicated TCI state information upon receiving the MAC CE.

[0081] In some cases, in order to configure the TCI state used for PDSCH reception, the BS may first configure a list of candidate TCI state information for PDSCH reception on the BWP via an RRC message. The BS may indicate to the UE via a MAC CE, which includes a BWP ID and a bitmap indicating which candidate TCI state information configured for PDSCH reception is activated. The BS may indicate via PDCCH signaling which activated TCI state information is used for PDSCH reception on the BWP. The UE may apply the corresponding TCI state information for PDSCH reception on the BWP.

[0082] Exemplary embodiment 4 may involve indicating TCI state information used for PDCCH monitoring or PDSCH reception when the BS configures the serving cell to an activated state or a dormant state via an RRC message or MAC CE. This can reduce the delay caused by additional MAC CE and PDCCH signaling.

[0083] A candidate list of TCI state information may be configured (block 402). When the BS configures a serving cell to an activated state or a dormant state via an RRC message, for example, to add a serving cell to a cell group or configure a serving cell, the BS may include the serving cell configuration in the RRC message. The RRC message may include at least one of the following: a serving cell ID, a cell group ID to which the serving cell belongs, and a downlink BWP configuration. For a specific BWP configuration, the RRC message may include a list of candidate TCI state information for PDSCH reception. The RRC message may include a list CORESET for a specific downlink BWP, and for each control resource set (CORESET), a list of candidate TCI state information for PDCCH reception on the CORESET.

[0084] The RRC message may include serving cell status information, which is used to indicate the status of the serving cell when the RRC message is applied. The serving cell status indicated in the RRC message may be activated, dormant or deactivated.

[0085] The RRC message may indicate which TCI state is used for PDCCH reception on the CORESET of a specific BWP of the serving cell via the RRC message. For the CORESET configured for the downlink BWP of the serving cell, the RRC message may indicate the TCI state ID or the index of the candidate TCI state information list configured for the CORESET to indicate the TCI state used for PDCCH reception on the CORESET. The RRC message may include an indicator for each candidate TCI state information configured for the CORESET to indicate whether the corresponding TCI state information is used for PDCCH reception on the CORESET.

[0086] The TCI state information list from the candidate list may be activated (block 404). Upon receiving the RRC message, the UE may apply the indicated TCI state information for PDCC monitoring on the corresponding CORSET.

[0087] The activated TCI state may be indicated to the terminal (block 406). In order to configure TCI state information for PDSCH reception on the downlink BWP of the serving cell, the BS may indicate activated TCI state information for PDSCH reception on the BWP via an RRC message. The BS may then indicate which activated TCI state information is used for PDSCH reception via PDCCH signaling. The UE may then apply the TCI state information indicated by the PDCCH signaling to PDSCH reception on the BWP.

[0088] In one embodiment, in addition to the candidate TCI state information for PDSCH reception or the activated TCI state information for PDSCH reception, the BS may indicate in the RRC message which TCI state information is used for PDSCH reception on the downlink BWP. In this case, the UE may apply the indicated TCI state to PDSCH reception on the BWP upon receiving the RRC message.

[0089] In order to indicate the activated TCI state information for PDSCH reception or the TCI information or TCI information for PDSCH reception, the RRC message may include an indicator for each candidate TCI state information for PDSCH reception on the BWP. The indicator may be defined to indicate whether the corresponding TCI state information is activated, or may be defined to indicate whether the corresponding TCI state information is (actually) used for PDSCH reception on the BWP.

[0090] For the downlink BWP of the serving cell, the RRC message may include one or more activated TCI state information or TCI state information used for PDSCH reception. The TCI state information may be a TCI state ID, a set of TCI state information, or an index to a candidate TCI state information list configured for the CORESET.

[0091] The BS can determine candidate TCI state information for PDCCH or PDSCH, activated TCI state information for PDSCH, and TCI state information to be used for PDCCH and PDSCH reception by the UE based on the radio network deployment, the serving cell configuration and the measurement report sent from the UE before the serving cell is configured to the UE.

[0092] After the UE applies the configuration carried in the RRC message, the BS can configure the TCI state information used for PDCCH or PDSCH monitoring without additional indication via MAC CE. Therefore, the delay caused by the additional MAC CE can be saved.

[0093] When the BS configures the serving cell to an activated state or a dormant state via an RRC message, the BS can configure TCI state information for PDCCH reception or PDSCH reception in the same RRC message. Therefore, upon receiving the RRC message, the UE can apply the TCI state information to PDCCH reception or PDSCH reception without an additional MAC CE to indicate the TCI state information.

[0094] Example embodiment 5:

[0095] Example embodiment 5 relates to how to maintain uplink time alignment across a group of cells.

[0096] In many cases, uplink time alignment for a serving cell is implemented by a timing advance (TA) command MAC CE transmitted from the BS to the UE via the cell group to which the serving cell belongs. The TA command MAC CE includes a timing advance group (TAG) ID and TA command information used to control the timing advance amount of the TAG identified by the TAG ID. The serving cell may be configured with a TAG ID to indicate the TAG to which the serving cell belongs. The TAG ID may identify a TAG within the cell group range.

[0097] To support uplink time alignment across cell groups, the BS may transmit a TA command MAC CE via a service of cell group A for a TAG defined for cell group B. The TA command MAC CE includes at least one of: cell group ID information, TAG ID, and TA command information. The cell group ID information may be implicitly indicated by defining a dedicated MAC CE type (logical channel ID, LCID) indicated in a MAC CE sub-header and dedicated to this purpose. The UE may apply the TA command included in the MAC CE to the TAG indicated by the TAG ID of cell group B.

[0098] In one embodiment, in order to support uplink time alignment across cell groups, the BS may configure the TAG ID defined for cell group A for the serving cell of cell group B via an RRC message or a MAC CE. Specifically, the BS may configure the cell group ID of cell group A and the TAG ID defined for cell group A for serving cell B. The BS may configure the TAG ID defined for cell group A to the UE by defining an information element (IE) (for example, this IE is defined as the TAG ID of another cell group). After receiving the TA command MAC CE including the TAG ID defined for cell group A, the UE may apply the TA command to serving cell B.

[0099] The BS may define a TAG with a unique TAG ID in a cell group via an RRC message. The BS configures the TAG ID for a serving cell of any cell group to indicate that the serving cell belongs to the TAG indicated by the TAG ID. The TA command MAC CE may include this TAG ID transmitted via any cell group. After receiving the TA command MAC CE including the TAG ID, the UE may apply the TA command to all serving cells belonging to the TAG.

[0100] The BS may associate TAG A defined for cell group A with TAG B defined for cell group B through TAG ID A in the configuration of TAG B. The UE may identify the TA command included in the TA command MAC CE (including TAG ID A) when receiving the MAC CE and apply the TA command included in the TA command MAC CE (including TAG ID A) to TAG B. The TA command MAC CE including TAG ID A may be transmitted via cell group A. (Equivalent)

[0101] By providing information supporting uplink time alignment across a cell group, the serving cells of the cell group may be modified / converted to a dormant state, i.e., CSI / CQI reporting is performed only on the cell group, and the UE does not monitor the PDCCH on any serving cell of the cell group.

[0102] TA management can be implemented across cell groups. In some cases, the TAG may include only serving cells of the same cell group. In addition, the TA command MAC CE may not be used for time advance adjustment across cell groups. By applying the method of this embodiment, the serving cell may be configured to include the TAG of the serving cells of any cell group, or may be configured to be a TAG defined for a cell group different from the cell group to which the serving cell belongs, or may be associated with two TAGs defined for different cell groups, or may be a TA command MAC CE transmitted across cell groups, and thus the BS may adjust the time alignment of the serving cell by transmitting the TA command MAC CE via a cell group different from the cell group to which the serving cell belongs.

[0103] Example embodiment 6:

[0104] Example embodiment 6 relates to how to implement a dormant state for a cell group, wherein all serving cells in the cell group are in a deactivated or dormant state, i.e., no serving cell is in an activated state. When the cell group is modified to a dormant state, at least one serving cell may be in a dormant state. In one embodiment, at least one serving cell is configured with PUCCH resources for CSI or CQI reporting.

[0105] BWP operation for the serving cell of the cell group may be implemented by one of the methods provided in exemplary embodiment 1. Beam failure handling for the serving cell of the cell group may be implemented by one of the methods provided in exemplary embodiment 3. TCI state maintenance may be implemented by one of the methods provided in exemplary embodiment 4. Uplink time alignment is maintained by one of the methods provided in exemplary embodiment 5.

[0106] The BS may indicate the state of the serving cell of the cell group via another cell group through the cell group information included in the MAC CE for serving cell state transition.

[0107] The MAC CE may include one of the following: cell group ID information, target state information, cell ID information. The cell group ID information may be implicitly indicated by defining a dedicated MAC CE type, i.e., a logical channel ID, an LCID indicated in the MAC subheader and dedicated to this purpose. The target state information may be indicated by different MAC CE types (i.e., LCID indicated in the MAC subheader), for example, a MAC CE for activation, a MAC CE for deactivation, and a MAC converted to a dormant state (sleep) are defined with different LCIDs, respectively. The cell ID information may be represented by a bitmap included in the MAC CE, and each bit of the bitmap represents a serving cell configured to the cell group.

[0108] The BS can modify / convert all serving cells of the cell group to an activated state, a dormant state, or a deactivated state. Since there is no PDCCH monitoring for all serving cells of the cell group, UE power can be saved, and at least one serving cell in a dormant state can be quickly activated.

[0109] Figure 5 A block diagram of a method for managing a serving cell is shown. A terminal may detect the occurrence of an event (block 502). The terminal may modify the state configuration of the serving cell based on the event (block 504).

[0110] In some embodiments, the event comprises expiration of a deactivation timer, and wherein the state configuration is modified to a deactivated state.

[0111] In some embodiments, the event comprises expiration of a sleep timer, and wherein the state configuration is modified to a sleep state.

[0112] In some embodiments, the event comprises receiving a message from a communications node, wherein the message comprises a status configuration of a serving cell.

[0113] In some embodiments, the event includes identifying a beam failure of the serving cell.

[0114] In some embodiments, the method includes modifying a state configuration of the serving cell from an active state to a dormant state.

[0115] In some embodiments, the method includes stopping, by the terminal, the BWP inactivity timer when modifying the state configuration of the serving cell from the active state to the dormant state.

[0116] In some embodiments, the method includes modifying, by the terminal, at least one of an active downlink BWP of the serving cell and an active uplink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and according to a first active uplink BWP configured for the serving cell, respectively.

[0117] In some embodiments, the method includes modifying, by the terminal, the state configuration of the serving cell from a deactivated state to a dormant state.

[0118] In some embodiments, the method includes activating, by the terminal, at least one of a downlink BWP and an uplink BWP according to a first active downlink BWP configured for a serving cell and according to a first active uplink BWP configured for the serving cell, respectively.

[0119] In some embodiments, the method includes activating, by the terminal, a downlink BWP according to a first active downlink BWP configured for a dormant state of a serving cell, or activating an uplink BWP according to a first active uplink BWP configured for a dormant state of a serving cell.

[0120] In some embodiments, the method includes activating, by the terminal, the downlink BWP or the uplink BWP according to a default BWP of a serving cell including the default BWP.

[0121] In some embodiments, the method includes modifying, by the terminal, a state configuration of the serving cell from a dormant state to a deactivated state.

[0122] In some embodiments, the method includes deactivating, by the terminal, an active uplink BWP and an active downlink BWP associated with the serving cell; and stopping, by the terminal, a BWP inactivity timer.

[0123] In some embodiments, the method includes modifying, by the terminal, a state configuration of the serving cell from a dormant state to an active state.

[0124] In some embodiments, the method includes modifying, by the terminal, at least one of an active downlink BWP of the serving cell and an active uplink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and according to a first active uplink BWP configured for the serving cell, respectively.

[0125] In some embodiments, the method includes, when the serving cell has no active BWP, activating, by the terminal, at least one of a downlink BWP of the serving cell and an uplink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and according to a first active uplink BWP configured for the serving cell, respectively.

[0126] In some embodiments, the method includes starting, by the terminal, an inactivity timer associated with the active uplink BWP or the active downlink BWP.

[0127] In some embodiments, the method includes reporting, by the terminal to the communications node via the configured uplink resources, at least one of a channel quality indicator (CQI) and channel state information (CSI) for the downlink BWP.

[0128] In some embodiments, the method includes suspending, by the terminal, at least one of a configured downlink allocation, a configured uplink grant type 2, and a configured uplink grant type 1 associated with at least one of an uplink BWP or a downlink BWP of a serving cell.

[0129] In some embodiments, the method includes initiating, by the terminal, at least one of a suspended configured uplink grant type 1, a suspended configured uplink grant type 2, and a suspended downlink allocation associated with at least one of an active uplink BWP and an active downlink BWP of a serving cell.

[0130] In some embodiments, the method includes identifying, by the terminal, a beam failure on a reference signal of a serving cell.

[0131] In some embodiments, the method includes transmitting, by the terminal to the communication node, a beam failure indication indicating a beam failure of the serving cell.

[0132] In some embodiments, the beam failure indication is transmitted via one of a second serving cell having a cell group including the serving cell and a third serving cell having a cell group not including the serving cell.

[0133] In some embodiments, the method includes modifying, by the terminal, the state configuration of the serving cell from a dormant state to a deactivated state when a beam failure is identified or based on receiving a request from a communication node to modify the state configuration of the serving cell to a deactivated state.

[0134] In some embodiments, the method includes initiating, by the terminal, a beam failure recovery procedure on a serving cell based on determining that the terminal is allowed to initiate the beam failure recovery procedure.

[0135] In some embodiments, a beam failure recovery procedure is initiated based on receiving a PDCCH command at the terminal, wherein the PDCCH command is transmitted via one of a second serving cell having a cell group including the serving cell and a third serving cell having a cell group not including the serving cell.

[0136] In some embodiments, the method includes modifying, by the terminal, one of an active uplink BWP or an active downlink BWP of the serving cell to one of a default BWP (if a default BWP is configured for the serving cell) and an initial BWP (if no default BWP is configured for the serving cell).

[0137] In some embodiments, the method includes stopping, by the terminal, CQI and CSI reporting for the serving cell.

[0138] In some embodiments, the beam failure indication is transmitted via one of an RRC message and a MAC CE, and wherein the beam failure indication includes at least one of a cell group identifier identifying a cell group associated with a serving cell, a serving cell identifier identifying a serving cell in the cell group, and a measurement result of the serving cell.

[0139] In some embodiments, a status configuration message indicating a configuration of a serving cell from a communication node includes at least one of: a serving cell identifier, a cell group identifier identifying a cell group of the serving cell, a downlink BWP configuration, candidate transmission configuration indicator (TCI) status information for physical downlink shared channel (PDSCH) reception, and control resource set (CORESET) information configured for the downlink BWP, wherein the CORESET information includes candidate TCI information for PDCCH reception.

[0140] In some embodiments, the message from the communications node indicating a state configuration of a serving cell indicates a TCI state for PDCCH reception on a CORESET of a BWP of the serving cell.

[0141] In some embodiments, the message indicates a TCI state identifier or an index of candidate TCI state information associated with the CORESET to indicate a TCI state for PDCCH reception on the CORESET, and wherein the terminal utilizes the TCI state information for PDCCH reception.

[0142] In some embodiments, the message includes an indicator for each candidate TCI state information configured for the CORESET to indicate whether the TCI state information is used for PDCCH reception on the CORESET, and wherein the terminal utilizes the TCI state information for PDCCH reception.

[0143] In some embodiments, the message includes an indicator for each candidate TCI state information for physical downlink shared channel (PDSCH) reception on the downlink BWP, wherein the indicator indicates whether the candidate TCI state information is activated or used for PDSCH reception.

[0144] In some embodiments, the message includes an activated TCI state or TCI state information for PDSCH reception, wherein the TCI state information includes at least one of a TCI state identifier and an index of candidate TCI state information configured for the BWP.

[0145] Figure 6 An example of a wireless communication system is shown in which processes according to one or more embodiments of the present technology can be applied. The wireless communication system 600 may include one or more base stations (BSs) 605a, 605b, one or more wireless devices 610a, 610b, 610c, 610d, and a core network 625. The base stations 605a, 605b may provide wireless services to the wireless devices 610a, 610b, 610c, and 610d in one or more wireless sectors. In some embodiments, the base stations 605a, 605b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

[0146] The core network 625 can communicate with one or more base stations 605a, 605b. The core network 625 provides connectivity with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to the subscribed wireless devices 610a, 610b, 610c and 610d. The first base station 605a can provide wireless services based on a first radio access technology, and the second base station 605b can provide wireless services based on a second radio access technology. Depending on the deployment scenario, the base stations 605a and 605b can be located at the same location or can be installed separately on site. The wireless devices 610a, 610b, 610c and 610d can support a variety of different radio access technologies.

[0147] In some implementations, a wireless communication system may include multiple networks using different wireless technologies. Dual-mode or multi-mode wireless devices introduce two or more wireless technologies that can be used to connect to different wireless networks.

[0148] Figure 7705 is a block diagram representation of a portion of a hardware platform. A hardware platform 705, such as a network device or base station or wireless device (or UE), may include a processor electronic device 710 (such as a microprocessor) that implements one or more of the techniques described in this document. The hardware platform 705 may include a transceiver electronic device 715 for sending and / or receiving wired or wireless signals through one or more communication interfaces (such as antenna 720) or a wired interface. The hardware platform 705 may implement other communication interfaces with defined protocols for transmitting and receiving data. The hardware platform 705 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, the processor electronic device 710 may include at least a portion of the transceiver electronic device 715. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the hardware platform 705.

[0149] From the foregoing, it will be appreciated that the specific embodiments of the presently disclosed technology are described for illustrative purposes, but various modifications may be made without departing from the scope of the invention. Therefore, the presently disclosed technology is not limited except by the limitations of the appended claims.

[0150] The disclosed and other embodiments, modules and functional operations described in this document may be implemented in digital electronic circuits or computer software, firmware or hardware (including the structures disclosed in this document and their equivalents) or a combination of one or more thereof. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by a data processing device or for controlling the operation of the data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a material composition that affects a machine-readable propagation signal, or a combination of one or more thereof. The term "data processing device" encompasses all devices, equipment and machines for processing data, including, for example, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, such as code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more thereof. A propagated signal is an artificially generated signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0151] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language (including compiled or interpreted languages) and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on one computer or on multiple computers located at one site or distributed over multiple sites and interconnected by a communications network.

[0152] The processes and logic flows described in this document may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may also be implemented as, special purpose logic circuits such as FPGAs (field programmable gate arrays) or ASICs (application specific integrated circuits).

[0153] Processors suitable for executing computer programs include, for example, both general-purpose and special-purpose microprocessors and any one or more processors of any kind of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or be operatively coupled to receive data from or transfer data to or both of mass storage devices. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit.

[0154] Although this patent document contains many details, these details should not be interpreted as limitations on the scope of any invention or the content that can be claimed, but rather as descriptions of features that can be specific to a particular embodiment of a specific invention. Certain features described in this patent document in the context of separate embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any suitable sub-combination, respectively. Moreover, although the features may be described above as working in certain combinations and even initially claimed as such, one or more features in the claimed combination may be cut out of the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0155] Similarly, although operations are depicted in a particular order in the drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in a continuous order, or that all of the illustrated operations be performed to achieve the desired results. In addition, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0156] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and illustrated in this patent document.

Claims

1. A wireless communication method, comprising: Receiving a message from a communication node by a terminal; and The terminal responds to the message and configures the state configuration of the serving cell according to the message, The message includes an indication of the state of the serving cell and an identifier of a transmission configuration indicator TCI state, wherein the TCI state is used to perform physical downlink control channel PDCCH reception on a control resource set CORESET configured for a downlink bandwidth part BWP of the serving cell, wherein the terminal uses the TCI state to perform PDCCH reception, and the state of the serving cell includes one of an activation state and a deactivation state.

2. The method according to claim 1, wherein: The message includes an indicator of a second TCI state for physical downlink shared channel (PDSCH) reception, wherein the indicator indicates whether the second TCI state for PDSCH reception is activated or used for PDSCH reception.

3. A wireless communication method, comprising: A message is transmitted by a communication node to a terminal, the message being used to configure a state configuration of a serving cell, the message comprising an indication of a state of the serving cell and an identifier of a transmission configuration indicator TCI state, the TCI state being used to perform physical downlink control channel PDCCH reception on a control resource set CORESET configured for a downlink bandwidth part BWP of the serving cell, The message is used to trigger the terminal to configure the state configuration of the service cell according to the message, and the TCI state is used for the PDCCH reception, and the state of the service cell includes one of an activation state and a deactivation state.

4. The method according to claim 3, wherein: The message includes an indicator of a second TCI state for physical downlink shared channel (PDSCH) reception.

5. The method according to claim 4, wherein: The indicator indicates whether the second TCI state for PDSCH reception is activated or used for PDSCH reception.

6. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read a code from the memory to implement the following operations: receiving a message from a communication node; and In response to the message, configuring a state configuration of the serving cell according to the message, in, The message includes an indication of the state of the serving cell and an identifier of a transmission configuration indicator TCI state, wherein the TCI state is used to perform physical downlink control channel PDCCH reception on a control resource set CORESET configured for a downlink bandwidth part BWP of the serving cell, wherein the terminal utilizes the TCI state to perform PDCCH reception, and the state of the serving cell includes one of an activation state and a deactivation state.

7. The device according to claim 6, wherein: The message includes an indicator of a second TCI state for physical downlink shared channel (PDSCH) reception, wherein the indicator indicates whether the second TCI state for PDSCH reception is activated or used for PDSCH reception.

8. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read a code from the memory to implement the following operations: transmitting a message to a terminal, the message being used to configure a state configuration of a serving cell, the message comprising an indication of a state of the serving cell and an identifier of a transmission configuration indicator TCI state, the TCI state being used to perform physical downlink control channel PDCCH reception on a control resource set CORESET configured for a downlink bandwidth part BWP of the serving cell, in, The message is used to trigger the terminal to configure the state configuration of the service cell according to the message, and wherein the TCI state is used for the PDCCH reception, and the state of the service cell includes one of an activation state and a deactivation state.

9. The device according to claim 8, wherein: The message includes an indicator of a second TCI state for physical downlink shared channel (PDSCH) reception.

10. The device according to claim 9, wherein: The indicator indicates whether the second TCI state for PDSCH reception is activated or used for PDSCH reception.

11. A non-transitory computer readable medium having stored thereon codes which, when executed by a processor, cause the processor to implement the method according to any one of claims 1 to 5.

Images