SIGNALING AND TIMELINE REQUIREMENTS FOR MULTIPLEXING BETWEEN HARQ-ACK CODEBOOKS WITH DIFFERENT PRIORITIES

A user equipment (UE) is described. The UE includes a processor configured to determine uplink control information (UCI) multiplexing on a single physical uplink control channel (PUCCH) when a low priority PUCCH carrying a hybrid automatic repeat request-acknowledgement (HARQ-ACK) collides with a high priority PUCCH carrying a HARQ-ACK. The processor is also configured to determine a processing timeline for the UCI multiplexing. The UE also includes transmitting circuitry configured to transmit the UCI multiplexing on the single PUCCH based on the processing timeline.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. More specifically, the present disclosure relates to signaling and timeline requirements for multiplexing between HARQ-ACK codebooks with different priorities.

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 uplink control information (UCI) multiplexing on a single physical uplink control channel (PUCCH) when a low priority PUCCH carrying a hybrid automatic repeat request-acknowledgement (HARQ-ACK) collides with a high priority PUCCH carrying a HARQ-ACK, and determine a processing timeline for the UCI multiplexing; and transmitting circuitry configured to transmit the UCI multiplexing on the single PUCCH based on the processing timeline.

In one example, a base station (gNB), comprising: a processor configured to: determine uplink control information (UCI) multiplexing on a single physical uplink control channel (PUCCH) when a low priority PUCCH carrying a hybrid automatic repeat request-acknowledgement (HARQ-ACK) collides with a high priority PUCCH carrying a HARQ-ACK, and determine a processing timeline for the UCI multiplexing; and receiving circuitry configured to receive the UCI multiplexing on the single PUCCH based on the processing timeline.

In one example, a method by a user equipment (UE), comprising: determining uplink control information (UCI) multiplexing on a single physical uplink control channel (PUCCH) when a low priority PUCCH carrying a hybrid automatic repeat request-acknowledgement (HARQ-ACK) collides with a high priority PUCCH carrying a HARQ-ACK; determining a processing timeline for the UCI multiplexing; and transmitting the UCI multiplexing on the single PUCCH based on the processing timeline.

In one example, a method by a base station (gNB), comprising: determining uplink control information (UCI) multiplexing on a single physical uplink control channel (PUCCH) when a low priority PUCCH carrying a hybrid automatic repeat request-acknowledgement (HARQ-ACK) collides with a high priority PUCCH carrying a HARQ-ACK; determining a processing timeline for the UCI multiplexing; and receiving the UCI multiplexing on the single PUCCH based on the processing timeline.

DESCRIPTION OF EMBODIMENTS

A user equipment (UE) is described. The UE includes a processor configured to determine uplink control information (UCI) multiplexing on a single physical uplink control channel (PUCCH) when a low priority PUCCH carrying a hybrid automatic repeat request-acknowledgement (HARQ-ACK) collides with a high priority PUCCH carrying a HARQ-ACK. The processor is also configured to determine a processing timeline for the UCI multiplexing. The UE also includes transmitting circuitry configured to transmit the UCI multiplexing on the single PUCCH based on the processing timeline.

A HARQ-ACK report mode may be configured to support joint HARQ-ACK reporting between different HARQ-ACK codebooks with different priorities. RRC parameters may be configured to allow different HARQ-ACK codebook multiplexing on a single PUCCH.

The processing timeline may allow extra processing time of potential multiplexing of HARQ-ACK codebooks with different priorities. In one approach, a UCI multiplexing delay parameter d1,3is applied jointly with a channel dropping timeline d1,1and a processing delay d1,2. In another approach, the UCI multiplexing delay parameter d1,3is applied independently from a channel dropping timeline d1,1and a processing delay d1,2. In another approach, the UCI multiplexing delay parameter d1,3is applied jointly with a channel dropping timeline d1,1, but independently form a processing delay d1,2. In yet another approach, the UCI multiplexing delay parameter d1,3is the same as a processing delay d1,2, so that only one delay parameter is used for the processing timeline.

The HARQ-ACK of different priorities may be multiplexed and transmitted on a PUCCH configured for high priority HARQ-ACK if the PUCCH for low priority HARQ-ACK can be fully dropped, and the UCI multiplexing timeline can be satisfied, and the PUCCH can support multiplexed HARQ-ACK bits.

A base station (gNB) is also described. The gNB includes a processor configured to determine UCI multiplexing on a single PUCCH when a low priority PUCCH carrying a HARQ-ACK collides with a high priority PUCCH carrying a HARQ-ACK. The processor is also configured to determine a processing timeline for the UCI multiplexing. The gNB also includes receiving circuitry configured to receive the UCI multiplexing on the single PUCCH based on the processing timeline.

A method by a UE is also described. The method includes determining UCI multiplexing on a single PUCCH when a low priority PUCCH carrying a HARQ-ACK collides with a high priority PUCCH carrying a HARQ-ACK. The method also includes determining a processing timeline for the UCI multiplexing. The method further includes transmitting the UCI multiplexing on the single PUCCH based on the processing timeline.

A method by a gNB is also described. The method includes determining UCI multiplexing on a single PUCCH when a low priority PUCCH carrying a HARQ-ACK collides with a high priority PUCCH carrying a HARQ-ACK. The method also includes determining a processing timeline for the UCI multiplexing. The method further includes receiving the UCI multiplexing on the single PUCCH based on the processing timeline.

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 interchangeably 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 EUTRAN 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.

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.

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.1is a block diagram illustrating one implementation of one or more gNBs160and one or more UEs102in 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 UEs102communicate with one or more gNBs160using one or more antennas122a-n. For example, a UE102transmits electromagnetic signals to the gNB160and receives electromagnetic signals from the gNB160using the one or more antennas122a-n. The gNB160communicates with the UE102using one or more antennas180a-n.

The UE102and the gNB160may use one or more channels119,121to communicate with each other. For example, a UE102may transmit information or data to the gNB160using one or more uplink channels121. Examples of uplink channels121include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channels121(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 channels121may 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 gNBs160may also transmit information or data to the one or more UEs102using one or more downlink channels119, for instance. Examples of downlink channels119include 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 UEs102may include one or more transceivers118, one or more demodulators114, one or more decoders108, one or more encoders150, one or more modulators154, a data buffer104, and a UE operations module124. For example, one or more reception and/or transmission paths may be implemented in the UE102. For convenience, only a single transceiver118, decoder108, demodulator114, encoder150, and modulator154are illustrated in the UE102, though multiple parallel elements (e.g., transceivers118, decoders108, demodulators114, encoders150, and modulators154) may be implemented.

The transceiver118may include one or more receivers120and one or more transmitters158. The one or more receivers120may receive signals from the gNB160using one or more antennas122a-n. For example, the receiver120may receive and downconvert signals to produce one or more received signals116. The one or more received signals116may be provided to a demodulator114. The one or more transmitters158may transmit signals to the gNB160using one or more antennas122a-n. For example, the one or more transmitters158may upconvert and transmit one or more modulated signals156.

The demodulator114may demodulate the one or more received signals116to produce one or more demodulated signals112. The one or more demodulated signals112may be provided to the decoder108. The UE102may use the decoder108to decode signals. The decoder108may produce decoded signals110, which may include a UE-decoded signal106(also referred to as a first UE-decoded signal106). For example, the first UE-decoded signal106may comprise received payload data, which may be stored in a data buffer104. Another signal included in the decoded signals110(also referred to as a second UE-decoded signal110) may comprise overhead data and/or control data. For example, the second UE decoded signal110may provide data that may be used by the UE operations module124to perform one or more operations.

In general, the UE operations module124may enable the UE102to communicate with the one or more gNBs160. The UE operations module124may include a UE scheduling module126. In some examples, the UE scheduling module126may 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 Tproc,2+d1after the end of PDCCH scheduling the high-priority transmission. In this case, Tproc,2is the UE processing time capability for the carrier. Value d1is the time duration corresponding to 0,1,2 symbols reported by UE capability. It should be noted that d2,1=0 is for cancellation. The minimum processing time of the high priority channel may be extended by d2symbols, where d2is 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 Tproc,1correspond 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 Tproc,1plus d1,1symbols 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 Tproc,1plus d1,1symbols after the end of last high priority PDSCH transmission, the low priority channel can be fully dropped, as shown inFIG.2(a). Value d1,1may 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 Tproc,1plus d1,1symbols after the end of last high priority PDSCH transmission, as shown inFIG.2(b).

Thus; for a PDSCH scheduled by a DCI, the UE may drop the low priority UL channel from a first symbol S0of the low priority UL low priority UL channel (e.g., PUCCH or PUSCH), where S0is not before a symbol with CP starting after Tproc,1dropafter a last symbol of any corresponding PDSCH, Tproc,1dropis given by the maximum of {Tproc,1drop,1, . . . , Tproc,1drop,i. . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH for high priority HARQ-ACK, Tproc,1drop,i=(N1+d1,1+1)·(2048+144)·κ·2−μ·TC, d1,1is selected for the i-th PDSCH following TS 38.214, N1is 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 S0of the low priority UL low priority UL channel (PUCCH or PUSCH), where S0is not before a symbol with CP starting after Tproc,1dropafter the last symbol of any DCI scheduling the corresponding PDSCH, Tproc,1dropis given by maximum of {Tproc,1drop,1, . . . , Tproc,1drop,i. . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH for high priority HARQ-ACK, Tproc,1drop,i=(N1+d1,1+1)·(2048+144)·κ·2−μ·TC, d1,1is selected for the i-th PDSCH following TS 38.214, N1is 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 d1,1symbols after the end of PDSCH transmission of a SPS release, where value d1,1may 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 S0of the low priority UL low priority UL channel (PUCCH or PUSCH), where S0is not before a symbol with CP starting after Tproc,releasedropafter a last symbol of any corresponding SPS PDSCH release. Tproc,releasedropis given by maximum of {Tproc,releasedrop,1, . . . , Tproc,releasedrop,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, Tproc,releasedrop,i=(N+1+d1,1)·(2048+144)·κ·2−μ·TC, 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 TIE may drop the low priority UL channel from a first symbol S0of the low priority UL low priority UL channel (PUCCH or PUSCH), where S0is not before a symbol with CP starting after Tproc,releasedropafter a last symbol of any corresponding SPS PDSCH release. Tproc,releasedropis given by maximum of {Tproc,releasedrop,1, . . . , Tproc,releasedrop,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, Tproc,releasedrop,i=(N+1)·(2048+144)·κ·2−μ·TC, 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 d1,2symbols, where value d1,2is 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 d1,2may be applied jointly with the dropping delay d1,1, where value d1,2and d1,2are the time durations corresponding to 0,1,2 reported by UE capability.

For a PDSCH scheduled by a DCI, S0is not before a symbol with CP starting after Tproc,1delayafter a last symbol of any corresponding PDSCH, Tproc,1delayis given by maximum of {Tproc,1delay,1, . . . , Tproc,1delay,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, Tproc,1delay,i=(N1+d1,1+d1,2+1)·(2048+144)·κ·2−μ·TC, d1,1and d1,2are selected for the i-th PDSCH, N1is 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 d1,1+d1,2symbols, as shown inFIG.3.

In another method, the extra delay d1,2may be applied independently from the dropping delay d1,1. In this case, the value of d1,2should be the same as or greater than the value d1,1, where value d1,2is the time duration corresponding to 0,1,2 or more symbols reported by UE capability. Thus, in this method, d1,2may be determined for the total delay required to perform collision resolution and channel dropping and be configured with a larger number than d1,1, For a PDSCH scheduled by a DCI, S0is not before a symbol with CP starting after Tproc,1delayafter a last symbol of any corresponding PDSCH, Tproc,1delayis given by maximum of {Tproc,1delay,1, . . . , Tproc,1delay,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, Tproc,1delay,i=(N1+d1,2+1)·(2048+144)·κ·2−μ·TC, d1,2is selected for the i-th PDSCH, N1is 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 d1,2symbols, as shown inFIG.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 d1,1symbols after the end of PDSCH transmission of a SPS release, and the extra delay d1,2may be applied jointly with the dropping delay d1,1, the S0is not before a symbol with CP starting after Tproc,releasedelayafter a last symbol of any corresponding SPS PDSCH release. Tproc,releasedelayis given by maximum of {Tproc,releasedelay,1, . . . , Tproc,releasedelay,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, Tproc,releasedelay,i=(N+1+d1,1+d1,2)·(2048+144)·κ·2−μ·TC, 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 d1,1+d1,2symbols.

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 d1,1symbols after the end of PDSCH transmission of a SPS release and if the extra delay d1,2may be applied independently from the dropping delay d1,1, S0is not before a symbol with CP starting after Tproc,releasedelayrelease after a last symbol of any corresponding SPS PDSCH release. Tproc,releasemuxis given by maximum of {Tproc,releasedelay,1, . . . , Tproc,releasedelay,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, Tproc,releasedelay,i=(N+1+d1,2)·(2048+144)·κ·2−μ·TC, 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., d1,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 (Method1), 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 ACKNACKFeedbackMode=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 ACKNACKFeedbackMode=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 (Method2), 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 simultaneousHARQ-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.11shows 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 d1,3symbols, where value d1,3is 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 d1,3symbols, where value d1,3is 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 S0of 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, d1,3is applied jointly with d1,1and d1,2. Thus, for a PDSCH scheduled by a DCI, S0is not before a symbol with CP starting after Tproc,1muxafter a last symbol of any corresponding PDSCH. Tproc,1muxis given by the maximum of {Tproc,1mux,1, . . . , Tproc,1mux,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, Tproc,1mux,i=(N1+d1,1+d1,2+d1,3+1)·(2048+144)·κ·2−μ·TC, d1,1, d1,2and d1,3are selected for the i-th PDSCH, N1is 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 d1,1+d1,2+d1,3symbols.

In another method, d1,3is applied separately from d1,1and d1,2. Furthermore, d1,3may be determined for the total delay required to perform UCI multiplexing and be configured with a larger number than d1,1and d1,2, and Tproc,1mux,i=(N1+d1,3+1)·(2048+144)·κ·2−μ·TCis determined based on d1,3only. Thus, for a PDSCH scheduled by a DCI, S0is not before a symbol with CP starting after Tproc,1muxafter a last symbol of any corresponding PDSCH. Tproc,1muxis given by the maximum of {Tproc,1mux,1, . . . , Tproc,1mux,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, Tproc,1mux,i=(N1+d1,3+1)·(2048+144)·κ·2−μ·TC, where d1,3is selected for the i-th PDSCH, N1is 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, d1,3is applied jointly with d1,1but separately from d1,2. Thus, for a PDSCH scheduled by a DCI, S0is not before a symbol with CP starting after Tproc,1muxafter a last symbol of any corresponding PDSCH. Tproc,1muxis given by the maximum of {Tproc,1mux,1, . . . , Tproc,1mux,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, Tproc,1mux,i=(N1+d1,1+d1,3+1)·(2048+144)·κ·2−μ·TC, d1,1and d1,3are selected for the i-th PDSCH, N1is 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 d1,1+d1,3symbols.

Similarly, for a high priority PDSCH by a SPS release, in one method, d1,3is applied jointly with d1,1and d1,2If the dropping timeline is determined based on the processing time of a PDSCH by a SPS release and plus d1,1symbols after the end of PDSCH transmission of a SPS release, and the extra delay d1,3may be applied jointly with the dropping delay d1,1and processing delay d1,2, S0is not before a symbol with CP starting after Tproc,releasemuxafter a last symbol of any corresponding SPS PDSCH release. Tproc,releasemuxis given by the maximum of {Tproc,releasemux,1, . . . , Tproc,releasemux,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, Tproc,releasemux,i=(N+1+d1,1+d1,2+d1,3)·(2048+144)·κ·2−μ·TC, where d1,1, proc,release and d1,3are 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, d1,3is applied separately from d1,1and d1,2. And d1,3may be determined for the total delay required to perform UCI multiplexing and be configured with a larger number than d1,1and d1,2. S0is not before a symbol with CP starting after Tproc,releasemuxafter a last symbol of any corresponding SPS PDSCH release. Tproc,releasemuxis given by maximum of {proc,releasemux,1, . . . , Tproc,releasemux,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, Tproc,releasemux,i=(N+1+d1,3)·(2048+144)·κ·2−μ·TC, where d1,3is 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, d1,3is applied jointly with d1,1but separately from d1,2. Thus, for a PDSCH scheduled by a DCI, S0is not before a symbol with CP starting after Tproc,releasemuxafter a last symbol of any corresponding SPS PDSCH release. Tproc,releasemuxis given by maximum of {Tproc,releasemux,1, . . . , Tproc,releasemux,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, Tproc,releasemux,i=(N+1++d1,1+d1,3)·(2048+144)·κ·2−μ·TC, where d1,3is selected proc,release 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 d1,3and processing delay d12can be the same. Thus, only d1,2or d1,3is 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 d1,1to the channel dropping, and UCI multiplexing timeline.

The UE operations module124may provide information148to the one or more receivers120. For example, the UE operations module124may inform the receiver(s)120when to receive retransmissions.

The UE operations module124may provide information138to the demodulator114. For example, the UE operations module124may inform the demodulator114of a modulation pattern anticipated for transmissions from the gNB160.

The UE operations module124may provide information136to the decoder108. For example, the UE operations module124may inform the decoder108of an anticipated encoding for transmissions from the gNB160.

The UE operations module124may provide information142to the encoder150. The information142may include data to be encoded and/or instructions for encoding. For example, the UE operations module124may instruct the encoder150to encode transmission data146and/or other information142. The other information142may include PDSCH HARQ-ACK information.

The encoder150may encode transmission data146and/or other information142provided by the UE operations module124. For example, encoding the data146and/or other information142may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder150may provide encoded data152to the modulator154.

The UE operations module124may provide information144to the modulator154. For example, the UE operations module124may inform the modulator154of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB160. The modulator154may modulate the encoded data152to provide one or more modulated signals156to the one or more transmitters158.

The UE operations module124may provide information140to the one or more transmitters158. This information140may include instructions for the one or more transmitters158. For example, the UE operations module124may instruct the one or more transmitters158when to transmit a signal to the gNB160. For instance, the one or more transmitters158may transmit during a UL subframe. The one or more transmitters158may upconvert and transmit the modulated signal(s)156to one or more gNBs160.

Each of the one or more gNBs160may include one or more transceivers176, one or more demodulators172, one or more decoders166, one or more encoders109, one or more modulators113, a data buffer162, and a gNB operations module182. For example, one or more reception and/or transmission paths may be implemented in a gNB160. For convenience, only a single transceiver176, decoder166, demodulator172, encoder109, and modulator113are illustrated in the gNB160, though multiple parallel elements (e.g., transceivers176, decoders166, demodulators172, encoders109, and modulators113) may be implemented.

The transceiver176may include one or more receivers178and one or more transmitters117. The one or more receivers178may receive signals from the UE102using one or more antennas180a-n. For example, the receiver178may receive and downconvert signals to produce one or more received signals174. The one or more received signals174may be provided to a demodulator172. The one or more transmitters117may transmit signals to the UE102using one or more antennas180a-n. For example, the one or more transmitters117may upconvert and transmit one or more modulated signals115.

The demodulator172may demodulate the one or more received signals174to produce one or more demodulated signals170. The one or more demodulated signals170may be provided to the decoder166. The gNB160may use the decoder166to decode signals. The decoder166may produce one or more decoded signals164,168. For example, a first eNB-decoded signal164may comprise received payload data, which may be stored in a data buffer162. A second eNB-decoded signal168may comprise overhead data and/or control data. For example, the second eNB decoded signal168may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module182to perform one or more operations.

In general, the gNB operations module182may enable the gNB160to communicate with the one or more UEs102. The gNB operations module182may include a gNB scheduling module194. The gNB scheduling module194may perform operations for PUCCH repetition as described herein.

The gNB operations module182may provide information188to the demodulator172. For example, the gNB operations module182may inform the demodulator172of a modulation pattern anticipated for transmissions from the UE(s)102.

The gNB operations module182may provide information186to the decoder166. For example, the gNB operations module182may inform the decoder166of an anticipated encoding for transmissions from the UE(s)102.

The gNB operations module182may provide information101to the encoder109. The information101may include data to be encoded and/or instructions for encoding. For example, the gNB operations module182may instruct the encoder109to encode information101, including transmission data105.

The encoder109may encode transmission data105and/or other information included in the information101provided by the gNB operations module182. For example, encoding the data105and/or other information included in the information101may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder109may provide encoded data111to the modulator113. The transmission data105may include network data to be relayed to the UE102.

The gNB operations module182may provide information103to the modulator113. This information103may include instructions for the modulator113. For example, the gNB operations module182may inform the modulator113of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s)102. The modulator113may modulate the encoded data111to provide one or more modulated signals115to the one or more transmitters117.

The gNB operations module182may provide information192to the one or more transmitters117. This information192may include instructions for the one or more transmitters117. For example, the gNB operations module182may instruct the one or more transmitters117when to (or when not to) transmit a signal to the UE(s)102. The one or more transmitters117may upconvert and transmit the modulated signal(s)115to one or more UEs102.

It should be noted that a DL subframe may be transmitted from the gNB160to one or more UEs102and that a UL subframe may be transmitted from one or more UEs102to the gNB160. Furthermore, both the gNB160and the one or more UEs102may 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)160and UE(s)102may 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.2illustrates examples of low priority channel dropping timelines. In these examples, a high priority PDSCH203may follow a PDCCH201. The PDSCH processing time209(referred to as Tproc,1) may be N1 symbols. Extra symbols211(referred to as d1,1) may be for delay for collision handling and channel dropping. The HARQ-ACK timing213for the PUCCH207for the HARQ-ACK corresponding to the high priority PDSCH203is also shown.

In example (a), if the starting symbol of the low priority channel205ais not earlier than Tproc,1plus d1,1symbols after the end of last transmission of the high priority PDSCH203, the low priority channel205acan be fully dropped. Value d1,1(i.e., the extra symbols211) 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 PUCCH207for high priority HARQ-ACK should be scheduled. The low priority channel205bcan be dropped from Tproc,1plus d1,1symbols after the end of last transmission of the high priority PDSCH203.

FIG.3illustrates an example of a high priority channel processing delay due to channel collision and channel dropping. In this example, a high priority PDSCH303may follow a PDCCH301. The basic PDSCH processing time309(referred to as Tproc,1) may be N1 symbols. Extra symbols311(referred to as a dropping delay d1,1) may be for delay for collision handling and channel dropping. The HARQ-ACK timing313for the PUCCH307for the HARQ-ACK corresponding to the high priority PDSCH303is also shown.

A low priority channel305athat starts Tproc,1plus d1,1symbols after the end of last transmission of the high priority PDSCH303can be fully dropped, as described inFIG.2. The low priority channel305bcan be dropped from Tproc,1plus d1,1symbols after the end of last transmission of the high priority PDSCH303, as described inFIG.2.

In one method, the extra delay315(referred to as d1,2) may be applied jointly with the dropping delay (d1,1)311, where value d1,1and d1,2are the time durations corresponding to 0,1,2 reported by UE capability. Therefore, the total delay for the PUCCH307for the HARQ-ACK for the high priority PDSCH303is defined by d1,1+d1,2. In other words, in this method, the processing timeline requirement for a PDSCH303is extended by a total of d1,1+d1,2symbols.

FIG.4illustrates another example of a high priority channel processing delay due to channel collision and channel dropping. In this example, a high priority PDSCH403may follow a PDCCH401. The basic PDSCH processing time409(referred to as Tproc,1) may be N1 symbols. Extra symbols411(referred to as a dropping delay d1,1) may be for delay for collision handling and channel dropping. The HARQ-ACK timing413for the PUCCH407for the HARQ-ACK corresponding to the high priority PDSCH403is also shown.

A low priority channel405athat starts Tproc,1plus d1,1symbols after the end of last transmission of the high priority PDSCH403can be fully dropped, as described inFIG.2. The low priority channel405bcan be dropped from Tproc,1plus d1,1symbols after the end of last transmission of the high priority PDSCH403, as described inFIG.2.

In this method, the extra delay415(referred to as d1,2) may be applied independent of the dropping delay (d1,1)411. In this case d1,2≥d1,1Therefore, the processing timeline requirement for a PDSCH403is extended by d1,2symbols.

FIG.5is a block diagram illustrating one implementation of a gNB560. The gNB560may be implemented in accordance with the gNB160described in connection withFIG.1in some examples, and/or may perform one or more of the functions described herein. The gNB560may include a higher layer processor523, a DL transmitter525, a UL receiver533, and one or more antenna531. The DL transmitter525may include a PDCCH transmitter527and a PDSCH transmitter529. The UL receiver533may include a PUCCH receiver535and a PUSCH receiver537.

The higher layer processor523may manage physical layer's behaviors (the DL transmitter's and the UL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor523may obtain transport blocks from the physical layer. The higher layer processor523may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor523may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.

The DL transmitter525may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas531. The UL receiver533may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas531and de-multiplex them. The PUCCH receiver535may provide the higher layer processor523UCI. The PUSCH receiver537may provide the higher layer processor523received transport blocks.

FIG.6is a block diagram illustrating one implementation of a UE602. The UE602may be implemented in accordance with the UE102described in connection withFIG.1in some examples, and/or may perform one or more of the functions described herein. The UE602may include a higher layer processor623, a UL transmitter651, a DL receiver643, and one or more antenna631. The UL transmitter651may include a PUCCH transmitter653and a PUSCH transmitter655. The DL receiver643may include a PDCCH receiver645and a PDSCH receiver647.

The higher layer processor623may manage physical layer's behaviors (the UL transmitter's and the DL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor623may obtain transport blocks from the physical layer. The higher layer processor623may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor623may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter653UCI.

The DL receiver643may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas631and de-multiplex them. The PDCCH receiver645may provide the higher layer processor623DCI. The PDSCH receiver647may provide the higher layer processor623received 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.7illustrates various components that may be utilized in a UE702. The UE702described in connection withFIG.7may be implemented in accordance with the UE102described in connection withFIG.1. The UE702includes a processor703that controls operation of the UE702. The processor703may also be referred to as a central processing unit (CPU). Memory705, 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 instructions707aand data709ato the processor703. A portion of the memory705may also include non-volatile random-access memory (NVRAM). Instructions707band data709bmay also reside in the processor703. Instructions707band/or data709bloaded into the processor703may also include instructions707aand/or data709afrom memory705that were loaded for execution or processing by the processor703. The instructions707bmay be executed by the processor703to implement the methods described above.

The UE702may also include a housing that contains one or more transmitters758and one or more receivers720to allow transmission and reception of data. The transmitter(s)758and receiver(s)720may be combined into one or more transceivers718. One or more antennas722a-nare attached to the housing and electrically coupled to the transceiver718.

The various components of the UE702are coupled together by a bus system711, 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 inFIG.7as the bus system711. The UE702may also include a digital signal processor (DSP)713for use in processing signals. The UE702may also include a communications interface715that provides user access to the functions of the UE702. The UE702illustrated inFIG.7is a functional block diagram rather than a listing of specific components.

FIG.8illustrates various components that may be utilized in a gNB860. The gNB860described in connection withFIG.8may be implemented in accordance with the gNB160described in connection withFIG.1. The gNB860includes a processor803that controls operation of the gNB860. The processor803may also be referred to as a central processing unit (CPU). Memory805, 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 instructions807aand data809ato the processor803. A portion of the memory805may also include non-volatile random-access memory (NVRAM). Instructions807band data809bmay also reside in the processor803. Instructions807band/or data809bloaded into the processor803may also include instructions807aand/or data809afrom memory805that were loaded for execution or processing by the processor803. The instructions807bmay be executed by the processor803to implement the methods described above.

The gNB860may also include a housing that contains one or more transmitters817and one or more receivers878to allow transmission and reception of data. The transmitter(s)817and receiver(s)878may be combined into one or more transceivers876. One or more antennas880a-nare attached to the housing and electrically coupled to the transceiver876.

The various components of the gNB860are coupled together by a bus system811, 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 inFIG.8as the bus system811. The gNB860may also include a digital signal processor (DSP)813for use in processing signals. The gNB860may also include a communications interface815that provides user access to the functions of the gNB860. The gNB860illustrated inFIG.8is a functional block diagram rather than a listing of specific components.

FIG.9is a block diagram illustrating one implementation of a UE902in which the systems and methods described herein may be implemented. The UE902includes transmit means958, receive means920and control means924. The transmit means958, receive means920and control means924may be configured to perform one or more of the functions described in connection withFIG.1above.FIG.7above illustrates one example of a concrete apparatus structure ofFIG.9. Other various structures may be implemented to realize one or more of the functions ofFIG.1. For example, a DSP may be realized by software.

FIG.10is a block diagram illustrating one implementation of a gNB1060in which the systems and methods described herein may be implemented. The gNB1060includes transmit means1023, receive means1078and control means1082. The transmit means1023, receive means1078and control means1082may be configured to perform one or more of the functions described in connection withFIG.1above.FIG.8above illustrates one example of a concrete apparatus structure ofFIG.10. Other various structures may be implemented to realize one or more of the functions ofFIG.1. For example, a DSP may be realized by software.

FIG.11is a flow diagram illustrating a method1100for multiplexing of HARQ-ACK with different priorities on a single PUCCH. In an example, the method1100may be implemented by a UE102.

The UE102may determine1102that PUCCH collision occurs between PUCCH with high priority HARQ-ACK and PUCCH with low priority HARQ-ACK. The UE102may determine1104whether 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 UE102may drop1106the 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 UE102determines1104that HARQ-ACK multiplexing between different priorities is configured and enabled, then the UE102may determine1108whether 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 UE102may drop1106the 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 UE102determines1108that the low priority PUCCH can be fully dropped based on the channel dropping timeline, then the UE102may determine1110whether 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 UE102may drop1106the 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 UE102determines1110that the PUCCH resource supports joint HARQ-ACK reporting, and UCI multiplexing delay timeline is satisfied for PUCCH with joint HARQ-ACK, then the UE102may multiplex1112the 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.

A program running on the gNB160or the UE102according 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 gNB160and the UE102according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB160and the UE102may 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.

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.

CROSS REFERENCE

This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 62,975,917 on Feb. 13, 2020, the entire contents of which are hereby incorporated by reference.