Sounding Reference Signal Resource Set Configuration

Abstract

Various aspects of this disclosure generally relate to wireless communications. In some aspects, a user device (UE) may obtain configuration information for downlink control information (DCI) having a first DCI format, indicating a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value. The UE may identify whether the DCI having a second DCI format consists of a third SRS resource set associated with the first CORESET pool index value, or consists of a third SRS resource set and a fourth SRS resource set associated with the second CORESET pool index value. The UE may selectively transmit a first transmission and a second transmission that at least partially overlap in the time domain within the component carrier. Numerous other aspects are described.

Description

Technical Field

[0001] (Cross - Reference to Related Applications)

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 495,703, filed Apr. 12, 2023, and U.S. Non - Provisional Patent Application No. 18 / 614,914, filed Mar. 25, 2024, both entitled "SOUNDING REFERENCE SIGNAL RESOURCE SET CONFIGURATION", which are hereby incorporated by reference in their entirety.

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication, as well as techniques and apparatus for sounding reference signal resource set configuration.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, including telephone communication, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard, published by the Third Generation Partnership Project (3GPP).

[0004]

[0004] A wireless network may include one or more network nodes that support communication between wireless communication devices, such as one user equipment (UE) or multiple UEs. An UE may communicate with a network node via downlink and uplink communications. "Downlink" (or "DL") refers to a communication link from a network node to an UE, and "uplink" (or "UL") refers to a communication link from an UE to a network node. Some wireless networks may support device-to-device communication via local links (e.g., sidelink (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, among other examples).

[0005]

[0005] The above-mentioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables various UEs to communicate at the city, country, regional, and / or global levels. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, enhancing services, utilizing new spectra, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) on the downlink and CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM, DFT-s-OFDM) on the uplink, as well as by supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful. [Brief explanation of the drawing]

[0006]

[0006] A more detailed description of the features of the Disclosure listed above can be obtained by referring to the embodiments partially shown in the accompanying drawings, in order to gain a more detailed understanding of the features of the Disclosure listed above. However, it should be noted that the accompanying drawings show only certain typical embodiments of the Disclosure, and therefore the description may be incorporated into other equally effective embodiments and should not be considered to limit the scope of the Disclosure. The same reference numeral in different drawings may identify the same or similar elements. [Figure 1]

[0007] This figure shows an example of a wireless network as described in this disclosure. [Figure 2]

[0008] This figure shows an example of a network node that communicates with user equipment (UE) within a wireless network, as disclosed herein. [Figure 3]

[0009] This figure shows an exemplary non-aggregated base station architecture as described herein. [Figure 4A]

[0010] This figure shows an example of physical uplink shared channel (PUSCH) resources and sounding reference signal transmission as disclosed herein. [Figure 4B] This figure shows an example of a physical uplink shared channel (PUSCH) resource and sounding reference signal transmission as described in this disclosure. [Figure 5]

[0011] This figure shows an example associated with a sounding reference signal resource set configuration as disclosed herein. [Figure 6]

[0012] This figure shows an example of time-domain overlapping PUSCH transmission according to this disclosure. [Figure 7]

[0013] This figure shows an example of time-domain overlapping PUSCH transmission according to this disclosure. [Figure 8]

[0014] This figure shows an example of time-domain overlapping PUSCH transmission according to this disclosure. [Figure 9]

[0015] This figure shows an exemplary process implemented by, for example, a UE as described in this disclosure. [Figure 10]

[0016] This figure shows an exemplary process performed, for example, by a network node, as described in this disclosure. [Figure 11]

[0017] This is a diagram of an exemplary device for wireless communication according to the present disclosure. [Figure 12]

[0018] This is a diagram of an exemplary device for wireless communication according to the present disclosure. [Overview of the project]

[0007]

[0019] Some aspects described herein relate to methods for wireless communication performed by user equipment (UE). The method may include obtaining configuration information for downlink control information (DCI) having a first DCI format, indicating a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value. The method may include identifying whether the DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. The method may include selectively transmitting a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format.

[0008]

[0020] Some embodiments described herein relate to methods of wireless communication performed by network nodes. The method may include transmitting configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. The method may include transmitting a DCI having a second DCI format, which consists only of a third SRS resource set associated with a first CORESET pool index value, or both of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. The method may include receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having a first DCI format or a DCI having a second DCI format.

[0009]

[0021] Some embodiments described herein relate to devices for wireless communications in a UE. The devices may include memory and one or more processors coupled to the memory. One or more processors may be configured to obtain configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. One or more processors may be configured to identify whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. One or more processors may be configured to selectively transmit a first PUSCH transmit and a second PUSCH transmit that at least partially overlap in the time domain within a component carrier, according to at least one of DCI having a first DCI format or DCI having a second DCI format.

[0010]

[0022] Some embodiments described herein relate to devices for wireless communication in network nodes. These devices may include memory and one or more processors coupled to the memory. One or more processors may be configured to transmit configuration information for a DCI having a first DCI format, indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value. One or more processors may be configured to transmit a DCI having a second DCI format, which consists only of a third SRS resource set associated with a first CORESET pool index value, or both of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. One or more processors may be configured to receive a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of DCI having a first DCI format or DCI having a second DCI format.

[0011]

[0023] Some embodiments described herein relate to a non-temporary computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions can cause the UE to obtain configuration information indicating a DCI having a first DCI format, a first SRS resource set associated with a first CORESET pool index value, and a second SRS resource set associated with a second CORESET pool index value. When executed by one or more processors of the UE, the set of instructions can cause the UE to identify whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. When the set of instructions is executed by one or more processors of the UE, it can cause the UE to selectively send a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format.

[0012]

[0024] Some embodiments described herein relate to a non-temporary computer-readable medium storing a set of instructions for wireless communication by network nodes. When executed by one or more processors of the network nodes, the set of instructions can cause the network nodes to transmit configuration information indicating a DCI having a first DCI format, a first SRS resource set associated with a first CORESET pool index value, and a second SRS resource set associated with a second CORESET pool index value. When executed by one or more processors of the network nodes, the set of instructions can cause the network nodes to transmit a DCI having a second DCI format, which consists only of a third SRS resource set associated with a first CORESET pool index value, or both of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. When the set of instructions is executed by one or more processors on a network node, it can cause the network node to receive a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format.

[0013]

[0025] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus may include means for obtaining configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for DCI having a first DCI format. The apparatus may include means for identifying whether DCI having a second DCI format is composed only of a third SRS resource set associated with the first CORESET pool index value or is composed of both a third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value. The apparatus may include means for selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in a time region within a component carrier according to at least one of DCI having a first DCI format or DCI having a second DCI format.

[0014]

[0026] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus may include means for transmitting configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for DCI having a first DCI format. The apparatus may include means for transmitting DCI having a second DCI format that is composed of only a third SRS resource set associated with the first CORESET pool index value or is composed of both a third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value. The apparatus may include means for receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in a time domain within a component carrier according to at least one of the DCI having the first DCI format or the DCI having the second DCI format.

[0015]

[0027] Aspects generally relate to a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system that are substantially described herein with reference to the drawings and as shown by the drawings.

[0016]

[0028] The above provides a fairly broad overview of the features and technical advantages of the embodiments of this disclosure so that the following “Modes for Carrying Out the Invention” may be better understood. Additional features and advantages are described below. The concepts and specific embodiments disclosed may be readily used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent structures shall not deviate from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their configuration and method of operation, will be better understood, along with the relevant advantages, by considering the following description in relation to the accompanying figures. Each figure is provided for illustrative and explanatory purposes and is not provided to define any limitation of the claims.

[0017]

[0029] While various embodiments are described herein by example to several embodiments, those skilled in the art will understand that such embodiments can be implemented in many different configurations and scenarios. The technologies described herein can be implemented using a variety of platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some embodiments can be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). The embodiments can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described embodiments and features may include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or analog adders) for analog and digital purposes. The embodiments described herein are intended to be applicable to a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures. [Modes for carrying out the invention]

[0018]

[0030] Hereafter, various aspects of this disclosure will be described more fully with reference to the accompanying drawings. However, this disclosure can be embodied in many different forms and should not be construed as being limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure sufficient and complete and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art should understand that the scope of this disclosure is intended to encompass any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of aspects described herein. In addition, the scope of this disclosure is intended to encompass any such apparatus or method practiced using other structures, functions, or structures and functions in addition to, or other than, the various aspects of this disclosure described herein. It should be understood that any aspect of this disclosure disclosed herein can be embodied by one or more elements of the claims.

[0019]

[0031] Next, several embodiments of telecommunications systems are presented with reference to various devices and techniques. These devices and techniques are described in the following “Modes for Carrying Out the Invention” and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “Elements”). These Elements may be implemented using hardware, software, or a combination thereof. Whether such Elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0020]

[0032] While various aspects may be described herein using terms commonly associated with 5G or New Radio (NR) radio access technology (RAT), the aspects of this disclosure may also apply to other RATs, such as 3G RAT, 4G RAT, and / or RATs following 5G (e.g., 6G).

[0021]

[0033] Various embodiments generally relate to sounding reference signal (SRS) resource set configurations. Some embodiments, in more detail, relate to SRS resource set configurations for overlapping physical uplink shared channel (PUSCH) transmissions associated with different downlink control information (DCI) formats. In some examples, user equipment (UE) may obtain configuration information indicating a first SRS resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value for a first DCI format. The UE may identify whether the second DCI format consists of a third SRS resource set associated with the first CORESET pool index value, or consists of a third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value. The UE may selectively transmit a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format. In some examples, the second PUSCH transmission may be a Type 1 configurable grant PUSCH transmission and may consist of a first SRS resource set, a second SRS resource set, a third SRS resource set, or a fourth SRS resource set. In some other examples, the second PUSCH transmission may be a Type 1 configurable grant PUSCH transmission and may consist of a first SRS resource set or a second SRS resource set.

[0022]

[0034] Certain aspects of the subject matter described herein can be implemented to achieve one or more of the following potential benefits. In some examples, by identifying whether the DCI format is composed of a single set of SRS resources or two sets of SRS resources, the techniques described can be used to selectively transmit time-domain overlapping PUSCH transmissions in a component carrier. The possibility of interference and / or dropped transmissions by UEs or network nodes can be reduced.

[0023]

[0035] Figure 1 shows an example of a wireless network 100 as described herein. The wireless network 100 may be, or may include, elements thereof, a 5G (e.g., NR) network and / or a 4G (e.g., Long-Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE120a, UE120b, UE120c, UE120d, and UE120e), and / or other entities. A network node 110 is a network node that communicates with a UE 120. As shown in the figure, a network node 110 may include one or more network nodes. For example, network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). Alternatively, network node 110 may be a non-aggregated network node (sometimes referred to as a non-aggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0024]

[0036] In some examples, network node 110 is a network node such as an RU that communicates with UE 120 via a wireless access link, or includes such network nodes. In some examples, network node 110 is a network node such as a DU that communicates with other network nodes 110 via a fronthaul link or a midhaul link, or includes such network nodes. In some examples, network node 110 is a network node such as a CU that communicates with other network nodes 110 via a midhaul link or with the core network via a backhaul link, or includes such network nodes. In some examples, network node 110 (such as an aggregated network node 110 or an unaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network nodes 110 may include, for example, NR base stations, LTE base stations, node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access points, transmission reception points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 may interconnect with each other or with one or more other network nodes 110 within the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0025]

[0037] In some examples, network node 110 may provide communication coverage to a specific geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” may refer to the coverage area of ​​network node 110 and / or the network node subsystems serving this coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 subscribing to the service. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 subscribing to the service. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow limited access by UEs 120 associated with that femtocell (e.g., UEs 120 within a closed subscriber group, CSG). A network node 110 for a macrocell may be referred to as a macronetwork node. A network node 110 for a picocell may be referred to as a piconetwork node. A network node 110 for a femtocell may be referred to as a femtonetwork node or home network node. In the example shown in Figure 1, network node 110a can be a macronetwork node for macrocell 102a, network node 110b can be a piconetwork node for picocell 102b, and network node 110c can be a femtonetwork node for femtocell 102c. A network node may support one or more (e.g., three) cells. In some embodiments, cells may not necessarily be fixed, and the geographical area of ​​a cell may move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0026]

[0038] In some embodiments, the terms “base station” or “network node” may refer to an aggregated base station, a non-aggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some embodiments, “base station” or “network node” may refer to a CU, DU, RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some embodiments, the terms “base station” or “network node” may refer to a single device configured to perform one or more functions, such as those described herein in relation to network node 110. In some embodiments, the terms “base station” or “network node” may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of several different devices (which may be located at the same or different geographical locations) may be configured to perform at least a portion of a function, or to replicate the performance of at least a portion of a function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some embodiments, the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some embodiments, two or more base station functions may be instantiated on a single device. In some embodiments, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may contain two or more base stations.

[0027]

[0039] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit that data to downstream nodes (e.g., UE 120 or network node 110). A relay station can be a UE 120 that can relay transmissions to other UE 120s. In the embodiment shown in Figure 1, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between them. The network node 110 that relays communications may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0028]

[0040] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macronetwork nodes, piconetwork nodes, femtonetwork nodes, and relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference within the wireless network 100. For example, macronetwork nodes may have high transmit power levels (e.g., 5 to 40 watts), while piconetwork nodes, femtonetwork nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0029]

[0041] The network controller 130 may be coupled to or communicate with a set of network nodes 110, and may provide coordination and control over these network nodes 110. The network controller 130 may communicate with the network nodes 110 via backhaul or midhaul communication links. The network nodes 110 may communicate with each other directly or indirectly via wireless or wireline backhaul communication links. In some embodiments, the network controller 130 may be a CU or core network device, or may include a CU or core network device.

[0030]

[0042] The UE120 can be distributed throughout the entire wireless network 100, and each UE120 can be fixed or mobile. The UE120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE120 may be a mobile phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0031]

[0043] Some UE120s can be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. Examples of MTC UEs and / or eMTC UEs may include robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with network nodes, other devices (e.g., remote devices), or any other entities. Some UE120s can be considered Internet-of-Things (IoT) devices and / or implemented as NB-IoT (narrowband IoT) devices. Some UE120s can be considered customer premises equipment. A UE120 may be contained within a housing that accommodates its components, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled to each other. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) can be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0032]

[0044] In general, any number of wireless networks 100 can be deployed within a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as wireless technology, air interface, etc. Frequencies may be referred to as carriers, frequency channels, etc. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT within a given geographical area. In some cases, NR or 5G RAT networks may be deployed.

[0033]

[0045] In some embodiments, two or more UE120s (e.g., indicated as UE120a and UE120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such embodiments, UE120s may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by network node 110.

[0034]

[0046] Devices in wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., depending on frequency or wavelength. For example, devices in wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands are defined as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) defined by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0035]

[0047] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Recent 5G NR research defines the operating band for these intermediate band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit the FR1 and / or FR2 characteristics, and thus, in effect, the features of FR1 and / or FR2 can be extended to the intermediate band frequencies. In addition, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been defined as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0036]

[0048] With the above examples in mind, please understand that, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that may be below 6GHz, frequencies that may be within the FR1 range, or frequencies that may include intermediate band frequencies. Furthermore, please understand that, unless otherwise specified, terms such as "millimeter wave" may broadly refer to frequencies that may include intermediate band frequencies, frequencies that may be within the FR2, FR4, FR4-a or FR4-1, and / or FR5 ranges, or frequencies that may be within the EHF band. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0037]

[0049] In some embodiments, UE120 may include a communications manager 140. As described in more detail elsewhere in this specification, the communications manager 140 may obtain configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format, identify whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or both of the third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value, and selectively transmit first and second PUSCH transmissions that at least partially overlap in the time domain within the component carrier, according to at least one of the DCI having a first DCI format or a DCI having a second DCI format. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0038]

[0050] In some embodiments, the network node 110 may include a communications manager 150. As described in more detail elsewhere in this specification, the communications manager 150 may transmit configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format; transmit a DCI having a second DCI format which consists only of a third SRS resource set associated with a first CORESET pool index value, or both of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value; and receive first and second PUSCH transmissions that at least partially overlap in the time domain within the component carrier, according to at least one of the DCI having a first DCI format or a DCI having a second DCI format. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0039]

[0051] As stated above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0040]

[0052] Figure 2 shows one embodiment 200 of a network node 110 communicating with a UE 120 within a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T (T≧1) antennas. The UE 120 may be equipped with a set of antennas 252a to 252r, such as R (R≧1) antennas. The network node 110 in Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0041]

[0053] At network node 110, the transmit processor 220 may receive data from data source 212 addressed to UE120 (or a set of UE120s). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE120, at least in part on one or more channel quality indicators (CQIs) received from the UE120. The network node 110 may process (e.g., encode and modulate) the data for the UE120, at least in part on the selected MCS(s) for the UE120, and may provide data symbols to the UE120. The transmit processor 220 may process system information (e.g., related to semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling), and may provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may, where applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and may provide a set of output symbol streams (e.g., T output symbol streams) to the corresponding set of modems 232 (e.g., T modems) indicated as modems 232a to 232t. For example, each output symbol stream may be provided to the modulator component of modem 232 (indicated as MOD).Each modem 232 may acquire an output sample stream by processing the corresponding output symbol stream (for example, for OFDM) using the corresponding modulator component. Each modem 232 may further acquire a downlink signal by processing the output sample stream (for example, converting it to analog, amplifying it, filtering it, and / or upconverting it) using the corresponding modulator component. Modems 232a to 232t may transmit a set of downlink signals (for example, T downlink signals) over the corresponding set of antennas 234 (for example, T antennas) indicated as antennas 234a to 234t.

[0042]

[0054] In UE120, a set of antennas 252 (indicated as antennas 252a to 252r) may receive downlink signals from network node 110 and / or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) indicated as modems 254a to 254r. For example, each received signal may be provided to a demodulator component of modem 254 (indicated as DEMOD). Each modem 254 may acquire input samples by modifying the received signals (e.g., filtering, amplifying, downconverting, and / or digitizing) using the corresponding demodulator component. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to acquire received symbols. A MIMO detector 256 is capable of acquiring received symbols from modem 254, performing MIMO detection on the received symbols where applicable, and providing the detected symbols. The receiving processor 258 may process the detected symbols (e.g., demodulate and decode), provide the decoded data for UE120 to the data sink 260, and provide the decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may, among other examples, determine the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the CQI parameter. In some examples, one or more components of UE120 may be contained within the housing 284.

[0043]

[0055] The network controller 130 may include a communication unit 294, a controller / processor 290, and memory 292. The network controller 130 may include, for example, one or more devices in the core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0044]

[0056] One or more antennas (for example, antennas 234a-234t and / or antennas 252a-252r) may include, or be included in, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components in Figure 2.

[0045]

[0057] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting, including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of UE120 may include a modulator and demodulator. In some examples, UE120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and memory 282 to carry out any of the methods described herein (see, for example, Figures 5 to 12).

[0046]

[0058] In network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244, which can communicate with network controller 130. Network node 110 may include a scheduler 246 for scheduling one or more UE 120 for downlink and / or uplink communication. In some examples, the modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of an antenna(s) 234, a modem(s) 232, a MIMO detector 236, a receiving processor 238, a transmitting processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., a controller / processor 240) and memory 242 to carry out any aspect of the methods described herein (see, for example, Figures 5 to 12).

[0047]

[0059] As will be described in more detail elsewhere in this specification, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or any other component(s) in Figure 2 may perform one or more techniques associated with SRS resource set configuration. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or any other component(s) in Figure 2 may perform or direct the operation of, for example, process 900 in Figure 9, process 1000 in Figure 10, and / or other processes as described herein. Memories 242 and 282 may store data and program code for network node 110 and UE 120, respectively. In some embodiments, memory 242 and / or memory 282 may include non-temporary computer-readable media storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors in the network node 110 and / or UE 120 (e.g., directly, or after being compiled, translated, and / or interpreted), one or more processors, UE 120, and / or network node 110 may be caused to perform or direct the operation of, for example, process 900 in Figure 9, process 1000 in Figure 10, and / or other processes as described herein. In some examples, executing an instruction may include, among other examples, running the instruction, translating the instruction, compiling the instruction, and / or interpreting the instruction.

[0048]

[0060] In some embodiments, the UE120 includes means for obtaining configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format; means for identifying whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value; and / or means for selectively transmitting first and second PUSCH transmissions that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having a first DCI format or a DCI having a second DCI format. Means for the UE120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receiving processor 258, transmitting processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0049]

[0061] In some embodiments, the network node 110 includes means for transmitting configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format; means for transmitting a DCI having a second DCI format which consists only of a third SRS resource set associated with a first CORESET pool index value, or both of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value; and means for receiving first and second PUSCH transmissions which at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having a first DCI format or a DCI having a second DCI format. Means for the network node 110 to perform the operations described herein may include, for example, one or more of the following: a communications manager 150, a transmitting processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0050]

[0062] Although the blocks in Figure 2 are shown as individual components, the functions described above with respect to these blocks may be implemented in a single hardware, software, or combination of components, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0051]

[0063] As stated above, Figure 2 is provided as an example. Other examples may differ from those described in relation to Figure 2.

[0052]

[0064] The deployment of communication systems such as 5G NR systems can be arranged in multiple ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in an aggregated or unaggregated architecture. For example, a base station (e.g., among other examples, Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell), or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or an unaggregated base station. "Network entity" or "network node" may refer to an unaggregated base station, or to one or more units of an unaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0053]

[0065] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A non-aggregated base station (e.g., a non-aggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0054]

[0066] The operation or network design of a base station type may take into account the aggregation characteristics of base station functionality. For example, by utilizing non-aggregated base stations in an IAB network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network, or C-RAN), the scaling of the communication system can be facilitated by separating base station functionality into one or more units that can be deployed individually. A non-aggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually in at least one unit, thereby enabling flexibility in network design. Various units of a non-aggregated base station can be configured to communicate with at least one other unit of the non-aggregated base station via wired or wireless communication.

[0055]

[0067] Figure 3 shows an exemplary non-aggregated base station architecture 300 according to the present disclosure. The non-aggregated base station architecture 300 may include a CU 310 that can communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more non-aggregated control units (e.g., a quasi-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DU 330 via separate midhaul links, for example, via an F1 interface. Each DU 330 may communicate with one or more RU 340 via separate fronthaul links. Each RU 340 may communicate with one or more UE 120 via its respective radio frequency (RF) access link. In some implementations, the UE 120 may be serviced simultaneously by multiple RU 340s.

[0056]

[0068] Each of the units, including CU310, DU330, RU340, and the quasi-RT RIC325, non-RT RIC315, and SMO framework 305, may include, or be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmitting medium. A related processor or controller providing instructions to each of the units, or to one or more communication interfaces of individual units, may be configured to communicate with one or more of the other units via a transmitting medium. In some embodiments, each of the units may include a wired interface configured to receive or transmit signals via a wired transmission medium to one or more of the other units, and a wireless interface which may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit or receive signals via a wireless transmitting medium to one or more of the other units.

[0057]

[0069] In some embodiments, the CU310 may host one or more higher-layer control functions. Such control functions include, among other examples, radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP). Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU310. The CU310 may be configured to handle user plane functionality (e.g., Central Unit-User Plane (CU-UP) functionality), control plane functionality (e.g., Central Unit-Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface such as the E1 interface. The CU310 can be implemented to communicate with the DU330 as needed for network control and signaling.

[0058]

[0070] Each DU330 may correspond to a logic unit containing one or more base station functions for controlling the operation of one or more RU340s. In some embodiments, the DU330 can host one or more of the radio link control (RLC) layer, the medium access control (MAC) layer, and one or more upper physical (PHY) layers, at least in part according to a functional partition such as a functional partition as defined by 3GPP. In some embodiments, one or more upper PHY layers may be implemented by one or more modules for forward error correction (FEC) coding and decoding, scrambling, and modulation and demodulation, among other examples. In some embodiments, the DU330 can further host one or more lower-level PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (sometimes referred to as a module) can be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU330, or with control functions hosted by the CU310.

[0059]

[0071] Each RU340 can perform lower-layer functionality. In some deployments, a RU340 controlled by a DU330 may correspond to a logical node hosting RF processing functions or lower PHY layer functions such as performing FFT, iFFT, digital beamforming, or PRACH extraction and filtering, based on functional partitioning (e.g., functional partitioning as defined by 3GPP), among other examples. In such architectures, each RU340 can operate to handle over-the-air (OTA) communication with one or more UE120s. In some implementations, the real-time and non-real-time modes of control plane communication and user plane communication with the RU340(one or more) can be controlled by the corresponding DU330. In some scenarios, this configuration can enable each DU330 and CU310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0060]

[0072] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as the open cloud (O-Cloud) platform 390) to perform lifecycle management of the network elements (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU310, DU330, RU340, non-RT RIC315, and quasi-RT RIC325. In some implementations, the SMO framework 305 can communicate with hardware embodiments of the 4G RAN, such as the open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RU340s via a separate O1 interface. The SMO framework 305 may also include a non-RT RIC315 configured to support the functionality of the SMO framework 305.

[0061]

[0073] Non-RT RIC315 may be configured to include logical functions that enable policy-based guidance for applications / functions in quasi-RT RIC325, including non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or applications / functions in quasi-RT RIC325. Non-RT RIC315 can be coupled to or communicate with quasi-RT RIC325 (via the A1 interface, for example). Quasi-RT RIC325 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources through data acquisition and action via an interface connecting one or more CU310s, one or more DU330s, or both, and an O-eNB to the quasi-RT RIC325 (via the E2 interface, for example).

[0062]

[0074] In some implementations, the non-RT RIC315 may receive parameter or external enrichment information from an external server to generate an AI / ML model to be deployed in the quasi-RT RIC325. Such information can be utilized by the quasi-RT RIC325 and may be received in the SMO framework 305 or the non-RT RIC315 from a non-network data source or from a network function. In some examples, the non-RT RIC315 or quasi-RT RIC325 may be configured to tune the behavior or performance of the RAN. For example, the non-RT RIC315 may monitor long-term trends and patterns in performance and employ an AI / ML model to take corrective action through the SMO framework 305 (e.g., reconfiguration via the O1 interface) or by creating a RAN management policy (e.g., an A1 interface policy).

[0063]

[0075] As stated above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0064]

[0076] Figures 4A and 4B show examples 400 of PUSCH resources and SRS transmissions according to this disclosure.

[0065]

[0077] In some cases, more than one type of push transmission may be supported, such as codebook (CB) based push transmission and non-codebook (NCB) based push transmission. For CB-based transmission, UE120 may consist of a single SRS resource set. A single SRS resource set may have usage configured for CB. Up to four SRS resources within the SRS resource set may be configured for UE120. Each SRS resource may be an RRC configured with several SRS ports (nrofSRS_Ports). The SRS resource indicator (SRI) field in the uplink DCI that schedules the push transmission may indicate a single SRS resource. The number of ports indicated for the SRS resource may determine the number of antenna ports used for the push transmission. The push transmission may be transmitted using the same spatial domain filter (e.g., uplink beam) as the indicated SRS resource. The number of layers (e.g., rank) and the transmitted precoding matrix indicator (TPMI) (precoder) for a scheduled PUSCH transmission can be determined from a separate DCI field associated with “Precoding Information and Number of Layers”. For NCB-based transmissions, the UE120 may consist of a single SRS resource set. A single SRS resource set may have a usage configured for the NCB. Up to four SRS resources within the SRS resource set may be configured for the UE120. Each SRS resource may be associated with a single port. The SRI field in the uplink DCI for scheduling a PUSCH transmission may indicate one or more SRS resources. The number of indicated SRS resources can determine the rank (e.g., number of layers) for the scheduled PUSCH transmission. The PUSCH may be transmitted using the same precoder and the same spatial domain filter (e.g., beam) as the indicated SRS resources.For both CB-based and NCB-based push transmissions, the size of the SRI field can be a function of the number of SRS resources in the SRS resource set.

[0066]

[0078] The SRS resource sets and SRI fields in the uplink DCI for the CB-based and NCB-based push transmissions described above may be used for DCI format 0_1. In some cases, DCI format 0_2 may be used for scheduling push transmissions. DCI format 0_2 may be used for DCI size reduction by reducing the number of bits required for each DCI field, at least in part based on the RRC configuration. The SRS resource sets (for CB-based and NCB-based push transmissions) may be configured separately for push transmissions scheduled by DCI format 0_2. For example, the RRC parameter srs-ResourceSetToAddModListDCI-0-2 may be used for DCI format 0_2, and the RRC parameter ResourceSetToAddModList may be used for DCI format 0_1. For CB-based push transmissions, a single SRS resource set with a configured use for the CB may be configured within srs-ResourceSetToAddModListDCI-0-2. For NCB-based push transmissions, a single SRS resource set with the usage configured for NCB can be configured within srs-ResourceSetToAddModListDCI-0-2. In some cases, fewer SRS resources (N) can be included in the SRS resource set. SRS,0_2 ) can be configured, which may result in a smaller SRI bit width. However, N in the SRS resource set for DCI format 0_2 SRS,0_2 The SRS resource is the first N in the SRS resource set for DCI format 0_1. SRS,0_2It may need to be an SRS resource. This can ensure that UE complexity does not increase (for example, in the case of DCI format 0_2, which uses a subset of SRS resources in a set of SRS resources scheduled by DCI with DCI format 0_1).

[0067]

[0079] In some cases, two different PUSCH resources within the same serving cell or component carrier may partially or completely overlap in the time domain and / or frequency domain. Two SRS resource sets (for CB or NCB) may be configured for two different PUSCH resources. Overlap in the time domain and / or frequency domain may be enabled by a multi-DCI-based multi-TRP framework, and the two PUSCH resources may be associated with different CORESET Pool Index (CORESETPoolIndex) values. As shown in Figure 4A, the first PUSCH resource 405 may be associated with the first SRS resource set and CORESET Pool Index value 0, and / or with a transmission using a first beam, a first transmission configuration indicator (TCI) state, a first power control parameter, or a first precoder. The second PUSCH resource 410 may be associated with a second SRS resource set and a CORESET pool index value of 1, and / or with a transmission using a second beam, a second TCI state, a second power control parameter, or a second precoder. As shown by reference no. 415, the first PUSCH resource 405 and the second PUSCH resource 410 may completely overlap in the time domain and in the frequency domain. As shown by reference no. 420, the first PUSCH resource 405 and the second PUSCH resource 410 may completely overlap in the time domain and partially overlap in the frequency domain. As shown by reference no. 425, the first PUSCH resource 405 and the second PUSCH resource 410 may partially overlap in the time domain but not overlap in the frequency domain. As indicated by reference number 430, the first PUSCH resource 405 and the second PUSCH resource 410 may partially overlap in the time domain and may partially overlap in the frequency domain.

[0068]

[0080] In some cases, SRS resources with lower identifiers (IDs) may be associated with CORESET pool index value 0, and SRS resources with higher IDs may be associated with CORESET pool index value 1. For dynamic grant (DG) pushes or Type 2 configured grant (CG) pushes, the SRI / TPMI fields may be interpreted, as described herein, at least partially based on the corresponding SRS resource set and at least partially based on the CORESET from which the scheduling or activation DCI is received. For Type 1 CG pushes, the corresponding SRS resource set (e.g., the index or ID of the SRS resource set) may be RRC configured (e.g., since there is no DCI). In some cases, two push transmissions may occur simultaneously (overlapping in time) if they are associated with different SRS resource sets, or, in the case of DG or Type 2 CG, with different CORESET pool index values.

[0069]

[0081] In some cases, when a separate SRS resource set is scheduled by DCI having DCI format 0_2, there can be up to four SRS resource sets for multi-DCI-based PUSCH+PUSCH transmission (for either CB or NCB). SRS resource sets with lower IDs can be associated with CORESET pool index value 0, and SRS resource sets with higher IDs can be associated with CORESET pool index value 1. This rule can be applied separately to the two SRS resource sets configured by srs-ResourceSetToAddModList (in the case of DCI format 0_1) and the two SRS resource sets configured by srs-ResourceSetToAddModListDCI-0-2 (in the case of DCI format 0_2). The SRI / TPMI field in DCI format 0_2 may be interpreted similarly. In some cases, the relationship between the SRS resource set for DCI format 0_1 and the SRS resource set for DCI format 0_2 may only be applicable to SRS resource sets associated with the same CORESET pool index value. As shown in Figure 4B, for DCI format 0_1, SRS resource set 435 can include SRS resource 0, SRS resource 1, SRS resource 2, and SRS resource 3 (shown as SRS 0, SRS 1, SRS 2, and SRS 3 respectively). SRS resource set 435 can be associated with SRS resource set IDx. SRS resource set 440 can include SRS resource 4, SRS resource 5, SRS resource 6, and SRS resource 7 (shown as SRS 4, SRS 5, SRS 6, and SRS 7 respectively). SRS resource set 440 can be associated with SRS resource set IDy, where x < y. SRS resource set 435 may be associated with CORESET pool index value 0, and SRS resource set 440 may be associated with CORESET pool index value 1.In the case of DCI format 0_2, the SRS resource set 445 may include SRS resource 0 and SRS resource 1. The SRS resource set 440 may be associated with the SRS resource ID z. The SRS resource set 450 may include SRS resource 4 and SRS resource 5. The SRS resource set 450 may be associated with the SRS resource ID t, where z < t. The SRS resource set 445 may be associated with the CORESET pool index value 0, and the SRS resource set 450 may be associated with the CORESET pool index value 1. The SRS resource sets associated with DCI format 0_1 and the SRS resource sets associated with DCI format 0_2 have a subset relationship with respect to the SRS resource sets associated with the same CORESETPoolIndex value. For example, as shown in FIG. 4B, the SRS resource sets 435 and 445 are both associated with the CORESETPoolIndex value 0, and the SRS resource set 445 associated with DCI format 0_2 is a subset of the SRS resource set 435 associated with DCI format 0_1. Similarly, the SRS resource sets 440 and 450 are both associated with the CORESETPoolIndex value 1, and the SRS resource set 450 associated with DCI format 0_2 is a subset of the SRS resource set 440 associated with DCI format 0_1.

[0070]

[0082] In some cases, two SRS resource sets may be scheduled by a DCI having a first DCI format, and a single SRS resource set may be scheduled by a DCI having a second DCI format. For example, two SRS resource sets may be scheduled by a DCI having DCI format 0_1, and a single SRS resource set may be scheduled by a DCI having DCI format 0_2. Alternatively, two SRS resource sets may be scheduled by a DCI having DCI format 0_1, and a single SRS resource set may be scheduled by a DCI having DCI format 0_2. In this case, the UE may not be able to determine the association between a single SRS resource set for a DCI format composed of a single SRS resource set and the CORESET pool index value. In some cases, the UE may not be able to determine whether time-domain overlapping PUSCH transmissions associated with different DCI formats are possible. This may result in interference transmissions and / or dropped transmissions by the UE or network nodes.

[0071]

[0083] Various embodiments generally relate to SRS resource set configurations. Some embodiments relate, more specifically, to SRS resource set configurations for overlapping push transmissions associated with different DCI formats. In some examples, a UE may obtain configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a first DCI format. The UE may identify whether the second DCI format consists of a third SRS resource set associated with the first CORESET pool index value, or a third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value. The UE may selectively transmit first and second push transmissions that at least partially overlap in the time domain within a component carrier, according to at least one of a DCI having the first DCI format or a DCI having the second DCI format. In some examples, the second PUSCH transmission may be a Type 1 configured grant PUSCH transmission and may consist of the first, second, third, or fourth SRS resource set. In some other examples, the second PUSCH transmission may be a Type 1 configured grant PUSCH transmission and may consist of the first or second SRS resource set.

[0072]

[0084] Certain aspects of the subject matter described herein can be implemented to achieve one or more of the following potential benefits. In some examples, by identifying whether the DCI format is composed of a single set of SRS resources or two sets of SRS resources, the techniques described can be used to selectively transmit time-domain overlapping PUSCH transmissions in a component carrier. The possibility of interference and / or dropped transmissions by UEs or network nodes can be reduced.

[0073]

[0085] As stated above, Figures 4A and 4B are provided as examples. Other examples may differ from those described with respect to Figures 4A and 4B.

[0074]

[0086] Figure 5 shows an example 500 associated with the SRS resource set configuration as described herein.

[0075]

[0087] As shown by reference number 505, UE120 may obtain configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. In some embodiments, network node 110 may transmit configuration information and UE120 may receive configuration information. Additionally or alternatively, UE120 may be configured (pre-configured) with configuration information. The first CORESET pool index value may be CORESET pool index value 0, and the second CORESET pool index value may be CORESET pool index value 1.

[0076]

[0088] In some embodiments, UE120 may consist of two CORESET pool index values ​​in a component carrier (e.g., CORESET pool index value 0 and CORESET pool index value 1) for push transmissions that at least partially overlap in the time domain within the component carrier (e.g., for multi-DCI based multi-TRP). UE120 may consist of two SRS resource sets (e.g., a first SRS resource set and a second SRS resource set) respectively associated with the two CORESET pool index values ​​for CB-based and / or NCB-based push transmissions associated with a DCI having a first DCI format. In some embodiments, the first DCI format may be DCI format 0_1. In this case, the first SRS resource set and the second SRS resource set may be configured in srs-ResourceSetToAddModList. In some other embodiments, the first DCI format may be DCI format 0_2. In this case, a first SRS resource set and a second SRS resource set may be configured in srs-ResourceSetToAddModListDCI-0-2. In some embodiments, the association between the two SRS resource sets and the two CORESET pool index values ​​may be based at least in part on the identifier values ​​associated with the SRS resource sets. For example, the first SRS resource set may be associated with the first CORESET pool index value at least in part on the fact that the first SRS resource set has an identifier (x) that has a lower value (y) than the identifier value (y) associated with the second SRS resource set (e.g., x <y)。

[0077]

[0089] As shown by reference number 510, UE120 can identify whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. As illustrated in relation to Figure 4, in one example, a DCI having a second DCI format may consist only of SRS resource set z associated with CORESET pool index value 0. In another example, a DCI having a second DCI format may consist of SRS resource set z associated with CORESET pool index value 0 and SRS resource set t associated with CORESET pool index value 1. UE120 can monitor DCI having a second DCI format for PUSCH scheduling. In some embodiments, the first DCI format may be DCI format 0_1, and the second DCI format may be DCI format 0_2. In some other embodiments, the first DCI format may be DCI format 0_2, and the second DCI format may be DCI format 0_1.

[0078]

[0090] As indicated by reference number 515, UE120 may transmit and network node 110 may receive a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier. The first PUSCH transmission and the second PUSCH transmission may at least partially be based on DCI having a first DCI format and / or DCI having a second DCI format.

[0079]

[0091] In the first example, UE120 may identify that two SRS resource sets are scheduled by a DCI having a second DCI format. For example, UE120 may identify that the DCI having a second DCI format consists of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value.

[0080]

[0092] In some embodiments, the SRS resource set for a Type 1 configured grant push transmission may be a first SRS resource set, a second SRS resource set, a third SRS resource set, or a fourth SRS resource set. In some other embodiments, the SRS resource set for a Type 1 configured grant push transmission may be a first SRS resource set or a second SRS resource set (for example, any of the SRS resource sets configured in srs-ResourceSetToAddModList for DCI format 0_1).

[0081]

[0093] In some embodiments, a first PUSCH transmission and a second PUSCH transmission may be transmitted simultaneously (e.g., at least partially overlapping in the time domain) on the same component carrier, at least partially based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially based on the fact that one of the SRS resource sets is not a subset of the other SRS resource set. In the above example, if the first PUSCH transmission and the second PUSCH transmission are associated with SRS resource sets IDx and IDy, SRS resource set IDz and IDt, SRS resource set IDx and IDt, or SRS resource set IDz and IDy, then the first PUSCH transmission and the second PUSCH transmission may be transmitted simultaneously. Alternatively, if the first and second push transmissions are associated with SRS resource sets IDx and IDz, or SRS resource sets IDy and IDt, the first and second push transmissions may not be transmitted simultaneously. Additional details regarding these features are described in relation to Figure 6. In some embodiments, if one SRS resource set is a subset of another SRS resource set (e.g., SRS resource sets IDx and IDz, or SRS resource sets IDy and IDt), the push transmissions may be transmitted from the same panel (e.g., using the same beam and the same power control parameters), but in the case of simultaneous push transmissions, the UE120 may need to use different panels.In some embodiments, this condition may be automatically guaranteed for two PUSCH transmissions corresponding to DG transmissions and DG transmissions, DG transmissions and Type 2 CG transmissions, or Type 2 CG transmissions and Type 2 CG transmissions, respectively, with the two PUSCH transmissions associated with different CORESET pool index values ​​(assuming that for each DCI format, the CORESET pool index of the CORESET from which the DCI is received determines the associated SRS resource set). However, this condition may need to be imposed for two PUSCH transmissions corresponding to DG transmissions and Type 1 CG transmissions, or Type 2 CG transmissions and Type 1 CG transmissions, respectively.

[0082]

[0094] In the second example, UE120 may identify that a single SRS resource set is scheduled by a DCI having a second DCI format. For example, UE120 may identify that a DCI having a second DCI format consists of a third SRS resource set associated with a first CORESET pool index value (CORESET pool index value 0). If the second DCI format is DCI format 0_2, the SRS resource set may be configured in srs-ResourceSetToAddModListDCI-0-2. Alternatively, if the second DCI format is DCI format 0_1, the SRS resource set may be configured in srs-ResourceSetToAddModList.

[0083]

[0095] In some embodiments, UE120 may decide not to receive a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value (CORESET pool index value 1). For example, a DCI having a second DCI format may only be received in a CORESET associated with CORESET pool index value 0. In some embodiments, if UE120 is scheduled to send a first PUSCH transmission by a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value (CORESET pool index value 1), UE120 may decide not to schedule a second PUSCH transmission that at least partially overlaps the first PUSCH transmission. If one of the PUSCH transmissions is scheduled by a DCI having a second DCI format associated with a second CORESET pool index value, simultaneous PUSCH transmissions may not be permitted. In some embodiments, if UE120 is scheduled to send a first PUSCH transmission by a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value (CORESET pool index value 1), UE120 may be scheduled to send a second PUSCH transmission that at least partially overlaps the first PUSCH transmission, only if UE120 is scheduled by a DCI having a first DCI format in a CORESET associated with the second CORESET pool index value. In this case, the conditions for simultaneous PUSCH transmissions may not be based on association with different CORESET pool index values. Additional details regarding these features are described in relation to Figure 7.

[0084]

[0096] In some embodiments, the SRS resource set for a Type 1 configured grant push transmission may be a first SRS resource set, a second SRS resource set, or a third SRS resource set. In some other embodiments, the SRS resource set for a Type 1 configured grant push transmission may be a first SRS resource set or a second SRS resource set (for example, any of the SRS resource sets configured in srs-ResourceSetToAddModList for DCI format 0_1).

[0085]

[0097] In some embodiments, a first PUSCH transmission and a second PUSCH transmission may be transmitted simultaneously (e.g., at least partially overlapping in the time domain) within the same component carrier, at least partially based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially based on the fact that one of the SRS resource sets is not a subset of the other SRS resource set. In the above example, if the first PUSCH transmission and the second PUSCH transmission are associated with SRS resource sets IDx and IDy, or SRS resource sets IDz and IDy, then the first PUSCH transmission and the second PUSCH transmission may be transmitted simultaneously. Alternatively, if the first PUSCH transmission and the second PUSCH transmission are associated with SRS resource sets IDx and IDz, then the first PUSCH transmission and the second PUSCH transmission may not be transmitted simultaneously. This condition may be required for simultaneous DG and DG transmissions, DG and Type 2 CG transmissions, Type 2 CG and Type 2 CG transmissions, DG and Type 1 CG transmissions, and Type 2 CG and Type 1 CG transmissions. If a DG or Type 2 CG transmission is scheduled by a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value, the DG or Type 2 CG transmission may overlap with a Type 1 CG transmission if the above condition is met. Additional details regarding these features are described in relation to Figure 8.

[0086]

[0098] As stated above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0087]

[0099] FIG. 6 is a diagram showing examples 600 and 605 of time-domain overlapping PUSCH transmissions according to the present disclosure. The first SRS resource set associated with the SRS resource set ID x can be scheduled by DCI having DCI format 0_1, and can be associated with the first CORESET pool index value (CORESET pool index value 0). The second SRS resource set associated with the SRS resource set ID y can be scheduled by DCI having DCI format 0_1, and can be associated with the second CORESET pool index value (CORESET pool index value 1), where x < y. The third SRS resource set associated with the SRS resource ID z can be scheduled by DCI having DCI format 0_1, and can be associated with the first CORESET pool index value. The fourth SRS resource associated with the SRS resource ID t can be scheduled by DCI having DCI format 0_1, and can be associated with the second CORESET pool index value, where z < t. As shown in example 600, PUSCH1 and PUSCH2 can be transmitted simultaneously (e.g., at least partially overlapping in the time domain) based at least in part on PUSCH1 being associated with the SRS resource ID x and PUSCH2 being a type 1 CG transmission associated with the SRS resource ID y or t. Alternatively, PUSCH1 and PUSCH2 may not be transmitted simultaneously based at least in part on PUSCH1 being associated with the SRS resource ID x and PUSCH2 being associated with the SRS resource set ID z.

[0088]

[0100] As described above, FIG. 6 is provided as an example. Other examples may be different from those described with respect to FIG. 6.

[0089]

[0101] FIG. 7 is a diagram showing an example 700 of time-domain overlapping PUSCH transmission according to the present disclosure. A first SRS resource set 705 associated with an SRS resource set ID x can be scheduled by DCI having DCI format 0_1, can be associated with a first CORESET pool index value (CORESET pool index value 0), and a second SRS resource set 710 associated with an SRS resource set ID y can be scheduled by DCI having DCI format 0_1, can be associated with a second CORESET pool index value (CORESET pool index value 1), where x < y. A third SRS resource set 715 associated with an SRS resource ID z can be scheduled by DCI having DCI format 0_2 and can be associated with the first CORESET pool index value. As shown in example 720, DCI having DCI format 0_2 and associated with the second CORESET pool index value can schedule PUSCH1 associated with an SRS resource set ID z, and DCI having DCI format 0_1 and associated with the second CORESET pool index value can schedule PUSCH2 associated with an SRS resource ID y. In this case, for example, since the SRS resource set for PUSCH1 and the SRS resource set for PUSCH2 are associated with different CORESET pool index values, PUSCH1 and PUSCH2 can be transmitted simultaneously. As shown in example 725, DCI having DCI format 0_2 and associated with the second CORESET pool index value can schedule PUSCH1 associated with an SRS resource set ID z, and DCI having DCI format 0_1 and associated with the first CORESET pool index value can schedule PUSCH2 associated with an SRS resource ID x.In this case, for example, the SRS resource set for PUSCH1 and the SRS resource set for PUSCH2 are associated with the same CORESET pool index value, and the SRS resource set for PUSCH2 is a subset of the SRS resource set for PUSCH1, so PUSCH1 and PUSCH2 may not be sent at the same time. As shown in Example 730, a DCI having DCI format 0_2 and associated with a second CORESET pool index value may schedule PUSCH1 associated with SRS resource set IDz, and a DCI having DCI format 0_1 ​​and associated with a first CORESET pool index value may schedule PUSCH2 associated with SRS resource IDz. In this case, for example, PUSCH1 and PUSCH2 are associated with the same SRS resource set and the same CORESET pool index value, so PUSCH1 and PUSCH2 may not be sent at the same time.

[0090]

[0102] As stated above, Figure 7 is provided as an example. Other examples may differ from those described in relation to Figure 7.

[0091]

[0103] Figure 8 shows examples 800, 805, 810, and 815 of time-domain overlapping PUSCH transmissions according to the present disclosure. As shown in Example 800, a DCI having DCI format 0_1 ​​and associated with a first CORESET pool index value (CORESET pool index value 0) may schedule a PUSCH1 associated with SRS resource ID x and the first CORESET pool index value. For example, since the SRS resource set for PUSCH1 and the SRS resource set for PUSCH2 are associated with different CORESET pool index values, simultaneous transmission of PUSCH2 (type 1 CG) associated with SRS resource ID y and a second CORESET pool index value (CORESET pool index value 1) may be permitted. As shown in Example 805, a DCI having DCI format 0_2 and associated with a first or second CORESET pool index value may schedule a PUSCH1 associated with SRS resource ID z and the first CORESET pool index value. For example, if the SRS resource set for PUSCH1 and the SRS resource set for PUSCH2 are associated with different CORESET pool index values, simultaneous transmission of PUSCH2 (Type 1 CG) associated with SRS resource IDy and the second CORESET pool index value may be permitted. As shown in Example 810, a DCI having DCI format 0_1 ​​and associated with the first CORESET pool index value may schedule PUSCH1 associated with SRS resource IDx and the first CORESET pool index value. For example, if the SRS resource set for PUSCH1 and the SRS resource set for PUSCH2 are associated with the same CORESET pool index value, and the SRS resource set for PUSCH2 is a subset of the SRS resource set for PUSCH1, simultaneous transmission of PUSCH2 (Type 1 CG) associated with SRS resource IDz and the first CORESET pool index value may not be permitted.As shown in Example 815, a DCI having DCI format 0_2 and associated with a first or second CORESET pool index value may schedule a PUSCH1 associated with SRS resource ID z and the first CORESET pool index value. For example, simultaneous transmission of a PUSCH2 (type 1 CG) associated with SRS resource ID x and the first CORESET pool index value may not be permitted, since the SRS resource set for PUSCH1 and the SRS resource set for PUSCH2 are associated with the same CORESET pool index value, and the SRS resource set for PUSCH2 is a subset of the SRS resource set for PUSCH1.

[0092]

[0104] As stated above, Figure 8 is provided as an example. Other examples may differ from those described with respect to Figure 8.

[0093]

[0105] Figure 9 shows an exemplary process 900 performed by, for example, a UE according to the present disclosure. The exemplary process 900 is an example in which a UE (e.g., UE120) performs an operation associated with SRS resource set configuration.

[0094]

[0106] As shown in Figure 9, in some embodiments, process 900 may include obtaining configuration information (block 910) indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. For example, as described above, a UE (e.g., using the receiving component 1102 and / or communication manager 1106 shown in Figure 11) may obtain configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format.

[0095]

[0107] As further shown in Figure 9, in some embodiments, process 900 may include identifying whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value (block 920). For example, (using, for example, the communications manager 1106 shown in Figure 11) the UE may identify, as described above, whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value.

[0096]

[0108] As further shown in Figure 9, in some embodiments, process 900 may include selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format (block 930). For example, (using, for example, the transmitting component 1104 and / or the communication manager 1106 shown in Figure 11) the UE may selectively transmit a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format, as described above.

[0097]

[0109] Process 900 may include additional embodiments, such as any single embodiment or any combination of embodiments, which are described below and / or in relation to one or more other processes described elsewhere in this specification.

[0098]

[0110] In the first embodiment, the first DCI format is DCI format 0_1 ​​or DCI format 0_2, and the second DCI format is the other of DCI format 0_1 ​​or DCI format 0_2.

[0099]

[0111] In the second aspect, identifying whether a DCI having a second DCI format is comprised of a third SRS resource set or both a third SRS resource set and a fourth SRS resource set, either alone or in combination with the first aspect, includes identifying that a DCI having a second DCI format is comprised of both a third SRS resource set and a fourth SRS resource set.

[0100]

[0112] In the third embodiment, either alone or in combination with one or more of the first and second embodiments, the second PUSCH transmission is a Type 1 configured grant PUSCH transmission and consists of one of the first SRS resource set, the second SRS resource set, the third SRS resource set, or the fourth SRS resource set.

[0101]

[0113] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0102]

[0114] In the fifth aspect, selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, either alone or in combination with one or more of the first to fourth aspects, includes transmitting a first PUSCH transmission and a second PUSCH transmission on at least partly because the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and on at least partly because the SRS resource set associated with either the first or second PUSCH transmission is not a subset of the SRS resource set associated with the other of the first or second PUSCH transmission.

[0103]

[0115] In the sixth aspect, identifying whether a DCI having the second DCI format is composed of a third SRS resource set or both the third SRS resource set and the fourth SRS resource set, either alone or in combination with one or more of the first to fifth aspects, includes identifying that a DCI having the second DCI format is composed of only the third SRS resource set.

[0104]

[0116] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the process 900 includes determining that the UE does not receive a DCI having a second DCI format within the CORESET associated with a second CORESET pool index value.

[0105]

[0117] In the eighth aspect, a DCI having the second DCI format is received only within a CORESET associated with the first CORESET pool index value, either alone or in combination with one or more of the first to seventh aspects.

[0106]

[0118] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 900 includes deciding to refrain from sending a second PUSCH transmission that at least partially overlaps with a first PUSCH transmission, based at least partially on the fact that the first PUSCH transmission is associated with a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0107]

[0119] In the tenth aspect, selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, either alone or in combination with one or more of the first to ninth aspects, includes refraining from transmitting the second PUSCH transmission on at least partly the basis that the first PUSCH transmission is associated with a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value.

[0108]

[0120] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 900 determines to transmit a second PUSCH transmit at least in part on the basis that the second PUSCH transmit is scheduled by a DCI having a first DCI format within a CORESET associated with a second CORESET pool index value, and at least in part on the basis that the UE is scheduled to transmit a first PUSCH transmit by a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value.

[0109]

[0121] In the twelfth aspect, selectively transmitting a first PUSCH transmit and a second PUSCH transmit that at least partially overlap in the time domain within a component carrier, either alone or in combination with one or more of the first to eleventh aspects, includes transmitting the second PUSCH transmit at least partially on the basis that the second PUSCH transmit is scheduled by a DCI having a first DCI format in a CORESET associated with a second CORESET pool index value, and at least partially on the basis that the UE is scheduled to transmit the first PUSCH transmit by a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0110]

[0122] In the 13th aspect, either alone or in combination with one or more of the 1st to 12th aspects, the second PUSCH transmission is a Type 1 configured grant PUSCH transmission and consists of either the first SRS resource set, the second SRS resource set, or the third SRS resource set.

[0111]

[0123] In the 14th aspect, either alone or in combination with one or more of the 1st to 13th aspects, the second PUSCH transmission is a Type 1 configured grant PUSCH transmission and consists of a first SRS resource set or a second SRS resource set.

[0112]

[0124] In the 15th aspect, selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, either alone or in combination with one or more of the first to 14th aspects, includes transmitting a first PUSCH transmission and a second PUSCH transmission on at least partly because the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and on at least partly because the SRS resource set associated with either the first PUSCH transmission or the second PUSCH transmission is not a subset of the SRS resource set associated with the other of the first PUSCH transmission and the second PUSCH transmission.

[0113]

[0125] In the sixteenth aspect, configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value, either alone or in combination with one or more of the first to fifteenth aspects, includes configuration information for codebook-based PUSCH transmissions and non-codebook-based PUSCH transmissions.

[0114]

[0126] In the 17th aspect, either alone or in combination with one or more of the 1st to 16th aspects, a first SRS resource set is associated with a first CORESET pool index value, at least partially based on the fact that the first SRS resource set has an identifier having a value smaller than the identifier value associated with the second SRS resource set, and a second SRS resource set is associated with a second CORESET pool index value, at least partially based on the fact that the second SRS resource set has an identifier having a value larger than the identifier value associated with the first SRS resource set.

[0115]

[0127] In the 18th embodiment, either alone or in combination with one or more of the 1st to 17th embodiments, the first CORESET pool index value is CORESET pool index value 0, and the second CORESET pool index value is CORESET pool index value 1.

[0116]

[0128] Figure 9 shows an exemplary block of process 900, but in some embodiments, process 900 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than shown in Figure 9. Additionally or alternatively, two or more blocks of process 900 may be executed in parallel.

[0117]

[0129] Figure 10 shows an exemplary process 1000 performed by, for example, a network node, according to the present disclosure. The exemplary process 1000 is an example of a network node (e.g., network node 110) performing an operation associated with SRS resource set configuration.

[0118]

[0130] As shown in Figure 10, in some embodiments, process 1000 may include transmitting configuration information (block 1010) indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. For example, as described above, a network node (using, for example, the transmitting component 1204 and / or communication manager 1206 shown in Figure 12) may transmit configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format.

[0119]

[0131] As further shown in Figure 10, in some embodiments, process 1000 may include transmitting a DCI having a second DCI format, which consists of either a third SRS resource set associated with a first CORESET pool index value, or both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value (block 1020). For example, a network node (using, for example, the transmitting component 1204 and / or the communication manager 1206 shown in Figure 12) may transmit a DCI having a second DCI format, which consists of either a third SRS resource set associated with a first CORESET pool index value, or both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value, as described above.

[0120]

[0132] As further shown in Figure 10, in some embodiments, process 1000 may include receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format (block 1030). For example, a network node (using, for example, the receiving component 1202 and / or communication manager 1206 shown in Figure 12) may receive a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format, as described above.

[0121]

[0133] Process 1000 may include additional embodiments, such as any single embodiment or any combination of embodiments, which are described below and / or in relation to one or more other processes described elsewhere in this specification.

[0122]

[0134] In the first embodiment, the first DCI format is DCI format 0_1 ​​or DCI format 0_2, and the second DCI format is the other of DCI format 0_1 ​​or DCI format 0_2.

[0123]

[0135] In the second embodiment, a DCI having the second DCI format, either alone or in combination with the first embodiment, comprises both a third SRS resource set and a fourth SRS resource set.

[0124]

[0136] In the third embodiment, either alone or in combination with one or more of the first and second embodiments, the second PUSCH transmission is a Type 1 configured grant PUSCH transmission and consists of one of the first SRS resource set, the second SRS resource set, the third SRS resource set, or the fourth SRS resource set.

[0125]

[0137] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0126]

[0138] In the fifth aspect, receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, either alone or in combination with one or more of the first to fourth aspects, includes receiving a first PUSCH transmission and a second PUSCH transmission, at least partially on the basis that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially on the basis that the SRS resource set associated with either the first or second PUSCH transmission is not a subset of the SRS resource set associated with the other of the first or second PUSCH transmission.

[0127]

[0139] In the sixth aspect, a DCI having the second DCI format, either alone or in combination with one or more of the first to fifth aspects, consists only of the third SRS resource set.

[0128]

[0140] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1000 includes sending an instruction not to send a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value.

[0129]

[0141] In the eighth aspect, a DCI having the second DCI format is transmitted only within a CORESET associated with a first CORESET pool index value, either alone or in combination with one or more of the first to seventh aspects.

[0130]

[0142] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1000 includes sending an instruction to send a second PUSCH transmission that at least partially overlaps with a first PUSCH transmission, based at least in part on the fact that a first PUSCH transmission is associated with a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0131]

[0143] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 1000 includes sending an instruction to send a second PUSCH transmission, at least partially based on the fact that the second PUSCH transmission is scheduled by a DCI having a first DCI format within a CORESET associated with a second CORESET pool index value, and at least partially based on the scheduling of the first PUSCH transmission by a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value.

[0132]

[0144] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the second push transmission is a type 1 configured grant push transmission and consists of either the first SRS resource set, the second SRS resource set, or the third SRS resource set.

[0133]

[0145] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0134]

[0146] In the 13th aspect, receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, either alone or in combination with one or more of the first to 12th aspects, includes receiving a first PUSCH transmission and a second PUSCH transmission, at least partially based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially based on the fact that the SRS resource sets associated with either the first or second PUSCH transmission are not a subset of the SRS resource sets associated with the other of the first or second PUSCH transmission.

[0135]

[0147] In the 14th aspect, configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value, either alone or in combination with one or more of the 1st to 13th aspects, includes configuration information for codebook-based PUSCH transmissions and non-codebook-based PUSCH transmissions.

[0136]

[0148] In the 15th aspect, either alone or in combination with one or more of the 1st to 14th aspects, a first SRS resource set is associated with a first CORESET pool index value, at least partially based on the fact that the first SRS resource set has an identifier having a value smaller than the identifier value associated with the second SRS resource set, and a second SRS resource set is associated with a second CORESET pool index value, at least partially based on the fact that the second SRS resource set has an identifier having a value larger than the identifier value associated with the first SRS resource set.

[0137]

[0149] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the first CORESET pool index value is CORESET pool index value 0, and the second CORESET pool index value is CORESET pool index value 1.

[0138]

[0150] Figure 10 shows an exemplary block of process 1000, but in some embodiments, process 1000 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than shown in Figure 10. Additionally or alternatively, two or more blocks of process 1000 may be executed in parallel.

[0139]

[0151] Figure 11 is a diagram of an exemplary apparatus 1100 for wireless communication according to the present disclosure. The apparatus 1100 may be a UE, or a UE may include the apparatus 1100. In some embodiments, the apparatus 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communications manager 1106, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some embodiments, the communications manager 1106 is the communications manager 140 described in relation to Figure 1. As shown, the apparatus 1100 may use the receiving component 1102 and the transmitting component 1104 to communicate with a UE or another apparatus 1108, such as a network node (CU, DU, RU, or base station).

[0140]

[0152] In some embodiments, the device 1100 may be configured to perform one or more operations described herein in relation to Figures 5 to 9. Additionally or alternatively, the device 1100 may be configured to perform one or more processes described herein, such as process 900 in Figure 9. In some embodiments, the device 1100 and / or one or more components shown in Figure 11 may include one or more components of the UE described in relation to Figure 2. Additionally or alternatively, one or more components shown in Figure 11 may be implemented within one or more components described in relation to Figure 2. Additionally or alternatively, one or more components of a set of components may be implemented as software, at least partially stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code, executable by a processor, stored in a controller or non-temporary computer-readable medium, that perform the function or operation of the component.

[0141]

[0153] The receiving component 1102 may receive communications from the device 1108, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some embodiments, the receiving component 1102 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and provide the processed signals to one or more other components of the device 1100. In some embodiments, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the UE described in relation to Figure 2.

[0142]

[0154] The transmitting component 1104 can transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1108. In some embodiments, one or more other components of the device 1100 can generate communications and provide the generated communications to the transmitting component 1104 for transmission to the device 1108. In some embodiments, the transmitting component 1104 can perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1108. In some embodiments, the transmitting component 1104 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the UE as described in relation to Figure 2. In some embodiments, the transmitting component 1104 may be co-located with the receiving component 1102 in the transceiver.

[0143]

[0155] The communication manager 1106 may support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 may receive information associated with configuring the receiving component 1102 to receive communications and / or the transmitting component 1104 to transmit communications. Additionally or alternatively, the communication manager 1106 may generate control information and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 in order to control the receiving and / or transmitting of communications.

[0144]

[0156] The receiving component 1102 may obtain configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. The communication manager 1106 may determine whether a DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. The transmitting component 1104 may selectively transmit a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of a DCI having a first DCI format or a DCI having a second DCI format.

[0145]

[0157] The communication manager 1106 may determine that the UE does not receive a DCI having a second DCI format in the CORESET associated with the second CORESET pool index value. The communication manager 1106 may decide to refrain from sending a second PUSCH transmission that at least partially overlaps the first PUSCH transmission, at least on the basis that the first PUSCH transmission is associated with a DCI having a second DCI format in the CORESET associated with the second CORESET pool index value. The communication manager 1106 may decide to send a second PUSCH transmission, at least on the basis that the second PUSCH transmission is scheduled by a DCI having a first DCI format in the CORESET associated with the second CORESET pool index value, and at least on the basis that the UE is scheduled to send a first PUSCH transmission by a DCI having a second DCI format in the CORESET associated with the second CORESET pool index value.

[0146]

[0158] The number and arrangement of components shown in Figure 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently from those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Additionally or alternatively, the set of components (one or more) shown in Figure 11 may perform one or more functions that are described as being performed by another set of components shown in Figure 11.

[0147]

[0159] Figure 12 is a diagram of an exemplary device 1200 for wireless communication according to the present disclosure. The device 1200 can be a network node, or a network node may include the device 1200. In some embodiments, the device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communications manager 1206, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some embodiments, the communications manager 1206 is the communications manager 150 described in relation to Figure 1. As shown, the device 1200 may use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1208, such as a UE or a network node (CU, DU, RU, or base station, etc.).

[0148]

[0160] In some embodiments, the device 1200 may be configured to perform one or more operations described herein in relation to Figures 5 to 9. Additionally or alternatively, the device 1200 may be configured to perform one or more processes described herein, such as process 1000 in Figure 10, or a combination thereof. In some embodiments, the device 1200 and / or one or more components shown in Figure 12 may include one or more components of a network node described in relation to Figure 2. Additionally or alternatively, one or more components shown in Figure 12 may be implemented within one or more components described in relation to Figure 2. Additionally or alternatively, one or more components of a set of components may be implemented as software, at least partially stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code, executable by a processor, that perform the function or operation of the component, and stored in a controller or non-temporary computer-readable medium.

[0149]

[0161] The receiving component 1202 may receive communications from the device 1208, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some embodiments, the receiving component 1202 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and provide the processed signals to one or more other components of the device 1200. In some embodiments, the receiving component 1202 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the network nodes described in relation to Figure 2. In some embodiments, the receiving component 1202 and / or the transmitting component 1204 may include, or may be included in, a network interface. The network interface may be configured to acquire and / or output signals for the device 1200 via one or more communication links, such as a backhaul link, a midhaul link, and / or a fronthaul link.

[0150]

[0162] The transmitting component 1204 can transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1208. In some embodiments, one or more other components of the device 1200 can generate communications and provide the transmitted component 1204 with the generated communications for transmission to the device 1208. In some embodiments, the transmitting component 1204 can perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1208. In some embodiments, the transmitting component 1204 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the network nodes described in relation to Figure 2. In some embodiments, the transmitting component 1204 may be located alongside the receiving component 1202 in the transceiver.

[0151]

[0163] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the receiving component 1202 to receive communications and / or the transmitting component 1204 to transmit communications. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 in order to control the receiving and / or transmitting of communications.

[0152]

[0164] The transmitting component 1204 may transmit configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value for a DCI having a first DCI format. The transmitting component 1204 may transmit a DCI having a second DCI format, which consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value. The receiving component 1202 may receive a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within the component carrier, according to at least one of the DCI having a first DCI format or a DCI having a second DCI format.

[0153]

[0165] The transmitting component 1204 may transmit an instruction not to transmit a DCI having a second DCI format within the CORESET associated with the second CORESET pool index value.

[0154]

[0166] The transmitting component 1204 may transmit an instruction to transmit a second PUSCH transmit that at least partially overlaps with the first PUSCH transmit, based at least partially on the fact that the first PUSCH transmit is associated with a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0155]

[0167] The transmitting component 1204 may transmit an instruction to transmit a second PUSCH transmit, at least partially based on the fact that the second PUSCH transmit is scheduled by a DCI having a first DCI format within a CORESET associated with a second CORESET pool index value, and at least partially based on the scheduling of the first PUSCH transmit by a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value.

[0156]

[0168] The number and arrangement of components shown in Figure 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently from those shown in Figure 12. Furthermore, two or more components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple distributed components. Additionally or alternatively, the set of components (one or more) shown in Figure 12 may perform one or more functions that are described as being performed by another set of components shown in Figure 12.

[0157]

[0169] The following provides an overview of some aspects of this disclosure.

[0158]

[0170] Embodiment 1: A method for wireless communication performed by a user device (UE), comprising: obtaining configuration information for downlink control information (DCI) having a first DCI format, indicating a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value; identifying whether the DCI having a second DCI format consists only of a third SRS resource set associated with a first CORESET pool index value, or consists of both a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value; and selectively transmitting a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having a first DCI format or the DCI having a second DCI format.

[0159]

[0171] Embodiment 2: The method according to Embodiment 1, wherein the first DCI format is DCI format 0_1 ​​or DCI format 0_2, and the second DCI format is the other of DCI format 0_1 ​​or DCI format 0_2.

[0160]

[0172] Embodiment 3: The method according to Embodiment 1 or 2, wherein identifying whether a DCI having a second DCI format is composed of a third SRS resource set or both a third SRS resource set and a fourth SRS resource set includes identifying that a DCI having a second DCI format is composed of both a third SRS resource set and a fourth SRS resource set.

[0161]

[0173] Embodiment 4: The method according to Embodiment 3, wherein the second push transmission is a type 1 configured grant push transmission and consists of one of the first SRS resource set, the second SRS resource set, the third SRS resource set, or the fourth SRS resource set.

[0162]

[0174] Embodiment 5: The method according to Embodiment 3, wherein the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0163]

[0175] Embodiment 6: The method of Embodiment 3, wherein selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier is at least partially based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially based on the fact that the SRS resource sets associated with either the first PUSCH transmission or the second PUSCH transmission are not a subset of the SRS resource sets associated with the other of the first PUSCH transmission and the second PUSCH transmission.

[0164]

[0176] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein identifying whether a DCI having a second DCI format is composed of a third SRS resource set or both a third SRS resource set and a fourth SRS resource set includes identifying that a DCI having a second DCI format is composed of only a third SRS resource set.

[0165]

[0177] Embodiment 8: The method according to Embodiment 7, further comprising determining that the UE does not receive a DCI having a second DCI format within the CORESET associated with a second CORESET pool index value.

[0166]

[0178] Embodiment 9: The method according to Embodiment 8, wherein the DCI having a second DCI format is received only within a CORESET associated with a first CORESET pool index value.

[0167]

[0179] Embodiment 10: The method of Embodiment 7, further comprising deciding to refrain from sending a second PUSCH transmission that at least partially overlaps with a first PUSCH transmission, based at least in part on the fact that a first PUSCH transmission is associated with a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0168]

[0180] Embodiment 11: The method of Embodiment 10, wherein selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier includes refraining from transmitting the second PUSCH transmission on at least partly the basis that the first PUSCH transmission is associated with a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0169]

[0181] Embodiment 12: The method according to Embodiment 7, further comprising determining to send a second PUSCH transmission based at least in part on the fact that a second PUSCH transmission is scheduled by a DCI having a first DCI format in a CORESET associated with a second CORESET pool index value, and at least in part on the fact that a UE is scheduled to send a first PUSCH transmission by a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0170]

[0182] Embodiment 13: The method of Embodiment 12, wherein selectively transmitting a first PUSCH transmit and a second PUSCH transmit that at least partially overlap in the time domain within a component carrier includes transmitting the second PUSCH transmit at least partially on the basis that the second PUSCH transmit is scheduled by a DCI having a first DCI format in a CORESET associated with a second CORESET pool index value, and the UE is scheduled to transmit the first PUSCH transmit by a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0171]

[0183] Embodiment 14: The method according to Embodiment 7, wherein the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set, a second SRS resource set, or a third SRS resource set.

[0172]

[0184] Embodiment 15: The method according to Embodiment 7, wherein the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0173]

[0185] Embodiment 16: The method of Embodiment 7, wherein selectively transmitting a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier is based at least partially on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially on the fact that the SRS resource sets associated with either the first PUSCH transmission or the second PUSCH transmission are not a subset of the SRS resource sets associated with the other of the first PUSCH transmission and the second PUSCH transmission.

[0174]

[0186] Embodiment 17: The method according to any one of Embodiments 1 to 16, wherein the configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value includes configuration information for codebook-based PUSCH transmissions and non-codebook-based PUSCH transmissions.

[0175]

[0187] Embodiment 18: The method according to any one of embodiments 1 to 17, wherein a first SRS resource set is associated with a first CORESET pool index value, at least in part on the basis that the first SRS resource set has an identifier having a value smaller than the identifier value associated with the second SRS resource set, and a second SRS resource set is associated with a second CORESET pool index value, at least in part on the basis that the second SRS resource set has an identifier having a value larger than the identifier value associated with the first SRS resource set.

[0176]

[0188] Embodiment 19: The method according to any one of Embodiments 1 to 18, wherein the first CORESET pool index value is CORESET pool index value 0, and the second CORESET pool index value is CORESET pool index value 1.

[0177]

[0189] Embodiment 20: A method for wireless communication performed by a network node, comprising: transmitting configuration information indicating a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value for downlink control information (DCI) having a first DCI format; transmitting a DCI having a second DCI format, which consists only of a third SRS resource set associated with a first CORESET pool index value, or both of a third SRS resource set associated with a first CORESET pool index value and a fourth SRS resource set associated with a second CORESET pool index value; and receiving a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having a first DCI format or the DCI having a second DCI format.

[0178]

[0190] Embodiment 21: The method according to Embodiment 20, wherein the first DCI format is DCI format 0_1 ​​or DCI format 0_2, and the second DCI format is the other of DCI format 0_1 ​​or DCI format 0_2.

[0179]

[0191] Embodiment 22: The method according to Embodiment 20 or 21, wherein the DCI having the second DCI format is comprised of both a third SRS resource set and a fourth SRS resource set.

[0180]

[0192] Embodiment 23: The method according to Embodiment 22, wherein the second push transmission is a type 1 configured grant push transmission and consists of one of the first SRS resource set, the second SRS resource set, the third SRS resource set, or the fourth SRS resource set.

[0181]

[0193] Embodiment 24: The method according to Embodiment 22, wherein the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0182]

[0194] Embodiment 25: The method of Embodiment 22, wherein receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier is at least partially based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially based on the fact that the SRS resource set associated with either the first PUSCH transmission or the second PUSCH transmission is not a subset of the SRS resource set associated with the other of the first PUSCH transmission and the second PUSCH transmission.

[0183]

[0195] Embodiment 26: The method according to any one of Embodiments 20 to 25, wherein the DCI having a second DCI format consists only of a third SRS resource set.

[0184]

[0196] Embodiment 27: The method according to Embodiment 26, further comprising sending an instruction not to send a DCI having a second DCI format within a CORESET associated with a second CORESET pool index value.

[0185]

[0197] Embodiment 28: The method according to Embodiment 27, wherein a DCI having a second DCI format is transmitted only within a CORESET associated with a first CORESET pool index value.

[0186]

[0198] Embodiment 29: The method of Embodiment 26, further comprising sending an instruction to send a second PUSCH transmission that at least partially overlaps with the first PUSCH transmission, based at least in part on the fact that the first PUSCH transmission is associated with a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0187]

[0199] Embodiment 30: The method of Embodiment 26, further comprising sending an instruction to send a second PUSCH transmission, at least in part on the fact that a second PUSCH transmission is scheduled by a DCI having a first DCI format in a CORESET associated with a second CORESET pool index value, and at least in part on the scheduling of the first PUSCH transmission by a DCI having a second DCI format in a CORESET associated with a second CORESET pool index value.

[0188]

[0200] Embodiment 31: The method according to Embodiment 26, wherein the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set, a second SRS resource set, or a third SRS resource set.

[0189]

[0201] Embodiment 32: The method according to Embodiment 26, wherein the second push transmission is a type 1 configured grant push transmission and consists of a first SRS resource set or a second SRS resource set.

[0190]

[0202] Embodiment 33: The method of Embodiment 26, wherein receiving a first PUSCH transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier is at least partially based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and at least partially based on the fact that the SRS resource set associated with either the first PUSCH transmission or the second PUSCH transmission is not a subset of the SRS resource set associated with the other of the first PUSCH transmission and the second PUSCH transmission.

[0191]

[0203] Embodiment 34: The method according to any one of Embodiments 20 to 33, wherein the configuration information indicating a first SRS resource set associated with a first CORESET pool index value and a second SRS resource set associated with a second CORESET pool index value includes configuration information for codebook-based PUSCH transmissions and non-codebook-based PUSCH transmissions.

[0192]

[0204] Embodiment 35: The method according to any one of embodiments 20 to 34, wherein a first SRS resource set is associated with a first CORESET pool index value, at least in part on the basis that the first SRS resource set has an identifier having a value smaller than the identifier value associated with the second SRS resource set, and a second SRS resource set is associated with a second CORESET pool index value, at least in part on the basis that the second SRS resource set has an identifier having a value larger than the identifier value associated with the first SRS resource set.

[0193]

[0205] Embodiment 36: The method according to any one of Embodiments 20 to 35, wherein the first CORESET pool index value is CORESET pool index value 0, and the second CORESET pool index value is CORESET pool index value 1.

[0194]

[0206] Embodiment 37: A device for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory that are executable by the processor and cause the device to implement one or more of the embodiments 1 to 36.

[0195]

[0207] Embodiment 38: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein one or more processors are configured to implement one or more methods of Embodiments 1 to 36.

[0196]

[0208] Embodiment 39: An apparatus for wireless communication, comprising at least one means for carrying out one or more methods from Embodiments 1 to 36.

[0197]

[0209] Embodiment 40: A non-temporary computer-readable medium storing code for wireless communication, wherein the code comprises instructions that are executable by a processor and perform one or more of the methods of Embodiments 1 to 36.

[0198]

[0210] Embodiment 41: A non-temporary computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods of Embodiments 1 to 36.

[0199]

[0211] The foregoing disclosures are illustrative and explanatory, but are not intended to be exhaustive or to limit the forms to those disclosed. Modified and altered forms may be added in light of the foregoing disclosures or obtained from the practice of the forms.

[0200]

[0212] Where used herein, the term “Components” is intended to be interpreted broadly as hardware and / or combinations of hardware and software. “Software” is intended to be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, among many other examples. Where used herein, “Processor” is implemented in hardware and / or combinations of hardware and software. It will become clear that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to these embodiments. Therefore, as those skilled in the art will understand, software and hardware can be designed to perform the system and / or method based at least in part on the description herein; the operation and behavior of the system and / or method are described herein without reference to specific software code.

[0201]

[0213] As used herein, “meeting the threshold” may mean, depending on the context, that a value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold.

[0202]

[0214] Even if certain combinations of features are enumerated in the claims and / or disclosed herein, those combinations are not intended to limit the disclosure of various embodiments. Many of these features can be combined in ways not specifically enumerated in the claims and / or disclosed herein. The disclosure of various embodiments includes each dependent claim in combination with any other claim in the set of claims. Where used herein, the phrase "at least one of" the list of items refers to any combination of those items, including a single member. As an example, “at least one of a, b, or c” is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other sequence of a, b, and c).

[0203]

[0215] None of the elements, actions, or commands used herein should be construed as essential or mandatory unless expressly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items with respect to the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” When only one item is intended, the phrase “only one” or similar words are used. Also, as used herein, terms such as “has,” “have,” and “having” are intended to be open-ended terms that do not limit the elements they modify (for example, an element that “has” A may also have B). Furthermore, unless otherwise specified, the phrase "based on" is intended to mean "at least partially based on." Also, as used herein, the term "or" is intended to be inclusive when used in a series, and may be used interchangeably with "and / or" unless otherwise specified (for example, when used in combination with "either" or "only one of").

Claims

1. A device for wireless communication in user equipment (UE), One or more memory devices, The system comprises one or more processors coupled to the one or more memory, and the one or more processors are connected to the UE. With respect to downlink control information (DCI) having a first DCI format, configuration information is obtained that shows a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value. To identify whether a DCI having a second DCI format consists only of a third SRS resource set associated with the first CORESET pool index value, or consists of both the third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value, A device configured to selectively transmit a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having the first DCI format or the DCI having the second DCI format.

2. The apparatus according to claim 1, wherein the first DCI format is DCI format 0_1 ​​or DCI format 0_2, and the second DCI format is the other of DCI format 0_1 ​​or DCI format 0_2.

3. The apparatus according to claim 1, wherein the one or more processors are configured to cause the UE to identify that the DCI having the second DCI format is composed of the third SRS resource set or of both the third SRS resource set and the fourth SRS resource set, in order to cause the UE to identify that the DCI having the second DCI format is composed of both the third SRS resource set and the fourth SRS resource set.

4. The apparatus according to claim 3, wherein the second PUSCH transmission is a Type 1 configuration grant PUSCH transmission and is composed of any of the first SRS resource set, the second SRS resource set, the third SRS resource set, or the fourth SRS resource set.

5. The apparatus according to claim 3, wherein the second PUSCH transmission is a Type 1 configuration grant PUSCH transmission and is composed of the first SRS resource set or the second SRS resource set.

6. The apparatus according to claim 3, wherein the one or more processors are configured to cause the UE to transmit the first PUSCH transmit and the second PUSCH transmit, at least partially on the basis that the first PUSCH transmit and the second PUSCH transmit are associated with different SRS resource sets, and at least partially on the basis that the SRS resource set associated with the first PUSCH transmit or the second PUSCH transmit is not a subset of the SRS resource set associated with the other of the first PUSCH transmit and the second PUSCH transmit, in order to cause the UE to selectively transmit the first PUSCH transmit and the second PUSCH transmit which at least partially overlap in the time domain within the component carrier.

7. The apparatus according to claim 1, wherein the one or more processors are configured to cause the UE to identify that the DCI having the second DCI format is composed of the third SRS resource set, or is composed of both the third SRS resource set and the fourth SRS resource set, and to cause the UE to identify that the DCI having the second DCI format is composed of only the third SRS resource set.

8. The apparatus according to claim 7, wherein the one or more processors are further configured to cause the UE to determine that the UE does not receive the DCI having the second DCI format in a CORESET associated with the second CORESET pool index value.

9. The apparatus according to claim 8, wherein the DCI having the second DCI format is received only within a CORESET associated with the first CORESET pool index value.

10. The apparatus according to claim 7, wherein the one or more processors are further configured to cause the UE to decide to refrain from transmitting a second PUSCH transmission that at least partially overlaps the first PUSCH transmission, based at least partially on the fact that the first PUSCH transmission is associated with the DCI having the second DCI format in a CORESET associated with the second CORESET pool index value.

11. The apparatus according to claim 10, wherein the one or more processors are configured to cause the UE to selectively transmit the first PUSCH transmit and the second PUSCH transmit which at least partially overlap in the time domain within the component carrier, by causing the UE to refrain from transmitting the second PUSCH transmit at least on the basis that the first PUSCH transmit is associated with the DCI having the second DCI format in the CORESET which is associated with the second CORESET pool index value.

12. The apparatus according to claim 7, wherein the one or more processors are further configured to cause the UE to decide to transmit the second PUSCH transmit at least in part on the fact that the second PUSCH transmit is scheduled by the DCI having the first DCI format in a CORESET associated with the second CORESET pool index value, and at least in part on the fact that the UE is scheduled to transmit the first PUSCH transmit by the DCI having the second DCI format in a CORESET associated with the second CORESET pool index value.

13. The apparatus according to claim 12, wherein the one or more processors are configured to cause the UE to selectively transmit the first PUSCH transmit and the second PUSCH transmit which at least partially overlap in the time domain within the component carrier, at least partially on the basis that the second PUSCH transmit is scheduled by the DCI having the first DCI format in the CORESET associated with the second CORESET pool index value, and at least partially on the basis that the UE is scheduled to transmit the first PUSCH transmit by the DCI having the second DCI format in the CORESET associated with the second CORESET pool index value.

14. The apparatus according to claim 7, wherein the second PUSCH transmission is a Type 1 configuration grant PUSCH transmission and is composed of the first SRS resource set, the second SRS resource set, or the third SRS resource set.

15. The apparatus according to claim 7, wherein the second PUSCH transmission is a Type 1 configuration grant PUSCH transmission and is composed of the first SRS resource set or the second SRS resource set.

16. The apparatus according to claim 7, wherein the one or more processors are configured to cause the UE to transmit the first PUSCH transmit and the second PUSCH transmit, at least partially on the basis that the first PUSCH transmit and the second PUSCH transmit are associated with different SRS resource sets, and at least partially on the basis that the SRS resource set associated with the first PUSCH transmit or the second PUSCH transmit is not a subset of the SRS resource set associated with the other of the first PUSCH transmit and the second PUSCH transmit, in order to cause the UE to selectively transmit the first PUSCH transmit and the second PUSCH transmit which at least partially overlap in the time domain within the component carrier.

17. The apparatus according to claim 1, wherein the configuration information indicating the first SRS resource set associated with the first CORESET pool index value and the second SRS resource set associated with the second CORESET pool index value includes configuration information for codebook-based PUSCH transmission and non-codebook-based PUSCH transmission.

18. The apparatus according to claim 1, wherein the first SRS resource set is associated with the first CORESET pool index value, at least in part on the basis that the first SRS resource set has an identifier having a value smaller than the value of the identifier associated with the second SRS resource set, and the second SRS resource set is associated with the second CORESET pool index value, at least in part on the basis that the second SRS resource set has an identifier having a value larger than the value of the identifier associated with the first SRS resource set.

19. The apparatus according to claim 1, wherein the first CORESET pool index value is CORESET pool index value 0, and the second CORESET pool index value is CORESET pool index value 1.

20. A device for wireless communication at a network node, One or more memory devices, The system comprises one or more processors coupled to one or more of the aforementioned memories, and the one or more processors are connected to the network node. With respect to downlink control information (DCI) having a first DCI format, configuration information is transmitted indicating a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value. To transmit a DCI having a second DCI format, which consists only of a third SRS resource set associated with the first CORESET pool index value, or both the third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value. A device configured to receive a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having the first DCI format or the DCI having the second DCI format.

21. The apparatus according to claim 20, wherein the first DCI format is DCI format 0_1 ​​or DCI format 0_2, and the second DCI format is the other of DCI format 0_1 ​​or DCI format 0_2.

22. The apparatus according to claim 20, wherein the DCI having the second DCI format is comprised of both the third SRS resource set and the fourth SRS resource set.

23. The apparatus according to claim 22, wherein the second PUSCH transmission is a Type 1 configuration grant PUSCH transmission and is composed of any of the first SRS resource set, the second SRS resource set, the third SRS resource set, or the fourth SRS resource set.

24. The apparatus according to claim 22, wherein the second PUSCH transmission is a Type 1 configuration grant PUSCH transmission and is composed of the first SRS resource set or the second SRS resource set.

25. The apparatus according to claim 22, wherein the one or more processors are configured to cause the network node to receive the first PUSCH transmission and the second PUSCH transmission, which at least partially overlap in the time domain within the component carrier, on at least partly based on the fact that the first PUSCH transmission and the second PUSCH transmission are associated with different SRS resource sets, and on at least partly based on the fact that the SRS resource set associated with the first PUSCH transmission or the second PUSCH transmission is not a subset of the SRS resource set associated with the other of the first PUSCH transmission and the second PUSCH transmission.

26. The apparatus according to claim 20, wherein the DCI having the second DCI format is composed solely of the third SRS resource set.

27. The apparatus according to claim 26, wherein the one or more processors are further configured to cause the network node to send an instruction not to send the DCI having the second DCI format within the CORESET associated with the second CORESET pool index value.

28. The apparatus according to claim 27, wherein the DCI having the second DCI format is transmitted only within a CORESET associated with the first CORESET pool index value.

29. A method of wireless communication performed by user equipment (UE), With respect to downlink control information (DCI) having a first DCI format, configuration information is obtained that indicates a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value. Identifying whether a DCI having a second DCI format consists only of a third SRS resource set associated with the first CORESET pool index value, or consists of both the third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value, Selectively transmitting a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having the first DCI format or the DCI having the second DCI format, Methods that include...

30. A method of wireless communication carried out by network nodes, With respect to downlink control information (DCI) having a first DCI format, configuration information is transmitted indicating a first sounding reference signal (SRS) resource set associated with a first control resource set (CORESET) pool index value and a second SRS resource set associated with a second CORESET pool index value. Sending a DCI having a second DCI format, which consists only of a third SRS resource set associated with the first CORESET pool index value, or consists of both the third SRS resource set associated with the first CORESET pool index value and a fourth SRS resource set associated with the second CORESET pool index value. Receiving a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain within a component carrier, according to at least one of the DCI having the first DCI format or the DCI having the second DCI format, Methods that include...

Images