Multiplexing uplink control information on uplink shared channel transmissions

Abstract

Methods, systems, and devices for wireless communications are described. User equipment (UE) may receive an uplink grant that schedules uplink shared channel transmissions of a first length. Subsequently, the UE may determine the actual lengths of transmissions that may differ from each other and from the scheduled lengths (e.g., due to conditions of the communication environment, such as the location of slot boundaries). The UE may also identify uplink control information to be multiplexed on the uplink shared channel (e.g., when a scheduled transmission overlaps with the control channel or based on an uplink grant for the uplink control information). The UE may multiplex the uplink control information on the uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the transmissions, and transmit the uplink control information in at least one of the transmissions.

Description

Technology Field

[0001] This patent application is U.S. Patent Application No. 17 / 001,326, filed by YANG et al. on August 24, 2020, with the title of the invention "MULTIPLEXING UPLINK CONTROL INFORMATION ON UPLINK SHARED CHANNEL TRANSMISSIONS"; U.S. Provisional Patent Application No. 62 / 892,460, filed by YANG et al. on August 27, 2019, with the title of the invention "MULTIPLEXING UPLINK CONTROL INFORMATION ON UPLINK SHARED CHANNEL TRANSMISSIONS"; Claiming priority to U.S. provisional patent application No. 62 / 976,964, filed by YANG et al. on February 14, 2020, with the title of the invention "MULTIPLEXING UPLINK CONTROL INFORMATION ON UPLINK SHARED CHANNEL TRANSMISSIONS", each of the said applications has been assigned to the assignee of the present invention.

[0002] The following relates to wireless communications in general, and more specifically to multiplexing uplink control information for uplink shared channel transmissions. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include 4th generation (4G) systems, e.g., LTE (Long Term Evolution) systems, LTE-A (LTE-Advanced) systems, or LTE-A Pro systems, and 5th generation (5G) systems, which may be referred to as NR (New Radio) systems. These systems may utilize technologies such as CDMA (code division multiple access), TDMA (time division multiple access), FDMA (frequency division multiple access), OFDMA (orthogonal frequency division multiple access), or DFT-S-OFDM (discrete Fourier transform-spread-orthogonal frequency division multiplexing). A wireless multiple access communication system may include one or more base stations or one or more network access nodes that each simultaneously support communication for a number of communication devices, which may otherwise be known as UEs (user equipment).

[0004] In some instances, a UE may transmit multiple times on the same uplink shared channel. In some cases, multiple transmissions may be scheduled as iterations to increase reliability. In other cases, multiple transmissions may occur because a scheduled transmission is split into more than one actual transmission. Uplink control information (UCI) may be multiplexed on the uplink shared channel for each of the multiple transmissions. Each of the multiple transmissions will have an associated coding scheme when multiplexing the UCI on the uplink shared channel. However, in certain situations, multiple coding schemes used for transmission iterations may make it difficult for the base station to combine and receive the UCI from the multiple iterations.

[0005] The described technologies relate to improved methods, systems, devices, and apparatus that support multiplexing uplink control information for uplink shared channel transmissions. Generally, the described technologies provide that when multiplexing uplink control information (UCI) over uplink shared channel transmissions of different lengths, a user equipment (UE) can prevent changes in coding schemes. The UE may receive an uplink grant scheduling transmissions of a first length (e.g., in downlink control information (DCI) or via radio resource control (RRC) signaling). Subsequently, the UE may determine the actual lengths of transmissions that may differ from each other and from the scheduled lengths (e.g., due to conditions of the communication environment, such as the location of slot boundaries). The UE may also identify the UCI to be multiplexed over the uplink shared channel (e.g., when the scheduled transmission overlaps with the physical uplink control channel (PUCCH) or based on the uplink grant for the UCI). The UE can multiplex the UCI on an uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the transmits, and transmit the UCI on at least one of the transmits.

[0006] A wireless communication method is described. The method may include receiving an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols; identifying, based on the uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols assigned to the uplink shared channel —; identifying a UCI to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity; multiplexing the UCI on the uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity; and transmitting the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0007] A device for wireless communications is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. Instructions may be executable by a processor to cause the device to receive an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols, and based on the uplink grant, to identify a first uplink transmission opportunity and a second uplink transmission opportunity to which the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols assigned to the uplink shared channel —, to identify a UCI to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity, to multiplex the UCI on the uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity, and to transmit the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0008] Other devices for wireless communications are described. The device may include means for receiving an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols; means for identifying, based on the uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which at least the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity comprises a second number of symbols different from the first number of symbols assigned to the uplink shared channel —; means for identifying a UCI to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity; means for multiplexing the UCI on the uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity; and means for transmitting the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0009] A non-transient computer-readable medium for storing codes for wireless communications is described. The code may include instructions executable by a processor to receive an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols, and based on the uplink grant, to identify a first uplink transmission opportunity and a second uplink transmission opportunity to which the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols assigned to the uplink shared channel —, to identify a UCI to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity, to multiplex the UCI on the uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity, and to transmit the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0010] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for assigning a first amount of resource elements to a UCI in a first uplink transmission opportunity based on a rate-matching method and a coding method, and assigning a second amount of resource elements to a UCI in a second uplink transmission opportunity based on a rate-matching method and a coding method, and the second amount may be different from the first amount.

[0011] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining that at least one uplink shared channel in a first uplink transmission opportunity or a second uplink transmission opportunity comprises a first number of symbols assigned to the uplink shared channel, and that at least one uplink shared channel in the first uplink transmission opportunity or a second uplink transmission opportunity comprises a second number of symbols different from the first number of symbols, multiplexing a UCI on at least one uplink shared channel comprising the first number of symbols, and inhibiting multiplexing a UCI on at least one uplink shared channel comprising the second number of symbols.

[0012] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining that an uplink shared channel includes an ultra-reliable low-latency communications (URLC) transmission, determining that a UCI includes a first part and a second part, and multiplexing the first part of the UCI with the URLLC transmission.

[0013] Some examples of the methods, devices, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining the payload size of a UCI and determining the amount of resource elements for transmitting the UCI.

[0014] Some examples of the methods, devices, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining whether the payload size of a UCI may exceed a threshold, and determining a reference amount of resource elements for the UCI.

[0015] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining an output sequence length based on a reference amount of resource elements and a rate-matching method, encoding a UCI into a sequence of coded bits using polar coding—the length of the sequence of coded bits corresponds to the output sequence length—determining an amount of coded bits based on an amount of resource elements for transmitting the UCI, and generating said amount of coded bits based on the sequence of coded bits.

[0016] In some examples of the methods, apparatuses and non-transient computer-readable media described herein, generating the amount of coded bits may include determining that the amount of coded bits may be greater than the output sequence length, and operations, features, means, or instructions for cyclically expanding the sequence of coded bits.

[0017] In some examples of the methods, apparatuses and non-transient computer-readable media described herein, a reference amount of resource elements for a UCI comprises: a first amount of resource elements in a scheduled transmission of an uplink shared channel; a second amount of resource elements in a first uplink transmission opportunity; a third amount of resource elements in a second uplink transmission opportunity; the greater of the first amount, the second amount, and the third amount; or the smaller of the first amount, the second amount, and the third amount.

[0018] In some examples of the methods, devices, and non-transient computer-readable media described herein, the rate-matching method may be determined based on the payload size of the UCI and the reference amount of resource elements for the UCI.

[0019] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining that the payload size of a UCI may be less than a threshold, encoding the UCI into a sequence of encoded bits using polar coding, and modulating symbols into a sequence of encoded bits based on a rate-matching method.

[0020] In some examples of the methods, devices, and non-transient computer-readable media described herein, multiplexing may include operations, features, means, or instructions for mapping modulated symbols to resource elements of an uplink shared channel.

[0021] In some examples of the methods, apparatuses and non-transient computer-readable media described herein, the amount of resource elements for the UCI comprises a first amount of resource elements in a scheduled transmission of an uplink shared channel, a second amount of resource elements in a first uplink transmission opportunity, a third amount of resource elements in a second uplink transmission opportunity, or the smaller of the first amount, the second amount, and the third amount.

[0022] In some examples of the methods, devices, and non-transient computer-readable media described above, the uplink sharing channel includes PUSCH.

[0023] Some examples of the methods, devices, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for receiving an uplink grant in DCI or via RRC signaling.

[0024] In some examples of the methods, devices, and non-transient computer-readable media described herein, the UCI includes ACK (acknowledgment), NACK (negative acknowledgment), CSI, A-CSI (aperiodic CSI), or a combination thereof.

[0025] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, A-CSI may be scheduled by a second uplink grant. In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the uplink grant includes a second uplink grant.

[0026] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining that an uplink transmission opportunity overlaps with a PUCCH, wherein the PUCCH includes a UCI, and the uplink transmission opportunity corresponds to at least one of a first uplink transmission opportunity or a second uplink transmission opportunity.

[0027] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for multiplexing ACK, NACK, CSI, or a combination thereof on an uplink shared channel over an uplink transmission opportunity overlapping with PUCCH.

[0028] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include determining that at least one uplink shared channel in a first uplink transmission opportunity or a second uplink transmission opportunity satisfies a resource constraint based on the amount of resource elements in the uplink shared channel — the resource constraint includes an amount of resource elements for transmitting a UCI that is not greater than the amount of resource elements in the uplink shared channel — and operations, features, means, or instructions for multiplexing an ACK, NACK, CSI, or a combination thereof on at least one uplink shared channel that satisfies the resource constraint.

[0029] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the amount of resource elements in an uplink shared channel excludes the amount of resource elements in one or more symbols including a demodulation reference signal, a phase-tracking reference signal, or both.

[0030] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include determining that each uplink shared channel in a first uplink transmission opportunity or a second uplink transmission opportunity satisfies a resource constraint based on the amount of resource elements in the uplink shared channel — the resource constraint includes an amount of resource elements for transmitting a UCI that is not greater than the amount of resource elements in the uplink shared channel — and operations, features, means, or instructions for multiplexing an ACK, NACK, CSI, or a combination thereof on at least one uplink shared channel that satisfies the resource constraint.

[0031] Some examples of the methods, apparatuses and non-transient computer-readable media described herein may further include operations, features, means, or instructions for multiplexing A-CSI on an uplink shared channel to a selected transmission opportunity among a first uplink transmission opportunity or a second uplink transmission opportunity, and UCI includes A-CSI.

[0032] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the selected uplink transmission opportunity may be the last uplink transmission opportunity comprising a first number of symbols assigned to an uplink shared channel, as identified based on an uplink grant.

[0033] In some examples of the methods, apparatuses and non-transient computer-readable media described herein, the selected uplink transmission opportunity may be the last uplink transmission opportunity identified based on an uplink grant, and the last uplink transmission opportunity includes a first number of symbols assigned to an uplink shared channel or a second number of symbols different from the first number of symbols assigned to an uplink shared channel. Brief explanation of the drawing

[0034] FIGS. 1 and 2 illustrate examples of wireless communication systems that support multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure.

[0035] FIG. 3 illustrates examples of communication scenarios that support multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure.

[0036] FIG. 4 illustrates an example of a process flow that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure.

[0037] FIGS. 5 and 6 illustrate block diagrams of devices that support multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure.

[0038] FIG. 7 illustrates a block diagram of a communication manager that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure.

[0039] FIG. 8 illustrates a diagram of a system including a device that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure.

[0040] FIGS. 9 through 11 illustrate flowcharts illustrating methods that support multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. Specific details for implementing the invention

[0041] User equipment (UE) of a wireless communication system may transmit the same data to a base station multiple times to increase reliability (e.g., to ensure that the base station receives information). For example, the UE may utilize PUSCH (physical uplink shared channel) repetitions, where the UE repeats the transmission of the same data multiple times over the PUSCH. These repetitions may be scheduled or may result from the UE splitting a scheduled transmission into multiple transmissions. Regardless of how the repetitions occur, the UE may multiplex the PUSCH with UCI (uplink control information). The UE may determine rate-matching and coding schemes for multiplexing the UCI with each PUSCH transmission based on the actual payload size of the UCI (e.g., the number of resource elements used to transmit the UCI) and the actual length of that specific PUSCH transmission (e.g., the number of symbols). This means that when the lengths of the PUSCH transmissions vary, the UE uses different coding schemes for different PUSCH transmissions. However, inconsistencies in coding schemes can adversely affect the base station's ability to receive and combine UCIs from multiple transmissions.

[0042] According to the techniques described herein, a UE can prevent changes in coding schemes between PUSCH transmissions of different lengths by multiplexing a UCI with the PUSCH in each transmission to maintain the same rate-matching and coding scheme across multiple PUSCH transmissions even when the lengths of the PUSCH transmissions vary. In one implementation, the UE may receive an uplink grant scheduling PUSCH repetitions of a first length (e.g., x symbols) (e.g., in downlink control information (DCI) or via radio resource control (RRC) signaling). Subsequently, the UE may determine the actual lengths of the PUSCH transmissions, which may differ from each other and from the scheduled lengths (e.g., due to conditions of the communication environment, such as the location of slot boundaries). The UE may also identify a UCI to be multiplexed with the PUSCH (e.g., when the scheduled PUSCH overlaps with a physical uplink control channel (PUCCH) or based on an uplink grant for the UCI). The UE multiplexes the PUSCH and UCI to maintain the same rate-matching scheme and the same coding scheme for each of the PUSCH iterations, and can transmit the UCI in at least one of the PUSCH transmissions.

[0043] Aspects of the present disclosure are initially described in the context of one or more wireless communication systems. Aspects of the present disclosure are also described in the context of systems and process flows illustrating the operations of one or more devices in one or more wireless communication systems. Aspects of the present disclosure are further illustrated and described with reference to device drawings, system drawings, and flowcharts relating to multiplexing uplink control information for uplink shared channel transmissions.

[0044] FIG. 1 illustrates an example of a wireless communication system (100) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. The wireless communication system (100) may include one or more base stations (105), one or more UEs (115), and a core network (130). In some examples, the wireless communication system (100) may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system (100) may support enhanced broadband communications, highly reliable (e.g., mission critical) communications, low-latency communications, communications by low-cost and low-complexity devices, or any combination thereof.

[0045] Base stations (105) may be distributed over an entire geographical area to form a wireless communication system (100) and may be devices having different forms or different capabilities. Base stations (105) and UEs (115) may communicate wirelessly through one or more communication links (125). Each base station (105) may provide a coverage area (110) in which UEs (115) and base station (105) can establish one or more communication links (125). The coverage area (110) may be an example of a geographical area in which base stations (105) and UEs (115) can support the communication of signals according to one or more radio access technologies.

[0046] UEs (115) may be distributed over the entire coverage area (110) of the wireless communication system (100), and each UE (115) may be stationary or mobile at different times, or both. UEs (115) may be devices of different forms or different capabilities. Some exemplary UEs (115) are illustrated in FIG. 1. The UEs (115) described herein may communicate with various types of devices, such as other UEs (115) as illustrated in FIG. 1, base stations (105), or network equipment (e.g., core network nodes, relay devices, IAB (integrated access and backhaul) nodes, or other network equipment).

[0047] Base stations (105) can communicate with the core network (130), with each other, or with both. For example, base stations (105) can interface with the core network (130) through one or more backhaul links (120) (e.g., through S1, N2, N3, or other interfaces). Base stations (105) can communicate with each other directly (e.g., directly between base stations (105)) or indirectly (e.g., through the core network (130)), or both, through the backhaul links (120) (e.g., through X2, Xn, or other interfaces). In some examples, the backhaul links (120) may be one or more wireless links or may include them.

[0048] One or more of the base stations (105) described herein may be referred to to those skilled in the art as a base transceiver station, a wireless base station, an access point, a radio transceiver, a NodeB, an eNB (eNodeB), a next-generation NodeB or a giga-NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB, or other suitable terms, or may include these.

[0049] The UE (115) may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, among other examples, where “device” may also be referred to as or include a unit, station, terminal, or client. The UE (115) may also be referred to as or include a personal electronic device such as a cellular phone, PDA (personal digital assistant), tablet computer, laptop computer, or personal computer. In some examples, the UE (115) may be referred to as or include a WLL (wireless local loop) station, IoT (Internet of Things) device, IoE (Internet of Everything) device, or MTC (machine type communications) device, among other examples, and may be implemented in various objects such as devices, vehicles, or instruments, among other examples.

[0050] The UEs (115) described herein can communicate with various types of devices, such as macro eNBs or gNBs, small cell eNBs or gNBs, or base stations (105) including relay base stations, as well as network equipment, as well as other UEs (115) that can sometimes operate as relays, among other examples, as shown in FIG. 1.

[0051] UEs (115) and base stations (105) can communicate wirelessly with each other through one or more communication links (125) via one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure to support the communication links (125). For example, a carrier used in a communication link (125) may include a portion of a radio frequency spectrum band (e.g., a BWP (bandwidth part)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry capture signaling (e.g., synchronization signals, system information), control signaling that coordinates the operation for the carrier, user data, or other signaling. The wireless communication system (100) may support communication with the UE (115) using carrier aggregation or multi-carrier operation. The UE (115) may be composed of multiple downlink component carriers and one or more uplink component carriers according to the carrier aggregation configuration. The carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.

[0052] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have capture signaling or control signaling that coordinates operations for other carriers. The carrier may be associated with a frequency channel (e.g., EARFCN (E-UTRA (evolved universal mobile telecommunication system terrestrial radio access) absolute radio frequency channel number)) and positioned according to a channel raster for discovery by UEs (115). The carrier may operate in a standalone mode where initial capture and connection can be performed by UEs (115) through the carrier, or the carrier may operate in a non-standalone mode where connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0053] The communication links (125) illustrated in the wireless communication system (100) may include uplink transmissions from the UE (115) to the base station (105) or downlink transmissions from the base station (105) to the UE (115). Carriers may be configured to carry downlink or uplink communications (e.g., in FDD mode) or to carry downlink and uplink communications (e.g., in TDD mode).

[0054] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the "system bandwidth" of the wireless communication system (100). For example, the carrier bandwidth may be one of a number of determined bandwidths for carriers of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz), etc.). Devices of the wireless communication system (100) (e.g., base stations (105), UEs (115), or both) may have hardware configurations that support communications over a specific carrier bandwidth or may be configured to support communications over one of a set of carrier bandwidths. In some examples, the wireless communication system (100) may include base stations (105) or UEs (115) that support simultaneous communications over carriers associated with a number of carrier bandwidths. In some examples, each serving UE (115) may be configured to operate through parts (e.g., subband, BWP) or all of the carrier bandwidth.

[0055] Signal waveforms transmitted through a carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform-spread-OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element can be composed of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier interval are inversely proportional. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, as the number of resource elements received by the UE (115) increases and the order of the modulation scheme becomes higher, the data rate for the UE (115) may increase. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with the UE (115).

[0056] One or more numerologies for the carrier may be supported, where the numerology is the subcarrier interval ( It may include ) and cyclic prefixes. The carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, the UE (115) may be composed of multiple BWPs. In some examples, a single BWP for the carrier may be active at a given time, and communications to the UE (115) may be limited to one or more active BWPs.

[0057] Time intervals for base stations (105) or UEs (115) are, for example It can be expressed as multiples of a basic time unit that can refer to a sampling period of seconds, where It can express the maximum supported subcarrier interval, and It can represent the maximum supported discrete Fourier transform (DFT) size. The time intervals of the communication resources can be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0058] Each frame may contain a number of consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of slots. Alternatively, each frame may contain a variable number of slots, and the number of slots may depend on the subcarrier interval. Each slot may contain a number of symbol periods (e.g., depending on the length of the cyclic prefix pre-defending each symbol period). In some wireless communication systems (100), a slot may be further divided into a number of mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., It may include sample periods. The duration of the symbol period may depend on the subcarrier interval or the operating frequency band.

[0059] A subframe, slot, mini-slot, or symbol may be the minimum scheduling unit of a wireless communication system (100) (e.g., in the time domain) and may be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) may be variable. Additionally or alternatively, the minimum scheduling unit of the wireless communication system (100) may be dynamically selected (e.g., in bursts of shortened TTIs).

[0060] Physical channels may be multiplexed onto a carrier according to various technologies. Physical control channels and physical data channels may be multiplexed onto a downlink carrier using, for example, one or more of time division multiplexing (TDM) technologies, frequency division multiplexing (FDM) technologies, or hybrid TDM-FDM technologies. A control zone (e.g., a set of control resources (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend over the system bandwidth of the carrier or a subset of the system bandwidth. One or more control zones (e.g., CORESETs) may be configured for a set of UEs (115). For example, one or more of the UEs (115) may monitor or search for control zones for control information according to one or more sets of search spaces, each set of search spaces may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., CCEs (control channel elements)) associated with encoded information for a control information format having a given payload size. The search space sets may include common search space sets configured to transmit control information to a plurality of UEs (115) and UE-specific search space sets for transmitting control information to a specific UE (115).

[0061] In some examples, the base station (105) may be mobile and thus may provide communication coverage for a moving geographical coverage area (110). In some examples, different geographical coverage areas (110) associated with different technologies may overlap, but the different geographical coverage areas (110) may be supported by the same base station (105). In other examples, overlapping geographical coverage areas (110) associated with different technologies may be supported by different base stations (105). The wireless communication system (100) may include a heterogeneous network in which base stations (105) of different types provide coverage for various geographical coverage areas (110) using the same or different radio access technologies.

[0062] A wireless communication system (100) may support synchronous or asynchronous operation. In the case of synchronous operation, base stations (105) may have similar frame timings, and transmissions from different base stations (105) may be roughly time-aligned. In the case of asynchronous operation, base stations (105) may have different frame timings, and in some examples, transmissions from different base stations (105) may not be time-aligned. The techniques described herein may be used for synchronous or asynchronous operation.

[0063] The wireless communication system (100) may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communication system (100) may be configured to support URLLC (ultra-reliable low-latency communications) or mission-critical communications. UEs (115) may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communications may include private communications or group communications and may be supported by one or more mission-critical services such as MCPTT (mission critical push-to-talk), MCVideo (mission critical video), or MCData (mission critical data). Support for mission-critical functions may include the prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliability, low-latency, mission-critical, and ultra-reliability low-latency may be used interchangeably herein.

[0064] In some examples, the UE (115) may also communicate directly with other UEs (115) via a D2D (device-to-device) communication link (135) (e.g., using a P2P (peer-to-peer) or D2D protocol). One or more UEs (115) utilizing D2D communications may be within the geographical coverage area (110) of the base station (105). Other UEs (115) in this group may be outside the geographical coverage area (110) of the base station (105) or may not receive transmissions from the base station (105). In some examples, UEs (115) in a group communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE (115) transmits to all other UEs (115) in the group. In some examples, the base station (105) facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are performed between UEs (115) without the involvement of a base station (105).

[0065] The core network (130) may provide user authentication, access authorization, tracking, IP (Internet Protocol) access, and other access, routing, or mobility functions. The core network (130) may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., mobility management entity, access and mobility management function) that manages access and mobility, and at least one user plane entity (e.g., serving gateway, Packet Data Network gateway, or user plane function) that routes and interconnects packets to external networks. The control plane entity may manage non-access layer functions (e.g., NAS), such as mobility, authentication, and bearer management for UEs (115) served by base stations (105) associated with the core network (130). User IP packets can be transmitted through a user plane entity, which can provide IP address allocation as well as other functions. The user plane entity can be connected to network operator IP services (150). The operators' IP services (150) may include access to the Internet, intranet(s), IMS (IP Multimedia Subsystem), or packet-switched streaming services.

[0066] Some of the network devices, for example, a base station (105), may include subcomponents such as an access network entity (140), which may be an example of an access node controller (ANC). Each access network entity (140) may communicate with UEs (115) through one or more other access network transmission entities (145), which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transmission entity (145) may include one or more antenna panels. In some configurations, various functions of each access network entity (140) or base station (105) may be distributed across various network devices (e.g., radio heads and ANCs) or integrated into a single network device (e.g., base station (105)).

[0067] A wireless communication system (100) can typically operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the range of 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) range or decimeter band, because the wavelengths are in the range of approximately 1 decimeter to 1 meter in length. Although UHF waves may be blocked or redirected by buildings and environmental features, the waves can penetrate structures sufficiently to provide service to UEs (115) where macro cells are located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0068] A wireless communication system (100) may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system (100) may utilize License Assisted Access (LAA), LTE-U (LTE-Unlicensed) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz ISM (industrial, scientific, and medical) band. When operating in unlicensed radio frequency spectrum bands, devices such as base stations (105) and UEs (115) may utilize carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on carrier aggregation configurations involving component carriers operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum may include, among other examples, downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions.

[0069] A base station (105) or UE (115) may be equipped with multiple antennas, which may be used to utilize technologies such as transmit diversity, receive diversity, MIMO (multiple-input multiple-output) communications, or beamforming. The antennas of the base station (105) or UE (115) may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be colocated in an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station (105) may be located in various geographical locations. The base station (105) may have an antenna array having multiple rows and columns of antenna ports that the base station (105) can use to support beamforming of communications with the UE (115). Likewise, the UE (115) may have one or more antenna arrays capable of supporting various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for a signal transmitted through an antenna port.

[0070] Base stations (105) or UEs (115) may use MIMO communications to utilize multipath signal propagation and increase spectrum efficiency by transmitting or receiving multiple signals through different spatial layers. These techniques may be referred to as spatial multiplexing. Multiple signals may be transmitted by a transmitting device, for example, through different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device through different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a distinct spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include SU-MIMO (single-user MIMO), where multiple spatial layers are transmitted to the same receiving device, and MU-MIMO (multiple-user MIMO), where multiple spatial layers are transmitted to multiple devices.

[0071] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station (105) or UE (115)) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between a transmitting device and a receiving device. Beamforming can be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in specific orientations of the antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated through antenna elements may include the transmitting device or the receiving device applying amplitude offsets, phase offsets, or both to the signals being returned through the antenna elements associated with the device. The adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a specific orientation (e.g., for the antenna array of the transmitting device or the receiving device, or for some other orientation).

[0072] The wireless communication system (100) may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP (Packet Data Convergence Protocol) layer may be IP-based. The RLC (Radio Link Control) layer may perform packet segmentation and reassembly for communication over logical channels. The MAC (Medium Access Control) layer may perform multiplexing of logical channels into transport channels and priority handling. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC (Radio Resource Control) protocol layer may provide setup, configuration, and maintenance of RRC connections between the core network (130) or base station (105) supporting radio bearers for user plane data and the UE (115). In the physical layer, transport channels may be mapped to physical channels.

[0073] UEs (115) and base stations (105) may support data retransmissions to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique to increase the likelihood of data being accurately received over a communication link (125). HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput of the MAC layer under poor radio conditions (e.g., low signal-to-noise conditions). In some examples, the device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in the previous symbol of the slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0074] In some implementations, the UE (115) may use an iteration method in which the UE (115) transmits the same data to the base station (105) multiple times. The iteration method can increase communication reliability by allowing the base station (105) to receive and combine multiple transmissions of data (e.g., the base station (105) can perform join channel estimation across multiple transmissions). In some examples, the iteration method may be a PUSCH iteration method in which the UE (115) repeatedly transmits the same uplink data in a PUSCH. PUSCH iterations may be scheduled by the base station (105) or result from a single scheduled PUSCH transmission being split into multiple PUSCH transmissions. In some cases, PUSCH iterations may be scheduled on a mini-slot basis as opposed to a slot basis.

[0075] To initiate PUSCH iterations, the base station (105) may send an uplink grant to the UE (115) (e.g., at DCI or via RRC signaling) that schedules the PUSCH iterations and indicates iteration parameters. For example, the uplink grant may include a iteration factor K indicating the number of times the UE (115) transmits the same data via PUSCH. The uplink grant may also include a SLIV (start and length indicator value), which may indicate the symbol S that PUSCH transmissions should start with and the length L of each PUSCH transmission.

[0076] Upon receiving an uplink grant, the UE (115) may determine a transmission opportunity for each scheduled PUSCH transmission. The UE (115) may also determine the length of each PUSCH transmission (e.g., based on individual transmission opportunities). The UE (115) may further identify UCIs to be multiplexed with the PUSCH. In some examples, the UE (115) may identify UCIs based on the PUCCH that overlaps with the scheduled PUSCH transmission or based on a scheduling grant for the UCI. In certain systems, the UE (115) may determine a rate-matching scheme and a coding scheme for multiplexing the UCI with each PUSCH transmission based on the payload size of the UCI and the length of the PUSCH transmission. The UE (115) may determine the number of resource elements for transmitting the UCI in the PUSCH. The “length” or “actual length” of a PUSCH transmission may refer to the number of symbols in which PUSCH data is transmitted, which may correspond to the number of symbols constituting the transmission opportunity. Similarly, the “actual number of resource elements” may refer to the number of resource elements that the UCI will use in the PUSCH. However, using the actual length of PUSCH transmissions and the actual number of resource elements to determine the rate-matching method and coding method may negatively affect the ability of the base station (105) to combine and receive UCIs from PUSCH transmissions. For example, when the length of PUSCH transmissions changes, the UE (115) may use different coding methods for different PUSCH transmissions, which may make it more difficult for the base station (105) to receive UCIs by combining UCIs from multiple PUSCH transmissions.

[0077] To address these issues, the UE (115) may multiplex the UCI with the PUSCH in each transmission to maintain the same rate-matching and coding scheme across multiple PUSCH transmissions regardless of the actual length of the PUSCH transmissions. To do so, the UE (115) may multiplex the UCI with the PUSCH in at least one transmission based on a reference number of resource elements. The reference number of resource elements may be determined based on the PUSCH length provided by the uplink grant rather than the actual length of the PUSCH transmissions. Although described with reference to PUSCH iterations, the techniques described herein may be implemented in any type of iteration method. Unless the context otherwise provides, the terms transmission and iteration may be used interchangeably herein. Thus, the wireless communication system (100) may include features for improved power saving and, in some examples, may promote improved UCI transmission efficiencies among other advantages.

[0078] FIG. 2 illustrates an example of a wireless communication system (200) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. In some examples, the wireless communication system (200) may implement aspects of the wireless communication system (100). In the illustrated example, the system (200) may include a UE (115-a) and a base station (105-a). The UE (115-a) may be an example of the UE (115) described with reference to FIG. 1, and the base station (105-a) may be an example of the base station (105) described with reference to FIG. 1.

[0079] The base station (105-a) and the UE (115-a) can communicate with each other via the uplink (205) and the downlink (210). For example, the UE (115-a) can transmit uplink data and control information to the base station (105-a) on various channels of the uplink (205), and the base station (105-a) can transmit downlink data and control information to the UE (115-a) on various channels of the downlink (210). In one example, the uplink grant can be carried on the physical downlink control channel (PDCCH). The uplink grant can schedule one or more PUSCH transmissions by the UE (115-a). For example, the uplink grants each have a length Two PUSCH transmitters It can be scheduled.

[0080] When receiving PUSCH scheduling information, the UE (115-a) can identify a transmission opportunity for each iteration of the PUSCH. However, due to system constraints, the length of the transmission opportunity may be shorter than the scheduled length x. This may occur, for example, when the PUSCH transmission is scheduled across slot boundaries and the UE (115-a) splits the PUSCH transmission into two transmissions. In such a scenario, the UE (115-a) may transmit three PUSCH iterations (e.g., Iteration 1, Iteration 2, and Iteration 3) even though only two transmissions are scheduled, and the lengths of the iterations may vary (e.g., the lengths of Iteration 2 and Iteration 3 may be shorter than the length of Iteration 1). Thus, when the length of the transmission opportunity decreases, the length of the associated PUSCH iteration may also decrease. However, the UE can compensate for the reduced length by increasing the amount of information returned by the resource (for example, the UE can increase the bits per resource element (BPRE) for shortened PUSCH transmission). The transmission opportunity may also be referred to herein as a transmission opportunity.

[0081] The UE (115-a) can identify the UCI to be multiplexed with the PUSCH. In some cases, the base station (105-a) can schedule a PUSCH transmission that overlaps in time with the PUCCH transmission, and the UE (115-a) can identify the UCI to be multiplexed with the PUCCH, such as an ACK (acknowledgment), a NACK (negative acknowledgment), a CSI (channel state information), or a combination thereof, in the PUCCH. Additionally or alternatively, the base station (105) can schedule the UCI (e.g., A-CSI (aperiodic CSI)) by uplink grants, for example, in the PDCCH. In some examples, the UE (115-a) can perform CSI calculations based on uplink grants. In some examples, the UE (115-a) can generate A-CSI reports based on CSI calculations. UE(115-a) can decide to multiplex UCI with PUSCH in at least one PUSCH iteration.

[0082] The UE (115-a) can determine the number of resource elements of the PUSCH to be allocated to transmit the UCI in each PUSCH iteration based on the length of the PUSCH iteration and the payload size of the UCI. For example, when the UCI includes an ACK or a NACK and the PUSCH is scheduled with uplink shared data, the number of allocated resource elements can be calculated using the following formula: (1) Here, is the payload size of the ACK or NACK, and can be an MCS (modulation and coding scheme) offset for the bits of PUSCH, and is the number of resource elements within PUSCH available to transmit UCI, and is the payload size of the uplink shared data. In another example, when PUSCH is scheduled without shared data, the number of allocated resource elements can be calculated using the following formula: (2) Here, is the modulation order and R is the coding rate. Similarly, UE (115-a) can calculate the number of allocated resource elements using formulas when UCI includes CSI, A-CSI, CSI part 1, CSI part 2, etc.

[0083] The UE (115-a) can determine a rate-matching scheme for PUSCH transmission based on the number of resource elements allocated to the UCI. The UCI may include K information bits that may contain bits of an attached CRC. The UE (115-a) may use polar coding to encode the K information bits into the output of a polar mother code, where the output is It may have a length (e.g., coded bit length). The UE (115-a) may use a rate-matching method to map an output of length N to length M, where length M may not be a power of 2. Length N may be based on K, a coding rate R, length M, or a combination thereof.

[0084] Before performing rate-matching, the UE (115-a) may pass a polar mother code to a circular buffer of length N. The rate-matching method may include a puncturing method, a shortening method, or a repetition method. The UE (115-a) may use a puncturing method or a shortening method when N is greater than M, and the UE (115-a) may use a repetition method when N is less than M. The puncturing method may include selecting bits from positions (N - M) through (N - 1) of the circular buffer. The shortening method may include selecting bits from positions 0 through (M - 1) of the circular buffer. The repetition method may include selecting all bits from the circular buffer, and additionally, repeating (M - N) consecutive bits of the circular buffer starting from the smallest index bit. The UE (115-a) can determine which rate-matching method to use based on the payload size (e.g., K) of the UCI and the output sequence length, where the output sequence length may refer to a desired number of bits (e.g., M) coded based on the number of resource elements allocated to transmit the UCI. For example, the UE (115-a) may decide to use a shortening method if the ratio K / M exceeds a threshold (e.g., 7 / 16), and otherwise decide to use a puncturing method.

[0085] In summary, the number of resource elements allocated to the UCI in a PUSCH may vary depending on the number of symbols in the associated PUSCH transmission opportunity. The rate-matching and coding scheme for PUSCH transmission may be determined based on the number of resource elements allocated to the UCI. This means that when the length of the PUSCH transmission opportunities changes, the rate-matching and coding scheme used to multiplex the PUSCH data and the UCI during the opportunities also changes. For example, the rate-matching and coding scheme used for PUSCH repetition 1 may differ from the rate-matching and coding scheme used for PUSCH repetition 2 or PUSCH repetition 3. Thus, the rate-matching and coding scheme used for PUSCH repetitions may vary depending on their length. However, such variation among PUSCH repetitions may hinder the reception and combination of the UCI at the base station (105-a).

[0086] The UE (115-a) can prevent differences in rate-matching and coding schemes between PUSCH iterations by multiplexing the UCI to maintain the same rate-matching and coding scheme for each iteration, regardless of the length of the associated transmission opportunity. The UE (115-a) can determine the coding scheme using the length of the PUSCH transmission provided by the uplink grant rather than the actual length of the PUSCH transmission. Additionally, the UE (115-a) [can] the number of resource elements for transmitting the UCI (For example, not only the "actual number" of resource elements but also the reference number of resource elements) can determine. For a given PUSCH iteration It can be determined based on the amount of resource elements in a PUSCH iteration, or the amount of resource elements in a PUSCH iteration indicated in the uplink grant, or the minimum available amount of resource elements across all PUSCH iterations (e.g., iteration 1, iteration 2, and iteration 3). may be the same for all PUSCH iterations (e.g., iteration 1, iteration 2, and iteration 3) and may be determined based on the amount of resource elements in the PUSCH iteration indicated in the uplink grant, the minimum available amount of resource elements across all PUSCH iterations, or the maximum available amount of resource elements across all PUSCH iterations. The UE may determine the amount of resource elements in the PUSCH iteration indicated in the uplink grant based on the reference signal configuration associated with length L. The reference signal configuration may refer to multiple resources (symbols or resource elements) within the PUSCH allocated to reference signals, such as DMRS (demodulation reference signal) or PTRS (phase-tracking reference signal). Each scheduled length L may have an associated reference signal configuration. For example, scheduled length L = 8 may indicate that the PUSCH transmission must include one reference signal and seven data symbols.

[0087] After determining, the UE (115-a) may perform channel coding for the UCI based, for example, on the payload size of the UCI. In some examples, if the payload size of the UCI is less than a threshold (e.g., 11 bits), the UE (115-a) may coding the UCI It can be encoded into a sequence of encoded bits. Subsequently, the UE (115-a) modulates the symbols into the sequence of encoded bits and maps the modulated symbols to resource elements in at least one PUSCH iteration. In some examples, if the payload size of the UCI is less than a threshold, the base station (105-a) can soft-combine the received UCI in PUSCH iterations despite differences in the lengths of the encoded bits.

[0088] In some examples, if the payload size of the UCI exceeds the threshold, the UE (115-a) is as described herein It can determine. UE (115-a) is the rate-matching output sequence length To determine You can use, and here And, represents the number of layers in PUSCH transmission, and is the modulation order. Subsequently, UE(115-a) is UCI A sequence of coded bits It can be encoded as. UE(115-a) is the actual number of coded bits. You can decide, and here and, a sequence of coded bits UCI coded from It can generate bits. The beats It can be expressed as. In some examples, go If it is larger, A sequence of coded bits It can be expanded cyclically.

[0089] UE(115-a) is the output sequence length Based on this, it can be determined which rate-matching method to use, and this is the same across all PUSCH iterations. This can enable the UE (115-a) to use the same rate-matching and coding method for the UCI in each PUSCH iteration. Based on the rate-matching and coding method, the base station (105-a) can soft-combine the UCI received through the PUSCH iterations.

[0090] FIG. 3 illustrates examples of communication scenarios (300) that support multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. In some examples, the communication scenarios (300) may implement aspects of a wireless communication system (100) and a wireless communication system (200). The communication scenarios (300) may be examples of scenarios that occur when a base station (105) schedules a UE (115) to transmit data via PUSCH (e.g., on a mini-slot basis). Communication scenarios (300-a, 300-b, and 300-c) may illustrate PUSCH repetitions having various lengths, and communication scenario (300-d) may illustrate a collision between PUSCH and PUCCH.

[0091] In scenario (300-a), the UE may be scheduled by the base station to transmit two PUSCH iterations of length L to the base station. However, after receiving the scheduling information, the UE may determine that the second PUSCH iteration crosses the slot boundary. Since the base station can anticipate specific signals (e.g., reference signals) at the beginning of the slot, transmitting the iteration across the slot boundary may interfere with reception at the base station. Therefore, the UE may convert (e.g., split) the PUSCH iteration into two iterations so that one iteration (e.g., iteration 2) occurs before the slot boundary and another iteration (e.g., iteration 3) occurs after the slot boundary. Thus, in scenario (300-a), the UE may transmit three iterations of PUSCH data instead of two, and the iterations may have various lengths.

[0092] The UE can identify the UCI to be multiplexed with the PUSCH, for example, based on a scheduling grant from the base station. Rather than determining separate rate-matching and coding schemes for multiplexing the UCI with each iteration based on the actual length of the iteration (which can result in reception and combinational complexities at the base station), the UE can multiplex the UCI for each iteration to maintain the same rate-matching and coding scheme across the PUSCH iterations regardless of the actual length of the PUSCH iterations. To do so, the UE can multiplex the UCI with the PUSCH based on a reference number of resource elements. The reference number of resource elements can be determined based on the length of the nominal iterations rather than the actual length of the PUSCH transmits. A nominal repeat may be a repeat whose length (e.g., number of symbols) is equal to the length L provided by the base station (e.g., indicated in SLIV). Thus, the UE may multiplex the UCI with PUSCH using the length of the nominal repeat (e.g., repeat 1) and use the same rate-matching and coding scheme for each repeat regardless of its actual length. In some examples, the UE may decide not to multiplex the UCI with PUSCH repeats whose length is equal to the length of the nominal repeats (e.g., repeat 1), while not multiplexing the UCI with PUSCH repeats having lengths other than those of the nominal repeats (e.g., repeats 2 and 3).

[0093] In some examples, the UE may perform CSI calculations based on scheduling grants. The UE may generate an A-CSI report based on the CSI calculation and decide to include the generated A-CSI report in the UCI in one or more iterations. For example, the UE may decide to include the A-CSI in one or more subsequent iterations to enable the UE to satisfy the timeline for the CSI calculation. In some examples, the UE may decide to include the A-CSI in the last nominal iteration (i.e., an iteration containing the same number of symbols as length L). Additionally or alternatively, the UE may decide to include the A-CSI in the last iteration of the scheduled iterations, where the last iteration may be the nominal iteration or may contain multiple symbols different from length L.

[0094] In scenario (300-b), the UE may be scheduled by the base station to transmit a single PUSCH transmission of length L to the base station. For example, the UE may be scheduled to transmit a PUSCH transmission of length 8 symbols (e.g., 7 data symbols followed by a preceding DMRS symbol). However, the UE may determine that the scheduled PUSCH transmission crosses a slot boundary. Thus, the UE may convert the PUSCH transmission into two PUSCH transmissions, namely repetition 1 and repetition 2, each starting with a DMRS, and each containing 3 symbols for PUSCH data. Thus, rather than transmitting a nominal repetition of 8 symbols, the UE may transmit two repetitions of 4 symbols.

[0095] When multiplexing the UCI with the PUSCH, the UE can multiplex the UCI with the PUSCH using the length of a virtual nominal iteration. This means that the UE can determine the rate-matching scheme and coding scheme based on the virtual nominal iteration, which includes DMRS and PTRS configurations associated with the nominal iteration. Therefore, even if the UE does not transmit any iterations of that length, the UE can multiplex the UCI with the PUSCH in each iteration based on the length L provided by the base station. In some examples, when the UE does not transmit iterations of the nominal length, the UE can declare an error associated with transmitting the UCI.

[0096] In scenario (300-c), the UE may be operating in a TDD system that includes uplink symbols designated as U and downlink symbols designated as D. The TDD system may also include special symbols designated as X for switching between downlink and uplink. In scenario (300-c), the UE may be scheduled by the base station to transmit two PUSCH repetitions of length L to the base station. For example, the UE may be scheduled to transmit two PUSCH repetitions, each having a length of 5 symbols. The first PUSCH repetition may be scheduled for slot n, and the second PUSCH repetition may be scheduled for slot n + 1. However, the UE may determine that one of the scheduled PUSCH transmissions corresponds to a downlink transmission. For example, the UE may determine that the second repetition, i.e., part of repetition 2, is scheduled for one or more symbols allocated for downlink data. Accordingly, the UE can shorten the length of the second repetition (e.g., to a number of symbols equal to the number of L minus downlink symbols). According to the techniques described herein, the UE can multiplex the PUSCH and UCI in at least one repetition based on the length L of the nominal repetition in order to maintain the same rate-matching and coding scheme across a number of PUSCH transmissions regardless of the actual length of the PUSCH transmissions.

[0097] In scenario (300-d), the UE may be scheduled by the base station to transmit the PUCCH during one or more PUSCH transmissions. The UE may decide to multiplex the UCI of the PUCCH with the PUSCH in one or more PUSCH iterations. The UE may multiplex the UCI with the PUSCH in each transmission to maintain the same rate-matching and coding scheme across multiple PUSCH transmissions, regardless of the actual length of the PUSCH transmissions. To do so, the UE may multiplex the UCI with the PUSCH in one or more transmissions based on a reference number of resource elements rather than the number of resource elements used to transmit the UCI. The reference number of resource elements may be determined based on the PUSCH length provided by the uplink grant rather than the actual length of the PUSCH transmissions. In some examples, the UE may decide that all iterations overlapping with the PUCCH contain multiple symbols of length L or different and declare an error associated with the UCI.

[0098] In some examples, the determined number of symbols in an iteration (e.g., the amount of resource elements) may exclude symbols used for reference signals (e.g., DMRS, PTRS, etc.). In some examples, the UE may not expect that the number of modulated symbols with coded bits is greater than the number of symbols in each iteration overlapping with PUCCH. Additionally or alternatively, the UE may not expect that the number of modulated symbols with coded bits is greater than the number of symbols in any iteration overlapping with PUCCH. In some examples, the UE may determine that all iterations overlapping with PUCCH contain fewer symbols than the number of modulated symbols and declare an error associated with the UCI. Additionally or alternatively, the UE may determine that at least one iteration overlapping with PUCCH contains fewer symbols than the number of modulated symbols and declare an error associated with the UCI.

[0099] FIG. 4 illustrates an example of a process flow (400) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. In some examples, the process flow (400) may implement aspects of a wireless communication system (100) and a wireless communication system (200). For example, the process flow (400) may include a base station (105-b) and a UE (115-b), which may be examples of corresponding devices described with reference to FIG. 1 and FIG. 2. In the following description of the process flow (400), operations between the base station (105-b) and the UE (115-b) may be transmitted in a different order than the exemplary order shown, or operations performed by the base station (105-b) and the UE (115-b) may be performed in different orders or at different times. Some operations may also be omitted from the process flow (400), and other operations may be added to the process flow (400). The operations performed by the base station (105-b) and the UE (115-b) can support improvements to the UE (115-b) PUSCH transmission operations and, in some examples, promote improvements to the reliability of the UE (115-b) among other advantages.

[0100] In 405, the UE (115-b) may receive an uplink grant that schedules uplink shared channel (e.g., PUSCH) transmits. In some examples, the uplink grant may be a dynamic grant in the DCI. In some examples, the uplink grant may be a configured grant indicated by RRC signaling. In some examples, the uplink grant may include a repetition factor K indicating the number of repetitions of uplink shared channel transmits to be performed by the UE (115-b). The uplink grant may also include a SLIV indicating the symbol S at which uplink shared channel transmits should be initiated and the length L of each transmit (e.g., the number of symbols). In some examples, the UE (115-b) may receive a second uplink grant scheduling UCI (e.g., A-CSI). In some examples, the UE (115-b) may receive an uplink grant in the PDCCH. In some examples, the UE (115-b) can identify an uplink shared channel that includes URLLC transmission based on an uplink grant.

[0101] In 410, the UE (115-b) can identify transmission opportunities to transmit uplink shared channel iterations. The UE (115-b) can determine that at least one of the scheduled iterations crosses a slot boundary. Since the base station (105-b) can anticipate specific signals (e.g., reference signals) at the beginning of the slot, transmitting an iteration across the slot boundary can interfere with reception at the base station (105-b). Therefore, the UE (115-b) can convert (e.g., split) the iteration into two iterations so that one iteration occurs before the slot boundary and another iteration occurs after the slot boundary. In some examples, the UE (115-b) can determine that one of the scheduled iterations coincides with a downlink transmission. For example, the UE (115-b) can determine that part of the iteration is scheduled for one or more symbols allocated for downlink data. Accordingly, the UE (115-b) can shorten the length of the repetition corresponding to the downlink transmission (e.g., to a number of symbols equal to L minus the number of downlink symbols). Based on the separation, the UE (115-b) can identify that at least one repetition contains multiple symbols different from length L.

[0102] In 415, the UE (115-b) can identify a UCI to be multiplexed over an uplink shared channel. In some examples, the UCI may be included in a PUCCH that overlaps with one of the iterations. In some examples, the UE (115-b) can identify the UCI based on an uplink grant. For example, the uplink grant may include an indication that triggers the transmission of an A-CSI report over the uplink shared channel. In some examples, the UCI may include an ACK, NACK, CSI, A-CSI, etc. In some examples, the UE (115-b) can determine that the UCI includes a first part (e.g., CSI part 1) and a second part (e.g., CSI part 2). In some examples, the UE (115-b) can perform a CSI calculation based on the uplink grant. In some examples, the UE (115-b) can generate an A-CSI report based on the CSI calculation.

[0103] In 420, the UE (115-b) may determine the allocation for the UCI in each iteration to maintain the same rate-matching scheme and the same coding scheme for each iteration. The number of resource elements allocated to the UCI in each iteration may vary depending on the number of symbols in the iteration. For example, the UE (115-b) may allocate a first amount of resource elements to the first iteration based on the rate-matching scheme and the coding scheme, and allocate a second amount of resource elements different from the first amount to the second iteration. In some examples, the UE (115-b) may determine the coding scheme using the length of the uplink shared channel transmission provided by the uplink grant rather than the actual length of the iteration. Additionally, the UE (115-b) may determine the number of resource elements for transmitting the UCI (e.g., ) as well as the standard number of resource elements (e.g., Can determine ). For a given iteration It can be determined based on the amount of resource elements in the iteration, or the amount of resource elements in the uplink shared channel transmission indicated in the uplink grant, or the minimum available amount of resource elements across all iterations. It may be the same for all iterations and may be determined based on the amount of resource elements in the uplink shared channel transmission indicated in the uplink grant, the minimum available amount of resource elements across all iterations, or the maximum available amount of resource elements across all iterations. In some examples, the rate-matching method is based on the payload size of the UCI and the reference number of resource elements. It can be determined based on.

[0104] UE(115-b) is determined It may not be expected that the number of resource elements allocated to the UCI in any iteration will be greater than the number of resource elements allocated to the UCI. The determined number of symbols (e.g., the amount of resource elements) in the iteration available for UCI transmission may exclude resource elements used in reference signals (e.g., all resource elements within DMRS OFDM symbols, resource elements including PTRS, etc.). In some examples, the determined number of symbols available for UCI transmission is as described with reference to FIG. 2 It can be expressed by.

[0105] In some examples, the UE (115-b) may decide to include the generated A-CSI report in the UCI in one or more iterations. For example, the UE (115-b) may decide to include the A-CSI in one or more subsequent iterations to enable the UE (115-b) to satisfy the timeline for CSI calculation. In some examples, the UE (115-b) may decide to include the A-CSI only in the last nominal iteration (i.e., an iteration containing a number of symbols equal to length L). Additionally or alternatively, the UE (115-b) may decide to include the A-CSI in the last iteration of scheduled iterations, where the last iteration may be the nominal iteration or may contain a number of symbols (e.g., OFDM symbols) different from length L. The UE (115-b) for one or more iterations containing the A-CSI (e.g., the last iteration, the last nominal iteration, etc.) It can determine. In some examples, when the last iteration contains multiple symbols (e.g., OFDM symbols) that differ in length L, the UE (115-b) determines the determined for the last iteration It may not be expected that the number of resource elements allocated to the UCI in the last iteration will be larger than the number of resource elements allocated to the UCI.

[0106] After determining, the UE (115-b) can perform channel coding for the UCI based on, for example, the payload size of the UCI. In some examples, if the payload size of the UCI is less than a threshold (e.g., 11 bits), the UE (115-b) can encode the UCI into a sequence of encoded bits.

[0107] In some examples, if the payload size of the UCI exceeds the threshold, the UE (115-b) is as described herein It can determine. The UE (115-b) determines the rate-matching output sequence length. It may use. Subsequently, the UE (115-b) may encode the UCI into a sequence of coded bits corresponding to the output sequence length. The UE (115-b) may determine the amount of coded bits and generate said amount of coded bits of the UCI from the sequence of coded bits. In some examples, the UE (115-b) may determine that the amount of coded bits is greater than the output sequence length and may periodically expand the sequence of coded bits.

[0108] In 425, the UE (115-b) may multiplex the UCI over one or more iterations on the uplink shared channel based on the UCI assignment. In some examples, the UE (115-b) may modulate the symbols with coded bits and map the modulated symbols to resource elements in the iterations. In some examples, the UE (115-b) may multiplex a first portion of the UCI with URLLC transmission. In some examples, the UE (115-b) may determine that each iteration contains multiple symbols of length L and declare an error associated with the UCI. In some examples, the UE (115-b) may multiplex the ACK, NACK, CSI, or a combination thereof from the PUCCH over the uplink shared channel in the iterations overlapping with the PUCCH. In some examples, the UE (115-b) may determine that all iterations overlapping with the PUCCH contain multiple symbols of length L and declare an error associated with the UCI.

[0109] In some examples, the determined number of symbols in an iteration (e.g., the amount of resource elements) may exclude symbols used in reference signals (e.g., DMRS, PTRS, etc.). In some examples, the UE (115-b) may not expect that the number of modulated symbols with coded bits is greater than the number of symbols in each iteration overlapping with PUCCH. In some examples, the UE (115-b) may determine that all iterations overlapping with PUCCH contain fewer symbols than the number of modulated symbols and declare an error associated with the UCI.

[0110] In 430, the UE (115-b) can transmit the uplink shared channel and UCI in each iteration. Thus, the operations performed by the base station (105-b) and the UE (115-b) can support improvements to the UE (115-b) UCI ​​transmission operations and, in some examples, can promote improvements to the reliability of the UE (115-b) among other advantages.

[0111] FIG. 5 illustrates a block diagram (500) of a device (505) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. The device (505) may be an example of aspects of a UE (115) as described herein. The device (505) may include a receiver (510), a communication manager (515), and a transmitter (520). The device (505) may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0112] The receiver (510) may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to multiplexing uplink control information for uplink shared channel transmissions). The information may be transmitted to other components of the device (505). The receiver (510) may be an example of aspects of the transceiver (820) described with reference to FIG. 8. The receiver (510) may utilize a single antenna or a set of antennas.

[0113] A communication manager (515) receives an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols, and based on the uplink grant, identifies a first uplink transmission opportunity and a second uplink transmission opportunity to which the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols assigned to the uplink shared channel —, identifies a UCI to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity, multiplexes the UCI on the uplink shared channel to maintain the same rate-matching method and the same coding method for each of the first uplink transmission opportunity and the second uplink transmission opportunity, and can transmit the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0114] As described herein, the communication manager (515) may be implemented to realize one or more potential benefits. One implementation may enable the device (505) to communicate more efficiently with the base station (105) (as illustrated in FIG. 1) thereby saving power and increasing battery life. For example, the device (505) may efficiently transmit UCIs to the base station (105) in uplink shared channel transmissions, because the device (505) may reconfigure UCI transmission processes and multiplex UCIs over uplink shared channel transmissions to successfully transmit UL messages while maintaining the same rate-matching and the same coding scheme across the uplink shared channel transmissions. Another implementation may facilitate low-latency communications in the device (505) because signaling overhead and the number of resources allocated to UCI transmissions may be reduced. The communication manager (515) may be an example of aspects of the communication manager (810) described herein.

[0115] The communication manager (515) or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. When implemented in code executed by a processor, the functions of the communication manager (515) or its sub-components may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0116] The communication manager (515) or its sub-components may be physically located in various positions, including distributed so that some of the functions are implemented by one or more physical components in different physical locations. In some examples, the communication manager (515) or its sub-components may be separate and distinct components according to various aspects of the present disclosure. In some examples, the communication manager (515) or its sub-components may be combined with one or more other hardware components, including (but not limited to) an I / O (input / output) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof according to various aspects of the present disclosure.

[0117] The transmitter (520) can transmit signals generated by other components of the device (505). In some examples, the transmitter (520) may be colocated with the receiver (510) of the transceiver module. For example, the transmitter (520) may be an example of aspects of the transceiver (820) described with reference to FIG. 8. The transmitter (520) may utilize a single antenna or a set of antennas.

[0118] FIG. 6 illustrates a block diagram (600) of a device (605) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. The device (605) may be an example of aspects of the device (505) or UE (115) as described herein. The device (605) may include a receiver (610), a communication manager (615), and a transmitter (640). The device (605) may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0119] The receiver (610) may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to multiplexing uplink control information for uplink shared channel transmissions). The information may be transmitted to other components of the device (605). The receiver (610) may be an example of aspects of the transceiver (820) described with reference to FIG. 8. The receiver (610) may utilize a single antenna or a set of antennas.

[0120] The communication manager (615) may be an example of aspects of the communication manager (515) as described herein. The communication manager (615) may include a scheduling manager (620), a transmission opportunity manager (625), a UCI component (630), and a multiplexing component (635). The communication manager (615) may be an example of aspects of the communication manager (810) described herein.

[0121] The scheduling manager (620) receives an uplink grant that schedules the transmission of the uplink shared channel using the first number of symbols.

[0122] A transmission opportunity manager (625) can, based on an uplink grant, identify a first uplink transmission opportunity and a second uplink transmission opportunity to transmit at least one uplink shared channel, and transmit the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity, wherein at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols assigned to the uplink shared channel.

[0123] The UCI component (630) can identify uplink control information (UCI) to be multiplexed on an uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0124] The multiplexing component (635) can multiplex UCIs on an uplink shared channel to maintain the same rate-matching method and the same coding method for each of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0125] The transmitter (640) can transmit signals generated by other components of the device (605). In some examples, the transmitter (640) may be colocated with the receiver (610) of the transceiver module. For example, the transmitter (640) may be an example of aspects of the transceiver (820) described with reference to FIG. 8. The transmitter (640) may utilize a single antenna or a set of antennas.

[0126] FIG. 7 illustrates a block diagram (700) of a communication manager (705) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. The communication manager (705) may be an example of aspects of the communication manager (515), communication manager (615), or communication manager (810) described herein. The communication manager (705) may include a scheduling manager (710), a transmission opportunity manager (715), a UCI component (720), a multiplexing component (725), a resource element component (730), and an encoding manager (735). Each of these modules may communicate with one another directly or indirectly (e.g., through one or more buses).

[0127] The scheduling manager (710) receives an uplink grant that schedules the transmission of the uplink shared channel using a first number of symbols. In some examples, the scheduling manager (710) may receive the uplink grant from DCI or via RRC signaling. In some cases, the uplink shared channel includes PUSCH. In some cases, A-CSI may be scheduled by the second uplink grant. In some cases, the uplink grant may include the second uplink grant.

[0128] A transmission opportunity manager (715) can identify, based on an uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which at least an uplink shared channel is to be transmitted, and at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from a first number of symbols assigned to the uplink shared channel. In some examples, the transmission opportunity manager (715) can determine that at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity includes a first number of symbols assigned to the uplink shared channel, and at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols.

[0129] In some examples, the transmission opportunity manager (715) may transmit an uplink shared channel and a UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity. In some examples, the transmission opportunity manager (715) may determine that the uplink shared channel includes URLLC transmission. In some examples, the transmission opportunity manager (715) may determine that the uplink transmission opportunity overlaps with a PUCCH, that the PUCCH includes a UCI, and that the uplink transmission opportunity corresponds to at least one of the first uplink transmission opportunity or the second uplink transmission opportunity. In some examples, the transmission opportunity manager (715) may determine that at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity satisfies a resource constraint based on the amount of resource elements in the uplink shared channel, the resource constraint includes an amount of resource elements for transmitting a UCI that is not greater than the amount of resource elements in the uplink shared channel. In some examples, the transmission opportunity manager (715) may determine that each uplink sharing channel in the first uplink transmission opportunity and the second uplink transmission opportunity satisfies a resource constraint based on the amount of resource elements in the uplink sharing channel, and the resource constraint includes an amount of resource elements for transmitting a UCI that is not greater than the amount of resource elements in the uplink sharing channel.

[0130] The UCI component (720) can identify uplink control information (UCI) to be multiplexed on an uplink shared channel during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. In some examples, the UCI component (720) can determine that the UCI includes a first part and a second part. In some cases, the UCI may include an ACK, a NACK, a CSI, an A-CSI, or a combination thereof.

[0131] In some examples, the UCI component (720) can determine the payload size of the UCI. In some examples, the UCI component (720) can determine that the payload size of the UCI exceeds a threshold. In some examples, the UCI component (720) can determine that the payload size of the UCI is less than a threshold.

[0132] The multiplexing component (725) can multiplex UCIs on an uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity. In some examples, the multiplexing component (725) can multiplex UCIs on at least one uplink shared channel containing a first number of symbols. In some examples, the multiplexing component (725) can prevent multiplexing UCIs on at least one uplink shared channel containing a second number of symbols.

[0133] In some examples, the multiplexing component (725) may multiplex a first portion of the UCI with a URLLC transmission. In some examples, the multiplexing component (725) may map modulated symbols to resource elements of an uplink shared channel. In some examples, the multiplexing component (725) may multiplex ACK, NACK, CSI, or a combination thereof on an uplink shared channel in an uplink transmission opportunity that overlaps with PUCCH. In some examples, the multiplexing component (725) may multiplex ACK, NACK, CSI, or a combination thereof on at least one uplink shared channel that satisfies resource constraints. In some cases, the amount of resource elements in an uplink shared channel excludes the amount of resource elements in one or more symbols including DMRS, PTRS, or both. In some examples, the multiplexing component (725) can multiplex ACK, NACK, CSI, or a combination thereof on each uplink shared channel based on each uplink shared channel that satisfies resource constraints.

[0134] In some examples, the multiplexing component (725) may multiplex A-CSI on the uplink shared channel to a selected transmission opportunity among a first uplink transmission opportunity or a second uplink transmission opportunity, and the UCI includes A-CSI. In some cases, the selected uplink transmission opportunity may be the last uplink transmission opportunity that includes a first number of symbols assigned to the uplink shared channel as identified based on the uplink grant. In some cases, the selected uplink transmission opportunity may be the last uplink transmission opportunity identified based on the uplink grant, and the last uplink transmission opportunity includes a first number of symbols assigned to the uplink shared channel or a second number of symbols different from the first number of symbols assigned to the uplink shared channel.

[0135] The resource element component (730) may allocate a first amount of resource elements to the UCI in a first uplink transmission opportunity based on a rate-matching method and a coding method. In some examples, the resource element component (730) may allocate a second amount of resource elements to the UCI in a second uplink transmission opportunity based on a rate-matching method and a coding method, and the second amount is different from the first amount. In some examples, the resource element component (730) may determine the amount of resource elements for transmitting the UCI. In some examples, the resource element component (730) may determine a reference amount of resource elements for the UCI.

[0136] In some cases, the reference amount of resource elements for the UCI includes a first amount of resource elements in a scheduled transmission of an uplink shared channel, a second amount of resource elements in a first uplink transmission opportunity; a third amount of resource elements in a second uplink transmission opportunity; the larger of the first amount, the second amount, and the third amount; or the smaller of the first amount, the second amount, and the third amount.

[0137] In some cases, the amount of resource elements for the UCI includes a first amount of resource elements in a scheduled transmission of an uplink shared channel, a second amount of resource elements in a first uplink transmission opportunity, a third amount of resource elements in a second uplink transmission opportunity, or the smaller of the first amount, the second amount, and the third amount.

[0138] The encoding manager (735) can determine the output sequence length based on a reference amount of resource elements and a rate-matching method. In some examples, the encoding manager (735) can use polar coding to encode the UCI into a sequence of coded bits, and the length of the sequence of coded bits corresponds to the output sequence length. In some examples, the encoding manager (735) can determine the amount of coded bits based on the amount of resource elements for transmitting the UCI.

[0139] In some examples, the encoding manager (735) may determine the amount of coded bits based on the sequence of coded bits. In some examples, the encoding manager (735) may determine that the amount of coded bits is greater than the output sequence length. In some examples, the encoding manager (735) may cyclically expand the sequence of coded bits.

[0140] In some examples, the encoding manager (735) can encode the UCI into a sequence of coded bits. In some examples, the encoding manager (735) can modulate the symbols into a sequence of encoded bits based on a rate-matching method.

[0141] FIG. 8 illustrates a system (800) comprising a device (805) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. The device (805) may be an example of or include components of a device (505), a device (605), or a UE (115) as described herein. The device (805) may include components for bidirectional voice and data communications, including components for transmitting and receiving communications, such as a communication manager (810), an I / O controller (815), a transceiver (820), an antenna (825), a memory (830), and a processor (840). These components may communicate electronically through one or more buses (e.g., a bus (845)).

[0142] A communication manager (810) receives an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols, and based on the uplink grant, identifies a first uplink transmission opportunity and a second uplink transmission opportunity to which the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from the first number of symbols assigned to the uplink shared channel —, identifies a UCI to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity, multiplexes the UCI on the uplink shared channel to maintain the same rate-matching method and the same coding method for each of the first uplink transmission opportunity and the second uplink transmission opportunity, and can transmit the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0143] The I / O controller (815) can manage input and output signals for the device (805). The I / O controller (815) can also manage peripheral devices that are not integrated into the device (805). In some cases, the I / O controller (815) can represent physical connections or ports to external peripheral devices. In some cases, the I / O controller (815) can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In other cases, the I / O controller (815) can represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller (815) can be implemented as part of a processor. In some cases, the user can interact with the device (805) through the I / O controller (815) or through hardware components controlled by the I / O controller (815).

[0144] As previously described, the transceiver (820) can communicate bidirectionally with wired or wireless links through one or more antennas. For example, the transceiver (820) can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver (820) may also include a modem that modulates packets, provides the modulated packets to the antennas for transmission, and demodulates the packets received from the antennas.

[0145] In some cases, the wireless device may include a single antenna (825). However, in some cases, the device may have more than one antenna (825) capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0146] Memory (830) may include random access memory (RAM), read-only memory (ROM), or a combination thereof. Memory (830) may store computer-readable computer-executable code (835) containing instructions, which, when executed, cause the processor to perform the various functions described herein. In some cases, memory (830) may include a basic input / output system (BIOS) capable of controlling basic hardware or software operations, such as interactions with peripheral components or devices, among other things.

[0147] The processor (840) may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a CPU (central processing unit), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor (840) may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor (840). The processor (840) may be configured to execute computer-readable instructions stored in memory (e.g., memory (830)) to enable the device (805) to perform various functions (e.g., functions or tasks that support multiplexing uplink control information for uplink shared channel transmissions).

[0148] The processor (840) of the device (805) (e.g., controlling the receiver (510), transmitter (520), or transceiver (820)) can reduce power consumption and increase UCI transmission reliability by multiplexing UCIs over uplink shared channel transmissions while maintaining the same rate-matching and coding scheme. In some examples, the processor (840) of the device (805) can reconfigure the parameters for transmitting UCIs. For example, the processor (840) of the device (805) can turn on one or more processing units to perform UCI transmissions, increase the processing clock, or perform similar mechanisms within the device (805). Thus, when subsequent UCI transmissions are required, the processor (840) can be prepared to respond more efficiently by reducing the ramp-up of processing power. Improvements in power saving and UCI transmission reliability (e.g., by reducing or eliminating unnecessary or failed UCI transmissions) can further increase battery life in the device (805).

[0149] Code (835) may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communications. Code (835) may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. In some cases, Code (835) may not be directly executable by the processor (840), but may enable the computer to perform the functions described herein (e.g., when compiled and executed).

[0150] FIG. 9 illustrates a flowchart illustrating a method (900) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. Operations of the method (900) may be implemented by a UE (115) or components thereof as described herein. For example, operations of the method (900) may be performed by a communication manager as described with reference to FIGS. 5 through 8. In some examples, the UE may execute a set of commands to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use special-purpose hardware to perform aspects of the functions described below.

[0151] In 905, the UE receives an uplink grant that schedules the transmission of an uplink shared channel using first number symbols. The operations of 905 may be performed according to the methods described herein. In some examples, aspects of the operations of 905 may be performed by a scheduling manager as described with reference to FIGS. 5 through 8.

[0152] In 910, the UE can identify, based on an uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which at least an uplink shared channel is to be transmitted, and at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from a first number of symbols assigned to the uplink shared channel. The operations of 910 may be performed according to the methods described herein. In some examples, aspects of the operations of 910 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0153] In 915, the UE can identify uplink control information (UCI) to be multiplexed on an uplink shared channel during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. The operations of 915 may be performed according to the methods described herein. In some examples, aspects of the operations of 915 may be performed by a UCI component as described with reference to FIGS. 5 through 8.

[0154] In 920, the UE may multiplex UCIs over an uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity. The operations of 920 may be performed according to the methods described herein. In some examples, aspects of the operations of 920 may be performed by a multiplexing component as described with reference to FIGS. 5 through 8.

[0155] In 925, the UE may transmit an uplink shared channel and a UCI during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. The operations of 925 may be performed according to the methods described herein. In some examples, aspects of the operations of 925 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0156] FIG. 10 illustrates a flowchart illustrating a method (1000) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. Operations of the method (1000) may be implemented by a UE (115) or components thereof as described herein. For example, operations of the method (1000) may be performed by a communication manager as described with reference to FIGS. 5 through 8. In some examples, the UE may execute a set of commands to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use special-purpose hardware to perform aspects of the functions described below.

[0157] In 1005, the UE receives an uplink grant that schedules the transmission of an uplink shared channel using first number symbols. The operations of 1005 may be performed according to the methods described herein. In some examples, aspects of the operations of 1005 may be performed by a scheduling manager as described with reference to FIGS. 5 through 8.

[0158] In 1010, the UE can identify, based on an uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which at least an uplink shared channel is to be transmitted, and at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from a first number of symbols assigned to the uplink shared channel. The operations of 1010 may be performed according to the methods described herein. In some examples, aspects of the operations of 1010 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0159] In 1015, the UE can identify uplink control information (UCI) to be multiplexed on an uplink shared channel during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. The operations of 1015 may be performed according to the methods described herein. In some examples, aspects of the operations of 1015 may be performed by a UCI component as described with reference to FIGS. 5 through 8.

[0160] In 1020, the UE can determine the payload size of the UCI. The operations of 1020 can be performed according to the methods described herein. In some examples, aspects of the operations of 1020 can be performed by the UCI component as described with reference to FIGS. 5 through 8.

[0161] In 1025, the UE can determine the amount of resource elements for transmitting the UCI and the reference amount of resource elements for the UCI. The operations of 1025 can be performed according to the methods described herein. In some examples, aspects of the operations of 1025 can be performed by a resource element component as described with reference to FIGS. 5 through 8.

[0162] In 1030, the UE can use polar coding to encode the UCI into a sequence of coded bits, and the length of the sequence of coded bits corresponds to the output sequence length based on the reference amount of resource elements and the rate-matching method. The operations of 1030 can be performed according to the methods described herein. In some examples, aspects of the operations of 1030 can be performed by an encoding manager as described with reference to FIGS. 5 through 8.

[0163] In 1035, the UE determines the amount of coded bits based on the amount of resource elements for transmitting the UCI, and can generate said amount of coded bits based on a sequence of coded bits. The operations of 1035 can be performed according to the methods described herein. In some examples, aspects of the operations of 1035 can be performed by an encoding manager as described with reference to FIGS. 5 through 8.

[0164] In 1040, the UE may multiplex UCIs over an uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity. The operations of 1040 may be performed according to the methods described herein. In some examples, aspects of the operations of 1040 may be performed by a multiplexing component as described with reference to FIGS. 5 through 8.

[0165] In 1045, the UE may transmit an uplink shared channel and a UCI during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. The operations of 1045 may be performed according to the methods described herein. In some examples, aspects of the operations of 1045 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0166] FIG. 11 illustrates a flowchart illustrating a method (1100) that supports multiplexing uplink control information for uplink shared channel transmissions according to aspects of the present disclosure. Operations of the method (1100) may be implemented by a UE (115) or its components as described herein. For example, operations of the method (1100) may be performed by a communication manager as described with reference to FIGS. 5 through 8. In some examples, the UE may execute a set of commands to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use special-purpose hardware to perform aspects of the functions described below.

[0167] In 1105, the UE receives an uplink grant that schedules transmissions on the uplink shared channel using first number symbols. The operations of 1105 may be performed according to the methods described herein. In some examples, aspects of the operations of 1105 may be performed by a scheduling manager as described with reference to FIGS. 5 through 8.

[0168] In 1110, the UE can identify, based on an uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which at least an uplink shared channel is to be transmitted, and at least one of the first uplink transmission opportunity or the second uplink transmission opportunity includes a second number of symbols different from a first number of symbols assigned to the uplink shared channel. The operations of 1110 may be performed according to the methods described herein. In some examples, aspects of the operations of 1110 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0169] In 1115, the UE can identify uplink control information (UCI) to be multiplexed on an uplink shared channel during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. The operations of 1115 may be performed according to the methods described herein. In some examples, aspects of the operations of 1115 may be performed by a UCI component as described with reference to FIGS. 5 through 8.

[0170] In 1120, the UE may multiplex UCIs over an uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity. The operations of 1120 may be performed according to the methods described herein. In some examples, aspects of the operations of 1120 may be performed by a multiplexing component as described with reference to FIGS. 5 through 8.

[0171] In 1125, the UE may determine that at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity comprises a first number of symbols assigned to the uplink shared channel, and that at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity comprises a second number of symbols different from the first number of symbols. The operations of 1125 may be performed according to the methods described herein. In some examples, aspects of the operations of 1125 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0172] In 1130, the UE can multiplex the UCI over at least one uplink shared channel comprising first number symbols. The operations of 1130 can be performed according to the methods described herein. In some examples, aspects of the operations of 1130 can be performed by a UCI component as described with reference to FIGS. 5 through 8.

[0173] In 1135, the UE may suppress multiplexing the UCI over at least one uplink shared channel containing the second number of symbols. The operations of 1135 may be performed according to the methods described herein. In some examples, aspects of the operations of 1135 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0174] In 1140, the UE may transmit an uplink shared channel and a UCI during at least one of a first uplink transmission opportunity and a second uplink transmission opportunity. The operations of 1140 may be performed according to the methods described herein. In some examples, aspects of the operations of 1140 may be performed by a transmission opportunity manager as described with reference to FIGS. 5 through 8.

[0175] It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Additionally, aspects from two or more of the methods may be combined.

[0001] The following provides an overview of examples of the present invention:

[0176] Example 1: A method for wireless communications, comprising: receiving an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols; identifying, at least partially based on the uplink grant, a first uplink transmission opportunity and a second uplink transmission opportunity to which the uplink shared channel is to be transmitted — at least one of the first uplink transmission opportunity or the second uplink transmission opportunity comprises a second number of symbols different from the first number of symbols assigned to the uplink shared channel —; identifying uplink control information (UCI) to be multiplexed on the uplink shared channel during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity; multiplexing the UCI on the uplink shared channel to maintain the same rate-matching scheme and the same coding scheme for each of the first uplink transmission opportunity and the second uplink transmission opportunity; and transmitting the uplink shared channel and the UCI during at least one of the first uplink transmission opportunity and the second uplink transmission opportunity.

[0177] Example 2: The method for wireless communications, wherein, in Example 1, the step of allocating a first amount of resource elements to a UCI in a first uplink transmission opportunity at least partially based on a rate-matching method and a coding method; and the step of allocating a second amount of resource elements to a UCI in a second uplink transmission opportunity at least partially based on a rate-matching method and a coding method, wherein the second amount is different from the first amount.

[0178] Example 3: A method for wireless communications, further comprising: determining that, in Example 1 or Example 2, at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity comprises a first number of symbols assigned to the uplink shared channel, and that at least one uplink shared channel in the first uplink transmission opportunity or the second uplink transmission opportunity comprises a second number of symbols different from the first number of symbols; multiplexing a UCI on at least one uplink shared channel comprising the first number of symbols; and suppressing the multiplexing of a UCI on at least one uplink shared channel comprising the second number of symbols.

[0179] Example 4: A method for wireless communications, further comprising, in any one of Examples 1 to 3, the step of determining that an uplink shared channel includes an ultra-reliable low latency communications (URLC) transmission; the step of determining that a UCI includes a first part and a second part; and the step of multiplexing the first part of the UCI with the URLLC transmission.

[0180] Example 5: A method for wireless communications, further comprising, in any one of Examples 1 to 4, a step of determining the payload size of a UCI; a step of determining the amount of resource elements for transmitting the UCI; and a step of determining a reference amount of resource elements for the UCI.

[0181] Example 6: A method for wireless communications, further comprising, in Example 5, a step of determining an output sequence length based at least partially on a reference amount of resource elements and a rate-matching method; a step of encoding a UCI into a sequence of coded bits using polar coding — the length of the sequence of coded bits corresponds to the output sequence length —; a step of determining an amount of coded bits based at least partially on an amount of resource elements for transmitting the UCI; and a step of generating said amount of coded bits based at least partially on a sequence of coded bits.

[0182] Example 7: A method for wireless communications, wherein, in Example 6, the step of generating the positive coded bits comprises: determining that the amount of coded bits is greater than the output sequence length; and cyclically expanding the sequence of coded bits.

[0183] Example 8: A method for wireless communications, wherein, in Example 6 or Example 7, the reference amount of resource elements for the UCI comprises a first amount of resource elements in a scheduled transmission of an uplink shared channel, a second amount of resource elements in at least one of a first uplink transmission opportunity and a second uplink transmission opportunity, the larger of the first amount and the second amount, or the smaller of the first amount and the second amount.

[0184] Example 9: A method for wireless communications, wherein in any one of Examples 6 to 8, the rate-matching method is determined at least partially based on the payload size of the UCI and the reference amount of resource elements for the UCI.

[0185] Example 10: A method for wireless communications, further comprising, in any one of Examples 5 to 9, the step of determining that the payload size of the UCI is less than a threshold; the step of encoding the UCI into a sequence of encoded bits; and the step of modulating symbols into a sequence of encoded bits based at least partially on a rate-matching method.

[0186] Example 11: A method for wireless communications, wherein, in Example 10, the multiplexing step includes the step of mapping modulated symbols to resource elements of an uplink shared channel.

[0187] Example 12: A method for wireless communications, wherein in any one of Examples 5 to 11, the amount of resource elements for transmitting a UCI comprises a first amount of resource elements in a scheduled transmission of an uplink shared channel, a second amount of resource elements in at least one of a first uplink transmission opportunity and a second uplink transmission opportunity, or the smaller of the first amount and the second amount.

[0188] Example 13: A method for wireless communications, wherein in any one of Examples 1 to 12, the uplink shared channel comprises a PUSCH (physical uplink shared channel).

[0189] Example 14: A method for wireless communications, further comprising the step of receiving an uplink grant in DCI (downlink control information) or through RRC (radio resource control) signaling in any one of Examples 1 to 13.

[0190] Example 15: A method for wireless communications, wherein in any one of Examples 1 to 14, the UCI comprises ACK (acknowledgment), NACK (negative acknowledgment), CSI (channel state information), A-CSI (aperiodic CSI), or a combination thereof.

[0191] Example 16: In Example 15, A-CSI is scheduled by the second uplink grant.

[0192] Example 17: In Example 16, the uplink grant includes a second uplink grant.

[0193] Example 18: A method for wireless communications, wherein in any one of Examples 15 to 17, the method further comprises the step of determining that an uplink transmission opportunity overlaps with a physical uplink control channel (PUCCH), wherein the PUCCH includes a UCI, and the uplink transmission opportunity corresponds to at least one of a first uplink transmission opportunity or a second uplink transmission opportunity.

[0194] Example 19: A method for wireless communications, further comprising the step of multiplexing an ACK, a NACK, the CSI, or a combination thereof on an uplink shared channel over an uplink transmission opportunity overlapping with a PUCCH in Example 18.

[0195] Example 20: A method for wireless communications, further comprising the step of determining, in Example 18 or Example 19, that at least one uplink shared channel in a first uplink transmission opportunity or a second uplink transmission opportunity satisfies a resource constraint based at least partially on the amount of resource elements in the uplink shared channel — the resource constraint includes an amount of resource elements for transmitting a UCI that is not greater than the amount of resource elements in the uplink shared channel — and the step of multiplexing an ACK, NACK, CSI, or a combination thereof on at least one uplink shared channel that satisfies the resource constraint.

[0196] Example 21: A method for wireless communications in which, in Example 20, the amount of resource elements in an uplink shared channel excludes the amount of resource elements in one or more symbols including a demodulation reference signal, a phase-tracking reference signal, or both.

[0197] Example 22: A method for wireless communications, comprising, in any one of Examples 18 to 21, a step of determining that each uplink shared channel in a first uplink transmission opportunity and a second uplink transmission opportunity satisfies a resource constraint based at least partially on the amount of resource elements in the uplink shared channel — the resource constraint includes an amount of resource elements for transmitting a UCI that is not greater than the amount of resource elements in the uplink shared channel — and a step of multiplexing an ACK, NACK, CSI, or a combination thereof on each uplink shared channel based at least partially on each uplink shared channel satisfying the resource constraint.

[0198] Example 23: A method for wireless communications, wherein in any one of Examples 1 to 22, the method further comprises the step of multiplexing A-CSI (aperiodic channel state information) on an uplink shared channel to a selected transmission opportunity among a first uplink transmission opportunity or a second uplink transmission opportunity, and the UCI comprises A-CSI.

[0199] Example 24: A method for wireless communications in which, in Example 23, the selected uplink transmission opportunity is the last uplink transmission opportunity comprising a first number of symbols assigned to an uplink shared channel, as identified at least partially based on an uplink grant.

[0200] Example 25: A method for wireless communications, wherein in Example 23 or Example 24, the selected uplink transmission opportunity is the last uplink transmission opportunity identified at least partially based on an uplink grant, and the last uplink transmission opportunity comprises a first number of symbols assigned to an uplink shared channel or a second number of symbols different from the first number of symbols assigned to an uplink shared channel.

[0201] Example 26: An apparatus for wireless communications comprising at least one means for performing any one of the methods of Example 1 to Example 25.

[0202] Example 27: A device for wireless communications comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to enable the device to perform any one of Examples 1 through 25.

[0203] Example 28: A non-transient computer-readable medium, wherein the non-transient computer-readable medium stores code for wireless communications, and the code comprises instructions executable by a processor to perform any one of the methods of Examples 1 through 25.

[0204] Aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for the purposes of example, and while the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the technologies described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described technologies may be applicable to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0205] It will be understood that the information and signals described herein may be represented using any of various other technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented as voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0206] The various exemplary blocks and components described in connection with the disclosure herein may be implemented or performed by general-purpose processors, DSPs, ASICs, CPUs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0207] 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, these functions may be stored as one or more instructions or codes on a computer-readable medium or transmitted therethrough. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be located in various physically positioned locations, including distributed so that parts of the functions are implemented in different physical locations.

[0208] Computer-readable media include both non-transient computer storage media and communication media, which include any media that facilitate the transfer of a computer program from one place to another. Non-transient storage media may be any available media accessible by a general-purpose or special-purpose computer. By example, not limiting, non-transient computer-readable media may include RAM, ROM, EEPROM (electrically erasable programmable ROM), flash memory, CD-ROM (compact disk) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transient media accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor that may be used to transmit or store desired means of program code in the form of instructions or data structures. Additionally, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair cable, DSL (digital subscriber line), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair cable, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. Disks and discs as used herein include CDs, laser discs, optical discs, DVDs (digital versatile discs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while discs reproduce data optically by lasers. Combinations of the above are also included within the scope of computer-readable media.

[0209] As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items followed by phrases such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A, B, and C). Additionally, as used herein, the phrase “based on” should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. That is, as used herein, the phrase “based on” will be interpreted in the same manner as the phrase “at least partially based on”.

[0210] In the attached drawings, similar components or features may have the same reference label. Additionally, various components of the same type may be distinguished by a dash symbol following the reference label and a second label distinguishing between similar components. Where only the first reference label is used in this specification, the description is applicable to any component among similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0211] The description provided herein in connection with the accompanying drawings describes exemplary configurations and does not represent all examples that are within the scope of the claims or that may be implemented. As used herein, the term “exemplary” means “serving as an example, illustration, or illustration,” rather than being “advantageous over other examples” or “preferred.” The detailed description includes specific details for the purpose of providing an understanding of the described technologies. However, these technologies may be practiced without such specific details. In some examples, known structures and devices are illustrated in block diagram form to avoid obscuring the concepts of the described examples.

[0212] The description of this application is provided to enable those skilled in the art to use or practice the present disclosure. Various variations of the present disclosure will be readily apparent to those skilled in the art, and the general principles defined in this specification may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described in this specification, but follows the broadest scope consistent with the principles and novel features disclosed in this specification.

Claims

Claim 1 A device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories, wherein the one or more processors enable the device: Receiving an uplink grant that schedules the transmission of an uplink shared channel using a first number of symbols — said uplink grant identifies at least a first uplink transmission opportunity and a second uplink transmission opportunity in which said uplink shared channel is to be transmitted, said first uplink transmission opportunity comprises a second number of symbols fewer than said first number of symbols allocated to said uplink shared channel, said second number of symbols define said first uplink transmission opportunity as a non-nominal repetition —; Based at least partially on the fact that the first uplink transmission opportunity includes the second number of symbols, the first uplink transmission opportunity is to multiplex uplink control information (UCI) on the uplink shared channel — the UCI includes ACK / NACK (acknowledgement / negative-acknowledgement) feedback —; and A device capable of operating individually or collectively to execute code that transmits the UCI and the uplink shared channel, including the ACK / NACK feedback, during the non-nominal repetition of the first uplink transmission opportunity.

Images