Enhanced uplink control information mapping to uplink channel assignments - Patents.com

Abstract

The method includes determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations that overlap in the time domain and correspond to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); and mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations, to each of the at least two PUSCH allocations individually, or across the at least two PUSCH allocations, wherein the mapping is based on at least one of one or more configurations or predefined rules, or an indication received by the user equipment from a network node, and wherein each of the at least two PUSCH allocations includes resources assigned to the user equipment for the PUSCH transmission.

Description

[Technical field]

[0001] This specification relates to wireless communications. [Background technology]

[0002] A communication system is a facility that enables communication between two or more nodes or devices, such as fixed and / or mobile communication devices. Signals are transmitted over wired or wireless carriers.

[0003] An example of a cellular communication system is the architecture being standardized by the 3rd Generation Partnership Project (3GPP®). Recent developments in this field are often referred to as the Universal Mobile Telecommunications System (UMTS) Long Term Evolution of Radio Access Technology (LTE). Evolved UMTS Terrestrial Radio Access (E-UTRA) is the air interface of the 3GPP® Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), called enhanced nodes APs (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices or mobile stations are called user equipment (UE). LTE includes numerous improvements or developments. Aspects of LTE continue to improve.

[0004] The development of 5G New Radio (NR) is part of the ongoing mobile broadband evolution process, similar to the evolution of previous 3G and 4G wireless networks. Furthermore, 5G targets new use cases in addition to mobile broadband. The goal of 5G is to provide significant improvements in radio performance, including new levels of data rate, latency, reliability and security. 5G NR can also be extended to efficiently connect the vast Internet of Things (IoT) and provide new types of mission-critical services. For example, Ultra-Reliable, Low-Latency Communications (URLLC) devices may require high reliability and ultra-low latency. Summary of the Invention

[0005] According to an example embodiment, the method includes determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations that overlap in the time domain and correspond to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); and mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations, separately to each of the at least two PUSCH allocations, or across the at least two PUSCH allocations, where the mapping is based on at least one of one or more configurations or predefined rules, or an indication received by the user equipment from a network node, and where each of the at least two PUSCH allocations includes resources assigned to the user equipment for the PUSCH transmission.

[0006] According to another example embodiment, the method includes: transmitting, by a network node, to a user equipment, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); and receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations, wherein the at least one UCI is mapped to one of the at least two PUSCH allocations, separately to each of the at least two PUSCH allocations, or across the at least two PUSCH allocations, based on at least one of one or more configurations or predefined rules, or at least one indication provided from the network node to the user equipment, and wherein the PUSCH allocation includes resources assigned to the user equipment for the PUSCH transmission.

[0007] Additional exemplary embodiments are provided corresponding to each of the methods, comprising for each of the methods an apparatus including means for performing at least the respective method, the apparatus including at least one processor, at least one memory including computer program code, the at least one memory and the computer program code configured, by the at least one processor, to cause at least the apparatus to perform the method, and a non-transitory computer readable storage medium having stored thereon instructions configured, when executed by the at least one processor, to cause a computing system to perform the method.

[0008] According to an example embodiment, an apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured, by the at least one processor, to cause the apparatus to at least determine, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one Uplink Control Information (UCI), and map, by the user equipment, the UCI to at least one of:

[0009] According to an example embodiment, an apparatus includes a non-transitory computer-readable storage medium having stored thereon instructions configured, when executed by at least one processor, to cause a computing system to determine, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); and mapping, by the user equipment, the UCI to at least one of:

[0010] According to an example embodiment, an apparatus includes means for determining, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); and means for mapping, by the user equipment, the UCI to one of the at least two PUSCH allocations, to each of the at least two PUSCH allocations individually, or across the at least two PUSCH allocations, wherein the mapping is based on at least one of one or more configurations or predefined rules, or at least one indication received by the user equipment from a network node, and wherein the PUSCH allocation includes resources assigned to the user equipment for the PUSCH transmissions.

[0011] According to an example embodiment, an apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to cause the apparatus to at least: transmit, by the at least one processor, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI) to the user equipment; and receive, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations, wherein the at least one UCI is mapped to one of the at least two PUSCH allocations, separately to each of the at least two PUSCH allocations, or across the at least two PUSCH allocations, based on at least one of one or more configurations or predefined rules, or at least one instruction provided from the network node to the user equipment, and the PUSCH allocation includes resources assigned to the user equipment for the PUSCH transmission.

[0012] According to an example embodiment, an apparatus includes a non-transitory computer-readable storage medium having stored thereon instructions configured, when executed by at least one processor, to cause a computing system to: transmit, by a network node, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI) to the user equipment; and receive, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations, wherein the at least one UCI is mapped to one of the at least two PUSCH allocations, individually to each of the at least two PUSCH allocations, or across the at least two PUSCH allocations, wherein the mapping includes mapping the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction provided from the network node to the user equipment, wherein the PUSCH assignment includes resources assigned to the user equipment for the PUSCH transmission.

[0013] An apparatus in an example embodiment includes: means for transmitting, by a network node, downlink control information to a user equipment, the downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); and means for receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations, where the at least one UCI is mapped to one of the at least two PUSCH allocations, separately to each of the at least two PUSCH allocations, or across the at least two PUSCH allocations, where the at least one UCI is mapped based on at least one of one or more configuration or predefined rules, or at least one indication provided from the network node to the user equipment, and the PUSCH allocation includes resources assigned to the user equipment for the PUSCH transmission.

[0014] The details of one or more exemplary embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram of a wireless network in accordance with an example embodiment. [Diagram 2] FIG. 2 is a diagram illustrating multi-TRP communication according to an example embodiment. [Diagram 3] FIG. 3 is a flow chart illustrating the operation of a user equipment or UE in accordance with an example embodiment. [Figure 4] FIG. 4 is a flowchart illustrating the operation of a network node (e.g., a transmission / reception point (TRP), a gNB, or other network node) in accordance with an example embodiment. [Diagram 5]FIG. 5 illustrates a mapping of UCI (eg, CSI) to two PUSCH allocations corresponding to two simultaneous PUSCH transmissions based on an illustrated beta offset. [Figure 6] FIG. 6 is a diagram illustrating mapping of UCI to PUSCH according to another example embodiment based on scheduling of concurrent PUSCH operation. [Figure 7] FIG. 7 is a block diagram of a wireless station (e.g., an AP, BS, gNB, TRP, network node, user equipment, UE, or other wireless node) in an example embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] FIG. 1 is a block diagram of a wireless network 130 in an exemplary embodiment. In the wireless network 130 of FIG. 1, user equipments 131, 132, 133, and 135, which may also be referred to as mobile stations (MS) or user equipments (UE), may be connected (communicate) with a base station (BS) 134, which may also be referred to as an access point (AP), enhanced node B (eNB), or next-generation node B (gNB). The terms user equipment and user equipment (UE) may be used interchangeably. The BS may also be referred to as a RAN (radio access network) or NG-RAN (next-generation radio access network) node. At least some of the functions of the BS (e.g., AP, gNB, eNB, RAN node) may also be performed by one or more network nodes, servers, or hosts, such as a centralized unit (CU) and a distributed unit (DU) in a split-RAN architecture, which may be operatively coupled to a remote transceiver, such as a remote radio head (RRH). BS 134 provides radio coverage in cell 136 which includes user equipment 131, 132, 133 and 135. Although BS 134 is shown as having only four user equipment connected or attached thereto, any number of user equipment may be provided. BS 134 is also connected to core network 150 via an S1 interface 151. This is merely one example of a radio network and others may be used.

[0017] According to an exemplary embodiment, BSs (e.g., APs, eNBs, gNBs, RAN nodes) may be part of a mobile communication system. The RAN may include, for example, one or more RAN nodes (e.g., APs, BSs, eNBs, gNBs) implementing radio access technologies to enable one or more UEs to access a network or core network. Thus, the RAN nodes reside between one or more user equipments or UEs and the core network. According to an exemplary embodiment, each RAN node may provide one or more wireless communication services to one or more UEs or user equipments, for example, to enable the UEs to wirelessly access the network via the RAN node. Each RAN node may perform or provide wireless communication services, such as, for example, enabling the UEs or user equipments to establish a wireless connection to the RAN node, transmitting data to one or more UEs, and / or receiving data from one or more UEs. For example, after establishing a connection to the UE, the RAN node may forward data received from the network or core network to the UE and / or forward data received from the UE to the network or core network. A RAN node may perform a wide variety of other radio functions or services, such as, for example, broadcasting control information (e.g., system information, etc.) to UEs, paging UEs when there is data to be delivered to the UE, assisting in handover of UEs between cells, scheduling resources for uplink data transmissions from and downlink data transmissions to the UE(s), sending control information to configure one or more UEs, etc. These are just some examples of one or more functions that a RAN node may perform.

[0018] User equipment (user terminal, user equipment (UE), mobile terminal, portable wireless device, etc.) may refer to portable computing devices including wireless mobile communication devices operating with or without a subscriber identity module (SIM), including, by way of example and without limitation, mobile stations (MS), mobile phones, mobile phones, smartphones, personal digital assistants (PDAs), handsets, devices using wireless modems (such as alarm devices or measurement devices), laptops and / or touch screen computers, tablets, phablets, gaming devices, notebooks, vehicles, sensors, wearable devices, or other wireless devices. By way of example, laptops and / or touch screen computers, tablets, phablets, gaming devices, notebooks, vehicles, sensors, wearable devices, or other wireless devices. It should be understood that user equipment may also be (or include) almost exclusively uplink only devices, an example of which would be a camera or camcorder that loads images or video clips into the network.

[0019] The core network 150 may include a Mobility Management Entity (MME) or Access Mobility Management Function (AMF) that controls access to the network and handles or assists mobility / handover of user equipment between BSs, one or more gateways that forward data between the BSs and a packet data network or the Internet, and other control nodes, functions or blocks.

[0020] Further, as an illustrative example, the various exemplary embodiments or techniques in this embodiment may be applied to various types of user equipment or data service types, or may be applied to user equipment running multiple applications thereon, which may be different data service types. New Wireless (5G) developments may support a wide variety of applications or a wide variety of data service types, such as, for example, machine type communications (MTC), enhanced machine type communications (eMTC), Internet of Things (IoT), and / or narrowband IoT user equipment, enhanced mobile broadband (eMBB), and ultra-reliable low latency communications (URLLC). Many of these new 5G (NR) related applications may require generally higher performance than traditional wireless networks.

[0021] IoT may refer to an ever-growing group of objects with Internet or network connectivity that can send information to and receive information from other network devices. For example, many sensor-type applications and devices may monitor physical conditions or status and send reports to servers or other network devices, such as when an event occurs. Machine-based communication (MTC) is characterized by fully automatic data generation, exchange, processing, and actuation between intelligent machines, with or without human intervention, for example. Enhanced Mobile Broadband (eMBB) has the potential to support much higher data rates than current LTE.

[0022] Ultra-reliable, low-latency communications (URLLC) is a new data service type or new usage scenario that may be supported by new wireless (5G) systems. It will enable new applications and services, such as industrial automation, autonomous driving, vehicle safety, and e-health services. 3GPP targets to provide reliable connections with a block error rate (BLER) of 10-5 and U-plane (user / data plane) latency of up to 1 ms. Thus, for example, URLLC user equipment / UE may require a significantly lower block error rate and lower latency (whether or not high reliability is required at the same time) than other types of user equipment / UE. Thus, for example, a URLLC UE (or a URLLC application on a UE) may require a much lower latency compared to an eMBB UE (or an eMBB application running on a UE).

[0023] Various exemplary embodiments may be applied to a wide variety of wireless technologies or networks, such as LTE, LTE-A, 5G / New Radio (NR), or other wireless networks or technologies operating in the cmWave and / or mmWave bands, and a wide variety of communication services, such as IoT, MTC, eMTC, eMBB, URLLC, etc. The types of networks, technologies, or data services in this example are provided by way of example only.

[0024] The UE may be configured by the gNB (or other network node) to perform different measurements and measurement reporting to the network (or gNB(s)). Configuring the UE to perform reference signal (or beam) measurements (e.g., CSI-RS measurements for different beams) and reporting may be performed by the gNB sending a reporting configuration (e.g., CSI-Report-Config, etc.) to the UE. The reporting configuration may indicate, for example, on which downlink resources (e.g., CSI-RS reference signals / SSBs or beams) measurements should be performed, specific quantities or parameters to be measured, and how reporting is to be performed, such as when reporting is to be performed.

[0025] The UE may measure a signal parameter (e.g., Reference Signal Received Power (RSRP), etc.) of each of multiple downlink reference signals (e.g., synchronization signal block / SSB signals, or Channel State Information (CSI) Reference Signals (CSI-RS), etc.) received by the UE from a gNB / network node (or BS), where each reference signal may be transmitted by the gNB via a different gNB transmission beam (or via a different downlink DL reference signal). The UE may determine the strongest (e.g., having the highest RSRP) beam or reference signal and then transmit a measurement report to the gNB, e.g., identifying the strongest N DL reference signals (or beams) and the RSRPs (or other measured signal parameters) of these N beams. The gNB may use this measurement report to determine, e.g., which beam to use for communicating with the UE.

[0026] According to an exemplary embodiment, a PDCCH (Physical Downlink Control Channel) may be transmitted using 1, 2, 4, 8, or 16 consecutive control channel elements (CCEs), where the number of CCEs may be referred to as an aggregation level (or CCE aggregation level). According to an exemplary embodiment, a CCE is a component of a PDCCH, and a CCE may be the smallest resource set available for a PDCCH. For example, a CCE may be a unit in which a search space for blind decoding is defined. Thus, each PDCCH may include one or more CCEs depending on the aggregation level. According to an exemplary embodiment, a CCE may include six resource element groups (REGs), each of which may include one resource block in an OFDM symbol.

[0027] A search space may include a set of PDCCHs (candidate downlink control channels) formed by CCEs of a given aggregation level that the UE is to attempt to decode. A UE may have multiple search spaces for different purposes (such as different common search spaces and user-specific search spaces). A search space may include one or more control resource sets (CORESET). A CORESET may be (or may include) the time-frequency resources on which the PDCCH(s) are transmitted. There may be multiple search spaces that use the same control resource set (CORESET), and multiple CORESETs may be configured for a UE. Also, a control resource set (CORESET) may be (or include) the time-frequency resources on which the UE attempts to decode candidate PDCCHs using one or more search spaces.

[0028] Furthermore, a transmission configuration indication (TCI) state may be used by a network node (gNB or BS) in a control resource set (or CORESET) to provide a beam indication to the UE, which may identify a beam that the UE should use for uplink and / or downlink communications with the network node or gNB. Each TCI state may be configured or associated with a transmit beam / receive beam pair. Thus, each TCI state may be associated with a particular beam or a particular reference signal. For example, TCI state 1 may be associated with (or used to indicate) CSI-RS#5, TCI state 2 with CSI-RS#9, etc. (where CSI-RS#5, CSI-RS#9 may be DL reference signals transmitted by the gNB). Thus, each TCI state may be associated with (or indicated by) a particular reference signal and / or a particular beam. For example, for data transmission via a physical downlink shared channel (PDSCH) and / or data transmission via a physical uplink shared channel (PUSCH), the UE is configured with 128 candidate TCI states by the gNB via a radio resource control (RRC) message. The gNB can then configure the UE with, for example, up to 8 (or other number) activated TCI states via a media access control (MAC) control element (MAC CE) that can be piggybacked (or added) to a downlink (DL) data transmission to the UE via a physical downlink shared channel (PDSCH). Thus, the gNB in ​​this embodiment can transmit an activation message to activate (in the UE) 8 (for example) indicated TCI states out of the 128 (for example) candidate TCI states. The UE can be requested by the network node to use a beam associated with any of these 8 (or other number) activated TCI states for communication (e.g., transmitting or receiving data) with the network node or the gNB.

[0029] Dynamically (e.g., as provided within the downlink control information / DCI of each subframe or slot), the gNB may indicate a selection of one of the activated TCI states (and thus identify a selected beam) for the UE to use for uplink or downlink data communications (e.g., via the PDSCH and / or PUSCH for scheduled uplink (UL) or downlink (DL) communications). The DCI (which may, at least in some aspects, identify the selected activated TCI state for the UE to use for communications) may be provided, for example, within a PDCCH (Physical Downlink Control Channel) transmitted to the UE as part of each slot or subframe. Thus, in some aspects, the DCI may be used to provide a fast beam indication indicating a selected TCI state (e.g., of a plurality of activated TCI states) associated with a reference signal or beam that the UE will use for UL or DL ​​data communications with the network node (BS or gNB). The UE may also receive control information (e.g., via a Radio Resource Control (RRC) message) indicating the selected TCI state (and thus the beam) that the UE will use to receive the PDCCH of each CORESET. Therefore, each CORESET may be configured with TCI states.

[0030] Release 16 of NR provides support for single-cell downlink multiple transmission / reception points (multi-TRP) (or multi-transmission / reception points), providing the possibility to transmit downlink data simultaneously via a physical downlink shared channel (PDSCH) from two different transmission / reception points (TRPs) located within the same cell, even if they are geographically separated (e.g., transmission of downlink data from two different radio heads or other nodes within a cell to a UE).

[0031] Furthermore, Rel-17 introduces a unified TCI framework, where the TCI state that provides QCL assumptions for reception of DL signals and channels will also be used to provide spatial sources for transmission of UL signals and channels. Furthermore, the unified TCI framework defines the concept of a directed TCI state. The directed TCI state can be a joint DL and UL TCI state or separate DL and separate UL TCI states. A directed TCI state provides QCL sources (DL) and spatial sources (UL) for a set of downlink signals and channels and a set of uplink signals and channels, respectively. In Rel-17, there can be one directed joint DL and UL or one directed DL and directed UL TCI state for a UE.

[0032] For example, the unified TCI framework may, at a high level, include the following capabilities: a common TCI state (e.g., indicated TCI) for a set of signals and channels at once; the TCI state can be a joint DL / UL TCI state, a separate DL TCI state and / or a separate UL TCI state; the RRC can configure a set (or pool) of joint and / or separate TCI states; the MAC (medium access control entity) can determine the number (e.g., DCI (downlink control information, e.g., provided from the gNB to the UE via the Physical Downlink Control Channel (PDCCH)) of activated TCI states as the indicated TCI state (which may be a common TCI state); for DCI based TCI state indication; for DCI based TCI state indication; the ability to use DCI format 1_1 / 1_2 with DL allocation and DCI format 1_1 / 1_2 without DL allocation to carry the TCI state indication; HARQ by the UE; Indication function confirmed by ACK (HARQ acknowledgment feedback to acknowledge data received by UE), application time of beam indication which is the first slot at least X ms or Y symbols after the last symbol of the acknowledgment of joint or separate DL / UL beam indication, codepoint of TCI field, joint, separate, pair of DL TCI state and UL TCI state, DL TCI state (maintain current UL TCI state), UL TCI state (maintain current DL TCI state), The unified TCI framework is extended in Rel-18 to include the function of being able to indicate multiple DL and UL TCI states.

[0033] Additionally, the UE may transmit uplink (UL) control information (UCI) to the gNB via a physical uplink control channel (PUCCH). The UCI may include, for example, one or more of: 1) Hybrid ARQ Acknowledgement (HARQ-ACK) feedback for received downlink data (to acknowledge receipt of DL (downlink) data), 2) Channel State Information (CSI) related to downlink channel conditions (e.g., used by the gNB to assist in downlink scheduling, including multiple antennas and beamforming schemes), and / or 3) a scheduling request (e.g., requesting a PUSCH allocation) indicating that the UE needs or is requesting uplink resources for an uplink transmission to the gNB.

[0034] Additionally, the UE may transmit data to a gNB or network node via a Physical Uplink Shared Channel (PUSCH). To transmit uplink data to the gNB, the UE may need a valid scheduling grant or PUSCH assignment (which provides the UE with an allocation of time-frequency resources that the UE can use for UL transmissions).

[0035] The PUCCH may be the basis for transmission of uplink control information (UCI) to the gNB. For example, in some cases, the UE may transmit UCI to the gNB via the PUCCH regardless of whether the UE has received a PUSCH assignment for transmission of UL data. However, in some cases, when the PUCCH and PUSCH overlap in time (such as in situations where the UE has received a valid grant or PUSCH assignment), the UE may transmit UCI on or within the PUSCH (e.g., by piggybacking UCI onto the PUSCH), which may include the UE multiplexing UCI onto the UL data and PUSCH to enable both data and UCI to be transmitted via the PUSCH. In this manner, multiplexing UCI with data on the PUSCH (or piggybacking UCI with data on the PUSCH) allows for more efficient transmission of data and UCI.

[0036] In some cases, explicit configuration / scheduling of CSI on PUSCH is only possible for semi-persistent CSI reporting and aperiodic CSI reporting. When PUSCH overlaps with PUCCH carrying UCI in the time domain, UE is expected to multiplex UCI content onto PUSCH according to a set of rules. This is called UCI piggybacking on PUSCH. UCI piggybacking onto PUSCH is supported for both CP-OFDM and DFT-S-OFDM waveforms. Piggybacked UCI is mapped after the first DMRS (Demodulation Reference Signal) of PUSCH (Frequency Division Multiplexing with DMRS is not allowed). Piggybacking of UCI is the only way to carry HARQ-ACK feedback on PUSCH. Piggybacking / multiplexing of UCI on PUSCH follows the multiplexing timeline conditions defined in TS38.213. For piggybacking / scheduling of UCI on PUSCH, almost all UCI content is rate-matched within PUSCH according to specific rules depending on the UCI type. The only exception is the HARQ-ACK feedback of up to 2 bits, which is transmitted by puncturing on the PUSCH.

[0037] Furthermore, the beta offset and / or alpha value may be configured / indicated by the gNB or network node (e.g., configured values ​​for the beta offset and / or alpha value may be transmitted to the UE). The beta offset may inform the UE how much resources from the PUSCH should (or may) be allocated to the UCI. There may be different beta offsets for different ranges of UCI payload sizes. The size of the UCI may determine the amount of PUSCH that the UCI can occupy or consume. The beta offset of the PUSCH may be used to decouple the BLER (Block Error Rate) of the UCI from the data. This may be achieved by weighting the number of resources consumed by HARQ-ACK, CSI Part 1, or CSI Part 2 (either or both may be considered as UCI). Beta offsets can be configured separately for different sizes of HARQ-ACK feedback, e.g., up to 2 bits (2-bit UCI with 1st beta offset), more than 2 bits up to 11 bits, more than 11 bits, CSI part 1 up to 11 bits, CSI part 1 more than 11 bits, CSI part 2 up to 11 bits, and / or CSI part 2 more than 11 bits. These offsets can be set / indicated semi-stationarily via RRC (Radio Resource Control Message) or by dynamically selecting the configuration using DCI. Beta offsets can be set separately for CSI and HARQ-ACK.

[0038] The alpha (α) value may be configured by a higher layer parameter "scaling" that is introduced to prevent the UCI from consuming all PUSCH resources (e.g., to ensure that at least some portion of the PUSCH is available for data transmission). The alpha value or alpha value may indicate the maximum amount of resources that the UCI may consume or use in the PUSCH. The alpha value may be indicated for the UCI.

[0039] Also, as used herein, the term beam or (UL) beam may refer to spatial relationship information, (separate) UL TCI state, joint or common TCI state, spatial filter, power control information (or configured power control parameters), SRS (Sounding Reference Signal) resource indicator (referring to one or more SRS resources) panel or panel ID (e.g., antenna panel identifier), quasi-location (QCL) information Type-D (or any other type), etc.

[0040] It should be noted that a UE panel (UE antenna panel) may be identified by an index of a corresponding UE capability value set or by a panel ID (panel identifier). Alternatively or additionally, a panel (or antenna panel) may be identified or associated by at least one reference signal (at least one downlink reference signal, such as an SSB (synchronization signal block) reference signal and / or a channel state information reference signal (CSI-RS)) or simply by a UL beam.

[0041] Release 18 may allow simultaneous PUSCH transmissions (e.g., two time-domain overlapping PUSCH transmissions), which may be transmitted to the same or different transmission / reception points (TRPs), e.g., to the same or different gNBs, and within the same (serving) cell. However, as mentioned above, when the PUCCH and PUSCH(s) overlap in time, the UE may transmit UCI on or within the PUSCH(s) (e.g., by piggybacking UCI onto the PUSCH), which may include the UE multiplexing UCI onto the PUSCH with UL data. Thus, when the PUSCH(s) overlap in time with the PUCCH carrying UCI, the UE may (is expected to) multiplex the content or bits of UCI onto the PUSCH(s). However, in the case of two PUSCHs with time domain overlap, there is currently no established rule on how the UE should map and / or transmit UCI content onto one or both of the time domain overlapping PUSCHs.

[0042] FIG. 2 illustrates a multi-TRP communication according to an example embodiment. As shown in FIG. 2, a UE 210 may communicate with (and / or be connected to) one or both of a transmission / reception point (TRP) 212 and / or 214. The TRPs 212 and 214 may be gNBs or other network nodes. In the example of FIG. 2, at 227, the UE 210 may receive two PUSCH allocations (e.g., PUSCH allocation #1, and PUSCH allocation #2) from a TRP(s) (e.g., from the TRP 212 and / or 214), e.g., via downlink control information (DCI) (or otherwise, the UE may receive, e.g., in the case of a configured grant PUSCH). The time-domain overlapping PUSCH allocations #1 and #2 may include at least time-frequency resources that may be used for PUSCH transmission. The PUSCH allocations #1 and #2 may include frequency resources that may overlap in time and may be fully / partially / non-overlapping.

[0043] 2, the UE 210 may map (225) the uplink control information (UCI) 220 (e.g., bits or content of the uplink control information (UCI 220)) to one or more of the PUSCH allocations (including in PUSCH Allocation #1 and / or PUSCH Allocation #2). Mapping (225) the UCI 220 to one or both (or one or more) PUSCH allocations may include, for example, assigning one or more of the UCI portions or bits to one or both (or one or more) of the PUSCH allocations for transmission (e.g., for transmission via the PUSCH transmission(s) corresponding to the PUSCH assignment). For example, mapping of UCI may include mapping UCI 220 (e.g., one or more UCI bits or portions) to PUSCH allocation #1 corresponding to PUSCH transmission #1 (230) and / or mapping UCI 220 (e.g., one or more UCI bits or portions) to PUSCH allocation #2 corresponding to PUSCH transmission #2 (240). Thus, PUSCH transmission #1 may include transmission by UE 210 of data (if any) and / or UCI (e.g., multiplexed data and UCI bits) over PUSCH allocation #1, and PUSCH transmission #2 may include transmission by UE 210 of data (if any) and / or UCI (e.g., multiplexed data and UCI bits). For example, mapping UCI 220 to a PUSCH allocation may include mapping corresponding coded UCI bits to the PUSCH allocation and / or multiplexing these coded UCI bits with data bits (if any).

[0044] In the present embodiment, two PUSCH allocations corresponding to two PUSCH transmissions are described, however, the techniques described herein may be applied to at least two (and possibly more than two) PUSCH allocations and corresponding transmissions, e.g., three, four, or more PUSCH allocations and corresponding PUSCH transmissions.

[0045] According to an example embodiment, the UE 210 may configure the UCI 220 (or at least one UCI 220) as: In one of at least two PUSCH allocations, separately for each of the at least two PUSCH allocations, Over at least two PUSCH allocations, The mapping (225, FIG. 2) can be performed according to at least one of the following:

[0046] Here, the mapping is (or may be) based on at least one of one or more configured or predefined rules (e.g., known and applied by the UE) or at least one indication (e.g., a message providing control information or a signal or other indication) received by the UE 210 from a TRP or a network node (e.g., gNB). As mentioned above, the PUSCH assignment may include resources (e.g., time-frequency resources and / or spatial resources such as beam(s)) assigned to the UE 210 for the corresponding PUSCH transmission. Examples of mapping based on one or more configured or predefined rules or at least one indication are described below.

[0047] Mapping the UCI to one of the at least two PUSCH allocations may include cases where the UCI is mapped to one (eg, only one and not both) of the PUSCH allocations.

[0048] Mapping the UCI across at least two PUSCH allocations may correspond to (or include) a case where a single codeword is mapped across the PUSCH allocations or a single RV (redundancy version) is used / indicated for both PUSCH allocations, in which case the same coded bits of the UCI are mapped across the PUSCH allocations, including cases where the coded bits of the UCI (e.g., all coded bits) are mapped to each (or both) of the PUSCH allocations, or cases where a first set (or a first portion) of coded bits of the UCI is mapped to PUSCH allocation #1 and a second set (or a second portion) of coded bits of the UCI is mapped to PUSCH allocation #2.

[0049] Mapping the UCI separately to each of the at least two PUSCH allocations may correspond to (or include) the case where different codewords are mapped to the PUSCH allocations, or the same codeword is mapped to both PUSCH allocations, e.g., different RVs are used / indicated for each PUSCH allocation, in which case parts of the UCI may be coded separately, with coded bits of one UCI part mapped to one PUSCH allocation and coded bits of the other UCI part mapped to the other PUSCH allocation.

[0050] In some embodiments, "mapping UCI across the PUSCH allocation" and "mapping UCI separately to (or onto) both PUSCH allocations" may correspond to or include the same thing and / or may correspond to one of the possibilities above.

[0051] 3 is a flow chart illustrating the operation of a user equipment or UE according to an example embodiment. Operation 310 includes a step of causing a user equipment (e.g., UE 210) in a wireless network to assign at least two time-domain overlapped physical uplink shared channel (PUSCH) assignments (e.g., PUSCH assignment #1 and PUSCH assignment #2, FIG. 2) corresponding to at least two PUSCH transmissions (e.g., corresponding to PUSCH transmission #1 (230) and PUSCH transmission #2 (240), respectively, FIG. 2) for use in transmitting at least one uplink control information (UCI 220, FIG. 2). Operation 320 includes mapping, by a user equipment (e.g., UE 210), a UCI (e.g., UCI 220, FIG. 2 ) to at least one of the at least two PUSCH allocations, either individually for each of the at least two PUSCH allocations, or across the at least two PUSCH allocations, the mapping based on at least one of one or more configured or predefined rules, or at least one indication received by the user equipment from a network node, the PUSCH allocation including resources assigned to the user equipment for PUSCH transmission.

[0052] In an example embodiment, the method of FIG. 3 may further include transmitting at least one uplink control information (e.g., PUSCH transmission #1 and / or PUSCH transmission #2, see FIG. 2) via one or both (or one or more) of the (at least two) PUSCH allocations based on the mapping (e.g., UCI 220, FIG. 2).

[0053] In an example embodiment, the mapping may be based on at least one of: 1) whether at least one UCI is scheduled for transmission on one of the at least two PUSCHs, or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH), which may be multiplexed onto one of the at least two PUSCHs.

[0054] In an example embodiment, if the UCI is scheduled for transmission on one or more of the at least two PUSCHs, the mapping may include mapping, by the user equipment or UE, the at least one UCI to each of the at least two PUSCH allocations separately or across the at least two PUSCH allocations, and if the at least one UCI is carried initially on a PUCCH that may be multiplexed into one of the PUSCHs, the mapping may include mapping, by the user equipment or UE 210, the at least one UCI to one of the at least two PUSCH allocations.

[0055] In an example embodiment, mapping of at least one UCI to one of the at least two PUSCH allocations may include mapping, by the user equipment or UE 210, the UCI to one of the at least two PUSCH allocations that correspond to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESETpoolindex), same CORESET group, same transmission configuration indication (TCI) state set, same reference signal set, or same corresponding PCI (physical cell ID) as the PUCCH.

[0056] In an example embodiment, the mapping of the at least one UCI may be based on whether the same data block or codeword is mapped to each of the at least two PUSCH allocations or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

[0057] In an example embodiment, if the same codeword or data block is mapped across the at least two PUSCH allocations, the mapping may include mapping, by the user equipment or UE, at least one UCI to the at least two PUSCH allocations separately or across both PUSCH allocations, and if different codewords or data blocks are mapped across the at least two PUSCH allocations, the mapping may include mapping, by the user equipment, the UCI to one corresponding to at least one of the at least two PUSCH allocations, including mapping the UCI to one of the at least two PUSCH allocations that corresponds to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESETpoolindex), same CORESET group, same set of transmission configuration indication (TCI) states, or same set of reference signals, or the same corresponding PCI (physical cell ID) as the PUCCH.

[0058] In an example embodiment, the mapping of the at least one UCI may be based on whether, for the same codeword, the same redundancy version (RV) of a data block is used or indicated for the at least two PUSCH allocations, or whether different redundancy versions (RVs) of a data block are used or indicated for the at least two PUSCH allocations.

[0059] In an example embodiment, if the same redundancy version (RV) of the data block is used for each of the at least two PUSCH allocations or separately across the at least two PUSCH allocations, the mapping may include mapping the UCI across the at least two PUSCH allocations by the user equipment, and if different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the mapping includes mapping the at least one UCI separately to each of the at least two PUSCH allocations or mapping the UCI to one of the at least two PUSCH allocations by the user equipment.

[0060] In an example embodiment, the mapping may be based on a beta offset value received by the user equipment or UE in the downlink control information.

[0061] In an example embodiment, a first subset of beta values ​​is associated with mapping at least one UCI to each of the at least two PUSCH allocations separately or across the at least two PUSCH allocations, and a second subset of beta values ​​is associated with mapping at least one UCI to one of the at least two PUSCHs.

[0062] In an exemplary embodiment, the mapping may be based on the number of layers that corresponds to each PUSCH allocation.

[0063] In an example embodiment, the mapping may include at least one of: mapping, by the user equipment or UE, at least one UCI to one of at least two PUSCH allocations having a higher or lower starting data block or frequency; or mapping, by the user equipment or UE, at least one UCI to one of at least two PUSCH allocations corresponding to a particular transmit reception point (TRP) or a particular transmit configuration indication (TCI) state or a particular PCI (Physical Cell ID).

[0064] In an example embodiment, the method may include determining, by a user equipment or UE, a first association between a beta offset and / or alpha value and a PUSCH allocation, determining, by the user equipment or UE, a second association between the beta offset and / or alpha value and a different capability value set or antenna panel, transmission / reception point (TRP), CORESETpool index or CORESET group, set of TCI states, set of reference signals, or PCI(s), and mapping, by the user equipment, mapping at least one UCI based on the first association and the second association.

[0065] In an example embodiment, the mapping may include mapping, by a user equipment or UE, of at least one UCI to a PUSCH assignment having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

[0066] 4 is a flow chart illustrating an operation of a network node (e.g., a transmission / reception point (TRP) or a gNB or other network node) in an example embodiment. Operation 410 includes transmitting, by the network node, to a user equipment, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may / can be used by the user equipment to transmit at least one uplink control information (UCI). Operation 420 includes receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations, wherein the at least one UCI has been mapped to at least one of the following or according to one of the following, to one of the at least two PUSCH allocations, to each of the at least two PUSCH allocations separately, or across the at least two PUSCH allocations: Operation 430 indicates that the at least one UCI has been mapped based on at least one of one or more configurations or predefined rules, or at least one instruction provided from the network node to the user equipment, and the PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission.

[0067] In an example embodiment, the at least one UCI may be mapped based on at least one of: 1) whether the at least one UCI is scheduled for transmission on one of the at least two PUSCHs, or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH) that may be multiplexed onto one of the at least two PUSCHs.

[0068] In an exemplary embodiment, at least one UCI is mapped to one of at least two PUSCH allocations that correspond to at least one of the same capability set, same antenna panel, same transmit reception point (TRP), same control resource set pool index (CORESETpoolindex), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH.

[0069] In an example embodiment, the at least one UCI is mapped based on whether the same data block or codeword is mapped to the at least two PUSCH allocations or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

[0070] In an exemplary embodiment, when the same codeword or data block is mapped across the at least two PUSCH allocations, the at least one UCI is mapped separately to the at least two PUSCH allocations or across the at least two PUSCH allocations, and when different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one corresponding to at least one of the at least two PUSCH allocations, and the at least one UCI is mapped to one of the at least two PUSCH allocations that corresponds to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESETpoolindex), same CORESET group, same transmission configuration indication (TCI) state set, same reference signal set, or same PCI as the PUCCH.

[0071] In an exemplary embodiment, the at least one UCI is mapped based on whether, for the same codeword, the same redundancy version (RV) of a data block is used or indicated for the at least two PUSCH allocations, or whether different redundancy versions (RVs) of a data block are used or indicated for the at least two PUSCH allocations.

[0072] In an exemplary embodiment, if the same redundancy version (RV) of a data block is used separately for each of the at least two PUSCH allocations or across the at least two PUSCH allocations, then the at least one UCI is mapped across the at least two PUSCH allocations, and if different redundancy versions (RVs) of a data block are used for the at least two PUSCH allocations, then the at least one UCI is mapped separately to each of the at least two PUSCH allocations or the UCI is mapped to one of the at least two allocations.

[0073] In an exemplary embodiment, the at least one UCI is mapped based on a beta offset value received by the user equipment in the downlink control information.

[0074] In an example embodiment, a first subset of beta values ​​is associated with mapping at least one UCI to each of the at least two PUSCH allocations separately or across the at least two PUSCH allocations, and a second subset of beta values ​​is associated with mapping at least one UCI to one of the at least two PUSCHs.

[0075] In an exemplary embodiment, the at least one UCI is mapped based on the layer number corresponding to each PUSCH allocation.

[0076] In an exemplary embodiment, at least one UCI is mapped to one of at least two PUSCH allocations having a higher or lower starting data block or frequency, or at least one UCI is mapped to one of at least two PUSCH allocations corresponding to a particular transmit reception point (TRP) or a particular transmit configuration indication (TCI) state.

[0077] In an example embodiment, at least one UCI is mapped to a PUSCH allocation having a transmission configuration indication (TCI) state that matches a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

[0078] For PUSCH allocations (or opportunities) that overlap in at least two time domains, DCI dynamic scheduling of the PUSCH allocation may be used, or the PUSCH allocation may be configured with grants (and not dynamically scheduled) corresponding to at least two PUSCH transmissions used to transmit at least one UCI.

[0079] In an example embodiment, the UCI may be mapped separately to one or both of the at least two PUSCH allocations (or to each of the at least two PUSCH allocations) (e.g., the UCI may be coded and then the coded UCI code bits may be transmitted over one or both of the PUSCH allocations, and the mapping of the UCI may be based on mapping the coded UCI bits, e.g., based on rate matching). For example, separately to both of the PUSCH allocations (or separately for each of the at least two), may mean or include that some of the UCI bits are transmitted / transmitted over PUSCH allocation #1 and transmitted over PUSCH transmission #1, and some other (e.g., different) UCI ​​bits are transmitted over PUSCH allocation #2 and transmitted over PUSCH transmission #2.

[0080] Also, for example, a PUSCH transmission may consider the case where the PUSCH carries a TB (transport block or block of data to be transmitted) (or carries multiple TBs) or does not carry a TB (i.e., the PUSCH carries UCI without UL-SCH data). Also, at least two time-overlapping PUSCH allocations corresponding to at least two PUSCH transmissions may use / apply two (UL or joint) TCI states.

[0081] In an example embodiment, the mapping to UCI (from at least one UCI) may depend on whether UCI is scheduled on PUSCH (such as A-CSI (aperiodic CSI) or SP (persistent)-CSI, both of which may be directly scheduled on PUSCH to transmit channel state information via PUSCH) (semi-persistent may also be on PUCCH and may be triggered separately) or whether UCI is carried initially on PUCCH, which may be multiplexed into PUSCH, and if UCI is scheduled on PUSCH (PUSCH is directly scheduled to carry UCI / CSI), In either case, the UE may map the UCI (which may be or may include CSI) to both PUSCH allocations separately or across both PUSCH allocations; if the UCI is carried first on a PUCCH that can be multiplexed into a PUSCH, the UE may map the UCI to one PUSCH allocation, which may be a PUSCH allocation corresponding to the same capability set (or panel), same TRP, same CORESETpoolindex, same CORESET group, same TCI state set, same RS set (SSB, CSI-RS, SRS, etc.) or same PCI as the PUCCH. In these cases (UCI results from any of these possibilities), the UE needs to decide whether to map the UCI to one PUSCH or to both PUSCHs.

[0082] In an example embodiment, the mapping of UCI (from at least one UCI) may depend on whether the same TB (or codeword) is mapped to both (or at least two) PUSCH allocations or different TBs (or codewords) are mapped to the at least two PUSCH allocations; if the same codeword is mapped across both PUSCH allocations, the UE may map the UCI across both PUSCH allocations or separately to both PUSCH allocations; or if different codewords are mapped to the at least two PUSCH allocations, the UE may map the UCI to one PUSCH allocation, such as a PUSCH allocation corresponding to the same capability value set (or panel) or the same TRP or the same CORESETpoolindex or the same CORESET group or the same TCI state set or the same RS set (SSB, CSI-RS, SRS (sounding reference signal), etc.) or capability value set or the same PCI as the (overlapping) PUCCH.

[0083] In an example embodiment, the mapping of UCI (from at least one UCI) depends on whether, for the same codeword, the same redundancy version (RV) is used / indicated for both PUSCH allocations or a different RV is used / indicated for each of the at least two PUSCH allocations: if the same redundancy version (RV) is used for both or more PUSCH allocations, the UE may map the UCI to the at least two PUSCH allocations, and if different RVs are used for the at least two PUSCH allocations, the UE may map the UCI to each PUSCH allocation separately. Alternatively, the UE may map the UCI to one PUSCH allocation.

[0084] In an example embodiment, the mapping of UCI may depend on an indication (new or existing) carried in the DCI, such as DCI scheduling a PUSCH allocation or an indication via RRC signaling such as a beta offset. As an example, a subset of beta offset values ​​is associated with mapping UCI to or across both PUSCH allocations, and another subset of beta offset values ​​is associated with mapping UCI to one PUSCH allocation. Thus, once the beta offset for UCI is indicated, the UE can know whether to map UCI to both PUSCH allocations, across both PUSCH allocations, or to one PUSCH allocation.

[0085] In an example embodiment, the mapping of UCI may depend on the number of layers corresponding to each PUSCH assignment / transmission, and if the number of layers is the same for the at least two PUSCH assignments / transmissions, the UE may map UCI to both PUSCH assignments separately or across both (or at least two) PUSCH assignments, or if the number of layers corresponding to one of the at least two PUSCH assignments / transmissions is equal to or greater than a certain threshold, the UE may map UCI to this PUSCH assignment. For example, if the number of layers corresponding to one of the at least two PUSCH assignments / transmissions is equal to or less than a certain threshold, the UE may not map UCI to this PUSCH assignment.

[0086] In an example embodiment, mapping the UCI to a PUSCH assignment / transmission may include mapping corresponding coded UCI bits to the PUSCH assignment / transmission and / or multiplexing these coded UCI bits with data bits (if any).

[0087] In an example embodiment, mapping the UCI to at least two PUSCH allocations may include first mapping the coded UCI bits to one PUSCH allocation (e.g., in a frequency-first time-second manner, starting from a lower frequency for PUSCH allocations in case of PUSCH allocations in FDM), and then continuing the mapping to the other PUSCH allocation as needed (e.g., in a frequency-first time-second manner). Regarding which PUSCH allocation to start mapping to, if the UCI is mapped to both PUSCH allocations, the UE may start mapping to a PUSCH allocation with a higher / lower starting RB (starting from the upper or lower end of the frequency range) in the frequency domain allocation. For example, mapping may start to a PUSCH allocation corresponding to a given TRP or TCI state, such as for FDM-like PUSCH operation, or a first indication / applicable TCI state for SDM / FDM PUSCH operation. Alternatively, the UE may be indicated via DCI, Medium Access Control (MAC) Control Element (CE), and / or Radio Resource Control (RRC) which PUSCH allocation to start mapping on. In one variation, the UE may map the UCI evenly or approximately evenly across at least two PUSCH allocations (which may be required, for example, for SDM PUSCH operation / schemes).

[0088] In an exemplary embodiment, the difference (if any) between mapping UCI to both PUSCH allocations separately and mapping across both PUSCH allocations is as follows for an exemplary embodiment: Mapping UCI across PUSCH allocations may correspond to the case where a single codeword is mapped across PUSCH allocations or a single RV is used / indicated for both (or at least two) PUSCH allocations. In this case, coded bits of the same UCI are mapped across at least two PUSCH allocations. Also, mapping UCI to both PUSCH allocations separately may correspond to the case where different codewords are mapped to PUSCH allocations or, for the same codeword mapped to both PUSCH allocations, different RVs are used / indicated for each PUSCH allocation. In this case, parts of UCI may be coded separately, and coded bits of one UCI part may be mapped to one PUSCH allocation and coded bits of the other UCI part may be mapped to the other PUSCH allocation, or coded bits of the same UCI are mapped to each PUSCH allocation.

[0089] If the UE is scheduled or instructed to perform coherent joint transmission operation, e.g., where the same layer(s) of the same codeword are transmitted over two panels (with some coherency) using two PUSCH opportunities or allocations, the UE may map the UCI across both PUSCH allocations.

[0090] If the UE is scheduled or instructed to perform SFN-like transmission operation, e.g., where the same layer(s) of the same codeword are repeated using each PUSCH opportunity or allocation across two panels, the UE may map the UCI to both PUSCH allocations where the UCI is repeated / mapped in exactly the same manner in each PUSCH allocation.

[0091] In some other embodiments, "mapping UCI across the PUSCH allocation" and "mapping UCI separately to both PUSCH allocations" may correspond / refer to the same thing and may correspond to one of the example examples or descriptions above.

[0092] For example, it should be noted that when mapping UCI to at least two PUSCH allocations, the amount of resources (e.g., the number of REs (resource elements)) that the coded UCI bits can occupy in the first and second PUSCH allocations is either defined using a single beta offset or is defined using at least two beta offset values ​​(where the beta offset can be per UCI type / portion). Furthermore, there may be a single alpha (i.e., scaling parameter) value that puts an upper limit on the amount of resources that the UCI can occupy (i.e., consume) in the at least two PUSCH allocations. Alternatively, there may be at least two alpha values ​​that respectively put an upper limit on the amount of resources that the UCI can occupy (or consume) in the first and second PUSCH allocations.

[0093] In an example embodiment, there may be an association between different capability value sets (or panels) or TRPs or CORESETpool indices or CORESET groups or sets of TCI states or sets of RSs (SSB, CSI-RS, SRS, etc.) and beta offset value(s) and / or alpha value(s), and the UE may determine which beta offset value or alpha value corresponds to which PUSCH assignment based on the association. (For example, there will be an association between each of those TCI states and each PUSCH, and thus there may be an association between the beta offset and the TCI state, and based on the association between the two, the UE may determine which PUSCH to use based on the configured beta offset.)

[0094] In an example embodiment, for joint HARQ-ACK feedback (for multiple DCI mode) carried first on the PUCCH that may be multiplexed into the PUSCH, the HARQ-ACK feedback / bit corresponding to the first TRP or CORESETPool index or CORESET group or PCI, etc. may be mapped to the corresponding PUSCH allocation, and the HARQ-ACK feedback / bit corresponding to the second TRP or CORESETPool index or CORESET group or PCI, etc. may be mapped to the corresponding PUSCH allocation.

[0095] In an example embodiment, in the case of two HARQ-ACK sub-codebooks, the existing (total) DAI (Downlink Allocation Indicator) field in the (UL) DCI may be reused or reinterpreted to indicate whether the corresponding sub-codebook should be mapped to both PUSCH allocations and if so, to which PUSCH allocation, or to one PUSCH allocation and if so, to which PUSCH allocation, or a new indication in the DCI (or MAC CE or RRC), jointly or separately with the DAI field, may be used to indicate which sub-codebook is mapped to which PUSCH allocation (or even if the sub-codebook should not be mapped to a PUSCH allocation).

[0096] In an example embodiment, to map UCI to two PUSCH allocations, the number of coded modulation symbols per layer for UCI may be determined jointly based on both PUSCH allocations (e.g., in the case of a joint beta offset (and / or alpha factor) for both PUSCH allocations), where the number of resource elements that can be used for transmission of UCI in the OFDM symbol(s) may correspond to both PUSCH allocations. Alternatively, the number of coded modulation symbols per layer for UCI may be determined separately for each PUSCH allocation (e.g., in the case of a separate beta offset (and / or alpha factor) for the PUSCH allocations), where the number of resource elements that can be used for transmission of UCI in the OFDM symbol(s) in the PUSCH allocation may correspond only to this PUSCH allocation.

[0097] In an example embodiment, the UCI mapping to the PUSCH allocation may be based on rate matching the coded UCI bits in this PUSCH or on puncturing the coded UCI bits in this PUSCH.

[0098] The UCI mapping to the PUSCH allocation or to the two PUSCH allocations in an example embodiment may be done on a per-layer basis.

[0099] In an example embodiment, the at least one UCI may be UCI scheduled on the PUSCH (such as A-CSI or SP-CSI scheduled / activated on the PUSCH) and / or UCI originally carried on the PUCCH (such as HARQ-ACK and / or CSI) that may be multiplexed into the PUSCH.

[0100] In an example embodiment, in case of frequency hopping, UCI may be mapped to both PUSCH hops for PUSCH allocation, so that any of the above proposed mapping operations may be applied per PUSCH hop.

[0101] It should be noted that although UCI mapping considering single DCI (or even multiple DCI) simultaneous PUSCH transmission operation has been described, a similar aspect can also be applied to UCI multiplexing / mapping considering single DCI (or even multiple DCI) simultaneous PUCCH transmission operation. At least some of the above aspect can be adapted to the PUCCH case by essentially replacing PUSCH with PUCCH and TB (transport block) with "first UCI".

[0102] FIG. 5 illustrates a mapping of UCI (e.g., CSI) to two PUSCH allocations corresponding to two simultaneous PUSCH transmissions based on an indicated beta offset. The PDCCH may carry or include DCI. The simultaneous PUSCH transmissions are scheduled (indicated to the UE via DCI or scheduling information) and control information may be transmitted to the UE indicating, for each CSI part, a beta offset that may correspond to a PUSCH allocation or PUSCH transmission, respectively. For example, as shown in FIG. 5, A-CSI may be mapped to PUSCH allocation #0 and A-CSI may be mapped to PUSCH allocation #1.

[0103] FIG. 6 illustrates a mapping of UCI to PUSCH in another exemplary embodiment based on scheduling of simultaneous PUSCH operation. FIG. 6 illustrates an example where UCI is mapped to a PUSCH assignment with a transmission configuration indication (TCI) state matching the TCI state of a physical uplink control channel (PUCCH) associated with at least one UCI. TCI state #1 and TCI state #2 in this embodiment correspond to the same capability value set or TRP or CORESET group (or CORESETPoolIndex) or the same UE antenna panel or the same PCI or the same TCI state group / pool or the same reference signal group. The arrow indicates multiplexing, e.g., HARQ ACK is multiplexed into PUSCH. As shown, PUCCH has TCI state #2, which corresponds to the same e.g., TRP or CORESETPoolIndex as TCI state #1. Thus, the UE in this embodiment maps UCI (e.g., HARQ-ACK) of PUCCH to PUSCH transmission #0 with TCI state #1.

[0104] Some further examples will now be described.

[0105] [Example 1] determining, by a user equipment in the wireless network, at least two physical uplink shared channel (PUSCH) allocations that overlap in the time domain and correspond to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); The at least one UCI is At least one of the at least two PUSCH allocations; Separately for each of the at least two PUSCH allocations, over the at least two PUSCH allocations, Mapping with at least one of Including, said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. method. [Example 2] transmitting the at least one UCI over one or more of the at least two PUSCH allocations based on the mapping; The method of Example 1, further comprising:

[0106] [Example 3] The mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, further comprises: 1) whether the at least one UCI is scheduled to be transmitted on one of the at least two PUSCHs; or 2) whether the at least one UCI is transmitted first on a physical uplink control channel (PUCCH) that may be multiplexed into one of the at least two PUSCHs; The method of any one of the preceding claims, further comprising: mapping at least one UCI based on at least one of:

[0107] [Example 4] If the UCI is scheduled for transmission on one or both of the at least two PUSCHs, the mapping includes mapping, by the user equipment, the at least one UCI to each of the two PUSCH allocations separately or across the at least two PUSCH allocations; If the at least one UCI is initially carried on the PUCCH that may be multiplexed into one of the at least two PUSCHs, the mapping includes mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations. The method described in Example 3.

[0108] [Example 5] Mapping the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, comprises: Mapping the UCI to one of the at least two PUSCH allocations that corresponds to at least one of the following: a same capability set, a same antenna panel, a same transmission / reception point (TRP), a same control resource set pool index (CORESET pool index), a same CORESET group, a same transmission configuration indication (TCI) state set, a same reference signal set, or a same physical cell ID (PCI) as a PUCCH by the user equipment. The method of Example 4, comprising:

[0109] [Example 6] Mapping the at least one UCI based on at least one of one or more settings or predefined rules, or at least one indication of the at least one UCI, comprises: whether the same data block or codeword is mapped to the at least two PUSCH allocations; or whether different data blocks or codewords are mapped to the at least two PUSCH allocations;

[0033] including mapping based on The method according to any one of Examples 1 to 5.

[0110] [Example 7] If the same codeword or data block is mapped across the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, includes mapping, by the user equipment, the at least one UCI to the two PUSCH allocations separately or across the at least two PUSCH allocations; If different codewords or data blocks are mapped across the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, includes mapping, by the user equipment, the UCI to one of the at least two PUSCH allocations that corresponds to at least one of the same capability value set, the same antenna panel, the same transmission / reception point (TRP), the same control resource set pool index (CORESET pool index), the same CORESET group, the same transmission configuration indication (TCI) state set, the same reference signal set, or the same PCI as the PUCCH. The method described in Example 6.

[0111] [Example 8] The mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, further comprises: whether or not the same redundancy version (RV) of a data block is used or indicated for both of the at least two PUSCH allocations for the same codeword; or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH allocations; mapping the at least one UCI based on The method according to any one of Examples 1 to 7.

[0112] [Example 9] If the same redundancy version (RV) of the data block is used separately for or across both of the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configured or predefined rules or at least one instruction includes mapping, by the user equipment, the UCI across both of the at least two PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, includes: mapping, by the user equipment, the at least one UCI to each of the at least two PUSCH allocations separately, or mapping the UCI to one of the at least two PUSCH allocations. The method described in Example 8.

[0113] [Example 10] 10. The method according to any one of claims 1 to 9, wherein the mapping of the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, includes mapping based on a beta offset value received by the user equipment in downlink control information.

[0114] [Example 11] a first subset of beta values ​​associated with mapping the at least one UCI to both of the at least two PUSCH allocations separately or across both of the at least two PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the at least two PUSCHs. The method described in Example 10.

[0115] [Example 12] 12. The method according to any one of embodiments 1 to 11, wherein the mapping is based on a layer number corresponding to each of the at least two PUSCH allocations.

[0116] [Example 13] The mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, further comprises: Mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations having a higher or lower starting data block or frequency; Mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations corresponding to a particular transmit reception point (TRP) or a particular transmit configuration indication (TCI) state; 13. The method according to any one of claims 1 to 12, comprising at least one of:

[0117] [Example 14] determining, by the user equipment, a first association between a beta offset and / or an alpha value and the at least two PUSCH allocations; and / or determining, by the user equipment, a second association between a beta offset and / or an alpha value and a different set of capability values ​​or antenna panels, a transmission / reception point (TRP), a CORESETpool index or CORESET group, a set of TCI states, or a set of reference signals; Including, and mapping the at least one UCI based on at least one of one or more settings or predefined rules or at least one instruction includes mapping, by the user equipment, the at least one UCI based on the first association and / or the second association. The method according to any one of Examples 1 to 13.

[0118] [Example 15] mapping the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction; matching, by the user equipment, the at least one UCI to a PUSCH allocation having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI; The method according to any one of Examples 1 to 14, comprising:

[0119] [Example 16] An apparatus comprising: At least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code, using the at least one processor, cause the device to at least: determining, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); by said user equipment, One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, over the at least two PUSCH allocations, Mapping the UCI by at least one of The method is configured to: said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. Device.

[0120] [Example 17] The at least one processor and the computer program code cause the apparatus to: transmitting the at least one uplink control information via one or more PUSCH allocations of the at least two PUSCH allocations based on the mapping. The apparatus of Example 16, further configured to: [Example 18] The at least one processor and computer program code configured to cause the device to perform mapping based on at least one of one or more settings or predefined rules, or at least one instruction, comprising: 1) whether the at least one UCI is scheduled for transmission on one of the at least two PUSCHs; or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH), which may be multiplexed onto one of the at least two PUSCHs; based on at least one of 18. The device according to any one of Examples 16 to 17,

[0121] [Example 19] The at least one processor and the computer program code cause the apparatus to: If the UCI is scheduled for transmission on one or both PUSCHs, the mapping comprises mapping the at least one UCI by the user equipment to both PUSCH allocations separately or across both PUSCH allocations; If the at least one UCI is initially carried on the PUCCH that may be multiplexed into one of the PUSCHs, the mapping includes mapping the at least one UCI to one of the PUSCH allocations by the user equipment. The apparatus of Example 18, configured to perform the steps of:

[0122] [Example 20] The at least one processor and the computer program code configured to cause the device to perform mapping based on at least one of one or more settings or predefined rules, or at least one instruction, further comprising: Mapping the UCI to one of the PUSCH allocations corresponding to at least one of the same capability set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH by the user equipment. 20. The apparatus of example 19, comprising the at least one processor and the computer program code configured to perform the steps of:

[0123] [Example 21] The at least one processor and the computer program code configured to cause the apparatus to map the at least one UCI to one of the PUSCH allocations based on at least one step of one or more configurations or predefined rules or at least one instruction, the at least one processor and the computer program code configured to cause the apparatus to: Whether the same data block or codeword is mapped to both PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; and mapping the at least one UCI based on The at least one processor and the computer program code are configured to execute the steps of: 21. A device according to any one of Examples 16 to 20.

[0124] [Example 22] The at least one processor and the computer program code cause the apparatus to: If the same codeword or data block is mapped across both PUSCH allocations, the mapping includes mapping, by the user equipment, the at least one UCI separately to both PUSCH allocations or across both PUSCH allocations; When different codewords or data blocks are mapped across at least two PUSCH allocations, the mapping includes mapping the UCI by the user equipment to one of the PUSCH allocations that corresponds to at least one of the same capability set, the same antenna panel, the same transmission / reception point (TRP), the same control resource set pool index (CORESET pool index), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set as the PUCCH. The apparatus of Example 21, configured to perform the steps of:

[0125] [Example 23] The at least one processor and the computer program code configured to cause the device to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, comprising: For the same codeword, the same redundancy version (RV) of a data block is used or indicated for both PUSCH allocations, or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; 23. An apparatus as described in any one of Examples 16 to 22, comprising the at least one processor and the computer program code configured to cause the apparatus to perform mapping of the at least one UCI based on:

[0126] [Example 24] The at least one processor and the computer program code cause the apparatus to: If the same redundancy version (RV) of the data block is used for both PUSCH allocations separately or across both PUSCH allocations, the mapping includes mapping the UCI by the user equipment across both PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the mapping may be further determined by the user equipment as follows: Mapping the at least one UCI separately to each of the PUSCH allocations; or mapping the UCI to one of the PUSCH allocations; Including, The apparatus of Example 23, configured to perform the steps of:

[0127] [Example 25] The at least one processor and the at least one computer program code configured to cause the device to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, include the at least one processor and the at least one computer program code configured to cause the device to map based on a beta offset value received by the user equipment in downlink control information. 25. A device according to any one of Examples 16 to 24.

[0128] [Example 26] a first subset of beta values ​​associated with mapping the at least one UCI to both PUSCH allocations separately or across both PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the PUSCHs. The apparatus described in Example 25.

[0129] [Example 27] The at least one processor and the computer program code configured to cause the apparatus to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one processor and the computer program code configured to map based on a layer number corresponding to each PUSCH allocation. 27. A device according to any one of Examples 16 to 26.

[0130] [Example 28] The at least one processor and the computer program code are configured to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, Mapping, by the user equipment, the at least one UCI to one of the PUSCH allocations having a higher or lower starting data block or frequency; or Mapping, by the user equipment, the at least one UCI to one of the PUSCH allocations corresponding to a particular transmit reception point (TRP) or a particular transmit configuration indication (TCI) state. the at least one processor and the computer program code configured to perform at least one of the following: 28. A device according to any one of Examples 16 to 27.

[0131] [Example 29] The at least one processor and the computer program code cause the apparatus to: determining, by the user equipment, a first association between a beta offset and / or an alpha value and a PUSCH allocation; and determining, by the user equipment, a second association between a beta offset and / or an alpha value and a different capability set or antenna panel, a transmission / reception point (TRP), a CORESETpool index or CORESET group, a set of TCI states, or a set of reference signals. The method is configured to: the at least one processor and the at least one computer program code configured to cause the device to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one processor and the at least one computer program code configured to cause the device to map, by the user equipment, the at least one UCI based on the first association and the second association; 29. A device according to any one of Examples 16 to 28.

[0132] [Example 30] The at least one processor and the computer program code are configured to cause the device to map at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one processor and the computer program code being configured to: mapping, by the user equipment, the at least one UCI to a PUSCH allocation having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI; the at least one processor and the computer program code configured to 30. A device according to any one of Examples 16 to 29.

[0133] [Example 31] transmitting, by a network node to a user equipment, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, wherein the at least one UCI comprises: One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, over the at least two PUSCH allocations, is mapped to at least one of Including, at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one indication provided by the network node to the user equipment; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. method.

[0134] [Example 32] The at least one UCI is mapped based on at least one of one or more settings or predefined rules or at least one instruction. 1) whether the at least one UCI is scheduled to be transmitted on one of the PUSCHs; or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH) that may be multiplexed into one of the PUSCHs; The method of example 31, wherein the at least one UCI is mapped based on at least one of the following:

[0135] [Example 33] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped to one of the PUSCH allocations corresponding to at least one of the same capability value set, the same antenna panel, the same transmission / reception point (TRP), the same control resource set pool index (CORESET pool index), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set as the PUCCH allocation. The method described in Example 32.

[0136] [Example 34] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, whether the same data block or codeword is mapped to both PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; The at least one UCI is mapped based on A method according to any one of Examples 31 to 33.

[0137] [Example 35] if the same codeword or data block is mapped across both PUSCH allocations, the at least one UCI is mapped separately to both PUSCH allocations or across both PUSCH allocations; When different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one of the PUSCH allocations that corresponds to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH. The method described in Example 33.

[0138] [Example 36] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, For the same codeword, the same redundancy version (RV) of a data block is used or indicated for both PUSCH allocations, or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; 36. The method of any one of claims 31 to 35, wherein the at least one UCI is mapped based on:

[0139] [Example 37] If the same redundancy version (RV) of the data block is used for both PUSCH allocations separately or across both PUSCH allocations, the at least one UCI is mapped across both PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the at least one UCI is mapped separately to each of the PUSCH allocations, or the UCI is mapped to one of the PUSCH allocations. The method described in Example 36.

[0140] [Example 38] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one UCI is mapped based on a beta offset value received by the user equipment in downlink control information. The method according to any one of Examples 31 to 37.

[0141] [Example 39] a first subset of beta values ​​associated with mapping the at least one UCI to both PUSCH allocations separately or across both PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the PUSCHs. The method described in Example 38.

[0142] [Example 40] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped based on a layer number corresponding to each PUSCH allocation. The method according to any one of Examples 31 to 39.

[0143] [Example 41] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped to one of the PUSCH allocations having a higher or lower starting data block or frequency, or The at least one UCI is mapped to one of the PUSCH allocations corresponding to a particular transmission / reception point (TRP) or a particular transmission configuration indication (TCI) state. the at least one UCI is mapped based on at least one of the following: The method according to any one of Examples 31 to 39.

[0144] [Example 42] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one UCI is mapped to a PUSCH allocation having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI. The method according to any one of Examples 31 to 41.

[0145] [Example 43] An apparatus comprising: At least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code, using the at least one processor, cause the device to: transmitting, by a network node, downlink control information to a user equipment, the downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, wherein the at least one UCI comprises: One of the at least two PUSCH allocations, or, separately for each of the at least two PUSCH allocations; over the at least two PUSCH allocations, is mapped to at least one of The method is configured to at least: The at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one instruction provided from the network node to the user equipment; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. Device.

[0146] [Example 44] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, 1) whether the at least one UCI is scheduled to be transmitted on one of the PUSCHs; or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH), which may be multiplexed into one of the PUSCHs; The at least one UCI is mapped based on at least one of The device described in Example 43.

[0147] [Example 45] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped to one of the PUSCH allocations corresponding to at least one of the same capability value set, the same antenna panel, the same transmission / reception point (TRP), the same control resource set pool index (CORESET pool index), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set as the PUCCH. The device described in Example 44.

[0148] [Example 46] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, whether the same data block or codeword is mapped to both PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; The at least one UCI is mapped based on 46. ​​A device according to any one of Examples 43 to 45.

[0149] [Example 47] if the same codeword or data block is mapped across both PUSCH allocations, the at least one UCI is mapped separately to both PUSCH allocations or across both PUSCH allocations; When different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one of the PUSCH allocations that corresponds to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH. The apparatus described in Example 45.

[0150] [Example 48] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, For the same codeword, the same redundancy version (RV) of a data block is used or indicated for both PUSCH allocations, or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; The at least one UCI is mapped based on 48. A device according to any one of Examples 43 to 47.

[0151] [Example 49] If the same redundancy version (RV) of the data block is used for both PUSCH allocations separately or across both PUSCH allocations, the at least one UCI is mapped across both PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the at least one UCI is mapped to each of the PUSCH allocations separately or to one of the PUSCH allocations. The apparatus described in Example 48.

[0152] [Example 50] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one UCI is mapped based on a beta offset value received by the user equipment in downlink control information. 50. A device according to any one of Examples 43 to 49.

[0153] [Example 51] a first subset of beta values ​​associated with mapping the at least one UCI to both PUSCH allocations separately or across both PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the PUSCHs. The device described in Example 50.

[0154] [Example 52] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped based on a layer number corresponding to each PUSCH allocation. 52. A device according to any one of Examples 43 to 51.

[0155] [Example 53] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped to one of the PUSCH allocations having a higher or lower starting data block or frequency; or the at least one UCI is mapped to one of the PUSCH allocations corresponding to a particular transmission / reception point (TRP) or a particular transmission configuration indication (TCI) state; The at least one UCI is mapped based on at least one of 52. A device according to any one of Examples 43 to 51.

[0156] [Example 54] The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one UCI is mapped to a PUSCH allocation having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI. 54. A device according to any one of Examples 43 to 53.

[0157] [Example 55] When executed by at least one processor, the computing system is provided with: transmitting, by a network node, downlink control information to a user equipment, the downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, wherein the at least one UCI comprises: One of the at least two PUSCH allocations, or, separately for each of the at least two PUSCH allocations; over the at least two PUSCH allocations, receiving a signal having a plurality of sigma-based address spaces, the signal having a plurality of sigma-based address spaces being mapped to at least one of the sigma-based address spaces; A non-transitory computer-readable storage medium having stored thereon instructions configured to cause a computer to execute The at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one instruction provided from the network node to the user equipment; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. A non-transitory computer-readable storage medium.

[0158] [Example 56] means for transmitting, by a network node, to a user equipment, downlink control information including information indicating at least two time-domain overlapped Physical Uplink Shared Channel (PUSCH) allocations that may be used by the user equipment to transmit at least one Uplink Control Information (UCI); A means for receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, the at least one UCI comprising: One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, over the at least two PUSCH allocations, a receiving means for receiving the signal, the receiving means being mapped to at least one of the following: Including, The at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one instruction provided by the network node to the user equipment; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. Device.

[0159] [Example 57] When executed by at least one processor, the computing system is provided with: determining, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); The UCI is One of the at least two PUSCH allocations, or, separately for each of the at least two PUSCH allocations; over the at least two PUSCH allocations, Mapping with at least one of A non-transitory computer-readable storage medium having stored thereon instructions configured to cause a said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. A non-transitory computer-readable storage medium.

[0160] [Example 58] Means for determining, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); The UCI is One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, over the at least two PUSCH allocations, and a means for mapping the An apparatus comprising: said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission. Device.

[0161] 7 is a block diagram of a network node (e.g., AP, BS, eNB, gNB, RAN node) 1200 in an exemplary embodiment. The wireless station 1200 may include, for example, one or more (e.g., two as shown in FIG. 7) RF (radio frequency) or wireless transceivers 1202A, 1202B, each of which includes a transmitter for transmitting signals and a receiver for receiving signals. The wireless station also includes a processor or control unit / entity (controller) 1204 for executing instructions or software and controlling the transmission and reception of signals, and a memory 1206 for storing data and / or instructions.

[0162] The processor 1204 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. The processor 1204 may be, for example, a baseband processor and may generate messages, packets, frames or other signals for transmission via the wireless transceiver 1202 (1202A or 1202B). The signal processor 1204 may control the transmission of signals or messages over a wireless network and may control the reception of signals or messages, etc. (e.g., after being downconverted by the wireless transceiver 1202) over a wireless network. The processor 1204 may be programmable and may execute software or other instructions stored on a memory or other computer medium to perform various tasks and functions described above, such as one or more tasks or methods described above. The processor 1204 may be (or may include), for example, hardware, programmable logic, a programmable processor executing software or firmware, and / or any combination thereof. Using other terminology, the processor 1204 and the transceiver 1202 together may be considered, for example, as a wireless transceiver system.

[0163] Further, with reference to FIG. 7, controller (or processor) 1208 may execute software and instructions and may provide overall control of station 1200, may provide control of other systems not shown in FIG. 7, such as control of input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 1200, such as, for example, an email program, an audio / video application, a word processor, a voice-over-IP application, or other applications or software.

[0164] Additionally, a storage medium may be provided containing instructions stored thereon that, when executed by a controller or processor, may cause the processor 1204, or another controller or processor, to perform one or more of the functions or tasks described above.

[0165] In another exemplary embodiment, the RF or wireless transceiver(s) 1202A / 1202B can receive signals or data and / or transmit or transmit signals or data. The signal processor 1204 (and possibly the transceiver 1202A / 1202B) can control the RF or wireless transceiver 1202A or 1202B to receive, transmit, broadcast or transmit signals or data.

[0166] The embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof. The embodiments may be implemented as a computer program product, i.e., a computer program tangentially embodied in an information carrier, e.g., a machine-readable storage device or a propagating signal, for execution by or to control the operation of a data processing device, e.g., a programmable processor, a computer, or a plurality of computers. The embodiments may also be provided on a computer-readable medium or a computer-readable storage medium, which may be a non-transitory medium. The embodiments of the various techniques may also include embodiments provided via a transitory signal or medium, and / or embodiments of programs and / or software downloadable via the Internet or other networks, either wired and / or wireless networks. Furthermore, the embodiments may be provided via machine-based communication (MTC) and / or via the Internet of Things (IOT).

[0167] The computer program may be in source code form, object code form, or some intermediate form, and may be stored on some kind of carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying a program. Such carriers include, for example, recording media, computer memory, read-only memory, optical and / or electrical carrier signals, telecommunications signals, software distribution packages, etc. Depending on the processing power required, the computer program may be executed on a single electronic digital computer or may be distributed across several computers.

[0168] Additionally, various embodiments of the technology described herein may use cyber-physical systems (CPS), a system of cooperating computational elements that control a physical entity. CPS may enable the realization and utilization of a large number of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects in different locations. Mobile cyber-physical systems are a subcategory of cyber-physical systems, where the physical system in question has inherent mobility. Examples of mobile physical systems include mobile robots and electronic devices that are moved by humans or animals. The popularity of smartphones has led to an increased interest in the field of mobile cyber-physical systems. Thus, various embodiments of the technology described herein may be provided via one or more of these technologies.

[0169] Computer programs such as those described above can be written in any format, including compiled or interpreted languages, and can be deployed in any format, such as a stand-alone program or as a module, component, subroutine, or other unit or portion thereof suitable for use in a computing environment. A computer program can be deployed to be executed on one computer, on multiple computers at a single site, or distributed across multiple sites and interconnected by a communications network.

[0170] The method steps may be performed by one or more programmable processors executing computer programs or computer program portions to perform functions by operating on input data and generating output. The method steps may also be performed by special purpose logic circuitry, for example an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), or may be implemented as an apparatus.

[0171] Processors suitable for executing computer programs include, by way of example, both general purpose and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Typically, a processor receives instructions and data from a read-only memory or a random access memory, or both. Elements of a computer may include at least one processor for executing instructions, and one or more memory devices for storing instructions and data. Typically, a computer may also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, operatively coupled to receive data from, transfer data to, or both. Information carriers suitable for carrying computer program instructions and data include, by way of example, all forms of non-volatile memory, including semiconductor memory devices, such as EPROM, EEPROM, and Flash memory devices, magnetic disks, such as internal hard disks or removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0172] To provide for user interaction, embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user, and a user interface, such as a keyboard and pointing device, e.g., a mouse or trackball, by which the user may provide input to the computer. Other types of devices may also be used to provide for user interaction. For example, feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, haptic feedback, etc., and input from the user may be received in any form, such as acoustic input, speech input, haptic input, etc.

[0173] The embodiments may be implemented in a computing system including a back-end component, e.g., a data server, or a computing system including a middleware component, e.g., an application server, or a computing system including a front-end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with the embodiments, or any combination of such back-end, middleware, or front-end components. The components may be interconnected by any form or medium of digital data communication, e.g., a communications network. Examples of communications networks include local area networks (LANs) and wide area networks (WANs), e.g., the Internet.

[0174] While certain features of the described embodiments have been illustrated as described herein, many modifications, substitutions, changes and equivalents will occur to those skilled in the art. It is therefore to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

1. determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations that overlap in the time domain and correspond to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); The at least one UCI is transmitted by the user equipment. At least one of the at least two PUSCH assignments; Separately for each of the at least two PUSCH allocations, Over the at least two PUSCH allocations, Mapping with at least one of Including, said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. method.

2. transmitting the at least one UCI over one or more of the at least two PUSCH allocations based on the mapping; The method of claim 1 further comprising:

3. The mapping of the at least one UCI based on at least one of one or more configuration or predefined rules, or at least one instruction, comprises: 1) whether the at least one UCI is scheduled to be transmitted on one of the at least two PUSCHs; or 2) whether the at least one UCI is transmitted first on a physical uplink control channel (PUCCH) that may be multiplexed into one of the at least two PUSCHs; The method of claim 1 or 2, further comprising: mapping at least one UCI based on at least one of:

4. If the UCI is scheduled for transmission on one or both of the at least two PUSCHs, the mapping includes mapping, by the user equipment, the at least one UCI to each of the two PUSCH allocations separately or across the at least two PUSCH allocations; If the at least one UCI is initially carried on the PUCCH that may be multiplexed into one of the at least two PUSCHs, the mapping includes mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations. The method according to claim 3.

5. Mapping the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, comprises: Mapping the UCI to one of the at least two PUSCH allocations that corresponds to at least one of the same capability set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, same reference signal set, or same physical cell ID (PCI) as a PUCCH by the user equipment. The method of claim 4 comprising:

6. Mapping the at least one UCI based on at least one of one or more configuration or predefined rules or at least one indication of the at least one UCI includes: whether the same data block or codeword is mapped to the at least two PUSCH allocations; or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; [0033] including mapping based on 6. The method according to any one of claims 1 to 5.

7. If the same codeword or data block is mapped across the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configurations or predefined rules or at least one indication comprises mapping, by the user equipment, the at least one UCI separately to the two PUSCH allocations or across the at least two PUSCH allocations; If different codewords or data blocks are mapped across the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one indication, includes mapping, by the user equipment, the UCI to one of the at least two PUSCH allocations that corresponds to at least one of the same capability set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, same reference signal set, or same PCI as the PUCCH. The method according to claim 6.

8. The mapping of the at least one UCI based on at least one of one or more configuration or predefined rules, or at least one instruction, comprises: whether or not the same redundancy version (RV) of a data block for the same codeword is used or indicated for both of the at least two PUSCH allocations; or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; mapping the at least one UCI based on A method according to any one of claims 1 to 7.

9. If the same redundancy version (RV) of the data block is used separately for or across both of the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configured or predefined rules or at least one indication includes mapping, by the user equipment, the UCI across both of the at least two PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the mapping of the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one indication, includes mapping, by the user equipment, the at least one UCI to each of the at least two PUSCH allocations separately, or mapping the UCI to one of the at least two PUSCH allocations. The method according to claim 8.

10. 10. The method of claim 1, wherein the mapping of the at least one UCI based on at least one of one or more configuration or predefined rules, or at least one indication, comprises mapping based on a beta offset value received by the user equipment in downlink control information.

11. a first subset of beta values ​​associated with mapping the at least one UCI to both of the at least two PUSCH allocations separately or across both of the at least two PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the at least two PUSCHs. The method of claim 10.

12. The method according to claim 1 , wherein the mapping is based on a layer number corresponding to each of the at least two PUSCH allocations.

13. The mapping of the at least one UCI based on at least one of one or more configuration or predefined rules, or at least one instruction, comprises: Mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations having a higher or lower starting data block or frequency; Mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations corresponding to a particular transmit reception point (TRP) or a particular transmit configuration indication (TCI) state; The method of any one of claims 1 to 12, comprising at least one of:

14. determining, by the user equipment, a first association between a beta offset and / or an alpha value and the at least two PUSCH allocations; and / or determining, by the user equipment, a second association between a beta offset and / or an alpha value and a different set of capability values ​​or antenna panels, a transmission / reception point (TRP), a CORESETpool index or CORESET group, a set of TCI states, or a set of reference signals; Including, and mapping the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction, includes mapping, by the user equipment, the at least one UCI based on the first association and / or the second association.

14. A method according to any one of claims 1 to 13.

15. mapping the at least one UCI based on at least one of one or more configurations or predefined rules, or at least one instruction; matching, by the user equipment, the at least one UCI to a transmission configuration indication (PUSCH) assignment having a TCI state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI; The method of any one of claims 1 to 14, comprising:

16. An apparatus comprising: At least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code are adapted to cause the device, using the at least one processor, to at least: determining, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); by said user equipment, One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, Over the at least two PUSCH allocations, Mapping the UCI in at least one of the following: The method is configured to: said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. Device.

17. The at least one processor and the computer program code cause the apparatus to: transmitting the at least one uplink control information via one or more PUSCH allocations of the at least two PUSCH allocations based on the mapping. The apparatus of claim 16 , further configured to:

18. The at least one processor and computer program code configured to cause the device to perform mapping based on at least one of one or more settings or predefined rules, or at least one instruction, comprising: 1) whether the at least one UCI is scheduled for transmission on one of the at least two PUSCHs; or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH), which may be multiplexed onto one of the at least two PUSCHs; based on at least one of 18. Apparatus according to any one of claims 16 to 17, comprising:

19. The at least one processor and the computer program code cause the apparatus to: If the UCI is scheduled for transmission on one or both PUSCHs, the mapping comprises mapping the at least one UCI by the user equipment to both PUSCH allocations separately or across both PUSCH allocations; If the at least one UCI is initially carried on the PUCCH that may be multiplexed into one of the PUSCHs, the mapping includes mapping the at least one UCI by the user equipment to one of the PUSCH allocations.

20. The apparatus of claim 18, configured to:

20. The at least one processor and the computer program code configured to cause the device to perform mapping based on at least one of one or more settings or predefined rules, or at least one instruction, further comprising: Mapping the UCI to one of the PUSCH allocations corresponding to at least one of the same capability set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH by the user equipment.

20. The apparatus of claim 19, comprising the at least one processor and the computer program code configured to:

21. The at least one processor and the computer program code configured to cause the device to map the at least one UCI to one of the PUSCH allocations based on at least one step of one or more configurations or predefined rules or at least one instruction, the at least one processor and the computer program code configured to cause the device to: Whether the same data block or codeword is mapped to both PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; mapping the at least one UCI based on The at least one processor and the computer program code are configured to execute the steps of:

21. Apparatus according to any one of claims 16 to 20.

22. The at least one processor and the computer program code cause the apparatus to: If the same codeword or data block is mapped across both PUSCH allocations, the mapping comprises mapping, by the user equipment, the at least one UCI separately to both PUSCH allocations or across both PUSCH allocations; When different codewords or data blocks are mapped across at least two PUSCH allocations, the mapping includes mapping the UCI by the user equipment to one of the PUSCH allocations that corresponds to at least one of the same capability set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH.

22. The apparatus of claim 21 configured to:

23. The at least one processor and the computer program code are configured to cause the device to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one processor and the computer program code being configured to: For the same codeword, the same redundancy version (RV) of a data block is used or indicated for both PUSCH allocations, or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; 23. The apparatus of claim 16, comprising the at least one processor and the computer program code configured to cause the apparatus to map the at least one UCI based on:

24. The at least one processor and the computer program code cause the apparatus to: If the same redundancy version (RV) of the data block is used separately for or across both PUSCH allocations, the mapping comprises mapping the UCI by the user equipment across both PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the mapping may be further determined by the user equipment as follows: Mapping the at least one UCI separately to each of the PUSCH allocations; or mapping the UCI to one of the PUSCH allocations; Including, 24. The apparatus of claim 23, configured to:

25. The at least one processor and the at least one computer program code configured to cause the device to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, comprises: the at least one processor and the at least one computer program code configured to cause the device to map based on a beta offset value received by the user equipment in downlink control information.

25. Apparatus according to any one of claims 16 to 24.

26. a first subset of beta values ​​associated with mapping the at least one UCI to both PUSCH allocations separately or across both PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the PUSCHs.

26. The apparatus of claim 25.

27. The at least one processor and the computer program code configured to cause the apparatus to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one processor and the computer program code configured to map based on a layer number corresponding to each PUSCH allocation.

27. Apparatus according to any one of claims 16 to 26.

28. The at least one processor and the computer program code are configured to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, Mapping, by the user equipment, the at least one UCI to one of the PUSCH allocations having a higher or lower starting data block or frequency; or Mapping, by the user equipment, the at least one UCI to one of the PUSCH allocations corresponding to a particular transmission reception point (TRP) or a particular transmission configuration indication (TCI) state. the at least one processor and the computer program code configured to perform at least one of the following:

28. Apparatus according to any one of claims 16 to 27.

29. The at least one processor and the computer program code cause the apparatus to: determining, by the user equipment, a first association between a beta offset and / or an alpha value and a PUSCH allocation; and determining, by the user equipment, a second association between a beta offset and / or an alpha value and a different capability value set or antenna panel, a transmission / reception point (TRP), a CORESETpool index or CORESET group, a set of TCI states, or a set of reference signals; The method is configured to: The at least one processor and the at least one computer program code configured to cause the device to map the at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, include the at least one processor and the at least one computer program code configured to cause the device to map, by the user equipment, the at least one UCI based on the first association and the second association.

29. Apparatus according to any one of claims 16 to 28.

30. The at least one processor and the computer program code are configured to cause the device to map at least one UCI based on at least one of one or more settings or predefined rules, or at least one instruction, the at least one processor and the computer program code being configured to: mapping, by the user equipment, the at least one UCI to a transmission configuration indication (PUSCH) assignment having a TCI state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI; The at least one processor and the computer program code are configured to:

30. Apparatus according to any one of claims 16 to 29.

31. transmitting, by a network node to a user equipment, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); receiving, by the network node, from the user equipment at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, wherein the at least one UCI comprises: One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, Over the at least two PUSCH allocations, is mapped to at least one of Including, at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one indication provided by the network node to the user equipment; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. method.

32. At least one UCI is mapped based on at least one of one or more settings or predefined rules or at least one instruction. 1) whether the at least one UCI is scheduled to be transmitted on one of the PUSCHs; or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH) that can be multiplexed into one of the PUSCHs; 32. The method of claim 31 , further comprising: mapping the at least one UCI based on at least one of:

33. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. The at least one UCI is mapped to one of the PUSCH allocations corresponding to at least one of the same capability value set, the same antenna panel, the same transmission / reception point (TRP), the same control resource set pool index (CORESET pool index), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set as the PUCCH allocation.

33. The method of claim 32.

34. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. Whether the same data block or codeword is mapped to both PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; The at least one UCI is mapped based on 34. A method according to any one of claims 31 to 33.

35. if the same codeword or data block is mapped across both PUSCH allocations, the at least one UCI is mapped separately to both PUSCH allocations or across both PUSCH allocations; When different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one of the PUSCH allocations that corresponds to at least one of the same capability set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH.

34. The method of claim 33.

36. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. For the same codeword, the same redundancy version (RV) of a data block is used or indicated for both PUSCH allocations, or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; 36. The method of claim 31 , further comprising mapping the at least one UCI based on:

37. If the same redundancy version (RV) of the data block is used for both PUSCH allocations separately or across both PUSCH allocations, the at least one UCI is mapped across both PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH assignments, the at least one UCI is mapped separately to each of the PUSCH assignments, or the UCI is mapped to one of the PUSCH assignments.

37. The method of claim 36.

38. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. the at least one UCI is mapped based on a beta offset value received by the user equipment in downlink control information.

38. A method according to any one of claims 31 to 37.

39. a first subset of beta values ​​associated with mapping the at least one UCI to both PUSCH allocations separately or across both PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the PUSCHs.

39. The method of claim 38.

40. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction, The at least one UCI is mapped based on a number of layers corresponding to each PUSCH allocation.

40. A method according to any one of claims 31 to 39.

41. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. the at least one UCI is mapped to one of the PUSCH allocations having a higher or lower starting data block or frequency; or The at least one UCI is mapped to one of the PUSCH allocations corresponding to a particular transmission / reception point (TRP) or a particular transmission configuration indication (TCI) state. the at least one UCI is mapped based on at least one of the following:

40. A method according to any one of claims 31 to 39.

42. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. the at least one UCI is mapped to a PUSCH assignment having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

42. A method according to any one of claims 31 to 41.

43. An apparatus comprising: At least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to: transmitting, by a network node, to a user equipment, downlink control information including information indicating at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, wherein the at least one UCI comprises: One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, or Over the at least two PUSCH allocations, is mapped to at least one of The method is configured to at least: The at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one indication provided from the network node to the user equipment; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. Device.

44. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. 1) whether the at least one UCI is scheduled to be transmitted on one of the PUSCHs; or 2) whether the UCI is carried primarily on a physical uplink control channel (PUCCH), which may be multiplexed into one of the PUSCHs; the at least one UCI is mapped based on at least one of 44. The apparatus of claim 43.

45. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. The at least one UCI is mapped to one of the PUSCH allocations corresponding to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH.

45. The apparatus of claim 44.

46. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. Whether the same data block or codeword is mapped to both PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations; The at least one UCI is mapped based on 46. ​​Apparatus according to any one of claims 43 to 45.

47. if the same codeword or data block is mapped across both PUSCH allocations, the at least one UCI is mapped separately to both PUSCH allocations or across both PUSCH allocations; When different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one of the PUSCH allocations that corresponds to at least one of the same capability value set, same antenna panel, same transmission / reception point (TRP), same control resource set pool index (CORESET pool index), same CORESET group, same transmission configuration indication (TCI) state set, or same reference signal set as the PUCCH.

46. ​​The apparatus of claim 45.

48. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. For the same codeword, the same redundancy version (RV) of a data block is used or indicated for both PUSCH allocations, or whether different redundancy versions (RVs) of the data block are used or indicated for the at least two PUSCH assignments; The at least one UCI is mapped based on 48. Apparatus according to any one of claims 43 to 47.

49. If the same redundancy version (RV) of the data block is used for both PUSCH allocations separately or across both PUSCH allocations, the at least one UCI is mapped across both PUSCH allocations; If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the at least one UCI is mapped to each of the PUSCH allocations separately or to one of the PUSCH allocations.

49. The apparatus of claim 48.

50. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. the at least one UCI is mapped based on a beta offset value received by the user equipment in downlink control information.

50. Apparatus according to any one of claims 43 to 49.

51. a first subset of beta values ​​associated with mapping the at least one UCI to both PUSCH allocations separately or across both PUSCH allocations; a second subset of beta values ​​associated with mapping the at least one UCI to one of the PUSCHs.

51. The apparatus of claim 50.

52. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. The at least one UCI is mapped based on a number of layers corresponding to each PUSCH allocation.

52. Apparatus according to any one of claims 43 to 51.

53. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. the at least one UCI is mapped to one of the PUSCH allocations having a higher or lower starting data block or frequency; or the at least one UCI is mapped to one of the PUSCH allocations corresponding to a particular transmission / reception point (TRP) or a particular transmission configuration indication (TCI) state; the at least one UCI is mapped based on at least one of 52. Apparatus according to any one of claims 43 to 51.

54. The at least one UCI is mapped based on at least one of one or more settings or predefined rules, or at least one instruction. the at least one UCI is mapped to a PUSCH assignment having a transmission configuration indication (TCI) state matching a TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

54. Apparatus according to any one of claims 43 to 53.

55. When executed by at least one processor, the computing system includes: transmitting, by a network node, to a user equipment, downlink control information including information indicating at least two time domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by the user equipment to transmit at least one uplink control information (UCI); receiving, by the network node, from the user equipment at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, wherein the at least one UCI comprises: One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, or Over the at least two PUSCH allocations, receiving a signal having a plurality of sigma-based address spaces, the signal having a plurality of sigma-based address spaces being mapped to at least one of the sigma-based address spaces; A non-transitory computer-readable storage medium having stored thereon instructions configured to cause a computer to execute The at least one UCI is mapped based on at least one of one or more configurations or predefined rules, or at least one indication provided from the network node to the user equipment; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. A non-transitory computer-readable storage medium.

56. means for transmitting, by a network node, to a user equipment, downlink control information including information indicating at least two time domain overlapped physical uplink shared channel (PUSCH) allocations that may be used by said user equipment to transmit at least one uplink control information (UCI); A means for receiving, by the network node, from the user equipment, at least two PUSCH transmissions corresponding to the at least two time domain PUSCH allocations, the at least one UCI comprising: One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, Over the at least two PUSCH allocations, a receiving means for receiving the signal, the receiving means being mapped to at least one of the following: Including, the at least one UCI is mapped based on at least one of one or more configuration or predefined rules, or at least one indication provided by the network node to the user equipment; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. Device.

57. When executed by at least one processor, the computing system includes: determining, by a user equipment in a wireless network, at least two time-domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); The UCI is transmitted by the user equipment. One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, or Over the at least two PUSCH allocations, Mapping with at least one of A non-transitory computer-readable storage medium having stored thereon instructions configured to cause a said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. A non-transitory computer-readable storage medium.

58. Means for determining, by a user equipment in a wireless network, at least two time domain overlapped physical uplink shared channel (PUSCH) allocations corresponding to at least two PUSCH transmissions for use in transmitting at least one uplink control information (UCI); The UCI is transmitted by the user equipment. One of the at least two PUSCH allocations, Separately for each of the at least two PUSCH allocations, Over the at least two PUSCH allocations, and a means for mapping the An apparatus comprising: said mapping being based on at least one of one or more configurations or predefined rules, or at least one indication received by said user equipment from a network node; The PUSCH assignment includes resources assigned to the user equipment for PUSCH transmission. Device.

Images