Terminal, base station, wireless communication system, and wireless communication method

Abstract

A terminal includes a communication section that performs communication of uplink signals and downlink signals within a time division duplex band, and a control section that performs an action related to transmission of an uplink signal in a subband of the uplink signal in which a synchronization signal from an additional cell is set.

Description

Technical Field

[0001] This disclosure relates to terminals, base stations, wireless communication systems, and wireless communication methods in next-generation mobile communication systems. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) 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, 3GPP Release 18 investigated an extension of duplexing methods (Non-Patent Document 1). Specifically, a new duplexing method, 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. SBFD can also be replaced by XDD (Cross Division Duplex).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: “New SI: Study on evolution of NR duplex operation”, RP-213591, 3GPP TSG RAN#94-e, 3GPP, December 2021 Summary of the Invention

[0007] Additionally, in 3GPP Release 16, the Carrier Aggregation (CA) of TDD defines an information element (directionalCollisionHandling-r16) that specifies whether to use DL / UL-related collision handling in half-duplex communication between the reference cell and other cells.

[0008] Similarly, in 3GPP Release 17, under DC (Dual Connectivity), an information element (directionalCollisionHandling-DC-r17) is defined that specifies whether to use DL / UL related collision handling in half-duplex communication between the reference cell and other cells.

[0009] Against this backdrop, the inventors conducted in-depth research and found that, in the case of setting up two or more serving cells that include serving cells that operate in the SBFD manner, and in the case of setting up the application of Directional Collision Handling, there is a need to clarify the actions related to the terminal that identifies SBFD (SBFD-aware UE).

[0010] Therefore, this disclosure was made to solve the above-mentioned problems, and its purpose is to provide a terminal, base station, wireless communication system and wireless communication method that, taking into account the situation where application directional collision handling can be set, can make the actions related to SBFD-aware UE clear.

[0011] The disclosed method is a terminal comprising: a communication unit that communicates with a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and a control unit that, in the case where two or more serving cells include the duplex cell, considers whether to configure a response to conflicts related to the uplink and downlink signals.

[0012] The disclosed method is a base station comprising: a communication unit that communicates with a terminal via a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and a control unit that, when two or more serving cells include the duplex cell, considers whether to configure a response to conflicts related to the uplink and downlink signals.

[0013] The disclosed method is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises: a communication unit that communicates with a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and a control unit that, in the case where two or more serving cells include the duplex cell, considers whether to configure a response to conflicts related to the uplink and downlink signals.

[0014] The disclosed method is a wireless communication method comprising the following steps: Step A, communicating with a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and Step B, in the case where two or more serving cells include the duplex cell, considering whether to configure a response to conflicts related to the uplink and downlink signals. Attached Figure Description

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

[0016] Figure 2 This is a diagram showing the frequency range used in the wireless communication system 10.

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

[0018] Figure 4 This is the function block structure diagram of UE200.

[0019] Figure 5 This is the function block structure diagram of gNB100.

[0020] Figure 6 It is a diagram used to illustrate the topic.

[0021] Figure 7 It is a diagram used to illustrate the topic.

[0022] Figure 8 This is a diagram used to illustrate action example 3.

[0023] Figure 9 This is a diagram used to illustrate action example 4.

[0024] Figure 10 This is a diagram used to illustrate action example 4.

[0025] Figure 11 This is a diagram used to illustrate action example 5.

[0026] Figure 12 This is a diagram used to illustrate action example 5.

[0027] Figure 13 This is a diagram used to illustrate action example 6.

[0028] Figure 14 This is a diagram used to illustrate action example 6.

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

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

[0031] The embodiments are described below based on the accompanying drawings. Furthermore, identical or similar labels are used to refer to the same functions and structures, and their descriptions are omitted where appropriate.

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

[0033] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10 according to the implementation method. The wireless communication system 10 is a wireless communication system that follows 5G New Radio (NR) and includes a next-generation radio access network 20 (NG-RAN20) and a terminal 200 (UE (User Equipment) 200).

[0034] Alternatively, the wireless communication system 10 can also be a wireless communication system that follows a protocol known as Beyond 5G, 5G Evolution, or 6G.

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

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

[0037] The gNB100 is a 5G-compliant wireless base station that performs 5G-compliant wireless communication with the UE200. The gNB100 and UE200 can support massive MIMO (Multiple-Input Multiple-Output) which generates more directional beams BM by controlling the wireless signals transmitted from multiple antenna elements, carrier aggregation (CA) which uses multiple component carriers (CC), and dual connectivity (DC) which enables simultaneous communication between the UE and two NG-RAN nodes on more than two transport blocks.

[0038] In addition, the wireless communication system 10 supports multiple frequency ranges (FRs). Figure 2 The frequency range used in the wireless communication system 10 is shown.

[0039] First, the wireless communication system 10 can also support... Figure 2 The multiple frequency ranges (FRs) are shown. For example, wireless communication system 10 supports FR1, FR2-1, and FR2-2. The frequency bands of each FR are as follows.

[0040] FR1: 410 MHz~7.125 GHz

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

[0042] FR2-2: Over 52.6GHz to 71GHz

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

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

[0045] Furthermore, the wireless communication system 10 can also support frequency bands higher than FR2. Specifically, the wireless communication system 10 can also support frequency bands exceeding 52.6 GHz, up to 71 GHz or 114.25 GHz.

[0046] Second, the wireless communication system 10 can also support Figure 3 The wireless frames, subframes, and time slots shown are illustrated.

[0047] like Figure 3 As shown, one time slot consists of 14 symbols. The larger (wider) the SCS, the shorter the symbol period (and time slot period). In addition to 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz, SCS can also be 480kHz, 960kHz, etc.

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

[0049] in addition, Figure 3 The time direction (t) shown can also be referred to as the time domain, symbol period, or symbol time, etc. Furthermore, the frequency direction can also be referred to as the frequency domain, resource block, subcarrier, or bandwidth part (BWP), etc.

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

[0051] Next, the functional block structure of the wireless communication system 10 will be explained.

[0052] First, the functional block structure of UE200 will be explained.

[0053] Figure 4 This is the function block structure diagram of UE200. (Example) Figure 4 As shown, the UE200 includes a wireless signal transceiver unit 210, an amplifier unit 220, a modem unit 230, and a control signal transceiver unit 20. Reference signal processing unit 240, encoding / decoding unit 250, data transceiver unit 260 and control unit 270.

[0054] The radio transceiver unit 210 transmits and receives radio signals conforming to NR. The radio transceiver unit 210 supports massive MIMO, CA using multiple CCs, and DC for simultaneous communication between the UE and each of the two NG-RAN nodes.

[0055] In this embodiment, the wireless transceiver unit 210 is configured as a communication unit for performing communication in a duplex cell that is capable of simultaneously communicating uplink signals (hereinafter, UL signals) and downlink signals (hereinafter, DL signals) within a time-division duplex frequency band. Furthermore, this new duplex mode capable of simultaneously communicating UL signals and DL signals can also be called SBFD (Sub-Band non-overlapping Full Duplex). SBFD can also be replaced with XDD (Cross Division Duplex).

[0056] Simultaneous communication of UL and DL signals can also be performed within a specific time resource. A specific time resource is a time resource to which SBFD can be applied. A specific time resource can be replaced by an SBFD resource (SBFD symbol / time slot) that is quasi-statically or dynamically configured in the time direction (or time domain). A specific time resource can also be replaced by a resource that simultaneously has (multiple) UL subbands and (multiple) DL subbands configured quasi-statically or dynamically in the time direction (or time domain).

[0057] A duplex cell can also be called an SBFD operation cell. An additional cell can also be called an Additional PCI (Physical Cell Identifier) ​​cell. An Additional PCI cell can contain SBFD operation cells or cells that do not operate in SBFD mode (legacy cells).

[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 or other gNB). 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 demodulation reference signal (DMRS) and phase tracking reference signal (PTRS).

[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] In addition, channels include control channels and data channels. 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 physical broadcast channel (PBCH), etc.

[0066] In addition, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via a data channel. A data channel can also be replaced by a shared channel.

[0067] Here, the control signal / reference signal processing unit 240 can receive downlink control information (DCI). The DCI, as an existing field, includes fields storing DCI formats, carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), RV (Redundancy Version), etc.

[0068] The DCI format field stores information elements specifying the DCI format. The CI field stores information elements specifying the CC for which the DCI is applied. The BWP indicator field stores information elements specifying the BWP for which the DCI is applied. The BWP that can be specified through the BWP indicator is set by the information element (BandwidthPart-Config) contained in the RRC message. The FDRA field stores information elements specifying the frequency domain resources for which the DCI is applied. Frequency domain resources are determined by the value stored in the FDRA field and the information element (RA Type) contained in the RRC message. The TDRA field stores information elements specifying the time domain resources for which the DCI is applied. Time domain resources are determined by the value stored in the TDRA field and the information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) contained in the RRC message. Time domain resources can be determined by the value stored in the TDRA field and the default table. The MCS field stores information elements specifying the MCS for which the DCI is applied. MCS is determined by the value stored in the MCS field and the MCS table. The MCS table can be specified via RRC messages or determined via RNTI scrambling. The value stored in the HPN field is an information element specifying the HARQProcess of the applied DCI. The value stored in the NDI field is an information element used to determine whether the data used in the applied DCI is initial data. The value stored in the RV field is an information element specifying the redundancy of the data used in the applied DCI.

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

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

[0071] 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 in 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 HARQ (Hybrid Automatic Repeat Request).

[0072] The control unit 270 controls the functional blocks constituting the UE 200. In an embodiment, the control unit 270 is configured to handle conflicts related to UL signals and DL signals when two or more serving cells include dual-signal mode (SBFD) operation cells. This handling of conflicts related to UL signals and DL signals can also be called directional collision handling. Directional collision handling can be the operation of half-duplex communication between the reference cell and other cells in TDD's CA (Carrier Aggregation), or it can be the operation of half-duplex communication between the reference cell and other cells in DC (Dual Connectivity).

[0073] Second, the functional block structure of gNB100 will be explained.

[0074] Figure 5 This is the function block structure diagram of gNB100. (Example) Figure 5 As shown, gNB100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0075] The receiver 110 receives various signals from the UE200. The receiver 110 can receive UL signals via PUCCH or PUSCH.

[0076] The transmitting unit 120 transmits various signals to the UE 200. The transmitting unit 120 can also transmit DL signals via PDCCH or PDSCH.

[0077] In the embodiment, the receiving unit 110 and the transmitting unit 120 constitute a communication unit that communicates with the UE200 via a duplex operation cell (SBFD) capable of simultaneously communicating UL signals and DL signals within the TDD band.

[0078] The control unit 130 controls the gNB 100. In this embodiment, the control unit 130 is configured to consider whether to set up directional collision handling when two or more serving cells include a duplex mode cell (SBFD operation cell).

[0079] (3) Problem

[0080] First, explain the resource allocation of gNB100.

[0081] In versions 15 / 16 / 17, such as Figure 6 As shown in the previous paragraph, the gNB100 sets or specifies "DL", "F (Flexible)" or "UL" for each symbol. Simultaneous communication of DL and UL signals is not allowed within a given time resource.

[0082] On the other hand, in version 18, such as Figure 6 As shown in the next paragraph, the gNB100 sets or designates "DL" for symbols of a certain frequency resource (e.g., (multiple) subbands) and sets or designates "UL" for symbols of other frequency resources (e.g., (multiple) subbands). Simultaneous communication of DL and UL signals is allowed within a certain time resource. This method can also be called SBFD (Sub-Band non-overlapping Full Duplex).

[0083] Second, directional collision handling will be explained. As mentioned above, directional collision handling refers to the actions taken in a reference cell to communicate with other cells in a half-duplex environment (CA) or control cell (DC). In a CA, the information element that sets directional collision handling can also be called directionalCollisionHandling-r16. In a DC, the information element that sets directional collision handling can also be called directionalCollisionHandling-DC-r17. Hereinafter, the information element that sets directional collision handling will sometimes be simply referred to as directionalCollisionHandling. In directional collision handling, collisions related to DL / UL are handled through the steps shown below.

[0084] In the first step, if UE200 has set two or more serving cells and directional CollisionHandling is set in at least one of the two or more serving cells, it determines the set of cells to be considered in the decision of the reference cell (candidate reference cells).

[0085] In the second step, UE200 determines the reference cell from the set of cells. For example, UE200 will determine the cell with the smallest cell index as the reference cell.

[0086] In the third step, UE200 determines how to handle conflicts corresponding to symbols from the reference cell and symbols from other cells (the Directional Collision Handling method).

[0087] Against this backdrop, the inventors conducted in-depth research and, focusing on the scenario of being able to set up two or more serving cells that operate in the manner of SBFD, discovered the following research findings.

[0088] First, when two or more serving cells contain SBFD operation cells, the existence of SBFD-aware UEs needs to be considered. Regarding the inclusion of SBFD operation cells in two or more serving cells, it is necessary to investigate whether restrictions are required from the UE200's perspective. For example, it is necessary to investigate whether it is permissible for two or more serving cells to include SBFD operation cells, and whether SBFD operation cells can be PCell / PSCell / SCell, etc.

[0089] Second, when UE200 specifies two or more serving cells, including the serving cell operating in SBFD mode, the actions related to directional collision handling are unclear. For example, ... Figure 7 As shown, in addition to D in CC#3 and U in CC#2, we also envision SBFD in CC#1. In this case, it is necessary to investigate whether to consider SBFD operation cell (CC#1) or SBFD symbol of SBFD operation cell (CC#1), etc.

[0090] As described above, the inventors conducted in-depth research and found that, in the case of setting up two or more serving cells that include serving cells that operate in the SBFD manner, and when Directional collision handling is set up, there is a need to clarify the actions related to the terminal that identifies SBFD (SBFD-aware UE).

[0091] (4) Definition of terms

[0092] The following is an explanation of the definitions of terms related to SBFD.

[0093] An SBFD operation cell is a cell that operates in SBFD mode when it is positioned in the time or frequency direction of an SBFD sub-band within the serving cell.

[0094] A non-SBFD operation cell is a cell in which no SBFD subband is configured in the serving cell.

[0095] Half-duplex CA serving cells are a set of directionalCollisionHandling-r16 cells with an "enabled" value provided to the UE200 when the UE200 supports half-duplex communication in the CA. Variations of Half-duplex CA serving cells as shown below can also be conceived.

[0096] In Variation 1, as an additional condition, a new UE capability can also be defined for UE200 to support directional collision handling for half-duplex communication in CA in the case of including an SBFD operation cell. Upon reporting the new UE capability, directional collision handling for half-duplex communication in CA can also be performed in the case of including an SBFD operation cell.

[0097] In Variation 2, when an SBFD operation cell is included, new higher-level parameters (e.g., directionalCollisionHandling-SBFD-CA-r19) for directional collision handling in half-duplex communication applied in CA can be imported. These new higher-level parameters can be parameters sent from the SBFD operation cell. In such a case, directionalCollisionHandling-r16 with an "enabled" value can be provided to the UE200 from a non-SBFD operation cell, and directionalCollisionHandling-SBFD-CA-r19 with an "enabled" value can be provided to the UE200 from an SBFD operation cell.

[0098] Semi-static DL slots / symbols are DL slots / symbols set by higher-level parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0099] Semi-static UL slots / symbols are UL slots / symbols set by higher-level parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0100] Semi-static flexible slot / symbol is a slot / symbol that is set to flexible via higher-level parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0101] Dynamic DL slot / symbol is a slot / symbol that is set to be flexible by a higher-level parameter (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is a slot / symbol that is specified as DL by DCI format 2_0.

[0102] Dynamic UL slot / symbol is a slot / symbol that is set to be flexible by the high-level parameter (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is a slot / symbol that is specified as UL by DCI format 2_0.

[0103] Dynamic flexible slot / symbol is a slot / symbol that is set to be flexible through high-level parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is specified as flexible through DCI format 2_0.

[0104] The SBFD DL symbol is a symbol that is set to DL by the high-level parameter (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). It is a symbol that sets the UL sub-band.

[0105] The SBFD flexible symbol is a symbol that is set to flexible by a higher-level parameter (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). It is a symbol that sets the UL subband in this symbol.

[0106] (5) Action Examples

[0107] To address the aforementioned issues, the following action examples can also be specified. Specifically, this mainly illustrates the situation where two or more serving cells, such as CA or DC, are communicating with UE200.

[0108] (5.1) Example of action 1

[0109] In Action Example 1, we will explain whether it is permissible for more than two serving cells to contain SBFD operation cells. As Action Example 1, consider the options shown below.

[0110] In option 1-1, UE200 supports two or more serving cells that include at least one SBFD operation cell.

[0111] Specifically, UE200 envisions the configuration of two or more serving cells, including those configured at time and frequency locations below X in the SBFD sub-band. Hereinafter, the serving cell configured at the time and frequency locations in the SBFD sub-band is referred to as an SBFD operation cell.

[0112] The maximum number of SBFD operation cells can be X. The value of X can be defined or reported separately or individually in the case where the serving cell is included in a PUCCH group and in the case where the serving cell crosses a PUCCH group. The value of X can be 1 or a number greater than 1. The value of X can be predetermined in the wireless communication system 10 or can be reported by the UE capability.

[0113] If there are more than two serving cells in option 1-1, at least one of PCell, PSCell and SCell can be set as SBFD operation cell in UE200.

[0114] In option 1-1, when there are two or more serving cells that include SBFD operation cells, the same parameters (numerology) can be envisioned for the SBFD operation cells.

[0115] In options 1-2, UE200 does not support more than two serving cells containing at least one SBFD operation cell.

[0116] Specifically, UE200 does not envision the setting of more than two serving cells, including the serving cell set at the time and frequency location of the SBFD subband.

[0117] In options 1-2, when there are more than two serving cells in UE200, the time and frequency location of the SBFD subband (in the cell group of the SBFD operation cell) are not set in any serving cell.

[0118] In action examples 2 and 3 described below, option 1-1 can also be a prerequisite.

[0119] (5.2) Action Example 2

[0120] In Action Example 2, we will explain the directional collision handling of half-duplex communication in the case where two or more serving cells contain at least one SBFD operating cell. As Action Example 2, the following options can be considered.

[0121] In option 2-1, UE200 can also be envisioned as not setting directional collision handling in any of two or more serving cells.

[0122] Specifically, when two or more serving cells contain at least one SBFD operation cell, higher-layer parameters (e.g., directionalCollisionHandling-r16) are not set in any serving cell.

[0123] In other words, when UE200 has at least one SBFD operation cell in two or more serving cells, it does not assume the setting of higher-layer parameters (e.g., directional Collision Handling-r16) in any one of the serving cells.

[0124] Directional collision handling is not assumed between serving cells where UE200 cannot simultaneously perform transmission and reception.

[0125] According to option 2-1, there is no need to change the existing Directional collisionhandling applied to CA, etc.

[0126] In option 2-2, UE200 can be envisioned as not setting directional collision handling in SBFD operation cells included in more than two serving cells.

[0127] Specifically, when two or more serving cells contain at least one SBFD operation cell, higher-layer parameters (e.g., directionalCollisionHandling-r16) are not set in the SBFD operation cell.

[0128] In other words, when UE200 has more than two serving cells containing at least one SBFD operation cell, the setting of higher-layer parameters (e.g., directionalCollisionHandling-r16) is not assumed in the SBFD operation cell.

[0129] After performing directional collision handling on a non-SBFD operation cell, UE200 does not assume directional collision handling between serving cells where UE200 cannot simultaneously perform transmission and reception.

[0130] UE200 may also not always assume the setting of higher-level parameters (e.g., directionalCollisionHandling-r16) in the SBFD operation cell. For example, if a higher-level parameter (e.g., directionalCollisionHandling-r16) is set in the SBFD operation cell, UE200 may ignore the higher-level parameter (e.g., directionalCollisionHandling-r16).

[0131] In option 2-2, if the Directional Collision Handling setting is not executed or assumed in the SBFD operating cell, the Directional Collision Handling setting may also not be executed or assumed in any cell within the same frequency band as the SBFD operating cell. Similarly, if the Directional Collision Handling setting is not executed or assumed in the SBFD operating cell, the Directional Collision Handling setting may also not be executed or assumed in any cell within the same cell group as the SBFD operating cell.

[0132] In option 2-2, UE200 may also not always assume the setting of higher-layer parameters (e.g., directional CollisionHandling-r16) in any cell within the same frequency band as the SBFD operation cell. UE200 may also not always assume the setting of higher-layer parameters (e.g., directional CollisionHandling-r16) in any cell within the same cell group as the SBFD operation cell. For example, if UE200 has set higher-layer parameters (e.g., directional CollisionHandling-r16) in any cell within the same frequency band or cell group as the SBFD operation cell, UE200 may ignore the higher-layer parameters (e.g., directional CollisionHandling-r16).

[0133] According to option 2-2, there is no need to change the existing Directional collisionhandling applied to CA, etc.

[0134] In options 2-3, UE200 can be envisioned as setting up directional collision handling in SBFD operation cells included in more than two serving cells.

[0135] Specifically, when two or more serving cells contain at least one SBFD operation cell, higher-layer parameters (e.g., directionalCollisionHandling-r16) are set for the SBFD operation cell.

[0136] In other words, when UE200 has more than two serving cells containing at least one SBFD operation cell, it envisions the setting of higher-layer parameters (e.g., directionalCollisionHandling-r16) in the SBFD operation cell.

[0137] In options 2-3, new higher-layer parameters can be imported (e.g., directionalCollisionHandling-SBFD-CA-r19). These new higher-layer parameters can be set in the SBFD operating cell or any other serving cell.

[0138] For example, if no new higher-layer parameters (e.g., directionalCollisionHandling-SBFD-CA-r19) are set for the SBFD operation cell, but existing higher-layer parameters (e.g., directionalCollisionHandling-r16) are set for the set of other cells that do not have SBFD operation, the UE200 can apply directional collisionhandling to the set of non-SBFD operation cells (other cells).

[0139] For example, if a new higher-layer parameter (e.g., directionalCollisionHandling-SBFD-CA-r19) is set for the SBFD operation cell, and existing higher-layer parameters (e.g., directionalCollisionHandling-r16) are set for the set of other cells that do not accompany SBFD operation, the UE200 can apply directional collision handling to both the SBFD operation cell and the non-SBFD operation cell.

[0140] For example, if a new higher-layer parameter (e.g., directionalCollisionHandling-SBFD-CA-r19) is set for the set of cells that are not involved in SBFD operation, and an existing higher-layer parameter (e.g., directionalCollisionHandling-r16) is set for the set of other cells that are not involved in SBFD operation, the UE200 can perform the actions shown below.

[0141] In step 1, UE200 applies directional collision handling to the set of non-SBFD operation cells (other cells) based on existing higher-layer parameters. As a result, the directional collision handling of half-duplex TDD CA cells that do not involve SBFD operation is aligned.

[0142] In step 2, UE200 applies directional collision handling to the set of SBFD operating cells based on new higher-layer parameters. As a result, the directional alignment of half-duplex TDD CA cells accompanying the SBFD operation is achieved.

[0143] In step 3, UE200 applies directional collision handling between the set of non-SBFD operation cells and the set of SBFD operation cells. In this case, consider the options shown below.

[0144] In option a, UE200 can always prioritize the direction of the SBFD operation cell. Alternatively, UE200 can always prioritize the direction of the Non-SBFD operation cell.

[0145] In option b, UE200 can treat the SBFD operating cell from step 2 as a reference cell. The method for treating the SBFD operating cell as a reference cell can be the method described in Example 4 below, or an existing method. For example, if the reference cell's symbol is an SBFD symbol, the method described in Example 4 below can be applied; if the reference cell's symbol is a non-SBFD symbol, an existing method can be applied.

[0146] In option c, UE200 may treat the Non-SBFD operating cell from step 1 as a reference cell. The method for treating the Non-SBFD operating cell as a reference cell may be the method described in Action Example 5 below, or an existing method. For example, the method described in Action Example 5 below may be applied when the symbols of other cells are SBFD symbols, and an existing method may be applied when the symbols of other cells are non-SBFD symbols.

[0147] (5.3) Action Example 3

[0148] In Action Example 3, the scenario where two or more serving cells contain at least one SBFD operation cell is described, and directional collision handling for half-duplex communication is configured. That is, Action Example 3 can also be considered as an action example based on options 2-3 of Action Example 2 above.

[0149] First, an example of an action related to the first step of deciding the set of cells to be considered in the decision of reference cells (candidate reference cells) is described. As such an example of an action, consider the options shown below.

[0150] In option 3-1, UE200 does not consider SBFD symbols and non-SBFD symbols, and determines the candidate reference cell according to the existing rules.

[0151] Specifically, UE200 determines the candidate reference cell according to existing rules. For example, UE200 may process SBFD symbols and DL symbols without distinguishing between them.

[0152] According to option 3-1, no changes are needed to the existing rules. However, the existing rules are based on semi-static settings (e.g., semi-static SFI (Slot Format Indicator), RRC configured DL / UL reception / transmission). Therefore, flexible symbols that are not accompanied by semi-static settings are not considered in the decision of candidate reference cells.

[0153] In option 3-2, UE200 determines the candidate reference cell without considering the SBFD operation cell.

[0154] Specifically, after excluding SBFD operation cells, UE200 determines the candidate reference cell from the non-SBFD operation cells according to existing rules. That is, it determines the candidate reference cell regardless of whether the symbol is an SBFD symbol or a non-SBFD symbol of the SBFD operation cell.

[0155] Option 3-2 selects a candidate reference cell from the non-SBFD operating cells, thus allowing the reuse of existing rules. However, since the SBFD operating cell will not become a reference cell, its priority is reduced in directional collision handling.

[0156] In option 3-3, UE200 determines the candidate reference cell without considering SBFD symbols.

[0157] Specifically, UE200 determines the candidate reference cells for the symbols. In this case, the symbols can be as follows.

[0158] If no SBFD UL subband is specified in the symbol, the symbol is either a downlink or an uplink, as specified by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0159] When the symbol is flexible and no SBFD UL subband is set in the symbol, and the UE200 transmits SRS, PUCCH, PUSCH or PRACH in the symbol, the symbol is an uplink.

[0160] When the symbol is flexible and no SBFD UL subband is set in the symbol, and the UE200 receives PDCCH, PDSCH or CSI-RS in the symbol, the symbol is a downlink.

[0161] In option 3-3, if the symbol is an SBFD symbol of an SBFD operation cell, the SBFD operation cell is not considered as a candidate for reference cell. If the symbol is a non-SBFD symbol of an SBFD operation cell, the SBFD operation cell is considered as a candidate for reference cell.

[0162] According to option 3-3, candidate reference cells are selected from cells with non-SBFD symbols, thus allowing the reuse of existing rules. Since SBFD operation cells with SBFD symbols will not become reference cells, their priority is reduced in directional collision handling.

[0163] In options 3-4, UE200 determines the candidate reference cell by either not considering SBFD symbols or considering SBFD symbols.

[0164] Specifically, UE200 determines whether to consider SBFD symbols in the selection of reference cell candidates based on whether PDCCH / PDSCH / CSI-RS is set by the higher layer (in the DL subband) and whether PUCCH / PUSCH / PRACH / SRS is set by the higher layer (in the UL subband).

[0165] For example, when the symbol is an SBFD symbol of the serving cell, in one or more of the cases shown below, the serving cell is considered in the decision of the candidate reference cell.

[0166] like Figure 8 As shown, Case-a is the case where UE200 transmits PUCCH / PUSCH / PRACH / SRS via symbols (within the UL subband).

[0167] like Figure 8 As shown, Case-b is the case where UE200 receives PDCCH / PDSCH / CSI-RS through symbols (within the DL subband).

[0168] like Figure 8 As shown, Case-c is the case where UE200 does not transmit PUCCH / PUSCH / PRACH / SRS through symbols (within the UL subband) and does not receive PDCCH / PDSCH / CSI-RS through symbols (within the DL subband).

[0169] like Figure 8 As shown, Case-d is the case where UE200 simultaneously transmits PUCCH / PUSCH / PRACH / SRS via symbols (within the UL subband) and receives PDCCH / PDSCH / CSI-RS via symbols (within the DL subband).

[0170] The application scenario can be predetermined in the wireless communication system 10 or set via RRC.

[0171] For example, regarding Case-a and Case-b, the SBFD operation cell of the SBFD symbol can be considered as a candidate reference cell. Regarding Case-a, the symbol can be considered as a (RRC) UL symbol. The same rules as existing rules such as "the symbol is flexible, and the UE200 transmits SRS, PUCCH, PUSCH, or PRACH in the symbol" can be applied to the SBFD symbol. Regarding Case-b, the symbol can be considered as a (RRC) DL symbol. The same rules as existing rules such as "the symbol is flexible, and the UE200 receives PDCCH, PDSCH, or CSI-RS in the symbol" can be applied to the SBFD symbol.

[0172] For example, regarding Case-c, the SBFD operation cell can also be disregarded as a candidate reference cell.

[0173] For example, regarding Case-d, the SBFD operation cell can be considered as a candidate for the reference cell, or it can be disregarded. For instance, in the wireless communication system 10, if it is determined that the UL / DL transmission / reception (defined by higher layers) of the (UL / DL subband) always takes precedence over the DL / UL transmission / reception (defined by higher layers) of the (DL / UL subband), the SBFD operation cell can be considered as a candidate for the reference cell, or the symbol can be assumed to be the (RRC) UL / DL symbol.

[0174] In options 3-4, different cases can be applied to the SBFD DL symbol and the SBFD Flexible symbol. For example, regarding the SBFD DL symbol, in Case-a to Case-d, the SBFD operation cell can be considered as a candidate for the reference cell. Regarding the SBFD Flexible symbol, in Case-a and Case-b, the SBFD operation cell can be considered as a candidate for the reference cell, while in Case-c and Case-d, the SBFD operation cell may not be considered as a candidate for the reference cell.

[0175] Second, an example of an action related to the first step of determining a reference cell from the candidates for reference cells will be described. Consider the following Alt as an example of such an action.

[0176] In Alt.3-a, the reference cell can be the cell with the smallest cell index among the candidates for reference cells. Alt.3-1 is the same as the existing rules.

[0177] In Alt.3-b, the reference cell can be a high-priority SBFD operation cell. For example, if there is at least one SBFD operation cell among the candidates for reference cells, the reference cell can be the cell with the smallest cell index among at least one SBFD operation cell. If there is no SBFD operation cell among the candidates for reference cells, the reference cell can be the cell with the smallest cell index among the candidates for reference cells.

[0178] In Alt.3-c, the reference cell can be a high-priority Non-SBFD operation cell. For example, if at least one Non-SBFD operation cell exists among the candidates for reference cells, the reference cell can be the cell with the smallest cell index among those at least one Non-SBFD operation cell. If no Non-SBFD operation cell exists among the candidates for reference cells, the reference cell can be the cell with the smallest cell index among those candidates.

[0179] In Alt.3-d, the reference cell can be an SBFD operation cell with a high-priority SBFD symbol. For example, if there is at least one SBFD operation cell with an SBFD symbol among the candidate reference cells, it can be the cell with the smallest cell index among those SBFD operation cells. If there is no SBFD operation cell with an SBFD symbol among the candidate reference cells, the reference cell can be the cell with the smallest cell index among the candidate reference cells.

[0180] In Alt.3-e, the reference cell can be a high-priority non-SBFD operation cell with non-SBFD symbols. For example, if at least one non-SBFD operation cell with non-SBFD symbols exists among the candidate reference cells, it can be the cell with the smallest cell index among those at least one non-SBFD operation cell. If no at least one non-SBFD operation cell with non-SBFD symbols exists among the candidate reference cells, the reference cell can be the cell with the smallest cell index among the candidate reference cells.

[0181] As described above, in Action Example 3, UE200, assuming the application of Directional Collision Handling in the SBFD operating cell, determines the steps for determining the reference cell based on conditions. The steps for determining the reference cell may include at least one of the first and second steps described above. The conditions are those defined by the options and Alt.

[0182] (5.4) Action Example 4

[0183] In Action Example 4, the scenario of configuring Directional Collision Handling for half-duplex communication is described when two or more serving cells contain at least one SBFD operation cell. That is, Action Example 4 can also be considered as an action example based on options 2-3 of Action Example 2 above.

[0184] Action Example 4 primarily explains the third step of determining the handling of conflicts corresponding to symbols from the reference cell and other cells (the Directional Collision Handling method). Action Example 4 explains the case where the reference cell's symbols are SBFD symbols, and the symbols from other cells are non-SBFD symbols.

[0185] In Action Example 4, the method of Directional Collision Handling can be determined based on the SBFD symbols of the reference cell (SBFD operation cell) according to the following viewpoints.

[0186] Case 1 is the case where UE200 receives PDCCH, PDSCH or CSI-RS in SBFD symbols within the DL subband.

[0187] Case 2 is the case where UE200 transmits SRS, PUCCH, PUSCH or PRACH in SBFD symbols within the UL subband.

[0188] Case 3 is a scenario where UE200 does not receive PDCCH, PDSCH, or CSI-RS in the SBFD symbols in the DL subband, and does not transmit SRS, PUCCH, PUSCH, or PRACH in the SBFD symbols in the UL subband.

[0189] Case 4 is a scenario where UE200 receives PDCCH, PDSCH, or CSI-RS in SBFD symbols within the DL subband, and transmits SRS, PUCCH, PUSCH, or PRACH in SBFD symbols within the UL subband.

[0190] Specific methods of Directional Collision Handling include Figure 9 and Figure 10 As shown.

[0191] like Figure 9 As shown, as Case 1, six scenarios were envisioned based on the types of symbols in other cells.

[0192] In Case 1-1, the symbols of other cells are Semi-SFI DL. In this case, no collision will occur.

[0193] In Case 1-2, the symbols of other cells are Semi-SFI UL. In this case, UE200 may also assume the symbols of other cells to be flexible (option 1-2a), or may not receive PDCCH / PDSCH / CSI-RS in the reference cell (option 1-2b), or may not assume Case 1-2 (option 1-2c).

[0194] In Cases 1-3, the symbols of other cells are configured with Semi-SFI DL for DL ​​reception via RRC. In this case, no collision will occur.

[0195] In Cases 1-4, the symbols of other cells are Semi-SFI ULs transmitted via RRC-configured ULs. In this case, UE200 may also choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 1-4a), or not to receive PDCCH / PDSCH / CSI-RS in the reference cell (Option 1-4b), or may disregard Case 1-4 (Option 1-4c).

[0196] In Cases 1-5, symbols from other cells are received via Semi-SFI DL through DCI scheduling. In this scenario, no collisions will occur.

[0197] In Cases 1-6, the symbols from other cells are scheduled by DCI for the Semi-SFI DL transmitted by the UL. In this case, the UE200 may also choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 1-6a), or not to receive PDCCH / PDSCH / CSI-RS in the reference cell (Option 1-6b), or may disregard Case 1-6 (Option 1-6c).

[0198] like Figure 9 As shown, as Case 2, six scenarios were envisioned based on the types of symbols in other cells.

[0199] In Case 2-1, the symbols for other cells are Semi-SFI DL. In this case, UE200 may also assume flexible symbols for other cells (Option 2-1a), or may not send PUSCH / PUCCH / PRACH / SRS in the reference cell (Option 2-1b), or may not assume Case 2-1 (Option 2-1c).

[0200] In Case 2-2, the symbols for other cells are Semi-SFI UL. In this case, no collision will occur.

[0201] In Case 2-3, the symbols of other cells are configured for Semi-SFI DL reception via RRC. In this case, UE200 may also choose not to receive PDCCH / PDSCH / CSI-RS in other cells (Option 2-3a), or not to transmit PUSCH / PUCCH / PRACH / SRS in the reference cell (Option 2-3b), or not to consider Case 2-3 (Option 2-3c).

[0202] In Cases 2-4, the symbols of other cells are configured via RRC to transmit Semi-SFI UL. In this case, no conflict will occur.

[0203] In Case 2-5, the symbols from other cells are received via Semi-SFI DL through DCI scheduling. In this case, UE200 may also choose not to receive PDCCH / PDSCH / CSI-RS in other cells (Option 2-5a), or not to transmit PUSCH / PUCCH / PRACH / SRS in the reference cell (Option 2-5b), or not to consider Case 2-5 (Option 2-5c).

[0204] In Cases 2-6, symbols from other cells are scheduled via DCI to transmit Semi-SFI DL signals from the UL. In this scenario, no collisions will occur.

[0205] like Figure 10 As shown, in Case 3, consider the following options depending on the type of symbols of other cells or regardless of the type of symbols of other cells.

[0206] In option 3a, Case 3 may also be absent. For example, SBFD symbols that are not configured for DL ​​reception or UL transmission via RRC can be excluded during reference cell determination (step 1 or step 2).

[0207] In option 3b, there is Case 3, but it can also be assumed that UE200 will not conflict.

[0208] In option 3c, UE200 can follow the same rules as Case 1 or Case 2.

[0209] In option 3d, UE200 can assume that the reference cell symbol is a non-SBFD DL symbol and follow existing rules.

[0210] like Figure 10 As shown, as Case 4, consider the following options, depending on the type of symbols of other cells or regardless of the type of symbols of other cells.

[0211] In option 4a, Case 4 may also be absent. For example, SBFD symbols that are not configured for DL ​​reception or UL transmission via RRC can be excluded during Reference cell determination (step 1 or step 2).

[0212] In option 4b, it is conceivable that the reference cell symbol is a non-SBFD DL / UL symbol, and follows existing rules.

[0213] In option 4c, UE200 can follow the same rules as Case 1 or Case 2. For example, it can determine whether to apply Case 1 or Case 2 based on the priority used when PDCCH / PDSCH / CSI-RS in the DL subband and PUCCH / PUSCH / PRACH / SRS in the UL subband are repeated in the same SBFD symbol. The priority can be predetermined in the wireless communication system 10 or set by RRC. For example, if the priority of PUCCH / PUSCH / PRACH / SRS in the UL subband set by the higher layer is higher than the priority of PDCCH / PDSCH / CSI-RS in the DL subband set by the higher layer, Case 2 can be applied. On the other hand, if the priority of PDCCH / PDSCH / CSI-RS in the DL subband set by the higher layer is higher than the priority of PUCCH / PUSCH / PRACH / SRS in the UL subband set by the higher layer, Case 1 can be applied.

[0214] In Action Example 4, apart from the four scenarios described above, UE200 does not intend to detect the first DCI format scheduled for transmission or reception in the SBFD symbols of the first cell. UE200 also does not intend to detect the first DCI format scheduled for transmission or reception in the non-SBFD symbols of the second cell.

[0215] As described above, in Action Example 4, UE200, assuming the application of Directional collision handling in the SBFD operation cell is configured, determines Directional collision handling based on conditions. These conditions are defined by the options mentioned above and the conditions defined by Alt (e.g., see reference...). Figure 9 as well as Figure 10 ).

[0216] (5.5) Example of action 5

[0217] In Action Example 5, the scenario of configuring Directional Collision Handling for half-duplex communication is described when two or more serving cells contain at least one SBFD operation cell. That is, Action Example 5 can also be considered as an action example based on options 2-3 of Action Example 2 above.

[0218] Action Example 5 primarily explains the third step of determining the handling of conflicts corresponding to symbols of the reference cell and symbols of other cells (the Directional Collision Handling method). Action Example 5 explains the case where the symbol of the reference cell is a non-SBFD symbol, while the symbols of other cells are SBFD symbols.

[0219] In Action Example 5, the method of Directional Collision Handling can be determined based on the SBFD symbols of other cells (SBFD operation cells) according to the following viewpoints.

[0220] Case 5 is the case where UE200 receives PDCCH, PDSCH or CSI-RS in SBFD symbols within the DL subband.

[0221] Case 6 is the case where UE200 transmits SRS, PUCCH, PUSCH or PRACH in SBFD symbols within the UL subband.

[0222] Case 7 is a case in which UE200 does not receive PDCCH, PDSCH or CSI-RS in SBFD symbols in DL subband, and does not transmit SRS, PUCCH, PUSCH or PRACH in SBFD symbols in UL subband.

[0223] Case 8 is a scenario where UE200 receives PDCCH, PDSCH, or CSI-RS in SBFD symbols within the DL subband, and transmits SRS, PUCCH, PUSCH, or PRACH in SBFD symbols within the UL subband.

[0224] Case 9 is the case where dynamic UL transmission is scheduled in SBFD symbols.

[0225] Case 10 is the case of scheduling dynamic DL reception in SBFD symbols.

[0226] Specific methods of Directional Collision Handling include Figure 11 and Figure 12 As shown.

[0227] like Figure 11 As shown, as Case 5, four scenarios are envisioned based on the type of symbols in the reference cell.

[0228] In Case 5-1, the reference cell's symbol is Semi-SFI DL. In this case, no collision will occur.

[0229] In Case 5-2, the reference cell's symbol is Semi-SFI UL. In this case, UE200 may not receive PDCCH / PDSCH / CSI-RS in other cells (Option 5-2a), or it may not consider Case 5-2 (Option 5-2b).

[0230] In Case 5-3, the reference cell's symbols are configured with Semi-SFI DL for DL ​​reception via RRC. In this case, no collision will occur.

[0231] In Case 5-4, the reference cell's symbols are configured via RRC for UL reception using the Semi-SFI DL. In this case, UE200 may not receive PDCCH / PDSCH / CSI-RS in other cells (Option 5-4a), or it may disregard Case 5-4 (Option 5-4b).

[0232] like Figure 11 As shown, as Case 6, four scenarios are envisioned based on the type of symbols in the reference cell.

[0233] In Case 6-1, the reference cell's symbol is Semi-SFI DL. In this case, UE200 may also choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 6-1a), or it may choose not to consider Case 6-1 (Option 6-1b).

[0234] In Case 6-2, the reference cell's symbol is Semi-SFI UL. In this case, no collision will occur.

[0235] In Case 6-3, the reference cell's symbols are configured via RRC for Semi-SFI DL reception. UE200 may choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 6-3a), or it may choose not to consider Case 6-3 (Option 6-3b).

[0236] In Case 6-4, the reference cell's symbols are configured with the UL-received Semi-SFI DL via RRC. In this case, no collision will occur.

[0237] like Figure 11 As shown, in Case 7, no conflict occurs regardless of the type of symbol in the reference cell.

[0238] like Figure 12 As shown, in Case 8, the following options are considered depending on the type of symbols of the reference cell or regardless of the type of symbols of the reference cell.

[0239] In option 8a, UE200 may envision the reference cell symbol as a non-SBFD DL / Flexible / UL symbol and follow existing rules.

[0240] In option 8b, UE200 can follow the same rules as Case 1 or Case 2. For example, it can determine whether to apply Case 1 or Case 2 based on the priority used when PDCCH / PDSCH / CSI-RS in the DL subband and PUCCH / PUSCH / PRACH / SRS in the UL subband are repeated in the same SBFD symbol. The priority can be predetermined in the wireless communication system 10 or set by RRC. For example, if the priority of PDCCH / PDSCH / CSI-RS in the DL subband, set by the higher layer, is higher than the priority of the SBFD symbol, Case 1 can be applied. On the other hand, if the priority of PUCCH / PUSCH / PRACH / SRS in the UL subband, set by the higher layer, is higher than the priority of the SBFD symbol, Case 2 can be applied.

[0241] like Figure 12 As shown, as Case 9, four scenarios are envisioned based on the type of symbols in the reference cell.

[0242] In Case 9-1, the reference cell's symbol is Semi-SFI DL. In this case, UE200 may also choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 9-1a), or not to receive PDCCH / PDSCH / CSI-RS in the reference cell, or the reference cell's symbol may be flexible (Option 9-1b), or Case 9-1 may not be assumed (Option 9-1c).

[0243] In Case 9-2, the reference cell's symbol is Semi-SFI UL. In this case, no collision will occur.

[0244] In Case 9-3, the reference cell's symbols are configured via RRC for Semi-SFI DL reception. UE200 may choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 9-3a), or not to receive PDCCH / PDSCH / CSI-RS in the reference cell (Option 9-3b), or may not consider Case 9-3 (Option 9-3c).

[0245] In Case 9-4, the reference cell's symbols are configured with the UL-received Semi-SFI DL via RRC. In this case, no collision will occur.

[0246] like Figure 12 As shown, as Case 10, four scenarios are envisioned based on the type of symbols in the reference cell.

[0247] In Case 10-1, the reference cell's symbol is Semi-SFI DL. In this case, no collision will occur.

[0248] In Case 10-2, the reference cell's symbol is Semi-SFI UL. In this case, UE200 may not receive PDCCH / PDSCH / CSI-RS in other cells (Option 10-2a), may not transmit PUSCH / PUCCH / PRACH / SRS in the reference cell, may assume the reference cell's symbol is flexible (Option 10-2b), or may not assume Case 10-2 (Option 10-2c).

[0249] In Case 10-3, the reference cell's symbols are configured with Semi-SFI DL for DL ​​reception via RRC. In this case, no collision will occur.

[0250] In Case 10-4, the reference cell's symbols are configured via RRC for UL reception using a Semi-SFI UL. In this case, UE200 may also choose not to transmit PUSCH / PUCCH / PRACH / SRS in the reference cell (Option 10-4a), or not to receive PDCCH / PDSCH / CSI-RS in other cells (Option 10-4b), or may disregard Case 10-4 (Option 10-4c).

[0251] In Action Example 5, apart from the six scenarios described above, UE200 does not intend to detect the first DCI format scheduled for transmission or reception in the SBFD symbols of the first cell. UE200 also does not intend to detect the first DCI format scheduled for transmission or reception in the non-SBFD symbols of the second cell.

[0252] As described above, in Action Example 5, UE200, assuming the application of Directional collision handling in the SBFD operation cell is configured, determines Directional collision handling based on conditions. These conditions are defined by the options mentioned above and the conditions defined by Alt (e.g., see reference...). Figure 11 as well as Figure 12 ).

[0253] (5.6) Example 6 of the action

[0254] In Action Example 6, the scenario of configuring Directional Collision Handling for half-duplex communication is described when two or more serving cells contain at least one SBFD operation cell. That is, Action Example 6 can also be considered as an action example based on options 2-3 of Action Example 2 above.

[0255] Action Example 6 primarily explains the third step of determining the handling of conflicts corresponding to symbols of the reference cell and symbols of other cells (the Directional Collision Handling method). Action Example 6 explains the case where the symbols of the reference cell are SBFD symbols and the symbols of other cells are SBFD symbols.

[0256] In Action Example 6, the method of Directional Collision Handling can be determined based on the SBFD symbols of the reference cell (SBFD operation cell) according to the following viewpoints.

[0257] Case 11 is the case where UE200 receives PDCCH, PDSCH or CSI-RS in SBFD symbols within the DL subband.

[0258] Case 12 is the case where UE200 transmits SRS, PUCCH, PUSCH or PRACH in SBFD symbols within the UL subband.

[0259] Case 13 is a case in which UE200 does not receive PDCCH, PDSCH or CSI-RS in SBFD symbols in DL subband, and does not transmit SRS, PUCCH, PUSCH or PRACH in SBFD symbols in UL subband.

[0260] Case 14 is a scenario where UE200 receives PDCCH, PDSCH, or CSI-RS in SBFD symbols within the DL subband, and transmits SRS, PUCCH, PUSCH, or PRACH in SBFD symbols within the UL subband.

[0261] Specific methods of Directional Collision Handling include Figure 13 and Figure 14 As shown.

[0262] like Figure 13 As shown, as Case 11, five scenarios were envisioned based on the types of symbols in other cells.

[0263] Case 11-1 describes a scenario where the symbols from other cells are configured within the DL subband using RRC to receive SBFD symbols. In this case, no conflict will occur.

[0264] Case 11-2 is a scenario where the symbols in other cells are SBFD symbols transmitted by UL through RRC settings within the UL subband. In this case, UE200 may choose not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 11-2a), or it may choose not to consider Case 11-2 (Option 11-2b).

[0265] In Case 11-3, the symbols of other cells are simultaneously configured via RRC for DL ​​reception in the DL subband and UL transmission in the UL subband using SBFD symbols. In this case, UE200 can follow the same rules as Case 11-1 or Case 11-2. For example, it can determine whether to apply Case 11-1 or Case 11-2 based on the priority used when PDCCH / PDSCH / CSI-RS in the DL subband and PUCCH / PUSCH / PRACH / SRS in the UL subband are repeated in the same SBFD symbol. The priority can be predetermined in the wireless communication system 10 or set via RRC. For example, if the priority of PDCCH / PDSCH / CSI-RS in the DL subband set by the higher layer is higher than the priority of the SBFD symbol, Case 11-1 can be applied. On the other hand, if the priority of PUCCH / PUSCH / PRACH / SRS in the UL subband set by the higher layer is higher than the priority of SBFD symbols, Case 11-2 can be applied.

[0266] In Case 11-4, the symbols from other cells were scheduled by DCI to receive SBFD symbols from DL. In this case, no collision will occur.

[0267] In Case 11-5, the symbols from other cells are SBFD symbols transmitted by UL via DCI scheduling. In such a case, it is also possible not to receive PDCCH / PDSCH / CSI-RS in the reference cell (Option 11-5a), not to transmit PUSCH / PUCCH / PRACH / SRS in other cells (Option 11-5b), or not to consider Case 11-5 (Option 11-5c).

[0268] like Figure 13 As shown, as Case 12, five scenarios were envisioned based on the types of symbols in other cells.

[0269] Case 12-1 is a scenario where the symbols in other cells are set to SBFD symbols received by DL via RRC within the DL subband. In this case, UE200 may choose not to receive PDCCH / PDSCH / CSI-RS in other cells (Option 12-1a), or it may choose not to consider Case 12-1 (Option 12-1b).

[0270] Case 12-2 describes a scenario where the symbols from other cells are configured within the UL subband as SBFD symbols transmitted by the UL via RRC. In this case, no conflict will occur.

[0271] In Case 11-4, the symbols of other cells are simultaneously configured via RRC for DL ​​reception in the DL subband and UL transmission in the UL subband using SBFD symbols. In this case, UE200 can follow the same rules as Case 12-1 or Case 12-2. For example, it can determine whether to apply Case 12-1 or Case 12-2 based on the priority used when PDCCH / PDSCH / CSI-RS in the DL subband and PUCCH / PUSCH / PRACH / SRS in the UL subband are repeated in the same SBFD symbol. The priority can be predetermined in the wireless communication system 10 or set via RRC. For example, if the priority of PDCCH / PDSCH / CSI-RS in the DL subband set by the higher layer is higher than the priority of the SBFD symbol, Case 12-1 can be applied. On the other hand, if the priority of PUCCH / PUSCH / PRACH / SRS in the UL subband set by the higher layer is higher than the priority of SBFD symbols, Case 12-2 can be applied.

[0272] In Case 12-4, the symbols from other cells are SBFD symbols received by DL via DCI scheduling. In such a case, it is also possible not to transmit PUSCH / PUCCH / PRACH / SRS in the reference cell (Option 12-4a), not to receive PDCCH / PDSCH / CSI-RS in other cells (Option 12-4b), or not to consider Case 12-4 (Option 12-4c).

[0273] In Case 12-5, the symbols from other cells are scheduled by DCI to transmit SBFD symbols from UL. In this case, no collision will occur.

[0274] like Figure 14 As shown, in Case 13, consider the following options depending on the type of symbols of other cells or regardless of the type of symbols of other cells.

[0275] In option 13a, Case 13 may also be absent. For example, SBFD symbols that are not configured for DL ​​reception or UL transmission via RRC can be excluded during Reference cell determination (step one or step two).

[0276] In option 13b, there is Case 13, but it can also be assumed that UE200 will not conflict.

[0277] In option 13c, UE200 can follow the same rules as Case 11 or Case 12.

[0278] like Figure 14 As shown, in Case 14, consider the following options depending on the type of symbols of other cells or regardless of the type of symbols of other cells.

[0279] In option 14a, Case 14 may also be absent. For example, SBFD symbols that are not configured for DL ​​reception or UL transmission via RRC can be excluded during Reference cell determination (step one or step two).

[0280] In option 14b, UE200 can follow the same rules as Case 11 or Case 12. For example, it can determine whether to apply Case 11 or Case 12 based on the priority used when PDCCH / PDSCH / CSI-RS in the DL subband and PUCCH / PUSCH / PRACH / SRS in the UL subband are repeated in the same SBFD symbol. The priority can be predetermined in the wireless communication system 10 or set by RRC. For example, if the priority of PDCCH / PDSCH / CSI-RS in the DL subband, set by the higher layer, is higher than the priority of the SBFD symbol, Case 11 can be applied. On the other hand, if the priority of PUCCH / PUSCH / PRACH / SRS in the UL subband, set by the higher layer, is higher than the priority of the SBFD symbol, Case 12 can be applied.

[0281] In Action Example 6, apart from the four scenarios described above, UE200 does not intend to detect the first DCI format scheduled for transmission or reception in the SBFD symbols of the first cell. UE200 also does not intend to detect the first DCI format scheduled for transmission or reception in the non-SBFD symbols of the second cell.

[0282] As described above, in Action Example 6, UE200, assuming the application of Directional collision handling in the SBFD operation cell is configured, determines Directional collision handling based on conditions. These conditions are defined by the options mentioned above and the conditions defined by Alt (e.g., see reference...). Figure 13 as well as Figure 14 ).

[0283] (6) Functions and effects

[0284] In the implementation, when the UE200 contains SBFD operation cells in two or more serving cells, it is envisioned whether to set up directional collision handling. According to this structure, when two or more serving cells contain SBFD operation cells, the actions related to directional collision handling are clarified, and thus appropriate communication can be performed in SBFD.

[0285] (7) Other implementation methods

[0286] The present invention has been described above according to the embodiments, but the present invention is not limited to these descriptions and various modifications and improvements can be made, which will be obvious to those skilled in the art.

[0287] While not specifically mentioned in the above disclosure, the choice of which action example 1 through 5 (hereinafter, which method to use) to use can be set via higher-level parameters. The choice of which option or Alt to use for action example 1 through 5 (hereinafter, which method to use) can be set via higher-level parameters. The supported method can be reported from UE200 as a UE capability. The method to use can also be predefined in the wireless communication system 20. The choice of which method to use can be set by higher-level parameters and reported from UE200 as a UE capability.

[0288] Although not specifically limited, UE capabilities may include information elements indicating whether two or more serving cells contain at least one SBFD operation cell.

[0289] Although not specifically limited, UE capabilities may include an information element indicating a maximum number (X) of at least one SBFD operation cell contained in more than two serving cells. Such an information element may also contain a value for the maximum number (X).

[0290] Although not specifically limited, UE capabilities may include information elements indicating whether more than two serving cells, including more than two SBFD operation cells, are supported.

[0291] Although not specifically limited, UE capabilities may include an information element indicating the maximum number (X) of SBFD operation cells contained in more than two serving cells that are supported. Such an information element may also contain a value for the maximum number (X).

[0292] Although not specifically limited, in cases where two or more serving cells contain at least one SBFD operation cell, UE capabilities may include information elements indicating whether DL / UL-related collision handling is supported in a non-SBFD operation cell.

[0293] Although not specifically limited, in cases where two or more serving cells contain at least one SBFD operation cell, UE capabilities may include information elements indicating whether DL / UL related directional collision handling is supported in the SBFD operation cell.

[0294] Although not specifically limited, in cases where two or more serving cells contain at least one SBFD operation cell, UE capabilities may include information elements indicating whether DL / UL-related collision handling is supported in both the non-SBFD operation cell and the SBFD operation cell.

[0295] Although not specifically limited, in cases where two or more serving cells contain at least one SBFD operation cell, UE capabilities may include information elements indicating whether existing higher-layer parameters (e.g., directional Collision Handling-r16 or directional Collision Handling-DC-r17) are supported.

[0296] Although not specifically limited, when two or more serving cells contain at least one SBFD operation cell, the UE capability may also include information elements indicating whether existing higher-layer parameters (e.g., directionalCollisionHandling-r16 or directionalCollisionHandling-DC-r17) set for the SBFD operation cell are supported.

[0297] Although not specifically limited, when two or more serving cells contain at least one SBFD operation cell, UE capabilities may also include information elements indicating whether new higher-layer parameters (e.g., directionalCollisionHandling-SBFD-CA-r19) newly introduced for the SBFD operation cell are supported.

[0298] Although not specifically limited, when two or more serving cells contain at least one SBFD operation cell, the UE capability may also include information elements indicating whether SBFD operation cell is supported as a reference cell for directional collision handling.

[0299] Although not specifically limited, when two or more serving cells contain at least one SBFD operation cell and the symbol is SBFD, UE capabilities may include information elements indicating whether or not Directional collision handling is supported.

[0300] In the above disclosure, configure, activate, update, indicate, enable, specify, and select can be used interchangeably. Similarly, link, associate, correspond, and map can be used interchangeably, as can allocate, assign, monitor, and map.

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

[0302] The block structure diagram used in the description of the above embodiments ( Figure 4 as well as Figure 5 The 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 also be implemented by combining software within the aforementioned single or multiple devices.

[0303] 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 (component) that enables the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0304] Furthermore, the aforementioned gNB100 and UE200 (the device) can also function as a computer for processing the wireless communication method disclosed herein. Figure 15 This is a diagram illustrating an example of the hardware structure of the device. (As shown...) Figure 15 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.

[0305] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of the device can be configured to include one or more of the devices shown in the figures, or it can be configured to exclude some of the devices.

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

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

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

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

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

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

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

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

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

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

[0316] Furthermore, the device can also 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.

[0317] 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, the notification of information 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 RRC messages, for example, RRC connection setup messages, RRC connection reconfiguration messages, etc.

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

[0319] The processing steps, timing, and processes described in this disclosure can be rearranged without contradiction. For example, the order of steps shown in the methods described in this disclosure indicates the elements of each step, but is not limited to the specific order indicated.

[0320] In this disclosure, specific 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, various actions performed for communication with a terminal can obviously be performed by at least one of the base station and other network nodes besides the base station (e.g., consider MME or S-GW, but not limited to these). The above illustrates the case where there is one other network node besides the base station, but it can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0321] Information and signals (such as data) can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output through multiple network nodes.

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

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

[0324] The various forms / implementations described in this disclosure can be used individually, in combination, or switched between each other during 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 notifying the predetermined information).

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

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

[0327] 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 can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

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

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

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

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

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

[0333] 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 a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

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

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

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

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

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

[0339] Furthermore, the base station in this disclosure can also be replaced by a mobile station (user terminal, hereinafter the same). For example, various methods / implementations of this disclosure can also be applied to a structure that replaces communication between the base station and the mobile station with communication between multiple mobile stations (e.g., it can also be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, it 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.

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

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

[0342] A subframe can also consist of one or more time slots in the time domain. A subframe can be a fixed time length (e.g., 1 ms) that is independent of the parameter set (numerology).

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

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

[0345] 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 time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type B.

[0346] 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 each be referred to by other corresponding names.

[0347] For example, a single subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a single time slot or a single mini-time slot can also be called a TTI. That is, at least one of a subframe or 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. Furthermore, the unit representing TTI can also be called a time slot, mini-time slot, etc., instead of a subframe.

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

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

[0350] Furthermore, when one time slot or one 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 also become the minimum time unit for scheduling. In addition, the number of time slots (mini-time slots) constituting the minimum time unit for scheduling can also be controlled.

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

[0352] Additionally, for long TTIs (e.g., normal TTIs, subframes, etc.), they can be replaced with TTIs with a duration of more than 1ms. For short TTIs (e.g., shortened TTIs, etc.), they can be replaced with TTIs with a duration of less than long TTIs but more than 1ms.

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

[0354] Furthermore, the temporal domain of an RB can contain one or more symbols, and can be 1 time slot, 1 mini-time slot, 1 subframe, or 1 TTI in length. 1 TTI, 1 subframe, etc., can each be composed of one or more resource blocks.

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

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

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

[0358] A BWP can include a UL BWP and a DL BWP. For a UE, one or more BWPs can be set within one carrier.

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

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

[0361] The terms “connected,” “coupled,” or all variations thereof mean any direct or indirect connection or combination between two or more elements, and can include the presence of one or more intermediate elements between 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.

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

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

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

[0365] 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 and second elements does not imply that only two elements can be used herein, or that in any form the first element must precede the second element.

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

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

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

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

[0370] Figure 16An example of the structure of vehicle 2001 is shown. For example... Figure 16 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.

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

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

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

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

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

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

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

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

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

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

[0381] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0382] (Postscript)

[0383] The aforementioned disclosure can also be expressed as follows.

[0384] The first feature is a terminal comprising: a communication unit that communicates with a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and a control unit that, in the case of two or more serving cells including the duplex cell, considers whether to configure a response to conflicts related to the uplink and downlink signals.

[0385] The second feature is that, in the first feature, the control unit either assumes that no response to the conflict is set in the duplex cell, or assumes that a response to the conflict is set in the duplex cell.

[0386] The third feature is that, in either the first or second feature, the control unit, assuming that a response to the conflict is configured in the duplex cell, determines, based on conditions, at least one of the following: the step of determining the reference cell; and the response to the conflict.

[0387] The fourth feature is a base station comprising: a communication unit that communicates with a terminal via a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and a control unit that, when two or more serving cells include the duplex cell, considers whether to configure a response to conflicts related to the uplink and downlink signals.

[0388] The fifth feature is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises: a communication unit that communicates with a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and a control unit that, in the case where two or more serving cells include the duplex cell, considers whether to configure a response to conflicts related to the uplink and downlink signals.

[0389] The sixth feature is a wireless communication method comprising the following steps: step A, communicating with a duplex cell capable of simultaneously communicating uplink and downlink signals within a time-division duplex frequency band; and step B, in the case where two or more serving cells include the duplex cell, considering whether to set up a response to conflicts related to the uplink and downlink signals.

[0390] Label Explanation

[0391] 10 Wireless Communication Systems

[0392] 20 NG-RAN

[0393] 100 gNB

[0394] 110 Receiving Department

[0395] 120 Dispatch Department

[0396] 130 Control Department

[0397] 200 UE

[0398] 210 Wireless Signal Transceiver Unit

[0399] 220 Enlarged Section

[0400] 230 Modulation and Demodulation Section

[0401] 240 Control Signal & Reference Signal Processing Unit

[0402] 250 Encoding / Decoding Unit

[0403] 260 Data Transceiver Department

[0404] 270 Control Department

[0405] 1001 processor

[0406] 1002 Memory

[0407] 1003 Storage device

[0408] 1004 Communication device

[0409] 1005 Input Device

[0410] 1006 Output Device

[0411] 1007 bus

[0412] Vehicle 2001

[0413] 2002 Drive Unit

[0414] 2003 Steering Unit

[0415] 2004 Accelerator Pedal

[0416] 2005 Brake Pedal

[0417] 2006 gearshift lever

[0418] Front wheels around 2007

[0419] 2008 rear wheels (left and right)

[0420] 2009 axle

[0421] 2010 Electronic Control Department

[0422] 2012 Information Service Department

[0423] 2013 Communication Module

[0424] 2021 Current Sensor

[0425] 2022 Speed ​​Sensor

[0426] 2023 Barometric Pressure Sensor

[0427] 2024 vehicle speed sensor

[0428] 2025 Accelerometer

[0429] 2026 Brake Pedal Sensor

[0430] 2027 Gearshift sensor

[0431] 2028 Object Detection Sensor

[0432] 2029 Accelerator Pedal Sensor

[0433] 2030 Driver Assistance Systems Department

[0434] 2031 microprocessor

[0435] 2032 Memory (ROM, RAM)

[0436] 2033 Communication Port

Claims

1. A terminal, comprising: The communication unit communicates with duplex cells capable of simultaneously communicating uplink and downlink signals within the time-division duplex frequency band; and The control unit considers whether to configure a response to conflicts related to the uplink signal and the downlink signal when there are two or more serving cells, including the duplex cell.

2. The terminal according to claim 1, wherein, The control unit envisions that there is no response to the conflict in the duplex cell, or that there is a response to the conflict in the duplex cell.

3. The terminal according to claim 1, wherein, If the control unit assumes that a response to the conflict is configured in the duplex cell, it determines at least one of the following based on conditions: the step of determining the reference cell; and the response to the conflict.

4. A base station, comprising: The communication unit communicates with the terminal via a duplex cell capable of simultaneously transmitting uplink and downlink signals within a time-division duplex frequency band; and The control unit considers whether to configure a response to conflicts related to the uplink signal and the downlink signal when there are two or more serving cells, including the duplex cell.

5. A wireless communication system comprising a terminal and a base station, wherein, The terminal has: The communication unit communicates with duplex cells capable of simultaneously communicating uplink and downlink signals within the time-division duplex frequency band; and The control unit considers whether to configure a response to conflicts related to the uplink signal and the downlink signal when there are two or more serving cells, including the duplex cell.

6. A wireless communication method comprising the following steps: Step A involves communicating with a duplex cell capable of simultaneously communicating uplink and downlink signals within the time-division duplex frequency band; and Step B: In the case where two or more serving cells include the duplex cell, consider whether to set up a response to the conflict related to the uplink signal and the downlink signal.

Images