Conflict resolution for channel state information reports on the physical uplink control channel

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may identify multiple channel state information (CSI) reports scheduled to be sent in a time slot on a corresponding physical uplink control channel (PUCCH) resource. For example, multiple CSI reports may include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type. The UE may select one or more CSI reports to be sent in a time slot from multiple CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type. Thus, the UE may send one or more PUCCH transmissions including one or more selected CSI reports in a time slot. Many other aspects are also provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 911,675, filed on October 7, 2019, entitled “COLLISION RESOLUTION FOR CHANNEL STATE INFORMATION REPORTING ON A PHYSICAL UPLINK CONTROL CHANNEL,” and U.S. Non-Provisional Patent Application No. 16 / 948,896, filed on October 5, 2020, entitled “COLLISION RESOLUTION FOR CHANNEL STATE INFORMATION REPORTING ON A PHYSICAL UPLINK CONTROL CHANNEL,” which are expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for contention resolution for reporting channel state information (CSI) on a physical uplink control channel (PUCCH). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that are capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a series of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs) that may support communications for multiple user equipment (UEs). User equipment (UEs) may communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0006] The multiple access technologies described above have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at municipal, national, regional and even global levels. New Radio (NR), also known as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink (DL), CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation for better integration with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies and the telecommunication standards that adopt them remain useful. Summary of the invention

[0007] In some aspects, a wireless communication method performed by a user equipment (UE) may include: identifying multiple channel state information (CSI) reports scheduled to be sent in a time slot on a corresponding physical uplink control channel (PUCCH) resource, wherein the multiple CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; selecting one or more CSI reports to be sent in the time slot from the multiple CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and sending one or more PUCCH transmissions in the time slot including the one or more selected CSI reports.

[0008] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: identify a plurality of CSI reports scheduled to be sent in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; select one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and send one or more PUCCH transmissions including the one or more selected CSI reports in the time slot.

[0009] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to: identify a plurality of CSI reports scheduled to be sent in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; select one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and send one or more PUCCH transmissions including the one or more selected CSI reports in the time slot.

[0010] In some aspects, an apparatus for wireless communication may include components for identifying multiple CSI reports scheduled to be sent in a time slot on a corresponding PUCCH resource, wherein the multiple CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; components for selecting one or more CSI reports to be sent in the time slot from the multiple CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and components for sending one or more PUCCH transmissions in the time slot including the one or more selected CSI reports.

[0011] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as described herein with reference to the accompanying drawings and descriptions.

[0012] In some aspects, a wireless communication method performed by a base station may include: identifying multiple CSI reports that a UE is scheduled to send in a time slot on a corresponding PUCCH resource, wherein the multiple CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; determining one or more CSI reports to be sent in the time slot from the multiple CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and receiving one or more PUCCH transmissions including the one or more CSI reports in the time slot.

[0013] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: identify a plurality of CSI reports that the UE is scheduled to send in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; determine one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and receive one or more PUCCH transmissions including the one or more CSI reports in the time slot.

[0014] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to: identify multiple CSI reports that the UE is scheduled to send in a time slot on a corresponding PUCCH resource, wherein the multiple CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; determine one or more CSI reports to be sent in the time slot from the multiple CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and receive one or more PUCCH transmissions including the one or more CSI reports in the time slot.

[0015] In some aspects, an apparatus for wireless communication may include components for identifying multiple CSI reports that a UE is scheduled to send in a time slot on a corresponding PUCCH resource, wherein the multiple CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; components for determining one or more CSI reports to be sent in the time slot from the multiple CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type; and components for receiving one or more PUCCH transmissions including the one or more CSI reports in the time slot.

[0016] In order to better understand the detailed description below, the foregoing content has been quite extensively summarized the features and technical advantages of examples according to the present disclosure. Other features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures to implement the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the features of the concepts disclosed herein, both their organization and method of operation, and the associated advantages will be better understood from the following description. Each of the drawings is provided for the purpose of illustration and description and not as a definition of the claim limitations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 is a diagram illustrating an example of a wireless network in accordance with various aspects of the present disclosure.

[0019] Figure 2 is a diagram illustrating an example of a base station communicating with a UE in a wireless network according to various aspects of the present disclosure.

[0020] Figure 3A is a diagram illustrating an example frame structure in a wireless network in accordance with various aspects of the present disclosure.

[0021] Figure 3B is a diagram illustrating an example synchronous communication hierarchy in a wireless network in accordance with various aspects of the present disclosure.

[0022] Figure 4 is a diagram illustrating an example slot format with a normal cyclic prefix in accordance with various aspects of the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a downlink center slot in accordance with various aspects of the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of an uplink center time slot according to various aspects of the present disclosure.

[0025] Figure 7A-7B is a diagram illustrating an example implementation of contention resolution for reporting channel state information (CSI) on a physical uplink control channel (PUCCH) in accordance with various aspects of the present disclosure.

[0026] Figure 8 Detailed description is given of example processes performed, for example, by a UE, according to various aspects of the present disclosure.

[0027] Fig. 9 Detailed description is given of example processes performed, for example, by a base station according to various aspects of the present disclosure. DETAILED DESCRIPTION

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

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

[0030] It should be noted that while aspects of the present disclosure may be described using terminology typically associated with 5G or NR radio access technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or RATs after 5G (e.g., 6G).

[0031] Figure 1is a diagram showing an example of a wireless network 100 according to various aspects of the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network, an LTE network, etc. The wireless network 100 may include a plurality of base stations 110 (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or BS subsystem serving this coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs through service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs through service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G-NB", and "cell" may be used interchangeably herein.

[0033] In some aspects, the cells are not necessarily stationary, and the geographic area of ​​the cells can move according to the location of the mobile BS. In some aspects, the BSs are interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, and / or similar networks using any suitable transport networks.

[0034] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the illustrated example, a relay BS 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.

[0035] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0036] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for the BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, for example, directly or indirectly via a wireless or wired backhaul.

[0037] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smart phones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biometric sensors / devices, wearable devices (smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable device configured to communicate via wireless or wired media.

[0038] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide a connection to a network (e.g., a wide area network such as the Internet or a cellular network) or provide a connection to the network via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (e.g., processor components, memory components, etc.). In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, electrically coupled, etc.

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

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

[0041] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, frequency bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using an operating frequency band having a first frequency range (FR1) and / or can communicate using an operating frequency band having a second frequency range (FR2), the first frequency range (FR1) can span from 410 MHz to 7.125 GHz, and the second frequency range (FR2) can span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz" band. Similarly, FR2 is often referred to as a "millimeter wave" band, but it is different from the ultra-high frequency (EHF) band (30 GHz–300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Thus, unless otherwise expressly stated, it should be understood that the term "sub-6 GHz," etc., if used herein, can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise expressly stated, it should be understood that the term "millimeter wave," etc., if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0042] As mentioned above, Figure 1 Provided as examples. Other examples may differ from the Figure 1 An example of description.

[0043] Figure 2 is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network according to various aspects of the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0044] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and / or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and / or the like), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and may provide T output symbol streams to T modulators (MOD) 232a through 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM and / or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0045] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM and / or the like) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included in the housing 284.

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

[0047] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0048] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 for scheduling the UE 120 for downlink and / or uplink communications. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of the antenna 234, the modulator and / or demodulator 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (eg, controller / processor 240 ) and memory 242 to perform aspects of any of the methods described herein.

[0049] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the base station 110 may perform one or more techniques associated with conflict resolution for reporting channel state information (CSI) of a physical uplink control channel (PUCCH), as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 8 The process of 800 Fig. 9 10 and / or other processes described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, interpretation, etc.) by one or more processors of base station 110 and / or UE 120, may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The operations of process 900 and / or other processes described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, interpreting instructions, etc.

[0050] In some aspects, UE 120 may include means for identifying a plurality of CSI reports scheduled to be sent in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type, means for selecting one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type, means for sending one or more PUCCH transmissions including the one or more selected CSI reports in the time slot, and the like. In some aspects, such means may include combining Figure 2 One or more components of the UE 120 are depicted, such as the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, and the like.

[0051] In some aspects, base station 110 may include means for identifying that a UE is scheduled to transmit a plurality of CSI reports in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type, means for determining one or more CSI reports to be transmitted in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type, means for receiving one or more PUCCH transmissions including the one or more CSI reports, etc. in the time slot, etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of the base station 110 are depicted, such as antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.

[0052] As mentioned above, Figure 2 Provided as examples. Other examples may differ from the Figure 2 An example of description.

[0053] Figure 3AAn example frame structure 300 for frequency division duplex (FDD) in a telecommunication system (e.g., NR) is shown. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames (sometimes referred to as frames). Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be divided into a set of Z (Z) ≥ 1) subframes (e.g., indexed 0 to Z-1). Each subframe may have a predetermined duration (e.g., 1 ms) and may include a set of time slots (e.g., Figure 3A Each subframe 2 is shown in m time slots, where m is the parameter set for transmission, e.g., 0, 1, 2, 3, 4, etc.). Each time slot may include a set of L symbol periods. For example, each time slot may include fourteen symbol periods (e.g., Figure 3A In the case where a subframe includes two time slots (e.g., when m=1), the subframe may include 2L symbol periods, where the 2L symbol periods in each subframe may be assigned indices from 0 to 2L–1. In some aspects, the scheduling unit for FDD may be frame-based, subframe-based, time slot-based, symbol-based, etc.

[0054] Although some techniques are described herein in conjunction with frames, subframes, time slots, etc., these techniques may also be applied to other types of wireless communication structures, which may be referred to using terms other than "frames," "subframes," "time slots," etc. in 5G NR. In some aspects, a "wireless communication structure" may refer to a periodic, time-limited communication unit defined by a wireless communication standard and / or protocol. Additionally or alternatively, a wireless communication structure may be used in conjunction with a wireless communication standard and / or protocol. Figure 3A The wireless communication structure shown in FIG.

[0055] In some telecommunications (e.g., NR), a base station may send synchronization signals. For example, a base station may send a primary synchronization signal (PSS), a secondary synchronization signal (SSS), etc. on the downlink for each cell supported by the base station. The PSS and SSS may be used by the UE for cell search and acquisition. For example, the UE may use the PSS to determine symbol timing, and the UE may use the SSS to determine the physical cell identifier and frame timing associated with the base station. The base station may also send a physical broadcast channel (PBCH). The PBCH may carry some system information, such as system information that supports initial access of the UE.

[0056] In some aspects, the base station may transmit the PSS, SSS, and / or PBCH according to a synchronization communication hierarchy (e.g., a synchronization signal (SS) hierarchy) including multiple synchronization communications (e.g., SS blocks), as described below in conjunction with Figure 3B described.

[0057] Figure 3B is a diagram showing an example SS hierarchy, which is an example of a synchronous communication hierarchy. Figure 3B As shown, the SS hierarchy may include an SS burst set, which may include a plurality of SS bursts (identified as SS burst 0 to SS burst B-1, where B is the maximum number of repetitions of the SS burst that may be sent by the base station). As further shown, each SS burst may include one or more SS blocks (identified as SS block 0 to SS block (b max_SS -1), where b max_SS -1 is the maximum number of SS blocks that can be carried by an SS burst). In some aspects, different SS blocks can be beamformed in different ways. Figure 3B As shown, the SS burst set may be sent by the wireless node periodically, for example, every X milliseconds. In some aspects, the SS burst set may have a fixed or dynamic length, such as Figure 3B The Y milliseconds are shown in Figure 2.

[0058] Figure 3B The SS burst set shown is an example of a synchronous communication set, and other synchronous communication sets can be used in conjunction with the techniques described herein. Figure 3B The SS blocks shown in are examples of synchronous communications, and other synchronous communications may be used in conjunction with the techniques described herein.

[0059] In some aspects, an SS block includes resources that carry a PSS, SSS, PBCH, and / or other synchronization signals (e.g., a third synchronization signal (TSS)) and / or a synchronization channel. In some aspects, multiple SS blocks are included in an SS burst, and the PSS, SSS, and / or PBCH may be the same across each SS block of an SS burst. In some aspects, a single SS block may be included in an SS burst. In some aspects, an SS block may be at least four symbol periods in length, with each symbol carrying one or more PSS (e.g., occupying one symbol), SSS (e.g., occupying one symbol), and / or PBCH (e.g., occupying two symbols).

[0060] In some aspects, the symbols of the SS blocks are consecutive, such as Figure 3B As shown. In some aspects, the symbols of the SS blocks are non-contiguous. Similarly, in some aspects, one or more SS blocks of an SS burst may be sent in continuous radio resources (e.g., continuous symbol periods) during one or more time slots. Additionally, or alternatively, one or more SS blocks of an SS burst may be sent in non-contiguous radio resources.

[0061] In some aspects, the SS burst may have a burst periodicity, whereby the base station sends the SS blocks of the SS burst according to the burst periodicity. In other words, the SS blocks may be repeated during each SS burst. In some aspects, the SS burst set may have a burst set periodicity, whereby the base station sends the SS bursts of the SS burst set according to a fixed burst set periodicity. In other words, during each SS burst set, the SS burst may be repeated.

[0062] The base station may send system information, such as system information blocks (SIBs), on a physical downlink shared channel (PDSCH) in certain time slots. The base station may send control information / data on a physical downlink control channel (PDCCH) in C symbol periods of a time slot, where B may be configurable for each time slot. The base station may send traffic data and / or other data on the PDSCH in the remaining symbol periods of each time slot.

[0063] As mentioned above, Figure 3A and 3B Provided as examples. Other examples may differ from the Figure 3A and 3B An example of description.

[0064] Figure 4 An example slot format 400 with a normal cyclic prefix is ​​shown. The available time-frequency resources may be divided into resource blocks. Each resource block may cover a set of subcarriers in a slot (e.g., 12 subcarriers) and may include multiple resource elements. Each resource element may cover a subcarrier in a symbol period (e.g., in time) and may be used to send a modulation symbol, which may be a real or complex number.

[0065] An interlace structure may be used for each of the downlink and uplink of FDD in certain telecommunication systems (e.g., NR). For example, Q interlaces indexed from 0 to Q–1 may be defined, where Q may be equal to 4, 6, 8, 10, or some other value. Each interlace may include time slots separated by Q frames. Specifically, interlace q may include time slots q, q+Q, q+2Q, etc., where q∈{0,…,Q–1}.

[0066] A UE may be located within the coverage of multiple BSs. One of these BSs may be selected to serve the UE. The serving BS may be selected based at least in part on various criteria such as received signal strength, received signal quality, path loss, etc. The received signal quality may be quantified by a signal to noise and interference ratio (SNIR) or a reference signal received quality (RSRQ) or some other metric. The UE may operate in a dominant interference scenario, where the UE may observe high interference from one or more interfering BSs.

[0067] Although aspects of the examples described herein may be associated with NR or 5G technology, aspects of the present disclosure may be applicable to other wireless communication systems. New Radio (NR) may refer to a radio configured to operate according to a new air interface (e.g., an air interface other than an orthogonal frequency division multiple access (OFDMA)-based air interface) or a fixed transport layer (e.g., other than the Internet Protocol (IP)). In some aspects, NR may utilize OFDM with CP (referred to herein as cyclic prefix OFDM or CP-OFDM) and / or SC-FDM on the uplink, may utilize CP-OFDM on the downlink, and include support for half-duplex operation using time division duplex (TDD). In some aspects, NR may utilize OFDM with CP (referred to herein as CP-OFDM) and / or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM), for example, on the uplink, may utilize CP-OFDM on the downlink, and include support for half-duplex operation using TDD. NR may include enhanced mobile broadband (eMBB) services for broadband (e.g., 80 megahertz (MHz) and above), millimeter wave (mmW) for high carrier frequencies (e.g., 60 gigahertz (GHz)), massive MTC (mMTC) for non-backward compatible MTC technologies, and / or mission critical ultra-reliable low latency communication (URLLC) services.

[0068] In some aspects, a single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 subcarriers with a subcarrier bandwidth of 60 or 120 kilohertz (kHz) and a duration of 0.1 milliseconds (ms). Each radio frame may include 40 time slots and may have a length of 10 ms. Thus, each time slot may have a length of 0.25 ms. Each time slot may indicate a link direction (e.g., downlink (DL) or uplink (UL)) for data transmission, and the link direction of each time slot may be switched dynamically. Each time slot may include DL / UL data and DL / UL control data.

[0069] Beamforming can be supported, and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas with multi-layer DL transmission with up to 8 streams and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple units of up to 8 service units is supported. Alternatively, NR can support different air interfaces instead of OFDM-based interfaces. NR networks can include entities such as central units or distributed units.

[0070] As mentioned above, providing Figure 4 As an example. Other examples may differ from Figure 4 An example of description.

[0071] Figure 5 5 is a diagram illustrating an example of a DL-centric time slot or wireless communication structure. The DL-centric time slot may include a control portion 502. The control portion 502 may be present in an initial or beginning portion of the DL-centric time slot. The control portion 502 may include various scheduling information and / or control information corresponding to various portions of the DL-centric time slot. In some configurations, the control portion 502 may be a physical DL control channel (PDCCH), such as Figure 5 In some aspects, the control portion 502 may include legacy PDCCH information, shortened PDCCH (sPDCCH) information, a control format indicator (CFI) value (e.g., carried on a physical control format indicator channel (PCFICH)), one or more grants (e.g., downlink grant, uplink grant, etc.), and / or the like.

[0072] The DL-centric time slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-centric time slot. The DL data portion 504 may include communication resources for communicating DL data from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 504 may be a physical DL shared channel (PDSCH).

[0073] The DL-centric time slot may also include an uplink (UL) short burst portion 506. The UL short burst portion 506 may sometimes be referred to as an uplink burst, an uplink burst portion, a common UL burst, a short burst, an uplink short burst, a common UL short burst, a common UL short burst portion, and / or various other suitable terms. In some aspects, the UL short burst portion 506 may include one or more reference signals. Additionally, or alternatively, the UL short burst portion 506 may include feedback information corresponding to various other portions of the DL-centric time slot. For example, the UL short burst portion 506 may include feedback information corresponding to the control portion 502 and / or the data portion 504. Non-limiting examples of information that may be included in the UL short burst portion 506 include an acknowledgement (ACK) signal (e.g., PUCCH ACK, physical uplink shared channel (PUSCH) ACK, immediate ACK), a negative acknowledgement (NACK) signal (e.g., PUCCH NACK, PUSCH NACK, immediate NACK), a scheduling request (SR), a buffer status report (BSR), a hybrid automatic repeat request (HARQ) indicator, a channel state indication (CSI), a channel quality indicator (CQI), a sounding reference signal (SRS), a demodulation reference signal (DMRS), PUSCH data, and / or various other suitable types of information. The UL short burst portion 506 may include additional or alternative information, such as information related to a random access channel (RACH) procedure, a scheduling request, and various other suitable types of information.

[0074] like Figure 5 As shown, the end of the DL data portion 504 can be separated in time from the beginning of the UL short burst portion 506. This time separation is sometimes referred to as an interval, a guard period, a guard interval, and / or various other suitable terms. This separation provides time for switching from DL communication (e.g., a receive operation performed by a slave entity (e.g., a UE)) to UL communication (e.g., a transmit operation performed by a slave entity (e.g., a UE)). The foregoing is an example of a DL-centric wireless communication structure, and alternative structures with similar features may exist without necessarily departing from the aspects described herein.

[0075] As mentioned above, Figure 5 Provided as examples. Other examples may differ from the Figure 5 An example of description.

[0076] Figure 6 600 is a diagram illustrating an example of an uplink (UL) centric timeslot or wireless communication structure. The UL centric timeslot may include a control portion 602. The control portion 602 may be present in an initial or beginning portion of the UL centric timeslot. Figure 6The control portion 602 in the embodiment may be similar to the control portion 602 in the embodiment of the present invention. Figure 5 The control portion 502 described above. The UL-centered time slot may also include an uplink long burst portion 604. The UL long burst portion 604 may sometimes be referred to as the payload of the UL-centered time slot. The UL long burst portion 604 may include communication resources for communicating UL data from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).

[0077] like Figure 6 As shown, the end of the control portion 602 can be separated in time from the beginning of the UL long burst portion 604. This time separation may sometimes be referred to as an interval, a guard period, a guard interval, and / or various other suitable terms. This separation provides time for switching from DL communication (e.g., receiving operation of the scheduling entity) to UL communication (e.g., transmission of the scheduling entity).

[0078] The UL-centric timeslot may also include an uplink short burst portion 606 . Figure 6 The UL short burst portion 606 in the above reference may be similar to Figure 5 The UL short burst portion 506 described above may include the combination of Figure 5 The foregoing is one example of an uplink-centric wireless communication architecture, and alternative architectures with similar features may exist without necessarily departing from aspects described herein.

[0079] In one example, a wireless communication structure such as a frame may include UL-centric time slots and DL-centric time slots. In this example, the ratio of UL-centric time slots to DL-centric time slots in a frame may be dynamically adjusted based at least in part on the amount of UL data and the amount of DL data to be sent. For example, if there is more UL data, the ratio of UL-centric time slots to DL-centric time slots may increase. Conversely, if there is more DL data, the ratio of UL-centric time slots to DL-centric time slots may decrease.

[0080] As mentioned above, Figure 6 Provided as examples. Other examples may differ from the Figure 6 An example of description.

[0081] In some cases, the base station and the UE may communicate with each other via different service types. For example, the first communication between the base station and the UE may use an enhanced mobile broadband (eMBB) service type, the second communication between the base station and the UE may use an ultra-reliable low-latency communication (URLLC) service type, and / or the like. In this case, different service types may have different priorities, for example, different latency and / or reliability requirements, based at least in part on different features and / or requirements (for example, URLLC services may have higher reliability and lower latency requirements compared to eMBB services, and thus have higher priorities). In some cases, the base station may configure corresponding PUCCH resources for the UE for sending channel state information (CSI) reports of different service types with different priorities. For example, the CSI report may be a periodic CSI (P-CSI) report, a semi-persistent CSI (SP-CSI) report, etc. In some cases, the corresponding PUCCH resources configured for CSI reports associated with different service types may conflict with each other, for example, when the corresponding PUCCH resources are scheduled in the same time slot on the same PUCCH carrier.

[0082] In this case, the UE may need to resolve conflicts to determine which CSI report(s) to send. For example, in the case where any PUCCH resources do not overlap in time, the UE can resolve conflicts by selecting up to two non-overlapping PUCCH resources corresponding to the CSI report with the highest priority. Alternatively, in the case where two or more PUCCH resources overlap in time, the UE can resolve conflicts by multiplexing all CSI reports scheduled to be sent in a time slot into a single PUCCH transmission, which is sent on one PUCCH resource that has been configured for the UE. However, these methods generally do not distinguish between CSI reports associated with different service types (e.g., eMBB and URLLC). Instead, the priorities associated with different CSI reports are typically determined according to a hierarchy including factors such as CSI report type (e.g., non-periodic, periodic, semi-persistent, etc.), cell identifier, CSI report configuration identifier, etc. In addition, multiplexing CSI reports associated with different service types may have a negative impact on reliability because the multiplexed CSI reports may not distinguish between CSI associated with different service types. Therefore, existing techniques for resolving conflicts between multiple CSI reports scheduled to be sent in a specific time slot often fall short in fully considering different characteristics and / or requirements associated with different service types (eg, different latency and / or reliability requirements).

[0083] Some aspects described herein provide techniques and apparatus for resolving conflicts between multiple CSI reports that are associated with different service types and are scheduled to be sent in the same time slot on corresponding PUCCH resources. In particular, as further described in detail herein, the UE may select one or more CSI reports to be sent in a time slot from multiple CSI reports based on corresponding priorities associated with different service types. For example, in some aspects, the URLLC service type generally has a higher priority than the eMBB service type. Therefore, the UE may send one or more PUCCH transmissions (e.g., up to two PUCCH transmissions) in a time slot, including selecting one or more CSI reports to be sent based on corresponding priorities associated with different service types. For example, in some aspects, the UE may discard any CSI reports associated with a low priority service type (e.g., an eMBB service type), and then apply one or more rules to select one or more CSI reports to be sent from the remaining CSI reports associated with a high priority service type (e.g., a URLLC service type). For example, after discarding CSI reports associated with low priority service types, the UE may select one or more of the remaining CSI reports associated with high priority service types with the highest priority, multiplex the remaining CSI reports associated with the high priority service types into a single PUCCH transmission, etc. Additionally, or alternatively, in some aspects, the UE may select a subset of CSI reports with the highest priority in the event that no CSI reports are associated with PUCCH resources that overlap in time. In this case, at least one CSI report selected to be sent in the time slot may be associated with the high priority service type, and other CSI reports selected to be sent in the time slot may be associated with the high priority service type or the low priority service type.

[0084] In this way, the UE can resolve conflicts between multiple CSI reports to be sent in a particular time slot based at least in part on the service types associated with the multiple CSI reports, which enables the UE to resolve conflicts in a manner that can meet different performance requirements associated with different service types (for example, based on the URLLC service having more stringent reliability and / or latency requirements than the eMBB service, the CSI report for the URLLC service takes precedence over the CSI report for the eMBB service).

[0085] Figure 7A-7B is a diagram illustrating an example implementation 700 for conflict resolution of CSI reporting on PUCCH in accordance with various aspects of the present disclosure. Figure 7A-7BAs shown, exemplary implementation 700 includes a UE communicating with a base station. In addition, as described herein, the UE may communicate with the base station using different service types associated with different priorities. For example, in some aspects, the UE may communicate with the base station using a first service type (e.g., an eMBB service) having a low priority and a second service type (e.g., a URLLC service) having a high priority. In some aspects, the first service type may be associated with a physical layer priority index having a first value (e.g., zero), and the second service type may be associated with a physical layer priority index having a second value (e.g., one), wherein the first value may indicate that the first service type has a low priority and the second value may indicate that the second service type has a high priority (e.g., a lower value of the physical layer priority index may indicate a lower priority, while a higher value of the physical layer priority index may indicate a higher priority, and vice versa).

[0086] like Fig. 7A As shown, by reference numeral 710, the base station may configure corresponding PUCCH resources for the UE for sending CSI reports associated with different service types (e.g., eMBB and URLLC). For example, in some aspects, the base station may configure one or more PUCCH resources for sending one or more CSI reports associated with a first service type (e.g., eMBB), one or more PUCCH resources for sending one or more CSI reports associated with a second service type (e.g., URLLC), and the like. In some aspects, the corresponding PUCCH resources configured for CSI reports associated with different service types may overlap in time and / or may not overlap in time. For example, as shown by reference numeral 720, the UE may be configured with multiple PUCCH resources 722, 724, 726, which correspond to corresponding CSI reports to be sent in the same time slot, and the PUCCH resources 722, 724, 726 do not overlap in time. In another example, as indicated by reference numeral 730, the UE may be configured with multiple PUCCH resources 732, 734, 736 corresponding to respective CSI reports to be sent in the same time slot, and at least two of the PUCCH resources 732, 734, 736 overlap in time (e.g., in the example shown, PUCCH resource 734 overlaps in time relative to PUCCH resource 736).

[0087] like Fig. 7AAs further shown in the figure, by reference numeral 740, the UE and the base station can identify a conflict between multiple CSI reports, and the multiple CSI reports are scheduled to be sent in a particular time slot. For example, in some aspects, the UE and the base station can generally identify a conflict based at least in part on the base station configuring multiple CSI reports on corresponding PUCCH resources in the same time slot. Thus, in some aspects, the UE and the base station can identify a conflict based at least in part on a single time slot including multiple non-overlapping PUCCH resources corresponding to different CSI reports (e.g., as shown in reference numeral 720), multiple overlapping PUCCH resources corresponding to different CSI reports (e.g., as shown in reference numeral 730), etc.

[0088] like Figure 7B As shown, by reference numeral 750, the UE and the base station may resolve conflicts between multiple CSI reports scheduled to be sent in a particular time slot based at least in part on corresponding service types associated with the conflicting CSI reports. For example, as described above, the conflicting CSI reports may include one or more CSI reports for a first (e.g., low priority) service type and one or more CSI reports for a second (e.g., high priority) service type. Thus, as described herein, the UE and the base station may employ one or more techniques to resolve conflicts and determine which CSI reports to send and receive in a particular time slot based at least in part on corresponding service types associated with multiple CSI reports that the UE is scheduled to send on corresponding PUCCH resources associated with the time slot, the PUCCH resources may be non-overlapping in time, overlapping in time, and / or the like.

[0089] In some aspects, in a first technique, the UE and the base station may determine that the UE is to discard each CSI report associated with a first (e.g., low priority) service type, and then select one or more CSI reports to be sent in a time slot from the remaining CSI reports (e.g., from one or more CSI reports associated with a second (e.g., high priority) service type). For example, in a case where the first service type is eMBB and the second service type is URLLC, where the eMBB service type has a lower priority than the URLLC service type, the UE may be configured to discard all CSI reports for the eMBB service type, and then select one or more CSI reports to be sent in the time slot from the remaining CSI reports associated with the URLLC service type. In the first technique, the UE may generally discard all CSI reports associated with the low priority service type, regardless of whether the PUCCH resources for the conflicting CSI reports overlap. Therefore, in the first technique, when one or more CSI reports for the low priority service type and one or more CSI reports for the high priority service type are scheduled to be sent on PUCCH resources within the same time slot, the UE may discard all CSI reports associated with the low priority service type. In addition, as described above, after discarding the CSI reports associated with the low priority service type, the UE may select one or more CSI reports from the remaining CSI reports associated with the high priority service type to send in the time slot. For example, as described herein, depending on whether the PUCCH resources associated with the remaining CSI reports overlap in time or do not overlap in time, the UE and the base station may adopt different methods to determine the CSI report to be sent in the time slot.

[0090] For example, in the event that the PUCCH resources associated with the remaining CSI reports do not overlap and / or the UE has not been configured with a higher-level (e.g., radio resource control (RRC) layer) parameter (e.g., a multi-CSI-PUCCH-resourceList parameter) that provides a list of PUCCH resources to be used to multiplex or otherwise combine multiple CSI reports, the UE may select one or more (typically up to two) non-overlapping PUCCH resources with the highest priority. For example, in some aspects, the priorities associated with PUCCH resources may generally be defined according to a hierarchy, where the first layer in the hierarchy may be a service type (e.g., prioritizing URLLC over eMBB), and subsequent layers in the hierarchy may include a CSI report type (e.g., where a non-periodic CSI report has a higher priority than a semi-persistent CSI report, which has a higher priority than a periodic CSI report, etc.), a cell identifier, a CSI report configuration identifier, etc. Therefore, to select among the CSI reports associated with the high priority service type, the UE may select a first PUCCH resource corresponding to one of the CSI reports associated with the high priority service type having the highest priority (e.g., based on the CSI report type, the cell identifier, the CSI report configuration identifier, etc.). Furthermore, in the event that there are multiple CSI reports associated with the high priority service type, the UE may select a second PUCCH resource corresponding to the highest priority CSI report among all remaining PUCCH resources that do not overlap with the first PUCCH resource corresponding to the CSI report having the highest priority.

[0091] Alternatively, if the PUCCH resources associated with the remaining CSI reports are overlapping and the UE has configured higher layer parameters that provide a list of PUCCH resources for multiplexing or otherwise combining multiple CSI reports, the UE may multiplex all CSI reports associated with the high priority service type into one PUCCH transmission. Thus, in this case, the UE may send one PUCCH transmission that includes a multiplexed high priority CSI report on one configured PUCCH resource that is selected from the list of PUCCH resources for multiplexing or otherwise combining multiple CSI reports (e.g., based at least in part on which PUCCH resource in the list is most appropriate for the payload size of the multiplexed CSI report, as indicated in an RRC parameter (e.g., multi-CSI-PUCCH-resourceList parameter)). In addition, the UE does not multiplex CSI reports associated with the low priority service type and CSI reports associated with the high priority service type in the same PUCCH transmission. Instead, the UE may typically use PUCCH resources configured in higher-level RRC parameters (e.g., multi-CSI-PUCCH-resourceList) to send multiplexed CSI reports associated with a high priority service type (e.g., URLLC), or to send multiplexed CSI reports associated with a low priority service type (e.g., eMBB). In this way, the base station does not need to configure separate PUCCH resources to multiplex CSI reports associated with a high priority service type or to multiplex CSI reports associated with a low priority service type, because each service type may rely on the same RRC parameters (e.g., for multiplexing URLLC CSI reports where all eMBB CSI reports are initially discarded, or for multiplexing eMBB CSI reports where no URLLC CSI reports are scheduled in a timeslot and two or more eMBB CSI reports are scheduled in the same timeslot on PUCCH resources that overlap in time).

[0092] Additionally, or alternatively, in the second technique, the UE and the base station may resolve conflicts between multiple CSI reports scheduled to be sent on corresponding PUCCH resources in the same time slot by initially determining whether the corresponding PUCCH resources associated with the multiple CSI reports overlap in time or do not overlap in time.

[0093] For example, when the second technique is applied in the case where conflicting CSI reports are scheduled to be sent on non-overlapping PUCCH resources (e.g., as in the case of the example time slot shown by reference numeral 720), the UE may select one or more (typically up to two) non-overlapping PUCCH resources with the highest priority. For example, in a similar manner as described above, the priority associated with the PUCCH resources may generally be defined according to a hierarchy, where the first level in the hierarchy may be a service type (e.g., giving priority to URLLC over eMBB), and subsequent levels in the hierarchy may include CSI report type, cell identifier, CSI report configuration identifier, etc. Therefore, in order to select one or more CSI reports with the highest priority, the UE may select a first PUCCH resource corresponding to one of the CSI reports associated with the high priority service type. In some aspects, the UE may then select a second PUCCH resource corresponding to one of the remaining CSI reports with the highest priority. For example, if the remaining CSI reports include one or more CSI reports associated with the high priority service type, the second CSI report may be one of the remaining CSI reports that is associated with the high priority service type and has the highest priority based on the CSI report type, cell identifier, CSI report configuration identifier, etc. Alternatively, in the case where the conflicting CSI reports include only one CSI report associated with the high priority service type, the second CSI report may be one CSI report among the remaining CSI reports that is associated with the low priority service type (e.g., eMBB) and has the highest priority based on the CSI report type, the cell identifier, and the CSI report configuration identifier. In other words, when the conflicting CSI reports do not overlap in time, the first CSI report may be associated with the high priority service type, and the second CSI report may be associated with the high priority service type (e.g., the conflicting CSI report includes two or more CSI reports associated with the high priority service type) or with the low priority service type (e.g., the conflicting CSI report includes only one CSI report associated with the high priority service type and one or more CSI reports associated with the low priority service type).

[0094] Alternatively, when the second technique is applied in the case where the conflicting CSI reports include two or more CSI reports scheduled to be transmitted on PUCCH resources that overlap in time (e.g., as in the case of the example time slot shown by reference numeral 730), the UE may discard each CSI report associated with the low priority service type (e.g., eMBB) and then select one or more CSI reports to be transmitted in the time slot from the remaining CSI reports associated with the high priority service type (e.g., URLLC). For example, in the case where the PUCCH resources associated with the remaining CSI reports associated with the high priority service type are non-overlapping (after the CSI reports associated with the low priority service type are discarded), the UE may select one or more (typically up to two) non-overlapping PUCCH resources with the highest priority (e.g., according to the above-described hierarchy). Alternatively, if, after discarding the CSI reports associated with the low priority service type, the PUCCH resources associated with the remaining CSI reports associated with the high priority service type are still overlapping in time, the UE may multiplex all CSI reports associated with the high priority service type into one PUCCH transmission. In this case, the UE may send one PUCCH transmission comprising a CSI report multiplexed on one configured PUCCH resource selected from a list of PUCCH resources for multiplexing or otherwise combining multiple CSI reports (e.g., as indicated in RRC parameters, such as the multi-CSI-PUCCH-resourceList parameter).

[0095] like Figure 7BAs further shown in the figure by reference numeral 760, the UE may send and the base station may receive one or more CSI reports selected from multiple CSI reports scheduled to be sent in a time slot after resolving conflicts between the multiple CSI reports. For example, in a case where the PUCCH resources corresponding to the selected CSI reports do not overlap in time, the UE may send one or more PUCCH transmissions including the selected CSI report on the corresponding PUCCH resources. Alternatively, in a case where the PUCCH resources corresponding to the selected CSI reports overlap in time, the UE may multiplex the selected CSI report into one PUCCH transmission that may be sent on one PUCCH resource, which is selected from a list of configured PUCCH resources for sending multiple CSI reports that are multiplexed or otherwise combined. In addition, in some aspects, the UE may determine whether there are one or more other uplink transmissions (e.g., other PUCCH transmissions, PUSCH transmissions, SRS transmissions, physical random access channel (PRACH) transmissions, etc.) in the time slot that overlap with the PUCCH resources used to send the CSI report. In this case, the UE may initially resolve conflicts between multiple CSI reports scheduled in a timeslot in the manner described in further detail above, and then use any suitable technique to resolve any other conflicts between surviving CSI reports and other uplink transmissions before sending the selected CSI report on the corresponding PUCCH resources.

[0096] As mentioned above, FIG7 is provided as an example. Other examples may differ from the example described with respect to FIG7.

[0097] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 800 is an example of operations in which a UE (eg, UE 120 and / or the like) performs contention resolution for reporting CSI on a PUCCH.

[0098] like Figure 8 As shown, in some aspects, process 800 may include identifying a plurality of CSI reports scheduled to be sent in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type (block 810). For example, as described above, the UE may identify (e.g., using controller / processor 280, memory 282, etc.) a plurality of CSI reports scheduled to be sent in a time slot on a corresponding PUCCH resource. In some aspects, the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type.

[0099] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include selecting one or more CSI reports to be sent in a time slot from a plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type (block 820). For example, as described above, the UE may select (e.g., using controller / processor 280, memory 282, etc.) one or more CSI reports to be sent in a time slot from a plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type.

[0100] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending one or more PUCCH transmissions including one or more selected CSI reports in a time slot (block 830). For example, as described above, the UE may send (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) one or more PUCCH transmissions including one or more selected CSI reports in a time slot.

[0101] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or be related to one or more other processes described elsewhere herein.

[0102] In a first aspect, selecting one or more CSI reports to be sent in a time slot includes discarding one or more CSI reports associated with the first service type based at least in part on determining that a first priority associated with the first service type is lower than a second priority associated with the second service type, and selecting one or more CSI reports to be sent in the time slot from one or more CSI reports associated with the second service type.

[0103] In a second aspect, alone or in combination with the first aspect, selecting one or more CSI reports to be sent in a time slot also includes determining that the one or more CSI reports associated with the second service type include two or more CSI reports, wherein selecting the one or more CSI reports to be sent in the time slot includes two of the two or more CSI reports associated with the second service type having the highest priority based at least in part on determining that none of the two or more CSI reports are associated with PUCCH resources that overlap in time.

[0104] In a third aspect, alone or in combination with one or more of the first and second aspects, sending one or more CSI reports in a time slot includes: multiplexing one or more CSI reports associated with the second service type into a PUCCH based at least in part on determining that the one or more CSI reports associated with the second service type include two or more CSI reports associated with PUCCH resources that overlap in time, and sending a PUCCH in a time slot on a configured PUCCH resource.

[0105] In a fourth aspect, alone or in combination with one or more of the first to third aspects, selecting one or more CSI reports to be sent in a time slot includes: discarding one or more CSI reports associated with the first service type based at least in part on determining that multiple CSI reports scheduled to be sent in the time slot include at least two CSI reports associated with PUCCH resources that overlap in time, and selecting one or more CSI reports to be sent in the time slot from one or more CSI reports associated with the second service type.

[0106] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more CSI reports selected to be sent in a time slot include two CSI reports having the highest priority among the multiple CSI reports based at least in part on determining that none of the multiple CSI reports is associated with PUCCH resources that overlap in time.

[0107] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the two CSI reports having the highest priority include a first CSI report associated with the second service type and a second CSI report associated with the first service type or the second service type.

[0108] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, one or more CSI reports to be sent in a time slot are further selected based at least in part on one or more of a report type, a cell identifier, or a configuration identifier associated with the multiple CSI reports.

[0109] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the first service type is eMBB, and the second service type is URLLC.

[0110] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 800 also includes resolving one or more conflicts between one or more CSI reports selected to be sent in a time slot and one or more additional uplink transmissions scheduled in the time slot after the one or more CSI reports are selected.

[0111] although Figure 8Example blocks of process 800 are shown, but in some aspects process 800 may include additional blocks, fewer blocks, different blocks, or different blocks. Figure 8 Blocks of different arrangements of the blocks shown. Additionally, or alternatively, two or more blocks of process 800 may be performed in parallel.

[0112] Fig. 9 9 is a diagram illustrating an example process 900 performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process 900 is an example of operations performed by a base station (eg, base station 110 and / or the like) associated with contention resolution for reporting CSI on a PUCCH.

[0113] like Fig. 9 As shown, in some aspects, process 900 may include identifying a plurality of CSI reports that a UE is scheduled to transmit in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type (block 910). For example, a base station (e.g., using controller / processor 240, memory 242, etc.) may identify a plurality of CSI reports that a UE is scheduled to transmit in a time slot on a corresponding PUCCH resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type, as described above.

[0114] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include determining one or more CSI reports to be sent in a time slot from a plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type (block 920). For example, a base station (e.g., using controller / processor 240, memory 242, etc.) may determine one or more CSI reports to be sent in a time slot from a plurality of CSI reports based at least in part on a first priority associated with the first service type and a second priority associated with the second service type, as described above.

[0115] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include receiving one or more PUCCH transmissions including one or more CSI reports in a time slot (block 930). For example, as described above, a base station (e.g., using antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) may receive one or more PUCCH transmissions including one or more CSI reports in a time slot.

[0116] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or be related to one or more other processes described elsewhere herein.

[0117] In a first aspect, determining one or more CSI reports to be sent in a time slot includes determining that the UE will discard one or more CSI reports associated with the first service type based at least in part on determining that a first priority associated with the first service type is lower than a second priority associated with the second service type, and determining one or more CSI reports to be sent in the time slot from one or more CSI reports associated with the second service type.

[0118] In a second aspect, alone or in combination with the first aspect, determining one or more CSI reports to be sent in a time slot includes: determining that one or more CSI reports associated with the second service type include two or more CSI reports, wherein the one or more CSI reports sent in the time slot include two with the highest priority among the two or more CSI reports associated with the second service type based at least in part on determining that none of the two or more CSI reports are associated with PUCCH resources that overlap in time.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving one or more CSI reports in a time slot includes receiving a PUCCH in a time slot on a configured PUCCH resource, wherein the one or more CSI reports associated with the second service type are multiplexed into one PUCCH based at least in part on the one or more CSI reports associated with the second service type including two or more CSI reports associated with PUCCH resources that overlap in time.

[0120] In a fourth aspect, alone or in combination with one or more of the first to third aspects, determining one or more CSI reports to be sent in a time slot includes determining that the UE will discard one or more CSI reports associated with the first service type based at least in part on determining that multiple CSI reports scheduled to be sent in the time slot include at least two CSI reports associated with PUCCH resources that overlap in time, and determining one or more CSI reports to be sent in the time slot from one or more CSI reports associated with the second service type.

[0121] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more CSI reports sent in a time slot include two CSI reports having the highest priority based at least in part on determining that none of the multiple CSI reports are associated with PUCCH resources that overlap in time.

[0122] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the two CSI reports with the highest priority include a first CSI report associated with the second service type and a second CSI report associated with the first service type or the second service type.

[0123] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, one or more CSI reports to be sent in a time slot are further determined based at least in part on one or more of a report type, a cell identifier, or a configuration identifier associated with the multiple CSI reports.

[0124] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first service type is enhanced mobile broadband, and the second service type is ultra-reliable low-latency communication.

[0125] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 900 includes resolving one or more conflicts between one or more CSI reports selected to be sent in a time slot and one or more additional uplink transmissions scheduled in the time slot after determining the one or more CSI reports.

[0126] although Fig. 9 Example blocks of process 900 are shown, but in some aspects process 900 may include additional blocks, fewer blocks, different blocks, or different Fig. 9 Blocks of different arrangements of the blocks shown. Additionally, or alternatively, two or more blocks of process 900 may be performed in parallel.

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

[0128] As used herein, the term "component" is broadly understood to mean hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

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

[0130] It is apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without referring to specific software code. It should be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0131] Even if the claims describe and / or disclose a specific combination of features in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. The phrase "at least one" in a series of projects refers to any combination of these projects, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, and any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc or any other order of a, b and c). Unless explicitly stated, any element, behavior or instruction used in this article shall not be interpreted as critical or necessary. In addition, as used herein, the words "one ("a" and "an")" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the words "said" and "the" are intended to include one or more reference items related to the word "said" and can be used interchangeably with "said one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and can be used interchangeably with "one or more". If only one item is intended to be used, the phrase "only one" or similar language is used. In addition, as used herein, the terms "having" and / or the like are intended to be open terms. In addition, unless otherwise expressly stated, the word "based on" means "at least partially based on". In addition, as used herein, the word "or" is intended to be inclusive when used in a series and can be used interchangeably with "and / or", unless otherwise expressly stated (e.g., if used in combination with "or" or "only one of them").

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: identifying a plurality of channel state information (CSI) reports scheduled to be transmitted in a time slot on a corresponding physical uplink control channel (PUCCH) resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; selecting one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type, a second priority associated with the second service type, and a hierarchy associated with the corresponding PUCCH resources, wherein a first layer in the hierarchy is a service type and subsequent layers in the hierarchy include CSI report types; and One or more PUCCH transmissions including the one or more selected CSI reports are sent in the time slot.

2. The method according to claim 1, wherein: Selecting the one or more CSI reports to be sent in the time slot comprises: discarding the one or more CSI reports associated with the first service type based at least in part on determining that the first priority associated with the first service type is lower than the second priority associated with the second service type; and The one or more CSI reports to be sent in the time slot are selected from the one or more CSI reports associated with the second service type.

3. The method according to claim 2, wherein: Selecting the one or more CSI reports to be sent in the time slot further comprises: Determining that the one or more CSI reports associated with the second service type include two or more CSI reports, wherein selecting the one or more CSI reports to be sent in the time slot includes two of the two or more CSI reports associated with the second service type having the highest priority based at least in part on determining that none of the two or more CSI reports are associated with PUCCH resources that overlap in time.

4. The method according to claim 2, wherein: Sending the one or more CSI reports in the time slot includes: multiplexing the one or more CSI reports associated with the second service type into one PUCCH based at least in part on determining that the one or more CSI reports associated with the second service type include two or more CSI reports associated with PUCCH resources that overlap in time; and The one PUCCH is sent in the timeslot on a configured PUCCH resource.

5. The method according to any one of claims 1 to 4, wherein: Selecting the one or more CSI reports to be sent in the time slot comprises: discarding the one or more CSI reports associated with the first service type based at least in part on determining that the plurality of CSI reports scheduled to be sent in the time slot include at least two CSI reports associated with PUCCH resources that overlap in time; and The one or more CSI reports to be sent in the time slot are selected from the one or more CSI reports associated with the second service type.

6. The method according to any one of claims 1 to 4, wherein: Selecting the one or more CSI reports to be sent in the time slot includes two CSI reports having highest priorities among the plurality of CSI reports based at least in part on determining that none of the plurality of CSI reports are associated with PUCCH resources that overlap in time.

7. The method according to claim 6, wherein: The two CSI reports having the highest priority include a first CSI report associated with the second service type and a second CSI report associated with the first service type or the second service type.

8. The method according to any one of claims 1 to 4, wherein: Subsequent layers in the hierarchy also include one or more of a cell identifier or a configuration identifier.

9. The method according to any one of claims 1 to 4, wherein: The first service type is enhanced mobile broadband, and the second service type is ultra-reliable low latency communication.

10. The method according to any one of claims 1 to 4, further comprising: One or more conflicts between the one or more CSI reports selected to be sent in the time slot and one or more additional uplink transmissions scheduled in the time slot after selecting the one or more CSI reports are resolved.

11. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: identifying a plurality of channel state information (CSI) reports scheduled to be transmitted in a time slot on a corresponding physical uplink control channel (PUCCH) resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; selecting one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type, a second priority associated with the second service type, and a hierarchy associated with the corresponding PUCCH resources, wherein a first layer in the hierarchy is a service type and subsequent layers in the hierarchy include CSI report types; and One or more PUCCH transmissions including the one or more selected CSI reports are sent in the time slot.

12. The UE according to claim 11, wherein: When selecting the one or more CSI reports to be sent in the time slot, the one or more processors are further configured to: discarding the one or more CSI reports associated with the first service type based at least in part on determining that the first priority associated with the first service type is lower than the second priority associated with the second service type; and The one or more CSI reports to be sent in the time slot are selected from the one or more CSI reports associated with the second service type.

13. The UE according to any one of claims 11 to 12, wherein: When selecting the one or more CSI reports to be sent in the time slot, the one or more processors are further configured to: discarding the one or more CSI reports associated with the first service type based at least in part on determining that the plurality of CSI reports scheduled to be sent in the time slot include at least two CSI reports associated with PUCCH resources that overlap in time; and The one or more CSI reports to be sent in the time slot are selected from the one or more CSI reports associated with the second service type.

14. The UE according to any one of claims 11 to 12, wherein: Selecting the one or more CSI reports to be sent in the time slot includes two CSI reports having highest priorities among the plurality of CSI reports based at least in part on determining that none of the plurality of CSI reports are associated with PUCCH resources that overlap in time.

15. The UE according to any one of claims 11-12, wherein the one or more processors are further configured to: One or more conflicts between the one or more CSI reports selected to be sent in the time slot and one or more additional uplink transmissions scheduled in the time slot after selecting the one or more CSI reports are resolved.

16. A method of wireless communication performed by a base station, comprising: identifying a plurality of channel state information (CSI) reports that a user equipment (UE) is scheduled to transmit in a time slot on a corresponding physical uplink control channel (PUCCH) resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; determining one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type, a second priority associated with the second service type, and a hierarchy associated with the corresponding PUCCH resources, wherein a first layer in the hierarchy is a service type and subsequent layers in the hierarchy include CSI report types; and One or more PUCCH transmissions including the one or more CSI reports are received in the time slot.

17. The method according to claim 16, wherein: Determining the one or more CSI reports to be sent in the time slot comprises: determining that the UE is to discard the one or more CSI reports associated with the first service type based at least in part on determining that the first priority associated with the first service type is lower than the second priority associated with the second service type; and The one or more CSI reports to be sent in the time slot are determined from the one or more CSI reports associated with the second service type.

18. The method according to claim 17, wherein: Determining the one or more CSI reports to be sent in the time slot comprises: Determining that the one or more CSI reports associated with the second service type include two or more CSI reports, wherein the one or more CSI reports sent in the time slot include two with highest priority among the two or more CSI reports associated with the second service type based at least in part on determining that none of the two or more CSI reports are associated with PUCCH resources that overlap in time.

19. The method according to claim 17, wherein: Receiving the one or more CSI reports in the time slot comprises: A PUCCH is received in the time slot on a configured PUCCH resource, wherein the one or more CSI reports associated with the second service type are multiplexed into the one PUCCH based at least in part on the fact that the one or more CSI reports associated with the second service type include two or more CSI reports associated with PUCCH resources that overlap in time.

20. The method according to any one of claims 16 to 19, wherein: Determining the one or more CSI reports to be sent in the time slot comprises: determining that the UE is to discard the one or more CSI reports associated with the first service type based at least in part on determining that the plurality of CSI reports scheduled to be sent in the time slot include at least two CSI reports associated with PUCCH resources that overlap in time; and The one or more CSI reports to be sent in the time slot are determined from the one or more CSI reports associated with the second service type.

21. The method according to any one of claims 16 to 19, wherein: The one or more CSI reports sent in the time slot include two CSI reports having highest priorities among the plurality of CSI reports based at least in part on determining that none of the plurality of CSI reports are associated with PUCCH resources that overlap in time.

22. The method according to claim 21, wherein: The two CSI reports having the highest priority include a first CSI report associated with the second service type and a second CSI report associated with the first service type or the second service type.

23. The method according to any one of claims 16 to 19, wherein: Subsequent layers in the hierarchy also include one or more of a cell identifier or a configuration identifier.

24. The method according to any one of claims 16 to 19, wherein: The first service type is enhanced mobile broadband, and the second service type is ultra-reliable low latency communication.

25. The method according to any one of claims 16 to 19, further comprising: One or more conflicts between the one or more CSI reports selected to be sent in the time slot and one or more additional uplink transmissions scheduled in the time slot after determining the one or more CSI reports are resolved.

26. A base station for wireless communication, comprising: Memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: identifying a plurality of channel state information (CSI) reports that a user equipment (UE) is scheduled to transmit in a time slot on a corresponding physical uplink control channel (PUCCH) resource, wherein the plurality of CSI reports include one or more CSI reports associated with a first service type and one or more CSI reports associated with a second service type; determining one or more CSI reports to be sent in the time slot from the plurality of CSI reports based at least in part on a first priority associated with the first service type, a second priority associated with the second service type, and a hierarchy associated with the corresponding PUCCH resources, wherein a first layer in the hierarchy is a service type and subsequent layers in the hierarchy include CSI report types; and One or more PUCCH transmissions including the one or more CSI reports are received in the time slot.

27. The base station according to claim 26, wherein: When determining the one or more CSI reports to be sent in the time slot, the one or more processors are further configured to: determining that the UE is to discard the one or more CSI reports associated with the first service type based at least in part on determining that the first priority associated with the first service type is lower than the second priority associated with the second service type; and The one or more CSI reports to be sent in the time slot are determined from the one or more CSI reports associated with the second service type.

28. The base station according to any one of claims 26-27, wherein: When determining the one or more CSI reports to be sent in the time slot, the one or more processors are further configured to: determining that the UE is to discard the one or more CSI reports associated with the first service type based at least in part on determining that the plurality of CSI reports scheduled to be sent in the time slot include at least two CSI reports associated with PUCCH resources that overlap in time; and The one or more CSI reports to be sent in the time slot are determined from the one or more CSI reports associated with the second service type.

29. The base station according to any one of claims 26-27, wherein: The one or more CSI reports sent in the time slot include two CSI reports having highest priorities among the plurality of CSI reports based at least in part on a determination that none of the plurality of CSI reports are associated with PUCCH resources that overlap in time.

30. The base station according to any one of claims 26-27, wherein: The one or more CSI reports to be sent in the time slot are further determined based at least in part on one or more of a report type, a cell identifier, or a configuration identifier associated with the plurality of CSI reports.

Images