Terminal, wireless communication method, base station, and system

Abstract

To appropriately control frequency hopping in a time resource applicable to an uplink and a downlink.SOLUTION: A terminal according to the present invention includes a receiver configured to receive indication information indicating that a time resource is applicable to an uplink and a downlink, and receive control information for the time resource, and a controller configured to control uplink frequency hopping in the time resource based on the control information, wherein the controller controls a start position of the frequency hopping based on the indication information.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

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

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

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

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

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

[0007] However, in the current NR specifications, methods for increasing uplink resources have not been fully considered. If these methods cannot be properly controlled, there is a risk of system performance degradation, such as increased latency and reduced coverage.

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

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives instruction information indicating that a time resource is applicable to an uplink and a downlink and receives control information for the time resource, and a control unit that controls uplink frequency hopping in the time resource based on the control information, and the control unit controls the start position of the frequency hopping based on the instruction information. [Effects of the Invention]

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

[0011] [Figure 1] 1A and 1B are diagrams showing an example of setting a slot configuration. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of an XDD. [Figure 3] 3A and 3B are diagrams illustrating an example of the configuration of time domain and frequency domain resources for XDD operation. [Figure 4] FIG. 4 is a diagram showing an example of a slot format according to the first embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of UE operation according to option 1 of the second embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of an error case according to option 1 of the second embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of UE operation according to option 2 of the second embodiment. [Figure 8] 8A and 8B are diagrams illustrating an example of a UE operation according to the third embodiment. [Figure 9] 9A and 9B are diagrams showing an example of a DL reception determination method according to the third embodiment. [Figure 10] 10A and 10B are diagrams illustrating an example of a UL transmission determination method according to the third embodiment. [Figure 11] 11A to 11C are diagrams illustrating an example of UE operation according to option 2 of the fourth embodiment. [Figure 12] 12A and 12B are diagrams illustrating an example of a UE operation according to the fifth embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (TDD settings) In Rel. 15, UL and DL resources (UL resources and DL resources) for Time Division Duplex (TDD) are configured for the UE. The UE may receive higher layer parameters for cell-specific UL / DL TDD configuration (TDD-UL-DL-ConfigCommon) or UE-specific UL / DL TDD configuration (TDD-UL-DL-ConfigDedicated).

[0013] The higher layer parameters for cell-specific UL / DL TDD configuration (TDD-UL-DL-ConfigCommon) include a parameter for setting the reference subcarrier spacing (referenceSubcarrierSpacing) and a parameter for TDD UL and DL patterns (TDD-UL-DL-Pattern).

[0014] The TDD-UL-DL-Pattern includes a parameter (dl-UL-TransmissionPeriodicity) that sets the period of the DL-UL pattern, a parameter (nrofDownlinkSlots) that sets the number of consecutive DL slots, a parameter (nrofDownlinkSymbols) that sets the number of consecutive DL symbols, a parameter (nrofUplinkSlots) that sets the number of consecutive UL slots, and a parameter (nrofUplinkSymbols) that sets the number of consecutive UL symbols.

[0015] The slot and slot index are configured in the higher layer parameters (TDD-UL-DL-ConfigDedicated) related to the UE-specific UL / DL TDD configuration.

[0016] The slot is configured using the parameter TDD-UL-DL-SlotConfig. TDD-UL-DL-SlotConfig includes a parameter related to the slot index (TDD-UL-DL-SlotIndex) and a parameter related to the symbols that make up the slot (symbols). The parameter related to the symbols that make up the slot (symbols) can be set to either a parameter indicating that all symbols that make up the slot are used for DL ​​(allDownlink), a parameter indicating that all symbols that make up the slot are used for UL (allUplink), or a parameter that explicitly indicates the number of symbols (explicit).

[0017] The parameter (explicit) that explicitly indicates the number of symbols includes a parameter (nrofDownlinkSymbols) that sets the number of DL symbols and a parameter (nrofUplinkSymbols) that sets the number of UL symbols.

[0018] The UE determines the slots / symbols to use for transmitting UL signals / channels and / or receiving DL signals / channels based on the above parameters.

[0019] (XDD) Considering the time ratio of transmission and reception (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel. 16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL ​​signals / channels. In such cases, UEs cannot transmit UL signals / channels frequently, which raises concerns about delays in transmission of important UL signals / channels. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal / channel congestion during UL transmission opportunities. Furthermore, since TDD limits the time resources available for UL signal / channel transmission, the application of UL coverage extension techniques, such as repetition transmission, is also limited.

[0020] In future wireless communication systems (for example, Rel. 17 / 18 and later), the introduction of a frequency division duplexing method that combines TDD and frequency division duplex (FDD) for UL and DL is being considered.

[0021] This division duplexing method may be called XDD (Cross Division Duplex). XDD may refer to a duplexing method in which DL and UL are frequency-division multiplexed (DL and UL can be used simultaneously) within one component carrier (CC) in the TDD band.

[0022] Fig. 1A is a diagram showing an example of TDD configuration defined up to Rel. 16. In the example shown in Fig. 1A, TDD slots / symbols are configured for a UE within the bandwidth of one component carrier (CC) (which may also be called a cell or serving cell).

[0023] In the example shown in Figure 1A, the time ratio of DL slots to UL slots is 4:1. This slot / symbol setting in conventional TDD does not ensure sufficient UL time resources, which can result in UL transmission delays and reduced coverage performance.

[0024] Fig. 1B is a diagram showing an example of the configuration of XDD. In the example of Fig. 1B, within one component carrier (CC), resources used for DL ​​reception and resources used for UL transmission overlap in time. With such a resource configuration, UL resources can be secured, and resource utilization efficiency can be improved.

[0025] For example, as shown in the example of Fig. 1B, by configuring both ends of the frequency domain in one CC as DL and sandwiching UL resources between the DL, it is possible to avoid and mitigate the occurrence of cross link interference (CLI) with neighboring carriers. Also, a guard area may be set at the boundary between the DL resource and the UL resource.

[0026] Considering the complexity of handling self-interference, it is possible for only the base station to use DL and UL resources simultaneously, i.e., where DL and UL resources overlap in time, one UE may use the DL resource and another UE may use the UL resource.

[0027] Fig. 2 is a diagram showing an example of the configuration of XDD. In the example shown in Fig. 2, part of the DL resources of the TDD band is used as UL resources, and the DL and UL are configured to overlap in time.

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

[0029] Furthermore, during the period when DL and UL overlap in time, one UE (UE#1 in the example of FIG. 2) receives the DL channel / signal, and another UE (UE#2 in the example of FIG. 2) transmits the UL channel / signal. During this period, the base station simultaneously transmits and receives DL and UL.

[0030] Additionally, during the UL-only period, each of the multiple UEs transmits an UL channel / signal.

[0031] In existing NR (e.g., those specified up to Rel. 15 / 16), DL frequency resources and UL frequency resources of a UE carrier are configured as DL Bandwidth Parts (BWPs) and UL BWPs, respectively. To switch DL / UL frequency resources to other DL / UL frequency resources, multiple BWP configurations and a BWP adaptation mechanism are required.

[0032] In addition, in existing NR, the time resource in the TDD carrier for the UE is configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.

[0033] The time and frequency domain resource configuration methods for XDD operation are being considered. For example, for UE#1 in Figure 2, the XDD resource (duration of DL and UL overlap) can be configured similarly to the existing DL resource (e.g., by using Frequency Domain Resource Allocation (FDRA) to avoid using part of the UL resource), minimizing the impact on the specification / UE (see Figure 3A).

[0034] Also, for example, for UE#2 in Figure 2, the XDD resources can be set to the same as the existing UL resources (e.g., by using Frequency Domain Resource Allocation (FDRA) to avoid using part of the DL resources), thereby minimizing the impact on the specifications / UE (see Figure 3B).

[0035] Time resources (subframes / slots / minislots / symbols) can be designated for different link directions for different UEs. Periodic / semi-persistent RS is considered to enable XDD for some UEs on DL time resources. UL channel / RS configuration is considered to enable XDD for some UEs on UL time resources.

[0036] Each UE needs to know whether resources are being used for XDD operations or not.

[0037] For example, for UE#1 as shown in Figure 2, the overlapping portion of the DL and UL in the TDD band (which may be called the XDD portion) can be configured as DL. However, it is unclear whether the frequency resources of the XDD portion should be configured separately from the frequency resources of the DL-only portion (e.g., the DL portion other than the XDD portion).

[0038] Since the UL part of the frequency resources of the XDD part can be used by other UEs (e.g., UE #2 in Figure 2) for UL transmission, there is a concern that CLI may occur if DL reception is performed in that part (UL part of the XDD part).In addition, it is being considered to disable DL resource allocation to that part in order to allocate the remaining resources other than that part to a single UE.

[0039] However, it is not clear how the link direction of each resource for XDD is specified. If the method for specifying the link direction is not clear, proper transmission and reception cannot be performed, and there is a risk that communication quality / communication throughput will decrease.

[0040] Therefore, the present inventors came up with the idea of ​​a method for indicating the link direction and the corresponding UE operation.

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

[0042] (Wireless communication method) The DL signal / channel in the present disclosure may be transmitted using unicast or may be transmitted using multicast / broadcast to multiple UEs, and the multicast / broadcast / unicast configuration may be performed using higher layer signaling.

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

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

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

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

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

[0048] In the present disclosure, reception of DL signals / channels and transmission of UL signals / channels may be transmitted and received using the same BWP / CC / band / operating band, or may be transmitted and received using different BWP / CC / band / operating band. In the following drawings of the present disclosure, a configuration for one CC will be described, but the number of resources in the frequency direction is not limited to this. In the present disclosure, the terms BWP, CC, cell, serving cell, band, carrier, operating band, PRG, PRB, RB, RE, and resource may be interchangeable.

[0049] In the present disclosure, A overlaps with B, A overlaps with B, and at least a portion of A overlaps with at least a portion of B may be read interchangeably.

[0050] Each embodiment of the present disclosure may be applied under at least one of the following conditions: when a UE reports UE capabilities corresponding to at least one function / capability in each embodiment to a NW; and when a UE capability corresponding to at least one function / capability in each embodiment is configured / activated / instructed to the UE by higher layer signaling. Each embodiment of the present disclosure may be applied when a specific higher layer parameter is configured / activated / instructed to the UE.

[0051] In this disclosure, the time domain (period) in which DL resources and UL resources within one CC of a TDD band are simultaneously available, the XDD portion, and the XDD period may be interpreted interchangeably. DL / UL resources in the XDD portion may be referred to as XDD DL / UL resources, XDD DL / UL, new DL / UL resources, etc. DL / UL resources in which the DL and UL of the TDD band do not overlap in time may be interpreted as non-XDD DL / UL resources, pure DL / UL resources, non-XDD DL / UL resources, normal (traditional, existing) DL / UL resources, etc. XDD operation may refer to operation during a period in which XDD DL / UL resources are configured, or may refer to operation of the entire TDD in which XDD can be used.

[0052] Furthermore, in the present disclosure, DL / UL BWP in the TDD band, DL / UL BWP defined up to Rel. 15 / 16, and normal DL / UL BWP may be interpreted as interchangeable.

[0053] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, etc. may be read interchangeably.

[0054] A time resource (unit time resource) of a certain size (unit time, time domain granularity) may be called a time unit. The terms time unit, subframe, slot, subslot, and symbol may be interchangeable.

[0055] A frequency resource (unit frequency resource) of a certain size (unit frequency, frequency domain granularity) may be called a frequency unit. The terms frequency unit, BWP, subband, RB bundle, RB, and subcarrier may be interchangeable.

[0056] A frequency-time resource (unit resource) having a frequency resource (unit frequency resource) of a certain size (unit frequency, frequency domain granularity) and a time resource (unit time resource) of a certain size (unit time, time domain granularity) may be referred to as a frequency-time unit.

[0057] One or more frequency-time units that are all for the downlink (DL) may be referred to as pure DL units or DL ​​units. One or more frequency-time units that are all for the uplink (UL) may be referred to as pure UL units or UL units. A pure DL unit and a pure UL unit (one or more frequency-time units that include only one link direction) may be referred to as a pure unit.

[0058] If one or more frequency-time units within a time unit are all for DL, the time unit may be referred to as a pure DL time unit or DL ​​time unit. If one or more frequency-time units within a time unit are all for UL, the time unit may be referred to as a pure UL time unit or UL time unit. Pure DL time units and pure UL time units (time units that include only one link direction) may be referred to as pure time units.

[0059] If one or more frequency-time units in a frequency unit are all for DL, the frequency unit may be called a pure DL frequency unit or DL ​​frequency unit. If one or more frequency-time units in a frequency unit are all for UL, the frequency unit may be called a pure UL frequency unit or UL frequency unit. Pure DL frequency units and pure UL frequency units (frequency units that include only one link direction) may be called pure frequency units.

[0060] If a time unit includes a frequency-time unit for DL ​​and a frequency-time unit for UL, the time unit may be called an XDD time unit, a flexible time unit, a mixed time unit, a special time unit, a special time resource, a time resource applicable to uplink and downlink, etc.

[0061] If a frequency unit includes a frequency-time unit for DL ​​and a frequency-time unit for UL, the frequency unit may be referred to as an XDD frequency unit, a flexible frequency unit, a mixed frequency unit, a special frequency unit, a special frequency resource, etc.

[0062] At least one of the one or more frequency-time units including a frequency-time unit for DL ​​and a frequency-time unit for UL (two link directions) and the one or more frequency-time units including a frequency-time unit whose link direction is designated as flexible (F) or XDD (F) may be referred to as an XDD unit, a flexible unit, a mixed unit, a special unit, a special resource, etc.

[0063] In the present disclosure, the slot format for a time / frequency / frequency-time unit may indicate at least one of D, U, F, and X. X may indicate XDD units / XDD time units / XDD frequency units.

[0064] In the present disclosure, the terms slot format, unit format, frequency-time unit format, XDD time unit format, and XDD format may be read interchangeably.

[0065] In the present disclosure, A overlapping with B and all or part of A overlapping with all or part of B may be read interchangeably.

[0066] First Embodiment For XDD, the slot format indication may be extended to a frequency-time domain indication.

[0067] The time domain granularity may be the same as that of Rel.15 / 16 NR. That is, the time domain granularity may be at the slot / symbol level. The time domain size (duration) indicated by the slot format indication (of the resource to which the slot format indication applies) may be indicated by the length of the slot format indication or by a periodicity. The periodicity may be configured by an RRC IE.

[0068] The frequency domain granularity may be at the level of a resource block (RB) / RB bundle / subband, and the frequency domain size (bandwidth) indicated by the slot format indication (of the resource to which the slot format indication applies) may be at the level of a cell (CC) / BWP.

[0069] The slot format indication may not support (option 1) or may support (option 2) a "flexible" (F) indication for the frequency-time unit. In option 1, the slot format indication may indicate D or U for the frequency-time unit. In option 2, the slot format indication may indicate D, U, or F for the frequency-time unit.

[0070] The slot format indication may be one of the following options 1 and 2.

[0071] Option 1: 1 level instruction The D / U / (F) indication for frequency-time units is frequency-first or time-first order.

[0072] For the example of FIG. 4, the slot format indication using option 1 frequency-first ordering is "DDDDDDDDDFUDFFFFUUFFUUUU".

[0073] Option 2: 2-level instruction At the first level, one-dimensional (time domain or frequency domain) indication is performed, and at the second level, two-dimensional indication based on the one-dimensional indication is performed. The first-level indication may be an indication per time unit. The second-level indication may be an indication for a frequency-time unit within an XDD time unit. The second-level indication may be in frequency-first or time-first order, as in option 1. Option 2 can reduce signaling overhead compared to option 1.

[0074] For the example of FIG. 4, the first level designation for option 2 is "DDXXXU" and the second level designation using frequency-first ordering is "DFUDFFFFUUFF".

[0075] The slot format indication may be performed using at least one of the following indication methods: semi-static setting by RRC, indication by MAC CE, and dynamic indication by an existing or new DCI format.

[0076] The two-level indication may use different indication methods for the two levels. For example, the first-level indication may use semi-static configuration by RRC, and the second-level indication may use dynamic indication by DCI. The first-level indication may indicate the length of a DL time unit / UL time unit / XDD time unit using the number of slots / symbols. For example, the first-level indication may indicate the first DL time unit and the last UL time unit within a certain period (cycle). The interval between the DL time unit and the UL time unit may be XDD time units.

[0077] If the slot format indication is dynamically notified and the UE fails to receive the slot format indication, the UE may follow any of the following actions 1 to 3. Action 1: The UE follows option 2 of the second embodiment. [[Action 2]] If there is an implicit indication, the UE follows option 2 of the second embodiment, or if there is no implicit indication, the UE does not transmit or receive. Action 3: The UE does not transmit or receive in the XDD time unit.

[0078] According to this embodiment, the UE can be properly instructed on the slot format including the XDD.

[0079] <Second embodiment> Whether DL reception or UL transmission occurs in an XDD time unit may be determined using an explicit link direction indication (option 1). Whether DL reception or UL transmission occurs in an XDD time unit may be determined without an explicit link direction indication (option 2).

[0080] In the present disclosure, the terms explicit link direction indication and control information may be interpreted as interchangeable.

[0081] Option 1: There is an explicit link direction for each XDD time unit The granularity of the explicit link direction indication may be the same as, smaller than, or larger than the granularity of an XDD time unit. For example, the granularity of an XDD time unit may be at the slot level, and the granularity of the explicit link direction indication may be at the symbol level. For example, the granularity of the explicit link direction indication may be N XDD time units.

[0082] [Explicit link direction method] The explicit link direction indication may follow at least one of the following indication methods 1 and 2.

[0083] [[Instruction method 1]] Dynamic indication, such as DCI (existing DCI format, new DCI format, UE-specific DCI, group-common DCI, DCI with cyclic redundancy check (CRC) scrambled with existing RNTI, DCI with CRC scrambled with new RNTI, etc.).

[0084] [[Instruction method 2]] Quasi-static RRC configuration.

[0085] [UE operation] In the UE operation of the present disclosure, the overlap of a channel / signal (UL transmission or DL ​​reception, a set of symbols of UL transmission or DL ​​reception) in one link direction with a time unit of another link direction, and the overlap of a channel / signal (UL transmission or DL ​​reception) in one link direction with a time unit of another link direction within a band containing that channel / signal (e.g., a band containing the same CC, the same BWP, or an adjacent BWP / CC) may be interpreted as interchangeable.

[0086] The UE action based on the explicit link direction indication may be at least one of the following actions 1 and 2.

[0087] [[Movement 1]] Even if a UL frequency-time unit is within a designated DL time unit, all resources on that DL time unit may be specified as unavailable for UL transmission. Even if a DL frequency-time unit is within a designated UL time unit, all resources on that UL time unit may be specified as unavailable for DL ​​reception.

[0088] It may be specified that UL transmissions that overlap the indicated DL time unit are canceled. It may be specified that UL transmissions that overlap the indicated DL time unit are rate-matched to the remaining resources in the UL frequency-time unit (and flexible frequency-time unit) within the UL time unit (and flexible time unit).

[0089] DL receptions that overlap the indicated UL time unit may be specified to be canceled. DL receptions that overlap the indicated UL time unit may be specified to be rate-matched to the remaining resources in the DL frequency-time unit (and flexible frequency-time unit) within the DL time unit (and flexible time unit).

[0090] [[Movement 2]] A DL frequency-time unit may be defined as available for DL ​​reception on a DL time unit, and a UL frequency-time unit may be defined as available for UL transmission on a UL time unit.

[0091] DL receptions that overlap the UL frequency-time unit may be specified to be canceled. DL receptions that overlap the UL frequency-time unit may be specified to be rate-matched to the remaining resources in the DL frequency-time unit (and flexible frequency-time unit) within the indicated DL time unit (and flexible time unit).

[0092] UL transmissions that overlap DL frequency-time units may be specified to be canceled. UL transmissions that overlap DL frequency-time units may be specified to be rate-matched to the remaining resources in the UL frequency-time units (and flexible frequency-time units) within the indicated UL time units (and flexible time units).

[0093] In the example of Figure 5, the DL link direction is explicitly indicated for XDD time unit #1, the UL link direction is explicitly indicated for XDD time unit #2, and the DL link direction is explicitly indicated for XDD time unit #3.

[0094] The semi-persistent scheduling (SPS) PDSCH in XDD time unit #1 is canceled because it overlaps with the UL frequency-time unit. The configured grant (CG) PUSCH in the flexible frequency-time unit in XDD time unit #2 is transmitted by the UE. The SPS PDSCH in XDD time unit #2 is canceled because it overlaps with the indicated UL time unit. The SPS PDSCH in XDD time unit #3 is canceled because it overlaps with the indicated DL time unit. The SPS PDSCH in the flexible frequency-time unit in XDD time unit #3 is received by the UE.

[0095] If the UE is configured to monitor dynamic link direction indication and no link direction indication is detected, the UE may follow any of the following actions 1 to 3. [[Action 1]] The UE falls back to option 2 of the second embodiment. [[Action 2]] If there is an implicit indication, the UE follows the implicit indication of option 2 of the second embodiment. If there is no implicit indication, the UE does not transmit or receive. Action 3: The UE does not transmit or receive in the XDD time unit.

[0096] [Restrictions (Error cases)] Explicit link direction indications may obey at least one of the following restrictions 1 through 3:

[0097] [[Limit 1]] It may be specified that the UE does not assume that the set of symbols for DL ​​reception scheduled / triggered by DCI, or the time units overlapping with that set of symbols, are indicated as UL by an explicit link direction indication.

[0098] It may be specified that the UE does not assume that the set of symbols of the UL transmission scheduled / triggered by the DCI, or the time units overlapping with that set of symbols, are indicated as DL by an explicit link direction indication.

[0099] [[Limit 2]] It may be specified that the UE does not assume that the set of symbols for configured SSB reception / Type 0 PDCCH reception, or time units overlapping with that set of symbols, are indicated as UL by explicit link direction indication.

[0100] [[Limit 3]] It may be specified that the UE does not assume that the set of symbols of a valid PRACH occasion and the set of N_gap symbols before that valid PRACH occasion, or the time units that overlap that set of symbols, are indicated as DL by an explicit link direction indication.

[0101] In the example of Figure 6, a dynamic grant (DG) PDSCH in XDD time unit #2 is scheduled by DCI. The UE does not assume that the DG PDSCH or the XDD time unit #2 that overlaps the DG PDSCH is indicated as UL. In other words, the case where the DG PDSCH or the XDD time unit #2 that overlaps the DG PDSCH is indicated as UL may be considered an error case (Limit 1).

[0102] Option 2: No explicit link direction indication for each XDD time unit Implicit link direction indication for an XDD time unit or one or more symbols may be achieved by at least one of DL or UL scheduling / triggering DCI and special channels / signals configured by higher layers (e.g., SSB / Type 0 PDCCH / PRACH).

[0103] In the present disclosure, implicit link direction indication, control information, and DCI for DL ​​or UL scheduling / triggering may be read interchangeably.

[0104] [Implicit link direction method] Specifically, the implicit link direction indication may be achieved by at least one of the following indication methods 1 to 3.

[0105] [[Instruction method 1]] A set of symbols of a DL transmission scheduled / triggered by a DCI, or a time unit overlapping that set of symbols, may be implicitly denoted as a DL symbol or DL ​​time unit. A set of symbols of a UL transmission scheduled / triggered by a DCI, or a time unit overlapping that set of symbols, may be implicitly denoted as a UL symbol or UL time unit.

[0106] [[Instruction method 2]] A set of symbols for configured SSB reception / Type 0 PDCCH reception, or a time unit that overlaps with that set of symbols, is implicitly designated as a DL symbol or DL ​​time unit.

[0107] [[Instruction method 3]] The set of symbols of a valid PRACH occasion and the set of N_gap symbols before that valid PRACH occasion, or a time unit that overlaps that set of symbols, is implicitly designated as an UL symbol or UL time unit.

[0108] [UE operation] The UE action based on the implicit link direction indication may be at least one of the following actions 1 and 2.

[0109] [[Movement 1]] Even if a UL frequency-time unit falls within an implicitly indicated DL time unit or symbol, all resources on that DL time unit or symbol may be specified as unavailable for UL transmission. Even if a DL frequency-time unit falls within an implicitly indicated UL time unit or symbol, all resources on that UL time unit or symbol may be specified as unavailable for DL ​​reception.

[0110] UL transmissions that overlap an implicitly designated DL time unit or symbol may be specified to be canceled. UL transmissions that overlap an implicitly designated DL time unit or symbol may be specified to be rate-matched to the remaining resources, if any, in the UL frequency-time unit (and flexible frequency-time unit) in time units or symbols that are not implicitly designated DL (UL time unit, flexible time unit).

[0111] DL receptions that overlap an implicitly designated UL time unit or symbol may be specified to be canceled. DL receptions that overlap an implicitly designated UL time unit or symbol may be specified to be rate-matched to the remaining resources, if any, in the DL frequency-time unit (and flexible frequency-time unit) in time units or symbols that are not implicitly designated UL (DL time unit, flexible time unit).

[0112] [[Movement 2]] A DL frequency-time unit may be defined as available for DL ​​reception on a DL time unit, and a UL frequency-time unit may be defined as available for UL transmission on a UL time unit.

[0113] DL receptions that overlap a UL frequency-time unit may be specified to be canceled. DL receptions that overlap a UL frequency-time unit may be specified to be rate-matched to the remaining resources in the DL frequency-time unit (and flexible frequency-time unit) within the indicated DL time unit (and flexible time unit) or symbol.

[0114] UL transmissions that overlap a DL frequency-time unit may be specified to be canceled. UL transmissions that overlap a DL frequency-time unit may be specified to be rate-matched to the remaining resources in the UL frequency-time unit (and flexible frequency-time unit) within the indicated UL time unit (and flexible time unit) or symbol.

[0115] In the example of Figure 7, DCI #1 in DL time unit #1 schedules a DG PDSCH in XDD time unit #2, which implicitly designates XDD time unit #2 as a DL time unit. DCI #2 in DL time unit #1 schedules a DG PUSCH in XDD time unit #3, which implicitly designates XDD time unit #3 as a UL time unit.

[0116] The DG PDSCH in XDD time unit #2 is received by the UE. The SPS PDSCH in XDD time unit #2 is canceled because it overlaps with an UL frequency-time unit. The SPS PUSCH in XDD time unit #2 is canceled because it overlaps with a DL time unit. The DG PUSCH in XDD time unit #3 is transmitted by the UE. The CG PUSCH in XDD time unit #3 is canceled because it overlaps with a DL frequency-time unit. The SPS PDSCH in XDD time unit #3 is canceled because it overlaps with an UL time unit.

[0117] [Restrictions (Error cases)] An implicit link direction indication may obey at least one of the following restrictions 1 through 3:

[0118] [[Limit 1]] It may be specified that the UE does not assume that a symbol or time unit is implicitly indicated to both DL and UL at the same time.

[0119] [[Limit 2]] It may be specified that the UE does not assume that resources for DL ​​reception scheduled / triggered by DCI or resources for configured SSB reception / Type 0 PDCCH reception overlap any frequency-time unit indicated as UL or overlap any XDD time unit that contains at least one UL frequency-time unit.

[0120] [[Limit 3]] It may be specified that the UE does not assume that resources for UL reception scheduled / triggered by DCI or resources between the symbols of a valid PRACH occasion and the N_gap symbols before that valid PRACH occasion overlap any frequency-time unit indicated as DL or overlap any XDD time unit that contains at least one DL frequency-time unit.

[0121] In the case of implicit link direction indication, specific UE behavior of channels / signals (e.g., PDSCH / PUSCH / PUCCH / CSI-RS / PRS / SRS) configured by higher layers will be described in the third embodiment.

[0122] According to this embodiment, the UE can appropriately determine its behavior in the XDD time unit.

[0123] <Third embodiment> In the case where there is no explicit link direction indication for the XDD time unit and no implicit link direction indication for DL ​​reception or UL transmission (e.g., PDSCH / PUSCH / PUCCH / CSI-RS / PRS / SRS) configured by higher layers, the UE may follow at least one of options 1 and 2 below.

[0124] In the present disclosure, the terms implicit link direction indication, control information, and DL reception or UL transmission configuration (RRC IE, higher layer signaling) may be read interchangeably.

[0125] Option 1 Higher layer configured DL reception (e.g., PDCCH / PDSCH / CSI-RS / PRS) may be prioritized over higher layer configured UL reception (e.g., PUSCH / PUCCH / SRS). The UE may follow steps 1 to 3 below.

[0126] [Step 1] The UE first determines whether to receive DL reception as configured by higher layers.

[0127] [Step 2] If the UE determines that it receives a higher layer configured DL reception on a set of symbols, it shall not transmit a higher layer configured UL transmission on that set of symbols or within an overlapping XDD time unit.

[0128] [Step 3] Otherwise, the UE decides whether to transmit a higher layer configured UL transmission.

[0129] In the example of Option 1 in Figure 8A, the SPS PDSCH and CG PUSCH are configured by higher layers within XDD time unit #1, and the CG PUSCH is configured by higher layers within XDD time unit #2. In this case, the SPS PDSCH is received by the UE within XDD time unit #1, and the CG PUSCH is canceled within XDD time unit #2. The CG PUSCH is transmitted by the UE within XDD time unit #2.

[0130] Option 2 Higher layer configured UL reception (e.g., PUSCH / PUCCH / SRS) may be prioritized over higher layer configured DL reception (e.g., PDCCH / PDSCH / CSI-RS / PRS). The UE may follow steps 1 to 3 below.

[0131] [Step 1] The UE first decides whether to transmit a UL transmission as configured by higher layers.

[0132] [Step 2] If the UE decides to send a higher layer configured UL transmission on a set of symbols, it does not receive a higher layer configured DL reception on that set of symbols or within an overlapping XDD time unit.

[0133] [Step 3] Otherwise, the UE decides whether to receive DL reception configured by higher layers.

[0134] In the example of Option 2 in Figure 8B, the SPS PDSCH and CG PUSCH are configured by higher layers within XDD time unit #1, and the SPS PDSCH is configured by higher layers within XDD time unit #2. In this case, the SPS PDSCH is canceled and the CG PUSCH is transmitted by the UE within XDD time unit #1. The SPS PDSCH is received by the UE within XDD time unit #2.

[0135] In step 1 of option 1 or step 3 of option 2, the decision of whether to receive DL reception configured by the higher layer may be made according to the following DL reception decision method.

[0136] <<How to decide whether to receive DL>> If a higher layer configured DL reception overlaps with invalid resources for the configured DL reception, collision handling for the configured DL reception is required.

[0137] The set invalid resource for DL ​​reception may follow at least one of the following invalid resource determination methods 1 and 2.

[0138] [Method 1 for determining invalid resources] The invalid resource may be an invalid resource from the frequency domain and time domain perspective, i.e., any UL frequency-time unit may be considered as an invalid resource for configured DL reception.

[0139] In the example of Figure 9A, XDD time unit #2 includes an UL frequency-time unit. In invalid resource determination method 1, the UL frequency-time unit in XDD time unit #2 is an invalid resource for configured DL reception. The UE may cancel the SPS PDSCH configured in the UL frequency-time unit.

[0140] [Method 2 for determining invalid resources] The invalid resource may be an invalid resource from a time domain perspective, i.e., any XDD time unit that contains at least one UL frequency-time unit may be considered an invalid resource for configured DL reception.

[0141] In the example of Figure 9B, XDD time unit #2 includes an UL frequency-time unit and a DL frequency-time unit. In invalid resource determination method 2, XDD time unit #2 is an invalid resource for configured DL reception. The UE may cancel the SPS PDSCH configured within XDD time unit #2.

[0142] Method 2 for determining an ineffective resource is stricter than method 1 for determining an ineffective resource.

[0143] Collision handling for configured DL reception may follow at least one of handling 1 and 2 below. [Handling 1] The UE does not receive the configured DL reception. [Handling 2] The UE receives the configured DL reception only on the remaining resources that are not invalid resources for the configured DL reception.

[0144] If the higher layer configured DL reception does not overlap with the invalid resources for the configured DL reception, the DL reception may be received on the resources of the configured DL reception.

[0145] In step 3 of option 1 or step 1 of option 2, the decision of whether to receive the UL transmission configured by the higher layer may follow the following UL transmission decision method.

[0146] If a higher layer configured UL transmission overlaps with invalid resources for the configured UL transmission, collision handling for the configured UL transmission is required.

[0147] The configured invalid resources for UL transmission may follow at least one of the following invalid resource determination methods 1 and 2.

[0148] [Method 1 for determining invalid resources] The invalid resource may be an invalid resource from the frequency domain and time domain perspective, i.e., any DL frequency-time unit may be considered as an invalid resource for configured UL transmission.

[0149] In the example of Figure 10A, XDD time unit #2 includes DL frequency-time units. In invalid resource determination method 1, the DL frequency-time units within XDD time unit #2 are invalid resources for configured UL transmission. The UE may cancel the CG PUSCH configured in the DL frequency-time units.

[0150] [Method 2 for determining invalid resources] The invalid resource may be an invalid resource from a time domain perspective, i.e., any XDD time unit that contains at least one DL frequency-time unit may be considered an invalid resource for configured UL transmissions.

[0151] In the example of Figure 10B, XDD time unit #2 includes an UL frequency-time unit and a DL frequency-time unit. In invalid resource determination method 2, XDD time unit #2 is an invalid resource for configured UL transmission. The UE may cancel the CG PUSCH configured within XDD time unit #2.

[0152] Method 2 for determining an ineffective resource is stricter than method 1 for determining an ineffective resource.

[0153] Collision handling for configured UL transmissions may follow at least one of handling 1 and 2 below. [Handling 1] The UE does not transmit the configured UL transmission. [Handling 2] The UE transmits the configured UL transmission only on the remaining resources that are not invalid resources for the configured UL transmission.

[0154] If a higher layer configured UL transmission does not overlap with the invalid resources for the configured UL transmission, the UL transmission may be transmitted on the resources of the configured UL transmission.

[0155] According to this embodiment, even if a channel / signal is configured by an upper layer within an XDD time unit in which the link direction is not indicated, the UE can appropriately control transmission / reception.

[0156] <Fourth embodiment> A UE using XDD (XDD mode) may follow either option 1 or 2 below.

[0157] Option 1 For UEs operating in XDD mode, frequency hopping of PUSCH / PUCCH is not supported.

[0158] Option 2 For UEs operating in XDD mode, frequency hopping of PUSCH / PUCCH is supported. The UE may follow either of options 2-1 and 2-2 below.

[0159] [Option 2-1] Frequency hopping of PUSCH / PUCCH occurs only if the PUSCH / PUCCH does not overlap XDD time units.

[0160] It may be specified that if (repetitions of) PUSCH / PUCCH overlap XDD time units, no frequency hopping is performed even if frequency hopping is enabled.

[0161] If the PUSCH / PUCCH (repetitions) do not overlap any XDD time unit and frequency hopping is enabled, frequency hopping may be performed.

[0162] In the example of Figure 11A, frequency hopping is applied to PUSCH #1 in UL time unit #1, and frequency hopping is not applied to PUSCH #2 in XDD time unit #2.

[0163] [Option 2-2] If the PUSCH / PUCCH overlaps the XDD time unit, frequency hopping of the PUSCH / PUCCH is also possible. The UE may follow either handling 1 or 2 below.

[0164] [Handling 1] After collision handling with the XDD time unit (eg, collision handling in the second embodiment), the frequency hopping decision is made.

[0165] The time and frequency resources for (repetitions of) PUSCH / PUCCH before frequency hopping are taken into account are used for collision handling with XDD time units (e.g., cancellation due to collisions with DL frequency-time units). In other words, if the resources for (repetitions of) PUSCH / PUCCH without frequency hopping collide, the PUSCH / PUCCH may be canceled.

[0166] Here, the time and frequency resources for a channel before frequency hopping is taken into consideration may be the time resource of that channel and the frequency resource of the first hop (start frequency resource), or the time resource of that channel and the frequency resource of the second hop, or the time resource of that channel and the frequency resources of the first hop and 22nd hop.

[0167] In the example of Figure 11B, PUSCH #1 is transmitted because the pre-frequency hopping resources of PUSCH #1 in XDD time unit #1 do not overlap with the DL frequency-time unit, and PUSCH #2 is canceled because the pre-frequency hopping resources of PUSCH #2 in XDD time unit #2 overlap with the DL frequency-time unit.

[0168] [Handling 2] The frequency hopping decision is made before the collision handling with the XDD time unit (eg, the collision handling in the second embodiment).

[0169] The time and frequency resources for (repetitions of) PUSCH / PUCCH after frequency hopping is taken into account are used for collision handling with XDD time units (e.g., cancellation due to collisions with DL frequency-time units). In other words, if resources for (repetitions of) PUSCH / PUCCH with frequency hopping collide, the PUSCH / PUCCH may be canceled, or only the colliding hops of the PUSCH / PUCCH may be canceled.

[0170] Here, the time and frequency resources for a channel after frequency hopping is taken into account may be a first hop resource and a second hop resource.

[0171] In the example of Figure 11C, the frequency-hopped resources of PUSCH #1 in XDD time unit #1 do not overlap with the DL frequency-time unit, so PUSCH #1 is transmitted. Of the frequency-hopped resources of PUSCH #2 in XDD time unit #2, the first hop overlaps with the DL frequency-time unit, but the second hop does not overlap with the DL frequency-time unit, so the first hop is canceled and the second hop is transmitted.

[0172] UE behavior (option 1 / 2 / 2-1 / 2-2 / handling 1 / 2) may differ between intra-slot and inter-slot frequency hopping. UE behavior (option 1 / 2 / 2-1 / 2-2 / handling 1 / 2) may differ between intra-time unit and inter-time unit frequency hopping.

[0173] The UE behavior (option 1 / 2 / 2-1 / 2-2 / handling 1 / 2) may differ between frequency hopping within an XDD time unit and frequency hopping within a pure time unit.

[0174] The setting of frequency hopping within an XDD time unit and the setting of frequency hopping within a pure time unit may be common or independent.

[0175] According to this embodiment, even if a channel / signal is configured by an upper layer within an XDD time unit in which the link direction is not indicated, the UE can appropriately control transmission / reception.

[0176] <Fifth embodiment> Within the DCI scheduling the PDSCH / PUSCH, a time domain resource assignment (TDRA) field may indicate the time resource within an XDD time unit, and a frequency domain resource assignment (FDRA) field may indicate the frequency resource within that XDD time unit.

[0177] In this disclosure, a pattern of link directions of multiple frequency-time units within an XDD time unit (a combination of link directions in the frequency domain) may be referred to as a frequency-time unit pattern.

[0178] The FDRA may indicate an absolute frequency position or a relative frequency position within a particular frequency-time unit, where the relative position may indicate a frequency (index) from the start position (e.g., the starting RB) in the frequency domain of the particular frequency-time unit.

[0179] The specific frequency-time unit may be a frequency-time unit within the XDD time unit indicated by the TDRA of the DCI that has the same frequency as the frequency-time unit indicated by the FDRA of the DCI.

[0180] The specific frequency-time unit may be a frequency-time unit that has the same frequency as the frequency-time unit containing the DCI within the XDD time units indicated by the TDRA of the DCI.

[0181] The UE behavior for DL ​​reception or UL transmission indicated by the FDRA for an XDD time unit may be in accordance with the second embodiment. For example, if the FDRA for a DL reception indicates resources within a DL frequency-time unit or a flexible frequency-time unit, the UE may receive the DL reception. For example, if the FDRA for a DL reception indicates resources that overlap with a UL frequency-time unit, the UE may cancel or rate-match the DL reception. For example, if the FDRA for a UL transmission indicates resources within a UL frequency-time unit or a flexible frequency-time unit, the UE may transmit the UL transmission. For example, if the FDRA for a UL transmission indicates resources that overlap with a DL frequency-time unit, the UE may cancel or rate-match the UL transmission.

[0182] If the channel scheduled by the DCI spans pure time units and XDD time units, the UE may apply the FDRA interpretation for pure time units to the XDD time units.

[0183] FDRA for PDSCH / PUSCH may follow either option 1 or 2 below.

[0184] Option 1 A common interpretation (e.g., formula / table / rule) of the FDRA (FDRA field) is used for any time unit with any frequency-time unit pattern. The interpretation of the FDRA field may be the same between pure time units and XDD time units.

[0185] The DCI (FDRA field) for scheduling multiple PDSCH / PUSCHs may follow either of the following options 1-1 and 1-2.

[0186] [Option 1-1] The DCI includes a separate FDRA field for each PDSCH / PUSCH.

[0187] [Option 1-2] The DCI includes one FDRA field for every PDSCH / PUSCH.

[0188] In the example of Option 1-2 in FIG. 12A , DCI in DL time unit #1 schedules PDSCH #1 in DL time unit #1, PDSCH #2 in XDD time unit #2, and PDSCH #3 in XDD time unit #3. The DCI includes one FDRA field. The UE interprets the FDRA field using a common interpretation for PDSCHs #1 through #3. As a result, the frequency resources of PDSCHs #1 through #3 are equal. The frequency resources of PDSCH #1 may be within the frequency-time unit containing the DCI (PDCCH). The frequency resources of PDSCHs #2 and #3 may be the same as those of PDSCH #1. PDSCH #3 may be canceled because it overlaps with the UL frequency-time unit.

[0189] Option 2 For multiple time units with different frequency-time unit patterns, different interpretations (interpretation methods, for example, formulas / tables / rules) of the FDRA (FDRA field) are used.

[0190] The interpretation for each frequency-time unit pattern may be set by the RRC.

[0191] For a PDSCH / PUSCH spanning multiple time units with different frequency-time unit patterns, the interpretation of FDRA for each time unit may follow either of options 2-1 and 2-2 below.

[0192] [Option 2-1] The interpretation of the FDRA for each time unit may follow the interpretation (common interpretation method) defined for a specific time unit among the overlapping time units (to the scheduled channel). The specific time unit may be the first or last time unit among the overlapping time units to the scheduled channel. The FDRA in the DCI scheduling a channel indicates the frequency resource of that channel in the specific time unit, and the same frequency resource may be used for that channel in other time units.

[0193] [Option 2-2] The individual interpretation method may be defined in the specification or may be configured by the RRC. The individual interpretation method may be an interpretation method for each time unit.

[0194] The DCI (FDRA field) for scheduling multiple PDSCH / PUSCHs may follow either of the following options 2-3 and 2-4.

[0195] [Option 2-3] The DCI includes a separate FDRA field for each PDSCH / PUSCH.

[0196] [Option 2-4] The DCI includes one FDRA field for every PDSCH / PUSCH.

[0197] The interpretation of FDRA for XDD time units (individual interpretation method) may follow at least one of the following rules: If the XDD time unit scheduled for DL ​​reception includes a DL frequency-time unit, the FDRA indicates the frequency resource within the DL frequency-time unit with the lowest or highest ID (or the DL frequency-time unit that includes the same frequency as the scheduling DCI) (specific frequency-time unit) within that XDD time unit. If the XDD time unit scheduled for UL transmission includes a UL frequency-time unit, the FDRA indicates the frequency resource within the UL frequency-time unit with the lowest or highest ID (or the UL frequency-time unit that includes the same frequency as the scheduling DCI) (specific frequency-time unit) within that XDD time unit. If the XDD time unit scheduled for DL ​​reception includes a DL frequency-time unit / flexible frequency-time unit, the FDRA indicates the frequency resource within the DL frequency-time unit / flexible frequency-time unit with the lowest or highest ID (or the DL frequency-time unit with the lowest or highest ID, or the DL frequency-time unit that includes the same frequency as the scheduling DCI) (specific frequency-time unit). If the XDD time unit scheduled for UL transmission includes a UL frequency-time unit / flexible frequency-time unit, the FDRA indicates the frequency resource within the UL frequency-time unit / flexible frequency-time unit with the lowest or highest ID (or the UL frequency-time unit with the lowest or highest ID, or the UL frequency-time unit that contains the same frequency as the scheduling DCI) (specific frequency-time unit).

[0198] In the example of options 2-4 in FIG. 12B, DCI in DL time unit #1 schedules PDSCH #1 in DL time unit #1, PDSCH #2 in XDD time unit #2, and PDSCH #3 in XDD time unit #3. The DCI includes one FDRA field. The UE interprets the FDRA field differently between PDSCHs #1 through #3. As a result, the frequency resources for PDSCHs #1 through #3 are different. The frequency resources for PDSCH #1 may be located within the frequency-time unit containing the DCI (PDCCH). The frequency resources for PDSCH #2 may have the same relative position within DL frequency-time units within XDD time unit #1 as the frequency resources for PDSCH #1. The frequency resources for PDSCH #3 may have the same relative position within DL frequency-time units within XDD time unit #3 as the frequency resources for PDSCH #1.

[0199] <Other embodiments> 《UE Capabilities / Upper Layer Parameters》 In each embodiment, a higher layer parameter (RRC information element) / UE capability corresponding to at least one function (feature) may be defined. The UE capability may indicate whether the function is supported.

[0200] A UE for which a higher layer parameter corresponding to the function is configured may perform the function. Alternatively, it may be specified that "a UE for which a higher layer parameter corresponding to the function is not configured does not perform the function (for example, applies the operation of Rel. 15 / 16)."

[0201] A UE that reports a UE capability indicating that it supports the function may perform the function. It may also be specified that "a UE that does not report a UE capability indicating that it supports the function shall not perform the function (e.g., apply the behavior of Rel. 15 / 16)."

[0202] If the UE reports a UE capability indicating that it supports the function and the corresponding upper layer parameter is configured, the UE may perform the function. It may also be specified that "if the UE does not report a UE capability indicating that it supports the function or if the corresponding upper layer parameter is not configured, the UE shall not perform the function (e.g., apply the behavior of Rel. 15 / 16)."

[0203] The UE capability may indicate whether the UE supports slot format indication with frequency domain granularity and time domain granularity.

[0204] The UE capability may indicate whether the UE supports explicit link direction indication for XDD time units.

[0205] The UE capability may indicate whether the UE supports implicit link direction indication for XDD time units.

[0206] The UE capability may indicate whether the UE supports dynamically scheduled / upper layer configured DL reception on XDD time units. The UE capability may indicate whether the UE supports dynamically scheduled / upper layer configured UL transmission on XDD time units.

[0207] The UE capability may indicate whether the UE supports frequency hopping of PUCCH / PUSCH in XDD time units.

[0208] The UE capabilities may indicate whether the UE supports different FDRA interpretations for different frequency-time unit patterns.

[0209] UE capability may be defined as the number of channels / RSs that can be simultaneously transmitted / received. UE capability may be defined as the number of channels / RSs that can be simultaneously transmitted / received within an operating band.

[0210] The above UE capabilities / upper layer parameters allow the UE to achieve the above functions while maintaining compatibility with existing specifications.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0254] The transceiver 120 may transmit one or more pieces of instruction information indicating a plurality of link directions, and the controller 110 may apply the plurality of link directions to a plurality of resources, including a plurality of consecutive time domain resources and a plurality of consecutive frequency domain resources, respectively.

[0255] The transceiver 120 may transmit indication information indicating that a time resource is applicable to the uplink and the downlink, and may transmit control information for the time resource. The controller 110 may control transmission or reception in the time resource based on the control information.

[0256] The transceiver 120 may transmit indication information indicating that multiple time resources are applicable to the uplink and downlink, and may transmit downlink control information for scheduling a channel across the multiple time resources. The controller 110 may determine a frequency resource for the channel in each of the multiple time resources based on the downlink control information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0274] The transceiver 220 may receive one or more indications indicating a plurality of link directions, and the controller 210 may apply the plurality of link directions to a plurality of resources, including a plurality of consecutive time domain resources and a plurality of consecutive frequency domain resources, respectively.

[0275] Each of the plurality of resources is a unit resource having a unit frequency and a unit time, and each of the plurality of link directions may indicate one from a group including: the unit resource is applicable to both uplink and downlink; the unit resource is applicable only to uplink; or the unit resource is applicable only to downlink.

[0276] The one or more pieces of instruction information may include first instruction information and second instruction information, wherein the first instruction information indicates, for each time resource having a unit time, one from a group including: that the time resource is applicable to both uplink and downlink, that the time resource is applicable only to uplink, or that the time resource is applicable only to downlink; and the second instruction information may indicate, for each unit resource having a unit frequency and a unit time, one from a group including: that the unit resource is applicable to both uplink and downlink, that the unit resource is applicable only to uplink, or that the unit resource is applicable only to downlink.

[0277] The one or more indication information may include first indication information and second indication information, and the first indication information may indicate, for each time resource having a unit time, one from a group including: that the time resource is applicable to both uplink and downlink, that the time resource is applicable only to uplink, or that the time resource is applicable only to downlink. The second indication information may indicate, for each unit resource having a unit frequency and a unit time, one from a group including: that the unit resource is applicable to both uplink and downlink, that the unit resource is applicable only to uplink, or that the unit resource is applicable only to downlink.

[0278] In the one or more pieces of instruction information, the multiple link directions may be arranged in order of the frequencies of the corresponding resources.

[0279] The transceiver 220 may receive indication information indicating that a time resource is applicable to the uplink and the downlink, and may receive control information for the time resource. The controller 210 may control transmission or reception in the time resource based on the control information.

[0280] The control information may indicate a link direction of the time resource.

[0281] The control information may indicate scheduling or triggering of transmission or reception within the time resource.

[0282] The control information may indicate frequency hopping within the time resource.

[0283] The transceiver 220 may receive indication information indicating that multiple time resources are applicable to the uplink and downlink, and may receive downlink control information for scheduling a channel across the multiple time resources. The controller 210 may determine a frequency resource for the channel in each of the multiple time resources based on the downlink control information.

[0284] The downlink control information may include a frequency domain resource allocation field, and the controller 210 may determine a plurality of frequency resources corresponding to the plurality of time resources, respectively, based on the frequency domain resource allocation field.

[0285] The controller 210 may determine the frequency resources using multiple interpretations of the single frequency domain resource allocation field.

[0286] The downlink control information may include a plurality of frequency domain resource allocation fields corresponding to the plurality of time resources, and the controller 210 may determine a plurality of frequency resources based on the plurality of frequency domain resource allocation fields.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a receiving unit for receiving indication information indicating that a time resource is applicable to an uplink and a downlink, and for receiving control information for the time resource; a control unit that controls uplink frequency hopping in the time resource based on the control information, The control unit controls a start position of the frequency hopping based on the instruction information.

2. receiving indication information indicating that time resources are applicable to uplink and downlink, and receiving control information for the time resources; controlling uplink frequency hopping in the time resource based on the control information; and controlling a start position of the frequency hopping based on the instruction information.

3. a transmitter configured to transmit indication information indicating that a time resource is applicable to an uplink and a downlink, and to transmit control information for the time resource; a control unit that controls uplink reception in the time resource that is frequency hopped based on the control information, A base station in which the start position of the frequency hopping is controlled based on the instruction information.

4. A system having a base station and a terminal, the base station includes a transmitter configured to transmit indication information indicating that time resources are applicable to uplink and downlink, and to transmit control information for the time resources; The terminal a receiving unit that receives the instruction information and the control information; a control unit that controls uplink frequency hopping in the time resource based on the control information, The control unit controls the start position of the frequency hopping based on the instruction information.

Images