Uplink control multiplexing for multiple transmit-receive points

By jointly multiplexing and resource sharing of overlapping uplink control information without distinguishing TRP in the wireless communication system, the problem of low efficiency of uplink control information multiplexing in the prior art is solved, and resources are realized efficient utilization and system performance improvement.

CN119072990APending Publication Date: 2024-12-03QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095194.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-29
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Existing wireless communication systems have problems of inefficiency and waste of resources in the multiplexing of uplink control information, especially in the multiplexing process between multiple transmit and receive points (TRPs), resulting in processing resources and signaling resources. Consumption increases.

Method used

By combining overlapping uplink control information (UCI) into a single UCI without distinguishing TRP, and sending the single in uplink communication between user equipment (UE) and network entity, using the combination of overlapping uplink control information (UCI) without distinguishing TRP, and UCI realizes resource sharing and efficiency improvement of multiple TRPs. The specific method includes selecting appropriate physical uplink channel resources, performing drilling and joint multiplexing of PUSCH and PUCCH channels, and determining multiplexing and transmission of UCI according to TRP configuration rules.

Benefits of technology

It improves the efficiency of uplink communication, reduces the consumption of processing resources and signaling resources, enhances the UCI multiplexing capability of multiple TRPs, and improves the overall performance and reliability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072990A_ABST
    Figure CN119072990A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive a configuration that specifies overlapping uplink control information (UCI) on one or more physical uplink channels to be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs) or multiplexed by the TRPs. The UE can generate the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCI into the single UCI without differentiating TRP, or by multiplexing the overlapping UCI by TRP. The UE can transmit the single UCI in an uplink communication. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for multiplexing uplink control information for multiple transmission reception points. Background Art

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

[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a configuration that specifies that overlapping uplink control information (UCI) on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs). The method may include generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCI into the single UCI without distinguishing the TRPs. The method may include sending the single UCI in an uplink communication.

[0006] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a configuration that specifies that overlapping UCI on one or more physical uplink channels for multiple TRPs are to be multiplexed into a single UCI per TRP. The method may include generating the single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration. The method may include sending the single UCI in an uplink transmission for each TRP.

[0007] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a configuration specifying that overlapping UCIs on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs. The method may include receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs. The method may include sending or receiving communications based at least in part on the one or more single UCIs.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration that specifies overlapping UCI on one or more physical uplink channels to be jointly multiplexed into a single UCI for multiple TRPs. The one or more processors may be configured to generate the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCI into the single UCI without distinguishing the TRPs. The one or more processors may be configured to send the single UCI in an uplink communication.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration that specifies that overlapping UCI on one or more physical uplink channels for multiple TRPs will be multiplexed into a single UCI per TRP. The one or more processors may be configured to generate the single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration. The one or more processors may be configured to send the single UCI in an uplink transmission for each TRP.

[0010] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a configuration specifying that overlapping UCIs on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple TRPs. The one or more processors may be configured to receive one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs. The one or more processors may be configured to send or receive communications based at least in part on the one or more single UCIs.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may enable the UE to receive a configuration that specifies overlapping UCIs on one or more physical uplink channels to be jointly multiplexed into a single UCI for multiple TRPs. The instruction set, when executed by one or more processors of the UE, may enable the UE to generate the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCIs into the single UCI without distinguishing TRPs. The instruction set, when executed by one or more processors of the UE, may enable the UE to send the single UCI in an uplink communication.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, can cause the UE to receive a configuration that specifies that overlapping UCIs on one or more physical uplink channels for multiple TRPs will be multiplexed into a single UCI per TRP. The instruction set, when executed by one or more processors of the UE, can cause the UE to generate a single UCI for each TRP by multiplexing the overlapping UCIs for the TRP into the single UCI based at least in part on the configuration. The instruction set, when executed by one or more processors of the UE, can cause the UE to send the single UCI in an uplink transmission for each TRP.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, can cause the network entity to send a configuration that specifies overlapping UCIs on one or more physical uplink channels to be jointly multiplexed into a single UCI for multiple TRPs. The instruction set, when executed by one or more processors of the network entity, can cause the network entity to receive one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs. The instruction set, when executed by one or more processors of the network entity, can cause the network entity to send or receive communications based at least in part on the one or more single UCIs.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving a configuration that specifies that overlapping UCI on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple TRPs. The apparatus may include a component for generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCI into the single UCI without distinguishing the TRPs. The apparatus may include a component for sending the single UCI in an uplink communication.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving a configuration that specifies that overlapping UCI on one or more physical uplink channels for multiple TRPs will be multiplexed into a single UCI per TRP. The apparatus may include a component for generating a single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration. The apparatus may include a component for sending the single UCI in an uplink transmission for each TRP.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending a configuration that specifies that overlapping UCI on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple TRPs. The apparatus may include a component for receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs. The apparatus may include a component for sending or receiving communications based at least in part on the one or more single UCIs.

[0017] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0018] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0019] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0022] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0023] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0024] Figure 4 An example logical architecture of a distributed radio access network according to the present disclosure is illustrated.

[0025] Figure 5 is a diagram illustrating an example of multiple transmit-receive point (TRP) communications according to the present disclosure.

[0026] Figure 6 is a diagram illustrating an example of a time slot format according to the present disclosure.

[0027] Figure 7 is a diagram illustrating an example of using a beam for communication between a base station and a UE according to the present disclosure.

[0028] Figure 8 is a diagram illustrating an example of uplink control information (UCI) multiplexing according to the present disclosure.

[0029] Fig. 9 is a diagram illustrating an example of UCI multiplexing with multiple TRPs according to the present disclosure.

[0030] Fig.10 is a diagram illustrating an example associated with joint UCI multiplexing of multiple TRPs according to the present disclosure.

[0031] Fig.11 is a diagram illustrating an example of joint UCI multiplexing according to the present disclosure.

[0032] Fig.12 is a diagram illustrating an example associated with UCI multiplexing of multiple TRPs per TRP according to the present disclosure.

[0033] Fig.13 It is a diagram illustrating an example of UCI multiplexing of multiple TRPs per TRP according to the present disclosure.

[0034] Fig.14 is a diagram illustrating an example of UCI multiplexing with multiple TRPs according to the present disclosure.

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

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

[0037] Fig.17 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0038] Figure 18 to Figure 19 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

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

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

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

[0042] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0043] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0044] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

[0045] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0046] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. A base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0047] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0048] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for the network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

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

[0050] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0053] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

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

[0056] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a configuration that specifies that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple TRPs. The communication manager 140 may generate the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCI into the single UCI without distinguishing the TRPs. The communication manager 140 may send the single UCI in an uplink communication.

[0057] In some aspects, the communication manager 140 may receive a configuration that specifies that overlapping UCI on one or more physical uplink channels for multiple TRPs will be multiplexed into a single UCI per TRP. The communication manager 140 may generate the single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration. The communication manager may send the single UCI in an uplink transmission for each TRP. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a configuration specifying that overlapping UCIs on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs. The communication manager 150 may receive one or more single UCIs, each of which is multiplexed to include overlapping UCIs. The communication manager 150 may send or receive communications based at least in part on the one or more single UCIs. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

[0060] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0061] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a group of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0062] At the UE 120, a group of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a group of received signals (e.g., R received signals) to a group of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data destined for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0064] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, an antenna group, a group of antenna elements, and / or an antenna array may include one or more antenna elements (in a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components).

[0065] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 19 ) or any aspect of any of the methods described herein.

[0066] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 4 to 19 ) or any aspect of any of the methods described herein.

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

[0068] In some aspects, the UE 120 includes: a means for receiving a configuration that specifies that overlapping UCI on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs; a means for generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCI into the single UCI without distinguishing the TRPs; and / or a means for sending the single UCI in an uplink communication. The means for the UE to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0069] In some aspects, UE 120 includes: a component for receiving a configuration specifying that overlapping UCI on one or more physical uplink channels for multiple TRPs are to be multiplexed into a single UCI per TRP; a component for generating the single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration; and / or a component for sending the single UCI in an uplink transmission for each TRP.

[0070] In some aspects, a network entity (e.g., base station 110) includes: means for sending a configuration specifying that overlapping UCIs on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs; means for receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs; and / or means for sending or receiving communications based at least in part on the one or more single UCIs. In some aspects, means for a network entity to perform operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0071] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

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

[0073] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

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

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

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

[0077] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as an F1 interface). The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0078] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

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

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

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

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

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

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

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

[0086] Figure 4 An example logical architecture of a distributed RAN 400 according to the present disclosure is illustrated.

[0087] The 5G access node 405 may include an access node controller 410. The access node controller 410 may be a CU of the distributed RAN 400. In some aspects, a backhaul interface to the 5G core network 415 may terminate at the access node controller 410. The 5G core network 415 may include a 5G control plane component 420 and a 5G user plane component 425 (e.g., a 5G gateway), and a backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller 410. Additionally or alternatively, a backhaul interface to one or more neighbor access nodes 430 (e.g., another 5G access node 405 and / or an LTE access node) may terminate at the access node controller 410.

[0088] The access node controller 410 may include one or more TRPs 435 and / or may communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). The TRP 435 may be a DU of the distributed RAN 400. In some aspects, the TRP 435 may correspond to a network entity, such as a TRP described above in conjunction with Figure 1The base station 110 described herein may be a base station 110. For example, different TRPs 435 may be included in different base stations 110. Additionally or alternatively, multiple TRPs 435 may be included in a single base station 110. In some aspects, a base station 110 may include a CU (e.g., an access node controller 410) and / or one or more DUs (e.g., one or more TRPs 435). In some cases, a TRP 435 may be referred to as a cell, a panel, an antenna array, or an array.

[0089] The TRP 435 may be connected to a single access node controller 410 or to multiple access node controllers 410. In some aspects, there may be a dynamic configuration of split logical functions within the architecture of the distributed RAN 400. For example, the PDCP layer, the RLC layer, and / or the MAC layer may be configured to terminate at the access node controller 410 or the TRP 435.

[0090] In some aspects, multiple TRPs 435 may transmit communications (e.g., the same communication or different communications) in the same transmit time interval (TTI) (e.g., time slot, mini-time slot, subframe, or symbol) or in different TTIs using different quasi-co-located (QCL) relationships (e.g., different spatial parameters, different transmit configuration indicator (TCI) states, different pre-coding parameters, and / or different beamforming parameters). In some aspects, the TCI state may be used to indicate one or more QCL relationships. A TRP 435 may be configured to provide services to a UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 435).

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

[0092] Figure 5 5 is a diagram illustrating an example 500 of multi-TRP communication (sometimes referred to as multi-panel communication) according to the present disclosure. Figure 5 As shown, multiple TRPs 505 can communicate with the same UE 120. TRP 505 can correspond to the above combination Figure 4 TRP 435 as described.

[0093] Multiple TRPs 505 (shown as TRP A and TRP B) may communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and / or increase throughput. TRPs 505 may coordinate such communications via interfaces between TRPs 505 (e.g., backhaul interfaces and / or access node controllers 410). When TRPs 505 are co-located at the same base station 110 (e.g., when TRPs 505 are different antenna arrays or panels of the same base station 110), the interface may have less latency and / or higher capacity, and when TRPs 505 are located at different base stations 110, the interface may have greater latency and / or lower capacity (compared to co-location). Different TRPs 505 may communicate with UE 120 using different QCL relationships (e.g., different TCI states), different DMRS ports, and / or different layers (e.g., different layers in multi-layer communications).

[0094] In a first multi-TRP transmission mode (e.g., Mode 1), a single physical downlink control channel (PDCCH) may be used to schedule downlink data communications of a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 505 (e.g., TRP A and TRP B) may transmit communications to UE 120 on the same PDSCH. For example, communications may be transmitted using a single codeword with different spatial layers for different TRPs 505 (e.g., one of the codewords is mapped to a first set of layers transmitted by a first TRP 505 and is mapped to a second set of layers transmitted by a second TRP 505). As another example, communications may be transmitted using multiple codewords, with different codewords being transmitted by different TRPs 505 (e.g., using different sets of layers). In either case, different TRPs 505 may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 505 may use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first set of layers, and the second TRP 505 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) set of layers. In some aspects, the TCI state in the downlink control information (DCI) (e.g., sent on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using a TCI field in the DCI. Typically, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0095] In a second multi-TRP transmission mode (e.g., Mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH may schedule a first codeword to be transmitted by the first TRP 505, and a second PDCCH may schedule a second codeword to be transmitted by the second TRP 505. In addition, a first DCI (e.g., transmitted by the first TRP 505) may schedule a first PDSCH communication associated with a first DMRS port set having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 505, and a second DCI (e.g., transmitted by the second TRP 505) may schedule a second PDSCH communication associated with a second DMRS port set having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 505. In this case, the DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state for the TRP 505 corresponding to the DCI. The TCI field of the DCI indicates a corresponding TCI state (eg, the TCI field of the first DCI indicates a first TCI state and the TCI field of the second DCI indicates a second TCI state).

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

[0097] Figure 6 600 is a diagram illustrating an example of a time slot format according to the present disclosure. Figure 6 As shown, the time-frequency resources in the radio access network can be divided into resource blocks (shown by a single resource block (RB) 605). RB 605 is sometimes referred to as a physical resource block (PRB). RB 605 includes a set of subcarriers (e.g., 12 subcarriers) and a set of symbols (e.g., 14 symbols) that can be scheduled as a unit by a network entity (e.g., base station 110). In some aspects, RB 605 may include a set of subcarriers in a single time slot. As shown, a single time-frequency resource included in RB 605 may be referred to as a resource element (RE) 610. RE 610 may include a single subcarrier (e.g., in frequency) and a single symbol (e.g., in time). A symbol may be referred to as an OFDM symbol. RE 610 may be used to send a modulation symbol, which may be a real value or a complex value.

[0098] In some telecommunication systems (e.g., NR), RB 605 may span 12 subcarriers in 0.1 millisecond (ms) duration, with a subcarrier spacing of, for example, 15 kilohertz (kHz), 30kHz, 60kHz, or 120kHz, etc. A radio frame may include 40 time slots and may have a length of 10ms. Thus, each time slot may have a length of 0.25ms. However, the time slot length may vary depending on the parameter set used to communicate (e.g., subcarrier spacing and / or cyclic prefix format). A time slot may be configured with a link direction (e.g., downlink or uplink) for transmission. In some aspects, the link direction for a time slot may be dynamically configured.

[0099] Downlink channels may include a PDCCH carrying DCI, a PDSCH carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. Uplink channels may include a physical uplink control channel (PUCCH) carrying UCI, a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access, etc. In some aspects, UE 120 may send acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in UCI on PUCCH and / or PUSCH.

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

[0101] Figure 7 is a diagram illustrating an example 700 of using beams for communication between a network entity (eg, base station 110) and a UE according to the present disclosure. Figure 7 As shown, network entities (eg, base station 110) and UE 120 may communicate with each other.

[0102] Base station 110 may transmit to UE 120 located within the coverage area of ​​base station 110. Base station 110 and UE 120 may be configured for beamformed communications, where base station 110 may transmit in the direction of UE 120 using a directional BS transmit beam, and UE 120 may receive the transmission using a directional UE receive beam. Each BS transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. Base station 110 may transmit downlink communications via one or more BS transmit beams 705.

[0103] UE 120 may attempt to receive downlink transmissions via one or more UE receive beams 710, which may be configured using different beamforming parameters at receive circuitry of UE 120. UE 120 may identify specific BS transmit beams 705 (shown as BS transmit beam 705-A) and specific UE receive beams 710 (shown as UE receive beam 710-A) that provide relatively good performance (e.g., having the best channel quality of different measured combinations of BS transmit beams 705 and UE receive beams 710). In some examples, UE 120 may send an indication of which BS transmit beam 705 UE 120 identifies as a preferred BS transmit beam, which base station 110 may select to transmit to UE 120. Thus, UE 120 can obtain and maintain a beam pair link (BPL) for downlink communication with base station 110 (e.g., a combination of BS transmit beam 705-A and UE receive beam 710-A), which can be further refined and maintained based on one or more established beam refinement processes.

[0104] A downlink beam (such as a BS transmit beam 705 or a UE receive beam 710) may be associated with a TCI state. The TCI state may indicate a directionality or characteristic of the downlink beam, such as one or more QCL attributes of the downlink beam. The QCL attributes may include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc. In some examples, each BS transmit beam 705 may be associated with a synchronization signal block (SSB), and the UE 120 may indicate a preferred BS transmit beam 705 by transmitting an uplink transmission in the resources of the SSB associated with the preferred BS transmit beam 705. A specific SSB may have an associated TCI state (e.g., for an antenna port or for beamforming). In some examples, the base station 110 may indicate a downlink BS transmit beam 705 based at least in part on an antenna port QCL attribute that may be indicated by a TCI state. For different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc.), the TCI state may be associated with a set of downlink reference signals (e.g., SSB and aperiodic, periodic, or semi-persistent channel state information (CSI) reference signals (CSI-RS)). In the case where the QCL type indicates spatial reception parameters, the QCL type may correspond to simulated reception beamforming parameters of the UE reception beam 710 at the UE 120. Thus, the UE 120 may select a corresponding UE reception beam 710 from the BPL set based at least in part on the base station 110 indicating the BS transmit beam 705 via the TCI indication.

[0105] The base station 110 may maintain an activated TCI state set for downlink shared channel transmission and an activated TCI state set for downlink control channel transmission. The activated TCI state set for downlink shared channel transmission may correspond to a beam that the base station 110 uses for downlink transmission on PDSCH. The activated TCI state set for downlink control channel communication may correspond to a beam that the base station 110 may use for downlink transmission on PDCCH or in a control resource set (CORESET). The UE 120 may also maintain an activated TCI state set for receiving downlink shared channel transmission and CORESET transmission. If the TCI state is activated for the UE 120, the UE 120 may have one or more antenna configurations based at least in part on the TCI state, and the UE 120 may not need to reconfigure the antenna or antenna weighting configuration. In some examples, the set of activated TCI states (e.g., activated PDSCH TCI states and activated CORESET TCI states) for the UE 120 may be configured by a configuration message (such as an RRC message).

[0106] Similarly, for uplink communications, UE 120 may transmit in the direction of base station 110 using a directional UE transmit beam, and base station 110 may receive the transmission using a directional BS receive beam. Each UE transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. UE 120 may transmit uplink communications via one or more UE transmit beams 715.

[0107] Base station 110 may receive uplink transmissions via one or more BS receive beams 720. Base station 110 may identify specific UE transmit beams 715 (shown as UE transmit beam 715-A) and specific BS receive beams 720 (shown as BS receive beam 720-A) that provide relatively good performance (e.g., having the best channel quality of different measured combinations of UE transmit beams 715 and BS receive beams 720). In some examples, base station 110 may send an indication of which UE transmit beam 715 base station 110 identifies as a preferred UE transmit beam that base station 110 may select to transmit from UE 120. Thus, UE 120 and base station 110 may obtain and maintain a BPL for uplink communications (e.g., a combination of UE transmit beam 715-A and BS receive beam 720-A), which may be further refined and maintained according to one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam 715 or a BS receive beam 720, may be associated with a spatial relationship. The spatial relationship may indicate a directionality or characteristic (similar to one or more QCL properties) of the uplink beam, as described above.

[0108] 3GPP standard Release 17 establishes a unified TCI state framework, in which TCI states can be used to indicate more than one beam. TCI states can be used to indicate beams used for downlink channels or RSs (such as PDCCH / PDSCH / CSI-RS) and / or uplink channels or RSs (such as PUCCH / PUSCH / sounding reference signals (SRS)). Unified TCI states can be of multiple types. For example, a joint downlink / uplink common TCI state (joint TCI) can indicate a common beam for at least one downlink channel or RS and at least one uplink channel or RS. A separate downlink common TCI state (downlink TCI) can indicate a common beam for more than one downlink channel or RS. A separate uplink common TCI state (uplink TCI) can indicate a common beam for more than one uplink channel or RS. Other types of unified TCI states may include a separate downlink single channel or RS TCI state indicating a beam for a single downlink channel or RS, a separate uplink single channel or RS TCI state indicating a beam for a single uplink channel or RS, or uplink spatial relationship information, such as a spatial relationship indicator (SRI), indicating a beam for a single uplink channel or RS. In some aspects, uplink MIMO with multiple TRPs may involve TCI states for transmitting multiple layers using time division multiplexing, frequency division multiplexing, or space division multiplexing.

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

[0110] Figure 8 is a diagram illustrating an example 800 of UCI multiplexing according to the present disclosure.

[0111] Example 800 illustrates multiple UCIs, including a first CSI report (CSI1) in a first PUCCH communication, a second CSI report (CSI2) in a second PUCCH communication, and feedback (e.g., ACK / NACK bits for PDSCH communications of different hybrid automatic repeat request (HARQ) identifiers (IDs)) and a scheduling request (SR) in a third PUCCH communication. Multiple PUCCH communications for sending UCI overlap with each other and also overlap with PUSCH communications. Multiple communications for sending UCI may overlap if at least a portion of the UCI overlaps in time or shares time resources. For example, the duration of multiple communications (PUCCH and / or PUSCH) for sending UCI may overlap with at least one OFDM symbol. "Overlapping UCI" may be a term referring to communications that are used to send UCI and overlap.

[0112] The UE may multiplex UCI for communications involving a single TRP. The UE may determine a set of overlapping communications of PUCCH and / or PUSCH with UCI in different serving cells configured for the UE. In the first step of UCI multiplexing shown by reference numeral 802, when multiplexing of different CSI reports is allowed, overlapping UCI with CSI reports on different PUCCHs (if any) may be multiplexed to form a single UCI as a PUCCH communication with CSI1 and CSI2. Some UCI may be discarded during UCI multiplexing based on UCI multiplexing rules. For example, CSI2 may be discarded if necessary. In the first step, the UE may determine a single PUCCH communication for sending UCI for CSI reports based on a set of overlapping communications of PUCCH with CSI reports.

[0113] In the second step of UCI multiplexing, shown by reference numeral 804, the overlapping UCI for feedback, SR (if present), and CSI reports from the first step may be multiplexed to form a single UCI as a PUCCH communication. In example 800, the PUCCH communication includes ACK, SR, CSI1, and CSI2. If necessary, CSI1 and CSI2 may be dropped, and this is indicated by the brackets around CSI1 and CSI2. In the second step, the UE may determine a single PUCCH communication for sending UCI for feedback, SR, and CSI reports based on the set of overlapping communications of PUCCH with feedback, SR, and CSI reports.

[0114] In the third step of UCI multiplexing, shown by reference numeral 806, overlapping UCI for PUSCH communication and PUCCH communication from the second step, if present, is multiplexed to form a single PUSCH communication including UCI. When UCI is transmitted in PUSCH communication, UCI for SR may be dropped.

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

[0116] Fig. 9 is a diagram illustrating example 900 of UCI multiplexing with multiple TRPs according to the present disclosure.

[0117] Although Figure 8Example 800 shows multiplexing with a single TRP, but the UE may operate with multiple TRPs. Different TRPs may be associated with different IDs (such as a CORESET pool index, a TCI state ID, a TCI group ID, a closed loop index, a sounding reference signal (SRS) resource set ID, or a CSI resource set ID). Different UCIs may be associated with different TRPs based on predetermined rules. For example, some CSI reports may be associated with a first TRP and some CSI reports may be associated with a second TRP, and the association between the TRPs and the CSI reports may be predetermined or preconfigured.

[0118] Feedback (e.g., ACK / NACK or A / N) and SR may also be associated with different TRPs. For example, feedback bits corresponding to PDSCH communications scheduled in a CORESET with CORESET pool index 0 or a CORESET with no CORESET pool index may be associated with a first TRP, and feedback bits corresponding to PDSCH communications scheduled in a CORESET with CORESET pool index 1 may be associated with a second TRP. Different PUCCH or PUSCH communications may also be associated with different TRPs based on predetermined rules. It is not yet specified how the UE handles UCI multiplexing with multiple TRPs. In the absence of appropriate configuration for UCI multiplexing with multiple TRPs, the UE may consume additional processing resources and signaling resources due to the inefficiency of sending UCI for multiple TRPs.

[0119] According to various aspects described herein, a network entity may configure a UE to have a configuration that overlapping UCI on a specified physical uplink channel (e.g., PUSCH, PUCCH) will be multiplexed into a single UCI for multiple TRPs. The UE may multiplex the overlapping UCI into the single UCI according to the configuration. The UE may send a single UCI to the network entity, and the network entity may determine precoding information or other information for future communications based at least in part on the UCI in the single UCI.

[0120] In some aspects, the configuration may specify joint UCI multiplexing. Joint UCI multiplexing may enable the UE to multiplex UCI from different PUCCH communications and / or different PUSCH communications associated with different TRPs into a single UCI to be sent in an uplink communication, which may be a PUCCH communication or a PUSCH communication based at least in part on a UCI multiplexing rule. The UE may jointly multiplex overlapping UCI into a single UCI without distinguishing between TRPs. That is, the UE may multiplex UCI independently of or without regard to which TRP the UCI is associated with or which TRP the PUCCH / PUSCH communication is associated with. As Figure 8As shown, the UE may follow a single TRP rule to multiplex overlapping UCI from multiple TRPs as if overlapping UCI for different TRPs were all used for a single TRP. For example, when the UE is configured with multiple TRP operations based on multiple DCIs and is configured with parameters such as "joint UCI transmission", the UE may multiplex all UCI from different overlapping PUCCH communications and / or PUSCH communications (if not discarded) into a single PUCCH communication or a single PUSCH communication.

[0121] Example 900 illustrates communications associated with two TCI states (TCI1 and TCI2), each of which directs uplink communications to a TRP. TCI1 is used for the first TRP and is shown by a black box. TCI2 is used for the second TRP and is shown by a white box. Although PUCCH communications PUCCH1 and PUCCH2 are associated with TCI2 (the second TRP), the UCI on PUCCH1 and PUCCH2 may be multiplexed into a PUSCH communication (PUSCH1) associated with TCI1 (the first TRP). That is, joint UCI multiplexing is not limited to the same TRP. In some aspects, if two PUSCH communications have the same starting symbol and / or are associated with a designated CORESET (e.g., CORESET pool index 0), the UE may select one or more UCIs for UCI multiplexing. For example, when the UE multiplexes all UCI from different overlapping PUCCH communications into one PUSCH communication among multiple PUSCH communications with the same grant type (all dynamically granted PUSCHs or all configured granted PUSCHs) and with the same starting symbol in the serving cell, the UE may select one PUSCH communication among the multiple PUSCH communications to send all UCI. The selected PUSCH communication may be associated with a specific TRP. For example, the selected PUSCH communication may be associated with a lower CORESET pool index, a lower TCI ID, or a lower SRS resource set ID.

[0122] Alternatively, in some aspects, the configuration may specify separate UCI multiplexing, where overlapping UCIs are multiplexed into a single UCI per TRP. There may be a single UCI for each TRP, and thus there may be multiple single UCIs for multiple TRPs.

[0123] Example 900 shows separate UCI multiplexing. UCI on PUCCH2 is associated with TCI2 (second TRP) and is multiplexed into PUSCH2 (also associated with TCI2) but not into PUSCH1 (associated with TCI1). PUCCH1 is multiplexed into PUSCH1 because both are associated with TCI1. That is, it is applied within each TRP rather than across multiple TRPs. Figure 8The configuration may also include timing conditions for determining which UCIs overlap and / or for determining which overlapping UCIs may be multiplexed.

[0124] In some aspects, when the UE is configured with multiple TRP operation based on multiple and is configured with the parameter "separate UCI transmission", the UE multiplexes all UCI on different overlapping PUCCH communications and / or PUSCH communications associated with the TRP into a single PUCCH communication or a single PUSCH communication associated with the same TRP based on the UCI multiplexing rules and procedures. First, the UE can determine a set of overlapping PUCCH communications and / or PUSCH communications for each TRP. For example, if the set of overlapping PUCCH and / or PUSCH is associated with the same CORESET pool index or shares the same TCI ID, the UE can determine that the set of overlapping PUCCH communications and / or PUSCH communications is associated with the same TRP.

[0125] Second, for each TRP, the UE may apply UCI multiplication rules and procedures individually among the set of overlapping PUCCH communications and / or PUSCH communications determined for that TRP. Figure 8 The UCI multiplication rules and procedures for each TRP are performed as shown in . Finally, the UE can determine a single PUCCH communication or a single PUSCH communication for a TRP to send all UCI (if not discarded) on different overlapping PUCCH communications or PUSCH communications associated with the TRP.

[0126] When applying UCI multiplexing rules and procedures for each TRP, the UE may also apply separate timing requirements for different TRPs to determine whether UCI should be multiplexed or discarded. In some aspects, the UE may determine that the uplink communications multiplexed with UCI for different TRPs are of the same type. The UE may not expect the determined uplink communications multiplexed with UCI for different TRPs to be of different types. For example, the UE may not expect the determined uplink communications multiplexed with UCI for a TRP to be PUCCH communications, and the determined uplink communications multiplexed with UCI for another TRP to be PUSCH communications.

[0127] By using a configuration that specifies UCI multiplexing for multiple TRPs, network entities and UEs can have greater certainty in sending UCI and can save processing resources and signaling resources.

[0128] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 Different than described.

[0129] Fig.10 1 is a diagram illustrating an example 1000 associated with joint UCI multiplexing of multiple TRPs according to the present disclosure. Fig.10 As shown, a network entity 1010 (eg, base station 110) and a UE 1020 (eg, UE 120) may communicate with each other over a wireless network (eg, wireless network 100).

[0130] As indicated by reference numeral 1025, the network entity 1010 may send a configuration specifying joint UCI multiplexing. As indicated by reference numeral 1030, the UE 1020 may generate a single UCI by jointly multiplexing overlapping UCI into a single UCI without distinguishing between TRPs. The overlapping UCI may include feedback (e.g., ACK / NACK), SR, or CSI reports associated with multiple TRPs.

[0131] The UE 1020 may select resources for physical uplink channel communications on one or more physical uplink channels as resources for a single UCI. The UE 1020 may select resources for physical uplink channel communications of one TRP among multiple TRPs as resources for a single UCI. The physical uplink channel communications may be in the same serving cell and have the same starting symbol. In some aspects, the UE 1020 may generate a single UCI by selecting resources for a physical uplink channel among one or more physical uplink channels as resources associated with a specified CORESET pool index.

[0132] In some aspects, the UE 1020 may puncture resources used for PUSCH communication for a single UCI. Puncturing may include not allocating some resources for data in the PUSCH communication and using those resources for a single UCI. This may be applicable if the UCI bit is 1 or 2 bits, such as 1 or 2 bits used for feedback.

[0133] In some aspects, the UE 1020 may jointly multiplex overlapping UCIs by jointly multiplexing one or more UCIs on the PUCCH and one or more UCIs on the PUSCH into a single UCI. The UE 1020 may also jointly multiplex overlapping UCIs by jointly multiplexing one or more UCIs in one or more PUCCH communications and one or more UCIs in one or more second PUCCH communications into a single UCI. In some aspects, the UE 1020 may multiplex aperiodic CSI or semi-persistent (SP) CSI reports on the PUSCH into the PUSCH communications. This may involve CSI triggering DCI or activating DCI.

[0134] As shown by reference numeral 1035, the UE 1020 may send a single UCI in a single uplink communication. The network entity 1010 may demultiplex the single UCI based on the configuration and use the UCI in the single UCI. As shown by reference numeral 1040, the network entity 1010 may determine precoding information, beam information, and / or other communication information based at least in part on the UCI in the single UCI. As shown by reference numeral 1045, the network entity 1010 may use the precoding information, beam information, and / or other information to send or receive communications. By jointly multiplexing the UCI without distinguishing between TRPs, the UE 1020 may more efficiently send UCI for multiple TRPs and may save processing resources and signaling resources.

[0135] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 Different than described.

[0136] Fig.11 is a diagram illustrating an example 1100 of joint UCI multiplexing according to the present disclosure.

[0137] Example 1100 illustrates steps for UCI multiplexing without distinguishing TRPs. Different TCI states, including different layers of TCI states, are indicated for different TRPs with shaded boxes. As shown in reference numeral 1102, UE 1020 may handle overlapping CSI reports and multiplex CSI1 and CSI2 on different PUCCH communications into a single PUCCH communication (CSI1+[CSI2]). As shown in reference numeral 1104, UE 1020 may handle overlapping feedback (e.g., ACK), SR, and / or CSI reports, and multiplex PUCCH (CSI1+[CSI2]) and PUCCH (ACK+SR) into a single PUCCH communication (ACK+SR+[CSI1]+[CSI2]). As shown in reference numeral 1106, UE 1020 may handle overlapping PUCCH communications and PUSCH communications, and may multiplex multiplexed UCI on PUCCH communications into PUSCH communications. When there are two PUSCH communications (PUSCH1 and PUSCH2) both with the same starting symbol in the serving cell, the UE may select one PUSCH communication based at least in part on a predetermined rule. For example, PUSCH1 may be associated with a lower CORESET pool index, and the UE may determine to use PUSCH1 to multiplex all UCIs.

[0138] As indicated above, Fig.11 are provided as examples. Other examples can be found in the Fig.11 Different than described.

[0139] Fig.12 is a diagram illustrating example 1200 associated with UCI multiplexing of multiple TRPs per TRP according to the present disclosure.

[0140] As shown by reference numeral 1225, the network entity 1010 may send a configuration specifying UCI multiplexing per TRP. This includes multiplexing overlapping UCI into a single UCI belonging to the same TRP. A single UCI may exist for each of the multiple TRPs. As shown by reference numeral 1230, the UE 1020 may generate a single UCI for each TRP by multiplexing overlapping UCI for the TRP into the single UCI based at least in part on the configuration.

[0141] The UE 1020 may select resources for physical uplink channel communications on one or more physical uplink channels associated with a TRP as resources for a single UCI for the TRP. In some aspects, the UE 1020 may puncture resources for PUSCH communications for a single UCI for each TRP.

[0142] In some aspects, the UE 1020 may jointly multiplex periodic or SP CSI reports in PUCCH communications associated with different TRPs into a physical uplink channel communication associated with a designated CORESET pool index (e.g., CORESET pool index 0).

[0143] In some aspects, the UE 1020 may multiplex CSI reports in one or more physical uplink channel communications by TRP. The UE 1020 may multiplex feedback and / or SR in one or more physical uplink channel communications by TRP. The UE 1020 may multiplex one or more UCIs on the PUCCH and one or more UCIs on the PUSCH into a single UCI by TRP. The UE 1020 may determine, at least in part based on a rule, that one or more UCIs on the PUCCH and one or more UCIs on the PUSCH share the same TRP. The rule may be based at least in part on a shared TCI state. That is, the same TCI state may indicate the same TRP. Other rules may be used.

[0144] In some aspects, the UE 1020 may multiplex one or more UCIs in the one or more first PUCCH communications and one or more UCIs in the one or more second PUCCH communications into a single UCI per TRP. The UE 1020 may determine, based at least in part on a rule, that the one or more UCIs in the one or more first PUCCH communications and the one or more UCIs in the one or more second PUCCH communications share the same TRP.

[0145] As shown in reference numeral 1235, UE 1020 may send a single UCI, where each single UCI is used for a TRP. UE 1020 may send each single UCI in a single uplink communication. Network entity 1010 may demultiplex the single UCI based on the configuration and use the UCI in the single UCI. As shown in reference numeral 1240, network entity 1010 may determine precoding information, beam information, and / or other communication information based at least in part on the UCI in the single UCI. As shown in reference numeral 1245, network entity 1010 may use precoding information, beam information, and / or other information to send or receive communications. By multiplexing UCIs by TRP, UE 1020 may provide TRP-specific UCIs to network entity 1010. UE 1020 may send UCIs for multiple TRPs more efficiently, and may save processing resources and signaling resources.

[0146] As indicated above, Fig.12 are provided as examples. Other examples can be found in the Fig.12 Different than described.

[0147] Fig.13 is a diagram illustrating example 1300 of UCI multiplexing for multiple TRPs per TRP according to the present disclosure.

[0148] Example 1300 illustrates the steps of UCI multiplexing by TRP. Black boxes and white boxes indicate different TCI states to different TRPs. For example, PUCCH (CSI2) and PUSCH2 are associated with TCI state 1 for the first TRP (black boxes for TCI1), while other UCIs are associated with TCI state 2 for the second TRP (white boxes for TCI2). UE 1020 will multiplex overlapping UCIs for a single TRP. In example 1300, UE 1020 will multiplex overlapping UCIs associated with uplink communications applied with TCI2.

[0149] As shown in reference numeral 1302, UE 1020 may handle overlapping CSI reports. Since only PUCCH (CSI1) is associated with TCI2, UE 1020 does not multiplex PUCCH (CSI1) and PUCCH (CSI2). As shown in reference numeral 1304, UE 1020 may handle overlapping feedback (e.g., ACK), SR and / or CSI reports, and multiplex PUCCH (CSI1) and PUCCH (ACK+SR) into PUCCH (ACK+SR+[CSI1]). As shown in reference numeral 1306, UE 1020 may handle overlapping PUCCH communications and PUSCH communications, and may multiplex PUCCH communications into PUSCH1 (ACK+SR+[CSI1]). Because PUSCH2 is associated with TCI1, PUSCH2 is ignored. PUSCH1 for TCI2 (second TRP) may be included in a single UCI in a single uplink communication.

[0150] UE 1020 may continue to multiplex overlapping UCI for another TRP. For example, UE 1020 may multiplex PUCCH(CSI2) into PUSCH2 to form PUSCH2(CSI2). PUSCH2 may be included in another single UCI in another single uplink communication. In some aspects, CSI reports from multiple TRPs may be multiplexed at step 1302 without distinguishing between TRPs, but steps 1304 and 1306 may be retained per TRP.

[0151] As indicated above, Fig.13 are provided as examples. Other examples can be found in the Fig.13 Different than described.

[0152] Fig.14 is a diagram illustrating example 900 of UCI multiplexing with multiple TRPs according to the present disclosure.

[0153] Example 1400 illustrates multiplexing of periodic or SP CSI reporting on PUCCH. In some aspects, the UE 1020 may handle periodic or SP CSI reporting on PUCCH. The UE 1020 may multiplex periodic or SP CSI reporting on PUCCH into overlapping PUSCH communications.

[0154] In some aspects, as a first option (Option 1), if any CORESET is applicable, the PUSCH communication may be associated with a specified CORESET pool index (e.g., CORESET pool index 0). The black box DCI may be associated with CORESET pool index 0. Example 1400 shows PUCCH1 and PUCCH2 multiplexed into PUSCH1. Otherwise, the UE 1020 may multiplex periodic or SP CSI reports into another PUSCH communication.

[0155] Alternatively, in some aspects, as a second option (Option 2), the UE 1020 may multiplex periodic or SP CSI reports on the PUCCH into overlapping PUSCH communications associated with the same TRP. Example 1400 illustrates multiplexing PUCCH2(CSI) and PUCCH2(A / N) into PUSCH2, all of which are associated with TCI2 or the second TRP. Example 1400 also illustrates multiplexing PUCCH1 into PUSCH1, all of which are associated with TCI1 or the first TRP. Either option may be configured by the network entity 1010 for joint UCI multiplexing or for UCI multiplexing per TRP.

[0156] As indicated above, Fig.14 are provided as examples. Other examples can be found in the Fig.14 Different than described.

[0157] Fig.15 1 is a diagram illustrating an example process 1500 performed, for example, by a UE according to the present disclosure. Example process 1500 is an example in which a UE (eg, UE 120, UE 1020) performs operations associated with UCI multiplexing for multiple TRPs without distinguishing between TRPs.

[0158] like Fig.15 As shown, in some aspects, process 1500 may include receiving a configuration specifying that overlapping UCIs on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs (block 1510). Fig.18 The communication manager 1808 and / or receiving component 1802 depicted in the figure can receive a configuration specifying that overlapping UCIs on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs, as described above.

[0159] like Fig.15 As further shown, in some aspects, process 1500 may include generating a single UCI based at least in part on the configuration by jointly multiplexing overlapping UCIs into the single UCI without distinguishing between TRPs (block 1520). Fig.18The communication manager 1808 and / or generation component 1810 depicted in the figure can generate a single UCI based at least in part on the configuration by jointly multiplexing overlapping UCIs into a single UCI without distinguishing TRPs, as described above.

[0160] like Fig.15 As further shown, in some aspects, process 1500 may include sending a single UCI in an uplink communication (block 1530). For example, a UE (e.g., using Fig.15 The communication manager 1808 and / or the transmitting component 1804 depicted in FIG. 1 may transmit a single UCI in an uplink communication, as described above.

[0161] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0162] In a first aspect, generating a single UCI includes selecting resources used for physical uplink channel communications on one or more physical uplink channels as resources for the single UCI.

[0163] In a second aspect, alone or in combination with the first aspect, process 1500 includes puncturing resources used for PUSCH communication for a single UCI.

[0164] In a third aspect, alone or in combination with one or more of the first and second aspects, the overlapping UCI includes one or more of feedback, scheduling requests, or CSI reports associated with multiple TRPs.

[0165] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1500 includes selecting resources for physical uplink channel communications of a TRP among a plurality of TRPs as resources for a single UCI.

[0166] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, physical uplink channels communicate in the same serving cell and have the same starting symbol.

[0167] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, generating the single UCI includes: selecting resources for a physical uplink channel of the one or more physical uplink channels as resources associated with a designated CORESET pool index.

[0168] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, jointly multiplexing overlapping UCIs includes: jointly multiplexing one or more UCIs on a PUCCH and one or more UCIs on a PUSCH into a single UCI.

[0169] In the eighth aspect, alone or in combination with one or more aspects from the first to seventh aspects, the jointly multiplexed overlapping UCI includes: jointly multiplexing one or more UCIs in one or more first PUCCH communications and one or more UCIs in one or more second PUCCH communications into a single UCI.

[0170] although Fig.15 Example blocks of process 1500 are shown, but in some aspects, process 1500 may include Fig.15 The blocks depicted in the process 1500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1500. Additionally or alternatively, two or more blocks in the blocks of the process 1500 may be performed in parallel.

[0171] Fig.16 1 is a diagram illustrating an example process 1600 performed, for example, by a UE according to the present disclosure. Example process 1600 is an example in which a UE (eg, UE 120, UE 1020) performs operations associated with multiplexing UCI per TRP for multiple TRPs.

[0172] like Fig.16 As shown, in some aspects, process 1600 may include receiving a configuration specifying that overlapping UCIs on one or more physical uplink channels for multiple TRPs are to be multiplexed into a single UCI per TRP (block 1610). Fig.18 The communication manager 1808 and / or receiving component 1802 depicted in the figure can receive a configuration specifying that overlapping UCIs on one or more physical uplink channels for multiple TRPs are to be multiplexed into a single UCI per TRP, as described above.

[0173] like Fig.16 As further shown, in some aspects, process 1600 may include generating, for each TRP, a single UCI by multiplexing overlapping UCIs for the TRP into a single UCI based at least in part on the configuration (block 1620). Fig.10 The communication manager 1808 and / or generation component 1810 depicted in FIG. 1 may generate a single UCI for each TRP by multiplexing overlapping UCIs for the TRP into a single UCI based at least in part on the configuration, as described above.

[0174] like Fig.16As further shown, in some aspects, process 1600 may include sending a single UCI in an uplink transmission for each TRP (block 1630). Fig.18 The communication manager 1808 and / or the transmitting component 1804 depicted in FIG. 1 may send a single UCI in the uplink transmission for each TRP, as described above.

[0175] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0176] In a first aspect, generating a single UCI for a TRP includes selecting resources for physical uplink channel communications on one or more physical uplink channels associated with the TRP as resources for the single UCI for the TRP.

[0177] In a second aspect, alone or in combination with the first aspect, process 1600 includes puncturing resources used for PUSCH communications for a single UCI for each TRP.

[0178] In a third aspect, either alone or in combination with one or more of the first and second aspects, the multiplexing comprises jointly multiplexing periodic CSI reports or SP CSI reports in PUCCH communications associated with different TRPs into a physical uplink channel communication associated with a specified CORESET pool index.

[0179] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the multiplexing comprises: multiplexing CSI reports in one or more physical uplink channel communications according to TRP.

[0180] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the multiplexing comprises: multiplexing feedback or SR in one or more physical uplink channel communications according to TRP.

[0181] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the multiplexing includes: multiplexing one or more UCIs on the PUCCH and one or more UCIs on the PUSCH into a single UCI according to the TRP.

[0182] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1600 includes determining, based at least in part on a rule, that one or more UCIs on the PUCCH and one or more UCIs on the PUSCH share the same TRP.

[0183] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the rule is based at least in part on a shared TCI state.

[0184] In the ninth aspect, alone or in combination with one or more aspects from the first to the eighth aspects, the multiplexing includes: multiplexing one or more UCIs in one or more first PUCCH communications and one or more UCIs in one or more second PUCCH communications into a single UCI according to TRP.

[0185] In a tenth aspect, either alone or in combination with one or more of aspects 1 to 9, process 1600 includes determining, based at least in part on a rule, that one or more UCIs in one or more first PUCCH communications and one or more UCIs in one or more second PUCCH communications share the same TRP.

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

[0187] Fig.17 17 is a diagram illustrating an example process 1700 performed, for example, by a network entity according to the present disclosure. Example process 1700 is an example in which a network entity (e.g., base station 110, network entity 1010) performs operations associated with configuring a UE for UCI multiplexing of multiple TRPs.

[0188] like Fig.17 As shown, in some aspects, process 1700 may include sending a configuration specifying that overlapping UCI on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs (block 1710). Fig.19 The communication manager 1908 and / or the sending component 1904 depicted in the figure may send a configuration specifying that overlapping UCIs on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple TRPs, as described above.

[0189] like Fig.17 As further shown, in some aspects, process 1700 may include receiving one or more individual UCIs, each of which is multiplexed to include overlapping UCIs (block 1720). For example, a network entity (e.g., using Fig.19The communication manager 1908 and / or receiving component 1902 depicted in FIG. 10 can receive one or more individual UCIs, each of which is multiplexed to include overlapping UCIs, as described above.

[0190] like Fig.17 As further shown, in some aspects, process 1700 may include sending or receiving communications based at least in part on one or more single UCIs (block 1730). Fig.19 The communication manager 1908 and / or the sending component 1904 depicted in FIG. 1 may send or receive communications based at least in part on one or more single UCIs, as described above.

[0191] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0192] In a first aspect, the configuration specifies joint multiplexing of overlapping UCIs without distinguishing TRPs, and joint multiplexing of a single UCI without distinguishing TRPs.

[0193] In a second aspect, alone or in combination with the first aspect, the configuration specifies that overlapping UCIs are multiplexed per TRP, and each single UCI of the one or more single UCIs is multiplexed for one TRP of the plurality of TRPs.

[0194] In a third aspect, alone or in combination with one or more of the first and second aspects, resources used for PUSCH communication are punctured for one or more single UCIs.

[0195] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the overlapping UCI comprises one or more of feedback, scheduling request or CSI report.

[0196] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more single UCIs are in a resource associated with a specified CORESET pool index.

[0197] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a single UCI among the one or more single UCIs includes one or more UCIs jointly multiplexed from one or more UCIs on a PUCCH and one or more UCIs on a PUSCH.

[0198] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, a single UCI in one or more single UCIs includes one or more UCIs jointly multiplexed from one or more UCIs in one or more first PUCCH communications and one or more UCIs in one or more second PUCCH communications.

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

[0200] Fig.18 1 is a diagram of an example apparatus 1800 for wireless communication. Apparatus 1800 may be a UE (e.g., UE 120, UE 1020), or a UE may include apparatus 1800. In some aspects, apparatus 1800 includes a receiving component 1802 and a transmitting component 1804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1800 may communicate with another apparatus 1806 (such as a UE, a base station, or another wireless communication device) using receiving component 1802 and transmitting component 1804. As further shown, apparatus 1800 may include a communication manager 1808. Communication manager 1808 may control and / or otherwise manage one or more operations of receiving component 1802 and / or transmitting component 1804. In some aspects, communication manager 1808 may include a communication manager 1808 in conjunction with receiving component 1802 and transmitting component 1804. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 1808 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1808 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1808 can include a receiving component 1802 and / or a sending component 1804. The communication manager 1808 can include one or more of a generating component 1810 and / or a selecting component 1812, among others.

[0201] In some aspects, the apparatus 1800 may be configured to perform Figures 1 to 14 Additionally or alternatively, the apparatus 1800 may be configured to perform one or more of the processes described herein, such as Fig.15 The process of 1500 Fig.16 In some aspects, Fig.18 The apparatus 1800 and / or one or more components shown in the drawings may include a combination of Figure 2 Additionally or alternatively, Fig.18 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0202] The receiving component 1802 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1806. The receiving component 1802 may provide the received communications to one or more other components of the apparatus 1800. In some aspects, the receiving component 1802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1800. In some aspects, the receiving component 1802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0203] Transmit component 1804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1806. In some aspects, one or more other components of device 1800 may generate communications and may provide the generated communications to transmit component 1804 for transmission to device 1806. In some aspects, transmit component 1804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1806. In some aspects, transmit component 1804 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1804 can be co-located with the receive component 1802 in a transceiver.

[0204] In some aspects, receiving component 1802 can receive a configuration that specifies overlapping UCI on one or more physical uplink channels to be jointly multiplexed into a single UCI for multiple TRPs. Generating component 1810 can generate a single UCI based at least in part on the configuration by jointly multiplexing overlapping UCI into a single UCI without distinguishing TRPs. Sending component 1804 can send the single UCI in an uplink communication.

[0205] The generation component 1810 can puncture resources used for PUSCH communication for a single UCI. The selection component 1812 can select resources used for physical uplink channel communication of one TRP among multiple TRPs as resources for a single UCI.

[0206] In some aspects, receiving component 1802 may receive a configuration specifying that overlapping UCI on one or more physical uplink channels for multiple TRPs are to be multiplexed into a single UCI per TRP. Generating component 1810 may generate a single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration. Transmitting component 1804 may transmit the single UCI in an uplink transmission for each TRP.

[0207] The generation component 1810 may puncture resources for PUSCH communications for a single UCI for each TRP. The generation component 1810 may determine, based at least in part on a rule, that one or more UCIs on the PUCCH and one or more UCIs on the PUSCH share the same TRP. The generation component 1810 may determine, based at least in part on a rule, that one or more UCIs in one or more first PUCCH communications and one or more UCIs in one or more second PUCCH communications share the same TRP.

[0208] Fig.18 The number and arrangement of components shown in the diagram are provided as examples. In practice, there may be Fig.18 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.18 Two or more components shown in may be implemented in a single component, or Fig.18 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.18 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.18 One or more functions performed by another set of components shown in FIG.

[0209] Fig.191 is a diagram of an example apparatus 1900 for wireless communication. Apparatus 1900 may be a network entity (e.g., base station 110, network entity 1010), or a network entity may include apparatus 1900. In some aspects, apparatus 1900 includes a receiving component 1902 and a transmitting component 1904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1900 may communicate with another apparatus 1906 (such as a UE, a base station, or another wireless communication device) using receiving component 1902 and transmitting component 1904. As further shown, apparatus 1900 may include a communication manager 1908. Communication manager 1908 may control and / or otherwise manage one or more operations of receiving component 1902 and / or transmitting component 1904. In some aspects, communication manager 1908 may include a communication manager 1908 in conjunction with receiving component 1902 and / or transmitting component 1904. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communication manager 1908 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communications manager 1908 may be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 1908 may include a receiving component 1902 and / or a sending component 1904. The communications manager 1908 may include a configuring component 1910, among other things.

[0210] In some aspects, the apparatus 1900 may be configured to perform Figures 1 to 14 Additionally or alternatively, the apparatus 1900 may be configured to perform one or more of the processes described herein, such as Fig.17 The process 1700. In some aspects, Fig.19 The apparatus 1900 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.19 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0211] The receiving component 1902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1906. The receiving component 1902 may provide the received communications to one or more other components of the device 1900. In some aspects, the receiving component 1902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1900. In some aspects, the receiving component 1902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0212] Transmit component 1904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1906. In some aspects, one or more other components of device 1900 may generate communications and may provide the generated communications to transmit component 1904 for transmission to device 1906. In some aspects, transmit component 1904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1906. In some aspects, transmit component 1904 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1904 can be co-located with the receive component 1902 in a transceiver.

[0213] The transmitting component 1904 may transmit a configuration specifying that overlapping UCIs on one or more physical uplink channels are to be jointly multiplexed into a single UCI for multiple TRPs. The configuring component 1910 may generate the configuration based at least in part on UE capabilities, channel conditions, and / or traffic conditions. The receiving component 1902 may receive one or more single UCIs, each of which is multiplexed to include overlapping UCIs. The transmitting component 1904 may transmit or receive communications based at least in part on the one or more single UCIs.

[0214] Fig.19 The number and arrangement of components shown in the diagram are provided as examples. In practice, there may be Fig.19 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.19 Two or more components shown in may be implemented in a single component, or Fig.19The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.19 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.19 One or more functions performed by another set of components shown in FIG.

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

[0216] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs); generating the single UCI at least partially based on the configuration by jointly multiplexing the overlapping UCI into the single UCI without distinguishing the TRPs; and sending the single UCI in uplink communication.

[0217] Aspect 2: The method according to aspect 1, wherein generating the single UCI comprises: selecting resources used for physical uplink channel communication on the one or more physical uplink channels as resources for the single UCI.

[0218] Aspect 3: The method according to aspect 1 or 2, further comprising: puncturing resources used for physical uplink shared channel (PUSCH) communication for the single UCI.

[0219] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the overlapping UCI includes one or more of feedback, scheduling requests, or channel state information (CSI) reports associated with the multiple TRPs.

[0220] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: selecting resources for physical uplink channel communication of one TRP among the multiple TRPs as resources for the single UCI.

[0221] Aspect 6: The method according to aspect 5, wherein the physical uplink channel communications are in the same serving cell and have the same starting symbol.

[0222] Aspect 7: The method according to any one of aspects 1 to 6, wherein generating the single UCI includes: selecting resources for a physical uplink channel among the one or more physical uplink channels as resources associated with a designated control resource set pool index.

[0223] Aspect 8: A method according to any one of Aspects 1 to 7, wherein jointly multiplexing the overlapping UCI includes: jointly multiplexing one or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH) into the single UCI.

[0224] Aspect 9: A method according to any one of Aspects 1 to 8, wherein jointly multiplexing the overlapping UCI includes: jointly multiplexing one or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications into the single UCI.

[0225] Aspect 10: A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels for multiple transmit receive points (TRPs) will be multiplexed into a single UCI per TRP; generating the single UCI for each TRP by multiplexing the overlapping UCI for the TRP into the single UCI based at least in part on the configuration; and sending the single UCI in an uplink transmission for each TRP.

[0226] Aspect 11: The method according to Aspect 10, wherein generating the single UCI for the TRP includes: selecting resources for physical uplink channel communication on the one or more physical uplink channels associated with the TRP as resources for the single UCI for the TRP.

[0227] Aspect 12: The method according to Aspect 10 or 11 further includes: puncturing resources used for physical uplink shared channel (PUSCH) communication for the single UCI for each TRP.

[0228] Aspect 13: A method according to any one of Aspects 10 to 12, wherein the multiplexing includes: jointly multiplexing periodic CSI reports or semi-persistent CSI reports in physical uplink control channel (PUCCH) communications associated with different TRPs into a physical uplink channel communication associated with a specified control resource set pool index.

[0229] Aspect 14: A method according to any one of Aspects 10 to 13, wherein the multiplexing includes: multiplexing channel state information (CSI) reports in one or more physical uplink channel communications according to TRP.

[0230] Aspect 15: A method according to any one of Aspects 10 to 14, wherein the multiplexing comprises: multiplexing feedback or scheduling requests in one or more physical uplink channel communications according to TRP.

[0231] Aspect 16: A method according to any one of Aspects 10 to 15, wherein the multiplexing includes: multiplexing one or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH) into the single UCI according to TRP.

[0232] Aspect 17: The method according to aspect 16 also includes: determining, at least in part based on a rule, that the one or more UCIs on the PUCCH and the one or more UCIs on the PUSCH share the same TRP.

[0233] Aspect 18: The method according to aspect 17, wherein the rule is based at least in part on a shared transmission configuration indicator (TCI) state.

[0234] Aspect 19: A method according to any one of Aspects 10 to 18, wherein the multiplexing includes: multiplexing one or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications into the single UCI according to TRP.

[0235] Aspect 20: The method according to Aspect 19 also includes: determining, at least in part based on a rule, that the one or more UCIs in the one or more first PUCCH communications and the one or more UCIs in the one or more second PUCCH communications share the same TRP.

[0236] Aspect 21: A method of wireless communication performed by a network entity, comprising: sending a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels will be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs); receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs; and sending or receiving communications based at least in part on the one or more single UCIs.

[0237] Aspect 22: The method according to Aspect 21, wherein the configuration specifies that the overlapping UCIs are jointly multiplexed without distinguishing TRPs, and wherein the single UCI is jointly multiplexed without distinguishing TRPs.

[0238] Aspect 23: The method according to aspect 21, wherein the configuration specifies multiplexing of the overlapping UCIs per TRP, and wherein each single UCI of the one or more single UCIs is multiplexed for one TRP of the plurality of TRPs.

[0239] Aspect 24: The method according to any one of aspects 21 to 23, wherein resources used for physical uplink shared channel (PUSCH) communication are punctured for the one or more single UCIs.

[0240] Aspect 25: The method according to any one of aspects 21 to 24, wherein the overlapping UCI includes one or more of feedback, scheduling request or channel state information (CSI) report.

[0241] Aspect 26: The method according to any one of aspects 21 to 25, wherein the one or more single UCIs are in resources associated with a specified control resource set pool index.

[0242] Aspect 27: A method according to any one of Aspects 21 to 26, wherein a single UCI among the one or more single UCIs includes one or more UCIs jointly multiplexed from one or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH).

[0243] Aspect 28: A method according to any one of Aspects 21 to 27, wherein a single UCI among the one or more single UCIs includes one or more UCIs jointly multiplexed from one or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications.

[0244] Aspect 29: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 28.

[0245] Aspect 30: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 28.

[0246] Aspect 31: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 28.

[0247] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 28.

[0248] Aspect 33: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 28.

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

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

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

[0252] Although the specific combination of features is described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

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

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs); generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCIs into the single UCI without distinguishing TRPs; as well as The single UCI is transmitted in uplink communication.

2. The method of claim 1 , wherein generating the single UCI comprises: Resources used for physical uplink channel communications on the one or more physical uplink channels are selected as resources for the single UCI.

3. The method according to claim 1, further comprising: Resources used for physical uplink shared channel (PUSCH) communication are punctured for the single UCI.

4. The method of claim 1, wherein the overlapping UCI comprises one or more of feedback, scheduling requests, or channel state information (CSI) reports associated with the multiple TRPs.

5. The method according to claim 1, further comprising: Resources for physical uplink channel communication of one TRP among the multiple TRPs are selected as resources for the single UCI. The method according to claim 5 , wherein the physical uplink channel communications are in the same serving cell and have the same starting symbol.

7. The method of claim 1 , wherein generating the single UCI comprises: Resources for a physical uplink channel of the one or more physical uplink channels are selected as resources associated with a designated control resource set pool index.

8. The method of claim 1, wherein jointly multiplexing the overlapping UCIs comprises: One or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH) are jointly multiplexed into the single UCI.

9. The method of claim 1 , wherein jointly multiplexing the overlapping UCIs comprises: One or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications are jointly multiplexed into the single UCI.

10. A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels for multiple transmit reception points (TRPs) is to be multiplexed into a single UCI per TRP; Based at least in part on the configuration, generating, for each TRP, the single UCI by multiplexing the overlapping UCIs for the TRP into the single UCI; as well as The single UCI is sent in the uplink transmission for each TRP.

11. The method of claim 10, wherein generating the single UCI for a TRP comprises: Resources for physical uplink channel communications on the one or more physical uplink channels associated with the TRP are selected as resources for the single UCI for the TRP.

12. The method according to claim 10, further comprising: Resources used for physical uplink shared channel (PUSCH) communications are punctured for the single UCI for each TRP.

13. The method of claim 10, wherein the multiplexing comprises: Periodic CSI reports or semi-persistent CSI reports in physical uplink control channel (PUCCH) communications associated with different TRPs are jointly multiplexed into a physical uplink channel communication associated with a specified control resource set pool index.

14. The method of claim 10, wherein the multiplexing comprises: Channel state information (CSI) reports are multiplexed in one or more physical uplink channel communications per TRP.

15. The method of claim 10, wherein the multiplexing comprises: Feedback or scheduling requests are multiplexed in one or more physical uplink channel communications according to TRP.

16. The method of claim 10, wherein the multiplexing comprises: One or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH) are multiplexed into the single UCI according to the TRP.

17. The method according to claim 16, further comprising: The one or more UCIs on the PUCCH and the one or more UCIs on the PUSCH share the same TRP based at least in part on a rule.

18. The method of claim 17, wherein the rule is based at least in part on a shared transmission configuration indicator (TCI) state.

19. The method of claim 10, wherein the multiplexing comprises: One or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications are multiplexed into the single UCI according to the TRP.

20. The method according to claim 19, further comprising: The one or more UCIs in the one or more first PUCCH communications and the one or more UCIs in the one or more second PUCCH communications share a same TRP, determined at least in part based on a rule.

21. A method of wireless communication performed by a network entity, comprising: transmitting a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit reception points (TRPs); receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs; and Communications are sent or received based at least in part on the one or more single UCIs.

22. The method of claim 21, wherein the configuration specifies that the overlapping UCIs are jointly multiplexed without distinguishing TRPs, and wherein the single UCI is jointly multiplexed without distinguishing TRPs.

23. The method of claim 21, wherein the configuration specifies multiplexing of the overlapping UCIs per TRP, and wherein each of the one or more single UCIs is multiplexed for one TRP of the plurality of TRPs.

24. The method of claim 21, wherein resources used for physical uplink shared channel (PUSCH) communications are punctured for the one or more single UCIs.

25. The method of claim 21, wherein the overlapping UCI comprises one or more of feedback, scheduling requests, or channel state information (CSI) reports.

26. The method of claim 21, wherein the one or more single UCIs are in resources associated with a specified control resource set pool index.

27. The method of claim 21, wherein a single UCI of the one or more single UCIs comprises one or more UCIs jointly multiplexed from one or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH).

28. The method of claim 21, wherein a single UCI of the one or more single UCIs comprises one or more UCIs jointly multiplexed from one or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications.

29. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs); generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCIs into the single UCI without distinguishing TRPs; and The single UCI is transmitted in uplink communication.

30. The UE of claim 29, wherein to generate the single UCI, the one or more processors are configured to select resources used for physical uplink channel communications on the one or more physical uplink channels as resources for the single UCI.

31. The UE of claim 29, wherein the one or more processors are configured to puncture resources used for physical uplink shared channel (PUSCH) communications for the single UCI.

32. A UE according to claim 29, wherein the overlapping UCI includes one or more of feedback, scheduling requests, or channel state information (CSI) reports associated with the multiple TRPs.

33. The UE according to claim 29, wherein the one or more processors are configured to: select resources for physical uplink channel communication of one TRP among the multiple TRPs as resources for the single UCI.

34. The UE of claim 33, wherein the physical uplink channel communications are in the same serving cell and have the same starting symbol.

35. The UE of claim 29, wherein to generate the single UCI, the one or more processors are configured to: select resources for a physical uplink channel of the one or more physical uplink channels as resources associated with a designated control resource set pool index.

36. A UE according to claim 29, wherein in order to jointly multiplex the overlapping UCI, the one or more processors are configured to: jointly multiplex one or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH) into the single UCI.

37. A UE according to claim 29, wherein in order to jointly multiplex the overlapping UCI, the one or more processors are configured to: jointly multiplex one or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications into the single UCI.

38. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels for multiple transmit reception points (TRPs) is to be multiplexed into a single UCI per TRP; Based at least in part on the configuration, generating, for each TRP, the single UCI by multiplexing the overlapping UCIs for the TRP into the single UCI; and The single UCI is sent in the uplink transmission for each TRP.

39. A UE according to claim 38, wherein in order to generate the single UCI for the TRP, the one or more processors are configured to: select resources for physical uplink channel communication on the one or more physical uplink channels associated with the TRP as resources for the single UCI for the TRP.

40. The UE of claim 38, wherein the one or more processors are configured to: puncture resources used for physical uplink shared channel (PUSCH) communications for the single UCI for each TRP.

41. The UE of claim 38, wherein the multiplexing comprises: Periodic CSI reports or semi-persistent CSI reports in physical uplink control channel (PUCCH) communications associated with different TRPs are jointly multiplexed into a physical uplink channel communication associated with a specified control resource set pool index.

42. The UE of claim 38, wherein the multiplexing comprises: Channel state information (CSI) reports are multiplexed in one or more physical uplink channel communications per TRP.

43. The UE of claim 38, wherein the multiplexing comprises: Feedback or scheduling requests are multiplexed in one or more physical uplink channel communications according to TRP.

44. The UE of claim 38, wherein the multiplexing comprises: One or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH) are multiplexed into the single UCI according to the TRP.

45. The UE of claim 44, wherein the one or more processors are configured to determine, based at least in part on a rule, that the one or more UCIs on the PUCCH and the one or more UCIs on the PUSCH share the same TRP.

46. ​​The UE of claim 45, wherein the rule is based at least in part on a shared transmission configuration indicator (TCI) state.

47. The UE of claim 38, wherein the multiplexing comprises: One or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications are multiplexed into the single UCI according to the TRP.

48. A UE according to claim 47, wherein the one or more processors are configured to: determine, at least in part based on a rule, that the one or more UCIs in the one or more first PUCCH communications and the one or more UCIs in the one or more second PUCCH communications share the same TRP.

49. A network entity for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: transmitting a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit reception points (TRPs); receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs; and Communications are sent or received based at least in part on the one or more single UCIs.

50. The network entity of claim 49, wherein the configuration specifies that the overlapping UCIs are jointly multiplexed without distinguishing TRPs, and wherein the single UCI is jointly multiplexed without distinguishing TRPs.

51. The network entity of claim 49, wherein the configuration specifies multiplexing of the overlapping UCIs per TRP, and wherein each of the one or more single UCIs is multiplexed for one TRP of the plurality of TRPs.

52. The network entity of claim 49, wherein resources used for physical uplink shared channel (PUSCH) communications are punctured for the one or more single UCIs.

53. The network entity of claim 49, wherein the overlapping UCI comprises one or more of feedback, scheduling requests, or channel state information (CSI) reports.

54. The network entity of claim 49, wherein the one or more single UCIs are in resources associated with a specified control resource set pool index.

55. The network entity of claim 49, wherein a single UCI of the one or more single UCIs comprises one or more UCIs jointly multiplexed from one or more UCIs on a physical uplink control channel (PUCCH) and one or more UCIs on a physical uplink shared channel (PUSCH).

56. The network entity of claim 49, wherein a single UCI of the one or more single UCIs comprises one or more UCIs jointly multiplexed from one or more UCIs in one or more first physical uplink control channel (PUCCH) communications and one or more UCIs in one or more second PUCCH communications.

57. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs); generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCIs into the single UCI without distinguishing TRPs; and The single UCI is transmitted in uplink communication.

58. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels for multiple transmit reception points (TRPs) is to be multiplexed into a single UCI per TRP; Based at least in part on the configuration, generating, for each TRP, the single UCI by multiplexing the overlapping UCIs for the TRP into the single UCI; and The single UCI is sent in the uplink transmission for each TRP.

59. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a network entity, cause the network entity to: transmitting a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit reception points (TRPs); receiving one or more single UCIs, each single UCI being multiplexed to include overlapping UCIs; and Communications are sent or received based at least in part on the one or more single UCIs.

60. An apparatus for wireless communication, comprising: means for receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit receive points (TRPs); means for generating the single UCI based at least in part on the configuration by jointly multiplexing the overlapping UCIs into the single UCI without distinguishing TRPs; as well as Means for transmitting the single UCI in an uplink communication.

61. An apparatus for wireless communication, comprising: means for receiving a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels for multiple transmit reception points (TRPs) is to be multiplexed into a single UCI per TRP; means for generating, for each TRP, the single UCI by multiplexing the overlapping UCIs for the TRP into the single UCI based at least in part on the configuration; as well as A component for sending the single UCI in the uplink transmission for each TRP.

62. An apparatus for wireless communication, comprising: means for transmitting a configuration specifying that overlapping uplink control information (UCI) on one or more physical uplink channels is to be jointly multiplexed into a single UCI for multiple transmit reception points (TRPs); means for receiving one or more individual UCIs, each individual UCI being multiplexed to include overlapping UCIs; as well as Means for sending or receiving communications based at least in part on the one or more single UCIs.