Enhanced uplink control information mapping to uplink channel allocation

Abstract

A method includes determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations, the at least two PUSCH allocations overlapping in a time domain and 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 at least one UCI to at least one of: one of the at least two PUSCH allocations; respectively mapping to each PUSCH allocation in the at least two PUSCH allocations; or allocating across at least two PUSCHs; wherein the mapping is based on at least one of one or more configured or predefined rules, or at least one indication received by the user equipment from the network node, and wherein each of the at least two PUSCH allocations comprises resources allocated to the user equipment for PUSCH transmission.

Description

Technical Field

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

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

[0003] An example of a cellular communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). The latest development in this field is generally referred to as the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. UETRA (Evolved UMTS Terrestrial Radio Access) is the air interface of the 3GPP Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, a base station or access point (AP) called an enhanced Node B (eNB) provides wireless access within a coverage area or cell. In LTE, a mobile device or mobile station is referred to as a user equipment (UE). LTE includes many improvements or developments. Various aspects of LTE are also constantly improving.

[0004] The 5G New Radio (NR) development is part of the ongoing mobile broadband evolution process, similar to the earlier evolution of 3G and 4G wireless networks. In addition, 5G targets emerging use cases beyond mobile broadband. One goal of 5G is to significantly improve wireless performance, which can include new levels of data rates, latency, reliability, and security. 5G NR can also be extended to efficiently connect large-scale Internet of Things (IoT) and can provide new types of mission-critical services. For example, ultra-reliable low-latency communication (URLLC) equipment may require high reliability and very low latency. Summary of the invention

[0005] According to an example embodiment, a method may include: determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations, the at least two PUSCH allocations overlapping in the time domain and corresponding to at least two PUSCH transmissions for use in sending at least one uplink control information (UCI); and mapping, by the user equipment, at least one UCI to at least one of: one of the at least two PUSCH allocations; respectively to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein the mapping is 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, and wherein each of the at least two PUSCH allocations includes resources allocated to the user equipment for PUSCH transmission.

[0006] According to another example embodiment, a method may include sending downlink control information by a network node to a user equipment, the downlink control information including information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send 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 at least one UCI has been mapped to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein at least one UCI has been mapped based on at least one of the following: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0007] Additional example embodiments corresponding to each method are provided, including at least the following for each method: an apparatus including components for performing each method; an apparatus including at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least perform the method; and a non-transitory computer-readable storage medium includes instructions stored thereon, which, when executed by the at least one processor, are configured 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 are configured to, together with the at least one processor, enable the apparatus to at least: determine, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use when sending at least one uplink control information (UCI); and map, by the user equipment, the UCI to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein the mapping is based on at least one of the following: one or more configured or predefined rules, or at least one indication received by the user equipment from a network node, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0009] According to an example embodiment, an apparatus includes: a non-transitory computer-readable storage medium having instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to: determine, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use when sending at least one uplink control information (UCI); and map, by the user equipment, the UCI to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein the mapping is based on at least one of the following: one or more configured or predefined rules, or at least one indication received by the user equipment from a network node, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0010] According to an example embodiment, an apparatus includes: a component for determining, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use when sending at least one uplink control information (UCI); and a component for mapping the UCI by the user equipment to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein the mapping is based on at least one of the following: one or more configured or predefined rules, or at least one indication received by the user equipment from a network node, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[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 are configured to, together with the at least one processor, enable the apparatus to at least: send downlink control information by a network node to a user equipment, the downlink control information including information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send at least one uplink control information (UCI); receive at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations from the user equipment by the network node, wherein at least one UCI has been mapped to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein at least one UCI has been mapped based on at least one of the following: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0012] According to an example embodiment, an apparatus includes: a non-transitory computer-readable storage medium including instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to: send downlink control information by a network node to a user equipment, the downlink control information including information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send at least one uplink control information (UCI); receive at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations from the user equipment by the network node, wherein at least one UCI has been mapped to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein at least one UCI has been mapped based on at least one or more configured or predefined rules, or at least one of at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0013] According to an example embodiment, an apparatus includes: a component for sending downlink control information by a network node to a user equipment, the downlink control information including information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send at least one uplink control information (UCI); a component for receiving, by the network node, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations from the user equipment, wherein at least one UCI has been mapped to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations; wherein at least one UCI has been mapped based on at least one of the following: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0014] The details of one or more examples of 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 is a block diagram of a wireless network according to an example embodiment.

[0016] Figure 2 is a diagram illustrating multi-TRP communication according to an example embodiment.

[0017] Figure 3 is a flow chart illustrating the operation of a user equipment or UE according to an example embodiment.

[0018] Figure 4 is a flow chart illustrating the operation of a network node (e.g., a transmission reception point (TRP), gNB, or other network node) according to an example embodiment.

[0019] Figure 5 is a diagram illustrating mapping of UCI (eg, CSI) to two PUSCH allocations corresponding to two simultaneous PUSCH transmissions based on an indicated β offset.

[0020] Figure 6 is a diagram illustrating mapping of UCI into PUSCH based on scheduling of simultaneous PUSCH operation according to another example embodiment.

[0021] Figure 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) according to an example embodiment. DETAILED DESCRIPTION

[0022] Figure 1 is a block diagram of a wireless network 130 according to an example embodiment. Figure 1 In a wireless network 130 of FIG. 1 , user equipment 131 , 132 , 133 , and 135 (also referred to as mobile stations (MS) or user devices (UE)) may be connected to (and communicate with) a base station (BS) 134 , which may also be referred to as an access point (AP), an enhanced Node B (eNB), or a next generation Node B (gNB). The terms user equipment and user device (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 a portion of the functionality of a 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 operably coupled to a remote transceiver, such as a remote radio head (RRH). BS 134 provides wireless coverage within a cell 136 , which includes user equipment 131 , 132 , 133 , and 135 . Although only four user equipments are shown as being connected or attached to BS 134, any number of user equipments may be provided. BS 134 is also connected to core network 150 via S1 interface 151. This is just one simple example of a wireless network, and other wireless networks may be used.

[0023] According to an illustrative example, a BS (e.g., an AP, an eNB, a gNB, a RAN node) may be part of a mobile telecommunications system. A RAN may include one or more RAN nodes (e.g., an AP, a BS, an eNB, a gNB) that implement a radio access technology, for example, to allow one or more UEs to access a network or a core network. Thus, a RAN node resides between one or more user devices or UEs and a core network. According to an example embodiment, each RAN node may provide one or more wireless communication services for one or more UEs or user devices, for example, to allow the UE to access a network wirelessly via a RAN node. Each RAN node may perform or provide wireless communication services, for example, such as to allow a UE or user device to establish a wireless connection to a RAN node, and to send data to one or more UEs and / or receive data from one or more UEs. For example, after establishing a connection to a UE, a RAN node may forward data received from a network or a core network to the UE, and / or forward data received from the UE to the network or a core network. The RAN nodes may perform a variety of other radio functions or services, such as, for example, broadcasting control information (e.g., such as system information) to UEs, paging UEs when there is data to be delivered to the UEs, assisting UEs in switching between cells, scheduling resources for uplink data transmission from (multiple) UEs and downlink data transmission to (multiple) UEs, issuing control information for configuring one or more UEs, etc. These are just a few examples of one or more functions that a RAN node may perform.

[0024] User equipment (UE), mobile terminal, handheld wireless device, etc.) may refer to a portable computing device, including a wireless mobile communication device operating with or without a subscriber identity module (SIM), such as, but not limited to, the following types of devices: mobile station (MS), mobile phone, cell phone, smart phone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, tablet phone, game console, notebook computer, vehicle, sensor, wearable device, or any other wireless device. It should be understood that a user device may also be (or may include) an almost exclusively uplink-only device, an example of which is a camera or video camera that loads images or video clips to a network.

[0025] The core network 150 may include: a mobility management entity (MME) or an access and mobility management function (AMF) that can control access to the network and process or assist movement / switching of user equipment between BSs, one or more gateways that can forward data between the BS and a packet data network or the Internet, and other control nodes, functions, or blocks.

[0026] In addition, as illustrative examples, various example embodiments or techniques described herein may be applied to various types of user equipment or data service types, or may be applied to user equipment on which multiple applications may be running, which may be different data service types. New radio (5G) developments may support many different applications or many different data service types, such as: machine type communication (MTC), enhanced machine type communication (eMTC), Internet of Things (IoT) and / or narrowband IoT user equipment, enhanced mobile broadband (eMBB), and ultra-reliable low latency communication (URLLC). Many of these new 5G (NR) related applications may require higher performance than previous wireless networks.

[0027] IoT can refer to the growing group of objects that can have Internet or network connectivity so that they can send and receive information to and from other network devices. For example, many sensor-type applications or devices can monitor physical conditions or states and can report to servers or other network devices, for example, when events occur. For example, machine-type communications (MTC or machine-to-machine communications) can be characterized by fully automatic data generation, exchange, processing, and actuation between intelligent machines, with or without human intervention. Enhanced mobile broadband (eMBB) can support higher data rates than current LTE.

[0028] Ultra-Reliable Low-Latency Communication (URLLC) is a new type of data service or new usage scenario that the new radio (5G) system can support. This enables emerging new applications and services such as industrial automation, autonomous driving, vehicle safety, e-health services, etc. As an illustrative example, 3GPP aims to provide a 5G-capable ... -5 Connectivity with reliability corresponding to a block error rate (BLER) of 100% and a U-plane (user / data plane) latency of up to 1 ms. Thus, for example, a URLLC user equipment / UE may require a significantly lower block error rate and low latency than other types of user equipment / UE (with or without simultaneous high reliability requirements). Thus, for example, a URLLC UE (or a URLLC application on a UE) may require shorter latency than an eMBB UE (or an eMBB application running on a UE).

[0029] Various example embodiments may be applied to a variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G / New Radio (NR), or any other wireless network or wireless technology operating on cmWave and / or mmWave frequency bands, and may be applied to a variety of communication services, such as IoT, MTC, eMTC, eMBB, URLLC, etc. These exemplary networks, technologies, or data service types are provided as illustrative examples only.

[0030] The UE may be configured by the gNB (or other network node) to perform different measurements and report measurements to the network (or gNB(s). Configuration of the UE to perform reference signal (or beam) measurements (e.g., such as CSI-RS measurements of different beams) and reporting may be performed by the gNB issuing a reporting configuration (e.g., such as CSI-Report-Config) to the UE. For example, the reporting configuration may indicate the downlink resource(s) on which the measurements should be performed (e.g., CSI-RS reference signal / SSB or beam), the specific quantities or parameters to be measured, and how the reporting is to be performed, such as when the reporting is complete.

[0031] The UE may measure (multiple) signal parameters (e.g., such as reference signal received power (RSRP)) of each of a plurality of downlink reference signals (e.g., such as synchronization signal block / SSB signals or channel state information (CSI) reference signals (CSI-RS)) received by the UE from a gNB / network node (or BS), where each reference signal may be sent by the gNB via a different gNB transmit beam (or via a different downlink DL reference signal). The UE may determine the strongest beam or reference signal (e.g., having the highest RSRP), and may then issue a measurement report to the gNB, which may, for example, identify the strongest N DL reference signals (or beams) and the RSRP (or other measured signal parameters) of the N beams. The gNB may use the measurement report to determine what beam to use to communicate with the UE.

[0032] According to an example embodiment, the PDCCH (physical downlink control channel) may be sent 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 example embodiment, a CCE is a building block of a PDCCH, where a CCE may be a minimum resource set that may be used for a PDCCH. For example, a CCE may be a unit based on which a search space for blind decoding may be defined. Thus, depending on the aggregation level, each PDCCH may include one or more CCEs. According to an example embodiment, a CCE may include 6 resource element groups (REGs), each of which may include a resource block in an OFDM symbol.

[0033] The search space may include a set of candidate PDCCHs (candidate downlink control channels) formed by (multiple) CCEs of a given aggregation level, which the UE should attempt to decode. The UE may have multiple search spaces for different purposes (such as different common search spaces and user-specific search spaces). The search space may include one or more control resource sets (CORESETs). A CORESET may be (or may include) a time-frequency resource on which (multiple) PDCCHs are sent. There may be multiple search spaces using the same control resource set (CORESET), and there may be multiple CORESETs configured for the UE. In addition, a control resource set (CORESET) may be (or may include) a time-frequency resource in which the UE attempts to decode a candidate PDCCH using one or more search spaces.

[0034] In addition, a transmission configuration indication (TCI) state can be used by a network node (gNB or BS) within a control resource set (or CORESET) to provide a beam indication to the UE, which can identify the beam that the UE should use for uplink communication and / or downlink communication with the network node or gNB. Each TCI state can be configured with or associated with a transmit beam / receive beam pair. Thus, each TCI state can be associated with a specific beam or a specific reference signal. For example, TCI state 1 can be associated with CSI-RS#5 (or can be used to indicate CSI-RS#5), and TCI state 2 can be associated with CSI-RS#9, and so on (where CSI-RS#5 and CSI-RS#9 can be DL reference signals sent by the gNB). Thus, in this way, each TCI state can be associated with a specific reference signal and / or a specific beam (or the TCI state can indicate a specific reference signal and / or a specific beam). For example, for data transmission via a physical downlink shared channel (PDSCH) and / or via a physical uplink shared channel (PUSCH), the UE may be configured by the gNB via a radio resource control (RRC) message with 128 candidate TCI states. The gNB may then configure the UE with up to, for example, 8 (or other number) activated TCI states via a MAC (media access control) control element (MAC CE), which may be carried with (or attached to) DL (downlink) data transmission to the UE via the PDSCH (physical downlink shared channel). Thus, in this manner, the gNB may issue an activation message to activate (within the UE) 8 (e.g.) indicated TCI states out of the 128 (e.g.) candidate TCI states. The network node may request the UE to use beams associated with any of these 8 (or other number) activated TCI states for communication with the network node or gNB (e.g., for sending or receiving data).

[0035] Dynamically (e.g., such as provided in downlink control information / DCI in each subframe or timeslot), the gNB can indicate the selection of one activated TCI state (and thus identify the selected beam) for the UE to use for uplink or downlink data communication (e.g., for scheduled uplink (UL) or downlink (DL) communication via PDSCH and / or PUSCH). The DCI (which, at least in some cases, can identify the selected activated TCI state for the UE to use for communication) can be provided within a PDCCH (Physical Downlink Control Channel) sent to the UE, for example, as part of each timeslot or subframe. In this way, in some cases, the DCI can be used to provide a fast beam indication that indicates a selected TCI state (e.g., a selected TCI state among multiple activated TCI states) associated with a reference signal or beam to be used by the UE for UL or DL ​​data communication with a network node (BS or gNB). The UE may also receive control information (eg, via a radio resource control (RRC) message) indicating the selected TCI state (and therefore beam) to be used by the UE to receive the PDCCH for each CORESET. Thus, each CORESET may be configured with a TCI state.

[0036] Release 16 of NR provides support for single-cell downlink multiple transmission reception points (multi-TRP) (or multiple transmission points), which provides the possibility to send downlink data simultaneously via PDSCH (Physical Downlink Shared Channel) from two different transmission reception points (TRPs), which can be geographically separated but provided within the same cell (for example, transmission of downlink data from two different radio heads or other nodes to UEs within the cell).

[0037] In addition, Rel-17 introduces a unified TCI framework, which means that the TCI state that provides QCL assumptions for the reception of DL signals and channels will also be used to provide spatial sources for the transmission of UL signals and channels. In addition, the unified TCI framework defines the concept of indicated TCI states. The indicated TCI states can be a joint DL TCI state and a UL TCI state, or a separate DL TCI state and a separate UL TCI state. The indicated TCI states provide QCL sources (DL) and spatial sources (UL) for downlink signals and channel sets and for uplink signals and channel sets, respectively. In Rel-17, for a UE, there can be an indicated joint DL TCI state and UL TCI state, or an indicated DL TCI state and an indicated UL TCI state.

[0038] For example, the unified TCI framework may include the following high-level functions: a common TCI state (e.g., the indicated TCI) for a set of signals and channels at one time; the TCI state may be a joint DL / UL TCI state, a separate DL TCI state, and / or a separate UL TCI state; RRC configures a set (or pool) of joint and / or separate TCI states; MAC (media access control entity) activates a certain number (e.g., 8) of joint and / or separate TCI states; before the first indication, the first activated TCI state is the currently indicated TCI state; DCI (downlink control information, e.g., provided by the gNB to the UE via the physical downlink control channel (PDCCH)) indicates one of the activated TCI states as the indicated TCI state (which may be a common TCI state); TCI state indication based on DCI: DCI formats 1_1 / 1_2 with and without DL allocation may be used to carry TCI state indication; ACK (HARQ confirmation feedback, used to confirm the data received by the UE); Application time of beam indication: the first time slot of at least X ms or Y symbols after the last symbol of the confirmation of the joint or individual DL / UL beam indication; TCI field code point: Joint: TCI state of both DL and UL; Individual: Pair of DL TCI state and UL TCI state; DL TCI state (maintain the current UL TCI state); UL TCI state (maintain the current DL TCI state); The unified TCI framework will be extended in Rel-18 so that there can be multiple indicated DL TCI states and UL TCI states;

[0039] In addition, the UE may send 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 the following: 1) Hybrid ARQ Acknowledgement (HARQ-ACK) feedback for received downlink data (used 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) Scheduling Requests, which indicate that the UE requires or is requesting uplink resources for uplink transmissions to the gNB (e.g., requesting a PUSCH allocation).

[0040] In addition, the UE may send data to the gNB or network node via the physical uplink shared channel (PUSCH). The UE sending uplink data to the gNB may require a valid scheduling grant or PUSCH allocation (which provides the UE with an allocation of time-frequency resources that can be used by the UE for UL transmission).

[0041] The PUCCH may be the basis for transmitting uplink control information (UCI) to the gNB. For example, in some cases, the UE may send UCI to the gNB via the PUCCH regardless of whether the UE has received a PUSCH allocation for transmission of UL data. However, in some cases, if the PUCCH and PUSCH overlap in time (such as for the case where the UE has received a valid grant or PUSCH allocation), the UE may send UCI on or within the PUSCH (e.g., by piggybacking the UCI on the PUSCH), which may include the UE multiplexing the UCI with the UL data onto the PUSCH to allow both the data and the UCI to be sent via the PUSCH. Thus, by multiplexing the UCI with the data on the PUSCH (or piggybacking the UCI and the data together via the PUSCH), this may provide more efficient transmission of data and UCI.

[0042] In some cases, explicit configuration / scheduling of CSI on PUSCH is only applicable to semi-persistent and non-periodic CSI reporting. When PUSCH overlaps with PUCCH carrying UCI in the time domain, according to the rule set, the UE shall multiplex the UCI content onto PUSCH. This is called UCI piggybacking on PUSCH. Both CP-OFDM and DFT-S-OFDM waveforms support UCI piggybacking on PUSCH. The piggybacked UCI is mapped after the first DMRS (demodulation reference signal) of PUSCH (frequency division multiplexing of DMRS is not allowed). UCI piggybacking is the only method for carrying HARQ-ACK feedback on PUSCH. Piggybacking / multiplexing UCI on PUSCH is subject to the multiplexing timeline conditions defined in TS 38.213. In the case of UCI piggybacking / scheduling on PUSCH, almost all UCI content is rate matched in PUSCH according to specific rules depending on the UCI type. The only exception is HARQ-ACK feedback with up to 2 bits, which is sent by puncturing on PUSCH.

[0043] In addition, the beta offset and / or alpha value may be configured / indicated by the gNB or network node (e.g., the configured value may be sent to the UE to obtain the beta offset or alpha value). 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 how much PUSCH the UCI may 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 the HARQ-ACK, CSI part 1, or CSI part 2 (one or both of which may be considered as UCI). For example, the beta offset may be configured separately for HARQ-ACK feedback for different sizes, such as for: up to 2 bits (2-bit UCI with a first beta offset), >2 bits and 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 may be semi-statically configured / indicated via RRC (Radio Resource Control messages) or via dynamic selection of configuration using DCI. The β offsets may be configured separately for CSI and HARQ-ACK.

[0044] The α value may be configured via a higher layer parameter "scaling", which is introduced to ensure that UCI does not consume all PUSCH resources (e.g., to ensure that at least a portion of the PUSCH is available for data transmission). α or the α value may indicate the maximum amount of resources that may be consumed or used by UCI within the PUSCH. α may be indicated for UCI.

[0045] In addition, as used in this document, the term beam or (UL) beam may also refer to spatial relationship information, (individual) UL TCI state, joint or common TCI state, spatial filter, power control information (or power control parameter set), SRS (sounding reference signal) resource indicator (pointing to one or more SRS resources) panel or panel ID (for example, antenna panel identifier), quasi-collocated (QCL) information type D (or any other type), etc.

[0046] Note 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, such as at least one downlink reference signal, such as an SSB (synchronization signal block (SSB) reference signal and / or a channel state information reference signal (CSI-RS)) or simply by a UL beam.

[0047] Release 18 may allow simultaneous PUSCH transmissions (e.g., transmission of two time-domain overlapping PUSCH transmissions), which may be sent to the same or different Transmission Reception Points (TRPs), e.g., to the same or different gNBs, and in the same (serving) cell. However, as previously described, if the PUCCH and PUSCH(s) overlap in time, the UE may send UCI on or within the PUSCH(s) (e.g., by piggybacking the UCI on the PUSCH), which may include the UE multiplexing the UCI with UL data onto the PUSCH. Thus, in the case where the PUSCH(s) overlap in time with the PUCCH carrying the UCI, the UE may (and may be expected to) multiplex the UCI content or bits onto the PUSCH(s). However, for two time-domain overlapping PUSCHs, there are currently no established rules as to how the UE should map and / or send the UCI content on one or both of the time-domain overlapping PUSCHs.

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

[0049] like Figure 2As shown, UE 210 may map (225) UCI ​​(uplink control information) 220 (e.g., map bits or content of uplink control information (UCI 220)) to one or more of the PUSCH allocations (include UCI 220 in PUSCH allocation #1 and / or PUSCH allocation #2). For example, mapping (225) UCI ​​220 to one or two (or one or more) PUSCH allocations may include allocating one or more of the UCI portions or bits to one or two (or one or more) of the PUSCH allocations for transmission (e.g., for transmission via (multiple) PUSCH transmissions corresponding to (multiple) PUSCH allocations). 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 200 (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 of data (if any) and / or UCI (e.g., multiplexed data and UCI bits) by UE 210 via PUSCH allocation #1, and PUSCH transmission #2 may include transmission of data (if any) and / or UCI (e.g., multiplexed data and UCI bits) by UE 210. For example, mapping UCI 220 to the PUSCH allocation may include mapping corresponding coded UCI bits into the PUSCH allocation and / or multiplexing these coded UCI bits into the PUSCH allocation together with data bits (if any).

[0050] The illustrative examples described herein are described with two PUSCH allocations corresponding to two PUSCH transmissions. However, the techniques described herein can be applied to at least two (possibly including more than two) PUSCH allocations and corresponding transmissions, such as, for example, three, four or more PUSCH allocations and corresponding PUSCH transmissions.

[0051] According to an example embodiment, UE 210 may map (225, Figure 2 ) to or according to at least one of the following:

[0052] Mapped to one of at least two PUSCH allocations;

[0053] respectively mapped to each of at least two PUSCH allocations; or

[0054] Mapping across at least two PUSCH allocations;

[0055] Wherein the mapping is (or may be) based on at least one of the following: one or more configured or predefined rules, (e.g., known and applied by the UE) or at least one indication (e.g., control information, or a message providing a signal or other indication) received by the UE 210 from the TRP or a network node (e.g., a gNB). As described above, the PUSCH allocation may include resources (e.g., time-frequency resources and / or spatial resources, such as (multiple) beams) allocated to the UE 210 for the corresponding PUSCH transmission. An example of mapping based on one or more configured or predefined rules, or at least one indication is described below.

[0056] Mapping the UCI to one of at least two PUSCH allocations may include a case where the UCI is mapped to one (eg, only one, but not both) of the PUSCH allocations.

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

[0058] Mapping the UCI to (or to or onto) each of the at least two PUSCH allocations, respectively, may correspond to (or may include) a case where different codewords are mapped to the PUSCH allocations, or a case where the same codeword is mapped to two PUSCH allocations. For example, a different RV is used / indicated for each PUSCH allocation. In this case, a portion of the UCI may be encoded separately, and the coded bits of one UCI portion may be mapped to one PUSCH allocation, and the coded bits of another UCI portion may be mapped to another PUSCH allocation; alternatively, the coded bits of the same UCI may be mapped to each PUSCH allocation.

[0059] In some embodiments, "mapping UCI across PUSCH allocations" and "mapping UCI into two PUSCH allocations, respectively (or onto two PUSCH allocations)" may correspond to or include the same thing and / or may correspond to one of the above possibilities.

[0060] Figure 3 2 is a flow chart illustrating the operation of a user equipment or UE according to an example embodiment. Operation 310 includes determining, by a user equipment (eg, UE 210) in a wireless network, at least two PUSCH allocations (eg, Figure 2 The at least two time-domain overlapping PUSCH allocation pairs are used to transmit at least one uplink control information ( Figure 2 at least two physical uplink shared channels (PUSCH) used for transmission (e.g., respectively with UCI 220 in Figure 2 Operation 320 includes transmitting, by a user equipment (eg, UE 210), UCI (eg, Figure 2 The UCI 220 in the network node performs at least one of the following: mapping to one of at least two PUSCH allocations; mapping to each PUSCH allocation of at least two PUSCH allocations respectively; or mapping across at least two PUSCH allocations; wherein the mapping is based on at least one of the following: based on one or more configured or predefined rules, or at least one indication received by the user equipment from the network node, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0061] In an example embodiment, Figure 3 The method may further include sending, based on the mapping, via one or two (or one or more) PUSCH allocations of the (at least two) PUSCH allocations (e.g., see Figure 2 at least one uplink control information (e.g., Figure 2 of UCI 220).

[0062] 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 at least two PUSCHs, or 2) whether the UCI is initially transmitted on a physical uplink control channel (PUCCH) that can be multiplexed to one of at least two PUSCHs.

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

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

[0065] In an example embodiment, 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.

[0066] In an example embodiment, if the same codeword or data block is mapped across at least two PUSCH allocations, the mapping may include mapping, by a user equipment or UE, at least one UCI to at least two PUSCH allocations, respectively, or mapping across two PUSCH allocations; and if different codewords or data blocks are mapped across at least two PUSCH allocations, the mapping may include mapping, by the user equipment, the UCI to one PUSCH allocation of at least two PUSCH allocations, the one PUSCH allocation corresponding to at least one of the following: the same capability value set as PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set, or the same corresponding PCI (physical cell ID).

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

[0068] 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, respectively, or is used 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 (RV) of the data block are used for the at least two PUSCH allocations, the mapping includes: mapping at least one UCI to each of the at least two PUSCH allocations, respectively, or mapping the UCI to one of the at least two PUSCH allocations, by the user equipment.

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

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

[0071] In an example embodiment, the mapping may be based on the number of layers corresponding to each PUSCH allocation.

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

[0073] In an example embodiment, the method may include determining, by a user equipment or UE: a first association between a β offset and / or an α value and a PUSCH allocation; and determining, by the user equipment or UE: a second association between the β offset and / or the α value and different capability value sets or antenna panels, transmission reception points (TRPs), CORESETpool indexes or CORESET groups, TCI state sets, reference signal sets or (multiple) PCIs; and wherein the mapping may include: mapping, by the user equipment, at least one UCI based on the first association and the second association.

[0074] In an example embodiment, mapping may include mapping, by a user equipment or UE, at least one UCI into 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.

[0075] Figure 4 is a flow chart illustrating the operation of a network node (e.g., a transmission reception point (TRP) or a gNB or other network node) according to an example embodiment. Operation 410 includes sending, by the network node, downlink control information to a user equipment, the downlink control information including information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being usable by the user equipment to send at least one uplink control information (UCI). Operation 420 includes receiving, by the network node, at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations from the user equipment, wherein at least one UCI has been mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across at least two PUSCH allocations. Operation 430 indicates that at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocations include resources allocated to the user equipment for the PUSCH transmissions.

[0076] In an example embodiment, at least one UCI has been mapped based on at least one of: 1) whether the at least one UCI is scheduled for transmission on one of at least two PUSCHs, or 2) whether the UCI was originally transmitted on a physical uplink control channel (PUCCH) that can be multiplexed to one of the at least two PUSCHs.

[0077] In an example embodiment, at least one UCI has been mapped to one PUSCH allocation of at least two PUSCH allocations, which corresponds to at least one of the following: the same capability value set as PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

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

[0079] In an example embodiment, if the same codeword or data block is mapped across at least two PUSCH allocations, at least one UCI is mapped to at least two PUSCH allocations, respectively, or is mapped across at least two PUSCH allocations; and if different codewords or data blocks are mapped across at least two PUSCH allocations, at least one UCI is mapped to one PUSCH allocation of the at least two PUSCH allocations, which one PUSCH allocation corresponds to at least one of the following: the same capability value set as PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, the same reference signal set, or the same PCI.

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

[0081] 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 is used across the at least two PUSCH allocations, at least one UCI is mapped across the at least two PUSCH allocations; and if different redundancy versions (RV) of the data block are used for the at least two PUSCH allocations, at least one UCI is mapped to each of the at least two PUSCH allocations, or the UCI is mapped to one of the at least two allocations.

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

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

[0084] In an example embodiment, at least one UCI is mapped based on the number of layers corresponding to each PUSCH allocation.

[0085] In an example embodiment, at least one UCI is mapped based on at least one of the following: at least one UCI is mapped to one of at least two PUSCH allocations, the one PUSCH allocation 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, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

[0086] In an example embodiment, at least one UCI is mapped into 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.

[0087] For at least two time-domain overlapping PUSCH allocations (or opportunities), DCI dynamic scheduling of PUSCH allocations may be used, or the PUSCH allocations may be configured with grants (rather than dynamic scheduling) corresponding to at least two PUSCH transmissions for sending at least one UCI.

[0088] In an example embodiment, UCI may be mapped to one of at least two PUSCH allocations, or mapped to two PUSCH allocations (or each of at least two PUSCH allocations) respectively (e.g., UCI will be encoded and then the encoded UCI code bits may be sent via one or both of the PUSCH allocations, for example, based on rate matching, the mapping of UCI may be based on the mapping of the encoded UCI bits). For example, mapping to the two PUSCH allocations respectively (or mapping to each of at least two PUSCH allocations respectively) may mean or may include: some UCI bits are sent / sent via PUSCH allocation #1 and sent via PUSCH transmission #1, and some other UCI bits (e.g., different UCI bits) may be sent / sent via PUSCH allocation #2 and sent via PUSCH transmission #2.

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

[0090] In an example embodiment, the mapping for UCI (from at least one UCI) may depend on whether the UCI is scheduled on PUSCH (such as A-CSI (aperiodic CSI) or SP (semi-persistent)-CSI, both of which can be scheduled directly on PUSCH to send channel state information via PUSCH) (semi-persistent can also be on PUCCH and can be triggered separately), or whether the UCI is originally carried on PUCCH, which can be multiplexed into PUSCH, where: If UCI is scheduled on PUSCH (PUSCH is directly scheduled to carry UCI / CSI), the UE may map the UCI ( It may be or may include CSI) mapped to two PUSCH allocations respectively or across two PUSCH allocations; if the UCI is originally carried on the PUCCH which can be multiplexed into the PUSCH, the UE may map the UCI to one PUSCH allocation; one PUSCH allocation may be a PUSCH allocation corresponding to the following: the same set of capability values ​​(or panels) as the PUCCH, or the same TRP, or the same CORESETpool index, or the same CORESET group, or the same TCI state set, or the same RS set (such as SSB, CSI-RS, SRS), or the same PCI. In both cases (UCI comes from one of the possibilities), the UE will need to determine whether to map the UCI to one PUSCH or to two PUSCHs.

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

[0092] In an example embodiment, mapping for UCI (from at least one UCI) may depend on whether, for the same codeword, the same redundancy version (RV) is used / indicated for two PUSCH allocations, or whether different RVs are used / indicated for each of the at least two PUSCH allocations, wherein: if the same redundancy version (RV) is used for both PUSCH allocations or is used across the two PUSCH allocations, the UE may map the UCI across the at least two PUSCH allocations; or, if different RVs are used for the at least two PUSCH allocations, the UE may map the UCI into each PUSCH allocation separately. Alternatively, the UE may map the UCI into one PUSCH allocation.

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

[0094] In an example embodiment, the mapping for UCI may depend on the number of layers corresponding to each PUSCH allocation / transmission, wherein: if the number of layers is the same for at least two PUSCH allocations / transmissions, the UE may map the UCI to the two PUSCH allocations respectively, or across two (or at least two) PUSCH allocations; or, if the number of layers corresponding to one of the at least two PUSCH allocations / transmissions is greater than or equal to a certain threshold, the UE may map the UCI to the PUSCH allocation. For example, if the number of layers corresponding to one of the at least two PUSCH allocations / transmissions is below a certain threshold, the UE may not map the UCI to the PUSCH allocation.

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

[0096] In an example embodiment, mapping the UCI into at least two PUSCH allocations may include mapping the coded UCI bits into one PUSCH allocation first (e.g., in a frequency first time second manner, if PUSCH allocation in FDM, then starting the PUSCH allocation from a lower frequency), and then, if necessary, continuing to map into another PUSCH allocation (e.g., in a frequency first time second manner). Which PUSCH allocation to start mapping on: For the case where the UCI is mapped into two PUSCH allocations, and which one to start from; the UE may start mapping into the PUSCH allocation with a higher / lower (starting from the top or bottom of the frequency range) starting RB in the frequency domain allocation, such as in the case of FDM-like PUSCH operation, or in the PUSCH configuration corresponding to a given TRP or TCI state (such as the first indication / applicable TCI state for SDM / FDM PUSCH operation). Alternatively, the PUSCH allocation to start mapping may be indicated to the UE via DCI, MAC CE (Media Access Control (MAC) Control Element), and / or RRC (Radio Resource Control). In one variation, the UE may map the UCI uniformly or almost uniformly to at least two PUSCH allocations (eg, this may be required in case of SDM PUSCH operation / scheme).

[0097] In an example embodiment, as an illustrative example, the difference (if any) between mapping UCI separately into two PUSCH allocations or mapping across two PUSCH allocations may be as follows: 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 two (or at least two) PUSCH allocations. In this case, the coded bits of the same UCI are mapped across at least two PUSCH allocations; and, mapping UCI separately into two PUSCH allocations may correspond to the case where different codewords are mapped to PUSCH allocations, or for the same codeword mapped to two PUSCH allocations, different RVs are used / indicated for each PUSCH allocation. In this case, the parts of UCI may be separately coded, and the coded bits of one UCI part may be mapped into one PUSCH allocation, and the coded bits of another UCI part may be mapped into another PUSCH allocation; alternatively, the coded bits of the same UCI are mapped to each PUSCH allocation.

[0098] If the UE is scheduled or indicated for coherent joint transmission operation, where, for example, the same layer(s) of the same codeword are to be transmitted using two PUSCH opportunities or allocations made across two panels (with a certain degree of consistency), the UE may map the UCI across the two PUSCH allocations.

[0099] If the UE is scheduled or indicated for SFN-like transmission operation, where, for example, the same layer(s) of the same codeword are repeated with each PUSCH opportunity or allocation made over two panels, the UE may map the UCI to two PUSCH allocations, where the UCI is repeated / mapped in exactly the same manner in each PUSCH allocation.

[0100] In some other embodiments, “mapping UCI across PUSCH allocations” and “mapping UCI into two PUSCH allocations, respectively” may correspond to / refer to the same thing, and may correspond to one of the above examples or explanations.

[0101] For example, note that for mapping UCI into at least two PUSCH allocations, the amount of resources (such as the number of REs (resource elements)) that the encoded UCI bits can occupy in the first PUSCH allocation and the second PUSCH allocation can be defined using a single β offset or at least two β offset values ​​(where the β offset can be per UCI type / part). In addition, there can be a single α (i.e., scaling parameter) value that sets an upper limit on the amount of resources that UCI can occupy (i.e., consume) in the at least two PUSCH allocations. Alternatively, there can be at least two α values ​​that set an upper limit on the amount of resources that UCI can occupy (or consume) in the first PUSCH allocation and the second PUSCH allocation, respectively.

[0102] In an example embodiment, (multiple) beta offset values ​​and / or (multiple) alpha values ​​may be associated with different capability value sets (or panels) or TRPs or CORESETpool indices or CORESET groups or TCI state sets or RS sets (such as SSB, CSI-RS, SRS), and the UE may determine which beta offset value or alpha value corresponds to which PUSCH allocation based on this association. (Example: each of these TCI states has an association with each PUSCH; therefore, there may be an association between the beta offset and the TCI state; and based on these two associations, the UE may determine which PUSCHs to use based on the configured beta offsets).

[0103] In an example embodiment, in the case of joint HARQ-ACK feedback (for multi-DCI mode), initially carried on PUCCH which may be multiplexed into 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 its corresponding PUSCH allocation.

[0104] In an example embodiment, in the case of two HARQ-ACK subcodebooks: the existing (overall) DAI (Downlink Allocation Indicator) field in the (UL) DCI may be reused or reinterpreted to indicate whether the corresponding subcodebook should be mapped to two PUSCH allocations, and if so, to which PUSCH allocation, or to one PUSCH allocation, and if so, to which PUSCH allocation; or, alternatively, a new indication in the DCI (or MAC CE or even RRC) may be used jointly or separately with the DAI field to indicate which subcodebook may be mapped to which PUSCH allocation(s) (or even if there should be no mapping of subcodebooks to PUSCH allocations).

[0105] In an example embodiment, for mapping UCI into two PUSCH allocations, the number of coded modulation symbols per layer of UCI may be determined jointly based on the two PUSCH allocations (e.g., in the case of a joint β offset (and / or α factor) of the two PUSCH allocations), where the number of resource elements in (multiple) OFDM symbols that may be used for UCI transmission may correspond to the two PUSCH allocations. Alternatively, the number of coded modulation symbols per layer of UCI may be determined separately for each PUSCH allocation (e.g., in the case of a separate β offset (and / or α factor) for the PUSCH allocation), where the number of resource elements in (multiple) OFDM symbols in the PUSCH allocation that may be used for UCI transmission may correspond only to the PUSCH allocation.

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

[0107] In an example embodiment, mapping of UCI into a PUSCH allocation or two PUSCH allocations may be done per layer.

[0108] 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 in the PUSCH) and / or UCI originally carried on the PUCCH (such as HARQ-ACK and / or CSI), which may be multiplexed into the PUSCH.

[0109] In an example embodiment, in case of frequency hopping, any of the mapping operations proposed above may be applied on a per PUSCH hop basis, since UCI may be mapped to two PUSCH hops for PUSCH allocation.

[0110] Note that although the description is made on UCI mapping considering single DCI (or even multiple DCI) simultaneous PUSCH transmission operation, similar aspects can also be applied to UCI multiplexing / mapping considering single DCI (or even multiple DCI) simultaneous PUCCH transmission operation, where UCI is initially carried on PUCCH, which can be multiplexed into another PUCCH. By basically replacing PUSCH with PUCCH and replacing TB (transport block) with "first UCI", at least some of the above aspects can be applied to the PUCCH case.

[0111] Figure 5is a diagram illustrating mapping of UCI (e.g., CSI) to two PUSCH allocations corresponding to two simultaneous PUSCH transmissions based on indicated β offsets. The PDCCH may carry or include DCI. Simultaneous PUSCH transmissions are scheduled (and indicated to the UE via DCI or scheduling information), and control information may be sent to the UE to indicate the β offsets, e.g., for each CSI part, each β offset may correspond to a PUSCH allocation or a PUSCH transmission. For example, Figure 5 As shown, A-CSI may be mapped to PUSCH allocation #0, and A-CSI may be mapped to PUSCH allocation #1.

[0112] Figure 6 is a diagram illustrating mapping of UCI into PUSCH based on scheduling of simultaneous PUSCH operation according to another example embodiment. Figure 6 An example of UCI being mapped to a PUSCH allocation having a transmission configuration indication (TCI) state that matches the TCI state of a physical uplink control channel (PUCCH) associated with at least one UCI is illustrated. In this example, TCI state #1 and TCI state #2 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, for example, HARQ ACK is multiplexed into PUSCH. As shown, PUCCH has TCI state #2, which corresponds to the same TRP or CORESETpool index as TCI state #1. Therefore, in this example, the UE maps the UCI (e.g., HARQ-ACK) of the PUCCH to PUSCH transmission #0 with TCI state #1.

[0113] Some additional examples will be described:

[0114] Example 1. A method, comprising: determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations, the at least two PUSCH allocations overlapping in the time domain and corresponding to at least two PUSCH transmissions for use in sending at least one uplink control information (UCI); and mapping, by the user equipment, the at least one UCI to at least one of: one of the at least two PUSCH allocations; respectively to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; wherein the mapping is 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, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0115] Example 2. The method according to Example 1 also includes: based on the mapping, sending the at least one UCI via one or more PUSCH allocations of the at least two PUSCH allocations.

[0116] Example 3. A method according to any one of Examples 1 to 2, wherein mapping 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 based on at least one of the following: 1) whether the at least one UCI is scheduled for transmission on one of the at least two PUSCHs, or 2) whether the at least one UCI is initially transmitted on a physical uplink control channel (PUCCH) as follows, and the PUCCH can be multiplexed to one of the at least two PUSCHs.

[0117] Example 4. A method according to Example 3, wherein: if the UCI is scheduled for transmission on one or both of the at least two PUSCHs, the mapping includes mapping the at least one UCI by the user equipment to each of the two PUSCH allocations, respectively, or across the at least two PUSCH allocations; and if the at least one UCI is initially carried on the PUCCH that can be multiplexed to one of the at least two PUSCHs, the mapping includes mapping the at least one UCI by the user equipment to one of the at least two PUSCH allocations.

[0118] Example 5. A method according to Example 4, wherein mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication includes: mapping the UCI to one PUSCH allocation of the at least two PUSCH allocations by the user equipment, the one PUSCH allocation corresponding to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, the same reference signal set, or the same physical cell ID (PCI).

[0119] Example 6. A method according to any one of Examples 1 to 5, wherein mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication includes mapping 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.

[0120] Example 7. A method according to Example 6, wherein: if the same codeword or data block is mapped across the at least two PUSCH allocations, mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication includes: mapping the at least one UCI to the two PUSCH allocations, respectively, or mapping across the at least two PUSCH allocations by the user equipment; and if different codewords or data blocks are mapped across the at least two PUSCH allocations, mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication includes mapping the UCI to one PUSCH allocation of the at least two PUSCH allocations by the user equipment, the one PUSCH allocation corresponding to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, the same reference signal set, or the same PCI.

[0121] Example 8. A method according to any one of Examples 1 to 7, wherein mapping 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 the at least one UCI based on: for the same codeword, whether the same redundancy version (RV) of the data block is used or indicated for both of the at least two PUSCH allocations, or whether different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

[0122] Example 9. A method according to Example 8, wherein: if the same redundancy version (RV) of the data block is used for both of the at least two PUSCH allocations, respectively, or is used across both of the at least two PUSCH allocations, mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication, includes: mapping the UCI across both of the at least two PUSCH allocations by the user equipment; and if different redundancy versions (RV) of the data block are used for the at least two PUSCH allocations, mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication, includes: mapping the at least one UCI to each of the at least two PUSCH allocations, respectively, or mapping the UCI to one of the at least two PUSCH allocations by the user equipment.

[0123] Example 10. A method according to any one of claims 1 to 9, wherein mapping the at least one UCI based on one or more configured or predefined rules, or at least one indication, includes: mapping based on a β offset value received by the user equipment in downlink control information.

[0124] Example 11. A method according to Example 10, wherein: a first subset of β values ​​is associated with: mapping the at least one UCI to two of the at least two PUSCH allocations, respectively, or mapping across the at least two PUSCH allocations; and a second subset of β values ​​is associated with: mapping the at least one UCI to one of the at least two PUSCHs.

[0125] Example 12. A method according to any one of Examples 1 to 11, wherein the mapping is based on the number of layers corresponding to each of the at least two PUSCH allocations.

[0126] Example 13. A method according to any one of Examples 1 to 12, wherein mapping the at least one UCI based on one or more configured or predefined rules, or at least one of at least one indication includes at least one of the following: mapping the at least one UCI to one of the at least two PUSCH allocations by the user equipment, the one PUSCH allocation having a higher or lower starting data block or frequency; or mapping the at least one UCI to one of the at least two PUSCH allocations by the user equipment, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

[0127] Example 14. A method according to any one of Examples 1 to 13, comprising: determining, by the user equipment, a first association between a β offset and / or an α value and the at least two PUSCH allocations; and / or determining, by the user equipment, a second association between a β offset and / or an α value and different capability value sets or antenna panels, transmission reception points (TRPs), CORESETpool indexes or CORESET groups, TCI state sets, or reference signal sets; and wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication, comprises: mapping the at least one UCI by the user equipment based on the first association and / or the second association.

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

[0129] Example 16. A device comprising: at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device to at least: determine at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations by a user equipment in a wireless network, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use when sending at least one uplink control information (UCI); and map the UCI by the user equipment to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; wherein the mapping is based on at least one of the following: one or more configured or predefined rules, or at least one indication received by the user equipment from a network node, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0130] Example 17. An apparatus according to Example 16, wherein the at least one processor and the computer program code are further configured to cause the apparatus to: based on the mapping, send the at least one uplink control information via one or more PUSCH allocations of the at least two PUSCH allocations.

[0131] Example 18. An apparatus according to any one of Examples 16 to 17, wherein the at least one processor and the computer program code are configured to cause the apparatus to: perform mapping based on at least one of one or more configured or predefined rules, or at least one indication, including mapping based on at least one of the following: 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 initially transmitted on a physical uplink control channel (PUCCH) that can be multiplexed to one of the at least two PUSCHs.

[0132] Example 19. An apparatus according to Example 18, wherein the at least one processor and the computer program code are configured to cause the apparatus to perform the following operations: if the UCI is scheduled to be transmitted on one or two PUSCHs, the mapping includes mapping the at least one UCI by the user equipment to two PUSCH allocations, respectively, or across two PUSCH allocations; and if the at least one UCI is initially capable of being multiplexed onto the PUCCH of one of the PUSCHs to be transmitted, the mapping includes mapping the at least one UCI by the user equipment to one of the PUSCH allocations.

[0133] Example 20. An apparatus according to Example 19, wherein the at least one processor and the computer program code configured to cause the apparatus to perform mapping based on one or more configured or predefined rules, or at least one of at least one indication include the at least one processor and the computer program code configured to cause the apparatus to perform the following operations: the user equipment maps the UCI to one of the PUSCH allocations, the one PUSCH allocation corresponding to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

[0134] Example 21. An apparatus according to any one of Examples 16 to 20, wherein 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 or more configured or predefined rules, or at least one indication, include the at least one processor and the computer program code configured to cause the apparatus to perform the following operations: mapping the at least one UCI based on: whether the same data block or codeword is mapped to two PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

[0135] Example 22. An apparatus according to Example 21, wherein the at least one processor and the computer program code are configured to cause the apparatus to perform the following operations: if the same codeword or data block is mapped across two PUSCH allocations, the mapping includes: the user equipment maps the at least one UCI to the two PUSCH allocations respectively, or maps across the two PUSCH allocations; and if different codewords or data blocks are mapped across the at least two PUSCH allocations, the mapping includes: the user equipment maps the UCI to one of the PUSCH allocations, the one PUSCH allocation corresponding to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

[0136] Example 23. An apparatus according to any one of Examples 16 to 22, wherein 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 configured or predefined rules, or at least one indication include the at least one processor and the computer program code configured to cause the apparatus to perform the following operations: mapping the at least one UCI based on: for the same codeword, whether the same redundancy version (RV) of the data block is used or indicated for two PUSCH allocations, or whether different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

[0137] Example 24. An apparatus according to Example 23, wherein the at least one processor and the computer program code are configured to cause the apparatus to perform the following operations: if the same redundancy version (RV) of the data block is used for two PUSCH allocations, respectively, or is used across two PUSCH allocations, the mapping includes mapping the UCI across two PUSCH allocations by the user equipment; and if different redundancy versions (RV) of the data block are used for the at least two PUSCH allocations, the mapping includes: mapping the at least one UCI to each of the PUSCH allocations, respectively, in the PUSCH allocations, or mapping the UCI to one of the PUSCH allocations, by the user equipment.

[0138] Example 25. An apparatus according to any one of Examples 16 to 24, wherein the at least one processor and the computer program code are configured to cause the apparatus to map the at least one UCI based on at least one or more configured or predefined rules, or at least one indication, including the at least one processor and the computer program code configured to cause the apparatus to perform the following operations: mapping based on a β offset value received by the user equipment in the downlink control information.

[0139] Example 26. An apparatus according to Example 25, wherein: a first subset of β values ​​is associated with: mapping the at least one UCI to two PUSCH allocations, respectively, or mapping across two PUSCH allocations; and a second subset of β values ​​is associated with: mapping the at least one UCI to one of the PUSCHs.

[0140] Example 27. An apparatus according to any one of Examples 16 to 26, wherein the at least one processor and the computer program code are configured to cause the apparatus to map the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication, including the at least one processor and the computer program code configured to perform the following operations: mapping based on the number of layers corresponding to each PUSCH allocation.

[0141] Example 28. An apparatus according to any one of Examples 16 to 27, wherein 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 configured or predefined rules, or at least one indication include the at least one processor and the computer program code configured to perform at least one of the following: mapping the at least one UCI to one PUSCH allocation in the PUSCH allocation by the user equipment, the one PUSCH allocation having a higher or lower starting data block or frequency; or mapping the at least one UCI to one PUSCH allocation in the PUSCH allocation by the user equipment, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

[0142] Example 29. An apparatus according to any one of Examples 16 to 28, wherein the at least one processor and the computer program code are configured to cause the apparatus to: determine, by the user equipment, a first association between a β offset and / or an α value and the PUSCH allocation; and determine, by the user equipment, a second association between a β offset and / or an α value and different capability value sets or antenna panels, transmission reception points (TRPs), CORESETpool indexes or CORESET groups, TCI state sets, or reference signal sets; and wherein 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 configured or predefined rules, or at least one indication include the at least one processor and the computer program code configured to cause the apparatus to perform the following operations: the user equipment maps the at least one UCI based on the first association and the second association.

[0143] Example 30. An apparatus according to any one of Examples 16 to 29, wherein 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 or more configured or predefined rules, or at least one indication include the at least one processor and the computer program code configured to perform the following operations: mapping the at least one UCI by the user equipment to a PUSCH allocation having a transmission configuration indication (TCI) state, the TCI state matching the TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

[0144] Example 31. A method, comprising: sending downlink control information by a network node to a user equipment, the downlink control information including information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send 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 has been mapped to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; wherein the at least one UCI has been mapped based on at least one or more configured or predefined rules, or at least one of at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0145] Example 32. A method according to Example 31, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on at least one of the following: 1) whether the at least one UCI is scheduled for transmission on one of the PUSCHs, or 2) whether the UCI was originally transmitted on a physical uplink control channel (PUCCH) as follows, and the PUCCH can be multiplexed to one of the PUSCHs.

[0146] Example 33. A method according to Example 32, wherein the at least one UCI has been mapped based on one or more configured or predefined rules, or at least one of at least one indication, including: the at least one UCI has been mapped to a PUSCH allocation in the PUSCH allocation, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

[0147] Example 34. A method according to any one of Examples 31 to 33, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on: whether the same data block or codeword is mapped to two PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

[0148] Example 35. A method according to Example 33, wherein: if the same codeword or data block is mapped across two PUSCH allocations, the at least one UCI has been mapped to the two PUSCH allocations respectively, or mapped across the two PUSCH allocations; and if different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI has been mapped to one PUSCH allocation in the PUSCH allocations, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

[0149] Example 36. A method according to any one of Examples 31 to 35, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on: for the same codeword, whether the same redundancy version (RV) of the data block is used or indicated for two PUSCH allocations, or whether different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

[0150] Example 37. A method according to Example 36, wherein: if the same redundancy version (RV) of the data block is used for two PUSCH allocations, respectively, or is used across two PUSCH allocations, the at least one UCI has been mapped across two PUSCH allocations; and if different redundancy versions (RV) of the data block are used for the at least two PUSCH allocations, the at least one UCI has been mapped to each of the PUSCH allocations, respectively, or the UCI is mapped to one of the PUSCH allocations.

[0151] Example 38. A method according to any one of Examples 31 to 37, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including: the at least one UCI has been mapped based on a β offset value received by the user equipment in the downlink control information.

[0152] Example 39. A method according to Example 38, wherein: a first subset of β values ​​is associated with: mapping the at least one UCI to two PUSCH allocations, respectively, or mapping across two PUSCH allocations; and a second subset of β values ​​is associated with: mapping the at least one UCI to one of the PUSCHs.

[0153] Example 40. A method according to any one of Examples 31 to 39, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including: the at least one UCI has been mapped based on the number of layers corresponding to each PUSCH allocation.

[0154] Example 41. A method according to any one of Examples 31 to 39, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including: the at least one UCI has been mapped based on at least one of the following: the at least one UCI is mapped to one PUSCH allocation in the PUSCH allocation, the one PUSCH allocation having a higher or lower starting data block or frequency; or the at least one UCI is mapped to one PUSCH allocation in the PUSCH allocation, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

[0155] Example 42. A method according to any one of Examples 31 to 41, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped into a PUSCH allocation, the PUSCH allocation having a transmission configuration indication (TCI) state, the TCI state matching the TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

[0156] Example 43. An apparatus comprising: at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: send downlink control information by a network node to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send at least one uplink control information (UCI); receive at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations from the user equipment by the network node, wherein the at least one UCI has been mapped to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; wherein the at least one UCI has been mapped based on at least one or more configured or predefined rules, or at least one of at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

[0157] Example 44. An apparatus according to Example 43, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on at least one of the following: 1) whether the at least one UCI is scheduled for transmission on one of the PUSCHs, or 2) whether the UCI was originally transmitted on a physical uplink control channel (PUCCH) as follows, and the PUCCH can be multiplexed to one of the PUSCHs.

[0158] Example 45. An apparatus according to Example 44, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one of at least one indication, including: the at least one UCI has been mapped to a PUSCH allocation in the PUSCH allocation, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

[0159] Example 46. An apparatus according to any one of Examples 43 to 45, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on: whether the same data block or codeword is mapped to two PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

[0160] Example 47. An apparatus according to Example 45, wherein: if the same codeword or data block is mapped across two PUSCH allocations, the at least one UCI is mapped to the two PUSCH allocations respectively, or is mapped across the two PUSCH allocations; and if different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one PUSCH allocation in the PUSCH allocations, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

[0161] Example 48. An apparatus according to any one of Examples 43 to 47, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on: for the same codeword, whether the same redundancy version (RV) of the data block is used or indicated for two PUSCH allocations, or whether different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

[0162] Example 49. An apparatus according to Example 48, wherein: if the same redundancy version (RV) of the data block is used for two PUSCH allocations, respectively, or is used across two PUSCH allocations, the at least one UCI has been mapped across two PUSCH allocations; and if different redundancy versions (RV) of the data block are used for the at least two PUSCH allocations, the at least one UCI has been mapped to each of the PUSCH allocations, respectively, or the UCI is mapped to one of the PUSCH allocations.

[0163] Example 50. An apparatus according to any one of Examples 43 to 49, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including: the at least one UCI has been mapped based on a β offset value received by the user equipment within the downlink control information.

[0164] Example 51. An apparatus according to Example 50, wherein: a first subset of β values ​​is associated with: mapping the at least one UCI to two PUSCH allocations, respectively, or mapping across two PUSCH allocations; and a second subset of β values ​​is associated with: mapping the at least one UCI to one of the PUSCHs.

[0165] Example 52. An apparatus according to any one of Examples 43 to 51, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including: the at least one UCI has been mapped based on the number of layers corresponding to each PUSCH allocation.

[0166] Example 53. An apparatus according to any one of Examples 43 to 51, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including: the at least one UCI has been mapped based on at least one of the following: the at least one UCI has been mapped to one PUSCH allocation in the PUSCH allocations, the one PUSCH allocation having a higher or lower starting data block or frequency; or the at least one UCI has been mapped to one PUSCH allocation in the PUSCH allocations, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

[0167] Example 54. An apparatus according to any one of Examples 43 to 53, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped into a PUSCH allocation, the PUSCH allocation having a transmission configuration indication (TCI) state, the TCI state matching the TCI state of a physical uplink control channel (PUCCH) associated with the at least one UCI.

[0168] Example 55. A non-transitory computer-readable storage medium, comprising instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to: send downlink control information by a network node to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send at least one uplink control information (UCI); and receive by the network node at least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations from the user equipment, wherein the at least one UCI has been mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; and wherein the at least one UCI has been mapped based on at least one or more configured or predefined rules, or at least one of at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

[0169] Example 56. An apparatus comprising: a component for sending downlink control information by a network node to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being used by the user equipment to send at least one uplink control information (UCI); and a component 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, wherein the at least one UCI has been mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; and wherein the at least one UCI has been mapped based on at least one or more configured or predefined rules, or at least one of at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

[0170] Example 57. A non-transitory computer-readable storage medium, comprising instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to: determine, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use when sending at least one uplink control information (UCI); and map, by the user equipment, the UCI to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; wherein the mapping is based on at least one of the following: one or more configured or predefined rules, or at least one indication received by the user equipment from a network node, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0171] Example 58. An apparatus comprising: a component for determining, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use in sending at least one uplink control information (UCI); and a component for mapping, by the user equipment, the UCI to at least one of: one of the at least two PUSCH allocations; respectively to each of the at least two PUSCH allocations; or across the at least two PUSCH allocations; wherein the mapping is 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, and wherein the PUSCH allocation includes resources allocated to the user equipment for PUSCH transmission.

[0172] Figure 7 1 is a block diagram of a network node (e.g., AP, BS, eNB, gNB, RAN node) 1200 according to an example embodiment. The wireless station 1200 may include, for example, one or more (e.g., Figure 7 The wireless station also includes two RF (radio frequency) or wireless transceivers 1202A, 1202B shown, each of which includes a transmitter for sending 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.

[0173] The processor 1204 may also make decisions or decisions, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. For example, the processor 1204, which may be a baseband processor, may generate messages, packets, frames or other signals for transmission via the wireless transceiver 1202 (1202A or 1202B). The processor 1204 may control the transmission of signals or messages through a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by the wireless transceiver 1202). The processor 1204 may be programmable and capable of executing software or other instructions stored in a memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. For example, the processor 1204 may be (or may include) hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. For example, using other terms, the processor 1204 and the transceiver 1202 may be considered together as a wireless transmitter / receiver system.

[0174] In addition, reference Figure 7 , the controller (or processor) 1208 can execute software and instructions and can provide overall control for the station 1200 and can Figure 7 Other systems not shown provide controls, such as controlling input / output devices (e.g., display, keypad), and / or software that can execute one or more applications that may be provided on wireless station 1200, such as an email program, audio / video applications, a word processor, voice over IP applications, or other applications or software.

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

[0176] According to another example embodiment, the RF or (multiple) wireless transceiver 1202A / 1202B can receive signals or data and / or send or transmit signals or data. The 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.

[0177] Embodiments of the various techniques described herein may be implemented in a digital electronic circuit system, or in computer hardware, firmware, software, or a combination thereof. Embodiments may be implemented as computer program products, i.e., computer programs tangibly embodied in information carriers, for example, in machine-readable storage devices or in propagated signals, for data processing devices to execute or control the operation of data processing devices, for example, programmable processors, one computer or multiple computers. Embodiments may also be provided on a computer-readable medium or a computer-readable storage medium, which may be a non-transitory medium. Embodiments of various techniques may also include embodiments provided via transient signals or media, and / or downloadable programs and / or software embodiments via the Internet or (multiple) other networks (wired networks and / or wireless networks). In addition, embodiments may be provided via machine type communications (MTC) or via the Internet of Things (IOT).

[0178] A computer program may be in source code form, object code form or some intermediate form and may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include, for example, recording media, computer memories, read-only memories, optoelectronic and / or electrical carrier signals, telecommunication signals and software distribution packages. Depending on the processing power required, a computer program may be executed in a single electronic digital computer or distributed among multiple computers.

[0179] In addition, embodiments of the various techniques described herein may use cyber-physical systems (CPS) (systems that enable computing elements that control physical entities to collaborate). CPS can implement and utilize a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in different locations in physical objects. Mobile cyber-physical systems (where the physical system in question has inherent mobility) are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals. The popularity of smartphones has increased interest in the field of mobile cyber-physical systems. Therefore, various embodiments of the techniques described herein may be provided by one or more of these techniques.

[0180] Computer programs such as the above-mentioned (multiple) computer programs can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program, or as a module, component, subroutine or other unit or part thereof suitable for a computing environment. A computer program can be deployed to execute on one computer, or on multiple computers at one site, or on multiple computers distributed between multiple sites and interconnected by a communication network.

[0181] The method steps may be performed by one or more programmable processors executing a computer program or a portion of a computer program to perform functions by operating on input data and generating output. The method steps may also be performed by, and the apparatus may be implemented as, a special purpose logic circuit system, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0182] For example, processors suitable for executing computer programs include both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Typically, the processor will receive 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 or be operatively coupled to receive data from or transfer data to or both of one or more mass storage devices (e.g., magnetic, magneto-optical disks, or optical disks) for storing data. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including, for example, 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 a dedicated logic circuit system.

[0183] To provide interaction with a user, an embodiment may be implemented on a computer having a display device (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) display) for displaying information to the user, and a user interface (such as a keyboard and a pointing device, such as a mouse or trackball) through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and the input from the user may be received in any form, including sound, voice, or tactile input.

[0184] Embodiments may be implemented in a computing system that includes: a back-end component, for example, as a data server; or includes a middleware component, for example, an application server; or includes a front-end component, for example, 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 media of digital data communication, such as a communication network. Examples of communication networks include local area networks (LANs) and wide area networks (WANs), such as the Internet.

[0185] Although certain features of the described embodiments have been illustrated as described herein, those skilled in the art will now be able to conceive of many modifications, substitutions, changes and equivalents. Therefore, it should be understood that the appended claims are intended to cover all such modifications and changes that fall within the true spirit of the various embodiments.

Claims

1. A method comprising: determining, by a user equipment in a wireless network, at least two physical uplink shared channel (PUSCH) allocations, the at least two PUSCH allocations overlapping in a time domain and corresponding to at least two PUSCH transmissions for use in sending at least one uplink control information (UCI); and The at least one UCI is mapped, by the user equipment, to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or allocated across the at least two PUSCHs; Wherein the mapping is 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, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

2. The method according to claim 1, further comprising: Based on the mapping, the at least one UCI is sent via one or more PUSCH allocations of the at least two PUSCH allocations.

3. The method of any one of claims 1 to 2, wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication, comprises mapping 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 at least one UCI is initially transmitted on a physical uplink control channel (PUCCH) that can be multiplexed to one of the at least two PUSCHs.

4. The method according to claim 3, wherein: If the UCI is scheduled for transmission on one or both of the at least two PUSCHs, the mapping comprises: mapping, by the user equipment, the at least one UCI to each of the two PUSCH allocations, respectively, or mapping across the at least two PUSCH allocations; and If the at least one UCI is originally transmitted on the PUCCH that can be multiplexed to one of the at least two PUSCHs, the mapping comprises mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations.

5. The method of claim 4, wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules or at least one indication comprises: The UCI is mapped by the user equipment to one PUSCH allocation of the at least two PUSCH allocations, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, the same reference signal set, or the same physical cell ID (PCI).

6. The method according to any one of claims 1 to 5, wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication, comprises mapping 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.

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

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

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

10. The method according to any one of claims 1 to 9, wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication comprises: The mapping is performed based on a beta offset value received by the user equipment in downlink control information.

11. The method according to claim 10, wherein: A first subset of β values ​​is associated with mapping the at least one UCI to or across both of the at least two PUSCH allocations, respectively; and A second subset of β values ​​is associated with mapping the at least one UCI to one of the at least two PUSCHs.

12. The method according to any one of claims 1 to 11, wherein the mapping is based on the number of layers corresponding to each of the at least two PUSCH allocations.

13. The method according to any one of claims 1 to 12, wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication comprises at least one of the following: mapping, by the user equipment, the at least one UCI to one of the at least two PUSCH allocations, the one PUSCH allocation having a higher or lower starting data block or frequency; or The at least one UCI is mapped, by the user equipment, to one PUSCH allocation of the at least two PUSCH allocations, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

14. The method according to any one of claims 1 to 13, comprising: 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 capability value set or antenna panel, a transmission reception point (TRP), a CORESETpool index or a CORESET group, a TCI state set, or a reference signal set; and Wherein mapping the at least one UCI based on at least one of one or more configured or predefined rules or at least one indication comprises: mapping, by the user equipment, the at least one UCI based on the first association and / or the second association.

15. The method according to any one of claims 1 to 14, wherein 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 comprises: The at least one UCI is mapped, by the user equipment, 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.

16. An apparatus comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: Determining, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use in sending at least one uplink control information (UCI); and The user equipment maps the UCI to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or allocated across the at least two PUSCHs; Wherein the mapping is 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, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

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

18. An apparatus according to any one of claims 16 to 17, wherein the at least one processor and the computer program code are configured to cause the apparatus to: perform mapping based on at least one of one or more configured or predefined rules, or at least one indication, including mapping based on at least one of the following: 1) whether the at least one UCI is scheduled to be transmitted on one of the at least two PUSCHs, or 2) whether the UCI is initially transmitted on a physical uplink control channel (PUCCH) as follows, and the PUCCH can be multiplexed to one of the at least two PUSCHs.

19. The apparatus of claim 18, wherein the at least one processor and the computer program code are configured to cause the apparatus to: If the UCI is scheduled for transmission on one or two PUSCHs, the mapping includes: Mapping, by the user equipment, the at least one UCI to two PUSCH allocations respectively, or mapping across two PUSCH allocations; and If the at least one UCI is originally transmitted on the PUCCH which can be multiplexed to one of the PUSCHs, the mapping comprises mapping, by the user equipment, the at least one UCI to one of the PUSCH allocations.

20. The apparatus of claim 19, wherein the at least one processor and the computer program code configured to cause the apparatus to perform mapping based on at least one of one or more configured or predefined rules, or at least one indication, comprises the at least one processor and the computer program code configured to cause the apparatus to: The UCI is mapped by the user equipment to a PUSCH allocation in the PUSCH allocation, and the PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

21. An apparatus according to any one of claims 16 to 20, wherein the at least one processor and the computer program code are configured to cause the apparatus to map the at least one UCI to one of the PUSCH allocations based on at least one of one or more configured or predefined rules, or at least one indication, and include the at least one processor and the computer program code configured to cause the apparatus to perform the following items: map the at least one UCI based on whether the same data block or codeword is mapped to two PUSCH allocations, or based on whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

22. The apparatus of claim 21, wherein the at least one processor and the computer program code are configured to cause the apparatus to: If the same codeword or data block is mapped across two PUSCH allocations, the mapping includes: Mapping, by the user equipment, the at least one UCI to two PUSCH allocations respectively, or mapping across two PUSCH allocations; as well as If different codewords or data blocks are mapped across the at least two PUSCH allocations, the mapping includes: mapping the UCI by the user equipment to one PUSCH allocation among the PUSCH allocations, the one PUSCH allocation corresponding to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

23. An apparatus according to any one of claims 16 to 22, wherein 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 configured or predefined rules, or at least one indication, include the at least one processor and the computer program code configured to cause the apparatus to perform the following items: mapping the at least one UCI based on whether the same redundancy version (RV) of the data block is used or indicated for two PUSCH allocations for the same codeword, or based on whether different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

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

25. The apparatus according to any one of claims 16 to 24, wherein the at least one processor and the computer program code are configured to cause the apparatus to map the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication, comprising the at least one processor and the computer program code configured to cause the apparatus to perform the following items: mapping based on a β offset value received by the user equipment in downlink control information.

26. The apparatus of claim 25, wherein: A first subset of β values ​​is associated with: mapping the at least one UCI to or across two PUSCH allocations, respectively; and A second subset of β values ​​is associated with mapping the at least one UCI to one of the PUSCHs.

27. The apparatus of any one of claims 16 to 26, wherein 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 configured or predefined rules, or at least one indication, comprises the at least one processor and the computer program code configured to: map based on the number of layers corresponding to each PUSCH allocation.

28. The apparatus of any one of claims 16 to 27, wherein the at least one processor and the computer program code configured to map the at least one UCI based on at least one of one or more configured or predefined rules, or at least one indication, comprises the at least one processor and the computer program code configured to perform at least one of the following: mapping, by the user equipment, the at least one UCI to one of the PUSCH allocations, the one PUSCH allocation having a higher or lower starting data block or frequency; or The at least one UCI is mapped, by the user equipment, to one of the PUSCH allocations, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

29. The apparatus of any one of claims 16 to 28, wherein the at least one processor and the computer program code are configured to 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, transmission reception point (TRP), CORESETpool index or CORESET group, TCI state set, or reference signal set; and 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 configured or predefined rules or at least one indication include the at least one processor and the computer program code configured to cause the apparatus to perform the following items: mapping the at least one UCI by the user equipment based on the first association and the second association.

30. The apparatus of any one of claims 16 to 29, wherein 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 configured or predefined rules, or at least one indication, comprises the at least one processor and the computer program code configured to: The at least one UCI is mapped, by the user equipment, 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.

31. A method comprising: Sending, by a network node, downlink control information to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being usable by the user equipment to send at least one uplink control information (UCI); At least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations are received by the network node from the user equipment, wherein the at least one UCI has been mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or allocated across the at least two PUSCHs; wherein the at least one UCI has been mapped based on at least one of: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

32. The method of claim 31 , wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including the at least one UCI having been mapped based on at least one of: 1) whether the at least one UCI is scheduled for transmission on one of the PUSCHs, or 2) whether the UCI was originally transmitted on a physical uplink control channel (PUCCH) that can be multiplexed to one of the PUSCHs.

33. The method of claim 32, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprises: The at least one UCI has been mapped to a PUSCH allocation in the PUSCH allocation, and the PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

34. A method according to any one of claims 31 to 33, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on the following items: whether the same data block or codeword is mapped to two PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

35. The method of claim 33, wherein: If the same codeword or data block is mapped across two PUSCH allocations, the at least one UCI has been mapped to the two PUSCH allocations, respectively, or is mapped across the two PUSCH allocations; and If different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI has been mapped to one PUSCH allocation among the PUSCH allocations, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

36. A method according to any one of claims 31 to 35, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on the following items: for the same codeword, the same redundancy version (RV) of the data block is used or indicated for two PUSCH allocations, or different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

37. The method of claim 36, wherein: If the same redundancy version (RV) of the data block is used for two PUSCH allocations, respectively, or is used across two PUSCH allocations, the at least one UCI has been mapped across two PUSCH allocations; and If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the at least one UCI has been mapped to each of the PUSCH allocations, respectively, or the UCI is mapped to one of the PUSCH allocations.

38. The method according to any one of claims 31 to 37, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been mapped based on a beta offset value received by the user equipment within downlink control information.

39. The method of claim 38, wherein: A first subset of β values ​​is associated with: mapping the at least one UCI to or across two PUSCH allocations, respectively; and A second subset of β values ​​is associated with mapping the at least one UCI to one of the PUSCHs.

40. The method of any one of claims 31 to 39, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been mapped based on the number of layers corresponding to each PUSCH allocation.

41. The method of any one of claims 31 to 39, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including the at least one UCI having been mapped based on at least one of: The at least one UCI is mapped to one of the PUSCH allocations, the one PUSCH allocation having a higher or lower starting data block or frequency; or The at least one UCI is mapped to one of the PUSCH allocations, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

42. The method of any one of claims 31 to 41, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been 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.

43. An apparatus comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: Sending, by a network node, downlink control information to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being usable by the user equipment to send at least one uplink control information (UCI); At least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations are received by the network node from the user equipment, wherein the at least one UCI has been mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or allocated across the at least two PUSCHs; wherein the at least one UCI has been mapped based on at least one of: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

44. An apparatus according to claim 43, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on at least one of the following: 1) whether the at least one UCI is scheduled for transmission on one of the PUSCHs, or 2) whether the UCI was originally transmitted on a physical uplink control channel (PUCCH) as follows, and the PUCCH can be multiplexed to one of the PUSCHs.

45. The apparatus of claim 44, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been mapped to a PUSCH allocation in the PUSCH allocation, and the PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

46. ​​An apparatus according to any one of claims 43 to 45, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on the following items: whether the same data block or codeword is mapped to two PUSCH allocations, or whether different data blocks or codewords are mapped to the at least two PUSCH allocations.

47. The apparatus of claim 45, wherein: If the same codeword or data block is mapped across two PUSCH allocations, the at least one UCI is mapped to the two PUSCH allocations, respectively, or is mapped across the two PUSCH allocations; and If different codewords or data blocks are mapped across the at least two PUSCH allocations, the at least one UCI is mapped to one PUSCH allocation among the PUSCH allocations, and the one PUSCH allocation corresponds to at least one of the following: the same capability value set as the PUCCH, the same antenna panel, the same transmission reception point (TRP), the same control resource set pool index (CORESETpoolindex), the same CORESET group, the same transmission configuration indication (TCI) state set, or the same reference signal set.

48. An apparatus according to any one of claims 43 to 47, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including that the at least one UCI has been mapped based on the following items: for the same codeword, the same redundancy version (RV) of the data block is used or indicated for two PUSCH allocations, or different redundancy versions (RV) of the data block are used or indicated for the at least two PUSCH allocations.

49. The apparatus of claim 48, wherein: If the same redundancy version (RV) of the data block is used for two PUSCH allocations, respectively, or is used across two PUSCH allocations, the at least one UCI has been mapped across two PUSCH allocations; and If different redundancy versions (RVs) of the data block are used for the at least two PUSCH allocations, the at least one UCI has been mapped to each of the PUSCH allocations, respectively, or the UCI is mapped to one of the PUSCH allocations.

50. The apparatus of any one of claims 43 to 49, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been mapped based on a beta offset value received by the user equipment within downlink control information.

51. The apparatus of claim 50, wherein: A first subset of β values ​​is associated with: mapping the at least one UCI to or across two PUSCH allocations, respectively; and A second subset of β values ​​is associated with mapping the at least one UCI to one of the PUSCHs.

52. The apparatus of any one of claims 43 to 51, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been mapped based on the number of layers corresponding to each PUSCH allocation.

53. The apparatus of any one of claims 43 to 51, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication, including the at least one UCI having been mapped based on at least one of: The at least one UCI has been mapped to one of the PUSCH allocations, the one PUSCH allocation having a higher or lower starting data block or frequency; or The at least one UCI has been mapped to one of the PUSCH allocations, the one PUSCH allocation corresponding to a specific transmission reception point (TRP) or a specific transmission configuration indication (TCI) state.

54. The apparatus of any one of claims 43 to 53, wherein the at least one UCI has been mapped based on at least one of one or more configured or predefined rules, or at least one indication comprising: The at least one UCI has been 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.

55. A non-transitory computer-readable storage medium comprising instructions stored thereon, which instructions, when executed by at least one processor, are configured to cause a computing system to: Sending, by a network node, downlink control information to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being usable by the user equipment to send at least one uplink control information (UCI); and At least two PUSCH transmissions corresponding to the at least two time-domain PUSCH allocations are received by the network node from the user equipment, wherein the at least one UCI has been mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or across the at least two PUSCH allocations; and wherein the at least one UCI has been mapped based on at least one of: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

56. An apparatus comprising: means for sending, by a network node, downlink control information to a user equipment, the downlink control information comprising information indicating at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations being usable by the user equipment for sending at least one uplink control information (UCI); as well as 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, wherein the at least one UCI is mapped to at least one of: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or across the at least two PUSCH allocations; and wherein the at least one UCI has been mapped based on at least one of: one or more configured or predefined rules, or at least one indication provided by the network node to the user equipment, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

57. A non-transitory computer-readable storage medium comprising instructions stored thereon, which instructions, when executed by at least one processor, are configured to cause a computing system to: Determining, by a user equipment in a wireless network, at least two time-domain overlapping physical uplink shared channel (PUSCH) allocations, the at least two time-domain overlapping PUSCH allocations corresponding to at least two PUSCH transmissions for use in sending at least one uplink control information (UCI); and The user equipment maps the UCI to at least one of the following: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or allocated across the at least two PUSCHs; Wherein the mapping is 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, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

58. An apparatus comprising: Means for determining, by a user equipment in a wireless network, at least two time-domain overlapping 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 at least one of: one of the at least two PUSCH allocations; respectively mapped to each PUSCH allocation of the at least two PUSCH allocations; or allocated across the at least two PUSCHs; Wherein the mapping is 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, and wherein the PUSCH allocation comprises resources allocated to the user equipment for PUSCH transmission.

Images