Downlink control information (DCI) and multiple DCI transmission modes

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive configuration information from a network node indicating a configuration of at least two sounding reference signal resource sets. The UE may receive one or more downlink control information (DCI) communications associated with the one or more uplink communications. The UE may receive, from the network node, an indication of whether the one or more DCI communications are associated with one or both of a single DCI (sDCI) mode or a plurality of DCI (mDCI) modes, wherein the indication is based at least in part on the configuration information. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Non-Provisional Patent Application No. 17 / 936,704, filed on September 29, 2022, entitled “DOWNLINK CONTROLINFORMATION (DCI) FOR SINGLE DCI AND MULTIPLE DCI TRANSMISSION MODES” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for downlink control information (DCI) for single DCI transmission mode and multiple DCI transmission modes. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support 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 enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, 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 to better integrate with other open standards; and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: receiving configuration information indicating a configuration of at least two sounding reference signal (SRS) resource sets from a network node. The method may include: receiving one or more downlink control information (DCI) communications associated with one or more uplink communications. The method may include: receiving an indication from the network node whether the one or more DCI communications are associated with a single DCI (sDCI) mode or one or both of a multiple DCI (mDCI) mode, wherein the indication is based at least in part on the configuration information.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: sending configuration information indicating a configuration of at least two SRS resource sets to a UE. The method may include: sending one or more DCI communications associated with one or more uplink communications to the UE. The method may include: indicating to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information.

[0009] Some aspects described herein relate to a UE for wireless communication. The user equipment may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to: receive configuration information indicating the configuration of at least two SRS resource sets from a network node. The one or more processors may be configured to: receive one or more DCI communications associated with one or more uplink communications. The one or more processors may be configured to: receive from the network node an indication of whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information.

[0010] Some aspects described herein relate to a network node for wireless communications. The network node may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to: send configuration information indicating a configuration of at least two SRS resource sets to a UE. The one or more processors may be configured to: send one or more DCI communications associated with one or more uplink communications to the UE. The one or more processors may be configured to: indicate to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive configuration information indicating the configuration of at least two SRS resource sets from a network node. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive one or more DCI communications associated with one or more uplink communications. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive an indication from the network node as to whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to: send configuration information indicating the configuration of at least two SRS resource sets to a UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to: send one or more DCI communications associated with one or more uplink communications to the UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to: indicate to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving configuration information indicating a configuration of at least two SRS resource sets from a network node. The apparatus may include means for receiving one or more DCI communications associated with one or more uplink communications. The apparatus may include means for receiving an indication from the network node whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending configuration information indicating a configuration of at least two SRS resource sets to a UE. The apparatus may include a component for sending one or more DCI communications associated with one or more uplink communications to the UE. The apparatus may include a component for indicating to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The devices incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a sounding reference signal (SRS) resource set according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example associated with time division multiplexing physical uplink shared channel (PUSCH) transmission based on a single downlink control information (DCI) according to the present disclosure.

[0024] FIG. 6A to FIG. 6B is a diagram illustrating an example associated with an SRS resource set indicator field according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of performing transmission and reception point differentiation at a UE based at least in part on a control resource set pool index according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example associated with a time-domain overlapping PUSCH with multiple DCIs according to the present disclosure.

[0027] 9A to 9D is a diagram of examples associated with DCI for single DCI and multiple DCI transmission modes according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0031] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0033] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated 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.

[0034] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or 5G and beyond (e.g., 6G) RATs.

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. 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), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged 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). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between 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)).

[0036] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0037] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0038] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a 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 aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with the network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "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 aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

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

[0040] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0041] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0042] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a 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, an 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.

[0043] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0044] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0045] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0046] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0047] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

[0048] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in 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 applicable to those modified frequency ranges.

[0049] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive configuration information from a network node indicating a configuration of at least two sounding reference signal (SRS) resource sets; receive one or more downlink control information (DCI) communications associated with one or more uplink communications; and receive from the network node an indication of whether the one or more DCI communications are associated with one or both of a single DCI (sDCI) mode or a multiple DCI (mDCI) mode, wherein the indication is based at least in part on the configuration information. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0050] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send configuration information indicating a configuration of at least two SRS resource sets to a UE; send one or more DCI communications associated with one or more uplink communications to the UE; and indicate to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0051] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0052] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in 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 antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. 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 a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0053] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and 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 perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0054] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the 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) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information 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 determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0056] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0057] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports 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 pre-decoded 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 the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform operations described herein (eg, with reference to FIG. 9A to FIG. 13 ) any aspects of any of the methods described.

[0058] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform the functions described herein (e.g., reference 2 FIG. 9A to FIG. 13 ) or any aspects of any of the methods described in .

[0059] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0060] In some aspects, the UE 120 includes a component for receiving configuration information indicating a configuration of at least two SRS resource sets from a network node; a component for receiving one or more DCI communications associated with one or more uplink communications; and / or a component for receiving an indication from the network node whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information. The components for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0061] In some aspects, the network node 110 includes means for sending configuration information indicating a configuration of at least two SRS resource sets to a UE; means for sending one or more DCI communications associated with one or more uplink communications to the UE; and / or means for indicating to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information. Means for the network node 110 to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0062] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for 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.

[0063] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0064] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[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 decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. The 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), and the like.

[0066] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0067] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RTRIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0068] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0069] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 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 specific implementations, the CU 310 may be logically split 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 may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0070] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0071] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0072] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements 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 may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0073] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0074] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0075] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0076] Figure 4 is a diagram illustrating an example 400 of an SRS resource set according to the present disclosure.

[0077] The UE 120 may be configured with one or more SRS resource sets to allocate resources for SRS transmission by the UE 120. For example, the configuration for the SRS resource set may be indicated in an RRC message (e.g., an RRC configuration message or an RRC reconfiguration message). As shown by reference numeral 405, the SRS resource set may include one or more resources (e.g., shown as SRS resources), which may include time resources and / or frequency resources (e.g., time slots, symbols, resource blocks, and / or periodicity of time resources).

[0078] As indicated by reference numeral 410, the SRS resources may include one or more antenna ports over which the SRS is to be sent (e.g., in time-frequency resources). Thus, a configuration for a set of SRS resources may indicate one or more time-frequency resources over which the SRS is to be sent, and may indicate antenna ports over which the SRS is to be sent in these time-frequency resources. In some aspects, a configuration for a set of SRS resources may indicate a use case for the set of SRS resources (e.g., in an SRS-SetUse information element). For example, a set of SRS resources may have use cases for antenna switching, codebook, non-codebook, or beam management.

[0079] The antenna switching SRS resource set may be used to indicate downlink CSI with reciprocity between the uplink channel and the downlink channel. For example, when there is reciprocity between the uplink channel and the downlink channel, the network node 110 may use the antenna switching SRS (e.g., an SRS sent using resources in the antenna switching SRS resource set) to obtain downlink CSI (e.g., to determine a downlink precoder to be used for communication with the UE 120).

[0080] When the network node 110 indicates an uplink precoder to the UE 120, the codebook SRS resource set may be used to indicate the uplink CSI. For example, when the network node 110 is configured to indicate an uplink precoder to the UE 120 (e.g., using a precoder codebook), the network node 110 may use the codebook SRS (e.g., an SRS sent using resources in the codebook SRS resource set) to obtain the uplink CSI (e.g., to determine the uplink precoder to be indicated to the UE 120 and used by the UE 120 to communicate with the network node 110). In some aspects, at least for the codebook SRS, a virtual port (e.g., a combination of two or more antenna ports) with a maximum transmit power may be supported.

[0081] When UE 120 selects an uplink precoder (e.g., instead of the uplink precoder that network node 110 indicates is to be used by UE 120), the non-codebook SRS resource set may be used to indicate uplink CSI. For example, when UE 120 is configured to select an uplink precoder, network node 110 may use a non-codebook SRS (e.g., an SRS sent using resources in the non-codebook SRS resource set) to obtain uplink CSI. In this case, the non-codebook SRS may be precoded using a precoder selected by UE 120 (e.g., the precoder may be indicated to network node 110).

[0082] The beam management SRS resource set may be used to indicate CSI for millimeter wave communication.

[0083] SRS resources may be configured as periodic, semi-persistent (sometimes referred to as semi-persistent scheduling (SPS), or aperiodic. Periodic SRS resources may be configured via a configuration message indicating the periodicity of the SRS resources (e.g., slot-level periodicity, where the SRS resources occur every Y slots) and a slot offset. In some cases, periodic SRS resources may always be activated and may not be dynamically activated or deactivated. Semi-persistent SRS resources may also be configured via a configuration message indicating the periodicity and slot offset for the semi-persistent SRS resources, and may be dynamically activated and deactivated (e.g., using DCI or MAC control element (MAC-CE)). Aperiodic SRS resources may be dynamically triggered, such as via DCI (e.g., UE-specific DCI or group-common DCI) or MAC-CE.

[0084] In some aspects, the UE 120 may be configured with a mapping between an SRS port (e.g., an antenna port) and a corresponding SRS resource. The UE 120 may send an SRS on a specific SRS resource using the SRS port indicated in the configuration. In some aspects, the SRS resource may span N adjacent symbols within a slot (e.g., where N is equal to 1, 2, or 4). The UE 120 may be configured with X SRS ports (e.g., where X≤4). In some aspects, each of the X SRS ports may be mapped to a corresponding symbol of the SRS resource and used to send the SRS in that symbol.

[0085] like Figure 4 As shown, in some aspects, different SRS resource sets (e.g., having different use cases) indicated to the UE 120 may overlap (e.g., in time and / or frequency, such as in the same time slot). For example, as shown by reference numeral 415, a first SRS resource set (e.g., shown as SRS resource set 1) is shown as having an antenna switching use case. As shown, the example antenna switching SRS resource set includes a first SRS resource (shown as SRS resource A) and a second SRS resource (shown as SRS resource B). Therefore, antenna port 0 and antenna port 1 can be used to send antenna switching SRS in SRS resource A (e.g., a first time-frequency resource), and antenna port 2 and antenna port 3 can be used to send antenna switching SRS in SRS resource B (e.g., in a second time-frequency resource).

[0086] As shown by reference numeral 420, a second SRS resource set (e.g., shown as SRS resource set 2) may be a codebook use case. As shown, the example codebook SRS resource set includes only a first SRS resource (shown as SRS resource A). Therefore, antenna port 0 and antenna port 1 may be used to send a codebook SRS in SRS resource A (e.g., a first time-frequency resource). In this case, UE 120 may not use antenna port 2 and antenna port 3 to send a codebook SRS in SRS resource B (e.g., a second time-frequency resource).

[0087] In some examples, UE 120 and / or network node 110 may support codebook (CB) based physical uplink shared channel (PUSCH) transmissions and non-codebook (NCB) based PUSCH transmissions. For CB based PUSCH transmissions, UE 120 may be configured with one SRS resource set, where a use case (sometimes referred to as "purpose") is set to the codebook. In such examples, up to four SRS resources within the SRS resource set may be configured for UE 120. An SRS resource indicator field (SRI) of an uplink DCI associated with a CB based PUSCH transmission (e.g., a DCI scheduling a PUSCH transmission) may indicate one SRS resource. A "precoding information and number of layers" field of the uplink DCI may indicate the number of layers (e.g., rank) and a transmitted precoding matrix indicator (TPMI) for the scheduled PUSCH transmission.

[0088] For NCB-based transmissions, UE 120 may be configured with one SRS resource set, where the use case is set to codebook. In such examples, up to four SRS resources within the SRS resource set may be configured for SRS 120, where each SRS resource has one port. The SRI of the uplink DCI associated with the NCB-based SRS transmission may indicate one or more SRS resources, where the number of indicated SRS resources corresponds to the rank (e.g., number of layers) of the scheduled SRS. In such examples, the scheduled SRS transmission may be sent using the same precoder as the indicated SRS resource. Figures 5 to 8 Additional details of associating SRS resources and / or SRS resource sets with SRS transmissions are described in greater detail.

[0089] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0090] Figure 5 is a diagram illustrating an example 500 associated with time division multiplexing (TDM) SRS transmission based on a single DCI according to the present disclosure. Figure 5The features shown and described may be referred to as sDCI transmission modes, or more simply sDCI modes.

[0091] In some examples, SRS 120 may be scheduled by a single DCI to transmit multiple SRS repetitions in a TDM manner. Each SRS repetition may be associated with the same transport block (TB) (e.g., each of the different repetitions may be used to transmit the same data packet), but each SRS repetition may correspond to different transmission parameters, such as beam parameters, spatial relationship parameters, transmission configuration indicator (TCI) state parameters, power control parameters, precoding parameters, or the like. In some cases, SRS repetitions scheduled by a single DCI may belong to two sets of SRS repetitions, where each set of SRS repetitions corresponds to a different set of transmission parameters (e.g., beam, spatial relationship, TCI, power control, or precoding).

[0092] More specifically, Figure 5 5 shows an example of uplink DCI 502 scheduling four SRS repetitions, including a first SRS repetition 504, a second SRS repetition 506, a third SRS repetition 508, and a fourth SRS repetition 510. The SRS repetitions 504, 506, 508, 510 may be associated with Figure 5 1 and 2. The two sets of transmission parameters indicated using stippling and cross-hatching are associated in FIG. 1 . For example, as indicated using stippling, the first SRS repetition 504 and the third SRS repetition 508 may be associated with a first set of repetitions using a first beam and / or a first set of power control parameters and other parameters. In some cases, the SRS repetitions associated with the first set of SRS repetitions may be targeted to a first network node 110 (e.g., a first TRP). As indicated using cross-hatching, the second SRS repetition 506 and the fourth SRS repetition 510 may be associated with a second set of repetitions using a second beam and / or a second set of power control parameters and other parameters. In some cases, the SRS repetitions associated with the second set of SRS repetitions may be targeted to a second network node 110 (e.g., a second TRP) that is different from the first network node 110.

[0093] To achieve Figure 5 For the single DCI based TDM SRS transmission shown in , the two sets of SRS repetitions may correspond to two SRS resource sets. More specifically, for both CB-based SRS transmission and NCB-based SRS transmission, the uplink DCI 502 may indicate two beams, two power control parameters, or two of the similar transmission parameters by using two corresponding SRI fields in the uplink DCI 502. For CB-based SRS transmission, the uplink DCI 502 may include two TPMI fields indicating two precoders for the two sets of SRS repetitions. Figure 5 In the example shown, and as indicated by reference numeral 512, a first set of PUSCH repetitions (e.g., first SRS repetition 504 and third SRS repetition 508) may be associated with a first set of SRS resources, which may be indicated by a first SRI field included in the uplink DCI 502. Similarly, and as indicated by reference numeral 514, a second set of SRS repetitions (e.g., second SRS repetition 506 and fourth SRS repetition 510) may be associated with a second set of SRS resources, which may be indicated by a second SRI field included in the uplink DCI 502.

[0094] In some cases, the SRS 120 may be scheduled by a single DCI (e.g., uplink DCI 502) to transmit multiple SRS repetitions associated with a spatial division multiplexing (SDM) transmission, a frequency division multiplexing (FDM) transmission, or a single frequency network (SFN) transmission. In this case, the DCI signaling associated with the multiple SRS repetitions associated with the SDM transmission, the FDM transmission, or the SFN transmission may be similar to the signaling described above in conjunction with the multiple SRS repetitions associated with the TDM transmission. For example, for multiple SRS repetitions associated with the SDM transmission, different sets of layers associated with the SRS transmission may be associated with different sets of SRS resources. For multiple SRS repetitions associated with the FDM transmission, different sets of resource blocks (RBs) associated with the SRS transmission may be associated with different sets of SRS resources. And for multiple SRS repetitions associated with the SFN transmission, each layer and / or DMRS may be associated with two sets of SRS resources.

[0095] Despite the combination Figure 5 The examples shown and described include SRS repetitions associated with two network nodes and / or TRPs (e.g., associated with two SRS resource sets), but in some other examples, the uplink DCI may schedule SRS repetitions associated with a single network node and / or TRP (e.g., associated with one SRS resource set). Fig. 6A and 6B Examples of dynamically switching between multiple network node and / or multiple TRP scenarios and single network node and / or single TRP scenarios are described in more detail.

[0096] As indicated above, Figure 5 are provided as examples. Other examples can be found in relation to Figure 5 The examples described are different.

[0097] FIG. 6A to FIG. 6B is a diagram illustrating an example 600 associated with an SRS resource set indicator field according to the present disclosure.

[0098] In some examples, the uplink DCI may include an SRS resource set indicator field that indicates whether the SRS repetition is associated with a single network node and / or TRP (sometimes referred to as a single TRP (STrP) mode) or with multiple network nodes and / or TRPs (sometimes referred to as a multiple TRP (mTRP) mode). More specifically, the SRS resource set indicator field may be a field included in an uplink DCI (e.g., a DCI format 0_1 ​​communication or a DCI format 0_2 communication), and the presence of the field in the uplink DCI may be based on whether two SRS resource sets are configured corresponding to the DCI format. Additionally, the presence of a second SRI field and / or a second TPMI field (e.g., for CB-based transmission) may be conditional on the presence of the SRS resource set indicator field.

[0099] More specifically, if Fig. 6A As shown in , uplink DCI 602 may schedule four SRS repetitions in a manner similar to that described above in conjunction with uplink DCI 502. In this example, the four SRS repetitions may be associated with one of the four repetition patterns indicated by reference numerals 604, 606, 608, and 610. In the first example indicated by reference numeral 604, each SRS repetition is associated with the same SRS resource set (e.g., the first SRS resource set), and thus all SRS repetitions may target the same network node and / or TRP (e.g., the example shown by reference numeral 604 may correspond to an sTRP mode). In such examples, the SRS resource set indicator field may indicate the code point "00". Similarly, in the second example indicated by reference numeral 606, each SRS repetition is associated with the same SRS resource set, but in this example, the SRS resource set is the second SRS resource set. Thus, all SRS repetitions in the example depicted by reference numeral 606 may be targeted to the same network node and / or TRP (e.g., sTRP mode), which may be a different network node and / or TRP than the network node and / or TRP associated with the first example indicated by reference numeral 604. In such an example, the SRS resource set indicator field may indicate code point "01".

[0100] In a third example indicated by reference numeral 608, two of the SRS repetitions (e.g., a first SRS repetition and a third SRS repetition) are associated with a first SRS resource set (e.g., targeted at a first network node and / or a TRP), and the other two SRS repetitions (e.g., a second SRS repetition and a fourth SRS repetition) are associated with a second SRS resource set (e.g., targeted at a second network node and / or a TRP). In this regard, the third example may be associated with an mTRP mode and may be substantially similar to the above example in conjunction with Figure 5 The example described. In such an example, the SRS resource set indicator field may indicate the code point "10". The fourth example indicated by reference numeral 610 may be similar to the third example, but has SRS repetitions in a different order. More specifically, in this example, the first SRS repetition and the third SRS repetition are associated with a second SRS resource set (e.g., targeted at a second network node and / or TRP), and the other two SRS repetitions (e.g., the second SRS repetition and the fourth SRS repetition) are associated with a first SRS resource set (e.g., targeted at a first network node and / or TRP). In such an example, the SRS resource set indicator field may indicate the code point "11".

[0101] In this way, the network node 110 can dynamically switch between the sTRP mode and the mTRP mode by indicating the corresponding code point (e.g., one of 00, 01, 10, or 11) in the SRS resource set indicator field of the uplink DCI. Figure 6B As shown in the table indicated by reference numeral 612 in FIG. 6 , the code point indicated by the SRS resource set indicator field may indicate which SRS resource sets to use, and / or which SRI and / or TPMI fields to use in the uplink DCI 602. More specifically, as described above in conjunction with the first example indicated by reference numeral 604, code point 00 may indicate an sTRP mode associated with a first SRS resource set (e.g., all SRS repetitions are associated with the first SRS resource set and / or are targeted to the same network node and / or TRP, in Figure 6B In such an example, only the first SRI field (for both CB-based and NCB-based transmissions) and / or the first TPMI field (for CB-based transmissions) may be used in the uplink DCI 602 (e.g., the second SRI field and the first TPMI field in the uplink DCI 602 may not be used in this example). As described above in conjunction with the second example indicated by reference numeral 606, code point 01 may indicate an sTRP mode associated with a second SRS resource set (e.g., all PUSCH repetitions are associated with the second SRS resource set and / or are targeted to the same network node and / or TRP, in Figure 6BIn such examples, only the first SRI field and / or the first TPMI field may be used in the uplink DCI 602 (eg, the second SRI field and the first TPMI field in the uplink DCI 602 may not be used in this example).

[0102] As described above in conjunction with the third example indicated by reference numeral 608, code point 10 may indicate an mTRP pattern associated with the transmission order of TRP1, TRP2 (e.g., the first PUSCH repetition and the third PUSCH repetition are associated with the first SRS resource set and / or are targeted at TRP1, and the second PUSCH repetition and the fourth PUSCH repetition are associated with the second SRS resource set and / or are targeted at TRP2). In such an example, both the first SRI field and / or the first TPMI field and the second SRS field and / or the second TPMI field may be used in the uplink DCI 602. Similarly, as described above in conjunction with the fourth example indicated by reference numeral 610, code point 11 may indicate an mTRP pattern associated with the transmission order of TRP2, TRP1 (e.g., the first PUSCH repetition and the third PUSCH repetition are associated with the second SRS resource set and / or are targeted at TRP2, and the second PUSCH repetition and the fourth PUSCH repetition are associated with the first SRS resource set and / or are targeted at TRP1). In such examples, both the first SRI field and / or the first TPMI and the second SRS field and / or the second TPMI field may be used in the uplink DCI 602 .

[0103] although Figures 5 to 6B A TDM PUSCH transmission based on a single DCI is shown (eg, sDCI mode), but in some other aspects, UE 120 may receive multiple DCI communications scheduling corresponding PUSCH communications, which will be discussed below in conjunction with Figure 7 Describe in more detail.

[0104] As indicated above, FIG. 6A to FIG. 6B are provided as examples. Other examples can be found in the FIG. 6A to FIG. 6B The content described is different.

[0105] Figure 7 is a diagram illustrating an example of TRP differentiation based at least in part on a control resource set (CORESET) pool index at a UE in accordance with the present disclosure. In some aspects, a CORESET pool index (or CORESETPoolIndex) value may be used by a UE (UE 120) to identify a TRP associated with an uplink grant received on a physical downlink control channel (PDCCH). In some aspects, in conjunction with Figure 7The features shown and described may be referred to as a multi-TRP communication mode based on multi-DCI, or more simply as an mDCI mode.

[0106] A CORESET may refer to a control region structured to support efficient use of resources, such as by flexible configuration or reconfiguration of resources for one or more PDCCHs associated with a UE 120. In some aspects, a CORESET may occupy the first symbol of an orthogonal frequency division multiplexing (OFDM) slot, the first two symbols of an OFDM slot, or the first three symbols of an OFDM slot. Thus, a CORESET may include multiple RBs in the frequency domain, and one, two, or three symbols in the time domain. In 5G, the number of resources included in a CORESET may be flexibly configured, such as by using RRC signaling to indicate a frequency domain region (e.g., the number of resource blocks) or a time domain region (e.g., the number of symbols) of a CORESET.

[0107] like Figure 7 As illustrated, UE 120 may be configured to have multiple CORESETs in a given serving cell. Each CORESET configured for UE 120 may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for UE 120 may be associated with CORESET ID 1, a second CORESET configured for UE 120 may be associated with CORESET ID 2, a third CORESET configured for UE 120 may be associated with CORESET ID 3, and a fourth CORESET configured for UE 120 may be associated with CORESET ID 4.

[0108] like Figure 7 As further illustrated in , two or more (e.g., up to five) CORESETs may be grouped into CORESET pools. Each CORESET pool may be associated with a CORESET pool index. For example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value may be associated with a particular TRP 705. As an example, and as Figure 7 As shown, the first TRP 705 (TRP A, which may correspond to the above combined Figure 6B The TRP 1) (or the first network node 110) may be associated with the CORESET pool index 0, and the second TRP 705 (TRP B, which may correspond to the above in conjunction with Figure 6BThe TRP2) (or the second network node 110) may be associated with a CORESET pool index 1. The UE 120 may be configured with information identifying an association between a TRP and a CORESET pool index value assigned to the TRP via a higher layer parameter such as PDCCH-Config. In other words, the UE 120 may determine that it is configured to operate with multiple TRPs based on multiple DCI (e.g., configured to operate in mDCI mode) based on whether the UE 120 is configured by a higher layer parameter PDCCH-Config including two different values ​​of CORESETPoolIndex for an active bandwidth part (BWP) for a serving cell. Thus, the UE may identify the TRP in which the DCI uplink grant is sent by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI uplink grant is sent, determining a CORESET pool index value associated with a CORESET pool in which the CORESET ID is included, and identifying the TRP associated with the CORESET pool index value.

[0109] In some examples, PUSCH communications scheduled by multiple DCIs (e.g., DCIs received from TRP A and TRP B) may be TDMed and thus use only one SRS resource set (for both CB-based PUSCH transmissions and NCB-based PUSCH transmissions). However, in some other examples, PUSCH communications scheduled by multiple DCIs may at least partially overlap in the time domain and / or may use multiple SRS resource sets, as described below in conjunction with Figure 8 Describe in more detail.

[0110] As indicated above, Figure 7 are provided as examples. Other examples can be found in relation to Figure 7 The examples described are different.

[0111] Figure 8 is a diagram illustrating an example 800 associated with time-domain overlapping PUSCH with multiple DCIs according to the present disclosure.

[0112] As indicated by reference numeral 802, in some examples, two PUSCH transmissions, shown as PUSCH 1 and PUSCH 2, may be scheduled by two DCIs (e.g., PUSCH 1 and PUSCH 2 may be associated with an mDCI mode). In this example, the two PUSCH transmissions (e.g., PUSCH 1 and PUSCH 2) may be associated with the same serving cell and / or component carrier and may at least partially overlap in the time domain. The first PUSCH transmission (e.g., PUSCH 1) (which may be associated with a CORESET pool index value of 0) may be associated with a first set of SRS resources and / or a first set of transmission parameters (e.g., beam, TCI state, power control parameters, precoder, or similar parameters). The second PUSCH transmission (e.g., PUSCH 2) (which may be associated with a CORESET pool index value of 1) may be associated with a second set of SRS resources and / or a second set of transmission parameters.

[0113] In such examples, PUSCH transmissions may overlap in the frequency domain. More specifically, as shown in the example indicated by reference numeral 804, PUSCH 1 and PUSCH 2 may completely overlap in both the time domain and the frequency domain. Furthermore, as shown in the example indicated by reference numeral 806, PUSCH 1 and PUSCH 2 may completely overlap in the time domain and may partially overlap in the frequency domain. As shown in the example indicated by reference numeral 808, PUSCH 1 and PUSCH 2 may partially overlap in the time domain and may not overlap in the frequency domain. And as shown in the example indicated by reference numeral 810, PUSCH 1 and PUSCH 2 may partially overlap in both the time domain and the frequency domain.

[0114] As described above, the sDCI mode (eg, the above combined Figures 5 to 6B The mode described above) and the mDCI mode (for example, the above combined Figures 7 and 8The modes described above) may share similarities and differences. More specifically, in both the sDCI mode and the mDCI mode, two SRS resource sets (e.g., with usage set to codebook or non-codebook) may be configured for use by the UE 120. In the sDCI mode, one PUSCH transmission scheduled by one uplink DCI may be associated with two SRS resource sets, while in the mDCI mode, two PUSCH transmissions scheduled by different uplink DCIs (which may completely overlap, partially overlap, or not overlap in the time domain and / or frequency domain) are associated with two SRS resource sets. In addition, the mDCI mode may be enabled based on the configuration of two different CORESET pool index values, which is not the case for the sDCI mode. Additionally, for the sDCI mode, the uplink DCI includes an SRS resource set indicator, but for the mDCI mode, the SRS resource set indicator is not required. In contrast, in mDCI mode, the associated SRS resource set may be determined based on the CORESET pool index value of the CORESET in which the DCI is received (e.g., in mDCI mode, one DCI does not indicate two SRS resource sets). In addition, in sDCI mode, a second SRI field and a second TPMI field are required in the DCI, which are not required for mDCI mode. In this regard, the presence of an SRS resource set indicator in the DCI (e.g., for DCI format 0_1 ​​and DCI format 0_2, respectively) may be based on whether two resource sets are configured to be associated with the DCI format.

[0115] In some examples, a UE 120 receiving an uplink DCI may not be able to determine whether the uplink DCI is associated with an sDCI mode or an mDCI mode. This may result in communication errors and thus increase power, computation, and network resource consumption associated with retransmission or otherwise associated with correcting communication errors. In addition, the UE 120 may not have the ability to operate in both an sDCI mode and an mDCI mode at the same time. Therefore, a UE 120 receiving DCI associated with both modes may not be able to send PUSCH communications associated with each mode, resulting in increased latency, reduced throughput, and overall inefficient use of network resources.

[0116] Some techniques and devices described herein enable UE 120 to distinguish between sDCI mode and mDCI mode and / or to operate in a combination of sDCI and mDCI-based operations. In some aspects, UE 120 may distinguish sDCI mode from mDCI mode based at least in part on implicit or explicit indications received from network node 110 (such as at least in part based on configuration information associated with two SRS resource sets, explicit configuration indications received from the network node, or similar information). Additionally or alternatively, in some aspects, UE 120 and network node 110 may dynamically switch between sDCI mode and mDCI mode, such as by using different DCI formats and / or DCI fields associated with each mode. Additionally or alternatively, in some aspects, UE 120 and network node 110 may be able to use both sDCI mode and mDCI mode for simultaneous transmission. Thus, communication errors between UE 120 and network node 110 may be reduced, resulting in reduced power, computational, and network resource consumption associated with correcting communication errors, and UE 120 and network node 110 may communicate with reduced latency, increased throughput, and overall more efficient use of network resources.

[0117] As indicated above, Figure 8 are provided as examples. Other examples can be found in relation to Figure 8 The examples described are different.

[0118] 9A to 9D 900 is a diagram of an example associated with DCI for sDCI and mDCI transmission modes according to the present disclosure. Fig.9A As shown, the network node 110 can communicate with the UE 120. In some aspects, the network node 110 and the UE 120 can be part of a wireless network (e.g., the wireless network 100). The UE 120 and the network node 110 can be in communication with each other. Fig.9A The operations shown are performed after a wireless connection has been established.

[0119] As indicated by reference numeral 905, UE 120 may send, and network node 110 may receive, capability information (e.g., a capability report). In some aspects, the capability information may indicate that the UE supports operation in a simultaneous transmission mode associated with both an sDCI mode and an mDCI mode. More specifically, in some aspects, UE 120 may be able to support overlapping (e.g., in the time domain) PUSCH transmissions associated with an sDCI mode and an mDCI mode (e.g., UE 120 may be able to send a first PUSCH communication scheduled by an uplink DCI associated with the sDCI mode and a second PUSCH communication scheduled by an uplink DCI associated with the mDCI mode that at least partially overlaps with the first PUSCH communication). Thus, UE 120 may send, and network node 110 may receive, capability information indicating the UE 120's ability to support overlapping uplink communications associated with an sDCI mode and an mDCI mode.

[0120] As indicated by reference numeral 910, network node 110 may send, and UE 120 may receive, configuration information. In some aspects, UE 120 may receive the configuration information via one or more of RRC signaling, one or more MAC-CEs, and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by UE 120 (e.g., already known to UE 120 and / or previously indicated by network node 110 or other network devices), and / or explicit configuration information for UE 120 to use to configure UE 120, etc.

[0121] In some aspects, the configuration information may indicate the configuration of at least two SRS resource sets. For example, the configuration information may configure the above combined Figures 4 to 8 Any one of the first SRS resource set and the second SRS resource set. The configuration information may also indicate additional parameters associated with the sDCI mode, the mDCI mode, the simultaneous transmission mode associated with overlapping PUSCH communications associated with both the sDCI mode and the mDCI mode, or a similar configuration. For example, in the aspect where the UE 120 indicates support for overlapping uplink communications associated with the sDCI mode and the mDCI mode in conjunction with the capability information described above in conjunction with reference numeral 905, the configuration information may include a simultaneous transmission configuration. In some aspects, the simultaneous transmission indication may indicate whether one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode, as described in more detail below in conjunction with reference numerals 920 and 925.

[0122] In some aspects, at least a portion of the configuration information may be associated with a specific BWP and / or a specific component carrier. Additionally or alternatively, in some aspects, at least a portion of the configuration information may be associated with a specific DCI format. For example, in some aspects where the configuration information includes a simultaneous transmission configuration (e.g., information indicating whether one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode), the simultaneous transmission configuration may be associated with at least one of a BWP or a component carrier. In some other aspects where the configuration information includes a simultaneous transmission configuration, the simultaneous transmission configuration may be associated with at least one DCI format (e.g., one of DCI format 0_1 ​​and / or DCI format 0_2). For example, in some aspects, the simultaneous transmission configuration may indicate that a first DCI format (e.g., one of DCI format 0_1 ​​or DCI format 0_2) is associated with an mDCI mode, and the simultaneous transmission configuration may indicate that a second DCI format different from the first DCI format (e.g., the other of DCI format 0_1 ​​or DCI format 0_2) is associated with an sDCI mode, which is described in more detail below in conjunction with reference numbers 920 and 925.

[0123] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0124] As indicated by reference numeral 915, the network node 110 may send and the UE 120 may receive one or more DCI communications associated with one or more uplink communications. In some aspects, the one or more DCI communications may correspond to the above with respect to Figures 4 to 8Any uplink DCI of the uplink DCI for scheduling one or more PUSCH communications. In this regard, in some aspects, one or more DCI communications may correspond to uplink DCI associated with the sDCI mode, while in some other aspects, one or more DCI communications may correspond to uplink DCI associated with the mDCI mode, and in some other aspects, one or more DCI communications may correspond to uplink DCI associated with both the sDCI mode and the mDCI mode. For example, in some aspects, the one or more DCI communications may include at least two DCI communications, wherein the first DCI communication is associated with a first uplink communication (e.g., a first PUSCH communication) associated with the sDCI mode, and the second DCI communication is associated with a second uplink communication (e.g., a second PUSCH communication) that at least partially overlaps with the first uplink communication in the time domain and is associated with the mDCI mode. In such aspects, receiving the first DCI communication and the second DCI communication associated with the sDCI mode and the mDCI mode, respectively, may be based at least in part on the capability information described above in conjunction with reference number 905. More specifically, receiving first and second DCI communications associated with the sDCI mode and the mDCI mode, respectively, may be based at least in part on capability information indicating support for overlapping uplink communications associated with the sDCI mode and the mDCI mode.

[0125] As shown by reference numeral 920, the UE 120 may receive an indication of whether one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode. In some aspects, the indication may be based at least in part on configuration information (e.g., configuration information configuring at least two sets of SRS resources, configuration information associated with a simultaneous transmission configuration, or the like). Further, in some aspects, the indication of whether one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode may be coupled with an explicit indication (e.g., explicit signaling from the network node 110 to the UE 120, such as using Fig.9A In some other aspects, the indication of whether one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode may be associated with an implicit indication (e.g., an indication not associated with an explicit RRC configuration, such as using Fig.9A), such as whether the active BWP is configured with at least two CORESETs associated with different CORESET pool index values, whether two SRS resource sets are associated with a DCI format for scheduling uplink communications, or similar implicit indications, which are described in more detail below in conjunction with reference number 925.

[0126] As shown by reference numeral 925, UE 120 may determine whether one or more DCI communications (e.g., one or more DCI communications described above in conjunction with reference numeral 915) are associated with an sDCI mode, an mDCI mode, or both an sDCI mode and an mDCI mode based at least in part on the indication described above in conjunction with reference numeral 920. In some aspects, determining whether one or more DCI communications are associated with an sDCI mode, an mDCI mode, or both an sDCI mode and an mDCI mode may include determining whether one or more fields are included in the one or more DCI communications. In other words, the indication of whether one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode may indicate whether one or more fields are included in the one or more DCI communications. This may be because a DCI communication associated with an sDCI mode may include fields that are not included in a DCI communication associated with an mDCI mode, such as an SRS resource set indicator field, a second SRI field, a second TPMI field, and / or a second PTRS-DMRS association field, as described above in conjunction with Figure 8 Thus, in some aspects, determining whether one or more fields are included in one or more DCI communications may include determining whether one or more of an SRS resource set indicator field, a second SRI field, a second TPMI field, and / or a second PTRS-DMRS association field are included in the one or more DCI communications.

[0127] In some aspects, such as in aspects where only one of the sDCI mode or the mDCI mode may be semi-statically configured (e.g., a combination of the sDCI mode and the mDCI mode is not possible), the UE 120 may determine whether one or more DCI communications are associated with the sDCI mode and / or the mDCI mode based at least in part on whether the configuration information configures at least two CORESETs associated with different CORESET pool index values ​​for the active BWP (e.g., the UE 120 may determine whether one or more of the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field are included in the one or more DCI communications). More specifically, when the configuration information configures at least two CORESETs associated with different CORESET pool index values ​​for the active BWP, this may implicitly indicate to the UE 120 that the one or more DCI communications are associated with the mDCI mode, and thus one or more fields (e.g., the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field) are not present in the one or more DCI communications. In other words, in some aspects, the configuration information enables the UE 120 to transmit time-domain overlapping PUSCH communications (e.g., mDCI mode for simultaneous transmission) in the same component carrier by configuring at least two SRS resource sets and configuring at least two CORESETs associated with different CORESET pool index values ​​for the active BWP.

[0128] In contrast, when the configuration information does not configure at least two CORESETs associated with different CORESET pool index values ​​for the active BWP, the configuration information may implicitly indicate to the UE 120 that the one or more DCI communications are associated with the sDCI mode, and thus one or more fields (e.g., the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field) are present in the one or more DCI communications. In other words, in some aspects, the UE 120 may determine that the one or more DCI communications are associated with the sDCI mode based at least in part on prohibiting the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0129] In some aspects, such as aspects where only one of the sDCI mode or the mDCI mode may be semi-statically configured (e.g., a combination of the sDCI mode and the mDCI mode is not possible), the UE 120 may determine whether one or more DCI communications are associated with the sDCI mode and / or the mDCI mode (e.g., the UE 120 may determine whether one or more of the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field are included in the one or more DCI communications based at least in part on an explicit configuration (e.g., an explicit RRC configuration) configured per BWP and / or component carrier that enables only one mode for simultaneous transmission of the corresponding BWP and / or component carrier.

[0130] For example, the network node 110 may send and the UE 120 may receive a simultaneous transmission configuration associated with an indication of whether one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, such as the simultaneous transmission configuration described above in conjunction with reference numerals 910 and 920. In some aspects, the simultaneous transmission configuration may be associated with at least one of a BWP or a component carrier. Thus, in some aspects, the UE 120 may determine that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission associated with the BWP and / or component carrier in which the DCI communication is received. In such aspects, the configuration of two SRS resource sets and two CORESET pool index values ​​may not necessarily mean that PUSCH transmissions associated with different CORESET pool values ​​may overlap in time. Instead, in some aspects, PUSCH transmissions associated with different CORESET pool values ​​may overlap in time only when the simultaneous transmission configuration indicates that the mDCI mode is enabled for simultaneous transmission.

[0131] Alternatively, in some other aspects, the UE 120 may determine that one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is not enabled for simultaneous transmission. For example, the simultaneous transmission configuration may explicitly indicate that the mDCI mode is not enabled for simultaneous transmission and / or may indicate that simultaneous transmission is not enabled (meaning that the PUSCH communication is associated with the sDCI mode). Additionally or alternatively, the simultaneous transmission configuration may indicate that one or more multiplexing modes associated with the sDCI mode are enabled for simultaneous transmission, such as a spatial domain multiplexing (SDM) mode, a frequency domain multiplexing (FDM) mode, and / or a single frequency network (SFN) mode. In some other aspects, the simultaneous transmission configuration may indicate that simultaneous transmission is not enabled, meaning that none of the SDM mode, the FDM mode, or the SFN mode is enabled, and therefore the UE 120 may determine that one or more DCI communications are associated with TDM SRS transmission based on a single DCI (e.g., associated with the sDCI mode).

[0132] In some aspects, the simultaneous transmission configuration may be associated with at least one DCI format. For example, the simultaneous transmission configuration may indicate that a first DCI format (e.g., one of DCI format 0_1 ​​or DCI format 0_2) is associated with an mDCI mode, and a second DCI format different from the first DCI format (e.g., the other of DCI format 0_1 ​​or DCI format 0_2) is associated with an sDCI mode. This may enable dynamic switching between sDCI mode and mDCI mode, as the UE 120 may determine which mode is associated with PUSCH communication based at least in part on the type of DCI format used for the uplink DCI. More specifically, in some aspects, UE 120 may determine that the first DCI communication is associated with the mDCI mode (and therefore does not include the SRS resource set indicator field, the second SRI field, the second TPMI field and / or the second PTRS-DMRS association field) based at least in part on the first DCI communication being associated with the first DCI format, and / or UE 120 may determine that the second DCI communication is associated with the sDCI mode (and therefore does not include the SRS resource set indicator field, the second SRI field, the second TPMI field and / or the second PTRS-DMRS association field) based at least in part on the second DCI communication being associated with the second DCI format.

[0133] In some aspects, when the simultaneous transmission configuration indicates that a first DCI format (e.g., one of DCI format 0_1 ​​or DCI format 0_2) is associated with an mDCI mode and a second DCI format (e.g., the other of DCI format 0_1 ​​or DCI format 0_2) is associated with an sDCI mode, if at least one of the DCIs is associated with a DCI format associated with the sDCI mode (e.g., if at least one of the DCIs includes an SRS resource set indicator field, a second SRI field, a second TPMI field, and / or a second PTRS-DMRS association field), then the UE 120 may not expect to be scheduled by two DCIs to transmit time-overlapping PUSCH communications (e.g., two PUSCH communications associated with different CORESET pool index values) in the same component carrier. In other words, and if Fig. 9B As shown in the example indicated by reference numeral 930 in , in some aspects, in order to be scheduled by two DCIs to send time-overlapping PUSCH communications (e.g., two PUSCH communications associated with different CORESET pool index values) in the same component carrier, the two DCIs may be associated with a DCI format configured to be associated with an mDCI mode (e.g., the two DCIs may be associated with a DCI format that does not include an SRS resource set indicator field, a second SRI field, a second TPMI field, and / or a second PTRS-DMRS association field).

[0134] In some aspects, such as in aspects where only one of the sDCI mode or the mDCI mode may be semi-statically configured (e.g., a combination of the sDCI mode and the mDCI mode is not possible), the UE 120 may determine whether one or more DCI communications are associated with the sDCI mode and / or the mDCI mode based at least in part on whether two sets of SRS resources are configured to be associated with a DCI format for scheduling PUSCH communications (e.g., the UE 120 may determine whether one or more of the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field are included in the one or more DCI communications). For example, the UE 120 may determine that the DCI communication is associated with the mDCI mode based at least in part on only one set of SRS resources being associated with the DCI format for sending the DCI communication. Similarly, the UE 120 may determine that the DCI communication is associated with the sDCI mode based at least in part on two sets of SRS resources being associated with the DCI format for sending the DCI communication.

[0135] In some aspects, when UE 120 is scheduled by two DCIs to transmit time-overlapping PUSCH communications (e.g., PUSCH communications associated with different CORESET pool index values) in the same component carrier, UE 120 may not expect one or more fields (e.g., an SRS resource set indicator field) to be present in each of the two DCIs (e.g., indicating that only one SRS resource set associated with the DCI format is configured), and / or may expect the SRS resource set indicator field to indicate only one SRS resource set (e.g., the SRS resource set indicator indicates one of code point 00 or code point 01). More specifically, as Fig. 9B As shown in the example indicated by reference numeral 925, in some aspects, a first DCI that schedules a first PUSCH communication and is associated with a first CORESET pool index value (e.g., CORESET pool index value 0) may be sent using a first DCI format (e.g., DCI format 0_1 ​​in the depicted example, but may be DCI format 0_2 in other examples) that indicates a first SRS resource set, such as by including an SRS resource set indicator field that indicates code point 00. Additionally, a second DCI that schedules a second PUSCH communication that at least partially overlaps with the first PUSCH communication and is associated with the first CORESET pool index value (e.g., CORESET pool index value 0) may also be sent using the first DCI format (e.g., DCI format 0_1), but the second DCI indicates a second SRS resource set, such as by including an SRS resource set indicator field that indicates code point 01.

[0136] In other words, in some aspects, the same DCI format (e.g., one of DCI format 0_1 ​​or DCI format 0_2) may be used to schedule PUSCH communications associated with the mDCI mode and PUSCH communications associated with the sDCI mode. In such aspects, when the SRS resource set indicator field of the DCI indicates one SRS resource set (e.g., when the SRS resource set indicator field indicates code point 01 or code point 10 for scheduling PUSCH communications associated with the mDCI mode, such as shown in the example indicated by reference numeral 935), another PUSCH communication in the same component carrier (e.g., a PUSCH communication scheduled by another DCI) may overlap in time with the PUSCH communication. However, when the SRS resource set indicator field of the DCI indicates two SRS resource sets (e.g., when the SRS resource set indicator field indicates code point 10 or code point 11 for scheduling PUSCH communications associated with the sDCI mode), no other PUSCH communication in the same component carrier may overlap in time with the PUSCH communication.

[0137] In some aspects, both the sDCI mode and the mDCI may be semi-statically configured (e.g., a combination of the sDCI mode and the mDCI mode is possible). In such aspects, the UE 120 may determine that the one or more DCI communications include both DCI communications associated with the sDCI mode (e.g., DCI communications that include one or more of the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field) and DCI communications associated with the mDCI mode (e.g., DCI communications that do not include one or more of the SRS resource set indicator field, the second SRI field, the second TPMI field, and / or the second PTRS-DMRS association field). More specifically, UE 120 may be configured to receive, from network node 110, a first DCI communication associated with a first uplink communication (e.g., a first PUSCH communication associated with a first CORESET pool index value), wherein the first DCI communication is associated with an sDCI mode, and a second DCI communication associated with a second uplink communication (e.g., a second PUSCH communication associated with a second CORESET pool index value), the second uplink communication at least partially overlapping with the first uplink communication in the time domain, wherein the second DCI communication is associated with an mDCI mode.

[0138] In such aspects, at least one of the DCI communications may indicate that two SRS resource sets are associated with the corresponding uplink communication. For example, a first DCI communication (e.g., a DCI communication associated with the sDCI mode in the above example) may indicate that two SRS resource sets are associated with the first uplink communication. For example, the first DCI communication may indicate that two SRS resource sets are associated with the first uplink communication via an SRS resource set indicator field indicating at least one of code point 10 or code point 11 associated with the first DCI communication.

[0139] In some aspects, the combination of the sDCI mode and the mDCI mode may be subject to the capabilities of the UE 120. For example, receiving a first DCI communication (e.g., a DCI communication associated with the sDCI mode) and a second DCI communication (e.g., a DCI communication associated with the mDCI mode) may be based at least in part on capability information indicating the UE 120's ability to support overlapping uplink communications associated with the sDCI mode and the mDCI mode (e.g., the capability information described above in conjunction with reference numeral 905). Additionally or alternatively, to operate with the combination of the sDCI mode and the mDCI mode, the DCI communication associated with the sDCI mode (e.g., a DCI communication indicating two sets of SRS resources) may be restricted to scheduling two sets of PUSCH repetitions in a TDM manner (e.g., the capability information described above in conjunction with reference numeral 905). Figure 5The two sets of PUSCH repetitions described above are combined with Fig. 6A In other words, in some aspects, DCI communications associated with the sDCI mode may not be used to schedule SDM-based PUSCH communications, FDM-based PUSCH communications, and / or SFN-based PUSCH communications. Additionally or alternatively, in order to operate with a combination of the sDCI mode and the mDCI mode at any given time (e.g., in any given OFDM symbol), if the first PUSCH repetition and the second PUSCH repetition are associated with the same SRS resource set (e.g., in any given OFDM symbol, the UE 120 may be expected to send only a single PUSCH repetition associated with a given SRS resource set), then the UE 120 may be expected to not send a first PUSCH repetition associated with the first PUSCH communication and a second PUSCH repetition associated with the second PUSCH communication.

[0140] In some aspects, when operating according to a combination of sDCI mode and mDCI mode, two sets of SRS resources may be shared for two CORESET pool index values ​​(e.g., each of the CORESET pool index values ​​may be associated with the same two sets of SRS resources). However, in some other aspects, the sets of SRS resources may be separated for the two CORESET pool index values ​​(e.g., each of the CORESET pool index values ​​may be associated with different sets of the two sets of SRS resources).

[0141] More specifically, Fig. 9C Examples 940, 945 are shown where two SRS resource sets may be shared for two CORESET pool index values. Fig. 9C In the example shown in FIG. 1 , UE 120 may detect two DCI communications that schedule corresponding PUSCH communications, Fig. 9C ” and “PUSCH 2” in the figure. A first DCI communication of the two DCI communications (e.g., the DCI communication for scheduling PUSCH 1) may be associated with a CORESET pool index value of 0 (e.g., the first DCI communication may be detected in a CORESET associated with the CORESET pool index value of 0), and a second DCI communication of the two DCI communications (e.g., the DCI communication for scheduling PUSCH 2) may be associated with a CORESET pool index value of 1 (e.g., the second DCI communication may be detected in a CORESET associated with the CORESET pool index value of 1).

[0142] In addition, Fig. 9CIn the example depicted in , PUSCH 1 (e.g., PUSCH communication scheduled by DCI associated with CORESET pool index value 0) and PUSCH 2 (e.g., PUSCH communication scheduled by DCI associated with CORESET pool index value 1) may be associated with the same two SRS resource sets. In other words, the first CORESET pool index value may be associated with two SRS resource sets of at least two configured SRS resource sets, and the second CORESET pool index value may also be associated with two SRS resource sets of at least two configured SRS resource sets.

[0143] More specifically, in example 940, similar to the above, Figure 5 For the PUSCH communication described, the first DCI communication may be associated with the sDCI mode, and PUSCH 1 may be associated with two sets of PUSCH repetitions (e.g., the first PUSCH repetition and the third PUSCH repetition may be associated with the first SRS resource set, and the second PUSCH repetition and the fourth repetition may be associated with the second SRS resource set). In addition, the second DCI communication may be associated with the mDCI mode, and PUSCH 2 may be associated with one SRS resource set (here, the second SRS resource set) of the two SRS resource sets associated with PUSCH 1. In example 945, both the first DCI communication and the second DCI communication may be associated with the sDCI mode, and thus both PUSCH 1 and PUSCH 2 may be associated with PUSCH repetitions associated with two SRS resource sets. In such examples, PUSCH 1 and PUSCH 2 may be associated with PUSCH repetitions of different orders, so that the PUSCH repetitions associated with the same SRS resource set do not overlap in the time domain. For example, with respect to PUSCH 1, the first PUSCH repetition and the third PUSCH repetition may be associated with the first SRS resource set and the second PUSCH repetition and the fourth repetition may be associated with the second SRS resource set, and with respect to PUSCH 2, the first PUSCH repetition and the third PUSCH repetition may be associated with the second SRS resource set and the second PUSCH repetition and the fourth repetition may be associated with the first SRS resource set.

[0144] Alternatively, for two CORSET pool index values, the SRS resource sets may be separate (e.g., different), and up to four SRS resource sets may be configured for the same DCI format, such that a DCI received in a CORESET associated with a CORESET pool index value of 0 may indicate one or more SRS resource sets in a first set of two SRS resource sets, and a DCI received in a CORESET associated with a CORESET pool index value of 1 may indicate one or more SRS resource sets in a second set of two SRS resource sets. More specifically, in Fig.9D In the example depicted in , PUSCH 1 (e.g., PUSCH communication scheduled by a DCI associated with a CORESET pool index value of 0) and PUSCH 2 (e.g., PUSCH communication scheduled by a DCI associated with a CORESET pool index value of 1) are shown as being associated with separate sets of SRS resources. In other words, a first CORESET pool index value may be associated with a first set of two sets of SRS resources of at least two configured sets of SRS resources, and a second CORESET pool index value may be associated with a second set of two sets of SRS resources of at least two configured sets of SRS resources.

[0145] More specifically, in the example indicated by reference numeral 950, similar to the above in conjunction with Figure 5 For the PUSCH communication described above, the first DCI communication may be associated with the sDCI mode, and PUSCH 1 may be associated with two sets of PUSCH repetitions (e.g., the first PUSCH repetition and the third PUSCH repetition may be associated with the first SRS resource set, and the second PUSCH repetition and the fourth repetition may be associated with the second SRS resource set). In addition, the second DCI communication may be associated with the mDCI mode, and PUSCH 2 may be associated with one of two other SRS resource sets (e.g., one of the third SRS resource set or the fourth SRS resource set, such as Fig.9D) is associated with the third SRS resource set shown in . In the example indicated by reference numeral 955, both the first DCI communication and the second DCI communication may be associated with the sDCI mode, and therefore both PUSCH 1 and PUSCH 2 may be associated with PUSCH repetitions associated with two SRS resource sets. In such an example, PUSCH 1 may be associated with a set of two SRS resource sets different from PUSCH 2. For example, with respect to PUSCH 1, the first PUSCH repetition and the third PUSCH repetition may be associated with the first SRS resource set and the second PUSCH repetition and the fourth repetition may be associated with the second SRS resource set, while with respect to PUSCH 2, the first PUSCH repetition and the third PUSCH repetition may be associated with the third SRS resource set and the second PUSCH repetition and the fourth repetition may be associated with the fourth SRS resource set. Alternatively, in an aspect where only three SRS resource sets are configured, the second repetition and the fourth repetition of PUSCH 2 may be associated with the third resource set.

[0146] Based at least in part on the UE 120 and / or the network node 110 distinguishing between the sDCI mode and the mDCI mode, dynamically switching between the sDCI mode and the mDCI mode, and / or operating in a combination of the sDCI mode and the mDCI mode, the UE 120 and / or the network node 110 may save computational, power, network, and / or communication resources that may otherwise have been consumed during the legacy sDCI mode and the mDCI mode. For example, based at least in part on the UE 120 and / or the network node 110 distinguishing between the sDCI mode and the mDCI mode, dynamically switching between the sDCI mode and the mDCI mode, and / or operating in a combination of the sDCI mode and the mDCI mode, the UE 120 and the network node 110 may communicate with increased capacity and / or reduced error rate, which may save computational, power, network, and / or communication resources that may otherwise be consumed to send and receive communications and / or detect and / or correct communication errors.

[0147] As indicated above, 9A to 9D are provided as examples. Other examples can be found in the 9A to 9D The examples described are different.

[0148] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120) performs operations associated with DCI for single DCI and multiple DCI transmission modes.

[0149] like Fig.10As shown, in some aspects, process 1000 may include receiving configuration information indicating configuration of at least two SRS resource sets from a network node (block 1010). For example, Fig.12 The UE depicted in (eg, using communication manager 140 and / or receiving component 1202) may receive configuration information indicating configuration of at least two sets of SRS resources from a network node, as described above.

[0150] like Fig.10 As further shown, in some aspects, process 1000 may include receiving one or more DCI communications associated with one or more uplink communications (block 1020). Fig.12 The UE depicted in FIG. 1200 (eg, using communications manager 140 and / or receiving component 1202 ) may accept one or more DCI communications associated with one or more uplink communications, as described above.

[0151] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include: receiving an indication from a network node whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information (block 1030). For example, a UE (e.g., using Fig.12 The communication manager 140 and / or receiving component 1202 depicted in the figure may receive an indication from the network node as to whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode, wherein the indication is based at least in part on the configuration information, as described above.

[0152] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0153] In a first aspect, the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode indicates whether one or more fields are included in the one or more DCI communications.

[0154] In a second aspect, either alone or in combination with the first aspect, the one or more fields include at least one of: an SRS resource set indicator field, a second SRS resource indicator field, a second transmitted pre-decoding matrix indicator field, or a second phase tracking reference signal and demodulation reference signal association field.

[0155] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is based at least in part on whether the configuration information is for an active BWP configuration of at least two CORESETs associated with different CORESET pool index values.

[0156] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1000 includes: determining that the one or more DCI communications are associated with the mDCI mode based at least in part on the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP configuration.

[0157] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1000 includes: determining that the one or more DCI communications are associated with the sDCI mode based at least in part on prohibiting the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0158] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 1000 comprises receiving from the network node a simultaneous send configuration associated with the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

[0159] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the simultaneous transmission configuration is associated with at least one of a bandwidth part or a component carrier.

[0160] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1000 includes determining that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

[0161] In a ninth aspect, alone or in combination with one or more of aspects one to eight, process 1000 includes: determining that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is not enabled for simultaneous transmission and the simultaneous transmission configuration indicating at least one of the following: a spatial domain multiplexing mode is enabled for simultaneous transmission, a frequency domain multiplexing mode is enabled for simultaneous transmission, or a single frequency network mode is enabled for simultaneous transmission.

[0162] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the simultaneous transmission configuration is associated with at least one DCI format.

[0163] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the simultaneous transmission configuration indicates that a first DCI format is associated with the mDCI mode, and the simultaneous transmission configuration indicates that a second DCI format different from the first DCI format is associated with the sDCI mode.

[0164] In a twelfth aspect, alone or in combination with one or more of aspects 1 to eleven, process 1000 includes: determining that the first DCI communication is associated with the mDCI mode based at least in part on the first DCI communication being associated with the first DCI format, and determining that the second DCI communication is associated with the sDCI mode based at least in part on the second DCI communication being associated with the second DCI format.

[0165] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is at least partially based on whether two SRS resource sets of the at least two SRS resource sets are associated with the DCI format associated with the one or more DCI communications.

[0166] In a fourteenth aspect, alone or in combination with one or more of aspects one to thirteen, process 1000 includes: determining that the one or more DCI communications are associated with the mDCI mode based at least in part on only one of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0167] In a fifteenth aspect, either alone or in combination with one or more of aspects one to fourteen, process 1000 includes determining that the one or more DCI communications are associated with the sDCI mode based at least in part on two of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0168] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 1000 includes: receiving a first DCI communication associated with a first uplink communication among the one or more DCI communications from the network node, wherein the first DCI communication is associated with the sDCI mode; and receiving a second DCI communication associated with a second uplink communication among the one or more DCI communications from the network node, which at least partially overlaps with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

[0169] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the first DCI communication indicates that two SRS resource sets of the at least two SRS resource sets are associated with the first uplink communication.

[0170] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the first DCI communication indicates, via an SRS resource set indicator field indicating at least one of code point 10 or code point 11 associated with the first DCI communication, that the two SRS resource sets are associated with the first uplink communication.

[0171] In a nineteenth aspect, alone or in combination with one or more of aspects one to eighteen, process 1000 includes sending capability information to the network node indicating the ability to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein receiving the first DCI communication and the second DCI communication is based at least in part on the capability information.

[0172] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the first DCI communication is associated with a first CORESET pool index value and the second DCI communication is associated with a second CORESET pool index value.

[0173] In the twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, the first CORESET pool index value is associated with two SRS resource sets of the at least two SRS resource sets, and the second CORESET pool index value is associated with the two SRS resource sets of the at least two SRS resource sets.

[0174] In the twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, the first CORESET pool index value is associated with a first set of two SRS resource sets among the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with a second set of two SRS resource sets among the at least two SRS resource sets.

[0175] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0176] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a network node, in accordance with the present disclosure. The example process 1100 is an example in which a network node (eg, network node 110) performs operations associated with DCI for single DCI and multiple DCI transmission modes.

[0177] like Fig.11 As shown, in some aspects, process 1100 may include: sending configuration information indicating configuration of at least two SRS resource sets to the UE (block 1110). For example, the network node (eg, using Fig.13 The communication manager 150 depicted in FIG. 1 , the sending component 1304 and / or the configuring component 1308 may send configuration information indicating the configuration of at least two SRS resource sets to the UE, as described above.

[0178] like Fig.11 As further shown, in some aspects, process 1100 may include sending one or more DCI communications associated with one or more uplink communications to a UE (block 1120). For example, a network node (eg, using Fig.13 The communication manager 150 and / or the transmitting component 1304 depicted in FIG. 1 may transmit one or more DCI communications associated with one or more uplink communications to the UE, as described above.

[0179] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include: indicating to the UE whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information (block 1130). For example, a network node (e.g., using Fig.13The communication manager 150 and / or indication component 1310 depicted in the figure may indicate to the UE whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information, as described above.

[0180] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0181] In a first aspect, indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode also indicates whether one or more fields are included in the one or more DCI communications.

[0182] In a second aspect, either alone or in combination with the first aspect, the one or more fields include at least one of: an SRS resource set indicator field, a second SRS resource indicator field, a second transmitted pre-decoding matrix indicator field, or a second phase tracking reference signal and demodulation reference signal association field.

[0183] In a third aspect, alone or in combination with one or more of the first and second aspects, indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is based at least in part on whether the configuration information is for an active BWP configuration of at least two CORESETs associated with different CORESET pool index values.

[0184] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1100 includes indicating that the one or more DCI communications are associated with the mDCI mode based at least in part on the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP configuration.

[0185] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, process 1100 includes indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on prohibiting the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0186] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 1100 includes sending to the UE a simultaneous transmission configuration indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

[0187] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the simultaneous transmission configuration is associated with at least one of a bandwidth part or a component carrier.

[0188] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1100 includes: indicating that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

[0189] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, process 1100 includes indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration indicating that the simultaneous transmission mode is not enabled.

[0190] In a tenth aspect, alone or in combination with one or more of aspects one to nine, process 1100 includes: indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration, the simultaneous transmission configuration indicating at least one of: a spatial domain multiplexing mode is enabled for simultaneous transmission, a frequency domain multiplexing mode is enabled for simultaneous transmission, or a single frequency network mode is enabled for simultaneous transmission.

[0191] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the simultaneous transmission configuration is associated with at least one DCI format.

[0192] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the simultaneous transmission configuration indicates that a first DCI format is associated with the mDCI mode, and the simultaneous transmission configuration indicates that a second DCI format different from the first DCI format is associated with the sDCI mode.

[0193] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 1100 includes: using the first DCI format to send a first DCI communication associated with the mDCI mode to the UE, and using the second DCI format to send a second DCI communication associated with the sDCI mode to the UE.

[0194] In a fourteenth aspect, either alone or in combination with one or more of aspects one to thirteen, indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is based at least in part on whether two of the at least two SRS resource sets are associated with a DCI format associated with the one or more DCI communications.

[0195] In a fifteenth aspect, either alone or in combination with one or more of aspects one to fourteen, process 1100 includes indicating that the one or more DCI communications are associated with the mDCI mode based at least in part on only one of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0196] In a sixteenth aspect, either alone or in combination with one or more of aspects one to fifteen, process 1100 includes indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on two of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0197] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1100 includes: sending a first DCI communication associated with the first uplink communication among the one or more DCI communications to the UE, wherein the first DCI communication is associated with the sDCI mode; and sending a second DCI communication associated with the second uplink communication among the one or more DCI communications to the UE, which at least partially overlaps with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

[0198] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the first DCI communication indicates that two SRS resource sets of the at least two SRS resource sets are associated with the first uplink communication.

[0199] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the first DCI communication indicates, via an SRS resource set indicator field indicating at least one of code point 10 or code point 11 associated with the first DCI communication, that the two SRS resource sets are associated with the first uplink communication.

[0200] In the twentieth aspect, alone or in combination with one or more of aspects one to nineteen, process 1100 includes: receiving capability information from the UE indicating the ability of the UE to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein sending the first DCI communication and the second DCI communication is based at least in part on the capability information.

[0201] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, the first DCI communication is associated with a first CORESET pool index value and the second DCI communication is associated with a second CORESET pool index value.

[0202] In the twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, the first CORESET pool index value is associated with two SRS resource sets of the at least two SRS resource sets, and the second CORESET pool index value is associated with the two SRS resource sets of the at least two SRS resource sets.

[0203] In the twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, the first CORESET pool index value is associated with a first set of two SRS resource sets among the at least two SRS resource sets, and the second CORESET pool index value is associated with a second set of two SRS resource sets among the at least two SRS resource sets.

[0204] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0205] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE (e.g., UE 120), or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a network node, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include a determining component 1208, among other things.

[0206] In some aspects, the apparatus 1200 may be configured to perform 9A to 9D Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 The process 1000. In some aspects, Fig.12The apparatus 1200 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the UE 120. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0207] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 The UE 120 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0208] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE 120. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0209] The receiving component 1202 may receive configuration information indicating a configuration of at least two SRS resource sets from a network node. The receiving component 1202 may receive one or more DCI communications associated with one or more uplink communications. The receiving component 1202 may receive an indication from the network node whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information.

[0210] Determining component 1208 can determine that the one or more DCI communications are associated with the mDCI mode based at least in part on configuring the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0211] Determining component 1208 may determine that the one or more DCI communications are associated with the sDCI mode based at least in part on refraining from configuring the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0212] The receiving component 1202 may receive, from the network node, a simultaneous transmission configuration associated with the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

[0213] Determining component 1208 can determine that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

[0214] The determination component 1208 may determine that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is not enabled for simultaneous transmission and the simultaneous transmission configuration indicating at least one of the following: a spatial domain multiplexing mode is enabled for simultaneous transmission, a frequency domain multiplexing mode is enabled for simultaneous transmission, or a single frequency network mode is enabled for simultaneous transmission.

[0215] Determining component 1208 can determine that the first DCI communication is associated with the mDCI mode based at least in part on the first DCI communication being associated with the first DCI format.

[0216] Determining component 1208 may determine that the second DCI communication is associated with the sDCI mode based at least in part on the second DCI communication being associated with the second DCI format.

[0217] Determining component 1208 can determine that the one or more DCI communications are associated with the mDCI mode based at least in part on only one of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0218] The determining component 1208 may determine that the one or more DCI communications are associated with the sDCI mode based at least in part on two SRS resource sets of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0219] The receiving component 1202 may receive a first DCI communication associated with a first uplink communication from the one or more DCI communications from the network node, wherein the first DCI communication is associated with the sDCI mode.

[0220] The receiving component 1202 may receive from the network node a second DCI communication of the one or more DCI communications associated with a second uplink communication, the second uplink communication at least partially overlapping with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

[0221] The sending component 1204 may send capability information to the network node indicating an ability to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein receiving the first DCI communication and the second DCI communication is based at least in part on the capability information.

[0222] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The assembly of (one or more) components shown may be described as being executable by Fig.12 Another collection of components shown performs one or more functions.

[0223] Fig.131 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network node (e.g., network node 110), or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a network node, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include one or more of a configuration component 1308 or an indication component 1310, etc.

[0224] In some aspects, the apparatus 1300 may be configured to perform 9A to 9D Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the network node 110. Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0225] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 The network node 110 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0226] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node 110. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0227] The transmitting component 1304 and / or the configuring component 1308 may transmit configuration information indicating the configuration of at least two SRS resource sets to the UE. The transmitting component 1304 may transmit one or more DCI communications associated with one or more uplink communications to the UE. The indicating component 1310 may indicate to the UE whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information.

[0228] Indicating component 1310 may indicate that the one or more DCI communications are associated with the mDCI mode based at least in part on configuring the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0229] The indicating component 1310 may indicate that the one or more DCI communications are associated with the sDCI mode based at least in part on refraining from configuring the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0230] The transmitting component 1304 and / or the configuring component 1308 may transmit to the UE a simultaneous transmission configuration indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

[0231] Indicating component 1310 can indicate that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

[0232] The indicating component 1310 may indicate that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration indicating that the simultaneous transmission mode is not enabled.

[0233] The indication component 1310 may indicate that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration, wherein the simultaneous transmission configuration indicates at least one of: a spatial domain multiplexing mode is enabled for simultaneous transmission, a frequency domain multiplexing mode is enabled for simultaneous transmission, or a single frequency network mode is enabled for simultaneous transmission.

[0234] Transmitting component 1304 can transmit a first DCI communication associated with the mDCI mode to the UE using the first DCI format.

[0235] The transmitting component 1304 may transmit a second DCI communication associated with the sDCI mode to the UE using the second DCI format.

[0236] Indicating component 1310 may indicate that the one or more DCI communications are associated with the mDCI mode based at least in part on only one of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0237] The indicating component 1310 may indicate that the one or more DCI communications are associated with the sDCI mode based at least in part on two SRS resource sets of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0238] The sending component 1304 can send a first DCI communication associated with the first uplink communication among the one or more DCI communications to the UE, wherein the first DCI communication is associated with the sDCI mode.

[0239] The sending component 1304 may send a second DCI communication associated with a second uplink communication among the one or more DCI communications to the UE, the second uplink communication at least partially overlapping with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

[0240] The receiving component 1302 may receive capability information from the UE indicating the UE's ability to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein sending the first DCI communication and the second DCI communication is based at least in part on the capability information.

[0241] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The assembly of (one or more) components shown may be described as being executable by Fig.13 Another collection of components shown performs one or more functions.

[0242] The following provides an overview of some aspects of the disclosure:

[0243] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving configuration information indicating the configuration of at least two SRS resource sets from a network node; receiving one or more DCI communications associated with one or more uplink communications; and receiving an indication from the network node whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode, wherein the indication is based at least in part on the configuration information.

[0244] Aspect 2: A method according to aspect 1, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode indicates whether one or more fields are included in the one or more DCI communications.

[0245] Aspect 3: A method according to aspect 2, wherein the one or more fields include at least one of the following: an SRS resource set indicator field, a second SRS resource indicator field, a second transmitted pre-decoding matrix indicator field, or a second phase tracking reference signal and demodulation reference signal association field.

[0246] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is based at least in part on whether the configuration information is an active BWP configuration of at least two CORESETs associated with different CORESET pool index values.

[0247] Aspect 5: According to the method of aspect 4, the method also includes: determining that the one or more DCI communications are associated with the mDCI mode based at least in part on the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP configuration.

[0248] Aspect 6: According to the method of Aspect 4, the method also includes: determining that the one or more DCI communications are associated with the sDCI mode based at least in part on prohibiting the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0249] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving from the network node a simultaneous transmission configuration associated with the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

[0250] Aspect 8: The method according to aspect 7, wherein the simultaneous transmission configuration is associated with at least one of a bandwidth part or a component carrier.

[0251] Aspect 9: According to any one of aspects 7 to 8, the method further includes: determining that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

[0252] Aspect 10: According to the method described in any one of Aspects 7 to 8, the method further includes: determining that the one or more DCI communications are associated with the sDCI mode at least in part based on the simultaneous transmission configuration indicating that the mDCI mode is not enabled for simultaneous transmission and the simultaneous transmission configuration indicating at least one of the following: the spatial domain multiplexing mode is enabled for simultaneous transmission, the frequency domain multiplexing mode is enabled for simultaneous transmission, or the single frequency network mode is enabled for simultaneous transmission.

[0253] Aspect 11: The method according to any one of aspects 7 to 10, wherein the simultaneous transmission configuration is associated with at least one DCI format.

[0254] Aspect 12: The method according to aspect 11, wherein the simultaneous transmission configuration indicates that a first DCI format is associated with the mDCI mode, and wherein the simultaneous transmission configuration indicates that a second DCI format different from the first DCI format is associated with the sDCI mode.

[0255] Aspect 13: According to the method described in Aspect 12, the method also includes: determining that the first DCI communication is associated with the mDCI mode based at least in part on the first DCI communication being associated with the first DCI format; and determining that the second DCI communication is associated with the sDCI mode based at least in part on the second DCI communication being associated with the second DCI format.

[0256] Aspect 14: A method according to any one of Aspects 1 to 13, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is at least partially based on whether two SRS resource sets of the at least two SRS resource sets are associated with a DCI format associated with the one or more DCI communications.

[0257] Aspect 15: According to the method of Aspect 14, the method also includes: determining that the one or more DCI communications are associated with the mDCI mode based at least in part on only one of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0258] Aspect 16: According to the method described in Aspect 14, the method also includes: determining that the one or more DCI communications are associated with the sDCI mode based at least in part on two SRS resource sets of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0259] Aspect 17: According to the method described in any one of Aspects 1 to 16, the method also includes: receiving a first DCI communication associated with a first uplink communication from the network node among the one or more DCI communications, wherein the first DCI communication is associated with the sDCI mode; and receiving a second DCI communication associated with a second uplink communication from the network node among the one or more DCI communications, wherein the second uplink communication at least partially overlaps with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

[0260] Aspect 18: The method according to aspect 17, wherein the first DCI communication indicates that two SRS resource sets of the at least two SRS resource sets are associated with the first uplink communication.

[0261] Aspect 19: The method according to aspect 18, wherein the first DCI communication indicates that the two SRS resource sets are associated with the first uplink communication via an SRS resource set indicator field indicating at least one of code point 10 or code point 11 associated with the first DCI communication.

[0262] Aspect 20: According to the method described in any one of Aspects 17 to 19, the method also includes: sending capability information to the network node indicating the ability to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein receiving the first DCI communication and the second DCI communication is at least partially based on the capability information.

[0263] Aspect 21: The method according to any one of aspects 17 to 20, wherein the first DCI communication is associated with a first CORESET pool index value, and wherein the second DCI communication is associated with a second CORESET pool index value.

[0264] Aspect 22: A method according to Aspect 21, wherein the first CORESET pool index value is associated with two SRS resource sets of the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with the two SRS resource sets of the at least two SRS resource sets.

[0265] Aspect 23: A method according to Aspect 21, wherein the first CORESET pool index value is associated with a first set of two SRS resource sets among the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with a second set of two SRS resource sets among the at least two SRS resource sets.

[0266] Aspect 24: A method of wireless communication performed by a network node, the method comprising: sending configuration information indicating the configuration of at least two SRS resource sets to a UE; sending one or more DCI communications associated with one or more uplink communications to the UE; and indicating to the UE whether the one or more DCI communications are associated with one or both of an sDCI mode or an mDCI mode based at least in part on the configuration information, wherein the indication is based at least in part on the configuration information.

[0267] Aspect 25: A method according to Aspect 24, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode also indicates whether one or more fields are included in the one or more DCI communications.

[0268] Aspect 26: A method according to Aspect 25, wherein the one or more fields include at least one of the following: an SRS resource set indicator field, a second SRS resource indicator field, a second transmitted pre-decoding matrix indicator field, or a second phase tracking reference signal and demodulation reference signal association field.

[0269] Aspect 27: A method according to any one of Aspects 24 to 26, wherein indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is at least partially based on whether the configuration information is an active BWP configuration of at least two CORESETs associated with different CORESET pool index values.

[0270] Aspect 28: The method according to aspect 27 further includes: indicating that the one or more DCI communications are associated with the mDCI mode based at least in part on the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP configuration.

[0271] Aspect 29: According to the method of Aspect 27, the method also includes: indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on prohibiting the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

[0272] Aspect 30: According to any one of Aspects 24 to 29, the method further includes: sending a simultaneous transmission configuration to the UE indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

[0273] Aspect 31: The method according to aspect 30, wherein the simultaneous transmission configuration is associated with at least one of a bandwidth part or a component carrier.

[0274] Aspect 32: According to any one of aspects 30 to 31, the method further includes: indicating that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

[0275] Aspect 33: According to any one of Aspects 30 to 31, the method further includes: indicating that the one or more DCI communications are associated with the sDCI mode at least in part based on the simultaneous transmission configuration indicating that the simultaneous transmission mode is not enabled.

[0276] Aspect 34: According to the method described in any one of Aspects 30 to 31, the method further includes: indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration, and the simultaneous transmission configuration indicates at least one of the following: the spatial domain multiplexing mode is enabled for simultaneous transmission, the frequency domain multiplexing mode is enabled for simultaneous transmission, or the single frequency network mode is enabled for simultaneous transmission.

[0277] Aspect 35: A method according to any one of aspects 30 to 34, wherein the simultaneous transmission configuration is associated with at least one DCI format.

[0278] Aspect 36: A method according to aspect 35, wherein the simultaneous transmission configuration indicates that a first DCI format is associated with the mDCI mode, and wherein the simultaneous transmission configuration indicates that a second DCI format different from the first DCI format is associated with the sDCI mode.

[0279] Aspect 37: According to the method according to Aspect 36, the method also includes: using the first DCI format to send a first DCI communication associated with the mDCI mode to the UE; and using the second DCI format to send a second DCI communication associated with the sDCI mode to the UE.

[0280] Aspect 38: A method according to any one of Aspects 24 to 37, wherein indicating whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is at least partially based on whether two SRS resource sets of the at least two SRS resource sets are associated with a DCI format associated with the one or more DCI communications.

[0281] Aspect 39: According to the method described in Aspect 38, the method also includes: indicating that the one or more DCI communications are associated with the mDCI mode based at least in part on the fact that only one of the at least two SRS resource sets is associated with the DCI format associated with the DCI communication.

[0282] Aspect 40: According to the method described in Aspect 38, the method also includes: indicating that the one or more DCI communications are associated with the sDCI mode based at least in part on two SRS resource sets of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

[0283] Aspect 41: According to the method described in any one of Aspects 24 to 40, the method also includes: sending a first DCI communication associated with a first uplink communication among the one or more DCI communications to the UE, wherein the first DCI communication is associated with the sDCI mode; and sending a second DCI communication associated with a second uplink communication among the one or more DCI communications to the UE, the second uplink communication at least partially overlapping with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

[0284] Aspect 42: The method according to aspect 41, wherein the first DCI communication indicates that two SRS resource sets of the at least two SRS resource sets are associated with the first uplink communication.

[0285] Aspect 43: A method according to aspect 42, wherein the first DCI communication indicates that the two SRS resource sets are associated with the first uplink communication via an SRS resource set indicator field indicating at least one of code point 10 or code point 11 associated with the first DCI communication.

[0286] Aspect 44: According to the method described in any one of Aspects 41 to 43, the method also includes: receiving capability information from the UE indicating the ability of the UE to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein sending the first DCI communication and the second DCI communication is at least partially based on the capability information.

[0287] Aspect 45: The method according to any one of aspects 41 to 44, wherein the first DCI communication is associated with a first CORESET pool index value, and wherein the second DCI communication is associated with a second CORESET pool index value.

[0288] Aspect 46: A method according to Aspect 45, wherein the first CORESET pool index value is associated with two SRS resource sets of the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with the two SRS resource sets of the at least two SRS resource sets.

[0289] Aspect 47: A method according to Aspect 45, wherein the first CORESET pool index value is associated with a first set of two SRS resource sets among the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with a second set of two SRS resource sets among the at least two SRS resource sets.

[0290] Aspect 48: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 23.

[0291] Aspect 49: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 23.

[0292] Aspect 50: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 1 to 23.

[0293] Aspect 51: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 23.

[0294] Aspect 52: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 23.

[0295] Aspect 53: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 24 to 47.

[0296] Aspect 54: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 24 to 47.

[0297] Aspect 55: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 24 to 47.

[0298] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 24 to 47.

[0299] Aspect 57: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 24 to 47.

[0300] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0301] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0302] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0303] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of each aspect includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination with 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 ordering of a, b and c).

[0304] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one project is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving configuration information indicating configuration of at least two sounding reference signal (SRS) resource sets from a network node; receiving one or more downlink control information (DCI) communications associated with one or more uplink communications; as well as An indication of whether the one or more DCI communications are associated with one or both of a single DCI (sDCI) mode or a multiple DCI (mDCI) mode is received from the network node, wherein the indication is based at least in part on the configuration information.

2. The UE of claim 1 , wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode indicates whether one or more fields are included in the one or more DCI communications.

3. The UE according to claim 2, wherein the one or more fields include at least one of the following: SRS resource set indicator field, The second SRS resource indicator field, The second transmitted precoding matrix indicator field, or The second phase tracking reference signal and demodulation reference signal association field.

4. The UE of claim 1 , wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is based at least in part on whether the configuration information configures at least two CORESETs associated with different control resource set (CORESET) pool index values ​​for an active bandwidth part (BWP).

5. The UE of claim 4, wherein the one or more processors are further configured to determine that the one or more DCI communications are associated with the mDCI mode based at least in part on the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP configuration.

6. The UE of claim 4, wherein the one or more processors are further configured to determine that the one or more DCI communications are associated with the sDCI mode based at least in part on prohibiting configuring the configuration information of the at least two CORESETs associated with the different CORESET pool index values ​​for the active BWP.

7. The UE of claim 1, wherein the one or more processors are further configured to receive, from the network node, a simultaneous transmission configuration associated with the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

8. The UE of claim 7, wherein the simultaneous transmission configuration is associated with at least one of a bandwidth part or a component carrier.

9. The UE of claim 7, wherein the one or more processors are further configured to determine that the one or more DCI communications are associated with the mDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is enabled for simultaneous transmission.

10. The UE of claim 7, wherein the one or more processors are further configured to determine that the one or more DCI communications are associated with the sDCI mode based at least in part on the simultaneous transmission configuration indicating that the mDCI mode is not enabled for simultaneous transmission and the simultaneous transmission configuration indicating at least one of: The spatial domain multiplexing mode is enabled for simultaneous transmission, Frequency domain multiplexing mode is enabled for simultaneous transmission, or Single frequency network mode is enabled for simultaneous transmission. The UE according to claim 7 , wherein the simultaneous transmission configuration is associated with at least one DCI format.

12. The UE of claim 11, wherein the simultaneous transmission configuration indicates that a first DCI format is associated with the mDCI mode, and wherein the simultaneous transmission configuration indicates that a second DCI format different from the first DCI format is associated with the sDCI mode.

13. The UE of claim 12, wherein the one or more processors are further configured to: determining that the first DCI communication is associated with the mDCI mode based at least in part on the first DCI communication being associated with the first DCI format; and The second DCI communication is determined to be associated with the sDCI mode based at least in part on the second DCI communication being associated with the second DCI format.

14. A UE according to claim 1, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is at least partially based on whether two SRS resource sets of the at least two SRS resource sets are associated with a DCI format associated with the one or more DCI communications.

15. The UE of claim 14, wherein the one or more processors are further configured to determine that the one or more DCI communications are associated with the mDCI mode based at least in part on only one of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

16. A UE according to claim 14, wherein the one or more processors are further configured to: determine that the one or more DCI communications are associated with the sDCI mode based at least in part on two SRS resource sets of the at least two SRS resource sets being associated with the DCI format associated with the DCI communication.

17. The UE of claim 1, wherein the one or more processors are further configured to: receiving, from the network node, a first DCI communication of the one or more DCI communications associated with a first uplink communication, wherein the first DCI communication is associated with the sDCI mode; and A second DCI communication of the one or more DCI communications associated with a second uplink communication is received from the network node, the second uplink communication at least partially overlapping with the first uplink communication in the time domain, wherein the second DCI communication is associated with the mDCI mode.

18. The UE of claim 17, wherein the first DCI communication indicates that two SRS resource sets of the at least two SRS resource sets are associated with the first uplink communication.

19. The UE of claim 18, wherein the first DCI communication indicates, via an SRS resource set indicator field indicating at least one of code point 10 or code point 11 associated with the first DCI communication, that the two SRS resource sets are associated with the first uplink communication.

20. The UE of claim 17, wherein the one or more processors are further configured to: send capability information to the network node indicating an ability to support overlapping uplink communications associated with the sDCI mode and the mDCI mode, wherein receiving the first DCI communication and the second DCI communication is based at least in part on the capability information.

21. The UE of claim 17, wherein the first DCI communication is associated with a first control resource set (CORESET) pool index value, and wherein the second DCI communication is associated with a second CORESET pool index value.

22. The UE of claim 21, wherein the first CORESET pool index value is associated with two SRS resource sets of the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with the two SRS resource sets of the at least two SRS resource sets.

23. The UE of claim 21, wherein the first CORESET pool index value is associated with a first set of two SRS resource sets in the at least two SRS resource sets, and wherein the second CORESET pool index value is associated with a second set of two SRS resource sets in the at least two SRS resource sets.

24. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: sending configuration information indicating configuration of at least two sounding reference signal (SRS) resource sets to a user equipment (UE); sending one or more downlink control information (DCI) communications associated with one or more uplink communications to the UE; as well as Indicating to the UE whether the one or more DCI communications are associated with one or both of a single DCI (sDCI) mode or a multiple DCI (mDCI) mode based at least in part on the configuration information, wherein the indicating is based at least in part on the configuration information.

25. The network node of claim 24, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode further indicates whether one or more fields are included in the one or more DCI communications.

26. The network node of claim 25, wherein the one or more fields include at least one of: SRS resource set indicator field, The second SRS resource indicator field, The second transmitted precoding matrix indicator field, or The second phase tracking reference signal and demodulation reference signal association field.

27. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving configuration information indicating configuration of at least two sounding reference signal (SRS) resource sets from a network node; receiving one or more downlink control information (DCI) communications associated with one or more uplink communications; as well as An indication of whether the one or more DCI communications are associated with one or both of a single DCI (sDCI) mode or a multiple DCI (mDCI) mode is received from the network node, wherein the indication is based at least in part on the configuration information.

28. The method of claim 27, wherein the indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode is based at least in part on whether the configuration information configures at least two CORESETs associated with different control resource set (CORESET) pool index values ​​for an active bandwidth part (BWP).

29. A method of wireless communication performed by a network node, the method comprising: sending configuration information indicating configuration of at least two sounding reference signal (SRS) resource sets to a user equipment (UE); sending one or more downlink control information (DCI) communications associated with one or more uplink communications to the UE; as well as Indicating to the UE whether the one or more DCI communications are associated with one or both of a single DCI (sDCI) mode or a multiple DCI (mDCI) mode based at least in part on the configuration information, wherein the indicating is based at least in part on the configuration information.

30. The method according to claim 29, further comprising: A simultaneous transmission configuration is transmitted to the UE along with an indication of whether the one or more DCI communications are associated with one or both of the sDCI mode or the mDCI mode.

Images