Conditional uplink channel conflict resolution based on medium access control (MAC) layer prioritization

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user device may detect a conflict between a physical uplink control channel and multiple physical uplink shared channels (PUSCHs) having corresponding multiple media access control (MAC) priorities, selectively apply a MAC prioritization rule for processing multiple PUSCHs based at least in part on the corresponding multiple MAC priorities and at least in part on the impact of the multiple MAC priorities on the uplink control information (UCI) multiplexing configuration for UCI multiplexing, and selectively send at least one of the multiple PUSCHs with UCI based at least in part on the result of selectively applying the MAC prioritization rule. Many other aspects are also provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 848,525, filed on May 15, 2019, entitled “UPLINK CHANNEL COLLISION RESOLUTION FOR CONDITIONAL MEDIA ACCESS CONTROL (MAC) LAYER BASED PRIORITIZATION,” and U.S. Non-Provisional Patent Application No. 15 / 931,497, filed on May 13, 2020, entitled “UPLINK CHANNEL COLLISION RESOLUTION FOR CONDITIONAL MEDIA ACCESS CONTROL (MAC) LAYER BASED PRIORITIZATION,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and techniques and apparatus for conditional medium access control (MAC) layer prioritization-based uplink channel contention resolution. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services, such as voice, video, data, messaging, and broadcast. 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, etc.). 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 collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard released by the Third Generation Partnership Project (3GPP).

[0005] A wireless communication network may include multiple base stations (BS) that can support communication for multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from BS to UE, and uplinks (or reverse links) refer to the communication link from UE to BS. As described in more detail herein, BSs may be referred to as Node Bs, gNBs, access points (APs), radio heads, transmit receive points (TRPs), new radio (NR) BSs, 5G Node Bs, etc.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at the city, country, region, and even global level. The new radio (NR), also known as 5G, is a collection of enhancements to the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. However, as the demand for mobile broadband access continues to grow, further improvements to LTE and NR technologies are still useful. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0007] In some aspects, a wireless communication method performed by a user equipment (UE) may include detecting a conflict between a physical uplink control channel (PUCCH) and multiple physical uplink shared channels (PUSCHs) having corresponding multiple media access control (MAC) priorities, wherein the PUCCH is associated with uplink control information (UCI); selectively applying a MAC prioritization rule for processing multiple PUSCHs based at least in part on the corresponding multiple MAC priorities and at least in part on an impact of the multiple MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and selectively sending at least one of the multiple PUSCHs with UCI based at least in part on a result of selectively applying the MAC prioritization rule.

[0008] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to detect a conflict between a PUCCH and a plurality of PUSCHs having corresponding plurality of MAC priorities, wherein the PUCCHs are associated with UCI; selectively apply a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and selectively send at least one of the plurality of PUSCHs having UCI based at least in part on a result of selectively applying the MAC prioritization rule.

[0009] In some aspects, a wireless communication method performed by a base station (BS) may include determining a UCI multiplexing configuration related to a MAC prioritization rule for a scheduling conflict between a PUCCH with UCI and multiple PUSCHs with corresponding multiple MAC priorities; and receiving at least one of the multiple PUSCHs based at least in part on determining the UCI multiplexing configuration.

[0010] In some aspects, a BS for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: determine a UCI multiplexing configuration related to a MAC prioritization rule for scheduling conflicts between a PUCCH with UCI and a plurality of PUSCHs with corresponding plurality of MAC priorities; and receive at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration.

[0011] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When the one or more instructions are executed by one or more processors of a BS, the one or more instructions may cause the one or more processors to: detect a conflict between a PUCCH and a plurality of PUSCHs having corresponding plurality of MAC priorities, wherein the PUCCHs are associated with UCI; selectively apply a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and at least in part on the impact of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and selectively send at least one of the plurality of PUSCHs having UCI based at least in part on the result of selectively applying the MAC prioritization rule.

[0012] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When the one or more instructions are executed by one or more processors of a BS, the one or more instructions may cause the one or more processors to: determine a UCI multiplexing configuration related to a MAC prioritization rule for scheduling conflicts between a PUCCH with UCI and a plurality of PUSCHs with corresponding plurality of MAC priorities; and receive at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration.

[0013] In some aspects, an apparatus for wireless communication may include components for detecting a conflict between a PUCCH and multiple PUSCHs having corresponding multiple MAC priorities, wherein the PUCCHs are associated with UCI; components for selectively applying a MAC prioritization rule for processing multiple PUSCHs based at least in part on the corresponding multiple MAC priorities and at least in part on an impact of the multiple MAC priorities on a UCI multiplexing configuration for UCI multiplexing; and components for selectively sending at least one of the multiple PUSCHs having UCI based at least in part on a result of selectively applying the MAC prioritization rule.

[0014] In some aspects, an apparatus for wireless communication may include components for determining a UCI multiplexing configuration related to a MAC prioritization rule for scheduling conflicts between a PUCCH having UCI and multiple PUSCHs having corresponding multiple MAC priorities; and components for receiving at least one of the multiple PUSCHs based at least in part on determining the UCI multiplexing configuration.

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

[0016] The foregoing has summarized the features and technical advantages of the examples according to the present disclosure in a rather broad manner so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples are easily used as the 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 characteristics of the concepts disclosed herein, their methods of organization and 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, but not as a limitation to the limits of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with aspects of the present disclosure.

[0019] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a UE in a wireless communication network according to aspects of the present disclosure.

[0020] Figure 3A and Figure 3B is a diagram illustrating an example of uplink channel conflict resolution for conditional MAC layer prioritization according to aspects of the present disclosure.

[0021] Figure 4 is a diagram illustrating an example process performed, for example, by a user device, according to aspects of the present disclosure.

[0022] Figure 5 is a diagram illustrating an example process performed, for example, by a user device, according to aspects of the present disclosure. DETAILED DESCRIPTION

[0023] The various aspects of the present disclosure are described in more detail 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 presented by the entire present disclosure. On the contrary, these aspects are provided so that the present disclosure will be exhaustive and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based at least in part on the teachings of this article, those skilled in the art should appreciate that the scope of the present disclosure is intended to cover any aspect disclosed herein in the present disclosure, whether independently or in combination with any other aspect of the present disclosure to realize the aspects of the present disclosure. For example, a device or implementation method can be realized with any number of aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such a device or method, i.e., a device or method implemented using other structures, functions, or structures and functions of the various aspects of the present disclosure set forth herein in addition to or different from those set forth herein. It should be understood that any aspect disclosed herein in the present disclosure can be implemented by one or more elements of the claims.

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

[0025] It should be noted that although various aspects are described herein using terminology generally associated with 3G and / or 4G, aspects of the present disclosure may be applied to communication systems based on other generations, such as 5G and beyond, including NR technology.

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

[0027] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to 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 1 In the example shown, 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", "nodeB", "5G NB", and "cell" may be used interchangeably herein.

[0028] 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 by various types of backhaul interfaces, such as direct physical connections using any suitable transport network, virtual networks, etc.

[0029] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the illustrated example, a relay station 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 station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0030] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. 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).

[0031] 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, for example, via a wireless or wired backhaul.

[0032] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smart phones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biometric sensors / devices, wearable devices (smart watches, smart clothing, smart glasses, smart bracelets, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable device configured to communicate via wireless or wired media.

[0033] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity to a network or to a network (e.g., a wide area network such as the Internet or a cellular 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 user premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120, such as a processor component, a memory component, etc.

[0034] Generally, 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 radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. 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.

[0035] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary for mutual communication) using one or more sidelink channels. 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, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein, such as those performed by base station 110.

[0036] As mentioned above, providing Figure 1 As an example. Other examples may differ from the reference Figure 1 The content described.

[0037] Figure 2 It shows that it can be Figure 1 1. Block diagram of a design 200 of base station 110 and UE 120 for one of the base stations and one of the UEs in the FIG. 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.

[0038] At the base station 110, the transmit processor 220 may receive data from the data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indication (CQI) received from the UE, process (e.g., encode and modulate) data for each UE based at least in part on the MCS selected for the 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), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), 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)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The 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, etc.) 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. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, a synchronization signal may be generated in the case of position coding to convey additional information.

[0039] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or 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 also process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A 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. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0040] 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, CQI, etc.). 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, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by MIMO detector 236 (if applicable), and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide decoded data to a data sink 239 and 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 network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0041] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of 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 can perform or direct e.g. Figure 4 The process of 400 Figure 5 The operations of process 500 and / or other processes described herein may be performed. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule data transmissions of UEs on the downlink and / or uplink.

[0042] In some aspects, the UE 120 may include means for detecting (e.g., using the controller / processor 280, etc.) a collision between a physical uplink control channel (PUCCH) and a plurality of physical uplink shared channels (PUSCHs) having corresponding plurality of media access control (MAC) priorities, means for selectively applying (e.g., using the controller / processor 280, etc.) a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an effect of the plurality of MAC priorities on an uplink control information (UCI) multiplexing configuration for UCI multiplexing, means for selectively transmitting (e.g., using the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, etc.) at least one of the plurality of PUSCHs having UCI based at least in part on a result of the selective application of the MAC prioritization rule, etc. In some aspects, such means may include means for combining Figure 2 One or more components of UE 120 are described.

[0043] In some aspects, the base station 110 may include means for determining (e.g., using the controller / processor 240, etc.) a UCI multiplexing configuration associated with a MAC prioritization rule for scheduling conflicts between a PUCCH having UCI and a plurality of PUSCHs having corresponding plurality of MAC priorities, means for receiving (e.g., using the antenna 234, the DEMOD 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, etc.) at least one of the plurality of PUSCHs based at least in part on determining the UCI multiplexing configuration, etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of base station 110 are described.

[0044] As mentioned above, providing Figure 2 As an example. Other examples may differ from the reference Figure 2 The content described.

[0045] In some communication systems, such as NR, a UE may be scheduled to transmit multiple channels simultaneously. For example, a BS may schedule a UE to transmit a PUCCH and one or more PUSCHs using the same orthogonal frequency division multiplexing (OFDM) symbol. The UE may not be able to transmit multiple PUSCHs simultaneously or PUCCHs and PUSCHs in the same PUCCH group using a single component carrier. However, the UE may be able to transmit multiple PUSCHs simultaneously using multiple different component carriers.

[0046] Therefore, the BS may define prioritization for different channels to enable the UE to decide which channel to transmit when the UE cannot transmit multiple channels simultaneously. For example, the BS may define an Ultra Reliable Low Latency Communication (URLLC) channel as a high priority channel that may preempt other low priority channels. The BS may define channel priorities using physical (PHY) layer prioritization. For example, the BS may define a URLLC hybrid automatic repeat request acknowledgement (HARQ-ACK) with a first PHY priority, a URLLCPUSCH with a second PHY priority, an enhanced mobile broadband (eMBB) HARQ-ACK with a third PHY priority, an eMBB PUSCH with a fourth priority, and so on. In this case, the BS may explicitly or implicitly indicate the PHY priority of a specific channel using downlink control information (DCI) of a scheduling grant that schedules a specific channel.

[0047] The UE may also define channel priorities using MAC layer prioritization. For example, the UE may determine the priority of a MAC payload to be transmitted via an uplink channel, and may assign a corresponding MAC priority to the uplink channel based at least in part on the priority of the MAC payload. In some cases, an uplink channel may lack a PHY priority, and only a MAC priority may be assigned to the uplink channel. In other cases, an uplink channel may have a PHY priority, and the MAC priority may override or change the PHY priority.

[0048] When the UE is scheduled to send PUCCH and one or more higher priority PUSCHs, the UE may multiplex the UCI of the PUCCH onto the PUSCH. In this case, the UE may discard the PUCCH and send one or more higher priority PUSCHs. In this way, the UE ensures that both the UCI and the data of one or more higher priority PUSCHs can be transmitted to the BS. When PHY layer prioritization is used, the UE may select a specific PUSCH on which the UCI is multiplexed from one or more higher priority PUSCHs based at least in part on a set of fixed rules. For example, when a specific PUSCH includes an aperiodic channel state information (A-CSI) message, the UE may select the specific PUSCH to multiplex the UCI onto it. This may improve the likelihood that A-CSI and UCI are sent on the same PUSCH. Similarly, when a dynamic PUSCH and a configured PUSCH are available, the UE may select a dynamic PUSCH on which the UCI is to be multiplexed. Similarly, when selecting a PUSCH on which to multiplex UCI among multiple PUSCHs associated with multiple component carriers, the UE may select the PUSCH associated with the lowest index component carrier. Other PHY layer rules are also possible. In this way, the UE may multiplex UCI and the BS may determine which PUSCH among the multiple PUSCHs the UE multiplexes UCI onto, thereby enabling the BS to decode the multiple PUSCHs and their UCI.

[0049] However, when MAC layer prioritization is applied, the BS may not be able to determine the relative priority of each PUSCH without decoding the payload data of each PUSCH. Therefore, the BS may not be able to determine which PUSCH among multiple PUSCHs the UCI is multiplexed onto, which may prevent the BS from being able to decode the payload data of each PUSCH.

[0050] Some aspects described herein provide for conditional uplink channel conflict resolution based on MAC layer prioritization. For example, the UE may determine the impact of applying MAC priority to multiple PUSCHs on the UCI multiplexing configuration. If the UE determines that applying MAC priority will result in ambiguity in deciding which PUSCH includes UCI, the UE may determine not to apply MAC priority. Conversely, if the UE determines that using MAC priority will not result in ambiguity, the UE may determine to apply MAC priority. After determining whether to apply MAC priority, the UE may selectively send one or more PUSCHs with UCI. For example, in some cases, the UE may send one or more PUSCHs and may multiplex UCI onto one of the one or more PUSCHs. In other cases, the UE may discard one or more PUSCHs (i.e., the UE may not send one or more PUSCHs) and may send PUCCH to transmit UCI. In this way, the UE reduces the decoding processing complexity of the BS while being able to use MAC layer prioritization in some cases.

[0051] Figure 3A and Figure 3B is a diagram illustrating an example 300 for conditional MAC layer prioritization based uplink channel conflict resolution. Figure 3A and Figure 3B As shown, example 300 includes BS 110 and UE 120 .

[0052] like Figure 3A As shown in the figure numerals 305 and 310-1 to 310-N, UE 120 may receive scheduling information for sending an uplink channel. For example, BS 110 may provide and UE 120 may receive PUCCH scheduling information identifying a resource set for sending a PUCCH with UCI. Additionally or alternatively, BS 110 may provide and UE 120 may receive PUSCH scheduling information identifying a resource set for sending a PUSCH set.

[0053] In some aspects, UE 120 may request a resource set for transmitting an uplink channel. For example, UE 120 may send a scheduling request to request BS 110 to provide PUSCH scheduling information to identify the resource set. In some aspects, the uplink channel may be associated with a PHY priority set. For example, the scheduling information may include a DCI set that identifies the PHY priority set for the PUSCH set. In this case, the DCI set may include explicit information (e.g., information that explicitly indicates the PHY priority set) or implicit information (e.g., information that identifies a channel type for the uplink channel set, from which the UE 120 may implicitly derive the PHY priority set).

[0054] like Figure 3A As further shown in FIG. 315 , the UE 120 may determine that the PUCCH conflicts with at least one PUSCH. For example, the UE 120 may determine that the PUCCH is scheduled for the same OFDM symbol as the PUSCH. In some aspects, the UE 120 may determine that multiple PUSCHs in the PUSCH set are scheduled at a common time. For example, the UE 120 may determine that multiple PUSCHs are scheduled for transmission at a common time using different component carriers.

[0055] like Figure 3B As shown in the figure numerals 320 and 325, the UE 120 can determine the impact of the MAC priority of the PUSCH on the UCI multiplexing configuration, and can determine whether to apply the MAC priority to the PUSCH. For example, the UE 120 can determine whether applying the MAC priority to the PUSCH results in a change in the PUSCH onto which the UCI is to be multiplexed relative to the set of PHY priority-based rules for multiplexing UCI. In this case, the UE 120 can determine whether applying the MAC priority will cause the BS 110 to be ambiguous in deciding which PUSCH includes UCI, and in this case the ambiguity can be avoided by choosing not to apply the MAC priority. Alternatively, when the ambiguity is not the result of applying the MAC priority, the UE 120 can apply the MAC priority.

[0056] In some aspects, the UE 120 may determine that the MAC priority does not change which PUSCH includes the UCI. For example, the UE 120 may determine that when the MAC priority is used, the UCI will be multiplexed to the same specific PUSCH as when the PHY priority is used. In this case, the UE 120 may choose to use the MAC priority (e.g., for the specific PUSCH and / or for allocating payload data to other PUSCHs). In some aspects, when a specific PUSCH is selected for UCI multiplexing using a UCI multiplexing configuration and / or PHY priority, the UE 120 may determine not to discard the specific PUSCH (e.g., related to the MAC priority). For example, when each of multiple PUSCHs does not have sufficient payload data, the use of MAC priority may indicate that the UE 120 is to discard the specific PUSCH. In this case, when the specific PUSCH is the PUSCH onto which the UCI is to be multiplexed, the UE 120 may determine not to discard the specific PUSCH. In this case, the UE 120 may change the distribution of data on the multiple PUSCHs and / or may drop one or more other PUSCHs in the multiple PUSCHs. Similarly, when the UE 120 determines (e.g., based at least in part on the MAC priority) that a first subset of PUSCHs is used to send high priority data and a second subset of PUSCHs is used to send low priority data, and UCI is to be multiplexed onto a specific PUSCH used to send low priority data to be dropped, the UE 120 may avoid dropping the specific PUSCH by choosing not to use MAC priority.

[0057] In some aspects, the UE 120 may determine that the use of MAC priority results in one or more candidate UCI multiplexing configurations based at least in part on which BS 110 can determine the actual UCI multiplexing configuration. For example, the UE 120 may determine that the use of MAC priority results in a candidate UCI multiplexing configuration that is less than or equal to a threshold number (e.g., less than or equal to two candidate UCI multiplexing configurations). In this case, the UE 120 may determine to use MAC priority, thereby enabling the use of MAC priority without creating excessive processing complexity for the BS 110. In some aspects, the UE 120 may select from a plurality of different UCI multiplexing configurations. For example, the UE 120 may select from two candidate UCI multiplexing configurations (e.g., to multiplex UCI according to PHY layer rules or to send UCI on PUCCH). In this case, the UE 120 may select a MAC layer data allocation configuration (e.g., according to MAC priority) that is consistent with the selected UCI multiplexing configuration. Therefore, the UE 120 ensures that the application of MAC priority satisfies the selected UCI multiplexing scheme, which may enable the BS 110 to receive UCI according to the UCI multiplexing scheme. When UE 120 multiplexes UCI with PUSCH based at least in part on PHY layer rules, the MAC layer of UE 120 may not drop the PUSCH. In this case, the MAC layer of UE 120 may cause the PHY layer of UE 120 to send a zero transport block (e.g., a set of padding bits) to maintain the PHY structure of the PUSCH.

[0058] In some aspects, the UE 120 may determine that using MAC priority changes the UCI multiplexing configuration relative to using PHY priority, but may still determine to use MAC priority. For example, when the UE 120 determines that MAC priority results in discarding the PUSCH on which UCI is to be multiplexed (e.g., related to PHY priority), the UE 120 may determine to discard the PUSCH and include the UCI in the PUCCH. In this case, the UE 120 may send the PUCCH and may abandon sending any PUSCH that conflicts with the PUCCH. In this case, the BS 110 may attempt to detect whether the UCI is multiplexed onto the PUSCH based on PHY layer rules rather than MAC priority (e.g., which may be applied consistently with the PHY layer rules). If not, the BS 110 may determine that the UCI is sent on the PUCCH. Additionally or alternatively, the UE 120 may transmit the UCI from the PUSCH to be discarded to another PUSCH with the next lowest index (e.g., of a component carrier on which other PUSCHs are to be sent). In this case, the UE 120 may give up sending the PUCCH, but may send other PUSCHs to convey the UCI.

[0059] like Figure 3B As further shown in FIG. 330, the UE 120 may selectively transmit (e.g., transmit in some cases and not transmit in other cases) one or more PUSCHs based on determining whether to use MAC priority. For example, the UE 120 may transmit a PUSCH that multiplexes UCI into the PUSCH. In some aspects, the UE 120 may transmit multiple PUSCHs. For example, the UE 120 may transmit a first PUSCH that multiplexes UCI into the PUSCH on a first component carrier, transmit a second PUSCH on a second component carrier, and so on.

[0060] In some aspects, the UE 120 may drop the PUSCH. For example, based at least in part on the MAC priority and at least in part on determining to apply the MAC priority, the UE 120 may drop the PUSCH scheduled for transmission. Additionally or alternatively, the UE 120 may choose not to transmit any PUSCH. For example, when the UE 120 determines to drop the PUSCH onto which the UCI is to be multiplexed based at least in part on the MAC priority, the UE 120 may transmit the UCI on the PUCCH and may transmit the PUCCH instead of the PUSCH. In this case, the UE 120 may forgo transmitting any PUSCH simultaneously with the PUCCH.

[0061] In some aspects, when transmitting one or more PUSCHs, the UE 120 may determine the data to be transmitted via the one or more PUSCHs. For example, the UE 120 may multiplex the UCI onto the first PUSCH based at least in part on the PHY priority, and may use the MAC priority to determine what data to allocate to each of the second PUSCH set. In this way, the UE 120 may avoid ambiguity when the BS 110 decides which PUSCH includes the UCI (e.g., the BS 110 may determine which PUSCH includes the UCI based at least in part on the PHY priority), and may use the MAC priority to allocate the data, thereby improving network utilization. In some aspects, the UE 120 may include one or more padding bits in the PUSCH transmission. For example, when the UE 120 lacks data included in a specific PUSCH onto which the UCI is to be multiplexed, the UE 120 may generate an all-zero transport block as a padding bit transmitted via the specific PUSCH to maintain the PHY layer structure of the specific PUSCH and avoid dropping the specific PUSCH.

[0062] like Figure 3BAs further shown in reference numerals 335 and 340, BS 110 may determine whether UE 120 will use MAC priority and may receive UCI based at least in part on the effect of MAC priority on the UCI multiplexing configuration. For example, BS 110 may determine that UE 120 discarded a PUSCH onto which UCI was to be multiplexed (e.g., based at least in part on MAC priority) and may determine to receive a PUCCH onto which UE 120 transmitted UCI.

[0063] Additionally or alternatively, BS 110 may determine that UE 120 discarded the PUSCH onto which UCI was to be multiplexed, and may determine that the next lowest indexed PUSCH includes UCI. In this case, BS 110 may decode the next lowest indexed PUSCH to receive UCI, and may decode one or more other PUSCHs that do not include UCI. Additionally or alternatively, BS 110 may determine that UCI is to be multiplexed onto a particular PUSCH based at least in part on PHY priority, and may determine that UE 120 does not apply MAC priority to the particular PUSCH (and UE 120 applies MAC priority to other PUSCHs, as described above). In this case, BS 110 may receive the particular PUSCH with UCI and one or more other PUSCHs without UCI.

[0064] As shown above, provide Figure 3A and Figure 3B As an example. Other examples may differ from the reference Figure 3A and Figure 3B The content described.

[0065] Figure 4 is a diagram illustrating an example process 400 performed, for example, by a UE in accordance with aspects of the present disclosure. Example process 400 is an example in which a UE (eg, UE 120, etc.) performs operations associated with uplink channel contention resolution for conditional MAC layer-based prioritization.

[0066] like Figure 4 As shown, in some aspects, process 400 may include detecting a collision between a PUCCH and a plurality of PUSCHs having corresponding plurality of MAC priorities, wherein the PUCCH is associated with UCI (block 410). For example, as described above, for example, with reference to Figure 3A and Figure 3B, the UE (e.g., using the receive processor 258, the transmit processor 264, the controller / processor 280, the memory 282, etc.) can detect a collision between a PUCCH and a plurality of PUSCHs having corresponding plurality of MAC priorities, and wherein the PUCCH is associated with the UCI. In some aspects, the PUCCH is associated with the UCI.

[0067] like Figure 4 As further shown, in some aspects, process 400 may include selectively applying a MAC prioritization rule for processing multiple PUSCHs based at least in part on the corresponding multiple MAC priorities and based at least in part on the impact of the multiple MAC priorities on the UCI multiplexing configuration for UCI multiplexing (block 420). For example, as described above, for example, with reference to Figure 3A and Figure 3B , the UE (e.g., using the receive processor 258, the transmit processor 264, the controller / processor 280, the memory 282, etc.) can selectively apply MAC prioritization rules for processing multiple PUSCHs based at least in part on the corresponding multiple MAC priorities and at least in part on the impact of the multiple MAC priorities on the UCI multiplexing configuration for UCI multiplexing.

[0068] like Figure 4 As further shown, in some aspects, process 400 may include selectively transmitting at least one of the plurality of PUSCHs with UCI based at least in part on the result of selectively applying the MAC prioritization rule (block 430). For example, as described above, for example, with reference to Figure 3A and Figure 3B , the UE (e.g., using the receive processor 258, the transmit processor 264, the controller / processor 280, the memory 282, etc.) can selectively transmit at least one of the multiple PUSCHs with UCI based at least in part on the results of selectively applying the MAC prioritization rules.

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

[0070] In a first aspect, multiple PUSCHs are scheduled on corresponding multiple different uplink component carriers.

[0071] In a second aspect, either alone or in combination with the first aspect, selectively applying MAC prioritization rules for processing multiple PUSCHs includes determining to process multiple PUSCHs using corresponding multiple MAC priorities without changing PHY layer rules for UCI multiplexing configuration based at least in part on the multiple MAC priorities.

[0072] In a third aspect, either alone or in combination with one or more of the first and second aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes multiplexing UCI to a first PUSCH among multiple PUSCHs based at least in part on a UCI multiplexing configuration; and allocating data to one or more second PUSCHs among the multiple PUSCHs to which UCI is not multiplexed using corresponding multiple MAC priorities.

[0073] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 400 may include applying a PHY layer priority to data allocations for a particular PUSCH onto which UCI is multiplexed.

[0074] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes multiplexing UCI to a specific PUSCH among multiple PUSCHs based at least in part on a UCI multiplexing configuration; and determining not to discard a specific PUSCH based on corresponding multiple MAC priorities.

[0075] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 400 may include adding one or more padding bits to a specific PUSCH so as to maintain a PHY layer structure of the specific PUSCH.

[0076] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes processing multiple PUSCHs according to corresponding multiple MAC priorities based at least in part on UCI multiplexing being associated with a number of UCI multiplexing options that is less than or equal to a threshold number.

[0077] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes processing multiple PUSCHs according to corresponding multiple MAC priorities based at least in part on UCI multiplexing associated with less than or equal to two UCI multiplexing options.

[0078] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes determining corresponding multiple MAC priority levels to change the UCI multiplexing configuration; and processing multiple PUSCHs without using corresponding multiple MAC priorities based at least in part on determining the corresponding multiple MAC priority levels to change the UCI multiplexing configuration.

[0079] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes discarding a specific PUSCH on which UCI in multiple PUSCHs will be multiplexed based at least in part on the corresponding multiple MAC priorities; transmitting UCI to the PUCCH based at least in part on discarding the specific PUSCH; and processing multiple PUSCHs according to the corresponding multiple MAC priorities based at least in part on determining to discard the specific PUSCH and transmit the UCI to the PUCCH.

[0080] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 400 may include sending a PUCCH based at least in part on transmitting UCI to the PUCCH; and dropping multiple PUSCHs based at least in part on transmitting UCI to the PUCCH.

[0081] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, selectively applying MAC prioritization rules for processing multiple PUSCHs includes discarding a specific PUSCH on which UCI will be multiplexed based at least in part on the corresponding multiple MAC priorities; moving the UCI to the next lowest indexed PUSCH after the specific PUSCH based at least in part on discarding the specific PUSCH; and processing multiple PUSCHs according to the corresponding multiple MAC priorities based at least in part on determining to discard the specific PUSCH and move the UCI to the next lowest indexed PUSCH.

[0082] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the index of the next lowest indexed PUSCH is the component carrier index of the component carrier for which the next lowest indexed PUSCH is scheduled.

[0083] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 400 may include dropping a plurality of PUSCHs based at least in part on a PHY layer priority rule.

[0084] Although Figure 4 An example block diagram of process 400 is shown, but in some aspects process 400 may include additional blocks, fewer blocks, different blocks, or different Figure 4 Depicted blocks arranged differently. Additionally or alternatively, two or more of the blocks of process 400 may be performed in parallel.

[0085] Figure 5is a diagram illustrating an example process 500, performed, for example, by a BS, in accordance with aspects of the present disclosure. Example process 500 is an example in which a BS (eg, BS 110, etc.) performs operations associated with uplink channel contention resolution for conditional MAC layer-based prioritization.

[0086] like Figure 5 As shown, in some aspects, process 500 may include: determining a UCI multiplexing configuration related to a MAC prioritization rule for scheduling conflicts between a PUCCH with UCI and a plurality of PUSCHs with corresponding plurality of MAC priorities (block 510). For example, as described above, with reference to e.g. Figure 3A and Figure 3B , the BS (e.g., using the transmit processor 220, the receive processor 238, the controller / processor 240, the memory 242, etc.) can determine a UCI multiplexing configuration related to a MAC prioritization rule for scheduling conflicts between a PUCCH with UCI and multiple PUSCHs with corresponding multiple MAC priorities.

[0087] like Figure 5 As further shown, in some aspects, process 500 may include receiving UCI via at least one of the plurality of PUSCHs or via the PUCCH according to the UCI multiplexing configuration (block 520). For example, as described above, with reference to e.g. Figure 3A and Figure 3B , the BS (eg, using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may receive at least one of the plurality of PUSCHs based at least in part on determining a UCI multiplexing configuration.

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

[0089] In a first aspect, determining the UCI multiplexing configuration includes deterministically deciding the UCI multiplexing configuration.For example, the BS may decide the UCI multiplexing configuration based at least in part on a set of rules for selecting which uplink channel to use for UCI.

[0090] In a second aspect, alone or in combination with the first aspect, determining the UCI multiplexing configuration includes processing a plurality of PUSCHs according to a plurality of candidate UCI multiplexing configurations.

[0091] In a third aspect, alone or in combination with any one or more of the first and second aspects, process 500 may include determining a UCI multiplexing configuration based at least in part on a PHY layer priority rule.

[0092] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 500 may include determining that UCI is multiplexed to a specific PUSCH among multiple PUSCHs, wherein the specific PUSCH is not discarded based at least in part on the UCI being multiplexed to the specific PUSCH; and demultiplexing the UCI from the specific PUSCH.

[0093] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a specific PUSCH includes one or more padding bits in order to maintain a PHY layer structure of at least one PUSCH.

[0094] Although Figure 5 Example blocks of process 500 are shown, but in some aspects process 500 may include additional blocks, fewer blocks, different blocks, or different blocks. Figure 5 Depicted blocks arranged differently. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0095] The above disclosure provides examples and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Various modifications and variations may be made on the teachings of the above disclosure or may be obtained from the implementation of the various aspects.

[0096] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, and / or a combination of hardware or software.

[0097] 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.

[0098] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not a limitation of the various aspects. Therefore, the operation and behavior of the systems and / or methods are described without reference to specific software code—it should be understood that software and hardware may be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0099] Even if a particular combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in a manner that is not specifically stated in the claims and / or disclosed in the specification. Although each dependent claim listed below may only be directly subordinate to one claim, the disclosure of the various aspects includes each dependent claim combined with each other claim in the claim set. The phrase "at least one" of a column of items 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, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc or any other arrangement of a, b and c).

[0100] Unless so explicitly described, the elements, actions or instructions used herein should not be considered critical or essential. In addition, as used herein, the articles "one" or "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". In the case of only one item, the phrase "only one" or similar language is used. In addition, as used herein, the terms "having" and the like are intended to be open-ended terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. A wireless communication method performed by a user equipment UE, include: detecting a conflict between a physical uplink control channel PUCCH and a plurality of physical uplink shared channels PUSCH having corresponding plurality of medium access control MAC priorities, Wherein the PUCCH is associated with uplink control information UCI; selectively applying a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an impact of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing, wherein the plurality of PUSCHs include a specific PUSCH onto which the UCI is multiplexed, and The specific PUSCH includes one or more padding bits so as to maintain a physical PHY layer structure of the specific PUSCH; and At least one of the plurality of PUSCHs with the UCI is selectively transmitted based at least in part on a result of selectively applying the MAC prioritization rule. 2 . The method according to claim 1 , wherein the plurality of PUSCHs are scheduled on corresponding plurality of different uplink component carriers.

3. The method of claim 1 , wherein the MAC prioritization rule for processing the plurality of PUSCHs is selectively applied include: Based at least in part on the multiple MAC priorities not changing a PHY layer rule for the UCI multiplexing configuration, determining to use the corresponding multiple MAC priorities to process the multiple PUSCHs.

4. The method of claim 1 , wherein the MAC prioritization rule for processing the plurality of PUSCHs is selectively applied include: Based at least in part on the UCI multiplexing configuration, multiplexing the UCI to a first PUSCH among the plurality of PUSCHs, wherein the first PUSCH is the specific PUSCH; as well as Data is allocated using the corresponding plurality of MAC priority levels to one or more second PUSCHs of the plurality of PUSCHs onto which the UCI is not multiplexed.

5. The method according to claim 1, further comprising: include: A PHY layer priority is applied to data allocation for the specific PUSCH.

6. The method of claim 1, wherein the MAC prioritization rule for processing the plurality of PUSCHs is selectively applied include: multiplexing the UCI onto the specific PUSCH based at least in part on the UCI multiplexing configuration; as well as Based at least in part on the UCI being multiplexed onto the specific PUSCH, it is determined not to drop the specific PUSCH.

7. The method of claim 1, wherein the MAC prioritization rule for processing the plurality of PUSCHs is selectively applied include: Based at least in part on the UCI multiplexing being associated with less than or equal to a threshold number of UCI multiplexing options, the plurality of PUSCHs are processed according to the corresponding plurality of MAC priority levels.

8. The method of claim 1, wherein the MAC prioritization rule for processing the plurality of PUSCHs is selectively applied include: Based at least in part on the UCI multiplexing being associated with less than or equal to two UCI multiplexing options, processing the plurality of PUSCHs according to the corresponding plurality of MAC priority levels.

9. The method of claim 1, wherein the MAC prioritization rule for processing the plurality of PUSCHs is selectively applied include: Determine the corresponding multiple MAC priorities to change the UCI multiplexing configuration; as well as The UCI multiplexing configuration is altered based at least in part on determining the corresponding plurality of MAC priority levels to process the plurality of PUSCHs without using the corresponding plurality of MAC priority levels.

10. The method of claim 1, wherein the PHY layer structure is maintained include: Based at least in part on UCI being multiplexed onto the specific PUSCH, determining not to drop the specific PUSCH.

11. The method according to claim 1, wherein at least one of the plurality of PUSCHs is selectively transmitted include: The specific PUSCH is transmitted based at least in part on the UCI being multiplexed onto the specific PUSCH.

12. A wireless communication method performed by a network entity, include: determining an uplink control information UCI multiplexing configuration associated with a media access control MAC prioritization rule for a scheduling conflict between a physical uplink control channel PUCCH having UCI and a plurality of physical uplink shared channels PUSCH having corresponding plurality of MAC priorities, wherein the plurality of PUSCHs include a specific PUSCH onto which the UCI is multiplexed, and The specific PUSCH includes one or more padding bits so as to maintain a physical PHY layer structure of the specific PUSCH; and The UCI is received via at least one of the plurality of PUSCHs or via the PUCCH according to the UCI multiplexing configuration.

13. The method according to claim 12, wherein determining the UCI multiplexing configuration include: Determine the UCI multiplexing configuration.

14. The method according to claim 12, wherein determining the UCI multiplexing configuration include: The plurality of PUSCHs are processed according to a plurality of candidate UCI multiplexing configurations.

15. The method according to claim 12, wherein determining the UCI multiplexing configuration include: The UCI multiplexing configuration is determined based at least in part on a PHY layer priority rule.

16. The method of claim 12, wherein receiving the UCI include: determining that the UCI is multiplexed onto the specific PUSCH, wherein the specific PUSCH is not dropped based at least in part on the UCI being multiplexed onto the specific PUSCH; and Based on determining that the UCI is multiplexed onto the specific PUSCH, the UCI is demultiplexed from the specific PUSCH.

17. The method of claim 12, wherein the PHY layer structure is maintained include: Based at least in part on UCI being multiplexed onto the specific PUSCH, determining not to drop the specific PUSCH.

18. A user equipment UE for wireless communication, include: Memory; as well as One or more processors operatively coupled to the memory, the one or more processors configured to: detecting a conflict between a physical uplink control channel PUCCH and a plurality of physical uplink shared channels PUSCH having corresponding plurality of medium access control MAC priorities, Wherein the PUCCH is associated with uplink control information UCI; selectively applying a MAC prioritization rule for processing the plurality of PUSCHs based at least in part on the corresponding plurality of MAC priorities and based at least in part on an impact of the plurality of MAC priorities on a UCI multiplexing configuration for UCI multiplexing, wherein the plurality of PUSCHs include a specific PUSCH onto which the UCI is multiplexed, and The specific PUSCH includes one or more padding bits so as to maintain a physical PHY layer structure of the specific PUSCH; and At least one of the plurality of PUSCHs with the UCI is selectively transmitted based at least in part on a result of selectively applying the MAC prioritization rule.

19. The UE of claim 18, wherein the plurality of PUSCHs are scheduled on a corresponding plurality of different uplink component carriers.

20. The UE of claim 18, wherein when selectively applying the MAC prioritization rule for processing the plurality of PUSCHs, the one or more processors are configured to: Based at least in part on the multiple MAC priorities not changing a PHY layer rule for the UCI multiplexing configuration, determining to use the corresponding multiple MAC priorities to process the multiple PUSCHs.

21. The UE of claim 18, wherein when selectively applying the MAC prioritization rule for processing the plurality of PUSCHs, the one or more processors are configured to: multiplexing the UCI onto a first PUSCH of the plurality of PUSCHs based at least in part on a PHY layer priority rule, wherein the first PUSCH is the particular PUSCH; and Data is allocated using the corresponding plurality of MAC priority levels to one or more second PUSCHs of the plurality of PUSCHs onto which the UCI is not multiplexed.

22. The UE of claim 18, wherein the one or more processors are further configured to: A PHY layer priority is applied to data allocation for the specific PUSCH.

23. The UE of claim 18, wherein maintaining the PHY layer structure comprises determining not to drop the specific PUSCH based at least in part on UCI being multiplexed onto the specific PUSCH.

24. The UE of claim 18, wherein when selectively transmitting at least one of the plurality of PUSCHs, the one or more processors are configured to: The specific PUSCH is transmitted based at least in part on the UCI being multiplexed onto the specific PUSCH.

25. A network entity for wireless communication, include: Memory; as well as One or more processors operatively coupled to the memory, the one or more processors configured to: determining an uplink control information UCI multiplexing configuration associated with a media access control MAC prioritization rule for a scheduling conflict between a physical uplink control channel PUCCH having UCI and a plurality of physical uplink shared channels PUSCH having corresponding plurality of MAC priorities, wherein the plurality of PUSCHs include a specific PUSCH onto which the UCI is multiplexed, and The specific PUSCH includes one or more padding bits so as to maintain a physical PHY layer structure of the specific PUSCH; and The UCI is received via at least one of the plurality of PUSCHs or via the PUCCH according to the UCI multiplexing configuration.

26. The network entity of claim 25, wherein when determining the UCI multiplexing configuration, the one or more processors are configured to: Determine the UCI multiplexing configuration.

27. The network entity of claim 25, wherein when determining the UCI multiplexing configuration, the one or more processors are configured to: The plurality of PUSCHs are processed according to a plurality of candidate UCI multiplexing configurations.

28. The network entity of claim 25, wherein when determining the UCI multiplexing configuration, the one or more processors are configured to: The UCI multiplexing configuration is determined based at least in part on a PHY layer priority rule.

29. The network entity of claim 25, wherein upon receiving the UCI, the one or more processors are configured to: determining that the UCI is multiplexed onto the specific PUSCH, wherein the specific PUSCH is not dropped based at least in part on the UCI being multiplexed onto the specific PUSCH; and Based on determining that the UCI is multiplexed onto the specific PUSCH, the UCI is demultiplexed from the specific PUSCH.

30. The network entity of claim 25, wherein maintaining the PHY layer structure comprises determining not to drop the specific PUSCH based at least in part on UCI being multiplexed onto the specific PUSCH.

31. An apparatus for wireless communication at a user equipment UE, include: Means for performing the method according to any one of claims 1-11.

32. An apparatus at a network entity for wireless communication, include: Means for performing a method according to any one of claims 12-17.

33. A computer readable medium having program code stored thereon, wherein the program code is executable by one or more processors to cause the one or more processors to perform the method according to any one of claims 1-17.

Images