Uplink control information multiplexing across different transmit-receive points

Abstract

Systems and methods are provided for uplink control information (UCI) multiplexing across multiple transmit and receive points (TRPs) in a wireless communication system. The UE may receive UCI requests for overlapping PUCCH resources from different TRPs. The PUCCH resource may also overlap with a PUSCH resource. The UE may be configured to multiplex the PUCCHs together and / or to multiplex the PUCCHs on the PUSCH. UCIs of different TRPs for the same UCI type may be encoded, rate matched, and mapped collectively or separately. When the PUCCHs are multiplexed together, the resulting PUCCH resources may be determined based on a predetermined rule.

Description

Technical Field

[0001] The present application relates to wireless communication devices, systems and methods, and more particularly to devices, systems and methods for uplink control information (UCI) multiplexing across different transmit and receive points (TRPs). Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include several base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may be otherwise referred to as user equipment (UE).

[0003] In order to meet the growing demand for extended mobile broadband connectivity, wireless communication technology is evolving from long term evolution (LTE) technology to next generation new radio (NR) technology, which may be referred to as fifth generation (5G), designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability than LTE. A UE device may communicate with multiple network entities (e.g., multiple TRPs) simultaneously. In some cases, existing methods for communication are not optimal for communicating with multiple network elements. Therefore, there is a need for improved methods for communicating across different network elements. Summary of the invention

[0004] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to a more detailed description presented later.

[0005] One aspect of the present disclosure includes a method of wireless communication performed by a user equipment (UE), the method comprising determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value. The method also includes receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that overlaps in time with at least one of the first PUCCH or the second PUCCH. The method also includes multiplexing the first set of UCI and the second set of UCI on the PUSCH.

[0006] Another aspect of the present disclosure includes a method of wireless communication performed by a user equipment (UE), the method including determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value, wherein the first PUCCH resource is determined based on a PUCCH resource indicator (PRI) field in a first DCI, and the second PUCCH resource is determined based on a PRI field in the second DCI. The method also includes selecting a PUCCH resource set from a PUCCH resource pool based on a total number of bits in the first set of UCI and the second set of UCI. The method also includes selecting a PUCCH resource associated with the selected PUCCH resource set based on a predetermined rule. The method also includes multiplexing the first set of UCI and the second set of UCI on the selected PUCCH resource.

[0007] Another aspect of the present disclosure includes a user equipment (UE) including a processor configured to determine that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value. The UE also includes a transceiver configured to receive a scheduling configuration for a physical uplink shared channel (PUSCH) that overlaps in time with at least one of the first PUCCH or the second PUCCH. The transceiver is further configured to multiplex the first set of UCI and the second set of UCI on the PUSCH.

[0008] Another aspect of the present disclosure includes a user equipment (UE) including a processor configured to determine that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in a time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value, wherein the first PUCCH resource is determined based on a PUCCH resource indicator (PRI) field in a first DCI, and the second PUCCH resource is determined based on a PRI field in a second DCI. The processor is further configured to select a PUCCH resource set from a PUCCH resource pool based on a total number of bits in the first set of UCI and the second set of UCI. The processor is further configured to select a PUCCH resource associated with the selected PUCCH resource set based on a predetermined rule. The UE also includes a transceiver configured to multiplex the first set of UCI and the second set of UCI on the selected PUCCH resource.

[0009] Another aspect of the present disclosure includes a user equipment (UE) that includes means for determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value. The UE also includes means for receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that overlaps in time with at least one of the first PUCCH or the second PUCCH. The UE also includes means for multiplexing the first set of UCI and the second set of UCI on the PUSCH.

[0010] After reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, other aspects, features, and embodiments will become apparent to those of ordinary skill in the art. Although each feature may be discussed below with respect to certain aspects and drawings, all aspects may include one or more of the advantageous features discussed herein. In other words, although one or more aspects may be discussed as having certain advantageous features, one or more of such features may also be used according to the various aspects discussed herein. In a similar manner, although the exemplary aspects may be discussed below as aspects of devices, systems, or methods, it should be understood that such exemplary aspects may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 A wireless communication network according to some aspects of the present disclosure is illustrated.

[0012] Figure 2 An example portion of a wireless communication system supporting RU sharing technology in wireless communications according to some aspects of the present disclosure is illustrated.

[0013] Figure 3 A diagram illustrating a system including devices supporting RU sharing technology in wireless communications according to some aspects of the present disclosure is illustrated.

[0014] Figure 4 An example wireless communication network according to some aspects of the present disclosure is illustrated.

[0015] Figure 5 An example resource diagram is illustrated according to some aspects of the present disclosure.

[0016] Figure 6 An example resource diagram is illustrated according to some aspects of the present disclosure.

[0017] Figure 7 An example process flow diagram is illustrated according to some aspects of the present disclosure.

[0018] Figure 8 An example process flow diagram is illustrated according to some aspects of the present disclosure.

[0019] Fig. 9 An example process flow diagram is illustrated according to some aspects of the present disclosure.

[0020] Fig.10 is a signaling diagram according to some aspects of the present disclosure.

[0021] Fig.11 A block diagram of a network element according to some aspects of the present disclosure is illustrated.

[0022] Fig.12 A block diagram illustrating a user equipment (UE) according to some aspects of the present disclosure is shown.

[0023] Fig.13 is a flow chart of a method of wireless communication performed by a user equipment (UE) according to some aspects of the present disclosure.

[0024] Fig.14 is a flow chart of a method of wireless communication performed by a user equipment (UE) according to some aspects of the present disclosure.

[0025] Fig.15 is a flow chart of a wireless communication method performed by a network element according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0026] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. In order to provide a comprehensive understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some aspects, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0027] The present disclosure as a whole relates to wireless communication systems, which are also referred to as wireless communication networks. In various aspects, various technologies and devices can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global mobile communication systems (GSM) networks, fifth generation (5G) or new radio (NR) networks and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0028] OFDMA network can implement radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunication association groups with the goal of defining globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP plan to improve UMTS mobile phone standards. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution from LTE, 4G, 5G, NR and beyond wireless technologies, where access to wireless spectrum is shared between networks using a range of new and different radio access technologies or radio air interfaces.

[0029] Specifically, 5G networks consider various deployments, various spectrums, and various services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to (1) ultra-high density (e.g., about 1M nodes / km) 2 (1) provide coverage for the massive Internet of Things (IoT) with ultra-low complexity (e.g., about 10 bits / second), ultra-low energy (e.g., about 10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) provide coverage including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond), and users with extensive mobility or lack of mobility; and (3) provide coverage with enhanced mobile broadband (including very high capacity (e.g., about 10Tbps / km 2 ), coverage of extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).

[0030] The 5G NR communication system can be implemented using an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can effectively address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing may appear at 15kHz on bandwidths (BW) such as 5MHz, 10MHz, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz on 80 / 100MHz BW. For various other indoor broadband implementations, TDD is used on the unlicensed portion of the 5GHz band, and the subcarrier spacing may appear at 60kHz on 160MHz BW. Finally, for various deployments that transmit using the mmWave component at 28GHz TDD, the subcarrier spacing may appear at 120kHz on 500MHz BW. In some aspects, the frequency bands used for 5G NR are divided into multiple different frequency ranges: frequency range one (FR1), frequency range two (FR2), and FR2x. The FR1 band includes a band of 7GHz or lower (e.g., between about 410MHz and about 7125MHz). The FR2 band includes a band within the millimeter wave range between about 24.25GHz and about 52.6GHz. The FR2x band includes a band within the millimeter wave range between about 52.6GHz and about 71GHz. Compared with the FR1 band, the mmWave band may have a shorter range but a higher bandwidth. Additionally, 5G NR may support different subcarrier spacing sets for different frequency ranges.

[0031] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL / downlink (which can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current business needs).

[0032] The various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, such a device can be implemented, or such a method can be implemented, using other structures, functionality, or structures and functionality other than or different from one or more of the aspects set forth herein. For example, the method can be implemented as a part of a system, device, device, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.

[0033] The present disclosure describes systems and methods for UCI multiplexing across different TRPs. A UE may have the ability to communicate with multiple network elements such as transmit receive points (TRPs), where each TRP may act as a wireless connection point between the UE and another network element such as a base station (BS). Communication methods such as multiplexing a physical uplink control channel (PUCCH) message with uplink control information (UCI) may be extended to be used by a UE across multiple TRPs. When multiple PUCCH messages are scheduled at overlapping times, the UE may benefit from multiplexing the two PUCCH messages together and transmitting the multiplexed PUCCH to a single TRP. In addition, when one or more of the two time-domain overlapping PUCCHs overlap with one or more PUSCHs, multiplexing the PUCCHs on the PUSCH may be beneficial.

[0034] PUCCH resources may be scheduled for a UE to send uplink control information (UCI). UCI may be of multiple types, including hybrid automatic repeat request acknowledgement (HARQ-Ack), channel state information (CSI) part 1, CSI part 2, and scheduling request (SR). UCI may be scheduled on PUCCH resources via a downlink control information (DCI) message transmitted from a TRP on a PDCCH.

[0035] A control resource set (CORESET) may indicate to the UE the resources for receiving a PDCCH message (e.g., DCI). Each CORESET may be configured with a value of a CORESET pool index (e.g., via a parameter CORESETPoolIndex). For example, CORESET ID 1 and CORESET ID 2 may be associated with CORESET pool index 0, and CORESET ID 3 and CORESETID 4 may be associated with CORESET pool index 1. In this way, the UE may identify which TRP is transmitting a message to the UE, since each CORESET pool index may be associated with a different TRP. Also associated with the CORESET pool index is a PUCCH resource pool. A PUCCH resource pool consists of multiple PUCCH resource sets, and a PUCCH resource set consists of multiple PUCCH resources. In some instances, a PUCCH resource set is determined based on the number of bits in the UCI to be sent on the resource. A PUCCH resource from a PUCCH resource set may be determined based on a PUCCH resource indicator (PRI) field in the DCI that schedules the PUCCH. However, when multiple PUCCHs are multiplexed, different rules may be defined for determining PUCCH resource pools, PUCCH resource sets, and PUCCH resources, as further described herein.

[0036] When multiple UCIs are scheduled for multiple TRPs, and one or more of the PUCCHs scheduled for the UCIs overlap with the PUSCH, the UCIs may be encoded, rate matched, and mapped to the PUSCH. In some aspects, UCIs of the same type and associated with different CORESET pool index values ​​may be cascaded and then jointly encoded, rate matched, and mapped. In other aspects, even UCIs of the same type and associated with different CORESET pool index values ​​may be individually encoded, rate matched, and mapped. In yet further aspects, whether to cascade the same type of UCI across different CORESET pool indexes may be based on UE configuration, such as radio resource control (RRC) configuration. Depending on UE capabilities, there may be a limit on the number of separate encoding / rate matching / mapping chains available at the same time. In this way, if there are more UCIs and / or cascaded UCIs to be encoded, rate matched, and mapped, the UCIs may be discarded.

[0037] When determining which PUCCH resource to use when two or more overlapping PUCCHs are concatenated together, the UE may use multiple different rules. When the PUCCH resource pool for each of the PUCCHs to be multiplexed is different, there may be a rule for determining the PUCCH resource pool. For example, the PUCCH resource pool may be determined based on a fixed CORESET pool index, or the PUCCH resource pool may be configured (e.g., via RRC). The PUCCH resource set may be selected from the PUCCH resource pool based on the total number of bits in all UCIs associated with two overlapping PUCCHs. The PUCCH resources from the PUCCH resource set may be determined based on the PRI field of the last DCI associated with the same CORESET pool index value as the determined PUCCH resource pool.

[0038] If the PUCCH resource pool for each of the two overlapping PUCCHs to be multiplexed is the same, the UE may use the PUCCH resource pool. A PUCCH resource set may be selected from a PUCCH resource pool based on the total number of bits in all UCIs associated with the two overlapping PUCCHs. The PUCCH resources from the PUCCH resource set may be determined based on a predetermined rule. One rule may be to select PUCCH resources based on the PRI field in the last DCI associated with a fixed CORESET pool index value (e.g., value 1) among the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH. Another rule may be to determine the PUCCH resources based on the PRI field in the last DCI indicating the lowest (or alternatively, the highest) PRI code point value among the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH.

[0039] Another rule may be to determine the PUCCH resources based on the PRI field in the last DCI among the first set of DCIs and the second set of DCIs (associated with both the first PUCCH and the second PUCCH). However, in some instances, the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH may be received in the same PDCCH monitoring opportunity. When this occurs, there may be a fallback rule for determining between the last two DCIs whose PRI value will be used to determine the PUCCH resources. The fallback rule may be a fallback rule based on, for example, a fixed CORESET pool index value, a highest / lowest PRI codepoint value, a highest / lowest CORESET ID, or a highest / lowest starting CCE index of the last DCI associated with each of the two overlapping PUCCHs, respectively.

[0040] The systems and methods described herein provide many advantages. By multiplexing PUCCH onto PUSCH, restrictions on simultaneous PUCCH and PUSCH transmissions can be broken, allowing more efficient communications. Multiplexing PUCCHs together can allow UCI scheduled for those PUCCHs to be transmitted together simultaneously in a single PUCCH resource. These efficiencies can reduce UE power consumption and use network resources more efficiently. In addition, by reusing existing coding / rate matching / mapping chains for different UCI types, existing UE hardware can be effectively adapted for use in the scenarios described herein.

[0041] Figure 1 A wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 may be a 5G network. The network 100 includes several base stations (BSs) 105 (respectively labeled 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities. The BS 105 may be a station that communicates with a UE 115 (respectively labeled 115a, 115b, 115c, 115d, 115e, 115f, 115g, 115h, and 115k), and may also be referred to as an evolved B node (eNB), a next generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the particular geographic coverage area of ​​the BS 105 and / or the BS subsystem serving the coverage area, depending on the context in which the term is used.

[0042] BS105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells), and / or other types of cells. Macro cells generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as femto cells) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1In the example shown, BS105d and 105e may be conventional macro BSs, while BS105a to 105c may be macro BSs with one of three-dimensional (3D), full-dimensional (FD) or massive MIMO capabilities. BS105a to 105c may utilize their higher dimensional MIMO capabilities to utilize 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS105f may be a small cell BS, which may be a home node or a portable access point. BS105 may support one or more (e.g., two, three, four, etc.) cells.

[0043] Network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0044] UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 may also be referred to as a terminal, a mobile station, a user unit, a station, etc. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 may be a device including a universal integrated circuit card (UICC). On the other hand, UE may be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC may also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a to 115d are examples of mobile smart phone type devices that access the network 100. UE 115 may also be a machine that is specifically configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). UEs 115e to 115h are examples of various machines configured for communication to access network 100. UEs 115i to 115k are examples of vehicles equipped with wireless communication devices configured for communication to access network 100. UE 115 may be able to communicate with any type of BS, whether macro BS, small cell, etc. Figure 1 , lightning (e.g., communication link) indicates wireless transmission between UE 115 and serving BS 105 (which is a BS designated to serve UE 115 on downlink (DL) and / or uplink (UL), desired transmission between BS 105, backhaul transmission between BSs, or sidelink transmission between UE 115.

[0045] In operation, BSs 105a to 105c may use 3D beamforming and cooperative spatial techniques such as coordinated multipoint (CoMP) or multiple connections to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BSs 105a to 105c and small cell BS 105f. Macro BS 105d may also transmit multicast services subscribed and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0046] The BSs 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communications with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., through the core network) over a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.

[0047] The network 100 may also support mission-critical communications using ultra-reliable and redundant links for mission-critical devices such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BS 105f. Other machine type devices such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) may communicate directly with BSs such as small cell BS 105f and macro BS 105e through the network 100, or communicate through the network in a multi-action size configuration by communicating with another user device such as UE 115f that communicates temperature measurement information to a smart meter (UE 115g), which then reports to the network through the small cell BS 105f, which relays its information to the network. The network 100 may also provide additional network efficiency through dynamic low latency TDD / FDD communications, such as V2V, V2X, C-V2X communications between UE 115i, 115j, or 115k and other UEs 115 and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j, or 115k and BS 105.

[0048] In some implementations, the network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system may divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, frequency modulations, frequency slots, etc. Each subcarrier may be modulated with data. In some aspects, the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system BW. The system BW may also be divided into subbands. In other aspects, the subcarrier spacing and / or the duration of the TTI may be scalable.

[0049] In some aspects, BS105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE 115 to BS105. The communication may be in the form of a radio frame. A radio frame may be divided into a plurality of subframes or time slots, for example, about 10. Each time slot may also be divided into micro-time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subframe subset (e.g., a DL subframe) in a radio frame may be used for DL ​​transmission, and another subframe subset (e.g., an UL subframe) in a radio frame may be used for UL transmission.

[0050] DL subframes and UL subframes may be further divided into several zones. For example, each DL or UL subframe may have a predefined zone for the transmission of reference signals, control information, and data. Reference signals are predetermined signals that facilitate communication between BS105 and UE 115. For example, a reference signal may have a specific pilot pattern or structure, wherein a pilot tone may span an operational BW or frequency band, and each pilot tone may be positioned at a predefined time and a predefined frequency. For example, BS105 may send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate a DL channel. Similarly, UE 115 may send a sounding reference signal (SRS) to enable BS105 to estimate an UL channel. Control information may include resource assignments and protocol controls. Data may include protocol data and / or operational data. In some aspects, BS105 and UE115 may communicate using self-contained subframes. Self-contained subframes may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL ​​communications than for UL communications. A UL-centric subframe may include a longer duration for UL communications than for UL communications.

[0051] In some aspects, network 100 may be an NR network deployed on a licensed spectrum. BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS 105 may broadcast system information associated with network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some aspects, BS 105 may broadcast PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB), and may broadcast RMSI and / or OSI on a physical downlink shared channel (PDSCH). MIB may be sent on a physical broadcast channel (PBCH).

[0052] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with the physical layer identification value to identify a cell. The PSS and SSS may be located in the center portion of a carrier or at any suitable frequency within a carrier.

[0053] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS.

[0054] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL authorization, a temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105 and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access process may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.

[0055] After establishing the connection, UE 115 and BS 105 may enter a normal operation phase, in which operation data may be exchanged. For example, BS 105 may schedule UE 115 for UL and / or DL ​​communications. BS 105 may send UL and / or DL ​​scheduling grants to UE 115 via PDCCH. Scheduling grants may be sent in the form of DL control information (DCI). BS 105 may send DL communication signals (e.g., carrying data) to UE 115 via PDSCH according to the DL scheduling grant. UE 115 may send UL communication signals to BS 105 via PUSCH and / or PUCCH according to the UL scheduling grant. The connection may be referred to as an RRC connection. When UE 115 actively exchanges data with BS 105, UE 115 is in an RRC connection state.

[0056] In an example, after establishing a connection with BS105, UE 115 may initiate an initial network attachment procedure with network 100. BS105 may coordinate with various network entities or fifth generation core (5GC) entities, such as access and mobility function (AMF), serving gateway (SGW) and / or packet data network gateway (PGW) to complete the network attachment procedure. For example, BS105 may coordinate with network entities in 5GC to identify UE, authenticate UE and / or authorize UE to transmit and / or receive data in network 100. In addition, AMF may assign a set of tracking areas (TAs) to UE. Once the network attachment procedure is successful, a context is established in AMF for UE 115. After successfully attaching to the network, UE 115 may move around the current TA. For tracking area update (TAU), BS105 may request UE 115 to periodically update network 100 with the location of UE 115. Alternatively, UE 115 may report the location of UE 115 to network 100 only when entering a new TA. The TAU allows the network 100 to quickly locate and page the UE 115 when an incoming data packet or call for the UE 115 is received.

[0057] UE 115 may have the ability to communicate with multiple network elements such as transmit receive points (TRPs), where each TRP may act as a wireless connection point between UE 115 and another network element such as BS 105. Communication methods such as multiplexing PUCCH messages with UCI may be extended to be used by UE 115 across multiple TRPs. When multiple PUCCH messages are scheduled at overlapping times, UE 115 may benefit from multiplexing the two PUCCH messages together and transmitting the multiplexed PUCCH to a single TRP. In addition, when one or more of the two time-domain overlapping PUCCHs overlap with one or more PUSCHs, multiplexing the PUCCHs on the PUSCH may be beneficial.

[0058] PUCCH resources may be scheduled for UE 115 to send UCI. UCI may be of multiple types, including HARQ-Ack, CSI part 1, CSI part 2, and SR. UCI may be scheduled on PUCCH resources via a DCI message transmitted from a TRP on a PDCCH.

[0059] A control resource set (CORESET) may indicate to the UE 115 the resources for receiving a PDCCH message (e.g., DCI). Each CORESET may be configured with a value of a CORESET pool index (e.g., via a parameter CORESETPoolIndex). For example, CORESET ID 1 and CORESET ID 2 may be associated with CORESET pool index 0, and CORESET ID 3 and CORESETID 4 may be associated with CORESET pool index 1. In this way, the UE 115 may identify which TRP is transmitting a message to the UE 115, since each CORESET pool index may be associated with a different TRP. Also associated with the CORESET pool index is a PUCCH resource pool. A PUCCH resource pool consists of a plurality of PUCCH resource sets, and a PUCCH resource set consists of a plurality of PUCCH resources. In some instances, a PUCCH resource set is determined based on the number of bits in the UCI to be sent on the resource. A PUCCH resource from a PUCCH resource set may be determined based on a PUCCH resource indicator (PRI) field in the DCI that schedules the PUCCH. However, when multiple PUCCHs are multiplexed, different rules may be defined for determining PUCCH resource pools, PUCCH resource sets, and PUCCH resources, as further described herein.

[0060] When multiple UCIs are scheduled for multiple TRPs, and one or more of the PUCCHs scheduled for the UCIs overlap with the PUSCH, the UCIs may be encoded, rate matched, and mapped to the PUSCH. In some aspects, UCIs of the same type and associated with different CORESET pool index values ​​may be concatenated and then jointly encoded, rate matched, and mapped. In other aspects, even UCIs of the same type and associated with different CORESET pool index values ​​may be individually encoded, rate matched, and mapped. In yet further aspects, whether to concatenate the same type of UCI across different CORESET pool index values ​​may be based on UE 115 configuration, such as radio resource control (RRC) configuration. Depending on the UE 115 capabilities, there may be a limit on the number of separate encoding / rate matching / mapping chains available at the same time. In this way, if there are more UCIs and / or concatenated UCIs to be encoded, rate matched, and mapped, the UCIs may be discarded.

[0061] In some aspects, BS105 may communicate with UE 115 using HARQ technology to improve communication reliability, for example, to provide URLLC services. BS105 may schedule UE 115 to perform PDSCH communication by sending DL grant in PDCCH. BS105 may send DL data packets to UE 115 according to the scheduling in PDSCH. DL data packets may be sent in the form of transport blocks (TBs). If UE 115 successfully receives the DL data packet, UE 115 may send HARQ ACK to BS105. On the contrary, if UE115 fails to successfully receive the DL transmission, UE 115 may send HARQ NACK to BS105. Upon receiving HARQ NACK from UE 115, BS105 may retransmit the DL data packet to UE 115. The retransmission may include a decoded version of the DL data that is the same as the initial transmission. Alternatively, the retransmission may include a decoded version of the DL data that is different from the initial transmission. The UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. The BS 105 and the UE 115 may also apply HARQ to UL communications using a substantially similar mechanism as DL HARQ.

[0062] In some aspects, the network 100 may operate on a system BW or a component carrier (CC) BW. The network 100 may divide the system BW into multiple BWPs (e.g., parts). The BS 105 may dynamically assign the UE 115 to operate on a specific BWP (e.g., a specific part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP to find signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL ​​communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within the CC to the UE 115 for UL and DL communications. For example, the BWP pair may include a BWP for UL communication and a BWP for DL ​​communication.

[0063] In some aspects, network 100 may operate on a shared channel, which may include a shared frequency band and / or an unlicensed frequency band. For example, network 100 may be an NR-U network operating on an unlicensed frequency band. In such aspects, BS105 and UE115 may be operated by multiple network operation entities. In order to avoid conflicts, BS105 and UE 115 may use a listen-before-talk (LBT) procedure to monitor a transmit opportunity (TXOP) in a shared channel. TXOP may also be referred to as COT. The goal of LBT is to protect the reception at the receiver from interference. For example, a transmitting node (e.g., BS105 or UE 115) may perform LBT before transmitting in a channel. When LBT passes, the transmitting node may continue to transmit. When LBT fails, the transmitting node may prohibit transmitting in a channel.

[0064] LBT can be based on energy detection (ED) or signal detection. For LBT based on energy detection, when the signal energy measured from the channel is lower than a threshold, the result of LBT is passed. Conversely, when the signal energy measured from the channel exceeds a threshold, the LBT result is a fault. For LBT based on signal detection, when a channel reservation signal (e.g., a predetermined preamble signal) is not detected in the channel, the LBT result is passed. In addition, LBT can be in multiple modes. The LBT mode can be, for example, type 4 (CAT4) LBT, type 2 (CAT2) LBT, or type 1 (CAT1) LBT. CAT1 LBT is referred to as a no-LBT mode, in which no LBT is performed before sending. CAT2 LBT refers to LBT without a random backoff period. For example, a transmitting node can determine a channel measurement in a time interval and determine whether the channel is available based on a comparison of the channel measurement with an ED threshold. CAT4 LBT refers to an LBT with a random backoff and a variable contention window (CW). For example, the sending node may draw a random number and back off for a duration in a certain time unit based on the drawn random number.

[0065] The deployment of a communication system (such as a 5G new radio (NR) system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a network element, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS) or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS 105 (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit and receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0066] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0067] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0068] Figure 2 A diagram illustrating an example decomposed base station 200 architecture is shown. The decomposed base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 115 via one or more radio frequency (RF) access links. In some implementations, a UE 115 may be served simultaneously by multiple RUs 240.

[0069] Each of the units (i.e., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0070] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 210. CU210 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0071] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0072] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 115. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0073] The SMO framework 205 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

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

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

[0076] Figure 3 A diagram of a system 300 including a device 305 supporting RU sharing techniques in wireless communications according to various aspects of the present disclosure is shown. The device 305 can communicate with one or more RUs 355. The device 305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 320, a network communication manager 310, a memory 330, a code 335, a processor 340, and a RU communication manager 345. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 350). One or more of the components of the system 300 may perform as described herein with reference to Figures 4 to 15 The functions described are, for example, described as functions performed by a base station or a network element.

[0077] The network communications manager 310 may manage communications with the core network 360 (eg, via one or more wired backhaul links). For example, the network communications manager 310 may manage the transfer of data communications for client devices such as one or more UEs 115.

[0078] Memory 330 may include RAM and ROM. Memory 330 may store computer-readable, computer-executable code 335 including instructions that, when executed by processor 340, cause device 305 to perform various functions described herein. Code 335 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 335 may not be directly executable by processor 340, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 330 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0079] The processor 340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 340. The processor 340 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 330) to enable the device 305 to perform various functions (e.g., functions or tasks that support RU sharing technology in wireless communications). For example, the device 305 or a component of the device 305 may include a processor 340 and a memory 330 coupled to the processor 340, and the processor 340 and the memory 330 are configured to perform the various functions described herein.

[0080] RU communication manager 345 may manage communications with RU 355 and may include a controller or scheduler for controlling communications with UE 115 in coordination with RU 355. For example, RU communication manager 345 may coordinate scheduling of transmissions to UE 115. In some examples, RU communication manager 345 may provide an F1 interface within a wireless communication network technology to provide communications with RU 355.

[0081] According to examples as disclosed herein, the communication manager 320 may support wireless communications at a network node. For example, the communication manager 320 may be configured to or otherwise support a component for sending a request for a radio resource configuration to a first RU during a first time period. The communication manager 320 may be configured to or otherwise support a component for sending an interference query associated with the radio resource configuration to a second RU during a first time period. The communication manager 320 may be configured to or otherwise support a component for receiving a response to the interference query from the second RU. The communication manager 320 may be configured to or otherwise support a component for sending a payload to the first RU for transmission during the first time period based on the response to the interference query.

[0082] By including or configuring the communication manager 320 according to the examples described herein, the device 305 can support technology for RU sharing, in which DUs of different MNOs can access wireless resources of other MNOs, which can increase the efficiency of resource utilization while providing competition and innovation among different MNOs, which can increase the reliability of wireless communications, reduce latency, and enhance user experience.

[0083] In some examples, the communication manager 320 may be configured to perform various operations (e.g., receive, monitor, send) using or otherwise cooperating with other components. Although the communication manager 320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 320 may be supported or performed by the processor 340, the memory 330, the code 335, or any combination thereof. For example, the code 335 may include instructions that can be executed by the processor 340 to cause the device 305 to perform various aspects of the RU sharing technology in wireless communications as described herein, or the processor 340 and the memory 330 may be otherwise configured to perform or support such operations.

[0084] Figure 4 4. An example wireless communication network according to some aspects of the present disclosure is illustrated. As shown, UE 115 communicates with network element 105 via communication channel 410. UE 115 also communicates with network element 105b via communication channel 420. Figures 5 to 15 As further discussed, UE 115 may receive messages requesting UCI from multiple network elements, such as network elements 105a and 105b. When UCI is scheduled using overlapping PUCCH and / or overlapping PUSCH, the UCI may be based on the information in the referenced Figure 13 to Figure 14 The predetermined rules described multiplex them onto a single PUCCH or PUSCH resource.

[0085] Figure 5 An example resource diagram according to some aspects of the present disclosure is illustrated. The horizontal axis represents time in some units, and the boxes represent communication resources scheduled between the UE and the network element. In this example, PUCCH resources 505 and 510 are scheduled at overlapping times. PUCCH 505 and 510 are each associated with a different network element (e.g., TRP). PUSCH 515 also overlaps with both PUCCH resources 505 and 510 in time and can be associated with one of the same network elements as the network element of PUCCH 505 or 510. PUCCH 505 is scheduled to send UCI1 of HARQ-Ack UCI type. PUCCH 510 is scheduled to send UCI2, which is also a HARQ-Ack UCI type. UE 115 can multiplex UCI1 and UCI2 on PUSCH 515, resulting in PUSCH 520 containing UCI1 and UCI2 as shown. In this way, the UE can send UCI even in cases where simultaneous PUCCH and PUSCH transmission is not allowed. Fig.13 Multiplexing of PUCCH on PUSCH across different network elements is discussed in more detail.

[0086] Figure 6An example resource diagram according to some aspects of the present disclosure is illustrated. The horizontal axis represents time in some units, and the boxes represent communication resources scheduled between the UE and the network element. In this example, PUCCH resources 605 and 610 are scheduled at overlapping times. PUCCH 605 and 610 are each associated with a different network element (e.g., TRP). PUCCH 605 is scheduled to send UCI1, which is a HARQ-Ack UCI type. PUCCH 610 is scheduled to send UCI2, which is also a HARQ-Ack UCI type. UE 115 can multiplex UCI1 and UCI2 on PUCCH 620. PUCCH 620 can be a different resource than PUCCH 605 or PUCCH 610. Reference Fig.14 Multiplexing of PUCCH across different network elements is discussed in more detail.

[0087] Figure 7 An example process flow diagram 700 is illustrated in accordance with some aspects of the present disclosure. Diagram 700 represents a process within UE 115 for multiplexing UCI on PUSCH. Figure 7 In the example of , a particular type of UCI (e.g., HARQ-Ack) associated with a first network unit and the same type of UCI associated with a second network unit are concatenated by a concatenation block 705. If UCI1 contains X bits and UCI2 contains Y bits, the concatenation results in a total of X+Y bits. CSI part 1 does not have a corresponding UCI associated with another network unit to be concatenated, so it is processed separately. The concatenated UCI1 and UCI2 are jointly encoded and rate matched by a channel decoding and rate matching block 710a. The concatenated UCI1 and UCI2 are then mapped to the PUSCH by a resource mapping block 715a. CSI part 1 is channel decoded and rate matched by a channel decoding and rate matching block 710b, respectively, and then resource mapped to the PUSCH by a resource mapping block 715b.

[0088] Figure 8 An example process flow diagram 800 is illustrated in accordance with some aspects of the present disclosure. Diagram 800 represents a process within UE 115 for multiplexing UCI on PUSCH. Figure 8In the example of , the UE is determined to multiplex four UCIs of different types (two HARQ-Acks, CSI part 1, and CSI part 2) to the PUSCH. In this example, the HARQ-Acks associated with different CORESET pool index values ​​are considered to be different UCI types. Each of the UCIs is channel decoded, rate matched, and mapped separately. Based on UE capabilities, there may be only a limited number of processing chains (e.g., 3 chains) in which excess UCIs may be discarded. In this example, CSI part 2 is discarded. The UCIs may be sorted based on priority rules so that the highest priority UCI is not discarded before the lower priority UCIs. In this example, the HARQ-Ack associated with the first CORESET pool index is considered to be a HARQ-Ack, the HARQ-Ack associated with the second CORESET pool index is considered to be a CSI part 1, and the CSI part 1 is considered to be a CSI part 2. Therefore, HARQ-Ack1 is encoded and rate matched by the channel decoding and rate matching block 810a, and then mapped to the PUSCH by the resource mapping block 815a. HARQ-Ack2 is encoded and rate matched by channel decoding and rate matching block 810b and then mapped to PUSCH by resource mapping block 815b. CSI part 1 is encoded and rate matched by channel decoding and rate matching block 810c and then mapped to PUSCH by resource mapping block 815c. CSI part 2 is discarded.

[0089] Fig. 9 An example process flow diagram 900 is illustrated in accordance with some aspects of the present disclosure. Diagram 900 represents a process within UE 115 for multiplexing UCI on PUSCH. Fig. 9 In the example of FIG. 1 , the UE is scheduled to send four UCIs of different types (two HARQ-Acks, CSI Part 1, and CSI Part 2). Each of the UCIs is channel decoded, rate matched, and mapped separately. In this example, the UE has the ability to process more than three UCIs individually, so CSI Part 2 may not be as Figure 8. The order of UCI mapping is defined as follows: the HARQ-Ack associated with the first CORESET pool index is higher than the HARQ-Ack associated with the second CORESET pool index, then the CSI part 1 associated with the first CORESET pool index, then the CSI part 1 associated with the second CORESET pool index, then the CSI part 2 associated with the first CORESET pool index, and then the CSI part 2 associated with the second CORESET pool index. For CSI part 1 and CSI part 2, if no association with the CORESET pool index is configured, the default CORESET pool index is assumed, such as the CORESET pool index value 0. In this example, HARQ-Ack1 is encoded and rate matched by the channel decoding and rate matching block 910a, and then mapped to PUSCH by the resource mapping block 915a. HARQ-Ack2 is encoded and rate matched by the channel decoding and rate matching block 910b, and then mapped to PUSCH by the resource mapping block 915b. CSI part 1 is encoded and rate matched by channel decoding and rate matching block 910c and then mapped to PUSCH by resource mapping block 915c. CSI part 2 is encoded and rate matched by channel decoding and rate matching block 910d and then mapped to PUSCH by resource mapping block 915d.

[0090] Fig.10 is a signaling diagram 1000 according to some aspects of the present disclosure. Diagram 1000 is represented by a signaling diagram such as reference Figure 1 BS105 discussed and referenced Figures 2 to 3 The network units 1100a and 1100b discussed above may be used with one or more components (e.g., CU 210, DU 230, and / or RU 240) of the decomposed base station 200. The network units 1100a and 1100b may utilize one or more components, such as Fig.11 1104, a UCI module 1108, a transceiver 1110, a modem 1112, and one or more antennas 1116. The UE 115 may utilize one or more components such as Fig.12 The processor 1202, memory 1204, multiplexing module 1208, transceiver 1210, modem 1212 and one or more antennas 1216 are shown. As shown, the signaling diagram 1000 includes a plurality of enumerated actions, but Fig.10 The various aspects of the invention may include additional actions before, after, and between the actions listed. In some aspects, one or more of the actions listed may be omitted, combined together, or performed in a different order.

[0091] At action 1002, the network element 1100a sends a processing configuration to the UE 115. The processing configuration may indicate, for example, whether to process the same type of UCI associated with different CORESET pool index values ​​jointly or individually.

[0092] At action 1004, the network element 1100a sends multiple DCI messages to the UE 115. The DCIs may have associated with them a PRI field indicating PUCCH resources. The DCIs may request UCI from the UE 115 of different UCI types.

[0093] At action 1006, network element 1100b also sends multiple DCI messages to UE 115. The DCIs may have PRI fields associated with them indicating PUCCH resources that may overlap with the PUCCH resources indicated by the DCI sent by network element 1100a. The DCIs may request UCI from UE 115 of different UCI types.

[0094] At action 1008, the network element 1100a sends a PUSCH configuration to the UE 115. The PUSCH configuration may be transmitted dynamically (eg, via DCI) or semi-statically (eg, via a configured grant). The PUSCH resources may overlap in time with one or more of the scheduled PUCCH resources.

[0095] At action 1010, the UE 115 determines overlapping resources. For example, one or more PUCCH resources scheduled at actions 1004 and 1006 may overlap, and one or more of these PUCCH resources may overlap with the PUSCH resources configured at action 1008. If it is determined by the UE that there is no overlap, the UE may send data using the resources as originally scheduled.

[0096] At action 1012, the UE 115 may concatenate UCI with overlapping PUCCH resources associated with different network elements 1100. In some aspects, UCI of the same type is concatenated, as described in reference to Figure 7 In some aspects, UCI is not cascaded but processed individually. Depending on the UE capabilities, it may be necessary to discard UCI, in which case the UCI may be discarded as described in reference Figure 8 Discard them in the order of priority discussed.

[0097] At action 1014, the UCI is multiplexed by the UE 115 to the PUCCH or PUSCH if the PUSCH overlaps one or more of the PUCCH resources.

[0098] At action 1016, the network unit 1100a receives a PUCCH or a PUSCH from the UE 115. The PUCCH or PUSCH may include all or a subset of the UCI requested in the DCI message.

[0099] Fig.11 1 is a block diagram of an exemplary network unit 1100 according to some aspects of the present disclosure. The network unit 1100 may be as follows: Figure 1 as discussed in BS105, or as referenced by Figures 2 to 3 The network unit 1100 may be a transmit and receive point (TRP). As shown, the network unit 1100 may include a processor 1102, a memory 1104, a UCI module 1108, a transceiver 1110 including a modem subsystem 1112 and an RF unit 1114, and one or more antennas 1116. These elements may be coupled to each other. The term "coupled" may refer to direct or indirect coupling or connection to one or more intermediate elements. For example, these elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0100] The processor 1102 may have various features as a particular type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1102 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0101] The memory 1104 may include cache memory (e.g., cache memory of the processor 1102), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and nonvolatile memory, or a combination of different types of memory. In some aspects, the memory 1104 may include a non-transitory computer-readable medium. The memory 1104 may store instructions 1106. The instructions 1106 may include instructions that, when executed by the processor 1102, cause the processor 1102 to perform the operations described herein (e.g., Figures 4 to 10 and Figures 13 to 15Instructions 1106 may also be referred to as program code. Program code may be used to cause the wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 1102) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0102] The UCI module 1108 may be implemented by hardware, software, or a combination thereof. For example, the UCI module 1108 may be implemented as a processor, circuit, and / or instruction 1106 stored in the memory 1104 and executed by the processor 1102. In some examples, the UCI module 1108 may be integrated within the modem subsystem 1112. For example, the UCI module 1108 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuit systems) within the modem subsystem 1112. The UCI module 1108 may communicate with one or more components of the network unit 1100 to implement various aspects of the present disclosure, such as, Figures 4 to 10 as well as Figures 13 to 15 all aspects.

[0103] In some aspects, the UCI module 1108 may be configured to receive a rank indicator (RI) from the UE. The RI may be received as part of the channel state feedback information. The channel state feedback may be received, for example, via an RRC message, an UL MAC CE, a channel state information (CSI) message, a synchronization signal block (SSB), or other suitable communication using a PUCCH, a PSCCH, or another suitable channel. The channel state feedback information may include a precoding matrix indicator (PMI) and / or a channel quality indicator (CQI) corresponding to the RI. The RI may define the number of possible transmission layers for downlink transmission under specific channel conditions. The RI may correspond to the maximum number of unrelated paths that can be used for downlink transmission. However, the RI may not contain information directly related to the number of antenna panels or modules used by the UE when implementing the indicated RI.

[0104] The UCI module 1108 may be configured to request different types of UCI from the UE. The UCI request may be sent via the PDCCH in a DCI message indicating PUCCH resources. The UCI module 1108 may receive UCI from the UE multiplexed onto a single PUCCH or PUSCH message.

[0105] As shown, the transceiver 1110 may include a modem subsystem 1112 and an RF unit 1114. The transceiver 1110 may be configured to communicate bidirectionally with other devices (such as UE 115 and / or BS 105 and / or another core network element). The modem subsystem 1112 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). The RF unit 1114 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., PDCCH DCI, RRC, etc.) from the modem subsystem 1112 (for outbound transmission) or from another source (such as UE 115 and / or UE 1200). The RF unit 1114 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 1110, the modem subsystem 1112 and / or the RF unit 1114 may be separate devices that are coupled together at the network unit 1100 to enable the network unit 1100 to communicate with other devices.

[0106] The RF unit 1114 may provide modulated and / or processed data (e.g., a data packet (or more generally, a data message that may include one or more data packets and other information)) to the antenna 1116 for transmission to one or more other devices. The antenna 1116 may also receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 1110. The transceiver 1110 may provide the demodulated and decoded data (e.g., PUCCH, PUSCH, etc.) to the UCI module 1108 for processing. The antenna 1116 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0107] In one aspect, the network unit 1100 may include multiple transceivers 1110 that implement different RATs (e.g., NR and LTE). In one aspect, the network unit 1100 may include a single transceiver 1110 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1110 may include various components, where different combinations of components may implement different RATs.

[0108] Fig.12 1 is a block diagram of an exemplary UE 1200 according to some aspects of the present disclosure. The UE 1200 may be Figures 1 to 4115 discussed in . As shown, UE 1200 may include a processor 1202, a memory 1204, a multiplexing module 1208, a transceiver 1210 including a modem subsystem 1212 and a radio frequency (RF) unit 1214, and one or more antennas 1216. These elements may be coupled to each other. The term "coupled" may refer to being directly or indirectly coupled or connected to one or more intervening elements. For example, these elements may communicate directly or indirectly with each other, such as via one or more buses.

[0109] The processor 1202 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1202 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0110] The memory 1204 may include cache memory (e.g., cache memory of the processor 1202), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, the memory 1204 includes a non-transitory computer-readable medium. The memory 1204 may store or have recorded thereon instructions 1206. The instructions 1206 may include instructions that, when executed by the processor 1202, cause the processor 1202 to perform various aspects of the present disclosure described herein with reference to the UE 115 (e.g., Figures 4 to 10 and Figure 13 to Figure 14 Instructions 1206 may also be referred to as codes, which may be broadly interpreted to include any type of computer-readable statements.

[0111] The multiplexing module 1208 may be implemented via hardware, software, or a combination thereof. For example, the multiplexing module 1208 may be implemented as a processor, circuit, and / or instruction 1206 stored in the memory 1204 and executed by the processor 1202. In some aspects, the multiplexing module 1208 may be integrated within the modem subsystem 1212. For example, the multiplexing module 1208 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuit systems) within the modem subsystem 1212. The multiplexing module 1208 may communicate with one or more components of the UE 1200 to implement various aspects of the present disclosure, such as, Figures 4 to 10 as well as Figure 13 to Figure 14 all aspects.

[0112] In some aspects, the multiplexing module 1208 may be configured to multiplex the PUCCH message with the UCI having overlapping PUCCH or PUSCH. PUCCH resources may be scheduled for the UE 1200 to send the UCI. The CORESET may indicate to the multiplexing module 1208 the resources for receiving the PDCCH message (e.g., DCI). Each CORESET may be configured with a value of a CORESET pool index (e.g., via a parameter CORESETPoolIndex). For example, CORESET ID 1 and CORESET ID 2 may be associated with CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be associated with CORESET pool index 1. In this way, the multiplexing module 1208 may identify which TRP is transmitting the message to the UE 1200, because each CORESET pool index may be associated with a different TRP. Also associated with the CORESET pool index is a PUCCH resource pool. A PUCCH resource pool consists of multiple PUCCH resource sets, and a PUCCH resource set consists of multiple PUCCH resources. In some examples, the PUCCH resource set is determined by the multiplexing module 1208 based on the number of bits in the UCI to be sent on the resource. The PUCCH resources from the resource set can be determined based on the PUCCH resource indicator (PRI) field in the DCI that schedules the PUCCH. However, when multiple PUCCHs are multiplexed, the multiplexing module 1208 can implement different rules for determining the PUCCH resource pool, PUCCH resource set, and PUCCH resources, as described herein with reference to Figures 4 to 10 as well as Figure 13 to Figure 14 Based on the determined resources for transmitting the UCI, the multiplexing module 1208 can encode the UCI, rate match, and map the UCI to the determined resources.

[0113] As shown, the transceiver 1210 may include a modem subsystem 1212 and an RF unit 1214. The transceiver 1210 may be configured to communicate bidirectionally with other devices, such as BSs 105 and 500. The modem subsystem 1212 may be configured to modulate and / or encode data from the memory 1204 and / or the multiplexing module 1208 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). The RF unit 1214 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., PDCCH, PUSCH, etc.) or modulated / encoded data transmitted from another source, such as a UE 115 or a BS 105. The RF unit 1214 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 1210, the modem subsystem 1212 and the RF unit 1214 may be separate devices that are coupled together at the UE 1200 to enable the UE 1200 to communicate with other devices.

[0114] The RF unit 1214 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 1216 for transmission to one or more other devices. The antenna 1216 may further receive data messages sent from other devices. The antenna 1216 may provide the received data messages for processing and / or demodulation at the transceiver 1210. The transceiver 1210 may provide the demodulated and decoded data (e.g., PDCCH DCI, RRC, etc.) to the multiplexing module 1208 for processing. The antenna 1216 may include multiple antennas of similar or different designs to maintain multiple transmission links. The antenna 1216 may include multiple antenna modules, each antenna module being associated with a different antenna panel. The antenna panel can be used to transmit and / or receive using beamforming techniques.

[0115] In one aspect, the UE 1200 may include multiple transceivers 1210 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 1200 may include a single transceiver 1210 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1210 may include various components, where different combinations of components may implement different RATs.

[0116] Fig.131300 is a flowchart illustrating a wireless communication method 1300 according to some aspects of the present disclosure. Various aspects of the method 1300 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing blocks. In one aspect, the UE 115 or 1200 may utilize a processor such as Fig.12 The components of the processor 1202 , memory 1204 , multiplexing module 1208 , transceiver 1210 , modem 1212 , and one or more antennas 1216 are shown to perform the method 1300 .

[0117] As shown, method 1300 includes a plurality of enumerated blocks, but various aspects of method 1300 may include additional blocks before, after, and between these enumerated blocks. In some aspects, one or more of the enumerated blocks may be omitted or performed in a different order.

[0118] At block 1305, a UE (e.g., UE 115, UE 1200, or other UE) determines that a first PUCCH resource including a first set of UCI associated with a first CORESET pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value. Each of the PUCCH resources may be associated with UE communications with a different network element (e.g., TRP). The UE may determine that a different network element is associated with each PUCCH based on a first CORESET pool index value and a second CORESET pool index value that are different from each other. In some examples, the CORESET pool index may have a value of 0 or 1, each value being associated with a different group of CORESETs. Each CORESET group defined by the CORESET pool index may be associated with a different network element. When the UE receives DCI in a monitoring period based on a CORESET associated with the first CORESET pool index, the UE may determine that the DCI is associated with a different network element than the DCI received using a CORESET with a different CORESET pool index. The CORESET pool index of the CORESET that received the DCI may be used for different purposes, such as for HARQ-Ack feedback.

[0119] The first group of UCI and the second group of UCI may include different types of UCI. For example, the UCI types may include HARQ-Ack, CSI (CSI part 1 and CSI part 2), SR, and any combination thereof. Grouping the UCI into a first PUCCH and a second PUCCH may be a result of a previous step involving resolving overlapping PUCCH resources scheduled via DCI. For example, a group of DCI messages from different TRPs or RRC messages may each schedule different UCIs of corresponding UCI types. The UE may determine that some of the PUCCH resources of the UCI overlap, and may multiplex those UCIs such that the first PUCCH resources include the first group of UCI and the second PUCCH resources include the second group of UCI.

[0120] At block 1310, the UE receives a scheduling configuration for a physical uplink shared channel (PUSCH) that overlaps in time with at least one of a first PUCCH or a second PUCCH. The scheduling configuration may be received from a network element associated with the first PUCCH or the second PUCCH. The PUSCH may be dynamically scheduled (e.g., via a DCI), or may be semi-statically scheduled (e.g., via a configured grant). When semi-statically configured, reception of the PUSCH configuration may occur long before other actions performed in method 1300. The UE may not support simultaneous transmission of PUSCH and PUCCH, so the overlap of PUSCH and PUCCH in time may be addressed as follows.

[0121] At decision block 1315, the UE determines whether to jointly process (code / rate match / map) the same type of UCI associated with different CORESET pool index values. In some aspects, the UE 115 does not actively make the decision because the decision whether to cascade is based on standard rules that the UE is configured to always follow. In some aspects, a configuration (e.g., received via RRC) can be used to determine whether to jointly code / rate match / map the same type of UCI associated with different CORESET pool index values. If the UE determines to cascade, the method 1300 proceeds to block 1320, otherwise the method 1300 proceeds to block 1335.

[0122] At block 1320, the UE concatenates UCI from the first set of UCI and the second set of UCI of the same type, resulting in concatenated UCI. The concatenation may be based on an ascending or descending order of the associated CORESET pool index values. For example, UCI associated with a lower relative CORESET pool index value may be included in the concatenated UCI before UCI associated with a higher relative CORESET pool index.

[0123] At block 1325, the UE performs coding and rate matching on the concatenated UCIs together. Different types of UCIs may be coded and rate matched separately. The coding and rate matching of block 1325 may be performed, for example, as described in reference Figure 7 Execution as described.

[0124] At block 1330, the UE maps the concatenated UCI jointly on the PUSCH. The individually coded and rate matched UCI may be individually mapped on the PUSCH.

[0125] At block 1335, when the UE determines not to commonly encode / rate match / map UCI of the same type associated with different CORESET pool index values, the UE encodes and rate matches UCI from the first set of UCI and the second set of UCI separately. This may be done without considering the relative UCI type of each UCI, for example, as described in reference Figures 8 to 9 As discussed. The UE may use the existing coding / rate matching / mapping chain for HARQ-Ack, CSI part 1, and CSI part 2 while changing the inputs as needed. For example, rate matching is performed on a first hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with a first CORESET pool index value by treating the first HARQ-ACK as a HARQ-ACK, rate matching is performed on a second HARQ ACK associated with a second CORESET pool index value by treating the second HARQ-ACK as CSI part 1, and rate matching is performed on CSI part 1 by treating CSI part 2.

[0126] At block 1340, the UE discards the UCI after the first three UCIs according to the priority order. The UE may only have the capability of three processing chains, thereby allowing only three separate UCIs to be coded, rate matched, and mapped simultaneously. In the above example, CSI part 2 may be discarded as two HARQ-Acks, and CSI part 1 utilizes three existing chains. Some UEs may have the capability to process more or less UCIs. If more concurrent processing chains are available to the UE, then additional UCIs may not be discarded, as shown in reference Fig. 9 As discussed. When discarding UCI, which UCI is discarded is determined based on a priority order. For example, HARQ-Ack and / or SR may have the highest priority, followed by CSI part 1, and then CSI part 2. When there are two UCIs of the same type associated with different CORESET pool indices, which of the two UCIs gets priority may be based on a predetermined CORESET pool index. If a UCI such as CSI part 1 or 2 is not associated with a CORESET pool index, a default CORESET pool index may be assumed for the purpose of determining the priority order.

[0127] At block 1345, the UE maps the remaining (ie, non-discarded) UCI ​​separately on the PUSCH.

[0128] Fig.14 1400 is a flowchart illustrating a wireless communication method 1400 according to some aspects of the present disclosure. Various aspects of the method 1400 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing blocks. In one aspect, the UE 115 or 1200 may utilize a processor such as Fig.12 The components of processor 1202 , memory 1204 , multiplexing module 1208 , transceiver 1210 , modem 1212 , and one or more antennas 1216 are shown to perform method 1400 .

[0129] As shown, method 1400 includes a plurality of enumerated blocks, but various aspects of method 1400 may include additional blocks before, after, and between these enumerated blocks. In some aspects, one or more of the enumerated blocks may be omitted or performed in a different order.

[0130] At block 1405, a UE (e.g., UE 115, UE 1200, or other UE) receives DCI requesting UCI, the DCI including a PRI field indicating PUCCH resources. The DCI may be received from different network elements (e.g., TRPs). The UE may determine that the DCI is from different network elements based on receiving DCI associated with CORESETs having different CORESET pool indices.

[0131] At box 1410, the UE determines that a first PUCCH resource including a first group of UCI associated with a first CORESET pool index value overlaps in the time domain with a second PUCCH resource including a second group of UCI associated with a second CORESET pool index value. The first group of UCI and the second group of UCI may include different types of UCI. The UCI type may include HARQ-Ack, CSI (CSI part 1 and CSI part 2), SR, and any combination thereof. Grouping the UCI into a first PUCCH and a second PUCCH may be a result of a previous step involving resolving overlapping PUCCH resources scheduled via DCI. For example, a group of DCI messages from different TRPs may each schedule different UCIs of corresponding UCI types. The UE may determine that some of the PUCCH resources of the UCI overlap, and may multiplex those UCIs so that the first PUCCH resource includes the first group of UCI and the second PUCCH resource includes the second group of UCI.

[0132] At decision block 1415, the UE determines whether the PUCCH resource pool associated with the first CORESET pool index is the same as the PUCCH resource pool associated with the second CORESET pool index. For example, the UE may compare the two PUCCH resource pool values. In some aspects, the UE may not need to actively make a decision, but instead assumes that the PUCCH resource pools are the same or different based on standard rules. In some aspects, the UE determines whether the PUCCH resource pools are the same or different based on configuration parameters previously received from the TRP, for example, via RRC. If the UE determines or assumes that the PUCCH resource pools are different, the method 1400 proceeds to block 1420. If the UE determines or assumes that the PUCCH resource pools are the same, the PUCCH pool is determined to be a common PUCCH resource pool, and the method 1400 proceeds to block 1425.

[0133] At block 1420, the UE selects a PUCCH resource pool from a first PUCCH resource pool associated with a first CORESET pool index and a second PUCCH resource pool associated with a second CORESET pool index. In some aspects, the UE selects the PUCCH resource pool based on a fixed CORESET pool index value (e.g., a highest or lowest CORESET pool index value of two PUCCH resource pools based on a standard or pre-configured rule). In other aspects, the UE selects the PUCCH resource pool based on a CORESET pool index value configured via an RRC message (e.g., received from one of the network elements).

[0134] At block 1425, the UE selects a PUCCH resource set from the PUCCH resource pool based on the total number of bits in the first set of UCI and the second set of UCI. If the UE determines or assumes that the PUCCH resource pools are the same at block 1415, the PUCCH resource pools are the PUCCH resource pools associated with the two CORESET pool indices, otherwise the PUCCH resource pools are the PUCCH resource pools selected at block 1420.

[0135] At block 1430, the UE selects a PUCCH resource associated with the selected PUCCH resource set based on a predetermined rule. When the PUCCH resource pool is different for the two PUCCHs and the UE has selected a PUCCH resource pool at block 1420, the predetermined rule may be to select a PUCCH resource indicated by the PRI field of the last DCI associated with the same CORESET pool index value as the determined CORESET pool index value of the PUCCH resource pool.

[0136] When the PUCCH resource pool associated with the first CORESET pool index and the PUCCH resource pool associated with the second CORESET pool index are the same, the predetermined rule for selecting the PUCCH resource may be one of the following rules.

[0137] In some aspects, the predetermined rule may be to determine the PUCCH resources based on a PRI field in a last DCI associated with a fixed CORESET pool index value (e.g., a value of 1) among a last DCI indicating a first PUCCH and a last DCI indicating a second PUCCH. For example, if the fixed CORESET pool index value is 1, and the first PUCCH is associated with a CORESET pool index value of 0 and the second PUCCH is associated with a CORESET pool index value of 1, the PUCCH resources will be determined based on the PRI value of the last DCI indicating the second PUCCH.

[0138] In other aspects, the predetermined rule may be to determine the PUCCH resource based on the PRI field in the last DCI indicating the lowest (or alternatively, the highest) PRI code point value among the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH. For example, if the last DCI indicating the first PUCCH has a PRI code point value of 2, and the last DCI indicating the second PUCCH has a PRI code point value of 4, and the predetermined rule is to select the lowest PRI code point value, then the PUCCH resource will be selected based on the PRI code point value of 2.

[0139] In a further aspect, the predetermined rule may be to determine the PUCCH resources based on the PRI field in the last DCI among the first group of DCIs and the second group of DCIs (associated with both the first PUCCH and the second PUCCH). For example, if the last DCI indicating the first PUCCH is received during the PDCCH monitoring opportunity before the last DCI indicating the second PUCCH is received, the PUCCH resources will be determined based on the last DCI indicating the second PUCCH. However, in some instances, the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH may be received in the same PDCCH monitoring opportunity. When this occurs, there may be a fallback rule for determining between the last two DCIs whose PRI value will be used to determine the PUCCH resources. The fallback rule may be one of the following rules.

[0140] In some aspects, the fallback rule may be to determine the PUCCH resources based on the PRI field in the last DCI associated with a fixed CORESET pool index value (e.g., value 1) among the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH. For example, if the fixed CORESET pool index value is 1, and the first PUCCH is associated with the CORESET pool index value 0 and the second PUCCH is associated with the CORESET pool index value 1, the PUCCH resources will be determined based on the PRI value of the last DCI indicating the second PUCCH.

[0141] In other aspects, the fallback rule may be to determine the PUCCH resource based on the PRI field in the last DCI indicating the lowest (or alternatively, the highest) PRI code point value among the last DCI indicating the first PUCCH and the last DCI indicating the second PUCCH. For example, if the last DCI indicating the first PUCCH has a PRI code point value of 2, and the last DCI indicating the second PUCCH has a PRI code point value of 4, and the predetermined rule is to select the highest PRI code point value, then the PUCCH resource will be selected based on the PRI code point value of 4.

[0142] In yet a further aspect, the fallback rule may be to determine the PUCCH resource based on a PRI field of a last DCI indicating a first PUCCH or a last DCI indicating a second PUCCH associated with a highest or lowest CORESET ID relative to the other. For example, if the last DCI indicating a first PUCCH has a higher CORESET ID relative to the last DCI indicating a second PUCCH, and the predetermined rule is to select the highest CORESET ID, the PUCCH resource will be selected based on the PRI of the last DCI indicating the first PUCCH.

[0143] In yet a further aspect, the fallback rule may be to determine the PUCCH resources based on the PRI field of the last DCI indicating the first PUCCH or the last DCI indicating the second PUCCH received in the CORESET having the highest (or alternatively, the lowest) starting CCE index relative to the other. For example, if the last DCI indicating the first PUCCH has a higher starting CCE index relative to the last DCI indicating the second PUCCH, and the predetermined rule is to select the highest starting CCE index, the PUCCH resources will be selected based on the PRI of the last DCI indicating the first PUCCH.

[0144] At block 1435, the UE multiplexes the first set of UCI and the second set of UCI on the selected PUCCH resources. The UE may transmit those UCI using the selected multiplexed PUCCH resources.

[0145] Fig.15 1 is a flow chart illustrating a wireless communication method 1500 according to some aspects of the present disclosure. Various aspects of the method 1500 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for executing blocks. In one aspect, the BS 105, the TRP, the CU 210, and / or the DU 230, or the network unit 1100 may utilize a method such as Fig.11 The method 1500 is performed by the components of the processor 1102 , memory 1104 , UCI module 1108 , transceiver 1110 , modem 1112 , and one or more antennas 1116 as shown.

[0146] As shown, method 1500 includes a plurality of enumerated blocks, but various aspects of method 1500 may include additional blocks before, after, and between these enumerated blocks. In some aspects, one or more of the enumerated blocks may be omitted or performed in a different order.

[0147] At block 1505, the network element sends a processing configuration to the UE 115. The processing configuration may indicate, for example, whether UCIs of the same type are processed jointly or individually.

[0148] At block 1510, the network element sends multiple DCI messages to the UE 115. The DCIs may have associated with them a PRI field indicating PUCCH resources. The DCIs may request UCI from the UE 115 of different UCI types.

[0149] At block 1515, the network element sends a PUSCH configuration to the UE 115. The PUSCH configuration may be transmitted dynamically (eg, via DCI) or semi-statically (eg, via a configured grant). The PUSCH resources may overlap in time with one or more of the scheduled PUCCH resources.

[0150] At block 1520, the network element receives a PUCCH or PUSCH from the UE 115. The PUCCH or PUSCH may include all or a subset of the UCI requested in the DCI message.

[0151] Other aspects of the present disclosure include the following:

[0152] Aspect 1. A method of wireless communication performed by a user equipment (UE), the method comprising:

[0153] determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value;

[0154] receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that temporally overlaps with at least one of the first PUCCH or the second PUCCH; and

[0155] The first group of UCI and the second group of UCI are multiplexed on the PUSCH.

[0156] Aspect 2. According to the method of aspect 1, the multiplexing further comprises:

[0157] responsive to the first UCI and the second UCI being of the same type, concatenating a first UCI from the first set of UCIs with a second UCI from the second set of UCIs, resulting in a concatenated UCI;

[0158] jointly encoding the concatenated UCI;

[0159] jointly performing rate matching on the concatenated UCIs; and

[0160] mapping the concatenated UCIs jointly to the PUSCH,

[0161] Wherein, the cascading of the first UCI and the second UCI is based on an ascending or descending order of the first CORSESET pool index value and the second CORSESET pool index value.

[0162] Aspect 3. According to the method of aspect 1, the multiplexing further comprises:

[0163] In response to the first UCI and the second UCI being of the same type, separately performing a first

[0164] encoding the UCI and a second UCI from the second set of UCIs;

[0165] performing rate matching on the first UCI and the second UCI separately; and

[0166] The first UCI and the second UCI are individually mapped to the PUSCH.

[0167] Aspect 4. According to the method of aspect 3, the multiplexing further comprises:

[0168] One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order.

[0169] Aspect 5. The method according to aspect 4, wherein the highest priority UCI type in the priority order is HARQ-ACK.

[0170] Aspect 6. According to the method according to any one of aspects 1 to 5, the multiplexing further comprises:

[0171] rate matching a first hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the first CORESET pool index value by treating the first HARQ-ACK as a HARQ-ACK;

[0172] performing rate matching on a second HARQ-ACK associated with the second CORESET pool index value by treating the second HARQ-ACK as CSI part 1;

[0173] performing rate matching on CSI part 1 by treating CSI part 1 as CSI part 2; and

[0174] One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order.

[0175] Aspect 7. The method according to any one of aspects 1 to 6, further comprising:

[0176] receiving a processing configuration for jointly or individually processing UCIs of the same type from the first set of UCIs and the second set of UCIs; and

[0177] Encoding, rate matching, and mapping of the first set of UCI and the second set of UCI are performed based on the processing configuration.

[0178] Aspect 8. A method of wireless communication performed by a user equipment (UE), the method comprising:

[0179] determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value, wherein the first PUCCH resource is determined based on a PUCCH resource indicator (PRI) field in the first DCI and the second PUCCH resource is determined based on a PRI field in the second DCI;

[0180] selecting a PUCCH resource set from a PUCCH resource pool based on a total number of bits in the first set of UCI and the second set of UCI;

[0181] selecting a PUCCH resource associated with the selected PUCCH resource set based on a predetermined rule; and

[0182] The first group of UCI and the second group of UCI are multiplexed on the selected PUCCH resource.

[0183] Aspect 9. The method according to aspect 8, wherein the predetermined rule comprises selecting the PUCCH resource based on the PUCCH resource indicator (PRI) field in the first DCI or the second DCI associated with a predetermined CORESET pool index value.

[0184] Aspect 10. The method according to aspect 8, wherein the predetermined rule comprises selecting the PUCCH resource based on the PUCCH resource indicator (PRI) field of the first DCI or the second DCI having a highest or lowest value relative to the other.

[0185] Aspect 11. A method according to aspect 8, wherein the predetermined rule comprises selecting the PUCCH resource based on which of the first DCI or the second DCI is received in a later physical downlink control channel (PDCCH) monitoring opportunity relative to the other.

[0186] Aspect 12. The method according to aspect 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, and the method further comprises:

[0187] The PUCCH resource is selected based on the PUCCH resource indicator (PRI) field in the first DCI or the second DCI associated with a predetermined CORESET pool index value.

[0188] Aspect 13. The method according to aspect 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, and the method further comprises:

[0189] The PUCCH resource is selected based on the PRI field of the first DCI or the second DCI having a highest or lowest PRI field value relative to the other.

[0190] Aspect 14. The method according to aspect 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, and the method further comprises:

[0191] The PUCCH resource is selected based on the PRI field of the first DCI or the second DCI associated with a highest or lowest CORESET ID relative to the other.

[0192] Aspect 15. The method according to aspect 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, further comprising:

[0193] The PUCCH resource is selected based on a PUCCH resource indicator (PRI) field of the first DCI or the second DCI received in a CORESET having a highest or lowest starting CCE index relative to the other.

[0194] Aspect 16. The method according to aspect 8, further comprising:

[0195] receiving a control message indicating a first PUCCH resource pool associated with the first CORESET pool index value and a second PUCCH resource pool associated with the second CORESET pool index value; and

[0196] selecting the PUCCH resource pool based on the first PUCCH resource pool or the second PUCCH resource pool associated with a predetermined CORESET pool index value,

[0197] Wherein the predetermined CORESET pool index value is one of a fixed value or a configurable value configured via a radio resource control (RRC) message.

[0198] Aspect 17. The method according to aspect 16, wherein the predetermined rule comprises selecting the PUCCH resource based on a PUCCH resource indicator (PRI) field of the first DCI or the second DCI associated with the predetermined CORESET pool index value.

[0199] Aspect 18. A user equipment (UE), the user equipment (UE) comprising:

[0200] A processor, the processor being configured to:

[0201] determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value; and

[0202] A transceiver, the transceiver being configured to:

[0203] receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that temporally overlaps with at least one of the first PUCCH or the second PUCCH; and

[0204] The first group of UCI and the second group of UCI are multiplexed on the PUSCH.

[0205] Aspect 19. The UE according to aspect 18, wherein the transceiver is further configured to:

[0206] responsive to the first UCI and the second UCI being of the same type, concatenating a first UCI from the first set of UCIs with a second UCI from the second set of UCIs, resulting in a concatenated UCI;

[0207] jointly encoding the concatenated UCI;

[0208] jointly performing rate matching on the concatenated UCIs; and

[0209] mapping the concatenated UCIs jointly to the PUSCH,

[0210] Wherein, the cascading of the first UCI and the second UCI is based on an ascending or descending order of the first CORSESET pool index value and the second CORSESET pool index value.

[0211] Aspect 20. The UE according to aspect 18, wherein the transceiver is further configured to:

[0212] In response to the first UCI and the second UCI being of the same type, separately performing a first

[0213] encoding the UCI and a second UCI from the second set of UCIs;

[0214] performing rate matching on the first UCI and the second UCI separately; and

[0215] The first UCI and the second UCI are individually mapped to the PUSCH.

[0216] Aspect 21. The UE according to any one of aspects 18 to 20, wherein the transceiver is further configured to:

[0217] rate matching a first hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the first CORESET pool index value by treating the first HARQ-ACK as a HARQ-ACK;

[0218] performing rate matching on a second HARQ-ACK associated with the second CORESET pool index value by treating the second HARQ-ACK as CSI part 1;

[0219] performing rate matching on CSI part 1 by treating CSI part 1 as CSI part 2; and

[0220] One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order.

[0221] Aspect 22. The UE according to any one of aspects 18 to 21, wherein the transceiver is further configured to:

[0222] receiving a processing configuration for jointly or individually processing UCIs of the same type from the first set of UCIs and the second set of UCIs; and

[0223] Encoding, rate matching, and mapping of the first set of UCI and the second set of UCI are performed based on the processing configuration.

[0224] Aspect 23. A user equipment (UE), the user equipment (UE) comprising:

[0225] A processor, the processor being configured to:

[0226] determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value, wherein the first PUCCH resource is determined based on a PUCCH resource indicator (PRI) field in the first DCI and the second PUCCH resource is determined based on a PRI field in the second DCI;

[0227] selecting a PUCCH resource set from a PUCCH resource pool based on a total number of bits in the first set of UCI and the second set of UCI; and

[0228] selecting a PUCCH resource associated with the selected PUCCH resource set based on a predetermined rule; and

[0229] A transceiver, the transceiver being configured to:

[0230] The first group of UCI and the second group of UCI are multiplexed on the selected PUCCH resource.

[0231] Aspect 24. The UE according to aspect 23, wherein the predetermined rule comprises selecting the PUCCH resource based on the PUCCH resource indicator (PRI) field in the first DCI or the second DCI associated with a predetermined CORESET pool index value.

[0232] Aspect 25. The UE according to aspect 23, wherein the predetermined rule comprises selecting the PUCCH resource based on the PUCCH resource indicator (PRI) field of the first DCI or the second DCI having a highest or lowest value relative to the other.

[0233] Aspect 26. The UE according to aspect 23, wherein the predetermined rule comprises selecting the PUCCH resource based on which of the first DCI or the second DCI is received in a later physical downlink control channel (PDCCH) monitoring opportunity relative to the other.

[0234] Aspect 27. The UE according to aspect 26, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, wherein the processor is further configured to:

[0235] The PUCCH resource is selected based on the PUCCH resource indicator (PRI) field in the first DCI or the second DCI associated with a predetermined CORESET pool index value.

[0236] Aspect 28. The UE according to aspect 26, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, wherein the processor is further configured to:

[0237] The PUCCH resource is selected based on the PRI field of the first DCI or the second DCI having a highest or lowest PRI field value relative to the other.

[0238] Aspect 29. The UE according to aspect 26, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, wherein the processor is further configured to:

[0239] The PUCCH resource is selected based on the PRI field of the first DCI or the second DCI associated with a highest or lowest CORESET ID relative to the other.

[0240] Aspect 30. The UE according to aspect 26, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, wherein the processor is further configured to:

[0241] The PUCCH resource is selected based on a PUCCH resource indicator (PRI) field of the first DCI or the second DCI received in a CORESET having a highest or lowest starting CCE index relative to the other.

[0242] Aspect 31. The UE according to aspect 23, wherein the transceiver is further configured to receive a control message indicating a first PUCCH resource pool associated with the first CORESET pool index value and a second PUCCH resource pool associated with the second CORESET pool index value,

[0243] wherein the processor is further configured to select the PUCCH resource pool based on the first PUCCH resource pool or the second PUCCH resource pool associated with a predetermined CORESET pool index value, and

[0244] Wherein the predetermined CORESET pool index value is one of a fixed value or a configurable value configured via a radio resource control (RRC) message.

[0245] Aspect 32. The UE according to aspect 31, wherein the predetermined rule comprises selecting the PUCCH resource based on a PUCCH resource indicator (PRI) field of the first DCI or the second DCI associated with the predetermined CORESET pool index value.

[0246] Aspect 33. A user equipment (UE), the user equipment (UE) comprising:

[0247] means for determining that a first physical uplink control channel (PUCCH) resource comprising a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource comprising a second set of UCI associated with a second CORESET pool index value;

[0248] means for receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that overlaps in time with at least one of the first PUCCH or the second PUCCH; and

[0249] means for multiplexing the first set of UCI and the second set of UCI on the PUSCH.

[0250] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0251] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0252] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software, hardware, firmware, hardware wiring, or any combination thereof executed by a processor. The features of the implementation functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), "or" as used in a list of items (e.g., "or" used in a list of items ending with "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of [at least one of A, B, or C] means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0253] As those skilled in the art will understand by now and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the specific aspects illustrated and described herein (as they are only some examples of the present disclosure), but should be fully equivalent to the attached claims and their functional equivalents.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value; receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that temporally overlaps with at least one of the first PUCCH or the second PUCCH; and The first group of UCI and the second group of UCI are multiplexed on the PUSCH.

2. The method according to claim 1, wherein the multiplexing further comprises: responsive to the first UCI and the second UCI being of the same type, concatenating a first UCI from the first set of UCIs with a second UCI from the second set of UCIs, resulting in a concatenated UCI; jointly encoding the concatenated UCI; jointly performing rate matching on the concatenated UCIs; as well as mapping the concatenated UCIs jointly to the PUSCH, Wherein, the cascading of the first UCI and the second UCI is based on an ascending or descending order of the first CORSESET pool index value and the second CORSESET pool index value.

3. The method according to claim 1, wherein the multiplexing further comprises: In response to the first UCI and the second UCI being of the same type, separately encoding the first UCI from the first set of UCIs and the second UCI from the second set of UCIs; performing rate matching on the first UCI and the second UCI separately; and The first UCI and the second UCI are individually mapped to the PUSCH.

4. The method according to claim 3, wherein the multiplexing further comprises: One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order. The method of claim 4 , wherein the highest priority UCI type of the priority order is HARQ-ACK.

6. The method according to claim 1, wherein the multiplexing further comprises: performing rate matching on a first hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the first CORESET pool index value by treating the first HARQ-ACK as a HARQ-ACK; performing rate matching on a second HARQ-ACK associated with the second CORESET pool index value by treating the second HARQ-ACK as CSI part 1; performing rate matching on the CSI part 1 by treating the CSI part 1 as CSI part 2; as well as One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order.

7. The method according to claim 1, further comprising: receiving a processing configuration for jointly or individually processing UCIs of the same type from the first set of UCIs and the second set of UCIs; as well as Encoding, rate matching, and mapping of the first set of UCI and the second set of UCI are performed based on the processing configuration.

8. A method of wireless communication performed by a user equipment (UE), the method comprising: determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value, wherein the first PUCCH resource is determined based on a PUCCH resource indicator (PRI) field in the first DCI and the second PUCCH resource is determined based on a PRI field in the second DCI; selecting a PUCCH resource set from a PUCCH resource pool based on a total number of bits in the first set of UCI and the second set of UCI; selecting a PUCCH resource associated with the selected PUCCH resource set based on a predetermined rule; as well as The first group of UCI and the second group of UCI are multiplexed on the selected PUCCH resource.

9. The method of claim 8, wherein the predetermined rule comprises selecting the PUCCH resource based on the PUCCH resource indicator (PRI) field in the first DCI or the second DCI associated with a predetermined CORESET pool index value.

10. The method of claim 8, wherein the predetermined rule comprises selecting the PUCCH resource based on the PUCCH resource indicator (PRI) field of the first DCI or the second DCI having a highest or lowest value relative to the other.

11. The method of claim 8, wherein the predetermined rule comprises selecting the PUCCH resource based on which of the first DCI or the second DCI is received in a later physical downlink control channel (PDCCH) monitoring opportunity relative to the other.

12. The method according to claim 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, the method further comprising: The PUCCH resource is selected based on the PUCCH resource indicator (PRI) field in the first DCI or the second DCI associated with a predetermined CORESET pool index value.

13. The method according to claim 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, the method further comprising: The PUCCH resource is selected based on the PRI field of the first DCI or the second DCI having a highest or lowest PRI field value relative to the other.

14. The method according to claim 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, the method further comprising: The PUCCH resource is selected based on the PRI field of the first DCI or the second DCI associated with a highest or lowest CORESET ID relative to the other.

15. The method according to claim 11, wherein the first DCI and the second DCI are received in the same PDCCH monitoring opportunity, the method further comprising: The PUCCH resource is selected based on a PUCCH resource indicator (PRI) field of the first DCI or the second DCI received in a CORESET having a highest or lowest starting CCE index relative to the other.

16. The method according to claim 8, further comprising: receiving a control message indicating a first PUCCH resource pool associated with the first CORESET pool index value and a second PUCCH resource pool associated with the second CORESET pool index value; and selecting the PUCCH resource pool based on the first PUCCH resource pool or the second PUCCH resource pool associated with a predetermined CORESET pool index value, Wherein the predetermined CORESET pool index value is one of a fixed value or a configurable value configured via a radio resource control (RRC) message.

17. The method of claim 16, wherein the predetermined rule comprises selecting the PUCCH resource based on a PUCCH resource indicator (PRI) field of the first DCI or the second DCI associated with the predetermined CORESET pool index value.

18. A user equipment (UE), the user equipment (UE) comprising: A processor, the processor being configured to: determining that a first physical uplink control channel (PUCCH) resource including a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including a second set of UCI associated with a second CORESET pool index value; and A transceiver, the transceiver being configured to: receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that temporally overlaps with at least one of the first PUCCH or the second PUCCH; and The first group of UCI and the second group of UCI are multiplexed on the PUSCH.

19. The UE according to claim 18, wherein the transceiver is further configured to: responsive to the first UCI and the second UCI being of the same type, concatenating a first UCI from the first set of UCIs with a second UCI from the second set of UCIs, resulting in a concatenated UCI; jointly encoding the concatenated UCI; jointly performing rate matching on the concatenated UCIs; as well as mapping the concatenated UCIs jointly to the PUSCH, Wherein, the cascading of the first UCI and the second UCI is based on an ascending or descending order of the first CORSESET pool index value and the second CORSESET pool index value.

20. The UE according to claim 18, wherein the transceiver is further configured to: In response to the first UCI and the second UCI being of the same type, separately encoding the first UCI from the first set of UCIs and the second UCI from the second set of UCIs; performing rate matching on the first UCI and the second UCI separately; and The first UCI and the second UCI are individually mapped to the PUSCH.

21. The UE according to claim 20, wherein the transceiver is further configured to: One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order.

22. The UE of claim 21, wherein the highest priority UCI type of the priority order is HARQ-ACK.

23. The UE according to claim 18, wherein the transceiver is further configured to: performing rate matching on a first hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the first CORESET pool index value by treating the first HARQ-ACK as a HARQ-ACK; performing rate matching on a second HARQ-ACK associated with the second CORESET pool index value by treating the second HARQ-ACK as CSI part 1; performing rate matching on CSI part 1 by treating CSI part 1 as CSI part 2; and One or more UCIs after the first three UCIs are discarded from the first group of UCIs and the second group of UCIs according to a priority order.

24. The UE according to claim 18, wherein the transceiver is further configured to: receiving a processing configuration for jointly or individually processing UCI of the same type from the first set of UCIs and the second set of UCIs; and Encoding, rate matching, and mapping of the first set of UCI and the second set of UCI are performed based on the processing configuration.

25. A user equipment (UE), the user equipment (UE) comprising: means for determining that a first physical uplink control channel (PUCCH) resource comprising a first set of uplink control information (UCI) associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource comprising a second set of UCI associated with a second CORESET pool index value; means for receiving a scheduling configuration for a physical uplink shared channel (PUSCH) that overlaps in time with at least one of the first PUCCH or the second PUCCH; and means for multiplexing the first set of UCI and the second set of UCI on the PUSCH.

26. The UE according to claim 25, wherein the means for multiplexing further comprises: means for, in response to the first UCI and the second UCI being of the same type, concatenating a first UCI from the first set of UCIs with a second UCI from the second set of UCIs, resulting in a concatenated UCI; means for jointly encoding the concatenated UCI; means for jointly rate matching the concatenated UCIs; and means for mapping the concatenated UCI jointly to the PUSCH, Wherein, the cascading of the first UCI and the second UCI is based on an ascending or descending order of the first CORSESET pool index value and the second CORSESET pool index value.

27. The UE according to claim 25, wherein the means for multiplexing further comprises: means for separately encoding a first UCI from the first set of UCIs and a second UCI from the second set of UCIs in response to the first UCI and the second UCI being of the same type; means for individually performing rate matching on the first UCI and the second UCI; and means for individually mapping the first UCI and the second UCI to the PUSCH.

28. The UE according to claim 20, wherein the means for multiplexing further comprises: means for discarding one or more UCIs after the first three UCIs from the first group of UCIs and the second group of UCIs according to a priority order.

29. The UE according to claim 25, wherein the means for multiplexing further comprises: means for performing rate matching on a first hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the first CORESET pool index value by treating the first HARQ-ACK as a HARQ-ACK; means for performing rate matching on a second HARQ-ACK associated with the second CORESET pool index value by considering the second HARQ-ACK as CSI part 1; means for performing rate matching on CSI part 1 by treating the CSI part 1 as CSI part 2; and means for discarding one or more UCIs after the first three UCIs from the first group of UCIs and the second group of UCIs according to a priority order.

30. The UE according to claim 25, further comprising: means for receiving a processing configuration for jointly or individually processing UCIs of the same type from the first and second sets of UCIs; and Means for performing encoding, rate matching, and mapping of the first set of UCI and the second set of UCI based on the processing configuration.

Images