Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit for receiving information relating to one or more patterns indicating link directions of one or more frequency units in one or more time units in which a downlink resource and an uplink resource are subjected to frequency-division multiplexing in specific bandwidths; and a control unit for controlling transmission or reception in the one or more time units, on the basis of the information. The information conforms to the restriction of a usable pattern and / or the number of the one or more patterns. According to the one aspect of the present disclosure, it is possible to improve the efficiency of resource utilization.

Description

[[Technical Field]]

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized for the purposes of achieving higher data rates, lower latency, and the like (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized for the purposes of achieving further increased capacity and sophistication beyond LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Post-LTE systems (also referred to as, for example, 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later releases, etc.) are also under study. [[Prior Art Documents]] [[Non-Patent Documents]]

[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]] [Problems that the invention aims to solve]

[0005] In future wireless communication systems (e.g., NR), it is anticipated that multiple terminals (user terminals, User Equipment (UEs)) will communicate in extremely high-density and high-traffic environments.

[0006] In this environment, it is anticipated that uplink (UL) resources will be insufficient compared to downlink (DL) resources.

[0007] However, previous NR specifications have not adequately considered methods for increasing uplink resources. If these methods cannot be properly controlled, system performance may deteriorate, such as increased latency and reduced coverage performance.

[0008] Therefore, this disclosure relates to a terminal and wireless communication method that improve the efficiency of resource utilization. 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0009] A terminal according to one aspect of this disclosure is configured such that downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth. 1 Time unit The system receives first information relating to the first time unit and first setting of the physical uplink control channel (PUCCH) within the first time unit, second information relating to the second time unit in which downlink resources and uplink resources are not frequency-division multiplexed within the specific bandwidth and second setting of the PUCCH within the second time unit, and Downlink Control Information (DCI) The receiving unit, PUCCH transmission according to either the first setting or the second setting corresponding to the PUCCH resource instruction included in the DCI. It has a control unit that controls, The control unit transmits capability information indicating support for the ability to control the transmission of PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction, prior to receiving the first information, the first setting, the second information, and the second setting. . [Effects of the Invention]

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

[0011] [Figure 1]1A and 1B are diagrams illustrating an example of a slot configuration setting. [Figure 2] Figure 2 is a diagram illustrating an example of an XDD configuration. [Figure 3] 3A and 3B are diagrams illustrating an example of a slot format. [Figure 4] 4A to 4D are diagrams illustrating an example of partial availability according to the third embodiment. [Figure 5] Figure 5 illustrates an example of PUCCH resource configuration. [Figure 6] 6A to 6E illustrate an example of link directions for a plurality of frequency resources within a time unit. [Figure 7] Figure 7 illustrates an example of a time unit for PUCCH transmission in Case A-1. [Figure 8] Figure 8 illustrates another example of a time unit for PUCCH transmission in Case A-1. [Figure 9] Figure 9 illustrates an example of a time unit for PUCCH transmission in Case A-2. [Figure 10] Figure 10 illustrates an example of a time unit for PUCCH transmission in Case B-3. [Figure 11] Figure 11 illustrates an example of a time unit for PUCCH transmission in Case B-4. [Figure 12] Figure 12 illustrates an example of a time unit for PUCCH transmission in Case B-5. [Figure 13] Figure 13 is a diagram illustrating an example of a schematic configuration of a radio communication system according to an embodiment. [Figure 14] Figure 14 is a diagram illustrating an example of a configuration of a base station according to an embodiment. [Figure 15] Figure 15 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. [Figure 16] Figure 16 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment. [Figure 17] Figure 17 is a diagram illustrating an example of a vehicle according to an embodiment. Mode for Carrying Out the Invention

[0012] (PUCCH format) In future wireless communication systems (e.g., Rel.15 and later, 5G, NR, etc.), configurations (formats, also called PUCCH formats (PF), etc.) for the uplink control channel (e.g., PUCCH) used to transmit uplink control information (UCI) are being considered. For example, Rel.15 NR is considering supporting five types of PF0-4. Note that the PF names shown below are merely examples, and different names may be used.

[0013] For example, PF0 and PF1 are PFs used to transmit UCIs of up to 2 bits. For example, the UCI may be at least one of a delivery acknowledgment (HARQ-ACK, also known as an acknowledgment (ACK), or negative-acknowledgment (NACK)) and a scheduling request (SR). PF0 can be assigned to 1 or 2 symbols and is therefore also called a short PUCCH or a sequence-based short PUCCH. On the other hand, PF1 can be assigned to 4-14 symbols and is therefore also called a long PUCCH. PF0 may transmit a sequence obtained by a cyclic shift of a base sequence using a cyclic shift based on at least one of an initial cyclic shift (CS) index, the UCI value, a slot number, and a symbol number. In PF1, multiple user terminals may be code-division multiplexed (CDM) within the same physical resource block (PRB) by time-domain block diffusion using at least one of CS and time-domain (TD)-orthogonal cover code (OCC).

[0014] PF2-4 are PFs used for transmitting UCI (e.g., Channel State Information (CSI), or at least one of CSI, HARQ-ACK, and SR) exceeding 2 bits. PF2 can be assigned to 1 or 2 symbols and is therefore also called a short PUCCH, etc. PF3 and PF4, on the other hand, can be assigned to 4-14 symbols and are therefore also called long PUCCH, etc. PF4 may allow multiple user terminals to perform CDM using pre-DFT (Frequency Domain (FD)-OCC) block spread.

[0015] Intra-slot frequency hopping may be applied to PF1, PF3, and PF4. The length of PUCCH is N. symb Therefore, the length before frequency hopping (first hop) is floor(N symb It may also be / 2), and the length after frequency hopping (second hop) is ceil(N symb (2) is also acceptable.

[0016] The waveforms of PF0, PF1, and PF2 may be Cyclic Prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM). The waveforms of PF3 and PF4 may be Discrete Fourier Transform (DFT)-spread(s)-OFDM.

[0017] The allocation of resources (e.g., PUCCH resources) used for transmission on the uplink control channel is performed using upper-layer signaling and / or downlink control information (DCI). Here, the upper-layer signaling can be at least one of the following: RRC (Radio Resource Control) signaling, system information (e.g., at least one of RMSI: Remaining Minimum System Information, OSI: Other System Information, MIB: Master Information Block, SIB: System Information Block), or broadcast information (PBCH: Physical Broadcast Channel).

[0018] Furthermore, in NR, the number of symbols assigned to PUCCH (which may also be called PUCCH-assigned symbols, PUCCH symbols, etc.) can be determined by slot-specific, cell-specific, user terminal-specific, or a combination thereof. Since increasing the number of PUCCH symbols is expected to increase the communication distance (coverage), it is conceivable that the number of symbols will be increased for user terminals that are farther from the base station (e.g., eNB, gNB).

[0019] (HARQ-ACK feedback) In NR, a mechanism is being considered for user equipment (UE) to provide feedback (report or transmit) delivery confirmation information (Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK), ACKnowledge / Non-ACK (ACK / NACK), HARQ-ACK information, or A / N, etc.) for downlink shared channels (also known as Physical Downlink Shared Channel (PDSCH), etc.).

[0020] For example, in NR Rel.15, the value of a predetermined field in the DCI (e.g., DCI format 1_0 or 1_1) used for scheduling the PDSCH indicates the HARQ-ACK feedback timing for that PDSCH. When a UE transmits a HARQ-ACK for a PDSCH received in slot #n in slot #n+k, the value of the predetermined field may be mapped to the value of k. This predetermined field is, for example, called the PDSCH-to-HARQ feedback timing indicator field.

[0021] Furthermore, NR Rel.15 determines the PUCCH resource used for HARQ-ACK feedback to a PDSCH based on the value of a predetermined field in the DCI (e.g., DCI format 1_0 or 1_1) used for scheduling the PDSCH. This predetermined field may be called, for example, the PUCCH resource indicator (PRI) field, the ACK / NACK resource indicator (ARI) field, etc. The value of this predetermined field may be called PRI, ARI, etc.

[0022] The PUCCH resources mapped to each value of the predetermined field may be pre-configured in the UE by higher-layer parameters (for example, ResourceList in PUCCH-ResourceSet). Alternatively, the PUCCH resources may be configured in the UE for each set containing one or more PUCCH resources (PUCCH resource set).

[0023] Furthermore, NR Rel.15 considers that the UE should not expect to transmit more than one Physical Uplink Control Channel (PUCCH) containing HARQ-ACKs within a single slot.

[0024] Specifically, NR Rel.15 states that one or more HARQ-ACKs in a single slot may be mapped to a single HARQ-ACK codebook, which may be transmitted in a PUCCH resource indicated by the last DCI.

[0025] Here, the HARQ-ACK codebook may consist of bits for HARQ-ACK in at least one unit of the time domain (e.g., slot), frequency domain (e.g., component carrier (CC)), spatial domain (e.g., layer), transport block (TB), and group of code blocks constituting the TB (code block group (CBG)). CC is also called a cell, serving cell, carrier, etc. The bits are also called HARQ-ACK bits, HARQ-ACK information, or HARQ-ACK information bits, etc.

[0026] HARQ-ACK codebooks are also known as PDSCH-HARQ-ACK codebooks, codebooks, HARQ codebooks, HARQ-ACK size, etc.

[0027] The number of bits (size), etc., included in a HARQ-ACK codebook may be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also called a Type-1 HARQ-ACK codebook or a dynamic codebook. A dynamic HARQ-ACK codebook is also called a Type-2 HARQ-ACK codebook or a dynamic codebook.

[0028] Whether to use a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook may be set in the UE by a higher-level parameter (e.g., pdsch-HARQ-ACK-Codebook).

[0029] In the case of a Type 1 HARQ-ACK codebook, the UE may feed back HARQ-ACK bits corresponding to a predetermined range (for example, a range set based on higher layer parameters), regardless of whether or not the PDSCH is scheduled.

[0030] The specified range may be determined based on at least one of the following: a specified period (for example, a set of a specified number of occasions for receiving candidate PDSCHs, or a specified number of monitoring occasions for PDCCHs), the number of CCs set or activated in the UE, the number of TBs (number of layers or ranks), the number of CBGs per TB, and whether or not spatial bundling is applied. The specified range is also called the HARQ-ACK bundling window, HARQ-ACK feedback window, bundling window, feedback window, etc.

[0031] In a Type 1 HARQ-ACK codebook, the UE will feed back the NACK bit even if there is no PDSCH scheduling for the UE, as long as it is within a specified range. Therefore, when using a Type 1 HARQ-ACK codebook, it is expected that the number of HARQ-ACK bits to be fed back may increase.

[0032] On the other hand, in the case of a Type 2 HARQ-ACK codebook, the UE may feed back the HARQ-ACK bits to the scheduled PDSCH within the predetermined range described above.

[0033] Furthermore, if the UE is not configured for code block group (CBG)-based transmission (CBG-based HARQ-ACK codebook determination) by the higher-layer parameter (PDSCH code block group transmission information element, PDSCH-CodeBlockGroupTransmission), the UE assumes transport block (TB)-based transmission (TB-based HARQ-ACK codebook determination). That is, the UE generates HARQ-ACK information bits for each TB.

[0034] If the UE is provided with a higher-layer parameter for the PDSCH code block group transmission information element for a serving cell (Component Carrier: CC), it receives a PDSCH containing multiple CBGs in a single TB. The PDSCH code block group transmission information element includes the maximum number of CBGs in a single TB (maxCodeBlockGroupsPerTransportBlock). Upon receiving the TB for the serving cell, the UE generates HARQ-ACK information bits for each of the multiple CBGs and generates a HARQ-ACK codebook containing the maximum number of HARQ-ACK information bits for the CBGs.

[0035] The UE may transmit one or more HARQ-ACK bits, determined (generated) based on the above Type 1 or Type 2 HARQ-ACK codebooks, using at least one of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH).

[0036] (XDD) Up to Rel.14, LTE primarily used Frequency Division Duplex (FDD), but also supported Time Division Duplex (TDD).

[0037] On the other hand, for NR from Rel.15 onwards, TDD was the main focus of consideration, while FDD was also supported at the same time (for example, migration of LTE bands).

[0038] In FDDs, DL reception and UL transmission can be performed simultaneously, which is preferable from the standpoint of reducing latency. On the other hand, in FDDs, the resource ratio of DL to UL is fixed (e.g., 1:1).

[0039] In TDD, it is possible to change the ratio of DL and UL resources. For example, in a typical environment where DL traffic is relatively high, it is possible to increase the amount of DL resources to improve DL throughput.

[0040] On the other hand, considering the transmission-to-reception time ratio using TDD up to Rel.16, there are cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE may not be able to transmit UL signals / channels frequently, raising concerns about delays in the transmission of important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, since the time resources available for transmitting UL signals / channels are limited in TDD, the application of UL coverage extension techniques such as repetition transmission is also limited.

[0041] In future wireless communication systems (e.g., Rel.17 / 18 and beyond), the introduction of a division duplex method combining TDD and Frequency Division Duplex (FDD) for UL and DL is being considered.

[0042] The division-duplex method may also be called XDD (Cross Division Duplex). XDD may mean a duplex method that frequency-division multiplexes DL and UL (allowing simultaneous use of DL and UL) within one component carrier (CC) of the TDD band, or across multiple CCs. When the duplex method is applied to multiple CCs, it may mean that in the time resources where DL is available in one CC, UL is available in another CC. The multiple CCs may be CCs in the same band.

[0043] Figure 1A shows an example of a TDD configuration as defined up to Rel. 16. In the example shown in Figure 1A, the UE is configured with TDD slots / symbols using the bandwidth of one component carrier (CC) (which may also be called a cell or serving cell).

[0044] In the example shown in Figure 1A, the time ratio of DL slots to UL slots is 4:1. With this conventional TDD slot / symbol setting, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and a decrease in coverage performance.

[0045] Figure 1B shows an example of an XDD configuration. In the example in Figure 1B, the resources used for receiving DL and the resources used for transmitting UL overlap in time within a single component carrier (CC). With such a resource configuration, UL resources can be secured, and the efficiency of resource utilization can be improved.

[0046] For example, as shown in the example in Figure 1B, by configuring DLs at both ends of the frequency domain in a 1CC and sandwiching UL resources between the DLs, it is possible to avoid and mitigate cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources.

[0047] Considering the complexity of handling self-interference, it is conceivable that only base stations use DL and UL resources simultaneously. In other words, for resources where DL and UL overlap in time, one UE may use the DL resource while another UE uses the UL resource.

[0048] Figure 2 shows an example of an XDD configuration. In the example shown in Figure 2, a portion of the DL resources in the TDD band are used as UL resources, resulting in a configuration where DL and UL partially overlap in time.

[0049] In the example shown in Figure 2, during the DL-only period, each of the multiple UEs (UE#1 and UE#2 in Figure 2) receives the DL channel / signal.

[0050] Furthermore, during periods when DL and UL overlap in time, one UE (UE#1 in the example in Figure 2) receives the DL channel / signal, while another UE (UE#2 in the example in Figure 2) transmits the UL channel / signal. During this period, the base station performs simultaneous transmission and reception of DL and UL.

[0051] Furthermore, during UL-only periods, each of the multiple UEs transmits a UL channel / signal.

[0052] In existing NRs (e.g., those defined up to Rel. 15 / 16), DL frequency resources and UL frequency resources in a UE carrier are configured as DL Bandwidth Parts (BWPs) and UL BWPs, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism.

[0053] Furthermore, in existing NRs, the time resources in the TDD carrier for UE are configured in the TDD settings as at least one of DL, UL, and Flexible (FL).

[0054] Methods for configuring time-domain and frequency-domain resources for XDD operation are being considered. For example, for UE#1 in Figure 2, the impact on the specification / UE can be minimized by configuring the XDD resources (the period during which DL and UL overlap) in the same way as existing DL resources (for example, by avoiding the use of the UL resource portion using frequency-domain resource allocation (FDRA)).

[0055] Furthermore, for example, with respect to UE#2 in Figure 2, the impact on the specification / UE can be minimized by configuring the XDD resources in the same way as existing UL resources (for example, by avoiding the use of the DL resource portion using Frequency Domain Resource Allocation (FDRA)).

[0056] Separate or common PUCCH settings are being considered for pure DL / UL time units (pure time units) and XDD time units.

[0057] When a common PUCCH setting is used for XDD time units or pure time units, the following problems occur: UE behavior when a decided / selected PUCCH resource overlaps with an invalid resource element (RE) within an XDD time unit. For example, UE behavior for PUCCH with DCI or PUCCH without DCI. How to avoid overlapping with invalid REs within an XDD time unit for decided / selected PUCCH resources.

[0058] When a PUCCH setting (different from the one for pure time units) is used for XDD time units, the following problems occur: • The number of PUCCH settings for the XDD time unit. The relationship between the number of PUCCH settings for the XDD time unit and the number of XDD frequency domain patterns. • PUCCH resource determination. How to determine / select PUCCH resources. Are slots / subslots possible consisting of different time units (e.g., pure UL time units, XDD time unit pattern 1, XDD time unit pattern 2)? UE behavior when PUCCH iteration is applied. • Is it possible for the decided / selected PUCCH resource to overlap with an invalid RE within the XDD time unit?

[0059] If these considerations are insufficient, it may not be possible to adequately improve resource utilization efficiency, potentially leading to a decrease in system performance.

[0060] Therefore, the inventors conceived of an operation relating to PUCCH within a pure time unit or an XDD time unit.

[0061] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0062] In the following disclosure, “specific types” are described with the understanding that… are…, but are not limited to…. In this disclosure, … may mean any of … or any combination thereof (i.e., … may be interpreted as any of … or any combination thereof).

[0063] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0064] In this disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0065] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, information elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0066] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0067] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0068] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0069] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0070] In this disclosure, channel, signal, reference signal, and channel / signal may be interpreted interchangeably. Also, in this disclosure, DL channel / signal reception, DL reception, and DL transmission may be interpreted interchangeably. Also, in this disclosure, UL channel / signal transmission, UL transmission, and UL reception may be interpreted interchangeably.

[0071] In this disclosure, the terms "support," "supported," "control," "controllable," "operate," and "operable" may be interpreted as interchangeable.

[0072] In this disclosure, "assume / expect that it is not A" may be interpreted as "do not assume / expect that it is A".

[0073] In this disclosure, the phrases "A overlaps with B," "A is redundant with B," and "At least a part of A is redundant with at least a part of B" may be interpreted interchangeably.

[0074] In this disclosure, the terms drop, suspend, cancel, puncture, and rate match may be interpreted interchangeably.

[0075] In this disclosure, time units, one or more symbols, one or more subslots, one or more slots, and one or more subframes may be interpreted as one another.

[0076] In this disclosure, frequency units, one or more RE symbols, one or more RB / PRBs, and one or more RB groups may be interpreted as interchangeable.

[0077] (Wireless communication method) In each embodiment, DL signals / channels may be received and transmitted using the same BWP / CC / bandwidth / operating band, or they may be transmitted and transmitted using different BWP / CC / bandwidth / operating bands. The drawings of this disclosure illustrate a configuration in 1CC, but the number of resources in the frequency direction is not limited thereto. In this disclosure, BWP, CC, cell, serving cell, band, carrier, operating band, PRG, PRB, RB, RE, and resource may be interpreted as mutually exclusive.

[0078] In each embodiment, the time domain (period) in which DL resources and UL resources within one CC of the TDD band can be used simultaneously, the XDD portion, and the XDD period may be interpreted interchangeably. DL / UL resources in the XDD portion may be called XDD DL / UL resources or XDD DL / UL. DL / UL resources in the TDD band where DL and UL do not overlap in time may be interpreted as non-XDD DL / UL resources, pure DL / UL resources, non-XDD DL / UL resources, new DL / UL resources, etc. XDD operation may refer to the operation during the period in which XDD DL / UL resources are set, or it may refer to the operation of the entire TDD in which XDD can be used.

[0079] In each embodiment, DL / UL BWP in the TDD band, DL / UL BWP as defined up to Rel. 15 / 16, and ordinary DL / UL BWP may be interpreted as mutually exclusive.

[0080] In each embodiment, the PRB for UL and the PRB instructed to use UL('U') may be interchangeable.

[0081] In each embodiment, the time units set / instructed by the TDD UL / DL pattern and the pure time units may be interchangeable. In each embodiment, the time units set / instructed by the TDD UL / DL pattern and the pure UL time units may be interchangeable. In each embodiment, the time units set / instructed by the TDD UL / DL pattern and the pure DL time units may be interchangeable.

[0082] In each embodiment, the XDD UL / DL pattern, the setting / instruction of the XDD time unit / frequency domain pattern, and the setting / instruction of time / frequency resources for XDD may be interchangeable. In each embodiment, the time unit in which the XDD UL / DL pattern is set / instructed, the XDD time unit, and the time resources for XDD may be interchangeable. In each embodiment, the frequency domain pattern, the frequency pattern, the setting / instruction of frequency resources for XDD, the combination of link directions in the frequency domain, and the combination of link directions of multiple frequency units FDM-treated within a specific band may be interchangeable.

[0083] In each embodiment, invalid RE for UL / PUCCH, RE unavailable for UL, RE with DL set / instructed, and PRB for DL ​​may be interchangeable. In each embodiment, invalid symbols for UL / PUCCH, symbols unavailable for UL, symbols with DL set / instructed, and DL symbols may be interchangeable.

[0084] In each embodiment, the UL resource, UL frequency unit, and UL PRB may be interchangeable. In each embodiment, the DL resource, DL frequency unit, and DL PRB may be interchangeable.

[0085] <Embodiment #A> "analysis" To enable XDD operation, existing settings / instructions regarding slot format may be used to instruct different slots with different link directions (DL('D') / UL('U') / Flexible('F')) for different UEs.

[0086] In the examples shown in Figures 3A and 3B, first, the link direction 'DDFFU' is set for slots #0 through #4 of UE#1 and #2, respectively, by RRC.

[0087] Subsequently, in the example in Figure 3A, the DCI for UE#1 instructs the two 'F's in slots #2 and #3 to be two 'D's. This allows UE#1 to receive DLs in slots #2 and #3.

[0088] To enable XDD operation in slots #2 and #3, the base station may schedule UE#1 without PDSCH reception on some of resource #1 within slots #2 and #3. If there is no explicit indication that resource #1 is unavailable and periodic / semi-persistent SSB / CSI-RS may be present on resource #1, problems may occur in measuring SSB / CSI-RS.

[0089] In the example in Figure 3B, the DCI for UE#2 instructs the two 'F's in slots #2 and #3 to be two 'U's. This allows UE#2 to send ULs in slots #2 and #3.

[0090] To enable XDD operation in slots #2 and #3, the base station may schedule UE#2 on some of resource #2 within slots #2 and #3 without performing a PUSCH transmission. If there is no explicit indication that resource #2 is unavailable, and the normal PUCCH / SRS resource setting on resource #2 is not limited to resource #1, problems may occur with PUSCH / SRS / PRACH transmission.

[0091] Different UEs may be instructed to have different link directions for time resources (subframes / slots / minislots / symbols).

[0092] Several periodic / semi-persistent RSs may be considered to enable XDD operations on time resources designated as 'D' for some UEs.

[0093] To enable XDD operations on time resources designated as 'U' for some UEs, the channel / RS configuration of some ULs may be considered.

[0094] In this disclosure, partial availability, partial available indication, partial non-available indication, partially available DL frequency resources, partially available UL frequency resources, partially unavailable DL frequency resources, partially unavailable UL frequency resources, link direction (D / F / U), and combinations of partial availability may be interpreted interchangeably.

[0095] 《Embodiment #A-1》 Based on existing link direction (D / F / U) instructions, a new type of instruction (new instruction) may be provided for indicating "partial availability" for a time unit. In this disclosure, a time unit may be a time resource having a certain length, such as a subframe / slot / minislot / symbol. In this disclosure, a partial availability instruction may indicate whether some frequency resources (resource blocks / resource elements) within a component carrier / BWP are available in a particular link direction, or may indicate such frequency resources.

[0096] New instructions may also be RRC IE / MAC CE / DCI.

[0097] The new indication may be a separate signaling from the existing link direction indication signaling. In other words, the elements of the RRC IE / MAC CE / DCI for a new indication (e.g., a partial availability indication, a partial frequency resource indication, etc.) may be separated from the elements of the RRC IE / MAC CE / DCI for an existing link direction indication (e.g., a D / F / U indication).

[0098] The new instruction may be a signaling that is combined with an existing link direction instruction signaling. In other words, an RRC IE / MAC CE / DCI indicating a combination of an existing link direction instruction and a new instruction (for example, an instruction for partial availability and D / F / U, or an instruction for D / F / U / partially available D / partially available U) may be notified.

[0099] The UE may indicate either a "partial available indication" (a partially available frequency resource) and a 'D' (time unit for DL) (an indication of a partially available frequency resource for DL, an indication of a partially available DL frequency resource), or a "partial non-available indication" (a partially unavailable frequency resource) and a 'D' (time unit for DL) (an indication of a partially unavailable frequency resource for DL, an indication of a partially unavailable DL frequency resource).

[0100] A UE may be indicated by either a “partially available indicator” (an available partial frequency resource) and a ‘U’ (a time unit for UL) (an indicator of a partial frequency resource available to UL, an indicator of a partially available UL frequency resource), or a “partially unavailable indicator” (an unavailable partial frequency resource) and a ‘U’ (a time unit for UL) (an indicator of a partial frequency resource unavailable to UL, an indicator of a partially unavailable UL frequency resource).

[0101] The UE may be instructed to provide at least one of the following: “Partially Available Indicator” (available partial frequency resources) and “D” (time unit for DL) (indicator of partially available DL frequency resources); and “Partially Available Indicator” (available partial frequency resources) and “U” (time unit for UL) (indicator of partially available UL frequency resources). Based on the indication of partially available DL frequency resources within a time unit, the UE may identify partially unavailable DL frequency resources within that time unit (partial frequency resources other than partially available DL frequency resources within that time unit). Based on the indication of partially available UL frequency resources within a time unit, the UE may identify partially unavailable DL frequency resources within that time unit (partial frequency resources other than partially available UL frequency resources within that time unit).

[0102] The UE may be instructed to provide at least one of the following: “Partially Unavailable Indication” (an unavailable partial frequency resource) and “D” (a time unit for DL) (an indication of a partially unavailable DL frequency resource); and “Partially Unavailable Indication” (an unavailable partial frequency resource) and “U” (a time unit for UL) (an indication of a partially unavailable DL frequency resource). Based on the indication of a partially unavailable DL frequency resource within a time unit, the UE may identify the partially available DL frequency resources within that time unit (partial frequency resources other than the partially unavailable DL frequency resources within that time unit). Based on the indication of a partially unavailable UL frequency resource within a time unit, the UE may identify the partially available UL frequency resources within that time unit (partial frequency resources other than the partially unavailable UL frequency resources within that time unit).

[0103] If a time unit is indicated as “Partially Available” and 'D' (indicating a partially available DL frequency resource), the UE may assume that it will receive DL channels / RS on the partially available DL frequency resources within that time unit, or it may not assume that it will receive DL channels / RS on the partially unavailable DL frequency resources within that time unit. If a time unit is indicated as “Partially Unavailable” and 'D' (indicating a partially unavailable DL frequency resource), the UE may assume that it will receive DL channels / RS on the partially available DL frequency resources within that time unit, or it may not assume that it will receive DL channels / RS on the partially unavailable DL frequency resources within that time unit.

[0104] If a time unit is indicated as “partially unavailable” and 'U' (indicating a partially unavailable UL frequency resource), the UE may assume that it will receive the DL's channel / RS on the partially unavailable UL frequency resource within that time unit, or it may not assume that it will receive the DL's channel / RS on the partially available UL frequency resource within that time unit.

[0105] Partially available DL frequency resources (P_AD) can be set / instructed by the RRC IE / MAC CE. For example, setting / instructing these partially available DL frequency resources may disable several frequency resources (partially unavailable DL frequency resources (P_ND)) (Figure 4A), or it may combine two sets of frequency resources (Figure 4B).

[0106] A common partially available DL frequency resource may be set / instructed for multiple time units (e.g., time units #0 and #1) (Figure 4A). Different partially available DL frequency resources may be set / instructed for multiple time units (e.g., time units #0 and #1) (Figure 4B).

[0107] If a time unit is indicated as “Partially Available” and 'U” (indicating a partially available UL frequency resource), the UE may assume that it will transmit the UL channel / RS over the partially available UL frequency resources within that time unit, or it may not assume that it will transmit the UL channel / RS over the partially unavailable UL frequency resources within that time unit. If a time unit is indicated as “Partially Unavailable” and 'U” (indicating a partially unavailable UL frequency resource), the UE may assume that it will transmit the UL channel / RS over the partially available UL frequency resources within that time unit, or it may not assume that it will transmit the UL channel / RS over the partially unavailable UL frequency resources within that time unit.

[0108] If a time unit is indicated as “partially unavailable” and 'D' (indicating a partially unavailable DL frequency resource), the UE may assume that it will transmit the UL channel / RS over the partially unavailable DL frequency resource within that time unit, or it may not assume that it will transmit the UL channel / RS over the partially available DL frequency resource within that time unit.

[0109] Partially available UL frequency resources (P_AU) can be set / instructed by the RRC IE / MAC CE. For example, setting / instructing a partially available UL frequency resource may disable several frequency resources (partially unavailable UL frequency resources (P_NU)) (Figure 4C), or it may combine two sets of frequency resources (Figure 4D).

[0110] A common partially available UL frequency resource may be set / instructed for multiple time units (e.g., time units #0 and #1) (Figure 4C). Alternatively, different partially available UL frequency resources may be set / instructed for multiple time units (e.g., time units #0 and #1) (Figure 4D).

[0111] According to this embodiment, the link direction can be set / instructed for each time resource, and partially available or unavailable frequency resources can be flexibly set / instructed.

[0112] 《Embodiment #A-2》 This section describes the UE operation in a partially available DL time unit. A partially available DL time unit may be a "partially available indicator" and 'D' (partially available DL frequency resource, P_AD), or a "partially unavailable indicator" and 'U' (partially unavailable UL frequency resource, P_UL).

[0113] -PDSCH reception The UE may assume that PDSCH reception is scheduled only on partially available DL frequency resources (or partially unavailable UL frequency resources) within a partially available DL time unit. The UE may perform rate matching around partially unavailable DL frequency resources (or partially available UL frequency resources) within a partially available DL time unit.

[0114] For PDSCH reception within a partially available DL time unit, the UE may follow at least one of options 1 to 3.

[0115] [Option 1] The frequency resource settings, the mapping to frequency domain resource assignments (FDMA instructions in DCI) for normal DL time units (time units that are not indicated as partially available and are indicated as 'D'), and the partially available DL time units are common (consistent). The UE does not have to assume that the FDRA instruction places a PDSCH resource that overlaps with a partially unavailable DL frequency resource (or partially available UL frequency resource) within a partially available DL time unit. It may be an error case if the FDRA field places a PDSCH resource that overlaps with a partially unavailable DL frequency resource within a partially available DL time unit.

[0116] [Option 2] The frequency resource settings, the mapping to frequency domain resource allocation (FDMA directives in DCI) for normal DL time units (time units that are not indicated as partially available and are indicated as 'D'), and the partially available DL time units are common (aligned). The UE may perform rate matching around partially unavailable DL frequency resources (or partially available UL frequency resources) within a partially available DL time unit. If an FDRA directive includes partially unavailable DL frequency resources within a partially available DL time unit, the UE may perform rate matching around those partially unavailable DL frequency resources.

[0117] [Option 3] The frequency resource settings and the mapping to frequency domain resource allocation (FDMA instructions in DCI) for partially available DL time units are configured separately by the RRC IE. The UE may interpret the FDRA for partially available DL frequency resources within a partially available DL time unit based on the new settings.

[0118] The UE may handle the DMRS and phase tracking reference signal (PTRS) in the same way as the PDSCH.

[0119] -PDCCH reception The UE does not monitor PDCCH(candidate) on partially unavailable DL frequency resources (or partially available UL frequency resources) within a partially available DL time unit. The UE may follow either option 1 or 2 below.

[0120] [Option 1] The CORESET and Search Space (SS) settings are common to all DL time units.

[0121] [Option 2] CORESET and SS settings may be configured separately by RRC IE for partially available DL time units.

[0122] -SSB measurement The UE does not monitor SSB on partially unavailable DL frequency resources (or partially available UL frequency resources) within a partially available DL time unit. The UE may follow either option 1 or 2 below. Alternatively, the UE does not need to assume that SSB monitoring is configured on the time resources where the partially available DL time unit is set up.

[0123] [Option 1] If SSB can be transmitted on a partially unavailable DL frequency resource within a partially available DL time unit according to its SSB period, the UE will ignore (not perform) SSB measurements on that partially unavailable DL frequency resource.

[0124] [Option 2] If SSB can be transmitted in a given time unit according to the SSB period, the UE does not assume that that time unit dictates a partially available DL frequency resource.

[0125] -CSI-RS measurement The UE does not monitor CSI-RS on partially unavailable DL frequency resources (or partially available UL frequency resources) within a partially available DL time unit. The UE may follow either option 1 or 2 below.

[0126] [Option 1] If CSI-RS can be transmitted on a partially unavailable DL frequency resource within a partially available DL time unit according to a periodic / semi-persistent CSI-RS period, the UE will ignore (not perform) CSI-RS measurements on that partially unavailable DL frequency resource.

[0127] [Option 2] The UE does not assume that aperiodic CSI-RS is transmitted in partially unavailable DL frequency resources within a partially available DL time unit (i.e., that aperiodic CSI-RS transmitted in partially unavailable DL frequency resources within a partially available DL time unit is scheduled (triggered) by DCI).

[0128] -DL-PRS measurement The UE does not monitor the DL-positioning reference signal (PRS) on partially unavailable DL frequency resources (or partially available UL frequency resources) within a partially available DL time unit. The UE may follow either of the following options 1 and 2.

[0129] [Option 1] If DL-PRS can be transmitted according to periodicity on a partially unavailable DL frequency resource within a partially available DL time unit, the UE will ignore (not perform) DL-PRS measurements on that partially unavailable DL frequency resource.

[0130] [Option 2] If DL-PRS can be transmitted in a time unit according to a period, the UE does not assume that that time unit indicates a partially available DL frequency resource.

[0131] According to this embodiment, for each time resource, the UE can appropriately control reception in time resources that have been instructed to be DL and partially available.

[0132] 《Embodiment #A-3》 This section describes the UE operation in a partially available UL time unit. A partially available UL time unit may be a "partially available indicator" and 'U' (partially available UL frequency resource, P_AU), or a "partially unavailable indicator" and 'D' (partially unavailable DL frequency resource, P_ND).

[0133] -PUCCH settings With regard to PUCCH settings for partially available UL time units, the UE may follow at least one of the following options 1 and 2:

[0134] [Option 1] A separate PUCCH setting can be configured for partially available UL time units. The PUCCH setting for partially available UL time units may be configured separately from the PUCCH setting for normal UL time units (time units that are not indicated as partially available and are indicated as 'U').

[0135] [Option 2] A single PUCCH configuration is set up, which typically has several PUCCH resources for UL time units and several PUCCH resources for partially available UL time units. The UE may select the PUCCH resources corresponding to the time resources.

[0136] For PUCCH applications, the UE may follow either of the following options 1 or 2.

[0137] [Option 1] There are no restrictions on the use of PUCCH (type of UCI, HARQ-ACK / CSI / SR, etc.) for partially available UL time units.

[0138] [Option 2] For partially available UL time units, the use of PUCCH is limited to HARQ-ACK feedback (HARQ-ACK with SR, or HARQ-ACK without SR).

[0139] The settings for Transmit Power Control (TPC) for partially available UL time units may differ from the settings for TPC for normal UL time units.

[0140] UE may handle DMRS in the same way as PUCCH.

[0141] -PUSCH settings With regard to the PUSCH setting for partially available UL time units, the UE may follow at least one of the following options 1 and 2:

[0142] [Option 1] A separate PUSCH setting (different from the PUSCH setting for a normal UL time unit) is set for a partially available UL time unit. In this case, the scheduled PUSCH may be within (or limited to) a partially available UL frequency resource.

[0143] [Option 2] No separate PUSCH setting is configured for the partially available UL time unit (a separate PUSCH setting from the PUSCH setting for the normal UL time unit). In this case, the UE does not need to assume that a PUSCH transmission is scheduled on the partially unavailable UL frequency resource.

[0144] The TPC settings for partially available UL time units may differ from the TPC settings for regular UL time units. DMRS and PTRS may be handled by the UE in the same way as PUSCH.

[0145] -PRACH setting With regard to PRACH settings for partially available UL time units, the UE may follow at least one of the following options 1 and 2:

[0146] [Option 1] A separate PRACH setting (a different PRACH setting from the one for a normal UL time unit) is set for a partially available UL time unit. In this case, PRACH resource selection and transmission may be within (or limited to) a partially available UL frequency resource.

[0147] [Option 2] No separate PRACH setting is set for the partially available UL time unit (a separate PRACH setting from the PRACH setting for the normal UL time unit). In this case, the UE may follow either of the following options 1 or 2. [[Option 1]] The UE does not have to select a PRACH resource on a partially unavailable UL frequency resource, nor does it have to be ordered by PDCCH to place a PRACH resource on a partially unavailable UL frequency resource. [[Option 2]] The UE may ignore (or not ignore) PRACH transmissions that overlap with partially unavailable UL frequency resources. For example, if a PRACH transmission commanded by PDCCH overlaps with a partially unavailable UL frequency resource, the UE may ignore (or not ignore) that PRACH transmission.

[0148] - SRS settings With regard to SRS settings for partially available UL time units, the UE may follow at least one of the following options 1 and 2:

[0149] [Option 1] A separate SRS setting (different from the SRS setting for a normal UL time unit) is configured for a partially available UL time unit. In this case, SRS resource selection and transmission may be within (or limited to) a partially available UL frequency resource.

[0150] [Option 2] No separate SRS setting is set for the partially available UL time unit (a separate SRS setting from the SRS setting for the normal UL time unit). In this case, the UE may follow either of the following options 1 and 2. [[Option 1]] The UE does not have to select an SRS resource on a partially unavailable UL frequency resource, nor does it have to be triggered by DCI on an SRS resource on a partially unavailable UL frequency resource. [[Option 2]] UE does not assume that partially available UL frequency resources / partially unavailable UL frequency resources are set for time resources with periodic / semi-persistent SRS.

[0151] According to this embodiment, for each time resource, the UE can appropriately control transmission in time resources that are designated as UL and partially available.

[0152] <Embodiment #0> This embodiment relates to a common PUCCH setting for TDD UL / DL patterns (pure time units) and XDD UL / DL patterns (XDD time units / frequency domain patterns).

[0153] 《Embodiment #0-1》 This configuration relates to UE operation considering invalid REs for UL / PUCCH in the XDD UL / DL pattern.

[0154] For a PUCCH associated with a DCI (a PUCCH resource indicated by a DCI that has an associated DCI), the UE may follow either of the following options 0a1 or 0a2. [Option 0a1] The UE does not expect a PRI that indicates an invalid RE for UL / PUCCH and an overlapping PUCCH resource. [Option 0a2] PRI is permitted to indicate a PUCCH resource that overlaps with an invalid RE for UL / PUCCH.

[0155] For a PUCCH without an associated DCI (not associated with a DCI, or not directed to a PUCCH resource by a DCI), or for option 0a2, if the selected / determined PUCCH resource overlaps with an invalid RE for UL / PUCCH, the UE may follow either of the following options 0b1 and 0b2. [Option 0b1] That PUCCH will be dropped. [Option 0b2] The PUCCH is rate-matched only for invalid REs for the UL / PUCCH (and around them). To avoid ambiguity between the base station and the UE, it is preferable that rate matching be based on the instruction for invalid REs for the UL / PUCCH (RRC setting). For acceptable rate-matching cases, additional constraints may be required regarding at least one of the following: PUCCH format, PUCCH PRB location, and PUCCH PRB number. For example, PUCCH rate matching may be allowed for PUCCH format x, where x may be at least one of 0, 1, 2, 3, or 4, or any other.

[0156] If different behaviors are employed for two collision types, pure time unit collisions (collisions between pure DL time units and PUCCH, or PUCCH overlapping with invalid symbols / DL symbols for UL / PUCCH) and XDD time unit collisions (collisions between DL resources and PUCCH within an XDD time unit, or PUCCH overlapping with invalid REs for UL / PUCCH), then handling pure time unit collisions may take precedence over handling XDD time unit collisions. In this case, the UE may follow at least one of the following rules: If a PUCCH overlaps with a DL symbol, that PUCCH is dropped. If a PUCCH overlaps with an invalid RE within an XDD time unit, that PUCCH will be rate-matched against that invalid RE. If a PUCCH overlaps with a DL symbol in a pure time unit and simultaneously overlaps with an invalid RE in an XDD time unit, the UE drops the PUCCH instead of rate matching it.

[0157] Embodiment #0-2 This configuration relates to a method for avoiding invalid REs for UL / PUCCH in the XDD UL / DL pattern.

[0158] In the RRC configuration, one or more starting PRBs may be configured for a single PUCCH resource / format. As shown in the example in Figure 5, the PUCCH resource configuration (PUCCH-Resource) may include a list of starting PRBs (e.g., Multiple-startingPRB-r18).

[0159] The PUCCH resource may be determined based on existing PUCCH resource selection rules. If the determined PUCCH resource overlaps with an XDD time unit, the UE may check one or more start PRBs set for the PUCCH resource, from the first value to the subsequent values, until at least one of the following conditions 1 and 2 is met.

[0160] (Condition 1) A start PRB is selected such that the PUCCH resource does not overlap with an invalid RE for UL / PUCCH. Here, an invalid RE for UL / PUCCH may be notified by the RRC setting. The UE may send a PUCCH on the PUCCH resource with the selected start PRB. The case in which the determined PUCCH resource overlaps with an XDD time unit may be defined as an error case. This may mean that one available RB placement is always ensured.

[0161] (Condition 2) All configured start PRBs are checked, and within one or more configured start PRBs, there are no start PRB values ​​that would prevent the PUCCH resource from overlapping with an invalid RE for UL / PUCCH. In this case, the handling in Embodiment #0-1 may be used.

[0162] If the determined PUCCH resource is located only on a pure time unit, the first of the one or more configured start PRBs may be used.

[0163] The maximum number of initiation PRBs that can be set for a single PUCCH resource may be specified in the specification, set by RRC signaling, or reported by the UE as UE capability.

[0164] According to this embodiment, the UE can appropriately use a common PUCCH setting for both TDD UL / DL patterns and XDD UL / DL patterns.

[0165] <Embodiment #1> This embodiment relates to constraints on the setting of frequency resources (frequency domain patterns) in XDD UL / DL patterns.

[0166] Here, the frequency domain pattern for the XDD time unit may also be a D / U( / X) setting / instruction that spans the frequency domain of the XDD time unit.

[0167] Examples in Figures 6A to 6E show whether each frequency unit within a single time unit is for UL (ultra-low frequency) or DL ​​(down-deep frequency).

[0168] Examples in Figures 6A to 6B illustrate pure time units. Figure 6A shows that all frequency resources within a single pure DL time unit are for DL. This corresponds to all frequency resources within a frequency domain pattern being for DL. Figure 6B shows that all frequency resources within a single pure UL time unit are for UL. This corresponds to all frequency resources within a frequency domain pattern being for UL.

[0169] Examples in Figures 6C to 6E show examples of frequency domain patterns for a single XDD time unit. A frequency domain pattern may also show combinations of link directions in multiple frequency units (whether each frequency unit is for UL or DL). Example in Figure 6C shows an example of frequency domain pattern #1 corresponding to a single XDD time unit. Example in Figure 6D shows an example of frequency domain pattern #2 corresponding to a single XDD time unit. Example in Figure 6E shows an example of frequency domain pattern #3 corresponding to a single XDD time unit.

[0170] Embodiment #1-1 The following explanation concerns the constraints on configurable XDD UL / DL patterns for configurable frequency resources.

[0171] For possible frequency domain patterns for the XDD time unit, the UE may follow at least one of the following options 1a1 and 1a2.

[0172] [Option 1a1] For XDD time unit indications, only specific frequency domain patterns are possible. The permissible frequency domain patterns may be defined by the specification, set by RRC signaling, or reported by the UE as UE capability. For example, only the frequency domain pattern {DL for subband 1 (RB#0-#19), UL for subband 2 (RB#20-#39), and DL for subband 3 (RB#40-#51)} may be permitted. UE operation may follow at least one of the following options 1a1-1 and 1a1-2.

[0173] [[Option 1a1-1]] The UE does not assume that it will receive signaling from the base station indicating other frequency domain patterns among the frequency domain patterns permitted for the XDD time unit.

[0174] [[Option 1a1-2]] If the UE receives a frequency domain pattern other than the permitted frequency domain patterns for an XDD time unit, the UE may apply a default pattern to that time unit. The XDD time unit may conform to at least one of the following options 1a1-2A and 1a1-2B. [[[Option 1a1-2A]]] The default pattern for the XDD time unit is the default frequency domain pattern specified by the specification or set by RRC signaling. [[[Option 1a1-2B]]] The XDD time unit is considered a pure DL time unit or a pure UL time unit.

[0175] [Variations of Option 1a1] If multiple frequency domain patterns are configured, constraints may be imposed. For example, the constraint may be that some or all of the multiple frequency domain patterns include a PRB for UL, or that the multiple frequency domain patterns include a frequency domain pattern with the minimum bandwidth. In this case, common PUCCH configuration for different frequency domain patterns becomes easier.

[0176] [Option 1a2] There are no restrictions. Any frequency domain pattern (as determined by the base station) may be permitted for XDD time unit indication.

[0177] 《Embodiment #1-2》 The following description concerns the constraints on XDD UL / DL patterns that can be set for specific frequency resources.

[0178] With respect to the number of frequency domain patterns for the XDD time unit indication, the UE may follow either of the following options 1a1 and 1a2.

[0179] [Option 1a1] The number of frequency domain patterns spanning all XDD time units and the number of frequency domain patterns within a given time period is less than or equal to M (M≧1), where M may be defined by the specification, set by RRC signaling, or reported by the UE as UE capability. For example, the UE may be specified not to expect to receive a slot format instruction indicating more than M=2 frequency domain patterns spanning all XDD time units. For example, the UE may be specified not to expect to receive a slot format instruction indicating more than M=1 frequency domain patterns for an XDD time unit within a single slot.

[0180] [Option 1a2] There are no constraints on the number of frequency domain patterns per XDD time unit.

[0181] According to this embodiment, frequency resources (frequency domain patterns) can be appropriately configured for XDD time units.

[0182] <Embodiment #2> This embodiment relates to a PUCCH setting distinguished for TDD UL / DL patterns and XDD UL / DL patterns.

[0183] 《Embodiment #2-1》 The following explanation concerns the maximum number of configurable PUCCH resources.

[0184] Existing PUCCH settings may be used for pure time units.

[0185] There may be at most N distinct PUCCH settings for an XDD time unit. The mapping from the PUCCH settings to the frequency domain patterns of the XDD time units may be configured by RRC signaling. For example, PUCCH setting #1 may be configured for frequency time domain pattern (XDD time unit and frequency domain pattern) #1, and PUCCH setting #2 may be configured for frequency time domain pattern #2. For example, only one PUCCH setting may be configured for multiple XDD time units with different frequency domain patterns.

[0186] Embodiment #2-2 The following explanation concerns the selection / decision-making process for PUCCH resources.

[0187] PUCCH resource selection may be interpreted based on the corresponding PUCCH resource settings.

[0188] For PUCCH associated with DCI, PUCCH resource set selection may involve selecting a PUCCH resource set from within the corresponding PUCCH configuration. PRI may be applied to the PUCCH resource set selected within the corresponding PUCCH configuration.

[0189] For PUCCH without DCI, PUCCH resource selection may involve selecting a PUCCH resource from within the corresponding PUCCH configuration.

[0190] Embodiment #2-3 The following explanation concerns the determination of the relevant / corresponding PUCCH resource settings.

[0191] The "corresponding PUCCH (resource) settings" in Embodiment #2-2 may follow at least one of the following options 2a1 and 2a2.

[0192] [Option 2a1] If there is a DCI associated with PUCCH, that DCI may indicate which PUCCH resource setting is used for a net time unit. A new DCI field for this indication may be added within the DL grant DCI.

[0193] [Option 2a2] Which PUCCH resource setting is used may be determined by the UE based on at least one of the following different cases. The PUCCH setting for XDD time units may follow at least one of cases A and B below.

[0194] [[Case A]] A single PUCCH configuration for multiple XDD time units with multiple different frequency domain patterns (N=1 in Embodiment #2-1). The slot / sub-slot determined for reporting the PUCCH may follow at least one of the following cases A-1 to A-3. [[[Case A-1]]] The determined slot / sub-slot spans only pure time units. In the examples in Figures 7 and 8, the slots to which PUCCH(HARQ-ACK) is sent for PDSCH span only pure time units. [[[Case A-2]]] The determined slot / sub-slot spans only one or more XDD time units. In the example in Figure 9, the slot to which PUCCH(HARQ-ACK) is sent for PDSCH spans only XDD time units. [[[Case A-3]]] The determined slot / subslot is such that the slot / subslot spans a net time unit and one or more XDD time units.

[0195] [[Case B]] Multiple PUCCH settings distinct for multiple different XDD time units with multiple different frequency domain patterns (N=1 in Embodiment #2-1). The slot / sub-slot determined for PUCCH reporting may follow at least one of the following cases B-1 to B-5. [[[Case B-1]]] The determined slot / sub-slot spans only the net time units. [[[Case B-2]]] The determined slot / sub-slot spans only one or more XDD time units with only one frequency domain pattern for each of those XDD time units. [[[Case B-3]]] The determined slot / sub-slot spans only one or more XDD time units with different frequency domain patterns for one or more XDD time units. In the example in Figure 10, the slot to which PUCCH (HARQ-ACK) is sent for PDSCH spans only three XDD time units with three different frequency domain patterns. [[[Case B-4]]] The determined slot / sub-slot spans one or more XDD time units with only one frequency domain pattern for each XDD time unit, and a pure time unit. In the example in Figure 11, the slot to which PUCCH (HARQ-ACK) is sent for PDSCH spans two pure time units and one XDD time unit. [[[Case B-5]]] The determined slot / sub-slot spans one or more XDD time units with different frequency domain patterns and a pure time unit. In the example in Figure 12, the slot to which PUCCH (HARQ-ACK) is sent for PDSCH spans two XDD time units with two different frequency domain patterns and one pure time unit.

[0196] Option 2a1 is simpler but can only be applied if PUCCH is associated with DCI. Option 2a2 can be applied in any case.

[0197] [PUCCH settings for option 2a2] In Case A-1, an existing PUCCH setting for the pure time unit may be applied.

[0198] In case A-2, the PUCCH setting for the XDD time unit may be applied.

[0199] In Case A-3, the UE may follow either of the following options 2a1 or 2a2.

[0200] [Option 2a1] Case A-3 is an error case. The UE may specify that Case A-3 is not to be considered.

[0201] [Option 2a2] Case A-3 is an acceptable case. The UE may follow at least one of the following options 2a2-1 through 2a2-4. [[Option 2a2-1]] Existing PUCCH settings for pure time units may be applied. [[Option 2a2-2]] The PUCCH setting for the XDD time unit may be applied. [[Option 2a2-3]] Whether the PUCCH setting for pure time units or for XDD time units is applied may be determined by the first or last time unit type in that slot / subslot (or whether the first or last unit is a pure (UL) time unit or an XDD time unit). [[Option 2a2-4]] A dedicated default PUCCH setting may be applied to this case.

[0202] In Case B-1, an existing PUCCH setting for the pure time unit may be applied.

[0203] In case B-2, a PUCCH setting may be applied for XDD time units that overlap with PUCCH.

[0204] In Case B-3, UE may follow either of the following options 2b1 or 2b2.

[0205] [Option 2b1] Case B-3 is an error case. The UE may specify that Case B-3 is not to be considered.

[0206] [Option 2b2] Case B-3 is an acceptable case. The UE may follow at least one of the following options 2b2-1 through 2b2-2. [[Option 2b2-1]] A PUCCH setting may be applied to the frequency domain pattern of an XDD time unit that overlaps with PUCCH. This PUCCH setting may be for the frequency domain pattern of the first or last XDD time unit that overlaps with PUCCH, or for the frequency domain pattern with the highest or lowest ID among all XDD time units that overlap with PUCCH, or for the frequency domain pattern with the most or fewest UL PRBs among all XDD time units that overlap with PUCCH. [[Option 2b2-2]] The default PUCCH setting may be applied. This PUCCH setting may be the PUCCH setting with the highest or lowest ID in the PUCCH setting list (for XDD time units), the PUCCH setting for pure time units, the PUCCH setting for frequency domain patterns with the highest or lowest ID, the PUCCH setting for frequency domain patterns with the most or fewest UL PRBs, or a PUCCH setting specifically for this case.

[0207] In Case B-4, the UE operation may be based on the options for Case A-3. In this case, "PUCCH setting for XDD time unit" may be reinterpreted as "PUCCH setting for frequency domain pattern of XDD time unit overlapping with that PUCCH".

[0208] In Case B-5, UE may follow either of the following options 2c1 or 2c2.

[0209] [Option 2c1] Case B-5 is an error case. The UE may specify that Case A-3 is not to be considered.

[0210] [Option 2c2] Case B-5 is an acceptable case. The UE may follow at least one of the following options 2c2-1 through 2c2-4. [[Option 2c2-1]] Existing PUCCH settings for pure time units may be applied. [[Option 2c2-2]] The PUCCH setting for the XDD time unit may be applied. [[Option 2c2-3]] Whether the PUCCH setting for pure time units or for XDD time units is applied may be determined by the first or last time unit type in that slot / subslot (or whether the first or last unit is a pure (UL) time unit or an XDD time unit). [[Option 2c2-4]] A dedicated default PUCCH setting may be applied to this case.

[0211] [Variation of Option 2a2] Which PUCCH resource setting is used may be determined by the UE based on at least one of the following different cases. The PUCCH setting for XDD time units may follow at least one of cases 1 to 3 below.

[0212] [[Case 1]] The slots / sub-slots determined for PUCCH reporting span only net time units.

[0213] [[Case 2]] The slot / sub-slot determined for PUCCH reporting spans only one or more XDD time units. These one or more XDD time units may follow either case 2-1 or 2-2 below. [[[Case 2-1]]] Each of these one or more XDD time units is accompanied by only one frequency domain pattern. [[[Case 2-2]]] Each of these XDD time units is associated with a different frequency domain pattern.

[0214] [[Case 3]] The slot / sub-slot determined for PUCCH reporting spans a net time unit and one or more XDD time units. These one or more XDD time units may follow one of the following cases 3-1 to 3-2. [[[Case 3-1]]] Each of these one or more XDD time units is accompanied by only one frequency domain pattern. [[[Case 3-2]]] Each of these XDD time units is associated with a different frequency domain pattern.

[0215] [PUCCH settings for variations of Option 2a2] [[Case 2]] [[[Case 2-1]]] If a single PUCCH setting is configured for multiple XDD time units with different frequency domain patterns (N=1 in Embodiment #2-1), that PUCCH setting may be applied to those multiple XDD time units.

[0216] If multiple distinct PUCCH settings are configured for multiple different XDD time units with multiple different frequency domain patterns (N>1 in Embodiment #2-1), then the PUCCH setting for a specific XDD time unit among those multiple XDD time units may be applied to those multiple XDD time units.

[0217] [[[Case 2-2]]] UE may follow either of the following options 2d1 or 2d2.

[0218] [Option 2d1] Case 2-2 is an error case. The UE may be specified as not assuming Case 2-2.

[0219] [Option 2d2] Case 2-2 is an acceptable case.

[0220] If a single PUCCH setting is configured for multiple XDD time units with different frequency domain patterns (N=1 in Embodiment #2-1), or if multiple distinct PUCCH settings are configured for multiple different XDD time units with different frequency domain patterns (N>1 in Embodiment #2-1) and the same single PUCCH setting is mapped to multiple frequency domain patterns, then that (same / single) PUCCH setting may be applied to all XDD time units that overlap with that PUCCH.

[0221] If multiple distinct PUCCH settings are configured for multiple different XDD time units with multiple different frequency domain patterns (N>1 in Embodiment #2-1) and each of the multiple different PUCCH settings is mapped to multiple frequency domain patterns, the UE may follow the following options 2d2-1 and 2d2-2. [[Option 2d2-1]] The PUCCH setting may be applied to the frequency domain pattern of the first or last XDD time unit among the XDD time units that overlap with the PUCCH. [[Option 2d2-2]] The default PUCCH setting may be applied. This PUCCH setting may be a PUCCH setting with the lowest or highest index in the PUCCH setting list (for XDD time units), a PUCCH setting for pure time units, or a PUCCH setting specifically for this case.

[0222] [[Case 3]] [[[Case 3-1]]] UE may follow either option 2e1 or 2e2 below.

[0223] [Option 2e1] Case 3-1 is an error case. The UE may be specified as not assuming Case 3-1.

[0224] [Option 2e2] Case B-3 is an acceptable case. The UE may follow at least one of the following options 2e2-1 through 2e2-4. [[Option 2e2-1]] Existing PUCCH settings for pure time units may be applied. [[Option 2e2-2]] The PUCCH setting for the XDD time unit may be applied. [[Option 2e2-3]] Whether the PUCCH setting for pure time units or for XDD time units is applied may be determined by the first or last time unit type in that slot / subslot (or whether the first or last unit is a pure (UL) time unit or an XDD time unit). [[Option 2e2-4]] A dedicated default PUCCH setting may be applied to this case.

[0225] [[[Case 3-2]]] UE may follow either of the following options 2f1 or 2f2.

[0226] [Option 2f1] Case 3-2 is an error case. It may be specified that the UE does not assume Case 3-2.

[0227] [Option 2f2] Case 3-2 is an allowable case. The UE may comply with at least one of the following options 2f2-1 to 2f2-4. [[Option 2f2-1]]The existing PUCCH configuration for pure time units may be applied. [[Option 2f2-2]]The PUCCH configuration for XDD time units may be applied. [[Option 2f2-3]]Whether the PUCCH configuration for pure time units or the PUCCH configuration for XDD time units is applied may be determined according to the first or last time unit type in the slot / subslot (may be determined according to whether a pure (UL) time unit is the first or last, or whether an XDD time unit is the first or last). [[Option 2f2-4]]A dedicated default PUCCH configuration for this case may be applied.

[0228] <<Embodiment #2-4>> The following description relates to the case where a configured PUCCH resource collides with an invalid RE for UL / PUCCH.

[0229] The UE operation in this case may comply with any one of the following options 2b1 to 2b3.

[0230] [Option 2b1] This case is an error case. It may be specified that the UE does not assume that the PUCCH resource determined (based on the PUCCH resource configuration for XDD time units distinguished from that for pure time units) overlaps any invalid RE in an XDD time unit.

[0231] [Option 2b2] This case is an acceptable case. When the determined PUCCH resource overlaps with an invalid RE in the XDD time unit, the UE behavior may utilize the method of Embodiment #0-1.

[0232] [Option 2b3] If the PUCCH is associated with a DCI, this is an error case; if the PUCCH is not associated with any DCI, this is an acceptable case. If a PUCCH associated with a DCI has a PUCCH setting distinct for XDD time units, the UE may be required not to assume that the determined PUCCH resource (based on the PUCCH resource setting distinct for XDD time units from that for pure time units) overlaps with any invalid RE within the XDD time unit. For a PUCCH without an associated DCI, the UE behavior when the determined PUCCH resource overlaps with an invalid RE within the XDD time unit may utilize the method of Embodiment #0-1.

[0233] According to this embodiment, PUCCH settings can be appropriately configured separately for pure time units (TDD UL / DL patterns) and XDD time units (XDD UL / DL patterns).

[0234] <Other Embodiments> 《UE Ability Information / Higher Layer Parameters》 Higher layer parameters (RRC IE) / UE capabilities may be defined corresponding to the features in each of the above embodiments. The higher layer parameters may indicate whether or not to enable the feature. The UE capabilities may indicate whether or not the UE supports the feature.

[0235] A UE that has the corresponding higher-level parameter set may perform that function. It may also be stipulated that "a UE that does not have the corresponding higher-level parameter set may not perform that function (for example, according to Rel. 15 / 16)."

[0236] A UE that reports / submits UE capability indicating support for that function may perform that function. It may be stipulated that "a UE that has not reported UE capability indicating support for that function shall not perform that function (e.g., in accordance with Rel. 15 / 16)."

[0237] If the UE reports / sends a UE capability indicating support for that function, and the corresponding higher-layer parameters are set, the UE may perform that function. It may also be stipulated that "if the UE does not report / send a UE capability indicating support for that function, or if the corresponding higher-layer parameters are not set, the UE shall not perform that function (e.g., in accordance with Rel. 15 / 16)."

[0238] Which of the above multiple embodiments / options / choices / features is used may be set by higher-layer parameters, reported by the UE as UE capability, specified in the specification, or determined by the reported UE capability and the setting of the higher-layer parameters.

[0239] UE capability may indicate whether the UE supports at least one of the following features: • PUCCH settings common to both XDD time units and pure time units. • Differentiated PUCCH settings for XDD time units and pure time units. • PUCCH (transmit) associated with DCI overlapping with an invalid RE within the XDD time unit. Rate matching in active REs (around invalid REs) when PUCCH overlaps with invalid REs within an XDD time unit. • Limitations on frequency domain patterns of XDD time units. • Limitations on the number of frequency domain patterns in an XDD time unit. • Multiple PUCCH settings distinct for multiple XDD time units, each with a different frequency domain pattern for different numbers of celestial bodies. • The applicable PUCCH settings must be as instructed by DCI.

[0240] UE capability may be such that the UE exhibits at least one of the following values: • The maximum number of PUCCH settings common to both pure time units and XDD time units. • Maximum number of PUCCH settings for pure time units. • Maximum number of PUCCH settings for XDD time units.

[0241] Based on the above UE capabilities / higher layer parameters, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

[0243] Figure 13 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0244] Further, the wireless communication system 1 may support dual connectivity between a plurality of Radio Access Technologies (RATs) (multi-RAT Dual Connectivity (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)), and the like.

[0245] In EN-DC, a base station (eNB) of LTE (E-UTRA) serves as a Master Node (MN), and a base station (gNB) of NR serves as a Secondary Node (SN). In NE-DC, an NR base station (gNB) serves as the MN, and an LTE (E-UTRA) base station (eNB) serves as the SN.

[0246] The wireless communication system 1 may support dual connectivity between a plurality of 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))).

[0247] The wireless communication system 1 may include: a base station 11 that forms a macro cell C1 with relatively wide coverage; and base stations 12 (12a to 12c) that are disposed within the macro cell C1 and form small cells C2 narrower than the macro cell C1. A user terminal 20 may be located in at least one cell. The arrangement, number, and the like of each cell and the user terminal 20 are not limited to the aspect shown in the drawing. Hereinafter, when the base stations 11 and 12 are not distinguished from each other, they are collectively referred to as a base station 10.

[0248] 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).

[0249] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 fall in a frequency band higher than FR2.

[0250] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0251] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0252] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0253] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0254] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0255] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0257] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0258] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0260] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0261] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0262] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0263] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0264] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0265] 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, as DL-RS, 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.

[0266] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0267] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0268] (base station) Figure 14 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0269] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0270] The control unit 110 controls the entire base station 10. The control unit 110 can consist of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0271] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140. 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 also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of radio resources, etc.

[0272] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0273] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0274] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0275] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0276] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0277] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.

[0278] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

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

[0280] 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 130.

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

[0282] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

[0283] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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.

[0284] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0285] The transmitting / receiving unit 120 may transmit first information relating to a first time unit in which downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth, and may transmit a first setting of a physical uplink control channel (PUCCH). The control unit 110 may control the reception of the first PUCCH within the first time unit based on the first information and the first setting.

[0286] The transmitting / receiving unit 120 may transmit information about one or more patterns indicating the link direction of one or more frequency units within one or more time units in which downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth. The control unit 110 may control transmission or reception within the one or more time units based on the information. The information may be subject to at least one constraint of the available patterns and the number of the one or more patterns.

[0287] (User terminal) Figure 15 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0288] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, 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 part described below may be omitted.

[0289] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0291] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0292] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0293] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0294] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0295] The transmitting / receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0296] The transmitting / receiving unit 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 and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

[0297] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0298] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

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

[0300] 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.

[0301] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (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.

[0302] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also 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.

[0303] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0304] The transmitting / receiving unit 220 may receive instructions for the link direction (e.g., D / U / F) for a first time resource (e.g., time unit) and the availability of some frequency resources within the first time resource (e.g., partially available, partially usable, partially unavailable). Based on these instructions, the control unit 210 may control uplink transmission or downlink reception on the frequency resources within the first time resource.

[0305] The aforementioned availability may indicate that the frequency resource is available for the downlink, that the frequency resource is not available for the downlink, that the frequency resource is available for the uplink, or that the frequency resource is not available for the uplink.

[0306] The transmitting / receiving unit 220 may receive a first setting of a first type of channel or signal for the first time resource and a second setting of the first type of channel or reference signal for the second time resource whose availability is not indicated. The control unit 210 may control the transmission or reception of the first type of channel or reference signal in the first time resource based on the first setting, and control the transmission or reception of the first type of channel or reference signal in the second time resource based on the second setting.

[0307] The transmission or reception of the second type of channel or signal may take place in a time resource whose availability is not indicated, and may not take place in the first time resource.

[0308] The transmitting / receiving unit 220 may receive first information (e.g., XDD time unit) relating to a first time unit (e.g., XDD UL / DL pattern / frequency domain pattern setting / instruction) in which downlink resources (e.g., DL frequency unit) and uplink resources (e.g., UL frequency unit) are frequency-division multiplexed (FDM) within a specific bandwidth (e.g., one CC / BWP), and may also receive first settings of a physical uplink control channel (PUCCH) (e.g., PUCCH setting for the XDD time unit, or PUCCH setting common to the XDD time unit and the pure time unit). The control unit 210 may control the transmission of the first PUCCH within the first time unit based on the first information and the first settings (Embodiment #0 / #2).

[0309] The control unit 210 may receive second information (e.g., TDD UL / DL pattern settings / instructions) relating to a second time unit (e.g., a pure time unit) in which downlink resources and uplink resources are not frequency-division multiplexed within the specified bandwidth, and may also receive a second setting of PUCCH within the second time unit (e.g., PUCCH setting for the pure time unit). Based on the second information and the first setting, the control unit 210 may control the transmission of the second PUCCH within the second time unit.

[0310] The transmitting / receiving unit 220 may receive second information relating to a second time unit in which downlink resources and uplink resources are not frequency-division multiplexed within the specified bandwidth, and may receive a second setting for PUCCH within the second time unit. The control unit 210 may control the transmission of the second PUCCH within the second time unit based on the second information and the second setting.

[0311] The control unit 210 may control the transmission of the first PUCCH based on at least one of the following: whether the first PUCCH is associated with downlink control information, and whether the first PUCCH overlaps with the second time unit.

[0312] The transmitting / receiving unit 220 may receive information (settings / instructions) regarding one or more patterns (e.g., frequency domain patterns) indicating the link direction (e.g., D / L / X) of one or more frequency units within one or more time units (e.g., XDD time units) in which downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth (e.g., one CC / BWP). The control unit 210 may control transmission or reception within the one or more time units based on the information. The information may be subject to at least one constraint of the available patterns and the number of the one or more patterns (Embodiment #1).

[0313] If one or more of the above patterns are not among the available patterns, the control unit 210 may control transmission or reception within one or more time units based on another pattern.

[0314] If the one or more patterns are multiple patterns, the constraint may be that some or all of the multiple patterns include uplink resources, or that some of the multiple patterns have minimum bandwidth.

[0315] The aforementioned constraint may be the maximum value of the aforementioned number.

[0316] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0317] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0319] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0320] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

[0321] 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 the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0322] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0323] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0324] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0325] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), 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 called an auxiliary storage device.

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

[0327] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0329] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0330] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0331] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0332] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

[0333] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0334] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0335] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0336] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0337] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0338] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0339] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0340] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0341] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0342] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0343] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0344] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0345] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0346] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0347] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0348] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0349] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0351] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0353] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0354] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0355] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0356] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0357] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not providing notification of the specified information or by providing notification of other information).

[0358] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0359] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0360] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0361] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0362] In this 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," and "panel" may be used interchangeably.

[0363] In this disclosure, terms such as "Base Station (BS)", "wireless 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", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0364] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0365] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0366] A mobile station may also be called 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 appropriate term.

[0367] 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 also be a device mounted on a moving object, the moving object itself, etc.

[0368] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0369] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.

[0370] Figure 17 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0371] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0372] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0373] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression signal of accelerator pedal 43 acquired by accelerator pedal sensor 55, brake pedal depression signal of brake pedal 44 acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by object detection sensor 58.

[0374] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, displays, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0375] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0376] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0377] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0378] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0379] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above input.

[0380] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0381] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0382] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.

[0383] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0384] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0385] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0386] Each aspect / embodiment described in this disclosure includes 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 (where x is, for example, an integer or 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0387] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0388] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0389] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0390] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0391] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0392] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0393] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0394] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0395] In this 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 "combine" may be interpreted similarly to "different."

[0396] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0397] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0398] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives first information relating to a first time unit in which downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth, and a first setting of a physical uplink control channel (PUCCH) within the first time unit, and second information relating to a second time unit in which downlink resources and uplink resources are not frequency-division multiplexed within the specific bandwidth, and a second setting of a PUCCH within the second time unit, and receives Downlink Control Information (DCI), The DCI includes a control unit that controls the transmission of PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction included in the DCI, A terminal wherein the control unit transmits capability information indicating support for the ability to control the transmission of PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction, prior to receiving the first information, the first setting, the second information, and the second setting.

2. The steps include receiving first information relating to a first time unit in which downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth, and a first setting of a physical uplink control channel (PUCCH) within the first time unit, The steps include receiving second information relating to a second time unit in which downlink resources and uplink resources are not frequency-division multiplexed within the specified bandwidth, and a second setting of PUCCH within the second time unit. The steps include receiving Downlink Control Information (DCI), A step of controlling the transmission of PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction included in the DCI, A step of transmitting capability information indicating support for the ability to control the transmission of PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction, prior to receiving the first information, the first setting, the second information, and the second setting. A wireless communication method for a terminal having the following features.

3. A receiving unit that receives capability information, A transmitting unit that, upon receiving the capability information, transmits first information relating to a first time unit in which downlink resources and uplink resources are frequency-division multiplexed within a specific bandwidth, and a first setting of the physical uplink control channel (PUCCH) within the first time unit, and upon receiving the capability information, transmits second information relating to a second time unit in which downlink resources and uplink resources are not frequency-division multiplexed within the specific bandwidth, and a second setting of the PUCCH within the second time unit, and transmits Downlink Control Information (DCI). The DCI includes a control unit that controls the reception of PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction included in the DCI, The capability information indicates support for the ability to control the transmission of the PUCCH according to either the first setting or the second setting corresponding to the PUCCH resource instruction, at the base station.

4. A system comprising the terminal described in Claim 1 and a base station, The aforementioned base station is A system having a transmitting unit that transmits the DCI.

Images