Scheduling enhancements for physical uplink shared channels communicating time domain channel state information

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive a physical downlink control channel (PDCCH) communication that schedules a physical uplink shared channel (PUSCH) communication that will include type II Doppler channel state information (CSI). The UE can determine a slot offset between the PDCCH communication and the PUSCH communication based at least in part on a slot offset value to be used in association with transmission type II Doppler CSI. The UE can transmit the PUSCH communication based at least in part on the PDCCH communication and the slot offset. 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 scheduling enhancements for a Physical Uplink Shared Channel (PUSCH) that conveys time-domain Channel State Information (CSI). 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 a user equipment (UE) or multiple UEs. A UE may communicate with a 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: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a first physical downlink control channel (PDCCH) communication that schedules a first physical uplink shared channel (PUSCH) communication that will include type II Doppler channel state information (CSI). The method may include receiving a second PDCCH communication that schedules a second PUSCH communication, wherein the last symbol of the second PDCCH communication is after the last symbol of the first PDCCH communication in the time domain, and wherein the first symbol of the second PUSCH communication will be before the last symbol of the first PUSCH communication in the time domain. The method may include sending the second PUSCH communication based at least in part on the second PDCCH communication.

[0006] Some aspects described herein relate to a 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 a first PDCCH communication that schedules a first PUSCH communication that will include type II Doppler CSI. The one or more processors may be configured to receive a second PDCCH communication that schedules a second PUSCH communication. The one or more processors may be configured to send the second PUSCH communication based at least in part on the second PDCCH communication.

[0007] 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 a first PDCCH communication that schedules a first PUSCH communication that will include type II Doppler CSI. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a second PDCCH communication that schedules a second PUSCH communication. The instruction set, when executed by one or more processors of the UE, may cause the UE to send the second PUSCH communication based at least in part on the second PDCCH communication.

[0008] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a first PDCCH communication that schedules a first PUSCH communication that will include Type II Doppler CSI. The apparatus may include components for receiving a second PDCCH communication that schedules a second PUSCH communication, wherein a last symbol of the second PDCCH communication is after a last symbol of the first PDCCH communication in a time domain, and wherein a first symbol of the second PUSCH communication will be before a last symbol of the first PUSCH communication in the time domain. The apparatus may include components for sending the second PUSCH communication based at least in part on the second PDCCH communication.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a PDCCH communication that schedules a PUSCH communication that will include Type II Doppler CSI. The method may include determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with sending the Type II Doppler CSI. The method may include sending the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

[0010] Some aspects described herein relate to a 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 a PDCCH communication that schedules a PUSCH communication that will include a type II Doppler CSI. The one or more processors may be configured to determine a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with sending the type II Doppler CSI. The one or more processors may be configured to send the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a PDCCH communication that schedules a PUSCH communication that will include a type II Doppler CSI. The instruction set, when executed by one or more processors of the UE, may cause the UE to determine a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with sending the type II Doppler CSI. The instruction set, when executed by one or more processors of the UE, may cause the UE to send the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a PDCCH communication that schedules a PUSCH communication that will include Type II Doppler CSI. The apparatus may include means for determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting the Type II Doppler CSI. The apparatus may include means for transmitting the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

[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 extensively 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 equipment 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 (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. 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 be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings 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 an illustrative example of an ordered scheduling rule.

[0021] Figure 5A and Figure 5B is a diagram illustrating an example associated with scheduling enhancement for a physical uplink shared channel (PUSCH) for delivering time-domain channel state information (CSI) according to the present disclosure.

[0022] Fig. 6A and Figure 6B is a diagram illustrating an example associated with scheduling enhancement for a PUSCH for delivering time domain CSI according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example of associating a CSI reference signal (RS) burst with a PUSCH communication based at least in part on a minimum offset.

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

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

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

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

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

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0031] Figure 1 1 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, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include 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.

[0033] 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 the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. 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).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated 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 the other. In this way, a single device may include more than one base station.

[0035] 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 can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication 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.

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

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

[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, which 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, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[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, which may be subdivided into various categories, bands, channels, etc., according to 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 portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[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.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0044] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a first PDCCH communication that schedules a first PUSCH communication that will include a Type II Doppler CSI; receive a second PDCCH communication that schedules a second PUSCH communication, wherein a last symbol of the second PDCCH communication is after a last symbol of the first PDCCH communication in the time domain, and wherein a first symbol of the second PUSCH communication is before a last symbol of the first PUSCH communication in the time domain; and send the second PUSCH communication based at least in part on the second PDCCH communication. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a PDCCH communication scheduling a PUSCH communication that will include a Type II Doppler CSI; determine a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with sending the Type II Doppler CSI; and send the PUSCH communication based at least in part on the PDCCH communication and the time slot offset. Additionally or alternatively, communications manager 140 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 Different than described.

[0048] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a user equipment (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, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and 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., precoding) 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 upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 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 be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0053] 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 sent 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 the functions described herein (eg, with reference to FIG. 5A to FIG. 11 ) or any aspects of any of the methods described herein.

[0054] 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 of the modem 232 shown as DEMOD), 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 and / or uplink communications. 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 FIG. 5A to FIG. 11 ) or any aspects of any of the methods described herein.

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

[0056] In some aspects, the UE 120 includes means for receiving a first PDCCH communication that schedules a first PUSCH communication that will include a Type II Doppler CSI; means for receiving a second PDCCH communication that schedules a second PUSCH communication, wherein the last symbol of the second PDCCH communication is after the last symbol of the first PDCCH communication in the time domain, and wherein the first symbol of the second PUSCH communication is before the last symbol of the first PUSCH communication in the time domain; and / or means for sending the second PUSCH communication based at least in part on the second PDCCH communication. Means for the UE 120 to perform operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0057] In some aspects, the UE 120 includes means for receiving a PDCCH communication that schedules a PUSCH communication that will include a Type II Doppler CSI; means for determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with sending the Type II Doppler CSI; and / or means for sending the PUSCH communication based at least in part on the PDCCH communication and the time slot offset. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

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

[0059] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0060] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components 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 functions can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

[0062] 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. Various 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.

[0063] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed 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.

[0064] 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 send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0065] In some aspects, 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 CU 310. 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, 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, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0066] 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 partition such as that defined by 3GPP. In some aspects, 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.

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

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

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

[0070] In some implementations, in order to generate the 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 regulate 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).

[0071] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0072] A network entity (such as a base station) may send many beams to a UE. For example, the network entity may generate beams using an antenna panel that generates beams that are spatially and / or phase-shifted from each other. The network entity and the UE may select a set of beams to be used for communication between the network entity and the UE. For example, a set of beams sent from a network entity to a UE may be referred to herein as a communication link, a downlink, etc. The communication link between the network entity and the UE may propagate in a medium and / or through various geometric paths, which are collectively referred to herein as a channel between the network entity and the UE.

[0073] In some aspects, the UE may select a beam set for communicating with a network entity. For example, the UE may select the beam set based at least in part on a beam set associated with a favorable characteristic (e.g., a satisfactory received power, a satisfactory signal to interference plus noise ratio (SINR) value, etc.). The UE may generate a codeword indicating the beam set and parameters to be used for using a codebook based at least in part on performing channel estimation of a channel between the network entity and the UE.

[0074] One such codebook is the type II codebook specified in 5G / NR. A type II codebook may generate codewords using a two-stage procedure: a first stage in which a beam set is selected for a wideband of a communication link (e.g., sometimes referred to herein as W1), and a second stage in which a linear combination is performed for a subband set using a beam set for each subband set. The codeword may be based at least in part on a linear combination and may indicate a beam set and / or corresponding amplitude, phase coefficients, etc. Thus, the UE may provide an indication of the channel state at the UE and may request a beam set to be used for the UE. A type II codebook may provide a more accurate designation of the channel state than a type I codebook, which may provide a predefined codeword-based method for designating a selected beam. Thus, compared to a type I codebook, a type II codebook may be referred to as a high-resolution codebook. For example, a type II codebook may improve multi-user multiple-input multiple-output (MU-MIMO) performance on a communication link.

[0075] For one type of type II codebook (e.g., the codebook specified in Release 15 of the 3GPP standard for 5G / NR), the precoder is based at least in part on a linear combination of discrete Fourier transform (DFT) beams. The linear combination may define the precoder W as W=W1W2, where the spatial domain compression matrix in are L space-domain basis vectors of dimension N1N2×1 (mapped to two polarizations, so 2L in total), P=2N1N2 indicates the dimension (sometimes denoted as D), and the combination coefficient matrix W2 consists of L=2Lv linear combination coefficients, where v indicates the total number of layers. Each column in W2 indicates a linear combination of complex coefficients (i.e., amplitude and phase) for one layer, where the amplitude coefficient is given by Given, where l = 0,…,v-1, and and are the broadband coefficient and the subband coefficient respectively. The phase coefficient is given by Given, where l = 0, ..., v-1, and c i It is one of the 8-phase shift keying (8PSK) constellation points or the quadrature phase shift keying (QPSK) constellation points.

[0076] The UE may use channel state information (CSI) feedback to report the above values ​​and / or other values ​​associated with channel estimation. CSI feedback for a type II codebook may include two parts: a first part (sometimes referred to as CSI part I) and a second part (sometimes referred to as CSI part II). In some cases, the first part may have a smaller payload than the second part, or may have a fixed payload. For example, the first part may have a payload size of less than about 50 bits, while the second part may have a variable payload size that may depend on the first part. In some cases, the second part may have a payload size of approximately 100 bits to 600 bits, but other values ​​may be used.

[0077] In some cases, the first part may identify one or more of the following: a rank indicator (RI) (e.g., 1 bit indicating one layer v=1 or two layers v=2 when the configured maximum rank is 2); a wideband and subband differential channel quality indicator (CQI), whose total payload size may depend on the number of subbands (e.g., approximately 4+18×2=40 bits for 19 subbands); a non-zero wideband amplitude coefficient Q for each layer. l In some cases, the second portion may identify one or more of: a wideband and / or subband precoding matrix indicator (PMI) including a spatial basis vector selection indication; wideband and subband amplitude coefficients; subband phase coefficients; and the like.

[0078] In some cases, Type IICSI feedback may use a compressed Type II precoder. This may reduce the overhead of Type IICSI feedback. A compressed precoder may exploit sparsity in the spatial domain and / or frequency domain. For example, an example of a compressed Type II precoder W is represented by Given, where the pre-decoder matrix W has P = 2N1N2 rows (indicating the spatial domain and the number of ports) and N3 columns (where N3 is the frequency domain compression unit of a resource block or reporting subband). The W1 matrix described above is a spatial basis consisting of L beams per polarization group (thus a total of 2L beams). The matrix W indicates all the required linear combination complex coefficients (amplitude and co-phase), similar to what was described above. f The matrix is ​​composed of basis vectors used to perform compression in the frequency domain, and W f =[f0f1…f M-1 ],in is M orthogonal DFT vectors of size N3×1 for each spatial basis i=0, ..., 2L-1. The above-mentioned type IICSI feedback may be referred to as enhanced type IICSI feedback or modified type IICSI feedback in some cases (e.g., enhanced relative to the approach of not using basis vectors in the spatial and frequency domains to compress the feedback size).

[0079] The CSI feedback for this enhanced type IICSI feedback may include a spatial domain basis vector selection similar to the approach described in conjunction with the type IICSI feedback configuration. The CSI feedback may also include a frequency domain (FD) basis subset selection (where M basis vectors out of a total of N3 basis vectors are selected). In some cases, a common FD basis vector for all 2L spatial beams may be used, which is referred to herein as Alternative 1. In these cases, the M basis vectors are dynamically selected and reported. The value of M may be configured by the network or reported by the UE. In other cases, referred to herein as Alternative 2, an independent FD basis vector may be used for each spatial domain basis vector, with a potentially different number and / or selected FD basis vector for each spatial domain basis vector. The total number of FD basis vectors across all 2L spatial beams may be configured.

[0080] Enhanced type IICSI feedback may also include FD coefficients (e.g., amplitude and phase) in . For Alternative 1 (common FD basis vector subset selection), enhanced type IICSI feedback may report only a subset of coefficients K0 < K = 2LM. For Alternative 2 (independent basis subset selection), enhanced type IICSI feedback may report Amplitude and phase coefficients, where M i is the number of FD basis vectors associated with a spatial beam. Various quantization and reporting options may be used, two examples of which are provided below. As a first example, for each of the K or K0 FD coefficients, the enhanced type IICSI feedback may use 3-bit amplitude and QPSK or 8PSK phase. As a second example, the enhanced type IICSI feedback may report 3-bit wideband amplitude for each beam or spatial domain basis vector, 2-bit or 3-bit differential amplitude for each FD coefficient, and QPSK or 8PSK phase bits.

[0081] In some scenarios, a UE may be moving at a relatively high speed relative to a network entity with which the UE will communicate. In such a scenario, the channel between the network entity and the UE may also vary at a relatively high rate due to the speed of the UE. In this case, the time domain codebook may represent a pre-decoder W that varies (with time instance n), as given by Here, the coefficient matrix is compressed into the Doppler domain.

[0082] In general, the UE receives one or more CSI reference signals (CSI-RS) in association with generating CSI feedback, such as Type II Doppler CSI (also known as time domain CSI). In some cases, the UE may be configured to receive a periodic CSI-RS (P-CSI-RS) with a specific periodicity and offset. In some scenarios, the P-CSI-RS may be communicated in a periodic burst (e.g., with a specific burst periodicity and burst duration). The UE may also be configured to receive a semi-persistent CSI-RS (SP-CSI-RS). The SP-CSI-RS may be configured via downlink control information (DCI) carried, for example, in a physical downlink control channel (PDCCH) communication. In some scenarios, the SP-CSI-RS may be communicated in a periodic burst (e.g., in a manner similar to the P-CSI-RS). The UE may also be configured to receive an aperiodic CSI-RS (AP-CSI-RS). The AP-CSI-RS may be configured via a DCI carried, for example, in a PDCCH communication. In some scenarios, the AP-CSI-RS may be communicated as a single burst over one or more time slots.

[0083] With respect to reporting CSI feedback generated from one or more CSI-RS (e.g., one or more P-CSI-RS, one or more SP-CSI-RS, or one or more AP-CSI-RS), the UE may be configured to provide CSI reports on a periodic basis, a semi-persistent basis, or an aperiodic basis. It is worth noting that any of these types of CSI reports may be used to provide CSI associated with P-CSI-RS, while only semi-persistent and aperiodic reports may be used to provide CSI associated with SP-CSI-RS, and only aperiodic reports may be used to provide CSI associated with AP-CSI-RS.

[0084] Periodic CSI reports are communicated in Physical Uplink Control Channel (PUCCH) communications. Semi-persistent CSI reports may be communicated in PUCCH communications (e.g., triggered by a Medium Access Control (MAC) Control Element (CE)) or in Physical Uplink Shared Channel (PUSCH) communications (e.g., triggered by DCI). Aperiodic CSI reports may be triggered only by DCI and communicated in PUSCH communications. Notably, due to the relatively large overhead, communication of Type II Doppler CSI feedback may be limited to PUSCH communications (e.g., via semi-persistent CSI reports or aperiodic CSI reports communicated on PUSCH and triggered by DCI).

[0085] In some scenarios, with respect to providing aperiodic CSI reporting, a CSI-RS burst may be located between PDCCH communications that schedule PUSCH communications in which Type II Doppler CSI will be conveyed. In such a scenario, the delay between the PDCCH communication and the PUSCH communication (e.g., the PDCCH to PUSCH slot offset, also referred to as the K2 parameter) may be undesirably long. For example, a CSI-RS burst with five slot reference signal periodicity and eight instances results in a burst duration of 40 slots. It is noteworthy that in some wireless communication standards, the K2 parameter has a maximum of 32 slots for frequency range 1 (FR1). This PDCCH to PUSCH slot offset may reduce uplink throughput due to the so-called ordered scheduling rule, which specifies that during the slot between the PDCCH communication and the PUSCH communication, the UE cannot be scheduled to send another PUSCH communication, even a PUSCH communication associated with a different HARQ process identifier. Figure 4 is an illustrative example of an ordered scheduling rule. Figure 4 In the example shown, for two different hybrid automatic repeat request (HARQ) processes (HARQ process 1 and HARQ process 2), if the UE is scheduled to send a first PUSCH communication (PUSCH1) through a first PDCCH communication (PDCCH1) ending with a symbol, it is not expected that the UE is scheduled to send a second PUSCH communication (PUSCH2) starting earlier than the end of the first PUSCH communication through a second PDSCCH communication (PDCCH2) later than the end of the symbol. For the same HARQ process, the UE is not expected to be scheduled to send another PUSCH communication until the previous PUSCH transmission for the HARQ process ends. In other words, only sequences like PDCCH-PUSCH-PDCCH-PUSCH-and so on are allowed for the same HARQ process.

[0086] Some aspects described herein provide techniques and apparatus for scheduling enhancements for PUSCH that conveys type II Doppler CSI. In some aspects, a UE may receive a first PDCCH communication that schedules a first PUSCH communication that will include type II Doppler CSI, and may receive a second PDCCH communication that schedules a second PUSCH communication. Here, the last symbol of the second PDCCH communication is after the last symbol of the first PDCCH communication in the time domain. Additionally, the first symbol of the second PUSCH communication is before the last symbol of the first PUSCH communication in the time domain. The UE may send a second PUSCH communication based at least in part on the second PDCCH communication. That is, in some aspects, out-of-order PUSCH scheduling may be permitted in association with sending type II Doppler CSI. In this way, PUSCH scheduling for the transmission of type II Doppler CSI may be enhanced to increase uplink throughput.

[0087] Additionally or alternatively, in some aspects, the UE may receive a PDCCH communication that schedules a PUSCH communication that will include a type II Doppler CSI. In some aspects, the UE may determine the time slot offset between the PDCCH communication and the PUSCH communication based at least in part on the time slot offset value to be used in association with the transmission of the type II Doppler CSI, and may transmit the PUSCH communication based at least in part on the PDCCH communication and the time slot offset. In some aspects, the time slot offset value corresponds to the time slot offset between the PDCCH communication and the PUSCH communication, wherein the time slot offset value will be used for the single PUSCH communication scheduling in FR1 and is permitted to be greater than the time slot offset value threshold. Additionally or alternatively, the time slot offset value corresponds to the time slot offset between the last symbol of the CSI-RS burst and the first symbol of the PUSCH communication. That is, in some aspects, the time slot offset may be determined in association with the transmission of the type II Doppler CSI in a specific manner. Additional details are provided below. In this way, the PUSCH scheduling for the transmission of the type II Doppler CSI may be enhanced to increase the uplink throughput.

[0088] Figure 5A and Figure 5B is a diagram illustrating an example associated with scheduling enhancement for a PUSCH for delivering time domain CSI according to the present disclosure. Figure 5A As shown, example 500 includes communications between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0089] As Figure 5AAs shown at reference numeral 502 in FIG. 1 , the network node 110 may send a first PDCCH communication (PDCCH1) scheduling a first PUSCH communication (PUSCH1) that will include Type II Doppler CSI, and the UE 120 may receive the first PDCCH communication (PDCCH1).

[0090] As indicated by reference numeral 504, the network node 110 may send a second PDCCH communication (PDCCH2) scheduling a second PUSCH communication (PUSCH2), and the UE 120 may receive the second PDCCH communication (PDCCH2). In some aspects, the last symbol of the second PDCCH communication is after the last symbol of the first PDCCH communication in the time domain. Additionally, in some aspects, the first symbol of the second PUSCH communication will be before the last symbol of the first PUSCH communication in the time domain. That is, in some aspects, out-of-order PUSCH scheduling may be permitted in association with conveying Type II Doppler CSI.

[0091] In some aspects, the first PUSCH communication is associated with a first hybrid automatic repeat request (HARQ) process identifier (HARQ process ID1), and the second PUSCH communication is associated with a second HARQ process identifier (HARQ process ID2) that is different from the first HARQ process identifier. In some aspects, the first HARQ process identifier is designated for PUSCH communications including type II Doppler CSI. That is, in some aspects, the designated HARQ process identifier (e.g., the first ID#0 or the last ID#15) is configured to convey PUSCH communications of transport blocks (TBs) multiplexed with type II Doppler CSI. In some aspects, the first HARQ process identifier is configured via radio resource control (RRC) signaling or may be determined at least in part based on an applicable wireless communication standard.

[0092] In some aspects, the first PUSCH communication is an uplink control information (UCI)-only PUSCH communication and is therefore not associated with a HARQ process identifier. That is, in some aspects, only a PUSCH with only UCI (e.g., no TB) can be used to send Type II Doppler CSI, which means that a PUSCH not associated with a HARQ process identifier can utilize out-of-order scheduling.

[0093] As indicated by reference numeral 506, UE 120 may send a second PUSCH communication based at least in part on the second PDCCH communication, and network node 110 may receive the second PUSCH communication. That is, UE 120 may send the second PUSCH in an out-of-order manner, meaning that the start of the second PUSCH communication is before the end of the first PUSCH communication. In some aspects, UE 120 may send a first PUSCH communication based at least in part on the first PDCCH communication, and network node 110 may receive the first PUSCH communication.

[0094] Figure 5B is an example such as Figure 5A An example of out-of-order scheduling is described in conjunction with FIG. Figure 5B , UE 120 is scheduled by PDCCH1 (e.g., ending with symbol i) to send PUSCH1 that conveys type II Doppler CSI and TBs associated with HARQ process ID 1. Then, UE 120 is scheduled by PDCCH2 (which ends later than symbol i) to send PUSCH2, where PUSCH2 is scheduled to start earlier than the end of PUSCH1, and where PUSCH2 conveys TBs associated with HARQ process ID2 (i.e., a different HARQ process identifier). In this way, out-of-order PUSCH scheduling can be used for transmission of type II Doppler CSI, thereby increasing throughput on the uplink.

[0095] As indicated above, Figure 5A and Figure 5B are provided as examples. Other examples can be found in the Figure 5A and Figure 5B Different than described.

[0096] Fig. 6A and Figure 6B is a diagram illustrating an example associated with scheduling enhancement for a PUSCH for delivering time domain CSI according to the present disclosure. Fig. 6A As shown, example 600 includes communications between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0097] As indicated by reference numeral 602, the network node 110 may send, and the UE 120 may receive, a PDCCH communication scheduling a PUSCH communication that will include Type II Doppler CSI.

[0098] As indicated by reference numeral 604, UE 120 may determine a slot offset between PDCCH communications and PUSCH communications based at least in part on a slot offset value to be used in association with transmitting Type II Doppler CSI.

[0099] In some aspects, the slot offset value corresponds to the slot offset between PDCCH communication and PUSCH communication (i.e., PDCCH to PUSCH offset), is to be used for single PUSCH communication scheduling in FR1, and is permitted to be greater than a slot offset value threshold. That is, in some aspects, for a UE 120 configured to provide Type II Doppler CSI (e.g., via aperiodic reporting or via semi-persistent reporting), the configurable value of the K2 parameter may be greater than the slot offset value threshold (e.g., 32 slots) for single PUSCH scheduling in FR1.

[0100] Alternatively, in some aspects, the slot offset value corresponds to the slot offset between the last symbol of the CSI-RS burst and the first symbol of the PUSCH communication (i.e., the CSI-RS to PUSCH offset). That is, in some aspects, the K2 parameter is reinterpreted as a CSI-RS to PUSCH offset (rather than a PDCCH to PUSCH offset). In this case, the slot offset may be further determined based at least in part on one or more other factors, such as the duration of the CSI-RS burst, or the slot offset associated with the PDCCH communication and the CSI-RS burst. For example, the slot offset may be determined based at least in part on the CSI-RS burst duration (W 突发 ), K2 parameter or an offset associated with PDCCH communication and CSI-RS burst (referred to herein as parameter X) to determine the time slot offset between PDCCH communication and PUSCH communication.

[0101] As an example, and with reference to Figure 6B , we can use the formula W 突发 +K2+X to determine the time slot offset. Here, W 突发 Can be defined as N 实例 ×T 间隔 , or (N 实例 -1)×T 间隔 +1 time slot, where T 间隔 is the time interval between two consecutive CSI-RS instances within a CSI-RS burst, and N 实例 is the number of CSI-RS instances within a CSI-RS burst. In some aspects, X may be greater than or equal to zero (e.g., for SP-CSI-RS or AP-CSI-RS) and may correspond to a trigger offset between a PDCCH communication and the first CSI-RS instance of a CSI-RS burst, such as Figure 6BIt is worth noting that in some scenarios (eg, for P-CSI-RS), X may be less than zero.

[0102] In some aspects, the time slot offset value is a default time slot offset value, and the time slot offset is further based at least in part on a default value for the time slot offset value (e.g., K2 默认 value), duration of CSI-RS burst (W 突发 ) or the number of symbols corresponding to the CSI processing time (the number of symbols Z'). For example, the formula formula or formula To determine the time slot offset. In some aspects, K2 默认 The value may depend on the subcarrier spacing (SCS) that UE 120 is operating (e.g., K2 默认 1 can be used for 15 kHz or 30kHz SCS, K2 默认 2 can be used for 60kHz SCS, K2 默认 3 may be used for 120kHz SCS, etc.). In some aspects, Z' is defined as the number of symbols from the last symbol of the last CSI-RS (e.g., among all CSI-RS used for channel measurements or interference measurements associated with the CSI report) to the first symbol reporting an uplink channel. In some aspects, the value of Z' depends on the UE capabilities and the SCS. Some example values ​​of Z' are given below (where μ corresponds to the SCS, and Z'1 and Z'2 correspond to different UE capabilities):

[0103]

[0104]

[0105] Return to Fig. 6A , as indicated by reference numeral 606, UE 120 may send a PUSCH communication based at least in part on the PDCCH communication and the time slot offset, and network node 110 may receive the PUSCH communication. In this way, determination of the time slot offset may be enhanced for PUSCH transmission of Type II Doppler CSI, thereby increasing throughput on the uplink.

[0106] As indicated above, Fig. 6A and Figure 6B are provided as examples. Other examples can be found in the Fig. 6A and Figure 6B Different than described.

[0107] In some aspects, semi-persistent reports may be sent based at least in part on a P-CSI-RS burst. In this case, the burst periodicity and the reporting periodicity may match. That is, the periodicity of the P-CSI-RS burst may match the periodicity of the semi-persistent reports. In this aspect, the association of a CSI-RS burst with a PUSCH communication (e.g., a PUSCH communication including a Type II Doppler CSI generated based at least in part on a CSI-RS burst) may be defined as satisfying a timeline (e.g., not less than 4 or 5 slots, or slots, or Z' symbols, where Z' is the minimum offset on the processing timeline). Figure 7 is a diagram illustrating an example of associating CSI-RS bursts with PUSCH communications based at least in part on a minimum offset.

[0108] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with the present disclosure. Example process 800 is an example of a UE (eg, UE 120) performing operations associated with scheduling enhancement for a PUSCH conveying time domain CSI.

[0109] like Figure 8 As shown, in some aspects, process 800 may include receiving a first PDCCH communication that schedules a first PUSCH communication that will include Type II Doppler CSI (block 810). For example, a UE (e.g., using Fig.10 The communication manager 140 and / or receiving component 1002 depicted in FIG. 1004 may receive a first PDCCH communication scheduling a first PUSCH communication that will include Type II Doppler CSI, as described above.

[0110] like Figure 8 As further shown, in some aspects, process 800 may include receiving a second PDCCH communication scheduling a second PUSCH communication, wherein a last symbol of the second PDCCH communication is after a last symbol of the first PDCCH communication in the time domain, and wherein a first symbol of the second PUSCH communication is to be before a last symbol of the first PUSCH communication in the time domain (block 820). For example, a UE (e.g., using Fig.10 The communication manager 140 and / or receiving component 1002 depicted in the figure may receive a second PDCCH communication that schedules a second PUSCH communication, wherein the last symbol of the second PDCCH communication is after the last symbol of the first PDCCH communication in the time domain, and wherein the first symbol of the second PUSCH communication is before the last symbol of the first PUSCH communication in the time domain, as described above.

[0111] like Figure 8 As further shown, in some aspects, process 800 may include sending a second PUSCH communication based at least in part on the second PDCCH communication (block 830). Fig.10 The communication manager 140 and / or the sending component 1004 depicted in FIG. 1 may send a second PUSCH communication based at least in part on the second PDCCH communication, as described above.

[0112] Process 800 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.

[0113] In a first aspect, the first PUSCH communication is associated with a first HARQ process identifier and the second PUSCH communication is associated with a second HARQ process identifier, the second HARQ process identifier being different from the first HARQ process identifier.

[0114] In a second aspect, alone or in combination with the first aspect, the first HARQ process identity is designated for PUSCH communication including Type II Doppler CSI.

[0115] In a third aspect, alone or in combination with one or more of the first and second aspects, the first HARQ process identifier is configured via RRC signaling.

[0116] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first PUSCH communication is a UCI-only PUSCH communication.

[0117] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first PUSCH communication is not associated with a HARQ process identifier.

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

[0119] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE in accordance with the present disclosure. Example process 900 is an example of a UE (eg, UE 120) performing operations associated with scheduling enhancement for a PUSCH conveying time domain CSI.

[0120] like Fig. 9As shown, in some aspects, process 900 may include receiving a PDCCH communication scheduling a PUSCH communication that will include Type II Doppler CSI (block 910). For example, a UE (e.g., using Fig.11 The communication manager 140 and / or receiving component 1102 depicted in FIG. 1 may receive a PDCCH communication scheduling a PUSCH communication that will include Type II Doppler CSI, as described above.

[0121] like Fig. 9 As further shown, in some aspects, process 900 may include determining a time slot offset between PDCCH communication and PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting Type II Doppler CSI (block 920). Fig.11 The communication manager 140 and / or offset determination component 1108 depicted in FIG. 1 may determine a time slot offset between PDCCH communications and PUSCH communications based at least in part on a time slot offset value to be used in association with transmitting Type II Doppler CSI, as described above.

[0122] like Fig. 9 As further shown, in some aspects, process 900 may include sending a PUSCH communication based at least in part on the PDCCH communication and the time slot offset (block 930). Fig.11 The communication manager 140 and / or the transmitting component 1104 depicted in FIG. 1 may transmit a PUSCH communication based at least in part on the PDCCH communication and the time slot offset, as described above.

[0123] Process 900 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.

[0124] In a first aspect, the slot offset value corresponds to the slot offset between the PDCCH communication and the PUSCH communication, wherein the slot offset value is to be used for single PUSCH communication scheduling in FR1 and is permitted to be greater than a slot offset value threshold.

[0125] In a second aspect, alone or in combination with the first aspect, the slot offset value corresponds to a slot offset between a last symbol of a CSI-RS burst and a first symbol of the PUSCH communication.

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, the time slot offset is further determined based at least in part on a duration of the CSI-RS burst.

[0127] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the time slot offset is further determined based at least in part on a time slot offset associated with the PDCCH communication and the CSI-RS burst.

[0128] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the time slot offset value is a default time slot offset value, and the time slot offset is further determined at least in part based on at least one of the following: a default value for the time slot offset value, the duration of the CSI-RS burst, or the number of symbols corresponding to the CSI processing time.

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

[0130] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 140.

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

[0132] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 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 1000. In some aspects, the receiving component 1002 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.

[0133] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 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 1006. In some aspects, the transmitting component 1004 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 1004 can be co-located with the receive component 1002 in a transceiver.

[0134] The receiving component 1002 may receive a first PDCCH communication that schedules a first PUSCH communication that will include Type II Doppler CSI. The receiving component 1002 may receive a second PDCCH communication that schedules a second PUSCH communication, wherein a last symbol of the second PDCCH communication is after a last symbol of the first PDCCH communication in the time domain, and wherein a first symbol of the second PUSCH communication is before a last symbol of the first PUSCH communication in the time domain. The transmitting component 1004 may transmit the second PUSCH communication based at least in part on the second PDCCH communication.

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

[0136] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 140. Communication manager 140 may include an offset determination component 1108, etc.

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

[0138] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 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 1100. In some aspects, the receiving component 1102 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.

[0139] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 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 1106. In some aspects, the transmitting component 1104 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 1104 can be co-located with the receive component 1102 in a transceiver.

[0140] The receiving component 1102 can receive a PDCCH communication scheduling a PUSCH communication that will include a Type II Doppler CSI. The offset determining component 1108 can determine a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting the Type II Doppler CSI. The transmitting component 1104 can transmit the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

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

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

[0143] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a first PDCCH communication that schedules a first PUSCH communication that will include Type II Doppler CSI; receiving a second PDCCH communication that schedules a second PUSCH communication, wherein the last symbol of the second PDCCH communication is after the last symbol of the first PDCCH communication in the time domain, and wherein the first symbol of the second PUSCH communication will be before the last symbol of the first PUSCH communication in the time domain; and sending the second PUSCH communication based at least in part on the second PDCCH communication.

[0144] Aspect 2: The method according to aspect 1, wherein the first PUSCH communication is associated with a first HARQ process identifier, and the second PUSCH communication is associated with a second HARQ process identifier, and the second HARQ process identifier is different from the first HARQ process identifier.

[0145] Aspect 3: The method according to aspect 2, wherein the first HARQ process identity is designated for PUSCH communication including Type II Doppler CSI.

[0146] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the first HARQ process identifier is configured via RRC signaling.

[0147] Aspect 5: The method according to aspect 1, wherein the first PUSCH communication is a UCI-only PUSCH communication.

[0148] Aspect 6: The method according to any one of aspects 1 and 5, wherein the first PUSCH communication is not associated with a HARQ process identifier.

[0149] Aspect 7: A method of wireless communication performed by a UE, the method comprising: receiving a PDCCH communication that schedules a PUSCH communication that will include a Type II Doppler CSI; determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with sending the Type II Doppler CSI; and sending the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

[0150] Aspect 8: The method according to aspect 7, wherein the time slot offset value corresponds to the time slot offset between the PDCCH communication and the PUSCH communication, wherein the time slot offset value is to be used for single PUSCH communication scheduling in FR1 and is permitted to be greater than a time slot offset value threshold.

[0151] Aspect 9: The method according to aspect 7, wherein the time slot offset value corresponds to the time slot offset between the last symbol of the CSI-RS burst and the first symbol of the PUSCH communication.

[0152] Aspect 10: The method of aspect 9, wherein the time slot offset is further determined based at least in part on a duration of the CSI-RS burst.

[0153] Aspect 11: The method according to any one of aspects 9 to 10, wherein the time slot offset is further determined based at least in part on a time slot offset associated with the PDCCH communication and the CSI-RS burst.

[0154] Aspect 12: A method according to any one of Aspects 9 to 11, wherein the time slot offset value is a default time slot offset value, and the time slot offset is further determined at least in part based on at least one of the following: a default value for the time slot offset value, the duration of the CSI-RS burst, or the number of symbols corresponding to the CSI processing time.

[0155] Aspect 13: 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 6.

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

[0157] Aspect 15: 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 6.

[0158] Aspect 16: 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 6.

[0159] Aspect 17: 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 6.

[0160] Aspect 18: 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 7 to 12.

[0161] Aspect 19: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 7 to 12.

[0162] Aspect 20: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 7 to 12.

[0163] Aspect 21: 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 7 to 12.

[0164] Aspect 22: 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 7 to 12.

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

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

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

[0168] Although the specific combination of features is set forth 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 described 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, and 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).

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

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a physical downlink control channel (PDCCH) communication scheduling a physical uplink shared channel (PUSCH) communication that will include type II Doppler channel state information (CSI); determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting Type II Doppler CSI; as well as The PUSCH communication is sent based at least in part on the PDCCH communication and the time slot offset.

2. The UE according to claim 1, wherein the time slot offset value corresponds to the time slot offset between the PDCCH communication and the PUSCH communication, The time slot offset value is to be used for single PUSCH communication scheduling in frequency range 1 (FR1) and is allowed to be greater than a time slot offset value threshold.

3. The UE of claim 1, wherein the slot offset value corresponds to a slot offset between a last symbol of a CSI reference signal (CSI-RS) burst and a first symbol of the PUSCH communication.

4. The UE of claim 3, wherein the time slot offset is further determined based at least in part on a duration of the CSI-RS burst.

5. The UE of claim 3, wherein the time slot offset is further determined based at least in part on a time slot offset associated with the PDCCH communication and the CSI-RS burst.

6. A UE according to claim 3, wherein the time slot offset value is a default time slot offset value, and the time slot offset is further determined at least in part based on at least one of the following: a default value for the time slot offset value, a duration of the CSI-RS burst, or a number of symbols corresponding to a CSI processing time.

7. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a physical downlink control channel (PDCCH) communication scheduling a physical uplink shared channel (PUSCH) communication that will include type II Doppler channel state information (CSI); determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting Type II Doppler CSI; as well as The PUSCH communication is sent based at least in part on the PDCCH communication and the time slot offset.

8. The method of claim 7, wherein the time slot offset value corresponds to the time slot offset between the PDCCH communication and the PUSCH communication, The time slot offset value is to be used for single PUSCH communication scheduling in frequency range 1 (FR1) and is allowed to be greater than a time slot offset value threshold.

9. The method of claim 7, wherein the slot offset value corresponds to a slot offset between a last symbol of a CSI reference signal (CSI-RS) burst and a first symbol of the PUSCH communication.

10. The method of claim 9, wherein the time slot offset is further determined based at least in part on a duration of the CSI-RS burst.

11. The method of claim 9, wherein the time slot offset is determined based further at least in part on a time slot offset associated with the PDCCH communication and the CSI-RS burst.

12. The method of claim 9, wherein the time slot offset value is a default time slot offset value, and the time slot offset is further determined at least in part based on at least one of: a default value for the time slot offset value, a duration of the CSI-RS burst, or a number of symbols corresponding to a CSI processing time.

13. 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 user equipment (UE), cause the UE to: receiving a physical downlink control channel (PDCCH) communication scheduling a physical uplink shared channel (PUSCH) communication that will include type II Doppler channel state information (CSI); determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting Type II Doppler CSI; as well as The PUSCH communication is sent based at least in part on the PDCCH communication and the time slot offset.

14. The non-transitory computer-readable medium of claim 13, wherein the time slot offset value corresponds to the time slot offset between the PDCCH communication and the PUSCH communication, wherein the time slot offset value is to be used for single PUSCH communication scheduling in frequency range 1 (FR1) and is permitted to be greater than a time slot offset value threshold.

15. The non-transitory computer-readable medium of claim 13, wherein the slot offset value corresponds to a slot offset between a last symbol of a CSI reference signal (CSI-RS) burst and a first symbol of the PUSCH communication.

16. The non-transitory computer-readable medium of claim 15, wherein the time slot offset is further determined based at least in part on a duration of the CSI-RS burst.

17. The non-transitory computer-readable medium of claim 15, wherein the time slot offset is determined based further at least in part on a time slot offset associated with the PDCCH communication and the CSI-RS burst.

18. A non-transitory computer-readable medium according to claim 15, wherein the time slot offset value is a default time slot offset value, and the time slot offset is further determined at least in part based on at least one of the following: a default value for the time slot offset value, a duration of the CSI-RS burst, or a number of symbols corresponding to a CSI processing time.

19. An apparatus for wireless communication, the apparatus comprising: means for receiving a physical downlink control channel (PDCCH) communication scheduling a physical uplink shared channel (PUSCH) communication that will include Type II Doppler channel state information (CSI); means for determining a time slot offset between the PDCCH communication and the PUSCH communication based at least in part on a time slot offset value to be used in association with transmitting Type II Doppler CSI; and Means for transmitting the PUSCH communication based at least in part on the PDCCH communication and the time slot offset.

20. The apparatus of claim 19, wherein the time slot offset value corresponds to the time slot offset between the PDCCH communication and the PUSCH communication, The time slot offset value is to be used for single PUSCH communication scheduling in frequency range 1 (FR1) and is allowed to be greater than a time slot offset value threshold.

21. The apparatus of claim 19, wherein the slot offset value corresponds to a slot offset between a last symbol of a CSI reference signal (CSI-RS) burst and a first symbol of the PUSCH communication.

22. The apparatus of claim 21, wherein the time slot offset is determined further based at least in part on a duration of the CSI-RS burst.

23. The apparatus of claim 21, wherein the slot offset is determined further based at least in part on a slot offset associated with the PDCCH communication and the CSI-RS burst.

24. An apparatus according to claim 21, wherein the time slot offset value is a default time slot offset value, and the time slot offset is further determined at least in part based on at least one of the following: a default value for the time slot offset value, a duration of the CSI-RS burst, or a number of symbols corresponding to a CSI processing time.

Images