WO2022027571A1 - Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro - Google Patents

Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro Download PDF

Info

Publication number
WO2022027571A1
WO2022027571A1 PCT/CN2020/107760 CN2020107760W WO2022027571A1 WO 2022027571 A1 WO2022027571 A1 WO 2022027571A1 CN 2020107760 W CN2020107760 W CN 2020107760W WO 2022027571 A1 WO2022027571 A1 WO 2022027571A1
Authority
WO
WIPO (PCT)
Prior art keywords
csi
pucch
tones
trigger
report
Prior art date
Application number
PCT/CN2020/107760
Other languages
English (en)
Inventor
Yi Huang
Huilin Xu
Yu Zhang
Chenxi HAO
Peter Gaal
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/107760 priority Critical patent/WO2022027571A1/fr
Publication of WO2022027571A1 publication Critical patent/WO2022027571A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027—Scheduling of signalling, e.g. occurrence thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0085—Timing of allocation when channel conditions change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0026—Division using four or more dimensions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload

Definitions

  • the technology discussed below relates generally to wireless communication systems, and more particularly, to using a zero power (ZP) -channel state information (CSI) -reference signal (RS) trigger to request an aperiodic CSI (A-CSI) report to be transmitted on the physical uplink control channel (PUCCH) .
  • ZP zero power
  • CSI channel state information
  • RS reference signal
  • Embodiments can provide and enable techniques for triggering A-CSI reports on PUCCH using a ZP-CSI-RS trigger to invoke multiple behaviors.
  • a method of wireless communication can include receiving, from a scheduling entity, a zero power (ZP) channel state information (CSI) -reference signal (RS) trigger specifying a codepoint i; identifying a plurality of tones corresponding to codepoint i using a list of ZP CSI-RS trigger states; performing rate matching around the plurality of tones as ZP CSI-RS tones; generating an aperiodic CSI (A-CSI) report based on channel quality measured using CSI-RSs transmitted on at least a subset of the plurality of tones; and transmitting the A-CSI report on a physical uplink control channel (PUCCH) .
  • ZP zero power
  • CSI channel state information
  • RS reference signal
  • the method can include transmitting, to a user equipment (UE) , a zero power (ZP) channel state information (CSI) -reference signal (RS) trigger specifying a codepoint i, wherein the UE has been configured to associate a plurality of tones with codepoint i; transmitting a plurality of CSI-RSs for the UE using the plurality of tones; performing rate matching around the plurality of tones designated as ZP CSI-RS tones for data transmitted for the UE using a physical downlink shared channel (PDSCH) resource; receiving, from the UE on a physical uplink control channel (PUCCH) resource, an aperiodic CSI (A-CSI) report indicative of channel quality measured using the plurality of CSI-RSs.
  • ZP zero power
  • CSI channel state information
  • RS reference signal
  • FIG. 1 is a schematic illustration of a wireless communication system in accordance with some aspects of the disclosed subject matter.
  • FIG. 2 is a conceptual illustration of an example of a radio access network in accordance with some aspects of the disclosed subject matter.
  • FIG. 3 is a block diagram illustrating a wireless communication system supporting multiple-input multiple-output (MIMO) communication in accordance with some aspects of the disclosed subject matter.
  • MIMO multiple-input multiple-output
  • FIG. 4 is a schematic illustration of an organization of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) in accordance with some aspects of the disclosed subject matter.
  • OFDM orthogonal frequency divisional multiplexing
  • FIG. 5 is a schematic illustration of a channel state information (CSI) request configured to trigger a CSI report on the physical uplink shared channel (PUSCH) and a trigger state list that can be used to determine a configuration for the CSI report in accordance with some aspects of the disclosed subject matter.
  • CSI channel state information
  • FIG. 6 is a schematic illustration of a communication system in which a pattern of tones can be used by a first user equipment (UE A) to generate an aperiodic CSI (A-CSI) report on PUSCH, excluded by a second user equipment (UE B) during rate matching, and used by UE B to generate an A-CSI report on PUCCH in accordance with some aspects of the disclosed subject matter.
  • UE A first user equipment
  • UE B aperiodic CSI
  • FIG. 7 is a schematic illustration of a zero power (ZP) CSI reference signal (RS) and trigger state lists to trigger a UE to exclude a pattern of tones during rate matching, and trigger state lists that can be used to determine the pattern of tones to exclude during rate matching, and a pattern of tones to use to generate an A-CSI report on PUCCH in accordance with some aspects of the disclosed subject matter.
  • ZP zero power
  • RS CSI reference signal
  • FIG. 8A is a schematic diagram of a technique for transmitting a CSI report on PUCCH in accordance with some aspects of the disclosed subject matter.
  • FIG. 8B is a schematic diagram of another technique for transmitting a CSI report on PUCCH in accordance with some aspects of the disclosed subject matter.
  • FIG. 9 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity in accordance with some aspects of the disclosed subject matter.
  • FIG. 10 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity in accordance with some aspects of the disclosed subject matter.
  • FIG. 11 is a flow chart illustrating an exemplary process for a scheduled entity to exclude a pattern of tones during rate matching and generate an A-CSI report on PUCCH responsive to a ZP CSI-RS trigger in accordance with some aspects of the disclosed subject matter.
  • FIG. 12 is a flow chart illustrating an exemplary process for a scheduling entity to request that a first UE generate an A-CSI report for a pattern of tones on PUSCH, and trigger a second UE to exclude the pattern of tones during rate matching and generate an A-CSI report for the pattern of tones on PUCCH responsive to a ZP CSI-RS trigger in accordance with some aspects of the disclosed subject matter.
  • Implementations can range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations.
  • devices incorporating described aspects and features can also necessarily include additional components and features for implementation and practice of claimed and described embodiments.
  • transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) .
  • innovations described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.
  • FIG. 1 is a schematic illustration of a wireless communication system 100 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • wireless communication system 100 can include three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106.
  • RAN radio access network
  • UE user equipment
  • UE 106 can be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.
  • an external data network 110 such as (but not limited to) the Internet.
  • RAN 104 can implement any suitable wireless communication technology or combination of technologies to provide radio access to UE 106.
  • RAN 104 can operate according to 3 rd Generation Partnership Project (3GPP) New Radio (NR) specifications, which is sometimes referred to as 5G NR or simply 5G.
  • 3GPP 3 rd Generation Partnership Project
  • NR New Radio
  • RAN 104 can operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, which is sometimes referred to as LTE.
  • eUTRAN Evolved Universal Terrestrial Radio Access Network
  • the 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN.
  • NG-RAN next-generation RAN
  • RAN 104 includes various base stations 108.
  • a base station can be used to implement a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE, such as UE 106.
  • UE such as UE 106.
  • various terminology has been used to refer to a network elements that act as a base station.
  • a base station can also be referred to by those skilled in the art using various terminology to refer to a network element that connects one or more UE apparatuses to one or more portions of core network 102, such as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.
  • BTS basic service set
  • ESS extended service set
  • AP access point
  • NB Node B
  • eNB eNode B
  • gNB gNode B
  • RAN 104 can support wireless communication for multiple mobile apparatuses.
  • a mobile apparatus can be referred to as user equipment (UE) in 3GPP standards, but can also be referred to by those skilled in the art using various terminology to refer to a network element that provides a user with access to one or more network services, such as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE can be an apparatus (e.g., a mobile apparatus) that provides a user with access to network services.
  • a "mobile” apparatus need not necessarily have a capability to move, and may be stationary.
  • the term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies.
  • UEs can include a number of hardware structural components sized, shaped, and arranged to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other.
  • a mobile apparatus examples include a mobile, a cellular (cell) phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an "Internet of things" (IoT) .
  • IoT Internet of things
  • a mobile apparatus can additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health and/or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc.
  • GPS global positioning system
  • a mobile apparatus can additionally be a digital home device or smart home device such as a home audio device, a home video device, and/or a home multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc.
  • a mobile apparatus can additionally be a smart energy device, a security device, a solar panel and/or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , a municipal infrastructure device controlling lighting, a municipal infrastructure device controlling water, etc. ; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weaponry, etc.
  • a mobile apparatus can provide for connected medicine or telemedicine support, e.g., health care at a distance.
  • Telehealth devices can include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information (e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data) .
  • wireless communication between RAN 104 and UE 106 illustrated in FIG. 1 can be described as utilizing an air interface.
  • Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmission.
  • DL downlink
  • the term downlink can refer to a point-to-multipoint transmission originating at a scheduling entity (e.g., base station 108) .
  • a downlink can be implemented using one or more broadcast channel multiplexing techniques.
  • transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions.
  • UL uplink
  • the term uplink can refer to a point-to-point transmission originating at a scheduled entity (e.g., UE 106) .
  • access to the air interface can be scheduled, wherein a scheduling entity (e.g., a base station of RAN 104, such as base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell.
  • a scheduling entity e.g., a base station of RAN 104, such as base station 108 allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities.
  • for scheduled communication scheduled entities e.g., UEs 106) can utilize resources allocated by a scheduling entity (e.g., base station 108) .
  • base stations 108 are not the only entities that can function as scheduling entities.
  • a UE can function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .
  • a scheduling entity can broadcast downlink traffic 112 to one or more scheduled entities (e.g., UEs 106) .
  • a scheduling entity e.g., base station 108 can act as a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities (e.g., UEs 106) to the scheduling entity (e.g., base station 108) .
  • a scheduled entity can act a node or device that receives downlink control information 114, which can include (but is not limited to) scheduling information (e.g., a grant) , synchronization or timing information, and/or other control information from another entity in the wireless communication network such as the scheduling entity (e.g., base station 108) .
  • scheduling information e.g., a grant
  • synchronization or timing information e.g., synchronization or timing information
  • base stations 108 can include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system.
  • backhaul 120 can provide a link between a particular base station and core network 102.
  • a backhaul network e.g., including backhaul 120
  • backhaul interfaces can be employed, such as a direct physical connection, a virtual network, and/or any other suitable connection, using any suitable transport network.
  • core network 102 can be a part of the wireless communication system 100, and can be independent of the radio access technology used in RAN 104.
  • core network 102 can be configured according to 5G standards (e.g., 5GC) .
  • core network 102 can be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.
  • EPC evolved packet core
  • UE 106 can simultaneously connect to multiple base stations 108 and/or can connect to a single base station 108 using multiple component carriers (e.g., at different frequencies) to increase the bandwidth available for communications to and/or from UE 106.
  • multiple component carriers e.g., at different frequencies
  • FIG. 2 is a conceptual illustration of an example of a radio access network 200 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • RAN 200 can be an implementation of RAN 104 described above in connection with, and illustrated in, FIG. 1.
  • the geographic area covered by RAN 200 can be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.
  • FIG. 2 illustrates macrocells 202, 204, and 206, and a small cell 208, each of which can include one or more sectors (not shown) .
  • a sector can be defined as a sub-area of a cell, and all sectors within one cell can be served by the same base station.
  • a radio link within a sector can be identified by a single logical identification belonging to that sector.
  • the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.
  • two base stations 210 and 212 are illustrated in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables.
  • cells 202, 204, and 206 can be referred to as macrocells, as base stations 210, 212, and 214 support cells having a relatively large size.
  • a base station 218 is shown in small cell 208 (which can be referred to, for example, as a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.
  • cell 208 can be referred to as a small cell, as base station 218 supports a cell having a relatively small size.
  • cell sizing can be done according to system design as well as component constraints.
  • radio access network 200 can include any number of wireless base stations and cells. Further, a relay node can be deployed to extend the size or coverage area of a given cell. Additionally, base stations 210, 212, 214, 218 can provide wireless access points to a core network for any number of mobile apparatuses. In some examples, base stations 210, 212, 214, and/or 218 can be particular implementations of base station 108 described above in connection with, and illustrated in, FIG. 1.
  • FIG. 2 further includes a quadcopter 220 (which is sometimes referred to as a drone) , which can be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile base station such as quadcopter 220.
  • a quadcopter 220 which is sometimes referred to as a drone
  • the cells may include UEs that may be in communication with one or more sectors of each cell.
  • each base station 210, 212, 214, 218, and 220 can be configured to provide an access point to a core network 102 (e.g., as described above in connection with FIG. 1) for all the UEs in the respective cells.
  • UEs 222 and 224 can be in communication with base station 210; UEs 226 and 228 can be in communication with base station 212; UEs 230 and 232 can be in communication with base station 214 by way of RRH 216; UE 234 can be in communication with base station 218; and UE 236 can be in communication with mobile base station 220.
  • UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and/or 242 can be particular implementations of UE 106 described above in connection with, and illustrated in, FIG. 1.
  • a mobile network node e.g., quadcopter 220
  • quadcopter 220 can be configured to function as a UE.
  • quadcopter 220 can operate within cell 202 by communicating with base station 210.
  • sidelink signals can be used between UEs without necessarily relying on scheduling or control information from a base station.
  • two or more UEs e.g., UEs 226 and 228, can communicate with each other using peer to peer (P2P) or sidelink signals without relaying that communication through a base station (e.g., base station 212) .
  • P2P peer to peer
  • UE 238 is illustrated communicating with UEs 240 and 242.
  • UE 238 can function as a scheduling entity or a primary sidelink device
  • UEs 240 and 242 can function as scheduled entities or a non-primary (e.g., secondary) sidelink device.
  • a UE can function as a scheduling entity in a device-to-device (D2D) , peer-to-peer (P2P) , vehicle-to-vehicle (V2V) network, and/or in a mesh network.
  • D2D device-to-device
  • P2P peer-to-peer
  • V2V vehicle-to-vehicle
  • UEs 240 and 242 can optionally communicate directly with one another in addition to communicating with a scheduling entity (e.g., UE 238) .
  • a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources.
  • the ability for a UE to communicate while moving, independent of its location can be referred to as mobility.
  • the various physical channels between the UE and the radio access network can generally be set up, maintained, and released under the control of an access and mobility management function (AMF, not illustrated, which can be provided via core network 102, which is described above in connection with FIG. 1) , which can include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality, and a security anchor function (SEAF) that performs authentication.
  • AMF access and mobility management function
  • SCMF security context management function
  • SEAF security anchor function
  • the air interface in the radio access network 200 can utilize one or more duplexing algorithms.
  • Duplex can refer to a point-to-point communication link between to nodes that is configured to facilitate communication by both endpoints in both directions.
  • Full duplex can refer to a configuration in which both endpoints can simultaneously communicate with one another.
  • Half duplex can refer to a configuration in which only one endpoint can send information to the other at a time.
  • a full duplex channel In a wireless link, a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies.
  • Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) . In FDD, transmissions in different directions can operate at different carrier frequencies.
  • FDD frequency division duplex
  • TDD time division duplex
  • transmissions in different directions on a given channel can be separated from one another using time division multiplexing. That is, at some times the channel can be dedicated for transmissions in one direction, while at other times the channel can be dedicated for transmissions in the other direction, where the direction can change very rapidly, e.g., several times per slot.
  • the scheduling entity and/or scheduled entity can be configured to implement beamforming and/or multiple-input multiple-output (MIMO) technology.
  • FIG. 3 is a block diagram illustrating a wireless communication system 300 supporting MIMO communication in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • Beamforming can generally refer to directional signal transmission or reception.
  • the amplitude and phase of each antenna in an array of antennas can be precoded, or controlled to create a desired (e.g., directional) pattern of constructive and destructive interference in the wavefront.
  • a transmitter 302 can include multiple transmit antennas 304 (e.g., N transmit antennas) and a receiver 306 can include multiple receive antennas 308 (e.g., M receive antennas) .
  • N transmit antennas e.g., N transmit antennas
  • M receive antennas multiple receive antennas 308 .
  • there are N ⁇ M signal paths 310 e.g., corresponding to a DL transmission to receiver 306 from transmit antennas 304 to receive antennas 308.
  • Each of transmitter 302 and receiver 306 can be implemented, for example, within a scheduling entity (e.g., base station 108) , a scheduled entity (e.g., UE 106) , or any other suitable wireless communication device. Additionally, in some aspects, each of transmitter 302 and receiver 306 can be implemented to operate as both a transmitter and a receiver. For example, receive antennas 308 (and/or corresponding transmit antennas of receiver 306) can be used to transmit signals, and transmit antennas 304 (and/or corresponding receive antennas of transmitter 302) can be used to receive signals. Thus, in such an example, there can be M ⁇ N corresponding signal paths (e.g., corresponding to a UL transmission to transmitter 308) . Each of transmitter 302 and receiver 306 can be implemented, for example, within a scheduling entity 108, a scheduled entity 106, or any other suitable wireless communication device.
  • a MIMO system can use multiple antenna technology to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.
  • spatial multiplexing can be used to transmit multiple different streams of data, also referred to as layers, simultaneously on the same time-frequency resource.
  • a transmitter can send multiple data streams to a single receiver.
  • a MIMO system can take advantage of capacity gains and/or increased data rates associated with using multiple antennas in rich scattering environments where channel variations can be tracked.
  • the receiver can track these channel variations and provide corresponding feedback to the transmitter. For example, as shown in FIG.
  • a simplest case can be illustrated using a rank-2 (i.e., including 2 data streams) spatial multiplexing transmission on a 2x2 MIMO antenna configuration will transmit two data streams via two transmit antennas 304.
  • the signal from each transmit antenna 304 reaches each receive antenna 308 along a different signal path 310.
  • Receiver 306 can then reconstruct the data streams using the received signals from each receive antenna 308.
  • a transmitter can send multiple data streams to multiple receivers.
  • This can generally be referred to as multi-user MIMO (MU-MIMO) .
  • MU-MIMO multi-user MIMO
  • a MU-MIMO system can exploit multipath signal propagation to increase the overall network capacity by increasing throughput and spectral efficiency, and reducing the required transmission energy.
  • This can be achieved by spatially precoding (i.e., multiplying the data streams with different weighting and phase shifting) each data stream (in some examples, based on known channel state information) and then transmitting each spatially precoded stream through multiple transmit antennas to the receiving devices using the same allocated time-frequency resources.
  • the receiver may transmit feedback including a quantized version of the channel so that the transmitter can schedule the receivers with good channel separation.
  • the spatially precoded data streams arrive at the receivers with different spatial signatures, which enables the receiver (s) (in some examples, in combination with known channel state information) to separate these streams from one another and recover the data streams destined for that receiver.
  • multiple transmitters can each transmit a spatially precoded data stream to a single receiver, which enables the receiver to identify the source of each spatially precoded data stream.
  • the number of data streams or layers in a MIMO or MU-MIMO (generally referred to as MIMO) system corresponds to the rank of the transmission.
  • the rank of a MIMO system is limited by the number of transmit antennas 304 or receive antennas 308, whichever is lower.
  • the channel conditions at the receiving device, as well as other considerations, such as the available resources at the transmitting device, can also affect the transmission rank. For example, a base station in a cellular RAN can assign a rank (and therefore, a number of data streams) for a DL transmission to a particular UE based on a rank indicator (RI) the UE transmits to the base station.
  • RI rank indicator
  • the UE can determine this RI based on the antenna configuration (e.g., the number of transmit and receive antennas) and a measured signal-to-interference-and-noise ratio (SINR) on each of the receive antennas.
  • the RI can indicate, for example, the number of layers that can be supported under the current channel conditions.
  • the base station can use the RI along with resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign a DL transmission rank to the UE.
  • the transmitting device can determine the precoding of the transmitted data stream or streams based, for example, on known channel state information of the channel on which the transmitting device transmits the data stream (s) .
  • the transmitting device can transmit one or more suitable reference signals (e.g., a channel state information reference signal, or CSI-RS) that the receiving device can measure.
  • the receiver can then report measured channel quality information (CQI) back to the transmitting device.
  • CQI channel quality information
  • This CQI generally reports the current communication channel quality, and in some examples, a requested transport block size (TBS) for future transmissions to the receiver.
  • TBS transport block size
  • the receiver can further report a precoding matrix indicator (PMI) back to the transmitting device.
  • PMI precoding matrix indicator
  • This PMI generally reports the receiving device's preferred precoding matrix for the transmitting device to use, and can be indexed to a predefined codebook.
  • the transmitting device can then utilize this CQI/PMI to determine a suitable precoding matrix for transmissions to the receiver.
  • a base station can assign a rank for DL MIMO transmissions based on an UL SINR measurement (e.g., based on a sounding reference signal (SRS) or other pilot signal transmitted from the UE) . Based on the assigned rank, the base station can then transmit channel state information reference signals (CSI-RS) with separate sequences for each layer to provide for multi-layer channel estimation. From the CSI-RS, the UE can measure the channel quality across layers and resource blocks. The UE can then transmit a CSI report (including, e.g., CQI, RI, and PMI) to the base station for use in updating the rank and assigning resources for future downlink transmissions.
  • CSI-RS channel state information reference signals
  • channel coding can be used. That is, wireless communication can generally utilize a suitable error correcting block code.
  • an information message or sequence is split up into code blocks (CBs) , and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. Exploitation of this redundancy in the encoded information message can improve the reliability of the message, enabling correction for bit errors that may occur due to the noise.
  • CBs code blocks
  • CODEC code blocks
  • user data can be coded using quasi-cyclic low-density parity check (LDPC) with two different base graphs: one base graph for large code blocks and/or high code rates, while the other base graph is used otherwise.
  • Control information and the physical broadcast channel (PBCH) can be coded using Polar coding, based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.
  • scheduling entities 108 and scheduled entities 106 can include suitable hardware and capabilities (e.g., an encoder, a decoder, and/or a CODEC) to utilize one or more of these channel codes for wireless communication.
  • suitable hardware and capabilities e.g., an encoder, a decoder, and/or a CODEC
  • the air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices.
  • 5G NR specifications provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and for multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) .
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) .
  • DFT-s-OFDM discrete Fourier transform-spread-OFDM
  • SC-FDMA single-carrier FDMA
  • a UE may provide for UL multiple access utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • SCMA sparse code multiple access
  • RSMA resource spread multiple access
  • a base station 210 may multiplex DL transmissions to UEs 222 and 224 utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.
  • TDM time division multiplexing
  • CDM code division multiplexing
  • FDM frequency division multiplexing
  • OFDM orthogonal frequency division multiplexing
  • SCM sparse code multiplexing
  • FIG. 4 is a schematic illustration of an organization of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • OFDM orthogonal frequency divisional multiplexing
  • a frame can refer to a duration of 10 milliseconds (ms) for wireless transmissions, with each frame including 10 subframes of 1 ms each.
  • ms milliseconds
  • FIG. 4 an expanded view of an exemplary DL subframe 402 is illustrated, showing an OFDM resource grid 404.
  • the PHY transmission structure for any particular application can vary from the example described here, depending on any number of factors.
  • time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers or tones.
  • Resource grid 404 can be used to schematically represent time–frequency resources for a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, a corresponding multiple number of resource grids 404 can be available for communication. Resource grid 404 can be divided into multiple resource elements (REs) 406. An RE, which is 1 subcarrier ⁇ 1 symbol, is the smallest discrete part of the time–frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more bits of information.
  • RE resource elements
  • a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 408, which contains any suitable number of consecutive subcarriers in the frequency domain.
  • PRB physical resource block
  • RB resource block
  • an RB can include 12 subcarriers, a number independent of the numerology used.
  • an RB can include any suitable number of consecutive OFDM symbols in the time domain.
  • a UE generally utilizes only a subset of resource grid 404.
  • An RB can be the smallest unit of resources that can be allocated to a UE.
  • the modulation scheme chosen for the air interface increases, and data rates that can be achieved by the UE also increase.
  • RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408.
  • subframe 402 can have a bandwidth corresponding to any number of one or more RBs 408.
  • RB 408 is shown as occupying less than the entire duration of subframe 402, although this is merely one possible example.
  • Each subframe 402 can include one or multiple adjacent slots.
  • one subframe 402 includes four slots 410, as an illustrative example.
  • a slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length.
  • CP cyclic prefix
  • a slot can include 7 or 14 OFDM symbols with a nominal CP.
  • Additional examples can include mini-slots having a shorter duration (e.g., 1, 2, 4, or 7 OFDM symbols) . Such mini-slots can in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs.
  • An expanded view of one of the slots 410 illustrates slot 410 including a control region 412 and a data region 414.
  • control region 412 can carry control channels (e.g., PDCCH)
  • data region 414 can carry data channels (e.g., PDSCH or PUSCH) .
  • a slot can contain various combinations of DL and UL, such as all DL, all UL, or at least one DL portion and at least one UL portion.
  • the simple structure illustrated in FIG. 4 is merely exemplary in nature, and different slot structures can be utilized, and can include one or more of each of the control region (s) and data region (s) .
  • various REs 406 within an RB 408 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc.
  • Other REs 406 within RB 408 can also carry pilot signals and/or reference signals. These pilot signals and/or reference signals can facilitate performance of channel estimation of the corresponding channel by a receiving device, which can enable coherent demodulation/detection of the control and/or data channels within RB 408.
  • the transmitting device e.g., the base station 108 can allocate one or more REs 406 (e.g., within a control region 412) to carry DL control information (e.g., downlink control information 114 described above in connection with FIG. 1) including one or more DL control channels that generally carry information originating from higher layers, such as a physical broadcast channel (PBCH) , a physical downlink control channel (PDCCH) , etc., to one or more scheduled entities (e.g., a particular UE 106) .
  • DL REs can be allocated to carry DL physical signals that generally do not carry information originating from higher layers.
  • These DL physical signals can include a primary synchronization signal (PSS) ; a secondary synchronization signal (SSS) ; demodulation reference signals (DM-RS) ; phase-tracking reference signals (PT-RS) ; channel-state information reference signals (CSI-RS) ; etc.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • DM-RS demodulation reference signals
  • PT-RS phase-tracking reference signals
  • CSI-RS channel-state information reference signals
  • the synchronization signals PSS and SSS (collectively referred to as SS) , and in some examples, the PBCH, can be transmitted in an SS block that includes 4 consecutive OFDM symbols (e.g., numbered via a time index in increasing order from 0 to 3) .
  • the SS block can extend over 240 contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from 0 to 239.
  • the disclosed subject matter is not limited to this specific SS block configuration.
  • Nonlimiting examples can utilize greater or fewer than two synchronization signals; can include one or more supplemental channels in addition to the PBCH; can omit a PBCH; and/or can utilize nonconsecutive symbols for an SS block, without departing from the scope of the present disclosure.
  • the PDCCH can carry downlink control information (DCI) for one or more UEs in a cell.
  • DCI downlink control information
  • This can include, but is not limited to, power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions.
  • a transmitting device e.g., UE 106 can utilize one or more REs 406 to carry UL control information (UCI) (e.g., uplink control information 118 described above in connection with FIG. 1) .
  • the UCI can originate from higher layers via one or more UL control channels, such as a physical uplink control channel (PUCCH) , a physical random access channel (PRACH) , etc., to the scheduling entity (e.g., base station 108) .
  • UL REs may carry UL physical signals that generally do not carry information originating from higher layers, such as demodulation reference signals (DM-RS) , phase-tracking reference signals (PT-RS) , sounding reference signals (SRS) , etc.
  • DM-RS demodulation reference signals
  • PT-RS phase-tracking reference signals
  • SRS sounding reference signals
  • the control information (e.g., uplink control information 118) can include a scheduling request (SR) , i.e., a request for the scheduling entity 108 to schedule uplink transmissions.
  • SR scheduling request
  • the scheduling entity e.g., base station 108
  • downlink control information e.g., downlink control information 114 that can schedule resources for uplink packet transmissions.
  • UL control information can also include hybrid automatic repeat request (HARQ) feedback such as an acknowledgment (ACK) or negative acknowledgment (NACK) , channel state information (CSI) , and/or any other suitable UL control information.
  • HARQ is a technique well-known to those of ordinary skill in the art, in which the integrity of packet transmissions can be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC) . If the integrity of the transmission confirmed, an ACK can be transmitted, whereas if not confirmed, a NACK can be transmitted. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement chase combining, incremental redundancy, etc.
  • CRC cyclic redundancy check
  • one or more REs 406 can be allocated for user data or traffic data.
  • traffic can be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH) ; or for an UL transmission, a physical uplink shared channel (PUSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the RAN can provide system information (SI) characterizing the cell.
  • This system information can be provided utilizing minimum system information (MSI) , and other system information (OSI) .
  • MSI minimum system information
  • OSI system information
  • the MSI can be periodically broadcast over the cell to provide the most basic information required for initial cell access, and for acquiring any OSI that may be broadcast periodically or sent on-demand.
  • the MSI can be provided over two different downlink channels.
  • the PBCH can carry a master information block (MIB)
  • the PDSCH can carry a system information block type 1 (SIB1) , which is sometimes referred to as the remaining minimum system information (RMSI) .
  • SIB1 system information block type 1
  • the MIB can include parameters for monitoring a control resource set, which can provide the UE with scheduling information corresponding to the PDSCH, e.g., a resource location of SIB1.
  • OSI can include any SI that is not broadcast in the MSI.
  • the PDSCH can carry multiple SIBs, not limited to SIB1, described above.
  • the OSI can be provided in these SIBs, e.g., SIB2 and/or above.
  • the channels or carriers described above and illustrated in FIGS. 1 and 4 are not necessarily all the channels or carriers that can be utilized between a scheduling entity (e.g., base station 108) and scheduled entities (e.g., UEs 106) , and those of ordinary skill in the art will recognize that other channels or carriers can be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.
  • These physical channels described above are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer.
  • Transport channels carry blocks of information called transport blocks (TB) .
  • the transport block size (TBS) which can correspond to a number of bits of information, can be a controlled parameter, based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.
  • FIG. 5 is a schematic illustration of a channel state information (CSI) request configured to trigger a CSI report on the physical uplink shared channel (PUSCH) and a trigger state list that can be used to determine a configuration for the CSI report in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • a scheduling entity e.g., base station 108 can schedule a user equipment (e.g., UE 106) to transmit an aperiodic CSI (A-CSI) report on the PUSCH using the uplink (UL) grant.
  • A-CSI aperiodic CSI
  • the scheduling entity can use a "CSI request" field 502 in downlink control information (DCI) transmitted to schedule transmission on PUSCH.
  • DCI downlink control information
  • DCI format 0_1 includes the CSI request field that has a length from 0 to 6 bits (e.g., 0, 1, 2, 3, 4, 5, or 6 bits) , which can be determined by a higher layer parameter (e.g., parameter reportTriggerSize) .
  • a higher layer parameter e.g., parameter reportTriggerSize
  • the CSI request field is set to 0 bits, it can indicate that no CSI request is include in the DCI. Otherwise, the value encoded in CSI request field 502 can be a codepoint 504 between 0 and M, where M ⁇ 63.
  • the UE can store a PUSCH trigger state list 506 that includes M trigger states corresponding to codepoints 504.
  • a scheduling entity can configure PUSCH trigger state list 506.
  • the scheduling entity can associate each trigger state with a set 508 of one or more report configurations 510 (which can sometimes be referred to as ReportConfigs) .
  • Each report configuration 510 can be associated with various CSI reference signal (RS) resource settings 512, and can be designated as periodic, semipersistent, or aperiodic.
  • RS CSI reference signal
  • Each CSI-RS resource setting 512 can be a periodic CSI-RS resource setting, a semipersistent CSI-RS resource setting, or an aperiodic CSI-RS resource setting.
  • trigger state 2 is associated with N report configurations (e.g., report configuration 510-1, report configuration 510-2, ..., report configuration 510-N) , and each report configuration is associated with one, two, or three CSI-RS resource settings.
  • report configuration 510-1 is associated with CSI-RS resource setting 512-1
  • report configuration 510-2 is associated with CSI-RS resource setting 512-2 and CSI-RS resource setting 512-3
  • report configuration 510-2 is associated with CSI-RS resource setting 512-4, CSI-RS resource setting 512-5, and CSI-RS resource setting 512-6.
  • each report configuration can be associated with different CSI-RS resource settings (e.g., CSI-RS resource settings 512-1 may or may not be the same as CSI-RS resource setting 512-2) .
  • CSI-RS resource settings 512 can identify one or more tones on which CSI-RSs are scheduled to be transmitted by the scheduling entity for the UE to use to generate a CSI report.
  • tones identified in CSI-RS resource settings 512 can correspond to non-zero power (NZP) CSI-RSs that are scheduled for transmission.
  • FIG. 6 is a schematic illustration of a communication system 600 in which a pattern of tones can be used by a first user equipment 604 (UE A) to generate an aperiodic CSI (A-CSI) report on PUSCH, excluded by a second user equipment 606 (UE B) during rate matching, and used by UE 606 to generate an A-CSI report on PUCCH in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • a base station 602 schedules UE 604 to transmit an aperiodic A-CSI report on the PUSCH using the UL grant.
  • the CSI request transmitted by base station 602 can specify a tone pattern 608 that is to be used by UE 604 to measure channel state information and generate the A-CSI report. As described above in connection with FIG. 5, these tones can be referred to as NZP-CSI-RSs. In some aspects, transmission of the NZP-CSI-RSs 608 for UE 604 can cause interference on those tones for other UEs (e.g., UE 606) .
  • base station 602 can facilitate other UEs in mitigating potential interference caused by NZP-CSI-RSs 608 for UE 604 by identifying a zero power (ZP) CSI-RSs tone pattern 610 for the UEs.
  • the scheduling entity can use a ZP CSI-RS trigger field in downlink control information (DCI) transmitted in DL grant.
  • the base station can transmit the ZP CSI-RS trigger field in DCI having any suitable DCI format, such as DCI format 1_0, 1_1, or 1_2.
  • the UE that receives the ZP CSI-RS trigger field can use the information to rate match the UE's physical downlink shared channel (PDSCH) around various tones identified using the ZP CSI-RS trigger field.
  • the ZP CSI-RS trigger field has a length from 0 to 2 bits (e.g., 0, 1, or 2 bits) .
  • the bitwidth can equal log 2 (n ZP +1) , where n ZP is the number of aperiodic ZP CSI-RS resources sets configured by a higher layer (e.g., as defined in 3GPP TS 38.214, clause 5.1.4.2) .
  • the ZP CSI-RS trigger field can indicate that a ZP CSI-RS trigger is not included in the DCI. Otherwise, the value encoded in the ZP CSI-RS trigger field can be a codepoint between 0 and M, where M ⁇ 4.
  • the UE can store a ZP CSI-RS trigger state list that includes M trigger states corresponding to various codepoints, where each trigger state identifies a ZP CSI-RS tone pattern (e.g., ZP CSI-RS tone pattern 610) to be used by the UE (e.g., UE 606) to rate match around due to those tones being used to transmit NZP CSI-RSs for UE 604.
  • the UE can use the codepoint in the ZP CSI-RS trigger field to trigger generation of an A-CSI report to be transmitted on PUCCH (e.g., rather than using PUSCH, which is used to transmit an A-CSI report triggered by the CSI request described above in connection with FIG. 5) .
  • the UE can generate the A-CSI report using a tone pattern 612 that is associated with the codepoint in a PUCCH trigger state list that identifies tones on which NZP-CSI-RSs are scheduled to be transmitted for UE 606.
  • NZP-CSI-RSs 612 for UE 606 can be scheduled on the same tones on which NZP-CSI-RSs 608 for UE 604 are scheduled.
  • utilizing the codepoint in the ZP CSI-RS trigger field to trigger generation of an A-CSI report to be transmitted on PUCCH can provide additional opportunities for the base station to request A-CSI reports, because the base station does not need to schedule the transmission of the A-CSI report in an UL slot which may be required less often than DL slots for many UEs. For example, a portion of a DL slot can be reserved for transmitting information from the UE to the base station using PUCCH, providing frequent opportunities to transmit an A-CSI report. In some cases, the base station can receive more up-to-date CSI information from an A-CSI report transmitted using PUCCH which can facilitate DL scheduling.
  • re-using the codepoint in the ZP CSI-RS trigger field can facilitate base stations to trigger the UE to generate an A-CSI report schedule for transmission on PUCCH without requiring that an additional field be added to the DL DCI.
  • a field can be added to DL DCI (e.g., in DCI format 1_0, 1_1, and/or 1_2) that is similar to the CSI request field provided in UL DCI (e.g., DCI format 0_1) , which would increase DL DCI overhead.
  • FIG. 7 is a schematic illustration of a zero power (ZP) CSI reference signal (RS) and trigger state lists to trigger a UE to exclude a pattern of tones during rate matching, and trigger state lists that can be used to determine the pattern of tones to exclude during rate matching, and a pattern of tones to use to generate an A-CSI report on PUCCH in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • a scheduling entity e.g., base station 108, base station 606 can transmit a ZP CSI-RS trigger field 702 using the DL grant. As described above in connection with FIG.
  • ZP CSI-RS trigger field 702 can indicate to a user equipment (e.g., UE 106, UE 606) that a set of resources (e.g., tones) are ZP CSI-RSs for that UE, which can cause the UE to rate match around those resources for transmissions on PDSCH.
  • the scheduling entity can include ZP CSI-RS trigger field 702 in DCI transmitted to schedule transmission to the UE on PDSCH.
  • each ZP CSI-RS trigger state 706 can include a ZP CSI-RS resource setting that can identify one or more tones to rate match around (e.g., because those tones are scheduled to transmit CSI-RSs for another UE) .
  • tones identified in ZP CSI-RS resource settings 706 can correspond to ZP CSI-RSs for the UE.
  • a scheduling entity can configure ZP CSI-RS trigger states 706. For example, the scheduling entity can associate each codepoint with a particular ZP CSI-RS resource setting identifying a pattern of tones that are to be used by another UE.
  • a scheduling entity e.g., base station 108 can schedule a user equipment (e.g., UE 106) to transmit an aperiodic CSI (A-CSI) report on PUCCH using ZP CSI-RS trigger field 702.
  • A-CSI aperiodic CSI
  • the value encoded in ZP CSI-RS trigger field 702 can be a codepoint 708 between 0 and M, where M ⁇ 4.
  • the UE can store a PUCCH A-CSI trigger state 710 that includes M trigger states corresponding to codepoints 708.
  • a scheduling entity can configure PUCCH trigger state list 710. For example, the scheduling entity can associate each trigger state with a set 712 of one or more report configurations 714.
  • Each report configuration 714 can be associated with a CSI-RS resource setting 716, and can be designated as periodic, semipersistent, or aperiodic.
  • coidepoint i is associated with a ZP CSI-RS resource setting identifying a tone pattern i
  • coidepoint i is also associated with trigger state i in PUCCH A-CSI trigger state list 710.
  • Trigger state i is associated with N report configurations (e.g., report configuration 714-1, report configuration 714-2, ..., report configuration 714-N) , and each report configuration is associated the same set of CSI-RS resource settings 716 that each identify tone pattern i.
  • CSI-RS resource settings 716 associated with state i can include identical resources to resources specified by ZP CSI-RS trigger state 706 corresponding to codepoint i.
  • the intersection of CSI-RS resource settings 716 associated with state i and resources specified by ZP CSI-RS trigger state 706 corresponding to codepoint i can include all elements of CSI-RS resource settings 716, but may exclude one or more elements of resources specified by ZP CSI-RS trigger state 706.
  • each resource specified by CSI-RS resource settings 716 associated with state i can also be included in the resources specified by ZP CSI-RS trigger state 706 corresponding to codepoint i, but resources specified by ZP CSI-RS trigger state 706 corresponding to codepoint i can include additional resources.
  • the UE can generate a CSI report for less than all of the tones specified as ZP CSI-RS tones.
  • CSI-RS resource settings 716 can be omitted from state i, and the UE can determine which resources to measure using resources specified by ZP CSI-RS trigger state 706 corresponding to codepoint i.
  • the UE that receives ZP CSI-RS trigger field 702 with codepoint i can rate match around tones identified in tone pattern i for PDSCH, and can also use the same tone pattern i to measure channel state information and generate the A-CSI report to be transmitted on PUCCH.
  • the scheduling entity can transmit NZP CSI-RSs for the different UEs using the same tones, but using one or more multiplexing techniques to mitigate interference. For example, the scheduling entity can use different codes to transmit the NZP CSI-RSs for the different UEs.
  • a UE storing PUCCH A-CSI trigger state list 710 can receive an indication (e.g., from a base station) of whether to use PUCCH A-CSI trigger state list 710 in response to receiving a ZP CSI-RS trigger.
  • a scheduling entity e.g., a base station
  • the scheduling entity can transmit such an indication as a 1 bit indicator that indicates whether the UE is to enable PUCCH A-CSI trigger state list 710 based on whether the bit is a 1 or 0. For example, if the scheduling entity transmits a 1, the UE can enable use of PUCCH A-CSI trigger state list 710. As another example, if the scheduling entity transmits a 0, the UE can inhibit use of PUCCH A-CSI trigger state list 710.
  • the UE can enable use of PUCCH A-CSI trigger state list 710 using any suitable technique or combination of techniques. For example, the UE can enable use of PUCCH A-CSI trigger state list 710 using by setting a flag associated with PUCCH A-CSI trigger state list 710 to 1 to indicate that use of PUCCH A-CSI trigger state list 710 is enabled. As another example, the UE can enable use of PUCCH A-CSI trigger state list 710 by setting a pointer used to identify a particular PUCCH A-CSI trigger state list that is to be referenced in response to receiving a ZP CSI-RS trigger to point to PUCCH A-CSI trigger state list 710.
  • the UE can inhibit use of PUCCH A-CSI trigger state list 710 using any suitable technique or combination of techniques.
  • the UE can inhibit use of PUCCH A-CSI trigger state list 710 by setting a flag associated with PUCCH A-CSI trigger state list 710 to 0 to indicate that use of PUCCH A-CSI trigger state list 710 is inhibited.
  • the UE can inhibit use of PUCCH A-CSI trigger state list 710 by setting a pointer used to identify a particular PUCCH A-CSI trigger state list that is to be referenced in response to receiving a ZP CSI-RS trigger to point to a different PUCCH A-CSI trigger state list, such as a null list that includes no information.
  • the UE can take no actions related to generating an A-CSI report in response to a ZP CSI-RS trigger.
  • FIGS. 8A and 8B are schematic diagrams of techniques for transmitting a CSI report on PUCCH in accordance with some aspects of the disclosed subject matter, and are described as illustrative examples without limitation.
  • a UE that generates an A-CSI report in response to a ZP CSI-RS trigger can transmit the A-CSI report using a PUCCH resource that is independently scheduled for transmission of HARQ-ACK information by the DL grant that included the ZP CSI-RS trigger.
  • a UE that generates an A-CSI report in response to a ZP CSI-RS trigger can transmit the A-CSI report using a PUCCH resource that is independently scheduled for transmission of the A-CSI report by the DL grant that included the ZP CSI-RS trigger.
  • transmitting the A-CSI report and the HARQ-ACK separately can mitigate the probability of errors, as both the A-CSI report and the HARQ-ACK can be self-decodable.
  • transmitting the A-CSI report and the HARQ-ACK can mitigate the probability of errors, as both the A-CSI report and the HARQ-ACK can be self-decodable.
  • the A-CSI report and the HARQ-ACK are transmitted together using the same resource they may not be self-decodable, which can lead to an error in one payload impacting the ability to decode both payloads.
  • a scheduling entity can include a field (e.g., a 3 bit field representing K1) that points to a PUCCH resource scheduled for the UE to use for transmitting HARQ-ACK. If the A-CSI report is transmitted with HARQ-ACK, the UE can use that single field to determine which PUCCH resource to use to transmit the combined payload. Alternatively, in some aspects, if the A-CSI report is to be transmitted separately from HARQ-ACK, a scheduling entity can include an additional field (e.g., a 2 bit or 3 bit field) that points to a PUCCH resource scheduled for the UE to use for transmitting the A-CSI report. As shown in FIGS.
  • transmitting the A-CSI report separately from HARQ-ACK can facilitate earlier transmission of the A-CSI report.
  • z can represent a time between the DL grant and transmission of the A-CSI report
  • z' can represent a time between transmission of the CSI-RSs for the UE and transmission of the A-CSI report.
  • z and z' can be reduced by scheduling transmission of the A-CSI report and HARQ-ACK separately.
  • FIG. 9 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity 900 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • scheduling entity 900 can be a user equipment (UE) as illustrated in any one or more of FIGS. 1, 2, and/or 3.
  • UE user equipment
  • scheduling entity 900 can be a base station as illustrated in any one or more of FIGS. 1, 2, and/or 3.
  • scheduling entity 1000 can be implemented with a processing system 914 that includes one or more processors 904.
  • processors 904 include central processing units (CPUs) , microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , graphics processing units (GPUs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors 904 include central processing units (CPUs) , microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , graphics processing units (GPUs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • scheduling entity 900 can be configured to perform any one or more of the functions described herein. That is, processor 904,
  • processing system 914 can be implemented with a bus architecture, represented generally by the bus 902.
  • Bus 902 can include any number of interconnecting buses and bridges depending on the specific application of processing system 914 and the overall design constraints.
  • Bus 902 can communicatively couple together various circuits including one or more processors (represented generally by processor 904) , memory 905, and computer-readable media (represented generally by computer-readable medium 906) .
  • Bus 902 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 908 can provide an interface between bus 902 and a transceiver 910.
  • Transceiver 910 can provide a communication interface or means for communicating with various other apparatus over a transmission medium.
  • a user interface 912 e.g., keypad, display, speaker, microphone, joystick
  • a user interface 912 can be omitted in some examples, such as a base station.
  • processor 904 can include ZP CSI-RS triggering circuitry 940 configured for various functions, including, for example, configuring a ZP CSI-RS trigger, selecting a codepoint to include in the ZP CSI-RS trigger, causing a ZP CSI-RS trigger to be transmitted to a second UE in response to an A-CSI request being transmitted to a first UE.
  • ZP CSI-RS triggering circuitry 940 can be configured to implement one or more of the functions described below in connection with FIG. 12, such as functions described in connection with 1208.
  • processor 904 can include PUCCH A-CSI state configuration circuitry 942 configured for various functions, including, for example, configuring a PUCCH A-CSI trigger state list for a UE, and causing the UE to enable or inhibit use of the PUCCH A-CSI trigger state list for UE B information to control whether a ZP CSI-RS trigger causes the UE to generate an A-CSI report.
  • PUCCH A-CSI state configuration circuitry 942 can be configured to implement one or more of the functions described below in connection with FIG. 12, such as functions described in connection with 1202 and/or 1204.
  • Processor 904 can manage bus 902 and can perform general processing, including the execution of software stored on computer-readable medium 906, which, when executed by processor 904, causes processing system 914 to perform the various functions described above (e.g., in connection with FIGS. 8 and 9) for any particular apparatus.
  • computer-readable medium 906 and memory 905 can also be used for storing data that is manipulated by processor 904 when executing software.
  • One or more processors 904 in the processing system can execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software can reside on a computer-readable medium 906.
  • the computer-readable medium 906 can be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip) , an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (e.g., a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software and/or instructions that can be accessed and read by a computer.
  • a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
  • an optical disk e.g., a compact disc (CD) or a digital versatile disc (DVD)
  • the computer-readable medium 906 can reside in the processing system 914, external to the processing system 914, or distributed across multiple entities including the processing system 914.
  • the computer-readable medium 906 can be embodied in a computer program product.
  • a computer program product can include a computer-readable medium in packaging materials.
  • computer-readable storage medium 906 can include ZP CSI-RS triggering software 952 configured for various functions, including, for example, configuring a ZP CSI-RS trigger, selecting a codepoint to include in the ZP CSI-RS trigger, causing a ZP CSI-RS trigger to be transmitted to a second UE in response to an A-CSI request being transmitted to a first UE.
  • ZP CSI-RS triggering software 952 can be configured to implement one or more of the functions described below in connection with FIG. 12, such as functions described in connection with 1208.
  • computer-readable storage medium 906 can include PUCCH A-CSI state configuration software 954 configured for various functions, including, for example, configuring a PUCCH A-CSI trigger state list for a UE, and causing the UE to enable or inhibit use of the PUCCH A-CSI trigger state list for UE B information to control whether a ZP CSI-RS trigger causes the UE to generate an A-CSI report.
  • PUCCH A-CSI state configuration software 954 can be configured to implement one or more of the functions described below in connection with FIG. 12, such as functions described in connection with 1202 and/or 1204.
  • scheduling entity 900 can include means for transmitting a ZP CSI-RS trigger, and means for configuring a PUCCH A-CSI trigger state list.
  • the aforementioned means can be the processor (s) 904 shown in FIG. 9 configured to perform the functions recited by the aforementioned means.
  • the aforementioned means can be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.
  • circuitry included in the processor 904 is merely provided as an example, and other means for carrying out the described functions can be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 906, or any other suitable apparatus or means described in any one of the FIGS. 1, 2, and/or 3, and utilizing, for example, the processes and/or algorithms described below in connection with FIGS. 11 and/or 12.
  • FIG. 10 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity 1000 in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • scheduled entity 1000 can be a user equipment (UE) as illustrated in any one or more of FIGS. 1, 2, and/or 3.
  • UE user equipment
  • FIGS. 1, 2, and/or 3 an element, or any portion of an element, or any combination of elements can be implemented with a processing system 1014 that includes one or more processors 1004.
  • processing system 1014 can be substantially the same as the processing system 1014 illustrated in FIG. 10, including a bus interface 1008, a bus 1002, memory 1005, processor 1004, and a computer-readable medium 1006.
  • scheduled entity 1000 can include a user interface 1012 and a transceiver 1010 substantially similar to those described above in FIG. 10. That is, processor 1004, as utilized in a scheduled entity 1000, can be used to implement any one or more of the processes described below in connection with, and illustrated in, FIG. 11.
  • processor 1004 can include PUCCH A-CSI triggering circuitry 1040 configured for various functions, including, for example, configuring a PUCCH A-CSI trigger state list, enabling or disabling use of the PUCCH A-CSI trigger state list in response to an indication from a scheduling entity, causing an A-CSI report to be generated when the PUCCH A-CSI trigger state list is enabled in response to receiving a ZP CSI-RS trigger.
  • PUCCH A-CSI triggering circuitry 1040 can be configured to implement one or more of the functions described below in connection with FIG. 11, such as functions described in connection with one or more of 1102-1110, 1114, and/or 1116.
  • processor 1004 can include A-CSI reporting circuitry 1042 configured for various functions, including, for example, measuring channel quality using CSI-RSs on tones specified by a particular state in a PUCCH A-CSI trigger state list, generating an A-CSI report, and causing the A-CSI report to be transmitted using the PUCCH.
  • A-CSI reporting circuitry 1042 can be configured to implement one or more of the functions described below in connection with FIG. 11, such as functions described in connection with one or more of 1118-1122.
  • computer-readable storage medium 1006 can include PUCCH A-CSI triggering software 1052 configured for various functions, including, for example, configuring a PUCCH A-CSI trigger state list, enabling or disabling use of the PUCCH A-CSI trigger state list in response to an indication from a scheduling entity, causing an A-CSI report to be generated when the PUCCH A-CSI trigger state list is enabled in response to receiving a ZP CSI-RS trigger.
  • PUCCH A-CSI triggering software 1052 can be configured to implement one or more of the functions described below in connection with FIG. 11, such as functions described in connection with one or more of 1102-1110, 1114, and/or 1116.
  • computer-readable storage medium 1006 can include A-CSI reporting software 1054 configured for various functions, including, for example, measuring channel quality using CSI-RSs on tones specified by a particular state in a PUCCH A-CSI trigger state list, generating an A-CSI report, and causing the A-CSI report to be transmitted using the PUCCH.
  • A-CSI reporting software 1054 can be configured to implement one or more of the functions described below in connection with FIG. 11, such as functions described in connection with one or more of 1118-1122.
  • scheduled entity 1000 can include means for triggering generation of an A-CSI report to be transmitted using the PUCCH in response to a ZP CSI-RS trigger, and means for generating an A-CSI and transmitting the A-CSI report using the PUCCH.
  • the aforementioned means can be the processor (s) 1004 shown in FIG. 10 configured to perform the functions recited by the aforementioned means.
  • the aforementioned means can be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.
  • circuitry included in the processor 1004 is merely provided as an example, and other means for carrying out the described functions can be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 1006, or any other suitable apparatus or means described in any one of the FIGS. 1, 2, and/or 3, and utilizing, for example, the processes and/or algorithms described below in connection with FIGS. 11 and/or 12.
  • FIG. 11 is a flow chart illustrating an exemplary process 1100 for a scheduled entity to exclude a pattern of tones during rate matching and generate an A-CSI report on PUCCH responsive to a ZP CSI-RS trigger in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation. As described below, some or all illustrated features can be omitted in a particular implementation within the scope of the disclosed subject matter, and some illustrated features may not be required for implementation of all embodiments.
  • process 1100 can be carried out (e.g., executed) by user equipment described above in connection with FIG. 6, and/or UE 106 described above in connection with FIG. 1. In some examples, process 1100 can be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.
  • a user equipment e.g., UE 106, UE 604, UE 606
  • the UE can receive PUCCH A-CSI trigger state list configuration information from a scheduling entity (e.g., a base station such as base station 108 and/or base station 602) .
  • the UE can utilize the configuration information to generate and/or update a PUCCH A-CSI trigger state list.
  • the UE can receive the configuration information by sampling and buffering a received wireless signal on a particular channel, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.
  • the UE can receive the configuration information using any suitable communication interface, such as a transceiver (e.g., transceiver 1010) .
  • a UE can receive a message from a scheduling entity (e.g., base station 108, base station 602) with an indication to enable or inhibit use of the PUCCH A-CSI trigger state list when a ZP CSI-RS trigger is received.
  • the indication to enable or inhibit use of the PUCCH A-CSI trigger state list can be any suitable information in any suitable message.
  • the indication can be a 1 bit indicator that indicates whether the UE is to enable PUCCH A-CSI trigger state list based on whether the bit is a 1 or 0.
  • the UE can receive the indication to enable or inhibit use of the PUCCH A-CSI trigger state list in a radio resource control (RRS) configuration message.
  • RTS radio resource control
  • the UE can receive the indication to enable or inhibit use of the PUCCH A-CSI trigger state list as a medium access control (MAC) -control element (CE) command.
  • the UE can receive the indication to enable or inhibit use of the PUCCH A-CSI trigger state list by sampling and buffering a received wireless signal on a particular channel, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.
  • the UE can receive the configuration information using any suitable communication interface, such as a transceiver (e.g., transceiver 1010) .
  • the UE may not receive a message at 1104, and 1104 can be omitted.
  • use of the PUCCH A-CSI trigger state list can be enabled (e.g., by default) or inhibited (e.g., by default) unless a contrary indication is received.
  • process 1100 can move to 1108. Otherwise, if the UE did not receive a message enabling or inhibiting use of the PUCCH A-CSI trigger state list configured at 1102 ( "NO” at 1106) , process 1100 can move to 1110.
  • a UE can set an indicator to enable or inhibit use of the PUCCH A-CSI trigger state list configured at 1102 in response to receiving a ZP CSI-RS trigger using any suitable technique or combination of techniques. For example, as described above in connection with FIG. 7, the UE can set a flag associated with the PUCCH A-CSI trigger state list configured at 1102 to 1 to indicate that it is enabled or to 0 to indicate that its use is inhibited (or vice versa) . As another example, as described above in connection with FIG.
  • the UE can set a pointer used to point at the PUCCH A-CSI trigger state list configured at 1102 to enable use of the list, or can set the pointer to point at another list (e.g., a null list) to inhibit use of the PUCCH A-CSI trigger state list configured at 1102.
  • a pointer used to point at the PUCCH A-CSI trigger state list configured at 1102 to enable use of the list, or can set the pointer to point at another list (e.g., a null list) to inhibit use of the PUCCH A-CSI trigger state list configured at 1102.
  • a UE can receive a ZP CSI-RS trigger from the scheduling entity with a value corresponding to a codepoint i.
  • the UE can receive a ZP CSI-RS trigger as a ZP CSI-RS trigger field in any suitable message.
  • the UE can receive a ZP CSI-RS trigger field transmitted in DCI having any suitable DCI format, such as DCI format 1_0, 1_1, or 1_2.
  • the UE can receive the message that includes the ZP CSI-RS trigger by sampling and buffering a received wireless signal on a particular channel, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.
  • the UE can receive the message including the ZP CSI-RS trigger using any suitable communication interface, such as a transceiver (e.g., transceiver 1010) .
  • a UE can rate match around the tones specified by the ZP CSI-RS trigger.
  • the UE can identify the tones specified by ZP CSI-RS trigger using any suitable technique or combination of techniques. For example, as described above in connection with FIG. 7, the UE can maintain a list of ZP CSI-RS resource settings associated with various codepoint values, and can use the ZP CSI-RS resource settings associated with codepoint i to determine the tones that are to be set as ZP CSI-RSs for the purposes of rate matching.
  • the UE can use any suitable technique or combination of techniques to perform rate matching. For example, the UE can estimate available resources available on PDSCH when the tones specified as ZP CSI-RS are excluded, and can rate match to use the available resources. As another example, the UE can use one or more techniques described in 3GPP TS 38.214, clause 5.1.4.2 to perform rate matching, in which resource elements (REs) specified as ZP CSI-RSs are declared not available.
  • REs resource elements
  • a UE can determine whether the PUCCH A-CSI trigger state list configured at 1102 is enabled.
  • the UE can use any suitable technique or combination of techniques to determine whether the PUCCH A-CSI trigger state list configured at 1102 is enabled. For example, as described above in connection with FIG. 7, the UE can check the value of a flag associated with the PUCCH A-CSI trigger state list configured at 1102. In a particular example, if the flag is set to 1, the UE can determine that use of the PUCCH A-CSI trigger state list configured at 1102 is enabled, and otherwise (e.g., if the flag is set to 0) the UE can determine that use of the PUCCH A-CSI trigger state list configured at 1102 is inhibited.
  • the UE can determine that use of the PUCCH A-CSI trigger state list configured at 1102 is enabled if a pointer used to indicate a PUCCH A-CSI trigger state list to utilize points to the PUCCH A-CSI trigger state list configured at 1102. Otherwise, the UE can determine that use of the PUCCH A-CSI trigger state list configured at 1102 is inhibited if the pointer does not point to the PUCCH A-CSI trigger state list configured at 1102 (e.g., if the pointer points to a null list) .
  • process 1100 can end. Otherwise, if the UE determines that use of the PUCCH A-CSI trigger state list configured at 1102 is enabled ( "YES” at 1116) , process 1100 can move to 1118.
  • a UE can use the CSI-RS tones specified by state i in the PUCCH A-CSI trigger state list to measure channel quality across one or more layers and/or resource blocks.
  • the UE can identify the tones specified by state i based on CSI-RS resource settings associated with one or more reports associated with state i.
  • CSI-RS resource settings can be omitted from the set the of one or more report configurations, and the UE can identify the tones associated with state i using the list of ZP CSI-RS resource settings associated with various codepoint values.
  • the UE can use any suitable technique or combination of techniques to measure channel quality, such as techniques described above in connection with FIG. 3, techniques described in 3GPP TS 38.214, section 5.2, and/or any other suitable technique.
  • a UE can generate one or more CSI reports specified by one or more report configurations associated with state i.
  • the UE can generate the one or more CSI reports using any suitable technique or combination of techniques, and can include any suitable information specified by the one or more report configurations associated with state i.
  • the UE can use techniques and/or include information described above in connection with FIG. 3.
  • a UE can transmit one or more CSI reports using PUCCH.
  • the UE can use any suitable technique or combination of technique to transmit the CSI report (s) and/or determine PUCCH resources to use to transmit the CSI report (s) .
  • the UE can transmit the CSI report (s) on PUCCH via any suitable communication network (e.g., via a RAN, such as RAN 104 or RAN 200, using one or more DL slots and/or one or more UL slots, etc. ) .
  • the UE can transmit the CSI report (s) using any suitable communication interface, such as a transceiver (e.g., transceiver 1010) .
  • the UE can use information received in a DL grant (e.g., the DL grant in which ZP CSI-RS trigger was received) to identify a PUCCH resource to use to transmit the CSI report (s) .
  • process 1100 can end after transmitting the CSI report at 1122.
  • FIG. 12 is a flow chart illustrating an exemplary process 1200 for a scheduling entity to request that a first UE generate an A-CSI report for a pattern of tones on PUSCH, and trigger a second UE to exclude the pattern of tones during rate matching and generate an A-CSI report for the pattern of tones on PUCCH responsive to a ZP CSI-RS trigger in accordance with some aspects of the disclosed subject matter, and is described as an illustrative example without limitation.
  • a scheduling entity can transmit configuration information for a PUCCH A-CSI trigger state list to any suitable device.
  • the scheduling entity can transmit PUCCH A-CSI trigger state list configuration information to a user equipment (e.g., UE 106, UE 606) .
  • the configuration information can cause the UE to generate and/or update a PUCCH A-CSI trigger state list.
  • the scheduling entity can transmit the configuration information via any suitable communication network (e.g., via a RAN, such as RAN 104 or RAN 200, using one or more DL slots and/or one or more UL slots, etc. ) .
  • the scheduling entity can transmit the configuration information using any suitable communication interface, such as a transceiver (e.g., transceiver 910) .
  • a scheduling entity can transmit a message to a UE B (e.g., UE 106, UE 606) including an indication to enable or inhibit use of the PUCCH A-CSI trigger state list when a ZP CSI-RS trigger is received.
  • the indication to enable or inhibit use of the PUCCH A-CSI trigger state list can be any suitable information in any suitable message.
  • the indication can be a 1 bit indicator that indicates whether the UE is to enable PUCCH A-CSI trigger state list based on whether the bit is a 1 or 0.
  • the scheduling entity can transmit the indication to enable or inhibit use of the PUCCH A-CSI trigger state list in a radio resource control (RRS) configuration message.
  • RTS radio resource control
  • the scheduling entity can transmit the indication to enable or inhibit use of the PUCCH A-CSI trigger state list as a medium access control (MAC) -control element (CE) command.
  • the scheduling entity can transmit the message including the indication via any suitable communication network (e.g., via a RAN, such as RAN 104 or RAN 200, using one or more DL slots and/or one or more UL slots, etc. ) .
  • the scheduling entity can transmit the message including the indication using any suitable communication interface, such as a transceiver (e.g., transceiver 910) .
  • the scheduling entity may not transmit a message at 1204, and 1204 can be omitted.
  • use of the PUCCH A-CSI trigger state list can be enabled (e.g., by default) or inhibited (e.g., by default) on the UE unless a contrary indication is transmitted.
  • a scheduling entity can transmit an A-CSI request for a particular user equipment A (e.g., UE 604) that specifies a particular codepoint (e.g., codepoint j, where 0 ⁇ j ⁇ M) .
  • the scheduling entity can transmit the A-CSI request using any suitable technique or combination of techniques. For example, as described above in connection with FIG. 5, the scheduling entity can transmit the A-CSI request using use a CSI request field in DCI (e.g., DCI format 0_1) transmitted to schedule transmission by UE A on PUSCH.
  • DCI e.g., DCI format 0_1
  • the scheduling entity can transmit the A-CSI request for UE A via any suitable communication network (e.g., via a RAN, such as RAN 104 or RAN 200, using one or more DL slots and/or one or more UL slots, etc. ) .
  • the scheduling entity can transmit the A-CSI request using any suitable communication interface, such as a transceiver (e.g., transceiver 910) .
  • a scheduling entity can transmit a ZP CSI-RS trigger for UE B that specifies a codepoint i.
  • the scheduling entity can transmit the ZP CSI-RS trigger using any suitable technique or combination of techniques. For example, as described above in connection with FIG. 7, the scheduling entity can transmit the ZP CSI-RS trigger using a ZP CSI-RS trigger field in DCI (e.g., DCI format 1_0, 1_1, or 1_2) transmitted in a DL grant.
  • DCI e.g., DCI format 1_0, 1_1, or 1_2
  • the scheduling entity can transmit the ZP CSI-RS trigger for UE B via any suitable communication network (e.g., via a RAN, such as RAN 104 or RAN 200, using one or more DL slots and/or one or more UL slots, etc. ) .
  • the scheduling entity can transmit the ZP CSI-RS trigger using any suitable communication interface, such as a transceiver (e.g., transceiver 910) .
  • the scheduling entity can select codepoint i based on the configuration of the PUCCH A-CSI trigger state list configured at 1202 and/or based on ZP CSI-RS trigger states associated with UE B. For example, as described above in connection with FIG. 6, the scheduled entity can select a codepoint value that is associated with ZP CSI-RS resource settings that specify the same tones specified for UE A by the codepoint included in the CSI request transmitted at 1206. Additionally, the scheduled entity can select a codepoint value that is associated with CSI-RS resource settings (e.g., via the PUCCH A-CSI trigger state list configured at 1202) that specify the same tones (or a subset of tones) specified for UE A by the codepoint included in the CSI request transmitted at 1206.
  • a scheduling entity can match around the tones specified by the ZP CSI-RS trigger for data sent to UE B on the physical downlink shared channel (PDSCH) resource designated by the DL grant.
  • the scheduling entity can use any suitable technique or combination of techniques to perform rate matching.
  • the scheduling entity can estimate available resources available on PDSCH when the tones specified as ZP CSI-RS are excluded, and can rate match to use the available resources.
  • the scheduling entity can use one or more techniques described in 3GPP TS 38.214, clause 5.1.4.2 to perform rate matching.
  • a scheduling entity can transmit NZP CSI-RSs for UE A and UE B using the same tones (or at least a subset of the same tones) concurrently.
  • the scheduling entity can multiplex the CSI-RSs for the different UEs using any suitable technique or combination of techniques.
  • the scheduling entity can use different codes to transmit the NZP CSI-RSs for the different UEs using the same tones.
  • a scheduling entity can receive an A-CSI report from UE B with one or more reports specified by state i in the PUCCH A-CSI trigger state list configured at 1202.
  • a CSI report can include, for example, channel quality information (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and/or any other suitable information.
  • the scheduling entity can receive the CSI report (s) by sampling and buffering a received wireless signal on a PUCCH, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.
  • the scheduling entity can receive the configuration information using any suitable communication interface, such as a transceiver (e.g., transceiver 910) .
  • a scheduling entity can receive an A-CSI report from UE A with one or more reports specified by state j in the PUSCH A-CSI trigger state list associated with UE A (e.g., as described above in connection with FIG. 5) .
  • a CSI report can include, for example, CQI, a PMI, an RI, and/or any other suitable information.
  • the scheduling entity can receive the CSI report (s) by sampling and buffering a received wireless signal on a PUSCH, and applying suitable processing to the buffered signal such as energy detection, demodulation, decoding, etc.
  • the scheduling entity can receive the configuration information using any suitable communication interface, such as a transceiver (e.g., transceiver 910) .
  • Example 1 A method, apparatus, and non-transitory computer-readable medium for wireless communication, including receiving, from a scheduling entity, a zero power (ZP) channel state information (CSI) -reference signal (RS) trigger specifying a codepoint i; identifying a plurality of tones corresponding to codepoint i using a list of ZP CSI-RS trigger states; performing rate matching around the plurality of tones as ZP CSI-RS tones; generating an aperiodic CSI (A-CSI) report based on channel quality measured using CSI-RSs transmitted on at least a subset of the plurality of tones; and transmitting the A-CSI report on a physical uplink control channel (PUCCH) .
  • ZP zero power
  • CSI channel state information
  • RS reference signal
  • Example 2 A method, apparatus, and non-transitory computer-readable medium of Example 1, further including receiving, from the scheduling entity, configuration information associated with a PUCCH A-CSI trigger state list, wherein the configuration information specifies a plurality of states that are each associated with one or more report configurations, each of the plurality of states associated with a codepoint; and configuring the PUCCH A-CSI trigger state list based on the configuration information.
  • Example 3 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 2, further including identifying a second plurality of tones corresponding to codepoint i using the PUCCH A-CSI trigger state list, wherein the second plurality of tones is at least a subset of the plurality of tones; and measuring channel quality using the CSI-RSs transmitted on the second plurality of tones.
  • Example 4 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 3, further including receiving, from the scheduling entity, a message comprising an indication that the PUCCH A-CSI trigger state list is to be enabled; in response to receiving the message, setting an indicator to a value that enables use of the PUCCH A-CSI trigger state list; and generating the A-CSI report based on the value of the indicator.
  • Example 5 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 4, wherein the indication that the PUCCH A-CSI trigger state list is to be enabled is a 1 bit indicator.
  • Example 6 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 5, further including receiving, from the scheduling entity, a message comprising an indication that use of the PUCCH A-CSI trigger state list is to be inhibited; in response to receiving the message, setting an indicator to a value that inhibits use of the PUCCH A-CSI trigger state list; receiving, from the scheduling entity, a second ZP CSI-RS trigger; identifying a third plurality of tones based on a value of a codepoint associated with the second ZP CSI-RS trigger; performing rate matching around the third plurality of tones as ZP CSI-RS tones; and inhibiting generation of an aperiodic CSI (A-CSI) report based on the third plurality of tones based on the value of the indicator.
  • A-CSI aperiodic CSI
  • Example 7 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 6, wherein setting the indicator to the value that inhibits use of the PUCCH A-CSI trigger state list comprises setting a pointer to point at a null list.
  • Example 8 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 7, wherein the ZP CSI-RS trigger comprises a ZP CSI-RS field included in downlink control information (DCI) associated with a downlink grant.
  • DCI downlink control information
  • Example 9 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 8, further including receiving a message comprising the ZP CSI-RS trigger and a value indicative of a PUCCH resource to be used to transmit the A-CSI report; and transmitting the A-CSI report using the PUCCH resource.
  • Example 10 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 9, wherein the value indicative of the PUCCH resource to be used to transmit the A-CSI report comprises a K1 value, and wherein transmitting the A-CSI report comprises transmitting the A-CSI report with HARQ-ACK in a slot designated by the K1 value.
  • Example 11 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 10, wherein the message comprises a K1 value indicative of a slot to be used to transmit HARQ-ACK, and the value indicative of the PUCCH resource to be used to transmit the A-CSI report comprises at least 2 bits, and wherein transmitting the A-CSI report comprises transmitting the A-CSI report in a slot designated by the value indicative of the PUCCH resource to be used to transmit the A-CSI report prior to the slot designated by the K1 value.
  • Example 12 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 11, further including transmitting, to a user equipment (UE) , a zero power (ZP) channel state information (CSI) -reference signal (RS) trigger specifying a codepoint i, wherein the UE has been configured to associate a plurality of tones with codepoint i; transmitting a plurality of CSI-RSs for the UE using the plurality of tones; performing rate matching around the plurality of tones designated as ZP CSI-RS tones for data transmitted for the UE using a physical downlink shared channel (PDSCH) resource; and receiving, from the UE on a physical uplink control channel (PUCCH) resource, an aperiodic CSI (A-CSI) report indicative of channel quality measured using the plurality of CSI-RSs.
  • ZP zero power
  • CSI channel state information
  • RS reference signal
  • Example 13 A method, apparatus, and non-transitory computer-readable medium for wireless communication, including transmitting, to a user equipment (UE) , a zero power (ZP) channel state information (CSI) -reference signal (RS) trigger specifying a codepoint i, wherein the UE has been configured to associate a plurality of tones with codepoint i; transmitting a plurality of CSI-RSs for the UE using the plurality of tones; performing rate matching around the plurality of tones designated as ZP CSI-RS tones for data transmitted for the UE using a physical downlink shared channel (PDSCH) resource; and receiving, from the UE on a physical uplink control channel (PUCCH) resource, an aperiodic CSI (A-CSI) report indicative of channel quality measured using the plurality of CSI-RSs.
  • ZP zero power
  • CSI channel state information
  • RS reference signal
  • Example 14 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 13, further including transmitting, to a second UE, a CSI request specifying a codepoint j, wherein the second UE has been configured with a physical uplink shared channel (PUSCH) trigger state list that associates at least the plurality of tones with codepoint j; and transmitting a second plurality of CSI-RSs for the second UE using at least the plurality of tones concurrently with transmission of the plurality of CSI-RSs for the UE using the plurality of tones; receiving, from the second UE on a PUSCH resource subsequent to receiving the A-CSI report from the UE, a second A-CSI report indicative of channel quality measured using CSI-RSs transmitted on at least the plurality of tones.
  • PUSCH physical uplink shared channel
  • Example 15 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 14, further including transmitting, to the UE, configuration information associated with a PUCCH A-CSI trigger state list, wherein the configuration information specifies a plurality of states that are each associated with one or more report configurations, each of the plurality of states associated with a codepoint.
  • Example 16 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 15, further including transmitting, to the UE, a message comprising an indication that the PUCCH A-CSI trigger state list is to be enabled; and receiving the A-CSI report subsequent to transmitting the message.
  • Example 17 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 16, wherein the indication that the PUCCH A-CSI trigger state list is to be enabled is a 1 bit indicator.
  • Example 18 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 17, further including transmitting, to the UE, a message comprising an indication that use of the PUCCH A-CSI trigger state list is to be inhibited; transmitting, to the UE, a second ZP CSI-RS trigger comprising a codepoint associated with a third plurality of tones in a list of ZP CSI-RS trigger states maintained by the UE; performing rate matching around the third plurality of tones as ZP CSI-RS tones; and receiving, from the UE, HARQ-ACK feedback on the PUCCH without receiving a A-CSI report from the UE based on the third plurality of tones based on the value of the indicator.
  • Example 19 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 18, wherein the ZP CSI-RS trigger comprises a ZP CSI-RS field included in downlink control information (DCI) associated with a downlink grant.
  • DCI downlink control information
  • Example 20 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 19, further including transmitting, to the UE, a message comprising the ZP CSI-RS trigger and a value indicative of a PUCCH resource to be used to transmit the A-CSI report; and receiving the A-CSI report using the PUCCH resource.
  • Example 21 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 20, wherein the value indicative of the PUCCH resource to be used to transmit the A-CSI report comprises a K1 value, and wherein the A-CSI report is received with HARQ-ACK in a slot designated by the K1 value.
  • Example 22 A method, apparatus, and non-transitory computer-readable medium of any of Examples 1 to 21, wherein the message comprises a K1 value indicative of a slot to be used to transmit HARQ-ACK, and the value indicative of the PUCCH resource to be used to transmit the A-CSI report comprises at least 2 bits, and wherein the A-CSI report is received in a slot designated by the value indicative of the PUCCH resource to be used to transmit the A-CSI report prior to the slot designated by the K1 value.
  • various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE) , the Evolved Packet System (EPS) , the Universal Mobile Telecommunication System (UMTS) , and/or the Global System for Mobile (GSM) .
  • LTE Long-Term Evolution
  • EPS Evolved Packet System
  • UMTS Universal Mobile Telecommunication System
  • GSM Global System for Mobile
  • Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2) , such as CDMA2000 and/or Evolution-Data Optimized (EV-DO) .
  • 3GPP2 3rd Generation Partnership Project 2
  • EV-DO Evolution-Data Optimized
  • Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Ultra-Wideband (UWB) , Bluetooth, and/or other suitable systems.
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 8
  • the word “exemplary” is used to mean “serving as an example, instance, or illustration. ” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.
  • the term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object.
  • circuit and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure.
  • FIGS. 1–12 One or more of the components, steps, features and/or functions illustrated in FIGS. 1–12 can be rearranged and/or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein.
  • the apparatus, devices, and/or components illustrated in FIGS. 1–12 can be configured to perform one or more of the methods, features, or steps described herein.
  • the novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.
  • “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des aspects de la présente invention concernent un UE recevant, à partir d'une entité de planification, un déclencheur de signal de référence (RS) d'informations d'état de canal (CSI) de puissance nulle (ZP) spécifiant un point de code i; identifiant une pluralité de tonalités correspondant au point de code i à l'aide d'une liste d'états de déclenchement de CSI-RS ZP; effectuant une adaptation de débit sur la pluralité de tonalités sous la forme de tonalités de CSI-RS ZP; générant un CSI apériodiques (A-CSI) sur la base d'une qualité de canal mesurée à l'aide de CSI-RS transmis sur au moins un sous-ensemble de la pluralité de tonalités; et transmettant le rapport A-CSI sur un canal physique de commande de liaison montante (PUCCH). La présente invention concerne également d'autres aspects, modes de réalisation et caractéristiques.
PCT/CN2020/107760 2020-08-07 2020-08-07 Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro WO2022027571A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107760 WO2022027571A1 (fr) 2020-08-07 2020-08-07 Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107760 WO2022027571A1 (fr) 2020-08-07 2020-08-07 Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro

Publications (1)

Publication Number Publication Date
WO2022027571A1 true WO2022027571A1 (fr) 2022-02-10

Family

ID=80120059

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/107760 WO2022027571A1 (fr) 2020-08-07 2020-08-07 Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro

Country Status (1)

Country Link
WO (1) WO2022027571A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019080107A1 (fr) * 2017-10-27 2019-05-02 Oppo广东移动通信有限公司 Procédé, dispositif terminal et dispositif de réseau permettant de transmettre un canal de commande de liaison montante physique (pucch)
US10594380B1 (en) * 2018-09-28 2020-03-17 At&T Intellectual Property I, L.P. Channel state information determination using demodulation reference signals in advanced networks
US20200112419A1 (en) * 2018-10-05 2020-04-09 Lenovo (Singapore) Pte. Ltd. Method and apparatus for generating a csi report
US20200178240A1 (en) * 2017-06-16 2020-06-04 Yu Zhang Reporting aperiodic csi via pucch

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200178240A1 (en) * 2017-06-16 2020-06-04 Yu Zhang Reporting aperiodic csi via pucch
WO2019080107A1 (fr) * 2017-10-27 2019-05-02 Oppo广东移动通信有限公司 Procédé, dispositif terminal et dispositif de réseau permettant de transmettre un canal de commande de liaison montante physique (pucch)
US10594380B1 (en) * 2018-09-28 2020-03-17 At&T Intellectual Property I, L.P. Channel state information determination using demodulation reference signals in advanced networks
US20200112419A1 (en) * 2018-10-05 2020-04-09 Lenovo (Singapore) Pte. Ltd. Method and apparatus for generating a csi report

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.214, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. V16.2.0, 20 July 2020 (2020-07-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 163, XP051925549 *
QUALCOMM INCORPORATED: "On Interference Measurement Resource", 3GPP DRAFT; R1-1702613, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051209766 *

Similar Documents

Publication Publication Date Title
US11228992B2 (en) Uplink transmissions without timing synchronization in wireless communication
CN111373687B (zh) 在无线通信中将上行链路控制信息映射到上行链路数据信道
US11323227B2 (en) Multiplexing of physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) in uplink short burst transmission
US10700760B1 (en) Minimizing block error rate (BLER) associated with a beam switch
US11405128B2 (en) Minimizing block error rate (BLER) associated with a beam switch
US11177865B2 (en) Precoder resource group allocation methods for MIMO communication
US10873869B2 (en) Cell-specific sounding and measurement configuration
WO2021227057A1 (fr) Configuration de transmission de liaison montante prenant en charge une transmission sur de multiples panneaux d'antenne
US11575424B2 (en) UE recommended CSI settings
US11159219B2 (en) Frequency domain segmentation for performance enhancement of channel state feedback
US11387875B2 (en) Beam selection for enhanced page performance
US20220007224A1 (en) Channel state information (csi) signaling for multiple report metrics
WO2021189246A1 (fr) Configuration de ressource srs basée sur un élément de commande d'accès au support (mac)
WO2021249531A1 (fr) Rapport d'informations d'état de canal basé sur un signal de référence et une hypothèse en duplex intégral
US20230179380A1 (en) Interference rank indication by a victim node in full duplex
WO2022198360A1 (fr) Commutation dynamique de panneau dans un cadre unifié d'informations de configuration de transmission
US10998956B1 (en) Optimized receive beam selection
WO2021097589A1 (fr) Optimisation de rapport de rétroaction d'état de canal (csf)
EP4005108A1 (fr) Réduction à un minimum du taux d'erreur de bloc (bler) associé à un commutateur de faisceau
WO2022027571A1 (fr) Déclenchement de rapports d'informations d'état de canal apériodiques sur un canal physique de commande de liaison montante à l'aide d'un déclencheur de signal de ressource d'informations d'état de canal de puissance zéro

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20948089

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20948089

Country of ref document: EP

Kind code of ref document: A1