Joint transmission scheme in unified transmission configuration indicator framework

Abstract

A joint transmission scheme in a unified transmission configuration indicator framework is disclosed. A system and method for joint transmission in a unified transmission configuration indicator (UTCI) framework are disclosed, the method including transmitting, by a user equipment (UE), a first transmission, where the first transmission includes information indicating capabilities per set of resources for a first feature associated with a UTCI scheme, the capability per resource set indicates that the UE is able to associate channel state information reference signal (CSI-RS) resources with a transmission configuration indicator (TCI) state at a resource set level, where the UE is configured to support joint transmission, and where the first feature indicates that the UE is able to support per aperiodic CSI-RS resource configuration for TCI selection, where the UE is configured to support joint transmission. Or each aperiodic CSI-RS resource set configuration for TCI selection.

Description

Technical Field

[0001] Various aspects of embodiments of the present disclosure relate to wireless communications. For example, various aspects of embodiments of the present disclosure relate to improved systems and methods for configuring a joint transmission scheme in a unified transmission configuration indicator (UTCI) framework. Background Art

[0002] Modern communication devices (e.g., mobile phones, vehicles, laptops, satellites, etc.), also referred to as user equipment (UE), can communicate with a network node (e.g., a base station, also referred to as a gNB) to receive data from a network associated with the network node and to send data to a network associated with the network node. Data can be sent via one or more transmit and receive points (TRPs) associated with the network node. The transmission of the same signal from multiple TRPs to a UE can be referred to as a joint transmission. Joint transmission can allow interference suppression and improved received signal quality. The transmission configuration indicator (TCI) state represents a configuration such as a quasi-co-location relationship (QCL relationship) between a target reference signal (RS) and a source RS. The TCI state may include a given transmission beam, where applicable, as in QCL type D. Under the UTCI framework, a UE may be provided with only one unified TCI state per TRP. For example, the UTCI framework may specify that all channels and resources used for transmission follow an indicated unified TCI state. By simplifying (e.g., by reducing) the number of available TCI states for transmission, the UTCI framework may allow more efficient communication between a network node and a UE.

[0003] The above information disclosed in this Background section is for enhancement of understanding of the background of the present disclosure and therefore it may contain information that does not constitute the prior art. Summary of the invention

[0004] The UTCI framework may simplify (e.g., may reduce) the number of available TCI states for transmission and allow efficient communication between network nodes and UEs. However, as discussed in further detail below, some UEs capable of receiving joint transmissions including non-coherent joint transmission (NCJT) and coherent joint transmission (CJT) may encounter performance limitations due to applying (e.g., complying with) the UTCI framework.

[0005] To overcome these issues, systems and methods for joint transmission (eg, for configuring joint transmission) in a UTCI framework are described herein.

[0006] Some embodiments of the present disclosure relate to sending information (eg, via capability signaling) by some UEs to indicate capabilities that may not be reported in the UTCI framework.

[0007] Some embodiments of the present disclosure relate to the denial of certain UE features by some UEs based on the capabilities of the given UE and potential limitations of operating within the UTCI framework.

[0008] Some embodiments of the present disclosure relate to determining, by some UEs, how to associate resource groups with two or more TCI states.

[0009] The above-described method improves upon previous methods by reducing the risk of ambiguity and under-reporting (eg, conservative reporting) associated with joint transmissions in the UTCI framework.

[0010] According to some embodiments of the present disclosure, a method for configuring joint transmission in a UTCI framework includes: sending a first transmission by a user equipment (UE), the first transmission including information indicating a per-resource set capability for a first feature associated with a unified transmission configuration indicator (UTCI) scheme, the per-resource set capability indicating that the UE is capable of associating a channel state information reference signal (CSI-RS) resource with a transmission configuration indicator (TCI) state at a resource set level, wherein the UE is configured to support joint transmission, and wherein the first feature indicates that the UE is capable of supporting per-non-periodic CSI-RS resource configuration for TCI selection, or per-non-periodic CSI-RS resource set configuration for TCI selection.

[0011] The first feature may be associated with index number 40-1-3 of the Radio Access Network 1 (RAN1) UE feature list.

[0012] The joint transmission may include non-coherent joint transmission (NCJT), and the UE may support NCJT CSI under a second feature, wherein the second feature indicates that the UE is capable of supporting one or more features of channel state information multiple transmission and reception points (CSIMTRP).

[0013] The second feature may be associated with index number 23-7-1 of the Radio Access Network 1 (RAN1) UE feature list.

[0014] The joint transmission may include coherent joint transmission (CJT), and the UE may support CJTCSI under a second feature, wherein the second feature indicates that the UE is capable of supporting two transmission configuration indicator (TCI) states for the CJT transmission scheme for a physical downlink shared channel (PDSCH).

[0015] The second feature may be associated with index number 40-1-4 of the Radio Access Network 1 (RAN1) UE feature list.

[0016] The method may further include: sending, by the user equipment (UE), a second transmission including information refusing to perform the first feature, wherein the joint transmission includes non-coherent joint transmission (NCJT), and the UE supports NCJT CSI under the second feature, and the second feature indicates that the UE is capable of supporting one or more features of channel state information multiple transmit and receive points (CSIMTRP).

[0017] The first feature may be associated with index number 40-1-3 of the Radio Access Network 1 (RAN1) UE feature list, and the second feature may be associated with index number 23-7-1 of the RAN1 UE feature list.

[0018] The UE may not support the joint operation of joint transmission and UTCI CSI-RS transmission.

[0019] According to other embodiments of the present disclosure, a method for configuring joint transmission in a UTCI framework includes: sending first capability information by a user equipment (UE) based on a rule indicating how the UE applies a first indicated transmission configuration indicator (TCI) state or a second indicated TCI state to a non-periodic channel state information reference signal (AP CSI-RS) resource, and receiving coherent joint transmission (CJT) by the UE based on the sending of the first capability information.

[0020] The first indicated TCI state may include a joint TCI state or a downlink (DL) TCI state, or the second indicated TCI state may include a joint TCI state or a DL TCI state.

[0021] The rule may indicate that support for the CJT is conditional on the UE supporting a resource-level radio resource control (RRC) configuration, wherein the resource-level RRC configuration indicates that the UE is to apply a first indicated transmission configuration indicator (TCI) state or a second indicated TCI state to a non-periodic channel state information reference signal (AP CSI-RS) resource.

[0022] Sending the first capability information may include sending information indicating support for capability with unified TCI (UTCI) per resource set and two or more unified TCI (UTCI) states in a CJT scheme, wherein the first indicated TCI state includes a first indicated UTCI state and the second indicated TCI state includes a second indicated UTCI state, and the rule indicates that for CJT measurement or reporting, the UE applies the first indicated UTCI state to CSI-RS resources in a first group, and the UE applies the second indicated UTCI state to CSI-RS resources in a second group, the CSI-RS resources in the first group correspond to a first TRP or a first TRP group associated with the first indicated UTCI state, and the CSI-RS resources in the second group correspond to a second TRP or a second TRP group associated with the second indicated UTCI state.

[0023] Sending the first capability information may include refusing to perform a first feature associated with a unified transmission configuration indicator (UTCI) scheme, wherein the UE supports the CJT scheme via a second feature and / or a third feature, and supports more than one unified transmission configuration indicator (UTCI) state for CJT via a fourth feature, wherein the first feature indicates that the UE can support per-non-periodic CSI-RS resource configuration for TCI selection or per-non-periodic CSI-RS resource set configuration for TCI selection, wherein the second feature indicates that the UE can support one or more features for a first CJT codebook, wherein the third feature indicates that the UE can support one or more features for a second CJT codebook, and wherein the fourth feature indicates that the UE can support two TCI states for the CJT scheme for a physical downlink shared channel (PDSCH).

[0024] The first feature may be associated with index number 40-1-3 of the radio access network 1 (RAN1) UE feature list, the second feature may be associated with index number 40-3-1-1 of the RAN1 UE feature list, the third feature may be associated with index number 40-3-1-5 of the RAN1 UE feature list, and the fourth feature may be associated with index number 40-1-4 of the RAN1 UE feature list.

[0025] According to other embodiments of the present disclosure, a method for configuring joint transmission in a UTCI framework includes: sending, by a user equipment (UE), information indicating a per-resource capability for a first feature associated with a unified transmission configuration indicator (UTCI) scheme, wherein the per-resource capability indicates that the UE is capable of associating a channel state information reference signal (CSI-RS) resource with a transmission configuration indicator (TCI) state at a resource level, and sending, by the UE, information indicating support for a second feature, wherein the second feature indicates that the UE is capable of supporting joint operation of joint transmission CSI and per-nonperiodic UTCI CSI-RS resource configuration for TCI selection, wherein the first feature indicates that the UE is capable of supporting per-nonperiodic CSI-RS resource configuration for TCI selection, or per-nonperiodic CSI-RS resource set configuration for TCI selection.

[0026] The first feature may be associated with index number 40-1-3 of the Radio Access Network 1 (RAN1) UE feature list.

[0027] The joint transmission CSI may include non-coherent joint transmission (NCJT) CSI.

[0028] The joint transmission CSI may include coherent joint transmission (CJT) CSI.

[0029] The granularity of support for the second feature may include a per-UE granularity, wherein the per-UE granularity may indicate that the UE is capable of performing the second feature in any scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and other aspects of the present disclosure will be more clearly understood from the following detailed description of illustrative, non-limiting embodiments with reference to the accompanying drawings.

[0031] Figure 1 is a block diagram depicting a system for joint transmission in a UTCI framework according to some embodiments of the present disclosure.

[0032] Figure 2 is a block diagram depicting resource grouping in a system for joint transmission in a UTCI framework according to some embodiments of the present disclosure.

[0033] Figure 3 is a diagram depicting a table entry from the Radio Access Network 1 (RAN1) UE feature list for index number 40-1-3.

[0034] Figure 4A is a diagram depicting a table entry from the RAN1 UE Features List for index number 23-7-1.

[0035] Figure 4Bis a diagram depicting the definition of parameters associated with the RAN1 UE Features List for Index Number 23-7-1.

[0036] Figure 5 is a flow chart depicting a method for configuring NCJT in a UTCI framework based on UE indication “per resource set” according to some embodiments of the present disclosure.

[0037] Figure 6 is a flow chart depicting a method for configuring NCJT in a UTCI framework based on UE indicating individual capabilities according to some embodiments of the present disclosure.

[0038] Figure 7 It is a description of some embodiments of the present disclosure for Figure 6 Figure 4 shows possible table entries (with index numbers such as 40-1-A) for individual capabilities discussed and depicted in a format associated with a RAN1 UE feature list.

[0039] Figure 8 is a diagram depicting a table entry from the RAN1 UE feature list for index number 40-1-4.

[0040] Fig. 9 is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE associating an indicated UTCI state with respective relevant TRPs according to some embodiments of the present disclosure.

[0041] Fig. 10A is a diagram depicting possible table entries (eg, with index number 40-1-B) for potential individual capabilities depicted in a format associated with a RAN1 UE feature list according to some embodiments of the present disclosure.

[0042] Fig. 10B is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE indicating separate capabilities for joint operation of CJT and UTCI according to some embodiments of the present disclosure.

[0043] Fig.11 is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE's refusal to perform a given feature according to some embodiments of the present disclosure.

[0044] Fig. 12A is a diagram depicting a table entry from the RAN1 UE feature list for index number 40-3-1-1.

[0045] Fig. 12B is a diagram depicting additional table entries from the RAN1 UE feature list for index number 40-3-1-1.

[0046] Fig.13A is a diagram depicting a table entry from the RAN1 UE feature list for index number 40-3-1-5.

[0047] Fig. 13B is a diagram depicting additional table entries from the RAN1 UE Features List for index number 40-3-1-5.

[0048] Fig. 13C is a diagram depicting a table entry from the RAN1 UE feature list for index number 2-35, which is listed as a prerequisite feature group in the table entry from the RAN1 UE feature list for index numbers 40-3-1-1 and 40-3-1-5.

[0049] Fig.13D is a diagram depicting additional table entries from the RAN1 UE feature list for index numbers 2-35.

[0050] Fig.14 is a flow chart depicting a method for configuring CJT in a UTCI framework based on UE indication “per resource set” according to some embodiments of the present disclosure.

[0051] Fig.15 is a diagram depicting possible table entries (eg, with index numbers 40-1-C) for potential individual capabilities depicted in a format associated with a RAN1 UE feature list according to some embodiments of the present disclosure.

[0052] Fig.16 is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE indicating separate capabilities for joint operation of CJT and UTCI with more than one UTCI state according to some embodiments of the present disclosure.

[0053] Fig.17 is a block diagram of an electronic device in a network environment according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0054] In the following detailed description, many specific details are set forth in order to provide a thorough understanding of the present disclosure. However, those skilled in the art will appreciate that the disclosed aspects may be practiced without these specific details. In other cases, well-known methods, processes, components, and circuits are not described in detail to avoid obscuring the subject matter disclosed herein.

[0055] References throughout this specification to "one embodiment" or "embodiment" mean that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment disclosed herein. Therefore, the phrases "in one embodiment" or "in an embodiment" or "according to an embodiment" (or other phrases with similar meanings) that appear in various places throughout this specification may not necessarily refer to the same embodiment. In addition, specific features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the word "exemplary" means "used as an example, instance or illustration". Any embodiment described herein as "exemplary" should not be interpreted as necessarily being preferred or advantageous over other embodiments. In addition, depending on the context discussed herein, a singular term may include a corresponding plural form, and a plural term may include a corresponding singular form. Similarly, hyphenated terms (e.g., "two-dimensional", "predetermined", "pixel-specific", etc.) may occasionally be used interchangeably with corresponding non-hyphenated versions (e.g., "two-dimensional", "predetermined", "pixel-specific", etc.). This occasionally interchangeable use should not be considered inconsistent with each other.

[0056] It should also be noted that the various drawings (including component drawings) shown and discussed herein are for illustrative purposes only and are not drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. In addition, where deemed appropriate, reference numerals have been repeated in the drawings to indicate corresponding and / or similar elements.

[0057] The terms used herein are only used for the purpose of describing some example embodiments and are not intended to limit the claimed subject matter. As used herein, the singular form is intended to also include the plural form, unless the context clearly indicates otherwise. It will be further understood that when used in this specification, the terms "include" and / or "comprise" specify the presence of the features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0058] It should be understood that when an element or layer is referred to as being on, "connected to" or "coupled to" another element or layer, it may be directly on, connected to or coupled to the other element or layer, or there may be intermediate elements or layers. In contrast, when an element is referred to as being "directly on," "directly connected to" or "directly coupled to" another element or layer, there are no intermediate elements or layers. The same reference numerals always represent the same element. As used herein, the term "or" and the term "and / or" include any and all combinations of one or more of the associated listed items.

[0059] As used herein, the terms "first," "second," and the like are used as labels for the nouns that follow them, and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.) unless explicitly defined as such. In addition, the same reference numerals may be used in two or more figures to refer to parts, components, blocks, circuits, units, or modules having the same or similar functions. However, such use is only for simplicity of illustration and ease of discussion; it does not mean that the construction or architectural details of such components or units are the same in all embodiments, or that such commonly referenced components / modules are the only way to implement some example embodiments disclosed herein.

[0060] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those skilled in the art to which the subject matter belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such in this article.

[0061] As used herein, the term "module" refers to any combination of software, firmware, and / or hardware configured to provide the functionality described herein in conjunction with the module. For example, software may be implemented as a software package, code, and / or instruction set or instructions, and the term "hardware" as used in any embodiment described herein may include, for example, components, hardwired circuits, programmable circuits, state machine circuits, and / or firmware storing instructions executed by programmable circuits, alone or in any combination. Modules may be implemented collectively or individually as circuits that form part of a larger system, such as, but not limited to, an integrated circuit (IC), a system on a chip (SoC), a component, etc.

[0062] Any suitable hardware, firmware (e.g., application specific integrated circuit (ASIC)), software, or a combination of software, firmware, and hardware may be used to implement the electronic or electrical devices and / or any other related devices or components according to the embodiments of the present disclosure described herein. For example, the various components of these devices may be formed on an integrated circuit (IC) chip or on a separate IC chip. In addition, the various components of these devices may be implemented on a flexible printed circuit film, a tape carrier package (TCP), a printed circuit board (PCB), or the various components of these devices may be formed on a substrate. In addition, the various components of these devices may be processes or threads running on one or more processors in one or more computing devices, which execute computer program instructions and interact with other system components for performing the various functions described herein. The computer program instructions are stored in a memory, which may be implemented in a computing device using a standard memory device (such as, for example, a random access memory (RAM)). The computer program instructions may also be stored in other non-temporary computer-readable media, such as, for example, a CD-ROM, a flash drive, etc. In addition, those skilled in the art should recognize that the functionality of various computing devices may be combined or integrated into a single computing device, or the functionality of a particular computing device may be distributed across one or more other computing devices without departing from the spirit and scope of the example embodiments of the present disclosure.

[0063] As discussed above, modern communication devices (e.g., mobile phones, vehicles, laptops, satellites, etc.), also referred to as user equipment (UE), can communicate with a network node (e.g., a base station) to receive data from a network associated with the network node and to send data to a network associated with the network node. Data can be sent via one or more transmit and receive points (TRPs) associated with the network node. The transmission of the same signal from multiple TRPs to a UE can be referred to as a joint transmission. Joint transmission can allow interference suppression and improved received signal quality. Under the UTCI framework, a UE can be set to only one TCI state. For example, the UTCI framework can specify that all channels and resources used for transmission follow an indicated TCI state. By simplifying (e.g., by reducing) the number of available TCI states for transmission, the UTCI framework can allow more efficient communication between a network node and a UE.

[0064] Figure 1 is a block diagram depicting a system for joint transmission in a UTCI framework (eg, for configuring a joint transmission) according to some embodiments of the present disclosure.

[0065] Reference Figure 1, system 1 may include a UE 105 and a network node 110 (e.g., a gNodeB, also referred to as a “base station”) in communication with each other. UE 105 may include a radio 115 and means for processing. The means for processing may include a processing circuit 120, which may perform various methods disclosed herein (e.g., Figure 5 , Figure 6 , Fig. 9 , Fig. 10B , Fig.11 , Fig.14 and Fig.16 The radio 115 may correspond to the communication module 1790 (see Fig.17 ). The processing circuit 120 may correspond to the processor 1720 (see Fig.17 ). The processing circuit 120 may receive a transmission from the network node 110 via the radio 115, and the processing circuit 120 may send a signal to the network node 110 via the radio 115. The transmission from the network node 110 may be provided to the UE 105 via a downlink (DL) transmission 10. The transmission from the UE 105 may be provided to the network node 110 via an uplink (UL) transmission 20. Aspects of some embodiments of the present disclosure are associated with configuring a channel state information reference signal (CSI-RS) resource, which is used by the UE 105 as a channel measurement resource (CMR) for a multi-TRP (MTRP, also written as mTRP) transmission based on a single downlink control information (S-DCI) associated with a UTCI framework (e.g., a UTCI scheme). In some embodiments, the network node 110 may include one or more transmit and receive points (TRPs) 50 in communication with the UE 105. Although the present disclosure discusses two TRPs located at the same network node, it should be understood that the present disclosure is not limited to this. For example, system 1 may include any number of TRPs located at any number of network nodes 110 communicating with one or more UEs 105.

[0066] In some embodiments, as part of the configuration process, UE 105 may perform capability signaling. For example, UE 105 may receive a capability request from network node 110. UE 105 may respond to the capability request by sending information to network node 110. The information may include capability information indicating the UE's ability to perform one or more features. For example, UE 105 may send the capability information to network node 110 via UL transmission 20. Based on the capability information, network node 110 may configure resources for UE 105. Network node 110 may send the resources to UE 105 via DL transmission 10.

[0067] Figure 2 is a block diagram depicting resource grouping in a system for joint transmission in a UTCI framework according to some embodiments of the present disclosure.

[0068] refer to Figure 2 , the system 1 may provide a joint transmission from the network node 110 to the UE 105. In the 3rd Generation Partnership Project (3GPP) framework, a joint transmission (JT) scheme refers to simultaneous data transmission to the same UE by the network node 110 in collaboration with a group of multiple TRPs 50 (also referred to as cooperative TRPs). As described above, joint transmission may allow interference suppression and improvement of the quality of received signals associated with simultaneous data transmission. Joint transmission may be classified into CJT and NCJT. In CJT, each participating TRP may send signals in a manner that may be considered synchronized across all participating TRPs. In NCJT, each participating TRP may send signals in a manner that may be considered asynchronous with respect to each other. CJT assumes that the network node 110 has detailed channel state information (CSI) for service links from all cooperative TRPs associated with sending signals to the UE 105. In CJT, the transmitted signals from different TRPs may be jointly precoded (e.g., by the network node 110) using prior information of phase synchronization across the TRPs. Joint precoding may allow system 1 to achieve coherent combining at the served UE (e.g., at UE 105). In contrast, system 1 assumes non-ideal backhaul conditions for NCJT, where full synchronization of all cooperating TRPs may not be feasible (e.g., may not be provided). In NCJT, transmit signals from different TRPs are precoded non-coherently across TRPs (e.g., by TRP). Precoding refers to a signal processing technique applied across cooperating TRPs within a system to improve the quality and reliability of data transmission and to enable successful decoding of information associated with the joint transmission.

[0069] In Release 17 of 3GPP, dynamic channel assumption and interference assumption CSI measurement and reporting are discussed and introduced for NCJT transmission. In Release 17 CSI enhancement for NCJT MTRP transmission, UE 105 may be configured with a CSI-RS resource set S, where the CSI-RS resource set S includes K s ≥2 (e.g., at least two) non-zero power (NZP) CSI-RS resources as CMRs for measurement assumptions associated with a single TRP. The UE 105 may be configured with N≥1 (e.g., at least one) NZP CSI-RS resource pairs. sK refers to the number of CSI-RS resources, and each resource pair may be used as one CMR for the NCJT measurement hypothesis. All CMRs in a CSI-RS resource set may have (e.g., may correspond to) the same number of ports. The association of different TRPs with CMRs (e.g., association of different TCI states) may be done at the resource level. For example, in order to associate different TRPs 50 with CMRs at the resource level, the UE 105 may be configured with two CMR groups, a first CMR group G1 and a second CMR group G2, corresponding to the first TRP 50a and the second TRP 50b, respectively, where K s =K 1 +K 2 , K 1 and K 2 The number of CMRs in the first CMR group G1 and the number of CMRs in the second CMR group G2, respectively. For example, the first CMR group G1 may include a first resource RSa1 and a second resource RSa2 associated with the first TRP 50a. The second CMR group G2 may include a first resource RSb1 and a second resource RSb2 associated with the second TRP 50b. The CMR pairs for the NCJT measurement hypothesis may be determined by selecting a resource per CMR group. This protocol from Release 17 (hereinafter, "NCJT Grouping Protocol") provides NCJT grouping. NCJT grouping allows UE 105 to associate resources with specific TRPs for S-DCI-based MTRPs.

[0070] The NCJT packet protocol indicates the following. For CSI measurements associated with a reporting setting for NCJT (e.g., CSI-ReportConfig), the UE may be configured with Ks≥2 NZP CSI-RS resources and N≥1 NZP CSI-RS resource pairs in the CSI-RS resource set for CMR, where each resource pair may be used for the following NCJT measurement assumptions. The UE may use K s =K 1 +K 2 The CMRs are configured with two CMR groups. A CMR pair may be determined from the two CMR groups by one or more of the following methods. 1 and K 2 K may be (eg, may represent) the number of CMRs in the two CMR groups, respectively. 1 Can be equal to K 2 In some embodiments, K 1 Different from K 2 The CMRs in each CMR group can be used for NCJT and single TRP measurement assumptions. N CMR pairs can be configured by higher layers by selecting from all possible resource pairs. N = 1 and K can be supported s= 2. For CPU occupancy, resource occupancy and / or port occupancy, the NCJT assumption can be considered separately from the single TRP assumption.

[0071] Due to the adoption of cloud (also known as "centralized") radio access network (C-RAN) architecture in real networks and facing the rapidly growing demand for CJT MTRP transmission, in Release 18 of 3GPP, additional enhancements to the CSI measurement and reporting framework were discussed and introduced for CJT MTRP transmission. Following the same approach as in the Release 17 CSI enhancements for NCJT, Release 18 indicates that the UE can be configured with a CSI-RS resource set including K>1 (e.g., more than one) NZP CSI-RS resources as CMRs, where each resource in the CMR can correspond to a TRP or a TRP group. All CMRs in the resource set can have the same number of ports, and the association of different TRPs (e.g., different TCI states) with the CMRs can be done at the resource level. This protocol from Release 18 (hereinafter, "CJT Grouping Protocol") provides CJT grouping. CJT grouping allows UE 105 to associate resources with specific TRPs for S-DCI-based MTRPs.

[0072] The CJT grouping protocol dictates the following. For Release 18 Type II codebook refinement for CJT multi-TRP (mTRP) with NTRP>1 TRP / TRP group, the following may be supported. A CMR may include K>1 NZP CSI-RS resources, where one resource corresponds to one TRP or one TRP group (e.g., K=NTRP). Each of the CSI-RS resources may have the same number of CSI-RS ports.

[0073] UE capability signaling refers to a mechanism that can be used by the UE 105 to inform the network node 110 of the UE 105's ability to perform certain features. For example, the UE can signal its ability to perform certain features via a given UE capability signaling mechanism. As described above, as part of the configuration process, the UE 105 can send capability information for performing capability signaling. For example, the network node 110 can configure CMRs for use by the UE 105 based on the capability information provided by the UE 105. The network node 110 can transmit the CMRs via the DL transmission 10 (e.g., see Figure 1 ) sends a capability request to UE 105. UE 105 may transmit a capability request via UL transmission 20 (e.g., see Figure 1 ) sends capability information to the network node 110. The CMR may be provided by the network node 110 via a DL transmission 10.

[0074] UE 105 may report its capabilities using one or more of the following mechanisms in accordance with 3GPP. UE 105 may report its capabilities to perform certain features in any scenario. For example, the UE may report its capabilities on a per-UE basis, indicating that the UE 105 may perform the reported capabilities in any scenario (e.g., in any given frequency band, etc.). UE 105 may report its capabilities to perform certain features in a specific frequency band. For example, the UE may report its capabilities on a per-band basis, indicating that the UE 105 may perform the reported capabilities in a specific frequency band. The UE may report its capabilities to perform certain features in a specific frequency band combination used for carrier aggregation (CA). For example, the UE may report its capabilities on a per-band combination (or per BC) basis, indicating that the UE 105 may perform the reported capabilities in a specific frequency band combination. The UE may report its capabilities to perform certain features in one or more specific frequency bands in a specific frequency band combination used for CA. For example, a mechanism called feature sets may be used to allow such flexibility in reporting, and the UE may report its capabilities on a per-feature set (or per-FS) basis, indicating that the UE 105 may perform the reported capabilities in one or more specific bands in a specific band combination. The UE may report its capabilities to perform certain features in one or more specific component carriers (CCs) in a specific band combination used for CA. For example, a mechanism called per-CC feature sets may be used to allow such flexibility in reporting, and the UE may report its capabilities on a per-CC per-feature set (or per-FSPC) basis, indicating that the UE 105 may perform the reported capabilities in one or more specific CCs in a specific band combination. A band combination refers to a collection of frequency bands used to represent a CA configuration (e.g., as described in 3GPP specification 38.101).

[0075] The flexibility of the UE for declaring support for certain features (e.g., for sending capability information) may be increased from a per-UE basis to a per-band basis, to a per-band combination (or per-BC) basis, to a per-feature set (or per-FS) basis, to a per-CC per-feature set (or per-FSPC) basis. For example, if feature A and feature B are for FSPC, the UE may have full flexibility to support only one of features A and B in each CC. However, if those features are for the UE, the UE may only support or only not support a given feature. The cost of increased flexibility is greater signaling overhead. Therefore, when determining how UE support for certain features may be declared (e.g., signaled), the complexity of the given feature in the UE implementation and the associated signaling overhead may be considered.

[0076] NCJT proposal

[0077] Figure 3is a diagram depicting a table entry from the Radio Access Network 1 (RAN1) UE Features List for Index Number 40-1-3. RAN1 is a group within 3GPP associated with determining standards for signaling and physical layers.

[0078] Figure 4A is a diagram depicting a table entry from the RAN1 UE Features List for index number 23-7-1.

[0079] Figure 4B is a diagram depicting the definition of parameters associated with the RAN1 UE Features List for Index Number 23-7-1.

[0080] It should be understood that for convenience, selection table entries from the RAN1 UE feature list are provided herein. A person skilled in the art will understand the contents of the table and how to find the information contained therein.

[0081] Reference Figure 3 , with the extension of the UTCI framework for S-DCI-based mTRP, RAN1 agrees to introduce a radio resource control (RRC) configuration in the CSI-AssociatedReportConfigInfo of the CSI-AperiodicTrigger State for each CSI-RS resource set or for each CSI-RS resource in each aperiodic CSI-RS resource set to inform the UE to apply the first indicated joint (or DL) TCI state or the second indicated joint (or DL) TCI state to the CSI-RS resource when the aperiodic CSI-RS resource set for CSI / beam management (BM) is configured to follow the UTCI state. Therefore, RAN1 agrees on the UE features associated with index number 40-1-3, such as Figure 3 As shown, component candidate values ​​indicating "per resource" and "per resource set" (e.g., see Figure 3 13th column of the ).

[0082] Because the configuration of "per CSI-RS resource set" or "per CSI-RS resource" depends on the capabilities of a given UE, there may be ambiguity (e.g., uncertainty) regarding the UE behavior when the UE is configured to apply the UTCI framework with per-resource set (rather than per-resource) capabilities for a non-periodic CSI-RS resource set with configuration of two or more resource groups for NCJT CSI measurement and / or NCJT CSI reporting. For example, because UE 105 (see Figure 2) is configured with more than one resource group (e.g., a first CMR group G1 and a second CMR group G2) in a CSI-RS resource set S, so a UE 105 configured for per-resource-set capability will face ambiguity (e.g., uncertainty) about how to associate one indicated TCI state (e.g., one UTCI) with more than one configured CMR group in a set. In contrast, if the UE 105 is configured for per-resource capability, the UE 105 may associate the first CMR group G1 with the first indicated TCI state and the second CMR group G2 with the second indicated TCI state.

[0083] To resolve this ambiguity, the RAN1#114 conference agreement indicates the following solution. On the UTCI framework extension, if the UE supports NCJT CSI, the UE may support resource-level RRC configuration to notify the UE that the first indicated joint (or DL) TCI state or the second indicated joint (or DL) TCI state should be applied to the non-periodic (AP) CSI-RS resource.

[0084] However, as in UE Feature Group (FG) 40-1-3, the RAN1#114 protocol implicitly bundles support for the NCJT scheme with per-CSI-RS resource configuration for TCI selection in S-DCI-based MTRP. Accordingly, an alternative approach may be implemented to avoid limiting a given UE to implicit bundling of support for NCJT with per-resource configuration in the UTCI framework.

[0085] In some embodiments, via FG 23-7-1 (see Figure 4A and Figure 4B ) (or similar feature group) UE 105 supporting the NCJT scheme may reject UE feature FG 40-1-3 (or similar feature group).

[0086] For example, in some embodiments, the UE may follow a rule that support for NCJT is conditional on the UE supporting resource-level radio resource control (RRC) configuration. For example, the UE may know the rule by default (support for NCJT is conditional on the UE supporting resource-level RRC configuration) (e.g., the rule may be programmed into the UE). The resource-level RRC configuration may indicate that the UE is to apply a first indicated transmission configuration indicator (TCI) state or a second indicated TCI state to a non-periodic channel state information reference signal (APCSI-RS) resource. The UE may send capability information based on the rule that support for CJT is conditional on the UE supporting resource-level RRC configuration. The capability information may include a refusal to execute FG 40-1-3 in the UTCI framework.

[0087] However, such an embodiment may result in under-reporting from the UE 105, since the UE 105 may have indicated "per resource set" for FG 40-1-3 of the UTCI framework supporting CSI-RS transmission in any other scheme than NCJT.

[0088] For illustration, if the granularity of these two UE features FG 40-1-3 and FG 23-7-1 is per FS (indicating the ability of the UE to perform reporting in one or more specific CCs in a specific band combination), then UE management reporting will be feasible, so that simultaneous support for both the NCJT scheme and the "per resource set" for TCI selection in one CC and / or in one band will be enabled. However, due to the fact that the granularity of FG 23-7-1 and FG 40-1-3 is per band (see Figure 3 The 9th column and Figure 4B ), so the UE may have no other options except to under-report the UE's capabilities for certain frequency bands. In such cases, the network node 110 may only use the traditional TCI status frame for CSI-RS transmission.

[0089] To solve the problem of under-reporting, the following three methods are discussed.

[0090] Figure 5 is a flow chart depicting a method for configuring NCJT in a UTCI framework based on UE indication “per resource set” according to some embodiments of the present disclosure.

[0091] In some embodiments, a UE that supports NCJT but does not support joint operation of NCJT and UTCI CSI-RS transmission may indicate “per resource set” for FG 40-1-3. In such an embodiment, the network may not jointly configure NCJT and UTCI framework for the UE.

[0092] For example, and with reference to Figure 5In some embodiments, a UE that supports FG 23-7-1 (or a similar feature) and does not support joint operation of NCJT and UTCI CSI-RS transmissions (e.g., a UE that supports only one selected from NCJT and UTCI CSI-RS transmissions for a given transmission at a given time) may perform method 500 for configuring joint transmission (e.g., NCJT) in a UTCI framework. Method 500 may include one or more of the following operations. The UE may receive a capability request associated with a UTCI framework from a network node (operation 501). The UE may send a transmission including information (e.g., capability information) indicating a "per resource set" capability for FG 40-1-3 (or a similar feature) (operation 502). The "per resource set" capability may indicate that the UE is capable of associating CSI-RS resources with TCI states at the resource set level. FG 40-1-3 indicates that the UE is configured to support per-aperiodic CSI-RS resource configuration and / or per-aperiodic CSI-RS resource set configuration for TCI selection in S-DCI-based MTRP (e.g., see Figure 3 4th column of ).

[0093] In some embodiments, the network may jointly configure the NCJT and UTCI frameworks, while the CSI-RS transmission configuration is based on the traditional TCI state framework. However, such embodiments may violate the RAN1 protocol that the UE will support "per CSI-RS resource" configuration to support the NCJT scheme.

[0094] Figure 6 is a flow chart depicting a method for configuring NCJT in a UTCI framework based on UE indicating individual capabilities according to some embodiments of the present disclosure.

[0095] Another alternative would be to introduce separate capabilities for joint operation of NCJT CSI scheme and UTCI CSI-RS for S-DCI based MTRP for UEs indicating "per resource" for FG 40-1-3. For such embodiments, separate capabilities may be introduced for joint operation of NCJT scheme and UTCI CSI-RS transmission. The signaling granularity of the separate UE capabilities may be as low as per UE.

[0096] For example, and refer to Figure 6In some embodiments, a UE may receive a capability request associated with a UTCI framework from a network node (operation 601). The UE may send information (e.g., capability information) indicating a capability per resource for FG 40-1-3 (or similar features) under the UTCI scheme (operation 602). The "per resource" capability may indicate that the UE is able to associate CSI-RS resources with TCI states at the resource level. The UE may also send information (e.g., capability information) indicating support for a separate capability to support joint operation of NCJT (e.g., NCJT CSI) and per-nonperiodic UTCI CSI-RS resource configuration for TCI selection (operation 603). The granularity of support for the separate capability may be as low as the per-UE granularity, thereby indicating that the UE is able to perform the separate capability in any scenario.

[0097] Figure 7 It is a description of some embodiments of the present disclosure for Figure 6 A diagram of possible table entries (with index numbers such as 40-1-A) depicting individual capabilities discussed and in a format associated with a RAN1 UE feature list. For example, the letter "A" may be replaced by an unused index number ending.

[0098] Reference Figure 7 , the 2nd column associated with the RAN1 format may indicate an index number (e.g., 40-1-A). The 3rd column may indicate: joint operation of NCJT CSI and per-non-periodic CSI-RS resource configuration for TCI selection in S-DCI-based MTRP. The 4th column may indicate: support for joint operation of NCJT CSI and per-non-periodic CSI-RS resource configuration for TCI selection in S-DCI-based MTRP. The 5th column may indicate a prerequisite feature group, including 23-7-1 and 40-1-3. The 9th column may indicate the type per UE (e.g., supported granularity). The 14th column may indicate that the feature (e.g., 40-1-A) is optional for capability signaling (also known as "capability signaling").

[0099] It should be understood that the column numbers and headings are based on the corresponding columns and headings in the relevant RAN1 UE feature list. For example, although columns 1, 6-8, and 10-13 of the potential RAN1 UE feature list are not shown, those skilled in the art will understand what the provided and omitted columns indicate in the relevant RAN1 UE feature list throughout this disclosure.

[0100] CJT Proposal

[0101] Figure 8 is a diagram depicting a table entry from the RAN1 UE feature list for index number 40-1-4.

[0102] Reference Figure 8, with the extension of the UTCI framework for CJT-based MTRP, RAN1 reached the following agreement reflected in FG 40-1-4 (at RAN1#110be) to support up to two UTCI states for CJT schemes based on UE capabilities in bandwidth part (BWP) / CC.

[0103] RAN1#110be protocol indicates that on the UTCI framework extension, up to two joint TCI states may be indicated via the Media Access Control-Control Element (MAC-CE) / DCI and applied to CJT-based physical downlink shared channel reception (PDSCH-CJT) in a BWP / CC configured with a joint DL TCI mode or a joint UL TCI mode. Whether one or two indicated joint TCI states for PDSCH-CJT are supported may depend on the capabilities of the UE. Quasi-co-location (QCL) type and / or assumption of the indicated joint TCI states may be applied to PDSCH-CJT. The UE may determine which indicated joint TCI states target channels and / or signals in the BWP / CC based on 3GPP Agenda Item (AI) 9.1.1.1. Therefore, UE Feature 40-1-4 is agreed to, as Figure 8 For example, Figure 8 The 4th column of indicates that FG 40-1-4 indicates that the UE is capable of performing a feature of supporting two TCI states for a CJT transmission (Tx) scheme for a physical downlink shared channel (PDSCH).

[0104] In the UTCI framework for MTRP transmission, for non-periodic CSI-RS resource sets for CSI / BM configured to follow UTCI states, RAN1 reached the following agreement (at RAN1#112be), wherein an RRC configuration is introduced for each CSI-RS resource set or for each CSI-RS resource in each set to notify (e.g., declare) the UE that a first indicated joint (or DL) TCI state will be applied or a second indicated joint (or DL) TCI state will be applied.

[0105] The RAN1#112be protocol indicates that on the UTCI framework extension for S-DCI-based MTRP, an RRC configuration may be provided in the CSI-AssociatedReportConfigInfo of the CSI-AperiodicTrigger State for each CSI-RS resource set or for each CSI-RS resource in each aperiodic CSI-RS resource set to notify the UE to apply the first indicated joint (or DL) TCI state or the second indicated joint (or DL) TCI state to the CSI-RS resource when the aperiodic CSI-RS resource set for CSI / BM is configured to follow the UTCI state. If the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set is equal to or greater than a threshold (if the threshold is appropriate), the RRC configuration may be provided in the CSI-AssociatedReportConfigInfo of the CSI-AperiodicTrigger State for each CSI-RS resource set or for each CSI-RS resource in each aperiodic CSI-RS resource set. In the case where the UE is configured with CSI-RS resource sets, for an aperiodic CSI-RS resource set configured with two resource groups for NCJT CSI and configured to follow the UTCI state, if the RRC configuration is not provided for the aperiodic CSI-RS resource set, the UE may apply the first indicated joint (or DL) TCI state to the CSI-RS resources in group 1 and may apply the second indicated joint (or DL) TCI state to the CSI-RS resources in group 2. The UE may determine whether to use "per CSI-RS resource set" or "per CSI-RS resource" based on the capabilities of the UE. The configuration of "per CSI-RS resource set" or "per CSI-RS resource" may depend on the configuration of the aperiodic CSI-RS resource set configured with two resource groups for NCJT CSI and configured to follow the UTCI state. Figure 3 )’s UE capabilities.

[0106] As described above, RAN1 has reached an agreement for the CJT scheme with UE capabilities to support up to two UTCI states. If the UE supports only one UTCI state for the CJT scheme via FG 40-1-4, there is no ambiguity about the UE behavior when the non-periodic CSI-RS resource sets used for CJT CSI measurement and / or reporting are configured in FG 40-1-3 to follow the UTCI state with "per resource set" capability. However, when the UE indicates support for more than one UTCI state for the CJT scheme via FG 40-1-4 and the UE is configured to follow the UTCI state with "per resource set" capability in FG 40-1-3 for the configured non-periodic CSI-RS resource sets for CJT CSI measurement / reporting, there may be ambiguity (e.g., uncertainty) about the UE behavior in a manner similar to the ambiguity discussed above with respect to NCJT.

[0107] To resolve UE behavior ambiguity, in some embodiments, UE behavior rules may be defined such that when the UE is configured to follow a UTCI state with "per resource set" capability and with the capability of two UTCI states in a CJT scheme, the UE may apply a first indicated joint (or DL) TCI state to the CSI-RS resources in group 1, and may apply a second indicated joint (or DL) TCI state to the CSI-RS resources in group 2 for CJT CSI measurement and / or reporting, wherein the resources in group 1 correspond to a first TRP (or a first TRP group) associated with the first UTCI state, and the resources in group 2 correspond to a second TRP (or a second TRP group) associated with the second UTCI state.

[0108] Fig. 9 is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE associating an indicated UTCI state with respective relevant TRPs according to some embodiments of the present disclosure.

[0109] refer to Fig. 9 In some embodiments, and as described above, a UE configured to follow the UTCI state with "per resource set" capability and with two UTCI states in the CJT scheme may perform a method 900 for configuring CJT in the UTCI framework. The method may include one or more of the following operations.

[0110] The UE may comply with a rule that support for CJT is conditional on the UE supporting a resource-level RRC configuration, the resource-level RRC configuration indicating that the UE is to apply a first indicated TCI state (e.g., a first indicated UTCI state) or a second indicated TCI state (e.g., a second indicated UTCI state) to non-periodic CSI-RS resources (operation 901). For example, the UE may know the rule by default (e.g., the rule may be programmed into the UE). The UE may send first capability information based on the rule that support for CJT is conditional on the UE supporting a resource-level RRC configuration (operation 902). The first capability information may include information indicating support for UTCI with a capability of two or more UTCI states per resource set. For CJT measurement or reporting, the UE may apply the first indicated UTCI state to the CSI-RS resources in the first group and / or may apply the second indicated UTCI state to the CSI-RS resources in the second group (operation 903). The CSI-RS resources in the first group may correspond to a first TRP (or a first TRP group) associated with a first indicated UTCI state (the CSI-RS resources in the first group may be sent from the first TRP (or the first TRP group)). The CSI-RS resources in the second group may correspond to a second TRP (or a second TRP group) associated with a second indicated UTCI state (e.g., the CSI-RS resources in the second group may be sent from the second TRP (or the second TRP group)).

[0111] To generalize this rule, in some embodiments, when the UE is configured to follow the UTCI state with "per resource set" capability in FG 40-1-3 and the UTCI state with k>1 UTCI state capability in the CJT scheme in FG 40-1-4, the UE may apply the k-th indicated joint (or DL) TCI state to the CSI-RS resources in the k-th group, where the resources in each group correspond to TRPs / TRP groups sharing the same QCL assumption.

[0112] Fig. 10A is a diagram depicting possible table entries (eg, with index numbers 40-1-B) for potential individual capabilities depicted in a format associated with a RAN1 UE feature list according to some embodiments of the present disclosure. For example, the letter "B" may be replaced with an unused index number ending.

[0113] In some embodiments, when the UE indicates "per resource" for 40-1-3, a separate capability for the joint operation of the CJT scheme and UTCI CSI-RS can be used to implement the UE behavior rules. A separate capability can be introduced for the joint operation of the CJT scheme and UTCI CSI-RS transmission, such as Fig. 10A As shown (e.g., as FG 40-1-B). For example, Fig. 10AColumn 4 of indicates: supporting joint operation of CJT CSI and per-aperiodic CSI-RS resource configuration for TCI selection in S-DCI based MTRP.

[0114] Fig. 10B is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE indicating separate capabilities for joint operation of CJT and UTCI according to some embodiments of the present disclosure.

[0115] refer to Fig. 10B In some embodiments, and as described above, the UE may perform the method 1000 for configuring CJT in the UTCI framework. The method may include one or more of the following operations.

[0116] The UE may send information indicating a capability (or similar feature) per resource for FG 40-1-3 associated with UTCI (operation 1001). The UE may send a separate capability indicating that the UE can support joint operation of CJT CSI and UTCI transmission (operation 1002). For example, the UE may send a separate capability indicating that the UE can support joint operation of CJT CSI and per-aperiodic UTCI CSI-RS resource configuration for TCI selection in S-DCI-based MTRP.

[0117] In some embodiments, support for CJT CSI may be conditional on support for resource-level RRC configuration for signaling that the UE may apply a first indicated joint (or DL) TCI or a second indicated joint (or DL) TCI state to a non-periodic CSI-RS resource. However, in such embodiments, support for the CJT scheme may be implicitly bundled with more than one UTCI state and per-CSI-RS resource configuration for TCI selection.

[0118] Fig.11 is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE's refusal to perform a given feature according to some embodiments of the present disclosure.

[0119] In some embodiments, to address potential implicit bundling issues, a UE that supports the CJT scheme via FG 40-3-1-1 and / or 40-3-1-5 and supports more than one unified TCI state for CJT via FG 40-1-4 may reject UE feature FG 40-1-3.

[0120] For example, and refer to Fig.11A UE supporting the CJT scheme via FG 40-3-1-1 and / or 40-3-1-5 and supporting more than one unified TCI state for CJT via FG 40-1-4 may perform method 1100 for configuring CJT in the UTCI framework to resolve implicit bundling. Method 1100 may include one or more of the following operations.

[0121] The UE may comply with a rule that support for CJT is conditional on the UE supporting a resource-level RRC configuration, the resource-level RRC configuration indicating that the UE is to apply a first indicated TCI state (e.g., a first indicated UTCI state) or a second indicated TCI state (e.g., a second indicated UTCI state) to an aperiodic CSI-RS resource (operation 1101). The UE may send first capability information based on the rule that support for CJT is conditional on the UE supporting a resource-level RRC configuration (operation 1102). The first capability information may include information for refusing to perform FG 40-1-3 (or similar features) associated with UTCI.

[0122] Fig. 12A is a diagram depicting a table entry from the RAN1 UE feature list for index number 40-3-1-1.

[0123] Fig. 12B is a diagram depicting additional table entries from the RAN1 UE feature list for index number 40-3-1-1.

[0124] Fig.13A is a diagram depicting a table entry from the RAN1 UE feature list for index number 40-3-1-5.

[0125] Fig. 13B is a diagram depicting additional table entries from the RAN1 UE Features List for index number 40-3-1-5.

[0126] Fig. 13C is a diagram depicting a table entry from the RAN1 UE feature list for index number 2-35, which is listed as a prerequisite feature group in the table entry from the RAN1 UE feature list for index numbers 40-3-1-1 and 40-3-1-5.

[0127] Fig.13D is a diagram depicting additional table entries from the RAN1 UE feature list for index numbers 2-35.

[0128] In this case, based on the UE's refusal to perform FG 40-1-3, the network node (e.g., gNB) may use only the legacy TCI status frame for CSI-RS transmission. However, this approach may be an under-reporting (e.g., may be a conservative reporting) from the UE, where the UE may have already performed FG 40-1-3 for the UTCI frame that supports CSI-RS transmission in any other scheme besides CJT (and / or NCJT) (see Figure 3 ) indicates "per resource set".

[0129] For example, if the granularity of these UE features is per FS, UE management reporting may be feasible, so that it is possible to allow both CJT schemes with more than one UTCI state and "per resource set" for TCI selection in one CC and / or band to be supported simultaneously. Because the granularity of FG 40-3-1-1 and FG 40-3-1-5 is per band and per BC (see Fig. 12B and Fig. 13B 9 in ) and due to the fact that the granularity of FG 40-1-3 is per frequency band (see Figure 3 ), so there may still be a problem of under-reporting of UE's capabilities for some frequency bands.

[0130] To address the under-reporting issue, in some embodiments, as discussed similarly above with respect to the NCJT proposal, a UE that supports CJT with more than one UTCI state and does not support joint operation of a CJT scheme with more than one UTCI state and UTCI CSI-RS transmission may indicate "per resource set" for UE feature 40-1-3. In such an embodiment, the network may not jointly configure a CJT scheme with more than one UTCI state or more than one UTCI framework for the UE. In some embodiments, the network may jointly configure the CJT scheme and the UTCI framework, while the CSI-RS transmission configuration may be based on the traditional TCI state framework.

[0131] Fig.14 is a flow chart depicting a method for configuring CJT in a UTCI framework based on UE indication “per resource set” according to some embodiments of the present disclosure.

[0132] refer to Fig.14 , a UE that supports the CJT scheme via FG 40-3-1-1 and / or 40-3-1-5 and supports more than one unified TCI state for CJT via FG 40-1-4 but does not support joint operation of CJT with more than one UTCI state and UTCI CSI-RS transmission may perform method 1400 for configuring CJT in the UTCI framework to resolve implicit bundling. Method 1400 may include one or more of the following operations.

[0133] The UE may comply with a rule that support for CJT is conditional on the UE supporting a resource-level RRC configuration, the resource-level RRC configuration indicating that the UE is to apply a first indicated TCI state (e.g., a first indicated UTCI state) or a second indicated TCI state (e.g., a second indicated UTCI state) to a non-periodic CSI-RS resource (operation 1401). The UE may send first capability information based on the rule that support for CJT is conditional on the UE supporting a resource-level RRC configuration (operation 1402). The first capability information may include information indicating a "per resource set" capability for FG 40-1-3.

[0134] Fig.15 is a diagram depicting possible table entries (eg, with index numbers 40-1-C) for potential individual capabilities depicted in a format associated with a RAN1 UE feature list according to some embodiments of the present disclosure. For example, the letter "C" may be replaced with an unused index number ending.

[0135] refer to Fig.15 In some embodiments, a separate capability may be introduced for joint operation of CJT and UTCI CSI-RS transmission. For example, when a UE is directed to FG 40-1-3 (see Figure 3 ) indicates "per resource" and for FG 40-1-4 (see Figure 8 ) indicates more than one UTCI state for the CJT scheme, a separate capability may be introduced for the joint operation of the CJT scheme with more than one unified TCI state and more than one UTCI CSI-RS transmission. Fig.15 Column 4 of indicates support for joint operation of CJT CSI with more than one unified TCI state and per-aperiodic CSI-RS resource configuration for TCI selection in S-DCI based MTRP.

[0136] Fig.16 is a flow chart depicting a method for configuring CJT in a UTCI framework based on a UE indicating separate capabilities for joint operation of CJT and UTCI with more than one UTCI state according to some embodiments of the present disclosure.

[0137] refer to Fig.16 In some embodiments, and as described above, the UE may perform method 1600 for configuring CJT in the UTCI framework. The method may include one or more of the following operations.

[0138] In some embodiments, the UE may send information indicating a capability of more than one UTCI state for CJT per resource for FG 40-1-3 and for 40-1-4 (operation 1601). The UE may also send information indicating support for a separate capability (e.g., a second feature) (operation 1602). The separate capability may indicate that the UE is capable of supporting joint operation of CJT and UTCI CSI-RS transmission with more than one UTCI state. For example, the separate capability may indicate that the UE is capable of supporting joint operation of CJT with more than one UTCI state and per-non-periodic UTCI CSI-RS resource configuration for TCI selection.

[0139] Method 500 (regarding NCJT) and method 1600 (regarding CJT) may be indicated by a note that mentions both NCJT and CJT and states that when the UE also supports NCJT CSI under 23-7-1 or CJT CSI under 40-1-4, declaring a component value {per resource set} indicates that joint operation of NCJT or CJT is not supported. For example, and as Figure 3 As indicated in column 13 of , when a UE supports NCJT CSI under 23-7-1 or CJT CSI under 40-1-4, a system including the UE may expect the UE to support "per resource" when configuring the corresponding NCJT CSI or CJT CSI.

[0140] Fig.17 is a block diagram of an electronic device in a network environment according to some embodiments of the present disclosure.

[0141] refer to Fig.17, the electronic device 1701 in the network environment 1700 may communicate with the electronic device 1702 via a first network 1798 (e.g., a short-range wireless communication network), or communicate with the electronic device 1704 or the server 1708 via a second network 1799 (e.g., a long-range wireless communication network). The electronic device 1701 may communicate with the electronic device 1704 via the server 1708. The electronic device 1701 may include a processor 1720, a memory 1730, an input device 1750, a sound output device 1755, a display device 1760, an audio module 1770, a sensor module 1776, an interface 1777, a haptic module 1779, a camera module 1780, a power management module 1788, a battery 1789, a communication module 1790, a subscriber identification module (SIM) card 1796, and / or an antenna module 1797. In one embodiment, at least one of the components (e.g., display device 1760 or camera module 1780) may be omitted from electronic device 1701, or one or more other components may be added to electronic device 1701. Some of the components may be implemented as a single integrated circuit (IC). For example, sensor module 1776 (e.g., fingerprint sensor, iris sensor, or illumination sensor) may be embedded in display device 1760 (e.g., display).

[0142] The processor 1720 may execute software (eg, program 1740 ) to control at least one other component (eg, hardware or software component) of the electronic device 1701 coupled to the processor 1720 , and may perform various data processing or calculations.

[0143] As at least part of data processing or calculation, the processor 1720 may load commands or data received from another component (e.g., the sensor module 1776 or the communication module 1790) into the volatile memory 1732, may process the commands or data stored in the volatile memory 1732, and may store the resulting data in the non-volatile memory 1734. The processor 1720 may include a main processor 1721 (e.g., a CPU or an application processor (AP)) and an auxiliary processor 1723 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that may operate independently of the main processor 1721 or in conjunction with the main processor 1721. Additionally or alternatively, the auxiliary processor 1723 may be adapted to consume less power than the main processor 1721, or to perform a specific function. The auxiliary processor 1723 may be implemented to be separate from the main processor 1721 or to be a part of the main processor 1721.

[0144] The auxiliary processor 1723 may control at least some of the functions or states related to at least one component (e.g., the display device 1760, the sensor module 1776, or the communication module 1790) opposite to the main processor 1721 when the main processor 1721 is in an inactive (e.g., sleep) state, or control at least some of the functions or states related to at least one component (e.g., the display device 1760, the sensor module 1776, or the communication module 1790) among the components of the electronic device 1701 together with the main processor 1721 when the main processor 1721 is in an active state (e.g., executing an application). The auxiliary processor 1723 (e.g., an image signal processor or a communication processor) may be implemented as a part of another component (e.g., a camera module 1780 or a communication module 1790) that is functionally related to the auxiliary processor 1723.

[0145] The memory 1730 may store various data used by at least one component of the electronic device 1701 (e.g., the processor 1720 or the sensor module 1776). The various data may include, for example, software (e.g., program 1740) and input data or output data for commands associated with the software (e.g., program 1740). The memory 1730 may include a volatile memory 1732 or a non-volatile memory 1734. The non-volatile memory 1734 may include an internal memory 1736 and / or an external memory 1738.

[0146] The program 1740 may be stored as software in the memory 1730 , and may include, for example, an operating system (OS) 1742 , middleware 1744 , or an application 1746 .

[0147] The input device 1750 may receive a command or data to be used by another component (eg, the processor 1720) of the electronic device 1701 from outside (eg, a user) of the electronic device 1701. The input device 1750 may include, for example, a microphone, a mouse, or a keyboard.

[0148] The sound output device 1755 can output sound signals to the outside of the electronic device 1701. The sound output device 1755 may include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as playing multimedia or recording, and the receiver can be used to receive incoming calls. The receiver can be implemented as a part of the speaker or as a separate speaker.

[0149] The display device 1760 may visually provide information to the outside of the electronic device 1701 (e.g., to a user). The display device 1760 may include, for example, a display, a holographic device, or a projector, and may include a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. The display device 1760 may include a touch circuit suitable for detecting a touch, or may include a sensor circuit (e.g., a pressure sensor) suitable for measuring the strength of a force caused by a touch.

[0150] The audio module 1770 may convert sound into an electrical signal and vice versa. The audio module 1770 may obtain sound via the input device 1750, or may output sound via the sound output device 1755 or an earphone of an external electronic device 1702 directly (eg, wired) or wirelessly coupled to the electronic device 1701.

[0151] The sensor module 1776 may detect an operating state (e.g., power or temperature) of the electronic device 1701 or an environmental state (e.g., a state of a user) outside the electronic device 1701. The sensor module 1776 may then generate an electrical signal or data value corresponding to the detected state. The sensor module 1776 may include, for example, a gesture sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, and / or an illumination sensor.

[0152] The interface 1777 may support one or more designated protocols for the electronic device 1701 to be directly (e.g., wired) or wirelessly coupled with the external electronic device 1702. The interface 1777 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0153] The connection terminal 1778 may include a connector via which the electronic device 1701 can be physically connected to the external electronic device 1702. The connection terminal 1778 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

[0154] The haptic module 1779 may convert the electrical signal into mechanical stimulation (eg, vibration or movement) or electrical stimulation that can be recognized by the user via tactile or kinesthetic sense. The haptic module 1779 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0155] The camera module 1780 may capture a still image or a moving image. The camera module 1780 may include one or more lenses, an image sensor, an image signal processor, or a flash. The power management module 1788 may manage the power supplied to the electronic device 1701. The power management module 1788 may be implemented as at least a portion of a power management integrated circuit (PMIC), for example.

[0156] The battery 1789 may supply power to at least one component of the electronic device 1701. The battery 1789 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0157] The communication module 1790 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 1701 and an external electronic device (e.g., electronic device 1702, electronic device 1704, or server 1708), and may support communication via the established communication channel. The communication module 1790 may include one or more communication processors that can operate independently of the processor 1720 (e.g., AP) and can support direct (e.g., wired) communication or wireless communication. The communication module 1790 may include a wireless communication module 1792 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 1094 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate via a first network 1798 (e.g., a short-range communication network such as Bluetooth). TM , Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA) standards) or communicate with an external electronic device via a second network 1799 (e.g., a long-distance communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules may be implemented as a single component (e.g., a single IC), or may be implemented as multiple components separated from each other (e.g., multiple ICs). The wireless communication module 1792 may use user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 1796 to identify and authenticate the electronic device 1701 in a communication network such as the first network 1798 or the second network 1799.

[0158] The antenna module 1797 may transmit or receive a signal or power to or from the outside of the electronic device 1701 (e.g., an external electronic device). The antenna module 1797 may include one or more antennas. The communication module 1790 (e.g., the wireless communication module 1792) may select at least one of the one or more antennas suitable for a communication scheme used in a communication network such as the first network 1798 or the second network 1799. Then, a signal or power may be transmitted or received between the communication module 1790 and the external electronic device via the selected at least one antenna.

[0159] A command or data may be sent or received between the electronic device 1701 and the external electronic device 1704 via a server 1708 coupled to the second network 1799. Each of the electronic devices 1702 and 1704 may be a device of the same type or a different type as the electronic device 1701. All or some operations to be performed at the electronic device 1701 may be performed at one or more of the external electronic devices 1702, 1704, or the server 1708. For example, if the electronic device 1701 should perform a function or service automatically or in response to a request from a user or another device, the electronic device 1701 may request one or more external electronic devices to perform at least a portion of the function or service instead of performing the function or service itself, or the electronic device 1701 may request one or more external electronic devices to perform at least a portion of the function or service in addition to performing the function or service. The one or more external electronic devices receiving the request may perform at least a portion of the requested function or service, or an additional function or additional service related to the request, and transmit the result of the execution to the electronic device 1701. The electronic device 1701 may provide the result with or without further processing the result as at least part of a reply to the request. To this end, for example, cloud computing, distributed computing, or client-server computing techniques may be used.

[0160] The subject matter and the embodiments of the operation described in this specification may be implemented in digital electronic circuits, or in computer software, firmware or hardware, including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, that is, one or more modules of computer program instructions, which are encoded on a computer storage medium for execution by a data processing device or the operation of a data processing device to control the data processing device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal (e.g., a machine-generated electrical, optical or electromagnetic signal), which is generated to encode information for transmission to a suitable receiver device for execution by a data processing device. The computer storage medium may be a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof or included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. In addition, although the computer storage medium is not a propagation signal, the computer storage medium may be the source or destination of the computer program instructions encoded in the artificially generated propagation signal. The computer storage medium may also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). In addition, the operations described in this specification may be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources.

[0161] Although this specification may include many specific implementation details, the implementation details should not be interpreted as a limitation on the scope of any claimed subject matter, but rather as a description of features specific to a particular embodiment. Certain features described in the context of a separate embodiment in this specification may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although the features may be described above as working in certain combinations and even initially claimed as such, one or more features from the claimed combination may be deleted from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variant of the sub-combination.

[0162] Similarly, although operations may be depicted in a particular order in the accompanying drawings, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order, or that all of the operations shown be performed, to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

[0163] Thus, specific embodiments of the subject matter have been described herein. Other embodiments are within the scope of the appended claims. In some cases, the actions set forth in the claims can be performed in a different order and still achieve the desired results. Additionally, the processes depicted in the accompanying drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing may be advantageous.

[0164] As will be appreciated by those skilled in the art, the innovative concepts described herein can be modified and varied in a wide range of applications. Therefore, the scope of the claimed subject matter should not be limited to any specific exemplary teachings discussed above, but rather is defined by the appended claims, wherein functional equivalents of the claims are included within the scope of the claimed subject matter.

Claims

1. A method comprising: A first transmission is sent by a user equipment (UE), wherein the first transmission includes information indicating a per-resource set capability for a first feature associated with a unified transmission configuration indicator (UTCI) scheme, the per-resource set capability indicating that the UE is capable of associating a channel state information reference signal (CSI-RS) resource with a transmission configuration indicator (TCI) state at a resource set level, The UE is configured to support joint transmission; and The first feature indicates that the UE can support the following items: Per aperiodic CSI-RS resource configuration for TCI selection; or Per-aperiodic CSI-RS resource set configuration for TCI selection.

2. The method according to claim 1, wherein: The first feature is associated with index number 40-1-3 of a Radio Access Network 1 (RAN1) UE feature list.

3. The method according to claim 1, wherein: The joint transmission comprises non-coherent joint transmission (NCJT); and The UE supports NCJT CSI under a second feature, wherein the second feature indicates that the UE is capable of supporting one or more features of channel state information multiple transmission and reception points (CSIMTRP).

4. The method according to claim 3, wherein: The second feature is associated with index number 23-7-1 of the Radio Access Network 1 (RAN1) UE feature list.

5. The method according to claim 1, wherein: The joint transmission comprises coherent joint transmission (CJT); and The UE supports CJT CSI under a second feature, wherein the second feature indicates that the UE is capable of supporting two TCI states for a CJT transmission scheme for a physical downlink shared channel (PDSCH).

6. The method according to claim 5, wherein: The second feature is associated with index number 40-1-4 of a Radio Access Network 1 (RAN1) UE feature list.

7. The method according to claim 1, further comprising: A second transmission including information for refusing to perform the first feature is sent by the UE, wherein: The joint transmission comprises non-coherent joint transmission (NCJT); and The UE supports NCJT CSI under a second feature, wherein the second feature indicates that the UE can support one or more features of CSI MTP.

8. The method according to claim 7, wherein: The first feature is associated with index number 40-1-3 of a Radio Access Network 1 (RAN1) UE feature list; and The second feature is associated with index number 23-7-1 of the RAN1 UE feature list.

9. The method according to claim 1, wherein: The UE does not support the joint operation of joint transmission and UTCI CSI-RS transmission.

10. A method comprising: sending, by a user equipment (UE), first capability information based on a rule indicating how the UE applies a first indicated transmission configuration indicator (TCI) state or a second indicated TCI state to an aperiodic channel state information reference signal (AP CSI-RS) resource; and A coherent joint transmission (CJT) is received by the UE based on the sending of the first capability information.

11. The method according to claim 10, wherein: The first indicated TCI state comprises a joint TCI state or a downlink (DL) TCI state; or The second indicated TCI state includes a joint TCI state or a DL TCI state.

12. The method according to claim 10, wherein: The rule indicates that support for the CJT is conditional on the UE supporting a resource-level radio resource control (RRC) configuration, The resource-level RRC configuration indicates that the UE is to apply the first indicated TCI state or the second indicated TCI state to the AP CSI-RS resources.

13. The method according to claim 10, wherein: Sending the first capability information includes sending information indicating support for a unified TCI (UTCI), the UTCI having capabilities of: per resource set; and Two or more UTCI status in the CJT program, in: The first indicated TCI state comprises a first indicated UTCI state, and the second indicated TCI state comprises a second indicated UTCI state; and The rules state that for CJT measurements or reports: The UE applies the first indicated UTCI state to CSI-RS resources in a first group; and The UE applies the UTCI state of the second indication to the CSI-RS resources in the second group; The CSI-RS resources in the first group correspond to a first TRP or a first TRP group associated with the first indicated UTCI state; and The CSI-RS resources in the second group correspond to a second TRP or a second TRP group associated with the second indicated UTCI state.

14. The method according to claim 10, wherein: sending the first capability information includes refusing to perform a first feature associated with a unified transmission configuration indicator (UTCI) scheme, The UE: Supporting the CJT scheme via the second feature and / or the third feature; and Supporting more than one UTCI state for CJT via the fourth feature, The first feature indicates that the UE can support the following items: Per aperiodic CSI-RS resource configuration for TCI selection; or Per-aperiodic CSI-RS resource set configuration for TCI selection, The second feature indicates that the UE can support one or more features for the first CJT codebook, The third feature indicates that the UE can support one or more features for the second CJT codebook, The fourth feature indicates that the UE is capable of supporting two TCI states for the CJT scheme for a physical downlink shared channel (PDSCH).

15. The method according to claim 14, wherein: The first feature is associated with index number 40-1-3 of a radio access network 1 (RAN1) UE feature list; The second feature is associated with index number 40-3-1-1 of the RAN1 UE feature list; The third feature is associated with index number 40-3-1-5 of the RAN1 UE feature list; and The fourth feature is associated with index number 40-1-4 of the RAN1 UE feature list.

16. A method comprising: transmitting, by a user equipment (UE), information indicating a per-resource capability for a first feature associated with a unified transmission configuration indicator (UTCI) scheme, wherein the per-resource capability indicates that the UE is capable of associating a channel state information reference signal (CSI-RS) resource with a transmission configuration indicator (TCI) state at a resource level; and Information indicating support for a second feature is sent by the UE, wherein the second feature indicates that the UE can support a joint operation of: Jointly transmit CSI; and Per-aperiodic UTCI CSI-RS resource configuration for TCI selection, The first feature indicates that the UE can support the following items: Per aperiodic CSI-RS resource configuration for TCI selection; or Per-aperiodic CSI-RS resource set configuration for TCI selection.

17. The method according to claim 16, wherein: The first feature is associated with index number 40-1-3 of a Radio Access Network 1 (RAN1) UE feature list.

18. The method according to claim 16, wherein: The joint transmission CSI includes non-coherent joint transmission (NCJT) CSI.

19. The method according to claim 16, wherein: The joint transmission CSI includes coherent joint transmission (CJT) CSI.

20. The method according to claim 16, wherein: The granularity of support for the second feature includes a per-UE granularity, wherein the per-UE granularity indicates that the UE can perform the second feature in any scenario.

Images