Terminal, radio communication method, base station, and system

Abstract

To solve the problem in which: inability to appropriately control a method for increasing uplink resources may reduce system performance.SOLUTION: A terminal according to an aspect of the present disclosure receives information indicating a first period that is used for reception of at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH), and a second period that is used for transmission of a physical uplink control channel (PUCCH), and in a time resource in which the first period and the second period at least partially overlap each other, controls reception of at least one of the DCI and the PDSCH and transmission of the PUCCH. The DCI, the PDSCH, and the PUCCH are mapped in one operation band that is defined as the combination of an operation band for an uplink and an operation band for a downlink. The operation band for an uplink is equal to the operation band for a downlink.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a wireless communication method, a base station, and a system in a next-generation mobile communication system. [Background technology]

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (for example, NR), it is expected that multiple user terminals (user equipment (UE)) will communicate in an ultra-high density and high traffic environment.

[0006] In such an environment, it is expected that uplink resources will be insufficient.

[0007] However, in the current NR specifications, methods for increasing uplink resources have not been fully considered. If the methods are not properly controlled, there is a risk of system performance degradation, such as a decrease in throughput.

[0008] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, a base station, and a system that improve resource utilization efficiency. [Means for solving the problem]

[0009] A terminal according to one embodiment of the present disclosure has a receiving unit that receives information indicating a first period used to receive at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH) and information indicating a second period used to transmit a physical uplink control channel (PUCCH), and receives at least one of the DCI and the PDSCH in a time resource in which at least a portion of the first period and the second period overlap, and a transmitting unit that transmits the PUCCH in the time resource, wherein the at least one of the DCI and the PDSCH and the PUCCH are mapped to different frequency resources within one operating band. [Effects of the Invention]

[0010] According to one aspect of the present disclosure, resource utilization efficiency can be improved. [Brief explanation of the drawings]

[0011] [Figure 1] 1A and 1B are diagrams illustrating an example of receiving DCI / PDSCH and transmitting PUCCH using multicast. [Figure 2] 2A to 2C are diagrams showing an example of reception of DCI / PDSCH and transmission of PUCCH according to the first embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of reception of DCI / PDSCH and transmission of PUCCH according to the second embodiment. [Figure 4] 4A and 4B are diagrams illustrating an example of PDSCH reception and PUCCH transmission according to embodiment 2-1-2. [Figure 5] 5A and 5B are diagrams illustrating an example of PDSCH reception and PUCCH transmission according to embodiment 2-2. [Figure 6] 6A and 6B are diagrams illustrating an example of PDSCH reception and PUCCH transmission according to embodiment 2-3. [Figure 7] 7A and 7B are diagrams showing an example of PDSCH reception and PUCCH transmission according to the third embodiment. [Figure 8] 8A and 8B are diagrams showing an example of PDSCH reception and PUCCH transmission according to the second embodiment and the modified example of the third embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (NR multicast / broadcast) In NR up to Rel. 16, transmission of at least one of a signal and a channel (hereinafter referred to as a signal / channel) from a network (NW (e.g., a base station)) to a UE is basically unicast transmission. In this case, it is assumed that each UE receives the same downlink (DL) data signal / channel (e.g., a downlink shared channel (PDSCH)) transmitted from the NW to multiple UEs using multiple reception opportunities corresponding to multiple beams (or panels) of the NW.

[0013] In addition, in an environment with high density and high traffic, such as a stadium where many UEs are geographically concentrated, it is expected that multiple UEs will simultaneously receive the same signal / channel. In such a case, if multiple UEs exist in the same area and each UE receives the same signal / channel by unicast, it is possible to ensure communication reliability, but it is thought that this will reduce resource utilization efficiency.

[0014] On the other hand, there are also use cases (e.g., television, radio, etc.) where multicast (broadcast) is performed to transmit the same DL data signal / channel to multiple UEs. However, in such use cases, it has been difficult to ensure reliability because the network does not confirm the reception of the DL data signal / channel from each UE.

[0015] In NR Rel. 17 and later, transmission of delivery acknowledgement information (which may be referred to as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information, HARQ-ACK, ACK / NACK, etc.) for PDSCH using multicast is being considered.

[0016] In this case, the UE receives Downlink Control Information (DCI) / PDSCH in a certain DL reception period, and transmits HARQ-ACK for the PDSCH in an UL transmission period that is at least temporally different from the DL reception period.

[0017] However, when the transmission / reception time ratio (e.g., DL:UL=4:1) is considered for Time Division Duplex (TDD), there may be cases where the number of HARQ-ACK transmission opportunities for PDSCH is fewer than the number of PDSCH reception opportunities. In such cases, the UE cannot transmit HARQ-ACK frequently, which may result in delays in HARQ-ACK transmission. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is a concern about signal / channel congestion during UL transmission opportunities.

[0018] FIG. 1A is a diagram showing an example of reception of a DCI / PDSCH using multicast and transmission of a PUCCH. FIG. 1A shows an example of reception of a DCI / PDSCH using multicast, which will be considered up to Rel. 17, and transmission of a PUCCH (HARQ-ACK) for the PDSCH. A UE receives a DCI / PDSCH #1 using multicast in DL reception period #1, and transmits a HARQ-ACK for the DCI / PDSCH #1 on PUCCH #1 in UL transmission period #1. The UE also receives a DCI / PDSCH #2 using multicast in DL reception period #2, and transmits a HARQ-ACK for the DCI / PDSCH #2 on PUCCH #2 in UL transmission period #2. Gaps (which may be referred to as timing advance (TA) gaps, etc.) may be set between DL reception period #1 and UL transmission period #1, and between DL reception period #2 and UL transmission period #2, respectively, based on the physical location of the UE.

[0019] As described above, in the example shown in FIG. 1A, the UE cannot transmit HARQ-ACKs frequently, and there is a concern that delays in HARQ-ACK transmission may occur.

[0020] Therefore, the present inventors have conceived a method for flexibly allocating uplink resources to UEs.

[0021] FIG. 1B is a diagram showing another example of reception of DCI / PDSCH using multicast and transmission of PUCCH. FIG. 1B shows an example of reception of DCI / PDSCH using multicast after Rel. 17 and transmission of PUCCH (HARQ-ACK) for PDSCH. In the example shown in FIG. 1B, similar to FIG. 1A, reception of DCI / PDSCH using multicast and transmission of PUCCH are performed. The inventors have conceived a method of transmitting PUCCH in an UL transmission period that is temporally included in a DL reception period, as shown in the example of FIG. 1B.

[0022] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0023] In the drawings in this disclosure, a case is described in which the DL reception period includes the UL transmission period, but this is not limited to this, and the following embodiments are also applicable to a case in which at least a part of the DL reception period and the UL transmission period overlap.

[0024] (Wireless communication method) Multicast / broadcast may be configured from the NW to multiple UEs, and the multicast / broadcast may be configured using higher layer signaling.

[0025] A UE configured for multicast / broadcast may receive a PDSCH scheduled by a blindly detected (received) DCI (PDCCH) in at least one of a PDCCH monitoring occasion, a search space, and a control resource set (CORESET) corresponding to the multicast / broadcast. The PDSCH may be referred to as a multicast-based PDSCH.

[0026] Furthermore, a UE configured with multicast / broadcast may transmit HARQ-ACK / NACK for a PDSCH using multicast using PUCCH or PUSCH.

[0027] The HARQ-ACK / NACK may be transmitted as one bit for each transport block (TB) / codeword (CW) of a PDSCH using multicast, or as one bit for each of multiple TBs / CWs.

[0028] In the present disclosure, multicast may be interchangeably read as broadcast (broadcast information). Furthermore, a PDSCH using multicast may be interchangeably read as a PDSCH common to multiple UEs, a common PDSCH, a shared PDSCH, a multicast PDSCH, a broadcast (broadcast) PDSCH, etc.

[0029] In the present disclosure, A / B may mean at least one of A and B. In the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0030] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

[0031] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0032] The physical layer signaling may be, for example, downlink control information (DCI).

[0033] In the present disclosure, the PUCCH / PUSCH resources for HARQ-ACK transmission corresponding to the multicast PDSCH may be simply referred to as HARQ-ACK transmission resources.

[0034] In this disclosure, each of the multiple UEs may be referred to as a respective UE, or simply as a UE.

[0035] In the present disclosure, a DCI format dedicated to a multicast PDSCH may be newly defined. When a multicast PDSCH is scheduled using a DCI format dedicated to a multicast PDSCH, a UE may report UE capability information (UE Capability) regarding whether the multicast PDSCH-dedicated DCI format is supported to a network (NW, for example, a gNB). In this case, the number of combinations of DCI sizes (payload size, number of bits) increases, the number of blind DCI detections performed by the UE increases, and the complexity of UE operation increases. Therefore, only UEs that support the DCI format may monitor the DCI format.

[0036] In the present disclosure, the multicast PDSCH may be interpreted as a reception occasion, an occasion, a reception period, downlink (DL) data, data, a transport block (TB), a codeword (CW), a PDSCH, or the like.

[0037] Multiple DCIs may each schedule one or more multicast PDSCHs (reception occasions). The same DL data may be transmitted to multiple UEs in each of the one or more multicast PDSCHs. In this disclosure, each of the multiple DCIs may be referred to as a UE-specific DCI.

[0038] One DCI with QCL#x may schedule DL data with QCL#x' to multiple UEs.

[0039] DCI detected in a PDCCH monitoring occasion associated with a QCL may schedule DL data in a receiving occasion associated with that QCL.

[0040] PDCCH monitoring in multiple DCIs may follow at least one of the following PDCCH monitoring methods 1 to 3.

[0041] [PDCCH monitoring method 1] Multiple DCIs may be transmitted (received) in a common search space or a group common search space. The UE may select a PDCCH monitoring occasion corresponding to a QCL configured / indicated for the PDCCH for receiving the DCI.

[0042] [PDCCH monitoring method 2] A common search space or a group common search space may be configured for each of multiple QCLs. The UE may select a search space corresponding to a QCL configured / instructed for the PDCCH for receiving DCI.

[0043] [PDCCH monitoring method 3] A common CORESET or a group common CORESET may be configured for each of multiple QCLs. The UE may select a search space corresponding to a QCL configured / instructed for the PDCCH for receiving DCI.

[0044] The UE detects DCI by monitoring a group scheduling search space configured as a common search space or a group common search space.

[0045] The search space for group scheduling may differ depending on the QCL assumption. For example, the search space for group scheduling may have different time-domain resources (symbols, slots, etc.) depending on the QCL assumption.

[0046] The UE may assume that the same DL data is scheduled in each PDCCH monitoring occasion (DCI in each PDCCH monitoring occasion) within the group scheduling search space.

[0047] The UE may have the search space for group scheduling configured by higher layer signaling.

[0048] In the present disclosure, UE-specific (or dedicated) DCI may be cyclic redundancy check (CRC) scrambled with a UE-specific Radio Network Temporary Identifier (RNTI) (e.g., a cell (C-) RNTI) or may be CRC-scrambled with a UE-common RNTI. Also, UE-specific DCI may be CRC-scrambled with an RNTI dedicated to a multicast / broadcast schedule.

[0049] One DCI for multiple UEs may schedule DL data for multiple UEs, and one DCI may schedule the same DL data in one or more multicast PDSCHs. In this disclosure, this one DCI may be referred to as a UE-common DCI.

[0050] The DCI may be transmitted in a common search space or a group common search space. The PDCCH monitoring occasion for the DCI may vary depending on the quasi-co-location (QCL) used by the UE. The UE may select the PDCCH monitoring occasion based on multiple QCL assumptions.

[0051] One DL data may be one codeword (CW) or one transport block (TB). The same DL data may have the same size (e.g., transport block size (TBS)) or different sizes.

[0052] In the present disclosure, a DCI common to multiple UEs (UE-common) may be CRC-scrambled with a UE-specific RNTI (e.g., C-RNTI) or a UE-common RNTI, and the UE-specific DCI may be CRC-scrambled with an RNTI dedicated to a multicast / broadcast schedule.

[0053] In the present disclosure, the search space dedicated to the multicast / broadcast schedule may be a common search space or a search space for group scheduling configured as a group common search space.

[0054] A UE may transmit a HARQ-ACK for a PDSCH that uses multicast on a UE-specific PUCCH resource. Alternatively, a UE may transmit a HARQ-ACK for a PDSCH that uses multicast on a PUCCH resource that is common to multiple UEs. When a UE transmits a negative acknowledgement (NACK) on a PUCCH resource that is common to multiple UEs, it may use a sequence-based PUCCH (e.g., a PUCCH using PUCCH format 0) resource.

[0055] The UE may follow at least one of HARQ-ACK transmission method 1 and transmission method 2 for HARQ-ACK for PDSCH using multicast.

[0056] [HARQ-ACK transmission method 1 (ACK / NACK feedback)] For a HARQ-ACK for a PDSCH that uses multicast, the UE may send an acknowledgement (ACK) if the reception process (e.g., demodulation, decoding) of the PDSCH is successful, or may send a negative acknowledgement (NACK) if not.

[0057] [HARQ-ACK transmission method 2 (NACK-only feedback)] Regarding the HARQ-ACK for a PDSCH using multicast, the UE may not transmit a signal if the reception process (e.g., demodulation, decoding) of the PDSCH is successful, and may transmit a negative acknowledgement (NACK) if not. In this case, resources for transmitting the ACK may not be allocated to the UE.

[0058] In the present disclosure, the terms port, antenna, antenna port, panel, beam, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), spatial relationship information, spatial relationship, state of Transmission Configuration Indication (TCI) (TCI-state), Quasi-Co-Location (QCL) assumption, Control Resource Set (CORESET), PDSCH, codeword, base station, predetermined antenna port (e.g., Demodulation Reference Signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group, panel group, beam group, spatial relationship group, PUCCH group), and CORESET pool may be interpreted as interchangeable.

[0059] In the present disclosure, if a PUCCH resource is configured for a UE but the UE does not actually transmit PUCCH, the UE may receive PDSCH in the same time resource (eg, the same symbol) as the PUCCH resource.

[0060] Each embodiment of the present disclosure will be described below using a PDSCH / PDCCH that uses multicast as an example, but can also be applied to a unicast PDSCH / PDCCH as appropriate.

[0061] The PUCCH resource described in the present disclosure may be any PUCCH resource or a specific PUCCH resource, such as a PUCCH resource to which HARQ-ACK information for a PDSCH is mapped, or a PUCCH resource to which HARQ-ACK information for a PDSCH using multicast is mapped.

[0062] In the present disclosure, PDSCH reception and PUCCH transmission may be performed using the same BWP / CC / band, or different BWP / CC / bands.

[0063] In the present disclosure, at least one of the waveform, sequence index, cyclic shift index (cyclic shift number), coding method, orthogonal cover code (OCC) index, and number of bits of a PUCCH transmitted in a DL reception period (reception period of a DCI / PDSCH) may be different from that of a PUCCH defined up to Rel. 15 or 16. Furthermore, the PUCCH transmitted in a DL reception period (reception period of a PDSCH) may be a sequence-based PUCCH (for example, a PUCCH using PUCCH format 0).

[0064] In the present disclosure, the PUCCH resource may be configured / indicated to the UE using at least one of higher layer signaling and DCI. The PUCCH resource may be indicated by DCI using a specific field (PUCCH resource indicator (PRI) field / control channel element (CCE) index field) included in the DCI.

[0065] In the following embodiments, an uplink operating band is equal to a downlink operating band, and DL signals / channels (e.g., PDCCH / PDSCH) and UL signals / channels (e.g., PUCCH / PUSCH) may be mapped (allocated) within one operating band defined as a combination of the uplink operating band and the downlink operating band. The operating band may be different from the TDD operating band or different from at least one of the TDD operating band, the FDD operating band, and the supplementary uplink (SUL) operating band. In the following embodiments, DL signals / channels and UL signals / channels may be mapped to different frequency resources within the one operating band. In the following embodiments, DL signals / channels and UL signals / channels in different frequency resources within the one operating band may overlap in the time domain. In the present disclosure, A overlaps with B, A overlaps with B, and at least a portion of A overlaps with at least a portion of B may be interpreted as interchangeable.

[0066] In each embodiment of the present disclosure, a UE may report (transmit) to a NW whether it has the capability (hereinafter, may be referred to as UE capability information) to simultaneously receive DL signals / channels and transmit UL signals / channels in a period (UL transmission period) used for transmitting UL signals / channels, which is set to the same time resource as at least a part of a period (DL reception period) used for receiving DL signals / channels. The UE capability information may indicate whether the UE supports simultaneously receiving DL signals / channels and transmitting UL signals / channels within one operating band.

[0067] The UE capability information may be defined as whether simultaneous reception of a PDCCH / PDSCH and transmission of a PUCCH is supported. In other words, the capability information may be defined as whether full duplex communication is applicable. In the following embodiments, simultaneous reception of a DL signal / channel and transmission of a UL signal / channel within one operating band and full duplex communication may be interpreted as interchangeable.

[0068] The UE capability information may also be defined as the number of channels / RSs that can be simultaneously transmitted / received.The UE capability information may also be defined as the number of channels / RSs that can be simultaneously transmitted / received within one operating band.

[0069] Note that the embodiments of the present disclosure may be applied under at least one of the following conditions: when the UE reports UE capabilities corresponding to the at least one of the above to the NW; and when the at least one UE capability is configured / activated / instructed to the UE by higher layer signaling. The embodiments of the present disclosure may be applied when a specific higher layer parameter is configured / activated / instructed to the UE.

[0070] First Embodiment The time resources allocated for transmitting UL signals / channels (UL transmission interval) may overlap with the time resources allocated for receiving DL signals / channels (DL reception interval). The UE may transmit the UL signals / channels in the UL transmission interval that overlaps with the DL reception interval. In the first embodiment, the reception of the signals / channels in the DL reception interval and the transmission of the signals / channels in the UL transmission interval may occur simultaneously.

[0071] In the first embodiment, the UE is configured with PUCCH resources used for HARQ-ACK transmission during at least a portion of the DL reception period for receiving the PDCCH (DCI) / PDSCH, and may receive the PDCCH (DCI) / PDSCH and transmit the PUCCH (HARQ-ACK) in the same time resource (e.g., symbol).

[0072] In the first embodiment, the receiving panel / antenna / beam / TCI state / spatial relationship / QCL assumption used for receiving DL signals / channels may be limited to a case where it is different from the receiving panel / antenna / beam / TCI state / spatial relationship / QCL assumption used for receiving UL signals / channels (embodiment 1-1). Embodiment 1-1 may be used in beamforming operation using a specific frequency range (e.g., FR2 / FR4).

[0073] Furthermore, in the first embodiment, when the above UE capability information is reported, the receiving panel / antenna / beam / TCI state / spatial relationship / QCL assumption used to receive DL signals / channels may be the same as or different from the receiving panel / antenna / beam / TCI state / spatial relationship / QCL assumption used to receive UL signals / channels (embodiment 1-2).

[0074] 2A is a diagram illustrating an example of receiving DCI / PDSCH and transmitting PUCCH according to the first embodiment. In the example illustrated in FIG. 2A, the time resource allocated for transmitting PUCCH (UL transmission period) overlaps with the time resource allocated for receiving DCI / PDSCH (DL reception period). In the example illustrated in FIG. 2A, the UE may receive DCI / PDSCH and transmit PUCCH simultaneously.

[0075] 2B is a diagram illustrating an example of transmission and reception of signals / channels according to embodiment 1-1. In the example illustrated in FIG. 2B, a UE receives DL signals / channels (e.g., PDSCH, DCI) and transmits UL signals / channels (e.g., PUCCH) using different transmission and reception antennas / panels.

[0076] 2C is a diagram illustrating an example of transmission and reception of signals / channels according to embodiment 1-2. In the example illustrated in FIG. 2C, a UE receives DL signals / channels (e.g., PDSCH, DCI) and transmits UL signals / channels (e.g., PUCCH) using the same transmitting and receiving antenna / panel.

[0077] As described above, according to the first embodiment, it is possible to ensure an opportunity to transmit a HARQ-ACK for a PDSCH, and to reduce a delay in transmitting a HARQ-ACK.

[0078] <Second embodiment> The UE may transmit a UL signal / channel in a UL transmission period that overlaps with a DL reception period. In the second embodiment, the reception of the signal / channel in the DL reception period and the transmission of the signal / channel in the UL transmission period do not have to be performed simultaneously. The second embodiment described below is also applicable to a UE that has not reported the UE capability information to the NW.

[0079] For example, in an UL transmission period within a DL reception period, the UE may not receive the PDSCH. Such a period during the DL reception period during which the UE does not receive a DL signal / channel may be referred to as a DL non-reception period. It may be specified that the UE is not required to receive the PDSCH in an UL transmission period within the DL reception period.

[0080] A specific period during which no signal / channel is transmitted or received may be set at least either before or after the DL non-reception period. The specific period may be called a gap, a TA gap, a transmission / reception switching gap, etc. The UE may not receive the PDCCH / PDSCH during the gap and the DL non-reception period. In other words, the UE may drop the DCI / PDSCH during the gap and the DL non-reception period.

[0081] In the present disclosure, the term "drop" may be interpreted as "abort," "cancel," "puncture," or the like.

[0082] The specific period may be defined in advance in a specification, may be set in the UE by higher layer signaling, or may be reported to the NW as UE capability information.

[0083] 3 is a diagram showing an example of reception of DCI / PDSCH and transmission of PUCCH according to the second embodiment. In the example shown in FIG. 3, the UL transmission period allocated for transmission of PUCCH overlaps with the DL reception period allocated for reception of DCI / PDSCH. In this case, the UE does not receive DCI / PDSCH in the time resource (DL non-reception period) that overlaps with the time resource for PUCCH transmission and in the gap period set before the time resource.

[0084] According to the second embodiment, when the coding rate of the PDSCH is sufficiently low, the UE can correctly decode the PDSCH even if some PDSCH resources are missing.

[0085] <<Embodiment 2-1>> In the second embodiment, the DL signal / channel that can be transmitted in the DL non-reception period (and gap) may be only the PDSCH (embodiment 2-1-1).

[0086] The UE may not assume or expect that reception of PDCCH / DCI is configured / instructed during DL non-reception periods (and gaps). For example, the UE may not assume that reception of PDCCH / DCI is configured / instructed at the same timing as PUCCH resources for transmitting HARQ-ACK for PDSCH.

[0087] Furthermore, when configured / instructed to receive PDCCH / DCI during DL non-reception periods (and gaps), the UE may receive the PDCCH / DCI. For example, when configured / instructed to receive PDCCH / DCI at the same timing as the PUCCH resource for transmitting HARQ-ACK for PDSCH, the UE may receive the PDCCH / DCI. The UE does not need to transmit HARQ-ACK at the timing to receive the PDCCH / DCI.

[0088] In addition, in the second embodiment, the UE may determine to transmit a UL signal / channel in the same time resource as at least a portion of the DL reception period based on the coding rate of the DL signal / channel (e.g., PDSCH) (embodiment 2-1-2).

[0089] For example, if the coding rate of the PDSCH is less than (or equal to) a specific value and a PUCCH resource for transmitting the HARQ-ACK is configured / instructed during the DL reception period, the UE may transmit the HARQ-ACK on the PUCCH resource.

[0090] For example, if the coding rate of the PDSCH is equal to or greater than a specific value (larger), the UE does not need to assume that the PDSCH and PUCCH resources are configured / instructed at the same timing.

[0091] Also, for example, if the coding rate of the PDSCH is equal to or greater than a specific value and the PDSCH and PUCCH resources are configured / instructed at the same timing, the UE may receive the PDSCH but not transmit the PUCCH.

[0092] The specific value may be explicitly notified to the UE using higher layer signaling / physical layer signaling, or may be implicitly determined by the UE from at least one of the PDSCH resources, demodulation reference signal (DMRS) settings, transport block (TB) size, and modulation and coding scheme (MCS) index indicated by the higher layer signaling / physical layer signaling.

[0093] In the present disclosure, "greater than" may be interchangeably read as "greater than or equal to," "smaller than" may be interchangeably read as "smaller than," and "greater than" may be interchangeably read as "smaller than."

[0094] The coding rate of the PDSCH may be interpreted as the PDSCH resource, the DMRS setting in the PDSCH resource, the TB size in the PDSCH resource, or the MCS index in the PDSCH resource.

[0095] 4A and 4B are diagrams illustrating an example of PDSCH reception and PUCCH transmission according to embodiment 2-1-2. The example illustrated in Fig. 4A illustrates a case where the coding rate of the PDSCH is equal to or lower than a specific value. In the example illustrated in Fig. 4A, the UE transmits the PUCCH in an UL transmission period that is set to the same time resource as at least a part of the DL reception period used for receiving the PDSCH. The UE does not receive DCI / PDSCH in a time resource (DL non-reception period) that overlaps with the PUCCH transmission resource and in a gap period that is set before the time resource.

[0096] On the other hand, the example shown in Fig. 4B shows a case where the coding rate of the PDSCH is higher than a specific value. In the example shown in Fig. 4B, the UE does not transmit the PUCCH, but only receives the PDSCH.

[0097] <<Embodiment 2-2>> In embodiment 2-2, the operation of multiple UEs will be described. In embodiment 2-2, the PDCCH / PDSCH transmitted to multiple UEs may be common to the multiple UEs. Also, in embodiment 2-2, the UE may transmit HARQ-ACK in a UE-specific PUCCH resource. The UE may be configured / instructed to use at least one of higher layer signaling and DCI to configure / instruct the UE-specific PUCCH resource. At least one of a specific field (PUCCH resource indicator (PRI) field) included in the DCI and an index of the first control channel element (CCE) of the PDCCH carrying the DCI may be used to indicate the PUCCH resource.

[0098] In embodiment 2-2, the PUCCH resources for multiple UEs may not overlap in time, that is, the PUCCH resources for multiple UEs may be time-division multiplexed (TDM).

[0099] The UE does not need to receive the PDSCH at the timing of its own PUCCH transmission, and a gap may be set before / after the timing of the PUCCH transmission.

[0100] 5A and 5B are diagrams showing an example of PDSCH reception and PUCCH transmission according to embodiment 2-2. FIGS. 5A and 5B show PDSCH reception and PUCCH transmission for UE#1 and UE#2, respectively. In the example shown in FIGS. 5A and 5B, a common PDSCH is transmitted from the network to UE#1 and UE#2. The DL reception period shown in FIGS. 5A and 5B is common to UE#1 and UE#2.

[0101] 5A and 5B, UE#1 transmits PUCCH#1 in an UL transmission period that is set to the same time resource as at least a part of the DL reception period used to receive the PDSCH. UE#2 transmits PUCCH#2 in an UL transmission period that is set to the same time resource as at least a part of the DL reception period used to receive the PDSCH. Each UE does not receive DCI / PDSCH in the time resource (DL non-reception period) that overlaps with the PUCCH transmission resource or in the gap period set before that time resource.

[0102] In the drawings in the present disclosure, the gaps (TA gaps) set for multiple UEs / multiple DL non-reception periods may be different for each UE or may be different for each DL non-reception period.

[0103] <<Embodiment 2-3>> In embodiments 2-3, the UE sequentially decodes multiple DL signals / channels / DL data, and when it determines that an error has occurred (reception processing has failed), it may transmit a UL signal / channel within the time resource (DL reception period) allocated to the multiple DL signals / channels / DL data.

[0104] For example, when the UE sequentially decodes multiple PDSCHs and determines that an error has occurred (reception processing has failed), it may transmit a NACK for the PDSCH for which reception processing has failed during an UL transmission period in the same time resource (e.g., symbol) as part of the DL reception period.

[0105] In embodiments 2 and 3, sequential decoding of a plurality of PDSCHs may mean sequential reception (decoding) of a plurality of PDSCHs / code blocks (CBs) / code words (CWs) / code block groups (CBGs). Furthermore, sequential decoding of a plurality of PDSCHs may mean sequential reception (decoding) of a plurality of PDSCHs from the start symbol of one PDSCH / CB / CW / CBG. Furthermore, the PUCCH resource used for HARQ-ACK transmission may be configured / instructed for each PDSCH / CB / CW / CBG.

[0106] The UE may not be required to receive (or may not receive) a DL signal / channel (PDSCH) in the same time resource, and may receive a DL signal / channel (PDSCH) in the same time resource if the UE reports to the NW that it supports the capability to simultaneously receive DL signals / channels and transmit UL signals / channels.

[0107] The PUCCH resources used for transmitting HARQ-ACK for each PDSCH / CB / CW / CBG may be configured / instructed to the UE using higher layer signaling / physical layer signaling. When the UE is configured to receive another PDSCH / CB / CW / CBG in a symbol for transmitting a PUCCH, the UE may not be required to receive (or may not receive) the other PDSCH / CB / CW / CBG in the symbol for transmitting the PUCCH. Also, when the UE reports to the NW that it supports the capability to simultaneously receive a DL signal / channel and transmit a UL signal / channel, the UE may receive the other PDSCH / CB / CW / CBG in the symbol for transmitting the PUCCH.

[0108] The UE may sequentially decode multiple DL signals / channels and, if it determines that no error has occurred, may not transmit a UL signal / channel. For example, the UE may sequentially decode multiple PDSCHs and, if it determines that no error has occurred, may not transmit a PUCCH (HARQ-ACK).

[0109] Note that the second and third embodiments are applicable to both the UE to which the HARQ-ACK transmission method 1 is applied and the UE to which the HARQ-ACK transmission method 2 is applied.

[0110] Hereinafter, an example will be described in which embodiment 2-3 is applied to a UE to which the above-mentioned HARQ-ACK transmission method 1 is applied (embodiment 2-3-1). In embodiment 2-3-1, when the UE is configured to receive a PDSCH in a time resource that overlaps with a UL transmission period (for example, a PUCCH resource) and the UE has successfully decoded the PDSCH, the UE may receive the PDSCH in the time resource without transmitting an ACK for the PDSCH.

[0111] Furthermore, in embodiment 2-3-1, when the UE is configured to receive a PDSCH in a time resource that overlaps with the UL transmission period in time, if the UE fails to decode the PDSCH, the UE may transmit a NACK for the PDSCH and not receive the PDSCH in the time resource. Note that in the present disclosure, ACK and NACK may be interpreted as interchangeable.

[0112] Furthermore, in embodiment 2-3-1, when the UE is configured to receive a PDSCH in a time resource that overlaps with the UL transmission period and fails to decode the PDSCH, the UE may transmit the NACK and one or more untransmitted ACKs prior to the PDSCH in the resource for transmitting a NACK for the PDSCH, and may not receive the PDSCH in the time resource. In this case, the UE may not transmit one or more untransmitted ACKs.

[0113] 6A is a diagram showing an example of PDSCH reception and PUCCH transmission according to embodiment 2-3-1. In the example shown in FIG. 6A, a UE is scheduled for a plurality of PDSCHs (PDSCHs #1-#4). The UE is also instructed to use a plurality of PUCCH resources (PUCCHs #1-#4) as resources for transmitting HARQ-ACKs corresponding to PDSCHs #1-#4, respectively.

[0114] In the example shown in Figure 6A, the UE successfully receives PDSCH #1 and PDSCH #2, but fails to receive PDSCH #3. In this case, the UE does not transmit ACKs on PUCCH #1 and PUCCH #2, and transmits ACKs for PDSCH #1 and PDSCH #2 and a NACK for PDSCH #3 on PUCCH #3. The UE does not receive PDSCH #4, which overlaps in time with PUCCH #3.

[0115] 6A, the UE may transmit, in PUCCH #4, ACKs for PDSCH #1 and PDSCH #2, and a NACK for PDSCH #3. Also, the UE does not need to transmit a HARQ-ACK (PUCCH #4) for PDSCH #4 that overlaps in time with the PUCCH resource (PUCCH #3) for transmitting a NACK.

[0116] Hereinafter, an example will be described in which embodiment 2-3 is applied to a UE to which the above-mentioned HARQ-ACK transmission method 2 is applied (embodiment 2-3-2). In embodiment 2-3-2, when the UE is configured to receive a PDSCH in a time resource that overlaps with a UL transmission period (for example, a PUCCH resource) and the UE has successfully decoded the PDSCH, the UE may receive the PDSCH in the time resource without transmitting an ACK for the PDSCH.

[0117] Furthermore, in embodiment 2-3-2, when the UE is configured to receive a PDSCH in a time resource that overlaps with the UL transmission period and fails to decode the PDSCH, the UE may transmit a NACK for the PDSCH and not receive the PDSCH in the time resource. In this case, the UE may not explicitly notify / report a NACK for the PDSCH that was not received to the NW.

[0118] Fig. 6B is a diagram showing an example of reception of a PDSCH and transmission of a PUCCH according to embodiment 2-3-2. In the example shown in Fig. 6B, the allocation of PDSCH and PUCCH scheduled for UE is the same as in Fig. 6A.

[0119] In the example shown in Figure 6B, the UE successfully receives PDSCH #1 and PDSCH #2, but fails to receive PDSCH #3. In this case, the UE does not transmit ACKs on PUCCH #1 or PUCCH #2, and transmits only a NACK for PDSCH #3 on PUCCH #3. The UE does not receive PDSCH #4, which overlaps in time with PUCCH #3.

[0120] 6B, the UE may transmit a NACK for PDSCH #3 in PUCCH #4. Also, the UE does not need to transmit a HARQ-ACK (PUCCH #4) for PDSCH #4 that overlaps in time with the PUCCH resource (PUCCH #3) for transmitting a NACK.

[0121] Although the start and end positions of each PDSCH and each PUCCH shown in Figures 6A and 6B above are the same, this is not limited to this, and embodiments 2-3 can also be applied when the periods of each PDSCH and each PUCCH partially overlap in time.

[0122] As described above, according to the second embodiment, it is possible to flexibly control the reservation of transmission opportunities for HARQ-ACK for PDSCH, and to reduce delays in HARQ-ACK transmission.

[0123] <Third embodiment> In the third embodiment, an example will be described in which a plurality of UEs each transmit a HARQ-ACK during a DL reception period in which a PDCCH / PDSCH using multicast is transmitted. The example described in embodiment 2-2 may be applied to a plurality of UEs receiving a multicast PDCCH / PDSCH.

[0124] The PDCCH / PDSCH using multicast in this embodiment may be a group common PDCCH / PDSCH. The group may refer to a PDSCH group.

[0125] In the PDCCH / PDSCH using multicast, the UE may assume that data / control information for each UE is mapped to resources that are orthogonal in time (non-overlapping in the time domain) among multiple UEs. The UE may receive information about resources for its own UE in advance using higher layer signaling / physical layer signaling. The information about resources for its own UE may be at least one of a time resource allocation, a frequency resource allocation, a code applied to the resource, a sequence applied to the resource, and a cyclic shift applied to the resource.

[0126] During the DL reception period, the UE may transmit the PUCCH in a time resource that does not overlap with the resource to which the multicast PDCCH / PDSCH for the UE is configured / mapped.

[0127] 7A and 7B are diagrams showing an example of PDSCH reception and PUCCH transmission according to the third embodiment. FIGS. 7A and 7B respectively show PDSCH reception and PUCCH transmission by UE#1 and UE#2. In the example shown in FIGS. 7A and 7B, a PDSCH using multicast is transmitted from the network to UE#1 and UE#2. The DL reception period shown in FIGS. 7A and 7B is common to UE#1 and UE#2. In the example shown in FIGS. 7A and 7B, each UE receives the PDSCH in the PDSCH resources configured / instructed for the UE.

[0128] 7A and 7B, UE#1 transmits PUCCH#1 in an UL transmission period that is set to the same time resource as at least a part of the DL reception period used to receive the PDSCH. UE#2 transmits PUCCH#2 in an UL transmission period that is set to the same time resource as at least a part of the DL reception period used to receive the PDSCH. Each UE does not receive DCI / PDSCH in the time resource (DL non-reception period) that overlaps with the PUCCH transmission resource or in the gap period set before that time resource.

[0129] As described above, according to the third embodiment, it is possible to flexibly control the allocation of HARQ-ACK transmission opportunities for the PDSCHs of each of a plurality of UEs, and to reduce delays in HARQ-ACK transmission.

[0130] <Modifications of the second and third embodiments> When the above second and third embodiments are applied, the DL non-reception period may not overlap in time with symbols to which DMRS for DL ​​signals / channels (e.g., PDSCH) are mapped. For example, the DMRS symbols for PDSCH may not overlap with symbols to which PUCCH resources are configured / instructed for a UE. That is, the symbols to which PUCCH resources are configured / instructed may be mapped to the same time resources as the data symbols for the PDSCH.

[0131] In the modifications of the second and third embodiments, the UE does not need to assume that a PUCCH resource is configured / indicated at least in a symbol to which a DMRS for a PDSCH is mapped (Modification 1). According to Modification 1, it is possible to simplify the implementation of the UE.

[0132] Furthermore, in the modifications of the second and third embodiments, when a PUCCH resource is configured / instructed at least in a symbol to which a DMRS for a PDSCH is mapped, the UE may transmit a PUCCH excluding the symbol to which a DMRS for a PDSCH is mapped (Modification 2). According to Modification 2, it is possible to suppress a decrease in the accuracy of channel estimation of the UE.

[0133] Furthermore, in the modifications of the second and third embodiments, when PUCCH resources are configured / instructed at least in symbols to which DMRS for PDSCH are mapped, the UE may transmit PUCCH without excluding symbols to which DMRS for PDSCH are mapped (Modification 3). According to Modification 3, in cases where high DMRS density is not required, such as when the UE's movement speed is relatively low, opportunities for PUCCH transmission can be efficiently secured.

[0134] 8A and 8B are diagrams showing an example of PDSCH reception and PUCCH transmission according to the second embodiment and the modified example of the third embodiment. FIGS. 8A and 8B show PDSCH reception and PUCCH transmission by UE#1 and UE#2, respectively. The PDSCH in the example shown in FIGS. 8A and 8B may be a PDSCH common to multiple UEs, or may be a PDSCH that uses multicast. Furthermore, the DL reception period shown in FIGS. 8A and 8B is common to UE#1 and UE#2.

[0135] 8A and 8B, UE#1 transmits PUCCH#1 in time resources excluding symbols to which DMRS for PDSCH are mapped within an UL transmission period set to the same time resource as at least a portion of a DL reception period used for receiving PDSCH. UE#2 transmits PUCCH#2 in time resources excluding symbols to which DMRS for PDSCH are mapped within an UL transmission period set to the same time resource as at least a portion of a DL reception period used for receiving PDSCH. At this time, each UE does not receive DCI / PDSCH in time resources (DL non-reception periods) that overlap with the PUCCH transmission resources and in gap periods set before the time resources.

[0136] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0137] 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0138] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0139] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0140] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0141] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0142] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0143] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

[0144] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

[0145] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0146] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0147] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0148] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0149] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0150] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0151] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0152] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

[0153] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0154] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0155] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0156] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0157] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0158] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0159] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0160] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[0161] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0162] (base station) 10 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0163] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0164] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0165] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0166] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0167] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0168] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0169] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0170] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0171] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0172] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0173] The transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .

[0174] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna .

[0175] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0176] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0177] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0178] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0179] The transceiver 120 may transmit information indicating a first time period used to receive at least one of downlink control information (DCI) and a downlink shared channel (PDSCH) and information indicating a second time period used to transmit a physical uplink control channel (PUCCH). When at least a portion of the first time period and the second time period overlap, the controller 110 may control the transmission of at least one of the DCI and the PDSCH and the reception of the PUCCH in the overlapping time resource. The DCI, the PDSCH, and the PUCCH may be mapped within a single operating band defined as a combination of an uplink operating band and a downlink operating band, and the uplink operating band may be equal to the downlink operating band (first to third embodiments).

[0180] (user terminal) 11 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0181] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0182] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0183] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.

[0184] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0185] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0186] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0187] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0188] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0189] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0190] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0191] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

[0192] The transmitting / receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna 230.

[0193] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0194] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0195] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0196] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0197] The transceiver 220 may receive information indicating a first time period used to receive at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH), and information indicating a second time period used to transmit a physical uplink control channel (PUCCH). When at least a portion of the first time period and the second time period overlap, the controller 210 may control the reception of at least one of the DCI and the PDSCH and the transmission of the PUCCH in the overlapping time resource. The DCI, the PDSCH, and the PUCCH may be mapped within a single operating band defined as a combination of an uplink operating band and a downlink operating band, and the uplink operating band may be equal to the downlink operating band (first to third embodiments).

[0198] The control unit 210 may perform control so that, in the overlapping time resource, both reception of at least one of the DCI and the PDSCH and transmission of the PUCCH are performed (first embodiment).

[0199] The control unit 210 may control the reception of at least one of the DCI and the PUSCH and the transmission of the PUCCH in the overlapping time resources based on the coding rate of the PDSCH (second and third embodiments).

[0200] If the decoding of the PDSCH fails, the control unit 210 may perform control so as not to receive the PDSCH in the overlapping time resource and to transmit a negative acknowledgement in the PUCCH resource (second embodiment).

[0201] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0202] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0203] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 12 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0204] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0205] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0206] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0207] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0208] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0209] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0210] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

[0211] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0212] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0213] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0214] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0215] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0216] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0217] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0218] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.

[0219] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0220] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0221] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0222] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0223] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0224] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0225] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0226] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0227] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0228] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0229] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0230] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0231] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0232] The BWP may include an UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0233] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0234] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0235] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0236] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0237] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0238] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0239] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0240] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0241] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0242] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0243] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0244] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0245] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0246] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0247] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0248] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0249] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0250] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0251] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0252] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0253] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0254] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0255] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0256] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0257] Each aspect / embodiment described in the present disclosure may be related to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0258] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0259] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0260] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0261] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0262] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0263] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[0264] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0265] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0266] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0267] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0268] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0269] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiving unit that receives information indicating a first time period used to receive at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH) and information indicating a second time period used to transmit a physical uplink control channel (PUCCH), and receives at least one of the DCI and the PDSCH in a time resource in which at least a portion of the first time period and the second time period overlap; a transmitter for transmitting the PUCCH in the time resource, A terminal, wherein at least one of the DCI and the PDSCH, and the PUCCH are mapped to different frequency resources within one operating band.

2. The terminal according to claim 1 , further comprising: a control unit configured to perform control so that, in the time resource, both reception of at least one of the DCI and the PDSCH and transmission of the PUCCH are performed.

3. The terminal according to claim 1 , further comprising: a control unit configured to control reception of at least one of the DCI and the PUSCH and transmission of the PUCCH in the time resource based on a coding rate of the PDSCH.

4. The terminal according to claim 1 , further comprising: a control unit configured to perform control such that, when decoding of the PDSCH fails, reception of the PDSCH is not performed in the time resource and a negative acknowledgement is transmitted in the PUCCH resource.

5. receiving information indicating a first time period used to receive at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH) and information indicating a second time period used to transmit a physical uplink control channel (PUCCH), and receiving at least one of the DCI and the PDSCH in a time resource in which the first time period and the second time period at least partially overlap; transmitting the PUCCH in the time resource; The wireless communication method for a terminal, wherein at least one of the DCI and the PDSCH, and the PUCCH are mapped to different frequency resources within one operating band.

6. a transmitter that transmits information indicating a first time period used to receive at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH) and information indicating a second time period used to transmit a physical uplink control channel (PUCCH), and that transmits at least one of the DCI and the PDSCH in a time resource in which at least a portion of the first time period and the second time period overlap; a receiving unit for receiving the PUCCH in the time resource, The base station, wherein at least one of the DCI and the PDSCH, and the PUCCH are mapped to different frequency resources within one operating band.

7. A system including a terminal and a base station, The terminal a receiving unit that receives information indicating a first time period used to receive at least one of downlink control information (DCI) and a physical downlink shared channel (PDSCH) and information indicating a second time period used to transmit a physical uplink control channel (PUCCH), and receives at least one of the DCI and the PDSCH in a time resource in which at least a portion of the first time period and the second time period overlap; a transmitter for transmitting the PUCCH in the time resource, At least one of the DCI and the PDSCH, and the PUCCH are mapped to different frequency resources within one operating band, The base station A system comprising a receiver for receiving the PUCCH in the time resource.

Images