Physical uplink shared channel partitioning for reporting time domain channel state information

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive, during a physical downlink control channel (PDCCH) occasion, scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH occasion, where the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content includes time domain channel state information (TD CSI) and additional uplink information. The UE may perform a PUSCH partitioning operation, where the first PUSCH occasion and the second PUSCH occasion correspond to the scheduled PUSCH communication, where performing the PUSCH partitioning operation includes transmitting the additional uplink information during the first PUSCH occasion and transmitting the TD CSI during the second PUSCH occasion. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for physical uplink shared channel partitioning for reporting time-domain channel state information. Background Art

[0002] 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).

[0003] 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.).

[0004] 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 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. 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

[0005] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity during a physical downlink control channel (PDCCH) opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including time domain channel state information (TD CSI) and additional uplink information. The one or more processors may be configured to perform a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein in order to perform the PUSCH split operation, the one or more processors are configured to send the additional uplink information during the first PUSCH opportunity and send the TD CSI during the second PUSCH opportunity.

[0006] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity during a PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information. The one or more processors may be configured to receive the additional uplink information during the first PUSCH opportunity. The one or more processors may be configured to receive the TD CSI during a second PUSCH opportunity.

[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TDCSI and additional uplink information. The method may include performing a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein performing the PUSCH split operation includes sending the additional uplink information during the first PUSCH opportunity and sending the TD CSI during the second PUSCH opportunity.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity during a PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TDCSI and additional uplink information. The method may include receiving the additional uplink information during the first PUSCH opportunity. The method may include receiving TD CSI during a second PUSCH opportunity.

[0009] 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 scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity during a PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information. The instruction set, when executed by one or more processors of the UE, may cause the UE to perform a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein the one or more instructions causing the UE to perform the PUSCH split operation are configured to cause the UE to send additional uplink information during the first PUSCH opportunity and to send TD CSI during the second PUSCH opportunity.

[0010] 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 scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity during a PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive additional uplink information during the first PUSCH opportunity. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive TD CSI during a second PUSCH opportunity.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including a TDCSI and additional uplink information. The apparatus may include means for performing a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein the means for performing the PUSCH split operation includes means for sending the additional uplink information during the first PUSCH opportunity and means for sending the TDCSI during the second PUSCH opportunity.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TDCSI and additional uplink information. The apparatus may include means for receiving the additional uplink information during the first PUSCH opportunity. The apparatus may include means for receiving TD CSI during a second PUSCH opportunity.

[0013] The various aspects generally 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.

[0014] 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 to the claims.

[0015] 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 various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate 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.

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

[0018] 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.

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

[0020] Figure 4 is a diagram illustrating an example of channel state information (CSI) reference signal (CSI-RS) beam management according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of physical uplink shared channel (PUSCH) partitioning for reporting time domain CSI according to the present disclosure.

[0022] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0024] Figure 8 is a diagram of an example apparatus for wireless communications according to the present disclosure.

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

[0026] 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 interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, 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 present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present 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 devices or methods implemented using other structures, functions, or structures and functions 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 claims.

[0027] 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 can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] 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 post-5G RATs (e.g., 6G).

[0029] 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). For 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)).

[0030] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. 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.

[0031] 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 micro 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 micro 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 micro cell may be referred to as a micro 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, 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. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0032] 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 number 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 repeat the execution of 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.

[0033] 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, 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.

[0034] In some aspects, the wireless network 100 may include one or more non-terrestrial network (NTN) deployments, where non-terrestrial wireless communication devices may include UEs (interchangeably referred to herein as "non-terrestrial UEs") and / or another network node (interchangeably referred to herein as a "non-terrestrial network node"). Non-terrestrial network nodes may include, for example, base stations (interchangeably referred to herein as "non-terrestrial base stations") and / or relay stations (interchangeably referred to herein as "non-terrestrial relay stations"), etc. As used herein, "NTN" may refer to a network to which access is facilitated by non-terrestrial UEs and / or non-terrestrial network nodes.

[0035] The wireless network 100 may include any number of non-terrestrial wireless communication devices. The non-terrestrial wireless communication devices may include satellites, manned aircraft systems, unmanned aircraft system (UAS) platforms, and the like. Satellites may include low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, geostationary orbit (GEO) satellites, and / or high elliptical orbit (HEO) satellites, and the like. Manned aircraft systems may include airplanes, helicopters, and / or airships, and the like. UAS platforms may include high altitude platform stations (HAPS), and may include balloons, airships, and / or airplanes, and the like. The non-terrestrial wireless communication devices may be a part of the NTN that is separate from the wireless network 100. Alternatively, the NTN may be part of the wireless network 100. Satellites may communicate directly and / or indirectly with other entities in the wireless network 100 using satellite communications. Other entities may include UEs (e.g., ground UEs and / or non-terrestrial UEs), other satellites in one or more NTN deployments, other types of network nodes (e.g., stationary or ground-based network nodes), relay stations, and / or one or more components and / or devices included in the core network of the wireless network 100, and the like.

[0036] 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).

[0037] 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 backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0038] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations and / or subscriber units. UE 120 can 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.

[0039] 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 operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] 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.

[0041] 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.

[0042] 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 ranges designated 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 a “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 a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0043] 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.

[0044] In view of 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 can be broadly referred to as frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can 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) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity during a physical downlink control channel (PDCCH) opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including time domain channel state information (TDCSI) and additional uplink information; and perform a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein performing the PUSCH split operation includes: sending the additional uplink information during the first PUSCH opportunity; and sending the TD CSI during the second PUSCH opportunity. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, the network node may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity during a PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information; receive the additional uplink information during the first PUSCH opportunity; and receive the TD CSI during the second PUSCH opportunity. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

[0048] 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.

[0049] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the 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-decoding) 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 set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0050] 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.

[0051] 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.

[0052] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a group of coplanar antenna elements, a group 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).

[0053] Each of the antenna elements may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element that is cross-polarized with a second sub-element, which can be used to independently transmit a cross-polarized signal. The antenna elements may include patch antennas, dipole antennas, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between the antenna elements may be such that signals having desired wavelengths respectively transmitted by the antenna elements may interact or interfere (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half wavelength, or other fraction of a wavelength of the spacing between adjacent antenna elements to allow interaction or interference of signals transmitted by separate antenna elements within the desired range.

[0054] Antenna elements and / or sub-elements may be used to generate beams. A "beam" may specify a wireless signal that is transmitted in a direction, such as in the direction of a recipient device. A beam may include a directional signal, a direction associated with the signal, a set of directional resources associated with the signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters indicating one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal.

[0055] As indicated above, antenna elements and / or sub-elements can be used to generate beams. For example, antenna elements can be individually selected or deselected for transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers. Beamforming includes generating beams using multiple signals on different antenna elements, wherein one or more or all of the multiple signals are shifted in phase relative to each other. The formed beams may carry physical or higher layer reference signals or information. When each of the multiple signals is radiated from the corresponding antenna element, the radiated signals interact, interfere (constructively and destructively), and amplify with each other to form the resulting beam. The shape (such as amplitude, width, and / or the presence of side lobes) and direction (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shift or phase offset of the multiple signals relative to each other.

[0056] Beamforming may be used for communication between a UE and a base station, such as for millimeter wave communication, etc. In this case, the base station may provide the UE with a configuration of a transmit configuration indicator (TCI) state, which respectively indicates beams that may be used by the UE, such as for receiving a physical downlink shared channel (PDSCH). The base station may indicate an activated TCI state to the UE, and the UE may use the activated TCI state to select a beam for receiving the PDSCH.

[0057] The beam indication may be or include a TCI state information element, a beam identifier (ID), spatial relationship information, a TCI state ID, a closed loop index, a panel ID, a TRP ID, and / or a sounding reference signal (SRS) set ID, etc. The TCI state information element (referred to herein as TCI state) may indicate information associated with a beam such as a downlink beam. For example, the TCI state information element may indicate a TCI state identifier (e.g., tci-StateID), a quasi co-location (QCL) type (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, qcl-TypeD, etc.), a cell identifier (e.g., ServCellIndex), a bandwidth part identifier (bwp-Id), a reference signal identifier (such as CSI-RS (e.g., NZP-CSI-RS-ResourceId, SSB-Index, etc.)), etc. The spatial relationship information may similarly indicate information associated with an uplink beam.

[0058] The beam indication may be a joint or separate downlink (DL) / uplink (UL) beam indication in a unified TCI framework. In some cases, the network may use at least UE-specific (unicast) downlink control information (DCI) to indicate a joint or separate DL / UL beam indication from an active TCI state, thereby supporting layer 1 (L1) based beam indication. In some cases, existing DCI formats 1_1 and / or 1_2 may be reused for beam indication. The network may include a support mechanism for the UE to confirm successful decoding of the beam indication. For example, an acknowledgment / negative acknowledgment (ACK / NACK) of a PDSCH scheduled by a DCI carrying a beam indication may also be used as an ACK for the DCI.

[0059] Beam indication may be provided for carrier aggregation (CA) scenarios. In a unified TCI framework, the network may support common TCI state ID update and activation information to provide common QCL and / or one or more common UL transmit spatial filters across a set of configured component carriers (CCs). This type of beam indication may be applicable to intra-band CA as well as joint DL / UL beam indication and separate DL / UL beam indication. A common TCI state ID may mean that a reference signal (RS) determined according to the TCI state indicated by the common TCI state ID is used to provide QCL type D indication and determine the UL transmit spatial filter across a set of configured CCs.

[0060] 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 Figures 5 to 9 ) any aspects of any of the methods described.

[0061] 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 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 operations described herein (e.g., with reference to Figures 5 to 9 ) any aspects of any of the methods described.

[0062] 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 network node 110 may perform one or more techniques associated with PUSCH segmentation for reporting time domain channel state information, as described in more detail elsewhere herein. For example, 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 Figure 6 The process of 600 Figure 7 10 and / or operations of process 700 and / or 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, or after compilation, conversion and / or interpretation), may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 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.

[0063] In some aspects, a UE (e.g., UE 120) includes means for receiving, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information; and / or means for performing a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein the means for performing the PUSCH split operation includes means for sending the additional uplink information during the first PUSCH opportunity and / or means for sending the TD CSI during the second PUSCH opportunity. Means for the UE to perform operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0064] In some aspects, a network node (e.g., network node 110) includes means for sending, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information; means for receiving the additional uplink information during the first PUSCH opportunity; and / or means for receiving the TD CSI during the second PUSCH opportunity. In some aspects, means for the network node 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.

[0065] 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.

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

[0067] 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 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 BS, 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. A "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).

[0068] An aggregated base station (e.g., an aggregated network node) can 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) can 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 can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can 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), etc.

[0069] 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.

[0070] 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-RT RIC 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.

[0071] 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 configured to receive or transmit 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 transmit signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0072] 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 divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit 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.

[0073] 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 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 also 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.

[0074] 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 partitioning (e.g., functional partitioning defined by 3GPP). 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 communications 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.

[0075] 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-RT RIC 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.

[0076] 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 in communication 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.

[0077] 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).

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

[0079] Figure 4 4 is a diagram illustrating an example 400 of channel state information (CSI) reference signal (CSI-RS) beam management according to the present disclosure. Figure 4 As shown in , example 400 includes a UE 120 communicating with a network node 110 in a wireless network (eg, wireless network 100). However, Figure 4 The devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and network node 110 or TRP, between mobile terminal node and control node, between IAB child node and IAB parent node, and / or between scheduled node and scheduling node). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., RRC connected state).

[0080] like Figure 4 As shown in , example 400 may include a network node 110 (e.g., one or more network node devices such as RU, DU and / or CU, etc.) and a UE 120 communicating to perform beam management using CSI-RS. As shown by reference numeral 402, the CSI-RS may be configured to be sent from the network node 110 to the UE 120. The CSI-RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using medium access control (MAC) control element (MAC-CE) signaling) and / or aperiodic (e.g., using DCI).

[0081] The first beam management process (e.g., P1 CSI-RS beam management) may include the network node 110 performing beam scanning on multiple transmit (Tx) beams. The network node 110 may transmit a CSI-RS using each transmit beam used for beam management. In order to enable the UE 120 to perform receive (Rx) beam scanning, the network node may transmit each CSI-RS multiple times (e.g., with repetitions) within the same RS resource set using a transmit beam, so that the UE 120 can sweep the receive beam in multiple transmit instances. For example, if the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be transmitted M times on each of the N transmit beams, so that the UE 120 may receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam scanning on the receive beam of the UE 120. Thus, the first beam management process may enable UE 120 to measure CSI-RS on different transmit beams using different receive beams to support selection of a network node 110 transmit beam / UE 120 receive beam pair. UE 120 may report the measurements to network node 110 to enable network node 110 to select one or more beam pairs for communication between network node 110 and UE 120.

[0082] The second beam management process (e.g., P2 CSI-RS beam management) may be referred to as a beam refinement process, a network node beam refinement process, a TRP beam refinement process, and / or a transmit beam refinement process. The second beam management process may include the network node 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (e.g., determined at least in part based on measurements reported by the UE 120 in conjunction with the first beam management process). The network node 110 may transmit a CSI-RS using each of the one or more transmit beams used for beam management. The UE 120 may measure each CSI-RS using a single (e.g., identical) receive beam (e.g., determined at least in part based on measurements performed in conjunction with the first beam management process). The second beam management process may enable the network node 110 to select the best transmit beam based at least in part on measurements of the CSI-RS reported by the UE 120 (e.g., measured by the UE 120 using a single receive beam).

[0083] The third beam management process (e.g., P3 CSI-RS beam management) may be referred to as a beam refinement process, a UE beam refinement process, and / or a receive beam refinement process. The third beam management process may include the network node 110 transmitting one or more CSI-RS using a single transmit beam (e.g., determined based at least in part on measurements reported by the UE 120 in conjunction with the first beam management process and / or the second beam management process). In order to enable the UE 120 to perform receive beam scanning, the network node may transmit the CSI-RS multiple times (e.g., with repetitions) within the same RS resource set using the transmit beam, so that the UE 120 may sweep across one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (e.g., determined based at least in part on measurements performed in conjunction with the first beam management process and / or the second beam management process). The third beam management process may enable the network node 110 and / or the UE 120 to select the best receive beam based at least in part on reported measurements received from the UE 120 (eg, the reported measurements are measurements of the CSI-RS of the transmit beam using the one or more receive beams).

[0084] For type I CSI feedback, the codebook for CSI may define a set of discrete Fourier transform (DFT) beams 404 in the spatial domain. In some aspects, each beam 404 in the set of beams 404 is orthogonal to the other beams 404 in the set of beams 404. In some aspects, the beam 404 may be represented by a DFT vector and / or may be identified by a beam index (e.g., b1, b2, etc.). The network node 110 may send CSI-RS for a set of beams 404 in the codebook, and the UE 120 may measure the CSI-RS for a set of candidate beams 404 (e.g., one or more beams in the codebook). The UE 120 may select the best beam 404 or a set of best beams 404 among the set of candidate beams 404 based at least in part on the measurement. The UE 120 may send CSI feedback (e.g., in a CSI report) to the network node 110 to indicate the selected beam 404. For example, a precoding matrix indicator (PMI) may be used to indicate the selected beam 404. However, using Type I CSI feedback may limit the spatial resolution of the beam 404 (e.g., candidate beams may be limited to beams in the codebook) and may result in the selection of a beam 404 that is worse than the beam that could otherwise be used (e.g., by linearly combining multiple DFT vectors corresponding to different beams 404). The UE 120 and the network node 110 may communicate using the selected beam 404 or a beam 404 selected from a set of beams 404.

[0085] For Type II CSI feedback, the codebook for the CSI may include multiple oversampled DFT beams 406, which may not all be orthogonal to each other. In some aspects, the beams 406 included in the codebook may be divided into multiple groups of orthogonal beams 406. The UE 120 may measure the CSI-RS, may select a group (e.g., a best group) based at least in part on the measurement, and may analyze different linear combinations of two or more beams 406 in the group. The UE 120 may determine whether any of the linear combinations forms a beam 406 with better spatial resolution than a single beam 406 in the group. If so, the UE 120 may send CSI feedback (e.g., in a CSI report) indicating the beam index of the selected beam to be combined (in Figure 4 and the linear combination coefficients (shown as b1 and b2 in ) to be applied to each selected beam to form a beam with better spatial resolution Figure 4 UE 120 and / or network node 110 may configure beams using the indicated beam indices and linear combination coefficients (sometimes referred to herein as “coefficients”) and may communicate via the configured beams.

[0086] In some aspects, UE 120 may report CSI feedback for multiple subbands (e.g., each subband via which UE 120 can communicate with base station 110). In this case, UE 120 may report beam indices and corresponding coefficients for multiple subbands (e.g., each subband). In some aspects, beam indices may be shared across subbands, but different subbands may be associated with different coefficients (e.g., different amplitude coefficients, different phase coefficients, etc.). Thus, Type II CSI feedback may consume more overhead than Type ICSI feedback, but may result in better beams for communication, resulting in higher throughput, lower latency, less likelihood of beam failure, etc. To reduce the overhead for Type II CSI feedback, UE 120 and / or base station 110 may employ Type II CSI compression.

[0087] In Type II CSI compression, the precoding matrix W for the transmitted layer is available Indicates that is the space-domain matrix formed using the selected space-domain basis, is the frequency domain matrix formed using the selected frequency domain basis, and is a coefficient matrix. However, the type II precoding matrix may be ineffective for high-speed UEs (eg, vehicular UEs and / or non-terrestrial UEs, etc.).

[0088] For high-speed UEs (which result in high-speed channels), the UE may use a time domain (TD) codebook to provide TD CSI, where the codebook is used to convert fast-changing (over time instances) Change) The pre-decoding matrix is ​​expressed as . The coefficient matrix Compression into the Doppler domain can be beneficial in reducing the overhead of CSI reporting associated with high-speed channels. For example, time instances 0, ..., -1 may correspond to an observation, and the time instance +1, ..., It may correspond to the extrapolated CSI measurement result. In some cases, the spatial domain basis and the frequency domain basis may be generally constant, while the coefficient matrix may change as the UE moves. In some cases, for example, the UE may only report the CSI-RS observation result ( In this case, CSI compression occurs at the UE and extrapolation occurs at the network node. In some cases, both observations and extrapolation results may be reported at the UE (e.g., ). In this case, both compression and extrapolation occur at the UE.

[0089] In some aspects, for example, UE 120 may, at time instance n trigger The CSI report trigger is detected at the measurement window W. meas UE 120 may be configured to transmit TD CSI at time instance n using PUSCH transmission during a PUSCH opportunity. For TD CSI reporting, the PDCCH to PUSCH distance K2 may be configured to be long enough to accommodate the measured CSI-RS opportunity, which may result in additional latency for uplink shared channel data and / or other (non-TD) CSI reports, which may also be delivered during a PUSCH opportunity. For example, a CSI-RS burst with a 5-slot period and 4 opportunities may require at least time slots for PDCCH to PUSCH offset, where Z' corresponds to the CSI processing timeline and the CSI reference cell time slot associated with the CSI reference signal resource (which may be denoted as time slot n ref ) and the PUSCH opportunity may correspond to the floor(Z' / 14) term. In some aspects, for example, Z' may include 69 symbols with a 30kHz subcarrier spacing (SCS). Therefore, the reporting of TD CSI may result in increased latency in uplink transmissions, thereby negatively impacting network performance.

[0090] Some aspects of the techniques and devices described herein may facilitate performing a split PUSCH operation, wherein TD CSI is sent during a deferred PUSCH opportunity, and the remaining scheduled uplink content is sent during a first scheduled PUSCH opportunity. For example, in some aspects, a UE may receive scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity during a PDCCH opportunity. The scheduling information may indicate a set of uplink content associated with the scheduled PUSCH communication. The set of uplink content may include TD CSI and additional uplink information. The UE may perform a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication. In order to perform the PUSCH split operation, the UE may send additional uplink information during the first PUSCH opportunity and send TD CSI during the second PUSCH opportunity. Therefore, some aspects of the techniques and devices described herein may facilitate splitting the scheduled PUSCH communication, deferring the transmission of TD CSI so that other uplink content can be sent in the scheduled PUSCH opportunity. In this way, some aspects may facilitate reporting TD CSI without increasing latency in the transmission of other uplink content, thereby positively affecting network performance.

[0091] As indicated above, Figure 4 is provided as an example of a beam management process. Other examples of beam management processes can be found in Figure 4 For example, UE 120 and network node 110 may perform the third beam management procedure before performing the second beam management procedure, and / or UE 120 and network node 110 may perform a similar beam management procedure to select a UE transmit beam.

[0092] Figure 5 5 is a diagram illustrating an example 500 of PUSCH segmentation for reporting TD CSI according to the present disclosure. Figure 5 As shown, UE 502 and network node 504 may communicate with each other.

[0093] As indicated by reference numeral 506, the network node 504 may send and the UE 502 may receive configuration information. For example, the network node 504 may send and the UE 502 may receive an RRC configuration. The RRC configuration may be associated with a split PUSCH operation. In some aspects, the RRC configuration may indicate a slot offset corresponding to a second PUSCH opportunity in a first PUSCH opportunity and a second PUSCH opportunity corresponding to the split PUSCH operation. In some aspects, the RRC configuration may include an indication to perform a PUSCH split operation.

[0094] As indicated by reference numeral 508, the network node 504 may send and the UE 502 may receive scheduling information. For example, in some aspects, during the PDCCH opportunity 510, the network node 504 may send and the UE 502 may receive scheduling information. The scheduling information may indicate a scheduled PUSCH communication corresponding to the first PUSCH opportunity 512. In some aspects, the scheduling information may indicate a set of uplink content associated with the scheduled PUSCH communication. The set of uplink content may include TD CSI and additional uplink information. For example, in some aspects, the additional uplink information may include at least one of uplink data, an acknowledgement indication, or non-TD CSI.

[0095] In some aspects, the UE 502 may receive scheduling information based on receiving a DCI transmission indicating the scheduling information. In some aspects, the DCI transmission may include an indication to perform a PUSCH split operation. The indication to perform a PUSCH split operation may include an indication of a split PUSCH slot offset X (e.g., shown as "X slot") associated with the second PUSCH opportunity 514. In some aspects, the indication of the split PUSCH slot offset X may be indicated by an indication of a value of X and / or by a value of the sum of the PDCCH to PUSCH slot offset K2 and the split PUSCH slot offset K2+X (K2+X). In some aspects, the scheduling information indicates a time domain resource allocation (TDRA). The TDRA may indicate a value of K2. In some aspects, the value of the split PUSCH slot offset X may be RRC configured.

[0096] In some aspects, the UE may set the width of the TD CSI measurement window to meas The value of the split PUSCH time slot offset X is reused. For example, the scheduling information may include an indication of reusing the TD CSI measurement window width. For example, as shown in the figure, the TD CSI measurement window width W meas A quantity N may include time units 516 (shown as "T units") ob (Shown as N ob = 4 time units). The time unit may include, for example, a symbol, a slot, a subslot, and / or a microsecond, etc. The amount of the time unit may include a CSI window width W CSI A subset of time units of a CSI window (shown as N4 ≥ 4) within which CSI-RS 518 is transmitted by network node 504 and received by UE 502. Each time unit may have T unit The length of the split PUSCH slot, and therefore, the split PUSCH slot offset X can be determined as X=W meas =N ob +T unit .

[0097] In some aspects, the DCI transmission may include an indication of at least one parameter associated with both the first PUSCH opportunity 512 and the second PUSCH opportunity 514. In some aspects, the at least one parameter may indicate at least one of a frequency domain source allocation (FDRA), an MCS, an SRS source indicator (SRI), a number of layers, a precoding matrix, an antenna port, a frequency hopping operation, an open loop power control, or a TDRA parameter. The TDRA parameters may include, for example, a start and length indicator value (SLIV) and / or a DMRS mapping type, among others. In some aspects, the DCI transmission may include a first indication of a first set of TDRA parameters associated with the first PUSCH opportunity 512 and a second indication of a second set of TDRA parameters associated with the second PUSCH opportunity 514.

[0098] In some aspects, the UE 502 may perform a PUSCH split operation. The PUSCH split operation may include transmissions during a first PUSCH opportunity 512 and a second PUSCH opportunity 514, wherein the first PUSCH opportunity 512 and the second PUSCH opportunity 514 correspond to scheduled PUSCH communications. For example, as indicated by reference numeral 520, during the first PUSCH opportunity 512, the UE 502 may transmit and the network node 504 may receive additional uplink information. As indicated by reference numeral 522, during the second PUSCH opportunity 514, the UE 502 may transmit and the network node 504 may receive TD CSI.

[0099] In some aspects, the UE 502 may perform a PUSCH split operation based on a set of uplink content. For example, a wireless communication standard may indicate that the UE 502 will perform a PUSCH split operation for any scheduled PUSCH communication including TD CSI. In some aspects, the scheduling information, DCI, and / or RRC configuration may include an indication to perform a PUSCH split operation. For example, in some aspects, the scheduling information may include an indication of a split PUSCH offset X. A specified value of the split PUSCH offset (e.g., X=0) may indicate that the UE 502 will not perform a split PUSCH operation, while any value other than the specified value may indicate that the UE 502 will perform a PUSCH split operation.

[0100] In some aspects, the UE 502 may perform a PUSCH split operation based on the TDRA failing to satisfy a split condition associated with the TD CSI processing timeline. In some aspects, the TDRA may fail to satisfy the split condition based on the first condition option and / or the second condition option. For example, in some aspects, the UE 502 may multiplex the TD CSI with the additional uplink content only when both condition options are satisfied.

[0101] For example, according to the first conditional option, the decision to perform a PUSCH split operation may be based on whether the indicated TDRA (including K2) for scheduling PUSCH satisfies the TD CSI calculation timeline. If not, the UE 502 may perform a PUSCH split operation, and if the condition is met, the UE 502 may multiplex the TD CSI with the additional uplink content. In some aspects, the TDRA may not meet the split condition based on at least a specified amount of symbols not being between the last CSI reference signal opportunity and the first PUSCH opportunity. For example, the specified amount of symbols may correspond to the TD CSI processing time Z'.

[0102] In some aspects, according to the second conditional option, based on at least a specified number of CSI reference signal opportunities being no later than time slot 524 (which may be denoted as time slot n) associated with the CSI reference signal resource. ref ) occurs, TDRA may not meet the segmentation condition. CSI reference resources may be defined for validation testing (e.g., a target block error rate (BLER) of 10%) with reported CQI (and PMI, if also reported). The frequency resource of the CSI reference signal resource may be the same frequency resource as the measurement CSI-RS 518 in the frequency domain. The time resource of the CSI reference signal resource may be a valid downlink time slot. (In uplink time slot 526, during which TD CSI is reported). For example, for periodic or semi-periodic CSI reporting, Can be greater than or equal to (single CSI-RS) or (multiple CSI-RS) minimum value, so that the time slot Corresponds to the valid downlink time slot. For aperiodic CSI reporting, Can be greater than or equal to The minimum value of the time slot Corresponds to the valid downlink time slot (where The CSI reference signal resource may include a specified PDSCH pattern. The PDSCH pattern may indicate the symbols used within the time slot, the DMRS pattern, the SCS and / or the layer mapping pattern associated with the reported PMI, etc.

[0103] In some aspects, performing a PUSCH split operation may include avoiding updating the TDCSI during the first PUSCH opportunity 512. For example, if the UE 502 performs a PUSCH split operation, the UE 502 does not need to update the TD CSI during the first PUSCH opportunity 512. In some aspects, the UE 502 may include one or more padding bits in a field allocated for the TD CSI. In this way, the UE 502 may avoid performing a re-rate matching operation associated with the first PUSCH opportunity 512. In some aspects, the UE 502 may drop the TD CSI from the PUSCH transmission in the first PUSCH opportunity, in which case the UE 502 may perform a re-rate matching operation associated with the first PUSCH opportunity 512.

[0104] In some aspects, the UE 502 may send uplink control information (UCI) indicating the TD CSI during the second PUSCH opportunity 514, without also including uplink data. For example, the second PUSCH opportunity may be a UCI-only PUSCH opportunity. In some aspects, the TD CSI may be sent as UCI piggybacked on the PUSCH transmission. The UE 502 may receive an indication of at least one UCI decoding rate scaling factor. In some aspects, the at least one UCI decoding rate scaling factor may correspond to both the first PUSCH opportunity 512 and the second PUSCH opportunity 514. In some aspects, the at least one UCI decoding rate scaling factor may include a first UCI decoding rate scaling factor corresponding to the first PUSCH opportunity 512 and a second UCI decoding rate scaling factor corresponding to the second PUSCH opportunity 514.

[0105] For example, for UCI piggybacked on PUSCH, the offset The decoding rate of UCI may be reduced via RRC configuration and / or indicated by DCI, which may result in higher reliability than uplink shared channel transmissions (because uplink shared channel transmissions may be retransmitted using hybrid automatic repeat request (HARQ) retransmissions, while UCI may not be subject to HARQ retransmissions). In some aspects, if more than one If a value is configured for the first PUSCH opportunity 512, the DCI may further indicate the value (e.g., if 2 or 4 values ​​are configured, 1 or 2 bits in the DCI may be used to indicate the value). If each PUSCH opportunity 512 and 514 is associated with a different UCI coding rate value, the number of bits in the DCI used to indicate the value may be different. For example, if 4 values ​​are configured for the first PUSCH opportunity 512, 2 bits may be used to indicate the value in the DCI, while if one value is configured for the second PUSCH opportunity 514, zero bits in the DCI may be used to indicate the value (e.g., the DCI may not indicate the value).

[0106] As indicated above, Figure 5 are provided as examples. Other examples can be found in relation to Figure 5 Described differently.

[0107] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE in accordance with the present disclosure. Example process 600 is an example of operations in which a UE (eg, UE 502) performs PUSCH segmentation for reporting TD CSI.

[0108] like Figure 6 As shown, in some aspects, process 600 may include receiving, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information (block 610). For example, a UE (e.g., using Figure 8 The communication manager 808 and / or receiving component 802 depicted in the figure can receive scheduling information indicating scheduled PUSCH communication corresponding to the first PUSCH opportunity during a PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information, as described above.

[0109] like Figure 6 As further shown, in some aspects, process 600 may include performing a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to scheduled PUSCH communications, wherein performing the PUSCH split operation includes sending additional uplink information during the first PUSCH opportunity and sending TD CSI during the second PUSCH opportunity (block 620). For example, a UE (e.g., using Figure 8 The communication manager 808 and / or the transmitting component 804 depicted in FIG. 8 may perform a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to scheduled PUSCH communications, wherein performing the PUSCH split operation includes sending additional uplink information during the first PUSCH opportunity and sending TD CSI during the second PUSCH opportunity, as described above.

[0110] Process 600 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.

[0111] In a first aspect, the additional uplink information includes at least one of uplink data, an acknowledgement indication, or non-TD CSI. In a second aspect, alone or in combination with the first aspect, a first PUSCH opportunity is offset from a PDCCH opportunity by a PDCCH to PUSCH slot offset, and a second PUSCH opportunity is offset from the first PUSCH opportunity by a split PUSCH slot offset, and wherein the scheduling information indicates the PDCCH to PUSCH slot offset. In a third aspect, alone or in combination with the second aspect, receiving the scheduling information includes receiving a DCI transmission indicating the split PUSCH slot offset. In a fourth aspect, alone or in combination with one or more of the second or third aspects, process 600 includes receiving an RRC configuration indicating the split PUSCH slot offset.

[0112] In a fifth aspect, either alone or in combination with one or more of the second to fourth aspects, the split PUSCH time slot offset corresponds to the width of the TD CSI measurement window. In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, performing a PUSCH split operation includes performing a PUSCH split operation based on a set of uplink content. In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 600 includes receiving a radio resource control configuration including an indication to perform a PUSCH split operation, and wherein performing a PUSCH split operation includes performing a PUSCH split operation based on the indication. In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, receiving scheduling information includes receiving a DCI transmission including an indication to perform a PUSCH split operation, and wherein performing a PUSCH split operation includes performing a PUSCH split operation based on the indication. In a ninth aspect, alone or in combination with the eighth aspect, the indication to perform a PUSCH split operation comprises an indication of a split PUSCH slot offset associated with the second PUSCH opportunity.

[0113] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the scheduling information indicates a TDRA, and performing a PUSCH segmentation operation includes performing a PUSCH segmentation operation based on the TDRA failing to satisfy a segmentation condition associated with a TD CSI processing timeline. In the eleventh aspect, alone or in combination with the tenth aspect, the TDRA fails to satisfy the segmentation condition based on at least a specified amount of symbols being between a last CSI reference signal opportunity and a first PUSCH opportunity. In the twelfth aspect, alone or in combination with the eleventh aspect, the specified amount of symbols corresponds to a TD CSI processing time. In the thirteenth aspect, alone or in combination with one or more of the tenth to twelfth aspects, the TDRA fails to satisfy the segmentation condition based on at least a specified amount of CSI reference signal opportunities occurring no later than a time slot associated with a CSI reference signal resource.

[0114] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, performing a PUSCH split operation includes avoiding updating TD CSI during a first PUSCH opportunity. In a fifteenth aspect, alone or in combination with the fourteenth aspect, avoiding updating TD CSI during a first PUSCH opportunity includes including one or more padding bits in a field allocated for TD CSI. In a sixteenth aspect, alone or in combination with one or more of the fourteenth or fifteenth aspects, avoiding updating TD CSI during a first PUSCH opportunity includes avoiding sending TDCSI during the first PUSCH opportunity.

[0115] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, sending TD CSI includes sending uplink control information indicating TD CSI without uplink data. In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, receiving scheduling information includes receiving a DCI transmission, the DCI transmission including an indication of at least one parameter associated with both the first PUSCH opportunity and the second PUSCH opportunity. In the nineteenth aspect, alone or in combination with the eighteenth aspect, the at least one parameter indicates at least one of FDRA, MCS, SRI, the number of layers, a precoding matrix, an antenna port, a frequency hopping operation, an open-loop power control, or a TDRA parameter. In the twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, receiving scheduling information includes receiving a DCI transmission, the DCI transmission including a first indication of a first set of TDRA parameters associated with the first PUSCH opportunity and a second indication of a second set of TDRA parameters associated with the second PUSCH opportunity.

[0116] In a twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, process 600 comprises receiving an indication of at least one UCI decoding rate scaling factor. In a twenty-second aspect, either alone or in combination with the twenty-first aspect, the at least one UCI decoding rate scaling factor corresponds to both a first PUSCH opportunity and a second PUSCH opportunity. In a twenty-third aspect, either alone or in combination with the twenty-first aspect, the at least one UCI decoding rate scaling factor comprises a first UCI decoding rate scaling factor corresponding to the first PUSCH opportunity and a second UCI decoding rate scaling factor corresponding to the second PUSCH opportunity.

[0117] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more of the blocks in the process 600 may be performed in parallel.

[0118] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a network node in accordance with the present disclosure. Example process 700 is an example in which a network node (eg, network node 504) performs operations associated with PUSCH segmentation for reporting TD CSI.

[0119] like Figure 7 As shown, in some aspects, process 700 may include sending, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including the TD CSI and the additional uplink information (block 710). For example, a network node (e.g., using Fig. 9 The communication manager 908 and / or the sending component 904 depicted in the figure can send scheduling information indicating scheduled PUSCH communication corresponding to the first PUSCH opportunity during the PDCCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including TD CSI and additional uplink information, as described above.

[0120] like Figure 7 As further shown, in some aspects, process 700 may include receiving additional uplink information during a first PUSCH opportunity (block 720). For example, a network node (eg, using Fig. 9 The communication manager 908 and / or receiving component 902 depicted in FIG. 9 may receive additional uplink information during the first PUSCH opportunity, as described above.

[0121] like Figure 7 As further shown, in some aspects, process 700 may include receiving TD CSI during a second PUSCH opportunity (block 730). For example, a network node (eg, using Fig. 9 The communication manager 908 and / or receiving component 902 depicted in FIG. 9 may receive TD CSI during the second PUSCH opportunity, as described above.

[0122] Process 700 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.

[0123] In a first aspect, the additional uplink information includes at least one of uplink data, an acknowledgement indication, or non-TD CSI. In a second aspect, alone or in combination with the first aspect, a first PUSCH opportunity is offset from a PDCCH opportunity by a PDCCH to PUSCH slot offset, and a second PUSCH opportunity is offset from the first PUSCH opportunity by a split PUSCH slot offset, and wherein the scheduling information indicates the PDCCH to PUSCH slot offset. In a third aspect, alone or in combination with the second aspect, sending the scheduling information includes sending a DCI transmission indicating the split PUSCH slot offset. In a fourth aspect, alone or in combination with one or more of the second or third aspects, process 700 includes sending an RRC configuration indicating the split PUSCH slot offset.

[0124] In a fifth aspect, either alone or in combination with one or more of the second to fourth aspects, the split PUSCH slot offset corresponds to a width of a TD CSI measurement window. In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 700 includes sending an RRC configuration including an indication to perform a PUSCH split operation. In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, sending scheduling information includes sending a DCI transmission including an indication to perform a PUSCH split operation. In an eighth aspect, either alone or in combination with the seventh aspect, the indication to perform a PUSCH split operation includes an indication of a split PUSCH slot offset associated with a second PUSCH opportunity.

[0125] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the scheduling information indicates a TDRA, and receiving the TD CSI during the second PUSCH opportunity includes receiving the TD CSI during the second PUSCH opportunity based on the TDRA failing to satisfy a split condition associated with the TD CSI processing timeline. In the tenth aspect, alone or in combination with the ninth aspect, the TDRA fails to satisfy the split condition based on at least a specified amount of symbols between the last CSI reference signal opportunity and the first PUSCH opportunity. In the eleventh aspect, alone or in combination with the tenth aspect, the specified amount of symbols corresponds to a TDCSI processing time. In the twelfth aspect, alone or in combination with one or more of the ninth to eleventh aspects, the TDRA fails to satisfy the split condition based on at least a specified amount of CSI reference signal opportunities occurring no later than a time slot associated with the CSI reference signal resource.

[0126] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, receiving the TD CSI comprises receiving UCI indicating the TD CSI without uplink data. In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, sending the scheduling information comprises sending a DCI transmission, the DCI transmission comprising an indication of at least one parameter associated with both the first PUSCH opportunity and the second PUSCH opportunity. In a fifteenth aspect, alone or in combination with the fourteenth aspect, the at least one parameter indicates at least one of FDRA, MCS, SRI, number of layers, precoding matrix, antenna port, frequency hopping operation, open loop power control, or TDRA parameters.

[0127] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, sending scheduling information comprises sending a DCI transmission comprising a first indication of a first set of TDRA parameters associated with a first PUSCH opportunity and a second indication of a second set of TDRA parameters associated with a second PUSCH opportunity. In a seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, process 700 comprises sending an indication of at least one UCI decoding rate scaling factor. In an eighteenth aspect, either alone or in combination with the seventeenth aspect, the at least one UCI decoding rate scaling factor corresponds to both the first PUSCH opportunity and the second PUSCH opportunity. In a nineteenth aspect, either alone or in combination with the seventeenth aspect, the at least one UCI decoding rate scaling factor comprises a first UCI decoding rate scaling factor corresponding to the first PUSCH opportunity and a second UCI decoding rate scaling factor corresponding to the second PUSCH opportunity.

[0128] although Figure 7An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks of process 700 may be performed in parallel.

[0129] Figure 8 800 for wireless communication according to the present disclosure. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using receiving component 802 and transmitting component 804. As further shown, apparatus 800 may include a communication manager 808.

[0130] In some aspects, the apparatus 800 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 800 and / or Figure 8 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components 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 code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0131] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 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 one or more other components of the device 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0132] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 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 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0133] The communication manager 808 and / or the receiving component 802 may receive, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including the TD CSI and the additional uplink information. In some aspects, the communication manager 808 may include combining Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE described herein. In some aspects, the communication manager 808 may include a receiving component 802 and / or a sending component 804. In some aspects, the communication manager 808 may be, be similar to, or include Figure 1 and Figure 2 The communication manager 140 depicted in, or included in, the communication manager.

[0134] The communication manager 808 and / or the transmitting component 804 may perform a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to scheduled PUSCH communications, wherein performing the PUSCH split operation includes sending additional uplink information during the first PUSCH opportunity; and sending TD CSI during the second PUSCH opportunity. The communication manager 808 and / or the receiving component 802 may receive a radio resource control configuration indicating a split PUSCH slot offset. The communication manager 808 and / or the receiving component 802 may receive a radio resource control configuration including an indication to perform a PUSCH split operation, and wherein performing the PUSCH split operation includes performing the PUSCH split operation based on the indication. The communication manager 808 and / or the receiving component 802 may receive an indication of at least one UCI decoding rate scaling factor.

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

[0136] Fig. 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 908.

[0137] In some aspects, the apparatus 900 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components 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 code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0138] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 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 one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0139] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 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 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0140] The communication manager 908 and / or the transmitting component 904 may transmit, during a PDCCH opportunity, scheduling information indicating a scheduled PUSCH communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including the TD CSI and the additional uplink information. In some aspects, the communication manager 908 may include combining Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network nodes described herein. In some aspects, the communication manager 908 may include a receiving component 902 and / or a sending component 904. In some aspects, the communication manager 908 may be, be similar to, or include Figure 1 and Figure 2 The communication manager 150 depicted in, or included in, the communication manager.

[0141] The communication manager 908 and / or the receiving component 902 may receive additional uplink information during a first PUSCH opportunity. The receiving component 902 may receive TD CSI during a second PUSCH opportunity. The communication manager 908 and / or the transmitting component 904 may transmit a radio resource control configuration indicating a split PUSCH slot offset. The communication manager 908 and / or the transmitting component 904 may transmit a radio resource control configuration including an indication to perform a PUSCH split operation. The communication manager 908 and / or the transmitting component 904 may transmit an indication of at least one UCI decoding rate scaling factor.

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

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

[0144] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity during a physical downlink control channel (PDCCH) opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including time domain channel state information (TD CSI) and additional uplink information; and performing a PUSCH split operation, wherein the first PUSCH opportunity and a second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein performing the PUSCH split operation includes: sending the additional uplink information during the first PUSCH opportunity; and sending the TD CSI during the second PUSCH opportunity.

[0145] Aspect 2: The method according to aspect 1, wherein the additional uplink information includes at least one of uplink data, an acknowledgement indication, or non-TD CSI.

[0146] Aspect 3: A method according to any one of Aspects 1 or 2, wherein the first PUSCH opportunity is offset from the PDCCH opportunity by a PDCCH to PUSCH time slot offset, and the second PUSCH opportunity is offset from the first PUSCH opportunity by a PUSCH time slot offset, and wherein the scheduling information indicates the PDCCH to PUSCH time slot offset.

[0147] Aspect 4: The method according to aspect 3, wherein receiving the scheduling information includes receiving a downlink control information transmission indicating the split PUSCH time slot offset.

[0148] Aspect 5: The method according to any one of aspects 3 or 4, further comprising receiving a radio resource control configuration indicating the split PUSCH time slot offset.

[0149] Aspect 6: The method according to any one of aspects 3 to 5, wherein the split PUSCH time slot offset corresponds to the width of a TD CSI measurement window.

[0150] Aspect 7: The method according to any one of aspects 1 to 6, wherein performing the PUSCH segmentation operation includes performing the PUSCH segmentation operation based on the set of uplink content.

[0151] Aspect 8: According to any one of Aspects 1 to 7, the method also includes receiving a radio resource control configuration including an indication to perform the PUSCH splitting operation, and wherein performing the PUSCH splitting operation includes performing the PUSCH splitting operation based on the indication.

[0152] Aspect 9: A method according to any one of Aspects 1 to 8, wherein receiving the scheduling information includes receiving downlink control information transmission, the downlink control information transmission includes an indication to perform the PUSCH splitting operation, and wherein performing the PUSCH splitting operation includes performing the PUSCH splitting operation based on the indication.

[0153] Aspect 10: The method according to aspect 9, wherein the indication to perform the PUSCH split operation includes an indication of a split PUSCH slot offset associated with the second PUSCH opportunity.

[0154] Aspect 11: A method according to any one of aspects 1 to 10, wherein the scheduling information indicates a time domain resource allocation (TDRA), and wherein performing the PUSCH segmentation operation includes performing the PUSCH segmentation operation based on the TDRA failing to satisfy a segmentation condition associated with a TD CSI processing timeline.

[0155] Aspect 12: The method according to aspect 11, wherein the TDRA fails to satisfy the segmentation condition based on at least a specified amount of symbols between a last CSI reference signal opportunity and the first PUSCH opportunity.

[0156] Aspect 13: The method according to aspect 12, wherein the specified amount of symbols corresponds to TD CSI processing time.

[0157] Aspect 14: The method according to any one of aspects 11 to 13, wherein the TDRA fails to satisfy the partitioning condition based on at least a specified number of CSI reference signal opportunities occurring no later than a time slot associated with a CSI reference signal resource.

[0158] Aspect 15: The method according to any one of aspects 1 to 14, wherein performing the PUSCH segmentation operation includes avoiding updating the TD CSI during the first PUSCH opportunity.

[0159] Aspect 16: The method of aspect 15, wherein avoiding updating the TDCSI during the first PUSCH opportunity comprises including one or more padding bits in a field allocated for the TD CSI.

[0160] Aspect 17: The method according to any one of aspects 15 or 16, wherein avoiding updating the TD CSI during the first PUSCH opportunity includes avoiding sending the TD CSI during the first PUSCH opportunity.

[0161] Aspect 18: The method according to any one of aspects 1 to 17, wherein sending the TD CSI includes sending uplink control information indicating the TD CSI without uplink data.

[0162] Aspect 19: A method according to any one of Aspects 1 to 18, wherein receiving the scheduling information includes receiving a downlink control information (DCI) transmission, the downlink control information (DCI) transmission including an indication of at least one parameter associated with both the first PUSCH opportunity and the second PUSCH opportunity.

[0163] Aspect 20: A method according to Aspect 19, wherein the at least one parameter indicates at least one of frequency domain resource allocation, modulation and coding scheme, sounding reference signal resource indicator, number of layers, precoding matrix, antenna port, frequency hopping operation, open loop power control or time domain resource allocation parameters.

[0164] Aspect 21: A method according to any one of Aspects 1 to 20, wherein receiving the scheduling information includes receiving a downlink control information (DCI) transmission, the downlink control information (DCI) transmission including a first indication of a first set of time domain resource allocation (TDRA) parameters associated with the first PUSCH opportunity and a second indication of a second set of TDRA parameters associated with the second PUSCH opportunity.

[0165] Aspect 22: The method according to any one of aspects 1 to 21, the method further comprising receiving an indication of at least one uplink control information (UCI) coding rate scaling factor.

[0166] Aspect 23: The method according to aspect 22, wherein the at least one UCI coding rate scaling factor corresponds to both the first PUSCH opportunity and the second PUSCH opportunity.

[0167] Aspect 24: The method according to aspect 22, wherein the at least one UCI decoding rate scaling factor comprises a first UCI decoding rate scaling factor corresponding to the first PUSCH opportunity and a second UCI decoding rate scaling factor corresponding to the second PUSCH opportunity.

[0168] Aspect 25: A method of wireless communication performed by a network node, the method comprising: sending scheduling information indicating scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity during a physical downlink control channel (PDCCH) opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content including time domain channel state information (TD CSI) and additional uplink information; receiving the additional uplink information during the first PUSCH opportunity; and receiving the TD CSI during a second PUSCH opportunity.

[0169] Aspect 26: The method according to aspect 25, wherein the additional uplink information includes at least one of uplink data, an acknowledgement indication, or non-TD CSI.

[0170] Aspect 27: A method according to any one of Aspects 25 or 26, wherein the first PUSCH opportunity is offset from the PDCCH opportunity by a PDCCH to PUSCH time slot offset, and the second PUSCH opportunity is offset from the first PUSCH opportunity by a PUSCH time slot offset, and wherein the scheduling information indicates the PDCCH to PUSCH time slot offset.

[0171] Aspect 28: The method according to aspect 27, wherein sending the scheduling information includes sending downlink control information indicating the split PUSCH time slot offset.

[0172] Aspect 29: The method according to any one of aspects 27 or 28, the method further comprising sending a radio resource control configuration indicating the split PUSCH time slot offset.

[0173] Aspect 30: The method according to any one of aspects 27 to 29, wherein the split PUSCH time slot offset corresponds to the width of a TD CSI measurement window.

[0174] Aspect 31: The method according to any one of aspects 25 to 30, further comprising sending a radio resource control configuration including an indication to perform a PUSCH split operation.

[0175] Aspect 32: A method according to any one of aspects 25 to 31, wherein sending the scheduling information comprises sending downlink control information including an indication to perform a PUSCH split operation.

[0176] Aspect 33: The method according to aspect 32, wherein the indication to perform the PUSCH split operation includes an indication of a split PUSCH slot offset associated with the second PUSCH opportunity.

[0177] Aspect 34: A method according to any one of Aspects 25 to 33, wherein the scheduling information indicates a time domain resource allocation (TDRA), and wherein receiving the TD CSI during the second PUSCH opportunity includes receiving the TDCSI during the second PUSCH opportunity based on the TDRA failing to satisfy a split condition associated with a TD CSI processing timeline.

[0178] Aspect 35: The method of aspect 34, wherein the TDRA fails to satisfy the segmentation condition based on at least a specified amount of symbols between a last CSI reference signal opportunity and the first PUSCH opportunity.

[0179] Aspect 36: The method according to Aspect 35, wherein the specified amount of symbols corresponds to TD CSI processing time.

[0180] Aspect 37: The method according to any one of aspects 34 to 36, wherein the TDRA fails to satisfy the partitioning condition based on at least a specified number of CSI reference signal opportunities occurring no later than a time slot associated with a CSI reference signal resource.

[0181] Aspect 38: The method according to any one of aspects 25 to 37, wherein receiving the TD CSI comprises receiving uplink control information indicating the TD CSI without uplink data.

[0182] Aspect 39: A method according to any one of Aspects 25 to 38, wherein sending the scheduling information includes sending downlink control information (DCI), and the downlink control information (DCI) includes an indication of at least one parameter associated with both the first PUSCH opportunity and the second PUSCH opportunity.

[0183] Aspect 40: A method according to Aspect 39, wherein the at least one parameter indicates at least one of frequency domain resource allocation, modulation and coding scheme, sounding reference signal resource indicator, number of layers, precoding matrix, antenna port, frequency hopping operation, open loop power control or time domain resource allocation parameters.

[0184] Aspect 41: A method according to any one of Aspects 25 to 40, wherein sending the scheduling information includes sending downlink control information (DCI), and the downlink control information (DCI) includes a first indication of a first set of time domain resource allocation (TDRA) parameters associated with the first PUSCH opportunity and a second indication of a second set of TDRA parameters associated with the second PUSCH opportunity.

[0185] Aspect 42: The method according to any one of aspects 25 to 41, the method further comprising sending an indication of at least one uplink control information (UCI) coding rate scaling factor.

[0186] Aspect 43: The method according to aspect 42, wherein the at least one UCI coding rate scaling factor corresponds to both the first PUSCH opportunity and the second PUSCH opportunity.

[0187] Aspect 44: The method according to aspect 42, wherein the at least one UCI decoding rate scaling factor comprises a first UCI decoding rate scaling factor corresponding to the first PUSCH opportunity and a second UCI decoding rate scaling factor corresponding to the second PUSCH opportunity.

[0188] Aspect 45: 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 24.

[0189] Aspect 46: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 24.

[0190] Aspect 47: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 24.

[0191] Aspect 48: 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 24.

[0192] Aspect 49: 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 24.

[0193] Aspect 50: An apparatus for wireless communication 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 25 to 44.

[0194] Aspect 51: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 25 to 44.

[0195] Aspect 52: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 25 to 44.

[0196] Aspect 53: 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 25 to 44.

[0197] Aspect 54: 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 25 to 44.

[0198] 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 foregoing disclosure or may be acquired from practice of the various aspects.

[0199] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of 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, execution threads, processes and / or functions, etc. As used herein, "processor" is implemented by 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, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0200] 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.

[0201] Although specific combinations of features are stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically stated in the claims and / or is not disclosed in the specification. The disclosure of various aspects 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).

[0202] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. 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 you only want to refer to an item, 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, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving, during a physical downlink control channel (PDCCH) opportunity, scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content comprising time domain channel state information (TD CSI) and additional uplink information; as well as performing a PUSCH splitting operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein to perform the PUSCH splitting operation, the one or more processors are configured to: sending the additional uplink information during the first PUSCH opportunity; and The TD CSI is transmitted during the second PUSCH opportunity.

2. The UE of claim 1, wherein the additional uplink information comprises at least one of uplink data, an acknowledgement indication, or non-TD CSI.

3. The UE of claim 1, wherein the first PUSCH opportunity is offset from the PDCCH opportunity by a PDCCH to PUSCH slot offset, and the second PUSCH opportunity is offset from the first PUSCH opportunity by a PUSCH slot offset, and wherein the scheduling information indicates the PDCCH to PUSCH slot offset.

4. The UE of claim 3, wherein to receive the scheduling information, the one or more processors are configured to receive a downlink control information transmission indicating the split PUSCH slot offset. 5 . The UE of claim 3 , wherein the one or more processors are further configured to receive a radio resource control configuration indicating the split PUSCH slot offset. The UE according to claim 3 , wherein the split PUSCH time slot offset corresponds to a width of a TD CSI measurement window.

7. The UE of claim 1, wherein to perform the PUSCH segmentation operation, the one or more processors are configured to perform the PUSCH segmentation operation based on the set of uplink content.

8. The UE of claim 1, wherein the one or more processors are further configured to receive a radio resource control configuration including an indication to perform the PUSCH splitting operation, and wherein in order to perform the PUSCH splitting operation, the one or more processors are configured to perform the PUSCH splitting operation based on the indication.

9. The UE according to claim 1, wherein in order to receive the scheduling information, the one or more processors are configured to receive downlink control information including an indication to perform the PUSCH splitting operation, and in order to perform the PUSCH splitting operation, the one or more processors are configured to perform the PUSCH splitting operation based on the indication.

10. The UE of claim 9, wherein the indication to perform the PUSCH split operation comprises an indication of a split PUSCH slot offset associated with the second PUSCH opportunity.

11. The UE of claim 1 , wherein the scheduling information indicates a time domain resource allocation (TDRA), and to perform the PUSCH segmentation operation, the one or more processors are configured to perform the PUSCH segmentation operation based on the TDRA failing to satisfy a segmentation condition associated with a TDCSI processing timeline.

12. The UE of claim 11, wherein the TDRA fails to satisfy the segmentation condition based on at least a specified amount of symbols between a last CSI reference signal opportunity and the first PUSCH opportunity.

13. The UE of claim 12, wherein the specified amount of symbols corresponds to a TD CSI processing time.

14. The UE of claim 11, wherein the TDRA fails to satisfy the partitioning condition based on at least a specified amount of CSI reference signal opportunities occurring no later than a time slot associated with a CSI reference signal resource.

15. The UE of claim 1, wherein to perform the PUSCH segmentation operation, the one or more processors are configured to avoid updating the TD CSI during the first PUSCH opportunity.

16. The UE of claim 15, wherein to avoid updating the TDCSI during the first PUSCH opportunity, the one or more processors are configured to include one or more padding bits in a field allocated for the TD CSI. 17 . The UE of claim 15 , wherein to avoid updating the TDCSI during the first PUSCH opportunity, the one or more processors are configured to avoid sending the TD CSI during the first PUSCH opportunity.

18. The UE of claim 1, wherein to transmit the TD CSI, the one or more processors are configured to transmit uplink control information indicating the TD CSI without uplink data.

19. The UE of claim 1, wherein to receive the scheduling information, the one or more processors are configured to receive a downlink control information (DCI) transmission comprising an indication of at least one parameter associated with both the first PUSCH opportunity and the second PUSCH opportunity.

20. The UE of claim 19, wherein the at least one parameter indicates at least one of frequency domain resource allocation, modulation and coding scheme, sounding reference signal resource indicator, number of layers, precoding matrix, antenna port, frequency hopping operation, open loop power control, or time domain resource allocation parameters.

21. The UE of claim 1, wherein to receive the scheduling information, the one or more processors are configured to receive a downlink control information (DCI) transmission comprising a first indication of a first set of time domain resource allocation (TDRA) parameters associated with the first PUSCH opportunity and a second indication of a second set of TDRA parameters associated with the second PUSCH opportunity.

22. The UE of claim 1, wherein the one or more processors are further configured to receive an indication of at least one uplink control information (UCI) coding rate scaling factor.

23. The UE of claim 22, wherein the at least one UCI coding rate scaling factor corresponds to both the first PUSCH opportunity and the second PUSCH opportunity.

24. The UE of claim 22, wherein the at least one UCI decoding rate scaling factor comprises a first UCI decoding rate scaling factor corresponding to the first PUSCH opportunity and a second UCI decoding rate scaling factor corresponding to the second PUSCH opportunity.

25. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: transmitting, during a physical downlink control channel (PDCCH) opportunity, scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content comprising time domain channel state information (TD CSI) and additional uplink information; receiving the additional uplink information during the first PUSCH opportunity; and The TD CSI is received during a second PUSCH opportunity.

26. The network node of claim 25, wherein the first PUSCH opportunity is offset from the PDCCH opportunity by a PDCCH to PUSCH slot offset, and the second PUSCH opportunity is offset from the first PUSCH opportunity by a split PUSCH slot offset, and wherein the scheduling information indicates the PDCCH to PUSCH slot offset.

27. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, during a physical downlink control channel (PDCCH) opportunity, scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content comprising time domain channel state information (TD CSI) and additional uplink information; as well as performing a PUSCH split operation, wherein the first PUSCH opportunity and the second PUSCH opportunity correspond to the scheduled PUSCH communication, wherein performing the PUSCH split operation comprises: sending the additional uplink information during the first PUSCH opportunity; as well as The TD CSI is transmitted during the second PUSCH opportunity.

28. The method of claim 27, wherein the first PUSCH opportunity is offset from the PDCCH opportunity by a PDCCH-to-PUSCH slot offset, and the second PUSCH opportunity is offset from the first PUSCH opportunity by a split PUSCH slot offset, and wherein the scheduling information indicates the PDCCH-to-PUSCH slot offset.

29. A method of wireless communication performed by a network node, the method comprising: transmitting, during a physical downlink control channel (PDCCH) opportunity, scheduling information indicating a scheduled physical uplink shared channel (PUSCH) communication corresponding to a first PUSCH opportunity, wherein the scheduling information indicates a set of uplink content associated with the scheduled PUSCH communication, the set of uplink content comprising time domain channel state information (TD CSI) and additional uplink information; receiving the additional uplink information during the first PUSCH opportunity; and The TD CSI is received during a second PUSCH opportunity.

30. The method of claim 29, wherein the first PUSCH opportunity is offset from the PDCCH opportunity by a PDCCH-to-PUSCH slot offset, and the second PUSCH opportunity is offset from the first PUSCH opportunity by a split PUSCH slot offset, and wherein the scheduling information indicates the PDCCH-to-PUSCH slot offset.

Images