Beam interference detection for single DCI-based multi-TRP schemes

Abstract

A method, network node and wireless device (WD) for beam failure detection for a single downlink control information (DCI) based multiple transmit receive point (TRP) scheme. In one embodiment, the network node is configured to configure at least one control resource set (CORESET) in the WD. The network node is also configured to activate at least two transmit configuration indicator (TCI) states. Furthermore, the network node is configured to determine at least one beam failure resource set, each beam failure resource set including a beam failure detection reference signal (BFD-RS), where the BFD-RS is a quasi-co-location (QCL) type-D source in at least one of the at least two activated TCI states for the at least one CORESET.

Description

[Technical Field]

[0001] This disclosure relates to wireless communication, and in particular to beam obstruction detection for a single downlink control information (DCI) based multi-transmit-receive-point (TRP) scheme. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) New Radio (NR, also known as 5th Generation or 5G) uses CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) for both downlink (DL) (in other words, the link from network nodes, gNBs, or base stations to user equipment or radio devices (WDs), also known as UEs) and uplink (UL) (in other words, the link from WDs to gNBs). Discrete Fourier Transform (DFT) spread OFDM is also supported for uplink. In the time domain, NR downlink and uplink transmissions are each organized into subframes of equal size, each 1 millisecond (ms). Each subframe is further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf = 15 kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

[0003] Data scheduling in NR is generally at the slot level. An example with 14 symbol slots is shown in Figure 1, where the first two symbols contain physical downlink control channels (PDCCH), and the remaining symbols contain physical shared data channels, i.e., either PDSCH (physical downlink shared channel) or PUSCH (physical uplink shared channel).

[0004] Different subcarrier spacing values ​​are supported in NR. (Also called different numerologies) The supported subcarrier spacing values ​​are Δf = (15 × 2 μThe interval is given by )kHz, where μ∈{0, 1, 2, 3, 4}. Δf=15kHz is the fundamental subcarrier interval. The slot durations at different subcarrier intervals are: This is given by TIFF0007899187000001.tif10170.

[0005] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 neighboring subcarriers. The RBs are numbered starting from 0 at one end of the system bandwidth. The basic NR physical time frequency resource grid is shown in Figure 2, where only one resource block (RB) within 14 symbol slots is shown. One OFDM subcarrier within one OFDM symbol interval forms one resource element (RE).

[0006] QCL and TCI status Several signals may be transmitted from different antenna ports of the same base station. These signals may share the same large-scale properties, such as Doppler shift / spread, mean delay spread, or mean delay. These antenna ports are said to be quasi-colocated (QCL) in this case.

[0007] If a WD knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the WD can estimate that parameter based on the signal at one of the antenna ports and apply that estimation to receive the signal on the other antenna port. Generally, the first antenna port is represented by a measurement reference signal, such as a channel state information reference signal (CSI-RS) or synchronization signal block (SSB), known as the source reference signal (RS), and the second antenna port is a demodulation reference signal (DMRS), known as the target RS.

[0008] For example, if antenna ports A and B are QCL with respect to mean delay, the WD can estimate the mean delay from the signal received from antenna port A and assume that the signal received from antenna port B has the same mean delay. This is useful for demodulation, for example, because the WD can know in advance the properties of the channels, which helps it when selecting an appropriate channel estimation filter.

[0009] Information regarding what assumptions may be made regarding QCL is signaled from the network to the WD. In the NR, the following four types of QCL relationships between the transmitted source RS and the transmitted target RS are defined: Type A: {Doppler shift, Doppler diffusion, mean delay, delayed diffusion} Type B: {Doppler shift, Doppler diffusion} Type C: {average delay, Doppler shift}, and Type D: {Spatial Rx parameter}.

[0010] QCL Type D was introduced to facilitate beam management with analog beamforming and is known as spatial QCL. Currently, there is no strict definition of spatial QCL, but it is understood that if two transmitted antenna ports are spatially QCL, the WD can use the same Rx beam to receive the signals associated with the two antenna ports.

[0011] Depending on the WD capability, the WD can be configured through radio resource control (RRC) signaling with up to 128 transmit setting indicator (TCI) states for the PDSCH in frequency range 2 (FR2) and up to 8 transmit setting indicator (TCI) states in FR1.

[0012] Each TCI state contains QCL information, in other words, one or two source DL RSs associated with each source RS's QCL type. For example, a TCI state contains a pair of reference signals, each associated with a QCL type. For instance, two different CSI-RSs {CSI-RS1, CSI-RS2} are set in the TCI state as {qcl-Type1, qcl-Type2} = {Type A, Type D}. This means that the WD can derive the Doppler shift, Doppler spread, mean delay, and delayed spread from CSI-RS1, and the spatial Rx parameter (in other words, the RX beam to be used) from CSI-RS2.

[0013] The list of TCI states can be interpreted as a list of possible beams transmitted from the network, or a list of possible TRPs used by the network to communicate with the WD.

[0014] Beam Fault Detection (BFD) in NR Beam Fault Detection (BFD) and Beam Fault Recovery (BFR) are features introduced to the NR since 3GPP Release 15 (3GPP Rel-15). For the purpose of BFD, the network sets a BFD reference signal (Synchronization Signal Block (SSB), Channel State Information Reference Signal (CSI-RS), or both SSB / CSI-RS resources) to the WD, and the WD declares a beam fault when the number of beam fault instance indications from the physical layer reaches a set threshold before a set timer expires. SSB-based BFD can be set based on the SSB associated with the initial DL bandwidth part (BWP), and only for the initial DL BWP, and only for DL ​​BWPs that contain the SSB associated with the initial DL BWP. For other DL BWPs, beam fault detection can be performed based only on CSI-RS.

[0015] Resources for BFD can be configured via Radio Resource Control (RRC) within the RadioLinkMonitoringConfig information element (IE) (as part of SpCellConfig in each dedicated BWP configuration, i.e., as part of BWP-DownlinkDedicated in RRCReconfiguration or RRCResume messages), as follows: RadioLinkMonitoringConfig::= Sequence { failureDetectionResourcesToAddModList RadioLinkMonitoringRS sequence (size (1..maxNrofFailureDetectionResources)) optional, --Need N failureDetectionResourcesToReleaseList RadioLinkMonitoringRS-Id sequence (size (1..maxNrofFailureDetectionResources)) optional, --Need N beamFailureInstanceMaxCount enumeration {n1, n2, n3, n4, n5, n6, n8, n10} optional, --Need N beamFailureDetectionTimer enumeration {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} optional, --Need N ... } RadioLinkMonitoringRS::= Sequence { radioLinkMonitoringRS-Id RadioLinkMonitoringRS-Id, Objective enumeration {beamFailure, rlf, both}, Selecting a Receiving Resource { SSB index, csi-RS-index NZP-CSI-RS-ResourceId }, ...}

[0016] The set threshold for BFD is Q out、LR and Q in、LR where Q out、LR and Q in、LR correspond to the default value of rlmInSyncOutOfSyncThreshold and the value provided by rsrp-ThresholdSSB or rsrp-ThresholdBFR-r16, respectively, as described in 3GPP Technical Specification (TS) 38.133 for Q out respectively, for Q --Serving cell specific MAC and PHY parameters for SpCell: SpCellConfig::= SEQUENCE { servCellIndex ServCellIndex OPTIONAL, --Cond SCG reconfigurationWithSync ReconfigurationWithSync OPTIONAL, --Cond ReconfWithSync rlf-TimersAndConstants SetupRelease {RLF-TimersAndConstants} OPTIONAL, --Need M rlmInSyncOutOfSyncThreshold ENUMERATED {n1} OPTIONAL, --Need S spCellConfigDedicated ServingCellConfig OPTIONAL, --Need M ... } TIFF0007899187000002.tif71170

[0017] The physical layer in WD evaluates the radio link quality according to a set of resource configurations for the threshold Q out、LR for the set TIFF0007899187000003.tif6170. The set[[ID=۴۴]] For TIFF0007899187000004.tif6170, the WD evaluates the radio link quality according to only the periodic CSI-RS resource configuration or the SS / PBCH blocks on the primary cell (PCell) or the primary secondary cell (PSCell) pseudo-collocated using the demodulation reference signal (DM-RS) of the PDCCH reception monitored by the WD. The WD applies the Q in、LR threshold to the layer 1 reference signal received power (L1-RSRP) measurement value obtained from the SS / PBCH block. After scaling each CSI-RS received power using the value provided by powerControlOffsetSS, the WD applies the Q in、LR threshold to the L1-RSRP measurement value obtained for the CSI-RS resource.

[0018] In non-DRX (non-discontinuous reception) mode operation, the physical layer in the WD provides an indication to the upper layer when the radio link quality for all corresponding resource configurations in TIFF0007899187000005.tif6170 is worse than the threshold Q . In other words, if at least one resource exceeds the threshold Q out、LR , the physical layer does not indicate BFD to the upper layer. The physical layer is determined by the periodicity determined by the maximum value during the shortest periodicity among the periodic CSI-RS configurations, and / or the set out、LR used by the WD to evaluate the radio link quality. When the radio link quality is worse than the threshold Q accompanied by the SS / PBCH blocks on the PCell or PSCell in TIFF0007899187000006.tif6170 and within 2 milliseconds, the physical layer notifies the upper layer. In DRX mode operation, the physical layer provides an indication to the upper layer when the radio link quality is worse than the threshold Q out、LR with the periodicity determined, for example, in 3GPP TS 38.133. out、LR

[0019] Beam interference detection based on TCI status According to 3GPP TS 38.213, WD sets a set of periodic CSI-RS resource configuration indices by failureDetectionResources for each bandwidth part (BWP) of a serving cell. TIFF0007899187000007.tif6170, a set of periodic CSI-RS resource configuration indexes. TIFF0007899187000008.tif6170 and / or candidateBeamRSList may be provided for SS / PBCH block indexes, or candidateBeamRSListExt-r16 or candidateBeamRSSCellList-r16 for wireless link quality measurement on the BWP of a serving cell.

[0020] WD uses failureDetectionResources or beamFailureDetectionResourceList for the BWP of the serving cell. If TIFF0007899187000009.tif6170 is not provided, the WD will include a periodic CSI-RS resource setting index with the same value as the RS index in the RS set indicated by the TCI-state (in other words, the activated TCI state) for each control resource set (CORESET) that the WD uses to monitor PDCCH. Determine TIFF0007899187000010.tif6170. If there are two RS indices in the TCI state, set TIFF0007899187000011.tif6170 contains an RS index with a QCL-TypeD setting for the corresponding TCI state. WD is set We expect TIFF0007899187000012.tif6170 to contain up to two RS indices.

[0021] This is referred to as part of the TCI state setting (in the PDSCH setting, PDSCH-Config, within the DL BWP setting), as follows: TCI-State::= Sequence { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info optional, --Need R ... } QCL-Info::= Sequence { Cell ServCellIndex (optional), --Need R bwp-Id BWP-Id Optional, --Cond-CSI-RS-Indicated referenceSignal selection { csi-rs NZP-CSI-RS-ResourceId, SSB Index }, qcl-type enumeration {typeA, typeB, typeC, typeD}, ... } --TAG-TCI-Status-Stop --ASN1STOP

[0022] In the current 3GPP specification, each PDCCH configuration (which is part of the DL BWP configuration, with up to three per cell per BWP) includes one or more control resource sets (CORESETs) configured as follows: PDCCH-Config::= Sequence { controlResourceSetToAddModList A sequence of ControlResourceSets (size (1..3)) Optional, --Need N (...) }

[0023] If multiple CORESETs are configured on a WD, the WD monitors multiple CORESETs for a given BWP. Each CORESET is configured with a list of TCI states. As can be seen below, each CORESET has a list of configured TCI states, given by the list tci-StatesPDCCH-ToAddList. Among the list of TCI states configured for a CORESET, one of the TCI states is activated via the media access control (MAC) control element (CE) command “TCI state indication for WD-specific PDCCH MAC CE” given in section 6.1.3.15 of 3GPP TS 38.321. If the activated TCI state for a CORESET includes a source RS index with a QCL-TypeD setting, the receive beam (in other words, the spatial Rx filter) for receiving the CORESET is derived from the beam used to receive the source RS. --ASN1START --TAG-CONTROLRESOURCESET-START ControlResourceSet::= Sequence { controlResourceSetId, (...) tci-StatesPDCCH-ToAddList Sequence of TCI-StateId (size (1..maxNrofTCI-StatesPDCCH)) optional, --Cond NotSIB1-initialBWP (...) } --TAG-CONTROLRESOURCESET-STOP --ASN1STOP

[0024] WD actions related to beam fault detection (BFD) are primarily specified in the media access control (MAC) specification (3GPP TS 38.321). When multi-radio dual connectivity (MR-DC) is configured for a WD, a secondary cell group (SCG) is configured for the WD.

[0025] When an SCG is set on a WD, two MAC entities—namely, a MAC entity for the Master Cell Group (MCG) and a MAC entity for the SCG—are set on the WD.

[0026] The functions of different MAC entities in WD operate independently unless otherwise specified. The timers and parameters used in each MAC entity are configured independently unless otherwise specified. The serving cell, cell radio network temporary identifier (C-RNTI), radio bearer, logical channel, upper and lower layer entities, LCG, and hybrid automatic retransmission request entity (HARQ) considered by each MAC entity refer to those mapped to that MAC entity unless otherwise specified.

[0027] If one or more SCells are configured in a MAC entity, there may be multiple downlink sharing channels (DL-SCHs), and for each MAC entity, there may be multiple uplink sharing channels (UL-SCHs) and multiple radio access channels (RACHs), i.e., one DL-SCH, one UL-SCH, and one RACH on a SpCell, and one DL-SCH, zero or one UL-SCH, and zero or one RACH for each SCell.

[0028] If no SCell is set for a MAC entity, there is one DL-SCH, one UL-SCH, and one RACH for each MAC entity.

[0029] According to the current MAC specification, the BFD procedure is defined for each serving cell, e.g., a special cell (SpCell), or for each secondary cell (SCell) in a given cell group (e.g., MCG and / or SCG). BFD is used to point a new SSB or CSI-RS to a serving network node (gNB) when a beam fault is detected on the serving SSB / CSI-RS.

[0030] Beam faults are detected by counting beam fault instance (BFI) instructions from lower layers to MAC entities. If beamFailureRecoveryConfig is reset by a higher layer during an ongoing random access (RA) procedure for beam fault recovery for a SpCell, the MAC entity stops the ongoing random access procedure and restarts it using the new setting.

[0031] 3GPP Release 17 (Rel-17) Single Frequency Network (SFN) Based PDCCH Diversity for Single DCI-Based Multi-TRP Schemes In 3GPP NR Rel-17, support for PDCCH diversity for single DCI-based multi-TRP schemes is being considered. One of the schemes being considered in 3GPP Rel-17 is support for extended single-frequency network (SFN) transmission of PDCCH from multiple TRPs. Figure 3 illustrates an example of single-frequency network (SFN) type transmission of PDCCH. In this scheme, the PDCCH DM-RS is associated with two TCI states (each associated with a different TRP). The same PDCCH (in other words, the same DCI) is transmitted from both TRPs through the same control channel resource. As shown in Figure 3, TRP1 uses TCI state k0 to transmit the PDCCH, and TRP2 uses TCI state k1 to transmit the PDCCH. When the PDCCH demodulation reference signal (DM-RS) is associated with two TCI states, at the receiver, the WD determines how to utilize the two TCI states when performing channel estimation on the PDCCH DM-RS.

[0032] To enable SFN-based PDCCH transmission through two TRPs, two TCI states must be activated for CORESET (in other words, the two TCI states to be activated are from the list of TCI states set for CORESET). When the WD receives a PDCCH DM-RS with a CORESET activated using the two TCI states, the WD can perform synchronization and estimation of the long-term channel properties in parallel using DL RS (e.g., TRS) in both TCI states. For example, the WD obtains two channel delay spreads. The WD can then combine these measurements to obtain the channel properties of the SFN channel. For example, the WD can calculate a weighted average of the delay spreads. This average is then used as input to a channel estimation algorithm for the PDCCH DM-RS. Note that PDCCH and PDCCH DM-RS transmit as SFN, while TRS do not transmit as SFN and are "per TRP" transmitters (see TRS#1 and TRS#2 in Figure 3). Therefore, measurements on the TRS provide the WD with some information about whether one TRP is dominant over the other, for example, whether the WD is close to one of the TRPs, or whether a channel leading to one of the TRPs is blocked. The algorithm on the WD can then decide to use only the estimate from one of the TRS (one TCI state) when SFN transmission is weak (meaning one TRP is dominant even when PDCCH is transmitted as SFN).

[0033] When a CORESET with two activated TCI states is set on the WD, the WD must be able to receive PDCCH from two TRPs simultaneously. In FR1, the WD antenna is typically omnidirectional, which allows it to receive signals from all TRPs simultaneously. In FR2, this generally means that the WD must have two receiving panels, each receiving from one TRP.

[0034] The TRS from each TRP may be used by the WD to estimate time, frequency, and other channel properties, such as delayed spread and / or Doppler spread associated with the TRP, while the SSB or CSI-RS may be used by the WD to determine the directional information of each TRP and the best receiving beam or panel for each TRP.

[0035] Non-SFN-based PDCCH repetition for single DCI-based multi-TRP schemes In 3GPP NR Rel-17, it has been proposed to extend the reliability of PDCCH using multiple TRPs by repeating PDCCH in a non-SFN'ed manner through different TRPs. An example is shown in Figure 4, where PDCCH is repeated at different times through two TRPs, both containing the same DCI.

[0036] The PDCCH is repeated in two PDCCH candidates, each associated with one of two TRPs. The two PDCCH candidates are linked, in other words, the location of one PDCCH candidate can be obtained from the other PDCCH candidate. The PDCCH candidates are in different sets of search spaces associated with different CORESETs, as illustrated in Figure 5.

[0037] When performing PDCCH detection, the WD can detect PDCCHs individually for each PDCCH candidate, or together through soft combining of two linked PDCCH candidates. Linked PDCCH candidates may be in two linked search space sets, each associated with a different CORESET. Each of the two associated CORESETs may be activated using one TCI state associated with its respective TRP.

[0038] 3GPP Rel-17 Agreement on BFD for Multi-TRP As explained above, in 3GPP NR Rel-15 / 16, a single beam fault detection resource set TIFF0007899187000013.tif6170 is supported for each BWP in the serving cell. Support for a per-TRP beam fault detection resource set is being considered in 3GPP NR Rel-17. The motivation for this is to detect beam faults on a per-TRP basis (instead of detecting beam faults across all TRPs). To this end, the following considerations were made. Consideration: Regarding M-TRP beam fault detection, it supports independent BFD-RS settings for each TRP, where each TRP is associated with a BFD-RS set. ○Further research (FF): Number of BFD RSs per BFD-RS set, number of BFD-RS sets, and number of BFD RSs across all BFD-RS sets per DL BWP. ○ Supports at least one of the following: explicit and implicit BFD-RS configurations. Each BFD-RS set is explicitly configured using explicit BFD-RS configuration. • Further study the QCL relationship between FFS:BFD-RS and CORESET. FFS: If supported, how should the implicit BFD-RS configuration be determined? ·Regarding the new beam identification for M-TRP: ○When an NBI-RS set is configured for each TRP, it supports independent configuration of a new beam identification RS (NBI-RS) set for each TRP. FFS: Details regarding the association of BFD-RS and NBI-RS, and / or It supports the same new beam identification and setting criteria as the Rel-16 threshold, including L1-RSRP.

[0039] In the above discussion, the beam fault detection resource set is referred to as the beam fault detection-reference signal (BFD-RS) set. Note that 3GPP RAN1 has not yet decided whether the beam fault detection resource set for each TRP should be set explicitly (in other words, via the RRC setting of failureDetectionResources) or implicitly (in other words, when the beam fault detection resource set is determined through the activated TCI state of CORESET). [Overview of the project]

[0040] Some embodiments advantageously provide methods, network nodes, and wireless devices for beam fault detection for single DCI-based multi-TRP schemes.

[0041] In some embodiments, a network node is configured to set up at least one control resource set (CORESET), activate at least one transmit configuration (TCI) state, determine at least one reference signal (RS) as a pseudo-collocation (QCL) type D source reference signal in at least one TCI state for at least one CORESET as at least one beam fault detection RS, and include the determined at least one beam fault detection RS in at least one beam fault resource set.

[0042] In some embodiments, the wireless device is configured to receive the configuration of at least one control resource set (CORESET) and the activation of at least one transmit configuration (TCI) state, and to determine at least one beam fault detection reference signal (BFD-RS) in at least one beam fault resource set.

[0043] In one embodiment, a network node configured to communicate with a wireless device (WD) includes processing circuitry configured to configure the WD with at least one control resource set (CORESET), activate first and second transmit setting indicator (TCI) states for one of the at least one CORESET, and determine at least one beam fault detection resource set, wherein each of the at least one beam fault detection resource set includes at least one beam fault detection reference signal (BFD-RS), the BFD-RS being a reference signal associated with one of the first and second activated TCI states.

[0044] According to this embodiment, in some embodiments, the reference signal associated with one of the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, at least one beam fault detection resource set comprises a single beam fault detection resource set including a first BFD-RS which is a reference signal associated with a first activated TCI state and a second BFD-RS which is a reference signal associated with a second activated TCI state. In some embodiments, at least one CORESET comprises a second CORESET which is activated using a third activated TCI state, and the single beam fault detection resource set includes a third BFD-RS which is a reference signal associated with a third activated TCI state. In some embodiments, at least one CORESET comprises a second CORESET activated using a third activated TCI state and a fourth activated TCI state, and a single beam fault detection resource set includes a third BFD-RS which is a reference signal associated with the third activated TCI state and a fourth BFD-RS which is a reference signal associated with the fourth activated TCI state. In some embodiments, the reference signal associated with one of the third and fourth activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, a first beam fault detection resource set comprises a QCL type D reference signal associated with a first activated TCI state. In some embodiments, a second beam fault detection resource set comprises a QCL type D reference signal associated with a second activated TCI state. In some embodiments, setting up at least one CORESET comprises setting up two linked CORESETs and activating TCI states for each of the two linked CORESETs. In some embodiments, determining at least one beam fault detection resource set includes a reference signal associated with the activated TCI state for both of the two linked CORESETs.

[0045] In another embodiment, a method in a network node configured to communicate with a wireless device (WD) includes configuring the WD with at least one control resource set (CORESET), activating first and second transmit configuration indicator (TCI) states for one of the at least one CORESET, and determining at least one beam fault detection resource set, each of which includes at least one beam fault detection reference signal (BFD-RS), the BFD-RS being a reference signal associated with one of the first and second activated TCI states.

[0046] According to this embodiment, in some embodiments, the reference signal associated with one of the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, at least one beam fault detection resource set comprises a single beam fault detection resource set including a first BFD-RS which is a reference signal associated with a first activated TCI state and a second BFD-RS which is a reference signal associated with a second activated TCI state. In some embodiments, at least one CORESET comprises a second CORESET which is activated using a third activated TCI state, and the single beam fault detection resource set includes a third BFD-RS which is a reference signal associated with a third activated TCI state. In some embodiments, at least one CORESET comprises a second CORESET activated using a third activated TCI state and a fourth activated TCI state, and a single beam fault detection resource set includes a third BFD-RS which is a reference signal associated with the third activated TCI state and a fourth BFD-RS which is a reference signal associated with the fourth activated TCI state. In some embodiments, the reference signal associated with one of the third and fourth activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, a first beam fault detection resource set comprises a QCL type D reference signal associated with a first activated TCI state. In some embodiments, a second beam fault detection resource set comprises a QCL type D reference signal associated with a second activated TCI state. In some embodiments, setting up at least one CORESET comprises setting up two linked CORESETs and activating TCI states for each of the two linked CORESETs. In some embodiments, determining at least one beam fault detection resource set includes a reference signal associated with the activated TCI state for both of the two linked CORESETs.

[0047] In another embodiment, a radio device (WD) configured to communicate with a network node includes a radio interface configured to receive the configuration of at least one control resource set (CORESET) and instructions for activating first and second transmit configuration indicator (TCI) states for one of the at least one CORESET. The WD also includes a processing circuit (84) communicating with the radio interface (82) and configured to determine at least one beam fault detection reference signal (BFD-RS) in at least one beam fault detection resource set, wherein each of the at least one BFD-RS is a pseudo-collocation (QCL) type D reference signal associated with one of the first and second activated TCI states.

[0048] According to this embodiment, in some embodiments, the reference signal associated with one of the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, at least one beam fault detection resource set comprises a single beam fault detection resource set including a first BFD-RS which is a reference signal associated with a first activated TCI state and a second BFD-RS which is a reference signal associated with a second activated TCI state. In some embodiments, at least one CORESET configuration includes two linked CORESET configurations and an indication of an activated TCI state for each of the two linked CORESETs.

[0049] In another embodiment, a method in a wireless device configured to communicate with a network node includes receiving instructions for setting up at least one control resource set (CORESET) and for activating first and second transmit setting indicator (TCI) states for one of the at least one CORESET, and determining at least one beam fault detection reference signal (BFD-RS) in at least one beam fault detection resource set, wherein each of the at least one BFD-RS is a pseudo-collocation (QCL) type D reference signal associated with one of the first and second activated TCI states.

[0050] According to this embodiment, in some embodiments, the reference signal associated with one of the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, at least one beam fault detection resource set comprises a single beam fault detection resource set including a first BFD-RS which is a reference signal associated with a first activated TCI state and a second BFD-RS which is a reference signal associated with a second activated TCI state. In some embodiments, at least one CORESET configuration includes two linked CORESET configurations and an indication of an activated TCI state for each of the two linked CORESETs.

[0051] A more complete understanding of this embodiment and its associated advantages and features will be more readily apparent by referring to the following detailed description, when considered in conjunction with the accompanying drawings. [Brief explanation of the drawing]

[0052] [Figure 1] This figure shows an exemplary NR time-domain structure with a 15 kHz subcarrier spacing. [Figure 2] This diagram shows an example of an NR physical resource grid. [Figure 3] This is an illustrative diagram of SFN-type transmission of a PDCCH through two TRPs. [Figure 4] This figure shows an example of PDCCH repetition from multiple TRPs. [Figure 5] Examples of linked PDCCH candidates in different search space sets within different CORESETs (linked PDCCH candidates are used to repeat PDCCH through different TRPs). [Figure 6] This is a schematic diagram of an exemplary network architecture illustrating a communication system connected to a host computer via an intermediate network, based on the principles of this disclosure. [Figure 7] This is a block diagram of a host computer communicating with a wireless device at least partially via a wireless connection through a network node, according to some embodiments of the present disclosure. [Figure 8] This flowchart illustrates an exemplary method implemented in a communication system including a host computer, network nodes, and wireless devices for running a client application on a wireless device, according to some embodiments of the present disclosure. [Figure 9] This flowchart illustrates exemplary methods implemented in a communication system including a host computer, network nodes, and a wireless device for receiving user data in a wireless device, according to some embodiments of the present disclosure. [Figure 10] This flowchart illustrates an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data from a wireless device on a host computer, according to some embodiments of the present disclosure. [Figure 11] This flowchart illustrates exemplary methods implemented in a communication system including a host computer, network nodes, and wireless devices for receiving user data on a host computer, according to some embodiments of the present disclosure. [Figure 12] This is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure. [Figure 13] This is a flowchart illustrating an exemplary process in a wireless device according to some embodiments of the present disclosure. [Figure 14] This is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure. [Figure 15] This is a flowchart illustrating an exemplary process in a wireless device according to some embodiments of the present disclosure. [Figure 16] This figure shows an example of BFD resource determination using a single BFD resource set when CORESET is configured for SFN-based PDCCH diversity, according to some embodiments of the present disclosure. [Figure 17] This figure shows a second example of BFD resource determination using a single BFD resource set when CORESET is configured for SFN-based PDCCH diversity, according to some embodiments of the present disclosure. [Figure 18] This figure shows a third example of BFD resource determination using a single BFD resource set when CORESET is configured for SFN-based PDCCH diversity, according to some embodiments of the present disclosure. [Figure 19] This figure shows an example of BFD resource determination using two BFD resource sets (e.g., one BFD resource set per TRP) when CORESET is configured for SFN-based PDCCH diversity, according to some embodiments of the present disclosure. [Figure 20] This figure shows an example of BFD resource determination using a single BFD resource set when two CORESETs are configured for non-SFN-based PDCCH iterations, according to some embodiments of the present disclosure. [Figure 21]This figure shows a second example of BFD resource determination using a single BFD resource set when two CORESETs are configured for non-SFN-based PDCCH iterations, according to some embodiments of the present disclosure. [Figure 22] This figure shows a third example of BFD resource determination using a single BFD resource set when two CORESETs are configured for non-SFN-based PDCCH iterations, according to some embodiments of the present disclosure. [Figure 23] This figure shows an example of BFD resource determination using two BFD resource sets when two CORESETs are configured for non-SFN-based PDCCH repetition, according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0053] In existing NR standards, when beam fault detection resources are implicitly determined, the WD is set It is determined that the resources in TIFF0007899187000014.tif6170 are determined from the TCI states activated for each CORESET. However, in NR Rel-15 / 16, only a single TCI state may be activated per CORESET. In the case of the Rel-17 SFN-based PDCCH diversity scheme recently considered in 3GPP RAN1, a CORESET may be activated using two TCI states. Therefore, how beam fault detection resources are determined when a CORESET is activated using two TCI states remains an unresolved issue.

[0054] For non-SFN-based PDCCH repetitions to be supported in NR Rel-17, the PDCCH is repeated through two different TRPs via two linked PDCCH candidates in two different search space sets in two different CORESETs. The different CORESETs are activated using different TCI states (in other words, one TCI state is activated for each CORESET). How the beam fault detection resource is determined when two linked CORESETs are configured in the WD (for the purpose of PDCCH repetition) is another unresolved issue.

[0055] Some embodiments of this disclosure are -In the case of the SFN-PDCCH scheme where two TCI states are activated for each CORESET, and - In the case of a PDCCH repetition scheme where two TCI states are activated for two linked CORESETs, This provides a proposed solution for beam fault detection resource determination.

[0056] Some embodiments may advantageously provide solutions for enabling BFD resource determination when two TCI states are activated per CORESET for SFN-based PDCCH reception. Some embodiments may enable BFD resource determination when two TCI states are activated for two linked CORESETs (for the purpose of PDCCH repetition). Some proposed solutions also enable BFD resource determination in multi-TRP scenarios.

[0057] Before describing exemplary embodiments in detail, it should be noted that the embodiments primarily concern combinations of apparatus components and processing steps relating to beam fault detection for single DCI-based multi-TRP systems. Therefore, components are represented in the figures by common symbols where appropriate, so as not to obscure this disclosure by details that would be immediately apparent to those skilled in the art who benefit from this specification, and only specific details relevant to understanding these embodiments are shown. Throughout this specification, similar numbers refer to similar elements.

[0058] Where used herein, relational terms such as “first” and “second,” “upper” and “lower” may be used solely to distinguish one entity or element from another, and do not necessarily require or imply any physical or logical relationship or order between such entities or elements. The terminology used herein is intended solely to describe specific embodiments and is not intended to limit the concepts described herein. Where used herein, the singular forms “a,” “an,” and “the” are intended to also include the plural form unless the context otherwise explicitly indicates. Where used herein, the terms “comprises,” “comprising,” “includes,” and / or “including,” when used herein, specify the presence of the described feature, integer, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0059] In embodiments described herein, the term "connecting," such as "communicating with," may be used to refer to electrical or data communication, which can be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will understand that multiple components may interact and that modifications and variations may be possible to achieve electrical and data communication.

[0060] In some embodiments described herein, terms such as “coupled” and “connected” may be used herein to refer, not necessarily directly, to a connection, and may include wired and / or wireless connections.

[0061] As used herein, the term "network node" can refer to any type of network node present in a wireless network, including TRPs, base stations (BS), radio base stations, base transceiver stations (BTS), base station controllers (BSC), radio network controllers (RNC), g-Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio nodes such as MSR BS, multi-cell / multicast coordination entities (MCE), integrated access and backhaul (IAB) nodes, relay nodes, donor node control relays, access points (AP), transmit points, transmit nodes, remote radio units (RRU), remote radio heads (RRH), and core network nodes (for example, mobile management entities (MME)). The network nodes may further include any of the following: entities, self-organizing network (SON) nodes, cooperative nodes, location determination nodes, MDT nodes, etc., external nodes (e.g., third-party nodes, nodes outside the current network), nodes in a distributed antenna system (DAS), spectrum access system (SAS) nodes, element management system (EMS), etc. Network nodes may also include test equipment.As used herein, the term “wireless node” may also be used to refer to a wireless device (WD) or a wireless network node or other wireless device (WD).

[0062] A “network node” may comprise one or more TRPs. In some embodiments, a TRP may be a network node, a radio head, a spatial relation, or a transmit-setting indicator (TCI) state. In some embodiments, a TRP may be represented by a spatial relation or a TCI state. In some embodiments, a TRP may use multiple TCI states. In some embodiments, a TRP may be part of a gNB that transmits and receives radio signals to and from a WD according to the physical layer properties and parameters inherent to its element. In some embodiments, in multiple transmit / receive point (multi-TRP) operation, a serving cell may schedule WDs from two TRPs to provide better PDSCH coverage, reliability, and / or data rate. There are two different operating modes for multi-TRP: single DCI and multi-DCI. For both modes, control of uplink and downlink operation is performed by both the physical layer and the MAC. In single DCI mode, the WD is scheduled by the same DCI for both TRPs, while in multi-DCI mode, the WD is scheduled by independent DCIs from each TRP.

[0063] While some embodiments of this disclosure may use the terms “TRP” or more generally “Network Node” to illustrate exemplary embodiments, it should be understood that the TRPs and Network Nodes described in various embodiments may be any of those described above as examples of TRPs and / or Network Nodes.

[0064] In some embodiments, the non-limiting terms "wireless device (WD)" and "user equipment (UE)" are used interchangeably. A WD as used herein can be any type of wireless device capable of communicating with a network node or another WD, such as another wireless device (WD), via radio signals. A WD may also be a wireless communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a machine-to-machine (M2M) capable WD, a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop onboard equipment (LME), a USB dongle, customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device.

[0065] In addition, in some embodiments, the general term “wireless network node” is used. This may be any type of wireless network node that may comprise any of the following: base station, wireless base station, base station transceiver station, base station controller, network controller, RNC, evolved node B (eNB), node B, gNB, multicell / multicast cooperative entity (MCE), IAB node, relay node, access point, wireless access point, remote radio unit (RRU), remote radio head (RRH).

[0066] As used herein, the term “signaling” may include any of the following: higher-layer signaling (e.g., via Radio Resource Control (RRC), etc.), lower-layer signaling (e.g., via a physical control channel or broadcast channel), or a combination thereof. Signaling may be implicit or explicit. Signaling may also be unicast, multicast, or broadcast. Signaling may also be direct to another node or mediated through a third node.

[0067] Signaling generally comprises one or more symbols and / or signals and / or messages. A signal may comprise one or more bits or represent one or more bits. An instruction may represent a signaling and / or be implemented as a signal or as multiple signals. One or more signals may be contained in a message and / or represented by a message. A signaling, in particular a control signaling, may comprise multiple signals and / or messages, and the multiple signals and / or messages may be transmitted on different carriers and / or associated with different signaling processes, for example, representing one or more such processes and / or corresponding information and / or relating to one or more such processes and / or corresponding information. An instruction may include, and / or contain, a signaling and / or multiple signals and / or messages, transmitted over different carriers and / or associated with different acknowledgment signaling processes, for example, representing one or more such processes and / or relating to one or more such processes. Signaling associated with a channel may be transmitted to represent signaling and / or information for that channel, and / or to be interpreted by the transmitter and / or receiver as belonging to that channel. Such signaling may generally conform to the transmission parameters and / or format for the channel.

[0068] Instructions can generally refer explicitly and / or implicitly to the information they represent and / or point to. Implicit instructions may be based, for example, on a location and / or resources used for transmission. Explicit instructions may be based, for example, on parameterization using one or more parameters and / or one or more indexes corresponding to a table and / or one or more bit patterns representing the information.

[0069] Downlink transmission may relate to transmission from the network or network node to a terminal. The terminal may be considered a WD or UE. Uplink transmission may relate to transmission from a terminal to the network or network node. Sidelink transmission may relate to (direct) transmission from one terminal to another. Uplink, downlink, and sidelink (e.g., sidelink transmission and reception) may be considered as directions of communication. In some variations, uplink and downlink may also be used to describe wireless communication between network nodes, for example, between base stations or similar network nodes, for example, for wireless backhaul and / or relay communications and / or (wireless) network communications, and especially for communications terminating therein. Backhaul and / or relay communications and / or network communications may be considered as being implemented as sidelink or uplink communications or similar forms.

[0070] Setting up a wireless node Configuring a radio node, particularly a terminal or user equipment or WD, may refer to a radio node that is adapted to operate according to a configuration, or is triggered to operate, or is set and / or commanded to operate. Configuration may be performed by another device, such as a network node (e.g., a base station or a radio node in a network such as gNodeB) or the network, in which case configuration may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and / or comprise one or more instructions relating to the configuration, such as a configuration for transmitting and / or receiving on allocated resources, particularly frequency resources, or a configuration for performing a particular measurement on a particular subframe or radio resource. A radio node may configure itself, for example, based on configuration data received from a network or network node. A network node may use and / or adapt to use one or more of its own circuits for configuration. Allocation information may be considered in the form of configuration data. Configuration data may comprise and / or comprise configuration information and / or comprise one or more corresponding instructions and / or messages.

[0071] Overview of what to set up Generally, configuring may include determining configuration data representing the configuration and providing, for example, transmitting, the configuration data to one or more other nodes (in parallel and / or sequentially), the nodes which may transmit the configuration data to further radio nodes (or to other nodes, which may be repeated until the configuration data reaches the radio device). Alternatively or additionally, configuring a radio node may include, for example, by a network node or other device, receiving configuration data and / or data related to the configuration data from another node, such as a network node, which may be a higher-level node in the network, and / or transmitting the received configuration data to the radio node. Thus, determining the configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities that can communicate via a suitable interface, for example, an X2 interface in the case of LTE, or a corresponding interface in the case of NR. Configuring a terminal (e.g., a WD) may include scheduling downlink and / or uplink transmissions to the terminal, such as downlink data and / or downlink control signaling and / or DCI and / or uplink control or data or communication signaling, in particular acknowledgment signaling, and / or configuring resources and / or resource pools for them. In particular, configuring a terminal (e.g., a WD) may include configuring the WD to perform specific measurements on a particular subframe or radio resource and reporting such measurements in accordance with embodiments of the present disclosure.

[0072] In the context of this disclosure, "prioritized" may refer to relevant information that is, for example, specified in a standard, and / or available from a network or network node, for example, stored in memory, for example, and for example, set, without any special configuration independent of that. "Setting" or "configurable" may be considered to be related to corresponding information that is, for example, set / configured by a network or network node.

[0073] In some embodiments, the term "set" as used herein may refer to a set of one or more elements within a set.

[0074] It should be noted that while terminology from a specific radio system, such as 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be considered to limit the scope of this disclosure to the aforementioned system only. Without limitation, other radio systems, including Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from leveraging the concepts covered within this disclosure.

[0075] Furthermore, it should be noted that the functions described herein as being implemented by wireless devices or network nodes may be distributed across multiple wireless devices and / or network nodes. In other words, the functions of network nodes and wireless devices described herein are not limited to implementation by a single physical device, but are intended to be distributed across several physical devices.

[0076] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as those commonly understood by those skilled in the art to which this disclosure belongs. Terms used herein should be construed to have meanings consistent with their meanings in the context of this specification and related art, and should not be interpreted in an idealized or overly formal sense unless explicitly stated herein.

[0077] Some embodiments provide configurations for beam fault detection for single DCI-based multi-TRP schemes. Referring again to drawings where similar elements are referenced by similar reference numbers, Figure 6 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP-type cellular network capable of supporting standards such as LTE and / or NR (5G), comprising an access network 12 such as a radio access network and a core network 14. The access network 12 comprises several network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of radio access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to a corresponding network node 16a or to be paged by the corresponding network node 16a. A second WD 22b in coverage area 18b is capable of wirelessly connecting to a corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless device 22) are illustrated in this example, the disclosed embodiments are equally applicable to situations where only one WD is in a coverage area or where only one WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0078] Furthermore, it is intended that the WD22 can be configured to communicate simultaneously with two or more network nodes 16 and two or more types of network nodes 16, and / or to communicate separately. For example, the WD22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, the WD22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0079] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a server implemented in the cloud, a distributed server, or as a processing resource in a server farm. The host computer 24 may be owned or controlled by a service provider, or operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend via an optional intermediate network 30. The intermediate network 30 may be one of a public, private, or hosted network, or a combination of two or more of these. The intermediate network 30 may be a backbone network or the internet, if any. In some embodiments, the intermediate network 30 may comprise two or more subnets (not shown).

[0080] The communication system in Figure 6, as a whole, enables connectivity between one of the connected WD22a, 22b and the host computer 24. The connectivity may also be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD22a, 22b are configured to communicate data and / or signaling over the OTT connection, using the access network 12, the core network 14, an optional intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of uplink and downlink communications. For example, base station 16 may not be aware of, or does not need to be aware of, the past routing of incoming downlink communications with data originating from the host computer 24 that should be forwarded (e.g., handed over) to the connected WD22a. Similarly, network node 16 does not need to be aware of the future routing of outgoing uplink communications originating from WD22a and destined for host computer 24.

[0081] Network node 16 is configured to include a configuration unit 32 configured to configure at least one control resource set (CORESET) and to activate at least one transmit configuration (TCI) state, to determine at least one reference signal (RS) as a pseudo-collocation (QCL) type D source RS in at least one TCI state for at least one CORESET as at least one beam fault detection RS (BFD-RS), and to include the determined at least one BFD-RS in at least one beam fault resource set.

[0082] The wireless device 22 is configured to include a determination unit 34 configured to receive the setting of at least one control resource set (CORESET) and the activation of at least one transmit setting (TCI) state, and is configured to determine at least one beam fault detection reference signal (BFD-RS) in at least one beam fault resource set. In some embodiments, the determination unit 34 is configured to determine at least one beam fault detection reference signal (BFD-RS) in at least one beam fault detection resource set, and each of the at least one BFD-RS is a pseudo-collocation (QCL) type D source RS in at least one of at least two activated TCI states for at least one of the at least one CORESET.

[0083] Next, exemplary implementations of embodiments of the WD22, network node 16, and host computer 24 discussed in the previous paragraph will be described with reference to Figure 7. In the communication system 10, the host computer 24 comprises hardware (HW) 38 including a communication interface 40, which is configured to set up and maintain wired or wireless connections with the interfaces of different communication devices in the communication system 10. The host computer 24 further comprises processing circuitry 42 which may have storage and / or processing capabilities. Processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to, or instead of, a processor and memory such as a central processing unit, processing circuitry 42 may comprise integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 44 may be configured to access memory 46 (for example, to write to memory 46 and / or read from memory 46), and memory 46 may comprise any kind of volatile and / or nonvolatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0084] The processing circuit 42 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be performed, for example, by the host computer 24. The processor 44 corresponds to one or more processors 44 for performing the functions of the host computer 24 described herein. The host computer 24 includes memory 46, which is configured to store the data, programmatic software code, and / or other information described herein. In some embodiments, the software 48 and / or host application 50 may include instructions, which, when executed by the processor 44 and / or processing circuit 42, cause the processor 44 and / or processing circuit 42 to perform the processes described herein with respect to the host computer 24. The instructions may be software associated with the host computer 24.

[0085] The software 48 may be executable by the processing circuit 42. The software 48 includes a host application 50. The host application 50 may be able to operate to provide services to a remote user, such as a WD22 connected via an OTT connection 52 that terminates at the host computer 24. When providing services to a remote user, the host application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information as described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider, and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, and control the network node 16 and / or wireless device 22, transmit to the network node 16 and / or wireless device 22, and / or receive from the network node 16 and / or wireless device 22. The processing circuitry 42 of the host computer 24 may include a monitor unit 54 configured to enable the service provider to observe, monitor, and control the network node 16 and / or wireless device 22, to transmit to the network node 16 and / or wireless device 22, and / or to receive from the network node 16 and / or wireless device 22.

[0086] The communication system 10 further includes a network node 16, which is provided within the communication system 10 and includes hardware 58 that enables the network node 16 to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining wired or wireless connections with the interfaces of different communication devices of the communication system 10, and a wireless interface 62 for setting up and maintaining at least a wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The wireless interface 62 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include them. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct, or the connection 66 may pass through the core network 14 of the communication system 10 and / or one or more intermediate networks 30 outside the communication system 10.

[0087] In the embodiments shown, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and memory 72. In particular, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 68 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 70 may be configured to access memory 72 (e.g., write to memory 72 and / or read from memory 72), and memory 72 may include any kind of volatile and / or non-volatile memory, for example, cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0088] As a result, the network node 16 further has software 74, which is stored internally, for example, in memory 72, or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by processing circuit 68. The processing circuit 68 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the functions of the network node 16 as described herein. Memory 72 is configured to store the data, programmatic software code, and / or other information described herein. In some embodiments, the software 74 may include instructions, which, when executed by the processor 70 and / or processing circuit 68, cause the processor 70 and / or processing circuit 68 to perform the processes described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include a configuration unit 32 configured to implement the network node method discussed herein, such as the method discussed with reference to Figures 12 and 14 and other drawings.

[0089] The communication system 10 further includes the WD22 already mentioned. The WD22 may have hardware 80, which may include a radio interface 82 configured to set up and maintain a radio connection 64 with a network node 16 serving the coverage area 18 in which the WD22 is currently located. The radio interface 82 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include them.

[0090] The WD22 hardware 80 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and memory 88. In particular, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 84 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 86 may be configured to access memory 88 (for example, to write to memory 88 and / or read from memory 88), and memory 88 may include any kind of volatile and / or non-volatile memory, for example, cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0091] As a result, the WD22 may further include software 90, which may be stored, for example, in memory 88 in the WD22 or in external memory accessible by the WD22 (e.g., a database, storage array, network storage device, etc.). The software 90 may be executable by processing circuit 84. The software 90 may include a client application 92. The client application 92 may be able to operate to provide services to human or non-human users via the WD22 with the support of a host computer 24. A host application 50 running on the host computer 24 may communicate with the running client application 92 via an OTT connection 52 that terminates in the WD22 and the host computer 24. When providing services to a user, the client application 92 may receive request data from the host application 50 and provide user data in response to that request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that the client application 92 provides.

[0092] The processing circuit 84 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be carried out, for example, by the WD22. The processor 86 corresponds to one or more processors 86 for carrying out the functions of the WD22 described herein. The WD22 includes a memory 88, which is configured to store the data, programmatic software code, and / or other information described herein. In some embodiments, the software 90 and / or client application 92 may include instructions, which, when executed by the processor 86 and / or processing circuit 84, cause the processor 86 and / or processing circuit 84 to carry out the processes described herein with respect to the WD22. For example, the processing circuit 84 of the wireless device 22 may include a decision unit 34 configured to carry out the WD methods discussed herein, such as the methods discussed with reference to Figures 13 and 15 and other drawings.

[0093] In some embodiments, the internal workings of the network node 16, WD22, and host computer 24 may be as shown in Figure 7, and separately, the surrounding network topology may be as shown in Figure 6.

[0094] In Figure 7, the OTT connection 52 is depicted abstractly to illustrate communication between the host computer 24 and the wireless device 22 via the network node 16, without explicitly mentioning any intermediate devices or the precise routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from WD22, the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may also make decisions to dynamically change the routing (for example, based on network load balancing considerations or reconfiguration).

[0095] The wireless connection 64 between WD22 and network node 16 follows the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to WD22 by using an OTT connection 52 in which the wireless connection 64 forms the final segment. More precisely, some teachings of these embodiments improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user wait time, relaxed file size limitations, improved responsiveness, and extended battery life.

[0096] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors, which are improved in one or more embodiments. Optional network functionality may further be available for reconfiguring the OTT connection 52 between the host computer 24 and the WD22 in response to variations in the measurement results. The measurement procedure and / or network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, or in the software 90 of the WD22, or both. In embodiments, a sensor (not shown) may be deployed in or in relation to a communication device through which the OTT connection 52 passes, and the sensor may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. Reconfiguring the OTT connection 52 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration may not need to affect the network node 16, and may be unknown to or imperceptible to the network node 16. Several such procedures and functionalities are known and can be practiced in the art. In some embodiments, the measurement may be accompanied by proprietary WD signaling that facilitates the measurement of the host computer 24, such as throughput, propagation time, latency, etc. In some embodiments, the measurement may be implemented in which software 48, 90 causes messages, in particular empty or "dummy" messages, to be sent using an OTT connection 52 while software 48, 90 monitors propagation time, errors, etc.

[0097] In some embodiments, the host computer 24 includes a processing circuit 42 configured to provide user data and a communication interface 40 configured to forward the user data to the cellular network for transmission to the WD22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 and / or the processing circuit 68 of the network node 16 are configured to perform the functions and / or methods described herein to prepare / start / maintain / support / terminate transmissions to the WD22 and / or prepare / terminate / maintain / support / terminate transmissions from the WD22.

[0098] In some embodiments, the host computer 24 includes a processing circuit 42 and a communication interface 40, the communication interface 40 being configured to receive user data originating from transmissions from the WD 22 to the network node 16. In some embodiments, the WD 22 is configured to perform the functions and / or methods described herein to prepare / start / maintain / support / terminate transmissions to the network node 16 and / or prepare / terminate / maintain / support / terminate transmissions from the network node 16, and / or includes a radio interface 82 and / or processing circuit 84 configured in such a manner.

[0099] Figures 6 and 7 show various "units," such as a setting unit 32 and a decision unit 34, which are located within each processor. It is intended that these units may be implemented such that a portion of the unit is stored in corresponding memory within the processing circuit. In other words, the units may be implemented in hardware or as a combination of hardware and software within the processing circuit.

[0100] Figure 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figures 6 and 7, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD22, which may be described with reference to Figure 7. In a first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides user data by executing a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission to carry the user data to the WD22 (block S104). In an optional third step, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the WD22, in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, WD22 executes a client application, such as client application 92, associated with the host application 50 executed by the host computer 24 (block S108).

[0101] Figure 9 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 6, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD22, which may be described with reference to Figures 6 and 7. In a first step of the method, the host computer 24 provides user data (block S110). In an optional substep (not shown), the host computer 24 provides user data by executing a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission to carry the user data to the WD22 (block S112). The transmission may travel through the network node 16, as taught in the embodiments described throughout this disclosure. In an optional third step, the WD22 receives the user data carried in the transmission (block S114).

[0102] Figure 10 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 6, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD22, which may be described with reference to Figures 6 and 7. In an optional first step of the method, the WD22 receives input data provided by the host computer 24 (block S116). In an optional substep of the first step, the WD22 runs a client application 92, which provides user data in response to the received input data provided by the host computer 24 (block S118). In an optional second step, either additionally or alternatively, the WD22 provides user data (block S120). In an optional substep of the second step, the WD provides user data by running a client application, such as the client application 92 (block S122). When providing user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, WD22 may, in an optional third substep, initiate transmission of the user data to the host computer 24 (block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from WD22 in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

[0103] Figure 11 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 6, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD22, which may be described with reference to Figures 6 and 7. In an optional first step of the method, the network node 16 receives user data from the WD22 (block S128), in accordance with the teachings of the embodiments described throughout this disclosure. In an optional second step, the network node 16 initiates a transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0104] Figure 12 is a flowchart of an exemplary process in a network node 16 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods performed by the network node 16 may be performed by one or more elements of the network node 16, such as by a setting unit 32 in a processing circuit 68, a processor 70, a radio interface 62, etc., according to the exemplary method. The exemplary method includes setting up at least one control resource set (CORESET) and activating at least one transmit setting (TCI) state, such as via the setting unit 32, the processing circuit 68, the processor 70 and / or the radio interface 62 (block S134). The method includes determining at least one reference signal (RS) as a pseudo-collocation (QCL) type D source reference signal in at least one TCI state for at least one CORESET as at least one beam fault detection RS, such as via the setting unit 32, the processing circuit 68, the processor 70 and / or the radio interface 62 (block S136). The method includes including at least one determined BFD-RS in at least one beam fault detection resource set, such as via the configuration unit 32, processing circuit 68, processor 70 and / or wireless interface 62 (block S138). In some embodiments, only some of these steps are performed by the network node 16. In some of these embodiments, the results associated with steps not performed by the network node 16 are performed elsewhere and derived and / or obtained by the network node 16 in a different manner, or they may be replaced by alternative steps.

[0105] In some embodiments, setting, activating and including further includes setting one CORESET and activating two TCI states via a medium access control (MAC) control element (CE), such as via a setting unit 32, a processing circuit 68, a processor 70 and / or a wireless interface 62, and including at least determined BFD-RS in a first beam fault detection resource set and a second beam fault detection resource set, such as via a setting unit 32, a processing circuit 68, a processor 70 and / or a wireless interface 62, wherein the first beam fault detection resource set corresponds to a first transmit / receive point (TRP) and the second beam fault detection resource set corresponds to a second TRP, and includes at least determined BFD-RS.

[0106] In some embodiments, setting, activating and including further comprises setting two CORESETs, such as via a setting unit 32, a processing circuit 68, a processor 70 and / or a wireless interface 62, activating one TCI state for each of the two CORESETs via a medium access control (MAC) control element (CE), and including at least one determined BFD-RS in a single beam fault detection resource set, such as via a setting unit 32, a processing circuit 68, a processor 70 and / or a wireless interface 62.

[0107] Figure 13 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods performed by WD22 may be performed by one or more elements of WD22, such as by a decision unit 34 in processing circuit 84, a processor 86, a wireless interface 82, etc. An exemplary method includes receiving the setting of at least one control resource set (CORESET) and the activation of at least one transmit setting (TCI) state, such as via the decision unit 34, processing circuit 84, processor 86 and / or wireless interface 82 (block S140). The method includes determining at least one beam fault detection reference signal (BFD-RS) in at least one beam fault detection resource set, such as via the decision unit 34, processing circuit 84, processor 86 and / or wireless interface 82 (block S142). In some of these embodiments, results associated with steps not performed by WD22 are performed elsewhere and derived and / or obtained by WD22 in a different manner, or they can be replaced by alternative steps.

[0108] In some embodiments, receiving a setting, receiving an activation, and determining a setting further comprises one or more of the following: receiving a setting for one CORESET and an activation for two TCI states via a medium access control (MAC) control element (CE) for the CORESET, such as via a determination unit 34, a processing circuit 84, a processor 86, and / or a wireless interface 82; and determining at least one BFD-RS in a first beam fault detection resource set and a second beam fault detection resource set, such as via a determination unit 34, a processing circuit 84, a processor 86, and / or a wireless interface 82, wherein the first beam fault detection resource set corresponds to a first transmit-receive point (TRP) and the second beam fault detection resource set corresponds to a second TRP.

[0109] In some embodiments, receiving settings, receiving activations, and determining settings further comprises receiving settings and activations of one TCI state for two CORESETs via a medium access control (MAC) control element (CE) for each of two CORESETs, such as via a determination unit 34, a processing circuit 84, a processor 86, and / or a wireless interface 82, and determining at least one BFD-RS in a single beam fault detection resource set, such as via a determination unit 34, a processing circuit 84, a processor 86, and / or a wireless interface 82.

[0110] Figure 14 is a flowchart of another exemplary process in a network node 16 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods performed by the network node 16 may be performed by one or more elements of the network node 16, such as by a setting unit 32 in a processing circuit 68, a processor 70, a radio interface 62, etc., according to the exemplary method. The exemplary method includes setting up at least one control resource set (CORESET) in the WD (block S144), activating first and second transmit setting indicator (TCI) states for one of the at least one CORESET (block S146), and determining at least one beam fault detection resource set, each of the at least one beam fault detection resource set including at least one beam fault detection reference signal (BFD-RS), where the BFD-RS is a reference signal associated with one of the first and second activated TCI states (block S148).

[0111] In some embodiments, the reference signal associated with one of the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, at least one beam fault detection resource set comprises a single beam fault detection resource set including a first BFD-RS which is a reference signal associated with a first activated TCI state and a second BFD-RS which is a reference signal associated with a second activated TCI state. In some embodiments, at least one CORESET comprises a second CORESET which is activated using a third activated TCI state, and the single beam fault detection resource set includes a third BFD-RS which is a reference signal associated with the third activated TCI state. In some embodiments, at least one CORESET comprises a second CORESET activated using a third activated TCI state and a fourth activated TCI state, and a single beam fault detection resource set includes a third BFD-RS which is a reference signal associated with the third activated TCI state and a fourth BFD-RS which is a reference signal associated with the fourth activated TCI state. In some embodiments, the reference signal associated with one of the third and fourth activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, a first beam fault detection resource set comprises a QCL type D reference signal associated with a first activated TCI state. In some embodiments, a second beam fault detection resource set comprises a QCL type D reference signal associated with a second activated TCI state. In some embodiments, setting up at least one CORESET comprises setting up two linked CORESETs and activating TCI states for each of the two linked CORESETs. In some embodiments, determining at least one beam fault detection resource set includes a reference signal associated with the activated TCI state for both of the two linked CORESETs.

[0112] Figure 15 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods performed by WD22 may be performed by one or more elements of WD22, such as a decision unit 34 in processing circuit 84, a processor 86, a wireless interface 82, etc. An exemplary method includes setting up at least one control resource set (CORESET) and receiving instructions to activate first and second transmit setting indicator (TCI) states for one of the at least one CORESET (block S150), and determining at least one beam fault detection reference signal (BFD-RS) in at least one beam fault detection resource set, wherein each of the at least one BFD-RS is a pseudo-collocation (QCL) type D reference signal associated with one of the first and second activated TCI states (block S152).

[0113] According to this embodiment, in some embodiments, the reference signal associated with one of the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal. In some embodiments, at least one beam fault detection resource set comprises a single beam fault detection resource set including a first BFD-RS which is a reference signal associated with a first activated TCI state and a second BFD-RS which is a reference signal associated with a second activated TCI state. In some embodiments, at least one CORESET configuration includes two linked CORESET configurations and an indication of an activated TCI state for each of the two linked CORESETs.

[0114] Having described the general process flow of the configuration of this disclosure and provided examples of hardware and software configurations for implementing the processes and functions of this disclosure, the following sections provide details and examples of configurations for beam fault detection for a single DCI-based multi-TRP scheme that may be implemented by a network node 16, a wireless device 22, and / or a host computer 24.

[0115] Embodiment 1: CORESET is configured for SFN-based PDCCH diversity - BFD resource determination when configured for a single BFD resource set In one embodiment, CORESET is activated using two TCI states (for example, via MAC CE sent to WD22 by network node 16), where each active TCI state includes a QCL-TypeD source RS, as shown in Figure 16. If the SSB / CSI-RS is not set as a beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set to WD22 by network node / NN16, for example), WD22 may assume that the reference signal used as the QCL-TypeD source reference signal in the two activated TCI states for CORESET is used as the beam detection reference signal. In the example in Figure 16, a QCL-TypeD source reference signal with a CSI-RS resource IDx (or SSB IDx) corresponding to the first activated TCI state and a QCL-TypeD source reference signal with a CSI-RS resource IDy (or SSB IDy) corresponding to the second activated TCI state may be included by WD22 in the beam fault detection resource set. In some embodiments, the beam fault detection resource set may include additional QCL-type D source reference signals corresponding to TCI states activated in other CORESETs (in other words, other CORESETs in the same bandwidth part and serving cell as the CORESET shown in Figure 16). Here, the first and second activated TCI states are identified as the first and second TCI states activated by the MAC CE, respectively. In alternative embodiments, the first and second activated TCI states are the TCI states activated for the CORESET having the lowest and highest TCI state IDs.

[0116] In another embodiment, CORESET is activated using two TCI states (for example, via MAC CE sent to WD22 by network node 16), where each active TCI state includes a QCL-TypeD source RS, as shown in Figure 17. If the SSB / CSI-RS is not set as the beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set), WD22 may assume that the reference signal used as the QCL-TypeD source reference signal in the first activated TCI state for CORESET is used as the beam detection reference signal. In the example in Figure 17, the QCL-TypeD source reference signal with the CSI-RS resource IDx (or SSB IDx) corresponding to the first activated TCI state is the beam fault detection resource set In some embodiments, a beam fault detection resource set may be included by WD22 in TIFF0007899187000015.tif6170. TIFF0007899187000016.tif6170 may include additional QCL-type D source reference signals corresponding to TCI states activated in other CORESETs (in other words, other CORESETs in the same bandwidth part and serving cell as the CORESET shown in Figure 17). Here, the first activated TCI state is identified as the first TCI state activated by the MAC CE. In an alternative embodiment, the first activated TCI state is the TCI state activated for the CORESET having the lowest TCI state ID.

[0117] In another embodiment, CORESET is activated using two TCI states (for example, via MAC CE sent to WD22 by network node 16), where each active TCI state includes a QCL-TypeD source RS, as shown in Figure 18. If the SSB / CSI-RS is not set as the beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set), WD22 may assume that the reference signal used as the QCL-TypeD source reference signal in the second activated TCI state for CORESET is used as the beam detection reference signal. In the example in Figure 18, the QCL-TypeD source reference signal with the CSI-RS resource IDy (or SSB IDy) corresponding to the second activated TCI state is used as the beam fault detection resource set In some embodiments, a beam fault detection resource set may be included by WD22 in TIFF0007899187000017.tif6170. TIFF0007899187000018.tif6170 may include an additional QCL-type D source reference signal corresponding to a TCI state activated in another CORESET (in other words, another CORESET in the same bandwidth part and serving cell as the CORESET shown in Figure 18). Here, the second activated TCI state is identified as the second TCI state activated by the MAC CE. In an alternative embodiment, the second activated TCI state is the TCI state activated for the CORESET having the highest TCI state ID.

[0118] In another embodiment, when a MAC CE (for example, transmitted to WD22 by NN16) activates two TCI states for CORESET, multiple fields in the MAC CE explicitly indicate which TCI state should be considered when determining the beam fault detection resource, namely the corresponding ID indicated as part of the MAC CE, i.e., the TCI state ID. x and TCI status IDy This indicates two activated TCI states. In that case, field C x and C y This is the TCI status ID. x and / or TCI status ID y The QCL-TypeD source associated with the set This indicates whether or not a beam fault detection resource should be included when determining the beam fault detection resource in TIFF0007899187000019.tif6170.

[0119] Embodiment 2: BFD resource determination when CORESET is configured for SFN-based PDCCH diversity - multiple BFD resource sets (one BFD resource set per TRP) In some embodiments, CORESET is activated using two TCI states (for example, via MAC CE transmitted to WD22 by NN16, for example), where each active TCI state includes a QCL-TypeD source RS, as shown in Figure 19. If the SSB / CSI-RS is not set as a beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set by NN16), WD22 may assume that the reference signal used as the QCL-TypeD source reference signal in the first activated TCI state for CORESET is used as the beam detection reference signal in the first beam fault detection resource set. Similarly, WD22 may assume that the reference signal used as the QCL-TypeD source reference signal in the second activated TCI state for CORESET is used as the beam detection reference signal in the second beam fault detection resource set.

[0120] In the example in Figure 19, the QCL type D source reference signal, accompanied by the CSI-RS resource IDx (or SSB IDx) corresponding to the first activated TCI state, is linked to the beam fault detection resource set. TIFF0007899187000020.tif5170 may include WD22. A QCL type D source reference signal with a CSI-RS resource IDy (or SSB IDy) corresponding to a second activated TCI state is included in the beam fault detection resource set TIFF0007899187000021.tif5170 may be included by WD22.

[0121] In some embodiments, beam fault detection resource set TIFF0007899187000022.tif5170 may contain additional QCL-type D source reference signals corresponding to TCI states associated with TRP1 activated in other CORESETs in the same bandwidth part and serving cell as shown in Figure 19. Similarly, beam fault detection resource sets TIFF0007899187000023.tif5170 may include an additional QCL-type D source reference signal corresponding to the TCI state associated with TRP2 activated in other CORESETs in the same bandwidth part and serving cell as the CORESET shown in Figure 19.

[0122] Here, the first and second activated TCI states are identified as the first and second TCI states activated by MAC CE, respectively. In some embodiments, the first and second activated TCI states are the TCI states activated for CORESET having the lowest and highest TCI state IDs, respectively.

[0123] In some embodiments, when a MAC CE (for example, transmitted to WD22 by NN16) activates two TCI states for CORESET, multiple fields in the MAC CE explicitly indicate which TCI states should be considered when determining the beam fault detection resource in different beam fault detection resource sets. The two activated TCI states are indicated by corresponding IDs pointed to as part of the MAC CE, namely TCI state IDx and TCI state IDy. In this case, fields Cx and Cy indicate the QCL-TypeD source associated with TCI state IDx and / or TCI state IDy, which is set TIFF0007899187000024.tif5170 or This indicates whether or not it should be included when determining the beam fault detection resources in TIFF0007899187000025.tif5170.

[0124] In some embodiments, the value Cx=0 is set when the QCL-TypeD source associated with TCI state IDx is set This indicates that when determining the beam fault detection resource in TIFF0007899187000026.tif5170, it should be included. In some embodiments, a value of Cx=1 indicates that the QCL-TypeD source associated with TCI state IDx is set This indicates that it should be included when determining the beam fault detection resources in TIFF0007899187000027.tif5170.

[0125] In some embodiments, the value Cy=0 is set when the QCL-TypeD source associated with the TCI state IDy is set This indicates that the beam fault detection resource in TIFF0007899187000028.tif5170 should be included. A value of Cy=1 indicates that the QCL-TypeD source associated with TCI state IDy is set This indicates that it should be included when determining the beam fault detection resources in TIFF0007899187000029.tif5170.

[0126] Embodiment 3: Linked CORESET is configured for non-SFN-based PDCCH repetition - BFD resource determination when configured for a single BFD resource set In some embodiments, linked PDCCH candidates, each associated with one of two TRPs, are in different search space sets associated with different CORESETs, as illustrated in Figure 20. If the SSB / CSI-RS is not set by NN16 as a beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set), WD22 may assume that the reference signal used as the QCL-type D source reference signal in activated TCI states x and y (in CORESET#1 and CORESET#2, respectively) is used as the beam detection reference signal.

[0127] In the example in Figure 20, the QCL type D source reference signal with CSI-RS resource IDx (or SSB IDx) corresponding to the activated TCI state x (for CORESET#1), and the QCL type D source reference signal with CSI-RS resource IDy (or SSB IDy) corresponding to the activated TCI state y (for CORESET#2) are used in the beam fault detection resource set. In some embodiments, a beam fault detection resource set may be included by WD22 in TIFF0007899187000030.tif6170. TIFF0007899187000031.tif6170 may include additional QCL-type D source reference signals corresponding to TCI states activated in other CORESETs in the same bandwidth part and serving cell as CORESET #1 and #2 shown in Figure 20.

[0128] In some embodiments, linked PDCCH candidates, each associated with one of two TRPs, are in different search space sets associated with different CORESETs, as illustrated in Figure 21. If the SSB / CSI-RS is not set by NN16 as the beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set), WD22 may assume that the reference signal used as the QCL-type D source reference signal in the activated TCI state x (in the first linked CORESET #1) is used as the beam fault detection reference signal. In some embodiments, the first linked CORESET may be defined as the CORESET with the lowest CORESET ID among the two linked CORESETs. In the example in Figure 21, the QCL-type D source reference signal with the CSI-RS resource ID x (or SSB ID x) corresponding to the activated TCI state x (for CORESET #1) is used as the beam fault detection resource set In some embodiments, the beam fault detection resource set will be included by WD22 in TIFF0007899187000032.tif6170. TIFF0007899187000033.tif6170 may include additional QCL-type D source reference signals corresponding to TCI states activated in other CORESETs in the same bandwidth part and serving cell as CORESET#1 shown in Figure 21.

[0129] In some embodiments, linked PDCCH candidates, each associated with one of two TRPs, are in different search space sets associated with different CORESETs, as illustrated in Figure 22. If the SSB / CSI-RS is not set as the beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set by NN16), then WD22 may assume that the reference signal used as the QCL-type D source reference signal in the activated TCI state x (in the last linked CORESET #1) is used as the beam fault detection reference signal. In some embodiments, the last linked CORESET may be defined as the CORESET with the highest CORESET ID among the two linked CORESETs. In the example in Figure 22, the QCL-type D source reference signal with the CSI-RS resource IDy (or SSB IDy) corresponding to the activated TCI state y (for CORESET #2) is used as the beam fault detection resource set In some embodiments, a beam fault detection resource set may be included by WD22 in TIFF0007899187000034.tif6170. TIFF0007899187000035.tif6170 may include additional QCL-type D source reference signals corresponding to TCI states activated in other CORESETs in the same bandwidth part and serving cell as CORESET#2 shown in Figure 22.

[0130] Embodiment 4: BFD Resource Determination When a Linked CORESET is Configured for Non-SFN-Based PDCCH Repetitive - Multiple BFD Resource Sets (One BFD Resource Set per TRP) In this embodiment, linked PDCCH candidates, each associated with one of two TRPs, are in different search space sets associated with different CORESETs, as shown in the exemplary diagram of Figure 23.

[0131] If the SSB / CSI-RS is not set as the beam fault detection reference signal (in other words, the beam fault detection reference signal is not explicitly set by NN16), WD22 may assume that the reference signal used as the QCL-type D source reference signal in the activated TCI state x (in the first linked CORESET #1) is used as the beam detection reference signal in the first beam fault detection resource set. In some embodiments, the first linked CORESET may be defined as the CORESET with the lowest CORESET ID among the two linked CORESETs. In the example in Figure 23, the QCL-type D source reference signal with the CSI-RS resource ID x (or SSB ID x) corresponding to the activated TCI state x is used as the beam fault detection resource set TIFF0007899187000036.tif5170 may be included by WD22.

[0132] Similarly, WD22 may assume that the reference signal used as the QCL-type D source reference signal in the activated TCI state y (in the last linked CORESET #2) is used as the beam detection reference signal in the second beam fault detection resource set. In some embodiments, the last linked CORESET may be defined as the CORESET with the largest CORESET ID among the two linked CORESETs. In the example in Figure 23, the QCL-type D source reference signal with the CSI-RS resource IDy (or SSB IDy) corresponding to the activated TCI state y is used as the beam fault detection resource set TIFF0007899187000037.tif5170 may be included by WD22.

[0133] Several further exemplary embodiments are described below. One or more of the following exemplary methods may be implemented by the network node 16 and / or WD22 and / or host computer 24.

[0134] Embodiment 1: 1. A method for determining beam fault detection resources, wherein the method is a. Set CORESET and activate the two TCI states via MAC CE, b. Determine the reference signal used as the QCL-type D source reference signal in at least one of the two activated TCI states for CORESET as the beam fault detection reference signal, c. Include a determined beam fault detection reference signal in a single beam fault detection resource set. A method comprising one or more of the following. 2. The method of 1 (of Embodiment 1), wherein the reference signal used as the QCL-type D source reference signal in both of the two activated TCI states for CORESET is determined as the beam fault detection reference signal. 3. The method of 1 (of Embodiment 1), wherein the reference signal used as the QCL-type D source reference signal in the first of two activated TCI states for CORESET is determined as the beam fault detection reference signal. 4. The method of 1 (of Embodiment 1), wherein the reference signal used as the QCL-type D source reference signal in the second of the two activated TCI states for CORESET is determined as the beam fault detection reference signal. 5. The method according to any one of 1 to 4 (of Embodiment 1), wherein a beam fault detection reference signal in a single beam fault detection resource set is used by the WD22 to detect a beam fault.

[0135] Embodiment 2: 1. A method for determining beam fault detection resources, wherein the method is a. Set CORESET and activate the two TCI states via MAC CE, b. Determine the reference signal used as the QCL-type D source reference signal in at least one of the two activated TCI states for CORESET as the beam fault detection reference signal, c. In two different beam fault detection resource sets corresponding to the first TRP and the second TRP, the determined beam fault detection reference signal is included. A method comprising one or more of the following. 2. The method according to (Embodiment 2), wherein a reference signal used as the QCL-type D source reference signal in the first of two activated TCI states for CORESET is determined to be the beam fault detection reference signal and is included in the first beam fault detection resource set. 3. The method according to (Embodiment 2) wherein a reference signal used as the QCL-type D source reference signal in the second of two activated TCI states for CORESET is determined to be the beam fault detection reference signal and is included in the second beam fault detection resource set. 4. The method according to any one of 1 to 3 (of Embodiment 2), wherein a beam fault detection reference signal in the first beam fault detection resource set is used by the WD22 to detect a beam fault corresponding to the first TRP. 5. The method according to any one of 1 to 3 (of Embodiment 2), wherein a beam fault detection reference signal in a second beam fault detection resource set is used by the WD22 to detect a beam fault corresponding to a second TRP.

[0136] Embodiment 3: 1. A method for determining beam fault detection resources, wherein the method is a. Set up two linked CORESETs and activate one TCI state via MAC CE for each CORESET, b. Determine the reference signal used as the QCL-type D source reference signal in at least one of the two activated TCI states corresponding to the two linked CORESETs as the beam fault detection reference signal, c. Include a determined beam fault detection reference signal in a single beam fault detection resource set. A method comprising one or more of the following. 2. The method according to (Embodiment 3), wherein the reference signal used as the QCL-Type D source reference signal in both of the two activated TCI states for the two linked CORESETs is determined as the beam fault detection reference signal. 3. The method of 1 (of Embodiment 3), wherein a reference signal used as the QCL-type D source reference signal in the first activated TCI state for the first of two linked CORESETs is determined as the beam fault detection reference signal. 4. The method of 1 (of Embodiment 3), wherein the reference signal used as the QCL-type D source reference signal in the second activated TCI state for the second of two linked CORESETs is determined as the beam fault detection reference signal. 5. The method according to any one of 1 to 4 (of Embodiment 3), wherein a beam fault detection reference signal in a single beam fault detection resource set is used by the WD22 to detect a beam fault.

[0137] Embodiment 4: 1. A method for determining beam fault detection resources, wherein the method is a. Set up two linked CORESETs and activate one TCI state via MAC CE for each CORESET, b. Determine the reference signal used as the QCL-type D source reference signal in at least one of the two activated TCI states corresponding to the two linked CORESETs as the beam fault detection reference signal, c. In two different beam fault detection resource sets corresponding to the first TRP and the second TRP, the determined beam fault detection reference signal is included. A method comprising one or more of the following. 2. The method of 1 (in Embodiment 4), wherein a reference signal used as the QCL-type D source reference signal in the first activated TCI state for the first of two linked CORESETs is determined as the beam fault detection reference signal. 3. The method of 1 (in Embodiment 4), wherein the reference signal used as the QCL-type D source reference signal in the second activated TCI state for the second of two linked CORESETs is determined as the beam fault detection reference signal. 4. The method according to any one of 1 to 3 (of Embodiment 4), wherein a beam fault detection reference signal in the first beam fault detection resource set is used by the WD22 to detect a beam fault corresponding to the first TRP. 5. The method according to any one of 1 to 3 (of Embodiment 4), wherein a beam fault detection reference signal in a second beam fault detection resource set is used by the WD22 to detect a beam fault corresponding to a second TRP.

[0138] Some further embodiments may include one or more of the following: Embodiment A1. A network node configured to communicate with a wireless device (WD), wherein the network node is Configure at least one Control Resource Set (CORESET) and activate at least one Transmit Configuration (TCI) state, Determine at least one reference signal (RS) as a pseudo-collocation (QCL) type D source in at least one TCI state for at least one CORESET as at least one beam fault detection RS (BFD-RS), The determination to include at least one BFD-RS in at least one beam fault resource set and A network node having a wireless interface configured to perform one or more of the following, and / or having processing circuitry configured to do so.

[0139] Embodiment A2. A network node and / or a wireless interface and / or processing circuit, Setting one CORESET and activating two TCI states via the Media Access Control (MAC) control element (CE), The first beam-fault resource set and the second beam-fault resource set include at least one determined BFD-RS, wherein the first beam-fault resource set includes at least one determined BFD-RS corresponding to a first transmit / receive point (TRP), and the second beam-fault resource set includes at least one determined BFD-RS corresponding to a second TRP. A network node according to Embodiment A1, configured to perform one or more of the following:

[0140] Embodiment A3. A network node and / or a wireless interface and / or processing circuit, This involves setting up two CORESETs and activating one TCI state for each of the two CORESETs via a Media Access Control (MAC) control element (CE), The determination to include at least one BFD-RS in a single beam fault resource set and A network node according to Embodiment A1, configured to perform one or more of the following:

[0141] Embodiment B1. A method implemented in a network node, wherein the method is Configure at least one Control Resource Set (CORESET) and activate at least one Transmit Configuration (TCI) state, Determine at least one reference signal (RS) as a pseudo-collocation (QCL) type D source in at least one TCI state for at least one CORESET as at least one beam fault detection RS (BFD-RS), The determination to include at least one BFD-RS in at least one beam fault resource set and A method comprising one or more of the following.

[0142] Embodiment B2. Setting, Activating and Including Setting one CORESET and activating two TCI states via the Media Access Control (MAC) control element (CE), The first beam-fault resource set and the second beam-fault resource set include at least determined BFD-RS, wherein the first beam-fault resource set corresponds to a first transmit / receive point (TRP), and the second beam-fault resource set corresponds to a second TRP, and the BFD-RS includes at least determined BFD-RS. The method of Embodiment B1, further comprising one or more of the above.

[0143] Embodiment B3. Setting, Activating and Including, This involves setting up two CORESETs and activating one TCI state for each of the two CORESETs via a Media Access Control (MAC) control element (CE), The determination to include at least one BFD-RS in a single beam fault resource set and The method of Embodiment B1, further comprising one or more of the above.

[0144] Embodiment C1. A wireless device (WD) configured to communicate with a network node, wherein the WD is Receiving the configuration of at least one control resource set (CORESET) and the activation of at least one transmit configuration (TCI) state, To determine at least one beam fault detection reference signal (BFD-RS) in at least one beam fault resource set and A wireless device (WD) comprising a wireless interface and / or processing circuit configured to perform one or more of the following:

[0145] Embodiment C2. The WD and / or wireless interface and / or processing circuit are: Receiving one CORESET setting and two TCI state activations via the Media Access Control (MAC) control element (CE), Determining at least one BFD-RS in a first beam-fault resource set and a second beam-fault resource set, wherein the first beam-fault resource set corresponds to a first transmit / receive point (TRP) and the second beam-fault resource set corresponds to a second TRP. The WD according to embodiment C1, configured to perform one or more of the following.

[0146] Embodiment C3. A network node and / or a wireless interface and / or processing circuit, For each of the two CORESETs, the system receives the configuration of both CORESETs and the activation of one TCI state via a Media Access Control (MAC) control element (CE), To determine at least one BFD-RS in a single beam fault resource set and The WD according to embodiment C1, configured to perform one or more of the following.

[0147] Embodiment D1. A method implemented in a wireless device (WD), wherein the method is Receiving the configuration of at least one control resource set (CORESET) and the activation of at least one transmit configuration (TCI) state, To determine at least one beam fault detection reference signal (BFD-RS) in at least one beam fault resource set and A method comprising one or more of the following.

[0148] Embodiment D2. Receiving settings, receiving and determining activations, Receiving one CORESET setting and two TCI state activations via the Media Access Control (MAC) control element (CE), Determining at least one BFD-RS in a first beam-fault resource set and a second beam-fault resource set, wherein the first beam-fault resource set corresponds to a first transmit / receive point (TRP) and the second beam-fault resource set corresponds to a second TRP. The method according to embodiment D1, further comprising one or more of the above.

[0149] Embodiment D3. Receiving settings, receiving activation and determining, For each of the two CORESETs, the system receives the configuration of both CORESETs and the activation of one TCI state via a Media Access Control (MAC) control element (CE), To determine at least one BFD-RS in a single beam fault resource set and The method according to embodiment D1, further comprising one or more of the above.

[0150] As will be understood by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Accordingly, the concepts described herein may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware embodiments, all of which are generally referred to herein as “circuits” or “modules.” Any process, step, action, and / or functionality described herein may be performed by and / or associated with a corresponding module, and the module may be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure may take the form of computer program products on tangible computer-readable storage media having computer program code embodied in a medium that can be executed by a computer. Any suitable tangible computer-readable medium may be used, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0151] Several embodiments have been described herein with reference to flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each block in a flowchart and / or block diagram, as well as combinations of blocks in a flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a dedicated computer, or other programmable data processing device (thereby creating a dedicated computer) to create a machine, thereby creating means for implementing functions / actions specified in one or more blocks of a flowchart and / or block diagram by the instructions executed via the processor of the computer or other programmable data processing device.

[0152] These computer program instructions may also be stored in computer-readable memory or storage medium that can be instructed to function in a particular manner, thereby producing a product that includes instruction means for implementing functions / actions specified in one or more blocks of a flowchart and / or block diagram.

[0153] Computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device, thereby creating a computer-implemented process, in which the instructions executed on the computer or other programmable device provide steps for implementing a function / action specified in one or more blocks of a flowchart and / or block diagram.

[0154] Please understand that the functions / actions described within a block may occur in an order other than that shown in the example of action. For example, depending on the functions / actions involved, two blocks shown consecutively may, in effect, be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Some of the diagrams include arrows on the communication path to indicate the primary direction of communication, but please understand that communication may occur in the opposite direction to the depicted arrow.

[0155] Computer program code for performing the operations of the concepts described herein may be written in an object-oriented programming language such as Java® or C++. However, computer program code for performing the operations of the disclosure may also be written in a conventional procedural programming language such as the C programming language. The program code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer may be connected to the user's computer via a local area network (LAN) or wide area network (WAN), or the connection may be to an external computer (for example, via the Internet using an Internet service provider).

[0156] Many different embodiments have been described herein in connection with the above description and drawings. It will be understood that a literal description and illustration of every combination and subcombination of these embodiments would be overly repetitive and obscure. Therefore, all embodiments may be combined in any way and / or combination, and this specification, including the drawings, shall be construed as constituting a fully written description of all combinations and subcombinations of the embodiments described herein, as well as the modes and processes of manufacturing and using them, and shall support any rights to any such combination or subcombination.

[0157] It will be understood by those skilled in the art that the embodiments described herein are not limited to those shown and described in detail above. Additionally, it should be noted that all accompanying drawings are not to a constant scale unless otherwise stated above. Various modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. A method in a network node (16) configured to communicate with a wireless device (WD) (22), wherein the method is: Setting two control resource sets (CORESET) in the aforementioned WD (22) (S144), The first transmit setting indicator (TCI) state and the second transmit setting indicator (TCI) state are activated for each of the two CORESETs (S146), Determining at least one beam fault detection (BFD) resource set (S148), wherein each of the at least one BFD resource set includes at least one BFD reference signal (BFD-RS), and one BFD-RS is a reference signal associated with one of a first activated TCI state and a second activated TCI state for both of the two CORESETs. A method that includes [a certain feature].

2. The method according to claim 1, wherein the reference signal associated with the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal.

3. The method according to claim 1 or 2, wherein the at least one BFD resource set comprises a first BFD resource set including a first BFD-RS which is a reference signal associated with the first activated TCI state and a second BFD-RS which is a reference signal associated with the second activated TCI state.

4. The method according to any one of claims 1 to 3, wherein the first BFD resource set comprises a pseudo-collocation (QCL) type D reference signal associated with the first activated TCI state.

5. The method according to any one of claims 1 to 4, wherein the second BFD resource set comprises a pseudo-collocation (QCL) type D reference signal associated with the second activated TCI state.

6. A network node (16) configured to communicate with a wireless device (WD) (22), wherein the network node (16) The WD (22) is configured with two control resource sets (CORESET), To activate the first Transmit Setting Indicator (TCI) state and the second Transmit Setting Indicator (TCI) state for each of the two CORESETs, Determining at least one beam fault detection (BFD) resource set, wherein each of the at least one BFD resource set includes at least one BFD reference signal (BFD-RS), and one BFD-RS is a reference signal associated with one of a first activated TCI state and a second activated TCI state for both of the two CORESETs. A network node (16) is provided with a processing circuit (68) configured to perform the following.

7. The network node (16) according to claim 6, wherein the processing circuit (68) is further configured to perform the method described in any one of claims 2 to 5.

8. A method in which a wireless device (WD) (22) configured to communicate with a network node (16) is, The configuration of two control resource sets (CORESETs) and the reception of instructions to activate the first transmit setting indicator (TCI) state and the second transmit setting indicator (TCI) state for each of the two CORESETs (S150), Determining at least one BFD reference signal (BFD-RS) in at least one beam fault detection (BFD) resource set (S152), wherein each of the at least one BFD-RS is a pseudo-collocation (QCL) type D reference signal associated with one of a first activated TCI state and a second activated TCI state for both of the two CORESETs (S152) A method that includes [a certain feature].

9. The method according to claim 8, wherein the reference signal associated with the first and second activated TCI states is a pseudo-collocation (QCL) type D reference signal.

10. The method according to claim 8 or 9, wherein the at least one BFD resource set comprises a first BFD resource set including a first BFD-RS which is a reference signal associated with the first activated TCI state and a second BFD-RS which is a reference signal associated with the second activated TCI state.

11. A wireless device (WD) (22) configured to communicate with a network node (16), wherein the WD (22) is A wireless interface (82) configured to receive the settings of two control resource sets (CORESETs) and instructions to activate a first transmit setting indicator (TCI) state and instructions to activate a second transmit setting indicator (TCI) state for each of the two CORESETs, A processing circuit (84) that communicates with the wireless interface (82), which determines at least one BFD reference signal (BFD-RS) in at least one beam fault detection (BFD) resource set, and each of the at least one BFD-RS is a pseudo-collocation (QCL) type D reference signal associated with one of a first activated TCI state and a second activated TCI state for both of the two CORESETs, and A wireless device (WD) (22) comprising the above.

12. The wireless device (WD) (22) according to claim 11, wherein the processing circuit (84) is further configured to perform the method described in claim 9 or 10.

13. A computer program that causes a processing circuit (70) of a network node (16) to execute the method described in any one of claims 1 to 5.

14. A computer program that causes a processing circuit (86) of a wireless device (WD) (22) to perform the method described in any one of claims 8 to 10.

Images