BETA offset factor configuration for uplink control information multiplexing on the physical uplink shared channel

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may select a set (represented in a table) from a plurality of sets (tables) including beta offset factors associated with multiplexing UCI with data on PUSCH based at least in part on a priority level of uplink control information (UCI) and a priority level of data on a physical uplink shared channel (PUSCH). The UE may select a beta offset factor from the selected set based on a type of UCI. The UE may multiplex UCI with data in an uplink communication on PUSCH based at least in part on the selected beta offset factor. The UE may send an uplink communication. Many other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 706,935, filed on September 18, 2020, entitled “BETA OFFSET FACTOR CONFIGURATION FOR UPLINK CONTROL INFORMATION MULTIPLEXING ON PHYSICAL UPLINK SHARED CHANNEL,” and U.S. Non-Provisional Patent Application No. 17 / 447,458, filed on September 13, 2021, entitled “BETA OFFSET FACTOR CONFIGURATION FOR UPLINK CONTROL INFORMATION MULTIPLEXING ON A PHYSICAL UPLINK SHARED CHANNEL,” which are hereby expressly incorporated herein by reference Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for beta offset factor configuration for uplink control information multiplexing on a physical uplink shared channel. Background Art

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

[0005] A wireless network may include multiple base stations (BSs) that may support communications for multiple user equipments (UEs). A UE may communicate with a BS via a downlink and an uplink. A "downlink" (or "forward link") refers to a communication link from a BS to a UE, and an "uplink" (or "reverse link") refers to a communication link from a UE to a BS. As will be described in detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, or 5G Node B.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at municipal, national, regional and even global levels. NR (also known as 5G) is a set of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), and using CP-OFDM or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL) to better integrate with other open standards; also supports beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there is a need for further improvements to LTE, NR and other radio access technologies. Summary of the invention

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: selecting a set (e.g., a table) from among a plurality of sets (tables) including beta offset factors associated with multiplexing the UCI with the data on a physical uplink shared channel (PUSCH) based at least in part on a priority level of uplink control information (UCI) and a priority level of data on the PUSCH. The method includes: selecting a beta offset factor from the selected set according to a type of the UCI; multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and transmitting the uplink communication.

[0008] In some aspects, a wireless communication method performed by a base station includes: determining a plurality of sets of beta offset factors for multiplexing UCI with data on a PUSCH; and sending configuration information associated with the plurality of sets to a UE, so that the UE is configured to select a beta offset factor from the plurality of sets for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH. The method includes: receiving the uplink communication having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

[0009] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: select a set from a plurality of sets including beta offset factors associated with multiplexing the UCI with the data on the PUSCH based at least in part on a priority level of UCI and a priority level of data on the PUSCH. The one or more processors are configured to: select a beta offset factor from the selected set according to a type of the UCI, multiplex the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor, and transmit the uplink communication.

[0010] In some aspects, a base station for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: determine a plurality of sets having beta offset factors for multiplexing UCI with data on a PUSCH; and send configuration information associated with the plurality of sets to a UE, such that the UE is configured to select a beta offset factor from the plurality of sets for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH. The one or more processors are configured to: receive the uplink communication having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: select a set from multiple sets including beta offset factors associated with multiplexing the UCI with the data on the PUSCH based at least in part on a priority level of the UCI and a priority level of data on the PUSCH; select a beta offset factor from the selected set according to a type of the UCI; multiplex the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and send the uplink communication.

[0012] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: determine multiple sets of beta offset factors for multiplexing UCI with data on a PUSCH; send configuration information associated with the multiple sets to a UE, so that the UE is configured to select a beta offset factor from the multiple sets for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH; and receive the uplink communication having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

[0013] In some aspects, an apparatus for wireless communication includes: a unit for selecting a set from multiple sets including beta offset factors associated with multiplexing the UCI with the data on the PUSCH based at least in part on a priority level of UCI and a priority level of data on the PUSCH; a unit for selecting the beta offset factor from the selected set according to a type of the UCI; a unit for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and a unit for sending the uplink communication.

[0014] In some aspects, an apparatus for wireless communication includes: a unit for determining multiple sets of beta offset factors for multiplexing UCI with data on a PUSCH; a unit for sending configuration information associated with the multiple sets to a UE, so that the UE is configured to select a beta offset factor from the multiple sets for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH; and a unit for receiving the uplink communication having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

[0015] As substantially described with reference to and as illustrated in the accompanying drawings and description, aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the subsequent detailed description may be better understood. Other features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features of the concepts disclosed herein (their organization and method of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above can be obtained by reference to various aspects, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, because the description may allow for other equivalent aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0019] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3An example of uplink control information (UCI) multiplexing according to the present disclosure is shown.

[0021] Figure 4 is a diagram illustrating an example of a beta shift factor table according to the present disclosure.

[0022] Figure 5 is a diagram showing an example of a beta shift factor table for different priorities according to the present disclosure.

[0023] Figure 6 is a diagram showing an example of a beta offset factor configuration for UCI multiplexing on a physical uplink shared channel (PUSCH) according to the present disclosure.

[0024] Figure 7 is a diagram illustrating an example of a beta shift factor table according to the present disclosure.

[0025] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0026] Fig. 9 is a diagram illustrating an example process performed, for example, by a base station according to the present disclosure.

[0027] Figure 10-11 is a block diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. Instead, these aspects are provided so that the present disclosure is thorough and complete, and the scope of the present disclosure is fully conveyed to those skilled in the art. Based on the teachings of this article, a person skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or combined with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or not. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

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

[0030] It should be noted that although terms generally associated with 5G or NR radio access technologies (RATs) may be used herein to describe various aspects, various aspects of the present disclosure may be applicable to networks based on other RATs, such as 3G RATs, 4G RATs and / or RATs after 5G (e.g., 6G).

[0031] Figure 1 is a diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, etc. The wireless network 100 may include a plurality of base stations 110 (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, or transmit receive point (TRP). Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0033] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (e.g., direct physical connections using any suitable transport network, or virtual networks).

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

[0035] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, and / or relay BSs). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0036] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly via a wireless or wired backhaul.

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

[0038] Some UEs may be considered as machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, a connection to a network (e.g., a wide area network such as the Internet or a cellular network) or a connection to the network via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120 (such as processor components, and / or memory components). In some aspects, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, electrically coupled, and the like.

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

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

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may span 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2), which may span 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as intermediate frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz" band. Similarly, FR2 is often referred to as a "millimeter wave" band, but it is different from the ultra-high frequency (EHF) band (30 GHz–300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise expressly stated, it should be understood that the term "sub-6 GHz" and the like, if used herein, can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or intermediate frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise expressly stated, it should be understood that the term "millimeter wave" and the like, if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] As noted above, Figure 1 is provided as an example. Other examples may differ from those described above. Figure 1 Examples described.

[0043] Figure 2is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t and UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0044] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively.

[0045] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or by other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), and / or CQI, etc. In some aspects, one or more components of the UE 120 may be included in the housing 284.

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

[0047] Among other examples, antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include or may be included within one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antennas coupled to one or more transmitting components and / or receiving components (e.g. Figure 2 One or more antenna elements of one or more components).

[0048] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM), and transmitted to the base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be configured by a processor (e.g., controller / processor 280) and memory 282 to perform operations described herein (e.g., as described with reference to FIG. 1 ). Figure 3-11 Aspects of any method described).

[0049] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modulators and / or demodulators 232, MIMO detectors 236, receive processors 238, transmit processors 220, and / or TX MIMO processors 230. The transceiver may be configured by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., as described with reference to FIG. 1 ). Figure 3-11 Aspects of any method described).

[0050] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the base station 110 may perform one or more techniques associated with beta offset factor configuration for uplink control information (UCI) multiplexing on a physical uplink shared channel (PUSCH), as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component may perform or direct e.g. Figure 8 The process of 800 Fig. 9 The operations of process 900 and / or other processes described herein may be performed by the memory 242 and 282. The memory 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some aspects, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station 110 and / or the UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), may cause the one or more processors, the UE 120 and / or the base station 110 to perform or direct operations such as the following: Figure 8 The process of 800 Fig. 9 The process 900 and / or other processes described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0051] In some aspects, the UE 120 includes: means for selecting a set (table) from a plurality of sets (tables) including beta offset factors associated with multiplexing the UCI with the data on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH; means for selecting the beta offset factor from the selected set (table) according to the type of the UCI; means for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and / or means for transmitting the uplink communication. The means for the UE 120 to perform the operations described herein may include, for example, an antenna 252, a demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, and / or a memory 282.

[0052] In some aspects, the base station 110 includes: means for determining a plurality of sets of beta offset factors for multiplexing UCI with data on a PUSCH; means for sending configuration information associated with the plurality of sets to a UE such that the UE is configured to select a beta offset factor from the plurality of sets for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH; and / or means for receiving the uplink communication having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor. Means for the base station 110 to perform operations described herein may include, for example, a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, and / or a scheduler 246.

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

[0054] As mentioned above, providing Figure 2 As an example. Other examples may differ from the Figure 2 An example of description.

[0055] Figure 3 is a diagram illustrating an example 300 for performing UCI multiplexing according to the present disclosure.

[0056] The UE may send UCI to the base station on a physical uplink control channel (PUCCH). The base station may use feedback in the UCI, such as a hybrid automatic repeat request (HARQ) acknowledgement (ACK), to configure and / or schedule communications for the UE. Example 300 illustrates UCI on the PUCCH and uplink shared data (UL-SCH) on the PUSCH. When the PUCCH overlaps in time with data to be sent on the PUSCH, the PUCCH transmission may be discarded, as shown by the crossed-out PUCCH in Example 300. However, the UCI to be carried on the PUCCH may be multiplexed with data on the PUSCH, as shown in Example 300. The UE may send the multiplexed UCI and data on the PUSCH.

[0057] Data on the PUSCH may have to share resource elements (REs) in the PUSCH with UCI, and therefore UCI may be provided on some REs on the PUSCH according to a particular spectral efficiency. "Spectral efficiency" may refer to how many REs are allocated. The amount of UCI multiplexed with data on the PUSCH may be too much or not enough, and the UE may increase or decrease the spectral efficiency of UCI when multiplexing UCI on the PUSCH. For example, the UE may increase the amount of REs used for UCI when UCI is multiplexed with data on the PUSCH, which results in higher reliability for UCI but a greater impact on the data on the PUSCH. The amount of REs used for UCI may be based on a beta offset factor to set it up, as shown in the following example equation:

[0058]

[0059] In this example equation, Q′ ACK Indicates the amount of REs assigned to HARQ-ACK. ACK represents the amount of ACK bits, and L ACK Indicates the cyclic redundancy check bits for ACK. Indicates the total number of REs allocated for PUSCH. represents the amount of bits used for PUSCH. The α in the term after the comma is used as an upper limit for the amount of REs. In summary, this equation specifies the ratio of the amount of bits used for ACK to the total amount of bits used for PUSCH to determine how many REs to allocate for ACK. beta offset factor The larger the beta offset factor is, the lower the spectrum efficiency of UCI is with respect to the spectrum efficiency of data. That is, the larger the beta offset factor is, the more REs are used for UCI.

[0060] As shown above, provide Figure 3 As an example. Other examples may differ from Figure 3 An example of description.

[0061] Figure 4 is a diagram illustrating an example 400 of a beta shift factor table in accordance with the present disclosure.

[0062] The base station may configure a beta offset factor set for the UE via a radio resource control (RRC) message, and example 400 illustrates an example framework for such a set. The beta offset factor set may include one or more beta offset factors for different bit amounts for HARQ-ACK, for CSI part 1, and / or for CSI part 2. The beta offset factor set may be represented in a table. The table may be applied to a configured grant (CG) PUSCH, or a dynamically granted (DG) scheduled PUSCH. Figure 4 The table in is an example applicable to CG PUSCH and lists entries for each UCI type (represented by letters A to G), including HARQ-ACK of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, channel state information (CSI) part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and / or CSI part 2 greater than 11 bits. The entry for beta offset can be semi-static.

[0063] UCI and PUSCH may have different priorities, so that the priority for UCI may be higher or lower than the priority for data on PUSCH. In some aspects, UCI may specifically have a high priority or a low priority, and the data on PUSCH may have a high priority or a low priority. The priority level may be indicated by a value such as 0 (zero) or 1 (one). However, there is currently a beta factor offset table that does not take into account multiplexing with different priorities. If high priority communications are not multiplexed with enough REs, important control information or data may be lost or delayed. Communications may be degraded or experience additional delays. Retransmissions may be necessary and cause the UE to waste power, processing resources, and signaling resources.

[0064] As shown above, provide Figure 4 As an example. Other examples may differ from Figure 4 An example of description.

[0065] Figure 5 is a diagram illustrating an example 500 of a beta shift factor table for different priority levels in accordance with the present disclosure.

[0066] According to various aspects described herein, a base station (e.g., a gNB) can configure a UE with multiple beta offset factor sets (which can be represented in a table) to be used for different priority combinations. In this way, an appropriate beta offset factor can be selected so that a certain amount of REs can be allocated to UCIs that are consistent with the priority of the UCI relative to the priority of data on the PUSCH. The UE can avoid degraded communications, reduce latency, and save power, processing resources, and signaling resources (otherwise, these power, processing resources, and signaling resources will be consumed by later or retransmitted high priority communications that should have been allocated more REs).

[0067] The multiple beta offset sets (tables) configured at the UE may include: Figure 5 As shown in Table 1, the UE may select Table 1 based at least in part on the priority level of UCI being low and the priority level of data on PUSCH being low. Table 2 shows a table selected based at least in part on the priority level of UCI being low and the priority level of data on PUSCH being high. Table 3 shows a table selected based at least in part on the priority level of UCI being high and the priority level of data on PUSCH being low. Table 4 shows a table selected based at least in part on the priority level of UCI being high and the priority level of data on PUSCH being high. Each of these tables may include an entry for a beta offset factor appropriate for the priority of the table.

[0068] As shown above, provide Figure 5 As an example. Other examples may differ from Figure 5 An example of description.

[0069] Figure 6 6 is a diagram illustrating an example 600 of a beta offset factor configuration for UCI multiplexing on PUSCH according to the present disclosure. Figure 6 As shown in FIG. 6 , example 600 includes a BS 610 (e.g., Figure 1 and 2 BS 110) and UE 620 (eg, in Figure 1 and 2 In some aspects, BS 610 and UE 620 may be included in a wireless network, such as wireless network 100. BS 610 and UE 620 may communicate over a wireless access link, which may include an uplink and a downlink.

[0070] As shown in reference numeral 630, BS 610 may determine a plurality of beta offset factor sets (tables) for multiplexing UCI with data on PUSCH. Figure 5As described, the tables may include tables selected based on different priority combinations for UCI and for data on PUSCH. As indicated by reference numeral 635, BS 610 may send configuration information associated with the table to UE 620. For example, BS 610 may send the table or information indicating the table to UE 620. In some aspects, UE 620 may have a table based at least in part on stored configuration information, and the information from BS 610 may indicate the table to be used.

[0071] The UE 620 may be configured with specific priority levels for UCI and for data on the PUSCH. In some aspects, the UE 620 may be configured for CG PUSCH, and the priority level of the UCI and / or the priority level of the data on the PUSCH may be configured by an RRC message. In some aspects, the UE 620 may be configured for DG for HARQ-ACK multiplexed on the CGPUSCH, and the priority level of the UCI (e.g., HARQ-ACK) may be configured by downlink control information (DCI), and the priority level of the data on the PUSCH may be configured by an RRC message. In some aspects, the UE 620 may be configured for persistent channel state information (P-CSI) feedback, and the priority level of the UCI and / or the priority level of the data on the PUSCH may be configured by an RRC message.

[0072] As shown by reference numeral 640, UE 620 may select a set (table) from among a plurality of sets (tables) of beta offset factors based at least in part on the priority level of UCI and the priority level of data on PUSCH. For example, if the priority level of UCI is low and the priority level of data on PUSCH is high, UE 620 may select a set (table) such as Figure 5 The table shown in Table 2.

[0073] As shown by reference numeral 645, UE 620 may select a beta offset factor from the selected set (table). This selection may be made based on the type of UCI. For example, if Figure 5 2, and if the UCI is a HARQ-ACK greater than 11 bits, the UE 620 may select the beta offset factor as an entry in the 4th column of Table 2.

[0074] As shown in reference numeral 650, UE 620 may multiplex UCI with data on PUSCH in uplink communications on PUSCH based at least in part on the selected beta offset factor. As shown in reference numeral 655, UE 620 may send uplink communications to BS 610. BS 610 may demultiplex uplink communications received on PUSCH to obtain UCI (e.g., HARQ-ACK) on one or more REs in the uplink communications and data on other REs of the uplink communications. To continue using the example of Table 2, the uplink communications may include, for example, a majority of data REs and only one or two UCI REs because UCI is of low priority and data is of high priority. By using a beta offset factor that does not take into account UCI priority and data priority, a beta offset factor selected from Table 2 may be used by BS 610 to receive higher priority data.

[0075] As shown above, provide Figure 6 As an example. Other examples may differ from Figure 6 An example of description.

[0076] Figure 7 is a diagram illustrating an example 700 of a beta shift factor table in accordance with the present disclosure.

[0077] Figure 7 Several beta shift factor tables are shown, including the Figure 5 However, in some aspects, when the priority level of UCI is the same as the priority level of data on PUSCH, Figure 5 Table 1 and Table 4 can be combined into one table, such as Figure 7 Other tables may be configured for other priority combinations, including for priorities other than "low" and "high".

[0078] As shown above, provide Figure 7 As an example. Other examples may differ from Figure 7 An example of description.

[0079] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE according to the present disclosure. The example process 800 is a diagram in which a UE (for example, Figure 1-2 UE 120 depicted in Figure 6 An example of a UE 620 depicted in FIG. 6 performing operations associated with a beta offset factor configuration for UCI multiplexing on a PUSCH.

[0080] like Figure 8As shown, in some aspects, process 800 may include selecting a set from among a plurality of sets including beta offset factors associated with multiplexing UCI with data on PUSCH based at least in part on a priority level of UCI and a priority level of data on PUSCH (block 810). Fig.10 The selection component 1008 depicted in can select a set from multiple sets including beta offset factors associated with multiplexing UCI with data on PUSCH based at least in part on the priority level of UCI and the priority level of data on PUSCH, as described above.

[0081] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include selecting a beta offset factor from a selected set based on the type of UCI (block 820). Fig.10 The selection component 1008 depicted in FIG. 1004 may select a beta offset factor from the selected set based on the type of UCI, as described above.

[0082] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include multiplexing UCI with data in uplink communications on the PUSCH based at least in part on the selected beta offset factor (block 830). Fig.10 The multiplexer component 1010 depicted in FIG. 1 may multiplex UCI with data in uplink communications on the PUSCH based at least in part on the selected beta offset factor, as described above.

[0083] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending an uplink communication (block 840). For example, as described above, a UE (e.g., using Fig.10 The sending component 1004 depicted in can send uplink communications.

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

[0085] In a first aspect, the plurality of sets include a set selected at least in part based on the UCI priority level being low and the priority level of data on a PUSCH being low, a set selected at least in part based on the UCI priority level being low and the priority level of data on a PUSCH being high, a set selected at least in part based on the UCI priority level being high and the priority level of data on a PUSCH being low, and a set selected at least in part based on the UCI priority level being high and the priority level of data on a PUSCH being high.

[0086] In a second aspect, alone or in combination with the first aspect, the plurality of sets include a set selected at least in part based on the priority level of the UCI and the priority level of the data on the PUSCH being the same, a set selected at least in part based on the priority level of the UCI being low and the priority level of the data on the PUSCH being high, and a set selected at least in part based on the priority level of the UCI being high and the priority level of the data on the PUSCH being low.

[0087] In a third aspect, either alone or in combination with one or more of the first and second aspects, selecting a beta offset factor from a selected set according to the type of UCI comprises: selecting a beta offset factor from a plurality of types of UCI, the plurality of types of UCI comprising HARQ-ACK of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, CSI part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and CSI part 2 greater than 11 bits.

[0088] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the UE is configured for CGPUSCH, and at least one of the priority level of UCI or the priority level of data on PUSCH is configured by an RRC message.

[0089] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the UE is configured for DG for HARQ-ACK multiplexed on CG PUSCH, and the priority level of UCI is configured by DCI, and the priority level of data on PUSCH is configured by RRC message.

[0090] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the UE is configured for P-CSI feedback, and at least one of the priority level of UCI or the priority level of data on PUSCH is configured by an RRC message.

[0091] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, multiplexing the UCI with the data comprises setting a spectral efficiency of the UCI based at least in part on a beta shift factor.

[0092] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, setting the spectral efficiency of UCI based at least in part on a beta offset factor comprises setting an amount of resource elements to be used for UCI when multiplexing UCI with data on a PUSCH.

[0093] although Figure 8 Example blocks of process 800 are shown, but in some aspects process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 800. Additionally or alternatively, two or more blocks of process 800 can be executed in parallel.

[0094] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a base station according to the present disclosure. The example process 900 is a diagram in which a base station (for example, Figure 1-2 The base station 110 depicted in Figure 6 An example of BS 610) depicted in FIG. 6 performing operations associated with beta offset factor configuration for UCI multiplexing on PUSCH.

[0095] like Fig. 9 As shown in , in some aspects, process 900 may include determining a plurality of sets of beta offset factors for multiplexing UCI with data on PUSCH (block 910). For example, as described above, a base station (e.g., using Fig.11 The determining component 1108 depicted in FIG. 1 can determine multiple sets of beta offset factors for multiplexing UCI with data on PUSCH.

[0096] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include sending configuration information associated with the plurality of sets to the UE, such that the UE is configured to select a beta offset factor from the plurality of sets for multiplexing UCI with data in uplink communications on the PUSCH based at least in part on a priority level of the UCI and a priority level of data on the PUSCH (block 920). For example, as described above, the base station (e.g., using Fig.11The transmitting component 1104 depicted in the figure can send configuration information associated with multiple sets to the UE, so that the UE is configured to select a beta offset factor from the multiple sets for multiplexing UCI with data in uplink communication on the PUSCH based at least in part on the priority level of the UCI and the priority level of the data on the PUSCH.

[0097] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include receiving an uplink communication having UCI and data multiplexed on a PUSCH (block 930). For example, as described above, a base station (e.g., using Fig.11 The receiving component 1102 depicted in FIG. 1 may receive an uplink communication having UCI and data multiplexed on a PUSCH. In some aspects, the UCI and data are multiplexed based at least in part on a selected beta offset factor.

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

[0099] In a first aspect, the plurality of sets include a set selected at least in part based on the UCI priority level being low and the priority level of data on a PUSCH being low, a set selected at least in part based on the UCI priority level being low and the priority level of data on a PUSCH being high, a set selected at least in part based on the UCI priority level being high and the priority level of data on a PUSCH being low, and a set selected at least in part based on the UCI priority level being high and the priority level of data on a PUSCH being high.

[0100] In a second aspect, alone or in combination with the first aspect, the plurality of sets include a set selected at least in part based on the priority level of the UCI and the priority level of the data on the PUSCH being the same, a set selected at least in part based on the priority level of the UCI being low and the priority level of the data on the PUSCH being high, and a set selected at least in part based on the priority level of the UCI being high and the priority level of the data on the PUSCH being low.

[0101] In a third aspect, either alone or in combination with one or more of the first and second aspects, each of the multiple sets includes beta offset factors for multiple types of UCI, wherein the multiple types of UCI include HARQ-ACK of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, CSI part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and CSI part 2 greater than 11 bits.

[0102] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the UE is configured for CG PUSCH, and process 900 further comprises sending an RRC message indicating at least one of a priority level of UCI or a priority level of data on PUSCH.

[0103] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the UE is configured for a DG for HARQ-ACK multiplexed on a CG PUSCH, and process 900 also includes sending a DCI indicating a priority level of the UCI and sending an RRC message indicating a priority level of data on the PUSCH.

[0104] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the UE is configured for P-CSI feedback, and process 900 further comprises sending an RRC message indicating at least one of a priority level of the UCI or a priority level of data on the PUSCH.

[0105] although Fig. 9 Example blocks of process 900 are shown, but in some aspects process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 900. Additionally or alternatively, two or more blocks of process 900 can be executed in parallel.

[0106] Fig.101 is a block diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a UE (e.g., UE 120, UE 620), or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (e.g., a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a selection component 1008 or a multiplexer component 1010, etc.

[0107] In some aspects, the apparatus 1000 may be configured to perform the Figure 3-9 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, Fig.10 The apparatus 1000 and / or one or more components shown in the figure may include the above combined Figure 2 One or more components of the UE described. Additionally or alternatively, Fig.10 One or more of the components shown in the above may be combined Figure 2 In addition or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and is executable by a controller or processor to perform the function or operation of the component.

[0108] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include the above in combination with Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a UE are described.

[0109] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1006. In some aspects, one or more other components of the apparatus 1006 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the apparatus 1006. In some aspects, the transmitting component 1004 may perform signal processing (e.g., filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1006. In some aspects, the transmitting component 1004 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1004 can be collocated with the receive component 1002 in a transceiver.

[0110] The selecting component 1008 can select a set from among a plurality of sets including beta offset factors associated with multiplexing the UCI with the data of the PUSCH based at least in part on the priority level of the UCI and the priority level of the data on the PUSCH. In some aspects, the selecting component 1008 can include the above in conjunction with Figure 2 A controller / processor, a memory, or a combination thereof of the described UE. The selecting component 1008 can select a beta offset factor from the selected set based on the type of UCI.

[0111] The multiplexer component 1010 may multiplex the UCI with the data in the uplink communication on the PUSCH based at least in part on the selected beta offset factor. In some aspects, the multiplexer component 1010 may include the above in combination with Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE.The transmit component 1004 may transmit uplink communications.

[0112] Fig.10 The number and arrangement of components shown in are provided as examples. Fig.10 There may be additional components, fewer components, different components, or components arranged differently than those shown in FIG. Fig.10 Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 A component set (one or more components) shown in FIG. 1 can perform one or more functions, and the one or more functions are described as being Fig.10 Another component set shown in is executed.

[0113] Fig.11 1 is a block diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a base station (e.g., BS 110, BS 610), or a base station may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (e.g., a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a determining component 1108, etc.

[0114] In some aspects, the apparatus 1100 may be configured to perform the Figure 3-9 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 In some aspects, in Fig.11 The apparatus 1100 and / or one or more components shown in the figure may include the above combined Figure 2 Additionally or alternatively, in Fig.11 One or more of the components shown in the above may be combined Figure 2 In addition or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and is executable by a controller or processor to perform the function or operation of the component.

[0115] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include the above in combination with Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a base station are described.

[0116] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described base stations. In some aspects, the transmit component 1104 can be collocated with the receive component 1102 in a transceiver.

[0117] The determining component 1108 may determine a plurality of sets of beta offset factors for multiplexing UCI with data on the PUSCH. In some aspects, the determining component 1108 may include the above in conjunction with Figure 2 A controller / processor, a memory, or a combination thereof of a base station described herein. A transmitting component 1104 may transmit configuration information associated with a plurality of sets to a UE, so that the UE is configured to select a beta offset factor from the plurality of sets for multiplexing UCI with data in an uplink communication of a PUSCH based at least in part on a priority level of the UCI and a priority level of data on a PUSCH. A receiving component 1102 may receive an uplink communication having UCI and data multiplexed on a PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

[0118] Fig.11 The number and arrangement of components shown in are provided as examples. Fig.11 There may be additional components, fewer components, different components, or components arranged differently than those shown in FIG. Fig.11 Two or more components shown in may be implemented in a single component, or Fig.11 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.11 A component set (one or more components) shown in FIG. 1 can perform one or more functions, and the one or more functions are described as being Fig.11 Another component set shown in is executed.

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

[0120] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: selecting a set (table) from multiple sets (tables) including beta offset factors associated with multiplexing the UCI with the data on the physical uplink shared channel (PUSCH) based at least in part on a priority level of uplink control information (UCI) and a priority level of data on the PUSCH; selecting a beta offset factor from the selected set (table) according to a type of the UCI; multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and sending the uplink communication.

[0121] Aspect 2: A method according to Aspect 1, wherein the multiple sets (tables) include a set (table) selected at least in part based on the UCI having a low priority level and the data on the PUSCH having a low priority level, a set (table) selected at least in part based on the UCI having a low priority level and the data on the PUSCH having a high priority level, a set (table) selected at least in part based on the UCI having a high priority level and the data on the PUSCH having a low priority level, and a set (table) selected at least in part based on the UCI having a high priority level and the data on the PUSCH having a high priority level.

[0122] Aspect 3: A method according to Aspect 1, wherein the multiple sets (tables) include a set (table) selected at least in part based on the priority level of the UCI and the priority level of the data on the PUSCH being the same, a set (table) selected at least in part based on the priority level of the UCI being low and the priority level of the data on the PUSCH being high, and a set (table) selected at least in part based on the priority level of the UCI being high and the priority level of the data on the PUSCH being low.

[0123] Aspect 4: A method according to any one of Aspects 1-3, wherein selecting the beta offset factor from the selected set according to the type of the UCI includes: selecting the beta offset factor from multiple types of UCI, the multiple types of UCI including: hybrid automatic repeat request acknowledgment (HARQ-ACK) of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, channel state information (CSI) part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and CSI part 2 greater than 11 bits.

[0124] Aspect 5: The method according to any one of Aspects 1-4, wherein the UE is configured to be configured to grant PUSCH, and wherein at least one of the priority level of the UCI or the priority level of the data on the PUSCH is configured by a radio resource control message.

[0125] Aspect 6: A method according to any one of Aspects 1-5, wherein the UE is configured for dynamic grant of a hybrid automatic repeat request acknowledgment (HARQ-ACK) multiplexed on a configured granted PUSCH, and wherein the priority level of the UCI is configured by downlink control information, and the priority level of the data on the PUSCH is configured by a radio resource control message.

[0126] Aspect 7: A method according to any one of Aspects 1-6, wherein the UE is configured for persistent channel state information (CSI) feedback, and wherein at least one of the priority level of the UCI or the priority level of the data on the PUSCH is configured by a radio resource control message.

[0127] Aspect 8: The method according to any one of aspects 1-7, wherein multiplexing the UCI with the data comprises: setting a spectral efficiency of the UCI based at least in part on the beta shift factor.

[0128] Aspect 9: The method according to aspect 8, wherein setting the spectral efficiency of the UCI based at least in part on the beta offset factor includes: setting an amount of resource elements to be used for the UCI when multiplexing the UCI with the data on the PUSCH.

[0129] Aspect 10: A method of wireless communication performed by a base station, comprising: determining multiple sets (tables) of beta offset factors for multiplexing uplink control information (UCI) with data on a physical uplink shared channel (PUSCH); sending configuration information associated with the multiple sets (tables) to a user equipment (UE), so that the UE is configured to select a beta offset factor from the multiple sets (tables) for multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on a priority level of the UCI and a priority level of the data on the PUSCH; and receiving the uplink communication having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed at least in part based on the selected beta offset factor.

[0130] Aspect 11: A method according to Aspect 10, wherein the multiple sets (tables) include a set (table) selected at least in part based on the UCI having a low priority level and the data on the PUSCH having a low priority level, a set (table) selected at least in part based on the UCI having a low priority level and the data on the PUSCH having a high priority level, a set (table) selected at least in part based on the UCI having a high priority level and the data on the PUSCH having a low priority level, and a set (table) selected at least in part based on the UCI having a high priority level and the data on the PUSCH having a high priority level.

[0131] Aspect 12: A method according to Aspect 10, wherein the multiple sets (tables) include a set (table) selected at least in part based on the priority level of the UCI and the priority level of the data on the PUSCH being the same, a set (table) selected at least in part based on the priority level of the UCI being low and the priority level of the data on the PUSCH being high, and a set (table) selected at least in part based on the priority level of the UCI being high and the priority level of the data on the PUSCH being low.

[0132] Aspect 13: The method of any one of Aspects 10-12, wherein each of the multiple sets (tables) includes beta offset factors for multiple types of UCI, and the multiple types of UCI include: hybrid automatic repeat request acknowledgment (HARQ-ACK) of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, channel state information (CSI) part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and CSI part 2 greater than 11 bits.

[0133] Aspect 14: A method according to any one of Aspects 10-13, wherein the UE is configured to be configured to grant PUSCH, and wherein the method further comprises sending a radio resource control message indicating at least one of a priority level of the UCI or a priority level of the data on the PUSCH.

[0134] Aspect 15: A method according to any one of Aspects 10-14, wherein the UE is configured for dynamic grant of a hybrid automatic repeat request acknowledgment (HARQ-ACK) multiplexed on a configured granted PUSCH, and wherein the method further comprises: sending downlink control information indicating the priority level of the UCI, and sending a radio resource control message indicating the priority level of the data on the PUSCH.

[0135] Aspect 16: A method according to any one of Aspects 10-15, wherein the UE is configured for persistent channel state information (CSI) feedback, and wherein the method further comprises: sending a radio resource control message indicating at least one of the priority level of the UCI or the priority level of the data on the PUSCH.

[0136] Aspect 17: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1-16.

[0137] Aspect 18: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1-16.

[0138] Aspect 19: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more of aspects 1-16.

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

[0140] Aspect 21: A non-transitory computer-readable medium storing an instruction set (table) for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 1-16.

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

[0142] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc., whether referring to software, firmware, middleware, microcode, hardware description languages, etc. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

[0143] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it should be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

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

[0145] Although the specific combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner not specifically stated in the claims and / or disclosed in the specification. Although each dependent claim listed below can directly rely on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one" in the reference item list refers to any combination of those items, including a single member. As an example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc and any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc or any other ordering of a, b and c).

[0146] Unless explicitly stated, any element, action or instruction used in this article should not be interpreted as critical or necessary. In addition, as used herein, the articles "one" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects related to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set (set)" and "group (group)" are intended to include one or more projects (for example, related projects, unrelated projects, combinations of related and unrelated projects), and can be used interchangeably with "one or more". In the case of only wanting a project, the term "only one" or similar language is used. In addition, as used herein, the terms "have", "have", "contain" etc. are intended to be open terms. In addition, unless explicitly stated otherwise, the phrase "based on" is intended to mean "based at least in part". Furthermore, as used herein, the term "or" when used in series is intended to be inclusive and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in combination with "each" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: one or more memories; as well as one or more processors operatively coupled to the one or more memories, the one or more processors being configured to: selecting a set of beta offset factors from a plurality of sets of beta offset factors associated with multiplexing uplink control information (UCI) with data on a physical uplink shared channel (PUSCH), wherein the set of beta offset factors is selected from the plurality of sets of beta offset factors using a priority level of the UCI and a priority level of the data on the PUSCH; selecting a beta offset factor from a selected set of a plurality of beta offset factors according to the type of the UCI; multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and The uplink communication is transmitted.

2. The UE according to claim 1, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is low, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is high.

3. The UE according to claim 1, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI and the priority level of the data on the PUSCH are the same, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low.

4. The UE according to claim 1, wherein: The UE is configured to be configured to grant a PUSCH, and wherein at least one of a priority level of the UCI or a priority level of the data on the PUSCH is configured by a radio resource control message.

5. The UE according to claim 1, wherein: The UE is configured for dynamic grant of a hybrid automatic repeat request acknowledgement (HARQ-ACK) multiplexed on a configured grant PUSCH, and wherein the priority level of the UCI is configured by downlink control information and the priority level of the data on the PUSCH is configured by a radio resource control message.

6. The UE according to claim 1, wherein: The UE is configured for persistent channel state information (CSI) feedback, and wherein at least one of a priority level of the UCI or a priority level of the data on the PUSCH is configured by a radio resource control message.

7. The UE according to claim 1, wherein: When multiplexing the UCI with the data, the one or more processors are configured to set a spectral efficiency of the UCI based at least in part on the beta shift factor.

8. The UE according to claim 7, wherein: When setting the spectral efficiency of the UCI based at least in part on the beta offset factor, the one or more processors are configured to set an amount of resource elements to be used for the UCI when multiplexing the UCI with the data on the PUSCH.

9. A base station for wireless communication, comprising: one or more memories; as well as one or more processors operatively coupled to the one or more memories, the one or more processors being configured to: determining a plurality of sets of a plurality of beta offset factors associated with multiplexing uplink control information (UCI) with data on a physical uplink shared channel (PUSCH); transmitting configuration information associated with the plurality of sets of beta offset factors to a user equipment (UE), such that the UE is configured to select a beta offset factor from the plurality of sets of beta offset factors for multiplexing the UCI with the data in uplink communication on the PUSCH using a priority level of the UCI and a priority level of the data on the PUSCH; as well as The uplink communication is received having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

10. The base station according to claim 9, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is low, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is high.

11. The base station according to claim 9, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI and the priority level of the data on the PUSCH are the same, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low.

12. The base station according to claim 9, wherein: The UE is configured to be configured to grant a PUSCH, and wherein the one or more processors are configured to send a radio resource control message indicating at least one of a priority level of the UCI or a priority level of the data on the PUSCH.

13. The base station according to claim 9, wherein: The UE is configured for dynamic grant of a hybrid automatic repeat request acknowledgement (HARQ-ACK) multiplexed on a configured grant PUSCH, and wherein the one or more processors are configured to: send downlink control information indicating a priority level of the UCI, and send a radio resource control message indicating a priority level of the data on the PUSCH.

14. The base station according to claim 9, wherein: The UE is configured for persistent channel state information (CSI) feedback, and wherein the one or more processors are configured to send a radio resource control message indicating at least one of a priority level of the UCI or a priority level of the data on the PUSCH.

15. A method of wireless communication performed by a user equipment (UE), comprising: selecting a set of beta offset factors from a plurality of sets of beta offset factors associated with multiplexing uplink control information (UCI) with data on a physical uplink shared channel (PUSCH), wherein the set of beta offset factors is selected from the plurality of sets of beta offset factors using a priority level of the UCI and a priority level of the data on the PUSCH; selecting a beta offset factor from a selected set of a plurality of beta offset factors according to the type of the UCI; multiplexing the UCI with the data in an uplink communication on the PUSCH based at least in part on the selected beta offset factor; and The uplink communication is transmitted.

16. The method according to claim 15, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is low, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is high.

17. The method according to claim 15, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI and the priority level of the data on the PUSCH are the same, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low.

18. The method according to claim 15, wherein: Selecting the beta offset factor from the selected set of multiple beta offset factors according to the type of the UCI includes: selecting the beta offset factor from multiple types of UCI, the multiple types of UCI including: hybrid automatic repeat request acknowledgment (HARQ-ACK) of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, channel state information (CSI) part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and CSI part 2 greater than 11 bits.

19. The method according to claim 15, wherein: The UE is configured to be configured to grant a PUSCH, and wherein at least one of a priority level of the UCI or a priority level of the data on the PUSCH is configured by a radio resource control message.

20. The method according to claim 15, wherein: The UE is configured for dynamic grant of a hybrid automatic repeat request acknowledgement (HARQ-ACK) multiplexed on a configured grant PUSCH, and wherein the priority level of the UCI is configured by downlink control information and the priority level of the data on the PUSCH is configured by a radio resource control message.

21. The method according to claim 15, wherein: The UE is configured for persistent channel state information (CSI) feedback, and wherein at least one of a priority level of the UCI or a priority level of the data on the PUSCH is configured by a radio resource control message.

22. The method according to claim 15, wherein: Multiplexing the UCI with the data includes setting a spectral efficiency of the UCI based at least in part on the beta shift factor.

23. The method according to claim 22, wherein: Setting the spectral efficiency of the UCI based at least in part on the beta offset factor includes setting an amount of resource elements to be used for the UCI when multiplexing the UCI with the data on the PUSCH.

24. A method of wireless communication performed by a base station, comprising: determining a plurality of sets of a plurality of beta offset factors associated with multiplexing uplink control information (UCI) with data on a physical uplink shared channel (PUSCH); transmitting configuration information associated with the plurality of sets of beta offset factors to a user equipment (UE), such that the UE is configured to select a beta offset factor from the plurality of sets of beta offset factors for multiplexing the UCI with the data in uplink communication on the PUSCH using a priority level of the UCI and a priority level of the data on the PUSCH; as well as The uplink communication is received having the UCI and the data multiplexed on the PUSCH, wherein the UCI and the data are multiplexed based at least in part on the selected beta offset factor.

25. The method according to claim 24, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is low, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is high.

26. The method according to claim 24, wherein: The multiple sets having multiple beta offset factors include: a set selected at least in part based on that the priority level of the UCI and the priority level of the data on the PUSCH are the same, a set selected at least in part based on that the priority level of the UCI is low and the priority level of the data on the PUSCH is high, and a set selected at least in part based on that the priority level of the UCI is high and the priority level of the data on the PUSCH is low.

27. The method according to claim 24, wherein: Each of the multiple sets having multiple beta offset factors includes beta offset factors for multiple types of UCI, the multiple types of UCI including: hybrid automatic repeat request acknowledgment (HARQ-ACK) of 2 bits or less, HARQ-ACK from 3 bits to 11 bits, HARQ-ACK greater than 11 bits, channel state information (CSI) part 1 of 11 bits or less, CSI part 1 greater than 11 bits, CSI part 2 of 11 bits or less, and CSI part 2 greater than 11 bits.

28. The method of claim 24, wherein: The UE is configured to be configured to grant a PUSCH, and wherein the method further comprises sending a radio resource control message indicating at least one of a priority level of the UCI or a priority level of the data on the PUSCH.

29. The method of claim 24, wherein: The UE is configured for dynamic grant of a hybrid automatic repeat request acknowledgement (HARQ-ACK) multiplexed on a configured grant PUSCH, and wherein the method further comprises: sending downlink control information indicating a priority level of the UCI, and sending a radio resource control message indicating a priority level of the data on the PUSCH.

30. The method of claim 24, wherein: The UE is configured for persistent channel state information (CSI) feedback, and wherein the method further comprises sending a radio resource control message indicating at least one of a priority level of the UCI or a priority level of the data on the PUSCH.

Images