Method and related device for transmitting physical uplink control channel

Abstract

A method for transmitting a physical uplink control channel (PUCCH) for a user equipment (UE) is provided. The method includes: receiving a first radio resource control (RRC) configuration including a first PUCCH resource configuration and a second PUCCH resource configuration; receiving a first downlink control information (DCI) format for scheduling a first physical downlink shared channel (PDSCH) and a second DCI format for scheduling a second PDSCH; determining a first PUCCH for a first hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook corresponding to the first PDSCH based on the first PUCCH resource configuration, and determining a second PUCCH for a second HARQ-ACK codebook corresponding to the second PDSCH based on the second PUCCH resource configuration; and transmitting the first PUCCH when the first PUCCH overlaps with the second PUCCH in the time domain, with the first HARQ-ACK codebook and the second HARQ-ACK codebook being multiplexed in the first PUCCH.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims the benefit of and priority to U.S. Provisional Patent Application Serial No. 63 / 104,925, filed on October 23, 2020, and entitled “MULTIPLEXING UPLINK CHANNELS OF DIFFERENT PRIORITIES” (hereinafter “the '925 Provisional”). The disclosure of the '925 Provisional is hereby incorporated by reference into this disclosure in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly, to a method and related apparatus for transmitting a Physical Uplink Control Channel (PUCCH). Background Art

[0004] With the huge growth in the number of connected devices and the rapid increase in user / network traffic, various efforts have been made to improve different aspects of wireless communications in next-generation wireless communication systems like fifth-generation (5G) New Radio (NR) by improving data rate, latency, reliability, and mobility.

[0005] The 5G NR system is designed to provide flexibility and configurability to optimize network services and types and accommodate various use cases such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0006] However, as the demand for radio access continues to increase, there is a need to further improve wireless communications for next generation wireless communication systems. Summary of the Invention

[0007] The present disclosure provides a method and related apparatus for transmitting a physical uplink control channel (PUCCH).

[0008] According to one aspect of the present disclosure, a method for transmitting PUCCH by user equipment (UE) is provided. The method includes: receiving a first radio resource control (RRC) configuration including a first PUCCH resource configuration and a second PUCCH resource configuration; receiving a first downlink control information (DCI) format for scheduling a first physical downlink shared channel (PDSCH) and a second DCI format for scheduling a second PDSCH; determining a first hybrid automatic repeat request (HARQ) for corresponding to the first PDSCH based on the first PUCCH resource configuration; reQuest, HARQ) acknowledgement (ACK) codebook, and determining, based on the second PUCCH resource configuration, a second PUCCH for a second HARQ-ACK codebook corresponding to the second PDSCH; when the first PUCCH and the second PUCCH overlap in the time domain, transmitting the first PUCCH, and the first HARQ-ACK codebook and the second HARQ-ACK codebook are multiplexed in the first PUCCH; determining, based on the smaller value of the total number of resource elements of the first PUCCH and the second number of resource elements, a first number of resource elements for the first HARQ-ACK codebook in the first PUCCH, the second number being based on the payload size of the first HARQ-ACK codebook, a cyclic redundancy check (CRC) for the first HARQ-ACK codebook, and a cyclic redundancy check (CRC) for the first HARQ-ACK codebook. The method is determined by at least one of a size of a HARQ Check (CRC) and a first maximum coding rate corresponding to the first PUCCH resource configuration, and determining a third number of resource elements for the second HARQ-ACK codebook in the first PUCCH according to a difference between the total number of resource elements of the first PUCCH and the first number of resource elements used for the first HARQ-ACK codebook.

[0009] According to another aspect of the present disclosure, a UE for transmitting a PUCCH is provided. The UE includes: a processor configured to execute a computer-executable program, and a memory coupled to the processor and configured to store the computer-executable program, wherein the computer-executable program instructs the processor to execute the above-mentioned method for transmitting a PUCCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Various aspects of the present disclosure are best understood from the following detailed disclosure when read with the accompanying drawings. Various features are not drawn to scale. The dimensions of various features may be arbitrarily increased or decreased for clarity of discussion.

[0011] Figure 1 is a schematic diagram illustrating a high priority physical uplink control channel (PUCCH) overlapping with a low priority PUCCH according to an embodiment of the present disclosure.

[0012] Figure 2 FIG. 1 is a schematic diagram illustrating a high-priority PUCCH overlapped with a high-priority PUCCH and a low-priority PUCCH overlapped with a low-priority PUCCH according to an embodiment of the present disclosure.

[0013] Figure 3 is a schematic diagram illustrating a low priority PUCCH and a high priority PUCCH overlapping with a high priority physical uplink shared channel (PUSCH) according to an embodiment of the present disclosure.

[0014] Figure 4 FIG. 1 is a schematic diagram illustrating a low-priority PUCCH and a high-priority PUCCH overlapping with a low-priority PUSCH according to an embodiment of the present disclosure.

[0015] Figure 5 is a flowchart illustrating a method of transmitting a PUCCH according to an embodiment of the present disclosure.

[0016] Figure 6 is a block diagram illustrating a node for wireless communication according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0017] The following disclosure contains specific information related to exemplary embodiments of the present disclosure. The accompanying drawings and the accompanying detailed disclosure are directed to exemplary embodiments. However, the present disclosure is not limited to these exemplary embodiments. Other variations and embodiments of the present disclosure will occur to those skilled in the art. Unless otherwise indicated, similar or corresponding elements in the drawings may be represented by similar or corresponding reference numerals. In addition, the drawings and illustrations are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

[0018] For consistency and ease of understanding, similar features are indicated by reference numerals in the exemplary drawings (although not shown in some examples). However, features in different embodiments may differ in other aspects and should not be narrowly limited to the features shown in the drawings.

[0019] The phrases "one embodiment" and "some embodiments" may each refer to one or more of the same or different embodiments. The term "coupled" is defined as connected directly or indirectly through intermediate elements and is not necessarily limited to physical connections. The term "comprising" can mean "including but not necessarily limited to" and specifically indicates open inclusion or membership in the disclosed combinations, groups, series, and equivalents.

[0020] The term "and / or" is used herein only to describe the association relationship between associated objects and indicates that three possible relationships exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. "A and / or B and / or C" can mean that at least one of A, B, and C exists, A and B exist simultaneously, A and C exist simultaneously, B and C exist simultaneously, and A, B, and C exist simultaneously. In addition, the character " / " used herein generally indicates that the former and the latter associated objects are in an "or" relationship.

[0021] In addition, any two or more items in this disclosure can be logically and reasonably appropriately combined: paragraphs, (sub) item numbers, points, actions, behaviors, terms, alternatives, examples or claims to form a specific method. Any sentence, paragraph, (sub) item number, point, action, behavior, term or claim in this disclosure can be implemented independently and separately to form a specific method. For example, dependencies such as "based on", "more specifically", "preferably", "in one embodiment", "in one implementation", "in an alternative" in this disclosure may only refer to a possible example that does not limit the specific method.

[0022] For the purpose of non-limiting explanation, specific details such as functional entities, technologies, protocols, standards, etc. are set forth to provide an understanding of the disclosed technology. In other instances, detailed disclosure of well-known methods, technologies, systems, and architectures is omitted to avoid obscuring the present disclosure with unnecessary details.

[0023] Those skilled in the art will recognize that any (one or more) disclosed network functions or (one or more) algorithms can be implemented by hardware, software, or a combination of software and hardware. The disclosed functions can correspond to modules, which can be software, hardware, firmware, or any combination thereof. Software implementations can include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. For example, one or more microprocessors or general-purpose computers with communication processing capabilities can be programmed with corresponding executable instructions and execute the disclosed (one or more) network functions or (one or more) algorithms. The microprocessor or general-purpose computer can be composed of an application-specific integrated circuit (ASIC), a programmable logic array, and / or one or more digital signal processors (DSP). Although some of the disclosed embodiments relate to software installed and executed on computer hardware, alternative implementations as firmware or hardware or a combination of hardware and software are also within the scope of this disclosure.

[0024] Computer-readable media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (CD) read-only memory (CD-ROM), cassettes, magnetic tapes, disk storage devices, or any other equivalent medium that can store computer-readable instructions.

[0025] A radio communication network architecture (e.g., a long term evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Pro system, or a new radio (NR) system) typically may include at least one base station (BS), at least one UE, and one or more optional network elements that provide a connection to the network. The UE may communicate with a network (e.g., a core network (CN), an evolved packet core (EPC) network, an evolved universal terrestrial radio access network (E-UTRAN), a next-generation core (NGC), a 5G core (5G Core, 5GC), or the Internet) via a radio access network (RAN) established by one or more BSs.

[0026] A UE according to the present disclosure may include, but is not limited to, a mobile base station, a mobile terminal or device, or a user communication radio terminal. For example, a UE may be a portable radio device, including, but not limited to, a mobile phone, tablet computer, wearable device, sensor, or personal digital assistant (PDA) with wireless communication capabilities. A UE may be configured to receive and transmit signals to one or more cells in a RAN over an air interface.

[0027] A BS may include, but is not limited to, a Node B (NB) in the Universal Mobile Telecommunication System (UMTS), an evolved Node B (eNB) in LTE-A, a Radio Network Controller (RNC) in UMTS, a Base Station Controller (BSC) in the Global System for Mobile Communications (GSM) / Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS connected to a 5GC, a next-generation Node B (gNB) in a 5G-RAN (or a 5G Access Network (5G-AN)), and any other device capable of controlling radio communications and managing radio resources within a cell. A BS may serve one or more UEs via a radio interface to the network.

[0028] The BS may be configured to provide communication services based on at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly referred to as 2G), GERAN, General Packet Radio Service (GPRS), UMTS based on basic Wideband Code Division Multiple Access (W-CDMA) (commonly referred to as 3G), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, enhanced LTE (eLTE), NR (commonly referred to as 5G), and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0029] The BS may be operable to provide radio coverage to a specific geographical area using a plurality of cells forming a RAN. The BS may support the operation of cells. Each cell may be operable to provide services to at least one UE within its radio coverage. More specifically, each cell (often referred to as a serving cell) may provide services to one or more UEs within its radio coverage (e.g., each cell schedules downlink (DL) resources and optional uplink (UL) resources to at least one UE within its radio coverage for DL ​​and optional UL packet transmission). The BS may communicate with one or more UEs in a radio communication system through a plurality of cells.

[0030] The cell can allocate sidelink (SL) resources to support proximity service (ProSe), LTE SL service, and LTE / NR vehicle-to-everything (V2X) service. Each cell may have a coverage area that overlaps with other cells. In the case of multi-RAT dual connectivity (MR-DC), the master cell of the master cell group (MCG) or the secondary cell group (SCG) may be referred to as a special cell (SpCell). The primary cell (PCell) may refer to the SpCell of the MCG. The primary SCG cell (PSCell) may refer to the SpCell of the SCG. MCG may refer to a group of service cells associated with a master node (MN), including SpCell and optionally one or more secondary cells (SCell). SCG may refer to a group of service cells associated with a secondary node (SN), including SpCell and optionally one or more SCells.

[0031] As previously disclosed, the frame structure of NR supports flexible configuration to adapt to various next-generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while meeting high reliability, high data rate, and low latency requirements. The orthogonal frequency-division multiplexing (OFDM) technology agreed in the 3rd Generation Partnership Project (3GPP) can be used as the baseline for the NR waveform. Scalable OFDM parameter sets such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP) can also be used. Additionally, two coding schemes are applied to NR: (1) low-density parity-check (LDPC) and (2) polarization code. The coding scheme adaptability can be configured based on channel conditions and / or service applications.

[0032] Furthermore, the transmission time interval of a single NR frame should include at least DL transmission data, a guard period, and UL transmission data. The respective portions of DL transmission data, guard period, and UL transmission data should also be dynamically configured, for example, based on the NR network. SL resources can also be provided via NR frames to support ProSe services or V2X services.

[0033] In a NR system, multiple types of services can be supported in a cell, each with different latency and reliability requirements. When a UE has both eMBB and URLLC services, the physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) transmission for the eMBB service may conflict with the PUSCH transmission for the URLLC service. In this case, to ensure that the latency requirements of the URLLC service are met, the PUSCH or PUCCH transmission for the eMBB service can be canceled so that the UE can transmit the PUSCH for the URLLC service. If the PUCCH transmission carrying the hybrid automatic repeat request (HARQ) acknowledgment (ACK) is canceled, the gNB needs to reschedule the physical downlink shared channel (PDSCH) corresponding to the PUCCH transmission, which may affect system capacity because PDSCH rescheduling can consume a large amount of radio resources. Therefore, when the PUSCH for URLLC services overlaps with the low-priority PUCCH carrying HARQ-ACK for eMBB services, a mechanism is needed in the NR system to multiplex the HARQ-ACK for eMBB services in the high-priority UL channel (e.g., PUSCH) for URLLC services.

[0034] In 3GPP Rel-16, the UE can be configured with two HARQ-ACK codebooks. If the UE is configured with a pdsch-HARQ-ACK-Codebook-List, the UE can generate one or two HARQ-ACK codebooks according to the pdsch-HARQ-ACK-Codebook-List. When the UE generates a HARQ-ACK codebook, the HARQ-ACK codebook is associated with the PUCCH with a priority index of 0. The UE only multiplexes HARQ-ACK information associated with the same priority index (e.g., priority index 0) in the HARQ-ACK codebook.

[0035] When the UE generates two HARQ-ACK codebooks, the first HARQ-ACK codebook is associated with a PUCCH with a priority index of 0 (e.g., low priority), and the second HARQ-ACK codebook is associated with a PUCCH with a priority index of 1 (e.g., high priority).

[0036] The UE is configured with the first and second HARQ-ACK codebooks for each of {PUCCH-Config, UCI-OnPUSCH, PDSCH-codeBlockGroupTransmission} through {PUCCHConfigurationList, UCI-OnPUSCH-List, PDSCH-CodeBlockGroupTransmission-List} respectively.

[0037] In 3GPP Rel-16, due to the introduction of intra-UE prioritization, if a UE is scheduled using a high-priority PUSCH or PUCCH that overlaps with a low-priority HARQ-ACK PUCCH, the low-priority HARQ-ACK PUCCH can be cancelled. Therefore, when a low-priority PUSCH overlaps with a high-priority PUCCH, the low-priority HARQ-ACK codebook multiplexed in the low-priority PUSCH is cancelled.

[0038] To improve spectral efficiency, when PUCCH overlaps, a mechanism is needed for multiplexing the low-priority HARQ-ACK codebook of the low-priority PUCCH and the high-priority HARQ-ACK codebook and high-priority scheduling request (SR) of the high-priority PUCCH in the PUCCH. In addition, when the PUCCH overlaps with the low-priority PUSCH or the high-priority PUSCH, it is also beneficial to consider a mechanism for multiplexing the low-priority HARQ-ACK codebook of the low-priority PUCCH and the high-priority HARQ-ACK codebook and high-priority SR of the high-priority PUCCH in the low-priority PUSCH or the high-priority PUSCH.

[0039] I. Multiplexing PUCCHs of different priorities on PUCCH

[0040] When a high priority PUCCH overlaps with a low priority PUCCH, the UE needs to determine the PUCCH in which high priority uplink control information (UCI) and low priority UCI are multiplexed. In order to avoid discarding low priority UCI without jeopardizing the delay and reliability requirements of high priority UCI, a high priority PUCCH can be selected. A method is needed to determine the PUCCH resources for multiplexing high priority UCI and low priority UCI. In order to ensure the reliability of high priority UCI and low priority UCI, some conditions can be considered to determine the applicability of multiplexing low priority UCI in high priority PUCCH. In addition, a rate matching method is needed for multiplexing high priority UCI and low priority UCI.

[0041] II. Multiplexing PUCCH and PUSCH with different priorities

[0042] When high-priority PUCCH and low-priority PUCCH overlap with low-priority PUSCH, to ensure the reliability of high-priority UCI and low-priority UCI, certain conditions can be considered to determine the applicability of multiplexing high-priority UCI and low-priority UCI in low-priority PUSCH. In addition, rate matching methods and resource mapping methods for multiplexing high-priority UCI and low-priority UCI are also required.

[0043] When high-priority PUCCH and low-priority PUCCH overlap with high-priority PUSCH, to ensure the reliability of high-priority UCI and low-priority UCI, certain conditions can be considered to determine the applicability of multiplexing high-priority UCI and low-priority UCI in high-priority PUSCH. In addition, rate matching methods and resource mapping methods for multiplexing high-priority UCI and low-priority UCI are also required.

[0044] Multiplexing PUCCHs of different priorities on PUCCH

[0045] Disclosed is a method for multiplexing (one or more) UCIs of a low-priority PUCCH in a high-priority PUCCH when the high-priority PUCCH overlaps with the low-priority PUCCH in the time domain. It should be noted that the "high-priority PUCCH" and "low-priority PUCCH" disclosed herein may refer to a group of high-priority PUCCHs and a group of low-priority PUCCHs, respectively, and refer to PUCCHs carrying (one or more) multiplexed UCIs determined according to the UCI multiplexing procedure specified in Section 9.2.5 of 3GPP TS 38.213 V16.3.0. Figure 1 is a schematic diagram illustrating a high priority PUCCH overlapping with a low priority PUCCH according to an embodiment of the present disclosure. Figure 1 As shown, when a high-priority PUCCH 100 (e.g., HP PUCCH 1) overlaps with a low-priority PUCCH 102 (e.g., LP PUCCH 1), the high-priority PUCCH 100 and the low-priority PUCCH 102 in the following methods may respectively refer to HP PUCCH 1 and LP PUCCH 1. In addition, the high-priority UCI and the low-priority UCI in the following methods may respectively refer to the UCI associated with HP PUCCH 1 and the UCI associated with LP PUCCH 1. Figure 2 is a schematic diagram showing a high priority PUCCH overlapping with a high priority PUCCH and a low priority PUCCH overlapping with a low priority PUCCH according to an embodiment of the present disclosure. Figure 2As shown, a high-priority PUCCH 200 (e.g., HP PUCCH 1) may overlap with a high-priority PUCCH 202 (e.g., HP PUCCH 2), and a low-priority PUCCH 204 (e.g., LP PUCCH 1) may overlap with a low-priority PUCCH 206 (e.g., LP PUCCH 2). The UE may first determine to multiplex the UCI associated with HP PUCCH 1 and the UCI associated with HP PUCCH 2 in HP PUCCH 1, and to multiplex the UCI associated with LP PUCCH 1 and the UCI associated with LP PUCCH 2 in LP PUCCH 1. The remaining PUCCHs include HP PUCCH 1 (e.g., high-priority PUCCH 200) and LP PUCCH 1 (e.g., low-priority PUCCH 204), where HP PUCCH 1 overlaps with LP PUCCH 1. The high priority PUCCH and the low priority PUCCH in the following methods may respectively refer to HP PUCCH 1 and LP PUCCH 1. The high priority UCI and the low priority UCI in the following methods may respectively refer to UCI multiplexed in HP PUCCH 1 and UCI multiplexed in LP PUCCH 1.

[0046] Method 1: When a high-priority PUCCH overlaps with a low-priority PUCCH in the time domain, the UE may multiplex the UCI of the low-priority PUCCH in the high-priority PUCCH when one or more of the following conditions are met:

[0047] Condition 1: For high-priority PUCCH and low-priority PUCCH, the timeline requirements for UCI multiplexing are met.

[0048] Condition 2: Channel state information (CSI) is not included in the high priority PUCCH.

[0049] Condition 3: CSI part 2 is not included in the high priority PUCCH.

[0050] Condition 4: The high-priority PUCCH is PUCCH format 2, PUCCH format 3, or PUCCH format 4.

[0051] Condition 5: The high-priority PUCCH is in the short PUCCH format.

[0052] Condition 6: PUCCHs of different priorities may use different PUCCH formats (eg, a high-priority PUCCH uses a short PUCCH, while a low-priority PUCCH uses a long PUCCH).

[0053] Condition 7: The high-priority PUCCH is scheduled by a DCI format, which may be DCI format 1_0, 1_1, or 1_2.

[0054] Condition 8: The high-priority PUCCH is not a PUCCH resource configured in the 'SPS-Config' IE.

[0055] Condition 9: The high-priority PUCCH is not a PUCCH resource configured in the 'sps-PUCCH-AN-List-r16' IE.

[0056] Condition 10: The UE has the capability to multiplex high-priority UCI and low-priority UCI.

[0057] Condition 11: The gNB configures the UE to multiplex high-priority UCI and low-priority UCI.

[0058] Condition 12: The DCI format notifies the UE to multiplex high-priority UCI and low-priority UCI.

[0059] Condition 13: The high priority PUCCH is configured by the 'PUCCH-Config' IE including the 'subslotLengthForPUCCH-R16' IE.

[0060] Condition 14: The high-priority PUCCH is configured by the 'PUCCH-Config' IE including the 'dl-DataToUL-ACK-R16' IE.

[0061] Condition 15: The high priority PUCCH is a PUCCH format configured for multiplexing low priority UCI. For the PUCCH format in the second 'PUCCH-Config' IE, the IE may be included in the 'PUCCH-FormatConfig' IE to indicate the applicability of the PUCCH format for multiplexing.

[0062] Condition 16: When the high-priority PUCCH is a PUCCH for HARQ-ACK, the number of multiplexed high-priority UCI bits is 0 HP UCI plus the number of low priority UCI bits O LP UCI The maxPayloadSize of the PUCCH resource set in which the high priority PUCCH is selected shall not exceed. LP UCI The scaling may be by a predefined or preconfigured scaling factor (eg, the ratio of the maxPayloadSize of the high priority PUCCH to the maxPayloadSize of the low priority PUCCH of the same PUCCH format).

[0063] Condition 17: The number of PRBs of the high-priority PUCCH determined for the high-priority UCI is less than PRBs, of which The maximum number of physical resource blocks (PRBs) configured by the 'nrofPRBS' IE of the PUCCH format of the high priority PUCCH.

[0064] Condition 18: The number of resource elements available for low-priority UCI bits in the high-priority PUCCH results in a code rate for the low-priority UCI being higher than a threshold. The threshold may be determined based on a preconfigured value or a value indicated via a DCI format.

[0065] Condition 19: The UE may reuse a low-priority HARQ-ACK codebook in a high-priority PUCCH when one or more of the following conditions are met:

[0066] Condition 19a: The size of the low-priority HARQ-ACK codebook is not greater than the preconfigured number of bits.

[0067] Condition 19b: The low-priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook;

[0068] Condition 19c: The low priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook. The UE transmits HARQ-ACK information in the low priority PUCCH for only Semi-Persistent Scheduling (SPS) PDSCH release indicated by DCI format 1_0 with a counter DAI field value of 1, only for PDSCH reception scheduled by DCI format 1_0 with a counter DAI field value of 1 on the PCell, or only for candidate PDSCH reception determined in section 9.1.2.1 of 3GPP TS 38.213. A,c (One or more) SPS PDSCH reception within an occasion.

[0069] Condition 19d: The low-priority HARQ-ACK codebook includes only a sub-codebook based on a transport block (TB).

[0070] Condition 19e: No 'PDSCH-CodeBlockGroupTransmission' IE is provided for the low priority HARQ-ACK codebook.

[0071] Condition 20: The UE may multiplex a low-priority SR in a high-priority PUCCH when one or more of the following conditions are met:

[0072] Condition 20a: The size of the low-priority SR is not greater than the preconfigured number of bits.

[0073] Condition 20b: The low-priority HARQ-ACK codebook is multiplexed with the low-priority SR in the low-priority PUCCH, and the size of the low-priority HARQ-ACK codebook plus the low-priority SR is not greater than the preconfigured number of bits.

[0074] Condition 21: The UE may multiplex low-priority CSI in high-priority PUCCH when one or more of the following conditions are met:

[0075] Condition 21a: Low-priority CSI includes only CSI part 1.

[0076] Condition 21b: The size of the low-priority CSI is not greater than the preconfigured number of bits.

[0077] Condition 21c: The low-priority HARQ-ACK codebook is multiplexed with the low-priority CSI in the low-priority PUCCH, and the size of the low-priority HARQ-ACK codebook plus the low-priority CSI is no greater than the preconfigured number of bits.

[0078] When a high-priority PUCCH overlaps with a low-priority PUCCH, the following method may be used to determine the PUCCH resource of the high-priority PUCCH.

[0079] Method 2: When the high-priority PUCCH is a dynamically scheduled PUCCH resource for the high-priority HARQ-ACK codebook, the UE may select a PUCCH resource set based on the total payload size of the high-priority UCI in the high-priority PUCCH, and use the PUCCH resource indicator (PRI) in the DCI format that schedules the high-priority PUCCH to select the high-priority PUCCH from the PUCCH resources in the selected PUCCH resource set. For example, based on the total payload size determined according to the UCI multiplexing procedure specified in Section 9.2.5 of 3GPP TS 38.213 V16.3.0. HP UCI For a high priority PUCCH, the PUCCH resource set may be selected as follows: If the UE transmits a PUCCH including HARQ-ACK information bits, HP UCI UCI information bits, the UE determines the PUCCH resource set as:

[0080] -If O HP UCI ≤2, then it is the first set of PUCCH resources with PUCCH-ResourceSetId = 0, if the HARQ-ACK information and SR transmission occur simultaneously, in which case the SR transmission includes 1 or 2 HARQ-ACK information bits and a positive or negative SR, or

[0081] -If 2≤O HP UCI ≤ N2, the second set of PUCCH resources with pucch-ResourceSetId=1 provided by higher layers, where N2 is equal to maxPayloadSize if maxPayloadSize is provided for the PUCCH resource set with pucch-ResourceSetId=1; otherwise, N2 is equal to 1706, or

[0082] -If N2≤O HP UCI ≤ N3, the third set of PUCCH resources with pucch-ResourceSetId=2 provided by higher layers, where N3 is equal to maxPayloadSize if maxPayloadSize is provided for the PUCCH resource set with pucch-ResourceSetId=2; otherwise, N3 is equal to 1706, or

[0083] -If N3≤O HP UCI ≤1706, it is the fourth group of PUCCH resources with pucch-ResourceSetId=3 provided by a higher layer.

[0084] After selecting the PUCCH resource, the number of PRBs of the PUCCH resource is determined based on one or more of the following parameters: the total payload size of the high priority UCI; HP UCI , the total payload size of low-priority UCI in low-priority PUCCHs multiplexed in high-priority PUCCHs, the maxCodeRate of the high-priority PUCCH, and the maxCodeRate of the low-priority PUCCHs. Note that a low-priority PUCCH can be a PUCCH carrying low-priority UCI, and the UE can perform the UCI multiplexing procedure specified in section 9.2.5 of 3GPP TS 38.213 V16.3.0 for a group of low-priority PUCCHs. Note that multiplexing of low-priority UCI to be included in a high-priority PUCCH can be performed based on Method 1 and the methods described below.

[0085] In some embodiments, if Then the UE satisfies Minimum quantity of PRBs are used to transmit the high priority HARQ-ACK codebook, high priority SR and low priority HARQ-ACK codebook, and if but in is the maximum number of PRBs configured by nrofPRB of the PUCCH format for the high priority PUCCH, r HP is the maxCodeRate of the PUCCH format of the high priority PUCCH configured in the second PUCCH-Config, and and Q m Defined in 3GPP TS 38.213 V16.3.0. If Then UE is The high priority HARQ-ACK codebook, high priority SR and low priority HARQ-ACK codebook (if determined to be used for multiplexing) are transmitted in PRBs.

[0086] In some embodiments, if Then the UE satisfies Minimum quantity of PRBs are used to transmit the high priority HARQ-ACK codebook, high priority SR and low priority HARQ-ACK codebook, and if but Where X can be a predefined or preconfigured value, such as where r LP It is the maxCodeRate of the PUCCH format of the low priority PUCCH configured in the first PUCCH-Config or the maxCodeRate of the PUCCH format of the high priority PUCCH configured in the first PUCCH-Config. When the low priority PUCCH is PUCCH format 0 or PUCCH format 1, it can be r LP Assume preconfigured or predefined values, such as r LP =0.8.

[0087] The following method may be used to determine the number of available resource elements for multiplexing low-priority UCI in a high-priority PUCCH and a threshold value of the number of available resource elements.

[0088] Method 3: When the high-priority PUCCH and the low-priority PUCCH overlap, the UE may perform rate matching on the UCI of the high-priority PUCCH to be multiplexed in the high-priority PUCCH based on the maxCodeRate of the PUCCH format of the high-priority PUCCH configured in the second PUCCH-Config, denoted as r HP For example, the number of resource elements used to multiplex the high-priority HARQ-ACK codebook can be calculated according to the following equation: Among them O HP ACK is the payload of the high priority HARQ-ACK codebook, O HP SR is the payload size of the high-priority SR, L HP UCI is the size of the cyclic redundancy check (CRC) of the high priority UCI, and E tot,HP is the total number of resource elements of high priority PUCCH resources.

[0089] In some embodiments, the high priority CSI part 1 HP CSI-1 The remaining number of resource elements available for multiplexing low priority UCI in high priority PUCCH may be determined as E tot,HP -E HP UCI The UE can determine whether to reuse the low-priority HARQ-ACK codebook in the high-priority PUCCH based on the minimum number of resource elements. The minimum number of resource elements is calculated according to the following equation: Among them O LP ACK is the net payload size of the low priority HARQ-ACK codebook, L LP UCI is the size of the CRC of the low priority UCI, r LP is the maxCodeRate of the PUCCH format of the low-priority PUCCH configured in the first PUCCH-Config or the maxCodeRate of the PUCCH format of the high-priority PUCCH configured in the first PUCCH-Config, E tot,LP is the total number of resource elements of the low priority PUCCH resources. LP SR The units digit may be included in the low priority UCI. Therefore, if E LP UCI,min Greater than E tot,HP -E HP UCI , the UE does not reuse the low-priority HARQ-ACK codebook in the high-priority PUCCH.

[0090] In some embodiments, when the number of resource elements is insufficient to multiplex the low-priority HARQ-ACK codebook in the high-priority PUCCH, the low-priority HARQ-ACK codebook may be compressed according to the method for HARQ-ACK codebook compression described below.

[0091] In some embodiments, when the number of resource elements is insufficient to reuse the low-priority HARQ-ACK codebook, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the dynamically scheduled PDSCH reception. Alternatively, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the SPS PDSCH reception.

[0092] The following method may be used to compress the size of the low priority HARQ-ACK codebook to be used for multiplexing in the high priority PUCCH.

[0093] Method 4: Spatial bundling parameters and code block group (CBG) parameters may be configured separately for a low priority HARQ-ACK codebook to be used for multiplexing in a high priority PUCCH and a low priority HARQ-ACK codebook to be used for multiplexing in a low priority PUCCH.

[0094] In some embodiments, harq-ACK-SpatialBundlingHPPUCCH may be configured in PhysicalCellGroupConfig to instruct the UE to perform spatial bundling on the low-priority HARQ-ACK codebook and / or the high-priority HARQ-ACK codebook when the UE multiplexes the low-priority HARQ-ACK codebook and / or the high-priority HARQ-ACK codebook in the high-priority PUCCH. In some embodiments, harq-ACK-SpatialBundlingPUCCH may be configured in PhysicalCellGroupConfig to instruct the UE to perform spatial bundling on the low-priority HARQ-ACK codebook when the UE multiplexes the low-priority HARQ-ACK codebook in the low-priority PUCCH. In some embodiments, when harq-ACK-SpatialBundlingPUCCH is configured, the UE performs spatial bundling on the low-priority HARQ-ACK codebook when the UE multiplexes the low-priority HARQ-ACK codebook in the high-priority PUCCH.

[0095] In some embodiments, harq-ACK-TBHPPUCCH can be configured in PhysicalCellGroupConfig or PUCCH-Config to indicate that the CBG-based HARQ-ACK codebook is compressed. In some embodiments, if the low-priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, when the UE multiplexes the low-priority HARQ-ACK codebook in the high-priority PUCCH, the UE only transmits the HARQ-ACK bits of the transport block (TB) in the PDSCH corresponding to the low-priority HARQ-ACK codebook. In some embodiments, if the low-priority HARQ-ACK codebook is a type 2 HARQ-ACK codebook, when the UE multiplexes the low-priority HARQ-ACK codebook in the high-priority PUCCH, the UE only transmits the TB-based subcodebook of the low-priority HARQ-ACK codebook. In some embodiments, if the low priority HARQ-ACK codebook is a type 2 HARQ-ACK codebook, when the UE multiplexes the low priority HARQ-ACK codebook in the high priority PUCCH, the UE transmits the TB-based subcodebook of the low priority HARQ-ACK codebook and the HARQ-ACK bits of the TB in the PDSCH corresponding to the CBG-based subcodebook of the low priority HARQ-ACK codebook.

[0096] Multiplexing PUCCH and PUSCH with different priorities

[0097] Figure 3 FIG. 1 is a schematic diagram illustrating a low-priority PUCCH and a high-priority PUCCH overlapping with a high-priority PUSCH according to an embodiment of the present disclosure. Figure 4 FIG is a schematic diagram showing a low priority PUCCH and a high priority PUCCH overlapping with a low priority PUSCH according to an embodiment of the present disclosure. Figure 3 and Figure 4 When a low priority PUCCH 302 or a low priority PUCCH 402 (e.g., LP PUCCH 1) associated with a low priority UCI and a high priority PUCCH 300 or a high priority PUCCH 400 (e.g., HP PUCCH 1) associated with a high priority UCI overlap with a PUSCH in the time domain, the following method may be used to configure or indicate a beta offset and a scaling factor for multiplexing the low priority UCI and the high priority UCI in the PUSCH. The PUSCH may be as follows: Figure 3 The high priority PUSCH (e.g., HP PUSCH 304) shown, or the PUSCH may be as shown Figure 4A low priority PUSCH is shown (eg, LP PUSCH 404). The priority of a PUSCH may be indicated by a priority indicator in the DCI format that schedules the PUSCH.

[0098] It should be noted that the high priority PUCCH and low priority PUCCH described below may refer to a group of high priority PUCCHs and a group of low priority PUCCHs, respectively, and refer to PUCCHs carrying (one or more) multiplexed UCIs determined according to the UCI multiplexing process specified in Section 9.2.5 of 3GPP TS 38.213 V16.3.0.

[0099] Method 5: When the UE multiplexes UCI of the first priority level in the PUSCH of the second priority level (e.g., low priority), the beta offset and scaling factor can be configured specifically for the UCI of the first priority level (e.g., high priority). In some embodiments, the first priority level and the second priority level can be the same or different.

[0100] In some embodiments, when the UE multiplexes UCI in the high-priority PUSCH, LPUCI-OnHPPUSCH and HPUCI-OnHPPUSCH are used to configure the beta offset and scaling factor for the low-priority UCI and high-priority UCI, respectively. For example, and And can be configured in HPUCI-OnHPPUSCH and In addition, when a dynamic beta offset is configured in LPUCI-OnHPPUSCH, a beta_offset indicator (e.g., a value of a DCI field) for the low-priority UCI may be included in the DCI format for scheduling a high-priority PUSCH. More specifically, when a dynamic beta offset is configured, 4 values ​​are configured for each of the above parameters. The beta_offset indicator in the DCI format may be used to indicate a value to be applied from the 4 values ​​of each parameter. When a dynamic beta offset is configured in HPUCI-OnHPPUSCH, a beta_offset indicator for the high-priority UCI may be included in the DCI format for scheduling a high-priority PUSCH. In some embodiments, when an explicit indication of a beta offset for the low-priority UCI is not included in the DCI format for scheduling a high-priority PUSCH, a semi-static beta offset may be configured in LPUCI-OnHPPUSCH. In addition, can be used to limit the maximum number of resource elements used to multiplex high-priority UCI in the high-priority PUSCH, and It can be used to limit the maximum number of resource elements used to multiplex low-priority UCI in high-priority PUSCH. It can be used to limit the maximum number of resource elements used to multiplex high-priority UCI and low-priority UCI in the high-priority PUSCH.

[0101] In some embodiments, when the UE multiplexes UCI in the low-priority PUSCH, LPUCI-OnLPPUSCH and HPUCI-OnLPPUSCH are used to configure the beta offset and scaling factor for the low-priority UCI and high-priority UCI, respectively. For example, and And can be configured in HPUCI-OnLPPUSCH and In addition, when a dynamic beta offset is configured in LPUCI-OnLPPUSCH, a beta_offset indicator for the low priority UCI (e.g., the value of a DCI field in a DCI format indicating a beta offset relative to the configured beta offset) may be included in the DCI format for scheduling the low priority PUSCH. When a dynamic beta offset is configured in HPUCI-OnLPPUSCH, a beta_offset indicator for the high priority UCI may be included in the DCI format for scheduling the low priority PUSCH. In some embodiments, when an explicit indication of the beta offset for the high priority UCI is not included in the DCI format for scheduling the low priority PUSCH, a semi-static beta offset may be configured in HPUCI-OnLPPUSCH. In addition, can be used to limit the maximum number of resource elements used to multiplex low-priority UCI in the low-priority PUSCH, and It can be used to limit the maximum number of resource elements used to multiplex high priority UCI in low priority PUSCH. It can be used to limit the maximum number of resource elements used for multiplexing high-priority UCI and low-priority UCI in the low-priority PUSCH.

[0102] In some embodiments, when an explicit indication of the beta offset for low-priority UCI is not included in the DCI format for scheduling a high-priority PUSCH, and a dynamic beta offset is configured in LPUCI-OnHPPUSCH, the UE uses the beta offset with the minimum value when multiplexing low-priority UCI in a high-priority PUSCH. In some embodiments, when high-priority UCI is not multiplexed in a high-priority PUSCH, the beta_offset indicator for the high-priority UCI may be used to indicate the beta offset for the low-priority UCI. In some embodiments, the beta offset in the same entry in LPUCI-OnHPPUSCH is shown as an entry in HPUCI-OnHPPUSCH, where the beta offset is indicated by the beta_offset indicator. For example, if the beta_offset indicator indicates a first set of beta offsets for high-priority UCI, the first set of beta offsets for low-priority UCI is also indicated.

[0103] In some embodiments, when an explicit indication of the beta offset for high-priority UCI is not included in the DCI format for scheduling a low-priority PUSCH, and a dynamic beta offset is configured in the HPUCI-OnLPPUSCH, the UE uses the beta offset with the maximum value when multiplexing high-priority UCI in the low-priority PUSCH. In some embodiments, when low-priority UCI is not multiplexed in the low-priority PUSCH, the beta_offset indicator for the low-priority UCI may be used to indicate the beta offset for the high-priority UCI. In some embodiments, the beta_offset indicator for the low-priority UCI may be used to indicate the beta offset for the high-priority UCI regardless of whether there is low-priority UCI for multiplexing in the low-priority PUSCH. In some embodiments, the beta offset in the same entry in the HPUCI-OnLPPUSCH is shown as the entry in the LPUCI-OnLPPUSCH, where the beta offset is indicated by the beta_offset indicator. For example, if the beta_offset indicator indicates the first set of beta offsets for the UCI of low priority, the first set of beta offsets for the UCI of high priority is also indicated.

[0104] The following method may be used to multiplex the UCI(s) of a low priority PUCCH in a high priority PUSCH.

[0105] Method 6: When the low-priority PUCCH overlaps with the high-priority PUSCH in the time domain, the UE may multiplex the UCI of the low-priority PUCCH in the high-priority PUSCH when one or more of the following conditions are met:

[0106] Condition 1: For low-priority PUCCH and high-priority PUSCH, the timeline requirements for UCI multiplexing are met.

[0107] Condition 2: A-CSI is not triggered to be used for multiplexing in the high-priority PUSCH.

[0108] Condition 3: A-CSI is triggered to be used for multiplexing in the high priority PUSCH, and all CSI part 1 reports are multiplexed in the high priority PUSCH.

[0109] Condition 4: High priority CSI with CSI part 2 is not configured or triggered in the high priority PUSCH or the high priority PUCCH overlapping with the high priority PUSCH.

[0110] Condition 5: The low-priority PUCCH is PUCCH format 0 or PUCCH format 2.

[0111] Condition 6: The low-priority PUCCH is a PUCCH used for HARQ-ACK, and is selected from the first PUCCH resource set.

[0112] Condition 7: The high-priority PUSCH is not a configured grant (CG) PUSCH.

[0113] Condition 8: The duration of the high-priority PUSCH is longer than the number of OFDM symbols. The number of OFDM symbols can be preconfigured.

[0114] Condition 9: The high-priority PUSCH is not PUSCH repetition type B.

[0115] Condition 10: The low-priority PUCCH and the low-priority PUSCH do not overlap.

[0116] Condition 11 indicates that the UE has the capability to multiplex low-priority UCI in high-priority PUSCH.

[0117] Condition 12: The gNB configures the UE to multiplex low-priority UCI in the high-priority PUSCH.

[0118] Condition 13: When a dynamic beta offset is configured for low priority UCI, an explicit indication of the beta offset for the low priority UCI is included in the UL grant scheduling the high priority PUSCH.

[0119] Condition 14: The UL grant scheduling the high-priority PUSCH may indicate that the low-priority UCI is multiplexed in the high-priority PUSCH.

[0120] Condition 15, for reuse High priority HARQ-ACK code base and for multiplexing The number of 1-bit resource elements in the high priority CSI part shall not exceed Wherein, when the UE multiplexes low-priority UCI in a high-priority PUSCH, X may be determined based on the beta offset and / or scaling factor of the low-priority UCI, and when the UE multiplexes high-priority UCI in a high-priority PUSCH, is the scaling factor for high priority UCIs.

[0121] Condition 16: The number of resource elements in the high-priority PUSCH that can be used to multiplex low-priority UCI bits (e.g., minus the resource elements used to multiplex the high-priority UCI) results in the code rate of the low-priority UCI being higher than the threshold, where The beta offset is the scaling factor for high-priority UCI when the UE multiplexes low-priority UCI in a high-priority PUSCH. When the UE multiplexes low-priority UCI in a high-priority PUSCH, the threshold can be determined based on the preconfigured scaling factor and / or beta offset for the low-priority UCI. The beta offset can be indicated via the UL grant that schedules the high-priority PUSCH.

[0122] Condition 17: When one or more of the following conditions are met, the UE may reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH.

[0123] Condition 17a: The size of the low-priority HARQ-ACK codebook is not greater than the preconfigured number of bits.

[0124] Condition 17b: The low-priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook.

[0125] Condition 17c: The low-priority HARQ-ACK codebook is a HARQ-ACK codebook used only for reception of one or more SPS PDSCHs.

[0126] Condition 17d: The SPS HARQ-ACK bits received by one or more SPS PDSCHs are not multiplexed in the low-priority HARQ-ACK codebook.

[0127] Condition 17e, the low priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, and the UE transmits information in the low priority PUCCH for SPS PDSCH release indicated only by DCI format 1_0 with a counter DAI field value of 1, for PDSCH reception scheduled only by DCI format 1_0 with a counter DAI field value of 1 on the PCell, or for M only for candidate PDSCH reception determined in section 9.1.2.1 of 3GPP TS 38.213 A,c (One or more) SPS PDSCH reception within the occasion. The UL grant scheduling high priority PUSCH may include the UL total DAI field of the low priority HARQ-ACK codebook and

[0128] Condition 17f: The low-priority HARQ-ACK codebook includes only the TB-based sub-codebook.

[0129] Condition 17g: PDSCH-CodeBlockGroupTransmission is not provided for the low-priority HARQ-ACK codebook.

[0130] Condition 17h: The UL grant for scheduling a high-priority PUSCH includes the UL total DAI field of the low-priority HARQ-ACK codebook.

[0131] Condition 17i: The low priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, the UL grant for scheduling the high priority PUSCH includes the UL total DAI field of the low priority HARQ-ACK codebook, and the DAI value indicates

[0132] Condition 178: The UE may multiplex low-priority CSI in high-priority PUSCH when one or more of the following conditions are met:

[0133] Condition 18a: Low priority CSI includes only CSI part 1.

[0134] Condition 18b: The size of the low-priority CSI is not greater than the preconfigured number of bits.

[0135] Condition 18c: The low-priority HARQ-ACK codebook is not multiplexed in the low-priority PUCCH (if the high-priority PUSCH does not exist).

[0136] Method 7: When a low-priority PUCCH including a low-priority HARQ-ACK codebook overlaps with a high-priority PUSCH in the time domain, the UL total DAI field of the low-priority HARQ-ACK codebook may be included in the UL grant scheduling the high-priority PUSCH, and the UE may use the UL total DAI value to determine the size of the low-priority HARQ-ACK codebook to be used for multiplexing in the high-priority PUSCH.

[0137] In some embodiments, the UE may determine whether the UL Total DAI field of the low priority HARQ-ACK codebook is included in the UL grant for scheduling a high priority PUSCH, which is configured by an IE (e.g., TotalDAIforLPUCIonHPPUSCH) in PhysicalCellGroupConfig or PUSCH-Config. In some embodiments, if the low priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, the number of bits is 1, and if the low priority HARQ-ACK codebook is a type 2 HARQ, the number of bits is 2 for a TB-based word codebook, and the number of bits is 2 for a CBG-based subcodebook (if PDSCH-CodeBlockGroupTransmission is configured for the low priority HARQ-ACK codebook). In some embodiments, the UL Total DAI field of the CBG-based subcodebook is not included in the UL grant. In some embodiments, the number of bits of the UL Total DAI field for each subcodebook may be 1 bit. A DAI value of 1 indicates that the UE multiplexes the low-priority HARQ-ACK (sub)codebook in the high-priority PUSCH, while a DAI value of 0 indicates that the UE does not multiplex the low-priority HARQ-ACK (sub)codebook in the high-priority PUSCH.

[0138] In some embodiments, when the UL total DAI field of the low priority HARQ-ACK codebook is not included in the UL grant scheduling the high priority PUSCH, when the low priority HARQ-ACK codebook is multiplexed in the high priority PUSCH and the high priority HARQ-ACK codebook is not multiplexed in the high priority HARCH, the UE may determine the UL total DAI value of the low priority HARQ-ACK codebook based on the UL total DAI field of the high priority HARQ-ACK codebook.

[0139] In some embodiments, when the UL total DAI field of the subcodebook based on the low priority HARQ-ACK CBG is not included in the UL grant for scheduling the high priority PUSCH, the UE may determine the UL total DAI value of the subcodebook based on the low priority HARQ-ACK CBG based on the UL total DAI field of the subcodebook based on the high priority HARQ-ACK CBG, regardless of whether the subcodebook based on the high priority HARQ-ACK CBG is multiplexed in the high priority PUSCH.

[0140] When the UL total DAI is not used to determine the size of the low priority HARQ-ACK (sub) codebook, the rate matching for multiplexing the low priority HARQ-ACK codebook can be based on the preconfigured or predefined HARQ-ACK codebook size. When the UE multiplexes the low priority HARQ-ACK codebook in the high priority PUSCH, the number of resource elements Q used to multiplex the low priority HARQ-ACK codebook can be determined based on the preconfigured or predefined HARQ-ACK codebook size and the preconfigured scaling factor and / or beta offset of the low priority UCI. LP ACK '. When mapped to Q LP ACK When the code rate of the low priority HARQ-ACK codebook of resource elements exceeds the threshold, the UE does not reuse the low priority HARQ-ACK codebook in the high priority PUSCH. When the UE reuses the low priority HARQ-ACK codebook in the high priority PUSCH, the threshold can be determined based on the preconfigured scaling factor and / or beta offset of the low priority UCI. It should be noted that the available resource elements for multiplexing the low priority HARQ-ACK codebook can be less than Q LP ACK The available resource elements for multiplexing the low priority HARQ-ACK codebook depends on the number of resource elements for multiplexing the high priority HARQ-ACK codebook and / or the high priority CSI, and the maximum number of resource elements for multiplexing UCI (e.g., based on In some embodiments, when the size of the low priority HARQ-ACK codebook is less than the preconfigured or predefined HARQ-ACK codebook size, multiple zero bits are padded to the low priority HARQ-ACK codebook until its size is equal to the preconfigured or predefined HARQ-ACK codebook size. In some embodiments, when the size of the low priority HARQ-ACK codebook is greater than the preconfigured or predefined HARQ-ACK codebook size, the low priority HARQ-ACK codebook is truncated until its size is equal to the preconfigured or predefined HARQ-ACK codebook size.

[0141] In some embodiments, when the UL total DAI is not used to determine the size of the low priority HARQ-ACK (sub) codebook, when the size of the low priority HARQ-ACK codebook is less than a threshold (e.g., 12 or 20 bits), rate matching is based on the aforementioned method 7, and when the size of the low priority HARQ-ACK codebook is greater than or equal to the threshold, rate matching is based on the low priority HARQ-ACK codebook size. In some embodiments, when the size of the low priority HARQ-ACK codebook is less than the threshold, multiple zero bits are padded to the low priority HARQ-ACK codebook until its size is equal to the threshold, and rate matching is based on the low priority HARQ-ACK codebook size using zero padding.

[0142] In some embodiments, when the UL total DAI is not used to determine the size of the low priority HARQ-ACK (sub) codebook, rate matching is based on the low priority HARQ-ACK codebook size, and the encoded low priority HARQ-ACK codebook is mapped from the last OFDM symbol of the PUSCH to the high priority PUSCH and backward to earlier OFDM symbols.

[0143] The following method may be used to determine the number of available resource elements for multiplexing low-priority UCI in a high-priority PUSCH and a threshold value of the number of available resource elements.

[0144] Method 8: When high-priority PUCCH and low-priority PUCCH overlap with high-priority PUSCH, when the UE multiplexes the UCI of high-priority PUCCH in high-priority PUSCH (e.g., based on and ), the UE may perform rate matching on the UCI of the high priority PUCCH to be multiplexed in the high priority PUSCH based on the beta offset and scaling factor of the high priority UCI in the high priority PUCCH. For example, the UE may calculate the number of resource elements Q′ for multiplexing the high priority HARQ-ACK codebook according to the following equation: HP ACK :

[0145] Among them O HP ACK is the net payload size of the high priority HARQ-ACK codebook, L HP ACK is the size of the CRC of the high priority HARQ-ACK codebook, C UL-SCH and K rDefined in 3GPP TS 38.212 V16.3.0, and l0 is the OFDM symbol index of the first OFDM symbol after the first set of consecutive (multiple) OFDM symbols carrying DMRS. The remaining number of resource elements available for multiplexing high priority UCI and low priority UCI in the high priority PUSCH can be determined as If no high priority CSI is multiplexed in the high priority PUSCH, but the low priority HARQ-ACK codebook is multiplexed in the high priority PUSCH, the UE may map the low priority HARQ-ACK codebook to resource elements that are not used for mapping the high priority HARQ-ACK codebook in symbols starting with symbol l′0, where l′0 may be preconfigured or predefined (e.g., l′0 may be the OFDM symbol index of the first OFDM symbol after the first group of consecutive (multiple) OFDM symbols carrying a demodulation reference signal (DMRS) in the second hop of the high priority PUSCH). l′0 may be the same as l0. In some embodiments, before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook, when the number of bits of the high priority HARQ-ACK codebook is 0, 1, or 2 bits, the UE may map the low priority HARQ-ACK codebook to resource elements reserved for the high priority HARQ-ACK codebook. The UE may determine whether to reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH based on the minimum number of resource elements. The minimum number of resource elements is calculated according to the following equation: In some embodiments, Then, if Q′ LP ACK,min Greater than The UE does not reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH, where is the number of resource elements used to map the high priority HARQ-ACK codebook in symbols starting from symbol l′0, where is the number of resource elements used to map the high priority HARQ-ACK codebook in symbol 1. In some embodiments, when the high priority HARQ-ACK codebook is not multiplexed in the high priority PUSCH, if Q′ LP ACK,min Greater than The UE does not reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH, where is the number of reserved resource elements for the high-priority HARQ-ACK codebook in symbols starting with 1′0. On the other hand, if the high-priority CSI is not multiplexed in the high-priority PUSCH and the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, the UE may first map the low-priority HARQ-ACK codebook, where the low-priority HARQ-ACK codebook is mapped to resource elements not used for mapping the high-priority HARQ-ACK codebook in symbols starting with symbol 1′0, and then the UE may map the high-priority CSI to resource elements not used for mapping the high-priority HARQ-ACK codebook and the low-priority HARQ-ACK codebook in symbols starting with symbol 0. Alternatively, the UE may map the low-priority HARQ-ACK codebook after mapping the high-priority CSI, and the low-priority HARQ-ACK codebook is mapped to resource elements not used for mapping the high-priority HARQ-ACK codebook and the high-priority CSI in symbols starting with symbol 1′0. The UE can calculate the number of resource elements Q′ used to multiplex the high priority CSI part 1 according to the following equation HP CSI-1 : The UE can calculate the number of resource elements used to multiplex the high priority CSI part 1 in the symbols starting from symbol l′0 according to the following equation in is the number of resource elements used to map high priority CSI part 1 in symbol 1. For example, if Q′ LP ACK,min Greater than Then the UE does not multiplex the low-priority HARQ-ACK codebook in the high-priority PUSCH (for example, assuming that the high-priority CSI only includes CSI part 1).

[0146] In some embodiments, if a high priority CSI Part 2 is multiplexed in a high priority PUSCH, the UE may omit that number of CSI Part 2 reports to provide some resource elements for multiplexing a low priority HARQ-ACK codebook. The number of CSI Part 2 reports may be preconfigured or may be determined based on the CSI report priority value specified in clause 5.2.5 of 3GPP TS 38.214. For example, if the CSI Part 2 report is a report with a priority value above a preconfigured or predefined threshold, the UE may omit the CSI Part 2 report when a low priority HARQ-ACK codebook is multiplexed in a high priority PUSCH. When a high priority CSI Part 2 is present, the UE may calculate the number of resource elements Q′ for multiplexing the high priority CSI Part 2 according to the following equation HP CSI-2 : The UE can calculate the number of resource elements used to multiplex the high priority CSI part 2 in the symbols starting from symbol l′0 according to the following equation in is the number of resource elements used to map high priority CSI Part 2 in symbol 1. If Q′ LP ACK,min Greater than Then the UE does not reuse the low priority HARQ-ACK codebook in the high priority PUSCH. Note that when the number of bits of the high priority HARQ-ACK codebook is 0, 1, or 2, the UE can calculate the number of reserved resource elements for the high priority HARQ-ACK codebook, and the UE can map CSI part 2 to the reserved resource elements before CSI part 2 is truncated by the high priority HARQ-ACK codebook. In this case, if Q′ LP ACK,min Greater than (For example, assuming that the low priority HARQ-ACK codebook is not mapped to the reserved resource element before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook), the UE does not reuse the low priority HARQ-ACK codebook in the high priority PUSCH, where is the number of reserved resource elements for the high priority HARQ-ACK codebook in symbols starting at l′0. Alternatively, if the UE maps the low priority HARQ-ACK codebook to the reserved resource elements before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook, the term in the preceding equation is not required. If the low priority HARQ-ACK codebook is not reused in the high priority PUSCH, the UE may not omit CSI Part 2 reports with priority values ​​higher than the preconfigured or predefined priority value. Note that the UE may omit some CSI Part 2 reports specified in 3GPP TS 38.214. In some embodiments, the UE may omit CSI Part 2 reports in descending order of priority value from the CSI Part 2 report with the highest priority value until the number of resource elements available for reuse of the low priority HARQ-ACK codebook is equal to or greater than Q′ LP ACK,min .

[0147] In some embodiments, when the number of resource elements is insufficient to multiplex the low-priority HARQ-ACK codebook, the UE may compress the low-priority HARQ-ACK codebook according to the method for HARQ-ACK codebook compression described below.

[0148] In some embodiments, when the number of resource elements is insufficient to reuse the low-priority HARQ-ACK codebook, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the dynamically scheduled PDSCH reception. Alternatively, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the SPS PDSCH reception.

[0149] In some embodiments, before the high priority CSI part 1 is punctured by the high priority HARQ-ACK codebook, the UE may map the high priority CSI part 1 to resource elements reserved for the high priority HARQ-ACK codebook.

[0150] In some implementations, the UE may map the low priority HARQ-ACK codebook to resource elements reserved for the high priority HARQ-ACK codebook before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook.

[0151] In some embodiments, when the payload size of the high priority HARQ-ACK codebook is equal to or less than the preconfigured or predefined payload size, the UE may, based on the preconfigured or predefined The payload size is calculated as the number of resource elements reserved for the high priority HARQ-ACK codebook, where O HP ACK,rvd is the preconfigured or predefined payload size, L HP ACK,rvd is the size of the CRC for a preconfigured or predefined payload size, and the high priority HARQ-ACK codebook is mapped to a subset of the reserved resource elements or all of the reserved resource elements.

[0152] High priority PUSCH without UL-SCH

[0153] In some embodiments, when the high priority PUSCH does not include UL-SCH, the UE may calculate the number of resource elements Q′ used to multiplex the high priority HARQ-ACK codebook according to the following equation: HP ACK : Where R is the code rate of the high priority PUSCH, and Q m is the modulation order of the high priority PUSCH. The UE can determine the remaining number of resource elements available for multiplexing high priority UCI and low priority UCI in the high priority PUSCH as The UE may first map a low-priority HARQ-ACK codebook that is mapped to resource elements not used for mapping a high-priority HARQ-ACK codebook in symbols starting with symbol 1′0, where 1′0 may be preconfigured or predefined (e.g., 1′0 may be the OFDM symbol index of the first OFDM symbol after the first set of consecutive (multiple) OFDM symbols carrying DMRS in the second hop of the high-priority PUSCH). 1′0 may be the same as 10. In some embodiments, before the low-priority HARQ-ACK codebook is punctured by the high-priority HARQ-ACK codebook, when the number of bits of the high-priority HARQ-ACK codebook is 0, 1, or 2 bits, the UE may map the low-priority HARQ-ACK codebook to resource elements reserved for the high-priority HARQ-ACK codebook. The UE may map the high-priority aperiodic CSI to resource elements not used for mapping a high-priority HARQ-ACK codebook and a low-priority HARQ-ACK codebook in symbols starting with symbol 0. Alternatively, the UE may map the low-priority HARQ-ACK codebook after mapping the high-priority aperiodic CSI, where the low-priority HARQ-ACK codebook is mapped to resource elements that are not used for mapping the high-priority HARQ-ACK codebook and the high-priority aperiodic CSI in symbols starting from symbol l′0. The UE may calculate the number of resource elements Q′ used to multiplex the high-priority CSI part 1 according to the following equation: HP CSI-1 : The UE can calculate the number of resource elements used to multiplex the high priority CSI part 1 in the symbols starting from symbol l′0 according to the following equation in is the number of resource elements used to map high priority CSI part 1 in symbol 1. The UE can calculate the number of available resource elements Q′ for multiplexing low priority HARQ-ACK according to the following equation LP ACK ,: In some embodiments, Therefore, if the calculation is (O LP ACK +L LP ACK ) / (N L ·Q′ LP ACK Q m ) is lower than the code rate threshold, the low-priority HARQ-ACK codebook is reused in the high-priority PUSCH. The code rate threshold can be calculated as Note that if the low priority HARQ-ACK codebook is not reused in the high priority PUSCH, the UE can calculate the number of resource elements Q′ used to reuse the high priority CSI part 1 according to the following equation:HP CSI-1 :

[0154] In some embodiments, if a high priority CSI Part 2 is multiplexed in a high priority PUSCH without UL-SCH, the UE may omit that number of CSI Part 2 reports to provide some resource elements for multiplexing a low priority HARQ-ACK codebook. The number of CSI Part 2 reports may be preconfigured or may be determined based on the CSI report priority value specified in clause 5.2.5 of 3GPP TS 38.214. For example, if the CSI Part 2 report is a report with a priority value above a preconfigured or predefined threshold, the UE may omit the CSI Part 2 report when a low priority HARQ-ACK codebook is multiplexed in a high priority PUSCH. When a high priority CSI Part 2 is present, the UE may calculate the number of resource elements Q′ for multiplexing a high priority CSI Part 2 according to the following equation HP CSI-2 : The UE can calculate the number of resource elements used to multiplex the high priority CSI part 2 in the symbols starting from symbol l′0 according to the following equation in is the number of resource elements used to map high priority CSI part 2 in symbol 1. The UE can then calculate the number of available resource elements Q′ for multiplexing low priority HARQ-ACK according to the following equation: LP ACK : In some embodiments, Therefore, if the calculation is (O LP ACK +L LP ACK ) / (N L ·Q′ LP ACK Q m ) is lower than the code rate threshold, the UE can reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH. The code rate threshold can be calculated as Note that if the low priority HARQ-ACK codebook is not reused in the high priority PUSCH, the UE can calculate the number of resource elements Q′ used to reuse the high priority CSI part 2 according to the following equation: HP CSI-2 ,: Note that when the number of bits of the high priority HARQ-ACK codebook is 0, 1, or 2, the UE can calculate the number of reserved resource elements for the high priority HARQ-ACK codebook, and the UE can map CSI part 2 to the reserved resource elements before CSI part 2 is truncated by the high priority HARQ-ACK codebook. In this case, the UE can calculate the number of available resource elements Q' for multiplexing the low priority HARQ-ACK according to the following equation LP ACK : (Assuming that the low priority HARQ-ACK codebook is not mapped to the reserved resource element before it is punctured by the high priority HARQ-ACK codebook), where is the number of reserved resource elements for the high priority HARQ-ACK codebook in symbols starting at l′0. In some embodiments, Alternatively, if the UE maps the low priority HARQ-ACK codebook to the reserved resource elements before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook, the term in the preceding equation is not required. Therefore, if the calculation is (O LP ACK +L LP ACK ) / (N L ·Q′ LP ACK Q m ) is lower than the code rate threshold, the UE can reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH. The code rate threshold can be calculated as If the low priority HARQ-ACK codebook is not reused in the high priority PUSCH, the UE may not omit CSI Part 2 reports with priority values ​​higher than the preconfigured or predefined priority value. It should be noted that the UE may omit some CSI Part 2 reports specified in 3GPP TS 38.214. In some embodiments, the UE may omit CSI Part 2 reports in descending order of priority value from the CSI Part 2 report with the highest priority value until the number of resource elements available for reuse of the low priority HARQ-ACK codebook results in a code rate lower than (0 LP ACK +L LP ACK ) / (N L ·Q′ LP ACK Q m ).

[0155] In some embodiments, when the number of resource elements available for multiplexing the low priority HARQ-ACK codebook results in a code rate lower than (0 LP ACK +L LP ACK ) / (N L ·Q′LP ACK Q m ), the UE may compress the low-priority HARQ-ACK codebook according to the method for HARQ-ACK codebook compression described below.

[0156] In some embodiments, when the number of resource elements available for multiplexing the low priority HARQ-ACK codebook results in a code rate lower than (0 LP ACK +L LP ACK ) / (N L ·Q′ LP ACK Q m ), the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the dynamically scheduled PDSCH reception. Alternatively, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the SPS PDSCH reception.

[0157] In some embodiments, before the high priority CSI part 1 is punctured by the high priority HARQ-ACK codebook, the UE may map the high priority CSI part 1 to resource elements reserved for the high priority HARQ-ACK codebook.

[0158] In some implementations, the UE may map the low priority HARQ-ACK codebook to resource elements reserved for the high priority HARQ-ACK codebook before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook.

[0159] In some embodiments, when the payload size of the high priority HARQ-ACK codebook is equal to or less than the preconfigured or predefined payload size, the UE may calculate the number of resource elements reserved for the high priority HARQ-ACK codebook according to the following equation: Among them O HP ACK,rvd is the preconfigured or predefined payload size, L HP ACK,rvd is the size of the CRC for a preconfigured or predefined payload size, and the high priority HARQ-ACK codebook is mapped to a subset of the reserved resource elements or all of the reserved resource elements.

[0160] In some embodiments, when the high priority PUSCH is a CG PUSCH with CG-UCI, if the high priority HARQ-ACK code base is multiplexed in the high priority PUSCH, the UE may append the CG UCI to the high priority HARQ-ACK code base. HP ACKIt can be the total payload size of the CG-UCI and the high priority HARQ-ACK codebook. If no high priority HARQ-ACK codebook is multiplexed in the high priority PUSCH, the UE can determine the CG-UCI as the high priority HARQ-ACK codebook, and HP ACK It can be the total payload size of CG-UCI.

[0161] When the UE multiplexes the low-priority HARQ-ACK codebook in the high-priority PUSCH, the following method can be used to compress the size of the low-priority HARQ-ACK codebook.

[0162] Method 9: When the UE multiplexes the low-priority HARQ-ACK codebook in the high-priority PUSCH, the spatial bundling parameters and CBG parameters can be separately configured for the low-priority HARQ-ACK codebook, and when the UE multiplexes the low-priority HARQ-ACK codebook in the low-priority PUSCH, the spatial bundling parameters and CBG parameters can be separately configured for the low-priority HARQ-ACK codebook.

[0163] In some embodiments, HARQ-ACK-SpatialBundlingHPPUSCH can be configured in PhysicalCellGroupConfig to instruct the UE to perform spatial bundling of low-priority HARQ-ACK codebooks when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, and HARQ-ACK-SpatialBundlingPUSCH can be configured in PhysicalCellGroupConfig to instruct the UE to perform spatial bundling of low-priority HARQ-ACK codebooks when the low-priority HARQ-ACK codebook is multiplexed in the low-priority PUSCH. In some embodiments, when HARQ-ACK-SpatialBundlingPUSCH is configured, the UE can perform spatial bundling of low-priority HARQ-ACK codebooks when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH.

[0164] In some embodiments, harq-ACK-TBHPPUSCH can be configured in PhysicalCellGroupConfig or PUSCH-Config to instruct the UE to compress the CBG-based HARQ-ACK codebook. In some embodiments, if the low-priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, the UE only transmits the HARQ-ACK bits for the TB in the PDSCH corresponding to the low-priority HARQ-ACK codebook. In some embodiments, if the low-priority HARQ-ACK codebook is a type 2 HARQ-ACK codebook, when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, the UE only transmits the TB-based sub-codebook of the low-priority HARQ-ACK codebook. In some embodiments, if the low priority HARQ-ACK codebook is a type 2 HARQ-ACK codebook, when the low priority HARQ-ACK codebook is multiplexed in the high priority PUSCH, the UE transmits the TB-based word codebook of the low priority HARQ-ACK codebook and the HARQ-ACK bits of the TB in the PDSCH corresponding to the CBG-based subcodebook of the low priority HARQ-ACK codebook.

[0165] The following method may be used to multiplex the UCI(s) of a high priority PUCCH in a low priority PUSCH.

[0166] Method 10: When a high-priority PUCCH overlaps with a low-priority PUSCH in the time domain, the UE may multiplex the UCI of the high-priority PUCCH in the low-priority PUSCH when one or more of the following conditions are met:

[0167] Condition 1: For high-priority PUCCH and low-priority PUSCH, the timeline requirements for UCI multiplexing are met.

[0168] Condition 2: A-CSI is not triggered for multiplexing in the low-priority PUSCH.

[0169] Condition 3: The low-priority CSI part 2 is not multiplexed in the high-priority PUSCH.

[0170] Condition 4: The low-priority PUSCH is included in the same subslot as the high-priority PUCCH.

[0171] Condition 5: PUSCH repetition is not used to configure or schedule low-priority PUSCHs.

[0172] Condition 6: High-priority PUCCH is scheduled by DCI format.

[0173] Condition 7: The low-priority PUSCH is not a CG PUSCH.

[0174] Condition 8: The low-priority PUSCH only contains the front-end loaded DMRS.

[0175] Condition 9: PUCCH does not contain HARQ-ACK information. For example, only high-priority CSI is allowed to be multiplexed in low-priority PUSCH.

[0176] Condition 10: The HARQ-ACK codebook in the high-priority PUCCH is a type 1 HARQ-ACK codebook.

[0177] Condition 11 indicates that the UE has the capability to multiplex high-priority UCI in low-priority PUSCH.

[0178] Condition 12: The gNB configures the UE to multiplex high-priority UCI in the low-priority PUSCH.

[0179] Condition 13: When a dynamic beta offset is configured for high priority UCI, an explicit indication of the beta offset for the high priority UCI is included in the UL grant that schedules the low priority PUSCH.

[0180] Condition 14: UL grant indication for scheduling low-priority PUSCH High-priority UCI may be multiplexed in the low-priority PUSCH.

[0181] Condition 15: The modulation order of the low-priority PUSCH is not greater than a threshold. The threshold can be pre-configured or determined based on the MCS table configuration. For example, if 'qam64LowSE' is configured for DCI format 0_2, the threshold can be determined to be '6'.

[0182] Condition 16: The number of resource elements in the low-priority PUSCH that can be used to multiplex high-priority UCI bits (e.g. ), resulting in the code rate of one or more high-priority UCIs being higher than the threshold, where The beta offset is the scaling factor for high-priority UCI when it is multiplexed in a low-priority PUSCH. When high-priority UCI is multiplexed in a low-priority PUSCH, the threshold can be determined based on the preconfigured scaling factor and / or beta offset for the high-priority UCI. The beta offset can be indicated via the UL grant that schedules the low-priority PUSCH.

[0183] Condition 17: The UE may reuse a high-priority HARQ-ACK codebook in a low-priority PUSCH when one or more of the following conditions are met:

[0184] Condition 17a: The size of the low-priority HARQ-ACK codebook is not greater than the number of bits. For example, the number of bits can be preconfigured. The number of bits can be 2.

[0185] Condition 17b: The high-priority HARQ-ACK codebook includes only TB-based sub-codebooks.

[0186] Condition 17c: No PDSCH-CodeBlockGroupTransmission is provided for the high-priority HARQ-ACK codebook.

[0187] Condition 17d: The UL grant for scheduling the low-priority PUSCH includes the UL total DAI field of the high-priority HARQ-ACK codebook.

[0188] Condition 17e: The high priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, the UL grant for scheduling the low priority PUSCH includes the UL total DAI field of the high priority HARQ-ACK codebook, and the DAI value indicates

[0189] Condition 18: The UE may multiplex high-priority CSI in low-priority PUSCH when one or more of the following conditions are met:

[0190] Condition 18a: High-priority CSI includes only CSI part 1.

[0191] Condition 18b: The size of the high-priority CSI is not greater than the preconfigured number of bits.

[0192] Condition 18c: The high-priority HARQ-ACK codebook is not multiplexed in the high-priority PUCCH (if the low-priority PUSCH does not exist).

[0193] When a high-priority PUCCH is not multiplexed in a low-priority PUSCH, the high-priority PUCCH is prioritized for transmission.

[0194] Method 11: When a high-priority PUCCH including a high-priority HARQ-ACK codebook overlaps with a low-priority PUSCH in the time domain, the UL total DAI field of the high-priority HARQ-ACK codebook may be included in the UL grant scheduling the low-priority PUSCH, and the UE may use the UL total DAI value to determine the size of the high-priority HARQ-ACK codebook to be used for multiplexing in the low-priority PUSCH.

[0195] In some embodiments, the UE may determine whether the UL total DAI field of the high priority HARQ-ACK codebook is included in the UL grant for scheduling the low priority PUSCH based on the IE (e.g., TotalDAIforLPUCIonHPPUSCH in PhysicalCellGroupConfig or PUSCH-Config). In some embodiments, if the high priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, the number of bits is 1, and if the high priority HARQ-ACK codebook is a type 2 HARQ, the number of bits is 2 for the TB-based word codebook, and the number of bits is 2 for the CBG-based sub-codebook (if PDSCH-CodeBlockGroupTransmission is configured for the high priority HARQ-ACK codebook). In some embodiments, the UL total DAI field of the CBG-based sub-codebook is not included in the UL grant. In some embodiments, when the DAI value 0 indicates that the UE does not multiplex the high priority HARQ-ACK (sub) codebook in the low priority PUSCH, the number of bits of the UL total DAI field per subcodebook may be 1 bit, and the DAI value 1 indicates that the UE multiplexes the high priority HARQ-ACK (sub) codebook in the low priority PUSCH.

[0196] In some embodiments, when the UL total DAI field of the high priority HARQ-ACK codebook is not included in the UL grant for scheduling the low priority PUSCH, when the high priority HARQ-ACK codebook is multiplexed in the low priority PUSCH and the low priority HARQ-ACK codebook is not multiplexed in the low priority HARCH, the UE may determine the UL total DAI value of the high priority HARQ-ACK codebook based on the UL total DAI field of the low priority HARQ-ACK codebook. In some embodiments, the UE may determine the UL total DAI value of the high priority HARQ-ACK codebook based on the UL total DAI field of the low priority HARQ-ACK codebook, regardless of whether the low priority HARQ-ACK codebook is multiplexed in the low priority PUSCH.

[0197] In some embodiments, when the UL total DAI field of the subcodebook based on the high priority HARQ-ACK CBG is not included in the UL grant for scheduling the low priority PUSCH, the UE may determine the UL total DAI value of the subcodebook based on the high priority HARQ-ACK CBG based on the UL total DAI field of the subcodebook based on the low priority HARQ-ACK CBG, regardless of whether the subcodebook based on the low priority HARQ-ACK CBG is multiplexed in the low priority PUSCH.

[0198] The following method may be used to determine the number of available resource elements for multiplexing high-priority UCI in a low-priority PUSCH and a threshold value of the number of available resource elements.

[0199] Method 12: When the high-priority PUCCH and the low-priority PUCCH overlap with the low-priority PUSCH, and when the UCI of the low-priority PUCCH is multiplexed in the low-priority PUSCH (e.g., and ), the UE may perform rate matching on the UCI of the low priority PUCCH to be multiplexed in the low priority PUSCH based on the beta offset and scaling factor of the low priority UCI. For example, the UE may calculate the number of resource elements Q′ for multiplexing the low priority HARQ-ACK codebook according to the following equation: LP ACK :

[0200] Among them O LP ACK is the payload size of the low priority HARQ-ACK codebook, and L LP ACK is the size of the CRC of the low priority HARQ-ACK codebook, and C UL-SCH and K r Defined in 3GPP TS 38.212 V16.3.0, and l′0 may be preconfigured or predefined (e.g., l′0 may be the OFDM symbol index of the first OFDM symbol after the first set of consecutive (multiple) OFDM symbols carrying DMRS in the second hop of the low-priority PUSCH). l′0 may be the same as l0, where l0 is the OFDM symbol index of the first OFDM symbol after the first set of consecutive (multiple) OFDM symbols carrying DMRS). The remaining number of resource elements available for multiplexing high-priority UCI and low-priority UCI in the low-priority PUSCH may be determined as If no low-priority CSI is multiplexed in the low-priority PUSCH, but the high-priority HARQ-ACK codebook is multiplexed in the low-priority PUSCH, the UE may map the high-priority HARQ-ACK codebook to resource elements that are not used to map the low-priority HARQ-ACK codebook in symbols starting with symbol 10. In some embodiments, the UE may first map the high-priority HARQ-ACK codebook in symbols starting with symbol 10 before mapping the low-priority HARQ-ACK codebook. The UE may determine whether to multiplex the high-priority HARQ-ACK codebook in the low-priority PUSCH based on the minimum number of resource elements, which is calculated according to the following equation: In some embodiments, Then, if Q′ HP ACK,min Greater than Then the UE does not reuse the high priority HARQ-ACK codebook in the low priority PUSCH. In some embodiments, if Q′ HP ACK,min Greater than Then the UE does not reuse the low-priority HARQ-ACK codebook in the high-priority PUSCH. Otherwise, the UE reuses the high-priority HARQ-ACK codebook in the low-priority PUSCH, but does not reuse the low-priority HARQ-ACK codebook in the low-priority PUSCH. Alternatively, when the high-priority HARQ-ACK codebook is reused in the low-priority PUSCH, the UE can calculate the number of resource elements Q' used to reuse the low-priority HARQ-ACK codebook according to the following equation LP ACK :

[0201] In some embodiments, when the number of bits of the high priority HARQ-ACK codebook is less than or equal to the predefined or preconfigured number of bits (e.g., 2 bits), multiple (RE rvd,HP ) resource elements, Among them O HP ACK,rvd is a preconfigured or predefined payload size and L HP ACK,rvd is the size of the CRC for the preconfigured or predefined payload size, and the high priority HARQ-ACK codebook is mapped to a subset or all of the reserved resource elements. On the other hand, if the low priority CSI is multiplexed in the low priority PUSCH, the UE can calculate the number of resource elements Q′ used to multiplex the low priority CSI part 1 according to the following equation LP CSI-1 ,: If Q′ HP ACK,min Greater than Then the UE does not reuse the high priority HARQ-ACK codebook in the low priority PUSCH. In some embodiments, the UE may omit this number of CSI Part 1 reports until Q′ HP ACK,min Greater than More specifically, the UE omits CSI Part 1 reports in descending order of priority value. In other words, if necessary, the UE omits the CSI Part 1 report with the highest priority value first. In some embodiments, if Q′HP ACK,min Less than or equal to The UE may omit the low priority CSI part 1 and reuse the high priority HARQ-ACK codebook in the low priority PUCCH. HP ACK,min Less than or equal to The UE may then omit the low priority HARQ-ACK codebook and the low priority CSI part 1 and multiplex the high priority HARQ-ACK in the low priority PUSCH. In some embodiments, when the number of bits of the high priority HARQ-ACK codebook is less than or equal to the predefined or preconfigured number of bits (e.g., 2 bits), the UE may reserve that number of resource elements for the high priority HARQ-ACK codebook, and the UE may map the low priority CSI part 1 to the reserved resource elements before it is punctured by the high priority HARQ-ACK codebook.

[0202] In some embodiments, if a low priority CSI Part 2 is multiplexed in a low priority PUSCH, the UE may omit that number of CSI Part 2 reports to provide some resource elements for multiplexing a high priority HARQ-ACK codebook. The number of CSI Part 2 reports may be preconfigured or may be determined based on a CSI report priority value as specified in clause 5.2.5 of 3GPP TS 38.214. For example, if a CSI Part 2 report is a report with a priority value above a preconfigured or predefined threshold, the UE may omit the CSI Part 2 report when a high priority HARQ-ACK codebook is multiplexed in a low priority PUSCH. When a low priority CSI Part 2 is present, the UE may calculate the number of resource elements Q′ for multiplexing a low priority CSI Part 2 according to the following equation LP CSI-2 : If Q′ HP ACK,min Greater than Then the UE does not reuse the high priority HARQ-ACK codebook in the low priority PUSCH. In some embodiments, the UE may omit CSI Part 2 reports from the CSI Part 2 report with the highest priority value in descending order of priority value until the number of resource elements available for reusing the high priority HARQ-ACK codebook is equal to or greater than Q′ HP ACK,min In some embodiments, if Q′ HP ACK,min Less than or equal to Then the UE may omit the low priority CSI Part 2 and reuse the high priority HARQ-ACK codebook in the low priority PUSCH. In some embodiments, the UE may omit the number of CSI Part 1 reports until Q′ HP ACK,min Greater than More specifically, the UE omits CSI Part 1 reports in descending order of priority value. In other words, if necessary, the UE omits the CSI Part 1 report with the highest priority value first. In one embodiment, if Q′ HP ACK,min Less than or equal to Then the UE may omit the low priority CSI part 1 and reuse the high priority HARQ-ACK codebook in the low priority PUSCH. In some embodiments, if Q′ HP ACK,min Less than or equal to The UE may then omit the low priority HARQ-ACK codebook and the low priority CSI part 1 and multiplex the high priority HARQ-ACK in the low priority PUSCH.

[0203] In some embodiments, when the number of resource elements is insufficient to multiplex a high-priority HARQ-ACK codebook, the UE may compress the low-priority HARQ-ACK codebook according to the method for HARQ-ACK codebook compression described below.

[0204] In some embodiments, when the number of resource elements is insufficient to reuse the high-priority HARQ-ACK codebook, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the dynamically scheduled PDSCH reception. Alternatively, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the SPS PDSCH reception.

[0205] Note that in the above embodiment, the UE first calculates the number of resource elements required to map the low-priority UCI, and then checks the remaining number of resource elements to determine whether to reuse the high-priority HARQ-ACK codebook. In some embodiments, the UE first calculates the number of resource elements required to map the high-priority HARQ-ACK codebook, and then checks the remaining number of resource elements to determine whether to reuse the low-priority UCI.

[0206] It should be noted that when it is determined not to reuse the high-priority HARQ-ACK codebook in the low-priority PUSCH, the high-priority PUCCH carrying the high-priority HARQ-ACK codebook is preferentially processed for transmission.

[0207] Low priority PUSCH without UL-SCH

[0208] In some embodiments, when the low priority PUSCH does not include UL-SCH, the UE may calculate the number of resource elements Q′ used to multiplex the low priority HARQ-ACK codebook according to the following equation: LP ACK :

[0209] Where R is the code rate of the high priority PUSCH, Q m is the modulation order of the high priority PUSCH, and l′0 may be preconfigured or predefined (e.g., l′0 may be the OFDM symbol index of the first OFDM symbol after the first group of consecutive (multiple) OFDM symbols carrying DMRS in the second hop of the low priority PUSCH). l′0 may be the same as l0, where l0 is the OFDM symbol index of the first OFDM symbol after the first group of consecutive (multiple) OFDM symbols carrying DMRS). The UE may map the high priority HARQ-ACK codebook to resource elements that are not used for mapping the low priority HARQ-ACK codebook in symbols starting with symbol l0. In some embodiments, the UE may first map the high priority HARQ-ACK codebook in symbols starting with symbol l0 before mapping the low priority HARQ-ACK codebook. The UE may map the low priority non-periodic CSI to resource elements that are not used for mapping the high priority HARQ-ACK codebook and the low priority HARQ-ACK codebook in symbols starting with symbol 0. The UE may calculate the number of resource elements Q′ used for multiplexing the low priority CSI part 1 according to the following equation LP CSI-1 : The remaining number of resource elements available for multiplexing high priority UCI and low priority UCI in the low priority PUSCH may be determined as The UE can then calculate the number of available resource elements Q′ for multiplexing the high priority HARQ-ACK codebook according to the following equation: HP ACK : In some embodiments, Therefore, if the calculation is (O HP ACK +L HP ACK ) / (N L ·Q′ HP ACK Q m ) is lower than the code rate threshold, the UE can reuse the high-priority HARQ-ACK codebook in the low-priority PUSCH. The code rate threshold can be calculated as In some embodiments, or And if the high priority HARQ-ACK codebook is multiplexed in the low priority PUSCH, the UE can calculate the number of resource elements Q′ used to multiplex the low priority CSI part 1 according to the following equation LP CSI-1 : Then the number of CSI Part 1 reports is omitted in descending order of priority value until it is calculated as (OLP CSI-1 +L LP CSI-1 ) / (N L ·Q′ LP CSI-1 Q m ) has a lower bit rate than In some embodiments, And if the high priority HARQ-ACK codebook is multiplexed in the low priority PUSCH, the UE can calculate the number of resource elements Q′ available for multiplexing the low priority CSI part 1 according to the following equation LP CSI-1 : The UE may omit the low priority HARQ-ACK codebook and may omit the number of CSI Part 1 reports in descending order of priority value until the value is calculated as (0 LP CSI-1 +L LP CSI-1 ) / (N L ·Q′ LP CSI-1 Q m ) has a lower bit rate than In some embodiments, when the number of bits of the high priority HARQ-ACK codebook is less than or equal to the predefined or preconfigured number of bits (e.g., 2 bits), multiple resource elements RE may be reserved for the high priority HARQ-ACK codebook. rvd,HP , Among them O HP ACK,rvd is a preconfigured or predefined payload size and L HP ACK,rvd is the size of the CRC for the preconfigured or predefined payload size, and the high priority HARQ-ACK codebook is mapped to a subset of the reserved resource elements or all of the reserved resource elements. In some embodiments, the UE may map the low priority HARQ-ACK codebook to the resource elements reserved for the high priority HARQ-ACK codebook before the low priority HARQ-ACK codebook is punctured by the high priority HARQ-ACK codebook. In this case, Q′ for multiplexing the high priority HARQ-ACK codebook in the aforementioned equation is LP ACK Can be subtracted in is the number of reserved resource elements for the high priority HARQ-ACK codebook in symbols starting at l′0. In some embodiments, when the number of bits of the high priority HARQ-ACK codebook is less than or equal to a predefined or preconfigured number of bits (e.g., 2 bits), the UE may reserve the number of resource elements for the high priority HARQ-ACK codebook and map the low priority CSI part 1 to the reserved resource elements before the low priority CSI part 1 is punctured by the high priority HARQ-ACK codebook.

[0210] In some embodiments, if a low priority CSI Part 2 is multiplexed in a low priority PUSCH, the UE may omit that number of CSI Part 2 reports to provide some resource elements for multiplexing a high priority HARQ-ACK codebook. The number of CSI Part 2 reports may be preconfigured or may be determined based on the CSI report priority value specified in clause 5.2.5 of 3GPP TS 38.214. For example, if the CSI Part 2 report is a report with a priority value above a preconfigured or predefined threshold, the UE may omit the CSI Part 2 report when a high priority HARQ-ACK codebook is multiplexed in a low priority PUSCH. When a low priority CSI Part 2 is present, the UE may calculate the number of resource elements Q′ for multiplexing a low priority CSI Part 2 according to the following equation LP CSI-2 : The UE can then calculate the number of available resource elements Q′ for multiplexing the high priority HARQ-ACK codebook according to the following equation: HP ACK : In some embodiments, Therefore, if the calculation is (O HP ACK +L HP ACK ) / (N L ·Q′ HP ACK Q m ) is lower than the code rate threshold, the UE can reuse the high-priority HARQ-ACK codebook in the low-priority PUSCH. The code rate threshold can be calculated as In some embodiments, or And if the high priority HARQ-ACK codebook is multiplexed in the low priority PUSCH, the UE can calculate the number of resource elements Q′ used to multiplex the low priority CSI part 2 according to the following equation LP CSI-2 : Then the number of CSI Part 2 reports is omitted in descending order of priority value until it is calculated as (0 LP CSI-2 +L LP CSI-2 ) / (N L ·Q′ LP CSI-2 Q m ) has a lower bit rate than In some embodiments, or And if the high priority HARQ-ACK codebook is multiplexed in the low priority PUSCH, the UE can calculate the number of resource elements Q′ used to multiplex the low priority CSI part 1 according to the following equation LP CSI-1 : Then the number of CSI Part 1 reports is omitted in descending order of priority value until it is calculated as (O LP CSI-1 +L LP CSI-1 ) / (N L ·Q′ LP CSI-1 Q m ) has a lower bit rate than In some embodiments, And if the high priority HARQ-ACK codebook is multiplexed in the low priority PUSCH, the UE can calculate the number of resource elements Q′ available for multiplexing the low priority CSI part 1 according to the following equation LP CSI-1 : Then omit the low priority HARQ-ACK codebooks and omit that number of CSI Part 1 reports in descending order of priority value until it is calculated as (0 LP CSI-1 +L LP CSI-1 ) / (N L ·Q′ LP CSI-1 Q m ) has a lower bit rate than

[0211] In some embodiments, when the number of resource elements available for multiplexing the high priority HARQ-ACK codebook results in a code rate lower than (0 HP ACK +L HP ACK ) / (N L ·Q′ HP ACK Q m ), the UE may compress the low-priority HARQ-ACK codebook according to the method for HARQ-ACK codebook compression described below.

[0212] In some embodiments, when the number of resource elements available for multiplexing the high priority HARQ-ACK codebook results in a code rate lower than (0 HP ACK +L HP ACK ) / (N L ·Q′ HP ACK Q m ), the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the dynamically scheduled PDSCH reception. Alternatively, the UE may omit the HARQ-ACK bits in the low-priority HARQ-ACK codebook corresponding to the SPS PDSCH reception.

[0213] Note that in the above embodiment, the UE first calculates the number of resource elements required to map the low-priority UCI, and then checks the remaining number of resource elements to determine whether to reuse the high-priority HARQ-ACK codebook. In some embodiments, the UE first calculates the number of resource elements required to map the high-priority HARQ-ACK codebook, and then checks the remaining number of resource elements to determine whether to reuse the low-priority UCI.

[0214] It should be noted that when the UE determines not to reuse the high-priority HARQ-ACK codebook in the low-priority PUSCH, the UE may prioritize the high-priority PUCCH carrying the high-priority HARQ-ACK codebook for transmission.

[0215] In some embodiments, when the low priority PUSCH is a CG PUSCH with CG-UCI, if the low priority HARQ-ACK code base is multiplexed in the low priority PUSCH, the UE may append the CG UCI to the low priority HARQ-ACK code base. LP ACK It can be the total payload size of the CG-UCI and the low priority HARQ-ACK codebook. When the UE determines not to multiplex the CG-UCI and the low priority HARQ-ACK codebook in the low priority PUSCH, the UE does not transmit the low priority PUSCH. If no low priority HARQ-ACK codebook is multiplexed in the low priority PUSCH, the UE can determine the CG-UCI as the low priority HARQ-ACK codebook, and LP ACK It can be the total payload size of the CG-UCI. When the UE determines not to multiplex the CG-UCI in the low-priority PUSCH, the UE may not transmit the low-priority PUSCH. In some embodiments, when no low-priority HARQ-ACK code base is multiplexed in the low-priority PUSCH and the high-priority HARQ-ACK code base is multiplexed in the low-priority PUSCH, the UE may append the CG UCI to the high-priority HARQ-ACK code base. In this case, HP ACK It can be the total payload size of CG-UCI and high priority HARQ-ACK codebook.

[0216] When the low-priority HARQ-ACK codebook is multiplexed in the low-priority PUSCH, the following method can be used to compress the size of the low-priority HARQ-ACK codebook.

[0217] Method 13: When the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, the spatial bundling parameters and CBG parameters can be configured separately for the low-priority HARQ-ACK codebook, and when the low-priority HARQ-ACK codebook is multiplexed in the low-priority PUSCH, the spatial bundling parameters and CBG parameters can be configured separately for the low-priority HARQ-ACK codebook.

[0218] In some embodiments, HARQ-ACK-SpatialBundlingHPPUSCH can be configured in PhysicalCellGroupConfig to instruct the UE to perform spatial bundling of low-priority HARQ-ACK codebooks when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, and HARQ-ACK-SpatialBundlingPUSCH can be configured in PhysicalCellGroupConfig to instruct the UE to perform spatial bundling of low-priority HARQ-ACK codebooks when the low-priority HARQ-ACK codebook is multiplexed in the low-priority PUSCH. In some embodiments, when HARQ-ACK-SpatialBundlingPUSCH is configured, the UE can perform spatial bundling of low-priority HARQ-ACK codebooks when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH.

[0219] In some embodiments, harq-ACK-TBHPPUSCH can be configured in PhysicalCellGroupConfig or PUSCH-Config to instruct the UE to compress the CBG-based HARQ-ACK codebook. In some embodiments, if the low-priority HARQ-ACK codebook is a type 1 HARQ-ACK codebook, when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, the UE only transmits the HARQ-ACK bits for the TB in the PDSCH corresponding to the low-priority HARQ-ACK codebook. In some embodiments, if the low-priority HARQ-ACK codebook is a type 2 HARQ-ACK codebook, when the low-priority HARQ-ACK codebook is multiplexed in the high-priority PUSCH, the UE only transmits the TB-based sub-codebook of the low-priority HARQ-ACK codebook. In some embodiments, if the low priority HARQ-ACK codebook is a type 2 HARQ-ACK codebook, when the low priority HARQ-ACK codebook is multiplexed in the high priority PUSCH, the UE transmits the TB-based word codebook of the low priority HARQ-ACK codebook and the HARQ-ACK bits of the TB in the PDSCH corresponding to the CBG-based subcodebook of the low priority HARQ-ACK codebook.

[0220] In some embodiments, when the low priority HARQ-ACK codebook is multiplexed in the low priority PUSCH in which the high priority UCI is multiplexed, the parameters applicable to the low priority HARQ-ACK codebook when the low priority HARQ-ACK codebook is multiplexed in the high priority PUSCH (e.g., HARQ-ACK-SpatialBundlingHPPUSCH and HARQ-ACK-TBHPPUSCH) may also be applied by the UE.

[0221] Figure 5 5 is a flowchart illustrating a method 500 for transmitting a PUCCH according to an embodiment of the present disclosure. In action 502, the UE receives a first RRC configuration including a first PUCCH resource configuration and a second PUCCH resource configuration. In action 504, the UE receives a first DCI format for scheduling a first PDSCH and a second DCI format for scheduling a second PDSCH. In action 506, the UE determines a first PUCCH for a first HARQ-ACK codebook corresponding to the first PDSCH based on the first PUCCH resource configuration, and determines a second PUCCH for a second HARQ-ACK codebook corresponding to the second PDSCH based on the second PUCCH resource configuration. In action 508, when the first PUCCH overlaps with the second PUCCH in the time domain, the UE transmits the first PUCCH, and the first HARQ-ACK codebook and the second HARQ-ACK codebook are multiplexed in the first PUCCH. In action 510, the UE determines the total number of resource elements of the first PUCCH (e.g., E tot,HP ) and a payload size based on the first HARQ-ACK codebook (e.g., HP ACK ), the size of the CRC used for the first HARQ-ACK codebook (e.g., L HP UCI ) and a first maximum coding rate corresponding to the first PUCCH resource configuration (e.g., r HP ), determine the first number of resource elements for the first HARQ-ACK codebook in the first PUCCH (e.g., E HP UCI In action 512, the UE determines a third number of resource elements (e.g., E ) for the second HARQ-ACK codebook in the first PUCCH based on a difference between the total number of resource elements in the first PUCCH and the first number of resource elements in the first HARQ-ACK codebook. tot,HP -E HP UCI ).

[0222] In some examples, the first number of resource elements for the first HARQ-ACK codebook is the total number of resource elements of the first PUCCH and the payload size (e.g., 0) of the scheduling request based on the first priority indicated by the first DCI format. HP SR ), a minimum value of a second number of resource elements determined by at least one of a payload size of the first HARQ-ACK codebook, a size of a CRC for the scheduling request, a size of a CRC for the first HARQ-ACK codebook, and a first maximum code rate.

[0223] In some examples, a UE may receive a second RRC configuration including a first set of offset values ​​(e.g., beta offsets) and a second set of offset values ​​(e.g., beta offsets), and receive a third DCI format that schedules a first PUSCH of a first priority, the first priority being indicated by the third DCI format. When the first PUSCH overlaps with the first PUCCH in the time domain, the UE may transmit the first PUSCH but not the first PUCCH, wherein the first HARQ-ACK codebook and the second HARQ-ACK codebook are multiplexed in the first PUSCH. The UE determines a fourth number of resource elements for the first HARQ-ACK codebook in the first PUSCH based on the first set of offset values ​​and a first value of a field in the third DCI format (e.g., a beta_offset indicator), wherein the first value is used to indicate an offset value of the first set of offset values, and the UE determines a fifth number of resource elements for the second HARQ-ACK codebook in the first PUSCH based on the second set of offset values ​​and a second value of the field in the third DCI format, wherein the second value is used to indicate an offset value of the second set of offset values.

[0224] In some examples, a UE may receive a second RRC configuration including a third set of offset values ​​and a fourth set of offset values, and receive a fourth DCI format, the fourth DCI format scheduling a second PUSCH of a second priority indicated by the fourth DCI format. When the second PUSCH overlaps with the first PUCCH in the time domain and the first PUSCH does not overlap with the first PUCCH and the second PUSCH in the time domain, the UE may transmit the second PUSCH but not the first PUCCH, wherein the first HARQ-ACK codebook and the second HARQ-ACK codebook are multiplexed in the second PUSCH. The UE determines a sixth number of resource elements for the first HARQ-ACK codebook in the second PUSCH based on the third set of offset values ​​and a third value of a field in the fourth DCI format, wherein the third value is used to indicate an offset value of the third set of offset values, and the UE determines a seventh number of resource elements for the second HARQ-ACK codebook in the second PUSCH based on the fourth set of offset values ​​and a fourth value of the field in the fourth DCI format, wherein the fourth value is used to indicate an offset value of the fourth set of offset values.

[0225] In some examples, the UE may select a maximum coding rate based on the payload size of the first HARQ-ACK codebook, the payload size of the second HARQ-ACK codebook, the first maximum coding rate, and the second maximum coding rate corresponding to the second PUCCH resource configuration (e.g., r LP ) to determine at least one of the PRBs of the first PUCCH.

[0226] Figure 6 is a block diagram illustrating a node 600 for wireless communication according to an embodiment of the present disclosure.

[0227] like Figure 6 As shown, the node 600 may include a transceiver 620, a processor 626, a memory 628, one or more presentation components 634, and at least one antenna 636. The node 600 may also include a radio frequency (RF) band module, a BS communication module, a network communication module, a system communication management module, an input / output (I / O) port, an I / O component, and a power supply ( Figure 6 not shown).

[0228] Each of the components may communicate with each other directly or indirectly via one or more buses 640. Figure 5 The various disclosed functions shown in FIG. 1 and the UE or BS of the examples / implementations in the present disclosure.

[0229] The transceiver 620 may include a transmitter 622 (having a transmit circuit) and a receiver 624 (having a receive circuit), and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 620 may be configured to transmit in different types of subframes and time slots, including but not limited to available, unavailable, and flexibly usable subframe and time slot formats. The transceiver 620 may be configured to receive data and control channels.

[0230] Node 600 may include a variety of computer-readable media. Computer-readable media may be any media accessible by node 600 and include volatile (and non-volatile) media and removable (and non-removable) media. Computer-readable media may include computer storage media and communication media. Computer storage media may include volatile (and / or non-volatile) and removable (and / or non-removable) media implemented according to any method or technology for storing information such as computer-readable media.

[0231] Computer storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVDs) (or other optical disk storage devices), magnetic cassettes, magnetic tape, magnetic disk storage devices (or other magnetic storage devices), etc. Computer storage media do not include propagated data signals.

[0232] Communication media generally may be embodied as computer-readable instructions, data structures, program modules, or other data in a modulated data signal (such as a carrier wave or other transport mechanism), and includes any information delivery media. The term "modulated data signal" may refer to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media (such as a wired network or direct-wired connection) and wireless media (such as acoustic, RF, infrared, and other wireless media). Any combination of the above media should be included within the scope of computer-readable media.

[0233] The memory 628 may include computer storage media in the form of volatile and / or non-volatile memory. The memory 628 may be removable, non-removable, or a combination thereof. For example, the memory 628 may include solid-state memory, a hard drive, an optical drive, etc. Figure 6 As shown, the memory 628 may store computer-readable and / or computer-executable instructions 632 (e.g., software code) that, when executed, are configured to cause the processor 626 (e.g., processing circuitry) to perform various disclosed functions. Alternatively, the instructions 632 may not be directly executed by the processor 626, but may be configured to cause the node 600 (e.g., when compiled and executed) to perform various disclosed functions.

[0234] Processor 626 may include an intelligent hardware device, a central processing unit (CPU), a microcontroller, an ASIC, etc. Processor 626 may include memory. Processor 626 may process data 630 and instructions 632 received from memory 628, as well as information received via transceiver 620, a baseband communication module, and / or a network communication module. Processor 626 may also process information to be sent to transceiver 620 for transmission via antenna 636 and / or to the network communication module for transmission to the CN.

[0235] One or more presentation components 634 can present data to a person or other device. Examples of presentation components 634 can include a display device, a speaker, a printout, a vibration element, and the like.

[0236] In light of this disclosure, it will be apparent that various techniques may be utilized to implement the disclosed concepts without departing from the scope of these concepts. Furthermore, while these concepts have been disclosed with specific reference to particular embodiments, those skilled in the art will recognize that variations in form and detail may be made without departing from the scope of these concepts. Thus, this disclosure is to be considered in all respects as illustrative and not restrictive. It will also be understood that this disclosure is not limited to the specific disclosed embodiments, and that numerous rearrangements, modifications, and substitutions of these embodiments are possible without departing from the scope of this disclosure.

Claims

1. A method for transmitting a physical uplink control channel (PUCCH) performed by a user equipment (UE), the method comprising: receiving a first radio resource control (RRC) configuration comprising a first PUCCH resource configuration and a second PUCCH resource configuration; Receiving a first downlink control information DCI format for scheduling a first physical downlink shared channel PDSCH and a second DCI format for scheduling a second PDSCH; Determining, according to the first PUCCH resource configuration, a first PUCCH for a first hybrid automatic repeat request HARQ acknowledgment ACK codebook corresponding to the first PDSCH; Determining, according to the second PUCCH resource configuration, a second PUCCH for a second HARQ-ACK codebook corresponding to the second PDSCH; as well as In a case where the first PUCCH and the second PUCCH overlap in the time domain and the first PUCCH is a high-priority PUCCH and the second PUCCH is a low-priority PUCCH, performing the following operations: When the first PUCCH is a dynamically scheduled PUCCH resource, determining a PUCCH resource for the first PUCCH based on a total payload size of high priority uplink control information (UCI) on the first PUCCH and a PUCCH resource indicator in a third DCI format that schedules the first PUCCH; After determining the PUCCH resource for the first PUCCH, determining the number of physical resource blocks (PRBs) of the first PUCCH based on a payload size of the first HARQ-ACK codebook, a payload size of the second HARQ-ACK codebook, a first maximum coding rate, and a second maximum coding rate, where the first maximum coding rate corresponds to a PUCCH format configured by the first PUCCH resource, and the second maximum coding rate corresponds to a PUCCH format configured by the second PUCCH resource; Determining, based on the smaller of a total number of resource elements and a second number of resource elements of the first PUCCH, a first number of resource elements for multiplexing resource elements of the first HARQ-ACK codebook, wherein the total number of resource elements of the first PUCCH is determined based on the number of PRBs of the first PUCCH, and the second number of resource elements is determined based on a payload size of the first HARQ-ACK codebook, a size of a cyclic redundancy check (CRC) for the first HARQ-ACK codebook, and the first maximum coding rate; determining, in the first PUCCH, a third number of resource elements for multiplexing resource elements of the second HARQ-ACK codebook according to a difference between the total number of resource elements of the first PUCCH and the first number of resource elements for multiplexing resource elements of the first HARQ-ACK codebook, When the difference between the total number of resource elements of the first PUCCH and the first number of resource elements is not zero, the first HARQ-ACK codebook and the second HARQ-ACK codebook are multiplexed in the first PUCCH; as well as Transmit the first PUCCH.

2. A user equipment (UE) for transmitting a physical uplink control channel (PUCCH), the UE comprising: a processor configured to execute a computer executable program; as well as a memory coupled to the processor, the memory being configured to store the computer-executable program, and when the computer-executable program is executed by the processor, causing the UE to: receiving a first radio resource control (RRC) configuration comprising a first PUCCH resource configuration and a second PUCCH resource configuration; Receiving a first downlink control information DCI format for scheduling a first physical downlink shared channel PDSCH and a second DCI format for scheduling a second PDSCH; Determining, according to the first PUCCH resource configuration, a first PUCCH for a first hybrid automatic repeat request HARQ acknowledgment ACK codebook corresponding to the first PDSCH; Determining, according to the second PUCCH resource configuration, a second PUCCH for a second HARQ-ACK codebook corresponding to the second PDSCH; as well as In a case where the first PUCCH and the second PUCCH overlap in the time domain and the first PUCCH is a high-priority PUCCH and the second PUCCH is a low-priority PUCCH, performing the following operations: When the first PUCCH is a dynamically scheduled PUCCH resource, determining a PUCCH resource for the first PUCCH based on a total payload size of high priority uplink control information (UCI) on the first PUCCH and a PUCCH resource indicator in a third DCI format that schedules the first PUCCH; After determining the PUCCH resource for the first PUCCH, determining the number of physical resource blocks (PRBs) of the first PUCCH based on a payload size of the first HARQ-ACK codebook, a payload size of the second HARQ-ACK codebook, a first maximum coding rate, and a second maximum coding rate, where the first maximum coding rate corresponds to a PUCCH format configured by the first PUCCH resource, and the second maximum coding rate corresponds to a PUCCH format configured by the second PUCCH resource; Determining, based on the smaller of a total number of resource elements and a second number of resource elements of the first PUCCH, a first number of resource elements for multiplexing resource elements of the first HARQ-ACK codebook, wherein the total number of resource elements of the first PUCCH is determined based on the number of PRBs of the first PUCCH, and the second number of resource elements is determined based on a payload size of the first HARQ-ACK codebook, a size of a cyclic redundancy check (CRC) for the first HARQ-ACK codebook, and the first maximum coding rate; determining, in the first PUCCH, a third number of resource elements for multiplexing resource elements of the second HARQ-ACK codebook according to a difference between the total number of resource elements of the first PUCCH and the first number of resource elements for multiplexing resource elements of the first HARQ-ACK codebook, When the difference between the total number of resource elements of the first PUCCH and the first number of resource elements is not zero, the first HARQ-ACK codebook and the second HARQ-ACK codebook are multiplexed in the first PUCCH; as well as Transmit the first PUCCH.

Images