WO2022089403A1

WO2022089403A1 - Methods for intra-ue multiplexing in mobile communications

Info

Publication number: WO2022089403A1
Application number: PCT/CN2021/126325
Authority: WO
Inventors: Abdellatif Salah; Mohammed S Aleabe AL-IMARI
Original assignee: Mediatek Singapore Pte. Ltd.; Mediatek Inc.
Priority date: 2020-10-27
Filing date: 2021-10-26
Publication date: 2022-05-05

Abstract

Various solutions for intra-user equipment (intra-UE) multiplexing in mobile communications are described. An apparatus, implementable in or as a UE, multiplexes a high-priority physical uplink control channel (HP-PUCCH) and a low-priority physical uplink control channel (LP-PUCCH) to result in a multiplexed PUCCH. The apparatus then performs an uplink (UL) transmission of the multiplexed PUCCH to a network. A guard gap timeline of the multiplexed PUCCH is based on a guard gap timeline of an earlier PUCCH between the two PUCCHs.

Description

METHODS FOR INTRA-UE MULTIPLEXING IN MOBILE COMMUNICATIONS

CROSS REFERENCE TO RELATED PATENT APPLICATION

The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 63/105,921, filed on 27 October 2020, the content of which being incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communications and, more particularly, to techniques for intra-user equipment (intra-UE) multiplexing in mobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.

In wireless communications, such as mobile communications under the 3 ^rd Generation Partnership Project (3GPP) specification (s) for 5 ^th Generation (5G) New Radio (NR) , certain multiplexing scenarios on physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) have been agreed upon and supported in Release 17 (Rel-17) of the 3GPP specification. Regarding PUCCH, multiplexing a high-priority (HP) hybrid automatic repeat request acknowledgement (HARQ-ACK) and a LP (LP) HARQ-ACK into a PUCCH is supported in Rel-17. Additionally, multiplexing a LP HARQ-ACK and a HP scheduling request (SR) into a PUCCH for some HARQ-ACK/SR PF combinations is supported in Rel-17. Moreover, multiplexing a LP HARQ-ACK, a HP HARQ-ACK and a HP SR into a PUCCH is supported in Rel-17. Regarding PUSCH, multiplexing a LP HARQ-ACK in a HP PUSCH (conveying uplink scheduling (UL-SCH) only) is supported in Rel-17. Additionally, multiplexing a HP HARQ-ACK in a LP PUSCH (conveying UL-SCH only) is supported in Rel-17. Moreover, multiplexing a LP HARQ-ACK, a HP PUSCH conveying UL-SCH, a HP HARQ-ACK and/or channel state information (CSI) is supported in Rel-17. Furthermore, multiplexing a HP HARQ-ACK, a LP PUSCH conveying UL-SCH, a LP HARQ-ACK and/or CSI is supported in Rel-17.

However, details about timeline, configurations, encoding, indication and so on are still up for discussion and finalized. Therefore, there is a need for a solution of intra-UE multiplexing in mobile communications.

SUMMARY

The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

An objective of the present disclosure is to propose solutions or schemes that address the issue (s) described herein. More specifically, various schemes proposed in the present disclosure are believed to provide solutions for intra-UE multiplexing in mobile communications.

In one aspect, a method may involve multiplexing a high-priority physical uplink control channel (HP-PUCCH) and a low-priority physical uplink control channel (LP-PUCCH) to result in a multiplexed PUCCH. The method may also involve performing an uplink (UL) transmission of the multiplexed PUCCH to a network, with a guard gap timeline of the multiplexed PUCCH is based on a guard gap timeline of an earlier PUCCH between the two PUCCHs.

In another aspect, a method may involve multiplexing a HP-PUCCH and a LP-PUCCH to result in a multiplexed PUCCH. The method may also involve performing an UL transmission of the multiplexed PUCCH to a network, with a guard gap timeline of the multiplexed PUCCH is based on a guard gap timeline of one of the two PUCCHs on which the multiplexing occurs.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as 5G/NR mobile communications, the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) , Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , vehicle-to-everything (V2X) , and non-terrestrial network (NTN) communications. Thus, the scope of the present disclosure is not limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.

FIG. 1 is a diagram of an example network environment in which various proposed schemes in accordance with the present disclosure may be implemented.

FIG. 2 is a diagram of an example scenario under a proposed scheme in accordance with the present disclosure.

FIG. 3 is a block diagram of an example communication apparatus and an example network apparatus in accordance with an implementation of the present disclosure.

FIG. 4 is a flowchart of an example process in accordance with an implementation of the present disclosure.

FIG. 5 is a flowchart of an example process in accordance with an implementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

Overview

Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to intra-UE multiplexing in mobile communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented. Referring to FIG. 1, network environment 100 may involve a user equipment (UE) 110 in wireless communication with a wireless network 120 (e.g., a 5G NR mobile network and/or another type of network such as a LTE network, a LTE-Advance network, a NB-IoT network, an IoT network, an IIoT network and/or an NTN) . UE 110 may be in wireless communication with wireless network 120 via a base station or network node 125 (e.g., an eNB, gNB or transmit-receive point (TRP) ) . In network environment 100, UE 110 and wireless network 120 may implement various schemes pertaining to intra-UE multiplexing in mobile communications, as described below.

FIG. 2 illustrates an example scenario 200 under a proposed scheme in accordance with the present disclosure with respect to multiplexing timeline. Under the proposed scheme, when multiplexing a HP-PUCCH and a LP-PUCCH to result in a new multiplexed PUCCH, guard gaps of the two PUCCHs may be taken into consideration in determining a new guard gap for the new multiplexed PUCCH. Advantageously, this may avoid increasing the latency of the HP-PUCCH while at the same time not causing UE implementation to be more complicated by shortening the guard gap. Under the proposed scheme, there may be two options. Referring to FIG. 2, T1 denotes a duration before LP-PUCCH during which the LP-PUCCH cannot be overridden anymore (e.g., by downlink control information (DCI) or physical downlink control channel (PDCCH) from wireless network 120) , and T2 denotes a duration before HP-PUCCH during which the HP-PUCCH cannot be overridden anymore (e.g., by DCI or PDCCH from wireless network 120) .

In a first option (Option 1) , a guard gap timeline of the new multiplexed PUCCH may be that of the earlier PUCCH between the two PUCCHs, and this guard gap timeline is denoted as T _option1 in FIG. 2. This may be a UE-friendly option as it aggregates the timeline of the two PUCCHs. However, the second PUCCH in time (e.g., whichever of the HP-PUCCH and LP-PUCCH that is the later one between the two) may not be overridden anymore (during a time period t although the original timeline of the second PUCCH is not impacted.

In a second option (Option 2) , the guard gap timeline of the new multiplexed PUCCH may be that of one of the two PUCCHs on which the multiplexing occurs (e.g., HP-PUCCH in the example shown in FIG. 2) , and this guard gap timeline is denoted as T _option2 in FIG. 2. This option may allow more flexibility for the second PUCCH to be overridden during the time period t. However, in case that the second PUCCH is overridden, the first PUCCH in time (e.g., whichever of the HP-PUCCH and LP-PUCCH that is the earlier one between the two) may not be transmitted anymore as its guard gap is impacted, unless it is transmitted on the same resource (s) used for transmission of the second PUCCH.

It is noteworthy that multiplexing between two PUCCHs that span over different sub-slot (or slot) durations may raise concerns. Moreover, in such cases, some HP-PUCCHs may be dropped or delayed. Accordingly, under a proposed scheme in accordance with the present disclosure, multiplexing of uplink control information (UCI) of different priorities may be allowed in case that PUCCHs are within the same sub-slot or slot. Otherwise, dropping rule (s) as specified in Release 16 (Rel-16) of the 3GPP specification may be utilized. That is, under the proposed scheme, multiplexing between a HP-PUCCH and a LP-PUCCCH may be allowed in an event that the resultant new multiplexed PUCCH is confined within the sub-slot of the HP-PUCCH.

It is also noteworthy that some of the conditions to possibly consider for multiplexing include the size of the LP HARQ-ACK bits. Specifically, a large number of bits leads to a longer PUCCH which could compromise the latency as well as reliability. However, this condition could be restrictive as it would limit the possibility of multiplexing. Accordingly, under a proposed scheme in accordance with the present disclosure, group-bundling may be supported. Under the proposed scheme, group bundling involves bundling every small group of N ₁ bits to N ₂ (e.g., N ₁ = 2, N ₂ = 1) , and N ₁ and/or N ₂ may be specified in the 3GPP specification or configured to UE 110 via radio resource control (RRC) signaling from wireless network 120. For instance, group bundling may be used in case that a new UCI payload (e.g., number of bits) is above a certain threshold maxUCIPayload. In some implementations, group bundling may be used to reduce the number of bits to a maximum of maxUCIPayload bits. In some implementations, the threshold maxUCIPayload may be specified in the 3GPP specification or RRC configured to the UE. In some implementations, group-bundling may be applied only to the low-priority UCI (LP-UCI) . In some implementations group-bundling may be supported as a UE capability. In some implementations, group-bundling may be enabled and disabled by RRC signaling from wireless network 120. In some implementations, group-bundling may be applied or otherwise enabled only when the LP-UCI is multiplexed on specific HP channels. For instance, group-bundling may be applied/enabled only when the LP-UCI is multiplexed on HP-PUCCH. In some implementations, group-bundling may be applied per transport block (TB) of the LP-HAQR feedback. For instance, in case that code block group (CBG) -level HARQ-ACK feedback is enabled for a TB, then only the TB HARQ-ACK feedback may be sent when the LP-UCI is multiplexed on HP channel (s) . In some implementations, group-bundling may be applied or otherwise enabled per specific HARQ codebook type. For instance, group-bundling may be enabled for dynamic HARQ codebook feedback and disabled for semi-static HARQ codebook feedback.

Illustrative Implementations

FIG. 3 illustrates an example communication system 300 having an example communication apparatus 310 and an example network apparatus 320 in accordance with an implementation of the present disclosure. Each of communication apparatus 310 and network apparatus 320 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to intra-UE multiplexing in mobile communications, including scenarios/schemes described above as well as processes described below.

Communication apparatus 310 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, communication apparatus 310 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Communication apparatus 310 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, IIoT or NTN apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, communication apparatus 310 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. Alternatively, communication apparatus 310 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. Communication apparatus 310 may include at least some of those components shown in FIG. 3 such as a processor 312, for example. Communication apparatus 310 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of communication apparatus 310 are neither shown in FIG. 3 nor described below in the interest of simplicity and brevity.

Network apparatus 320 may be a part of an electronic apparatus/station, which may be a network node such as a base station, a small cell, a router, a gateway or a satellite. For instance, network apparatus 320 may be implemented in an eNodeB in an LTE, in a gNB in a 5G, NR, IoT, NB-IoT, IIoT, or in a satellite in an NTN network. Alternatively, network apparatus 320 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network apparatus 320 may include at least some of those components shown in FIG. 3 such as a processor 322, for example. Network apparatus 320 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of network apparatus 320 are neither shown in FIG. 3 nor described below in the interest of simplicity and brevity.

In one aspect, each of processor 312 and processor 322 may be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 312 and processor 322, each of processor 312 and processor 322 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 312 and processor 322 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 312 and processor 322 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including intra-UE multiplexing in mobile communications in accordance with various implementations of the present disclosure.

In some implementations, communication apparatus 310 may also include a transceiver 316 coupled to processor 312 and capable of wirelessly transmitting and receiving data. In some implementations, communication apparatus 310 may further include a memory 314 coupled to processor 312 and capable of being accessed by processor 312 and storing data therein. In some implementations, network apparatus 320 may also include a transceiver 326 coupled to processor 322 and capable of wirelessly transmitting and receiving data. In some implementations, network apparatus 320 may further include a memory 324 coupled to processor 322 and capable of being accessed by processor 322 and storing data therein. Accordingly, communication apparatus 310 and network apparatus 320 may wirelessly communicate with each other via transceiver 316 and transceiver 326, respectively.

Each of communication apparatus 310 and network apparatus 320 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. To aid better understanding, the following description of the operations, functionalities and capabilities of each of communication apparatus 310 and network apparatus 320 is provided in the context of a mobile communication environment in which communication apparatus 310 is implemented in or as a communication apparatus or a UE (e.g., UE 110) and network apparatus 320 is implemented in or as a network node or base station (e.g., network node 125) of a communication network (e.g., wireless network 120) . It is also noteworthy that, although the example implementations described below are provided in the context of mobile communications, the same may be implemented in other types of networks.

Under various proposed schemes pertaining to intra-UE multiplexing in mobile communications in accordance with the present disclosure, with communication apparatus 310 implemented in or as UE 110 and network apparatus 320 implemented in or as network node 125 in network environment 100, processor 312 of communication apparatus 310 may multiplex a HP-PUCCH and a LP-PUCCH to result in a multiplexed PUCCH. Additionally, processor 312 may perform, via transceiver 316, an UL transmission of the multiplexed PUCCH to a network (e.g., wireless network 120 via apparatus 320 as network node 125) . A guard gap timeline of the multiplexed PUCCH being based on a guard gap timeline of an earlier PUCCH between the two PUCCHs. Alternatively, the guard gap timeline of the multiplexed PUCCH being based on a guard gap timeline of one of the two PUCCHs on which the multiplexing occurs.

In some implementations, in multiplexing the HP-PUCCH and the LP-PUCCH, processor 312 may multiplex the HP-PUCCH and the LP-PUCCH in an event that the multiplexed PUCCH is confined within a sub-slot or slot of the HP-PUCCH.

In some implementations, in multiplexing, processor 312 may multiplex with group bundling in an event that a number of bits of a new UCI payload of the multiplexed PUCCH is above a threshold (e.g., maxUCIPayload) . In such cases, the threshold may be either specified or configured via RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, processor 312 may multiplex with group bundling to limit a number of bits of a new UCI payload of the multiplexed PUCCH to a threshold (e.g., maxUCIPayload) . In such cases, the threshold may be either specified or configured via RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, processor 312 may multiplex with group bundling applied to LP-UCI.

In some implementations, in multiplexing, processor 312 may multiplex with group bundling, which may be a UE capability.

In some implementations, in multiplexing, processor 312 may multiplex with group bundling, which may be enabled and disabled by RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, processor 312 may multiplex with group bundling applied in an event that LP-UCI is multiplexed on the HP-PUCCH.

In some implementations, in multiplexing, processor 312 may multiplex with group bundling applied per TB of a LP-HARQ feedback. For instance, in case that CBG-level HARQ-ACK feedback is enabled for a TB, then only the TB HARQ-ACK feedback may be sent when the LP-UCI is multiplexed on HP channel (s) .

In some implementations, in multiplexing, processor 312 may multiplex with group bundling applied per specific HARQ codebook type. For instance, group-bundling may be enabled for dynamic HARQ codebook feedback and disabled for semi-static HARQ codebook feedback.

Illustrative Processes

FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may be an example implementation of schemes described above whether partially or completely, with respect to intra-UE multiplexing in mobile communications in accordance with the present disclosure. Process 400 may represent an aspect of implementation of features of communication apparatus 310 and network apparatus 320. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of

blocks

410 and 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 400 may executed in the order shown in FIG. 4 or, alternatively, in a different order. Process 400 may be implemented by communication apparatus 310 or any suitable UE or machine type devices as well as by and network apparatus 320 or any suitable network node or base station. Solely for illustrative purposes and without limitation, process 400 is described below in the context of communication apparatus 310 implemented in or as UE 110 and network apparatus 320 implemented in or as network node 125. Process 400 may begin at block 410.

At 410, process 400 may involve processor 312 of communication apparatus 310, implemented in or as UE 110, multiplexing a HP-PUCCH and a LP-PUCCH to result in a multiplexed PUCCH. Process 400 may proceed from 410 to 420.

At 420, process 400 may involve processor 312 performing, via transceiver 316, an UL transmission of the multiplexed PUCCH to a network (e.g., wireless network 120 via apparatus 320 as network node 125) , with a guard gap timeline of the multiplexed PUCCH being based on a guard gap timeline of an earlier PUCCH between the two PUCCHs.

In some implementations, in multiplexing the HP-PUCCH and the LP-PUCCH, process 400 may involve processor 312 multiplexing the HP-PUCCH and the LP-PUCCH in an event that the multiplexed PUCCH is confined within a sub-slot or slot of the HP-PUCCH.

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling in an event that a number of bits of a new UCI payload of the multiplexed PUCCH is above a threshold (e.g., maxUCIPayload) . In such cases, the threshold may be either specified or configured via RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling to limit a number of bits of a new UCI payload of the multiplexed PUCCH to a threshold (e.g., maxUCIPayload) . In such cases, the threshold may be either specified or configured via RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling applied to LP-UCI.

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling, which may be a UE capability.

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling, which may be enabled and disabled by RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling applied in an event that LP-UCI is multiplexed on the HP-PUCCH.

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling applied per TB of a LP-HARQ feedback.

In some implementations, in multiplexing, process 400 may involve processor 312 multiplexing with group bundling applied per specific HARQ codebook type.

FIG. 5 illustrates an example process 500 in accordance with an implementation of the present disclosure. Process 500 may be an example implementation of schemes described above whether partially or completely, with respect to intra-UE multiplexing in mobile communications in accordance with the present disclosure. Process 500 may represent an aspect of implementation of features of communication apparatus 310 and network apparatus 320. Process 500 may include one or more operations, actions, or functions as illustrated by one or more of

blocks

510 and 520. Although illustrated as discrete blocks, various blocks of process 500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 500 may executed in the order shown in FIG. 5 or, alternatively, in a different order. Process 500 may be implemented by communication apparatus 310 or any suitable UE or machine type devices as well as by and network apparatus 320 or any suitable network node or base station. Solely for illustrative purposes and without limitation, process 500 is described below in the context of communication apparatus 310 implemented in or as UE 110 and network apparatus 320 implemented in or as network node 125. Process 500 may begin at block 510.

At 510, process 500 may involve processor 312 of communication apparatus 310, implemented in or as UE 110, multiplexing a HP-PUCCH and a LP-PUCCH to result in a multiplexed PUCCH. Process 500 may proceed from 510 to 520.

At 520, process 500 may involve processor 312 performing, via transceiver 316, an UL transmission of the multiplexed PUCCH to a network (e.g., wireless network 120 via apparatus 320 as network node 125) , with a guard gap timeline of the multiplexed PUCCH being based on a guard gap timeline of one of the two PUCCHs on which the multiplexing occurs.

In some implementations, in multiplexing the HP-PUCCH and the LP-PUCCH, process 500 may involve processor 312 multiplexing the HP-PUCCH and the LP-PUCCH in an event that the multiplexed PUCCH is confined within a sub-slot or slot of the HP-PUCCH.

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling in an event that a number of bits of a new UCI payload of the multiplexed PUCCH is above a threshold (e.g., maxUCIPayload) . In such cases, the threshold may be either specified or configured via RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling to limit a number of bits of a new UCI payload of the multiplexed PUCCH to a threshold (e.g., maxUCIPayload) . In such cases, the threshold may be either specified or configured via RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling applied to LP-UCI.

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling, which may be a UE capability.

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling, which may be enabled and disabled by RRC signaling from the network (e.g., via apparatus 320 as network node 125) .

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling applied in an event that LP-UCI is multiplexed on the HP-PUCCH.

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling applied per TB of a LP-HARQ feedback.

In some implementations, in multiplexing, process 500 may involve processor 312 multiplexing with group bundling applied per specific HARQ codebook type.

Additional Notes

The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”

From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

A method, comprising:

multiplexing a high-priority physical uplink control channel (HP-PUCCH) and a low-priority physical uplink control channel (LP-PUCCH) to result in a multiplexed PUCCH; and

performing an uplink (UL) transmission of the multiplexed PUCCH to a network,

wherein a guard gap timeline of the multiplexed PUCCH is based on a guard gap timeline of an earlier PUCCH between the two PUCCHs.
The method of Claim 1, wherein the multiplexing of the HP-PUCCH and the LP-PUCCH comprises multiplexing the HP-PUCCH and the LP-PUCCH in an event that the multiplexed PUCCH is confined within a sub-slot or slot of the HP-PUCCH.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling in an event that a number of bits of a new uplink control information (UCI) payload of the multiplexed PUCCH is above a threshold, and wherein the threshold is either specified or configured via radio resource control (RRC) signaling from the network.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling to limit a number of bits of a new uplink control information (UCI) payload of the multiplexed PUCCH to a threshold, and wherein the threshold is either specified or configured via radio resource control (RRC) signaling from the network.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling applied to low-priority uplink control information (LP-UCI) .
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling, and wherein the group bundling is a user equipment (UE) capability.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling, and wherein the group bundling is enabled and disabled by radio resource control (RRC) signaling from the network.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling applied in an event that low-priority uplink control information (LP-UCI) is multiplexed on the HP-PUCCH.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling applied per transport block (TB) of a low-priority hybrid automatic repeat request (LP-HARQ) feedback.
The method of Claim 1, wherein the multiplexing comprises multiplexing with group bundling applied per specific hybrid automatic repeat request (HARQ) codebook type.
A method, comprising:

multiplexing a high-priority physical uplink control channel (HP-PUCCH) and a low-priority physical uplink control channel (LP-PUCCH) to result in a multiplexed PUCCH; and

performing an uplink (UL) transmission of the multiplexed PUCCH to a network,

wherein a guard gap timeline of the multiplexed PUCCH is based on a guard gap timeline of one of the two PUCCHs on which the multiplexing occurs.
The method of Claim 11, wherein the multiplexing of the HP-PUCCH and the LP-PUCCH comprises multiplexing the HP-PUCCH and the LP-PUCCH in an event that the multiplexed PUCCH is confined within a sub-slot or slot of the HP-PUCCH.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling in an event that a number of bits of a new uplink control information (UCI) payload of the multiplexed PUCCH is above a threshold, and wherein the threshold is either specified or configured via radio resource control (RRC) signaling from the network.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling to limit a number of bits of a new uplink control information (UCI) payload of the multiplexed PUCCH to a threshold, and wherein the threshold is either specified or configured via radio resource control (RRC) signaling from the network.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling applied to low-priority uplink control information (LP-UCI) .
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling, and wherein the group bundling is a user equipment (UE) capability.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling, and wherein the group bundling is enabled and disabled by radio resource control (RRC) signaling from the network.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling applied in an event that low-priority uplink control information (LP-UCI) is multiplexed on the HP-PUCCH.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling applied per transport block (TB) of a low-priority hybrid automatic repeat request (LP-HARQ) feedback.
The method of Claim 11, wherein the multiplexing comprises multiplexing with group bundling applied per specific hybrid automatic repeat request (HARQ) codebook type.