Terminal

Abstract

This terminal receives configuration information of an uplink control channel. The terminal configures the uplink control channel on the basis of the configuration information, and transmits the uplink control channel to a radio base station. The terminal receives separate configuration information when using a sub-band full duplex scheme in which an uplink sub-band and a downlink sub-band are allocated in a non-overlapping manner in the frequency direction within a specified time period based on time division duplexing, and when not using a sub-band full duplex scheme.

Description

Terminal

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

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

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

[0004] Non-Patent Document 1 points out that when SBFD is used, the sizes of the UL subband and BWP (Bandwidth Part) differ between SBFD symbols and non-SBFD symbols, and therefore it should be possible to configure separate PUCCH (Physical Uplink Control Channel) resources for a terminal (User Equipment, UE) when SBFD is used and when SBFD is not used.

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

[0006] However, the appropriate PUCCH resource configuration method (e.g., type of Uplink Control Information (UCI)) to be applied when SBFD is used and when SBFD is not used has not yet been established. Furthermore, it is necessary to consider the repetition of PUCCH transmission to be applied when SBFD is used.

[0007] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal that can realize appropriate PUCCH transmission when SBFD is used and when SBFD is not used.

[0008] One aspect of the present disclosure is a terminal (UE200) that includes a receiver (control signal / reference signal processor 240) that receives configuration information for an uplink control channel, a controller (controller 270) that configures the uplink control channel based on the configuration information, and a transmitter (control signal / reference signal processor 240) that transmits the uplink control channel to a radio base station, wherein the receiver receives different configuration information for a case where a subband full duplex scheme is used, in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex, and a case where the subband full duplex scheme is not used.

[0009] One aspect of the present disclosure is a terminal including a transmitter (control signal / reference signal processor 240) that repeatedly transmits an uplink control channel to a radio base station, and a controller (controller 270) that assumes that resources of the uplink control channel when using a subband full-duplex scheme in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplexing are associated with the uplink control channel when the subband full-duplex scheme is not used.

[0010] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram showing an example configuration of a wireless frame, a subframe, and a slot used in the wireless communication system 10. FIG. 3 is a diagram showing an example configuration of TDD and SBFD. FIG. 4 is a functional block configuration diagram of a gNB 100 and a UE 200. FIG. 5 is a diagram showing an example sequence of PUCCH setting and transmission according to an operation example 1. FIG. 6 is a diagram showing an example of the contents of the 3GPP specifications related to PUCCH-Config. FIG. 7 is a diagram showing an example hardware configuration of a gNB 100 and a UE 200. FIG. 8 is a diagram showing an example configuration of a vehicle 2001.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0052] The control signal and reference signal processor 240 may transmit the uplink control channel to the radio base station. In this embodiment, the control signal and reference signal processor 240 may constitute a transmitter that transmits the uplink control channel.

[0053] Specifically, the control signal and reference signal processing unit 240 may transmit the PUCCH to the gNB 100. The PUCCH may be repeatedly transmitted. Here, repeated transmission may mean repetition.

[0054] Furthermore, the control signal and reference signal processing unit 240 may receive PUCCH configuration information. In this embodiment, the control signal and reference signal processing unit 240 may configure a receiving unit that receives the configuration information. Specifically, the control signal and reference signal processing unit 240 may receive a PUCCH-Config for SBFD and a PUCCH-Config for non-SBFD.

[0055] More specifically, the control signal / reference signal processing unit 240 may receive separate PUCCH-Configs when using a subband full duplex method (SBFD) in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplexing, and when not using the subband full duplex method.

[0056] Furthermore, the control signal and reference signal processing unit 240 may receive not only the PUCCH-Config but also other configuration information with different contents for SBFD and non-SBFD. For example, resources for an acknowledgement (HARQ-ACK) of an automatic repeat request (HARQ), resources for a scheduling request (SR), and resources for a CSI (Channel State Information) PUCCH may be targeted.

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

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

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

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

[0061] Specifically, control unit 270 may configure the PUCCH based on PUCCH configuration information (for example, PUCCH-Config) received by control signal / reference signal processing unit 240. As described above, the PUCCH-Config may be configured separately for SBFD and non-SBFD. Therefore, control unit 270 can configure the PUCCH based on the PUCCH-Config for SBFD, and can also configure the PUCCH based on the PUCCH-Config for non-SBFD.

[0062] The control unit 270 may configure a PUCCH used for transmitting the HARQ-ACK based on the configuration information. The HARQ-ACK resources may be for a dynamic HARQ-ACK and / or an SPS HARQ-ACK. A dynamic HARQ-ACK may be interpreted as a HARQ-ACK associated with DCI.

[0063] The control unit 270 may configure a PUCCH used to transmit a scheduling request (SR) based on the configuration information. As described above, SR resources may also be configured separately for SBFD and non-SBFD.

[0064] The control unit 270 may configure a PUCCH used for transmitting channel state information (CSI) based on the configuration information. As described above, CSI PUCCH resources may also be configured separately for SBFD and non-SBFD.

[0065] In addition, the control unit 270 may assume that the resources of the PUCCH when using a subband full duplex method (SBFD) in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplexing are associated with the PUCCH when the subband full duplex method is not used.

[0066] Specifically, in the case of PUCCH repetition (repeated transmission), the control unit 270 may select an SBFD / non-SBFD type PUCCH resource associated with the PUCCH resource selected in the first non-SBFD / SBFD slot / subslot. The SBFD type PUCCH resource may be associated with the non-SBFD type PUCCH resource based on the RRC configuration.

[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 transmission and reception of the PUCCH when SBFD is applied.

[0068] (3.1) Assumptions According to 3GPP TR 38.858, considering that UL subbands and UL BWP sizes differ between SBFD symbols and non-SBFD symbols, it is considered effective to apply separate PUCCH configurations to SBFD and non-SBFD. In particular, it is considered acceptable to apply separate PUCCH repetition settings to SBFD and non-SBFD.

[0069] (3.2) Issues As described above, it is considered desirable to support separate configuration of PUCCH resources for SBFD and non-SBFD. However, such support is considered to have the following issues.

[0070] - (Problem 1): It is not clear how to set / obtain different PUCCH resource configurations for SBFD and non-SBFD.

[0071] For example, there are multiple levels of PUCCH resource configurations for different uplink control information (UCI) types (such as HARQ-ACK related to DCI). Different methods can be applied to configure different PUCCH resource configurations for SBFD and non-SBFD for all UCI types or for specific UCI types. Therefore, a method for configuring different PUCCH resources for SBFD and non-SBFD for different UCI types is required.

[0072] (Problem 2): When multiple solutions to Problem 1 are applied, the detailed behavior within the "corresponding PUCCH settings" may differ.

[0073] (Problem 3): Considering that the same coding rate is required for polar coding combinations, the method of transmitting PUCCH repetitions that takes into account SBFD slots / subslots and non-SBFD slots / subslots (hereinafter referred to as slots as appropriate) may require more special processing than PDSCH / PUSCH repetitions that span SBFD slots and non-SBFD slots.

[0074] (3.3) Overview of Operations The following operations may be performed for transmitting and receiving PUCCH when SBFD is applied.

[0075] (Operation Example 1): Configure separate PUCCH resources for the HARQ-ACK PUCCH, the CSI PUCCH, and the SR PUCCH.

[0076] (Option 1): Configure separate PUCCH-Configs for SBFD and non-SBFD.

[0077] (Option 2): Configure dynamic HARQ-ACK resources separately for SBFD and non-SBFD.

[0078] (Option 3): Configure SPS HARQ-ACK resources separately for SBFD and non-SBFD.

[0079] (Option 4): Configure SR resources separately for SBFD and non-SBFD.

[0080] (Option 5): Configure single CSI PUCCH resources separately for SBFD and non-SBFD.

[0081] (Option 6): Configure multi-CSI PUCCH resources separately for SBFD and non-SBFD.

[0082] Note that options 2 to 6 may be applied simultaneously.

[0083] (Operation Example 2): Determining PUCCH Resources Based on the Options in Operation Example 1 (Operation Example 2-1): Determining HARQ-ACK PUCCH Resources (Operation Example 2-2): Transmitting SR PUCCH Resources (Operation Example 2-3): Determining Single-CSI PUCCH Resources and Multi-CSI PUCCH Resources "Single-CSI PUCCH" may refer to a PUCCH for periodic CSI reporting. "Multi-CSI PUCCH" may refer to a PUCCH on which multiple CSI reports are multiplexed.

[0084] (Operation Example 3): Determining PUCCH Resources for PUCCH Repetition in SBFD Slots and Non-SBFD Slots Operation Example 3 may be independent of Operation Examples 1 and 2, or may be based on Operation Examples 1 and 2.

[0085] (3.4) Operational Examples (3.4.1) Operational Example 1 In this operational example, separate PUCCH resources may be configured for the HARQ-ACK PUCCH, CSI PUCCH, and SR PUCCH, and options 1 to 6 may be applied as described above.

[0086] (3.4.1.1) Option 1 In Option 1, separate PUCCH-Configs may be configured for SBFD and non-SBFD. Fig. 5 shows an example of a PUCCH configuration and transmission sequence according to Operation Example 1. Fig. 6 shows an example of the provisions of the 3GPP specifications related to PUCCH-Config. Specifically, Fig. 6 shows the provisions of Chapter 9 (partial excerpt) of 3GPP TS38.213.

[0087] One or two new or additional PUCCH-Configs may be configured for the SBFD type, such as PUCCH-Config-SBFD-r19. Option 1 may be applied to any UCI type.

[0088] If a new / additional PUCCH-Config (such as PUCCH-Config-SBFD-r19) is configured, the previous PUCCH-Config is for a non-SBFD type (i.e., applicable to PUCCHs with non-SBFD symbols), and the new PUCCH-Config-SBFD-r19 is for an SBFD type (i.e., applicable to PUCCHs with SBFD symbols).

[0089] The number of configured PUCCH-Config-SBFD-r19s will not be greater than the number of configured PUCCH-Configs.

[0090] If only one PUCCH-Config is configured and one PUCCH-Config-SBFD-r19 is configured, the PUCCH-Config-SBFD-r19 is for an SBFD type PUCCH resource with physical layer (PHY) priority index 0.

[0091] The UE may assume subslotLengthForPUCCH in PUCCH-Config-SBFD-r19 to be the same as subslotLengthForPUCCH in PUCCH-Config.

[0092] If two PUCCH-Configs are configured and two PUCCH-Config-SBFD-r19s are set, the first and second PUCCH-Config-SBFD-r19s are for SBFD type PUCCH resources with PHY priority indexes 0 and 1, respectively.

[0093] The UE may assume that the subslotLengthForPUCCH in the first and second PUCCH-Config-SBFD-r19 is the same as the subslotLengthForPUCCH in the first and second PUCCH-Config, respectively.

[0094] If two PUCCH-Configs are configured and only one PUCCH-Config-SBFD-r19 is configured, the PUCCH resource of PUCCH-Config-SBFD-r19 is an SBFD type PUCCH resource with PHY priority index 0 (or 1).

[0095] The UE may assume that the subslotLengthForPUCCH in PUCCH-Config-SBFD-r19 is the same as the subslotLengthForPUCCH in the first (or second) PUCCH-Config.

[0096] (3.4.1.2) Option 2 In option 2, SBFD and non-SBFD dynamic HARQ-ACK resources may be separated.

[0097] (Option 2-1): Separate PUCCH resource set lists for SBFD and non-SBFD In previous specifications, only one PUCCH resource set list exists in PUCCH-Config. A new list of PUCCH resource sets for SBFD may be additionally configured by PUCCH-Config (e.g., resourceSetToAddModList-SBFD-r19) (Example 2-A).

[0098] For PUCCH resource set IDs included in the legacy resourceSetToAddModList, the corresponding PUCCH resource set is of non-SBFD type. For PUCCH resource set IDs included in the new resourceSetToAddModList-SBFD-r19, the corresponding PUCCH resource set is of SBFD type.

[0099] As a variation, the maximum number of PUCCH resource sets in the SBFD / non-SBFD type PUCCH resource set list may be 4 or less than 4. Also, the maximum total number of PUCCH resource sets in the two lists of SBFD type and non-SBFD type in PUCCH-Config may remain 4 or may be greater than 4.

[0100] (Option 2-2): Divide SBFD and non-SBFD PUCCH resource sets within one PUCCH resource set list.

[0101] In the previous specification, up to four PUCCH resource sets can be configured in one PUCCH resource set list, and the PUCCH resource set list can include SBFD-type PUCCH resource sets and non-SBFD-type PUCCH resource sets.

[0102] To indicate the symbol type of the PUCCH resources in the PUCCH resource set, a new RRC parameter or non-SBFD type may be introduced into the PUCCH resource set configuration (Example 2-B).

[0103] If more than X (any natural number) PUCCH resource sets are configured, the first Y PUCCH resources (i.e., PUCCH resource sets with resource set IDs 0 to Y-1) may be for SBFD / non-SBFD type, and the remaining PUCCH resource sets may be for non-SBFD / SBFD type (Example 2-C).

[0104] The value of X may be defined by the specification or set by the RRC. The value of Y may be defined by the specification or set by the RRC and may depend on the value of X.

[0105] As a variation, the maximum number of PUCCH resources in a PUCCH resource set of SBFD / non-SBFD type may be 32 or less than 32. Also, the maximum total number of PUCCH resource sets including SBFD and non-SBFD types in a PUCCH-Config may remain at 4 or may be greater than 4.

[0106] (Option 2-3): Split the SBFD and non-SBFD resource lists within a single PUCCH resource set.

[0107] In previous specifications, a single resource list containing up to 32 resources can be configured in a PUCCH resource set, which can include a list of SBFD-type resources and a list of non-SBFD-type resources.

[0108] A new list of PUCCH resources for SBFD may be additionally configured in the PUCCH resource set (i.e., in PUCCH-ResourceSet). For example, resourceList-SBFD-r19 may be used (Example 2-D). For PUCCH resource IDs included in the conventional resourceList, the corresponding PUCCH resources are of non-SBFD type. For PUCCH resource IDs included in the new resourceList-SBFD-r19, the corresponding PUCCH resources are of SBFD type.

[0109] As a variation, the maximum number of PUCCH resources in a resource list of SBFD / non-SBFD type in a PUCCH resource set may be 32 or less than 32. Also, the maximum total number of PUCCH resources in two resource lists of SBFD type and non-SBFD type in a PUCCH resource set may remain at 32 or may be greater than 32.

[0110] (Option 2-4): Divide SBFD and non-SBFD PUCCH resources by resource list of PUCCH resource set. In the previous specification, one resource list containing up to 32 resources can be configured in a PUCCH resource set.

[0111] If more than X PUCCH resources are configured in the resource list of a PUCCH resource set, the first Y PUCCH resources are for SBFD / non-SBFD type, and the remaining PUCCH resources are for non-SBFD / SBFD type (Example 2-F).

[0112] The value of X may be defined by the specification or set by the RRC. The value of Y may be defined by the specification or set by the RRC and may depend on the value of X.

[0113] The SBFD / non-SBFD type for each PUCCH resource in the resource list of a PUCCH resource set may be determined based on a PUCCH resource ID (Example 2-F). For example, a new RRC parameter (SBFD type or non-SBFD type) may be indicated by a PUCCH resource configuration to indicate the symbol type of the PUCCH resource. Note that, if a PUCCH resource configuration includes a PUCCH resource ID, the relationship between the PUCCH resource ID and the SBFD / non-SBFD type may be configured.

[0114] As a variation, if the PUCCH resources are not configured in the new RRC parameters, the type of the PUCCH resources may be based on a predefined rule. For example, the default may be SBFD type or non-SBFD type, or the default may be non-type (which may mean, for example, that the PUCCH can be transmitted in SBFD and SBFD symbols in different slots / subslots). Also, a new list of SBFD type PUCCH resources may be additionally configured in PUCCH-Config. For example, resourceToAddModList-SBFD-r19 may be used.

[0115] For PUCCH resource IDs included in the legacy resourceToAddModList, the corresponding PUCCH resources are of non-SBFD type. For PUCCH resource IDs included in the new resourceToAddModList-SBFD-r19, the corresponding PUCCH resources are of SBFD type.

[0116] As a variation, the maximum total number of PUCCH resources, including SBFD and non-SBFD types, in a PUCCH resource set may remain at 32 or may be increased to more than 32.

[0117] (3.4.1.3) Option 3 In option 3, SPS HARQ-ACK resources may be separated for SBFD and non-SBFD.

[0118] (Option 3-1): Separate SPS HARQ-ACK resource lists for SBFD and non-SBFD In the previous specification, there is only one SPS HARQ-ACK resource list in the PUCCH-Config. A new SPS HARQ-ACK resource list for SBFD may be additionally configured in the PUCCH-Config (e.g., sps-PUCCH-AN-List-SBFD-r19, Example 3-A).

[0119] The SPS HARQ-ACK resources included in the conventional sps-PUCCH-AN-List-r16 are not of SBFD type. The SPS HARQ-ACK resources included in the new sps-PUCCH-AN-List-SBFD-r19 are of SBFD type.

[0120] As a variation, the maximum number of SPS HARQ-ACK resources in the SBFD / non-SBFD type SPS HARQ-ACK resource list may be 4 or less than 4. Also, the maximum total number of SPS HARQ-ACK resources in the two lists of SBFD type and non-SBFD type in the PUCCH-Config may remain 4 or may be greater than 4.

[0121] (Option 3-2): Separate SPS HARQ-ACK resources for SBFD and non-SBFD in one SPS HARQ-ACK resource list In the previous specification, up to four SPS HARQ-ACK resources could be configured in an SPS HARQ-ACK resource list. If more than X SPS HARQ-ACK resources are configured in an SPS HARQ-ACK resource list, the first Y SPS HARQ-ACK resources are for the SBFD / non-SBFD type, and the remaining SPS HARQ-ACK resources in the SPS HARQ-ACK resource list are for the non-SBFD / SBFD type (Example 3-B).

[0122] The value of X may be defined by the specification or set by the RRC. The value of Y may be defined by the specification or set by the RRC and may depend on the value of X.

[0123] To indicate the symbol type of the SPS HARQ-ACK resource, a new RRC parameter (SBFD type or non-SBFD type) may be configured in the SPS HARQ-ACK resource configuration (SPS-PUCCH-AN-r16) (Example 3-C).

[0124] As a variation, if the SPS HARQ-ACK resource is not configured in the new RRC parameters, the type of the SPS HARQ-ACK resource may be based on a predefined rule. For example, the default may be SBFD type or non-SBFD type, or the default may be non-type (e.g., this may mean that the SPS HARQ-ACK resource can be used in SBFD and SBFD symbols of different slots / subslots). Also, the maximum total number of SPS HARQ-ACK resources, including SBFD and non-SBFD types, in one SPS HARQ-ACK resource list may remain at 4 or may be greater than 4.

[0125] (Option 3-3): Separate PUCCH resources (or PUCCH resource IDs) for SBFD and non-SBFD within one SPS HARQ-ACK resource. The conventional SPS HARQ-ACK resource configuration corresponds to one PUCCH resource ID. Two PUCCH resource IDs, one for SBFD and one for non-SBFD types, may be configured in the SPS HARQ-ACK resource configuration (SPS-PUCCH-AN-r16, Example 3-D).

[0126] For example, a first PUCCH resource ID may be for SBFD / non-SBFD, and a second PUCCH resource ID may be for non-SBFD / SBFD. Furthermore, the SBFD / non-SBFD type of the two PUCCH resources may be determined based on the PUCCH resource IDs. Details of the mapping to PUCCH resource IDs and SBFD / non-SBFD types may be the same as those in Option 2-4 (Example 2-F) of Operation Example 1.

[0127] (3.4.1.4) Option 4 In option 4, SR resources may be separated for SBFD and non-SBFD.

[0128] (Option 4-1): Separation of SBFD and non-SBFD SR resource lists In the previous specification, there is only one SR resource list in PUCCH-Config. A new SR resource list for SBFD may be configured additionally (e.g., :schedulingRequestResourceToAddModList-SBFD-r19, Example 4-A). For SR PUCCH resource IDs included in the previous schedulingRequestResourceToAddModList, the corresponding SR resources are of non-SBFD type. For SR PUCCH resource IDs included in the new schedulingRequestResourceToAddModList-SBFD-r19, the corresponding SR resources are of SBFD type.

[0129] As a variation, the maximum number of SR resources in an SBFD / non-SBFD type SR resource list may be 8 or less than 8. Also, the maximum total number of SR resources in the two lists of SBFD and non-SBFD type in the PUCCH-Config may remain 8 or may be greater than 8.

[0130] (Option 4-2): Separate SR resources for SBFD and non-SBFD in one SR resource list. In the previous specification, up to eight SR resources can be configured in one SR resource list. To indicate the symbol type of the SR PUCCH resource, a new RRC parameter (e.g., SBFD type or non-SBFD type) may be configured in the SR resource configuration (SchedulingRequestResourceConfig) (Example 4-B).

[0131] If SR resources are not configured in the new RRC parameters, the type of SR resource may be based on predefined rules, e.g., default to SBFD type or non-SBFD type, or default to non-type (which may mean, for example, that SR can be transmitted in SBFD and SBFD symbols in different slots / subslots).

[0132] If there are X or more SR resources configured in the SR resource list, the first Y SR resources are for SBFD / non-SBFD type, and the remaining SR resources are for non-SBFD / SBFD type (Example 4-C).

[0133] The value of X may be defined by the specification or set by the RRC. The value of Y may be defined by the specification or set by the RRC and may depend on the value of X.

[0134] As a variation, the maximum total number of SR resources, including SBFD and non-SBFD types, in the SR resource list may remain at eight or may be greater than eight.

[0135] (Option 4-3): Separate PUCCH resources (or PUCCH resource IDs) for SBFD and non-SBFD within one SR resource In the previous specification, the SR resource configuration (SchedulingRequestResourceConfig) corresponds to one PUCCH resource ID. Two PUCCH resource IDs of SBFD and non-SBFD types may be configured in the SR resource configuration (SchedulingRequestResourceConfig), respectively (Example 4-D).

[0136] The first PUCCH resource ID is for SBFD / non-SBFD, and the second PUCCH resource ID is for non-SBFD / SBFD. In addition, the SBFD / non-SBFD type of the two PUCCH resources may be determined based on the PUCCH resource IDs.

[0137] Details of the mapping to the PUCCH resource ID and SBFD / non-SBFD type may be the same as those in Option 2-4 (Example 2-F) of Operation Example 1.

[0138] (3.4.1.5) Option 5 In option 5, a single CSI PUCCH resource may be separated for SBFD and non-SBFD.

[0139] (Option 5-1): Separate Periodic CSI Reporting Configuration for SBFD and Non-SBFD To indicate the symbol type of the CSI PUCCH resource, a new RRC parameter (e.g., SBFD type or non-SBFD type) may be configured in the CSI PUCCH resource configuration (PUCCH-CSI-Resource) (Example 5-A).

[0140] As a variation, if the CSI PUCCH resource is not configured in the new RRC parameters, the type of the CSI PUCCH resource may be based on a predefined rule, e.g., default to SBFD type or non-SBFD type, or default to non-type (which may mean, for example, that the CSI PUCCH can be transmitted in SBFD and SBFD symbols of different slots / subslots).

[0141] A new RRC parameter (e.g., SBFD type or non-SBFD type) may be configured in the periodic CSI reporting configuration (e.g., under reportConfigType) (Example 5-B).

[0142] As a variation, if the CSI reporting configuration is not configured in the new RRC parameters, the type of CSI reporting configuration may be based on a predefined rule, e.g., default to SBFD type or non-SBFD type, or default to non-type (which may mean, for example, that the CSI PUCCH can be transmitted in SBFD and SBFD symbols of different slots / subslots).

[0143] (Option 5-2): SBFD and non-SBFD PUCCH resources within one periodic CSI reporting configuration In the previous specification, one periodic CSI reporting configuration is associated with one list of PUCCH-CSI resources (only one PUCCH-CSI resource for BWP), and each PUCCH-CSI resource corresponds to one PUCCH resource ID.

[0144] For one periodic CSI reporting configuration, two lists of SBFD and non-SBFD type PUCCH-CSI resources may be configured. For example, the SBFD / non-SBFD type for each PUCCH-CSI resource may be configured by a new RRC parameter. Also, the first PUCCH-CSI resource may be for SBFD / non-SBFD, and the second PUCCH-CSI resource may be for non-SBFD / SBFD (Example 5-C).

[0145] Two PUCCH resource IDs of SBFD and non-SBFD type may be configured within one PUCCH-CSI-Resource (Example 5-D). For example, the first PUCCH resource ID may be for SBFD / non-SBFD, and the second PUCCH resource ID may be for non-SBFD / SBFD. Furthermore, the SBFD / non-SBFD type of the two PUCCH resources may be determined based on the PUCCH resource IDs.

[0146] Details of the mapping to the PUCCH resource ID and SBFD / non-SBFD type may be the same as those in Option 2-4 (Example 2-F) of Operation Example 1.

[0147] (3.4.1.6) Option 6 In option 6, multi-CSI PUCCH resources may be separated for SBFD and non-SBFD.

[0148] (Option 6-1): Separation of multi-CSI PUCCH resource list In the previous specification, there is only one multi-CSI resource list in PUCCH-Config. A new multi-CSI PUCCH resource list for SBFD may be additionally configured (e.g., multi-CSI-PUCCH-ResourceList-SBFD-r19, Example 6-A).

[0149] For multi-CSI PUCCH resource IDs included in the legacy multi-CSI-PUCCH-ResourceList, the corresponding multi-CSI PUCCH resources are of non-SBFD type. For multi-CSI PUCCH resource IDs included in the new multi-CSI-PUCCH-ResourceList-SBFD-r19, the corresponding multi-CSI PUCCH resources are of SBFD type.

[0150] As a variation, the maximum number of PUCCH resources in a multi-CSI PUCCH resource list of SBFD / non-SBFD type may be 2 or less than 2. Also, the maximum total number of PUCCH resources in the two lists of SBFD and non-SBFD type in PUCCH-Config may remain 2 or may be greater than 2.

[0151] (Option 6-2): Separate PUCCH Resources for SBFD and Non-SBFD in One Multi-CSI PUCCH Resource List In previous specifications, up to two PUCCH resources could be configured in one multi-CSI PUCCH resource list. If more than X PUCCH resources are configured in a multi-CSI PUCCH resource list (i.e., multi-CSI-PUCCH-ResourceList), the first Y PUCCH resources in the multi-CSI PUCCH resource list are for SBFD / non-SBFD type, and the remaining PUCCH resources in the multi-CSI PUCCH resource list are for non-SBFD / SBFD type (Example 6-B).

[0152] The value of X may be defined by the specification or set by the RRC. The value of Y may be defined by the specification or set by the RRC and may depend on the value of X.

[0153] The SBFD / non-SBFD type of the two PUCCH resources may be determined based on the PUCCH resource ID (Example 6-C). Details of the mapping between the PUCCH resource ID and the SBFD / non-SBFD type may be the same as those in Option 2-4 (Example 2-F) of Operation Example 1.

[0154] As a variation, the maximum total number of PUCCH resources, including SBFD and non-SBFD types, in a multi-CSI PUCCH resource list may remain at two or may be greater than two.

[0155] (3.4.2) Operational Example 2 In this operational example, PUCCH resources may be determined based on the options in Operational Example 1. Specifically, operational examples related to HARQ-ACK PUCCH resource determination, SR PUCCH resource transmission, single-CSI PUCCH transmission, and multi-CSI PUCCH resource determination will be described.

[0156] (3.4.2.1) Operation Example 2-1 In a slot for reporting ARQ-ACK, the HARQ-ACK PUCCH resource is determined based on the UCI payload size (and the PUCCH resource indicator (PRI)). In a slot for reporting HARQ-ACK, there are candidate PUCCH resources to select from SBFD PUCCH resources or non-SBFD PUCCH resources depending on the SBFD or non-SBFD type of the slot.

[0157] If a HARQ-ACK is reported in a slot containing only non-SBFD / SBFD symbols, the UE may determine the PUCCH resource from the non-SBFD / SBFD type HARQ-ACK PUCCH resources.If a HARQ-ACK is reported in a slot containing SBFD and non-SBFD symbols, the UE may determine the PUCCH resource from the non-SBFD or SBFD type HARQ-ACK PUCCH resources.

[0158] (Option a): The UE decides based on predefined rules.

[0159] (Option a-1): Use SBFD type or non-SBFD type by default. (Option a-2): Decide based on the order of SBFD / non-SBFD slots within a slot. For example, if an SBFD / non-SBFD symbol is located before (or after) a non-SBFD / SBFD symbol in a slot, the SBFD / non-SBFD type may be used. Also, if a PUCCH resource is selected using the SBFD / non-SBFD type and the determined PUCCH resource overlaps with a non-SBFD / SBFD symbol in the slot, the UE may not transmit the HARQ-ACK PUCCH (drop or postpone to the next slot).

[0160] As a variation, the UE may not assume that the PUCCH resource determined from the PUCCH resources of SBFD / non-SBFD type overlaps with the non-SBFD / SBFD symbols of the slot.

[0161] (Option b): The UE tries both types.

[0162] (Step 1): The UE may determine a PUCCH resource using a non-SBFD / SBFD type. If the determined PUCCH resource overlaps with an SBFD / non-SBFD symbol, the UE performs step 2.

[0163] (Step 2): The UE may determine the PUCCH resource using the SBFD / non-SBFD type. If the determined SBFD / non-SBFD type PUCCH resource overlaps with a non-SBFD / SBFD symbol, the UE may not transmit the HARQ-ACK PUCCH in that slot (drop it or postpone it to the next slot).

[0164] In Option a / b, "using SBFD / non-SBFD type" may mean the following: When Option 1 of Operation Example 1 (separate PUCCH-Configs for SBFD and non-SBFD) is applied, it may mean "selecting PUCCH resources based on the PUCCH resources configured in PUCCH-Config-SBFD-r19 / PUCCH-Config."

[0165] When option 2-1 / 2-2 of operation example 1 (separate PUCCH resource sets for SBFD and non-SBFD) is applied, this may mean "selecting a PUCCH resource set from the SBFD / non-SBFD PUCCH resource sets" for dynamic HARQ-ACK resource determination.

[0166] When option 2-3 / 2-4 of operation example 1 (separate PUCCH resources for SBFD and non-SBFD within a PUCCH resource set) is applied, this may mean that "PUCCH resource selection within a PUCCH resource set is made from SBFD / non-SBFD PUCCH resources within the PUCCH resource set" for dynamic HARQ-ACK resource determination.

[0167] (Alt-a): The PRI bit may apply / map to all PUCCH resources in the resource set, including SBFD and non-SBFD types. The maximum PRI field length may exceed 3 bits.

[0168] (Alt-b): The PRI bit may only be applied / mapped to PUCCH resources of type SBFD / non-SBFD in a resource set (or may be applied / mapped to a list of resources of type SBFD / non-SBFD in a resource set).

[0169] When option 3-1 / 3-2 of operation example 1 (separate SPS HARQ-ACK resources for SBFD and non-SBFD) is applied, this may mean that "SPS HARQ-ACK resources are selected from SBFD / non-SBFD SPS HARQ-ACK resources."

[0170] When option 3-3 of operation example 1 (separate PUCCH resources for SBFD and non-SBFD within the SPS HARQ-ACK resource) is applied, this may mean that "the selection of the SPS HARQ-ACK resource is the same as conventional, and the PUCCH resource for SBFD / non-SBFD within the selected SPS HARQ-ACK resource is used."

[0171] (3.4.2.2) Operation Example 2-2 For SR PUCCH transmission, the SR PUCCH resource may be configured for the SR setting. The UE may not perform PUCCH resource selection for SR reporting.

[0172] When Option 1 of Operation Example 1 is applied, for the SR configuration in PUCCH-Config / PUCCH-Config-SBFD-r19, the UE may report only SR opportunities with SR configuration of non-SBFD / SBFD symbols. If the SR PUCCH opportunity overlaps with an SBFD / non-SBFD symbol, the UE may avoid transmission in the SR PUCCH opportunity.

[0173] When Option 4-1 / 4-2 of Operation Example 1 is applied, the SR configuration may be configured as a non-SBFD / SBFD type. For a non-SBFD / SBFD type SR configuration, the UE may report only SR opportunities with SR configurations of non-SBFD / SBFD symbols. If an SR PUCCH occasion overlaps with an SBFD / non-SBFD symbol, the UE may avoid transmission in the SR PUCCH opportunity.

[0174] When option 4-3 of operation example 1 is applied (when the SR resource configuration is configured with two PUCCH resource IDs) and the SR reports a PUCCH occasion in a non-SBFD symbol, the UE may transmit a periodic CSI PUCCH using a non-SBFD type PUCCH resource. When the SR reports a PUCCH occasion in a SBFD symbol, the UE may transmit a periodic CSI PUCCH using a SBFD type PUCCH resource.

[0175] (3.4.2.3) Operation Example 2-3 In the case of single CSI PUCCH transmission, the CSI PUCCH resource may be configured for periodic CSI reporting. The UE may not perform PUCCH resource selection for the periodic CSI PUCCH.

[0176] If the periodic CSI reporting configuration is configured with only one PUCCH resource (conventional specifications), if the configured PUCCH resource is for non-SBFD / SBFD (e.g., option 1 or option 5-1 in operation example 1), the UE may transmit the periodic CSI PUCCH only on non-SBFD / SBFD symbols.

[0177] If the occurrence of the CSI PUCCH overlaps with an SBFD / non-SBFD symbol, the UE may not transmit the CSI PUCCH in that slot. When the periodic CSI reporting configuration is configured with two PUCCH resources (e.g., option 5-2 in operation example 1), one PUCCH resource is for the non-SBFD type and the other is for the non-SBFD type, if a PUCCH for a CSI report of a non-SBFD symbol occurs, the UE may transmit the periodic CSI PUCCH using the PUCCH resource for the non-SBFD type.

[0178] When a PUCCH for CSI reporting of an SBFD symbol occurs, the UE may transmit a regular CSI PUCCH using a PUCCH resource for SBFD type.

[0179] Regarding multi-CSI PUCCH resource determination, if the UE multiplexes multiple CSI reports into one PUCCH in a slot, the UE may select the multi-CSI PUCCH resource based on the UCI payload size. If the multi-CSI PUCCH is reported in a slot containing only non-SBFD / SBFD symbols, the UE may determine the PUCCH resource from the non-SBFD / SBFD type multi-CSI PUCCH resources.

[0180] If a multi-CSI PUCCH is reported in a slot containing SBFD and non-SBFD symbols, the UE may determine the PUCCH resource from the multi-CSI PUCCH resources of non-SBFD or SBFD type.

[0181] (Option a): The UE decides based on predefined rules.

[0182] (Option a-1): Use SBFD type or non-SBFD type by default. (Option a-2): Decision based on the order of SBFD / non-SBFD slots within a slot. For example, if an SBFD / non-SBFD symbol is located before (or after) a non-SBFD / SBFD symbol in a slot, the SBFD / non-SBFD type may be used. If a PUCCH resource is selected using the SBFD / non-SBFD type and the determined PUCCH resource overlaps with a non-SBFD / SBFD symbol in the slot, the UE may not transmit the PUCCH (drop or postpone to the next slot).

[0183] As a variation, the UE may not assume that the PUCCH resource determined from the PUCCH resources of SBFD / non-SBFD type overlaps with the non-SBFD / SBFD symbols of the slot.

[0184] (Option b): The UE tries both types.

[0185] (Step 1): The UE may determine a PUCCH resource using a non-SBFD / SBFD type. If the determined PUCCH resource overlaps with an SBFD / non-SBFD symbol, the UE performs step 2.

[0186] (Step 2): The UE may determine the PUCCH resource using the SBFD / non-SBFD type. If the determined SBFD / non-SBFD type PUCCH resource overlaps with a non-SBFD / SBFD symbol, the UE may not transmit the PUCCH in the slot (drop or postpone to the next slot).

[0187] In option a / b, "using SBFD / non-SBFD type" may mean, for example, based on option 6 in operation example 1.

[0188] (3.4.3) Operation Example 3 In this operation example, PUCCH resources for PUCCH repetition in SBFD slots and non-SBFD slots may be determined. In the case of HARQ-ACK PUCCH repetition, in conventional specifications, the PUCCH resource is determined in the first slot, and the same resource is used in the remaining slots.

[0189] If the first repetition of the HARQ-ACK PUCCH is in a non-SBFD / SBFD slot and the remaining repetition slots are in SBFD / non-SBFD slots, the operation may be performed according to one of the following.

[0190] - (Alt-1): The UE always uses the same resource.

[0191] (Alt-2): The UE selects a PUCCH resource from SBFD / non-SBFD type PUCCH resources (or PUCCH resource set, or PUCCH-Config) based on conventional PUCCH resource selection rules (e.g., corresponding UCI payload size and / or PRI).

[0192] - (Alt-2-1): The UE may assume that the PUCCH resource selected in the SBFD / non-SBFD slot and the PUCCH resource selected in the first non-SBFD / SBFD slot have the same number of REs / symbols / RBs and / or parameters (including code rate, repetition factor, and / or PUCCH format).

[0193] - (Alt-2-2): The UE may not repeatedly transmit PUCCH in an SBFD / non-SBFD slot (drop or postpone to the next slot) if the RE / symbol / RB and / or parameters (including code rate, repetition factor, and / or PUCCH format) of the PUCCH resource selected in the SBFD / non-SBFD slot are different from those of the PUCCH resource selected in the first non-SBFD / SBFD slot.

[0194] The slot may or may not be counted towards the Repetition factor (or available slot count).

[0195] (Alt-3): The UE may select a PUCCH resource of type SBFD / non-SBFD that is associated with the PUCCH resource selected in the first non-SBFD / SBFD slot.

[0196] The PUCCH resources of the SBFD type may be associated with the PUCCH resources of the non-SBFD type based on the RRC configuration.

[0197] In the case of SR / CSI PUCCH Repetition, in the conventional specification, the same resources as those in the first slot are used in the remaining slots. If the CSI / SR PUCCH is configured for a specific type (SBFD or non-SBFD type) (e.g., Option 1, 4-1, 4-2, or 5-1 in Operational Example 1), the UE may repeatedly transmit the CSI / SR PUCCH only for symbols of the corresponding type.

[0198] If the PUCCH resource of a slot overlaps with symbols of a different type, the slot may not be counted in the available slot count (or may not be counted in the Repetition factor).

[0199] If the CSI / SR PUCCH is not restricted to a specific type (SBFD or non-SBFD type), and the first repetition of the SR / CSI PUCCH is located in a non-SBFD / SBFD slot and the remaining repetition slots are located in SBFD / non-SBFD slots, the operation may be as follows:

[0200] - (Alt-1): The UE always uses the same resource.

[0201] (Alt-2): The UE selects a PUCCH resource of type SBFD / non-SBFD that is associated with the PUCCH resource selected in the first non-SBFD / SBFD slot.

[0202] The PUCCH resources of the SBFD type may be associated with the PUCCH resources of the non-SBFD type based on the RRC configuration.

[0203] (Alt-3): When two PUCCH resources of SBFD type and non-SBFD type are configured for the SR configuration or CSI reporting configuration (e.g., option 4-3 / 5-2 in operation example 1), the UE uses the other PUCCH resource of SBFD / non-SBFD type for the remaining repetitions of the SBFD / non-SBFD slot.

[0204] The UE may use the other PUCCH resource of SBFD / non-SBFD type for the remaining Repetitions of the SBFD / non-SBFD slot.

[0205] (Alt-3-1): The UE may assume that the number of REs / symbols / RBs and / or parameters (including code rate, repetition factor, and / or PUCCH format) of two PUCCH resources of SBFD type and non-SBFD type configured for one SR configuration or CSI reporting configuration are the same.

[0206] (Alt-3-2): If the number of REs / symbols / RBs and / or parameters (including code rate, repetition factor, and / or PUCCH format) of two PUCCH resources of SBFD type and non-SBFD type configured for one SR setting or CSI reporting setting are different, the UE may not repeatedly transmit the PUCCH of the SBFD / non-SBFD slot (drop or postpone to the next slot).

[0207] The slot may or may not be counted towards the Repetition factor (or available slot count).

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

[0209] Support for individual / additional / new PUCCH-Configs for SBFD type Support for individual PUCCH resource set lists for SBFD and non-SBFD in PUCCH-Config Support for individual PUCCH resource sets for SBFD and non-SBFD in one PUCCH resource set list Support for individual PUCCH resources for SBFD and non-SBFD within a PUCCH resource set Support for individual SPS HARQ-ACK resource set lists for SBFD and non-SBFD in PUCCH-Config Support for individual SPS HARQ-ACK resources for SBFD and non-SBFD in one SPS HARQ-ACK resource set list Support for individual PUCCH resources (or resource IDs) for SBFD and non-SBFD within one SPS HARQ-ACK resource Support for individual PUCCH resources (or resource IDs) for SBFD and non-SBFD within one SPS HARQ-ACK resource Support for individual SR resource lists for SBFD and non-SBFD in PUCCH-Config Support for separate SR resources for SBFD and non-SBFD in one SR resource list Support for separate PUCCH resources (or PUCCH resource IDs) for SBFD and non-SBFD in one SR resource Support for separate periodic CSI reporting configurations for SBFD and non-SBFD Support for separate PUCCH resources for SBFD and non-SBFD within one periodic CSI reporting configuration Support for separate multi-CSI PUCCH resource lists in PUCCH-Config Support for separate PUCCH resources for SBFD and non-SBFD in one multi-CSI PUCCH resource list Support for PUCCH Repetition in SBFD and non-SBFD slots

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

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

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

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

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

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

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

[0217] Furthermore, the above-described gNB100 and UE200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 7 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 7, the devices may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0291] (Additional Note) The above disclosure may be expressed as follows: A first feature is a terminal including: a receiver unit that receives configuration information for an uplink control channel; a controller unit that configures the uplink control channel based on the configuration information; and a transmitter unit that transmits the uplink control channel to a radio base station, wherein the receiver unit receives different configuration information for a case where a subband full duplex scheme is used, 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 case where the subband full duplex scheme is not used.

[0292] In a second feature based on the first feature, the control unit configures the uplink control channel used for transmitting an acknowledgment of an automatic repeat request based on the configuration information.

[0293] A third feature based on the first or second feature is that the control unit configures the uplink control channel used for transmitting a scheduling request based on the configuration information.

[0294] A fourth feature is any one of the first to third features, wherein the control unit configures the uplink control channel used for transmitting channel state information based on the configuration information.

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

Claims

1. A terminal comprising: a receiving unit that receives setting information for an uplink control channel; a control unit that sets the uplink control channel based on the setting information; and a transmitting unit that transmits the uplink control channel to a radio base station, wherein the receiving unit receives different setting information when using a subband full duplex method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex, and when not using the subband full duplex method.

2. The terminal according to claim 1, wherein the control unit sets the uplink control channel used for transmitting an acknowledgment of an automatic repeat request based on the setting information.

3. The terminal according to claim 1, wherein the control unit configures the uplink control channel used for transmitting a scheduling request based on the configuration information.

4. The terminal according to claim 1, wherein the control unit sets the uplink control channel used for transmitting channel state information based on the setting information.

5. A terminal comprising: a transmitter that repeatedly transmits an uplink control channel to a radio base station; and a controller that assumes that resources of the uplink control channel when using a subband full-duplex system in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplexing are associated with the uplink control channel when the subband full-duplex system is not used.

Images