Signaling for updating tci state of coreset with dci

Abstract

Systems and methods of the present disclosure relate to a method performed by a wireless communication device. The method includes receiving, via RRC signaling, a configuration of a plurality of TCI states. The method includes receiving a MAC CE activating a subset of the plurality of TCI states. The method includes receiving a DCI indicating one or more TCI states of the subset of the plurality of TCI states to use and explicitly or implicitly indicating one or more specific CORESETs for which the one or more TCI states of the subset of the plurality of TCI states are to be used. The method includes receiving a PDCCH corresponding to the one or more specific CORESETs using one or more spatial QCL downlink reference signals contained in the one or more TCI states of the subset of the plurality of TCI states.

Description

[0001] Related Applications

[0002] This application claims the benefit of provisional patent application serial number 63 / 062,986, filed on August 7, 2020, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] Typically, this disclosure relates to signaling for updating the Transmission Configuration Indicator (TCI) status of a Control Resource Set (CORESET) with downlink control information (DCI). Background Technology

[0004] 1. New Radio (NR)

[0005] Next-generation mobile wireless communication systems (5G), or New Radio (NR), support a variety of use cases and deployment scenarios. NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the downlink (i.e., from network nodes, gNodeBs (gNBs), evolved NodeBs (eNBs), or base stations to user equipment (UEs)), and both CP-OFDM and Direct Fourier Transform (DFT) Extended OFDM (DFT-S-OFDM) in the uplink (i.e., from UE to gNB). In the time domain, NR downlink and uplink physical resources are organized into subframes of equal size, each subframe being one millisecond (1 ms). Subframes are further divided into multiple time slots of equal duration.

[0006] The length of multiple time slots depends on the subcarrier spacing. As an example, for a subcarrier spacing of Δf = 15 kHz, each subframe typically has only one time slot and each time slot always consists of 14 OFDM symbols, regardless of the subcarrier spacing.

[0007] Typically, data scheduling in NR is performed on a per-slot basis. Figure 1 An example of data scheduling based on each time slot is shown, where the first two symbols contain the Physical Downlink Control Channel (PDCCH), while the remaining 12 symbols contain the Physical Data Channel (PDCH), namely PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel).

[0008] NR supports different subcarrier spacing values. The supported subcarrier spacing values ​​(also known as different parameter sets) are determined by Δf = (15 × 2) / ( ... α The value is given as 15 kHz, where α is a non-negative integer. Δf = 15 kHz is the basic subcarrier spacing also used in Long Term Evolution (LTE). Figure 2 Examples of time slot durations under different subcarrier intervals are shown.

[0009] In the frequency domain physical resource definition, the system bandwidth is divided into resource blocks (RBs), each of which corresponds to 12 contiguous subcarriers. The common RBs (CRBs) are numbered starting from zero (0) from one end of the system bandwidth. The UE is configured with one or up to four bandwidth parts (BWPs), which can be a subset of the RBs supported on the carrier. Thus, a BWP can start from a CRB greater than zero. All configured BWPs have a common reference, which is CRB 0. Thus, a UE can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g., 100 MHz), but at a given point in time, only one BWP can be active for the UE. Physical RBs (PRBs) are numbered from 0 to N-1 within a BWP (but the 0th PRB can thus be the Kth CRB, where K > 0).

[0010] Figure 3 An example basic NR physical time-frequency resource grid is shown, in which only one RB within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

[0011] Downlink transmissions can be dynamically scheduled. For example, in each time slot, the gNB sends downlink control information (DCI) through PDCCH, which indicates the UE to which data is to be sent. In addition, the DCI indicates on which RBs in the current downlink slot the data is sent. The PDCCH is typically sent in the first one or two OFDM symbols in each slot in NR. UE data is carried on PDSCH. The UE first detects and decodes the PDCCH, and when the decoding is successful, the UE then decodes the corresponding PDSCH based on the decoded control information in the PDCCH.

[0012] Uplink data transmissions can also be dynamically scheduled using PDCCH. Similar to downlink, the UE first decodes the uplink grant in PDCCH, and then transmits data through PUSCH based on the decoded control information in the uplink grant (e.g., modulation order, coding rate, uplink resource allocation, etc.).

[0013] II. Synchronization Signal Block (SSB)

[0014] The synchronization signal block (SSB) is a broadcast signal in NR, which is intended to provide initial synchronization, basic system information, and mobility measurements. Figure 4An example structure of an SSB is shown, which includes one primary synchronization signal (PSS), one secondary synchronization signal (SSS), and one physical broadcast channel (PBCH). The PSS and SSS are transmitted over 127 subcarriers, where the subcarrier spacing can be 15 / 30 kHz for sub-6 GHz and 120 / 240 kHz for above 6 GHz.

[0015] For low frequencies, it is expected that one SSB is transmitted per cell covering the entire cell, while for higher frequencies, it is expected that several beamformed SSBs are needed to achieve coverage over the entire cell, as shown in Figure 5 The maximum number of configurable SSBs per cell depends on the carrier frequency. For example, when the carrier frequency is below 3 GHz, a maximum number of 4 configurable SSBs can be used, when the carrier frequency is between 3 and 6 GHz, a maximum number of 8 configurable SSBs can be used, and when the carrier frequency is above 6 GHz, a maximum number of 64 configurable SSBs can be used. The SSBs are transmitted in SSB transmission bursts, which can last up to 5 ms. The periodicity of the SSB burst is typically configurable (e.g., with options such as 5, 10, 20, 40, 80, 160 ms, etc.).

[0016] III. PDCCH

[0017] Messages transmitted to users over the radio link can be broadly classified as control messages or data messages. Control messages are used to facilitate correct operation of the system and correct operation of each UE within the system. Control messages can include commands for control functions, such as transmit power from a UE, signaling of RBs in which data will be received or transmitted by a UE, etc. An example of a control message in NR is the PDCCH, which, for example, carries scheduling information and power control messages. Different DCI formats can be used depending on what control data is communicated in the PDCCH. The PDCCH message in NR is demodulated using PDCCH demodulation reference signals (DMRS) that are frequency multiplexed with the DCI. Thus, the PDCCH can be understood as a self-contained transmission that enables beamforming of the PDCCH.

[0018] In NR, the PDCCH is located within one or several configurable / dynamic control regions called Control Resource Sets (CORESETs). In NR, the size of the CORESET is flexible with respect to time and frequency. In the frequency domain, a bitmap is used for allocation in units of 6 RBs, while in the time domain, a CORESET can consist of 1 to 3 consecutive OFDM symbols. The CORESET is then associated with a search space set defining when in time the UE should monitor the CORESET. The search space set includes, for example, parameters defining a periodicity, an OFDM starting symbol within a slot, a slot level offset, a DCI format to be blindly decoded, and an aggregation level for that DCI format. Thus, the CORESET and the associated search space set define when in time and frequency the UE should monitor for control channel reception. Although the OFDM PDCCH can be located in any OFDM symbol in a slot, it is expected that the PDCCH will be primarily scheduled in the first few OFDM symbols of a slot in order to enable early data decoding and low latency.

[0019] Each “PDCCH-config” can configure up to five CORESETs for a UE, and thus, the maximum number of CORESETs per serving cell is 20 (e.g., when the maximum number of BWP per serving cell is 4, the maximum number of CORESETs per serving cell is 4*5=20). Each CORESET can be configured with a transmission configuration indicator (TCI) state, which contains a downlink reference signal (DL-RS) indicated as a spatial quasi-co-location (QCL) indication that indicates to the UE a spatial direction from which the UE can assume to receive the PDCCH corresponding to the CORESET. To improve reliability (e.g., to counteract radio link failure (RLF) due to blockage), a UE can be configured with multiple CORESETs, each with a different spatial QCL assumption (e.g., transmission configuration indicator (TCI) state). In this way, in the event that one beam pair link (e.g., associated with a first spatial QCL relationship) is blocked, the network can still reach the UE by transmitting a PDCCH associated with a CORESET configured with another spatial quasi-co-location (QCL) relationship.

[0020] IV. Transmission with multiple beams

[0021] Within the high frequency range (FR2), multiple radio frequency (RF) beams can be used to transmit and receive signals at the gNB and the UE. For each DL beam from the gNB, there is typically an associated best UE Rx beam for receiving signals from the DL beam. The DL beam and the associated UE Rx beam form a beam pair. This beam pair can be identified through so-called beam management procedures in NR.

[0022] Generally, a downlink (DL) beam is identified by an associated DL reference signal (RS) that is transmitted periodically, semi-persistently or aperiodically in the beam. The DL RS for this purpose can be a synchronization signal (SS) and physical broadcast channel (PBCH) block (SSB) or a channel state information RS (CSI-RS). For each DL RS, the UE can perform a Rx beam sweep to determine the best Rx beam associated with the DL beam. The best Rx beam for each DL RS is then memorized by the UE. By measuring all DL RSs, the UE can determine and report to the gNB the best DL beam for DL transmission.

[0023] With the reciprocity principle, the same beam pair can also be used in the UL for transmitting UL signals to the gNB, which is commonly referred to as beam correspondence. Figure 6 An example is shown where the gNB consists of a transmission / reception point (TRP) with two DL beams, each associated with a CSI-RS and one SSB beam. Each DL beam is associated with a best UE Rx beam, i.e., Rx beam #1 is associated with the DL beam with CSI-RS #1, while Rx beam #2 is associated with the DL beam with CSI-RS #2.

[0024] The best DL beam for the UE can change over time due to UE movement or environmental changes, and different DL beams can be used at different times. The DL beam used for DL data transmission in PDSCH can be indicated by a TCI field in the corresponding DCI that schedules the PDSCH or activates the PDSCH in case of semi-persistent scheduling (SPS). The TCI field indicates a TCI state that contains the DL RSs associated with the DL beam. In the DCI, a physical uplink control channel (PUCCH) resource is indicated for carrying the corresponding hybrid automatic repeat request ack / nack (HARQ A / N). The UL beam used for carrying the PUCCH is determined by the PUCCH spatial relation activated for the PUCCH resource. For PUSCH transmission, the UL beam is indirectly indicated by a sounding reference signal (SRS) resource indicator (SRI) that points to one or more SRS resources associated with the PUSCH transmission. The SRS resources can be periodic, semi-persistent or aperiodic. Each SRS resource is associated with an SRS spatial relation that specifies a DL RS (or another periodic SRS). The UL beam for the PUSCH is implicitly indicated by the SRS spatial relation.

[0025] V. TCI state

[0026] A. DL TCI state

[0027] Several signals can be transmitted from different antenna ports of the same base station. These signals can have the same large-scale properties, such as Doppler shift / spread, average delay spread, or average delay. These antenna ports are then referred to as QCL.

[0028] If a UE knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the UE can estimate that parameter based on one of these antenna ports and apply that estimate to receive signals on the other antenna ports. For example, a TCI state can indicate a QCL relationship between a CSI-RS for tracking RS (TRS) and a PDSCH DMRS. When the UE receives the PDSCH DMRS, the UE can use measurements already made on the TRS to assist the DMRS reception.

[0029] Information is signaled from the network to the UE about which assumptions can be made for QCL. In NR, four types of QCL relationships between a transmitting source RS and a target RS are defined:

[0030] Type A: {Doppler shift, Doppler spread, average delay, delay spread}

[0031] Type B: {Doppler shift, Doppler spread}

[0032] Type C: {average delay, Doppler shift}

[0033] Type D: {spatial Rx parameters}.

[0034] QCL Type D was introduced to facilitate beam management by mimicking beamforming and is referred to as spatial QCL. There is currently no strict definition of spatial QCL, but it can be understood that if two transmit antenna ports are QCL in space, the UE can receive them using the same Rx beam. This is helpful for a UE that uses analog beamforming to receive signals, as the UE needs to adjust its Rx beam in a certain direction before receiving a certain signal. If the UE knows that this signal is QCL in space with some other signal that it has already received before, the UE can safely use the same Rx beam to receive this signal.

[0035] It should be noted that for beam management, the UE that utilizes the same Rx beam is typically related to QCL Type D, but it is also necessary to convey to the UE a Type A QCL relationship for an RS so that the UE can estimate all relevant large-scale parameters. Typically, this is achieved by configuring a CSI-RS for tracking (TRS) to the UE for time / frequency offset estimation. In order to be able to use any QCL reference, the UE will have to receive it with a good enough signal-to-noise ratio (SINR). In many cases, this means that the TRS has to be transmitted to the specific UE in a suitable beam.

[0036] To introduce dynamics in beam and TRP selection, a UE can be configured by radio resource control (RRC) signaling with M TCI states, where M is up to 128 in frequency range 2 (FR2) for PDSCH reception and up to 8 in FR1, depending on UE capability.

[0037] Each TCI state contains QCL information, i.e., one or two source DL RS, each source RS is associated with a QCL type. For example, a TCI state contains a pair of reference signals, each reference signal is associated with a QCL type, e.g., two different CSI-RS {CSI-RS1, CSI-RS2} are configured in a TCI state as {qcl-Type1, qcl-Type2} = {typeA, typeD}. Thus, the UE can derive Doppler shift, Doppler spread, average delay, and delay spread from CSI-RS1 and spatial Rx parameters (i.e., RX beam to use) from CSI-RS2.

[0038] Each of the M states in the list of TCI states can be interpreted as a list of M possible beams transmitted from the network or a list of M possible TRPs used by the network to communicate with the UE. The M TCI states can also be interpreted as a combination of one or more beams transmitted from one or more TRPs.

[0039] A first list of available TCI states is configured for PDSCH, while a second list of TCI states is configured for PDCCH. Each TCI state contains a pointer to the TCI state, which is referred to as a TCI state ID. The network then activates one TCI state for PDCCH (i.e., provides a TCI for PDCCH) and up to eight active TCI states for PDSCH via a medium access control (MAC) control element (MAC CE). The number of active TCI states supported by the UE is a UE capability, but the maximum number is 8.

[0040] Each configured TCI state contains parameters for QCL association between a source reference signal (CSI-RS or SS / PBCH) and a target reference signal (e.g., PDSCH / PDCCH DMRS port). The TCI state is also used to convey QCL information for receiving CSI-RS.

[0041] Assume that a UE is configured with 4 active TCI states (from a list of total 64 configured TCI states). Thus, 60 TCI states are inactive for this particular UE (but some TCI states can be active for another UE) and the UE does not need to be prepared with large scale parameter estimates for these TCI states. But the UE continuously tracks and updates the large scale parameters for the 4 active TCI states by measuring and analyzing the source RSs indicated by each TCI state. When PDSCH is scheduled to the UE, the DCI contains a pointer to one active TCI. The UE then knows which large scale parameter estimate to use when performing PDSCH DMRS channel estimation and thus PDSCH demodulation.

[0042] B. TCI state indication for UE-specific PDCCH via MAC CE

[0043] MAC CE signaling is used to indicate the TCI state for UE-specific PDCCH. As an example, Figure 7 An example structure of the MAC CE for indicating the TCI state for UE-specific PDCCH is shown. As Figure 7 The MAC CE contains the following fields as shown in

[0044] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0045] CORESET ID: This field indicates the control resource set, identified with ControlResourceSetld as specified in 3GPP TS 38.331, for which the TCI state is being indicated. In case the value of this field is 0, then this field refers to the control resource set configured by controlResourceSetZero as specified in TS 38.331 [5]. The length of this field is 4 bits.

[0046] TCI state ID: This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331 [5], applicable to the control resource set identified by the CORESET ID field. If the CORESET ID field is set to 0, this field indicates the TCI-StateId of one of the first 64 TCI states configured in tci-States-ToAddModList and tci-States-ToReleaseList in PDSCH-Config in the active BWP. If the CORESET ID field is set to a value other than 0, this field indicates the TCI-StateId configured in tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet (control resource set) identified by the indicated CORESET ID. The length of this field is 7 bits.

[0047] The MAC CE for indicating the TCI state of UE-specific PDCCH has a fixed size of 16 bits.

[0048] It should be noted that the CORESET ID identified with ControlResourceSetId is specified in 3GPP TS 38.331 as follows:

[0049] -- ControlResourceSetId

[0050] The ControlResourceSETId IE involves a short identity for identifying a control resource set within a serving cell. ControlResourceSetId = 0 identifies ControlResourceSet #0 in controlResourceSetZero (ServingCellConfigCommon) configured via PBCH (MIB). The ID space is used across BWPs of a serving cell. The number of CORESETs per BWP is limited to 3 (including common CORESET and UE-specific CORESET).

[0051] ControlResourceSetId information element

[0052] -- ASN1START

[0053] -- TAG-CONTROLRESOURCESETID-START

[0054] ControlResourceSetId ::= INTEGER

[0055] (0..maxNrofControlResourceSets-1)

[0056] --TAG-CONTROLRESOURCESETID-STOP

[0057] --ASN1STOP

[0058] In NR Rel-15, maxNrofControlResourceSET which represents the maximum number of CORESETs per serving cell is 12. In NR Rel-15, the maximum number of BWPs per serving cell is 4. These maximum values are defined in TS 38.331 in section 6.4 as follows:

[0059] Multiplicity and type constraint definitions

[0060] --ASN1START

[0061] --

[0062] TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-ST

[0063] ART ...

[0065] maxNrofBWPs INTEGER ::= 4

[0066] --Maximum number of BWPs per serving cell ...

[0068] maxNrofControlResourceSets-1 INTEGER ::= 11 -- Maximum number of CoResets configurable on a serving cell minus 1

[0069] C. TCI state activation / deactivation for UE-specific PDSCH via MAC CE

[0070] MAC CE signaling can be used to activate / deactivate TCI states for UE-specific PDSCH. As an example, Figure 8 an example structure of a MAC CE for activating / deactivating TCI states for UE-specific PDSCH is shown. As shown in Figure 8 the MAC CE contains the following fields:

[0071] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0072] BWP ID: This field contains the ID corresponding to the downlink BWP to which the MAC CE applies. The BWP ID is given by the higher layer parameter BWP-Id as specified in 3GPP TS 38.331. The length of the BWP ID field is 2 bits because a UE can be configured with up to 4 BWPs for DL.

[0073] Variable number of fields T i : If the UE is configured with a TCI state with TCI state ID i, the field T i indicates the activation / deactivation status of the TCI state with TCI state ID i. If the UE is not configured with a TCI state with TCI state ID i, the MAC entity shall ignore the T i field. The T i field is set to "1" to indicate that the TCI state with TCI state ID i shall be activated and mapped to the codepoint of the DCI Transmission Configuration Indication field as specified in 3GPP TS 38.214. The T i field is set to "0" to indicate that the TCI state with TCI state ID i shall be deactivated and not mapped to the codepoint of the DCI Transmission Configuration Indication field. It should be noted that the codepoint to which a TCI state is mapped is determined by the position of the serial number in all TCI states for which the T i field is set to "1". That is, the first TCI state for which the T i field is set to "1" shall be mapped to the codepoint value 0 of the DCI Transmission Configuration Indication field, the second TCI state for which the T i field is set to "1" shall be mapped to the codepoint value 1 of the DCI Transmission Configuration Indication field, and so on. In NR Rel. 15, the maximum number of activated TCI states is 8.

[0074] A reserved bit R: This bit is set to "0" in NR Rel. 15.

[0075] It should be noted that the TCI state activation / deactivation for UE-specific PDSCH MAC CE is identified by a MAC PDU subheader with a logical channel ID (LCID) as specified in Table 6.2.1-1 in 3GPP TS 38.321. The MAC CE for activation / deactivation of TCI states for UE-specific PDSCH has a variable size.

[0076] VI. 3-Stage Indication of TCI States for PDCCH

[0077] A 3-stage method for activating TCI states to CORESET is known (see, e.g., R1-2003483, “Preliminary Views on Further Enhancements for NR MIMO” ZTE, RAN1 #101-e, May 25 - June 5, 2020). In the first stage, RRC is used to configure a pool of TCI states. In the second stage, one or more of the RRC configured TCI states are activated via MAC-CE signaling. Finally, in the third stage, DCI signaling is used to select one of the TCI states activated via MAC-CE. SUMMARY

[0078] In some embodiments, a method is performed by a wireless communication device. The method includes receiving, via radio resource control (RRC) signaling, a configuration of a plurality of transmission configuration indicator (TCI) states. The method includes receiving a medium access control (MAC) control element (CE) that activates a subset of the plurality of TCI states. The method includes receiving downlink control information (DCI) that indicates one or more TCI states of the subset of the plurality of TCI states to use and explicitly or implicitly indicates one or more specific control resource sets (CORESETs) for which the one or more TCI states of the subset of the plurality of TCI states are to be used. The method includes receiving a physical downlink control channel (PDCCH) corresponding to the one or more specific CORESETs using one or more spatial quasi co-location (QCL) downlink reference signals contained in the one or more TCI states of the subset of the plurality of TCI states.

[0079] In some embodiments, the method further includes receiving a configuration of TCI state IDs of the plurality of TCI states, the configuration of TCI state IDs being common for two or more control resource sets (CORESETs) or per CORESET.

[0080] In some embodiments, the configuration of the plurality of TCI states and the configuration of TCI state IDs are received in a physical downlink shared channel (PDSCH) configuration information element (PDSCH-CONFIG IE).

[0081] In some embodiments, the configuration of the plurality of TCI states applies to all CORESETs configured in the same bandwidth part as the PDSCH-CONFIG IE.

[0082] In some embodiments, the MAC CE activates the subset of the plurality of TCI states for all CORESETs configured in the same bandwidth part as the configuration of the plurality of TCI states.

[0083] In some embodiments, the MAC CE includes a bandwidth part ID, a serving cell ID, and TCI state IDs of the activated subset of the plurality of TCI states, but does not include CORESET IDs.

[0084] In some embodiments, the MAC CE activates the subset of the plurality of TCI states for all CORESETs configured in the same bandwidth part as the bandwidth part indicated by the bandwidth part ID included in the MAC CE.

[0085] In some embodiments, the configuration of the TCI state IDs of the plurality of TCI states is per CORESET.

[0086] In some embodiments, the MAC CE activates up to M TCI states per CORESET.

[0087] In some embodiments, the MAC CE includes a bandwidth part ID, a serving cell ID, TCI state IDs of the activated subset of the plurality of TCI states, and CORESET IDs.

[0088] In some embodiments, the DCI implicitly indicates one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states.

[0089] In some embodiments, the one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states includes the CORESET in which the PDCCH carrying the DCI is received.

[0090] In some embodiments, the DCI explicitly indicates one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states.

[0091] In some embodiments, the DCI includes a bit field that indicates one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states.

[0092] In some embodiments, the TCI update provided by the DCI is applied to two or more serving cells or CORESETs in two or more component carriers simultaneously.

[0093] In some embodiments, the two or more serving cells or two or more component carriers to which the TCI update provided by the DCI is to be applied simultaneously are preconfigured.

[0094] In some embodiments, the two or more serving cells or two or more component carriers are indicated by a higher layer parameter.

[0095] In some embodiments, the two or more serving cells or two or more component carriers are indicated by a higher layer parameter indicating that when the TCI state of a particular CORESET is updated via DCI in one serving cell, then the TCI state of the corresponding CORESET in one or more other serving cells will also be updated simultaneously.

[0096] In some embodiments, the CORESETs in the two or more serving cells or two or more component carriers are CORESETs in the same CORESET pool as the CORESET implicitly or explicitly indicated by the DCI.

[0097] In some embodiments, a wireless communication device is presented. The wireless communication device is adapted to receive, via RRC signaling, a configuration of a plurality of TCI states. The wireless communication device is adapted to receive a MAC CE activating a subset of the plurality of TCI states. The wireless communication device is adapted to receive a DCI indicating one or more TCI states in the subset of the plurality of TCI states to be used and explicitly or implicitly indicating one or more particular CORESETs for which the one or more TCI states in the subset of the plurality of TCI states are to be used. The wireless communication device is adapted to receive a PDCCH corresponding to the one or more particular CORESETs using one or more spatial QCL downlink reference signals contained in the one or more TCI states in the subset of the plurality of TCI states.

[0098] In some embodiments, a wireless communication device is presented. The wireless communication device includes one or more receivers and processing circuitry associated with the one or more receivers. The processing circuitry is configured to cause the wireless communication device to receive, via RRC signaling, a configuration of a plurality of TCI states. The processing circuitry is configured to cause the wireless communication device to receive a MAC CE activating a subset of the plurality of TCI states. The processing circuitry is configured to cause the wireless communication device to receive a DCI indicating one or more TCI states of the subset of the plurality of TCI states to be used, and explicitly or implicitly indicating one or more specific CORESETs for which the one or more TCI states of the subset of the plurality of TCI states are to be used. The processing circuitry is configured to cause the wireless communication device to receive a PDCCH corresponding to the one or more specific CORESETs using one or more spatial QCL downlink reference signals contained in the one or more TCI states of the subset of the plurality of TCI states.

[0099] In some embodiments, a method is performed by a network node. The method includes sending, via RRC signaling, a configuration of a plurality of TCI states to a wireless communication device. The method includes sending, to the wireless communication device, a MAC CE activating a subset of the plurality of TCI states. The method includes sending, to the wireless communication device, a DCI indicating one or more TCI states of the subset of the plurality of TCI states to be used, and explicitly or implicitly indicating one or more specific control resource sets, CORESETs, for which the one or more TCI states of the subset of the plurality of TCI states are to be used.

[0100] In some embodiments, a network node is presented. The network node is adapted to send, via RRC signaling, a configuration of a plurality of TCI states to a wireless communication device. The network node is adapted to send, to the wireless communication device, a MAC CE activating a subset of the plurality of TCI states. The network node is adapted to send, to the wireless communication device, a DCI indicating one or more TCI states of the subset of the plurality of TCI states to be used, and explicitly or implicitly indicating one or more specific control resource sets, CORESETs, for which the one or more TCI states of the subset of the plurality of TCI states are to be used.

[0101] In some embodiments, a network node is presented. The network node includes processing circuitry. The processing circuitry is configured to cause the network node to transmit, to a wireless communication device via RRC signaling, a configuration of a plurality of TCI states. The processing circuitry is configured to cause the network node to transmit, to the wireless communication device, a MAC CE activating a subset of the plurality of TCI states. The processing circuitry is configured to cause the network node to transmit, to the wireless communication device, a DCI indicating one or more TCI states of the subset of the plurality of TCI states to be used, and explicitly or implicitly indicating one or more specific control resource sets, CORESETs, for which the one or more TCI states of the subset of the plurality of TCI states are to be used. BRIEF DESCRIPTION OF DRAWINGS

[0102] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0103] Figure 1 An example of per-slot basis data scheduling in New Radio (NR) is shown;

[0104] Figure 2 An example of slot duration under different subcarrier spacings is shown;

[0105] Figure 3 An example basic NR physical time-frequency resource grid is shown, with only one resource block (RB) within a 14-symbol slot shown;

[0106] Figure 4 An example structure of a synchronization signal block (SSB) is shown, including one primary synchronization signal (PSS), one secondary synchronization signal (SSS), and one physical broadcast channel (PBCH);

[0107] Figure 5 Cell coverage using a single SSB and multiple beamformed SSBs is shown;

[0108] Figure 6 An example of transmission and reception using multiple beams is shown;

[0109] Figure 7 An example structure of a medium access control (MAC) control element (CE) for indicating transmission configuration indicator (TCI) states for a user equipment (UE)-specific physical downlink control channel (PDCCH) is shown;

[0110] Figure 8 An example structure of a MAC CE for activating / deactivating TCI states for a UE-specific physical downlink shared channel (PDSCH) is shown;

[0111] Figure 9A timeline for updating a TCI state of a control resource set (CORESET) using MAC-CE signaling based on SSB beam sweeping and aperiodic SSB beam sweeping reporting is shown;

[0112] Figure 10 One example of a cellular communications system in which embodiments of the disclosure can be implemented in accordance with some embodiments of the disclosure is shown;

[0113] Figure 11 A wireless communication system is shown represented as a Fifth Generation (5G) network architecture composed of core network functions (NFs), wherein the interaction between any two NFs is represented by a point-to-point reference point / interface in accordance with some embodiments of the disclosure;

[0114] Figure 12 A 5G network architecture in accordance with some embodiments of the disclosure is shown using service-based interfaces between NFs in the control plane (CP) instead ofpoint-to-point reference points / interfaces used in the 5G network architecture of Figure 11

[0115] Figure 13 is a flowchart of a first option of a method for configuration and activation of a TCI state for a CORESET in accordance with some embodiments of the disclosure;

[0116] Figure 14 is a flowchart of a second option of a method for configuration and activation of a TCI state for a CORESET in accordance with some embodiments of the disclosure;

[0117] Figure 15 is a flowchart of a method for implicit update of a CORESET TCI in accordance with some embodiments of the disclosure;

[0118] Figure 16 is a flowchart of a method for explicit update of a CORESET TCI in accordance with some embodiments of the disclosure;

[0119] Figure 17 is a schematic block diagram of a radio access node 1700 in accordance with some embodiments of the disclosure;

[0120] Figure 18 is a schematic block diagram illustrating a virtualized embodiment of a radio access node in accordance with some embodiments of the disclosure;

[0121] Figure 19 is a schematic block diagram of a radio access node 1700 in accordance with some other embodiments of the disclosure;

[0122] Figure 20 is a schematic block diagram of a wireless communication device in accordance with some embodiments of the disclosure;

[0123] Figure 21 is a schematic block diagram of a wireless communication device according to some other embodiments of the disclosure;

[0124] Figure 22 is a flowchart of a method performed by a wireless communication device according to some embodiments of the disclosure; and

[0125] Figure 23 is a flowchart of a method performed by a base station according to some embodiments of the disclosure. DETAILED DESCRIPTION

[0126] The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the embodiments and illustrate the best modes of practicing the embodiments. Upon reading the following description, one skilled in the art will understand how to implement the concepts to arrive at some embodiments of the disclosure and will recognize that the concepts can be practiced with various modifications that are apparent to one skilled in the art. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0127] Radio node: As used herein, a “radio node” is a radio access node or a wireless communication device.

[0128] Radio access node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high- power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB central unit (gNB-CU) or a network node that implements a gNB distributed unit (gNB-DU)), or a network node that implements a gNB distributed unit (gNB-DU), or a network node that implements part of the functionality of some other type of radio access node.

[0129] Core network node: As used herein, a “core network node” is any type of node in a core network or any node implementing core network functionality. Some examples of core network nodes include, e.g., a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include implementing an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), an authentication server function (AUSF), a network slice selection function (NSSF), a network exposure function (NEF), a network function (NF) repository function (NRF), a policy control function (PCF), a unified data management (UDM), etc.

[0130] Communication device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of communication devices include, but are not limited to: a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a household appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device (such as, but not limited to, a television, a radio, a lighting installation, a tablet computer, a laptop or personal computer (PC). A communication device can be a portable, hand-held, computer- including, or car-mounted mobile device that communicates voice and / or data via a radio

[0131] Wireless communication device: One type of communication device is a wireless communication device, which can be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to: a user equipment (UE) in a 3GPP network, a machine-type communication (MTC) device, and an Internet of Things (IoT) device. Such a wireless communication device can be or can integrate with a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a household appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device (such as, but not limited to, a television, a radio, a lighting installation, a tablet computer, a laptop or a PC). A communication device can be a portable, hand-held, computer-including, or car-mounted mobile device that communicates voice and / or data via a radio

[0132] Network node: As used herein, a “network node” is any node that is part of a RAN or a core network of a cellular communications network / system.

[0133] Note that the description given herein focuses on 3GPP cellular communications systems, and thus often uses 3GPP terminology or terminology similar to 3GPP terminology. However, the concepts disclosed herein are not limited to 3GPP systems.

[0134] Note that in the description herein, reference can be made to the term "cell", however, especially with respect to the 5G NR concept, beams can be used instead of cells, and thus it is important to note that the concepts described herein equally apply to both cells and beams.

[0135] There are certain challenges currently. In Rel-15 / 16 NR, a medium access control (MAC) control element (CE) message can be used to update the transmission configuration indicator (TCI) state of a given control resource set (CORESET) by indicating one of the 64 first TCI states configured by tci-States-ToAddModList and tci-States-ToReleaseList in PDSCH-Config (see 3GPP TS 38.331) in the active bandwidth part (BWP). Although faster than radio resource control (RRC) signaling, the MAC-CE based TCI state update is still associated with a significant delay.

[0136] Figure 9 A timeline for updating the TCI state of a CORESET using MAC-CE signaling based on synchronization signal block (SSB) beam sweeping and aperiodic SSB beam sweeping reporting is shown. As shown, the delay is mainly dominated by the MAC CE application delay and the delay for the UE to reacquire the quasi co-located (QCL) properties of the reference signal (RS) in the activated TCI state.

[0137] One possible approach to accelerate the TCI state update of a CORESET is to introduce a downlink control information (DCI) based TCI state update framework in a similar way as the TCI state update of the physical downlink shared channel (PDSCH) in Rel-15. By using DCI to indicate one of the M activated TCI states, the delay associated with the MAC-CE based TCI state update can be significantly reduced, as there is no need for the RAN4 requirement (in clause 8.10.3 of 3GPP TS 38.133) for waiting for a new transmission of the RS in the selected TCI state when DCI is used to select one of the M activated TCI states.

[0138] However, since there can be several CORESETs configured for a specific UE for a given BWP, the existing solution does not address the question of how the UE will know which CORESET the DCI-based TCI state update should be applied to. Therefore, this is an open issue. Although Rl-2003483 discusses a general three-stage (i.e., RRC + MAC CE + DCI) framework for indicating the TCI state of PDCCH, it does not provide the configuration / signaling details of the RRC + MAC CE + DCI framework. Therefore, the configuration / signaling details of the RRC + MAC CE + DCI framework are also an open issue to be addressed.

[0139] Particular aspects of the present disclosure and embodiments thereof can provide solutions to the above-described or other challenges. The solutions in the present disclosure propose a framework for indicating which CORESET the TCI state update is for when the TCI state is updated with DCI. The framework also provides configuration / signaling details for the three-stage indication (i.e., RRC + MAC CE + DCI) of the TCI state of CORESET. The solutions in the present disclosure propose a framework for indicating which CORESET the TCI state update is for when the TCI state is updated with DCI.

[0140] Figure 10One example of a cellular communications system 1000 in which embodiments of the present disclosure can be implemented is shown. In the embodiments described herein, the cellular communications system 1000 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC), or an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC). In this example, the RAN includes base stations 1002-1 and 1002-2, which in the 5GS include NR base stations (gNBs) and optionally, a Next Generation eNB (ng-eNB) (e.g., an LTE RAN node connected to a 5GC), which in the EPS include eNBs, controlling corresponding (macro) cells 1004-1 and 1004-2. The base stations 1002-1 and 1002-2 are generally referred to herein collectively as base stations 1002, and individually as base station 1002. Likewise, the (macro) cells 1004-1 and 1004-2 are generally referred to herein collectively as (macro) cells 1004, and individually as (macro) cell 1004. The RAN can also include a plurality of low-power nodes 1006-1 through 1006-4 controlling corresponding small cells 1008-1 through 1008-4. The low-power nodes 1006-1 through 1006-4 can be small base stations (such as pico or femto base stations) or a Remote Radio Head (RRH), among others. Notably, while not shown, one or more of the small cells 1008-1 through 1008-4 can alternatively be provided by the base stations 1002. The low-power nodes 1006-1 through 1006-4 are generally referred to herein collectively as low-power nodes 1006, and individually as low-power node 1006. Likewise, the small cells 1008-1 through 1008-4 are generally referred to herein collectively as small cells 1008, and individually as small cell 1008. The cellular communications system 1000 also includes a core network 1010, which in the 5G system (5GS) is referred to as a 5GC. The base stations 1002 (and optionally the low-power nodes 1006) are connected to the core network 1010.

[0141] The base stations 1002 and the low-power nodes 1006 serve corresponding cells 1004 and 1008 with wireless communication devices 1012-1 through 1012-5. The wireless communication devices 1012-1 through 1012-5 are generally referred to herein collectively as wireless communication devices 1012, and individually as wireless communication device 1012. In the following description, the wireless communication devices 1012 are typically UEs, and are therefore sometimes referred to herein as UEs 1012, but the present disclosure is not limited to this.

[0142] Figure 11 A wireless communication system is shown represented as a 5G network architecture composed of core network functions (NFs), where the interaction between any two NFs is represented by a point-to-point reference point / interface.Figure 11 may be considered Figure 10 a particular implementation of the system 1000.

[0143] From an access side, Figure 11 The 5G network architecture shown in FIG. 10 includes a plurality of UEs 1012 connected to a RAN 1002 or access network (AN) and an AMF 1100. Generally, the R(AN) 1002 includes a base station, e.g., a base station such as an eNB or gNB. From a core network side, Figure 11 The 5GC NFs shown in FIG. 11 include an NSSF 1102, an AUSF 1104, a UDM 1106, an AMF 1100, an SMF 1108, a PCF 1110, and an application function (AF) 1112.

[0144] In the specification standardization, the reference points of the 5G network architecture represent for forming detailed call flows. The N1 reference point is defined as carrying signaling between the UE 1012 and the AMF 1100. The reference points for the connection between the AN 1002 and the AMF 1100 and between the AN 1002 and the UPF 1114 are defined as N2 and N3, respectively. There is a reference point N11 between the AMF 1100 and the SMF 1108, which means that the SMF 1108 is at least partially controlled by the AMF 1100. N4 is used by the SMF 1108 and the UPF 1114 so that the UPF 1114 can be set using the control signal generated by the SMF 1108, and the UPF 1114 can report its state to the SMF 1108. Respectively, N9 is the reference point for the connection between different UPFs 1114, and N14 is the reference point for the connection between different AMFs 1100. N15 and N7 are defined because the PCF 1110 applies policies to the AMF 1100 and the SMF 1108, respectively. The AMF 1100 needs N12 to perform authentication of the UE 1012. N8 and N10 are defined because the AMF 1100 and the SMF 1108 need the subscription data of the UE 1012.

[0145] The 5GC network aims to separate the UP and CP. In the network, the UP carries user traffic, while the CP carries signaling. In Figure 11In this case, the UPF 1114 is in the UP, and all other NFs, i.e., the AMF 1100, the SMF 1108, the PCF 1110, the AF 1112, the NSSF 1102, the AUSF 1104, and the UDM 1106 are in the CP. Separating the UP and the CP ensures that each plane resource can be scaled independently. It also allows the UPF to be deployed in a distributed manner separate from the CP functions. In this architecture, the UPF can be deployed very close to the UE to shorten the round-trip time (RTT) between the UE and the data network for some applications that require low latency.

[0146] The core 5G network architecture is composed of modularized functions. For example, the AMF 1100 and the SMF 1108 are independent functions in the CP. The separated AMF 1100 and the SMF 1108 allow independent evolution and scaling. Other CP functions, such as the PCF 1110 and the AUSF 1104, can be separated as shown in Figure 11 . The modularized function design enables the 5GC network to flexibly support various services.

[0147] Each NF interacts directly with another NF. Messages can be routed from one NF to another NF using intermediate functions. In the CP, a set of interactions between two NFs is defined as a service so that it can be reused. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

[0148] Figure 12 The 5G network architecture is shown, which uses service-based interfaces between NFs in the CP instead of the point-to-point reference points / interfaces used in the Figure 11 5G network architecture described above with reference to Figure 11 . The NFs described above with reference to Figure 12 correspond to the NFs shown in Figure 12 . The services provided by an NF to other authorized NFs can be exposed to the authorized NFs through the service-based interfaces. In Figure 12 , the service-based interfaces are denoted by the letter “N” followed by the name of the NF, e.g., the service-based interface Namf for the AMF 1100, the service-based interface Nsmf for the SMF 1108, and so on. Figure 11 The NEF 1200 and the NRF 1202 in Figure 11 are not shown in the Figure 11 discussed above. However, it should be clarified that, although not explicitly indicated in Figure 12 , all the NFs depicted in may interact with the NEF 1200 and the NRF 1202 in

[0149] as needed. Figure 11 Figure 12Some of the properties of the NFs shown in the middle. The AMF 1100 provides UE-based authentication, authorization, mobility management, etc. A UE 1012, even using multiple access technologies, is basically connected to a single AMF 1100 because the AMF 1100 is independent of the access technology. The SMF 1108 is responsible for session management and allocates an Internet Protocol (IP) address to the UE. It also selects and controls the UPF 1114 for data transfer. If the UE 1012 has multiple sessions, different SMFs 1108 can be assigned to each session to manage them individually and possibly provide different functions for each session. The AF 1112 provides information on packet flow to the PCF 1110 responsible for policy control to support Quality of Service (QoS). Based on this information, the PCF 1110 determines policies regarding mobility and session management to enable the AMF 1100 and the SMF 1108 to function normally. The AUSF 1104 supports authentication functions for UEs and the like, so it stores data for authenticating UEs and the like, while the UDM 1106 stores subscription data for the UE 1012. A Data Network (DN) that is not part of the 5GC network provides Internet access or operator services, etc.

[0150] The NFs can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0151] When the TCI state of a CORESET is updated using DCI, it is expected that M TCI states are activated via MAC CE (in a similar way that 8 TCI states can be activated for PDSCH in Rel-15), and different codepoints in a new bitfield in the DCI are used to select one of the activated TCI states.

[0152] I. Configuration and activation of TCI states for CORESET

[0153] In some embodiments, TCI states can be configured and activated for a CORESET. Multiple embodiments are provided for the configuration / signaling for this 3-stage (RRC + MAC CE + DCI) framework.

[0154] A. Option 1

[0155] At a high level, this option is in Figure 13is represented as procedure 1300. Initially, a list of TCI states is RRC configured in the PDSCH-CONFIG information element (IE) (step 1302). A list of TCI state IDs is configured in the PDSCH-CONFIG IE (step 1304). A MAC CE activates up to M TCI states for PDCCH (step 1306), and a DCI indicates which of the activated TCI states to use for a CORESET (step 1308).

[0156] More specifically, in this option, at step 1302, a list of TCI states is RRC configured in the “PDSCH-Config” IE, and at step 1304, a corresponding list of TCI state identifiers (i.e., TCI state IDs) is also configured in the “PDSCH-Config” IE. It should be noted that this option is different from how TCI state identifiers are traditionally configured for PDCCH in NR, because this option does not require TCI state identifiers to be configured for each CORESET (or ControlResourceSet). In addition, it should be noted that in NR Release 15 / 16, a list of TCI state IDs is configured for each CORESET. The list of TCI state IDs configured in each CORESET points to a subset of TCI state IDs configured in PDSCH-config.

[0157] In one variant of this option, the list of TCI state IDs is directly configured in PDCCH-Config at step 1304, and this list of TCI state IDs applies to all CORESETs in the BWP where PDCCH-Config is configured. In some embodiments, this list of TCI state IDs can point to a subset of TCI states or TCI state IDs configured in PDSCH-config included in the same BWP-DownlinkDedicated where PDCCH-Config is configured.

[0158] In another variant of this option, the list of TCI states or the list of TCI state IDs configured in PDSCH-Config in the same BWP in which the CORESET is configured is re-used to apply to all CORESETs in the BWP. This can be specified in different ways. One way is to configure the same set of TCI states in PDCCH-Config as in PDSCH-Config. Another way is to specify in the field description of IE ControlResourceSet that without the list of TCI state IDs, the same set of TCI states as in PDSCH-Config configured in the same BWP-DownlinkDedicated is assumed. Yet another way is to configure, e.g., in PDCCH-Config, one parameter that informs the UE to use the same set of TCI states as configured in PDSCH-Config belonging to the same BWP-DownlinkDedicated. Yet another way is to specify in RAN1 specification, e.g., based on UE capability, the assumed set of TCI states by the UE.

[0159] At step 1306, in the second stage, the MAC CE activates up to M TCI states configured in the first stage. The MAC CE indicates up to M TCI state identities (corresponding to the M TCI states to be activated) from the list of TCI states configured in the first stage. Note that the M activated TCI states here are common for all CORESETs configured in the same BWP (Bandwidth Part) as “PDSCH-Config”. That is, assuming CORESET#1 and CORESET#2 are configured in the same BWP as “PDSCH_Config”, the following are possible:

[0160] - Any of the M activated TCI states can be indicated via DCI to CORESET#1 in stage 3.

[0161] - Any of the M activated TCI states can be indicated via DCI to CORESET#2 in stage 3.

[0162] Hence, in the alternative of stage 2, at step 1306, when the MAC CE activates M TCI states for PDCCH, the MAC CE needs to provide the BWP ID, the serving cell ID, and the identifiers of the TCI states to be activated for PDCCH. In this option, there is no need to provide the CORESET ID in the MAC CE. This is different from the Rel-15 MAC CE (PDSCH-TCI-State) that activates the TCI states of a CORESET. Figure 7CORESET ID is provided in the Rel-15 MAC CE) is different.

[0163] Another alternative for phase 2 is to reuse the Rel-15 PDSCH MAC CE shown in Figure 8 to indicate the activated TCI states for CORESETs. Note that the CORESET ID is not provided in the MAC CE in Figure 8 Figure 8 The TCI states activated via the MAC CE in Figure 8 apply to all CORESETs in the same BWP as the BWP ID indicated in the MAC CE in Figure 8 In some embodiments, the UE is configured by higher layers such that the UE uses the same activated TCI state set provided by the MAC CE in

[0164] In another alternative, the MAC CE from Rel-15 for CORESET is reused, but the fields are configured to be interpreted in another way. The UE ignores the CORESET ID field and interprets the TCI state ID field as a bitmap that can activate M > 1 TCI states in a list of TCI states. In a variant, the CORESET ID field and the TCI state field together are used to indicate to the UE the activated TCI states. As a generalization, the MAC CE is defined with an LCID that maps the MAC CE to one purpose, e.g., updating TCI states for PDCCH. Part of the fields are fixed as today, e.g., serving cell ID and bandwidth part ID. Part of the fields are RRC configurable maximum size. For example, the CORESET ID field can be present or not, and the TCI state ID field is configurable. The configurability of the MAC CE fields can be generalized to any MAC CE.

[0165] In phase 3, at step 1308, any of the M TCI states activated in phase 2 can be indicated to a CORESET via DCI. Which CORESET the TCI state indicated in the DCI applies to is determined via the embodiments described in section II and section III below.

[0166] ​Note that the list of TCI states and the list of corresponding TCI state identifiers in the first stage can also be configured elsewhere than in “PDSCH-Config”. For example, these lists can be configured in BWP level in one of the following IEs in 3GPP TS 38.331: BWP-Downlink or BWP-DownlinkDedicated, or PDCCH-Config.

[0167] Note that in this option, up to M TCI states can be activated for each BWP’s PDCCH (i.e., the CORESET carrying PDCCH) only. The maximum number of TCI states that can be activated for each BWP’s PDCCH can be reported by the UE as part of the UE capability, and the gNB can configure an explicit parameter to the UE to indicate the maximum number of TCI states that can be activated for PDCCH.

[0168] B. Option 2

[0169] At a high level, this option is represented as procedure 1400 in the flowchart of Figure 14 Initially, a list of TCI states is RRC configured in PDSCH-CONFIG IE (step 1402). A subset of TCI state IDs of this list is configured for each CORESET (step 1404). A MAC CE activates up to M TCI states for PDCCH (step 1406), and a DCI indicates for a CORESET which one of the activated TCI states to use (step 1408).

[0170] More specifically, in this option, in the first stage, at step 1402, a list of TCI states is RRC configured in the “PDSCH-Config” IE. At step 1404, then, a TCI state identifier corresponding to a subset of the TCI states configured in “PDSCH-Config” is configured for each CORESET (i.e., in ControlResourceSet).

[0171] In the second stage, at step 1406, a MAC CE activates up to M TCI states for each CORESET from the subset of TCI state identifiers configured in the first stage. Note that there can be up to M activated TCI states for each CORESET. Thus, the total number of activated TCI states for all CORESETs configured in the same BWP can be up to N*M, where N is the number of CORESETs configured in the BWP.

[0172] Therefore, in this option, when the MAC CE activates M TCI states for each CORESET's PDCCH, the MAC CE needs to provide the BWP ID, serving cell ID, CORESET ID, and an identifier for the TCI state to be activated for the PDCCH. This differs from version 15 MAC CE, which activates only one TCI state per CORESET in this case. Instead, in this option, it is done via a different MAC CE than version 15 (i.e., Figure 7 The new MAC CE (MAC CE in the CORESET) can activate up to M TCI states of PDCCH for each CORESET.

[0173] Another alternative to introducing a new MAC CE is to reuse... Figure 7 In version 15 of MAC CE, the TCI field is interpreted differently. In this alternative, each bit in the 7-bit TCI ID field is interpreted as a different TCI state. Therefore, up to 7 TCI states can be configured for each CORESET, and up to M = 7 TCI states can be activated in this alternative. The first bit in the TCI field of MAC CE version 15 is interpreted as an activation / deactivation indicator bit for the first TCI state of the CORESET (i.e., the CORESET corresponding to the CORESET ID provided in MAC CE) configured to provide a TCI state activation command for it. Similarly, the second bit in the TCI field of MAC CE version 15 is interpreted as an activation / deactivation indicator bit for the second TCI state of the CORESET (i.e., the CORESET corresponding to the CORESET ID provided in MAC CE) configured to provide a TCI state activation command for it, and so on.

[0174] In step 1408, in stage 3, any one of the M TCI states activated in stage 2 can be indicated to the CORESET via the DCI. Which CORESET the TCI state indicated in the DCI applies to is determined via embodiments 2 and 3 described below.

[0175] Note that the TCI status list in Phase 1 can also be configured elsewhere instead of in PDSCH-Config. For example, these lists can be configured at the BWP level in one of the following IEs in 3GPP TS 38.331: BWP-Downlink or BWP-DownlinkDedicated, or PDCCH-Config.

[0176] It should be noted that in this option, up to N*M TCI states can be activated per PDCCH (i.e. the CORESET carrying the PDCCH). The maximum total number of TCI states that can be activated per PDCCH (across all CORESETs) can be reported by the UE as part of the UE capability and the gNB can configure an explicit parameter to the UE to indicate the maximum total number of TCI states that can be activated per BWP.

[0177] II. Implicit update of CORESET TCI

[0178] In this embodiment, where the CORESET receiving the PDCCH carrying the DCI containing the TCI state update is also the CORESET for which the TCI state is updated. For example, assume that the UE is configured with two CORESETs; CORESET#1 and CORESET#2. Further assume that: CORESET#1 has one currently used TCI state called TCI state #1 and CORESET#2 has one currently used TCI state called TCI state #4. If we want to update the TCI state of CORESET#1, we can send the DCI carrying the codepoint for TCI state update in the PDCCH received in CORESET#1. Then, the UE will know that the TCI state update indicated in the DCI in the received PDCCH should be applied to CORESET#1.

[0179] More generally, this can be seen in the procedure 1500 shown in Figure 15 where the DCI containing the TCI state update in the PDDCH is sent to the UE (step 1502). The DCI is received in a CORESET (step 1504), and the TCI state in the CORESET receiving the DCI is updated (step 1506).

[0180] III. Explicit update of CORESET TCI

[0181] In this embodiment, a new bitfield is included in the DCI indicating the TCI state update pointing to one of the configured CORESETs. The size of the new bitfield can depend on the number of CORESETs configured per BWP for this UE. For example, if the UE is configured with two CORESETs, the bitfield can consist of a single bit, where the codepoint “0” will point to the CORESET with the lowest ID and the codepoint “1” will point to the CORESET with the highest ID.

[0182] In case only a single CORESET is defined, then no bit field is needed and the UE updates the TCI state of the single CORESET.

[0183] As mentioned before, one potential issue with implicit updating of CORESET TCI is that in case the beam pair link associated with a particular CORESET has become blocked, we can not be able to reach the UE using that CORESET with DCI, thus prohibiting the TCI state update of that CORESET. With explicit updating of CORESET TCI, the TCI state of the blocked CORESET can be updated using the DCI received in the second CORESET. However, the additional flexibility provided by implicit updating of CORESET TCI comes with the additional DCI overhead cost due to the additional bit field.

[0184] If DCI format 1 0 is used to carry the TCI update information, a new Radio Network Temporary Identifier (RNTI) can be introduced so that the UE applies the same DCI length 1 0 when decoding the PDCCH but uses the new RNTI to descramble the Cyclic Redundancy Check (CRC) in order to distinguish the interpretation of the fields from other RNTIs. An acknowledgement (ACK) from the UE is expected to receive and successfully decode the DCI.

[0185] If PDSCH data is indicated in this DCI, the ACK for PDSCH can be anchored when the UE starts applying the TCI switch of the CORESET. The anchoring of the TCI switch time can also be the time / slot / symbol when the PDCCH sending the TCI update information is received, the ACK can be sent via PUCCH or a MAC CE via PUSCH.

[0186] The new RNTI can be assumed to be called TCI-RNTI. When the TCI-RNTI for a UE is configured by higher layers, the following information can be sent by the DCI format 1 0 scrambled with the TCI-RNTI:

[0187] - TCI field

[0188] - CORESET ID field

[0189] - SRI field

[0190] - UL channel indication field

[0191] - Time to apply the beam switch

[0192] - Time to send ACK via PUCCH

[0193] Thus, when the CRC of DCI format 1_0 is scrambled by TCI-RNTI, then both the TCI field and the CORESET ID field can be present in the DCI. These fields can be used to indicate the TCI state to be updated (provided via the TCI field in the DCI) and the CORESET to which the TCI state update applies (provided via the CORESET ID field in the DCI). Although this embodiment is written in terms of DCI format 1_0, it can be generalized to other DCI formats as well (e.g., DCI format 0_0, etc.).

[0194] IV. Simultaneous updating of TCI states of CORESETs in multiple serving cells via DCI

[0195] In this embodiment, the DCI containing the TCI state update is applied to the CORESETs in multiple serving cells (or component carriers, CCs) simultaneously. In one embodiment, the UE is preconfigured with a list of serving cells for simultaneous updating of the TCI states of the CORESETs. Now, consider the case when the UE receives a DCI containing a TCI state update for a CORESET, where the CORESET to which the TCI update in the DCI applies can be determined according to the embodiments described in part II or III in the specific embodiments above. If the serving cell of the CORESET for which the TCI state update is performed belongs to the list of serving cells, then the TCI state update indicated by this DCI is also applied to the corresponding CORESETs in all serving cells in the list of serving cells. Note that this can re-use one of the existing lists of serving cells in the IE CellGroupConfig, e.g., simultaneousTCI-UpdateListl, simultaneousTCI-UpdateList2 (as defined in 3GPP TS 38.331), or a new list can be defined.

[0196] In an alternative embodiment, the gNB can configure the UE with a higher layer parameter (e.g., an RRC parameter) such that when the TCI state of a CORESET is updated via DCI in one serving cell, then the TCI state of the corresponding CORESETs in all serving cells configured for the UE in the sCellToAddModList in the IE CellGroupConfig (as defined in 3GPP TS 38.331) are also updated simultaneously.

[0197] In yet another alternative embodiment, the CORESETs are grouped into multiple pools and each CORESET is configured with a CORESET pool index. The CORESET pool index can be configured across serving cells. In this alternative embodiment, when the TCI state of a CORESET corresponding to one CORESET pool is updated via DCI, then the TCI states of other CORESETs with the same CORESET pool index are also updated simultaneously.

[0198] Simultaneous updating of the TCI states of CORESETs in multiple serving cells is beneficial as it can significantly reduce the TCI state activation delay in multiple serving cells. For example, updating the TCI states for each serving cell can consume large delays in addition to controlling the signaling overhead for performing these TCI state updates on a per-cell basis. However, simultaneous updating of the TCI states of CORESETs across multiple serving cells can significantly reduce these delays while reducing the control signaling overhead. The above embodiments are also applicable to PDCCH-Config or BWP level. That is, the UE can be updated with the TCI states of all CORESETs as described in embodiment 1. Then, in a similar manner, the sCellToAddModList, simultaneousTCI-UpdateList 1, simultaneousTCI-UpdateList2 (as defined in 3GPP TS 38.331), or a new list, all cells, and any of the BWP in all cells are updated if this PDCCH-Config belongs to a BWP that belongs to a serving cell listed in the list of RRC configured. In another embodiment, if the list of serving cells in simultaneousTCI-UpdateList 1 or simultaneousTCI-UpdateList 2 (as defined in 3GPP TS 38.331) or a new list for this purpose consists of only one serving cell, and the UE receives a MAC CE or DCI to update the TCI state related to PDCCH, then the UE applies the update for all BWP in this serving cell.

[0199] In another embodiment, TCI state update is performed across BWP even if the list of cells is not configured in a particular cell. That is, the UE is only configured with sCellToAddModList in IE CellGroupConfig and the list only has one cell, i.e., the UE is only configured with PSCell. In order to be able to update TCI state across BWP of PCell, the UE is configured with a new RRC parameter to indicate the UE that this operation. In addition, although the disclosure is for PDCCH, this embodiment can also be applied to PDSCH, PUCCH and PUSCH. For all these channels, the RRC parameter can be separate or there is one parameter with different values specific to different DL / UL channels.

[0200] More generally, this embodiment is shown as process 1600 in Figure 16 Process 1600 begins with grouping elements (e.g., multiple cells or CORESETs) (step 1602). DCI containing TCI update is transmitted (step 1604). Upon receiving the DCI, all elements of the group are updated (step 1606).

[0201] V. Other Notes

[0202] Figure 17is a schematic block diagram illustrating a radio access node 1700 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 1700 can be, for example, a base station 1002 or 1006 or a network node implementing all or part of the functionality of a base station 1002 or gNB described herein. As illustrated, the radio access node 1700 includes a control system 1702 that includes one or more processors 1704 (for example, central processing units (CPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and / or the like), memory 1706, and a network interface 1708. The one or more processors 1704 are also referred to herein as processing circuitry. In addition, the radio access node 1700 can include one or more radio units 1710 that each include one or more transmitters 1712 and one or more receivers 1714 coupled with one or more antennas 1716. The radio units 1710 can be referred to or be part of radio interface circuitry. In some embodiments, the radio units 1710 are external from the control system 1702 and connected to the control system 1702 via, for example, a wired connection (for example, an optical cable). However, in some other embodiments, the radio units 1710 and possibly the antennas 1716 are integrated with the control system 1702. The one or more processors 1704 are used to provide one or more functions of the radio access node 1700 as described herein. In some embodiments, the functions are implemented in software that is stored, for example, in the memory 1706 and executed by the one or more processors 1704.

[0203] Figure 18 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1700 according to some embodiments of the present disclosure. The discussion applies equally to other types of network nodes. In addition, other types of network nodes can have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0204] As used herein, a “virtualized” radio access node is an implementation of the radio access node 1700 in which at least a portion of the functionality of the radio access node 1700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network). As illustrated, in this example, the radio access node 1700 can include a control system 1702 and / or one or more radio units 1710, as described above. The control system 1702 can be connected to the radio unit(s) 1710 via, for example, an optical cable or the like. The radio access node 1700 includes one or more processing nodes 1800 coupled to or included as part of a network 1802. If present, the control system 1702 or the radio unit(s) are connected to the processing node(s) 1800 via the network 1802. Each processing node 1800 includes one or more processors 1804 (e.g., CPUs, ASICs, FPGAs, or the like), memory 1806, and a network interface 1808.

[0205] In this example, the functionality 1810 of the radio access node 1700 described herein is implemented at the processing node(s) 1800 or distributed across the processing node(s) 1800 and the control system 1702 and / or the radio unit(s) 1710 in any desired manner. In some particular embodiments, some or all of the functionality 1810 of the radio access node 1700 described herein is implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1800. As will be appreciated, in order to perform at least some of the desired functionality 1810, additional signaling or communication between the processing node(s) 1800 and the control system 1702 is used. Especially, in some embodiments, the control system 1702 can not be included, in which case the radio unit(s) 1710 communicate directly with the processing node(s) 1800 via an appropriate network interface.

[0206] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality 1810 of a radio access node 1700 or a node (e.g., a processing node 1800) implementing one or more functions of the functionality 1810 of a radio access node 1700 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0207] Figure 19is a schematic block diagram of a radio access node 1700 according to some other embodiments of the present disclosure. The radio access node 1700 includes one or more modules 1900, each of which is implemented in software. The one or more modules 1900 provide the functionality of the radio access node 1700 described herein. This discussion is equally applicable to the processing node 1800 Figure 18 where the modules 1900 can be implemented at one of the processing nodes 1800 or distributed across multiple processing nodes 1800 and / or distributed across the processing nodes 1800 and the control system 1702.

[0208] Figure 20 is a schematic block diagram of a wireless communication device 2000 according to some embodiments of the present disclosure. As shown, the wireless communication device 2000 includes one or more processors 2002 (e.g., CPUs, ASICs, FPGAs, etc.), memory 2004, and one or more transceivers 2006, each including one or more transmitters 2008 and one or more receivers 2010 coupled to one or more antennas 2012. The transceiver 2006 includes radio-front end circuitry connected to the antenna 2012 that is configured to condition signals communicated between the antenna 2012 and the processor 2002, as will be appreciated by those skilled in the art. The processors 2002 are also referred to herein as processing circuitry. The transceiver 2006 is also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 2000 described above can be fully or partially implemented in software that is, for example, stored in the memory 2004 and executed by the processor 2002. Note that the wireless communication device 2000 can include additional components not Figure 20 indicated in FIG. 2, such as one or more user interface components (e.g., input / output interfaces including displays, buttons, touchscreens, microphones, speakers, etc., and / or any other components that allow input of information into and / or output of information from the wireless communication device 2000), power supplies (e.g., batteries and associated power circuitry), etc.

[0209] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of a wireless communication device 2000 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the computer program

[0210] Figure 21This is a schematic block diagram of a wireless communication device 2000 according to some other embodiments of the present disclosure. The wireless communication device 2000 includes one or more modules 2100, each module being implemented in software. Modules 2100 provide the functionality of the wireless communication device 2000 described herein.

[0211] Figure 22 This is a flowchart of a method performed by the wireless communication device 1012. It should be noted that... Figure 22 The steps described herein can be performed by a wireless device, a wireless communication device (e.g., WCD1012, etc.), a virtualized wireless device, etc., or otherwise operated by a wireless device, a wireless communication device (e.g., WCD1012, etc.), a virtualized wireless device, etc. Note that, according to some embodiments, the steps can be performed... Figure 22 One or more steps are specified, while other steps are optional. Such steps are indicated by dashed boxes.

[0212] At step 2202, the wireless communication device receives the configuration of multiple TCI states via RRC signaling (e.g., regarding...). Figure 13 Step 1302 Figure 14 (as described in 1402, etc.).

[0213] At step 2204, the wireless communication device receives a MAC CE that activates a subset of multiple TCI states (e.g., as per [reference]). Figure 13 Step 1306 Figure 14 (as described in 1406, etc.).

[0214] At step 2206, the wireless communication device receives DCI (e.g., as about Figure 13 Step 1308 Figure 14 (as described in step 1408, etc.). The DCI indicates one or more TCI states from a subset of multiple TCI states to be used. In addition, the DCI explicitly or implicitly indicates one or more specific CORESETs from one or more TCI states from a subset of multiple TCI states to be used.

[0215] At step 2207, the wireless communication device uses one or more spatial quasi-co-located (QCL) downlink reference signals contained in one or more states within a subset of multiple states to receive a PDCCH corresponding to one or more specific CORESETs, as will be understood by those skilled in the art.

[0216] At step 2208, in some embodiments, the wireless device receives a configuration of the TCI state IDs of multiple TCI states (e.g., as per the information provided). Figure 13 Step 1304 Figure 14The configuration of the plurality of TCI states is common for two or more CORESETs, or is common for each CORESET.

[0217] In some embodiments, both the configuration of the plurality of TCI states and the configuration of the TCI state IDs are received via a PDSCH-CONFIG IE. In some embodiments, the configuration of the plurality of TCI states applies to all CORESETs configured in the same bandwidth part as the PDSCH-CONFIG IE.

[0218] In some embodiments, the MAC CE activates a subset of the plurality of TCI states for all CORESETs configured in the same bandwidth part as the configuration of the plurality of TCI states. In some embodiments, the MAC CE includes a bandwidth part ID, a serving cell ID, and TCI state IDs of the activated subset of the plurality of TCI states, but does not include a CORESET ID.

[0219] In some embodiments, the MAC CE activates a subset of the plurality of TCI states for all CORESETs configured in the same bandwidth part as the bandwidth part indicated by the bandwidth part ID included in the MAC CE.

[0220] In some embodiments, the configuration of the TCI state IDs of the plurality of TCI states is per CORESET. In some embodiments, the MAC CE activates up to M TCI states for each CORESET. In some embodiments, the MAC CE includes a bandwidth part ID, a serving cell ID, TCI state IDs of the activated subset of the plurality of TCI states, and a CORESET ID.

[0221] In some embodiments, the DCI implicitly indicates one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states.

[0222] In some embodiments, the one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states includes the CORESET in which the PDCCH carrying the DCI is received.

[0223] In some embodiments, the DCI explicitly indicates one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states. In some embodiments, the DCI includes a bit field that indicates the one or more specific CORESETs to use one or more TCI states of the subset of the plurality of TCI states.

[0224] In some embodiments, the TCI update provided by the DCI is applied simultaneously to CORESETs in two or more serving cells or two or more component carriers. In some embodiments, the two or more serving cells or two or more component carriers to which the TCI update provided by the DCI is to be applied simultaneously are preconfigured. In some embodiments, the two or more serving cells or two or more component carriers are indicated by a higher layer parameter. In some embodiments, the two or more serving cells or two or more component carriers are indicated by a higher layer parameter. The higher layer parameter indicates that when the TCI state of a particular CORESET is updated via the DCI in one serving cell, then the TCI state of the corresponding CORESET in one or more other serving cells will also be updated simultaneously. In some embodiments, the CORESETs in the two or more serving cells or two or more component carriers are CORESETs in the same CORESET pool as the CORESET indicated by the DCI implicitly or explicitly.

[0225] Figure 23 is a flowchart of a method performed by a base station 1002 (e.g., gNB, etc.). Note that according to some embodiments, one or more of the steps in Figure 23 may be performed, while other steps are optional. Such steps are represented by dashed boxes.

[0226] At step 2302, the base station transmits, to a wireless communication device via RRC signaling, a configuration of a plurality of TCI states.

[0227] At step 2304, the base station transmits, to the wireless communication device, a MAC CE activating a subset of the plurality of TCI states.

[0228] At step 2306, the base station transmits, to the wireless communication device, a DCI. The DCI indicates one or more TCI states of the subset of the plurality of TCI states to use. Additionally, the DCI explicitly or implicitly indicates one or more particular CORESETs for which the one or more TCI states of the subset of the plurality of TCI states are to be used.

[0229] Any appropriate steps, methods, features, functions, or benefits disclosed herein can be performed by one or more virtual apparatuses. Each virtual apparatus can comprise a plurality of these functional units. Such functional units can be implemented by processing circuitry, which can include one or more microprocessor or microcontroller, along with other digital hardware. The processing circuitry can be configured to execute program code stored in memory, which can include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols and for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry can be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0230] While the processes in the accompanying figures illustrate particular orders of performing the operations, it should be understood that such order is exemplary (e.g., alternative embodiments can perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0231] Embodiments

[0232] Group A Examples

[0233] Embodiment 1 : A method performed by a wireless device for updating at least one TCI state, the method comprising receiving a DCI, wherein the DCI indicates which activated TCI state is used for a CORESET.

[0234] Embodiment 2: The method according to the preceding embodiment, further comprising the step of receiving a PDSCH-CONFIG IE configuring a list of TCI states IDs.

[0235] Embodiment 3: The method according to any preceding embodiment, further comprising the step of configuring a subset of TCI state IDs for each CORESET.

[0236] Embodiment 4: The method according to any of the preceding embodiments, further comprising one or more of: (a) receiving a PDSCH-CONFIG IE configuring a list of TCI states, (b) receiving a MAC CE activating at least one TCI state from the list of TCI states, and (c) receiving a DCI at a CORESET, wherein the DCI indicates to the CORESET which activated TCI state is used.

[0237] Group B Examples

[0238] Example 5: A method performed by a base station for communicating with a UE, the method comprising transmitting DCI, wherein the DCI indicates which activated TCI state is used for a CORESET.

[0239] Example 6: The method of the group B example, further comprising one or more of: (a) configuring a list of TCI states using a PDSCH-CONFIG IE, (b) activating at least one TCI state from the list of TCI states using a MAC CE, and (c) transmitting DCI to the CORESET, wherein the DCI indicates to the CORESET which activated TCI state is used.

[0240] Example 7: The method of the group B example, further comprising the step of transmitting a PDSCH-CONFIG IE that configures a list of TCI state IDs.

[0241] Example 8: The method of the group B example, further comprising the step of configuring a subset of TCI state IDs for each CORESET.

[0242] Group C Examples

[0243] Example 9: A wireless device for operating in a 5G network, the wireless device comprising processing circuitry configured to perform any of the steps of any of the group A examples, and power supply circuitry configured to supply power to the wireless device.

[0244] Example 10: A base station for operating in a 5G network, the base station comprising: processing circuitry configured to perform any of the steps of any of the group B examples; and power supply circuitry configured to supply power to the base station.

[0245] Example 11: A UE for operating in a 5G network, the UE comprising: an antenna configured to transmit and receive wireless signals; and radio front-end circuitry connected to the antenna and the processing circuitry and configured to condition signals passing between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the group A examples. An input interface is connected to the processing circuitry and is configured to allow information to be input into the UE to be processed by the processing circuitry. An output interface is connected to the processing circuitry and is configured to output information from the UE that has been processed by the processing circuitry. A battery is connected to the processing circuitry and is configured to supply power to the UE.

[0246] At least some of the following abbreviations can be used in the present disclosure. If there is an inconsistency in the use of a term among the abbreviations, the above should take precedence over any subsequent listing. Abbreviation

[0247] 3GPP Third Generation Partnership Project

[0248] 5G Fifth Generation

[0249] 5GC Fifth Generation Core

[0250] 5GS Fifth Generation System

[0251] AMF Access and Mobility Management Function

[0252] AN Access Network

[0253] ASIC Application-Specific Integrated Circuit

[0254] AUSF Authentication Server Function

[0255] BWP Bandwidth Part

[0256] CE Control Element

[0257] CONFIG IE Configuration Information Element

[0258] CORESET Control Resource Set

[0259] CP Control Panel

[0260] CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0261] CPU Central Processor Unit

[0262] CRC Cyclic Redundancy Check

[0263] CSI-RS Channel State Information Reference Signal

[0264] DCI Downlink Control Information

[0265] DFT Discrete Fourier Transform

[0266] DL Downlink

[0267] DMRS Demodulation Reference Signal

[0268] DN Data Network

[0269] DSP Digital Signal Processor

[0270] eNB Enhanced or Evolved Node B

[0271] EPS Evolved Packet System

[0272] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0273] FPGA Field-Programmable Gate Array

[0274] FR frequency range

[0275] gNB new radio base station

[0276] gNB-CU new radio base station central unit

[0277] gNB-DU new radio base station distributed unit

[0278] HARQ hybrid automatic repeat request

[0279] HSS home subscriber server

[0280] IE information element

[0281] IoT Internet of Things

[0282] IP Internet Protocol

[0283] LTE Long Term Evolution

[0284] MAC medium access control

[0285] MCS modulation and coding scheme

[0286] MME mobility management entity

[0287] MTC machine type communication

[0288] NEF network exposure function

[0289] NF network function

[0290] NR new radio

[0291] NRF network function repository function

[0292] NSSF network slice selection function

[0293] OFDM orthogonal frequency division multiplexing

[0294] PBCH physical broadcast channel

[0295] PC personal computer

[0296] PCF policy control function

[0297] PDCCH physical downlink control channel

[0298] PDSCH physical downlink shared channel

[0299] P-GW packet data network gateway

[0300] PRB physical resource block

[0301] PSS primary synchronization signal

[0302] PUCCH physical uplink control channel

[0303] PUSCH physical uplink shared channel

[0304] QCL quasi co-location

[0305] QoS quality of service

[0306] RAM random access memory

[0307] RAN radio access network

[0308] Rbs resource block

[0309] RE resource element

[0310] RF radio frequency

[0311] ROM read only memory

[0312] RRC radio resource control

[0313] RRH remote radio head

[0314] RS reference signal

[0315] RTT round trip time

[0316] SCEF service capability exposure function

[0317] SMF session management function

[0318] SPS semi-persistent scheduling

[0319] SRI SRS resource indicator

[0320] SRS sounding reference signal

[0321] SS synchronization signal

[0322] SSB synchronization signal block

[0323] TCI transmission configuration indicator

[0324] TP transmission point

[0325] TRP transmission / reception point

[0326] TRS tracking reference signal

[0327] UDM unified data management

[0328] UE user equipment

[0329] UL uplink

[0330] UPF user plane function

[0331] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless communication device (1012), the method comprising: receiving (1302; 1402; 2202) a configuration of a plurality of transmission configuration indicator, TCI, states via radio resource control, RRC, signaling; receiving (1306; 1406; 2204) a medium access control, MAC, control element, CE, activating a subset of the plurality of TCI states; receiving (1308; 1408; 2206) a downlink control information, DCI, that: indicates one or more TCI states of the subset of the plurality of TCI states to be used; and explicitly indicates one or more specific control resource sets, CORESETs, for which the one or more TCI states of the subset of the plurality of TCI states are to be used; and receiving (2207) a physical downlink control channel, PDCCH, corresponding to the one or more specific CORESETs using one or more spatial quasi co-location, QCL, downlink reference signals contained in the one or more TCI states of the subset of the plurality of TCI states.

2. The method of claim 1, further comprising receiving (1304; 1404) a configuration of TCI state IDs of the plurality of TCI states, the configuration of TCI state IDs being common for two or more control resource sets, CORESETs, or being per CORESET. both the configuration of the plurality of TCI states and the configuration of the TCI state IDs are received in a physical downlink shared channel, PDSCH, configuration information element, PDSCH-CONFIG IE. the configuration of the plurality of TCI states is applicable to all CORESETs configured in a same bandwidth part as the PDSCH-CONFIG IE.

3. The method of claim 2, wherein, the MAC CE activates the subset of the plurality of TCI states for all CORESETs configured in a same bandwidth part as the configuration of the plurality of TCI states.

4. The method of claim 3, wherein, the MAC CE includes a bandwidth part ID, a serving cell ID, and TCI state IDs of the activated subset of the plurality of TCI states, but does not include a CORESET ID.

5. The method of claim 4, wherein, the MAC CE activates the subset of the plurality of TCI states for all CORESETs configured in a same bandwidth part as a bandwidth part indicated by the bandwidth part ID included in the MAC CE.

6. The method of claim 4 or 5, wherein, the configuration of TCI state IDs of the plurality of TCI states is per CORESET.

7. The method of claim 6, wherein, the MAC CE activates up to M TCI states per CORESET.

8. The method of claim 2, wherein, the MAC CE includes a bandwidth part ID, a serving cell ID, TCI state IDs of the activated subset of the plurality of TCI states, and a CORESET ID.

9. The method of claim 8, wherein, the DCI includes a bit field indicating the one or more specific CORESETs for which the one or more TCI states of the subset of the plurality of TCI states are to be used.

10. The method of claim 9, wherein, ​ 11. The method of any one of claims 1-5 and 8-10, wherein, ​ 12. The method of any one of claims 1-5 and 8-10, wherein, The TCI update provided by the DCI is applied simultaneously to two or more serving cells or CORESETs in two or more component carriers.

13. The method of claim 12, wherein, The TCI update provided by the DCI is applied simultaneously to two or more serving cells or two or more component carriers.

14. The method of claim 12, wherein, The two or more serving cells or the two or more component carriers are indicated by a higher layer parameter.

15. The method of claim 12, wherein, The two or more serving cells or the two or more component carriers are indicated by a higher layer parameter, which indicates that when the TCI state of a specific CORESET is updated via DCI in one serving cell, the TCI state of the corresponding CORESET in one or more other serving cells will also be updated simultaneously.

16. The method of claim 12, wherein, The CORESETs in the two or more serving cells or the two or more component carriers are CORESETs in the same CORESET pool as the CORESET implicitly or explicitly indicated by the DCI.

17. A wireless communication device (1012; 2000), comprising: one or more receivers (2010); and processing circuitry (2002) associated with the one or more receivers (2010), the processing circuitry (2002) being configured to cause the wireless communication device (1012; 2000) to perform the method of any one of claims 1-16.

18. A method performed by a network node, the method comprising: sending (2302), to a wireless communication device (2012) via radio resource control, RRC, signaling, a configuration of a plurality of transmission configuration indicator, TCI, states comprising one or more spatial quasi-co-located, QCL, downlink reference signals to enable the wireless communication device to receive a physical downlink control channel, PDCCH, corresponding to one or more specific control resource sets, CORESETs; sending (2304), to the wireless communication device (2012), a medium access control, MAC, control element, CE, activating a subset of the plurality of TCI states; and sending (2306), to the wireless communication device (2012), a downlink control information, DCI, that: indicates one or more TCI states in the subset of the plurality of TCI states to use; and explicitly indicates one or more specific control resource sets, CORESETs, for which the one or more TCI states in the subset of the plurality of TCI states are to be used.

19. A network node (1700) comprising processing circuitry (1704; 1804) configured to cause the network node (1700) to perform the method of claim 18.

Images