terminal

Abstract

The terminal receives setting information of the uplink control channel. The terminal sets the uplink control channel based on the setting information, and transmits the uplink control channel to the radio base station. The terminal receives respective setting information in a case where a sub-band full duplex manner is used and in a case where the sub-band full duplex manner is not used, the sub-band full duplex manner referring to a manner in which an uplink sub-band and a downlink sub-band are non-overlappedly allocated in a frequency direction within a prescribed time based on time division duplex.

Description

Technical Field

[0001] This disclosure relates to terminals that support SBFD. Background Technology

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

[0003] For example, in 3GPP Release 18, an extension of duplex mode was studied (Non-Patent Document 1). Specifically, a new duplex mode, XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex), was proposed, which allows simultaneous use of downlink (DL) and uplink (UL) within a carrier of a time division duplex (TDD) band.

[0004] Non-patent document 1 points out that when using SBFD, since the size of the UL subband and BWP (Bandwidth Part) are different in SBFD symbols and non-SBFD symbols, it should be possible to set the PUCCH (Physical Uplink Control Channel) resources for each terminal (User Equipment, UE) when using SBFD and when not using SBFD.

[0005] Existing technical documents

[0006] Non-patent literature

[0007] Non-patent document 1: 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 Summary of the Invention

[0008] However, the appropriate PUCCH resource configuration methods (e.g., UCI (Uplink Control Information) types, etc.) for use when SBFD is employed and not employed have not yet been established. Furthermore, research is needed on PUCCH repetition, etc., that should be applied when SBFD is employed.

[0009] Therefore, the following disclosure is made in view of the situation and its purpose is to provide a terminal that can implement appropriate PUCCH transmission when using SBFD and when not using SBFD.

[0010] One aspect of the present invention is a terminal (UE200) comprising: a receiving unit (control signal) Reference signal processing unit 240, which receives uplink control channel setting information; control unit 270, which sets the uplink control channel based on the setting information; and transmission unit (control signal processing unit 240). Referring to the signal processing unit 240, which transmits the uplink control channel to the wireless base station, the receiving unit receives the setting information when using sub-band full-duplex mode and when not using the sub-band full-duplex mode, wherein the sub-band full-duplex mode refers to the mode in which the uplink sub-band and downlink sub-band are non-overlapping in the frequency direction within a specified time based on time division duplex.

[0011] One aspect of the present invention is a terminal comprising: a transmitting unit (control signal) Referring to the signal processing unit (240), which repeatedly transmits uplink control channels to the wireless base station; and the control unit (control unit 270), which envisions as associating the resources of the uplink control channel in the case of using subband full-duplex mode with the uplink control channel in the case of not using the subband full-duplex mode, wherein the subband full-duplex mode refers to the mode in which uplink subbands and downlink subbands are non-overlapping in the frequency direction within a specified time based on time division duplex. Attached Figure Description

[0012] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10.

[0013] Figure 2 This is a diagram illustrating an example of the structure of wireless frames, subframes, and time slots used in the wireless communication system 10.

[0014] Figure 3 This is a diagram showing structural examples of TDD and SBFD.

[0015] Figure 4This is a functional block structure diagram of gNB100 and UE200.

[0016] Figure 5 This is a diagram showing the PUCCH settings and transmission timing example for action example 1.

[0017] Figure 6 This is a diagram illustrating an example of the 3GPP specification related to PUCCH-Config.

[0018] Figure 7 This is a diagram illustrating an example of the hardware structure of gNB100 and UE200.

[0019] Figure 8 This is a diagram showing a structural example of vehicle 2001. Detailed Implementation

[0020] The embodiments are described below based on the accompanying drawings. Furthermore, the same or similar reference numerals are used to denote the same function or structure, and their descriptions are omitted where appropriate.

[0021] (1) Overall general structure of wireless communication system

[0022] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10 according to this embodiment. The wireless communication system 10 is a 5G New Radio (NR) compliant wireless communication system, including a Next Generation Radio Access Network (NG-RAN20) and a terminal 200 (hereinafter, UE200, User Equipment, UE). Alternatively, the wireless communication system 10 may also be a wireless communication system following protocols such as Beyond 5G, 5G Evolution, or 6G.

[0023] NG-RAN20 includes a radio base station 100 (hereinafter, gNB100). Furthermore, the specific structure of the wireless communication system 10, which includes gNBs and UEs, is not limited to [specific details needed]. Figure 1 The example shown.

[0024] NG-RAN20 actually contains multiple NG-RAN nodes, specifically multiple gNBs (or ng-eNBs), connected to a 5G-compliant core network (5GC, not shown). Furthermore, NG-RAN20 and 5GC can also be simply referred to as a "network".

[0025] The gNB100 is a 5G-compliant wireless base station that performs 5G-compliant wireless communication with the UE200. The gNB100 and UE200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output) by controlling the generation of more directional antenna beams (hereinafter, beams BM) through the control of wireless signals transmitted from multiple antenna elements, carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that allows simultaneous communication between the UE and each of the two NG-RAN nodes.

[0026] In addition, the DC can be of the type of multi-RATDual Connectivity (MR-DC) which utilizes multiple wireless access technologies, or NR-NR Dual Connectivity (NR-DC) which only utilizes NR. Furthermore, MR-DC can be E-UTRA-NR Dual Connectivity (EN-DC) where eNBs form the master node (MN) and gNBs form the slave node (SN), or it can be the opposite: NR-E-UTRA Dual Connectivity (NE-DC).

[0027] The gNB100 can transmit multiple beams (BMs) with different transmission directions (also referred to as direction, radiation direction, or coverage area, etc.) in a spatial and time-division manner. Furthermore, the gNB100 can also transmit multiple beams (BMs) simultaneously.

[0028] In addition, the wireless communication system 10 can support multiple frequency ranges (FRs). Specifically, it can support the following frequency ranges.

[0029] FR1: 410 MHz~7.125 GHz

[0030] ·FR2-1: 24.25 GHz~52.6 GHz

[0031] In FR1, sub-carrier spacing (SCS) of 15, 30, or 60 kHz can be used, along with a bandwidth (BW) of 5–100 MHz. FR2-1 is a higher frequency than FR1, and can use sub-carrier spacing (SCS) of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50–400 MHz.

[0032] Furthermore, SCS can be interpreted as a numerology. The numerology is defined in 3GPP TS 38.300 and corresponds to a subcarrier spacing in the frequency domain.

[0033] Furthermore, the wireless communication system 10 also supports frequency bands higher than FR2-1. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz and up to 71 GHz. Such high-frequency bands can also be referred to as FR2-2.

[0034] When using a band domain exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread (DFT-S-OFDM) with larger sub-carrier spacing (SCS) can be applied.

[0035] Furthermore, in high-frequency bands like FR2-2, as mentioned above, the increase in inter-carrier phase noise becomes a problem. Therefore, a larger (wider) SCS or single-carrier waveform is required.

[0036] The larger the SCS, the shorter the symbol / CP (Cyclic Prefix) period and the slot period (while maintaining a 14 symbol / slot structure). Figure 2 An example of the structure of wireless frames, subframes, and time slots used in wireless communication system 10 is shown.

[0037] While maintaining a 14-symbol / slot structure, a larger (wider) SCS results in a shorter symbol period (and slot period). The time direction can also be referred to as the time domain, time region, symbol period, symbol length, or symbol time, etc. Additionally, the frequency direction can be referred to as the frequency domain, resource block, subcarrier, BWP (Bandwidth part), etc.

[0038] Frequency resources may include component carriers, subcarriers, resource blocks (RBs), resource block groups (RBGs), and bandwidth parts (BWPs). Time resources may include symbols, time slots, mini-time slots, subframes, radio frames, and DRX (Discontinuous Reception) periods.

[0039] Furthermore, the number of symbols constituting one time slot does not necessarily have to be 14 symbols (e.g., 28, 56 symbols). In addition, the number of time slots in each subframe can vary depending on the SCS.

[0040] In the wireless communication system 10, an SSB (SS / PBCH Block) consisting of a synchronization signal (SS) and a downlink physical broadcast channel (PBCH) can be used.

[0041] The SSB is primarily transmitted periodically from the network for UE200 to perform cell ID and / or receive timing detection at the start of communication. In NR, the SSB is also used for receive quality measurements in each cell. The transmission period of the SSB can be specified as 5, 10, 20, 40, 80, 160 milliseconds, etc. Furthermore, the initial access period for UE200 can also be assumed to be 20 milliseconds.

[0042] Furthermore, various duplex modes can be used in the wireless communication system 10. Specifically, time division duplex (TDD) and frequency division duplex (FDD) can be used. Duplex mode can be explained as a way to achieve simultaneous transmission and reception (duplex communication) of downlink (DL) and uplink (UL).

[0043] Both gNB100 and UE200 can perform wireless communication via multiple channels with different purposes. These channels include control channels and data channels. Specifically, the physical layer control channels may include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) containing the Random Access Radio Network Temporary Identifier (RA-RNTI), and PBCH, etc.

[0044] Data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data can refer to data transmitted via data channels.

[0045] This channel can be scheduled not only dynamically, but also semi-fixed, semi-persistent, or semi-persistent SPS (Semi-Persistent Scheduling). Conceptually, SPS can be interpreted as a middle ground between dynamic and static scheduling. Compared to dynamic scheduling, SPS omits scheduling grants, which can help reduce signaling load.

[0046] In the wireless communication system 10, other duplexing methods capable of simultaneously using DL and UL can be used. Specifically, XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex) can be used. Hereinafter, XDD / SBFD will be appropriately abbreviated as SBFD.

[0047] Figure 3 Examples of TDD and SBFD structures are shown. Figure 3 As shown, in TDD as specified in 3GPP Releases 15-17, each symbol can be set to DL, UL or F (flexible: can be set to DL (D) or UL (U)) and indicated to UE200.

[0048] On the other hand, in SBFD (Subband Full-Duplex Mode), gNB100 is set to DL on specific frequency resources (e.g., subband) and UL on other frequency resources in the time domain (SBFD slot / symbol), and can be indicated to UE200.

[0049] In SBFD, both DL and UL can be used simultaneously 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 can also be referred to as a type of full-duplex communication, or FDD full-duplex, or, as SBFD is labeled, sub-band (DL / UL) full-duplex communication.

[0050] In SBFD, frequency resources for DL ​​(DL band) and frequency resources for UL (UL band) are allocated non-overlapping within the duplex frequency band at the same time.

[0051] Specifically, SBFD is a method of allocating the DL and UL bands in the time domain (SBFD slot / symbol) without frequency overlap, based on time-division duplex (TDD). The DL band can be interpreted as a DL sub-band, and the UL band as a UL sub-band. The time domain based on TDD duplex (without SBFD) is called the non-SBFD slot / symbol, in contrast to the SBFD slot / symbol.

[0052] (2) Functional block structure of wireless communication system

[0053] Next, the functional block structure of the wireless communication system 10 will be described. Specifically, the functional block structure of gNB100 will be described. Figure 4 This is a functional block structure diagram of gNB100 and UE200.

[0054] like Figure 4 As shown, the gNB100 includes a wireless signal transceiver unit 210, an amplifier unit 220, a modem unit 230, and a control signal transceiver unit 240. Reference signal processing unit 240, encoding / decoding unit 250, data transceiver unit 260 and control unit 270.

[0055] in addition, Figure 4 Only the main functional blocks relevant to the description of the implementation are shown, and the gNB100 (UE200) has other functional blocks (e.g., power supply section). Additionally, Figure 4 This shows the functional block structure of the gNB100. For more information on the hardware structure, please refer to [link / reference needed]. Figure 8 .

[0056] The radio transceiver unit 210 transmits and receives radio signals that comply with NR. The radio transceiver unit 210 can support Massive MIMO, which generates more directional beams by controlling radio (RF) signals transmitted from multiple antenna elements, carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that enables simultaneous communication between the UE and each node of two NG-RAN nodes.

[0057] Furthermore, the wireless transceiver unit 210 can transmit and receive wireless signals following the SBFD (Signal-Based Frequency Division Duplex) method. SBFD refers to a method in which uplink subbands (UL subbands) and downlink subbands (DL subbands) are allocated non-overlapping in the frequency direction within a specified time period based on Time Division Duplex (TDD). Of course, the wireless transceiver unit 210 can also support TDD and FDD (Frequency Division Duplex) duplex methods.

[0058] The amplification unit 220 is composed of a power amplifier (PA) and a low-noise amplifier (LNA). The amplification unit 220 amplifies the signal output from the modem 230 to a predetermined power level. Additionally, the amplification unit 220 amplifies the RF signal output from the wireless transceiver unit 210.

[0059] The modem 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication target (gNB100, etc.). Cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) / discrete Fourier transform spread (DFT-S-OFDM) can also be applied in the modem 230. Furthermore, DFT-S-OFDM can be used not only for the uplink (UL) but also for the downlink (DL).

[0060] The control signal and reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, as well as processing related to various reference signals transmitted and received by the UE200.

[0061] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, such as control signals from the Radio Resource Control (RRC) layer. Additionally, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via the predetermined control channel.

[0062] control signals The reference signal processing unit 240 performs processing using reference signals (RS) such as the demodulation reference signal (DMRS) and the tracking reference signal (TRS).

[0063] DMRS is a terminal-specific reference signal (pilot signal) used to estimate fading channels used in data demodulation, and is known between the base station and the terminal. PTRS is a terminal-specific reference signal used to estimate phase noise, which is a problem in the high-frequency band.

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

[0065] control signals The reference signal processing unit 240 can transmit an uplink control channel to the wireless base station. In this embodiment, the control signal... The reference signal processing unit 240 can be configured as a transmitter for transmitting the uplink control channel.

[0066] Specifically, control signals The reference signal processing unit 240 can send a PUCCH to the gNB100. The PUCCH can also be sent repeatedly. Here, repeated transmission can refer to repetition.

[0067] In addition, control signals The reference signal processing unit 240 can receive PUCCH setting information. In this embodiment, the control signal... The reference signal processing unit 240 can be configured as a receiving unit for receiving setting information. Specifically, the control signal The reference signal processing unit 240 can receive PUCCH-Config for SBFD and PUCCH-Config for non-SBFD respectively.

[0068] More specifically, control signals The reference signal processing unit 240 can receive its respective PUCCH-Config using a subband full-duplex mode (SBFD) 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 without using the subband full-duplex mode.

[0069] In addition, control signals The reference signal processing unit 240 can also receive not only PUCCH-Config, but also other configuration information for both SBFD and non-SBFD scenarios. For example, it can receive resources for HARQ-ACK (Hybrid Automatic Repeat Request), resources for SR (Schedule Request), and resources for CSI (Channel State Information) PUCCH.

[0070] The encoding / decoding unit 250 performs data segmentation / linking and channel encoding / decoding for each predetermined communication target (gNB100 or other gNB).

[0071] Specifically, the encoding / decoding unit 250 divides the data output from the data transceiver unit 260 into predetermined sizes and performs channel coding on the divided data. Additionally, the encoding / decoding unit 250 decodes the data output from the modem unit 230 and concatenates the decoded data.

[0072] The data transceiver unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transceiver unit 260 performs the assembly / disassembly of PDUs / SDUs at multiple layers (Media Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP), etc.). In addition, the data transceiver unit 260 performs error correction and retransmission control based on Hybrid Automatic Repeat Request (ARQ).

[0073] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 is capable of performing control related to SBFD.

[0074] Specifically, the control unit 270 can be based on control signals The PUCCH is configured using the PUCCH configuration information (e.g., PUCCH-Config) received by the reference signal processing unit 240. As described above, PUCCH-Config can be configured separately for SBFD and non-SBFD scenarios. Therefore, the control unit 270 can configure the PUCCH based on either the SBFD-oriented PUCCH-Config or the non-SBFD-oriented PUCCH-Config.

[0075] The control unit 270 can also configure the PUCCH for HARQ-ACK transmission based on this configuration information. Resources used for HARQ-ACK can target dynamic HARQ-ACK and / or SPS HARQ-ACK. Dynamic HARQ-ACK can be interpreted as HARQ-ACK associated with the DCI.

[0076] The control unit 270 can also set the PUCCH for sending scheduling requests (SRs) based on this setting information. As mentioned above, the resources for SRs can also be set separately for SBFD-oriented and non-SBFD-oriented scenarios.

[0077] The control unit 270 can also configure the PUCCH for transmitting Channel State Information (CSI) based on this configuration information. As described above, the CSI PUCCH resource can also be configured separately for SBFD and non-SBFD.

[0078] Furthermore, the control unit 270 can also be conceived as linking the PUCCH resources in the case of using a subband full-duplex mode (SBFD) where the uplink subband and downlink subband are allocated non-overlapping in the frequency direction within a specified time based on time division duplex, with the PUCCH in the case of not using the subband full-duplex mode.

[0079] Specifically, in the case of PUCCH repetition, the control unit 270 can select SBFD / non-SBFD type PUCCH resources to be associated with the PUCCH resources initially selected in the non-SBFD / SBFD time slot / sub-time slot. SBFD type PUCCH resources can be associated with non-SBFD type PUCCH resources based on RRC settings.

[0080] (3) Operation of wireless communication system

[0081] Next, the operation of the wireless communication system 10 will be explained. Specifically, the operation related to the transmission and reception of PUCCH in the case of SBFD application will be explained.

[0082] (3.1) Prerequisites

[0083] According to 3GPP TR 38.858, if the different UL subbands and UL BWP sizes in SBFD and non-SBFD symbols are taken into account, then PUCCH settings specific to SBFD and non-SBFD applications are considered valid. In particular, regarding PUCCH repetition, settings specific to SBFD and non-SBFD applications can be considered.

[0084] (3.2) Topic

[0085] As mentioned above, while it may be considered preferable to support the setting of PUCCH resources for both SBFD and non-SBFD, the following problems are believed to exist when implementing this support.

[0086] • (Question 1): The method for setting / obtaining separate PUCCH resource structures in SBFD and non-SBFD is unclear.

[0087] For example, there are multiple levels of PUCCH resource structures for different uplink control information (UCI) types (such as HARQ-ACK associated with DCI). Different methods can be applied to set separate PUCCH resource structures for all UCI types or specific UCI types in both SBFD and non-SBFD. Therefore, a method is needed to set separate PUCCH resources for different UCI types in both SBFD and non-SBFD.

[0088] • (Question 2): When applying multiple solutions for Question 1, the detailed actions in the "corresponding PUCCH settings" may differ.

[0089] • (Question 3): If the same coding rate is required in the combination of polar coding, the transmission method of PUCCH repetition considering SBFD time slots / sub-time slots and non-SBFD time slots / sub-time slots (hereinafter, appropriately abbreviated as time slots) may require more special handling compared to PDSCH / PUSCH repetition across SBFD time slots and non-SBFD time slots.

[0090] (3.3) Action Summary

[0091] Regarding the sending and receiving of PUCCH when using SBFD, the following actions can be performed.

[0092] • (Action Example 1): Set up dedicated PUCCH resources for HARQ-ACK PUCCH, CSI PUCCH and SR PUCCH.

[0093] • (Option 1): Set up dedicated PUCCH-Config for SBFD and non-SBFD respectively.

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

[0095] • (Option 3): Configure SPS HARQ-ACK resources for SBFD and non-SBFD respectively.

[0096] • (Option 4): Set SR resources separately for SBFD and non-SBFD.

[0097] • (Option 5): Configure a separate CSI PUCCH resource for SBFD and non-SBFD.

[0098] • (Option 6): Configure multiple CSI PUCCH resources for SBFD and non-SBFD respectively.

[0099] In addition, options 2 through 6 can also be used simultaneously.

[0100] • (Action Example 2): Decision on PUCCH resources based on the options in Action Example 1

[0101] • (Action Example 2-1): HARQ-ACK PUCCH resource decision

[0102] • (Action Example 2-2): SR PUCCH resource sending

[0103] • (Action Examples 2-3): Single CSI PUCCH transmission and multi-CSI PUCCH resource decision

[0104] "Single CSI PUCCH" refers to a PUCCH used for periodic CSI reports. "Multiple CSI PUCCH" refers to a PUCCH reused for multiple CSI reports.

[0105] • (Action Example 3): PUCCH resource determination for PUCCH repetition in SBFD and non-SBFD time slots

[0106] Action Example 3 can be independent of Action Examples 1 and 2, or it can be based on Action Examples 1 and 2.

[0107] (3.4) Example of an action

[0108] (3.4.1) Action Example 1

[0109] In this example, dedicated PUCCH resources can be set for HARQ-ACK PUCCH, CSI PUCCH, and SR PUCCH, as described above, and options 1 to 6 can be applied.

[0110] (3.4.1.1) Option 1

[0111] In option 1, you can set a dedicated PUCCH-Config for both SBFD and non-SBFD. Figure 5 The PUCCH settings and transmission timing example for action example 1 are shown. Figure 6 This section shows an example of the 3GPP specification regarding PUCCH-Config. Specifically, Figure 6 This shows a portion of the provisions in Chapter 9 of 3GPP TS38.213.

[0112] You can set one or two new or appended PUCCH-Configs for the SBFD type, such as PUCCH-Config-SBFD-r19. Option 1 can be applied to any UCI type.

[0113] When a new / appended PUCCH-Config (PUCCH-Config-SBFD-r19, etc.) is set, the existing PUCCH-Config is for non-SBFD types (that is, it can be applied to PUCCHs with non-SBFD symbols). In addition, the new PUCCH-Config-SBFD-r19 is for SBFD types (that is, it can be applied to PUCCHs with SBFD symbols).

[0114] The number of PUCCH-Config-SBFD-r19 values ​​set will not exceed the number of PUCCH-Config values ​​set.

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

[0116] Similar to subslotLengthForPUCCH in PUCCH-Config, the UE can envision subslotLengthForPUCCH in PUCCH-Config-SBFD-r19.

[0117] When two PUCCH-Configs are configured and two PUCCH-Config-SBFD-r19s are set, the first and second PUCCH-Config-SBFD-r19s are used for PUCCH resources of type SBFD with PHY priority index 0 and 1, respectively.

[0118] The UE can assume that the subslotLengthForPUCCH of the first and second PUCCH-Config-SBFD-r19 are the same as the subslotLengthForPUCCH of the first and second PUCCH-Config, respectively.

[0119] When two PUCCH-Configs are constructed, but only one PUCCH-Config-SBFD-r19 is constructed, the PUCCH resource of PUCCH-Config-SBFD-r19 becomes the SBFD type PUCCH resource with PHY priority index 0 (or 1).

[0120] The UE can also envision the same subslotLengthForPUCCH as the first (or second) PUCCH-Config-SBFD-r19.

[0121] (3.4.1.2) Option 2

[0122] In option 2, dynamic HARQ-ACK resources for SBFD and non-SBFD can be separated.

[0123] • (Option 2-1): List of dedicated PUCCH resource sets for SBFD and non-SBFD.

[0124] In the existing specification, only one list of PUCCH resource sets exists in PUCCH-Config. New lists of PUCCH resource sets for SBFD can be added through PUCCH-Config (e.g., resourceSetToAddModList-SBFD-r19) (Example 2-A).

[0125] With the existing resourceSetToAddModList containing PUCCH resource set IDs, the corresponding PUCCH resource set is not of type SBFD. With the new resourceSetToAddModList-SBFD-r19 containing PUCCH resource set IDs, the corresponding PUCCH resource set is of type SBFD.

[0126] As a variation, the maximum number of PUCCH resource sets in the SBFD / non-SBFD type PUCCH resource set list can be set to 4 or less. Furthermore, the maximum total number of PUCCH resource sets in both the SBFD and non-SBFD type lists of PUCCH-Config can be either 4 or greater than 4.

[0127] • (Option 2-2): Split the PUCCH resource sets in a list of PUCCH resource sets, including both SBFD and non-SBFD PUCCH resource sets.

[0128] In the existing specification, a maximum of four PUCCH resource sets can be set in a single PUCCH resource set list. The PUCCH resource set list can include SBFD type PUCCH resource sets and non-SBFD type PUCCH resource sets.

[0129] To indicate the symbol type of PUCCH resources within a PUCCH resource set, new RRC parameters or non-SBFD types can be imported into the PUCCH resource set settings (Example 2-B).

[0130] When there are more than X (any natural number) PUCCH resource sets, the first Y PUCCH resources (i.e., PUCCH resource sets with resource set IDs from 0 to Y-1) can be set to SBFD / non-SBFD type, and the remaining PUCCH resource sets can be set to non-SBFD / SBFD type (Example 2-C).

[0131] The value of X can be defined by the specification or set by the RRC. The value of Y can be defined by the specification or set by the RRC, or it can depend on the value of X.

[0132] As a variation, the maximum number of PUCCH resources within a PUCCH resource set of SBFD / non-SBFD types can be set to 32 or less. Furthermore, the maximum total number of PUCCH resource sets containing both SBFD and non-SBFD types within the PUCCH-Config can be either 4 or greater.

[0133] • (Options 2-3): Split the list of SBFD and non-SBFD resources within a single PUCCH resource set.

[0134] The existing specification allows setting a single resource list containing up to 32 resources within a PUCCH resource set. A PUCCH resource set can include lists of SBFD type resources and lists of non-SBFD type resources.

[0135] A new list of PUCCH resources for setting SBFD can be appended to the PUCCH resource set (i.e., within PUCCH-ResourceSet). For example, resourceList-SBFD-r19 (Example 2-D) can be used. With PUCCH resource IDs included in the existing resourceList, the corresponding PUCCH resource is not of type SBFD. With PUCCH resource IDs included in the new resourceList-SBFD-r19, the corresponding PUCCH resource is of type SBFD.

[0136] As a variation, the maximum number of PUCCH resources in the SBFD / non-SBFD type resource lists within the PUCCH resource set can be set to 32 or less. Furthermore, the maximum total number of PUCCH resources in both the SBFD and non-SBFD type resource lists within the PUCCH resource set can remain at 32 or be greater than 32.

[0137] • (Options 2-4): Split SBFD and non-SBFD PUCCH resources in the resource list of the PUCCH resource set.

[0138] In the existing specifications, it is possible to set a resource list that includes a maximum of 32 resources in the PUCCH resource set.

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

[0140] The value of X can be defined by the specification or set by the RRC. The value of Y can be defined by the specification or set by the RRC, and can also depend on the value of X.

[0141] The SBFD / non-SBFD type of each PUCCH resource within the resource list of a PUCCH resource set can be determined based on the PUCCH resource ID (Example 2-F). For example, to indicate the symbol type of a PUCCH resource, a new RRC parameter (SBFD type or non-SBFD type) can be indicated through the PUCCH resource setting. Additionally, when a PUCCH resource structure includes a PUCCH resource ID, the relationship between the PUCCH resource ID and the SBFD / non-SBFD type can be established.

[0142] As a variation, when PUCCH resources are not configured via new RRC parameters, the type of PUCCH resources can be based on predefined rules. For example, the default can be set to SBFD type or non-SBFD type, or the default can be set to non-type (e.g., this could mean that the PUCCH can be transmitted via SBFD and SBFD symbols in different time slots / sub-time slots). Furthermore, a new list of SBFD type PUCCH resources can be appended to the PUCCH-Config. For example, resourceToAddModList-SBFD-r19 can be used.

[0143] With the existing PUCCH resource IDs included in resourceToAddModList, the corresponding PUCCH resource is of type non-SBFD. With the new resourceToAddModList-SBFD-r19, the corresponding PUCCH resource is of type SBFD.

[0144] As a variation, the maximum total number of PUCCH resources in the PUCCH resource set, including both SBFD and non-SBFD types, can be kept at 32 or greater.

[0145] (3.4.1.3) Option 3

[0146] In option 3, SPS HARQ-ACK resources can be separated for SBFD and non-SBFD.

[0147] • (Option 3-1): List of dedicated SPS HARQ-ACK resources for both SBFD and non-SBFD

[0148] In the existing technical specifications, the SPS HARQ-ACK resource list in PUCCH-Config is only one. A new SPS HARQ-ACK resource list for setting SBFD can be appended to PUCCH-Config (e.g., sps-PUCCH-AN-List-SBFD-r19, e.g., 3-A).

[0149] In the case of SPS HARQ-ACK resources included in the existing sps-PUCCH-AN-List-r16, it is not of type SBFD. In the case of SPS HARQ-ACK resources included in the new sps-PUCCH-AN-List-SBFD-r19, it is of type SBFD.

[0150] As a variation, the maximum number of SPS HARQ-ACK resources in the SBFD / non-SBFD type SPS HARQ-ACK resource list can be set to 4 or less. Furthermore, the maximum total number of SPS HARQ-ACK resources in both the SBFD and non-SBFD type lists of PUCCH-Config can be 4 or greater than 4.

[0151] • (Option 3-2): A list of SPS HARQ-ACK resources for SBFD and dedicated SPSHARQ-ACK resources for non-SBFD.

[0152] In the existing specification, a maximum of four SPS HARQ-ACK resources can be set in the SPS HARQ-ACK resource list. If more than X SPS HARQ-ACK resources are set in the SPS HARQ-ACK resource list, the first Y SPS HARQ-ACK resources are for SBFD / non-SBFD types, and the remaining SPS HARQ-ACK resources in the SPS HARQ-ACK resource list are for non-SBFD / SBFD types (Example 3-B).

[0153] The value of X can be defined by the specification or set by the RRC. The value of Y can be defined by the specification or set by the RRC, or it can depend on the value of X.

[0154] To indicate the symbol type of an SPS HARQ-ACK resource, a new RRC parameter (SBFD type or non-SBFD type) can be set in the SPS HARQ-ACK resource settings (SPS-PUCCH-AN-r16) (Example 3-C).

[0155] As a variation, when SPS HARQ-ACK resources are not configured via new RRC parameters, the type of SPS HARQ-ACK resources can be based on predefined rules. For example, the default can be set to SBFD type or non-SBFD type, or the default can be set to no type (e.g., this could mean that SPS HARQ-ACK resources can be used in SBFD and SBFD symbols in different time slots / sub-slots). Furthermore, the maximum total number of SPS HARQ-ACK resources containing both SBFD and non-SBFD types within a single SPS HARQ-ACK resource list can be either 4 or greater.

[0156] • (Option 3-3): SBFD within an SPS HARQ-ACK resource and a dedicated PUCCH resource (or PUCCH resource ID) for non-SBFD use.

[0157] The existing SPS HARQ-ACK resource setting corresponds to one PUCCH resource ID. The two PUCCH resource IDs used for SBFD and non-SBFD types can be set separately through the SPS HARQ-ACK resource setting (SPS-PUCCH-AN-r16, Example 3-D).

[0158] For example, the first PUCCH resource ID can be SBFD / non-SBFD, and the second PUCCH resource ID can be non-SBFD / SBFD. Furthermore, the SBFD / non-SBFD type of the two PUCCH resources can be determined based on the PUCCH resource ID. Details of the mapping to PUCCH resource IDs and SBFD / non-SBFD types can be the same as options 2-4 (Example 2-F) in Action Example 1.

[0159] (3.4.1.4) Option 4

[0160] In option 4, SR resources can be separated for SBFD and non-SBFD.

[0161] • (Option 4-1): Separation of SR resource lists for SBFD and non-SBFD

[0162] In the existing specification, only one SR resource list exists in PUCCH-Config. A new list of SR resources for SBFD can be set by appending (e.g., schedulingRequestResourceToAddModList-SBFD-r19, Example 4-A). With the SR PUCCH resource IDs included in the existing schedulingRequestResourceToAddModList, the corresponding SR resource is not of SBFD type. With the SR PUCCH resource IDs included in the new schedulingRequestResourceToAddModList-SBFD-r19, the corresponding SR resource is of SBFD type.

[0163] As a variation, the maximum number of SR resources in the SBFD / non-SBFD type SR resource list can be set to 8 or less. Furthermore, the maximum total number of SR resources in both the SBFD and non-SBFD type lists of PUCCH-Config can be either 8 or greater than 8.

[0164] • (Option 4-2): SBFD within an SR resource list and dedicated SR resources for non-SBFD use.

[0165] In the existing specification, a maximum of 8 SR resources can be set in a single SR resource list. To indicate the symbol type of an SRPUCCH resource, new RRC parameters (e.g., SBFD type or non-SBFD type) can be set through SR resource settings (SchedulingRequestResourceConfig) (Example 4-B).

[0166] Without setting SR resources through new RRC parameters, the type of SR resources can be based on predefined rules. For example, the default can be set to SBFD type or non-SBFD type, or the default can be set to non-type (for example, it could mean that the SR can be transmitted in SBFD and SBFD symbols in different time slots / sub-time slots).

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

[0168] The value of X can be defined by the specification or set by the RRC. The value of Y can be defined by the specification or set by the RRC, or it can depend on the value of X.

[0169] As a variation, the maximum total number of SR resources in the SR resource list, including both SBFD and non-SBFD types, can be kept at 8 or greater than 8.

[0170] • (Option 4-3): SBFD within an SR resource and dedicated PUCCH resources (or PUCCH resource IDs) for non-SBFD use.

[0171] In the existing specification, the SR resource setting (SchedulingRequestResourceConfig) corresponds to one PUCCH resource ID. SBFD and two PUCCH resource IDs of non-SBFD types can also be set separately through the SR resource setting (SchedulingRequestResourceConfig) (Example 4-D).

[0172] The initial PUCCH resource ID is for SBFD / non-SBFD use, and the second PUCCH resource ID is for non-SBFD / SBFD use. Furthermore, the SBFD / non-SBFD type of the two PUCCH resources can be determined based on the PUCCH resource ID.

[0173] The details of the mapping to PUCCH resource ID and SBFD / non-SBFD types can be the same as options 2-4 (Example 2-F) of Action Example 1.

[0174] (3.4.1.5) Option 5

[0175] In option 5, individual CSI PUCCH resources can be separated for SBFD and non-SBFD.

[0176] • (Option 5-1): Setting up dedicated periodic CSI reports for SBFD and non-SBFD applications.

[0177] To indicate the symbol type of a CSI PUCCH resource, a new RRC parameter (e.g., SBFD type or non-SBFD type) can be set in the CSI PUCCH resource settings (PUCCH-CSI-Resource) (Example 5-A).

[0178] As a variation, when the CSI PUCCH resource is not set via new RRC parameters, the type of the CSI PUCCH resource can be based on predefined rules. For example, it can be set to SBFD type or non-SBFD type by default, or it can be set to non-type by default (for example, this could mean that the CSI PUCCH can be transmitted through SBFD and SBFD symbols in different time slots / sub-time slots).

[0179] New RRC parameters (e.g., SBFD type or non-SBFD type) can be set through periodic CSI reporting settings (e.g., under reportConfigType) (Example 5-B).

[0180] As a variation, if the CSI report setting is not configured through new RRC parameters, the type of the CSI report setting can be based on predefined rules. For example, the default can be set to SBFD type or non-SBFD type, or the default can be set to non-type (for example, this could mean that the CSI PUCCH can be transmitted through SBFD and SBFD symbols in different time slots / sub-time slots).

[0181] • (Option 5-2): SBFD and non-SBFD PUCCH resources within a periodic CSI reporting setting.

[0182] In the existing specification, a periodic CSI report is associated with a list of PUCCH-CSI-Resources (only one PUCCH-CSI-Resource in BWP). Furthermore, each PUCCH-CSI-Resource corresponds to a PUCCH resource ID.

[0183] For a periodic CSI report setup, two lists of PUCCH-CSI-Resource types can be set separately: one for SBFD and one for non-SBFD types. For example, the SBFD / non-SBFD type of each PUCCH-CSI-Resource can be set using a new RRC parameter. Furthermore, the initial PUCCH-CSI-Resource can be set to SBFD / non-SBFD, and the second PUCCH-CSI-Resource can be set to non-SBFD / SBFD (Example 5-C).

[0184] Two PUCCH resource IDs, one SBFD and one non-SBFD, can be set separately within a single PUCCH-CSI-Resource (Example 5-D). For example, the initial PUCCH resource ID can be set to SBFD / non-SBFD, and the second PUCCH resource ID can be set to non-SBFD / SBFD. Furthermore, the SBFD / non-SBFD type of the two PUCCH resources can be determined based on the PUCCH resource ID.

[0185] The details of the mapping to PUCCH resource ID and SBFD / non-SBFD types can be the same as options 2-4 (Example 2-F) of Action Example 1.

[0186] (3.4.1.6) Option 6

[0187] Option 6 allows for the separation of multiple CSI PUCCH resources for SBFD and non-SBFD purposes.

[0188] • (Option 6-1): Separation of multi-CSI PUCCH resource lists

[0189] In the existing specification, only one multi-CSI resource list exists in PUCCH-Config. New lists of multi-CSI resource lists for SBFD can be appended (e.g., multi-CSI-PUCCH-ResourceList-SBFD-r19, Example 6-A).

[0190] In the case of multiple CSI PUCCH resource IDs included in the existing multi-CSI-PUCCH-ResourceList, the corresponding multiple CSI PUCCH resources are of type non-SBFD. In the case of multiple CSI PUCCH resource IDs included in the new multi-CSI-PUCCH-ResourceList-SBFD-r19, the corresponding multiple CSI PUCCH resources are of type SBFD.

[0191] As a variation, the maximum number of PUCCH resources in the multi-CSI PUCCH resource list of SBFD / non-SBFD types can be 2 or less. Furthermore, the maximum total number of PUCCH resources in both the SBFD and non-SBFD lists of PUCCH-Config can remain at 2 or be greater than 2.

[0192] • (Option 6-2): A multi-CSI PUCCH resource list containing SBFD and dedicated PUCCH resources for non-SBFD use.

[0193] In the existing specification, a maximum of two PUCCH resources can be set in a multi-CSI PUCCH resource list. When more than X PUCCH resources are set in the 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 types, and the remaining PUCCH resources in the multi-CSI PUCCH resource list are for non-SBFD / SBFD types (Example 6-B).

[0194] The value of X can be defined by the specification or set by the RRC. The value of Y can be defined by the specification or set by the RRC, or it can depend on the value of X.

[0195] The SBFD / non-SBFD type of two PUCCH resources can be determined based on the PUCCH resource ID (Example 6-C). The details of the mapping to PUCCH resource ID and SBFD / non-SBFD type can be the same as options 2-4 of action example 1 (Example 2-F).

[0196] As a variation, the maximum total number of PUCCH resources containing both SBFD and non-SBFD types in the multi-CSI PUCCH resource list can be kept to 2 or greater.

[0197] (3.4.2) Action Example 2

[0198] In this action example, PUCCH resources can be determined based on the options in Action Example 1. Specifically, action examples related to HARQ-ACK PUCCH resource determination, SR PUCCH resource transmission, single CSI PUCCH transmission, and multi-CSI PUCCH resource determination are explained.

[0199] (3.4.2.1) Action Example 2-1

[0200] In the time slots used for ARQ-ACK reporting, the HARQ-ACK PUCCH resource is determined based on the UCI payload size (and the PUCCH resource indicator (PRI)). In the time slots used for HARQ-ACK reporting, depending on whether the time slot is SBFD or non-SBFD, there are candidate PUCCH resources selected from either SBFD or non-SBFD PUCCH resources.

[0201] When a HARQ-ACK is reported in a time slot containing only non-SBFD / SBFD symbols, the UE can determine the PUCCH resource from the non-SBFD / SBFD type HARQ-ACK PUCCH resource. When a HARQ-ACK is reported in a time slot containing both SBFD and non-SBFD symbols, the UE can determine the PUCCH resource from the non-SBFD or SBFD type HARQ-ACK PUCCH resource.

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

[0203] • (Option a-1): Defaults to using SBFD type or non-SBFD type

[0204] • (Option a-2): Determining the order of SBFD / non-SBFD time slots within a time slot.

[0205] For example, the SBFD / non-SBFD type can be used when the SBFD / non-SBFD symbol is located before (or after) a non-SBFD / SBFD symbol within a time slot. Furthermore, when using the SBFD / non-SBFD type to select PUCCH resources, and the determined PUCCH resource overlaps with a non-SBFD / SBFD symbol in the time slot, the UE may not send a HARQ-ACK PUCCH (discarding or deferring it to the next time slot).

[0206] As a variation, the UE may also disregard the overlap between the PUCCH resources determined based on the SBFD / non-SBFD type PUCCH resources and the non-SBFD / SBFD symbols of the time slot.

[0207] • (Option b): UE tries two types.

[0208] • (Step 1): The UE can use a non-SBFD / SBFD type to determine the PUCCH resource. If the determined PUCCH resource overlaps with SBFD / non-SBFD symbols, the UE performs step 2.

[0209] • (Step 2): The UE can use the SBFD / non-SBFD type to determine the PUCCH resource. If the determined SBFD / non-SBFD type PUCCH resource overlaps with non-SBFD / SBFD symbols, the UE may choose not to send the HARQ-ACK PUCCH in that time slot (discard or postpone it to the next time slot).

[0210] In options a / b, "Use SBFD / Non-SBFD type" can mean the following. In the case of option 1 of action example 1 (separate PUCCH-Config in SBFD and non-SBFD), it can mean "Select PUCCH resource based on the PUCCH resource set in PUCCH-Config-SBFD-r19 / PUCCH-Config".

[0211] In the case of applying option 2-1 / 2-2 of action example 1 (separate PUCCH resource sets in SBFD and non-SBFD respectively), it can mean "selecting a PUCCH resource set from the SBFD / non-SBFD PUCCH resource set" for dynamic HARQ-ACK resource determination.

[0212] In the case of option 2-3 / 2-4 of action example 1 (for SBFD and non-SBFD dedicated PUCCH resources within the PUCCH resource set), it can mean "selecting PUCCH resources within the PUCCH resource set from SBFD / non-SBFD PUCCH resources within the PUCCH resource set" in order to dynamically determine HARQ-ACK resources.

[0213] • (Alt-a): The PRI bit can be applied / mapped to all PUCCH resources within the resource set, including both SBFD and non-SBFD types. The maximum PRI field length can exceed 3 bits.

[0214] • (Alt-b): The PRI bit can be applied / mapped only to PUCCH resources of type SBFD / non-SBFD within the resource set (or can be applied / mapped to a list of resources of type SBFD / non-SBFD within the resource set).

[0215] In the case of applying option 3-1 / 3-2 of action example 1 (SPS HARQ-ACK resources dedicated to SBFD and non-SBFD), it can mean that "the selection of SPS HARQ-ACK resources is made from SPS HARQ-ACK resources of SBFD / non-SBFD".

[0216] In the case of option 3-3 of action example 1 (for SBFD and non-SBFD dedicated PUCCH resources within the SPS HARQ-ACK resource), it can mean that "the selection of the SPS HARQ-ACK resource is the same as the existing one, and the PUCCH resource for SBFD / non-SBFD within the selected SPSHARQ-ACK resource is used".

[0217] (3.4.2.2) Action Example 2-2

[0218] When SR PUCCH is transmitted, the SR PUCCH resources can be configured for SR settings. The UE may also choose not to perform PUCCH resource selection for SR reporting.

[0219] When applying option 1 of action example 1, in the SR settings of PUCCH-Config / PUCCH-Config-SBFD-r19, the UE can only report SR opportunities for non-SBFD / SBFD symbols. If an SR PUCCH opportunity overlaps with SBFD / non-SBFD symbols, the UE can avoid transmission during the SR PUCCH opportunity.

[0220] In the case of option 4-1 / 4-2 of action example 1, the SR setting can be set using a non-SBFD / SBFD type. With a non-SBFD / SBFD type SR setting, the UE can only report SR opportunities for non-SBFD / SBFD symbols. When an SR PUCCH occasion overlaps with SBFD / non-SBFD symbols, the UE can avoid transmission during the SR PUCCH occasion.

[0221] When option 4-3 of Action Example 1 is applied (where the SR resource setting consists of two PUCCH resource IDs), when the SR reports a PUCCH opportunity via non-SBFD symbols, the UE can use non-SBFD type PUCCH resources to send periodic CSI PUCCHs. When the SR reports a PUCCH occasion via SBFD symbols, the UE can use SBFD type PUCCH resources to send periodic CSI PUCCHs.

[0222] (3.4.2.3) Action Example 2-3

[0223] In the case of a single CSI PUCCH transmission, the CSI PUCCH resource can be configured for periodic CSI reporting. The UE may also choose not to perform PUCCH resource selection for periodic CSI PUCCHs.

[0224] In the case where the periodic CSI report is set using only one PUCCH resource (as per the existing specification), if the set PUCCH resource is not SBFD / SBFD (e.g., option 1 or option 5-1 of action example 1), the UE can send the periodic CSI PUCCH using only non-SBFD / SBFD symbols.

[0225] If the occurrence of a CSI PUCCH overlaps with SBFD / non-SBFD symbols, the UE may choose not to send the CSI PUCCH in that time slot. If the periodic CSI report is configured using two PUCCH resources (e.g., option 5-2 of Action Example 1), with one PUCCH resource designated for non-SBFD type and the other for non-SBFD type, and a non-SBFD symbol CSI report PUCCH is generated, the UE can use the non-SBFD type PUCCH resource to send the periodic CSI PUCCH.

[0226] When a CSI report using PUCCH occurs for SBFD symbols, the UE can use the PUCCH resources for SBFD type to send periodic CSI PUCCH.

[0227] Regarding the determination of multi-CSI PUCCH resources, when the UE multiplexes multiple CSI reports for one PUCCH in a time slot, the UE can select multi-CSI PUCCH resources based on the UCI payload size. When multiple CSI PUCCHs are reported through time slots containing only non-SBFD / SBFD symbols, the UE can decide on the PUCCH resources from non-SBFD / SBFD type multi-CSI PUCCH resources.

[0228] When multiple CSI PUCCHs are reported via time slots containing SBFD and non-SBFD symbols, the UE can determine the PUCCH resource from multiple CSI PUCCH resources of non-SBFD or SBFD type.

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

[0230] • (Option a-1): Defaults to using SBFD type or non-SBFD type

[0231] • (Option a-2): Determining the order of SBFD / non-SBFD time slots within a time slot.

[0232] For example, the SBFD / non-SBFD type can be used when the SBFD / non-SBFD symbol is located before (or after) the non-SBFD / SBFD symbol within the time slot. When using the SBFD / non-SBFD type to select the resource PUCCH, and the determined PUCCH resource overlaps with the non-SBFD / SBFD symbol of the time slot, the UE may not send the PUCCH (discarding or deferring it to the next time slot).

[0233] As a variation, the UE may also disregard the overlap between the PUCCH resources determined based on the SBFD / non-SBFD type PUCCH resources and the non-SBFD / SBFD symbols of the time slot.

[0234] • (Option b): UE tries two types.

[0235] • (Step 1): The UE can use a non-SBFD / SBFD type to determine the PUCCH resource. If the determined PUCCH resource overlaps with SBFD / non-SBFD symbols, the UE performs step 2.

[0236] • (Step 2): The UE can use SBFD / non-SBFD type to determine PUCCH resources. If the determined SBFD / non-SBFD type PUCCH resources overlap with non-SBFD / SBFD symbols, the UE may not transmit the PUCCH in the time slot (discard or postpone to the next time slot).

[0237] In options a / b, "use SBFD / non-SBFD type" could refer to option 6 based on action example 1, for example.

[0238] (3.4.3) Action Example 3

[0239] In this action example, the PUCCH resources used for PUCCH repetitions in SBFD and non-SBFD time slots can be determined. In the case of HARQ-ACK PUCCH repetitions, in the existing specification, the PUCCH resources are determined in the initial time slot, and the same resources are used in the remaining time slots.

[0240] If the initial repetition of the HARQ-ACK PUCCH is located in a non-SBFD / SBFD time slot, and the remaining repetitions are located in SBFD / non-SBFD time slots, the following actions can be performed.

[0241] • (Alt-1): The UE always uses the same resources.

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

[0243] • (Alt-2-1): The UE may assume that the same number of REs / symbols / RBs and / or parameters (including code rate, repetition coefficient and / or PUCCH format) are used for the PUCCH resources selected in the SBFD / non-SBFD time slot and the PUCCH resources selected in the initial non-SBFD / SBFD time slot.

[0244] • (Alt-2-2): If the PUCCH resource selected by the UE in the SBFD / non-SBFD time slot has different RE / symbol / RB and / or parameters (including code rate, repetition coefficient and / or PUCCH format) from the PUCCH resource selected in the initial non-SBFD / SBFD time slot, the UE may not repeatedly transmit PUCCH in the SBFD / non-SBFD time slot (discard or postpone to the next time slot).

[0245] The time slot can be counted for the Repetition coefficient (or the available time slot count), or it can be left uncounted.

[0246] • (Alt-3): The UE can select a PUCCH resource of type SBFD / non-SBFD associated with the PUCCH resource selected in the initial non-SBFD / SBFD time slot.

[0247] SBFD type PUCCH resources can be associated with non-SBFD type PUCCH resources based on RRC settings.

[0248] In the case of SR / CSI PUCCH Repetition, under the existing specifications, the same resources as the first time slot are used in the remaining time slots. When CSI / SR PUCCH is set for a specific type (SBFD or non-SBFD type) (e.g., option 1.4-1 / 4-2 / 5-1 of Action Example 1), the UE can repeatedly send CSI / SR PUCCH only for the corresponding type of symbols.

[0249] When a slot’s PUCCH resource overlaps with a different type of symbol, the slot may not be counted as a usable slot count (or may not be counted as a repetition coefficient).

[0250] When the CSI / SR PUCCH is unrestricted relative to a specific type (SBFD or non-SBFD type), and the initial repetition of the SR / CSI PUCCH is located in a non-SBFD / SBFD time slot, while the remaining repetitions are located in SBFD / non-SBFD time slots, it can be operated according to any of the following.

[0251] • (Alt-1): The UE always uses the same resources.

[0252] • (Alt-2): The UE selects a PUCCH resource of type SBFD / non-SBFD associated with the PUCCH resource selected in the initial non-SBFD / SBFD time slot.

[0253] SBFD type PUCCH resources can be associated with non-SBFD type PUCCH resources based on RRC settings.

[0254] • (Alt-3): When the UE has set both SBFD type and non-SBFD type PUCCH resources in the SR setting or CSI report setting (e.g., option 4-3 / 5-2 of action example 1), the remaining repetition of the SBFD / non-SBFD time slot uses the PUCCH resource of the other of the SBFD / non-SBFD types.

[0255] The UE can use the PUCCH resource of the other party in the SBFD / non-SBFD type for the remaining repetition of the SBFD / non-SBFD slot.

[0256] • (Alt-3-1): The UE may envision that for an SR setting or CSI report setting, the number of RE / symbol / RB and / or parameters (including code rate, repetition coefficient and / or PUCCH format) of two PUCCH resources of SBFD type and non-SBFD type are the same.

[0257] • (Alt-3-2): The UE may not repeatedly transmit PUCCH in SBFD / non-SBFD time slots (discard or postpone to the next time slot) if the number of RE / symbol / RB and / or parameters (including code rate, repetition coefficient and / or PUCCH format) of two PUCCH resources of SBFD type and non-SBFD type set in an SR setting or CSI report setting is different.

[0258] The time slot can be counted for the Repetition coefficient (or the available time slot count), or it can be left uncounted.

[0259] (3.5) UE capabilities

[0260] Regarding the transmission and reception of various channels when using SBFD, the following UE capabilities and reporting signaling (including RRC settings) can be defined. These UE capabilities and signaling can also be defined per UE, per frequency range (FR), or per frequency channel (FC).

[0261] • Support for dedicated / additional / new PUCCH-Config of SBFD type

[0262] • Support for dedicated PUCCH resource set lists for SBFD and non-SBFD in PUCCH-Config

[0263] • Support for dedicated PUCCH resource sets for SBFD and non-SBFD users in a PUCCH resource set list.

[0264] • Support for dedicated PUCCH resources for both SBFD and non-SBFD within the PUCCH resource set

[0265] • Support for a dedicated SPS HARQ-ACK resource set list for SBFD and non-SBFD in PUCCH-Config

[0266] • Support for dedicated SPS HARQ-ACK resources for both SBFD and non-SBFD in a list of SPS HARQ-ACK resource sets.

[0267] • Support for SBFD within an SPS HARQ-ACK resource and dedicated PUCCH resources (or resource IDs) used for non-SBFDs.

[0268] • Support for SBFD within an SPS HARQ-ACK resource and dedicated PUCCH resources (or resource IDs) used for non-SBFDs.

[0269] • Support for SBFD and dedicated SR resource lists for non-SBFD uses in PUCCH-Config

[0270] • Support for SBFD in an SR resource list and dedicated SR resources for non-SBFD use.

[0271] • Support for SBFD in an SR resource and dedicated PUCCH resources (or PUCCH resource IDs) used for non-SBFD purposes

[0272] • Support for dedicated periodic CSI reporting settings for both SBFD and non-SBFD applications

[0273] • Support for dedicated PUCCH resources for both SBFD and non-SBFD within a periodic CSI report setting.

[0274] • Support for a dedicated multi-CSI PUCCH resource list in PUCCH-Config

[0275] • Support for SBFD and dedicated PUCCH resources for non-SBFD use in a multi-CSI PUCCH resource list

[0276] • Support for PUCCH Repetition in SBFD and Non-SBFD Slots

[0277] (4) Other implementation methods

[0278] The above describes the embodiments, but the present invention is not limited to the embodiments described therein, and various modifications and improvements can be made, which will be obvious to those skilled in the art.

[0279] For example, in the above embodiments, channels of a specific physical layer are described as objects, but channels of other physical layers can also be used as objects. Furthermore, in the above embodiments, the term "subband" is used, but a subband can be simply referred to as a band, or it can be called an auxiliary band, a reserve band, or similar terms. Additionally, XDD / SBFD can be a temporary designation, or it can be referred to as similar terms as described above.

[0280] Furthermore, in the above description, the terms configure, activate, update, indicate, enable, specify, and select can be interchanged. Similarly, the terms link, associate, correspond, and map can be interchanged, as can allocate, assign, monitor, and map.

[0281] Furthermore, specific, dedicated, UE specific, and UE dedicated can be used interchangeably. Similarly, common, shared, group-common, UE common, and UE shared can also be used interchangeably.

[0282] In this disclosure, the terms "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", "beamwidth", "beam angle", "antenna", "antenna element", and "panel" can be used interchangeably.

[0283] Furthermore, the block structure diagram used in the above description of the embodiments ( Figure 4The diagram illustrates blocks organized by function. These functional blocks (components) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can be implemented by combining software with one or more of the aforementioned devices.

[0284] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0285] Furthermore, the aforementioned gNB100 and UE200 (the device) can also function as a computer for processing the wireless communication method disclosed herein. Figure 7 This is a diagram illustrating an example of the hardware structure of the device. (As shown...) Figure 7 As shown, the device can also be configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0286] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of this device can be configured as either a device comprising one or more of the illustrated components, or a device without any components.

[0287] The functional blocks of the device (refer to) Figure 4 This can be achieved through any hardware element or combination of hardware elements of the computer device.

[0288] Furthermore, the functions of the device are implemented by reading predetermined software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication of communication device 1004 or controls at least one of reading and writing data in memory 1002 and storage device 1003.

[0289] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc.

[0290] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one direction of memory 1002 in the storage device 1003 and the communication device 1004, and performs various processes accordingly. The program is used to cause the computer to perform at least a portion of the actions described in the above embodiments. Moreover, the various processes described above can be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 can also be implemented using one or more chips. Furthermore, the program can also be transmitted from a network via a telecommunications line.

[0291] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and random access memory (RAM). The memory 1002 may be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 may store programs (program code), software modules, etc., capable of executing the methods involved in one embodiment of this disclosure.

[0292] Storage device 1003 is a computer-readable recording medium, and may be composed of at least one of the following: optical discs such as CD-ROM (Compact Disc ROM), hard disk drives, floppy disks, magneto-optical discs (e.g., compact discs, digital multipurpose discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. Storage device 1003 may also be referred to as an auxiliary storage device. The aforementioned recording medium may, for example, be a database, server, or other suitable media that includes at least one of memory 1002 and storage device 1003.

[0293] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. For example, it may also be called a network device, network controller, network card, communication module, etc.

[0294] The communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0295] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0296] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured using a single bus or different buses can be used between each device.

[0297] Furthermore, the device can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), which can be used to implement some or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0298] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, information notification may also be implemented through 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 combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0299] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (x being, 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 The system may include at least one of 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on these systems. Alternatively, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) for application.

[0300] The processing procedures, timing, and flow of the various forms / implementations described in this disclosure may be changed in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order in the methods described in this disclosure, but are not limited to the specific order indicated.

[0301] In this disclosure, certain actions performed by the base station are sometimes also performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having a base station, it is obvious that various actions performed to communicate with a terminal can be performed by at least one of the base station and other network nodes besides the base station (e.g., considering an MME or S-GW, but not limited to these). The above illustration depicts a case where there is only one other network node besides the base station, but it can also be a combination of multiple other network nodes (e.g., an MME and an S-GW).

[0302] It can output information and signals (information, etc.) from a higher (or lower) level to a lower (or higher) level. It can also be input or output through multiple network nodes.

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

[0304] The determination can be made by the value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparing numerical values ​​(e.g., comparing with a predetermined value).

[0305] The various forms / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information (e.g., a "It is X" notification) is not limited to being explicit, but can also be implicit (e.g., not being notified of the predetermined information).

[0306] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0307] In addition, software, commands, information, etc., can be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0308] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description as a whole can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0309] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0310] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0311] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources can also be indicated using indexes.

[0312] The names used for the parameters described above are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters may sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any appropriate name, and therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0313] In this disclosure, the terms "Base Station (BS)," "wireless 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" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0314] 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 also provide communication services through the base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0315] Terms such as “cell” or “sector” refer to a portion or the entire coverage area of ​​at least one of the base stations and base station subsystems that provide communication services within that coverage area.

[0316] In this disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal on information-based control / actions.

[0317] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.

[0318] For mobile stations, those skilled in the art sometimes also use the following terms: 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, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0319] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Furthermore, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). In addition, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0320] Furthermore, the base station in this disclosure can also be replaced by a mobile station (user terminal, hereinafter the same). For example, various forms / implementations of this disclosure can also be applied to structures that replace communication between the base station and the mobile station with communication between multiple mobile stations (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the structure can also be configured such that the mobile station has the functions of the base station. In addition, terms such as "uplink" and "downlink" can also be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel (or side link).

[0321] Similarly, the mobile station in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of a mobile station.

[0322] A radio frame can consist of one or more frames in the time domain. In the time domain, one or more frames can be called subframes. A subframe can also consist of one or more time slots in the time domain. A subframe can be a fixed duration (e.g., 1 ms) independent of the parameter set (numerology).

[0323] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0324] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

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

[0326] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also be referred to by their respective alternative names.

[0327] For example, a subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., symbols 1-13), or a period longer than 1ms. In addition, the unit representing TTI can also be called a time slot, mini-time slot, etc., instead of a subframe.

[0328] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc. available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0329] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than that TTI.

[0330] Furthermore, when a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can become the minimum time unit for scheduling. Additionally, the number of time slots (mini-time slots) constituting this minimum time unit for scheduling can also be controlled.

[0331] A TTI with a duration of 1ms can also be called a normal TTI (TTI in LTE Rel.8-12), a regular TTI, a long TTI, a regular subframe, a normal subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0332] Additionally, for long TTIs (e.g., normal TTIs, subframes, etc.), a TTI with a duration of more than 1ms can be used as a replacement, and for short TTIs (e.g., shortened TTIs, etc.), a TTI with a duration of less than a long TTI and more than 1ms can be used as a replacement.

[0333] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0334] Furthermore, the temporal domain of an RB can include one or more symbols, or it can be the length of a time slot, a mini-time slot, a subframe, or a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0335] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0336] Furthermore, a resource block can consist of one or more resource elements (REs). For example, 1 RE can be a radio resource area with 1 subcarrier and 1 symbol.

[0337] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a given carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0338] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.

[0339] At least one of the configured BWPs can be active, and it is not assumed that the UE will transmit or receive predetermined signals / channels outside of an active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0340] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc., can be varied in many ways.

[0341] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0342] The reference signal can be simply called the Reference Signal (RS), or, depending on the standard applied, the pilot.

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

[0344] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0345] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first or second element does not imply that only two elements can be used there, or that the first element must in some form precede the second element.

[0346] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0347] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0348] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include situations where judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), or ascertaining are considered as "determining" or "determining." Furthermore, "determining" or "determining" may include situations where receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory) are considered as "determining" or "determining." Additionally, "determining" or "determining" may include situations where resolving, selecting, choosing, establishing, or comparing are considered as "determining" or "determining." That is, "judgment" and "decision" can include situations where certain actions are regarded as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0349] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0350] Figure 8 An example of the structure of vehicle 2001 is shown. For example... Figure 8 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear 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.

[0351] The drive unit 2002 may consist of, for example, an engine, a motor, or a hybrid power system of an engine and a motor.

[0352] The steering unit 2003 includes at least a steering wheel (also called a steering wheel) 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.

[0353] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2027 of the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

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

[0355] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of vehicle 1.

[0356] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

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

[0358] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0359] The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. Additionally, the communication module 2013 also transmits the following signals input to the electronic control unit 2010 via wireless communication to external devices: the front and rear wheel speed signals obtained by the speed sensor 2022; the front and rear wheel air pressure signals obtained by the air pressure sensor 2023; the vehicle speed signal obtained by the vehicle speed sensor 2024; the acceleration signal obtained by the acceleration sensor 2025; the accelerator pedal depressor signal obtained by the accelerator pedal sensor 2029; the brake pedal depressor signal obtained by the brake pedal sensor 2026; the gear shift lever operation signal obtained by the gear shift lever sensor 2027; and the detection signals for detecting obstacles, vehicles, pedestrians, etc., obtained by the object detection sensor 2028.

[0360] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 provided by the vehicle. Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, and sensors 2021-2028 provided by the vehicle 2001 based on the information stored in the memory 2032.

[0361] (Postscript)

[0362] The above disclosure can also be expressed as follows. A first feature is 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 wireless base station. The receiving unit receives the setting information in a sub-band full-duplex mode and in a non-sub-band full-duplex mode, wherein the sub-band full-duplex mode refers to a mode in which uplink sub-bands and downlink sub-bands are non-overlapping in the frequency direction within a predetermined time period based on time-division duplex.

[0363] The second feature is that, in the first feature, the control unit sets up the uplink control channel for sending an affirmative response to an automatic retransmission request based on the setting information.

[0364] The third feature is that, in the first or second feature, the control unit sets up the uplink control channel for sending scheduling requests based on the setting information.

[0365] The fourth feature is that, among the first to third features, the control unit sets up the uplink control channel for transmitting channel state information based on the setting information.

[0366] Label Explanation

[0367] 10 Wireless Communication Systems

[0368] 20 NG-RAN

[0369] 100 gNB

[0370] 200 UE

[0371] 210 Wireless Signal Transceiver Unit

[0372] 220 Enlarged Section

[0373] 230 Modulation and Demodulation Section

[0374] 240 Control Signal & Reference Signal Processing Unit

[0375] 250 Encoding / Decoding Unit

[0376] 260 Data Transceiver Department

[0377] 270 Control Department

[0378] 1001 processor

[0379] 1002 Memory

[0380] 1003 Storage device

[0381] 1004 Communication device

[0382] 1005 Input Device

[0383] 1006 Output Device

[0384] 1007 bus

[0385] Vehicle 2001

[0386] 2002 Drive Unit

[0387] 2003 Steering Unit

[0388] 2004 Accelerator Pedal

[0389] 2005 Brake Pedal

[0390] 2006 gearshift lever

[0391] Front wheels around 2007

[0392] 2008 rear wheels (left and right)

[0393] 2009 axle

[0394] 2010 Electronic Control Department

[0395] 2012 Information Service Department

[0396] 2013 Communication Module

[0397] 2021 Current Sensor

[0398] 2022 Speed ​​Sensor

[0399] 2023 Barometric Pressure Sensor

[0400] 2024 vehicle speed sensor

[0401] 2025 Accelerometer

[0402] 2026 Brake Pedal Sensor

[0403] 2027 Gearshift sensor

[0404] 2028 Object Detection Sensor

[0405] 2029 Accelerator Pedal Sensor

[0406] 2030 Driver Assistance Systems Department

[0407] 2031 microprocessor

[0408] 2032 Memory (ROM, RAM)

[0409] 2033 Communication Port

Claims

1. A terminal, comprising: The receiving unit receives the setting information of the uplink control channel; The control unit configures the uplink control channel based on the configuration information; and The transmitting unit sends the uplink control channel to the wireless base station. The receiving unit receives the setting information in both the case of using subband full-duplex mode and the case of not using subband full-duplex mode, wherein... The sub-band full-duplex mode refers to the method in which uplink sub-bands and downlink sub-bands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex.

2. The terminal according to claim 1, wherein, Based on the setting information, the control unit sets up the uplink control channel for sending a positive response to the automatic retransmission request.

3. The terminal according to claim 1, wherein, Based on the setting information, the control unit sets up the uplink control channel for sending scheduling requests.

4. The terminal according to claim 1, wherein, Based on the setting information, the control unit sets up the uplink control channel for transmitting channel status information.

5. A terminal, comprising: The transmitting unit repeatedly transmits uplink control channels to the wireless base station; and The control unit envisions as associating the uplink control channel resources in the case of utilizing subband full-duplex mode with the uplink control channel in the case of not utilizing the subband full-duplex mode, wherein... The sub-band full-duplex mode refers to the method in which uplink sub-bands and downlink sub-bands are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex.

Images