Patent Publication Number: US-2023155720-A1

Title: Multiplexing of harq-ack with different priorities on pucch

Description:
TECHNICAL FIELD 
     The present disclosure relates generally to communication systems. More specifically, the present disclosure relates to signaling and timeline requirements for multiplexing of HARQ-ACK with different priorities on physical uplink control channel (PUCCH). 
     BACKGROUND ART 
     Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices. 
     As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility, and/or efficiency may present certain problems. 
     For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial. 
     SUMMARY OF INVENTION 
     In one example, a user equipment (UE), comprising: a processor configured to: determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size, multiplex the HARQ-ACK based on the determined coding method; and transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH. 
     In one example, a base station (gNB), comprising: a processor configured to: determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size; and receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
     In one example, a method by a user equipment (UE), comprising: determining a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size, multiplexing the HARQ-ACK based on the determined coding method; and transmitting the multiplexed HARQ-ACK on the PUCCH. 
     In one example, a method by a base station (gNB), comprising: determining a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size; and receiving multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG.  1    is a block diagram illustrating one implementation of one or more gNBs and one or more UEs in which systems and methods for multiplexing of HARQ-ACK with different priorities on physical uplink control channel (PUCCH) may be implemented. 
         FIG.  2    illustrates examples of low priority channel dropping timelines. 
         FIG.  3    illustrates an example of a high priority channel processing delay due to channel collision and channel dropping. 
         FIG.  4    illustrates another example of a high priority channel processing delay due to channel collision and channel dropping. 
         FIG.  5    is a block diagram illustrating one implementation of a gNB. 
         FIG.  6    is a block diagram illustrating one implementation of a UE. 
         FIG.  7    illustrates various components that may be utilized in a UE. 
         FIG.  8    illustrates various components that may be utilized in a gNB. 
         FIG.  9    is a block diagram illustrating one implementation of a UE in which the systems and methods described herein may be implemented. 
         FIG.  10    is a block diagram illustrating one implementation of a gNB in which the systems and methods described herein may be implemented. 
         FIG.  11    is a flow diagram illustrating a method for multiplexing of HARQ-ACK with different priorities on a single PUCCH. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     A user equipment (UE) is described. The UE includes a processor configured to determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH). The coding method is determined based on higher layer signaling, an uplink control information (UCI) payload size or PUCCH resource configuration. The processor is also configured to multiplex the HARQ-ACK based on the determined coding method. The UE also includes transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH. 
     The coding method may include joint coding. HARQ-ACK bits of different priorities may be concatenated into a single codebook, joint coded and transmitted on a ultra-reliable low-latency communication (URLLC) PUCCH resource. 
     The coding method may include separate coding. A HARQ-ACK codebook of URLLC and eMBB may be coded and rate matched independently based on a maximum coding rate of a URLLC PUCCH configuration and an eMBB PUCCH configuration. Rate matched outputs may be concatenated together and transmitted on a selected URLLC PUCCH resource. 
     In an example, joint coding may be used if a HARQ-ACK codebook is less than or equal to a number of bits. In another example, joint coding may be used if a number of HARQ-ACK bits is less than or equal to a threshold. 
     In an example, the coding method may be configured by RRC signaling. In another example, the coding method may be based on a number of configured code rates for multiplexing HARQ-ACK. 
     A base station (gNB) is also described. The gNB includes a processor configured to determine a coding method for multiplexing HARQ-ACK with different priorities on a PUCCH. The coding method is determined based on higher layer signaling, a UCI payload size or PUCCH resource configuration. The gNB also includes receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH. The HARQ-ACK is multiplexed based on the determined coding method. 
     A method by a UE is also described. The method includes determining a coding method for multiplexing HARQ-ACK with different priorities on a PUCCH. The coding method is determined based on higher layer signaling, a UCI payload size or PUCCH resource configuration. The method also includes multiplexing the HARQ-ACK based on the determined coding method. The method further includes transmitting the multiplexed HARQ-ACK on the PUCCH. 
     A method by a gNB is also described. The method includes determining a coding method for multiplexing HARQ-ACK with different priorities on a PUCCH. The coding method is determined based on higher layer signaling, a UCI payload size or PUCCH resource configuration. The method also includes receiving multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
     The 3rd Generation Partnership Project, also referred to as “3GPP,” is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third, fourth, and fifth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems, and devices. 
     3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). 
     At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, etc.). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems. 
     A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms “UE” and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device.” A UE may also be more generally referred to as a terminal device. 
     In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,” “Node B,” “eNB,” “gNB” and/or “HeNB” may be used inter-changeably herein to mean the more general term “base station.” Furthermore, the term “base station” may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and/or a base station. An eNB may also be more generally referred to as a base station device. 
     It should be noted that as used herein, a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a “cell” may be defined as “combination of downlink and optionally uplink resources.” The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources. 
     “Configured cells” are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information. “Configured cell(s)” may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. “Configured cell(s)” for a radio connection may include a primary cell and/or no, one, or more secondary cell(s). “Activated cells” are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). “Deactivated cells” are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a “cell” may be described in terms of differing dimensions. For example, a “cell” may have temporal, spatial (e.g., geographical) and frequency characteristics. 
     Fifth generation (5G) cellular communications (also referred to as “New Radio,” “New Radio Access Technology” or “NR” by 3GPP) envisions the use of time/frequency/space resources to allow for enhanced mobile broadband (eMBB) communication and ultra-reliable low-latency communication (URLLC) services, as well as massive machine type communication (MMTC) like services. A new radio (NR) base station may be referred to as a gNB. A gNB may also be more generally referred to as a base station or base station device. 
     In NR Release-16 (referred to herein as Rel-16), for intra-UE collision handling at the physical (PHY) layer, in the case that a high-priority UL transmission overlaps with a low-priority UL transmission, the high priority UL channel is transmitted, and the low-priority UL channel transmission is dropped fully or partially depending on timeline constraints. A dropping timeline for low priority channel collision with high priority PUCCH of URLLC HARQ-ACK is described herein. For example, in this disclosure, a detailed dropping timeline of the low priority channel when it collides with a high priority PUCCH carrying high priority HARQ-ACK is described. The timeline for channel dropping may be different based on whether the PDSCH is scheduled by a DCI or by a semi-persistent scheduling (SPS) release. Furthermore, the processing time of the high priority channel may be postponed due to channel dropping. 
     HARQ-ACK multiplexing of URLLC and eMBB HARQ-ACK is also described herein. For a UE that supports different service types (e.g., both eMBB and URLLC services), when a PUCCH carrying eMBB HARQ-ACK collides with a PUCCH carrying URLLC HARQ-ACK, the eMBB HARQ-ACK may be dropped. The dropped eMBB HARQ-ACK from the UE may cause the gNB to unnecessarily retransmit the corresponding eMBB PDSCHs even if they are correctly received. Also, the dropped eMBB HARQ-ACK from the UE may increase the delay for data delivery because of the retransmission and waiting for the HARQ-ACK feedback. 
     HARQ-ACK multiplexing methods of URLLC and eMBB HARQ-ACK on PUCCH are also described herein. In a case that multiplexing of HARQ-ACK with different priorities on a PUCCH is supported or configured, how to perform the HARQ-ACK multiplexing is described herein. For example, how to select joint coding or separate coding methods for HARQ-ACKs with different priorities is described. 
     Methods of UCI multiplexing between different priorities are described herein. For example, the configurations and timeline conditions to support multiplexing of eMBB HARQ-ACK and URLLC HARQ-ACK on a single PUCCH are described herein. As enhancements of HARQ-ACK reporting with different priorities, multiplexing of UCI between different priorities (e.g., between eMBB and URLLC) can be supported by high layer signaling under some timing restrictions. For example, this may include support of multiplexing of the same UCI type on a single PUCCH (e.g., URLLC HARQ-ACK and eMBB HARQ-ACK). 
     New RRC parameters can be configured to allow different HARQ-ACK codebook multiplexing on a single PUCCH, as described herein. Different HARQ-ACK codebook multiplexing on a single PUCCH can be performed based on timeline constraints. New processing timeline(s) may be specified to allow extra processing time of potential multiplexing of HARQ-ACK codebooks with different priorities. 
     If multiplexing of HARQ-ACK with different priorities on a PUCCH is supported, at least two coding methods of HARQ-ACK multiplexing may be supported. In one method, joint coding is used. The HARQ-ACK bits of different priorities may be concatenated into a single codebook, and the joint codebook may be coded and transmitted on a URLLC PUCCH resource using the URLLC HARQ-ACK coding and rate matching methods based on the maximum coding rate of the URLLC PUCCH configuration. In another method, separate coding is used. The HARQ-ACK codebook of URLLC and eMBB may be coded and rate matched independently based on the maximum coding rate of the URLLC and eMBB PUCCH configuration. The coded bits may be rate matched separately and then concatenated together and transmitted on the selected PUCCH resource for URLLC. The method for the HARQ-ACK multiplexing may be determined based on new higher layer signaling or conditions of HARQ-ACK payload sizes. 
     Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods. 
       FIG.  1    is a block diagram illustrating one implementation of one or more gNBs  160  and one or more UEs  102  in which systems and methods for signaling and timeline requirements for multiplexing between HARQ-ACK codebooks with different priorities may be implemented. The one or more UEs  102  communicate with one or more gNBs  160  using one or more antennas  122   a - n.  For example, a UE  102  transmits electro-magnetic signals to the gNB  160  and receives electromagnetic signals from the gNB  160  using the one or more antennas  122   a - n.  The gNB  160  communicates with the UE  102  using one or more antennas  180   a - n.    
     The UE  102  and the gNB  160  may use one or more channels  119 ,  121  to communicate with each other. For example, a UE  102  may transmit information or data to the gNB  160  using one or more uplink channels  121 . Examples of uplink channels  121  include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channels  121  (e.g., PUSCH) may be used for transmitting UL data (i.e., Transport Block(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)). 
     In some examples, UL data may include URLLC data. The URLLC data may be UL-SCH data. Here, URLLC-PUSCH (i.e., a different Physical Uplink Shared Channel from PUSCH) may be defined for transmitting the URLLC data. For the sake of simple description, the term “PUSCH” may mean any of (1) only PUSCH (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not regular PUSCH). 
     Also, for example, uplink channels  121  may be used for transmitting Hybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel State Information (CSI), and/or Scheduling Request (SR) signals. The HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)). 
     The CSI may include information indicating a channel quality of downlink. The SR may be used for requesting UL-SCH (Uplink-Shared Channel) resources for new transmission and/or retransmission. For example, the SR may be used for requesting UL resources for transmitting UL data. 
     The one or more gNBs  160  may also transmit information or data to the one or more UEs  102  using one or more downlink channels  119 , for instance. Examples of downlink channels  119  include a PDCCH, a PDSCH, etc. Other kinds of channels may be used. The PDCCH may be used for transmitting Downlink Control Information (DCI). 
     Each of the one or more UEs  102  may include one or more transceivers  118 , one or more demodulators  114 , one or more decoders  108 , one or more encoders  150 , one or more modulators  154 , a data buffer  104 , and a UE operations module  124 . For example, one or more reception and/or transmission paths may be implemented in the UE  102 . For convenience, only a single transceiver  118 , decoder  108 , demodulator  114 , encoder  150 , and modulator  154  are illustrated in the UE  102 , though multiple parallel elements (e.g., transceivers  118 , decoders  108 , demodulators  114 , encoders  150 , and modulators  154 ) may be implemented. 
     The transceiver  118  may include one or more receivers  120  and one or more transmitters  158 . The one or more receivers  120  may receive signals from the gNB  160  using one or more antennas  122   a - n.  For example, the receiver  120  may receive and downconvert signals to produce one or more received signals  116 . The one or more received signals  116  may be provided to a demodulator  114 . The one or more transmitters  158  may transmit signals to the gNB  160  using one or more antennas  122   a - n.  For example, the one or more transmitters  158  may upconvert and transmit one or more modulated signals  156 . 
     The demodulator  114  may demodulate the one or more received signals  116  to produce one or more demodulated signals  112 . The one or more demodulated signals  112  may be provided to the decoder  108 . The UE  102  may use the decoder  108  to decode signals. The decoder  108  may produce decoded signals  110 , which may include a UE-decoded signal  106  (also referred to as a first UE-decoded signal  106 ). For example, the first UE-decoded signal  106  may comprise received payload data, which may be stored in a data buffer  104 . Another signal included in the decoded signals  110  (also referred to as a second UE-decoded signal  110 ) may comprise overhead data and/or control data. For example, the second UE decoded signal  110  may provide data that may be used by the UE operations module  124  to perform one or more operations. 
     In general, the UE operations module  124  may enable the UE  102  to communicate with the one or more gNBs  160 . The UE operations module  124  may include a UE scheduling module  126 . In some examples, the UE scheduling module  126  may be utilized to perform signaling and timeline requirements for multiplexing between HARQ-ACK codebooks with different priorities as described herein. 
     UCI types reported in a PUCCH may include HARQ-ACK information, SR, LRR, and CSI. UCI bits may include HARQ-ACK information bits, if any, SR information bits, if any, LRR information bit, if any, and CSI bits, if any. The HARQ-ACK information bits correspond to a HARQ-ACK codebook. 
     In NR Rel-16, two levels of priorities can be indicated for different services. For example, a lower priority or priority index 0 may be indicated for eMBB services. A higher priority or priority index 1, may be indicated for URLLC service. 
     To resolve collision between UL transmissions, a UE may perform the following. In a first step, the UE may resolve collision between UL transmissions with the same priority. In a second step, the UE may resolve collision between UL transmissions with different priorities. 
     For UL channel transmission in Rel-16, UCI multiplexing of different priorities are not supported. In a case of a collision between different priorities, the high priority channel is transmitted, and the low priority channel is dropped.
         When a high-priority UL transmission overlaps with a low-priority UL transmission in a slot, the UE is expected to cancel the low-priority UL transmission starting from T proc,2 +d 1  after the end of PDCCH scheduling the high-priority transmission. In this case, T proc,2  is the UE processing time capability for the carrier. Value d 1  is the time duration corresponding to 0,1,2 symbols reported by UE capability. It should be noted that d 2,1 =0 is for cancellation. The minimum processing time of the high priority channel may be extended by d 2  symbols, where d 2  is the time duration corresponding to 0,1,2 symbols reported by UE capability. The overlapping condition may be per repetition of the uplink transmission.       

     The timeline above mainly refers to PUSCH transmission scheduling by a DCI. Basically, in the case of intra-UE UL channel collision with different priorities, the low priority channel should be cancelled as soon as the high priority channel transmission is known. On the other hand, the minimum processing time of the high priority channel may be extended to allow the process of the cancellation of the low priority channel. However, the detailed timeline for the collision case between a high priority PUCCH carrying high priority HARQ-ACK and a low priority channel is not defined yet. 
     Examples of a timeline for low priority channel dropping when colliding with a PUCCH carrying a high priority HARQ-ACK codebook are described herein. For a high priority PUCCH with a high priority HARQ-ACK codebook, a high priority HARQ-ACK is corresponding to a high priority PDSCH transmission. The PDSCH may be a scheduled transmission or a SPS release, and the processing timeline can be slightly different between them. 
     After a first step of resolved collision between UL transmissions with same priority, if there is a collision between channels with different priorities, the low priority channel may be dropped fully or partial depending on the timeline relationships. If the high priority channel starts at the same symbol as the low priority channel or the high priority channel starts earlier than the low priority channel, the low priority channel is fully dropped without transmission, and only the high priority channel is transmitted. 
     If the starting symbol of a low priority channel is earlier than a high priority channel, different methods may be considered depending on the timing restrictions, especially if the high priority channel transmission is known before the low priority channel transmission. The dropping timeline and processing timeline for this case are described herein.
         Examples of a low priority channel dropping timeline are described herein. Let T proc,1  correspond to the UE processing time of a high priority PDSCH transmission for the carrier. The transmission of a PUCCH carrying the HARQ-ACK for the corresponding PDSCH can be known T proc,1  plus d 1,1  symbols after the end of last high priority PDSCH transmission.   In one method, if the starting symbol of the low priority channel is not earlier than T proc,1  plus d 1,1  symbols after the end of last high priority PDSCH transmission, the low priority channel can be fully dropped, as shown in  FIG.  2 ( a ) . Value d 1,1  may be the time duration corresponding to 0,1,2 symbols reported by UE capability. Otherwise, the low priority PUCCH for eMBB HARQ-ACK transmission is already started when the UE realizes the high priority PUCCH for high priority HARQ-ACK should be scheduled. The low priority channel can be dropped from T proc,1  plus d 1,1  symbols after the end of last high priority PDSCH transmission, as shown in  FIG.  2 ( b ) .   Thus, for a PDSCH scheduled by a DCI, the UE may drop the low priority UL channel from a first symbol s 0  of the low priority UL low priority UL channel (e.g., PUCCH or PUSCH), where s 0  is not before a symbol with CP starting after T proc,1   drop  after a last symbol of any corresponding PDSCH, T proc,1   drop  is given by the maximum of {T proc,1   drop,1 , . . . , T proc,1   drop,i , . . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH for high priority HARQ-ACK, T proc,1   drop,i =(N 1 +d 1,1 +1)·(2048+144)·κ·2 −μ ·T C , d 1,1  is selected for the i-th PDSCH following TS 38.214, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   Alternatively with further enhancement, in another method, for a PDSCH scheduled by a DCI, the UE may drop the low priority UL channel from a first symbol s 0  of the low priority UL low priority UL channel (PUCCH or PUSCH), where s 0  is not before a symbol with CP starting after T proc,1   drop  after the last symbol of any DCI scheduling the corresponding PDSCH, T proc,1   drop  is given by maximum of {T proc,1   drop,1 , . . . , T proc,1   drop,i , . . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH for high priority HARQ-ACK, T proc,1   drop,i =(N 1 +d 1,1 +1)·(2048+144)·κ·2 −μ ·T C , d 1,1  is selected for the i-th PDSCH following TS 38.214, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. Compare with the previous method, the UE can drop the low priority UL channel after the scheduling DCI is detected with the corresponding PUCCH starting point.   For a high priority PDSCH by a SPS release, the processing time is defined separately from a PDSCH scheduled by a DCI. In one method, the dropping timeline is determined based on the processing time of a PDSCH by a SPS release and plus d 1,1  symbols after the end of PDSCH transmission of a SPS release, where value d 1,1  may be the time duration corresponding to 0,1,2 symbols reported by UE capability. Thus, for a high priority PDSCH by a SPS release, the UE may drop the low priority UL channel from a first symbol s 0  of the low priority UL low priority UL channel (PUCCH or PUSCH), where s 0  is not before a symbol with CP starting after T proc,release   drop  after a last symbol of any corresponding SPS PDSCH release. T proc,release   drop  is given by maximum of {T proc,release   drop,1 , . . . , T proc,release   drop,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   drop,i =(N+1+d 1,1 )·(2048+144)·κ·2 −μ ·T C , N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   In another method, the dropping timeline is determined based on the processing time of a PDSCH by a SPS release only. Thus, for a high priority PDSCH by a SPS release, the UE may drop the low priority UL channel from a first symbol s 0  of the low priority UL low priority UL channel (PUCCH or PUSCH), where s 0  is not before a symbol with CP starting after T proc,release   drop  after a last symbol of any corresponding SPS PDSCH release. T proc,release   drop  is given by maximum of {T proc,release   drop,1 , . . . , T proc,release   drop,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   drop,i =(N+1)·(2048+144)·κ·2 −μ ·T C , N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   Processing time delay requirements for high priority PUCCH with URLLC HARQ-ACK are also described herein. Due to the evaluation of channel collision and channel dropping of low priority channels, the processing time for the high priority PUCCH with URLLC HARQ-ACK may be extended with some extra delay. For example, the minimum processing time of the high priority channel may be extended by d 1,2  symbols, where value d 1,2  is the time duration corresponding to 0,1,2 or more symbols reported by UE capability.       

     The HARQ-ACK timing of a PDSCH transmission may be determined by the PDSCH-to-HARQ timing indication with a k value. If the PUCCH resource is configured at subslot level, a subslot structure or duration is configured. For a PDSCH transmission ended in subslot n, the HARQ-ACK should be report in a PUCCH resource in subslot n+k. If the PUCCH resource is configured at slot level, for a PDSCH transmission ended in slot n, the HARQ-ACK should be reported in a PUCCH resource in slot n+k. In all cases, the HARQ-ACK timing should satisfy the processing time requirements even with processing delay considerations. 
     Thus, in the case of channel collision with different priorities, and if dropping of low priority channel is performed, the UE expects that the first symbol of the high priority PUCCH for high priority HARQ-ACK, among a group overlapping PUCCHs and PUSCHs in the slot, satisfies the following timeline conditions.
         In one method, the extra delay d 1,2  may be applied jointly with the dropping delay d 1,1 , where value d 1,2  and d 1,2  are the time durations corresponding to 0,1,2 reported by UE capability.   For a PDSCH scheduled by a DCI, s 0  is not before a symbol with CP starting after T proc,1   delay  after a last symbol of any corresponding PDSCH, T proc,1   delay  is given by maximum of {T proc,1   delay,1 , . . . , T proc,1   delay,i , . . . }, where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,1   delay,i =(N 1 +d 1,1 +d 1,2 +1)·(2048+144)·κ·2 −μ ·T C , d 1,1  and d 1,2  are selected for the i-th PDSCH, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. In this method, the processing timeline requirement for a PDSCH is extended by a total of d 1,1 +d 1,2  symbols, as shown in  FIG.  3   .   In another method, the extra delay d 1,2  may be applied independently from the dropping delay d 1,1 . In this case, the value of d 1,2  should be the same as or greater than the value d 1,1 , where value d 1,2  is the time duration corresponding to 0,1,2 or more symbols reported by UE capability. Thus, in this method, d 1,2  may be determined for the total delay required to perform collision resolution and channel dropping and be configured with a larger number than d 1,1 , For a PDSCH scheduled by a DCI, s 0  is not before a symbol with CP starting after T proc,1   delay  after a last symbol of any corresponding PDSCH, T proc,1   delay  is given by maximum of {T proc,1   delay,1 , . . . , T proc,1   delay,i , . . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,1   delay,i =(N 1 +d 1,2 +1)·(2048+144)·κ·2 −μ ·T C , d 1,2  is selected for the i-th PDSCH, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. In this method, the processing timeline requirement for a PDSCH is extended by d 1,2  symbols, as shown in  FIG.  4   .   For a high priority PDSCH by a SPS release, in one method, if the dropping timeline is determined based on the processing time of a PDSCH by a SPS release and plus d 1,1  symbols after the end of PDSCH transmission of a SPS release, and the extra delay d 1,2  may be applied jointly with the dropping delay d 1,1 , the s 0  is not before a symbol with CP starting after T proc,release   delay  after a last symbol of any corresponding SPS PDSCH release. T proc,release   delay  is given by maximum of {T proc,release   delay,1 , . . . , T proc,release   delay,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   delay,i =(N+1+d 1,1 +d 1,2 )·(2048+144)·κ· 2   −μ ·T C , N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. In this method, the processing timeline requirement for a PDSCH is extended by a total of d 1,1 +d 1,2  symbols.   For a high priority PDSCH by a SPS release, if the dropping timeline is determined based on the processing time of a PDSCH by a SPS release only, or if the dropping timeline is determined based on the processing time of a PDSCH by a SPS release and plus d 1,1  symbols after the end of PDSCH transmission of a SPS release and if the extra delay d 1,2  may be applied independently from the dropping delay d 1,1 , s 0  is not before a symbol with CP starting after T proc,release   delay  after a last symbol of any corresponding SPS PDSCH release. T proc,release   mux  is given by maximum of {T proc,release   delay,1 , . . . , T proc,release   delay,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   delay,i =(N+1+d 1,2 )·(2048+144)·κ·2 −μ ·T C , N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   In another approach, for simplicity, a single timeline can be defined for both channel dropping and high priority channel processing. Thus, a single delay parameter (e.g., d 1,1 ) can be selected to satisfy both low priority channel dropping and high priority channel processing timeline.
 
HARQ-ACK reporting and HARQ-ACK priorities is also described herein. In NR, two codebooks with different priorities can be constructed simultaneously. A priority 0 or low priority HARQ-ACK codebook is constructed for eMBB services, and a priority 1 or high priority HARQ-ACK codebook is constructed for URLLC services. PUCCH resources can be configured separately for different HARQ-ACK codebooks in subslot level or slot level.
       

     A UE may transmit one or two PUCCHs on a serving cell in different symbols within a slot. For HARQ-ACK reporting, when the UE transmits two PUCCHs in a slot and the UE is not provided ACKNACKFeedbackMode=SeparateFeedback, at least one of the two PUCCHs uses PUCCH format 0 or PUCCH format 2. If a UE is provided ACKNACKFeedbackMode=SeparateFeedback, the UE may transmit up to two PUCCHs with HARQ-ACK information in different symbols within a slot. 
     Since UCI multiplexing between different channel priorities is currently not supported, for PUCCH collision between URLLC HARQ-ACK and eMBB HARQ-ACK, the PUCCH for eMBB HARQ-ACK will be dropped and the PUCCH carrying HARQ-ACK for URLLC is transmitted. The frequent dropping of eMBB HARQ-ACK will cause unnecessary retransmissions of eMBB PDSCHs. Consequently, it will increase the data delivery delay, and will reduce the effective throughput and spectrum efficiency of NR services. Thus, some enhancements for dropped eMBB HARQ-ACK feedback may be introduced for channel collision between URLLC HARQ-ACK and eMBB HARQ-ACK. 
     Some examples of enhancements of HARQ-ACK multiplexing are described herein. To enhance HARQ-ACK feedback in the case of collision between URLLC HARQ-ACK and eMBB HARQ-ACK, multiplexing of HARQ-ACK between eMBB and URLLC can be supported under some timing restrictions. 
     In a first method (Method 1), a new HARQ-ACK report mode may be specified. To allow multiplexing of HARQ-ACK codebooks with different priorities, a new ACKNACK feedback mode may be introduced to allow multiplexing of two HARQ-ACK codebooks in one PUCCH reporting. For example, the new mode may be named as JointFeedback, or MultiFeedback. Thus, if a UE is provided ACKNACKFeed-backMode=JointFeedback, and if there is no collision between the PUCCHs with HARQ-ACK information, the UE may transmit up to two PUCCHs with HARQ-ACK information in different symbols within a slot. This has the same behavior as ACK-NACKFeedbackMode=SeparateFeedback. 
     If a UE is provided ACKNACKFeedbackMode=JointFeedback, and if there is collision between the PUCCHs with HARQ-ACK information with different priorities, the HARQ-ACK information from two different codebooks with different priorities may be multiplexed and jointly reported in one PUCCH if timeline can be satisfied. In this case, the reporting PUCCH resource should be selected from the PUCCH resources configured for the high priority HARQ-ACK codebook (e.g., HARQ-ACK PUCCH resource configured for URLLC). 
     In a second method (Method 2), new RRC parameters may be introduced by higher layer signaling. In this method, new RRC configurations can be specified to allow multiplexing of UCI with different priorities for different service types on a single PUCCH. For example, a parameter of multi-HARQ-ACKs or simultaneous-HARQ-ACKs can be configured to allow multiplexing of URLLC HARQ-ACK and eMBB HARQ-ACK on a single PUCCH. Thus, if a UE is configured or enabled with multi-HARQ-ACKs, and if there is no collision between the PUCCHs with HARQ-ACK information, the UE may transmit up to two PUCCHs with HARQ-ACK information in different symbols within a slot. 
     If a UE is configured or enabled with multi-HARQ-ACKs, and if there is collision between the PUCCHs with HARQ-ACK information with different priorities, the HARQ-ACK information from two different codebooks with different priorities may be multiplexed and jointly reported in one PUCCH if timeline can be satisfied. Again, the reporting PUCCH resource should be selected from the PUCCH resources configured for the high priority HARQ-ACK codebook (e.g., HARQ-ACK PUCCH resource configured for URLLC). 
     Timeline requirements for multiplexing of HARQ-ACK codebooks with different priorities are also described. The multiplexing of HARQ-ACK with different priorities for different service types and reporting on PUCCH may have some timing restrictions. In NR Rel-16, out of order HARQ-ACK is not supported. However, to ensure proper joint operation of eMBB and URLLC on a single UE, out of order HARQ-ACK is important and should be allowed in Rel-17 and beyond. The out of order HARQ-ACK may be achieved by defining a single UE capability of processing time, or different UE capability of processing time for eMBB and URLLC respectively. 
     The first timing restriction is the low priority channel dropping timeline. The PUCCH reporting with URLLC HARQ-ACK and eMBB HARQ-ACK multiplexing is allowed if the low priority PUCCH channel for low priority HARQ-ACK can be fully dropped based on high priority channel processing timeline. Otherwise, if the low priority eMBB HARQ-ACK PUCCH transmission is already started, eMBB HARQ-ACK and URLLC HARQ-ACK multiplexing should not be applied. The channel dropping behavior should be performed as described above. Thus, the URLLC HARQ-ACK PUCCH is transmitted, and the eMBB HARQ-ACK PUCCH is dropped based on the dropping timeline. 
     If eMBB and URLLC HARQ-ACK is allowed based on the first dropping timeline, the second timeline should be further evaluated so that the processing time of the high priority PDSCH processing and PUCCH preparation time can be extended to allow HARQ-ACK multiplexing. The processing time may be called as multiplexing timeline, which includes the processing time of PDSCH detection, HARQ-ACK codebook generation, HARQ-ACK multiplexing, joint or separate HARQ-ACK codebook encoding and rate matching, and PUCCH resource selection, etc. If the second processing timeline can be satisfied, eMBB HARQ-ACK and URLLC HARQ-ACK multiplexing is applied and reported on a single PUCCH resource. 
     Even if joint HARQ-ACK or simultaneous HARQ-ACKs are configured, if the second timeline cannot be satisfied, there is not enough time to perform UCI multiplexing before the URLLC PUCCH transmission, the URLLC HARQ-ACK PUCCH should be transmitted, and the eMBB HARQ-ACK PUCCH is dropped. Similarly, if there is no configured URLLC PUCCH resource can carry the multiplexed eMBB HARQ-ACK and URLLC HARQ-ACK, the URLLC HARQ-ACK PUCCH should be transmitted, and the eMBB HARQ-ACK PUCCH is dropped.  FIG.  11    shows the procedures to support multiplexing of HARQ-ACK with different priorities on a single PUCCH. 
     In another approach, only one timeline is specified. Thus, the second multiplexing timeline above can be used to evaluate if HARQ-ACK multiplexing can be performed. If the starting symbol of the low priority PUCCH for eMBB HARQ-ACK is earlier than the second timeline, HARQ-ACK multiplexing is not possible, and channel dropping is performed. If the starting symbol of the low priority PUCCH for eMBB HARQ-ACK is after the second timeline, HARQ-ACK multiplexing may be performed. However, if there is no configured URLLC PUCCH resource that can carry the multiplexed eMBB HARQ-ACK and URLLC HARQ-ACK, the URLLC HARQ-ACK PUCCH should be transmitted, and the eMBB HARQ-ACK PUCCH is dropped. 
     Timeline definitions for channel dropping and UCI multiplexing of HARQ-ACK codebooks with different priorities are also described herein. For high priority PUCCH with high priority HARQ-ACK codebook, a high priority HARQ-ACK corresponds to a high priority PDSCH transmission. The PDSCH may be a scheduled transmission or a SPS release, and the processing timeline can be slightly different between them.
         The first timeline of low priority channel dropping timeline is given above. The second timeline is determined to support UCI multiplexing of different priorities on a single PUCCH. This may be similar to or the same as the processing time delay described above. However, since UCI multiplexing operation requires coding, multiplexing and PUCCH resource selection, the UCI multiplexing time should be the same as or longer than the channel dropping delay and the processing delay for channel dropping. Thus, the minimum processing time of the high priority channel should be extended by d 1,3  symbols, where value d 1,3  is the time duration reported by UE capability.   If URLLC HARQ-ACK and eMBB HARQ-ACK multiplexing on a single PUCCH is allowed based on the first low priority dropping timeline, the minimum processing time of the high priority PDSCH and preparation of high priority PUCCH should be extended by d 1,3  symbols, where value d 1,3  is the time duration corresponding to 0,1,2 or more symbols reported by UE capability. That is, if URLLC HARQ-ACK and eMBB HARQ-ACK multiplexing on a single PUCCH is support in case of channel collision, the UE expects that the first symbol s 0  of the high priority PUCCH for multiplexed HARQ-ACK, among a group overlapping PUCCHs and PUSCHs in the slot, satisfies the following timeline conditions.   In one approach, d 1,3  is applied jointly with d 1,1  and d 1,2 . Thus, for a PDSCH scheduled by a DCI, s 0  is not before a symbol with CP starting after T proc,1   mux  after a last symbol of any corresponding PDSCH. T proc,1   mux  is given by the maximum of {T proc,1   mux,1 , . . . , T proc,1   mux,i , . . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,1   mux,i =(N 1 +d 1,1 +d 1,2 +d 1,3 +1)·(2048+144)·κ·2 −μ ·T c , d 1,1 , d 1,2  and d 1,3  are selected for the i-th PDSCH, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. In this method, the processing timeline requirement for a PDSCH is extended by a total of d 1,1 +d 1,2 +d 1,3  symbols.   In another method, d 1,3  is applied separately from d 1,1  and d 1,2 . Furthermore, d 1,3  may be determined for the total delay required to perform UCI multiplexing and be configured with a larger number than d 1,1  and d 1,2 , and T proc,1   mux,i =(N 1 +d 1,3 +1)·(2048+144)·κ·2 −μ ·T C  is determined based on d 1,3  only. Thus, for a PDSCH scheduled by a DCI, s 0  is not before a symbol with CP starting after T proc,1   mux  after a last symbol of any corresponding PDSCH. T proc,1   mux  is given by the maximum of {T proc,1   mux,1 , . . . , T proc,1   mux,i , . . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,1   mux,i =(N 1 +d 1,3 +1)·(2048+144)·κ·2 −μ ·T C , where d 1,3  is selected for the i-th PDSCH, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   In yet another approach, d 1,3  is applied jointly with d 1,1  but separately from d 1,2 . Thus, for a PDSCH scheduled by a DCI, s 0  is not before a symbol with CP starting after T proc,1   mux  after a last symbol of any corresponding PDSCH. T proc,1   mux  is given by the maximum of {T proc,1   mux,1 , . . . , T proc,1   mux,i , . . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,1   mux,i =(N 1 +d 1,1 +d 1,3 +1)·(2048+144)·κ·2 −μ ·T C , d 1,1  and d 1,3  are selected for the i-th PDSCH, N 1  is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. In this method, the processing timeline requirement for a PDSCH is extended by a total of d 1,1 +d 1,3  symbols.   Similarly, for a high priority PDSCH by a SPS release, in one method, d 1,3  is applied jointly with d 1,1  and d 1,2 . If the dropping timeline is determined based on the processing time of a PDSCH by a SPS release and plus d 1,1  symbols after the end of PDSCH transmission of a SPS release, and the extra delay d 1,3  may be applied jointly with the dropping delay d 1,1  and processing delay d 1,2 , s 0  is not before a symbol with CP starting after T proc,release   mux  after a last symbol of any corresponding SPS PDSCH release. T proc,release   mux  is given by the maximum of {T proc,release   mux,1 , . . . , T proc,release   mux,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   mux,i =(N+1+d 1,1 +d 1,2 +d 1,3 )·(2048+144)·κ·2 −μ ·T C , where d 1,1 , d 1,2  and d 1,3  are selected for the i-th PDSCH, N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   For a high priority PDSCH by a SPS release, in another method, d 1,3  is applied separately from d 1,1  and d 1,2 . And d 1,3  may be determined for the total delay required to perform UCI multiplexing and be configured with a larger number than d 1,1  and d 1,2 . s 0  is not before a symbol with CP starting after T proc,release   mux  after a last symbol of any corresponding SPS PDSCH release. T proc,release   mux  is given by maximum of {T proc,release   mux,1 , . . . T proc,release   mux,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   mux,i =(N+1+d 1,3 )·(2048+144)·κ·2 −μ ·T C , where d 1,3  is selected for the i-th PDSCH, N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   Yet in another approach, for a high priority PDSCH by a SPS release, d 1,3  is applied jointly with d 1,1  but separately from d 1,2 . Thus, for a PDSCH scheduled by a DCI, s 0  is not before a symbol with CP starting after T proc,release   mux  after a last symbol of any corresponding SPS PDSCH release. T proc,release   mux  is given by maximum of {T proc,release   mux,1 , . . . , T proc,release   mux,i , . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, T proc,release   mux,i =(N+1++d 1,1 +d 1,3 )·(2048+144)·κ·2 −μ ·T C , where d 1,3  is selected for the i-th PDSCH, N is described in Clause 10.2 of TS38.213 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.   In yet another approach, for a PDSCH scheduled by a DCI or a PDSCH by a SPS release, the multiplexing delay d 1,3  and processing delay d 1,2  can be the same. Thus, only d 1,2  or d 1,3  is specified and applied as the UCI multiplexing time and the extra processing delay.   In yet another approach, for simplicity, for a PDSCH scheduled by a DCI or a PDSCH by a SPS release, only one timeline is specified and applied. The maximum number of symbols required for extra processing time is evaluated and determined based on UE capability. The determined maximum number of symbols required for extra processing time may be applied as d 1,1  to the channel dropping, and UCI multiplexing timeline.       

     Channel coding method selection for HARQ-ACK multiplexing between different priorities is also described herein. If a UE  102  is provided ACKNACKFeedbackMode=JointFeedback, or if multiplexing of UCI with different priorities for different service types on a single PUCCH is supported and configured by higher layer signaling, and if the timeline conditions can be satisfied, HARQ-ACK multiplexing between different priorities is supported on a single PUCCH. The PUCCH resource for HARQ-ACK multiplexing of different priorities may be a PUCCH resource configured for the high priority HARQ-ACK codebook (e.g., HARQ-ACK codebook with priority index 1). 
     If a UE is  102  provided only one PUCCH resource set for transmission of high priority HARQ-ACK information (e.g., HARQ-ACK codebook with priority index 1), in response to PDSCH reception scheduled by a DCI format or in response to a SPS PDSCH release, the UE  102  does not expect to be provided with joint HARQ-ACK feedback of different priorities on a single PUCCH. Otherwise if supported, HARQ-ACK multiplexing of different priorities in a PUCCH transmission is performed on a PUCCH resource using PUCCH format 2, PUCCH format 3, or PUCCH format 4. 
     When HARQ-ACK multiplexing of different priorities is supported, a coding method may be employed, as described herein. The multiplexed UCI for each priority may include the HARQ-ACK of the given priority and the SR bits if applicable for the given priority. 
     In a first method (Method 1), joint coding of UCI with different priorities may be applied. In this method, the UCI bits of different priorities may be concatenated into a single codebook for channel coding and rate matching on PUCCH resources. Joint coding methods may be used in LTE and NR UCI multiplexing on PUCCH (e.g., UCI multiplexing of HARQ-ACK and CSI, and multiplexing of HARQ-ACK and SR on PUCCH format 2/3/4). 
     The PUCCH resource for HARQ-ACK multiplexing of different priorities may be a PUCCH resource configured for the high priority HARQ-ACK codebook (e.g., HARQ-ACK codebook with priority index 1). A UE  102  may be configured by max-CodeRate a code rate multiplexing HARQ-ACK of different priorities in a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 configured for high priority HARQ-ACK codebook. 
     Joint coding may apply a one channel coding process and may be simple to implement. This is a priority inheritance mechanism. When low priority UCI is multiplexed with high priority UCI, the channel coding and error protection for the low priority UCI is promoted/evaluated or inherited from the high priority UCI. For UCI multiplexing between different priorities, the low priority UCI may be provided with the same reliability and error protection as the high priority UCI. On the other hand, the PUCCH resource utilization may be low because all bits are coded together, and the coded bits are rate matched with ultra-reliability requirements following the maximum coding rate configured for the high priority PUCCH. 
     Joint coding may provide some benefits. For example, joint coding may provide validation by CRC for a codebook with up to 1 bits of UCI but with a total payload greater than 11 bits. Joint coding may reduce overhead with one CRC instead of two CRCs. Joint coding may provide higher coding gain (e.g., larger payload by polar code vs. smaller payload by RM code). 
     In a second method (Method 2), separate coding of UCI with different priorities may be implemented. In this method, the UCIs of different priorities may be channel coded and rate matched separately. The channel coding of UCIs with different priorities may be coded based on the UCI size of the given priority, and the rate match of the UCI encoded bits may be performed based on the maximum coding rate configured for the PUCCH resources of the given priority. The rate matched outputs may then be concatenated and transmitted on the PUCCH resource. 
     Compared with joint coding, the separate coding method may use two channel coding processes for UCIs with different priorities. However, separate coding may allow larger payload sizes on the same PUCCH resource. Because eMBB UCI does not need ultra-reliability (as compared to URLLC UCI), eMBB UCI may be rate matched with a higher maximum coding rate than the maximum coding rate for the URLLC UCI. Therefore, with separate coding of UCIs with different priorities, the total number of URLLC and eMBB UCI bits on a PUCCH resource configured for URLLC may be higher than the maximum payload size configured for the URLLC UCI only. This may provide better resource utilization and spectrum efficiency for the PUCCH transmissions. If the configured PUCCH resource for high priority cannot carry all UCI with separate coding, the low priority UC may be dropped, and only the high priority UCI is transmitted. 
     Separate coding may provide some benefits. Separate coding may provide different reliability for different UCI type or UCIs for different service types. Separate coding may reduce the total resource usage of PUCCH transmission. Separate coding may support larger total UCI payload than joint coding. 
     With the different channel coding methods described herein, methods and configurations to determine which channel coding method should be used for HARQ-ACK multiplexing with different priorities are also described. As discussed above, each channel coding method has benefits. The channel coding method may be selected based on the conditions to provide the best benefit and performance for the UCI feedback. 
     In one method, only joint coding is used. This may be considered a priority inheritance mechanism. When low priority UCI is multiplexed with high priority UCI, the channel coding and error protection for the low priority UCI is promoted/evaluated or inherited from the high priority UCI. 
     For up to 2 bits of UCI reporting on PUCCH, a sequence may be used in PUCCH format 0 and PUCCH format 1. The channel coding method of less than or equal to 2 bits is not specified for PUCCH format 2/3/4. Thus, with joint coding, in the case of 1 or 2 bits of HARQ-ACK, the UE  102  may always assume 2 bits when HARQ-ACK multiplexing between different priorities is performed. In the case of 1 bit of HARQ-ACK, a bit of “0” may be reported with “00”, and a bit of “1” may be reported with “11”. This ensures the total payload is always more than 2 bits. 
     The concatenated HARQ-ACK bits are then encoded and transmitted on a PUCCH resource with PUCCH format 2 or PUCCH format 3 or PUCCH format 4. If the total payload exceeds the maximum payload size, the HARQ-ACK codebook with priority 0 may be dropped, and only the HARQ-ACK codebook with priority 1 is reported. 
     In another method, separate coding may be applied. This method can be applied at least for the case where the number of HARQ-ACK bits for codebooks with different priorities is greater than 2 bits. With this method, HARQ-ACK codebooks may be encoded separately and rate matching may be based on the maximum coding rate of each PUCCH configuration. 
     In other approaches, the coding method may be determined based on the payload size of the codebooks or determined by higher layer signaling, as given in detail below. In a first approach (Approach 1), the coding method may be determined by payload size. Because there is no effective coding method defined for 1 or 2 bits of UCI on PUCCH, virtually only repetition can be used. Thus, in one approach, if any HARQ-ACK is no more than 2 bits, joint coding of HARQ-ACK multiplexing with different priorities may be used. Separate coding may be used if both HARQ-ACK codebooks are more than 2 bits. 
     For less than or equal to 11 bits of UCI, Reed-Muller (RM) code may be used. The RM code generates an output of 20 coded bits. The effective coding rate is higher if the number of UCI bits is larger. Furthermore, there is no CRC with RM code. Thus, there is no validation if the UCI is received with error. In order to provide CRC verification for the HARQ-ACKs, in another approach, joint coding can be used if the number of bits for HARQ-ACK with or without SR of any priority index is less or equal to 11 bits. And separate coding is used if the number of bits for HARQ-ACK with or without SR of both priority index is more than 11 bits. Of course, if the total number of UCI bits after concatenation is still less or equal to 11 bits, RM code may still be used for channel coding. 
     In another approach, the coding method may be determined by the payload size of the low priority HARQ-ACK with or without SR. Because the low priority UCI bits are appended to high priority UCI bits, joint coding may be used if the number of low priority UCI bits is small. Thus, if the number of bits for low priority HARQ-ACK with or without SR is less than or equal to a threshold, joint coding is used. Otherwise, if the number of bits for low priority HARQ-ACK with or without SR is greater than a threshold, separate coding may be used. In an example, the payload threshold may be a fixed value (e.g., 11 bits). In another example, the payload threshold may be an existing configured value (e.g., the N 2  or N 3  of the maxPayloadSize for a PUCCH resource set). In yet another example, the payload threshold may be a separate configured parameter. 
     In another approach, the coding method may be determined by the total payload size of the HARQ-ACK with or without SR for each priority. Thus, if the total number of bits of high priority HARQ-ACK with or without SR and low priority HARQ-ACK with or without SR is less than or equal to a threshold, joint coding is used. Otherwise, if the number of bits of high priority HARQ-ACK with or without SR and low priority HARQ-ACK low priority with or without SR is greater than a threshold, separate coding is used. In an example, the payload threshold may be a fixed value (e.g., 11 bits). In another example, the payload threshold may be an existing configured value (e.g., the N 2  or N 3  of the maxPayloadSize for a PUCCH resource set). In yet another example, the payload threshold may be a separate configured parameter. 
     As a special case of this approach, the maximum payload size is 1706 bits. Thus, if the total number of bits of high priority HARQ-ACK with or without SR and low priority HARQ-ACK with or without SR is less than or equal to the maximum payload configured for the URLLC PUCCH resources, joint coding is used. Otherwise, separate coding is used. If the configured PUCCH resource for high priority cannot carry all UCI with separate coding, the low priority UCI may be dropped, and only the high priority UCI is transmitted. With this approach, the joint coding method is first evaluated to see if there is a PUCCH resource that can carry all UCI bits with the maximum coding rate for high priority UCI. If this is not possible, separate coding is then evaluated. 
     In a second approach (Approach 2), the coding method may be configured by higher layer signaling (e.g., RRC signaling). In this approach, the higher layer signaling (e.g., RRC signaling) may indicate if joint coding or separate coding is configured. Additionally, the higher layer signaling (e.g., RRC signaling) may configure a payload threshold so that joint coding is applied if the UCI payload is less than or equal to the threshold, and separate coding is applied if the payload is greater than the threshold. The payload threshold may be evaluated by the total UCI payload of HARQ-ACK with or without SR of all priorities. The payload threshold may be evaluated by the UCI payload of HARQ-ACK with or without SR of low priority only. 
     In a third approach (Approach 3), the coding method may be determined based on PUCCH resource configuration. In this approach, the PUCCH resource configuration for high priority HARQ-ACK may be configured with one or two maxCodeRate parameters. In the case of two maxCodeRate parameters, a first maxCodeRate has a smaller value and is applied on HARQ-ACK with or without SR with high priority, and a second maxCodeRate has a larger value and is applied on HARQ-ACK with or without SR with low priority. Thus, a UE  102  may be configured by one or two max-CodeRate, and/or one or two code rates for multiplexing HARQ-ACK with different priorities in a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4. If only one maxCodeRate is configured, joint coding may be used. If two maxCodeRate is configured, separate coding may be used. 
     The UE operations module  124  may provide information  148  to the one or more receivers  120 . For example, the UE operations module  124  may inform the receiver(s)  120  when to receive retransmissions. 
     The UE operations module  124  may provide information  138  to the demodulator  114 . For example, the UE operations module  124  may inform the demodulator  114  of a modulation pattern anticipated for transmissions from the gNB  160 . 
     The UE operations module  124  may provide information  136  to the decoder  108 . For example, the UE operations module  124  may inform the decoder  108  of an anticipated encoding for transmissions from the gNB  160 . 
     The UE operations module  124  may provide information  142  to the encoder  150 . The information  142  may include data to be encoded and/or instructions for encoding. For example, the UE operations module  124  may instruct the encoder  150  to encode transmission data  146  and/or other information  142 . The other information  142  may include PDSCH HARQ-ACK information. 
     The encoder  150  may encode transmission data  146  and/or other information  142  provided by the UE operations module  124 . For example, encoding the data  146  and/or other information  142  may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder  150  may provide encoded data  152  to the modulator  154 . 
     The UE operations module  124  may provide information  144  to the modulator  154 . For example, the UE operations module  124  may inform the modulator  154  of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB  160 . The modulator  154  may modulate the encoded data  152  to provide one or more modulated signals  156  to the one or more transmitters  158 . 
     The UE operations module  124  may provide information  140  to the one or more transmitters  158 . This information  140  may include instructions for the one or more transmitters  158 . For example, the UE operations module  124  may instruct the one or more transmitters  158  when to transmit a signal to the gNB  160 . For instance, the one or more transmitters  158  may transmit during a UL subframe. The one or more transmitters  158  may upconvert and transmit the modulated signal(s)  156  to one or more gNBs  160 . 
     Each of the one or more gNBs  160  may include one or more transceivers  176 , one or more demodulators  172 , one or more decoders  166 , one or more encoders  109 , one or more modulators  113 , a data buffer  162 , and a gNB operations module  182 . For example, one or more reception and/or transmission paths may be implemented in a gNB  160 . For convenience, only a single transceiver  176 , decoder  166 , demodulator  172 , encoder  109 , and modulator  113  are illustrated in the gNB  160 , though multiple parallel elements (e.g., transceivers  176 , decoders  166 , demodulators  172 , encoders  109 , and modulators  113 ) may be implemented. 
     The transceiver  176  may include one or more receivers  178  and one or more transmitters  117 . The one or more receivers  178  may receive signals from the UE  102  using one or more antennas  180   a - n.  For example, the receiver  178  may receive and downconvert signals to produce one or more received signals  174 . The one or more received signals  174  may be provided to a demodulator  172 . The one or more transmitters  117  may transmit signals to the UE  102  using one or more antennas  180   a - n.  For example, the one or more transmitters  117  may upconvert and transmit one or more modulated signals  115 . 
     The demodulator  172  may demodulate the one or more received signals  174  to produce one or more demodulated signals  170 . The one or more demodulated signals  170  may be provided to the decoder  166 . The gNB  160  may use the decoder  166  to decode signals. The decoder  166  may produce one or more decoded signals  164 ,  168 . For example, a first eNB-decoded signal  164  may comprise received payload data, which may be stored in a data buffer  162 . A second eNB-decoded signal  168  may comprise overhead data and/or control data. For example, the second eNB decoded signal  168  may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module  182  to perform one or more operations. 
     In general, the gNB operations module  182  may enable the gNB  160  to communicate with the one or more UEs  102 . The gNB operations module  182  may include a gNB scheduling module  194 . The gNB scheduling module  194  may perform operations for PUCCH repetition as described herein. 
     The gNB operations module  182  may provide information  188  to the demodulator  172 . For example, the gNB operations module  182  may inform the demodulator  172  of a modulation pattern anticipated for transmissions from the UE(s)  102 . 
     The gNB operations module  182  may provide information  186  to the decoder  166 . For example, the gNB operations module  182  may inform the decoder  166  of an anticipated encoding for transmissions from the UE(s)  102 . 
     The gNB operations module  182  may provide information  101  to the encoder  109 . The information  101  may include data to be encoded and/or instructions for encoding. For example, the gNB operations module  182  may instruct the encoder  109  to encode information  101 , including transmission data  105 . 
     The encoder  109  may encode transmission data  105  and/or other information included in the information  101  provided by the gNB operations module  182 . For example, encoding the data  105  and/or other information included in the information  101  may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder  109  may provide encoded data  111  to the modulator  113 . The transmission data  105  may include network data to be relayed to the UE  102 . 
     The gNB operations module  182  may provide information  103  to the modulator  113 . This information  103  may include instructions for the modulator  113 . For example, the gNB operations module  182  may inform the modulator  113  of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s)  102 . The modulator  113  may modulate the encoded data  111  to provide one or more modulated signals  115  to the one or more transmitters  117 . 
     The gNB operations module  182  may provide information  192  to the one or more transmitters  117 . This information  192  may include instructions for the one or more transmitters  117 . For example, the gNB operations module  182  may instruct the one or more transmitters  117  when to (or when not to) transmit a signal to the UE(s)  102 . The one or more transmitters  117  may upconvert and transmit the modulated signal(s)  115  to one or more UEs  102 . 
     It should be noted that a DL subframe may be transmitted from the gNB  160  to one or more UEs  102  and that a UL subframe may be transmitted from one or more UEs  102  to the gNB  160 . Furthermore, both the gNB  160  and the one or more UEs  102  may transmit data in a standard special subframe. 
     It should also be noted that one or more of the elements or parts thereof included in the eNB(s)  160  and UE(s)  102  may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.
           FIG.  2    illustrates examples of low priority channel dropping timelines. In these examples, a high priority PDSCH  203  may follow a PDCCH  201 . The PDSCH processing time  209  (referred to as T proc,1 ) may be N1 symbols. Extra symbols  211  (referred to as d 1,1 ) may be for delay for collision handling and channel dropping. The HARQ-ACK timing  213  for the PUCCH  207  for the HARQ-ACK corresponding to the high priority PDSCH  203  is also shown.   In example (a), if the starting symbol of the low priority channel  205   a  is not earlier than T proc,1  plus d 1,1  symbols after the end of last transmission of the high priority PDSCH  203 , the low priority channel  205   a  can be frilly dropped. Value d 1,1  (i.e., the extra symbols  211 ) may be the time duration corresponding to 0,1,2 symbols reported by UE capability.   In example (b), the low priority PUCCH for eMBB HARQ-ACK transmission is already started when the UE realizes the high priority PUCCH  207  for high priority HARQ-ACK should be scheduled. The low priority channel  205   b  can be dropped from T proc,1  plus d 1,1  symbols after the end of last transmission of the high priority PDSCH  203 .     FIG.  3    illustrates an example of a high priority channel processing delay due to channel collision and channel dropping. In this example, a high priority PDSCH  303  may follow a PDCCH  301 . The basic PDSCH processing time  309  (referred to as T proc,1 ) may be N1 symbols. Extra symbols  311  (referred to as a dropping delay d 1,1 ) may be for delay for collision handling and channel dropping. The HARQ-ACK timing  313  for the PUCCH  307  for the HARQ-ACK corresponding to the high priority PDSCH  303  is also shown.   A low priority channel  305   a  that starts T proc,1  plus d 1,1  symbols after the end of last transmission of the high priority PDSCH  303  can be fully dropped, as described in  FIG.  2   . The low priority channel  305   b  can be dropped from T proc,1  plus d 1,1  symbols after the end of last transmission of the high priority PDSCH  303 , as described in  FIG.  2   .   In one method, the extra delay  315  (referred to as d 1,2 ) may be applied jointly with the dropping delay (d 1,1 )  311 , where value d 1,1  and d 1,2  are the time durations corresponding to 0,1,2 reported by UE capability. Therefore, the total delay for the PUCCH  307  for the HARQ-ACK for the high priority PDSCH  303  is defined by d 1,1 +d 1,2 . In other words, in this method, the processing timeline requirement for a PDSCH  303  is extended by a total of d 1,1 +d 1,2  symbols.     FIG.  4    illustrates another example of a high priority channel processing delay due to channel collision and channel dropping. In this example, a high priority PDSCH  403  may follow a PDCCH  401 . The basic PDSCH processing time  409  (referred to as T proc,1 ) may be N1 symbols. Extra symbols  411  (referred to as a dropping delay d 1,1 ) may be for delay for collision handling and channel dropping. The HARQ-ACK timing  413  for the PUCCH  407  for the HARQ-ACK corresponding to the high priority PDSCH  403  is also shown.   A low priority channel  405   a  that starts T proc,1  plus d 1,1  symbols after the end of last transmission of the high priority PDSCH  403  can be fully dropped, as described in  FIG.  2   . The low priority channel  405   b  can be dropped from T proc,1  plus d 1,1  symbols after the end of last transmission of the high priority PDSCH  403 , as described in  FIG.  2   .   In this method, the extra delay  415  (referred to as d 1,2 ) may be applied independent of the dropping delay (d 1,1 )  411 . In this case d 1,2 ≥d 1,1 . Therefore, the processing timeline requirement for a PDSCH  403  is extended by d 1,2  symbols.       

       FIG.  5    is a block diagram illustrating one implementation of a gNB  560 . The gNB  560  may be implemented in accordance with the gNB  160  described in connection with  FIG.  1    in some examples, and/or may perform one or more of the functions described herein. The gNB  560  may include a higher layer processor  523 , a DL transmitter  525 , a UL receiver  533 , and one or more antenna  531 . The DL transmitter  525  may include a PDCCH transmitter  527  and a PDSCH transmitter  529 . The UL receiver  533  may include a PUCCH receiver  535  and a PUSCH receiver  537 . 
     The higher layer processor  523  may manage physical layer&#39;s behaviors (the DL transmitter&#39;s and the UL receiver&#39;s behaviors) and provide higher layer parameters to the physical layer. The higher layer processor  523  may obtain transport blocks from the physical layer. The higher layer processor  523  may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE&#39;s higher layer. The higher layer processor  523  may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks. 
     The DL transmitter  525  may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas  531 . The UL receiver  533  may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas  531  and de-multiplex them. The PUCCH receiver  535  may provide the higher layer processor  523  UCI. The PUSCH receiver  537  may provide the higher layer processor  523  received transport blocks. 
       FIG.  6    is a block diagram illustrating one implementation of a UE  602 . The UE  602  may be implemented in accordance with the UE  102  described in connection with  FIG.  1    in some examples, and/or may perform one or more of the functions described herein. The UE  602  may include a higher layer processor  623 , a UL transmitter  651 , a DL receiver  643 , and one or more antenna  631 . The UL transmitter  651  may include a PUCCH transmitter  653  and a PUSCH transmitter  655 . The DL receiver  643  may include a PDCCH receiver  645  and a PDSCH receiver  647 . 
     The higher layer processor  623  may manage physical layer&#39;s behaviors (the UL transmitter&#39;s and the DL receiver&#39;s behaviors) and provide higher layer parameters to the physical layer. The higher layer processor  623  may obtain transport blocks from the physical layer. The higher layer processor  623  may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE&#39;s higher layer. The higher layer processor  623  may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter  653  UCI. 
     The DL receiver  643  may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas  631  and de-multiplex them. The PDCCH receiver  645  may provide the higher layer processor  623  DCI. The PDSCH receiver  647  may provide the higher layer processor  623  received transport blocks. 
     It should be noted that names of physical channels described herein are examples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH”, “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or the like can be used. 
       FIG.  7    illustrates various components that may be utilized in a UE  702 . The UE  702  described in connection with  FIG.  7    may be implemented in accordance with the UE  102  described in connection with  FIG.  1   . The UE  702  includes a processor  703  that controls operation of the UE  702 . The processor  703  may also be referred to as a central processing unit (CPU). Memory  705 , which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions  707   a  and data  709   a  to the processor  703 . A portion of the memory  705  may also include non-volatile random-access memory (NVRAM). Instructions  707   b  and data  709   b  may also reside in the processor  703 . Instructions  707   b  and/or data  709   b  loaded into the processor  703  may also include instructions  707   a  and/or data  709   a  from memory  705  that were loaded for execution or processing by the processor  703 . The instructions  707   b  may be executed by the processor  703  to implement the methods described above. 
     The UE  702  may also include a housing that contains one or more transmitters  758  and one or more receivers  720  to allow transmission and reception of data. The transmitter(s)  758  and receiver(s)  720  may be combined into one or more transceivers  718 . One or more antennas  722   a - n  are attached to the housing and electrically coupled to the transceiver  718 . 
     The various components of the UE  702  are coupled together by a bus system  711 , which may include a power bus, a control signal bus, and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in  FIG.  7    as the bus system  711 . The UE  702  may also include a digital signal processor (DSP)  713  for use in processing signals. The UE  702  may also include a communications interface  715  that provides user access to the functions of the UE  702 . The UE  702  illustrated in  FIG.  7    is a functional block diagram rather than a listing of specific components. 
       FIG.  8    illustrates various components that may be utilized in a gNB  860 . The gNB  860  described in connection with  FIG.  8    may be implemented in accordance with the gNB  160  described in connection with  FIG.  1   . The gNB  860  includes a processor  803  that controls operation of the gNB  860 . The processor  803  may also be referred to as a central processing unit (CPU). Memory  805 , which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions  807   a  and data  809   a  to the processor  803 . A portion of the memory  805  may also include non-volatile random-access memory (NVRAM). Instructions  807   b  and data  809   b  may also reside in the processor  803 . Instructions  807   b  and/or data  809   b  loaded into the processor  803  may also include instructions  807   a  and/or data  809   a  from memory  805  that were loaded for execution or processing by the processor  803 . The instructions  807   b  may be executed by the processor  803  to implement the methods described above. 
     The gNB  860  may also include a housing that contains one or more transmitters  817  and one or more receivers  878  to allow transmission and reception of data. The transmitter(s)  817  and receiver(s)  878  may be combined into one or more transceivers  876 . One or more antennas  880   a - n  are attached to the housing and electrically coupled to the transceiver  876 . 
     The various components of the gNB  860  are coupled together by a bus system  811 , which may include a power bus, a control signal bus, and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in  FIG.  8    as the bus system  811 . The gNB  860  may also include a digital signal processor (DSP)  813  for use in processing signals. The gNB  860  may also include a communications interface  815  that provides user access to the functions of the gNB  860 . The gNB  860  illustrated in  FIG.  8    is a functional block diagram rather than a listing of specific components. 
       FIG.  9    is a block diagram illustrating one implementation of a UE  902  in which the systems and methods described herein may be implemented. The UE  902  includes transmit means  958 , receive means  920  and control means  924 . The transmit means  958 , receive means  920  and control means  924  may be configured to perform one or more of the functions described in connection with  FIG.  1    above.  FIG.  7    above illustrates one example of a concrete apparatus structure of  FIG.  9   . Other various structures may be implemented to realize one or more of the functions of  FIG.  1   . For example, a DSP may be realized by software. 
       FIG.  10    is a block diagram illustrating one implementation of a gNB  1060  in which the systems and methods described herein may be implemented. The gNB  1060  includes transmit means  1023 , receive means  1078  and control means  1082 . The transmit means  1023 , receive means  1078  and control means  1082  may be configured to perform one or more of the functions described in connection with  FIG.  1    above.  FIG.  8    above illustrates one example of a concrete apparatus structure of  FIG.  10   . Other various structures may be implemented to realize one or more of the functions of  FIG.  1   . For example, a DSP may be realized by software. 
       FIG.  11    is a flow diagram illustrating a method  1100  for multiplexing of HARQ-ACK with different priorities on a single PUCCH. In an example, the method  1100  may be implemented by a UE  102 . 
     The UE  102  may determine  1102  that PUCCH collision occurs between PUCCH with high priority HARQ-ACK and PUCCH with low priority HARQ-ACK. The UE  102  may determine  1104  whether HARQ-ACK multiplexing between different priorities is configured and enabled. If HARQ-ACK multiplexing between different priorities is not configured and/or enabled, then the UE  102  may drop  1106  the PUCCH with low priority HARQ-ACK following the channel dropping timeline. The PUCCH with high priority HARQ-ACK may be transmitted subject to the processing delay timeline. 
     If the UE  102  determines  1104  that HARQ-ACK multiplexing between different priorities is configured and enabled, then the UE  102  may determine  1108  whether the low priority PUCCH can be fully dropped based on the channel dropping timeline. If the low priority PUCCH cannot be fully dropped based on the channel dropping timeline, then the UE  102  may drop  1106  the PUCCH with low priority HARQ-ACK following the channel dropping timeline and transmit the PUCCH with high priority HARQ-ACK subject to the processing delay timeline. 
     If the UE  102  determines  1108  that the low priority PUCCH can be fully dropped based on the channel dropping timeline, then the UE  102  may determine  1110  whether the PUCCH resource supports joint HARQ-ACK reporting, and UCI multiplexing delay timeline is satisfied for PUCCH with joint HARQ-ACK. If the PUCCH resource does not support joint HARQ-ACK reporting, and/or UCI multiplexing delay timeline is not satisfied for PUCCH with joint HARQ-ACK, then the UE  102  may drop  1106  the PUCCH with low priority HARQ-ACK following the channel dropping timeline and transmit the PUCCH with high priority HARQ-ACK subject to the processing delay timeline. 
     If the UE  102  determines  1110  that the PUCCH resource supports joint HARQ-ACK reporting, and UCI multiplexing delay timeline is satisfied for PUCCH with joint HARQ-ACK, then the UE  102  may multiplex  1112  the HARQ-ACK on a PUCCH configured for high priority HARQ-ACK.
         The term “computer-readable medium” refers to any available medium that can be accessed by a computer or a processor. The term “computer-readable medium,” as used herein, may denote a computer- and/or processor-readable medium that is non-transitory and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.       

     It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc. 
     Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims. 
     It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes, and variations may be made in the arrangement, operation, and details of the systems, methods, and apparatus described herein without departing from the scope of the claims. 
     A program running on the gNB  160  or the UE  102  according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD, and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk, and the like), and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described above is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program. 
     Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB  160  and the UE  102  according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB  160  and the UE  102  may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies. 
     Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned implementations may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a micro-controller, or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used. 
     As used herein, the term “and/or” should be interpreted to mean one or more items. For example, the phrase “A, B, and/or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase “at least one of” should be interpreted to mean one or more items. For example, the phrase “at least one of A, B and C” or the phrase “at least one of A, B or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase “one or more of” should be interpreted to mean one or more items. For example, the phrase “one or more of A, B and C” or the phrase “one or more of A, B or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. 
     In one example, a user equipment (UE), comprising: a processor configured to: determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on higher layer signaling, an uplink control information (UCI) payload size or PUCCH resource configuration, multiplex the HARQ-ACK based on the determined coding method; and transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH. 
     In one example, the UE, wherein the coding method comprises joint coding, and wherein HARQ-ACK bits of different priorities are concatenated into a single codebook, joint coded and transmitted on a ultra-reliable low-latency communication (URLLC) PUCCH resource. 
     In one example, the UE, wherein the coding method comprises separate coding, wherein a HARQ-ACK codebook of URLLC and eMBB are coded and rate matched independently based on a maximum coding rate of a URLLC PUCCH configuration and an eMBB PUCCH configuration, and wherein rate matched outputs are concatenated together and transmitted on a selected URLLC PUCCH resource. 
     In one example, the UE, wherein joint coding is used if a HARQ-ACK codebook is less than or equal to a number of bits. 
     In one example, the UE, wherein joint coding is used if a number of HARQ-ACK bits is less than or equal to a threshold. 
     In one example, the UE, wherein the coding method is configured by RRC signaling. 
     In one example, the UE, wherein the coding method is based on a number of configured code rates for multiplexing HARQ-ACK. 
     In one example, a base station (gNB), comprising: a processor configured to: determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on higher layer signaling, an uplink control information (UCI) payload size or PUCCH resource configuration; and receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
     In one example, the gNB, wherein the coding method comprises joint coding, and wherein HARQ-ACK bits of different priorities are concatenated into a single codebook, joint coded and transmitted on a ultra-reliable low-latency communication (URLLC) PUCCH resource. 
     In one example, the gNB, wherein the coding method comprises separate coding, wherein a HARQ-ACK codebook of URLLC and eMBB are coded and rate matched independently based on a maximum coding rate of a URLLC PUCCH configuration and an eMBB PUCCH configuration, and wherein rate matched outputs are concatenated together and transmitted on a selected URLLC PUCCH resource. 
     In one example, the gNB, wherein joint coding is used if a HARQ-ACK codebook is less than or equal to a number of bits. 
     In one example, the gNB, wherein joint coding is used if a number of HARQ-ACK bits is less than or equal to a threshold. 
     In one example, the gNB, wherein the coding method is configured by RRC signaling. 
     In one example, the gNB, wherein the coding method is based on a number of configured code rates for multiplexing HARQ-ACK. 
     In one example, a method by a user equipment (UE), comprising: determining a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on higher layer signaling, an uplink control information (UCI) payload size or PUCCH resource configuration, multiplexing the HARQ-ACK based on the determined coding method; and transmitting the multiplexed HARQ-ACK on the PUCCH. 
     In one example, a method by a base station (gNB), comprising: determining a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on higher layer signaling, an uplink control information (UCI) payload size or PUCCH resource configuration; and receiving multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
     In one example, a user equipment (UE), comprising: a processor configured to: determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size, multiplex the HARQ-ACK based on the determined coding method; and transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH. 
     In one example, the UE, wherein the coding method comprises joint coding, and wherein HARQ-ACK bits of different priorities are concatenated into a single codebook, joint coded and transmitted on a high priority PUCCH resource. 
     In one example, the UE, wherein the coding method comprises separate coding, wherein a high priority HARQ-ACK codebook and a low priority HARQ-ACK codebook are coded and rate matched independently based on a maximum coding rate of a high priority PUCCH configuration and a low priority PUCCH configuration respectively, and wherein rate matched outputs are concatenated together and transmitted on a selected high priority PUCCH resource. 
     In one example, the UE, wherein joint coding is used if the total number of bits of the high priority HARQ-ACK codebook and the low priority HARQ-ACK codebook is less than or equal to a threshold of a fixed number of bits. 
     In one example, a base station (gNB), comprising: a processor configured to: determine a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size; and receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
     In one example, the gNB, wherein the coding method comprises joint coding, and wherein HARQ-ACK bits of different priorities are concatenated into a single codebook, joint coded and transmitted on a high priority PUCCH resource. 
     In one example, the gNB, wherein the coding method comprises separate coding, wherein a high priority HARQ-ACK codebook and a low priority HARQ-ACK codebook are coded and rate matched independently based on a maximum coding rate of a high priority PUCCH configuration and a low priority PUCCH configuration respectively, and wherein rate matched outputs are concatenated together and transmitted on a selected high priority PUCCH resource. 
     In one example, the gNB, wherein joint coding is used if the total number of bits of the high priority HARQ-ACK codebook and the low priority HARQ-ACK codebook is less than or equal to a threshold of a fixed number of bits. 
     In one example, a method by a user equipment (UE), comprising: determining a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size, multiplexing the HARQ-ACK based on the determined coding method; and transmitting the multiplexed HARQ-ACK on the PUCCH. 
     In one example, a method by a base station (gNB), comprising: determining a coding method for multiplexing hybrid automatic repeat request-acknowledgement (HARQ-ACK) with different priorities on a physical uplink control channel (PUCCH), the coding method being determined based on an uplink control information (UCI) payload size; and receiving multiplexed HARQ-ACK on the PUCCH, the HARQ-ACK being multiplexed based on the determined coding method. 
     CROSS REFERENCE 
     This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 63/049,929 on Jul. 9, 2020, the entire contents of which are hereby incorporated by reference.