Sounding reference signal resource indicator design for codebook-based communications

Abstract

Methods, systems, and devices for wireless communication are described. A UE may receive one or more control messages indicating a number of sets of sounding reference signal (SRS) resources configured for codebook use and at least one maximum rank value associated with uplink shared channel transmissions of the UE. The UE may receive downlink control information (DCI) having an SRS resource indicator (SRI) field and a transmit precoding matrix indicator (TPMI) field. The UE may then interpret the SRI and TPMI fields according to a mapping based on the maximum rank value and a maximum number of ports that the UE can support. The UE may then transmit the uplink shared channel message according to the mapping.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 397,271, filed on August 11, 2022 by KHOSHNEVISAN et al., entitled “SOUNDING REFERENCE SIGNAL RESOURCE INDICATOR DESIGNS FOR CODEBOOK-BASED COMMUNICATIONS,” and U.S. Patent Application No. 18 / 446,347, filed on August 8, 2023 by KHOSHNEVISAN et al., entitled “SOUNDING REFERENCE SIGNAL RESOURCE INDICATOR DESIGNS FOR CODEBOOK-BASED COMMUNICATIONS,” each of which is assigned to the assignee of the present application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including a sounding reference signal (SRS) resource indicator (SRI) design for codebook (CB) based communications. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses that support the design of sounding reference signal (SRS) resource indicators (SRI) for codebook (CB) based communications. For example, the described technology provides a signaling-based mechanism according to which a user equipment (UE) can dynamically switch between communicating with a single transmit and receive point (TRP) in a single TRP (sTRP) operating mode and communicating with multiple TRPs in a multi-TRP (mTRP) operating mode, while supporting various configurations related to how many layers (e.g., rank) and how many ports the UE can use for uplink transmissions (such as physical uplink shared channel (PUSCH) transmissions). In some aspects, the uplink transmission may include two or more PUSCH transmissions that at least partially overlap in the time domain. In some cases, the UE may interpret one or more DCI fields (e.g., a transmit precoding matrix indicator (TPMI) field, an SRI field) scheduling a PUSCH transmission in an sTRP or mTRP mode of operation based on a maximum number of layers that the UE can support in the mTRP mode of operation when two PUSCH transmissions that at least partially overlap in the time domain are transmitted via the same component carrier. Based on interpreting the one or more DCI fields, the UE may transmit the one or more PUSCH transmissions according to the SRS resource, port, and layer indicated by the DCI.

[0006] A method for wireless communication by a UE is described. The method may include receiving one or more control messages indicating: a set number of a plurality of SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the plurality of SRS resource sets is configured for CB use; and at least one maximum rank value associated with uplink shared channel transmissions from the UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. The method may also include: receiving a message including a DCI for scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; interpreting the one or more SRI fields and the one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by: the number of at least one maximum rank values, and the maximum number of ports that the UE can support; and sending the uplink shared channel message based on the mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the multiple SRS resource sets.

[0007] A UE for wireless communication is described. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to receive one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. In some examples, the one or more processors can be configured, individually or collectively, to: receive a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; interpret the one or more SRI fields and the one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by: the number of at least one maximum rank values, and the maximum number of ports that the UE can support; and send the uplink shared channel message based on the mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource from the multiple SRS resource sets.

[0008] Another UE for wireless communication is described. The UE may include means for receiving one or more control messages indicating: a set number of a plurality of SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the plurality of SRS resource sets is configured for CB use; and means for at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. In some examples, the UE may include: a component for receiving a message including a DCI for scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; a component for interpreting the one or more SRI fields and the one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by: the number of at least one maximum rank values, and the maximum number of ports that the UE can support; and a component for sending the uplink shared channel message based on the mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource from the multiple SRS resource sets.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to receive one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with uplink shared channel transmissions from the UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. In some examples, the instructions may be executable by the one or more processors to: receive a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; interpret the one or more SRI fields and the one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the set of multiple SRS resource sets, the mapping being indicated by: the number of at least one maximum rank values, and the maximum number of ports that the UE can support; and send the uplink shared channel message based on the mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource from the set of multiple SRS resource sets.

[0010] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, instructions, or one or more processors configured to: send information associated with the maximum number of ports that the UE may be able to support via a capability report when the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message may be associated with a single uplink shared channel, or both, wherein receiving the message including the DCI may be based on sending the information via the capability report.

[0011] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, instructions, or one or more processors configured for the following actions: receiving an indication of a configuration associated with the at least one maximum rank value, wherein the configuration may be a first configuration or a second configuration, and wherein: the first configuration indicates that when the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message may be equal to the larger of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource, and the second configuration indicates that when the uplink shared channel message is associated with the single uplink shared channel, the maximum number of ports associated with the uplink shared channel message may be equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

[0012] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the configuration may be indicated per DCI format, per bandwidth part, or per component carrier.

[0013] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the one or more control messages indicating the at least one maximum rank value may include operations, features, components, instructions, or one or more processors configured for the following actions: receiving an indication of a corresponding maximum rank value for each corresponding SRS resource set in the set of multiple SRS resource sets configured at the UE.

[0014] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, interpretation of the one or more TPMI fields may be independent of whether the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain, interpretation of the one or more SRI fields may be independent of whether the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain, at least one maximum rank value associated with uplink shared channel transmission from the UE may be applicable when the uplink shared channel message may be associated with a single uplink shared channel or more than one uplink shared channels that at least partially overlap in the time domain, and a threshold number of ports supported by the UE may be applicable when the uplink shared channel message may be associated with the single uplink shared channel or more than one uplink shared channels that at least partially overlap in the time domain.

[0015] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, when the uplink shared channel message may be associated with a single uplink shared channel or with more than one uplink shared channels that at least partially overlap in the time domain, the corresponding maximum rank value of each corresponding SRS resource set in the set of multiple SRS resource sets may be applicable.

[0016] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, each of the at least one maximum rank value can be indicated by a control resource set index value, by an SRS resource set, by a DCI format, by a bandwidth part, or by a component carrier.

[0017] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the one or more control messages indicating the at least one maximum rank value may include operations, features, components, instructions, or one or more processors configured for the following actions: when the uplink shared channel message may be associated with a single uplink shared channel, receiving an indication of a baseline maximum rank value that may be applicable to any one or more SRS resource sets in the set of the multiple SRS resource sets; and when the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain, receiving an indication of a corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set in the set of the multiple SRS resource sets, wherein the corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set may be applicable to the corresponding SRS resource set, and wherein the baseline maximum rank value may be less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each corresponding SRS resource set in the set of the multiple SRS resource sets.

[0018] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, in a case where the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value, and in a case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set of the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

[0019] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, interpreting the one or more TPMI fields may be independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more SRI fields may be independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, in the case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRI fields each indicate a number of ports that may be less than or equal to the maximum number of ports that the UE may be able to support, and in the case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRI fields each indicate a number of ports that may be less than or equal to a plurality of maximum number of ports of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum number of ports that the UE may be able to support may be equal to the sum of the plurality of maximum number of ports of each corresponding SRS resource set.

[0020] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the DCI includes a field including information indicating whether the uplink shared channel message can be associated with more than one uplink shared channels that at least partially overlap in the time domain, and the mapping can also be indicated by whether the uplink shared channel message can be associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0021] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields includes interpreting the one or more TPMI fields based on the mapping between the content of the one or more TPMI fields and each of the number of ports associated with an SRS resource of the single uplink shared channel, and when the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes interpreting the one or more TPMI fields based on a first mapping between the content of the first TPMI field and a first subset of the first number of ports associated with a first SRS resource from a first SRS resource set, and a second mapping between the content of the second TPMI field and a second subset of the second number of ports associated with a second SRS resource from a second SRS resource set.

[0022] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the first subset includes a first half of the number of first ports associated with the first SRS resource, and the second subset includes a first half of the number of second ports associated with the second SRS resource.

[0023] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the one or more control messages may include operations, features, components, instructions, or one or more processors configured for the following actions: receiving an indication of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

[0024] Some examples of the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, instructions, or one or more processors configured to: send information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, when the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain, the first subset and the second subset corresponding to the maximum number of ports that the UE may be able to support for the first SRS resource and the second SRS resource.

[0025] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, interpreting the one or more SRI fields may be independent of whether the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0026] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, a size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE may be able to support when the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0027] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, receiving the message including the DCI includes receiving the message within a first control resource set associated with a first control resource set index value, receiving the message within a second control resource set associated with a second control resource set index value, or a combination thereof, one or more SRS resource sets may be indicated from the multiple SRS resource sets by a combination of the fields in the DCI, the field indicating whether the uplink shared channel message may be associated with the more than one uplink shared channels, and whether the message including the DCI may be received within the first control resource set associated with the first control resource set index value or in the second control resource set associated with the second control resource set index value; and interpreting the one or more SRI fields includes: selecting, according to the one or more SRI fields, the at least one SRS resource for sending the uplink shared channel message from the one or more SRS resource sets indicated by the set of the multiple SRS resource sets.

[0028] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, when the field in the DCI indicates that the uplink shared channel message may be associated with a single uplink shared channel and the message including the DCI may be received within the first control resource set associated with the first control resource set index value, the first SRS resource set may be indicated from the multiple SRS resource sets; when the field in the DCI indicates that the uplink shared channel message may be associated with the single uplink shared channel and the message including the DCI may be received within the second control resource set associated with the second control resource set index value, the second SRS resource set may be indicated from the multiple SRS resource sets. S resource set indicated in the DCI; when the field in the DCI indicates that the uplink shared channel message can be associated with the more than one uplink shared channels and the message including the DCI can be received within the first control resource set associated with the first control resource set index value, the third SRS resource set can be indicated from the multiple SRS resource sets; and when the field in the DCI indicates that the uplink shared channel message can be associated with the more than one uplink shared channels and the message including the DCI can be received within the second control resource set associated with the first control resource set index value, the fourth SRS resource set can be indicated from the multiple SRS resource sets.

[0029] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the first SRS resource set and the third SRS resource set may be associated with a first common power control parameter set, the second SRS resource set and the fourth SRS resource set may be associated with a second common power control parameter set, the number of first SRS resources in the first SRS resource set and the third SRS resource set may be the same, and the number of second SRS resources in the second SRS resource set and the fourth SRS resource set may be the same.

[0030] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, a first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with the same beam, the same transmit configuration indicator (TCI) state, the same spatial relationship information, or a combination thereof; a third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; the first SRS resource having a first position in the third SRS resource set is associated with a smaller number of ports than the second SRS resource having the first position in the first SRS resource set; and the third SRS resource having a second position within the fourth SRS resource set is associated with a smaller number of ports than the fourth SRS resource having the second position within the second SRS resource set.

[0031] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, in a case where the message including the DCI is received within the first set of control resources, the field including information indicating whether the uplink shared channel message can be associated with more than one uplink shared channels that at least partially overlap in the time domain includes one bit, which indicates; and in a case where the message including the DCI is received within the second set of control resources, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes one bit, which indicates.

[0032] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, interpretation of the one or more SRI fields may be based at least in part on a combination of the fields in the DCI, which indicate whether the uplink shared channel message can be associated with the more than one uplink shared channels, and whether the message including the DCI can be received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and interpretation of the one or more TPMI fields may be based at least in part on a port number associated with at least one SRS resource selected for sending the uplink shared channel message.

[0033] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain may include a bit indicating: the uplink shared channel message is associated with a single uplink shared channel; or the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0034] A method for wireless communication by a network entity is described. The method may include sending one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from a UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. In some examples, the method may include: sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; and receiving the uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the set of the multiple SRS resource sets, the mapping being indicated by the number of the at least one maximum rank value and the maximum number of ports that the UE can support.

[0035] A network entity for wireless communication is described. The network entity may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to send one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from a UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. In some examples, the one or more processors may be configured individually or collectively to send a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; and receive the uplink shared channel message according to a mapping between the content of the one or more TPMI fields and a number of ports associated with at least one SRS resource from the set of the multiple SRS resource sets, the mapping being indicated by the following items: the number of the at least one maximum rank value and the maximum number of ports that the UE can support.

[0036] Another network entity for wireless communication is described. The network entity may include a component for sending one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of the multiple SRS resource sets is configured for CB use; and a component for at least one maximum rank value associated with an uplink shared channel transmission from a UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. In some examples, the network entity may include: a component for sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; and a component for receiving the uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the set of the multiple SRS resource sets, the mapping being indicated by the number of the at least one maximum rank value and the maximum number of ports that the UE can support.

[0037] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions that can be executed by one or more processors to send one or more control messages, the one or more control messages indicating: the number of sets of multiple SRS resource sets, the number of one or more SRI fields included in the one or more control messages, and the number of one or more TPMI fields included in the one or more control messages, wherein the set of the multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from a UE, the at least one maximum rank value being based on the number of threshold rank values ​​supported by the UE. In some examples, the instructions may be executable by the one or more processors to send a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; and receive the uplink shared channel message according to a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the set of the multiple SRS resource sets, the mapping being indicated by the following items: the number of the at least one maximum rank value and the maximum number of ports that the UE can support.

[0038] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, instructions, or one or more processors configured to: when the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message may be associated with a single uplink shared channel, or both, receive information associated with the maximum number of ports that the UE may be able to support via a capability report, wherein sending the message including the DCI may be based on sending the information via the capability report.

[0039] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, instructions, or one or more processors configured for the following actions: sending an indication of a configuration associated with the at least one maximum rank value, wherein the configuration may be a first configuration or a second configuration, and wherein: the first configuration indicates that: in the case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message may be equal to the larger of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource, and the second configuration indicates that: in the case where the uplink shared channel message is associated with the single uplink shared channel, the maximum number of ports associated with the uplink shared channel message may be equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

[0040] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the configuration may be indicated per DCI format, per bandwidth part, or per component carrier.

[0041] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the one or more control messages indicating the at least one maximum rank value may include operations, features, components, instructions, or one or more processors configured for the following actions: sending an indication of a corresponding maximum rank value for each corresponding SRS resource set in the set of multiple SRS resource sets configured at the UE.

[0042] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, interpreting the one or more TPMI fields may be independent of whether the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more SRI fields may be independent of whether the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message may be associated with a single uplink shared channel or more than one uplink shared channels that at least partially overlap in the time domain, at least one maximum rank value associated with an uplink shared channel transmission from the UE may be applicable, and when the uplink shared channel message may be associated with the single uplink shared channel or more than one uplink shared channels that at least partially overlap in the time domain, a threshold number of ports supported by the UE may be applicable.

[0043] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, when the uplink shared channel message may be associated with a single uplink shared channel or with more than one uplink shared channels that at least partially overlap in the time domain, the corresponding maximum rank value of each corresponding SRS resource set in the set of multiple SRS resource sets may be applicable.

[0044] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, each of the at least one maximum rank value can be indicated by a control resource set index value, by an SRS resource set, by a DCI format, by a bandwidth part, or by a component carrier.

[0045] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the one or more control messages indicating the at least one maximum rank value may include operations, features, components, instructions, or one or more processors configured for the following actions: when the uplink shared channel message may be associated with a single uplink shared channel, sending an indication of a baseline maximum rank value that may be applicable to any one or more SRS resource sets in the set of the multiple SRS resource sets; and when the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain, sending an indication of a corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set in the set of the multiple SRS resource sets, wherein the corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set may be applicable to the corresponding SRS resource set, and wherein the baseline maximum rank value may be less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each corresponding SRS resource set in the set of the multiple SRS resource sets.

[0046] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, in a case where the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value, and in a case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set of the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

[0047] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, interpreting the one or more TPMI fields may be independent of whether the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more SRI fields may be independent of whether the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain, in the case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRI fields each indicate a number of ports that may be less than or equal to the maximum number of ports that the UE may be able to support, and in the case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRI fields each indicate a number of ports that may be less than or equal to a plurality of maximum number of ports of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum number of ports that the UE may be able to support may be equal to the sum of the plurality of maximum number of ports of each corresponding SRS resource set.

[0048] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the DCI includes a field that includes information indicating whether the uplink shared channel message can be associated with more than one uplink shared channels that at least partially overlap in the time domain, and the mapping can also be indicated by whether the uplink shared channel message can be associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0049] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, in a case where the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields includes interpreting the one or more TPMI fields based on the mapping between the content of the one or more TPMI fields and each of the number of ports associated with an SRS resource of the single uplink shared channel, and in a case where the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes interpreting the one or more TPMI fields based on a first mapping between the content of the first TPMI field and a first subset of the first number of ports associated with a first SRS resource from a first SRS resource set, and a second mapping between the content of the second TPMI field and a second subset of the second number of ports associated with a second SRS resource from a second SRS resource set.

[0050] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the first subset includes a first half of the number of first ports associated with the first SRS resource, and the second subset includes a first half of the number of second ports associated with the second SRS resource.

[0051] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the one or more control messages may include operations, features, components, instructions, or one or more processors configured to: send an indication of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

[0052] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, instructions, or one or more processors configured to: receive information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, when the uplink shared channel message may be associated with the more than one uplink shared channels that at least partially overlap in the time domain, the first subset and the second subset corresponding to the maximum number of ports that the UE may be able to support for the first SRS resource and the second SRS resource.

[0053] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the interpretation of the one or more SRI fields may be independent of whether the uplink shared channel message can be associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0054] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, a size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE may be able to support when the uplink shared channel message may be associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0055] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending the message including the DCI includes sending the message within a first control resource set associated with a first control resource set index value, sending the message within a second control resource set associated with a second control resource set index value, or a combination thereof, one or more SRS resource sets may be indicated from the multiple SRS resource sets by a combination of the fields in the DCI, the field indicating whether the uplink shared channel message may be associated with the more than one uplink shared channels, and whether the message including the DCI may be sent within the first control resource set associated with the first control resource set index value or in the second control resource set associated with the second control resource set index value; and interpreting the one or more SRI fields includes: selecting, according to the one or more SRI fields, the at least one SRS resource for receiving the uplink shared channel message from the one or more SRS resource sets indicated by the set of the multiple SRS resource sets.

[0056] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, when the field in the DCI indicates that the uplink shared channel message can be associated with a single uplink shared channel and the message including the DCI can be sent within the first control resource set associated with the first control resource set index value, the first SRS resource set can be indicated from the multiple SRS resource sets; when the field in the DCI indicates that the uplink shared channel message can be associated with the single uplink shared channel and the message including the DCI can be sent within the second control resource set associated with the second control resource set index value, the second SRS resource set is from the multiple SRS resource sets. RS resource set; when the field in the DCI indicates that the uplink shared channel message can be associated with the more than one uplink shared channels and the message including the DCI can be sent within the first control resource set associated with the first control resource set index value, the third SRS resource set can be indicated from the multiple SRS resource sets; and when the field in the DCI indicates that the uplink shared channel message can be associated with the more than one uplink shared channels and the message including the DCI can be sent within the second control resource set associated with the first control resource set index value, the fourth SRS resource set can be indicated from the multiple SRS resource sets.

[0057] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the first SRS resource set and the third SRS resource set may be associated with a first common power control parameter set, the second SRS resource set and the fourth SRS resource set may be associated with a second common power control parameter set, the number of first SRS resources in the first SRS resource set and the third SRS resource set may be the same, and the number of second SRS resources in the second SRS resource set and the fourth SRS resource set may be the same.

[0058] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, a first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; a third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; the first SRS resource having a first position in the third SRS resource set is associated with a smaller number of ports than the second SRS resource having the first position in the first SRS resource set; and the third SRS resource having a second position within the fourth SRS resource set is associated with a smaller number of ports than the fourth SRS resource having the second position within the second SRS resource set.

[0059] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, in a case where the message including the DCI can be sent within the first set of control resources, the field including information indicating whether the uplink shared channel message can be associated with more than one uplink shared channels that at least partially overlap in the time domain includes one bit, which indicates; and in a case where the message including the DCI can be sent within the second set of control resources, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes one bit, which indicates.

[0060] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the interpretation of the one or more SRI fields may be based at least in part on a combination of the fields in the DCI indicating whether the uplink shared channel message can be associated with the more than one uplink shared channels, and whether the message including the DCI can be sent within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and the interpretation of the one or more TPMI fields may be based at least in part on the number of ports associated with the selected at least one SRS resource for receiving the uplink shared channel message.

[0061] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain may include a bit indicating: the uplink shared channel message is associated with a single uplink shared channel; or the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figures 1 to 3 An example of a wireless communication system supporting a sounding reference signal (SRS) resource indicator (SRI) design for codebook (CB) based communication according to one or more aspects of the present disclosure is illustrated.

[0063] Figures 4 to 6 An example of a resource selection process supporting SRI design for CB-based communications in accordance with one or more aspects of the present disclosure is illustrated.

[0064] Figure 7 An example of a process flow in a system supporting SRI design for CB-based communications according to one or more aspects of the present disclosure is illustrated.

[0065] Figure 8 and Fig. 9 A block diagram of a device supporting SRI design for CB-based communications according to one or more aspects of the present disclosure is shown.

[0066] Fig.10 A block diagram of a communication manager supporting an SRI design for CB-based communications in accordance with one or more aspects of the present disclosure is shown.

[0067] Fig.11 A diagram of a system including a device supporting a SRI design for CB-based communications in accordance with one or more aspects of the present disclosure is shown.

[0068] Fig.12 and Fig.13 A block diagram of a device supporting SRI design for CB-based communications according to one or more aspects of the present disclosure is shown.

[0069] Fig.14 A block diagram of a communication manager supporting an SRI design for CB-based communications in accordance with one or more aspects of the present disclosure is shown.

[0070] Fig.15 A diagram of a system including a device supporting a SRI design for CB-based communications in accordance with one or more aspects of the present disclosure is shown.

[0071] Fig.16 and Fig.17 A flow chart illustrating a method of supporting SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0072] In some wireless communication systems, a network entity may dynamically schedule uplink shared channel messages, such as a physical uplink shared channel (PUSCH), from a user equipment (UE) via a message including downlink control information (DCI). In some cases, the message including the DCI may indicate information associated with a PUSCH message to be sent from the UE. For example, the DCI may include an indication of whether the transmission is associated with a codebook (CB)-based PUSCH transmission or an indication of a non-CB (NCB)-based PUSCH transmission. For example, for CB-based PUSCH transmission, the DCI message may include a transmit precoding matrix indicator (TPMI) field indicating information associated with the number of PUSCH ports selected by the UE from a set of ports associated with a sounding reference signal (SRS) resource, which in some cases may be indicated via an SRS resource indicator (SRI) field in the DCI. For CB-based transmission, the UE may use the TPMI field to identify the number of layers and predecoders used to send the PUSCH message. In some examples, different DCI messages (e.g., sent by different transmit reception points (TRPs)) can be used to schedule corresponding PUSCH messages to two or more TRPs, which can be referred to as multiple DCI (mDCI) mTRP operation.

[0073] In addition, the UE may support one of a variety of different configurations related to how many layers the UE may use for a PUSCH message at a given time. That is, the UE may be able to send up to (X1, X2) layers in a simultaneous transmission with a multiple panel (STxMP) deployment. Here, when the first PUSCH and the second PUSCH are transmitted via the same component carrier and at least partially overlap in the time domain, the UE may be able to use up to X1 layers to send the first PUSCH via the first SRS resource and use up to X2 layers to send the second PUSCH via the second SRS resource. Additionally, in an STxMP deployment, the UE may be able to support up to (P1, P2) ports for PUSCH transmission. That is, when the first PUSCH and the second PUSCH are transmitted via the same component carrier and at least partially overlap in the time domain, the UE may be able to use up to P1 ports to send the first PUSCH transmission via the first SRS resource, and use up to P2 ports to send the second PUSCH transmission via the second SRS resource. According to the first configuration, when operating in a single transmit receive point (TRP) deployment, the UE can use up to max(X1,X2) layers and up to max(P1,P2) ports to send PUSCH. According to the second configuration, when operating in a single TRP (sTRP) deployment, the UE can use up to X1+X2 layers and up to P1+P2 ports to send PUSCH.

[0074] Although both configurations may be valid UE specific implementations, some systems may not be able to dynamically support both sTRP and STxMP deployments. For example, some systems may not define a mapping that enables the UE to obtain information consistent with one or both of the first configuration and the second configuration for both sTRP and STxMP PUSCH transmissions based on interpreting fields within the DCI. Therefore, in the case of both the first configuration and the second configuration, the network entity may not be able to dynamically schedule UEs with sTRP and STxMP PUSCH messages.

[0075] In some specific implementations, the UE and the network entity may support one or more configuration or signaling-based mechanisms, according to which the network entity may configure one or more maxRank values ​​and one or more threshold (e.g., maximum) numbers of port values ​​according to a first configuration or a second configuration, and according to which the UE may interpret one or more DCI fields to identify, ascertain, or otherwise determine information associated with an sTRP or STxMP PUSCH message. For example, in a scenario where the UE is configured according to the first configuration, the network entity may configure a maxRank value and a threshold (e.g., maximum) number of ports value for each SRS resource set (e.g., X1 and P1 for the first SRS resource set configuration, and X2 and P2 for the second SRS resource set configuration), which is applicable regardless of whether sTRP operation or STxMP operation is indicated.

[0076] Additionally or alternatively, in a scenario where the UE is configured according to the second configuration, the network entity may configure a baseline maxRank value (e.g., X) and a baseline maximum number of ports value (e.g., P) applicable when indicating sTRP operation and one or more additional maxRank values ​​and maximum number of ports values ​​for each SRS resource set applicable when indicating STxMP operation (e.g., X1 and P1 for the first SRS resource set and X2 and P2 for the second SRS resource set). Additionally or alternatively, in a scenario where the UE is configured according to the second configuration, the network entity may indicate via a field in the DCI whether a scheduled PUSCH overlaps in time with another scheduled PUSCH. In this case, the UE may interpret one or more fields of the DCI differently based on whether the scheduled PUSCH overlaps in time with another scheduled PUSCH. Therefore, the network entity may schedule PUSCH transmissions for sTRP operation or STxMP operation that meet a threshold (e.g., maximum) number of layers or ports supported by the UE for the corresponding operation.

[0077] Various aspects of the disclosure are first described in the context of a wireless communication system. Various aspects of the disclosure are then described in the context of PUSCH configurations and process flows. In addition, various aspects of the disclosure are illustrated by apparatus diagrams, system diagrams, and flow charts related to SRI designs for CB-based communications, and are described herein with reference to these.

[0078] Figure 1An example of a wireless communication system 100 supporting an SRI design for CB-based communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0079] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0080] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0081] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0082] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0083] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0084] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a TRP. One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0085] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0086] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0087] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the SRI design for CB-based communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0088] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0089] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0090] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0091] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0092] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0093] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0094] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0095] Carrier multiplexing physical channels may be used for communication according to various techniques. Physical control channels and physical data channels may be multiplexed, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0096] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0097] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0098] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0099] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0100] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0101] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the network entity may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0102] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0103] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0104] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0105] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0106] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0107] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0108] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0109] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0110] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or CB-based feedback (e.g., multi-panel CB, linear combination CB, port selection CB). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0111] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0112] The wireless communication system 100 may support two types of PUSCH transmissions: CB-based PUSCH transmissions and non-CB (NCB)-based PUSCH transmissions. For CB-based PUSCH transmissions, the UE 115 may be configured with one SRS resource set in which "Use" is set or configured as "Codebook". The UE 115 may be configured with a threshold (e.g., maximum) or upper limit of four SRS resources of an SRS resource set with "Use" set to "Codebook", and each SRS resource may be configured with the number or quantity of ports, such as configuring the RRC (e.g., via the nrofSRS-Ports parameter). In addition, the SRI field in the uplink DCI (e.g., the DCI that schedules the PUSCH) may indicate one SRS resource. The number of ports configured for the indicated SRS resource may inform, indicate, imply, or otherwise assist the UE 115 in determining or selecting the number of antenna ports for the scheduled PUSCH. The UE 115 may send the scheduled PUSCH using the same spatial domain filter (e.g., the same uplink beam or directional configuration) as the indicated SRS resources. The UE 115 may determine or select the number of layers (e.g., rank) and TPMI (e.g., precoder) for the scheduled PUSCH from or using a separate DCI field (such as the "Precoding Information and Number of Layers" field).

[0113] For non-CB-based PUSCH transmissions, the UE 115 may be configured with one SRS resource set with "Use" set or configured as "Non-Codebook". The UE 115 may be configured with a maximum or upper limit of four SRS resources within the SRS resource set with "Use" set to "Non-Codebook", and each SRS resource may have a port or be otherwise associated with a port. The SRI field in the uplink DCI (e.g., the DCI that schedules the PUSCH) may indicate one or more SRS resources. The number or amount of SRS resources indicated may inform, indicate, imply, or otherwise assist the UE 115 in determining or selecting the rank (e.g., the number or amount of layers) for the scheduled PUSCH, and the UE 115 may use the same precoder and the same spatial domain filter (e.g., precoder) as the indicated SRS resources to transmit the scheduled PUSCH.

[0114] For both CB-based PUSCH transmissions and non-CB-based PUSCH transmissions, the size of the SRI field may be a function of the number of SRS resources within the applicable SRS resource set. For example, in the case where the higher layer parameter txConfig is set equal to codebook, the size of the SRI field for CB-based PUSCH transmissions may be defined according to Table 1, where N SRSThe size of the SRI field may be the number or quantity of configured SRS resources in the SRS resource set configured by the higher layer parameter srs-ResoureSetToAddModList and associated with the higher layer parameter usage with the value 'codeBook'. Bit.

[0115] Table 1: SRI indication for CB-based PUSCH transmission

[0116] Maps to indexed bit fields <![CDATA[SRI,N SRS =4]]> 0 0 1 1 2 2 3 3

[0117] In some wireless communication systems 100, the network entity 105 may dynamically schedule uplink shared channel messages, such as PUSCH messages from the UE 115 via a message including a DCI. In some cases, the message including the DCI may indicate information associated with the PUSCH message to be sent from the UE 115. For example, the DCI may include an indication of whether the transmission is associated with a CB-based PUSCH transmission or an NCB-based PUSCH transmission. For example, for a CB-based PUSCH transmission, the DCI message may include a TPMI field indicating information associated with the number of PUSCH ports selected by the UE 115 from a set of ports associated with an SRS resource, which in some cases may be indicated via an SRI field in the DCI. For a CB-based transmission, the UE 115 may use the TPMI field to identify the number of layers and pre-decoders used to send the PUSCH message.

[0118] In some cases, for each pair of numbers including a certain number of layers and a certain number of PUSCH ports (e.g., as indicated for a PUSCH message), a set of precoding matrices may be defined (e.g., in a specification) using a corresponding set of TPMI indices. That is, UE 115 may receive a message including a DCI that includes a DCI field "precoding information and number of layers" indicating a TPMI index. Based on the TPMI index within the "precoding information and number of layers" field of the DCI, UE 115 may identify a precoding matrix associated with the TPMI index (e.g., based on the defined set of precoding matrices). For example, Table 2 illustrates an example mapping between a TPMI index and a precoding matrix for a PUSCH message associated with one layer and four ports (e.g., for a value pair (1,4)).

[0119] Table 2: Precoding for single layer transmission using four antenna ports with transform precoding disabled Matrix W

[0120]

[0121] In another example, Table 3 illustrates an example mapping between TPMI indices and precoding matrices for a PUSCH message associated with two layers and two ports (eg, for a value pair (2, 2)).

[0122] Table 3: Precoding for dual layer transmission using two antenna ports with transform precoding disabled Matrix W

[0123]

[0124] In another example, Table 4 illustrates an example mapping between TPMI indices and precoding matrices for a PUSCH message associated with three layers and four ports (eg, for a value pair (3, 4)).

[0125] Table 4: Precoding for three-layer transmission using four antenna ports with transform precoding disabled Matrix W

[0126]

[0127] For CB-based PUSCH transmission, the TPMI index may be indicated in the DCI field "precoding information and number of layers". Tables 6, 7, 8, and 9 provide additional information for the case where FullpowerMode1 is not configured. As illustrated in Tables 5, 6, 7, and 8, different tables may correspond to different numbers of antenna ports or different maximum ranks (e.g., different maxRank values).

[0128] Table 5: Pre-coding information and number of layers

[0129]

[0130]

[0131] Table 6: Pre-coding information and number of layers

[0132]

[0133]

[0134] Table 7: Pre-coding information and number of layers

[0135]

[0136] Table 8: Pre-coding information and number of layers

[0137]

[0138] In some aspects, the UE 115 and the network entity 105 may support a threshold (e.g., maximum) number of TPMI field bit widths and ports. For example, for a higher layer parameter txConfig=codebook, in the case where ul-FulPowerTransmission is configured as fullpowerMode2, maxRank may be configured to be greater than 2, and at least one SRS resource with 4 antenna ports may be configured in a set of SRS resources with usage set to 'codebook', and SRS resources with 2 antenna ports may be indicated via SRI in the same set of SRS resources, then Table 7 may be used. For a higher layer parameter txConfig=codebook, in the case where different SRS resources with different numbers of antenna ports are configured, the bit width may be determined based on the maximum number of ports in the SRS resources among the SRS resources configured in the set of SRS resources with usage set to 'codebook'. In the case where the number of ports for the configured SRS resources in the set is less than the maximum number of ports in the SRS resources among the configured SRS resources, the number of most significant bits with a value set to '0' may be inserted into the field. Therefore, for a set of SRS resources, the UE 115 and the network entity 105 may assume that a threshold (eg, maximum) number of ports is p. max , and for the indicated SRS resource, the number of ports is p, and the TPMI field size can be based on p max The actual table to be used may be determined according to p, and the number of PUSCH ports may be equal to the number of ports p of the indicated SRS resources.

[0139] In some cases, UE 115 may support one of various different configurations related to how many layers the UE can use for PUSCH messages. That is, UE 115 may be able to send up to (X1, X2) layers in an STxMP deployment. Here, when the first PUSCH and the second PUSCH are transmitted via the same component carrier and at least partially overlap in the time domain, UE 115 may be able to use up to X1 layers to send the first PUSCH via the first SRS resource and use up to X2 layers to send the second PUSCH via the second SRS resource. Additionally, in an STxMP deployment, UE 115 may be able to support up to (P1, P2) ports for PUSCH transmission. That is, when the first PUSCH and the second PUSCH are transmitted via the same component carrier and at least partially overlap in the time domain, UE 115 may be able to use up to P1 ports to send the first PUSCH transmission via the first SRS resource, and use up to P2 ports to send the second PUSCH transmission via the second SRS resource. According to the first configuration, when operating in a single transmit receive point (TRP) deployment, the UE 115 can use up to max(X1,X2) layers and up to max(P1,P2) ports to send PUSCH. According to the second configuration, when operating in an sTRP deployment, the UE 115 can use up to X1+X2 layers and up to P1+P2 ports to send PUSCH.

[0140] Although both configurations may be valid UE 115 specific implementations, some wireless communication systems 100 may not be able to dynamically support both sTRP and STxMP deployments. For example, some wireless communication systems 100 may not define a mapping that enables UE 115 to obtain information consistent with one or both of the first configuration and the second configuration for both sTRP and STxMP PUSCH transmissions based on interpreting fields within the DCI. Therefore, in the case of both the first configuration and the second configuration, the network entity 105 may not be able to dynamically schedule UE 115 with sTRP and STxMP PUSCH messages.

[0141] In some embodiments, the UE 115 and the network entity 105 may support one or more configuration or signaling-based mechanisms, according to which the network entity may configure one or more maxRank values ​​and one or more maximum number of port values ​​according to a first configuration or a second configuration, and according to which the UE 115 may interpret one or more DCI fields to identify, ascertain, or otherwise determine information associated with an sTRP or STxMP PUSCH message. For example, in a scenario where the UE 115 is configured according to the first configuration, the network entity 105 may configure a maxRank value and a maximum number of ports value for each SRS resource set (e.g., X1 and P1 for the first SRS resource set configuration, and X2 and P2 for the second SRS resource set configuration), which is applicable regardless of whether sTRP operation or STxMP operation is indicated.

[0142] Additionally or alternatively, in a scenario where the UE 115 is configured according to the second configuration, the network entity 105 may configure a baseline maxRank value (e.g., X) and a baseline maximum number of ports value (e.g., P) applicable when indicating sTRP operation and one or more additional maxRank values ​​and maximum number of ports values ​​for each SRS resource set applicable when indicating STxMP operation (e.g., X1 and P1 for the first SRS resource set and X2 and P2 for the second SRS resource set). Additionally or alternatively, in a scenario where the UE 115 is configured according to the second configuration, the network entity may indicate via a field in the DCI whether a scheduled PUSCH overlaps in time with another scheduled PUSCH. In this case, the UE 115 may interpret one or more fields of the DCI differently based on whether the scheduled PUSCH overlaps in time with another scheduled PUSCH. Therefore, the network entity 105 can schedule PUSCH transmissions for sTRP operations or STxMP operations that conform to the maximum number of layers or ports supported by the UE 115 for the corresponding operation.

[0143] Figure 2 An example of a wireless communication system 200 supporting an SRI design for CB-based communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement or may be implemented to achieve or facilitate aspects of the wireless communication system 100. For example, the wireless communication system 200 illustrates communication between a UE 215 and a network entity 205 via a TRP 210-a or a TRP 210-b or both. The UE 215, the network entity 205, the TRP 210-a, and the TRP 210-b may be via Figure 1Examples of corresponding devices described herein are illustrated and referenced. In some implementations, the UE 215 and the network entity 205 can support dynamic switching between sTRP operation and mTRP operation at the UE 215 based on a specific configuration of one or more maxRank values ​​and interpretation rules that the UE 115 can use when receiving, decoding, or interpreting scheduling DCI from the network entity 205.

[0144] UE 215 and network entity 205 may communicate via uplink and downlink communication links. UE 215 and network entity 205 may use the communication links to send signaling to one or both of TRP 210-a and TRP 210-b, and may receive signaling from one or both of TRP 210-a and TRP 210-b.

[0145] The network entity 205 may send one or more control messages 220 to the UE 215. The control message 220 may include information indicating an SRS resource set 225. For example, the control message 220 may include an indication of up to five control resource sets, each control resource set being associated with a CORESET identifier (e.g., CORESET ID). Additionally, each CORESET may correspond to a variety of SRS resource sets 225. Thus, each SRS resource set 225 may be associated with a CORESET identifier (CORESET ID). For example, the SRS resource set 225-a may be associated with CORESET ID=1, and the SRS resource set 225-b may be associated with CORESET ID=2. Additionally, the control message 220 may indicate a corresponding CORESETPoolIndex value for each CORESET (e.g., and each associated SRS resource set 225). In some cases, each CORESETPoolIndex value may correspond to a different TRP 210. For example, a CORESETPoolIndex value = 0 may correspond to TRP 210-a, and a CORESETPoolIndex value = 1 may correspond to TRP 210-b. In the example of wireless communication system 200, UE 215 may be configured (e.g., by one or more control messages 220) by a higher layer parameter PDCCH-Config containing two different values ​​of CORESETPoolIndex inf CORESETs for the active BWP of the serving cell.

[0146] The UE 215 and the network entity 205 may communicate using the PUSCH 250 in a TDM manner corresponding to different transmission parameters (such as different beam or spatial relationship parameters, different power control parameters, or different precoding parameters, or any combination thereof) indicated or configured to the UE 215. In some implementations, the PUSCH 250 repetitions may be scheduled by a single DCI 235, which may belong to two sets (e.g., each set is associated with a different CORESETPoolIndex value), where each set may have a corresponding precoding beam (e.g., a corresponding transmit configuration indicator (TCI) state or spatial relationship) or a corresponding power control parameter, or any combination thereof. To facilitate such separate PUSCH 250 repetition sets, the UE 215 and the network entity 205 may associate separate PUSCH 250 repetition sets with separate SRS resource sets 225.

[0147] In an example of a wireless communication system 200, a UE 215 and a network entity 205 may support multi-TRP transmission based on multi-DCI. In some examples, a UE 215 may receive a message (e.g., a first PUSCH message) from a TRP 210-a including a first DCI 235 transmitted from the TRP 210-a, the first DCI scheduling a first PUSCH 250 to be transmitted to the TRP 210-a. Additionally, the UE 215 may receive another message (e.g., transmitted from a TRP 210-b) including a second DCI 235 scheduling a second PUSCH 250 to be transmitted to the TRP 210-b (e.g., a second PUSCH message). The UE 215 may perform TRP 210 differentiation based on a CORESETPoolIndex value. In some cases, multiple DCIs 235 may be scheduled for two different PUSCHs 250 in the same serving cell or component carrier that are TDMed (eg, sent to two different TRPs 210, or associated with different CORESETPoolIndex values).

[0148] In some other cases, multiple DCIs 235 may schedule two different PUSCHs 250 (e.g., sent to two different TRPs 210) that at least partially overlap in the time domain in the same serving cell or component carrier. Here, the first PUSCH 250 may be associated with a first SRS resource set 225 associated with a first CORESETPoolIndex value. For example, the UE 215 may send the first PUSCH 250 to the TRP 210-a using an SRS resource set 225 (e.g., SRS resource set 225-a or SRS resource set 225-b) associated with CORESETPoolIndex=0. Additionally, the second PUSCH 250 may be associated with a second SRS resource set 225 associated with a second CORESETPoolIndex value. For example, the UE 215 may send the second PUSCH 250 to the TRP 210 - a using an SRS resource set 225 (eg, SRS resource set 225 - c or SRS resource set 225 - d ) associated with CORESETPoolIndex=1.

[0149] In the case where the UE 215 is configured to transmit two PUSCHs 250 that at least partially overlap in the time domain, the UE 215 may support one of a variety of different configurations regarding how many layers the UE may use for the PUSCH 250. That is, the UE 215 may be able to transmit up to (X1, X2) layers in an STxMP deployment. Here, when a first PUSCH 250 and a second PUSCH 250 are transmitted via the same component carrier and at least partially overlap in the time domain, the UE 215 may be able to transmit the first PUSCH 250 via a first SRS resource using up to X1 layers and transmit the second PUSCH 250 via a second SRS resource using up to X2 layers. Additionally, in an STxMP deployment, the UE 215 may be able to support up to (P1, P2) ports for PUSCH transmission. That is, when the first and second PUSCH 250 are transmitted via the same component carrier and at least partially overlap in the time domain, the UE 215 may be able to transmit the first PUSCH 250 transmission via the first SRS resource using up to P1 ports, and transmit the second PUSCH 250 transmission via the second SRS resource using up to P2 ports. According to the first configuration, when operating in a single transmit receive point (TRP) deployment, the UE 215 may use up to max(X1,X2) layers and up to max(P1,P2) ports to transmit the PUSCH 250. According to the second configuration, when operating in an sTRP deployment, the UE 215 may use up to X1+X2 layers and up to P1+P2 ports to transmit the PUSCH 250. In some examples, X1 and X2 may be equal to 1 or 2.

[0150] Examples of the first configuration and the second configuration may be further described according to Table 9 shown below.

[0151] Table 9: Maximum number of ports and layers supported in STxMP and sTRP

[0152]

[0153] These two configurations may be valid because they correspond to different UE 215 RF or baseband specific implementations. In the case of non-ideal backhaul between two TRPs 210, scheduling may be based on the first configuration even when the UE 215 is capable of supporting the second case. In some examples, TRP 210-b may not be aware of whether TRP 210-a dynamically schedules the first PUSCH 250 in a given time slot. Therefore, the UE 215 may assume the case where PUSCH 250 has been scheduled. In this case, when the first PUSCH 250 is not actually scheduled, TRP 210-b may not use a higher number of layers for the second PUSCH 250. The second configuration may be applicable when the UE 215 is capable of implementing the second configuration and when the two TRPs 210 can dynamically coordinate (e.g., at least regarding whether the other TRP 210 will schedule overlapping PUSCH 250).

[0154] In the example of the wireless communication system 200, the UE 215 may send a capability report 255 to the network entity 205 indicating the capability of the UE 215 to support the number of ports. That is, the UE 215 may indicate a threshold (e.g., maximum) number of PUSCH ports that the UE 215 can support, which may be the same as the maximum number of SRS ports. In one case, the UE 215 may send an explicit indication of whether the UE 215 supports the first configuration or the second configuration via the capability report 255. Here, when the UE 215 indicates the capability (e.g., existing or legacy capability) that the UE 215 supports a maximum number of P SRS ports for SRS resources, in the case where the UE 215 supports the first configuration, when two PUSCHs 250 overlap (e.g., in the same component carrier), the UE 215 may simultaneously support (P, P) PUSCH ports for two PUSCHs 250. Additionally, in case that the UE 215 supports the second configuration, when two PUSCHs 250 overlap, the UE 215 may simultaneously support (P / 2, P / 2) PUSCH ports for the two PUSCHs 250 .

[0155] In another case, the UE 215 may send an indication of the maximum number of SRS ports per SRS resource for the CB-based PUSCH via the capability report 255. Here, in the case where the PUSCH 250 does not overlap in time with any other PUSCH 250, the UE 215 may indicate a first maximum number of SRS ports (e.g., P ports) applicable or supportable to the UE 215. Additionally, in the case where two PUSCHs 250 overlap in time, the UE 215 may indicate a second one or more maximum numbers of SRS ports associated with each SRS resource set or CORESETPoolIndex value applicable or supportable to the UE 215 (e.g., (P1, P2) ports). In one example, for the second one or more maximum numbers of SRS ports, the UE 215 may indicate a number or quantity (e.g., P1=P2) that may be associated with each of the two SRS resource sets 225. In another example, for the second one or more maximum numbers of SRS ports, the UE 215 may indicate a separate number of port values ​​(e.g., with corresponding CORESETPoolIndex values) that are each associated with a corresponding SRS resource set 225. Here, P1 may be the same as P2 or different from P2. In this case, the values ​​of P, P1, and P2 indicated by the UE 215 (e.g., within the capability report 255) may determine whether the UE 215 is capable of supporting the first configuration or the second configuration.

[0156] In some cases, the configuration may be indicated to the UE 215 in one of the control messages 220. For example, the network entity 205 may send a control message 220 (e.g., via RRC signaling) indicating that the UE 215 implements a first configuration (e.g., where the UE 215 may use up to max (X1, X2) layers and up to max (P1, P2) ports to send PUSCH 250) or a second configuration (e.g., when operating in an sTRP deployment, the UE 215 may use up to X1+X2 layers and up to P1+P2 ports to send PUSCH 250). In some cases, the UE 215 may be configured to implement the first configuration or the second configuration per DCI 235 format (e.g., the UE 215 is configured with the first configuration or the second configuration for DCI formats 0_1 and 0_2, respectively), per BWP, or per component carrier.

[0157] However, in some wireless communication systems 200, allowing the UE 215 to implement the second configuration may be incompatible with some interpretation rules at the UE 215. That is, in order to dynamically switch between sTRP and STxMP, the size of the TPMI field 240, the indication of the TPMI field 240, and the interpretation of the TPMI field 240 may take into account both STxMP and sTRP scheduling.

[0158] Thus, in some implementations of the present disclosure, the UE 215 and the network entity 205 may support one or more configuration or signaling-based mechanisms, according to which the network entity 205 may configure one or more maxRank values ​​and one or more maximum number of port values ​​according to a first configuration or a second configuration, and according to which the UE 215 may interpret one or more fields in the DCI 235 to identify, ascertain, or otherwise determine information associated with an sTRP or STxMP PUSCH 250 message. For example, in a scenario where the UE 215 is configured according to the first configuration, the network entity 205 may configure (e.g., via one or more control messages 220 sent via RRC signaling) a maxRank value and a maximum number of ports value for each SRS resource set 225 (e.g., X1 and P1 for a first SRS resource set 225-a, and X2 and P2 for a second SRS resource set 225-d), which values ​​are applicable regardless of whether sTRP operation or STxMP operation is indicated.

[0159] Additionally or alternatively, in a scenario where the UE 215 is configured according to the second configuration, the network entity 205 may configure (e.g., via one or more control messages 220 sent via RRC signaling) a baseline maxRank value (e.g., X) and a baseline maximum number of ports value (e.g., P) applicable when indicating sTRP operation and one or more additional maxRank values ​​and maximum number of ports values ​​for each SRS resource set 225-b applicable when indicating STxMP operation (e.g., X1 and P1 for the first SRS resource set and X2 and P2 for the second SRS resource set 225-d). Additionally or alternatively, in a scenario where the UE 215 is configured according to the second configuration, the network entity 205 may indicate via a field in the DCI 235 whether a scheduled PUSCH 250 overlaps in time with another scheduled PUSCH 250. In this case, the UE 215 may interpret one or more fields of the DCI 235 differently based on whether a scheduled PUSCH 250 overlaps in time with another scheduled PUSCH 250. Thus, the network entity 205 may schedule PUSCH transmissions for sTRP operation or STxMP operation that conform to the maximum number of layers or ports supported by the UE 215 for the corresponding operation.

[0160] Thus, the UE 215 may be configured by one or more control messages 220 to have one of the first configuration or the second configuration (e.g., via RRC signaling). The one or more control messages 220 may additionally indicate whether any restrictions are required (e.g., for a maximum number of ports or layers for PUSCH transmission), the configuration of the SRS resource set 225 (e.g., and how many SRS resource sets 225 may be configured), the field in the DCI 235 indicating whether there is another overlapping PUSCH 250, the determination of the number of PUSCH ports, and the interpretation of the TPMI field 240 and the SRI field 245 (e.g., whether the interpretation depends on whether there is another overlapping PUSCH 250), or a combination thereof. In some cases, the UE 215 may be configured per DCI format (e.g., separately configured for DCI formats 0_1 and 0_2), per BWP, or per CC.

[0161] Figure 3 An example of a wireless communication system 300 supporting an SRI design for CB-based communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 can implement or be implemented to implement or facilitate aspects of the wireless communication system 100 or the wireless communication system 200. For example, the wireless communication system 300 illustrates communication between a UE 315 and a network entity 305 associated with a TRP 310-a and a TRP 310-b, which can be as described in reference to Figure 1 and Figure 2 Examples of corresponding devices are illustrated and described.

[0162] In some examples, the wireless communication system 300 may illustrate multiple PUSCH transmissions from a single UE 315 to multiple TRPs 310 of a network entity 305 via different directional beams 320 (including directional beam 320-a and directional beam 320-b), where the different directional beams 320 may be associated with different SRS resource sets 325, different TCI states, different layers, different PUSCH ports, or different panels of the UE 315, or any combination thereof. Figure 3 As described in the example of , UE 315 and network entity 305 can support a multi-TRP framework based on multi-DCI, where two PUSCHs are associated with different CORESETPoolIndex values. The first PUSCH (associated with CORESETPoolIndex value 0) can be associated with the first SRS resource set 325-a and can be sent using a first beam or TCI state or power control parameter or predecoder. Similarly, the second PUSCH (associated with CORESETPoolIndex value 1) can be associated with the second SRS resource set 325-b and can be sent using a second beam or TCI state or power control parameter or predecoder.

[0163] In some examples, two different PUSCHs in the same serving cell or component carrier may overlap partially or completely at least in the time domain. PUSCHs may or may not overlap in the frequency domain. In the example of the PUSCH transmission scheme 330-a, the first PUSCH and the second PUSCH may overlap in both time and frequency. In the example of the PUSCH transmission scheme 330-b, the first PUSCH and the second PUSCH overlap in time but do not overlap in frequency. In the example of the PUSCH transmission scheme 330-c, the first PUSCH and the second PUSCH partially overlap in time but do not overlap in frequency. In the example of the PUSCH transmission scheme 330-a, the first PUSCH and the second PUSCH partially overlap in time and frequency. In order to identify SRS resources for sending overlapping PUSCH transmissions, the number of ports and layers for each PUSCH transmission, and the predecoder for the PUSCH transmissions, the UE 315 can interpret the control message (e.g., multiple messages including DCI) according to the techniques described herein, and can use at least one of the PUSCH transmission scheme 330-a, PUSCH transmission scheme 330-b, PUSCH transmission scheme 330-c, and PUSCH transmission scheme 330-d to send PUSCH transmissions that at least partially overlap in the time domain.

[0164] Figure 4 An example of a resource selection process 400 for supporting SRI design for CB-based communication according to one or more aspects of the present disclosure is illustrated. The resource selection process 400 may be implemented or implemented to implement the Figures 1 to 3 Aspects of the wireless communication system described.

[0165] The SRS resource set 425 may be configured by a network entity and indicated to the UE via RRC signaling. Here, the network entity may configure the SRS resource set 425-a to correspond to a CORESETPoolIndex value of 0 (e.g., associated with a PUSCH transmission to a first TRP). Additionally, the network entity may configure the SRS resource set 425-b to correspond to a CORESETPoolIndex value of 1 (e.g., associated with a PUSCH transmission to a second TRP). For example, the SRS resource set 425-a may include SRS resources 430-a and SRS resources 430-b. In addition, the SRS resource set 425-b may include SRS resources 430-c and SRS resources 430-d.

[0166] The UE may rely on the resource selection process 400 to identify one or more SRS resources 430 for transmitting one or more PUSCHs 450. For example, the UE may select a single SRS resource 430-a to transmit a single PUSCH 450-a in sTRP mode. Additionally, the UE may select two SRS resources 430-c and 430-d in STxMP mode to transmit two PUSCHs 450-b and 450-c, respectively.

[0167] In the example of resource selection process 400, the network entity may send signaling (e.g., via RRC signaling) to the UE indicating maxRank=X. Here, the maxRank value may correspond to the maximum number of layers of PUSCH 450, regardless of whether there is another time-overlapping PUSCH 450 (e.g., associated with another CORESETPoolIndex value) in the same component carrier, such as in STxMP mode. Thus, the UE may identify that the maximum number of layers of PUSCH 450 is equal to X, regardless of whether the UE sends PUSCH 450-a in sTRP mode or PUSCH 450-b and 450-c in STxMP mode.

[0168] In one case, the network entity may indicate the maxRank value according to the CORESETPoolIndex value (e.g., according to the SRS resource set 425). Here, the network entity may indicate a first value X1 of the SRS resource set 425-a (e.g., which is associated with a CORESETPoolIndex value = 0), and may indicate a second value X1 of the SRS resource set 425-b (e.g., which is associated with a CORESETPoolIndex value = 1). In some cases, X1 may be the same as or different from X2. In another case, the network entity may indicate the maxRank value according to the DCI format (e.g., the network entity may configure the maxRank value separately for DCI format 0_1 ​​and DCI format 0_2), or according to the BWP, or according to the CC. Here, the value of X1 may be the same as the value of X2.

[0169] To configure the UE to transmit one or more PUSCHs 450, the network entity may transmit a message including a DCI 435 (e.g., DCI 435-a, DCI 435-b, DCI 435-c). In some cases, the DCI 435 may include a TPMI field 440 (e.g., TPMI field 440-a, TPMI field 440-b, TPMI field 440-c), and may include an SRI field 445 (e.g., SRI field 445-a, SRI field 445-b, SRI field 445-c) when one or more SRS resource sets 425 include more than one SRS resource 430. In some cases, the network entity may transmit the DCI via resources (e.g., CORESET) associated with the same CORESETPoolIndex value as the SRS resource set 425 that includes the SRS resource 430 for transmitting the corresponding PUSCH 450. For example, to schedule PUSCH 450 to be sent by SRS resource 430 (e.g., SRS resource 430-a or 430-b) within SRS resource set 425-a associated with CORESETPoolIndex value 0, the network entity may send DCI 435 via a control source associated with the same CORESETPoolIndex value 0.

[0170] Based on receiving the DCI 435, the UE may interpret the TPMI field 440 of the scheduled PUSCH 450 regardless of whether there is a second overlapping PUSCH 450. Additionally, the UE may interpret the SRI field 445 of the scheduled PUSCH 450 regardless of whether there is a second overlapping PUSCH 450. That is, the UE may identify the mapping between the value within the TPMI field 440 of the DCI 435 and the number of ports and layers used to transmit the PUSCH 450 and the precoding matrix used to transmit the PUSCH 450, regardless of whether the scheduled PUSCH 450 overlaps in time with another PUSCH 450. Additionally, the UE may interpret the value in the SRI field 445 to identify the SRS resource 430 (e.g., for transmitting the PUSCH 450) from the SRS resource set 425 regardless of whether the scheduled PUSCH 450 overlaps in time with another PUSCH 450.

[0171] In the case where the network entity has configured the UE (e.g., via RRC signaling) to operate according to a first configuration, wherein the UE is capable of supporting up to (X1, X2) layers and (P1, P2) layers in STxMP mode, and when operating in sTRP mode, the UE is capable of supporting up to max (X1, X2) layers and up to max (P1, P2) ports, each PUSCH 450 may be scheduled with up to the number of layers of maxRank (e.g., X1 or X2), regardless of whether there is another overlapping PUSCH. Additionally, each PUSCH may be scheduled with the maximum number of ports (e.g., P1 or P2, which may be indicated by the UE via a capability report), regardless of whether there is another overlapping PUSCH 450. For example, the UE may send PUSCH 450-a according to the sTRP mode (e.g., in the absence of overlapping PUSCHs in the time domain) using a number of layers less than or equal to maxRank (e.g., X1 or X2), and send PUSCH 450-b and 450-c according to the STxMP mode. Additionally, the UE may send PUSCH 450-a and PUSCH 450-b and 450-c using a number of ports less than or equal to the maximum number of PUSCH ports P1 or P2 that the UE can support.

[0172] In the case where the network entity has configured the UE (e.g., via RRC signaling) to operate according to a second configuration, wherein the UE is capable of supporting up to (X1, X2) layers and (P1, P2) layers in STxMP mode, and up to X1+X2 layers and up to P1+P2 ports when operating in sTRP mode, the number of layers or ports associated with a PUSCH 450 scheduled by the network for transmission by the UE may be based on whether the PUSCH 450 overlaps with another PUSCH 450 in the time domain. That is, when there are no overlapping PUSCHs 450, the network entity may indicate up to X (e.g., corresponding to maxRank) layers for a PUSCH 450-a. Additionally, when there are no overlapping PUSCHs 450, the network entity may indicate up to P (e.g., the maximum number of ports that the UE is capable of supporting) for a PUSCH 450-a.

[0173] In the event that the network entity has configured the UE to operate according to the second configuration and schedule overlapping PUSCH 450-b and 450-c, the network entity may schedule PUSCH 450-b and PUSCH 450-c having less than one or more threshold numbers of PUSCH layers and less than one or more threshold numbers of ports. In some cases, the threshold number of layers and ports may be associated with each CORESETPoolIndex value. That is, the threshold number of layers for sending PUSCH 450-b that is sent via SRS resource 430-b and is therefore associated with CORESETPoolIndex value 0 may correspond to X1, and the threshold number of ports for sending PUSCH 450-b may correspond to P1. Here, both X1 and P1 may be values ​​specific to PUSCH 450 sent via SRS resource 430 associated with CORESETPoolIndex value 0. Additionally, the threshold number of layers for transmitting a PUSCH 450-c transmitted via an SRS resource 430-d and thus associated with a CORESETPoolIndex value of 1 may correspond to X2, and the threshold number of ports for transmitting the PUSCH 450-c may correspond to P2. Here, both X2 and P2 may be values ​​specific to a PUSCH 450 transmitted via an SRS resource 430 associated with a CORESETPoolIndex value of 1.

[0174] Here, in the case where another PUSCH 450-c associated with a second CORESETPoolIndex value (e.g., CORESETPoolIndex value 1) with time domain overlap is scheduled in the same CC, it may not be desirable to indicate to the UE via the TPMI field 440-b more than X1 layers for the PUSCH 450-b associated with the first CORESETPoolIndex value (e.g., CORESETPoolIndex value 0). Additionally, in the case where another PUSCH 450-b associated with a first CORESETPoolIndex value (e.g., CORESETPoolIndex value 0) with time domain overlap is scheduled in the same CC, it may not be desirable to indicate to the UE via the TPMI field 440-c more than X2 layers for the PUSCH 450-c associated with the second CORESETPoolIndex value (e.g., CORESETPoolIndex value 1). Additionally, in the case where another PUSCH 450-c associated with a second CORESETPoolIndex value (e.g., CORESETPoolIndex value 1) with time domain overlap is scheduled in the same CC, it may not be desirable to indicate to the UE via the SRI field 445-b more than P1 ports for the PUSCH 450-b associated with the first CORESETPoolIndex value (e.g., CORESETPoolIndex value 0). Additionally, in the case where another PUSCH 450-c associated with a first CORESETPoolIndex value (e.g., CORESETPoolIndex value 0) with time domain overlap is scheduled in the same CC, it may not be desirable to indicate to the UE via the SRI field 445-c more than P2 ports for the PUSCH 450-c associated with the second CORESETPoolIndex value (e.g., CORESETPoolIndex value 1).

[0175] In some cases, the threshold number of layers (e.g., X1 and X2) may be indicated by the network entity to the UE via RRC signaling (e.g., separate from configuring maxRank=X (which may be used by the UE to interpret the SRI field 445)). Additionally or alternatively, the UE may indicate the threshold number of layers (e.g., X1 and X2) within a capability report to the network entity. In either case, the values ​​of X1 and X2 may be configured such that maxRank=X≤X1+X2. Additionally, the threshold number of ports (e.g., P1 and P2) may be indicated by the UE to the network entity via a capability report. That is, the UE can send a capability report to the network entity, which indicates P within the capability report (e.g., the maximum number of ports that the UE can support), P1 (e.g., when the PUSCH overlaps with another PUSCH in time, the maximum number of ports that the UE can support for PUSCH sent via SRS resources 430 associated with a CORESETPoolIndex value of 0), and P2 (e.g., when the PUSCH overlaps with another PUSCH in time, the maximum number of ports that the UE can support for PUSCH sent via SRS resources 430 associated with a CORESETPoolIndex value of 1).

[0176] In some cases, when the UE is configured according to the second configuration, in order to enable the UE to dynamically switch between sending PUSCH 450-a according to the sTRP mode and sending PUSCH 450-b and 450-c according to the STxMP mode, the network entity may configure each SRS resource set 425 to include at least one SRS resource 430 associated with P ports for non-overlapping PUSCH 450-a transmission and at least one SRS resource 430 associated with P1 ports (e.g., for SRS resource set 425-a) or P2 ports (e.g., for SRS resource set 425-b) for overlapping PUSCH 450-b and 450-c transmission.

[0177] Figure 5 An example of a resource selection process 500 for supporting SRI design for CB-based communication according to one or more aspects of the present disclosure is illustrated. The resource selection process 500 may be implemented or implemented to implement the Figures 1 to 3 Aspects of the wireless communication system described.

[0178] The SRS resource set 525 may be configured by a network entity and indicated to the UE via RRC signaling. Here, the network entity may configure the SRS resource set 525-a to correspond to a CORESETPoolIndex value of 0 (e.g., associated with a PUSCH transmission to a first TRP). Additionally, the network entity may configure the SRS resource set 525-b to correspond to a CORESETPoolIndex value of 1 (e.g., associated with a PUSCH transmission to a second TRP). The SRS resource set 525-a may include SRS resources 530-a, and the SRS resource set 525-b may include SRS resources 530-b. The network entity may additionally configure the UE (e.g., via RRC signaling) to operate according to a second configuration, wherein in the case where the UE is capable of supporting up to (X1, X2) layers and (P1, P2) layers in STxMP mode, when operating in sTRP mode, the UE is capable of supporting up to X1+X2 layers and up to P1+P2 ports.

[0179] The UE may rely on the resource selection process 500 to identify one or more SRS resources 530 for transmitting one or more PUSCHs 550. For example, the UE may select a single SRS resource 530-a to transmit a single PUSCH 550-a in sTRP mode. Additionally, the UE may select two SRS resources 530-a and 530-b in STxMP mode to transmit two PUSCHs 550-b and 550-c, respectively.

[0180] To configure the UE to transmit one or more PUSCHs 550, the network entity may transmit a message including a DCI 535 (e.g., DCI 535-a, DCI 535-b, DCI 535-c). In some cases, the network entity may transmit the DCI 535 via resources (e.g., CORESET) associated with the same CORESETPoolIndex value as the SRS resource set 525 that includes the SRS resource 530 for transmitting the corresponding PUSCH 550. For example, to schedule a PUSCH 550-a or 550-b to be transmitted by an SRS resource 530-a (e.g., SRS resource 530-a or 530-b) within an SRS resource set 525-a associated with a CORESETPoolIndex value of 0, the network entity may transmit the DCI 535 via a control source associated with the same CORESETPoolIndex value of 0.

[0181] The DCI 535 may include an overlap field 505, a TPMI field 540, and, in the case where one or more SRS resource sets 525 include more than one SRS resource 530, an SRI field 545. The overlap field 505 within the DCI 535 may indicate (e.g., via a single bit) the presence of another PUSCH 550 that overlaps in time with the PUSCH 550 scheduled by the DCI 535 (e.g., in the case of STxMP) or the absence of another PUSCH that overlaps in time with the PUSCH 550 scheduled by the DCI 535 (e.g., in the case of sTRP). For example, the overlap field 505-a within the DCI 535-a may indicate that no other PUSCH 550 overlaps in time with the PUSCH 550-a. Additionally, the overlap fields 505-b and 505-c may both indicate that the scheduled PUSCH 550 overlaps at least partially with another PUSCH 550 in the time domain.

[0182] In some cases, the UE may interpret the SRI field 545 (e.g., SRI field 545-a, SRI field 545-b, SRI field 545-c) regardless of whether there is a second overlapping PUSCH 550. That is, the UE may interpret the value in the SRI field 545 to identify the SRS resource 530 (e.g., for transmitting the PUSCH 550) from the SRS resource set 525, regardless of whether the scheduled PUSCH 550 overlaps in time with another PUSCH 550. In some cases, the DCI 535 may not include the SRI field 545, where each SRS resource set 525 includes a single SRS resource 530. In this case, the UE may identify the SRS resource 530 for transmitting the PUSCH 550 based on the CORESETPoolIndex value associated with the CORESET in which the DCI is detected.

[0183] In the example of resource selection process 500, the UE may interpret the TPMI field 540 based on whether there is a second overlapping PUSCH 550. In some examples, the size of the TPMI field 540 may be based on the maximum number of SRS ports supported by the UE.

[0184] For example, in the case where the overlap field 505 indicates that there is no overlapping PUSCH 550, the UE may transmit the PUSCH 550 using each of the PUSCH ports associated with the SRS resource 530 indicated by the SRI field 545. Additionally, the UE may interpret the TPMI field 540 according to the number of ports including each of the PUSCH ports associated with the indicated SRS resource 530. For example, in the case where the DCI 535-a indicates via the overlap field 505-a that there is no scheduled PUSCH 550 that overlaps with the PUSCH 550-a in the time domain, the UE may transmit the PUSCH 550-a using each of the SRS ports associated with the SRS resource 530-a. Additionally, the UE may interpret the TPMI field 540-a (e.g., or the TMPI field 540-b) according to a mapping based on four ports associated with the SRS resource 530-a.

[0185] In the case where the overlap field 505 indicates the presence of an overlapping PUSCH 550, the UE may transmit the PUSCH 550 having the PUSCH port subset associated with the SRS resource 530 indicated by the SRI field 545. Additionally, the UE may interpret the TPMI field 540 according to the number of ports included in each subset of the PUSCH port subsets associated with the indicated SRS resource 530. For example, in the case where the DCI 535-c indicates via the overlap field 505-c that there is a scheduled PUSCH 550-b that overlaps with the PUSCH 550-c in the time domain, the UE may transmit the PUSCH 550-c using each of the two SRS ports included in the SRS port subset associated with the SRS resource 530-b. Additionally, the UE may interpret the TPMI field 540-c according to a mapping based on four ports associated with the SRS resource 530-b. Table 10 shown below illustrates an example mapping between the indicated SRS resources 530 and the number of PUSCH ports used to transmit the PUSCH 550 .

[0186]

[0187] Table 10: Mapping between PUSCH ports and indicated SRS resources

[0188] In some examples, the UE may identify a subset of ports associated with each SRS resource 530 by selecting the first half of the ports associated with the SRS resource 530. For example, the UE may identify two subsets of ports associated with the SRS resource 530-a by selecting the first two ports from the four ports associated with the SRS resource 530-a. In some other examples, the network entity may configure (e.g., via RRC signaling) a subset of ports for each SRS resource 530. In some cases, the network entity may indicate, for each SRS resource 530, the number of ports (m) in the total number of ports associated with the SRS resource 530 included in the subset. That is, for the SRS resource 530-b, the network entity may indicate (e.g., via RRC signaling) the number of ports. The UE may then identify a subset of ports by selecting the first m ports (e.g., two) from the total number of ports associated with the SRS resource 530-b. In some other cases, the network entity may indicate, for each SRS resource 530, the number of ports associated with the ports within the subset. For example, the network entity may indicate that SRS port numbers 1 and 3 (eg, from a set of ports including SRS ports 0, 1, 2, and 3) are in the subset of ports associated with SRS resource 530-a.

[0189] In some other examples, the UE may indicate a subset of ports for each SRS resource based on information within a capability report sent by the UE to a network entity. That is, the UE may indicate, via a capability report, a first number of ports P1 associated with an SRS resource 530 associated with a CORESETPoolIndex value of 0, and may indicate a second number of ports P2 associated with an SRS resource 530 associated with a CORESETPoolIndex value of 1. Here, the subset of ports for each SRS resource 530 associated with a CORESETPoolIndex value of 0 may include the first P1 ports, and the subset of ports for each SRS resource 530 associated with a CORESETPoolIndex value of 1 may include the first P2 ports.

[0190] Figure 6 An example of a resource selection process 600 for supporting SRI design for CB-based communication according to one or more aspects of the present disclosure is illustrated. The resource selection process 600 may be implemented or implemented to implement the Figures 1 to 3 Aspects of the wireless communication system described.

[0191] The SRS resource set 625 may be configured by a network entity and indicated to the UE via RRC signaling. Here, the network entity may configure the SRS resource sets 625-a and 625-c to correspond to a CORESETPoolIndex value of 0 (e.g., associated with a PUSCH transmission to a first TRP). The SRS resource set 625-a may include an SRS resource 630-a, the SRS resource set 625-b may include an SRS resource 630-b, the SRS resource set 625-c may include an SRS resource 630-c, and the SRS resource set 625-d may include an SRS resource 630-d. Additionally, the network entity may configure the SRS resource sets 625-b and 625-d to correspond to a CORESETPoolIndex value of 1 (e.g., associated with a PUSCH transmission to a second TRP). The network entity may additionally configure the UE (e.g., via RRC signaling) to operate according to a second configuration, wherein when the UE is capable of supporting up to (X1, X2) layers and (P1, P2) layers in STxMP mode, the UE is capable of supporting up to X1+X2 layers and up to P1+P2 ports when operating in sTRP mode.

[0192] The network entity may additionally configure each of the SRS resource sets 625 to be associated with a PUSCH 650 when there is no overlapping PUSCH 650 (e.g., for sTRP transmission), or to be associated with a PUSCH 650 when another PUSCH 650 at least partially overlaps with the PUSCH 650 in the time domain (e.g., for STxMP transmission). In some cases, the network entity may explicitly indicate to the UE whether each SRS resource set 625 is configured for PUSCH 650 (e.g., via RRC signaling) when there is an overlapping PUSCH 650 or when there is no overlapping PUSCH 650. Additionally or alternatively, the UE may implicitly determine whether each SRS resource set 650 is configured for PUSCH 625 when there is an overlapping PUSCH 650 or when there is no overlapping PUSCH 650 based on an SRS resource set identifier associated with each SRS resource set 625.

[0193] In some cases, by configuring each SRS resource set 625 for non-overlapping PUSCH transmission or overlapping PUSCH transmission, the network entity may configure each SRS resource set 625 to be associated with the number of ports and layers to ensure that the UE operates according to a second configuration, wherein when the UE is capable of supporting up to (X1, X2) layers and (P1, P2) layers in STxMP mode, the UE is capable of supporting up to X1+X2 layers and up to P1+P2 ports when operating in sTRP mode.

[0194] In an example of the resource selection process 600: the SRS resource set 625-a can be associated with a CORESETPoolIndex value of 0 and configured for PUSCH 650 when there are no other overlapping PUSCH 650, the SRS resource set 625-b can be associated with a CORESETPoolIndex value of 1 and configured for PUSCH 650 when there are no other overlapping PUSCH 650, the SRS resource set 625-c can be associated with a CORESETPoolIndex value of 0 and configured for PUSCH 650 when there is another overlapping PUSCH 650, and the SRS resource set 625-d can be associated with a CORESETPoolIndex value of 1 and configured for PUSCH 650 when there is another overlapping PUSCH 650. In this example, SRS resource set 625-a and SRS resource set 625-c may be configured with the same power control parameter set, and SRS resource sets 625-b and 625-d may be configured with the same power control parameter set. In some cases, SRS resource sets 625-a and 625-b configured for when there are no other overlapping PUSCHs 650 may be associated with four ports. Additionally, SRS resource sets 625-c and 625-d configured for when there are overlapping PUSCHs 650 may be associated with two ports.

[0195] The SRS resource set 625-a and the SRS resource set 625-c can be configured with the same number of SRS resources 630. Here, the i-th SRS resource 630-a and the i-th SRS resource 630-c in the SRS resource set 625-a can be configured with the same beam, TCI state or other spatial relationship information. Additionally, the number of SRS ports of the i-th SRS resource 630-c in the SRS resource set 625-c can be configured to be less than the number of SRS ports of the i-th SRS resource 630-a in the SRS resource set 625-a. In addition, the SRS resource set 625-b and the SRS resource set 625-d can be configured with the same number of SRS resources 630. Here, the i-th SRS resource 630-b and the i-th SRS resource 630-d in the SRS resource set 625-b can be configured with the same beam, TCI state or other spatial relationship information. Additionally, the number of SRS ports of the i-th SRS resource 630 - d in the SRS resource set 625 - d may be configured to be smaller than the number of SRS ports of the i-th SRS resource 630 - b in the SRS resource set 625 - b .

[0196] The UE may rely on the resource selection process 600 to identify one or more SRS resources 630 for transmitting one or more PUSCHs 650. For example, the UE may select a single SRS resource 630-a to transmit a single PUSCH 650-a in sTRP mode. Additionally, the UE may select two SRS resources 630-c and 630-d in STxMP mode to transmit two PUSCHs 650-b and 650-c, respectively.

[0197] To configure the UE to transmit one or more PUSCHs 650, the network entity may transmit a message including a DCI 635. In some cases, the network entity may transmit the DCI 635 via resources (e.g., a CORESET) associated with the same CORESETPoolIndex value as the SRS resource set 625 that includes the SRS resource 630 used to transmit the corresponding PUSCH 650. For example, to schedule a PUSCH 650-a or 650-b to be transmitted by an SRS resource 630 (e.g., an SRS resource 630-a or 630-c) within an SRS resource set 625 associated with a CORESETPoolIndex value of 0, the network entity may transmit the DCI 635 via a control source associated with the same CORESETPoolIndex value of 0.

[0198] The DCI 635 may include an overlap field 605, a TPMI field 640, and, in the case where one or more SRS resource sets 625 include more than one SRS resource 630, an SRI field 645. The overlap field 605 within the DCI 635 may indicate (e.g., via a single bit) the presence of another PUSCH 650 that overlaps in time with the PUSCH 650 scheduled by the DCI 635 (e.g., in the case of STxMP) or the absence of another PUSCH that overlaps in time with the PUSCH 650 scheduled by the DCI 635 (e.g., in the case of sTRP). For example, the overlap field 605-a within the DCI 635-a may indicate that no other PUSCH 650 overlaps in time with the PUSCH 650-a. Additionally, the overlap fields 605-b and 605-c may both indicate that the scheduled PUSCH 650 overlaps at least partially with another PUSCH 650 in the time domain.

[0199] In some cases, the UE may interpret the SRI field 645 (e.g., SRI field 645-a, SRI field 645-b, SRI field 645-c) based on whether there is a second overlapping PUSCH 650. In one example, for PUSCH 650, the UE may interpret the overlap field 605 as indicating one of two SRS resource sets 625 from the SRS resource set 625 associated with the CORESETPoolIndex value of the CORESET in which the DCI 635 is received. For example, the UE may receive the DCI 635-a via a CORESET associated with a CORESETPoolIndex value of 0. Here, the overlap field 605-a may indicate that the PUSCH 650-a does not overlap (e.g., by setting bits of the overlap field 605-a to 0), and the UE may interpret the overlap field 605-a as indicating the SRS resource set 625-a from the SRS resource sets 625-a and 625-c (e.g., both of which are associated with a CORESETPoolIndex value of 0). In another example, the UE may receive the DCI 635-c via a CORESET associated with a CORESETPoolIndex value of 1. Here, the overlap field 605-c may indicate that the PUSCH 650-c overlaps (e.g., by setting bits of the overlap field 605-c to 1), and the UE may interpret the overlap field 605-c as indicating the SRS resource set 625-d from the SRS resource sets 625-b and 625-d (e.g., both of which are associated with a CORESETPoolIndex value of 1).

[0200] In another example, the UE may interpret the overlap field 605 as indicating whether another overlapping PUSCH 650 is scheduled in the same component carrier. For example, in the case where the overlap field 605-a is 0 (e.g., indicating that there is no another overlapping PUSCH 650-a scheduled in the same component carrier as the PUSCH 650-a) and DCI 635-a is received in a CORESET with a CORESETPoolIndex value of 0, the UE may select an SRS resource set 625-a for the PUSCH 650-a (e.g., PUSCH transmission). Additionally, in the case where the overlap field 605-b is 1 (e.g., indicating that there is another overlapping PUSCH 650-c scheduled in the same component carrier as the PUSCH 650-b) and DCI 635-b is received in a CORESET with a CORESETPoolIndex value of 0, the UE may select an SRS resource set 625-c for the PUSCH 650-b (e.g., PUSCH transmission). Additionally, in the event that the UE receives DCI 635 in a CORESET having a CORESETPoolIndex value of 1 and including an overlap field 605 with a value of 0 (e.g., indicating that another overlapping PUSCH 650 is not scheduled in the same component carrier as the PUSCH 650), the UE may select the SRS resource set 625-b. Additionally, in the event that the UE receives DCI 635-c in a CORESET having a CORESETPoolIndex value of 1 and including an overlap field 605-c with a value of 1 (e.g., indicating that there is an overlapping PUSCH 650-b scheduled in the same component carrier as the PUSCH 650-b), the UE may select the SRS resource set 625-d.

[0201] Thus, the UE may determine an SRS resource set 625 (e.g., associated with a CORESET in which the DCI 635 is received and associated with the SRS resource set 625) for transmitting the PUSCH 650 based on a combination of the overlap field 605 and the CORESETPoolIndex value. The UE may identify the SRS resource 630 from the determined SRS resource set 625 based on the SRI field 645. In the case where each of the SRS resource sets 625 includes a single SRS resource 630, the DCI 635 may not include the SRI field 645. Here, the UE may identify the SRS resource 630 by identifying the SRS resource set 625 that includes the single SRS resource 630. In some cases, the size of the SRI field 645 may be based on the maximum number of SRS resources 630 within the SRS resource set 625. The SRI field 645 may include at least bits, where N SRSCorresponds to the maximum number of SRS resources 630 within any SRS resource set 625 .

[0202] In the example of resource selection process 600, the UE may interpret the TPMI field 640 (e.g., TPMI field 640-a, TPMI field 640-b, TMPI field 640-c) based on whether there is a second overlapping PUSCH 650. That is, the UE may interpret the TPMI field 640 based on the actual number of PUSCH ports, which may be equal to the number of SRS ports of the indicated SRS resources 630, which itself may be a function of whether there is a second overlapping PUSCH. In some cases, the size of the TPMI field 640 may be based on the maximum number of SRS ports that may be indicated on all SRS resources 630 of all four SRS resource sets 625.

[0203] Figure 7 An example of a process flow 700 in a system supporting SRI design for CB-based communications according to one or more aspects of the present disclosure is illustrated. The process flow 700 may implement or may be implemented to achieve or facilitate aspects of the wireless communication system 100, the wireless communication system 200, the wireless communication system 300, the resource selection process 400, or the resource selection process 500. For example, the process flow 700 illustrates communications between a UE 715 and a network entity 705 associated with a TRP 710-a and a TRP 710-b, which may be as described in reference to FIG. Figure 1 and Figure 2 Examples of corresponding devices are illustrated and described.

[0204] In the following description of process flow 700, operations (such as reporting or providing) may be performed in a different order than shown, or operations performed by the example device may be performed in a different order or at a different time. For example, certain operations may also be omitted from process flow 700, or other operations may be added to process flow 700. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may actually occur simultaneously. In addition, reference is made to Figure 6 The illustrated and described signaling may include one or more UCI messages, one or more DCI messages, RRC signaling, one or more MAC-CEs, or one or more data messages, or any combination thereof.

[0205] At 720, the UE 715 may receive one or more control messages from the network entity 705. The one or more control messages may indicate a number of SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages. Here, the SRS resource sets may be configured for CB use. The one or more control messages may additionally indicate at least one maximum rank value (e.g., maxRank=X) associated with a PUSCH message from the UE 715, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE.

[0206] At 725, the UE 715 may receive one or more messages including DCI scheduling a PUSCH message from the network entity 705. The DCI may include one or more TPMI fields and one or more SRI fields.

[0207] At 730, the UE 715 may interpret the DCI. For example, the UE 715 may interpret the one or more SRI fields and the one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource. In some cases, the mapping may be indicated by the number of the at least one maximum rank value and the maximum number of ports that the UE 715 can support when the PUSCH message overlaps in time with another PUSCH message (e.g., is associated with more than one PUSCH that overlaps at least partially in the time domain).

[0208] At 735 , the UE 715 may send a PUSCH message to the network entity 705 based on a mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource.

[0209] Figure 8 A block diagram 800 of a device 805 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0210] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to SRI designs for CB-based communications). The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0211] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to SRI designs for CB-based communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0212] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the SRI design for CB-based communications as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0213] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0214] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). Where implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0215] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0216] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured to or otherwise support components for: receiving one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. The communication manager 820 may be configured to or otherwise support components for: receiving a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The communication manager 820 may be configured to or otherwise support components for the following actions: interpreting one or more SRI fields and one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource in a set from a plurality of SRS resource sets, the mapping being indicated by the number of at least one maximum rank value and the maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain). The communication manager 820 may be configured to or otherwise support components for the following actions: sending an uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource in a set from a plurality of SRS resource sets.

[0217] By including or configuring a communication manager 820 according to examples as described herein, a device 805 (e.g., a processor controlling or otherwise coupled to a receiver 810, a transmitter 815, a communication manager 820, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0218] Fig. 9A block diagram 900 of a device 905 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0219] The receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to SRI designs for CB-based communications). The information may be passed to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0220] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to SRI designs for CB-based communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0221] The device 905 or its various components may be examples of components for performing various aspects of the SRI design for CB-based communications as described herein. For example, the communication manager 920 may include a control message receiver 925, a DCI receiver 930, an interpretation component 935, a PUSCH transmitter 940, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0222] According to examples as disclosed herein, the communication manager 920 may support wireless communication at the UE. The control message receiver 925 may be configured to or otherwise support components for the following actions: receiving one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and the control message receiver 925 may be configured to or otherwise support components for the following actions: at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. The DCI receiver 930 may be configured to or otherwise support components for the following actions: receiving a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The interpretation component 935 may be configured to or otherwise support components for interpreting one or more SRI fields and one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by the number of at least one maximum rank value, and the interpretation component 935 may be configured to or otherwise support components for the following actions: the maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain). The PUSCH transmitter 940 may be configured to or otherwise support components for the following actions: sending an uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets.

[0223] Fig.10A block diagram 1000 of a communication manager 1020 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing aspects of the SRI design for CB-based communications as described herein. For example, the communication manager 1020 may include a control message receiver 1025, a DCI receiver 1030, an interpretation component 1035, a PUSCH transmitter 1040, a capability component 1045, a configuration component 1050, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0224] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at the UE. The control message receiver 1025 may be configured to or otherwise support components for the following actions: receiving one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and the control message receiver 1025 may be configured to or otherwise support components for the following actions: at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. The DCI receiver 1030 may be configured to or otherwise support components for the following actions: receiving a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The interpretation component 1035 may be configured to or otherwise support components for interpreting one or more SRI fields and one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by the number of at least one maximum rank value, and the interpretation component 1035 may be configured to or otherwise support components for the following actions: the maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain). The PUSCH transmitter 1040 may be configured to or otherwise support components for the following actions: transmitting an uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets.

[0225] In some examples, capability component 1045 may be configured to or otherwise support components for sending information associated with a maximum number of ports that the UE is capable of supporting via a capability report when an uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message is associated with a single uplink shared channel, or both, wherein receiving the message including the DCI is based on sending the information via the capability report.

[0226] In some examples, configuration component 1050 may be configured as or otherwise support components for the following actions: receiving an indication of a configuration associated with the at least one maximum rank value, wherein the configuration is a first configuration or a second configuration. In some examples, configuration component 1050 may be configured as or otherwise support components for the following actions: a first configuration, the first configuration indicating that in the case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the larger of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource, and configuration component 1050 may be configured as or otherwise support components for the following actions: a second configuration, the second configuration indicating that in the case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

[0227] In some examples, the configuration is indicated per DCI format, per bandwidth part, or per component carrier.

[0228] In some examples, to support receiving one or more control messages indicating at least one maximum rank value, the control message receiver 1025 may be configured as or otherwise support components for receiving an indication of a corresponding maximum rank value for each corresponding SRS resource set in a set of multiple SRS resource sets configured at the UE.

[0229] In some examples, interpreting the one or more TPMI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, when the uplink shared channel message is associated with a single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the at least one maximum rank value associated with the uplink shared channel transmission from the UE is applicable. In some examples, when the uplink shared channel message is associated with the single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the threshold number of ports supported by the UE is applicable.

[0230] In some examples, when the uplink shared channel message is associated with a single uplink shared channel or more than one uplink shared channel that at least partially overlap in the time domain, the corresponding maximum rank value for each corresponding SRS resource set in the set of multiple SRS resource sets is applicable.

[0231] In some examples, each of the at least one maximum rank value is indicated by a control resource set index value, by an SRS resource set, by a DCI format, by a bandwidth part, or by a component carrier.

[0232] In some examples, to support receiving the one or more control messages indicating the at least one maximum rank value, the control message receiver 1025 may be configured to or otherwise support components for the following actions: when the uplink shared channel message is associated with a single uplink shared channel, receive an indication of a baseline maximum rank value applicable to any one or more of the sets of the multiple SRS resource sets. In some examples, to support receiving the one or more control messages indicating the at least one maximum rank value, the control message receiver 1025 may be configured to or otherwise support components for the following actions: receive an indication of a corresponding set of one or more maximum rank values ​​for each respective SRS resource set in the set of the multiple SRS resource sets, wherein the corresponding set of one or more maximum rank values ​​for each respective SRS resource set is applicable to the respective SRS resource set when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, and wherein the baseline maximum rank value is less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each respective SRS resource set in the set of the multiple SRS resource sets.

[0233] In some examples, where the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value. In some examples, where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set that is less than or equal to the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

[0234] In some examples, interpreting the one or more TPMI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0235] In some examples, in the case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRI fields each indicate a port number that is less than or equal to the maximum port number that the UE can support. In some examples, in the case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRI fields each indicate a port number that is less than or equal to a plurality of maximum port numbers of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum port number that the UE can support is equal to the sum of the plurality of maximum port numbers of each corresponding SRS resource set.

[0236] In some examples, the DCI includes a field including information indicating whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, the mapping is also indicated by whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0237] In some examples, where the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to the mapping between the content of the one or more TPMI fields and each of the number of ports associated with an SRS resource of the single uplink shared channel. In some examples, where the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to a first mapping between the content of the first TPMI field and a first subset of the first number of ports associated with a first SRS resource from a first SRS resource set and a second mapping between the content of the second TPMI field and a second subset of the second number of ports associated with a second SRS resource from a second SRS resource set.

[0238] In some examples, the first subset includes a first half of the number of the first ports associated with the first SRS resource. In some examples, the second subset includes a first half of the number of the second ports associated with the second SRS resource.

[0239] In some examples, to support receiving the one or more control messages, the control message receiver 1025 may be configured as or otherwise support components for receiving indications of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

[0240] In some examples, capability component 1045 may be configured as or otherwise support components for the following actions: when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, sending information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, the first subset and the second subset corresponding to the maximum number of ports that the UE can support for the first SRS resource and the second SRS resource.

[0241] In some examples, interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0242] In some examples, a size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE can support when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0243] In some examples, receiving the message including the DCI includes: receiving the message within a first control resource set associated with a first control resource set index value, receiving the message within a second control resource set associated with a second control resource set index value, or a combination thereof. In some examples, one or more SRS resource sets are indicated from the set of the multiple SRS resource sets by a combination of the fields in the DCI, the field indicating whether the uplink shared channel message is associated with the more than one uplink shared channel, and whether the message including the DCI is received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value. In some examples, interpreting the one or more SRI fields includes: selecting, based on the one or more SRI fields, the at least one SRS resource for sending the uplink shared channel message from the one or more SRS resource sets indicated by the set of the multiple SRS resource sets.

[0244] In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel and the message including the DCI is received within the first control resource set associated with the first control resource set index value, the first SRS resource set is indicated from the set of the multiple SRS resource sets. In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with the single uplink shared channel and the message including the DCI is received within the second control resource set associated with the second control resource set index value, the second SRS resource set is indicated from the set of the multiple SRS resource sets. In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channel and the message including the DCI is received within the first control resource set associated with the first control resource set index value, the third SRS resource set is indicated from the set of the multiple SRS resource sets. In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the DCI is received within the second control resource set associated with the first control resource set index value, the fourth SRS resource set is indicated from the set of the multiple SRS resource sets.

[0245] In some examples, the first set of SRS resources and the third set of SRS resources are associated with a first set of common power control parameters. In some examples, the second set of SRS resources and the fourth set of SRS resources are associated with a second set of common power control parameters.

[0246] In some examples, the number of first SRS resources in the first SRS resource set and the third SRS resource set is the same. In some examples, the number of second SRS resources in the second SRS resource set and the fourth SRS resource set is the same.

[0247] In some examples, a first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof. In some examples, a third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof.

[0248] In some examples, a first SRS resource having a first position in the third SRS resource set is associated with a smaller number of ports than a second SRS resource having the first position in the first SRS resource set. In some examples, a third SRS resource having a second position in the fourth SRS resource set is associated with a smaller number of ports than a fourth SRS resource having the second position in the second SRS resource set.

[0249] In some examples, in the case where the message including the DCI is received within the first set of control resources, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit that: indicates the first set of SRS resources when the uplink shared channel message is associated with the single uplink shared channel; and indicates the third set of SRS resources when the uplink shared channel message is associated with the more than one uplink shared channels. In some examples, in the case where the message including the DCI is received within the second set of control resources, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit that: indicates the second set of SRS resources when the uplink shared channel message is associated with the single uplink shared channel; and indicates the fourth set of SRS resources when the uplink shared channel message is associated with the more than one uplink shared channels.

[0250] In some examples, the interpretation of the one or more SRI fields is based on a combination of the fields in the DCI, which indicate whether the uplink shared channel message is associated with the more than one uplink shared channels, and whether the message including the DCI is received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value.

[0251] In some examples, interpreting the one or more TPMI fields is based on a port number associated with the selected at least one SRS resource for transmitting the uplink shared channel message.

[0252] In some examples, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit indicating: the uplink shared channel message is associated with a single uplink shared channel; or the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0253] Fig.11A diagram of a system 1100 including a device 1105 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein or include components thereof. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

[0254] I / O controller 1110 can manage input signals and output signals of device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor (such as processor 1140). In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

[0255] In some cases, the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bidirectionally via one or more antennas 1125, a wired or wireless link, as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. The transceiver 1115 or the transceiver 1115 and one or more antennas 1125 may be examples of transmitters 815, transmitters 915, receivers 810, receivers 910, or any combination thereof or components thereof as described herein.

[0256] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1130 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0257] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting SRI designs for CB-based communications). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to or to the processor 1140, the processor 1140 and the memory 1130 being configured to perform the various functions described herein.

[0258] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. For example, the communication manager 1120 may be configured to or otherwise support components for: receiving one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold number of rank values ​​supported by the UE. The communication manager 1120 may be configured to or otherwise support components for: receiving a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The communication manager 1120 may be configured to or otherwise support components for the following actions: interpreting one or more SRI fields and one or more TPMI fields based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource in a set from a plurality of SRS resource sets, the mapping being indicated by the number of at least one maximum rank value and the maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain). The communication manager 1120 may be configured to or otherwise support components for the following actions: sending an uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource in a set from a plurality of SRS resource sets.

[0259] By including or configuring a communication manager 1120 according to examples as described herein, a device 1105 can support techniques for more efficiently utilizing communication resources.

[0260] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions that are executable by the processor 1140 to cause the device 1105 to perform various aspects of the SRI design for CB-based communications as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0261] Fig.12 A block diagram 1200 of a device 1205 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0262] Receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1205. In some examples, receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0263] The transmitter 1215 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0264] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the SRI design for CB-based communications as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0265] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0266] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). Where implemented in code executed by a processor, the functionality of the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0267] In some examples, communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in conjunction with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0268] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support components for the following actions: sending one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. The communication manager 1220 may be configured to or otherwise support components for the following actions: sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The communication manager 1220 may be configured to or otherwise support components for receiving an uplink shared channel message based on a mapping between the contents of one or more TPMI fields and a number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by a number of at least one maximum rank values ​​and a maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain).

[0269] By including or configuring a communication manager 1220 according to examples as described herein, a device 1205 (e.g., a processor controlling or otherwise coupled to a receiver 1210, a transmitter 1215, a communication manager 1220, or a combination thereof) may support techniques for reduced power consumption.

[0270] Fig.13A block diagram 1300 of a device 1305 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0271] Receiver 1310 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0272] The transmitter 1315 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1305. For example, the transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1315 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1315 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0273] Device 1305 or its various components may be examples of components for performing various aspects of the SRI design for CB-based communications as described herein. For example, communication manager 1320 may include control message transmitter 1325, DCI transmitter 1330, PUSCH receiver 1335, or any combination thereof. Communication manager 1320 may be an example of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0274] According to examples as disclosed herein, the communication manager 1320 may support wireless communication at a network entity. The control message transmitter 1325 may be configured to or otherwise support components for the following actions: sending one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and the control message transmitter 1325 may be configured to or otherwise support components for the following actions: at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. The DCI transmitter 1330 may be configured to or otherwise support components for the following actions: sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The PUSCH receiver 1335 may be configured to or otherwise support components for receiving an uplink shared channel message based on a mapping between the contents of one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by the number of at least one maximum rank values, and the PUSCH receiver 1335 may be configured to or otherwise support components for the following actions: the maximum number of ports that the UE is capable of supporting (e.g., when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain).

[0275] Fig.14A block diagram 1400 of a communication manager 1420 supporting an SRI design for CB-based communication according to one or more aspects of the present disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of the SRI design for CB-based communication as described herein. For example, the communication manager 1420 may include a control message transmitter 1425, a DCI transmitter 1430, a PUSCH receiver 1435, a capability report receiver 1440, a configuration component 1445, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0276] According to examples as disclosed herein, the communication manager 1420 may support wireless communication at a network entity. The control message transmitter 1425 may be configured to or otherwise support components for the following actions: components for sending one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and the control message transmitter 1425 may be configured to or otherwise support components for the following actions: at least one maximum rank value associated with uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. The DCI transmitter 1430 may be configured to or otherwise support components for the following actions: sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The PUSCH receiver 1435 may be configured to or otherwise support components for receiving an uplink shared channel message based on a mapping between the contents of one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by the number of at least one maximum rank values, and the PUSCH receiver 1435 may be configured to or otherwise support components for the following actions: the maximum number of ports that the UE is capable of supporting (e.g., when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain).

[0277] In some examples, the capability report receiver 1440 may be configured to or otherwise support components for receiving information associated with a maximum number of ports that the UE is capable of supporting via a capability report when an uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message is associated with a single uplink shared channel, or both, wherein sending a message including a DCI is based on sending the information via the capability report.

[0278] In some examples, configuration component 1445 may be configured to or otherwise support components for the following actions: sending an indication of a configuration associated with the at least one maximum rank value, wherein the configuration is a first configuration or a second configuration. In some examples, configuration component 1445 may be configured to or otherwise support components for the following actions: a first configuration, the first configuration indicating that in the case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the larger of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource, and configuration component 1445 may be configured to or otherwise support components for the following actions: a second configuration, the second configuration indicating that in the case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

[0279] In some examples, the configuration is indicated per DCI format, per bandwidth part, or per component carrier.

[0280] In some examples, to support sending one or more control messages indicating at least one maximum rank value, the control message transmitter 1425 may be configured as or otherwise support components for sending an indication of a corresponding maximum rank value for each corresponding SRS resource set in a set of multiple SRS resource sets configured at the UE.

[0281] In some examples, interpreting the one or more TPMI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, when the uplink shared channel message is associated with a single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the at least one maximum rank value associated with the uplink shared channel transmission from the UE is applicable. In some examples, when the uplink shared channel message is associated with the single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the threshold number of ports supported by the UE is applicable.

[0282] In some examples, when the uplink shared channel message is associated with a single uplink shared channel or more than one uplink shared channel that at least partially overlap in the time domain, the corresponding maximum rank value for each corresponding SRS resource set in the set of multiple SRS resource sets is applicable.

[0283] In some examples, each of the at least one maximum rank value is indicated by a control resource set index value, by an SRS resource set, by a DCI format, by a bandwidth part, or by a component carrier.

[0284] In some examples, to support sending the one or more control messages indicating the at least one maximum rank value, the control message transmitter 1425 may be configured to or otherwise support components for the following actions: when the uplink shared channel message is associated with a single uplink shared channel, send an indication of a baseline maximum rank value that is applicable to any one or more of the sets of the multiple SRS resource sets. In some examples, to support sending the one or more control messages indicating the at least one maximum rank value, the control message transmitter 1425 may be configured to or otherwise support components for the following actions: send an indication of a corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set in the set of the multiple SRS resource sets, wherein when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set is applicable to the corresponding SRS resource set, and wherein the baseline maximum rank value is less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each corresponding SRS resource set in the set of the multiple SRS resource sets.

[0285] In some examples, where the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value. In some examples, where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set that is less than or equal to the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

[0286] In some examples, interpreting the one or more TPMI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0287] In some examples, in the case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRI fields each indicate a port number that is less than or equal to the maximum port number that the UE can support. In some examples, in the case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRI fields each indicate a port number that is less than or equal to a plurality of maximum port numbers of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum port number that the UE can support is equal to the sum of the plurality of maximum port numbers of each corresponding SRS resource set.

[0288] In some examples, the DCI includes a field including information indicating whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain. In some examples, the mapping is also indicated by whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0289] In some examples, where the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to the mapping between the content of the one or more TPMI fields and each of the number of ports associated with an SRS resource of the single uplink shared channel. In some examples, where the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to a first mapping between the content of the first TPMI field and a first subset of the first number of ports associated with a first SRS resource from a first SRS resource set and a second mapping between the content of the second TPMI field and a second subset of the second number of ports associated with a second SRS resource from a second SRS resource set.

[0290] In some examples, the first subset includes a first half of the number of the first ports associated with the first SRS resource. In some examples, the second subset includes a first half of the number of the second ports associated with the second SRS resource.

[0291] In some examples, to support sending the one or more control messages, the control message transmitter 1425 may be configured as or otherwise support components for sending indications of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

[0292] In some examples, the capability report receiver 1440 may be configured to or otherwise support components for the following actions: when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, receiving information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, the first subset and the second subset corresponding to the maximum number of ports that the UE can support for the first SRS resource and the second SRS resource.

[0293] In some examples, interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0294] In some examples, a size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE can support when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0295] In some examples, sending the message including the DCI includes: sending the message within a first control resource set associated with a first control resource set index value, sending the message within a second control resource set associated with a second control resource set index value, or a combination thereof. In some examples, one or more SRS resource sets are indicated from the set of the multiple SRS resource sets by a combination of the fields in the DCI, the field indicating whether the uplink shared channel message is associated with the more than one uplink shared channel, and whether the message including the DCI is sent within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value. In some examples, interpreting the one or more SRI fields includes: selecting, according to the one or more SRI fields, the at least one SRS resource for receiving the uplink shared channel message from the one or more SRS resource sets indicated by the set of the multiple SRS resource sets.

[0296] In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel and the message including the DCI is sent within the first control resource set associated with the first control resource set index value, the first SRS resource set is indicated from the set of multiple SRS resource sets. In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with the single uplink shared channel and the message including the DCI is sent within the second control resource set associated with the second control resource set index value, the second SRS resource set is indicated from the set of multiple SRS resource sets. In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channel and the message including the DCI is sent within the first control resource set associated with the first control resource set index value, the third SRS resource set is indicated from the set of multiple SRS resource sets. In some examples, when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the DCI is sent within the second control resource set associated with the first control resource set index value, the fourth SRS resource set is indicated from the set of the multiple SRS resource sets.

[0297] In some examples, the first set of SRS resources and the third set of SRS resources are associated with a first set of common power control parameters. In some examples, the second set of SRS resources and the fourth set of SRS resources are associated with a second set of common power control parameters.

[0298] In some examples, the number of first SRS resources in the first SRS resource set and the third SRS resource set is the same. In some examples, the number of second SRS resources in the second SRS resource set and the fourth SRS resource set is the same.

[0299] In some examples, a first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof. In some examples, a third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof.

[0300] In some examples, a first SRS resource having a first position in the third SRS resource set is associated with a smaller number of ports than a second SRS resource having the first position in the first SRS resource set. In some examples, a third SRS resource having a second position in the fourth SRS resource set is associated with a smaller number of ports than a fourth SRS resource having the second position in the second SRS resource set.

[0301] In some examples, in the case where the message including the DCI is sent within the first set of control resources, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit that: indicates the first set of SRS resources when the uplink shared channel message is associated with the single uplink shared channel; and indicates the third set of SRS resources when the uplink shared channel message is associated with the more than one uplink shared channels. In some examples, in the case where the message including the DCI is sent within the second set of control resources, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit that: indicates the second set of SRS resources when the uplink shared channel message is associated with the single uplink shared channel; and indicates the fourth set of SRS resources when the uplink shared channel message is associated with the more than one uplink shared channels.

[0302] In some examples, the interpretation of the one or more SRI fields is based on a combination of the fields in the DCI, which indicate whether the uplink shared channel message is associated with the more than one uplink shared channels, and whether the message including the DCI is sent within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value.

[0303] In some examples, interpreting the one or more TPMI fields is based on a port number associated with the selected at least one SRS resource for receiving the uplink shared channel message.

[0304] In some examples, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit indicating: the uplink shared channel message is associated with a single uplink shared channel; or the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0305] Fig.15 A diagram of a system 1500 including a device 1505 supporting an SRI design for CB-based communications according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of a device 1205, a device 1305, or a network entity 105 as described herein, or include components thereof. The device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1505 may include components that support output and acquisition of communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, a code 1530, and a processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1540).

[0306] The transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving a modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating a signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1515 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured to be coupled to one or more processors or memory components that are operable to perform the following operations: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processors or memory components (e.g., processor 1535, or memory 1525, or both) may be included in a chip or chip component installed in the device 1505. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0307] Memory 1525 may include RAM and ROM. Memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by processor 1535, cause device 1505 to perform various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by processor 1535, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1525 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0308] Processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1535. Processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to cause device 1505 to perform various functions (e.g., functions or tasks supporting SRI designs for CB-based communications). For example, device 1505 or a component of device 1505 may include processor 1535 and memory 1525 coupled to processor 1535, the processor 1535 and memory 1525 being configured to perform the various functions described herein. Processor 1535 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that can host functions for performing functions of device 1505 (e.g., by executing code 1530). Processor 1535 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as in memory 1525). In some specific implementations, processor 1535 can be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which can be passed to other systems or components of device 1505, for example). For example, a processing system of device 1505 can refer to a system including various other components or subcomponents of device 1505, such as processor 1535, or transceiver 1510, or communication manager 1520, or other components or combinations of components of device 1505. The processing system of device 1505 may interface with other components of device 1505, and may process information (such as input or signal) received from other components, or output information to other components. For example, a chip or modem of device 1505 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1505 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1505 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0309] In some examples, bus 1540 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1540 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1505, or communications performed between different components of device 1505 that may be co-located or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one component or divided between different components).

[0310] In some examples, communication manager 1520 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1520 may manage delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1520 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1520 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0311] According to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. For example, the communication manager 1520 may be configured to or otherwise support components for the following actions: sending one or more control messages, the one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being based on a threshold rank value number supported by the UE. The communication manager 1520 may be configured to or otherwise support components for the following actions: sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The communication manager 1520 may be configured to or otherwise support components for receiving an uplink shared channel message based on a mapping between the contents of one or more TPMI fields and a number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by a number of at least one maximum rank values ​​and a maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlap in the time domain).

[0312] By including or configuring a communication manager 1520 according to examples as described herein, the device 1505 can support techniques for more efficiently utilizing communication resources and improving coordination.

[0313] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof. For example, the code 1530 may include instructions that are executable by the processor 1535 to cause the device 1505 to perform various aspects of the SRI design for CB-based communications as described herein, or the processor 1535 and the memory 1525 may be otherwise configured to perform or support such operations.

[0314] Fig.16A flowchart illustrating a method 1600 for supporting an SRI design for CB-based communication according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 11 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0315] At 1605, the method may include receiving one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with uplink shared channel transmissions from the UE, the at least one maximum rank value based on a threshold number of rank values ​​supported by the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by reference to Fig.10 The control message receiver 1025 is used to execute.

[0316] At 1610, the method may include receiving a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.10 The DCI receiver 1030 described above is performed.

[0317] At 1615, the method may include interpreting one or more SRI fields and one or more TPMI fields according to a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by the number of at least one maximum rank value and the maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain). The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.10 The interpretation component 1035 is used to execute.

[0318] At 1620, the method may include sending an uplink shared channel message based on a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.10 The PUSCH transmitter 1040 is used to perform the above operation.

[0319] Fig.17 A flowchart illustrating a method 1700 for supporting SRI design for CB-based communication according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 7 as well as Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0320] At 1705, the method may include sending one or more control messages indicating: a set number of multiple SRS resource sets, a number of one or more SRI fields included in the one or more control messages, and a number of one or more TPMI fields included in the one or more control messages, wherein the set of multiple SRS resource sets is configured for CB use; and at least one maximum rank value associated with uplink shared channel transmissions from the UE, the at least one maximum rank value based on a threshold number of rank values ​​supported by the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by reference to Fig.14 The described control message sender 1425 is executed.

[0321] At 1710, the method may include sending a message including a DCI scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.14 The DCI transmitter 1430 is used to perform the above operation.

[0322] At 1715, the method may include receiving an uplink shared channel message according to a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from a set of multiple SRS resource sets, the mapping being indicated by the number of at least one maximum rank value and the maximum number of ports that the UE can support (e.g., when the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain). The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.14 The PUSCH receiver 1435 performs the above operations.

[0323] The following provides an overview of various aspects of the disclosure:

[0324] Aspect 1: A method for wireless communication by a UE, the method comprising: receiving one or more control messages, the one or more control messages indicating: the number of multiple SRS resource sets, the number of one or more SRI fields included in the one or more control messages, and the number of one or more TPMI fields included in the one or more control messages, wherein the multiple SRS resource sets are configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from the UE, the at least one maximum rank value being at least partially based on the number of threshold rank values ​​supported by the UE; receiving a message including a DCI for scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; interpreting the one or more SRI fields and the one or more TPMI fields according to a mapping between the content of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the multiple SRS resource sets, the mapping being indicated by the following items: the number of the at least one maximum rank value, and the maximum number of ports that the UE can support; and sending the uplink shared channel message according to the mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource from the multiple SRS resource sets.

[0325] Aspect 2: According to the method according to Aspect 1, the method also includes: when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message is associated with a single uplink shared channel, or both, sending information associated with the maximum number of ports that the UE can support via a capability report, wherein receiving the message including the DCI is at least partially based on sending the information via the capability report.

[0326] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: receiving an indication of a configuration associated with the at least one maximum rank value, wherein the configuration is a first configuration or a second configuration, and wherein: the first configuration indicates: when the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the larger of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource, and the second configuration indicates: when the uplink shared channel message is associated with the single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

[0327] Aspect 4: The method according to aspect 3, wherein the configuration is indicated according to a DCI format, according to a bandwidth part, or according to a component carrier.

[0328] Aspect 5: A method according to any one of Aspects 1 to 4, wherein receiving the one or more control messages indicating the at least one maximum rank value also includes: receiving an indication of the corresponding maximum rank value of each corresponding SRS resource set in the multiple SRS resource sets configured at the UE.

[0329] Aspect 6: A method according to Aspect 5, wherein the interpretation of the one or more TPMI fields is independent of whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain; the interpretation of the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; when the uplink shared channel message is associated with a single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the at least one maximum rank value associated with the uplink shared channel transmission from the UE is applicable; and when the uplink shared channel message is associated with the single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the threshold number of ports supported by the UE is applicable.

[0330] Aspect 7: A method according to any one of Aspects 5 to 6, wherein when the uplink shared channel message is associated with a single uplink shared channel or more than one uplink shared channel that at least partially overlap in the time domain, the corresponding maximum rank value of each corresponding SRS resource set in the multiple SRS resource sets is applicable.

[0331] Aspect 8: A method according to any one of Aspects 1 to 7, wherein each of the at least one maximum rank value is indicated according to a control resource set index value, according to an SRS resource set, according to a DCI format, according to a bandwidth part, or according to a component carrier.

[0332] Aspect 9: A method according to any one of Aspects 1 to 8, wherein receiving the one or more control messages indicating the at least one maximum rank value further includes: when the uplink shared channel message is associated with a single uplink shared channel, receiving an indication of a baseline maximum rank value applicable to any one or more SRS resource sets in the multiple SRS resource sets; and receiving an indication of a corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set in the multiple SRS resource sets, wherein when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, the corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set is applicable to the corresponding SRS resource set, and wherein the baseline maximum rank value is less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each corresponding SRS resource set in the multiple SRS resource sets.

[0333] Aspect 10: A method according to Aspect 9, wherein, when the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value; and when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set of the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

[0334] Aspect 11: A method according to any one of Aspects 9 to 10, wherein the interpretation of the one or more TPMI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; the interpretation of the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; in the case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRI fields each indicate a port number that is less than or equal to the maximum port number that the UE can support; and in the case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRI fields each indicate a port number that is less than or equal to a plurality of maximum port numbers of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum port number that the UE can support is equal to the sum of the plurality of maximum port numbers of each corresponding SRS resource set.

[0335] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the DCI includes a field, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain; and the mapping is also indicated by whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0336] Aspect 13: A method according to Aspect 12, wherein, when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to the mapping between the content of the one or more TPMI fields and each of the port numbers associated with an SRS resource of the single uplink shared channel; and when the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to a first mapping between the content of the first TPMI field and a first subset of the first port numbers associated with a first SRS resource from a first SRS resource set and a second mapping between the content of the second TPMI field and a second subset of the second port numbers associated with a second SRS resource from a second SRS resource set.

[0337] Aspect 14: The method according to aspect 13, wherein the first subset includes a first half of the number of the first ports associated with the first SRS resource; and the second subset includes a first half of the number of the second ports associated with the second SRS resource.

[0338] Aspect 15: A method according to any one of Aspects 13 to 14, wherein receiving the one or more control messages further comprises: receiving an indication of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

[0339] Aspect 16: According to the method described in any one of Aspects 13 to 15, the method further includes: when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, sending information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, the first subset and the second subset corresponding to the maximum number of ports that the UE can support for the first SRS resource and the second SRS resource.

[0340] Aspect 17: A method according to any one of Aspects 13 to 16, wherein the interpretation of the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

[0341] Aspect 18: A method according to any one of Aspects 12 to 17, wherein the size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE can support when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0342] Aspect 19: A method according to any one of Aspects 12 to 18, wherein receiving the message including the DCI includes: receiving the message within a first control resource set associated with a first control resource set index value, receiving the message within a second control resource set associated with a second control resource set index value, or a combination thereof; one or more SRS resource sets are indicated from the multiple SRS resource sets by a combination of the fields in the DCI, the fields indicating whether the uplink shared channel message is associated with the more than one uplink shared channels, and whether the message including the DCI is received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and interpreting the one or more SRI fields includes: selecting, according to the one or more SRI fields, the at least one SRS resource for sending the uplink shared channel message from the one or more SRS resource sets indicated in the multiple SRS resource sets.

[0343] Aspect 20: A method according to aspect 19, wherein when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel and the message including the DCI is received within the first control resource set associated with the first control resource set index value, the first SRS resource set is indicated from the multiple SRS resource sets; when the field in the DCI indicates that the uplink shared channel message is associated with the single uplink shared channel and the message including the DCI is received within the second control resource set associated with the second control resource set index value, the second SRS resource set is indicated from the multiple SRS resource sets when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the DCI is received within the first control resource set associated with the first control resource set index value, a third SRS resource set is indicated from the multiple SRS resource sets; and when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the DCI is received within the second control resource set associated with the first control resource set index value, a fourth SRS resource set is indicated from the multiple SRS resource sets.

[0344] Aspect 21: A method according to Aspect 20, wherein the first SRS resource set and the third SRS resource set are associated with a first common power control parameter set; the second SRS resource set and the fourth SRS resource set are associated with a second common power control parameter set; the number of first SRS resources in the first SRS resource set and the third SRS resource set is the same; and the number of second SRS resources in the second SRS resource set and the fourth SRS resource set is the same.

[0345] Aspect 22: A method according to any one of Aspects 20 to 21, wherein a first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; a third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; the first SRS resource having a first position in the third SRS resource set is associated with a smaller number of ports than the second SRS resource having the first position in the first SRS resource set; and the third SRS resource having a second position within the fourth SRS resource set is associated with a smaller number of ports than the fourth SRS resource having the second position within the second SRS resource set.

[0346] Aspect 23: A method according to any one of Aspects 20 to 22, wherein, in a case where the message including the DCI is received within the first control resource set, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit, and the bit: indicates the first SRS resource set when the uplink shared channel message is associated with the single uplink shared channel, or indicates the third SRS resource set when the uplink shared channel message is associated with the more than one uplink shared channels; and in a case where the message including the DCI is received within the second control resource set, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit, and the bit: indicates the second SRS resource set when the uplink shared channel message is associated with the single uplink shared channel, or indicates the fourth SRS resource set when the uplink shared channel message is associated with the more than one uplink shared channels.

[0347] Aspect 24: A method according to any one of Aspects 19 to 23, wherein the interpretation of the one or more SRI fields is at least partially based on a combination of the fields in the DCI, the fields indicating whether the uplink shared channel message is associated with the more than one uplink shared channels, and whether the message including the DCI is received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and the interpretation of the one or more TPMI fields is at least partially based on the number of ports associated with the at least one SRS resource selected for sending the uplink shared channel message.

[0348] Aspect 25: A method according to any one of Aspects 12 to 24, wherein the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit, and the one bit indicates: the uplink shared channel message is associated with a single uplink shared channel; or the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0349] Aspect 26: A method for wireless communication by a network entity, the method comprising: sending one or more control messages, the one or more control messages indicating: the number of multiple SRS resource sets, the number of one or more SRI fields included in the one or more control messages, and the number of one or more TPMI fields included in the one or more control messages, wherein the multiple SRS resource sets are configured for CB use; and at least one maximum rank value associated with an uplink shared channel transmission from a UE, the at least one maximum rank value being at least partially based on a threshold number of rank values ​​supported by the UE; sending a message including a DCI for scheduling an uplink shared channel message, the DCI including one or more SRI fields and one or more TPMI fields; and receiving the uplink shared channel message based on a mapping between the contents of the one or more TPMI fields and the number of ports associated with at least one SRS resource from the multiple SRS resource sets, the mapping being indicated by: the number of the at least one maximum rank value, and the maximum number of ports that the UE can support.

[0350] Aspect 27: According to the method of Aspect 26, the method also includes: when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message is associated with a single uplink shared channel, or both, receiving information associated with the maximum number of ports that the UE can support via a capability report, wherein sending the message including the DCI is at least partially based on sending the information via the capability report.

[0351] Aspect 28: The method according to any one of Aspects 26 to 27 further includes: sending an indication of a configuration associated with the at least one maximum rank value, wherein the configuration is a first configuration or a second configuration, and wherein: the first configuration indicates: when the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the larger of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource, and the second configuration indicates: when the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

[0352] Aspect 29: The method according to aspect 28, wherein the configuration is indicated per DCI format, per bandwidth part, or per component carrier.

[0353] Aspect 30: A method according to any one of Aspects 26 to 29, wherein sending the one or more control messages indicating the at least one maximum rank value also includes: sending an indication of the corresponding maximum rank value for each corresponding SRS resource set in the multiple SRS resource sets configured at the UE.

[0354] Aspect 31: A method according to Aspect 30, wherein the interpretation of the one or more TPMI fields is independent of whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain; the interpretation of the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; when the uplink shared channel message is associated with a single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the at least one maximum rank value associated with the uplink shared channel transmission from the UE is applicable; and when the uplink shared channel message is associated with the single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, the threshold number of ports supported by the UE is applicable.

[0355] Aspect 32: A method according to any one of Aspects 30 to 31, wherein when the uplink shared channel message is associated with a single uplink shared channel or more than one uplink shared channel that at least partially overlap in the time domain, the corresponding maximum rank value of each corresponding SRS resource set in the multiple SRS resource sets is applicable.

[0356] Aspect 33: A method according to any one of Aspects 26 to 32, wherein each of the at least one maximum rank value is indicated according to a control resource set index value, according to an SRS resource set, according to a DCI format, according to a bandwidth part, or according to a component carrier.

[0357] Aspect 34: A method according to any one of Aspects 26 to 33, wherein sending the one or more control messages indicating the at least one maximum rank value further includes: when the uplink shared channel message is associated with a single uplink shared channel, sending an indication of a baseline maximum rank value applicable to any one or more SRS resource sets in the multiple SRS resource sets; and sending an indication of a corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set in the multiple SRS resource sets, wherein when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, the corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set is applicable to the corresponding SRS resource set, and wherein the baseline maximum rank value is less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each corresponding SRS resource set in the multiple SRS resource sets.

[0358] Aspect 35: A method according to Aspect 34, wherein, in a case where the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value; and in a case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set of the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

[0359] Aspect 36: A method according to any one of Aspects 34 to 35, wherein the interpretation of the one or more TPMI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; the interpretation of the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; in the case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRI fields each indicate a port number that is less than or equal to the maximum port number that the UE can support; and in the case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRI fields each indicate a port number that is less than or equal to a plurality of maximum port numbers of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum port number that the UE can support is equal to the sum of the plurality of maximum port numbers of each corresponding SRS resource set.

[0360] Aspect 37: A method according to any one of Aspects 26 to 36, wherein the DCI includes a field, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain; and the mapping is also indicated by whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0361] Aspect 38: A method according to Aspect 37, wherein, when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to the mapping between the content of the one or more TPMI fields and each of the port numbers associated with an SRS resource of the single uplink shared channel; and when the field in the DCI indicates that the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes: interpreting the one or more TPMI fields according to a first mapping between the content of the first TPMI field and a first subset of the first port numbers associated with a first SRS resource from a first SRS resource set and a second mapping between the content of the second TPMI field and a second subset of the second port numbers associated with a second SRS resource from a second SRS resource set.

[0362] Aspect 39: The method according to aspect 38, wherein the first subset includes a first half of the number of the first ports associated with the first SRS resource; and the second subset includes a first half of the number of the second ports associated with the second SRS resource.

[0363] Aspect 40: A method according to any one of Aspects 38 to 39, wherein sending the one or more control messages further comprises sending an indication of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

[0364] Aspect 41: According to the method described in any one of Aspects 38 to 40, the method further includes: when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, receiving information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, the first subset and the second subset corresponding to the maximum number of ports that the UE can support for the first SRS resource and the second SRS resource.

[0365] Aspect 42: A method according to any one of aspects 38 to 41, wherein the interpreting the one or more SRI fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain;

[0366] Aspect 43: A method according to any one of Aspects 37 to 42, wherein the size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE can support when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0367] Aspect 44: A method according to any one of Aspects 37 to 43, wherein sending the message including the DCI includes: sending the message within a first control resource set associated with a first control resource set index value, sending the message within a second control resource set associated with a second control resource set index value, or a combination thereof; one or more SRS resource sets are indicated from the multiple SRS resource sets by a combination of the fields in the DCI, the fields indicating whether the uplink shared channel message is associated with the more than one uplink shared channels, and whether the message including the DCI is sent within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and interpreting the one or more SRI fields includes: selecting, according to the one or more SRI fields, the at least one SRS resource for receiving the uplink shared channel message from the one or more SRS resource sets indicated in the multiple SRS resource sets.

[0368] Aspect 45: A method according to aspect 44, wherein when the field in the DCI indicates that the uplink shared channel message is associated with a single uplink shared channel and the message including the DCI is sent within the first control resource set associated with the first control resource set index value, the first SRS resource set is indicated from the multiple SRS resource sets; when the field in the DCI indicates that the uplink shared channel message is associated with the single uplink shared channel and the message including the DCI is sent within the second control resource set associated with the second control resource set index value, the second SRS resource set is indicated from the multiple SRS resource sets when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the DCI is sent within the first control resource set associated with the first control resource set index value, a third SRS resource set is indicated from the multiple SRS resource sets; and when the field in the DCI indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the DCI is sent within the second control resource set associated with the first control resource set index value, a fourth SRS resource set is indicated from the multiple SRS resource sets.

[0369] Aspect 46: A method according to Aspect 45, wherein the first SRS resource set and the third SRS resource set are associated with a first common power control parameter set; the second SRS resource set and the fourth SRS resource set are associated with a second common power control parameter set; the number of first SRS resources in the first SRS resource set and the third SRS resource set is the same; and the number of second SRS resources in the second SRS resource set and the fourth SRS resource set is the same.

[0370] Aspect 47: A method according to any one of Aspects 45 to 46, wherein a first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; and a third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with the same beam, the same TCI state, the same spatial relationship information, or a combination thereof; the first SRS resource having a first position in the third SRS resource set is associated with a smaller number of ports than the second SRS resource having the first position in the first SRS resource set; and the third SRS resource having a second position within the fourth SRS resource set is associated with a smaller number of ports than the fourth SRS resource having the second position within the second SRS resource set.

[0371] Aspect 48: A method according to any one of Aspects 45 to 47, wherein, in the case where the message including the DCI is sent within the first control resource set, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit, and the bit: indicates the first SRS resource set when the uplink shared channel message is associated with the single uplink shared channel, or indicates the third SRS resource set when the uplink shared channel message is associated with the more than one uplink shared channels; and in the case where the message including the DCI is sent within the second control resource set, the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit, and the bit: indicates the second SRS resource set when the uplink shared channel message is associated with the single uplink shared channel, or indicates the fourth SRS resource set when the uplink shared channel message is associated with the more than one uplink shared channels.

[0372] Aspect 49: A method according to any one of Aspects 44 to 48, wherein the interpretation of the one or more SRI fields is based at least in part on a combination of the fields in the DCI, the fields indicating whether the uplink shared channel message is associated with the more than one uplink shared channels, and whether the message including the DCI is sent within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and the interpretation of the one or more TPMI fields is based at least in part on the number of ports associated with the selected at least one SRS resource for receiving the uplink shared channel message.

[0373] Aspect 50: A method according to any one of Aspects 37 to 49, wherein the field including information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain includes a bit, and the one bit indicates: the uplink shared channel message is associated with a single uplink shared channel; or the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

[0374] Aspect 51: A UE for wireless communication, the UE comprising one or more memories and one or more processors coupled to the one or more memories, and the one or more memories and the one or more processors are individually or collectively configured to perform a method according to any one of Aspects 1 to 25.

[0375] Aspect 52: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 25.

[0376] Aspect 53: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 25.

[0377] Aspect 54: A network entity for wireless communication, the UE comprising one or more memories and one or more processors coupled to the one or more memories, and the one or more memories and the one or more processors are individually or collectively configured to perform a method according to any one of Aspects 26 to 50.

[0378] Aspect 55: A network entity for wireless communication, the network node comprising at least one component for performing a method according to any one of aspects 26 to 50.

[0379] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method according to any one of aspects 26 to 50.

[0380] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0381] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0382] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0383] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0384] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. In the case of software implementation executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0385] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, in the case where software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0386] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0387] As used herein, including in the claims, the article "a" before a noun is open ended and is understood to mean "at least one" of those nouns or "one or more" of those nouns. Thus, the terms "a", "at least one", "one or more", "atleast one of one or more" are interchangeable. For example, where a claim lists a "component" that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term "component" having a characteristic or performing a function may refer to "at least one of one or more components" having a particular characteristic or performing a particular function. Subsequent references to components introduced using the term "the" or "said" together with the article "a" may refer to any or all of the one or more components. For example, a component introduced with the article "a" may be understood to mean "one or more components", and a subsequent reference in a claim to "the component" may be understood to be equivalent to a reference to "at least one of the one or more components". Similarly, subsequent reference to a component introduced as "one or more components" using the term "the" or "said" may refer to any or all of the one or more components. For example, subsequent reference to "the one or more components" in a claim may be understood to be equivalent to reference to "at least one of the one or more components."

[0388] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0389] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. Where only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0390] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0391] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories; and one or more processors coupled to the one or more memories and individually or collectively configured to: Receiving one or more control messages indicating: a number of a plurality of sounding reference signal (SRS) resource sets, a number of one or more SRS resource indicator fields included in one or more control messages, and a number of one or more transmit precoding matrix indicator (TPMI) fields included in the one or more control messages, wherein the plurality of SRS resource sets are configured for codebook use, and at least one maximum rank value associated with uplink shared channel transmissions from the UE, the at least one maximum rank value based at least in part on a threshold number of rank values ​​supported by the UE; receiving a message including downlink control information for scheduling an uplink shared channel message, the downlink control information including one or more SRS resource indicator fields and one or more TPMI fields; interpreting the one or more SRS resource indicator fields and the one or more TPMI fields according to a mapping between contents of the one or more TPMI fields and a number of ports associated with at least one SRS resource from the plurality of SRS resource sets, the mapping being indicated by: the number of the at least one maximum rank values, and The maximum number of ports that the UE can support; and The uplink shared channel message is transmitted according to the mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource from the plurality of SRS resource sets.

2. The UE of claim 1 , wherein the one or more processors are further configured, individually or collectively, to: send information associated with the maximum number of ports that the UE can support via a capability report when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message is associated with a single uplink shared channel, or both, wherein receiving the message including the downlink control information is at least partially based on sending the information via the capability report.

3. The UE of claim 1 , wherein the one or more processors are individually or collectively further configured to: receiving an indication of a configuration associated with the at least one maximum rank value, wherein the configuration is a first configuration or a second configuration, and wherein: The first configuration indicates that, in a case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the larger of a first maximum number of ports of a first SRS resource and a second maximum number of ports of a second SRS resource, and The second configuration indicates that: when the uplink shared channel message is associated with the single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

4. The UE according to claim 3, wherein: The configuration is indicated according to a downlink control information format, according to a bandwidth part or according to a component carrier.

5. A UE according to claim 1, wherein in order to receive the one or more control messages indicating the at least one maximum rank value, the one or more processors are further configured individually or collectively to receive an indication of the corresponding maximum rank value of each corresponding SRS resource set in the multiple SRS resource sets configured at the UE.

6. The UE according to claim 5, wherein: interpreting the one or more TPMI fields as being independent of whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain; interpreting the one or more SRS resource indicator fields as being independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; The at least one maximum rank value associated with an uplink shared channel transmission from the UE is applicable when the uplink shared channel message is associated with a single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain; and When the uplink shared channel message is associated with the single uplink shared channel or the more than one uplink shared channels that at least partially overlap in the time domain, a threshold number of ports supported by the UE is applicable.

7. The UE of claim 5, wherein the corresponding maximum rank value of each corresponding SRS resource set in the multiple SRS resource sets is applicable when the uplink shared channel message is associated with a single uplink shared channel or more than one uplink shared channels that at least partially overlap in the time domain.

8. The UE according to claim 1, wherein: Each maximum rank value of the at least one maximum rank value is indicated per control resource set index value, per SRS resource set, per downlink control information format, per bandwidth part or per component carrier.

9. The UE of claim 1 , wherein to receive the one or more control messages indicating the at least one maximum rank value, the one or more processors are further configured, individually or collectively, to: When the uplink shared channel message is associated with a single uplink shared channel, receiving an indication of a baseline maximum rank value applicable to any one or more of the plurality of SRS resource sets; and Receive an indication of a corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set in the multiple SRS resource sets, wherein the corresponding set of one or more maximum rank values ​​for each corresponding SRS resource set is applicable to the corresponding SRS resource set when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, and wherein the baseline maximum rank value is less than or equal to the sum of the corresponding sets of one or more maximum rank values ​​for each corresponding SRS resource set in the multiple SRS resource sets.

10. The UE according to claim 9, wherein: In a case where the uplink shared channel message is associated with the single uplink shared channel, the one or more TPMI fields each indicate a rank value that is less than or equal to the baseline maximum rank value; and In a case where the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, the one or more TPMI fields each indicate a rank value of a corresponding set that is less than or equal to the one or more maximum rank values ​​of each corresponding SRS resource set of the more than one uplink shared channels that at least partially overlap in the time domain.

11. The UE according to claim 9, wherein: interpreting the one or more TPMI fields as being independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; interpreting the one or more SRS resource indicator fields as being independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain; In a case where the uplink shared channel message is associated with the single uplink shared channel, the one or more SRS resource indicator fields each indicate a number of ports that is less than or equal to the maximum number of ports that the UE can support; and In a case where the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, the one or more SRS resource indicator fields each indicate a port number that is less than or equal to a plurality of maximum port numbers of each corresponding SRS resource set of the more than one uplink shared channels, wherein the maximum port number that the UE can support is equal to the sum of the plurality of maximum port numbers of each corresponding SRS resource set.

12. The UE according to claim 1, wherein: The downlink control information includes a field containing information indicating whether the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain; and The mapping is further indicated by whether the uplink shared channel message is associated with the more than one uplink shared channels at least partially overlapping in the time domain.

13. The UE according to claim 12, wherein: In a case where the field in the downlink control information indicates that the uplink shared channel message is associated with a single uplink shared channel, interpreting the one or more TPMI fields comprises: interpreting the one or more TPMI fields according to the mapping between the content of the one or more TPMI fields and each of the port numbers associated with one SRS resource of the single uplink shared channel; and In a case where the field in the downlink control information indicates that the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, interpreting the one or more TPMI fields includes interpreting the one or more TPMI fields based on a first mapping between the content of the first TPMI field and a first subset of the first number of ports associated with a first SRS resource from a first SRS resource set, and a second mapping between the content of the second TPMI field and a second subset of the second number of ports associated with a second SRS resource from a second SRS resource set.

14. The UE according to claim 13, wherein: The first subset includes a first half of the first number of ports associated with the first SRS resource; and The second subset includes a first half of the second number of ports associated with the second SRS resource.

15. The UE of claim 13, wherein in order to receive the one or more control messages, the one or more processors are further configured, individually or collectively, to receive an indication of the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource.

16. A UE according to claim 13, wherein the one or more processors are further configured, individually or collectively, to: when the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain, send information indicating the first subset of the first number of ports associated with the first SRS resource and the second subset of the second number of ports associated with the second SRS resource via a capability report, the first subset and the second subset corresponding to the maximum number of ports that the UE can support for the first SRS resource and the second SRS resource.

17. The UE of claim 13, wherein interpreting the one or more SRS resource indicator fields is independent of whether the uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

18. The UE of claim 12, wherein a size of each of the one or more TPMI fields corresponds to the maximum number of ports that the UE can support when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain.

19. The UE according to claim 12, wherein: Receiving the message including the downlink control information comprises: receiving the message within a first set of control resources associated with a first set of control resources index value, receiving the message within a second set of control resources associated with a second set of control resources index value, or a combination thereof; one or more SRS resource sets are indicated from the plurality of SRS resource sets by a combination of the fields in the downlink control information, the fields indicating whether the uplink shared channel message is associated with the more than one uplink shared channels and whether the message including the downlink control information is received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and Interpreting the one or more SRS resource indicator fields includes: selecting the at least one SRS resource for sending the uplink shared channel message from the one or more SRS resource sets indicated by the multiple SRS resource sets according to the one or more SRS resource indicator fields.

20. The UE according to claim 19, wherein: when the field in the downlink control information indicates that the uplink shared channel message is associated with a single uplink shared channel and the message including the downlink control information is received within the first control resource set associated with the first control resource set index value, the first SRS resource set is indicated from the plurality of SRS resource sets; when the field in the downlink control information indicates that the uplink shared channel message is associated with the single uplink shared channel and the message including the downlink control information is received within the second control resource set associated with the second control resource set index value, the second SRS resource set is indicated from the plurality of SRS resource sets; when the field in the downlink control information indicates that the uplink shared channel message is associated with the more than one uplink shared channels and the message including the downlink control information is received within the first control resource set associated with the first control resource set index value, a third SRS resource set is indicated from the plurality of SRS resource sets; and When the field in the downlink control information indicates that the uplink shared channel message is associated with more than one uplink shared channels and the message including the downlink control information is received within the second control resource set associated with the first control resource set index value, a fourth SRS resource set is indicated from the multiple SRS resource sets.

21. The UE according to claim 20, wherein: The first SRS resource set and the third SRS resource set are associated with a first common power control parameter set; The second SRS resource set and the fourth SRS resource set are associated with a second common power control parameter set; The number of first SRS resources in the first SRS resource set and the number of first SRS resources in the third SRS resource set are the same; and The number of second SRS resources in the second SRS resource set and the fourth SRS resource set is the same.

22. The UE according to claim 20, wherein: A first SRS resource having a first position within the first SRS resource set and a second SRS resource having the first position within the third SRS resource set are associated with a same beam, a same transmission configuration indicator state, a same spatial relationship information, or a combination thereof; A third SRS resource having a second position within the second SRS resource set and a fourth SRS resource having the second position within the fourth SRS resource set are associated with a same beam, a same transmission configuration indicator state, a same spatial relationship information, or a combination thereof; the first SRS resource having the first position in the third set of SRS resources is associated with a smaller number of ports than the second SRS resource having the first position in the first set of SRS resources; and The third SRS resource having the second position within the fourth set of SRS resources is associated with a smaller number of ports than the fourth SRS resource having the second position within the second set of SRS resources.

23. The UE according to claim 20, wherein: In case the message comprising the downlink control information is received within the first set of control resources, the field comprising information indicating whether the uplink shared channel message is associated with more than one uplink shared channel at least partially overlapping in the time domain comprises one bit, the one bit: In case the uplink shared channel message is associated with the single uplink shared channel, indicating the first SRS resource set, or In case the uplink shared channel message is associated with the more than one uplink shared channels, indicating the third SRS resource set; and In case the message comprising the downlink control information is received within the second set of control resources, the field comprising information indicating whether the uplink shared channel message is associated with more than one uplink shared channel at least partially overlapping in the time domain comprises one bit, the one bit: In case the uplink shared channel message is associated with the single uplink shared channel, indicating the second SRS resource set, or In case the uplink shared channel message is associated with the more than one uplink shared channels, the fourth SRS resource set is indicated.

24. The UE according to claim 19, wherein: interpreting the one or more SRS resource indicator fields based at least in part on a combination of the fields in the downlink control information, the fields indicating whether the uplink shared channel message is associated with the more than one uplink shared channels and whether the message including the downlink control information is received within the first control resource set associated with the first control resource set index value or within the second control resource set associated with the second control resource set index value; and Interpreting the one or more TPMI fields is based at least in part on a port number associated with the selected at least one SRS resource for transmitting the uplink shared channel message.

25. The UE of claim 12, wherein the field comprising information indicating whether the uplink shared channel message is associated with more than one uplink shared channel that at least partially overlaps in the time domain comprises one bit indicating: The uplink shared channel message is associated with a single uplink shared channel; or The uplink shared channel message is associated with the more than one uplink shared channels that at least partially overlap in the time domain.

26. A network entity for wireless communication, the network entity comprising: one or more memories; and one or more processors coupled to the one or more memories and individually or collectively configured to: Send one or more control messages indicating: a number of a plurality of sounding reference signal (SRS) resource sets, a number of one or more SRS resource indicator fields included in one or more control messages, and a number of one or more transmit precoding matrix indicator (TPMI) fields included in the one or more control messages, wherein the plurality of SRS resource sets are configured for codebook use, and at least one maximum rank value associated with an uplink shared channel transmission from a user equipment (UE), the at least one maximum rank value based at least in part on a threshold number of rank values ​​supported by the UE; sending a message including downlink control information for scheduling an uplink shared channel message, the downlink control information including one or more SRS resource indicator fields and one or more TPMI fields; as well as The uplink shared channel message is received according to a mapping between content of the one or more TPMI fields and a number of ports associated with at least one SRS resource from the plurality of SRS resource sets, the mapping being indicated by: the number of the at least one maximum rank values, and The maximum number of ports that the UE can support.

27. A network entity according to claim 26, wherein the one or more processors are further configured, individually or collectively, to: when the uplink shared channel message is associated with more than one uplink shared channels that at least partially overlap in the time domain, when the uplink shared channel message is associated with a single uplink shared channel, or both, receive information associated with the maximum number of ports that the UE can support via a capability report, wherein sending the message including the downlink control information is at least partially based on sending the information via the capability report.

28. The network entity of claim 26, wherein the one or more processors are further configured, individually or collectively, to: sending an indication of a configuration associated with the at least one maximum rank value, wherein the configuration is a first configuration or a second configuration, and wherein: The first configuration indicates that, in a case where the uplink shared channel message is associated with a single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the larger of a first maximum number of ports of a first SRS resource and a second maximum number of ports of a second SRS resource, and The second configuration indicates that: when the uplink shared channel message is associated with the single uplink shared channel, the maximum number of ports associated with the uplink shared channel message is equal to the sum of the first maximum number of ports of the first SRS resource and the second maximum number of ports of the second SRS resource.

29. A method for wireless communication by a user equipment (UE), the method comprising: Receiving one or more control messages indicating: a number of a plurality of sounding reference signal (SRS) resource sets, a number of one or more SRS resource indicator fields included in one or more control messages, and a number of one or more transmit precoding matrix indicator (TPMI) fields included in the one or more control messages, wherein the plurality of SRS resource sets are configured for codebook use, and at least one maximum rank value associated with uplink shared channel transmissions from the UE, the at least one maximum rank value based at least in part on a threshold number of rank values ​​supported by the UE; receiving a message including downlink control information for scheduling an uplink shared channel message, the downlink control information including one or more SRS resource indicator fields and one or more TPMI fields; interpreting the one or more SRS resource indicator fields and the one or more TPMI fields according to a mapping between contents of the one or more TPMI fields and a number of ports associated with at least one SRS resource from the plurality of SRS resource sets, the mapping being indicated by: the number of the at least one maximum rank values, and The maximum number of ports that the UE can support; and The uplink shared channel message is transmitted according to the mapping between the content of the one or more TPMI fields and the number of ports associated with the at least one SRS resource from the plurality of SRS resource sets.

30. A method for wireless communication by a network entity, the method comprising: Send one or more control messages indicating: a number of a plurality of sounding reference signal (SRS) resource sets, a number of one or more SRS resource indicator fields included in one or more control messages, and a number of one or more transmit precoding matrix indicator (TPMI) fields included in the one or more control messages, wherein the plurality of SRS resource sets are configured for codebook use, and at least one maximum rank value associated with an uplink shared channel transmission from a user equipment (UE), the at least one maximum rank value based at least in part on a threshold number of rank values ​​supported by the UE; sending a message including downlink control information for scheduling an uplink shared channel message, the downlink control information including one or more SRS resource indicator fields and one or more TPMI fields; as well as The uplink shared channel message is received according to a mapping between content of the one or more TPMI fields and a number of ports associated with at least one SRS resource from the plurality of SRS resource sets, the mapping being indicated by: the number of the at least one maximum rank values, and The maximum number of ports that the UE can support.

Images