PUCCH collision handling for multi-slot long PUCCH in 5G NR

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a first parameter. The receiving circuit is also configured to receive a second parameter. The UE also includes a transmission circuit, which is configured to perform the first PUCCH repetition in a first plurality of time slots based on the first parameter. The transmission circuit is also configured to perform the second PUCCH repetition in a second plurality of time slots based on the second parameter. For a situation where the first PUCCH repetition collides with the second PUCCH repetition, priorities for different types of uplink control information (UCI) are applied. A hybrid automatic repeat request acknowledgment (HARQ‑ACK) has a higher priority than a scheduling request (SR) and a channel state information (CSI). The SR has a higher priority than the CSI.

Description

[0001] Related Applications

[0002] This application is related to and claims priority from U.S. Provisional Patent Application No. 62 / 631,280, entitled “PUCCH COLLISION HANDLING FORMULTI-SLOT LONG PUCCH IN 5G NR,” filed on February 15, 2018, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to PUCCH conflict handling for a multi-slot long physical uplink control channel (PUCCH) in 5G New Radio (NR). Background Art

[0004] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage areas, and enhanced functionality. A wireless communication system may provide communication for multiple wireless communication devices, each of which may be served by a base station. A base station may be a device that communicates with a wireless communication device.

[0005] With the development of wireless communication equipment, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.

[0006] For example, a wireless communication device may communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a block diagram illustrating one specific implementation of one or more gNBs and one or more UEs in which systems and methods for PUCCH collision handling for a multi-slot long physical uplink control channel (PUCCH) may be implemented;

[0008] Figure 2 is an example showing a combination of short PUCCH and PUCCH collision between short PUCCHs;

[0009] Figure 3 is an example showing a combination of PUCCH collisions between short PUCCH and long PUCCH;

[0010] Figure 4 is an example showing a combination of long PUCCH and PUCCH collision between long PUCCHs;

[0011] Figure 5 is an example showing a PUCCH discard method based on priority rules;

[0012] Figure 6 is an example showing another PUCCH discard method based on priority rules;

[0013] Figure 7 is an example showing yet another PUCCH discard method based on priority rules;

[0014] Figure 8 is an example of collision handling between multi-slot PUCCH and single-slot PUCCH;

[0015] Fig. 9 is a diagram showing an example of a resource grid for a downlink;

[0016] Fig.10 is a diagram showing one example of a resource grid for an uplink;

[0017] Fig.11 Examples of several parameters are shown;

[0018] Fig.12 Shown for Fig.11 An example of a subframe structure of the parameters shown in;

[0019] Fig.13 Examples of time slots and sub-time slots are shown;

[0020] Fig.14 An example of a scheduling timeline is shown;

[0021] Fig.15 An example of a DL control channel monitoring area is shown;

[0022] Fig.16 An example of a DL control channel including more than one control channel element is shown;

[0023] Fig.17 An example of a UL control channel structure is shown;

[0024] Fig.18 is a block diagram illustrating a specific implementation of a gNB;

[0025] Fig.19 is a block diagram illustrating a specific implementation of a UE;

[0026] Fig. 20 shows various components that may be utilized in a UE;

[0027] Fig.21 Various components that may be utilized in a gNB are shown;

[0028] Fig. 22 is a block diagram illustrating one specific implementation of a UE in which systems and methods for PUCCH collision handling for multi-slot long PUCCHs may be implemented; and

[0029] Fig.23 is a block diagram illustrating one specific implementation of a gNB in ​​which systems and methods for PUCCH collision handling for multi-slot long PUCCH may be implemented. DETAILED DESCRIPTION

[0030] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a first parameter for configuring a number of time slots for a first physical uplink control channel (PUCCH) repetition. The receiving circuit is also configured to receive a second parameter for configuring a number of time slots for a second PUCCH repetition. The UE also includes a transmission circuit configured to perform a first PUCCH repetition in a first plurality of time slots based on the first parameter, wherein each transmission of the first PUCCH repetition is performed at the same position within each of the first plurality of time slots. The transmission circuit is also configured to perform a second PUCCH repetition in a second plurality of time slots based on the second parameter, wherein each transmission of the second PUCCH repetition is performed at the same position within each of the second plurality of time slots. For a situation where the first PUCCH repetition collides with the second PUCCH repetition, a priority for uplink control information (UCI) of different types is applied. A hybrid automatic repeat request confirmation (HARQ-ACK) has a higher priority than a scheduling request (SR) and a channel state information (CSI). SR has a higher priority than CSI.

[0031] The present invention also describes a base station device. The base station device includes a transmission circuit configured to transmit a first parameter, the first parameter being used to configure the number of time slots for a first physical uplink control channel (PUCCH) repetition. The transmission circuit is also configured to transmit a second parameter, the second parameter being used to configure the number of time slots for a second PUCCH repetition. The base station device also includes a receiving circuit configured to receive a first PUCCH repetition in a first plurality of time slots based on the first parameter, wherein each transmission of the first PUCCH repetition is received at the same position within each time slot in the first plurality of time slots. The receiving circuit is also configured to receive a second PUCCH repetition in a second plurality of time slots based on the second parameter, wherein each transmission of the second PUCCH repetition is received at the same position within each time slot in the second plurality of time slots. For a situation where the first PUCCH repetition collides with the second PUCCH repetition, a priority for different types of uplink control information (UCI) is applied. A hybrid automatic repeat request confirmation (HARQ-ACK) has a higher priority than a scheduling request (SR) and a channel state information (CSI). SR has a higher priority than CSI.

[0032] The present invention also describes a communication method for a UE. The method includes receiving a first parameter, which is used to configure the number of time slots for a first physical uplink control channel (PUCCH) repetition. The method also includes receiving a second parameter, which is used to configure the number of time slots for a second PUCCH repetition. The method also includes performing a first PUCCH repetition in a first plurality of time slots based on the first parameter, wherein each transmission of the first PUCCH repetition is performed at the same position within each time slot in the first plurality of time slots. The method also includes performing a second PUCCH repetition in a second plurality of time slots based on the second parameter, wherein each transmission of the second PUCCH repetition is performed at the same position within each time slot in the second plurality of time slots. For the case where the first PUCCH repetition conflicts with the second PUCCH repetition, the priority for different types of uplink control information (UCI) is applied. A hybrid automatic repeat request confirmation (HARQ-ACK) has a higher priority than a scheduling request (SR) and a channel state information (CSI). SR has a higher priority than CSI.

[0033] The present invention also describes a communication method for a base station device. The method includes transmitting a first parameter, which is used to configure the number of time slots for a first physical uplink control channel (PUCCH) repetition. The method also includes transmitting a second parameter, which is used to configure the number of time slots for a second PUCCH repetition. The method also includes receiving a first PUCCH repetition in a first plurality of time slots based on the first parameter, wherein each transmission of the first PUCCH repetition is received at the same position within each time slot in the first plurality of time slots. The method also includes receiving a second PUCCH repetition in a second plurality of time slots based on the second parameter, wherein each transmission of the second PUCCH repetition is received at the same position within each time slot in the second plurality of time slots. For the case where the first PUCCH repetition conflicts with the second PUCCH repetition, priorities for different types of uplink control information (UCI) are applied. A hybrid automatic repeat request acknowledgment (HARQ-ACK) has a higher priority than a scheduling request (SR) and a channel state information (CSI). SR has a higher priority than CSI.

[0034] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that aims to develop globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems and devices.

[0035] 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 specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0036] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, and / or 12). 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 used in other types of wireless communication systems.

[0037] A wireless communication device may be an electronic device that is used to transmit voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, 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 the 3GPP specification, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device". UE may also be more generally referred to as a terminal device.

[0038] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB), or some other similar term. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station", "Node B", "eNB", "gNB" and / or "HeNB" may be used interchangeably herein to represent the more general term "base station". In addition, the term "base station" may be used to represent an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.

[0039] It should be noted that, as used herein, a "cell" may be any communication channel specified by a standardization or regulatory body for International Mobile Telecommunications-Advanced (IMT-Advanced), and all or a subset of such "cells" may be adopted by 3GPP as an authorized band (e.g., frequency band) for communication between an eNB and a UE. It should also be noted that, in the E-UTRA and E-UTRAN general description, as used herein, a "cell" may be defined as "a combination of downlink resources and optional uplink resources". The link 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.

[0040] "Configured cells" are those cells that the UE is aware of and is permitted by the eNB to transmit or receive information. "Configured cells" may be serving cells. The UE may receive system information and perform required measurements on all configured cells. "One or more configured cells" for a radio connection may include a primary cell and / or none, one or more secondary cells. "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 downlink transmissions, those cells for which the UE decodes the physical downlink shared channel (PDSCH). "Deactivated cells" are those configured cells for which the UE does not monitor the transmission PDCCH. It should be noted that "cells" may be described in different dimensions. For example, a "cell" may have time, space (e.g., geographic) and frequency characteristics.

[0041] The 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 enable services such as enhanced mobile broadband (eMBB) communications and ultra-reliable low latency communications (URLLC) services and massive machine type communications (MMTC). New radio (NR) base stations may be referred to as gNBs. gNBs may also be more generally referred to as base station equipment.

[0042] In NR, multiple PUCCH formats are defined that can be used to report various UCIs. In some cases, multiple UCIs can be reported on different PUCCHs in the same time slot with partial or full overlap between these PUCCHs. Different rules can be applied to handle partial and full PUCCH overlap situations for different combinations of UCI content. Generally speaking, the rules can be classified into two cases. In the first case, UCI can be multiplexed and reported on a single PUCCH. In this case, the UCI payload of the PUCCH will increase, and the same or different PUCCH resources can be used to report the aggregated UCI. In the second case, UCI cannot be multiplexed, so some partial or full PUCCH discard rules must be specified. In this case, at least part or all of the PUCCHs for some UCIs can be discarded.

[0043] The systems and methods described herein include possible approaches to both of these approaches. Special cases are then described when UCI is reported on a multi-slot PUCCH (i.e., a long PUCCH configured with repetitions or a long PUCCH configuration with multi-slot transmission). If the UCI carries a long PUCCH with multi-slot transmission and partially or completely overlaps with another PUCCH carrying different UCI, the long PUCCH with multi-slot transmission may be discarded and postponed to a later slot, and the PUCCH carrying the other UCI should be transmitted. This avoids potential PUCCH format and / or resource modifications where UCI multiplexing is supported, and avoids PUCCH discards where UCI multiplexing is not supported. Therefore, because UCI is not discarded and the PUCCH format is not modified, this provides better UCI reporting performance.

[0044] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods as generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0045] Figure 1 1 is a block diagram illustrating one specific implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for PUCCH collision handling for a multi-slot long physical uplink control channel (PUCCH) may be implemented. One or more UEs 102 use one or more antennas 122a-n to communicate with one or more gNBs 160. For example, UE 102 transmits electromagnetic signals to gNB 160 and receives electromagnetic signals from gNB 160 using one or more antennas 122a-n. gNB 160 communicates with UE 102 using one or more antennas 180a-n.

[0046] The UE 102 and the gNB 160 may communicate with each other using one or more channels 119, 121. For example, the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include PUCCH (Physical Uplink Control Channel) and PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, the uplink channel 121 (e.g., PUSCH) may be used to transmit UL data (i.e., transport blocks), MAC PDUs, and / or UL-SCH (Uplink Shared Channel).

[0047] Here, the 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 to transmit URLLC data. For the sake of simple description, the term "PUSCH" may represent any one of the following: (1) only PUSCH (e.g., conventional PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not conventional PUSCH).

[0048] In addition, for example, the uplink channel 121 may be used to transmit a hybrid automatic repeat request-ACK (HARQ ACK), channel state information (CSI) and / or a scheduling request (SR). The HARQ ACK may include information indicating a positive acknowledgement (ACK) or a negative acknowledgement (NACK) of DL data (i.e., a transport block), a medium access control protocol data unit (MAC PDU) and / or a DL SCH (downlink shared channel).

[0049] The CSI may include information indicating the channel quality of the downlink. The SR may be used to request UL-SCH (Uplink Shared Channel) resources for new transmission and / or retransmission. That is, the SR may be used to request UL resources for transmitting UL data.

[0050] For example, one or more gNBs 160 may also use one or more downlink channels 119 to transmit information or data to one or more UEs 102. Examples of downlink channels 119 include PDCCH, PDSCH, etc. Other types of channels may be used. PDCCH may be used to transmit downlink control information (DCI).

[0051] 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 operation module 124. For example, one or more receive paths and / or transmit 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 shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0052] 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 122a-n. For example, the receiver 120 may receive and downconvert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

[0053] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may decode the signal using the decoder 108. The decoder 108 may generate a decoded signal 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 include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as a second UE decoded signal 110) may include overhead data and / or control data. For example, the second UE decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0054] Generally speaking, the UE operation module 124 enables the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include a UE scheduling module 126.

[0055] The UE scheduling module 126 may perform simultaneous HARQ-ACK and SR transmission on the NR PUCCH. In a first aspect, the NR PUCCH format and UCI reporting are described. The physical uplink control channel supports multiple formats as shown in Table 1.

[0056]

[0057]

[0058] Table 1

[0059] As given in Table 1, NR defines multiple PUCCH formats. Short PUCCH can be 1 to 2 symbols. Short PUCCH can include format 0 (less than or equal to 2 bits, sequence-based) and / or format 2 (greater than 2 bits, OFDM-based). Long PUCCH can be greater than or equal to 4 symbols. Long PUCCH can include format 1 (less than or equal to 2 bits, sequence-based), format 3 (greater than 2 bits, DFT-S-OFDM-based, without UE multiplexing) and / or format 4 (greater than 2 bits, DFT-S-OFDM-based, with UE multiplexing).

[0060] If the UE 102 is not transmitting PUSCH, and the UE 102 is transmitting UCI, the UE 102 may transmit UCI on PUCCH format 0 if the transmission exceeds 1 symbol or 2 symbols and / or the number of UCI bits is 1 or 2. If the transmission exceeds 4 or more symbols and / or the number of UCI bits is 1 or 2, the UE 102 may transmit UCI on PUCCH format 1. If the transmission exceeds 1 symbol or 2 symbols and / or the number of UCI bits is greater than 2, the UE 102 may transmit UCI on PUCCH format 2. If the transmission exceeds 4 or more symbols and / or the number of UCI bits is greater than 2, the UE 102 may transmit UCI on PUCCH format 3. If the transmission exceeds 4 or more symbols; the number of UCI bits is greater than 2 and / or the PUCCH resources include orthogonal cover codes, the UE 102 may transmit UCI on PUCCH format 4.

[0061] For PUCCH format 3 or for PUCCH format 4, the UE 102 may be configured by a higher layer parameter PUCCH-F3-F4-additional-DMRS (Multiple Symbols for DM-RS).

[0062] For PUCCH formats 1, 3 or 4, the UE may configure the number of time slots used for PUCCH transmission by the corresponding higher layer parameters PUCCH-F1-number-of-slots, PUCCH-F3-number-of-slots or PUCCH-F4-number-of-slots.

[0063] for UE 102 can The PUCCH transmission in each time slot The UCI is repeated in the PUCCH transmission in the first slot of the PUCCH. Each of the time slots has the same number of consecutive symbols as provided by the higher-level parameter PUCCH-F1-F3-F4-number-of-symbols. PUCCH transmissions may be Each of the time slots has the same first symbol as provided by the higher layer parameter PUCCH-F1-F3-F4-starting-symbol.

[0064] for The UE 102 may be configured by the higher layer parameter PUCCH-F1-F3-F4-interslot-FH whether to perform frequency hopping for PUCCH transmissions in different time slots. If PUCCH-F1-F3-F4-interslot-FH=ON, the first PRB for PUCCH transmission is provided by the higher layer parameter PUCCH-starting-PRB, and the second PRB for PUCCH transmission is provided by the higher layer parameter PUCCH-2nd-hop-PRB.

[0065] for If the UE 102 is configured to perform frequency hopping for PUCCH transmissions in different time slots, the UE 102 may perform frequency hopping for each time slot and / or the UE 102 is not expected to be configured to perform frequency hopping for PUCCH transmissions within one time slot.

[0066] If the UE 102 is configured with the higher-layer parameter UL-DL-configuration-common or is additionally configured with the higher-layer parameter UL-DL-configuration-dedicated for the slot format of each slot over the number of slots, the UE 102 may determine the number of slots for PUCCH transmission. The first slot is the first slot starting at the slot indicated to the UE 102 and having a UL symbol (because the symbol provided by the higher layer parameter PUCCH-F1-F3-F4-starting-symbol is the UL symbol) and consecutive UL symbols (starting from this symbol, equal to the number of symbols provided by the higher layer parameter PUCCH-F1-F3-F4-number-of-symbols).

[0067] If the UE 102 is not configured with the higher layer parameter UL-DL-configuration-common, the UE 102 may use the PUCCH transmission The time slots are determined to be the time slots starting from the time slot indicated to the UE 102. consecutive time slots.

[0068] Based on the above description, for long PUCCH formats 1, 3, and 4, multi-slot transmission is supported by configuring the number of slots (nrofSlots) used for PUCCH repetition or multi-slot transmission. The nrofSlots parameter can be selected from the value set of {1, 2, 4, 8}. The nrofSlots parameter can be configured according to the long PUCCH format (i.e., PUCCH 1, PUCCH 3, and PUCCH 4).

[0069] For multi-slot long PUCCH transmissions, the PUCCH format resources (i.e., RB position, number of symbols, etc.) may be determined by the initial PUCCH transmission. In each consecutive PUCCH transmission, the same PUCCH position within the slot is used. The PUCCH transmission may be repeated until the configured number of slots is reached.

[0070] When a UE receives a grant to transmit a long PUCCH, the "unknown" symbols in the semi-static DL / UL allocation can be used for long PUCCH transmission over multiple slots. During PUCCH repetition, if there are not enough symbols in the slot for the long PUCCH position and duration, the long PUCCH is not transmitted in a given slot and repetition is performed in later slots until the configured number of slots is reached.

[0071] In a second aspect, PUCCH collision scenarios for UCI reporting are described herein. PUCCH may be used to report different types of UCI, including HARQ-ACK, where PUCCH format 0 or 1 may be used if the number of HARQ-ACK bits is at most 2 bits, and / or PUCCH format 2 or 3 or 4 may be used if the number of HARQ-ACK bits is greater than 2 bits.

[0072] PUCCH can be used to report channel state information. CSI may include channel quality indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), strongest layer indication (SLI), rank indication (RI) and / or L1-RSRP. CSI reports can be periodic CSI (P-CSI), semi-persistent CSI or aperiodic CSI (A-CSI). CSI may include CSI part 1 and CSI part 2. CSI PUCCH resources can be PUCCH format 2 / 3 / 4. For P-CSI, PUCCH resources can be semi-statically configured by high-layer signaling. For A-CSI, PUCCH resources can be dynamically indicated.

[0073] PUCCH may be used to report a scheduling request (SR). Multiple SR configurations may be configured for the UE 102. Each SR configuration may be linked to a different communication type or service. The SR configuration may include the SR PUCCH format and resource, periodicity, and offset within the periodicity. Since the SR carries only one bit, the SR PUCCH resource may be configured with PUCCH format 0 or PUCCH format 1.

[0074] HARQ-ACK is a feedback for PDSCH transmission that can be scheduled at any time slot. In addition, CSI and SR can be scheduled at different periodicities. Therefore, multiple UCI situations can be reported in the same time slot, causing conflicts between PUCCHs carrying different UCI.

[0075] In NR, since multiple PUCCH formats are defined and the duration of PUCCH is configurable, there are many different collision situations between PUCCHs. Figure 2 A combination of short PUCCH and PUCCH collision between short PUCCHs is shown. Figure 3 A combination of PUCCH collisions between short PUCCH and long PUCCH is shown. Figure 4 A combination of long PUCCH and PUCCH collision between long PUCCHs is shown.

[0076] For collision cases, PUCCHs may fully overlap (i.e., one PUCCH occupies the same symbol or is contained within another PUCCH). PUCCHs may partially overlap (i.e., some symbols of one PUCCH overlap with another PUCCH). For full and partial overlap cases, the number of overlapping symbols may be different based on the duration and relative starting position of the PUCCHs. It is neither feasible nor necessary to define different behaviors for each combination.

[0077] Generally speaking, in case of collision between UCI transmission and PUCCH, two approaches can be considered. In contrast, CSI reporting is not as time-sensitive as HARQ-ACK reporting. Periodic CSI is configured by RRC and the reporting timing is known in advance. Aperiodic CSI on PUCCH is triggered by DL DCI and should be well known before PUCCH reporting based on minimum processing time. In addition, the gNB should be able to avoid collision between HARQ-ACK and A-CSI reporting. Therefore, in case of collision between PUCCH for HARQ-ACK and PUCCH for CSI reporting, the CSI content should be known at the time of HARQ-ACK PUCCH transmission. And simultaneous HARQ-ACK and CSI transmission on a single PUCCH can be configured and / or supported.

[0078] Therefore, in one method, multiple UCIs may be multiplexed and reported on a single PUCCH channel. If the PUCCH for HARQ-ACK partially or completely overlaps with one or more PUCCHs for SR, simultaneous HARQ-ACK and SR may be reported on a single PUCCH resource for HARQ-ACK. If the PUCCH for HARQ-ACK partially or completely overlaps with the PUCCH for CSI reporting, and if simultaneous HARQ-ACK and CSI are configured, HARQ-ACK and CSI multiplexing may be considered. Therefore, the UE should select an appropriate HARQ-ACK PUCCH resource based on the combined payload size and maximum coding rate of the PUCCH resource to determine whether the PUCCH resource can support multiplexing HARQ-ACK with CSI, and which part of the CSI should be multiplexed and reported together. If multiplexing is feasible, joint coding of all or part of the HARQ-ACK and CSI is performed. If multiplexing is not feasible, for example, the coding rate is too high and the payload exceeds the maximum supported value of the PUCCH, a method without simultaneous HARQ-ACK and CSI should be used.

[0079] In another approach, only one PUCCH channel is transmitted at any given time, so some channel dropping rules may be applied to determine which channel to transmit and which channel to drop.

[0080] Considering that different types of UCIs may have different priorities and delay tolerances, a common framework may be designed for any conflicting situations (ie, for both partial overlap and full overlap situations), as described herein.

[0081] If simultaneous HARQ-ACK and CSI are not configured, multiplexing of CSI and HARQ-ACK on a single PUCCH resource may not be supported. In this case, some priority rules may be defined to determine which PUCCH should be transmitted.

[0082] In one approach, channel priority may be based on the UCI type on each PUCCH. Priority may be listed from high to low as HARQ-ACK ≥ SR > CSI. A single CSI report should be transmitted even if multiple CSI reports are triggered with a high to low priority of aperiodic CSI > semi-persistent CSI > periodic CSI. For UCIs with the same priority, if the communication type is considered, the UCI for URLLC services should have a higher priority than the UCI for eMBB services.

[0083] In another method, the PUCCH priority can be based on the starting symbol of each PUCCH. The PUCCH that starts transmission earlier has a higher priority. In the case of the same starting symbol, the UCI priority can be further applied to determine the channel priority.

[0084] In another method, the PUCCH priority may be determined based on the duration of each PUCCH. A PUCCH with a shorter duration has a higher priority. In the case of the same starting symbol, the UCI priority and / or starting position may be further applied to determine the channel priority.

[0085] Based on the priority rules, PUCCH discard can be performed in different ways, such as Figures 5 to 7 Without loss of generality, assume that Figures 5 to 7 PUCCH 1 has a higher priority than PUCCH 2.

[0086] In one approach, PUCCH discarding can be performed at the symbol level, such as Figure 5 As shown. Therefore, the overlapping symbols on the PUCCH with lower priority are discarded. If there are any remaining symbols after the overlapping symbols, the transmission of the PUCCH with lower priority can be resumed.

[0087] Alternatively, in Figure 6 In the case of a PUCCH with a lower priority, the overlapping symbols on the PUCCH are discarded. If there are any remaining symbols after the overlapping symbols, the transmission of the PUCCH with a lower priority is also discarded.

[0088] In both cases, the PUCCH with lower priority is punctured and the result is a partial PUCCH transmission. The performance of the PUCCH with lower priority may be degraded. Sometimes the PUCCH may not be decodable (for example, if the DMRS symbols are punctured by symbol dropping).

[0089] Therefore, in another approach, complete channel dropping can be used, e.g. Figure 7 As shown. In case of a collision between two PUCCHs, the PUCCH with lower priority is not transmitted. This assumes that the UE 102 will know the collision situation in advance before transmitting another PUCCH. Complete PUCCH channel discard is easier to implement if there is sufficient processing time before PUCCH transmission. However, the UCI carried on the discarded PUCCH cannot be reported.

[0090] In a third aspect, the present invention describes PUCCH collision handling for long PUCCH with multi-slot transmissions. The PUCCH collision situations discussed above are primarily applicable to PUCCH reports in a single slot. That is, the PUCCH priority and channel drop rules discussed above can be applied to situations where multi-slot transmissions (e.g., nrofSlots parameter) are not configured for long PUCCH. As described above, for multi-slot long PUCCH transmissions, the PUCCH format resources (i.e., RB positions, number of symbols, etc.) are determined by the initial PUCCH transmission. In each consecutive PUCCH transmission, the same PUCCH position within the slot is used. The PUCCH transmission is repeated until the configured number of slots is reached.

[0091] However, for several reasons, the above approach may not be possible for PUCCH collisions between long PUCCH transmissions with multi-slot configurations and a single PUCCH instance in a given slot. Figure 8 An example of collision handling between multi-slot PUCCH and single-slot PUCCH is shown.

[0092] If UCI multiplexing is used (such as Figure 8 If the PUCCH format / resources are determined by the initial long PUCCH transmission in the multi-slot PUCCH, there may not be PUCCH resources available for aggregate payload size and multi-slot transmission.

[0093] On the other hand, if PUCCH dropping is applied, another PUCCH will be dropped and the UCI carried on the PUCCH will be dropped, such as Figure 8 This may lead to unnecessary performance loss.

[0094] When the UE 102 receives a grant to transmit a long PUCCH, the "unknown" symbols in the semi-static DL / UL allocation can be used for long PUCCH transmission over multiple slots. During PUCCH repetition, i.e., during continuous PUCCH transmission, if there are not enough symbols in the slot for the long PUCCH position and duration, the long PUCCH is not transmitted in a given slot, and multi-slot transmission will be performed in a later slot until the configured number of slots is reached. That is, for multi-slot long PUCCH, PUCCH discard and postponed transmission are already supported (e.g., due to insufficient resources or mismatch of the slot format indicator (SFI) structure).

[0095] For long PUCCH with multi-slot transmission, in case of PUCCH channel collision with single-slot PUCCH, similar behavior can be considered by assuming that some UL symbols are unavailable (because they are occupied by single-slot PUCCH). Therefore, during long PUCCH with multi-slot transmission, if the long PUCCH with multi-slot transmission overlaps with another single-slot PUCCH, UCI multiplexing is not applied. Instead, another single-slot PUCCH is transmitted, and the long PUCCH with multi-slot transmission in the slot is discarded and the transmission is postponed to the next slot with available resources, such as Figure 8 The single-slot PUCCH may be a short PUCCH with format 0 or format 2; the single-slot PUCCH may be a long PUCCH with format 1, 3 or 4.

[0096] Long PUCCH configured with multi-slot transmission is usually used to report HARQ-ACK, although in theory it can also be used to carry CSI. In several cases, conflicts may occur between long PUCCH with multi-slot transmission. For example, the multi-slot PUCCH is postponed due to the SFI mismatch with the slot with another PUCCH report in the previous slot; or a new UCI report is scheduled or triggered in the slot where the multi-slot PUCCH is scheduled for transmission within the multi-slot duration. The new UCI report can be HARQ-ACK for the most recent PDSCH transmission, triggered SR, configured periodic CSI, triggered A-CSI, etc.

[0097] For example, in a given time slot, in the case where a long PUCCH with multi-slot transmission (e.g., PUCCH format 1, 3, or 4) transmitting HARQ-ACK collides with a short PUCCH (e.g., PUCCH format 0 or 2) transmitting HARQ-ACK, the short PUCCH carrying HARQ-ACK may be transmitted. In addition, the long PUCCH with multi-slot transmission transmitting HARQ-ACK in the given time slot is discarded and postponed for transmission in the next available time slot. That is, in the case where multi-slot transmission is configured for the long PUCCH (e.g., nrofSlots parameter), for a given time slot, the short PUCCH may be prioritized over the long PUCCH with multi-slot transmission configured.

[0098] In addition, for example, in a given time slot, in the event that a long PUCCH with multi-slot transmission (e.g., PUCCH format 1, 3, or 4) transmitting HARQ-ACK collides with another single-slot long PUCCH (e.g., PUCCH format 1, 3, or 4) transmitting HARQ-ACK, a single-slot long PUCCH (e.g., PUCCH format 3 or 4) carrying HARQ-ACK may be transmitted. And, the long PUCCH with multi-slot transmission transmitting HARQ-ACK is discarded in the given time slot and is postponed for transmission in the next available time slot. That is, in the event that multi-slot transmission is configured for the long PUCCH (e.g., nrofSlots parameter), for a given time slot, a single-slot long PUCCH (e.g., PUCCH format 1, PUCCH format 3, or PUCCH format 4) may take precedence over a long PUCCH with multi-slot transmission.

[0099] For another example, in a given time slot, when a long PUCCH with multi-slot transmission (e.g., PUCCH format 1, 3, or 4) transmitting HARQ-ACK collides with a short PUCCH (e.g., PUCCH format 2) or a long PUCCH (e.g., PUCCH formats 3 and 4) transmitting CSI, the PUCCH carrying CSI may be transmitted. Furthermore, the long PUCCH with multi-slot transmission transmitting HARQ-ACK in the given time slot is discarded and postponed for transmission in the next available time slot. That is, when multi-slot transmission (e.g., nrofSlots parameter) is configured for a long PUCCH (e.g., PUCCH format 1), for a given time slot, a single-slot PUCCH transmission for CSI may take precedence over a long PUCCH with multi-slot transmission of HARQ-ACK.

[0100] Although the examples are about multi-slot long PUCCH carrying HARQ-ACK, the same principle applies if CSI is carried on multi-slot long PUCCH with format 3 or format 4. That is, single-slot PUCCH transmission for UCI (e.g., HARQ-ACK and / or SR and / or CSI) may take precedence over long PUCCH with multi-slot transmission.

[0101] That is, in the case where multi-slot transmission is configured for a long PUCCH format (e.g., nrofSlots parameter), the long PUCCH format configured with multi-slot transmission has a lower priority and can be discarded for a given slot. One or more other PUCCH formats (e.g., PUCCH and / or long PUCCH) can take precedence over the long PUCCH format configured with multi-slot transmission.

[0102] As a special case, if up to 2 bits of HARQ-ACK are carried on long PUCCH format 1 with multi-slot transmission, and the PUCCH partially or fully overlaps with a positive SR transmission on another PUCCH resource, the HARQ-ACK PUCCH can be used to carry both HARQ-ACK and SR (e.g., SR may be represented by a cyclic shift on the HARQ-ACK sequence).

[0103] In another approach, if SR is also configured with PUCCH format 1, HARQ-ACK may be reported on the PUCCH resources used for SR, i.e., in the case of a negative SR, HARQ-ACK is reported on the PUCCH format 1 resources used for HARQ-ACK; in the case of a positive SR, HARQ-ACK is reported using the SR PUCCH 1 resources. Thus, SR is indicated by on / off keying of the PUCCH transmission on the SR resources. This approach is good if the SR PUCCH resources and the HARQ-ACK PUCCH resources completely overlap, i.e., they have the same starting symbol and duration in the time slot. However, in the case of partial overlap, there are timing issues associated, such as whether HARQ-ACK can be reported earlier or delayed due to the misalignment of the PUCCH formats 1 of the HARQ-ACK and SR resources.

[0104] If a long PUCCH with multi-slot transmission collides with another long PUCCH with multi-slot transmission, the PUCCH priority and channel drop rules discussed above can be used to determine which PUCCH is transmitted. The other PUCCH in a given slot should be dropped and postponed for transmission in an upcoming slot with available long PUCCH resources.

[0105] The UE operations module 124 may provide the information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the one or more receivers 120 when to receive a retransmission.

[0106] 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 the modulation pattern expected for transmissions from the gNB 160.

[0107] 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 the encoding expected for the transmission from the gNB 160.

[0108] The UE operation 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 operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0109] The encoder 150 may encode the 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 the data to space, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0110] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmission to gNB 160. Modulator 154 may modulate coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0111] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The 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 signals to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upconvert the one or more modulated signals 156 and transmit the one or more modulated signals to the one or more gNBs 160.

[0112] 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 operation module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113) may be implemented.

[0113] 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 180a-n. For example, the receiver 178 may receive and downconvert the signals to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0114] The demodulator 172 may demodulate 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 decode the signals using the decoder 166. The decoder 166 may produce one or more decoded signals 164, 168. For example, the first eNB decoded signal 164 may include received payload data, which may be stored in the data buffer 162. The second eNB decoded signal 168 may include overhead data and / or control data. For example, the second eNB decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operations module 182 may use to perform one or more operations.

[0115] In general, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include a gNB scheduling module 194. As described herein, the gNB scheduling module 194 may perform operations for PUCCH collision handling for multi-slot long PUCCH.

[0116] 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 the modulation pattern expected for transmissions from one or more UEs 102.

[0117] 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 the encoding expected for transmissions from one or more UEs 102.

[0118] The gNB operation 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 operation module 182 may instruct the encoder 109 to encode the information 101, including the transmission data 105.

[0119] The encoder 109 may encode the 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 the data to space, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide the encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0120] The gNB operations module 182 may provide information 103 to the modulator 113. The 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 transmission to one or more UEs 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0121] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The 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 (or when not) to transmit signals to the one or more UEs 102. The one or more transmitters 117 may upconvert the one or more modulated signals 115 and transmit the one or more modulated signals to the one or more UEs 102.

[0122] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.

[0123] It should also be noted that one or more of the elements or components thereof included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0124] URLLC can coexist with other services (e.g., eMBB). Due to latency requirements, in some methods, URLLC may have the highest priority. This article provides some examples of URLLC coexisting with other services (e.g., in one or more of the following figures).

[0125] Figure 2 is an example showing a combination of short PUCCH and PUCCH collision between short PUCCHs. Figure 2 This includes both complete overlap and partial overlap.

[0126] Figure 3 is an example showing a combination of PUCCH collisions between short PUCCH and long PUCCH. Figure 3 This includes both complete overlap and partial overlap.

[0127] Figure 4 is an example showing a combination of a long PUCCH and a PUCCH collision between long PUCCHs. Figure 4 This includes both complete overlap and partial overlap.

[0128] Figure 5 is an example showing a PUCCH discard method based on priority rules. In this method, PUCCH discard can be at the symbol level. Lower priority PUCCH transmission is resumed after overlapping symbols.

[0129] Figure 6 is an example showing another PUCCH discard method based on priority rules. In this method, partial PUCCH discard may occur. For lower priority PUCCHs, symbols after overlapping symbols and conflicting symbols may be discarded.

[0130] Figure 7 is an example showing yet another PUCCH discard method based on priority rules. In this method, complete PUCCH discard may occur.

[0131] Figure 8 is an example of collision handling between multi-slot PUCCH and single-slot PUCCH. Collision may occur between multi-slot PUCCH and single PUCCH transmissions. In the first method (a), multiplexing UCI on a single PUCCH may destroy the PUCCH repetition format and may require different PUCCH resources.

[0132] In the second method (b), another PUCCH will be dropped, and the UCI carried on the PUCCH will be dropped.

[0133] In the third method (c), another PUCCH may be transmitted. A long PUCCH with multi-slot transmission may be discarded and postponed to a later slot.

[0134] Fig. 9 is a diagram showing an example of a resource grid for a downlink. Fig. 9 The resource grid shown may be used in some specific implementations of the systems and methods disclosed herein. Figure 1 More details about the resource grid are given.

[0135] exist Fig. 9 In the embodiment, a downlink subframe 969 may include two downlink time slots 983. DL RB is the downlink bandwidth configuration of the serving cell, expressed in N RB SC Multiples of N RB SC is the size of resource block 989 in the frequency domain, expressed as the number of subcarriers, and N DL symb is the number of OFDM symbols 987 in the downlink slot 983. A resource block 989 may include a plurality of resource elements (REs) 991.

[0136] For PCell, N DL RB Broadcast as part of system information. For SCell (including Licensed Assisted Access (LAA) SCell), N DL RB The configuration is performed through an RRC message dedicated to the UE 102. For PDSCH mapping, the available RE 991 may be one whose index 1 satisfies 1≥1 in the subframe. 数据，开始 And / or 1 数据，结束 ≥1 of RE 991.

[0137] In the downlink, an OFDM access scheme with a cyclic prefix (CP) may be adopted, which may also be referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH, etc. may be transmitted. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs), which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair includes two downlink RBs that are consecutive in the time domain.

[0138] A downlink RB includes twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indices in the frequency domain and the time domain, respectively. Although a downlink subframe in one component carrier (CC) is discussed herein, a downlink subframe is defined for each CC, and the downlink subframes are substantially synchronized with each other between CCs.

[0139] Fig.10 is a diagram showing an example of a resource grid for uplink. Fig.10 The resource grid shown may be used in some specific implementations of the systems and methods disclosed herein. Figure 1 More details about the resource grid are given.

[0140] exist Fig.10 In the embodiment, an uplink subframe 1069 may include two uplink time slots 1083. UL RB is the uplink bandwidth configuration of the serving cell, expressed in N RB SC Multiples of N RB SC is the size of the resource block 1089 in the frequency domain, expressed as the number of subcarriers, and N UL symb is the number of SC-FDMA symbols 1093 in the uplink slot 1083. A resource block 1089 may include a plurality of resource elements (REs) 1091.

[0141] For PCell, N UL RB Broadcast as part of system information. For SCell (including LAA SCell), N UL RB The configuration is performed through an RRC message dedicated to UE 102.

[0142] In the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme can also be used, which is also called discrete Fourier transform spread OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH, etc. can be transmitted. An uplink radio frame may include multiple pairs of uplink resource blocks. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair includes two uplink RBs that are consecutive in the time domain.

[0143] An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called an RE and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indices in the frequency domain and time domain, respectively. Although this article discusses an uplink subframe in one component carrier (CC), an uplink subframe is defined for each CC.

[0144] Fig.11 Several examples of parameters 1101 are shown. Parameter #1 1101a may be a basic parameter (e.g., a reference parameter). For example, RE 1195a of basic parameter 1101a may be defined as having a subcarrier spacing 1105a of 15kHz in the frequency domain and a length of 2048Ts+CP (e.g., 160Ts or 144Ts) in the time domain (i.e., symbol length #1 1103a), where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds. For the i-th parameter, the subcarrier spacing 1105 may be equal to 15*2 i And the effective OFDM symbol length is 2048*2 -i *Ts. This makes the symbol length 2048*2 -i *Ts+CP length (e.g., 160*2 -i *Ts or 144*2 -i *Ts). In other words, the subcarrier spacing of the i+1th parameter is twice the subcarrier spacing of the ith parameter, and the symbol length of the i+1th parameter is half the symbol length of the ith parameter. Fig.11 Four parameters are shown, but the system may support another number of parameters. Furthermore, the system does not necessarily support all of the 0th to Ith parameters (i=0, 1, ..., I).

[0145] For example, the first UL transmission on the first SPS resource as described above may be performed only on parameter #1 (e.g., subcarrier spacing is 15 kHz). Here, UE 102 may acquire (detect) parameter #1 based on the synchronization signal. In addition, UE 102 may receive a dedicated RRC signal including information configuring parameter #1 (e.g., a handover command). The dedicated RRC signal may be a UE-specific signal. Here, the first UL transmission on the first SPS resource may be performed on parameter #1, parameter #2 (subcarrier spacing is 30 kHz), and / or parameter #3 (subcarrier spacing is 60 kHz).

[0146] In addition, the second UL transmission on the second SPS resource as described above may be performed only on parameter #3. Here, for example, UE 102 may receive system information (e.g., master information block (MIB) and / or system information block (SIB)) including information configuring parameter #2 and / or parameter #3.

[0147] In addition, UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) for configuring parameter #2 and / or parameter #3. System information (e.g., MIB) may be transmitted on a BCH (broadcast channel) and / or a dedicated RRC signal. System information (e.g., SIB) may include information about when to evaluate whether UE 102 is allowed to access a cell and / or define scheduling of other system information. System information (SIB) may include radio resource configuration information shared by multiple UEs 102. That is, the dedicated RRC signal may include each of a plurality of parameter configurations (first parameter, second parameter, and / or third parameter) for each of UL transmissions (e.g., each of UL-SCH transmissions, each of PUSCH transmissions). In addition, the dedicated RRC signal may include each of a plurality of parameter configurations (first parameter, second parameter, and / or third parameter) for each of DL transmissions (e.g., each of PDCCH transmissions).

[0148] Fig.12 Shows Fig.11 An example of a subframe structure of parameters 1201 is shown in FIG. Considering that time slot 1283 includes N DL symb (or N UL symb ) = 7 symbols, the time slot length of the i+1th parameter 1201 is i The number of slots 1283 (eg, 1 ms) in a subframe is doubled by half the length of the slot of parameter 1201. It should be noted that a radio frame may include 10 subframes and the radio frame length may be equal to 10 ms.

[0149] Fig.13 An example of a time slot 1383 and a sub-time slot 1307 is shown. If the sub-time slot 1307 is not configured by a higher layer, the UE 102 and the eNB / gNB 160 may use only the time slot 1383 as a scheduling unit. More specifically, a given transport block may be allocated to the time slot 1383. If the sub-time slot 1307 is configured by a higher layer, the UE 102 and the eNB / gNB 160 may use the sub-time slot 1307 as well as the time slot 1383. The sub-time slot 1307 may include one or more OFDM symbols. The maximum number of OFDM symbols constituting the sub-time slot 1307 may be N DL symb -1(or N ULsymb -1).

[0150] The sub-slot length may be configured by higher layer signaling. Alternatively, the sub-slot length may be indicated by a physical layer control channel (eg, via a DCI format).

[0151] Subslot 1307 can start from any symbol in slot 1383 unless it collides with a control channel. Based on the starting position, the length of the minislot may be limited. For example, the length is N DL symb -l(or N UL symb -1) may start from the second symbol in time slot 1383. The starting position of sub-time slot 1307 may be indicated by a physical layer control channel (e.g., by a DCI format). Alternatively, the starting position of sub-time slot 1307 may be derived from information of a physical layer control channel that schedules data in sub-time slot 1307 (e.g., a search space index, a blind decoding candidate index, a frequency and / or time resource index, a PRB index, a control channel element index, a control channel element aggregation level, an antenna port index, etc.).

[0152] Where subslots 1307 are configured, a given transport block may be allocated to a slot 1383, a subslot 1307, an aggregated subslot 1307, or one or more aggregated subslots 1307 and a slot 1383. This unit may also be a unit for HARQ-ACK bit generation.

[0153] Fig.14 An example of a scheduling timeline 1409 is shown. For a normal DL scheduling timeline 1409a, a DL control channel is mapped to the initial part of a time slot 1483a. A DL control channel 1411 schedules a DL shared channel 1413a in the same time slot 1483a. HARQ-ACKs for DL ​​shared channels 1413a (i.e., HARQ-ACKs each indicating whether a transport block in each DL shared channel 1413a is successfully detected) are reported via a UL control channel 1415a in a subsequent time slot 1483b. In this case, a given time slot 1483 may contain one of a DL transmission and a UL transmission.

[0154] For the normal UL scheduling timeline 1409b, the DL control channel 1411b is mapped to the initial part of the time slot 1483c. The DL control channel 1411b schedules the UL shared channel 1417a in the next time slot 1483d. For these cases, the associated timing (time offset) between the DL time slot 1483c and the UL time slot 1483d can be fixed or configured by high-layer signaling. Alternatively, it can be indicated by a physical layer control channel (e.g., a DL allocation DCI format, a UL authorization DCI format, or another DCI format, such as a UE common signaling DCI format that can be monitored in a common search space).

[0155] For the self-contained basic DL scheduling timeline 1409c, the DL control channel 1411c is mapped to the initial part of the time slot 1483e. The DL control channel 1411c schedules the DL shared channel 1413b in the same time slot 1483e. The HARQ-ACK for the DL shared channel 1413b is reported in the UL control channel 1415b, which is mapped at the end of the time slot 1483e.

[0156] For the self-contained basic UL scheduling timeline 1409d, the DL control channel 1411d is mapped to the initial part of the time slot 1483f. The DL control channel 1411d schedules the UL shared channel 1417b in the same time slot 1483f. For these cases, the time slot 1483f may contain a DL part and a UL part, and there may be a guard period between the DL transmission and the UL transmission.

[0157] The use of self-contained time slots may be based on the configuration of self-contained time slots. Alternatively, the use of self-contained time slots may be based on the configuration of sub-time slots. Still alternatively, the use of self-contained time slots may be based on the configuration of shortened physical channels (e.g., PDSCH, PUSCH, PUCCH, etc.).

[0158] Fig.15An example of a DL control channel monitoring area is shown. One or more groups of PRBs may be configured for DL ​​control channel monitoring. In other words, a control resource set is a group of PRBs in the frequency domain within which UE 102 attempts to blindly decode downlink control information, wherein the PRBs may or may not be frequency continuous, UE 102 may have one or more control resource sets, and one DCI message may be located in one control resource set. In the frequency domain, a PRB is a resource unit size for a control channel (which may or may not include a demodulation reference signal (DM-RS)). A DL shared channel may start at an OFDM symbol later than one or more symbols carrying a detected DL control channel. Alternatively, a DL shared channel may start at the last OFDM symbol carrying a detected DL control channel (or at a symbol earlier than the last OFDM symbol). In other words, dynamic reuse of at least a portion of resources in a control resource set for data of the same or different UEs 102 may be supported at least in the frequency domain.

[0159] Fig.16 An example of a DL control channel including more than one control channel element is shown. When the control resource set spans multiple OFDM symbols, the control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element may be mapped on an RE defined by a single PRB and a single OFDM symbol. If more than one DL control channel element is used for a single DL control channel transmission, DL control channel element aggregation may be performed.

[0160] The number of aggregated DL control channel elements is referred to as the DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to an integer power. The gNB 160 may inform the UE 102 which control channel candidates are mapped to each subset of OFDM symbols in the control resource set. If a DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, DL control channel element aggregation is performed within one OFDM symbol, i.e., multiple DL control channel elements are aggregated within one OFDM symbol. Otherwise, DL control channel elements may be aggregated in different OFDM symbols.

[0161] Fig.17An example of a UL control channel structure is shown. The UL control channel may be mapped on REs defined by PRBs in the frequency domain and time slots in the time domain, respectively. The UL control channel may be referred to as a long format (or just a first format). The UL control channel may be mapped on REs on a limited OFDM symbol in the time domain. This may be referred to as a short format (or just a second format). A UL control channel with a short format may be mapped on REs within a single PRB. Alternatively, a UL control channel with a short format may be mapped on REs within multiple PRBs. For example, staggered mapping may be applied, i.e., the UL control channel may be mapped to every N PRBs (e.g., 5 or 10) within the system bandwidth.

[0162] Fig.18 is a block diagram illustrating one specific implementation of a gNB 1860. The gNB 1860 may include a higher layer processor 1823, a DL transmitter 1825, a UL receiver 1833, and one or more antennas 1831. The DL transmitter 1825 may include a PDCCH transmitter 1827 and a PDSCH transmitter 1829. The UL receiver 1833 may include a PUCCH receiver 1835 and a PUSCH receiver 1837.

[0163] The high-level processor 1823 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1823 may obtain a transport block from the physical layer. The high-level processor 1823 may send / obtain high-level messages such as RRC messages and MAC messages to / from the high-level layer of the UE. The high-level processor 1823 may provide a PDSCH transmitter transport block and provide a PDCCH transmitter transmission parameter related to the transport block.

[0164] The DL transmitter 1825 may multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmit antenna 1831. The UL receiver 1833 may receive the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1831 and demultiplex them. The PUCCH receiver 1835 may provide the upper layer processor 1823 with UCI. The PUSCH receiver 1837 may provide the received transport block to the upper layer processor 1823.

[0165] Fig.191 is a block diagram illustrating one specific implementation of UE 1902. UE 1902 may include a higher layer processor 1923, a UL transmitter 1951, a DL receiver 1943, and one or more antennas 1931. UL transmitter 1951 may include a PUCCH transmitter 1953 and a PUSCH transmitter 1955. DL receiver 1943 may include a PDCCH receiver 1945 and a PDSCH receiver 1947.

[0166] The high-level processor 1923 may manage the behavior of the physical layer (the behavior of the UL transmitter and the DL receiver) and provide high-level parameters to the physical layer. The high-level processor 1923 may obtain a transport block from the physical layer. The high-level processor 1923 may send / obtain high-level messages such as RRC messages and MAC messages to / from the high-level layer of the UE. The high-level processor 1923 may provide a transport block to the PUSCH transmitter and provide the PUCCH transmitter 1953 UCI.

[0167] The DL receiver 1943 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1931. The PDCCH receiver 1945 may provide the higher layer processor 1923 with DCI. The PDSCH receiver 1947 may provide the higher layer processor 1923 with the received transport block.

[0168] It should be noted that the names of the physical channels described herein are examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH," "New Generation - (G)PDCCH, GPDSCH, GPUCCH, and GPUSCH," etc.

[0169] Fig. 20 Various components that may be used in UE 2002 are shown. Fig. 20 The UE 2002 described may be combined with Figure 1100 is implemented by the UE 102 described in the embodiment of the present invention. The UE 2002 includes a processor 2003 that controls the operation of the UE 2002. The processor 2003 may also be referred to as a central processing unit (CPU). The memory 2005 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 2007a and data 2009a to the processor 2003. A portion of the memory 2005 may also include a non-volatile random access memory (NVRAM). The instructions 2007b and data 2009b may also reside in the processor 2003. The instructions 2007b and / or data 2009b loaded into the processor 2003 may also include instructions 2007a and / or data 2009a from the memory 2005, which are loaded for execution or processing by the processor 2003. The instructions 2007b may be executed by the processor 2003 to implement the above method.

[0170] The UE 2002 may also include a housing that houses one or more transmitters 2058 and one or more receivers 2020 to allow transmission and reception of data. The one or more transmitters 2058 and one or more receivers 2020 may be combined into one or more transceivers 2018. One or more antennas 2022a-n are attached to the housing and electrically coupled to the transceiver 2018.

[0171] The various components of the UE 2002 are coupled together via a bus system 2011 (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 described in detail in the following sections. Fig. 20 2002 is shown as bus system 2011. UE 2002 may also include a digital signal processor (DSP) 2013 for processing signals. UE 2002 may also include a communication interface 2015 that provides user access to the functions of UE 2002. Fig. 20 The UE 2002 shown is a functional block diagram rather than a listing of specific components.

[0172] Fig.21 Various components that may be used in the gNB 2160 are shown. Fig.21 The gNB 2160 described may be configured in accordance with the Figure 1The gNB 2160 described herein may be implemented by the gNB 160. The gNB 2160 includes a processor 2103 that controls the operation of the gNB 2160. The processor 2103 may also be referred to as a central processing unit (CPU). The memory 2105 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of the two memories, or any type of device that can store information) provides instructions 2107a and data 2109a to the processor 2103. A portion of the memory 2105 may also include a non-volatile random access memory (NVRAM). The instructions 2107b and data 2109b may also reside in the processor 2103. The instructions 2107b and / or data 2109b loaded into the processor 2103 may also include instructions 2107a and / or data 2109a from the memory 2105, which are loaded for execution or processing by the processor 2103. The instructions 2107b may be executed by the processor 2103 to implement the above method.

[0173] The gNB 2160 may also include a housing that houses one or more transmitters 2117 and one or more receivers 2178 to allow transmission and reception of data. The one or more transmitters 2117 and one or more receivers 2178 may be combined into one or more transceivers 2176. One or more antennas 2180a-n are attached to the housing and electrically coupled to the transceiver 2176.

[0174] The various components of the gNB 2160 are coupled together via a bus system 2111 (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 referred to in the figure. Fig.21 2160 is shown as bus system 2111. gNB 2160 may also include a digital signal processor (DSP) 2113 for processing signals. gNB 2160 may also include a communication interface 2115 that provides user access to the functions of gNB 2160. Fig.21 The gNB 2160 shown is a functional block diagram rather than a listing of specific components.

[0175] Fig. 22 2 is a block diagram illustrating a specific implementation of a UE 2202 in which systems and methods for PUCCH collision handling for multi-slot long PUCCH in 5G NR may be implemented. The UE 2202 includes a transmitting device 2258, a receiving device 2220, and a control device 2224. The transmitting device 2258, the receiving device 2220, and the control device 2224 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Fig. 20 Shows Fig. 22Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0176] Fig.23 2 is a block diagram illustrating a specific implementation of a gNB 2360 in which systems and methods for PUCCH collision handling for multi-slot long PUCCH in 5G NR may be implemented. The gNB 2360 includes a transmitting device 2323, a receiving device 2378, and a control device 2382. The transmitting device 2323, the receiving device 2378, and the control device 2382 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Fig.21 Shows Fig.23 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0177] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example, and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Optical disks, where magnetic disks usually reproduce data magnetically, optical disks reproduce data optically using lasers.

[0178] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0179] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with each other 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 the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0180] It is to be understood that the claims are not limited to the precise configuration and components shown 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.

[0181] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls the CPU, etc. in a manner that realizes the functions according to the system and method (a program that causes the computer to operate). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, the information is stored in various ROMs or HDDs, and is read by the CPU whenever necessary for modification or writing. As a recording medium on which the program is stored, any of a semiconductor (e.g., ROM, nonvolatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., a magnetic tape, a floppy disk, etc.), etc. is possible. In addition, in some cases, the above-mentioned functions according to the system and method are realized by running the loaded program, and in addition, the functions according to the system and method are realized based on instructions from the program and in combination with an operating system or other application programs.

[0182] In addition, in the case where the program is available on the market, the program stored on a portable recording medium may be distributed, or the program may be transferred to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. In addition, some or all of the gNB 160 and UE 102 according to the above-mentioned system and method may be implemented as an ESI as a typical integrated circuit. Each functional block of the gNB 160 and UE 102 may be built into a chip separately, and some or all of the functional blocks may be integrated into the chip. In addition, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block may be implemented using a dedicated circuit or a general-purpose processor. In addition, if an integrated circuit technology that replaces LSI emerges as semiconductor technology continues to advance, an integrated circuit applying this technology may also be used.

[0183] In addition, each functional block or various features of the base station equipment and terminal equipment used by each of the above-mentioned specific implementations can be implemented or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each of the above-mentioned circuits may be configured by a digital circuit, or may be configured by an analog circuit. In addition, when a technology for making an integrated circuit that replaces the current integrated circuit appears due to advances in semiconductor technology, the integrated circuit produced by the technology can also be used.

[0184] As used herein, the term "and / or" should be interpreted as meaning one or more items. For example, the phrase "A, B, and / or C" should be interpreted as meaning any of the following: 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" should be interpreted as meaning 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 as meaning any of the following: 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" should be understood to refer to 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 the following: 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.

Claims

1. A user equipment UE, comprising: a processor configured to determine that a first physical uplink control channel PUCCH carrying first uplink control information UCI overlaps with a second PUCCH carrying second UCI in a time slot, the processor configured to determine one of the first PUCCH and the second PUCCH based on a first priority for the first PUCCH and a second priority for the second PUCCH, the one of the first PUCCH and the second PUCCH having a higher priority than the other of the first PUCCH and the second PUCCH, the first PUCCH being a PUCCH with multi-slot transmission; as well as an uplink UL transmitter, the UL transmitter being configured to transmit the one of the first PUCCH and the second PUCCH in the time slot, and not to transmit the other of the first PUCCH and the second PUCCH in the time slot, wherein, The first priority for the first PUCCH is based on a type of the first UCI, and the second priority for the second PUCCH is based on a type of the second UCI, In a case where the type of the first UCI is channel state information CSI having a higher priority and the type of the second UCI is CSI having a lower priority, the one of the first PUCCH and the second PUCCH is the first PUCCH, and the other of the first PUCCH and the second PUCCH is the second PUCCH, and The processor is configured to determine, based on a priority rule that the semi-persistent CSI is defined as having a higher priority than the periodic CSI, that the semi-persistent CSI and the periodic CSI are the CSI with a higher priority and the CSI with a lower priority, respectively. The second PUCCH is another PUCCH with multi-slot transmission.

2. A base station device, comprising: a processor configured to determine that a first physical uplink control channel PUCCH carrying first uplink control information UCI overlaps with a second PUCCH carrying second UCI in a time slot, the processor configured to determine one of the first PUCCH and the second PUCCH based on a first priority for the first PUCCH and a second priority for the second PUCCH, the one of the first PUCCH and the second PUCCH having a higher priority than the other of the first PUCCH and the second PUCCH, the first PUCCH being a PUCCH with multi-slot transmission; as well as an uplink (UL) receiver configured to receive the one of the first PUCCH and the second PUCCH in the time slot and not to receive the other of the first PUCCH and the second PUCCH in the time slot, wherein: The first priority for the first PUCCH is based on a type of the first UCI, and the second priority for the second PUCCH is based on a type of the second UCI, In a case where the type of the first UCI is channel state information CSI having a higher priority, and the type of the second UCI is CSI having a lower priority, the one of the first PUCCH and the second PUCCH is the first PUCCH, and the other of the first PUCCH and the second PUCCH is the second PUCCH, wherein Based on a priority rule that (a) the semi-persistent CSI is defined as having a higher priority than the periodic CSI, and (b) determining, by the user equipment, that the semi-persistent CSI and the periodic CSI are the CSI with a higher priority and the CSI with a lower priority, respectively, the second PUCCH is not received and the first PUCCH is received, The second PUCCH is another PUCCH with multi-slot transmission.

3. A communication method of a user equipment, comprising: Determining that a first physical uplink control channel PUCCH carrying first uplink control information UCI overlaps with a second PUCCH carrying second UCI in a time slot; determining one of the first PUCCH and the second PUCCH based on a first priority for the first PUCCH and a second priority for the second PUCCH, the one of the first PUCCH and the second PUCCH having a higher priority than the other of the first PUCCH and the second PUCCH, the first PUCCH being a PUCCH with multi-slot transmission; as well as The one of the first PUCCH and the second PUCCH is transmitted in the time slot, and the other of the first PUCCH and the second PUCCH is not transmitted in the time slot, wherein, The first priority for the first PUCCH is based on a type of the first UCI, and the second priority for the second PUCCH is based on a type of the second UCI, In a case where the type of the first UCI is channel state information CSI having a higher priority and the type of the second UCI is CSI having a lower priority, the one of the first PUCCH and the second PUCCH is the first PUCCH, and the other of the first PUCCH and the second PUCCH is the second PUCCH, and Based on a priority rule that the semi-persistent CSI is defined as having a higher priority than the periodic CSI, determining that the semi-persistent CSI and the periodic CSI are the CSI with a higher priority and the CSI with a lower priority, respectively, The second PUCCH is another PUCCH with multi-slot transmission.

4. A communication method of a base station device, comprising: Determining that a first physical uplink control channel PUCCH carrying first uplink control information UCI overlaps with a second PUCCH carrying second UCI in a time slot; determining one of the first PUCCH and the second PUCCH based on a first priority for the first PUCCH and a second priority for the second PUCCH, the one of the first PUCCH and the second PUCCH having a higher priority than the other of the first PUCCH and the second PUCCH, the first PUCCH being a PUCCH with multi-slot transmission; as well as receiving the one of the first PUCCH and the second PUCCH in the time slot, and not receiving the other of the first PUCCH and the second PUCCH in the time slot, wherein: The first priority for the first PUCCH is based on a type of the first UCI, and the second priority for the second PUCCH is based on a type of the second UCI, In a case where the type of the first UCI is channel state information CSI having a higher priority, and the type of the second UCI is CSI having a lower priority, the one of the first PUCCH and the second PUCCH is the first PUCCH, and the other of the first PUCCH and the second PUCCH is the second PUCCH, wherein Based on a priority rule that (a) the semi-persistent CSI is defined as having a higher priority than the periodic CSI, and (b) determining, by the user equipment, that the semi-persistent CSI and the periodic CSI are the CSI with a higher priority and the CSI with a lower priority, respectively, the second PUCCH is not received and the first PUCCH is received, The second PUCCH is another PUCCH with multi-slot transmission.

Images