Terminal and wireless communication method

Abstract

This terminal transmits and receives a radio signal in accordance with a sub-band full-duplex communication system in which an uplink sub-band and a downlink sub-band are allocated in a non-overlapping manner in the frequency direction within a prescribed time with reference to time division duplexing. The terminal assumes, according to an information element of a radio resource control layer, that the frequency positions of the uplink sub-band and the downlink sub-band are set for each uplink and downlink sub-carrier interval.

Description

Terminal and wireless communication method

[0001] The present disclosure relates to a terminal and a wireless communication method 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 19 is studying an extension of the duplex method (Non-Patent Document 1). Specifically, regarding Sub-Band non-overlapping Full Duplex (SBFD), which is a duplex method that enables simultaneous use of a downlink (DL) and an uplink (UL) within a carrier of a time division duplex (TDD) band, it has been agreed to study a method of indicating to a terminal (User Equipment, UE) the positions in the time direction (time positions) of the UL sub-band and the DL sub-band (which may also be called SBFD sub-band).

[0004] On the other hand, it has been agreed that the position in the frequency direction (frequency position) of the SBFD subband is set for each subcarrier spacing (SCS) in accordance with the SCS-SpecificCarrierList, which is a type of information element (IE) of the radio resource control layer (RRC) (Non-Patent Document 2).

[0005] "New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)", RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 2023 "Draft Report of 3GPP TSG RAN WG1 #116b v0.3.0", 3GPP, April 2024

[0006] According to the existing 3GPP specifications, the SCS-SpecificCarrierList is applied to both DL and UL. However, in the case of SBFD subbands, it is unclear whether the SCS-SpecificCarrierList is applied to either DL or UL, or both DL and UL.

[0007] For this reason, in the case of SBFD, even if the UE receives an SCS-SpecificCarrierList instruction from the network, there is a risk that the UE will not be able to perform appropriate configuration.

[0008] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal and a wireless communication method that can set the frequency position of an appropriate SBFD subband while using an SCS-SpecificCarrierList.

[0009] One aspect of the present disclosure is a terminal (UE200) including: a communication unit (radio signal transceiver unit 210) that transmits and receives radio signals according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time period based on time division duplex; and a control unit (control unit 270) that assumes that the frequency positions of the uplink subbands and the downlink subbands are set for each uplink and downlink subcarrier interval using information elements of a radio resource control layer.

[0010] One aspect of the present disclosure is a terminal (UE200) including: a communication unit (radio signal transceiver unit 210) that transmits and receives radio signals according to a subband full-duplex communication method in which uplink subbands or downlink subbands are allocated non-overlapping in the frequency direction within a specified time period based on time division duplex; and a control unit (control unit 270) that assumes that the frequency position of the uplink subband and the number of resource blocks of a guard band provided between the uplink subband and the downlink subband are set for each subcarrier interval of the uplink and downlink by information elements of a radio resource control layer.

[0011] 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 XDD / 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 configuration (Example 1-1a) of RRC layer information elements according to Operation Example 1. FIG. 6 is a diagram illustrating an example configuration (Example 1-1b) of RRC layer information elements according to Operation Example 1. FIG. 7 is a diagram illustrating an example determination of PRBs according to Operation Example 1 (Option 1-1b). FIG. 8 is a diagram illustrating an example configuration (Example 2-1a) of RRC layer information elements according to Operation Example 2. FIG. 9 is a diagram illustrating an example configuration (Example 2-1b) of RRC layer information elements according to Operation Example 2. FIG. 10 is a diagram illustrating an example determination of DL subbands according to Operation Example 2 (Option 2-1). FIG. 11 is a diagram illustrating an example determination of DL subbands according to Operation Example 2 (Option 2-2). Fig. 12 is a diagram illustrating an example of the hardware configuration of the gNB 100 and the UE 200. Fig. 13 is a diagram illustrating an example of the configuration of a vehicle 2001.

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

[0013] (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.

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

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

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

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

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

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

[0020] ・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.

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

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

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

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

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

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

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

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

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

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

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

[0032] Furthermore, the wireless communication system 10 may use another duplexing method that enables simultaneous use of DL and UL, specifically, XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex).

[0033] Figure 3 shows an example of the configuration of TDD and XDD / 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 or UL) can be set for each symbol and instructed to UE 200.

[0034] On the other hand, in XDD / SBFD, gNB100 can configure specific frequency resources (e.g., subbands) as DL and other frequency resources as UL at a specified time T, such as a symbol, and instruct UE200 accordingly.

[0035] XDD / 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. XDD / SBFD may also be referred to as a type of full duplex, or FDD full duplex, or as sub-band (DL / UL) full duplex, as abbreviated as SBFD.

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

[0037] Specifically, XDD / SBFD is a scheme in which DL bands and UL bands are allocated non-overlappingly in the frequency direction within a specified time T 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. In the following, XDD / SBFD will be abbreviated simply as SBFD where appropriate.

[0038] (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 UE 200 will be described. Fig. 4 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0039] As shown in FIG. 4 , the UE 200 includes a radio signal transmitting / receiving 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 transmitting / receiving unit 260, and a control unit 270.

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

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

[0042] Furthermore, the radio signal transceiver 210 can transmit and receive radio signals in accordance with SBFD, i.e., subband full-duplex (SBFD) 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. In this embodiment, the radio signal transceiver 210 constitutes a communication unit. Of course, the radio signal transceiver 210 may also support duplexing methods such as TDD and FDD (frequency division duplexing). The amplifier 220 is constituted by a PA (power amplifier) / LNA (low noise amplifier), etc. The amplifier 220 amplifies the signal output from the modem 230 to a predetermined power level. The amplifier 220 also amplifies the RF signal output from the radio signal transceiver 210.

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

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

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

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

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

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

[0049] The channels include a control channel and a data channel, which may include a PDCCH, a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0050] Furthermore, the data channel includes a PDSCH and a PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via a data channel.

[0051] The control signal and reference signal processor 240 may transmit capability information of the UE 200 to the network. In particular, in this embodiment, the control signal and reference signal processor 240 may transmit capability information related to SBFD. The capability information may include, for example, support for cell-specific configuration related to the locations in the frequency direction of the UL subbands and DL subbands (which may be referred to as frequency locations).

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

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

[0054] 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 the Medium Access Control layer (MAC), the Radio Link Control layer (RLC), and the 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).

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

[0056] Specifically, the control unit 270 can execute control related to cell-specific setting of the frequency location of the SBFD subband. Note that the frequency location may also be referred to as a frequency domain location.

[0057] More specifically, the control unit 270 performs cell-specific configuration of the frequency locations of the UL subbands and DL subbands. Regarding the cell-specific configuration of the SBFD subbands, specifically, the frequency locations of the UL subbands and DL subbands, the following two cases may be assumed.

[0058] (Case 1): The frequency locations of the UL subband and DL subband are explicitly set.

[0059] (Case 2): The frequency location of the UL subband and the number of resource blocks (RBs) allocated to the guard band (only when the guard band is set) are explicitly set.

[0060] In Case 1, the control unit 270 may assume that the frequency locations of the UL subbands and the DL subbands are set for each UL and DL subcarrier spacing (SCS). Specifically, the control unit 270 may assume that the frequency locations of the UL subbands are set for each UL SCS, and that the frequency locations of the DL subbands are set for each DL SCS, by an information element (IE) of the radio resource control layer (RRC). The RRC IE is not particularly limited, but in this embodiment, an SCS-SpecificCarrierList may be used, which indicates the configuration of not only the SBFD subbands but also the SCSs of the UL and DL carriers. The SCS-SpecificCarrierList may be included in FrequencyInfoDL-SIB or FrequencyInfoDL, or FrequencyInfoUL-SIB or FrequencyInfoUL, and FrequencyInfoDL-SIB, FrequencyInfoDL, FrequencyInfoUL-SIB, or FrequencyInfoUL may be interpreted as the information element.

[0061] The SCS-SpecificCarrierList may be included in, for example, a system information block (SIB) transmitted from the network. The SCS-SpecificCarrierList may include settings related to the SCS of a specific carrier (SCS-SpecificCarrier). For example, the SCS-SpecificCarrierList may include an offset amount, an SCS value, and a carrier bandwidth for a specific carrier.

[0062] In this embodiment, the SCS-SpecificCarrier may include settings for each SBFD subband (UL subband or DL ​​subband).

[0063] Furthermore, in Case 2, the control unit 270 may assume that the frequency location of the UL subband and the number of resource blocks (RBs) of the guard band provided between the UL subband and the DL subband are configured for each of the UL and DL SCSs by an (RRC) information element (IE). As in Case 1, the RRC IE may use an SCS-SpecificCarrierList. That is, the control unit 270 may assume that the frequency location is configured by an SCS-SpecificCarrierList (or SCS-SpecificCarrier), which is an information element that instructs the configuration of an SCS.

[0064] In addition, in Case 1, the control unit 270 may assume that the frequency positions of the UL subband and DL subband are set for each SCS in the DL SCS-SpecificCarrierList, or may assume that the frequency positions of the UL subband and DL subband are set for each SCS in the UL SCS-SpecificCarrierList.

[0065] In addition, in Case 2, control unit 270 may assume that the frequency position of the UL subband and the number of RBs of the guard band provided between the UL subband and the DL subband are set for each DL SCS, or that the frequency position of the UL subband and the number of RBs of the guard band provided between the UL subband and the DL subband are set for each UL SCS. Control unit 270 may also assume that RBs of the guard band are set for each DL SCS.

[0066] The control unit 270 may assume that the intersection of the UL (active) bandwidth portion (BWP) and the UL sub-band is set by the above-mentioned information element (IE). Note that the control unit 270 may assume that the intersection of the DL (active) BWP and the DL sub-band is set by the above-mentioned information element (IE).

[0067] (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 communication using frequency domain locations of the UL subband and DL subband to which SBFD is applied.

[0068] (3.1) Assumptions and Issues In 3GPP, it is agreed that the frequency location of the SBFD subband is configured for each SCS according to the SCS-SpecificCarrierList, which is a type of RRC IE. In the existing 3GPP specifications, the SCS-SpecificCarrierList can be configured for both DL and UL. However, it is not clear whether the frequency location of the SBFD subband applies to DL, UL, or both DL and UL for each SCS configuration in the SCS-SpecificCarrierList.

[0069] A solution is needed that can set the frequency locations of DL and / or UL subbands for DL ​​SCS and / or UL SCS and determine the physical resource blocks (PRBs) available for DL / UL use.

[0070] (3.2) Overview of Operation The following cases and options are possible for the operation regarding the cell-specific setting of the frequency location of the SBFD subband.

[0071] Operation example 1 (Case 1): The frequency positions of the UL subband and DL subband are explicitly set.

[0072] (Option 1-1): The frequency locations of the UL subbands and DL subbands are configured for each SCS configuration in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0073] (Option 1-2): The frequency locations of the UL subbands and DL subbands are configured for each SCS configuration in the SCS-SpecificCarrierList of the UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0074] (Options 1-3): The frequency locations of the UL subbands are configured in each SCS-SpecificCarrier for each SCS configuration in the UL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). The frequency locations of the DL subbands are configured for each SCS configuration in the SCS-SpecificCarrierList for the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0075] - (Options 1-4): The frequency locations of the UL subbands and DL subbands are set for each SCS setting in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL) and for each SCS setting in the SCS-SpecificCarrierList of the UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0076] Operation example 2 (Case 2): The frequency position of the UL subband and the number of RBs for the guard band, if any, are explicitly set.

[0077] (Option 2-1): The frequency location of the UL subband and the number of RBs for the guard band (if any) are set for each SCS setting in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0078] (Option 2-2): The frequency location of the UL subband and the number of RBs in the guard band are set for each SCS setting in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0079] (Option 2-3): The frequency location of the UL subband is configured for each SCS setting in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). The number of RBs in the guard band is configured for each SCS setting in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0080] - (Option 2-4): The frequency position of the UL subband and the number of guard band RBs, if any, are set for each SCS setting in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL) and for each SCS setting in the SCS-SpecificCarrierList of the UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0081] (3.3) Operation Example 1 In Case 1, as described above, the frequency locations of the UL subband and DL subband are explicitly configured. In Option 1-1, the frequency locations of the UL subband and DL subband are configured for each SCS setting in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). Specifically, the following example can be given:

[0082] (Example 1-1a): The frequency locations of the UL subband and DL subband are configured within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0083] 5 shows an example (Example 1-1a) of the configuration of information elements of the RRC layer according to Operation Example 1. Note that the names and structures of the information elements (IEs) are merely examples and are not necessarily limited to such examples. In the case of Option 1, new parameters for DL ​​subband / UL subband configuration may be present only when SCS-SpecificCarrier is DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0084] The offset and size parameters may be set for each UL / DL subband within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0085] UL and DL subband configuration parameters, such as sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19, are configured within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList. The offset and size (number of RBs) are configured for each of sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19.

[0086] For example, sbfd-ul-subband-offset-r19, sbfd-ul-subband-size-r19, sbfd-dl-subband1-offset-r19, sbfd-dl-subband1-size-r19, sbfd-dl-subband2-offset-r19 and sbfd-dl-subband2-size-r19 are set within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList.

[0087] (Example 1-1b): For each SCS configuration in the SCS-SpecificCarrierList, the frequency locations of the UL subband and DL subband are set in FrequencyInfoDL-SIB or FrequencyInfoDL.

[0088] 6 shows an example (Example 1-1b) of the configuration of information elements of the RRC layer according to Operation Example 1. The offset and size parameters of each UL / DL subband of each SCS in the SCS-SpecificCarrierList may be configured in the FrequencyInfoDL-SIB or FrequencyInfoDL. The list of DL / UL subband configurations may be configured in the FrequencyInfoDL-SIB or FrequencyInfoDL. Each element in the list may be mapped one-to-one to each SCS configuration in the SCS-SpecificCarrierList.

[0089] The determination of the PRBs available for use in the DL may be based on the intersection, which may also be referred to as a crossing point, a boundary, or the like, of the (active) DL BWP and the DL subbands configured for the SCS corresponding to the (active) DL BWP.

[0090] The determination of the PRBs available in the UL may be based on one of the following options:

[0091] (Option 1-1a): May be based on the intersection of the (active) UL BWP and the UL sub-band configured for the SCS of the DL BWP with the same BWP ID as the (active) UL BWP ID.

[0092] For example, if the active UL BWP ID is #0, the UL usable PRBs may be determined using the UL subbands configured for the SCS with DL BWP ID #0. Alternatively, the UE may assume that the UL subband boundaries are aligned with the boundaries of the RBs of the (active) UL BWP. Also, if the UL subband boundaries (i.e., some of the RBs of the UL BWP are within the UL subband and other parts of the RBs are outside the UL subband) are not aligned with the RB boundaries of the (active) UL BWP, the RBs may be assumed not to be UL usable PRBs.

[0093] (Option 1-1b): May be based on the intersection of the (active) UL BWP and the UL sub-band configured for the SCS corresponding to the (active) UL BWP.

[0094] For example, if the active UL BWP ID#0 has a 15 kHz SCS, the UL subbands configured for the 15 kHz SCS may be used to determine the PRBs available in the UL. Alternatively, the UE may assume that the UL subbands are configured for the SCS of the (active) UL BWP. Also, if the SCS of the (active) UL BWP is not configured in the DL SCS-SpecificCarrierList, the UE may not assume SBFD operation, regardless of whether the DL subbands are configured for the SCS of the (active) DL BWP.

[0095] 7 shows an example of determining PRBs according to operation example 1 (option 1-1b). In option 1-1, DL and UL subbands are configured for DL ​​SCS. However, no UL subband configuration for UL SCS is provided. Therefore, in order to determine PRBs that can be used in UL, it is necessary to select a UL subband configuration for DL ​​SCS.

[0096] In the case of Option 1-2, the frequency locations of the UL subband and DL subband are configured for each SCS configuration in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL). Specifically, the following examples are given:

[0097] (Example 1-2a): The frequency locations of the UL subband and DL subband are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0098] The offset and size parameters may be set for each UL / DL subband within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0099] UL and DL subband configuration parameters, such as sbfd-ul-subband-r19, sbfd-dl-subband1-r1, and sbfd-dl-subband2-r19, are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList. An offset and size (number of RBs) are configured for each of sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19.

[0100] For example, sbfd-ul-subband-offset-r19, sbfd-ul-subband-size-r19, sbfd-dl-subband1-offset-r19, sbfd-dl-subband1-size-r19, sbfd-dl-subband2-offset-r19 and sbfd-dl-subband2-size-r19 are set within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList.

[0101] (Example 1-2b): The frequency locations of the UL subbands and DL subbands are configured in FrequencyInfoUL-SIB and / or FrequencyInfoUL for each SCS setting in the UL SCS-SpecificCarrierList.

[0102] The offset and size parameters of each UL / DL subband for each SCS in the SCS-SpecificCarrierList may be configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL. A list of DL / UL subband configurations may be configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL. Each element in the list may map one-to-one to each SCS configuration in the SCS-SpecificCarrierList.

[0103] The determination of the PRBs available for use in the UL may be based on the intersection of the (active) UL BWP and the UL subbands configured for the SCS corresponding to the (active) UL BWP.

[0104] The determination of the PRBs available for use in the DL may be based on one of the following options:

[0105] (Option 1-2a): May be based on the intersection of the (active) DL BWP and the DL subband configured for the SCS of the UL BWP with the same BWP ID as the (active) DL BWP ID.

[0106] For example, if the active DL BWP ID is #0, the UL subbands configured for the SCS with UL BWP ID #0 may be used to determine the DL usable PRBs. Alternatively, the UE may assume that the DL subband boundaries are aligned with the RB boundaries of the (active) DL BWP. Also, if the DL subband boundaries (i.e., some of the RBs of the DL BWP are within the DL subband and other parts of the RBs are outside the DL subband) are not aligned with the RB boundaries of the (active) DL BWP, the RBs may be assumed not to be DL usable PRBs.

[0107] (Option 1-2b): May be based on the intersection of the (active) DL BWP and the DL subband configured for the SCS corresponding to the (active) DL BWP.

[0108] For example, if the active DL BWP ID#0 has a 15 kHz SCS, the DL subbands configured for the 15 kHz SCS may be used to determine the available PRBs for DL. Alternatively, the UE may assume that DL subbands are configured for the SCS of the (active) DL BWP. Also, if the SCS of the (active) DL BWP is not configured in the UL SCS-SpecificCarrierList, the UE may not assume SBFD operation, regardless of whether UL subbands are configured for the SCS of the (active) UL BWP.

[0109] In Option 1-2, DL and UL subbands are configured for the UL SCS. However, there is no DL subband configuration for the DL SCS. Therefore, to determine the DL usable PRBs, it is necessary to select the DL subband configuration for the UL SCS.

[0110] For Options 1-3, the frequency location of the UL subband is configured in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL) for each SCS configuration. The frequency location of the DL subband is configured in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). Specifically, the following examples are given:

[0111] (Example 1-3a): The frequency location of the UL subband is configured in the SCS-SpecificCarrier of the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL). The frequency location of the DL subband is configured in the SCS-SpecificCarrier of the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0112] The offset and size parameters of the UL subbands are configured in each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL), and the offset and size parameters of the DL subbands are configured in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0113] UL subband setting parameters, for example, sbfd-ul-subband-r19, are set within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList. DL subband setting parameters, for example, sbfd-dl-subband1-r19 and sbfd-dl-subband2-r19, are set within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList. The offset and size (number of RBs) are set for each of sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19.

[0114] For example, sbfd-ul-subband-offset-r19 and sbfd-ul-subband-size-r19 are set within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList, and sbfd-dl-subband1-offset-r19, sbfd-dl-subband1-size-r19, sbfd-dl-subband2-offset-r19, and sbfd-dl-subband2-size-r19 are set within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList.

[0115] (Example 1-3b): The frequency location of the UL subband is configured in FrequencyInfoUL-SIB and / or FrequencyInfoUL for each SCS configuration in SCS-SpecificCarrierList. The frequency location of the DL subband is configured in FrequencyInfoDL-SIB and / or FrequencyInfoDL for each SCS configuration in SCS-SpecificCarrierList.

[0116] The offset and size parameters of the UL subbands of each SCS in the SCS-SpecificCarrierList are configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL. The offset and size parameters of the DL subbands of each SCS in the SCS-SpecificCarrierList are configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL.

[0117] For example, a list of UL subband configurations may be configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL, where each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList. A list of DL subband configurations may be configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL, where each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList.

[0118] The determination of the PRBs available for use in the UL may be based on the intersection of the (active) UL BWPs and the UL subbands configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL of the SCS corresponding to the (active) UL BWPs.

[0119] The determination of the PRBs available for use in DL may be based on the FrequencyInfoDL-SIB of the SCS corresponding to the (active) DL BWP and / or the intersection of the (active) DL BWP and the DL subband configured in FrequencyInfoDL.

[0120] In the case of Options 1 to 4, the frequency locations of the UL subband and DL subband are configured for each SCS setting in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL) and for each SCS setting in the SCS-SpecificCarrierList of the UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).Specific examples include the following:

[0121] (Example 1-4a): The frequency locations of the UL subbands and DL subbands are configured in each SCS-SpecificCarrier in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). The frequency locations of the UL subbands and DL subbands are configured in each SCS-SpecificCarrier in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0122] The offset and size parameters are set for each UL / DL subband within each SCS-SpecificCarrier in the SCS-SpecificCarrierList for DL ​​(e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL), and for each SCS-SpecificCarrier in the SCS-SpecificCarrierList for UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0123] The UL and DL subband configuration parameters, e.g., sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19, are configured within each SCS-SpecificCarrier in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL). The offset and size (number of RBs) are configured for each of sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19.

[0124] sbfd-ul-subband-offset-r19, sbfd-ul-subband-size-r19, sbfd-dl-subband1-offset-r19, sbfd-dl-subband1-size-r19, sbfd-dl-subband2-offset-r19 and sbfd-dl-subband2-size-r19 are configured in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList and in each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0125] (Example 1-4b): For each SCS configuration in the SCS-SpecificCarrierList, the frequency locations of the UL subbands and DL subbands are configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL. The frequency locations of the UL subbands and DL subbands are configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL for each SCS configuration in the SCS-SpecificCarrierList.

[0126] For each SCS in the SCS-SpecificCarrierList, the offset and size parameters of each UL / DL subband are set in the FrequencyInfoUL-SIB and / or FrequencyInfoUL, and each SCS in the SCS-SpecificCarrierList is set in the FrequencyInfoDL-SIB and / or FrequencyInfoDL.

[0127] For example, a list of DL / UL subband configurations may be configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL, where each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList. A list of DL / UL subband configurations may be configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL, where each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList.

[0128] The determination of the PRBs available for use in the UL may be based on the intersection of the (active) UL BWP and the UL subbands configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL of the SCS corresponding to the (active) UL BWP.

[0129] The determination of the PRBs available for use in the DL may be based on the intersection of the active DL BWP and the DL subbands configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL of the SCS corresponding to the (active) DL BWP.

[0130] In options 1-4, DL and UL subbands are configured for DL ​​SCS and UL SCS, but the DL subband configuration for UL SCS is not used. Also, the UL subband configuration for DL ​​SCS is not used.

[0131] (3.4) Operation Example 2 In Case 2, as described above, the frequency location of the UL subband and the number of RBs of the guard band (if any) are explicitly set. In the case of Option 2-1, the frequency location of the UL subband and the number of RBs of the guard band (if any) are set for each SCS setting in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). Specifically, the following examples are given.

[0132] - (Example 2-1a): The frequency location of the UL subband and the number of RBs of the guard band (if any) are set within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0133] 8 shows a configuration example (Example 2-1a) of information elements of the RRC layer according to Operation Example 2. UL subband offset and size parameters and guard band size may be configured in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0134] UL subband and guard band configuration parameters, such as sbfd-ul-subband-r19 and sbfd-GB-size-r19, are configured in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList. An offset and size (number of RBs) may be configured for each sbfd-ul-subband-r19.

[0135] For example, sbfd-ul-subband-offset-r19, sbfd-ul-subband-size-r19, and sbfd-GB-size-r19 are set in each SCS-SpecificCarrier in the SCS-SpecificCarrierList of the DL.

[0136] (Example 2-1b): For each SCS configuration in the SCS-SpecificCarrierList, the frequency location of the UL subband and the number of RBs of the guard band (if any) are set in the FrequencyInfoDL-SIB or FrequencyInfoDL.

[0137] 9 shows a configuration example (Example 2-1b) of information elements of the RRC layer according to Operation Example 2. The parameters of the UL subband offset and size, and the guard band size of each SCS in the SCS-SpecificCarrierList may be set in FrequencyInfoDL-SIB or FrequencyInfoDL.

[0138] The list of UL subband and guard band size configurations may be configured in FrequencyInfoDL-SIB or FrequencyInfoDL, and each element in the list may have a one-to-one mapping to each SCS configuration in SCS-SpecificCarrierList.

[0139] The determination of PRBs available in the UL may be the same as in Option 1-1. For PRBs available in the DL, the DL subband(s) for each SCS configuration in the DL may be determined (in FrequencyInfoDL-SIB and / or SCS-SpecificCarrierList in FrequencyInfoDL).

[0140] The DL subbands for each SCS configuration in the SCS-SpecificCarrierList of the FrequencyInfoDL-SIB and / or FrequencyInfoDL may be configured with RBs within the carrier frequency resources for the DL SCS configuration, excluding the RBs of the UL subbands and guard bands configured for the DL SCS configuration.

[0141] Based on the determined DL subband, DL usable PRBs may be determined according to the same method for determining DL usable PRBs as in Option 1-1.

[0142] 10 shows an example of determining a DL subband according to operation example 2 (option 2-1). Note that in the case of option 2, the DL subband is not explicitly set. The UE needs to determine the DL subband based on the UL subband and the guard band.

[0143] In the case of Option 2-2, the frequency location of the UL subband and the number of RBs of the guard band (if any) are configured for each SCS configuration in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0144] - (Example 2-2a): The frequency location of the UL subband and the number of RBs of the guard band (if any) are set within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0145] The offset and size parameters of the UL subband and the guard band size are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0146] UL subband and guard band configuration parameters, such as sbfd-ul-subband-r19 and sbfd-GB-size-r19, are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList. The offset and size (number of RBs) are configured for each sbfd-ul-subband-r19. For example, sbfd-ul-subband-offset-r19, sbfd-ul-subband-size-r19, and sbfd-GB-size-r19 are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList.

[0147] - (Example 2-2b): For each SCS setting in the SCS-SpecificCarrierList, the frequency location of the UL subband and the number of RBs in the guard band (if any) are set in the FrequencyInfoUL-SIB and / or FrequencyInfoUL.

[0148] The offset and size parameters of the UL subband and the guard band size of each SCS in the SCS-SpecificCarrierList are set in FrequencyInfoUL-SIB and / or FrequencyInfoUL.

[0149] For example, a list of UL subband and guard band size configurations may be configured in FrequencyInfoUL-SIB and / or FrequencyInfoUL, and each element in the list may have a one-to-one mapping to each SCS configuration in SCS-SpecificCarrierList.

[0150] 11 shows an example of determining DL subbands according to operation example 2 (option 2-2). The determination of PRBs available in the UL may be based on the intersection of the (active) UL BWP and the UL subbands configured for the UL SCS configuration corresponding to the (active) UL BWP. For PRBs available in the DL, DL subbands for each SCS configuration in the DL may be determined (in FrequencyInfoDL-SIB and / or SCS-SpecificCarrierList of FrequencyInfoDL). In addition, any of the following operations may be applied.

[0151] (Alt-a): DL subbands are configured with RBs within the carrier frequency resources for SCS configuration by excluding UL subbands and RBs for the guard band configured for UL SCS configuration of a UL BWP with the same BWP ID as the (active) DL BWP ID.

[0152] For example, if the active DL BWP ID is #0, the DL subbands for the DL SCS are determined using the UL subbands and guard bands configured for the UL SCS configuration of UL BWP ID #0.

[0153] (Alt-b): The DL subband is configured with RBs within the carrier frequency resources for SCS configuration by excluding the UL subbands and RBs for the guard band configured for SCS.

[0154] If an UL subband and a guard band are configured in the SCS, the UE may assume the configuration. Based on the determined DL subband, the UE may determine DL usable PRBs according to the same method for determining DL usable PRBs as in Option 1-2.

[0155] In the case of Option 2-3, the frequency location of the UL subband is configured for each SCS configuration in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). The number of RBs of the guard band (if any) is configured for each SCS configuration in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL). Specifically, the following examples are given:

[0156] (Example 2-3a): The frequency location of the UL subband is configured in the SCS-SpecificCarrier of the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL). The number of RBs of the guard band (if any) is configured in the SCS-SpecificCarrier of the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0157] The offset and size parameters of the UL subbands are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL), and the guard band size is configured within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0158] UL subband configuration parameters, such as sbfd-ul-subband-r19, are configured within each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList. The offset and size (number of RBs) are configured for each sbfd-ul-subband-r19. Guard band size configuration, such as sbfd-GB-size-r19, is configured within each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList.

[0159] For example, sbfd-ul-subband-offset-r19 and sbfd-ul-subband-size-r19 are set in each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList, and sbfd-GB-size-r19 is set in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList.

[0160] (Example 2-3b): For each SCS configuration in the SCS-SpecificCarrierList, the frequency location of the UL subband is configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL. The number of RBs of the guard band (if any) is configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL for each SCS configuration in the SCS-SpecificCarrierList.

[0161] The offset and size parameters of the UL subband of each SCS in the SCS-SpecificCarrierList are configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL. The guard band size of each SCS in the SCS-SpecificCarrierList is configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL.

[0162] For example, a list of UL subband configurations may be configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL, where each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList. A list of guard band size configurations may be configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL, where each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList.

[0163] The determination of the PRBs available for use in the UL may be based on the intersection of the (active) UL BWP and the UL subbands configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL of the UL SCS configuration corresponding to the (active) UL BWP.

[0164] For PRBs available in DL, DL subbands for each SCS configuration in DL may be determined (in FrequencyInfoDL-SIB and / or SCS-SpecificCarrierList in FrequencyInfoDL), and one of the following actions may be applied:

[0165] (Alt-a): The DL subband is configured with the RBs within the carrier frequency resources of the SCS configuration and the number of RBs for the guard band configured for the DL SCS, by excluding the UL subbands configured for the SCS of the UL BWP with the same BWP ID as the (active) DL BWP ID.

[0166] For example, if the active DL BWP ID is #0, the DL subbands for the DL SCS are determined using the UL subbands configured for the SCS with UL BWP ID #0.

[0167] (Alt-b): The DL subband is configured with the RBs within the carrier frequency resources of the SCS configuration and the number of RBs for the guard band configured for the DL SCS, excluding the UL subband configured for the SCS.

[0168] Note that the UE may assume that an UL subband is configured for the SCS. Based on the determined DL subband, the DL usable PRB may be determined as the intersection of the (active) DL BWP of the DL SCS and the DL subband.

[0169] In the case of Options 2-4, the frequency location of the UL subband and the number of RBs for the guard band (if any) are configured for each SCS setting in the SCS-SpecificCarrierList of both DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL) and for each SCS setting in the SCS-SpecificCarrierList of UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0170] (Example 2-4a): The frequency location of the UL subband is configured in the SCS-SpecificCarrier of the SCS-SpecificCarrierList of the UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL). If there are guard band RBs, their number is configured in the SCS-SpecificCarrier of the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0171] The offset and size parameters of the UL subband and the size of the guard band are configured for each UL / DL subband within each SCS-SpecificCarrier in the SCS-SpecificCarrierList for DL ​​(e.g., FrequencyInfoDL-SIB and / or FrequencyInfoDL) and for each SCS-SpecificCarrier in the SCS-SpecificCarrierList for UL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0172] The UL subband and guard band configuration parameters, e.g., sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19, are configured within each SCS-SpecificCarrier in the SCS-SpecificCarrierList of the DL (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL). The offset and size (number of RBs) are configured for each of sbfd-ul-subband-r19, sbfd-dl-subband1-r19, and sbfd-dl-subband2-r19.

[0173] For example, sbfd-ul-subband-offset-r19, sbfd-ul-subband-size-r19 and sbfd-GB-size-r19 are set in each SCS-SpecificCarrier in the DL SCS-SpecificCarrierList and in each SCS-SpecificCarrier in the UL SCS-SpecificCarrierList (e.g., FrequencyInfoUL-SIB and / or FrequencyInfoUL).

[0174] (Example 2-4b): The frequency location of the UL subband is configured in FrequencyInfoUL-SIB and / or FrequencyInfoUL for each SCS configuration in the SCS-SpecificCarrierList. The number of RBs of the guard band (if any) is configured in FrequencyInfoDL-SIB and / or FrequencyInfoDL for each SCS configuration in the SCS-SpecificCarrierList.

[0175] The offset and size parameters of the UL subband and the guard band size of each SCS in the SCS-SpecificCarrierList are set in the FrequencyInfoDL-SIB and / or FrequencyInfoDL, and each SCS in the SCS-SpecificCarrierList is set in the FrequencyInfoDL-SIB and / or FrequencyInfoDL.

[0176] For example, a list of UL subbands and guard band size configurations may be configured in the FrequencyInfoDL-SIB and / or FrequencyInfoDL. Each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList. A list of UL subbands and guard band size configurations may be configured in the FrequencyInfoUL-SIB and / or FrequencyInfoUL. Each element in the list may have a one-to-one mapping to each SCS configuration in the SCS-SpecificCarrierList.

[0177] The determination of the PRBs available in the UL may be based on the intersection of the (active) UL BWP and the UL subbands configured in FrequencyInfoUL-SIB and / or FrequencyInfoUL for the UL SCS corresponding to the (active) UL BWP. For the PRBs available in the DL, the DL subbands for each DL SCS configuration may be determined (in the SCS-SpecificCarrierList of FrequencyInfoDL-SIB and / or FrequencyInfoDL).

[0178] The DL subbands of each DL SCS configuration in the SCS-SpecificCarrierList of FrequencyInfoDL-SIB and / or FrequencyInfoDL are configured with RBs within the carrier frequency resources of the DL SCS configuration by excluding the UL subbands and RBs of the guard band configured for the SCS of the DL.

[0179] Based on the determined DL subbands, the DL usable PRBs may be determined as the intersection of the (active) DL BWP of the DL SCS and the DL subbands.

[0180] (3.5) UE Capability The UE may report its capability (UE Capability Information) regarding support for cell-specific configuration of frequency locations of DL and UL subbands to the network. The UE Capability Information may be defined for each UE, frequency range (FR), frequency channel (FC), etc. Furthermore, RRC signaling and configuration for reporting the UE Capability Information may be defined.

[0181] According to the above-described operation example, when the frequency positions of the UL subband and DL subband are explicitly set (Case 1), or when the frequency position of the UL subband and the number of resource blocks (RBs) allocated to the guard band (which may only be the case when a guard band is set) are explicitly set, it is clearly defined how the SCS-SpecificCarrierList is specifically applied to the SBFD subband, and therefore the UE can appropriately and quickly set the SBFD subband while using the SCS-SpecificCarrierList.

[0182] That is, according to the above-described operation example, it is possible to set the frequency position of an appropriate SBFD subband while using the SCS-SpecificCarrierList.

[0183] (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.

[0184] For example, 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, a spare band, etc. Furthermore, XDD / SBFD may be a provisional name, and may be called by other similar terms as described above.

[0185] Additionally, 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.

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

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

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

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

[0190] 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 12 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 12, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0208] 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 to. The output information may be deleted. The input information may be transmitted to another device.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0255] 13 shows an example of the configuration of a vehicle 2001. As shown in Fig. 13, 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.

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

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

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

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

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

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

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

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

[0264] 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 Rotation speed 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 communication unit that transmits and receives radio signals according to a subband full-duplex communication 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 control unit that assumes that the frequency positions of the uplink subbands and the downlink subbands are set for each uplink and downlink subcarrier interval using information elements of a radio resource control layer.

2. A terminal comprising: a communication unit that transmits and receives radio signals according to a subband full-duplex communication method in which uplink subbands or downlink subbands are allocated non-overlapping in the frequency direction within a specified time period based on time division duplex; and a control unit that assumes that the frequency position of the uplink subband and the number of resource blocks of the guard band provided between the uplink subband and the downlink subband are set for each subcarrier interval of the uplink and downlink by information elements of a radio resource control layer.

3. The terminal according to claim 1 or 2, wherein the control unit assumes that the frequency position is set by the information element that instructs setting of the subcarrier spacing.

4. The terminal according to claim 1 or 2, wherein the control unit assumes that the information element sets an intersection point between an uplink bandwidth portion and the uplink subband.

5. A wireless communication method in a terminal, comprising: a step of transmitting and receiving wireless signals according to a subband full-duplex communication method in which uplink subbands or downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex; and a step of assuming that the frequency positions of the uplink subbands and the downlink subbands are set at subcarrier intervals using information elements of a radio resource control layer.

6. A wireless communication method in a terminal, comprising: a step of transmitting and receiving wireless signals according to a subband full-duplex communication method in which uplink subbands or downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex; and a step of assuming that the frequency position of the uplink subband and the number of resource blocks of a guard band provided between the uplink subband and the downlink subband are set for each subcarrier interval by information elements of a radio resource control layer.

Images