Terminal

Abstract

A terminal according to the present invention repeatedly transmits an uplink data channel to a wireless base station. The terminal divides repeated transmission of an uplink data channel with reference to a boundary between a first time domain based on a sub-band full-duplex method, in which in a stipulated time based on time division duplexing, an uplink sub-band and a downlink sub-band are allocated in a non-overlapping manner in the frequency direction, and a second time domain based on a method other than the sub-band full-duplex method, when the uplink data channel spans the first time domain and the second time domain.

Description

Terminal

[0001] The present disclosure relates to a terminal that supports SBFD.

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, 3GPP Release 18 is considering an extension of the duplex method (Non-Patent Document 1). Specifically, a new duplex method called XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex, hereinafter referred to as SBFD) is proposed, which enables simultaneous use of the downlink (DL) and uplink (UL) within a carrier in a time division duplex (TDD) band.

[0004] Non-Patent Document 1 considers coexistence of SBFD symbols and non-SBFD symbols in one slot. In this case, the positions in the time direction and frequency direction where SBFD is applied may be set semi-statically, and dynamic setting may not be supported.

[0005] Furthermore, it is not necessary to assume that a terminal (User Equipment, UE) transmits a PUSCH (Physical Uplink Shared Channel) that spans both SBFD symbols and non-SBFD symbols within the same slot. In other words, a PUSCH that spans both SBFD symbols and non-SBFD symbols within the same slot is dropped.

[0006] 3GPP TR 38.858 V1.0.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Evolution of NR Duplex Operation (Release 18), 3GPP, September 2023

[0007] As described above, if a PUSCH that straddles an SBFD symbol and a non-SBFD symbol in the same slot is dropped, the operation of the UE transmitting the PUSCH is affected. For example, this can be the case when repetition of the PUSCH is set, when the PUSCH is in accordance with multi-PUSCH scheduling, or when the PUSCH is for UTO (Unused Transmission Occasion) - UCI (Uplink Control Information) Reporting.

[0008] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal that can transmit PUSCH normally even when SBFD symbols and non-SBFD symbols coexist in one slot.

[0009] One aspect of the present disclosure is a terminal (UE200) comprising: a transmitter (data transmitter / receiver 260) that repeatedly transmits an uplink data channel to a radio base station; and a control unit (control unit 270) that, when the uplink data channel straddles a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex, and a second time domain according to a method other than the subband full-duplex method, divides the repeated transmission of the uplink data channel based on the boundary between the first time domain and the second time domain.

[0010] One aspect of the present disclosure is a terminal comprising: a transmitter that repeatedly transmits an uplink data channel to a radio base station; and a controller that, when the uplink data channel spans a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex, and a second time domain according to a method other than the subband full-duplex method, determines whether to include a time domain including at least either the first time domain or the second time domain in a transmittable time domain of the uplink data channel.

[0011] One aspect of the present disclosure is a terminal including: a transmitter that transmits multiple uplink data channels indicated by downlink control information; and a controller that assumes that, when the uplink data channels span a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are assigned non-overlappingly in the frequency direction within a specified time based on time division duplex, and a second time domain according to a method other than the subband full-duplex method, assignment of automatic repeat request processing identifiers to the multiple uplink data channels is avoided.

[0012] One aspect of the present disclosure is a terminal including: a transmitter that transmits multiple uplink data channels to a radio base station; and a controller that, when a scheduling grant for the multiple uplink data channels spans a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex, assumes that the scheduling grant is invalid and assumes that allocation of automatic repeat request processing identifiers to the multiple uplink data channels is avoided.

[0013] One aspect of the present disclosure is a terminal including: a transmitter that transmits an uplink data channel to a radio base station; and a controller that assumes that uplink control information is not associated with the uplink data channel when the uplink data channel spans a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplexing, and a second time domain according to a method other than the subband full-duplex method.

[0014] FIG. 1 is a diagram illustrating an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram illustrating an example configuration of a radio frame, a subframe, and a slot used in the wireless communication system 10. FIG. 3 is a diagram illustrating an example configuration of TDD and SBFD. FIG. 4 is a functional block configuration diagram of a gNB 100 and a UE 200. FIG. 5 is a diagram illustrating an example of PUSCH repetition. FIG. 6 is a diagram illustrating an example of multi-PUSCH scheduling. FIG. 7 is a diagram illustrating an example configuration of multi-CG PUSCH. FIG. 8 is a diagram illustrating an example display of UTO-UCI by a CG PUSCH. FIG. 9 is a diagram illustrating an example division of PUSCH actual repetition according to Operation Example 1. FIG. 10 is a diagram illustrating an example of changes to the provisions of the 3GPP specifications according to Operation Example 1. FIG. 11 is a diagram illustrating an example of changes to the provisions of the 3GPP specifications according to Operation Example 2. FIG. 12 is a diagram illustrating an example of changes to the provisions of the 3GPP specifications according to Operation Example 2. FIG. 13 is a diagram illustrating an example of changes to the provisions of the 3GPP specifications according to Operation Example 2. FIG. 14 is a diagram illustrating an example of changes to the provisions of the 3GPP specifications according to Operation Example 3. Fig. 15 is a diagram showing an example of changes to the provisions of the 3GPP specifications according to operation example 4. Fig. 16 is a diagram showing an example of changes to the provisions of the 3GPP specifications according to operation example 5. Fig. 17 is a diagram showing an example of the hardware configuration of the gNB 100 and the UE 200. Fig. 18 is a diagram showing an example of the configuration of a vehicle 2001.

[0015] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0016] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE 200, User Equipment, UE). Note that the wireless communication system 10 may also be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0017] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1 .

[0018] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0019] The gNB 100 is a 5G-compliant radio base station that performs 5G-compliant radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional antenna beam (hereinafter referred to as beam BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and two NG-RAN nodes.

[0020] The type of DC may be Multi-RAT Dual Connectivity (MR-DC), which uses multiple radio access technologies, or NR-NR Dual Connectivity (NR-DC), which uses only NR. MR-DC may also be E-UTRA-NR Dual Connectivity (EN-DC), in which the eNB constitutes the master node (MN) and the gNB constitutes the secondary node (SN), or NR-E-UTRA Dual Connectivity (NE-DC), which is the reverse.

[0021] The gNB 100 can transmit multiple beams BM with different transmission directions (which may also be simply referred to as directions, or radiation directions, or coverages) in a space- and time-division manner. Note that the gNB 100 may transmit multiple beams BM simultaneously.

[0022] The wireless communication system 10 may also support multiple frequency ranges (FR). Specifically, the wireless communication system 10 may support the following frequency ranges:

[0023] ・FR1: 410 MHz to 7.125 GHz ・FR2-1: 24.25 GHz to 52.6 GHz FR1 may use a sub-carrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2-1 is a higher frequency than FR1 and may use a sub-carrier spacing (SCS) of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0024] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0025] Furthermore, the wireless communication system 10 also supports a frequency band higher than the FR2-1 frequency band. Specifically, the wireless communication system 10 supports a frequency band exceeding 52.6 GHz up to 71 GHz. Such a high frequency band may be referred to as FR2-2.

[0026] When using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.

[0027] Additionally, as mentioned above, in high frequency bands such as FR2-2, increased inter-carrier phase noise becomes an issue, which may necessitate the application of a larger (wider) SCS or a single-carrier waveform.

[0028] The larger the SCS, the shorter the symbol / cyclic prefix (CP) period and slot period (assuming a 14 symbol / slot configuration is maintained). Figure 2 shows an example of the configuration of radio frames, subframes, and slots used in the wireless communication system 10.

[0029] If the 14 symbols / slot configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period). The time direction may be called the time domain, symbol period, symbol length, or symbol time. The frequency direction may be called the frequency domain, resource block, subcarrier, or BWP (Bandwidth part).

[0030] The frequency resources may include component carriers, subcarriers, resource blocks (RBs), resource block groups (RBGs), bandwidth parts (BWPs), etc. The time resources may include symbols, slots, minislots, subframes, radio frames, discontinuous reception (DRX) periods, etc.

[0031] The number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Also, the number of slots per subframe may differ depending on the SCS.

[0032] The wireless communication system 10 may use an SSB (SS / PBCH Block) that is configured from a synchronization signal (SS) and a downlink physical broadcast channel (PBCH).

[0033] SSBs are transmitted periodically from the network mainly to allow UE 200 to detect cell IDs and reception timings when starting communication. In NR, SSBs are also used to measure the reception quality of each cell. The SSB transmission periodicity may be specified as 5, 10, 20, 40, 80, 160 milliseconds, etc. Note that the initial access UE 200 may assume a transmission period of 20 milliseconds.

[0034] Furthermore, multiple duplexing methods may be used in the wireless communication system 10. Specifically, time division duplexing (TDD) and frequency division duplexing (FDD) may be used. The duplexing method may be interpreted as a method for realizing simultaneous transmission and reception (duplex communication) of downlink (DL) and uplink (UL).

[0035] The gNB 100 and the UE 200 can perform wireless communication via multiple channels for different purposes. The channels include control channels and data channels. In particular, physical layer control channels may include a Physical Downlink Control Channel (PDCCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), and a PBCH.

[0036] The data channel includes a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), etc. Data may refer to data transmitted via a data channel.

[0037] The channel may be scheduled not only by dynamic scheduling but also by semi-fixed, semi-persistent, or semi-persistent scheduling (SPS). SPS may be interpreted as a concept intermediate between dynamic scheduling and static scheduling. Compared to dynamic scheduling, SPS can omit a scheduling grant, which may contribute to reducing the amount of signaling.

[0038] The wireless communication system 10 may use another duplexing scheme that enables simultaneous use of DL and UL, specifically, XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex). In the following, XDD / SBFD will be abbreviated to simply SBFD where appropriate.

[0039] Figure 3 shows an example of the configuration of TDD and SBFD. As shown in Figure 3, in TDD defined in 3GPP Releases 15 to 17, DL, UL, or F (flexible: can be set to DL (D) or UL (U)) can be set for each symbol and instructed to UE 200.

[0040] On the other hand, in SBFD (subband full duplex), the gNB100 can be configured as DL on certain frequency resources (e.g., subbands) in the time domain such as a symbol (SBFD slot / symbol), and as UL on other frequency resources, and instruct the UE200 accordingly.

[0041] SBFD allows simultaneous use of DL and UL within a carrier (CC) in the TDD band. Using the central portion of the frequency resources within the DL and UL carriers can avoid or mitigate potential cross-link interference (CLI) with adjacent carriers. SBFD may also be referred to as a type of full duplex, FDD full duplex, or sub-band (DL / UL) full duplex, as written SBFD.

[0042] In SBFD, frequency resources for DL ​​(DL band) and frequency resources for UL (UL band) are allocated in a non-overlapping manner to the same duplex band on the same time period.

[0043] Specifically, SBFD is a scheme in which DL bands and UL bands are allocated non-overlappingly in the frequency direction within a time domain (SBFD slot / symbol) based on time division duplex. The DL band may be interpreted as a DL subband, and the UL band may be interpreted as a UL subband. The time domain based on time division duplex to which SBFD is not applied may be called a non-SBFD slot / symbol, as opposed to an SBFD slot / symbol.

[0044] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the gNB 100 will be described. Fig. 4 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0045] As shown in Figure 4, the gNB100 includes a radio signal transceiver unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transceiver unit 260, and a control unit 270.

[0046] It should be noted that Fig. 4 shows only the main functional blocks relevant to the description of the embodiment, and that the gNB100 (UE200) has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the gNB100, and for the hardware configuration, please refer to Fig. 17.

[0047] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.

[0048] Furthermore, the radio signal transceiver 210 can transmit and receive radio signals according to SBFD, i.e., a scheme in which uplink subbands (UL subbands) and downlink subbands (DL subbands) are allocated non-overlappingly in the frequency direction within a specified time based on time division duplexing (TDD). Of course, the radio signal transceiver 210 may also support duplexing schemes such as TDD and FDD (Frequency Division Duplexing).

[0049] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0050] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0051] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0052] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0053] The control signal and reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Tracking Reference Signal (TRS).

[0054] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0055] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0056] The control signal and reference signal processor 240 may transmit capability information (UE capability information) of the UE 200 to the network. For example, the control signal and reference signal processor 240 may transmit UE capability information related to channel transmission and reception according to SBFD. The UE capability information will be described in detail later.

[0057] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).

[0058] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0059] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0060] Furthermore, the data transmitter / receiver 260 transmits an uplink data channel and receives a downlink data channel. Specifically, the data transmitter / receiver 260 transmits a PUSCH to the gNB 100 and receives a PDSCH from the gNB 100. In this embodiment, the data transmitter / receiver 260 may constitute a transmitter and a receiver.

[0061] The data transmitter / receiver 260 can transmit a PUSCH (uplink data channel) to the gNB 100 (radio base station). The data transmitter / receiver 260 may repeatedly transmit the PUSCH to the gNB 100. Here, repeated transmission may mean repetition.

[0062] For example, Repetition may be defined as Repetition type A and Repetition type B. Repetition type A may be interpreted as a form in which a PUSCH allocated within a slot is repeatedly transmitted. In other words, a PUSCH is 14 symbols or less and may not be allocated across multiple slots (adjacent slots). In 3GPP Release 17, the maximum number of repetitions in PUSCH Repetition type A has been extended from 16 to 32.

[0063] On the other hand, Repetition type B may be interpreted as repeated transmission of PUSCH allocated to consecutive symbols, which is 14 symbols or less, regardless of slot boundaries.

[0064] The actual repetition is the repetition finally transmitted, and the nominal repetition may be interpreted as the repetition notified / assigned to the UE by the gNB. For example, the actual repetition and the nominal repetition may change depending on the following factors.

[0065] (i) If no nominal repetition is placed in the UL symbol, the nominal repetition may be omitted.

[0066] (ii) If a nominal repetition is placed on a slot boundary, the nominal repetition may be split at the slot boundary and turned into two actual repetitions.

[0067] Furthermore, the data transmitter / receiver 260 may transmit multiple PUSCHs to the radio base station. For example, the data transmitter / receiver 260 may transmit multiple PUSCHs indicated by downlink control information (DCI). That is, multiple PUSCHs may be indicated by a single DCI.

[0068] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 can execute control related to SBFD.

[0069] Specifically, the control unit 270 can perform various controls depending on whether the PUSCH spans a first time domain according to a subband full duplex method (SBFD) in which UL subbands and DL subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex (TDD), and a second time domain according to a method other than the subband full duplex method.

[0070] Here, the specified time may refer to a time domain based on TDD including the SBFD slots or SBFD symbols shown in FIG. 3. The specified time may also be expressed in units other than slots or symbols (e.g., minislots). The first time domain may be interpreted as SBFD slots or SBFD symbols. The second time domain may be interpreted as slots or symbols to which TDD is applied without SBFD being applied.

[0071] When the PUSCH straddles the first time domain and the second time domain, the control unit 270 may divide the repeated transmission of the PUSCH based on the boundary between the first time domain and the second time domain. Specifically, when PUSCH Repetition type B is set and the nominal repetition or the actual repetition straddles the first time domain and the second time domain, that is, when the nominal repetition or the actual repetition is mapped to both the SBFD symbol and the non-SBFD symbol, the control unit 270 may divide the repetition into multiple actual repetitions near the boundary between the SBFD symbol and the non-SBFD symbol.

[0072] When the PUSCH straddles the first time domain and the second time domain, the control unit 270 may determine whether to include a time domain including at least either the first time domain or the second time domain in the time domain in which the PUSCH can be transmitted. Specifically, when the PUSCH straddles the first time domain and the second time domain, the control unit 270 may count slots allocable for PUSCH Repetition type A or TB processing over multi-slot PUSCH (TBoMS) as the number of N*K slots for PUSCH transmission, where K may be interpreted as a repetition factor (number of repeated transmissions).

[0073] TBoMS may be interpreted as processing a transport block (TB) via a PUSCH allocated to multiple slots. While the above-mentioned Repetition method repeatedly transmits a TB generated for a PUSCH in a single slot or 14 symbols or less over multiple slots (N slots), TBoMS generates a TB for a PUSCH spanning multiple slots (M slots). It is also possible to transmit a combination of TBoMS and repetition, where a TB generated and processed based on TBoMS is transmitted over M slots and then repeated N times. However, M×N is limited to 32 or less.

[0074] When a PUSCH spans the first time domain and the second time domain, the control unit 270 may assume that allocation of a process identifier for hybrid automatic repeat request (HARQ), specifically, an HARQ Process ID (HP ID), to multiple PUSCHs is avoided. Note that the HP ID may be read as an HARQ Process Number (HPN).

[0075] When a scheduling grant for multiple PUSCHs, specifically, a multi-PUSCH CG (configured grant), spans the first time domain and the second time domain, the control unit 270 may assume that the scheduling grant is invalid and may assume that allocation of HARQ HP IDs to the multiple PUSCHs is avoided.

[0076] When a PUSCH spans the first time domain and the second time domain, the control unit 270 may assume that no uplink control information (UCI) is associated with the PUSCH. Specifically, with regard to UTO-UCI Reporting, the control unit 270 may prevent information (bits) indicating UTO-UCI from being mapped to a CG PUSCH that spans the first time domain and the second time domain.

[0077] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to transmission and reception of the PUSCH when SBFD is applied.

[0078] (3.1) Definition of Terms For clarity, the terms used in this embodiment are defined as follows:

[0079] SBFD operation cell: When the time and frequency locations of the SBFD subbands are configured in a serving cell, the cell may be called an SBFD operation cell.

[0080] Half-duplex CA serving cell: A set of serving cells for which directionalCollisionHandling-r16='enabled' is provided to the UE among the configured serving cells, if the UE indicates support for half-duplex TDD-CA-SameSCS-r16 capability. Quasi-SFI (Slot Format Indication) D (or Quasi-Static D) symbol: A symbol indicated as DL by TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated. Quasi-SFI U (or Quasi-Static U) symbol: A symbol indicated as UL by TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated. Quasi-SFI F (or Quasi-Static F) symbol: A symbol indicated as flexible by TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated. SBFD DL symbol: A symbol indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and for which the SBFD UL subband is configured. SBFD flexible symbol: A symbol indicated as flexible by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and for which the SBFD UL subband is set. Note that information elements (IEs) such as the above-mentioned half-duplex TDD-CA-SameSCS-r16 are specified in 3GPP TS38.331 and other standards.

[0081] (3.2) Assumptions Fig. 5 shows an example of PUSCH Repetition. Specifically, Fig. 5 shows examples of PUSCH Repetition type A and Repetition type B. As shown in Fig. 5, PUSCH Repetition type A is slot-based PUSCH repetition transmission.

[0082] PUSCH Repetition type B is a repeated transmission of PUSCH allocated to consecutive symbols regardless of slot boundaries. The nominal repetition may be divided into multiple actual repetitions near DL / SSB symbols and slot boundaries. Each actual repetition may include multiple UL / flexible symbols within a slot.

[0083] Furthermore, regarding counting the number of PUSCH slots, if K>1, the UE may determine the PUSCH transmission slots for PUSCH Repetition type A scheduled by DCI format 0_1 ​​or DCI format 0_2 based on the tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, and the Time Domain Resource Allocation (TDRA) field value of DCI format 0_1 ​​or DCI format 0_2. In other words, the UE may determine the number of N*K slots to be used for PUSCH repetition.

[0084] 6 shows an example of multi-PUSCH scheduling. In multi-PUSCH scheduling, DCI format 0_1 ​​may be used. SCSs of 120, 480, and 960 kHz may be supported. The maximum number of PUSCHs that can be scheduled by one DCI is eight.

[0085] For TDRA, if a PUSCH collides with a semi-static UL symbol or SSB symbol, that PUSCH may be canceled, but not all PUSCHs may be canceled. HPN may be skipped for invalid PUSCHs (i.e., collisions between PUSCH and semi-static DL or SSB symbols TO).

[0086] Fig. 7 shows an example of the configuration of a multi-CG PUSCH. Specifically, Fig. 7 shows an example in which a single CG PUSCH (opportunity) is allocated in one period, and an example in which multiple CG PUSCHs (opportunities) are allocated in a CG period.

[0087] In this case, the HP ID may be incremented by "1" for each subsequent valid PUSCH opportunity (ie, no interfering DL / SSB symbols) during that period.

[0088] Figure 8 shows an example of UTO-UCI display using CG PUSCH. As shown in Figure 8, bitmap (0011) may indicate "used" or "unused." UTO-UCI allows a UE to report unused CG opportunities to a gNB. Based on the report, the gNB can use unused CG resources for other UEs, thereby improving resource utilization efficiency.

[0089] A UTO-UCI report may be configured for each CG. The same physical priority as that of the CG PUSCH may be configured for the UTO-UCI. When HARQ-ACK with the same priority is multiplexed with the CG PUSCH, the UTO-UCI is coded together with the HARQ-ACK. The HARQ-ACK bits are coded together after the UTO-UCI bits. A CG PUSCH containing both CG-UCI and UTO-UCI may not be supported.

[0090] (3.3) Issues As described above, the wireless communication system 10 supports semi-static configuration of SBFD time and frequency locations. However, dynamic SBFD operation does not have to be supported. A PUSCH (opportunity) that straddles an SBFD symbol and a non-SBFD symbol within a slot does not have to be transmitted. However, if appropriate, SBFD slots and non-SBFD slots may be used instead of SBFD symbols and non-SBFD symbols.

[0091] The dropping of PDSCH due to overlap between SBFD symbols and non-SBFD symbols in a slot is a novel behavior, which may have the following effects on UE operation:

[0092] (Problem 1): It is unclear how the UE operates when PUSCH Repetition type B PUSCH Repetition type B overlaps with an SBFD symbol and a non-SBFD symbol. For example, it is unclear whether the repetition should be divided into multiple actual repetitions or whether it should be deleted.

[0093] (Problem 2): When a PUSCH in a PUSCH Repetition type A or TBoMS slot is dropped because it overlaps with an SBFD symbol and a non-SBFD symbol, it is not clear whether the slot is counted as a Repetition slot or a TBoMS slot.

[0094] (Problem 3): Multi-PUSCH Scheduling and Multi-CG PUSCH When multiple scheduled PUSCHs or multiple CG PUSCHs in one CG period overlap with SBFD symbols and non-SBFD symbols in a slot, it is unclear whether to skip determining the HP ID of the PUSCH.

[0095] (Problem 4): UTO-UCI reporting in CG PUSCH When a CG PUSCH overlaps with an SBFD symbol and a non-SBFD symbol in a slot, it is unclear whether the UTO-UCI reported before the CG PUSCH contains an indication bit for that CG PUSCH.

[0096] (3.4) Overview of Operations The following operations may be performed for transmitting and receiving PUSCH when SBFD is applied.

[0097] (Operation Example 1): Partitioning of PUSCH Repetition type B When the nominal repetition or the actual repetition (which may be obtained according to conventional 3GPP specifications) is mapped to both SBFD symbols and non-SBFD symbols, one of the following options may be applied.

[0098] (Option 1): The nominal repetition / actual repetition may be divided into multiple actual repetitions near the boundary between SBFD symbols and non-SBFD symbols.

[0099] - (Option 2): Nominal repetition / actual repetition is not sent.

[0100] (Operation Example 2): Counting the number of slots in PUSCH Repetition type A or a single TBoMS If the PUSCH time domain resource in a slot overlaps both SBFD symbols and non-SBFD symbols, one of the following options may be applied.

[0101] (Option 1): Count the slot as N*K slots.

[0102] (Option 2): Do not count the slot as part of the N*K slots.

[0103] (Operation Example 3): Scheduling of multiple PUSCHs using DCI. (Option 1): Operates according to conventional 3GPP specifications.

[0104] (Option 2): No HP ID is assigned to a PUSCH that overlaps an SBFD symbol and a non-SBFD symbol.

[0105] (Operation Example 4): When the Configured Grant (CG) of a multi-CG PUSCH PUSCH overlaps an SBFD symbol and a non-SBFD symbol at the same time, one of the following options may be applied.

[0106] ・(Option 1): Operates according to conventional 3GPP specifications.

[0107] (Option 2): Invalid PUSCH CG, does not determine HP ID for this CG PUSCH.

[0108] (Operation Example 5): UTO-UCI Reporting (Option 1): Operate according to the conventional 3GPP specifications, i.e., UTO-UCI bits can be mapped to CG PUSCH overlapping SBFD and non-SBFD symbols.

[0109] (Option 2): UTO-UCI bits are not mapped to CG PUSCHs that overlap SBFD and non-SBFD symbols.

[0110] (3.5) Operational Examples (3.5.1) Operational Example 1 In this operational example, for division of PUSCH Repetition type B, either option 1 or 2 may be applied as described above.

[0111] In option 1, the nominal repetition / actual repetition between SBFD symbols and non-SBFD symbols is segmented into multiple actual repetitions, and each actual repetition may be mapped to only SBFD symbols or only non-SBFD symbols.

[0112] 9 shows an example of division of the PUSCH actual repetition according to operation example 1. Specifically, FIG. 9 shows an example of division of the PUSCH actual repetition according to option 1.

[0113] Fig. 10 shows an example of changes to the provisions of the 3GPP specifications related to Operation Example 1. Specifically, Fig. 10 shows an example of changes to the provisions of 3GPP TS38.214 Chapter 6.1.2.1 (partial excerpt) corresponding to Option 1. The underlined parts indicate the changes.

[0114] (3.5.2) Operation Example 2 In this operation example, either option 1 or 2 may be applied as described above with respect to counting the number of slots in PUSCH Repetition type A or a single TBoMS.

[0115] Option 1 reuses existing specifications, which reduces the number of PUSCH transmission slots and is not suitable for improving the reliability and coverage of the PUSCH.

[0116] 11 to 13 show examples of changes to the provisions of the 3GPP specifications relating to Operation Example 2. Specifically, Figures 11 to 13 show examples of changes to the provisions of 3GPP TS38.214 Chapter 6.1.2.1 (partial excerpt) corresponding to Option 2. The underlined parts indicate the changes.

[0117] (3.5.3) Operation Example 3 In this operation example, either option 1 or 2 may be applied to scheduling of multiple PUSCHs by DCI, as described above.

[0118] In the case of option 1, an HP ID may be assigned to the dropped PUSCH because it overlaps with an SBFD symbol and a non-SBFD symbol. There is no need to assign an HP ID to the PUSCH, which may be inefficient in terms of HP ID resource usage.

[0119] For option 2, the HP ID allocation may be optimized: the HP ID indicated by the DCI may be applied to the first PUSCH that does not overlap with non-SBFD quasi-static DL symbols or SSB symbols and does not overlap with both SBFD and non-SBFD symbols simultaneously.

[0120] If at least one of the symbols indicated in the index row of the used resource allocation table in a slot overlaps with a non-SBFD quasi-static DL symbol or SSB symbol, or overlaps with both SBFD and non-SBFD symbols simultaneously, the HP ID may not be incremented for a PUSCH that is not received.

[0121] Fig. 14 shows an example of changes to the provisions of the 3GPP specifications according to Operation Example 3. Specifically, Fig. 14 shows an example of changes to the provisions of 3GPP TS38.214 Chapter 6.1 (partial excerpt) corresponding to Option 2. The underlined parts indicate the changes.

[0122] (3.5.4) Operation Example 4 In this operation example, either option 1 or 2 may be applied to the multi-CG PUSCH as described above.

[0123] In the case of option 1, an HP ID may be assigned to the dropped PUSCH because it overlaps with an SBFD symbol and a non-SBFD symbol. There is no need to assign an HP ID to the PUSCH, which may be inefficient in terms of HP ID resource usage.

[0124] Fig. 15 shows an example of changes to the provisions of the 3GPP specifications related to operation example 4. Specifically, Fig. 15 shows an example of changes to the provisions of 3GPP TS38.214 Chapter 6.1.2.3 (partial excerpt) corresponding to option 2. The underlined parts indicate the changes.

[0125] (3.5.5) Operational Example 5 In this operational example, either option 1 or 2 may be applied to the UTO-UCI report as described above.

[0126] In the case of option 1, there is no need to report whether the CG PUSCH is "used" or "unused," and one bit of information is wasted.

[0127] Fig. 16 shows an example of changes to the provisions of the 3GPP specifications related to operation example 5. Specifically, Fig. 16 shows an example of changes to the provisions of 3GPP TS38.214 Chapter 6.1.2.3 (partial excerpt) corresponding to option 2. The underlined parts indicate the changes.

[0128] (3.6) UE Capabilities Regarding transmission and reception of various channels when SBFD is applied, the following UE capabilities and signaling for reporting (including RRC configuration) may be defined. The UE capabilities and signaling may be defined for each UE, each frequency range (FR), or each frequency channel (FC).

[0129] Whether to support scheduling / setting related to PDSCH reception that overlaps SBFD symbols and non-SBFD symbols within a slot Whether to support skipping of HP IDs of PDSCHs that overlap SBFD symbols and non-SBFD symbols within a slot when multiple PDSCHs are scheduled by a single DCI Whether to support skipping of HARQ feedback of PDSCHs that overlap SBFD symbols and non-SBFD symbols within a slot Whether to support excluding SPS PDSCHs that overlap SBFD symbols and non-SBFD symbols within a slot before performing the SPS collision handling procedure Whether to support splitting nominal / actual PUSCH Repetitions that overlap SBFD symbols and non-SBFD symbols within a slot into multiple actual PUSCH Repetitions near the boundary between SBFD symbols and non-SBFD symbols for PUSCH Repetition type A or TBoMS (TB processing over multi-slot Whether to support skipping the HP ID of a PUSCH opportunity that overlaps with SBFD symbols and non-SBFD symbols in a slot when multiple PDSCHs are scheduled by a single DCI. Whether to support skipping the HP ID of a CG PUSCH opportunity that overlaps with SBFD symbols and non-SBFD symbols in a slot when multiple PUSCH opportunities are configured in one CG (Configure Grant) period. Whether to support skipping the HP ID of a CG PUSCH opportunity that overlaps with SBFD symbols and non-SBFD symbols in a slot when reporting UTO (Unused Transmission Occasion) - UCI (Uplink Control Information).Whether to support skipping of PUSCH unused information notification Whether to support not counting slots in which PUCCH symbols overlap with SBFD symbols and non-SBFD symbols in the number of PUCCH repetition slots Whether to support delaying SPS HARQ-ACK when SPS HARQ-ACK overlaps with SBFD symbols and non-SBFD symbols in the first reporting slot / subslot Whether to support dropping PUSCH / PUCCHs that overlap with SBFD symbols and non-SBFD symbols in a slot before the UL channel multiplexing / prioritization procedure Whether to support performing the UL channel multiplexing / prioritization procedure before dropping PUSCH / PUCCHs that overlap with SBFD symbols and non-SBFD symbols in a slot Note that a UE may support only some or all of the above-mentioned UE capabilities.

[0130] (4) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

[0131] For example, in the above-described embodiment, a specific physical layer channel has been described as the target, but other physical layer channels may also be targeted. Furthermore, in the above-described embodiment, the term "subband" is used, but the subband may simply be called a "band," or may be called by other similar terms such as an auxiliary band or a spare band. Furthermore, XDD / SBFD may be a provisional name, or may be called by other similar terms as described above.

[0132] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0133] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

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

[0135] The block diagram ( FIG. 4 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or 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 (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0136] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0137] Furthermore, the above-described gNB 100 and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 17 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 17, the devices may be configured as a computer 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.

[0138] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0139] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0140] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0141] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0142] 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. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0143] 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 ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0144] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0145] 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 called, for example, a network device, a network controller, a network card, or a communication module.

[0146] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0147] The input device 1005 is an input device (e.g., 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 (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0148] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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.

[0149] Furthermore, the device 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 by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0150] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0151] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0152] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0153] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

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

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

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

[0157] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

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

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

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

[0161] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0162] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0163] 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 an index.

[0164] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., 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.

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

[0166] A base station can accommodate one or more (e.g., three) cells (also called sectors). 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 services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0167] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0168] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0170] A mobile station may also be referred to by those skilled in the art 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.

[0171] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. 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.

[0172] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. 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 (or sidelink).

[0173] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0174] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further 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.

[0175] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

[0177] A slot may include multiple minislots. Each minislot may consist of one or more 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 (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0178] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0179] For example, one subframe may be referred to as a transmission time interval (TTI), 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 the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 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.

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

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

[0182] In addition, 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, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

[0185] 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 be determined based on numerology.

[0186] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

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

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

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

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

[0191] 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."

[0192] The above-described structures of the radio frame, subframe, slot, minislot, and symbol 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, and other configurations may be changed in various ways.

[0193] 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." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0194] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

[0195] 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."

[0196] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0197] 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 therein or that the first element must precede the second element in some way.

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

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

[0200] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0201] 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."

[0202] 18 shows an example of the configuration of a vehicle 2001. As shown in Fig. 18, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0203] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0204] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0205] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0206] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0207] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0208] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0209] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0210] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0211] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transceiver 220 Amplifier 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transceiver 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a transmitter that repeatedly transmits an uplink data channel to a radio base station; and a controller that, when the uplink data channel straddles a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex, divides the repeated transmission of the uplink data channel based on the boundary between the first time domain and the second time domain.

2. A terminal comprising: a transmitting unit that repeatedly transmits an uplink data channel to a radio base station; and a control unit that, when the uplink data channel spans a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex, and a second time domain according to a method other than the subband full-duplex method, determines whether or not to include a time domain including at least either the first time domain or the second time domain in the transmittable time domain of the uplink data channel.

3. A terminal comprising: a transmitter that transmits multiple uplink data channels indicated by downlink control information; and a controller that assumes that allocation of automatic repeat request processing identifiers to the multiple uplink data channels is avoided when the uplink data channels span a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplexing, and a second time domain according to a method other than the subband full-duplex method.

4. A terminal comprising: a transmitter that transmits multiple uplink data channels to a radio base station; and a controller that, when a scheduling grant for the multiple uplink data channels straddles a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex, assumes that the scheduling grant is invalid and assumes that allocation of automatic repeat request processing identifiers to the multiple uplink data channels is avoided.

5. A terminal comprising: a transmitter that transmits an uplink data channel to a radio base station; and a controller that, when the uplink data channel spans a first time domain according to a subband full-duplex method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex, assumes that uplink control information is not associated with the uplink data channel.

Images