Transmission configuration indicator state configuration for asymmetric multiple transmission reception point deployment

Abstract

A method, network node and user equipment (UE) for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment are disclosed. According to one aspect, a method in a UE includes receiving a configuration of a plurality of transmission configuration indicator (TCI) states. The method includes applying a first number of the plurality of TCI states associated with uplink communications and applying a second number of the plurality of TCI states associated with downlink communications. The first number of applied TCI states may be different from the second number of applied TCI states. The method nay also include transmitting and receiving signals using UL and DL communication properties associated with respective applied TCI states.

Description

[0001]TRANSMISSION CONFIGURATION INDICATOR STATE CONFIGURATION FOR ASYMMETRIC MULTIPLE TRANSMISSION RECEPTION POINT DEPLOYMENT TECHNICAL FIELD The present disclosure relates to wireless communications, and in particular, to transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment. BACKGROUND The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks. NR Data scheduling in NR is typically on a per slot basis. An example is shown in FIG.1 with a 14-symbol slot, where the first two symbols contain a physical downlink control channel (PDCCH) and the remaining symbols contain a physical shared data channel, either PDSCH (physical downlink shared channel) or PUSCH (physical uplink shared channel). Downlink transmissions may be dynamically scheduled on a slot-by-slot basis. The scheduling information such as resource allocation and modulation order is contained in downlink control information (DCI) carried by the PDCCH. Downlink (DL) user data is carried in the PDSCH. Uplink data transmission may also be dynamically scheduled using DCI carried in PDCCH. A UE first decodes uplink grants in DCI and then transmits data in PUSCH based at least in part on the scheduling information in the uplink (UL) grant. In addition to dynamic scheduling of PUSCH, semi-persistent transmission of periodic PUSCH using configured grants (CG) is also supported in NR. In CG type 1, the periodicity, as well as a slot offset, are configured by radio resource control (RRC) signaling. In CG type 2, the PUSCH transmission may be activated or deactivated dynamically by DCI. For channel estimation purposes, channel state information reference signals, CSI-RS in the DL, and sounding reference signals (SRS) in the UL, are also supported. Synchronization signals (SS), primary SS (PSS) and secondary SS (SSS), are used in NR to allow a UE to acquire DL synchronization to a cell and the physical cell ID (PCI) associated to a cell. PSS and SSS are transmitted together with the physical broadcast channel (PBCH), referred to a SS / PBCH block or SSB in short. is used to transmit some information that includes master information block (MIB) in a cell for a UE to acquire system information from other system information blocks (SIBs). Uplink power control in NR The gNB (network node) may consist of a single transmission and reception point (TRP) or multiple TRPs. In case of multiple TRPs, a UE may be scheduled with downlink transmissions from one or more of the TRPs and uplink data transmission to one or more of the TRPs, either one TRP at a time or simultaneously. Uplink power control in NR consists of two parts, i.e., open-loop power control closed-loop power control. Open-loop power control is used to set the uplink transmit power based on a few factors such as pathloss estimation between the UE and a TRP in a serving cell, the target receive power, channel / signal bandwidth, modulation and coding scheme (MCS), fractional power control factor (also known as the fractional compensation factor), etc. Closed-loop power control is based on power adjustments signaled in power control commands received from the network node. The power control commands are typically determined based on the difference between the actual received power and a received power at the network node. Up to two closed power control loops may be configured in NR for each UL channel or signal. Either cumulative or non-cumulative closed-loop power adjustments are supported in NR. A closed loop adjustment at a given time is also referred as a power control adjustment state. A DL reference signal (RS) is transmitted from each TRP, which may be used a UE to estimate the pathloss between the UE and the TRP. Each DL RS has an associated index for identifying it. For UL transmission, power control may be performed separately for each TRP. For an UL channel or signal (e.g., PUSCH, physical uplink control channel (PUCCH), or SRS) to be transmitted in the uplink (UL) associated with a pathloss RS with index ^^, the transmit power in a transmission occasion i within a slot in a bandwidth part (BWP) of a carrier frequency of a serving cell and a closed-loop index^^ ^^^ ൌ 0,1^ may be expressed as:^^ ^^, ^^ ൌ min ^ ^ெ^^,^,^^^^^^^^^, ^ ^^^^^^^ି^^^^^^^, ^^^ ^ ^^^^^^^ௗି^^^^^^^, ^^^where ^^^ெ^^,^,^^^^^ is a UE’s maximum output power for the carrier frequency, ^^, of the serving cell, ^^, in transmission occasion ^^ for the UL channel or signal.^^^^^^ି^^^^^^^, ^^^ is the open loop transmit power and ^^^^^^^ௗି^^^^^^^, ^^^ is the closed loopadjustment. ^^^^^^ି^^^^^^^, ^^^ is given by:^^^^^^ି^^^^^^^, ^^^ ൌ ^^ை ^ ^^ோ^^^^^ ^ ^^^^^^^^^^ ^ ∆^^^^where ^^ைis the nominal target receive power for the UL channel or signal and comprises a cell specific part ^^ை,^^^^and a UE specific part ^^ை,^ா, ^^ோ^^^^^is a power adjustment to the bandwidth or number of resource blocks (RBs) occupied by the channel or signal at transmission occasion ^^, ^^^^^^^^ is a pathloss (PL) estimation based on adownlink reference signal (RS) with index ^^, ^^ ^0 ^ ^^ ^ 1^ is a fractional pathlosscompensation factor, and ∆^^^^is a power offset determined by modulation and code rate of the UL channel or signal. ^^^^^^^ௗି^^^^^^^, ^^^ is given by:ெ^^ ^^^^^^^ௗି^^^^^^^ െ ^^ , ^^^ ^ ^ ^^^^^, ^^^ ; if cumulation is enabled^^ௗି^^^^^^^ ^ ^^^^ , ^^ ൌ ^^ୀ^ ^^^^^, ^^^; if cumulation is disabled ^i. e. , absolute is enable^where ^^^^^, ^^^ is a power adjustment value indicated in a transmit power control (TPC)command in a DCI associated with the UL channel or signal at transmission occasion ^^and configured with closed-loop index ^^; ∑ெ^ୀ^ ^^^^^, ^^^ is a sum of power adjustmentvalues indicated in TPC commands that the UE received for the channel or signal sincethe TPC command for transmission occasion ^^ െ ^^^.Note that power control parameters ^^ை, ^^ோ^^^^^, ^^, ^^^^, ∆^^^^, ^^^^^, ^^^ are generallyseparately for each UL channel or signal (e.g., PUSCH, PUCCH, and SRS) and may be different for different UL channels or signals. UE panel For UEs, the signals may arrive and emanate from all different directions. Hence, is beneficial to have an antenna implementation at the UE which has the possibility to generate omni-directional-like coverage in addition to the high gain narrow beams. One way to increase the omni-directional coverage at a UE is to install multiple panels, and point the panels in different directions, which typically is the case for commercial UEs. However, in order to reduce the cost and energy consumption, these UEs may only transmit from one UE panel at each time instance. FIG.2 illustrates one example of a realistic UE with two baseband chains per polarization) which are used to switch between three different dual-polarized panels. SRS In NR, the SRS is used for providing channel state information (CSI) to the node in the UL. The usage of SRS includes, e.g., deriving the appropriate transmission / reception beams and / or to perform link adaptation (i.e., setting the transmission rank and the MCS), and for selecting DL (e.g., for PDSCH transmissions) and UL (e.g., for PUSCH transmissions) multiple input multiple output (MIMO) In LTE and NR, the SRS is configured via RRC, where parts of the configuration may be updated (for reduced latency) through medium access control-control element (MAC-CE) signaling. The configuration includes, for example, the SRS resource allocation (the physical mapping and the sequence to use) as well as the time-domain (aperiodic, semi-persistent, or periodic). For aperiodic SRS transmissions, the RRC configuration does not activate an SRS transmission from the UE but instead, a dynamic activation trigger is transmitted from the network node in the DL, via the DCI in the PDCCH. The dynamic activation trigger instructs the UE to transmit the SRS at a predetermined time. When configuring SRS transmissions, the network node configures, through the SRS-Config information element (IE), a set of SRS resources and a set of SRS resource sets, where each SRS resource set contains one or more SRS resources. and TCI states In NR, several signals may be transmitted from different antenna ports of a same base station. These signals may have the same large-scale properties such as Doppler shift / spread, average delay spread, or average delay. These antenna ports are then said to be quasi co-located (QCL). If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the UE may estimate that parameter based on one of the antenna ports and apply that estimate for receiving signals on the other antenna port. For example, there may be a QCL relation between a CSI-RS for tracking RS (TRS) and the PDSCH demodulation reference signals (DMRS). When the UE receives the PDSCH DMRS, it may use the measurements already made on the TRS to assist the DMRS reception. Information about what may be made regarding QCL is signaled to the UE from the network. In NR, four of QCL relations between a transmitted source RS and transmitted target reference signal (RS) were defined: Type A: {Doppler shift, Doppler spread, average delay, delay spread}; Type B: {Doppler shift, Doppler spread}; Type C: {average delay, Doppler shift}; and Type D: {Spatial Rx parameter}. QCL type D was introduced to facilitate beam management with analog beamforming and is known as spatial QCL. There is currently no strict definition of QCL, but the understanding is that if two transmitted antenna ports are spatially QCL, the UE may use the same receive (RX) beam to receive them. This is helpful for a UE that uses analog beamforming to receive signals, since the UE needs to adjust its RX beam in some direction prior to receiving a certain signal. If the UE knows that the signal is spatially QCL with some other signal it has received earlier, then it may safely the same RX beam to receive also this signal. Note that for beam management, the discussion mostly revolves around QCL Type D, but it is also necessary to convey a Type A QCL relation for the RSs to the UE, so that it may estimate all the relevant large-scale parameters. To introduce dynamics in beam and transmission / reception point (TRP) selection, the UE may be configured through RRC signaling with up to 128 TCI (Transmission Configuration Indicator) states. The TCI state information element is shown below: TCI-State ::= SEQUENCE { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info ... } QCL-Info ::= SEQUENCE { cell ServCellIndex bwp-Id BWP-Id referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index typeD}, UE that it The field being used in the DCI is Transmission configuration indication, which is 3 bits if tci- PresentInDCI is “enabled”or tci-PresentForDCI-Format1-2-r16 is present respectively for DCI format 1_1 and DCI 1_2 by higher layer. TCI state In 3GPP Technical Release 17 (3GPP Rel-17), a new unified TCI state framework is specified, which aims to streamline the indication of transmit / receive spatial filter (and other QCL properties) to the UE by letting a single TCI state indicate QCL properties for multiple different DL and / or UL signals / channels. The unified TCI state framework of 3GPP Rel-17 may be RRC configured in one of two modes of operation “Joint DL / UL TCI” or “Separate DL / UL TCI”. For “Joint DL / UL TCI” operation, one common Joint TCI state is used for both DL and UL signals / channels. For “Separate DL / UL TCI” operation, one common DL-only TCI state is used for DL and one common UL-only TCI state is used for UL signals / channels. MIMOParam-r17 ::= SEQUENCE { additionalPCI-ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, - Need N additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, -- Need N unifiedTCI-StateType-r17 ENUMERATED {separate, joint} -- Need R uplink-PowerControlToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI- r17)) OF Uplink-powerControl-r17 OPTIONAL, -- Need N uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI- r17)) OF Uplink-powerControlId-r17 OPTIONAL, -- Need N sfnSchemePDCCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL, -- Need R sfnSchemePDSCH-r17 ENUMERATED use in “Separate DL / UL TCI” operation, up to two TCI states may be activated per TCI codepoint, one for DL signals / channels (DL-only TCI state) and one for UL signals / channels (UL-only TCI state). One schematic example of how this may look is in FIG. 4. In case the TCI codepoint is “0”, the UE should apply “DL-only TCI state 3” as common QCL source for DL signals / channels, and not update the QCL source for UL signal channels. In case the TCI codepoint is “7”, the UE should apply “UL-only TCI state 57” as QCL source for UL signals / channels, and not update the QCL source for DL signals / channel. In case the TCI codepoint is “2”, the UE should apply only TCI state 9” as QCL source for DL signals / channels and apply “UL-only TCI state 1” as QCL source for UL signals / channels. The existing DCI formats 1_1 and 1_2 in NR are reused (as in 3GPP Rel-15 / 16 beam management framework) for beam indication, both with and without DL UL-only nodes It is expected that the demand on capacity and user throughput will increase in the future. It is also expected that UL will become a limiting factor, partly due to the natural of spectral efficiency between UL and DL (which may arise from different numbers of antennas, different power levels, etc., but also partly due to an increase of UL heavy services like gaming, vehicle to vehicle (V2V) communication, etc.) A potential remedy to this is to densify the networks more in the UL than in the DL. This may be done by for instance providing radio nodes that only receive in the UL hence, do not perform any DL transmissions). Such a transmission node may be referred to herein as an “UL-only node / TRP”. By using such UL-only nodes, one may consequently enhance the UL without enhancing the DL. While there is no direct improvement in downlink performance, as compared to normal DL+UL nodes, benefits of UL-only nodes include lower complexity, lower weight, smaller volumes, ease of deployment and avoiding the need for permits to deploy radio transmitters. A first step to better support UL-only nodes has been included in the NR MIMO 3GPP Rel-19 work item description (WID), where the power control for FR1 and FR2 will be enhanced to better support UL-only nodes. In the 3GPP Rel-19 MIMO WID, the following objective is included: Specify enhancement for asymmetric DL sTRP / UL mTRP deployment scenarios, assuming intra-band intra-DU non-co-located mTRP scenarios, without changing existing cell definition or defining a new cell (e.g., UL-only cell), assuming the 3GPP Rel-17 / 18 unified TCI framework and fully reusing the legacy QCL / UL spatial relation rules, targeting FR1 and FR2; and two closed-loop PC adjustment states for SRS, both separate from PUSCH; and pathloss offset configurations for pathloss calculation to UL TRP(s), when the pathloss RS is from DL sTRP. In the RAN1#116 meeting, the following agreements on association between TCI state and pathloss offset for pathloss calculation to UL TRP were achieved: Agreement For the asymmetric DL sTRP / UL mTRP deployment scenarios, support to associate an UL TCI state with a pathloss (PL) offset: ^ When a UL TCI state associated with a PL offset is applied for the PUSCH / PUCCH / SRS transmission, the UE calculates the transmit (TX) power of the PUSCH / PUCCH / SRS based on the DL PL RS and PL offset associated with this UL TCI state: o Reuse the legacy uplink power control formulation by replacing legacy PL with UL PL which is derived from the DL PL RS and the PL offset; o For Further Study (FFS): The UE may update UL PL in a way that new UL PL = current UL PL + an update delta indicated by the network (NW); ^ Note: it does not intend to increase the number of maintained PLs per cell; and ^ FFS: whether to support associating joint TCI state (if supported) with a PL offset. Further study includes whether / how to apply a PL offset on PDCCH-order physical random access channel (PRACH) transmission: ^ FFS: how to determine the TX beam of PRACH towards UL TRP; ns ^ Note: this does not imply to support 2 TA for single-DCI based system. Agreement For the asymmetric DL sTRP / UL mTRP deployment scenarios, separate DL / UL TCI state mode of 3GPP Rel-17 / 18 unified TCI framework may be configured for both FR1 and FR2. Joint TCI state mode may be configured at least for FR1. In this disclosure, the terms UL- node, UL-only TRP, and UL-only RP may be used interchangeably. In existing NR multi-TRP operation, it is assumed that each node may be used for both DL transmission and UL reception. For NR 3GPP Rel-19, the idea of deploying UL- only nodes in a cell has been considered. UL-only nodes may be useful in the following scenarios: ^ UL-only nodes deployed at the cell edge to provide better UL coverage for cell edge UEs; ^ UL-only node deployed in a time division duplex (TDD) band where there is dominant UL allocation; and ^ UL-only node deployed in a band that may only be used for UL transmission due to regulatory issues. An UL-only node receives only and does not transmit any DL signals. However, one issue with enabling UL-only node operation is UL power control for UL transmissions to those nodes. In NR, UL power control is based on the DL pathloss (e.g., based on the pathloss computed from a DL path loss reference signal (PL-RS) computation at the UE. Without DL RS (e.g., DL PL-RS) transmission available from a UL-only node, pathloss cannot be estimated in the current framework to determine the UL power control for the UL-only node. In the RAN1116 meeting, it was considered that the pathloss offset is associated to the UL TCI state, and that both “Separate DL / UL TCI” and “Joint DL / UL TCI” (at least for FR1) are supported for asymmetric DL sTRP UL mTRP scenarios. The legacy (normal) TRPs provides both DL and UL service. Hence, in legacy NR, both for “Separate DL / UL TCI” and “Joint DL / UL TCI”, each UE may only be indicated with as many TCI states used for DL as are used for UL. For single TRP operation, one Joint TCI state or one DL TCI state and one UL TCI state may be indicated, and for multi TRP operation, either two Joint TCI states, or two DL TCI state and two UL TCI states may be indicated. However, for UL-only nodes deployment where one might operate in single TRP DL and multi-TRP UL communication, one may want to have a single TCI state indicated for DL and two TCI states indicated for UL. However, this is not possible with the legacy NR unified TCI state framework. SUMMARY Some embodiments advantageously provide methods, network nodes and user equipments for transmission indicator (TCI) state configuration for asymmetric multiple transmission point (MTRP) deployment. Some embodiments include methods to support UL-only node deployments for the NR unified TCI state framework (or similar new TCI state framework in 6G), where a Joint TCI state is indicated to a UE to perform DL and UL communication with an TRP, and an UL TCI state is indicated to the UE to perform UL communication to an UL-only node. The methods described herein enable the network to reduce signaling overhead and enable efficient configuration and indication for TCI states used in the asymmetric DL UL mTRP scenarios. Some methods are beneficial for other operations where the number of TRPs with DL communication differs from the number of TRPs for UL communications or for operations where either UL only TRP(s) or DL only TRP(s), or both, exist. Some embodiments enable D-MIMO communication in 6G where different sets of might be used for DL compared to UL, which enables a more flexible D-MIMO communication. According to one aspect, a method in a network node includes configuring the UE with a plurality of transmission configuration indicator, TCI, states, a first number of TCI of the plurality of TCI states to be applied to UL communication and a second number of TCI states of the plurality of TCI states to be applied to DL communications, the first and second numbers being indicated by a plurality of codepoints. In some embodiments, the first number of TCI states is not equal to the second of TCI states. In some embodiments, the method includes activating the plurality of TCI states via a medium access control, MAC, control element, CE, message. In some embodiments, the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the TCI state configuration is indicated by radio resource control, RRC, signaling. In some the TCI state configuration configures the UE to assume a same quasi co- location, QCL, property for two joint TCI states. In some embodiments, the TCI state configuration configures the UE to apply a joint TCI state for UL and DL communications and at least one of an UL TCI state for UL communications and a DL TCI state for DL communications. In some embodiments, the TCI state configuration configures the UE with a list of joint TCI states, UL TCI states and DL TCI states. In some embodiments, the method includes receiving a pathloss offset from the network node and determining a pathloss based at least in part on the pathloss offset. In some embodiments, the pathloss offset is one of activated and deactivated for power control determination for UL communications by a medium access control, MAC, control element, CE. According to another aspect, a network node configured to communicate with an uplink-only network node and with a user equipment, UE, is provided. The network node processing circuitry configured to: configure the UE with a plurality of transmission configuration indicator, TCI, states, a first number of TCI states of the plurality of TCI states to be applied to UL communication and a second number of TCI states of the plurality of TCI states to be applied to DL communications, the first and numbers being indicated by a plurality of codepoints. According to this aspect, in some embodiments, the first number of TCI states is not equal to the second number of TCI states. In some embodiments, the processing circuitry is configured to activate the plurality of TCI states via a medium access control, MAC, control element, CE, message. In some embodiments, the MAC CE associates TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the TCI state configuration is received by radio resource control, RRC, signaling. In some embodiments, the TCI state configuration configures the UE to assume a same quasi co-location, QCL, property for two joint TCI In some embodiments, the TCI state configuration configures the UE to apply a joint TCI state for UL and DL communications and at least one of an UL TCI state for UL communications and a DL TCI state for DL communications. In some embodiments, the TCI state configuration configures the UE with a list of joint TCI states, UL TCI states DL TCI states. In some embodiments, the processing circuitry is configured to receive a pathloss offset from the network node and determining a pathloss based at least in part on the pathloss offset. In some embodiments, the pathloss offset is one of activated and deactivated for power control determination for UL communications by a medium access control, MAC, control element, CE. According to another aspect, a method in a UE includes receiving from the network node a transmission configuration indicator, TCI, state configuration for a plurality of TCI states. The method includes applying a first number of TCI states of the plurality of TCI states to UL communication and applying a second number of TCI states of the plurality of TCI states to DL communications. In some embodiments, the first number of TCI states is not equal to the second number of TCI states. In some embodiments, the method includes receiving a medium access control, MAC, control element, CE, activating the plurality of TCI states. In some embodiments, the MAC CE activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the applied first and second number of TCI states are indicated TCI states. In some embodiments, the TCI state configuration indicates two joint TCI states. In some TCI state configuration configures the UE to ignore at least one TCI state property of at least one joint TCI state. In some embodiments, the TCI state configuration configures the UE to ignore a quasi co-location, QCL, property of a joint TCI state for DL communications. In some embodiments, the TCI state configuration configures the UE to one DL TCI state for DL communications and apply two UL TCI states for UL communication. In some embodiments, the method includes receiving a pathloss offset from the network node and determining a pathloss based at least in part on the pathloss offset. According to yet another aspect, a user equipment, UE, configured to communicate a network node and with an uplink-only network node is provided. The includes processing circuitry configured to receive from the network node a transmission configuration indicator ,TCI, state configuration for a plurality of TCI states. The processing circuitry is configured to apply a first number of TCI states of the plurality of states to UL communication and applying a second number of TCI states of the plurality of TCI states to DL communications. According to this aspect, in some embodiments, the first number of TCI states is not equal to the second number of TCI states. In some embodiments, the processing is configured to receive a medium access control, MAC, control element, CE, message activating the plurality of TCI states. In some embodiments, the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the applied first and second number of TCI states are indicated TCI states. In some embodiments, the TCI state configuration at least one joint TCI state. In some embodiments, the TCI state configuration configures the UE to ignore at least one TCI state property of at least one joint TCI state. In some embodiments, the TCI state configuration configures the UE to ignore a quasi co- location, QCL, property of a joint TCI state for one of UL and DL communications. In some embodiments, the TCI state configuration configures the UE to apply one DL TCI state for DL communications and apply two UL TCI states for UL communication. In some embodiments, the processing circuitry is configured to receive a pathloss offset from the network node and determining a based at least in part on the pathloss offset. BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the detailed description when considered in conjunction with the accompanying drawings wherein: FIG.1 is an NR time domain structure; FIG.2 shows a UE with three panels; FIG.3 is an example of activated TCI states and their mapping to TCI field codepoints for joint TCI states; FIG.4 is an example of activated TCI states and their mapping to TCI field codepoints for separate DL / UL TCI states; FIG.5 is a schematic diagram of an example network architecture illustrating a system according to principles disclosed herein; FIG.6 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure; FIG.7 is a flowchart of an example process in a network node for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment; FIG.8 is a flowchart of an example process in a user equipment for transmission indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment; FIG.9 is a flowchart of an example process in a network node for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment; FIG.10 is a flowchart of an example process in a user equipment for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment; FIG.11 is an example of a TCI state activation / deactivation MAC CE; FIG.12 is another example of a TCI state activation / deactivation MAC CE; FIG.13 is an example of a legacy MAC CE for unified TCI state activation / deactivation; FIG.14 is an example of a legacy MAC CE for enhanced TCI state activation / deactivation; FIG.15 is another example of a legacy MAC CE for enhanced TCI state activation / deactivation; FIG.16 is a flowchart of an example process for configuring and applying different TCI states; FIG.17 is an example signaling diagram for deployment with UL-only mode; and FIG.18 is a schematic deployment related to the signaling diagram of FIG.15. DETAILED DESCRIPTION Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components interoperate and modifications and variations are possible of achieving the and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The term “network node” used herein may be any kind of network node comprised a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity , relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node. In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein may be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc. Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). Note that although terminology from one particular wireless system, such as, for 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation 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 benefit from exploiting the ideas covered within this disclosure. Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network and user equipment described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Some embodiments are directed to transmission configuration indicator (TCI) state for asymmetric multiple transmission reception point (MTRP) deployment. Returning to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG.5 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16. Also, it is contemplated that a UE 22 may be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and than one type of network node 16. For example, a UE 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 may be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN. A network node 16 (eNB or gNB) is configured to include a configuration unit 24 which may be configured to configure the UE with a plurality of transmission configuration indicator, TCI, states, a first number of the plurality of TCI states to be applied to uplink, UL, communications and a second number of the plurality of TCI states be applied to downlink, DL, communications, the first and second numbers being indicated by a plurality of codepoints. A user equipment 22 is configured to include a TCI unit 26 which is configured to apply a first number of the plurality of TCI states associated with uplink, UL, communications and apply a second number of the plurality of TCI states associated with downlink, DL, communications, the first and second numbers being by a plurality of codepoints. Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG.6. The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves. In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 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, e.g., by network node 16. 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include configuration unit 24 which may be configured to configure the UE with a plurality of transmission configuration indicator, TCI, states, a first number of the plurality of TCI states to be applied to uplink, UL, communications and a second number of the plurality of TCI states to be applied to downlink, DL, communications, the first and second numbers being indicated by a plurality of codepoints. The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves. The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., 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). Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22. The processing circuitry 50 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, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include TCI unit 26 which is configured to apply a first number of the plurality of TCI states associated with uplink, UL, communications and apply a second number of the plurality of TCI states associated with DL, communications, the first and second numbers being indicated by a plurality of codepoints. In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG.6 and independently, the surrounding network topology may be that FIG.5. The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. Although FIGS.5 and 6 show various “units” such as configuration unit 24 and TCI unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a of hardware and software within the processing circuitry. FIG.7 is a flowchart of an example process in a network node 16 for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment. One or more blocks described herein may be by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to configure the UE, via radio resource control, RRC, signaling, with a plurality of transmission configuration indicator, TCI, states, a first of the plurality of TCI states associated with uplink, UL, communications and a second number of the plurality of TCI states associated with downlink, DL, communications, the first number of TCI states being different from the second number of TCI states (Block S10). The process includes activating at least one TCI state of the first number of TCI states and / or at least one TCI state of the second number of TCI states via a medium access control, MAC, control element, CE (Block S12). In some embodiments, the process includes indicating a joint TCI state associated with a downlink, DL, reference signal, RS. In some embodiments, the process includes triggering transmission by the UE of a set to determine an uplink, UL, beam pair link between the UE and an uplink-only transmission reception point, TRP. In some embodiments, the process includes determining TCI states for DL single-TRP and UL multi-TRP. In some embodiments, the process includes determining a pathloss offset at least in part on a difference in reference signal received power, RSRP, for different SRS resource sets. FIG.8 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the TCI unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to receive a configuration of a plurality of transmission configuration indicator, TCI, states (Block S14). The process includes applying a first of the plurality of TCI states associated with uplink, UL, communications and apply a second number of the plurality of TCI states associated with downlink, DL, communications, the first number of applied TCI states being different from the second number of applied TCI states (Block S16). The process also includes transmitting and signals using UL and DL communication properties associated with respective applied TCI states (Block S18). In some embodiments, the first number of the TCI states and / or the second number of the TCI states are activated by a medium access control, MAC, control element, CE. In embodiments, the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the MAC CE indicates a pathloss offset for calculating output power for UL transmissions associated with an activated TCI state. In some embodiments, the MAC CE indicates activation or deactivation of the path loss offset for calculating the output power. In some the process includes applying activated TCI states associated with the codepoint of the TCI indication bitfield. In some embodiments, the process includes receiving a TCI configuration via radio resource control, RRC, signaling. In some embodiments, the process includes receiving a list of joint TCI states, a list of UL TCI states and / or a list of DL TCI states. In some embodiments, a number of configured joint TCI states is different than a number of UL TCI states. In some embodiments, the first number of the TCI states associated with UL communications is greater than the second number of TCI states associated with DL communications. FIG.9 is a flowchart of an process in a network node 16 for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to configure the UE with a plurality of transmission configuration indicator, TCI, states, a first number of TCI states of the plurality of TCI to be applied to UL communication and a second number of TCI states of the plurality of TCI states to be applied to DL communications, the first and second numbers being indicated by a plurality of codepoints (Block S20). In some embodiments, the first number of TCI states is not equal to the second number of TCI states. In some embodiments, the method includes activating the plurality TCI states via a medium access control, MAC, control element, CE, message. In some embodiments, the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the TCI state configuration is indicated by radio resource control, RRC, signaling. In some the TCI state configuration configures the UE to assume a same quasi co- location, QCL, property for two joint TCI states. In some embodiments, the TCI state configuration configures the UE to apply a joint TCI state for UL and DL communications and at least one of an UL TCI state for UL communications and a DL TCI state for DL In some embodiments, the TCI state configuration configures the UE with a list of joint TCI states, UL TCI states and DL TCI states. In some embodiments, the method includes receiving a pathloss offset from the network node and determining a pathloss based at least in part on the pathloss offset. In some embodiments, the pathloss offset is one of activated and deactivated for power control determination for UL by a medium access control, MAC, control element, CE. FIG.10 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the TCI unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to receive from the network node a transmission configuration indicator, TCI, state for a plurality of TCI states (Block S22). The process includes applying a first of TCI states of the plurality of TCI states to UL communication and applying a second number of TCI states of the plurality of TCI states to DL communications (Block S24). In some embodiments, the first number of TCI states is not equal to the second of TCI states. In some embodiments, the method includes receiving a medium access control, MAC, control element, CE, message activating the plurality of TCI states. In some embodiments, the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. In some embodiments, the first and second number of TCI states are indicated TCI states. In some embodiments, the TCI state configuration indicates two joint TCI states. In some embodiments, TCI state configuration configures the UE to ignore at least one TCI state property of at least one joint TCI state. In some embodiments, the TCI state configuration configures the UE to ignore a quasi co-location, QCL, property of a joint TCI state for DL In some embodiments, the TCI state configuration configures the UE to apply one DL TCI state for DL communications and apply two UL TCI states for UL communication. In some embodiments, the method includes receiving a pathloss offset from the network node and determining a pathloss based at least in part on the pathloss Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples arrangements for transmission configuration indicator (TCI) state configuration for asymmetric multiple transmission reception point (MTRP) deployment. RRC configurations In some embodiments, the UE is higher layer configured with a TCI state operation allowing a number of applied TCI states associated with DL communication that is than the number of applied TCI states associated with UL communication. In some embodiments, the different configurations may, e.g., be one or more of: ^ “Application of multiple Joint TCI states” alt 1 “multipleJoint-Ignore”, where the UE ignores one or more DL and / or UL communication properties of the one or multiple applied Joint TCI states (e.g., the UE might be indicated with two Joint TCI state, but when configured with this mode of operation, the UE may ignore, e.g., the DL QCL properties of one Joint TCI state, and instead assume that one Joint TCI state is a UL TCI state): i. In some either an explicit indication (e.g., a pointer to one or more Joint TCI states) or implicit indication is used to indicate which Joint TCI states the UE should ignore DL and / or UL communication properties. In some embodiments, for an implicit indication, if the UE has two applied Joint TCI states, the UE may ignore the DL communication properties of the second applied Joint TCI state (and hence, assume that the second Joint TCI state is an UL TCI state). In some embodiments, the UE may apply the DL QCL properties of the first joint TCI state. In some embodiments, the PL-RS and pathloss offset is not counted as DL communication properties and may not be ignored. ^ “Application of multiple Joint TCI states” alt 2 “multipleJoint-merge”, where two or more joint TCI state configurations are expected to be same in one or more DL or UL communication properties, e.g., DL related QCL info or UL related pathloss configuration. For example, the UE may be indicated with two Joint TCI states, but the network may ensure that the QCL info configurations of the two joint TCI states are the same: i. In some embodiments, either an explicit indication (e.g., a pointer to one or more Joint TCI states) or implicit indication may be used to indicate which Joint TCI states the UE should merge DL and / or UL communication properties. In some embodiments, for an implicit indication, if the UE has two applied Joint TCI states, the UE may merge the DL communication properties of the first and second applied Joint TCI state. In some embodiments, the PL-RS and pathloss offset are not counted as DL communication properties and may not be ignored; ^ “Application of mixed Joint-UL TCI states”, where the UE may apply one (or more) Joint TCI state used for DL and UL communication, and one (or more) UL TCI state used for UL communication; ^ “Application of mixed Joint-DL TCI states”, where the UE may apply one (or more) Joint TCI state used for DL and UL communication, and one (or more) DL TCI state used for DL communication; ^ “Application of mixed Joint-DL-UL TCI states”, where the UE may apply one (or more) Joint TCI state used for DL and UL communication, and one (or more) DL TCI state used for DL communication, and one (or more) UL TCI state(s) for UL communication; and / or ^ “Application of uneven number TCI state for Separate TCI states”, where the UE may apply a single DL TCI state and two UL TCI states. In some embodiments for NR, the legacy parameter “unifiedTCI-stateType-r17” as specified in 3GPP Technical Standard (TS) 38.331 version 18.0.0 is extended to include an additional option indicating one of the TCI state mode operations as described above. One schematic example is as follows: MIMOParam-r17 ::= SEQUENCE { additionalPCI-ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, - - Need N additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, -- Need N unifiedTCI-StateType-r19 ENUMERATED {separate, joint, mixed- separate-joint} OPTIONAL, -- Need R uplink-PowerControlToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI- r17)) OF Uplink-powerControl-r17 OPTIONAL, -- Need N uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI- r17)) OF Uplink-powerControlId-r17 OPTIONAL, -- Need N sfnSchemePDCCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL, -- Need R sfnSchemePDSCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL -- Need R } In some embodiments, a new parameter is introduced, e.g., in servingCellConfig information element (IE) as specified in 3GPP TS 38.331 version 18.0.0. For example: MIMOParam-r17 ::= SEQUENCE { additionalPCI-ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, - - Need N additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, -- Need N unifiedTCI-StateType-r17 ENUMERATED {separate, joint} unifiedTCI-StateType-r19 ENUMERATED {mixedJointUL} OPTIONAL, -- Need R uplink- r17 SEQUENCE (SIZE (1..maxUL-TCI- r17)) OF Uplink-powerControl-r17 OPTIONAL, -- Need N uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI- r17)) OF Uplink-powerControlId-r17 OPTIONAL, -- Need N sfnSchemePDCCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL, -- Need R sfnSchemePDSCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL -- Need R } In an example of “Application of multiple Joint TCI states” alt 1 “multipleJoint- Ignore” and an alternative embodiment, a new parameter is introduced, e.g., in PUSCH- Config IE, as specified in 3GPP TS 38.311 version 18.0.0, to indicate if the DL communication properties associated with configuration of a joint TCI state may be UE may ignore some of the QCL types and DL RS (e.g. CSI-RS or SSB) associated with the joint TCI state and may apply only UL related information, e.g., the PL-RS and / or PL-RS offset for UL power control. For example: PUSCH-Config ::= SEQUENCE { … [[… multipanelScheme-r18 CHOICE { sdm-r18 SetupRelease { SDM-Scheme-r18 }, sfn-r18 SetupRelease { SFN-Scheme-r18 } } OPTIONAL, -- Cond SRSsets codebookTypeUL-r18 SetupRelease { CodebookTypeUL-r18 } OPTIONAL, -- Need M applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL -- Need R ]] [[ applyIndicatedTCI-State-IgnoreDL-r19 ENUMERATED {first, second} OPTIONAL -- Need R ]] … } In some embodiments, a method “Application of multiple Joint TCI states” alt 2 “multipleJoint-Merge” may be configured. The configuration of DL related properties in TCI-State IE is expected to be the same for one or more following parameters: ^ cellID; ^ bwp-Id; ^ referenceSignal: NZP-CSI-RS-ResourceID or SSB-Index; ^ qcl-Type; ^ AdditionalPCIIndex; ^ QCL-Info for qcl-Type1; and / or ^ QCL-Info for qcl-Type2; while the configuration of UL related properties in TCI-State IE is expected to be the same for one or more of the following parameters: ^ cellID; ^ bwp-Id; ^ tag-Id-ptr-r18; ^ PathlossReferenceRS-Id; ^ Uplink-powerControlID; and / or ^ PathlossOffset. The parameters listed above are used in TCI-State IE as shown below from 3GPP TS 38.331 version 18.0.0. TCI-State information element -- ASN1START -- TAG-TCI-STATE-START TCI-State ::= SEQUENCE { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ..., [[ additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond JointTCI1 ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL -- Cond JointTCI ]], [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } ::= SEQUENCE { ServCellIndex OPTIONAL, -- Need R bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index }, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ... } For 6G, new RRC parameters may be defined, supporting one or more of the mentioned configurations for TCI state mode operations. MAC-CE activations In some embodiments, a new MAC CE message is used to activate / deactivate TCI when the unified TCI state type is configured as one of the mentioned TCI state operation modes above. FIG.11 gives a schematic example of a case where the UE may be activated / deactivated with one or more Joint TCI state at the same time as it may be applied with one or more UL TCI states, i.e., configured with “Application of mixed Joint- UL TCI states”. In some embodiments, a field Pi (i=1,…8) may be used to indicate with value “0” or “1” if the ith TCI field codepoint in DCI is associated with both “a Joint TCI state and a UL TCI state” or “one of a TCI state” or “an UL TCI state”, depending on the RRC configured TCI state lists: “Pi: This field indicates whether each TCI codepoint has multiple TCI states or single TCI state. If Pi field is set to 1, it indicates that ithTCI codepoint includes the joint TCI state and the UL TCI state. If Pi field is set to 0, it indicates that ithTCI codepoint only the DL / joint TCI state or the UL TCI state. The codepoint to which a TCI state is mapped may be determined by its ordinal position among all the TCI state ID fields;” In some embodiments, a MAC CE is used to both activate / deactivate TCI states activate / deactivate pathloss offsets associated with an activated TCI state, see a schematic example in FIG.12. In some embodiments, a legacy MAC CE message is “re-used” to activate / deactivate TCI states when the unified TCI state type is configured as “Application of mixed Joint-UL TCI states”. One example is illustrated in FIG.13, where “Unified TCI States Activation / Deactivation MAC CE,” as specified in section 6.1.3.47 in 3GPP TS 38.321 version 18.0.0, may be re-used to activate TCI / deactivate TCI states for “Application of mixed Joint-UL TCI states” configuration: “Pi: This field indicates whether each TCI codepoint has multiple TCI states or single state. If Pi field is set to 1, it indicates that ith TCI codepoint includes the DL Joint TCI state and the UL TCI state. If Pi field is set to 0, it indicates that ith TCI codepoint includes only the DL / joint TCI state or the UL TCI state. The codepoint to which a TCI state is mapped is determined by its ordinal position among all the TCI state ID fields.” Another example is given in FIG.14, where the legacy “Enhanced TCI state activation / deactivation MAC CE for Separate TCI states” may be reused to activate / deactivate TCI state for operation in asymmetric DL sTRP UL mTRP deployment. For example, when the unified TCI state type is configured to “Application of mixed Joint-UL TCI states”, the field ^^^,^provides association to the j-th Joint TCI state: - Fi,j: This field indicates for the TCI state ID fields associated with the codepoint i of the DCI Transmission Configuration Indication field whether the j-th DL Joint TCI state is present or not, where j=1, 2. If Fi,j field is set to 1, it indicates the j-th DL Joint TCI state for codepoint i is present. If Fi,jfield is set to 0, it indicates the j-th DL Joint TCI state for codepoint i is absent. FIG.15 is another example of enhancement of the legacy “Enhanced TCI state activation / deactivation MAC CE for Separate TCI states” where the mode “Application of mixed Joint-UL TCI states” is configured. In this example, the activation / deactivation of TCI states and activation / deactivation of offsets are signaled with one MAC CE message. Default beam behavior In some embodiments, the rule on the default beam behavior for UEs in legacy NR updated to support the mixed Joint / UL TCI state operation. Below is an example of the modification to the specification text in 3GPP TS 38.214: “After a UE receives an initial higher layer configuration of dl-OrJointTCI- StateList with more than one TCI-State or ul-TCI-StateList with more than one TCI-UL- or is configured with “mixed-separate-joint TCI state” and an initial higher layer configuration of dl-OrJointTCI-StateList with one (or more) TCI state and UL- TCI-StateList with one (or more) TCI state and before application of an indicated TCI state from the configured TCI states: - The UE assumes that the UL TX spatial filter, if applicable, for dynamic- and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH transmission scheduled by a RAR UL grant or a MsgA PUSCH transmission during the initial access procedure” Other descriptions of methods and detailed embodiments FIG.16 is a flowchart of a disclosed scheme from the UE perspective. In summary, the example method depicted in FIG.16 includes the following steps at the UE: In a Step S26, the UE receives the higher layer configurations on unified TCI states, which may contain non equal numbers of DL and UL TCIs. In addition, the UE higher layer configurations related to, e.g., pathloss Reference signal (PL RS), default pathloss offset, etc. In a Step S28, the UE receives a dynamic message to activate or deactivate one or multiple UL / DL TCI states. In a Step S30, the UE receives a dynamic message of an indicated spatial filter and transmission power settings, including information on pathloss offset. In a Step S32, the UE transmits UL signal towards UL-only TRP based on the determination in Step S26. FIG.17 depicts an example of TCI state configuration and signaling scenario for a schematic simplified asymmetric single DL TRP and multiple UL TRPs deployment. See the example deployment in FIG.14. In FIG.18, the Anchor node has two SSBs, and the UE has 2 panels, where each panel is equipped with 2 beams (please note that the low number of beams used at TRP and UE are used for simplicity of the description). It is further assumed that the UE support UL TRP operation (e.g. using repetition or STxMP), and that the UE is configured with the following SRS resource sets: ^ SRS resource set 1 with usage =”beam management” is configured with 2 SRS resources: o SRS resource 1 and SRS resource 2; ^ SRS resource set 2 with usage = “codebook based” is configured with: o one two-port SRS resource; and / or o configured to follow first indicated UL TCI state; ^ SRS resource set 3 with usage = “codebook based” is configured with: o one two-port SRS resource; and / or o configured to follow second indicated UL TCI state The examples in FIGS.17 and 18 assume that the Anchor TRP is configured with 2 SSBs. The extension to more than 2 SSBs is straightforward. The flowchart in FIG.17 includes the following steps. The description below is based on the example of the DL sTRP UL mTRP scenario. Some embodiments are also to the extension to asymmetric UL mTRP scenarios. In Step S34, the UE is RRC configured with TCI states, and SRS resource sets. In some embodiments, the UE may be configured with separate UL-TCI-stateList and dl-JointTCI-stateList for operation in asymmetric DL sTRP UL mTRP deployment. instance, the dl-Joint-TCI-stateList may include the N joint TCI states used by the Anchor TRP, and the UL-TCI-stateList may contain the M UL TCI states used by the UL- only TRPs. The number of joint TCI states may be different from the number of UL TCI states. In some embodiments, the UE may be configured with a single mixed-separate- TCI state list that includes all the TCI states used by the anchor TRP and the UL-only TRPs. In some embodiments, the mixed-separate-joint TCI state list is per bandwidth part (BWP). In some embodiments, the pathloss reference signal and pathloss offset are only associated to the UL TCI state, as shown in the following example. TCI-UL-State information element -- ASN1START -- -- ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Need R pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 -- Cond Mandatory pathlossReferenceOffset-rxx PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond Mandatory ..., [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } -- TAG-TCI-UL-STATE-STOP -- ASN1STOP In some embodiments, the pathloss offset is always associated to the pathloss Reference Signal and is configured together with the PL RS. In Step S36, the network, e.g., via network node 16, indicates Joint TCI state 1 which is associated to the first DL RS, i.e., SSB1. In some embodiments, the asymmetric DL sTRP UL mTRP is based on single-DCI solutions. In some embodiments, the DL sTRP UL mTRP is based on multi-DCI solutions. In Step S38, the network, e.g., via network node 16, triggers transmission of SRS set 1 to determine a suitable UL beam pair link between UE and UL-only TRP. In Step S40, the network, e.g., via network node 16, triggers transmission of SRS set 2 to determine a suitable UL CQI / PMI etc. for UL transmission of a UL beam pair link between UE and Anchor TRP. In Step S42, based on the measurement of received SRSs and the difference between received SRS RSRPs, the network, e.g., via network node 16, determines and indicates the appropriate TCI states to DL single-TRP and UL multi-TRP. For instance, considering the example in FIG.18, the network node 16 may configure: ^ Joint-TCI state 1 using SSB1 as the QCL reference; and / or ^ UL-TCI state 4 using SRS resource2 as QCL reference and indicated with e.g. “pathloss offset = 10dB” (which e.g. may depend on estimated path loss offset based on e.g. received SRSs in Step 3). In Step S44, the network, e.g., via network node 16, triggers transmission of SRS set 2 towards the Anchor TRP. In Step S46, the network, e.g., via network node 16, triggers transmission of SRS set 3 towards the UL-only TRP. In Step S44 and Step S46, the network, e.g., via network node 16, will derive new pathloss offset based on the difference of RSRP for SRS resource set 2 and SRS resource set 3. Some Examples may include one or more of the following: 1. A method in a wireless device or UE for determining DL and UL communication properties (e.g., QCL related information, spatial filter, and / or power control related information), the method comprising: a. Receiving a configuration of a set of TCI states: b. Apply a number of TCI states (where each TCI state may either be associate with DL communication (e.g. DL TCI state), UL communication (e.g. UL TCI state) or both DL and UL communication (e.g. Joint TCI state)), and where the number of applied TCI states associated with UL communication may differ from number of applied TCI states associated with DL communication. c. Transmitting and receiving signals / channels using the DL and UL communication properties associated with the applied TCI states. 2. Example 1 and where the receives a MAC CE message activating the TCI states. 3. Example 2 and where the UE applies the TCI states activated in the MAC- CE. 4. Example 2 and where the MAC-CE associates activated TCI states to a codepoint of a TCI indication bitfield in DCI. 5. Example 4 and where the UE applies activated TCI states associated with indicated codepoint of a TCI indication bitfield in DCI. 6. At least one of the above Examples and where the UE may be RRC configured with one or more of the following TCI configurations: a. “Application of multiple Joint TCI states”: i. Alt 1 of a, “multipleJoint-Ignore”, where the UE ignores one or more DL and / or UL communication properties of the multiple applied Joint TCI states (e.g. the UE might be indicated with two Joint TCI state, but when configured with this mode of operation, the UE ignores e.g. the DL QCL properties of one Joint TCI state, and instead assume that one Joint TCI state is a UL TCI state); and ii. Alt 2 of a, “multipleJoint-merge”, where two or more joint TCI state configurations are expected to be same in one or more DL or UL communication properties, e.g. DL related QCL info or UL related pathloss configuration. (e.g. the UE might be indicated with two Joint TCI states, but the network makes sure the QCL info configurations of the two joint TCI states are the same). b. “Application of mixed Joint-UL TCI states”, where the UE may apply one Joint TCI state used for DL and UL communication, and one UL TCI state used for UL communication. c. “Application of uneven number TCI state for Separate TCI states”, where the UE may apply a single DL TCI state and two UL TCI states. d. “Application of mixed Joint-DL-UL TCI states”, where the UE may apply one (or more) Joint TCI state used for DL and UL communication, and one (or more) DL TCI state used for DL communication, and one (or more) UL TCI state(s) for UL communication. 7. Example 1a and where the UE may be configured with a single TCI state list including Joint TCI state, and / or UL TCI states, and / or DL TCI states. 8. Example 1a and where the may be configured with a list of Joint TCI states (e.g., used by for DL / UL communication with the Anchor TRP) and another list of UL TCI states (e.g. used for communication with the UL-only TRP), or a list of DL TCI states (e.g., used for communication with the DL-only TRP). 9. Example 1a and where the number of configured Joint TCI states may be different from the number of UL TCI states. 10. Example 1b and the number of applied TCI states associated with UL communication is larger than number of applied TCI states associated with DL 11. Example 2 and where the MAC-CE activating the TCI states is a new MAC-CE (in NR or 6G). 12. Example 2 and where the MAC-CE activating the TCI states is a re-use of a legacy NR MAC-CE (by re-purposing one or more fields in the MAC-CE) 13. Example 12 and where the legacy MAC-CE is the “Unified TCI States Activation / Deactivation MAC CE” as specified in section 6.1.3.47 of TS 38.321 version 18.0.0. 14. Example 13 and where when the UE is RRC configured with “Application mixed Joint-UL TCI states”, the “Unified TCI States Activation / Deactivation MAC CE” as specified in section 6.1.3.47 of TS 38.321 version 18.0.0, may be used to indicate Joint TCI state and UL TCI states. 15. Example 2 and where the MAC-CE indicates a pathloss offset for output power for UL transmission associated with a TCI-state activated by the MAC-CE. 16. Example 2 and where the MAC-CE indicates an activation / deactivation of a pathloss offset for calculating output power for UL transmission associated with a TCI-state activated by the MAC-CE. example embodiments may include one or more of the following: Embodiment A1. A network node configured to communicate with a user equipment (UE), the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: configure the UE, via radio resource control, RRC, signaling, with a plurality of transmission configuration indicator, TCI, states, a first number of the plurality of TCI states associated with uplink, UL, communications and a second number of the plurality of TCI states associated with downlink, DL, communications, the first number of TCI states being different from the second number states; and activate at least one TCI state of the first number of TCI states and / or at least one TCI state of the second number of TCI states via a medium access control, MAC, control element, CE. Embodiment A2. The network node of Embodiment A1, wherein the network node, radio interface and / or processing circuitry are configured to indicate a joint TCI state associated with a downlink, DL, reference signal, RS. Embodiment A3. The network node of any of Embodiments A1 and A2, the network node, radio interface and / or processing circuitry are configured to trigger transmission by the UE of a first SRS set to determine an uplink, UL, beam pair link between the UE and an uplink-only transmission reception point, TRP. Embodiment A4. The network node of Embodiment A3, wherein the network node, radio interface and / or processing circuitry are configured to determine TCI states for single-TRP and UL multi-TRP. Embodiment A5. The network node of any of Embodiments A3 and A4, wherein the network node, radio interface and / or processing circuitry are configured to determine a pathloss offset based at least in part on a difference in reference signal power, RSRP, for different SRS resource sets. Embodiment B1. A method implemented in a network node that is configured to communicate with a user equipment, the method comprising: configuring the UE, via radio resource control, RRC, signaling, with a plurality of configuration indicator, TCI, states, a first number of the plurality of TCI states associated with uplink, UL, communications and a second number of the plurality of TCI states associated with downlink, DL, communications, the first number of TCI states being different from the second number of TCI states; and activating at least one TCI state of the first number of TCI states and / or at least one state of the second number of TCI states via a medium access control, MAC, control element, CE. Embodiment B2. The method of Embodiment B1, further comprising indicating a joint TCI state associated with a downlink, DL, reference signal, RS. Embodiment B3. The method of any of Embodiments B1 and B2, further comprising triggering transmission by the UE of a first SRS set to determine an uplink, UL, beam pair link between the UE and an uplink-only transmission reception point, TRP. Embodiment B4. The method of Embodiment B3, further comprising determining TCI states for DL single- UL multi-TRP. Embodiment B5. The method of any of Embodiments B3 and B4, further comprising determining a pathloss offset based at least in part on a difference in reference signal received power, RSRP, for different SRS resource sets. Embodiment C1. A user equipment (UE) configured to communicate with a network node, the UE configured to, and / or comprising a radio interface and / or processing circuitry configured to: receive a configuration of a plurality of transmission configuration indicator, TCI, apply a first number of the plurality of TCI states associated with uplink, UL, communications and apply a second number of the plurality of TCI states associated with downlink, DL, communications, the first number of applied TCI states being different from the second number of applied TCI states; and transmit and receive signals using UL and DL communication properties associated with respective applied TCI states. Embodiment C2. The UE of Embodiment C1, wherein the first number of the TCI states and / or the second number of the TCI states are activated by a medium access MAC, control element, CE. Embodiment C3. The UE of Embodiment C2, wherein the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI. Embodiment C4. The UE of any of Embodiments C2 and C3, wherein the MAC CE indicates a pathloss offset for calculating output power for UL transmissions associated with an activated TCI state. Embodiment C5. The UE of Embodiment C4, wherein the MAC CE indicates activation or deactivation of the path loss offset for calculating the output power. Embodiment C6. The UE of any of Embodiments C1-C5, wherein the UE, radio interface, and / or processing circuitry are configured to apply activated TCI states associated with the codepoint of the TCI indication bitfield. Embodiment C7. The UE of any of Embodiments C1-C6, wherein the UE, radio interface, and / or processing circuitry are configured to receive a TCI configuration via radio resource control, RRC, signaling. Embodiment C8. The UE of any of Embodiments C1-C7, wherein the UE, radio interface, and / or processing are configured to receive a list of joint TCI states, a list of UL TCI states and / or a list DL TCI states. Embodiment C9. The UE of Embodiment C8, wherein a number of configured joint TCI states is different than a number of UL TCI states. Embodiment C10. The UE of any of Embodiments C1-C9, wherein the first of the TCI states associated with UL communications is greater than the second number of TCI states associated with DL communications. Embodiment D1. A method implemented in a user equipment (UE) that is configured to communicate with a network node, the method comprising: receiving a configuration of a plurality of transmission configuration indicator, TCI, states; applying a first number of the plurality of TCI states associated with uplink, UL, communications and applying a second number of the plurality of TCI states associated with downlink, DL, communications, the first number of applied TCI states being from the second number of applied TCI states; and transmitting and receive signals using UL and DL communication properties associated with respective applied TCI states. Embodiment D2. The method of Embodiment D1, wherein the first number of TCI states and / or the second number of the TCI states are activated by a medium access control, MAC, control element, CE. Embodiment D3. The method of Embodiment D2, wherein the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink information, DCI. Embodiment D4. The method of any of Embodiments D2 and D3, wherein the MAC CE indicates a pathloss offset for calculating output power for UL transmissions associated with an activated TCI state. Embodiment D5. The method of Embodiment D4, wherein the MAC CE activation or deactivation of the path loss offset for calculating the output power. Embodiment D6. The method of any of Embodiments D1-D5, further comprising applying activated TCI states associated with the codepoint of the TCI indication bitfield. Embodiment D7. The method of any of Embodiments D1-D6, further comprising receiving a TCI configuration via radio resource control, RRC, signaling. Embodiment D8. The method of any of Embodiments D1-D7, further comprising receiving a list of joint TCI states, a list of UL TCI states and / or a list of DL TCI states. Embodiment D9. The method of Embodiment D8, wherein a number of configured joint TCI states is different than a number of UL TCI states. Embodiment D10. The method of any of Embodiments D1-D9, wherein the number of the TCI states associated with UL communications is greater than the second number of TCI states associated with DL communications. As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices. Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act in the flowchart and / or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination. It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method in a user UE (22), configured to communicate with a network node (16) and with an uplink- the method comprising: receiving (S22) from the network node (16) a transmission configuration indicator, TCI, state configuration for a plurality of TCI states; and applying (S24) a first number of TCI states of the plurality of TCI states to UL communication and applying a second number of TCI states of the plurality of TCI states to DL communications.

2. The method of Claim 1, wherein the first number of TCI states is not equal the second number of TCI states.

3. The method of any of Claims 1 and 2, further comprising receiving a medium access control, MAC, control element, CE, message activating the plurality of TCI states.

4. The method of Claim 4, wherein the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI.

5. The method of any of Claims 1-4, wherein the applied first and second number of TCI states are indicated TCI states.

6. The method of any of Claims 1-5, wherein the TCI state configuration two joint TCI states.

7. The method of any of Claims 1-6, wherein the TCI state configuration configures the UE (22) to ignore at least one TCI state property of at least one joint TCI state.

8. The method of any of Claims 1-7, wherein the TCI state configuration configures the UE (22) to ignore a quasi co-location, QCL, property of a joint TCI state for DL communications.

9. The method of any of Claims 1-8, wherein the TCI state configuration configures the UE (22) to apply one DL TCI state for DL communications and apply two UL TCI states for UL communication.

10. The method of any of Claims 1-9, further comprising receiving a pathloss offset from the network node (16) and determining a pathloss based at least in part on the pathloss offset.

11. A user equipment, UE (22), configured to communicate with a network node (16) and with an uplink-only network node (16), the UE (22) comprising processing circuitry (50) configured to: receive from the network node (16) a transmission configuration indicator, TCI, state configuration for a plurality of TCI states; and apply a first number of TCI states of the plurality of TCI states to UL communication and applying a second number of TCI states of the plurality of TCI states to DL communications.

12. The UE (22) of Claim 11, wherein the first number of TCI states is not equal to the second number of TCI states.

13. The UE (22) of any of Claims 11 and 12, wherein the processing circuitry (50) is configured to receive a medium access control, MAC, control element, CE, message activating the plurality of TCI states.

14. The UE (22) of Claim 13, wherein the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI.

15. The UE (22) of any of Claims 11-14, wherein the applied first and second number of TCI states are indicated TCI states.

16. The UE (22) of any of Claims 11-15, wherein the TCI state configuration indicates at least one joint TCI state.

17. The UE (22) of any of Claims 11-16, wherein the TCI state configuration configures the UE (22) to ignore at least one TCI state property of at least one joint TCI state.

18. The UE (22) of any of Claims 11-17, wherein the TCI state configuration configures the UE (22) to ignore a quasi co-location, QCL, property of a joint TCI state for one of UL and DL communications.

19. The UE (22) of any of Claims 11-18, wherein the TCI state configuration configures the UE (22) to apply one DL TCI state for DL communications and apply two UL TCI states for UL communication.

20. The UE (22) of any of Claims 11-19, wherein the processing circuitry (50) is configured to receive a pathloss offset from the network node (16) and determining a pathloss based at least in part on the pathloss offset.

21. A method in a network node (16) configured to communicate with an uplink-only network node (16) and with a user equipment, UE (22), the method comprising: configuring (S22) the UE (22) with a plurality of transmission configuration TCI, states, a first number of TCI states of the plurality of TCI states to be applied to UL communication and a second number of TCI states of the plurality of TCI states to be applied to DL communications, the first and second numbers being indicated by a plurality of codepoints.

22. The method of Claim 21, the first number of TCI states is not equal to the second number of TCI states.

23. The method of any of Claims 21 and 22, further comprising activating the of TCI states via a medium access control, MAC, control element, CE, message.

24. The method of Claim 23, wherein the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink control information, DCI.

25. The method of any of Claims 21-24, wherein the TCI state configuration is indicated by radio resource control, RRC, signaling.

26. The method of any of 21-25, wherein the TCI state configuration configures the UE (22) to assume a same quasi co-location, QCL, property for two joint TCI states.

27. The method of any of Claims 21-26, wherein the TCI state configuration configures the UE (22) to apply a joint TCI state for UL and DL communications and at least one of an UL TCI state for UL communications and a DL TCI state for DL communications.

28. The method of any of Claims 21-27, wherein the TCI state configuration configures the UE (22) with a list of joint TCI states, UL TCI states and DL TCI states.

29. The method of any of Claims 21-29, further comprising receiving a offset from the network node (16) and determining a pathloss based at least in part on the pathloss offset.

30. The method of Claim 29, wherein the pathloss offset is one of activated and for power control determination for UL communications by a medium access control, MAC, control element, CE.

31. A network node (16) configured to communicate with an uplink-only node (16) and with a user equipment, UE (22), the network node (16) comprising processing circuitry (36) configured to: configure the UE (22) with a plurality of transmission configuration indicator, TCI, states, a first number of TCI states of the plurality of TCI states to be applied to UL communication and a second number of TCI states of the plurality of TCI states to be to DL communications, the first and second numbers being indicated by a plurality of codepoints.

32. The network node (16) of Claim 31, the first number of TCI states is not equal to the second number of TCI states.

33. The network node (16) of any of Claims 31 and 32, wherein the processing circuitry (36) is configured to activate the of TCI states via a medium access control, MAC, control element, CE, message.

34. The network node (16) of Claim 33, wherein the MAC CE associates activated TCI states to a codepoint of a TCI indication bitfield in downlink controlnformation, DCI.

35. The network node (16) of any of Claims 31-34, wherein the TCI state configuration is received by radio resource control, RRC, signaling.

36. The network node (16) of any of Claims 31-35, wherein the TCI state configuration configures the UE (22) to assume a same quasi co-location, QCL, property for two joint TCI states.

37. The network node (16) of any of Claims 31-36, wherein the TCI state configuration configures the UE (22) to apply a joint TCI state for UL and DL communications and at least one of an UL TCI state for UL communications and a DL TCI state for DL communications.

38. The network node (16) of any of Claims 31-37, wherein the TCI state configuration configures the UE (22) with a list of joint TCI states, UL TCI states and DL TCI states.

39. The network node (16) of any of Claims 31-38, wherein the processing circuitry (36) is configured to receive a pathloss offset from the network node (16) and determining a pathloss based at least in part on the pathloss offset.

40. The network node (16) of Claim 39, wherein the pathloss offset is one of activated and deactivated for power control determination for UL communications by a medium access control, MAC, control element, CE.

Images