Uplink control information message multiplexing on physical uplink shared channel resources across different transmit-receive points

Abstract

The present disclosure provides systems, methods, and devices for supporting wireless communications of uplink control information (UCI) message multiplexing onto physical uplink shared channel (PUSCH) resources across different transmit receive points (TRPs). In a first aspect, a method of wireless communication includes determining that a first physical uplink control channel (PUCCH) including one or more first UCI messages associated with a first control resource set (CORESET) pool index value overlaps in time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value. The UE may identify one or more PUSCH resources that overlap with at least one of the PUCCH resources. The UE multiplexes one or more of the UCI messages onto one or more of the PUSCH resources, and transmits those of the PUSCH resources that include the UCI messages. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to a serving cell configured with multiple transmit receive points (TRPs) based on multiple downlink control information (DCI). Some features enable and provide improved communications, including multiplexing uplink control information (UCI) messages onto physical uplink shared channel (PUSCH) resources across different TRPs in a serving cell. Background Art

[0002] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0003] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or Node B) that may support communications for several user equipments (UEs). UEs may communicate with base stations via downlinks and uplinks. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.

[0004] The base station may send data and control information to the UE on the downlink, or may receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmission from a neighboring base station or other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from other UEs communicating with the neighboring base station or from uplink transmissions of other wireless RF transmitters. This interference may degrade the performance on both the downlink and the uplink.

[0005] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows as more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in communities. Research and development continues to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications. Summary of the invention

[0006] 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 is it intended 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 more specific embodiments presented later.

[0007] In one aspect of the present disclosure, a method of wireless communication includes: determining, by a UE, that a first physical uplink control channel (PUCCH) resource including one or more first uplink control information (UCI) messages associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value; identifying, by the UE, one or more physical uplink shared channel (PUSCH) resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and sending, by the UE after the multiplexing, the one or more PUSCH resources on an associated component carrier.

[0008] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to: determine, by a UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value in a time domain; identify, by the UE, one or more PUSCH resources overlapping with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplex, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and send, by the UE after the multiplexing, the one or more PUSCH resources on an associated component carrier.

[0009] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes: a component for determining, by a UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value in a time domain; a component for identifying, by the UE, one or more PUSCH resources overlapping with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; a component for multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and a component for sending, by the UE, the one or more PUSCH resources on an associated component carrier after execution of the component for multiplexing.

[0010] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations, including: determining, by a UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps in a time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value; identifying, by the UE, one or more PUSCH resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and sending, by the UE, one or more PUSCH resources on an associated component carrier after execution of the component for multiplexing.

[0011] For those of ordinary skill in the art, other aspects, features, and specific implementations will become apparent when reviewing the following description of specific exemplary aspects in conjunction with the accompanying drawings. Although each feature may be discussed below with respect to certain aspects and accompanying drawings, each aspect 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 each aspect. In a similar manner, although the exemplary aspects may be discussed below as aspects of a device, system, or method, the exemplary aspects may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by adding a dash and a second label to distinguish between similar components after the reference label. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, regardless of the second reference label.

[0013] Figure 1 is a block diagram illustrating example details of an example wireless communication system according to one or more aspects.

[0014] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) according to one or more aspects.

[0015] Figure 3 is a block diagram illustrating a serving cell 30 served by a transmit reception point (TRP) and having at least one CC / BWP configured with a plurality of CORESET pool index values.

[0016] Figure 4 is a flow chart illustrating an example process for supporting UCI message multiplexing onto PUSCH resources across different TRPs according to one or more aspects.

[0017] FIG. 5A to FIG. 5B is a block diagram illustrating a UE configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0018] FIG. 6A to FIG. 6B is a block diagram illustrating a UE configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0019] FIG. 7A to FIG. 7B is a block diagram illustrating a UE configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0020] FIG. 8A to FIG. 8B is a block diagram illustrating a UE configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0021] Fig. 9 is a block diagram illustrating a UE configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0022] FIG. 10A to FIG. 10Bis a block diagram illustrating a UE configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0023] Fig.11 is a block diagram of an example UE supporting UCI message multiplexing onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure.

[0024] The same reference numbers and designations in different drawings indicate the same elements. DETAILED DESCRIPTION

[0025] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to limit the scope of the present disclosure. Instead, the specific embodiments include specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0026] The present disclosure provides systems, apparatus, methods, and computer-readable media that support uplink control information (UCI) message multiplexing on physical uplink shared channel (PUSCH) resources across different transmit receive points (TRPs). Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, the present disclosure provides techniques for multiplexing UCI messages on PUSCH resources across different base stations, allowing higher priority UCI messages to be sent while retaining PUSCH transmissions that may overlap with scheduled PUCCH resource transmissions in the time domain.

[0027] The present disclosure as a whole relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, the techniques and devices may be used in 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, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices), and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0028] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0029] For example, a TDMA network can implement a radio technology such as a global system for mobile communications (GSM). The third generation partnership project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rate GSM Evolution) radio access network (RAN) (also known as GERAN). GERAN is the radio component of the network of GSM / EDGE together with connecting base stations (e.g., Ater interface and Abis interface) and base station controllers (A interface, etc.). The radio access network represents the component of the GSM network through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also known as user terminals or user equipment (UE)) and from subscriber phones to the public switched telephone network (PSTN) and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled with UTRAN in the case of a UMTS / GSM network. Additionally, the operator network may also include one or more LTE networks, or one or more other networks. Various network types may use different radio access technologies (RATs) and RANs.

[0030] OFDMA networks can implement radio technologies 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 that uses 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, 3GPP is a collaboration between telecommunications association groups to define globally applicable third generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP plan to improve UMTS mobile phone standards. 3GPP can define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G or 5G NR technology; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0031] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse 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 being considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about 10s of bits / second), ultra-low energy (e.g., about 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) 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 (ms)), and users with a wide range of mobility or lack of mobility; and (3) providing services with enhanced mobile broadband (including extremely 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).

[0032] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically referred to (interchangeably) as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is typically (interchangeably) referred to as the “millimeter wave” (mmW) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “mmW” band by the International Telecommunication Union (ITU).

[0033] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.126GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, currently exploring higher frequency bands to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2x (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-275GHz). Each of these higher frequency bands falls within the EHF band.

[0034] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "mmW" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR2x, FR4, and / or FR5, or can be within the EHF band.

[0035] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform features. These features may include scalable parameter sets and transmission time intervals (TTIs); a common flexible framework that efficiently multiplexes services and features using dynamic, low-latency time division duplex (TDD) designs or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust mmW transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5GNR 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 or TDD implementations, the subcarrier spacing may appear at 15kHz, such as over bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz over 80MHz / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, the subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting over mmW components at 28GHz TDD, the subcarrier spacing may occur at 120kHz over a 500MHz bandwidth.

[0036] 5G NR's scalable parameter sets facilitate scalable TTIs for diverse 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 anticipates a self-contained integrated subframe design where uplink or downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic demands.

[0037] For clarity, certain aspects of the devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0038] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed spectrum or unlicensed spectrum depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0039] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many other arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementation or use can be implemented via integrated chip specific implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically relate to use cases or applications, the innovation described may have various types of applicability. The scope of specific implementation can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more described aspects. In some practical environments, the devices incorporating the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be practiced in a wide variety of implementations of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, and the like.

[0040] Figure 1 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements (including, for example, cellular-style network arrangements and non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.)).

[0041] Figure 1The illustrated wireless network 100 includes several base stations 105 and other network entities. A base station may be a station that communicates with a UE, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 5G NR operation, a transmit receive point (TRP) may include various types of base stations 105, relay stations, or other types of network entities that provide a communication link with a UE such as UE 115. In 3GPP, the term "cell" may refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In a specific implementation of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in a specific implementation of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more frequencies (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) in the same frequency as an adjacent cell. In some examples, an individual base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0042] A base station may provide communication coverage for a macro cell or a small cell (such as a pico cell or a femto cell) or other type of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with a service subscription with a network provider. A small cell (such as a pico cell) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription with a network provider. A small cell (such as a femto cell) 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 cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation beamforming and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0043] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous operation or asynchronous operation.

[0044] UE 115 is dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as UEs in the standards and specifications promulgated by 3GPP, such devices may be additionally or otherwise referred to as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices or vehicle modules, or some other suitable terminology by those skilled in the art. In this document, a "mobile" device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices, such as specific implementations that may include one or more UEs in UE 115, include mobile phones, cellular phones (handsets), smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an IoT or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quad-rotor helicopter, a smart energy or security device, a solar panel or solar array, city lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device that includes a universal integrated circuit card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1 The illustrated specific implementation UE 115a-115d is an example of a mobile smart phone type device accessing the wireless network 100. The UE may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The illustrated UEs 115e - 115k are examples of various machines that access the wireless network 100 and are configured for communication.

[0045] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication link (represented as a lightning ball) indicates the wireless transmission between the UE and the serving base station (which is a base station designated to serve the UE on the downlink or uplink) or the expected transmission between the base stations and the backhaul transmission between the base stations. The UE can operate as a base station or other network node in some scenarios. The backhaul communication between the base stations of the wireless network 100 can be carried out using wired or wireless communication links.

[0046] In operation, at the wireless network 100, base stations 105a-105c use 3D beamforming and coordinated spatial techniques (such as coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to 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.

[0047] The wireless network 100 of the specific implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e as drones. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter) and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports the temperature measurement information to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD communications or low-latency FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i - 115k communicating with a macro base station 105e .

[0048] Figure 2 1 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1For a restricted association scenario (as described above), base station 105 may be any base station in the base station and one of the UEs. Figure 1 The small cell base station 105f in the example of FIG. 105 and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown in FIG. 1 , the base station 105 may be equipped with antennas 234a through 234t and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0049] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (such as a processor). The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, the transmit processor 220 may process the data and control information (e.g., encode and symbol map them) respectively to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, or reference symbols, if applicable, and may provide an output symbol stream to modulators (MOD) 232a to 232t. For example, the spatial processing performed on the data symbol, the control symbol, or the reference symbol may include pre-coding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., analog-convert, amplify, filter, and up-convert) to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0050] At the UE 115, antennas 252a to 252r may receive the downlink signal from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition the corresponding received signal (e.g., filter, amplify, downconvert, and digitize it) to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols as needed, and provide detected symbols. A receive processor 258 may process the detected symbols (e.g., demodulate, deinterleave, and decode them), provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller 280 (such as a processor).

[0051] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. These symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if necessary, further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signals from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if necessary, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller 240 .

[0052] The controllers 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution of various processes for the techniques described herein. Figure 4 The illustrated execution or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0053] In some cases, the UE 115 and the base station 105 may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or the base station 105 may traditionally perform a medium sensing procedure to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-send (LBT) procedure (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some specific implementations, the CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating the use of the channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT procedure may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets as a manifestation of a collision.

[0054] Generally, four categories of LBT procedures have been proposed for sensing signals on a shared channel that may indicate that the channel is occupied. In the first category (CAT 1 LBT), no LBT or CCA is applied to detect occupancy of a shared channel. The second category (CAT 2 LBT) (which may also be referred to as shortened LBT, single LBT, 16-μs LBT, or 25-μs LBT) specifies that a node performs CCA to detect energy above a predetermined threshold or to detect a message or preamble occupying a shared channel. CAT 2 LBT performs CCA without using a random backoff operation, which results in its shortened length relative to the next category.

[0055] The third category (CAT 3LBT) performs CCA to detect energy or messages on the shared channel, but also uses random backoff and fixed contention windows. Therefore, when a node initiates CAT 3LBT, it performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle during the first CCA, the node can continue to transmit. However, if the first CCA detects a signal occupying the shared channel, the node selects a random backoff based on the fixed contention window size and performs an extended CCA. If the shared channel is detected to be idle during the extended CCA and the random number has been decremented to 0, the node can start transmitting on the shared channel. Otherwise, the node decrements the random number and performs another extended CCA. The node will continue to perform extended CCAs until the random number reaches 0. If the random number reaches 0 without any extended CCA detecting channel occupancy, the node can then transmit on the shared channel. If in any extended CCA, the node detects channel occupancy, the node can reselect a new random backoff based on the fixed contention window size to start the countdown again.

[0056] The fourth category (CAT 4 LBT) (which may also be referred to as the full LBT procedure) performs CCA with energy or message detection using random backoff and variable contention window size. The sequence of CCA detection proceeds similarly to the process of CAT 3 LBT, except that the contention window size is variable for the CAT 4 LBT procedure.

[0057] Sensing for shared channel access may also be categorized into full or shortened types of LBT procedures. For example, full LBT procedures such as CAT 3 or CAT 4 LBT procedures (including extended channel clearance assessment (ECCA) over a non-trivial number of 9-μs time slots) may also be referred to as "Type 1 LBT". Shortened LBT procedures such as CAT 2 LBT procedures (which may include a one-time CCA for 16-μs or 25-μs) may also be referred to as "Type 2 LBT".

[0058] Using medium sensing procedures to compete for access to unlicensed shared spectrum can result in inefficient communications. This is particularly evident when multiple network operating entities (e.g., network operators) attempt to access shared resources. In the wireless communication system 100, the base station 105 and the UE 115 may be operated by the same or different network operating entities. In some examples, a separate base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity. Requiring each base station 105 and UE 115 of different network operating entities to compete for shared resources may result in increased signaling overhead and communication latency.

[0059] In some cases, operation in an unlicensed band may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. Duplexing in the unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.

[0060] Physical uplink control channel (PUCCH) resources including acknowledgement information (e.g., hybrid automatic reception request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) information) or channel state information (CSI) may sometimes overlap with physical uplink shared channel (PUSCH) resources in the time domain. 3GPP Release 15 (Rel.15) and Release 16 (Rel.16) New Radio (NR) standards specify that uplink control information (UCI) messages (e.g., acknowledgement information, CSI, etc.) may be multiplexed on PUSCH resources. In this functionality, the UE will first resolve any overlapping different PUCCH resources in order to perform UCI multiplexing. For example, the UE may determine that a first PUCCH resource including HARQ-ACK / NACK overlaps in time with a second PUCCH resource including CSI or a scheduling request. The UE will multiplex the HARQ-ACK / NACK, CSI, or SR onto a single PUCCH resource. This process generates non-overlapping PUCCH resources including multiple UCI messages (eg, HARQ-ACK / NACK / CSI / SR).

[0061] When the corresponding PUCCH resource overlaps with the PUSCH resource in the time domain, the UE may then multiplex one or more UCI messages of the non-overlapping PUCCH resource onto the PUSCH resource. In this case, the PUCCH resource will not be sent by the UE. The overlapping PUCCH and PUSCH in this process may reside in the same component carrier (CC) or in different CCs.

[0062] It should be noted that when dynamically scheduled channels such as channels scheduled by downlink control information (DCI) messages are involved, the UE shall meet any joint timeline for UCI multiplexing on PUCCH resources or PUSCH resources.

[0063] The multiplexing procedure may be facilitated using a beta offset that is signaled to the UE in an uplink grant (e.g., DCI0_1 / 0_2), radio resource control (RRC) signaling, etc. The beta offset may be used to control rate matching behavior, such as identifying the amount of resources that a UCI payload may occupy on a PUSCH resource.

[0064] Support for simultaneous transmission of PUCCH / PUSCH resources has been introduced in 3GPP Release 17 (Rel. 17). However, such simultaneous transmission is provided when the PUCCH resources and PUSCH resources are located on different cells in inter-band carrier aggregation (CA), where the PUCCH / PUSCH resources are associated with different physical (PHY) layer priorities (e.g., one of the PUCCH / PUSCH resources is high priority and the other PUSCH / PUCCH resource is low priority). Simultaneous PUCCH / PUSCH transmission for PUCCH / PUSCH resources on the same cell, or on a CC in intra-band CA, or on a CC in inter-band CA is not currently supported when the PUCCH / PUSCH resources have the same PHY layer priority. PUSCH resources that may be transmitted simultaneously with PUCCH resources may be excluded from overlapping channels due to rules regarding UCI multiplexing or priority sorting, and may not be subject to intra-UE multiplexing timeline constraints.

[0065] 5G NR operation may provide multiple serving cells, wherein each serving cell may be configured with multiple bandwidth parts (BWPs) for serving UEs within the associated serving cell, and wherein each serving cell may be served by multiple base stations, such that each CC or BWP may be configured with multiple control resource sets (CORESETs) and each CORESET is associated with a CORESET pool index. When such a UE receives downlink control information (DCI) messages and downlink transmissions from multiple transmit receive points (TRPs) within the serving cell, multiple timing advances may be defined for uplink transmissions from the UE. The DCI message may be received in a CORESET associated with a given CORESET pool index value, such that the UE may identify which TRP the DCI is associated with.

[0066] Figure 3 1 is a block diagram illustrating a serving cell 30 served by TRPs 105x and 105y and having at least one CC / BWP configured with multiple CORESET pool index values. The serving cell 30 is configured for a UE 115 to maintain communications with multiple TRPs such as TRPs 105x and 105y. In one implementation, the UE 115 may maintain such multi-TRP communications using a design based on multiple DCI messages. For example, TRP 105x may send a first DCI in PDCCH1, which is scheduled for downlink transmission from TRP 105x, i.e., PDSCH1. TRP 105y may send a second DCI in PDCCH2, which is scheduled for downlink transmission from TRP 105y, i.e., PDSCH2.

[0067] On the UE side, the UE 115 may be configured with multiple CORESETs for active BWPs for serving cells such as serving cell 30 via upper layer signaling. The UE 115 may then distinguish which of the TRPs 105x or 105y is transmitting based on the CORESET pool index value associated with the CORESET in which the DCI message is received. Each CORESET (currently up to 5 CORESETs) may be configured with a CORESET pool index value. Current standards specify that the CORESET pool index value may be 0 or 1. This configuration divides the CORESETs into two groups. In addition to the different CORESETs, the number of TRPs serving the serving cell is transparent to the UE 115. The CORESET pool index of the CORESET in which the DCI is received may be used for different purposes, such as for HARQ-ACK / NACK feedback, CSI, SR, etc.

[0068] Rel. 16 also defines two acknowledgement feedback modes for such operation. In separate acknowledgement feedback mode, UE 115 will provide any ACK or NACK feedback to TRPs 105x and 105y in PUCCH1 and PUCCH2, respectively. In joint acknowledgement feedback mode, UE 115 may include ACK / NACK for each of the downlink transmissions (i.e., PDSCH 1 and PDSCH2) in a single PUCCH, such as PUCCH 1.

[0069] Support for simultaneous PUCCH transmission on a CC may be specified in 3GPP Release 18 (Rel. 18) for multi-DCI, multi-TRP operation. One proposed implementation of such simultaneous PUCCH transmission in a CC provides simultaneous PUCCH transmission for separate feedback. However, simultaneous PUCCH / PUSCH transmission is not within the scope of Rel. 18. For the case of multi-TRP operation based on multi-DCI, multiple PUSCH resources may be transmitted simultaneously across two antenna panels in the same CC, or multiple PUCCH resources may be transmitted simultaneously across two antenna panels in the same CC.

[0070] For example, assuming that the first PUCCH resource and the second PUCCH resource are determined to overlap in the time domain so that the first PUCCH resource and the second PUCCH resource can be transmitted simultaneously, in this example, the first PUCCH includes a first UCI message of HARQ-ACK / NACK associated with CORESET pool index 0, and the second PUCCH includes a second UCI message of HARQ-ACK / NACK associated with CORESET pool index 1. In the described example, the PUSCH resource overlaps with both the first PUCCH resource and the second PUCCH resource and is associated with CORESET pool index 0. If the first UCI message is multiplexed onto the PUSCH resource associated with the same CORESET pool index value 0, the second UCI message will be discarded because simultaneous PUCCH / PUSCH resource transmission is not supported, except for the limited case described above from Rel. 17. However, HARQ-ACK / NACK has a higher priority than PUSCH.

[0071] Solutions for UE behavior have been proposed that assume that UCI messages may be multiplexed on PUSCH associated with the same CORESET pool index. In this proposed case, the UE may determine which of the first UCI message and the second UCI message is multiplexed with which of the PUSCH resources, and which resource between the PUCCH resources and the PUSCH resources should be discarded after multiplexing. However, for an ideal backhaul implementation, the UCI message may be multiplexed on any of the PUSCH resources, regardless of the associated CORESET pool index value. In such an ideal backhaul implementation, different UE behaviors may be considered, such as whether the UE may multiplex both the first UCI message and the second UCI message on the PUSCH resource. Various aspects of the present disclosure provide UE behavior when one or more of two time-domain overlapping PUCCH resources that may be sent simultaneously overlap with one or more PUSCH resources.

[0072] Figure 4 4 is a flow chart illustrating an example process 400 for supporting multiplexing of UCI messages onto PUSCH resources across different TRPs according to one or more aspects. The operations of process 400 may be performed by a UE (such as the one described above with reference to Figure 1 , Figure 2 , Figure 3 5). For example, the example operations (also referred to as "boxes") of process 400 may enable UE 115 to support UCI message multiplexing on PUSCH resources across different TRPs.

[0073] About Fig.11 4. The process 400 is described below. Fig.11 1 is a block diagram of an example UE 115 supporting multiplexing of UCI messages on PUSCH resources across different base stations according to various aspects of the present disclosure. The UE 115 may be configured to perform operations including referring to Figure 4 In some implementations, the UE 115 includes a reference Figure 1 to Figure 2 1. The structure, hardware, and components of the UE 115 shown and described in detail. For example, the UE 115 includes a controller 280 that is used to execute logic or computer instructions stored in a memory 282 and control components of the UE 115 that provide the features and functionality of the UE 115. The UE 115 sends and receives signals via the radios 1100a-r and antennas 252a-r under the control of the controller 280. The radios 1100a-r include various components and hardware, such as Figure 2 As illustrated for UE 115, modulators and demodulators 254a-r, a MIMO detector 256, a receive processor 258, a transmit processor 264, and a TX MIMO processor 266 are included.

[0074] As shown, the memory 282 may include a CORESET configuration 1101, an uplink (UL) communication logic 1102, and an uplink message generator 1103. The CORESET configuration 1101 may be configured to maintain the CORESETs configured for the UE 115, which may be indexed via a CORESET pool index value. The uplink communication logic 1102 may be configured to manage uplink communications from the UE 115, including determination of scheduling of PUCCH and PUSCH. The uplink message generator 1103 may be configured to generate uplink communications, which may include UCI messages, data transmissions, etc. The UE 115 may receive communications from one or more network entities (such as UEs) via the antennas 252a-r and the radio devices 1100a-r. Figures 1 to 3 and FIG. 5A to FIG. 10B A base station or TRP 105) receives signals or sends signals to one or more network entities.

[0075] At block 401, the UE determines that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps in the time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORE SET pool index value. A UE such as UE 115 may be configured to communicate with multiple TRPs and will receive configuration information about multiple CORESETs. The CORESET identified by the CORESET pool index value in the DCI message is stored in the memory 282 at the CORESET configuration 1101. The UE 115 may further execute uplink communication logic 1102 under the control of the controller 280. The controller 280 executes the code of the uplink communication logic 1102, referred to as the "execution environment" of the uplink communication logic 1102, to provide features and functionality for managing uplink communications to the UE 115. The functionality may include scheduling, determining and planning UCI messages sent by PUCCH and PUSCH resources, etc.

[0076] Within the execution environment of the uplink communication logic 1102, the UE 115 may determine two time-domain overlapping PUCCH resources that may be simultaneously transmitted in a first CC (e.g., a primary cell (PCell), a PUCCH secondary cell (PSCell), etc.), wherein the first PUCCH resource may include one or more UCI messages associated with a first CORESET pool index value. The UCI message may be HARQ-ACK / NACK, CSI, SR, or a combination of such UCI types (e.g., HARQ-ACK / NACK+CSI or HARQ-ACK / NACK+SR or HARQ-ACK / NACK+SR+CSI). The second PUCCH resource may also include one or more UCI associated with a second different CORESET pool index value. The UCI message of the second PUCCH may also be HARQ-ACK / NACK, CSI, SR, or a combination thereof. After determining a procedure for UCI multiplexing of overlapping PUCCHs, the first PUCCH resource and the second PUCCH resource are determined.

[0077] At block 402, the UE identifies one or more PUSCH resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain. Within the execution environment of the uplink communication logic 1102, the UE 115 may determine whether the one or more PUSCH resources overlap with at least one PUCCH resource regardless of the CC with which the PUSCH resources are associated, which means that the one or more PUSCH resources may be in the same CC or in a different CC than the first CC.

[0078] At block 403, the UE multiplexes one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources. Within the execution environment of the uplink communication logic 1102, the UE 115 may determine whether to multiplex any of the UCI messages on one of the PUSCH resources or whether to multiplex each of the UCI messages on the corresponding PUSCH resources. The UE 115 may then execute the uplink message generator logic 1103 stored in the memory 282 under the control of the controller 280. The execution environment of the uplink message generator logic 1103 provides the UE 115 with functionality for generating uplink transmissions, including generating one or more PUSCH resource transmissions and multiplexing any UCI message onto one or more of the PUSCH resource transmissions.

[0079] At block 404, one or more PUSCH resources are sent on the associated component carriers after multiplexing.The UE 115, under control of the controller 280, may then send the one or more PUSCH resources via the radios 1100a-r and antennas 252a-r.

[0080] As reference Figure 4 As described, the present disclosure provides a technique for multiplexing UCI messages onto PUSCH resources across different TRPs, allowing higher priority UCI messages to be sent while retaining PUSCH transmissions that can overlap with scheduled PUCCH resource transmissions in the time domain.

[0081] Figure 5A 1 is a block diagram illustrating a UE 115 configured for UCI message multiplexing onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure. When the UE 115 determines at a determination stage 500 that the PUCCH1 resource and the PUCCH2 resource overlap in the time domain and are available for simultaneous PUCCH transmission and that a plurality of PUSCH resources (i.e., the PUSCH 1 resource and the PUSCH2 resource) also overlap in the time domain with at least one of the PUCCH 1 resource and the PUCCH2 resource, the UE performs a UCI message multiplexing procedure 50. The UE 115 selects one PUSCH resource from the PUSCH 1 resource and the PUSCH2 resource for the UCI multiplexing procedure 50. In one example implementation, the UE 115 may select a PUSCH from the PUSCH 1 resource and the PUSCH2 resource that overlaps with both the PUCCH 1 resource and the PUCCH2 resource. In this example, PUSCH 1 resources overlap with both PUCCH 1 resources and PUCCH 2 resources, so UE 115 will select PUSCH 1 resources for UCI multiplexing.

[0082] In an additional example implementation, the UE 115 may determine that more than one PUSCH resource overlaps with both the PUCCH 1 resource and the PUCCH 2 resource. In such an example implementation, the UE 115 may apply the PUSCH priority rules identified in Rel. 15 among the more than one PUSCH resources overlapping with both the PUCCH 1 resource and the PUCCH 2 resource. The Rel. 15 PUSCH priority rules identify the priority PUSCH resource using the associated CC index first, followed by the start time of the resource. Thus, the priority PUSCH resource will be determined as having the lowest associated CC index first and the earliest start time second. If more than one PUSCH resource shares the lowest CC index, the PUSCH resource with the earliest start time will then be identified as the priority PUSCH resource.

[0083] exist Figure 5A In the illustrated first optional aspect, when a PUSCH resource is selected from a plurality of overlapping PUSCH resources, the UCI messages of the PUCCH 1 resource and the PUCCH 2 resource (i.e., UCI1 including HARQ ACK1 and UCI2 including HARQ ACK2) will each be multiplexed onto the selected PUSCH resource. Therefore, as illustrated, after determining to select the PUSCH 1 resource at the determination stage 500, the UE 115 multiplexes UCI1 and UCI2 onto the PUSCH 1 resource at the multiplexing stage 501. Then, the UE 115 may send the PUSCH 1 resource including UCI1 and UCI2 and the PUSCH 2 resource to one or both of the TRPs 105x and 105y, and may not send either the PUCCH 1 resource or the PUCCH 2 resource.

[0084] It should be noted that within the determination phase 500, the UE 115 may use a variety of different methods to select a "priority" PUSCH resource. For example, instead of the Rel. 15 priority rule, the UE 115 may use the opposite criteria by first selecting the PUSCH resource with the earliest start time, and resolving multiple PUSCHs with the same start time by selecting the PUSCH with the lowest CC index, or another variation may be to resolve multiple PUSCHs with the same start time using the highest CC index selection. Any combination or other selection criteria may be used. According to various aspects of the present disclosure, a single method of selecting a PUSCH from multiple overlapping PUSCHs is not required.

[0085] Figure 5B1 is a block diagram illustrating a UE 115 configured for UCI message multiplexing onto PUSCH resources across different TRPs according to various aspects of the present disclosure. The UE 115 performs a UCI message multiplexing procedure 51, which may be Figure 5A A variation of the illustrated first optional aspect. Similarly, in the determination phase 500, the UE 115 determines that the PUCCH1 resource and the PUCCH2 resource overlap in the time domain and are available for simultaneous transmission, and that one or more PUSCH resources (i.e., the PUSCH1 resource and the PUSCH2 resource) overlap in the time domain with one or more of the PUCCH1 resource and the PUCCH2 resource. However, as Figure 5B As illustrated, neither the PUSCH1 resources nor the PUSCH2 resources overlap with both the PUCCH1 resources and the PUCCH2 resources.

[0086] In this scenario, UE 115 will again use one of the various methods to select a first PUSCH resource that overlaps with a PUCCH1 resource from one or more PUSCHs. Then, UE 115 will again use one of the various selection criteria to select another PUSCH resource that overlaps with a PUCCH2 resource from the multiple PUSCH resources. In multiplexing stage 501, UE 115 will multiplex UCI 1 onto PUSCH 1 resources and UCI2 onto PUSCH2 resources. Similarly, UE 115 will then send PUSCH 1 including UCI1 and PUSCH2 including UCI2 to one or both of TRPs 105x and 105y without sending PUCCH 1 resources or PUCCH2 resources.

[0087] Fig. 6A 6 is a block diagram illustrating a UE 115 configured for UCI message multiplexing onto PUSCH resources across different TRPs according to various aspects of the present disclosure. A UCI message multiplexing procedure 60 provides a second optional aspect according to the present disclosure. Within a determination phase 600, the UE 115 determines that at least one PUSCH resource among a plurality of PUSCH resources (i.e., a PUSCH1 resource and a PUSCH2 resource) overlaps with at least one of a PUCCH 1 resource and a PUCCH2 resource. The UCI message multiplexing procedure 60 includes: the UE 115 uses one of a plurality of selection criteria to select a first PUSCH resource from the PUSCH 1 resource and the PUSCH2 resource that overlap with the PUCCH 1 resource. The UE 115 selects PUSCH 1 that overlaps with PUCCH 1 in the time domain.

[0088] In the first multiplexing stage 601, the UE 115 multiplexes UCI1 onto PUSCH1. Also in the first multiplexing stage 601, the UE 115 uses one or more selection criteria to select another PUSCH resource overlapping with the PUCCH2 resource from the multiple PUSCH resources. Fig. 6A As illustrated, UE 115 selects PUSCH2 resources that overlap with PUCCH2 resources in the time domain. In the second multiplexing stage 602, UE 115 multiplexes UCI12 onto PUSCH2 resources. Then, UE 115 may send PUSCH1 resources including UCI1 and PUSCH2 resources including UCI2 to one or both of TRPs 105x and 105y, and not send PUCCH 1 resources and PUCCH2 resources.

[0089] Figure 6B 6 is a block diagram illustrating a UE 115 configured for multiplexing of UCI messages onto PUSCH resources across different TRPs according to various aspects of the present disclosure. In a variation of the second optional aspect, the PUSCH resource selected by the UE 115 may result in the selected PUSCH resource being the same PUSCH resource. For example, in the determination phase 600, the UE 115 uses one of a plurality of selection criteria to select a PUSCH1 resource for one or more first UCIs (e.g., UCI1) in a PUCCH 1 resource that overlaps in the time domain. The UE 115 multiplexes UCI1 onto the PUSCH1 resource in a first multiplexing phase 601. Within the first multiplexing phase 601, the UE 115 also selects a PUSCH1 resource for one or more second UCIs (e.g., UCI2) in a PUCCH2 resource that overlaps in the time domain. The UE 115 also multiplexes UCI2 onto the PUSCH1 resource in a second multiplexing phase 602. UE 115 may then send PUSCH1 resources including both UCI1 and UCI2 and PUSCH2 resources to one or both of TRPs 105x and 105y without sending PUCCH1 resources or PUCCH2 resources.

[0090] Fig. 7Ais a block diagram illustrating a UE 115 configured for UCI message multiplexing onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure. A UCI message multiplexing procedure 70 provides a third optional aspect in accordance with the present disclosure. The third optional aspect provides that the UE 115 selects one PUSCH resource that overlaps in the time domain with a PUCCH resource having an earliest start time among a plurality of PUSCH resources determined in the determination phase 700 to overlap with one or more PUCCH resources among a plurality of PUCCH resources available for simultaneous PUCCH transmission (i.e., PUCCH1 resources and PUCCH2 resources). In this third optional aspect, PUCCH2 has the earliest start time.

[0091] like Fig. 7A As illustrated, the PUCCH1 resource and the PUCCH2 resource have the same start time. In this instance, the UE 115 selects the PUCCH resource based on the associated CORESET pool index value of the PUCCH resource. In one example implementation, the UE 115 may select the PUCCH resource associated with the highest CORESET pool index value. Alternative implementations may use the lowest CORESET pool index value or other criteria. In the illustrated example, the PUCCH 2 resource is associated with the highest CORESET pool index value. Therefore, the UE 115 selects the PUSCH resource that overlaps with PUCCH2 in the time domain, i.e., PUSCH1, from among multiple PUSCH resources. As described above, the UE 115 selects the PUSCH resource using one of multiple criteria.

[0092] In the first multiplexing stage 701, UE 115 multiplexes UCI2 onto PUSCH1 resources and selects another PUSCH resource, i.e., PUSCH2 resource, from multiple PUSCH resources that overlaps with the later start time PUCCH resource (i.e., PUCCH1 resource) in the time domain. Similarly, UE 115 selects PUSCH2 resources using one of a plurality of criteria. Then, UE 115 multiplexes UCI1 onto PUSCH2 resources at the second multiplexing stage 702. UE 115 transmits PUSCH 1 including UCI2 and PUSCH2 including UCI 1 to one or both of TRPs 105x and 105y without transmitting PUCCH 1 resources or PUCCH2 resources.

[0093] Figure 7B700 is a block diagram illustrating a UE 115 configured for multiplexing of UCI messages onto PUSCH resources across different TRPs according to various aspects of the present disclosure. The UCI message multiplexing procedure 71 provides a variation according to the third optional aspect of the present disclosure, in which the PUSCH resource selected by the UE 115 may result in the selection of the same PUSCH resource. For example, in the determination phase 700, the UE 115 uses one of a plurality of selection criteria to select a PUSCH1 resource that overlaps with a PUCCH resource (e.g., PUCCH2) having the earliest start time in the time domain from one or more PUSCH resources. The UE 115 multiplexes UCI2 onto the PUSCH1 resource in a first multiplexing phase 701, and also selects a PUSCH1 resource that overlaps with a PUCCH resource (e.g., PUCCH1) having a later start time in the time domain from one or more PUSCH resources as a PUSCH resource. The UE 115 also multiplexes UCI1 onto the PUSCH1 resource in a second multiplexing phase 702. UE 115 may then send PUSCH 1 resources including both UCI1 and UCI2 and PUSCH2 resources to one or both of TRPs 105x and 105y without sending PUCCH 1 resources or PUCCH2 resources.

[0094] Fig. 8A 8 is a block diagram illustrating a UE 115 configured for UCI message multiplexing onto PUSCH resources across different TRPs according to various aspects of the present disclosure. A UCI message multiplexing procedure 80 provides a fourth optional aspect according to the present disclosure. In a determination phase 800, the UE 115 determines that at least one PUSCH resource among a plurality of PUSCH resources (i.e., a PUSCH1 resource and a PUSCH2 resource) overlaps with at least one of a PUCCH 1 resource and a PUCCH2 resource. The UCI message multiplexing procedure 80 includes: the UE 115 uses one of a plurality of selection criteria to select a first PUSCH resource from the PUSCH 1 resource and the PUSCH2 resource that overlap with the PUCCH 1 resource. The UE 115 selects PUSCH 1 that overlaps with PUCCH 1 in the time domain.

[0095] In the first multiplexing stage 801, the UE 115 multiplexes UCI1 onto PUSCH1. Also in the first multiplexing stage 801, the UE 115 selects another PUSCH resource overlapping with the PUCCH2 resource from the remaining multiple PUSCH resources except the PUSCH1 resource using one of the multiple selection criteria. Fig. 8AAs illustrated, UE 115 selects a PUSCH2 resource that overlaps with a PUCCH2 resource in the time domain. In the second multiplexing stage 802, UE 115 multiplexes UCI2 onto the PUSCH2 resource. Then, UE 115 may send a PUSCH1 resource including UCI1 and a PUSCH2 resource including UCI2 to one or both of TRPs 105x and 105y, and may not send PUCCH1 resources and PUCCH2 resources.

[0096] Figure 8B 800 is a block diagram illustrating a UE 115 configured for multiplexing of UCI messages onto PUSCH resources across different TRPs in accordance with various aspects of the present disclosure. UCI message multiplexing procedure 81 provides a variation of the fourth optional aspect. The process within determining stage 800 is similar to Fig. 8A The determination stage 800 in is performed similarly, and the UE 115 selects PUSCH1 which overlaps with PUCCH1 in the time domain. However, among the remaining multiple PUSCH resources, the PUSCH2 resource does not overlap with PUCCH2. Since Rel.18 currently does not support simultaneous PUCCH / PUSCH transmission, the UE 115 cannot simply transmit PUCCH2 resources, PUSCH 1 resources with UCI 1, and PUSCH2 resources. Since UCI with HARQ-ACK / NACK takes precedence over PUSCH resources, the UE 115 should not discard PUCCH2 or PUSCH1 with UCI1. Figure 8B As illustrated, in response to a failure that the remaining PUSCH resources overlap with the PUCCH2 resources, the UE 115 declares an error state. In the case where the error state is declared, the network may not perform such scheduling, or if such scheduling occurs, the UE 115 may determine which of the PUCCH resources or the PUSCH to send. For example, the UE 115 may simultaneously send the PUCCH 1 resources and the PUCCH 2 resources and discard the PUSCH 1 resources and the PUSCH 2 resources, or the UE 115 may discard the PUCCH 2 and simultaneously send the PUSCH 1 including the UCI 1 and the PUSCH 2, or the UE may send nothing.

[0097] It should be noted that, as an alternative to declaring an error state, UE 115 may fall back to a different optional aspect. For example, when an error state situation occurs, UE 115 may fall back to the second optional aspect or the third optional aspect, wherein each of the UCIs of the overlapping PUCCH resources may be multiplexed onto the same selected overlapping PUSCH resources.

[0098] Fig. 91 is a block diagram illustrating a UE 115 configured for multiplexing of UCI messages on PUSCH resources across different TRPs according to various aspects of the present disclosure. UCI message multiplexing procedure 90 provides a fifth optional aspect according to the present disclosure. Similar to the third optional aspect, as Fig. 7A and Figure 7B As illustrated, in the determination phase 900, the UE 115 selects one of the multiple overlapping PUSCH resources that overlaps with the PUCCH resource having the earliest start time in the time domain. The UE 115 identifies the PUCCH2 resource as having an earlier start time than the PUCCH1 resource. Then, the UE 115 selects the PUSCH 1 resource because it overlaps with the PUCCH2 resource in the time domain.

[0099] and Fig. 7A As with the illustrated third optional aspect, if any two or more overlapping PUCCH resources have the same starting time, the UE 115 may select the first PUCCH resource based on one of a variety of criteria, such as a CORESET pool index value associated with the PUCCH resource.

[0100] At the first multiplexing stage 901, the UE 115 multiplexes UCI2 onto the PUSCH1 resource. The UE 115 also identifies the next PUSCH resource that overlaps with the PUCCH resource with a later start time (e.g., the PUCCH1 resource) among the remaining multiple PUSCH resources other than the PUSCH 1 resource. Since the PUSCH2 resource overlaps with the PUCCH1 resource that starts later, the UE 115 may further select the PUSCH2 resource as the next PUSCH resource. At the second multiplexing stage 902, the UE 115 multiplexes UCI1 onto the PUSCH2 resource. Then, the UE 115 may send the PUSCH 1 resource including UCI2 and the PUSCH2 resource including UCI 1 to one or both of the TRPs 105x and 105y without sending the PUCCH 1 resource and the PUCCH2 resource.

[0101] It should be noted that similar to the fourth optional aspect, after selecting a PUSCH resource that overlaps with a PUCCH resource with an earlier start time in the time domain, if none of the remaining PUSCH resources in the plurality of overlapping PUSCH resources overlaps with a PUCCH resource with a later start time, the UE 115 may fall back to the operation of the second optional aspect or the third optional aspect, or declare an error state, such as regarding Figure 8B As pointed out.

[0102] Fig. 10A1 is a block diagram illustrating a UE 115 configured for multiplexing of UCI messages onto PUSCH resources across different TRPs according to various aspects of the present disclosure. UCI message multiplexing procedure 1000 provides a sixth optional aspect according to the present disclosure. At a determination stage 1002, the UE 115 determines that PUCCH 1 resources and PUCCH 2 resources overlap in the time domain and can be used for simultaneous PUCCH transmission. The UE 115 also determines that multiple PUSCH resources (i.e., PUSCH 1 resources and PUSCH 2 resources) overlap with at least one of the PUCCH 1 resources and the PUCCH 2 resources. At a first multiplexing stage 1003, the UE 115 multiplexes UCI1 and UCI2 into a single PUCCH resource (e.g., a new PUCCH resource, i.e., a PUCCH 3 resource). The UE 115 may then determine whether any of the multiple overlapping PUSCH resources overlaps with the PUCCH 3 resource in the time domain. At the second multiplexing stage 1004, UE 115 uses one of a plurality of selection criteria to multiplex UCI1 and UCI2 from PUCCH3 onto PUSCH2. UE 115 may then send PUSCH1 resources and PUSCH2 resources with UCI1 and UCI2 to one or both of TRPs 105x and 105y without sending PUCCH3 resources.

[0103] Fig. 10B 1 is a block diagram illustrating a UE 115 configured for multiplexing of UCI messages onto PUSCH resources across different TRPs according to various aspects of the present disclosure. A UCI message multiplexing procedure 1001 provides a variation according to the sixth optional aspect of the present disclosure. After a determination phase 1002 in which the UE 115 identifies PUCCH1 resources and PUCCH2 resources as overlapping and available for simultaneous transmission and identifies PUSCH1 resources and PUSCH2 resources as overlapping with at least one of PUCCH1 resources or PUCCH2 resources in the time domain and a first multiplexing phase 1003 in which the UE 115 multiplexes UCI1 and UCI2 onto PUCCH3 resources, the UE 115 determines that neither the PUSCH1 resources nor the PUSCH2 resources overlap with the PUCCH3 resources. In this scenario, because PUCCH3 resources do not overlap with PUSCH1 resources or PUSCH2 resources in the time domain, UE 115 may send PUCCH3 resources including UCI 1 and UCI2, PUSCH1 resources, and PUSCH2 resources to one or both of TRPs 105x and 105y.

[0104] about FIG. 5A to FIG. 10BThe various aspects of the disclosure illustrated and described present six optional aspects of the disclosure that define UCI multiplexing across different CORESET pool index values. It should be noted that the first to fifth optional aspects may be performed under one of the following conditions: in condition 1, the UCI message may be multiplexed onto overlapping PUSCH resources without regard to the CORESET pool index value associated with each of the one or more PUSCH resources overlapping with the one or more PUCCH resources; in condition 2, during the determination phase, the UE 115 determines that at least one of the PUCCH1 resource or the PUCCH2 resource does not overlap with any PUSCH resource (in any CC) associated with the same CORESET pool index value as the PUCCH resource; and in condition 3, in addition to condition 2, it also includes that at least one PUCCH in condition 2 overlaps with one or more PUSCH resources (in any CC) associated with a CORESET pool index value different from the CORESET pool index value associated with the PUCCH. The sixth optional aspect may be performed under condition 3, in which case simultaneous PUCCH transmission may be problematic.

[0105] about FIG. 5A to FIG. 10B Any one or more of the first optional aspect to the sixth optional aspect illustrated and described may be enabled by a wireless specification. Alternatively, one of the sixth optional aspects may be enabled via RRC signaling. For example, in FIG. 5A to FIG. 10B In each of the above, at a time before the UCI signal multiplexing procedure is performed, one of TRPs 105x or 105y may send an RRC signal that will enable any one of the first optional aspect to the sixth optional aspect in UE 115. Alternatively, the RRC signaling may provide for the enabling of one of the six optional aspects based on the presence of one of the conditions indicated (i.e., conditions 1-3).

[0106] It should be noted that for each of the first to sixth optional aspects, when dynamically scheduled channels such as channels scheduled via DCI are involved, the joint timeline should be met for UCI multiplexing on PUCCH or PUSCH resources.

[0107] It should be noted that reference Figure 4 One or more blocks (or operations) described herein may be combined with one or more blocks (or operations) described in another figure in the reference figure. Figure 5A One or more boxes (or operations) of Fig. 9 As another example, with Figure 7B One or more boxes associated with Fig. 6A As another example, Figure 4 One or more boxes associated with Figure 1 to Figure 2 One or more associated boxes (or operations) are combined. Additionally or alternatively, the above reference Figure 1 to Figure 2 One or more of the operations described may be combined with reference to Fig.11 One or more combinations of the above operations.

[0108] In one or more aspects, a technique for supporting multiplexing of UCI messages onto PUSCH resources across different base stations may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes or devices described elsewhere herein. In one or more aspects, supporting multiplexing of UCI messages onto PUSCH resources across different base stations may include a device configured to determine that a first PUCCH resource including one or more first UCI messages associated with a first CORE SET pool index value overlaps in the time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORE SET pool index value. The device may be further configured to identify one or more PUSCH resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain. The device may be further configured to multiplex one or more of the one or more first UCI messages and one or more of the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources, and to send the one or more PUSCH resources on the associated component carrier after multiplexing. Additionally, the device may be performed or operated according to one or more aspects as described below.

[0109] In some specific implementations, the apparatus includes a wireless device, such as a UE. In some specific implementations, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other specific implementations, the apparatus may include a non-transitory computer-readable medium having a program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some specific implementations, the apparatus may include one or more components configured to perform the operations described herein. In some specific implementations, the method of wireless communication may include one or more operations described herein with reference to the apparatus.

[0110] A first aspect of wireless communication performed by a UE includes: determining, by the UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps in the time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value; identifying, by the UE, one or more PUSCH resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and sending, by the UE, the one or more PUSCH resources on an associated component carrier after the multiplexing.

[0111] In a second aspect, alone or in combination with the first aspect, wherein the associated component carrier is one of: a same component carrier as a PUCCH component carrier on which the first PUCCH resource and the second PUCCH resource may be simultaneously transmitted or a different component carrier.

[0112] In a third aspect, alone or in combination with one or more of the first and second aspects, the identifying the one or more PUSCH resources comprises: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with both the first PUCCH resource and the second PUCCH resource, wherein the multiplexing comprises multiplexing the one or more first UCI messages and the one or more second UCI messages onto the first PUSCH resource.

[0113] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the identifying the one or more PUSCH resources includes: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; and identifying a second PUSCH resource among the one or more PUSCH resources that overlaps with the second PUCCH resource, wherein the one or more second UCI messages are multiplexed onto the second PUSCH resource, wherein the sending includes sending the first PUSCH resource and the second PUSCH resource.

[0114] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the identifying of the first PUSCH resource and the second PUSCH resource is in response to the UE determining that a single PUSCH resource among the one or more PUSCH resources fails to overlap with both the first PUCCH resource and the second PUCCH resource.

[0115] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first PUCCH resource is scheduled earlier than the second PUCCH resource in the time domain.

[0116] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, when the first PUCCH resource has the same start time as the second PUCCH resource, the UE identifies the first PUSCH overlapping with the first PUCCH resource having the one or more first UCI messages associated with the first CORESET pool index value, and the first CORESET pool index value is one of a higher value or a lower value than the second CORESET pool index value associated with the one or more second UCI messages of the second PUCCH resource.

[0117] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the first PUSCH resource and the second PUSCH resource are the same PUSCH resource.

[0118] In a ninth aspect, alone or in combination with one or more of aspects 1 to 8, the identifying the one or more PUSCHs comprises: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; determining whether any remaining PUSCH resources among the one or more PUSCH resources excluding the first PUSCH resource overlap with the second PUCCH resource, wherein in response to at least one PUSCH resource overlapping with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the second PUSCH resource among the at least one PUSCH resource, and wherein in response to the one or more PUSCH resources excluding the first PUSCH resource not overlapping with the second PUCCH resource, one of the following: when the first PUSCH resource also overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the first PUSCH resource; or declaring an error state by the UE, wherein the UE avoids the multiplexing and the sending of the one or more PUSCH resources.

[0119] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first PUCCH resource is identified as being earlier than the second PUCCH resource in the time domain.

[0120] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, it also includes: multiplexing the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH resources by the UE; determining by the UE whether any PUSCH resource among the one or more PUSCH resources overlaps with the multiplexed PUCCH resources, wherein in response to at least one PUSCH resource among the one or more PUSCH resources overlapping with the multiplexed PUCCH resources, the one or more first UCI messages and the one or more second UCI messages are multiplexed onto the first PUSCH resource among the at least one PUSCH resource, and wherein in response to the one or more PUSCH resources not overlapping with the multiplexed PUCCH resources, the multiplexed PUCCH resources and the one or more PUSCH resources are sent by the UE.

[0121] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, wherein the multiplexing of the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH and the determining whether the PUSCH resource overlaps with the multiplexed PUCCH resource are performed in response to: an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with at least one PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the at least one PUSCH resource is different from the corresponding CORESET pool index value associated with the at least one PUCCH resource; and an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the any PUSCH resource is equal to the corresponding CORESET pool index value associated with the at least one PUCCH resource.

[0122] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, it also includes: receiving, by the UE, an RRC message including a PUSCH multiplexing parameter, the PUSCH multiplexing parameter identifier being used to identify a predetermined procedure for the one or more PUSCH resources that overlap with the first PUCCH resource or the second PUCCH resource in the time domain.

[0123] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, wherein the multiplexing of the one or more first UCI messages and the one or more second UCI messages onto the one or more PUSCH resources of the one or more PUSCH resources includes one or more of the following: identification of the one or more PUSCH resources, without considering the CORESET pool values ​​associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resource and the second PUCCH resource; identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource of the one or more PUSCH resources, wherein the CORESET pool value associated with the at least one PUSCH resource is equal to the corresponding CORESET pool value associated with the at least one PUCCH resource. SET pool value; or an identifier of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with at least one PUSCH resource, wherein the CORESET pool value associated with the at least one PUSCH resource is different from the corresponding CORESET pool value associated with the at least one PUCCH resource.

[0124] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, it also includes: avoiding sending the first PUCCH resource and the second PUCCH resource by the UE in response to sending the one or more PUSCH resources.

[0125] A sixteenth aspect may include a UE configured for wireless communication, the UE comprising: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: determine, by the UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value in a time domain; identify, by the UE, one or more PUSCH resources overlapping with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplex, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and send, by the UE, the one or more PUSCH resources on an associated component carrier after performing the configuration for multiplexing.

[0126] In a seventeenth aspect, alone or in combination with the sixteenth aspect, the associated component carrier is one of: a component carrier that is the same as a PUCCH component carrier on which the first PUCCH resource and the second PUCCH resource may be simultaneously transmitted or a different component carrier.

[0127] In the eighteenth aspect, alone or in combination with one or more of the sixteenth aspect and the seventeenth aspect, the configuration of the at least one processor for identifying the one or more PUSCH resources includes the configuration of the at least one processor for the following operations: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with both the first PUCCH resource and the second PUCCH resource, wherein the configuration of the at least one processor for multiplexing includes the configuration of the at least one processor for the following operations: multiplexing the one or more first UCI messages and the one or more second UCI messages onto the first PUSCH resource.

[0128] In the nineteenth aspect, alone or in combination with one or more of the sixteenth to eighteenth aspects, the configuration of the at least one processor for identifying the one or more PUSCH resources includes the configuration of the at least one processor for the following operations: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; and identifying a second PUSCH resource among the one or more PUSCH resources that overlaps with the second PUCCH resource, wherein the one or more second UCI messages are multiplexed onto the second PUSCH resource, wherein the configuration of the at least one processor for sending includes the configuration of the at least one processor for the following operations: sending the first PUSCH resource and the second PUSCH resource.

[0129] In the twentieth aspect, alone or in combination with one or more of aspects 16 to 19, the configuration of the at least one processor for identifying the first PUSCH resource and the second PUSCH resource is in response to the UE determining that a single PUSCH resource among the one or more PUSCH resources fails to overlap with both the first PUCCH resource and the second PUCCH resource.

[0130] In a twenty-first aspect, alone or in combination with one or more of the sixteenth to twentieth aspects, the first PUCCH resource is scheduled earlier than the second PUCCH resource in the time domain.

[0131] In the twenty-second aspect, alone or in combination with one or more of aspects sixteen to twenty-first aspects, wherein when the first PUCCH resource has the same start time as the second PUCCH resource, the UE identifies the first PUSCH overlapping with the first PUCCH resource having the one or more first UCI messages associated with the first CORESET pool index value, and the first CORESET pool index value is one of a higher value or a lower value than the second CORESET pool index value associated with the one or more second UCI messages of the second PUCCH resource.

[0132] In a twenty-third aspect, alone or in combination with one or more of aspects sixteen to twenty-second, wherein the first PUSCH resource and the second PUSCH resource are the same PUSCH resource.

[0133] In a twenty-fourth aspect, alone or in combination with one or more of aspects 16 to 23, the configuration of the at least one processor for identifying the one or more PUSCHs includes the configuration of the at least one processor for the following operations: identifying a first PUSCH resource of the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; determining whether any remaining PUSCH resources of the one or more PUSCH resources excluding the first PUSCH resource overlap with the second PUCCH resource, wherein in response to at least one PUSCH The resource overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the second PUSCH resource of the at least one PUSCH resource, and in response to the one or more PUSCH resources excluding the first PUSCH resource not overlapping with the second PUCCH resource, one of the following: when the first PUSCH resource also overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the first PUSCH resource; or the UE declares an error state, wherein the UE avoids execution of the configuration of the at least one processor for multiplexing and sending the one or more PUSCH resources.

[0134] In a twenty-fifth aspect, alone or in combination with one or more of the sixteenth to twenty-fourth aspects, the first PUCCH resource is identified as being earlier than the second PUCCH resource in the time domain.

[0135] In the twenty-sixth aspect, alone or in combination with one or more of aspects from the sixteenth to the twenty-fifth aspect, it also includes: the configuration of the at least one processor for the following operations: multiplexing the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH resources through the UE; determining through the UE whether any PUSCH resource among the one or more PUSCH resources overlaps with the multiplexed PUCCH resources, wherein in response to at least one PUSCH resource among the one or more PUSCH resources overlapping with the multiplexed PUCCH resources, the one or more first UCI messages and the one or more second UCI messages are multiplexed onto the first PUSCH resource among the at least one PUSCH resource, and wherein in response to the one or more PUSCH resources not overlapping with the multiplexed PUCCH resources, the configuration of the at least one processor for the following operations is executed: sending the multiplexed PUCCH resources and the one or more PUSCH resources through the UE.

[0136] In the twenty-seventh aspect, alone or in combination with one or more of aspects from the sixteenth to the twenty-sixth aspects, the configuration of the at least one processor for multiplexing the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH and the configuration of the at least one processor for determining whether the PUSCH resource overlaps with the multiplexed PUCCH are performed in response to: an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with at least one PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the at least one PUSCH resource is different from the corresponding CORESET pool index value associated with the at least one PUCCH resource; and an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the any PUSCH resource is equal to the corresponding CORESET pool index value associated with the at least one PUCCH resource.

[0137] In the twenty-eighth aspect, alone or in combination with one or more of aspects from the sixteenth to the twenty-seventh aspect, it also includes: the configuration of the at least one processor for the following operations: receiving, by the UE, an RRC message including a PUSCH multiplexing parameter, the PUSCH multiplexing parameter identifier being used to identify a predetermined procedure for the one or more PUSCH resources that overlap with the at least one of the first PUCCH resource or the second PUCCH resource in the time domain.

[0138] In the twenty-ninth aspect, alone or in combination with one or more of the sixteenth to twenty-eighth aspects, the configuration of the at least one processor for multiplexing the one or more first UCI messages and the one or more second UCI messages onto the one or more PUSCH resources of the one or more PUSCH resources includes one or more of the following: identification of the one or more PUSCH resources without considering the CORESET pool value associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resource and the second PUCCH resource; An identifier of at least one PUCCH resource in the UCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool value associated with the at least one PUSCH resource is equal to the corresponding CORESET pool value associated with the at least one PUCCH resource; or an identifier of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with the at least one PUSCH resource, wherein the CORESET pool value associated with the at least one PUSCH resource is different from the corresponding CORESET pool value associated with the at least one PUCCH resource.

[0139] In the thirtieth aspect, alone or in combination with one or more of aspects from sixteen to twenty-ninth aspect, it also includes: the configuration of the at least one processor for the following operation: avoiding the sending of the first PUCCH resource and the second PUCCH resource by the UE in response to the execution of the configuration of the at least one processor for sending the one or more PUSCH resources.

[0140] A thirty-first aspect may include a UE configured for wireless communication, including: a component for determining, by the UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORE SET pool index value overlaps with a second PUCCH resource including one or more second UCI messages associated with a second CORE SET pool index value in the time domain; a component for identifying, by the UE, one or more PUSCH resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; a component for multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and a component for sending, by the UE, the one or more PUSCH resources on an associated component carrier after the component for multiplexing.

[0141] In the thirty-second aspect, alone or in combination with the thirty-first aspect, the associated component carrier is one of: the same component carrier as the PUCCH component carrier on which the first PUCCH resource and the second PUCCH resource can be sent simultaneously or a different component carrier.

[0142] In aspect thirty-third, alone or in combination with one or more of aspects thirty-first and thirty-second, the component for identifying the one or more PUSCH resources includes: a component for identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with both the first PUCCH resource and the second PUCCH resource, wherein the component for multiplexing includes a component for multiplexing the one or more first UCI messages and the one or more second UCI messages onto the first PUSCH resource.

[0143] In aspect 34, alone or in combination with one or more of aspects 31 to 33, the component for identifying the one or more PUSCH resources includes: a component for identifying a first PUSCH resource overlapping with the first PUCCH resource among the one or more PUSCH resources, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; and a component for identifying a second PUSCH resource overlapping with the second PUCCH resource among the one or more PUSCH resources, wherein the one or more second UCI messages are multiplexed onto the second PUSCH resource, wherein the component for sending includes a component for sending the first PUSCH resource and the second PUSCH resource.

[0144] In aspect thirty-fifth, alone or in combination with one or more of aspects thirty-first to thirty-fourth, the component for identifying the first PUSCH resource and the second PUSCH resource is responsive to the UE determining that a single PUSCH resource among the one or more PUSCH resources fails to overlap with both the first PUCCH resource and the second PUCCH resource.

[0145] In a thirty-sixth aspect, alone or in combination with one or more of aspects thirty-first to thirty-fifth, wherein the first PUCCH resource is scheduled earlier than the second PUCCH resource in the time domain.

[0146] In aspect 37, alone or in combination with one or more of aspects 31 to 36, when the first PUCCH resource has the same start time as the second PUCCH resource, the UE identifies the first PUSCH overlapping with the first PUCCH resource having the one or more first UCI messages associated with the first CORESET pool index value, the first CORESET pool index value being one of a higher value or a lower value than the second CORESET pool index value associated with the one or more second UCI messages of the second PUCCH resource.

[0147] In aspect 38, alone or in combination with one or more of aspects 31 to 37, wherein the first PUSCH resource and the second PUSCH resource are the same PUSCH resource.

[0148] In the thirty-ninth aspect, alone or in combination with one or more of aspects 31 to 38, the component for identifying the one or more PUSCHs includes: a component for identifying a first PUSCH resource overlapping with the first PUCCH resource among the one or more PUSCH resources, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; a component for determining whether any remaining PUSCH resources of the one or more PUSCH resources excluding the first PUSCH resource overlap with the second PUCCH resource, wherein in response to at least one PUSCH resource overlapping with the second PUCCH resource, The one or more second UCI messages are multiplexed onto a second PUSCH resource among the at least one PUSCH resource, and wherein in response to the one or more PUSCH resources excluding the first PUSCH resource not overlapping with the second PUCCH resource, one of the following: when the first PUSCH resource also overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the first PUSCH resource; or a component for declaring an error state by the UE, wherein the UE avoids executing the component for multiplexing and the component for sending the one or more PUSCH resources.

[0149] In the 40th aspect, alone or in combination with one or more of the 31st to 39th aspects, the first PUCCH resource is identified as being earlier than the second PUCCH resource in the time domain.

[0150] In the forty-first aspect, alone or in combination with one or more of aspects 31 to 40, it also includes: a component for multiplexing the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH resources through the UE; a component for determining through the UE whether any PUSCH resource of the one or more PUSCH resources overlaps with the multiplexed PUCCH resources, wherein in response to at least one PUSCH resource of the one or more PUSCH resources overlapping with the multiplexed PUCCH resources, the one or more first UCI messages and the one or more second UCI messages are multiplexed onto a first PUSCH resource of at least one PUSCH resource, and wherein in response to the one or more PUSCH resources not overlapping with the multiplexed PUCCH resources, a component for sending the multiplexed PUCCH resources and the one or more PUSCH resources through the UE.

[0151] In aspect 42, alone or in combination with one or more of aspects 31 to 41, the component for multiplexing the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH and the component for determining whether the PUSCH resource overlaps with the multiplexed PUCCH resource are performed in response to: identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with at least one PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the at least one PUSCH resource is different from the corresponding CORESET pool index value associated with the at least one PUCCH resource; and identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the any PUSCH resource is equal to the corresponding CORESET pool index value associated with the at least one PUCCH resource.

[0152] In the 43rd aspect, alone or in combination with one or more of aspects 31 to 42, it also includes: a component for receiving, through the UE, an RRC message including a PUSCH multiplexing parameter, the PUSCH multiplexing parameter identifier being a predetermined procedure of the component for identifying the one or more PUSCH resources overlapping with the at least one of the first PUCCH resource or the second PUCCH resource in the time domain.

[0153] In aspect 44, alone or in combination with one or more of aspects 31 to 43, the component for multiplexing the one or more first UCI messages and the one or more second UCI messages onto the one or more PUSCH resources of the one or more PUSCH resources includes one or more of the following: identification of the one or more PUSCH resources, without considering the CORESET pool value associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resource and the second PUCCH resource; identification of the one or more PUSCH resources, without considering the CORESET pool value associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resource and the second PUCCH resource; identification of the one or more PUSCH resources, without considering the CORESET pool value associated with the one or more PUSCH resources overlapping with the first PUCCH resource or ... An identifier of at least one PUCCH resource in the first PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool value associated with the at least one PUSCH resource is equal to the corresponding CORESET pool value associated with the at least one PUCCH resource; or an identifier of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with the at least one PUSCH resource, wherein the CORESET pool value associated with the at least one PUSCH resource is different from the corresponding CORESET pool value associated with the at least one PUCCH resource.

[0154] In the 45th aspect, alone or in combination with one or more of the 31st to 44th aspects, it also includes: a component for avoiding the transmission of the first PUCCH resource and the second PUCCH resource by the UE in response to the component for sending the one or more PUSCH resources.

[0155] The forty-sixth aspect may include a non-transitory computer-readable medium having a program code recorded thereon. The program code includes: a program code executable by a computer to enable the computer to determine, through the UE, that a first PUCCH resource including one or more first UCI messages associated with a first CORESET pool index value overlaps with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value in the time domain; a program code executable by a computer to enable the computer to identify, through the UE, one or more PUSCH resources overlapping with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; a program code executable by a computer to enable the computer to multiplex one or more of the one or more first UCI messages and the one or more second UCI messages to one or more PUSCH resources among the one or more PUSCH resources through the UE; and a program code executable by a computer to enable the computer to send the one or more PUSCH resources on an associated component carrier through the UE after executing the program code executable by the computer to enable the computer to multiplex.

[0156] In a 47th aspect, alone or in combination with the 46th aspect, the associated component carrier is one of: the same component carrier as the PUCCH component carrier on which the first PUCCH resource and the second PUCCH resource can be sent simultaneously or a different component carrier.

[0157] In the 48th aspect, alone or in combination with one or more of the 46th aspect and the 47th aspect, the program code executable by the computer for causing the computer to identify the one or more PUSCH resources includes a program code executable by the computer for causing the computer to identify and perform the following operations: a first PUSCH resource among the one or more PUSCH resources that overlaps with both the first PUCCH resource and the second PUCCH resource, wherein the program code executable by the computer for causing the computer to multiplex includes a program code executable by the computer for causing the computer to perform the following operations: multiplexing the one or more first UCI messages and the one or more second UCI messages onto the first PUSCH resource.

[0158] In the forty-ninth aspect, alone or in combination with one or more of aspects forty-six to forty-eight, the program code executable by the computer for causing the computer to identify the one or more PUSCH resources includes program code executable by the computer for causing the computer to perform the following operations: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; and identifying a second PUSCH resource among the one or more PUSCH resources that overlaps with the second PUCCH resource, wherein the one or more second UCI messages are multiplexed onto the second PUSCH resource, wherein the program code executable by the computer for causing the computer to send includes configuration of the at least one processor for the following operations: sending the first PUSCH resource and the second PUSCH resource.

[0159] In the fiftieth aspect, alone or in combination with one or more of aspects 46 to 49, the program code executable by the computer to cause the computer to identify the first PUSCH resource and the second PUSCH resource in response to the UE determining that a single PUSCH resource among the one or more PUSCH resources fails to overlap with both the first PUCCH resource and the second PUCCH resource.

[0160] In the fifty-first aspect, alone or in combination with one or more of the forty-sixth to fiftieth aspects, the first PUCCH resource is scheduled earlier than the second PUCCH resource in the time domain.

[0161] In aspect 52, alone or in combination with one or more of aspects 46 to 51, wherein when the first PUCCH resource has the same start time as the second PUCCH resource, the UE identifies the first PUSCH overlapping with the first PUCCH resource having the one or more first UCI messages associated with the first CORESET pool index value, and the first CORESET pool index value is one of a higher value or a lower value than the second CORESET pool index value associated with the one or more second UCI messages of the second PUCCH resource.

[0162] In a fifty-third aspect, alone or in combination with one or more of aspects forty-six to fifty-second, wherein the first PUSCH resource and the second PUSCH resource are the same PUSCH resource.

[0163] In a fifty-fourth aspect, alone or in combination with one or more of aspects forty-six to fifty-third, the program code executable by the computer for causing the computer to identify the one or more PUSCHs includes program code executable by the computer for causing the computer to perform the following operations: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; determining whether any remaining PUSCH resources of the one or more PUSCH resources excluding the first PUSCH resource overlap with the second PUCCH resource, wherein in response to At least one PUSCH resource overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto a second PUSCH resource among the at least one PUSCH resource, and in response to the one or more PUSCH resources excluding the first PUSCH resource not overlapping with the second PUCCH resource, one of the following: when the first PUSCH resource also overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the first PUSCH resource; or the UE declares an error state, wherein the UE avoids execution of the configuration of the at least one processor for multiplexing and sending the one or more PUSCH resources.

[0164] In a fifty-fifth aspect, alone or in combination with one or more of aspects forty-six to fifty-four, wherein the first PUCCH resource is identified as being earlier than the second PUCCH resource in the time domain.

[0165] In the fifty-sixth aspect, alone or in combination with one or more of aspects forty-six to fifty-fifth, it also includes: a program code executable by the computer to cause the computer to perform the following operations: multiplexing the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH resources through the UE; determining through the UE whether any PUSCH resource among the one or more PUSCH resources overlaps with the multiplexed PUCCH resources, wherein in response to at least one PUSCH resource among the one or more PUSCH resources overlapping with the multiplexed PUCCH resources, the one or more first UCI messages and the one or more second UCI messages are multiplexed onto the first PUSCH resource among the at least one PUSCH resource, and wherein in response to the one or more PUSCH resources not overlapping with the multiplexed PUCCH resources, executing the program code executable by the computer to cause the computer to perform the following operations: sending the multiplexed PUCCH resources and the one or more PUSCH resources through the UE.

[0166] In the fifty-seventh aspect, alone or in combination with one or more of aspects 46 to 56, the program code executable by the computer for causing the computer to multiplex the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH and the program code executable by the computer for causing the computer to determine whether the PUSCH resource overlaps with the multiplexed PUCCH resource are executed in response to: a determination that the first PUCCH resource or the second PUCCH resource overlaps with at least one of the one or more PUSCH resources. an identifier of at least one PUCCH resource of the first PUCCH resource or the second PUCCH resource, wherein the CORESET pool index value associated with the at least one PUSCH resource is different from the corresponding CORESET pool index value associated with the at least one PUCCH resource; and an identifier of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the any PUSCH resource is equal to the corresponding CORESET pool index value associated with the at least one PUCCH resource.

[0167] In the fifty-eighth aspect, alone or in combination with one or more of aspects 46 to 57, it also includes a program code executable by the computer to cause the computer to perform the following operations: receiving, through the UE, an RRC message including a PUSCH multiplexing parameter, the PUSCH multiplexing parameter identifying a predetermined procedure for the identifier to overlap with the one or more PUSCH resources that overlap with at least one of the first PUCCH resource or the second PUCCH resource in the time domain.

[0168] In the fifty-ninth aspect, alone or in combination with one or more of aspects fifty-six to fifty-eight, the program code executable by the computer to cause the computer to multiplex the one or more first UCI messages and the one or more second UCI messages onto the one or more PUSCH resources of the one or more PUSCH resources includes one or more of the following: identification of the one or more PUSCH resources, without regard to the CORESET pool value associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resource and the second PUCCH resource; an identifier of at least one PUCCH resource in the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool value associated with the at least one PUSCH resource is equal to the corresponding CORESET pool value associated with the at least one PUCCH resource; or an identifier of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with the at least one PUSCH resource, wherein the CORESET pool value associated with the at least one PUSCH resource is different from the corresponding CORESET pool value associated with the at least one PUCCH resource.

[0169] In the sixtieth aspect, alone or in combination with one or more of aspects from the forty-sixth to the fifty-ninth aspect, it also includes: a program code executable by the computer for causing the computer to perform the following operations: avoiding the sending of the first PUCCH resource and the second PUCCH resource by the UE in response to the execution of the program code executable by the computer for causing the computer to send the one or more PUSCH resources.

[0170] It will be appreciated by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. 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.

[0171] This article is about Figures 1 to 11The components, functional blocks and modules include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, firmware codes and other examples, or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions and other examples, whether referred to as software, firmware, middleware, microcode, hardware description language or other. In addition, the features discussed herein can be implemented via a dedicated processor circuit system, via executable instructions or a combination thereof.

[0172] The technician will further understand that the various exemplary logic blocks, modules, circuits and algorithm steps described in conjunction with the disclosure of this article can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been roughly described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing departure from the scope of the present disclosure. The technician will also easily recognize that the order or combination of components, methods or interactions described herein are only examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner other than the manner illustrated and described herein.

[0173] The various illustrative logic components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0174] The hardware and data processing apparatus for implementing the various exemplary logic components, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. In some specific implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuits specific to a given function.

[0175] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or in any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device.

[0176] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that may be implemented to transfer a computer program from one place to another. The storage medium may be any available medium that a computer can access. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that may be used to store the required program code in the form of an instruction or data structure and may be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0177] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0178] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions on a properly oriented page corresponding to the orientation of the drawing, and may not reflect the proper orientation of any device as implemented.

[0179] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to a subcombination or variations of a subcombination.

[0180] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations that are not depicted can be incorporated into the schematically illustrated example process. For example, one or more additional operations can be performed before, after, simultaneously or between any illustrated operations. In some environments, multitasking and parallel processing can be advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions narrated in the claims can be performed in different orders and still achieve the desired result.

[0181] As used herein, including in the claims, the term "or" used in a list of two or more items means that any one of the listed items may be taken alone, or any combination of two or more of the listed items may be taken. For example, if a composition is described as containing components A, B, or C, the composition may contain A alone; B alone; C alone; A and B combined; A and C combined; B and C combined; or A, B, and C combined. In addition, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one" indicates a separate list, 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) or any combination of any of these. The term "substantially" is defined as largely, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed implementation, the term "substantially" may be replaced with "within [percent] of" a specified content, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0182] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to be consistent with the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: determining, by the UE, that a first physical uplink control channel (PUCCH) including one or more first uplink control information (UCI) messages associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value; identifying, by the UE, one or more physical uplink shared channel (PUSCH) resources overlapping with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and The one or more PUSCH resources are transmitted by the UE on an associated component carrier after the multiplexing.

2. The method of claim 1, wherein the associated component carrier is one of: the same component carrier as a PUCCH component carrier on which the first PUCCH resource and the second PUCCH resource can be simultaneously transmitted or a different component carrier.

3. The method according to claim 1, wherein the identifying the one or more PUSCH resources comprises: A first PUSCH resource of the one or more PUSCH resources that overlaps with both the first PUCCH resource and the second PUCCH resource is identified, wherein the multiplexing includes multiplexing the one or more first UCI messages and the one or more second UCI messages onto the first PUSCH resource.

4. The method according to claim 1, The identifying the one or more PUSCH resources comprises: identifying a first PUSCH resource of the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; and identifying a second PUSCH resource overlapping with the second PUCCH resource among the one or more PUSCH resources, wherein the one or more second UCI messages are multiplexed onto the second PUSCH resource, The sending includes sending the first PUSCH resource and the second PUSCH resource.

5. The method of claim 4, wherein the identifying the first PUSCH resource and the second PUSCH resource is in response to the UE determining that a single PUSCH resource of the one or more PUSCH resources fails to overlap with both the first PUCCH resource and the second PUCCH resource. The method according to claim 4 , wherein the first PUCCH resource is scheduled earlier than the second PUCCH resource in the time domain.

7. The method of claim 4, wherein when the first PUCCH resource has the same start time as the second PUCCH resource, the UE identifies the first PUSCH overlapping with the first PUCCH resource having the one or more first UCI messages associated with the first CORESET pool index value, the first CORESET pool index value being one of a higher value or a lower value than the second CORESET pool index value associated with the one or more second UCI messages of the second PUCCH resource.

8. The method of claim 4, wherein the first PUSCH resource and the second PUSCH resource are the same PUSCH resource.

9. The method of claim 1, wherein the identifying the one or more PUSCH resources comprises: identifying a first PUSCH resource overlapping with the first PUCCH resource among the one or more PUSCH resources, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; determining whether any remaining PUSCH resources of the one or more PUSCH resources excluding the first PUSCH resource overlap with the second PUCCH resource, wherein in response to at least one PUSCH resource overlapping with the second PUCCH resource, the one or more second UCI messages are multiplexed onto a second PUSCH resource in the at least one PUSCH resource, and In response to the one or more PUSCH resources excluding the first PUSCH resource not overlapping with the second PUCCH resource, one of the following: When the first PUSCH resource also overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the first PUSCH resource; or An error condition is declared by the UE, wherein the UE avoids the multiplexing and the sending of the one or more PUSCH resources.

10. The method of claim 9, wherein the first PUCCH resource is identified as being earlier than the second PUCCH resource in the time domain.

11. The method according to claim 1, further comprising: multiplexing, by the UE, the one or more first UCI messages and the one or more second UCI messages onto a multiplexed PUCCH resource; determining, by the UE, whether any of the one or more PUSCH resources overlaps with the multiplexed PUCCH resource, wherein in response to at least one PUSCH resource of the one or more PUSCH resources overlapping with the multiplexed PUCCH resource, the one or more first UCI messages and the one or more second UCI messages are multiplexed onto a first PUSCH resource of the at least one PUSCH resource, and In response to the one or more PUSCH resources not overlapping with the multiplexed PUCCH resources, the multiplexed PUCCH resources and the one or more PUSCH resources are sent by the UE.

12. The method of claim 11, wherein the multiplexing of the one or more first UCI messages and the one or more second UCI messages onto a multiplexed PUCCH resource and the determining whether the PUSCH resource overlaps with the multiplexed PUCCH resource are performed in response to: an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with at least one PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the at least one PUSCH resource is different from a corresponding CORESET pool index value associated with the at least one PUCCH resource; and An identification of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the any PUSCH resource is equal to the corresponding CORESET pool index value associated with the at least one PUCCH resource.

13. The method according to claim 1, further comprising: A radio resource control (RRC) message including a PUSCH multiplexing parameter is received by the UE, the PUSCH multiplexing parameter identifying a predetermined procedure for identifying the one or more PUSCH resources overlapping with the at least one of the first PUCCH resource or the second PUCCH resource in the time domain.

14. The method of claim 1, wherein the multiplexing of the one or more of the one or more first UCI messages and the one or more second UCI messages onto the one or more PUSCH resources of the one or more PUSCH resources comprises one or more of the following: The identification of the one or more PUSCH resources disregards a CORESET pool value associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resources and the second PUCCH resources; an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool value associated with at least one PUSCH resource in the one or more PUSCH resources is equal to a corresponding CORESET pool value associated with the at least one PUCCH resource; or An identification of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with the at least one PUSCH resource, wherein the CORESET pool value associated with the at least one PUSCH resource is different from the corresponding CORESET pool value associated with the at least one PUCCH resource.

15. The method according to claim 1, further comprising: In response to the sending of the one or more PUSCH resources, sending of the first PUCCH resources and the second PUCCH resources is avoided by the UE.

16. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: determining, by the UE, that a first physical uplink control channel (PUCCH) including one or more first uplink control information (UCI) messages associated with a first control resource set (CORESET) pool index value overlaps in the time domain with a second PUCCH resource including one or more second UCI messages associated with a second CORESET pool index value; identifying, by the UE, one or more physical uplink shared channel (PUSCH) resources overlapping with at least one of the first PUCCH resource or the second PUCCH resource in the time domain; multiplexing, by the UE, one or more of the one or more first UCI messages and the one or more second UCI messages onto one or more PUSCH resources of the one or more PUSCH resources; and The one or more PUSCH resources are sent by the UE on an associated component carrier after performing the configuring for multiplexing.

17. The UE of claim 16, wherein the associated component carrier is one of: the same component carrier as a PUCCH component carrier on which the first PUCCH resource and the second PUCCH resource can be simultaneously transmitted or a different component carrier.

18. The UE according to claim 16, wherein the configuration of the at least one processor for identifying the one or more PUSCH resources includes the configuration of the at least one processor for the following operation: identifying a first PUSCH resource among the one or more PUSCH resources that overlaps with both the first PUCCH resource and the second PUCCH resource, wherein the configuration of the at least one processor for multiplexing includes the configuration of the at least one processor for the following operation: multiplexing the one or more first UCI messages and the one or more second UCI messages onto the first PUSCH resource.

19. The UE according to claim 16, wherein the configuration of the at least one processor for identifying the one or more PUSCH resources comprises the configuration of the at least one processor for: identifying a first PUSCH resource of the one or more PUSCH resources that overlaps with the first PUCCH resource, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; and identifying a second PUSCH resource overlapping with the second PUCCH resource among the one or more PUSCH resources, wherein the one or more second UCI messages are multiplexed onto the second PUSCH resource, The configuration of the at least one processor to transmit includes configuration of the at least one processor to transmit the first PUSCH resource and the second PUSCH resource.

20. The UE of claim 19, wherein the configuration of the at least one processor for identifying the first PUSCH resource and the second PUSCH resource is in response to the UE determining that a single PUSCH resource of the one or more PUSCH resources fails to overlap with both the first PUCCH resource and the second PUCCH resource. 21 . The UE according to claim 19 , wherein the first PUCCH resource is scheduled earlier than the second PUCCH resource in the time domain.

22. The UE of claim 19, wherein when the first PUCCH resource has the same start time as the second PUCCH resource, the UE identifies the first PUSCH overlapping with the first PUCCH resource having the one or more first UCI messages associated with the first CORESET pool index value, the first CORESET pool index value being one of a higher value or a lower value than the second CORESET pool index value associated with the one or more second UCI messages of the second PUCCH resource.

23. The UE of claim 19, wherein the first PUSCH resource and the second PUSCH resource are the same PUSCH resource.

24. The UE of claim 16, wherein the configuration of the at least one processor to identify the one or more PUSCH resources comprises configuration of the at least one processor to: identifying a first PUSCH resource overlapping with the first PUCCH resource among the one or more PUSCH resources, wherein the one or more first UCI messages are multiplexed onto the first PUSCH resource; determining whether any remaining PUSCH resources of the one or more PUSCH resources excluding the first PUSCH resource overlap with the second PUCCH resource, wherein in response to at least one PUSCH resource overlapping with the second PUCCH resource, the one or more second UCI messages are multiplexed onto a second PUSCH resource in the at least one PUSCH resource, and In response to the one or more PUSCH resources excluding the first PUSCH resource not overlapping with the second PUCCH resource, one of the following: When the first PUSCH resource also overlaps with the second PUCCH resource, the one or more second UCI messages are multiplexed onto the first PUSCH resource; or The UE declares an error state, wherein the UE avoids execution of the configuration of the at least one processor for multiplexing and transmitting the one or more PUSCH resources.

25. The UE of claim 24, wherein the first PUCCH resource is identified as being earlier than the second PUCCH resource in the time domain.

26. The UE according to claim 16, further comprising: The at least one processor is configured to: multiplexing, by the UE, the one or more first UCI messages and the one or more second UCI messages onto a multiplexed PUCCH resource; determining, by the UE, whether any of the one or more PUSCH resources overlaps with the multiplexed PUCCH resource, wherein in response to at least one PUSCH resource of the one or more PUSCH resources overlapping with the multiplexed PUCCH resource, the one or more first UCI messages and the one or more second UCI messages are multiplexed onto a first PUSCH resource of the at least one PUSCH resource, and In response to the one or more PUSCH resources not overlapping with the multiplexed PUCCH resources, the configuration of the at least one processor for the following operation is performed: sending the multiplexed PUCCH resources and the one or more PUSCH resources through the UE.

27. The UE of claim 26, wherein the configuration of the at least one processor to multiplex the one or more first UCI messages and the one or more second UCI messages onto the multiplexed PUCCH resources and the configuration of the at least one processor to determine whether the PUSCH resources overlap with the multiplexed PUCCH resources are performed in response to: an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with at least one PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the at least one PUSCH resource is different from a corresponding CORESET pool index value associated with the at least one PUCCH resource; and An identification of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool index value associated with the any PUSCH resource is equal to the corresponding CORESET pool index value associated with the at least one PUCCH resource.

28. The UE according to claim 16, further comprising: The at least one processor is configured to perform the following operations: receiving, by the UE, a radio resource control (RRC) message including a PUSCH multiplexing parameter, wherein the PUSCH multiplexing parameter identifies a predetermined procedure for identifying the one or more PUSCH resources that overlap with the at least one of the first PUCCH resource or the second PUCCH resource in the time domain.

29. The UE of claim 16, wherein the configuration of the at least one processor to multiplex the one or more of the one or more first UCI messages and the one or more second UCI messages onto the one or more PUSCH resources of the one or more PUSCH resources comprises one or more of the following: The identification of the one or more PUSCH resources disregards a CORESET pool value associated with the one or more PUSCH resources overlapping with one or both of the first PUCCH resources and the second PUCCH resources; an identification of at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that does not overlap with any PUSCH resource in the one or more PUSCH resources, wherein the CORESET pool value associated with the at least one PUSCH resource is equal to a corresponding CORESET pool value associated with the at least one PUCCH resource; or An identification of the at least one PUCCH resource in the first PUCCH resource or the second PUCCH resource that overlaps with the at least one PUSCH resource, wherein the CORESET pool value associated with the at least one PUSCH resource is different from the corresponding CORESET pool value associated with the at least one PUCCH resource.

30. The UE according to claim 16, further comprising: The at least one processor is configured to: avoid, by the UE, transmission of the first PUCCH resource and the second PUCCH resource in response to the execution of the at least one processor's configuration to transmit the one or more PUSCH resources.

Images