Techniques for configuring multiplexing of uplink control information in wireless communications

Abstract

Aspects described herein relate to receiving downlink control information (DCI) including a parameter from a network node, the parameter having a value indicating whether uplink control information (UCI) is to be multiplexed with an uplink control channel or an uplink shared channel; multiplexing the UCI with one of an uplink control channel or an uplink shared channel based on the value; and transmitting one of an uplink control channel or an uplink shared channel multiplexed with the UCI. Other aspects relate to generating DCI and demultiplexing UCI.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. nonprovisional patent application No. 18 / 483,804, filed October 10, 2023, entitled "Techniques for Configuring Multiplexing of Uplink Control Information in Wireless Communications," the entire contents of which are incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication systems in general, and more specifically to techniques for multiplexing uplink control information (UCI). Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can be multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, and Single Carrier Frequency Division Multiple Access (SC-FDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. For example, fifth-generation (5G) wireless communication technology (which may be referred to as 5G New Radio (5G NR)) is designed to expand and support a diverse range of use cases and applications compared to current mobile network generations. In one aspect, 5G communication technologies may include: enhanced mobile broadband addressing for human-centric use cases to access multimedia content, services, and data; ultra-reliable low-latency communication (URLLC) with certain specifications for latency and reliability; and massive machine-type communication that allows the transmission of a very large number of connected devices and a relatively small amount of non-latency-sensitive information. Summary of the Invention

[0005] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a broad overview of all anticipated aspects, nor is it intended to identify key or essential elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0006] According to one aspect, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; one or more memories configured to store instructions individually or in combination; and one or more processors communicatively coupled to the one or more memories. The one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to: receive downlink control information (DCI) from a network node, the parameters having a value indicating whether uplink control information (UCI) should be multiplexed with an uplink control channel or an uplink shared channel; multiplex the UCI with the uplink control channel or the uplink shared channel based on the value; and transmit the uplink control channel or the uplink shared channel multiplexed with the UCI.

[0007] On the other hand, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; one or more memories configured to store instructions individually or in combination; and one or more processors communicatively coupled to the one or more memories. The one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to: generate a DCI including parameters having values ​​indicating whether the UCI should be multiplexed with an uplink control channel or an uplink shared channel; and transmit the DCI to a user equipment (UE).

[0008] In another aspect, a method for wireless communication at a UE is provided, the method comprising: receiving from a network node a DCI including parameters having a value indicating whether the UCI is to be multiplexed with an uplink control channel or an uplink shared channel; having the UE multiplex the UCI with the uplink control channel or the uplink shared channel based on the value; and transmitting the uplink control channel or the uplink shared channel multiplexed with the UCI.

[0009] On the other hand, a method for wireless communication at a network node is provided, the method comprising: generating a DCI including parameters having values ​​indicating whether the UCI should be multiplexed with an uplink control channel or an uplink shared channel; and transmitting the DCI to a UE.

[0010] In another aspect, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions to perform operations of the methods described herein. In another aspect, an apparatus for wireless communication is provided, the apparatus including components for performing operations of the methods described herein. In yet another aspect, a computer-readable medium is provided, the computer-readable medium including code executable by one or more processors to perform operations of the methods described herein.

[0011] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate some exemplary features of one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0012] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided for illustration and not limitation of the disclosed aspects, wherein similar names represent similar elements, and in the drawings: Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are illustrated; Figure 2 These are illustrations illustrating examples of decomposed base station architectures according to various aspects of this disclosure; Figure 3 This is a block diagram illustrating examples of user equipment (UE) according to various aspects of this disclosure; Figure 4 This is a block diagram illustrating examples of base stations according to various aspects of this disclosure; Figure 5 This is a flowchart illustrating examples of methods for multiplexing uplink control information (UCI) in an uplink control channel or multiplexing uplink control information (UCI) with an uplink shared channel, according to the aspects described herein. Figure 6 This is a flowchart illustrating an example of a method for indicating whether UCI is multiplexed in the uplink control channel or multiplexed with the uplink shared channel, according to the aspects described herein. Figure 7 Examples of resource allocation for multiplexing UCI on an uplink shared channel are illustrated according to the aspects described herein; Figure 8Examples of resource allocation for multiplexing UCI over multiple uplink shared channels are illustrated according to the aspects described herein; and Figure 9 This is a block diagram illustrating examples of multiple-input multiple-output (MIMO) communication systems including base stations and UEs according to various aspects of this disclosure. Detailed Implementation

[0013] Various aspects will now be described with reference to the accompanying drawings. In the following description, numerous specific details are described for illustrative purposes and to provide a thorough understanding of one or more aspects. However, it will be apparent that such aspects can be practiced without these specific details.

[0014] The described features generally involve configuring a device to multiplex uplink control information (UCI) with uplink control channels or uplink shared channels. For example, a device (such as a user equipment (UE) in a fifth-generation (5G) new radio (NR) or other wireless communication technology) can be scheduled (e.g., by a network node, such as a gNB) to communicate on an uplink control channel (such as a physical uplink control channel (PUCCH)) or an uplink shared channel (such as a physical uplink shared channel (PUSCH)). In some examples, the UE can multiplex UCI transmissions with other PUCCH transmissions or PUSCH transmissions to send to the network node. In one example, the device can multiplex multiple UCI transmissions to transmit on a single PUCCH, but can schedule multiple PUCCH resources for transmitting the UCI. In another example, if the UCI or corresponding PUCCH overlaps with PUSCH resources, the device can multiplex the UCI with the PUSCH to save radio resources, reduce potential interference between PUCCH and PUSCH transmissions, etc. For example, when overlapping or parallel PUCCH or PUSCH transmissions are scheduled on the same component carrier (CC), mutual modulation and / or out-of-band transmission may increase, which may cause the UE to reduce its transmission power and correspondingly reduce uplink coverage.

[0015] Therefore, the multiplexing of PUCCHs (e.g., with other PUCCHs and / or PUSCHs) is introduced. In 5G NR, the device performs a sequential process to determine whether to multiplex a UCI with other PUCCHs and / or PUSCHs. For example, the device can determine whether the scheduled PUCCHs overlap in the time domain, and if so, it can perform an iterative pseudocode process to determine the final PUCCH used for multiplexing the UCI. Similarly, the device can determine whether the scheduled PUCCHs overlap with one or more PUSCHs in the time domain, and if so, it can execute a set of rules for prioritizing the PUSCHs and select the PUSCH with the highest priority as the final PUSCH used for multiplexing the UCI. Specifically, in 5G NR, for UCI multiplexing within a PUCCH group and on a PUSCH, the device can perform the following two steps: 1) multiplexing the UCIs of overlapping PUCCH transmissions into a PUCCH resource (resource Z), which can be per PUCCH slot; and 2) if Z overlaps with at least one PUSCH, then multiplexing the UCIs in Z, excluding scheduling requests (SRs), into a PUSCH according to the following priorities (in descending order): first priority - PUSCHs with aperiodic channel state information (A-CSI), as long as they overlap with Z; second priority - the earliest PUSCH slot based on the start of the slot. Then, if multiple PUSCHs still overlap with Z in the earliest PUSCH slot: the third priority - dynamically granted PUSCHs have a higher priority than PUSCHs configured by the corresponding ConfiguredGrantConfig or semiPersistentOnPUSCH; the fourth priority - PUSCHs on serving cells with smaller serving cell indices have a higher priority than PUSCHs on serving cells with larger serving cell indices; the fifth priority - earlier PUSCHs have a higher priority than later PUSCHs.

[0016] However, there can be some ambiguity regarding which PUCCH to use for multiplexing the UCI. For example, the UE can choose a PUCCH of sufficient size to transmit the multiplexed UCI, but multiple PUCCHs can have similar or sufficient sizes. For example, based on multiple bits in the merged UCI, the UE can find the corresponding PUCCH resource set (the new PUCCH resource set) and reinterpret the PUCCH resource indicator (PRI) associated with the PUCCH used for the UCI in the new PUCCH resource set, pointing to the new PUCCH resource in that set. Size ambiguity due to the loss of downlink control information (DCI) can also lead to ambiguity regarding the new PUCCH resource. In this example, the new PUCCH resource and the old PUCCH resource can end with different start and end symbols. Furthermore, as described, merging the UCI can be an iterative method. The new PUCCH resource set used for merging the UCI can overlap with another PUCCH resource set, which can trigger a new round of merging and end with a new floating PUCCH. Similarly, for example, due to the UE's loss of DCI reception, there may be ambiguity regarding which PUSCH should be used to carry the multiplexed UCI. In one example, as described above, ambiguity about which PUCCH to use may lead to ambiguity in the set of candidate PUSCHs for UCI multiplexing. Furthermore, the loss of a scheduled PUSCH in the DCI may create ambiguity in the candidate PUSCH set. Additionally, the rules that the UE verifies when selecting the final PUSCH to carry the combined UCI may be complex.

[0017] As described herein, a DCI may include parameters specifying whether a UCI should be multiplexed with an uplink control channel (e.g., a PUCCH) or an uplink shared channel (PUSCH), and the UE may multiplex the UCI with either the uplink control channel or the uplink shared channel accordingly based on the indication specified in the UCI. In one example, a DCI (e.g., certain DCI formats for uplink or downlink granting) may be extended to include a one-bit indicator for this purpose. For example, for multiplexing with a PUSCH, the multiplexing may be slot-based, such that a UCI occurring within a slot can be multiplexed with a PUSCH, or it may be boundary-based, such that a UCI corresponding to a PUCCH that overlaps with a PUSCH in time can be multiplexed with a PUSCH. For multiplexing with a PUCCH, for example, dedicated PUCCH resources may be available for the multiplexed UCI, or a dedicated resource pool may be specified from which PUCCH resources can be selected for the multiplexed UCI. In yet another example, for PUCCH multiplexing, the set indicator can be used to indicate which scheduled PUCCH resource is selected for PUCCH multiplexing. In another example, parameters in the DCI may include the downlink assignment index (DAI) indicated in the DCI. In this example, a DAI value of zero may indicate that the UCI is not multiplexed on the associated PUSCH, and a value greater than zero may indicate that the UCI is multiplexed on the associated PUSCH, and / or may indicate the number of UCI bits (e.g., the number of hybrid automatic repeat / request (HARQ)-acknowledge (ACK) bits that the UE wants to multiplex on the PUSCH).

[0018] The aspects described herein allow the DCI to indicate whether UCI is multiplexed with PUCCH or PUSCH. This allows the UE to perform multiplexing without having to execute iterative code to find the PUCCH for multiplexing UCI or complex rules to determine the PUSCH to carry the multiplexed UCI. For example, in the case where UCI is to be multiplexed with PUSCH, the DCI scheduling PUSCH can indicate that UCI should be multiplexed with the scheduled PUSCH. In any case, this can improve the UE's performance in determining on which resources to multiplex UCI and / or improve UCI multiplexing performance by resolving potential ambiguities between the timing of PUCCH and / or PUSCH resources used for UCI multiplexing.

[0019] The following will refer to Figures 1 to 9 To present the described features in more detail.

[0020] As used in this application, the terms "component," "module," "system," etc., are intended to include computer-related entities such as, but not limited to, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and the computing device itself can be components. One or more components may reside within a process and / or an execution thread, and components may be located in one computer and / or distributed across two or more computers. Furthermore, these components are executable from various computer-readable media on which various data structures are stored. Components can communicate via local and / or remote processes, such as based on signals having one or more data packets (e.g., data from a component that interacts with a local system, another component in a distributed system, and / or interacts with other systems across a network such as the Internet).

[0021] As used herein, a processor configured to perform or be operable to perform a plurality of actions, at least one processor, and / or one or more processors (alone or in combination) are intended to include at least two different processors capable of performing different subsets, overlapping subsets, or non-overlapping subsets of the plurality of actions, or a single processor capable of performing all of the plurality of actions. In a non-limiting example of a plurality of processors capable of performing different combinations of the plurality of actions, the description of a processor configured to perform or be operable to perform actions X, Y, and Z, at least one processor, and / or one or more processors may include at least a first processor configured to perform or be operable to perform a first subset of X, Y, and Z (e.g., performing X) and at least a second processor configured to perform or be operable to perform a second subset of X, Y, and Z (e.g., performing Y and Z). Alternatively, the first, second, and third processors may be configured to perform corresponding actions in actions X, Y, and Z, respectively. It should be understood that any combination of one or more processors may each be configured to perform or be operable to perform any one of the plurality of actions or any combination of the plurality of actions.

[0022] As used herein, a memory, at least one memory, and / or one or more memories (individually or in combination) configured to store or have thereon instructions executable by one or more processors for performing multiple actions are intended to include at least two different memories capable of storing different subsets, overlapping subsets, or non-overlapping subsets of instructions for performing the multiple actions, or a single memory capable of storing instructions for performing all of the multiple actions. In a non-limiting example of one or more memories (alone or in combination) capable of storing different subsets of instructions for performing different actions among the plurality of actions, the description of a memory configured or operable to store or thereon instructions for performing actions X, Y, and Z, at least one memory, and / or one or more memories may include at least a first memory configured or operable to store or thereon instructions for performing a first subset of X, Y, and Z (e.g., instructions for performing X), and at least a second memory configured or operable to store or thereon instructions for performing a second subset of X, Y, and Z (e.g., instructions for performing Y and Z). Alternatively, the first, second, and third memories may be configured to store or thereon a corresponding one of the first subset of instructions for performing X, the second subset of instructions for performing Y, and the third subset of instructions for performing Z. It should be understood that any combination of one or more memories may be configured or operable to store or have thereon any instruction or any combination of instructions executable by one or more processors to perform any of a plurality of actions or any combination of such actions. Furthermore, one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute instructions to perform the plurality of actions. For example, in the above non-limiting example of different subsets of instructions for performing actions X, Y, and Z, a first processor may be coupled to a first memory storing instructions for performing action X, at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first and second processors may combine to execute the respective subsets of instructions to complete the execution of actions X, Y, and Z. Alternatively, three processors may access one of three different memories, each storing instructions for performing action X, Y, or Z, and the three processors may combine to execute the respective subsets of instructions to complete the execution of actions X, Y, and Z. Alternatively, a single processor may execute instructions stored in a single memory or distributed across multiple memories to complete the execution of actions X, Y, and Z.

[0023] The technologies described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, single-carrier FDMA, and others. The terms "system" and "network" are often used interchangeably. CDMA systems implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High-Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. ™ UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-A Advanced (LTE-A) are newer versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the aforementioned systems and radio technologies, as well as in other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio frequency spectrum bands. However, the following description describes LTE / LTE-A systems for illustrative purposes, and the term LTE is used in most of the following description, although these technologies can also be applied beyond LTE / LTE-A applications (e.g., to fifth-generation (5G) New Radio (NR) networks or other next-generation communication systems).

[0024] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the various examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described in some examples may be combined in other examples.

[0025] Various aspects or features will be presented according to the system, which may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Combinations of these methods may also be used.

[0026] Figure 1 This is an illustration of an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells may include base stations. Small cells may include femtocells, picocells, and microcells. In this example, base station 102 may also include a gNB 180, as further described herein. In one example, according to aspects described herein, some nodes of the wireless communication system may have a modem 340 and a UE communication component 342 for multiplexing the UCI with an uplink control channel or an uplink shared channel based on parameters in the DCI. Furthermore, according to aspects described herein, some nodes may have a modem 440 and a BS communication component 442 for indicating whether the UCI is multiplexed in the uplink control channel or multiplexed with an uplink shared channel. Although UE 104 is shown as having modem 340 and UE communication component 342, and base station 102 / gNB 180 is shown as having modem 440 and BS communication component 442, this is an illustrative example, and essentially any node or any type of node may include modem 340 and UE communication component 342 and / or modem 440 and BS communication component 442 for providing the corresponding functionality described herein.

[0027] Base station 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via backhaul link 132 (e.g., using the S1 interface). Base station 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) can interface with 5GC 190 via backhaul link 184. Among other functions, base station 102 may also perform one or more of the following functions: user data delivery, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages. Base stations 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on backhaul link 134 (e.g., using an X2 interface). Backhaul link 134 can be wired or wireless.

[0028] Base station 102 can wirelessly communicate with one or more UEs 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide services to restricted groups (which may be referred to as a Closed Subscriber Group (CSG)). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may carry one or more carriers. Base station 102 / UE104 may use spectrum allocated per carrier up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) of bandwidth in carrier aggregation for transmissions in the DL and / or UL directions, totaling up to Yx MHz (e.g., corresponding to x component carriers). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetrical for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0029] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0030] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) to determine the availability of a channel before communication.

[0031] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR, and uses the same 5 GHz unlicensed spectrum as the Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network.

[0032] Base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, can operate in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has extremely high path loss and short range. The mmW base station 180 can be used with the UE 104 in conjunction with beamforming 182 to compensate for extremely high path loss and short range. The base station 102 mentioned herein may include the gNB 180.

[0033] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and BM-SC 170 are connected to the IP Service 176. The IP Service 176 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functions for MBMS user service dispatch and delivery. The BM-SC 170 can act as an entry point for content provider MBMS transmission, authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can allocate MBMS services to base station 102 belonging to a Broadcast-Specific Service Multicast Single Frequency Network (MBSFN) area, and is responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0034] 5GC 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 may be a control node handling signaling between UE 104 and 5GC 190. Generally, AMF 192 provides QoS streaming and session management. (For example, user Internet Protocol (IP) packets from one or more UEs 104 may be delivered via UPF 195. UPF 195 may provide UE IP address allocation and other functions for one or more UEs. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0035] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, transceiver base station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmit-Receive Point (TRP), or some other suitable terminology. Base station 102 provides UE 104 with access to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). IoT UEs may include Machine Type Communication (MTC) / Enhanced MTC (eMTC, also known as Category (CAT)-M or Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In this disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or are based on these technologies. For example, eMTC may include FeMTC (Further eMTC), eFeMTC (Enhanced Further eMTC), mMTC (Massive MTC), etc., and NB-IoT may include eNB-IoT (Enhanced NB-IoT), FeNB-IoT (Further Enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0036] The deployment of communication systems (such as 5G New Radio (NR) systems) can involve a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS, e.g., BS 102)), or one or more units (or components) performing base station functionality can be implemented in either a converged or decomposed architecture. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as converged base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0037] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs) (i.e., one or more central or centralized units). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0039] In the example, UE communication component 342 can multiplex the UCI in the uplink control channel or multiplex the UCI with the uplink shared channel based on parameters received from base station 102, gNB 180, or other network nodes. For example, parameters can be received in the DCI. In some examples, the DCI may correspond to resource granting for the uplink shared channel (e.g., uplink granting), but the DCI may also correspond to resource granting for the uplink control channel or one or more downlink channels. UE communication component 342 can accordingly multiplex the UCI in the uplink control channel or multiplex the UCI with the uplink shared channel based on the parameters. In the example, BS communication component 442 can send parameters to UE 104 (e.g., in the DCI). In another example, BS communication component 442 can also demultiplex the UCI with the uplink control channel or the uplink shared channel based on the parameters.

[0040] Figure 2 A diagram illustrating an example of a decomposed base station 200 architecture is shown. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0041] Each unit in the array (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals or transmit signals to one or more other units via wireless transmission media, or both.

[0042] In some aspects, the CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 210 can be implemented to communicate with the DU 230 for network control and signaling, as needed.

[0043] DU 230 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may, at least in part, host one or more of the following, depending on functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP): a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0044] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that at least partially hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) based on functional decomposition such as lower-layer functional decomposition, or both. In this architecture, the RU 240 can be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration allows the DU 230 and CU 210 to be implemented in cloud-based RAN architectures such as vRAN architectures.

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

[0046] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

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

[0048] Turn now Figures 3 to 9 The aspects are described with reference to one or more components and one or more methods that can perform the actions or operations described herein, wherein the aspects shown in dashed lines may be optional. Although the following text... Figure 5 and Figure 6 The operations described herein are presented in a specific order and / or performed as by example components; however, it should be understood that the order of actions and the components performing the actions may vary depending on the specific implementation. Furthermore, it should be understood that the actions, functions, and / or components described below may be performed by a specially programmed processor, a processor executing specially programmed software or a computer-readable medium, or any other combination of hardware and / or software components capable of performing the described actions or functions.

[0049] refer to Figure 3 An example of a specific implementation of UE 104 may include various components, some of which have already been described above and are further described herein, including components such as one or more processors 312 and one or more memories 316 and one or more transceivers 302 communicating via one or more buses 344. For example, one or more processors 312 may include a single processor or multiple processors configured to perform one or more functions described herein. For example, multiple processors may be configured to perform a specific subset of the set of functions described herein, such that multiple processors can perform the set of functions together. Similarly, for example, one or more memories 316 may include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein. For example, multiple memory devices may be configured to store instructions or parameters for performing a specific subset of the set of functions described herein, such that multiple memory devices can store instructions or parameters for the set of functions together. According to the aspects described herein, one or more processors 312, one or more memories 316, and one or more transceivers 302 may be combined to operate a modem 340 and / or UE communication component 342 for multiplexing UCI with uplink control channel or uplink shared channel based on parameters in DCI.

[0050] In one aspect, one or more processors 312 may include modem 340 and / or may be part of modem 340 using one or more modem processors. Therefore, various functions associated with UE communication component 342 may be included in modem 340 and / or processor 312, and in one aspect, may be performed by a single processor, while in other aspects, different functions may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 312 may include any or any combination of a modem processor, or baseband processor, or digital signal processor, or transmit processor, or receiver processor, or transceiver processor associated with transceiver 302. In other aspects, some features of one or more processors 312 and / or modem 340 associated with UE communication component 342 may be performed by transceiver 302.

[0051] Additionally, memory 316 may be configured to store data used herein and / or a local version of application 375, or one or more sub-components of UE communication component 342 and / or its sub-components executed by at least one processor 312. Memory 316 may include any type of computer-readable medium that can be used by a computer or at least one processor 312, such as random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when UE 104 is operating at least one processor 312 to execute UE communication component 342 and / or one or more sub-components of its sub-components, memory 316 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes and / or associated data defining UE communication component 342 and / or one or more sub-components of its sub-components.

[0052] Transceiver 302 may include at least one receiver 306 and at least one transmitter 308. Receiver 306 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code including instructions and stored in memory (e.g., a computer-readable medium). Receiver 306 may be, for example, a radio frequency (RF) receiver. In one aspect, receiver 306 may receive signals transmitted by at least one base station 102. Additionally, receiver 306 may process such received signals and may also obtain measurements of these signals, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter 308 may include hardware, firmware, and / or software code executable by a processor for transmitting data, the code including instructions and stored in memory (e.g., a computer-readable medium). Suitable examples of transmitter 308 may include, but are not limited to, RF transmitters.

[0053] Furthermore, in one aspect, UE 104 may include an RF front-end 388 that can operate communicatively with one or more antennas 365 and transceiver 302 to receive and transmit radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by UE 104. The RF front-end 388 may be connected to one or more antennas 365 and may include one or more low-noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for transmitting and receiving RF signals.

[0054] On one hand, the LNA 390 can amplify the received signal at the desired output level. On another hand, each LNA 390 can have a specified minimum gain value and a maximum gain value. On yet another hand, the RF front end 388 can use one or more switches 392 to select a particular LNA 390 and its specified gain value based on the desired gain value for a particular application.

[0055] Furthermore, for example, the RF front-end 388 may use one or more PAs 398 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 398 may have a specified minimum gain value and a maximum gain value. In another aspect, the RF front-end 388 may use one or more switches 392 to select a particular PA 398 and its specified gain value based on the desired gain value for a particular application.

[0056] Additionally, for example, the RF front-end 388 may use one or more filters 396 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 396 may be used to filter the output from a corresponding PA 398 to generate an output signal for transmission. In one aspect, each filter 396 may be connected to a specific LNA 390 and / or PA 398. In one aspect, the RF front-end 388 may use one or more switches 392 to select the transmission path or reception path using a specified filter 396, LNA 390, and / or PA 398 based on a configuration as specified by the transceiver 302 and / or processor 312.

[0057] Therefore, transceiver 302 can be configured to transmit and receive wireless signals via RF front end 388 through one or more antennas 365. In one aspect, the transceiver can be tuned to operate at a specified frequency, enabling UE 104 to communicate with, for example, one or more base stations 102 or with one or more cells associated with one or more base stations 102. In another aspect, for example, modem 340 can configure transceiver 302 to operate at a specified frequency and power level based on UE configuration of UE 104 and communication protocols used by modem 340.

[0058] In one aspect, modem 340 may be a multi-band, multi-mode modem capable of processing digital data and communicating with transceiver 302, enabling the use of transceiver 302 to transmit and receive digital data. In another aspect, modem 340 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In another aspect, modem 340 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 340 may control one or more components of UE 104 (e.g., RF front-end 388, transceiver 302) to transmit and / or receive signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the modem's mode and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with UE 104, such as information provided by the network during cell selection and / or cell reselection.

[0059] In one aspect, the UE communication component 342 may optionally include: a DCI processing component 352 for receiving and / or processing DCI received from a network node; and / or a UCI multiplexing component 354 for multiplexing UCI in an uplink control channel or multiplexing UCI with an uplink shared channel based on parameters in the DCI.

[0060] On one hand, processor 312 may correspond to a combination Figure 9 The UE describes one or more processors in the processor. Similarly, memory 316 may correspond to the combination of Figure 9 The UE describes one or more memories.

[0061] Reference Figure 4 An example of a specific implementation of base station 102 (e.g., base station 102 and / or gNB 180, as described above) may include various components, some of which have already been described above, but also include components such as one or more processors 412 and one or more memories 416 communicating via one or more buses 444, and one or more transceivers 402. For example, one or more processors 412 may include a single processor or multiple processors configured to perform one or more functions described herein. For example, multiple processors may be configured to perform a specific subset of the set of functions described herein, such that multiple processors can perform the set of functions together. Similarly, for example, one or more memories 416 may include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein. For example, multiple memory devices may be configured to store instructions or parameters for performing a specific subset of the set of functions described herein, such that multiple memory devices can store instructions or parameters for the set of functions together. Based on the aspects described herein, one or more processors 412, one or more memories 416, and one or more transceivers 402 may be combined to operate a modem 440 and / or BS communication component 442 for demultiplexing the UCI with the uplink control channel or uplink shared channel based on parameters in the DCI.

[0062] Transceiver 402, receiver 406, transmitter 408, one or more processors 412, memory 416, application 475, bus 444, RF front end 488, LNA 490, switch 492, filter 496, PA 498 and one or more antennas 465 may be the same as or similar to the corresponding components of UE 104 as described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0063] In one aspect, the BS communication component 442 may optionally include: a DCI generation component 452 for generating a DCI for transmission to the UE, wherein the DCI may include parameters indicating whether the UCI is multiplexed with the uplink control channel or the uplink shared channel; and / or a UCI demultiplexing component 454 for indicating whether the UCI is multiplexed in the uplink control channel or with the uplink shared channel.

[0064] On one hand, processor 412 may correspond to a combination Figure 9 The base station described in the text refers to one or more processors. Similarly, memory 416 may correspond to the combination of... Figure 9 The base station in the text describes one or more memories.

[0065] Figure 5 A flowchart illustrating an example of a method 500 for multiplexing UCI in an uplink control channel or multiplexing UCI with an uplink shared channel, according to the aspects described herein. Figure 6 A flowchart illustrating an example of a method 600 for indicating whether UCI is multiplexed in the uplink control channel or shared with the uplink channel, according to the aspects described herein. In the example, UE 104 can use Figure 1 and / or Figure 3 One or more of the components described in the document are used to perform the action. Figure 5 The functionality described in method 500 is illustrated. In the example, nodes that utilize communication resources to schedule UE104 (such as base station 102 or gNB 180, a monolithic base station or gNB, a portion of a split base station or gNB, a UE in sidelink communication, etc.) can use... Figure 1 and / or Figure 4 One or more of the components described in the document are used to perform the action. Figure 6 The functions described in method 600 are shown. For ease of explanation, methods 500 and 600 are described together; however, methods 500 and 600 do not need to be executed together and can actually be executed independently using separate devices.

[0066] In method 600, at block 602, a DCI including parameters can be generated, the parameters having values ​​indicating whether the UCI should be multiplexed with an uplink control channel or an uplink shared channel. On one hand, DCI generation component 452 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can generate a DCI including parameters having values ​​indicating whether the UCI should be multiplexed with an uplink control channel (e.g., PUCCH) or an uplink shared channel (e.g., PUSCH). For example, DCI generation component 452 can generate a DCI for UE 104, wherein the DCI may include a scheduling DCI, which may include resource granting (e.g., uplink granting or downlink granting) for resources used by UE 104 when transmitting or receiving wireless communications.

[0067] In the example, DCI generation component 452 can determine whether UE 104 should multiplex the UCI in the PUCCH or with the PUSCH based on the PUCCH and / or PUSCH resources being scheduled for UE 104. For example, DCI generation component 452 can determine whether a PUCCH resource scheduled for UE 104 is sufficient to carry the multiplexed UCI expected to be transmitted by UE 104 (e.g., including the UCI for HARQ-ACK feedback sent to the downlink to UE 104). In the example (e.g., if there is no scheduled PUCCH resource sufficient to carry the multiplexed UCI), DCI generation component 452 can determine that the UCI should be multiplexed on the PUSCH instead of the PUCCH. In either case, DCI generation component 452 can generate a DCI for UE 104 (e.g., to schedule PUCCH or PUSCH resources) that includes parameters indicating whether the UCI is multiplexed on the PUCCH or PUSCH. In one example, the DCI generation component 452 can also determine which PUCCH or PUSCH to use to send the multiplexed UCI, and can include the parameters of the PUCCH or PUSCH determined by the scheduler in the DCI.

[0068] In method 600, at block 604, a DCI can be transmitted to the UE. On one hand, a DCI generation component 452 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can transmit the DCI to the UE 104. For example, the DCI generation component 452 can transmit the DCI to the UE 104 via a downlink control channel (e.g., physical downlink control channel (PDCCH)), a downlink shared channel (e.g., physical downlink shared channel (PDSCH)), etc. The DCI may include a DCI formatted based on a DCI format indicated in a wireless communication technology (e.g., a DCI format in 5G NR or similar technologies).

[0069] In method 500, at block 502, a DCI including parameters can be received from the network node. These parameters have values ​​indicating whether the UCI should be multiplexed with an uplink control channel or an uplink shared channel. On one hand, a DCI processing component 352 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can receive and / or process the DCI including parameters from the network node (e.g., base station 102). These parameters have values ​​indicating whether the UCI should be multiplexed with an uplink control channel (e.g., PUCCH) or an uplink shared channel (e.g., PUSCH). For example, the DCI processing component 352 can receive the DCI in a PDCCH or PDSCH transmitted by the network node.

[0070] In method 500, at block 504, the UCI can be multiplexed with either the uplink control channel or the uplink shared channel based on a value. In one aspect, the UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex the UCI with either the uplink control channel (e.g., PUCCH) or the uplink shared channel (e.g., PUSCH) based on the value of a parameter. For example, UE 104 may have multiple UCI values ​​or instances (e.g., multiple HARQ-ACK feedback bits for multiple downlink transmissions) to send to the network node.

[0071] When the parameter value indicates that the UCI should be multiplexed with the uplink control channel, the UCI multiplexing component 354 can multiplex various UCI values ​​or instances in one or more PUCCH resources. In one example, as described in further detail herein, the UCI multiplexing component 354 can select the PUCCH resource for multiplexing the UCI based on the DCI with parameters, based on another parameter indicating the PUCCH resource, based on the PUCCH resource calculated using an algorithm, etc., as described in the various examples herein.

[0072] When the parameter value indicates that the UCI is to be multiplexed with the uplink shared channel, the UCI multiplexing component 354 can multiplex various UCI values ​​or instances in one or more PUSCH resources. In one example, as described in further detail herein, the UCI multiplexing component 354 can select the PUSCH resource for multiplexing the UCI based on the DCI with parameters, based on another parameter indicating the PUSCH resource, based on the PUSCH resource calculated using an algorithm, etc., as described in the various examples herein.

[0073] In method 500, at block 506, one of an uplink control channel multiplexed with UCI or an uplink shared channel may be transmitted. In one aspect, UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may transmit one of an uplink control channel multiplexed with UCI or an uplink shared channel. For example, UCI multiplexing component 354 may transmit an uplink control channel (e.g., PUCCH) or an uplink shared channel (e.g., PUSCH) on associated resources, which may be sent to and / or received by network nodes, as described above and in other examples herein.

[0074] In the various examples described herein, the parameters used in the DCI may include a single bit indicator, which may be a newly defined bit, a reserved bit, or some other existing bit in the DCI format, with one value indicating that the UCI is multiplexed on the PUCCH and another value indicating that the UCI is multiplexed on the PUSCH. In some examples, additional auxiliary information may also be provided to multiplex the UCI or to determine the PUCCH resource on which the UCI is multiplexed. In other examples, the parameters used in the DCI may include a DAI already defined in the DCI format, where a value of zero may indicate that the UCI is multiplexed on the PUCCH, and other values ​​may indicate that multiple UCIs are multiplexed on the PUSCH, and / or other values ​​may also be used for their intended purpose, as further described herein.

[0075] In the example, the network node can also receive and demultiplex the UCI based on parameters indicated in the DCI. For ease of explanation, this document describes demultiplexing in conjunction with multiplexing; however, the aspects described herein do not require the execution or configuration of both multiplexing and demultiplexing functions. For example, in method 600, optionally at block 606, a UCI multiplexed with either an uplink control channel or an uplink shared channel can be received from the UE. In one aspect, a UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can receive a UCI multiplexed with either an uplink control channel (e.g., PUCCH) or an uplink shared channel (e.g., PUSCH) from the UE (e.g., UE 104). For example, the UCI demultiplexing component 454 can receive a PUCCH or PUSCH based on resources scheduled for transmitting the PUCCH or PUSCH as indicated in the DCI sent to UE 104. In addition, for example, the UCI demultiplexing component 454 may understand or determine which PUCCH or PUSCH includes a multiplexed UCI based on its generated DCI, which includes parameters indicating whether the UCI is multiplexed with a PUCCH or a PUSCH, or based on other methods of calculating or determining which PUCCH or PUSCH resource includes a multiplexed UCI, as described herein.

[0076] In this example, in method 600, optionally at block 608, the UCI can be demultiplexed with either the uplink control channel or the uplink shared channel based on a value. On one hand, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex the UCI with either the uplink control channel or the uplink shared channel based on the value of a parameter. Furthermore, in method 600, optionally at block 610, the UCI can be processed. On one hand, the BS communication component 442 (e.g., in conjunction with processor 412, memory 416, transceiver 402, etc.) can process the UCI. For example, the BS communication component 442 can process various HARQ-ACK feedback values ​​indicated in the multiplexed UCI to determine whether to retransmit any downlink communication, or it can process other various UCI values ​​that can be multiplexed (e.g., Channel State Information (CSI), Scheduling Request (SR), etc.).

[0077] In some examples, if the parameters include a bit indicator in the DCI indicating that the UCI is multiplexed with the PUSCH (e.g., a bit value "1"), the UCI multiplexing component 354 may multiplex the UCI on the PUSCH scheduled by the DCI. Otherwise, the UCI multiplexing component 354 may not multiplex the UCI on that PUSCH. In the example, if the PUSCH scheduled in the time slot does not have a parameter indicating that the UCI is multiplexed with the PUSCH (e.g., a bit value "1"), the UCI multiplexing component 354 may multiplex the UCI on the PUCCH. If the UCI multiplexing component 354 detects at least one PUSCH (e.g., in the time slot) with a parameter indicating that the UCI is multiplexed, the UCI multiplexing component 354 may use time slot-based multiplexing or PUSCH boundary-based multiplexing.

[0078] For example, when multiplexing a UCI at block 504, optionally at block 508, the UCI can be multiplexed on a PUCCH scheduled or configured in the same time slot as the uplink shared channel. In one aspect, UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex a UCI on a PUCCH scheduled or configured in the same time slot as the uplink shared channel (referred to as time-slot-based multiplexing). For example, given a DCI for scheduling a PUSCH that includes parameter values ​​indicating the multiplexing of a UCI on the PUSCH, UCI multiplexing component 354 can multiplex a UCI scheduled on a PUCCH resource in the same time slot, instead of transmitting it together with a PUSCH scheduled by a DCI including the parameter values. This can reduce ambiguity due to a lost DCI (e.g., if the DCI is lost, the UCI may not be reusable).

[0079] In the example, when demultiplexing the UCI at block 608, optionally at block 610, the UCI can be demultiplexed for a PUCCH scheduled or configured in the same time slot as the uplink shared channel. On one hand, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex the UCI for a PUCCH scheduled or configured in the same time slot as the uplink shared channel. For example, given a DCI for scheduling a PUSCH that includes parameter values ​​indicating the multiplexing of the UCI on the PUSCH, the UCI demultiplexing component 454 can demultiplex the UCI scheduled on the PUCCH resource in the same time slot as the PUSCH with the PUSCH.

[0080] For example, when multiplexing UCI at block 504, optionally at block 510, UCI can be multiplexed on PUCCHs that overlap temporally with the uplink shared channel. In one aspect, UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex UCI on PUCCHs that overlap temporally (e.g., in the time domain) with the uplink shared channel (referred to as boundary-based multiplexing). For example, given a DCI for scheduling PUSCHs that includes parameter values ​​indicating the multiplexing of UCI on the PUSCHs, UCI multiplexing component 354 can multiplex UCIs scheduled on PUCCH resources that overlap temporally with PUSCHs scheduled by a DCI including parameter values. This can reduce unnecessary multiplexing of UCIs.

[0081] In the example, when demultiplexing the UCI at block 608, optionally at block 612, the UCI can be demultiplexed for PUCCHs that time-overlap with the uplink shared channel. On one hand, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex the UCI for PUCCHs that time-overlap with the uplink shared channel. For example, given a DCI for scheduling a PUSCH that includes parameter values ​​indicating the multiplexing of the UCI on the PUSCH, the UCI demultiplexing component 454 can demultiplex the UCI scheduled on PUCCH resources that time-overlap with the PUSCH. Figure 7 and Figure 8 Examples of slot-based multiplexing and boundary-based multiplexing are shown in the figure.

[0082] Figure 7Examples of resource allocations 700 and 710 for multiplexing UCI on an uplink shared channel, according to various aspects described herein, are illustrated. In resource allocation 700, a network node can schedule time and frequency resources for uplink communication for the UE, including PUCCH resource allocation for HARQ-ACK 702, PUCCH resource allocation for CSI 704, and resource allocation for PUSCH 706. In one example, PUSCH 706 may be scheduled by DCI, which includes parameter values ​​indicating the multiplexing of UCI on PUSCH 706. UCI multiplexing component 354 can accordingly determine, for slot-based multiplexing, the UCI to be scheduled for transmission in the PUCCH resource allocation for HARQ-ACK 702 and the PUCCH resource allocation for CSI 704, and multiplexed with PUSCH 706.

[0083] In resource allocation 710, the network node can schedule time and frequency resources for uplink communication for the UE, including PUCCH resource allocation for HARQ-ACK 712, PUCCH resource allocation for CSI 714, and resource allocation for PUSCH 716. In one example, PUSCH 716 can be scheduled by DCI including parameter values ​​indicating the multiplexing of UCIs on PUSCH 716. UCI multiplexing component 354 can accordingly determine, for boundary-based multiplexing, the UCIs scheduled for transmission in the PUCCH resource allocation for CSI 714 to be multiplexed with PUSCH 716 transmissions. UE 104 can transmit the UCIs scheduled for transmission in the PUCCH resource allocation for HARQ-ACK 712 separately.

[0084] Figure 8Examples of resource allocations 800 and 810 for multiplexing UCI over multiple uplink shared channels are illustrated according to the aspects described herein. In resource allocation 800, a network node can schedule time and frequency resources for uplink communication for the UE, including a PUCCH resource allocation for HARQ-ACK 802, a PUCCH resource allocation for CSI 804, and two resource allocations for PUSCH 806 and PUSCH 808. In one example, PUSCH 806 and PUSCH 808 can be scheduled by DCI including parameter values ​​indicating the multiplexing of UCI on PUSCH 806 and PUSCH 808. The UCI multiplexing component 354 can accordingly determine, for slot-based multiplexing, the UCI to be scheduled for transmission in the PUCCH resource allocation for HARQ-ACK 802 and the PUCCH resource allocation for CSI 804, multiplexing it with PUSCH 806 transmission and PUSCH 808 transmission, such that each UCI is repeated and multiplexed on each PUSCH in multiple PUSCHs.

[0085] In resource allocation 810, the network node can schedule time and frequency resources for uplink communication for the UE, including PUCCH resource allocation for HARQ-ACK 812, PUCCH resource allocation for CSI 814, and two resource allocations for PUSCH 816 and PUSCH 818. In one example, PUSCH 816 and PUSCH 818 can be scheduled by DCI including parameter values ​​indicating the multiplexing of UCI on PUSCH 816 and PUSCH 818. UCI multiplexing component 354 can accordingly determine, for boundary-based multiplexing, the UCI to be scheduled for transmission in the PUCCH resource allocation for HARQ-ACK 812 multiplexed with PUSCH 816, and the UCI to be scheduled for transmission in the PUCCH resource allocation for CSI 814 multiplexed with PUSCH 818. In these examples, UCI rate matching, resource element (RE) mapping, etc., can follow the beta factor used for each individual PUSCH 816 and PUSCH 818.

[0086] Furthermore, in the examples, as described above and further herein, UCI multiplexing with an uplink shared channel can be limited to UCIs scheduled in PUCCH resources that are in the same component carrier (CC) or in-band consecutive carrier aggregation (CA) as the PUSCH resource with which the UCI is to be multiplexed. For example, for PUCCH and PUSCH transmissions across different CCs (and / or not in-band consecutive CAs), UE 104 can perform parallel transmissions of PUCCH and PUSCH across CCs. Thus, in one example, multiplexing a UCI at block 504 and / or demultiplexing a UCI at block 608 can be further based on (e.g., in addition to determinations corresponding to slot-based or boundary-based multiplexing) determining that the UCI to be multiplexed / demultiplexed is scheduled in a PUCCH resource in the same CC or in-band consecutive CA as the corresponding PUSCH resource.

[0087] When the parameter value indicates that the UCI is multiplexed with the uplink control channel, the UCI multiplexing component 354 can multiplex various UCI values ​​or instances in one or more PUCCH resources. In one example, as described further in detail herein, the UCI multiplexing component 354 can select the PUCCH resource for multiplexing the UCI based on a DCI with parameters, based on another parameter indicating the PUCCH resource, based on calculating the PUCCH resource using an algorithm, etc., as described in the various examples herein. In the example, the DCI with parameters indicating the multiplexing of the UCI may correspond to the DCI of the PDSCH corresponding to the scheduled UCI. In one example, the determination of the PUCCH resource for multiplexing the UCI can be a non-iterative process decoupled from the UCI size.

[0088] In method 500, optionally at block 512, resources for the uplink control channel of the UCI can be selected for multiplexing. In one aspect, the UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can select resources for the uplink control channel of the UCI (e.g., PUCCH resources) for multiplexing. For example, as described, UCIs scheduled in multiple different PUCCH resources can be multiplexed in a single PUCCH resource for transmission. For example, multiplexed UCIs may correspond to UCIs scheduled for transmission in the same time slot. The UCI multiplexing component 354 can select resources based on various considerations or determinations, such as selecting resources dedicated to UCI multiplexing, selecting resources from a pool of resources dedicated to UCI multiplexing, etc.

[0089] For example, UCI multiplexing component 354 can receive an indication of a dedicated PUCCH for UCI multiplexing from a network node. For example, DCI processing component 352 can process the DCI to obtain the PRI for the scheduled PUCCH resource, thereby determining the frequency and / or time resources of the PUCCH resource. In other examples, UE communication component 342 can obtain the RRC configuration of the PUCCH resource. In any case, for configured or scheduled PUCCH resources, UCI multiplexing component 354 determines whether the PUCCH resources overlap, and if so, UCI multiplexing component 354 can select a dedicated resource for multiplexing the UCI from the time-overlapping PUCCH resources. In some examples, as similarly described above regarding PUSCH multiplexing, UCI multiplexing component 354 can multiplex a UCI scheduled in a time slot with a dedicated resource (time slot-based multiplexing), or multiplex a UCI scheduled in a time-overlapping PUCCH resource with a dedicated resource (boundary-based multiplexing).

[0090] In one example, when multiplexing a UCI at block 504, optionally at block 514, multiple UCIs within a time slot can be multiplexed with an uplink control channel. On one hand, UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex multiple UCIs within a time slot with an uplink control channel (e.g., in a PUCCH resource associated with one of the UCIs). In another example, when multiplexing a UCI at block 504, optionally at block 516, portions of multiple UCIs within a time slot that time-overlap with the uplink control channel can be multiplexed with the uplink control channel (e.g., time slot-based multiplexing). On one hand, UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex portions of multiple UCIs that time-overlap with uplink control channels (e.g., selected PUCCH resources) within a time slot with uplink control channels (e.g., in PUCCH resources associated with one of the UCIs) (e.g., boundary-based multiplexing). In any case, in dedicated PUCCH resources, the number of resource blocks (RBs) in the frequency domain can increase with the size of the combined UCI payload and / or can be limited by the maximum number of RBs configured by the network.

[0091] In method 600, optionally at block 614, the resources for the uplink control channel with which the UCI is demultiplexed can be selected. In one aspect, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can select the resources (e.g., PUCCH resources) with which the UCI is demultiplexed. For example, as described, UCIs scheduled in multiple different PUCCH resources can be demultiplexed with a single received PUCCH resource. For example, the multiplexed UCIs may correspond to UCIs scheduled for transmission in the same time slot. The UCI demultiplexing component 454 can select resources based on various considerations or determinations, such as selecting resources dedicated to UCI multiplexing, selecting resources from a pool of resources dedicated to UCI multiplexing, etc.

[0092] For example, the UCI demultiplexing component 454 can send an indication to the UE for a dedicated PUCCH for UCI multiplexing. For configured or scheduled PUCCH resources, the UCI demultiplexing component 454 determines whether the PUCCH resources overlap, and if so, the UCI demultiplexing component 454 can select a dedicated resource for demultiplexing UCI from the temporally overlapping PUCCH resources.

[0093] In one example, when demultiplexing a UCI at block 606, optionally at block 616, multiple UCIs within a time slot can be demultiplexed with the uplink control channel. On one hand, UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex multiple UCIs within a time slot with the uplink control channel (e.g., in the PUCCH resource associated with one of the UCIs). In another example, when demultiplexing a UCI at block 606, optionally at block 618, portions of multiple UCIs within a time slot that time-overlap with the uplink control channel can be demultiplexed with the uplink control channel (e.g., where the UCIs are time-slot-based multiplexing). On one hand, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex portions of multiple UCIs that overlap temporally with the uplink control channel (e.g., the selected PUCCH resource) within a time slot with the uplink control channel (e.g., in the PUCCH resource associated with one of the UCIs) (e.g., where the UCI is based on boundary multiplexing).

[0094] In another example, a resource pool of dedicated PUCCH resources for UCI multiplexing can be defined. In this example, when selecting resources at block 512, DCI processing component 352 can obtain parameters from the DCI that schedules the PDSCH to determine whether PUCCH multiplexing is indicated. If not, the UE can anticipate that there are no time-overlapping scheduled PUCCH resources and can therefore use the legacy resource pool for non-overlapping PUCCHs to transmit UCI using time-division multiplexing (TDM). However, if the parameters do indicate PUCCH multiplexing, UCI multiplexing component 354 can select a PUCCH resource for multiplexing UCI from the dedicated PUCCH resource pool for UCI multiplexing based on the PRI indicated in the DCI. As described above, for example, UCI multiplexing component 354 can use slot-based multiplexing or boundary-based multiplexing (e.g., based on the slot or boundary of the selected PUCCH resource) to multiplex UCI in the selected PUCCH resource. In this example, the start symbol, end symbol, and start PRB of the selected PUCCH resource may remain unchanged with the size of the merged UCI payload, while the number of RBs (e.g., in terms of frequency) may increase with the size of the merged UCI payload. In one example, if the DCI does not include UCI multiplexing parameters, the UCI multiplexing component 354 may use a default resource (e.g., the first resource) from the dedicated resource pool to multiplex the UCI. The UCI demultiplexing component 454 may perform a similar selection of PUCCH resources from the dedicated PUCCH resource pool for demultiplexing the UCI.

[0095] In another example, the set indicator may be included in the DCI of the PUCCH or the PDSCH of the scheduled PUCCH. As described, in 5G NR, four sets of PUCCH resource pools are defined for transmitting UCI. In the example, when selecting resources at block 512, the DCI processing component 352 can obtain the set indicator (e.g., a 2-bit set indicator capable of indicating one of the four PUCCH resource pools), and the UCI multiplexing component 354 can select PUCCH resources based on the set indicator. For example, the UCI multiplexing component 354 can select PUCCH resources by selecting a resource pool based on the set indicator and then selecting resources from the resource pool based on the PRI. Similarly, for example, the DCI generation component 452 can set the set indicator in the DCI, and the UCI demultiplexing component 454 can demultiplex the UCI with PUCCH resources from the PUCCH resource pool indicated by the set indicator and PUCCH resources within the pool indicated by the PRI.

[0096] In another example, the parameter could be an uplink DAI as defined in 5G NR, which could be used such that a value of zero indicates the multiplexing of UCI on the PUCCH, and a value greater than zero indicates the multiplexing of UCI on the PUSCH and / or the use of the uplink DAI value for its intended purpose (e.g., to determine the number of HARQ-ACK bits to be multiplexed on the PUSCH). For example, the functionality of the UL DAI defined in 5G NR could be to indicate the number of HARQ-ACK bits (e.g., 0, 1, 2, 3) that the UE should multiplex on the PUSCH, thereby determining the multiplexing of UCI on the PUSCH. If UCI is not multiplexed on the PUSCH, the UL DAI for that PUSCH can be obsolete. According to the aspects described herein, the UL DAI can be used in advance to determine whether UCI is multiplexed on the PUCCH or the PUSCH, and if the UCI is transmitted on the PUSCH, to determine how many HARQ-ACK bits the UE should multiplex.

[0097] For example, DCI processing component 352 can process DCI to check the DAI of scheduled PUSCHs in a time slot. If none of the DAIs is greater than zero, UCI multiplexing can multiplex the UCI on the PUCCH resource (e.g., on the PUCCH resource of the primary CC (e.g., CC1)). If the PUCCH resource does not overlap temporally with PUSCH resources on the same CC, UCI multiplexing component 354 can transmit the multiplexed UCI on the PUCCH resource. If the PUCCH resource overlaps temporally with PUSCH resources on the same CC, UCI multiplexing component 354 may discard the multiplexed UCI transmission due to a scheduling error. If at least one UL DAI is greater than zero, UCI multiplexing component 354 can multiplex the UCI with the corresponding PUSCH. For example, if only one PUSCHDAI is greater than zero, UCI multiplexing component 354 can multiplex the UCI with that PUSCH. If multiple PUSCHs have a DAI greater than zero, the UCI multiplexing component 354 can repeatedly multiplex UCI (e.g., HARQ-ACK and / or CSI) on multiple PUSCHs.

[0098] In this regard, for example, when multiplexing the UCI at block 504, optionally at block 518, the UCI can be multiplexed with the uplink control channel based on the fact that none of the multiple DCIs has a DAI greater than zero. On one hand, the UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex the UCI with the uplink control channel based on the fact that none of the multiple DCIs has a DAI greater than zero. As described, the DCI processing component 352 can obtain the DAI in the DCI for each PUSCH to determine whether any DCI has a DAI greater than zero. Furthermore, as described, the UCI multiplexing component 354 can select a PUCCH on the primary CC for transmitting the multiplexed UCI.

[0099] Similarly, for example, when demultiplexing the UCI at block 606, optionally at block 620, the UCI can be demultiplexed with the uplink control channel based on the fact that none of the multiple DCIs has a DAI greater than zero. In one aspect, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex the UCI with the uplink control channel based on the fact that none of the multiple DCIs has a DAI greater than zero. As described, the DCI generation component 452 can generate DCIs for the PUSCH, which may not have a DAI greater than zero, and the UCI demultiplexing component 454 can determine to demultiplex the UCI with the PUCCH based on the determination that none of the DCIs has a DAI greater than zero. Furthermore, as described, the UCI multiplexing component 354 can select the PUCCH on the primary CC for demultiplexing the UCI.

[0100] In another example, when multiplexing a UCI at block 504, optionally at block 520, the UCI can be multiplexed with the uplink shared channel based on at least one of the multiple DCIs having a DAI greater than zero. In one aspect, the UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex the UCI with the uplink shared channel based on at least one of the multiple DCIs having a DAI greater than zero. As described, the DCI processing component 352 can obtain the DAI in the DCI for each PUSCH to determine whether any DCI has a DAI greater than zero, and if so, the UCI multiplexing component 354 can multiplex the UCI with that PUSCH / those PUSCHs.

[0101] Similarly, for example, when demultiplexing the UCI at block 606, optionally at block 622, the UCI can be demultiplexed with the uplink control shared channel based on at least one of the multiple DCIs having a DAI greater than zero. In one aspect, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex the UCI with the uplink shared channel based on at least one of the multiple DCIs having a DAI greater than zero. As described, the DCI generation component 452 can generate DCIs for the PUSCH, which may have a DAI greater than zero, and the UCI demultiplexing component 454 can determine to demultiplex the UCI with the PUSCH based on determining which corresponding DCIs have a DAI greater than zero.

[0102] In another example, when multiplexing the UCI at block 504, optionally at block 522, the UCI can be multiplexed with a number of feedback bits indicated by the DAI. In one aspect, the UCI multiplexing component 354 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) can multiplex the UCI with a number of feedback bits indicated by the DAI. Similarly, for example, when demultiplexing the UCI at block 606, optionally at block 624, the UCI can be demultiplexed with a number of feedback bits indicated by the DAI. In one aspect, the UCI demultiplexing component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) can demultiplex the UCI with a number of feedback bits indicated by the DAI. In one example, DAI code points can be remapped based on using DAI=0 to indicate UCI multiplexing with PUCCH (or otherwise not multiplexing UCI on PUSCH).

[0103] For example, the DAI defined in 5G NR can be two bits, used to represent four values ​​(e.g., 0, 1, 2, 3) using modulo-4 arithmetic. In 5G NR, each value can be represented by the number of bits to be multiplexed as the indicated value plus 4. n ,in n It can be a non-negative integer (e.g., 0, 1, 2, ...). According to the aspects described herein, when using DAI=0 to indicate UCI multiplexing with PUCCH, the code point value of DAI can be remapped to not use zero (e.g., using modulo-3 arithmetic, such that the value indicates the value indicated by the multiplexing plus 3). n For example, DAI=1 can indicate the multiplexing of 1, 4, 7, ... feedback bits, DAI=2 can indicate the multiplexing of 2, 5, 8, ... feedback bits, and DAI=3 can indicate the multiplexing of 3, 6, 9, ... feedback bits.

[0104] In another example, to improve the robustness of UL DAI against lost DL DCIs (e.g., where modulo 3 cannot be recovered if 3 consecutive DL DCIs are lost), the UL DAI field can be extended to 3 bits, which allows modulo 8 operations. In this example, DAI=0 can be used to indicate UCI multiplexing on the PUCCH (or otherwise not multiplexing UCI on the PUSCH), DAI=1 can indicate multiplexing of 1, 8, 15, ... feedback bits, DAI=2 can indicate multiplexing of 2, 9, 16, ... feedback bits, DAI=3 can indicate multiplexing of 3, 10, 17, ... feedback bits, DAI=4 can indicate multiplexing of 4, 11, 18, ... feedback bits, DAI=5 can indicate multiplexing of 5, 12, 19, ... feedback bits, DAI=6 can indicate multiplexing of 6, 13, 20, ... feedback bits, and DAI=7 can indicate multiplexing of 7, 14, 21, ... feedback bits. The number of feedback bits to be multiplexed can be determined based on the number of downlink grants received and the associated number of DAIs.

[0105] In any case, the UCI multiplexing component 354 can use the DAI value and appropriate modulo 3 (or modulo 8) arithmetic to determine the number of feedback bits to be multiplexed with the PUSCH based on the DAI value, where the DAI value is greater than zero, as described above. Similarly, the UCI demultiplexing component 454 can use the DAI value and appropriate modulo 3 (or modulo 8) arithmetic to determine the number of feedback bits to be demultiplexed with the PUSCH based on the DAI value, where the DAI value is greater than zero, as described above.

[0106] Figure 9 This is a block diagram of a MIMO communication system 900 including base station 102 and UE 104. The MIMO communication system 900 can be illustrated by reference. Figure 1 The wireless communication access network 100 is described in various aspects. Base station 102 may be a reference. Figure 1 Examples of various aspects of the described base station 102 are provided. Base station 102 may be equipped with antennas 934 and 935, and UE 104 may be equipped with antennas 952 and 953. In the MIMO communication system 900, base station 102 can transmit data simultaneously through multiple communication links. Each communication link may be referred to as a "layer," and the "rank" of the communication link indicates the number of layers used for communication. For example, in a 2x2 MIMO communication system in which base station 102 transmits two "layers," the rank of the communication link between base station 102 and UE 104 is two.

[0107] At base station 102, a transmit (Tx) processor 920 can receive data from a data source. The transmit processor 920 can process the data. The transmit processor 920 can also generate control symbols or reference symbols. A transmit MIMO processor 930 can perform spatial processing (e.g., pre-decoding, if applicable) on the data symbols, control symbols, or reference symbols, and can provide output symbol streams to transmit modulators / demodulators 932 and 933. Each modulator / demodulator 932 to 933 can process (e.g., for OFDM, etc.) its corresponding output symbol stream to obtain an output sample stream. Each modulator / demodulator 932 to 933 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In one example, the DL signal from modulators / demodulators 932 and 933 can be transmitted via antennas 934 and 935, respectively.

[0108] UE 104 can be used as a reference. Figure 1 and Figure 3 Examples of various aspects of the described UE 104. At UE 104, UE antennas 952 and 953 can receive DL signals from base station 102 and can provide the received signals to modulators / demodulators 954 and 955, respectively. Each modulator / demodulator 954 to 955 can adjust (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain an input sample. Each modulator / demodulator 954 to 955 can further process (e.g., for OFDM, etc.) the input sample to obtain a received symbol. A MIMO detector 956 can obtain the received symbol from modulators / demodulators 954 and 955, perform MIMO detection on the received symbol (if applicable), and provide the detected symbol. A receive (Rx) processor 958 can process (e.g., demodulate, deinterleave, and decode) the detected symbol to provide decoded data for UE 104 to the data output and to provide decoded control information to processor 980 or memory 982.

[0109] In some cases, the processor 980 may execute stored instructions to instantiate the UE communication component 342 (see, for example...). Figure 1 and Figure 3 ).

[0110] On the uplink (UL), at UE 104, the transmitting processor 964 can receive and process data from a data source. The transmitting processor 964 can also generate reference symbols for a reference signal. Symbols from the transmitting processor 964 can be pre-decoded (if applicable) by the transmitting MIMO processor 966, further processed by modulators / demodulators 954 and 955 (e.g., for single-carrier FDMA, etc.), and transmitted to base station 102 according to communication parameters received from base station 102. At base station 102, the UL signal from UE 104 can be received by antennas 934 and 935, processed by modulators / demodulators 932 and 933, detected (if applicable) by MIMO detector 936, and further processed by the receiving processor 938. The receiving processor 938 can provide decoded data to the data output and processor 940 or memory 942.

[0111] In some cases, processor 940 may execute stored instructions to instantiate BS communication component 442 (see, for example...) Figure 1 and Figure 4 ).

[0112] Components of UE 104 may be implemented individually or collectively using one or more ASICs, which are adapted to perform some or all of the applicable functions in hardware. Each of the indicated modules may be a component for performing one or more functions related to the operation of the MIMO communication system 900. Similarly, components of base station 102 may be implemented individually or collectively using one or more application-specific integrated circuits (ASICs), which are adapted to perform some or all of the applicable functions in hardware. Each of the indicated components may be a component for performing one or more functions related to the operation of the MIMO communication system 900.

[0113] The following aspects are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein without limitation.

[0114] Aspect 1 is a method for performing wireless communication at a UE, the method comprising: receiving from a network node a DCI including parameters having a value indicating whether the UCI is to be multiplexed with an uplink control channel or an uplink shared channel; having the UE multiplex the UCI with one of the uplink control channel or the uplink shared channel based on the value; and transmitting the uplink control channel or the uplink shared channel multiplexed with the UCI.

[0115] In aspect 2, the method according to aspect 1 includes: wherein the parameter includes a single bit indicator having a value indicating whether the UCI is to be multiplexed with the uplink control channel or the uplink shared channel.

[0116] In aspect 3, the method according to any one of aspects 1 or 2 includes: wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and wherein multiplexing the UCI with the uplink shared channel includes multiplexing the UCI on a PUCCH scheduled or configured in the same time slot as the uplink shared channel.

[0117] In aspect 4, the method according to any one of aspects 1 to 3 includes: wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and wherein multiplexing the UCI with the uplink shared channel includes multiplexing the UCI on a PUCCH that overlaps with the uplink shared channel in time.

[0118] In aspect 5, the method according to any one of aspects 1 to 4 includes: wherein the parameter indicates that a UCI is to be multiplexed with the uplink shared channel, and wherein multiplexing the UCI includes: multiplexing a plurality of UCIs with each of the plurality of uplink shared channels on a PUCCH scheduled or configured in the same time slot as the plurality of uplink shared channels.

[0119] In aspect 6, the method according to any one of aspects 1 to 5 includes: wherein the parameter indicates that a UCI is to be multiplexed with the uplink shared channel, and wherein multiplexing the UCI includes: multiplexing the UCI scheduled or configured on a first PUCCH that overlaps with the uplink shared channel in time slot with the uplink shared channel in the time slot; and multiplexing a second UCI scheduled or configured on a second PUCCH that overlaps with the second uplink shared channel in time slot with the second uplink shared channel.

[0120] In aspect 7, the method according to any one of aspects 1 to 6 includes: wherein the multiplexing of the UCI with the uplink shared channel is based at least in part on the UCI and the uplink shared channel being associated with the same CC or with different CCs in in-band consecutive carrier aggregation.

[0121] In aspect 8, the method according to any one of aspects 1 to 7 includes: wherein multiplexing the UCI includes multiplexing the UCI with the uplink control channel, wherein the parameter indicates that the UCI is to be multiplexed with the uplink control channel, and wherein the uplink control channel is dedicated to UCI multiplexing.

[0122] In aspect 9, the method according to aspect 8 includes: wherein multiplexing the UCI with the uplink control channel dedicated to UCI multiplexing is based at least in part on detecting multiple UCIs within a time slot.

[0123] In aspect 10, the method according to aspect 9 includes: wherein multiplexing the UCI with the uplink control channel dedicated to UCI multiplexing includes: multiplexing the plurality of UCIs within the time slot with the uplink control channel.

[0124] In aspect 11, the method according to any one of aspects 9 or 10 includes: wherein multiplexing the UCI with the uplink control channel dedicated to UCI multiplexing includes: multiplexing portions of the plurality of UCIs that time overlap with the uplink control channel within the time slot with the uplink control channel.

[0125] In aspect 12, the method according to any one of aspects 1 to 11 includes: wherein multiplexing the UCI includes: multiplexing the UCI with the uplink control channel, wherein the parameter indicates that the UCI is to be multiplexed with the uplink control channel; and selecting resources for the uplink control channel from an uplink control channel resource pool dedicated to UCI multiplexing.

[0126] In aspect 13, the method according to aspect 12 includes: wherein the resource for the uplink control channel is selected based on a Physical Uplink Control Channel Resource Indicator (PRI) value specified in the DCI.

[0127] In aspect 14, the method according to any one of aspects 12 or 13 includes: wherein multiplexing the UCI with the uplink control channel includes: multiplexing a plurality of UCIs within a time slot with the uplink control channel.

[0128] In aspect 15, the method according to any one of aspects 12 to 14 includes: wherein multiplexing the UCI with the uplink control channel includes: multiplexing portions of a plurality of UCIs that overlap with the uplink control channel in time within a time slot with the uplink control channel.

[0129] In aspect 16, the method according to any one of aspects 12 to 15 includes: wherein the resource for the uplink control channel is selected based on a set indicator value and a PRI value specified in the DCI, wherein the set indicator value indicates one uplink control channel resource set in a plurality of uplink control channel resource sets, and the PRI value indicates the uplink control channel in the one uplink control channel resource set of the plurality of uplink control channel resource sets.

[0130] In aspect 17, the method according to any one of aspects 1 to 16 includes: wherein the parameter is an uplink downlink assignment index (DAI), and wherein an uplink DAI with a value of zero indicates that the UCI is not multiplexed with the uplink shared channel, and wherein an uplink DAI with a value greater than zero indicates that the UCI is multiplexed with the uplink shared channel.

[0131] In aspect 18, the method according to any one of aspects 1 to 17 includes: wherein receiving the DCI includes receiving a plurality of DCIs for a plurality of uplink shared channels, and wherein multiplexing the UCI includes: multiplexing the UCI with the uplink control channel based at least in part on the fact that none of the plurality of DCIs has an uplink DAI greater than zero, or multiplexing the UCI with the uplink shared channel based at least in part on the fact that at least one of the plurality of DCIs has an uplink DAI greater than zero.

[0132] In aspect 19, the method according to aspect 18 includes: wherein the uplink shared channel is one of the at least one DCI having an uplink DAI greater than zero among the plurality of DCIs.

[0133] In aspect 20, the method according to any one of aspects 18 or 19 includes: wherein multiplexing the UCI with the uplink shared channel includes: multiplexing the UCI with a number of feedback bits indicated at least in part by the DAI, wherein the number of feedback bits is indicated at least in part by the DAI using a modulo operation based on the maximum value of the DAI minus 1.

[0134] In aspect 21, the method according to any one of aspects 1 to 20 includes: wherein the DCI corresponds to one of downlink grant or uplink grant.

[0135] Aspect 22 is a method for wireless communication at a network node, the method comprising: generating a DCI including parameters having values ​​indicating whether the UCI should be multiplexed with an uplink control channel or an uplink shared channel; and transmitting the DCI to a UE.

[0136] In aspect 23, the method according to aspect 22 includes: wherein the parameter includes a single bit indicator having a value indicating whether the UCI is to be multiplexed with the uplink control channel or the uplink shared channel.

[0137] In aspect 24, the method according to any one of aspects 22 or 23 includes: wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and receiving the UCI multiplexed with the uplink shared channel from the UE, and demultiplexing the UCI with a PUCCH scheduled or configured in the same time slot as the uplink shared channel based on the parameter.

[0138] In aspect 25, the method according to any one of aspects 22 to 24 includes: wherein the parameter indicates that a UCI is to be multiplexed with the uplink shared channel, and receiving a UCI multiplexed with the uplink shared channel from the UE, and demultiplexing the UCI with a PUCCH that overlaps with the uplink shared channel in time based on the parameter.

[0139] In aspect 26, the method according to any one of aspects 22 to 25 includes: wherein the parameter indicates that a UCI is to be multiplexed with the uplink shared channel, and receiving the UCI multiplexed with the uplink shared channel from the UE, and demultiplexing the plurality of UCIs with each of the plurality of uplink shared channels based on the parameter on a PUCCH scheduled or configured in the same time slot as the plurality of uplink shared channels.

[0140] In aspect 27, the method according to any one of aspects 22 to 26 includes: wherein the parameter indicates that a UCI is to be multiplexed with the uplink shared channel, and receiving from the UE a UCI multiplexed with either the uplink control channel or the uplink shared channel; demultiplexing the UCI scheduled or configured on a first PUCCH in a time slot that overlaps with the uplink shared channel in the time slot with the uplink shared channel in the time slot based on the parameter; and demultiplexing a second UCI scheduled or configured on a second PUCCH in a time slot that overlaps with the second uplink shared channel in the time slot with the second uplink shared channel based on the parameter.

[0141] In aspect 28, the method according to any one of aspects 22 to 27 includes: receiving from the UE a UCI multiplexed with one of the uplink control channel or the uplink shared channel; and demultiplexing the UCI with the uplink shared channel based on the parameters, at least in part based on the fact that the UCI and the uplink shared channel are associated with the same CC or different CCs in in-band continuous carrier aggregation.

[0142] In aspect 29, the method according to any one of aspects 22 to 28 includes: receiving from the UE a UCI multiplexed with one of the uplink control channel or the uplink shared channel; and demultiplexing the UCI with the uplink control channel based on the parameters, wherein the parameters indicate that the UCI is to be multiplexed with the uplink control channel, and wherein the uplink control channel is dedicated to UCI multiplexing.

[0143] In aspect 30, the method according to aspect 29 includes: wherein demultiplexing the UCI with the uplink control channel dedicated to UCI multiplexing is based at least in part on scheduling multiple UCIs within a time slot.

[0144] In aspect 31, the method according to aspect 30 includes: wherein demultiplexing the UCI with the uplink control channel dedicated to UCI multiplexing includes: demultiplexing the plurality of UCIs within the time slot with the uplink control channel.

[0145] In aspect 32, the method according to any one of aspects 30 or 31 includes: wherein demultiplexing the UCI with the uplink control channel dedicated to UCI multiplexing includes: demultiplexing portions of the plurality of UCIs that time overlap with the uplink control channel within the time slot with the uplink control channel.

[0146] In aspect 33, the method according to any one of aspects 22 to 32 includes: receiving from the UE a UCI multiplexed with the uplink control channel; and demultiplexing the UCI with the uplink control channel based on the parameters, wherein the parameters indicate that the UCI is to be multiplexed with the uplink control channel, and wherein the uplink control channel is in resources selected from an uplink control channel resource pool dedicated to UCI multiplexing.

[0147] In aspect 34, the method according to aspect 33 includes: wherein the DCI includes a PRI value indicating the resource to be selected from the uplink control channel resource pool dedicated to UCI multiplexing.

[0148] In aspect 35, the method according to any one of aspects 33 or 34 includes: wherein demultiplexing the UCI with the uplink control channel includes: demultiplexing a plurality of UCIs within a time slot with the uplink control channel.

[0149] In aspect 36, the method according to any one of aspects 33 to 35 includes: wherein demultiplexing the UCI with the uplink control channel includes: demultiplexing portions of a plurality of UCIs that overlap with the uplink control channel in time slots with the uplink control channel.

[0150] In aspect 37, the method according to any one of aspects 33 to 36 includes: wherein the DCI includes a set indicator value and a PRI value, wherein the set indicator value indicates an uplink control channel resource set in a plurality of uplink control channel resource sets, and the PRI value indicates the uplink control channel in the one uplink control channel resource set in the plurality of uplink control channel resource sets.

[0151] In aspect 38, the method according to any one of aspects 22 to 37 includes: wherein the parameter is an uplink DAI, and wherein an uplink DAI of zero indicates multiplexing the UCI with the uplink control channel, and wherein an uplink DAI of greater than zero indicates multiplexing the UCI with the uplink shared channel.

[0152] In aspect 39, the method according to any one of aspects 22 to 38 includes: wherein transmitting the DCI includes transmitting a plurality of DCIs for a plurality of uplink shared channels, and receiving a UCI multiplexed with an uplink control channel from the UE, and demultiplexing the UCI with the uplink control channel based on the parameters, at least in part based on the fact that none of the plurality of DCIs has an uplink downlink assignment index (DAI) greater than zero, or demultiplexing the UCI with the uplink shared channel based on the parameters, at least in part based on the fact that at least one of the plurality of DCIs has an uplink DAI greater than zero.

[0153] In aspect 40, the method according to aspect 39 includes: wherein the uplink shared channel is one of the at least one DCI having an uplink DAI greater than zero among the plurality of DCIs.

[0154] In aspect 41, the method according to any one of aspects 39 or 40 includes: wherein demultiplexing the UCI with the uplink shared channel includes: demultiplexing the UCI with a number of feedback bits indicated at least in part by the DAI, wherein the number of feedback bits is indicated at least in part by the DAI using a modulo operation based on the maximum value of the DAI minus 1.

[0155] In aspect 42, the method according to any one of aspects 22 to 41 includes: wherein the DCI corresponds to one of downlink grant or uplink grant.

[0156] Aspect 43 is an apparatus for wireless communication, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and operable, when executed by the one or more processors, to cause the apparatus to perform any of the methods described in aspects 1 to 42.

[0157] Aspect 44 is an apparatus for wireless communication, the apparatus including components for performing any of the methods described according to aspects 1 to 42.

[0158] Aspect 45 is one or more computer-readable media, the computer-readable medium including code executable by one or more processors for wireless communication, the code including code for performing any of the methods described according to aspects 1 to 42.

[0159] The above detailed description, illustrated in conjunction with the accompanying drawings, describes examples and does not represent only examples that can be implemented or fall within the scope of the claims. The term "example" as used in this description means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0160] Information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0161] The various exemplary frames and components described in connection with the disclosure herein may be implemented or executed using specially programmed devices, such as, but not limited to, processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, designed to perform the functions described herein. While a specially programmed processor may be a microprocessor, in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0162] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or code on or transmitted via a non-transitory computer-readable medium. Other examples and specific implementations fall within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using hardware, firmware, hardwired, software executed by a specially programmed processor, or any combination of these. Features implementing the functions may also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations. Additionally, as used herein, including in the claims, the word "or" used in a list of entries beginning with "at least one of" indicates a distributed list, such that a list such as "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0163] Computer-readable media includes both computer storage media and communication media, with the latter including any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of carrying or storing desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. As used herein, disks and optical discs include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically copy data magnetically, while optical discs use lasers to copy data optically. Combinations of the above are also included within the scope of computer-readable media.

[0164] The prior description of this disclosure is provided to enable those skilled in the art to implement or use it. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Furthermore, while elements of the described aspects and / or embodiments are described or claimed in the singular, plural forms are contemplated unless explicitly stated otherwise. Additionally, unless otherwise stated, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication, the apparatus comprising: transceiver; One or more memories, the one or more memories being configured to store instructions individually or in combination; and One or more processors, the one or more processors being communicatively coupled to the one or more memories, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the device to: Receive downlink control information (DCI) from network nodes, including parameters having values ​​indicating whether uplink control information (UCI) should be multiplexed with the uplink control channel or the uplink shared channel; Based on the value, the UCI is multiplexed with either the uplink control channel or the uplink shared channel; as well as Transmit one of the uplink control channel multiplexed with the UCI or the uplink shared channel.

2. The apparatus of claim 1, wherein the parameter includes a single bit indicator having a value indicating whether the UCI is to be multiplexed with the uplink control channel or the uplink shared channel.

3. The apparatus of claim 1, wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCI on a Physical Uplink Control Channel (PUCCH) scheduled or configured in the same time slot as the uplink shared channel.

4. The apparatus of claim 1, wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCI on a physical uplink control channel (PUCCH) that overlaps with the uplink shared channel in time.

5. The apparatus of claim 1, wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the plurality of UCIs with each of the plurality of uplink shared channels on a Physical Uplink Control Channel (PUCCH) scheduled or configured in the same time slot as the plurality of uplink shared channels.

6. The apparatus of claim 1, wherein the parameter indicates that the UCI is to be multiplexed with the uplink shared channel, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to: multiplex the UCI scheduled or configured on a first physical uplink control channel (PUCCH) that overlaps with the uplink shared channel in a time slot with the uplink shared channel in the time slot; and multiplex the second UCI scheduled or configured on a second PUCCH that overlaps with the second uplink shared channel in the time slot with the second uplink shared channel.

7. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCI with the uplink shared channel at least in part based on the UCI and the uplink shared channel being associated with the same component carrier (CC) or with different CCs in in-band continuous carrier aggregation.

8. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCI with the uplink control channel, wherein the parameters indicate that the UCI is to be multiplexed with the uplink control channel, and wherein the uplink control channel is dedicated to UCI multiplexing.

9. The apparatus of claim 8, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCIs with the uplink control channel dedicated to UCI multiplexing, at least in part, based on detecting a plurality of UCIs within a time slot.

10. The apparatus of claim 9, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the plurality of UCIs within the time slot with the uplink control channel.

11. The apparatus of claim 9, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex portions of the plurality of UCIs that time-overlap with the uplink control channel within the time slot with the uplink control channel.

12. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCI with the uplink control channel, wherein the parameters indicate that the UCI is to be multiplexed with the uplink control channel, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to select resources for the uplink control channel from an uplink control channel resource pool dedicated to UCI multiplexing.

13. The apparatus of claim 12, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to select the resources for the uplink control channel based on a Physical Uplink Control Channel Resource Indicator (PRI) value specified in the DCI.

14. The apparatus of claim 12, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex a plurality of UCIs within a time slot with the uplink control channel.

15. The apparatus of claim 12, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex portions of a plurality of UCIs that time-overlap with the uplink control channel within a time slot with the uplink control channel.

16. The apparatus of claim 12, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to select the resources for the uplink control channel based on a set indicator value and a physical uplink control channel resource indicator (PRI) value specified in the DCI, wherein the set indicator value indicates one uplink control channel resource set in a plurality of uplink control channel resource sets, and the PRI value indicates the uplink control channel in the one uplink control channel resource set of the plurality of uplink control channel resource sets.

17. The apparatus of claim 1, wherein the parameter is an uplink downlink assignment index (DAI), and wherein an uplink DAI of zero indicates that the UCI is not multiplexed with the uplink shared channel, and wherein an uplink DAI of greater than zero indicates that the UCI is multiplexed with the uplink shared channel.

18. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive a plurality of DCIs for a plurality of uplink shared channels, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to perform one of the following: multiplexing the UCI with the uplink control channel based at least in part on the fact that none of the plurality of DCIs has an uplink downlink assignment index (DAI) greater than zero, or multiplexing the UCI with the uplink shared channel based at least in part on the fact that at least one of the plurality of DCIs has an uplink DAI greater than zero.

19. The apparatus of claim 18, wherein the uplink shared channel is one of the at least one DCI having an uplink DAI greater than zero among the plurality of DCIs.

20. The apparatus of claim 18, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to multiplex the UCI with a number of feedback bits at least partially indicated by the DAI, wherein the number of feedback bits is at least partially indicated by the DAI using a modulo operation based on the maximum value of the DAI minus 1.

21. The apparatus of claim 1, wherein the DCI corresponds to either downlink grant or uplink grant.

22. An apparatus for wireless communication, the apparatus comprising: transceiver; One or more memories, the one or more memories being configured to store instructions individually or in combination; and One or more processors, the one or more processors being communicatively coupled to the one or more memories, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the device to: Generate downlink control information (DCI) including parameters, the parameters having values ​​indicating whether uplink control information (UCI) should be multiplexed with the uplink control channel or the uplink shared channel; as well as The DCI is sent to the user equipment (UE).

23. The apparatus of claim 22, wherein the parameter includes a single bit indicator having a value indicating whether the UCI is to be multiplexed with the uplink control channel or the uplink shared channel.

24. The apparatus of claim 22, wherein the parameter indicates that the UCI is to share a channel with the uplink, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to: Receives a UCI multiplexed with the uplink shared channel from the UE; and The UCI is demultiplexed with the Physical Uplink Control Channel (PUCCH) scheduled or configured in the same time slot as the uplink shared channel based on the parameters.

25. The apparatus of claim 22, wherein the parameter indicates that the UCI is to share a channel with the uplink, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to: Receives a UCI multiplexed with the uplink shared channel from the UE; and The UCI is demultiplexed with the Physical Uplink Control Channel (PUCCH) that overlaps with the uplink shared channel in time, based on the parameters.

26. The apparatus of claim 22, wherein the parameter indicates that the UCI is to share a channel with the uplink, and wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to: Receives a UCI multiplexed with the uplink shared channel from the UE; and On the Physical Uplink Control Channel (PUCCH) scheduled or configured in the same time slot as the multiple uplink shared channels, the multiple UCIs are demultiplexed with each of the multiple uplink shared channels based on the parameters.

27. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive downlink control information (DCI) from network nodes, including parameters having values ​​indicating whether uplink control information (UCI) should be multiplexed with the uplink control channel or the uplink shared channel; The UE multiplexes the UCI with either the uplink control channel or the uplink shared channel based on the value. as well as Transmit one of the uplink control channel multiplexed with the UCI or the uplink shared channel.

28. The method of claim 27, wherein the parameter includes a single bit indicator having a value indicating whether the UCI is to be multiplexed with the uplink control channel or the uplink shared channel.

29. A method for wireless communication at a network node, the method comprising: Generate downlink control information (DCI) including parameters, the parameters having values ​​indicating whether uplink control information (UCI) should be multiplexed with the uplink control channel or the uplink shared channel; as well as The DCI is sent to the user equipment (UE).

30. The method of claim 29, wherein the parameter includes a single bit indicator having a value indicating whether the UCI is to be multiplexed with the uplink control channel or the uplink shared channel.

Images