Traitement en cours

Veuillez attendre...

Paramétrages

Paramétrages

Aller à Demande

1. WO2020155160 - GESTION D’ÉTATS DE CELLULE DE DESSERTE

Document

Description

Title of Invention 0001   0002   0003   0004   0005   0006   0007   0008   0009   0010   0011   0012   0013   0014   0015   0016   0017   0018   0019   0020   0021   0022   0023   0024   0025   0026   0027   0028   0029   0030   0031   0032   0033   0034   0035   0036   0037   0038   0039   0040   0041   0042   0043   0044   0045   0046   0047   0048   0049   0050   0051   0052   0053   0054   0055   0056   0057   0058   0059   0060   0061   0062   0063   0064   0065   0066   0067   0068   0069   0070   0071   0072   0073   0074   0075   0076   0077   0078   0079   0080   0081   0082   0083   0084   0085   0086   0087   0088   0089   0090   0091   0092   0093   0094   0095   0096   0097   0098   0099   0100   0101   0102   0103   0104   0105   0106   0107   0108   0109   0110   0111   0112   0113   0114   0115   0116   0117   0118   0119   0120   0121   0122   0123   0124   0125   0126   0127   0128   0129   0130   0131   0132   0133   0134   0135   0136   0137   0138   0139   0140   0141   0142   0143   0144   0145   0146   0147   0148   0149   0150   0151   0152   0153   0154   0155   0156   0157  

Claims

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37  

Drawings

1   2   3   4   5   6   7  

Description

Title of Invention : SERVING CELL STATE MANAGEMENT

TECHNICAL FIELD

[0001]
This patent document is directed generally to wireless communications.

BACKGROUND

[0002]
Mobile communication technologies are moving the world toward an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have led to greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios. Various techniques, including new ways to provide higher quality of service, are being discussed.
[0003]
SUMMARY
[0004]
This document discloses methods, systems, and devices related to digital wireless communication, and more specifically, to techniques related to maintaining a state of a serving cell.
[0005]
In one exemplary aspect, a method for wireless communication is disclosed. The method includes detecting an occurrence of an event. The method also includes modifying the state configuration of the serving cell based on the occurrence of the event.
[0006]
In another exemplary aspect, a wireless communications apparatus comprising a processor is disclosed. The processor is configured to implement a method described herein.
[0007]
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.
[0008]
The details of one or more implementations are set forth in the accompanying attachments, 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

[0009]
FIG. 1 shows an exemplary schematic diagram of a system architecture for Dual Connectivity (DC) .
[0010]
FIG. 2 illustrates a block diagram of a method to manage a state of a serving cell.
[0011]
FIG. 3 illustrates a block diagram of a method to recover a failed beam of a serving cell.
[0012]
FIG. 4 illustrates a block diagram to configure and activate a TCI state configuration.
[0013]
FIG. 5 illustrates a block diagram of a method to manage a serving cell.
[0014]
FIG. 6 shows an example of a wireless communication system where techniques in accordance with one or more embodiments of the present technology can be applied.
[0015]
FIG. 7 is a block diagram representation of a portion of a hardware platform.

DETAILED DESCRIPTION

[0016]
The development of the new generation of wireless communication –5G New Radio (NR) communication –is a part of a continuous mobile broadband evolution process to meet the requirements of increasing network demand. NR will provide greater throughput to allow more users connected at the same time. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios.
[0017]
As NR emerges in the wireless domain, UEs will be capable of supporting both protocols at the same time. FIG. 1 shows an exemplary schematic diagram of a system architecture for Dual Connectivity (DC) . The current base station (referred to as the first network element 101) in the core network 103 may select a suitable base station for the UE 100 to function as the second network element 102. For example, the suitable based station can be selected by comparing the channel quality of the base station with a predetermined threshold. Both base stations can provide radio resources to the UE 100 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 may establish a user plane interface 105 for the UE 100. An interface 106 (e.g., Xn interface) inter-connects the two network elements. On the wireless interface side, the first and the second network elements (101 and 102) may provide radio resources using the same or different Radio Access Technologies (RATs) . Each of the network element can schedule transmissions with the UE 100 independently. The network element that has a control plane connection to the core network is referred to as the master node (e.g., the first network element 101) , and the network element that has only a user plane connection with the core network is referred to as the secondary node (e.g., the second network element 102) . In some cases, the UE 100 can be connected to more than two nodes, with one node acting as the primary note and the remaining acting as the secondary nodes.
[0018]
In some embodiments, a UE can support a LTE-NR dual connection (DC) . For example, one of the typical LTE-NR dual connectivity architectures can be set up as follows: the master node is an LTE RAN node (e.g., eNB) and the secondary node is an NR RAN node (e.g., gNB) . The eNB and the gNB are simultaneously connected the Evolved Packet Core (EPC) network (e.g., LTE core network) . The architecture shown in FIG. 1 can also be modified to include various master/secondary node configurations. For example, a NR RAN node can be the master node and the LTE RAN node can be the secondary node. In such case, the core network for the master NR RAN node is a Next Generation Converged Network (NG-CN) .
[0019]
UE capabilities for the LTE protocol and the NR protocol in LTE-NR DC include two parts: common capabilities of the UE that are applicable to both LTE and NR protocols for single connectivity scenarios, and band combination capabilities of the UE that are relevant for dual connectivity scenarios. When the UE has multiple simultaneous connections with network nodes, the frequency bands used for different network nodes must cooperate with each other regardless of the RAT type (s) used. Here, the term “cooperate” means that the UE can operate in the frequency bands without any conflicts or substantial interference –that is, the frequency bands can co-exist. For example, the 3rd Generation Partnership Project (3GPP) Standards specify a set of band combinations that can cooperate with each other. If frequency band 1 and frequency band 2 are not specified as a valid band combination, the UE cannot use frequency band 1 in communication with node 1 and frequency band 2 in communication with node 2 and the same time.
[0020]
This patent document describes techniques that can be implemented to manage a configuration state of a serving cell. In some cases, a base station (or “network node” ) may add a secondary cell (SCell) to an activated cell group. A UE (or “terminal” ) may start to monitor a physical downlink control channel (PDCCH) on the SCell, and be ready for uplink transmission (e.g., physical uplink control channel (PUCCH) , physical uplink shared channel (PUSCH) ) after the terminal receives a RRC message containing configuration information for adding the SCell.
[0021]
In some systems, a SCell may be configured in any of an activated state, a deactivated state, or a dormant state based on receipt of a medium access control (MAC) control element (CE) or RRC message. When a SCell is in dormant state, the SCell may be configured with dormant state specific channel quality Indication (CQI) resources. The UE may perform channel monitoring and CQI reporting without monitoring a PDCCH. If a SCell is in deactivated state, the UE may not perform CQI reporting or PDCCH monitoring on the SCell. With CQI reporting in the dormant state, the delay in time domain needed to activate a SCell in the dormant state may be smaller than that needed from deactivated state.
[0022]
However, some systems do not address issues when implementing similar functions to 5G new radio (NR) system. These issues may include bandwidth part (BWP) operation, beam management, uplink time alignment when transit a serving cell from/to dormant state, or when keep a serving cell in dormant state.
[0023]
In any of the example embodiments of the present disclosure, the base station may configure a serving cell to a cell group in one of an activated, deactivated or dormant state by a RRC message or a MAC CE. The base station may configure one or more timers to control the state transition of a serving cell. Specifically, the base station may configure a deactivation timer controlling whether to switch the serving cell state to a deactivated state, or a hibernation timer controlling whether to switch the serving cell state to a dormant state. For example, if the deactivation timer associated with a serving cell expires, the UE may transition/modify the serving cell state to the deactivated state. Similarly, if the hibernation timer associated with a serving cell expires, the UE may transition/modify the serving cell into dormant state if the serving cell is in an activated state.
[0024]
In any of the example embodiments of the present disclosure, a configuration configured for a serving cell may be serving cell specific, i.e. common for all UEs and/or dedicated to a UE, i.e. a different UE may be configured with a configuration dedicated for the serving cell.
[0025]
Example Embodiment 1:
[0026]
Example Embodiment 1 relates to BWP operation when adding a serving cell and modifying a state of the serving cell. Generally, a BWP may be a segment in frequency domain within a cell carrier bandwidth. The BS may configure a serving cell with one or more BWPs via an RRC message or system information. In an 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) .
[0027]
FIG. 2 illustrates a block diagram of a method to manage a state of a serving cell. A state of a serving cell included within 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 assigning a BWP ID for each of BWPs or by configuring a set of parameters to for a BWP. Specifically, a serving cell may be configured with 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 first active uplink BWP ID (firstActiveUplinkBWP-Id) .
[0028]
With a serving cell, one or more BWPs may be activated by the UE, which may be referred to as an active BWP. The active BWP may include active uplink BWP and active downlink BWP. A UE may be configured with a BWP inactivity timer associated with an active BWP. In an embodiment, when a BWP inactivity timer expires, the UE may modify/switch an active BWP to one of a default BWP (indicated by defaultDownlinkBWP-Id) if the default downlink BWP is configured for the serving cell, or an initial BWP (indicated by initialDownlinkBWP) if default downlink BWP is not configured for the serving cell. As part of active BWP switching/modification, a BWP inactivity timer associated with a new active BWP may be started or restarted if the timer is already started.
[0029]
A terminal may modify a state configuration of the serving cell (block 204) .
[0030]
In a first case, a serving cell may be configured in a dormant state when the serving cell is added to a cell group. In an embodiment, a terminal may activate a downlink (DL) BWP or an uplink (UL) BWP according to first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and first active uplink BWP (indicated by firstActiveUplinkBWP-Id) configured for this serving cell respectively.
[0031]
In an embodiment, the UE may activate a DL BWP or UL BWP according to a first active downlink BWP for dormant state and first active uplink BWP for dormant state. The base station may configure the serving cell with the first active downlink BWP for dormant state or first active uplink BWP for dormant state via a RRC message or system information for the serving cell. The first active BWP configuration for a serving cell state modified to a dormant state may be different to the configuration for the serving cell state modified to an activated state.
[0032]
In an embodiment, the UE may activate a DL BWP or UL BWP according to default downlink BWP configuration or default uplink BWP configuration if the default BWP configuration is configured by the BS for this serving cell. If the default BWP is not configured at the serving cell, the DL BWP and UL BWP may be activated according to the initial BWP configuration configured for the serving cell.
[0033]
In an embodiment, the UE may activate a DL BWP or UL BWP according to an initial BWP configuration configured for the serving cell.
[0034]
In a second case, the serving cell may be modified from an activated state to a dormant state. In this case, the UE may keep a currently active BWP for the serving cell. The UE may keep or restart an associated BWP inactivity timer running if the timer is running. This may indicate that when the serving cell state is modified from the activated state to the dormant state, the BWP modification/switching may not be performed until the associated BWP inactivity timer expires or a signaling via PDCCH is received to switch the active BWP for this serving cell.
[0035]
In an embodiment, the current active BWP for this serving cell may be kept active. The UE may also stop a BWP inactivity timer associated with the active BWP if it is running. If the serving cell is modified/switched from the activated state to the dormant state, the active BWP of the serving cell may be the same as it is in activated state. The BWP switching may be triggered by receiving a message, receiving a MAC CE, or a PDCCH DCI that indicates a BWP modification for the serving cell.
[0036]
In an embodiment, the active BWP may be modified/switched to a BWP that is used when the serving cell is switched/modified from the activated state to the dormant state. This BWP may comprise a downlink BWP or a uplink BWP. This BWP may be configured to be activated when the associated serving cell is switched/modified from activated state to dormant state. The BWP may be configured by the base station via a RRC message, or system information, or indicated by the MAC CE or PDCCH DCI, which is used to modify the serving cell to the dormant state. The UE may start or restart an BWP inactivity timer upon the BWP switching.
[0037]
In an embodiment, the active BWP may be switched to a default BWP if the default BWP for the serving cell is configured. Otherwise, UE may perform BWP switching to an initial BWP if the initial BWP is configured for the serving cell. If the serving cell state transitions/switches from the activated to dormant state, the active BWP of the serving cell may be different than the active BWP before the serving cell state transition.
[0038]
If the serving cell is configured with uplink radio resources for channel quality information (CQI) or channel state information (CSI) reporting on another serving cell, the UE may deactivate any active uplink BWPs associated with the serving cell and stop any BWP inactivity timers associated with the active uplink BWP if it is running. The base station may control the UE behavior on whether to deactivate any active uplink BWPs in this case via an indicator included in a MAC CE, a RRC message, or a PDCCH DCI.
[0039]
In a third case, the serving cell state may modify/transition from a deactivated state to a dormant state. In this case, the terminal may activate DL BWP or UL BWP according to first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and first active uplink BWP (indicated by firstActiveUplinkBWP-Id) configured for this serving cell. The UE may start a BWP inactivity timer upon the activation of the DL BWP or UL BWP.
[0040]
In some embodiments, the terminal may activate a DL BWP or UL BWP according to a first active downlink BWP for dormant state and first active uplink BWP for dormant state respectively, which may be configured by the base station via a RRC message or system information for the serving cell. The first active BWP configuration for a serving cell being modified to the dormant state may be different than the configuration for the serving cell state being modified to the activated state. The UE may start a BWP inactivity timer upon activating the DL BWP or UL BWP.
[0041]
In some embodiments, the terminal may activate a DL BWP or UL BWP according to configured default BWP if the default BWP for the serving cell is configured, or according to initial BWP configured for this serving cell if the default BWP for this serving cell is not configured. More specifically, if a default downlink BWP is configured, the terminal may activate UL BWP according to the configured default downlink BWP. If the default downlink BWP is not configured, the terminal may activate a downlink BWP according to initial downlink BWP. The terminal may activate uplink BWP according to initial uplink BWP.
[0042]
In some embodiments, the terminal may activate no uplink BWP for the serving cell if an uplink resource for CQI/CSI reporting for the serving cell is configured on another serving cell.
[0043]
In a fourth case, a serving cell state may be modified from the dormant state to a deactivated state upon either receiving a MAC CE or upon a timer expiration. In this case, the UE may deactivate any active BWP associated with the serving cell and stop BWP inactivity timer if the timer is running.
[0044]
In a fifth case, a serving cell state may be modified from the dormant state to an activated state. In this case, the UE may perform BWP switching to first active downlink BWP and first active uplink BWP according to first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and first active uplink BWP (indicated by firstActiveUplinkBWP-Id) configured for this serving cell respectively, if a previous active UL BWP in dormant or active DL BWP in dormant are not the configured first active downlink BWP or first active uplink BWP respectively. The UE may start or restart the BWP inactivity timer.
[0045]
In some embodiments, the UE may activate the DL BWP or UL BWP according to a first active downlink BWP (indicated by firstActiveDownlinkBWP-Id) and a first active uplink BWP (indicated by firstActiveUplinkBWP-Id) respectively, if there is no active BWP before the serving cell state transition. The UE may start the BWP inactivity timer.
[0046]
In some embodiments, the UE may keep or maintain the active BWP of the serving cell when the serving cell is in dormant state and before the cell state modification, and start a BWP inactivity timer associated with the active BWP if it is not running or restart BWP inactivity timer if it is running, or in some embodiments, keep the BWP inactivity timer associated with the active BWP running.
[0047]
In some embodiments, the UE may perform BWP switching to a first active downlink BWP or first active uplink BWP defined to be activated upon the serving cell state transition from a dormant to an activated state and are configured by the base station via a RRC message or system information. If the serving cell state is transitioned/modified from a dormant to an activated state, the first active BWP may be different to that when the serving cell transit from deactivated to activated state. The UE may start/restart the BWP inactivity timer.
[0048]
If the UE starts or restarts a BWP inactivity timer when it is in dormant state, or upon transition the serving cell state to dormant state, the UE may use a BWP inactivity timer length dedicated for a dormant state, i.e. the base station may configure the BWP inactivity timer length for a serving cell in activated state and dormant state separately by comprising separate information IEs in a RRC message or system information.
[0049]
If a serving cell is in dormant state, or if the serving cell is modified to a dormant state from the activated state or the deactivated state, the UE may perform a step on an active BWP. One such step may include reporting CQI or CSI for the active BWP via configure uplink resources for CQI or CSI reporting. Another such step may include transmitting PUCCH on the active BWP, if the PUCCH is configured on the active BWP. Another such step may include suspending any configured uplink grants of configured grant type 1 or type 2 on the active BWP. The UE may stop monitoring PDCCH on the active BWP. The UE may transmit random-access channel (RACH) on the BWP if PRACH occasions are configured on the active BWP.
[0050]
The present embodiments may provide solutions on how to perform BWP operation when the serving cell state is modified to dormant state or from dormant state.
[0051]
The present embodiments may reduce scheduling delay caused by BWP switching on serving cell state transition. When a serving cell state transition from dormant state to activated state, the BWP may not be changed/switching by applying some of the methods in this embodiment. For example, when a serving cell state is modified from activated state to dormant state, and from deactivated state to dormant state, and when configure a serving cell state as dormant via RRC message, the UE activate or switch active DL BWP or UL BWP according to a BWP configuration which is activated or switched to when the serving cell is activated from dormant state. The said BWP configuration may be first active downlink BWP and first uplink BWP, or first active BWP for dormant state and first active uplink BWP for dormant state, or initial downlink and uplink BWP. In this way, the active BWP is the same before and after serving cell state is modified to activated state from dormant state. Thus the CSI/CQI measurement on the downlink active BWP may be valid after the serving cell state transition. The BS can schedule on the active BWP according the CSI/CQI reported before the cell state transition, i.e. not need to waiting for new CSI/CQI measurement and reporting due to active BWP is changed before and after the serving cell state transition.
[0052]
Example Embodiment 2:
[0053]
Example embodiment 2 relates to how a configured uplink grant and configured downlink assignment are handled when a serving cell is added in a dormant state, including the serving cell state transition between the dormant state.
[0054]
Configured grant type 1 and configured grant type 2 may be a set of periodic uplink resources. A UE may utilize these uplink resources without dynamic scheduling signaling to save data transmission delay.
[0055]
In a first case, a serving cell may be configured as a dormant state when the serving cell is added to a cell group. The UE may store configured grant Type 1 configuration associated with a BWP of the serving cell or associated with a serving cell provided by an RRC message from the base station. The UE may suspend any configured grant type 1 associated with a BWP of the serving cell or associated with the serving cell.
[0056]
In a second case, a serving cell state may be modified from an activated state to a dormant state. In this case, the UE may clear any configured downlink assignment associated with any BWP of the serving cell. The UE may suspend a configured downlink assignment associated with any BWP of the serving cell. The configured downlink assignment may not be cleared/released when the serving cell is modified from activated state to dormant state.
[0057]
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 the serving cell. Suspending any configured uplink grant type 2 may mean that the configured uplink grant type 2 associated with a BWP or associated with the serving cell is not released when the serving cell is modified from activated state to dormant state.
[0058]
The UE may suspend any configured uplink grant Type 1 associated with previous active BWP or any BWP of the serving cell.
[0059]
In a third case, the serving cell may be modified from a dormant state to an activated state. In this case, the UE may initialize (or re-initialize) any suspended configured uplink grants of configured grant Type 1 associated with the active BWP of this serving cell. The UE may initialize (or re-initialize) any suspended configured uplink grants of configured grant Type 2 associated with active BWP of this serving cell. The UE may initialize (or re-initialize) any suspended configured downlink assignment associated with active BWP of this serving cell.
[0060]
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 serving cell. The UE may clear any stored configured downlink assignment associated with any BWP of the serving cell. The UE may also keep suspending any configured uplink grant Type 1 associated with any BWP of the serving cell.
[0061]
If there is any configured downlink assignment, configured uplink grant type 1, or configured uplink type 2 associated with a BWP or associated with the serving cell to be initiated due to the associated serving cell state transition from dormant state to activated state, or due to the serving cell is added as activated or dormant state, the UE may perform one of various steps. Such a step may include the UE starting to receive downlink transmission on the configured downlink assignment no earlier than when the UE is ready for PUCCH transmission for the serving cell. Such a step may include the UE starting to perform uplink transmission on the configured uplink grants no earlier than when the UE is ready for PDCCH monitoring on the serving cell.
[0062]
In some embodiments, when a UE is in the dormant state, it may suspend the configured grant type 1 or configured grant type 2 or configured assignment instead of clearing them. When the BS activates the serving cell, the UE may activate/re-initialize the suspended configured grant type 1 or configured grant type 2 or configured assignment, i.e. the delay needed for an additional MAC to re-initiate configured grant or configured assignment may be saved.
[0063]
When the serving cell is in dormant state, the configured downlink assignment and configured uplink grants may be suspended but not cleared. Thus, when the serving cell is activated from dormant state, the UE can restore (re-initiate) the suspended configured downlink assignments and configured uplink grants without the delay caused by reconfiguration of configured assignment or configured uplink grants otherwise.
[0064]
Example Embodiment 3:
[0065]
Example Embodiment 3 relates to UE behavior when a beam failure is detected on the reference signal (e.g. SSB or CSI-RS) on a serving cell in a dormant state. FIG. 3 illustrates a block diagram of a method to recover a failed beam of a serving cell.
[0066]
The terminal may detect a beam failure of the serving cell (block 302) . For a serving cell in the dormant state, UE may perform beam failure detection on the serving cell by counting beam failure instance indication from the lower layers 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.
[0067]
In some embodiments, if the dormant serving cell detects a beam failure, the UE may perform at least one of various steps. Such a step may include the UE indicating to a base station that beam failure is detected on the serving cell (block 304) . The UE may indicate a beam failure by transmitting a RRC message or a MAC CE to the base station. The RRC message may be transmitted from UE to the base station via the cell group that the serving cell belongs to, or via the cell group different to that the serving cell belongs to. The MAC CE may be transmitted from the UE to the base station via another serving cell of the cell group the serving cell belongs to, or via another serving cell of the cell group different to which this serving cell belongs to.
[0068]
Such a step may include the UE changing the serving cell state to a deactivated state autonomously, or after receiving a MCE CE or a RRC message which indicates a request to modify the serving cell to a deactivated state. The UE may keep this serving cell in a dormant state before receiving a RRC message or MAC CE that configure the serving cell with another state.
[0069]
Such a step may include the UE triggering a beam failure recovery procedure on this serving cell autonomously. A base station may transmit an indication to the terminal to initiate a beam failure recovery procedure (block 306) . The terminal may initiate a beam failure recovery procedure (block 308) . A base station may configure whether the UE can trigger beam failure recovery procedure for this serving cell in dormant state. By default, if this serving cell is a primary cell of a cell group (SpCell) , the UE may trigger a beam failure recovery procedure when a beam failure is detected on the serving cell. The UE may initiate the beam failure recovery if beam failure recovery is allowed for a dormant state serving cell, UE initiates beam failure recovery procedure on this serving cell immediately after this serving cell is activated. In some embodiments, the UE initiates beam failure recovery procedure immediately upon the beam failure is detected on this serving cell.
[0070]
The UE may trigger beam failure recovery procedure on the serving cell when it receives a PDCCH order via another serving cell of the same cell group or via another serving cell of a different cell group. In this case, the base station (BS) may indicate the UE to trigger a beam failure recovery for this serving cell when the BS receives a RRC message or a MAC CE transmitted from the UE to the BS to indicate beam failure is detected on this serving cell.
[0071]
If a beam failure recovery is allowed for a dormant state serving cell, UE may initiate beam failure recovery procedure on this serving cell immediately after this serving cell is activated. The UE may initiate beam failure recovery procedure immediately upon the beam failure is detected on this serving cell.
[0072]
The UE may perform BWP switching to switch an active BWP to default BWP if default BWP is configured for this serving cell, or to initial downlink BWP or initial uplink BWP if default BWP is not configured for this serving cell or keep current active BWP and the associated BWP inactivity timer if it is running. The UE may stop CQI/CSI reporting for this serving cell.
[0073]
In an embodiment, the beam failure recovery procedure may be implemented by a random-access procedure for beam failure recovery (RA for beam failure recovery) .
[0074]
If UE indicates to the BS that beam failure is detected on the serving cell by a RRC message or a MAC CE, the RRC message or the MAC CE may include the cell group ID of the cell group to which the serving cell belongs, an indicator to indicate whether the serving cell belongs to secondary cell group, an indicator to indicate whether the serving cell belongs to master cell group, an indicator to indicate whether the serving cell belongs to the cell groups different to the cell on which the MAC CE is transmitted, the serving cell ID or index of the serving cell to identify the serving cell in a cell group, or across all cell groups configured to the UE.
[0075]
The message may also include a measurement result of the serving cell, which may include cell level measurement results, or beam level measurement results. The beam level measurement results may include a list of reference signal ID, including SSB index and CSI-RS index, and the measurement quality on the reference signals.
[0076]
When beam failure is detected on the serving cell in dormant state, the BS can be notified of the beam failure. Thus, when the BS intend to activate for data scheduling, it can avoid activating a serving cell occurs beam failure. Otherwise, if the BS activating a serving cell occurs beam failure, more delay will be caused to perform beam failure recovery, e.g. by trigger a RACH procedure. On the other side, when beam failure occurs, the present embodiments may provide methods on how to trigger beam failure recovery procedure to restore the beam for this serving cell.
[0077]
Example Embodiment 4:
[0078]
Example Embodiment 4 relates to a transmission configuration indicator (TCI) state configuration when adding a serving cell in an activated or dormant state. FIG. 4 illustrates a block diagram to configure and activate a TCI state configuration.
[0079]
In many cases, TCI state information is used to indicate the beam for UE monitoring PDCCH or PDSCH by associating one or two downlink reference signals (SSB or CSI-RS in NR) with a corresponding quasi-colocation (QCL) type.
[0080]
A set of TCI state information may include a TCI state ID, a cell ID of the serving cell in which the reference signal is configured, a BWP ID of downlink BWP in which the downlink reference signal is locate, a QCL type, and the reference signal ID (SSB index, or CSI-RS resource ID) . When the serving cell ID is not configured in the TCI state information, the reference signal may be located in the serving cell for which the TCI state information is configured.
[0081]
In many cases, the configured TCI states for PDCCH and PDSCH reception may be deactivated upon configuration via a RRC configuration. Also, in many cases, to configure the TCI state information used for PDCCH monitoring, the BS may first configure a list of candidate TCI state information for a CORSET configured for a downlink BWP of the serving cell via a RRC message. Second, the BS may indicate to the UE which TCI state information is used for PDCCH monitoring on a specific CORSET configured for a downlink BWP of a serving cell by a MAC CE transmitted from the BS to the UE, and comprising a serving cell ID which is used to indicate which serving cell the MAC CE is applied for, a control resource set ID (CORESET ID) which is used to indicate the CORESET for which the TCI state is indicated, a TCI state ID which is one of the candidate PDCCH TCI state which are configured via RRC message. The UE may apply the indicated TCI state information upon receiving the MAC CE.
[0082]
In some cases, 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 a BWP via a RRC message. The BS may indicate the UE via a MAC CE which comprise a BWP ID, a bitmap to indicate which configured candidate TCI state information for PDSCH reception is activated. The BS may indicate which activated TCI state information is used for PDSCH reception on the BWP via a PDCCH signaling. The UE may apply a corresponding TCI state information for PDSCH reception on the BWP.
[0083]
Example Embodiment 4 may relate to indicating the TCI state information used for PDCCH monitoring or PDSCH reception when the BS configures a serving cell as activated state or dormant state via RRC message or MAC CE. This may reduce the delay caused by the additional MAC CE and PDCCH signaling.
[0084]
A candidate list of TCI state information may be configured (block 402) . When the BS configures a serving cell as activated state or dormant state via a RRC message, e.g. to adding a serving cell to a cell group or to configure serving cell, the BS may include the serving cell configuration in the RRC message. The RRC message may comprise at least one of following: the serving cell ID, the cell group ID to which the serving cell belongs, 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) , comprise a list of candidate TCI state information for PDCCH reception on the CORESET.
[0085]
The RRC message may include the serving cell state information to indicate the state of the serving cell on application of the RRC message. The serving cell state indicated in the RRC message may be activated, dormant, or deactivated.
[0086]
The RRC message may indicate which TCI state is used for PDCCH reception on a CORESET of a specific BWP of the serving cell via a RRC message. For a CORESET configured for a downlink BWP of the serving cell, the RRC message may indicate the TCI state ID or an index to 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.
[0087]
A list of TCI state information from the candidate list may be activated (block 404) . On reception of the RRC message, the UE may apply the indicated TCI state information for PDCCH monitoring on the corresponding CORSET.
[0088]
An activated TCI state may be indicated to a terminal (block 406) . To configure the TCI state information used for PDSCH reception on a downlink BWP of a serving cell, the BS may indicate the activated TCI state information for PDSCH reception on a BWP via the RRC message. Then the BS may indicate which activated TCI state information is used for PDSCH reception via a PDCCH signaling. The UE may then apply the TCI state information indicated by the PDCCH signaling for PDSCH reception on the BWP.
[0089]
In an embodiment, the BS may indicate which TCI state information is used for PDSCH reception on a downlink BWP in the RRC message besides the candidate TCI state information for PDSCH reception or activated TCI state information for PDSCH reception. In this case, the UE may apply the indicated TCI state to be used for PDSCH reception on the BWP upon reception of the RRC message.
[0090]
To indicate the activated TCI state information for PDSCH reception or TCI information used for PDSCH reception or TCI information, the RRC message may include an indicator for each candidate TCI state information for PDSCH reception on a BWP. The indicator can be defined to indicate whether the corresponding TCI state information is activated or can be defined to indicate whether corresponding TCI state information is (actually) used for PDSCH reception on the BWP.
[0091]
For a 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 can be TCI state ID, a set of TCI state information, or an index to the candidate TCI state information list configured for the CORESET.
[0092]
The BS may determine the candidate TCI state information for PDCCH or PDSCH, the activated TCI state information for PDSCH, and the TCI state information to be used for PDCCH and PDSCH reception according to the radio network deployment, serving cell configuration and measurement report sent from UE before configuring the serving cell to the UE.
[0093]
The BS may configure the TCI state information used for PDCCH or PDSCH monitoring after the UE applies the configuration carried in the RRC message without an additional indication via a MAC CE. Accordingly, the delay caused by the additional MAC CE may be saved.
[0094]
When the BS configures the serving cell in activated state or dormant state via a RRC message, the BS can configure the TCI state information for PDCCH reception or PDSCH reception in the same RRC message. Thus, upon reception of the RRC message, the UE can apply the TCI state information for PDCCH reception or PDSCH reception without an additional MAC CE to indicate the TCI state information.
[0095]
Example Embodiment 5:
[0096]
Example Embodiment 5 relates to how to maintain uplink time alignment cross cell groups.
[0097]
In many cases, uplink time alignment for a serving cell is implemented by Time 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 comprise a Time Advance Group (TAG ) ID, and a TA command information which is used to control the amount of time advancement for the TAG identified by the TAG ID. A serving cell may be configured with a TAG ID to indicate the TAG of the serving cell belongs to. The TAG ID may identify the TAG within the scope of a cell group.
[0098]
To support uplink time alignment cross cell group, the BS may transmit a TA command MAC CE via a serving of cell group A for a TAG defined for cell group B. The TA command MAC CE include at least one of: a cell group ID information, TAG ID, and TA command information. The cell group ID information may be indicated implicitly by defining a dedicated MAC CE type (aLogical channel ID, LCID) indicated in the MAC CE sub-header, and dedicated for this usage. The UE may apply the TA command comprised in the MAC CE for the TAG indicated by TAG ID of the cell group B.
[0099]
In an embodiment, to support uplink time alignment cross cell group, the BS may configure a serving cell of cell group B with a TAG ID defined for cell group A via a RRC message or a MAC CE. Specifically, the BS may configure the serving cell B with a cell group ID of cell group A along with TAG ID defined for cell group A. The BS may configure the TAG ID defined for cell group A to the UE by define an information element (IE) , e.g. this IE is defined as a TAG ID of another cell group. Upon receiving a TA command MAC CE comprising the TAG ID defined for cell group A, UE may apply the TA command to the serving cell B.
[0100]
The BS may define a TAG with unique TAG ID among cell groups via a RRC message. The BS configures a serving cell of any cell group with this TAG ID to indicate that this serving cell belongs to the TAG indicated by this TAG ID. The TA command MAC CE may include this TAG ID may be transmitted via any cell group. Upon receiving a TA command MAC CE comprising this TAG ID, the UE may apply the TA command to all serving cells that belong to this TAG.
[0101]
The BS may associate a TAG A defined for cell group A to a TAG B defined for cell group B, by a TAG ID A in the configuration of TAG B. The UE may identify and apply TA command comprised in TA command MAC CE which comprise TAG ID A to TAG B on reception of the MAC CE. The TA command MAC CE comprising TAG ID A may be transmitted via cell group A. (equivalent)
[0102]
By providing information to support uplink time alignment cross cell groups, serving cell of a cell group may be modified/transitioned to a dormant state, i.e. only CSI/CQI reporting is performed on this cell group while the UE does not monitor PDCCH on any serving cells of this cell group.
[0103]
TA management can be implemented cross cell groups. In some cases, TAG may only comprise serving cells of a same cell group. Further, a TA command MAC CE may not be used for time advance adjustment cross cell groups. By applying the methods in this embodiment, a serving cell can be configured to a TAG which include serving cells of any cell groups, or can be configure to a TAG which is defined for a cell group different to the cell group to which the serving cell belongs, or two TAG defined for different cell group can be associated, or a TA command MAC CE can be transmitted cross cell groups, and thus the BS can adjust time alignment of a serving cell by transmit TA command MAC CE via a cell group different to the cell group to which the serving cell belongs.
[0104]
Example Embodiment 6:
[0105]
Example Embodiment 6 relates to how to implement dormant state of a cell group where all serving cells in the cell group are in deactivated or dormant state, i.e. no serving cell in activated state. When a cell group is modified to a dormant state, there may be at least one serving cell in dormant state. In an embodiment, there is at least one serving cell is configured with PUCCH resource for CSI or CQI reporting.
[0106]
The BWP operation for serving cell of this cell group can be implemented by one of the methods provided in Example Embodiment 1. The beam failure handling for serving cell of this cell group can be implemented by one the methods provided in Example Embodiment 3. The TCI state maintenance can be implemented by one the method provided in Example Embodiment 4. The uplink time alignment is maintained by one of the methods provided in Example Embodiment 5.
[0107]
The BS may indicate the state of serving cell of this cell group via another cell group by including cell group information in the MAC CE used for serving cell state transition.
[0108]
This MAC CE may include one of following: cell group ID information, the target state information, the cell ID information. The cell group ID information may be indicated implicitly by defining a dedicated MAC CE type, i.e. a Logical channel ID, LCID indicated in the MAC sub-header, and dedicated for this usage. The target state information may be indicated by the different MAC CE types, i.e. the LCID indicated in MAC sub-header, e.g. MAC CE for activating, MAC CE for deactivating, MAC for transiting to dormant state (hibernating) are defined separately with different LCIDs. The cell ID information may be represented by a bitmap comprised in the MAC CE and each bit of the bitmap re-present a serving cell configured to a cell group.
[0109]
The BS can modify/transition all serving cells of a cell group into an activated state, dormant state, or deactivated state. The UE power may be saved due to having no PDCCH monitoring on all serving cells of this cell group, and at least one serving cell in dormant state can be activated rapidly.
[0110]
FIG. 5 illustrates a block diagram of a method to manage a serving cell. A terminal may detect an occurrence of an event (block 502) . The terminal may modify the state configuration of the serving cell based on the event (block 504) .
[0111]
In some embodiments, the event includes an expiration of a deactivation timer, and wherein the state configuration is modified to a deactivated state.
[0112]
In some embodiments, the event includes an expiration of a hibernation timer, and wherein the state configuration is modified to a dormant state.
[0113]
In some embodiments, the event includes receiving a message from a communication node, wherein the message includes the state configuration of the serving cell.
[0114]
In some embodiments, the event includes identifying a beam failure of the serving cell.
[0115]
In some embodiments, the method includes modifying the state configuration of the serving cell from an activated state to the dormant state.
[0116]
In some embodiments, the method includes stopping, by the terminal, a BWP inactivity timer upon modifying the state configuration of the serving cell from the activated state to the dormant state.
[0117]
In some embodiments, the method includes modifying, by the terminal, at least one of an active downlink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and an active uplink BWP of the serving cell according to a first active uplink BWP configured for the serving cell.
[0118]
In some embodiments, the method includes modifying, by the terminal, the state configuration of the serving cell from a deactivated state to the dormant state.
[0119]
In some embodiments, the method includes activating, by the terminal, at least one of a downlink BWP according to a first active downlink BWP configured for the serving cell and an uplink BWP according to a first active uplink BWP configured for the serving cell.
[0120]
In some embodiments, the method includes activating, by the terminal, a downlink BWP according to a first active downlink BWP configured for the dormant state of the serving cell, or an uplink BWP according to a first active uplink BWP configured for the dormant state of the serving cell.
[0121]
In some embodiments, the method includes activating, by the terminal, the downlink BWP or the uplink BWP according to a default BWP for the serving cell that includes the default BWP.
[0122]
In some embodiments, the method includes modifying, by the terminal, the state configuration of the serving cell from the dormant state to a deactivated state.
[0123]
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.
[0124]
In some embodiments, the method includes modifying, by the terminal, the state configuration of the serving cell from the dormant state to an activated state.
[0125]
In some embodiments, the method includes modifying, by the terminal, at least one of an active downlink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and an active uplink BWP of the serving cell according to a first active uplink BWP configured for the serving cell.
[0126]
In some embodiments, the method includes activating, by the terminal, at least one of a downlink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and an uplink BWP of the serving cell according to a first active uplink BWP configured for the serving cell, when there is not an active BWP at the serving cell.
[0127]
In some embodiments, the method includes starting, by the terminal, an inactivity timer associated with an active uplink BWP or an active downlink BWP.
[0128]
In some embodiments, the method includes reporting, by the terminal, at least one of a channel quality indicator (CQI) and a channel state information (CSI) for a downlink BWP to the communication node via configured uplink resources.
[0129]
In some embodiments, the method includes suspending, by the terminal, at least one of a configured downlink assignment, 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 the serving cell.
[0130]
In some embodiments, the method includes initializing, 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 assignment associated with at least one of an active uplink BWP and an active downlink BWP of the serving cell.
[0131]
In some embodiments, the method includes identifying, by the terminal, a beam failure on a reference signal of the serving cell.
[0132]
In some embodiments, the method includes transmitting, by the terminal, a beam failure indication to the communication node indicating the beam failure of the serving cell.
[0133]
In some embodiments, the beam failure indication is transmitted via one of a second serving cell with a cell group that includes the serving cell and a third serving cell that includes a cell group that does not include the serving cell.
[0134]
In some embodiments, the method includes modifying, by the terminal, the state configuration of the serving cell from the dormant state to a deactivated state upon identifying a beam failure or based on receiving a request from the communication node to modify the state configuration of the serving cell to the deactivated state.
[0135]
In some embodiments, the method includes initiating, by the terminal, a beam failure recovery procedure on the serving cell based on determining that the terminal is allowed to initiate the beam failure recovery procedure.
[0136]
In some embodiments, the beam failure recovery procedure is initiated based on receiving a PDCCH order at the terminal, wherein the PDCCH order is transmitted via one of a second serving cell with a cell group that includes the serving cell and a third serving cell that includes a cell group that does not include the serving cell.
[0137]
In some embodiments, the method includes modifying, by the terminal, one of the active uplink BWP or active downlink BWP of the serving cell to one of a default BWP if the default BWP is configured for the serving cell and an initial BWP if the default BWP is not configured for the serving cell.
[0138]
In some embodiments, the method includes stopping, by the terminal, CQI and CSI reporting for the serving cell.
[0139]
In some embodiments, the beam failure indication is transmitted via one of a 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 the serving cell, a serving cell identifier identifying the serving cell in the cell group, and a measurement result of the serving cell.
[0140]
In some embodiments, the message from the communication node indicating configured state configuration of the serving cell 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) state information for physical downlink shared channel (PDSCH) reception, a control-resource set (CORESET) information configured for a downlink BWP, wherein the CORESET information includes candidate TCI information for PDCCH reception.
[0141]
In some embodiments, the message from the communication node indicating configured state configuration of the serving cell indicates a TCI state used for PDCCH reception on a CORESET of a BWP of the serving cell.
[0142]
In some embodiments, the message indicates a TCI state identifier or an index to a candidate TCI state information associated with the CORESET to indicate the TCI state 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 configure for the CORESET to indicate whether TCI state information is used for PDCCH reception on the CORESET, and wherein the terminal utilizes the TCI state information for PDCCH reception.
[0144]
In some embodiments, the message includes an indicator for each candidate TCI state information for physical downlink shared channel (PDSCH) reception on a downlink BWP, wherein the indicator indicates whether the candidate TCI state information is activated or used for PDSCH reception.
[0145]
In some embodiments, the message includes activated TCI state or TCI state information used for PDSCH reception, wherein the TCI state information includes at least one of a TCI state identifier and an index for the candidate TCI state information configured for a BWP.
[0146]
FIG. 6 shows an example of a wireless communication system where techniques in accordance with one or more embodiments of the present technology can be applied. A wireless communication system 600 can include one or more base stations (BSs) 605a, 605b, one or more wireless devices 610a, 610b, 610c, 610d, and a core network 625. A base station 605a, 605b can provide wireless service to wireless devices 610a, 610b, 610c and 610d in one or more wireless sectors. In some implementations, a base station 605a, 605b includes directional antennas to produce two or more directional beams to provide wireless coverage in different sectors.
[0147]
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. A first base station 605a can provide wireless service based on a first radio access technology, whereas a second base station 605b can provide wireless service based on a second radio access technology. The base stations 605a and 605b may be co-located or may be separately installed in the field according to the deployment scenario. The wireless devices 610a, 610b, 610c, and 610d can support multiple different radio access technologies.
[0148]
In some implementations, a wireless communication system can include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that could be used to connect to different wireless networks.
[0149]
FIG. 7 is a block diagram representation of a portion of a hardware platform. A hardware platform 705 such as a network device or a base station or a wireless device (or UE) can include processor electronics 710 such as a microprocessor that implements one or more of the techniques presented in this document. The hardware platform 705 can include transceiver electronics 715 to send and/or receive wired or wireless signals over one or more communication interfaces such as antenna 720 or a wireline interface. The hardware platform 705 can implement other communication interfaces with defined protocols for transmitting and receiving data. The hardware platform 705 can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics 710 can include at least a portion of the transceiver electronics 715. In some embodiments, at least some of the disclosed techniques, modules or functions are implemented using the hardware platform 705.
[0150]
From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.
[0151]
The disclosed and other embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can 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, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
[0152]
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can 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 can 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 that store one or more modules, sub programs, or portions of code) . A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
[0153]
The processes and logic flows described in this document can 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 can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit) .
[0154]
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. 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 by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0155]
While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub combination or variation of a sub combination.
[0156]
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, 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.
[0157]
Only a few implementations and examples are described, and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.

Claims

[Claim 1]
A method for wireless communication, comprising: detecting, by a terminal, an occurrence of an event; and modifying, by the terminal, the state configuration of the serving cell based on the occurrence of the event.
[Claim 2]
The method of claim 1, wherein the event includes an expiration of a deactivation timer, and wherein the state configuration is modified to a deactivated state.
[Claim 3]
The method of claim 1, wherein the event includes an expiration of a hibernation timer, and wherein the state configuration is modified to a dormant state.
[Claim 4]
The method of claim 1, wherein the event includes receiving a message from a communication node, wherein the message includes the state configuration of the serving cell.
[Claim 5]
The method of claim 1, wherein the event includes identifying a beam failure of the serving cell.
[Claim 6]
The method of claim 1, further comprising: modifying, by the terminal, the state configuration of the serving cell from an activated state to a dormant state.
[Claim 7]
The method of claim 6, further comprising: stopping, by the terminal, a BWP inactivity timer upon modifying the state configuration of the serving cell from the activated state to the dormant state.
[Claim 8]
The method of claim 6, further comprising: modifying, by the terminal, at least one of an active downlink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and an active uplink BWP of the serving cell according to a first active uplink BWP configured for the serving cell.
[Claim 9]
The method of claim 1, further comprising: modifying, by the terminal, the state configuration of the serving cell from a deactivated state to a dormant state.
[Claim 10]
The method of claim 9, further comprising: activating, by the terminal, at least one of a downlink BWP according to a first active downlink BWP configured for the serving cell and an uplink BWP according to a first active uplink BWP configured for the serving cell.
[Claim 11]
The method of claim 9, further comprising: activating, by the terminal, a downlink BWP according to a first active downlink BWP configured for the dormant state of the serving cell, or an uplink BWP according to a first active uplink BWP configured for the dormant state of the serving cell.
[Claim 12]
The method of claim 9, further comprising: activating, by the terminal, the downlink BWP or the uplink BWP according to a default BWP for the serving cell that includes the default BWP.
[Claim 13]
The method of claim 1, further comprising: modifying, by the terminal, the state configuration of the serving cell from a dormant state to a deactivated state.
[Claim 14]
The method of claim 13, further comprising: 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.
[Claim 15]
The method of claim 1, further comprising: modifying, by the terminal, the state configuration of the serving cell from a dormant state to an activated state.
[Claim 16]
The method of claim 15, further comprising: modifying, by the terminal, at least one of an active downlink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and an active uplink BWP of the serving cell according to a first active uplink BWP configured for the serving cell.
[Claim 17]
The method of claim 15, further comprising: activating, by the terminal, at least one of a downlink BWP of the serving cell according to a first active downlink BWP configured for the serving cell and an uplink BWP of the serving cell according to a first active uplink BWP configured for the serving cell, when there is not an active BWP at the serving cell.
[Claim 18]
The method of claim 15, further comprising: starting, by the terminal, an inactivity timer associated with an active uplink BWP or an active downlink BWP.
[Claim 19]
The method of claim 15, further comprising: reporting, by the terminal, at least one of a channel quality indicator (CQI) and a channel state information (CSI) for a downlink BWP to the communication node via configured uplink resources.
[Claim 20]
The method of claim 1, further comprising: suspending, by the terminal, at least one of a configured downlink assignment, 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 the serving cell.
[Claim 21]
The method of claim 15, further comprising: initializing, 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 assignment associated with at least one of an active uplink BWP and an active downlink BWP of the serving cell.
[Claim 22]
The method of any of claims 1 and 5, further comprising: transmitting, by the terminal, a beam failure indication to the communication node indicating the beam failure of the serving cell.
[Claim 23]
The method of claim 22, wherein the beam failure indication is transmitted via one of a second serving cell with a cell group that includes the serving cell and a third serving cell that includes a cell group that does not include the serving cell.
[Claim 24]
The method of claim 22, further comprising: modifying, by the terminal, the state configuration of the serving cell from a dormant state to a deactivated state upon identifying the beam failure or based on receiving a request from the communication node to modify the state configuration of the serving cell to the deactivated state.
[Claim 25]
The method of claim 22, further comprising: initiating, by the terminal, a beam failure recovery procedure on the serving cell based on determining that the terminal is allowed to initiate the beam failure recovery procedure.
[Claim 26]
The method of claim 25, wherein the beam failure recovery procedure is initiated based on receiving a PDCCH order at the terminal, wherein the PDCCH order is transmitted via one of a second serving cell with a cell group that includes the serving cell and a third serving cell that includes a cell group that does not include the serving cell.
[Claim 27]
The method of claim 22, further comprising: modifying, by the terminal, one of the active uplink BWP or active downlink BWP of the serving cell to one of a default BWP if the default BWP is configured for the serving cell and an initial BWP if the default BWP is not configured for the serving cell.
[Claim 28]
The method of claim 22, further comprising: stopping, by the terminal, CQI and CSI reporting for the serving cell.
[Claim 29]
The method of claim 22, wherein the beam failure indication is transmitted via one of a 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 the serving cell, a serving cell identifier identifying the serving cell in the cell group, and a measurement result of the serving cell.
[Claim 30]
The method of claim 4, wherein the message from the communication node indicating configured state configuration of the serving cell 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) state information for physical downlink shared channel (PDSCH) reception, a control-resource set (CORESET) information configured for a downlink BWP, wherein the CORESET information includes candidate TCI information for PDCCH reception.
[Claim 31]
The method of claim 30, wherein the message from the communication node indicating configured state configuration of the serving cell indicates a TCI state used for PDCCH reception on a CORESET of a BWP of the serving cell.
[Claim 32]
The method of claim 30, wherein the message indicates a TCI state identifier or an index to a candidate TCI state information associated with the CORESET to indicate the TCI state used for PDCCH reception on the CORESET, and wherein the terminal utilizes the TCI state information for PDCCH reception.
[Claim 33]
The method of claim 30, wherein the message includes an indicator for each candidate TCI state information configure for the CORESET to indicate whether TCI state information is used for PDCCH reception on the CORESET, and wherein the terminal utilizes the TCI state information for PDCCH reception.
[Claim 34]
The method of claim 30, wherein the message includes an indicator for each candidate TCI state information for physical downlink shared channel (PDSCH) reception on a downlink BWP, wherein the indicator indicates whether the candidate TCI state information is activated or used for PDSCH reception.
[Claim 35]
The method of claim 30, wherein the message includes activated TCI state or TCI state information used for PDSCH reception, wherein the TCI state information includes at least one of a TCI state identifier and an index for the candidate TCI state information configured for a BWP.
[Claim 36]
An apparatus for wireless communication comprising a processor that is configured to carry out the method of any of claims 1 to 35.
[Claim 37]
A non-transitory computer readable medium having code stored thereon, the code when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 35.

Drawings

[ Fig. 1]  
[ Fig. 2]  
[ Fig. 3]  
[ Fig. 4]  
[ Fig. 5]  
[ Fig. 6]  
[ Fig. 7]